Real Driving Emissions (RDE) Testing

Real Driving Emissions (RDE) Testing

1. What Is Real Driving Emissions (RDE) Testing?

Real Driving Emissions (RDE) Testing measures a vehicle’s exhaust emissions while it operates on public roads using a portable emissions measurement system (PEMS). It complements laboratory testing by examining emissions under a broader range of driving and environmental conditions. RDE is a regulated validation procedure, not a conventional management framework or vehicle-safety test.

For passenger vehicle manufacturers, it provides evidence for a consequential decision: whether a powertrain and emissions-control system are ready for approval and release. Consultants can help organize testing capacity, evidence, corrective actions, and decision governance; qualified emissions specialists must perform and interpret the technical work.

2. Origin and Background

RDE has no single individual creator. The European Commission established its Real-Driving Emissions–Light-Duty Vehicles working group in January 2011, supported by the Joint Research Centre and stakeholder participation. The objective was to address the discrepancy between laboratory results and on-road pollutant emissions, particularly nitrogen oxides from diesel vehicles. Development therefore preceded the 2015 diesel-emissions scandal.

The initial procedure entered European legislation in 2016. Binding requirements were phased in for new passenger-car types from September 2017 and new passenger cars from September 2019. Subsequent development expanded the procedure’s treatment of cold starts, particle-number measurement, and in-service conformity. RDE evolved from an additional measurement exercise into part of a broader compliance system.

3. How Real Driving Emissions (RDE) Testing Works

The acronym describes the method’s essential features, rather than three separate testing stages:

  • R — Real: Measurements occur outside the laboratory, within defined environmental and operating boundaries.
  • D — Driving: The vehicle follows an on-road trip containing urban, rural, and motorway operation, rather than reproducing a fixed laboratory speed trace.
  • E — Emissions: Portable instruments measure exhaust pollutants; the applicable regulation determines the required measurements, processing, and acceptance criteria.

Published implementation guidance describes six technical stages: vehicle selection, vehicle preparation, trip design, trip execution, trip verification, and emissions calculation. Their order matters. A result is useful only when both the measurement system and the trip satisfy the relevant requirements.

PEMS data are synchronized with exhaust-flow, vehicle-motion, and environmental measurements to calculate emissions per distance traveled. Important European light-duty outputs include nitrogen oxides, commonly reported in milligrams per kilometer, and particle number, reported as particles per kilometer. Prescribed processing and uncertainty treatment mean that a raw trip average is not necessarily the final regulatory result.

The appropriate business unit of analysis is usually a defined vehicle configuration and its relationship to the applicable emissions-testing family—not simply a model name. Record powertrain hardware, aftertreatment, transmission, software, vehicle mass, and relevant hybrid operating states. Executives should distinguish three questions: Was the test valid? Did the evaluated result comply? Does the development evidence demonstrate sufficient robustness?

4. When to Use Real Driving Emissions (RDE) Testing

Use RDE during combustion-engine and hybrid development, homologation preparation, relevant engineering changes, and applicable in-service conformity investigations. It is especially valuable when laboratory results appear satisfactory but the team needs to understand behavior across road conditions. Cold-start treatment matters because emissions before the engine and aftertreatment warm up can materially affect the evaluated trip.

For automotive suppliers, the practical question is often how a catalyst, filter, sensor, or control-system change performs after integration into the complete vehicle. Component-level evidence should inform—but not substitute for—the manufacturer’s vehicle-level validation plan.

Required inputs include the applicable protocol, configuration records, laboratory reference data, calibrated instruments, route information, and synchronized measurements. Assemble homologation, calibration, aftertreatment, test operations, and data specialists. Plan effort around vehicle availability, conditioning, weather, instrumentation, repeat testing, and analysis—not just driving time.

RDE is not an unrestricted survey of every customer journey. Its validity boundaries can exclude real operating situations, so supplement it when investigating unusual duty cycles. Nor does a European RDE result replace the separate United States Environmental Protection Agency certification process.

Where failures recur across programs, connect the testing workflow to quality management: consistent issue classification, clear ownership, controlled releases, and evidence-based closure are more useful than additional dashboard reporting alone.

5. How to Apply Real Driving Emissions (RDE) Testing: Step-by-Step

  1. Clarify the decision and regulatory scope.

    Specify whether the work supports development, approval, a change assessment, or an in-service investigation. Identify market, vehicle category, approval timing, and applicable regulatory version. Separate mandatory acceptance criteria from internal engineering targets.

  2. Gather configuration and reference data.

    Collect hardware identifiers, software versions, fuel specifications, vehicle history, laboratory results, instrument records, and previous road-test files. For hybrids, include battery state of charge and engine-operation history where relevant to the protocol.

  3. Select vehicles and define coverage.

    Map configurations to the applicable testing-family rules. Use engineering judgment to identify potentially challenging combinations, but do not assume that a commercially representative trim is automatically an acceptable regulatory representative.

  4. Design the route and coverage matrix.

    Plan urban, rural, and motorway operation within the required boundaries. Build a matrix linking vehicles, conditions, objectives, and acceptance criteria. Keep exploratory stress tests distinct from trips intended to produce formal compliance evidence.

  5. Prepare and validate the measurement system.

    Install PEMS safely, check sampling integrity, perform required calibration and validation checks, and synchronize signals. Preserve setup records. An instrumentation problem can undermine an otherwise well-executed campaign.

  6. Execute the trip and verify validity.

    Follow the prescribed preparation and driving requirements. Record interruptions, traffic, weather, and deviations. Complete instrument and trip-validity checks before interpreting acceptance; document invalid tests rather than quietly removing them.

  7. Calculate results and diagnose patterns.

    Use controlled processing software implementing the applicable method. Review required evaluation outputs and underlying time-series data. Investigate emissions events alongside engine state and aftertreatment behavior; do not infer a root cause from the final average alone.

  8. Translate findings into controlled actions.

    Assign responsibility for calibration, hardware, instrumentation, or process changes. Specify affected variants, verification requirements, release controls, and closure evidence. Assess approval implications before incorporating a change into production.

  9. Test robustness, align stakeholders, and iterate.

    Challenge development conclusions across additional permitted conditions and representative configurations. Resolve disagreements among engineering, suppliers, and homologation teams. Broaden engineering coverage without changing regulatory calculations or selecting only favorable results.

6. Example: Real Driving Emissions (RDE) Testing in Action

Fictional example: Alder Mobility is preparing a diesel crossover for European approval. Laboratory testing is satisfactory, but development road tests show inconsistent nitrogen-oxide results during the early urban portion. The chief engineer needs to determine whether to release the calibration or fund additional remediation.

The team defines its units as vehicle hardware-and-software configurations. It records test preparation, ambient conditions, instrument checks, and aftertreatment temperatures, then compares valid development trips using the prescribed processing method.

Time-series analysis identifies delayed aftertreatment warm-up as the leading hypothesis for one configuration. The team first checks measurement integrity, then conducts controlled diagnostic work rather than attributing every difference to the catalyst supplier.

Alder revises the warm-up calibration and verifies its effects on emissions, drivability, and other release requirements. It repeats the required validation, reviews related configurations, and updates its approval evidence before authorizing release.

The follow-on management work is a corrective and preventive action program: establish configuration traceability, ownership, verification criteria, and controls preventing the same issue from recurring. The example illustrates decision discipline, not an industry benchmark or guaranteed technical remedy.

7. Strengths and Limitations

Strengths

  • Broader operating evidence: Road testing complements the controlled laboratory environment and exposes performance across varying conditions.
  • System-level visibility: Teams can investigate integrated vehicle behavior rather than treating engine, software, and aftertreatment decisions independently.
  • Clearer release discussions: Separating validity, compliance, and robustness helps executives avoid treating one favorable result as complete readiness evidence.

Limitations

RDE covers a defined operating envelope, not every possible journey. Traffic and environmental variability complicate direct comparisons, while portable instruments introduce measurement uncertainty. Compliance results therefore need careful interpretation; they do not establish that every vehicle will behave identically throughout its life.

RDE also does not replace the broader approval and validation program. Euro 7, adopted in 2024, includes requirements beyond exhaust emissions, including brake-particle emissions and battery durability. Passing a tailpipe test is not equivalent to satisfying the entire regulatory regime.

8. Common Pitfalls and How to Avoid Them

  • Using obsolete acceptance rules: Historic conformity factors or processing methods can produce an incorrect conclusion. Freeze the applicable protocol and software version before testing, with homologation review.
  • Confusing invalidity with failure: A trip outside the protocol and a valid noncompliant result are different findings. Report validity and emissions acceptance separately; retain both records.
  • Optimizing for one route: A familiar route can create unjustified confidence. Broaden development coverage across relevant permitted conditions and retain supplementary investigation results.
  • Losing configuration traceability: An undocumented calibration or component change makes comparisons unreliable. Link each trip to controlled vehicle, hardware, software, and instrumentation records.
  • Discarding inconvenient observations: Selective reporting hides weaknesses. Establish exclusion rules in advance and distinguish regulatory processing from engineering investigation.
  • Closing issues without verification: A plausible technical explanation is not proof of resolution. Require repeat evidence, assessment of affected variants, and explicit release authorization.

9. How Real Driving Emissions (RDE) Testing Relates to Other Frameworks

WLTP: Complementary laboratory evidence

The Worldwide Harmonised Light Vehicles Test Procedure (WLTP) provides standardized laboratory testing. RDE provides complementary on-road evidence. Use laboratory work to establish controlled reference behavior and investigate repeatable mechanisms; use RDE to evaluate performance under its road-testing requirements. Neither should be treated as a universal substitute for the other.

FMEA: Prioritize potential failure mechanisms

Failure Mode and Effects Analysis (FMEA) structures product and process risk assessment. Before testing, use it to identify hypotheses concerning sensors, thermal management, dosing, or control interactions. After testing, update the analysis with observed evidence. FMEA prioritizes risks; it does not measure emissions or confer approval.

Design of Experiments: Investigate causality

Design of Experiments structures controlled changes to inputs to understand their effects. Apply it alongside RDE when investigating a mechanism that uncontrolled road comparisons cannot isolate. Use laboratory or suitable development experiments to evaluate hypotheses, then verify the resulting solution through the required vehicle-validation process.

10. Key Takeaways

  • RDE is a regulated on-road emissions procedure, not a general strategy framework.
  • Separate test validity, regulatory acceptance, and engineering robustness.
  • Analyze defined configurations and controlled software releases—not model names alone.
  • Connect findings to owned corrective actions, revalidation, and release decisions.
  • Use complementary evidence for operating conditions and requirements outside RDE’s scope.

11. FAQs About Real Driving Emissions (RDE) Testing

What is the difference between RDE and WLTP?

WLTP uses standardized laboratory conditions; RDE measures emissions on the road within prescribed boundaries. They provide complementary evidence, not interchangeable approval results.

Does RDE apply to battery-electric vehicles?

Conventional tailpipe RDE testing concerns exhaust emissions, which battery-electric vehicles do not produce. Other requirements, such as brake-particle emissions and battery durability, require separate assessment under the applicable regime.

Can smaller manufacturers use RDE testing effectively?

Yes. Consider qualified external testing providers rather than immediately investing in an internal PEMS fleet. Retain ownership of configuration records, test objectives, applicable requirements, and release decisions.

How long does an RDE testing campaign take?

Estimate the campaign from its vehicle coverage, preparation, equipment availability, weather constraints, repeat-test allowance, and analysis workload. Driving time alone is a poor planning basis. Agree the evidence package and approval dependencies before committing to a completion date.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]