Contact Request a Demo

Ordova Dispatch · Live operations

See every delay and breakdown the moment it happens.

From 03:30 pull-out to end-of-day closure, Ordova watches every vehicle, driver, trip and depot, and brings the dispatcher only what needs a decision.

Operations Command Center

Your whole fleet on one screen.

Running, reserve and broken-down buses; scheduled vs. active trips; OTP, load factor, driver availability, incidents, exceptions, fuel anomalies and revenue leakage. Select a tile to drill in. This is how the Command Center is designed to read.

Demo data · not an operator’s results
Full Ordova application window: navigation sidebar grouped by Operations, Fleet, Asset & Cost, and Analytics, with the Command Center dashboard showing live KPIs, a fleet map and depot performance.
The Ordova Command Center today: live KPIs, fleet map, fleet composition and depot performance Real Ordova screen · demo data

Exceptions-first operating model

Every problem is ranked and tracked until it’s fixed.

Ordova auto-detects schedule deviations, vehicle and driver no-shows, ghost trips, HOS breach risk, overdue maintenance, fuel anomalies, occupancy breaches, GPS silence, bunching and double-booking, then ranks them by severity × passenger impact × time-to-cascade.

Critical

Safety incidents, accidents, multi-route breakdown cascades, HOS violations in progress.

Immediate dispatcher action

Breakdowns, no-shows, safety events.

Supervisor approval

Reroutes, service suspensions, cross-depot vehicle sharing, emergency fleet activation.

Auto-resolvable

Minor headway correction notices, routine expiry reminders, auto-reconciliation of closed work orders.

Tracked to closure

  1. Detected
  2. Acknowledged
  3. Action Recommended
  4. Approved
  5. Executed
  6. Verified
  7. Closed

Every exception gets a ticket with timestamped status. Breakdown closures require dispatcher sign-off and a maintenance root-cause code.

Automatic escalation

0

Exception raised to dispatcher

X min

Unresolved critical → Operations Manager

2X min

Still unresolved → duty Operations Head

Live dispatch

One card per problem, with a suggested fix.

Problem in plain language. Impact. A ranked, explainable recommendation with alternatives and expected result. Approve, reject (with a reason code) or modify, then Ordova executes, verifies and logs the outcome.

Action Center Interactive simulation of the Ordova decision card
Illustrative scenario · demo data
EX-24-0817 Critical Awaiting approval

Problem

Bus 4021 on Route 12 stalled at 8th & Main

Detected via GPS stall + driver call

Impact

  • 47 passengers onboard
  • Next 3 trips will bunch
  • 12-min cascade delay projected
Recommended action & alternatives

Expected result

Restores schedule within 18 min · deadhead cost $34

What dispatchers see in Ordova today

The current Action Center presents each exception as a Problem / Impact / Recommended options card. When no vehicle or driver substitution applies (a road closure, for instance), the card says so plainly and asks the dispatcher to decide.

Ordova decision dialog for a road-closure exception showing Problem, Impact and Recommended Options sections with Close, Reject and Approve buttons.
Action Center decision card (real screen) Real Ordova screen · demo data

A day in the control center

A day in the control room with Ordova.

Monitoring

Depot pull-out readiness, vehicles released by maintenance, driver first-report, weather/road advisories.

Typical problems

Vehicle failed pre-trip inspection; driver called in sick with no relief; depot congestion delaying pull-out.

Ordova auto-detects

Vehicles not released by maintenance past cutoff; drivers not clocked in 30 min before report; low fuel/charge vehicles on long blocks.

Ordova recommends

Best-fit substitute vehicle and best-fit reserve driver.

Human approval

Any substitution that changes a block, driver reassignment, use of reserve fleet.

Auto-executed

Status flags, roster reconciliation, pre-trip checklist validation, depot supervisor alerts.

KPIs % blocks pulled out on time · vehicle readiness · report-in compliance

Dispatch workflows

How common disruptions are handled.

Each workflow defines where Ordova acts on its own, and where a person must decide. Explore all 25 scenarios on the Solutions page.

Bus breakdown during peak hours

  1. Detection
  2. Impact analysis
  3. Identify replacement vehicle
  4. Identify driver
  5. Check route/depot compatibility
  6. Passenger impact calc
  7. Recommend
  8. Approve
  9. Dispatch
  10. Notify driver/passengers
  11. Update trip/KPI
  12. Close

Driver doesn’t report for duty

  1. Detection (roster)
  2. Reserve shortlist
  3. HOS/qualification check
  4. Recommend
  5. Approve
  6. Notify driver app
  7. Update roster
  8. Close

Route demand suddenly increases

  1. Detection (occupancy)
  2. Nearest reserve check
  3. Recommend tripper
  4. Approve
  5. Dispatch
  6. Monitor load post-deployment
  7. Close

Accident on route

  1. Detection
  2. Safety protocol trigger
  3. Emergency services notify
  4. Reroute affected buses
  5. Replacement dispatch
  6. Incident investigation ticket
  7. Close after safety sign-off

Road closure (planned or unplanned)

  1. Detection / manual entry
  2. Identify affected blocks
  3. Generate legal detour
  4. Approve
  5. Push to driver apps
  6. Update PIS
  7. Monitor detour OTP
  8. Close when road reopens

Human decision point

Operations in the product

Screens from the Ordova app.

Ordova AI Intelligence dashboard showing a planning readiness score of 89 out of 100 broken into fleet, crew, depot capacity, demand coverage and operational risk dimensions, with a recommended pre-planning sequence.
AI Operations Intelligence & Planning Readiness Real Ordova screen · demo data

Next step

Book a demo with our team.

We’ll walk you through Ordova using your routes, fleet size and current systems.

Request a Demo Talk to a Transportation Expert