T2-T2S Consolidation User Testing - Testing conditions - European Central Bank
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
ECB-Public
21/06/2022
T2-T2S Consolidation
User Testing - Testing conditions
Next Version(s) delivery Date Author Reviewed by
05/07/2022 ECB/4CB
19/07/2022 ECB/4CB
Table 1: Document log
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 1 of 13ECB-PUBLIC Contents 1. Introduction 3 2. User Testing Conditions 4 2.1 Temporary adaptations to the UT ToR principles 4 2.2 Complementary information to UT ToR 5 2.3 Software limitations - category 1 - functionalities not yet delivered 6 2.3.1 CRDM 6 2.3.2 CLM 6 2.3.3 RTGS 7 2.3.4 Billing 7 2.3.5 Data Warehouse (DWH) 7 2.3.6 Change Requests 8 2.4 Software limitations - category 2 – functionalities with open defects 8 2.5 Software limitations - category 3 - functionalities not yet fully tested by the Eurosystem. 8 3. Annex 10 T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 2 of 13
ECB-PUBLIC
1. Introduction
The T2 User Testing (UT) started on 01/12/2021 and prior to this test stage the software was tested by
Central Banks in Central Bank Testing (CBT) and in the Eurosystem Acceptance Testing (EAT). Some
software limitations were identified in the course of these test stages and these limitations will be
gradually lifted during UT.
The objective of this document is to provide an overview of these limitations in such a way that parties
involved in UT are informed, adapt their detailed testing plan accordingly and do not raise incidents on the
documented limitations.
This overview will present the limitations in three categories:
1. Functionalities not yet released or delivered,
2. Functionalities delivered but still impacted by open defects, and
3. Functionalities delivered that the Eurosystem has not fully tested yet
The timeline and availability of other TARGET services (i.e. TIPS and T2S) for end-to-end testing with T2
is provided in User Testing Terms of Reference (UT ToR) published on the ECB website. Any temporary
changes to the principles mentioned in the UT ToR will be listed in section 2.1 of this document. Also, in
situation when any of the testing principle mentioned in UT ToR needs to be clarified/detailed with
additional information, then these details will be included in section 2.2 of this document
In addition to this fortnightly testing conditions document, starting from 14/02/2022, the particular testing
conditions applicable in User Testing for the beginning of each testing day is being communicated on a
daily basis by the National Service Desk.
Based on the request from the participants, the information on Minimum Reserve interests applied in User
Testing Environment, is now included in Annex 2 of this document.
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 3 of 13ECB-PUBLIC
2. User Testing Conditions
The date of the status presented below is 17/06/2022.
2.1 Temporary adaptations to the UT ToR principles
As mentioned in the UT ToR (section 4.6), the Central Banks and the T2 participants shall follow the
recommendation document (CLM/RTGS Reference Data / recommendations for setting up data in
CRDM) for reference data, in order to ensure the successful propagation of data from and/loading in
CRDM to CLM and RTGS systems.
With the deployment of the CR74 and CR75 on 01/04/2022, these recommendations are enforced by the
system.
Also, the timeline mentioned (in section 4.3 of UT ToR) for the Migration Weekend Dress Rehearsal
(MWDR) for User Testing phase with T2S and TIPS services has been replanned and the current time
period to conduct the MWDR is on 16 and 17 July 2022.
In addition to support the testing, it was agreed to extend the testing time in UT environment, with a delay
to the start of EoD processes from 15:30 to 16:30 CET. This change was implemented as of 14/03/2022
and shall last until end of June (i.e. 30/06/2022) with further possible extension. In general, the extended
testing time will apply to days with standard day schedule (i.e. Monday-Thursday), while the timing of the
release day schedule on Fridays will remain unchanged. The table below shows the T2-T2S - CLM/RTGS
- testing schedules during the extended period of testing time.
As of 23/05/2022, in order to tackle the RTGS/GUI issues and A2A communication issues which was
caused by the long running queries triggered from “Query message screen”, the pertinent GUI screen were
adapted with a rebuild of the search criteria so that only either Inbound or Outbound option can be selected.
In addition, the participants are recommended to use the additional search criteria (e.g. Message Type,
BICs) to avoid the queries impact on the system resource. These temporary measures will be applied until
the SQL queries are optimized for the GUI (i.e. A2A queries are not impacted) but will be removed with Go-
Live at the latest. A more precise date cannot be provided at the moment.
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 4 of 13ECB-PUBLIC
CLM Standard & RTGS Standard & CLM Release RTGS Release
Synchronised Day Synchronised Day Day Day
Start of RTGS RTS II and
Settlement Window for
- 06:30 - 06:30
Interbank and Customer
Payments
Cut-off for customer
payments in T2
- 16:15 - 13:45
Inbound LTO cut-off for
T2S / Optional Cash sweep
(EUR) in T2S
Cut-off for CLM RTS
Cut-off for RTGS RTS II
and Settlement window for
16:30 16:30 14:00 14:00
Interbank and Customer
Payments. Execution of
Standing Orders after last
settlement attempt
General cut-off for
16:45 - 14:15 -
standing facilities
CB cut-off for standing
17:10 - 14:40 -
facilities
Change of business day
Start of day 17:15 17:15 14:45 14:45
Start of CLM RTS
17:30 - 15:00 -
Feeds from CMS to T2S
Execution of standing
orders in CLM
18:00 18:00 15:30 15:30
Start of RTGS RTS I and
Execution of Standing
Orders in RTGS
Start of NTS / cash
- - - -
injection
End of Testing 19:00 19:00 17:30 17:30
2.2 Complementary information to UT ToR
TIPS and T2S Liquidity Simulator (UT ToR - section 9.2)
The TIPS and T2S liquidity simulator software is partially (with issues blocking testing of CLM U2A Liquidity
monitoring and CLM pull U2A Inter-service liquidity transfers) available for testing from 01/04/2022.
The testing can be conducted after the account and liquidity details for those accounts are loaded into the
system. So, in order to perform this load, the T2Ps submitted the TIPS and T2S simulator - cash account
liquidity reference data template 1. After the data checks, the liquidity was loaded into the system and made
available for testing the TIPS and T2S Liquidity simulator from 11/04/2022.
Similar to the first load, after the data checks, the liquidity was loaded into the system and made available
for testing the TIPS and T2S Liquidity simulator as part of the second load from 30/05/2022.The timeline
for the next load will be planned based on the requirement from the participants.
AS testing campaign
1 The reference data template and the explainer to fill the template to be provided by the respective National Service Desk.
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 5 of 13ECB-PUBLIC
The Ancillary testing campaign is planned to be executed from 11/07 to 14/07 and from 19/07 to 29/07. The
deadline to meet the entry criteria for this campaign is 01/07/2022. The entry criteria to be met is explained
in the Summary document for this AS testing campaign and this document can be requested from the
respective Central Banks.
Migration Weekend Dress Rehearsal (MWDR)
The User Testing MWDR will be taking place from 15/07 till 17/07/2022. The participants activities are
planned to be executed on 17/07/2022. Further details on the activities and timeline is available in the
Migration Weekend Playbook for the July rehearsal. This document can be requested from the respective
Central Banks
2.3 Software limitations - category 1 - functionalities not yet delivered
This category covers the functionalities not yet released to UT classified by service component (i.e. CLM,
RTGS, DWH, etc.).
2.3.1 CRDM
All CRDM functionalities are released.
The T2 participants (T2Ps) are requested to follow the recommendations described in the document
“CLM/RTGS Reference Data / recommendations for setting up data in CRDM” in order to avoid data
inconsistencies that might hamper the business day processing which will be shared by the relevant
National Service Desk (NSD).
The CRDM Non-Repudiation of Origin (NRO) has been activated on 18/05/2022. The participants shall
complete the Go-Sign Desktop installation using the latest URL in ECB website 2.The ESMIG guide and
the FAQ 2.0 contains details on the technical NRO checks to be done by the server administrators and by
the user.
2.3.2 CLM
All CLM functionalities are released except the functionalities mentioned below which are planned to be
released on 01/07/2022:
2
See more information in
https://www.ecb.europa.eu/paym/target/t2s/profuse/shared/pdf/ESMIG_U2A_Qualified_Configurations_v1_3_3.pdf and please use
the latest URL below to download the GSD v6.9 (the URL referred in the above pdf will be soon updated) https://esmig-cert-
portal.emip.swiftnet.sipn.swift.com/gosign/ADSS-Go-Sign-Desktop-v6.9.0.1-Win64-SU.msi
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 6 of 13ECB-PUBLIC
o Blocking/Unblocking of CLM parties/accounts
The Non-Repudiation of Origin (NRO) functionality for CLM is planned to be delivered in batches of
screens between July and September 2022.
2.3.3 RTGS
All RTGS functionalities are released except for those mentioned below which are planned to be in the
upcoming releases
o Back-up payments to be released on 01/07/2022
o Blocking/Unblocking of RTGS parties/accounts to be released on 01/07/2022
All four algorithms were activated as of 24/05/2022.
As of 20/06/2022, the algorithms 2,3 and 4 run as per the below schedule:
o Monday – Thursday: Algo 2+3+4 four times a day >> at 9:00 / 11:00 / 13:00 / 15:00 hrs CET.
o Friday: Algo 2+3+4 three times a day >> at 9:00 / 11:00 / 13:00 hrs CET.
o Order of execution: Algo 2, Algo 3= directly after Algo 2, Algo 4 = directly after Algo 3 but only
in case an AS settlement procedure B is available
The Non-Repudiation of Origin (NRO) functionality for RTGS is planned to be delivered in batches of
screens between beginning of July and September 2022.
2.3.4 Billing
All Billing functionalities delivered except for the following one planned to be released on 01/07/2022:
o Queries
o Missing data flow from T2 incoming from DWH
The detailed plan of the T2 Billing testing will be provided once the DWH data flow is in place from
01/07/2022.
2.3.5 Data Warehouse (DWH)
The DWH infrastructure and the daily load were delivered. The planning for granting access and for the
availability of the predefined reports will be communicated as part of the next version (i.e. 04/07/2022).
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 7 of 13ECB-PUBLIC
2.3.6 Change Requests
Some change requests (CR) are scheduled for delivery during UT as per below table:
CR Reference Title Planned Delivery Date
CSLD-0050-URD CLM Adaptations to TIPS Interface 11/07/2022
CSLD-0061-UDFS Delta set retrieval 01/07/2022
Section B (Adaptation of business rules and filtering
CSLD-0075-UDFS Data propagation operational tools
data configurations) 30/09/2022
2.4 Software limitations - category 2 – functionalities with open defects
This category includes the functionalities delivered to UT but impacted by open defects:
• CRDM - 3 open defects impact the CRDM functionalities
• CLM – 10 open defects impact the CLM functionalities
• RTGS - 14 open defects impact the RTGS functionalities
The table in Annex 1 provides the impacted functionality, business description and target delivery date of
those open defects.
2.5 Software limitations - category 3 - functionalities not yet fully tested by the Eurosystem
This category includes the functionalities which were delivered but not yet fully tested by the CBs:
• Billing
• DWH
• ECONSII
• Ancillary system procedures
o Procedure A
o Procedure B
o Procedure D
o Procedure E
• CLM
o Broadcasts
o Download statement of account
o Direct debit sent by BILL to CLM
o Query files in U2A
o Modify 4 eyes tasks
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 8 of 13ECB-PUBLIC
• RTGS
o Query files in U2A
o Modify 4 eyes tasks
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 9 of 13ECB-PUBLIC
3. Annexes
Annex 1 – Open Defects
CRDM – 3 Defects
Problem ID Functionality/ Service Business Description/Summary Target delivery date
Standing order for bilateral limit cannot be
PBI000000218617 Cash Management changed in A2A (through camt.011) in CRDM Under analysis
Participant has identified security issues in the
PBI000000221461 Go-Sign Desktop current Go-Sign-Desktop Software Under analysis
Configuration of Conditional routing for RTGS
PBI000000221774 RTGS Directory directory to be amended Under analysis
CLM – 10 Defects
Problem ID Functionality/service Business Description/Summary Target delivery date
Issue with marginal lending - ML
PBI000000218862 Marginal Lending interests not generated Under analysis
Liquidity transfer CLM-T2S DCA not
PBI000000219294 Liquidity Transfer reflected in the T2S DCA balance Under analysis
The List of Minimum Reserve
Information per Account Holder did
not show the expected entries (for co-
manager and co-managed). This was
due to missing data in the Minimum
Minimum Reserve Reserve History data table in the
PBI000000220279 Requirement backend Under analysis
camt.053 for co-managed MCA not
received by a T2P even when the
report configuration has been set up
PBI000000220519 Statement of account correctly at the party level Under analysis
PBI000000220839 Account Balance CLM Adjustment balance incorrect Under analysis
camt.005 at CLM answered with
PBI000000220962 CLM, A2A camt.006 with E118 - No data found Under analysis
Standing Order generated in CLM
without the 'Order reference' entered
PBI000000221347 Standing Order in CRDM Under analysis
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 10 of 13ECB-PUBLIC
Problem ID Functionality/service Business Description/Summary Target delivery date
Both current and future maintenance
period should be displayed in the
GUI. Instead on the last of
Maintenance period in maintenance period, only the running
PBI000000221866 GUI maintenance period is displayed Under analysis
When keying a Pull Liquidity Transfer
in CLM to debit RTGS DCA and credit
MCA (same Party BIC) an error
message is received by the approver
PBI000000221887 Liquidity Transfer (U039) Under analysis
When minimum reserves fulfilments
queried for a BIC, the EOD balance is
showing as ‘0’ instead of actual
PBI000000222053 Minimum reserves balance value for that business day Under analysis
RTGS – 14 Defects
Problem ID Functionality/Service Business Description/Summary Target delivery Date
Outbound messages were missing for
payment instructions via the GUI and
PBI000000220439 A2A Outbound message A2A.although the instructions were settled. Under analysis
Liquidity Transfer RTGS to T2S settled but
PBI000000220476 Liquidity Transfer no response due to issue routing 01/07/2022
AS Procedure A and B Error message
incorrectly triggered: (Sum of debit amounts Hot-fix feasibility on
PBI000000220783 Debit/credit account is not equal to sum of credit amount) going
In screens - enter of backup payment via
GUI is rejected by error in field Under analysis
In Screens - enter of backup payment via
PBI000000220960 RTGS Credit transfer GUI is rejected Under analysis
[pain.998] [ASInitiationStatus not visible]
missing messages in RTGS GUI related to
AS files (AS InitiationStatus received via
PBI000000221344 AS initiation SWIFT) Under analysis
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 11 of 13ECB-PUBLIC
Problem ID Functionality/Service Business Description/Summary Target delivery Date
camt.053 expected pairs (DBIT + CRDT)
PBI000000221367 Debit/credit notification but received DBIT only Under analysis
After sending a revocation before
settlement via CAMT.056, CAMT.029 and
PACS.002 received as expected. But,
unexpectedly a second PACS.002 also
PBI000000221385 RTGS payments received. Under analysis
Execution of RTGS to CLM rule based
liquidity transfer for floor breach on the CLM
PBI000000221528 RTGS Liquidity Transfer MCA does not work Under analysis
In camt004 notification after triggering
floor/ceiling breach, the field with the
current balance amount is not present
PBI000000221541 Account transaction (CRRT) Under analysis
The creditor and debtor tags are not filled in
the received credit camt.054 whereas they
PBI000000221567 Credit/Debit notification have been filled in the GUI RTGS Under analysis
admi.007 received for camt.005 (payment
PBI000000221844 Payment instructions instructions) 01/07/2022
PBI000000221875 Payment queues Camt.006 – schema problem 01/07/2022
After sending CAMT.005 the receiving
CAMT.006 indicates while
there is a payment executed in T2 for this
PBI000000221877 Payment instructions account Under analysis
T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 12 of 13ECB-PUBLIC Annex 2 – Minimum Reserve Requirement interests in User Testing Environment The following values applied in T2 UTEST environment (starting from 14/06 till 27/07) for July Migration Weekend Dress Rehearsal. The maintenance period for these interest rates is weekly (Wednesday till Tuesday). MRIR minimum reserve interest rate: 0% MRP1 penalty rate type 1: 0.25% MRP2 penalty rate type 2: 0.5% EXIR excess reserve interest rate (exempt tier): 0% excess reserve interest rate (non-exempt tier): -0.5 % ODIR overnight deposit interest rate: -0.5 % MLIR marginal lending interest rate: 0.25% ERE - Excess reserve exemption factor: 3% T2-T2S Consolidation User Testing Execution - Testing conditions.docx Page 13 of 13
You can also read
