Resources
KPIs, roadmap and common questions.
The KPIs we measure, the roadmap from first module to go-live, and straight answers to the questions buyers ask most.
KPI framework
12 KPIs to track.
Each KPI comes with its formula, a typical target for a large public operator and a clear owner. During onboarding we set your own targets from your current baseline.
| Group | KPI | Formula | Target | Frequency | Owner |
|---|---|---|---|---|---|
| Operations | On-Time Performance | Trips within ±X min / total trips | 90% | Daily | Ops Manager |
| Fleet | Fleet Availability | Available buses / total fleet | 92% | Daily | Fleet Manager |
| Scheduling | Deadhead Ratio | Deadhead miles / total miles | 8% | Weekly | Scheduling Manager |
| Drivers | Overtime % | OT hours / total hours | 5% | Weekly | Driver Supervisor |
| Maintenance | Preventive Maintenance Compliance | On-time PM / scheduled PM | 95% | Monthly | Maintenance Manager |
| Fuel | Fuel Cost per km | Total fuel cost / total km | Trend down | Monthly | Fuel Manager |
| Passenger Service | Load Factor | Passengers / capacity (avg peak) | 70–90% | Daily | Ops Manager |
| Revenue | Revenue Leakage % | (Expected − actual revenue) / expected | 2% | Monthly | Finance Manager |
| Safety | Incidents per 100k km | Incidents / (km / 100,000) | 0.3 | Monthly | Safety Manager |
| Compliance | Regulatory Filing Timeliness | On-time filings / total | 100% | Per cycle | Compliance Officer |
| Sustainability | CO₂ per passenger-km | Emissions / passenger-km | Trend down | Quarterly | Sustainability Lead |
| Financial | Cost per Revenue-km | Total operating cost / revenue-km | Trend down | Monthly | Finance Manager |
Track from day one: OTP · fleet availability · overtime % · preventive maintenance compliance · breakdown rate · trip cancellation rate · load factor · deadhead ratio · revenue leakage % · incidents per 100k km.
Implementation roadmap
Go live in phases.
A live dashboard in six months. Dispatch, optimisation and AI follow, one agreed phase at a time. Your people approve anything affecting safety, staff or passengers.
-
Foundation
- Master data: vehicles, drivers, routes
- Maintenance system integration
- AVL feed
- Basic dashboard
-
Operations
- Exceptions queue
- Live dispatch workflows
- PIS integration
- Mobile driver app
-
Optimization
- Run-cutting / blocking optimization engine
- Fuel reconciliation
- Revenue reconciliation
-
AI / Predictive
- Predictive maintenance
- Demand forecasting
- AI-recommended substitutions
-
Autonomous Operations
- Expanded auto-execution for low-risk, high-frequency decisions
- Full closed-loop optimization
- Continuous human oversight on safety- and labour-impacting actions
FAQ
Common questions.
Does Ordova replace our maintenance, ticketing or ERP systems?
No. Ordova is the operational orchestration layer. Your maintenance system (for example IBM Maximo) remains the system of record for asset and maintenance data, AFC for revenue transactions, ERP for the financial ledger and HR for employee master data. Ordova owns operational and scheduling data and the decision about what should happen right now.
Will the AI make decisions without a person?
Not for anything safety-critical, labour-impacting or passenger-facing. Vehicle and driver reassignment, reroutes, trip cancellations and extra service are recommended and require human approval. Only low-risk, reversible, high-frequency actions, such as “hold 30 seconds” corrections or compiling a regulatory report for human review, can run automatically, and classifications are configurable by the Authority.
What happens if an integration feed goes down?
Ordova falls back to last-known-good data with a visible “stale data” flag and blocks any auto-execution that depends on that feed until it is fresh again. Messages use idempotency keys with retry and exponential backoff; failed syncs queue for reconciliation and alert the integration owner.
Are the ROI figures on this site customer results?
No. They are illustrative, conservative planning assumptions for a reference fleet of 5,000 buses. They are not drawn from any specific authority’s actuals and should be replaced with your own baseline before use in a business case.
How long does implementation take?
Ordova is rolled out in phases: Foundation (0–6 months), Operations (6–12), Optimization (12–18), AI/Predictive (18–30) and Autonomous Operations (30+ months). Benefits typically ramp over 18–24 months; Year 1 usually realises 30–40% of steady-state benefit. Actual timelines depend on scope and data readiness.
How is access controlled?
Through role-based access with permissions scoped by action (view live operations, approve tactical or strategic dispatch, edit schedules, approve maintenance, financial reports, system configuration) and by depot. Every action, including approving, rejecting or modifying an AI recommendation, is written to the audit trail.
Can Ordova be deployed on-premises or in a government cloud?
Talk to us about your hosting, data-residency and enterprise security requirements. Deployment options are agreed per engagement.
Which vehicle types and fleets does Ordova support?
Ordova’s planning constraints cover vehicle capacity and type, fuel/charge/range profiles and charging-window feasibility, including range-aware blocking for electric fleets. Share your fleet mix with us and we’ll walk through how it is modelled.
More resources
Documentation
Product and integration documentation is shared with evaluating organizations during the demo and procurement process.
Request documentationNext step
Book a demo with our team.
We’ll walk you through Ordova using your routes, fleet size and current systems.