Software provider readiness is a phase for software providers (vendors and those developing in-house systems that connect to CHESS) allowing them to complete development and test their systems. Software providers will be able to complete these activities in a dedicated environment (ITE1).
Customer readiness is a test phase for CHESS users allowing them to test their systems in preparation for operational readiness. CHESS Users will be able to complete these activities in a dedicated environment (ITE2).
ITE1 and ITE2 allows software providers and all CHESS users respectively, to move into a structured testing period following the development of software in the Customer Development Environment (CDE).
There are two distinct phases for software providers in ITE1;
- System development and testing provides software providers a phase to complete their functional and non-functional development and undertake testing (expected to open in late November 2021).
- Technical accreditation where software providers will need to demonstrate their software’s ability to connect and interact with CHESS (expected to commence end April 2022).
There are two distinct phases for CHESS Users in ITE2;
- User Testing allows CHESS Users the ability to perform their own internal tests on newly delivered software from their system providers. It will enable them to become familiar with new or upgraded systems, including any functionality changes, as well as undertake a level of testing that provides confidence that the system is ready for the more formalised operational readiness phase (expected to commence mid April 2022).
- Operational readiness where CHESS users will need to demonstrate that organisations meet the operational requirements of their business (expected to commence September 2022).
Characteristics of ITE
ITE1 and ITE2 share the same characteristics and will be provided on production grade infrastructure:
- Single dedicated integrated environment;
- Availability of CHESS User Interface (UI);
- Production style authentication model;
- Third party certificate signing authority;
- Multi-site/multi-node topology across ASX’s data centre; and
- Ability to test with other participants (ITE2 only).
From a functional perspective the clearing and settlement functionality available is as follows (subject to final code drops into ITE1):
- Account management;
- Trade registration;
- Holding management;
- Corporate actions;
- Reporting; and
- Connectivity testing
- Failover and recovery
ASX will provide further information on performance testing windows in a subsequent update.
All connectivity networks and access methods will be available from the opening of each ITE environment.
|Connectivity Network||Access Methods|
- Ledger API (Node Access)
- AMQP (ISO 20022 XML Messaging)
- CHESS User Interface
- FIX (Approved Market Operators only)
- SWIFT (ISO 20022 XML Messaging)
*Including IPSec VPN, Switch in Cabinet and Cross Connect.
The choice of software to connect into ITE2 resides directly with each CHESS User.
CHESS Users should note they are required to enter ITE2 with their 'to-be' production systems and connectivity options.
Industry Test Environment (ITE1)
System Development and Testing
To assist with development and testing ASX will provide a number of auto-responders to support bilateral workflows.
ITE1 will provide for:
- functional and non-functional testing
- ability to create test accounts
- full end-to-end settlement flows
- netting and settlement will run on a daily basis
ITE1 will not provide for (note this is not an exhaustive list):
- any production data, directly or masked, relating to end investor personal information
- AMO connectivity including Signal B (AMOs will be present in ITE1 for their own internal development and testing)
- ASX Reference Point
- Connectivity with ASX Derivative Clearing System (DCS)
The main activity to be conducted in ITE1 will be system development and testing by software providers.
Each software provider will be provided their own dedicated test kit which will include their own dedicated UICs and security codes, these test kits will be provided to software providers prior to the opening of ITE1.
Technical accreditation is a mandatory requirement for all external systems connecting to the CHESS replacement system in the production environment. It forms part of a broader set of requirements that help ensure the stability of the clearing and settlement facility. Technical accreditation is to be completed by software providers, including both system vendors and CHESS users developing their own in-house system.
Technical accreditation covers both connectivity and messaging:
- Connectivity accreditation: testing connectivity and resiliency within ITE1
- Messaging accreditation: demonstrating compliance with new message formats, for example ISO 20022, FIX and Ledger API commands. Messaging accreditation covers both ISO 20022 messages and Ledger API commands. As CHESS users have optionality on how they access CHESS Replacement, accreditation depends on the access choice you make for that functionality
Accreditation is available from end April 2022 until mid July 2022.
Who will need to be technically accredited?
Only software providers or those developing in-house software that connect directly to CHESS must be technically accredited. If organisations are using a software provider, or plan to use the new CHESS User Interface, no separate technical accreditation is required.
Industry Test Environment (ITE2)
User testing allows CHESS users to perform their own internal tests on newly delivered software from their system providers. It will enable them to become familiar with new or upgraded systems, including any functionality changes, as well as undertake a level of testing that provides confidence that the system is ready for the more formalised operational readiness phase. Users will also be able to undertake their own testing with new software, which may include integration with their own internal upstream, downstream and reporting systems.
ASX will provide details of CHESS User configuration, test tooling and integrated systems to assist with testing in a subsequent update.
Operational Readiness is where CHESS users will need to demonstrate their technical configuration and operational procedures using technically accredited software. Operational Readiness will be conducted in ITE2.
The scope of this verification step will be appropriate to the CHESS user's role and services provided. ASX will provide criteria for the Operational Readiness process which will include demonstration of functional processes.
Operational Readiness cannot commence until systems have been technically accredited.
Once Operational Readiness activities are completed, organisations will be required to submit an Attestation to ASX prior to the go-live phase.
Further details of ITE, Technical Accreditation, Operational Readiness and Attestation will be provided in a subsequent release.