Ordova Connect · Integrations
Works with your maintenance, GPS, ticketing and ERP systems.
Ordova owns the “what should happen right now” decision. Your asset, revenue, financial and employee systems stay the systems of record for what they already do well.
Integration architecture
13 systems Ordova connects to.
Select a system to see what flows into Ordova, what flows back out, and who owns the record.
Assets & maintenance
Vehicles & workforce
Operational orchestration layer
Ordova
Owns the “what should happen right now” decision. The underlying asset, revenue, financial and employee records stay where they are.
- Plan
- Schedule
- Dispatch
- Operate
- Report
IBM Maximo
- Into Ordova
- Vehicle availability, work order status, maintenance schedule
- Out of Ordova
- Vehicle usage/mileage, fault reports from drivers
- System of record
- Maximo owns asset and maintenance master data
Fuel Management
- Into Ordova
- Fuel inventory, transaction logs
- Out of Ordova
- Consumption anomalies for investigation
- System of record
- Fuel system owns inventory data
IoT / Telemetry
- Into Ordova
- Engine health, fuel/energy use, harsh-event data
- Out of Ordova
- None
- System of record
- Telemetry vendor (raw); Ordova interprets
AVL / GPS
- Into Ordova
- Live position, speed
- Out of Ordova
- Geofence and route definitions
- System of record
- AVL vendor (raw telemetry); Ordova owns operational interpretation
HR / Workforce Management
- Into Ordova
- Driver certifications, leave, contracts
- Out of Ordova
- Actual hours worked, duty records
- System of record
- HR owns employee master data
Mobile apps (driver / passenger)
- Into Ordova
- Driver check-ins, incident reports
- Out of Ordova
- Duty assignments, notifications
- System of record
- Ordova
Ticketing / AFC
- Into Ordova
- Boarding counts, revenue
- Out of Ordova
- Trip/route reference data
- System of record
- AFC system owns revenue transactions
ERP
- Into Ordova
- Cost centres, budget codes
- Out of Ordova
- Actual cost/utilization data for financial reporting
- System of record
- ERP owns the financial ledger
Payment Systems
- Into Ordova
- Fare transaction confirmation
- Out of Ordova
- None
- System of record
- Payment processor
Traffic Management
- Into Ordova
- Incidents, closures, congestion
- Out of Ordova
- None
- System of record
- External authority
Weather APIs
- Into Ordova
- Forecasts, alerts
- Out of Ordova
- None
- System of record
- External provider
Passenger Information Systems
- Into Ordova
- None
- Out of Ordova
- Real-time arrivals, disruption notices (GTFS-realtime)
- System of record
- Ordova owns service-status truth
Government Reporting
- Into Ordova
- None
- Out of Ordova
- Compliance reports, SLA metrics
- System of record
- Ordova compiles; the Authority owns submission
Revenue & finance
External signals
Passengers & reporting
Maintenance systems · example: IBM Maximo
Maintenance status goes straight to dispatch.
Two-way synchronisation of asset status and work orders. Maximo remains the system of record for maintenance and asset data; Ordova remains the system of record for operations and scheduling.
System of record · maintenance & assets
IBM Maximo
- Asset master
- Maintenance & schedules
- Work orders
- Vehicle availability
System of record · operations & scheduling
Ordova
- Operations
- Scheduling
- Dispatch
- Operational decisions
IBM Maximo owns
- Asset master data
- Maintenance and schedules
- Work orders
- Vehicle availability
Ordova owns
- Operations
- Scheduling
- Dispatch
- Operational decisions
What the integration enables
- Dispatchers see read-only, near-real-time availability (target lag 1–5 minutes)
- Maintenance-overdue vehicles are blocked from the next-day assignable pool, automatically for hard safety thresholds, as advice for soft ones
- Schedulers are notified of coverage gaps and offered substitute vehicles
- Vehicle mileage and driver fault reports flow back to maintenance
- Overnight bay sequencing with a prioritised work-order list from the day’s fault logs
Ordova does not replace Maximo, and a vehicle removed from the Ordova operational fleet is not deleted from Maximo. Integration specifics (authentication, endpoints, sync frequency) are agreed per deployment.
Integration resilience
What happens when a data feed fails.
Legacy AVL and telemetry data quality is the number-one implementation risk. Ordova is built to degrade safely rather than act on stale information.
Last-known-good fallback
If a feed such as Maximo is unavailable, Ordova falls back to last-known-good status with a visible “stale data” flag.
Safe automation
Auto-execution that depends on a stale feed is blocked until the feed is fresh again.
Idempotent messaging
All inbound and outbound messages use idempotency keys and retry with exponential backoff.
Reconciliation queue
Failed syncs queue for reconciliation and alert the integration owner.
Open by design. RESTful APIs for custom integrations and data exchange, and GTFS-realtime export for passenger information.
Reference
Which system owns which data.
| System | Data into Ordova | Data out of Ordova | System of record |
|---|---|---|---|
| IBM Maximo | Vehicle availability, work order status, maintenance schedule | Vehicle usage/mileage, fault reports from drivers | Maximo owns asset and maintenance master data |
| Fuel Management | Fuel inventory, transaction logs | Consumption anomalies for investigation | Fuel system owns inventory data |
| IoT / Telemetry | Engine health, fuel/energy use, harsh-event data | None | Telemetry vendor (raw); Ordova interprets |
| AVL / GPS | Live position, speed | Geofence and route definitions | AVL vendor (raw telemetry); Ordova owns operational interpretation |
| HR / Workforce Management | Driver certifications, leave, contracts | Actual hours worked, duty records | HR owns employee master data |
| Mobile apps (driver / passenger) | Driver check-ins, incident reports | Duty assignments, notifications | Ordova |
| Ticketing / AFC | Boarding counts, revenue | Trip/route reference data | AFC system owns revenue transactions |
| ERP | Cost centres, budget codes | Actual cost/utilization data for financial reporting | ERP owns the financial ledger |
| Payment Systems | Fare transaction confirmation | None | Payment processor |
| Traffic Management | Incidents, closures, congestion | None | External authority |
| Weather APIs | Forecasts, alerts | None | External provider |
| Passenger Information Systems | None | Real-time arrivals, disruption notices (GTFS-realtime) | Ordova owns service-status truth |
| Government Reporting | None | Compliance reports, SLA metrics | Ordova compiles; the Authority owns submission |
IBM and Maximo are trademarks of International Business Machines Corporation. Naming a system category does not imply a certified integration with any specific vendor product.
Next step
Show us your systems and we’ll map the integration.
Bring your system inventory and we’ll show which records stay where, and what flows between them.