1. Declaration of Conformance (DOC) Proposal for Implementation

2. Principles concerning the DOC
Objective of DOC:
Authorities in the CPs should have the possibility to check, which versions of Regulations a single vehicle complies with
Proposed implementation
DOC is fully implemented within DETA
There is no document which would accompany a vehicle at this stage of the IWVTA process
A complimentary proposal to amend the draft of UN R0 is provided
The following slides illustrate the concept

3. Requirements in UN R0
The vehicle manufacturer has to upload the following information into DETA
The VIN for single vehicles
A confirmation that the single vehicle complies with the requirements of a given IWVTA
Alternatively, a Type Approval Authority can upload the information on behalf of the manufacturer
DETA has a user interface for query and provides output in a harmonised format defined in UN R0

4. Insertion of information into DETA
Type Approval Authority
Vehicle Manufacturer
IWVTA
contains
IWVTA approval number
List of all separate approval numbers
For produced vehicles:
VIN
IWVTA approval number
Confirmation
DETA 1. 2.

5. Insertion of information into DETA (alternative process)
Type Approval Authority
Vehicle Manufacturer
For produced vehicles:
VIN
IWVTA approval number 2.
IWVTA
contains
IWVTA approval number
List of all separate approval numbers 3.
DETA 1.

6. Query for information in DETA
authorized person
(e.g.Type Approval Authority)
VIN
with
IWVTA approval number
Declaration of Conformance
List of all separate approval numbers 2.
VIN 1.
DETA

7. Issues to be addressed in the development of DETA (1)
Access rights: Different access layers are necessary
Group
Write
Read
Type approval authorities
Approvals
All
Manufacturers
Connection between UI and approval numbers
Connection between approval number and VINs
Their own approvals
Other approvals for which they are permitted by the owner (e.g. parts)
Registration offices in CPs
---
List of individual approval numbers for an IWVTA number
Public
Expand a unique identifier into approval numbers

8. Issues to be addressed in the development of DETA (2)
Connect VIN numbers to an IWVTA
Who: vehicle manufacturer (alternatively: type approval authority)
Process:
Select IWVTA type approval number (from those contained in DETA attributed to the manufacturer, i.e. which the manufacturer may access)
Insert (list of) VINs
Confirmation
An automated import must be possible

9. Issues to be addressed in the development of DETA (3)
Obtain the DoC for a VIN
Who: type approval authority, registration office
Process:
Insert VIN
Obtain DoC including IWVTA type approval number as well as list of all separate UN Regulations (including versions) this vehicle complies with

10. Backup
The following slides define additional functionalities needed in DETA in conjunction with IWVTA but not directly related to the DoC

11. Further issues to be addressed in the development of DETA (1)
Connection between Unique Identifier (UI) and approval numbers
Who: vehicle manufacturer
Process:
Insert a UI
Select type approval numbers (from those contained in DETA attributed to the manufacturer, i.e. which the manufacturer may access)
Add additional type approval or registration numbers (e.g. from countries outside the 58 agreement)

12. Further issues to be addressed in the development of DETA (2)
Expand a Unique Identifier (UI)
Who: everybody, open access
Process:
Insert a UI
Get list of approval and/or registration numbers associated to that UI