e-SENS Electronic Simple European Networked Services

1. e-SENSElectronic Simple European Networked Services e-SENS General Assembly Presentation of the Work Packages General timeline & high-level objectives Berlin, Germany Apr 9th 2013

2. What e-SENS is about: Presentation of the Work Packages

3. e-SENS WP Structure WP1: Project Management (General Coordination, Administrative Management & Advocacy) WP2: Communication & Marketing WP3: Sustainability and long-term governance WP4: Project Legal Expertise Centre 5.3: e-Justice 5.2: e-Health 5.1: e-Procurement 5.4: Business life-cycle 5.5: New domain WP5: Piloting WP6: Building blocks Provision 6.1: e-Delivery & e-Interaction 6.2: Semantics, Processes and Documents 6.3: Identity, Security and Trust 6.4: Conformance & Tests

4. WP5: Piloting

5. WP5: Piloting Objectives • Develop a Requirements Framework as a “demand landscape” for public ICT services • Coordinate mapping of Requirements to Building Blocks, together with WP6, within indentified and new domains • Define domain specific and cross-domain use cases and pilot scenarios • Establish pilot implementation projects at specific pilot sites, engaging relevant stakeholders and pilot participants and supporting them along their full lifecycle • Support WP3 to assess the LTS potential of building blocks and services through pilot experience and requirement validation • Support WP2 marketing and recruitment activities to engage and commit stakeholders in new domains and pilots

6. WP5 Structure and Interfaces: Conceptual View WP5 Management 5.1:e- Procurement 5.4: Business Lifecycle 5.2: e-Health 5.3: e-Justice Other Domain 1 Other Domain 2 Other Domain 3 WP5.x domain driven: Requirements extraction and validation per domain and across domains Member State driven: Pilot Implementation of building blocks and services at Pilot Sites Pilot Coordination and Lifecycle Management Consolidation of Requirements Mapping and Validation Identification of new pilots and expansion in new domains WP4: Legal Validation WP3: LTS and Governance WP6: Technology Building Blocks WP2: Advocacy and Marketing

7. WP5 Workstreams, Milestones and Deliverables • D5.1, D5.7: Requirements Framework v.1, 2 • D5.2, D5.6: Pilot Lifecycle Management, Pilot Evaluation • D5.3, D5.4, D5.5: Pilot Scenarios and Plans (3 Waves) • 1st Wave Pilots: Decision M12, going live M24 • 2nd Wave Pilots: Decision M21, going live M30 • 3rd Wave Pilots: Decision M30, going live M36

8. e-SENS Piloting Scope E-SENS Domain/BB scope E-SENS Piloting E-SENS funding Other national and European initiatives Implementation Communities “old LSP” Sustainable infrastructure

9. E-SENS Domain/BB scope target (indicative) Specific Service Domains: Public procurement Pre-award Public procurement Post-award Business Lifecycle eHealth eJustice Other Specific Service Dpmain (e.g Social Security?) Otrher Specific Service Domains In e-SENS only In other LSPs Other Initiatives Core Services: BBs in e-SENS In other LSPs E-SENS Scope of Common Components and Pilot Implementation eID (from STORK) Semantics and eDocs eSignatures eDelivery

10. Domain Use of Building Blocks • Started the consultations! • Still a long way to go • WP5/WP6 alignment • Taking Stock of what’s already there • Where do we want to go • How far are we from getting there

11. Current WP5 Scope/MS Participation in Domain-level work Participation in Piloting

12. WP5: Meeting the Challenges • Domain and Piloting Scope • Budget size and distribution, resource management • Requirements validation by Domains and MS • Common Principles for cross-Domain cooperation • Common Principles for Piloting Value • Pilot Prioritization and Governance • Expansion into new Domains

13. WP6: Building Blocks Provision

14. WP6: Building Blocks Provision Year 1 – WP5-6 WP5 Domain requirements & gap analysis Development of cross-domain use cases • D5.1 Requirements Framework n°1 (M12) • D5.2 Pilot Lifecycle Management Methodology & Workflow Support Tools (M12) • D5.3 First-wave Pilot Scenarios and Plans n°1 (M12) Requirements Framework & Mappingwith Architecture Framework Pilot Lifecycle Management, Methodology & Procedures Pilot Support & Monitioring Tools Pilot Scenario Definition & mappingwith Building Blocks Pilot Project Planning & Particpation WP6 SGCC Business Modelling SGCC Requirements Analysis & Design • D6.1 Executable ICT Baseline Architecture (M6)

15. WP6: Building blocks Provision Overall WP6 Plan M6.1 (M4) Business Modelling Consolidated (M4) Individual placement of Building Blocks Dependent on LCM, Maturity and WP5 Requirements M6.2 (M6) Inception Phase Ended D6.1 (M6) Executable ICT Baseline Architecture

16. WP6: Building blocks Provision Methodology Unified process European Interoperability Architecture Maturity Model

17. WP6: Building blocks Provision D6.1 ‘Executable ICT Baseline Architecture’ Taking Stock (brain storm on building blocks) Collect descriptions and relationships Classify according to EIA and Maturity Model Life Cycle Management (ownership and stakeholders) Business Relationships Prioritise Model and Plan (Place in UP development cycle) Result: ICT Architectural Baseline: A draft version of EIA Cartography with plans and objectives for the individual Building Blocks

18. WP6: Building blocks Provision Issues • A WP6 Deliverable is the aggregate of deliverables from each subgroup • Milestones and Deliverables are minimum requirements, meaning that a Subgroup can be futher down the road and leaving room for agility and flexibility • Collaboration with WP3 and WP5 • Collaboration with Standard Organisations • Collaboration with EC initiatives

19. WP6: Building blocks Provision Who’s Who in WP6 WP6 Leader: Klaus Vilstrup Pedersen (kpe@difi.no) Lead Architect: Sven Rasmussen(svrra@digst.dk) SG 6.1 manager: Susanne Wigard (Susanne.Wigard@it.nrw.de) SG 6.2 manager: Olgierd Dziamski (Olgierd.Dziamski@ilim.poznan.pl) SG 6.3 manager: Antonio Lioy (lioy@polito.it) SG 6.3 manager: Cagatay Karabat (cagatay@uekae.tubitak.gov.tr) SG 6.4 manager: Tuncay Namli (tuncay@srdc.com.tr)

20. WP3: Sustainability and long-term governance

22. Objectives: Long-term consolidation of the building blocks of the LSPs with a view to overall acceptance Sustainability models Bringing business cases of building blocks together Governance structure for Cross-border delivery of eGovernment services Working towards legal stability Handover of what is done in the EC policy framework (e.g. CEF). WP3: Sustainability and long-term governance

23. Issues to be resolved Interfaces: National vs international Private vs Public Generic vs Sectoral ….. Infrastructure or paper? Governance organisation WP3: Sustainability and long-term governance

24. WP3: Sustainability and long-term governance Year 1 – WP3 D3.1 Guidelines to the assessment the sustainability and maturity of building blocks (M6) T3.1 Preparation Phase D3.2 Assessment maturity of building blocks (M6) T3.2 Sustainability Assessment phase D3.3 Report on the integrated view of LSP strategies (M6) D3.6 Scenarios for governance models on short, medium and long-term (M9) T3.3 Scenarios and recommendations for sustainability models T3.4 Common business case D3.4 Preliminary proposal for a governance body (M6) D3.5 Preliminary proposal for long-term sustainability within the CEF (M6) T3.5 Governance implementation

25. WP3: Breakdown of PMs Note: PMs in T3.3 and T3.4 need to be separated.

26. WP3: Sustainability and long-term governance Responsibilities WP3 leader: Freek van Krevel (f.j.m.vankrevel@minez.nl) T3.1 manager: Jaak Tepandi(jaak@tepandi.ee) T3.2 manager : Jack Verhoosel (jack.verhoosel@tno.nl) T3.3 manager : Carmen Ciciriello (carmen.ciciriello@celeris-group.eu) T3.4 manager : Bertrand Gregoire (bertrand.gregoire@tudor.lu) T3.5 manager : Katrin Weigend(Katrin.Weigend@bva.bund.de) Subtask manager T3.5.1: Roberto Zuffada(roberto.zuffada@cnt.lispa.it) Subtask manager T3.5.2: Luc Ferrand(luc.ferrand@justice.gouv.fr) Subtask manager T3.5.3: Aleida Alcaide(aleida.alcaide@seap.minhap.es)

27. WP4: Project Legal Expertise Centre

28. WP4: Project Legal Expertise Centre Objectives of WP4 • Draw on the experience of previous LSPs • Maintain a network of legal experts who can provide legal advice on request, both on the themes of the pilots as well as on general, cross-sector EU legislation • Along with sector knowledge, incorporate horizontal legal expertise, related to the great principles and the wide-encompassing instruments of EU law, such as the Services Directive

29. WP4: Project Legal Expertise Centre Objectives of WP4 • Explore the horizontal regulations applicable to eGovernment in each participating country, as well as the applicability of the Administrative Cooperation articles included in the Lisbon Treaty to the field of eGovernment • Monitor legislative developments at EU and national level

30. WP4: Project Legal Expertise Centre Work approach Year 1 • Set up a core group able to give legal advice at short notice • D4.1 Inventory of legal issues encountered by LSPs, including identification of unexplored legal, due Sept. 2013 • Collaboration with other projects • D4.2 Legal process modelling of the proposed pilots, due Nov. 2013 • Collaboration with other WPs

31. WP2: Communication & Marketing

32. WP2: Communication & Marketing Objectives of WP2: BUILDING A SUSTAINABLE COMMUNITY AROUND THE E-SENS • to raiseawareness across Europe of the project’s objectives and achievements • to actively engage relevant stakeholdersgroups • to collectfeedbackandopinionsabouttheproject • to promote e-SENS solutions as re-usableinotherdomains

33. WP2: Communication & Marketing Website Report Report Report Marketing Strategy Pilot Marketing Strategy cooperationwithLSPs social media cooperationwithotherWPs newsletters, articles, events

34. Marketing according to AIDA model

35. WP2: Communication & Marketing Communication success factors: • active national marketing • broad scope • identifying stakeholders needs • close cooperation with LSPs • cooperation with other WPs

36. WP1 Project Management

37. WP1 Project Management Project Management is about ensuring the smooth running of the e-SENS project through timely and sound management • Alignment of partners • Achievement of project milestones and goals • Monitoring of progress • Quality assurance and change management • Involvement of the EC Institutions • Timely delivery of high quality outputs • Respect of budgetary constraints • Distribution of Community funds • Reporting towards the European Commission • Coordination of external relations with WP2

38. e-SENS project governance and organisation General Assembly(1 representative per beneficiary) EC, Council, Etc. . . . . Partner 1 Partner 2 Partner n Coordinator (WP1) Advisory Policy Board Management Board Administration, advocacy & overall management WP1leader WP2leader WP3leader WP5leader WP6leader WP4leader QM eProc. eHealth eBusiness eJustice Partner 1 eID eDelivery eSign. eDoc. Partner 2 ….. WP1 WP2 WP4 WP6 WP3 WP5 Domain Board Architectural Board WP2leader WP1leader WP4leader WP5leader WP3leader WP6leader EC WPL Partner n Policygovernance Administrativegovernance Technical governance Partner = Beneficiary (national consortium)

39. General timeline & high-level objectives Zoom on first year of the project

40. e-SENS: 6 WPs but One Project

41. e-SENS Global Project Plan Legaladvice LSP & Pilots Legaladvice WP4 WP3 Assessment & Design Sustainability Scenarios for GovernanceModels Recommendations & Final Sustainability Plan WP5 Pilot Requirements Framework & Planning Go live preparation 1st Wave live Revision of Framework 2nd Wave live Evaluation & Consolidation Business Modelling & Requirements Design & Implementation Deploy WP6 Evaluation & Consolidation WP2 Communication & Marketing WP1 Project Management

42. Year 1 - WP1,2,3,4 • D1.1 How to Write a Good Deliverable (M2) • D1.2 Internal Communication Plan (M2) • D1.3Risk Management and Quality Assurance (M2) Internal Guidelines WP1 Interim Report Annual Report • D1.4 Interim Activity Report (M7) Website WP2 Comm. Report • D2.1 Project Website (M3) • D2.2 Communication and marketing plan (M3) Communication Plan • D2.3 Report on Communication (M12) • D3.1 Guidelines to Assessment of Building Blocks (M6) • D3.2 Assessment of Building Blocks (M6) • D3.3 Report on Integrated Views of LSPs (M6) • D3.4 Preliminary Proposal for a Governance Body (M6) • D3.5 Preliminary Proposal for Long-term Sustainability (M6) WP3 Preparation Phase Common Business Case • D3.9 Scenarios for • Governancemodels (M9) WP4 Inventory Of Legal Issues • D4.1 Inventory of Legal Issues encountered by LSPs (M4) AnnualSummary Inventory Of Legal Issues • D4.2 Legal Process Modelling of Proposed Pilots (M6) • D4.3 Summary of Activity • (M12)

43. Year 1 – WP5-6 WP5 Domain requirements & gap analysis Development of cross-domain use cases • D5.1 Requirements Framework n°1 (M12) • D5.2 Pilot Lifecycle Management Methodology & Workflow Support Tools (M12) • D5.3 First-wave Pilot Scenarios and Plans n°1 (M12) Requirements Framework & Mappingwith Architecture Framework Pilot Lifecycle Management, Methodology & Procedures Pilot Support & Monitioring Tools Pilot Scenario Definition & mappingwith Building Blocks Pilot Project Planning & Particpation WP6 SGCC Business Modelling SGCC Requirements Analysis & Design • D6.1 Executable ICT Baseline Architecture (M6)