Besides the contractual aspects of the on boarding, the End User must also ensure that his IT system is ready to generate the necessary verification and decommissioning transactions to be submitted to the Verification System.

A specific process needs to be followed by the IT department or the external software supplier of the End User before this End User can move into the phase of the Technical Implementation of the access to the Verification System.

In this chapter we will not enter into the details of the functionality that needs to be developed at the level of the End User. We refer to the information sessions that have been organised during 2017 and 2018 as well as the different documents available on the BeMVO website and the BeMVO development portal describing in detail the FMD actions required from the End Users.

Software implementation process

implementatie van de software

The first phase in the software implementation process is to develop the solution/module that will be implemented at the level of the End User. This phase is composed of following main steps:

a) The IT department/external software provider (hereafter both called SWS) connects to the BeMVO/Arvato development portal and requests access to this portal.

b) BeMVO is performing a legitimacy check and verifies is the requesting SWS can receive approval to access to the development portal.

c) In case of a positive evaluation, BeMVO confirms the request to the portal and the portal is sending the access credentials to the requesting party.

d) The SWS can download all necessary documentation & files that will allow him to develop the webservice and the user’s access to the system.

e) The SWS develops the different business processes in the user’s ERP, POS, … system or sets up a stand-alone system, to generate the different access and transaction types, integrating the access requirements.

f) During the development, the SWS can test the different aspects using the test scripts available on the development portal.

Optional Pilot testing

When the SWS considers his development is ready, he can apply for some additional Pilot tests. These Pilot tests are done on the NMVS IQE environment, allowing the SWS not only to test the transactions (verification and decommissioning) but also to test his user implementation procedures.
The Pilot testing can also be set up after the Baseline Testing.

The second phase of the software implementation concerns the Baseline Testing, which needs to be executed for each major version of the End User’s systems:

A new section is added on the Arvato Development portal: Baseline Testing.
The objective of this section is mainly to provide to the SWS a formal way of verifying if the different web services that have been developed are resulting in the expected outcomes.

Execution of the Baseline Testing. The Baseline Testing consists of a set of basic test cases representing logical chains of business processes and is providing the possibility to create tests data.

When the Baseline testing is successful, the SWS completes the Test Report Template and uploads the report to the Baseline Testing environment.

BeMVO reviews the completeness of the Test Report and confirms the reception of this Test Report, containing the evidence that all tests were closed successfully. BeMVO also verifies the underlying audit trail of the performed tests.

BeMVO and the SWS agree on the implementation approach.

The Baseline Testing needs to be executed for each major version upgrade of the User’s system.

Upgrade of the Verification System

Depending on the needs and requirements from the EU commission, the EU stakeholders or the National competent Authorities, 2 major upgrades of the Verification System per year are to be expected.

The upgrades will always be backwards compatible with the last previous version.

User’s IT departments and providers need to execute the Baseline testing also for each new version of the Verification System in case the functionality added in the new version of the Verification System is impacting the connection with the End Users and this before a following new version becomes active.

This phase together with the contractual on boarding of the End User are the prerequisites to move to the next phase which is the implementation of the End User for access to the Verification System.