Transcript SGCC 6.1 Kick-off

SGCC 6.1 Kick-off
Project Setup
Introduction
• Tour de Table
– Who’s who
– Attendance list, e-mails
• Scope of CC 6.1
What is e-Delivery?
• Cross-border, cross-enterprise business integration
–
–
–
–
Modern, service-oriented approach
Support standard business processes and structured content
Typically, sender and receiver are business applications
B2G, B2B, G2G communication, used in mature domains
• Electronic mail Cross-border communication with citizen
– Email-like exchanges with more unstructured content and natural
language content
– Standardized forms with coded values can help alleviate language
barriers
• Common Challenges
– Secure and reliable exchange of arbitrary content
– Authentication, Signature, Non-Repudiation, Legal validity
e-Delivery Convergence
http://www.e-codex.eu/about-the-project/technical-background/e-deliveryconvergence.html
• Synchronous/Asynchronous, cross-border
vs inside one country
• Hopefully using the same technology
What’s been done
• First meeting with the commission and LSPs in January
2011
• Input from PEPPOL, SPOCS and SDOs to e-CODEX eDelivery WP in February 2011
• First meeting of “Task Force” in Juli
• August 2011 publication of “Scenario document”
• Consolidation in meeting with the EC in September
• e-Government conf in Poznan Nov 2011-- e-CODEX joins
BDX
• 2nd Task Force meeting January 2012
• BDX TC face2face meeting in Sept 2012
• 3rd Task Force meeting in Sept 2012 – EESSI joins Task
Force
• BDX TC face2face meeting in April 2012
• April 2013 Kickoff e-SENS
Converged Solution
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.1: eProcurement
5.3: e-Justice
5.2: e-Health
5.4: Business
life-cycle
5.5: New
domain
WP5: Piloting
WP6: Building blocks Provision
6.1: e-Delivery & eInteraction
6.2: Semantics,
Processes and
Documents
6.3: Identity,
Security and Trust
6.4: Conformance &
Tests
Project Plan Year 1 – WP5-6
Apr
M1
May
M2
Jun
Jul
M3
M4
Aug
M5
Sep
M6
Oct
M7
Nov
Dec
M8
M9
Jan
Feb
Mar
M10
M11
M12
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
SGCC Business Modelling
SGCC Requirements
•D6.1 Executable ICT
Baseline Architecture (M6)
Analysis &
Design
Deliverables
• D6.1 Executable ICT Baseline Architecture R
PU Month 6
• D6.2 Enterprise Interoperability Architecture n°1
SP PU Month 15
• D6.3 Enterprise Interoperability Architecture n°2
SP PU Month 24
• D6.4 Architecture Evaluation R PU Month 30
• D6.5 Transfer of Operation and Ownership SP
PU Month 36
• D6.6 Enterprise Interoperability Architecture n°3
SP PU Month 36
R = Report, SP = Specification / PU = Public
• Requirements in Terms of MS solutions
• Default Backend Interface
Work assignment for
Inception phase (4 months)
• Abstract Business Process Description
(Technical Use Case)
• Requirements (Technical)
• Stock Taking
– Results from Previous LSPs, OASIS, ETSI
– PEPPOL, SPOCS, e-CODEX => e-Delivery
Convergence
– Generalize to other domains, Gap Analysis
• Scoping
Later Tasks
• Elaboration phase
– Identification of Components (for e-Delivery
Infrastructure)
– Specification
• Construction phase
– Development
• Transition phase
– Deployment and Sustainabilty
Resources & Planning
• 250 PM total / 36 months -> 7 Full-time
people per month
• 13 countries
SGCC internal processes
• Communication
– TelCos
– Web Conferences
• Change Management
– Deliverables Review Cycles, Process
– (Jira)
• Risk Management
Tools
• Cooperation
– BSCW
• Time tracking
• Development
– Jira (Deliverables and Source Code)
– Git
Meetings
• Announcement
– Who
– Agenda
– Materials
• Minutes
• How many, When
– 2-3 per year
– 1st meeting May, 2nd probably Sept
Monitoring
• Work Results / Documents / Deliverables
• Time logging
Mailing lists
…[email protected]
Groups
Work Packages
•general: all project members
•pd: primary / deputy
•aa: admin aspects
•info: information
•mb: management board
•pb: policy board
•ab: architectural board
•db: domain board
•wp1
•wp2
•wp3
•wp4
•wp5
-wp5.1-wp5.4
•wp6
-wp6.1-wp6.4
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
and so on…
Stakeholders
• …
Where to look:
MS
EC
Standards
other initiatives
Taking stock
Brainstorm on "Taking
stock"
Thank you for your
attention
• [email protected]
• [email protected]
• [email protected]