The BMS remains authoritative for vehicle state; EV Journey Cloud owns versioned predictions and plans; charger sources own observations.
AutoBuild your programIF-08 · Cloud interface
EV vehicle context, prediction and journey plan
Bind BMS-approved truth, vehicle calibration, route, environment, charger qualification, prediction confidence and plan revision.
Authority model
Name the source—and name what it cannot prove.
The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.
Missing or stale authoritative inputs prevent feasibility claims; incompatible or unreachable chargers remain excluded with reasons.
A predicted range, arrival SoC or charging plan does not imply charger availability, reservation, payment or successful charging.
Product allocation
Producer and consumer responsibilities are explicit.
A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.
Transport allocation
Choose transport after semantics are fixed.
The program can select one or more transports without changing the source authority or failure contract.
Vehicle-signal adapterTyped journey APIPlan and charger event stream
Compatibility vector
- schema or ABI version
- producer release
- consumer release
- policy and entitlement revision
- content/configuration revision
- territory/platform profile
Acceptance evidence
- contract compatibility
- nominal and negative scenarios
- ordering, replay and idempotency
- latency, capacity and resource bounds
- security, privacy and role enforcement
- offline, recovery and rollback
- target or operational acceptance
OEM program workshop
Freeze the EV vehicle context, prediction and journey plan contract before integration.
Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.