By the VectorLink Engineering Team
Real-time fleet visibility is the foundation of a modern shuttle operation, but it is the floor, not the ceiling. Once you can see the operation, the next question is what else the operation is connected to that you cannot see yet.
Most operations today still answer that question across several disconnected systems. Maintenance lives in one tool. Workforce scheduling lives in another. Telematics lives in a third. The operations dashboard, if there is one, sees fleet location and very little else. Cross-domain questions ("is deferred maintenance affecting headway," "are staffing patterns aligned with peak demand," "is this driver's performance correlated with specific shifts or specific vehicles") can only be answered hours later by hand, by someone willing to compile data across three tools and a spreadsheet.
That is the layer of the operation our current roadmap is focused on closing.
Maintenance as part of the live operation
Vehicle health, utilization, and service history live in the same platform as the dispatcher's view in our product roadmap. Three capabilities follow from that:
- Preventive maintenance scheduling that uses actual vehicle utilization, not calendar averages. A bus running a high-load loop ten hours a day reaches service intervals on a different timeline than one assigned to a lighter route.
- Predictive maintenance signals from OBD-II/J1939 and IMU sensor data, surfaced as recommendations before a fault becomes a road call.
- Repair-or-replace economics tracked at the vehicle level, with maintenance cost trends visible alongside utilization. A vehicle whose service costs are climbing while its uptime is falling can be flagged as a candidate for replacement well before it becomes an availability problem.
When the maintenance picture lives next to the operations picture, "the bus is in the shop" stops being a single line item. It becomes a service capacity event with a known impact on headway, and a planning input for the next shift.
Workforce context inside the dispatcher's view
The dispatcher and the workforce manager are looking at the same operation, but they almost never look at the same screen. We are integrating bidirectionally with workforce management partners so that the operational picture and the staffing picture share context.
What that looks like in practice:
- Dispatchers see real-time clock state, shift countdowns, and scheduled breaks alongside vehicle location and route assignment
- Driver assignments push into the WFM system automatically, removing manual handoffs that lose information
- Staffing gaps surface as operational alerts, not as a discovery the dispatcher makes when nobody shows up
- Driver performance data correlates with route, vehicle, and shift, supporting evidence-based coaching
We are deliberately not replacing the workforce management platform. Drivers should not have to learn a new app for shift bidding, clock in/out, or messaging. The integration is the product, not a new employee-facing tool.
What this enables, and what it does not
Connecting fleet, maintenance, workforce, and rider data does not turn the operation into a fully autonomous system. It does not eliminate the need for experienced dispatchers, operations managers, or maintenance leads. The expertise still matters, and probably matters more.
What it does is move the routine cross-domain questions out of "spend an afternoon compiling" and into "show me." The expertise gets directed at the harder problems, not the data assembly.
Where this is going
Looking further out, the connected operation enables capabilities that are not realistic today: dynamic route adjustment based on flight bank arrivals, demand-driven fleet sizing, integrated airport data platform exchange, and rider communications that adapt to real conditions across mobile, onboard, and curbside channels. None of those are products you can buy this quarter. All of them are easier to build on top of an already-connected operation than from the disconnected starting point most operators face today.
The visibility layer is the prerequisite. The connected layer is the work in progress. Where it leads is the part of the roadmap we are most excited about.