e-sens Electronic Simple European Networked Services Klaus Vilstrup Pedersen WP6 Manager DIFI, Norway

Transcription

1 e-sens Electronic Simple European Networked Services Klaus Vilstrup Pedersen WP6 Manager DIFI, Norway

2 esens BCSS call for proposal Objectives Consolidate and align work from the LSPs Create Long Term Sustainability Broaden the piloting into new areas Keywords: Single Market, Citizens, SME, CEF Max budget is 27 mill euro Germany (Nordrhein Westphalen) is lead Proposal , Negotiation with EC from Project start with a duration of 3 years

3 esens Participants Austria Czech Republic Denmark Estonia France Germany Greece Italy Luxembourg Netherlands Norway Poland Portugal Romania Slovakia Spain Sweden Turkey Ireland (New) ETSI OpenPEPPOL

4 e-sens Project

5 e-sens Project governance and organisation EC/DG CONNECT EC, Council, Etc. General Assembly (1 representative per Beneficiary).... P.1 P.2 P.n Coordinator Admin., advocacy & overall management WP1. Management Board WPn QM ehealth eproc. Policy Board ejustice ebusines s. Partner 2 Partner n WP1 leade r WP1 WP2 leade r WP2 WP3 leade r WP3 WP4 leade r WP4 WP5 leader Domain Board WP5 WP6 leade r Architect ural Board WP6 eid esign. WPn edeliver y edoc. EC As Observers Administrative governance Project governance Policy governance

6 WP 5 Objective The vision of WP5 is to demonstrate that it is feasible, realistic and sustainable to deploy real-life ICT services within and among countries across Europe. The pilots will be in so-called production pilot environments where actual transactions among public administrations, or between them and European citizens and businesses, can take place based on technological building blocks in a cross border context.

7 Domain Tasks

8 Domain Plan Task Year 1 Year 2 Year 3 Code WP/Task/Activity Name Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 WP5. Horizontal Coordination Activities T5.. WP Management T5..1 Consolidation of Requirements Mapping and Validation A Domain Requirements Synthesis, synergies and gaps A Development of cross-domain use cases A Development of BCSS Requirements Framework A Mapping BCSS Requirements Framework with BCSS Architectural Framework T5..2 Coordination of Pilot Definition/Identification/Expansion to new pilots/domains A Support to the Identification of Domain and Cross-Domain Pilots A Support to Domain and Cross-Domain Pilot Definition and Planning T5..3 Pilot Coordination and Lifecycle Management A Pilot Lifecycle Management Methodology and Procedures A Pilot Support and Monitoring Tools A Structured Workflow for 1st and 2nd Level Support to Pilots D5.1 D5.2 D5.7 WP5.x Piloting Activities T5.x.1 Domain Requirements Capture and Consolidation A5.x.1.1 Functional Requirements from Use Cases and Policy Requirements from Domains A5.x.1.2 Technical Requirements for building blocks/services needed T5.x.2 Pilot Definition and Identification A5.x.2.1 Pilot Scenario definition and mapping with available BCSS building blocks A5.x.2.2 Pilot project planning A5.x.2.3 Identification and commitment of pilot site participants T5.x.3 Pilot Implementation D5.3 D5.4 D5.5 A5.x.3.1 Pilot enablement ` A5.x.3.2 Pilot running and monitoring A5.x.3.3 Pilot evaluation Three Pilot Waves going live M24,M3, M36 D5.6 A5.x.3.4 Pilot Adoption TOTAL M M6 M12 M18 M21 M24 M3 M36 D5.1 D5.7 e-sens Workplan Tasks and Timeline D5.2 D5.6 D5.3 D5.4 D5.5 Taking Stock W1P Dec. W1P Live W2P Dec. W2P Live W3P Dec W3P Live M5.1 M5.2 M5.3 M5.4 M5.5 M5.6 M5.7

9 WP5 Organisation WP Manager Domain Board Domain 5.1 eprocurement Domain 5.2 ehealth Domain 5.3 ejustice Domain 5.4 Business Life Cycle KO? KO? KO? KO?

10 WP 6 Objective The objective of WP6 is to make available a comprehensive set of building blocks for a sustainable European infrastructure for cross sector services. It is the goal that the building blocks provided by WP6 shall be modular and exchangeable of nature. The aim is to provide building blocks that are suitable for integration into existing systems in EU Member States and Associated Countries where this offers high value. Starting point is requirements and solutions from LSPs

11 Cluster Objectives SGCC 6.1 edelivery & einteraction to establish a common transport infrastructure suitable for the requirements of cross-border communication between egovernment applications in different domains. SGCC 6.2 Semantics, Processes & Documents to provide a method to create documents and electronic messages with any type of content, in any type of appearance and for any domain aimed at the exchange of information for cross border procedures. The method assures that documents and messages for multiple domains can be created out of generic building blocks.

12 Cluster Objectives SGCC 6.3 Identity, Security & Trust to create re-usable generic blocks for cross-sector authentication and creation/validation of eid and e- Signatures. Also look at issues of cross-sector / crossborder service security mechanisms and trust establishment SGCC 6.4 Conformance & Test to provide an extensible, highly available and preferably Web accessible testing infrastructure

13 Methodology

14 Overall WP6 Plan 4 D6.1 (M6) Executable ICT Baseline D6.2 (M15) Enterprise Interoperability Architecture n 1 D6.4 (M3) Architecture Evaluation 2 7 D6.3 (M24) Enterprise Interoperability Architecture n D6.5 (M36) Transfer of Operation and Ownership D6.6 (M36) Enterprise Interoperability Architecture n 3

15 WP6 Organisation WP Manager Lead Architect Architectural Board SGCC 6.1 edelivery & einteraction SGCC 6.2 Semantics, Processes & Documents SGCC 6.3 Identity, Security & Trust SGCC 6.4 Conformance & Test KO? KO? KO? KO?

16 EC Strategy Stakeholders... European Interoperability Architecture SEMIC ISA DG DIGIT LSPs (epsos, STORK II, ecodex, SPOCS, PEPPOL) Standardisation Organisations CEN UN/CEFACT OASIS ETSI

17 Nordic/Baltic Perspective Participants Sweden, Denmark, Estonia, Norway Objective Nordic esens Coordination Minimize risks (create a Nordic/Baltic infrastructure as minimum) Reuse/learn from each others solutions Create High momentum in esens Funding Nordisk Ministerråds Sekretariat esens Baltic Development Fund (EC)

18 Nordic/Baltic Perspective Capabilities Already established cooperation NES ehealth group (Nordisk Ministarråd) High technical maturity High LSP project maturity Ability to move fast Precondition Close coordination Setup of a Nordic/Baltic coordination governance

19 Nordic/Baltic Resources

20 Nordic/Baltic Perspective Today (from Søren s presentation) Pin point areas of common interest Nail down pilot candidates in the respective domains Expose challenges and potential risks Explore the possibilities of sharing resources Discuss existing or potential cooperation outside the boundaries of e-sens Map Use Cases / Pilot scenarios in domains to building blocks

21