Regulated/aftermarket tracking
AutoBuild your programEDGE-02 · Automotive electronics
AIS-140 / fleet tracker
Regulated/aftermarket tracking
Program scope
Current or composable by program
Composed from the wider Mappls platform and confirmed in the selected solution scope.
Automotive electronics
Open solution →- Hardware system
- Embedded firmware
- Device cloud
- Application integration
Product allocation
Delivered by named products—not an implied monolith.
The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.
AIS-140 / Fleet Tracker
Provide location, ignition, movement, event, geofence, history and device-health inputs for regulated or operational fleets with explicit product and homologation scope.
Open product →Location Runtime
Fuse GNSS and approved dead-reckoning inputs, distinguish raw and matched position, expose quality, and recover through tunnels, urban canyons, flyover overlap and weak-signal conditions.
Open product →Connectivity & Telemetry Agent
Manage link policy, telemetry normalization, priority buffering, batching, retry, acknowledgement, cost/power behavior and secure upload across TCU and edge products.
Open product →Device Lifecycle & OTA Agent
Operate identity bootstrap, inventory, health, configuration, signed software and firmware rollout, recovery, diagnostics, replacement and decommission across Mappls Auto edge products.
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.