Maneuver clarity
AutoBuild your programNAV-15 · Navigation
Lane, junction and sign guidance
Maneuver clarity
Program scope
Current, configured by program
Requires named OEM interfaces, configuration, acceptance evidence and commercial entitlement.
Navigation
Open solution →- Turnkey embedded application
- Navigation SDK
- Device runtime
- Connected 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.
Embedded Navigation
Combine India-aware search, hybrid routing and guidance, traffic, safety, lanes, junctions, local language, route profiles and multiscreen outputs in an OEM-controlled in-vehicle experience.
Open product →Navigation Runtime
Provide device map access, search, routing, guidance, route state, voice and structured display outputs through stable platform-independent contracts.
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.