Bidding and Dispatch
The IESS Integrating Energy Storage Systems project is seeking to better integrate storage and hybrid systems into the National Electricity Market See Relevant Rules or Procedures (NEM). There are significant changes to registration and dispatch Energy Rules Terms arrangements as well as in areas such as non-energy cost recovery, performance standards, and participation options for aggregation of small resources, including batteries.
High-level changes
The high-level changes to the Bidding and Dispatch See National Electricity Rules stream are as follows:
Application |
Description |
Submit Energy and FCAS bids JSON Format changes |
All Participant Submit Energy and FCAS bids submission methods (FTP, API, Markets Portal Web UI and File Upload) leverage the single submit bids JSON format. The format is enhanced to support the additional attribute data for BDU Energy and FCAS bids. For more details, see Bidding submissions. The modified format supports backward compatibility. Enhance Bid format for BDU: Energy bids Supports a new conditional direction indicator (LOAD, GEN) allowing submission of separate energyBids object and energyPeriods arrays (10 price, availability, and associated parameters) for the Load side and Generation side of the BDU (20 in total). This field is mandatory for BDU Energy and Regulation FCAS bid submissions. For non-BDU, the attribute is optional and may be provided. It is optional to support backward compatibility. If provided, validation is performed as per allowable combination. Contingency FCAS Offers unchanged (single FCAS enablement - 10 bands) with variation the four trapezium period parameters support provision of positive and negative numeric values (currently positive only). Regulation FCAS Supports a new optional direction indicator allowing submission of separate fcasBids array and fcasPeriods arrays (10 price, availability and associated parameters) for the Load side and Generation side of the BDU (20 in total). Submit bids response Formats remain unchanged, existing attributes support new error BDU responses. |
APIs |
Submit Bids, Get Bid(s) Get Submission(s) API requests and responses to support the extended JSON format for BDU, syntax/schema/business validation for the amended BDU Bid submission format. Backward compatibility for non BDU. |
FTP Participant Server |
Participant file server (FTP protocols) to support extended JSON format for BDU i.e., syntax/schema/business validation for the amended BDU Bid submission format. Backward compatibility for non BDU. |
Markets Portal: Energy and FCAS Bids and file upload |
Energy & FCAS 5min Bids web portal view/modify/submit (UI) and file upload functionality support for BDU Energy and FCAS bids. |
NEMReports, MMS Data Model and Market Notices |
Enhance the existing Market Reports and Notices to support the introduction of the new IRP participant category and BDU generally described as:
|
MT PASA offers |
MT PASA Offers support submissions from Integrated Resource Providers (IRP) and DUID type BDU. IRP offers leveraged in PASA modelling. Data Interchange and MT PASA DUID availability report support of IRP offer(s). |
PASA (PD and ST) |
PASA calculations (processing) and outputs include BDU generation PASA related data (BDU Load PASA availability excluded). No change to formats. |
Markets Portal > Market Info |
Uplift Markets Portal > EMMS > Market Info interfaces (View Market Summary, View Dispatch and View Pre-dispatch) as per the current web portal framework |
NEM Data Dashboard |
Extend support to include and display IRP and BDU related details:
|
Bidding submissions
The NEM Dispatch Bidding systems and interfaces allows authorised participants to submit and retrieve their NEM Dispatch Bids/Offers. AEMO Australian Energy Market Operator uses effective NEM See Relevant Rules or ProceduresDispatch Bid See National Electricity Rules/Offer Energy, Dispatch, FCAS Offer, MNSP, MTPASA Bid or Offer submission submissions in the Central Dispatch process.
AEMO allows participant submission and response of Energy The unit must be a generator for the service type: ‘energy’. Loads cannot bid for mandatory restrictions capacity., FCAS Frequency Controlled Ancillary Services. A service that balances, over short intervals (shorter than the dispatch interval), the power supplied by generating units and the power consumed by loads., or MNSP Market Network Service Provider. A network service provider (NSP) that earns revenue from the spot market. Bids by four methods. Under IESS, all methods are extended to support the introduction of BDU Bi-directional Unit. A bi-directional unit capable of charge and discharge; for example, battery technologies..
- Directly in the Energy and FCAS Bids web interface using the Markets Portal Web applications for registered participants only. Requires access to MarketNet. web.
- JSON JavaScript Object Notification file upload to the Energy and FCAS Bids web interface using the Markets Portal web.
- FTP File transfer protocol to the participant file server\ParticipantID\Export\Bids folder.
- Submit Bids APIs over MarketNet AEMO's private VPN for Registered Participants. A network of more than 300 registered participants in the National Electricity Market, including market generators, transmission network service providers, distribution network service providers, and market customers. and Internet.
- Participants can also query previously submitted bid information using get API Application Programming Interface; a set of clearly defined methods of communication between various software components. endpoints – getSubmission, getSubmissions, getBids, and getBid. For more details on the existing Bidding and Dispatch APIs, see NEM Dispatch Bidding Open API Specification Reference.
The following table provides a list of modified and updated fields in the JSON format for BDUs:
Energy bids
Name |
Rule |
Data Type |
Description |
energyBids |
Mandatory |
Object |
Object |
tradingDate |
Mandatory |
String |
String in date format Format: |
duid |
Mandatory |
String(10) |
Dispatchable Unit identifier recorded in AEMO's Must be upper case |
direction |
Optional |
String(8) |
Mandatory for BDU submissions (excludes Contingency FCAS); optional for all other unit types. To indicate no value, remove the entire attribute. Validation performed if provided. See Direction Field Enumeration and Use table for allowable enumerated values and use. type: string maximum 15, format: upper case. For BDU, direction expresses if associated energyBids and energyPeriods reflect the LOAD or GEN side of the BDU. |
prices |
Mandatory |
Array |
The band price. Required. Type: number. Format: multiple of: 0.01 e.g. 0.01, etc. For all unit types prices are 0.00 or positive. |
fastStartProfile |
Optional |
Object |
Only valid for fast-start units. If not provided, the unit is treated as slow start, and all values in the data model default to null. Fast-Start Inflexibility Profile Properties: minimumLOAD, t1, t2, t3, t4 Required: minimumLOAD, t1, t2, t3, t4 For BDU and semi-scheduled generating units remove the entire attribute (must not be provided). |
dailyEnergyConstraint |
Optional |
Integer (number) |
Represents the maximum energy available from a constrained Plant in the Trading Day Only relevant to the Energy Service Type Cannot be negative Expressed in MWh/day minimum: 0 maximum: 999999 For BDU remove the entire attribute (must not be provided). |
rebidExplanation |
Conditional |
Object |
Required for rebids, fixed LOAD, and low ramp rates Properties: reason, eventTime, awareTime, decisionTime, category For BDU, if supplied for direction LOAD and GEN, the values must be identical (single provision of rebidExplanaton for LOAD and GEN acceptable) |
Energy periods
Name |
Rule |
Data Type |
Description |
energyPeriods |
Mandatory |
Array |
Mandatory for energy bids only. |
periodId |
Mandatory |
Integer |
The 5-minute trading interval from 4:05 am to 4:00 am. Required for energyPeriods, mnspPeriods, and fcasPeriods, type: integer minimum item: 1, maximum item: 288, format: 1, 2, 3...288 |
maxAvail |
Mandatory |
Integer |
Maximum availability for a period, integer minimum 0, format: whole numbers, value: megawatts. For BDU for each direction (LOAD and GEN) integer minimum 0, format: whole numbers, value: megawatts. |
rampUpRate |
Mandatory |
Integer |
Rate of change up - The maximum rate of increase for the unit. Required for energyPeriods and mnspPeriods, type: integer minimum 0, format: whole numbers, value: megawatts. For BDU for each direction (LOAD and GEN) integer minimum 0, format: whole numbers, value: MW/min |
rampDownRate |
Mandatory |
Integer |
Rate of change down - The maximum rate of decrease for the unit. Required for energyPeriods and mnspPeriods, type: integer maximum 0, format: whole numbers, value: megawatts. For BDU for each direction (LOAD and GEN) integer minimum 0, format: whole numbers, value: MW/min |
pasaAvail |
Mandatory |
Integer |
The unit's capability including any capability potentially available in 24 hours, including the offered availability. Required for energyPeriods, mnspPeriods, type: integer minimum: 0, format: whole numbers, value: megawatts. For BDU for each direction (LOAD and GEN) integer minimum 0, format: whole numbers, value: megawatts. |
fixedLoad |
Optional |
Integer |
Fixed unit output, in MW. Must be 1MW or greater. For BDU provide a single (1) fixedLoad for LOAD and GEN (direction) - remove the entire attribute for direction not provided.
|
bandAvail |
Mandatory |
Array |
The availability for each 10 price bands. Required for energyPeriods, mnspPeriods, and fcasPeriods. Required properties: avail, type: array, minimum: 10 maximum: 10, format. For BDU for each direction (LOAD and GEN) required properties: avail, type: array, minimum: 10 maximum: 10, format: whole number (0 and positive values for each direction) |
energyLimit |
Optional |
Integer |
Optional for BDU Bid submissions. For non-BDU remove the entire attribute. For each direction (LOAD and GEN) integer minimum 0, format: whole numbers, value: megawatthours. Direction of ‘GEN’ indicates the min charge level, and Direction of ‘LOAD’ indicates the max charge level. Rules:
|
FCAS bids
Name |
Rule |
Data Type |
Description |
fcasBids |
Mandatory |
Array |
Mandatory for FCAS Offers only. |
tradingDate |
Mandatory |
String |
String in date format |
duid |
Mandatory |
String(10) |
Dispatchable Unit identifier recorded in AEMO's |
direction |
Optional |
String(15) |
Mandatory for BDU Regulation FCAS Bid submissions (service = RAISEREG or LOWERREG); optional for all other unit types and BDU Contingency FCAS. To indicate no value, remove the entire attribute. Validation performed if provided. See 'Direction Field Enumeration and Use' table for allowable enumerated values and use. type: string maximum 15, format: upper case. |
prices |
Mandatory |
Array |
An array of 10 prices - Items:price minItems: 10 maxItems: 10 e.g. [0.00, 0.00, 20.00, …] For all unit types prices are 0.00 or positive. |
service |
Mandatory |
String (10) |
One of the FCAS service types. Required for fcasBid. Required properties: one of, RAISE1SEC, RAISE6SEC, RAISE60SEC, RAISE5MIN, RAISEREG, LOWER1SEC, LOWER6SEC, LOWER60SEC, LOWER5MIN, LOWERREG, type: string maximum 10, format: upper case |
rebidExplanation |
Conditional |
Object |
Required for rebids. Properties: reason, eventTime, awareTime, decisionTime, category. For BDU, if supplied for direction LOAD and GEN, the values must be identical (single provision of rebidExplanaton for LOAD and GEN acceptable) |
FCAS periods
Name |
Rule |
Data Type |
Description |
fcasPeriods |
Mandatory |
Array |
Mandatory for FCAS Offers only. |
periodId |
Mandatory |
Integer |
The 5-minute trading interval from 4:05 am to 4:00 am. Required for energyPeriods, mnspPeriods, and fcasPeriods, type: integer minimum item: 1, maximum item: 288, format: 1, 2, 3...288 |
maxAvail |
Mandatory |
Integer |
Maximum availability loading for a period, in whole megawatts minimum: 0 |
bandAvail |
Mandatory |
Integer |
The availability for each 10 price bands. Required for energyPeriods, mnspPeriods, and fcasPeriods. Required properties: avail, type: array, minimum: 10 maximum: 10, format. For BDU for each direction (LOAD and GEN) required properties: avail, type: array, minimum: 10 maximum: 10, format: whole number (0 and positive values for each direction) |
enablementMin |
Mandatory |
Integer |
For all unit types and Reg FCAS for BDU where direction = GEN, value is minimum FCAS enablement limit this service can supply. integer minimum 0, format: whole numbers, value: megawatts. |
enablementMax |
Mandatory |
Integer |
For all unit types and Reg FCAS for BDU where direction = GEN, value is the maximum FCAS enablement limit this service can supply. Required for fcasPeriods, type: integer minimum 0, format: whole numbers, value: megawatts. |
lowBreakPoint |
Mandatory |
Integer |
For all unit types and Reg FCAS for BDU where direction = GEN, value is the FCAS low break point. Required for fcasPeriods, type: integer minimum 0, format: whole numbers, value: megawatts |
highBreakPoint |
Mandatory |
Integer |
For all unit types and Reg FCAS for BDU where direction = GEN, value is the maximum FCAS MW output this unit can provide (as per MaxAvail). Required for fcasPeriods, type: integer minimum 0, format: whole numbers, value: megawatts |
Direction Field Enumeration and Use Table
Submit Bids energybid and fcasBids supports a new conditional direction indicator. You must provide uppercase enumerated value for BDU Energy and Regulation FCAS service type, optional for remainder.
If these values are provided, AEMO validates these attribute value combinations as follows:
Unit Type |
Service Type |
Allowable Enumerated Value |
Provision in Submit Bid (JSON) |
Generator |
Energy |
GEN |
Optional |
Generator |
Contingency FCAS |
GEN |
Optional |
Generator |
Regulation FCAS |
GEN |
Optional |
Load |
Energy |
LOAD |
Optional |
Load |
Contingency FCAS |
LOAD |
Optional |
Load |
Regulation FCAS |
LOAD |
Optional |
BDU |
Energy |
GEN |
Mandatory |
|
Energy |
LOAD |
Mandatory |
BDU |
Contingency FCAS |
BIDIRECTIONAL |
Optional |
BDU |
Regulation FCAS |
GEN |
Mandatory |
|
Regulation FCAS |
LOAD |
Mandatory |
WDR |
Energy |
GEN |
Optional |
Normally On Load |
Energy |
LOAD |
Optional |
Market portal web bid and JSON file upload
Update the Energy & FCAS 5min Bids web interface to support BDU units.
- Energy & FCAS Bids screen:
- Allows participant to select BDU units, retrieve and display energy and FCAS bids.
- Allows participant to view the extended BDU Energy and FCAS attributes to support BDU single DUID.
- Displays the Energy and Regulation FCAS Bid bands (10 load and 10 generation) with the option to expand and collapse either load or generation.
- Allows participants to select Available chart option to view a graphical display of BDU unit data for energy bids and regulation FCAS bids, 20 price and availability bands including associated parameters.
- Adds support to Contingency FCAS to display positive and negative FCAS bids.
- Energy and FCAS screen displaying the availability chart:
- On the Enter bid screen:
- Allows participant to select BDU units, retrieve and display energy and FCAS bids.
- Allows participant to view the extended BDU Energy and FCAS attributes to support BDU single DUID.
- Displays the Energy and Regulation FCAS bands ((20 price and availability bands including associated parameters) with the option to expand and collapse either load or generation.
- Extends other existing features to support and display BDU-related information.
- On the Import and Upload Bid File See Relevant Rules or Procedures screens:
- Extends existing capabilities to allow participants to manually upload bid-related payloads (csv) for BDU JSON information.
- On the Export screen:
- Allows a participant to save the Bid data csv file to a participant’s local folder for BDU information.
Bidding submission formats
Extend the Bidding submission JSON format to allow energy and FCAS bids for a single BDU DUIDs.
Enhance Bid See Relevant Rules or Procedures format for BDU:
- Energy bids supports a new optional direction indicator (LOAD, GEN) allowing submission of separate energyBids object and energyPeriods arrays (10 price, availability, and associated parameters) for the Load side and Generation Energy Rules Terms side of the BDU (20 in total). For non-BDU, remove the entire attribute.
- Contingency FCAS offers unchanged (single FCAS enablement - 10 bands) with variation the four trapezium period parameters support provision of positive and negative numeric values (currently positive only).
- Regulation FCAS supports a new optional direction indicator (LOAD, GEN) allowing submission of separate fcasBids array and fcasPeriods arrays (10 price, availability and associated parameters) for the Load side and Generation side of the BDU (20 in total). For non-BDU, remove the entire attribute.
- Response The information returned by an API after a request is made. Responses are usually in JSON or XML format. formats remain unchanged - existing attributes support new error BDU responses.
Bidding enhancements for FTP
Extend the existing FTP service to allow participants to submit the extended JSON payload to support BDU single DUID Dispatchable Unit Identifier.
NEM Bidding validations
Error title |
Error message |
Detail |
Band Availability exceeds Max Load capacity |
Band Availability must be <= Registered Maximum Load Capacity {1} |
Your Bid is rejected because the BDU Energy Bid Direction is LOAD for the associated Energy Periods and the Band Availability (1 to 10) is greater than the Registered Maximum Load Capacity. The Band Availability must be less than or equal to the Registered Maximum Load Capacity for the DUID. Or the BDU Energy Bid MLF-adjusted Price Bands must monotonically increase from LOAD Band Availability (1 to 10) to GEN Band Availability (1 to 10). They must increase from lowest to highest. |
Fixed Load violation |
Fixed Load cannot be provided for GEN and LOAD DUID {0} |
Your Bid is rejected because the optional Fixed Load value for the Energy Periods is for both directions: LOAD and GEN. For a BDU, if you provide the value, it is only allowed for a LOAD or GEN direction at a time. |
Monotonically Increased Prices violation |
Prices must increase monotonically for DUID {0} |
Your Bid is rejected because your BDU Energy Bid for a Trading Day must include the Direction: LOAD or GEN. You must separate the Energy Bid and associated Energy Periods for the Load and Generation side of the BDU. Or the MLF-adjusted Price Bands do not monotonically increase for LOAD (1 to 10) and GEN Band Availability (1 to 10). They must increase from lowest to highest. |
FastStartProfile unit requirement violation |
Unit registered as Semi-Scheduled cannot have FaststartProfile in the offer for DUID {0} |
Your Bid is rejected because the Fast Start Profile associated with the Energy Bid has a value. A Fast Start Profile is not required for a Semi-Scheduled Generating Unit. |
Invalid Faststart details |
Unit registered as BDU cannot have FaststartProfile in the bid for DUID {0} |
Your Bid is rejected because the Fast Start Profile associated with the Energy Bid has a value. A Fast Start Profile is not required for a Bidirectional Unit. |
Minimum/Maximum Price Band Violation |
Prices bands must be with in Market Floor Price {0}, Market Price Cap {1}, for DUID {2} |
Your Bid is rejected because the Prices Bands must be within the Market Floor Price and Market Price Cap for the DUID |
Invalid Direction |
The Direction for DUID {1} is not matching the registration details in {0} the offer |
Your Bid is rejected because the conditional Direction value: GEN, LOAD, or BIDIRECTIONAL, associated with the Energy Bid, does not match the allowable combination for the DUID or Bid type, or both. |
Missing {0} Direction in the Offer |
Missing {0} Direction in the {1} offer for DUID {2} |
Your Bid is rejected because you did not enter a Direction value. You must enter a value for BDU Energy and Regulation FCAS Bids with one of the following values: GEN, LOAD, or BIDIRECTIONAL. A Direction value is optional for all other DUID types. |
Missing Offer |
BDU submission must have both LOAD and GEN offers for DUID {0} |
Your Bid is rejected because you did not enter Direction values for both sides. For a Bidirectional Unit (BDU), the Direction value associated with the Energy Bid or Energy Period determines if it is LOAD or GEN. For BDU Energy and Regulation FCAS bids, you must provide a value for both directions, and that value must be different for both sides. A Direction value is optional for all other DUID types and BDU contingency FCAS. |
Invalid unit disptach type |
Unit {0} is not registered as a BDU |
Your Bid is rejected because energy or FCAS bid parameters are only allowable for a BDU and the DUID is not registered as a BDU. |
Energy limit violation |
Unit {0} is not registered as a BDU and cannot provide Energy limit. |
Your Bid is rejected because you did not enter a value for the Energy Limit for a non-BDU DUID associated with the Energy Bid or Energy Period. The Energy Limit value is optional for BDU DUID Energy Bids. For more information, see Energy limit validation. |
Energy limit violation |
BDU {0} is violating Energy Limit criteria for direction {1}, in periodId {2} |
Your Bid is rejected because the BDU value violates the Energy Limit for the Direction in Period ID {2}. For more information, see Energy Limit in BDU bids |
Convexity violation |
BDU {0} is violating Convexity criteria in Load band avail[{1}] and Gen band avail[{2}], in periodId {3} |
Your Bid is rejected is because the BDU Energy Bid MLF-adjusted prices for effective Bid bands do not increase monotonically from LOAD bandAvail1 to bandAvail10 to GEN bandAvail1 to bandAvail10. |
Invalid DailyEnergyConstraint details |
Daily energy constraint must not be provided for BDUs in the bid for DUID {0} |
Your Bid is rejected because you have provided the DailyEnergyConstraint field for BDU. This field is only required for energyBids. |
Standard trapezium size violation |
Standard trapezium size violation in periodid {0}, for DUID {1} |
Your Bid is rejected because the following conditions are not met: |
Value is Positive |
{0} cannot be positive in periodId {1} |
Your Bid is rejected because the Direction value associated with the Energy Bid is LOAD and the FCAS Periods with: Enablement Min, Enablement Max, Low BreakPoint, or High BreakPoint have positive values. The values must be negative or 0. |
Value is Negative |
{0} cannot be negative in periodId {1} |
Your Bid is rejected because the Direction value associated with the Energy Bid is Gen and the Energy Bids with: Enablement Min, Enablement Max, LowBreakPoint, or HighBreakPoint has negative values. The values must be positive or 0. |
Invalid FCAS service |
{0} Duid cannot have invalid fcas service {1} |
Your Bid is rejected because the DUID is not registered to provide FCAS service. Please check the DUID's registration details. |
Sum of max avail exceeds max capacity |
Sum of max avail from GEN and LOAD must be <= unit {0} max capacity {1} |
Your Bid is rejected because the BDU Energy or FCAS Bid summed values with Max Availability for the LOAD and GEN Direction is greater than the DUID's Registered Maximum Capacity. Sum of Band Availabilities must be less than or equal to the Registered Maximum Capacity of the DUID for the direction. |
Non identical rebid values |
Rebid values not identical for Direction LOAD and GEN, unit {0} |
You BDU Energy or FCAS Bid is rejected because the 5 field values associated with rebidExplanation array for LOAD and GEN (direction) are not identical. |
BDU FCAS Regulation Band Availability violation |
Sum of Band Availabilities of GEN and LOAD must be >= Maximum Capacity {0} for the direction GEN and LOAD. |
Your Bid is rejected because the sum of the BDU Regulation FCAS Availabilities for Band Availability (1 to 10) for the FCAS Periods for both the LOAD and GEN Direction is greater than the Registered Maximum Capacity of the DUID. |
Net Trapezium Gap Violation |
Both GEN and LOAD trapeziums should not have any gaps in them i.e. GEN enablementMin=0 and LOAD enablementMax=0, for DUID {0} in periodid {1} |
Your Bid is rejected because there is a gap in the combined GEN and LOAD trapezium. When both sides have availability, the individual trapeziums should meet at 0 MW. |
Net Trapezium Upper Angle Violation |
Both GEN and LOAD trapeziums should have the same upper angles, instead of GEN upper angle {2} and LOAD upper angle {3}, for DUID {0} in periodid {1} |
Your Bid is rejected because the GEN and LOAD trapezium must have the same upper angle. |
Net Trapezium Lower Angle Violation |
Both GEN and LOAD trapeziums should have the same lower angles, instead of GEN lower angle {2} and LOAD lower angle {3}, for DUID {0} in periodid {1} |
Your Bid is rejected because the GEN and LOAD trapezium must have the same lower angle. |
Net Trapezium Upper Angle Less Than 90° Violation |
When upper angle {4} is less than 90°, bid high {3} and low {2} breakpoints on the generation trapezium must be zero, for DUID {0} in periodid {1} |
Your Bid is rejected because both Low Breakpoint and High Breakpoint for GEN must be 0 when upper angle is less than 90°. |
Net Trapezium Lower Angle Less Than 90° Violation |
When lower angle {4} is less than 90°, bid high {3} and low {2} breakpoints on the generation trapezium must be zero, for DUID {0} in periodid {1} |
Your Bid is rejected because both Low Breakpoint and High Breakpoint for LOAD must be 0 when lower angle is less than 90°. |
Reason missing for Ramprateup voilation |
Reason required for Ramp Rate lower than registered minimum ramp up rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid. |
Reason missing for Rampratedown voilation |
Reason required for Ramp Rate lower than registered minimum ramp down rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid. |
Reason missing for ramprateup violation |
Reason required for Ramp Rate lower than registered minimum ramp up rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid. |
Reason missing for rampratedown violation |
Reason required for Ramp Rate lower than registered minimum ramp down rate of {0} |
Your Bid is rejected because the value provided is less than the registered minimum value. The validation message provides additional information comparing the minimum ramp rate and the value in the Bid. |
Band Availability violation |
Sum of Band Availabilities must be >= Maximum Capacity {0} for the Direction {1} |
Your Bid is rejected because the sum of Energy FCAS Bid Availabilities (1 to 10) is greater than the Registered Generation or Load Capacity of the DUID. This validation is applied to all DUIDs, including BDUs and is associated with the LOAD or GEN Direction of the Bid. |
Rebid Price violation |
Band prices cannot be changed for a rebid Direction {0}. |
Your Bid is rejected because the band prices must remain same for a rebid. |
NEM Bidding API updates
Extend support to the NEM Bidding APIs for BDU:
- Get Bid – to additionally return Energy BDU and FCAS information.
- Get Bids - to additionally return one or more Energy and FCAS BDU information.
- Get Submission A Bid/Offer submission can have: 1. Multiple Trading Days 2. Multiple DUIDs/LinkIDs 3. All Service Types in the same Submission – to additionally return Energy BDU and FCAS information.
- Get Submissions - to additionally return one or more Energy and FCAS BDU bid information.
- Response error messaging remains same.
For more information on the NEM Dispatch and Bidding API changes, see NEM Dispatch Bidding Open API Specification Reference.
Dispatch and pre-dispatch updates
The TOTALCLEARED, INITIALMW and ACTUALMW fields in the Dispatch and Predispatch tables now support negative and positive values.
Market reports, notices and MMS Data Model
Enhance the existing Market Reports and Notices to support the introduction of the new IRP Integrated Resource Provider. Any person who owns, controls or operates an integrated resource system connected to a transmission or distribution network must register as an Integrated Resource Provider participant category and BDU generally described as:
1. Energy and FCAS Bid related reports to accommodate the new BDU related attributes i.e., 20 price and availability bands including associated parameters.
2. Variable Dispatch and Pre-dispatch See Relevant Rules or Procedures reports inclusion of BDU Energy Targets negative and positive), new summations/calculations at regional and DUID level.
3. MT PASA Medium Term Projected Assessment of System Adequacy. A 24-month supply demand forecast, published weekly, with daily resolution. DUID Availability report supports provision of IRP MT PASA Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules offer(s).
BDU MLF calculations
Currently, batteries have 2 connection points, one for generation and one for consumption, each with their own primary TLF stored. With the IESS rule change, following the transition of the battery to the BDU configuration, there is a single connection point for the battery and it is configured with dual TLFs.
As per the current Settlements See Relevant Rules or Procedures functionality for dual TLFs loaded against TNIs, the battery connection point primary TLF is used for consumption and the secondary TLF Transmission Loss Factor. A calculation that ensures customers aren’t charged for the electricity that is lost in transit over poles and wires.(if populated) is used for generation.
In cases where the BDU does not have dual MLFs configured, only the primary is populated and it is the TLF applied for both the consumption and generation of the battery.
BDU MT PASA enhancements
Extend support to allow existing submission mechanisms (FTP, API and Market Portal) to include IRP participants.
Extend support in NEMReports and Data Model The definition of the interface to participants of data published by AEMO for gas or electricity. A database conforming to the Data Model can contain a local copy of all current participant-specific data recorded in the main database. The Data Model includes database tables, indexes, and primary keys. to process offer data to support IRP and associated unit type offers.
BDU PASA enhancements
PASA calculations (processing) and outputs include BDU generation PASA related data (BDU Load PASA availability Energy Rules Terms excluded) No change to formats
BDU external interface enhancements
View market on the Markets portal
Rebuild the following interfaces on the Markets Portal > EMMS Energy Market Management System (formerly MMS); software, hardware, network and related processes. > View Market:
- View Market Summary
- View Dispatch
- View Predispatch
NEM data dashboard
Extend support to the NEM Data Dashboard to include IRP and BDU related information:
- Include the generation and demand calculation in Dispatch Overview.
- Include BDU-related information in calculations for Price Energy Rules Terms and Demand The amount of power consumed at any time.
- Fuel Mix displays battery info (as well as other fuel mixes). This must include BDU in existing battery MW Megawatt and MWh displays and calculations inclusive of time chart MWh view (24 and 48 hr, 3- and 12-months views aggregated).
- Renewable Penetration displays battery info (as well as other fuel mixes). This must include BDU into existing battery MW but exclude the load side of BDU. This update is applied to Renewable Penetration as well.
- Average Price price calculations including historical year/month views to include BDU.
- 7-day Outlook forecast capacity and demand at daily Energy Rules Terms peak for NEM Regions (figures in MW) to include BDU based on data ingested from csv payload Payload from EMMS NEMReports.
EMMS Data Model
The new version of the EMMS Data Model includes new and updated tables to capture all the changes listed in the above sections. The EMMS Technical Specification - Data Model v5.3 – April 2024 captures list of table changes.
The important changes to the Bidding tables in the Data Model release 5.3 are as follows:
- The bidding tables maintain a 10-band model through the inclusion of a new DIRECTION field as a primary key of the main bidding tables. (BIDDAYOFFER, BIDOFFERPERIOD, BIDDAYOFFER_D, BIDPEROFFER_D)
- The transition approach for these tables includes a component to back populate the new field to enable Energy Rules Terms the amendment of the primary key.
- If participants subscribe to the NEXT DAY set of bidding data, you MUST upgrade the MMS Data Model to receive the new bidirectional bids.