Availability and schedules of the customer simulation
The CBF customer simulation environment (IMS23) is connected to the T2S Pre-Production environment (UTEST). The comprehensive processing of test cases demands the availability of both test environments. Additionally, the test schedule that is applicable for a desired test day (that is, either T2S Synchronised Standard Day, T2S Change Request Test Day or T2S Release Day) must be considered for a successful execution.
The below graphic provides a forecast for the different customer simulation periods until July 2023.
To enlarge click on the image
- During the CBF Free Simulation customers can execute test cases on their demand.
- CBF regularly offers a Guided Customer Simulation. This is applicable for T2S minor and major releases if the introduction of a CBF project requires market readiness activities or if the scope of the new service needs dedicated test cases. Customer simulation:
- Will restart for the project Corporate Actions Harmonisation (CAH) - KADI DE Migration to OneClearstream Asset Servicing (OneCAS), also named (CAH - KADI DE migration), as soon as the revised implementation timeline has been confirmed. A further test cycle is in preparation.
- Is planned to be offered for the migration of CBF Fileservice to ClearstreamXact - depending on the test cycle for the CAH project - during the period from 27 February to 24 March 2023. Customers wishing to participate in this guided simulation are asked to register. Registration is required in order to set up the necessary configuration in the CBL test environment (OCCT). The form will be made available in time on the Clearstream website.
The CBF customer simulation environment (IMS23) and the T2S Pre-Production environment (UTEST) are regularly updated for deployment activities. Therefore, on the business day prior to the deployment activities, with the end of day procedures, CBF will close all connectivity channels towards IMS23 and UTEST.
Based on the CBF implementation schedule, IMS23 is planned to be closed from:
- 22 December 2022 to 2 January 2023; and
- 7 April to 5 May 2023.
In addition, maintenance activities are required. Therefore, on every Friday, after 14:00, testing will not be conducted as software updates will be installed. Additional downtimes might become necessary due to deployment activities by T2S and/or CBF.
Instructions can be entered or transmitted depending on the customer’s connectivity mode. Customers acting in ICP mode provide their instructions via CASCADE Online functionality (HOST/PC) or use an automated connectivity channel (SWIFT, MQ, File Transfer) to IMS23.
The current planning for the UTEST shows the following dedicated test cases that are executed under the control of T2S or ECB. The test execution impacts the processing of the "T2S Synchronised Standard Day". Test cases performed by CBF customers can therefore not be processed on UTEST as usual. As a result, the related settlement reporting cannot be transferred via T2S or CBF according to the regular test schedule:
- 25 January 2023: Delay in the start of NTS test case;
- 8 and 9 February 2023: AID tool testing;
- 22 March 2023: Insolvency of CSD/NCB participant testing;
- 31 May 2023: OMEGA tool testing;
- 14 June 2023: Insolvency of CSD/NCB participant testing;
- 12 July 2023: Data integrity full test; and
- 26 July 2023: Delay in RTGS start (processing without liquidity).
In preparation of the implementation of the T2 / T2S consolidation project in March 2023, the liquidity management procedures in UTEST were modified mid-July 2022. In the new T2 platform, direct Participants can use below the options to manage liquidity:
- Immediate Liquidity Transfer via T2 RTGS GUI
T2 RTGS GUI can be used to transfer funds from the RTGS DCA to the T2S DCA. For details on how to use this functionality please refer to section “Liquidity Transfer – New Screen” of the Real-Time Gross Settlement User Handbook. - Immediate Liquidity Transfer via T2 CLM GUI
T2 CLM GUI can be used to transfer funds from the CLM MCA to the T2S DCA. For details on how to use this functionality please refer to section “Liquidity Transfer – New Screen” of the Central Liquidity Management User Handbook. - Configure Standing Orders in CRDM
Standing order for liquidity transfers can be created via CRDM GUI (U2A). This functionality offers the possibility to create a daily liquidity transfer. Standing orders can be configured to execute at certain time or event. Please refer to Common Reference Data Management User Handbook regarding the set-up and the related fields descriptions. - Liquidity Transfer via A2A camt.050 message
Participants can use the A2A channel for liquidity transfers from RTGS DCA or CLM MCA to T2S DCA. If so, the participant must provide in the creditor account of the T2S DCA to be funded. Please refer to the Real-Time Gross Settlement User Detailed Functional Specifications and Central Liquidity Management User Detailed Functional Specifications.
In addition, today's automated “T2S Cash Sweep out” to clear the balance on the T2S DCA with a simultaneous transfer of cash to the T2 cash account will become optional. A sweep out can be achieved by setting up a standing order in T2 CRDM. If customers require an automated liquidity transfer to the RTGS DCA, it is mandatory that a standing order is set up.
Allowing an efficient settlement on UTEST, customers are requested to manage their liquidity transfer to their DCA used for simulation activities related to Clearstream Banking Frankfurt and Luxembourg as well as Eurex Clearing AG. Potential changes in the settings are requested to be introduced as part of the migration activities.
The T2S Test Service Desk, before the deployment of any major and minor release will refresh the UTEST by changing the recycling period in the T2S UTEST environment for matched pending instructions and for unmatched pending instructions to one business day. With this option, the pending instructions with an intended settlement day far in the past are cancelled. The change to recycling parameter will be done in the same week when the deployment is executed. The T2S Test Service Desk will revert the parameters to their original values (60 business days for pending matched instructions and five business days for pending unmatched instructions) during the deployment weekend. The changes will be valid as of the next testing day. This process will also be applied on Friday four weeks after the implementation of a major and a minor release.
Based on the test or infrastructure requirements, T2S will run the processing day using the:
- T2S Synchronised Standard Day, that is, the general daily test schedule applies.
- T2S Change Request Test Day, which is required for T2S dedicated test cases.
- T2S Release Day, which is defined for installation procedures required by the T2S Actors.
- T2S Living Timing, which is announced for specific test procedures. In UTEST the operational schedule defined for the production environment will apply.
T2S Settlement Procedure | T2S Synchronised Standard Day | T2S Change Request Test upon announcement | T2S Release Day |
Start of Testing | 07:00 | 07:00 | 07:00 |
Real-Time Settlement | |||
Partial Settlement 1 | 08:00 | 08:00 | 08:00 |
Partial Settlement 2 | 10:00 | 10:00 | 10:00 |
Partial Settlement 3 | 12:00 | 12:00 | 11:00 |
Partial Settlement 4 | Not supported | 12:30a | 12:15 |
Partial Settlement 5 | 14:00 | 14:00 | 12:30 |
DvP / Cash SR Cut-off | 14:30 | 14:30 | 13:00 |
Collateral reimbursement | 15:00 | 14:50 | 13:30 |
BATM / CBO Cut-off | 15:10 | 15:10 | 13:40 |
Inbound LTO Cut-off / Automated cash sweep | 15:15 | 15:15 | 13:45 |
Securities SR / FoP Cut-off | 15:30 | 15:30 | 14:00 |
End of Day / Start of Day | |||
Change Business Day | 16:15 | 16:15 | 14:45 |
Feeds from Collateral Management System | 16:30 | 16:30 | 15:00 |
Start Night-Time / Cash Injection | 17:15 | 17:15 | 15:45 |
Night-Time Settlement | |||
End of Testing | 19:00 | 19:00 | 17:30 |
a. Times that deviate from the T2S Synchronised Standard Day are shown in bold.