COMMISSION 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
Article 2
Definitions
Article 3
Obligation to connect to ERRU
Article 4
Technical specifications
Article 5
Use of ERRU
Article 6
Repeal
Article 7
Entry into force
ANNEX I
GENERAL ASPECTS OF ERRU
1. ARCHITECTURE
2. MANAGEMENT
2.5. MOVEHUB web portal
2.6. Contact management
ANNEX II
ERRU FUNCTIONALITIES
ANNEX III
ERRU MESSAGE PROVISIONS
1. GENERAL TECHNICAL REQUIREMENTS
2. XML MESSAGES STRUCTURE AND SCHEMA DEFINITION (XSD)
Appendix
Minimum requirements for the content of the XML messages
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 Hub for forwarded requests. This will inform the responding Member State of the time when the request will be timed out. This value is not required in MS2TCN_ |
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 |
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. |
Yes |
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 |
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 |
End Date of Unfitness |
End date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). Applicable if the Fitness is unfit. |
No |
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 as recorded in the register. |
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 |
Infringement Notification
Infringement Notification Request |
Mandatory |
|||||||||||||||||
Business Case Identifier |
A serial or reference number identifying each individual request. |
Yes |
||||||||||||||||
Notifying Authority |
The competent authority that issues the infringement notification. |
Yes |
||||||||||||||||
Transport Undertaking |
Yes |
|||||||||||||||||
Transport Undertaking Name |
The name of the transport undertaking against which the infringement is being recorded. |
Yes |
||||||||||||||||
Community Licence Number |
The serial number of the certified true copy of the Community license of the transport undertaking. |
Yes |
||||||||||||||||
Vehicle Registration Number |
The Vehicle registration number of the offending vehicle. |
Yes |
||||||||||||||||
Vehicle Registration Country |
The country in which the vehicle is registered. |
Yes |
||||||||||||||||
Serious Infringement |
Yes |
|||||||||||||||||
Date of Infringement |
Date of the infringement in ISO 8601 format. (YYYY-MM-DD) |
Yes |
||||||||||||||||
Category |
The category of the infringement:
|
Yes |
||||||||||||||||
Infringement Type |
In accordance with the classification provided in Annex IV to Regulation (EC) No 1071/2009 and Annex I to Regulation (EU) 2016/403 |
Yes |
||||||||||||||||
Date of Check |
The date of the check at which infringement has been ascertained in ISO 8601 format (YYYY-MM-DD). |
Yes |
||||||||||||||||
Penalty Imposed (for each Serious Infringement) |
Yes |
|||||||||||||||||
Penalty Imposed Identifier |
The serial number of the individual penalty imposed. |
Yes |
||||||||||||||||
Final Decision Date |
The final decision date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). |
Yes |
||||||||||||||||
Penalty Type Imposed |
Declaration of either:
|
Yes |
||||||||||||||||
Start Date |
The start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD) |
No |
||||||||||||||||
End Date |
The end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD) |
No |
||||||||||||||||
Is Executed |
Yes/No |
Yes |
||||||||||||||||
Penalty Requested (for each Serious Infringement) |
No |
|||||||||||||||||
Penalty Requested Identifier |
The serial number of the individual penalty requested. |
Yes |
||||||||||||||||
Penalty Type Requested |
Declaration of either:
|
Yes |
||||||||||||||||
Duration |
The duration of the requested penalty (calendar days). |
No |
Infringement Notification Response |
Mandatory |
|||||||||||||||||||
Business Case Identifier |
A serial or reference number matching the business case identifier of the request. |
Yes |
||||||||||||||||||
Originating Authority |
The competent authority that issued the original infringement notification. |
Yes |
||||||||||||||||||
Licensing Authority |
The competent authority responding to the infringement notification. |
Yes |
||||||||||||||||||
Status Code |
The status code of the infringement response (e.g. found, not found, error, etc.). |
Yes |
||||||||||||||||||
Status Message |
An explanatory status description (if necessary). |
No |
||||||||||||||||||
Transport Undertaking |
Yes |
|||||||||||||||||||
Transport Undertaking Name |
The name of the transport undertaking as recorded in the register. |
Yes |
||||||||||||||||||
Penalty Imposed |
No |
|||||||||||||||||||
Penalty Imposed Identifier |
The serial number of the individual penalty imposed (given in the Penalty Requested Identifier of the Infringement Notification). |
Yes |
||||||||||||||||||
Authority Imposing Penalty |
The name of the authority imposing penalty. |
Yes |
||||||||||||||||||
Is Imposed |
Yes/No |
Yes |
||||||||||||||||||
Penalty Type Imposed |
Declaration of either:
|
Yes |
||||||||||||||||||
Start Date |
The start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). |
No |
||||||||||||||||||
End Date |
The end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). |
No |
||||||||||||||||||
Reason |
Reason if penalty is not imposed. |
No |
Infringement Notification Acknowledgement |
Mandatory |
|||||
Business Case Identifier |
A serial or reference number matching the business case identifier of the notification or the response. |
Yes |
||||
Status Code |
Status code of the acknowledgement. |
Yes |
||||
Status Message |
Status Message String |
No |
||||
Originating Authority |
For an IN_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’. For an IR_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’. |
Yes |
||||
Licensing Authority |
For an IN_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’. For an IR_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’. |
Yes |
||||
Acknowledgement Type |
Defining Acknowledgement Type Possible Values:
|
Yes |
Check Community Licence
Check Community Licence Request |
Mandatory |
|
Business Case Identifier |
A serial or reference number identifying each individual request. |
Yes |
Originating Authority |
The authority issuing the search request. |
No |
Transport Undertaking |
Yes |
|
Transport Undertaking Name |
The name of the transport undertaking for which the community licence details are requested. |
Yes |
Community Licence Number |
The serial number of the certified true copy of the community license for which the details are requested. |
Yes |
Vehicle Registration Number |
The vehicle registration number for which the certified true copy of the community licence is issued. |
No |
Check Community Licence Response |
Mandatory |
|||||||||||||||
Business Case Identifier |
A serial or reference number identifying each individual request. |
Yes |
||||||||||||||
Originating Authority |
The authority that issued the search request. |
No |
||||||||||||||
Transport Undertaking |
Yes |
|||||||||||||||
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 Details |
Yes |
|||||||||||||||
Licence Number |
The serial number of the community licence of the transport undertaking as recorded in the register. |
Yes |
||||||||||||||
Licence Status |
The status of the community licence of the transport undertaking as recorded in the register:
|
Yes |
||||||||||||||
Licence Type |
The type of the community licence as recorded in the register. A declaration of:
|
Yes |
||||||||||||||
Start Date |
The start date of the community licence. |
Yes |
||||||||||||||
Expiry Date |
The expiry date of the community licence. |
Yes |
||||||||||||||
Withdrawal Date |
The withdrawal date of the community licence. |
No |
||||||||||||||
Suspension Date |
The suspension date of the community licence. |
No |
||||||||||||||
Suspension Expiry Date |
The date on which the community licence suspension expires. |
No |
||||||||||||||
Managed Vehicles |
The number of vehicles managed as recorded in the register. |
Yes |
||||||||||||||
Certified True Copy Details |
Yes |
|||||||||||||||
Licence Number |
The serial number of the certified true copy of the community licence of the transport undertaking as recorded in the register (this is the licence number that was received in the request). |
Yes |
||||||||||||||
Licence Status |
The status of the certified true copy of the community licence of the transport undertaking as recorded in the register:
|
Yes |
||||||||||||||
Licence Type |
The type of the certified true copy of the community licence as recorded in the register. A declaration of:
|
Yes |
||||||||||||||
Start Date |
The start date of the certified true copy of the community licence. |
Yes |
||||||||||||||
Expiry Date |
The expiry date of the certified true copy of the community licence. |
Yes |
||||||||||||||
Withdrawal Date |
The withdrawal date of the certified true copy of the community licence. |
No |
||||||||||||||
Suspension Date |
The suspension date of the certified true copy of the community licence. |
No |
||||||||||||||
Suspension Expiry Date |
The date on which the certified true copy of the community licence suspension expires. |
No |
ANNEX IV
TRANSLITERATION AND NYSIIS SERVICES
ANNEX V
SECURITY REQUIREMENTS
ANNEX VI
SERVICE LEVELS
An availability of |
means an unavailability of |
||
Daily |
Monthly |
Yearly |
|
98 % |
0,5 hours |
15 hours |
7,5 days |