Plant, port, campus and special routing
AutoBuild your programDATA-20 · Map data & live location
Private roads, yards and customer layers
Plant, port, campus and special routing
Program scope
Program-specific capability
Requires named OEM interfaces, configuration, acceptance evidence and commercial entitlement.
Map data & live location
Open solution →- Data license
- Cloud API
- Device content
- Managed map operations
Product allocation
Delivered by named products—not an implied monolith.
The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.
Map & Content Cloud
Manage territory, layers, entitlement, quality, compatibility, package lineage, release notes, feedback, delivery, activation and rollback across vehicle programs and model years.
Open product →Geoanalytics & Command Center
Compose OEM-private layers, vehicle and asset state, tasks, incidents, geofences, video, field teams, catchments and analytics into role-specific operational workspaces.
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.