AutoBuild your programSeparate software, maps and content, cloud usage, electronics, integration engineering, SaaS, managed operations and specialist data services—then align each line to scope, evidence, lifecycle and one authoritative commercial meter.
A program can select one or many forms. Keeping them separate makes rights, volume, acceptance, updates, support and exit testable.
Per vehicle, module, term, trim and territory for navigation, EV, connected, eHorizon/ADAS, assistant or fleet software.
By territory, layer, format, update cadence, deployment and permitted use for embedded or cloud content.
By calls, vehicles or assets, MAU, transactions, map loads, environments or committed capacity.
Per selected device or BOM, with NRE, tooling, test, provisioning, warranty and recurring connectivity/cloud separated.
Milestone or work-package engineering across HMI, vehicle, platform, cloud, apps, content, devices and validation.
By tenant, users, assets, enabled features, transactions or committed platform capacity.
By coverage hours, service tier, staffing, fleet or device population, release load and operational scope.
Project, corridor, survey, dataset, analysis or outcome work package with accepted source and delivery evidence.
The checklist follows the product through supply chain, scope, enablement, lifecycle, security, assurance, data exit and financial mechanics.
Each topic becomes named assumptions, decisions, gaps and owners—not an unstructured feature list.
vehicle lines and trims · markets and territories · SOP and model years · volumes and adoption · target customer outcomes · mandatory, differentiating and subscription-ready features
data, SDK, app, cloud, device or full program · OEM and Mappls ownership · selected Tier 1s and platform vendors · build-versus-configure choices · IP and source expectations · operations and acceptance authority
OS, SoC and head unit · IVI, cluster, HUD and passenger displays · input, voice and audio · startup and performance budgets · UI, localization and accessibility ownership · moving-state and distraction rules
embedded modem, tethering and projection · carrier and roaming · offline territories and journeys · data budget and update windows · store-forward and recovery · service-loss customer behavior
territory and content depth · route and vehicle profiles · traffic, ETA, search and POI · lanes, junctions, tolls and alerts · private, truck and two-wheeler routing · representative proof routes
TCU, identity and provisioning · vehicle signals and digital twin · remote-service authority · ownership transfer and consent · alerts, diagnostics and applications · support and lifecycle operations
battery and vehicle signals · model calibration and reserve policy · range and arrival targets · charger sources and compatibility · cluster, cockpit and app behavior · reservation, payment and fleet analytics
functions, item and ODD · corridors and content coverage · HD/eHorizon format and consumers · localization, sensors and controllers · safety allocation and degradation · simulation, replay and validation evidence
vehicle, driver and rider identities · orders, dispatch and optimization · customer ETA and route adherence · video, workforce and proof · partner and enterprise integrations · operations KPIs and support
region, tenancy and deployment · identity and entitlement · consent, residency and retention · analytics and partner feeds · backup, export and disaster recovery · exit and portability
OEM CSMS and SUMS · threat analysis and trust boundaries · secure boot, OTA and keys · ASPICE, functional safety and SOTIF · IATF, PPAP and homologation · vulnerability and incident management
development and test fleets · environments and promotion · map, app, firmware and device releases · field issue and correction process · LTS, warranty and support hours · obsolescence, migration and end-of-life
license and usage metric · minimums and committed volumes · integration NRE and acceptance · hardware forecast and MOQ · capacity, SLA and remedies · data rights and price protection
Evaluation proves a coherent journey and its degraded behavior; it does not silently promote simulation into field acceptance.
Resolve an ambiguous Indian address, landmark and Mappls PIN; compare suggestions and entrances.
Failure variantNo confident match or entrance remains explicit, evidence-bearing and user-confirmable before route activation.
3 products · 2 interfacesTransfer the journey to vehicle and establish one route revision across IVI, cluster and companion.
Failure variantDisconnected or incompatible surfaces retain last qualified state without divergence.
4 products · 3 interfacesCompare fastest and energy-efficient routes, traffic, tolls, elevation, arrival SoC and reachable area.
Failure variantStale traffic or invalid energy signals are excluded, disclosed and cannot silently support a current prediction.
3 products · 3 interfacesAdd a compatible charging stop and replan after deviation or qualified charger change.
Failure variantStale, incompatible or unavailable charger evidence cannot create a physical availability claim.
3 products · 2 interfacesShow junction, lane and sign guidance plus route-aware traffic, speed, curve and safety context.
Failure variantUnknown localization, content or probable path holds unsupported presentation.
4 products · 3 interfacesShare trip, evaluate a geofence or status alert and review the post-drive summary.
Failure variantConsent withdrawal, sequence gaps or offline state remain distinct and auditable.
4 products · 3 interfacesInspect digital twin, versions, route trace, issue workflow, health and analytics.
Failure variantObserved, calculated, predicted and externally accepted states remain separate.
5 products · 3 interfacesFeed the route into eHorizon/HD tooling and inspect attributes, versions, coverage and freshness.
Failure variantOutside ODD, stale content or invalid localization produces explicit safe degradation.
3 products · 3 interfacesThese are the minimum bridge from workshop to technical proposal, SOW, commercial schedule and acceptance plan.
A price, schedule, public example or demonstration is not vehicle, laboratory, regulatory, manufacturing, production-operations or OEM acceptance. The accountable program gate still decides.
Bring program, platform, territory, volume and lifecycle assumptions. Leave with comparable scope, evidence, commercial meters and responsibilities.