8 FAQs

8.1 Why is AEMO updating the hazard field?

The approach for the hazard field update is still being determined.

8.2 When is the draft r46 schema be available?

24 April 2025.

8.3 How do I find the latest electricity schema?

There are two electricity schema types - B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. and B2M Business-to-Market. You can find the latest aseXML schema Specification to describe the structure of an aseXML message. 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.:

B2M – In the Participant > Participant schema interface. See View your B2M schema.
B2B – In the B2B Browser A web interface supporting the creation and management of a defined set of business-to-business transactions and acknowledgements. Optionally used to manage your B2B inbox and outbox. It remains part of the B2B e-Hub services. > Transforms and Protocol interface. See B2B protocols.

8.4 Is an aseXML schema version specific to either gas or electricity?

Yes, some versions do not apply to the gas or electricity market. Additionally, an electricity schema version can contain B2B and B2M changes, only B2B changes, or only B2M changes.

8.5 When does a participant receive the new LCCD value?

The LCCD update is an automated change triggered through specified CRs. When AEMO Australian Energy Market Operator detects an NMI See Relevant Rules or Procedures transitioning from a “Greenfield” (G) to “active” (A), a batch process is initiated to update the LCCD field. This field is in the completion notification for the change request.

8.6 Does the change request notification include the LCCD element when the NMI status updates from G to A?

The change in NMI status from greenfield (G) to active (A) is captured in the 5050/5051 change request. The 5050/5051 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. notification includes the LCCD value on a COM status as shown in the example below.

Copy

<ChangeRequest>
   <Participant>ENGYPART</Participant>
   <RequestID>1441204352</RequestID>
   <ChangeStatusCode>COM</ChangeStatusCode>
   <ChangeData>
      <ChangeReasonCode>5051</ChangeReasonCode>
      <ActualChangeDate>2025-06-01</ActualChangeDate>
      <NMIStandingData xsi:type="ase:ElectricityStandingData" version="r46">
         <NMI checksum="0">9990005230</NMI>
         <MasterData>
            <Status>A</Status>
            <LastConsumerChangeDate>2025-06-01</LastConsumerChangeDate>
         </MasterData>
      </NMIStandingData>
   </ChangeData>
</ChangeRequest>

8.7 Why is the r46 aseXML schema being released on 26 October 2025, but the effective date is 1 December 2025?

To minimise impacts to all Market Participants, AEMO aims to only release one schema version per year. Participants are obligated to populate and maintain the LegacyMtrReplacementPlan field from 26 October 2025.

The schema also includes new and updated fields to support Rule changes effective from 1 December 2025. Participants can send r46 transactions with B2B Procedures v3.9 elements prior to 1 December 2025 only if supported under a bilateral agreement.

8.8 How should participants send an address with 2 house numbers and 2 house number suffixes in B2B transactions between 26 October and 1 December 2025?

To comply with the B2B Procedures The documents that comprise the B2B Procedures prescribing the content of, the processes for, and the information to be provided to support B2B communication.:

From 26 October to 30 November 2025, participants can begin using 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. r46 but must continue to use 2 instances of the BuildingOrPropertyName element (that is, maxOccurs=2) to represent primary and secondary complex names.
From 1 December 2025, when the B2B Procedure Technical Delivery Specification Process v3.9 takes effect, participants must use BuildingOrPropertyName and BuildingOrPropertyName2 to represent primary and secondary complex names.
We plan to remove the maxOccurs=2 setting for BuildingOrPropertyName in the next schema release through the 2026 Flexible Trading Arrangements (FTA) initiative.

8.9 Have the aseXML schema enumerations for Flat Type and Street Type changed?

No. The Enumerations.xsd schema file includes comments describing the mapping of street types of values used in MSATS to the AS4590.1:2017 address standard.

8.10 Why is the 4060 CR being created?

The 4060 CR Change Request manages Embedded Network Child NMI The NMI assigned to a child connection point. datastreams. The new CR allows the MDP Meter Data Provider. An organisation which installs, commissions, gathers, and verifies data remotely from meters in the National Electricity Market (NEM). to prospectively activate Energy Rules Terms and inactivate an existing datastream. Retrospective activation and inactivation are no longer allowed.

When creating a new Embedded Network Child NMI, the 4001 CR can still be used to retrospectively create the initial datastream. Once created, the 4060 CR maintains the datastream.

8.11 Why are embedded Network Child NMIs only allowed to be prospectively changed?

Retrospective changes to Embedded Network Child NMIs cause settlement anomalies, affecting the settlement of the NEM. Removing retrospective activation and inactivation of Embedded Network Child NMI Datastreams eliminates this impact.

8.12 Are other NMIs affected by the new 4060 CR?

Existing NEM connected NMIs will still use the 4050 / 4051 CRs to retrospectively and prospectively activate NMI datastreams. The introduction of Secondary Settlements See Relevant Rules or Procedures Points (SSPs) as part of the FTA Rules The National Gas or Electricity rules. change does not allow retrospective datastream changes.

8.13 When do Site Defects details get removed in MSATS?

To assist participants in maintaining the Defect Flag, Defect Type and Defect Issuing MC Meter Coordinator; The Role Code used in MSATS for an MC is RP. fields, MSATS removes the values when a CR 3004 / 3005 or 3090 / 3091 is completed, a Basic or MRIM meter is removed, and a COMMS or MRAM meter is installed.

When the Site The physical location of the connection point, see B2B Procedures: Customer and Site Details and Service Orders Process. Defect values are removed, the PEND and COM notification includes the updated fields as shown in the following example.

Copy

<?xml version="1.0" ?>
<ase:aseXML xmlns:ase="urn:aseXML:r46" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:aseXML:r46 http://www.nemmco.com.au/aseXML/schemas/r46/aseXML_r46.xsd">
  <Header>
    <From description="Australian Energy Market Operator Limited">NEMMCO</From>
    <To description="Market Participant">MKTPART</To>
    <MessageID>NEMMCO-MSG-999112971</MessageID>
    <MessageDate>2025-03-25T02:38:08+10:00</MessageDate>
    <TransactionGroup>CATS</TransactionGroup>
    <Priority>Medium</Priority>
    <SecurityContext>NEMMCOBATCH</SecurityContext>
    <Market>NEM</Market>
  </Header>
  <Transactions>
    <Transaction transactionID="NOTF-8888980297" transactionDate="2025-03-25T00:12:03+10:00" initiatingTransactionID="CAT888274387">
    <CATSNotification version="r29">
         <Role>NEM</Role>
         <RoleStatus>C</RoleStatus>
<ChangeRequest>
   <Participant>MKTPART</Participant>
   <RequestID>9991203710</RequestID>
   <ChangeStatusCode>PEND</ChangeStatusCode>
   <ChangeData>
      <ChangeReasonCode>3090</ChangeReasonCode>
      <ActualChangeDate>2025-03-24</ActualChangeDate>
      <NMIStandingData xsi:type="ase:ElectricityStandingData" version="r46">
         <NMI checksum="7">5555449002</NMI>
         <MasterData>
            <DefectFlag xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
            <DefectType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
            <DefectIssuingMC xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
         </MasterData>
         <DataStreams>
            <DataStream>
               <Suffix>E1</Suffix>
               <ProfileName>NOPROF</ProfileName>
               <AveragedDailyLoad>11</AveragedDailyLoad>
               <DataStreamType>Interval</DataStreamType>
               <Status>A</Status>
            </DataStream>
         </DataStreams>
         <MeterRegister>
            <Meter>
               <SerialNumber>MTR1234</SerialNumber>
               <InstallationTypeCode>MRIM</InstallationTypeCode>
               <Status>R</Status>
               <RegisterConfiguration>
                  <Register>
                     <RegisterID>001</RegisterID>
                     <NetworkTariffCode>NAST11</NetworkTariffCode>
                     <UnitOfMeasure>KWH</UnitOfMeasure>
                     <TimeOfDay>INTERVAL</TimeOfDay>
                     <Multiplier>1</Multiplier>
                     <DialFormat>5.1</DialFormat>
                     <Suffix>E1</Suffix>
                     <ControlledLoad>NO</ControlledLoad>
                     <ConsumptionType>Actual</ConsumptionType>
                     <Status>R</Status>
                  </Register>
               </RegisterConfiguration>
            </Meter>
            <Meter>
               <SerialNumber>COMMS1234</SerialNumber>
               <InstallationTypeCode>MRAM</InstallationTypeCode>
               <Use>AVERAGE</Use>
               <Manufacturer>METERMAN</Manufacturer>
               <Model>MODEL</Model>
               <Status>C</Status>
               <RegisterConfiguration>
                  <Register>
                     <RegisterID>E2</RegisterID>
                     <NetworkTariffCode>TARABC</NetworkTariffCode>
                     <UnitOfMeasure>KWH</UnitOfMeasure>
                     <TimeOfDay>INTERVAL</TimeOfDay>
                     <Multiplier>1</Multiplier>
                     <DialFormat>6.3</DialFormat>
                     <Suffix>E2</Suffix>
                     <ControlledLoad>NO</ControlledLoad>
                     <ConsumptionType>Actual</ConsumptionType>
                     <Status>C</Status>
                  </Register>
               </RegisterConfiguration>
            </Meter>
         </MeterRegister>
      </NMIStandingData>
   </ChangeData>
</ChangeRequest>
<JurisdictionCode>VIC</JurisdictionCode>
<NMIClassificationCode>LARGE</NMIClassificationCode>
<ObjectionEndDate>2025-03-24</ObjectionEndDate>
</CATSNotification>
    </Transaction>
    <Transaction transactionID="NOTF-8888980309" transactionDate="2025-03-25T00:12:10+10:00" initiatingTransactionID="CAT888274387">
    <CATSNotification version="r29">
         <Role>NEM</Role>
         <RoleStatus>C</RoleStatus>
<ChangeRequest>
   <Participant>MARKPART</Participant>
   <RequestID>9991203710</RequestID>
   <ChangeStatusCode>COM</ChangeStatusCode>
   <ChangeData>
      <ChangeReasonCode>3090</ChangeReasonCode>
      <ActualChangeDate>2025-03-24</ActualChangeDate>
      <NMIStandingData xsi:type="ase:ElectricityStandingData" version="r46">
         <NMI checksum="7">5555449002</NMI>
         <MasterData>
            <DefectFlag xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
            <DefectType xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
            <DefectIssuingMC xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
         </MasterData>
         <DataStreams>
            <DataStream>
               <Suffix>E1</Suffix>
               <ProfileName>NOPROF</ProfileName>
               <AveragedDailyLoad>11</AveragedDailyLoad>
               <DataStreamType>Interval</DataStreamType>
               <Status>A</Status>
            </DataStream>
         </DataStreams>
         <MeterRegister>
            <Meter>
               <SerialNumber>MET1234</SerialNumber>
               <InstallationTypeCode>MRIM</InstallationTypeCode>
               <Status>R</Status>
               <RegisterConfiguration>
                  <Register>
                     <RegisterID>001</RegisterID>
                     <NetworkTariffCode>TARABC</NetworkTariffCode>
                     <UnitOfMeasure>KWH</UnitOfMeasure>
                     <TimeOfDay>INTERVAL</TimeOfDay>
                     <Multiplier>1</Multiplier>
                     <DialFormat>5.1</DialFormat>
                     <Suffix>E1</Suffix>
                     <ControlledLoad>NO</ControlledLoad>
                     <ConsumptionType>Actual</ConsumptionType>
                     <Status>R</Status>
                  </Register>
               </RegisterConfiguration>
            </Meter>
            <Meter>
               <SerialNumber>COMMS1234</SerialNumber>
               <InstallationTypeCode>MRAM</InstallationTypeCode>
               <Use>AVERAGE</Use>
               <Manufacturer>METERMAN</Manufacturer>
               <Model>MODEL</Model>
               <Status>C</Status>
               <RegisterConfiguration>
                  <Register>
                     <RegisterID>E2</RegisterID>
                     <NetworkTariffCode>TARABC</NetworkTariffCode>
                     <UnitOfMeasure>KWH</UnitOfMeasure>
                     <TimeOfDay>INTERVAL</TimeOfDay>
                     <Multiplier>1</Multiplier>
                     <DialFormat>6.3</DialFormat>
                     <Suffix>E2</Suffix>
                     <ControlledLoad>NO</ControlledLoad>
                     <ConsumptionType>Actual</ConsumptionType>
                     <Status>C</Status>
                  </Register>
               </RegisterConfiguration>
            </Meter>
         </MeterRegister>
      </NMIStandingData>
   </ChangeData>
</ChangeRequest>
<JurisdictionCode>VIC</JurisdictionCode>
<NMIClassificationCode>LARGE</NMIClassificationCode>
<ObjectionEndDate>2025-03-24</ObjectionEndDate>
</CATSNotification>
    </Transaction>
  </Transactions>
</ase:aseXML>