EReg TG I International Data Exchange Schiphol, 25 November 2008 Herman Grooters (RDW / NL)

1. EReg TG I International Data Exchange Schiphol, 25 November 2008 Herman Grooters (RDW / NL) Project Manager EUCARIS

2. Contents of this presentation • Tachonet • Introduction • IDT and MIDT projects • Tachonet architecture and main features • Current project status • Recent Developments • Problems with the current system • Initiatives CINC: TENET • Tachonet User Group • Tachonet release 2 • Integration of EUCARIS and Tachonet • Demo: fictive enforcement case

3. Introduction Tachonet • The Digital Tachograph project is about • Registration of resting- and driving times of truckers and busdrivers • In the Tachograph and in the chip of the strictly personal Tachocard of the trucker

4. IDT and MIDT projects • IDT project • Implementation of the Digital Tachograph • 2002 ? – 2004 • Responsible for development of Tachonet • Main functions: • Support of CIA’s (Card Issuing Authorities) by 4 services: • Check Issued Cards => to guarantee the uniqueness of an issued card • Notification of issued cards on a foreign DL => to improve the efficiency of the issuing process • Check Card Status => to enable enforcers to check the validity of the card • Modify Card Status => to inform CIA’s on confiscated cards • MIDT project • Monitoring of Implementation of the Digital Tachograph • 2004 – 2007; Carried out by SRA • Mainly concerned with roll-out of procedures and Tachonet in the MS

5. Tachonet Architecture and main features • Central application by the EU Data Centre in Brussels • All outgoing request to Brussels; all incoming requests from Brussels; the requesting MS is hidden • Requests for all are broadcasted by central application • For each dialogue 4 messages are used: MS2TCNrequest; TCN2MSrequest; MS2TCNresponse; TCN2MSresponse • A-synchronous communication (like e-mail) • Designed for batch processing in the card issuing process; completeness of the answer most important • Time outs (waiting time) determined by requester • Retry mechanism • Currently mainly interactive use

6. Tachonet Architecture Central TACHOnet system

7. Current project status • Member States in Production: • Austria, Belgium, Cyprus, Estonia, Finland, France, Germany, Iceland, Ireland, Italy, Latvia, Lichtenstein, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, UK • In test: • Bulgaria, Czech Republic, Greece, Hungary • Not involved: • Denmark, Portugal

8. Current project status; continued • Total of queries processed by Tachonet: 1,5 million • Supporting the issuing process: 99,5% • Supporting enforcement: 0,5% • Total of messages processed: 30 million • Online: 99% • Batch: 1 %

9. Recent developments Problems with the current system • The following problems were raised during MIDT meetings related to functionality: • Place of Birth should not be used as search criterion • Applications of drivers without a first name can not be processed • Inquiries of DL info should be added • Specification of Card Status needs reconsideration, in cooperation with enforcers

10. Recent developments Problems with the current system • The following problems were raised during MIDT meetings related to availability and security: • Tachonet should be mandatory; guaranteed level of availability is needed • 80% of CIC request get an incomplete reply (even after 48 hours) => process is ineffective; some MS want a central index • Number of requests to small countries out of proportion • Security measures need evaluation, e.g. network accreditation • Requesting MS unknown => no compliance with Data Protection Directive 95/46/EC, art.12

11. Recent developments Problems with the current system • The following problems were raised during MIDT meetings related to enforcement: • Enforcers should be able to use Tachonet • Information on company cards (transport undertakings) should be added to support enforcers • Non EU-AETR drivers should be included

12. Recent developments Initiatives CINC: TENET • CINC: Card Issuing and Network Committee • Working group of CIA’s within MIDT • Currently supported by CORTE • No formal status; but EC has invited MS to deliver input via CINC • Recent Developments • CINC and CORTE have written a letter to the EC to indicate their problems • CORTE has written a project plan for TENET • TENET is Tachonet Enhanced Network => Tachonet release 2

13. Recent developments Tachonet User Group • Working Group of the Committee on Social Legislation Relating to Road Transport • Scope of work: improvements of functionality, operation and maintenance • Assessment of future developments of the Tachonet system, over the short-, medium- and long term • Duration of the user group: 24 months or longer if needed • Actions/decisions via comitology procedure or other means such as co-decision

14. Recent developments Tachonet release 2 • IBM/Siemens already got an assignment for an upgrade • Work Package 1 • ‘Technical’ upgrade of BizTalk, .NET, SQL server, Windows Server • Necessary because of discontinuation of support by Microsoft (end of life) • Transparent for MS • 01-11-2008 – 31-03-2009 • Work Package 2 • Addition of country-code in request messages • Aim: enabling of MS to inform a citizen about the origins of a request • By this compliancy with 95/46/EC? • Data Protection Officer of the EC will carry out a final assessment • All MS will have to adapt their applications • 01-04-2009 – 31-05-2009 => illusion! • Work Package 3 • Development of reporting tool on availability • 01-06-2009 – 30-06-2009

15. Recent developments Tachonet release 2; continued • All MS are requested by the EC to comment on the other issues raised by CINC and CORTE • Working group on functional issues like card statusses • Larger functional issues like a central index or addition of DL info have to be discussed • No time schedule yet • Security evaluation by EC • Availability hard to improve without a SLA • SLA requires that Tachonet is mandatory • Tachonet mandatory after a recast of Regulation 3821/85, probably mid-2010

16. Recent developments Tachonet release 2; conclusions • EC will stick to minor technical upgrades and improvements • Functional requests will have too much impact; MS do not agree => stagnation • Enforcers will not be supported • Consequently: alternative solutions should be considered • CINC has invited the EUCARIS Secretariat to present EUCARIS at the next MIDT meeting, February 2009

17. Integration of Tachonet and EUCARIS sTESTA EUC EUC Brussels Tacho broker Tacho broker

18. Integration of Tachonet and EUCARIS sTESTA EUC EUC What’s new? Brussels Tacho broker Tacho broker

19. Integration of Tachonet and EUCARIS; what’s new ? • New services; new messages • New screens in the Webclient • Adaptation of routing: direct or via Brussels • Mapping of the message protocol: EUCARIS (SOAP) => TCN (plain XML, other header) • Conversion of synchronous  asynchronous communication

20. Advantages of the use of one interface to EUROPE: EUCARIS • One standardised interface between Europe and national organisations • One time installation of generic functionality • No interoperability issues (all MS use the same interface) • Resulting in reduction of costs • Increased service levels • Investment in a cluster of servers shared by different stakeholders • Fail-over guarantees higher availability • Load balancing guarantees better performance • Monitoring and support concentrated • Possibilities for integrated client applications: vehicle, owner/holder, DL, Tachograph card, transport undertaking all in one application • Demo: fictive enforcement case

21. Demo: Fictive enforcement case Licence number Vehicle + O/H Licence number CoC number Transport Undertakings Insurances Card number Tachocards File number File number DL number Notific. on infringements Get sanctions Driving Licence