Type approval Data- base and vehicle registration in The Netherlands EReg Luxembourg, 12 May 2010 P.E.Th. Striekwold Manager Type Approval Department

Agenda Purpose of Database COC or Database? Quantity Process Quality Exchange Future

Efficient vehicle admission for higher quantities of vehicles Vehicle tax Road tax Yearly production of fuel consumption booklet CO2 monitoring for EU Policy/decision making (esp. in combination with registration data) Supporting EU member states for completing vehicle registration systems Purpose of type approval data in the Netherlands

COC or Type Approval data? RDW is confronted with COC’s which do not match with the type approval data Vehicle data should be supplied by an independent, non-commercial organisation

Connections with RDW database

Quantity: Registered number of European Type Approvals cat. M1 Numbers Type approvals Variants Versions

Quantity: Registered number of European Type Approvals cat. L Numbers Type approvals Variants Versions

Process: Distribution of European Type Approval information Each EG-member state sends issued WVTA information to all other EG- member states within 20 working days Most of the Member states use ETAES Some Member states send the information by post

Processing of European Type Approval information by RDW RDW downloads all WVTA approvals (.pdf) from ETAES every day RDW files a lot of this information from all type approvals into the RDW (ETR) database (all variants and versions) Lead-time for processing is maximum 14 days from downloading ETAES

Vehicle registration (efficient way) Day 1: -Importer sending digital file to RDW with: type-approval number, Variant code and Version code + some vehicle information (VIN, colour, tax-information etc.) -Checking validity into RDW computer system (art. 26, 2007/46) Day 2: -Production of vehicle registration document -Sending vehicle registration document to importer -Sending online information to ministry of finance for vehicle tax and road tax Reg. Doc. Reg. Doc.

Vehicle registration (efficient way) Random check of COC versus vehicle registration Periodical audit importers Penalty system for importers

Vehicle registration (individual way) Step 1: Physical check of vehicle/document for issuing vehicle at RDW Testing-centre (Same checks as vehicle registration efficient way) Step 2: Payment of vehicle tax Step 3: Registration of vehicle into RDW vehicle database Production of vehicle registration document Sending vehicle registration document to owner Lead-time 2, 3 days from payment of vehicle tax

Quality Software tools for processing (digital) data Four eyes principle during processing Frequent validation by “integrity-software” ISO certification for registration process Yearly EDP audit by external accountancy office Result: > 99% accuracy

Exchange of type approval data Phase I For completion of existing registrations in your own system (XML) RDW Member state send known information or incomplete TA-number, VAR- code, VERSION- code to RDW Member state receive limited files concerning type approval information for completing type approval keys (TA-number VAR+VERSiON code)

Exchange of type approval data Phase II For completion of existing registrations in your own system (XML) RDW Member state send complete typeapprovalnr, + VAR-code, + VERSION-code to RDW Member state receives type approval information for earlier vehicle registrations

Exchange of type approval data Phase III For new registrations. You can pull the information you desire - via Eucaris - into your own system (XML) RDW Member state send typeapprovalnr, variantcode, versioncode to RDW Member state receive on-line type approval information for registration vehicle

Future Central type approval database Integrated digital process including manufacturers and importers/dealers/etc Focus on surveillance of the process-management instead of data- management

Thank you for your attention !