You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Current »


Transition to Service Plan

1: Technical Product delivery 

May-Mid June.

a) Technical delivery of release of product offering as agreed in meeting 17th May.

b) Finalise roadmap for delivery of next release post launch (continuous improvement)

Mid June →

c) Finalise relevant documentation for gate (see gate deliverables technology aspects).

2. Business/Service Transition

Based on the initial product offering agreed at technical product delivery phase, the overall vision and the roadmap

Mid June → 

a) Finalise business models

b) Finalise non technical aspects of service offer (especially consultancy/support on bespoke option)

c) Prepare relevant documentation for gate.

3. Operations Transition

Based on the initial product offering agreed at technical product delivery phase, and requirements from service definitions and roadmap

Mid June →

a) Finalise operational models

b) Confirm operator & staffing

c) Prepare relevant operational documents based on product, service and ops model (see gate deliverables checklist)


Gate Deliverables Checklist

Business/Service Aspects Ann HardingAlan Lewis

Technology Aspects

Operational Aspects (Mihály Héder, Michael Schmidt (TBC with Michael) TBD from SA2/GEANT)

  • Operational Requirements: Mihály Héder, TBD from SA2/GEANT

  • Operational Documentation (as above)
  • Operational Processes (as above)
  • OLA (as above plus Niels van Dijk). Note, OLA in this sense is the requirements we would expect from an operator.
  • User Support (Mihály Héder plus SA2/SA3 TBD)


Business/Service Transition

Cost Benefit Analysis

Service Description

Service Policy

Branding & Visibility

Pilot Plan Review


Technology/Infrastructure

Roadmap

Design Docs

Service Description (infra components)

Operational Requirements

Operational Docs

Operational Procs

OLA

User Support



  • No labels