Boot & trust
Device identity, secure startup where applicable, configuration provenance and verified application/content loading.
AutoBuild your programDeveloper docs · embedded & edge
Design the device and its cloud as one product.
This reference covers the public integration shape for embedded navigation, firmware and selected hardware families. Exact electronics, certifications and production readiness are confirmed per product and OEM program.
Embedded runtime
Eight responsibilities inside a resilient vehicle baseline.
The runtime separates signal, location, navigation, content, connectivity and lifecycle concerns so each can fail, update and be diagnosed predictably.
Vehicle abstraction
Unit, rate, validity, timeout and ownership adapters for approved CAN, service, GNSS, energy and diagnostic signals.
Location runtime
GNSS, dead reckoning inputs, map matching, tunnel/urban-canyon recovery and confidence propagation.
Navigation runtime
Map database, search, routing, guidance, route state, voice and multiscreen output interfaces.
Connectivity manager
Embedded modem or tether state, buffering, retry policy, cost controls and connected/offline capability negotiation.
Content manager
Territory manifest, storage budget, release compatibility, resumable update, integrity, activation and rollback.
Telemetry & diagnostics
Health, versions, failures, route quality and update evidence designed for privacy-safe support.
Lifecycle agent
Provisioning, entitlement, configuration, application/firmware update, recovery and decommissioning.
Reference flow
Vehicle to edge to cloud to experience.
Interface ownership remains explicit even when Mappls supplies several layers.
Signals & controls
GNSS · speed · ignition · gear · SoC · energy · DTC · approved actions
Trusted runtime
Identity · buffer · location · map · guidance · firmware · diagnostics
Services & operations
Digital twin · content · route · analytics · command · OTA · support
OEM surfaces
IVI · cluster · HUD · companion · fleet · dealer · command center
Hardware families
Selected edge systems with recurring software attachment.
These are capability families, not a universal line-fit catalogue. Product, vehicle, country, interface and certification scope must be verified.
◉
Line-fit TCU
GNSS and communications bridge to vehicle signals and the connected vehicle cloud.
Program / product dependent▰
Fleet / AIS-140 tracker
Regulated or operational tracking with ignition, events, geofences and history.
Program / product dependent◉
Video telematics device
Road or cabin video, local event buffering, retrieval and map/telemetry correlation.
Program / product dependent▰
Navitainment system
Display, navigation and connected content as a coordinated software-hardware product.
Program / product dependent◉
Two-wheeler cluster / HUD
Compact, glanceable navigation and approved communication or vehicle context.
Program / product dependent▰
Rider accessory
Program-selected navigation-adjacent or safety hardware with app and cloud linkage.
Program / product dependentHardware design schedule
What the RFQ needs to pin down.
A credible device program separates assumptions from evidence and assigns every production responsibility.
Electrical
Power states, transients, vehicle networks, wake and sleep, connectors, GNSS/RF and installation.
Compute
SoC/MCU, memory, storage, video, accelerators, operating system and performance headroom.
Security
Identity, keys, secure boot, signed firmware, debug policy, rollback and vulnerability response.
Environment
Temperature, vibration, ingress, EMC, RF, thermal, power and vehicle mounting.
Manufacturing
Design validation, production test, traceability, PPAP as applicable, change and obsolescence.
Field lifecycle
Provisioning, connectivity, OTA, diagnostics, service tooling, warranty and decommissioning.
Assurance boundary
Do not infer blanket IATF, ISO 26262, ISO/SAE 21434, AIS, ARAI, TEC, MTCTE, EMC or environmental compliance from a hardware-family label. The selected product receives a product- and site-specific compliance matrix.
OEM program workshop
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.