1. Status DETA Ways forward
DETA-31-03e revised
Informal document WP Rev.1
173rd WP.29, November 2017
Agenda item 4.5.
Submitted by the IWG on DETA
Working paper DETA-30-09
30th session of the IWG on DETA
Status DETA Ways forward
November 2017
Revision: New slides added after slide 10

2. What is DETA? Definition Different evolutions
DETA-31-03e revised
What is DETA?
Definition
Database for the Exchange of Type Approval documentation and information
Supports mutual recognition
Different evolutions
V0: existing test version based on ETAES* (exchange of Approval & Compliance Documents) currently managed by KBA
V1: is V0 in productive phase with basic functionalities, only
V2: include Unique Identifier (UI)
V3: include DOC
*European Type Approval Exchange System (ETAES) used in EU

3. DETA-31-03e revised
DETA and WP.29
DETA is introduced by Revision 3 to the 1958 Agreement Schedule 5 through outlining in its Schedule 5 the provisions for “…utilizing the secure internet database established by the United Nations Economic Commission for Europe…”.
The Unique Identifier (UI) is introduced by Revision 3 to the 1958 Agreement Schedule 5.
The Declaration of Conformance (DoC) is introduced by Regulation No. 0 (IWVTA).

4. Expected benefits Direct Indirect Reduction of administrative burden
DETA-31-03e revised
Expected benefits
Direct
Reduction of administrative burden
Faster processes
Crucial for the simplification of the GRE Regulations (UI)
Accommodate new needs regarding certification marking
Access (without request) to compliance documentation
Important for market surveillance
Check certification withdrawn (e.g. COP non compliance)
Indirect
Important for authorities to verify the validity of certificates
Important for authorities to authenticity (e.g. falsification) of certificates

5. Potential benefits* Software updates (e.g. Over The Air)
DETA-31-03e revised
Potential benefits*
Software updates (e.g. Over The Air)
Storage of software version numbers
Storage of validation models for Automated Driving
Available for other compliance certifications e.g. blue ribbons, CCC
* To be further elaborated

6. DETA-31-03e revised
Scenario 1
Stand alone project hosted at UNECE (See letter sent by the secretariat)
Estimated costs: 3.6 Mio USD
Includes Step 1 to 3, running costs and HR for 5 years
Conditions:
donation pledge (public or private)
Implementation steps:
Donation pledge for 3.6 Mio USD (time reference)
Project adopted by EXCOM (+3 months)
Purchasing (+4 months) ,
migration / installation (+1 month)
USD per year
USD per year per CP

7. Scenario 2 DETA-31-03e revised
Step-by-step installation of DETA at UNECE
3 consecutive projects
Estimated costs:
Step 1 (DETA V1 License, installation, running costs 1 year) EUR*
Step 2 (DETA V2 Unique Identifier): EUR
Step 3 (DETA V3 Declaration Of Conformance): EUR
Conditions
Pledge for each Steps
Pledge for 1 JPO post (Confirmation JPO post) – important savings vs. scenario 1
Implementation steps
Step 1
Donation pledge EUR (reference date)
Project adopted by EXCOM (+3 months)
Purchasing (+4 months) ,
migration / installation (+1 month)
Step 2 (UI)
Donation pledge EUR (reference date) (public or private)
UI (+1 year)
Step 3 (DOC)
Donation pledge EUR (reference date) (public or private)
DOC (+1 year)
* Estimation based on the list price from 2007
USD per year
2.000 USD per CP per year

8. Scenario 3 Temporary [2 years] hosting in Germany (KBA)
DETA-31-03e revised
Scenario 3
Temporary [2 years] hosting in Germany (KBA)
This is only a catalyst to promote DETA
Estimated costs for UNECE:
 0 during the temporary hosting
 running costs etc. after migration to UNECE to be determined by experience
Minimum conditions:
UNECE is then hosting DETA
Pledge from donors [for EUR (V2+V3)]
Implementation step:
Agreement by WP.29

9. Consequence of not deciding…
DETA-31-03e revised
Consequence of not deciding…
Jeopardizing the simplification of GRE Regs.
Increasing administrative burden for exchange of compliance documents
Jeopardizing mutual recognition of IWVTA certificates (no or difficult or limited access to system type approvals)
Other solutions would need to be found for:
Software updates (e.g. Over The Air)
Storage of software version numbers
Storage of validation models for Automated Driving

10. DETA-31-03e revised
Decision of WP.29
The IWG on DETA is requesting WP.29 to decide on one scenario until March 2018
A decision “engages” the CP in terms of donation pledge
IWG is recommending Scenario 2 (with 3 as fall back)
Scenario 1 
+ best solution
- expensive
Scenario 2 
+ good solution
+ feasible
Scenario 3 
+ fastest solution
+ “catalyst”
+ good fall back solution
- Uncertain migration

11. Discussion during the 173rd WP.29
DETA-31-03e revised
Discussion during the 173rd WP.29
WP presented
Scenario 3 was supported but neither AI (OICA + CLEPA + IMMA + …) or UNECE could commit to the conditions.
Some Contracting Parties asked for an alternative:
Annual subscription fee
Pay per upload
(It was proposed to rename DETA)
Note: The IWG on DETA already explored these alternative financing options and assessed them as less effective than the RB option

12. Feasibility check – pay per upload
DETA-31-03e revised
Feasibility check – pay per upload
Pre-requisit: modifications of the DETA software needed:
Programming and testing (costs time and money – n/a)
Scenario 1:
CPs register and pay through the system
Start: once software would be modified
Scenario 2:
Start of Phase 1: once software would be modified
Scenario 3:
n/a

13. Feasibility check – subscription fee
DETA-31-03e revised
Feasibility check – subscription fee
No modification of the DETA software needed
Scenario 1:
Login credentials provided by UNECE upon subscription («upload» access rights)*
Start of Phase 1: ~10 subscriptions à $ – not realistic so far
Scenario 2:
Login credential provided by UNECE upon subscription («upload» access right)*
Start: e.g. ~11 subscriptions à $ realistic
Scenario 3:
No subscription
* No subscription fee for «read only» CP’s access