MSATS Validation

CR validation logic

AEMO Australian Energy Market Operator validates the new CATS Standing Data for maximum length, data type for all inbound CRs where a value is provided. AEMO only accepts allowed enumerations defined under the MSATS Procedures All of the following procedures: CATS Procedures, WIGS Procedures, MDM Procedures, NMI Standing Data Schedule, NMI Procedure, and Part A of the NEM RoLR Processes..

Validation A process to test the veracity and integrity of metering data. logic does not consider the proposed effective date of the CR Change Request, it considers when the CR is received and processed.

AEMO ignores values received for new supported 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. fields currently not existing in 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..

Removed standing data

AEMO rejects CRs with removed Standing Data items.

Unstructured address

If an unstructured AddressLine NMI See Relevant Rules or Procedures Data value is provided in a 2XXX or 5XXX series CR, AEMO rejects it because the field is no longer supported under the MSATS Procedures. Unstructured AddressLine will however continue to be returned via NMI Discover until 7 November 2023 as part of the 12 month transition window.

GPS Coordinates Lat and Long

For GPS Coordinates Lat and Long, trailing zeros will be removed by MSATS upon receipt. For example, when submitting GPS Coordinates Lat, a 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. Submission A Bid/Offer submission can have: 1. Multiple Trading Days 2. Multiple DUIDs/LinkIDs 3. All Service Types in the same Submission of ‘36’ and ‘36.0000000’ are accepted by MSATS and treated as equal. The CATS Notification A transaction that does not have a corresponding reply transaction, see Notification Business Transaction Pattern. or CATS Report A data report that loads into a data model table. Identified by its type, subtype, and version. For example: BILLING,BILLINGASPAYMENTS,2 generated by MSATS for that NMI Standing Data See National Electricitiy Rules item will, however, remove any trailing zeros, resulting in a CATS Notification GPS Coordinates Lat value of ‘36’. Similarly, where no GPS coverage is available, a value of ‘0’, ‘0.0000’, or ‘0.000000’ shall be accepted for a CATS Submission and shall be reported as ‘0’ within a CATS Notification or CATS Report.

Inbound change requests

CATS_METER_REGISTER

The following list of enumerations is validated for inbound CRs:

Enumeration

Value

Description

CurrentTransformerTest

VoltageTransformerTest

SAMPLE

Part of 100% testing

SAMPLE TESTED

Tested as part of a sample plan

TESTED

Part of an approved sample plan

CurrentTransformerAccuracyClass

0.1

0.5ME2.5

0.2

0.5 EXT 200%

0.2M

0.5S

0.2ME1.5

0.5S EXT 200%

0.2ME2

1

0.2ME2.5

2

0.2S

AM

0.5

BM

0.5M

0.05PX

0.5ME1.25

UNKNOWN

0.5ME2

 

 

Allowed enumerations

CurrentTransformerType

A

S

B

T

C

U

HV 1A

V

HV 5A

W

LV OTHER

 

 

Allowed enumerations

CurrentTransformerRatioConnected

5:5

160:5

2000:5

150:1

1250:1

10:5

200:5

2400:5

200:1

1400:1

15:5

250:5

2500:5

250:1

1500:1

20:5

300:5

3150:5

300:1

1600:1

25:5

400:5

3200:5

400:1

1700:1

30:5

500:5

4000:5

500:1

1900:1

40:5

600:5

4500:5

600:1

2000:1

50:5

630:5

5000:5

630:1

2400:1

60:5

750:5

5:1

650:1

2500:1

80:5

1000:5

40:1

800:1

3000:1

75:5

800:5

25:1

750:1

3000:5

100:5

1200:5

50:1

900:1

3200:1

120:5

1250:5

75:1

1000:1

4000:1

125:5

1500:5

100:1

1100:1

4500:1

150:5

1600:5

125:1

1200:1

4800:1

5000:1

 

 

 

 

 

Allowed enumerations

Manufacturer

For values, see MSATS online help > Metering Data > Update Manufacturer and Model

MarketNet access required

Allowed enumerations

Model

For values, see MSATS online help > Metering Data > Update Manufacturer and Model

MarketNet access required

Allowed enumerations

Test Result

PASS

FAIL

Allowed enumerations

VoltageTransformerAccuracyClass

0.01M

B

0.2M

BL

0.5M

C

1M

D

A

UNKNOWN

AL

 

 

Allowed enumerations

VoltageTransformerRatio

3300:110

44000:110

5000:110

66000:110

5500:110

110000:110

6600:110

132000:110

11000:110

220000:110

11500:110

275000:110

22000:110

330000:110

33000:110

500000:110

 

Allowed enumerations

VoltageTransformerType

COMBINED

IVT + CT

CVT

Capacitive Voltage Transformer

IVT

Inductive Voltage Transformer

THREE-PHASE THREE-LIMB

 

THREE-PHASE FIVE-LIMB

 

 

CATS_REGISTER_IDENTIFIER

Enumeration

Value

Description

ControlledLoad

NO

No controlled load

YES

There is a controlled load associated with a controlled load network tariff on this register

EXT

There is controlled load which is externally switched by the LNSP associated with a controlled load network tariff on this register

TimeOfDay

ALLDAY

All day

BUSINESS

Business time of day

CONTROLLED

Controlled time of day

DEMAND

Demand is used for describing a register

EVENING

Evening time of day

INTERVAL

Interval time of day, used for all Interval metering

OFFPEAK

Off peak time of day

PEAK

Peak time of day

SHOULDER

Shoulder time of day

Use

AVERAGE

Average meter

CHECK

Check meter

INFORM

Information meter

LOGICAL

Logical meter

PREPAID

Prepaid meter

REVENUE

Revenue meter or unmetered load

SAMPLE

Sample meter

STATIS

Statistical meter

TUOS

TUOS meter

UNKNOWN

Unknown meter use code

 

Inflight change requests

MSATS validation and processing behaviour for CRs post this Release. Applies to all Prospective CRs where the Proposed date is after Procedual Effective Date The trading day specified in a Bid/Offer, and any subsequent trading days until superseded by a later valid Bid/Offer. and Retrospective CRs where the Proposed Date is before Procedual Effective Date.

ID

CR Submitted

CR Characteristics

CR Status on Validation

Notification

On CR COM

CATS Reports

1

Before MSATS 48.0 deployment.

CR that includes a value for a removed CRI or CMR Standing Data item  (e.g. AdditionalSiteInformation)

REQ

  1. REQ notifications will include removed CRI or CMR items.

  2.  

  3. All other notifications (including PEND, COM) after the Procedural Effective Date will not include the value of the removed Standing Data item.

The value of the removed field is written to Standing Data but viewable by AEMO only.

C1/C4/C7 Does not include the updated value of the removed Standing Data item.

2

CR that includes a value for Unstructured Address.

REQ

Includes the value of Unstructured Address.

Value of the Unstructured Address written to Standing Data.

C1 includes the updated value of the Unstructured Address.

C4/C7 includes the updated value of Unstructured Address where no Structured alternative exists.

3

CR that includes a value for a new MSDR  Standing Data item  (e.g.optional HouseNumberTo or mandatory ConnectionConfiguration)

REQ

Does not include the value of the new Standing Data item.

The value of the new optional field is not written to Standing Data.

C1/C4/C7 Does not include the updated value of the new Standing Data item.

4

In the window between MSATS 48.0 deployment and the effective date of the Procedure.

CR that includes a value for a removed CRI or CMR Standing Data item  (e.g. Demand1)

REQ

  1. REQ notifications will include removed CRI or CMR items.

  1. All other notifications(including PEND, COM) after the Procedural Effective Date will not include the value of the removed Standing Data item.

The value of the removed Standing Data item is written to Standing Data but viewable by AEMO only.

C1/C4/C7 Does not include the updated value of the removed  Standing Data item.

5

CR that includes a value for Unstructured Address.

REQ

Includes the value of Unstructured Address.

Value of the Unstructured Address Deprecated from: May 2023 An address with the following format: • A string of text characters with a maximum length of 80 per line. • A maximum of 3 lines. written to Standing Data.

C1 includes the updated value of the Unstructured Address.
C4/C7 includes the updated value of Unstructured Address where no Structured alternative exists.

6

CR that includes a value for a new MSDR Standing Data item  (e.g. optional HouseNumberTo or mandatory ConnectionConfiguration)

REJ - Event code 1101 - Data fields provided that are not valid for this Change Request Type.

REJ is inclusive of new Standing Data items.

The value of the new optional field is not written to Standing Data.

 

7

After Procedural Effective Date.

CR that includes a value for a deprecated CRI or CMR Standing Data item  (e.g. Demand1)

REJ - Event code 1101 - Data fields provided that are not valid for this Change Request Type.

Does not include the value of the removed Standing Data item.

Values of the CR not written to Standing Data.

 

8

CR that includes a value for Unstructured Address.

REJ - Event code 1101 - Data fields provided that are not valid for this Change Request Type.

Includes the value of Unstructured Address.

Values of the CR not written to Standing Data.

 

9

CR that includes a value for a new MSDR Standing Data item  (e.g.optional HouseNumberTo or mandatory ConnectionConfiguration)

REQ

Includes the value of the new Standing Data item.

The value of the new optional field is written to Standing Data.

C1/C4/C7 includes the updated value of the new Standing Data item.

10

CR that does not include a field that has been made Mandatory under the CATS/WIGS v5.31 Procedures  (e.g. ConnectionConfiguration)

REJ - Event code 1151 - Not all required fields have been entered.  Please ensure all fields have been completed.

Includes the value of the mandatory Standing Data item.

Values of the CR not written to Standing Data.

 

11

CR that does not include a valid enumeration under the CATS/WIGS v5.31 Procedures  (e.g. an invalid value for ControlledLoad)

REJ - Event codes 1919 and 1920 for Invalid ControlledLoad and TimeOfDay
REJ - Event code 1100 for other new CMR fields

Includes the value of the mandatory Standing Data item.

Values of the CR not written to Standing Data.