Live position
In-transit vehicles and stops show on the dispatch desk.
Transportation
Dispatchers see vehicle location, assignments and fuel or power use.
- Vehicle tracking
- Task dispatch
- Energy per trip
- Anomaly reminders
4–8 wksfirst scenario live
50+projects delivered
6protocol families
On-premdata stays local
Location, job status and fuel or power exceptions sit on the dispatch desk instead of in phone calls.
Pain Points
- 01
Location is whatever the driver last reported
- 02
Assigned routes and actual routes do not match
- 03
Fuel and power issues hide until the month-end total
- 04
Faults and delays wait for a phone call
How the system is put together
Keep the equipment you have, connect the data first, then split the views by role. The connection layer takes the most work, and it is where most of our effort goes.
L1
Devices
- Telematics units
- Fuel and power
- Cameras
- Temperature
- Door sensors
PLCs, meters, access control, cameras and sensors already on site. Read what is readable, add a module where it is not, and leave the existing control system alone.
L2
Connection
Modbus · OPC UA · MQTT · HTTP · GB28181 · SDK
Common protocols connect directly. The gateway handles protocol mapping, local buffering and backfill, so the data does not break.
L3
Platform
- Device registry
- Time-series data
- Alert rules
- Work orders
- Roles and audit
Device registry, time-series data, alert rules, work orders, roles and audit in one back end that serves several scenarios.
L4
Applications
- Vehicle tracking
- Task dispatch
- Energy per trip
- Anomaly reminders
- Manager view
- Phone actions on site
- Narrow external lookup
Data is collected once and reused by every scenario added later, which is why the connection layer has to be done properly the first time.
What we deliver
Job on the vehicle
Dispatch, arrival and completion stay on one job.
Energy per trip
Fuel or power is shown per vehicle and trip, with odd trips marked.
Exception notice
Long stops, route drift and device alarms reach dispatch directly.
Where it fits
- Freight fleets
- Yard transfer
- Cold chain in transit
- Work vehicles
What a real day looks like
Not a feature list: what actually happens in a day. These four steps are the common shape of such projects.
- 06:20 Departure
Dispatch assigns the vehicle and pushes route and stops to the cab screen.
- 10:40 Long stop
A truck sits 26 minutes off-route; the dispatch board flags it.
- 11:00 Explained
The driver confirms a queue at the dock, the note stays on the job, and trip time counts as it happened.
Delivery rhythm
Every stage has a checkable output. No six-month build followed by a single review.
- Week 1
Site survey
Walk the site, list devices, available ports and current systems, and mark what reads directly versus what needs a module.
- Week 2
Pick the first scenario
Rank the ideas by impact, feasibility and dependencies, then choose one that proves value without dragging in every department.
- Weeks 3-5
Connect and wire up
Gateways connect devices, data lands on the platform, and alert rules, roles and recipients are configured for a small internal group.
- Weeks 5-7
Pilot
One team or one building uses it for real; rules and screens change with feedback until false and missed alarms settle.
- Week 8
Accept and repeat
Check every acceptance item, finish documentation and training, then decide which buildings, lines or sites come next.
Acceptance is these three lines
The three items below come from projects of this kind and go into the acceptance sheet, instead of relying on a general impression.
Dispatch sees the current position
Empty runs and detours have a track
Fuel or power exceptions are found per trip
Related Cases
IoT
IoT Management Platform
Scattered plant devices and protocols, brought into one platform for inventory, boards and alerts—less ad-hoc ops handoff.
Device onboarding and inventory in one place
Learn More →IoTDevice Control System
Remote device control and monitoring system
Command results can be acknowledged
Learn More →Related solutions
Questions
Where does this industry get stuck?
Location is whatever the driver last reported Assigned routes and actual routes do not match Fuel and power issues hide until the month-end total Faults and delays wait for a phone call
What does Yifu do here?
Live position: In-transit vehicles and stops show on the dispatch desk. Job on the vehicle: Dispatch, arrival and completion stay on one job. Energy per trip: Fuel or power is shown per vehicle and trip, with odd trips marked. Exception notice: Long stops, route drift and device alarms reach dispatch directly.
What changes after it is in place?
Dispatch sees the current position Empty runs and detours have a track Fuel or power exceptions are found per trip
Do we have to replace our current systems?
No. The platform reads through interfaces or gateways and the existing systems stay in use. Only modules nobody maintains are worth replacing.
What does it cost, and how soon is it live?
Priced by scenarios and device connection points: a site survey produces the list, then a quote and schedule. Most projects have a first scenario live in four to eight weeks.
Free diagnosis
Tell us where it gets stuck
Leave one contact. We send how similar projects were handled plus a scenario list. If it is not worth doing, we say so.
- A 30-minute call to judge whether it is worth doing
- A workable scenario list and timeline
- No consulting fee up front
Get Industry-specific Solution
Phones are answered 9:00-18:00 on weekdays, or scan the WeChat code.