1. Report of Japanese Test Phase <Software Update>
Test Phase Coordination Meeting 2
17-18, July, 2019
Leiden, Netherlands

2. Outline
4 Manufacturers, 1 TS, 1 AA and the Government were actively involved in the Japanese Test Phase.
Evidencing documents which have been developed with a format in the same manner with existing regulations were reviewed.
Summary of results in the first round of the test phase will be shared in the later pages.

3. Software Update
Evidences which are described in the current draft of “Interpretation Document” are sufficient in general in comparison with the results of Japanese test phase.

4. Software Update (Continued)
“Interpretation Document”
“ID” will provide what kind of evidences are needed for the certification by TS/AA.
“ID” will not define the criteria on quality of evidencing.
“ID” will not define boundary conditions on OEM’s process.

5. Software Update (Continued)
“Demonstration”
The demonstration specified in paragraph & 7.1.4, which will be conducted for the certification of OEM’s processes shall include audits on the sites, such as vehicle design department. Such auditing includes e.g. interviews.
The demonstration for type approval specified in paragraph 7.2 shall be done from the viewpoint of investigation whether vehicle was actually designed in accordance with content of application form. This demonstration includes investigation of actual vehicle.

6. Additional Input: RxSWIN
In order to understand how RxSWIN is used for certifications, Japan is working to integrate the idea into the existing regulation(R79) as a trial bases.
Japanese case study which involves multiple ECUs and functions will be described in the following page.

7. Software Update Operation and Management Requirements
(1) Instead of identifying particular ECU component software, a software identification RXSWIN is set to identify the ECU software program relevant to each type approval (RXSWIN: Software identification No. for Regulation No. x).
(2) RXSWIN consists of a maximum of 50 alphabetic/numeric characters. (Each manufacturer can define its own numbering rules.)
(3) RXSWIN must be capable of being read out via an electronic interface or the standard interface (OBD port).
(4) It must have a mechanism whereby information on specific software versions of relevant components as well as information to link them to RXSWIN is recorded.
(5) Vehicle information and RXSWIN-linked information must be informed to the authority.
(6) Data used to determine whether or not the software update will affect the approval must be maintained.
(7) Management is also required after vehicle registration.
VIN
Basic vehicle spec.
RXSWIN
ECU-A1 software version
ECU-B1 software version
Diagram of management by linking the vehicle, approval information, EUC and RXSWIN
Option list
Approval info

8. Relation Between RXSWIN/SysID and ECU
· RXSWIN is an identifier that is assigned for each vehicle type on one UNR and intended to identify software (function) on an ECU which is a component of a type-approved system.
· SysIDs are unique management identifiers managed by the design side and are uniquely assigned even to those OEM systems that are not subject to type approval.
ECU Software ID
Ver5
Ver7
Ver3
Ver7
ABS
IVI
MET
EPS
RXSWIN
(Approved types only)
SysID
R13H
Brake
SysID
BR-
Sys04
RXSWIN
WMI-VDS-R13H-Sys04
Subject to
approval
R39
Speedometer
SysID
SPMT-
Sys06
RXSWIN
WMI-VDS-R39-Sys06
R79
Steering equipment
SysID
ST-
Sys02
RXSWIN
WMI-VDS-R79-Sys02
Not subject to
approval
Luxury equipment
SysID
MM-
Sys09

9. Determination of Whether Any Approved Type Will Be Affected by the ECU Software Update
If changes are made to software on an ECU, the OEM needs to be able to identify types that are possibly related to that ECU. In addition, the OEM needs to be able to determine, based on the software configuration on that ECU as well as the changes made, whether any of such types will be affected, whether any other types will be affected, and whether it will be necessary to newly obtain approval.
Confirm that other related systems (R13H) will not be affected. It does not increment SysIDs of those systems that will not be affected.
Confirm that other functions within the same ECU will not be affected.
Ver8
ECU Software ID
Ver5
Ver7
Ver3
Ver7
Ver7
No need to newly obtain approval for the other relevant type (R13H)
ABS
IVI
MET
EPS
RXSWIN
(Approved types only)
SysID
R13H
Brake
SysID
BR-
Sys04
RXSWIN
WMI-VDS-R13H-Sys04
Subject to
approval
R39
Speedometer
SysID
SPMT-
Sys06
RXSWIN
WMI-VDS-R39-Sys06
Need to newly obtain approval for the type (R79)
R79
Steering equipment
SysID
ST-
Sys03
RXSWIN
WMI-VDS-R79-Sys03
Not subject to
approval
Luxury equipment
SysID
MM-
Sys09
Steering-related functional change; the type (R79) will be affected

10. ECU Software ID (Example)
· Need to identify all the relations to the level of functions within an ECU by linking them to ECU Software IDs, which are linked to RXSWIN through SysID
* It is not intended to require the Part No. management at the function level (installation).
Function 0
Function B
Function C
R13H …
ECU
Software A
R79
User data
Application data
Calibration data
Boot
Hardware
BSW/OS
Bracket
Microcontroller
Software Information Identifier
(ECU Software ID)
Function A
SysID
RXSWIN
Change made
Ver7
Ver8
Function A
Function B

11. ECU Software Update and RXSWIN Update Processes
The Design Department has a process to determine whether any approved type will be affected.
As a result of such process, if it is determined that there is an affected type, the applicable SysID will be updated and reported to the Certification Department.
OEM
Authority (Japan)
Apply
SysID
ST-
Sys02
RXSWIN
WMI-VDS-R79-Sys02
Certification Dept.
ECU SW ID
IVI-07
EPS-07
Sys03
WMI-VDS-R79-Sys03
EPS-08
ECU Dept. 2
(1) A functional change that will affect an approved type is made
No change
Certification Dept. newly assigns an RXSWIN in response to the request from the Design Dept. and notifies it to the authority.
ECU Dept. 1
The authority receives from the OEM an application for modifying the existing type approval and re-approves the type.
As a result of the process to determine whether any approved type will be affected, the Design Dept. determines that there is an affected type and thus newly assigns a System Configuration Management No. (SysID).
Design Dept.
(System)
RXSWIN is assumed to be numbered using the process/system within the Certification Dept.
SysID is assumed to be numbered using the management process/system within the Design Dept.

12. Modification of Annex B
・x.y.2.2. The vehicle manufacturer shall provide the following information in the communication form of this Regulation:
the RXSWIN
the regulation binding to the RXSWIN
the information to bind the RXSWIN and relevant software packages which form the type approved according to this regulation
how to read the RXSWIN