1. Vehicle Approval case study A) Same type approval R79 for new vehicles and already registered vehicles
New vehicle with HW and SW updates
All Type date for 02 series
R79-01 Appr
RXSWIN 1
R79-01 Appr
HW change
SW change
RXSWIN 2
R79-02 Appr
HW change
SW change
RXSWIN 4
R79-01 Appr
SW change
RXSWIN 3
R79-?? Appr
SW change
RXSWIN 5
Registered vehicle with SW updates
For already registered vehicles:
SW updates are based on original HW
RXSWIN3 & RXSWIN5 are not necessarily related to RXSWIN2 & RXSWIN4
Extension of approvals stay within original regulation series
In some cases, it is not possible to have the same approval for new vehicles and already registered vehicles (see example above with Approval x)

2. Vehicle Approval case study B) Different type approvals R79 for new vehicles and registered vehicles
With different type approvals for new vehicles and registered vehicles, all issues addressed in the previous slide can be covered.
New vehicle with HW and SW updates
Production stop
All Type date for 02 series
R79-01 Appr
RXSWIN 01
R79-01 Appr
HW change
SW change
RXSWIN 02
R79-02 Appr
SW change
RXSWIN 03
Notify discontinuation
Appr. 322
R79-01 Appr
SW change
RXSWIN 91
R79-01 Appr
SW change
RXSWIN 92
R79-01 Appr
SW change
RXSWIN 93
R79-01 Appr
SW change
RXSWIN 94
R79-01 Appr
SW change
RXSWIN 95
Registered vehicle with SW updates

3. Text proposal as an example for ECE R79
Paragraph 1.5 of Annex B
The vehicle manufacturer may obtain a new vehicle approval for the purpose of differentiating software versions intended to be used on vehicles already registered in the market from the software versions that are used on new vehicles. In agreement with the testing agency duplication of tests shall be avoided where possible.

4. Annex

5. Vehicle Approval case study
The SW update requirement of a given Regulation should allow to obtain separate approvals for
SW of new vehicles (in production)
SW update of registered vehicles
Background:
Approvals or extensions of approvals for registered vehicles are a new concept for UN ECE 1958 agreement. Such a new concept should allow a different approach:
SW updates may be specifique for registered vehicles
SW updates for registered vehicles may be managed separately from new vehicle specifications by an OEM
Not every CP is requesting approvals of SW updates:
System approvals (e.g. R79) are used for several countries with same specifications Separating the registered vehicle specification avoids unnecessary updates of National Vehicle Type approval for these CP (e.g. If new vehicle SW and registered vehicle SW of R79 is within the same approval, we have to update the National Type Approval in every Country that uses this R79 approval)
depending on OEM’s internal SW version management system, the management of SW versions is easier
-> Both ways should be allowed depending on OEM’s choice

6. Proposals:
Most important is that Contracting Parties that grant approvals of SW updates don’t object to obtain a separate approval (These CP are not necessarily represented in this TF CS/OTA):
In Annex B (Annex integrating RXSWIN into each UN ECE Reg.)
In the recommendation

7. Vehicle Approval case study (for NTA)
Country A
NTA
Country B
R79 (incl.new vehicle RXSWIN) +
R79 (incl. registered vehicle RXSWIN)
R79 (incl.new vehicle RXSWIN)
R13H (incl.new vehicle RXSWIN) +
R13H (incl. registered vehicle RXSWIN)
R13H (incl.new vehicle RXSWIN)
RXX
RXX
Country A is UNECE Contracting Party with obligation of
UNECE registered vehicle SW update approval
Country B has no obligation of
UNECE registered vehicle SW update approval

8. Vehicle Approval case study (vehicle life cycle)
Model cycle for 1 regulation
New Vehicle type
OTA 1 (registered vehicle only)
Project 1 (New vehicle)
OTA 2 (registered vehicle only
Project 2 (New vehicle)
OTA 3 (registered vehicle only
Project 3 (New vehicle)
Vehicle Specification
Actuator A
No change B
Sensor
Soft A'
A'', B' C
A''', B'', C' D
Today
New vehicle /
Future
RXX SW approvals
R79 approval new vehicle
R79 approval registered vehicle
A, B
A', A'', B'
A', A'', A''', B‘, B'', C'