Vehicle Connected Services Management › Vehicle Data Platform Operations

Vehicle Data Platform Operations

BC-3460.40 Level 2 Automotive & Mobility 8 providers 31 API surfaces

Operation of the vehicle data platform — ingestion, storage, sharing, and consent management — supporting first- and third-party use cases.

Vehicle Data Platform Operations (BC-3460.40) is a level-2 business capability under Vehicle Connected Services Management in the Automotive & Mobility model. The catalog holds 31 API surface(s) from 8 provider(s) that can perform some part of it. 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

Vehicle Data Ingestion and Storage Management BC-3460.40.10

Ingestion, normalisation, and storage of vehicle telemetry and event data at fleet scale.

no catalog coverage

Vehicle Data Sharing and API Management BC-3460.40.20

Provision of vehicle data APIs to internal teams, dealers, and external partners under data-sharing agreements.

no catalog coverage

Vehicle Data Privacy and Consent Management BC-3460.40.30

Management of customer consent, preferences, and privacy controls for vehicle-generated data.

no catalog coverage

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.

Developing 4 Usable, with meaningful gaps to close
Amazon IoT FleetWise#X Amz Target=IoTAutobahnControlPlane.AssociateVehicleFleet#X Amz Target=IoTAutobahnControlPlane.BatchCreateVehicle#X Amz Target=IoTAutobahnControlPlane.BatchUpdateVehicle#X Amz Target=IoTAutobahnControlPlane.CreateCampaign22 APIs52.8VolterasAccountsVehicle Telemetry2 APIs51.8GeotabRecords1 API40.5SmartcarVehicle Data1 API40.4
Thin 4 Limited public surface area
High MobilityFleet ClearanceVehicle Data2 APIs36.6TRONITYVehicle Data1 API33.3BMW ConnectedDriveVehicles1 API30.1OtonomoEU1 API30.0
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 Vehicle Data Platform Operations. 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 →