ISA - e-SENS workshop on EIRA and CarTool pilot - Joinup

e-SENS pilot on the use of

EIRA and the Cartography

Tool

ISA Programme Action 2.1 and Action 2.14

7-8 January 2015

Workshop

Workshop

Agenda 7 January

Time Topic

08:30

09:00

09:10

09:30

10:00

11:00

11:15

11:45

13:00

14:30

14:45

16:30

16:45

18:00

19:00

Registration and coffee

Welcome – Raul Abril, European Commission, ISA Programme

Round table – All participants

Overview of e-SENS WP6 – Klaus Vilstrup Pedersen, e-SENS

Overview of the EIRA – Raul Abril, European Commission, ISA Programme

Coffee break

Work session on the EIRA – Max Stahlecker

Lunch – all (MO34)

Work session SAT eID part I (Design Solution Architecture use case)

Coffee break

Work session SAT eID part II (Design Solution Architecture use case)

Coffee break

Work session SAT eID part III (Design Solution Architecture use case)

Closing and end

Dinner (at own expense)

Workshop


Time Topic

08:30

09:00

09:10

09:20

09:30

11:00

11:15

12:15

13:30

15:00


Overview – Raul Abril, European Commission, ISA Programme

Recap of previous day- summary of SAT results and link to Cartography session

Coffee break

Cartography Tool in practise – Debora Di Giacomo

Coffee break

Collecting data for the Cartography Tool

Lunch

Document Interoperability Solutions use case – work session

Closing and end

Round table

Welcome

Rules and objectives

E-SENS Pilot of EIRA and CarTool

Rules of engagement 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 CarTool o 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

Workshop objectives

1. Attain a common understanding about EIRA and CarTool

2. Plan the work

3. Get a lot of the work done already

8

Workshop on EIRA (1/2)

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

9

Workshop on EIRA (2/2)

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)

10

Pilot evaluation criteria

• 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

11

Overview of e-SENS WP6

Klaus Vilstrup Pedersen, e-SENS

Overview of the EIRA

Raul Abril, European Commission

Outline

01 The European Interoperability Reference Architecture (EIRA)

02 Context and Positioning of the EIRA

03 Objectives and use cases

04 Solution Architecture Templates

05 Summary

14

Overview

• 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

01 02 03 04 05

The European Interoperability

Reference Architecture (EIRA)

15

The EIRA

Overview

European Interoperability Architecture (EIA) – Reference Architecture

Archimate modelling notation legend: active structure element behaviour element passive structure element

Overview

Information System

Development Reference

Architecture

National Reference

Architecture

Other Reference

Architectures

01 02 03 04 05



16

The EIRA

01 02 03 04 05



Legal layer



Legal View

Public Policy Cycle

Definition of Public

Policy Objectives

Formulation of Public

Policy Scenarios

Impact Assessment

Public Policy

Implementation

Public Policy

Evaluation

Approach

Public Policy

Mandate

EU level National level Sub-National level

Binding Instrument

Non-binding

Instrument

Binding Instrument

Non-binding

Instrument

Financial Resource

Implementing

Guideline

17

The EIRA

01 02 03 04 05



Organisational layer

Archimate modelling notation legend:

Organisational View

Organisational

Policy is a source of

Organisational

Procedure is a source of

Business Rule

Organisational

Structure

Public Policy

Business

Process Model

Interoperability

Collaboration

Agreement

Citizen

Service

Catalogue documents

User signs signs

European

Business Public

Administration accepts

Interoperability

Service

Agreement proposes consumes offers

Service Delivery

Model

National

Service

Provider signs

Aggregated Public

Service

Sub-National signs

Interoperability

Provider

Agreement

Public Service documents

Business Process

Business Information Exchange

Business Transaction

Basic Public Service

Business

Information

Entity applies to applies to

18

The EIRA

01 02 03 04 05



Semantic layer



Semantic View

Public Policy influences

Data Policy applies to

Security & Privacy

Policy

Business

Information Entity

Licensing &

Charging Policy

Business Rule Service Catalogue

Business Process

Model

Representation

Data documents

DataSet DataSet Catalogue

Data Entity

Data Model Reference Data

Metadata

Management Policy

Identifier Schema

Controlled

Vocabulary

Code list

19

The EIRA

01 02 03 04 05



Technical View - Application


Archimate modelling notation legend: active structure element

Technical View - Application behaviour element passive structure element

User

Public Policy

Public Service

Human System

Data

Specification

Operational

Procedure

Configuration

Management

Test Service

Test

Component

Test Scenario

Test Report

Human Interface

Machine to

Machine Interface

Service Discovery

Service

Service

Discovery

Component

Choreography

Service

Orchestration

Service

Business

Process

Management

Component

Messaging Service

Collaboration

Component

Audiovisual

Service

Data Routing

Service

Data Routing

Component

Data

Transformation

Service

Data

Transformation

Component

Data Validation

Service

Data Validation

Component

Data Exchange

Service

Data Exchange

Component

Business Analytics

Service

Business

Intelligence

Component

Business

Reporting Service

Forms

Management

Service

Forms

Management

Component

Records

Management

Service

Record

Management

Component

Document

Management

Service

Content

Management

Service

Content

Management

Component

Metadata

Management

Service

Metadata

Management

Component e-Archiving service e-Archiving component

Administration and Monitoring

Service

Lifecycle

Management

Service

Administration

Component

Partner

Management

Service

Partner

Management

Component

Access

Management

Service

Access

Management

Component

Audit

Service

Logging Service

Audit and

Logging

Component

20

The EIRA

Technical View - Infrastructure



Technical View - Infrastructure

Interoperable

European

System

Public Policy e-Signing Service e-Signature

Validation Service e-Signature

Component

Identity

Management

Service

Identity

Management

Component

Trust

Management

Service

Trust

Management

Component e-Payment

Service e-Payment

Component

Machine

Translation service

Machine

Translation

Component

Public Network

Networking

Service

Network

Hosting Service

Hosting Facility

Secure Access

Storage

Processing

Private Network

Private Hosting

Facility

Public Hosting Facility

01 02 03 04 05



21

The EIRA

01 02 03 04 05



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

22

Outline

01 The European Interoperability Reference Architecture (EIRA)

02 Context and Positioning of the EIRA



05 Summary

23

Context of the EIRA

01 02 03 04

Context and Positioning of the EIRA

05

European Interoperability Strategy (EIS)

Governance and strategy

European Interoperability Framework (EIF)

Framework and principles

European Interoperability Reference Architecture (EIRA)

Guidelines and Implementation

24

Alignment between

EIF and EIRA

EIF

Framework

01 02 03 04


05

EIRA

Guidelines

25

Positioning the EIRA

01 02 03 04


05

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

Solution Architectures: e.g.

Automatic Information Exchange,

FATCA, VIES, …

Domain Reference Architectures: e.g. Taxation Reference

Architecture Framework

Core Reference Architecture:

EIRA – minimal cross-sector interoperability

EIRA

Core

1.

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

2.

Reference architecture for a domain: domainspecific architecture building blocks. Minimum agreements for taxation.

3.

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

26

Reference architecture

01 02 03 04


05

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).

27

Positioning the EIRA

01 02 03 04


05

EIRA’s positioning within the Enterprise Continuum

28

Architectural patterns

Service consumption

Orchestration Service 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

DSI service 1 DSI service 2

DSI service ...

DSI service n

IES service 1 IES service 2

IES service ...

IES service n

Choreography service

IES service

01 02 03 04


05

Machine to Machine

Interface

Human Interface

29

Architectural patterns

Service provisioning

Orchestration Service

DSI service 1 DSI service 2

DSI service ...

DSI service n

IES service 1 IES service 2

IES service ...

IES service n

Choreography service

IES service

01 02 03 04


05

Machine to Machine

Interface

Human Interface

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

30

Outline



03 Objectives and use cases


05 Summary

31

Objectives of the EIRA

01 02 03 04

Objectives and use cases

05

Expected benefits of the EIRA

Designing

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

Assessing

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

Communicating and Sharing

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

Discovering and Reusing

Ease the discovery and reuse of interoperability solutions through the

Cartography – Cart in Joinup website.

32

Use-cases overview

01 02 03 04

Objectives and use cases

05

EIRA and CarTool use-cases

Designing

Design solution architecture

(templates)

Design reference architectures

Create portfolio

Communicating and

Sharing

Assess impact of ICT

Document interoperability solutions

EIRA Cart

Assessing

Compare reference architectures

Compare solution architectures

Rationalise portfolio

Manage portfolio

Discovering and

Reusing

Search for interoperability solutions

33

Outline




04 Solution Architecture Templates

05 Summary

34

Definition

01 02 03 04 05

Solution Architecture Templates

What is a Solution Architecture Template?

• 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

35

Spatial positioning

Position within the Enterprise Continuum

01 02 03 04 05


Solution Architecture Templates

36

Temporal positioning

Position within the ADM

01 02 03 04 05


Reference Architecture

Solution Architecture

Templates

Solution Architecture

37

Creation and usage of SATs

01 02 03 04 05


Creation of SATs

Step 1: Identify needed EIRA BBs

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.

Step 2: Create blueprint of solution template

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.

Step 3 :

Add Interoperability requirements and solution BBs

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.

Step 4: Share solution template

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

38

Creation and usage of SATs

01 02 03 04 05


Usage of SATs

Step 1: Consultation of the solution template

Step 2: Mapping with existing solutions

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

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.

Step 3: Design solution

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.

39

Outline





05 Summary

40

Summary

01 02

Summary

03 04 05

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.

41

Work session on the EIRA

Max Stahlecker

Work session on EIRA

Brown paper session

Put 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?

43

Work session

Design a solution architecture template for eID

Outline

01 Objectives of the work session

02

03

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

Part II: Interoperability specifications for the eID SAT

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

45

Objectives of the work session

01 02 03

Objectives of the work session

04

Expected Outcomes

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

46

Outline

01 Objectives of the work session

02

03

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



47

Agreeing on the scope of the

SAT and target audience

01

Part I

02 03 04

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/1Aoc29agmBLgcOVVR97kTw0ocipMd

We-_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

48

Outline


02

03

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

Part II: Interoperability specifications for the eID SAT


49

Interoperability specifications for the eID SAT

01

Part II

02 03 04

What are interoperability specifications

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.

50


01

Part II

02 03 04

Why use interoperability specifications?

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.

51


01

Part II

02 03 04

Exercise II : identify interoperability specifications

• 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


We-_qyalenDseQQ/edit#heading=h.o68matyt3grx


• Interoperability specifications structured according to

• related ABB(s)

• related SAT(s)

• related EIF principle(s)

• related interoperability area(s)

53

Outline


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

03

04


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

54

Updating /completing

Archimate diagrams

01

Part III

02 03 04

Aligning EIRA and eSENS SA(T) blueprints

• 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


We-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0


• Updated diagrams

55

Updating/completing


Organisation / business view

01

Part III

02 03 04

Identity claim creation

Public Service

Business Process



Basic Public Service

Identity claim verification

56

Updating/completing


Organisation / business view

Public Service Basic Public Service

Business Process



Identity claim creation Identity claim verification

01

Part III

02 03 04

57

Conclusion

Design Solution Architecture Templates use case

Preliminary evaluation:

• Does the alignment of the e-SENS

SATs with EIRA provide added value?

o Increased consistency o Cross-domain coordination and interoperability o Visibility

• Can EIRA provide a common terminology?

• Are the pilot evaluation criteria still relevant?

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

58

End of day 1

Social dinner @ 19:00

Lune de Miele – Rue Jules van Praet,

Brussels 1000

Metro Bourse

Taxi Place St Gery

Workshop


Time Topic

08:30

09:00

09:10

09:20

09:30

11:00

11:15

12:15

13:30

15:00


Overview – Raul Abril, European Commission, ISA Programme

Recap of previous day- summary of SAT results and link to Cartography session

Coffee break

Cartography Tool in practise – Debora Di Giacomo

Coffee break

Collecting data for the Cartography Tool

Lunch

Document Interoperability Solutions use case – work session

Closing and end

60

Contact us

Project Officers

Raul.Abril@ec.europa.eu

Suzanne.Wigard@ec.europa.eu

Hans.Vanderbeke@ec.europa.eu

Project team eia@be.pwc.com

EIRA

European Interoperability Reference Architecture

Cartography tool

European Interoperability Cartography

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

ISA website https://webgate.ec.europa.eu/CITnet/confluence/display/EIA/EI

A+Home http://ec.europa.eu/isa/index_en.htm

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

61

Practical details

Practical information (lost in Brussels?)

Zakaria Arrassi: +32 498 54 98 02

Stijn Goedertier: +32 496 10 53 90

Max Stahlecker: +32 491 62 17 95

Restaurant

Time : 19:00

Name: 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

Emergencies

Number : 112

ISA - e-SENS workshop on EIRA and CarTool pilot - Joinup

EIRA

Cartography tool

Related documents

Products

Support

ISA - e-SENS workshop on EIRA and CarTool pilot - Joinup

EIRA

Cartography tool

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib