Insight Session on T2S User Testing Dedicated Info Session on T2S User Testing and Migration: an urgent matter Frankfurt, 3 July 2013 T2S Programme Office European Central Bank 1
T2S User Testing Agenda 1 General Framework 2 User Testing Execution 3 User Testing Preparation 2
T2S User Testing Agenda 1 General Framework 2 User Testing Execution 3 User Testing Preparation 3
General Framework Introduction Monday, 22 June 2015 first CSDs and Central Banks migrate to T2S What will happen before? 4
General Framework Introduction The CSDs, Central Banks and their communities shall test without negatively impacting other testing actors The key is to bring all testing aspects in sync Actors T2S User Testing Processes Data 5
General Framework Introduction What is the context and which constraints have to be taken into account for T2S User Testing? In parallel, the User Testing will orchestrate - The testing of 23 CSDs and 19 Central Banks - In 4 migration waves/configurations in production - Over the testing period from October 2014 until February 2017 - Through 5 mandatory testing stages - On 4 T2S test environments 6
General Framework Mandatory testing stages Connectivity Bilateral Interoperability Multilateral Interoperability Community Business Day 7
General Framework Usage of T2S test environments (1) 8 Test Environment Usage Q2 2014 Q3 2014 Q4 2014 Q1 2015 Q2 2015 Q3 2015 Q4 2015 Q1 2016 Q2 2016 Q3 2016 Q4 2016 Q1 2017 Eurosystem Acceptance Testing Pilot Testing Connectivity Set-up & Testing WAVE 1 Testing Bilateral Interoperability Interoperability Multilateral Interoperability CSD Acceptance WAVE 2 Testing Bilateral Interoperability Multilateral Interoperability CSD Acceptance WAVE 3 Testing Bilateral Interoperability Multilateral Interoperability CSD Acceptance WAVE 4 Testing Bilateral Interoperability Multilateral Interoperability CSD Acceptance CSD Certification 30 May 30 Sep Remedy period in accordance with Article 38(1)(b) of the FA Overlap of Wave II and Wave III Multilateral Interoperability testing stage Wave I Go-Live Wave 2 Go-Live Additional Testing Wave 3 Go-Live Wave 4 Go-Live
General Framework Usage of T2S test environments (2) Test Environment Usage Q2 2014 Q3 2014 Q4 2014 Q1 2015 Q2 2015 Q3 2015 Q4 2015 Q1 2016 Q2 2016 Q3 2016 Q4 2016 Q1 2017 Connectivity Set-up & Testing Migration Slow Motion Bilateral Interoperability WAVE 2 Migration Test WAVE 3 Migration Test WAVE 4 Migration Test Connectivity Set-up & Testing WAVE I Testing Migration Test Community Community/Business Day WAVE 2 Community/Business Day WAVE 3 Testing Community/Business Day/Stabilisation WAVE 4 Testing Community/Business Day/Stabilisation Pre-Prod Connectivity Set-up & Testing Pre-Production tests WAVE 2 Community - Cycle 2* 30 May 30 Sep Phased-in connectivity set-up and connectivity testing for waves 2, 3 & 4 Wave 1 Go-Live Wave 2 Go-Live Wave 3 Go-Live Wave 4 Go-Live * With Liquidity Transfer Utility 9
General Framework Monitoring & Coordination How is the monitoring and coordination of User Testing ensured? Coordination during the User Testing - Programme level synchronisation points (SPs) - Multilateral stage transitions by migration wave The purpose of the synchronisation is to monitor the progress of all parties participating in the User Testing and to make sure that known dependencies are resolved at pre-defined check points SPs and multilateral stage transitions reflect the multilateral aspect of required coordination during the User Testing execution 10
General Framework Roles and responsibilities Who is involved in the preparation and execution of User Testing? User Testing Subgroup (UTSG) as PMG substructure coordinates the User Testing preparation and execution The UTSG members are CSDs, Central Banks and Eurosystem CSD participants and payment banks are involved through observers and their relevant CSDs and Central Banks The UTSG analyses, prepares and defines the various user testing activities and supporting processes 11
General Framework Roles and responsibilities How are roles & responsibilities assigned during User Testing? Eurosystem Manage the User Testing preparation Coordinate and support the User Testing execution (all activities) CSDs, Central Banks Participate in the User Testing preparation Participate in the User Testing execution in the various testing stages Coordinate the User Testing execution of its community covering indirectly connected parties (ICP) as well as directly connected parties (DCPs) CSD Participants, Payment Banks Participate in the User Testing execution according to the testing plan of the relevant CSDs and Central Banks 12
T2S User Testing Agenda 1 General Framework 2 User Testing Execution 3 User Testing Preparation 13
User Testing Execution Actors User Testing Actor Testing activities Participate in all testing stages CSDs and Central Participate in the migration testing Banks Coordinate and support the testing activities of their communities CSD participants and Payment Banks Eurosystem DCPs participate in the Connectivity testing stage DCPs and ICPs participate in the Community and Business Day testing stages DCPs and ICPs participate in the migration testing Monitor the test environments Deploy the new bug fix releases Execute the specific testing requests from the CSDs and Central Banks: snapshot, purge, reload, etc. Coordinate and support the testing activities 14
User Testing Execution Data segregation T2S is a multi-entity settlement application that enables cross- CSD settlement: T2S Operator CSD 1 CSD 2 Central Bank 1 Central Bank 2 During the bilateral testing, CSDs and Central Banks can set up mock entities in order to test independently of each other: T2S Operator CSD 1 Mock CSD 2 Mock Central Bank 1 Mock CSD 1 CSD 2 Mock Central Bank 2 Group entities of CSD 1 Group entities of CSD 2 15
User Testing Execution Processes overview Testing Tools Liquidity Transfer Utility Snapshot, purge and reload Data Migration Tool Processes Monitoring of testing Incident Management Defect Management Release Planning Deployment Management Testing Activities Connectivity testing Bilateral Interoperability testing Multilateral Interoperability testing Community testing Business Day testing Migration testing 16
User Testing Execution Testing Activities mandatory testing stages Connectivity CSDs and Central Banks Validate the proper setup and configuration of all connectivity related aspects, to ensure that the actor s systems and T2S can communicate via A2A and/or U2A Bilateral Interoperability CSDs and Central Banks Test bilaterally with T2S the adaptation of their internal systems to T2S, i.e. the interaction between their systems and T2S Multilateral Interoperability CSDs and Central Banks Test the interaction between multiple parties using T2S, e.g. cross-csd settlement, auto-collateralisation, etc. 17
User Testing Execution Testing Activities mandatory testing stages Connectivity DCP Validate the proper setup and configuration of all connectivity related aspects, to ensure that the actor s systems and T2S can communicate via A2A and/or U2A Community CSDs, CBs, communities Test the adaptation of participants internal systems to T2S and the updated systems of the CSDs/CBs upon involvement by the CSDs and CBs Business Day CSDs, CBs, communities Test the adaptation of participants internal systems to T2S based on the production schedule and similar to the day-to-day business 18
User Testing Execution Testing Activities migration testing Migration tests are performed in parallel to functional tests Several migration rehearsals will be executed with and without the community and repeated until they can be successfully executed Bilateral migration testing Multilateral migration testing without the community Multilateral migration testing with the community To validate the quality of the migrated data To validate before involving the community, the migration processes and the migration timing in executing several migration rehearsals with a limited set of data and also with the production data volume To validate with the community the migration processes and the migration timing in executing several migration rehearsals with the production-like conditions 19
User Testing Execution Additional activities in parallel to User Testing Acceptance testing Optionally, the CSDs could test T2S in order to bilaterally confirm to the Eurosystem whether T2S complies with the T2S Service Description and the T2S Scope Defining Set of Documents Certification testing The CSDs, Central Banks and DCPs have to complete the Eurosystem Certification testing based on the certification test cases defined by the Eurosystem Authorisation testing In addition to completing the Eurosystem Certification, DCPs might have to complete authorisation tests defined by the respective CSD / Central Bank to receive the authorisation to directly access T2S for the business with this CSD/Central Banks 20
User Testing Execution Processes Whether and what shall I do in certain situations? The aim of the User Testing Processes is to ensure that all Actors know how certain standard situations are managed Who shall do something When shall they do something What shall they do - Bilaterally with the Eurosystem - Multilaterally with the Eurosystem and other CSDs and Central Banks Test Managers in the User Testing Subgroup 21
User Testing Execution Key aspects of major User Testing processes Monitoring of User Testing - The proactive monitoring of the testing progress - Early identification of potential issues and problems Release Planning and Deployment Management - Agreement on bundling of defect resolutions and timing of their deployment to the test environments - The bug-fix releases are deployed to test environments in fixed sequence Eurosystem (4CB) Acceptance Test Environment Interoperability Test Environment Migration Test Environment Community Test Environment Pre-Production Test Environment Production Environment 22
User Testing Execution Key aspects of major User Testing processes Incident Management - Specify how and when testing actors receive information on incidents and other technical issues on test environments and on their resolution Defect Management - Ensure that all identified T2S defects are logged, prioritised and their resolution planned 23
User Testing Execution Testing tools The snapshot, purge and reload utilities - Capture, delete and store the data of a group of system entities on a test environment The Data Migration Tool - Allow CSDs and Central Banks to migrate their business data from their internal systems to T2S in order to, inter alia, set-up and align the test environments The liquidity transfer utility - Inject liquidity to the dedicated cash accounts to emulate an RTGS system during User Testing 24
T2S User Testing Agenda 1 General Framework 2 User Testing Execution 3 User Testing Preparation 25
User Testing Preparation Current status 26 Where are we today? 2009 2010 2011 2012 2013 2014 2015 2016 2017 Concept User Testing Preparation Phase User Testing Execution Phase Today Migration Period T2S Go-Live of 1 st wave
User Testing Preparation User Testing phases Phase Description Status Concept Elaborate on User Testing strategy Completed User Testing Preparation User Testing Execution Define the organisation of testing activities and processes required for: - the User Testing Execution Phase - the period after the end of the User Testing Execution Phase Prepare and design all necessary documentation Execute User Testing following the organisation of testing activities and processes for the User Testing Execution Phase In progress Not started 27
User Testing Preparation The UTSG s main deliverables User Testing Terms of Reference - Outlines the principles for the organisation and structure of the testing stages User Testing Process Guide - Detailed processes for facilitating and organising the execution of User Testing User Testing Calendar - Information on the organisation and availability of the test environments User Testing Reporting Framework - Defines the content and templates for different User Testing reports Migration Testing Approach and Plan - Defines the testing organisation for migration processes and tools and scheduling of different test scenarios for pre-migration and migration weekend processes per wave 28
29 Thank you for your attention www.t2s.eu