Navigation path

European Interoperability Reference Architecture (EIRA)

(
 
)
3.33/5 | 15 votes
Editor's choice

Description

   

 

  1. The European Interoperability Architecture
  2. Expected benefits
  3. EIRA Support Series
  4. Continuous improvement
  5. EIRA releases
  6. Solution Architecture Templates
  7. Cartography tool
  8. Supporting material
  9. Learning material
  10. Additional material

With the growing amount of information exchanges between public services (across borders and sectors), the need for interoperability in Europe is higher than ever. The ISA² Action 2016.32 (EIA) introduces a reference architecture to guide public administrations in their work to provide interoperable European public services to businesses and citizens.

 

 

The European Interoperability Architecture

The modernisation of public administrations, fostered by technological advancements, leads to a rapidly growing amount of information exchanges between public administrations (across borders and sectors). To facilitate these information exchanges, the need for interoperability in Europe is higher than ever. Solution developers in all domains of the public sector often deem interoperability and reusability essential to a solution design. 

 

 

To attain interoperability, public administrations in Europe need to coordinate across borders and sectors when developing digital solutions to avoid the risk of creating new digital barriers for administrations, businesses, and citizens. They have the following needs:

  • Need for a common terminology to design, assess, and communicate about e-Government solutions: public administrations need a common terminology to design, assess, communicate about, and find solutions building blocks (frameworks, tools, services) used to deliver interoperable digital public services;
  • Need for a stable interfaces for digital public services: public administrations need to define stable interfaces between digital public services, so that others can rely on them to build new, aggregated digital public services;
  • Need for an overview of already existing solution building blocks: public administrations need to be aware of already existing solution building blocks that have been developed by others.

The ISA Programme is providing concrete interoperability solutions that contribute to making the modernisation of public administrations a success story. It, among others, developed the European Interoperability Reference Architecture (EIRA) to guide public administrations in their work to provide interoperable European public services to other public administrations, businesses and citizens.

The EIRA is a four-view reference architecture for delivering interoperable digital public services across borders and sectors. It defines the required capabilities for promoting interoperability as a set of architecture building blocks (ABBs). The EIRA has four main characteristics:

  • Common terminology to achieve a minimum level of coordination: It provides a set of well-defined ABBs that provide a minimal common understanding of the most important building blocks needed to build interoperable public services.
  • Reference architecture for delivering digital public services: It offers a framework to categorise (re)usable solution building blocks (SBBs) of an e-Government solution. It allows portfolio managers to rationalise, manage and document their portfolio of solutions.  
  • Technology- and product-neutral and a service-oriented architecture (SOA) style: The EIRA adopts a service-oriented architecture style and promotes ArchiMate as a modelling notation. In fact, the EIRA ABBs can be seen as an extension of the model concepts in ArchiMate.
  • Alignment with EIF and TOGAF: The EIRA is aligned with the European Interoperability Framework (EIF) and complies with the context given in the European Interoperability Strategy (EIS) . The views of the EIRA correspond to the interoperability levels in the EIF: legal, organisational, semantic and technical interoperability. Within TOGAF and the Enterprise Architecture Continuum, EIRA focuses on the architecture continuum. It re-uses terminology and paradigms from TOGAF such as architecture patterns, building blocks and views. 

The figure belows show the high-level overview of the EIRA. Each view has a set of ABBs and relations pertaining to the legal, organisational, semantic and technical domain of an Interoperable European Architecture. Each view has entry - and exit points from one view to another.

EIRA high-level overview

 

Expected benefits

The common use of the EIRA when developing, assessing, and communicating about e-Government solutions will result in network effects, enhancing the coordination between public administrations at EU level and within the Member States. The common use of the EIRA will result in the following benefits:

  • Development of more interoperable e-Government solutions: The consistent use of the EIRA when developing e-Government solutions will make them more interoperable, for the following reasons:
    • The EIRA provides a common language of architecture building blocks for the design and comparison of the solution architectures of e-Government solutions;
    • The EIRA promotes the identification and use of common interoperability specifications, which hare to provide a basis for stable interfaces between digital public services;
    • The EIRA will contribute to an increased awareness and usage of EIF principles and recommendations.
    • Increased application of the principles of service-oriented architecture (SOA).
  • Cost-savings due to better assessment of solution portfolios: The EIRA will contribute to realising cost-savings related to rationalisation of the portfolio of solutions and solution building blocks (e.g. phasing out superfluous SBBs; or making building blocks more generic to be more generally applicable.);
  • Cost-savings via increased findability: the EIRA and TES Cartography provide a consistent way to document and classify reusable solution building blocks, allowing reusable and interoperable solution building blocks to be found and understood more easily.

EIRA Support Series

Continuous improvement

As the EIRA is being applied, new challenges and ideas for the EIRA arise and need to be managed. Therefore the ISA² Programme welcomes feedback, additional thoughts, and open dialog on the idea of advancing the EIRA. To facilitate this, the ISA² Programme set up an open change, configuration and release management process for the EIRA.

Please follow this link to submit feedback using the 'Actions' option of Joinups' ticketing system (registration and/or login is required). Stakeholders working in the field of architecture and interoperability can provide their comments on the EIRA release page on Joinup.

EIRA releases

The current EIRA release is EIRA v1.1.1.

Solution Architecture Templates

A Solution Architecture Template (SAT) is a specification extending the EIRA. It provides support to solution architects in a specific solution domain. The SATs' purpose is to provide guidance by defining a minimal, but holistic (legal, organisational, semantic and technical) interoperability architecture to develop an interoperable solution. 

The following documents are available to help the architect in documenting an SAT:

Four SATs have been published to date: 

  • Open Data SAT v1.0.1 Beta - Enterprise and Solution architects can use this document to design solution architectures in the domain of Open Data.
  • eHI (Human Interface) SAT v1.0.1 Beta - Enterprise and Solution architects can use this document and the related SAT model to design solution architectures that have a Human Interface (as opposed to a machine-to-machine interface) as part of the solution. The proposed solution architecture template is EC centric.
  • eDelivery SAT v1.0.1 Beta - Enterprise and Solution architects can use this document to design solution architectures in the domain of eDelivery.
  • eID SAT v1.0.1 Beta – Enterprise and Solution architects can use this document to design solution architectures in the domain of eID cross border authenticated service.

Cartography tool

A major improvement is the introduction of the Cartography Tool (CarTool)imageThe CarTool brings  together high level support for the EIRA as an Archi® plug-in. It includes both editing features to model solutions using the EIRA, and querying features to query an EIRA-based Cartography of solutions. More information regarding the plugin as well as its version 1.0.1 have been published on Joinup

Supporting material

Presentation of the project by the European commission*

*Please note that the video were produced for an alpha version of the EIRA. As such some building blocks might have been modified. The political view is no longer part of the EIRA.

Learning material

Additional material

*ArchiMate® and TOGAF® are registered trademarks of The Open Group.

**Archi® is a registered trademark of Phillip Beauvoir.

 

 

Birol Berkem
Posted by Birol Berkem on December 03, 2015 at 10:53
"
Hi,
 
Sorry, I'm late for this public consultation and feedback.
 
However, would you consider checking whether the 12 EIF principles available at http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf have been completely treated throughout the different layered views of the EIRA Framework ? 
 
So that on the basis of goals and values of the architecture, principles imply requirements that are to be considered to influence other principles to impact "building blocks" of all of the layered views by establishing appropriate relationships...
 
I provided an example of this "goal driven, value and principle based" chain of responsibility propagation on http://goobiz.com/Value_Based_IT_Alignment_Using_TOGAF_ITIL_SE_and_Agile.html (cf. figures 2 and 3). Please do not consider ITIL and underlying components in the case of EIRA.  
 
Kind Regards, 
Birol Berkem
www.goobiz.com
 

Subscribe to newsletter

You will receive news and links to the most interesting developments...