MT PASA Offer Payload
About the offer payload
Scheduled Generators See Relevant Rules or Procedures and Market Customers create MT PASA Medium Term Projected Assessment of System Adequacy. A 24-month supply demand forecast, published weekly, with daily resolution. Offer Energy, Dispatch, FCAS Offer, MNSP, MTPASA Bid or Offer submission Payloads as text files in a comma-separated variable (csv Comma Separated Values. A file format for data using commas as delimiters.) layout. The Offer Payload Bid or Offer submitted by a participant allows for multiple Scheduled Generating Units See Relevant Rules or Procedures. Each data row is for one week, notifying the weekly energy limit and the capacity for each day in the week.
MT PASA offer payload rules
To create a valid Offer 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., it must:
- Follow AEMO's csv file format, starting with a comment row, then the fixed format information row, then the data rows, then the end of offer comment row.
- Use delimiting commas for empty optional fields in each row.
- Use UPPERCASE text.
- Terminate each row with an end-of-line (CRLF), including the last row.
- Have a data row for each week, with the Weekly Energy Limit Weekly energy constraints submitted by participants, as described in clause 3.7.2(d)(2) of the National Electricity Rules, the NER glossary, and the MT PASA process description. (MWh), 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 (DUID Dispatchable Unit Identifier capacity), Unit State A Scheduled Generating Unit’s availability or unavailability and the reason for it, and Recall Times.
- Have the first Offer date as Sunday week or future Sunday.
- Have successive data rows for the same Generating Unit A Scheduled, Semi-Scheduled, or Non-Scheduled Generating Unit (DUID) at weekly intervals for the period of the projection (usually two years). Other relevant units follow.
- Data lines have no spaces, including before numbers and for empty fields.
- The Participant ID Registered participant identifier; A company can have more than one Participant ID. matches the registered DUID in AEMO Australian Energy Market Operator's systems.
A valid Offer Payload can have many Scheduled Generating Units (DUIDs). If your submission has multiple DUIDs in a single Payload, and one has an error, AEMO rejects the whole Payloads
Offer payload name
Payload name size
An acceptable Offer Payload name:
- Is 40 characters or less
- Must be unique (for traceability)
- Only used once.
Payload name example
ppp_MT PASA Projected Assessment of System Adequacy. except executable files e.g., .DLLs, .LIBs and .EXEs with the user mentioned. See National Energy Rules_20040314_20040308162815.csv
Payload format
For example, considering the Payload name example, the components of the name are:
|
Component |
Participant ID |
Offer type |
Offer start date |
Date and time of payload creation |
Payload extension |
|---|---|---|---|---|---|
|
Description |
Identifies the submitting Participant ID |
Identifies the Payload as an MT PASA Offer |
The date for the first effective Offer in the Payload. In the format YYYYMMDD 4 digit year, 2 digit month, 2 digit day |
The date and time of Payload creation. In the form YYYYMMDDhhmmss 4 digit year, 2 digit month, 2 digit day, 2 digit hour in 24-hour count, 2 digit minute and 2 digit second |
file extension |
|
Example |
ppp_ |
MT PASA_ |
20040314_ |
20040308162815 |
csv |
Processing order
If more than one Payload is present in a participant’s \Export\PASA\ directory, the Offer processor handles files in ascending order determined by file name's modified date.
Offer payload
Payload submission size
A MT PASA Offer payload must not exceed 10MB in size, whether compressed or uncompressed. If the MT PASA csv file supplied is large and has a significant number of data entry errors, the time taken to write out all the individual error conditions may exceed the allowable file processing time, resulting in the return error:
Exception: Client request of type [Aemo.Interface.MTPASAOffers.SubmitMTPASAOffersRequest] from client [MTPASAOfferFileHandler] unsuccessful
AEMO recommends the following:
-
Break up the file and test with smaller files until all the data entry conditions can be met successfully.
-
Submit a file size of approximately 20kb to ensure processing. It also provides for easier review and resolution to future issues that may arise in production.
MT PASA offer example
C,PROD,MTPASA,PARTID,NEMMCO,2020/08/30,17:30:00,GENERATION CONTROL TEAM LEADER,
I,MTPASA,BID,1,DATE,DUID,ENERGYLIMIT,CAPACITY1,CAPACITY2,CAPACITY3,CAPACITY4,CAPACITY5,CAPACITY6,CAPACITY7,UNITSTATE1,UNITSTATE2,UNITSTATE3,UNITSTATE4,UNITSTATE5,UNITSTATE6,UNITSTATE7,RECALLTIME1,RECALLTIME2,RECALLTIME3,RECALLTIME4,RECALLTIME5,RECALLTIME6,RECALLTIME7,
D,MTPASA,BID,1,2022/03/14,BASTYAN,,0,0,0,0,0,0,0,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,90,90,90,90,90,90,90,
D,MTPASA,BID,1,2022/03/14,CETHANA,,360,360,360,360,360,360,360,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,,,,,,,,
C,END OF REPORT,5,
Comment row
The first row starts with a C, indicating it is a comment row. Some fields in the first comment row are subject to validation rules and others are optional. Each field is followed by a comma:
|
Field |
Data type |
Description |
Example |
Status |
|---|---|---|---|---|
|
C (comment) Use delimiting commas for optional fields |
String |
Indicates a comment row |
C |
Required |
|
System |
String |
AEMO environment |
PROD PREPROD |
Optional |
|
Application |
String |
System application |
MT PASA |
Required |
|
From Participant ID |
String |
Initiating Participant ID |
PARTID |
Required |
|
To Participant ID |
String |
Receiving Participant ID |
NEMMCO |
Required |
|
Creation date |
Date |
DATE YYYY/MM/DD |
2020/08/30 |
Optional |
|
Creation time |
Time |
TIME HH:MM:SS |
17:30:00 |
Optional |
|
Authorising person |
String |
Authorising person's name |
GENERATION CONTROL TEAM LEADER |
Optional |
|
Version |
String |
Version number 3 characters |
1 |
Optional |
Comment row example
C,PROD,MTPASA,PARTID,NEMMCO,2020/08/30,17:30:00,GENERATION CONTROL TEAM LEADER,
Delimiting commas for empty optional fields example
C,,MTPASA,PARTID,NEMMCO,,,,
Information row
The information row is the column headings, for the data. The row is ignored for validation purposes, but is useful for human readers.
|
Field |
Data type |
Example |
Status |
|---|---|---|---|
|
I (information) Use delimiting commas for optional fields Ignored for validation Useful for human readers |
String |
I |
Required |
|
Report type heading |
String |
MTPASA |
Optional |
|
Report subtype heading |
String |
BID |
Optional |
|
Report version heading |
Number |
1 |
Optional |
|
Offer date heading |
String |
DATE |
Optional |
|
Generating Unit ID (DUID) heading |
String |
DUID |
Optional |
|
MWh limit heading |
String |
ENERGYLIMIT |
Optional |
|
MT PASA Availability values (1-7) heading |
String |
CAPACITY1 |
Optional |
|
Unit state values (1-7) heading |
String |
UNITSTATE1 |
Conditional on participant category |
|
Recall time values (1-7) heading |
String |
RECALLTIME1 |
Conditional on unit state |
Information row example
I,MTPASA,BID,1,DATE,DUID,ENERGYLIMIT,CAPACITY1,CAPACITY2,CAPACITY3,CAPACITY4,CAPACITY5,CAPACITY6,CAPACITY7,UNITSTATE1,UNITSTATE2,UNITSTATE3,UNITSTATE4,UNITSTATE5,UNITSTATE6,UNITSTATE7,RECALLTIME1,RECALLTIME2,RECALLTIME3,RECALLTIME4,RECALLTIME5,RECALLTIME6,RECALLTIME7,S
Data row
Each data row is one week from Sunday to Saturday with the Energy The unit must be a generator for the service type: ‘energy’. Loads cannot bid for mandatory restrictions capacity. Limit in MWh (ENERGYLIMIT field), MT PASA Availability (DUID capacity) values (1-7), Unit State values (1-7), and Recall Time The time the Participant ID expects the Scheduled Generating Unit to take to return to full PASA Availability under normal conditions values(1-7). A comma follows each field, including the last.
|
Field |
Data type |
Example |
Status |
|---|---|---|---|
|
D (data row) |
String |
D |
Required |
|
Report type |
String |
MTPASA |
Required |
|
Report subtype |
String |
BID |
Required |
|
Report version |
Number |
1 |
Required |
|
Offer date (future Sunday) |
Date |
2022/03/14 |
Required |
|
Generating Unit ID (DUID) |
String |
DUID1 |
Required |
|
Weekly Energy Limit (MWh) Sum of daily PASA Availability * 24 or less 0 = no availability, the unit has an outage Null or blank = unlimited Energy |
Number |
1000 |
Optional |
|
Daily capacity of the Generating Unit (DUID) (Sunday–Saturday) in increasing range from zero to the registered maximum capacity |
Number |
80 |
Required |
|
One of the Unit State values if the Generating Unit is unavailable (Sunday–Saturday) |
Enumeration Varchar(20) |
MOTHBALLED |
Required |
|
The corresponding Recall Time (days) for the Unit State to bring it back into service (Sunday–Saturday) |
Number |
365 |
Required |
Data row example
D,MTPASA,BID,1,2022/03/14,BASTYAN,,0,0,0,0,0,0,0,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,Mothballed,90,90,90,90,90,90,90,
D,MTPASA,BID,1,2022/03/14,CETHANA,,360,360,360,360,360,360,360,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,NoDeratings,,,,,,,,
Count of records comment row
The end of the Offer Payload is another C comment row:
- The string C,END OF REPORT,
- The number of rows in the Payload (including this row) with no space before and followed by a comma and row termination
Count of records comment row example
C,END OF REPORT,5,