Vehicle Electronics
Vehicle Electronics Compliance and Component Approval
Automotive EMC under UNECE R10 and CISPR 25, functional safety, component type approval, and radio approval for ECUs, infotainment, sensors, lighting, and electronic sub-assemblies supplied to vehicle manufacturers and the aftermarket.
The category
Vehicle electronics are approved twice: by the customer's specification and by the regulator's rules.
Electronic control units, infotainment and displays, cameras and sensors, lighting, body electronics, battery management systems, and the growing list of electronic sub-assemblies in a vehicle are regulated through a combination of vehicle type approval regulations and the electronics regulatory set. UNECE R10 governs EMC for vehicles and their electronic sub-assemblies, with component-level approval available. Lighting components have their own UNECE regulations. Functional safety under ISO 26262 is a customer requirement in practice and increasingly a regulatory expectation. Any radio in the component needs communications regulator approval in every market of sale. And aftermarket sales bring replacement part rules and national certification schemes.
On top of the regulatory requirements sit the OEM's specifications: CISPR 25 and ISO 11452 EMC test plans that often exceed R10, environmental and durability testing under ISO 16750 and customer standards, and cybersecurity requirements flowing down from UNECE R155. A supplier's compliance file has to satisfy both the regulator and the customer, and the two don't always ask for the same thing.
ORBIS Compliance works with vehicle electronics suppliers to scope the regulatory and customer requirements together, coordinate testing at automotive-recognized laboratories, manage component type approvals and radio approvals across markets, and keep the file current through the frequent hardware and software revisions automotive programs involve.
The vehicle electronics file
What electronic components are evaluated and approved for.
- Automotive EMC under UNECE R10 for electronic sub-assemblies, with CISPR 25, ISO 11452, and ISO 7637 test methods at regulatory and OEM severities.
- Component type approval under UNECE regulations for lighting, mirrors, audible warning, and other regulated component categories.
- Functional safety under ISO 26262 for components with safety-related functions, with ASIL-appropriate development and evidence.
- Radio type approval for Bluetooth, Wi-Fi, cellular, UWB, and other transmitters in infotainment, telematics, keyless, and sensor modules, in every market.
- Environmental and durability testing under ISO 16750 and OEM standards: temperature, humidity, vibration, and electrical transients.
- Cybersecurity evidence under ISO/SAE 21434 flowing down from UNECE R155, for connected and software-updatable components.
- Substance and producer compliance: ELV Directive substance restrictions, RoHS-adjacent rules, and battery obligations for components containing cells.
- Aftermarket certification where components are sold as replacement parts under national schemes and replacement part rules.
The radio in the component
The OEM approves the vehicle. The communications regulator approves your radio. Separately.
Infotainment units with Bluetooth and Wi-Fi, telematics control units with cellular modems, keyless entry and UWB digital key modules, tire pressure sensors, and radar sensors are all transmitters. Each needs type approval from the communications regulator in every market where the vehicle is sold, under rules that don't care whether the transmitter is in a car. Vehicle type approval covers EMC under R10; it doesn't cover radio authorization.
Suppliers often assume the OEM handles radio approvals, and OEMs often assume the supplier's module certification covers it. In practice the approvals frequently need to be held at the component or module level, in the supplier's name or under a local holder, in each market. Antenna integration, co-location with other radios, and firmware updates all affect the grants.
ORBIS scopes the radio approvals for vehicle electronics across markets, clarifies who holds what with the OEM, provides local representation where required, and assesses hardware and firmware changes against every affected grant.
Change control
Automotive programs revise hardware and software constantly. Every revision touches approvals.
An R10 approval, a radio grant, a functional safety case, and a lighting component approval each have their own rules for what counts as a change. ORBIS Intelligent Compliance holds them together so a revision is assessed against all of them before it ships.
Questions
Vehicle electronics compliance
Does our OEM's vehicle type approval cover our component's EMC?
+
It can, if the vehicle-level R10 approval includes your sub-assembly. Many OEMs prefer or require component-level R10 approval so the ESA can be used across vehicle types and in the aftermarket. Which route applies is agreed with the OEM, and ORBIS manages the component approval where it's needed.
Our component uses a pre-certified cellular module. Do we need our own radio approvals?
+
In many markets, yes, at the component or vehicle level depending on integration and local rules. The module's grant covers the module in its tested configuration. Vehicle integration, antenna choices, and co-located radios can require host-level filings. ORBIS reviews it per market.
How do UNECE R155 requirements reach us as a supplier?
+
Through the OEM's cybersecurity management system, which requires evidence from suppliers of connected and software-relevant components, typically structured around ISO/SAE 21434. Suppliers need documented cybersecurity development and vulnerability management for their products. ORBIS helps scope and document that evidence alongside the rest of the component file.
Electronics that pass the OEM's gate and the regulator's.
Bring the component, its interfaces and radios, and the markets the vehicles will sell into. We'll scope the EMC, functional safety, component approval, and radio requirements as one file.
Book a Discussion