Difference between revisions of "Conclusions and major achievements of initial iteration"

From DE4A
Jump to navigation Jump to search
Line 5: Line 5:
 
[[Pilot Procedures|Back to previous Chapter: 4. Pilot Procedures]]
 
[[Pilot Procedures|Back to previous Chapter: 4. Pilot Procedures]]
  
[Work in progress]
+
The pilot has arrived at the starting point of actually piloting with real life participants. Pilot partners developed an international infrastructure for cross-border exchange of company evidence, by deploying and integrating DE4A common components to business registers and service providers. Also, a cross-border authorization and authentication infrastructure for piloting was established, using eIDAS pilot nodes. This infrastructure was designed, implemented and extensively tested until the point where the operation of the infrastructure was considered proven, and reliable to facilitate real-life piloting. The infrastructure supports the exchange of harmonized dataset for company-registration, while the designs and assessments have been completed to extend the infrastructure for cross-border notifications about changes in company-registrations. The infrastructure established for the first iteration of the pilot, is expected to provide a good starting point for the extensions that will be introduced for the second iteration and make cross-border notification possible.
  
Major achievements:
+
The exercise of analyzing, developing and testing the infrastructure as well as all legal and organizational preparation leads to the conclusion that the DE4A common components to support SDG have proven to be deployable and can be integrated to national infrastructures. All DBA partners managed to do so without running into any major technical or legal difficulties.Based on extensive tests and analysis, the intermediation pattern is useful for the business procedures as defined in the SDG. The need for receiving notifications about changes in business register entries was validated during analysis and design, regarding both changes in company data and company-concerned events. Analysis shows that this need cannot be fulfilled by BRIS. For the DBA pilot, a small set of events and changes has been selected for piloting, using the Subscription and Notification pattern.
* 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
 
  
Main lessons learned until now:
+
The availability of notified eID for companies, a mandate check mechanism and eIDAS infrastructure is a prerequisite for implementing the SDG. Using eIDAS for the cross border exchange of company_ids, makes reliable record matching at the Data Evaluator possible, preventing unintended extra registration and securing data quality in the Data Evaluator systems. Regarding the check on mandates of representatives, fine grained powers validation should be the ultimate goal and SEMPER specifications match the requirements for this goal. Starting with a simpler full-powers validation turns out to be a feasible and useful first step.
  
* DE4A common components to support SDG have proven to be deployable and can be integrated to national infrastructures. All DBA partners managed to do so without running into any major technical or legal difficulties.
+
Member States establish their own maximum velocity for implementing the necessary infrastructural, legal and procedural changes, and therefore velocities differ between Member States. Establishing  implementation projects 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. A European strategy to implement the SDG should allow for individual timelines, while still having all Member States converge to a clear endpoint in time in order to secure progress and make sure that the solution will become available for European Citizens and companies. Applying a step-by-step approach for implementing the SDG infrastructure, increasing complexity gradually, has proven to help with focus and managent of the implementation.
* Based on extensive tests and analysis, the intermediation pattern is useful for the business procedures as defined in the SDG. The need for receiving notifications about changes in business register entries was validated during analysis and design, regarding both changes in company data and company-concerned events. Analysis shows that this need cannot be fulfilled by BRIS. For the DBA pilot, a small set of events and changes has been selected for piloting, using the Subscription and Notification pattern.
 
* Member States establish their own maximum velocity for implementing the OOP TS, and velocities differ.
 
* Establishing a harmonized evidence definition that matches the needs of Data Evaluators and can be provided by Data Owners proves exhausting and time consuming. Focusing on a limited set increases feasibility and secures progress.
 
* 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 for companies, a mandate check mechanism and eIDAS infrastructure before, or at the same time of implementing the SDG infrastructure.
 
** Using eIDAS for the cross border exchange of company_ids, makes reliable record matching at the Data Evaluator possible, preventing unintended extra registration and securing data quality.
 
** Fine grained powers validation for mandate checks should be the ultimate goal and SEMPER specifications match the requirements for this goal. Starting with a simpler full-powers validation turns out to be a feasible and useful first step.
 
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).  
 
  
 
+
Establishing a harmonized dataset that embodies the evidence to be exchanged cross border turns out to be exhausting and time-consuming. Having the evidence match the needs of Data Evaluators and making sure that this van be provided by Data Owners requires much analysis, but is key in making the cross-border exchange of information valuable and durable. Focusing on a first limited, yet still valuable set of data increases feasibility and secures progress.
 
 
''This is a preliminary conclusion. The next deliverable (final report) will provide final conclusions, based on all executed cases with all DE/DO combinations and all patters / power validation methods that have been executed until Q3 2022. But if things are only piloted once, than these are final onclusiions. But in DBA probably limited.''
 

Revision as of 11:16, 2 February 2022

Back to Doing Business Abroad main page

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

Back to previous Chapter: 4. Pilot Procedures

The pilot has arrived at the starting point of actually piloting with real life participants. Pilot partners developed an international infrastructure for cross-border exchange of company evidence, by deploying and integrating DE4A common components to business registers and service providers. Also, a cross-border authorization and authentication infrastructure for piloting was established, using eIDAS pilot nodes. This infrastructure was designed, implemented and extensively tested until the point where the operation of the infrastructure was considered proven, and reliable to facilitate real-life piloting. The infrastructure supports the exchange of harmonized dataset for company-registration, while the designs and assessments have been completed to extend the infrastructure for cross-border notifications about changes in company-registrations. The infrastructure established for the first iteration of the pilot, is expected to provide a good starting point for the extensions that will be introduced for the second iteration and make cross-border notification possible.

The exercise of analyzing, developing and testing the infrastructure as well as all legal and organizational preparation leads to the conclusion that the DE4A common components to support SDG have proven to be deployable and can be integrated to national infrastructures. All DBA partners managed to do so without running into any major technical or legal difficulties.Based on extensive tests and analysis, the intermediation pattern is useful for the business procedures as defined in the SDG. The need for receiving notifications about changes in business register entries was validated during analysis and design, regarding both changes in company data and company-concerned events. Analysis shows that this need cannot be fulfilled by BRIS. For the DBA pilot, a small set of events and changes has been selected for piloting, using the Subscription and Notification pattern.

The availability of notified eID for companies, a mandate check mechanism and eIDAS infrastructure is a prerequisite for implementing the SDG. Using eIDAS for the cross border exchange of company_ids, makes reliable record matching at the Data Evaluator possible, preventing unintended extra registration and securing data quality in the Data Evaluator systems. Regarding the check on mandates of representatives, fine grained powers validation should be the ultimate goal and SEMPER specifications match the requirements for this goal. Starting with a simpler full-powers validation turns out to be a feasible and useful first step.

Member States establish their own maximum velocity for implementing the necessary infrastructural, legal and procedural changes, and therefore velocities differ between Member States. Establishing implementation projects 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. A European strategy to implement the SDG should allow for individual timelines, while still having all Member States converge to a clear endpoint in time in order to secure progress and make sure that the solution will become available for European Citizens and companies. Applying a step-by-step approach for implementing the SDG infrastructure, increasing complexity gradually, has proven to help with focus and managent of the implementation.

Establishing a harmonized dataset that embodies the evidence to be exchanged cross border turns out to be exhausting and time-consuming. Having the evidence match the needs of Data Evaluators and making sure that this van be provided by Data Owners requires much analysis, but is key in making the cross-border exchange of information valuable and durable. Focusing on a first limited, yet still valuable set of data increases feasibility and secures progress.