Current status of pilot

Back to Doing Business Abroad main page

Back to main page of D4.7 Initial Running Phase Report

Back to previous Chapter: 1. Introduction

2.1 Catalogue of services and status

Teruggrijpen naar de UC en scenarios zoals beschreven in D4.5 en per scenario beschrijven welke combinaties beschikbaar zijn op dit moment. (en eventueel welke beperkingen er bestaan op dit moment, alsook wat de verwachting is qua oplossing)

2.1.1 Use case and pilot scenario status

Previous deliverables already defined the two use cases and six pilot scenarios for the DE4A Doing Business Abroad pilot. During the customization and integration phase for the first pilot iteration these have been refined (and is some cases were abandoned due to pilot partners having to leave the consortium:

• Use case 1: starting a business in another Member State
  • the core of this use case is the fulfilment of procedural obligations to start doing business in the Member State. Therefore the pilot concentrates on the steps for a business to register with a service provider abroad.

• Use case 2: doing business in another Member State
  • the core of this use case is retrieving and updating company information by the service provider. Therefore the pilot will focus on the subscription process and the process of sending, receiving and processing event notifications.
  • the option to fulfill corporate tax duties or apply for a service may still be possible with the service provider, but will not be piloted.

Doing Business Abroad partners participate with Data Owners (DO) and Data Evaluators (DE), allowing to pilot these use cases in multiple DE/DO combinations. Unfortunately, some partners had to terminate their involvement in the DE4A Consortium due to - for example - higher priorities caused by establishing the international COVID-19 certificates. The table below displays the remaining DE/DO combinations per use case, and the current status (green = ready; orange = not completely ready)

	Data consumer			UC-1 Starting a business in another Member State				UC-2 Doing business in another Member State
pilot scenario	Country	Name	Portal	AT DO	NL DO	RO DO	SE DO	AT DO	NL DO	RO DO	SE DO
DBA1	Austria	BMDW	USP.gv.at		KvK	ONRC	BVK
DBA4	The Netherlands	RVO	mijn.rvo.nl	BMDW		ONRC	BVK			ONRC	BVK
DB6	Romania	ONRC	portal.onrc.ro	BMDW	KvK		BVK		KvK		BVK
DBA5	Sweden	BVE	verksamt.se	BMDW	KvK	ONRC			KvK	ONRC

To include the National side of catalogue of services. Describe per case what was intended and what has actually been achieved.

Example:

A table with name of the service, URL, description, any type of limitations (for example: access for registered users with an existing profile only), including availability limitations (examples: from April to September or Monday to Friday, 9:00 to 17:00). Additionally, any other interesting information about the service could be included

2.2 Strategy to mitigate infrastructure delays

Describe strategies that have been put into place until now, in order to prevent delays.

• bypass eIDAS authentication and add manual entry for eIDASLegalPersonIdentifier
• develop components between DT and DO to reduce dependency on DO development resources
• use existing infrastructure (SEMPER NODE) for piloting purposes and to deploy DE4A Connector
• temporarily use dummy IdP (ATLAS) with eIDAS
• use simulated data source and eProcedures
• Establish a demonstration of the DE4A Connector and DE/DO Mocks before starting usage in Member States
• Mention that NL will create a temporary and highly focussed MVP fix for the NL DO to be able to pilot the S&N pattern

2.3 Achieved interoperability status

To provide an overview of all possible DE/DO combinations and display the extend to which interoperability is possible

• NL: DO, DT, DR, DE operational; eIDAS operational
• AT: DO, DT, DT operational; DE operational but connected to eIDAS in March 2022; eIDAS operation with version 2.5, profile 1.2
• RO: DO, DT, DR, DE operational (DE=simulated); eIDAS operational
• SE: DO, DT, DR, DE operational (DE/DO simulated); eIDAS operational per January 2022

2.4 Updates in Metrics

To describe (if any) changes in metrics compared to the previous deliverable. Use D4.6 section 2.2 as a basis.

Include explanation about the changes performed and reasons behind.

• no updates?
• Or perhaps, now that we have more knowledge about S&N, Lookup and Fine Grained Powers Validation, we might want to refine the metrics on that?
• Mention that an additional questionnaire (limited in size) will be added, focussing on technical adequacy, process of connecting and deploying, and documentation. Not related to DBA pilot goals or success criteria, but to collect lessons learned for Chapter 3 of D4.7.

Next chapter: 3. Goals and success criteria