UN-R 171
DCAS · 01 series of amendments
Driver assistance systems for vehicle control (Driver Control Assistance Systems).
- 46 logical scenarios according to Annex 4
- Test report Annex 4
- Demo dataset to try out
Why SCENARIUM?
From regulation to test report in one continuous chain.
Approval testing under UN-R 171, (EU) 2022/1426 or UN-R 185 involves dozens of scenarios, test specifications, approvals and runs. SCENARIUM links them: every requirement can be traced from the regulation text to the evaluated run in the test report.
parametrised→Approved by TS→evaluated→passed
Time and cost
No more manual tables.
Today, approval tests are often prepared with many Excel spreadsheets, copied-out limits and reports pieced together by copy and paste. Every transfer takes time and is a source of errors. An error that only shows up in the test report means renewed coordination with the Technical Service or even a retest on the test track. SCENARIUM takes this manual work off your hands, saving a great deal of time – and therefore cost – in preparation, evaluation and reporting.
Manual tables
With SCENARIUM
Parameter
Transferring limits from the regulation text and manufacturer's declaration into tables by hand.
Limits are resolved automatically from the regulation and system capability; impermissible combinations are blocked.
Approval
Sending test specifications back and forth by email, reconciling versions by hand.
Submission, checklist and approval by the TS in one place, with a complete history.
Evaluation
Calculating metrics per run with formulas and comparing them with limits.
Upload one CSV per run from the template: key values, validity, run protocol and evaluation of each run are generated automatically.
Evidence status
Maintaining your own status list of where each mandatory test stands.
Visible for every mandatory test: parametrised, approved by the TS, evaluated, passed.
Simulation
Rebuilding scenarios by hand a second time for the simulation environment.
Export of scenarios as OpenSCENARIO, e.g. for SiL and HiL simulation environments. (not included in the demo)
Test report
Copying results and charts together into a text document.
Test report according to Annex 4 or Annex III at the push of a button, ready to print as PDF.
One platform for DCAS and AD.
SCENARIUM is designed for all scenario-based approval tests in the DCAS and AD field. It is set up for UN-R 171 (DCAS), Commission Implementing Regulation (EU) 2022/1426 (ADS Level 4) and UN-R 185 (ADS); in the demo, you switch between them in the demo bar at the top. Scenarios, requirements and report template are data rather than program code – further regulations can therefore be added with minor changes.
(EU) 2022/1426
AD · ADS Level 4 · Implementing Regulation
Type approval of the automated driving system (ADS) of fully automated vehicles – shuttle, hub-to-hub, valet parking.
- 33 logical scenarios according to Annex III Part 3 point 8 and Annex II
- Parameters from Annex III Part 1 (TTC_cut-in, TTC_dyn, pedestrian/cyclist) and UN-R 157
- Test report according to Annex III · demo with fictitious Level 4 shuttle
UN-R 185
AD · ADS · 00 series
Automated Driving Systems (ADS) – scenarios derived according to Annex 7 from the manufacturer's ODD declaration.
- 32 logical scenarios from ODD, interactions and behavioural competencies (nominal, critical, failure)
- Confirmatory tests of the Technical Service with the test areas (a)–(h)
- Virtual testing with sampling plan · demo with a fictitious urban shuttle
UN-R 157
AD · ALKS
Automated Lane Keeping Systems.
- own scenario library and requirements
- same workflow: parametrise, approve, evaluate
Three steps to the evidence.
The data flows through – nothing is entered twice.
1
Select and parametrise scenario
You start with a logical scenario from the library. Limits that depend on your vehicle come from the system capability.
- Select a scenario, e.g. Decelerating lead vehicle.
- Enter the system capability of the vehicle type: v_max 130 km/h limits the parameter space.
- Set concrete values. The test is parametrised.
input/scenarios
2
Get it approved by the Technical Service
The parameters produce the test specification. The Technical Service checks it against a checklist and approves it; only approved specifications count.
- Submit test specification.
- The TS ticks off the checklist items.
- Approval with date. Status: Approved by TS.
output/test_specs
3
Evaluate measurement data
Driving takes place on the test track. For each test specification, the testers receive a CSV template with exactly the columns needed and the run protocol; each measurement file is assigned to a run and evaluated automatically.
- Upload one CSV per run – assigned via the run protocol.
- Metrics are calculated: evaluated.
- All runs meet the criteria: passed.
input/measurements · output/results
Passed means: all mandatory tests passed.
SCENARIUM shows how far each mandatory test has progressed. The approval tests only count as passed once every mandatory test is passed. Until then, the number still missing is shown in red.
You then generate the test report according to Annex 4 or Annex III, ready to print as PDF.
output/test_reports
Simulation
Ready for virtual testing.
Every test specification is exported as ASAM OpenSCENARIO with an OpenDRIVE road. The same scenarios as on the proving ground thus also run in simulation environments (SiL, HiL) and form the basis for virtual testing.
- ASAM OpenSCENARIO 1.2
- ASAM OpenDRIVE
- SiL · HiL
DEMO What you see here
Trying it out is explicitly encouraged.
The demo contains three complete datasets: UN-R 171 (DCAS) with 46 scenarios, (EU) 2022/1426 (ADS Level 4) with 33 scenarios and UN-R 185 (ADS) with 32 scenarios – each with test specifications and synthetic runs (CSV with run protocol) in all states – verified, repeat required, invalid, simulation, outdated. You switch between them in the demo bar at the top (“Regulation”). Click through all three steps and generate your own test report.
- Three regulations. UN-R 171 (DCAS), (EU) 2022/1426 (ADS Level 4) or UN-R 185 (ADS) – switch in the demo bar at the top, and the app loads the matching scenarios.
- Fictitious data. Vehicle, measured values and approvals are fictitious – the results are not valid evidence.
- Stays with you. What you save stays only in your browser. “Reset demo” restores the initial state.
- Your own data? In Chrome or Edge, connect your own SCENARIUM folder – files are then read and saved directly there.
Frequently asked questions about approval tests under UN-R 171, (EU) 2022/1426 and UN-R 185.
What is DCAS?
DCAS stands for Driver Control Assistance Systems: driver assistance systems that continuously assist the driver with longitudinal and lateral control – for example keeping the lane, keeping a distance or changing lanes. The driver remains responsible at all times and must stay engaged in the driving task.
What does UN Regulation No. 171 cover?
UN-R 171 sets out the requirements for DCAS for type approval: positioning of the vehicle in the lane of travel, lane changes and other manoeuvres, response to other road users, system boundaries, driver state monitoring with warnings when the driver is motorically or visually disengaged, system safety response to detected failures and HMI. Compliance is demonstrated through tests on the test track and on public roads (Annex 4) and through an audit (Annex 3). SCENARIUM is set up for the 01 series of amendments.
What does Commission Implementing Regulation (EU) 2022/1426 cover?
It lays down uniform procedures and technical specifications for the EU type-approval of the automated driving system (ADS) of fully automated vehicles – vehicles without a driver as fallback (Level 4), such as shuttles on predefined routes (hub-to-hub), in predefined areas or for automated valet parking. Annex II contains the performance requirements (dynamic driving task, emergency operation, ODD boundaries, faults, minimal risk manoeuvre, HMI, ADS data), Annex III the traffic scenarios and parameters (Part 1), the assessment of the safety concept (Part 2) and the minimum tests on the test track and on-road (Part 3). For lane changes and crossing pedestrians on the motorway, it refers to UN-R 157.
How are the scenarios of UN-R 185 derived?
According to Annex 7 of UN-R 185, in five stages: the manufacturer describes the operational design domain in the ODD declaration (§ 7.3.1.3). For every matching ODD element, SCENARIUM proposes the interactions from Table 1, which the manufacturer confirms or rejects with a justification. Each interaction leads to behavioural competencies, each in the situation classes nominal, critical and failure. Every competency × situation class needs at least one scenario; SCENARIUM shows the gaps. From these, the Technical Service selects the confirmatory tests, at least one per test area (a)–(h) under § 8.3.3.
How do I switch between the regulations in the demo?
At the top of every demo page, below the step bar, is the demo notice with the switcher “Regulation”: UN-R 171 · DCAS, (EU) 2022/1426 · ADS or UN-R 185 · ADS. After switching, SCENARIUM loads the scenarios, test specifications, test results and measurement files of the selected regulation; the choice is remembered for all three steps.
What does scenario-based approval testing mean?
Instead of individual fixed tests, a logical scenario describes a traffic situation with its parameter space – for example a cutting-in vehicle with speeds, distances and time-to-collision as ranges. From this, concrete test specifications are derived, approved by the Technical Service, driven and evaluated against pass and fail criteria.
How does testing with SCENARIUM work?
In three steps: (1) select and parametrise a logical scenario, (2) have the test specification reviewed and approved by the Technical Service, (3) for each test specification, upload the measurement files of the runs (CSV from the template) and evaluate them automatically. The result is the test report according to Annex 4 with requirement coverage and individual results – ready to print as PDF.
Is there an interface to simulation?
Yes. As a simulation interface, SCENARIUM exports every test specification as ASAM OpenSCENARIO with an OpenDRIVE road. The same scenarios that are parametrised for the test track then run in simulation environments (SiL, HiL) as well, e.g. for virtual testing. The export is locked in the public demo.
Do I need to install anything or create an account?
No. SCENARIUM is a pure web app and runs in Chrome, Edge and Firefox, even offline. In the demo, everything you save stays in your browser. You work with your own data via folder access (Chrome, Edge) or the included local server – the data does not leave your computer.
Is the data in the demo real?
No. The vehicles, measured values and approvals in the demo are fictitious and only for trying it out. The logical scenarios reflect the test procedures of UN-R 171 (46) and the minimum tests of (EU) 2022/1426 (33); those of UN-R 185 (32) are derived from a fictitious ODD declaration; the applicable regulation text is always authoritative.
Which regulations are coming next?
After UN-R 171, (EU) 2022/1426 and UN-R 185, UN-R 157 (ALKS, Automated Lane Keeping System) is planned. The workflow stays the same; it adds its scenarios, requirements and a report template.
Contact
Connect on LinkedIn
Questions, ideas or interest in SCENARIUM?
Felix Rother – I welcome feedback on the demo and exchanges about approval tests in the DCAS and AD field.
Email: felix@scenarium.io