top of page

Mastering Car Informatics: Essential Standards for On-Board Computer Systems and Automated Driving

53 minutes ago
8 min read

Car informatics is revolutionizing the automotive industry, driving advancements in automated driving functions and connected vehicle systems. As on-board computer systems grow more complex, the need for clear, standardized methods of connecting environmental sensors to data fusion units has never been more critical. This article explores four essential ISO standards that define logical interfaces for radar, ultrasonic, supportive sensor, and object-level data in road vehicles. By adopting these standards, businesses leverage improved productivity, enhanced security, futureproof scalability, and a decisive edge in digital transformation.


Overview: The Essential Role of Standards in Car Informatics

The automotive sector is entering an era where intelligent vehicles—equipped with advanced driver assistance systems (ADAS), autonomous features, and rich onboard data—are the norm. On-board computer systems process real-time inputs from various environmental sensors (like radar and ultrasonic modules) and make split-second decisions impacting both safety and operational efficiency. To manage the complexity and diversity of sensor data, manufacturers and solution providers must rely on well-defined international standards that ensure:

  • Consistent and secure sensor integration

  • Interoperability among diverse suppliers and platforms

  • Reliable, validated information exchange to underpin critical driving functions

  • Rapid, scalable deployment of new technologies within connected fleets

In this guide, you’ll learn about four cornerstone standards in car informatics:

  • ISO 23150-11:2026: Radar specific logical interfaces

  • ISO 23150-14:2026: Ultrasonic specific logical interfaces

  • ISO 23150-20:2026: Supportive and sensor input interfaces

  • ISO 23150-2:2026: Object level interfaces

Understanding and implementing these standards is vital for businesses seeking to innovate, remain compliant, and secure a sustainable position in today’s fast-evolving mobility ecosystem.


Detailed Standards Coverage

ISO 23150-11:2026 - Radar Specific Logical Interfaces

Road vehicles — Logical interface between sensors and data fusion unit for automated driving functions — Part 11: Radar specific interfaces

What does this standard cover? ISO 23150-11:2026 specifies technology-specific logical interfaces for radar sensors or radar sensor clusters in road vehicles with automated driving capabilities. It focuses on well-structured logical (software-level) connections, distinguishing between feature, advanced detection, and detection level interfaces. Significantly, it does not address hardware (electrical or mechanical) specifications or raw data flows, streamlining implementation for system architects.

Key requirements and specifications:

  • Defines the logical structure and signals for integrating radar-based environmental data.

  • Requires implementation of dynamic interface structures (such as detection headers and detection entities for radar returns).

  • Mandates handling of ambiguity grouping IDs, detection ambiguity probabilities, and various domain-specific ambiguity signals when radar technology introduces uncertainties.

  • References general interface principles found in ISO 23150-1:2026 but specializes them for radar.

Who should comply?

  • Automotive manufacturers (OEMs) integrating or supplying advanced driver assistance or automated driving systems.

  • Sensor and electronics suppliers providing radar hardware and software stacks.

  • Tier one system integrators developing vehicle data fusion and control modules.

Practical implications:

  • Streamlines integration and certification of new radar sensor models.

  • Reduces system development complexity by clearly defining software data exchange contracts.

  • Ensures robust data fusion for use cases including adaptive cruise control, collision avoidance, and automated parking.

Notable features:

  • Focus on dynamic interface structures for scalable support of multiple radar sensors.

  • Clear delineation between generic and technology-specific interface profiles.

  • Comprehensive signal set for all logical levels, supporting modular vehicle electronics development.

Key highlights:

  • Modular, scalable radar interface structures

  • Unambiguous data exchange semantics for automated driving

  • Enables efficient, safe integration of radar technologies across platforms

ISO 23150-14:2026 - Ultrasonic Specific Logical Interfaces

Road vehicles — Logical interface between sensors and data fusion unit for automated driving functions — Part 14: Ultrasonic specific interfaces

What does this standard cover? ISO 23150-14:2026 articulates the logical interface requirements and signal structures for integrating ultrasonic sensors or sensor clusters into advanced vehicle computing environments. As with the radar standard, its focus is on technology-specific, software-level exchanges, spanning feature, advanced detection, and detection levels.

Key requirements and specifications:

  • Standardizes headers, signal groupings, and entity profiles for transmitting rich ultrasonic sensing information such as object position, classification, and recognition probability.

  • Ensures support for dynamically managed sensor arrays and multiple feature classifications.

  • Defines status, segment, measurement, and trilateration structures critical for interpreting near-field environments (e.g., parking, low-speed maneuvers).

  • Integrates alignment with general sensor interface principles, with adaptations for high-frequency, short-range ultrasonic operation.

Who should comply?

  • OEMs incorporating parking assist, collision avoidance, or low-speed autonomous driving features.

  • Developers of ultrasonic sensor systems, ECUs, or integrated fusion units.

  • Tier one/aftermarket solution providers implementing modular sensor clusters.

Practical implications:

  • Promotes tight, safe integration of ultrasonic sensors in dense environments (e.g., urban, parking garages).

  • Simplifies multi-sensor fusion, crucial for reliable object detection and automated low-speed vehicle decision-making.

  • Fosters product interoperability and upgradability.

Notable features:

  • Dynamic, multi-dimensional feature and detection set structures

  • Capability to flag sensor status, measurements, and operational anomalies

  • Full support for multi-classification of detected ultrasonic features

Key highlights:

  • Robust, future-ready ultrasonic data exchange protocols

  • Detailed measurement/status signal specification

  • Enables seamless adoption of ultrasonic clusters in modern fleets

ISO 23150-20:2026 - Supportive and Sensor Input Interfaces

Road vehicles — Logical interface between sensors and data fusion unit for automated driving functions — Part 20: Supportive and sensor input interfaces

What does this standard cover? ISO 23150-20:2026 extends the car informatics interface suite to include supportive sensor interfaces and a common sensor input interface. It establishes how data such as sensor health, calibration, and performance are exchanged, ensuring that environmental sensors function with verified accuracy and reliability.

Key requirements and specifications:

  • Specifies:

    • Sensor performance interfaces (for quality and impairment reporting, e.g., rain, dirt, hardware issues)

    • Sensor health interfaces (diagnostics, cleaning, defect status)

    • Sensor calibration interfaces (position/sensor alignment management)

    • Common sensor input interfaces (centralized commands such as mode configuration or pose adjustments)

  • Mandates dynamic, modular representation for all supportive data elements.

  • Facilitates multiple ECUs providing complementary sensor input data streams.

  • References, extends, and integrates with generic principles from ISO 23150-1.

Who should comply?

  • Automotive electronics/system providers designing diagnostic, maintenance, and calibration workflows

  • Fleet operators demanding robust, scalable approaches to sensor health and remote configuration

  • Developers integrating live sensor self-checks and automated over-the-air updates

Practical implications:

  • Supports predictive maintenance and minimizing costly downtime

  • Essential for reliable, certified operation of safety-critical autonomous functions

  • Allows for remote diagnostics, sensor recalibration, and streamlined in-field service

Notable features:

  • Comprehensive interface support for real-world sensor impairments

  • Standardized health and calibration data objects

  • Supports flexible configuration/command pathways for complex sensor networks

Key highlights:

  • Pivotal for operational assurance and lifecycle management

  • Reduces maintenance costs via standard, interoperable health reporting

  • Makes large, complex fleets easier to scale and support

ISO 23150-2:2026 - Object Level Interfaces

Road vehicles — Logical interface between sensors and data fusion unit for automated driving functions — Part 2: Object level interfaces

What does this standard cover? ISO 23150-2:2026 underpins the semantic bridge between raw or feature-based sensor data and object-centric environmental models. The standard details object-level logical interfaces for potentially moving objects, road objects, static objects, and free-space objects—all critical to accurate, real-time scene interpretation in automated driving systems.

Key requirements and specifications:

  • Prescribes headers, entity groupings, and signal formats for:

    • Potentially moving objects (e.g., vehicles, pedestrians)

    • Road objects (road markings, lane boundaries)

    • Static objects (buildings, signs)

    • Free-space definitions (drivable/non-drivable zones)

  • Specifies existence probability, object recognition, motion status, position, measurement, and bounding box definitions.

  • Mandates dynamic sizing for varying detection volumes and frequent scene changes.

  • Adapts to modular object groupings for scalable perception pipeline design.

Who should comply?

  • Developers of vehicle perception stacks, sensor fusion algorithms, and scene modeling engines

  • Automotive companies integrating multi-sensor systems for automated and connected cars

  • ADAS and ADF (autonomous driving function) integrators

Practical implications:

  • Standardizes 360-degree scene awareness, crucial for safe autonomous vehicle decision-making

  • Ensures clear interpretation and fusion of multi-source, multi-type object data

  • Enables modular architectural growth, supporting rapid feature expansion

Notable features:

  • Universal object definition—enabling seamless sensor data aggregation

  • Detailed tracking, recognition, and object classification semantics

  • Support for real-time updates and object state transitions

Key highlights:

  • The cornerstone for semantic modeling in connected vehicles

  • Facilitates next-generation ADAS/ADF development

  • Streamlines future updates and cross-platform compatibility

Access the full standard: View ISO 23150-2:2026 on iTeh Standards

Industry Impact & Compliance

How Do These Standards Affect Automotive Businesses?

Logical interface standards for on-board computer systems have become a business imperative—not just a technical check-box. They impact:

  • Productivity: Minimize engineering time and resource duplication with clearly defined software/hardware handoffs. Teams can work in parallel, boosting output and shortening time-to-market for new vehicle features.

  • Security: Standardized logical connections mean fewer ad-hoc integrations, reducing cyberattack surfaces and creating robust, testable interfaces ideal for safety-critical contexts.

  • Scalability: Scale sensor networks with plug-and-play simplicity. New suppliers or next-generation sensors can be incorporated without re-architecting the system, supporting ‘future-ready’ vehicle upgrades.

  • Interoperability: Multiple suppliers, platforms, and partners can coexist in the same system, making sourcing and lifecycle management more resilient.

  • Regulatory & Legal Compliance: Meeting ISO standards is a growing expectation among regulators, insurers, and industry partners. Non-compliance risks regulatory delays, liability, and loss of market access.


The Risks of Non-Compliance

  • Integration failures and wasted engineering effort

  • Security vulnerabilities due to mismatches or ‘black box’ components

  • Loss of market access in regulated regions demanding certified automation

  • Product recalls or safety issues causing brand or financial damage

  • Competitive disadvantage—as automation, OTA updates, and rapid scaling become the norm

Benefits of Adopting These Standards

  • Streamlined product development and smoother upgrades

  • Lower operational costs over the vehicle’s lifetime

  • Proven quality and elevated customer trust

  • Compliance with current and future mobility regulations

  • Competitive differentiation: quicker, safer, more adaptable products


Implementation Guidance: Best Practices for Adopting Car Informatics Standards

a. Start with a Standards Assessment

  • Map current sensor interfaces and data fusion architectures to the ISO 23150 series

  • Identify legacy systems or proprietary protocols that would benefit from migration

b. Prioritize Modular Design

  • Design sensor and computing modules to conform to the specified logical interfaces (radar, ultrasonic, supportive, object)

  • Leverage dynamic and flexible sizing features for multi-sensor and scalable deployments

c. Engage in Cross-Functional Planning

  • Bring together R&D, software, security, and operations teams at the project’s outset

  • Use standards-aligned interface definitions as collaboration and compliance checkpoints

d. Partner with Trusted Suppliers

  • Work with suppliers who already support ISO 23150-compliant products or APIs

  • Request compliance documentation and certification as part of the procurement process

e. Automate Testing and Validation

  • Build automated test routines to validate conformance of sensor and fusion interfaces

  • Simulate dynamic environments to catch edge cases early in the product lifecycle

f. Invest in Lifecycle Management Tools

  • Adopt fleet or factory management systems that track sensor health, calibration, and data integrity as prescribed in the standards

  • Use remote OTA update frameworks compatible with the logical interface modularity

Resources for Organizations

  • iTeh Standards Portal – For access to the latest versions andsupport documents

  • ISO/TC 22/SC 31 – Technical updates and support

  • Industry groups and alliances advancing common interface implementation


Conclusion & Next Steps

Car informatics standards like ISO 23150-11, ISO 23150-14, ISO 23150-20, and ISO 23150-2 have become the foundation of safe, secure, and future-ready automated driving systems. By leveraging these logical interface specifications, organizations:

  • Streamline integration and validation across the automotive supply chain

  • Enhance cybersecurity and operational resilience

  • Enable rapid scaling as sensor technologies and software evolve

  • Comply with both today’s and tomorrow’s regulatory frameworks and customer expectations

Recommendations:

  1. Audit your current and planned on-board systems against these standards—identify gaps and opportunities for accelerated transformation.

  2. Engage with suppliers and partners early—ensure the whole ecosystem is aligned around these best practices.

  3. Stay up-to-date—as ISO and related standards advance, continuous improvement will ensure compliance and maximize value.

Explore these critical car informatics and on-board systems standards on iTeh Standards to stay ahead in the evolving world of automotive technology.

 
 
 

Comments


© 2021 by SAUGATECH

bottom of page