MT PASA Offers
About
Scheduled Generators See Relevant Rules or Procedures, Market Participants, Integrated Service Providers, and Market Network Service Providers provide Medium Term PASA Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules Inputs in accordance with the Spot Market See National Electricity Rules Operations Timetable.
For more details, in the NER National Electricity Rules. The rules made under the National Electricity Law (NEL). They govern the day-to-day operations of the National Electricity Market (NEM) and provide the framework for network regulation., see Administration of PASA 3.7.1 and Medium term PASA 3.7.2.
Goal
Implement new data fields to standardise the collection and reporting of PASA Availability PASA Availability For a scheduled generating unit, scheduled bidirectional unit, scheduled load or scheduled network service in a given period, its available physical plant capability (taking ambient weather conditions into account) and any additional physical plant capability that can be made available during that period within a given recall period in accordance with the reliability standard implementation guidelines:
-
Unit A Scheduled, Semi-Scheduled, or Non-Scheduled Generating Unit States: Distinguish between an economic outage and a physical outage.
-
Recall times: The time the participant expects the DUID Dispatchable Unit Identifier to return to full availability under normal conditions.
For more details, see NEM Reliability Forecasting Guidelines and Methodology Consultation.
High-level changes
Function |
Description |
Change |
---|---|---|
API |
Submit and retrieve MT PASA Offers using a JSON schema |
New |
Bid format |
New MT PASA bid format structure |
Modified |
Data Model |
Data Model v5.2 Changes to:
For details, see EMMS Technical Specification - Data Model – May 2023 |
Modified |
FTP |
Submit MT PASA Offer CSV Payload over FTP to the Participant File Server |
Modified |
Markets Portal |
Submit MT PASA Offers CSV Payload and view existing offers in the Markets Portal MT PASA Offer interface |
Modified |
NEMweb data |
MT PASA DUID availability report Public next-day report |
Modified |
Validation |
New and modified validations |
Modified |
Submission interfaces
Interface |
Description |
---|---|
API |
Submit MT PASA Offers to the API e-Hub Gateway using a JSON schema. For help, see MT PASA Offer API Reference |
FTP |
Submit MT PASA Offer CSV Payload over FTP to the Participant File Server. For help, see Offer submission |
Markets Portal |
Submit MT PASA Offers CSV Payload and view existing offers in the Markets Portal MT PASA Offer interface. For help, see Markets portal > MT PASA offers |
Participant categories, unit states, and recall times
Unit states are from the IEEE 762-2006 standard. DUID connection types:
-
Bi-directional Unit (BDU)
-
Scheduled Generation Energy Rules Terms Unit (SGU Scheduled Generating Unit. A generating unit with a nameplate rating of 30MW or greater. Note that a group of generating units with a combined nameplate rating of 30MW or greater is also classified as a Scheduled Generating Unit.)
-
Scheduled Network Service (SNS)
AEMO Australian Energy Market Operator has introduced Mandatory if Available Recall Times because it may not be possible to bring a unit back once planned maintenance begins. This means they are only mandatory where recall information applies. NULL submissions are valid if recall is not possible.
See Participant Categories, Units, and Recall Times for more information.
Example of how unit states and recall times work
The following example demonstrates how unit states work in practice. The table depicts an MT PASA Medium Term Projected Assessment of System Adequacy. A 24-month supply demand forecast, published weekly, with daily resolution. submission for a combined cycle gas turbine with a 110 MW Megawatt maximum Capacity PASA Availability, as described in clause 3.7.2(d)(1) of the National Electricity Rules and the NER glossary. and a 100 MW dependable Capacity in summer, considering seasonal deratings. Due to fuel supply and operation limitations, the Generating Unit (DUID) is subject to weekly Energy The unit must be a generator for the service type: ‘energy’. Loads cannot bid for mandatory restrictions capacity. limits approximately equal to a 20% average Capacity factor.
Trading day |
Event |
Weekly |
Availability |
Unit state |
Recall time |
---|---|---|---|---|---|
31/12/2023 |
Plant fully available considering summer derating |
3,408 |
100 |
No Derating |
null |
01/01/2024 |
100 |
No Derating |
null |
||
02/01/2024 |
100 |
No Derating |
null |
||
03/01/2024 |
Planned boiler maintenance Plant partially available as an open cycle gas turbine with a two-day Recall Time to full availability |
70 |
Basic Planned Derating |
2 |
|
04/01/2024 |
70 |
Basic Planned Derating |
2 |
||
05/01/2024 |
70 |
Basic Planned Derating |
2 |
||
06/01/2024 |
Plant fully available considering summer derating |
100 |
No Derating |
null |
|
07/01/2024 |
960 |
100 |
No Derating |
null |
|
08/01/2024 |
Planned major Plant upgrade No Recall Time required due to complex physical works |
0 |
Basic Planned Outage |
null |
|
09/01/2024 |
0 |
Basic Planned Outage |
null |
||
10/01/2024 |
|
0 |
Inactive Reserve |
2 |
|
11/01/2024 |
|
0 |
Inactive Reserve |
2 |
|
12/01/2024 |
|
0 |
Inactive Reserve |
2 |
|
13/01/2024 |
|
100 |
No Derating |
null |
Offer submission rules
-
The first date must be a current or future Sunday.
-
One Offer Payload Bid or Offer submitted by a participant (csv Comma Separated Values. A file format for data using commas as delimiters. or JSON JavaScript Object Notification) can have many Scheduled Generating Units See Relevant Rules or Procedures (DUIDs).
-
Each data line is for one week, notifying the Weekly Energy Rules Terms Energy Limit and capacity for each day in the week.
-
The entire Offer Energy, Dispatch, FCAS Offer, MNSP, MTPASA Bid or Offer submission submission must pass validation, or it is rejected.
-
If your submission has multiple DUIDs in a single Payload The content in the csv file. For example: For APIs, it is the data sent by a POST request that sits after the API header. For MSATS transactions, it is the data wrapped in the standard aseXML wrapper. For NEM reports it is the csv payload compressed in a zip file., and one has an error, AEMO rejects the whole Payload.
-
Successive data rows are for the same Generating Unit (DUID) at weekly intervals for the period of the projection (usually two years).
-
Interfaces are interchangeable, you can submit to any of the submission interfaces.
User rights access
See MT PASA Web Offers for more information.
MT PASA offer API
See the Draft MT PASA Offer API Reference for more information.
Offer csv payload format
The csv payload Payload format is used for submission by:
-
FTP File transfer protocol to the Participant File Server The publishing point from AEMO systems to participant systems. Each participant is allocated an account and access to private and public areas. Participants are responsible for interfacing with the participant file server.
-
Web interface in the Markets Portal Web applications for registered participants only. Requires access to MarketNet..
Csv payload example
The previous version of the document showed an incorrect example of a csv payload.
See MT PASA Offer Payload for an example of a csv payload.
Csv payload fields
For help with the AEMO csv payload format, see CSV Data Format Standard.
See MT PASA Offer Payload for a description of all csv payload fields.
Offer submission
Submit the Offer csv Payload to the Participant File Server > Participant ID > Export > PASA > folder.
Offer acknowledgement
See MT PASA Acknowledgements for more information.
Markets portal > MT PASA offers
The MT PASA Offer interface in the Markets Portal is upgraded to include the new fields and comply with contemporary AEMO style and branding.
Link to draft Guide to MT PASA Web Offers
Validation
Link to MT PASA Offer Validation.
Data model v5.2
MT PASA data model structure changes
Only the Data Model structure is released for Data Model v5.2. MT PASA NEM reports and data are available on the rule effective date: 9 October 1023
High-level MT PASA Data Model v5.2 changes
-
Package: BIDS > Table: MTPASA_OFFERDATA > File ID: MTPASA_OFFERFILETRK
-
Package: MTPASA > Table: MTPASA_DUIDAVAILABILITY > File ID: MTPASADUIDAVAILABILITY
For details, see EMMS Technical Specification - Data Model – May 2023.
Subscription and legacy files
There are no auto-subscriptions for the MT PASA 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. release as all tables and files are existing.
Subscribed participants are moved to the Legacy version of changed files and continue to receive the same data until they upgrade to MMS Data Model v5.2. To receive the new data you must subscribe manually to the following files:
-
MTPASA_OFFERFILETRK
-
MTPASA_SOLUTION
For help, see Unsubscribe from files.
NEMweb reports
MT PASA DUID availability report
Purpose
Contains the region Energy Rules Terms-aggregate offered MTPASA Availability for all registered Scheduled Generating Units and the latest MTPASA Offer submission date and time for the region and day.
For details, see PASA Outputs.
Visibility
Public (next day)
Report changes/details
New fields for Scheduled Generating Units’ MT PASA Input status and recall times. For details, see MT PASA data model v5.2 changes.
Report format
Comma-separated values (csv).
Report trigger
The report is updated at 0900, 1200, 1500, and 1800 hours Australian Eastern Standard Time (AEST Australian Eastern Standard Time (market time)) each day Energy Rules Terms(excluding Sunday).
Report delivery
Manual retrieval
http://www.nemweb.com.au/REPORTS/CURRENT/MTPASA_DUIDAvailability/
Data subscription
Subscribe to the report in the Markets Portal > Data Subscription interface to have the report delivered your Participant ID Registered participant identifier; A company can have more than one Participant ID. folder on the Participant File Server.
For help, see Data Subscription.
Participant file server
Retrieve the report manually from your Participant ID folder on the Participant File Server.
PDR batcher
You can automate the delivery of reports to your local folder by setting up a PDR Batcher An application providing an interface for batch transactions, called MSATS Participant Batcher.. For help, see Participant Data Replication Batcher.
Data interchange
You can automate the delivery of reports and tables to your local database by setting up a Data Interchange A set of cooperating applications used to replicate data between AEMO's energy market systems and a participant's DBMS conforming to the MMS Data Model. instance. For help, see About Data Interchange.