Autonomous safety
A

Give the vehicle a governed view of the road beyond its sensors.

Use route-ahead map attributes to extend awareness beyond line of sight and support predictive driver-assistance, energy and vehicle-control functions within the OEM safety architecture.

Compose the exact experience.

Capability labels below describe public or configurable scope. The status note makes program dependence visible before a technical commitment.

01Current + configured

Electronic horizon

Probable path and structured road-ahead attributes for an approved consumer ECU or function.

02Coverage-dependent

Speed and sign context

Map inputs for display, warnings, ISA and traffic-sign assistance as allocated by program.

03Coverage-dependent

Curvature and slope

Preview for curve-speed warning, lighting, predictive cruise, gearing and energy management.

04Coverage-dependent

Road and lane topology

Road type, lane structure, transitions, tunnels, tolls and special structures.

05Feed-dependent

Live hazard context

Incident, queue, work-zone and closure information where an entitled live feed exists.

06Corridor/program-specific

HD lane model

High-precision lane geometry, connectivity, merges, splits and selected attributes.

07Corridor/program-specific

Localization landmarks

Surveyed road furniture and map objects usable by approved localization or perception systems.

08Professional service

Acquisition and processing

LiDAR, camera and high-accuracy GNSS collection with extraction, conflation and validation.

09Publicly positioned

ADASIS and NDS

Industry map and eHorizon interface families, profile and release validated per integration.

10Program-specific

Simulation assets

Custom map and scenario assets for virtual validation and regression workflows.

One capability. Multiple buyers.

ADAS teams

Route-ahead context and a versioned map interface inside the function architecture.

Chassis and powertrain

Predictive curve, slope and road-state inputs for comfort and efficiency.

Validation

Traceable corridor, version, freshness and scenario evidence.

Designed into the vehicle program.

  • ADASIS v2/v3 profiles
  • NDS and OEM-agreed formats
  • ADAS domain controllers
  • Cloud-to-vehicle update services
  • High-accuracy localization
  • Simulation and replay toolchains

What responsible integration makes explicit.

01

ODD, corridor coverage, freshness and failure behavior are explicitly declared.

02

Responsibility is allocated across Mappls, OEM, Tier 1, sensor and cloud providers.

03

Safety use may require ISO 26262, SOTIF and cybersecurity evidence.

04

Safety-relevant content needs provenance, anomaly handling and rollback.

OEM program workshop

Turn autonomous safety into an OEM-ready scope.

Capture the vehicle, territory, surfaces and adjacent modules. The output becomes the starting point for a capability and interface workshop.