TRIAS 99-R156-01

プログラム等改変業務管理システム試験（協定規則第 156 号（同規則の規則 7.1.に限る））
1. 総則
プログラム等改変業務管理システム試験の実施にあたっては、「自動車の特定改造等の許可に関する技術上の基準に関する細目等を定める告示」（令和 2 年国土交通省告示第 787 号）に定める「協定規則第 156 号の技術的な要件（同規則の規則 7.1.に限る。）」の規定及び本規定によるものとする。
2. 試験条件
書面及び現地審査により試験を行うことができる。
3. 試験記録及び成績
試験記録及び成績は、付表の様式に記入する。
3.1.

当該試験時において該当しない箇所には斜線を引くこと。

3.2.

記入欄は、順序配列を変えない範囲で伸縮することができ、必要に応じて追加してもよい。

3.3.

試験記録及び成績は、日本語又は英語のみの記載でもよい。

1/1

1/1

TRIAS 99-R156-01

付表Attached Table

プログラム等改変業務管理システム試験記録及び成績
SOFTWARE UPDATE MANAGEMENT SYSTEM TEST DATE RECORD FORM

（協定規則第156号（規則7.1.プログラム等改変業務管理システムに関する要件））
1958 Agreement of the United Nations Economic Commission for Europe Regulation No.156(Restricted to paragraphs 7.1. Requirements for the Software Update Management System)

試験期日

年月日

試験場所

試験担当者

Test Date

Y.

M.

D.

Test Site

Tested by〇改訂Series

改訂番号

補足改訂番号

Series No.

Supplement No.

○ 試験対象業務管理システム
Test Management System
社名
Manufacturer

業務管理システムの名称
Names of Management System○ 試験成績
Test Results※ 各項目について適合性を裏付ける資料のリストを添付のこと。書式は任意で構わない。
Attach a list of supporting material for each paragraph. The format does not matter.

要件
適合性

Requirements

段落

内容Paragraph7.1.1.
7.1.1.1.

Contents
Processes to be verified at initial assessment
A process whereby information relevant to this Regulation is documented
and securely held at the vehicle manufacturer and can be made available toan Approval Authority or its Technical Service upon request;

7.1.1.2.

7.1.1.3.

7.1.1.4.

7.1.1.5.
7.1.1.6
7.1.1.7.

Confomity

pass ／ failA process whereby information regarding all initial and updated software
versions, including integrity validation data, and relevant hardware
components of a type approved system can be uniquely identified;pass ／ failA process whereby, for a vehicle type that has an RXSWIN, information
regarding the RXSWIN of the vehicle type before and after an update can beaccessed and updated. This shall include the ability to update information
regarding the software versions and their integrity validation data of all
relevant software for each RXSWIN;

pass ／ fail／ N.A

A process whereby, for a vehicle type that has an RXSWIN, the vehicle
manufacturer can verify that the software version(s) present on a componentof a type approved system are consistent with those defined by the relevant
RXSWIN;pass ／ fail／ N.A

A process whereby any interdependencies of the updated system with othersystems can be identified;
A process whereby the vehicle manufacturer is able to identify target
vehicles for a software update;
A process to confirm the compatibility of a software update with the target
vehicle(s) configuration before it is issued. This shall include an assessmentof the last known software/hardware configuration of the target vehicle(s) forcompatibility with the update before it is issued;

pass ／ failpass ／ failpass ／ failTRIAS 99-R156-01
7.1.1.8.

A process to assess, identify and record whether a software update will affectany type approved systems. This shall consider whether the update will
impact or alter any of the parameters used to define the systems the update pass ／ fail
may affect or whether it may change any of the parameters used to typeapprove those system (as defined in the relevant legislation);

7.1.1.9.

A process to assess, identify and record whether a software update will add,alter or enable any functions that were not present, or enabled, when thevehicle was type approved or alter or disable any other parameters orfunctions that are defined within legislation. The assessment shall include
consideration of whether:

(a)
(b)
(c)

Entries in the information package will need to be modified;
Test results no longer cover the vehicle after modification;
Any modification to functions on the vehicle will affect the vehicle’s typeapproval.
A process to assess, identify and record if a software update will affect anyother system required for the safe and continued operation of the vehicle orif the update will add or alter functionality of the vehicle compared to when it
was registered;pass ／ failpass ／ failA process whereby the vehicle user is able to be informed about updates.
A process whereby the vehicle manufacturer shall be able to make theinformation according to paragraph 7.1.2.3. and 7.1.2.4. available toresponsible Authorities or the Technical Services. This may be for the
purpose of type approval, conformity of production, market surveillance,
recalls and Periodic Technical Inspection (PTI).

pass ／ fail7.1.1.10.

7.1.1.11.
7.1.1.12.

7.1.2.
7.1.2.1.

7.1.2.2.

7.1.2.3.

7.1.2.4.

7.1.2.5.
(a)
(b)
(c)
(d)
(e)
(f)
(g)
(h)
(i)
7.1.3.
7.1.3.1.
7.1.3.2.
7.1.3.3.

The vehicle manufacturer shall record, and store, the following informationfor each update applied to a given vehicle type:
Documentation describing the processes used by the vehicle manufacturer
for software updates and any relevant standards used to demonstrate theircompliance;pass ／ failpass ／ failpass ／ failpass ／ failpass ／ failDocumentation describing the configuration of any relevant type approved
systems before and after an update, this shall include unique identification
for the type approved system’s hardware and software (including softwareversions) and any relevant vehicle or system parameters;

pass ／ failFor every RXSWIN, there shall be an auditable register describing all thesoftware relevant to the RXSWIN of the vehicle type before and after anupdate. This shall include information of the software versions and theirintegrity validation data for all relevant software for each RXSWIN.

pass ／ fail／ N.A

Documentation listing target vehicles for the update and confirmation of thecompatibility of the last known configuration of those vehicles with theupdate.

pass ／ failDocumentation for all software updates for that vehicle type describing:
The purpose of the update;
What systems or functions of the vehicle the update may affect;
Which of these are type approved (if any);
If applicable, whether the software update affects the fulfilment of any of therelevant requirements of those type approved system;
Whether the software update affects any system type approval parameter;
Whether an approval for the update was sought from an approval body;
How the update may be executed and under what conditions;
Confirmation that the software update will be conducted safely and securely.
Confirmation that the software update has undergone and successfully
passed verification and validation procedures.
Security, the vehicle manufacturer shall demonstrate:
The process they will use to ensure that software updates will be protected
to reasonably prevent manipulation before the update process is initiated;
The update processes used are protected to reasonably prevent them being
compromised, including development of the update delivery system;
The processes used to verify and validate software functionality and code forthe software used in the vehicle are appropriate.

pass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ failpass ／ fail

TRIAS 99-R156-01
7.1.4.
7.1.4.1.

7.1.4.2.

備考
Remarks

Additional Requirements for Software Updates over the air
The vehicle manufacturer shall demonstrate the processes and procedures
they will use to assess that over the air updates will not impact safety, if
conducted during driving.
The vehicle manufacturer shall demonstrate the processes and procedures
they will use to ensure that, when an over the air update requires a specificskilled or complex action, for example recalibrate a sensor postprogramming, in order to complete the update process, the update can only
proceed when a person skilled to do that action is present or is in control ofthe process.

pass ／ fail／ N.A

pass ／ fail／ N.A