| UN R155: Proposal to amend the Interpretation Document |
| Reference Number: TFCS-39-02 |
|
Proposal to amend Paragraph B to insert new requirement 5.1.3 establishing that the Approval Authority or Technical Service shall refuse to grant type approval regarding cyber security where the vehicle manufacturer has not fulfilled requirements in paragraph 7.3., notably that the Certificate of Compliance for the Cyber Security Management System has not been issued by the same Approval Authority granting the type approval, add explanatory text clarifying that this ensures Article 2(2) of the 1958 Agreement compliance while permitting cooperation between Approval Authorities and acceptance of prior documentation, amend Paragraph K to remove existing guidance text in paragraphs 6.1 and 7.1 regarding Certificate of Compliance issuance and inter-Authority arrangements, and insert statement that no guidance is included regarding paragraph 6 requirements. These changes support proposal GRVA/2026/30. |
| Submitted by: UK |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 28 Aug 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R155: Concept for approval of components |
| Reference Number: TFCS-39-04 |
|
This document presents a concept for approvals of electrical/electronic sub-assemblies (ESAs) as components according to UN R155, and the installation of such approved components on vehicles already holding UN R155 approval. The proposal removes the possibility of separate technical unit (STU) approvals as a first step, limiting coverage to components connected only to power and/or reading data through approved existing interfaces. The document restructures UN R155 into three parts: Part I covers vehicle type approvals; Part II covers ESA component approvals with cybersecurity requirements; Part III covers vehicle type approvals regarding installation of approved ESAs. Requirements include cybersecurity management systems, risk assessments, threat mitigations, and reporting provisions for development, production, and post-production phases. |
| Submitted by: UK |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 28 Aug 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
| UN R13 / UN R13-H / UN R79 / UN R89 / UN R131 / UN R130 / UN R178 / UN R155 / UN R156 / UN R152 / UN R157 / UN R171 / UN R175: Proposal to amend GRVA/2026/27 |
| Reference Number: TFCS-39-06 |
|
Proposal to amend GRVA/2026/27, which proposes amendments to UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R139, UN R140, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178:
|
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 02 Sep 26 |
| Relevant to: UN Regulation No. 13 | Heavy-Duty Vehicle Braking, UN Regulation No. 13-H | Light-Duty Vehicle Braking, UN Regulation No. 79 | Steering Equipment, UN Regulation No. 89 | Speed Limitation Devices, United Nations Agreement | RE3 Construction of Vehicles, UN Regulation No. 131 | Advanced Emergency Braking Systems, UN Regulation No. 130 | Lane Departure Warning Systems, UN Regulation No. 140 | Electronic Stability Control Systems, UN Regulation No. 178 | Emergency Lane-Keeping Systems, UN Regulation No. 155 | Cyber Security and Cyber Security Management, UN Regulation No. 156 | Software Update Processes and Management Systems, UN Regulation No. 152 | Automatic Emergency Braking for M1/N1 vehicles, UN Regulation No. 157 | Automated Lane-Keeping Systems (ALKS), UN Regulation No. 171 | Driver-Control Assistance Systems (DCAS), and UN Regulation No. 175 | Acceleration Control for Pedal Error |
| Click here to view the full document file |
| Position on GRVA/2026/30 |
| Reference Number: TFCS-39-07 |
|
OICA, CLEPA, and CLCCR oppose the requirement in GRVA/2026/30 for a single Approval Authority to issue the Certificate of Compliance for CSMS/SUMS and vehicle type approval. They contend the approach would create multiple approvals of the same Management System, imposing administrative burden and creating unresolved legal consequences if a CoC is challenged. The organizations propose adding a new paragraph 5.1.5. instead of paragraph 5.1.3. e) to permit mutual agreement between Approval Authorities, allowing usage of a CoC issued by another Approval Authority, with such agreement documented in type approval documentation. |
| Submitted by: OICA, CLCCR, and CLEPA |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 02 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management and UN Regulation No. 156 | Software Update Processes and Management Systems |
| Click here to view the full document file |
| UN R155: Comments on GRVA/2026/28 concerning multistage vehicles |
| Reference Number: TFCS-39-08/Rev.1 |
|
Proposal to insert new paras. 27 and 28 in Part C Guidance for the application of UN Regulation No. 155 to transformed vehicles. Para. 27 states the requirement that the Certificate of Compliance and type approval are issued by the same Approval Authority applies only within the scope of the type approval granted to the manufacturer concerned. Para. 28 states where a vehicle manufacturer modifies a vehicle with existing type approval and applies for new type approval covering the modification, they need not use the same type approval authority as was used by the original vehicle manufacturer. |
| Submitted by: OICA, CLCCR, and CLEPA |
| Meeting Sessions: 39th TFCS session (3 Sep) |
| Document date: 03 Sep 26 |
| Relevant to: UN Regulation No. 155 | Cyber Security and Cyber Security Management |
| Click here to view the full document file |
No matching documents.