The 43rd session of the IWG on PTI convened on 8 May 2026 in Brussels. The group reaffirmed the need to strengthen integration between type approval and in-use inspection per WP.29 Whole-Life Compliance framework (WP.29/2023/89). At least 20 UN Regulations contain incomplete, non-harmonised PTI provisions. The IWG agreed to add “Review of PTI provisions in UN Regulations (1958 Agreement)” to its Action Plan and submit a proposal to WP.29 requesting endorsement. Work on diagnostic tools in PTI and automated vehicles inspection continues. The group reviewed recent amendments to UN Regulations Nos. 13 and 13-H for new braking technologies and identified challenges regarding LED replacement light source inspection.

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:

• Throughout these regulations, amend references to the Consolidated Resolution on the Construction of Vehicles (R.E.3) as document ECE/TRANS/WP.29/78/Rev.8,
• insert new definitions for Software Identification Numbers referring to R.E.3 Annex 7 para. 2,
• amend requirements for software identification to require manufacturers provide necessary information allowing Technical Services to uniquely identify hardware and software configurations,
• insert new provisions allowing vehicle manufacturers to apply for new approvals differentiating software versions for vehicles already registered in the market from new vehicles,
• amend production discontinuation provisions to clarify production is not considered definitively discontinued if manufacturer intends to obtain subsequent extensions of approval for software updates of registered vehicles,
• insert new items in annexes regarding additional information on software identification and software updates including R_xSWIN identification, whether held on vehicle, how to read if not held on vehicle, and relevant parameters for vehicle identification.

Proposed changes to align RxSWIN provisions with the RxSWIN template adopted through WP.29-197-06, remove the proposed requirement to comply with UN R156/01 or later from R157 and R171, remove amendments to UN R155 as decided by the IWG CS/OTA, apply the RxSWIN amendments also to earlier series of amendments in R13, R13-H, R79, R131, R152, R157, and R171, update references to the latest version of R.E.3, ECE/TRANS/WP.29/78/Rev.8, in earlier series, and correct paragraph references and improve structure in R89, R139, R140, R155, R156, and R171.

Proposal to insert provisions on Software Identification Numbers and software updates across UN R13, R13-H, R79, R89, R130, R131, R152, R155, R156, R157, R171, R175, and R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7 paragraph 2, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance with test reports, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered vehicles from new vehicles where type approval regulations are updated or hardware changes occur in series production with test duplication avoided where possible, clarifying that production is not considered definitively discontinued if manufacturers obtain subsequent extensions for software updates of registered vehicles, renumbering and inserting new items in approval communication annexes for R13SWIN, R13-HSWIN, R79SWIN, R89SWIN, R130SWIN, R131SWIN, R152SWIN, R155SWIN, R157SWIN, R171SWIN, R175SWIN, and R178SWIN information including whether held on vehicle and relevant parameter identification lists, and amending R157 and R171 to align software update requirements with R156 technical specifications and transitional provisions.

Proposal to amend Annex 8, para. 3.4.1. to require that the strategy chosen shall not prejudice safe operation of the system due to failures with other systems involved in achieving the function of the system, and amend Annex 8, para. 3.4.4. to require that analysis of system behaviour on fault occurrence includes faults with other systems involved in achieving the function of the system, and to correct ‘safetys’ to ‘safety’. The proposal addresses a collision where tyre failure resulted in unsafe ABS activation. Although the 02 series clarified ABS as part of electronic control systems assessment, it does not explicitly state what is covered, potentially missing relevant faults or failures influencing system function. The additions ensure all relevant faults or failures are accounted for in manufacturers’ safety concept and analysis.

Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information.

Proposal to insert provisions on software identification and software updates into UN R13, UN R13-H, UN R79, UN R89, UN R130, UN R131, UN R152, UN R155, UN R156, UN R157, UN R171, UN R175, and UN R178 by adding definitions referencing Consolidated Resolution R.E.3 Annex 7, requiring manufacturers to provide Technical Services with information on hardware and software influencing performance, permitting vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles, clarifying that production discontinuation does not apply when manufacturers seek approval extensions for software updates of registered vehicles, and amending communication forms to include software identification numbers and related information.

Proposal to amend Annex 8, para. 3.4.1. to require the vehicle manufacturer to supplement its statement with an explanation of how the chosen strategy ensures system objectives do not prejudice safe operation of systems referred to and a description of the validation plan, and to require the designated technical service to perform an assessment of the manufacturer’s explanation and validation plan suitability and may perform or require tests as specified in para. 4., and amend Annex 8, para. 3.4.4. to require documentation supported by analysis showing system behaviour on fault occurrence including faults with other systems involved in achieving system function, to establish and maintain analytical approaches open for inspection by the designated technical service at type approval, and to require the designated technical service to perform assessment including inspection of safety approach at concept and system levels and validation plans and results.

Single N₁ and N₂ vehicles with fluted brake drums for parking brakes cannot be inspected on roller and plate test benches or in test drives. Electric parking brake systems cannot be tested on roller and plate test benches or test drives, and wheels cannot be turned on lifts to inspect for damages or bearing wear. Some vehicles have hydraulic braking systems with brake fluid reservoirs not accessible without dismantling or special tools, requiring removal of covers, fasteners, and screws to access brake fluid for inspection. PTI inspection provisions require updating to address these vehicle design variations.

UN R13 and UN R78 establish different brake system requirements for 4-wheel vehicles. R13H requires split service brake systems with front/rear proportioning; R78 permits split service brake systems, combined brake systems, or two separate service brake systems without proportioning requirements. Type-O dry braking tests differ: R13H requires engine disconnected at 100 km/h with stopping distance 0.1v + 0.0060 v² and MFDD 6.43 m/s²; R78 specifies multiple tests at 40, 60, and 100 km/h with varying requirements. Type-I brake fade tests use different snub protocols and performance thresholds. Secondary braking failure criteria differ at specified speeds. R78 requires wet brake testing, a 30 km/h dynamic park brake test with 18% gradient and 5 minutes hold time; R13H specifies static gradient tests. R78 includes detailed ABS, functional safety, and regenerative braking requirements; R13H does not.

The Informal Working Group on EV/HFCV Retrofit Systems held its seventh meeting on 5th March 2026. The group adopted the provisional agenda, approved minutes of the previous meeting, and acknowledged ongoing activities under GRPE, GRSP and GRVA. Electrical safety review will continue once clarification regarding UN R100 is available. Cybersecurity discussions covered very old vehicles, older vehicles without cybersecurity provisions, and modern vehicles compliant with UN R155. Braking aspects and the structure of the draft UN Regulation were discussed, including vehicle versus system approval approaches and minimum and maximum vehicle age within the regulation’s scope.

Proposal to amend UN R13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178 by introducing provisions on software identification and software updates. Amendments add new paragraphs referring to Software Identification Number definitions in Consolidated Resolution R.E.3, require manufacturers to provide Technical Services with information on hardware and software influencing performance, permit vehicle manufacturers to apply for new approvals differentiating software versions for registered versus new vehicles while avoiding test duplication, and modify production discontinuation provisions to exclude cases where manufacturers seek approval extensions for software updates of registered vehicles.

Proposal to amend the regulation to enable application to ADS vehicles, including: Proposal to amend braking equipment functions for Automated Driving Systems:

• clarify braking equipment functions for Automated Driving Systems,
• define transmission control and energy transmission,
• specify secondary and parking braking system requirements for ADS-equipped vehicles,
• permit disabling braking controls during ADS operation,
• establish testing procedures for vehicles of categories X and Y without manual driving controls,
• allow alternative static condition brake actuation testing.