Transaction limits and stop files

Transaction limits

Transaction See Relevant Rules or Procedures limits allow participants to manage the submission and receipt of 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. files to prevent the application of Stop Files.

Stopfiles

When the number of unacknowledged outbound files in your Participant Outbox exceeds the upper or lower limit, a Stop File is imposed on your Participant Outbox Transactions. Once imposed no more processing on inbound or outbound Transactions occurs until the file numbers fall below the Lower Limit. Where a participant belongs to a group, the limits apply to the group not to the individual.

If a stop file is imposed MSATS stops processing files for the Transaction:

  • Change Request or Change Request Notification. Other Transactions are processed.

  • NSRD Notification or Response reasons. MSATS does not process any CATS Change Request transactions with Change Reason Codes: 5070 or 5071. Other Transactions are processed.

  • Outbox files. MSATS only processes Meter Data Notification Transactions.

  • Report requests. MSATS does not process any Report Request Transactions. Other Transactions are processed.

Viewing limits

All Upper Limits are reset at midnight.

Where a participant belongs to a group, the limits apply to the group not to the individual Participant ID Registered participant identifier; A company can have more than one Participant ID..

You can view your limits (upper and lower) for the accumulation of Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS. Response The information returned by an API after a request is made. Responses are usually in JSON or XML format. and notification messages to monitor how many Transactions are currently queued:

  • In the MSATS Web Portal > Reports and Alerts > Queue Monitoring.

  • Using the MSATS Limits API. For help, see Guide to NEM Retail B2M APIs.

Increasing limits

Participants can temporarily increase their Change Request The way information is returned from an API. In a request, the client provides a resource URL with the proper authorization to an API server. The API returns a response with the information requested. and Change Request Notifications Upper Limits to the maximum allowed in the MSATS Web Portal > Reports and Alerts > Queue Monitoring.

To increase the allowed Upper Limit for queues, in the relevant queue interface, click Increaseto increase the Upper Limit to the maximum allowed. Calculated by multiplying the Lower Limit by the maximum increase factor.

If you cannot see the Increase option, the functionality is unavailable to you, speak with your Participant Administrator Creates and maintains access to AEMO systems for their Participant ID users..