1. DG DIGIT, ISA 12 th May 2016 EIRA semantic interoperabiblity specifications based on standards Dr. Raul Abril, European Commission SEMIC 2016 Rome, Italy

2. Click to edit Master title style 2  EIRA v1.0.0 introduction  Why EIRA uses interoperability specifications?  EIRA Interoperability specifications use-cases  What is an EIRA interoperability specification?  Examples AGENDA

3. 3 EIRA v1.0.0 Introduction -The EIRA JoinUp community http://joinup.ec.europa.eu/asset/eia/description

4. Click to edit Master title style 4 EIRA v1.0.0 Introduction – High Level Overview

5. Click to edit Master title style 5 EIRA v1.0.0 Introduction– Semantic view

6. Click to edit Master title style 6 EIRA v1.0.0 Introduction– IOP specification underpinning view

7. Click to edit Master title style 7 To prescribe interoperability in ABBs and to document interoperability in SBBs. In EIRA to prescribe interoperability for an ABB means to provide the set of the most salient cross-domain (not related to any public-policy domain) and public policy domain-specific IOP specifications to which any SBB implementing the ABB should be compliant to. In EIRA to document interoperability for an SBB means to provide the set of the most salient cross-domain (not related to any public-policy domain) and public policy domain-specific IOP specifications to which the SBB is compliant to. Why EIRA uses IOP specifications?

8. Click to edit Master title style 8 Design solution architectures: IoP specifications provide a valuable source of information to formulate requirements during architecture development and solution development. Write tender terms of reference for public procurement: referral to IoP specifications in tenderterms of references ensures that procurement contains clear requirements. In addition, conformance to standards can help avoid vendor lock-in. Test and certify conformance: test, certify and document that SBBs conforms to particular interoperability standards and specifications, and tests. EIRA IOP specifications uses-cases

9. Click to edit Master title style 9 An Interoperability Specification (IoP spec) is a document with the following logical components and whereas I.The is unique. It identifies univocally the IoP spec in the Cartography II.The is a short text. It describes the IoP spec. III.The can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the IoP spec. What is an EIRA IOP specification?

10. Click to edit Master title style 10 An Interoperability Specification (IoP spec) is a document with the following logical components and whereas IV.The interface identifies the type of business information exchange to which the IoP spec is applicable. It informs on the constituents involved in the association agent-to-agent exchanging business information whereas:  An agent is described by the tuple  The agent belongs to an agent_type {human, machine}  The agent acts on behalf of a principal who belongs to a principal_type {citizen, business, PA} V.The scope is either a set of EIRA ABBs (on the endorsed mode) or a set of SBBs supporting EIRA ABBs (on the descriptive mode). ABBs/SBBs might be in different EIF views. It informs on the scope of the IOP spec What is an EIRA IOP specification? Cont.

11. Click to edit Master title style 11 What is an EIRA IOP specification? Cont. An Interoperability Specification (IoP spec) is a document with the following logical components and whereas VI.The modality can be either endorsing (i.e. to be used) or describing (i.e. actually used). It informs on the mode of the IOP spec. VII.The body contains statements on one or several Solution Building Blocks (SBBs). It informs either (i.e. endorsed mode) on the endorsed specification at the Architectural Building Block (ABB) level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability.

12. Click to edit Master title style 12 EIRA endorses IOP specifications maintained by either a governance body and based on open standards or EC ISA specifications. The EIRA allows the possibility to document solutions that uses IOP specifications that are not EIRA endorsed. The CarTool will reference the European Catalogue of Standards as well as non-endorsed standards. An IOP specification is modelled as an SBB. No competing endorsed standards or specifications. One IOP specification may reference another IOP specification. What is an EIRA IOP specification? Cont. An Interoperability Specification (IoP spec) is a document with the following logical components and whereas

13. Click to edit Master title style 13 Example semantic IOP spec for the Data Model ABB

14. Click to edit Master title style 14 Example semantic IOP spec for the Core Data Model ABB

15. Click to edit Master title style 15 Example semantic IOP spec for the Data Set, Data Catalogue, Descriptive Metadata and Data Standard ABBs

16. Click to edit Master title style 16 Contact us Project Officer Raul Abril EIRA@ec.europa.eu For more information Cartography tool European Interoperability Cartography EIRA European Interoperability Reference Architecture EIA Joinup communityhttps://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

17. BACKUP slides

18. Click to edit Master title style EIRA contribution for the Quality of Public Administrations

19. Click to edit Master title style Context of the EIRA 19 European Interoperability Reference Architecture (EIRA) Guidelines and Implementation European Interoperability Strategy (EIS) Governance and strategy European Interoperability FrameworkStrategy (EIF) Framework and principles

20. Click to edit Master title style Alignment between EIF and EIRA 20 EIRA EIF Guidelines Framework

21. Click to edit Master title style EIRA v1.0.0 - Release components The EIRA v1.0.0 beta consists of the following release components: 1.EIRA_v1.0.0_ArchiMate_model.ARCHIMATE: Archi file containing the EIRA ArchiMate model. 2.EIRA_v1.0.0_ArchiMate_model.HTML: HTML version of the EIRA ArchiMate model. 3.EIRA_v1.0.0_Overview.PDF: PDF document containing an introduction to the EIRA, including its key concepts, used ArchiMate notation, tool support, and views. 4.EIRA_v1.0.0_Release document set.ZIP: Zip file containing each of the above mentioned files. 5.EIRA_v1.0.0_Release_notes.PDF: PDF document containing the release notes. The release components can be found in the respective release folder under the following link: https://joinup.ec.europa.eu/asset/eia/description#releasehttps://joinup.ec.europa.eu/asset/eia/description#release 21

22. Click to edit Master title style 22 Expected benefits of the EIRA Assessing Discovering and Reusing Communicating and Sharing 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. Designing 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.

23. Click to edit Master title style Use-cases overview 23 Discovering and Reusing Search for interoperability solutions EIRA Cart Design solution architecture (templates) Design reference architectures Designing Support Impact Assessment on 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