Fleet Cost Reduction & Maintenance Optimization | The Freedom Masons
Project 05 / Operations / Fleet Management

Root cause found in weeks. Millions saved in maintenance.

A city transit operator watched fleet maintenance costs spiral with no clear cause. We came in, found the root problem within weeks, and redesigned how they manage every vehicle in the fleet.

Cost Analysis Maintenance Systems Fleet Operations
Client
Metro Transit Solutions
Sector
Transport · Fleet operations
Scope
Audit + system redesign
Our role
Operations consultant & analyst
City bus fleet at transit depot with maintenance equipment
The Project

Costs rising. No one knew why. Every bus in the fleet bleeding money.

A city transit operator managed a fleet of several hundred buses. Maintenance costs had been climbing for three years. Management tried new suppliers, new schedules, and new supervisors. Nothing worked. The problem kept growing.

The operator needed someone to find the root cause, not another band-aid. We were brought in to audit the entire maintenance system: how work was scheduled, how parts were ordered, how failures were recorded, and how decisions were made.

We found the problem in the data: maintenance was being scheduled by calendar date, not by actual vehicle condition. Buses that needed early attention were waiting. Buses that did not need work were being opened up. Parts were being replaced on guesswork. Labor hours were being spent on the wrong vehicles.

The result: a new maintenance system built on actual vehicle condition, usage patterns, and failure history. Costs dropped. Downtime dropped. And the operator had a system it could run without us.

What was going wrong

Maintenance costs had climbed for three years. Management tried new suppliers, new schedules, and new supervisors. Nothing stopped the bleeding. Every month the numbers got worse.

No one had audited the actual system: how work orders were created, how parts were allocated, or how mechanics decided what to fix. Decisions were made on habit, not on evidence.

How we found it

We audited six months of maintenance records, parts invoices, and work orders. The pattern was clear: buses were being serviced on fixed calendar intervals regardless of condition.

Some vehicles were being over-serviced. Others were being under-serviced until they failed on the road. Parts inventory was being driven by supplier deals, not by actual failure rates.

Where it landed

The operator received a condition-based maintenance system: service when the data says service, not when the calendar says so. Parts ordering was tied to actual failure patterns. And every mechanic had clear criteria for what to check and when.

Costs dropped within the first quarter. Breakdowns fell. And the operator had a system it could manage, measure, and improve on its own.

Our Method

How the work ran

The same five stages we run on every engagement, applied here. Hover or tap a stage to see what it covered.

01Scope the Decision
02Set the Standard of Proof
03Test the Evidence
04Challenge the Answer
05Deliver the Verdict
01
Scope the Decision What evidence would prove where the money was actually going? We defined the data we needed before asking for a single record.
What the operator got

The deliverables, built to be run

Every item below was written to be used by the mechanics who fix the buses and the managers who run the depot, not to sit in a file.

  • Complete maintenance audit: six months of records, costs, and failure patterns
  • Condition-based service schedule tied to actual vehicle usage and wear
  • Parts inventory system based on real failure rates, not supplier deals
  • Mechanic checklists with clear criteria for what to inspect and when
  • Management dashboard for tracking cost, downtime, and fleet health

What it added up to

What this engagement put in place, and the evidence base behind the team that delivered it.

0 weeks from start to root cause identification
0 complete maintenance system redesigned from evidence
0 years of climbing costs before the audit began
0 key drivers found: scheduling, parts, labor, breakdowns
0 prior condition-based maintenance system existed
0 months from audit start to full system rollout

Facing a decision like this?

Tell us the decision you face. A senior engineer will review it and reply within two business days. If we are not the right firm for it, we will say so.

Every inquiry is reviewed by a senior engineer. Response within 2 business days.