...
The trigger that begins the process of generating and submitting validating an algo bid is the publication of a new 5min forecast (for example AEMO’s p5min). Once this process is completed the algo bid is ready to be submitted, a scheduler is invoked whereby the set of algo bids are submitted at a predefined number of seconds into a dispatch interval. For example 240 seconds into the dispatch interval. In this instance the The AEMO acknowledged timestamp will generally be 2-5 seconds later after the scheduled bid time (for example 10:04:03).
...
Bid Formulation and Submit Cycle
...
Note that all three checks must be validated before an Algo Bid will be submitted. Whatever happens pdBidr will repeat the cycle again.
| Info |
|---|
The first two validation checks are applied to each individual bid. For example if Submit Mode is OFF for an individual bid then only that bid is not submitted. However if there is a new reference bid detected then all bid from that solve will not be submitted. |
Synchronisation
...
pdBidr synchronises with the eHub-API. This is a direct query to AEMO to check and download any new bids from third party systems. If a new manual rebid is detected then this bid becomes the Latest Manual Acknowledged Bid (Reference Bid). Mini Sync checks that there are no new AEMO identifiers without downloading new bids. A mini sync is performed because it is completed more quickly than a Sync.
...