97. The representative of the European Union, on behalf of the Chair of the IWG on DETA, presented informal document WP.29-176-23. He mentioned that the expert from CITA offered to fund the development of the Declaration of Conformance (DoC) functionality in DETA as it may offer a platform for exchanging information about permissible vehicle software (including version numbers and integrity validation data) for various use cases and stakeholders including PTI and also for providing type approval information for the benefit of the PTI process as stated in WP.29-176-18.

98. The representative of OICA stated the highly confidential nature of documents stored in DETA and highlighted the need to create access rights that would respect their intellectual property and confidentiality. He proposed that WP.29 clarify who would be able to access the documents in DETA. The representative of Germany offered that IWG on DETA explore the possibility to organize a WebEx meeting to work on this issue and proposed that only type approval authorities should have access to the DETA, in a first stage.

99. The representative of France sought clarification whether the starting date for the use of DETA in its productive phase is meant to have an optional or mandatory nature.

100. The representative of Tunisia highlighted the importance to have secured and reliable access to trustworthy type approval documentation in the shortest time frame possible to allow the verification of authenticity of type approval documentation.

101. The representative of Spain requested further information on the status of the availability of a manual detailing the protocol to access and use DETA.

102. The representative from EuroMed mentioned that access to DETA was critical for all EuroMed countries and requested information on the ways to access to DETA.

103. The representative of Global NCAP explained, as an example, that South American countries envisaged applying United Nations regulations as an interim measure until they potentially accede to the 1958, 1997 and 1998 Agreements. He stated that these countries, not yet contracting party to the agreements would need access to DETA and that it might accelerate the adhesion process.

104. The secretariat invited the heads of delegations to provide the secretariat with the Single Point Of Contact (SPOC) on the designation of type approval authorities and technical services that would receive credentials for accessing the application for introducing new or changes to existing information.

105. The representative from CITA introduced a proposal for a next evolution of DETA by presenting WP.29-176-18 on individual vehicle specific information on permissible vehicle software. This would support the process of Periodic Technical Inspection (PTI) of modern vehicles, which is an important factor for road safety.

106. CITA confirmed its financial contribution for the development of the Document of Conformity (DoC) module of DETA without any preconditions.

107. The representative of the United Kingdom expressed, in principal, his agreement to the availability of software information (RxSWIN) for the purpose of PTI, nevertheless, questions on confidentiality and data security need to be solved first.

108. The representative of OICA recalled ongoing work in the Task Force on Cyber security, where software information is handled as software identifier RxSWIN, and introduced as part of the type approval certificate.

108 bis. The representative from the Netherlands supported this. The WP.29 Chair expressed the need for coordination between the Task Force on Cyber Security and the IWG on DETA on this issue.

109. Addressed by the WP.29 Chair on financial contributions to the further development of DATA for the module of the Unique Identifier (UI):

1. CLEPA stated that a budget had been reserved and awaited the outcome of Executive Committee (EXCOM) discussions on the ECE budget proposal, an anticipated funding was envisaged for 2019;
2. ETRTO confirmed its commitment to contribute to funding UI; and
3. OICA reiterated their willingness to contribute to developing UI, if CLEPA, ETRTO and other stakeholders would do so.

Proposal to use the DETA system to store up-to-date VIN-related information about permissible vehicle software including version numbers and integrity validation data and to provide this data to all relevant stakeholders including Approval Authorities, Technical Services and the Periodical Technical Inspection (PTI) in order to support use cases like certification, including the validation of the conformity of production, and market surveillance, including recalls and PTI.

97. The representative of the European Union, on behalf of the Chair of the IWG on DETA, presented informal document WP.29-176-23. He mentioned that the expert from CITA offered to fund the development of the Declaration of Conformance (DoC) functionality in DETA as it may offer a platform for exchanging information about permissible vehicle software (including version numbers and integrity validation data) for various use cases and stakeholders including PTI and also for providing type approval information for the benefit of the PTI process as stated in WP.29-176-18.

98. The representative of OICA stated the highly confidential nature of documents stored in DETA and highlighted the need to create access rights that would respect their intellectual property and confidentiality. He proposed that WP.29 clarify who would be able to access the documents in DETA. The representative of Germany offered that IWG on DETA explore the possibility to organize a WebEx meeting to work on this issue and proposed that only type approval authorities should have access to the DETA, in a first stage.

99. The representative of France sought clarification whether the starting date for the use of DETA in its productive phase is meant to have an optional or mandatory nature.

100. The representative of Tunisia highlighted the importance to have secured and reliable access to trustworthy type approval documentation in the shortest time frame possible to allow the verification of authenticity of type approval documentation.

101. The representative of Spain requested further information on the status of the availability of a manual detailing the protocol to access and use DETA.

102. The representative from EuroMed mentioned that access to DETA was critical for all EuroMed countries and requested information on the ways to access to DETA.

103. The representative of Global NCAP explained, as an example, that South American countries envisaged applying United Nations regulations as an interim measure until they potentially accede to the 1958, 1997 and 1998 Agreements. He stated that these countries, not yet contracting party to the agreements would need access to DETA and that it might accelerate the adhesion process.

104. The secretariat invited the heads of delegations to provide the secretariat with the Single Point Of Contact (SPOC) on the designation of type approval authorities and technical services that would receive credentials for accessing the application for introducing new or changes to existing information.

105. The representative from CITA introduced a proposal for a next evolution of DETA by presenting WP.29-176-18 on individual vehicle specific information on permissible vehicle software. This would support the process of Periodic Technical Inspection (PTI) of modern vehicles, which is an important factor for road safety.

106. CITA confirmed its financial contribution for the development of the Document of Conformity (DoC) module of DETA without any preconditions.

107. The representative of the United Kingdom expressed, in principal, his agreement to the availability of software information (RxSWIN) for the purpose of PTI, nevertheless, questions on confidentiality and data security need to be solved first.

108. The representative of OICA recalled ongoing work in the Task Force on Cyber security, where software information is handled as software identifier RxSWIN, and introduced as part of the type approval certificate.

108 bis. The representative from the Netherlands supported this. The WP.29 Chair expressed the need for coordination between the Task Force on Cyber Security and the IWG on DETA on this issue.

109. Addressed by the WP.29 Chair on financial contributions to the further development of DATA for the module of the Unique Identifier (UI):

1. CLEPA stated that a budget had been reserved and awaited the outcome of Executive Committee (EXCOM) discussions on the ECE budget proposal, an anticipated funding was envisaged for 2019;
2. ETRTO confirmed its commitment to contribute to funding UI; and
3. OICA reiterated their willingness to contribute to developing UI, if CLEPA, ETRTO and other stakeholders would do so.

Updated proposal for guidelines on the application of the UI.

Spreadsheet of DETA documentation requirements to aid in making decisions on whether to combine or split documents into separate parts.

72. The representative of the European Union, on behalf of the Chair of the IWG on DETA, presented the informal document WP.29-175-16 detailing the state of play of the development of DETA. She requested an update by the secretariat on actions taken for the financing of DETA under the ECE regular budget. She added that the IWG on DETA was initiating a pilot project in August 2018. So far, six institutions have volunteered to participate in the pilot project, and the IWG was willing to welcome more volunteers to test the functioning of DETA.

73. The WP.29 Secretary referred to the new United Nations budget process (informal document WP.29-175-26). The hosting and maintenance costs of DETA had been added under Part III of the draft ECE budget proposal for 2020, and would follow the internal procedure within ECE and at United Nations Headquarters leading to a general assembly resolution.

74. WP.29 welcomed that OICA and CITA, respectively, would contribute to the development of the Unique Identifier and Declaration of Conformance modules and would act as contractor vis-à-vis the software provider.

75. The representative of ETRTO stated that he would also contribute on the condition that DETA would be migrated to the United Nations servers by 2020.

76. The representative of CLEPA clarified that he would also contribute once DETA would be on United Nations servers.

77. The representative of the European Union requested a better coordination of funders to make DETA a reality in the short term. In this context, the secretariat reiterated that contribution from contracting parties would also be welcomed.

78. The representative of the Russian Federation expressed his interest of being involved in the testing of the DETA system. The importance of the activity in testing the DETA system was also conditioned by the present work for the soon planned start of the electronic Whole Vehicle Type Approval (WVTA) in the Russian Federation.

Draft Guidelines for application of the DETA Unique Identifier (UI).

Inputs for the type approval data exchange system.

85. The Chair of the IWG on DETA presented the existing numerous benefits of DETA as well as those of the future further development of this data exchange system, with possible linkages to other parties engaged in the vehicle regulatory process, such as vehicle certification agencies, vehicle registration authorities, vehicle testing centres, enforcement authorities or customs and thus providing a seamless flow of vehicle related technical information among themselves (WP.29-174-19).

Request of the DETA informal working group for WP.29 decisions during its March 2018 session on the program development, including initial deployment and rebranding to communicate that the system is not limited to the exchange of type approval information, but can be used for other vehicle-related information.

76. The Chair of the IWG on DETA reported on the last meeting of the IWG (WP.29‑174-05) highlighting the importance and necessity of having DETA operational and expressed his hopes to have a positive decision towards the financing of DETA under regular budget by EXCOM, as alternative financing solutions were proven not to be feasible in the short term. He also proposed, in this context, to rename DETA to better reflect its universal use.

77. WP.29 recognized the huge efforts made by Germany and thanked the German Government for its offer and decided to proceed towards scenario 3. WP.29 requested the UNECE secretariat to take the necessary steps to request financing for the hosting of DETA under regular budget. The World Forum invited the IWG on DETA to continue work on further software developments for the Unique Identifier (UI) and the Declaration of Conformance (DoC).

78. The representative of the United Kingdom reiterated his country’s willingness to contribute to the hosting of DETA based on an equal share with all other contracting parties.

79. The representative of OICA expressed the willingness of his organization to financially contribute to the development of the software for the UI with $50,000, as previously requested by WP.29, however the software for the DoC was not in the core interest of the automotive industry for the time being, but, with additional features such as information on software versions of electronically controlled vehicle systems, this position could change. He stressed that OICA would only invest in DETA once long-term assurance of its operation is granted, independent of the solution.

80. The representatives of CLEPA and ETRTO expressed a positive attitude towards financial contributions for the future development of DETA, once its operation at UNECE was secured.

81. The representative of IMMA stated that, considering current situation and government program status, IMMA is neutral towards DETA and hence currently has no interest to participate in the sponsoring of the Unique Identifier.

82. The representative of Germany stressed the fact that access to type approval data via DETA was important for the approval process, which is an authoritative task of the government. He therefore advised WP.29 to consider that the financing of DETA operation and further development should not be covered by the industry but preferably by the regular budget.

83. The representative of CITA stated the readiness of his organization to collaborate on, and to contribute to the further development of DETA, as access to information was crucial for performing Periodic Technical Inspections (PTI).

84. The representative of Australia expressed the willingness of his Government to contribute to the financing of DETA.

Draft request of the DETA informal working group for WP.29 decisions during its March 2018 session on the program development, including initial deployment and rebranding to communicate that the system is not limited to the exchange of type approval information, but can be used for other vehicle-related information.

This document is also available in a version with track changes.

Proposal from the Simplification of Lighting Regulations (SLR) informal group to limit new unique identifiers to cases where a product variant no longer meets a series of amendments. If all variants using the same original UI continue to meet all applicable series of amendments, the variants would all continue to share the same UI. A new UI would be needed only when one or more variants cannot comply with a new series of amendments.