e-sens Nordic & Baltic Area Meeting Stockholm April 23rd 2013

Transcription

1 e-sens Nordic & Baltic Area Meeting Stockholm April 23rd 2013

2 Objectives of the afternoon parallel tracks sessions 2

3 Meeting objectives High level: Identification of shared interests with emphasis on those areas with significance for the Nordic / Baltic area stakeholders. Identification of piloting areas and distribution of Nordic/Baltic WP6-resources. Expected output: For each WP 5 domain: List of Pilot scenarios and main Use Cases Suggested common Pilot scenarios Use of Building Blocks (specifying which ones) WP 6: General description of BB s If possible: thus far known use of BB in the WP 5 Domains (map WP 6 WP 5) 3

4 Food for thoughts Pilot Pilot Pilot eservice Building Building Blocks Building Blocks Building Blocks Building Blocks Blocks Success? Applicable Applicable Standards Applicable Standards Applicable Standards Standards 4

5 but we also need - We need to acknowledge /the need for/: - Complexity - Collaboration - Alignment - Communication - Risk mitigation - Resource sharing Business Functional Pilot Scenarios Validation & Test Cases Req. model Requirements Legal Architectural design Cross-cutting (non functional) Use Cases. Project execution support 5

6 WP 5 Vision 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 To run Production pilots To execute Real transactions (Government / Business / Citizens) Create solutions for the use C2B and B2B as A2C, A2B and A2A 6

7 WP 5 Objectives To develop and maintain a Framework of Requirements for e- SENS services across Europe; To define piloting scenarios and use cases for the real-life implementation of the e-sens services across a variety of domains, countries, administrations and end users, Purpose: to prove that the e-sens building blocks defined and developed within WP6 can be re-used in a wide spectrum of domains and environments. To establish and run pilot implementation projects To coordinate, monitor and support pilot implementation projects across beneficiaries and other involved organizations Considering the their entire lifecycle To coordinate the development of requirements coming from the domains and countries involved in WP5 with the architectural framework and the technical work done by WP6 and WP 4 Validate requirements (to support WP3) /../ from a functional and organizational acceptance viewpoint. To support WP1 and WP2 in its efforts to raise awareness and drive recruitment of new piloting domains 7

8 Project Plan Year 1 WP5-6 Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 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 & Mapping with Architecture Framework Pilot Lifecycle Management, Methodology & Procedures Pilot Support & Monitioring Tools Pilot Scenario Definition & mapping with Building Blocks Pilot Project Planning & Particpation WP6 SGCC Business Modelling SGCC Requirements D6.1 Executable ICT Baseline Architecture (M6) Analysis & Design

9 WP 5 WP 6 interaction WP 5 WP5 presents requirements and specification requests to WP6 ii. WP6 provides building block design specifications to WP5 WP 6 WP 5 iii. WP5 validates design specifications so that WP6 can begin developing building blocks 9

10 WP 5 WP 6 Interaction (cont d) WP 6 v. WP5 pilots WP6 building blocks, evaluates them and their usage and validates their functional suitability and applicability as well as their compliance to WP5 requirements. WP 5 iv. WP6 rolls out building blocks to WP5 pilot sites and supports their integration into pilot site infrastructures during pilot enablement 10

11 WP 5 Baseline 1. Pilot lifecycle management methodology for planning, executing and monitoring Timeline, milestones and resources from recruitment to readiness Structured pilot support procedures and tools 2. Pilot scenario definition and development, in order to determine: Use case(s) and piloting landscape against domain(s) Infrastructure to be developed/adapted/integrated Participant organizations, type of transactions and usage 3. A pilot implementation plan is the baseline approach Project-based execution according to pilot lifecycle methodology Monitored progress along milestones, measurable results against clear and quantifiable objectives stated in defined pilot scenarios 11

12 WP 5 Execution Definition phase Deployment Phase Production Running Phase First wave pilots Second wave pilots Third wave pilots 12

13 WP 5 Criterion for selecting pilots Core prioritization principles Support key policy targets (e.g., Digital Agenda for Europe and Connecting Europe Facility) Aim for the highest value for e-sens Higher value: Use of new e-sens building blocks created through consolidation of old LSP components Lower value: Re-use of old LSP components across domains i.e. same building block used as-is elsewhere. Generally out of scope: incremental functionality in old domains, incremental advances in old components, mere expansion of MS coverage Combine domain prioritization with building block prioritization, in alignment with WP6 and WP3 priorities Adopt Key Success Indicators (KSI) as an objective baseline to quantify value Consider volume and usage as value to assess benefits for users. Domain scope prioritization order: Current LSP domains with high-value advances over the state of art that shows significant consolidation value New domains where no LSPs have been established, and where e-sens building blocks can be re-used, showing portability and a generic approach When all else is equal, prioritize old LSP domains where LSPs have finished, over those where LSPs continue Building Block scope prioritization order: New and converged building blocks with high e-sens added value Generic building blocks applicable across domains Domain/ old LSP building blocks as-is piloted in the same domain and/or in more countries not participating in previous LSPs: generally out of scope 13

14 Call to action! It is expected that Member States and Associated Countries have already identified pilot scenarios and participants at project start A mapping of Member State (MS) and Associated Countries (AC) piloting intentions to domains and WP6 building blocks will be part of the initial work on the Requirements Framework Pilot template to be used (see separate proposal) in order to identify Pilots deemed appropriate according to the selection criterion 14

15 Call to action (cont d) Mapping the use of building blocks to the domains and to each pilot being considered Listing pilot candidates according to a common template Establishing criterion for selecting pilots Finalizing the responsibilities Finalizing the Requirements Framework Harmonizing the work and the methodology, in general, in order move the work forward in a consistent way Making project tools available 15