Annual-report wording on embedded navigation with major OEMs; not a global navigation share.
Judge the suite by the journeys it can demonstrate.
Public customer and product pages show portfolio presence; they do not imply identical features across every vehicle. Each card links to its source so scope and wording remain inspectable.
Publicly referenced programs across navigation, EV and connected services.
Customer names and descriptions below are intentionally conservative. Confirm current approval before reusing logos, screenshots or broader scope in a proposal.
Mahindra XUV700
Publicly referenced embedded navigation and connected-cockpit program example.
MG Motor
Public customer material describes embedded connected navigation with India-depth map, guidance, voice and alert capabilities.
Tata Safari
Public solution page describes cluster route display, lane and junction guidance, live context, bilingual voice and hybrid operation.
Tata Harrier.ev
Public page presents embedded navigation, spider range, chargers, energy routing, arrival SoC and charge-stop planning.
Maruti Suzuki Connect
Public material describes vehicle location, geofence, trip history, sharing and smartwatch interactions.
BYD
Public automotive customer page presents Mappls navigation capabilities for BYD vehicles in India.
Scale claims remain dated and distinct.
Annual attachment, cumulative vehicles, API count, road network, places, probes and alerts describe different things. Never merge them into one number.
Public API portfolio breadth; product taxonomy and exact count can change.
Territory, hardware, map coverage, partner feeds, software release and entitlement still require confirmation.
One controlled scenario. The whole suite in context.
A coherent India EV demonstration reveals more than a disconnected feature menu.
Plan
Use an ambiguous Indian address, landmark and Mappls PIN; compare search suggestions and arrival entrances.
Continue
Send the route to the vehicle and establish route state across IVI, cluster and companion.
Optimize
Compare fastest and energy-efficient routes, traffic, tolls, elevation, arrival SoC and reachable area.
Charge
Add a compatible charging stop, inspect route relevance and replan after a simulated change.
Drive
Demonstrate junction, lane and sign guidance plus route-aware traffic, speed, curve and safety context.
Connect
Share the trip, trigger a configured geofence or status alert and review the post-drive summary.
Operate
Open the digital twin, map and software versions, route trace, issue workflow and analytics.
Predict
For an ADAS scope, inspect eHorizon or HD attributes, version, coverage and freshness evidence.
Credibility is a product feature.
Public language should communicate strength without hiding dependency.
“Maps are always accurate”
PreferOperate a versioned content lifecycle with program-defined coverage, freshness, correction and quality metrics.
“Autonomous-driving solution”
PreferHD-map and eHorizon components support specified functions under the OEM safety architecture and ODD.
“Charger data is real time”
PreferStatus is displayed when supplied by an entitled partner feed, with source and freshness behavior defined.
“AI controls the car”
PreferThe assistant invokes OEM-approved services under permissions, vehicle-state rules, confirmation and audit.
“Everything, everywhere”
PreferProvide a territory, platform and vehicle-specific capability and entitlement matrix.
“Replace every Tier 1”
PreferReduce fragmentation across data, software, cloud and selected electronics while integrating with the chosen ecosystem.
Bring us the vehicle. Leave with the program shape.
Choose the surfaces, modules, deployment and lifecycle that fit your next RFQ. We will turn it into a focused discovery brief.