Commission Implementing Decision (EU) 2018/1614Show full title

2. ARCHITECTURE U.K.

2.1. The EVR architecture U.K.

2.1.1. Data search and consultation function (DSC function) U.K.

The DSC function shall be implemented by the Agency via a centralised web-based tool and an interface for machine to machine communication. The function shall enable the searching and consultation of data in the EVR after authentication.

The DSC function shall provide the registration entities with the means to extract the values of parameters in table 1 of their recorded vehicle registrations.

2.1.2. User creation and administration function (UCA function) U.K.

The UCA function shall be implemented via a centralised web-based tool setup by the Agency. The function shall enable persons and organisations to request access to EVR data and the competent registration entity (‘RE’) to create users and manage access rights.

2.1.3. Reference data administration function (RDA function) U.K.

The RDA function shall be implemented via a centralised web-based tool setup by the Agency. The function shall enable REs and the Agency to manage the common reference data.

2.1.4. Application, registration and data storage functions (ARS functions) U.K.

The ARS function shall enable keepers, after authentication, to submit applications for registration or update of an existing registration to the selected RE, via a web-based tool presenting the harmonised e-form (see Appendix 4). This function shall also allow the RE to register the registration data. The set of registrations for a given Member State shall be referred to as the vehicle register of such Member State.

Member States may decide to use the centralised ARS function (C-ARS) provided by the Agency or may implement the ARS function autonomously in a de-centralised manner. In the latter case, the Member State and the Agency shall ensure the compatibility and communication between the de-centralised ARS functions (D-ARS) and the centralised functions (DSC, UCA and RDA).

The centralised ARS function shall provide pre-reservation and management of vehicle numbers. The pre-reservation process shall allow for pre-filling of information required in the e-form by the applicant or the keeper.

2.2. Usability U.K.

The EVR functions shall be accessible to users with the most commonly used web browsers and in all Union official languages.

2.3. Availability U.K.

As a general rule, the EVR shall be permanently available, with a target system availability of 98 %.

However, in the case of a failure occurring out of business hours — Monday to Friday from 07:00 to 20:00 Central European Time — the restoration of the service shall be handled the next working day after the failure. The unavailability of the system shall be minimal during the maintenance.

2.4. Service level U.K.

Support shall be provided during business hours by a Help Desk to users on matters related to the use of the system and to the REs on the functioning of the system.

The Agency shall provide a test environment for the EVR.

2.5. Change control U.K.

The Agency shall establish a change control management process for the EVR.

2.6. Data integrity U.K.

The EVR shall ensure appropriate data integrity.

2.7. Pre-check U.K.

The EVR system shall provide automatic checks of data entered in the e-form, including checks against EVR vehicle registrations, completeness check and check of the format of data entered.

2.8. Facilitation of the use in the Union of vehicles registered in third countries U.K.

The Agency may implement the DSC function to allow for relevant entities in third countries to get access to appropriate data of the EVR when an international agreement to which the European Union is party provides for that.

The Agency may allow for the use of EVR functions by entities in third countries when an international agreement to which the European Union is party provides for that.