‘Contracting party’ or ‘party’ means any Contracting party to the AETR; ‘eDelivery’ means the service developed by the European Commission making possible to transmit data between third parties by electronic means, providing evidence relating to the handling of the transmitted data, including proof of sending and receiving the data, and protecting transmitted data against the risk of any unauthorised alteration; ‘TACHOnet’ means the system for the electronic exchange of information on driver cards between contracting parties referred to in Article 31(2) of Regulation (EU) No 165/2014; ‘Central hub’ means the information system enabling the routing of TACHOnet messages between requesting and responding parties; ‘Requesting party’ means the contracting party emitting a TACHOnet request or a notification, which is then routed to the appropriate responding party by the central hub; ‘Responding party’ means the contracting party to whom the TACHOnet request or notification is addressed; ‘Card issuing authority’ or ‘CIA’ means the entity empowered by a contracting party for the issuing and management of tachograph cards.

TACHOnet is an electronic system for the exchange of information on driver cards between AETR contracting parties. TACHOnet routes the requests for information from the requesting parties to the responding parties, as well as the replies from the latter to the former. Contracting parties being part of TACHOnet must connect their national registers on driver cards to the system.

TACHOnet messaging system shall be composed of the following parts:

A central hub, which shall be able to receive a request from the requesting party, validate it and process it by forwarding it to the responding parties. The central hub shall wait for each responding party to answer, consolidate all the answers and forward the consolidated response to the requesting Party. National systems of the parties, which shall be fitted with an interface capable of both sending requests to the central hub and receiving the corresponding replies. National systems may use propriety or commercial software to transmit and receive messages from the central hub.

The following functionalities shall be provided through TACHOnet messaging system:

Check Issued Cards (CIC): allows the requesting party to send a Check Issued Cards Request to one or all responding parties, in order to determine if a card applicant already possesses a driver card issued by the responding parties. The responding parties shall reply to the request by sending a Check Issued Cards Response. Check Card Status (CCS): allows the requesting party to ask the responding party about the details of a card issued by the latter by sending a Check Card Status Request. The responding party shall reply to the request by sending a Check Card Status Response. Modify Card Status (MCS): allows the requesting party to notify the responding party, through a Modify Card Status Request, that the status of a card issued by the latter has changed. The responding party shall reply with a Modify Card Status Acknowledgement. Issued Card Driving Licence (ICDL): allows the requesting party to notify the responding party, through an Issued Card Driving Licence Request, that a card has been issued by the former against a driving licence issued by the latter. The responding party shall reply with an Issued Card Driving Licence Response.

Other message types deemed suitable for the efficient functioning of TACHOnet shall be included, for instance error notifications.

National systems shall recognise the card statuses listed in Table 1, when using any of the functionalities described in point 1. However, parties are not required to implement an administrative procedure that makes use of all of the listed statuses.

When a party receives a response or notification giving a status that is not used in its administrative procedures, the national system shall translate the status on the received message to the appropriate value in that procedure. The message shall not be rejected by the responding party, as long as the status in the message is listed in Table 1.

The card status listed in Table 1 shall not be used to determine if a driver card is valid for driving. When a party queries the register of the card issuing national authority via the CCS functionality, the response shall contain the dedicated field ‘valid for driving’. The national administrative procedures shall be such that CCS responses always contain the appropriate ‘valid for driving’ value.

Card statuses

Card Status	Definition
Application	The CIA has received an application to issue a driver card. This information has been registered and stored in the database with the generated search keys.
Approved	The CIA has approved the application for the tachograph card.
Rejected	The CIA did not approve the application.
Personalised	The tachograph card has been personalised.
Dispatched	The National Authority has dispatched the driver card to the relevant driver or delivering agency.
Handed Over	The National Authority has handed over the driver card to the relevant driver.
Confiscated	The driver card has been taken from the driver by the competent authority.
Suspended	The driver card has been taken temporarily from the driver.
Withdrawn	The CIA has decided to withdraw the driver card. The card has been permanently invalidated.
Surrendered	The tachograph card has been returned to the CIA, and declared no longer needed.
Lost	The tachograph card has been declared lost to the CIA.
Stolen	The tachograph card has been reported stolen to the CIA. A stolen card is considered lost.
Malfunctioning	The tachograph card has been reported as malfunctioning to the CIA.
Expired	The period of validity of the tachograph card has expired.
Replaced	The tachograph card, which has been reported lost, stolen or malfunctioning, has been replaced by a new card. The data on the new card is the same, with the exception of the card number replacement index, which has been increased by one.
Renewed	The tachograph card has been renewed because of a change of administrative data or the validity period coming to an end. The card number of the new card is the same, with the exception of the card number renewal index, which has been increased by one.
In Exchange	The CIA that issued a driver card has received a notification that the procedure to exchange that card for a driver card issued by the CIA of another Party has started.
Exchanged	The CIA that issued a driver card has received a notification that the procedure to exchange that card for a driver card issued by the CIA of another Party has completed.

The NYSIIS algorithm implemented in the central hub shall be used to encode the names of all the drivers in the national register.

When searching for a card via the CIC functionality the NYSIIS keys shall be used as the primary search mechanism.

Additionally, parties may employ a custom algorithm to return additional results.

The search results shall indicate the search mechanism which was used to find a record, either NYSIIS or custom.

If a party chooses to record ICDL notifications then the NYSIIS keys contained in the notification shall be recorded as part of the ICDL data. When searching the ICDL data the party shall use the NYSIIS keys of the applicant's name.

HTTPS shall be used for the exchange of messages between the central hub and the national systems.

National systems shall use the digital certificates referred to in Sub-appendices 4.8 and 4.9 for the purposes of securing the transmission of messages between the national system and the central hub.

National systems shall implement, as a minimum, certificates using the SHA-2 (SHA-256) signature hash algorithm and a 2 048 bit public key length.

National systems shall fulfil the following minimum level of service:

They shall be available 24 hours a day, 7 days a week. Their availability shall be monitored by a heartbeat message issued from the central hub. Their availability rate shall be 98 %, according to the following table (the figures have been rounded to the nearest convenient unit):

An availability of	means an unavailability of
	Daily	Monthly	Yearly
98 %	0,5 hours	15 hours	7,5 days

Parties are encouraged to respect the daily availability rate, however it is recognised that certain necessary activities, such as system maintenance, require a downtime of more than 30 minutes. However, the monthly and yearly availability rates remain mandatory. They shall respond to a minimum of 98 % of the requests forwarded to them in one calendar month. They shall respond to requests within 10 seconds. The global request timeout (time within which the requestor may wait for a response) shall not exceed 20 seconds. They shall be able to service a request rate of 6 messages per second. National systems may not send requests to the TACHOnet hub at a rate exceeding 2 requests per second. Every national system shall be able to cope with potential technical problems of the central hub or national systems in other parties. These include, but are not limited to: loss of connection to the central hub; no response to a request; receipt of responses after message timeout; receipt of unsolicited messages; receipt of invalid messages.

The central hub shall:

feature an availability rate of 98 %; provide to national systems notification of any errors, either via the response message or via a dedicated error message. The national systems, in turn, shall receive these dedicated error messages and have an escalation workflow in place to take any appropriate action to rectify the notified error.

Parties shall notify other parties and the European Commission of any routine maintenance activities via the web application, at least one week before the beginning of those activities if technically possible.

In order to ensure privacy, the data for statistical purposes shall be anonymous. Data identifying a specific card, driver or driver licence shall not be available for statistical purposes.

Logging information shall keep track of all transactions for monitoring and debugging purposes, and allow the generation of statistics about these transactions.

Personal data shall not be retained in the logs for more than 6 months. Statistical information shall be retained indefinitely.

the requesting party; the responding party; the type of message; the status code of the response; the date and time of the messages; the response time.

The Directorate-General for Informatics of the European Commission (DIGIT) shall make available a PKI service (referred to as ‘CEF PKI service’) to the AETR Contracting Parties connecting to TACHOnet (henceforth the national authorities) through eDelivery.

The procedure for request and revocation of digital certificates, as well as the detailed terms and conditions for its usage, are defined in the Appendix

Usage of certificates:

Once the certificate is issued, the national authority, shall use the certificate only in the context of TACHOnet. The certificate can be used to: authenticate the origin of data; encrypt data; ensure detection of integrity breaches of data. Any usage not explicitly authorised as part of the permitted usages of the certificate is prohibited.

Contracting parties shall:

protect their private key against unauthorised use; refrain from transferring or revealing their private key to third parties, even as representatives; ensure confidentiality, integrity, and availability of the private keys generated, stored and used for TACHOnet; refrain from continued use of the private key following expiry of the validity period or revocation of the certificate, other than to view encrypted data (e.g., decrypting emails). Expired keys shall be either destroyed or retained in a manner preventing its use; provide the Registration Authority with the identification of those authorised representatives who are authorised to request revocation of certificates issued to the organisation (revocation requests shall include a revocation request password and details about the events that lead to revocation); prevent misuse of the private key by requesting the revocation of the associated public key certificate in case of compromise of the private key or of the private key activation data; be responsible and hold the obligation of requesting revocation of certificate under circumstances identified in the certification policies (CP) and certification practices statement (CPS) of the Certification Authority; notify the Registration Authority without delay of loss, theft, or potential compromise of any AETR keys used in the context of TACHOnet.

Without prejudice of the liability of the European Commission in contravention of any requirements laid down in applicable national law or with respect to liability for matters which may not be excluded under that law, the European Commission shall not be responsible or liable with regard to:

the content of the certificate which lies exclusively with the certificate owner. It shall be the responsibility of the certificate owner to check the accuracy of the certificate content; the use of the certificate by its owner.

A PKI (Public Key Infrastructure) is a set of roles, policies, procedures and systems needed to create, manage, distribute and revoke digital certificates. The CEF PKI service of eDelivery enables issuance and management of digital certificates used to ensure confidentiality, integrity and non-repudiation of the information exchanged between Access Points (AP).

The PKI service of eDelivery is based on the Trust Centre Services TeleSec Shared Business CA (Certification Authority) for which the Certificate Policy (CP)/Certification Practices Statement (CPS) of TeleSec Shared-Business-CA of T-Systems International GmbH apply.

The PKI service issues certificates that are suitable for securing various business processes within and outside of companies, organisations, public authorities and institutions that require a medium security level to prove the authenticity, integrity and trustworthiness of the end-entity.

I, [name and address of the organisation representative], certifies that the following information are to be used in the context of the request, generation and retrieval of public key digital certificates for TACHOnet access points supporting the confidentiality, integrity and non-repudiation of the TACHOnet messages:

Contact person information:

— Contact person #1	— Contact person #2
— Name:	— Name:
— First names:	— First names:
— Mobile phone:	— Mobile phone:
— Telephone:	— Telephone:
— Email:	— Email:
— —	— — — —

Trusted courier information:

— Trusted courier #1	— Trusted courier #2
— Name:	— Name:
— First names:	— First names:
— Mobile phone:	— Mobile phone:
— Email:	— Email:
— Passport issuing country:	— Passport issuing country:
— Passport number:	— Passport number:
— Passport validity end date:	— Passport validity end date:

Place, date, company stamp or seal of the Organisation:

Signature of the authorised representative:

The key terms used in this Sub-appendix are defined in the CEF Definitions section on the CEF Digital Single Web Portal:

https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/CEF+Definitions

The key acronyms used in this Component Offering Description are defined in the CEF Glossary on the CEF Digital Single Web Portal:

https://ec.europa.eu/cefdigital/wiki/pages/viewpage.action?spaceKey=CEFDIGITAL&title=CEF+Glossary