Current/historical vehicle state
AutoBuild your programCON-03 · Connected vehicle
Vehicle digital twin
Current/historical vehicle state
Program scope
Current, configured by program
Requires named OEM interfaces, configuration, acceptance evidence and commercial entitlement.
Connected vehicle
Open solution →- Connected-vehicle SaaS
- Owner application
- Edge agent
- Device + cloud program
Product allocation
Delivered by named products—not an implied monolith.
The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.
Connected Vehicle Cloud
Securely connect vehicle identity, telemetry, trips, alerts, approved remote services, consent and lifecycle operations—then expose a consistent state model to owner, fleet, EV, service and analytics products.
Open product →OEM Owner Companion
Bring vehicle status, planning and send-to-car, approved remote journeys, trip history, security, EV charging, service, roadside and privacy controls into one native ownership experience.
Open product →Connectivity & Telemetry Agent
Manage link policy, telemetry normalization, priority buffering, batching, retry, acknowledgement, cost/power behavior and secure upload across TCU and edge products.
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.