previous meeting next meeting
Geneva
(Latest 12 November 2015)
Agenda
Report
1. Adoption of the agenda

The revised draft agenda has been adopted.

DETA-22-01/Rev.1 | Updated provisional agenda for the 22nd DETA informal group session
2. Approval of the report of the previous session

The draft minutes have been adopted.

DETA-22-02 | Minutes of the 21st DETA informal group session
DETA-22-02/Att.1 | Participants list from the 21st DETA informal group session (annex to the session report)
3. Status report by T-Systems

The representative of the software house T-Systems explains the state of play. There is no issue with regard to the first step of exchanging approvals (pdf files) between Type Approval Authorities. With regard to the second step, where manufacturers are involved exchanging information on single vehicles (DoC), the representative requests, for technical reasons, to include the variant/version into the attributes. However, as the “type” refers to one conformance level only, it is concluded that the attribute “type” should be sufficient. The representative of T-Systems will confirm before next meeting if this is achievable.

Also it is decided that the grey coloured solutions in document DETA-21-04e need to be deleted as these solutions are not yet agreed with.
The group furthermore confirmed that it is the manufacturers responsibility to upload the correct VIN information to DETA.

DETA-21-04 | Database diagram for DETA under IWVTA
4. Developing the attributes for DETA

Mr. Secretary shows on screen the ‘try-out version’ of DETA. Then explains document DETA-22-04e rev. 01. This document shows the attributes currently in as well as proposals for attributes to be added. It is decided to modify the document to distinguish between approvals for systems/components and IWVTA’s and to make clear which attributes should be entered by the TAA, which attributes may be entered by the manufacturers or which are generated automatically by the DETA system.

The group is in favour of deleting some attributes currently in. Mr. Secretary will put these between square brackets and will check before next session the reason for these attributes within ETAES.

With regard to the attribute “Commercial Name(s)” it is recognized that the type approval may include more commercial names where the DoC applies to a single vehicle and can have only one commercial name. Because this situation results in the technical difficulty of generating the DoC with the corresponding commercial name, and because the commercial name is not necessary for the purpose of the DoC, SGR0-18 will be requested to remove the commercial name from the DoC.

Finally it has been decided that the user manual for DETA should give a precise description/definition of the various attributes.
Further details with regard to the outcome of this discussion will be included in DETA-22-04e rev. 02.

DETA-22-04/Rev.1 | Revised preliminary proposal for database attributes of the Data Exchange for Type Approvals
DETA-22-04/Rev.2 | Revised proposal for database attributes of the Data Exchange for Type Approvals
5. Creating an area in DETA for the purpose of information exchange (e.g. for withdrawal of type approvals)

Mr. Secretary explains this document. Due to the limited time, the participants are asked to study this document and to send comments by e-mail. A new document, including these comments, will then be further discussed during the next session.

DETA-22-05/Rev.1 | Revised preliminay proposal concerning information exchanges under the Data Exchange for Type Approvals
6. Stepwise approach of defining the various parties requiring access to DETA and their access rights

OICA explains this document which is based on OICA’s opinion and complemented with comments by KBA and Mr. Secretary. Due to the limited timing the participants are asked to study this document and to sent comments by e-mail. A new document, including these comments, will then be further discussed during the next session.

DETA-22-06/Rev.1 | Revised preliminary proposal for access rights under the Data Exchange for Type Approvals
7. Clarifying the process of applying for a UI in advance of type approval

Mr. Secretary explains the outcome of the discussion from the 21st (drafting group) meeting, being:

  • only the Type Approval Authority is responsible for extracting the UI out of DETA,
  • manufacturers must be able to receive a UI prior to type-approval,
  • for such case, a ‘document envelope’ is entered with a minimum number of attributes, including the type-
    approval number.

8. Any other business

a) Feedback from TCMV with regard to the financing of DETA.

Mr. Secretary explains the outcome of the Technical Committee Motor Vehicles 50th session. The European Commission will express during the WP.29 167th session the Member States opinion for financing DETA by additional UNECE regular budget.

b) Withdrawal of IWVTA type approvals due to R0 paragraph 7 (modification and extension of approval).

This issue is due to approvals required to be withdrawn when the U-IWVTA is modified into an L- IWVTA. Due to the negative connotation of the wording “withdrawn”, where this otherwise relates to non-CoP, the request, during previous session, was to use “production definitely discontinued” or any similar solution. The Secretary of the Sub Group IWVTA explains this will be on the agenda for the SGR0-18 meeting.

Postponed to next session.

c) Feedback from 2nd TF meeting Pre-Test IWVTA.

Mr. Chairman explains the outcome of the Task Force Pre-Test IWVTA, 2nd session. DETA is not involved within this pre-testing.

9. Next meetings

- 23rd session: Drafting Group DETA, 27 January, T-Systems, Stuttgart, Germany. Main issue for the meeting will be setting up the use cases.

- 24th session: Informal Group DETA, 2 March, OICA, Paris.