B2M transition process

About

Outbox states and transitions

Empty specifically means there are no MSATS output .ZIP files (excludes reference to acknowledgement files and B2B files).

Environments

The transition occurs in AEMO Australian Energy Market Operator’s pre-production systems prior to production, allowing for familiarisation and testing.

AEMO transition

When AEMO makes the transition to a new schema, all the produced files conform to the new schema.

The process placing the output files into the file share for each participant checks which version of the aseXML schema Specification to describe the structure of an aseXML message. the participant requires (Latest The participant is set up to receive both current and next projected future version of aseXML-compliant files., Current The participant can receive files compliant to the current aseXML version. or Superseded The participant can receive files compliant to the The participant can receive files compliant to the superseded aseXML version, and needs to change over their receiving system before the next aseXML version release.) and delivers files and acknowledgements accordingly.

If the participant needs files conforming to the Superseded schema, the process has the additional step of transforming the files from the Current schema to the Superseded schema before placing them on the Participant Server.

If the participant needs files conforming to the Current or Latest schema, no transformation is needed. Acknowledgements are directly generated to match the participant’s chosen version of the aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. schema.

When AEMO transforms files, the process adds a comment (or comments) to the file for AEMO use so we can handle all versions of aseXML. Normal aseXML processing ignores comments.

Participant transition

Participants can transition at a time independent of AEMO and independently of one another. The schema version for the files and acknowledgements you receive is dependent on your schema status: Latest, Current or Superseded.

So each participant can manage their own schema transition, they stop AEMO’s creation of files so their system can process all files in 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., then restart AEMO’s file creation process after their receiving system is transitioned. This interaction is browser-based so it is independent of the file transfer system.

AEMO’s acknowledgement process is not stopped when the 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. output files are stopped. For participants to avoid having a mixture of superseded and current acknowledgement files (for example, both r36 and r25), they stop sending files to AEMO and delete the already-acknowledged .ZIP files in the inbox before stopping MSATS from producing files.