Day-to-day operation of charge points including monitoring, session lifecycle, and firmware control over OCPP.
Charge Point Operations (BC-3480.20) is a level-2 business capability under EV Charging Network Operations Management in the Automotive & Mobility model. The catalog holds 6 API surface(s) from 4 provider(s) that can perform some part of it, 1 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
Charge Point Monitoring BC-3480.20.10
Real-time monitoring of charge-point health, availability, and alarm states.
no catalog coverage
Charge Session Lifecycle Management BC-3480.20.20
Management of the charge-session lifecycle from authorisation through energy delivery and termination.
no catalog coverage
Charger Firmware and Configuration Management BC-3480.20.30
Management of charger firmware versions, configuration profiles, and remote updates.
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.
Strong
1
Solid coverage with minor gaps
Developing
1
Usable, with meaningful gaps to close
Thin
2
Limited public surface area
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 Charge Point 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 →