Report of Japanese Test Phase Software Update Japan

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

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. 2

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. 3

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. 4

Software Update (Continued) “Demonstration” • The demonstration specified in paragraph 7. 1. 3 & 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. 5

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

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. Diagram of management by linking the vehicle, approval information, EUC and RXSWIN Approval info VIN Basic vehicle spec. Option list RXSWIN ECU-A 1 software version ECU-B 1 software version 7

Relation Between RXSWIN/Sys. ID 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. · Sys. IDs 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 R 13 H Brake Subject to approval R 39 Speedometer R 79 Steering equipment Not subject to approval Luxury equipment Ver 5 Ver 7 Ver 3 Ver 7 ABS IVI MET EPS Sys. ID RXSWIN (Approved types only) Sys. ID BRSys 04 RXSWIN WMI-VDSR 13 H-Sys 04 Sys. ID SPMTSys 06 RXSWIN WMI-VDS-R 39 -Sys 06 Sys. ID STSys 02 RXSWIN WMI-VDS-R 79 -Sys 02 Sys. ID MMSys 09 8

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. ECU Software ID No need to newly obtain approval for the other relevant type (R 13 H) R 13 H Brake Subject to approval Need to newly obtain approval for the type (R 79) Not subject to approval R 39 Speedometer R 79 Steering equipment Luxury equipment Ver 8 Ver 5 Ver 7 Ver 3 Ver 7 ABS IVI MET EPS Confirm that other functions within the same ECU will not be affected. Sys. ID Confirm that other related systems (R 13 H) will not be affected. It does not increment Sys. IDs of those systems that will not be affected. RXSWIN (Approved types only) Sys. ID BRSys 04 RXSWIN WMI-VDSR 13 H-Sys 04 Sys. ID SPMTSys 06 RXSWIN WMI-VDS-R 39 -Sys 06 Sys. ID STSys 03 RXSWIN WMI-VDS-R 79 -Sys 03 Sys. ID MMSys 09 Steering-related functional change; the type (R 79) will be affected 9

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 Sys. ID * It is not intended to require the Part No. management at the function level (installation). RXSWIN ECU Hardware Bracket Sys. ID Software Information Identifier (ECU Software ID) Ver 8 Ver 7 Change made Software Information Identifier (ECU Software ID) Change made … ECU Function A Function B Microcontroller Software User data Calibration Function data B Application data Function A R 79 BSW/OS Function … Function C R 13 H Function 0 Boot 10

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 Sys. ID will be updated and reported to the Certification Department. Authority (Japan) OEM Certification Dept. RXSWIN WMI-VDSR 79 -Sys 02 Apply RXSWIN WMI-VDSR 79 -Sys 02 Design Dept. (System) Sys. ID STSys 02 ECU Dept. 1 ECU SW ID IVI-07 No change RXSWIN WMI-VDSR 79 -Sys 03 The authority receives from the OEM an application for modifying the existing type approval and reapproves the type. Apply RXSWIN WMI-VDSR 79 -Sys 03 Certification Dept. newly assigns an RXSWIN in response to the request from the Design Dept. and notifies it to the authority. RXSWIN is assumed to be numbered using the process/system within the Certification Dept. Sys. ID STSys 03 As a result of the ECU Dept. 2 process to determine whether any approved type will be ECU SW ID EPS-07 affected, the Design Dept. determines that there is an affected ECU SW ID EPS-08 type and thus newly assigns a System (1) A functional change that Configuration will affect an approved Management No. type is made (Sys. ID). Sys. ID is assumed to be numbered using the management process/system within the Design Dept. 11

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 12