BOMOS in e-SENS

e-SENS
Electronic Simple European Networked Services
BOMOS in e-SENS
Using the BoMOS model in day2day practice, June 23 rd 2015.
Xander van der Linde, Marijke Salters, Bertrand.Gré[email protected]
e-Justice primary use cases
e-Justice Overview
3
e-Justice primary use cases
Matrimonial matters and parental responsibility
Maintenance Obligations
European Account Preservation Order
 facilitation of the resolution of legal issues across national borders
 making easier either cross-border court-to-court or cross-border court-to-citizen
communications involving electronic signing and secure transmission of electronic
documents
Real life scenarios
eDocuments
eId
semantics
eSignature
eDelivery
Cross border cases for:
 e-Health – easier access to health services while abroad
 e-Justice – electronic issuing of a claim in a foreign court
 e-Procurement – electronic bidding in other EU countries
 business lifecycle – online completion of formalities for company setup abroad
5
 and more: e-citizen lifecycle, maritime e-cooperation, e-agriculture
major building blocks
Formal standards (ETSI, CEN) & non-formal
specifications (OASIS, W3C,…)
reference implementation (Join-Up)
community of users & support
Re-using LSP solutions
e-CODEX
epSOS
SPOCS
“e-Justice Communication via Online Data EXchange”
“European Patients Smart Open Services”
“Simple Procedures Online for Cross-border Services”
finished
STORK
“Secure idenTity acrOss boRders linKed”
continued by STORK 2.0
PEPPOL
“Pan European Public Procurement OnLine
finished: maintained by OpenPEPPOL
All projects run with existing national back office systems
7
Consolidate, improve, extend
e-SENS
- Consolidates the results of LSP projects
- Improves solutions and develops generic
modules
- Extends their usage to more domains
aims at a coherent infrastructure vision
& links to the future
8
e-SENS
Electronic Simple European Networked Services
Introduction of Workpackage 3 of eSENS – Governance & Sustainability
What sustainability is to us
Long term (10+y) consolidation and maintenance of building blocks.
●
Building Blocks (BB) lifecycle (assessment, improvement,
operations)
●
governance (principles, structure & legal form)
●
financing (rationales & business case)
many external dependencies
●
developments in the framework of eIDAS Regulation,
10
●
Connecting Europe Facility (CEF)
●
eGovernment Expert Group.
Sustainable Building Blocks
Assessing the sustainability of Building Blocks
Assessment framework with 3 main assessment criteria:
●
●
●
Standardization (technical maturity, openness, IPR, lifecycle
management, maintenance, service levels, security)
Policy Alignment (interoperability, compliance, member states,
legal, data protection, applicability, potential)
Market/business need (business need by users, market support by
implementers)
assessment framework building on
●
11
CAMSS (Common Assessment Method for Standards and
Specifications) from EC ISA program
●
ADMS (Asset Description Metadata Scheme)
●
Specific sustainability requirements from eSENS
First formal sustainability
assessment cycle
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
eSignature:
EU eSignature Standards Framework
Stork 2 signature creation
eCodex trust library
PEPPOL eSignature verification
Digitial Signature Service
eDelivery:
Transport ebMS3 and AS4
Metadata service location
Addressing ebCore partyID
Service Metadata Publisher
Representational State Transfer
eDocuments:
Omnifarious Container for eDocuments
Virtual Company Dossier
Associated Signature Container
eID:
Personal identity attributes
Security Assertion Markup Language
Quality Authentication Assurance Levels
Online Certificate Status Protocol profile
What has been assessed?
Maturity
Openness
Alignment with existing policies
IPR
Life cycle management
Applicability
Market support
Appreciation of ABBs:
Ready for public consultation
Adjustment / further piloting
needed
Governance (legacy)
Before e-SENS (in the LSP)
lack of long-term governance perspective, except for Open Peppol
Governance was considered withing the domain
projects-oriented approach -> no long term strategies and
organizations
Transparency only to for those within
e-SENS is an EU co-funded project under the ICT PSP
governance: scope
governance: finance
governance: operations
preferences on governance &
sustainability
deciding
17
funding
operating
Member States MS
EC
private
EC
EC
private
private
private sector
private
MS
private
To what extent is a European IT governance
structure for BB DSIs perceived as necessary?
In which way can your country voice a single coherent position
in eGovernment cross-border and cross-domain
interoperability functions/activities?
4% 4% 8%
12%
73%
18
21/05/2015
e-SENS WP3
Al rea dy achi eved
Requi res national coordi nation
wi th many i nvol ved organi zations
Requi res s ome l i ght national
coordi nation wi th a few i dentified i ndi vi dua l s
Currentl y i mpos s i bl e (pl ea se
expl ai n)
Al rea dy achi eved, Requi res
national coordi nation wi th
many i nvolved organizations
What are the preferred features of a
governance structure, for now and in the long
term?
Which principles should be preferred when a function/activity
will be governed at European level?
1.
2.
3.
4.
19
21/05/2015
Active involvement of MS in the process;
Clarity of responsibility and accountability for different tasks between the
stakeholders;
Keeping in mind the construction of a European interoperability ecosystem;
Ease of use by the administrations and businesses.
e-SENS WP3
What to jointly govern?
more efficient alignment efforts
aim of the ecosystem is to provide cross-domain services, enabled by BBs.
more efficient alignment efforts
aim of the ecosystem is to provide cross-domain services, enabled by BBs.
central "agora" to coordinate efforts
coordinate (here) = to align
relevant (local) decisions and share
knowledge proactively
with added value
High-Level value network of the eco-system for
domain public services (black) and cross-domain (blue)
4 Guiding principles
Four guidelines to add these values at low cost
• Subsidiarity
• Reciprocity
• Transparency
• Flexibility
added value from improved Knowledge Sharing
4 Guiding principles
Origins of these principles:
• EU & Australian Public Bodies Governance good
practices guides
• Permaculture
IT Governance of CEF BB DSIs
Non-paper on the IT Governance of CEF Building Block
Digital Service Infrastructures (DSIs)
Requirements for sustainability
In order to further lock in the benefits of addressing the critical success
factors and to make it sustainable, the processes and procedures that enable
the governance and linked implementation should ensure the following:
That the fundamental principles of the EU mandate are respected: Conferral,
Subsidiarity and Proportionality;
That core value of the EU are respected in both the approach to governance
and the resulting solutions: Openness, transparency and inclusiveness;
That the stakeholder representation and taking into consideration of their
needs is locked in.;
That the governance decisions are implemented.
Confirms both principles AND the use of BOMOS
Deloitte report on Cross-Border Services
Krechmer Criteria on Openness
●
Open Meeting: All stakeholders can participate in the development process
●
Consensus: All interests were discussed and agreement reached no domination.
●
Due Process: Balloting and an appeals procedure may be used for the definitive solution.
●
●
●
●
●
●
●
Open IPR: IPR (intellectual propertyrights) in relation to the standard are available for those
using it.
One World: Univocal definition of the standard, worldwide
Open Change: All changes are proposed and agreed in a forum supporting the five rights
above.
Open Documentation: Draft documents of the committee or other consultative groups and
completed documents about the standard are readily available for implementation and use
Open Interface: An open interface supports migration and makes it possible to market
private label versions. The standardized interfaces are not hidden or controlled.
Open use: There are objective conformity checks and mechanisms for implementation
testing and user evaluation.
Continuity in Support: Standards are supported until use of the standard ceases, instead of
support until the suppliers lose interest
BOMOS made it practical
BOMOS was not intended for:
●
an ecosystem of organisations
–
coordination more than governance
●
SBB’s → Open Peppol did a check
●
Detailed RFC processes → maybe ITIL??
●
–
(even) more (& good) service provisioning framework, less inter-organisation governance
–
close to no business development/market adoption focus
For every situation → translation for each context
–
●
trade-off between flexibility (~shopping list) and structure
in general OPENNESS is not garanteed, needs attention through the
entire process
–
what's open: participation? decision making? process? result?
E-SENS Objective in relation to BOMOS
1. Clear and efficient decision-making process
●
BOMOS2i page: 15 Decision making
2. Involvement LSP’s
●
BOMOS2i page: 15 participation
3. Stakeholders involvement
●
BOMOS2i page 15 stakeholder analysis (NEN)
(new) e-SENS Activity Model
Thank you!
What do you take away from these discussions?
Discussions
●
Contribute assessment model (back) to CAMSS
●
Interesting putting ethics at the heart of design
●
●
●
●
How to discuss reciprocity in public bodies and with
businesses?
Want to discuss in particular some of the changes we
made to BOMOS?
How to collaborate with other existing standardisation
structures (& their workflow/requirements)
Should there be a BOMOS-light, with less activities?
e-SENS
Electronic Simple European Networked Services
BOMOS in e-SENS
Thank you!
Xander van der Linde, Marijke Salters, Bertrand.Gré[email protected]