EU CE新规: LiDAR Must Pass ASAM OpenX 2.1 Interop Testing

On May 10, 2026, the EU Notified Bodies Joint Working Group (NB-JWG) officially mandated ASAM OpenX 2.1 as the compulsory interoperability test benchmark for LiDAR sensors under CE conformity assessment. This regulatory shift directly affects manufacturers and suppliers targeting EU markets for autonomous driving, smart port operations, and AGV navigation systems — marking a significant escalation in technical validation requirements for sensor-level interoperability.

Event Overview

The EU Notified Bodies Joint Working Group (NB-JWG) activated ASAM OpenX 2.1 as a mandatory testing standard for CE certification of LiDAR sensors on May 10, 2026. All LiDAR products intended for use in EU-regulated applications — including autonomous vehicles, intelligent port infrastructure, and automated guided vehicle (AGV) navigation — must now pass all 217 defined full-scenario test cases under OpenX 2.1. These include edge conditions such as rain, fog, intense ambient light, and multi-vehicle cooperative perception. Certification by an EU-accredited third-party body is required; non-compliant products will be denied the CE marking and excluded from placing on the EU market.

Industries Affected

Direct Exporters and Trade Enterprises: These entities face immediate market access risk. CE marking is a legal prerequisite for product placement in the EU; failure to meet the OpenX 2.1 requirement renders existing or planned LiDAR offerings commercially nonviable in the region. Impact manifests not only in delayed time-to-market but also in contractual exposure — especially where OEMs or system integrators have incorporated CE compliance clauses into procurement agreements.

Raw Material and Component Suppliers: While upstream suppliers do not undergo CE certification directly, their subcomponents (e.g., laser diodes, photodetectors, timing controllers) influence sensor-level behavior in OpenX 2.1 scenarios. As LiDAR OEMs tighten design specifications to meet reproducible test outcomes, suppliers may face stricter performance validation requests — particularly around thermal stability under high-duty-cycle fog simulation or spectral consistency across illumination conditions.

LiDAR Design and Manufacturing Firms: These are the primary obligated parties. Compliance requires full integration of OpenX 2.1 test logic into development workflows — including scenario-based functional safety analysis, traceable test reporting, and version-controlled simulation-to-hardware validation. Engineering teams must now allocate resources for OpenX 2.1-compatible toolchains, certified test environments, and personnel trained in ASAM standards interpretation — increasing both R&D lead time and certification cost per model variant.

Supply Chain Service Providers (e.g., Test Labs, Certification Consultants, Simulation Platform Vendors): Demand for OpenX 2.1-aligned services is rising sharply. Independent test labs must achieve NB-JWG recognition for OpenX 2.1 execution; simulation platform vendors are under pressure to certify their tools against OpenX 2.1’s reference implementations. Meanwhile, consultants assisting SMEs with CE documentation must now demonstrate competence in mapping OpenX 2.1 test results to EN IEC 61508/ISO 26262 safety arguments — adding complexity to service scope and pricing models.

Key Focus Areas and Recommended Actions

Verify current product alignment with OpenX 2.1 v2.1 test suite

Manufacturers should conduct internal gap assessments using publicly available OpenX 2.1 documentation and reference datasets — prioritizing coverage of the 217 test cases, especially those involving adverse weather and dynamic multi-agent interactions. Early identification of scenario-specific failures enables targeted firmware or optical redesign before formal certification attempts.

Engage accredited test laboratories early — not just before submission

Given limited capacity among NB-JWG-recognized labs offering OpenX 2.1 testing, firms are advised to secure preliminary validation slots and co-develop test plans well ahead of intended CE application dates. Pre-submission dry-run audits help uncover inconsistencies between lab execution and manufacturer’s interpretation of scenario definitions.

Update technical documentation to reflect OpenX 2.1 traceability

CE technical files must now explicitly link each OpenX 2.1 test case to corresponding functional requirements, safety mechanisms, and verification evidence. This includes version-controlled logs of simulation parameters, hardware-in-the-loop configurations, and environmental replication settings — moving beyond pass/fail summaries toward auditable, reproducible validation narratives.

Editorial Perspective / Industry Observation

Observably, this regulation signals a structural pivot in EU sensor policy: from component-level electromagnetic compatibility and mechanical safety toward system-aware, scenario-driven interoperability. It is not merely a technical update but a de facto standardization lever — encouraging convergence around ASAM’s open simulation frameworks while raising barriers for proprietary or closed-loop validation approaches. Analysis shows that firms relying heavily on in-house test suites without OpenX alignment may face disproportionate rework costs. From an industry perspective, the emphasis on real-world edge cases — rather than idealized lab conditions — reflects growing regulatory attention to operational design domain (ODD) fidelity in automated systems. Current more critical concern lies less in the number of test cases (217) and more in the lack of harmonized guidance on how to interpret ambiguous scenario boundaries — e.g., “moderate fog” — across different labs.

Conclusion

This mandate does not represent a temporary compliance hurdle but a foundational recalibration of what constitutes ‘interoperable’ in EU-regulated mobility ecosystems. For LiDAR stakeholders, it underscores that sensor qualification is increasingly inseparable from contextual system behavior — demanding deeper cross-disciplinary collaboration between optics engineers, software architects, and functional safety specialists. A rational reading suggests that long-term competitiveness will hinge less on raw specification metrics and more on verifiable, standardized, and scenario-resilient performance narratives.

Source Attribution

Official source: EU Notified Bodies Joint Working Group (NB-JWG), OpenX 2.1 Implementation Notice for LiDAR Sensors under CE Framework, effective May 10, 2026. Published via NANDO database and ASAM e.V. official repository (asam.net/openx).
Note: Pending clarification on transitional provisions for legacy-certified LiDAR models, and potential extension of scope to non-automotive LiDAR applications (e.g., robotics, infrastructure monitoring) — both remain under active review by NB-JWG and expected to be updated before Q4 2026.