BMS / approved gateway
Vehicle energy evidence
OwnsSoC, usable energy, thermal/consumption context and freshness
Must not inferPrediction never overwrites BMS truth
AutoBuild your programPublic reference architecture
EV Journey & Charging
Keep vehicle energy truth, prediction and charging-network evidence visibly separate.
Bind every plan to the exact vehicle configuration, BMS observation, route, model, calibration and charger qualification used to produce it.
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-05
Journey intelligence
OwnsVersioned route-energy estimate, reserve and feasibility
Must not inferEstimate is conditional on declared assumptions
Operator/content sources
Charging evidence
OwnsConnector, power, access and source-reported status
Must not inferAvailability is not reservation or successful charge
APP-03
Cockpit and companion
OwnsComparison, user acceptance and transfer intent
Must not inferUI receipt does not activate navigation, reserve or charge
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
Bind vehicle
Resolve exact configuration, battery and current authoritative BMS evidence.
vehicle/config ID · BMS source · observation - 02
Predict routes
Calculate energy, arrival SoC and reserve under versioned assumptions.
model · calibration · weather/traffic/elevation basis - 03
Qualify charging
Filter connector, access, route reachability, freshness and partner availability.
charger source · observed time · exclusion reasons - 04
Compare and accept
Present feasible alternatives without collapsing prediction into truth.
plan/context revision · selected route · policy - 05
Transfer or activate
Record a scoped request with exact lineage and wait for downstream evidence.
idempotency · target device · activation receipt
Contract families
Interfaces that a production program must own.
Energy context
Vehicle configuration, BMS evidence, assumptions and calibration.
Plan
Alternatives, predicted energy, arrival/reserve and feasibility reasons.
Charger qualification
Connector, access, reachability, status source and freshness.
Continuity
Plan transfer, acceptance and downstream activation evidence.
Designed degradation
Failure states stay truthful and useful.
Stale/unavailable BMS
Withhold feasibility and arrival SoC rather than substitute a guessed state.
Charger status stale
Keep route relevance but label status stale and exclude from current-availability claims.
Partner unavailable
Do not imply reservation, payment or successful charging; offer alternate planning.
Plan/context revision changed
Reject acceptance/transfer and require a refreshed plan.
Security & privacy controls
Privilege follows the narrowest useful boundary.
- ✓Vehicle/configuration binding before prediction or transfer
- ✓Purpose-minimized BMS and trip context
- ✓Partner data isolated from vehicle/control credentials
- ✓Exact revision and idempotency on acceptance/activation
- ✓No payment or reservation outcome without authoritative partner receipt
Release evidence
A green demo is not a production acceptance case.
- 01Energy model calibration and route replay by vehicle/conditions
- 02Reserve and unreachable/incompatible charger tests
- 03BMS staleness and source-conflict behavior
- 04Cockpit moving-state and companion continuity validation
- 05Partner outage, price/status freshness and activation uncertainty
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 EV Journey & Charging reference into your program architecture.
Confirm target products, vehicle and cloud boundaries, source systems, contract versions, deployment, validation and lifecycle ownership.