1. ISA Programme Action 2.1 and Action 2.14 e-SENS pilot on the use of EIRA and the Cartography Tool 7-8 January 2015 Workshop

2. Click to edit Master title style Disclaimer 2 The information and views set out in this presentation are those of the author(s) and do not necessarily reflect the official opinion of the Commission. The Commission does not guarantee the accuracy of the data included in this presentation. Neither the Commission nor any person acting on the Commission’s behalf may be held responsible for the use which may be made of the information contained therein. © European Union, 2014 ArchiMate® and TOGAF® are registered trademarks of The Open Group.

3. TimeTopic 08:30Registration and coffee 09:00Welcome – Raul Abril, European Commission, ISA Programme 09:10Round table – All participants 09:30Overview of e-SENS WP6 – Klaus Vilstrup Pedersen, e-SENS 10:00Overview of the EIRA – Raul Abril, European Commission, ISA Programme 11:00Coffee break 11:15Work session on the EIRA – Max Stahlecker 11:45Lunch – all (MO34) 13:00Work session SAT eID part I (Design Solution Architecture use case) 14:30Coffee break 14:45Work session SAT eID part II (Design Solution Architecture use case) 16:30Coffee break 16:45Work session SAT eID part III (Design Solution Architecture use case) 18:00Closing and end 19:00Dinner (at own expense) Workshop Agenda 7 January

4. TimeTopic 08:30Registration and coffee 09:00Overview – Raul Abril, European Commission, ISA Programme 09:10Recap of previous day- summary of SAT results and link to Cartography session 09:20Coffee break 09:30Cartography Tool in practise – Debora Di Giacomo 11:00Coffee break 11:15Collecting data for the Cartography Tool 12:15Lunch 13:30Document Interoperability Solutions use case – work session 15:00Closing and end Workshop Agenda 8 January

5. Round table

6. Welcome Rules and objectives

7. 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 Rules of engagement and objectives

8. E-SENS Pilot of EIRA and CarTool 8 Workshop objectives 1.Attain a common understanding about EIRA and CarTool 2.Plan the work 3.Get a lot of the work done already

9. Workshop on EIRA (1/2) 9 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-IDhttp://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

10. Workshop on EIRA (2/2) 10 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/Glossaryhttp://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/loginhttps://ec.europa.eu/eusurvey/auth/login 2.Provide informal feedback (preliminary)

11. Pilot evaluation criteria 11 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

12. Overview of e-SENS WP6 Klaus Vilstrup Pedersen, e-SENS

13. Overview of the EIRA Raul Abril, European Commission

14. Outline 14 03 02 04 The European Interoperability Reference Architecture (EIRA) Context and Positioning of the EIRA Objectives and use cases Solution Architecture Templates 01 05 Summary

15. Overview 15 The European Interoperability Reference Architecture (EIRA) 03020401 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 05

16. The EIRA 16 Overview The European Interoperability Reference Architecture (EIRA) 0302040105

17. The EIRA 17 Legal layer The European Interoperability Reference Architecture (EIRA) 0302040105

18. The EIRA 18 Organisational layer The European Interoperability Reference Architecture (EIRA) 0302040105

19. The EIRA 19 Semantic layer The European Interoperability Reference Architecture (EIRA) 0302040105

20. The EIRA 20 Technical View - Application The European Interoperability Reference Architecture (EIRA) 0302040105

21. The EIRA 21 Technical View - Infrastructure The European Interoperability Reference Architecture (EIRA) 0302040105

22. The EIRA 22 The European Interoperability Reference Architecture (EIRA) 03020401 The EIA Community on Joinup http://joinup.ec.europa.eu/asset/eia/description 05

23. Outline 23 03 02 The European Interoperability Reference Architecture (EIRA) Context and Positioning of the EIRA Objectives and use cases 01 04 Solution Architecture Templates 05 Summary

24. Context of the EIRA 24 03020401 Context and Positioning of the EIRA European Interoperability Reference Architecture (EIRA) Guidelines and Implementation European Interoperability Framework (EIF) Framework and principles European Interoperability Strategy (EIS) Governance and strategy 05

25. Alignment between EIF and EIRA 25 03020401 Context and Positioning of the EIRA EIRA EIF Guidelines Framework 05

26. Positioning the EIRA 26 03020401 Context and Positioning of the EIRA EIRA provides a common core of context-neutral architecture building blocks Domain Reference Architectures: e.g. Taxation Reference Architecture Framework 1.EIRA: context-neutral architecture building blocks (ABBs). Focused on interoperability. 2.Reference architecture for a domain: domain- specific architecture building blocks. Minimum agreements for taxation. 3.Solution architecture: specific solution designed using a domain-specific architecture Core Reference Architecture: EIRA – minimal cross-sector interoperability Solution Architectures: e.g. Automatic Information Exchange, FATCA, VIES, … EIRA Core Social Security HR TAX Environment FATCA VIES 05

27. Reference architecture 27 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). 03020401 Context and Positioning of the EIRA 05

28. Positioning the EIRA 28 03020401 Context and Positioning of the EIRA EIRA’s positioning within the Enterprise Continuum EIRA Cartography Tool 05

29. Architectural patterns 29 03020401 Context and Positioning of the EIRA Service consumption 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 05

30. Architectural patterns 30 03020401 Context and Positioning of the EIRA Service provisioning 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 05

31. Outline 31 03 02 The European Interoperability Reference Architecture (EIRA) Context and Positioning of the EIRA Objectives and use cases 01 04 Solution Architecture Templates 05 Summary

32. Objectives of the EIRA 32 03020401 Objectives and use cases 05 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 Cartography – Cart in Joinup website. Help documenting the most salient interoperability elements of complex systems and facilitate the sharing of reusable solutions. Expected benefits of the EIRA

33. Use-cases overview 33 03020401 Objectives and use cases 05 Discovering and Reusing Search for interoperability solutions EIRA Cart Design solution architecture (templates) Design reference architectures Designing Assess impact of 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

34. Outline 34 03 02 The European Interoperability Reference Architecture (EIRA) Context and Positioning of the EIRA Objectives and use cases 01 04 Solution Architecture Templates 05 Summary

35. Definition 35 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 Solution Architecture Templates 0302040105 What is a Solution Architecture Template?

36. Spatial positioning 36 Solution Architecture Templates 0302040105 EIRA Cartography Tool Solution Architecture Templates Position within the Enterprise Continuum

37. Temporal positioning 37 Solution Architecture Templates 0302040105 Reference Architecture Solution Architecture Templates Solution Architecture Position within the ADM

38. Creation and usage of SATs 38 Solution Architecture Templates 0302040105 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. 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. 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. The architectural solution template is shared with the involved stakeholders (e.g. by sharing or uploading the Archimate diagram of the solution template). Step 1: Identify needed EIRA BBs Step 2: Create blueprint of solution template Step 3 : Add Interoperability requirements and solution BBs Step 4: Share solution template Creation of SATs

39. Creation and usage of SATs 39 Solution Architecture Templates 0302040105 Text The user consults the architectural solution template, via the Cartography tool, related to the particular interoperability need he/she wants to address. 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. Step 1: Consultation of the solution template Step 3: Design solution Step 2: Mapping with existing solutions 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. Usage of SATs

40. Outline 40 03 02 The European Interoperability Reference Architecture (EIRA) Context and Positioning of the EIRA Objectives and use cases 01 04 Solution Architecture Templates 05 Summary

41. 41 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. Summary 0302040105

42. Work session on the EIRA Max Stahlecker

43. Work session on EIRA 43 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?

44. Work session Design a solution architecture template for eID

45. Outline 45 03 02 04 Objectives of the work session Part I: Agreeing on the scope of the eID SAT and target audience Part II: Interoperability specifications for the eID SAT Part III: Updating/complementing Archimate diagrams for the eID SAT 01

46. Objectives of the work session 46 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 Objectives of the work session 03020401 Expected Outcomes

47. Outline 47 03 02 04 Objectives of the work session Part I: Agreeing on the scope of the eID SAT and target audience Part II: Interoperability specifications for the eID SAT Part III: Updating/complementing Archimate diagrams for the eID SAT 01

48. 48 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 https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd We-_qyalenDseQQ/edit#heading=h.swo3jgnyv8cm https://docs.google.com/spreadsheets/d/1Hh_v- 2k153IfGwTZ0aQwbDRZofDtfRcaA_6itz25JeM/edit?usp=sharing Expected results Agreed definition, target audience, stakeholders and list of ABBs Part I 03020401 Agreeing on the scope of the SAT and target audience

49. Outline 49 03 02 04 Objectives of the work session Part I: Agreeing on the scope of the eID SAT and target audience Part II: Interoperability specifications for the eID SAT Part III: Updating/complementing Archimate diagrams for the eID SAT 01

50. 50 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. Part II 03020401 Interoperability specifications for the eID SAT What are interoperability specifications

51. 51 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. Part II 03020401 Interoperability specifications for the eID SAT Why use interoperability specifications?

52. 52 Part II 03020401 Levels of abstraction

53. 53 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 https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd We-_qyalenDseQQ/edit#heading=h.o68matyt3grx https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd We-_qyalenDseQQ/edit#heading=h.o68matyt3grx Expected results Interoperability specifications structured according to related ABB(s) related SAT(s) related EIF principle(s) related interoperability area(s) Part II 03020401 Interoperability specifications for the eID SAT Exercise II : identify interoperability specifications

54. Outline 54 03 02 04 Objectives of the work session Part I: Agreeing on the scope of the eID SAT and target audience Part II: Interoperability specifications for the eID SAT Part III: Updating/complementing Archimate diagrams for the eID SAT 01

55. 55 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 https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd We-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0 https://docs.google.com/document/d/1Aoc29agmBLgcOVVR97kTw0ocipMd We-_qyalenDseQQ/edit#heading=h.6vi6o0w24mk0 Expected results Updated diagrams Part III 03020401 Updating /completing Archimate diagrams Aligning EIRA and eSENS SA(T) blueprints

56. 56 Part III 03020401 Updating/completing Archimate diagrams Organisation / business view

57. 57 Part III 03020401 Updating/completing Archimate diagrams Organisation / business view

58. Conclusion 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 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? Design Solution Architecture Templates use case 58

59. End of day 1 Social dinner @ 19:00 Lune de Miele – Rue Jules van Praet, Brussels 1000 Metro Bourse Taxi Place St Gery

60. 60 TimeTopic 08:30Registration and coffee 09:00Overview – Raul Abril, European Commission, ISA Programme 09:10Recap of previous day- summary of SAT results and link to Cartography session 09:20Coffee break 09:30Cartography Tool in practise – Debora Di Giacomo 11:00Coffee break 11:15Collecting data for the Cartography Tool 12:15Lunch 13:30Document Interoperability Solutions use case – work session 15:00Closing and end Workshop Agenda 8 January

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

62. Disclaimer This presentation was prepared for the ISA programme of the European Commission by PwC EU Services. The views expressed in this report are purely those of the authors and may not, in any circumstances, be interpreted as stating an official position of the European Commission. The European Commission does not guarantee the accuracy of the information included in this study, nor does it accept any responsibility for any use thereof. Reference herein to any specific products, specifications, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favouring by the European Commission. All care has been taken by the author to ensure that s/he has obtained, where necessary, permission to use any parts of manuscripts including illustrations, maps, and graphs, on which intellectual property rights already exist from the titular holder(s) of such rights or from her/his or their legal representative.

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