Dispatch Notification Load

  • 147 Views
  • Last post 2 weeks ago
  • Discussion is solved
rgbowmaker posted this 3 weeks ago

I have some questions re Dispatch Notification Load (DNL):

  • Is anyone currently participating in the wholesale market via DNL?
  • If they are, would this appear in the 'Bids' wholesale dataset?
  • If so, is there any way to differentiate DNL vs DD in the bids data?

Thanks!

Order by: Standard | Newest | Votes
Tuong Nguyen posted this 3 weeks ago

Hi Richard,

In the SPD model and the associated bids dataset, Dispatchable Demand (DD) and Dispatch Notification Load (DNL) are treated the same — there is no distinction between the two in the SPD input files or results.

If a participant is submitting DNL offers, these will appear in the SPD bids data just like DD offers. However, the dataset does not include any flags or identifiers to differentiate DNL from DD.

DNL is generally used for small-scale load (typically under 10 MW) and cannot participate in instantaneous reserves (IL). For more detail on the distinctions between DD and DNL, I recommend referring to the guideline GL-EA-1052 Guideline for Connection DD & DNL into the Electricity Market.

According to this document, the only potential DNL currently in the market is the “STK0331 SZR0” bid, which is from SolarZero.

 

Regards,
Tuong Nguyen

  • Liked by
  • rgbowmaker
rgbowmaker posted this 3 weeks ago

Hi Tuong,

Thanks, this is really helpful.

Richard

Isaac_Severinsen posted this 2 weeks ago

Hi Tuong,

Could you elaborate a bit on adding new DD/DNL to vSPD?

Overrides work fine for "STK0331 SZR0" as you say, but none of the other bids from "vSPD_Overrides.xlsx" seem to work.
Is there an easy way to 're-enable' them withing vSPD or is it within the .gdx files itself.

As an example lets say i wanted to investigate the impact of Norske-Skog, if they were still around today.

I'd also be interested to know how the Binary Load flag is handled, from the document you linked.

Cheers,

Isaac

Tuong Nguyen posted this 2 weeks ago

Hi Isaac,

I'm not entirely certain about the issue you've described, but one possibility is that the bid you're trying to override doesn't exist for the specific period or interval. It's also worth noting that Norske Skog has not submitted any dispatchable demand bids since October 2022.

You also mentioned the "Binary Load" flag—could you clarify exactly what you're referring to in the context of vSPD or SPD data?

Please keep in mind that the current overrides functionality only allows you to modify existing bids or offers. If a bid or offer doesn't exist for the specified period or interval, the override will be ignored.

Cheers,

Tuong Nguyen

Isaac_Severinsen posted this 2 weeks ago

Hi Tuong,

 

Thanks for the information,

I suppose I would have to add new bids to the input gdx instead of relying upon overrides.

I suppose this would entail in vSPD-5.0.2 :

  • Adding a new row for i_dateTimeBidNode
  • Adding a new row for i_dateTimeBidParameter
  • Adding a new row for i_dateTimeBidTrader
  • Adding new rows to i_dateTimeEnergyBid

With BidNode, the bid and the node have the same name for the case of SZR0, is this always the same, would STK0331 work as a node instead of STK0331 SZR0? looking at some old GDX's: SKOG used both KAW0113 DLS0/1 for bid and node. Is there any issue with just adding this back in?

Bid Parameter has an attribute 'dispatchable' are there any other options here?

Bid Trader is relatviely straightforward but are there any definitions for these? e.g. who is "38527"

 

Binary Load is mentioned in section 1.4.3 of this document you linked:

GL-EA-1052 Guideline for Connection DD & DNL into the Electricity Market

Cheers,

Isaac

Tuong Nguyen posted this 2 weeks ago

Hi Isaac,

At this stage, we haven't developed any override or template functionality in vSPD to support the addition of new elements or entities. If you need to add something that doesn’t already exist in the model input—such as a new bid or participant—you’ll need to modify the input GDX file directly, or implement the necessary logic in the vSPD code base yourself. Unfortunately, due to resource constraints, we don’t expect this feature to be added to vSPD in the near future.

Regarding bid parameters: in SPD, each bid has three attributes—dispatchable, discrete, and difference. While the model does support discrete bids (i.e. binary load), there are currently no examples of these in the published market data, so you won't find any relevant entries in the input files.

Lastly, "38527" <==> SKOG <==> Norske Skog 

Best regards,

Tuong Nguyen