CPO / device / approved partner adapters
Charging source evidence
OwnsSource observation, clock, schema and status
Must not inferReceipt or discovery is not physical availability, reservation or successful charge
AutoBuild your programPublic reference architecture
Charging Intelligence Operations
Route-aware charging evidence from source-qualified asset state to explainable network action.
Keep partner observations, compatible route coverage, candidate predictions and field-work authority distinct while connecting each network decision to the journeys it affects.
Authority by layer
Know which component owns the state—and what it must never infer.
Every layer exposes an authoritative responsibility and an explicit non-authority boundary.
SAAS-11 registry / governed aggregates
Asset, rights and demand
OwnsConnector compatibility, source rights, freshness and consent-safe route demand
Must not inferStale/conflicting evidence cannot become current state
Mappls route graph / analysis services
Coverage and suitability
OwnsVersioned coverage, impact, factors, exclusions and score sensitivity
Must not inferPrediction cannot approve land, grid, site or investment
SAAS-11 / APP-06 / partner systems
Operations and field workflow
OwnsPriority, revision-bound intent and authoritative downstream receipt
Must not inferUI intent cannot dispatch a crew, repair an asset or close production work
End-to-end operating flow
State advances through evidence—not optimistic UI.
Each transition names both the action and the identity or version evidence that makes it reproducible.
- 01
Qualify sources
Resolve asset, connector, operator, rights, source time, freshness and conflicts.
asset/source IDs · event/receipt time · schema · rights - 02
Calculate coverage
Bind compatible current assets to route-demand aggregates and a declared detour/reliability policy.
road graph · demand aggregate · denominator · fingerprint - 03
Prioritize impact
Rank current outages and gaps by route demand, compatibility, detour and service policy.
priority basis · threshold · picture revision - 04
Evaluate candidates
Apply versioned factors, weights, mandatory exclusions and sensitivity.
model/policy · factors · exclusions · score range - 05
Prepare and reconcile
Create expiring work intent and await authoritative partner/field evidence.
role/right · expected revision · idempotency · downstream receipt
Contract families
Interfaces that a production program must own.
Asset evidence
Charger/EVSE/connector, source clocks, status, quality, freshness and conflict.
Demand and coverage
Aggregate definition, compatibility, route/drive-time basis, denominator and gap.
Candidate evaluation
Factors, weights, exclusions, sensitivity, model and human decision boundary.
Operations
Priority, expected revision, work intent, partner/field receipt, proof and reconciliation.
Designed degradation
Failure states stay truthful and useful.
Partner status stale
Retain source history and route relevance, but withhold current availability/outage action.
Operator/device conflict
Preserve both observations and keep the asset unresolved and non-actionable.
Demand or route basis unavailable
Remove demand-based ranking or use only an explicitly versioned fallback basis.
Rights/capacity unavailable
Keep the priority inspectable but reject work intent without dispatch or ETA.
Security & privacy controls
Privilege follows the narrowest useful boundary.
- ✓Tenant, territory, source-right, role and purpose policy
- ✓Consent-safe route-demand aggregation and retention
- ✓CPO control/transaction credentials isolated from analytics and clients
- ✓Exact picture revision and idempotency for operational intent
- ✓No reservation, payment, dispatch, site approval or production outcome without authoritative receipt
Release evidence
A green demo is not a production acceptance case.
- 01Freshness, duplicate, late and source-conflict contract tests
- 02Compatible route coverage and privacy-threshold golden corridors
- 03Candidate weights, exclusions, sensitivity and reproducibility
- 04Role, stale revision and field-capacity fail-closed behavior
- 05Partner outage, downstream reconciliation and accessible non-map workflow
Independently scopeable products
Compose the system without collapsing product ownership.
Each product can be bought and operated independently while sharing identity, context and lifecycle contracts.
OEM program workshop
Turn the Charging Intelligence Operations reference into your program architecture.
Confirm target products, vehicle and cloud boundaries, source systems, contract versions, deployment, validation and lifecycle ownership.