Clarification on Detailed Impact Assessment Activities
Summary
The first complex technical change R0067 (Introduction of CSS Refresh Functionality) encountered a number of challenges within the design and implementation process, the change was scheduled for implementation on the 6th December 2023, however, the change was deployed with defects and was not fully operational until February 2024. Following that session, the Code Manager held discussions, and a formal Lessons Learned session with all Service Providers and identified a number of challenges with the technical change process. Some of these challenges can be attributed to the timing of the detailed design, Detailed Impact Assessments (DIA) and party impact assessments
Latest update and next planned activity
Date of latest update
Latest Update
This Change Proposal has been implemented as part of the June 2026 REC Release.
Impacts Overview
Impacted Consumers
Others
Impacted REC Documents
Schedule 5 - Change Management
Priority and rationale
Standard
Change Reports, Impact Assessments, Consultations and Documents
Change Reports
Solution development
Problem Statement
The technical change process currently creates five challenges which can be attributed to the timing of the detailed design, PIA and DIAs. These are as follows: Lack of Clarity, Limited Feedback, Misalignment, High Contingency Costs and Inaccurate Timelines.
Proposed solution summary
- An update to the REC Schedule 5 - Change Management.
Solution documents
There is currently no Change Plan.
Original submission
Change details
April Harbour - REC Technical Services
2 Oct 2025
Change details
Clarification on Detailed Impact Assessment Activities
The first complex technical change R0067 (Introduction of CSS Refresh Functionality) encountered a number of challenges within the design and implementation process, the change was scheduled for implementation on the 6th December 2023, however, the change was deployed with defects and was not fully operational until February 2024. Following that session, the Code Manager held discussions, and a formal Lessons Learned session with all Service Providers and identified a number of challenges with the technical change process. Some of these challenges can be attributed to the timing of the detailed design, Detailed Impact Assessments (DIA) and party impact assessments. These issues are detailed below:
1. Lack of Clarity Where Service Providers and impacted parties are dependent on each other, it’s is difficult for them to properly impact assess a change when there is no clarity on the design at the point of detailed impact assessment and party impact assessments are issued. 2. Limited Feedback Where design happens post a change being approved, there is no formal opportunity for impacted stakeholders to provide feedback and amends for the design to ensure that it meets their needs. 3. Misalignment Where designs are not shared early, assumptions can be made by all impacted parties, this can be discovered late in the development phase which may cause rework and or delays to testing / deployment. 4. High Contingency Costs Where there is uncertainty over design, Service Providers built in a high degree of contingency costs to ensure they have sufficient commercial coverage when completing a DIA. 5. Inaccurate timelines Completing an end-to-end implementation timeline as part of a DIA without having certainty on design can result in longer timelines being provided, lengthening the Change Process overall.
The Code Manager is proposing a new approach with the lead Service Provider completing design up front as part of the DIA. The decision to undertake design will be based on the level of complexity of the change and the strength of the business case. The changes will be assessed on a case-by-case basis, if the change is a suitable candidate for design as part of the DIA, a Technical Design Authority recommendation will be created. This will then be presented to the Relevant Committee for approval to release the funds for design as part of the DIA. Where the committee do not approve the release of funds, the change will continue down the standard change route and design will be completed following the approval of the full change proposal.
This approach was initially trialled with R0080. The recommendation was completed by the TDA, views sought from the Technical Expert Panel and RECCo approved the release of funds for the Service Provider to complete the design as part of the DIA. The detailed design documents were then able to be shared with industry at the Party Impact Assessment stage and highlighted a number of clarifications required within the design. This enabled the documents to be updated in advance of approval and ensure that the design was fit for purpose across the industry. The full change has subsequently been approved and is on track to be released in June 2025. This change seeks to formalise the committee approval to release funds to complete design as part of the DIA.
Impacts
Other (please specify in the Additional information box below)
Trust and confidence
This change will improve the quality of complex technical changes that are delivered through the REC. Indirectly, it will improve speed and efficiency of complex technical changes using the design first approach.
Schedule 5 - Change Management
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No
No details provided
Priority & timing
No
-
None
None
No details provided
Trust and confidence