Supporting the Unique Requirements of VLPs

Wider access to the BM will promote competition and provide the Electricity National Control Centre (ENCC) with greater access to flexibility. Wider Access will lower cost to consumers, improve quality of service and contribute towards zero carbon operation of Great Britain’s electricity system by 2025.

The implementation of Wider Access by National Grid ESO in December 2019 will see the beginning of Virtual Lead Party (VLP) operations. While VLPs are exempt from some of the requirements imposed on other BSC Party Roles, they are required to submit PNs, MEL and Bid Offer Data via EDT and establish EDL systems for the communication of BOAs and post gate closure Dynamic Data submissions. In addition, due to their unique relationship with suppliers, they must calculate and submit Delivered Volumes at MSID Pair level, a requirement that is supported by Sentinel VLP SVAA module.

Key Features

  • Capture of Secondary BM Unit component baseline levels
  • Capture of actual metered values
  • Determination of the Delivered Volumes
  • Interface to the Elexon SVAA Agent.

How it Works

Receipt of Input Data

Maintain a register of the relationships between Secondary BM Units and their component MSID Pairs and import the component meter data at MSID level.

Calculation of the Delivered Volume

Calculate the Delivered Volume at MSID level and store the calculated values for actual energy, baseline energy and Delivered Energy.

Creation and submission of P0282 flows

Create P0282 files once all the Delivered Volumes for a Settlement Day have been calculated. If not all the input data has arrived, Sentinel will produce the P0282 with what data is available and raise an alarm. For each submission Sentinel will receive and process the file returned by Elexon (P0283: Rejection, P0284: Confirmation or P0285: Exception Report).

Viewing imports, submissions and responses

Display a record for each baseline and actual meter readings file imported, each P0282 file submitted and each P0283, P0284, P0285 and P0288 file received.

Editing and resubmitting P0282 files

Resubmit P0282 files to override previously submitted data. Sentinel allows you to edit the data in a P0282 file and submit the edited file manually, maintaining a version record of amended files in order to display a revision history.

Creating and submitting a P0282 manually

Create and submit a P0282 file manually applying validation irrespective of whether the submission is manually, or system initiated.

Importing SVAA Feedback Files

Imports P0283, P0284 and P0285 feedback flies and records the status of respective MSID/Settlement Periods.

Viewing the latest submitted Delivered Volume position

Provides a view of the submitted position for Delivered Volume for a selected day for both MSIDs and BM Units.

Supplier Delivered Volumes

Suppliers affected by customers participating in Balancing Services activities are informed of the volumes affected via the P0287 file. Sentinel will download, decrypt and save any P0287 file issued to the BSC Party.

Alarms

The Sentinel Alarms system informs users of various operational events including any breaks in the SVAA interface process.

Data Export

The Sentinel API will allow you to extract latest data submitted in a P0282 file for a given Settlement Date and BM Unit, latest MSID position data and latest data received in a P0288 file.

Why are Delivered Volume Submissions Needed?

A VLP is a non-Trading Party operating Secondary BM Units for the provision of Balancing Services to the National Grid ESO via BM (and RR) actions. A Secondary BM Unit is a GSP Group specific collection of SMRS registered customer meters, not restricted to a single Supplier.

In the event that a Secondary BM Unit is instructed to vary its energy consumption or generation there will be an effect on the imbalance position of each of the Suppliers. As there could be many such Units across many VLPs affecting a Supplier there is a need to determine the net effect of all these Units so that adjustment can be made to the Supplier’s Energy Account Imbalance position to ensure it is not disadvantaged.

This adjustment is calculated by the SVAA and a key input to this is the Delivered Volume; the amount of energy delivered in response to a Balancing Services Instruction. Responsibility for submitting the Delivered Volume at an MSID Pair level to the SVAA falls to the VLP.

Delivered Volumes must be submitted within 1 working day of the relevant Settlement Date in the SVAA P0282 flow, to which the SVAA may respond with a Rejection (P0283), Confirmation (P0284) or Exception Report (P0285). The Secondary BM Unit Delivered Volumes position is reported back to the VLP by the SVAA via the P0288 flow.

 

 

 

Request a call back