Important notes on the ERRU specification changes in EUCARIS release 7
The EUCARIS ERRU Extension includes support for the ERRU v1.5 specification, adding Serious- and Very Serious Infringements (SI & VSI) in the EUCARIS Notification Infringement message version 2.0.
Background & timescale
The ERRU notification messages (v1.0) only allow the automated exchange of the Most Serious Infringements (MSI) defined in [1071/2009]. This paragraph lays out the procedure and timescale for including Serious Infringements (SI) and Very Serious Infringements (VSI) in the automated message exchange. Until 31/12/2015 Member States may choose to record only the Most Serious Infringements (MSI) in their register ( [1071/2009] Article 16.2 of). After this date Member States are obliged to include SI and VSI in their register as well. The ERRU infringement messages will need updating to allow SI and VSI codes to be exchanged.
Unfortunately, the Commission’s original proposal for the classification of VSIs and SIs was rejected by the European Parliament in December 2014. However, this rejection of the classifications did not release Member States from their obligation to record SI and VSI events in their register nor from their obligation to exchange this data with other competent authorities. However, until a defined set of common classifications enters into force it will not be possible to use ERRU to exchange SI and VSI data.
A revised Commission regulation on the classification of serious infringements has been submitted to and passed by the European Parliament and the Council in the beginning of 2016. It was then adopted on 18 March 2016 as Regulation 2016/403 ( [2016/403]) and published in the European Commission Official Journal 19th March 2016. The Regulation is binding in its entirety and it shall apply directly in Member States from 1 January 2017.
The EUCARIS ERRU notification messages 2.0 are compliant with the new regulation 2016/403, which means that after upgrading the EUCARIS instance can send and receive all Most Serious Infringements (MSI), Very Serious Infringements (VSI) and Serious Infringements (SI) that are mentioned in regulation 2016/403.
All ERRU Member States are legally obliged to be able to send and receive v2.0 messages, as of 1st January 2017, ultimately. Since ERRU Member States that use the Central Hub have a deadline of 1st December 2016, all EUCARIS member states should update before this date as well.
Impact of the ERRU changes between EUCARIS Member states
EUCARIS will -after upgrade- support EUCARIS ERRU Notification Infringements v2.0 messages. Since the 1.0 messages are not compatible with the 2.0 messages, EUCARIS will not downgrade v2.0 messages to 1.0. Instead, the message will retain in the upload queue until the recipient country is supporting and able to receive v2.0 Messages. Once the recipient country supports EUCARIS ERRU Notification Infringements v2.0 messages, the retaining messages will automatically sent by EUCARIS.
Impact of the ERRU changes between Central HUB countries and EUCARIS Member states
Identical to the impact between the EUCARIS member states, with the exception that EUCARIS Operations will issue a Configuration Update as soon as the Central HUB and connected countries are supporting the ERRU v1.5 specification. From that moment, retaining EUCARIS ERRU v2.0 messages will be sent to the Central HUB countries automatically.
Impact of the ERRU changes in the domestic domain (custom clients)
EUCARIS web client: fully supports the EUCARIS ERRU v2.0 messages.
Forwarding to custom client: The message version supported by the receiving custom client must be configured in the EUCARIS Services configuration of the local country. As long as the receiving custom client is configured to only support EUCARIS ERRU Notification Infringements v1.0 messages, the v2.0 messages will not be forwarded and retained in the EUCARIS upload queue. Once the service is capable of processing v2.0 messages and the receiving custom client is configured in the EUCARIS Services as v2.0 compatible client, the retaining messages will automatically be sent.
Retrieving by custom client: Retrieving an EUCARIS ERRU Notification Infringements v2.0 while requesting a v1.0 version (explicitly or implicitly) will result in a SOAP exception for the retrieving custom client. The retrieving custom client should handle this appropriately.