Fleet maintenance covers ships, aircraft and rolling stock, and all six providers are trucks

Fleet maintenance covers ships, aircraft and rolling stock, and all six providers are trucks

Fleet Maintenance Management (BC-2430.20) is defined as preventive, corrective and heavy maintenance of vehicles, vessels, aircraft and rolling stock. The catalog maps 21 API surfaces from 6 providers to it. Every one of the six works on road vehicles. None of them is rated strong.

The capability sits under Fleet & Mobile Asset Management in the Transportation & Logistics model, which comes from the Turbo EA capability model under CC BY 4.0. Capabilities themselves are not scored; the providers that land on them are.

The six providers

Provider Kin Score Band Agent Readiness APIs What lands here
Decisiv 52.2 developing 49.0 agent-native 10 Cases, case line items, parts, technician stories
Automile 45.9 developing 28.2 agent-aware 4 Vehicle inspections, defect comments
Lytx 40.8 developing 48.0 agent-ready 2 DVIR (DriveCam), maintenance records (GO9)
Revvo 36.0 thin 23.9 agent-aware 1 Tire operations
Ryder System 35.4 thin 17.9 agent-aware 1 Service history
Samsara 31.8 thin 18.6 agent-aware 3 Defects, DVIRs, maintenance

Decisiv contributes nearly half the surface, 10 of 21, and its tags read like a service shop’s workflow: a case, its line items, the parts on each line, and the technician’s story. That is the shape of corrective maintenance, and it is the only provider here that models it in that much detail.

Two things the table shows

Inspection is the common denominator. Automile, Lytx and Samsara all land through driver vehicle inspection reports and defects. The pre-trip inspection is the part of fleet maintenance that regulation forces into software, so it is the part that has APIs.

The telematics leader is last. Samsara is the most recognizable name in the list and has the lowest Kin Score at 31.8. Its maintenance surface is three tag groups. Lytx, a smaller video telematics company, scores 9 points higher and posts more than double Samsara’s Agent Readiness, 48.0 to 18.6.

The empty subcapabilities

The capability breaks into four children, and every one of them has 0 providers and 0 APIs:

  • Preventive Maintenance Scheduling
  • Corrective Maintenance Execution
  • Mandatory Inspection Compliance, which includes airworthiness and seaworthiness directives
  • Heavy Maintenance and Overhaul, which includes dry-docking and heavy checks

So the six providers map to the parent only, not to any of its parts, and nothing in the catalog lands on the aircraft, vessel or rail side of the definition. Even in rail, where Cedarai and Railinc publish railcar data, nothing reaches this capability.

Takeaway

If you maintain trucks, start with Decisiv for service events and Lytx or Samsara for inspections. If you maintain aircraft, ships or railcars, this capability has nothing for you yet. For the prediction side of the same problem, see the Predictive Maintenance use case.

← BNSF's Trains API says up to 25 trains and its schema accepts 300
HERE vs Entur, sixty points of access clarity against forty-five of governance →