MSATS Reports

C1 Data Replication Resynchronisation Report

Purpose

A synchronisation report designed for participants to replicate data from a single 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. table if they did not receive all notifications or lost access to MSATS for a short time. It assists participant to keep local copies of CATS Standing Data The data held in the following database tables: • CATS_NMI_Data_Stream • CATS_NMI_Data • CATS_Meter_Register • CATS_NMI_Participants_Relationships • CATS_Register_Identifier NMI Standing Data is a sub-set of the CATS Standing Data. in sync with MSATS.

Change

AEMO Australian Energy Market Operator is making the following changes to the C1 report, so it identifies records altered by 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:

• The nominated field on the current Active record is updated.
• The creation and maintenance dates remain unchanged.

 

Identifying BUT updated records

To find records updated by the Blind Update Tool, AEMO uses a lookup for the C1 against the BUT Blind Update Tool log table.

The BUT log table catalogues all Standing Data updated records initiated through 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. These rows do not have an updated SequenceNumber, FromDate, ToDate, CreationDate, MaintenanceDate.

Because participants do not have direct access to the BUT log table so they can assume rows appearing in the C1 with no CreationDate or MaintenanceDate falling between the report selection criteria are updated by the BUT.

Snapshot report

Purpose

Reports on all NMI Standing Data See National Electricitiy Rules records a participant ID can access, according to the CATS Standing Data Access Rules The rules specifying which CATS Standing Data can be accessed, as specified in section 41.5 of the CATS Procedures.. It includes current, historic, active, and inactive records.

Use the snapshot report infrequently during bulk data correction or bulk data loading exercises.

CATS Standing Data Access Rules

Participants are entitled to all rows where, during the period the row was active, the participant had a relationship with the NMI See Relevant Rules or Procedures overlapping at least part of the period between the Start Date The date the change occurs. and End Date on the row.

Row limits

There are no row limits, but high volumes of data may impact performance during busy times. AEMO mitigate this risk by running snapshot reports at its discretion.

File size

To keep file sizes manageable, AEMO may split a report across multiple files and zipped.

File name

Example zipped file name: Snapshot_PARTID_CMR_20020423111741.zip

Example report file name: Snapshot_PARTID_CMR_20020423111741_P000001.xml

Where CMR is short for 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._METER_REGISTER and P000001 is the split file count for large reports.

Report output

The report output is in 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. format using the same: <ReportResults xsi:type="ase:ReplicationReportFormat" /> used by C4 reports to present NMI Standing Data.

If participants use schema validation on input to their systems, their schema version must be compatible with AEMO’s schema version.

Report detail

The NMI Standing Data for an individual NMI is spread across multiple files, with each report file containing records from only one table.

You can request records from the following tables:

• CATS_NMI_DATA
• CATS_PARTICIPANT_RELATIONS
• CATS_NMI_DATA_STREAM
• CATS_METER_REGISTER
• CATS_REGISTER_IDENTIFIER

Report parameters

Allocation

Two free reports each year. To reduce the load on AEMO’s systems, participants should request snapshot reports infrequently.

Report Delivery

• Files less than 1 MB zipped are emailed or delivered to the root directory of the participants MSATS 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..
• Files over 1 MB zipped are delivered via web transfer.

Obtaining a snapshot report

You request a snapshot report from the Support Hub, providing the following relevant details:

 

Requestor details
Participant ID
Name
MSATS User ID *
Position
email
Contact number
Reason for report request *
MSATS tables required
CATS_NMI_PARTICIPANT_RELATIONS
CATS_NMI_DATA
CATS_NMI_DATA_STREAM
CATS_METER_REGISTER
CATS_REGISTER_IDENTIFIER
Preferred delivery method (dependent on file size)
CD
Mailing address (if file is over 1 MB)
Email
Participant File Server