1

T2S Manual of Operational Procedures (MOP)Current Status and Way forward

T2S Programme OfficeEuropean Central Bank

Item 6.2, T2S Advisory Group meetingFrankfurt am Main, 18th and19th November 2013

Table of contents

1 Manual of Operational Procedures (MOP)

2 Operations Managers Group (OMG)

3 Issues related to MOP of relevance for AG

2.1

Work organisation2.2

Delivery of the MOP2.3

Current work status

3.1

Role of the AG in approval of the MOP

3.2

Crisis Management – Decision-making process

3

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.

Manual of Operational Procedures (MOP)Purpose and scope

4

Operations Managers Group (OMG)Work organisation

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)

Release 2 - September 2014 – after OMG approval, including all modules, for subsequent approval by the Governing Council

5

Operations Managers Group (OMG)Delivery of the MOP

Operational Procedures in Normal& Abnormal Situations - Phase II

Operational Procedures in Normal& Abnormal Situations - Phase II

Incident Management

Incident Management

Service LevelManagementService LevelManagement

CrisisManagement

CrisisManagement

Change, Release & DeploymentManagement

Change, Release & DeploymentManagement

Service ContinuityManagement

Service ContinuityManagement

ProblemManagement

ProblemManagement

FundamentalsFundamentals Operational Procedures in Normal & Abnormal Situations - Phase 1

Operational Procedures in Normal & Abnormal Situations - Phase 1

Request FulfilmentRequest Fulfilment

Access ManagementAccess Management

MO

P R

ele

ase –

1 D

elivera

ble

sM

OP

Rele

ase –

1 D

elivera

ble

s

1

2

3

4

5

6

7

8

9

10

5.1

MO

P R

ele

ase –

2 D

elivera

ble

sM

OP

Rele

ase –

2 D

elivera

ble

s

Operational Procedures in Normal & Abnormal Situations – updates

Operational Procedures in Normal & Abnormal Situations – updates

Information SecurityManagement

Information SecurityManagement

Operational RiskManagement

Operational RiskManagement

Service Validationand Testing

Service Validationand Testing

Business Relationship Management(Client Relationship Management)

Business Relationship Management(Client Relationship Management)

Financial Management (Invoice Management)Financial Management (Invoice Management)

5.2

11

12

13

14

15

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

Split into release 1 and 2 ensure that, in the light of intensive work, those MOP modules which are relevant for User Testing are delivered in April 2014

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

6

Operations Managers Group (OMG)Current work status

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

7

Issues related to MOP of relevance for AGRole of the AG in approval of the MOP

Background

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? (CSDs proposed to limit the participation in order to allow for an efficient decision making)

• In case no consensus can be reached during the Crisis Managers’ telco, who takes 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

8

Issues related to MOP of relevance for AGCrisis Management – Decision-making process

• To provide operational guidance to all participating T2S Actors onthe communication & handling of a crisis situation• To provide operational guidance to all participating T2S Actors onthe communication & handling of a crisis situation

Purpose of MOP ModulePurpose of MOP Module

• 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

• 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

Module Coverage (High Level) Module Coverage (High Level)

www.t2s.eu

Thank You