1. What is ECE R10?

Electromagnetic compatibility (EMC) is a fundamental requirement in modern automotive engineering. Vehicles increasingly depend on electronic systems for propulsion, braking, steering, safety functions, communication, driver assistance and many other functions. These systems must operate reliably in close proximity to one another and within an environment where electromagnetic disturbances are unavoidable.

This is where UN Regulation No. 10, commonly referred to as ECE R10 or UN R10, comes into play.

ECE R10 establishes requirements for the electromagnetic compatibility of vehicles and certain electrical/electronic sub-assemblies intended for use in vehicles. It is not simply an automotive version of a conventional EMC laboratory test. Instead, it forms part of the UNECE vehicle type-approval framework and defines the conditions under which vehicles and relevant electrical/electronic equipment can demonstrate compliance with electromagnetic compatibility requirements.

1.1 What does ECE R10 mean?

The official designation is:

UN Regulation No. 10 – Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility.

The regulation was developed within the framework of the United Nations Economic Commission for Europe (UNECE) and its World Forum for Harmonization of Vehicle Regulations (WP.29).

The term “ECE R10” is still widely used throughout the automotive industry. In regulatory documentation, however, the designation UN Regulation No. 10 is generally the more precise reference.

The regulation has evolved through multiple revisions and series of amendments. UNECE continues to develop and amend the regulation, including work on the 07 series of amendments and subsequent supplements. This means that manufacturers cannot rely solely on the generic term “R10”; the applicable version and amendment status need to be established for a specific approval project.

1.2 What is the purpose of ECE R10?

The fundamental purpose of ECE R10 is to ensure that vehicles and relevant electrical/electronic equipment are electromagnetically compatible with their environment.

This involves two basic aspects of EMC.

Electromagnetic emissions

A vehicle or electronic system can itself generate electromagnetic disturbances.

These disturbances can be:

• radiated through the air;
• conducted through electrical wiring;
• generated by switching electronics;
• associated with motors, inverters or power electronics; or
• produced by other electronic functions operating within the vehicle.

ECE R10 establishes requirements intended to prevent such disturbances from reaching levels that could unacceptably affect other equipment.

The basic question is:

Does the vehicle or equipment generate electromagnetic disturbances that could interfere with other systems?

Electromagnetic immunity

The opposite problem can occur as well.

A vehicle or electronic system can be exposed to electromagnetic disturbances generated by other equipment, communication systems, transmitters, electrical systems or the vehicle’s own electronics.

The relevant equipment therefore needs to maintain its required functions when exposed to defined electromagnetic disturbances.

The basic question is:

Can the vehicle or equipment continue to perform its intended functions when exposed to defined electromagnetic disturbances?

ECE R10 therefore addresses both sides of electromagnetic compatibility:

Emissions → The equipment must not create unacceptable electromagnetic interference.

Immunity → The equipment must be sufficiently resistant to electromagnetic interference.

1.3 Why is this particularly important for vehicles?

A modern vehicle is effectively a complex network of interconnected electronic systems.

Depending on the vehicle, this can include:

• Electronic control units (ECUs)
• Battery management systems
• Inverters and converters
• Electric drive systems
• Sensors
• Radar systems
• Cameras
• ADAS functions
• Infotainment systems
• GNSS receivers
• Bluetooth and Wi-Fi systems
• Cellular communication systems
• Charging systems
• Electronic steering systems
• Electronic braking systems
• Lighting systems
• Body control modules
• Actuators and other electronic control systems

These systems do not operate independently.

They share electrical networks, wiring harnesses, communication interfaces and physical space. A disturbance generated by one system can therefore potentially affect another system.

At the same time, external electromagnetic fields can enter the vehicle and affect electronic systems inside it.

The consequences can range from a temporary loss of a non-critical function to a malfunction of a system that is important for vehicle operation.

For this reason, automotive EMC is not simply about protecting radio reception or preventing interference with consumer electronics. It is closely connected to the reliable operation of the vehicle’s electronic architecture.

1.4 ECE R10 is part of the vehicle type-approval system

One of the most important points to understand about ECE R10 is its regulatory context.

ECE R10 is part of the UNECE type-approval system established under the 1958 Agreement.

This makes it fundamentally different from a general product EMC assessment.

A conventional EMC assessment may demonstrate that a product satisfies the applicable electromagnetic compatibility requirements of a product-specific regulatory framework.

An ECE R10 approval, by contrast, is connected to the vehicle type-approval process and can apply either to a complete vehicle or, under the relevant provisions, to an electrical/electronic sub-assembly (ESA).

The regulation itself contains provisions covering areas such as application for approval, approval, markings, conformity of production, modifications and extensions of approval, as well as specific requirements and test methods.

This distinction becomes important later when considering the approval authority, technical service, test scope and documentation required for an R10 project.

1.5 What is an Electrical/Electronic Sub-Assembly?

ECE R10 does not only concern complete vehicles.

The regulation also addresses certain electrical/electronic sub-assemblies, commonly referred to as ESAs.

An ESA is essentially an electrical or electronic unit intended for installation in a vehicle and capable of affecting the vehicle’s electromagnetic environment or being affected by it.

Depending on the application, this can include equipment such as:

• Electronic control units
• Automotive electronic modules
• Lighting electronics
• Communication equipment
• Sensors
• Power electronics
• Charging-related equipment
• Other vehicle-mounted electrical or electronic systems

However, this does not mean that every electronic device that happens to be used in a vehicle automatically requires an individual R10 approval.

The applicability of the regulation depends on factors such as the intended vehicle installation, the electrical connection to the vehicle, the function of the equipment and the specific provisions of the regulation.

The R10 classification provisions therefore need to be examined rather than applying a simple rule of “automotive product = R10.”

The UNECE material for the 07 series, for example, contains a specific ESA classification approach addressing factors such as whether an ESA is intended for vehicle fitment, whether it is connected to vehicle wiring, and how it is installed or used.

1.6 ECE R10 is not just an EMC test

This is one of the most important concepts for manufacturers.

It is common to hear statements such as:

“The product passed EMC, so it is R10 compliant.”

That statement can be misleading.

An EMC test is part of the technical evidence required to demonstrate compliance. It is not necessarily equivalent to the complete regulatory approval.

ECE R10 involves a broader framework that can include:

• Determining whether the regulation applies
• Defining the approval scope
• Identifying the relevant vehicle or ESA
• Establishing the applicable regulatory version
• Defining the test configuration
• Performing the required tests
• Assessing the results
• Preparing the required documentation
• Obtaining the applicable type approval
• Maintaining conformity of production
• Managing later modifications and extensions

The distinction between testing and type approval is therefore fundamental.

A laboratory can generate test results.

The type-approval process establishes whether the relevant vehicle or ESA has been approved under UN Regulation No. 10.

1.7 Why the applicable version matters

ECE R10 is not static.

The regulation has been amended repeatedly to reflect developments in automotive technology and EMC testing.

UNECE documents show ongoing work on amendments and supplements to the regulation, including proposals addressing technical requirements and test methods.

For manufacturers, this means that referring simply to “ECE R10” is often not enough when planning a compliance project.

A proper assessment should establish:

• Which revision or series of amendments applies
• Which supplements and corrigenda are relevant
• Whether transitional provisions apply
• Which test methods and standards are referenced
• Which requirements apply to the particular vehicle or ESA

This is particularly important for projects with long development cycles, because the regulatory requirements can evolve between initial product development, testing and final approval.

1.8 ECE R10 in the broader automotive compliance landscape

ECE R10 should also not be viewed in isolation.

Automotive products can be subject to numerous regulatory and technical requirements depending on their function and intended market.

For example, a product may involve requirements relating to:

• EMC
• Radio communication
• Functional safety
• Cybersecurity
• Electrical safety
• Environmental performance
• Vehicle-specific functional requirements
• Type approval
• Conformity of production

ECE R10 addresses the electromagnetic compatibility aspect of this broader compliance landscape.

It does not by itself demonstrate that an automotive product satisfies every other regulatory requirement that may apply to it.

This is why the correct starting point for an automotive compliance project is not simply:

“Which EMC test should we perform?”

The better question is:

“Which regulatory framework applies to this product, and what role does ECE R10 play within the overall approval strategy?”

1.9 The key distinction manufacturers should remember

The simplest way to understand ECE R10 is this:

ECE R10 is the UNECE regulatory framework for electromagnetic compatibility within the vehicle type-approval environment.

It addresses both emissions and immunity, applies to vehicles and certain electrical/electronic sub-assemblies, and connects EMC testing with a formal type-approval process.

For manufacturers, the first challenge is therefore not necessarily the laboratory test itself.

The first challenge is determining:

Does ECE R10 apply, what exactly needs to be approved, which requirements apply, and what approval route is appropriate?

That is the starting point for an effective R10 compliance strategy.

Control the Scope. Control the Cost.

2. Why is ECE R10 Important in Automotive Applications?

The role of electronics in vehicles has changed fundamentally over the past decades. A modern vehicle is no longer primarily a mechanical system with a limited number of electronic functions. It is a highly interconnected electronic system in which numerous control units, sensors, communication interfaces and power electronics operate simultaneously.

This increasing electronic complexity makes electromagnetic compatibility (EMC) a critical part of automotive compliance.

ECE R10 provides the regulatory framework for addressing this issue within the UNECE vehicle type-approval system.

2.1 The increasing amount of electronics in modern vehicles

A modern vehicle can contain a large number of electronic systems that operate simultaneously.

Depending on the vehicle, these may include:

• Engine and powertrain control units
• Battery management systems
• Inverters and DC/DC converters
• Electric drive systems
• Advanced Driver Assistance Systems (ADAS)
• Radar sensors
• Cameras
• Ultrasonic sensors
• GNSS receivers
• Bluetooth and Wi-Fi systems
• Cellular communication systems
• Infotainment systems
• Charging systems
• Electronic steering systems
• Electronic braking systems
• Lighting control units
• Body control modules
• Airbag and restraint systems
• Sensors and actuators

Each system can have its own electrical characteristics, operating frequencies, switching behaviour and interfaces.

At the same time, these systems are physically close to one another and are often connected through common power supplies, ground systems, wiring harnesses and communication networks.

This creates a complex electromagnetic environment inside the vehicle.

2.2 Electromagnetic interference can work in both directions

EMC problems can generally occur in two ways.

First, one system can generate electromagnetic disturbances that affect another system.

For example, a switching power converter or inverter can generate high-frequency disturbances. These disturbances may be conducted through the vehicle’s electrical network or radiated into the surrounding environment.

Second, a system can be affected by electromagnetic disturbances generated elsewhere.

A sensitive electronic control unit may, for example, react incorrectly when exposed to an electromagnetic field or conducted transient that exceeds its immunity capability.

This creates a basic EMC relationship:

One system can be the source of interference while another system becomes the victim.

In a modern vehicle, the same electronic system can potentially be both.

2.3 Why this matters for vehicle functionality

Not every EMC problem has the same consequences.

A disturbance affecting an entertainment function may be inconvenient without creating a significant safety concern.

A disturbance affecting a critical vehicle function can have much more serious consequences.

Consider systems involved in:

• Steering
• Braking
• Propulsion
• Driver assistance
• Vehicle stability
• Safety-related sensing
• Charging
• Communication between control units

If such a system behaves unexpectedly because of electromagnetic interference, the consequences can extend far beyond a simple loss of comfort.

This is one reason why automotive EMC is closely connected to the reliable operation of the vehicle.

ECE R10 is therefore not simply about ensuring that electronic devices do not interfere with radios or other consumer equipment.

It forms part of the regulatory framework intended to ensure that the vehicle’s electronic systems can operate together without unacceptable electromagnetic interference.

2.4 The vehicle is an interconnected electromagnetic system

A vehicle should not be considered as a collection of completely independent electronic products.

The electrical architecture connects many of the systems together.

Power distribution, grounding, communication networks and wiring harnesses can provide paths through which disturbances propagate.

At the same time, the physical arrangement of components determines how electromagnetic fields can couple from one system to another.

This means that the EMC performance of a component can depend not only on the electronics inside the enclosure, but also on factors such as:

• Cable routing
• Cable length
• Shielding
• Grounding
• Connector design
• Vehicle installation
• Power supply
• Load conditions
• Physical location
• Operating mode

For this reason, automotive EMC testing must consider the intended configuration rather than treating the equipment as an isolated electronic box.

2.5 Electrification increases EMC challenges

The transition from conventional internal-combustion vehicles to hybrid and fully electric vehicles has introduced additional high-power electronic systems.

Electric vehicles can contain:

• High-voltage batteries
• Traction inverters
• DC/DC converters
• On-board chargers
• Charging interfaces
• Electric motors
• Battery management systems
• High-voltage distribution systems

Many of these systems involve rapid switching of significant electrical power.

High-frequency switching can create electromagnetic disturbances that need to be controlled.

At the same time, sensitive electronic systems must continue to operate correctly in the presence of the electromagnetic environment created by these high-power systems.

Electrification therefore increases the importance of EMC at both the system and component level.

2.6 Connected vehicles create additional electromagnetic activity

Modern vehicles increasingly communicate with external systems and networks.

Depending on the vehicle, this can include:

• Cellular communication
• Wi-Fi
• Bluetooth
• GNSS
• Vehicle-to-everything communication
• Keyless entry and access systems
• Remote services
• Wireless charging
• Other radio-based functions

These systems intentionally generate or receive electromagnetic energy.

The vehicle must therefore accommodate a growing number of radio systems while ensuring that these systems do not cause unacceptable interference with other vehicle functions.

This makes the relationship between EMC and radio functionality increasingly important.

A system can be designed to transmit electromagnetic energy intentionally while still needing to control unwanted emissions and maintain adequate immunity.

2.7 ADAS and automated driving increase the importance of immunity

Advanced Driver Assistance Systems rely on multiple electronic systems operating together.

Depending on the vehicle, these can include:

• Radar
• Cameras
• Lidar
• Ultrasonic sensors
• GNSS
• Vehicle motion sensors
• Electronic control units
• Communication networks

These systems continuously collect and process information.

If an electromagnetic disturbance causes a sensor or control unit to behave incorrectly, the resulting effect can propagate through the vehicle’s electronic architecture.

As vehicle automation increases, the reliability of these electronic functions becomes increasingly important.

This is one reason why the automotive EMC environment continues to evolve alongside developments in ADAS and automated driving.

2.8 EMC is also a system-integration issue

A common mistake is to treat EMC exclusively as a property of an individual component.

In reality, the final EMC behaviour of an automotive system can depend on how multiple components interact.

A component may perform well under laboratory conditions but behave differently after installation into a vehicle because:

• The wiring configuration has changed.
• The grounding arrangement is different.
• Additional loads are connected.
• The component operates in a different environment.
• Other electronic systems are operating simultaneously.
• The cable routing creates different coupling paths.

This is particularly relevant for electrical/electronic sub-assemblies.

The compliance assessment must therefore consider the intended installation and operating conditions.

2.9 EMC requirements are becoming more complex

The automotive industry is moving towards vehicles with more electronics, higher levels of electrification, greater connectivity and increasing automation.

Each of these trends adds new electromagnetic sources or increases the sensitivity of the overall system.

At the same time, manufacturers must manage increasingly complex product configurations and variants.

A single electronic module may be installed:

• In different vehicle models
• In different vehicle platforms
• With different wiring configurations
• With different software versions
• With different communication interfaces
• In different physical locations

This creates additional challenges for compliance planning.

The manufacturer must understand which configurations are represented by the approval and whether changes to the product or installation could affect the existing compliance evidence.

2.10 Why EMC needs to be addressed early

One of the most important practical lessons is that EMC should not be treated as something that starts when the vehicle or component reaches the laboratory.

EMC performance is strongly influenced by design decisions made much earlier.

Examples include:

• PCB layout
• Component selection
• Power architecture
• Filtering
• Shielding
• Grounding
• Connector design
• Cable routing
• Enclosure design
• Software operating modes

If an EMC problem is discovered late in development, correcting it can require hardware modifications, software changes, additional testing or even mechanical redesign.

This can have a direct impact on both cost and project timing.

Early EMC consideration therefore reduces the risk that major problems are discovered only after the product has reached formal testing.

2.11 ECE R10 provides the regulatory framework

This is where ECE R10 becomes particularly relevant.

The regulation establishes the EMC requirements and approval framework against which the applicable vehicle or electrical/electronic sub-assembly is assessed.

It provides a structured basis for evaluating electromagnetic emissions and immunity rather than leaving the manufacturer to define an arbitrary EMC test program.

However, the existence of the regulation does not eliminate the need for proper project scoping.

The manufacturer still needs to determine:

• What is being approved?
• Which R10 provisions apply?
• Which vehicle or ESA configuration is relevant?
• Which functions must be monitored during immunity testing?
• Which operating conditions need to be represented?
• Which test methods and referenced standards apply?
• Which product variants are covered?

These questions should be answered before formal testing begins.

2.12 Why poor EMC scoping can become expensive

A poorly defined EMC scope can create problems in several ways.

The manufacturer may request testing that is not actually required.

Alternatively, an important test condition may be omitted.

Both situations can be costly.

Unnecessary testing increases laboratory costs and project time.

Missing testing can be even more problematic because the issue may only become visible later, potentially requiring:

• Additional laboratory time
• Retesting
• Design modifications
• New documentation
• Approval extensions
• Project delays

The cost of EMC compliance is therefore not determined only by the laboratory’s hourly rate.

It is also influenced by how well the project was scoped before testing started.

2.13 The importance of a structured compliance approach

For complex automotive products, EMC should be treated as part of an overall compliance strategy rather than as an isolated laboratory activity.

A structured approach can connect:

Product definition → Regulatory scope → Test plan → Laboratory quotation → Testing → Documentation → Approval → Change management

This creates a clearer relationship between the product configuration and the evidence required to demonstrate compliance.

It also makes it easier to identify potential problems before they become expensive.

2.14 Key takeaway

The importance of ECE R10 comes from the increasing electromagnetic complexity of modern vehicles.

Vehicles now contain large numbers of interconnected electronic systems, high-power electrical systems, wireless communication functions and increasingly sophisticated safety and automation technologies.

All of these systems must coexist within the same electromagnetic environment.

ECE R10 provides the regulatory framework for assessing this compatibility within the UNECE vehicle type-approval system.

For manufacturers, the central issue is therefore not simply whether a product can pass an EMC test.

The real question is:

Can the product perform its intended function reliably within the electromagnetic environment of the vehicle, while avoiding unacceptable interference with other systems?

And from a compliance perspective, that question needs to be translated into a clearly defined test scope before testing begins.

Control the Scope. Control the Cost.

3. Which Vehicles and Products Are Covered?

One of the first questions in an ECE R10 project is whether the regulation actually applies to the product in question.

This is more important than it may initially appear. Not every electronic product used in connection with a vehicle automatically requires an individual ECE R10 approval. The applicability depends on the type of vehicle or equipment, its intended use, its installation, its electrical connection to the vehicle and the applicable vehicle type-approval framework.

Understanding the scope of ECE R10 is therefore an essential part of the compliance assessment.

3.1 ECE R10 covers more than complete vehicles

ECE R10 is primarily associated with vehicle electromagnetic compatibility, but its scope is not limited to complete vehicles.

The regulation addresses:

• Vehicles subject to the relevant type-approval framework
• Electrical/electronic sub-assemblies (ESAs) intended for installation in vehicles
• Certain components and electronic systems that fall within the applicable ESA provisions

This distinction is important because the compliance route can be very different depending on whether the subject of approval is a complete vehicle or an individual electronic assembly.

A manufacturer developing an electronic control unit, for example, may not be applying R10 in exactly the same way as a vehicle manufacturer seeking approval for an entire vehicle type.

3.2 Vehicles within the type-approval framework

At vehicle level, ECE R10 forms part of the UNECE vehicle type-approval system.

The relevant vehicle categories depend on the applicable regulatory framework and the specific type-approval legislation under which the vehicle is being approved.

The vehicle itself is assessed as an integrated system.

This is important because the electromagnetic behaviour of a complete vehicle depends on the interaction between numerous systems, including:

• Powertrain electronics
• Electrical distribution
• Control units
• Wiring harnesses
• Sensors
• Communication systems
• Lighting
• Infotainment
• Charging systems
• Radio equipment
• Other electronic functions

Vehicle-level EMC assessment therefore looks at the vehicle in its intended configuration rather than treating each electronic system as an isolated product.

3.3 Electrical/Electronic Sub-Assemblies (ESAs)

A particularly important part of ECE R10 is the concept of the Electrical/Electronic Sub-Assembly, or ESA.

An ESA is an electrical or electronic unit intended to be fitted to a vehicle and capable of influencing the vehicle’s electromagnetic environment or being influenced by it.

Examples can include:

• Electronic control units
• Automotive electronic modules
• Lighting control electronics
• Sensors
• Power electronics
• Charging-related equipment
• Communication-related equipment
• Electronic control systems
• Other vehicle-mounted electrical/electronic equipment

An ESA can therefore be a relatively small electronic module while still being subject to the automotive EMC approval framework.

The fact that the equipment is supplied as a separate component does not by itself remove it from the scope of R10.

3.4 Not every automotive electronic product automatically requires R10 approval

This is one of the most important points for manufacturers.

It would be incorrect to apply a simple rule such as:

“If the product is used in a vehicle, it needs ECE R10.”

The actual applicability needs to be determined from the regulatory context.

Relevant considerations can include:

• What the equipment is
• What function it performs
• Whether it is intended for vehicle installation
• How it is electrically connected to the vehicle
• Whether it can influence vehicle functions
• Whether it is connected to the vehicle wiring
• Whether it is covered by the applicable ESA provisions
• Whether the equipment is already covered by the vehicle manufacturer’s approval strategy
• Which vehicle type-approval legislation applies

This means that an automotive product should first be scoped, rather than immediately assigned a predefined test program.

3.5 Vehicle equipment can have different regulatory roles

Two electronic products may look very similar from a technical perspective but have different regulatory roles.

For example, one device may be:

• Permanently installed in the vehicle
• Connected directly to the vehicle electrical system
• Responsible for a vehicle function
• Supplied as an automotive component

Another device might:

• Be temporarily connected
• Operate independently from the vehicle electrical system
• Be used outside the vehicle
• Have no defined role within the vehicle type-approval configuration

The fact that both products are used “in a vehicle” does not necessarily mean that they have the same regulatory status.

The intended installation and use therefore need to be considered as part of the scope assessment.

3.6 The intended installation matters

For automotive EMC, the installation environment is particularly important.

The same electronic unit can have different EMC characteristics depending on how it is installed.

Relevant factors can include:

• Supply voltage
• Power connections
• Grounding
• Cable length
• Cable routing
• Connector type
• Shielding
• Location within the vehicle
• Connected loads
• Communication interfaces
• Antennas
• Operating modes

For an ESA, the approval and testing configuration therefore needs to represent the conditions under which the equipment is intended to operate.

This is one reason why ECE R10 cannot always be treated like a generic standalone product EMC assessment.

3.7 What is the difference between a component and an ESA?

The terminology used in automotive compliance can sometimes create confusion.

Manufacturers may use terms such as:

• Component
• Module
• ECU
• Device
• Electronic unit
• Subsystem
• ESA

These terms do not necessarily have identical regulatory meanings.

For ECE R10 purposes, the important question is not simply what the manufacturer calls the product.

The important question is whether the equipment falls within the regulatory definition and scope applicable to an electrical/electronic sub-assembly.

This distinction matters because the regulatory status determines the applicable approval and testing route.

3.8 What about radio equipment?

Modern automotive products frequently contain radio functionality.

Examples include:

• Bluetooth
• Wi-Fi
• Cellular communication
• GNSS
• Short-range radio systems
• Keyless entry
• Remote control functions
• Vehicle-to-everything communication

The presence of a radio module does not eliminate the relevance of ECE R10.

Instead, several regulatory requirements may apply to the same product.

A wireless automotive product can therefore have to be considered from multiple perspectives, such as:

Radio compliance + EMC + vehicle type approval + other applicable automotive requirements

The exact combination depends on the product, installation and market.

This is an important distinction because manufacturers sometimes assume that radio approval or CE marking automatically covers the automotive EMC approval requirements.

It does not necessarily do so.

3.9 Integrated radio modules do not automatically determine the R10 status

Many automotive products contain pre-approved radio modules.

A manufacturer may therefore have an electronic assembly containing a radio module that already has its own radio approvals.

This can simplify certain aspects of radio compliance.

However, the host product still has to be considered as a complete system for the applicable requirements.

The integration of the module can introduce new EMC characteristics through:

• Power supply design
• PCB layout
• Antenna arrangement
• Grounding
• Shielding
• Cable configuration
• Enclosure design
• Additional electronics

A pre-approved radio module therefore does not automatically mean that the complete automotive assembly requires no additional EMC assessment.

The module approval and the host product’s compliance are separate considerations.

3.10 Vehicle systems and complete vehicle approval

At vehicle level, manufacturers may have a large number of electronic systems that contribute to the overall EMC behaviour.

The complete vehicle approval therefore considers the vehicle configuration as a whole.

This creates an important relationship between component-level and vehicle-level compliance.

An individual ESA may be assessed separately under the relevant provisions, while the vehicle manufacturer remains responsible for demonstrating compliance of the complete vehicle within the applicable type-approval framework.

Component approval and vehicle approval should therefore not be treated as interchangeable.

A component having an R10 approval does not mean that the complete vehicle automatically requires no further vehicle-level assessment.

Conversely, a vehicle manufacturer’s approval strategy may determine how individual components are handled within the overall vehicle type approval.

3.11 Different vehicle applications can affect the compliance strategy

The same electronic product may potentially be used in different vehicle applications.

For example, an electronic module could be installed in:

• Passenger vehicles
• Commercial vehicles
• Buses
• Special-purpose vehicles
• Trailers or other vehicle-related applications

The exact regulatory requirements depend on the applicable vehicle category and approval framework.

The manufacturer therefore needs to understand not only what the product is, but also where and how it will be used.

This becomes particularly important when the same product is intended to be sold to multiple vehicle manufacturers or integrated into multiple vehicle platforms.

3.12 Variants and different configurations

Automotive products frequently exist in several variants.

Differences can include:

• Hardware configuration
• PCB version
• Software version
• Power supply
• Communication interfaces
• Connector configuration
• Cable length
• Enclosure
• Antenna configuration
• Operating modes
• Vehicle installation

From a compliance perspective, these differences cannot simply be ignored.

The manufacturer needs to determine which variants are represented by the approval and whether a change remains within the approved configuration.

A poorly defined variant strategy can result in unnecessary testing or, more seriously, a configuration that is not adequately covered by the available compliance evidence.

3.13 When ECE R10 may not be the only applicable requirement

Even when ECE R10 clearly applies, it may only represent one part of the regulatory assessment.

Depending on the product, other requirements can relate to:

• Radio equipment
• Functional safety
• Cybersecurity
• Electrical safety
• Vehicle-specific functional requirements
• Environmental requirements
• Software-related requirements
• Type approval
• Conformity of production

ECE R10 should therefore be considered as one element within the overall automotive compliance architecture.

The correct approach is to identify the complete regulatory landscape first and then determine where R10 fits into it.

3.14 Why scope determination should come first

The biggest practical mistake is to start with the question:

“Which EMC tests should we book?”

before answering:

“What exactly is the product, where will it be installed, and which regulatory framework applies?”

The second question has to come first.

A proper scope assessment should establish:

1. What is the product?
2. Is it a vehicle or an ESA?
3. What vehicle category or application is relevant?
4. How is the product installed?
5. How is it connected electrically?
6. Which vehicle functions does it perform or influence?
7. Which radio functions are integrated?
8. Which product variants exist?
9. Which regulatory version applies?
10. Which approval route is appropriate?

Only after these questions have been answered can the appropriate test and approval strategy be developed.

3.15 The key takeaway

ECE R10 covers vehicles and relevant electrical/electronic sub-assemblies, but its applicability cannot be determined simply by asking whether a product is “automotive.”

The regulatory status depends on the product, its intended use, its installation, its electrical connections, its function and the applicable vehicle type-approval framework.

For manufacturers, this means that scope determination is the first compliance activity, not the laboratory test.

Before testing begins, the manufacturer should know:

What is being approved, why is R10 applicable, which configuration is covered, and which approval route is required?

Getting these questions right at the beginning can prevent unnecessary testing, reduce project risk and provide a much clearer basis for the subsequent R10 approval process.

Control the Scope. Control the Cost.

4. ECE R10 vs. CE EMC Compliance

One of the most common sources of confusion in automotive compliance is the relationship between ECE R10 and the EU EMC Directive.

Both address electromagnetic compatibility. Both deal with emissions and immunity. Both can involve laboratory testing.

However, they are not the same regulatory framework, and compliance with one does not automatically mean compliance with the other.

For manufacturers developing electrical or electronic products for automotive applications, understanding this distinction is essential.

4.1 Two different regulatory frameworks

The EMC Directive 2014/30/EU is European Union product legislation.

It establishes electromagnetic compatibility requirements for equipment placed on the EU market and forms part of the broader CE-marking framework.

ECE R10, in contrast, is a UNECE regulation within the vehicle type-approval system.

Its purpose is to establish uniform provisions for the approval of vehicles and relevant electrical/electronic equipment with regard to electromagnetic compatibility.

The two frameworks therefore have different regulatory foundations.

In simplified terms:

EMC Directive → EU product compliance

ECE R10 → UNECE vehicle type approval

This distinction is fundamental.

The fact that both frameworks address EMC does not make them interchangeable.

4.2 Similar engineering topic, different regulatory objective

From an engineering perspective, there is considerable overlap.

Both frameworks are concerned with questions such as:

• Does the equipment generate excessive electromagnetic emissions?
• Can the equipment withstand electromagnetic disturbances?
• Does the equipment continue to perform its intended function during immunity testing?

However, the regulatory objective is different.

The EMC Directive is designed to ensure that electrical and electronic equipment placed on the EU market does not cause unacceptable electromagnetic interference and has adequate immunity.

ECE R10 addresses electromagnetic compatibility within the vehicle type-approval environment.

This means that the vehicle context, installation conditions and type-approval process become important parts of the assessment.

Therefore, an automotive manufacturer should not simply take a generic EMC test plan and assume that it represents an R10 approval.

4.3 CE marking does not mean ECE R10 approval

A product may comply with the EMC Directive and carry a CE marking.

That does not automatically mean that the same product has an ECE R10 approval.

For example, an electronic device may have successfully completed:

• Radiated emissions testing
• Conducted emissions testing
• Radiated immunity testing
• Conducted immunity testing

under an applicable EU EMC compliance assessment.

Those test results may be technically useful.

However, they do not automatically create an R10 type approval.

The manufacturer must still determine whether the product falls under the relevant R10 provisions and, if so, which automotive approval and testing requirements apply.

The key distinction is:

CE marking demonstrates compliance with applicable EU legislation.

ECE R10 approval demonstrates compliance within the applicable UNECE vehicle type-approval framework.

4.4 ECE R10 is not simply an automotive version of the EMC Directive

It can be tempting to think of ECE R10 as the “automotive EMC Directive.”

That description is misleading.

ECE R10 has its own:

• Scope
• Definitions
• Approval procedure
• Technical requirements
• Test configurations
• Referenced standards
• Documentation requirements
• Approval markings
• Production conformity requirements
• Change and extension procedures

The applicable requirements must therefore be determined from the R10 framework itself.

A manufacturer should not construct an R10 compliance program simply by taking the requirements of the EMC Directive and adding the word “automotive.”

4.5 The test standards can also be different

Another reason for confusion is that both compliance routes use electromagnetic compatibility testing.

However, automotive EMC testing relies heavily on automotive-specific test methods and standards.

Depending on the applicable R10 requirements, testing can involve standards such as:

• CISPR 12
• CISPR 25
• ISO 11451
• ISO 11452
• ISO 7637

The EMC Directive, depending on the product and applicable harmonised standards, may instead involve standards from a different standards framework.

There can be technical overlap, but the applicable test methods, limits, configurations and acceptance criteria must be determined independently.

This is why a test performed for one regulatory framework should not automatically be treated as sufficient evidence for another.

4.6 The installation environment is particularly important

Automotive products are installed in a very different environment from many conventional electrical products.

An ESA may be connected to:

• Vehicle power supplies
• Ground systems
• Communication networks
• Long wiring harnesses
• Sensors
• Actuators
• Other electronic control units

Its physical location can also be important.

For example, an electronic unit installed close to an antenna, inverter or high-current power electronics may experience a significantly different electromagnetic environment from the same unit tested as a standalone product.

ECE R10 therefore places the product within the context of its intended automotive application.

This is one of the key reasons why a generic EMC assessment cannot automatically replace an R10 assessment.

4.7 What happens if a product already has CE EMC testing?

Existing EMC test data can still be valuable.

A manufacturer may already have test results from:

• EMC Directive testing
• Internal EMC development testing
• Other international EMC programs
• Customer-specific automotive testing

These results should not simply be discarded.

They can potentially support the engineering assessment and help identify areas that have already been evaluated.

However, their suitability for an R10 project must be assessed.

The relevant questions include:

• Was the same product configuration tested?
• Were the same operating modes used?
• Were the same cables and harnesses used?
• Were the same loads connected?
• Were the same frequencies and field strengths applied?
• Were the applicable R10 limits used?
• Was the test method equivalent?
• Is the test evidence acceptable within the approval process?

Only after these questions have been answered can existing test evidence be considered relevant to the R10 project.

4.8 Why “the product already passed EMC” is not enough

A manufacturer may approach an R10 project with the statement:

“The product already passed EMC testing.”

The correct response is:

Which EMC testing?

A successful test result is meaningful only in relation to:

• The applicable regulation
• The test method
• The test configuration
• The limits
• The operating conditions
• The product configuration
• The required acceptance criteria

A product can therefore pass one EMC assessment and still require additional testing for another regulatory framework.

This does not necessarily mean that the previous testing was useless.

It means that compliance evidence must always be evaluated in context.

4.9 ECE R10 approval is not simply an EMC test report

This distinction is particularly important.

A laboratory report documents technical test results.

An ECE R10 approval is part of a formal type-approval process.

The approval involves the relevant approval authority and technical service within the applicable UNECE framework.

Therefore, the following statements should not be treated as equivalent:

“The product has an EMC test report.”

and

“The product has an ECE R10 approval.”

The first describes technical evidence.

The second describes a regulatory approval status.

This difference becomes particularly important when a manufacturer communicates compliance to customers, vehicle manufacturers or authorities.

4.10 Can one test support both CE EMC and ECE R10?

Potentially, some technical test results may be useful for more than one regulatory purpose.

However, this should never be assumed automatically.

Whether existing evidence can be reused depends on the exact requirements and test conditions.

For example, two tests may both evaluate radiated emissions but use:

• Different measurement distances
• Different frequency ranges
• Different limits
• Different detector settings
• Different antenna arrangements
• Different equipment configurations

The fact that both tests are called “radiated emissions” does not make their results automatically interchangeable.

The same applies to immunity testing.

A structured comparison of the applicable requirements and test methods is therefore necessary before relying on existing evidence.

4.11 Why this distinction matters commercially

The difference between CE EMC compliance and ECE R10 can have a direct impact on project planning.

If a manufacturer assumes that existing CE EMC testing is automatically sufficient, the project may later discover that additional automotive testing is required.

This can result in:

• Additional laboratory costs
• Additional test samples
• Longer project lead times
• Retesting
• Documentation changes
• Approval delays

Conversely, a manufacturer that understands the relationship between the two frameworks can identify reusable evidence and avoid unnecessary duplication where technically and regulatorily possible.

The objective should therefore not be:

“Test everything again.”

Nor should it be:

“Reuse everything automatically.”

The objective should be:

“Determine exactly which existing evidence is valid for the intended approval.”

4.12 ECE R10 and CE marking can coexist

ECE R10 and CE marking are not mutually exclusive.

Depending on the product and market, a manufacturer may need to address both.

For example, an electronic product can have:

• CE-related obligations under applicable EU legislation
• ECE R10 requirements within a vehicle type-approval project
• Additional requirements arising from the vehicle application

The regulatory strategy therefore needs to identify which requirements apply to the specific product and market.

The presence of one compliance marking does not automatically eliminate the need to consider the other regulatory framework.

4.13 The practical question manufacturers should ask

Instead of asking:

“Do we need EMC or ECE R10?”

the manufacturer should ask:

“Which regulatory frameworks apply to this product, and what evidence is required under each one?”

This approach avoids treating different regulatory systems as competing alternatives.

A product can be subject to multiple regulatory requirements at the same time.

The compliance strategy should therefore map:

Product → Intended use → Market → Regulatory frameworks → Applicable requirements → Test evidence → Approval / Declaration

This provides a much clearer picture of what actually needs to be done.

4.14 Key takeaway

ECE R10 and CE EMC compliance deal with the same broad engineering discipline — electromagnetic compatibility — but they belong to different regulatory frameworks.

The EMC Directive is an EU product legislation framework.

ECE R10 is part of the UNECE vehicle type-approval framework.

Therefore:

CE EMC compliance does not automatically equal ECE R10 approval.

At the same time, existing EMC test evidence can potentially provide value in an R10 project if its applicability and equivalence are properly assessed.

For manufacturers, the important step is therefore not to assume that existing EMC evidence is either completely sufficient or completely irrelevant.

The correct approach is to scope the requirements first and then determine which existing evidence can be reused and which additional testing is required.

Control the Scope. Control the Cost.

ECE R10: Electromagnetic Compatibility Requirements for Vehicles and Automotive Components

Electromagnetic compatibility is a critical part of automotive compliance. Modern vehicles contain an increasing number of electronic control units, sensors, communication systems, charging systems and other electronic functions. These systems must operate reliably in an increasingly complex electromagnetic environment without causing unacceptable interference to other equipment.

For vehicles and certain electrical or electronic equipment intended for use in vehicles, one of the key regulatory frameworks is UN Regulation No. 10, commonly referred to as ECE R10 or UN R10.

ECE R10 establishes requirements for the electromagnetic compatibility of vehicles and relevant electrical/electronic equipment used in vehicles. Unlike a general EMC assessment for an electrical product, ECE R10 is part of the UN vehicle type-approval framework.

1. What is ECE R10?

ECE R10 is the UNECE regulation covering the electromagnetic compatibility (EMC) of vehicles and relevant electrical/electronic equipment.

Its official designation is:

UN Regulation No. 10 – Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility.

The regulation forms part of the vehicle regulations developed under the UNECE World Forum for Harmonization of Vehicle Regulations (WP.29).

The current regulatory framework has evolved through several series of amendments. UNECE currently lists Revision 6 and the subsequent 07 series of amendments for UN Regulation No. 10.

The purpose of R10 is essentially twofold:

1. The vehicle must not generate electromagnetic disturbances that could unacceptably affect other equipment.
2. The vehicle and relevant electrical/electronic systems must remain functional when exposed to defined electromagnetic disturbances.

In other words, R10 addresses both sides of EMC:

Emissions → Does the vehicle or equipment disturb its electromagnetic environment?

Immunity → Can the vehicle or equipment continue to function correctly in the presence of electromagnetic disturbances?

2. Why is ECE R10 important in automotive applications?

The amount of electronics in modern vehicles has increased dramatically.

A vehicle may contain:

• Engine and powertrain control units
• Battery management systems
• Inverters and converters
• ADAS systems
• Radar sensors
• Cameras
• Infotainment systems
• GNSS and communication systems
• Bluetooth and Wi-Fi systems
• Charging equipment
• Electric steering and braking systems
• Lighting control systems
• Body control modules
• Sensors and actuators

These systems are not electrically isolated from one another.

A disturbance generated by one system can potentially affect another system. Conversely, an electronic control unit may malfunction if it is exposed to sufficiently strong electromagnetic fields or conducted disturbances.

This makes EMC a functional safety and reliability consideration as well as a regulatory requirement.

ECE R10 therefore does not simply ask whether an electronic product “passes an EMC test.”

It evaluates whether the vehicle or relevant equipment is sufficiently compatible with its electromagnetic environment under defined automotive conditions.

3. What products and vehicles are covered?

The scope of UN R10 covers vehicles and relevant electrical/electronic equipment intended for use in vehicles.

The regulation addresses vehicles in the categories covered by the vehicle type-approval framework and electrical/electronic sub-assemblies (ESAs) intended for installation in vehicles.

An ESA can include an electrical or electronic unit that is supplied as a separate component and intended to perform a function within the vehicle.

Examples can include:

• Electronic control units
• Automotive chargers
• Lighting electronics
• Infotainment equipment
• Sensors
• Electronic modules
• Power electronics
• Communication-related equipment
• Control systems
• Other vehicle-mounted electronic assemblies

However, an important distinction is necessary:

Not every electronic product used in or around a vehicle automatically requires a separate ECE R10 type approval.

The actual regulatory obligation depends on the vehicle type-approval framework, the role of the equipment, how it is installed and whether the equipment falls within the applicable regulatory requirements.

For example, EU vehicle type-approval legislation contains specific provisions concerning electrical/electronic sub-assemblies and their relationship with UN Regulation No. 10.

This is why simply classifying a product as an “automotive electronic device” is not sufficient to determine whether an R10 approval is required.

4. ECE R10 vs. CE-EMV-Konformität

Eine der häufigsten Verwechslungen im Automotive-Bereich besteht in der Annahme, dass ein Automotive-Produkt einfach nach dem normalen europäischen EMV-Rahmen bewertet werden kann und damit automatisch ECE R10 erfüllt.

Das ist nicht zwingend der Fall.

Die EMV-Richtlinie 2014/30/EU und UN Regulation No. 10 (ECE R10) sind unterschiedliche regulatorische Rahmenwerke.

Die EMV-Richtlinie ist europäische Produktgesetzgebung für elektrische und elektronische Geräte.

ECE R10 ist dagegen Bestandteil des UN-Fahrzeug-Typgenehmigungssystems.

Das zugrunde liegende technische Thema ist zwar in beiden Fällen die elektromagnetische Verträglichkeit – also Störaussendungen und Störfestigkeit –, der regulatorische Kontext, das Genehmigungsverfahren, die Dokumentation und die anzuwendenden Prüfanforderungen unterscheiden sich jedoch.

Daher gilt:

CE-EMV-Konformität ≠ automatisch ECE-R10-Typgenehmigung

Und ebenso:

ECE-R10-Genehmigung ≠ einfach nur ein weiterer CE-EMV-Prüfbericht

Welcher Compliance-Weg erforderlich ist, muss anhand der vorgesehenen Anwendung des Produkts und des für das Fahrzeug bzw. die Ausrüstung geltenden regulatorischen Rahmens bestimmt werden.

4.1 Zwei unterschiedliche regulatorische Systeme

Die EMV-Richtlinie 2014/30/EU ist EU-Produktgesetzgebung. Sie legt Anforderungen an die elektromagnetische Verträglichkeit von Geräten fest, die in den Anwendungsbereich der Richtlinie fallen und auf dem EU-Markt bereitgestellt werden.

ECE R10 verfolgt dagegen einen anderen Ansatz. Die Regelung ist Bestandteil des UNECE-Typgenehmigungsrahmens für Fahrzeuge.

Vereinfacht dargestellt:

EMV-Richtlinie → EU-Produktkonformität

ECE R10 → UNECE-Fahrzeug-Typgenehmigung

Beide Systeme beschäftigen sich mit EMV, aber sie erfüllen unterschiedliche regulatorische Funktionen.

4.2 Ähnliches technisches Thema, unterschiedlicher regulatorischer Zweck

Aus technischer Sicht gibt es deutliche Überschneidungen.

In beiden Fällen geht es beispielsweise um Fragen wie:

• Erzeugt das Produkt zu hohe elektromagnetische Störungen?
• Kann das Produkt elektromagnetischen Störungen ausreichend widerstehen?
• Bleibt das Produkt während definierter Störfestigkeitsprüfungen funktionsfähig?

Der regulatorische Zweck ist jedoch unterschiedlich.

Die EMV-Richtlinie soll sicherstellen, dass elektrische und elektronische Geräte keine unzulässigen elektromagnetischen Störungen verursachen und über eine ausreichende Störfestigkeit verfügen.

ECE R10 betrachtet die elektromagnetische Verträglichkeit dagegen innerhalb des Fahrzeug-Typgenehmigungsumfelds.

Damit werden Fahrzeugkontext, Einbaubedingungen und Typgenehmigungsprozess zu wichtigen Bestandteilen der Bewertung.

Ein Automotive-Hersteller sollte deshalb nicht einfach einen allgemeinen EMV-Prüfplan nehmen und davon ausgehen, dass dieser automatisch einer R10-Genehmigung entspricht.

4.3 CE-Kennzeichnung bedeutet nicht automatisch ECE-R10-Genehmigung

Ein Produkt kann die Anforderungen der EMV-Richtlinie erfüllen und eine CE-Kennzeichnung tragen.

Das bedeutet nicht automatisch, dass für dasselbe Produkt eine ECE-R10-Genehmigung vorliegt.

Ein elektronisches Gerät kann beispielsweise erfolgreich Prüfungen durchgeführt haben wie:

• gestrahlte Störaussendungen;
• leitungsgebundene Störaussendungen;
• gestrahlte Störfestigkeit;
• leitungsgebundene Störfestigkeit.

Solche Prüfergebnisse können technisch sehr wertvoll sein.

Sie stellen jedoch nicht automatisch eine R10-Typgenehmigung dar.

Der Hersteller muss weiterhin prüfen, ob das Produkt unter die relevanten R10-Bestimmungen fällt und – falls dies der Fall ist – welche Automotive-Genehmigungs- und Prüfanforderungen gelten.

Die entscheidende Unterscheidung lautet:

Die CE-Kennzeichnung weist die Konformität mit den jeweils anwendbaren EU-Rechtsvorschriften aus.

Die ECE-R10-Genehmigung weist die Konformität innerhalb des anwendbaren UNECE-Fahrzeug-Typgenehmigungsrahmens nach.

4.4 ECE R10 ist nicht einfach die „Automotive-Version“ der EMV-Richtlinie

Es ist verlockend, ECE R10 als eine Art „Automotive-EMV-Richtlinie“ zu betrachten.

Diese Vereinfachung ist jedoch irreführend.

ECE R10 besitzt eigene:

• Anwendungsbereiche
• Definitionen
• Genehmigungsverfahren
• technische Anforderungen
• Prüfkonfigurationen
• referenzierte Normen
• Dokumentationsanforderungen
• Genehmigungskennzeichnungen
• Anforderungen an die Konformität der Produktion
• Verfahren für Änderungen und Erweiterungen

Die anwendbaren Anforderungen müssen deshalb aus dem R10-Regelwerk selbst bestimmt werden.

Ein Hersteller sollte ein R10-Compliance-Programm nicht einfach erstellen, indem er die Anforderungen der EMV-Richtlinie übernimmt und lediglich den Begriff „Automotive“ ergänzt.

4.5 Auch die Prüfstandards können unterschiedlich sein

Ein weiterer Grund für Verwechslungen besteht darin, dass beide Compliance-Wege EMV-Prüfungen verwenden.

Im Automotive-Bereich spielen jedoch spezifische Prüfverfahren und Automotive-EMV-Normen eine wichtige Rolle.

Abhängig von den geltenden R10-Anforderungen können unter anderem Standards wie folgende relevant sein:

• CISPR 12
• CISPR 25
• ISO 11451
• ISO 11452
• ISO 7637

Die EMV-Richtlinie kann abhängig vom Produkt und den anzuwendenden harmonisierten Normen dagegen auf einen anderen Normenrahmen zurückgreifen.

Es kann technische Überschneidungen geben, aber Prüfverfahren, Grenzwerte, Konfigurationen und Akzeptanzkriterien müssen jeweils eigenständig bestimmt werden.

Deshalb sollte eine Prüfung, die für einen regulatorischen Rahmen durchgeführt wurde, nicht automatisch als ausreichender Nachweis für einen anderen Rahmen behandelt werden.

4.6 Die Einbauumgebung ist besonders wichtig

Automotive-Produkte werden in einer völlig anderen Umgebung eingesetzt als viele herkömmliche elektrische Produkte.

Eine ESA kann beispielsweise verbunden sein mit:

• der Fahrzeugstromversorgung;
• dem Masse- bzw. Ground-System;
• Kommunikationsnetzwerken;
• langen Kabelbäumen;
• Sensoren;
• Aktoren;
• weiteren elektronischen Steuergeräten.

Auch der physische Einbauort kann eine Rolle spielen.

Ein elektronisches Gerät, das beispielsweise in unmittelbarer Nähe einer Antenne, eines Inverters oder einer leistungsstarken Leistungselektronik installiert wird, kann einer deutlich anderen elektromagnetischen Umgebung ausgesetzt sein als dasselbe Gerät bei einer isolierten Produktprüfung.

ECE R10 ordnet das Produkt deshalb in den Kontext seiner vorgesehenen Automotive-Anwendung ein.

Das ist einer der wesentlichen Gründe, warum eine allgemeine EMV-Bewertung nicht automatisch eine R10-Bewertung ersetzt.

4.7 Was passiert, wenn bereits CE-EMV-Prüfungen vorliegen?

Vorhandene EMV-Prüfdaten können für ein R10-Projekt durchaus wertvoll sein.

Ein Hersteller kann beispielsweise bereits Ergebnisse aus folgenden Aktivitäten besitzen:

• Prüfungen nach der EMV-Richtlinie;
• internen EMV-Entwicklungsprüfungen;
• internationalen EMV-Programmen;
• kundenspezifischen Automotive-EMV-Prüfungen.

Solche Ergebnisse sollten nicht automatisch verworfen werden.

Sie können die technische Bewertung unterstützen und dabei helfen, bereits untersuchte Bereiche zu identifizieren.

Ihre Eignung für ein R10-Projekt muss jedoch geprüft werden.

Dabei sind unter anderem folgende Fragen relevant:

• Wurde dieselbe Produktkonfiguration geprüft?
• Wurden dieselben Betriebsmodi verwendet?
• Wurden dieselben Kabel und Kabelbäume eingesetzt?
• Waren dieselben Lasten angeschlossen?
• Wurden dieselben Frequenzbereiche und Feldstärken verwendet?
• Wurden die relevanten R10-Grenzwerte angewendet?
• War das Prüfverfahren gleichwertig?
• Ist der vorhandene Nachweis innerhalb des Genehmigungsprozesses akzeptabel?

Erst wenn diese Fragen beantwortet sind, kann beurteilt werden, welchen Wert vorhandene Prüfnachweise für das R10-Projekt tatsächlich haben.

4.8 Warum „Das Produkt hat EMV bereits bestanden“ nicht ausreicht

Ein Hersteller kann mit folgender Aussage in ein R10-Projekt starten:

„Das Produkt hat die EMV-Prüfung bereits bestanden.“

Die richtige Anschlussfrage lautet:

Welche EMV-Prüfung?

Ein Prüfergebnis ist nur im Zusammenhang mit folgenden Faktoren aussagekräftig:

• der anwendbaren Regelung;
• dem Prüfverfahren;
• der Prüfkonfiguration;
• den Grenzwerten;
• den Betriebsbedingungen;
• der Produktkonfiguration;
• den geforderten Akzeptanzkriterien.

Ein Produkt kann daher eine EMV-Bewertung erfolgreich bestehen und trotzdem zusätzliche Prüfungen für einen anderen regulatorischen Rahmen benötigen.

Das bedeutet nicht, dass die vorherige Prüfung wertlos war.

Es bedeutet, dass Konformitätsnachweise immer im jeweiligen regulatorischen Kontext bewertet werden müssen.

4.9 Eine ECE-R10-Genehmigung ist nicht einfach ein EMV-Prüfbericht

Diese Unterscheidung ist besonders wichtig.

Ein Laborbericht dokumentiert technische Prüfergebnisse.

Eine ECE-R10-Genehmigung ist dagegen Bestandteil eines formalen Typgenehmigungsverfahrens.

An diesem Verfahren sind die zuständige Genehmigungsbehörde und der entsprechende Technische Dienst innerhalb des UNECE-Rahmens beteiligt.

Deshalb sollten folgende Aussagen nicht als gleichwertig betrachtet werden:

„Das Produkt verfügt über einen EMV-Prüfbericht.“

und

„Das Produkt verfügt über eine ECE-R10-Genehmigung.“

Die erste Aussage beschreibt technische Nachweise.

Die zweite beschreibt einen regulatorischen Genehmigungsstatus.

Dieser Unterschied wird insbesondere dann relevant, wenn ein Hersteller den Compliance-Status gegenüber Kunden, Fahrzeugherstellern oder Behörden kommuniziert.

4.10 Kann eine Prüfung für CE-EMV und ECE R10 gleichzeitig genutzt werden?

Unter bestimmten Umständen können technische Prüfergebnisse für mehr als einen regulatorischen Zweck relevant sein.

Das darf jedoch nicht automatisch angenommen werden.

Ob vorhandene Nachweise wiederverwendet werden können, hängt von den konkreten Anforderungen und Prüfbedingungen ab.

Zwei Prüfungen können beispielsweise beide gestrahlte Störaussendungen untersuchen, aber unterschiedliche:

• Messabstände;
• Frequenzbereiche;
• Grenzwerte;
• Detektoreinstellungen;
• Antennenanordnungen;
• Geräte- oder Systemkonfigurationen

verwenden.

Die Tatsache, dass beide Prüfungen „gestrahlte Störaussendungen“ heißen, macht ihre Ergebnisse daher nicht automatisch austauschbar.

Dasselbe gilt für Störfestigkeitsprüfungen.

Vor einer Wiederverwendung vorhandener Nachweise ist deshalb ein strukturierter Vergleich der geltenden Anforderungen und Prüfverfahren erforderlich.

4.11 Warum die Unterscheidung kommerziell relevant ist

Der Unterschied zwischen CE-EMV-Konformität und ECE R10 kann direkte Auswirkungen auf die Projektplanung haben.

Wenn ein Hersteller davon ausgeht, dass vorhandene CE-EMV-Prüfungen automatisch ausreichen, kann später festgestellt werden, dass zusätzliche Automotive-Prüfungen erforderlich sind.

Das kann zu Folgendem führen:

• zusätzlichen Laborkosten;
• zusätzlichen Prüfmustern;
• längeren Projektlaufzeiten;
• Wiederholungsprüfungen;
• Änderungen an der Dokumentation;
• Verzögerungen bei der Genehmigung.

Umgekehrt kann ein Hersteller, der die Beziehung zwischen den beiden Rahmenwerken versteht, vorhandene Nachweise gezielt bewerten und unnötige Doppelprüfungen vermeiden, sofern dies technisch und regulatorisch möglich ist.

Das Ziel sollte daher weder sein:

„Alles noch einmal prüfen.“

noch:

„Alles automatisch wiederverwenden.“

Das Ziel sollte sein:

„Genau bestimmen, welche vorhandenen Nachweise für die geplante Genehmigung gültig und nutzbar sind.“

4.12 ECE R10 und CE-Kennzeichnung können nebeneinander bestehen

ECE R10 und die CE-Kennzeichnung schließen sich nicht gegenseitig aus.

Je nach Produkt und Zielmarkt können beide regulatorischen Themen relevant sein.

Ein elektronisches Produkt kann beispielsweise gleichzeitig folgende Anforderungen berücksichtigen müssen:

• CE-relevante Verpflichtungen aus anwendbarer EU-Gesetzgebung;
• ECE-R10-Anforderungen innerhalb eines Fahrzeug-Typgenehmigungsprojekts;
• zusätzliche Anforderungen aus der konkreten Fahrzeuganwendung.

Die regulatorische Strategie muss deshalb für das konkrete Produkt und den konkreten Markt bestimmen, welche Anforderungen tatsächlich gelten.

Das Vorhandensein einer Compliance-Kennzeichnung beseitigt nicht automatisch die Notwendigkeit, das jeweils andere regulatorische System zu betrachten.

4.13 Die praktische Frage, die Hersteller stellen sollten

Statt zu fragen:

„Brauchen wir EMV oder ECE R10?“

sollte der Hersteller fragen:

„Welche regulatorischen Rahmenwerke gelten für dieses Produkt, und welche Nachweise werden innerhalb jedes dieser Rahmenwerke benötigt?“

Damit werden die verschiedenen regulatorischen Systeme nicht fälschlicherweise als Alternativen behandelt.

Ein Produkt kann gleichzeitig mehreren regulatorischen Anforderungen unterliegen.

Die Compliance-Strategie sollte deshalb möglichst klar abbilden:

Produkt → Vorgesehene Verwendung → Markt → Regulatorische Rahmenwerke → Anwendbare Anforderungen → Prüfnachweise → Genehmigung / Erklärung

Dieser Ansatz schafft ein deutlich klareres Bild davon, was tatsächlich erforderlich ist.

4.14 Fazit

ECE R10 und die CE-EMV-Konformität behandeln dasselbe übergeordnete technische Thema – die elektromagnetische Verträglichkeit –, gehören jedoch zu unterschiedlichen regulatorischen Systemen.

Die EMV-Richtlinie ist ein EU-Produktrechtsrahmen.

ECE R10 ist Bestandteil des UNECE-Fahrzeug-Typgenehmigungsrahmens.

Daher gilt:

CE-EMV-Konformität bedeutet nicht automatisch ECE-R10-Genehmigung.

Gleichzeitig können vorhandene EMV-Prüfnachweise für ein R10-Projekt wertvoll sein, wenn ihre Anwendbarkeit und Gleichwertigkeit korrekt bewertet werden.

Für Hersteller besteht der entscheidende Schritt deshalb nicht darin, vorhandene EMV-Nachweise pauschal als ausreichend oder als irrelevant einzustufen.

Der richtige Ansatz besteht darin, zuerst den regulatorischen Umfang zu bestimmen und anschließend systematisch zu prüfen, welche vorhandenen Nachweise wiederverwendet werden können und welche zusätzlichen Prüfungen erforderlich sind.

Control the Scope. Control the Cost.

5. What Does ECE R10 Require?

ECE R10 is an electromagnetic compatibility regulation, but it is not a single EMC test. The applicable requirements depend on whether the subject of approval is a complete vehicle or an electrical/electronic sub-assembly (ESA), as well as on the applicable version of the regulation and the specific configuration being assessed.

At a high level, the regulation addresses both sides of electromagnetic compatibility:

Emissions → The vehicle or equipment must not generate unacceptable electromagnetic disturbances.

Immunity → The vehicle or equipment must continue to perform its intended functions when exposed to defined electromagnetic disturbances.

The individual requirements are implemented through defined test methods, limits, operating conditions and performance criteria. The exact test matrix therefore has to be established from the applicable R10 provisions rather than from a generic automotive EMC checklist.

5.1 Emissions and immunity are both part of the assessment

An automotive EMC assessment cannot be reduced to checking whether the product produces interference.

There are two fundamental questions:

1. Does the product or vehicle disturb its electromagnetic environment?
2. Can the product or vehicle tolerate electromagnetic disturbances without unacceptable loss of function?

The first question leads to emission testing. The second leads to immunity testing.

Both are important because a product can have good emission performance and still be vulnerable to external electromagnetic fields or conducted disturbances.

Likewise, a product can be highly immune but generate unacceptable interference to other systems.

ECE R10 therefore treats electromagnetic compatibility as a two-sided requirement.

5.2 Radiated emissions

Radiated emissions are electromagnetic disturbances that are emitted through the surrounding electromagnetic field rather than being transmitted only through an electrical connection.

For automotive systems, these emissions can originate from many sources, including:

• switching power supplies;
• microprocessors and digital electronics;
• DC/DC converters;
• inverters and power electronics;
• high-speed communication interfaces;
• motors and actuators;
• charging systems; and
• other switching or oscillating circuits.

The purpose of radiated-emission testing is to determine whether the vehicle or equipment remains below the applicable limits under the defined test conditions.

The exact limits, frequency ranges, measurement arrangements and applicable test methods depend on the subject of approval and the relevant provisions of R10.

This is why simply stating that a product needs a “radiated emissions test” is not yet a complete test scope.

The manufacturer also needs to know which R10 requirement, which configuration and which test method are applicable.

5.3 Conducted emissions

Not all electromagnetic disturbances are radiated directly into the environment.

Disturbances can also propagate through electrical connections, particularly through vehicle power and wiring systems.

Conducted disturbances can be generated by switching electronics, converters, motors, chargers and other electrical systems. Once coupled into a wiring harness, they can potentially reach other electronic systems in the vehicle.

The applicable R10 requirements therefore also address conducted disturbances under defined conditions.

This is one reason why the test configuration matters so much in automotive EMC.

A cable is not simply an accessory to the test setup. Depending on the equipment and the applicable test, the wiring can form part of the electrical path through which disturbances are generated, coupled or measured.

5.4 Radiated immunity

Radiated immunity testing addresses the opposite direction of the EMC problem.

The equipment is exposed to defined electromagnetic fields to determine whether it continues to operate as intended.

This is particularly important in vehicles because electronic systems can be exposed to electromagnetic energy from:

• radio transmitters;
• mobile communication systems;
• vehicle communication equipment;
• other electronic systems;
• charging infrastructure; and
• electromagnetic sources outside the vehicle.

The purpose is not simply to determine whether the electronics remain powered.

The relevant question is whether the intended functions and defined performance criteria remain within the acceptable limits during the disturbance.

For an automotive control unit, for example, it may be necessary to monitor specific outputs, communication functions, actuator states or other defined functions during the immunity test.

This makes the definition of the equipment’s operating modes and critical functions an important part of the R10 test scope.

5.5 Conducted immunity

Electromagnetic disturbances can also enter an electronic system through its electrical connections.

Conducted immunity testing evaluates the ability of the equipment to withstand specified disturbances coupled onto relevant cables or supply connections.

In an automotive environment, this is particularly relevant because electronic systems share electrical infrastructure and are connected through extensive wiring harnesses.

The test setup therefore has to reproduce the relevant electrical interfaces and operating conditions defined by the applicable test method.

As with radiated immunity, the assessment is not simply about whether the product continues to receive power.

The manufacturer must determine which functions need to remain operational and how degradation or malfunction is classified under the applicable requirements.

5.6 Transient disturbances

Automotive electrical systems are exposed to transient disturbances that can arise from switching events, changes in electrical loads and interactions within the vehicle electrical network.

These disturbances can be particularly relevant for equipment connected to the vehicle’s power supply or other electrical interfaces.

The ISO 7637 series is one of the important automotive standards associated with electrical transient phenomena and is referenced within the automotive EMC testing framework.

Depending on the applicable R10 requirements and the type of equipment, the assessment can therefore include tests designed to evaluate the response of the equipment to specified transient disturbances.

The exact pulse types, test levels, coupling arrangements and acceptance criteria must be determined from the applicable requirements. They should not be inferred simply from the fact that the product is automotive.

5.7 Vehicle-level and ESA-level requirements are different

One of the most important points when defining an R10 test program is the distinction between vehicle-level testing and ESA-level testing.

A complete vehicle is assessed as an integrated system.

An ESA is assessed as an individual electrical/electronic unit under defined conditions representative of its intended use.

This means that the test matrix cannot be copied unchanged from one approval level to the other.

The applicable R10 provisions define different test approaches, configurations and referenced methods for vehicles and ESAs.

For example, the ISO 11451 series is relevant to vehicle-level immunity testing, while the ISO 11452 series is used for various component-level automotive immunity methods.

The distinction is therefore fundamental when preparing a laboratory quotation or building a test plan.

5.8 Functional performance during immunity testing

Automotive EMC immunity testing is closely connected to the actual function of the equipment.

The manufacturer needs to know what the product is supposed to do while the disturbance is being applied.

Depending on the product, this can involve monitoring:

• control outputs;
• sensor values;
• actuator states;
• communication links;
• diagnostic functions;
• displays;
• alarms;
• charging functions; or
• other safety- or performance-related functions.

The applicable performance criteria determine what constitutes an acceptable response.

This is why a good R10 test plan must contain more than a list of frequencies and field strengths. It also needs a clear definition of the operating condition and function to be monitored.

5.9 The test configuration can change the result

Automotive EMC results are strongly influenced by the test configuration.

Relevant parameters can include:

• cable type and length;
• harness arrangement;
• power supply configuration;
• load conditions;
• grounding and bonding;
• shielding;
• connectors;
• auxiliary equipment;
• software mode;
• communication activity; and
• physical installation.

A product that passes in one configuration cannot automatically be assumed to pass in another.

This is especially important for products that are installed in multiple vehicle platforms or offered in several hardware and software variants.

The configuration used to demonstrate compliance therefore needs to be clearly defined and controlled.

5.10 The referenced standards matter

ECE R10 works together with a number of automotive EMC standards and test methods rather than replacing them with one universal laboratory procedure.

Depending on the applicable requirement, relevant references can include:

• CISPR 12 for vehicle-level radio disturbance characteristics;
• CISPR 25 for the protection of receivers used on board vehicles against disturbances from components and systems;
• ISO 11451 series for vehicle immunity testing;
• ISO 11452 series for component-level immunity testing; and
• ISO 7637 series for electrical transient phenomena on supply and signal lines.

The exact standard, edition and test method must always be checked against the applicable R10 version and the specific approval scope.

This is particularly important because UN Regulation No. 10 continues to evolve. UNECE working groups have been developing and updating the 07 series of amendments and related supplements.

5.11 Why the applicable edition cannot be ignored

A common mistake is to define the test program by saying only:

“Test according to ECE R10.”

That statement is incomplete for a real project.

The manufacturer and the technical service need to establish which regulatory version and transitional provisions apply to the approval.

This can affect:

• applicable test methods;
• referenced standards;
• limits;
• test configurations;
• documentation;
• approval timing; and
• whether a previous approval can continue to be used without modification.

The regulatory status of R10 should therefore be checked when the project is scoped, not only when the laboratory test is booked.

5.12 A test list is not yet a test scope

It is easy to create a superficial R10 test list:

Radiated emissions + conducted emissions + radiated immunity + conducted immunity + transients.

But such a list is not enough to obtain a reliable project estimate.

A useful R10 test scope should additionally identify:

• the approval object;
• vehicle or ESA level;
• product variants;
• operating modes;
• relevant interfaces;
• cable and harness configuration;
• loads;
• functional performance criteria;
• applicable standards and editions;
• required samples;
• documentation requirements; and
• the approval route.

Only then can a laboratory provide a meaningful quotation and the manufacturer understand what the project actually requires.

5.13 What happens if a test fails?

A failed EMC test does not automatically mean that the entire product must be redesigned.

The first step should be to understand the failure mechanism.

Depending on the failure, corrective actions can include:

• filtering;
• shielding;
• grounding changes;
• PCB layout changes;
• cable routing changes;
• software changes;
• component changes;
• enclosure modifications; or
• changes to the installation configuration.

After a modification, the impact on the remaining test program and on any existing evidence must be assessed.

This is another reason why early EMC scoping and pre-compliance work can be valuable: problems discovered before formal approval testing are generally easier to address than failures discovered after the complete approval configuration has been submitted to the formal test process.

5.14 ECE R10 testing is about the complete compliance picture

The individual EMC tests should not be viewed as isolated laboratory events.

They are elements of a larger chain:

Product → Configuration → Applicable R10 requirements → Test methods → Test conditions → Functional criteria → Test evidence → Type approval

If one of these elements is poorly defined, the resulting test program can become unnecessarily expensive or incomplete.

The goal is therefore not simply to perform as many tests as possible.

The goal is to perform the right tests, under the right conditions, against the right requirements, for the right configuration.

5.15 Key takeaway

ECE R10 does not prescribe one generic EMC test for every automotive product.

The regulation covers a combination of emission and immunity requirements, with the exact test program depending on the approval object, product configuration, applicable R10 provisions and referenced test standards.

For manufacturers, the most important step is therefore to define the scope before laboratory testing begins.

The relevant questions are:

What is being approved?

Which R10 requirements apply?

Which test methods and standards are required?

Which configuration and operating modes must be tested?

Which functions must remain operational during immunity testing?

6. Vehicle-Level vs. ESA-Level Approval

One of the most important distinctions in an ECE R10 project is whether the approval concerns a complete vehicle or an electrical/electronic sub-assembly (ESA).

Although both are covered within the same UN Regulation No. 10 framework, the regulatory context, test approach and practical scope can be different.

Understanding this distinction is essential before defining a test plan or requesting a laboratory quotation.

6.1 Complete vehicle approval

At vehicle level, the vehicle is assessed as an integrated system.

This means that the EMC performance is considered in the context of the complete vehicle configuration, including its:

• Electronic control units
• Wiring harnesses
• Power distribution
• Sensors
• Actuators
• Communication systems
• Lighting systems
• Infotainment
• Charging systems
• Radio equipment
• Other relevant electrical and electronic systems

The objective is to demonstrate that the vehicle as a whole meets the applicable electromagnetic compatibility requirements.

This is fundamentally different from testing one electronic component in isolation.

A vehicle contains many potential sources of electromagnetic emissions and many systems that may be susceptible to electromagnetic disturbances.

The vehicle-level assessment therefore considers the interaction of these systems within the vehicle architecture.

6.2 Electrical/electronic sub-assembly approval

An Electrical/Electronic Sub-Assembly (ESA) is an electrical or electronic unit intended for installation in a vehicle.

Examples can include:

• Electronic control units
• Sensors
• Lighting modules
• Power electronics
• Charging equipment
• Communication-related equipment
• Electronic control modules
• Other vehicle-mounted electronic assemblies

An ESA can be assessed separately under the applicable provisions of UN R10.

This allows manufacturers of components and systems to establish compliance for equipment that is supplied for integration into vehicles.

However, ESA approval does not mean that the equipment can be treated as completely independent from its intended automotive environment.

The relevant electrical connections, wiring, operating modes and installation conditions remain important.

6.3 Why the distinction matters

The difference between vehicle-level and ESA-level approval directly affects the test strategy.

A complete vehicle and an individual ESA are not tested in exactly the same way.

The test environment, configuration, monitoring and applicable test methods can differ.

For example, vehicle-level immunity testing can involve methods from the ISO 11451 series, while ESA-level testing can involve methods from the ISO 11452 series, depending on the applicable R10 requirements.

Therefore, a manufacturer should not take a vehicle-level test plan and simply apply it to a component.

Likewise, successful ESA testing does not automatically mean that the complete vehicle has been demonstrated to comply in every respect.

6.4 Vehicle-level testing considers the complete system

A complete vehicle can contain hundreds of electrical and electronic functions.

During vehicle-level EMC assessment, the vehicle therefore has to be operated in appropriate configurations that represent its intended functionality.

Depending on the vehicle, this can involve operating:

• The propulsion system
• Charging functions
• Communication systems
• Lighting
• Infotainment
• Driver assistance systems
• Electrical auxiliaries
• Other relevant vehicle functions

The objective is to ensure that relevant functions remain within the applicable performance criteria while the vehicle is exposed to defined electromagnetic conditions.

At the same time, the vehicle’s emissions must remain within the applicable limits.

This makes vehicle-level testing a system-level assessment rather than simply a collection of component tests.

6.5 ESA testing focuses on the individual equipment

ESA testing takes a different approach.

The equipment is evaluated as an individual unit under a defined test configuration.

The manufacturer and technical service need to establish how the ESA is intended to operate and which interfaces are relevant.

The configuration can include:

• Power supply
• Ground connections
• Wiring harnesses
• Loads
• Communication interfaces
• Sensors
• Actuators
• Auxiliary equipment

The ESA is then operated in defined modes while the applicable emissions and immunity requirements are assessed.

The objective is to demonstrate that the equipment itself meets the relevant R10 requirements under the specified conditions.

6.6 The vehicle installation remains important

Testing an ESA separately does not eliminate the importance of its intended installation.

The electromagnetic behaviour of an electronic unit can depend significantly on how it is installed.

Relevant factors can include:

• Cable length
• Cable routing
• Shielding
• Grounding
• Connector configuration
• Supply voltage
• Connected loads
• Physical location
• Distance from other electronic systems
• Communication interfaces

A component that performs well in one configuration may behave differently when installed in another.

This is why the approved configuration and intended installation conditions must be clearly defined.

6.7 ESA approval can simplify vehicle integration — but does not replace vehicle approval

For component manufacturers, obtaining an ESA approval can provide an important compliance basis when supplying equipment to vehicle manufacturers.

It can demonstrate that the equipment has been assessed against the applicable R10 requirements in its defined configuration.

However, it should not be interpreted as a universal approval of every possible vehicle installation.

The vehicle manufacturer still has to consider the complete vehicle configuration and the requirements applicable to the vehicle type approval.

This creates an important distinction:

ESA approval → compliance of the approved electrical/electronic equipment under the defined conditions

Vehicle approval → compliance of the complete vehicle within the applicable type-approval framework

The two levels complement each other rather than replacing one another.

6.8 Different configurations can require additional assessment

A manufacturer may have one ESA that is supplied in several configurations.

For example:

• Different hardware versions
• Different software versions
• Different connectors
• Different cable lengths
• Different power ratings
• Different communication interfaces
• Different enclosure configurations

The manufacturer cannot automatically assume that all variants are covered by one approval.

The impact of each variant needs to be assessed.

Depending on the nature of the change, the result may be:

1. The existing approval remains applicable.
2. Additional technical evidence is required.
3. Additional testing is required.
4. An extension or update of the approval is required.

This is why configuration management is an important part of an R10 project.

6.9 The role of the vehicle manufacturer

The vehicle manufacturer has an important role when an ESA is integrated into a vehicle.

Even where the ESA has been separately approved, the vehicle manufacturer needs to understand:

• Which version of the ESA was approved
• Which installation conditions were evaluated
• Which wiring configuration was used
• Which operating conditions were covered
• Which limitations apply
• Whether the production configuration corresponds to the approved configuration

This information can become part of the broader vehicle type-approval strategy.

The integration of an ESA is therefore not simply a matter of installing a component with an E-mark.

The vehicle architecture and approval configuration must remain consistent with the applicable requirements.

6.10 Component approval versus system integration

A common misunderstanding is:

“If every component is R10 approved, the vehicle must automatically be R10 compliant.”

That conclusion is too simplistic.

Individual component approvals can provide valuable evidence, but the vehicle is still a system.

When components are integrated, new interactions can arise through:

• Wiring
• Grounding
• Power distribution
• Communication networks
• Antenna systems
• Physical proximity
• Simultaneous operation
• Software interactions

The complete vehicle can therefore exhibit electromagnetic behaviour that cannot always be predicted simply by looking at the individual component approvals.

This is why vehicle-level compliance remains relevant.

6.11 Vehicle-level and ESA-level testing should be planned together

For complex vehicle programs, the most effective approach is often to consider component and vehicle compliance together.

A manufacturer can ask:

Which requirements should be demonstrated at ESA level?

and:

Which requirements must ultimately be demonstrated at vehicle level?

This allows the manufacturer to establish a more structured compliance strategy.

It can also help avoid unnecessary duplication.

For example, existing ESA test evidence may provide useful technical information during vehicle development.

However, its applicability to the vehicle-level requirements must be evaluated rather than assumed.

6.12 Why this matters for suppliers

For an automotive component supplier, the regulatory expectations of the customer should be clarified early.

A vehicle manufacturer may require:

• ECE R10 approval
• Specific EMC test reports
• Customer-specific EMC testing
• Specific installation conditions
• Particular test configurations
• Defined documentation
• Evidence of ongoing conformity

The supplier therefore needs to understand not only the regulatory requirements but also how its product will be integrated into the customer’s vehicle.

This is particularly important when a component is intended for several customers or vehicle platforms.

6.13 A practical example

Consider an electronic control unit designed for an electric vehicle.

At ESA level, the manufacturer may test the unit with:

• A defined power supply
• Defined wiring
• Representative loads
• Communication interfaces
• Defined operating modes

The unit can then be assessed against the applicable R10 requirements.

Later, the same ECU may be installed in a vehicle together with:

• A high-voltage inverter
• Battery electronics
• Several communication systems
• Radar sensors
• Charging equipment
• Multiple other ECUs

The electromagnetic environment of the complete vehicle is now much more complex.

The ESA approval remains valuable, but it does not eliminate the need to consider the complete vehicle configuration.

This example illustrates why component-level compliance and vehicle-level compliance are related but not interchangeable.

6.14 What manufacturers should define before testing

Before starting an R10 project, the manufacturer should establish:

Approval object

Is the subject of approval:

• A complete vehicle?
• An ESA?
• A specific variant of an ESA?

Configuration

Which:

• Hardware?
• Software?
• Wiring?
• Connectors?
• Loads?
• Communication interfaces?

are included?

Installation

Where and how will the equipment be installed?

Functions

Which functions must remain operational during immunity testing?

Variants

Which product variants are intended to be covered?

Regulatory basis

Which R10 provisions and amendments apply?

These questions should be answered before the laboratory scope is finalized.

6.15 Key takeaway

Vehicle-level and ESA-level approval are two different perspectives within the ECE R10 framework.

A vehicle-level assessment evaluates the electromagnetic compatibility of the complete vehicle as an integrated system.

An ESA-level assessment evaluates a specific electrical/electronic unit under defined conditions relevant to its intended automotive application.

Neither level should automatically be treated as a replacement for the other.

For manufacturers and suppliers, the most important step is to clearly establish what is being approved, in which configuration, for which installation and for which vehicle application.

That definition determines the appropriate test strategy and helps prevent unnecessary testing or gaps in the compliance evidence.

7. Standards and Test Methods Referenced by ECE R10

ECE R10 does not function as a completely standalone EMC test standard.

Instead, the regulation defines the applicable requirements and refers to established international and automotive standards for specific measurement and test methods. This creates a framework in which R10 determines what needs to be demonstrated, while the referenced standards define how particular aspects are tested.

This distinction is important when preparing an R10 test plan. Simply listing standards such as CISPR 25 or ISO 11452 does not yet define the complete test scope. The applicable standard, part, edition, test method and R10 requirement must all be considered together.

The standards referenced by UN R10 have also evolved over time. UNECE’s documentation shows changes to the referenced editions, and the 07 series of amendments has introduced further developments to the EMC test framework. (UNECE)

7.1 Why does R10 reference other standards?

UN Regulation No. 10 establishes the regulatory framework for electromagnetic compatibility, but detailed EMC measurement techniques require highly specific technical procedures.

For example, a regulation may require that radiated emissions remain below defined limits. A laboratory then needs a standardized method specifying matters such as:

• Test distance
• Antenna arrangement
• Measurement equipment
• Frequency range
• Detector characteristics
• Test environment
• Calibration
• Operating conditions

Instead of defining every technical laboratory detail independently, R10 references established standards.

This creates a relationship between the regulatory requirement and the technical test method:

ECE R10 → Defines the regulatory requirement

Referenced standard → Defines the applicable technical test method

This is why both elements need to be considered when determining the actual test scope.

7.2 CISPR 12

CISPR 12 is one of the important standards referenced for vehicle-level radiated emission measurements.

Its scope concerns the radio disturbance characteristics of vehicles and certain other engine-driven equipment, including the limits and methods of measurement.

Within the R10 framework, CISPR 12 is associated primarily with vehicle-level emission testing.

The purpose is to determine whether electromagnetic disturbances emitted by the vehicle remain within the applicable limits.

This is particularly relevant because a complete vehicle contains numerous potential emission sources:

• Electric motors
• Inverters
• DC/DC converters
• Electronic control units
• Switching power supplies
• Ignition systems where applicable
• Charging systems
• Communication electronics
• Other high-speed electronic circuits

The test therefore considers the vehicle as an integrated system rather than measuring one electronic module in isolation.

UNECE’s R10 documentation explicitly lists CISPR 12 among the referenced standards. (UNECE)

7.3 CISPR 25

CISPR 25 addresses radio disturbance characteristics for the protection of receivers used on board vehicles.

It is particularly relevant at component/ESA level.

The basic concern is different from simply asking whether the component itself emits electromagnetic energy.

The question is whether the electromagnetic disturbances generated by the component could interfere with radio receivers or other sensitive equipment within the vehicle.

This becomes increasingly important in modern vehicles because a single vehicle may contain numerous receivers and communication systems, including:

• AM/FM radio
• GNSS
• Bluetooth
• Wi-Fi
• Cellular communication
• Digital radio
• Other wireless systems

An electronic component can therefore create a potential interference problem even when its primary function has nothing to do with radio communication.

CISPR 25 provides standardized methods and limits for evaluating such disturbances.

UNECE lists CISPR 25 among the standards referenced by UN R10. (UNECE)

7.4 ISO 11451 – Vehicle-level immunity testing

The ISO 11451 series addresses electrical disturbances caused by narrowband radiated electromagnetic energy and provides vehicle-level test methods.

This is particularly relevant for assessing how a complete vehicle behaves when exposed to defined electromagnetic fields.

Depending on the applicable R10 requirements and test method, the vehicle can be exposed to electromagnetic energy using defined sources and test arrangements.

The objective is to determine whether the vehicle continues to perform its intended functions according to the applicable performance criteria.

The ISO 11451 series includes several parts addressing different aspects of vehicle-level immunity testing.

For example:

• ISO 11451-1 – General and definitions
• ISO 11451-2 – Off-vehicle radiation source
• ISO 11451-4 – Bulk current injection (BCI)

The exact part and edition applicable to an R10 project must be determined from the relevant version of the regulation.

UNECE’s proposed updates to the R10 referenced standards specifically include updates to ISO 11451-1 and ISO 11451-2. (UNECE)

7.5 ISO 11452 – Component-level immunity testing

Where ISO 11451 is primarily associated with vehicle-level immunity testing, ISO 11452 addresses immunity testing at component level.

The series is particularly relevant to ESAs.

It provides different methods for exposing an electronic component to controlled electromagnetic disturbances.

Depending on the applicable test, methods can include:

• Absorber-lined chamber (ALSE)
• TEM cell
• Bulk Current Injection (BCI)
• Stripline
• Reverberation chamber

For example:

ISO 11452-2 → Absorber-lined chamber

ISO 11452-3 → TEM cell

ISO 11452-4 → Bulk Current Injection

ISO 11452-5 → Stripline

ISO 11452-11 → Reverberation chamber

The exact method is not selected simply because it is available in the laboratory.

The appropriate method depends on the applicable R10 requirement, the equipment configuration and the characteristics of the ESA.

UNECE’s current R10 development documents include updates to several ISO 11452 references. (UNECE)

7.6 ISO 7637 – Electrical transient disturbances

Automotive electronic equipment can experience transient disturbances on electrical supply and signal lines.

The ISO 7637 series addresses electrical disturbances resulting from conduction and coupling in road vehicles.

It is particularly important for understanding the behaviour of electronic equipment connected to vehicle electrical networks.

One of the best-known parts is:

ISO 7637-2 – Electrical transient conduction along supply lines

The standard defines standardized transient phenomena and corresponding test methods.

Depending on the applicable R10 requirements, an ESA may need to demonstrate that it can tolerate defined transient disturbances without unacceptable loss of function.

The specific test pulses, levels, source impedance and acceptance criteria must be determined from the applicable requirements rather than assumed from the general name of the standard.

UNECE’s R10 documentation references the ISO 7637 series. (UNECE)

7.7 ISO 11451 and ISO 11452 are not interchangeable

This distinction is important enough to emphasize.

A manufacturer may hear:

“The product needs an immunity test according to ISO 11451/11452.”

That statement is still incomplete.

The two series address different testing contexts.

ISO 11451 → Vehicle test methods

ISO 11452 → Component test methods

Therefore, the first question should always be:

Are we testing the complete vehicle or an ESA?

Only after this has been established can the appropriate test methodology be selected.

Using the wrong series can result in a technically incorrect test program even if the laboratory performs the test perfectly according to the selected standard.

7.8 IEC 61000 standards can also appear in the R10 framework

ECE R10 is primarily associated with automotive EMC standards, but the regulation can also reference standards from the IEC 61000 series for specific requirements.

This is particularly relevant for certain electrical characteristics associated with charging or other power-related operating conditions.

Depending on the applicable R10 version and operating mode, requirements can concern topics such as:

• Harmonic current emissions
• Voltage changes
• Voltage fluctuations
• Flicker
• Electrical disturbances

This is particularly relevant to modern electric and hybrid vehicles because charging introduces electrical interactions that were less prominent in conventional vehicle architectures.

The applicable IEC 61000 standard must therefore be determined from the specific R10 requirements rather than added automatically to every R10 project.

7.9 CISPR 16 and measurement infrastructure

Some R10 tests also rely on standards governing EMC measurement equipment and test sites.

For example, the CISPR 16 series addresses measurement instrumentation, measurement methods and test-site characteristics.

This matters because an EMC result is only meaningful when the measurement system itself satisfies the relevant technical requirements.

Factors such as:

• Antenna characteristics
• Measurement receivers
• Test-site performance
• Calibration
• Measurement uncertainty
• Grounding arrangements
• Absorber performance

can all affect the reliability of the measurement.

R10 therefore does not exist in isolation from the broader EMC measurement framework.

7.10 ISO/IEC 17025 and laboratory competence

The competence of the testing organization is another important part of the overall framework.

ISO/IEC 17025 defines general requirements for the competence of testing and calibration laboratories.

This does not itself define an R10 EMC test.

Instead, it establishes requirements concerning the competence and management of laboratories performing testing and calibration activities.

The distinction is important:

ISO/IEC 17025 → Laboratory competence

ECE R10 → Regulatory requirements for vehicle EMC approval

CISPR / ISO / IEC test standard → Technical test method

These standards therefore serve different purposes within the overall compliance process.

7.11 The edition of a referenced standard matters

One of the easiest mistakes in an R10 project is to identify the correct standard but use the wrong edition.

For example:

“ISO 11451-2”

does not necessarily provide enough information for a formal test plan.

The applicable edition can matter because a newer edition may introduce changes to:

• Test setup
• Calibration
• Field uniformity
• Frequency ranges
• Test equipment
• Modulation
• Acceptance criteria
• Test procedure

UNECE has been actively updating the standards referenced by UN R10.

For example, recent UNECE working documents propose updating references from older editions of ISO 11451-1, ISO 11451-2 and ISO 11452-1 to newer editions. (UNECE)

This illustrates why an R10 test plan should always identify not only the standard number but also the applicable edition and regulatory status.

7.12 The 07 series makes the issue even more important

The transition to the 07 series of amendments introduced important changes to the R10 EMC framework.

One notable change is the extension of the immunity test frequency range from 2 GHz to 6 GHz.

UNECE documentation also identifies changes to pulse modulation methods and related test procedures. (UNECE)

This has practical consequences.

A laboratory that performed an older R10 test program may not necessarily have performed the same technical scope that is required under a newer amendment series.

Therefore, when reviewing an existing R10 test report, the manufacturer should always establish:

• Which R10 series was applied
• Which referenced standards were used
• Which editions were used
• Which frequency range was covered
• Which test methods were applied
• Which product configuration was tested

This is particularly important when an existing approval or test report is being used as the basis for a new project.

7.13 The regulation and the standards have to be read together

A common mistake is to treat the referenced standards as independent requirements.

For example, a manufacturer might say:

“We have tested according to CISPR 25, therefore the ESA is R10 compliant.”

That conclusion is not necessarily valid.

CISPR 25 describes a particular technical test area.

ECE R10 determines how that technical requirement fits into the regulatory approval framework.

The same principle applies to ISO 11452, ISO 7637 and the other referenced standards.

A proper assessment therefore follows a chain such as:

R10 requirement → Applicable test → Referenced standard → Applicable part → Applicable edition → Test configuration → Acceptance criteria

Only then is it possible to determine what the test actually demonstrates.

7.14 Different operating modes can trigger different requirements

Modern vehicles can operate in significantly different electrical states.

For example:

• Normal driving
• Charging
• Regenerative braking
• High-power acceleration
• Standby
• Communication-active modes
• Auxiliary functions
• Service modes

The relevant R10 requirements can depend on the operating condition being evaluated.

This is particularly relevant to electric and hybrid vehicles, where charging can introduce additional EMC considerations.

A test plan should therefore identify the operating modes relevant to the approval rather than assuming that one static operating condition represents the entire vehicle.

7.15 Why the standards should be identified during scoping

The standards referenced by R10 should not be selected only after the laboratory has been booked.

They should form part of the initial compliance scope.

A structured scoping process should establish:

1. What is being approved?
2. Which R10 amendment series applies?
3. Which emission requirements apply?
4. Which immunity requirements apply?
5. Which transient requirements apply?
6. Which charging-related requirements apply, if relevant?
7. Which test standards are referenced?
8. Which parts of those standards apply?
9. Which editions are applicable?
10. Which product configuration and operating modes must be tested?

This creates a clear bridge between the regulatory requirement and the laboratory test program.

7.16 What this means when requesting a laboratory quotation

A laboratory quotation based only on:

“ECE R10 testing required”

is unlikely to provide enough detail for reliable project planning.

A better request identifies the expected scope, for example:

• Vehicle or ESA
• Applicable R10 amendment series
• Emission tests
• Immunity tests
• Transient tests
• Applicable charging mode
• Referenced standards
• Product configuration
• Number of variants
• Required operating modes
• Required test samples

This gives the laboratory a much clearer basis for preparing the quotation.

It also allows the manufacturer to compare quotations more effectively.

Two laboratories may quote different prices not because one is necessarily more expensive, but because they have interpreted the scope differently.

A clearly defined standards and test-method matrix helps expose those differences.

7.17 Standards are technical tools — not the approval itself

It is important to keep the hierarchy clear.

A successful CISPR 25 test does not itself create an R10 approval.

A successful ISO 11452 test does not itself create an R10 approval.

A successful ISO 7637 test does not itself create an R10 approval.

These standards provide technical evidence within the broader regulatory process.

The approval results from applying the relevant technical requirements within the UN Regulation No. 10 type-approval framework.

This distinction becomes particularly important when communicating compliance status to customers.

7.18 Standards can change during a product lifecycle

Automotive products often remain in production for many years.

During that time:

• R10 can be amended;
• referenced standards can be updated;
• test methods can change;
• new technologies can create new requirements;
• transition periods can apply.

Therefore, a test report that was correct when issued does not automatically answer every question for a new product variant or a new approval project years later.

The manufacturer should maintain a clear record of:

• R10 version
• Amendment series
• Referenced standards
• Standard editions
• Test configuration
• Product version
• Approval status

This information is particularly valuable when extending an approval or assessing a product change.

7.19 Practical example

Consider an electronic control unit intended for installation in an electric vehicle.

The manufacturer may initially identify:

ESA → R10 → Emissions + Immunity + Transients

That is a useful starting point, but it is not yet a complete test plan.

The scope may then be developed into something such as:

Emissions → CISPR 25

Radiated immunity → applicable ISO 11452 method

Transient immunity → applicable ISO 7637 method

The manufacturer must then determine:

• Which specific parts apply
• Which editions apply
• Which operating modes are required
• Which cable configuration is representative
• Which loads are connected
• Which functions must be monitored
• Which R10 amendment series governs the approval

Only after these questions have been answered does the laboratory have a sufficiently defined technical basis for the test program.

7.20 Key takeaway

ECE R10 and the referenced standards should be viewed as parts of one compliance structure.

The most important standards include:

• CISPR 12 – vehicle-level radiated emissions
• CISPR 25 – component/ESA radio disturbance emissions
• ISO 11451 – vehicle-level immunity methods
• ISO 11452 – component/ESA immunity methods
• ISO 7637 – automotive electrical transient disturbances
• IEC 61000 series – specific EMC requirements where referenced
• CISPR 16 series – EMC measurement infrastructure and methods
• ISO/IEC 17025 – laboratory competence

However, simply naming these standards does not define an R10 project.

The manufacturer must establish the relationship between:

R10 → Requirement → Test method → Standard → Part → Edition → Configuration → Acceptance criteria

That is what turns a list of standards into an actual, usable compliance scope.

And because UNECE continues to update both UN R10 and its referenced standards, the applicable edition should always be verified at the time of the project rather than copied from an older test report or quotation. (UNECE)

8. The ECE R10 Approval Process

Obtaining an ECE R10 approval is more than completing a series of EMC tests.

The testing is one part of a broader type-approval process that connects the product, its technical configuration, the applicable requirements, the Technical Service, the Type Approval Authority and the manufacturer’s production controls.

For manufacturers, understanding this process is important because many problems that later appear during testing or approval can actually be traced back to an insufficiently defined scope at the beginning of the project.

A typical R10 project can be structured into several stages:

Product definition → Regulatory scoping → Test planning → Test configuration → Testing → Documentation → Type approval → Conformity of Production

The exact procedure depends on whether the subject is a complete vehicle or an ESA and on the applicable type-approval framework.

8.1 Step 1 – Define the approval object

The first question is:

What exactly is being approved?

This may be:

• A complete vehicle
• A vehicle type
• An electrical/electronic sub-assembly (ESA)
• A specific automotive electronic system

The distinction is fundamental because vehicle-level and ESA-level approval follow different technical approaches.

The manufacturer should establish at the beginning:

• Product name and designation
• Manufacturer
• Hardware configuration
• Software configuration where relevant
• Intended vehicle application
• Vehicle categories or platforms
• Intended installation
• Electrical interfaces
• Communication interfaces
• Relevant operating modes
• Product variants

The approval scope should be defined before the laboratory test program is finalized.

8.2 Step 2 – Determine whether ECE R10 applies

Before planning any test, the manufacturer should establish that UN R10 is actually applicable.

This requires considering the regulatory role of the product and its intended use.

Questions can include:

• Is the product intended for installation in a vehicle?
• Is it an ESA within the applicable regulatory framework?
• Is it part of a vehicle type-approval project?
• Is separate approval required?
• Is the product already covered by another approval?
• Which vehicle legislation applies?
• Which market and approval route are relevant?

This stage is particularly important for suppliers because the fact that a customer describes a product as an “automotive component” does not by itself determine its exact regulatory status.

8.3 Step 3 – Identify the applicable R10 version

Once applicability has been established, the manufacturer must determine which version of UN R10 applies.

This can involve:

• Revision
• Series of amendments
• Supplements
• Corrigenda
• Transitional provisions
• Referenced standards and their applicable editions

The approval number itself also reflects the series of amendments incorporated at the time the approval is issued. UNECE’s general type-approval provisions specify that the first two digits of the approval number indicate the series of amendments incorporating the latest major technical amendments applicable at the time of approval. (UNECE)

This is important when an existing approval is being extended or when an older test report is being considered for a new project.

8.4 Step 4 – Define the regulatory and technical scope

The next step is to convert the regulatory requirements into a concrete project scope.

The manufacturer should determine:

• Applicable emission requirements
• Applicable immunity requirements
• Transient requirements
• Relevant operating modes
• Functional performance criteria
• Applicable test methods
• Referenced standards
• Applicable standard editions
• Required test configurations
• Product variants
• Required documentation

The result should be a structured R10 test plan.

This test plan should answer a simple question:

What exactly has to be demonstrated before approval can be granted?

A generic statement such as “ECE R10 testing required” is not sufficient for reliable project planning.

8.5 Step 5 – Define the test configuration

The equipment must then be prepared in a configuration representative of the intended application.

Depending on the product, this can involve:

• Power supply
• Wiring harnesses
• Connectors
• Loads
• Communication interfaces
• Sensors
• Actuators
• Antennas
• Auxiliary equipment
• Software
• Operating modes
• Functional monitoring

The configuration is particularly important for ESA testing.

A component can behave differently depending on its cable arrangement, grounding, connected loads and operating mode.

The manufacturer should therefore define the configuration before testing rather than allowing the laboratory to make assumptions about how the product should be operated.

8.6 Step 6 – Prepare the test samples

The required test samples must be identified and prepared.

Depending on the project, this can include:

• Production-representative equipment
• Multiple product variants
• Appropriate cable harnesses
• Connectors
• Loads
• Power supplies
• Communication equipment
• Auxiliary devices

The sample should represent the configuration for which approval is being sought.

This is particularly important where several hardware or software variants exist.

A manufacturer should not assume that every variant can automatically be covered by a single test sample.

Instead, a worst-case strategy may be developed where permitted, with a clear technical justification for why the selected configuration represents the relevant variants.

8.7 Step 7 – Laboratory and Technical Service

The formal approval testing is performed within the applicable type-approval framework by the relevant Technical Service.

The Technical Service is not simply an ordinary commercial laboratory selected independently of the approval process.

Within the type-approval framework, Technical Services are designated for specific categories of activities and must demonstrate appropriate technical competence and independence. (EUR-Lex)

Depending on the applicable framework and arrangement, testing may be conducted in the Technical Service’s facilities or under its supervision in another facility.

This distinction is important when selecting a laboratory for an R10 project.

The question is therefore not simply:

“Which laboratory can perform an EMC test?”

It is:

“Which Technical Service and testing arrangement can provide the evidence required for this specific type-approval project?”

8.8 Step 8 – Perform the EMC tests

Once the scope and configuration are established, the applicable EMC tests can be performed.

Depending on the approval object and applicable requirements, the program can include areas such as:

• Radiated emissions
• Conducted emissions
• Radiated immunity
• Conducted immunity
• Transient disturbances
• Other specific EMC tests required by the applicable R10 provisions

The test methods and limits must be taken from the applicable R10 requirements and referenced standards.

During immunity testing, the relevant vehicle or ESA functions must also be monitored according to the applicable performance criteria.

The purpose is therefore not simply to obtain measurement values.

The test must demonstrate that the approved type satisfies the applicable technical requirements.

8.9 Step 9 – Evaluate the test results

After testing, the results are evaluated against the applicable limits and performance criteria.

There are generally three possible situations:

The product passes

The test results demonstrate compliance with the applicable requirement.

The results can then become part of the technical approval documentation.

The product fails

A failure must be investigated.

Depending on the cause, the manufacturer may need to modify:

• Hardware
• Software
• Filtering
• Shielding
• Grounding
• Cable configuration
• Installation
• Components

Additional testing may then be required.

The result is unclear

In some cases, the issue may not simply be a straightforward pass/fail result.

Questions may arise regarding:

• Test configuration
• Measurement uncertainty
• Functional performance
• Interpretation of a requirement
• Applicability of a particular test method

These situations may require clarification between the manufacturer, Technical Service and, where necessary, the relevant approval authority.

8.10 Step 10 – Prepare the technical documentation

The test results form part of a larger technical documentation package.

The approval documentation can include information such as:

• Manufacturer information
• Product description
• Technical specifications
• Drawings
• Electrical diagrams
• Product variants
• Installation information
• Test configuration
• Test results
• Test reports
• Applicable standards
• Relevant declarations and supporting documentation

The general UNECE type-approval framework requires approval documentation to contain, among other things, information documents from the manufacturer and the Technical Service test report. (UNECE)

The documentation must clearly identify the configuration that has actually been approved.

This becomes particularly important later when the manufacturer introduces product changes.

8.11 Step 11 – Application and approval by the Type Approval Authority

The Type Approval Authority is responsible for granting the formal approval.

This is distinct from the Technical Service.

A simplified division of responsibilities is:

Manufacturer → Provides the product and technical information

Technical Service → Performs or supervises the required technical assessment and testing

Type Approval Authority → Grants the formal type approval

The Type Approval Authority reviews the applicable documentation and evidence within the relevant approval framework.

If the requirements have been satisfied, the approval is granted and an approval number is assigned.

UNECE’s general type-approval provisions state that when the approval tests demonstrate compliance with the technical requirements, an approval is granted and an approval number and approval mark are assigned in accordance with the applicable UN Regulation. (UNECE)

8.12 Step 12 – The approval is linked to a defined type

An important point is that an approval does not simply say:

“This manufacturer is R10 compliant.”

The approval relates to a defined type and its approved characteristics.

That means the technical documentation must make clear what configuration is covered.

For an ESA, this can involve characteristics such as:

• Hardware
• Software
• Enclosure
• Electrical connections
• Interfaces
• Operating conditions
• Variants

For a vehicle, the approved type is defined through the relevant vehicle characteristics and configurations.

This is why configuration management becomes an important part of maintaining an R10 approval.

8.13 Step 13 – Conformity of Production

Obtaining the approval is not the end of the process.

The manufacturer must continue producing the approved product in conformity with the approved type.

This is known as Conformity of Production (CoP).

The purpose is straightforward:

The product tested and approved must remain representative of the products that are actually manufactured.

UNECE explains that, before granting type approval, the approval authority must verify satisfactory arrangements and procedures for ensuring that products in production conform to the approved type. It may also verify conformity-control methods at production facilities after approval has been granted. (UNECE)

This means that the manufacturer needs appropriate production and quality controls to prevent uncontrolled changes from affecting the approved characteristics.

8.14 Why production changes can affect the approval

Consider an ESA that was approved using:

• A specific PCB
• A specific power supply
• A specific connector
• A defined cable
• A particular enclosure
• A specific software version

The manufacturer later replaces one of the electronic components with another component that appears functionally equivalent.

From a purchasing or engineering perspective, this might be considered a minor change.

From an EMC perspective, however, the change could affect:

• Switching behaviour
• Noise generation
• Filtering
• Power consumption
• Ground currents
• Radiated emissions
• Conducted emissions
• Immunity

The manufacturer therefore needs a process for assessing changes against the approved configuration.

8.15 Step 14 – Managing changes and extensions

When a product changes, the manufacturer should determine whether the existing approval remains applicable.

Depending on the nature of the change, the result may be:

No impact → Existing approval remains applicable

Limited impact → Additional evidence or testing

Significant impact → Extension or modification of the approval

The applicable R10 provisions determine how changes and extensions are handled.

This is why a manufacturer should maintain a clear record of:

• Approved configuration
• Tested configuration
• Product variants
• Software versions
• Hardware revisions
• Relevant test reports
• Approval documentation

Without this information, it becomes much more difficult to determine whether a future change remains within the approved scope.

8.16 What happens if production is no longer compliant?

Conformity of Production is not merely a documentation exercise.

The manufacturer is expected to maintain procedures that ensure ongoing conformity.

Within the EU vehicle type-approval framework, for example, the approval authority can verify conformity arrangements and require appropriate corrective action where products are not produced in conformity with the approved type. (EUR-Lex)

The same principle is fundamental to the UNECE type-approval system:

Approval is based on a defined type, and production must remain consistent with that approved type.

8.17 How long does the process take?

There is no single standard timeline for an ECE R10 project.

The duration can depend on:

• Product complexity
• Number of variants
• Availability of test samples
• Test laboratory availability
• Test scope
• Existing test evidence
• Product readiness
• Number of failures
• Required modifications
• Documentation quality
• Approval authority workload

A project that is technically mature and has a clearly defined scope can move much faster than a project where the product is still changing during testing.

This is why laboratory availability alone should not be used as the project schedule.

The manufacturer should consider the complete chain:

Scope → Preparation → Laboratory → Testing → Corrections → Documentation → Approval

8.18 Why the laboratory quotation should be based on a defined scope

A laboratory quotation is only as reliable as the scope on which it is based.

If the request simply says:

“Please quote ECE R10 testing.”

the laboratory may need to make assumptions.

Different assumptions can concern:

• Number of variants
• Test methods
• Operating modes
• Harnesses
• Loads
• Samples
• Required supervision
• Existing test data
• Documentation
• Retesting

Two laboratories can therefore return significantly different quotations while both technically interpreting the request correctly.

A structured test plan provides a much better basis for comparison.

8.19 Where can manufacturers reduce project risk?

The greatest opportunities to reduce project risk are often before formal testing starts.

A manufacturer can improve the project by:

• Defining the approval object clearly
• Identifying the correct R10 version
• Defining the test scope
• Selecting representative samples
• Identifying worst-case configurations
• Preparing the required harnesses
• Defining functional monitoring
• Reviewing existing test evidence
• Confirming the Technical Service
• Preparing documentation in advance

This reduces the probability that the laboratory discovers basic scope or configuration problems after testing has already begun.

8.20 A practical example

Consider an automotive electronic control unit intended for installation in several vehicle platforms.

A poorly structured approach might look like this:

Product → Book laboratory → Start testing → Discover missing configuration → Modify product → Retest → Prepare documentation → Approval

This can quickly become expensive.

A structured approach would instead be:

Product definition

↓

R10 applicability

↓

Applicable R10 version

↓

Vehicle/ESA classification

↓

Variant analysis

↓

Test scope

↓

Test configuration

↓

Laboratory quotation

↓

Sample preparation

↓

Formal testing

↓

Documentation

↓

Type approval

↓

Conformity of Production

The second approach gives the manufacturer considerably more control over the project before significant laboratory costs are incurred.

8.21 The role of the manufacturer does not end with the certificate

An R10 approval should not be treated as a document that is obtained once and then forgotten.

The manufacturer needs to maintain control over the approved product throughout its lifecycle.

This includes:

• Engineering changes
• Supplier changes
• Component substitutions
• Software updates
• Production changes
• New variants
• New vehicle applications
• Manufacturing locations
• Changes to the production process

Each change should be assessed for its potential impact on the approved configuration.

This becomes particularly important for products with long automotive lifecycles.

8.22 The complete approval chain

The ECE R10 approval process can therefore be summarized as:

1. Define the product

↓

2. Determine R10 applicability

↓

3. Identify the applicable R10 version

↓

4. Define the regulatory and technical scope

↓

5. Define the test configuration

↓

6. Prepare samples and documentation

↓

7. Select/confirm the Technical Service

↓

8. Perform the required tests

↓

9. Evaluate the results

↓

10. Complete the approval documentation

↓

11. Type Approval Authority grants approval

↓

12. Maintain Conformity of Production

↓

13. Assess future changes and extensions

This is the complete compliance lifecycle rather than simply a laboratory test.

8.23 Key takeaway

ECE R10 approval is a structured type-approval process.

The EMC testing is an essential part of that process, but it is only one element.

For manufacturers, the most important steps are often the ones that happen before the product enters the laboratory:

Define the product.

Define the regulatory scope.

Define the applicable R10 version.

Define the test configuration.

Define the required evidence.

Only then should the formal test program begin.

A well-defined scope gives the Technical Service a clear basis for testing, gives the manufacturer a more reliable basis for laboratory quotations, and reduces the risk of discovering fundamental project problems after testing has already started.

And after approval, the process continues through Conformity of Production and change management.

That is what makes ECE R10 a type-approval process rather than simply an EMC laboratory test.

9. How to Define the ECE R10 Test Scope

One of the most important steps in an ECE R10 project takes place before the product enters the laboratory:

Defining the correct test scope.

ECE R10 does not provide one identical EMC test program for every automotive product. The applicable requirements depend on the approval object, the product configuration, the intended installation, the applicable R10 series of amendments, and the relevant test methods.

A well-defined scope therefore answers a fundamental question:

What exactly needs to be demonstrated for this specific product and configuration to obtain the required approval?

The answer should be established before laboratory testing is scheduled.

9.1 Start with the approval object

The first step is to identify exactly what is being assessed.

The project may concern:

• A complete vehicle
• An electrical/electronic sub-assembly (ESA)
• An ESA used in a specific vehicle application
• An ESA involved in REESS charging mode
• A particular vehicle type or configuration

This distinction is fundamental because R10 contains different requirements and test approaches for vehicles and ESAs.

The current R10 framework also distinguishes between different ESA operating/configuration categories, including ESAs involved in REESS charging mode coupled to the power grid. UNECE documentation for the 07 series specifically addresses separate testing provisions for these configurations. (UNECE)

Therefore, the scope should never begin with a generic statement such as:

“Automotive EMC testing according to ECE R10.”

It should begin with:

“What exactly is the approval object?”

9.2 Define the intended application

The next step is to understand how the product will actually be used.

For an ESA, this can include:

• Intended vehicle application
• Installation location
• Electrical connection
• Power supply
• Communication interfaces
• Connected sensors
• Connected actuators
• Connected loads
• Cable harness
• Antenna configuration
• Operating modes
• Charging mode, where applicable

The same electronic unit can have significantly different EMC characteristics depending on how it is installed.

A product that is connected to a long vehicle harness, for example, may behave differently from the same electronics evaluated with a short laboratory cable.

The intended application therefore needs to be part of the scope definition.

9.3 Identify the applicable R10 requirements

Once the approval object and application are known, the applicable R10 requirements can be identified.

These may cover areas such as:

• Radiated emissions
• Conducted emissions
• Radiated immunity
• Conducted immunity
• Electrical transient disturbances
• Specific charging-related requirements
• Functional performance during immunity testing

The exact combination depends on the product and applicable R10 provisions.

The current regulatory landscape is also evolving. UNECE has introduced the 07 series of amendments to UN R10, and further supplements are being developed. For example, UNECE published proposals for additional supplements to the 07 series during 2025 and 2026. (UNECE)

This makes the identification of the applicable regulatory version an essential part of the initial scope.

9.4 Determine the applicable R10 amendment series

Simply writing “ECE R10” into a test request is not sufficient.

The manufacturer should determine:

• Applicable series of amendments
• Relevant supplements
• Corrigenda
• Transitional provisions
• Referenced standards
• Applicable editions of those standards

This is particularly important for projects with long development cycles.

A product may be designed under one regulatory situation and tested or approved later under another.

The scope should therefore document the regulatory basis on which the test program has been established.

9.5 Identify the product variants

Automotive products frequently exist in multiple variants.

Differences may include:

• Hardware versions
• PCB revisions
• Software versions
• Power ratings
• Communication interfaces
• Connector configurations
• Cable lengths
• Enclosures
• Antennas
• Optional functions
• Different operating modes

The scope must determine which of these variants need to be considered.

The objective is not necessarily to test every single variant independently.

Instead, the manufacturer and Technical Service should establish whether variants can be represented by a common configuration or whether additional testing is necessary.

This requires a technically justified variant assessment.

9.6 Identify the worst-case configuration

One of the central questions in a multi-variant project is:

Which configuration represents the worst case for the applicable test?

The worst case can differ depending on the requirement.

For emissions, for example, a configuration with:

• maximum processor activity;
• maximum switching activity;
• maximum load;
• active communication interfaces

may produce higher emissions than another configuration.

For immunity, a different operating mode may be more critical because a particular function is more susceptible to interference.

Therefore, there may not be one universal “worst-case product.”

The relevant worst case can depend on:

Test + operating mode + configuration + function

The selected representative configuration should therefore be technically justified and documented.

9.7 Define the operating modes

The equipment must be operated in conditions that allow the relevant functions and EMC behaviour to be evaluated.

Depending on the product, this can include:

• Normal operating mode
• Maximum load
• Standby mode
• Communication-active mode
• Charging mode
• Maximum power mode
• Diagnostic mode
• Specific functional modes

The correct operating condition depends on the applicable test.

For example, an electronic control unit may need to operate multiple outputs simultaneously to reproduce a realistic electrical and functional condition.

A charging-related ESA may require a dedicated charging configuration.

The scope should therefore define how the product will operate during each relevant test, not simply identify the test name.

9.8 Define the interfaces

The electrical and communication interfaces of the equipment are an important part of the test scope.

These can include:

• DC power
• AC power
• Ground
• CAN
• LIN
• Ethernet
• USB
• Sensor interfaces
• Actuator interfaces
• RF interfaces
• Charging interfaces
• Other proprietary interfaces

Each interface can potentially influence EMC behaviour.

Some interfaces may carry disturbances into the equipment.

Others may act as coupling paths through which disturbances leave the equipment.

The scope should therefore identify the relevant interfaces and determine how they are represented during testing.

9.9 Define the wiring and harness configuration

The wiring configuration can have a significant impact on EMC results.

Relevant parameters can include:

• Cable type
• Cable length
• Number of cables
• Harness arrangement
• Shielding
• Connector type
• Grounding
• Routing
• Termination
• Connected loads

For an ESA, the harness should represent the intended installation or the configuration required by the applicable test method.

This is particularly important because cables can act as both:

Sources of electromagnetic emissions

and

Paths through which electromagnetic disturbances enter the equipment.

A change in cable configuration can therefore potentially change the EMC result.

9.10 Define the connected loads

The equipment should not necessarily be tested as an isolated electronic box.

Depending on its function, it may need to operate with representative loads.

These can include:

• Motors
• Lamps
• Valves
• Relays
• Actuators
• Heating elements
• Electronic loads
• Communication devices
• Sensors

The load can influence both the electrical behaviour and the EMC characteristics of the equipment.

For example, switching an actuator can generate electrical transients that are not present when the output is left unloaded.

The test scope should therefore identify which loads need to be connected and under which operating conditions.

9.11 Define the functions that must be monitored

For immunity testing, defining the test conditions is only half of the task.

The manufacturer must also determine:

What must continue to function while the disturbance is being applied?

Depending on the equipment, this can involve monitoring:

• Control outputs
• Sensor signals
• Actuator commands
• Communication
• Displays
• Alarms
• Charging functions
• Diagnostic functions
• Safety-related functions

The applicable R10 requirements determine the relevant performance criteria.

The test plan should translate those requirements into practical monitoring instructions for the laboratory.

For example:

Function: Motor control

Operating condition: Motor running at defined load

Monitoring: Speed, control signal and diagnostic status

Acceptance: No unacceptable loss of function according to the applicable performance criterion

This is much more useful than simply writing:

“Radiated immunity – perform test.”

9.12 Separate emissions and immunity requirements

The test scope should clearly distinguish between emission and immunity testing.

Emissions

The question is:

How much electromagnetic disturbance does the product generate?

Relevant considerations can include:

• Frequency range
• Measurement method
• Measurement distance
• Detector
• Operating mode
• Maximum load
• Applicable limit

Immunity

The question is:

How does the product behave when electromagnetic disturbances are applied?

Relevant considerations can include:

• Frequency range
• Field strength or disturbance level
• Modulation
• Coupling method
• Cable configuration
• Operating mode
• Functional monitoring
• Acceptance criteria

These two areas require different test strategies.

9.13 Identify the applicable test methods

Once the requirements have been identified, the corresponding test methods need to be established.

Depending on the approval object, the R10 framework references automotive standards and methods including:

• CISPR 12
• CISPR 25
• ISO 11451 series
• ISO 11452 series
• ISO 7637 series

The applicable method depends on the individual requirement.

For example, vehicle-level and ESA-level immunity testing do not simply use the same setup.

The current R10 documentation also contains specific provisions for ESAs in different configurations, including separate provisions for ESAs involved in REESS charging mode coupled to the power grid. (UNECE)

Therefore, the test method should be selected after the approval object and configuration have been defined.

9.14 Check the applicable edition of every referenced standard

Identifying the standard alone is not enough.

The applicable edition must also be established.

For example:

ISO 11452-2

is not a complete regulatory reference unless the applicable edition is known.

This matters because standards are periodically revised.

UNECE’s recent R10 development work explicitly addresses updates to referenced standards. In its work on the 07 series, UNECE has discussed, among other things, updates to ISO 11452-3 and changes to referenced standards and their editions. (UNECE)

The scope should therefore document the relevant edition rather than relying on a laboratory to select one without further discussion.

9.15 Define the test samples

The number and type of samples required should be determined before the laboratory is booked.

The scope should consider:

• Number of samples
• Product variants
• Hardware revisions
• Special configurations
• Charging configuration
• Required accessories
• Harnesses
• Auxiliary equipment
• Replacement samples

The exact sample requirement depends on the applicable R10 test program and the Technical Service.

The manufacturer should therefore establish the sample plan together with the test scope rather than sending arbitrary samples to the laboratory.

9.16 Define the laboratory configuration

A useful test scope should provide the laboratory with enough information to reproduce the intended configuration.

This can include:

• Product drawings
• Electrical diagrams
• Harness drawings
• Connector information
• Load information
• Communication setup
• Operating software
• Test modes
• Installation information
• Photographs
• Functional monitoring instructions

This information helps the laboratory understand what is being tested and reduces the need for assumptions during the test campaign.

9.17 Consider existing test data

Manufacturers often already have EMC data from:

• Development testing
• Pre-compliance testing
• Customer-specific testing
• Previous R10 projects
• Other regulatory programs
• Previous product generations

Existing evidence should be reviewed before the scope is finalized.

It may reveal:

• Known weak points
• Already tested frequency ranges
• Existing worst-case configurations
• Previously successful test setups
• Potentially reusable technical evidence

However, existing data should not automatically be treated as valid R10 evidence.

Its relevance depends on the applicable requirements and the similarity of:

• Product configuration
• Test method
• Limits
• Operating mode
• Harness
• Loads
• Functional criteria

A structured gap analysis can therefore be useful before deciding which tests still need to be performed.

9.18 Define what happens if the product fails

The test scope should also consider the possibility of a failure.

Before testing begins, the manufacturer should understand:

• Which results constitute a failure
• Who evaluates the failure
• How modifications will be controlled
• Whether retesting is required
• Which tests may be affected by a hardware change
• How the modified configuration will be documented

This is particularly important when testing is performed as part of a formal approval project.

A modification after a failed test can potentially affect other test results or the approved configuration.

9.19 The test scope should become a controlled document

The final R10 test scope should not exist only as an email exchange between the manufacturer and laboratory.

It should ideally become a controlled project document.

It should identify at least:

Area	Information
Approval object	Vehicle / ESA
R10 version	Applicable series and amendments
Product	Product designation and revision
Variants	Included configurations
Operating modes	Modes to be tested
Interfaces	Electrical and communication interfaces
Harness	Type, length and configuration
Loads	Connected loads
Emissions	Applicable emission tests
Immunity	Applicable immunity tests
Transients	Applicable transient tests
Functional monitoring	Functions and acceptance criteria
Standards	Applicable standards and editions
Samples	Required test samples
Documentation	Required technical information
Approval route	Technical Service / approval authority

The exact structure can be adapted to the project, but the principle remains the same:

The scope should be explicit enough that the manufacturer, laboratory and approval organization understand what is being assessed.

9.20 Scope definition should happen before the laboratory quotation

A common approach is:

Find laboratory → request quotation → discuss scope

A more reliable approach is:

Define regulatory scope → define technical scope → request comparable quotations

This difference can be significant.

If the scope is unclear, laboratories may make different assumptions.

One laboratory may include:

• additional variants;
• additional operating modes;
• additional samples;
• additional retest time.

Another may assume a narrower configuration.

The resulting quotations are then not directly comparable.

A structured scope makes the commercial comparison much more meaningful.

9.21 The relationship between scope and cost

The test scope directly influences:

• Laboratory time
• Number of test days
• Number of samples
• Preparation effort
• Retesting
• Engineering support
• Documentation
• Project duration

A broader scope is not necessarily wrong.

A narrower scope is not necessarily better.

The objective is to define the correct scope.

Too broad:

Unnecessary testing → unnecessary cost

Too narrow:

Missing evidence → additional testing and potential project delays

The most efficient scope is therefore not the smallest possible scope.

It is the scope that is technically and regulatorily sufficient for the intended approval.

9.22 A practical example

Consider an automotive electronic control unit with three variants:

• Variant A: Standard hardware
• Variant B: Additional communication interface
• Variant C: Higher-power output stage

All three use the same basic enclosure.

A superficial test plan might simply state:

“ECE R10 testing for ECU.”

A structured scope would instead ask:

• Which variant has the highest switching activity?
• Which variant has the highest electrical load?
• Does the additional communication interface affect emissions?
• Are the cable configurations identical?
• Are the operating modes identical?
• Which functions need to be monitored?
• Can one configuration represent the others?
• Are additional samples required?
• Are existing test results available?

The result could be a test strategy in which certain tests use one representative configuration while other variants require additional evidence or testing.

The important point is that this decision is made before the laboratory campaign, based on a documented technical assessment.

9.23 Scope definition is not the same as test execution

Another important distinction is between:

Defining what must be tested

and

performing the test.

The manufacturer, compliance team and Technical Service may need to clarify the scope before testing begins.

The laboratory then executes the agreed test program under the applicable requirements and procedures.

This separation helps avoid a situation where the laboratory effectively determines the regulatory scope only after the product has already arrived.

The laboratory should be able to start from a clearly defined project rather than having to discover the intended approval strategy during the test campaign.

9.24 The scope should remain traceable throughout the project

The scope should not disappear once testing begins.

It should remain connected to:

Requirement → Test → Configuration → Result → Report → Approval

This traceability becomes especially valuable when:

• a test fails;
• a product changes;
• a variant is added;
• a customer requests additional applications;
• an approval is extended;
• an old test report is reused.

If the manufacturer can clearly demonstrate which configuration was tested against which requirement, later compliance decisions become much easier.

9.25 Key takeaway

Defining the ECE R10 test scope is one of the most important activities in the entire approval project.

A reliable scope should establish:

1. What is being approved?
2. Which R10 version and amendments apply?
3. Which product variants are included?
4. Which operating modes must be tested?
5. Which interfaces, harnesses and loads are relevant?
6. Which emissions and immunity requirements apply?
7. Which test methods and standard editions are required?
8. Which functions must be monitored?
9. Which samples are required?
10. Which existing evidence can potentially be reused?

Only after these questions have been answered should the formal laboratory program be finalized.

A well-defined ECE R10 scope gives the manufacturer a much clearer basis for laboratory quotations, test planning, sample preparation, project scheduling and approval documentation.

Most importantly, it reduces the risk of discovering during formal testing that the project was never properly defined in the first place.

10. Preparing for ECE R10 Testing

Once the ECE R10 scope has been defined, the next step is to prepare the product and the complete test setup for the laboratory.

Good preparation is critical because an R10 test campaign involves much more than delivering the product to a laboratory. The laboratory needs to know exactly what is being tested, how it is intended to operate, which configuration represents the approved product, and which external equipment is required to reproduce the intended conditions.

Insufficient preparation can lead to delays, additional laboratory time, incorrect test configurations or the need to repeat tests.

The objective of the preparation phase is therefore to ensure that the laboratory can start testing with a clearly defined and controlled configuration.

10.1 Start with the final test scope

Before preparing samples or booking laboratory time, the manufacturer should have a documented test scope.

The scope should establish, at minimum:

• the approval object;
• the applicable R10 version and amendment series;
• the product designation and revision;
• applicable product variants;
• operating modes;
• relevant interfaces;
• cable and harness configuration;
• connected loads;
• applicable emissions tests;
• applicable immunity tests;
• functional monitoring requirements;
• applicable test standards;
• required samples;
• required auxiliary equipment.

The laboratory quotation should ideally be based on this defined scope.

If the scope changes after the laboratory has been booked, the original quotation may no longer reflect the actual work required.

10.2 Prepare a complete product description

The laboratory needs to understand what the equipment actually is and what it does.

A useful product description should include information such as:

• product name;
• model or part number;
• hardware revision;
• software or firmware version;
• intended function;
• electrical ratings;
• communication interfaces;
• operating modes;
• connected loads;
• relevant accessories;
• intended vehicle application.

The description does not need to be unnecessarily long.

What matters is that the laboratory can clearly identify the equipment and understand its relevant operating characteristics.

10.3 Control the exact product configuration

Configuration control is particularly important for formal approval testing.

The manufacturer should clearly identify the exact configuration that is going to be tested.

This can include:

• hardware revision;
• PCB revision;
• component population;
• software version;
• firmware;
• enclosure;
• connectors;
• cable configuration;
• shielding;
• antenna;
• external components;
• auxiliary equipment.

The tested configuration should be traceable to the configuration that is intended to be covered by the approval.

This becomes particularly important when several development versions of the product exist at the same time.

A laboratory should not have to determine which engineering sample represents the final approval configuration.

10.4 Prepare the required technical documentation

The documentation required for an R10 project depends on the specific approval and the technical service, but the manufacturer should generally be prepared to provide sufficient information to identify and reproduce the relevant configuration.

This may include:

• product datasheet;
• product drawings;
• photographs;
• electrical schematics;
• block diagrams;
• PCB information where required;
• connector drawings;
• pin assignments;
• cable diagrams;
• wiring diagrams;
• operating instructions;
• software or firmware information where relevant;
• installation instructions;
• information about connected loads;
• product variants.

The purpose is not to provide every document the company has ever created.

The purpose is to provide the information necessary for the approval and test configuration to be understood and controlled.

10.5 Prepare the test samples

The required number of samples should be agreed before the laboratory campaign begins.

The manufacturer should establish:

• how many samples are required;
• which hardware revision each sample represents;
• whether different variants require separate samples;
• whether spare samples are recommended;
• whether samples need to be production-equivalent;
• whether special configurations are required.

The samples should be clearly identified.

For example:

Sample 01 – HW Rev. C / SW 4.2.1

Sample 02 – HW Rev. C / SW 4.2.1

This may seem simple, but clear identification becomes extremely useful if several variants or samples are involved.

10.6 Prepare the harnesses

For automotive EMC testing, the harness is often an important part of the test configuration.

The manufacturer should therefore prepare the required cables and harnesses in advance.

Relevant information can include:

• cable type;
• cable length;
• conductor cross-section;
• shielding;
• connector type;
• termination;
• branching;
• grounding;
• routing requirements;
• vehicle-side connections.

If the product normally uses a specific vehicle harness, it should be determined whether this harness or an appropriate representative configuration is required for the test.

A laboratory should not have to improvise the harness configuration on the day of testing.

10.7 Prepare the required loads

Many automotive electronic products cannot be tested meaningfully without representative loads.

Depending on the equipment, these may include:

• motors;
• valves;
• lamps;
• relays;
• actuators;
• electronic loads;
• heating elements;
• sensors;
• communication equipment.

The manufacturer should define which loads are required and how they are operated during each test.

This is particularly important when the load itself influences the EMC behaviour of the product.

For example, an output stage driving a motor may generate significantly different electrical conditions than the same output operating without a load.

10.8 Define the operating modes before testing

The laboratory needs clear instructions regarding how the product should operate during the tests.

A useful test instruction can specify, for example:

Parameter	Test condition
Power supply	13.5 V DC
Operating mode	Normal operation
Communication	CAN active
Output 1	Active
Output 2	Active
Motor	Running at defined load
Monitoring	Speed + diagnostic status

The actual conditions depend entirely on the product and applicable requirements.

The important point is that the manufacturer should define them before testing begins.

This avoids situations where the laboratory has to decide how the product should be operated after the test campaign has already started.

10.9 Define the functions that need to be monitored

For immunity testing, the laboratory needs to know what constitutes normal operation.

The manufacturer should identify the functions that need to be monitored and define the acceptable behaviour.

Depending on the product, monitoring may include:

• output signals;
• sensor values;
• communication;
• actuator operation;
• motor speed;
• charging behaviour;
• diagnostic messages;
• alarms;
• display functions;
• safety-related functions.

The monitoring method should also be practical.

If a critical function cannot be observed directly, the manufacturer should provide an appropriate method to verify its status during the test.

10.10 Prepare software and control interfaces

Modern automotive products are often highly dependent on software.

The manufacturer should therefore determine whether the laboratory requires:

• specific firmware;
• test software;
• diagnostic software;
• configuration files;
• calibration data;
• communication tools;
• CAN or Ethernet interfaces;
• programming tools;
• special operating commands.

The software version used during the test should be documented.

If the product has several software configurations, the manufacturer should clearly identify which one is included in the approval scope.

A software change can potentially affect EMC behaviour, particularly where the change modifies switching activity, communication behaviour, processor loading or operating modes.

10.11 Prepare communication interfaces

Many automotive products require active communication during testing.

Examples include:

• CAN;
• CAN FD;
• LIN;
• Automotive Ethernet;
• FlexRay;
• proprietary interfaces.

The manufacturer should provide the laboratory with the necessary equipment and information to reproduce the required communication activity.

This can include:

• message definitions;
• communication rates;
• network configuration;
• test scripts;
• interface hardware;
• required message sequences.

The communication activity should be representative of the operating condition being assessed.

10.12 Prepare auxiliary equipment

The product under test may require additional equipment to operate correctly.

This can include:

• power supplies;
• signal generators;
• loads;
• communication interfaces;
• computers;
• diagnostic tools;
• simulators;
• battery emulators;
• network equipment;
• control units;
• charging equipment.

The manufacturer should agree with the laboratory which equipment will be supplied by whom.

This should be clarified before the test campaign.

Otherwise, a missing auxiliary device can prevent testing from starting even though the main product is already at the laboratory.

10.13 Consider the physical installation

The physical position and orientation of the equipment can influence EMC behaviour.

Depending on the applicable test, relevant factors can include:

• equipment orientation;
• mounting arrangement;
• distance to the ground plane;
• cable routing;
• antenna position;
• enclosure position;
• grounding;
• mounting hardware.

For an ESA, the test configuration should be consistent with the applicable test method and the intended installation conditions.

The manufacturer should therefore provide the laboratory with appropriate installation information rather than leaving the setup open to interpretation.

10.14 Prepare a test instruction

For complex products, a dedicated test instruction can be extremely useful.

It can contain:

Product identification

• Product name
• Part number
• Hardware revision
• Software version

Electrical configuration

• Supply voltage
• Current
• Grounding
• Power connections

Communication

• CAN/LIN/Ethernet configuration
• Required messages
• Communication activity

Loads

• Connected loads
• Load levels
• Operating states

Functional monitoring

• Functions to monitor
• Monitoring method
• Acceptance criteria

Test modes

• Normal mode
• Maximum load
• Communication active
• Charging mode
• Other relevant conditions

Special instructions

• Programming requirements
• Diagnostic functions
• Reset procedure
• Recovery procedure

This document gives the laboratory a controlled reference for operating the equipment.

10.15 Prepare for pre-test checks

Before formal testing begins, the laboratory may perform setup checks or preliminary measurements.

These checks can help identify:

• incorrect wiring;
• communication problems;
• missing loads;
• incorrect operating modes;
• unexpected emissions;
• malfunctioning samples;
• configuration errors.

The manufacturer should use this stage to verify that the product behaves as expected in the intended test configuration.

It is much better to discover that a communication interface does not work with the laboratory equipment during preparation than after several hours of formal testing have already been scheduled.

10.16 Consider pre-compliance testing

Pre-compliance testing can be particularly useful for products with significant EMC risk.

It can help identify potential problems before formal approval testing.

Typical objectives include:

• identifying emission peaks;
• identifying sensitive operating modes;
• checking immunity weaknesses;
• evaluating cable configurations;
• testing design changes;
• selecting representative worst-case variants.

Pre-compliance testing is not automatically a substitute for formal R10 testing.

Its value is that it allows the manufacturer to identify and address problems earlier in the development process.

10.17 Prepare a failure-response plan

The manufacturer should know what will happen if the product does not meet a requirement.

A practical response process could be:

Failure detected → Failure analysed → Root cause identified → Corrective action defined → Modification implemented → Impact assessed → Retest planned

The manufacturer should also determine who has authority to approve modifications during the test campaign.

This is important because informal changes made during testing can create configuration-control problems.

Every modification should be documented.

10.18 Keep configuration control throughout the test campaign

The configuration tested on Monday should still be identifiable on Friday.

This becomes more difficult when:

• firmware is updated;
• components are replaced;
• cables are modified;
• connectors are changed;
• samples are repaired;
• hardware is reworked.

Every such change should be recorded.

A simple configuration log can contain:

Date	Sample	Change	Reason	Approved by
15 Aug	Sample 01	Firmware update	Communication issue	Engineering
16 Aug	Sample 01	Cable replaced	Damaged cable	Engineering

This provides valuable traceability if questions arise later regarding the test results.

10.19 Agree on the laboratory responsibilities

Before the test campaign begins, responsibilities should be clear.

For example:

Manufacturer provides:

• samples;
• harnesses;
• product documentation;
• loads;
• software;
• communication equipment;
• test instructions;
• technical support.

Laboratory provides:

• test facility;
• test equipment;
• test setup;
• measurements;
• test execution;
• test records;
• test report.

The exact division of responsibilities will vary between projects.

The important point is that it should be agreed before testing starts.

10.20 Confirm the laboratory quotation against the final scope

Before issuing the final purchase order, the manufacturer should compare the quotation against the approved test scope.

Check:

• number of test days;
• number of samples;
• number of variants;
• included test methods;
• included setup time;
• included reporting;
• retest conditions;
• engineering support;
• additional equipment;
• travel or logistics costs where applicable.

This is particularly important when comparing multiple laboratories.

A lower price does not necessarily mean a lower project cost if important activities have simply been excluded from the quotation.

10.21 Prepare for the test report

The final report should be able to identify exactly what was tested.

The manufacturer should therefore ensure that the laboratory has the correct information for:

• product identification;
• sample identification;
• hardware revision;
• software version;
• test configuration;
• applicable standards;
• operating conditions;
• test dates;
• test results.

Errors in product identification or configuration information can become surprisingly difficult to correct after the formal report has been issued.

10.22 What a well-prepared test campaign looks like

A well-prepared R10 test campaign should allow the laboratory to answer the following questions immediately:

What are we testing?

Which configuration is being approved?

Which R10 requirements apply?

How must the equipment operate?

Which cables and loads are required?

Which functions must be monitored?

What constitutes acceptable performance?

Which documentation and standards apply?

If the laboratory has to discover the answers to these questions during the test campaign, the project was probably not sufficiently prepared.

10.23 Final preparation checklist

Before sending the product to the laboratory, the manufacturer should verify:

Regulatory

• Applicable R10 version identified
• Approval scope defined
• Applicable standards identified
• Required test methods confirmed

Product

• Correct hardware revision
• Correct software version
• Product variants identified
• Samples clearly labelled

Test setup

• Harnesses prepared
• Loads prepared
• Communication equipment prepared
• Auxiliary equipment prepared
• Power supply requirements defined
• Installation configuration documented

Operation

• Test modes defined
• Functions to be monitored defined
• Acceptance criteria defined
• Test instruction prepared

Documentation

• Product description
• Drawings
• Schematics
• Cable information
• Installation information
• Configuration information

Project

• Laboratory quotation checked against scope
• Responsibilities agreed
• Test schedule confirmed
• Failure-response process agreed
• Configuration-control process established

10.24 Key takeaway

Preparation is a major part of an ECE R10 test campaign.

The laboratory should receive more than a product sample.

It should receive a defined and controlled test configuration consisting of the correct product version, harnesses, loads, operating modes, auxiliary equipment and technical information.

The better this preparation is, the less room there is for assumptions during the formal testing.

For manufacturers, the most important principle is simple:

The laboratory should test the configuration you intended to approve — not a configuration that has to be reconstructed during the test campaign.

11. ECE-R10-Typgenehmigung vs. EMV-Prüfbericht

Ein erfolgreicher EMV-Test und eine ECE-R10-Typgenehmigung sind nicht dasselbe.

Diese Unterscheidung ist für Hersteller besonders wichtig, weil Begriffe wie „R10-Test“, „R10-Zertifikat“, „EMV-Bericht“ und „R10-Zulassung“ in der Praxis häufig miteinander vermischt werden.

Ein Labor kann nachweisen, dass eine bestimmte Produktkonfiguration die festgelegten Prüfanforderungen erfüllt. Die eigentliche ECE-R10-Typgenehmigung ist jedoch Teil eines formalen Fahrzeug-Typgenehmigungsverfahrens.

11.1 Was zeigt ein EMV-Prüfbericht?

Ein EMV-Prüfbericht dokumentiert die Ergebnisse der durchgeführten Prüfungen.

Er kann beispielsweise festhalten:

• welches Produkt geprüft wurde;
• welche Hardware- und Softwareversion verwendet wurde;
• welche Prüfkonfiguration eingesetzt wurde;
• welche Prüfverfahren angewendet wurden;
• welche Betriebsbedingungen vorlagen;
• welche Grenzwerte galten;
• welche Messergebnisse erzielt wurden;
• ob die geprüfte Konfiguration die jeweiligen Prüfanforderungen erfüllt hat.

Der Prüfbericht ist damit ein technischer Nachweis.

Er dokumentiert, was unter den beschriebenen Bedingungen geprüft wurde und welches Ergebnis dabei erzielt wurde.

Ein solcher Bericht kann ein wichtiger Bestandteil eines Genehmigungsprojekts sein.

Er ist jedoch nicht automatisch selbst die Typgenehmigung.

11.2 Was bedeutet ECE-R10-Typgenehmigung?

Eine ECE-R10-Typgenehmigung ist eine regulatorische Genehmigung innerhalb des UNECE-Fahrzeug-Typgenehmigungsrahmens.

Sie basiert nicht ausschließlich auf einem einzelnen Messergebnis.

Vielmehr gehört die Prüfung zu einem umfassenderen Genehmigungsprozess, in dem unter anderem berücksichtigt werden:

• der Genehmigungsgegenstand;
• der definierte technische Umfang;
• die anzuwendenden R10-Bestimmungen;
• die technische Dokumentation;
• die durchgeführten Prüfungen;
• die Prüfungsergebnisse;
• die zuständige Genehmigungsbehörde;
• der zuständige Technische Dienst;
• gegebenenfalls Anforderungen an die Konformität der Produktion.

Die tatsächliche Genehmigung entsteht somit erst im Rahmen des entsprechenden Typgenehmigungsverfahrens.

11.3 Der Technische Dienst

Der Technische Dienst spielt eine zentrale Rolle im Genehmigungsprozess.

Er führt die relevanten Prüfungen beziehungsweise die für die Genehmigung erforderlichen technischen Bewertungen nach den geltenden Anforderungen durch.

Dabei geht es nicht nur darum, Messwerte zu erzeugen.

Der Technische Dienst muss feststellen, ob die geprüfte Konfiguration die für die Genehmigung relevanten technischen Anforderungen erfüllt.

Je nach Genehmigungsprojekt können daher neben den eigentlichen Messungen auch die technische Dokumentation und die konkrete Prüfkonfiguration eine wichtige Rolle spielen.

11.4 Die Genehmigungsbehörde

Die Genehmigungsbehörde ist von der Rolle des Prüflabors beziehungsweise Technischen Dienstes zu unterscheiden.

Die Genehmigungsbehörde ist für die Erteilung der Typgenehmigung innerhalb des jeweiligen Genehmigungsrahmens zuständig.

Der Technische Dienst liefert die technische Grundlage beziehungsweise führt die entsprechenden Bewertungen und Prüfungen im Rahmen seiner Benennung durch.

Vereinfacht dargestellt:

Technischer Dienst → technische Prüfung und Bewertung

Genehmigungsbehörde → Typgenehmigung

Die konkrete organisatorische Ausgestaltung hängt vom jeweiligen Genehmigungsweg und der zuständigen Behörde ab.

11.5 Warum ein Laborbericht nicht automatisch ein „R10-Zertifikat“ ist

Ein häufiger Fehler besteht darin, einen erfolgreichen Prüfbericht als „R10-Zertifikat“ zu bezeichnen.

Das kann zu einer falschen Darstellung des tatsächlichen Genehmigungsstatus führen.

Ein Prüfbericht kann beispielsweise zu dem Ergebnis kommen:

„Die geprüfte Konfiguration erfüllt die anwendbaren Prüfanforderungen.“

Das bedeutet jedoch nicht automatisch:

„Für diese Ausrüstung wurde eine ECE-R10-Typgenehmigung erteilt.“

Zwischen diesen beiden Aussagen besteht ein regulatorischer Unterschied.

Der Prüfbericht ist technische Evidenz.

Die Typgenehmigung ist der regulatorische Genehmigungsstatus.

11.6 Warum diese Unterscheidung in der Praxis wichtig ist

Die Unterscheidung wird besonders relevant, wenn Hersteller ihren Compliance-Status gegenüber Kunden kommunizieren.

Ein Kunde kann beispielsweise fragen:

„Ist das Produkt ECE R10 approved?“

Eine Antwort wie:

„Ja, wir haben einen EMV-Prüfbericht.“

würde diese Frage nicht zwangsläufig beantworten.

Ein Prüfbericht kann zwar Bestandteil des Nachweises sein, aber er bestätigt nicht automatisch, dass die entsprechende Typgenehmigung tatsächlich erteilt wurde.

Der Hersteller sollte daher klar zwischen folgenden Begriffen unterscheiden:

Begriff	Bedeutung
EMV-Prüfung	Technische Prüfung bestimmter Anforderungen
EMV-Prüfbericht	Dokumentation der durchgeführten Prüfung und Ergebnisse
Technischer Nachweis	Technische Evidenz für die Compliance-Bewertung
ECE-R10-Typgenehmigung	Formale Genehmigung innerhalb des UNECE-Typgenehmigungsrahmens
E-Mark	Kennzeichnung im Zusammenhang mit der erteilten Typgenehmigung

11.7 Ein erfolgreicher Test ist trotzdem ein wichtiger Schritt

Die Tatsache, dass ein Prüfbericht keine Typgenehmigung darstellt, bedeutet nicht, dass die Prüfung unwichtig ist.

Im Gegenteil.

Die erfolgreich durchgeführte Prüfung liefert einen wesentlichen technischen Nachweis für den Genehmigungsprozess.

Ohne die erforderlichen technischen Nachweise kann die Genehmigungsbehörde die Konformität nicht auf der vorgesehenen Grundlage bewerten.

Der Prüfbericht ist daher ein Baustein der Typgenehmigung, aber nicht automatisch die Typgenehmigung selbst.

11.8 Die Bedeutung der geprüften Konfiguration

Ein weiterer wichtiger Punkt ist, dass sich ein Prüfbericht immer auf eine konkrete Prüfkonfiguration bezieht.

Dazu können gehören:

• bestimmte Hardware;
• bestimmte Software;
• bestimmte Kabel;
• bestimmte Kabelbäume;
• bestimmte Lasten;
• bestimmte Betriebsmodi;
• bestimmte Installationsbedingungen.

Wenn der Hersteller nach der Prüfung Änderungen am Produkt vornimmt, kann die Aussagekraft des ursprünglichen Prüfberichts dadurch beeinflusst werden.

Beispielsweise können relevant sein:

• PCB-Änderungen;
• neue elektronische Komponenten;
• Änderungen der Stromversorgung;
• neue Kommunikationsschnittstellen;
• Änderungen der Kabellängen;
• Änderungen der Schirmung;
• Softwareänderungen;
• Änderungen des Betriebsmodus.

Deshalb muss nach einer Produktänderung bewertet werden, ob die bestehende technische Evidenz weiterhin für die genehmigte Konfiguration gilt.

11.9 Prüfbericht und Typgenehmigung im Projektablauf

Der Zusammenhang lässt sich vereinfacht so darstellen:

1. Produkt definieren

↓

2. ECE-R10-Anwendbarkeit und Umfang bestimmen

↓

3. Prüfkonfiguration festlegen

↓

4. Prüfungen durchführen

↓

5. Prüfergebnisse dokumentieren

↓

6. Technische Dokumentation und Nachweise zusammenführen

↓

7. Genehmigungsprozess abschließen

↓

8. Typgenehmigung

Der Prüfbericht befindet sich damit innerhalb des gesamten Genehmigungsprozesses.

Er ist nicht dessen Endpunkt.

11.10 Was Hersteller gegenüber Kunden kommunizieren sollten

Bei der Kommunikation des Compliance-Status sollte der Hersteller möglichst präzise formulieren.

Statt pauschal zu schreiben:

„ECE R10 certified“

sollte eindeutig feststehen, ob tatsächlich eine entsprechende Typgenehmigung erteilt wurde.

Wenn lediglich Prüfungen durchgeführt wurden, ist eine Formulierung wie:

„The product has been tested against the applicable ECE R10 requirements.“

inhaltlich etwas anderes als:

„The product has received ECE R10 type approval.“

Diese Unterscheidung ist nicht nur sprachlich relevant. Sie beschreibt zwei unterschiedliche Stufen des regulatorischen Prozesses.

11.11 Fazit

Eine ECE-R10-Prüfung und eine ECE-R10-Typgenehmigung sind zwei unterschiedliche Dinge.

Der EMV-Prüfbericht dokumentiert die technischen Ergebnisse einer bestimmten Prüfung und Konfiguration.

Die ECE-R10-Typgenehmigung ist dagegen die formale regulatorische Genehmigung innerhalb des UNECE-Fahrzeug-Typgenehmigungsrahmens.

Deshalb gilt:

Ein erfolgreicher EMV-Prüfbericht ist nicht automatisch eine ECE-R10-Typgenehmigung.

Für Hersteller ist es entscheidend, diesen Unterschied zu verstehen und den tatsächlichen Genehmigungsstatus eindeutig zu dokumentieren.

Technische Prüfung ist der Nachweis.
Typgenehmigung ist der regulatorische Status.

Control the Scope. Control the Cost.

12. The E-Mark and ECE R10 Approval

One of the most visible signs of an ECE R10 type approval is the E-mark.

For manufacturers, however, the E-mark is more than a symbol placed on a product. It identifies a formal type approval granted under the UNECE framework and provides information about the country that granted the approval and the corresponding approval number.

This makes the E-mark fundamentally different from the CE marking used under EU product legislation.

Understanding what the E-mark actually represents is important when reviewing automotive compliance documentation, checking an existing approval, or communicating an approval status to customers.

12.1 What is the E-mark?

The E-mark is the approval marking associated with type approvals granted under the UNECE 1958 Agreement.

It consists of a capital E together with a distinguishing number identifying the Contracting Party that granted the approval.

For an ECE R10 approval, the marking also identifies the relevant UN Regulation and the approval number.

A simplified example is:

E4

followed by information identifying:

UN Regulation No. 10 → approval number

The exact marking format depends on the applicable version and marking provisions of the relevant regulation.

UNECE examples for UN Regulation No. 10 show an approval mark consisting of the country identifier inside a circle together with the R10 approval information.

12.2 What does the number after the “E” mean?

The number associated with the E identifies the Contracting Party that granted the type approval.

For example:

E number	Contracting Party
E1	Germany
E2	France
E3	Italy
E4	Netherlands
E5	Sweden
E6	Belgium
E7	Hungary
E8	Czech Republic
E9	Spain
E11	United Kingdom
E12	Austria
E13	Luxembourg
E16	Norway
E17	Finland
E18	Denmark
E19	Romania
E20	Poland
E21	Portugal
E24	Ireland

The number therefore does not identify where the product was manufactured.

It identifies the Contracting Party whose approval authority granted the type approval.

The country-code system is defined within the UNECE framework.

12.3 E1, E4, E11, E13 – does the country matter?

This is one of the most common questions surrounding E-mark approvals.

Suppose a manufacturer obtains an R10 approval carrying:

E1

and another manufacturer obtains an R10 approval carrying:

E13

The two approvals are not automatically different in their technical requirements simply because the approval was issued by different countries.

The important point is that both approval authorities operate within the UNECE type-approval framework and apply the relevant UN Regulation.

The E number identifies who granted the approval, not a different version of R10.

This is why manufacturers sometimes have a choice regarding which Contracting Party they approach for an approval.

However, the practical approval route, authority, technical service, documentation requirements, lead time and commercial conditions can differ.

That subject becomes particularly important when comparing countries such as Germany, Luxembourg and the United Kingdom.

12.4 What does the approval number tell you?

The approval number provides information about the approval itself.

Under the current UNECE type-approval numbering structure, an approval number contains several elements.

The general structure includes:

1. The E number identifying the Contracting Party;
2. the relevant UN Regulation number;
3. information about the series of amendments applied;
4. the sequential approval number; and
5. an extension number where applicable.

The current UNECE framework defines a four-section approval-number structure.

This means that an approval number is not simply an internal reference.

It can provide information about the regulatory basis under which the approval was granted.

12.5 Example of an R10 approval marking

UNECE provides examples of R10 approval markings.

An example from the regulation shows a marking corresponding to an approval granted in the Netherlands:

E4

with the R10 approval information:

10 R – 06 2439

The example indicates that the approval was granted in the Netherlands under UN Regulation No. 10 and that the approval was based on the 06 series of amendments.

The exact format of approval markings can change with revisions of the regulatory framework, so manufacturers should always refer to the applicable version of UN R10 rather than assuming that an older marking example represents the current format.

12.6 The E-mark is not the CE mark

The distinction between the two markings is essential.

CE marking

The CE marking is associated with applicable European Union product legislation.

Depending on the product, this can involve legislation such as:

• EMC legislation;
• Radio Equipment Directive;
• Machinery legislation;
• Low Voltage Directive;
• other applicable EU legislation.

E-mark

The E-mark is associated with type approvals granted under the UNECE vehicle regulatory framework.

For an R10 approval, it indicates that the relevant vehicle or ESA has received approval with regard to electromagnetic compatibility under UN Regulation No. 10.

Therefore:

CE ≠ E-mark

and:

CE marking ≠ ECE R10 type approval

They belong to different regulatory systems.

12.7 Does an E-mark mean the product passed an EMC test?

The E-mark indicates an approval status, not merely that someone performed an EMC test.

An R10 approval is based on the applicable type-approval process, including the relevant technical evidence and assessment.

The underlying testing is an important part of that process.

However, the presence of an E-mark should be understood as evidence of the formal approval, rather than simply evidence that an EMC laboratory test was performed.

This distinction is important when reviewing supplier documentation.

A document saying:

“EMC Test Report – Pass”

is not equivalent to a product carrying or being covered by a valid:

ECE R10 Type Approval

12.8 Can an ESA carry an E-mark?

Yes.

UN Regulation No. 10 contains approval provisions for electrical/electronic sub-assemblies.

Depending on the approval route and applicable requirements, an ESA can therefore be subject to an R10 type approval and associated approval marking.

This is particularly relevant for manufacturers supplying electronic equipment directly to vehicle manufacturers or into automotive supply chains.

A component supplier may therefore need to understand not only the technical EMC requirements but also whether the customer expects the component to have its own type approval.

12.9 Does every automotive component need an E-mark?

No.

This is an important distinction.

The fact that a product is used in a vehicle does not automatically mean that it must carry its own E-mark.

The applicable approval strategy depends on factors such as:

• the type of equipment;
• its intended installation;
• its function;
• its relationship to the vehicle;
• the applicable vehicle type-approval framework;
• whether it is treated as an ESA;
• and the approval strategy of the vehicle manufacturer.

In some cases, a component may be covered within the vehicle manufacturer’s overall type-approval strategy rather than requiring a separate approval in the same way as another ESA.

The regulatory status therefore needs to be determined before assuming that an E-mark is required.

12.10 What does the E-mark tell a customer?

An E-mark can provide a customer with a quick indication that an approved configuration exists.

However, the marking alone does not necessarily tell the complete story.

A proper compliance review should also establish:

• the approval number;
• the applicable UN Regulation;
• the series of amendments;
• the approval authority;
• the approved product or type;
• the scope of the approval;
• applicable variants;
• approval extensions;
• and whether the supplied product corresponds to the approved configuration.

This is particularly important when a manufacturer has multiple hardware versions or product variants.

An E-mark should therefore be treated as a starting point for verification rather than as a substitute for reviewing the underlying approval documentation.

12.11 Approval marking and product changes

A manufacturer may have a valid E-marked approval and later modify the product.

For example:

• a PCB may be redesigned;
• a component may be replaced;
• the software may change;
• a connector may be modified;
• the cable configuration may change;
• the enclosure may be changed;
• a communication interface may be added.

The existence of an existing E-mark does not mean that every future product configuration is automatically covered.

The manufacturer must assess whether the change remains within the approved type or requires additional technical assessment, testing or an extension of the approval.

This is why configuration management is an essential part of maintaining an R10 approval.

12.12 What is an approval extension?

Type approvals can be extended when changes or additional variants need to be incorporated into an existing approval.

The exact process depends on the applicable regulation and approval authority.

An extension can be relevant when, for example:

• a product variant is added;
• a hardware change is introduced;
• a new vehicle application is added;
• an additional configuration is covered;
• a technical modification affects the approved type.

The approval documentation should therefore be checked whenever the product changes.

The manufacturer should not simply assume:

“The original E-mark still covers everything.”

Instead, the manufacturer should establish whether the change remains within the existing approval scope.

12.13 Why the E number can matter commercially

Although the technical requirements come from the UNECE regulation, the choice of approval authority can have practical consequences.

Manufacturers may compare potential approval routes based on:

• availability of the relevant approval authority;
• technical-service capacity;
• lead time;
• administrative process;
• communication;
• project coordination;
• cost;
• existing relationships;
• customer expectations.

This is one reason why manufacturers sometimes consider approvals through different Contracting Parties.

For example, an approval carrying:

E1

is not automatically technically superior to one carrying:

E13

The E number identifies the granting Contracting Party.

The important question is whether the approval itself is valid and applicable to the intended product and market.

12.14 Can an E13 approval be used outside Luxembourg?

Yes, subject to the applicable UNECE mutual-recognition framework and the specific regulatory requirements of the destination market.

This is one of the fundamental characteristics of the UNECE 1958 Agreement.

The purpose of the agreement is to establish harmonized technical requirements and reciprocal recognition of type approvals granted under the relevant UN Regulations.

Therefore, an R10 approval granted by one Contracting Party is not intended to be treated as a purely domestic approval limited to that country.

This is also why the E number should not be interpreted as a geographic limitation on where the approved product can be used.

The exact legal recognition for a particular application should nevertheless be checked against the applicable type-approval framework and market requirements.

12.15 What about the United Kingdom?

The United Kingdom has its own E number within the UNECE system:

E11

The UK remains a Contracting Party to the UNECE 1958 Agreement and has designated approval authorities and technical services for UN Regulations.

Therefore, an R10 approval granted through the UK within the UNECE framework can carry an E11 marking.

This is important after Brexit because the UK can participate in the UNECE type-approval system independently of its former EU membership.

The distinction between UNECE approval and separate GB type-approval requirements should nevertheless be considered for the specific market and product.

The UK situation is therefore not simply:

“Brexit = E11 approvals are no longer relevant in Europe.”

The UNECE framework continues to operate independently of EU membership.

12.16 Why manufacturers should not choose an approval country based only on the E number

It can be tempting to think:

“E13 is easier, so we should always use Luxembourg.”

or:

“E1 is Germany, so it must be more accepted.”

Neither assumption is sufficient.

The E number itself does not determine the technical quality of the approval.

The relevant questions are:

• Is the authority competent for the required approval?
• Is the relevant Technical Service available?
• Can the required tests be performed?
• Is the documentation acceptable?
• What is the expected lead time?
• What are the total costs?
• Is the approval route suitable for the intended vehicle and product?
• Are there customer-specific requirements?
• How will future extensions be handled?

The country of approval can therefore be a project-management and commercial consideration, but it should not be confused with a different technical version of R10.

12.17 How to verify an E-mark

When reviewing an E-mark or R10 approval document, the manufacturer should verify at least:

Approval identity

• E number
• Approval number
• UN Regulation number
• Amendment series

Product identity

• Manufacturer
• Type designation
• Model
• Hardware/configuration
• Relevant variants

Approval scope

• Vehicle or ESA
• Applicable configurations
• Installation conditions
• Covered variants

Approval status

• Original approval
• Extensions
• Amendments
• Current validity/status

Supporting evidence

• Test report
• Technical documentation
• Approval documentation

This provides a much more reliable compliance check than simply looking for the letter E on the product.

12.18 Key takeaway

The E-mark is the visible identifier associated with a UNECE type approval.

For ECE R10, it provides information about the Contracting Party that granted the approval and the corresponding approval under UN Regulation No. 10.

The most important points are:

E1 does not mean “better than E13.”

E13 does not mean “only valid in Luxembourg.”

E11 identifies the United Kingdom as the Contracting Party granting the approval.

And most importantly:

The E-mark should not be confused with CE marking or with a simple EMC test report.

For manufacturers, the E-mark is best understood as the visible result of a formal type-approval process. To determine exactly what has been approved, the underlying approval number, scope, configuration and documentation must still be reviewed.

13. Where Can ECE R10 Approval Be Obtained?

ECE R10 approvals are not limited to the country where the manufacturer is located or where the vehicle will ultimately be sold.

The approval system is based on the UNECE 1958 Agreement, under which Contracting Parties designate Type Approval Authorities and Technical Services for the relevant UN Regulations. A manufacturer can therefore work with an appropriate approval authority in another Contracting Party, provided that the authority is applying the relevant regulation and is competent for the required approval scope.

This is one of the practical differences between an ECE R10 type-approval project and many national product-certification schemes.

The important question is not simply:

“In which country is our company located?”

It is:

“Which approval authority and Technical Service are suitable for our specific ECE R10 project?”

13.1 The basic structure of the approval system

The UNECE 1958 Agreement establishes the framework for mutual recognition of type approvals granted under the applicable UN Regulations.

Within this system, Contracting Parties designate:

• a Type Approval Authority;
• one or more Technical Services;
• and the specific UN Regulations for which they are designated.

UNECE maintains an official overview of the Contracting Parties, their designated Type Approval Authorities and Technical Services.

The basic structure is therefore:

UNECE / 1958 Agreement

↓

Contracting Party

↓

Type Approval Authority

↓

Technical Service

↓

Testing and technical assessment

↓

Type Approval

The Technical Service performs or supervises the technical work within its designation.

The Type Approval Authority is responsible for the formal approval.

13.2 Does the approval have to be obtained in the manufacturer’s country?

No.

A manufacturer does not generally have to obtain an ECE R10 approval from the authority of the country in which the manufacturer is established.

This is one of the advantages of the UNECE type-approval framework.

For example, a manufacturer located in Germany may potentially use an approval route involving another UNECE Contracting Party, provided the relevant authority applies UN Regulation No. 10 and has the necessary designation and competence for the approval.

The same principle applies to manufacturers outside the European Union that want to use the UNECE system.

The relevant question is whether the selected authority can legally grant the required approval under the applicable UN Regulation.

13.3 What is the role of the Type Approval Authority?

The Type Approval Authority is the governmental or officially designated authority responsible for granting the type approval.

Its responsibilities can include:

• reviewing the application;
• assessing the required documentation;
• ensuring that the necessary technical evidence is available;
• granting the type approval;
• issuing approval documentation;
• handling extensions and modifications;
• overseeing conformity-of-production requirements;
• and taking action if the approved type no longer complies with the applicable requirements.

The authority is therefore more than an administrative mailbox.

It is the entity responsible for the formal regulatory approval.

The UNECE framework requires each Contracting Party applying a UN Regulation to designate the relevant Type Approval Authority.

13.4 What is the role of the Technical Service?

The Technical Service is responsible for the technical side of the approval process.

Depending on its designation, this can include:

• performing tests;
• supervising tests;
• assessing technical documentation;
• carrying out inspections;
• evaluating test results;
• supporting the Type Approval Authority in determining compliance.

The Technical Service does not simply act as an ordinary commercial laboratory.

Its work is performed within a formally designated type-approval framework.

This distinction is important because not every laboratory that can technically perform an EMC test is automatically a Technical Service for ECE R10.

The Technical Service must have the relevant designation for the applicable subject and regulation.

13.5 Not every laboratory can issue an ECE R10 approval

This is a common misunderstanding.

A laboratory may be technically capable of performing automotive EMC testing without being able to issue an ECE R10 type approval.

The laboratory needs to have the appropriate status within the applicable type-approval system.

The UNECE framework specifically distinguishes between Type Approval Authorities and Technical Services, and Contracting Parties notify UNECE of the authorities and services designated for particular regulations.

Therefore, when selecting a laboratory, manufacturers should ask:

• Is the laboratory a designated Technical Service?
• Is it designated for UN Regulation No. 10?
• Which series of amendments is covered?
• Does the designation cover the specific approval subject?
• Is the specific laboratory site covered?
• Can the Technical Service perform the required testing or supervise it?

The last point can be particularly important because a Technical Service’s designation can be limited to specific regulations, activities or locations.

13.6 Germany

Germany is one of the major UNECE type-approval jurisdictions.

The German Kraftfahrt-Bundesamt (KBA) is the federal authority responsible for vehicle type approval and participates in the UNECE type-approval framework.

For an R10 project using the German route, the KBA acts as the Type Approval Authority, while the relevant technical work is performed or supervised by appropriately designated Technical Services.

Germany therefore provides a complete established infrastructure for UNECE type approval.

For manufacturers already working extensively with German automotive authorities or German vehicle manufacturers, this can be a natural approval route.

However, that does not mean that Germany is automatically the best route for every R10 project.

The suitability of the route still depends on:

• product type;
• approval scope;
• Technical Service availability;
• project timing;
• documentation;
• costs;
• customer requirements;
• and future extensions.

13.7 Luxembourg

Luxembourg is also a Contracting Party to the UNECE 1958 Agreement and is identified within the UNECE system by E13.

This means that Luxembourg can participate in the UNECE type-approval framework for the UN Regulations it applies and for which the relevant authorities and Technical Services are designated. UNECE’s current information identifies Luxembourg as E13 and provides the applicable designation information for its authorities and services.

This is important because a Luxembourg approval is not simply a Luxembourg national approval.

A properly granted UNECE approval under UN Regulation No. 10 belongs to the international UNECE type-approval framework.

The fact that the approval carries E13 therefore identifies the Contracting Party that granted it; it does not mean that the approval is restricted to products sold or installed in Luxembourg.

13.8 Why Luxembourg can be considered as an approval route

Manufacturers sometimes consider Luxembourg as an alternative to larger approval jurisdictions such as Germany.

The reason is not that Luxembourg has a fundamentally different technical version of ECE R10.

The underlying UNECE regulation remains the relevant technical basis.

Instead, manufacturers may consider differences in:

• administrative handling;
• availability of the relevant authority;
• Technical Service capacity;
• communication;
• project coordination;
• lead time;
• cost structure;
• and practical accessibility.

These factors can make one approval route more attractive than another for a particular project.

However, the assumption that “Luxembourg is always easier” should not be treated as a regulatory rule.

The practical experience can depend heavily on the product, Technical Service, project complexity and current authority capacity.

13.9 The United Kingdom

The United Kingdom is also part of the UNECE 1958 Agreement.

For UNECE approvals, the Vehicle Certification Agency (VCA) is the designated UK Type Approval Authority. VCA also designates Technical Services for UNECE approval testing.

The UK therefore remains a viable route for an ECE R10 approval.

A UNECE approval granted through the UK can carry the UK’s E number:

E11

The UK’s participation in the UNECE system is particularly important because it is separate from the UK’s post-Brexit national type-approval framework.

This means that:

UNECE approval through the UK

and

GB national type approval

are not the same thing.

VCA explicitly distinguishes between the UN/UNECE system and the separate GB type-approval framework.

13.10 UNECE approval and the UK market

This distinction is particularly relevant for manufacturers targeting the United Kingdom.

The UK currently has several possible approval routes depending on the product, vehicle category and market:

• UNECE type approval;
• GB type approval;
• UK(NI) type approval;
• and, in certain circumstances, recognition of EU approvals.

VCA identifies UN type approvals as a route primarily used for systems, components and separate technical units within the UNECE 1958 Agreement framework.

Therefore, a manufacturer should not automatically assume that obtaining an E11 R10 approval is equivalent to obtaining a complete GB type approval.

The appropriate route depends on what exactly is being approved and where it is intended to be placed on the market.

13.11 UNECE approvals can be used internationally

One of the major advantages of the UNECE system is the principle of reciprocal recognition between Contracting Parties applying the relevant UN Regulation.

The UK VCA, for example, explicitly states that UK-issued UNECE type approvals are accepted by the other Contracting Parties applying the relevant regulation.

This means that the country issuing the approval should not be confused with the geographic market in which the approved product can be used.

For example:

E13

does not mean:

“only Luxembourg.”

Similarly:

E11

does not mean:

“only United Kingdom.”

And:

E1

does not mean:

“only Germany.”

The E number identifies the granting Contracting Party.

13.12 Why the choice of approval authority still matters

If approvals are mutually recognized, manufacturers may reasonably ask:

Why not simply choose the cheapest authority?

In practice, the answer is more complicated.

The approval route can influence:

• project coordination;
• communication;
• lead time;
• Technical Service availability;
• laboratory capacity;
• documentation requirements;
• technical interpretation;
• production conformity arrangements;
• extensions;
• modifications;
• and overall project cost.

A technically valid approval route can therefore still be a poor project choice if it creates unnecessary delays or complications later.

The best approval route is not necessarily the one with the lowest initial quotation.

It is the one that provides the most suitable combination of:

regulatory suitability + technical capability + project timing + cost + long-term support.

13.13 Availability of Technical Services is critical

One of the most practical constraints can be the availability of a suitable Technical Service.

A Type Approval Authority may be able to grant an R10 approval, but the manufacturer still needs the required technical work to be performed by an appropriately designated service.

This can become particularly relevant for specialized or complex products.

Before selecting an approval route, manufacturers should therefore verify:

• which Technical Services are designated;
• which R10 activities they cover;
• which amendment series they cover;
• which locations are covered;
• whether they have current capacity;
• whether they can support the required testing;
• whether they can support future extensions.

The UK VCA, for example, explicitly warns that manufacturers should establish which specific regulations and amendment series are covered by a Technical Service’s designation and which sites are designated.

The same principle applies generally within the UNECE system.

13.14 The approval route should be selected before testing starts

A manufacturer should ideally decide on the approval route before finalizing the laboratory test program.

Otherwise, there is a risk that testing is performed under assumptions that do not fully match the eventual approval process.

A sensible sequence is:

Product definition

↓

R10 applicability

↓

Approval object

↓

Applicable R10 version

↓

Potential approval authorities

↓

Suitable Technical Service

↓

Test scope

↓

Testing

↓

Approval

This sequence helps prevent a common mistake:

performing technically valid tests without first establishing how those tests will be used within the actual type-approval process.

13.15 What manufacturers should compare

When considering different approval routes, manufacturers should compare more than the laboratory price.

A useful comparison can include:

Criteria	Questions to ask
Regulatory scope	Is the authority designated for the required R10 approval?
Technical Service	Is the required R10 testing within its designation?
Amendment series	Does the designation cover the applicable version?
Test capacity	Can the required testing be scheduled within the project timeline?
Documentation	What information is required before testing?
Lead time	What is the realistic end-to-end timeline?
Cost	What are the total authority, Technical Service and testing costs?
Extensions	How are future product variants handled?
Communication	Can the project be managed efficiently?
Customer requirements	Does the vehicle manufacturer require a particular approval route?

This makes it possible to compare approval routes on the basis of the complete project, rather than only the initial testing price.

13.16 The approval authority does not replace the manufacturer’s responsibility

Choosing a recognized authority and Technical Service does not transfer the manufacturer’s responsibility for product compliance.

The manufacturer remains responsible for ensuring that:

• the correct product is submitted;
• the technical information is accurate;
• the tested configuration represents the intended product;
• production remains consistent with the approved type;
• relevant changes are assessed;
• the approval documentation remains accurate.

Conformity of Production is a fundamental part of the UNECE type-approval system. UNECE states that the approval authority must establish that adequate production controls are in place before granting type approval and can verify continued conformity afterward.

The approval route therefore needs to be viewed as a complete compliance process, not simply as a laboratory booking.

13.17 Can a manufacturer change approval authority later?

This should not be treated as a simple administrative switch.

The approval is associated with the authority that granted it, and changes, extensions and other approval activities are handled through the applicable regulatory procedures.

If a manufacturer anticipates significant future product development, it should therefore consider the long-term suitability of the original approval route.

Relevant questions include:

• Will additional variants be required?
• Will the product be installed in different vehicles?
• Are major hardware changes expected?
• Will software be updated frequently?
• Will future approval extensions be needed?
• Will the same Technical Service remain available?

Choosing an approval route should therefore be part of the long-term product compliance strategy.

13.18 The practical reality: there is no universally “best” country

Germany, Luxembourg and the United Kingdom can all be relevant to an ECE R10 project.

However, there is no universal rule saying:

Germany = best

or:

Luxembourg = easiest

or:

UK = cheapest

The practical situation depends on the individual project.

A small ESA with a straightforward configuration may have a very different approval path from a complex electronic system intended for multiple vehicle platforms.

The availability and designation of Technical Services can also change over time.

For that reason, manufacturers should treat the choice of approval route as a project decision that needs to be evaluated, rather than as a fixed rule based solely on the E number.

13.19 A useful decision process

Before selecting an authority, a manufacturer can ask five basic questions:

1. Is the authority applying UN R10?

If not, it cannot be used for the intended UNECE R10 approval.

2. Is there a suitable designated Technical Service?

The Technical Service must have the required designation for the relevant R10 scope.

3. Can the required testing be performed within the required timeframe?

Technical capability is not enough if the required capacity is unavailable.

4. Does the route fit the intended market and approval strategy?

The manufacturer should distinguish between UNECE approval and any separate national requirements.

5. Is the route suitable for the product’s future lifecycle?

Extensions, modifications and future variants should be considered from the beginning.

13.20 Key takeaway

ECE R10 approval does not have to be obtained in the same country where the manufacturer is located.

The UNECE 1958 Agreement provides an international framework in which Contracting Parties designate Type Approval Authorities and Technical Services for the relevant UN Regulations.

Germany, Luxembourg and the United Kingdom are all part of this system and can therefore be relevant approval routes.

The most important point is:

The E number identifies the Contracting Party granting the approval. It does not define the geographic market of the approved product.

For manufacturers, the better question is therefore not:

“Which country has the easiest ECE R10 approval?”

but:

“Which approval authority and Technical Service provide the most suitable regulatory, technical and commercial route for our specific product?”

That decision should ideally be made before testing begins, because the approval route, Technical Service and applicable requirements form part of the overall compliance strategy.

14. Germany vs. Luxembourg vs. UK

When planning an ECE R10 type-approval project, manufacturers may have several possible approval routes. Germany, Luxembourg and the United Kingdom are three examples that can be relevant.

At first glance, the E-numbers make the choice appear simple:

• E1 → Germany
• E13 → Luxembourg
• E11 → United Kingdom

However, the E-number alone does not tell a manufacturer which route is best.

All three countries participate in the UNECE 1958 Agreement, and the UNECE framework provides for designated Type Approval Authorities and Technical Services. The practical differences therefore arise less from the underlying R10 technical requirements and more from which authority and Technical Service are available, how the project is handled, what capacity exists, and what the manufacturer’s overall market and approval strategy looks like.

14.1 E1, E13 and E11 – what do the numbers mean?

The E-number identifies the Contracting Party that granted the approval.

For the three countries discussed here:

E number	Contracting Party
E1	Germany
E11	United Kingdom
E13	Luxembourg

These identifiers are part of the UNECE approval system. They do not mean that the approval is geographically restricted to the issuing country.

This distinction is particularly important when manufacturers compare approval routes.

An E13 approval is not a “Luxembourg-only” approval.

Likewise, an E11 UNECE approval is not simply a UK-only approval.

The relevant UNECE regulation and its recognition rules determine where the approval can be used.

14.2 The technical requirements are not simply different versions of R10

A common misconception is that choosing Germany, Luxembourg or the UK means choosing between three different technical versions of ECE R10.

That is not how the UNECE system works.

The underlying technical requirements originate from UN Regulation No. 10.

The Contracting Party provides the approval framework through its designated authority and Technical Services.

Therefore, a manufacturer should not expect:

Germany → one R10

Luxembourg → another R10

UK → another R10

Instead, the manufacturer should expect the relevant authority and Technical Service to apply the applicable version and requirements of UN R10 within the UNECE framework.

The important practical differences are therefore more likely to concern the approval route and project execution than a fundamentally different EMC requirement.

14.3 Germany – E1

Germany is an established participant in the UNECE type-approval system and uses E1 as its country identifier.

The Kraftfahrt-Bundesamt (KBA) is the German federal authority responsible for vehicle type approval.

For manufacturers already working with German automotive customers, suppliers and technical organizations, the German route can be a natural choice.

Potential advantages can include:

• established automotive infrastructure;
• proximity for German manufacturers;
• extensive experience with European vehicle type approval;
• access to established Technical Services;
• familiarity with German automotive supply chains.

However, choosing Germany does not automatically mean that the project will be faster or cheaper.

The actual project experience depends heavily on:

• the selected Technical Service;
• test capacity;
• product complexity;
• required testing;
• documentation;
• project timing;
• and the authority’s current workload.

Germany should therefore be considered as one suitable route, rather than automatically the default route for every manufacturer.

14.4 Luxembourg – E13

Luxembourg uses E13 within the UNECE approval system.

The country is a Contracting Party to the 1958 Agreement and can issue UNECE approvals for the UN Regulations it applies through its designated approval framework. UNECE publishes the relevant contracting-party and designation information.

For manufacturers, Luxembourg can therefore be considered as an alternative approval jurisdiction.

This is particularly interesting because the size of the country does not prevent it from participating in the international UNECE type-approval framework.

The key question is not:

“Is Luxembourg a large automotive country?”

The relevant question is:

“Can the competent Luxembourg authority and its designated Technical Service provide the approval route required for this project?”

If the answer is yes, the size of the country itself is not a reason to exclude the route.

14.5 Why do manufacturers sometimes consider Luxembourg?

In practical discussions, Luxembourg is sometimes perceived as offering a more straightforward route than larger approval jurisdictions.

There can be reasons why a particular project experiences this.

For example:

• smaller administrative structures;
• potentially direct communication;
• availability of the relevant authority;
• availability of a suitable Technical Service;
• project-specific lead times;
• different cost structures.

However, none of these factors should be treated as a permanent regulatory advantage.

A statement such as:

“ECE R10 is easier in Luxembourg.”

is too broad.

A more accurate statement would be:

“For some projects, the Luxembourg approval route may be more practical depending on the authority, Technical Service, capacity and project requirements.”

That distinction is important.

14.6 United Kingdom – E11

The United Kingdom is also a Contracting Party to the UNECE 1958 Agreement.

The Vehicle Certification Agency (VCA) is the designated UK Type Approval Authority for the associated UN regulations. VCA also has its own Technical Service and designates additional Technical Services for UNECE testing.

The UK therefore remains a genuine option for UNECE R10 approval.

A UK-issued UNECE approval carries the E11 identifier.

The UK’s continued participation in the UNECE framework is especially relevant after Brexit because manufacturers sometimes incorrectly assume that Brexit removed the UK from the UNECE approval system.

It did not.

14.7 The UK requires an important distinction

The United Kingdom now has multiple type-approval frameworks.

This means that manufacturers must distinguish between:

UNECE approval

and

GB type approval

These are not the same thing.

VCA explicitly identifies United Nations type approval as one of the approval routes available for the UK and distinguishes it from the separate GB and UK(NI) schemes.

For components and separate technical units, UNECE approval remains particularly relevant.

Therefore, a manufacturer considering an E11 R10 approval should not automatically interpret this as a GB national type approval.

The approval route has to be selected according to the product and the intended market.

14.8 UNECE approval can still be highly relevant for the UK

The UK VCA states that UNECE type approvals are internationally recognized within the UNECE framework and continue to be accepted in the UK and EU markets under the applicable arrangements.

This makes the UNECE route particularly interesting for manufacturers supplying automotive components internationally.

A manufacturer may therefore have a genuine reason to consider an E11 UNECE approval even if the manufacturer is not primarily targeting the UK market.

The reason is that the approval is part of an international regulatory framework rather than being merely a national UK certification.

14.9 Germany vs. Luxembourg vs. UK – the basic comparison

At a high level, the three routes can be compared as follows:

Factor	Germany	Luxembourg	United Kingdom
UNECE Contracting Party	Yes	Yes	Yes
E-number	E1	E13	E11
UNECE R10 route	Yes	Yes, where designated	Yes
National authority	KBA	Competent Luxembourg authority	VCA
Technical Services	Designated under UNECE framework	Designated under UNECE framework	VCA and designated external services
EU country	Yes	Yes	No
UNECE framework after Brexit	N/A	N/A	Yes
Separate national vehicle approval system	EU type-approval framework	EU type-approval framework	GB / UK(NI) systems
Potentially relevant for international component approval	Yes	Yes	Yes

The table should not be interpreted as meaning that all three routes are interchangeable for every product.

The actual applicability depends on the relevant approval scope and the designation of the authority and Technical Service.

14.10 The Technical Service can matter more than the country

This is one of the most important practical points.

A manufacturer may initially focus on the country:

Germany or Luxembourg or UK?

But the better question is often:

Which Technical Service can actually handle our R10 project?

For example, a Technical Service may have:

• the necessary R10 designation;
• the required EMC facilities;
• experience with the relevant product type;
• available test capacity;
• suitable test locations;
• experience with the relevant vehicle manufacturer.

UNECE maintains information about designated authorities and Technical Services, while national approval authorities publish more detailed information about their designations.

The VCA, for example, specifically warns that manufacturers should verify the specific regulations, amendment series and designated sites covered by a Technical Service.

This is a very important practical consideration.

A Technical Service being generally “designated for UNECE” does not necessarily mean that it is designated for every UN Regulation, every amendment series or every location.

14.11 Availability can change the best route

Suppose a manufacturer has three technically suitable options.

Germany

The required Technical Service is fully booked for several months.

Luxembourg

The relevant Technical Service can start within a few weeks.

UK

The Technical Service has suitable capacity but requires a longer administrative preparation period.

In that situation, the best route may not be determined by the country itself.

It may simply be determined by project availability.

This is why an R10 approval strategy should consider current project conditions rather than relying on general assumptions about a particular country.

14.12 Cost should be compared at project level

The cheapest laboratory quotation does not necessarily represent the cheapest approval route.

A realistic comparison should include:

• Technical Service fees;
• Type Approval Authority fees;
• laboratory testing;
• sample preparation;
• transportation;
• travel;
• documentation;
• engineering support;
• retesting;
• potential extensions;
• administrative fees;
• project management.

A route that appears €2,000 cheaper at the beginning can become more expensive if it requires additional coordination, longer lead times or repeated testing.

Conversely, a slightly more expensive initial route may prove more efficient if the project can be completed correctly on the first attempt.

The relevant figure is therefore:

Total project cost

rather than:

Laboratory test price

14.13 Lead time should be evaluated realistically

Manufacturers often ask:

“How long does ECE R10 take?”

There is no universal answer.

The total duration depends on:

• scope definition;
• availability of the Technical Service;
• product readiness;
• documentation;
• sample availability;
• test duration;
• test failures;
• corrective actions;
• report preparation;
• authority review;
• approval issuance.

A laboratory may quote only the physical test duration.

For example:

“Testing: 3 days.”

That does not necessarily mean:

“ECE R10 approval in 3 days.”

The complete project may take substantially longer.

Therefore, when comparing Germany, Luxembourg and the UK, manufacturers should compare end-to-end lead time, not merely laboratory test time.

14.14 Customer requirements can override the preferred route

A manufacturer may prefer Luxembourg because of cost or lead time.

However, the vehicle manufacturer may have its own requirements.

An OEM may specify:

• preferred Technical Services;
• accepted approval authorities;
• specific test facilities;
• specific test procedures;
• customer-specific EMC requirements;
• preferred documentation;
• specific approval management processes.

This can significantly influence the choice of approval route.

Therefore, before selecting an authority, a component manufacturer should determine whether its customer has already specified an approval or testing strategy.

The theoretically most efficient route is not always the commercially acceptable route.

14.15 The E-number should not be used as a quality ranking

It is tempting to interpret the E-number as an indicator of the quality or difficulty of the approval.

That would be incorrect.

There is no regulatory hierarchy such as:

E1 > E13 > E11

or:

E13 = easier than E1

The number identifies the Contracting Party.

It does not indicate:

• approval quality;
• EMC requirements;
• product quality;
• market acceptance;
• test severity;
• or regulatory importance.

A properly issued UNECE approval is part of the same international regulatory framework, subject to the applicable UN Regulation and recognition rules.

14.16 What about an E11 approval after Brexit?

This deserves particular attention because the UK situation is often misunderstood.

The UK’s participation in the UNECE 1958 Agreement continued after Brexit.

VCA remains the UK’s designated Type Approval Authority for UNECE approvals.

Therefore:

E11 UNECE approval still exists.

However:

E11 UNECE approval ≠ GB national type approval.

For vehicle manufacturers placing complete vehicles on the GB market, the separate GB type-approval regime can become relevant. VCA currently states that, from February 2026, M and N category vehicle types must hold full GB or UKNI type approval to be manufactured for sale in Great Britain.

For components and systems, the exact route must be determined according to the relevant approval framework.

This distinction is essential when discussing the UK as an alternative to Germany or Luxembourg.

14.17 What should a manufacturer actually compare?

Instead of simply asking:

“Which country is cheapest?”

a manufacturer should compare the following:

Regulatory suitability

Is the authority able to grant the required UN R10 approval?

Technical Service designation

Is the selected Technical Service specifically designated for the required R10 scope?

Test capability

Can it perform or supervise all required tests?

Test capacity

Can it meet the project schedule?

Experience

Does it have experience with the relevant type of Automotive electronics?

Documentation

Is the manufacturer comfortable with the required documentation process?

Authority interaction

How efficiently can technical questions and approval issues be resolved?

Cost

What is the complete project cost?

Future extensions

Can the same route support future variants and modifications?

Customer acceptance

Does the vehicle manufacturer accept the selected route?

14.18 A practical decision matrix

A manufacturer can therefore approach the decision like this:

Question	Germany	Luxembourg	UK
Is UNECE R10 applicable?	Verify	Verify	Verify
Is the authority designated?	Verify	Verify	Verify
Is the Technical Service designated for the required R10 scope?	Verify	Verify	Verify
Is the required test facility available?	Verify	Verify	Verify
What is the earliest realistic test date?	Compare	Compare	Compare
What is the total project cost?	Compare	Compare	Compare
Are future extensions expected?	Evaluate	Evaluate	Evaluate
Does the customer accept the route?	Verify	Verify	Verify
Does the route fit the target market?	Verify	Verify	Verify

The important point is that the table should be completed with project-specific information.

A generic ranking would be misleading.

14.19 So, which one is “best”?

There is no universal winner.

Germany may make sense when:

• the manufacturer is already deeply integrated into the German automotive ecosystem;
• the relevant German Technical Service is readily available;
• the customer prefers a German approval route;
• local communication and coordination are important.

Luxembourg may make sense when:

• the relevant authority and Technical Service are suitable;
• the project benefits from the available capacity;
• the administrative route is attractive;
• lead time or project coordination is better for the specific project.

The UK may make sense when:

• a suitable VCA or designated Technical Service is available;
• an international UNECE approval is desired;
• the project benefits from the UK’s technical-service infrastructure;
• the manufacturer has an established relationship with VCA or a UK-designated service.

These are project considerations, not fixed regulatory advantages.

14.20 The most important lesson

The choice between Germany, Luxembourg and the UK should not be made solely by looking at the E-number.

The better approach is:

Product → R10 scope → Applicable requirements → Suitable Technical Services → Availability → Cost → Customer requirements → Approval route

This approach makes the decision much more transparent.

For manufacturers, the key question is therefore not:

“Where can I get an ECE R10 approval most easily?”

It is:

“Which competent approval route gives me the most efficient and reliable path for this specific product?”

That may be Germany.

It may be Luxembourg.

It may be the United Kingdom.

And it may change from one project to another.

14.21 Key Takeaway

Germany, Luxembourg and the United Kingdom are all relevant participants in the UNECE type-approval framework.

Their E-numbers are:

E1 = Germany

E13 = Luxembourg

E11 = United Kingdom

The technical basis remains UN Regulation No. 10. The practical differences are primarily related to the competent authority, designated Technical Services, project capacity, lead times, costs, administrative processes and customer requirements.

For that reason, manufacturers should not select an approval route based solely on assumptions such as:

“Germany is expensive.”

“Luxembourg is easier.”

“The UK is cheaper.”

Those statements may be true for an individual project, but they are not reliable regulatory rules.

The correct approach is to compare the complete approval route for the specific product and project.

And above all, the manufacturer should verify that the selected Technical Service is actually designated for the required R10 regulation, amendment series and testing scope before committing to the project.

For an R10 project, the right approval route is the one that combines regulatory validity with technical capability, availability, predictable timing and manageable total cost.

15. ECE R10 and the United Kingdom After Brexit

Brexit changed the regulatory framework for vehicle type approval in the United Kingdom. At the same time, the United Kingdom remains part of the UNECE type-approval system and can continue to issue approvals under UN Regulations.

For manufacturers, it is therefore important to distinguish between:

UNECE type approval ≠ GB type approval

These two frameworks now exist alongside each other and can have different implications depending on the product, vehicle category and intended market.

15.1 The United Kingdom remains part of the UNECE framework

Brexit did not end the United Kingdom’s participation in the UNECE 1958 Agreement.

The United Kingdom remains a Contracting Party and continues to use the approval identifier:

E11

This means that the UK can continue to issue approvals under applicable UN Regulations, including UN Regulation No. 10.

An approval issued by the UK under UN R10 can therefore carry the designation:

E11

This remains a UNECE type approval.

The important point is that Brexit did not remove the United Kingdom from the international UNECE type-approval system.

15.2 What actually changed after Brexit?

The major change concerns the relationship between the UK and the EU type-approval framework.

Before Brexit, the United Kingdom participated in the EU vehicle type-approval system.

Following Brexit, the UK established its own national type-approval framework for Great Britain.

Manufacturers therefore need to distinguish between:

UNECE type approval

and

GB type approval

These are not simply two names for the same approval.

A technical requirement may be based on the same international UNECE regulation, but the regulatory framework under which the approval is issued can be different.

15.3 E11 does not automatically mean GB type approval

This is one of the most important points for manufacturers.

An:

E11 approval

is an approval issued by the UK within the UNECE system under the relevant UN Regulation.

A:

GB type approval

is an approval within the UK’s national type-approval framework.

The two should therefore not automatically be treated as interchangeable.

This distinction is particularly important when an existing E11 approval is being used for a product or vehicle intended for the GB market.

The UK Vehicle Certification Agency (VCA) provides specific guidance on the relationship between UNECE approvals and the GB type-approval framework.

15.4 Why is this distinction relevant to ECE R10?

Consider a manufacturer developing an electronic automotive component.

The manufacturer may decide to obtain:

E11 – UN Regulation No. 10

That provides a UNECE approval under R10.

The next question is:

What is the intended regulatory use of that approval?

If the objective is to obtain a UNECE approval for an automotive component, E11 may be a suitable approval route.

If the component is intended to be used within a GB vehicle type-approval project, however, the manufacturer must additionally determine how the relevant UNECE approval is treated under the applicable GB framework.

The important point is:

Obtaining an E11 R10 approval does not, by itself, answer every question concerning GB market access.

The approval must always be considered in the context of the intended vehicle, product and market.

15.5 The VCA plays an important role

The Vehicle Certification Agency (VCA) is the UK’s vehicle type-approval authority and plays an important role in both the UK and international type-approval environment.

Depending on the project, VCA can be involved in:

• UNECE type approvals;
• GB type approvals;
• technical assessments;
• conformity of production;
• extensions and modifications;
• other vehicle type-approval activities.

Therefore, simply stating:

“We will obtain approval through VCA.”

is not sufficient to define the regulatory route.

The manufacturer should establish whether the intended procedure is:

UNECE E11 approval

or

GB type approval

and what the approval will be used for.

15.6 UNECE E11 and GB type approval

The distinction can be summarized as follows:

Aspect	UNECE E11	GB Type Approval
Regulatory framework	UNECE	United Kingdom
Approval identifier	E11	GB-specific approval identifier
Basis	Applicable UN Regulations	UK GB type-approval framework
UK authority	VCA / designated UK approval authority	UK approval authority
Part of UNECE system	Yes	No, not as a UNECE approval
EU type approval	No	No
International UNECE relevance	Yes	Not by itself
GB market relevance	Depends on applicable requirements	Directly relevant to GB type approval

The exact treatment can depend on the vehicle category, product type and applicable legislation.

For an actual project, the current UK requirements must therefore be checked rather than relying on a general assumption.

15.7 UNECE regulations remain important in the GB framework

The UK’s post-Brexit type-approval strategy continues to make extensive use of international UNECE regulations.

This is important because it allows the UK to maintain a high degree of technical alignment with international vehicle regulations while retaining its own national regulatory framework.

For manufacturers, this can reduce the need to develop completely different technical solutions for the UK market.

However, technical alignment does not mean that every UNECE approval automatically satisfies every GB requirement.

The manufacturer still needs to establish:

• which approval is required;
• which regulation applies;
• which version is applicable;
• how the approval is recognized;
• and which additional GB requirements may apply.

15.8 What about existing E11 approvals?

Existing approvals require particular attention.

A manufacturer should not assume that an older E11 approval automatically remains sufficient for every UK application simply because it was originally issued by a UK approval authority.

The regulatory framework changed after Brexit, and specific transition arrangements applied to existing approvals.

The VCA has published guidance concerning the treatment of existing UK-issued approvals and their relationship with the GB type-approval system.

For an existing product, manufacturers should therefore check:

• when the approval was issued;
• under which framework it was issued;
• which vehicle or component category it covers;
• whether it was transferred or recognized under the applicable GB framework;
• whether the approval has subsequently been extended;
• which current UK requirements apply.

This is particularly important for products with long lifecycles.

15.9 Great Britain and Northern Ireland are not identical

Another important distinction is between:

Great Britain

and

Northern Ireland.

Great Britain comprises:

• England;
• Scotland;
• Wales.

Northern Ireland is subject to a different regulatory framework in certain areas because of the arrangements established following Brexit.

Therefore, manufacturers should avoid treating:

“UK approval”

as a sufficiently precise regulatory description.

For a product intended for the entire UK market, the manufacturer should determine separately:

What is required for GB?

and

What is required for Northern Ireland?

The answer can depend on the product, vehicle category, approval route and applicable legislation.

15.10 Example: an automotive electronic control unit

Consider a manufacturer developing an electronic control unit for installation in vehicles.

The manufacturer determines that UN R10 applies and prepares an approval project.

One possible route is:

UNECE R10 → UK approval authority → E11 approval

The manufacturer now has a UNECE R10 approval.

If the component is subsequently supplied to a vehicle manufacturer for use in a GB type-approval project, the manufacturer must determine how that existing E11 approval fits into the applicable GB regulatory framework.

The important point is that the following statements are not automatically equivalent:

“The component has an E11 R10 approval.”

and:

“The component is approved for every GB application.”

The second statement requires an additional regulatory assessment.

15.11 What does this mean for automotive suppliers?

For suppliers, the distinction becomes particularly important when the same product is supplied to several vehicle manufacturers or vehicle platforms.

A supplier may have:

• one hardware platform;
• several software versions;
• different vehicle applications;
• different installation configurations;
• several target markets.

The supplier should therefore define the approval strategy before testing begins.

For example:

Product → R10 scope → UNECE approval → Target markets → GB applicability → Vehicle OEM requirements

This creates a clearer relationship between the technical approval and its intended commercial use.

15.12 Can an E11 approval still be useful outside the UK?

Yes.

An E11 approval is a UNECE approval, not merely a UK national approval.

Its relevance therefore comes from the international UNECE framework rather than from the fact that it was issued by the United Kingdom.

This is an important distinction.

The fact that the approval authority is located in the UK does not turn the resulting UNECE approval into a purely British approval.

For manufacturers operating internationally, an E11 approval can therefore remain a potentially useful approval route where the relevant UNECE requirements and recognition arrangements apply.

15.13 Is E11 technically different from E1 or E13?

No.

The E-number identifies the Contracting Party that issued the approval.

For example:

• E1 → Germany
• E13 → Luxembourg
• E11 → United Kingdom

The E-number does not indicate a different version of UN Regulation No. 10.

There is no:

German R10

Luxembourg R10

or

British R10

from a technical-regulation perspective.

The underlying UN Regulation is the same framework.

The practical differences between approval routes can instead result from:

• approval authority;
• technical service;
• availability;
• project capacity;
• administrative processes;
• costs;
• lead times;
• customer requirements.

15.14 Why the UK can still be an interesting approval route

The UK’s continued participation in UNECE means that an E11 route can still be relevant for manufacturers.

Possible reasons include:

• availability of an appropriate technical service;
• experience with the relevant automotive product;
• existing relationships with VCA;
• project capacity;
• international UNECE approval strategy;
• existing UK automotive customers;
• suitable lead times.

The decision should nevertheless be based on the complete project rather than on the E-number alone.

The manufacturer should compare:

Technical suitability + approval route + technical service + availability + cost + lead time + target-market requirements

15.15 What should manufacturers check before choosing E11?

Before starting an E11 R10 project, manufacturers should answer at least the following questions.

1. What type of approval is actually required?

Is the project for:

UNECE E11

or:

GB type approval?

2. What is the target market?

Is the product intended for:

• EU;
• GB;
• Northern Ireland;
• or multiple markets?

3. What is the approval object?

Is it:

• a complete vehicle;
• an ESA;
• a component;
• a system;
• or another vehicle-related product?

4. Which UN Regulation applies?

For this article:

UN Regulation No. 10

5. Which version of R10 applies?

The applicable amendment series and transitional provisions must be established.

6. Which approval authority is responsible?

The relevant UK authority must be competent for the intended approval route.

7. Which technical service is appropriate?

The technical service should have the appropriate designation, competence and capability for the required R10 scope.

8. How will the approval be used?

The manufacturer should determine how the approval fits into the intended vehicle type-approval and market-access strategy.

15.16 Brexit did not make E11 obsolete

One of the clearest conclusions is therefore:

Brexit did not eliminate E11.

The United Kingdom remains part of the UNECE type-approval system and continues to participate in the international framework established under the 1958 Agreement.

E11 therefore remains a valid and relevant UNECE approval route.

What changed is the relationship between:

UNECE approval

and

UK national type approval.

For manufacturers, this means:

E11 remains internationally relevant as a UNECE approval.

But:

E11 should not automatically be interpreted as a GB type approval.

15.17 The practical decision for manufacturers

The relevant question is therefore not simply:

“Is E11 still valid after Brexit?”

The more useful questions are:

“What approval do we actually need?”

“Which market are we targeting?”

“Which approval route is required for that market?”

“Can an E11 UNECE approval be used for our intended application?”

“Do we additionally need a GB approval or other national requirements?”

Answering these questions before testing begins can prevent a situation where a technically successful R10 project does not provide the regulatory result the manufacturer actually needs.

15.18 Conclusion

Brexit changed the UK’s vehicle type-approval framework, but it did not remove the United Kingdom from the UNECE system.

The UK remains a Contracting Party and continues to use:

E11

for UNECE type approvals.

A UK-issued E11 approval under UN Regulation No. 10 therefore remains a UNECE R10 type approval.

At the same time, the UK has its own GB type-approval framework. An E11 approval should therefore not automatically be treated as equivalent to a GB type approval.

For manufacturers, particularly automotive component suppliers, the key is to distinguish clearly between:

UNECE approval

GB type approval

Northern Ireland requirements

and the requirements of the specific vehicle type-approval project.

The right approval route should be selected based on the product, vehicle application, target market, applicable regulation, approval authority, technical service and overall project strategy.

16. What Happens When the Product Changes?

An ECE R10 approval is based on a defined product configuration and a defined scope of approval. Automotive products, however, rarely remain completely unchanged throughout their lifetime.

Hardware is updated, software evolves, components become unavailable, connectors are modified, cable configurations change, and the same product may be introduced into additional vehicle platforms.

A change does not automatically invalidate an existing ECE R10 approval.

However, every relevant change should be assessed before it is introduced into an approved configuration.

The key question is not simply:

“Did the product change?”

but:

“Could this change affect the conditions under which compliance with ECE R10 was demonstrated?”

16.1 Why changes matter for ECE R10

EMC performance can be influenced by many aspects of a product.

A change that appears insignificant from a product-development perspective can nevertheless affect electromagnetic behavior.

Examples include:

• replacing an electronic component;
• changing a PCB layout;
• modifying a power supply;
• changing a connector;
• changing cable length;
• changing shielding;
• modifying the enclosure;
• changing software;
• adding a communication interface;
• changing an operating mode;
• changing the installation location.

The fact that the product still performs its primary function does not mean that its EMC characteristics remain unchanged.

For this reason, configuration management is an important part of maintaining an R10 approval.

16.2 Hardware changes

Hardware changes are among the most obvious changes that should trigger a compliance assessment.

Examples include:

• replacing an integrated circuit;
• changing a voltage regulator;
• replacing a switching device;
• changing a clock source;
• modifying filters;
• changing capacitors or inductors;
• modifying PCB traces;
• changing the power supply;
• adding or removing electronic components.

The impact depends on what has changed and how closely the new design corresponds to the approved configuration.

A direct replacement with an electrically and EMC-equivalent component may have a very different compliance impact from a redesign of the power stage or communication circuitry.

The important point is that the manufacturer should evaluate the change rather than making an automatic assumption.

16.3 PCB layout changes

PCB modifications deserve particular attention.

The PCB layout can directly influence:

• signal integrity;
• return currents;
• electromagnetic coupling;
• radiated emissions;
• conducted disturbances;
• susceptibility to external disturbances;
• high-frequency current paths.

A component may remain exactly the same while a PCB redesign changes its electromagnetic behavior.

Examples include:

• moving a switching regulator;
• changing the ground plane;
• modifying high-speed signal routing;
• changing the position of filtering components;
• changing the return-current path;
• modifying shielding structures;
• changing connector placement.

A PCB revision should therefore not automatically be considered irrelevant simply because the electrical schematic remains largely unchanged.

16.4 Component substitutions

Automotive manufacturers frequently face component obsolescence or supply-chain issues.

An approved product may use a particular:

• semiconductor;
• capacitor;
• resistor;
• crystal;
• connector;
• filter;
• transceiver;
• power device.

If that component becomes unavailable, a replacement may be introduced.

The replacement may appear functionally equivalent, but functional equivalence does not automatically mean EMC equivalence.

The manufacturer should consider factors such as:

• switching characteristics;
• clock frequencies;
• rise and fall times;
• power consumption;
• internal architecture;
• impedance characteristics;
• filtering;
• thermal behavior;
• electromagnetic emissions.

Depending on the change, additional technical evidence or testing may be appropriate.

16.5 Software changes

Software changes are often overlooked in EMC change assessments.

A software update does not necessarily change the physical EMC characteristics of the hardware.

However, software can influence:

• switching frequencies;
• operating modes;
• processor activity;
• communication traffic;
• actuator activity;
• power consumption;
• duty cycles;
• system states;
• diagnostic modes.

A software change can therefore alter the electromagnetic environment generated by the equipment.

For example, a new software function could activate a communication interface more frequently or change the operating pattern of a power converter.

The manufacturer should therefore consider whether the software change modifies any of the operating conditions relevant to the R10 approval.

16.6 New communication interfaces

Adding a communication interface can have a significant impact on EMC.

Examples include:

• CAN;
• CAN FD;
• LIN;
• Ethernet;
• USB;
• wireless interfaces;
• additional sensor interfaces;
• additional vehicle-network connections.

The new interface may introduce:

• additional cables;
• new connectors;
• new signal frequencies;
• additional switching activity;
• new current paths;
• additional coupling paths.

If a new interface is added to an approved product, the manufacturer should therefore assess whether the existing R10 evidence remains representative of the new configuration.

16.7 Cable and harness changes

Cable configuration is particularly important in automotive EMC.

Changes can include:

• cable length;
• cable type;
• number of conductors;
• shielding;
• connector type;
• termination;
• routing;
• grounding;
• harness arrangement.

The cable can form part of the path through which electromagnetic disturbances are generated or coupled.

A change from a short shielded cable to a longer unshielded harness, for example, can potentially have a significant effect on EMC behavior.

Even when the electronic unit itself remains unchanged, the installation configuration can therefore influence the compliance assessment.

16.8 Connector changes

Connectors are sometimes treated as purely mechanical components.

From an EMC perspective, however, they can be important.

A connector change can modify:

• shielding;
• grounding;
• pin arrangement;
• signal routing;
• separation between noisy and sensitive signals;
• cable termination;
• return-current paths.

A different connector may therefore change the EMC characteristics of the complete installation.

This is particularly relevant when the connector change also modifies the associated wiring harness.

16.9 Shielding and enclosure changes

Changes to the enclosure can also affect electromagnetic performance.

Examples include:

• changing the enclosure material;
• modifying the enclosure geometry;
• changing ventilation openings;
• changing shielding;
• modifying grounding points;
• changing conductive coatings;
• changing cable entry points.

A metal enclosure and a plastic enclosure, for example, can have substantially different electromagnetic characteristics.

Similarly, changing the location or size of an opening can influence radiated emissions or immunity.

The compliance impact should therefore be assessed before introducing such a change into an approved configuration.

16.10 Changes to the power supply

Power-supply changes are especially relevant for EMC.

Examples include:

• changing the input voltage range;
• replacing a DC/DC converter;
• changing a switching regulator;
• modifying input filtering;
• changing the power architecture;
• adding a new power mode;
• changing current consumption.

Power electronics can be significant sources of electromagnetic disturbances.

A change in the power architecture may therefore affect both emissions and immunity.

For an approved ESA, the manufacturer should determine whether the new power configuration remains within the conditions represented by the existing R10 evidence.

16.11 Changes to operating modes

The product may also change without any physical modification.

For example, new software may introduce a new operating mode.

A product that previously operated in:

Normal mode

may now also operate in:

High-performance mode

Diagnostic mode

Charging mode

or

Communication-intensive mode

Different operating states can generate different electromagnetic conditions.

The manufacturer should therefore identify which operating modes are relevant to the R10 approval and whether a new mode changes the worst-case EMC condition.

16.12 Changes to the vehicle installation

A particularly important point is that the product itself may remain unchanged while its installation changes.

Examples include:

• different mounting location;
• different distance from antennas;
• different cable routing;
• different grounding point;
• different vehicle power supply;
• different harness configuration;
• different adjacent electronic systems.

The same ESA can therefore experience a different electromagnetic environment in another vehicle platform.

This is particularly relevant for suppliers whose product is installed in multiple vehicle models.

The manufacturer should determine whether the new installation remains covered by the existing approval or whether additional assessment is required.

16.13 New vehicle applications

A common situation in the automotive industry is the reuse of an existing electronic product on a new vehicle platform.

For example:

Product A

may already have an established R10 approval and then be introduced into:

Vehicle Platform B

The hardware may remain unchanged.

However, the vehicle installation may be different.

The manufacturer should therefore assess:

• installation location;
• wiring;
• power supply;
• grounding;
• connected loads;
• communication interfaces;
• operating conditions;
• surrounding electronic systems.

The existing approval should not simply be assumed to cover every possible vehicle installation.

The exact regulatory and approval implications depend on the applicable R10 provisions and the scope under which the original approval was granted.

16.14 Minor changes vs. major changes

Not every change has the same compliance significance.

A useful internal classification can distinguish between:

Low-impact changes

Examples might include:

• purely cosmetic changes;
• changes with no electrical impact;
• administrative corrections;
• changes demonstrably unrelated to EMC.

These may require only documentation and an internal assessment.

Potentially relevant changes

Examples include:

• component substitutions;
• PCB changes;
• software changes affecting operating modes;
• connector changes;
• cable changes;
• power-supply changes.

These generally deserve a documented technical assessment.

Significant changes

Examples can include:

• major hardware redesign;
• new communication architecture;
• substantial power-stage modification;
• new operating modes;
• major changes to installation;
• changes affecting the fundamental configuration assessed during approval.

Such changes may require additional testing and potentially an update or extension of the approval.

The exact classification should always be based on the applicable regulatory requirements and the technical impact of the specific change.

16.15 Change assessment should happen before implementation

One of the most important practical rules is:

Do not wait until after the product change has entered production to determine its compliance impact.

The change should be assessed during the engineering change process.

A typical workflow can be:

Engineering Change → Compliance Impact Assessment → Technical Review → Decision on Evidence/Testing → Approval Update if Required → Release

This approach prevents the situation where production has already switched to a new configuration and the manufacturer discovers afterwards that additional approval work is required.

16.16 What should a change assessment contain?

A structured R10 change assessment can include:

Product identification

• Product name
• Part number
• Hardware revision
• Software version
• Existing approval number

Description of the change

• What changed?
• Why did it change?
• Which components or functions are affected?

EMC impact

• Could emissions change?
• Could immunity change?
• Could operating modes change?
• Could cable or grounding conditions change?
• Could the installation change?

Existing evidence

• Previous R10 test reports
• Internal EMC test data
• Design analysis
• Component information
• Previous approval documentation

Required action

Possible outcomes could include:

• No additional action;
• Documentation update;
• Technical justification;
• Additional testing;
• Approval extension;
• New approval.

The final decision should be based on the applicable regulatory framework and, where required, agreement with the relevant approval authority or technical service.

16.17 Regression testing

Where a change could influence EMC, targeted regression testing can be useful.

The objective is not necessarily to repeat the entire R10 test program.

Instead, the manufacturer can identify the parts of the compliance evidence most likely to be affected by the change.

For example, a change to:

Power electronics

may justify particular attention to conducted and radiated emissions.

A change to:

Communication hardware

may require assessment of the relevant emission and immunity behavior.

A change to:

Cable shielding

may affect both emissions and immunity.

The appropriate testing should therefore be determined from the technical change and the applicable regulatory requirements.

16.18 Approval extensions and updates

Where a product change falls within the scope of the existing approval framework but is not fully covered by the current approval documentation, an extension or update of the approval may be required.

The exact procedure depends on the applicable type-approval framework and the nature of the change.

The important distinction is:

A technical change does not necessarily mean a completely new approval is required.

An existing approval may potentially be extended or otherwise updated.

However, the manufacturer should not make this determination solely on the basis of internal engineering judgment where formal approval authority involvement is required.

The appropriate technical service and approval authority should be involved according to the applicable procedure.

16.19 Configuration management is therefore essential

A manufacturer should be able to identify exactly which product configuration was covered by the approval.

This can include:

• hardware revision;
• software version;
• PCB revision;
• BOM;
• cable configuration;
• connectors;
• enclosure;
• operating modes;
• installation conditions;
• approved variants.

Without effective configuration management, it becomes difficult to determine whether a production unit is actually covered by the existing approval.

This can create significant problems when:

• customers request compliance evidence;
• an audit takes place;
• a product change is introduced;
• an approval is extended;
• multiple manufacturing sites are involved.

16.20 The BOM can be relevant to EMC compliance

A Bill of Materials is often considered a manufacturing document rather than a compliance document.

For EMC-related approvals, however, certain components can be particularly relevant.

Examples include:

• filters;
• switching regulators;
• oscillators;
• processors;
• transceivers;
• power semiconductors;
• shielding components.

If a critical component is changed, the manufacturer should be able to identify the change and assess its potential impact.

This does not mean that every BOM change automatically requires a new R10 test.

It means that the manufacturer should have sufficient configuration information to determine whether the change could affect the approved EMC characteristics.

16.21 Change management across the product lifecycle

ECE R10 compliance should not be treated as a one-time event that ends when the certificate is issued.

A typical automotive product may remain in production for many years.

During that period, the product can undergo:

• supplier changes;
• component obsolescence;
• software updates;
• cost reductions;
• manufacturing changes;
• new vehicle applications;
• product variants;
• design improvements.

Each change creates the potential for a compliance impact.

A structured change-management process therefore helps maintain the connection between:

Approved configuration → Production configuration → Compliance evidence

16.22 What manufacturers should avoid

Several approaches create unnecessary risk.

“It is only a software update.”

Software can change operating conditions and therefore potentially influence EMC behavior.

“The replacement component is functionally equivalent.”

Functional equivalence does not automatically establish EMC equivalence.

“The cable is different, but the electronics are unchanged.”

The wiring configuration can significantly affect automotive EMC.

“The product already passed R10.”

The relevant question is whether the current configuration remains covered by the approval.

“We will check it when the customer asks.”

By then, production or vehicle integration may already be underway.

The better approach is to perform the compliance assessment as part of the engineering change process.

16.23 A practical change-management workflow

A structured process can look like this:

1. Change identified

↓

2. Product configuration recorded

↓

3. R10 impact assessment

↓

4. Existing approval and test evidence reviewed

↓

5. EMC impact determined

↓

6. Additional testing identified if required

↓

7. Technical Service / Approval Authority consulted where necessary

↓

8. Approval documentation updated

↓

9. Production configuration released

This creates traceability between the engineering change and the regulatory status of the product.

16.24 Why this matters for suppliers

Automotive suppliers frequently deliver the same product to multiple customers.

A single hardware change can therefore affect:

• several vehicle platforms;
• several customers;
• multiple approval documents;
• different installation configurations.

Without a structured change process, the supplier may not know which approvals are affected.

This becomes particularly challenging when the product has:

• many variants;
• multiple vehicle applications;
• long production lifecycles;
• several approval authorities;
• different technical services.

For such products, change management is not merely an engineering task.

It is part of the overall compliance management process.

16.25 How ScopeRight can support change assessment

ScopeRight can support manufacturers in structuring the compliance impact assessment when a product changes.

This can include helping organize:

• the original compliance scope;
• the approved product configuration;
• the applicable R10 requirements;
• the affected product variants;
• existing test evidence;
• the nature of the engineering change;
• potential additional testing;
• required documentation updates.

ScopeRight does not replace the formal decision of the relevant approval authority or technical service where their involvement is required.

Instead, it can help manufacturers structure the information needed to make the change assessment more efficient and traceable.

The objective is to avoid treating every engineering change as either:

“No impact”

or:

“Repeat everything.”

A structured assessment allows the manufacturer to determine what has actually changed and what evidence is genuinely required.

16.26 Key takeaway

An ECE R10 approval is tied to a defined configuration and scope.

Changes to:

• hardware;
• software;
• components;
• PCB;
• cables;
• connectors;
• shielding;
• power supply;
• operating modes;
• installation;
• vehicle application

can potentially affect the compliance basis.

This does not mean that every change requires a complete new R10 test program.

It means that relevant changes should be assessed systematically.

The most effective approach is to integrate R10 change assessment into the normal engineering change process:

Change → Impact Assessment → Evidence Review → Additional Testing if Required → Approval Update if Required → Release

For manufacturers, this creates a clear link between the product that was approved and the product that is actually being manufactured.

That link is essential for maintaining compliance throughout the product lifecycle.

17. Conformity of Production and Maintaining the Approval

Obtaining an ECE R10 type approval is not the end of the compliance process.

Once an approval has been granted, the manufacturer must ensure that the products placed into production continue to conform to the approved type.

This is the purpose of Conformity of Production (CoP).

The principle is straightforward:

The product tested and approved must correspond to the product that is actually manufactured.

Under the UNECE type-approval framework, conformity of production is not an optional quality activity. It forms part of the type-approval system itself. UNECE describes CoP as the means of demonstrating that series production continues to conform to the approved type. (UNECE)

For ECE R10, this is particularly important because EMC performance can be affected by changes to components, PCB layouts, wiring, shielding, software and other aspects of the product configuration.

17.1 What is Conformity of Production?

Conformity of Production means that products manufactured after approval must continue to comply with the configuration and requirements on which the approval was based.

The approval is therefore not simply a statement about one individual sample that was tested in a laboratory.

It relates to a defined type and to the manufacturer’s ability to reproduce that approved type consistently in production.

UNECE’s general type-approval framework requires the approval authority to establish that appropriate production arrangements and documented controls exist to ensure continued conformity with the approved type. (UNECE)

This creates a direct connection between:

Type Approval → Production Controls → Manufactured Product

If that connection is lost, the manufacturer can no longer reliably demonstrate that the products being placed on the market correspond to the approved configuration.

17.2 Why CoP matters for ECE R10

EMC performance can depend on relatively small technical details.

For example, a production change involving:

• a filter;
• a switching regulator;
• a PCB component;
• a connector;
• a cable;
• shielding;
• grounding;
• a software version;

can potentially affect electromagnetic performance.

A product may therefore pass the original R10 testing and subsequently change during production.

If the change affects the approved configuration, the manufacturer needs to determine whether the existing approval remains applicable.

CoP provides the framework for maintaining conformity between the approved design and series production.

17.3 Approval is based on a defined product type

The concept of a type is fundamental to vehicle type approval.

The manufacturer does not normally test every individual production unit.

Instead, representative configurations are selected for approval testing.

UNECE’s general framework specifically provides for representative testing and the selection of variants or versions representing the relevant worst-case conditions. (UNECE)

This means that the manufacturer needs to understand:

• which variants belong to the approved type;
• which technical characteristics define those variants;
• which configuration was tested;
• which differences are permitted;
• which production changes could affect the approval.

Without this information, it becomes difficult to determine whether a new production version is still covered.

17.4 Production must remain consistent with the approved configuration

After approval, production should not gradually drift away from the configuration that was assessed.

This can happen unintentionally.

For example:

A component becomes unavailable.

↓

Purchasing selects a replacement.

↓

Engineering confirms that the replacement performs the same function.

↓

Production begins using the new component.

From a functional perspective, the product may appear unchanged.

From an EMC perspective, however, the replacement could have different:

• switching characteristics;
• impedance;
• frequency behavior;
• filtering;
• parasitic characteristics;
• electromagnetic emissions.

This is why production changes should be linked to the compliance and change-management process.

17.5 CoP is more than final-product inspection

Conformity of Production should not be understood simply as:

“Test a finished product occasionally.”

The broader concept includes the systems and controls used by the manufacturer to ensure continued conformity.

This can involve:

• documented manufacturing procedures;
• configuration control;
• component control;
• supplier control;
• production inspections;
• defined testing;
• traceability;
• quality records;
• handling of non-conformities;
• change management.

The exact CoP arrangements depend on the applicable regulatory requirements and the approval authority’s procedures.

The manufacturer must be able to demonstrate that its production system is capable of consistently reproducing the approved type.

17.6 Initial assessment of production arrangements

Before type approval is granted, the approval authority generally needs to establish that adequate production conformity arrangements exist.

UNECE’s CoP guidance describes an initial assessment of the manufacturer’s production facilities and the existence of satisfactory arrangements and procedures for effective production control. (UNECE)

This can include consideration of:

• production processes;
• quality management arrangements;
• documented control plans;
• inspection procedures;
• testing facilities;
• responsibilities;
• records;
• handling of production changes.

The exact assessment method depends on the applicable regulatory framework and the approval authority.

The important principle is:

The manufacturer must be able to demonstrate not only that the prototype complies, but that production can continue to produce compliant products.

17.7 Production controls

Once approval has been granted, production controls should ensure that relevant characteristics remain within the approved configuration.

For an electronic product, this may involve controlling:

• Bill of Materials;
• PCB revision;
• firmware/software version;
• component suppliers;
• critical components;
• cable configuration;
• connectors;
• shielding;
• enclosure;
• manufacturing process;
• calibration;
• final inspection.

Not every item necessarily has the same compliance relevance.

The manufacturer should identify which characteristics are important to the approved type and ensure that those characteristics are appropriately controlled.

17.8 Supplier changes can affect conformity

Modern automotive products often rely on complex supply chains.

A manufacturer may not manufacture every component itself.

A supplier can therefore introduce a change without the final product manufacturer immediately recognizing its potential compliance significance.

Examples include:

• semiconductor substitutions;
• passive-component changes;
• connector changes;
• cable changes;
• PCB material changes;
• filter changes;
• changes to shielding materials.

Supplier change notifications should therefore feed into the manufacturer’s own engineering and compliance change process.

A supplier statement such as:

“Form, fit and function unchanged”

does not automatically mean:

“ECE R10 compliance impact = none.”

The manufacturer must determine the actual compliance impact.

17.9 Configuration management is central to CoP

A strong configuration-management system makes it possible to answer a basic question:

Which exact configuration was approved, and does the production version still correspond to it?

For an electronic product, useful configuration identifiers can include:

• Part number
• Hardware revision
• PCB revision
• Software version
• BOM revision
• Connector configuration
• Cable configuration
• Enclosure version
• Variant designation

These identifiers should be traceable to the relevant approval documentation.

This becomes particularly important when a manufacturer has several variants that look almost identical but differ in technically relevant details.

17.10 Changes during production

Production changes should be assessed before implementation whenever they could potentially affect the approved type.

A useful process is:

Proposed Change

↓

Technical Assessment

↓

R10 Compliance Impact Assessment

↓

Existing Approval Reviewed

↓

Additional Evidence / Testing if Required

↓

Approval Update if Required

↓

Production Release

This prevents the production organization from implementing a change first and asking the compliance question afterwards.

17.11 What happens if production no longer conforms?

If products are found not to conform to the approved type, the manufacturer needs to take appropriate corrective action.

Depending on the nature and extent of the non-conformity, this can involve:

• stopping production;
• identifying affected products;
• correcting the manufacturing process;
• replacing components;
• conducting additional testing;
• informing the relevant approval authority;
• updating the approval where required;
• addressing products already produced.

The exact regulatory consequences depend on the nature of the non-conformity and the applicable approval framework.

For ECE R10, the regulation provides that approval may be withdrawn when the applicable requirements for conformity of production are not fulfilled. (UNECE)

This illustrates why CoP should not be treated as an administrative formality.

17.12 The approval authority can verify production controls

The approval authority that granted the approval can verify the manufacturer’s conformity-control methods.

UNECE’s general CoP guidance states that the approval authority may verify the conformity-control methods applied at production facilities, with the applicable frequency determined by the relevant framework and regulation. (UNECE)

The specific ECE R10 provisions also contain requirements concerning conformity of production and verification.

This means that manufacturers should be prepared to demonstrate:

• how the approved configuration is controlled;
• how production changes are managed;
• how conformity is verified;
• how records are maintained;
• how non-conformities are handled.

17.13 Records and documentation

Traceability is an important part of maintaining an approval.

Production and CoP records can provide evidence that the manufacturer has continued to produce the approved type.

Depending on the applicable requirements, records can include:

• production test results;
• inspection records;
• configuration records;
• component information;
• supplier documentation;
• change records;
• corrective-action records;
• approval documentation.

For ECE R10 specifically, the regulation requires records of conformity-of-production test results to be maintained, with the applicable retention period agreed with the Approval Authority or Technical Service and subject to the limit specified in the regulation.

The exact documentation requirements should therefore be established as part of the approval project.

17.14 What does CoP mean for an ESA manufacturer?

For an ESA manufacturer, CoP can be particularly important because the product may be supplied to several vehicle manufacturers or used across multiple vehicle platforms.

The manufacturer may have:

• multiple hardware variants;
• several software versions;
• different harnesses;
• different installation configurations;
• different customer requirements.

The approval documentation must therefore be linked to the relevant product configurations.

A change made for one customer should not accidentally be introduced into another approved configuration without first assessing the compliance consequences.

17.15 Software configuration matters

Modern automotive products are increasingly software-defined.

A production unit may therefore differ from the original approval sample not because of a hardware change but because of a different software version.

Software can influence:

• operating modes;
• switching behavior;
• communication activity;
• processor load;
• actuator control;
• power consumption;
• diagnostic functions.

The manufacturer should therefore determine whether software versions form part of the compliance-relevant configuration.

Where software changes can affect the conditions under which EMC compliance was demonstrated, they should be included in the change-management and approval assessment.

17.16 Production tooling and process changes

Not every production change is an obvious electronic change.

Manufacturing processes can also affect the final product.

Examples include:

• changes to soldering processes;
• changes to assembly methods;
• changes to shielding assembly;
• changes to bonding;
• changes to grounding;
• changes to cable termination;
• changes to enclosure assembly.

If such a process change alters a compliance-relevant characteristic, its potential impact should be evaluated.

This is another reason why CoP is broader than simply checking whether the BOM is unchanged.

17.17 Maintaining conformity across manufacturing sites

Large automotive suppliers may manufacture the same product at several facilities.

This creates another challenge.

The manufacturer must ensure that the product produced at:

Plant A

remains equivalent to the approved type when compared with the product produced at:

Plant B

Differences in:

• components;
• suppliers;
• assembly processes;
• testing;
• software loading;
• calibration;
• final inspection;

can potentially affect conformity.

Production-site controls therefore need to be aligned with the approved configuration and the manufacturer’s CoP system.

17.18 Production conformity and product lifecycle management

ECE R10 compliance should be viewed as a lifecycle activity.

The process does not end when the approval number is issued.

A typical lifecycle looks like:

Development

↓

Scoping

↓

Testing

↓

Type Approval

↓

Series Production

↓

Conformity of Production

↓

Engineering Changes

↓

Approval Maintenance

↓

End of Production

This lifecycle approach is particularly important for products with long automotive production periods.

A product may remain in production for many years after its original approval.

During that period, the manufacturer must continue to manage the relationship between the approved type and the actual production configuration.

17.19 What happens when production ends?

If the holder of an approval completely stops manufacturing the approved type, the approval authority must be informed according to the applicable procedure.

The authority then communicates the discontinuation to the relevant Contracting Parties. The ECE R10 provisions contain specific requirements for definitive discontinuation of production. (UNECE)

This is another indication that the approval is connected to the manufacturer’s ongoing production activity rather than being merely a historical laboratory certificate.

17.20 CoP and change management must work together

Conformity of Production and engineering change management are closely connected.

Consider a simple example:

Original approved product

→

Supplier announces component discontinuation

→

Engineering selects replacement

→

Compliance impact assessment

→

Additional R10 evidence/testing if required

→

Approval documentation updated if necessary

→

New configuration released to production

→

CoP controls updated

This creates a controlled transition between the old and new configurations.

Without this connection, there is a risk that production changes faster than the regulatory documentation.

17.21 Common CoP mistakes

Several mistakes can create unnecessary regulatory risk.

“The product passed R10, so production is covered.”

The approval covers a defined type. Production must continue to conform to that type.

“The supplier says the replacement is equivalent.”

The manufacturer still needs to assess the compliance impact.

“It is only a firmware update.”

Software can influence EMC-relevant operating conditions.

“The factory produces the same part number.”

The same part number does not necessarily prove that every compliance-relevant configuration detail is unchanged.

“CoP is the quality department’s responsibility.”

CoP requires cooperation between quality, engineering, production, purchasing and compliance.

“We only need to think about compliance when the approval is renewed.”

R10 approval maintenance is an ongoing lifecycle responsibility.

17.22 A practical CoP structure for an R10 product

A manufacturer can structure its internal process around several basic elements.

1. Approved configuration

Maintain a clear definition of the approved product.

2. Critical characteristics

Identify components and design features that can influence EMC performance.

3. Production controls

Define how those characteristics are controlled during manufacturing.

4. Change management

Ensure that production and supplier changes trigger an appropriate compliance assessment.

5. Verification

Perform the applicable production checks and tests.

6. Records

Maintain evidence that production continues to conform.

7. Corrective action

Define what happens when a product does not conform.

8. Approval maintenance

Update the approval documentation when changes require it.

This creates a practical connection between the type approval and day-to-day manufacturing.

17.23 How ScopeRight can support CoP-related activities

ScopeRight can support the compliance-management side of maintaining an ECE R10 approval.

For example, manufacturers can use a structured compliance process to keep track of:

• approved product configurations;
• applicable requirements;
• test evidence;
• product variants;
• regulatory documentation;
• engineering changes;
• compliance assessments;
• additional testing;
• approval updates.

ScopeRight does not replace the manufacturer’s production quality system, nor does it replace the formal responsibilities of the Approval Authority or Technical Service.

Instead, it can help maintain a structured connection between the approved compliance scope and the current product configuration.

This can be particularly useful when products have long lifecycles and multiple variants.

17.24 Key Takeaway

ECE R10 compliance does not end when the approval is issued.

The manufacturer must continue to ensure that production conforms to the approved type.

That requires a combination of:

Configuration Control + Production Controls + Change Management + Verification + Documentation

The most important principle is simple:

The product being manufactured today must remain consistent with the product that was approved.

When a component, PCB, software version, cable, shielding, manufacturing process or other compliance-relevant characteristic changes, the manufacturer should determine whether the existing approval remains applicable.

A well-structured Conformity of Production process helps make that connection visible and controllable throughout the product lifecycle.

For automotive manufacturers, CoP should therefore not be treated as a final administrative step after testing.

It is part of the ongoing responsibility of maintaining the ECE R10 approval.

18. ECE R10 and Modern Automotive Technologies

Automotive technology is changing rapidly. Vehicles are becoming more electrified, connected, automated and increasingly dependent on complex electronic architectures.

These developments do not make electromagnetic compatibility less important. On the contrary, they increase the number of potential electromagnetic sources, the number of sensitive electronic systems and the complexity of the interactions between them.

ECE R10 therefore remains highly relevant as automotive technology evolves.

18.1 Electric Vehicles

The transition from conventional powertrains to hybrid and fully electric vehicles has introduced significantly more power electronics into vehicles.

Modern electric vehicles can include:

• High-voltage battery systems
• Battery management systems
• Traction inverters
• DC/DC converters
• On-board chargers
• Charging interfaces
• Electric motors
• High-voltage distribution systems
• Power conversion equipment

Many of these systems operate with high currents and high switching frequencies.

Fast switching is essential for efficient power conversion, but it can also generate electromagnetic disturbances.

These disturbances can potentially propagate through:

• High-voltage cables
• Low-voltage wiring
• Vehicle ground systems
• Communication networks
• The surrounding electromagnetic environment

At the same time, sensitive electronic systems must continue to function correctly in the presence of these disturbances.

This makes EMC a particularly important design consideration for electric vehicles.

18.2 Charging Systems

Vehicle charging introduces another important electromagnetic environment.

Depending on the charging architecture, a vehicle can interact with:

• AC charging infrastructure
• DC fast-charging infrastructure
• On-board chargers
• High-voltage battery systems
• Charging communication systems
• Power conversion equipment

Charging can involve significant electrical power and switching activity.

The vehicle therefore has to maintain electromagnetic compatibility while charging as well as during normal driving conditions.

The increasing use of high-power charging technologies also means that manufacturers need to consider EMC across a broader range of operating conditions.

For an R10 project, the relevant charging-related operating modes and configurations should therefore be considered when determining the applicable test scope.

18.3 ADAS and Increasing Sensor Density

Advanced Driver Assistance Systems (ADAS) have significantly increased the number of electronic sensors and control systems installed in vehicles.

Depending on the vehicle, these can include:

• Radar sensors
• Cameras
• Ultrasonic sensors
• GNSS receivers
• Lidar systems
• Inertial sensors
• Electronic control units
• Communication interfaces

Many of these systems operate simultaneously.

This creates a more complex electromagnetic environment in which systems must continue to function reliably without interfering with one another.

For example, an electronic system that generates excessive electromagnetic emissions could potentially interfere with another sensor or receiver.

Conversely, a sensor or control unit must remain sufficiently immune to electromagnetic disturbances generated elsewhere in the vehicle.

18.4 Radar Systems

Radar has become an increasingly important technology in modern vehicles.

Automotive radar systems are used for functions such as:

• Adaptive cruise control
• Blind-spot detection
• Collision warning
• Emergency braking
• Parking assistance
• Other driver-assistance functions

Radar systems intentionally generate and receive electromagnetic energy.

This makes the relationship between radio functionality and EMC particularly important.

The radar system itself must operate reliably while the vehicle’s other electronic systems must continue functioning in its electromagnetic environment.

The presence of radar therefore reinforces the need to consider the vehicle as an integrated electromagnetic system rather than as a collection of isolated components.

18.5 Connected Vehicles

Modern vehicles increasingly communicate with external networks.

Depending on the vehicle architecture, this can include:

• Cellular communication
• Wi-Fi
• Bluetooth
• GNSS
• Vehicle-to-Vehicle communication
• Vehicle-to-Infrastructure communication
• Remote access systems
• Keyless-entry systems
• Telematics

Each additional communication interface introduces additional electromagnetic activity.

The vehicle therefore has to accommodate intentional radio transmissions while maintaining compatibility with its own electronic systems.

This creates a close relationship between:

Radio functionality + EMC + vehicle integration

A radio module may comply with its applicable radio requirements, but the final vehicle integration still has to be considered as part of the overall compliance strategy.

18.6 Software-Defined Vehicles

Another major development is the increasing importance of software.

Modern vehicles can receive software updates throughout their operational lifetime. Functions that were previously determined primarily by hardware can increasingly be changed through software.

Software can influence:

• Communication activity
• Switching behaviour
• Operating modes
• Sensor activation
• Actuator control
• Data processing
• Diagnostic functions
• Charging behaviour

A software update may therefore alter the electromagnetic operating conditions of the vehicle or an electronic sub-assembly even if the physical hardware remains unchanged.

This is one reason why software configuration should be considered as part of the overall product configuration when assessing changes to an R10-approved system.

18.7 Automated Driving

Higher levels of vehicle automation increase the dependence on electronic systems.

Automated driving architectures can involve the simultaneous operation of:

• Multiple sensors
• Multiple control units
• Communication networks
• High-performance processors
• Actuators
• Redundant systems
• Positioning systems
• Perception systems

The reliability of these systems depends not only on their individual performance but also on their ability to operate correctly within the vehicle’s electromagnetic environment.

As vehicle automation increases, electromagnetic compatibility becomes increasingly connected to the reliable operation of the overall electronic architecture.

18.8 More Electronics Means More Potential Sources of Interference

A modern vehicle may contain hundreds of electronic functions distributed throughout the vehicle.

Every electronic circuit can potentially contribute to the electromagnetic environment.

Potential sources include:

• Switching regulators
• Inverters
• Motors
• Digital processors
• High-speed communication interfaces
• Wireless transmitters
• LED drivers
• Charging systems
• Power conversion systems

At the same time, the vehicle contains many systems that can potentially be affected by electromagnetic disturbances.

This creates an increasingly complex relationship:

More electronic systems → more potential sources → more potential coupling paths → more potential victims

EMC engineering therefore becomes increasingly important as vehicle architectures become more complex.

18.9 High-Speed Communication

Modern vehicles increasingly rely on high-speed internal communication.

Examples include automotive communication networks used to exchange information between:

• Sensors
• ECUs
• Displays
• Powertrain systems
• ADAS systems
• Gateway systems
• Infotainment systems

Higher data rates can introduce additional EMC challenges.

Signal integrity, cable routing, shielding, grounding and electromagnetic coupling become increasingly important.

A change to a communication interface may therefore have consequences beyond the communication function itself.

The compliance assessment should consider whether the change can affect the electromagnetic behaviour of the product.

18.10 Wireless Communication Inside the Vehicle

Wireless technologies are increasingly integrated directly into vehicle functions.

A single vehicle may contain several radio technologies operating in different frequency ranges.

These systems can include:

• Bluetooth
• Wi-Fi
• Cellular communication
• GNSS
• Keyless-entry systems
• Short-range radar
• Other wireless interfaces

The simultaneous operation of several radio systems creates a complex RF environment.

The vehicle architecture must ensure that intentional radio transmissions do not create unacceptable interference with other electronic functions.

At the same time, the radio systems themselves need sufficient immunity against electromagnetic disturbances generated by the vehicle.

18.11 The Importance of System Integration

Modern automotive EMC cannot always be understood by testing each electronic unit independently.

The final electromagnetic behaviour can depend on how the individual systems are integrated.

Relevant factors can include:

• Physical installation
• Cable routing
• Grounding
• Shielding
• Power distribution
• Communication networks
• Vehicle body structure
• Antenna locations
• Adjacent electronic systems

This means that an electronic unit can have good component-level EMC performance while the final vehicle architecture still requires careful system-level evaluation.

Component compliance and vehicle compliance therefore remain related but distinct concepts.

18.12 New Technologies Can Change the Regulatory Landscape

Automotive technology is developing faster than many traditional vehicle architectures were designed for.

Regulatory requirements therefore continue to evolve as new technologies become established.

The development of newer R10 amendment series reflects this ongoing evolution.

Topics relevant to the continued development of automotive EMC requirements include:

• Automated driving systems
• New vehicle architectures
• Charging systems
• Increasingly complex electronic systems
• New communication technologies
• Radiated emissions
• Updated test methods

For manufacturers, this means that an R10 compliance strategy should not rely indefinitely on assumptions made at the beginning of a long product development cycle.

The applicable regulatory version should be verified at the relevant stages of the project.

18.13 Product Lifecycle Management Becomes More Important

The increasing complexity of automotive electronics also makes lifecycle management more important.

A vehicle or ESA can remain in production for many years.

During that time, manufacturers may introduce:

• New components
• New software versions
• New suppliers
• New production locations
• New vehicle applications
• New communication functions
• New hardware revisions

Each change can potentially affect the existing compliance basis.

A manufacturer therefore needs a process that connects:

Product development → Compliance → Type approval → Production → Change management

Without such a connection, the regulatory documentation can gradually diverge from the actual product.

18.14 Why Early Compliance Planning Matters Even More

As automotive technology becomes more complex, the cost of discovering an EMC problem late in development can increase.

A late-stage problem may require:

• Hardware redesign
• PCB modifications
• Shielding changes
• Filter redesign
• Software changes
• Additional laboratory testing
• Changes to vehicle integration
• Additional approval activities

Early compliance planning can help identify potential problems before the product reaches formal approval testing.

This is particularly valuable for complex products involving multiple interfaces, operating modes and vehicle configurations.

18.15 What Modern Automotive Technology Means for R10 Scoping

Modern technologies make the initial R10 scope definition increasingly important.

A useful scope assessment should consider:

• Product architecture
• Vehicle application
• Hardware variants
• Software variants
• Communication interfaces
• Wireless technologies
• Power architecture
• Charging modes
• Operating modes
• Cable configurations
• Vehicle installation
• Relevant functions during immunity testing

The goal is not to test every imaginable configuration.

The goal is to determine which configurations and operating conditions are relevant to demonstrating compliance with the applicable R10 requirements.

18.16 The Role of Future Regulatory Development

ECE R10 is not a finished, static framework.

As automotive technology evolves, the regulatory framework is expected to evolve with it.

This is particularly relevant for manufacturers developing products with long development and production lifecycles.

A product designed today may still be produced many years from now.

Manufacturers should therefore monitor:

• New R10 amendment series
• New supplements
• Changes to referenced standards
• Transitional provisions
• New vehicle technologies
• Changes affecting charging and automated driving

Regulatory monitoring becomes particularly valuable when the product development cycle is long enough that the applicable requirements may change before final approval or during continued production.

18.17 Modern Automotive Technology Does Not Change the Basic R10 Principle

Despite all of these technological developments, the fundamental objective remains unchanged.

The vehicle and its relevant electronic systems must be able to operate together without creating unacceptable electromagnetic interference and while maintaining the required immunity to electromagnetic disturbances.

What has changed is the complexity of achieving that objective.

More electronics, more communication, more power electronics and more automated functions create more possible interaction paths.

This makes structured compliance planning increasingly important.

18.18 How ScopeRight Can Support Modern Automotive Compliance

ScopeRight can support manufacturers by helping structure the compliance information associated with increasingly complex products.

For example, relevant information can be organized around:

• Product variants
• Hardware configurations
• Software versions
• Applicable requirements
• Test plans
• Test evidence
• Regulatory changes
• Product changes
• Approval documentation

ScopeRight does not replace the technical service, approval authority or laboratory responsible for the formal R10 approval process.

Its role is to help manufacturers establish and maintain a structured view of the compliance scope and the evidence associated with their products.

This becomes particularly useful as the number of product variants and regulatory dependencies increases.

18.19 Conclusion

Modern automotive technology is making EMC more important, not less.

Electric vehicles introduce powerful switching systems and charging technologies.

ADAS introduces increasing numbers of sensors and electronic control functions.

Connected vehicles introduce more wireless communication.

Automated driving increases dependence on reliable electronic systems.

Software-defined vehicles introduce a new dimension to configuration management.

All of these developments increase the importance of understanding the electromagnetic environment as a complete system.

ECE R10 remains an important part of that regulatory environment.

For manufacturers, the challenge is therefore not simply to determine whether an individual electronic component can pass an EMC test.

The challenge is to understand how the product, its configuration, its installation and its intended vehicle application fit together within the applicable R10 requirements.

As automotive technology becomes more complex, a well-defined compliance scope and controlled product configuration become increasingly important throughout the entire product lifecycle.

19. Common ECE R10 Compliance Mistakes

ECE R10 projects can become unnecessarily complex when the regulatory scope, technical configuration or approval strategy is not clearly defined from the beginning.

Many problems do not originate in the laboratory itself. They arise earlier — for example, when the wrong regulatory framework is assumed, product variants are not properly identified, or testing begins before the actual approval scope has been established.

The following are some of the most common mistakes manufacturers should avoid.

19.1 Assuming CE EMC Compliance Is Sufficient

One of the most common misconceptions is:

“The product already has CE EMC compliance, so it is compliant with ECE R10.”

This is not automatically correct.

CE EMC compliance and ECE R10 belong to different regulatory frameworks.

A product may have been successfully assessed under the applicable EU EMC legislation while still requiring a separate assessment or approval under the UNECE vehicle type-approval framework.

Existing EMC test results may nevertheless be useful.

The important question is whether those results are applicable to the specific R10 requirements, configuration and approval strategy.

Manufacturers should therefore distinguish between:

Existing EMC evidence

and

Evidence that is acceptable for the specific ECE R10 approval.

19.2 Treating ECE R10 as a Single EMC Test

Another common mistake is to think of R10 as one standardized EMC test that can simply be booked at a laboratory.

In reality, the applicable test program depends on factors such as:

• Vehicle or ESA approval
• Applicable R10 version
• Product configuration
• Operating modes
• Interfaces
• Wiring
• Loads
• Installation conditions
• Relevant functions
• Applicable test methods

A laboratory cannot always provide a meaningful quotation based only on the statement:

“We need an ECE R10 test.”

The laboratory needs to know what is being approved and which requirements apply.

A proper test scope should therefore be established before requesting quotations.

19.3 Starting Laboratory Testing Before Defining the Scope

Starting testing too early can create unnecessary cost and project risk.

For example, a manufacturer may send a product to a laboratory before determining:

• Which variants need to be covered
• Which operating modes are relevant
• Which cables and loads must be connected
• Which software version should be tested
• Which R10 requirements apply
• Which approval route will be used

The laboratory may then test a configuration that does not fully represent the intended approval scope.

This can lead to additional testing later.

A better approach is:

Define → Scope → Plan → Quote → Test

rather than:

Book laboratory → Test → Determine what was actually required

19.4 Using the Wrong Test Configuration

The test configuration can have a significant influence on EMC results.

Potentially relevant variables include:

• Cable length
• Harness arrangement
• Power supply
• Loads
• Grounding
• Shielding
• Connectors
• Communication activity
• Software
• Operating mode
• Auxiliary equipment

A product may behave differently depending on how it is connected and operated.

Testing a configuration that is technically convenient but does not represent the intended application can therefore create problems later.

The configuration used during testing should be deliberately defined and documented.

19.5 Ignoring Installation Conditions

Automotive electronics do not operate in isolation.

The electromagnetic environment can depend on where and how the equipment is installed.

Relevant factors can include:

• Installation location
• Distance from other electronics
• Cable routing
• Vehicle grounding
• Power distribution
• Nearby antennas
• High-voltage systems
• Motors and inverters
• Other electronic control units

An ESA installed close to a high-power inverter may experience a very different electromagnetic environment from the same ESA installed elsewhere in the vehicle.

Installation conditions should therefore be considered when defining the compliance scope.

19.6 Assuming a Pre-Approved Radio Module Solves the EMC Problem

Many automotive products contain radio modules that already have their own regulatory approvals.

This can simplify certain aspects of radio compliance, but it does not automatically establish compliance of the complete host product.

The integration of the module can change its electromagnetic behaviour through:

• PCB layout
• Power supply
• Grounding
• Shielding
• Antenna placement
• Enclosure design
• Additional electronics
• Cable configuration

The module’s existing approval and the compliance of the final automotive product should therefore be treated as separate questions.

A pre-approved module can be useful evidence, but it does not automatically eliminate the need to evaluate the complete product.

19.7 Ignoring Product Variants

Automotive products frequently exist in multiple variants.

Differences may include:

• Hardware revisions
• PCB versions
• Software versions
• Connectors
• Power supply configurations
• Communication interfaces
• Cable lengths
• Antennas
• Enclosures
• Operating modes

A manufacturer may assume that all variants are covered by one test because the products share the same basic design.

That assumption needs to be justified.

The manufacturer should determine which differences can affect EMC performance and which variants are actually represented by the tested configuration.

Poor variant management can result in either unnecessary testing or insufficient coverage.

19.8 Underestimating Software Changes

Software can influence the electromagnetic behaviour of an electronic product.

A software update may change:

• Switching behaviour
• Communication activity
• Data transmission
• Operating modes
• Sensor activation
• Motor control
• Charging behaviour
• Diagnostic functions

A software change therefore should not automatically be treated as irrelevant to EMC.

Not every software update requires additional R10 testing, but the potential impact should be assessed.

This becomes particularly important for modern vehicles where software is continuously updated throughout the product lifecycle.

19.9 Treating Component Changes as Automatically Irrelevant

Component substitutions are common in automotive production.

A manufacturer may replace a component because of:

• Supplier changes
• Obsolescence
• Availability
• Cost
• Second-source strategies
• Manufacturing changes

The replacement component may perform the same basic electrical function.

That does not necessarily mean that its electromagnetic behaviour is identical.

Differences in switching characteristics, impedance, frequency response or internal architecture can influence EMC performance.

A component change should therefore be assessed before assuming that the existing R10 evidence remains completely unaffected.

19.10 Ignoring Cable and Harness Changes

Cable configuration can be particularly important in automotive EMC.

Changes to:

• Cable length
• Cable type
• Shielding
• Connector
• Pin assignment
• Routing
• Ground connection

can influence both emissions and immunity.

A manufacturer should therefore include relevant harness configurations in its change-management process.

The statement “The electronics are unchanged” does not necessarily mean that the electromagnetic configuration is unchanged.

19.11 Using an Outdated R10 Version

ECE R10 has evolved through multiple revisions, amendment series and supplements.

A manufacturer may have an old project specification or laboratory quotation that refers simply to:

“ECE R10.”

That may not be sufficient to determine the applicable requirements for a current project.

Before testing, the manufacturer should establish:

• Applicable R10 revision or amendment series
• Relevant supplements
• Corrigenda
• Transitional provisions
• Referenced standards
• Applicable editions of those standards

Using an outdated requirement set can result in additional work or an approval strategy that does not match the current regulatory situation.

19.12 Confusing a Test Report With Type Approval

A laboratory test report and an R10 type approval are not the same thing.

A test report provides technical evidence that a defined configuration was tested against defined requirements.

Type approval is the formal regulatory approval within the applicable vehicle type-approval framework.

Therefore, the statement:

“We have the R10 test report.”

does not necessarily mean:

“We have an ECE R10 type approval.”

The distinction becomes particularly important when communicating compliance status to customers, vehicle manufacturers or authorities.

19.13 Assuming a Successful Test Automatically Covers Future Changes

A successful R10 test demonstrates compliance of the configuration that was assessed.

It does not automatically mean that every future configuration will remain covered.

Changes to:

• Hardware
• Software
• Components
• Wiring
• Shielding
• Power supply
• Installation
• Vehicle application

may require a new assessment.

Manufacturers should therefore establish a change-management process that connects engineering changes with the regulatory approval status.

19.14 Failing to Control the Approved Configuration

A type approval is associated with a defined technical configuration.

If production gradually diverges from the configuration on which the approval was based, the regulatory documentation may no longer accurately describe the manufactured product.

This can happen through:

• Uncontrolled supplier substitutions
• Engineering changes
• New software versions
• Alternative components
• Production changes
• New manufacturing sites
• Uncontrolled product variants

Configuration management is therefore an important part of maintaining compliance after the original approval has been obtained.

19.15 Choosing the Laboratory Before Defining the Project

Another practical mistake is selecting a laboratory based primarily on availability or price before the technical scope has been established.

A laboratory quotation is only meaningful if the laboratory understands what needs to be tested.

The manufacturer should ideally provide information such as:

• Product description
• Approval object
• R10 version
• Product variants
• Operating modes
• Wiring configuration
• Required functions
• Existing test evidence
• Target approval
• Expected timing

This allows laboratories to quote against a defined project rather than against a vague request for “R10 testing.”

19.16 Failing to Review Existing Test Evidence

Manufacturers sometimes assume that all previous test results are either fully reusable or completely irrelevant.

Both approaches can be problematic.

Existing evidence should instead be reviewed systematically.

For each existing test, the manufacturer should consider:

• Which requirement was tested?
• Which standard was used?
• Which edition was applicable?
• Which configuration was tested?
• Which operating mode was used?
• Which limits were applied?
• Is the test method comparable?
• Is the evidence still current?
• Can the technical service accept the evidence for the intended approval?

This approach can identify opportunities to reuse valid technical evidence without assuming that every previous test automatically satisfies R10.

19.17 Not Defining Functional Performance Criteria

Immunity testing is not simply about whether the device remains powered.

The manufacturer needs to define what the equipment is expected to do during the disturbance.

Depending on the product, this may involve:

• Communication
• Control outputs
• Sensor readings
• Actuator functions
• Displays
• Alarms
• Charging functions
• Diagnostic functions

If the expected behaviour is not defined before testing, it can become difficult to determine whether an observed response constitutes an acceptable or unacceptable result.

Functional performance should therefore be considered during test planning, not only when a failure occurs.

19.18 Treating EMC as a Laboratory Problem

A particularly costly mistake is to treat EMC as something that belongs exclusively to the laboratory.

The laboratory can identify whether a configuration passes or fails a defined test.

It cannot compensate for an unclear product scope, uncontrolled variants or poorly defined operating conditions.

EMC performance is influenced by design decisions such as:

• PCB layout
• Filtering
• Grounding
• Shielding
• Component selection
• Cable routing
• Power architecture
• Software behaviour
• Mechanical design

The earlier these aspects are considered, the greater the opportunity to address problems before formal approval testing.

19.19 Not Connecting Compliance With Engineering Change Management

Compliance should not operate independently from product development.

When an engineering change is released, the organization should be able to determine whether the change affects:

• Applicable regulations
• Existing test evidence
• R10 approval
• Product variants
• Production conformity
• Required additional testing

If engineering and compliance systems are disconnected, potentially relevant changes can easily be overlooked.

A structured change-assessment process can close this gap.

19.20 Focusing Only on the Initial Approval

Obtaining the initial R10 approval is only one stage of the product lifecycle.

The product may remain in production for many years.

During that period:

• regulations can change;
• components can become obsolete;
• software can evolve;
• suppliers can change;
• vehicle applications can expand;
• production locations can change;
• new variants can be introduced.

The compliance strategy should therefore continue after the initial approval.

Ongoing monitoring and controlled change management are essential to maintaining the validity of the compliance basis.

19.21 A Better Approach

Most of these mistakes can be avoided by establishing a structured process before testing begins.

A practical approach is:

1. Define the product

What exactly is being assessed?

2. Define the application

Where and how will it be installed?

3. Determine the regulatory framework

Does ECE R10 apply, and which version is relevant?

4. Define the variants

Which hardware, software and installation configurations need to be covered?

5. Review existing evidence

Which previous tests and technical documents can potentially be used?

6. Define the test scope

Which tests, methods, configurations and functional criteria are required?

7. Obtain laboratory quotations

Request quotations against a defined technical scope.

8. Perform testing

Test the agreed and controlled configuration.

9. Review the evidence

Ensure the results support the intended approval.

10. Control future changes

Assess subsequent engineering and production changes against the approved configuration.

This approach makes the approval process more predictable and reduces the likelihood of discovering major compliance gaps late in the project.

19.22 Conclusion

Most ECE R10 problems are not caused by the existence of EMC requirements themselves.

They are often caused by an unclear understanding of what needs to be approved, which configuration needs to be tested and which regulatory requirements actually apply.

The most important mistakes to avoid are therefore:

• Assuming CE EMC compliance is automatically sufficient
• Treating R10 as one generic EMC test
• Starting testing before defining the scope
• Using the wrong test configuration
• Ignoring installation conditions
• Failing to manage product variants
• Overlooking software and component changes
• Using outdated regulatory requirements
• Confusing test reports with type approval
• Failing to maintain configuration control

A structured approach to scoping, testing, documentation and change management can significantly reduce these risks.

For manufacturers, the objective should not be to perform the maximum number of tests.

It should be to establish the correct regulatory scope, the correct test configuration and the correct evidence for the intended approval.

20. How ScopeRight Can Support ECE R10 Projects

ECE R10 projects involve more than laboratory testing. Before a product reaches a technical service or testing laboratory, manufacturers need to determine what exactly has to be assessed, which requirements apply, which product configurations are relevant and what evidence is already available.

This preparation can have a significant impact on project cost, timing and the amount of testing ultimately required.

ScopeRight can support manufacturers in structuring these activities around an ECE R10 project.

ScopeRight is not a testing laboratory, Technical Service or Approval Authority. It does not issue ECE R10 type approvals.

Its role is to help manufacturers structure the compliance process, define the technical and regulatory scope and prepare the project for the activities that must ultimately be performed or accepted by the relevant laboratory, Technical Service and Approval Authority.

20.1 Regulatory scope definition

One of the first challenges in an ECE R10 project is determining the actual regulatory scope.

Before testing begins, manufacturers should establish questions such as:

• What exactly is being approved?
• Is the subject a complete vehicle or an ESA?
• Which vehicle application is relevant?
• Which R10 requirements apply?
• Which R10 version or amendment series is relevant?
• Which product variants need to be considered?
• Which operating modes are relevant?
• Which interfaces and wiring configurations must be included?
• Are existing test results potentially reusable?

ScopeRight can help structure this information so that the project starts with a defined compliance scope rather than an undefined request for “ECE R10 testing.”

This is particularly important when a product has multiple configurations or is intended for use across different vehicle platforms.

20.2 Identifying the applicable requirements

ECE R10 contains a range of requirements covering electromagnetic emissions and immunity.

The exact requirements applicable to a project depend on the approval object and configuration.

A manufacturer therefore needs to establish which requirements are relevant before building the final test program.

ScopeRight can support this process by organizing the relevant regulatory and technical information around the specific product and intended application.

The objective is not to replace the applicable regulation or the Technical Service’s assessment.

Instead, the objective is to create a structured starting point for the project.

20.3 Building a structured test plan

A laboratory needs more than the statement:

“We need ECE R10 testing.”

A useful test plan should identify the relevant:

• emissions tests;
• immunity tests;
• transient tests;
• operating modes;
• functional criteria;
• product configurations;
• cable and harness configurations;
• loads;
• interfaces; and
• applicable test methods.

ScopeRight can help manufacturers organize these elements into a structured test plan.

This gives the manufacturer a clearer overview of what is expected to be tested and provides a more useful basis for discussions with laboratories and Technical Services.

20.4 Defining product variants

Variant management is particularly important in Automotive compliance.

A manufacturer may have several versions of essentially the same product with differences in:

• Hardware
• Software
• PCB configuration
• Power supply
• Communication interfaces
• Connectors
• Cables
• Antennas
• Enclosures
• Operating modes

Not every difference necessarily requires a separate test.

However, each relevant difference should be considered when determining whether one tested configuration can adequately represent another configuration.

ScopeRight can help structure the relevant product information and identify the variants that need to be considered during the scoping process.

The final determination of whether a configuration is covered by an approval remains part of the applicable approval process.

20.5 Preparing laboratory quotations

Laboratory quotations can be difficult to compare when different laboratories interpret the requested scope differently.

For example, one laboratory may quote against a broad interpretation of “ECE R10 testing,” while another may make different assumptions about:

• Number of configurations
• Number of samples
• Test methods
• Operating modes
• Harnesses
• Additional measurements
• Retesting
• Documentation

A structured test plan can make laboratory requests significantly clearer.

ScopeRight can support manufacturers in preparing the information required for an RFQ and in structuring the requested testing scope.

This helps ensure that laboratories are quoting against a defined technical basis rather than against an incomplete description of the product.

20.6 Supporting laboratory selection

ScopeRight does not replace the manufacturer’s decision regarding which laboratory or Technical Service to use.

However, a structured project scope can make the selection process more transparent.

Manufacturers can compare laboratories based on factors such as:

• Quoted test scope
• Included test methods
• Number of test configurations
• Lead time
• Laboratory capabilities
• Required samples
• Additional costs
• Retest conditions
• Documentation
• Technical Service involvement

The goal is not simply to select the lowest laboratory price.

The more important question is whether the quotation actually covers the required project scope.

A low initial quotation can become significantly more expensive if important activities are excluded and have to be added later.

20.7 Reviewing existing test evidence

Manufacturers often enter an R10 project with existing EMC documentation.

This may include:

• Previous EMC test reports
• Development test results
• Component-level EMC reports
• Customer-specific Automotive EMC testing
• CE-related EMC test results
• Previous R10 testing
• Supplier documentation

These documents should not automatically be considered either fully reusable or completely irrelevant.

ScopeRight can help organize and review existing technical evidence against the defined project scope.

The objective is to identify:

• Which requirements have already been tested
• Which configurations were tested
• Which test methods were used
• Which requirements may still need evidence
• Where gaps may exist

Whether a particular report can formally be accepted for a type-approval project ultimately depends on the applicable requirements and the responsible Technical Service or Approval Authority.

20.8 Supporting gap identification

A structured comparison between the intended R10 scope and existing evidence can reveal potential gaps before the product reaches the laboratory.

For example, the manufacturer may discover that:

• One operating mode has not been tested;
• A different cable configuration is required;
• A relevant immunity test is missing;
• An additional product variant exists;
• An older test method was used;
• The existing report covers a different configuration.

Identifying such gaps before formal testing can be considerably more efficient than discovering them after the project has already started.

ScopeRight can support this type of structured gap assessment.

20.9 Test report review

An R10 project can generate substantial technical documentation.

A test report review should not be limited to checking whether the final page says “Pass.”

The report should be considered in relation to the intended approval scope.

Relevant questions can include:

• Is the tested product correctly identified?
• Is the tested configuration documented?
• Are the relevant variants covered?
• Are the operating modes correctly described?
• Are the applicable test methods identified?
• Are the test results complete?
• Are deviations documented?
• Are failures or anomalies explained?
• Does the report correspond to the requested test scope?

ScopeRight can support manufacturers in structuring this review and identifying points that require clarification.

The formal acceptance of the evidence remains with the responsible parties within the type-approval process.

20.10 Supporting change assessment

ECE R10 compliance does not end when the initial approval has been obtained.

Products change throughout their lifecycle.

Changes may involve:

• Electronic components
• PCB design
• Software
• Power supply
• Connectors
• Cable configurations
• Shielding
• Enclosures
• Communication interfaces
• Vehicle applications
• Installation locations

The important question after a change is:

Does this change affect the existing compliance basis?

ScopeRight can support manufacturers in structuring this assessment.

A change can then be classified for further evaluation, for example as:

• No apparent impact on the existing evidence
• Requires technical review
• Requires additional testing
• Potentially requires an approval update or extension

The actual regulatory decision remains dependent on the applicable approval framework and the responsible Technical Service or Approval Authority.

20.11 Connecting engineering changes with compliance

One of the challenges in long-running Automotive projects is that engineering changes and regulatory information are often managed separately.

Engineering may know that a component has changed.

Procurement may know that a supplier has changed.

Software teams may know that a new firmware version has been released.

Compliance needs to know whether any of those changes can affect the existing approval.

A structured compliance workflow can connect these activities.

For example:

Engineering Change → Compliance Assessment → Existing Evidence → Additional Testing? → Approval Impact

This creates a clearer relationship between the product lifecycle and the regulatory status of the product.

20.12 Supporting project coordination

An ECE R10 project can involve several parties:

• Product development
• Compliance
• Procurement
• Laboratory
• Technical Service
• Approval Authority
• Suppliers
• Customers
• Project management

Each party may hold different pieces of information.

ScopeRight can help bring the relevant compliance information into a structured project view.

This can include:

• Product information
• Regulatory requirements
• Test scope
• Test plan
• Laboratory information
• Quotations
• Test reports
• Open questions
• Changes
• Approval documentation

The purpose is to reduce information gaps between the different participants.

20.13 ScopeRight is not the laboratory

This distinction is important.

ScopeRight does not perform the formal ECE R10 laboratory tests.

It does not replace:

• Accredited or designated testing facilities
• Technical Services
• Approval Authorities
• Vehicle manufacturers’ own approval processes

The physical testing and formal regulatory acceptance remain with the appropriate organizations.

ScopeRight’s role is to support the manufacturer before, during and around the testing process by helping structure the compliance information and project activities.

20.14 ScopeRight is not the Approval Authority

The final regulatory approval is not determined by ScopeRight.

The applicable Approval Authority is responsible for the formal type-approval process within the relevant regulatory framework.

Likewise, a Technical Service performs or supports the technical assessment according to the applicable requirements.

ScopeRight can help the manufacturer prepare for these interactions, but it does not issue the approval.

This distinction is important because compliance software should support the approval process rather than create the impression that software itself constitutes regulatory approval.

20.15 Supporting the manufacturer before testing

The greatest opportunity for improving an R10 project often exists before the first formal laboratory test.

Before testing, ScopeRight can help manufacturers structure:

Product → Application → Regulatory Scope → Requirements → Variants → Test Plan → Laboratory RFQ

This creates a defined basis for the subsequent testing activities.

Instead of approaching a laboratory with an incomplete request, the manufacturer can provide a more structured project definition.

This can improve the quality of quotations and reduce uncertainty about what is actually included.

20.16 Supporting the manufacturer after testing

The compliance process continues after the laboratory work.

Once testing is complete, the manufacturer may need to:

• Review the test evidence
• Resolve open issues
• Complete documentation
• Address deviations
• Track approval status
• Manage changes
• Maintain the approved configuration
• Prepare future variants

ScopeRight can support these activities by keeping the relevant compliance information structured and connected to the product configuration.

20.17 Supporting complex and multi-variant products

The value of structured compliance management becomes particularly apparent when a manufacturer has:

• Multiple product variants
• Multiple vehicle applications
• Multiple software versions
• Multiple hardware configurations
• Multiple laboratories
• Multiple customers
• Long product lifecycles

In such projects, information can quickly become fragmented across spreadsheets, emails, laboratory reports and internal engineering systems.

A structured compliance platform can provide a central reference point for the relevant regulatory and technical information.

20.18 Where ScopeRight adds value

The main value of ScopeRight in an ECE R10 project is therefore not replacing the laboratory.

It is helping the manufacturer answer the questions that should be answered before the laboratory work begins.

For example:

What exactly are we approving?

Which requirements apply?

Which configurations need to be covered?

What has already been tested?

What is still missing?

What should we ask the laboratory to quote?

What happens if the product changes?

These questions directly influence project cost, timing and risk.

20.19 A structured ECE R10 workflow with ScopeRight

A manufacturer could structure an R10 project around the following workflow:

1. Product definition

Define the product, intended application and relevant variants.

2. Regulatory scoping

Determine the applicable R10 framework and requirements.

3. Configuration definition

Identify hardware, software, wiring, interfaces and operating modes.

4. Existing evidence review

Collect and assess available test reports and technical documentation.

5. Gap assessment

Identify missing evidence and potential additional testing requirements.

6. Test plan

Create a structured test plan based on the defined scope.

7. Laboratory RFQ

Provide laboratories with a consistent technical scope for quotation.

8. Testing

Perform the required testing with the selected laboratory or Technical Service.

9. Report review

Review the resulting evidence against the defined scope.

10. Approval support

Maintain the information required for the applicable approval process.

11. Change assessment

Evaluate future product changes against the existing compliance basis.

This creates a continuous process rather than treating R10 as a single laboratory event.

20.20 The role of ScopeRight in the overall approval process

The overall relationship can be summarized as:

Manufacturer

defines the product and intended application.

↓

ScopeRight

helps structure the regulatory scope, requirements, configurations, test plan and compliance information.

↓

Laboratory / Technical Service

performs or supports the applicable technical assessment and testing.

↓

Approval Authority

handles the formal type-approval process.

↓

Manufacturer

maintains the approved configuration and manages future changes.

ScopeRight therefore sits around the compliance workflow rather than replacing the organizations responsible for testing and approval.

20.21 Why structured scoping matters

The earlier the scope is defined, the more opportunities the manufacturer has to avoid unnecessary cost and project delays.

A clearly defined scope can help reduce:

• Unnecessary testing
• Ambiguous laboratory quotations
• Missing test configurations
• Unplanned retesting
• Documentation gaps
• Uncontrolled product variants
• Late discovery of compliance issues

This does not guarantee that an R10 project will pass without problems.

It does, however, provide a much stronger basis for managing the project.

20.22 Conclusion

ECE R10 compliance involves regulatory interpretation, technical assessment, laboratory testing, documentation and ongoing configuration management.

The laboratory is an essential part of the process, but the laboratory is not where the project begins.

The project begins with understanding:

What is the product?

Where will it be used?

What exactly needs to be approved?

Which R10 requirements apply?

Which configurations and operating modes need to be covered?

What evidence already exists?

What still needs to be tested?

ScopeRight can support manufacturers in structuring these questions and turning them into a defined compliance workflow.

It can help with regulatory scope definition, requirement identification, test planning, laboratory quotation preparation, existing evidence review, test report review, change assessment and project coordination.

The formal testing and regulatory approval remain with the appropriate laboratory, Technical Service and Approval Authority.

The result is a more structured way to prepare, manage and maintain an ECE R10 compliance project — from the initial scope definition through testing and into the product lifecycle.

21. ECE R10: Key Takeaways for Manufacturers

ECE R10 compliance should not be approached as a single laboratory test that is booked shortly before a vehicle or automotive component is ready for approval.

It is a regulatory and technical process that begins much earlier — with understanding the product, its intended application, the applicable requirements and the configuration that ultimately needs to be approved.

For manufacturers, a well-structured approach can make the difference between a predictable compliance project and one that becomes expensive and difficult to manage.

21.1 Start with the product, not the test

The first question should not be:

“Which ECE R10 tests do we need?”

It should be:

“What exactly are we trying to approve?”

The answer determines much of what follows.

The manufacturer should establish:

• What the product is
• Whether it is a complete vehicle or an ESA
• Its intended vehicle application
• Its intended installation
• Its electrical interfaces
• Its relevant operating modes
• Its product variants
• Its role within the vehicle

Only after these points are understood can the applicable R10 requirements be properly assessed.

21.2 Determine whether ECE R10 actually applies

Not every electronic product used in connection with a vehicle automatically requires an individual ECE-R10 approval.

The applicability depends on the regulatory framework and the specific characteristics and intended use of the equipment.

Manufacturers should therefore establish early:

• Whether the product falls within the applicable R10 scope
• Whether it is being assessed as an ESA
• Whether it is part of a vehicle-level approval
• Which vehicle type-approval framework applies
• Whether additional regulatory frameworks are relevant

This prevents a common mistake: defining a complete test program before establishing whether that test program is actually required.

21.3 Identify the applicable R10 version

ECE R10 has evolved through revisions and amendment series.

The phrase “ECE R10 compliant” therefore does not provide enough information by itself for a project.

The manufacturer should determine:

• The applicable revision or amendment series
• Relevant supplements and corrigenda
• Transitional provisions
• Referenced standards
• Applicable editions of those standards

This should be established at the beginning of the project.

Using an outdated requirement set can create problems later, particularly when a project extends over a long development period.

21.4 Define the complete test configuration

The test sample is only one part of an Automotive EMC test.

The configuration surrounding the product can significantly influence the result.

Before testing, manufacturers should define, where relevant:

• Power supply
• Harnesses
• Cable lengths
• Connectors
• Loads
• Communication interfaces
• Operating modes
• Software version
• Auxiliary equipment
• Grounding and shielding
• Installation conditions

The configuration used to demonstrate compliance should be clearly documented.

This becomes particularly important when the same product is supplied in multiple variants or installed in different vehicle platforms.

21.5 Identify the functions that must remain operational

Immunity testing is not simply about keeping the device powered.

The manufacturer needs to understand what the equipment is expected to do while exposed to electromagnetic disturbances.

Depending on the product, this may involve:

• Communication
• Control outputs
• Sensor signals
• Actuator functions
• Displays
• Alarms
• Charging functions
• Diagnostic functions
• Other critical functions

These functional criteria should be defined before testing begins.

Otherwise, it can become difficult to determine whether an observed change during testing represents an acceptable behavior or a failure.

21.6 Review existing EMC evidence before commissioning new tests

Many manufacturers already have technical evidence available.

This may include:

• Previous EMC reports
• Development testing
• Customer-specific Automotive EMC testing
• CE-related EMC testing
• Previous R10 testing
• Supplier test reports
• Component-level evidence

These documents should be reviewed before automatically commissioning another complete test program.

The relevant question is not:

“Do we already have an EMC report?”

It is:

“Does the existing evidence address the requirements and configuration relevant to this R10 project?”

A structured gap assessment can identify where existing evidence may be useful and where additional testing may still be required.

21.7 Do not assume that CE EMC compliance equals R10 approval

CE EMC compliance and ECE R10 belong to different regulatory frameworks.

A product can have valid CE EMC conformity and still require an assessment within the ECE R10 type-approval framework.

At the same time, existing CE EMC test results may provide useful technical evidence for an R10 project.

The correct approach is therefore to assess the existing evidence rather than automatically accepting or rejecting it.

21.8 Choose the approval route carefully

ECE R10 approvals are part of the UNECE type-approval system.

Manufacturers may therefore have practical considerations when deciding where and through which approval authority to conduct the approval process.

Factors can include:

• Availability of the relevant approval authority
• Technical Service capabilities
• Experience with the product category
• Lead time
• Administrative process
• Cost
• Communication
• Customer requirements
• Intended markets

Different approval authorities within the UNECE framework can issue approvals under the same UN regulation, subject to the applicable framework.

The choice of approval route can therefore be a practical project consideration, but it does not mean that the technical requirements of ECE R10 can simply be selected or reduced by choosing a particular country.

21.9 Keep the distinction between testing and approval

A laboratory test and a type approval are related, but they are not the same thing.

A test report provides technical evidence from a defined test.

The type approval is the formal regulatory approval within the applicable vehicle type-approval framework.

Manufacturers should therefore keep track of:

Test evidence

and

Approval status

as separate but connected elements of the compliance process.

This distinction becomes particularly important when communicating compliance status to customers or when managing multiple products and approvals.

21.10 Control product variants

Variant management is one of the most important long-term aspects of Automotive compliance.

A product may have different:

• Hardware versions
• Software versions
• Connectors
• Cable configurations
• Power supplies
• Communication interfaces
• Enclosures
• Antennas
• Operating modes

A change does not automatically invalidate an approval.

However, neither should it automatically be assumed that the approval remains unaffected.

Each relevant change should be assessed against the approved configuration and the existing compliance evidence.

21.11 Integrate compliance into engineering change management

Compliance should not operate independently from product development.

When Engineering proposes a change, the compliance process should be able to answer:

Could this change affect the existing R10 compliance basis?

Examples include:

• Component replacement
• PCB redesign
• Firmware update
• New connector
• Cable change
• Shielding modification
• Power supply change
• New installation location

A structured change-assessment process allows manufacturers to identify potential compliance impacts before the changed product enters production.

21.12 Consider the entire product lifecycle

ECE R10 compliance does not end when the first approval is issued.

The product may remain in production for many years.

During that time, the manufacturer may introduce:

• New components
• New suppliers
• New software
• New variants
• New vehicle applications
• Manufacturing changes
• Updated electronic architectures

The manufacturer therefore needs a process for maintaining the relationship between the approved configuration and the actual product being manufactured.

This is essential for maintaining conformity over the product lifecycle.

21.13 Do not treat the laboratory as the starting point

The laboratory is an important part of the R10 process, but it should not be the place where the project scope is discovered.

Before requesting a quotation, the manufacturer should ideally understand:

• What needs to be approved
• Which requirements apply
• Which configurations are relevant
• Which tests are expected
• Which evidence already exists
• Which variants need to be considered
• What documentation is available

This gives the laboratory a much clearer basis for preparing an offer.

It also makes quotations from different laboratories easier to compare.

21.14 Compare laboratory quotations based on scope

The cheapest quotation is not necessarily the lowest-cost option.

Two laboratories may quote different prices because they have interpreted the requested scope differently.

For example, one quotation may include:

• One configuration
• One operating mode
• A limited number of tests

while another may include:

• Multiple configurations
• Additional operating modes
• Additional documentation
• Retesting provisions

The manufacturer should therefore compare quotations based on what is included, not simply on the final price.

A clearly defined test scope is essential for making this comparison meaningful.

21.15 Plan for failures and retesting

Even a well-prepared product can encounter an EMC issue during formal testing.

Manufacturers should therefore consider the possibility of:

• Test failures
• Troubleshooting
• Design modifications
• Retesting
• Additional laboratory time
• Documentation updates

A project plan that assumes every test will pass on the first attempt can underestimate the actual schedule and budget.

Pre-compliance testing and early EMC analysis can help reduce this risk.

21.16 Treat EMC as part of product design

The best time to address an EMC problem is usually before the product reaches the formal approval test.

Relevant design considerations can include:

• PCB layout
• Filtering
• Grounding
• Shielding
• Component selection
• Power architecture
• Cable routing
• Connector design
• Enclosure design
• Software behavior

EMC should therefore be considered throughout product development rather than being treated exclusively as a certification activity.

21.17 Keep the documentation connected to the product configuration

A strong compliance process should make it possible to answer:

Which exact product configuration was tested?

This should include, where relevant:

• Hardware revision
• Software version
• Component configuration
• Cable configuration
• Test setup
• Operating modes
• Applicable standards
• Test reports
• Approval documents

Without this connection, it becomes increasingly difficult to determine whether a future product variant remains within the demonstrated compliance basis.

21.18 Think beyond the initial approval

An R10 approval is not the end of the compliance process.

Manufacturers should also consider:

• Future product variants
• Engineering changes
• New vehicle applications
• Regulatory updates
• Production changes
• Supplier changes
• Additional approvals

A compliance strategy that considers these issues from the beginning is much easier to maintain than one that only focuses on obtaining the first approval.

21.19 The questions manufacturers should answer before testing

Before an ECE R10 project enters the laboratory, the manufacturer should ideally be able to answer the following questions:

1. What exactly are we approving?
2. Does ECE R10 apply to this product?
3. Which R10 version and amendment status apply?
4. Are we dealing with vehicle-level or ESA-level requirements?
5. Which product variants are relevant?
6. Which operating modes must be tested?
7. Which cables, loads and interfaces must be included?
8. Which functions must be monitored during immunity testing?
9. What EMC evidence already exists?
10. What gaps remain?
11. What exactly should the laboratory quote?
12. How will future product changes be assessed?

If these questions cannot yet be answered, the project may not be ready for formal testing.

21.20 Where ScopeRight fits into this process

ScopeRight can support manufacturers in organizing these activities before and around the formal testing process.

The platform can help structure:

• Regulatory scope
• Applicable requirements
• Product information
• Product variants
• Test planning
• Existing compliance evidence
• Gap assessment
• Laboratory RFQs
• Test documentation
• Report review
• Change assessment
• Compliance project information

ScopeRight does not replace the laboratory, Technical Service or Approval Authority.

Its role is to help manufacturers create a structured compliance basis so that the technical and regulatory activities performed by those organizations can begin with a clearer understanding of the project.

21.21 The overall principle

The most important lesson from an ECE R10 project is simple:

The quality of the compliance process depends heavily on the quality of the scope defined before testing begins.

A manufacturer that clearly understands the product, application, configuration, requirements and existing evidence has a much stronger basis for:

• Planning the test program
• Comparing laboratory quotations
• Avoiding unnecessary testing
• Managing variants
• Handling changes
• Controlling documentation
• Maintaining compliance

ECE R10 should therefore be treated as a structured compliance process rather than a single laboratory appointment.

21.22 Final takeaway

For manufacturers, the most important ECE R10 questions are not limited to:

“Will the product pass?”

The more important questions are:

“What exactly needs to be demonstrated?”

“Which requirements apply?”

“Which configuration needs to be tested?”

“What evidence do we already have?”

“What is still missing?”

“How will we maintain the approval when the product changes?”

Answering these questions early creates a stronger foundation for the entire approval process.

ECE R10 compliance is ultimately about more than obtaining a successful test result.

It is about establishing a clear, traceable and maintainable compliance basis for the product throughout its lifecycle.

22. Official References and Further Information

ECE R10 is part of the UNECE vehicle type-approval framework. Because the regulation is amended over time, manufacturers should use the official UNECE documents as the primary source when determining the applicable requirements for a specific approval project.

22.1 UNECE and the Vehicle Regulations Framework

The United Nations Economic Commission for Europe (UNECE) maintains the regulatory framework for vehicle type approval under the 1958 Agreement and publishes the relevant UN Regulations, amendments, supplements and related working documents.

For ECE R10 projects, the UNECE vehicle-regulations database should be treated as the starting point for checking the current regulatory status.

UNECE provides the official text of UN Regulation No. 10 – Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility, together with its revisions and amendments.

22.2 UN Regulation No. 10

The official regulation is the primary reference for determining:

• the scope of ECE R10;
• definitions;
• approval requirements;
• marking requirements;
• conformity of production provisions;
• modifications and extensions of approval;
• technical requirements;
• test methods;
• applicable limits; and
• the relevant annexes.

UNECE currently provides Revision 6 of UN Regulation No. 10 and lists amendments to that revision. The UNECE database also provides the corresponding documents in English, French and Russian. (UNECE)

For a real project, the manufacturer should not rely on a general statement such as “R10 Rev.6” alone. The applicable amendment and supplement status should also be checked.

22.3 Amendments and Supplements

UN Regulations are updated through formal amendment series and supplements.

This is particularly important for ECE R10 because the regulation continues to evolve in response to developments in automotive electronics and EMC technology.

UNECE documentation shows the development of the 07 series of amendments to UN Regulation No. 10, with subsequent proposals for supplements to that series. (UNECE)

The manufacturer should therefore distinguish between:

Adopted and applicable requirements

and

Proposals or working documents under development.

A proposal published by UNECE is not automatically an applicable legal requirement merely because it appears in the UNECE document database.

The actual entry-into-force status and applicable transitional provisions must be verified.

22.4 Entry into Force and Transitional Provisions

When a new amendment series or supplement is adopted, the date on which it enters into force and the transitional provisions determine when and how it affects approvals.

This is particularly important for manufacturers whose development and approval projects extend over several years.

A project may begin under one regulatory version and reach formal approval after a newer amendment has entered into force.

The manufacturer should therefore establish:

• the applicable version at the start of the project;
• the applicable version at the time of approval;
• whether transitional provisions apply;
• whether existing approvals are affected; and
• whether an extension or updated approval is required.

These questions should be answered from the applicable regulatory documents rather than from an undated secondary summary.

22.5 UNECE Contracting Parties and Approval Authorities

The UNECE vehicle type-approval system operates through contracting parties to the relevant agreements.

The official UN R10 documentation identifies contracting parties and the corresponding approval arrangements.

This is relevant when a manufacturer is considering where an approval should be obtained.

The approval country is identified through the E-mark associated with the approval. The country code therefore identifies the contracting party whose approval authority issued the approval.

The official UNECE material provides the authoritative basis for identifying the participating countries and their approval arrangements.

22.6 Relevant UNECE Working Groups

The technical development of UN Regulation No. 10 takes place within the UNECE vehicle-regulations structure, including the relevant working groups dealing with electromagnetic compatibility and vehicle regulations.

For manufacturers that need to follow future developments, UNECE working documents can provide useful insight into proposed changes before they become part of the applicable regulation.

However, working documents should be treated as regulatory-development material, not automatically as current compliance requirements.

This distinction is particularly important when using regulatory information for product planning.

22.7 Referenced Technical Standards

ECE R10 works together with referenced technical standards and test methods.

Depending on the applicable requirement, these can include standards such as:

• CISPR 12
• CISPR 25
• ISO 11451 series
• ISO 11452 series
• ISO 7637 series

The applicable standard and edition should always be determined from the relevant version of UN R10.

Manufacturers should avoid building a test plan solely from a generic list of automotive EMC standards. The relevant R10 provisions determine which methods apply to the specific approval scope.

22.8 Other Vehicle Type-Approval Legislation

UN R10 does not exist in isolation from the wider vehicle type-approval framework.

Depending on the market and approval route, manufacturers may also need to consider applicable vehicle type-approval legislation and related regulatory requirements.

For products supplied into the European Union, this can include the EU vehicle type-approval framework in addition to the UNECE regulations incorporated or referenced within that framework.

The manufacturer should therefore distinguish between:

The technical requirements of UN R10

and

The wider legal framework under which the vehicle or component is being type-approved.

The relationship between these frameworks should be established for the specific project.

22.9 Official Information Should Take Priority Over Secondary Sources

Automotive regulatory information is frequently reproduced by laboratories, consultants, industry associations and technical websites.

These sources can be useful for explanation and practical interpretation, but the manufacturer should use the official regulatory documents when making a final compliance decision.

In particular, the following should be verified against the official source:

• applicable R10 revision;
• amendment series;
• supplements;
• entry-into-force dates;
• transitional provisions;
• applicable test requirements;
• approval procedures; and
• approval status.

This is especially important where a project depends on a specific deadline or where a regulatory change may affect an existing approval.

22.10 Useful Official Reference Points

The following UNECE resources are particularly relevant when working with ECE R10:

UNECE Vehicle Regulations Database

The UNECE vehicle-regulations pages provide access to the UN Regulations developed under the vehicle type-approval framework.

UN Regulation No. 10 – Revision 6 and Amendments

The UNECE database provides the official consolidated regulation and the associated amendments to Revision 6. (UNECE)

UNECE Working Documents on the 07 Series

The UNECE working documents provide information on the development of the 07 series of amendments and subsequent supplements. (UNECE)

These documents are useful when assessing upcoming regulatory developments, but their legal status must always be distinguished from adopted requirements.

22.11 How Manufacturers Should Use These References

For a new ECE-R10 project, a practical regulatory research sequence is:

1. Identify the approval object

Determine whether the project concerns a vehicle or an ESA.

2. Identify the applicable regulatory framework

Determine which vehicle type-approval legislation and UNECE requirements apply.

3. Identify the applicable UN R10 version

Check the relevant revision, amendment series and supplements.

4. Check entry into force and transitional provisions

Determine whether a new amendment applies to the project.

5. Identify the applicable technical requirements

Determine the relevant R10 annexes, test methods and referenced standards.

6. Define the technical configuration

Establish the product, variants, wiring, operating modes and installation conditions.

7. Build the test and compliance plan

Only after the regulatory scope and technical configuration are defined should the detailed laboratory program be finalized.

22.12 Why Regulatory Monitoring Matters

ECE R10 is not a static document.

The ongoing development of amendments and supplements demonstrates that automotive EMC requirements continue to evolve.

For manufacturers with long product lifecycles, regulatory monitoring is therefore an important part of compliance management.

A change in the applicable regulation can potentially affect:

• new product approvals;
• future variants;
• test plans;
• referenced standards;
• approval extensions;
• existing approval strategies; and
• development schedules.

Manufacturers should therefore establish a process for identifying relevant regulatory changes and determining whether those changes affect their products.

22.13 Final Takeaway

The official UNECE documentation should always be the primary reference for ECE R10.

Secondary sources can help explain the regulation, but the final compliance decision should be based on the applicable official version, amendments, supplements and entry-into-force provisions.

For manufacturers, the most important references are therefore not simply a list of EMC standards. The complete regulatory chain must be understood:

UNECE framework → UN Regulation No. 10 → applicable revision and amendments → technical requirements → referenced standards → test evidence → type approval

Keeping this chain clear helps manufacturers avoid one of the most common problems in regulatory compliance: using technically relevant information that is no longer the legally applicable information for the specific approval project.

Official UNECE sources

• UNECE – Addenda to the 1958 Agreement, Regulations 0–20, including UN Regulation No. 10, Revision 6 and its amendments. (UNECE)
• UNECE – Proposal for the 07 series of amendments to UN Regulation No. 10. (UNECE)
• UNECE – Proposal for a Supplement to the 07 series of amendments, published in 2026. (UNECE)
• UNECE – Status of adopted proposals and entry into force under the 1958 Agreement. (UNECE)