MapplsAutoBuild your program
CON-20 · Connected vehicle

OTA/device management

Configuration and lifecycle

Scope this capability →Back to catalogue ↗
Program scope

Program-specific capability

Confirm current product, platform, territory, dependencies, evidence and commercial scope before representing availability.

Primary use

Configuration and lifecycle

Delivery choices
  • Connected-vehicle SaaS
  • Owner application
  • Edge agent
  • Device + cloud program
Product allocation

Delivered by named products—not an implied monolith.

The final RFQ allocates authority, interfaces, evidence and commercial scope across the selected products.

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 →

Connected Vehicle Cloud

Securely connect vehicle identity, telemetry, trips, alerts, approved remote services, consent and lifecycle operations—then expose a consistent state model to owner, fleet, EV, service and analytics products.

Open product →

Line-fit TCU

Combine cellular/eSIM, GNSS, secure compute, approved vehicle interfaces, priority buffering, diagnostics and recoverable OTA in a traceable line-fit vehicle-cloud bridge.

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.

Build your program Open developer hub ↗