isa programme action 2.1 and action 2.14 e-sens pilot on the use of eira and the cartography tool...

ISA Programme Action 2.1 and Action 2.14

e-SENS pilot on the use of EIRA and the Cartography Tool

7-8 January 2015

Workshop

Time Topic08:30 Registration and coffee09:00 Welcome – Raul Abril, European Commission, ISA Programme09:10 Round table – All participants09:30 Overview of e-SENS WP6 – Klaus Vilstrup Pedersen, e-SENS10:00 Overview of the EIRA – Raul Abril, European Commission, ISA Programme11:00 Coffee break11:15 Work session on the EIRA – Max Stahlecker11:45 Lunch – all (MO34)13:00 Work session SAT eID part I (Design Solution Architecture use case)14:30 Coffee break14:45 Work session SAT eID part II (Design Solution Architecture use case)16:30 Coffee break16:45 Work session SAT eID part III (Design Solution Architecture use case)18:00 Closing and end19:00 Dinner (at own expense)

Workshop Agenda 7 January

Time Topic08:30 Registration and coffee09:00 Overview – Raul Abril, European Commission, ISA Programme09:10 Recap of previous day- summary of SAT results and link to Cartography session09:20 Coffee break09:30 Cartography Tool in practise – Debora Di Giacomo11:00 Coffee break11:15 Collecting data for the Cartography Tool12:15 Lunch13:30 Document Interoperability Solutions use case – work session15:00 Closing and end


Round table

Welcome

Rules and objectives

• Rules of engagement:• One-month period• e-SENS takes a leading role• EIA and CarTool support team in an active coaching role

• Objectives: pilot two use cases of the EIRA and CarToolo Design Solution Architecture Template (SAT) use case:

• eID• eSignature• eDelivery• eDocument

o Document Interoperability Solutions use case

7

E-SENS Pilot of EIRA and CarTool

Rules of engagement and objectives

E-SENS Pilot of EIRA and CarTool

8

Workshop objectives

1. Attain a common understanding about EIRA and CarTool

2. Plan the work

3. Get a lot of the work done already

Workshop on EIRA (1/2)

9

Expected Outcome

1. Update of the e-SENS eID SAT making it more consistent with the EIRA:

1. http://wiki.ds.unipi.gr/display/ESENS/SAT+-+e-ID

2. Add selected ABBs (and agreed definitions) that form the e-ID SAT to the wikipage

3. Add interoperability specifications, requirements, and agreed definitions

4. Add four views to structure the SAT

5. Update/complement the Archimate diagrams

http://wiki.ds.unipi.gr/display/ESENS/SAT+-+e-ID

Workshop on EIRA (2/2)

10

Expected Outcome

2. An aligned glossary of terms between the EIRA and the e-SENS reference architecture

1. http://wiki.ds.unipi.gr/display/ESENS/Glossary

2. Filling it the definition of ABBs into the glossary from the eID SAT

3. Adding common terminology (between EIRA and e-SENS) to the glossary in place

3. Preliminary evaluation (informal)

1. Validate the pilot evaluation criteria (see also evaluation form for the e-SENS pilot: https://ec.europa.eu/eusurvey/auth/login

2. Provide informal feedback (preliminary)

http://wiki.ds.unipi.gr/display/ESENS/Glossary

https://ec.europa.eu/eusurvey/auth/login

https://ec.europa.eu/eusurvey/auth/login

Pilot evaluation criteria

11

• Demonstrate that the usage of the EIRA and/or Cartography Tool provides value.

• The benefit(s) of the use case was documented and understood

• The outcome was in line with the expected benefit(s) of the use case

• Your perception of the EIRA’s and/or Cartography Tool’s value during the pilot was well understood

• Your perception of the EIRA’s and/or Cartography Tool’s value beyond the pilot was well understood

• Test EIRA and/or Cartography Tool use cases.

• The use case documentation (including its expected result) was available and, if needed, updated with the gained insight from the pilot

• Each use case step was documented and understood

• Sufficient resources, tools and support were provided to apply the use case

• Each use case step was performed

• The outcome was in line with the expected use case result

• All feedback with regard to the usability, enhancement or non-existence of the applied uses case, the EIRA and the CarTool has been captured and, if applicable, managed as change requests

• Further contribute to the enhancement of the EIRA and Cartography Tool based on the pilot experiences.

• The importance of the feedback on the EIRA and CarTool was understood

Overview of e-SENS WP6

Klaus Vilstrup Pedersen, e-SENS

Overview of the EIRA

Raul Abril, European Commission

Outline

14

03

02

04

The European Interoperability Reference Architecture (EIRA)

Context and Positioning of the EIRA

Objectives and use cases

Solution Architecture Templates

01

05 Summary

Overview

15


0302 0401

• A four-view reference architecture for delivering digital public services

• Aligns with the EIF and TOGAF• Defines minimal capabilities for

cross-sector and/or cross-border interoperability using the most salient Architecture Building Blocks

• Common terminology to achieve a minimum level of coordination

• Endorsed by the ISA Coordination group

05

The EIRA

16

Overview


0302 0401

Overview

Information System Development Reference

Architecture

National Reference Architecture

Other Reference Architectures

European Interoperability Architecture (EIA) – Reference Architecture

active structure element behaviour element

passive structure element

Archimate modelling notation legend:

05

The EIRA

17

Legal layer


0302 0401

Legal View

Public Policy

Non-binding Instrument

EU level

Binding Instrument

National level Sub-National level

Financial Resource Implementing Guideline

Approach Mandate

Binding Instrument Non-binding Instrument

Public Policy Cycle

Definition of Public Policy Objectives

Formulation of Public Policy Scenarios

Impact Assessment

Public Policy Implementation

Public Policy Evaluation





05

The EIRA

18

Organisational layer


0302 0401

Organisational View

Business Process

User

Public Service

Service Provider

Interoperability Service

Agreementaccepts

Organisational Structure

Business Information ExchangeBusiness

Information Entity

consumes

Business Transaction

Citizen

Public Administration

BusinessOrganisational

Policy

Business Rule

Service Delivery Modelis a source of Aggregated Public

Service

Basic Public Service

European

National

Sub-National

proposes

Public Policy

Organisational Procedure

offers

Interoperability Provider

Agreement

signs

signsis a source of

InteroperabilityCollaboration

Agreement

signs

signs

Service Catalogue

applies to

applies to

documentsBusiness

Process Model

documents


05

The EIRA

19

Semantic layer


0302 0401

Semantic View

Data Model

Identifier Schema

Controlled VocabularyReference Data

Data Entity

Metadata Management Policy

Business Information Entity

Data Policy

Licensing & Charging Policy

Security & Privacy Policy

Business Rule

RepresentationData

DataSet

applies to

Business Process ModelService Catalogue

DataSet Catalogue

documents

Public Policyinfluences

Code list





05

The EIRA

20

Technical View - Application


0302 0401

Public Service

Audit Service

Audit and Logging

Component

Logging Service

Access Management Component

Access Management

Service

Business Intelligence Component

Business Analytics Service

Business Reporting Service

Orchestration Service

Choreography Service

Business Process

Management Component

User

Human System

Data Transformation

Service

Data Transformation

Component

Data Validation Service

Data Validation Component

Data Exchange Service

Data Exchange Component

Forms Management

Service

Forms Management Component

Metadata Management Component

Metadata Management

Service

Content Management Component

Content Management

Service

Record Management Component

Records Management

Service

Human Interface Machine to Machine Interface

Collaboration Component

Messaging Service AudiovisualService

Document Management

Service

Service Discovery

Component

Service Discovery Service

Technical View - Application

Data Routing Service

Data Routing Component

Administration Component

Administration and Monitoring

Service

Lifecycle Management

Service

Partner Management Component

Partner Management

Service

Specification

Operational Procedure

Configuration Management Test

Component

Test ServiceTest Scenario

Test Report

Public Policy Data

e-Archiving component

e-Archiving service





05

The EIRA

21

Technical View - Infrastructure


0302 0401

Technical View - Infrastructure

Hosting Facility

Interoperable European System

Public Hosting FacilityPrivate Hosting

Facility

NetworkStorage

Processing

Public Network

Private Network

Hosting ServiceNetworking

Service

Secure Access

e-Signing Service

e-Signature Component

e-Signature Validation Service

Identity Management Component

Identity Management

Service

Trust Management Component

Trust Management

Service

e-Payment Component

e-PaymentService

Public Policy

Machine Translation

service

Machine Translation Component





05

The EIRA

22


0302 0401

The EIA Community on Joinup http://joinup.ec.europa.eu/asset/eia/description

05

http://joinup.ec.europa.eu/asset/eia/description

Outline

23

03

02




01

04 Solution Architecture Templates

05 Summary

Context of the EIRA

24

0302 0401


05

Alignment between EIF and EIRA

25

0302 0401


EIRAEIRAEIFGuidelinesFramework

05

Positioning the EIRA

26

0302 0401


EIRA provides a common core of context-neutral architecture building blocks

Domain Reference Architectures: e.g. Taxation Reference Architecture Framework

1. EIRA: context-neutral architecture building blocks (ABBs). Focused on interoperability.

2. Reference architecture for a domain: domain-specific architecture building blocks. Minimum agreements for taxation.

3. Solution architecture: specific solution designed using a domain-specific architecture

Core Reference Architecture: EIRA – minimal cross-sector interoperability

Solution Architectures: e.g. Automatic Information Exchange, FATCA, VIES, …

EIRA Core

SocialSecurity

HR

TAX

Environment

FATCA

VIES

05

Reference architecture

27

What does a reference architecture consist of?• Architecture principles: a minimum set of principles (e.g. EIF principles: subsidiarity,

proportionality, multilingualism, reusability, …)

• Architecture building blocks: a minimum set of ABBs that capture fundamental requirements cross-border/cross-sectoral solutions

• Public service reference model: generic public services (types)

• Common glossary: relevant definitions (multi-lingual) of core business information entities

• Business process reference models: generic, high-level, inter-organisational process models (choreography)

• Application service reference model: generic application services (e.g. tax calculation).

• Catalogue of standards and interoperability specifications: a minimum set of common standards structured according to the EIRA architecture building blocks

• data model: e.g. common reporting standard, XBRL, XML

• e-Signature: e.g. XaDES

• Federated authentication: SAML protocol

• Cartography of reusable SBBs: a minimal cartography of existing reusable solution building blocks (SBBs) described according to the EIRA architecture building blocks (ABBs).

0302 0401


05

Positioning the EIRA

28

0302 0401


EIRA’s positioning within the Enterprise Continuum

EIRA

Cartography Tool

05

Architectural patterns

29

0302 0401


Service consumption

An Interoperable European System contains:

• One or more software components providing services that are public service neutral

• One or several interfaces which are public service neutral


Choreography service

IES service

Machine to Machine Interface

Human Interface

DSI service 1

DSI service ...

DSI service 2

DSI service n

IES service 1

IES service ...

IES service 2

IES service n

Service consumption

Service provisioningService delivery

05

Architectural patterns

30

0302 0401


Service provisioning

An Interoperable European System service consumes in a public service sensitive way:• One or more

Orchestration services• None, one or more DSI

services• None, one or more IES

services• One or more

Choreography services specific to the supported public service


Choreography service

IES service

Machine to Machine Interface

Human Interface

DSI service 1

DSI service ...

DSI service 2

DSI service n

IES service 1

IES service ...

IES service 2

IES service n

Service consumption

Service provisioningService delivery

05

Outline

31

03

02




01


05 Summary

Objectives of the EIRA

32

0302 0401


05

Designing

Assessing

Discovering and Reusing

Communicating and Sharing

Accelerate the design of systems that support the delivery of interoperable digital public services (across borders and sectors).

Provide a reference model for comparing existing architectures in different policy domains and thematic areas, to identify focal points for convergence and reuse.

Ease the discovery and reuse of interoperability solutions through the Cartography – Cart in Joinup website.

Help documenting the most salient interoperability elements of complex systems and facilitate the sharing of reusable solutions.

Expected benefits of the EIRA

Use-cases overview

33

0302 0401


05

Discovering and Reusing

Search for interoperability solutions

EIRA Cart

Design solution architecture (templates)

Design reference architectures

Designing

Assess impact of ICT

Communicating and Sharing

Document interoperability solutions

Compare reference architectures

Compare solution architectures

Manage portfolio

Rationalise portfolio

Assessing

Create portfolio

EIRA and CarTool use-cases

Outline

34

03

02




01


05 Summary

Definition

35

• A Solution Architecture Template (SAT) is a specification containing a sub-set of ABBs of the EIRA. It focuses on the most salient building blocks (including IOP requirements defined in terms of IOP specs) needed to build an interoperable solution addressing a particular interoperability need.

• A SAT consists of:• Goal and description• A set of EIRA ABBs• A set of IOP specifications & recommendations on ABBs -> Session II:

Interoperability specifications and recommendations• A visual Archimate diagram


0302 0401 05

What is a Solution Architecture Template?

Spatial positioning

36


0302 0401 05

EIRA

Cartography Tool


Position within the Enterprise Continuum

Temporal positioning

37


0302 0401 05

Reference Architecture


Solution Architecture

Position within the ADM

Creation and usageof SATs

38


0302 0401 05

If needed, per each building block, the user adds a set of additional interoperability requirements that are needed to address the specific interoperability need (e.g. specific protocols to be used by an application). Solution building blocks might be recommended for the implementation of the architecture building bocks of the solution template.

The user consults the views of the EIRA to define the scope of the architecture to be designed, by identifying the architectural building blocks that are needed to address the interoperability need.

Based on the identified architectural building blocks, the user can design an architectural solution template (e.g. in Archimate format). The solution template includes the needed sub-set of architectural building blocks of the EIRA.

The architectural solution template is shared with the involved stakeholders (e.g. by sharing or uploading the Archimate diagram of the solution template).

Step 1: Identify needed EIRA BBs

Step 2: Create blueprint of solution

template

Step 3 : Add Interoperability

requirements and solution BBs

Step 4: Share solution template

Creation of SATs

Creation and usageof SATs

39


0302 0401 05

TextText

TextText

The user consults the architectural solution template, via the Cartography tool, related to the particular interoperability need he/she wants to address.

The user includes the solution building blocks identified in the previous step (i.e. step 2) in the system’s solution architecture, in order to address initial interoperability need.

Step 1: Consultation of the solution

template

Step 3: Design solution

Step 2: Mapping with existing solutions

The user maps the solution building blocks of its current IT landscape to the template. For each building block (BB) in the solution template:• If an existing solution of the user’s IT landscape is compliant with the

interoperability requirements of the BB, the user maps the solution with the BB.• If no existing solutions are compliant with the interoperability requirements of the

BB, the user searches in the Cartography for a re-usable solution. If a solution is found, the user maps the discovered solution to the BB.

• If no compliant solutions are found on the Cartography, the user initiates a project to develop a new solution BB compliant with the interoperability requirements. The user maps the solution to be developed to the BB.

Usage of SATs

Outline

40

03

02




01


05 Summary

Summary

41

1. The European Interoperability Reference Architecture (EIRA) is an application of Enterprise Architecture with a focus on interoperability in the public sector.

2. The European Interoperability Reference Architecture is based on the Service Oriented Architecture style and uses the Archimate modelling notation.

3. EIRA implements the European Interoperability Framework (EIF). There is a full alignment between the EIRA and the EIF.

4. Each view of the European Interoperability Reference Architecture is defined in terms of the interoperability aspects that are supported.

5. Views of the European Interoperability Reference Architecture are linked through designated entry and exit building blocks following a layered approach.

6. The ambition of the EIRA is to provide real value to the European public administration, both at the Member States level as to the European Institutions level. The EIRA is developed in collaboration with the Member States.

Summary

0302 0401 05

Work session on the EIRA

Max Stahlecker

Work session on EIRA

43

Brown paper sessionPut your name on each sticky note.

Form groups of 3 persons.

Discuss the relationship between ABBs in e-SENS and EIRA.• What are the top-3 most relevant ABBs to e-SENS (e-SENS eID SAT)?• How do they relate to EIRA ABBs?• Which additional ABBs in EIRA are relevant to e-SENS?

Update the e-SENS Glossary

http://wiki.ds.unipi.gr/display/ESENS/Glossary• Which ABBs could be added to the Glossary?• How can the e-SENS Glossary be best exploited?• What are possible benefits / drawbacks of a common set of ABBs?

Work session

Design a solution architecturetemplate for eID

Outline

45

03

02

04

Objectives of the work session

Part I: Agreeing on the scope of the eID SAT and target audience

Part II: Interoperability specifications for the eID SAT

Part III: Updating/complementing Archimate diagrams for the eID SAT

01

Objectives of the worksession

46

1. Update of the e-SENS eID Solution Architecture Template (SAT) making it more consistent with the EIRA:

1. Part I: Agreeing on the scope, target audience and stakeholders of the eID SAT• Add selected ABBs (and agreed definitions) that form the e-ID SAT to

the wikipage

2. Part II: Interoperability specifications and recommendations• Add interoperability specifications and recommendations

3. Part III: Updating/complementing Archimate diagrams• Add four views to structure the SAT• Update/complement the Archimate diagrams


0302 0401

Expected Outcomes

Outline

47

03

02

04





01

48

Exercise I: Which ABBs are the most-salient?• Define and agree on target audience and stakeholders• Identify a list a candidate ABBs to be included within the Solution Architecture

Template• Work document

• https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.swo3jgnyv8cm and https://docs.google.com/spreadsheets/d/1Hh_v-2k153IfGwTZ0aQwbDRZofDtfRcaA_6itz25JeM/edit?usp=sharing

• Expected results• Agreed definition, target audience, stakeholders and list of ABBs

Part I

0302 0401Agreeing on the scope of theSAT and target audience

https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.swo3jgnyv8cm



https://docs.google.com/spreadsheets/d/1Hh_v-2k153IfGwTZ0aQwbDRZofDtfRcaA_6itz25JeM/edit?usp=sharing

https://docs.google.com/spreadsheets/d/1Hh_v-2k153IfGwTZ0aQwbDRZofDtfRcaA_6itz25JeM/edit?usp=sharing

Outline

49

03

02

04





01

50

1. Describe a standard or specification helping at interoperability of an architecture building block.

2. An interoperability specification is defined in terms of existing standards and/or specifications.

3. An interoperability specification is relevant to one or more interoperability levels (e.g. ISO 27001 (organisational, semantic, technical) or SAML (semantic, technical)).

4. An interoperability specification can be linked to no, one or more architecture building blocks.

Part II

0302 0401Interoperability specificationsfor the eID SAT

What are interoperability specifications

51

The EIRA uses interoperability specifications to make solution building blocks more interoperable. Within the EIRA a minimum set of interoperability specifications can be linked to an architecture building block. This set consists of the most salient and cross-sector interoperability specifications to which an architecture building block’s solution building block needs to adhere to.

By focusing only on the most salient and cross-sector interoperability specifications, the EIRA itself complies with the 1st principle of the European Interoperability Framework (EIF): Subsidiarity and proportionality. Similar to “the EU opting for solutions that leave the greatest possible freedom to Member States” (source: EIF), interoperability specifications shall as well leave the greatest possible freedom to Member States when designing Interoperable European Solutions.

Part II


Why use interoperability specifications?

53

• Find some interoperability specifications that are relevant to the ABBs selected previously and explain why? How is it link to the EIF principle(s)?

• How do they compare to the requirements on the wiki? Are they complementary?

• Work document• https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd

We-_qyalenDseQQ/edit#heading=h.o68matyt3grx • Expected results

• Interoperability specifications structured according to• related ABB(s)• related SAT(s)• related EIF principle(s)• related interoperability area(s)

Part II


Exercise II : identify interoperability specifications

https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.o68matyt3grx

https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.o68matyt3grx

Outline

54

03

02

04





01

55

• How do the Business, Application and Information view compare to the EIRA layers?

• Can we put the e-SENS building blocks on the EIRA layers?• The e-SENS BB have no indication on whether it is active, passive or

behavioural. Can we add that?• Work document

• https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0

• Expected results• Updated diagrams

Part III

0302 0401Updating /completingArchimate diagrams

Aligning EIRA and eSENS SA(T) blueprints

https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0

https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMdWe-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0

56

Part III

0302 0401

Business Process

Public Service

Business Information Exchange



Identity claim creation Identity claim verification

Updating/completingArchimate diagrams

Organisation / business view

57

Part III

0302 0401

Business Process

Public Service

Business Information Exchange



Identity claim creation Identity claim verification

Updating/completingArchimate diagrams

Organisation / business view

Conclusion

Next steps:• Incorporate EIRA into the the eSENS

glossary• Finalise the eID SAT• Align eSENS Solution Architecture

Templates (SATs) with EIRA:• eID• eSignature• eDelivery• eDocument

Preliminary evaluation:• Does the alignment of the e-SENS

SATs with EIRA provide added value?o Increased consistencyo Cross-domain coordination and

interoperabilityo Visibility

• Can EIRA provide a common terminology?

• Are the pilot evaluation criteria still relevant?

Design Solution Architecture Templates use case

58

End of day 1

Social dinner @ 19:00Lune de Miele – Rue Jules van Praet, Brussels 1000Metro BourseTaxi Place St Gery

60

Time Topic08:30 Registration and coffee09:00 Overview – Raul Abril, European Commission, ISA Programme09:10 Recap of previous day- summary of SAT results and link to Cartography session09:20 Coffee break09:30 Cartography Tool in practise – Debora Di Giacomo11:00 Coffee break11:15 Collecting data for the Cartography Tool12:15 Lunch13:30 Document Interoperability Solutions use case – work session15:00 Closing and end


61

Contact usProject Officers

[email protected]@[email protected]

Project [email protected]

For more information

Cartography toolEuropean Interoperability Cartography

EIRAEuropean Interoperability Reference Architecture

EIA Joinup community https://joinup.ec.europa.eu/asset/eia/description

EIA project collaborative space https://webgate.ec.europa.eu/CITnet/confluence/display/EIA/EI

A+Home

ISA website http://ec.europa.eu/isa/index_en.htm

ISA FAQ http://ec.europa.eu/isa/faq/faq_en.htm

https://joinup.ec.europa.eu/asset/eia/description

https://webgate.ec.europa.eu/CITnet/confluence/display/EIA/EIA+Home

https://webgate.ec.europa.eu/CITnet/confluence/display/EIA/EIA+Home

http://ec.europa.eu/isa/index_en.htm

http://ec.europa.eu/isa/faq/faq_en.htm

Practical details

Practical information (lost in Brussels?)Zakaria Arrassi: +32 498 54 98 02Stijn Goedertier: +32 496 10 53 90Max Stahlecker: +32 491 62 17 95 Restaurant Time : 19:00Name: Lune de Miele Rue Jules van Praet, Brussels 1000 (+32 2 513 9181)Access: Metro De Brouckère (5mn walking)

Tram Bourse (2mn walking)Taxi Place St Gery

EmergenciesNumber : 112

isa programme action 2.1 and action 2.14 e-sens pilot on the use of eira and the cartography tool...

Documents