Download - 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 [email protected]
EIRA and EIC update
Click to edit Master title style
Overall view
Monitoring activities (M)
Programme 5.1
Accompanying Measures (A)
Community building
4.2.1 4.2.2 Communication Activities
4.1.1
TES 2.14 NIFO 4.2.3
Supporting Instruments to European Public Administrations (PA)
EIS 5.2
Sharing & reuse 4.2.5
IMM 4.1.2
CAMMS 2.2
EIA 2.1
CIRCABC 2.5
EFIR 4.2.4
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.20 1.13
Sources of trusted information 1.2 2.9
eSignature & eIdentification
1.18 1.4 1.5 1.9 2.3
Semantics 2.15 1.1
2
Source: ISA Legal Decision Art. 1, 2, 3 , Kurt Salmon analysis
ISA portfolio
Click to edit Master title style
3
Objectives of the EIA action
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 European Interoperability Cartography – EICart in Joinup website.
Help documenting the most salient interoperability elements of complex systems and facilitate the sharing of reusable solutions.
Click to edit Master title style
Main work products of the EIA action
A mapping of solutions to the Building
Blocks of the EIRA.
A four-view reference architecture for
delivering digital public services
(across borders and sectors).
EIRA European Interoperability Reference Architecture
EICart European Interoperability Cartography
4
Click to edit Master title style
Legal view
5
Public Policy Implementation InstrumentsPublic Policy Development Enablers
Operational Enablers
Legal Requirements
Legal View
Public Policy
Non-binding Instrument
EU level
Binding Instrument
National level Sub-National levelFinancial Resource
Implementing Guideline
Approach Mandate
Legal Constraints
Binding InstrumentNon-binding Instrument
Public Policy Cycle
Definition of Public Policy Objectives
Formulation of Public Policy Scenarios
Impact Assessment
Public Policy Implementation
Public Policy Evaluation
Click to edit Master title style
Organisational view
6
Organisational Enablers
Organisational View
Business Process
User
Public Service
Service ProviderInteroperability Service Agreement
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
signsproposes
is a source of
accepts
Public Policy
Organisational Procedure
Interoperability Provider Agreement
applies to
offersconsumes signs
is a source of
applies to
InteroperabilityCollaboration
Agreement
signs
signs
Service Catalogue
documentsBusiness Process
Model
documents
Click to edit Master title style
Semantic view
7
Semantic View
Metadata
Data Model
Identifier Schema
Controlled VocabularyReference Data
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 Policyinfluences
Code list
Click to edit Master title style
Technical view – Application
8
Interoperable European System
Processing Enablers
Presentation and Access Enablers
Data Source Enablers
Application Security Enablers
Public Service
Audit Service
Audit and Logging Component
Logging Service
Access Management Component
Access Management Service
Workflow Enablers
Mediation Enablers Decision Support Enablers
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 InterfaceMachine to
Machine Interface
Collaboration Enablers
Collaboration Component
Messaging ServiceAudiovisual
Service
Document Management
Service
Discovery Enablers
Service Discovery Component
Service Discovery Service
Technical View - Application
Data Routing Service
Data Routing Component
Administration Enablers
Administration Component
Administration and Monitoring Service
Lifecycle Management
Service
Partner Management Component
Partner Management
Service
Documentation Enablers
Specification
Operational Procedure
Configuration Management
Test Enablers
Test Component
Test ServiceTest Scenario
Test Report
Public PolicyData
e-Archiving component
e-Archiving service
Click to edit Master title style
Technical view – Infrastructure
9
Technical View - Infrastructure
Hosting and Networking Services Infrastructure
Digital Services Infrastructure
Infrastructure Security Enablers
Hosting Facility
Interoperable
European
System
Public Hosting FacilityPrivate Hosting Facility
Network
Storage
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
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
Organisational Enablers
Organisational View
Business Process
User
Public Service
Service ProviderInteroperability Service Agreement
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
signsproposes
is a source of
accepts
Public Policy
Organisational Procedure
Interoperability Provider Agreement
applies to
offersconsumes signs
is a source of
applies to
InteroperabilityCollaboration
Agreement
signs
signs
Service Catalogue
documentsBusiness Process
Model
documents
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).
Technical View - Infrastructure
Hosting and Networking Services Infrastructure
Digital Services Infrastructure
Infrastructure Security Enablers
Hosting Facility
Interoperable
European
System
Public Hosting FacilityPrivate Hosting Facility
Network
Storage
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
Hosting and Networking
enablers sTESTAO
Private Network
GeantO
CCNO
R R
E-Payment Service
BRISD
DP
FNSO
Identity Management
service
E-Signing Service Validate digital signature
certificates
P
DSS TLManagerO
R
FNSO
Text Translation
SURVEILLANCE 2O
ECRISO
ESBRD
FNSO
TRISO
eJustice PortalO
MT@EC
R
O
IMIO
ICSMSO
Infrastructure Security Enablers
Digital Services
Infrastructure
STORK
ECASO
ESSIO
O
R
R
R
S
D
P
O
Study
Development
Pilot
Operational
Internal Market
Anti-Fraud Policy
Taxation and customs union
Research
Cross-Sector
Multi-Sector
R Reusable sytems/components
DP Development planned
Caption:
R Reusable services
Click to edit Master title style
DO NOT DISTRIBUTE FURTHER 12
Use cases of the EIA action
Discovering and Reusing
Search for interoperability solutions
EIRA Cart
Design solution architectures
Design reference architectures
Designing
Structure the architectural implications of policy or thematic domains (to the extent
of the views of the EIRA)
Communicating and Sharing
Document interoperability solutions
Compare reference architectures
Compare solution architectures
Manage portfolio
Rationalise portfolio
Assessing
Create portfolio
Click to edit Master title style
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
Click to edit Master title style
DO NOT DISTRIBUTE FURTHER 14
KEY BENEFITS
How to ensure interoperability between a national system and the systems of the EC and of other MSs.
Marco can use the technical view - application
of the EIRA to find the BBs that are relevant for
interoperable message exchange.
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
Design solution architecture Search for interoperability solutions
Scenario 1 – Use cases
CHALLENGE
EIA in PRACTICE
Click to edit Master title style
DO NOT DISTRIBUTE FURTHER
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
Click to edit Master title style
DO NOT DISTRIBUTE FURTHER 16
KEY BENEFITS
How to rationalise the application landscape to support efficient business process implementation.
• Structured communication with stakeholders
• Accelerated assessment of architectures
• Simplified decision-making process for application portfolio rationalisation
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
PROBLEM
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.
Rationalise portfolio
Scenario 2 – Use cases
EIA in PRACTICE
Click to edit Master title style
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
VOCABULARY
PUBLICSERVICE
17
The caption below should ease the user comprehension of the EU Cartography, 3 main information are represented :
18
Reuse examples - Mapped in to the EIRA
Reuse
Current state
Policy domain1
S
D
Study
Development
P
O
Pilot
Operational
DP Development planned
Reused by
Internal Market
Humanitarian aid
Health and consumer protection
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
Cross-Sector
Multi-Sector
Statistics
R Reusable component/functionality/module
R Reusable service
R Reusable code
1 A policy domain may have more than one Public Policy as referred to in the EIRA.
Click to edit Master title style
(make the link …)
Alignment with the EIRA Reference Architecture
•What exists? •What is still missing?
National Interoperability Frameworks Observatory (NIFO)
EICart
19
Click to edit Master title style
Context view
20
Context View
Information System
Development Reference
Architecture
National Reference
Architecture
Other Reference
Architectures
Click to edit Master title style
DO NOT DISTRIBUTE FURTHER
21
Introduction
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)
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.
Click to edit Master title style Organisational Enablers
Organisational View
Business Process
User
Public Service
Service ProviderInteroperability Service Agreement
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
signsproposes
is a source of
accepts
Public Policy
Organisational Procedure
Interoperability Provider Agreement
applies to
offersconsumes signs
is a source of
applies to
InteroperabilityCollaboration
Agreement
signs
signs
Service Catalogue
documentsBusiness Process
Model
documents
22
Electronic notification and information request
Services
Competent authorities of the Member States
IMI acting as a Single Point of Contact
Notifications process
Notifications and questions and answers
transactions
DIGIT DG MARKT
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
Organisational View of IMI
Click to edit Master title style
Narrative of the Semantic View
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].
Generic IMI
23
Click to edit Master title style Semantic View
Metadata
Attribute
Data Model
Identifier Schema
Controlled
Vocabulary
Reference DataData
Data Policy
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
Notifications data model
General security policy for the EC Information
Systems
Specific IMI directories
Notifications
Click to edit Master title style
Narrative of the Technical View - Application
[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 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].
Generic IMI
25
[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].
Click to edit Master title style
Processing enablers
Presentation and Access Enablers
Data Source Enablers
Technical view - Application
Security Enablers
Digital Public
Service
Audit
Service
Audit and
Logging
Component
Logging Service
Identity
Management
Service
Identity &
Access
Management
Component
Access
Management
Service
e-Signature
Service
e-Signature
Component
Workflow Enablers
Data exchange enablers Decision Support Enablers
Business
Analytics
Component
Business Analytics
Service
Business
Reporting
Component
Business
Reporting Service
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
Metadata
Management
Component
Metadata Service
Content
Management
Component
Content Service
Record
Management
Component
Records Service
Human InterfaceMachine to
Machine Interface
Specific Purpose Enablers
e-Payment
Component
e-Payment
Service
Communication Enablers
Instant
Messaging
Component
Instant Messaging
ServiceAudiovisual
Service
Audiovisual
Component
Technical View of IMI – 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
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 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.
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
8 TES relies on a data transformation component and 1 TES was built to support data format translation.
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.
Focus on
Interoperable European System
Processing Enablers
Presentation and Access Enablers
Data Source Enablers
Application Security Enablers
Public Service
Audit Service
Audit and Logging Component
Logging Service
Access Management Component
Access Management Service
Workflow Enablers
Mediation Enablers Decision Support Enablers
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 InterfaceMachine to
Machine Interface
Collaboration Enablers
Collaboration Component
Messaging ServiceAudiovisual
Service
Document Management
Service
Discovery Enablers
Service Discovery Component
Service Discovery Service
Technical View - Application
Data Routing Service
Data Routing Component
Administration Enablers
Administration Component
Administration and Monitoring Service
Lifecycle Management
Service
Partner Management Component
Partner Management
Service
Documentation Enablers
Specification
Operational Procedure
Configuration Management
Test Enablers
Test Component
Test ServiceTest Scenario
Test Report
Public PolicyData
e-Archiving component
e-Archiving service
28
Data transformation service
ADNSO
SURVEILLANCE 2O
SPEED2D
eDAMISO
ECRISO ESBR
DFNS
O
INSPIRED
XML GateO
R
EIC. Reuse a Form management component
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
EUDRANETO
RGENIS
RD
RAS CHEMO
R
CRMSO
DynFormO
ECC-NetO
eDAMISO
ICSMSO
TRISO
R
Focus on
Interoperable European System
Processing Enablers
Presentation and Access Enablers
Data Source Enablers
Application Security Enablers
Public Service
Audit Service
Audit and Logging Component
Logging Service
Access Management Component
Access Management Service
Workflow Enablers
Mediation Enablers Decision Support Enablers
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 InterfaceMachine to
Machine Interface
Collaboration Enablers
Collaboration Component
Messaging ServiceAudiovisual
Service
Document Management
Service
Discovery Enablers
Service Discovery Component
Service Discovery Service
Technical View - Application
Data Routing Service
Data Routing Component
Administration Enablers
Administration Component
Administration and Monitoring Service
Lifecycle Management
Service
Partner Management Component
Partner Management
Service
Documentation Enablers
Specification
Operational Procedure
Configuration Management
Test Enablers
Test Component
Test ServiceTest Scenario
Test Report
Public PolicyData
e-Archiving component
e-Archiving service
29
EIC. Reuse a machine translation service
8 TES relies on a text translation component and 1 TES is providing a text translation service to others.
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)
Focus on
Technical View - Infrastructure
Hosting and Networking Services Infrastructure
Digital Services Infrastructure
Infrastructure Security Enablers
Hosting Facility
Interoperable
European
System
Public Hosting FacilityPrivate Hosting Facility
Network
Storage
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
30
Text Translation
SURVEILLANCE 2O
ECRISO
ESBRD
FNSO
TRISO
eJustice PortalO
MT@EC
R
O
IMIO
ICSMSO
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
Click to edit Master title style
32
IEEE's COMPUTER vol 47 issue 10
"Promoting Interoperability in
Europe’s e-Government"
Click to edit Master title style
33
https://joinup.ec.europa.eu/asset/eia/description