Library — Fleets and maintenance
Keeping fleets available
For anything that moves — aircraft, vehicles, vessels, rolling stock — availability is decided in maintenance long before it shows on the schedule.
01The problem
Availability is lost in the gaps between maintenance, supply and operations.
A fleet’s availability rests on a chain that is easy to break: the condition of each asset, the maintenance it is due, the parts that work needs, the people and bays to do it, and the schedule that assumes all of it will happen on time. When a part is late, an inspection finds more than expected or a bay is occupied, the asset stays down — and whatever depended on it has to find another.
Maintenance, supply and operations each see that chain from their own end. The cost is paid in assets waiting for parts that were available elsewhere, and in unplanned downtime the condition data had been predicting all along.
An asset waiting for a part is a supply problem wearing a maintenance badge.
02How it plays out
An operator runs a mixed fleet across four depots. Next month’s schedule assumes thirty-eight of its forty assets will be available.
An illustrative sequence, not a customer account.
The signal
Vibration on one asset’s gearbox has been rising for three weeks — slowly enough that it has never crossed an alarm threshold. Separately, one depot has pushed back two inspections because a bay is out of action.
What it means
Trajectory Intelligence flags the gearbox as a sustained drift against how that asset normally behaves. Theralon then reads the rest of the chain: the replacement gearbox is in stock, but at a depot two hundred miles away; the nearest bay with the right tooling is the one already running behind; and two more assets of the same type are approaching the same service interval. The forecast for next month falls from thirty-eight available assets to thirty-four.
What is recommended
Move the gearbox now, schedule the replacement into the first free slot at the better-equipped depot, and swap one inspection between depots to absorb the lost bay. The recommendation states what each step returns in availability, and what doing nothing would cost.
What follows
Maintenance control accepts it. The gearbox is changed as planned work on a weekday, rather than as a recovery job after a failure in service.
None of the three teams involved was doing anything wrong. Each was looking at its own end of a chain that only made sense whole.
On your fleet
We'd show you next month's availability, honestly.
Terra reads condition, parts, bays and the schedule as one plan, so the assets that will not make it are seen while there is still time to order the part or move the work.
- Drift seen before it crosses an alarm
- Parts and bays matched to the work that is due
- Availability forward, asset by asset
A screen from Terra, on synthetic data.
03Where Theralon applies
- 01
From condition to plan
Telemetry and maintenance history turned into early warning of degradation — early enough to plan the work instead of reacting to the failure.
- 02
Parts for the work
Upcoming maintenance matched to parts availability across locations, so a job is never scheduled against stock that is not there.
- 03
Capacity to do it
Bays, tooling and skilled hours treated as constraints alongside the parts themselves.
- 04
Availability, forward
How many assets will be ready next week and next month, and the single dependencies that projection rests on.
- 05
Where the scarce part goes
When stock is short, the allocation that returns the most availability across the whole fleet.
04What changes
Assets waiting on parts held elsewhere
Parts sent where they return the most availability
Failures found in service
Degradation planned for
Availability reported
Availability projected
05Under the hood
Asset Intelligence reads early indicators of degradation from operational history, telemetry, maintenance records and environmental conditions. Trajectory Intelligence learns how each asset normally behaves and watches for sustained drift — the slow decline that never trips a static threshold. Every model in production carries a versioned model card: its intended use, known failure modes and retrain history.
Two questions
- When an asset starts drifting, does anything tell you before it crosses an alarm, and what it will take off the schedule?
- When a part is late or a bay is out, does anything tell you which assets stay down and what depended on them?
Terra does both. See it on your own operation.
Show us where the operation breaks down. We build around your data, your systems and how you actually operate, at whatever size the operation is. Then compare it with what you run today.
There's no cost while we work with you, for the foreseeable future. You see what the software does on your own operation before it costs you anything.
When it has shown its value there, we agree terms with you, sized to what you run, and nothing becomes a contract until you agree to it.