Addition of key information to all Service Now tickets
Summary
This Change seeks to improve the key business information, required by the DNOs, included in the SNOW tickets produced by CSS Service Desk for CSS Asynchronously rejected messages
Latest update and next planned activity
Date of latest update
Latest Update
The code elements of this change were implemented on the 12 April 2024. The technical solution will be delivered as part of the June 2024 REC Release.
Impacts Overview
Impacted REC Parties and Market Participants
Electricity Distribution Network Operator (R)
Data and Communications Company (DCC)
Priority and rationale
Standard
Solution development
Problem Statement
The SNOW tickets received by ERDS and GRDS for messages that CSS has asynchronously rejected (e.g., for business rule reasons) currently do not contain the relevant data for the SDSPs to triage and take any necessary action to resolve the underlying issue(s).This may delay the resolution of the SNOW tickets, potentially having an impact on aConsumers Switch.
Proposed solution summary
- As a Consumer I want the Switch process to work efficiently and effectively, so that I can switch Energy Supplier without unnecessary delay or issues.
- As an ERDS and GRDS, I want to receive SNOW tickets that contain all of the relevant data to enable me to triage and resolve issues efficiently, so that Consumers do not experience unnecessary switching delays and I am able to meet my service level obligations.
- As the CSS Provider, I want the ERDS related SNOW tickets to contain all of the relevant data to enable the efficient resolution of issues without the need for a manual workaround to be utilised, so that Consumers do not experience unnecessary switching delays.
Solution documents
Documents Library
Change Plan
Solution Analysis and Development
Completed
Start:
22 Aug 2022Due:
07 Feb 2023Completion:
07 Feb 2023Service Provider Impact Assessment - Preliminary
Completed
Start:
07 Feb 2023Due:
20 Mar 2023Completion:
20 Mar 2023Service Provider Detailed Impact Assessments
Completed
Start:
20 Mar 2023Due:
10 Jul 2023Completion:
27 Jun 2023Preliminary Change Report issued
Completed
Start:
10 Jul 2023Due:
14 Jul 2023Completion:
14 Jul 2023Responsible Committee review
Completed
Start:
14 Jul 2023Due:
26 Jul 2023Completion:
26 Jul 2023Consultation trigger
Completed
Start:
26 Jul 2023Due:
28 Jul 2023Completion:
28 Jul 2023Consultation close
Completed
Start:
28 Jul 2023Due:
18 Aug 2023Completion:
18 Aug 2023Final Change Report issued
Completed
Start:
18 Aug 2023Due:
15 Sep 2023Completion:
14 Sep 2023Responsible Committee decision
Completed
Start:
15 Sep 2023Due:
27 Sep 2023Completion:
27 Sep 2023Original submission
Change details
Ann Perry - St Clements Ltd (on behalf of DNOs)
22 Aug 2022
Change details
Addition of key information to all Service Now tickets
Currently there is a lack of key business information, required by the DNOs, included in the SNOW tickets produced by CSS Service Desk for CSS Asynchronously rejected messages
Without the required business information DNOs are unable to action and resolve the SNOW tickets. As a short term measure, DCC/Landmark have a workaround in place and the DNOs have been granted a derogation if the volumes of rejected messages make the workaround unviable for DCC/Landmark
The enduring solution should include the following data items within the SNOW tickets:
• MPXN (Meter Point Administration Number & Metering Point Registration Number
• CSS Correlation ID
• CSS Event ID
• CSS errorCode
• CSS errorTitle
• CSS errorDescription
• The full message request from ERDA which generated the error at CSS, e.g. a RECM_SN_CSS01000
Operational MPRS issues are resolved by Business Users who have no access to Adapter Services or backend Databases and are relying on Front End Systems to resolve these tickets. Having key Business Information, such as MPAN in SNOW greatly reduces the triage time for these errors leading to a swift accurate resolution. The involvement of wider teams to lookup messages is time consuming and can sometimes lead to data errors due to manual processes, ultimately to the Customers detriment.
• MPXN (Meter Point Administration Number & Metering Point Registration Number
• CSS Correlation ID
• CSS Event ID
• CSS errorCode
• CSS errorTitle
• CSS errorDescription
• The full message request from ERDA which generated the error at CSS, e.g. a RECM_SN_CSS01000
Operational MPRS issues are resolved by Business Users who have no access to Adapter Services or backend Databases and are relying on Front End Systems to resolve these tickets. Having key Business Information, such as MPAN in SNOW greatly reduces the triage time for these errors leading to a swift accurate resolution. The involvement of wider teams to lookup messages is time consuming and can sometimes lead to data errors due to manual processes, ultimately to the Customers detriment.
This issue first arose during Transition Testing when the E2E Service Management processes were first fully tested and was initially the focus of an IRG (Issue Resolution Group) series of meetings.
Impacts
Electricity
Switching experience, Trust and confidence
-
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
No details provided
Priority & timing
No
-
The derogation awarded to DNOs expires after 9 months.
It would be more efficient and reliable for all Parties if the enduring solution is put in place as soon as reasonably practicable
It would be more efficient and reliable for all Parties if the enduring solution is put in place as soon as reasonably practicable
-
No details provided
-