Standard eHorizon integration
AutoBuild your programADAS-02 · ADAS, eHorizon & HD maps
ADASIS v2/v3 interfaces
Standard eHorizon integration
Program scope
Current, configured by program
Requires named OEM interfaces, configuration, acceptance evidence and commercial entitlement.
ADAS, eHorizon & HD maps
Open solution →- Map data
- eHorizon runtime
- Cloud service
- Engineering and validation 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.
eHorizon & HD Map Cloud
Manage ADAS-grade corridor content, probable-path preparation, profile generation, freshness, coverage, quality evidence and vehicle distribution for approved eHorizon consumers.
Open product →eHorizon & ADAS Map Runtime
Resolve probable path, map position, profile horizon and agreed ADAS attributes into versioned bounded outputs for approved chassis, powertrain and assistance consumers.
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.