1 / 22

Future requirements for data exchange of PTI and CoC data

Future requirements for data exchange of PTI and CoC data EReg Annual Conference 2011, 12/13 May 2011, Warsaw/Poland. Dr. Detlef Marek, KBA/Germany, detlef.marek@kba.de. Agenda. Exchange of CoC data Legal aspects and requirements CoC database operated by KBA

ivrit
Télécharger la présentation

Future requirements for data exchange of PTI and CoC data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future requirements for data exchange of PTI and CoC data EReg Annual Conference 2011, 12/13 May 2011, Warsaw/Poland Dr. Detlef Marek, KBA/Germany, detlef.marek@kba.de

  2. Agenda • Exchange of CoC data • Legal aspects and requirements • CoC database operated by KBA • Approach for an European wide CoC database • Use for CO2-Monitoring • Exchange of PTI data • Legal aspects and requirements • Possible solution

  3. CoC (Certificate of Conformity) data • Legal aspects • Directive 2007/46/EC (EC Type Approval) • Manufacturer has to issue a CoC for each vehicle • shows that the vehicle has been manufactured in conformity with the approved vehicle type • contains ‘all’ technical data of the vehicle • Manufacturer may provide CoC data to the Registration Authority by electronic means • Commission interpretative communication 2007/C 68/04 • MS must request the CoC for registration of a new vehicle • Registration is based on the CoC • Directive 2009/443/EC (CO2-Monitoring) • CO2-Monitoring based on CoC data

  4. CoC data: requirements and problems • CoC data are needed: • for vehicle registration (technical data of the vehicle) • for CO2-Monitoring (Regulation 2009/443/EC) • for PTI (Periodical Technical Inspection) • Registration Procedure • In most countries registration of new vehicles with type approval is based on the “type approval data” or so called “type data” (type/ variant/version) and not on the individual CoCs • Type approval data can contain ranges (not exact values like CoC) • “Type data” (e.g. in Germany) only contain data necessary for the registration certificates • CoC data normally not exactly and not completely stored in the central vehicle registers

  5. CoC data: requirements and problems • New CoC since 29.04.2010 • no ranges allowed, e. g. actual mass (“real” mass of the vehicle) • value can differ from value in type approval data or “type data” • CO2-Monitoring • exact values needed (CO2 emission, mass, track width, wheelbase) • exact values normally not stored in the central vehicle registers • not all data (e.g. track width) are stored in the vehicle registers • Presentation by Mr Striekwold on EReg Topic Group IX • Problem of falsified or incorrect CoCs • Need for central storing of CoC data for each individual vehicle (VIN) in a CoC database • Use for registration and CO2-Monitoring

  6. CoC database at KBA/Germany • KBA made the decision to build up a CoC database: • will contain CoC data for each vehicle (VIN) produced for the German market • “open” for vehicles produced for the EU market • Manufacturers can deliver (voluntary) CoC data to KBA electronically • using existing communication infrastructure between KBA and manufacturers for “type data production” and “proof of utilization of registration document Part II” • XML-message, Batch-Mode • KBA will store the CoC data in a central database • “Quality check” of CoC data by using • “type data” (type, variant, version) • type approval documentation

  7. CoC database at KBA/Germany • KBA will use/provide the CoC data: • use them for CO2-Monitoring • provide them to the local registration authorities (online access) • provide them to other Member States (via extension of EUCARIS) • for CO2-Monitoring • for registration purposes • KBA currently implements the interface and the database • XML-specification already published to the manufacturers • operational by the end of this year (2011) • Manufacturers can start delivering CoC data by the end of this year

  8. Approach for an European wide CoC database • Build CoC databases in different Member States • Each manufacturer decides to which country/CoC database it sends the CoC data for a vehicle (VIN) • CoC data for a vehicle are stored only in one CoC database • Connect the CoC databases via an extension of EUCARIS • „virtual“ European CoC database consisting of the CoCs of all vehicles produced for the European market • no need for a „physical“ central European database (Commission idea, vehicle administrative platform) • „virtual“ central CoC database can be used for vehicle registration and CO2-Monitoring in the Member States

  9. Other central CoC Other central CoC Other central CoC MS Vehicle Reg. Manufacturer CoC EUCARIS Manufacturer Network Manufacturer Present, valid? Content? Type Data CoC database Vehicle Registration Member State (e.g. Germany) CO2- Monitoring Information

  10. CoC database – use for CO2-Monitoring Manufacturer 1 KOM Manufacturer 2 EUCARIS Manufacturer 3 Manufacturer 4

  11. CoC database – use for CO2-Monitoring CoC Manufacturer 1 CoC CoC KOM Manufacturer 2 CoC Manufacturer 3 Manufacturer 4

  12. TA TA CoC TA Manufacturer 1 TA CoC CoC KOM Manufacturer 2 CoC TA Manufacturer 3 Manufacturer 4

  13. CoC Manufacturer 1 CoC CoC KOM Manufacturer 2 CoC Manufacturer 3 Manufacturer 4

  14. CoC Manufacturer 1 CoC CoC KOM Manufacturer 2 CoC Manufacturer 3 Manufacturer 4

  15. CO2-Monitoring CO2 CoC Manufacturer 1 CO2 CoC CoC CO2 KOM Manufacturer 2 CoC Manufacturer 3 CO2 CO2 Manufacturer 4 CO2

  16. CoC data exchange - Open Issues • Dataset: • Should the dataset be limited to the current CoC or be extended by (national) “specialities” (needed for registration or PTI)? • Single uniform European dataset? • Quality check of the data? • Data exchange/Communication • Extension of EUCARIS (functionalities, financing, etc.)? • Communication with the manufacturers (e.g. via Internet) • Co-operation/co-ordination of the different activities • NL/RDW has the same approach/idea like DE/KBA • Maybe other countries have also plans for a CoC database? • Co-operation with the manufacturers (provision of CoC data) • Co-operation with the European Commission • Co-operation with NorType, ETAES, … • Need for close co-operation!

  17. CoC data exchange – Next steps • Meeting/Workshop • to discuss the approach, possible requirements and open issues • will be organized by KBA in Hamburg (eventually on 15 or 16 June 2011) • Meeting between RDW and KBA • open also for other interested countries/parties • Invitation will be send via EReg secretariat • Maybe starting a new EReg Topic Group on this subject?

  18. Exchange of PTI (Periodical technical inspection) data • Data needed to carry out the PTI: • Need for more technical data of the vehicle • Directive 2010/48/EU amending Directive 2009/40/EC • Checking of Electric Controlled Safety Systems (ECS), like ABS, ESC, Airbags  „System data“ • System data normally not available in the national vehicle registers • In Germany the FSD (Fahrzeugsystemdaten GmbH) operates a database with „system data“ based on information delivered by the vehicle manufacturers (presentation EReg Conference 2010) • FSD provides these data to the technical inspection companies • Data with results of the PTI (roadworthiness certificate) • Mutual recognition of the roadworthiness certificates • Exchange of data of roadworthiness certificates

  19. Exchange of PTI data • Need for exchange of PTI data between the MS • However: • Development of European Database for (modernized) PTI is extremely time and money consuming • Decision making (political, managerial and financial) takes a long time • Existence of FSD database in Germany (with extra needed PTI information and PTI results) • FSD and German Government are willing to give access to this database to other MS (under certain preconditions) • Existing technology of EUCARIS offers a practical possibility for the exchange of these PTI-data • Member States and European Commission only need to invest in the initial development of a special PTI application

  20. FSD otherenforcementauthorities KBA Police Customs ClosedNetwork Technical Inspection Centers RegistrationAuthority RegistrationAuthority Possible architecture RegistrationAuthority 2009 CITA Conference

  21. Exchange of PTI data • Using the existing network and connections between the national Registration authorities will: • Save time • Prevent high investments • Prevent reinventing the wheel • Accelerate the introduction of PTI data exchange • Proposal: • Workshop with KBA, FSD, EUCARIS andotherinterested countries ororganizationstospecifyfurtherdetails • Eventually starting a pilot

  22. Thank you for your attention ! Questions ?

More Related