Transport Operations Management

BC-2420 Level 1 Transportation & Logistics 49 providers 87 API surfaces 11 rated strong or better

Multimodal execution of transport movements from pickup through line-haul, drayage, and last-mile delivery, including operational disruption response.

Transport Operations Management (BC-2420) is a level-1 business capability in the Transportation & Logistics model. The catalog holds 87 API surface(s) from 49 provider(s) that can perform some part of it, 11 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

Dispatch Management BC-2420.10

Assignment of loads, drivers, crews, and equipment to scheduled and ad-hoc transport moves.

16 providers, 21 API surfaces

Line-Haul Operations Management BC-2420.20

Long-distance movement of cargo between hubs, terminals, and gateways across modes.

1 provider, 1 API surface

Pickup and Drayage Operations Management BC-2420.30

First-mile pickups from shippers and short-haul drayage between terminals, yards, and inland points.

7 providers, 7 API surfaces

Last-Mile Delivery Operations Management BC-2420.40

Final-leg delivery to consignees including routing, execution, and proof-of-delivery.

21 providers, 33 API surfaces

Operational Disruption Management BC-2420.50

Detection of in-flight operational disruptions and orchestration of recovery actions.

no catalog coverage

Operational Performance Management BC-2420.60

Operational measurement of on-time performance, transit times, and service-level adherence.

1 provider, 2 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.

Exemplar 2 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 16 Limited public surface area
Emerging 4 Early or largely undocumented

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 Transport Operations 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 →