Session 1. ISA-the baseline for e-SENS interoperability architecture, Raul-Mario-Abril-Jimenez

Interoperability Solutions for
European Public
Administrations
Luxembourg
7th November 2014
Dr. Raul M. Abril
Raul-Mario.Abril-Jimenez@ec.europa.eu
EIRA and EIC update

Overall view
Click to edit Master title style
Semantics 1.1 2.15
Monitoring activities (M)
Programme 5.1
Accompanying Measures (A)
Community
building
4.2.1 4.2.2
Communication
Activities
Supporting Instruments to European Public
EIS 5.2
Sharing & reuse 4.2.5
IMM 4.1.2
CAMMS 2.2
4.1.1
Administrations (PA)
TES 2.14 NIFO 4.2.3
EIA 2.1
EFIR 4.2.4
CIRCABC 2.5
Support the effective Implementation
of EU legislations (L)
PSI
CISE 1.16
ECI 1.12
State Aid 1.11
IMI 1.10
INSPIRE 1.17
EULF 2.13
eProcurement
1.6 1.7 2.11
ELI 1.21
ICT Impact
Assessments
3.1
Key Interoperability Enablers (I)
Decision Support
Enablers
2.6
Networks 2.4
Machine
Translation
2.8
Information exchange 1.8 1.13 1.20
Sources of trusted information 1.2 2.9
eSignature & eIdentification
1.4 1.5 1.9 1.18 2.3
2
Source: ISA Legal Decision Art. 1, 2, 3 , Kurt Salmon analysis
ISA portfolio

Objectives of the EIA action
3
Designing
Assessing
Communicating
and Sharing
Discovering and
Reusing
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.
Help documenting the most salient interoperability elements of complex systems
and facilitate the sharing of reusable solutions.
Ease the discovery and reuse of interoperability solutions through the European
Interoperability Cartography – EICart in Joinup website.

Main work products of
the EIA action
A mapping of solutions to the Building
Blocks of the EIRA.
EIRA
European Interoperability Reference Architecture
A four-view reference architecture for
delivering digital public services
(across borders and sectors).
EICart
European Interoperability Cartography
4

Legal view
5
Public Policy Implementation Public Policy Development Enablers Instruments
Legal Requirements
Operational Enablers
Legal View
Public Policy
Non-binding
Instrument
EU level
Binding Instrument
National level Sub-National level
Financial Resource
Implementing
Guideline
Approach Mandate
Legal Constraints
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

Organisational view
6
Organisational View
Organisational Enablers
Interoperability Service Provider
Service Agreement
Business Process
User
Public Service
Organisational
Structure
Business Information Exchange
Business Information
Entity
Business Transaction
Citizen
Organisations
Public
Administration
Business
Organisational Policy
Business Rule
Service Delivery
Model
Aggregated Public Service
Basic Public Service
European
National
Sub-National
proposes signs
is a source of
accepts
Public Policy
Organisational
Procedure
Interoperability
Provider Agreement
applies to
consumes offers signs
is a source of
applies to
Interoperability
Collaboration
Agreement
signs
signs
Service Catalogue
documents
Business Process
Model
documents

Semantic view
7
Semantic View
Metadata
Data Model
Identifier Schema
Controlled Reference Data Vocabulary
Data Entity
Metadata
Management Policy
applies to
Business
Information Entity
Data Policy
Licensing & Charging
Policy
Security & Privacy
Policy
Business Rule
Representation
Data
DataSet
Business Process
Model
Service Catalogue
DataSet Catalogue
documents
Public Policy
influences
Code list

Technical view – Application
Access Management
Service
Management
Component
Logging Service
8
Interoperable European System
Processing Enablers
Presentation and Access Enablers
Data Source Enablers
Application Security Enablers
Public Service
Audit
Service
Access
Audit and Logging
Component
Human System
Workflow Enablers
User
Service Discovery
Service
Test Service
Mediation Enablers Decision Support Enablers
Business
Intelligence
Component
Business Analytics
Service
Business Reporting
Service
Orchestration
Service
Choreography
Service
Business Process
Management
Component
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
Service
Metadata
Management
Component
Content
Management
Component
Content
Management
Service
Records
Management
Service
Record
Management
Component
Human Interface
Machine to
Machine Interface
Collaboration Enablers
Collaboration
Component
Messaging Service
Audiovisual
Service
Document
Management
Service
Discovery Enablers
Service Discovery
Component
Technical View - Application
Data Routing Service
Data Routing
Component
Administration Enablers
Administration and
Monitoring Service
Lifecycle
Management
Administration
Component
Service
Partner
Management
Service
Partner
Management
Component
Documentation Enablers
Specification
Operational
Procedure
Configuration
Management
Test Enablers
Test Component
Test Scenario
Test Report
Public Policy
Data
e-Archiving service
e-Archiving
component

Technical view – Infrastructure
9
Technical View - Infrastructure
Digital Services Infrastructure
Infrastructure Security Enablers
e-Signature
Validation Service
Hosting and Networking Services Infrastructure
Trust Management
Public Policy
Hosting Facility
Interoperable
European
System
Identity
Management
Service
Network
Storage
Processing
Service
e-Payment
Service
Public Private Hosting Facility Hosting Facility
Public Network
Private Network
Hosting Service
Networking
Service
Secure Access
e-Signing Service
e-Signature
Component
Identity
Management
Component
Trust
Management
Component
e-Payment
Component
Machine Translation
service
Machine
Translation
Component

Organisational View
Service Agreement
The major business transactions2 supported by a TES answer the
business needs expressed in the legal basis and reflect the business
purpose of a TES.
The identification of TES supporting specific business needs
can therefore be based on the business transactions
supported.
Examples of business transactions identified:
• Alerts for Crisis management needs
• Electronic data entry for Data collection, monitoring and
reporting needs
• Exchange of requests for information for Administrative
cooperation needs
10
EIC. Identification of TES based
on the EIRA Organisational view
2 Atomic
unit of interaction between two or more public administrations, businesses or citizens, EIRA v 2.10
Business Process
User
Public Service
Organisational
Structure
Entity
Citizen
Organisations
Public
Administration
Business
Business Rule
Service Delivery
Model
European
National
Sub-National
proposes signs
is a source of
accepts
Public Policy
Organisational
Procedure
Interoperability
Provider Agreement
applies to
is a source of
applies to
Interoperability
Collaboration
Agreement
signs
signs
Service Catalogue
documents
Business Process
Model
documents

Trust Management
Storage
Processing
Public Policy
R Reusable sytems/components
DP Development planned
11
EIC. Reuse of infrastructure services
Seven reusable infrastructure services were identified:
• Two private networks – CCN (DG TAXUD) and sTESTA (DG DIGIT);
• One identity management service – ECAS (DG DGIT);
• Two e-signing services – ESSI (DG DIGIT) and DSS (DG MARKT);
• One digital signature certificates validation service – TLManager (DG MARKT);
• One text translation service – MT@EC (DG DIGIT).
e-Signature
Validation Service
Hosting Facility
Interoperable
European
System
Identity
Management
Service
Network
Service
e-Payment
Service
Public Network
Private Network
Hosting Service
Networking
Service
Secure Access
e-Signing Service
e-Signature
Component
Identity
Management
Component
Trust
Management
Component
e-Payment
Component
Machine Translation
service
Machine
Translation
Component
Hosting and Networking
R
enablers sTESTA
O
Private Network
Geant
O
CCN
O
O
R R
E-Payment Service
BRIS
D
DP
FNS
O
Identity Management
service
E-Signing Service Validate digital signature
certificates
P
DSS TLManager
O
R
FNS
O
Text Translation
SURVEILLANCE 2
O
ECRIS
O
ESBR
D
FNS
O
TRIS
O
eJustice Portal
O
MT@EC
R
O
IMI
O
ICSMS
O
Digital Services
Infrastructure
ECAS
STORK
O
ESSI
O
R
R
S
D
P
O
Study
Development
Pilot
Operational
Internal Market
Anti-Fraud Policy
Taxation and customs union
Research
Cross-Sector
Multi-Sector
Caption:
R Reusable services

Use cases of the EIA action
Assessing
Compare reference architectures
Compare solution architectures
Rationalise portfolio
Manage portfolio
Discovering and Reusing
Search for interoperability solutions
EIRA Cart
Designing
Design solution architectures
Design reference architectures
Create portfolio
Communicating and Sharing
Structure the architectural implications
of policy or thematic domains (to the extent
of the views of the EIRA)
Document interoperability solutions
DO NOT DISTRIBUTE FURTHER 12

DO NOT DISTRIBUTE FURTHER
Scenario 1 – Context
.
Marco Rinaldi is an Enterprise Architect, working in the social
security sector for a public administration in Italy. In order to be
compliant with a new EU directive, his organisation has the
mandate to build a new information system that enables
automatic exchange of social security information with the
European Commission and other public administrations in
Europe.
FICTIONAL
13

Scenario 1 – Use cases
CHALLENGE
How to ensure interoperability between a national system and the systems of the EC and of other MSs.
EIA in PRACTICE
Marco can use the technical view - application
of the EIRA to find the BBs that are relevant for
interoperable message exchange.
Design solution architecture Search for interoperability solutions
KEY BENEFITS
Marco can use the Cartography tool to find
reusable solutions for the BBs he needs.
• Strong focus on cross-border interoperability from the outset
• Faster access to reusable solutions
• Alignment to a common reference model

Scenario 2 – Context
.
Christine Dupont is working for DG AGRI, European Commission.
Due to a change in the business processes supporting the
implementation of rural development policies, her DG has
launched an assessment of the current application landscape to
evaluate the impact of the change. The DG has found out that
there is an overlap between the functionalities of different
systems, and the cost of implementing a change are significant.
Christine has been asked to evaluate a strategy for rationalising
application landscape and implement the new business process.
FICTIONAL
15

Scenario 2 – Use cases
PROBLEM
How to rationalise the application landscape to support efficient business process implementation.
EIA in PRACTICE
Christine can use the
organisational view of the EIRA
to organise the key business
processes and related business
rules, and explain this
relationship to stakeholders.
Structure the architectural
implications of a policy
KEY BENEFITS
Christine can use the EIRA to
understand her DG’s
architecture and identify
missing BBs.
Compare reference architectures
Christine can map the current
applications to the EIRA BBs,
and plan which ones have to be
dismissed, merged or replaced.
• Structured communication with stakeholders
• Accelerated assessment of architectures
• Simplified decision-making process for application portfolio rationalisation
Rationalise portfolio

Join ISA initiatives at: http://ec.europa.eu/isa/index_en.htm
and @ http://joinup.ec.europa.eu
http://goo.gl/eK1EY @SEMICeu http://joinup.ec.europa.eu
CORE
PUBLIC
SERVICE
VOCABULARY
17

Reuse examples -
Mapped in to the EIRA
The caption below should ease the user comprehension of the EU
Cartography, 3 main information are represented :
18
Reuse
R Reusable service
Current state
Policy domain1
S
D
Reused by
Study
Development
P
O
Pilot
Operational
DP Development planned
Health and consumer protection
Humanitarian aid
Internal Market
Anti-Fraud Policy
Home Affairs
Justice
Maritime affairs and fisheries
Mobility and transport
Environment
Competition
Employment and social affairs
Trade
Taxation and customs union
Information society and media
Research
Energy
Statistics
Cross-Sector
Multi-Sector
R Reusable component/functionality/module
R Reusable code
1 A policy domain may have more than one Public Policy as referred to in the EIRA.

National
Interoperability
Frameworks
Observatory (NIFO)
(make the link …)
Alignment
with the EIRA
Reference
Architecture
•What exists?
•What is still missing?
EICart
19

Context view
20
Context View
Information System
Development Reference
Architecture
National Reference
Architecture
Other Reference
Architectures

Introduction
Definition
An architectural solution template is a sub-set of the building blocks of the EIRA, which focuses on the
most salient building blocks needed to build an interoperable solution addressing a particular
interoperability need.
Benefits
• An architectural solution template provides solution architects with a common and unambiguous
approach to cope with a specific interoperability challenge.
• A solution architect can easily create a solution architecture by mapping existing solution building
blocks (developed in his/her organisation or discovered through the TES Cartography) to an
architectural solution template.
• When a user creates an architectural solution template, he/she can recommend specific solution
building blocks (e.g. a particular application or data model) for its implementation. This allows a
faster implementation of the architectural solution template when it is shared with other parties.
• An architectural solution template can be created within and across the different views of the EIRA.
A solution template can then support architects specialised in different architecture domains
(organisational/business architecture, application architecture, data/semantic architecture,
technology architecture)

Organisational View of IMI
Organisational View
Service Agreement
Business Process
User
Public Service
Organisational
Structure
Electronic notification
and information request
Entity
Citizen
Organisations
Public
Administration
Business
Business Rule
Service Delivery
Model
DIGIT DG MARKT
European
National
Sub-National
proposes signs
is a source of
accepts
Public Policy
Organisational
Procedure
Interoperability
Provider Agreement
applies to
is a source of
applies to
Interoperability
Collaboration
Agreement
signs
signs
Service Catalogue
documents
Business Process
Model
documents
22
Services
Competent authorities of
the Member States
IMI acting as a Single
Point of Contact
Notifications process
Notifications and
questions and answers
transactions
Specific sectors
defined in the
Directive on
services in the
Internal Market
Citizens
Professional qualifications
Posted workers
Cross-border services
e-Commerce services
Information request process
SLA

Narrative of the
Semantic View
Generic IMI
The [Data Entities] are described according
to the [Data Model] and [Reference Data].
These are managed according to the
[Metadata Management Policy]. This data
is classified according to the [Security &
Privacy Policy], in terms of Confidentiality
the data is [Level] in terms of Integrity and
Availability the data is [Level]. A [Licensing
& Charging Policy] is applied/ not applied.
The data is published/ not published in a
[Data Catalogue] and its metadata is
available/ not available in a [Metadata
Catalogue].
The [Notifications] are described according to
the [IMI 1.0]. This data is classified according
to the [general security policy for the EC
Information Systems ]. The data are published
in [specific IMI directories] and the metadata
of its services are formalised according to
[WSDLs].
23

Semantic View Click to edit Master title style
Metadata
Attribute
Data Model
Identifier Schema
Controlled
Vocabulary
Data Policy
Notifications data
Data Reference Data
Licensing &
Charging Policy
Security & Privacy
Policy
Dataset
Data Catalogue
Data Entity
Metadata
Catalogue
Metadata
Management
Policy
contains
applies to
Semantic View of IMI
24
IMI 1.0
model
General security policy
for the EC Information
Systems
Specific IMI
directories
Notifications

Narrative of the Technical
View - Application
Generic IMI
[Trans-European Systems (TES)] implement
[Digital Public Services]. They can be
accessed by [Users], which can be [humans]
or [systems], through [Presentation and
Access enablers]. TES provide access to
data through [data source enablers]. Data
can be exchanged cross-border and cross-sector
[IMI] implements [notification services],
and can be accessed by [citizens and
Member State authorities via a web Portal].
IMI provides access to data through [IMI
data service and a Metadata Management
Tool]. Data can be exchanged across-border
with the support of [IMI data validation,
transformation, translation and workflow
services]. IMI can send out the notifications
and data with the support of [IMI data
transmission services]. IMI supports the
dynamic creation of forms through the [IMI
dynamic forms service]. IMI facilitates
internal logging and log processing through
the [IMI monitoring tools]. E-Signature is
supported through the use of [ESSI
services]. Access control is managed
through the [IMI authentication and
authorisation services].
with the support of [data exchange
enablers], can be processed to make
informed decisions with the help of
[decision support enablers] or can be used
in custom ways, for which [specific
purposes enablers] are built. TES can
execute complex business processes
through [workflow enablers] and can
support interaction among humans through
[communication enablers]. Access control
and data security are managed through the
services offered by [security enablers].
25

Technical View of IMI –
Technical view - Application
Processing enablers
Security Enablers
Digital Public
Service
Audit
Service
Logging Service
Audit and
Logging
Component
Identity
Management
Service
Identity &
Access
Management
Component
Access
Management
Service
e-Signature
Service
e-Signature
Component
Workflow Enablers
Human Interface
Instant Messaging
Data exchange enablers Decision Support Enablers
Business Analytics
Service
Business
Analytics
Component
Business
Reporting Service
Business
Reporting
Component
Orchestration
Service
Choreography
Service
Business
Process
Management
Component
Trans-European
System
User
Human System
Data
Transformation
Service
Data
Transformation
Component
Data Validation
Service
Data Validation
Component
Data Transmission
Service
Data
Transmission
Component
Data Translation
Service
Data Translation
Component
Forms Service
Forms
Management
Component
Service
Metadata Service
Metadata
Management
Component
Content Service
Content
Management
Component
Records Service
Record
Management
Component
Machine to
Machine Interface
Specific Purpose Enablers
e-Payment
Service
e-Payment
Component
Communication Enablers
Instant
Messaging
Component
Audiovisual
Service
Audiovisual
Component
Application
Notification
services
IMI
Private and public IMI
Portal
IMI Workflow
Service
IMI data
transmission service
IMI data
validation service
IMI data
service
Metadata
Management Tool
IMI dynamic
forms service
Business
Objects
ESSI
services
IMI authentication and
authorisation services
IMI monitoring
tools
Translation
Management
Service
IMI data
transformation
service
Citizens and
registered Member
State authorities

R Service operated by DG MARKT for others wishing to reuse IMI. In
that case DG MARKT and DIGIT can configure existing generic modules to
be used for new policy areas and without the need for development.
27
IMI as an example of TES for
exchange of requests for information
IMI (Internal Market information System from DG
MARKT) is a system that is prepared to support
multiple policy domains and already does it today. It
implements several business processes, handle notifications
and handle requests for information. IMI can be reused as:
Legal constraint: reuse of the service is possible within the internal market
field only
R The IMI source code can be offered for reuse to others as a basis for
their own administrative cooperation communities outside the internal
market field

EIC. Reuse a Data transformation
service
Public Policy
Specification
Operational
Procedure
Configuration
Management
Processing Enablers
Public Service
Human System
Machine to
Machine Interface
Orchestration
Service
Choreography
Service
User
Business Process
Management
Component
Human Interface
Data
Messaging Service
Discovery Enablers
Service Discovery
Service
Service Discovery
Component
Test Enablers
Test Service
Test Component
Test Scenario
Test Report
Data Routing
Component
Workflow Enablers
Collaboration
Component
Business
Intelligence
Component
Business Analytics
Service
Audiovisual
Service
Business Reporting
Service
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
Service
Metadata
Management
Component
Content
Management
Document
Management
Management
Component
Content
Service
Records
Management
Service
Record
Management
Component
Service
Administration and
Monitoring Service
Lifecycle
Management
Administration
Component
Service
Partner
Management
Service
Partner
Management
Component
e-Archiving service
e-Archiving
component
8 TES relies on a data transformation component and 1 TES was built to
support data format translation.
Focus on
Audit
Service
Access Management
Service
Management
Component
Logging Service
Access
Audit and Logging
Component
XMLGate is a Web service application , used
in DG SANCO, to validate an XML instance
against a well-defined schema.
From a high level perspective XML Gate supports
the collection of structured information and
transfer to back-office systems in charge of the
information processing.
28
Data transformation service
ADNS
O
SURVEILLANCE 2
O
SPEED2
D
eDAMIS
O
ECRIS
O ESBR
D
FNS
O
INSPIRE
D
XML Gate
O
R

EIC. Reuse a Form management
component
Access Management
User
Human System
Metadata
Management
Service
Test Service
Records
Management
Service
Service Discovery
Service
Administration and
Monitoring Service
Lifecycle
Management
Partner
Management
Service
e-Archiving service
9 TES relies on a form management component out of which 2 are generic
and built to be reusable; and 2 are part of a TES and supports form
management capability:
• EUDRANET is a secured infrastructure for communication and data processing between the EU
regulatory authorities for medicinal products.
• RASCHEM is an alert system supporting communication between poison centres and public health
authorities in Member States, regarding chemical incidents in Europe.
2 generic components built to be reused:
• GENIS form management component (DG COMP)
supports the easy creation and maintenance of forms
(simple or complex) for being used in the client
application; and has repository and versioning features.
• Dyn Form (DG EMPL) GUI component which allows to
very easily configure Web Forms, execute them in real-time
and collect the input data in several formats.
Forms Management
EUDRANET
O
R GENIS
R
D
RAS CHEM
O
R
CRMS
O
DynForm
O
ECC-Net
O
eDAMIS
O
ICSMS
O
TRIS
O
R
Focus on
Processing Enablers
Public Service
Audit
Service
Service
Management
Component
Logging Service
Access
Audit and Logging
Component
Workflow Enablers
Business
Intelligence
Component
Business Analytics
Service
Business Reporting
Service
Orchestration
Service
Choreography
Service
Business Process
Management
Component
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
Content
Management
Component
Content
Management
Service
Record
Management
Component
Human Interface
Machine to
Machine Interface
Collaboration
Component
Messaging Service
Audiovisual
Service
Document
Management
Service
Discovery Enablers
Service Discovery
Component
Data Routing
Component
Administration
Component
Service
Partner
Management
Component
Specification
Operational
Procedure
Configuration
Management
Test Enablers
Test Component
Test Scenario
Test Report
Public Policy
Data
e-Archiving
component
29

EIC. Reuse a machine translation service
Identity
Management
Service
Network
Trust Management
Storage
Processing
e-Signature
Validation Service
Service
Public Policy
e-Payment
Service
8 TES relies on a text translation component and 1 TES is providing a text
translation service to others.
Focus on
MT@EC is a service operated by DGT. Users
can directly request a translation and have it
delivered without any further intervention from a
professional translator or the DGT translation
workflow.
Trans-European Solutions already reusing
the MT@EC service are:
• IMI (DG MARKT)
• e-Justice Portal (DG JUST)
• ICSMS (DG ENTR)
Hosting Facility
Interoperable
European
System
Public Network
Private Network
Hosting Service
Networking
Service
Secure Access
e-Signing Service
e-Signature
Component
Identity
Management
Component
Trust
Management
Component
e-Payment
Component
Machine Translation
service
Machine
Translation
Component
30
Text Translation
SURVEILLANCE 2
O
ECRIS
O
ESBR
D
FNS
O
TRIS
O
eJustice Portal
O
MT@EC
R
O
IMI
O
ICSMS
O

Cartography process
Using the EU Cartography for TES 4 Steps
31
Data
Collection
• Data collected via questionnaires filled in by IES owners
• Data on 56 IES, all of them TES, are available
• Target 90 IES, all of them TES
Data
mapping
• Structure the data collected from questionnaires according to
the EIRA Building blocks and attributes
Data
publication
• Publishing the structured data on the Cartography Tool.
Data
Analysis
• Analyse data using the Cartography tool
• Provide recommendations on the potential areas and means for
rationalisation

IEEE's COMPUTER vol 47 issue 10
"Promoting Interoperability in
Europe’s e-Government"
32

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

Session 1. ISA-the baseline for e-SENS interoperability architecture, Raul-Mario-Abril-Jimenez

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (19)

Destacado

Destacado (16)

Similar a Session 1. ISA-the baseline for e-SENS interoperability architecture, Raul-Mario-Abril-Jimenez

Similar a Session 1. ISA-the baseline for e-SENS interoperability architecture, Raul-Mario-Abril-Jimenez (20)

Más de e-SENS project

Más de e-SENS project (13)

Último

Último (20)

Session 1. ISA-the baseline for e-SENS interoperability architecture, Raul-Mario-Abril-Jimenez