In accordance with the 11 May 2022 CHESS Replacement Project Update, the following documentation and timelines will be revised in future documentation releases as ASX continues to work with our technology partner and stakeholders on the timing of project milestones including; industry testing, operational readiness, accreditation, market dress rehearsals and implementation.
Please refer to the 20 June 2022 CHESS Replacement Project Update for the latest information on project status.
Context of this Document
The ASX Cutover and Migration Strategy must be read in the context of the ASX CHESS Replacement Technical Documentation (as applicable).
In the interests of readability and comprehension, where a procedure applies only in the context of securities in a listed company, the specific term security has been used instead of the more generic term financial product.
Jul 06, 2022 06:46
Jul 06, 2022 06:37
Jul 04, 2022 02:23
Apr 28, 2022 01:15
Dec 17, 2021 01:11
Dec 16, 2021 08:53
Market Dress Rehearsals (MDRs) are mandatory events for all CHESS users. They are designed to replicate the single cutover approach by ensuring all required target state cutover activities can be achieved over a single weekend.
ASX will work with CHESS users to ensure considerations from each organisation’s cutover plan is incorporated into the master runbook. This ensures the timing associated with change or rollback activities is considered in the broader plan and rehearsed as part of MDRs. These, along with target dates for MDRs, will be key topics that ASX will explore as part of the CHESS user working groups or by bilateral engagement in Q1 2022.
5.1.1 Market Dress Rehearsal (MDR) Objectives
prove, test and refine the cutover approach
confirm the sequence of activities are correct;
allow for adjustments to be made to the run sheet, as necessary, to ensure all activities can be completed within the actual migration window;
test the communication channels with the ASX command room;
test cutover incident management procedures; and
ensure success criteria is clear and outcomes achieved.
5.1.2 Rehearsal Guiding Principles
The following is a set of guiding principles that
all activity required to be performed over the go-live cutover weekend,
rollback will need to be proven for any change planned for the cutov;
any deviation from the go-live plan for rehearsals must transparent and may require risk mitigation planning;
rehearsal activity is required to mimic the data, timing, resourcing and duration planned for the go-live event;
success criteria that is required to be met in must form part of either the entry criteria (measured pre event) or critical success factors (measured during including the Go decision), refer to section 5.2.2 for additional information; and
ASX to ensure internal cutover plans can successfully meet a go-live target prior to entering into 1 (MDR 1).
In order for the MDR phase to demonstrate confidence that ASX and CHESS users are ready to go-live, each MDR must rehearse what will occur over the go-live weekend.
5.2.1 Entry Criteria
If a decision is madwith an MDR, the market will be advised of the rescheduled commencement.
22.214.171.124 CHESS User Entry Criteria
The entry criteria for CHESS users are:
CHESS confirmed readiness for coming event;
CHESS high level MDR plan including rollback timing shared with ASX in order for critical milestones to be tracked (Due Q2 2022 in order for MDR plan to consider key CHESS user milestones);
CHESS user connectivity to ASX “to be” production environment proven prior to event;
Customer Migration Report format understood with verification plan in place; and
weekend communication contacts confirmed for both CHESS user change managers and ASX support staff.
ASX will publish further details on CHESS user entry criteria, and will engage with CHESS users on this topic in Q1 2022 in advance of publishing no later than July 2022.
5.2.2 Critical Success Factors
Critical success factors (CSF) are used to inform go-live event success. Each CSF is a measurable verification scenario that is performed as part of the cutover weekend and is fundamental in determining a Go or No-Go decision
126.96.36.199 CHESS User Critical Success Factors
Currently there are primary critical success factors that CHESS will be required to validate and report back to ASX as part of weekend events.
ASX will publish further details on CHESS critical success factors and contingency planning, and will engage with CHESS users on these topics in Q1 2022 in advance of publishing no later than July 2022.
5.3 MDR environment onsiderations
All market dress rehearsals will be conducted in the CHESS replacement‘To be’ Production Environment. This ensures all tasks in scope for the go-live weekend are rehearsed in the ASX hat will become the production environment.
As outlined in section 6, the ASX CHESS ‘To be’ Production Environment will be available following each MDR to support post MDR Day 1 testing. If CHESS users plan to participate in this of testing, their MDR environment must also be available post the MDR weekend activities completing.
ASX prefers that CHESS also adopt a ‘To be’ Production Environment strategy for each rehearsal. This ensure all MDR events will validate the cutover process on target Production environment and infrastructure. However, following focus group feedback, ASX understands that some organisations will leverage aproduction like environment for MDRs. This is an area that requires further discussion as part of CHESS user engagement in 2022.
5.3.1 Handling Unmasked Production data
All MDRs will be using unmasked production data validate the migration and cutover process for the following reasons:
masked data will not expose data quality exceptions where remediation actions may be required from either ASX or Controlling Participants. This means the exception handling process will not be rehearsed in MDRs;
data migration requires and reconciliation results will not be reliable or reflective of the real event if it cannot be performed on unmasked data;
ASX will not be able to generate meaningful for and
CHESS users will not be able to complete or execute a number of post MDR day 1 test scenarios with masked data.
5.3.2 Security controls for MDR environments
Any environment that CHESS users use to connect to ‘to-be’ Production must have appropriate data security controls in place. In order to ensure that unmasked production data is protected:
ASX will use the ‘to-be’ Production environment with production level security controls.
ASX expects that CHESS users will have production level security implemented in the environment to be used for MDRs and that CHESS users will perform adequate levels of security testing appropriate for a production environment;
It isthat the security of MDR environments is focused on protecting confidentiality of data and
MDRs will use a production data cut. CHESS users will be required to consider go-live preparation tasks when securing the snapshot targeting an MDR.
The approach to what date each of the MDR data snapshot will take was a key topic discussed during the Focus Groups held during November 20.
Following engagement with CHESS users in Q1 2022, it is now confirmed that each MDR will follow a current dated data snapshot approach.
5.5 Rollback as of MDR
The high level approach to rollback will be to reverse any change made to live production integrations and systems as part of the go-live weekend.
Key points relating to rollback as part of an MDR are that:
ASX will execute the ASX rollback plan as part of internal rehearsal events, and at least 1 MDR event with the market;
execution of CHESS user rollback plans will be requested as part of selected MDR events, however ASX will not evidence CHESS connecting back into current CHESS;
ASX will seek to understand the duration of each CHESS user’s rollback plan to ensure the final Go / No-Go and point of no return takes all rollback plans into consideration; and
CHESS users will be required to ensure rollback plans are validated internally prior to the MDR phase.
The window for CHESS user BVT requires connectivity and verification checks only. If transactions are sent during this period, these will need to be rolled back if a No Go decision is determined.
5.6.1 Communication during events
To ensure CHESS users are informed of status throughout each event, ASX will provide live updates to the System Status page or similar, advising of current status including any known high impact issues.
For scenarios where CHESS users are required to contact ASX, existing support teams will be leveraged to provide dedicated support during MDRs and the go-live cutover event. Support phone contact details will be provided that will allow CHESS users to contact ASX during weekend hours to either request updates on status tracking, or to provide information on how their respective change activity is tracking.
The event communication plan will be provided as part of the MDR overview document planned to be published July 2022.
5.6.2 Communication following each event
A summary version of the MDR outcomes will also be by the end of the week following an MDR.