versioned test definition and acceptance threshold
AutoBuild your programVER-05 · OEM verification domain
EV journey and charging
Prove vehicle-aware energy decisions while keeping BMS truth, prediction, charger evidence and physical charging separate.
Scenario matrix
Ten paths—including ambiguity, loss, replay and recovery.
The vehicle program turns each scenario into versioned test cases with routes, fixtures, conditions, thresholds and accountable verdicts.
- 01
missing or invalid SoC and energy signals
- 02
climate, elevation and traffic sensitivity
- 03
vehicle and battery degradation
- 04
charger incompatibility and exclusion
- 05
unavailable or stale charger evidence
- 06
skipped charge stop
- 07
route deviation and dynamic replanning
- 08
arrival SoC and reserve policy
- 09
charging-plan reproducibility
- 10
handoff to cockpit and companion
Product allocation
Every participant retains its own authority and release evidence.
Green results in one participant do not promote another product—or a physical outcome—to accepted.
Interface allocation
Verify behavior at the handoff, not only inside the component.
Open each contract to freeze authority, compatibility, degradation and prohibited outcome claims.
IF-01 · Vehicle
Vehicle signal observation
Invalid, stale, out-of-range or unavailable signals remain explicit and cannot be replaced with a plausible default.
Open contract →IF-06 · CockpitRoute plan, activation and guidance state
Position ambiguity, stale traffic, incompatible content or secondary-display loss preserve route lineage and expose degradation.
Open contract →IF-08 · CloudEV vehicle context, prediction and journey plan
Missing or stale authoritative inputs prevent feasibility claims; incompatible or unreachable chargers remain excluded with reasons.
Open contract →IF-17 · Mobile/webNotification, deep link and cross-surface continuation
Expired, revoked, unknown-version or unentitled links fail non-destructively; delivery gaps do not mutate source state.
Open contract →Evidence package
A verdict stays reproducible, attributable and reviewable.
These fields travel together so a screenshot or summary cannot become disconnected from its exact conditions.
fixture, route, data and environment provenance
raw result plus summarized verdict
defect, deviation and retest disposition
product, schema, content, policy and configuration versions
independent review and accountable approval
target, laboratory, vehicle or operational evidence where required
OEM program workshop
Plan ev journey and charging evidence for the exact vehicle.
Allocate scenarios, targets, versions, fixtures, thresholds, review and acceptance before declaring readiness.