SVA Qualification: Storyboards and Test Guidelines
v 11.0
Effective From Date:
Status:SUPERSEDED
Other versions
Download
SVA Qualification: Storyboards and Test Guidelines |
Guidance Note |
Introduction
Background
As part of the Supplier Volume Allocation (SVA) Qualification Process under the BSC, Qualification Applicants are expected to design and execute their own testing to satisfy BSC requirements. Elexon1 may either witness the execution of tests or review the results as appropriate as part of the Self Assessment Document (SAD) review process and in order to verify an Applicants’ responses to the SAD.
This guidance provides a set of storyboards and other aids that can be used by Applicants when designing a test programme to satisfy the Qualification Requirements.
Applicants wishing to become Qualified in the role(s) of Party Agents are recommended to use the Storyboards as much as possible in support of their responses to the Testing Requirements on business processes and data flows.
Applicants wishing to become Qualified in the role(s) of Half-Hourly (HH) or Non Half-Hourly (NHH) Data Collector (DC) or Data Aggregator (DA) are recommended to perform arithmetic tests at the start and end of their business process tests.
Applicants wishing to become Qualified in the roles of DCs, DAs or Supplier Meter Registration Agents (SMRAs) are recommended to demonstrate that their business processes and systems can operate:
Consistently and robustly, and
At the volumes they intend to operate at in the live market, ensuring that daily timescales can be achieved.
Applicants are required to provide a proposal of how they wish to undertake the appropriate testing and how they will meet each of the requirements.
These guidelines are to advise applicants on some of the ways that they can demonstrate compliance with the SAD requirements.
Applicability of the Storyboards
Elexon has developed these storyboards to make the Qualification (and Re-Qualification) process easier to follow. The storyboards do not represent a definitive list of activities or a prescribed sequence to follow. Rather they clarify the objectives of the various scenarios as an aid for each applicant to produce its own business process tests. It is not obligatory to use them when going through the Qualification process.
As well as exercising the business processes relevant to the particular storyboards, your organisation will need to demonstrate its ability to send and receive all flows (e.g. Market Domain Data) and scheduled reports that are appropriate to its roles.
Applicants should also have processes to receive and respond to rejection messages for flows sent to other participants, i.e. they should be able to correct and re-send rejected flows.
Sections 2 and 3 cover the Non Half Hourly (NHH) and Half Hourly (HH) sectors of the market respectively. A Party Agent can operate in one or both sectors, so you should test the scenarios that are appropriate to your organisation.
If any information in this document conflicts with the BSC, the BSC takes precedence.
Structure of the Storyboards
Each storyboard has the following structure:
Title: This starts with the storyboard reference (e.g. AGS401) and contains a descriptive title for the scenario. The reference is coded within the following meanings:
AGS4xx – Agent Storyboard: NHH.
AGS5xx – Agent Storyboard: HH.
Applicant Role: Denotes the roles to be performed in the scenario. You take the market role(s) appropriate to you. Other market roles don’t need to be performed but you need to simulate inputs from other roles.
Associated Joint Storyboards: These refer to storyboards developed jointly by Elexon and Retail Energy Code (REC) for business scenarios from the perspective of Suppliers and Licensed Distribution System Operators (LDSOs). The reference is coded within the following meanings:
JSS0xx – Joint Storyboard for Supplier role; NHH.
JSS1xx – Joint Storyboard for Supplier role; HH.
JSD2xx – Joint Storyboard for LDSO role; NHH.
JSD3xx – Joint Storyboard for LDSO role; HH.
Initial Conditions: Sets out the conditions needed before the scenario can begin. In some cases this involves significant preparation for the organisation under test.
The Story: Gives a step-by-step description of events that occur in the scenario. The events are described in business terms and you will need to interpret these into technical activities. Normal business processes should be used for the completion of these key events.
Some events are described that will not involve you. These don’t need to be actioned by you but you may need to simulate their effects.
Final Conditions: Sets out the conditions that should prevail when the scenario has been completed. The scenario isn’t complete until all of the final conditions are met that are appropriate to you.
Variations: Indicate optional variations to the scenario. Some of these are additional or alternative business events; others replace or modify elements of the initial conditions. A re-interpretation of the final conditions may be needed. The assessment body concerned may request that a particular variation is invoked.
Completion of the Storyboards
When using the storyboards, you should create all flows that would be sent by you while performing the market role covered by the scenario. In addition, you need to simulate flows that would normally be received during completion of the scenarios. This includes manual as well as automated information flows.
It is not mandatory to follow normal operational timings when carrying out the scenarios.
Most of the storyboards describe ‘normal’ business processes. Some scenarios and variations focus on exceptional situations, giving you the opportunity to demonstrate your ability to respond to unusual circumstances.
Arithmetic Accuracy Testing
Applicants are expected to create a test strategy that verifies the arithmetic accuracy of their organisation’s systems.
This test strategy should comprise of a number of elements, relating to the input of logical pre-requisite data, inputs (meter readings) and corresponding expected results.
Tests should be completed based on the roles for which you are seeking Qualification - Half Hourly (HH) and Non Half Hourly (NHH) market sectors, or both.
Section 4 contains guidelines on the scope of arithmetic testing.
Performance, Capacity and Resilience Testing
Applicants are expected to create a test strategy that defines the actions necessary to facilitate their organisation’s performance, capacity and resilience testing.
This test strategy should comprise a number of discrete elements, relating to:
Processing meter readings
Aggregation of data
Variation activities
Resilience tests
If you prefer to use an alternative way of verifying the performance and resilience of your systems, then that is permissible as long as the scope and thoroughness of your testing is equivalent.
Tests should be completed based on the roles for which you are seeking Qualification - Half Hourly (HH) and Non Half Hourly (NHH) market sectors, or both.
Section 5 contains guidelines on the scope of performance, capacity and resilience tests.
Non Half Hourly Storyboards
AGS401: NHH Change of Supplier, MOA, DC and DA (concurrent)
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS001, JSS002, JSD201
Initial Conditions:
The Metering System (MS) is registered to the old Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate (old) agents.
Previous valid meter readings, Estimated Annual Consumption (EAC) and Annualised Advance (AA) are held at the old Non Half Hourly Data Collector (NHHDC) and Non Half Hourly Data Aggregator (NHHDA) as appropriate.
The MS is energised.
The old Supplier, its agents and the SMRA have retained evidence of the above.
The customer has received a quotation for supply and has agreed terms with the new Supplier.
The Story:
The new Supplier registers liability for the metering system with the SMRA and receives back confirmation and details of the old Supplier’s registration details. It also notifies the SMRA of the new agents’ details.
The new Supplier notifies all its agents (which are different from the old Supplier’s) of the start of their appointments, which are all accepted.
The SMRA notifies the old Supplier of its loss of liability. There is no objection from the old Supplier.
The old NHHDA is notified by the SMRA of the end of its appointment.
The new NHHDA is notified by the SMRA of the start of its appointment and that of the NHHDC.
All appropriate customer and MS information is exchanged between agents, including Customer Own Reading (COR).
The old Supplier notifies its agents of the end of their appointments.
The new NHHDC requests and receives MS history and EAC/AA data from the old NHHDC.
The new NHHMOA notifies the Supplier, the other agents and the LDSO of relevant Meter Technical Details (MTD) and mapping details.
The new NHHDC requests and receives settlement details for the MS from the new Supplier.
The new NHHDC sends the new Supplier and the LDSO confirmation of the inclusion of the MS in the reading schedules.
The new NHHDC notifies the new Supplier, LDSO and old NHHDC of valid readings.
The old NHHDC provides validated readings to the old Supplier.
The old and new NHHDCs calculate EAC/AAs and send them to the old and new Suppliers and NHHDAs as appropriate.
The old and new NHHDAs aggregate data for the day before the change and the day of the change, as appropriate.
Final Conditions:
The SMRA has recorded all of the changes to registration details, terminated the old Supplier, advised the new Supplier of the old Supplier’s agents and settlement configuration, and notified the old and new NHHDAs accordingly.
The new NHHMOA has received notice of its appointment and identified the Grid Supply point (GSP) Group. It has confirmed its appointment to the new Supplier. It has obtained MTD from the old NHHMOA and responded to the new NHHDC’s request for MTD.
The new NHHDC has received notice of its appointment and identified the GSP Group. It has requested and received MTD and reading history. It has obtained a COR reading and forwarded it to the appropriate parties.
The old NHHDC has received notice of its loss of appointment. It has responded to requests for meter reading history and MTD and forwarded them as required.
The new NHHDA has received notice of its appointment from the SMRA and received and aggregated the EAC from the new NHHDC.
The old NHHDA has received notice of its loss of appointment from the SMRA and received and aggregated the final AA from the old NHHDC.
For the day prior to the change Initial Supplier Volume Allocation was on the basis of the AA which is calculated using the CoS reading. The consumption was attributed to the old Supplier by the old NHHDC and aggregated by the old NHHDA.
For the effective day of the change Initial Supplier Volume Allocation was on the basis of the EAC which is calculated with the above AA. The estimated consumption was attributed to the new Supplier by the new NHHDC and aggregated by the new NHHDA.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Customer has recently been registered as a special needs person by the local authority.
2. The Supplier may use a full or skeleton registration that will impact on the content and quantities of appointment flows. A full registration is one where the initial registration contains all the required information without the need for any subsequent registration updates. A skeleton registration may imply use of the old agents by default, if no details of new ones are subsequently provided (in which case the final conditions will be appropriately different).
3. The old NHHDC does not provide valid EAC/AA history.
4. The new Supplier disputes the CoS reading prior to first reconciliation. A new COR is agreed with the old Supplier. The original reading is withdrawn and the new NHHDC calculates a deemed reading for the CoS date. New EAC/AA values are calculated and used in the next aggregation.
5. The meter reading does not have to be COR. Alternative reading types may be used by making arrangements with the appropriate agents.
6. There may be no change of Supplier, just a change of agents; or there may be only a change of one or some of the agents.
AGS402: NHH Change of Supplier, MOA, DC, DA, and Metering System
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS001, JSS002, JSS012, JSD207
Initial Conditions:
The Metering System (MS) is registered to the old Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate (old) agents.
Previous valid meter readings, EAC and AA are held at the old NHHDC and NHHDA as appropriate.
The MS is energised.
The old Supplier, its agents and the SMRA have retained evidence of the above.
The customer has received a quotation for supply and has agreed terms with the new Supplier.
The Story:
The new Supplier registers liability for the metering system with the SMRA and receives back confirmation of change of liability and the Supply Start Date (SSD) and details of the old Supplier’s registration details. It also notifies the SMRA of the new agents’ details.
The new Supplier notifies all its agents (which are different from the old Supplier’s) of the start of their appointments, which are all accepted.
The SMRA notifies the old Supplier of its loss of liability for the MS. There is no objection from the old Supplier.
The old Non Half Hourly Data Aggregator (NHHDA) is notified by the SMRA of the end of its appointment.
The new NHHDA is notified by the SMRA of the start of its appointment and that of the Non Half Hourly Data Collector (NHHDC).
All appropriate customer and MS information is exchanged between agents, including Customer Own Reading (COR).
The old Supplier notifies its agents of the end of their appointments.
The new NHHDC requests and receives MS history and EAC/AA data from the old NHHDC.
The new NHHMOA notifies the Supplier, the new NHHDC and the LDSO of relevant MTD and mapping details as appropriate.
The new NHHDC requests and receives settlement details for the MS from the new Supplier.
The new NHHDC sends the new Supplier and the LDSO confirmation of the inclusion of the MS in the reading schedules.
The new Supplier requests the new NHHMOA to replace the meter, which it does.
The new NHHMOA then notifies the Supplier, LDSO and new NHHDC of the mapping and MTD. It also informs the new NHHDC of the final meter reading of the old meter and the initial reading of the new one.
The new NHHDC notifies the new Supplier, LDSO and old NHHDC of valid readings.
The old NHHDC provides validated readings to the old Supplier.
The old and new NHHDCs calculate EAC/AAs and send them to the old and new Suppliers and NHHDAs as appropriate.
The old and new NHHDAs aggregate data for the day before the change and the day of the change, as appropriate.
Final Conditions:
The SMRA has recorded all of the changes to registration details, terminated the old Supplier, advised the new Supplier of the old Supplier’s agents and settlement configuration, and notified the old and new NHHDAs accordingly.
The new NHHMOA has received notice of its appointment and identified the GSP Group. It has confirmed its appointment to the new Supplier. It has obtained MTD from the old NHHMOA and responded to the new NHHDC’s request for MTD. It has responded to the request to change the meter and advised the other parties appropriately.
The new NHHDC has received notice of its appointment and identified the GSP Group. It has requested and received MTD and reading history. It has received final readings for the old meter and initial readings for the new one and forwarded them to the appropriate parties.
The old NHHDC has received notice of its loss of appointment. It has responded to requests for meter reading history and MTD and forwarded them as required. It has received the final reading for the old meter.
The new NHHDA has received notice of its appointment from the SMRA and received and aggregated the EAC from the new NHHDC.
The old NHHDA has received notice of its loss of appointment from the SMRA and received and aggregated the final AA from the old NHHDC.
For the day prior to the change Initial Supplier Volume Allocation was on the basis of the AA which is calculated using the CoS reading. The consumption was attributed to the old Supplier by the old NHHDC and aggregated by the old NHHDA.
For the effective day of the change Initial Supplier Volume Allocation was on the basis of the EAC which is calculated with the above AA. The estimated consumption was attributed to the new Supplier by the new NHHDC and aggregated by the new NHHDA.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
The Supplier may use a full or skeleton registration that will impact on the content and quantities of appointment flows. A full registration is one where the initial registration contains all the required information without the need for any subsequent registration updates. A skeleton registration may imply use of the old agents by default, if no details of new ones are subsequently provided (in which case the final conditions will be appropriately different).
There may be no change of Supplier, just a change of agents; or there may be only a change of one or some of the agents.
AGS403: NHH Change of Supplier, MOA, DC, DA, Invalid Meter Reading from DC
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS004, JSD202
Initial Conditions:
The Metering System (MS) is registered to the old Supplier with the SMRA.
Appointments are in place with all of the appropriate (old) agents.
Previous valid meter readings, EAC and AA are held at old NHHDC and NHHDA as appropriate.
The MS is energised.
The old Supplier, its agents and the SMRA have retained evidence of the above.
The customer has received a quotation for supply and has agreed terms with the new Supplier.
The Story:
The new Supplier registers liability for the metering system with the SMRA and receives back confirmation and details of the old Supplier’s registration details. It also notifies the SMRA of the new agents’ details.
The new Supplier notifies all its agents (which are different from the old Supplier’s) of the start of their appointments, which are all accepted.
The SMRA notifies the old Supplier of its loss of liability. There is no objection from the old Supplier.
The old Non Half Hourly Data Aggregator (NHHDA) is notified by the SMRA of the end of its appointment.
The new NHHDA is notified by the SMRA of the start of its appointment and that of the Non Half Hourly Data Collector (NHHDC).
All appropriate customer and MS information is exchanged between agents, including Customer Own Reading (COR).
The old Supplier notifies its agents of the end of their appointments.
The new NHHDC requests and receives MS history and EAC/AA data from the old NHHDC.
The new NHHMOA notifies the Supplier, the other agents and the LDSO of relevant MTD and mapping details.
The new NHHDC processes an invalid meter reading, and sends an invalid data report to the LDSO, new Supplier and old NHHDC.
The new Supplier requests the new NHHDC to provide a meter reading to replace the COR previously obtained.
The new NHHDC notifies the new Supplier, LDSO and old NHHDC of valid CoS readings.
The new NHHDC requests and receives settlement details for the MS from the new Supplier.
The new NHHDC sends the new Supplier and the LDSO confirmation of the inclusion of the MS in the reading schedules.
The old NHHDC provides validated readings to the old Supplier.
The old and new NHHDCs calculate EAC/AAs and send them to the old and new Suppliers and NHHDAs as appropriate.
The old and new NHHDAs aggregate data for the day before the change and the day of the change, as appropriate.
Final Conditions:
The SMRA has recorded all of the changes to registration details, terminated the old Supplier, advised the new Supplier of the old Supplier’s agents and settlement configuration, and notified the old and new NHHDAs accordingly.
The new NHHMOA has received notice of its appointment and identified the GSP Group. It has confirmed its appointment to the new Supplier. It has obtained MTD from the old NHHMOA and responded to the new NHHDC’s request for MTD.
The new NHHDC has received notice of its appointment and identified the GSP Group. It has requested and received MTD and reading history. It has sent an invalid data report, then obtained a valid COS reading and forwarded it to the appropriate parties.
The old NHHDC has received notice of its loss of appointment, also an invalid data report for the COR. It has responded to requests for meter reading history and MTD and forwarded them as required.
The new NHHDA has received notice of its appointment from the SMRA and received and aggregated the EAC from the new NHHDC.
The old NHHDA has received notice of its loss of appointment from the SMRA and received and aggregated the final AA from the old NHHDC.
For the day prior to the change Initial Supplier Volume Allocation was on the basis of the AA which is calculated. The consumption was attributed to the old Supplier by the old NHHDC and aggregated by the old NHHDA.
For the effective day of the change Initial Supplier Volume Allocation was on the basis of the EAC which is calculated with the above AA. The estimated consumption was attributed to the new Supplier by the new NHHDC and aggregated by the new NHHDA.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Supplier may use a full or skeleton registration that will impact on the content and quantities of appointment flows. A full registration is one where the initial registration contains all the required information without the need for any subsequent registration updates. A skeleton registration may imply use of the old agents by default, if no details of new ones are subsequently provided (in which case the final conditions will be appropriately different).
AGS404: NHH Change of SSC and TPR
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS007, JSD208
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate agents.
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate.
The MS is energised.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The Supplier requests the NHHMOA to reprogram the meter registers. The required change to the meter will require changes to the Standard Settlement Class (SSC) and Time Pattern Regime (TPR)).
The NHHMOA determines if the proposed combination of SSC/TPR/MTC is valid in the GSP Group and notifies the Supplier, NHHDC and LDSO of the new Meter Technical Details (MTD) and the new mapping of physical registers to TPRs.
The SMRA is notified of the changes by the Supplier and in turn notifies the NHHDA.
The NHHDC is notified of the initial class average EAC for each Settlement Register associated with the new SSC by the Supplier.
The NHHMOA passes the final meter reading(s) for the old register configuration and the initial reading(s) for the new one to the NHHDC for validation.
The NHHDC sends validated readings to the Supplier and LDSO.
The NHHDCs calculates EAC/AAs and sends them to the Supplier and NHHDA.
The NHHDA aggregates data for the day before the change and the day of the change, as appropriate.
Final Conditions:
The SMRA has confirmed the changes of SSC and MTC and notified the NHHDA.
The NHHMOA has received a request to re-program the meter registers and notified the Supplier, LDSO and NHHDC of the changes.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. Appropriate consumption was attributed to the Supplier.
The NHHDA has been notified of the changes to SSC and received and aggregated the EAC/AA from the NHHDC.
For the day prior to the change Initial Supplier Volume Allocation would be on the basis of the AA which is calculated using the final reading from the old meter. For the effective day of the change Initial Supplier Volume Allocation would be on the basis of the EAC information provided by the Supplier.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Supplier instructs the NHHDC to change the Profile Class of the metering point where no physical change of meter is required.
2. The SMRA fails to receive the registration updates for the new metering details. As a result, exception reports are sent to the Supplier and corrective actions taken.
3. The NHHDC is unable to obtain the required initial readings, so informs the Supplier and acts on its instructions.
4. The reprogramming may not require all of the suggested changes to be effected.
AGS405: NHH Credit Meter Replaced with Prepayment Meter
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS013, JSD208
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate agents
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate
The MS is energised.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Supplier has decided to replace the credit meter with a prepayment meter (PPM) that is appropriate for the LDSO or geographical area. The required change will require changes to the Standard Settlement Class (SSC).
The Story:
The Supplier requests the NHHMOA to replace a meter with the appropriate type of PPM.
The NHHMOA replaces the meter, advises the Supplier of the successful installation and the NHHDC of the final readings for the credit meter and initial readings for the new PPM.
The NHHMOA notifies the Supplier, LDSO and NHHDC of the Meter Technical Details (MTD) and mapping of physical registers to TPRs for the PPM.
The SMRA is notified by the Supplier of the change to the SSC and notifies the LDSO and NHHDA accordingly.
The NHHDC is informed by the Supplier of the changed SSC and the Initial EAC.
The NHHDC sends validated readings to the Supplier and LDSO.
The NHHDC calculates EAC/AA values and sends them to the Supplier and NHHDA.
The NHHDA aggregates data for the day before the change and the day of the change, as appropriate.
Final Conditions:
The credit meter has been replaced with a PPM.
The SMRA has confirmed the changes of SSC and notified the LDSO and NHHDA.
The NHHMOA has received a request to change the meter and notified the Supplier, LDSO and NHHDC of the changes.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. Appropriate consumption has been attributed to the Supplier.
The NHHDA has been notified of the changes to SSC and received and aggregated the EAC/AA from the NHHDC.
For the day prior to the change Initial Supplier Volume Allocation would be on the basis of the AA which is calculated using the final reading from the old meter. For the effective day of the change Initial Supplier Volume Allocation would be on the basis of the EAC information provided by the Supplier.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. Replacement with various types of PPM (key, token or smart).
2. For the type of PPM chosen, the new meter configuration may not require a change of SSC.
3. For Smartcard meters or any variants of Token or Key meters where the PPM Infrastructure Provider (PPMIP) obtains meter readings, the story may be extended as follows:
Remotely collected meter readings are forwarded by the Supplier to the NHHDC, who validates the readings and forwards them to the NHHDA for inclusion in the next allocation run (i.e. 1st reconciliation).
AGS406: NHH Withdrawal of Meter Reading
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: N/A
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate agents
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate
The MS is energised.
The NHHDC has calculated AA/EACs based on the valid meter data for the day before and the day of the last reading, and sent them to the NHHDA.
The NHHDA has carried out an Initial Settlement (SF) aggregation run for both days.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The NHHMOA notifies the NHHDC and Supplier of an invalid reading and the associated metering faults. After the fault is corrected, the NHHMOA sends an initial meter reading to the NHHDC.
The NHHDC withdraws the invalid meter reading (back to the last valid meter reading) and the AA/EACs relating to the period at fault. It informs the Supplier and LDSO of the invalid meter reading.
NHHDC produces a Valid Data Report for the initial meter reading and sends it to the Supplier.
The NHHDC sends a revised AA and EAC to the NHHDA and Supplier based on the last valid meter reading. The NHHDC assigns last valid EAC to AA from the last valid reading to the day prior to the NHHMOA visit and calculates a new EAC.
The NHHDC sends validated readings to the Supplier and LDSO.
The NHHDA carries out the Reconciliation aggregation runs for the day before the last (invalid) reading and the day of the reading.
Final Conditions:
The NHHMOA has notified the NHHDC of the invalid reading and the metering faults, and has also sent an initial meter reading, taken after the fault has been corrected, to the NHHDC.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. Appropriate consumption has been attributed to the Supplier.
The NHHDA has been notified of the changes to SSC and received and aggregated the EAC/AA from the NHHDC.
The Reconciliation Volume Allocation run has demonstrated the successful withdrawal of the AAs and EACs.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The NHHMOA, Supplier or LDSO could all potentially notify the Data Collector of an invalid reading.
AGS407: NHH De-Energisation
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS009, JSD205
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA) with all Registration Data items set.
Appointments are in place with all of the appropriate agents.
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate.
The MS is energised.
The customer has approached the Supplier to request temporary de-energisation of the meter.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The NHHMOA receives a request from the Supplier to de-energise the meter.
After de-energising the meter, the NHHMOA advises the Supplier, the NHHDC and the LDSO of the changed energisation status and the final meter reading.
The SMRA is advised of the changed energisation status by the Supplier, and notifies the NHHDA of the changes.
The NHHDC calculates EAC/AA values for the Meter Advance Period and sends them to the NHHDA and Supplier.
The NHHDC sends validated readings to the Supplier and LDSO.
The NHHDA carries out the aggregation runs for the day before and the day of the de-energisation.
Final Conditions:
The NHHMOA has received and confirmed a request from the Supplier to de-energise the meter. It has confirmed the change of energisation status with the LDSO and sent the final meter readings.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. The appropriate consumption has been attributed to the Supplier for the day before and the day of the de-energisation.
The NHHDA has been notified of the energisation changes by the SMRA and received and aggregated the EAC/AA from the NHHDC.
Throughout the scenario notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. (None currently suggested.)
AGS408: NHH De-Energisation & Disconnection
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS010, JSD206
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA) with all Registration Data items set.
Appointments are in place with all of the appropriate agents.
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate.
The MS is energised.
The customer has approached the Supplier to request disconnection of the meter.
The Supplier has requested disconnection from the LDSO.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The NHHMOA receives a request from the Supplier to de-energise and remove the meter.
The NHHDC, NHHDA and NHHMOA all receive notice from the Supplier that their appointments are to be terminated.
After de-energising and disconnecting the meter, the NHHMOA advises the Supplier, the NHHDC and the LDSO of the changed energisation status and the final meter reading.
The SMRA is advised of the changed energisation status by the Supplier, and notifies the NHHDA accordingly. When advised by the LDSO, it confirms the disconnection to the Supplier.
The NHHMOA advises the Supplier, LDSO and NHHDC that the meter has been disconnected and sends Meter Technical Details (MTD).
The NHHDC calculates AA values for the Meter Advance Period and sends them to the NHHDA and Supplier.
The NHHDC sends validated readings to the Supplier and LDSO.
The NHHDA carries out the aggregation runs for the day before and the day of the de-energisation.
Final Conditions:
The NHHMOA has received notice of its de-appointment and confirmed a request from the Supplier to de-energise and removed the disconnected meter. It has sent the final reading. It has confirmed the disconnection with the LDSO, Supplier and NHHDC and sent the final meter readings.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. The appropriate consumption has been attributed to the Supplier for the day before and the day of the de-energisation.
The NHHDA has been notified of its de-appointment and the disconnection by the SMRA and received and aggregated the AA from the NHHDC.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. (None currently suggested.)
AGS409: NHH Re-Energisation
Applicant Role: Party Agents (SMRA, NHHDC, NHHDA)
Associated Joint Storyboards: JSS011
Initial Conditions:
The Metering System (MS) is registered to the Supplier with the SMRA with all Registration Data items set.
Appointments are in place with all of the appropriate agents.
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate.
The MS is de-energised.
The customer has approached the Supplier to request re-energisation of the meter.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The NHHMOA receives a request from the Supplier to re-energise the meter.
After re-energising the meter, the NHHMOA advises the Supplier, the NHHDC and the LDSO of the changed energisation status and the initial meter reading.
The SMRA is advised of the changed energisation status by the Supplier, and notifies the NHHDA accordingly. When advised by the LDSO, it confirms the energisation to the Supplier.
The NHHDC calculates EAC values for the Meter Advance Period and sends them to the NHHDA and Supplier. The NHHDC sends initial readings to the Supplier and LDSO.
The NHHDA carries out the aggregation runs for the day before and the day of the re-energisation.
Final Conditions:
The NHHMOA has received and confirmed a request from the Supplier to re-energise the meter. It has confirmed the re-energisation with the LDSO, Supplier and NHHDC and sent the initial meter reading.
The NHHDC has been notified of the changes and forwarded readings to the appropriate parties. The appropriate consumption has been attributed to the Supplier for the day before and the day of the re-energisation.
The NHHDA has been notified of the re-energisation by the SMRA and received and aggregated the EAC from the NHHDC.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Supplier does not notify the SMRA of the re-energisation so the SMRA does not notify the NHHDA. For the day of re-energisation, the NHHDA attributes zero consumption instead of using the new EAC supplied by the NHHDC, as the Metering System is de-energised according to the SMRA. An exception is identified from an Exception Report during the Initial Supplier Volume Allocation processing.
Resolution: The NHHDA requests a comparison of NHHDC and SMRA data and the Supplier is notified of the discrepancy in the Energisation Status. The Supplier notifies the SMRA, who in turn notifies the NHHDA. In the next aggregation run for the day of re-energisation, the NHHDA will use the new EAC supplied by the NHHDC.
2. The Meter Operator goes on site but cannot energise the Metering System due to a damaged supply cable. The Supplier is informed of this and tasks the Distributor with the energisation. The Distributor successfully energises the meter, takes an initial meter reading and notifies the Supplier of the successful re-energisation.
AGS410: NHH to HH - Change of Measurement Class
Applicant Role: Party Agents (SMRA, NHHDC, HHDC, NHHDA, HHDA)
Associated Joint Storyboards: JSS111, JSD318
Initial Conditions:
The NHH Metering System (MS) is registered to the Supplier with the SMRA with all Registration Data items set.
Appointments are in place with all of the appropriate NHH agents.
Previous valid meter readings, EAC and AA are held at the NHHDC and NHHDA as appropriate.
The NHH MS is energised.
The Customer has approached the Supplier with a view to changing the metering to Half Hourly, has accepted the contractual terms offered by the Supplier and has instructed that the change of metering should proceed.
The Supplier, its agents and the SMRA have retained evidence of the above.
The Story:
The HH agents receive their appointments to the HH metering system from the Supplier; they confirm their acceptance and receive details of the other agents, Customer details, the NHH Metering System and the required settlement configuration.
The Supplier terminates the NHHMOA, NHHDC and NHHDA appointments and notifies the SMRA of the change of Measurement Class and the HH agent appointments.
The Supplier requests the new HHMOA to install an HH meter.
The HHMOA requests Site Technical Details from the LDSO.
After replacing the meter, the NHHMOA sends a final meter reading for the removed MS to the NHHDC.
The HHMOA confirms the installation of the HH meter to the Supplier, LDSO and HHDC, and provides initial meter register readings as necessary.
The NHHMOA notifies the Supplier, NHHDC and LDSO of Meter Technical Details (MTD) for the removed MS.
The HHMOA requests a proving test from the HHDC and confirms the final NHH readings with the NHHMOA.
The HHDC provides the HHMOA with initial HH advances.
The HHMOA reports the successful proving test to the HHDC, Supplier and LDSO.
The SMRA confirms the changes of Measurement Class and Data Collector appointment to the LDSO and Supplier, informs the NHHDA of the termination of its appointment and the HHDA of the start of its appointment.
The HHDC confirms the reading schedule to the Supplier and LDSO. It collects meter data for the day of the change and sends it to the Supplier, LDSO and HHDA.
The NHHDC sends the final meter readings to the Supplier and LDSO. It calculates the AA and revised EAC and notifies the Supplier and NHHDA.
The NHHDA and HHDA carry out the appropriate aggregation runs.
For the day before the change, consumption is attributed to the Supplier via the NHHDA but none is attributed via the HHDA.
For the day on which the HH meter is installed, consumption is attributed to the Supplier via the HHDA but not via the NHHDA.
Final Conditions:
Appointments are in place with all of the appropriate HH agents.
The SMRA has received notice of the change in measurement class along with the de-appointment of the old agents and the appointment of the new agents, which is acknowledged and passed to the NHHDA and HHDA.
The NHHMOA has received notification of the termination of its appointment from the Supplier. It has sent a final meter reading for the removed MS to the NHHDC and notified the Supplier and NHHDC of the MTD.
The NHHDC has received notification of the termination of its appointment from the Supplier. It has received a final meter reading and MTD from the NHHMOA. It has processed and validated the final meter reading and produced a Valid Data Report and sent it to the Supplier and LDSO. The AA and revised EAC have been calculated and sent to the Supplier and the NHHDA.
The NHHDA has received notifications of its termination of appointment from the Supplier and the SMRA. It has received AA data from the NHHDC and carried out the appropriate aggregation runs.
The HHMOA has received notice of its appointment to the HH metering system, confirmed acceptance and received details of the other agents, Customer details, NHH Metering System and required settlement configuration. It has requested and obtained site details from the LDSO, provided MTD to the Supplier, LDSO and HHDC and initial register readings to the HHDC. It has requested and received proving data from the HHDC, proved the metering system and notified the success to the LDSO, Supplier and HHDC.
The HHDC has received notice of its appointment to the HH metering system, confirmed acceptance and received details of the other agents, Customer details and the required settlement configuration. It has received MTD from the HHMOA along with initial register readings and forwarded initial register readings to the LDSO and Supplier. It has received a request to prove test data and forwarded it to the HHMOA, then received confirmation of the successful proving test. It has confirmed the inclusion of the meter in the reading schedule to the LDSO and Supplier and collected HH period data, and forwarded it to the Supplier, LDSO and HHDA. For the day prior to the change consumption is attributed to the Supplier on the basis of the AA calculated using the final NHH meter reading.
The HHDA has received notice of its appointment to the HH metering system and confirmed acceptance. It has been appointed by the SMRA to the metering system and notified of the start date and energisation status. It has received HH advances from the HHDC and aggregated it accordingly.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Customer has chosen a new Meter Operator who is qualified in both Non-Half Hourly and Half Hourly market sectors.
2. The day of energisation may be a BST (British Summer Time) day. Consequently the initial reading and the HH period readings will be extracted in UTC and converted as appropriate to settlement time (BST) by the HHDC.
3. The proving test may fails, in which case the HHMOA must initiate a re-test by arrangement with the HHDC.
AGS411: NHH to HH (concurrent Change of Supplier)
Applicant Role: Party Agents (SMRA, HHDC, NHHDC, MAP and LDSO)
Associated Joint Storyboards:
Initial Conditions:
The Metering System (MS) is registered to the old Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate old Non Half Hourly agents.
Previous valid Meter Technical Details (MTDs) are held at the old Non Half Hourly Meter Operator Agent (NHHMOA) and Non Half Hourly Data Aggregator (NHHDA) as appropriate.
The Metering System is energised.
The old Supplier, its agents and the SMRA have retained evidence of the above.
The customer has agreed terms with a new Supplier to electively switch to Half Hourly (HH) Settlement.
The Story:
The old Supplier notifies old MOA and the NHHDC of their de-appointment from the Metering System. The new Supplier appoints its new agents (new MOA and HHDC) and receives confirmation of contractual terms.
The new Supplier notifies HHDC of the other agents, the Measurement Class (MC) and the Profile Class (PC) and Estimate of Annual Consumption (EAC) to be used if estimation is required. Optionally, the Supplier notifies the HHDC of the Customer details.
If required the Supplier re-configures the Meter’s Time of Use (TOU) registers.
The new Supplier notifies the new MOA of the TOU configuration details (if changed), which are received. If the Time of Use registers are not configured to a valid Standard Settlement Configuration (SSC) (as defined in Market Domain Data, the Supplier will notify a single rate SSC.
If notification of change in ToU configuration received the new MOA sends MTD to the new Supplier and the LDSO. The new Supplier notifies the SMRS of the new Measurement Class (MC), MOA type of ‘H’ and HH Agent IDs. The new MOA sends new Supplier’s details to the Meter Asset Provider (MAP) and the MAP receives it.
The new Supplier sends configured reads to the old Supplier. The old Supplier receives it and sends final readings to the NHHDC. The NHHDC send validated Change of Supplier (CoS) reads to old Supplier and LDSO.
Final conditions:
Appointments are in place with all of the appropriate HH agents.
The SMRA has received notice of the de-appointment of the old agents and the appointment of the new agents, which is acknowledged and passed to the HHDAs.
The old MOA has received notification of the termination of its appointment.
The old NHHDC has received notification of the termination of its appointment from the Supplier. It has processed and validated the final meter reading and produced a Valid Data Report and sent it to the old Supplier and LDSO.
The new MOA has received notice of its appointment, confirmed acceptance and received details of the other agents, customer details, Metering System and required settlement configuration. It has provided MTD to the Supplier, LDSO and HHDC and initial register readings to the HHDC.
The HHDC has received notice of its appointment, confirmed acceptance of terms and received details of the other agents, customer details and the required PC and EAC for use in estimation.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
AGS412: NHH to HH (no Change of Supplier)
Applicant Roles: Party Agent (SMRA, HHDC, NHHDC, LSDO)
Associated Joint Storyboards:
Initial Condition:
The Metering System (MS) is registered to the Supplier with the LDSO’s Supplier Metering Registration Agent (SMRA).
Appointments are in place with all of the appropriate Non Half Hourly Agents.
Previous valid Meter Technical Details (MTDs) are held at the Non Half Hourly Meter Operator Agent (NHHMOA) and Non Half Hourly Data Aggregator (NHHDA) as appropriate.
The Non Half Hourly (NHH) Metering System is energised.
The Supplier, its agents and the SMRA have retained evidence of the above.
The customer has agreed terms with the Supplier to electively switch to Half Hourly (HH) Settlement.
The story:
If required the Supplier re-configures the Meter’s Time of Use (TOU) registers.
The Supplier notifies the MOA of the TOU configuration details (if changed). If the Time of Use registers are not configured to a valid Standard Settlement Configuration (SSC) (as defined in Market Domain Data, the Supplier will notify a single rate SSC.
If notification of change in ToU configuration received the MOA sends MTD to the Supplier and the LDSO. The Supplier notifies the Half Hourly Data Collector (HHDC) of its appointment to the Metering System.
HHDC sends agreement of contractual terms to Supplier. The Supplier notifies the Non Half Hourly Data Collector (NHHDC) of its de-appointment from the Metering System.
The Supplier notifies HHDC of the other agents, the Measurement Class (MC) and the Profile Class (PC) and Estimate of Annual Consumption (EAC) to be used if estimation is required. Optionally, the Supplier notifies the HHDC of the Customer details.
The Supplier notifies the SMRS of the MC, MOA type of ‘H’ and HH Agent IDs.
The Supplier takes final NHH reading(s) and sends final reading(s) to NHHDC. The NHHDC receives and validates the final reading(s).
The NHHDC sends validated final reading(s) to the Supplier and the LDSO.
Final Conditions:
Appointments are in place with all of the appropriate agents.
The SMRA has received notice of the de-appointment of the old agents and the appointment of the new agents, which is acknowledged and passed to the HHDAs.
The NHHDC has received notification of the termination of its appointment from the Supplier. It has processed and validated the final meter reading(s) and sent to the Supplier and LDSO.
The HHDC has received notice of its appointment, confirmed acceptance and received details of the other agents, customer details and the required PC and EAC for use in estimation.
The MOA has sent any changes to MTDs to the LDSO and Supplier. Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Half-Hourly Storyboards
AGS501: HH Change of Supplier, MOA, DC and DA
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSS102, JSS103, JSD314
Initial Conditions:
The HH Metering System (MS) is registered to the old Supplier with the SMRA with all registration data items set.
Appointments are in place with all of the appropriate HH agents.
Previous valid meter readings are held at the old HHDC and old HHDA as appropriate
The HH MS is energised.
The Customer has entered into a contract with the new Supplier.
The old and new Supplier, their agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The new Supplier registers liability for the MS with the SMRA and receives back confirmation and details of the old Supplier’s registration details. It also notifies the SMRA of the new agents’ details.
The SMRA notifies the old Supplier of its loss of liability. There is no objection from the old Supplier, who terminates the old HHMOA, HHDC and HHDA appointments. The old HHDA is notified by the SMRA of the end of its appointment.
The HH agents receive their appointments to the MS from the Supplier; they confirm their acceptance and receive details of the other agents, customer details, the HH MS and the required settlement configuration. The new HHDA is informed of its appointment and details of the HHDC by the SMRA.
The new HHMOA requests and receives Meter Technical Data from the old HHMOA, and forwards it to the Supplier, HHDC and LDSO.
The new HHDC confirms the reading schedule to the new Supplier and LDSO. It requests and receives historic meter data from the old HHDC.
The old and new HHDCs collect metering data for the day before and the day of the change, as appropriate, and send the HH advances to the relevant Suppliers, HHDAs and LDSO.
The HHDAs carry out the appropriate aggregation runs.
For the day before the change, consumption is attributed to the old Supplier via the old HHDA.
For the day of the change, consumption is attributed to the new Supplier via the new HHDA.
Final Conditions:
Appointments are in place with all of the appropriate HH agents.
The SMRA has received notice of the de-appointment of the old agents and the appointment of the new agents, which is acknowledged and passed to the HHDAs.
The old HHDC has received notification of the termination of its appointment from the Supplier. It has processed and validated the final meter reading and produced a Valid Data Report and sent it to the old Supplier, old HHDA and LDSO.
The old HHDA has received notifications of its termination of appointment from the Supplier and the SMRA. It has received meter readings from the old HHDC and carried out the appropriate aggregation runs.
The new HHMOA has received notice of its appointment, confirmed acceptance and received details of the other agents, customer details, Metering System and required settlement configuration. It has provided MTD to the Supplier, LDSO and HHDC and initial register readings to the HHDC.
The new HHDC has received notice of its appointment, confirmed acceptance and received details of the other agents, customer details and the required settlement configuration. It has received MTD from the HHMOA along with initial register readings and forwarded initial register readings to the LDSO and Supplier. It has received a request to prove test data and forwarded it to the HHMOA, then received confirmation of the successful proving test. It has confirmed the inclusion of the meter in the reading schedule to the LDSO and Supplier and collected HH period data, and forwarded it to the Supplier, LDSO and HHDA. For the day prior to the change consumption is attributed to the Supplier on the basis of the AA calculated using the final NHH meter reading.
The new HHDA has received notice of its appointment and confirmed acceptance. It has been appointed by the SMRA to the metering system and notified of the start date and energisation status. It has received HH advances from the HHDC and carried out the appropriate aggregation runs.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions, unless otherwise stated.
1. There may be no change of agents involved. The old and new Supplier have appointed the same HH agents for the MS. This will mean that some of the above final conditions do not apply.
AGS502: HH Change of LLF Class
Applicant Role: Party Agents (SMRA, HHDA)
Associated Joint Storyboards: JSS106
Initial Conditions:
The HH Metering System (MS) is registered to the Supplier with the SMRA with all registration data items set.
Appointments are in place with all of the appropriate HH agents.
Previous valid meter readings are held at the HHDA as appropriate
The HH MS is energised.
The Supplier’s agents and the SMRA have retained evidence, as appropriate, of the above.
The LDSO has assigned a different Line Loss Factor (LLF) Class for the Metering System (MS).
The Story:
The SMRA notifies the Supplier and HHDA of the change of LLF Class.
The HHDA makes the appropriate system updates for the change.
Meter data is received from the HHDC for the day before and the day of the change.
The HHDA carries out the appropriate aggregation runs. For the day before the change, consumption is attributed to the Supplier for the old LLF Class. For the day of the change, consumption is attributed for the new LLF Class.
Final Conditions:
The SMRA has notified the Supplier and HHDA of the change.
The HHDA has received HH meter advances from the HHDC and carried out the appropriate aggregation runs.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. This story may be run for a variety of meter configurations to demonstrate that the relationships between Agents, GSP Groups and LDSOs can be handled correctly. E.G Maintenance of LLF Classes for multiple LDSOs within a single GSP Group.
AGS503: HH Replacement of Meter & Proving Test
Applicant Role: Party Agents (HHDC, HHDA)
Associated Joint Storyboards: JSS109
Initial Conditions:
The HH Metering System (MS) is registered to the Supplier with the SMRA with all registration data items set.
Appointments are in place with all of the appropriate HH agents.
Previous valid meter readings are held at the HHDA as appropriate
The HH MS is energised.
The Supplier’s agents have retained evidence, as appropriate, of the above.
Following a customer notification to the Supplier, an investigation has shown that there is a fault with the meter.
The Story:
The Supplier requests the HHMOA to replace the meter.
The HHMOA arranges with the HHDC for the final HH data to be collected.
After changing the meter, the HHMOA informs the Supplier, HHDC and LDSO of the new MTDs.
The HHMOA advises the HHDC of the final and initial meter readings and requests a proving test.
After comparing the expected and collected data, the HHMOA advises the Supplier, LDSO and HHDC of the successful proving test.
The HHDC determines the date of the next Meter Advance Reconciliation (MAR) and collects data for the new meter.
The HHDA carries out the appropriate aggregation runs for the day before the change and the day of the change.
Final Conditions:
The HHMOA has received a request to replace the meter and agreed a time for the HHDC to take final HH readings. It has taken final register readings, replaced the meter with an equivalent type and taken initial register readings. It has sent MTD to the HHDC, Supplier and LDSO and initial and final register readings to the HHDC. It has requested proving data from the HHDC, received the proving data and confirmed the successful proving to the Supplier, LDSO and HHDC.
The HHDC has received notice of the meter change and the requirement to extract HH period data. It has agreed a date and time with the HHMOA and read the HH period data at the appointed time. It has received MTD for the replacement meter along with final and initial register readings from the HHMOA and forwarded the readings to the Supplier and LDSO. It has begun reading HH data and received a request from the HHMOA for proving data, forwarded the proving data then received confirmation of the successful proving and has set the date for the next MAR accordingly. The HHDC has provided an unbroken sequence of HH period data to the Supplier, LDSO and HHDA.
The HHDA has received HH meter advances from the HHDC and carried out the appropriate aggregation runs.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The HHDC may decide to use any of the 4 methods for proving the meter, making the appropriate changes to the story.
AGS504: HH New Metering System, Initial Registration, Energisation
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSS101, JSD313
Initial Conditions:
The customer has approached the Supplier requesting a cable installation for the connection of a new, Half Hourly Metering System (MS) and has entered into a supply contract.
The MS is not yet registered to the Supplier with the SMRA.
No appointments are in place with any of the Supplier’s HH agents.
In response to the Supplier’s request, the Distributor has installed cabling according to the site plans and informed the Supplier that this work has been completed, together with the Registration Data and Site Details.
The Supplier’s agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The Supplier registers the new connection (as de-energised initially) and receives confirmation of the registration from the SMRA.
The HH agents receive their appointments to the MS from the Supplier; they confirm their acceptance and receive details of the other agents, customer details, the MS and the required settlement configuration. The HHDA is informed of its appointment and details of the HHDC by the SMRA.
The HHMOA is instructed by the Supplier to install and energise the MS at the new connection. The HHMOA requests and receives Site Technical Details from the LDSO.
The HHMOA confirms to the Supplier, LDSO and HHDC that both the installation and energisation occurred and also provides the initial meter register reading and meter technical details.
The HHMOA requests a proving test from the HHDC. After comparing the expected and collected data, the HHMOA advises the Supplier, LDSO and HHDC of the successful proving test.
The HHDC confirms the reading schedule and sends initial meter readings to the Supplier and LDSO.
After being informed by the Supplier that the meter is now installed and energised, the SMRA notifies the LDSO and Supplier agents of the change in energisation status.
The HHDC collects metering data for the day of the energisation and sends the HH advances to the Supplier, HHDA and LDSO.
The HHDA carries out the appropriate aggregation runs. For the day before the energisation, no consumption is attributed to the Supplier. For the day of the energisation, consumption is attributed to the Supplier.
Final Conditions:
The SMRA system has been updated with the new connection details, received the Supplier registration, and acknowledged and updated the HHDA accordingly. It has received notice of energisation, confirmed successful processing and advised HHDA.
The HHMOA has received new connection appointment details and notification of other agents, determined the GSP Group, obtained site technical details from the LDSO, received a request to install HH metering and advised the Supplier, LDSO and HHDC of the associated MTD and sent initial register readings to the HHDC. It has conducted proving in conjunction with the HHDC.
The HHDC has received and acknowledged its appointment to the new connection and notification of other agents. It has received MTD and initial register readings from the HHMOA and passed initial register readings to the Supplier and LDSO. It has begun reading the meter and conducted proving in conjunction with the HHMOA. It has identified MAR requirements and passed HH periods to the HHDA, LDSO and Supplier.
The HHDA has received its appointment to the new connection and notice of the HHDC. It has received and acknowledged its Supplier appointment. It has received notice of the energisation of the MS and HH period readings. The meter readings have been aggregated as required.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. Either skeleton or full registration details may be sent to the SMRA by the supplier. When the SMRA notifies the HHDA of its liability for the new MS; if full registration details are used, then subsequent instructions to the HHDA will only notify it of the new energisation status. If skeleton registration then subsequent instructions will notify the HHDA of their appointment, the HHDC appointment AND the energisation status.
AGS505: HH De-Energisation of Metering System
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSS107, JSD316
Initial Conditions:
The Customer has written to the Supplier requesting de-energisation of the Metering System (MS) and a mailing address is agreed where notification of completion of the work can be sent to.
The Supplier processed this request and has agreed the date and time when the work should be carried out.
The MS is registered to the Supplier with the SMRA.
The MS is energised.
All appointments are in place with the Supplier’s HH agents.
The Supplier’s agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The Supplier requests the HHMOA to de-energise the MS.
The HHMOA arranges with the HHDC to collect final data.
The HHDC collects metering data for the day of the de-energisation and sends the HH advances to the Supplier, HHDA and LDSO.
After de-energising the meter, the HHMOA confirms the change of status and final meter readings to the HHDC, Supplier and LDSO.
The SMRA is notified of the change of energisation status by the Supplier and informs the HHDA and LDSO.
The HHDA carries out the appropriate aggregation runs. For the day of the de-energisation, consumption is attributed to the Supplier only for half-hours prior to the de-energisation. For the day after, no consumption is attributed to the Supplier.
Final Conditions:
The SMRA system has received notice of the de-energisation and advised the HHDA and LDSO accordingly.
The HHMOA has received a request from the Supplier to de-energise the meter and advised the Supplier, LDSO and HHDC of the status change and final register readings.
The HHDC has received a request to read HH period data, received notice of de-energisation and final readings, converted HH period data from UTC to BST and sent HH period readings on to the Supplier, LDSO and HHDA.
The HHDA has received notice of the de-energisation and aggregated HH advances for periods prior to the de-energisation.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Supplier instructs the LDSO to carry out the de-energisation. The LDSO arranges the collection of the final data with the HHDC and informs the appropriate parties when the de-energisation is completed.
AGS506: HH De-Energisation of Metering System, DC Not Notified
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSS107, JSD316
Initial Conditions:
The Customer has written to the Supplier requesting de-energisation of the Metering System (MS) and a mailing address is agreed where notification of completion of the work can be sent to.
The Supplier processed this request and has agreed the date and time when the work should be carried out.
The MS is registered to the Supplier with the SMRA.
The MS is energised.
All appointments are in place with the Supplier’s HH agents.
The Supplier’s agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The Supplier requests the HHMOA to de-energise the MS.
After de-energising the meter, the HHMOA confirms the change of status and final meter readings to the Supplier, HHDC and LDSO, but the HHDC does not receive or process the information.
The SMRA is notified of the change of energisation status by the Supplier and informs the HHDA and LDSO.
The HHDC is unable to collect metering data for the day of the de-energisation and sends estimated data to the Supplier, HHDA and LDSO.
The HHDA carries out the appropriate aggregation runs (Initial Settlement) using the estimated consumption values for the de-energised meter and reports the anomaly to the Data Collector and Supplier.
The HHDC requests information from the HHMOA, who responds by sending information about the energisation status and final register readings.
The HHDC advises the Supplier of the result of the investigation into their exception report and sends the final meter reading data to the Supplier, HHDA and LDSO for the Reconciliation run.
The HHDA carries out the appropriate aggregation runs (Reconciliation) for the day of de-energisation using the final readings.
NOTE: The HHDC must NOT resolve the exception prior to Initial Settlement or the exception will not occur as required.
Final Conditions:
The SMRA system has received notice of the de-energisation and advised the HHDA and LDSO accordingly.
The HHMOA has received a request from the Supplier to de-energise the meter and advised the Supplier, LDSO and HHDC of the status change and final register readings.
The HHDC has received notice of the de-energisation and final readings, converted HH period data from UTC to BST and sent HH period readings on to the Supplier, LDSO and HHDA.
The HHDA has received notice of the de-energisation and aggregated HH advances for periods prior to the de-energisation for the Reconciliation run.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. Instead of the HHDC, it may be the Supplier that requests the HHMOA to notify the HHDC of the de-energisation and of the final cumulative meter reading.
2. The Supplier may instruct the LDSO to carry out the de-energisation. The LDSO arranges the collection of the final data with the HHDC and informs the appropriate parties when the de-energisation is completed.
AGS507: HH De-Energisation & Disconnection of Metering System
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSS108, JSD317
Initial Conditions:
The Customer has written to the Supplier requesting the disconnection and de-energisation of the Metering System (MS).
The Supplier processed this request and has agreed the date and time when the work should be carried out.
The MS is registered to the Supplier with the SMRA.
The MS is energised.
All appointments are in place with the Supplier’s HH agents.
The Supplier’s agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The Supplier requests the HHMOA to de-energise the MS and agrees the date with the MOA for work to take place.
Subsequently, the Supplier instructs the LDSO to physically disconnect the meter.
The HHMOA arranges with the HHDC to collect final data.
After de-energising the meter, the HHMOA confirms the change of status and final meter readings to the HHDC, Supplier and LDSO.
The SMRA is notified of the change of energisation status by the Supplier and informs the HHDA and LDSO.
The LDSO notifies the SMRA of the disconnection, which occurred on the date requested, and they notify the HHDA that their appointment to the MS is terminated.
The HHDC collects metering data for the day of the de-energisation and sends the HH advances to the Supplier, HHDA and LDSO.
The Supplier receives notification from the LDSO that the disconnection has been successful.
The LDSO then updates their Registration Service and sends the final meter reading onto the HHDC for Validation and the SMRA in turn confirms details of the successful disconnection to the Supplier.
The Supplier terminates the HHMOA and HHDC appointments to the MS.
The HHDA carries out the appropriate aggregation runs. For the day of the de-energisation, consumption is attributed to the Supplier only for half-hours prior to the de-energisation. For the day after, no consumption is attributed to the Supplier.
Final Conditions:
The SMRA system has received notice of the de-energisation and disconnection and advised the Supplier, HHDA and LDSO accordingly.
The HHMOA has received a request from the Supplier to de-energise the meter and advised the Supplier, LDSO and HHDC of the status change and final register readings. It has received notice that its appointment to the MS has been terminated, and has noted the correct disconnection date.
The HHDC has received a request to read HH period data, received notice of de-energisation, disconnection and final readings, converted HH period data from UTC to BST and sent HH period readings on to the Supplier, LDSO and HHDA. It has received notice that its appointment to the MS has been terminated, and has noted the correct disconnection date.
The HHDA has received notice of the de-energisation and disconnection and aggregated HH advances for periods prior to the de-energisation. It has received notice that its appointment to the MS has been terminated, and has noted the correct disconnection date.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The Supplier instructs the Distributor to carry out both the de-energisation and disconnection on the same day. The Distributor arranges the collection of the final data with the HHDC and informs the appropriate parties when the disconnection is completed.
2. The disconnection occurs several days after the date requested.
AGS508: HH Re-Energisation of Metering System
Applicant Role: Party Agents (SMRA, HHDC, HHDA)
Associated Joint Storyboards: JSD320
Initial Conditions:
The Customer requires a currently de-energised half hourly metering point to be re-energised.
The HH Metering System (MS) is registered to the Supplier with the SMRA with all registration data items set.
Appointments are in place with all of the appropriate HH agents.
Previous valid meter readings are held at the HHDC and HHDA.
The Supplier, its agents and the SMRA have retained evidence, as appropriate, of the above.
The Story:
The Supplier requests the HHMOA to energise the MS, which it accepts.
Following the energisation, the HHMOA notifies the Supplier, LDSO and HHDC of the change of status and the initial meter register reading.
The Supplier notifies the SMRA, who then notifies the HHDA, of the change in energisation status.
The HHMOA requests a proving test from the HHDC. After comparing the expected and collected data, the HHMOA advises the Supplier, LDSO and HHDC of the successful proving test.
The HHDC collects metering data for the day of the change and sends the HH advances to the Supplier, HHDA and LDSO.
The HHDA carries out the appropriate aggregation run.
For the day before the change, no consumption is attributed to the Supplier for the MS.
For the day of the change, consumption is attributed to the Supplier for the MS.
Final Conditions:
The SMRA has received notice of the change in energisation status from the Supplier, acknowledged and informed the HHDA.
The HHMOA has energised the meter and informed the Supplier, LDSO and HHDC of the change in energisation status and the initial register readings. It has conducted proving in conjunction with the HHDC.
The HHDC has received notice of the energisation and initial readings, read the meter for HH consumption, and sent HH period readings on to the Supplier, LDSO and HHDA. It has conducted proving in conjunction with the HHMOA.
The HHDA has received notice of the change in energisation status from the SMRA. It has received HH advances from the HHDC and carried out the appropriate aggregation runs.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. The MS may be energised by the LDSO instead. In this case, the HHMOA receives notice of the energisation and initial register readings from the LDSO and then informs the HHDC.
AGS509: HH New UnMetered Supply (Equivalent Metering), Initial Registration, Energisation
Applicant Role: Party Agents (SMRA, UMSO, MA, HHDC, HHDA)
Associated Joint Storyboards: JSD211
Initial Conditions:
The LDSO has established a new HH unmetered supply point which will require two Photo Electric Cell Unit (PECU) arrays to provide equivalent metering.
The UMSO has agreed that the inventory meets the criteria for HH UMS.
There is no record of the Metering System (MS) on the Registration Service or any of the Supplier’s agents’ systems.
The Suppliers’ agents have retained evidence of all of the above.
The Story:
The UMSO requests the SMRA to create a UMS Skeleton registration record.
The SMRA informs the UMSO of the new MSID details and issues the UMS certificate to the customer and the Supplier.
The UMSO is notified of the appointed Meter Administrator (MA) and they agree the type of Equivalent Metering (EM) required and the location of the PECU array.
The UMSO confirms with the Supplier the type of EM and the location of the 2 PECU arrays. The Supplier and MA are notified of the EM technical details.
The Supplier registers liability for the MS with the SMRA and appoints all its agents including the MA.
The MA acknowledges its appointment and is notified of the HHDC.
The MA inputs information into the EM and confirms with the UMSO that it is correct.
The MA sends MTD to the HHDC and they liaise to ensure that the EM data can be read.
The UMSO energises the MS and confirms the energisation date with the Supplier and MA.
The Supplier confirms energisation with the SMRA.
The MA notifies the HHDC of the energisation date.
The HHDA is informed of its liability by the SMRA.
The HHDC collects EM data from the day of energisation and sends it to the Supplier, UMSO and HHDA.
The HHDA aggregates data for the day of the energisation.
Final Conditions:
The SMRA has recorded the creation of the new UMS and the supplier registration, agent appointments and energisation and notified the HHDA accordingly.
The UMSO has agreed the details of the UMS and communicated them with all the relevant parties. It has energised the UMS and notified the Supplier, then received HH metering data based on the equivalent metering.
The MA has accepted its appointment to the UMS, recorded the details of the UMS and configured the PECU arrays accordingly, provided technical details to the HHDC and sent them estimated HH consumption to check that it can be processed.
The HHDC has accepted its appointment to the new UMS and received technical details and other agents’ details. It has checked that it can process EM data from the MA, received notice of energisation and submitted consumption data to the HHDA for the first day.
The HHDA has aggregated the UMS as directed by the SMRA using the HH consumption provided by the HHDC.
Throughout the scenario, notifications received by the agents have been processed according to their normal business processes, including the updating of any records.
Throughout the scenario, routine confirmations and notifications have been sent to other market participants by the agents according to their normal business processes.
Variations:
The following variations may, optionally, be made part of this story but should be resolved so as not to impact the above Final Conditions.
1. (None currently suggested)
Guidelines to Arithmetic Accuracy Testing
Background
The objective of arithmetic testing is to ensure your systems and processes accurately perform the calculations required. Testing arithmetic accuracy both before and after you complete your business process testing can provide assurance the systems and processes will remain accurate throughout business-as-usual events. Additionally this testing may be used for regression tests following any software changes.
Scope of Arithmetic Testing
The test scripts and data should be designed to test the arithmetic accuracy of systems during an SMRA full refresh of the DA’s database followed by a compressed ‘normal’ Initial Volume Allocation Run (without profile calculation) for a particular trading day. Applicants should complete tests which are appropriate to the roles they are seeking Qualification for HH and NHH market sectors or both.
The tests should involve Supplier, Supplier Meter Registration Agent (SMRA), Data Collector and Data Aggregator actions; it is your responsibility to simulate flows from non-participating roles. An example of the scope of these tests could include:
NHH arithmetic
Testing could comprise of a wide scope, this could include 200 meters of various Line Loss Factor Classes, with different combinations of Profile Class, Standard Settlement Class and Time Pattern Regime. The scope could also include, 280 settlement registers; 80 meters with 2 settlement registers 120 with 1 settlement register. A mix of both Annualised Advances (AA) and Estimated Annual Consumption (EAC) values should be used to ensure variation in the testing. The volume tested should be reflective of the intended scale of operation.
HH arithmetic
Testing is similar to NHH and could include, 200 meters split across 2 GSP Groups and 2 LDSOs with various Profile Class values. Of the 200 meters used for testing a mixture of complete readings for the settlement day, some partial readings and none could be used to ensure variation in the testing. Estimated readings should be based on the GSP Group Average EAC for the appropriate Profile Class. The volume tested should be reflective of the intended scale of operation.
Guidelines to Performance, Capacity and Resilience Testing
Background
Performance, Capacity and Resilience tests are designed to allow you to demonstrate that your systems and processes will cope with the maximum projected activity levels within operational timescales for the number of Metering Systems (MS) for which you are seeking approval.
It is recommended that you perform this testing after successfully demonstrating that your systems and processes are accurate and that they correctly operate your business processes (i.e. after doing any arithmetic accuracy or storyboard testing).
Scope of Elexon Performance and Capacity Testing
Meter Readings
You will need to process a ‘realistic volume’ of meter readings for five traded days. The activity should be completed over three consecutive working days where the first and last represent normal daily processing volumes and the middle one a “busy day” including three normal day’s worth of transactions. This is to represent the processing around weekends.
The numbers of meters for each day should be based on your intended scale of operation.
To reflect the live market situation not all HH meters are settled fully on actual data, the HH readings should be 99% actual readings and 1% estimates.
For Example: If your expected daily volume is deemed to be 1000 HH readings, then one of the trading days will require 3000 readings to be processed within a 24 hour period.
Note: 1 HH reading here equals 48 period readings.
NHH readings for 2 meters should be processed on each working day and the EAC/AA data calculated and forwarded.
Data Aggregation
Data Aggregators should be able to run all five aggregation types (SF, R1, R2, R3 and RF) on each of the traded days making a total of 25 day’s worth of data (5 allocation runs by 5 days).
The NHHDA should be able to have adequate history for all of the NHH meters (EACs and AAs).
The HHDA should be able to have blocks of HH reading data for the appropriate traded days (i.e. up to 288 Working Days) prior to the run days.
Some exception conditions and discrepancies are expected on a small percentage of meters to reflect that the live market is not perfectly clean.
Variation Activities
You should be able to demonstrate the processing of meter registrations and exceptions in the course of normal day to day operations. While the actions may be determined from the Storyboards it may be more practical to detail the changes explicitly as follows.
NHH Example: If you are proposing to handle 1 million NHH meters the activities and volumes could be:
Activity | Volume per Traded Day (per 1 million meters) |
Change of Supplier | 800 |
Change of DC & DA, Change of SSC | 160 |
Change of MOA, DC & DA, Change of Metering System, Change of Profile Class | 120 |
Withdrawal of Meter Reading | 80 |
New Connection | 40 |
Change of DC | 40 |
HH example: If you are proposing to handle 1,000 HH meters the activities and volumes could be:
Activity | Volume per Traded Day (per 1 million meters) |
Change of Supplier | 6 |
Meter Replacement (by equivalent type) | 2 |
Change of MOA | 1 |
Change NHH to HH | 1 |
Change of DC |
|
(Change of DC & DA) | 1 as old 1 as new |
New Meter Point, registration, energisation | 1 |
SMRA example: If you are proposing to handle 10,000 meters (NHH and HH), the activities and volumes could be:
Activity | Volume per Traded Day (per 1 million meters) |
Change of Supplier and all NHH agents | 20 |
Change of NHH DC & DA, Change of SSC | 5 |
Change of all NHH agents, change of MS, change of PC | 5 |
De-energisation of an NHH Metering System | 5 |
New Connection (NHH) | 5 |
Change of NHHDC | 5 |
Change of Supplier and all HH agents | 40 |
Energisation of an HH Metering System | 5 |
Change of HH DC and DA | 5 |
Change of Measurement Class (NHH to HH) | 5 |
Change of HH MOA | 5 |
New HH Meter, Registration, Energisation | 5 |
You should calculate the volume of activity to reflect your proposed intended scale of operation. The above figures are for normal days so, for busy days, you should adjust the volumes accordingly.
The actual number of GSP Groups, Suppliers per GSP, LDSOs etc. should be calculated to reflect your proposed market position with a 50% uplift for future growth. During testing you will be expected to support multiple suppliers, GSP Groups and LDSOs concurrently. As a minimum, the meters should be spread across at least 4 GSP Groups and 5 Suppliers.
The choice of ad-hoc tests will be partly determined by the particular role you are undertaking, and they should be chosen to simulate meaningful activity by your organisation.
Scope of Elexon Resilience Testing
You should be able to demonstrate continuous fault-free operation for an agreed number of NHH and/or HH meters over an agreed number of working days. Every day, one or more meters should include some supplier initiated activity (e.g. change of Supplier, Agent or energisation status).
During the test period, you should perform three types of activity:
scheduled activities, such as Data Aggregation runs, will be run on all working days with Initial Allocation Runs (SF) and First Reconciliation Runs (R1) performed to a pre-defined schedule.
routine activities, such as data collection, will be run on all working days throughout the period.
ad-hoc (event-driven) activities, such as processing new connections and changes of Supplier, will be undertaken to ensure that you undertake a variety of ad-hoc updates during each working day.
The meters should ideally be split between several separate GSP Groups. If the required processing cannot be conducted on each of the working days, then the test should be restarted.
Resilience testing should normally be undertaken in parallel with Storyboard testing (if that is being done) to minimise the total elapse time of the Qualification tests. However there is a risk associated with this as resilience testing should be run on unchanged systems. If it were necessary to implement a software fix (e.g. during Storyboard testing) to resolve an error, then the resilience period would need to be extended to demonstrate resilience on the new release of the system.
Note: The above tests involve Supplier, SMRA, Meter Operator, Data Collector and Data Aggregator actions; it is your responsibility to simulate flows from market roles other than yourself.
Further Information
Further information please contact the BSC Service Desk or call 0370 010 6950.
Intellectual Property Rights, Copyright and Disclaimer The copyright and other intellectual property rights in this document are vested in Elexon or appear with the consent of the copyright owner. These materials are made available for you for the purposes of your participation in the electricity industry. If you have an interest in the electricity industry, you may view, download, copy, distribute, modify, transmit, publish, sell or create derivative works (in whatever format) from this document or in other cases use for personal academic or other non-commercial purposes. All copyright and other proprietary notices contained in the document must be retained on any copy you make. All other rights of the copyright owner not expressly dealt with above are reserved. No representation, warranty or guarantee is made that the information in this document is accurate or complete. While care is taken in the collection and provision of this information, Elexon Limited shall not be liable for any errors, omissions, misstatements or mistakes in any information or damages resulting from the use of this information or action taken in reliance on it. |
1 Elexon Ltd is the Balancing and Settlement Code Company (BSCCo.), pursuant to Section X: Annex X-1 of the Balancing and Settlement Code (BSC).