Product
One Fleet. Every Role. Any Device.
The Open VTS application puts live fleet maps, push notifications, trip timelines, and dispatch controls in the hands of every team member — each seeing only the vehicles, alerts, and actions their role requires, on desktop or mobile, with no native app install.
Who this is for
Fleet managers reviewing performance summaries, dispatchers making real-time reassignment decisions, field supervisors checking vehicle status between sites, and drivers reviewing personal trip logs and assigned alerts.
What this is
The fleet interface every team member actually uses
Positioning
Why the Application Layer Matters
The daily interface
The Open VTS application is everything your team touches. It renders live GPS data as fleet maps, translates device events into push notifications, organizes trip history into searchable timelines, and provides dispatch-action controls — all through a responsive web interface that works on desktops, tablets, and phones without a native app install.
The visibility gap
Most fleet platforms give every user the same view — a dense admin dashboard designed for someone who monitors all day. A dispatcher looking for an available vehicle wastes time scrolling past analytics panels. A driver checking their own trips sees fleet-wide data they should never access. A field supervisor on a phone gets a desktop layout squeezed into a small screen. Same interface, different needs — nobody works efficiently.
The role-filtered experience
Open VTS filters the entire experience by role. Managers see fleet-wide KPIs, alert queues, and utilization trends. Dispatchers see an assignment board with vehicle availability and quick-action controls. Drivers see only their own vehicle, personal trip log, and alerts directed to them. Each role loads a purpose-built view — not a permission-restricted version of the admin panel.
Roles
Who Uses the Application
Fleet Manager
Starts the day reviewing overnight alerts and fleet utilization. Needs at-a-glance summaries, exception-based views, and the ability to drill into any vehicle's recent history without switching tools.
What they access
Fleet-wide KPI dashboard, alert queues with priority filtering, utilization trends, trip-history search across all vehicles, scheduled report configuration, and user-role administration.
Dispatcher
Works the live board all shift — assigning vehicles, monitoring delivery progress, and responding to delays. Decisions happen in seconds; the interface must surface availability and status instantly.
What they access
Live assignment board with vehicle availability status, drag-and-drop trip reassignment, driver messaging, map-based vehicle locate, quick-action controls for engine cut and immobilizer, and geofence alert feed.
Field Supervisor
Moves between job sites with intermittent connectivity. Checks vehicle locations and crew status from a phone screen between meetings. Needs a view that loads fast and works offline.
What they access
Mobile-optimized fleet map with cached tiles, vehicle-group filter for their assigned crews, recent trip summaries, alert history for supervised vehicles, and offline access via the PWA with background sync.
Driver
Opens the app to review completed trips, check tomorrow's assignment, or acknowledge a maintenance alert. Should never see fleet-wide data, other drivers' information, or management analytics.
What they access
Personal trip log with route replay, assigned-vehicle status and location, maintenance and compliance alerts directed to them, and trip-acknowledgment actions. Zero visibility into fleet-wide data.
Use Cases
Everyday Operational Workflows
Morning Dispatch Readiness
The dispatch team opens the assignment board before the first vehicle leaves. Flagged vehicles with overnight alerts are immediately visible. Unassigned trips are listed by priority. As drivers clock in through the app, they appear on the live map — available for assignment.
Field Check Between Job Sites
A supervisor pulls up the mobile view on a phone between site visits. Cached map data shows recent vehicle positions even on a weak signal. When connectivity restores, new alerts and position updates sync silently in the background — no manual refresh.
Driver End-of-Day Trip Review
A driver opens their personal view to review the day's completed trips, acknowledge a maintenance alert, and check tomorrow's assignment. The interface shows only their vehicle and their trips — nothing fleet-wide, nothing from other drivers.
After-Hours Geofence Breach
An unauthorized movement alert fires at 1 AM. The on-call manager receives a push notification, opens the mobile view in seconds, confirms the vehicle's live position on the map, and escalates to security — without a desktop, VPN, or control room.
Last-Mile ETA Communication
Dispatch monitors delivery vehicles approaching customer locations on the live map. When a vehicle enters the final-mile geofence, the dispatcher triggers a customer notification from the dispatch board — no phone call, no manual timestamp.
Outcomes
What Better Fleet Access Delivers
Decisions at the Point of Need
Managers act from hotel lobbies. Supervisors act from job sites. Dispatchers act from the board. The interface works wherever the decision-maker is — not just in the control room.
Noise Elimination Through Role Filtering
Each user sees only the vehicles, alerts, and metrics their role requires. A driver never encounters fleet-wide analytics. A dispatcher never hunts for their assignment queue inside a management dashboard.
Immediate Incident Response
Push alerts reach the right person in seconds and link directly to the relevant vehicle on the map. The mobile-optimized view means assessment and action happen on the same screen, on any device.
First-Shift Productivity
Purpose-built views mean new dispatchers and drivers learn only the interface they actually use — not an expansive admin panel they must mentally filter. Most users operate independently within their first working shift.
Auditable Accountability Per User
Every trip acknowledgment, alert dismissal, dispatch reassignment, and command action is timestamped and attributed to a named user and role. Audit trails are built into the interaction layer, not reconstructed after the fact.
FAQ
Questions About the Application
6questionsNo. The application is the user-facing interface included with every Open VTS deployment. Desktop and mobile access, role-based views, and push notifications are standard — not a paid add-on or premium tier.
No. The application is a responsive web app that runs in any modern mobile browser. For an app-like experience, users can add it to their home screen as a PWA — no app store submission, no MDM enrollment, no separate codebase to maintain.
Admins define custom roles with specific permissions: which vehicles are visible, which data panels are exposed, which actions are available (view-only, dispatch, command, admin). Roles can be scoped to fleets, vehicle groups, or individual assets. The interface enforces these boundaries at every level.
The PWA continues to display cached map tiles and recent trip data. Any pending actions — alert acknowledgments, dispatch commands — queue locally and sync automatically when the connection restores. No manual refresh or re-login required.
Yes. The driver role surfaces only the driver's assigned vehicle, personal trip history, and alerts directed to them. They cannot see fleet-wide data, other vehicles, other drivers, or management-level analytics and reports.
Via the browser's Push API, supported on modern Android and iOS browsers. Alert routing rules determine which event types — geofence, SOS, speed, maintenance — reach which user roles. Notifications link directly to the relevant vehicle on the map.
Next Step
Give Every Team Member the Fleet View They Need
Managers, dispatchers, supervisors, and drivers — each with a purpose-built interface on any device. Included with every Open VTS deployment.