Elexon provides a set of storyboards and other aids that can be used when designing a test programme to meet the BSC's Supplier Volume Allocation (SVA) Qualification Requirements.

12.0

<div data-id="background" style="text-align:left">Background</div>

<div data-id="applicability-of-the-storyboards" style="text-align:left">Applicability of the Storyboards</div>

<div data-id="structure-of-the-storyboards" style="text-align:left">Structure of the Storyboards</div>

<div data-id="completion-of-the-storyboards" style="text-align:left">Completion of the Storyboards</div>

<div data-id="arithmetic-accuracy-testing" style="text-align:left">Arithmetic Accuracy Testing</div>

<div data-id="performance-capacity-and-resilience-testing" style="text-align:left">Performance, Capacity and Resilience Testing</div>

<div data-id="introduction" style="text-align:left">Introduction</div>

<div data-id="initial-conditions" style="text-align:left">Initial Conditions:</div>

<div data-id="the-story" style="text-align:left">The Story:</div>

<div data-id="final-conditions" style="text-align:left">Final Conditions:</div>

<div data-id="variations" style="text-align:left">Variations:</div>

<div data-id="ags401-1" style="text-align:left"><span>1. The <u class='defined-term'>Customer</u> has recently been registered as a special needs person by the local authority.</span></div>

<div data-id="ags401-2" style="text-align:left"><span>2. The <u class='defined-term'>Supplier</u> 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).</span></div>

<div data-id="ags401-3" style="text-align:left"><span>3. The old NHHDC does not provide valid EAC/AA history.</span></div>

<div data-id="ags401-4" style="text-align:left"><span>4. The new <u class='defined-term'>Supplier</u> disputes the CoS reading prior to first reconciliation. A new COR is agreed with the old <u class='defined-term'>Supplier</u>. 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.</span></div>

<div data-id="ags401-5" style="text-align:left"><span>5. The meter reading does not have to be COR. Alternative reading types may be used by making arrangements with the appropriate agents.</span></div>

<div data-id="ags401-6" style="text-align:left"><span>6. There may be no change of <u class='defined-term'>Supplier</u>, just a change of agents; or there may be only a change of one or some of the agents.</span></div>

<div data-id="ags401" style="text-align:left">AGS401: NHH Change of <u class='defined-term'>Supplier</u>, MOA, DC and DA (concurrent)</div>

<div data-id="ags402" style="text-align:left">AGS402: NHH Change of <u class='defined-term'>Supplier</u>, MOA, DC, DA, and <u class='defined-term'>Metering System</u></div>

<div data-id="ags403-1" style="text-align:left"><span>1. The <u class='defined-term'>Supplier</u> 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).</span></div>

<div data-id="ags403" style="text-align:left">AGS403: NHH Change of <u class='defined-term'>Supplier</u>, MOA, DC, DA, Invalid <u class='defined-term'>Meter</u> Reading from DC</div>

<div data-id="ags404-1" style="text-align:left"><span>1. The <u class='defined-term'>Supplier</u> instructs the NHHDC to change the <u class='defined-term'>Profile Class</u> of the metering point where no physical change of meter is required.</span></div>

<div data-id="ags404-2" style="text-align:left"><span>2. The <u class='defined-term'>SMRA</u> fails to receive the registration updates for the new metering details. As a result, exception reports are sent to the <u class='defined-term'>Supplier</u> and corrective actions taken. </span></div>

<div data-id="ags404-3" style="text-align:left"><span>3. The NHHDC is unable to obtain the required initial readings, so informs the <u class='defined-term'>Supplier</u> and acts on its instructions.</span></div>

<div data-id="ags404-4" style="text-align:left"><span>4. The reprogramming may not require all of the suggested changes to be effected.</span></div>

<div data-id="ags404" style="text-align:left">AGS404: NHH Change of SSC and TPR</div>

<div data-id="ags405-1" style="text-align:left"><span>1. Replacement with various types of PPM (key, token or smart).</span></div>

<div data-id="ags405-2" style="text-align:left"><span>2. For the type of PPM chosen, the new meter configuration may not require a change of SSC.</span></div>

<div data-id="ags405-3" style="margin-left:0.47in;text-align:left;text-indent:-0.47in"><span>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:</span></div>

<div data-id="ags405" style="text-align:left">AGS405: NHH Credit <u class='defined-term'>Meter</u> Replaced with Prepayment <u class='defined-term'>Meter</u></div>

<div data-id="ags406" style="text-align:left">AGS406: NHH Withdrawal of <u class='defined-term'>Meter</u> Reading</div>

<div data-id="ags407-1" style="text-align:left"><span>1. (None currently suggested.)</span></div>

<div data-id="ags407" style="text-align:left">AGS407: NHH De-Energisation</div>

<div data-id="ags408-1" style="text-align:left"><span>1. (None currently suggested.)</span></div>

<div data-id="ags408" style="text-align:left">AGS408: NHH De-Energisation &amp; Disconnection</div>

<div data-id="ags409-1" style="text-align:left"><span>1. The <u class='defined-term'>Supplier</u> does not notify the <u class='defined-term'>SMRA</u> of the re-<u class='defined-term'>energisation</u> so the <u class='defined-term'>SMRA</u> does not notify the NHHDA. For the day of re-<u class='defined-term'>energisation</u>, the NHHDA attributes zero consumption instead of using the new EAC supplied by the NHHDC, as the <u class='defined-term'>Metering System</u> is de-energised according to the <u class='defined-term'>SMRA</u>. An exception is identified from an Exception Report during the Initial <u class='defined-term'>Supplier Volume Allocation</u> processing.</span></div>

<div data-id="resolution" style="margin-left:0.47in;text-align:left"><span>Resolution: The NHHDA requests a comparison of NHHDC and <u class='defined-term'>SMRA</u> data and the <u class='defined-term'>Supplier</u> is notified of the discrepancy in the Energisation Status. The <u class='defined-term'>Supplier</u> notifies the <u class='defined-term'>SMRA</u>, who in turn notifies the NHHDA. In the next aggregation run for the day of re-<u class='defined-term'>energisation</u>, the NHHDA will use the new EAC supplied by the NHHDC.</span></div>

<div data-id="ags409-2" style="text-align:left"><span>2. The <u class='defined-term'>Meter</u> Operator goes on site but cannot energise the <u class='defined-term'>Metering System</u> due to a damaged supply cable. The <u class='defined-term'>Supplier</u> is informed of this and tasks the Distributor with the <u class='defined-term'>energisation</u>. The Distributor successfully energises the meter, takes an initial meter reading and notifies the <u class='defined-term'>Supplier</u> of the successful re-<u class='defined-term'>energisation</u>.</span></div>

<div data-id="ags409" style="text-align:left">AGS409: NHH Re-Energisation</div>

<div data-id="ags410-1" style="text-align:left"><span>1. The <u class='defined-term'>Customer</u> has chosen a new <u class='defined-term'>Meter</u> Operator who is qualified in both Non-Half Hourly and Half Hourly market sectors.</span></div>

<div data-id="ags410-2" style="text-align:left"><span>2. The day of <u class='defined-term'>energisation</u> 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.</span></div>

<div data-id="ags410-3" style="text-align:left"><span>3. The proving test may fails, in which case the HHMOA must initiate a re-test by arrangement with the HHDC.</span></div>

<div data-id="ags410" style="text-align:left">AGS410: NHH to HH - Change of <u class='defined-term'>Measurement Class</u></div>

<div data-id="final-conditions" style="text-align:left">Final conditions:</div>

<div data-id="ags411" style="text-align:left">AGS411: NHH to HH (concurrent Change of <u class='defined-term'>Supplier</u>)</div>

<div data-id="initial-condition" style="text-align:left">Initial Condition:</div>

<div data-id="the-story" style="text-align:left">The story:</div>

<div data-id="ags412" style="text-align:left">AGS412: NHH to HH (no Change of <u class='defined-term'>Supplier</u>)</div>

<div data-id="non-half-hourly-storyboards" style="text-align:left">Non Half Hourly Storyboards</div>

<div data-id="ags501-1" style="text-align:left"><span>1. There may be no change of agents involved. The old and new <u class='defined-term'>Supplier</u> have appointed the same HH agents for the MS. This will mean that some of the above final conditions do not apply.</span></div>

<div data-id="ags501" style="text-align:left">AGS501: HH Change of <u class='defined-term'>Supplier</u>, MOA, DC and DA</div>

<div data-id="ags502-1" style="text-align:left"><span>1. This story may be run for a variety of meter configurations to demonstrate that the relationships between Agents, <u class='defined-term'>GSP Group</u>s and <u class='defined-term'>LDSO</u>s can be handled correctly. E.G Maintenance of LLF <u class='defined-term'>Class</u>es for multiple <u class='defined-term'>LDSO</u>s within a single <u class='defined-term'>GSP Group</u>.</span></div>

<div data-id="ags502" style="text-align:left">AGS502: HH Change of LLF <u class='defined-term'>Class</u></div>

<div data-id="ags503-1" style="text-align:left"><span>1. The HHDC may decide to use any of the 4 methods for proving the meter, making the appropriate changes to the story.</span></div>

<div data-id="ags503" style="text-align:left">AGS503: HH Replacement of <u class='defined-term'>Meter</u> &amp; Proving Test</div>

<div data-id="ags504-1" style="text-align:left"><span>1. Either skeleton or full registration details may be sent to the <u class='defined-term'>SMRA</u> by the supplier. When the <u class='defined-term'>SMRA</u> 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 <u class='defined-term'>energisation</u> status. If skeleton registration then subsequent instructions will notify the HHDA of their appointment, the HHDC appointment AND the <u class='defined-term'>energisation</u> status.</span></div>

<div data-id="ags504" style="text-align:left">AGS504: HH New <u class='defined-term'>Metering System</u>, Initial Registration, Energisation</div>

<div data-id="ags505-1" style="text-align:left"><span>1. The <u class='defined-term'>Supplier</u> instructs the <u class='defined-term'>LDSO</u> to carry out the <u class='defined-term'>de-energisation</u>. The <u class='defined-term'>LDSO</u> arranges the collection of the final data with the HHDC and informs the appropriate parties when the <u class='defined-term'>de-energisation</u> is completed. </span></div>

<div data-id="ags505" style="text-align:left">AGS505: HH De-Energisation of <u class='defined-term'>Metering System</u></div>

<div data-id="ags506-1" style="text-align:left"><span>1. Instead of the HHDC, it may be the <u class='defined-term'>Supplier</u> that requests the HHMOA to notify the HHDC of the <u class='defined-term'>de-energisation</u> and of the final cumulative meter reading.</span></div>

<div data-id="ags506-2" style="text-align:left"><span>2. The <u class='defined-term'>Supplier</u> may instruct the <u class='defined-term'>LDSO</u> to carry out the <u class='defined-term'>de-energisation</u>. The <u class='defined-term'>LDSO</u> arranges the collection of the final data with the HHDC and informs the appropriate parties when the <u class='defined-term'>de-energisation</u> is completed.</span></div>

<div data-id="ags506" style="text-align:left">AGS506: HH De-Energisation of <u class='defined-term'>Metering System</u>, DC Not Notified</div>

<div data-id="ags507-1" style="text-align:left"><span>1. The <u class='defined-term'>Supplier</u> instructs the Distributor to carry out both the <u class='defined-term'>de-energisation</u> 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.</span></div>

<div data-id="ags507-2" style="text-align:left"><span>2. The disconnection occurs several days after the date requested.</span></div>

<div data-id="ags507" style="text-align:left">AGS507: HH De-Energisation &amp; Disconnection of <u class='defined-term'>Metering System</u></div>

<div data-id="ags508-1" style="text-align:left"><span>1. The MS may be energised by the <u class='defined-term'>LDSO</u> instead. In this case, the HHMOA receives notice of the <u class='defined-term'>energisation</u> and initial register readings from the <u class='defined-term'>LDSO</u> and then informs the HHDC.</span></div>

<div data-id="ags508" style="text-align:left">AGS508: HH Re-Energisation of <u class='defined-term'>Metering System</u></div>

<div data-id="ags509-1" style="text-align:left"><span>1. (None currently suggested)</span></div>

<div data-id="ags509" style="text-align:left">AGS509: HH New <u class='defined-term'>Unmetered Supply</u> (<u class='defined-term'>Equivalent Meter</u>ing), Initial Registration, Energisation</div>

<div data-id="half-hourly-storyboards" style="text-align:left">Half-Hourly Storyboards</div>

<div data-id="scope-of-arithmetic-testing" style="text-align:left">Scope of Arithmetic Testing</div>

<div data-id="guidelines-to-arithmetic-accuracy-testing" style="text-align:left">Guidelines to Arithmetic Accuracy Testing</div>

<div data-id="meter-readings" style="text-align:left"><u class='defined-term'>Meter</u> Readings</div>

<div data-id="data-aggregation" style="text-align:left">Data Aggregation</div>

<div data-id="variation-activities" style="text-align:left">Variation Activities</div>

<div data-id="scope-of-elexon-performance-and-capacity-testing" style="text-align:left">Scope of Elexon Performance and Capacity Testing</div>

<div data-id="scope-of-elexon-resilience-testing" style="text-align:left">Scope of Elexon Resilience Testing</div>

<div data-id="guidelines-to-performance-capacity-and-resilience-testing" style="text-align:left">Guidelines to Performance, Capacity and Resilience Testing</div>

<div data-id="further-information" style="text-align:left">Further Information</div>

CONTENTS

SVA Qualification: Joint Storyboards and Test Guidelines V12.0