LegalizeCommission Implementing Regulation (EU) 2016/480 of 1 April 2016 establishing common rules concerning the interconnection of national electronic registers on road transport undertakings and repealing Regulation (EU) No 1213/2010 (Text with EEA relevance)
Article 1
Subject matter
This Regulation lays down the requirements regarding the connection of the national electronic registers on road transport undertakings to the ERRU messaging system, as set out in Article 16(5) of Regulation (EC) No 1071/2009.
Article 2
Definitions
For the purpose of this Regulation and in addition to the definitions laid down in Article 2 of Regulation (EC) No 1071/2009, the following definitions shall apply:
(a) ‘ERRU (European Registers of Road Transport Undertakings)’ means a system of interconnection of national electronic registers, set up in accordance Article 16(5) of Regulation (EC) No 1071/2009;
(b) ‘Asynchronous interface’ means a process whereby a message in response to a request is returned on a new HTTP connection;
(c) ‘Broadcast search’ means a request message from a Member State addressed to all other Member States;
(d) ‘Central hub’ means the information system enabling the routing of ERRU messages between Member States;
(e) ‘CPC’ means certificate of professional competence, as referred to in Article 8(8) of Regulation (EC) No 1071/2009;
(f) ‘Member State of infringement’ means the Member State in which a transport undertaking has committed an infringement;
(g) ‘Member State of establishment’ means the Member State in which an undertaking is established;
(h) ‘National system’ means the information system set up in each Member State for the purpose of emitting, processing and responding to ERRU messages;
(i) ‘Synchronous interface’ means a process whereby a message in response to a request is returned on the same HTTP connection as the one used for the request;
(j) ‘Requesting Member State’ means the Member State emitting a request or a notification, which is then routed to the responding Member States;
(k) ‘Responding Member State’ means the Member State to whom the ERRU request or notification is directed;
(l) ‘Clean check’ means a check where no infringements are detected.
Article 3
Obligation to connect to ERRU
Member States shall carry out the interconnection of the national electronic registers referred to in Article 16 of Regulation (EC) No 1071/2009 to ERRU in accordance with the procedures and technical requirements laid down in this Regulation.
The connection to ERRU of a Member State shall be considered to be established after the completion of the connection, integration and performance tests in accordance with the instructions and under the supervision of the Commission. The maximum duration of the tests shall be six months. The Commission shall take measures in case of failure of the above-mentioned tests. If those measures prove insufficient, the Commission may withdraw the testing support until the Member State proves that sufficient progress has been made at national level regarding connection to ERRU.
Article 4
Technical specifications
ERRU shall fulfil the technical specifications laid down in Annexes I to VII to this Regulation.
Article 5
Use of ERRU
Article 6
Repeal
Regulation (EU) No 1213/2010 is hereby repealed as from the date of application of this Regulation. References to the repealed Regulation shall be construed as references to this Regulation.
Article 7
Entry into force
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
It shall apply from 30 January 2019.
This Regulation shall be binding in its entirety and directly applicable in all Member States.
ANNEX I
GENERAL ASPECTS OF ERRU
1. ARCHITECTURE
ERRU shall be composed of the following parts:
1.1. A central hub, which shall be able to receive a request from the requesting Member State, validate it and process it by forwarding it to the responding Member States. The central hub will wait for each responding Member State to answer, consolidate all the answers and forward the consolidated response to the requesting Member State.
1.2. A national system per Member State, 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.
1.3. All messages exchanged shall be routed through the central hub.
2. MANAGEMENT
2.1. The central hub shall be managed by the Commission, which shall be responsible for the technical operation and maintenance of the central hub.
2.2. The central hub shall not store data for a period exceeding 6 months, other than the logging, statistical and routing data set out in Annex VII.
2.3. The central hub shall not provide access to personal data, except for authorised Commission personnel, when necessary for the purpose of monitoring the technical operation, maintenance and troubleshooting.
2.4. Member States shall be responsible for:
2.5. The Commission shall provide a web based application with secured access, referred to as ‘MOVEHUB web portal’, providing at least the following services:
2.6. The contact management functionality will provide each Member State with the ability to manage the contact details regarding policy, business, operational and technical categories of that Member State, being each Member State's competent authority responsible for the maintenance of its own contacts. It will be possible to view, but not edit, the contact details of the other Member States.
ANNEX II
ERRU FUNCTIONALITIES
1.The following functionalities shall be provided through ERRU:
1.1. Check Good Repute (CGR): allows the requesting Member State to send a query to one or all responding Member States, to determine the fitness of a transport manager and so the authorisation to operate a transport undertaking.
1.2. Notification of Check Result (NCR): allows the Member State where the check was carried out to notify the result of a check to the Member State of establishment. When a serious infringement has been found during the check, the Member State where the infringement was detected notifies the Member State of establishment through NCR that the transport undertaking has committed a serious infringement, and may request penalties to be applied to the transport undertaking in the Member State of establishment. When no infringement has been detected during the check, NCR allows the Member State where the check has been carried out to notify the Member State of establishment the positive result of the check.
1.3. Check Transport Undertaking Data (CTUD): allows the requesting Member State to send a query to the responding Member State about the following data that are specific to a transport undertaking: — information about the Community Licence and the certified true copies, — risk rating and risk rating band, — number of vehicles at the disposal of the transport undertaking, — registration number and registration country of the vehicles at the disposal of the transport undertaking, — number of employees.
1.4. Notification of Unfitness (NU): allows a Member State to inform all other Member States that a transport manager has been declared unfit and that as a result, its certificate of professional competence is no longer valid in any Member State.
2.Other message types deemed suitable for the efficient functioning of ERRU shall be included, for instance error notifications.
ANNEX III
ERRU MESSAGE PROVISIONS
1. GENERAL TECHNICAL REQUIREMENTS
1.1. The central hub will provide both synchronous and asynchronous interfaces for the exchange of messages. Member States may choose the most suitable technology to interface with their own applications.
1.2. All messages exchanged between the central hub and the national systems must be UTF-8 encoded.
1.3. Member States will ensure that their national systems can receive and process messages containing Greek or Cyrillic characters.
2. XML MESSAGES STRUCTURE AND SCHEMA DEFINITION (XSD)
2.1. The general structure of XML messages shall follow the format defined by the XSD schemas installed in the central hub.
2.2. The central hub and the national systems shall transmit and receive messages that conform to the message XSD schema.
2.3. National systems will be capable of sending, receiving and processing all messages corresponding to any of the functionalities set out in Annex II.
2.4. The XML messages shall include at least the minimum requirements laid down in the Appendix to this Annex.
Appendix
| Common Header | Mandatory | |
|---|---|---|
| Version | The official version of the XML specifications will 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’) will be defined as fixed value in every release of the XML Schema Definition file (xsd). | Yes |
| Test Identifier | Optional id for testing. The originator of the test will populate the id and all participants in the workflow will forward/return the same id. In production it should be ignored and will not be used if it is supplied. | No |
| Technical Identifier | A UUID uniquely identifying each individual message. The sender generates a UUID and populates this attribute. This data is not used in any business capacity. | Yes |
| Workflow Identifier | The workflowId is a UUID and should be generated by the requesting Member State. This id is then used in all messages to correlate the workflow. | Yes |
| Sent At | The date and time (UTC) that the message was sent. | Yes |
| Timeout | This is an optional date and time (in UTC format) attribute. This value will 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 central hub. This will inform the responding Member State of the time when the request will be timed out. This value is not required in initial requests sent to the central hub and all response messages. | No |
| From | The ISO 3166-1 Alpha 2 code of the Member State sending the message or ‘EU’. | Yes |
| To | The ISO 3166-1 Alpha 2 code of the Member State to which the message is being sent or ‘EU’. | Yes |
Check Good Repute
| Check Good Repute Request | Mandatory | |
|---|---|---|
| Business Case Identifier | A serial or reference number identifying each individual request. | Yes |
| Requesting Competent Authority | The competent authority that has issued the search request. | Yes |
| Transport Manager Details | Yes, if no CPC details | |
| Family Name | Transport manager’s family name(s) as indicated on the CPC. | Yes |
| First Name | Transport manager’s complete given name as indicated on the certificate of professional competence. | Yes |
| Date of Birth | Transport manager’s birth date in ISO 8601 format (YYYY-MM-DD). | Yes |
| Place of Birth | Transport manager’s place of birth. | No |
| Address | The address, city, postcode and country of the transport manager. | No |
| CPC Details | Yes, if no transport manager details | |
| CPC Number | Number of certificate of professional competence | Yes |
| CPC Issue Date | Date of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD). | Yes |
| CPC Issue Country | Issuing country of the CPC in ISO 3166-1 alpha 2 format. | Yes |
| Check Good Repute Response | Mandatory | |
| --- | --- | --- |
| Business Case Identifier | A serial or reference number matching the business case identifier of the request. | Yes |
| Requesting Competent Authority | The competent authority that has issued the search request. | Yes |
| Responding Competent Authority | The competent authority that has responded to the search request. | Yes |
| Status Code | The status code of the search (e.g. found, not found, error, etc.). | Yes |
| Status Message | An explanatory status description (if necessary). | No |
| Found Transport Manager Details | Yes if Status Code is Found | |
| Family Name | Transport manager’s family name(s) as recorded in the register. | Yes |
| First Name | Transport manager’s complete given name as recorded in the register. | Yes |
| Date of Birth | Transport manager’s birth date in ISO 8601 format (YYYY-MM-DD) as recorded in the register. | Yes |
| Place of Birth | Transport manager’s place of birth as recorded in the register. | No |
| CPC Number | Number of certificate of professional competence as recorded in the register. | Yes |
| CPC Issue Date | Date of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD) as recorded in the register. | Yes |
| CPC Issue Country | Issuing country of the CPC in ISO 3166-1 alpha 2 format as recorded in the register. | Yes |
| CPC Validity | Declaration of either ‘Valid’ or ‘Invalid’ | Yes |
| Total Managed Undertakings | The number of transport undertakings with which the transport manager is associated. | Yes |
| Total Managed Vehicles | The total number of vehicles with which the transport manager is associated. | Yes |
| Fitness | Declaration of either ‘Fit’ or ‘Unfit’. | Yes |
| Start Date of Unfitness | Start date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). | Yes if ‘Fitness’ is ‘Unfit’. |
| End Date of Unfitness | End date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). | Yes if ‘Fitness’ is ‘Unfit’. |
| Search Method | The method used to find the transport manager: NYSIIS, CPC, Custom. | Yes |
| Transport Undertaking (for each found Transport Manager) | Yes if Managed Undertakings > 0 | |
| Transport Undertaking Name | The name of the transport undertaking (name and legal form) as recorded in the register. | Yes |
| Transport Undertaking Address | The address of the transport undertaking (address, postal code, city, country) as recorded in the register. | Yes |
| Community Licence Number | The serial number of the Community licence of the transport undertaking (free text alphanumeric field with length 1 to 20). | Yes |
| Community Licence Status | The status of the community licence of the transport undertaking as recorded in the register. | Yes |
| Managed Vehicles | The number of vehicles managed as recorded in the register. | Yes |
Notification of Check Result
Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.