ANNEX
Annexes I, III, VI, VII and VIII to Implementing Regulation (EU) 2016/480 are amended as follows:
(1)
Annex I is amended as follows:
(a)
point 1.3 is replaced by the following:
‘1.3.
All messages exchanged shall be routed through the central hub.’;
(b)
point 2.2 is replaced by the following:
‘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.’;
(c)
point 2.3 is replaced by the following:
‘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.’;
(d)
point 2.6 is replaced by the following:
‘2.6. Contact management
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.’;
(2)
in Annex III, the Appendix is amended as follows:
(a)
in the first table, the item ‘Timeout’ is replaced by the following:
‘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’
(b)
in the table with the heading ‘Check Good Repute Response’, the item ‘Community Licence Number’ is replaced by the following:
‘Community Licence Number
The serial number of the Community licence of the transport undertaking (free text alphanumeric field with length 1 to 20).
Yes’
(c)
in the table with the heading ‘Infringement Notification Request’, the item ‘Community Licence Number’ is replaced by the following:
‘Community Licence Number
The serial number of the certified true copy or of the Community licence of the transport undertaking (free text alphanumeric field with length 1 to 20).
Yes’
(d)
in the table with the heading ‘Infringement Notification Response’, the following items are inserted after the item ‘Transport Undertaking Name’:
‘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 (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’
(e)
in the table with the heading ‘Check Community Licence Request’ the item ‘Community Licence Number’ is replaced by the following:
‘Community Licence Number
The serial number of the certified true copy or of the community licence for which the details are requested (free text alphanumeric field with length 1 to 20).
Yes’
(f)
the table with the heading ‘Check Community Licence Response’ is amended as follows:
(i)
the following items are inserted after the item ‘Originating Authority’:
‘Status Code
The status code of the response (e.g. found, not found, error, etc.).
Yes
Status Message
An explanatory status description (if necessary).
No’
(ii)
the item ‘Transport Undertaking’ is replaced by the following:
‘Transport Undertaking
Yes if status code is Found’
(iii)
the item ‘Community Licence Details’ is replaced by the following:
‘Community Licence Details
Yes, if status code is Found’
(iv)
the following item is inserted after the item ‘Community Licence Details’:
‘Licencing Authority
The authority that issued the community licence to the transport undertaking.
Yes’
(v)
the items ‘Licence Number’ and ‘Licence Status’ are replaced by the following:
‘Licence Number
The serial number of the community licence of the transport undertaking as recorded in the register (free text alphanumeric field with length 1 to 20).
Yes
Licence Status
The status of the community licence of the transport undertaking as recorded in the register.
Yes’
(vi)
the items ‘Certified True Copy Details’ and ‘Licence Number’ are replaced by the following:
‘Certified True Copy Details
No
Certified True Copy Number
The serial number of the certified true copy of the community licence of the transport undertaking as recorded in the register (free text alphanumeric field with length 1 to 20).
Yes’
(vii)
the items ‘Licence Status’, ‘Licence Type’, ‘Start Date’ and ‘Suspension Date’ are deleted;
(viii)
the item ‘Suspension Expiry Date’ is replaced by the following:
‘Withdrawal Expiry Date
The date on which the certified true copy of the community licence withdrawal expires.
No’
(3)
in Annex VI, the following sentence is added at the end of point 2.2:
‘The escalation procedure should be detailed to the Commission upon request’;
(4)
Annex VII is amended as follows:
(a)
point 2 is replaced by the following:
‘2.
In order to ensure privacy, the data for statistical and routing purposes shall be anonymous. Data identifying a specific transport manager, transport undertaking, community licence or CPC will not be available for statistical purposes.’;
(b)
points 4 and 5 are replaced by the following:
‘4.
Personal data shall not be retained in the logs for more than 6 months after a transaction is complete. Statistical and routing information will be retained indefinitely.
5.
The statistical data used for reporting may include, among others:
(a)
The requesting Member State.
(b)
The responding Member State.
(c)
The type of message.
(d)
The status code of the response.
(e)
The date and time of the messages.
(f)
The response time.’;
(5)
in Annex VIII, point 2.4 is replaced by the following:
‘2.4.
In all cases, any Infringement Notification Request and Response shall be acknowledged with an Infringement Notification Acknowledgment’.
