GreenbayGreenbay

Plan vs actual analytics

Compare what was scheduled with what actually happened. One consistent definition of on-time across every data source.

Real scenario
The situation

Quarterly review. The headline OTP number sits comfortably above the contract target.

The problem

The data comes from three systems with three different definitions of on-time. Apply one consistent rule and the real number lands several points lower. Nobody knows until the penalty notice arrives.

With Greenbay

Greenbay applies one definition across every source. Revenue assurance surfaces deviations immediately, before they become penalties.

Root cause analysis across all operational data

Plan vs actual comparison

Side-by-side at route, block, or fleet level, for any day, week, or period. Same methodology end to end.

PlanActualRoute AbehindRoute BbehindRoute Cahead

Revenue assurance

Quantify missed kilometres, cancellations, and late starts in pounds, not anecdotes. Prioritise by penalty risk.

Revenue at riskRoute AHighRoute BMedRoute CLow

Root cause analysis

Not just that Route 171 was late. Whether it was charging, blocking, vehicle, or scheduling, traced across systems.

?vehiclechargeschedule

Cross-organisational alignment

Custom views per role: ops sees OTP, maintenance sees work orders, management sees utilisation. One dataset under all of them.

Eliminate blind spots

Cross-source validation flags when a scheduled trip has no completed match, or a charger session has no vehicle record.

!
Connected

Where this fits

Aggregates allocations, live performance, depot utilisation, and (for electric fleets) charging into one set of unified views.

Ready to see it in action?

Book a 30-minute walkthrough tailored to your depot setup. We'll show you how Greenbay connects your entire operation.

Request a demo
No commitment
Your depot setup
30-minute call