Request for data transfer
When 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. receives a Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS., it checks the existing data, ensuring it can proceed through the Validation A process to test the veracity and integrity of metering data. process. If some data required to complete the 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. is missing from the NMI Master Record The NMI master record with an end date set to the year 9999., MSATS send a Request for Data Transfer Future Transfer Submission (RDAT) to the appropriate participants according to the Change Request Field Validation Rules As described in the CATS Procedures, they specify, for each Change Reason Code, the fields in MSATS populated at the creation of a transaction or at other times in the life cycle of a transaction. (see Change request field validation rules).
The nominated parties provide the requested data in a new Change Request. For more details, see Receiving and responding to an RDAT.