DBA D4.7 Initial Running Phase Report

From DE4A
Jump to navigation Jump to search

Back to Doing Business Abroad main page

[Work in progress]

Executive Summary

All project deliverables will have an Executive Summary.  

  • For the Executive Summary, all deliverables should follow these guidlelines:
  • Length: please limit the Executive Summary to 1 page (2 pages in exceptional cases).
  • ALL deliverables must have conclusions at the end of the document.
  • Goal: The Executive summary is not an “introduction” to the deliverable. The main goal of this section is to provide readers with a whole picture of the document (i.e. the abstract section from the papers), so that they can understand the content of the deliverable at once without further reading.
  • Self-contained: If there is any input coming from other deliverables, it must be mentioned here.
  • Motivation for the reader (Recommended: 1 –10  lines):
    • What is the reason for being for this deliverable? Which challenges it addresses?
    • What will the reader will learn from it?
  • Main results and findings (Recommended: 5 to 50 lines):
    • What are the main results achieved?
    • How does it contribute in the DE4A context?
  • Short conclusions (Recommended: 1 to 10 lines):
    • Key takeaway messages
  • Style: Please use a formal and practical writing style without jargon.


Topics to cover

This document embodies the intermediate report on the DE4A Doing Business Abroad pilot, providing preliminary conclusions and lessons learned from piloting cross border information exchange in the context of the Single Digital Gateway. It

Major achievements:

  • Developed international infrastructure for cross-border exchange of company evidence by all DBA partners, by deploying and integration DE4A common components to business registers and service providers.
  • Developed international infrastructure for croon-border authorization and authentication but most DBA Member Status, using eIDAS pilot nodes
  • Collected proof of proper operation of the cross border infrastructure for authentication, authorization and evidence exchange
  • Established an internationally supported evidence definition, for exchange of company-information between business registers and service providers.
  • Established design, architecture and assessment of infrastructure for cross border subscription and notification on company events, to be piloted in 2nd iteration.

Project status:

  • facing challenges of pandemic (priorities, resource availability), external events (acute vulnerabilities) and challenges on national level (implementation requires involvement of multiple organizations per Member State, complicating coordination and alignment). Occasionally leading to DBA partners terminating their involvement.
  • 5 DE/DO combinations finishing preparation for piloting by establishing secure communication. Others later in Q1/
  • Established all designs in order to start development of infrastructure for 2nd iteration.
  • Pilot runs behind schedule due to reasons mentioned above. Scheduled to start in February 2022.

Main lessons learned until now:

  • DE4A common components to support SDG have proven to be deployable and can be integrated to national infrastructures. Alle DBA partners managed to do so.
  • Member States establish their own maximum velocity for implementing the OOP TS, and velocities differ.
  • Applying a step-by-step approach for implementing the SDG infrastructure, increasing complexity gradually, has proven to aid with focus and managing the implementation.
  • Establishing an implementation project on Member State level, involving necessary competent authorities and setting priority over all these authorities, will ease the implementation of the SDG in Member States.
  • Member States need to establish a notified eID and eIDAS infrastructure before, or at the same time of implementing the SDG infrastructure.

Established infrastructure will be a good basis for future piloting activities (in iteration 2). The infrastructure can be extended with additional patterns and power validation mechanism (meaning there will not be a new infrastructure, but functionality wil be added to the established infrastructure).

Other Chapters

  1. Introduction
  2. Current status of pilot
  3. Goals and success criteria
  4. Pilot Procedures
  5. Conclusions and major achievements of initial iteration

References

Annexes