Interactive product preview

Make range explainable—and the charging plan actionable.

Explore a synthetic EV journey that keeps BMS-authoritative SoC separate from prediction, compares route energy, qualifies compatible chargers, preserves reserve and creates an explicit simulated send-to-vehicle request.

EV
EV Journey StudioEnergy planning · synthetic reference
Qualified context
BMS state of charge Authoritative58%BMS via approved vehicle gateway · current
Predicted usable range Mappls prediction171 kmAbove 12% reserve · 198 Wh/km
Destination arrival With selected charge31.5%20 points above reserve
Prediction confidencehigh · 84%Hot-weather and traffic inputs are synthetic; charger state is source-qualified
CCS274 kWh usableCalibration matched
Loading Mappls map
Reachable above
12% reserve
GURUGRAMJAIPURNH 48 · SYNTHETIC
Selected energy routeAlternativeQualified charge
Verified reference plan readyConfiguration aurora-ev-74-ccs2-my27Plan r1BMS truth ≠ Mappls prediction
01

Truth and prediction stay separate.

BMS SoC retains its source and observation time; range, dwell and arrival SoC are explicitly qualified predictions.

02

Charging is a compatibility decision.

Reachability, connector, power, status source and freshness remain visible, including why a charger was excluded.

03

Transfer is not activation.

A send request never implies vehicle receipt, navigation activation, reservation, payment or a physical-system change.

One qualified EV plan—adapted for journey cloud, vehicle and mobile.

The responsive lab, native companion clients and Android Automotive cockpit share vehicle, configuration, calibration, route, plan, charger and policy identity without collapsing source authority.

EV Journey + Cockpit/Companion

Calibrate this workflow for your vehicle program.

Scope the EV program →Review the integration blueprint ↗