Fleet & Mobile Asset Management

BC-2430 Level 1 Transportation & Logistics 21 providers 113 API surfaces 2 rated strong or better

Provisioning, maintenance, utilisation, and disposal of vehicles, vessels, aircraft, rolling stock, and pooled equipment such as containers, trailers, and ULDs.

Fleet & Mobile Asset Management (BC-2430) is a level-1 business capability in the Transportation & Logistics model. The catalog holds 113 API surface(s) from 21 provider(s) that can perform some part of it, 2 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Fleet Acquisition and Disposal Management BC-2430.10

Specification, acquisition, leasing, chartering, and end-of-life disposal of mobile assets.

no catalog coverage

Fleet Maintenance Management BC-2430.20

Preventive, corrective, and heavy maintenance of vehicles, vessels, aircraft, and rolling stock.

6 providers, 21 API surfaces

Equipment Pool Management BC-2430.30

Management of pooled containers, trailers, chassis, and ULDs across depots, customers, and partners.

2 providers, 2 API surfaces

Fleet Telematics and Monitoring BC-2430.40

Continuous monitoring of asset position, condition, and operator behaviour to inform maintenance and operations.

13 providers, 51 API surfaces

Fleet Compliance and Certification Management BC-2430.50

Registration, certification, and emissions compliance of fleet assets with regulators and class societies.

1 provider, 3 API surfaces

Fleet Utilisation and Performance Management BC-2430.60

Measurement of asset utilisation, turn-times, and total cost of ownership to drive fleet decisions.

4 providers, 7 API surfaces

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 2 Solid coverage with minor gaps
BringgVehicles1 API59.6Track-PODVehicle1 API56.1
Developing 12 Usable, with meaningful gaps to close
tread.ioEquipmentTelematics2 APIs52.2DNVCertificatesSurveysVessels3 APIs51.6DecisivCase ActionsCase Line Item PartsCase Line ItemsCase Line Items Technician Stories18 APIs49.5OneRailOwn Fleet Vehicle1 API47.8LocoNavAlertsVehicles / TelematicsVideo Telematics VT / Live StreamVideo Telematics VT / Videos4 APIs47.2QargoAPI / Resource1 API47.1AMCS GroupApiGpsDataExternalApiGpsTrailExportServiceAssetExternalVehicle9 APIs46.4AutomileResourceOwnerGeofenceResourceOwnerGeofence2ResourceOwnerGeofence3ResourceOwnerIMEIEvent20 APIs43.7DottVehicles1 API43.4Ryder SystemFleetService History2 APIs42.0Maven MachinesLocationsTrailersVehiclesreports4 APIs41.9LytxDVIR (DriveCam)DeviceStatusInfo (GO9)Diagnostics (GO9)ECM11 APIs40.4
Thin 6 Limited public surface area
FleetbaseFleetsVehicles2 APIs38.1LocusVehicle1 API36.0RevvoDeviceEventFleetTire Operation5 APIs36.0SamsaraAempAssetsDefectsDvirs22 APIs34.9WorkWaveGPSVehicles2 APIs33.8LimeFree Bike Status1 API33.0
Emerging 1 Early or largely undocumented
FleetMonFleet TrackerHistorical Track API2 APIs21.6

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Fleet & Mobile Asset Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →