How to use BUT

For details about the fields requiring updating and who can update them see, MSATS Technical Specifications.

Data history

For a blind update, the CATS History Model See Technical Guide to MSATS does not change (the creation and maintenance dates remain unchanged).

For details about other tools for updating Standing Data, see MSATS data update tools.

CATS notifications

There are no CATS Customer Administration and Transfer Solution. A set of procedures, principles and obligations made under the National Electricity Rules as part of Market Settlement and Transfer Solutions (MSATS), and applicable to NMI (National Metering Identifier) small and large classifications. Notifications sent for Standing Data updates using BUT Blind Update Tool.

BUT interfaces

Participants can use the following interfaces to submit their csv Comma Separated Values. A file format for data using commas as delimiters. 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 retrieve the processing results:

MSATS Web Portal (this guide): Upload, track status, and retrieve submission results.

The interfaces are interchangeable, for example you can upload a Payload to the MSATS Web Portal and retrieve the results using AEMO’s API Gateway.

AEMO’s API Gateway: Submit, track status, and retrieve submission results via API calls. For details, see Guide to Blind Update Tool API.

Submission

BUT submission rules

The BUT submission:

For help with the CSV format, see Guide to AEMO CSV Data Format Standard.

Must adhere to AEMO Australian Energy Market Operator’s CSV Data Format Standard.
The payload format must be CSV (comma delimited) (*.csv).
AEMO rejects files saved as CSV UTF-8 (comma delimited) (*.csv).
Can contain mixed record types in the csv Payload I and D records.
Each record in the Payload must start with one of the following 3 characters:
C = comment (metadata)
I = information
D = data
Must have a C record for its first and last row.
Can have each csv row containing a single new value for a single column for a specific MSATS Market Settlement and Transfer Solutions. The procedures published by AEMO under clause 7.2.8 of the National Electricity Rules, which include those governing the recording of financial responsibility for energy flows at a connection point, the transfer of that responsibility between market participants, and the recording of energy flows at a connection point. record. If you are updating multiple columns for a single MSATS record in the same submission payload, there is one csv row per column.
Can have any mixture of tables and columns.
Must be unique for the target:
Table
Row (using Business keys for the row)
Column

BUT submission payload and subtypes

Type	C row	Payload type	Subtype	CATS table
Participant submission	BLIND_UPDATE_SUBMISSION	BUS	NMI_DATA	NMI_DATA
	METER_REGISTER		METER_REGISTER
	REGISTER_IDENTIFIER		REGISTER_IDENTIFIER	REGISTER_IDENTIFIER
AEMO acknowledgement	n/a	BUA (Blind Update Acknowledgement)	n/a	n/a
AEMO acknowledgement	BLIND_UPDATE_TOOL	BUT	n/a	n/a
AEMO response	BLIND_UPDATE_RESPONSE	BUR	NMI See Relevant Rules or Procedures_DATA	NMI DATA
	BLIND_UPDATE_RESPONSE	BUR	METER_REGISTER	METER_REGISTER
	BLIND_UPDATE_RESPONSE	BUR	REGISTER_IDENTIFIER	REGISTER_IDENTIFIER

Business keys

The relevant technical specification details the business-key combinations for each release.

A BUT Submission A Bid/Offer submission can have: 1. Multiple Trading Days 2. Multiple DUIDs/LinkIDs 3. All Service Types in the same Submission D field can only contain unique record type business-key combinations. For each record type, the business keys are defined as a combination of the D fields and the updated column.

Submission row limit

The limit for a single Payload is 100,000 rows (to be confirmed after AEMO testing).

Response time

BUT submission to response times shall meet the following technology response time targets (to be confirmed after AEMO testing):

Connection time out 10 seconds.
Response The information returned by an API after a request is made. Responses are usually in JSON or XML format. time out including connection time out 30 seconds.

Submission process

Participant Roles having a current relationship with the NMI use the following self-service process to upload and view Blind Update Submissions. There is no coordination required with AEMO.

The high-level submission process is:

Who	What
Participant	Create a csv Payload with their Blind Update Submissions following AEMO’s CSV Data Format Standard
Participant	Send the csv Payload to AEMO using one of the following interfaces: MSATS Web Portal API e-Hub Gateway
AEMO	Receives and validates the submission for security and syntax (typically not business validations at this stage)
AEMO	Acknowledges the submission with Accept or Reject. Accept or Reject applies to the entire payload A rejection on submission, results in the entire payload being rejected
AEMO	If AEMO accepts the submission, it applies business validations and processes the updates at a later time
Participant	Track their submission status using the API or MSATS Web Portal interfaces
Participant	Download the processing results when they are ready using the API or MSATS Web Portal interfaces. The processing results are a mixture of payload successes and failures. The content is a similar csv format to the Submission with some extra columns

Seeing updated BUT fields

A Blind Update Submission does not trigger CATS CR Notifications.

BUT submitting party

For the party submitting the BUT Payload, you can download the Submission response with the status of the update using the API Application Programming Interface; a set of clearly defined methods of communication between various software components. or MSATS Web Portal interfaces.

Other parties

For other parties having a relationship with the NMI, you can see the modified fields in a C1 - Data Replication Resynchronisation or MSATS Snapshot report, retrieved using API, file, or web interface.

The reports provide no specific indication the Blind Update Tool Allows participants to submit a csv formatted payload containing data for new CATS Standing Data fields requiring a value A limited subset of CATS CR validations is applied to a BUT Submission The History Model is not updated so not suitable for Settlement or Compliance Standing Data altered the data or when.

The modified C1 may have records where both the Create and Update timestamps fall outside the C1 reporting period.

BUT submission status

For each step in the process, your submission has the following statuses:

Who	Action	From status	To status	Description	Response
Participant	Submit	n/a	ERROR	Security & syntax validation fail Applies to the entire payload, not individual rows The entire submission is rejected No further processing	Acknowledgement Payload is not stored
Participant	Submit	n/a	PENDING	Security & syntax validation pass Applies to the entire payload, not individual rows Initial accepted status	Payload stored
AEMO	Process	PENDING	PROCESSED	All rows processed where each payload row is updated with a success or fail reason and a timestamp Result awaiting participant download	Row level responses
Participant	Retrieve result	PROCESSED	DOWNLOADED	BUT end-to-end process complete Downloads can be repeated Only the first download moves status from PROCESSED to DOWNLOADED	Row level responses