Ownership convenience
AutoBuild your programAI-04 · AI cockpit
Vehicle state and health queries
Ownership convenience
Program scope
Configured OEM program capability
Requires named OEM interfaces, configuration, acceptance evidence and commercial entitlement.
AI cockpit
Open solution →- Cockpit application
- Orchestration SaaS
- Tool SDK
- OEM integration
Product allocation
Delivered by named products—not an implied monolith.
The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.
AI Cockpit Orchestration Cloud
Ground conversational navigation, vehicle, EV, service and approved concierge journeys in versioned tools, permissions, moving-state policy, confirmation and trace—without giving a model direct vehicle control.
Open product →AI Cockpit Assistant
Present governed navigation, vehicle, EV, service and concierge journeys across moving/parked IVI, cluster, HUD and companion continuation using an interruptible deterministic state machine.
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.