Partner-enabled charge transaction
AutoBuild your programEV-14 · EV intelligence
Reservation/payment/roaming
Partner-enabled charge transaction
Program scope
Program-specific capability
Confirm current product, platform, territory, dependencies, evidence and commercial scope before representing availability.
EV intelligence
Open solution →- EV journey SaaS
- Cockpit and companion application
- Typed API
- Calibration service
Product allocation
Delivered by named products—not an implied monolith.
The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.
EV Journey & Charging Cloud
Fuse BMS-authoritative context, vehicle calibration, route alternatives, elevation, traffic, environment and compatible charging into revisioned, confidence-aware EV journey plans.
Open product →EV Cockpit & Companion
Connect BMS-authoritative vehicle state with route, terrain, traffic, environment and charging intelligence across IVI, cluster, HUD and mobile.
Open product →Discovery contract
Six questions turn catalogue presence into an engineering scope.
Answers become requirements, interface contracts, degraded behavior and acceptance evidence.
Vehicle & territory
Which vehicle lines, trims, territories, model years and user roles need this capability?
Surface & platform
Which cockpit, mobile, web, cloud or device surfaces own presentation and interaction?
Authority & inputs
Which source is authoritative, how is freshness expressed and what happens when input is missing or invalid?
Connectivity & degradation
What must work online, hybrid or offline, and which behavior fails closed?
Evidence & acceptance
Which functional, performance, UX, safety, security and target tests determine acceptance?
Lifecycle & commercials
Which entitlement, update, support, retention and long-term branch terms apply?
OEM program workshop
Turn this capability into a program requirement.
Define the vehicle, territory, product allocation, interfaces, evidence and lifecycle behind the capability.