The DCC is proposing that the implementation date for the June 2020 SEC Release is brought forward from 25 June 2020 to 6 May 2020. To help inform the Panel’s decision, we are seeking information on whether this date change would adversely impact you.
Further information on this release, including the current scope and the latest version of the Release Implementation Document, can be found on our June 2020 SEC Release webpage.
If you would be impacted by this change of date or have any comments on the DCC’s proposal, please contact us at firstname.lastname@example.org by close of play on Thursday, 12 March 2020. The Panel will be notified of any comments received when it considers the DCC’s request on Friday, 13 March 2020.
Why does the DCC want to bring this date forward?
The primary driver for the DCC seeking to bring the go-live date forward is that the SMETS1 Middle Operating Capability (MOC) release currently occupies the June 2020 SEC Release slot. Having considered a number of delivery options, and the importance of SECMP0062 ‘Northbound Application Traffic Management – Alert Storm Protection’ part 1, the DCC has identified that a revised go-live date of 6 May 2020 is the preferred option. This revised date also provides an improved risk profile to deliver SECMP0053 ‘Amend Target Response Times for Service Requests Critical to Installation and Commissioning Processes’ and SECMP0062 part 1.
The SMETS1 Core 1.1 release is currently planned to use the DCC’s testing environment before the SMETS1 MOC release in June. Attempting to deliver the SEC Release in-between these two releases would add significant risk for the SEC Release. Any slippage in the delivery of SMETS1 Core 1.1 would result in the June 2020 SEC Release being cancelled, as MOC delivery cannot be put at risk.
Combining the System Integration Testing (SIT), User Integration Testing (UIT), and Go-Live timelines for the SMETS1 Core 1.1 release and the SEC Release allows for the timely delivery of both releases, well in advance of the SMETS1 MOC delivery in June.
Bringing forward the SEC Release go-live date will also allow the SECMP0062 solution to be implemented earlier than currently planned, while also mitigating the risk of a delay to its delivery. The DCC highlights that any slippage to the delivery of SECMP0062 would expose the industry to the risks related to Alert Storms highlighted under this modification.
Who can I contact with any questions?
If you have any questions, please contact us at email@example.com or call the SECAS Helpdesk on 020 7090 7755.