Pilot Procedures - Revision history

Ard.vanderheijden: /* 4.3 Planned improvement following received feedback */

2022-02-04T07:36:06Z

4.3 Planned improvement following received feedback

Ard.vanderheijden: /* 4.3.2 Pilot procedures improvement */

2022-02-04T07:28:28Z

4.3.2 Pilot procedures improvement

Ivar.Vennekens: /* 4.3.2 Pilot procedures improvement */

2022-02-03T19:06:45Z

4.3.2 Pilot procedures improvement

Ivar.Vennekens: /* 4.3.1 Functional and technical improvement */

2022-02-03T19:05:03Z

4.3.1 Functional and technical improvement

Ivar.Vennekens: /* 4.3.1 Functional and technical improvement */

2022-02-03T19:04:50Z

4.3.1 Functional and technical improvement

Ivar.Vennekens: /* 4.3.1 Functional and technical improvement */

2022-02-03T19:02:16Z

4.3.1 Functional and technical improvement

Ivar.Vennekens at 16:24, 3 February 2022

2022-02-03T16:24:04Z

Ivar.Vennekens at 16:12, 3 February 2022

2022-02-03T16:12:09Z

Ard.vanderheijden at 09:33, 28 January 2022

2022-01-28T09:33:01Z

Ard.vanderheijden: /* 4.1.1 General approach */

2022-01-28T09:30:31Z

4.1.1 General approach

@@ Line 176: / Line 176: @@
 ==== 4.3.1 Functional and technical improvement ====
-<span style="color:red">''Suggested text:''
+Functional scope of the first pilot iteration:
-''Functional scope of the first pilot iteration:''
+* eIDAS for full powers validation
-* ''eIDAS for full powers validation''
+Functional scope of the second pilot iteration:
-''Functional scope of the second pilot iteration:''
+*eIDAS for fine grained powers validation
-''It is likely that the running phase may lead to some optimisations for the intermediation pattern. Although the intermediation pattern will be used in the second pilot iteration (as starting point for subscribing to updates), it is not expected that these optimisations will be implemented in the second iteration. Looking at the goal of the pilot however, the objective is to learn as much as possible. To maximise "learning" the second pilot iteration will direct efforts towards experimenting with the new functionalities defined within scope of the second iteration. eIDAS full powers will be replaces by fine grained powers validation, allowing companies to differentiate in the procedures company representatives may apply for. Furthermore, the subscription and notification pattern allow data evaluators to receive information on business events that might impact the procedure. Finally, the lookup pattern allows the evaluator's back office to request updates or additional information on the company required to assess the impact on the procedure or prevent fraud. Resources are scarce it seems to make more sense to direct the effort to implement this additional functionality and learn new things, which can be considered for future European implementation of the OOP TS.''
+It is likely that the running phase may lead to some optimisations for the intermediation pattern. Although the intermediation pattern will be used in the second pilot iteration (as starting point for subscribing to updates), it is not expected that these optimisations will be implemented in the second iteration. Looking at the goal of the pilot, the objective is to learn as much as possible. To maximise "learning" the second pilot iteration will direct efforts towards experimenting with the new functionalities defined within scope of the second iteration. eIDAS full powers will be replaces by fine grained powers validation, allowing companies to differentiate in the procedures company representatives may apply for. Furthermore, the subscription and notification pattern allow data evaluators to receive information on business events that might impact the procedure. Finally, the lookup pattern allows the evaluator's back office to request updates or additional information on the company required to assess the impact on the procedure or prevent fraud. Resources are scarce it seems to make more sense to direct the effort to implement this additional functionality and learn new things, which can be considered for future European implementation of the OOP TS.
-''This way, the pilot intends to input as much as possible to the future development of the SDG in stead of technically fine-tuning the DE4A common components. Technical optimizations will however be summarized in the final report and could be addressed before European implementation of the OOP TS.''
+This way, the pilot intends to input as much as possible to the future development of the SDG in stead of technically fine-tuning the DE4A common components. Technical optimizations will however be summarized in the final report and could be addressed before European implementation of the OOP TS.
 ====4.3.2 Pilot procedures improvement ====

@@ Line 190: / Line 190: @@
-''It is likely that the running phase may lead to some optimisations for the intermediation pattern. Although the intermediation pattern will be used in the second pilot iteration (as starting point for subscribing to updates), it is not expected that these optimisations will be implemented in the second iteration. To maximise "learning" the second pilot iteration will direct efforts towards experimenting with the new functionalities defined within scope of the second iteration. eIDAS full powers will be replaces by fine grained powers validation, allowing companies to differentiate in the procedures company representatives may apply for. Furthermore, the subscription and notification pattern allow data evaluators to receive information on business events that might impact the procedure. Finally, the lookup pattern allows the evaluator's back office to request updates or additional information on the company required to assess the impact on the procedure or prevent fraud.''
+''It is likely that the running phase may lead to some optimisations for the intermediation pattern. Although the intermediation pattern will be used in the second pilot iteration (as starting point for subscribing to updates), it is not expected that these optimisations will be implemented in the second iteration. Looking at the goal of the pilot however, the objective is to learn as much as possible. To maximise "learning" the second pilot iteration will direct efforts towards experimenting with the new functionalities defined within scope of the second iteration. eIDAS full powers will be replaces by fine grained powers validation, allowing companies to differentiate in the procedures company representatives may apply for. Furthermore, the subscription and notification pattern allow data evaluators to receive information on business events that might impact the procedure. Finally, the lookup pattern allows the evaluator's back office to request updates or additional information on the company required to assess the impact on the procedure or prevent fraud. Resources are scarce it seems to make more sense to direct the effort to implement this additional functionality and learn new things, which can be considered for future European implementation of the OOP TS.''
 ====4.3.2 Pilot procedures improvement ====
@@ Line 208: / Line 199: @@
 On the one hand, it seems hard to involve users and therefore, all effort should start long before the actual start of running a pilot. On the other hand, the pilot seems to be relevant for users (especially companies) for a short moment in time: the moment that they see a business opportunity. The users will not necessarily wait for the pilot to start, in order to initiate doing business across border.
-Several considerations for the remains period of executing the pilot procedures are:
+Several considerations for the remaining period of executing the pilot procedures are:
 *The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross-border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.

@@ Line 210: / Line 210: @@
 Several considerations for the remains period of executing the pilot procedures are:
-*The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.
+*The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross-border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.
 *Additional promotion to involve users might be necessary. Data Owners and Data Evaluators seem often equipped to execute their core task (register business or providing services) but are not necessarily the best organization to broadcast the opportunity to join the pilot. DE4A has expertise available that might have to be used more extensively and team up with the DE and DO of the DBA partners.
 * As stated in section 2, possibly the metrics for evaluating the new interaction patterns will be extended and detailed during the 'customization and integration' phase for the second iteration. This will lead to changes in the questionnaires as well.

← Older revision		Revision as of 19:05, 3 February 2022
Line 193:		Line 193:

	''This way, the pilot intends to input as much as possible to the future development of the SDG in stead of technically fine-tuning the DE4A common components.''		''This way, the pilot intends to input as much as possible to the future development of the SDG in stead of technically fine-tuning the DE4A common components.''
		+	</span>

@@ Line 176: / Line 176: @@
 ==== 4.3.1 Functional and technical improvement ====
-''Suggested text:''
+<span style="color:red">''Suggested text:''
 ''Functional scope of the first pilot iteration:''
 * ''eIDAS for full powers validation''
-* ''intermediation pattern''
+*''intermediation pattern''
 ''Functional scope of the second pilot iteration:''
-* ''eIDAS for fine grained powers validation''
+*''eIDAS for fine grained powers validation''
-* ''subscription & notification pattern''
+*''subscription & notification pattern''
-* ''lookup pattern''
+*''lookup pattern''
@@ Line 201: / Line 201: @@
 Looking at the goal of the pilot however, the objective is to learn as much as possible. Implementing technical and functional optimizations for the second pilot iteration might learn the pilot that the functionality and technology performs better. But since resources are scares it seems to make more sense to direct the effort to implement additional functionality (the additional interaction patterns and powers validation) and learn new things, which can be considered for future European implementation of the OOP TS. This is the direction the DBA pilot is headed, and only improvements on the functionality piloted in the first iteration that seem absolutely necessary for proper pilot execution will be considered to include for the second iteration.
 ==== 4.3.2 Pilot procedures improvement ====
 Activities and effort spent on recruiting users to become involved in the pilot have learned that these activities are very timing-sensitive.
@@ Line 208: / Line 209: @@
 Several considerations for the remains period of executing the pilot procedures are:
-* The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.
+*The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.
-* Additional promotion to involve users might be necessary. Data Owners and Data Evaluators seem often equipped to execute their core task (register business or providing services) but are not necessarily the best organization to broadcast the opportunity to join the pilot. DE4A has expertise available that might have to be used more extensively and team up with the DE and DO of the DBA partners.
+*Additional promotion to involve users might be necessary. Data Owners and Data Evaluators seem often equipped to execute their core task (register business or providing services) but are not necessarily the best organization to broadcast the opportunity to join the pilot. DE4A has expertise available that might have to be used more extensively and team up with the DE and DO of the DBA partners.
 * As stated in section 2, possibly the metrics for evaluating the new interaction patterns will be extended and detailed during the 'customization and integration' phase for the second iteration. This will lead to changes in the questionnaires as well.
 [[Conclusions and major achievements of initial iteration|Next Chapter: 5. Conclusions]]

← Older revision		Revision as of 19:02, 3 February 2022
Line 176:		Line 176:

	==== 4.3.1 Functional and technical improvement ====		==== 4.3.1 Functional and technical improvement ====
		+	''Suggested text:''
		+
		+	''Functional scope of the first pilot iteration:''
		+
		+	* ''eIDAS for full powers validation''
		+	* ''intermediation pattern''
		+
		+	''Functional scope of the second pilot iteration:''
		+
		+	* ''eIDAS for fine grained powers validation''
		+	* ''subscription & notification pattern''
		+	* ''lookup pattern''
		+
		+
		+	''It is likely that the running phase may lead to some optimisations for the intermediation pattern. Although the intermediation pattern will be used in the second pilot iteration (as starting point for subscribing to updates), it is not expected that these optimisations will be implemented in the second iteration. To maximise "learning" the second pilot iteration will direct efforts towards experimenting with the new functionalities defined within scope of the second iteration. eIDAS full powers will be replaces by fine grained powers validation, allowing companies to differentiate in the procedures company representatives may apply for. Furthermore, the subscription and notification pattern allow data evaluators to receive information on business events that might impact the procedure. Finally, the lookup pattern allows the evaluator's back office to request updates or additional information on the company required to assess the impact on the procedure or prevent fraud.''
		+
		+	''This way, the pilot intends to input as much as possible to the future development of the SDG in stead of technically fine-tuning the DE4A common components.''
		+
		+
	From a functional perspective, Doing Business Abroad aims to pilot additional interaction patterns (subscription and notification / lookup) and fine grained powers validation mechanisms in the second iteration of the pilot. The functionality scoped for the first iteration of the pilot (intermediation pattern and full powers validation) will remain unchanged, and it is expected that this functionality will be used in the second iteration as well (in order to enroll additional companies, for which subscriptions will be set up with the DO). Doing Business Abroad foresees no functional improvements on functionality scoped in the first iteration, that will be piloted in the second iteration.		From a functional perspective, Doing Business Abroad aims to pilot additional interaction patterns (subscription and notification / lookup) and fine grained powers validation mechanisms in the second iteration of the pilot. The functionality scoped for the first iteration of the pilot (intermediation pattern and full powers validation) will remain unchanged, and it is expected that this functionality will be used in the second iteration as well (in order to enroll additional companies, for which subscriptions will be set up with the DO). Doing Business Abroad foresees no functional improvements on functionality scoped in the first iteration, that will be piloted in the second iteration.

@@ Line 169: / Line 169: @@
 |}
-User involvement was initiated 10 weeks in advance of the planned start of all pilot combinations. Depending of the actually expected starting date of each specific Data Owner/Data Evaluator combination, the intensity of the activities mentioned in the table above were set. This means that for those 5 DE/DO combinations mentioned in Chapter 2 of this document, more activities have been completed (and activities have been executed mote actively) than for the other combinations. The knowledge gained in DE/DO combinations is shared with other DBA DO/combinations as well as with other DE4A pilots, in order to smoothen future activities to recruit participants.
+User involvement was initiated 10 weeks in advance of the planned start of all pilot combinations. Depending of the actually expected starting date of each specific Data Owner/Data Evaluator combination, the intensity of the activities mentioned in the table above were set. This means that for those 5 DE/DO combinations mentioned in Chapter 2 of this document, more activities have been completed (and activities have been executed mote actively) than for the other combinations. The knowledge gained in DE/DO combinations is shared with other DBA DO/DE-combinations as well as with other DE4A pilots, in order to smoothen future activities to recruit participants.
 In addition to the planned activities to recruit users, preparations for an international event were made (in collaboration with other work packages in the DE4A program). Preparations were set up as a joined venture between DE4A and the EuroChambers organization, but had to be cancelled due to changes in priorities. The preparations made were useful for future events that DE4A aims to organize.
@@ Line 187: / Line 187: @@
 On the one hand, it seems hard to involve users and therefore, all effort should start long before the actual start of running a pilot. On the other hand, the pilot seems to be relevant for users (especially companies) for a short moment in time: the moment that they see a business opportunity. The users will not necessarily wait for the pilot to start, in order to initiate doing business across border.
-Several considerations for the remains period of execting the pilot procedures are:
+Several considerations for the remains period of executing the pilot procedures are:
 * The procedures for recruiting users should still become a continuous process, in order to offer as many companies as possible the opportunity to participate and if they can, schedule their cross border business initiation in line with the running period of the pilot. This will still not be possible for business activities having a limited window of opportunity, but might result in several additional users that can participate in the pilot.

@@ Line 36: / Line 36: @@
 ==== 4.1.2 Connectathons ====
-Member states performed unit-tests themselves before attempting cross border testing. Specific meetings, named connectathons, were held to test and confirm connection (at Milestone-level) between all Data Owners, Data Transferers, Data Requestors and Data Evaluators. In these meetings, structured testing (see [[DBA D4.6 Pilot planning|D4.6 Pilot Planning]] for testcases) was applied to confirm connections for both the eIDAS track and the OOP TS track, making sure that cross border communication and error handling works as expected. In case of errors and issues, the technical experts attending the meeting used the available time to investigate and solve issues like configuration-errors etcetera, or defined actions to perform between meetings, for issue regarding firewalls and local DNS-components. For issue-solving, experts shared screens and collectively studied log-files in involved Member States.
+Member states performed unit-tests themselves before attempting cross-border testing. Specific meetings, named connectathons, were held to test and confirm connection (at Milestone-level) between all Data Owners, Data Transferrers, Data Requestors and Data Evaluators. In these meetings, structured testing (see [[DBA D4.6 Pilot planning|D4.6 Pilot Planning]] for testcases) was applied to confirm connections for both the eIDAS track and the OOP TS track, making sure that cross-border communication and error handling works as expected. In case of errors and issues, the technical experts attending the meeting used the time available to investigate and solve issues like configuration-errors. In case experts could not solve the issue right away, they defined actions to perform between two connectathons, e.g. configuration of firewalls and local DNS-components. For issue-solving, experts shared screens and collectively studied log-files in involved Member States.
-Knowledge developed in the earlier connectathons was shared across other DBA partners and DE4A pilots, in order to smoothen future connectathons and establish remaining connections sooner. Also, test cases and presentations to structure these connectathons were re-used for future meetings, securing a constant quality of the established connection between components.
+Knowledge developed in the earlier connectathons was shared with other DBA partners and DE4A pilots, in order to smoothen future connectathons and establish remaining connections sooner. Also, test cases and presentations to structure these connectathons were re-used for future meetings, securing a constant quality of the established connection between components.
 Up until the moment of reporting, the OOP TS connection between a total of 5 Data Owner / Data Evaluator combinations were confirmed and in total 8 connectathons for the OOP TS track were organized. For the eIDAS track, three connectathons (and several bilateral technical investigations) were organized between Austria, Romania and The Netherlands, leading to one confirmed connection between Romania and The Netherlands, and connections between Austria and both Romania and The Netherlands with issues remaining to be resolved. [[Current status of pilot|Chapter 2]] of this document provides more detail of the connection status of each DBA partner.
@@ Line 47: / Line 47: @@
 # employees of the data evaluator in al DBA Member States
 # employees of the data owner in all Member States
-# representatives of companies in alle Member States, where 3 subgroups were identified
+# representatives of companies in all Member States, where 3 subgroups were identified:
-#* real representatives of real companies, aiming to actually do business in another Member State (also called invited companies)
+#* real representatives of real companies, aiming to ''actually do business'' in another Member State (also called invited companies)
-#* real representatives of (invited) real companies, aiming to contribute for learning purposes (also called companies of professional/private networks)
+#* real representatives of (invited) real companies, aiming to ''contribute for learning purposes'' (also called companies of professional/private networks)
-#* fake representatives of fake companies, to be used for piloting simulated/fictitious DE/DO combinations (also called fictitious companies)
+#* fictitious representatives of fictitious companies, to be used for piloting simulated/fictitious DE/DO combinations (also called fictitious companies)
-The table below displays the participation of each of these groups in specifica pilot DE/DO combinations , and remains unchanged compared to the planned involvement
+The table below displays the participation of each of these groups in specific pilot DE/DO combinations. The table remains unchanged compared to the planned involvement.
 {| class="wikitable" style="width:80%;"
 ! colspan="3" rowspan="3" |

@@ Line 9: / Line 9: @@
 == 4.1 Cross border pilot testing approach ==
-=== 4.1.1 General approach ===
+==== 4.1.1 General approach ====
 To establish and confirm the cross border connection between Data Owners and Data Evaluators, two tracks were defined in the [[DBA D4.6 Pilot planning|Pilot Planning deliverable]], which were each divided into several milestones. The milestone sequences were designed to introduce complexity in cross-border communication in a step-by-stap fashion, allowing involved Member States to focus on one challenge at a time and keep the complexity manageable. To summarize, the tracks and milestones that were used are:
 {| class="wikitable"
@@ Line 35: / Line 35: @@
 These tracks were meant for all Member States to use synchronously. This however, turned out to be unrealistic because all Member States seems to have their own challenges, leading to different speeds of development. The general approach, where tracks and milestones were defined, remained useful, however for each combination of Data Owner and Data Evaluator a separate timeline turned out necessary.
-=== 4.1.2 Connectathons ===
+==== 4.1.2 Connectathons ====
 Member states performed unit-tests themselves before attempting cross border testing. Specific meetings, named connectathons, were held to test and confirm connection (at Milestone-level) between all Data Owners, Data Transferers, Data Requestors and Data Evaluators. In these meetings, structured testing (see [[DBA D4.6 Pilot planning|D4.6 Pilot Planning]] for testcases) was applied to confirm connections for both the eIDAS track and the OOP TS track, making sure that cross border communication and error handling works as expected. In case of errors and issues, the technical experts attending the meeting used the available time to investigate and solve issues like configuration-errors etcetera, or defined actions to perform between meetings, for issue regarding firewalls and local DNS-components. For issue-solving, experts shared screens and collectively studied log-files in involved Member States.
@@ Line 43: / Line 43: @@
 == 4.2 End users engagement progress and dissemination/impact activities ==
-=== 4.2.1 End user involvement ===
+==== 4.2.1 End user involvement ====
 The [[DBA D4.6 Pilot planning|pilot planning deliverable]], section 4.4 described the user involvement activities. To summarize, the following user groups are targeted for participation in/evaluation of the pilot:
 # employees of the data evaluator in al DBA Member States
@@ Line 98: / Line 98: @@
 |}
-=== 4.2.2 Engagement activities ===
+==== 4.2.2 Engagement activities ====
 The table below shows the activities that were identified to recruit participants, as well as the status of each activity.
 {| class="wikitable" style="width:80%;"
@@ Line 168: / Line 168: @@
 |This activity applies to Data Owners that will work with fictitious data sources (mostly due to legal restrictions). For DBA, this applies to the Swedish Data Owner in particular. This data source is not ready yet (at the moment of creating this document), so therefore this user involvement activity has not been completed yet.
 |}
 User involvement was initiated 10 weeks in advance of the planned start of all pilot combinations. Depending of the actually expected starting date of each specific Data Owner/Data Evaluator combination, the intensity of the activities mentioned in the table above were set. This means that for those 5 DE/DO combinations mentioned in Chapter 2 of this document, more activities have been completed (and activities have been executed mote actively) than for the other combinations. The knowledge gained in DE/DO combinations is shared with other DBA DO/combinations as well as with other DE4A pilots, in order to smoothen future activities to recruit participants.
@@ Line 177: / Line 175: @@
 Before addressing possible improvements it must be noted that the paragraphs in this section are based on planning and preparation experiences only. As stated earlier in [[Current status of pilot|Chapter 2]], actual piloting is yet to be done. Still, feedback is available from the 'customization and integration phase' of the pilot, allowing for some reflection and reporting on possible improvements. It is to be expected that additional feedback form the pilot runs will lead to the identification of more improvements on Many aspects of the pilot procedures, as well as technical and functional properties of the OOP TS and SDG implementation.
-=== 4.3.1 Functional and technical improvement ===
+==== 4.3.1 Functional and technical improvement ====
 From a functional perspective, Doing Business Abroad aims to pilot additional interaction patterns (subscription and notification / lookup) and fine grained powers validation mechanisms in the second iteration of the pilot. The functionality scoped for the first iteration of the pilot (intermediation pattern and full powers validation) will remain unchanged, and it is expected that this functionality will be used in the second iteration as well (in order to enroll additional companies, for which subscriptions will be set up with the DO). Doing Business Abroad foresees no functional improvements on functionality scoped in the first iteration, that will be piloted in the second iteration.
@@ Line 184: / Line 182: @@
 Looking at the goal of the pilot however, the objective is to learn as much as possible. Implementing technical and functional optimizations for the second pilot iteration might learn the pilot that the functionality and technology performs better. But since resources are scares it seems to make more sense to direct the effort to implement additional functionality (the additional interaction patterns and powers validation) and learn new things, which can be considered for future European implementation of the OOP TS. This is the direction the DBA pilot is headed, and only improvements on the functionality piloted in the first iteration that seem absolutely necessary for proper pilot execution will be considered to include for the second iteration.
-=== 4.3.2 Pilot procedures improvement ===
+==== 4.3.2 Pilot procedures improvement ====
 Activities and effort spent on recruiting users to become involved in the pilot have learned that these activities are very timing-sensitive.

@@ Line 17: / Line 17: @@
 !OOP TS track
 |-
-|1
+!1
 |eIDAS for natural persons up and running
 |"Hello Europe" in lab (using a playground with DE/DO Mocks)
 |-
-|2
+!2
 |eIDAS for legal persons up and running
 |"Hello Europe" between two connected Member States
 |-
-|3
+!3
 |powers validation implemented
 |full scale cross-border communication between all Member States
 |-
-|4
+!4
+|
 |ready to start pilot