Introduction of End of Gate Closure notifications
Summary
This change seeks to introduce additional functionality within the CSS, to allow CSS users to be notified (by CSS) that the CSS has completed the processing of gate closure messages (i.e. sending of securedActive and securedInactive messages). CSS Users in receipt of this End-of-Gate-Closure (EoGC) notification are then able to commence any applicable downstream processing. It is recognised that an EoGC notification is of value to specific parties which have post-gate closure obligations, however the availability of an EoGC notification is to be made available for all CSS users.
Latest update and next planned activity
Date of latest update
Latest Update
15/09/2025 - following discussions at the August Change Issues Group, the Proposer has decided to withdraw R0169. The adoption window is closed.
Impacts Overview
Priority and rationale
Standard
Priority last updated on 29 May 2026
Solution development
Problem Statement
The completion of a gate closure event is not reported to CSS Users (at the time), and CSS Users which require to complete downstream processing must assume when the gate closure event has completed in order to initiate any downstream processing they require to complete.
No documents available.
There is currently no Change Plan.
Original submission
Change details
- - -
7 May 2024
Change details
Introduction of End of Gate Closure notifications
-
-
-
-
Impacts
No details provided
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
No details provided
-
-
No details provided
Priority & timing
No
-
-
-
No details provided
-
Activity
james.hardy has been allocated as Lead Analyst.
caroline.milner has been allocated as SME.