Presentation 2 of 2 by Ermo Taks, senior consultant in E-governance architectures and interoperability, Estonia, at seminar 2, held on 18 March 2021, which addresses digital government principles and building blocks. This 2nd event takes place in the framework of a series of three webinars organised by the SIGMA Programme, a joint initiative of the OECD and EU, principally financed by the EU, on the role of life events in end-to-end public service delivery.

1. © OECD
Digital government building
blocks in the context of end-
to-end public service delivery
The Once Only Principle and the TOOP
Large Scale Pilot of the Once Only
Principle
[Ermo Täks, MSA, Estonia]
18 March 2021

2. How to build EU wide
information system?
• This includes the development of appropriate
technical solutions for
 bridging the different architectures
 an analysis of the legal and organisational context
 the formulation of tailor-made recommendations
for pilots
 providing generic recommendations, based on the
project’s experience.

3. How to build EU wide
information system?
• What is needed?
 the presence of a variety of strengths, capacities
and mandates in the developing team,
 public administrations and their private sector
partners
• directly responsible for the practical implementation
 research partners
• to provide assistance

4. The Once-Once Principle (OOP)
• The Once-Once Principle (OOP) - citizens and
businesses should supply information only
once to a public administration.
• It is the public administration who has to
 take actions in order to internally share this data
 by respecting the relevant data protection rules.
• The overall aim is to reduce administrative
burden

5. Two OOP related projects
• First projects initated 2017
• Contains two paralleel projects
 Stakeholder Community on the Once-Only
Principle For Citizens (SCOOP4C)
• Investigates, discusses and disseminates how the OOP
can be implemented in public service provisioning
• A stakeholder community of actors that have
implemented or will implement OOP solutions
 The Once Only Principle Project
• explores and demonstrates the once-only principle through
multiple sustainable pilots.
5

6. SCOOP4C findings
• OOP enablers
 Political commitment
 Legal interoperability
 Semantic interoperability
 Technical interoperability
 Trust and Transparency
 Data protection and Privacy
 Data quality
 Citizen-centred design
6

7. SCOOP4C findings
• Technical building blocks
 Secure Data Exchange
 eID and Trust Services
 Network Infrastructure
 Interoperability Governance
 Interoperability Assets
 Catalogue
7

8. Motivation for TOOP
• e-Government has multi-disciplinary and inter-sectoral
character;
• development of e-services is rooted narrowly in existing
organisational structures,
 without any vision on how those structures can be improved and
related to, and supported
 by the legislative process and other drivers often attributed to
successful public sector innovation
 leading to failures in information systems development
• Today’s technology is limited to strategy improving public
sector efficiency
 To support the effectiveness of policies
 To create more open, inclusive, innovative, participatory and
trustworthy government

9. TOOP
• TOOP develops a federated architecture
 on a cross-border collaborative pan-European scale in
order to identify drivers and barriers and
 to provide a basis for future implementations and
wider use of the OOP in public service provisioning for
businesses.
• consortium of 51 organizations, 19 different EU
Member States public administrations and two
Associated Countries

10. TOOP Pilot Areas and countries
• eProcurement
 DE, FR, GR, IT, PT
• •General Business Mobility (eGov-to-BR)
 AT, EE, GR, IT, NL, NO, PL, RO, SE, SI, SK
 Licenses, permissions, mandates, company data
 Cooperation with BRIS
• Online Ship and Crew Certificates
 BG, DK, EE, GR, LV, NO
10

11. How TOOP fits into the big
picture
11

12. Baseline Scenario: Simple pull of
data
12
10
DATA CONSUMER DATA PROVIDER
TOOP
Identification
Determine Data
Requirements
Data Provider Capability
Prepare Data
Request
Process Data
Request
Prepare Data
Response
Process Data
Response
Transform Data Transform Data
Ensure Consent
Map Semantics
Discover Publish
Data Request
Send Receive
Data Response
Receive Send
VIEW &
ACCEPT
VIEW &
ACCEPT

13. Extended Scenario: Notify and
push
13
DATA CONSUMER DATA PROVIDER
Aware of EO
Notification Capability
Process
Notification
Prepare
Notification
Prepare Data
Update
Decision to
accept Data
Subscribe Publish
Data Change Notification
Receive Broadcast
Send Receive
Event: EO
Data Change
Data Change Acceptance
Process
Acceptance
Process Data
Update Data Update
Receive Send
Ensure Consent
TOOP
Map Semantics
Transform Data

14. Re-use and enhance existing
panEuropeaninfrastructure
14
eIDAS infrastructure
eDelivery
infrastructure
Additional Attribute Discovery,
Mandates modelling etc.
OO profiling of Message Exchange,
Dynamic Discovery etcetc.
Semantic mapping (e.g.
eCertis)
CEF, ISA
TOOP
Ensure Consent
DATA
PROVIDER
DATA
CONSUMER
Provide EO
Attributes
Provide
Company
Data
Identify EO
Request EO
Attributes
Request
Company
Data

15. Implementation Option
15
TOOP Message
Exchange Date
Model
DP
DP
Bespoke MS Solution
complianct
to common
TOOP specifications
Bespoke MS
Solution
complianct
to common TOOP
specifications

16. TOOP Reference Architecture
(TOOPRA)
16

17. Lessons learned
• SDGR evidence is a document, not evidence of
transmission or smth.
• Governmental digital systems should have integration
layer,
 integrating PA silos, businesses and citizens,
 great enabler of also cross-border data and service exchange
• Basic solutions need to be in place
 mindset: to reuse rather duplicate data
• Personal data protection
 of upmost importance
 enabler and barrier at the same time
17

18. Additional information
• TOOP Project website: toop.eu
• EIF recommendations regarding
interoperability
 https://joinup.ec.europa.eu/collection/nifo-
national-interoperability-framework-
observatory/solution/eif-
toolbox/recommendations
18