Insight Session: T2S User Testing and Migration

Transcription

1 Insight Session: T2S User Testing and Migration T2S Info Session Vienna, 5 October 2012 T2S Programme Office European Central Bank ECB-PUBLIC 0

2 Agenda 1 T2S User Testing 2 T2S Migration 1

3 User testing in context of T2S How to understand user testing in the context of other T2S phases? It is the first testing phase involving users following Eurosystem internal tests Main objective of user testing is to ensure that the T2S platform meets the user requirements After completion of user testing the migration of a particular wave is conducted Specification and Development Eurosystem Testing Phase User Testing Phase Migration Phase MAC IAC EAT Pre-Migration Module Acceptance Test (4CB) Integration Acceptance Test (4CB) Eurosystem Acceptance Test (ECB) Migration Weekend 2

4 Overview - User testing stages How is the user testing phase structured? User testing is conducted in several distinct stages This allows for gradual increase of test case complexity and number of testing participants User Testing Phase Connectivity Bilateral I/O Multilateral I/O Community BD Connectivity and Bilateral Interoperability Testing: CSD/CB testing of connectivity and T2S functionalities Multilateral Interoperability Testing: Joint CSD/CB testing of T2S functionalities according to wave composition Community and Business Day Testing: CSD/CB testing with their communities according to wave composition 3

5 Characteristics of user testing stages (I) What are the characteristics of each user testing stage? Connectivity Testing Set-up of connection to T2S test environments via the Value Added Network or Dedicated Link Verification of communication with the T2S test environment through out limited set of test cases Bilateral Interoperability Testing Individual CSD/CB testing of T2S functionalities with the aim to validate adaptation to the T2S system and to pass certification tests No real interaction between T2S actors (e.g. only mock CSDs and mock CBs established on the test environment) Multilateral Interoperability Testing Testing of T2S functionalities between CSDs and CBs Cross-border testing according to the wave configuration (e.g. all CSDs and CBs involved in one migration wave to test jointly) 4

6 Characteristics of user testing stages (II) What are the characteristics of each user testing stage? Community Testing End-to-end testing of T2S functionalities with other CSDs, CBs and their clients (community) Cross-border testing according to the wave configuration with full community Business Day Testing Simulation of several consecutive business days of operation with CSDs, CBs and their clients Validation of the migration weekend under production-like conditions (according to wave configuration) 5

7 User testing stages and related activities (I) Which activities are foreseen during the user testing stages? The actual activities depend upon your business role in the T2S context Connectivity Bilateral Interoperability CSDs and Central Banks Connect Test T2S functionalities Obtain Eurosystem Certification Multilateral Interoperability Test T2S functionalities according to wave configuration DCPs (Directly Connected Parties): CSD Participants and Payment Banks ICPs (Indirectly Connected Parties): CSD Participants and Payment Banks Not involved Not involved Not involved Not involved Not involved Not involved 6

8 User testing stages and related activities (II) Which activities are foreseen during the user testing stages? The actual activities depend upon your business role in the T2S context CSDs and Central Banks DCPs (Directly Connected Parties): CSD Participants and Payment Banks ICPs (Indirectly Connected Parties): CSD Participants and Payment Banks Community Test T2S functionalities with their community (end-to end) according to wave configuration Connect Test T2S functionalities Obtain Eurosystem Certification Obtain CSD/CB Authorisation Execute test cases (through CSD/CB) Business Day Migration rehearsals with community Contingency tests Operational procedures Execute test cases and operational procedures (additionally through CSD/CB in ICP role ) Execute test cases and operational procedures (through CSD/CB) 7

9 Eurosystem certification vs. CSD/CB authorisation What is the difference between Eurosystem certification and CSD/CB authorisation and why is it required? Eurosystem Certification CSDs, CBs and DCPs have to conduct a series of mandatory test cases in order to be certified by the Eurosystem These test cases aim at ensuring that T2S actors do not harm T2S in the broad sense CSD/CB Authorisation Only required to be obtained by DCPs In addition to the Eurosystem certification, CSDs and CBs may have additional requirements and may define additional test cases to be conducted by their DCPs in order to allow them to use T2S 8

10 User testing Roles and responsibilities (I) Who is involved in the preparation of user testing? User testing preparation is conducted by the UTSG (User Testing Subgroup) The UTSG analyses, prepares and defines the various testing stages and supporting processes The UTSG consists of Eurosystem, CSD and CB representatives and reports to the PMG CSD participants and payment banks are involved through their relevant CSDs and CBs 9

11 User testing Roles and responsibilities (II) How are roles & responsibilities assigned during user testing? Roles and responsibilities during preparation and execution are summarised below: Eurosystem Manages the user testing preparation Coordinates and support the user testing execution (all stages) CSDs, CBs Participate in user testing preparation Actively participate in user testing execution (all stages) Coordinate the testing activities (preparation and execution) with their community in the community and business day testing stages CSD Participants, Payment Banks Actively participate in user testing execution of community and business day testing according to the plan of the relevant CSDs and CBs 10

12 User testing Status update What is the latest status with respect to user testing preparation? On 30 August 2012 the PMG endorsed the User Testing Terms of Reference (TOR) V1.0, which were approved by the T2S Board on 6 September topics have been identified requiring further work within the UTSG in order to achieve clarity and timely completion of deliverables Initial user testing timelines have already been drafted to support the composition of migration wave discussion Further elaboration of the user testing preparation, interactions between CSDs, Central Banks and their participants may be required 11

13 Considerations for user testing planning Which factors have been used for the current planning of user testing execution? The planning exercise of user testing involved several factors: - Envisaged testing stages - Migration following a wave approach - Availability & amount of test environments - Number & role of the various stakeholders 12

14 Draft user testing schedule Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q WAVE 1 WAVE 2 WAVE 3 Connectivity Bilateral I/O Multilateral I/O Community Business Day Connectivity Bilateral I/O Multilateral I/O Community Business Day Connectivity Bilateral I/O Multilateral I/O Community Business Day Disclaimer: This illustration shows a sample timeline of testing stages and as such should not be considered as final. Go live: 22/06/ 2015 Go live: 01/02/2016 Go live: 18/07/

15 User testing support by already migrated CSDs and CBs Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q Connectivity Support to wave 2 Support to wave 2 and 3 Support to wave 3 WAVE 1 Bilateral I/O Multilateral I/O Community Business Day Connectivity WAVE 2 Bilateral I/O Multilateral I/O Community Business Day Connectivity WAVE 3 Bilateral I/O Multilateral I/O Community Business Day Disclaimer: This illustration shows a sample timeline of testing stages and as such should not be considered as final. 14

16 Software release during user testing execution Is it foreseen to promote new T2S software releases during the user testing execution phase? No new functionality is expected to be released during user testing execution phase Bug fixes may be released if applicable only 15

17 User testing Main contacts Who will be my main contact during user testing in T2S? CSDs and CBs The Eurosystem will be the main contact for CSDs and CBs CSD Participants CSDs will be the main contact for banks acting as CSD participants in the T2S context Payment Banks CBs will be the main contact for banks acting as payment bank in the T2S context Banks which are acting as CSD Participant and Payment Bank simultaneously Relevant CSDs (securities part) and CBs (cash part) will be the contacts for those institutions 16

18 Agenda 1 T2S User Testing 2 T2S Migration 17

19 Migration in context of T2S How to understand migration in the context of other T2S phases? During the migration phase CSDs are migrating their business from their legacy systems to the T2S platform The migration phase is conducted following the completion of user testing In order to prevent a big bang approach the migration is executed in waves During the migration execution a three months pre-migration period is distinguished from the actual migration weekend Specification and Development Eurosystem Testing Phase User Testing Phase Migration Phase Pre-Migration Migration Weekend 18

20 Migration - Objectives and scope How is the objective and scope of the T2S migration defined? The T2S migration objective is to enable a smooth and successful transition to the usage of T2S services for the CSDs, CBs and their communities The scope of the T2S migration covers two dimensions: Actors: All T2S stakeholders who will connect to T2S during the migration period i.e. CSDs, CBs, CSD participants and payment banks Activities: All activities that prepare, steer and monitor the migration process into the T2S production environment, e.g. the upload of static data and the preparation of the migration weekend 19

21 Migration Organisational framework How is the migration organised? The migration activities are organised in the following four phases: 1. Conceptual phase (completed): Elaboration of migration strategy and generic migration plans 2. Preparation phase (work in progress): Detailed planning & preparatory work for the preparation of all individual migrations 3. Implementation phase: Execution of migration activities prior to and during the migration weekends 4. Closing phase: Reporting on the results of each migration wave and reflection on lessons learned 20

22 Migration Roles and responsibilities (I) Who is involved in the preparation phase of the migration? Migration preparation is conducted by the MSG (Migration Subgroup) The MSG analyses, prepares and defines the various migration activities and supporting processes The MSG consists of Eurosystem, CSD and CB representatives and reports to the PMG CSD participants and payment banks are involved through their relevant CSDs and CBs 21

23 Migration Roles and responsibilities (II) How are roles & responsibilities assigned during migration? Roles and responsibilities during the preparation, implementation and closing phase are summarised in the following: Eurosystem Manage the migration preparation Coordinate and support the migration implementation and closing (all activities) CSDs, CBs Participate in migration preparation Execute the migration of CSD/CB business to the T2S platform Coordinate and execute the migration of its community s business to the T2S platform CSD Participants, Payment Banks Support the migration preparation and execution according to the plan of the relevant CSDs and CBs 22

24 Migration - General approach and pre-agreed principles Which migration approach is followed for T2S and under which preagreed principles is the migration to be executed? A phased by CSD migration approach is to be implemented The migration will be organised targeting a maximum number of 4 waves A period of minimum 3 months between the waves is to be ensured One additional contingency wave is foreseen to take place not later than 6 months after the last migration wave A period of maximum 18 months between the T2S Go-live date (i.e. for wave 1) and the contingency wave migration weekend is envisaged No CSD/CB can be enforced to migrate earlier than their indicated preferred date 23

25 Migration Draft high-level schedule How could the high-level migration schedule look like? The following high-level view on the migration phases is under discussion: Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Migration Phase Contingency Phase Pre- Migration Periods 8 months 5 months 5 months [W1] Jun 2015 [W2] Feb 2016 [W3] Jul 2016 [CW] Jan 2017 Disclaimer: This illustration shows an example of the migration timelines and as such should not be considered as final. 24

26 Migration Status update What is the latest status of the migration preparation? On 30 August the PMG endorsed the Basic Migration Storyline as well as the a baseline version of the DMT (Data Migration Tool) Specification, which were approved by the T2S Board on 6 September 2012 The MSG identified 14 deliverables relevant for the migration preparation, implementation and closing phases requiring further work within the subgroup Inter alia: discussions on the composition and timing of migration waves are in progress and to be finalised in due course CSDs and Central Banks participating in the MSG are informing their communities of the progress accomplished. Furthermore, selected banks have been involved in the composition and timing of migration wave discussion Further elaboration on the migration preparation and interactions between CSDs, Central Banks and their participants are foreseen 25

27 Migration Key deliverables Which are the key deliverables the MSG is currently working on? The following two key deliverables are in the focus of the MSG work currently: 1. Detailed Migration Storyline Description of all generic activities, deadlines and procedures according to which all relevant T2S Actors will migrate to T2S Covering the pre-migration period as well as the migration weekend 2. DMT Specifications and Related Procedures Description of requirements for the DMT which is to ease and secure the migration process, e.g. defining the data coverage of the DMT (dynamic and static data objects) Covering also the procedures to be applied and respected for the use of the DMT 26

28 Migration Main contacts Who will be my main contact for the migration to T2S? CSDs and CBs The Eurosystem will be the main contact for CSDs and CBs CSD Participants CSDs will be the main contact for banks acting as CSD participants in the T2S context Payment Banks CBs will be the main contact for banks acting as payment bank in the T2S context Banks which are acting as CSD Participant and Payment Bank simultaneously Relevant CSDs (securities part) and CBs (cash part) will be the contacts for those institutions 27

29 Thank you for your attention