Last consumer change date

New CR5056 and CR5057

There is a new change request: Change NMI Energy Rules Terms– Last Consumer An end use customer of energy. Change Date for FRMPs maintaining the mandatory Last Consumer Change Date Change with Change Reason Codes:

The LCCD is enforced in the Field Validation Rules (not through the aseXML schema).

LCCD validation

Field

Procedure use

Validation

Code

Actual End Date

Optional

yyyy-mm-dd

 

Change Reason Code

Mandatory

In accordance with the Field Validation Rules

 

Initiator

Mandatory

Must be the current FRMP on the CR submission and completion dates

5106

Jurisdiction

Mandatory

ACT, NSW, QLD, SA, TAS, VIC

 

Last Consumer Change Date

Mandatory

The LCCD is invalid when it is:

  • xsd:date

  • Not a valid date (e.g. cannot be February 30)

  • Not provided in the format YYYY-MM-DD

  • Prior to 1900-01-01

  • After 9999-12-31

3012

The LCCD for a retrospective CR5057 must be less than or equal to the current date

 

The LCCD for a prospective CR5057 must be less than the proposed change date

 

NMI

Mandatory

Must exist in MSATS

1113

NMI Checksum

Mandatory

In accordance with the Field Validation Rules

 

NMI Classification Code

 

Must be SMALL, LARGE, WHOLESAL, GENERATR, NREG or DWHOLSAL

1168

Participant ID

Mandatory

In accordance with the Field Validation Rules

 

Proposed Change Date

Mandatory

Must be between:

  • For Prospective CRs: The current date + 1 day and current date + 65 Business Days

  • Retrospective CRs: The current date - 1 Business Day and the current date

 

Transaction ID

Mandatory

In accordance with the Field Validation Rules

 

FRMP responsibility

FRMPs can correct the Last Consumer Change Date if they are aware the consumer changed.

There is no restriction on the date the current FRMP Financially Responsible Market Participant, usually a retailer, Generator, Market Customer or a Market Small Generator Aggregator, identified in respect of a connection point. Responsible for dealings with AEMO in relation to a specific load. can provide. Once they verify the consumer’s start date, they can update the LCCD to a retrospective date.

CR1030 and CR1040

Where a transfer completes for a CR1030 or CR1040, the Last Consumer Change Date is populated by AEMO Australian Energy Market Operator using the Actual Change Date The effective date of changes specified in a Change Request. The same date as the FromDate in a C4 Report and the Start Date in MSATS interfaces displaying NMI master data..

CATS_NMI_DATA

The Last Consumer Change Date field is in the table.

Table

Format

CATS_NMI_DATA

dd-mmm-yyyy

Change request status notification rules

The Last Consumer Change Date is included in the Change Request Status Notification Rules Rules that specify which roles are advised when a Change Request undergoes a change in status, as described in the CATS Procedures for each Change Reason Code.. The current LNSP, MDP Meter Data Provider. An organisation which installs, commissions, gathers, and verifies data remotely from meters in the National Electricity Market (NEM)., MPB See MP, and RP Responsible Person. The participant with formal responsibility for the provision, installation and maintenance of a metering installation. receive the Completed One of the status points of a Change Request. status that includes the Last Consumer Change Date:

Status

FRMP

ENLR

LNSP

MDP

MPB

MPC

MC (RP)

RoLR

DRSP

New

Current

New

Current

New

Current

New

Current

New

Current

New

Current

New

Current

New

Current

New

Current

CAN

û

ü

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

COM

û

ü

û

û

û

ü

û

ü

û

ü

û

û

û

ü

û

û

û

û

OBJ

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

PEND

û

ü

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

REJ

û

ü

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

REQ

û

ü

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

û

Standing data access rules

To comply with the Standing Data Access Rules The National Gas or Electricity rules., only participants with a current role for a NMI See Relevant Rules or Procedures can query the Last Consumer Change Date in 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. report requests. The fields are accessible by the following Participant Roles:

Field

Jurisdiction

Standing Data Access Rules

DRSP

FRMP

ENLR

LNSP

MDP

MPB

MPC

MC (RP)

RoLR

NEMM

NSP2

Last Consumer Change Date

ALL

û

ü

û

ü

ü

ü

û

ü

û

ü

û

NMI discovery

The Last Consumer Change Date is not available in NMI Discovery:

Field

Jurisdiction

NMI Discovery

NMID1

NMID2

NMID3

MC search

Last Consumer Change Date

ALL

û

û

û

û

The LCCD field displays in NMI Discovery web interfaces, however because the field is not included in a NMI Discovery Search its value is always blank.

NMI classification code

The NMI Classification Code A code identifying the type of consumer to which a NMI belongs, e.g. large or small wholesale generators. for CR5056 and CR Change Request 5057 must be SMALL, LARGE, WHOLESAL, GENERATR, NREG or DWHOLSAL.

Notification rules

The notification rules for CR1030 and CR1040 follow the defined Change Request Status Notification Rules.

Objection rules

Objections are not permitted for a CR 5056 or CR 5057. If the CR passes validation and goes to Requested A status point of a Change Request. status, it proceeds directly to Pending A status point of a Change Request. status.

Completion rules

Where CR validation passes:

  1. The LCCD value is updated for the NMI according to the CATS History Model.
  2. Notifications are issued according to the CR status notification rules.

getUsageAPI

The Last Consumer Change Date is added to the Consumer Data Right > getUsageAPI.

MSATS web portal

NMI Master - view

In compliance with the Standing Data Access Rules, the following participant roles can view the LCCD field in 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. web portal > NMI Master, NMI Master Summary, and Point in Time web interfaces:

Change Request – [New/Edit]  – NMI Standing Data

CR5056 and CR5057

When creating a CR5056 or CR5057 there is a new Last Consumer Change Date field for FRMPs in the Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS. - New - NMI Standing Data See National Electricitiy Rules interface.

NMI Information> NMI Master > NMI Master – View

There is a new Last Consumer Change Date field in the NMI Information> NMI Master > NMI Master – View interface for FRMPs viewing CATS_NMI_DATA records.

C1, C4, and snapshot reports

The new SAPS Standalone Power Systems Role The role a company has with a connection point in CATS. A single company can have more than one role associated with a NMI. Category Generating units modelled in the EAAP are categorised into Baseload, Intermediate or Peaking generation groups. is added to the CATS_PARTICIPANT_ROLES table.

The LCCD is included under Master Data Records in the C1, C4, and, snapshot reports.

In compliance with the Standing Data Access Rules, the following participant roles receive the LCCD field in the LCCD field in C1 report:

  • LNSP
  • MDP
  • MPB
  • MC (RP)
  • FRMP

MSATS generic field names

AEMO uses the CND CATS NMI Data_[nn] framework. Where possible, participants should use the Procedural field names defined in the Standing Data for MSATS. AEMO does not support participants using the Oracle database table and field names. For participants using the C1 CATS Transaction See Relevant Rules or Procedures Field Validations report these are the new MSATS field name mappings.

Procedural field

MSATS field

Data type

Table

Last Consumer Change Date (LCCD)

CND_11

Date DD-MON-YYYY

CATS_NMI_DATA

LCCD FAQs

Who can update the LCCD and when?

FRMPs update the LCCD when they are aware the consumer changed.

Who receives the Last consumer change date in a C1 report?

In compliance with the Standing Data Access Rules, the following roles have access to the LCCD field in a C1 report:

  • LNSP
  • MDP
  • MPB
  • MC (RP)
  • FRMP
  • AEMO

If the LCCD changes are postponed, will the r43 schema still have the LCCD field?

Yes, the LCCD is in the r43 aseXML schema Specification to describe the structure of an aseXML message., but the field is not populated until the effective date (1 November 2023 TBC To be confirmed) so there are no obligations for participants to send CR5056 and CR5057 until then.

For CR5056 and CR5057, if participants remain on r42, do they receive a notification when the CRs complete?

They receive the notification with a comment flagging the removal of the unsupported fields.