T2S PROGRAMME STATUS AS OF MID-SEPTEMBER

Transcription

1 T2S PROGRAMME OFFICE ECB-PUBLIC AG Meeting 18/19 September 2012 Item /2012/ T2S PROGRAMME STATUS AS OF MID-SEPTEMBER Introduction In this note the T2S Programme Office provides the T2S Advisory Group with information on the current status of the T2S Programme. The note starts with the achievements made during Q2 and Q3 2012(April to mid-september 2012) and then indicates the status of deliverables (including identified risks and issues) by programme work stream and deliverable stream. Finally, the note gives detail where any work stream has a red or yellow status or risk. Further explanations regarding the reading of this report are provided in the annex. 2. Achievements As specified in the T2S Programme Plan, the following deliverables have been finalised/milestones have been reached: Q2 2012: Adoption of the Framework Agreement (FA) by CSDs in two waves o Wave 1: By 30 April 2012 (9 CSDs with approx. 65 % of euro market share) o Wave 2: By 30 June 2012 (15 CSDs with approx. 34 % of euro market share) large majority of euro area CSDs - and outside the euro area 6 CSDs - have adopted the FA. Adoption of the Currency Participation Agreement (CPA) by Danmark s National Bank. CSDs/CBs have provided their feasibility assessment Dedicated Link Connectivity Specifications v1.0 (published on 29 June 2012) T2S Public Training Framework (published on 29 June 2012)

2 Q3 2012: Confirmation of the External Network after Proof of Concept (VAN) - July 2012 Data Migration Tool Specifications v0.6 July 2012 [Basic Migration Storyline v1.0 July 2012] Composition and Timing of Migration Waves by CSDs/CBs (Migration waves common proposal by CSDs/CBs) - 03 Aug 2012 User Detailed Functional Specification (UDFS) v published on 10 Sep 2012 GUI Business Functionality Document Technical Annex - published on 10 Sep 2012 User Requirements Document (URD) v5.02 draft version published on 10 Sep 2012 User Testing Terms of Reference v1.0 July 2012 Furthermore, Synchronisation Point 2 (SP2) has been achieved - 10 Aug T2S Programme Status 3.1 Summary PROGRAMME WORKSTREAM AND SUB-STREAM STATUS CHANGE TREND RISK CHANGE CLIENT READINESS FRAMEWORK Y X - CLIENT READINESS USER TRAINING G X - USER TESTING G Y CONTRACTUAL FRAMEWORK X X PRODUCT READINESS SPECIFICATION AND DOCUMENTATION Y Y SOFTWARE AND 4CB TESTING Y Y EUROSYSTEM ACCEPTANCE TEST G G - OPERATIONAL READINESS PRODUCTION INFRASTRUCTURE G X - NETWORK CONNECTIVITY G G OPERATIONS G G MIGRATION G Y Page of 7 2

3 3.2 Client Readiness Client Readiness Framework Client Readiness Framework Y X A draft version of the Implementation Guide for Client Readiness had been delivered to the i-pmg end of May CSDs were invited to provide written feedback and sent their comments (which were substantial) on 7 Aug As follow-up it was agreed with the PMG to organise an ad hoc workshop on this matter with a view to have the document finalised by the end of the year. ISSUE Delay in the finalisation of the Implementation Guide for Client Readiness following receipt of substantial comments from CSDs early August. The agreed (already changed) delivery date (31/08/2012) could not be achieved. RESOLUTION (by Q3 2012) T2S Board has approved the proposal to set as new deadline for delivery 28/12/ User Testing User Testing (UT) G Y Since January 2012 the T2S PO has been discussing and negotiating with CSDs and CBs how the T2S UT Phase shall be organised. UT Terms of Reference v1.0 have been finalised by the T2S PO in July 2012 and submitted to PMG (30/31 Aug 2012) and T2S Board (6/7 Sep 2012) and CSG (17 Sep 2012). Based on cost, CSDs may re-consider the need for additional test environments, invalidating User Testing terms agreed with CSDs (although the revised 4CB cost estimation resulted in a substantial cost decrease (by streamlining the technical and organisational aspects). MITIGATION (by Q3 2012) The T2S Board, in order to mitigate this risk, will continue the dialogue on this matter with CSDs with a view to get approval for the additional two test environments before autumn Page of 7 3

4 CSDs and NCBs do not agree on a joint testing calendar and operational day schedule for the test environments, resulting in a re-planning of the usage of the test environments and potentially delaying the T2S Programme MITIGATION (by Q1 2013) Eurosystem, CSDs and NCBs have agreed in the User Testing Terms of Reference that they are to decide on a joint testing calendar and operational day schedule for the test environments and different stages of user testing. Eurosystem, CSDs and NCBs have agreed in principle on the usage of the test environments that caters for both slow motion and day-for-day schedule at the start of user testing. Furthermore, a dedicated substructure on user testing, in which CSDs and NCBs participate, will develop starting in autumn 2012 a User Testing Guide in which the joint testing calendar and operational day schedule for the test environments and different stages of user testing is a key component. As work is still to commence on the detailed organisation of UT, the Eurosystem will act as a facilitator to achieve the required agreement between CSDs and NCBs. 3.3 Product Readiness Specification and Documentation User Detailed Functional Specification Y Y The User Detailed Functional Specifications (UDFS v1.2.1 published on 10 Sep 2012) as well as other specification documents reflect the functional scope, based on the approved T2S User Requirements Document. Specification and development are broadly on track, but are threatened by potential scope changes triggered by the feasibility assessments performed by CSDs and CBs. Changes to the T2S functional scope may ultimately lead to a delay of the T2S go-live date, as the Programme Plan has very limited margin for implementing new functionalities (e.g. change requests arising from new requirements or different interpretations). MITIGATION (ongoing) 1. Change requests from the market to be analysed carefully with acceptance and implementation of such change requests to be kept to the absolute minimum. Change requests raised by the NCBs and the CSDs (which are not showstoppers) will be considered for implementation in a subsequent release of T2S. 2. Update of the T2S Plan to include a small buffer for unforeseen developments done -. Page of 7 4

5 The GUI may not satisfy the usability requirements of the user and may require some redesign. MITIGATION (by Q2 2013) The dialogue with the market on this matter will be continued end 2012/early 2013 when finalising the User Handbook in order to minimise potential changes. User Handbook (UHB) v1.0 Y X - ECB feedback has been received on the intermediate version 0.5 of the UHB delivered by the 4CB in May. The comments are under review for integration in the UHB v1.0 document. - Owing to the shift of some development activities to the latest iterations, the timetable for the delivery of the UHB v1.0 is very tight Software and 4CB Testing See separate status report provided by 4CB 3.4 Operational Readiness Migration Migration preparation G Y The T2S Programme Office reached an agreement with CSDs, Central Banks and the 4CB on the migration storyline which provides an overview of the overall migration process and related sequence of activities. A joint proposal of CSDs and Central Banks on the composition and timing of migration waves was received on 3 Aug This proposal is the basis for the Eurosystem s decision on the composition and timing of the migration waves which will be communicated to the market by the end of Some CSDs requested to add an additional (fourth) migration wave within the defined migration period. It is not certain that the inclusion of such an additional wave would allow for sufficient time for User Testing between the migration waves. MITIGATION (by Q3 2012) To continue discussions with CSDs. As regards the other Operational Readiness sub-streams see separate 4CB status report Page of 7 5

6 4. Conclusion With the Framework Agreement entering into force, a new governance structure has been put into place. The first meetings of the new governance bodies have taken place (PMG 30/31 Aug 2012, T2S Board 6/7 Sep 2012, CSG 17 Sep 2012) and AG (18/19 Sep 2012). On 10 Aug 2012 the Eurosystem has sent in a formal response letter to all CSDs and CBs its feedback on the feasibility assessments received (SP2). At the moment when the T2S Programme Board passes on its responsibilities to the T2S Board, the project is well on track. In the fields of User Testing and Migration discussions are still on-going and need to be finalised soon to achieve clarity on the Plan. The T2S Programme Office currently still considers as the main risk to the Plan the number of mandatory change requests ( showstoppers ) raised by the market. The change requests submitted so far have already put significant pressure on the development work. Any failure in limiting the changes to those which, if not implemented, would prevent T2S from going live, or in excluding changes that impact the T2S design, would seriously jeopardize the planned go-live date. Page of 7 6

7 Annex Reporting Structure The structure of the T2S Programme is based on work streams. Within each work stream, a work breakdown structure groups the activities and deliverables. A deliverable stream within a programme work stream is a grouping of deliverables, i.e. it aggregates a set of related deliverables for reporting purposes. Status and Risk The T2S Programme status provides traffic light reporting for both status and risk. The status evaluates a deliverable based on time, quality and scope. Colour Green Yellow Red Description Deliverable is within the required scope and quality and is on time Deliverable will not have the required scope, will be delayed and/or not of the required quality if no corrective measures are taken Corrective measures have not delivered the expected effect or no corrective measures are possible. Deliverable will be delayed to achieve the required quality or scope if no extraordinary action taken. Potential impact on T2S go-live date. The risk documents whether critical threats exist to a programme deliverable based on the criteria time, quality and scope. The existence of a risk does not affect the status of a deliverable unless it materialises. Colour Green Yellow Red [ ] Description Risks effectively managed. Threats, endangering activity or deliverable or risks are not managed effectively. Significant threats, endangering activity or deliverable, or risks are not managed. Potential delay on the T2S go-live date. Risk has already been reported previously. Page of 7 7