{
  "url": "https://openlegislation.uk/eu-regulation-2017-1503/annex-I",
  "json_url": "https://openlegislation.uk/eu-regulation-2017-1503/annex-I.json",
  "legislation": "eur/2017/1503",
  "legislation_title": "Commission Implementing Regulation (EU) 2017/1503 of 25 August 2017 amending Implementing Regulation (EU) 2016/68 on common procedures and specifications necessary for the interconnection of electronic registers of driver cards (Text with EEA relevance)",
  "legislation_url": "https://openlegislation.uk/eu-regulation-2017-1503",
  "path": "annex/I",
  "kind": "annex",
  "number": "I",
  "heading": null,
  "text": "Annexes I, II, III, VI, VII and VIII to Implementing Regulation (EU) 2016/68 are amended as follows:\n(1) Annex I is amended as follows:\n(a) in point 1.1, the second paragraph is replaced by the following:\n‘All TACHOnet messages shall be routed through the central hub.’;\n(b) point 2.2 is replaced by the following:\n‘2.2.\nThe central hub shall not store data for a period exceeding six months, other than the logging, statistical and routing data set out in Annex VII.’;\n(c) point 2.6.1 is replaced by the following:\n‘2.6.1.\nThe contact management functionality shall provide each Member State with the ability to manage the contact details regarding policy, business, operational and technical categories of that Member State, each Member State's competent authority being responsible for the maintenance of its own contacts. It shall be possible to view, but not edit, the contact details of the other Member States.’;\n(d) point 2.6.2 is deleted;\n(2) Annex II is amended as follows:\n(a) point 1.3 is replaced by the following:\n‘1.3.\nModify Card Status (MCS): allows the requesting Member State to notify the responding Member State, through a Modify Card Status Request, that the status of a card issued by the latter has changed. The responding Member State shall reply to the Modify Card Status request by sending a Modify Card Status response as soon as the register has been updated or the notification has been rejected, giving the result of the update and indicating the current card status (as recorded in the tachograph card register). This response shall be sent at the latest 10 calendar days after the notification request has been sent. In all cases, a Modify Card Status request or response shall be acknowledged with a Modify Card Status acknowledgment.’;\n(b) point 5 is replaced by the following:\n‘5.\nThe card status listed in the Appendix to this Annex shall not be used to determine if a driver card is valid for driving. When a Member State queries the register of the card issuing Member State via the CCS or CIC functionality, the response shall contain the dedicated field “valid for driving”. The national administrative procedures shall be such that CCS or CIC responses always contain the appropriate “valid for driving” value.’;\n(3) Annex III is amended as follows:\n(a) point 2.3 is replaced by the following:\n‘2.3.\nNational systems shall be capable of sending, receiving and processing all messages corresponding to any of the functionalities set out in Annex II.’;\n(b) the Appendix is replaced by the following:\n‘Appendix\nMinimum requirements for the content of the XML messages\nCommon header\nMandatory\nVersion\nThe official version of the XML specifications shall be specified through the namespace defined in the message XSD and in the version attribute of the Header element of any XML message. The version number (“n.m”) shall be defined as fixed value in every release of the XML Schema Definition file (xsd).\nYes\nTest Identifier\nOptional id for testing. The originator of the test shall populate the identifier and all participants in the workflow shall forward/return the same identifier. In production it shall be ignored and shall not be used if it is supplied.\nNo\nTechnical Identifier\nA UUID uniquely identifying each individual message. The sender shall generate a UUID and shall populate this attribute. This data shall not be used in any business capacity.\nYes\nWorkflow Identifier\nThe workflowId is a UUID and shall be generated by the requesting Member State. This identifier shall be then used in all messages to correlate the workflow.\nYes\nSent At\nThe date and time (in UTC format) that the message was sent.\nYes\nTimeout\nThis is an optional date and time (in UTC format) attribute. This value shall be set only by the central hub for forwarded requests and is calculated based on the date/time the initial request has been received by the hub. This shall inform the responding Member State of the time when the request shall be timed out. This value is not required in initial requests sent to the hub and all response messages.\nNo\nFrom\nThe ISO 3166-1 Alpha 2 code of the Member State sending the message or “EU”.\nYes\nTo\nThe ISO 3166-1 Alpha 2 code of the Member State to which the message is being sent or “EU”.\nYes\nCheck Issued Cards Request\nMandatory\nFamily Name\nDriver's family name.\nYes\nFirst Name\nDriver's first/given name.\nNo\nDate of Birth\nDriver's date of birth.\nYes\nPlace of Birth\nDriver's place of birth.\nNo\nDriving Licence Number\nDriver's driving licence number.\nNo\nDriving Licence Issuing Country\nThe country that issued the driver's driving licence.\nNo\nCheck Issued Cards Response\nMandatory\nStatus Code\nThe status code of the response.\nYes\nStatus Message\nAn explanatory status description.\nNo\nSearch Mechanism\nWas the card found by the NYSIIS search or a custom search.\nYes\nFound Driver Details\nYes if the driver is found\nFamily Name\nThe family name of any found drivers.\nYes\nFirst Name\nThe first name of any found drivers.\nNo\nDate of Birth\nThe date of birth of any found drivers.\nYes\nPlace of Birth\nThe place of birth of any found drivers.\nNo\nCard Details\nYes if the driver is found\nCard Number\nThe found card number.\nYes\nCard Status\nThe found card status.\nYes\nValid for driving\nThe found card is/is not valid for driving.\nYes\nCard Issuing Authority\nThe name of the authority that issued the found card.\nYes\nCard Start of Validity Date\nThe date of the start of validity of the found card.\nYes\nCard Expiry Date\nThe date of expiry of the found card.\nYes\nCard Status Modified Date\nThe date that the found card was last modified.\nYes\nTemporary Card\nThe found card is a temporary card.\nNo\nDriving Licence Details\nYes if a driver card is found\nDriving Licence Number\nThe found driver's driving licence number.\nYes\nDriving Licence Issuing Country\nThe issuing country of the found driver's driving licence.\nYes\nDriving Licence Status\nThe status of the found driver's driving licence.\nNo\nDriving Licence Issuing Date\nThe issuing date of the found driver's driving licence.\nNo\nDriving Licence Expiry Date\nThe expiry date of the found driver's driving licence.\nNo\nWorkshop Card Details\nYes if a workshop card is found\nWorkshop name\nThe name of the workshop to which the found workshop card was issued.\nYes\nWorkshop address\nThe address of the workshop to which the found workshop card was issued.\nYes\nCheck Card Status Request\nMandatory\nCard Number\nThe number of the card for which details are required.\nYes\nCheck Card Status Response\nMandatory\nStatus Code\nThe status code of the response.\nYes\nStatus Message\nAn explanatory status description.\nNo\nRequested Card Details\nYes if the requested card is found\nCard number\nThe requested card number.\nYes\nCard Status\nThe status of the requested card.\nYes\nValid for driving\nThe requested card is/is not valid for driving.\nYes\nCard Issuing Authority\nThe name of the authority that issued the requested card.\nYes\nCard Start of Validity Date\nThe date of the start of validity of the requested card.\nYes\nCard Expiry Date\nThe date of expiry the requested card.\nYes\nCard Status Modified Date\nThe date that the requested card was last modified.\nYes\nTemporary Card\nThe requested card is a temporary card.\nNo\nWorkshop Card Details\nYes if a workshop card is found\nWorkshop Name\nThe name of the workshop to which the card was issued.\nYes\nWorkshop Address\nThe address of the workshop to which the card was issued.\nYes\nCard Holder Details\nFamily Name\nThe family name of the driver to whom the card was issued.\nYes\nFirst Name\nThe first name of the driver to whom the card was issued.\nNo\nDate of Birth\nThe date of birth of the driver to whom the card was issued.\nYes\nPlace of Birth\nThe place of birth of the driver to whom the card was issued.\nNo\nDriving Licence Details\nYes if a driver card is found\nDriving Licence Number\nThe driving licence number of the driver to whom the card was issued.\nYes\nDriving Licence Issuing Country\nThe country that issued driving licence number to the driver to whom the card was issued.\nYes\nDriving Licence Status\nThe status of the driving licence of the driver to whom the card was issued.\nNo\nDriving Licence Issuing Date\nThe issuing date of the driving licence of the driver to whom the card was issued.\nNo\nDriving Licence Expiry Date\nThe expiry date of the driving licence of the driver to whom the card was issued.\nNo\nModify Card Status Request\nMandatory\nCard Number\nThe number of the card of which the status has changed.\nYes\nNew Card Status\nThe status to which the card has been changed.\nYes\nCard Status Modified Date\nThe date and time that the card status was modified.\nYes\nDeclared by\nAuthority\nThe name of the authority that made the card status change.\nYes\nAuthority address\nThe address of the authority that made the card status change.\nYes\nFamily Name\nThe family name of the person who made the card status change.\nNo\nFirst Name\nThe first name of the person who made the card status change.\nNo\nPhone\nThe phone number of the person who made the card status change.\nNo\nEmail\nThe email address of the person who made the card status change.\nNo\nModify Card Status Acknowledgement\nMandatory\nStatus Code\nThe status code of the acknowledgement.\nYes\nStatus Message\nAn explanatory status description.\nNo\nAcknowledgement type\nThe type of the acknowledgment: for request or response.\nYes\nModify Card Status Response\nMandatory\nStatus Code\nThe status code of the response.\nYes\nStatus Message\nAn explanatory status description.\nNo\nCard Number\nThe requested driver card number.\nYes\nCard Status\nThe status of the requested card as it exists in the tachograph card register.\nYes\nIssued Card Driving Licence Request\nMandatory\nCard Number\nThe number of the card that has been issued.\nYes\nDriving Licence Number\nThe number of the foreign driving licence that was used to apply for the driver card.\nYes\nFamily Name\nThe family name of the driver to whom the card was issued.\nYes\nFirst Name\nThe first name of the driver to whom the card was issued.\nNo\nDate of Birth\nThe date of birth of the driver to whom the card was issued.\nYes\nPlace of Birth\nThe place of birth of the driver to whom the card was issued.\nNo\nIssued Card Driving Licence Response\nMandatory\nStatus Code\nThe status code of the response.\nYes\nStatus Message\nAn explanatory status description.\nNo\n’\n(4) Annex VI is amended as follows:\n(a) points 1.4 to 1.8 are replaced by the following:\n‘1.4.\nThey shall respond to a minimum of 98 % of the requests forwarded to them in one calendar month and be able to service a request rate of 6 messages per second.\n1.5.\nWhen sending CIC, CCS, ICDL Responses and MCS Acknowledgments in accordance with Annex VIII, they shall respond to requests within 10 seconds.\nThe global request timeout (time within which the requestor may wait for a response) shall not exceed 20 seconds.\n1.6.\nMCS Responses shall be sent within 10 calendar days of the MCS Request being sent.\n1.7.\nNational systems shall not send requests to the TACHOnet hub at a rate exceeding 2 requests per second.\n1.8.\nEvery national system shall be able to cope with potential technical problems of the central hub or national systems in other Member States. These include, but are not limited to the following:\n(a) loss of connection to the central hub;\n(b) no response to a request;\n(c) receipt of responses after message timeout;\n(d) receipt of unsolicited messages;\n(e) receipt of invalid messages.’;\n(b) point 1.9 is deleted;\n(c) in point 2.2, the following sentence is added:\n‘The escalation procedure shall be detailed to the Commission upon request.’;\n(5) Annex VII is amended as follows:\n(a) the following paragraph is inserted after the heading of the Annex:\n‘This Annex provides details of logging, statistical and routing data collected at the central hub, not at the Member States.’;\n(b) point 3 is replaced by the following:\n‘3.\nPersonal data shall not be retained in the logs for more than 6 months after a transaction is complete. Statistical and anonymised routing information shall be retained indefinitely.’;\n(c) in point 4, the introductory wording is replaced by the following:\n‘The statistical data used for reporting may include, among others:’;\n(6) Annex VIII is amended as follows:\n(a) point 1.3 is replaced by the following:\n‘1.3.\nWhen the applicant for a driver card holds a driving licence issued in the Member State of application, that Member State shall check if an ICDL notification had been previously recorded in its national register. This check shall be done by searching the notifications first by Driving Licence number and secondly by NYSIIS keys and date of birth. If a notification is found, the Member State shall perform either a singlecast CIC or CCS search addressed to the Member State that sent the ICDL notification.’;\n(b) point 1.6 is replaced by the following:\n‘1.6.\nMember States may choose not to record in their national register the ICDL notifications received in accordance with points 1.3, 1.4 and 1.5. In this case, they shall carry out a broadcast CIC search for every application received.’;\n(c) in point 2.1, point (a) is replaced by the following:\n‘(a)\ncheck the actual status of the card by sending a CCS request to the issuing Member State. If the number of the card is not known, a singlecast CIC request shall be sent instead;’;\n(d) point 3.2 is replaced by the following:\n‘3.2.\nOnce the status of the driver card has been checked and it is valid for exchange, the competent authority of the Member State where the application has been made shall send a MCS notification through the TACHOnet messaging system to the issuing Member State.’.",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eur/2017/1503/annex/I",
    "retrieved_at": "2026-11-01T14:44:36.118725+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}