T2S Manual of Operational Procedures (MOP)
Current Status and Way forward
Item 6.2, T2S Advisory Group meeting
Frankfurt am Main, 18th and19th November 2013
T2S Programme Office
European Central Bank
0
Table of contents
1 Manual of Operational Procedures (MOP)
2 Operations Managers Group (OMG)
2.1 Work organisation
2.2 Delivery of the MOP
2.3 Current work status
3 Issues related to MOP of relevance for AG
3.1 Role of the AG in approval of the MOP
3.2 Crisis Management – Decision-making process
Manual of Operational Procedures (MOP)
Purpose and scope
 Purpose and nature of the Manual of Operational Procedures (MOP)
 The MOP describes the day-to-day T2S operational procedures for T2S Actors (CSDs, CBs (incl. ECB), DCPs, the
4CB and the T2S Coordination function)
 The description of the T2S Service processes and procedures is based on the best practices described in the
Information Technology Infrastructure Library (ITIL® V3)
 The MOP shall be of a lean nature, only pointing out important activities within client context
 The MOP itself is not legally binding but is based on legally binding documents (Framework Agreement, Currency
Participation Agreement, T2S Scope Defining Set of Documents). It is assumed that T2S Actors (excluding ICPs),
comply in good faith with the processes and procedures set out in the MOP.
 Scope and Structure of the T2S MOP
 It shall cover the operational procedures aimed for T2S Actors (excluding ICPs), namely:
• activities to ensure the smooth and reliable processing of T2S under normal circumstances, and
• activities aiming to restore proper functioning of the T2S Service by mitigating the effect of incidents.
 The primary objective is to document operational procedures for live operations. However, the MOP also
serves as a reference for testing and migration activities.
2
Operations Managers Group (OMG)
Work organisation
Operations
Managers
Group
(OMG)
Forum:
Members being managers responsible for operations in CSDs, NCBs, 4CB/T2S as well as
T2S PO
Observers representing the DCPs
Meetings:
Physical meetings on a quarterly basis
In case of need, ad-hoc teleconferences
Tasks:
OMG
Drafting
Group
Development (T2S project phase) and maintenance (T2S operational phase) of the T2S MOP
Proposal for relevant KPIs after the bedding-down period
Reviewing the T2S Service performance against the SLA
Coordinating the ex-post analysis of operational incidents
Forum:
Smaller group composed of operational experts nominated by CSDs and NCBs
participating in the OMG, as well as 4CB/T2S PO representatives
Meetings:
Physical meetings on a monthly basis
In case of need, ad-hoc teleconferences
Tasks:
Drafting of the T2S MOP
3
Operations Managers Group (OMG)
Delivery of the MOP
 Delivery of the Manual of Operational Procedures
 Release 1 - April 2014 – after OMG approval, those modules which are relevant for the User Testing preparation
(6 months prior to the start of User Testing)
1
Fundamentals
5
Operational Procedures in Normal
& Abnormal Situations - Phase 1
5.2
Operational Procedures in Normal
& Abnormal Situations – updates
2
Incident
Management
6
Service Level
Management
11
Information Security
Management
3
Crisis
Management
7
Change, Release & Deployment
Management
12
Operational Risk
Management
4
Service Continuity
Management
8
Problem
Management
13
Service Validation
and Testing
14
Business Relationship Management
(Client Relationship Management)
15
Financial Management
(Invoice Management)
5.1
Operational Procedures in Normal
& Abnormal Situations - Phase II
9
Request Fulfilment
10
Access Management
MOP Release – 2 Deliverables
MOP Release – 1 Deliverables
 Release 2 - September 2014 – after OMG approval, including all modules, for subsequent approval by the
Governing Council
4
Operations Managers Group (OMG)
Current work status
 Overall status:
 Work is progressing according to the revised OMG work plan (more time required than originally envisaged for
finalisation of the modules)
 In order to streamline discussions within the OMG Drafting Group, a written procedure has been introduced to
collect feedback on the modules
 Following the ‘Yellow’ risk that MOP in its full scope cannot be delivered in April 2014, as a mitigation measure,
it was agreed to split the delivery of the MOP into a release 1 and 2 ensuring that those MOP modules which
are relevant for User Testing are delivered in time
 Delivery of the Manual of Operational Procedures
 Release 1
•
Scope of the release 1 modules is defined
•
OMG reviewed 8 modules, considering 4 of those as stable, and agreed with the identified open Action
Points
•
Remaining 3 draft modules are under OMG Drafting Group consideration
 Release 2
•
Scope of the release 2 modules under discussion
5
Issues related to MOP of relevance for AG
Role of the AG in approval of the MOP
 After preparation of the T2S Manual of Operational Procedures by the OMG:
 the MOP will be submitted to the T2S Board
 the CSD Steering Group (CSG) and Non-euro Currency Steering Group (NECSG)
will be consulted
 the Advisory Group (AG) can be invited to give advice, in case the T2S Board or the
CSG see a need for it e.g. on aspects that have implications on DCPs or crisis
management
6
Issues related to MOP of relevance for AG
Crisis Management – Decision-making process
 Background
Purpose of MOP Module
• To provide operational guidance to all participating T2S Actors on
the communication & handling of a crisis situation
Module Coverage (High Level)
•
•
•
•
•
High level Crisis Management process flow
Details on Crisis Management Telco and their participants
Crisis Simulation and Reporting
Crisis communication channels and
Interfaces and dependencies to other processes
 Decision-making process during a Crisis situation was identified as the most crucial open Action Point
 The OMG Drafting Group considered various principles and asked for OMG guidance on the below aspects:
•
Should the Crisis Managers’ telco consist of all Contracting CSDs and CBs. There is a concern about the
practicalities of a crisis management telephone conference with so many participants (50+ persons)
•
In case no consensus can be reached during the Crisis Managers’ telco, who takes the final decision. The
majority of OMG participants are of the view that the business owner should take the final decision. The
Eurosystem is of the view that the ECB Crisis Manager as chair of the telco.
 OMG resolution (5th meeting on 29 October 2013)
 CSDs and the Eurosystem will formulate their proposals on the matter
 Way forward
 Based on these proposals, the Eurosystem will prepare a note for consideration at the Steering Level in
December 2013
7
Thank You
www.t2s.eu