4 Flexible Trading Arrangements

4.1 Goal

The Unlocking CER Benefits Through Flexible Trading rule change facilitates flexible trading with multiple energy service providers at large customer premises, optimizes Customer Energy The unit must be a generator for the service type: ‘energy’. Loads cannot bid for mandatory restrictions capacity. Resources (CER) flexibility for small customers, and measures energy flows from in-built technology such as streetlights and EV Electric Vehicle chargers.

The project’s main objective is to implement the Flexible Trader See Relevant Rules or Procedures Model 2 (FTM2), allowing end users to establish private metering arrangements (PMA) for controllable resources managed by separate financially responsible Market Participants (FRMPs), and to introduce minor energy flow metering to accommodate non-traditional metering installations within PMAs.

This release only introduces type 9 meters allowing street-furniture, like kerbside EV chargers, smart street lighting systems and some unmetered connections, to integrate into the NEM metering framework.

A Type 9 meter can aggregate multiple loads, for example multiple streetlights under one NMI See Relevant Rules or Procedures using a Central Management System (CMS).

4.2 MITC codes

New Metering Installation Type Codes (MITC).

Meter Installation type

MITC

Meter installation description

Type 9

COMMS9

Interval Comms – Type 9
Applicable for single device metering installations

Type 9 CMS

COMMS9CM

Interval Comms – Type 9 CMS

Applicable for multiple device installations using a Central Management System (CMS)

4.3 Manufacturer values

Type 9 meters added to 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._CODES_DATED table.

CODEGROUP	CODE	CODEDESC
METER_MANUFACTURER	TYPE9	TYPE9
METER_MANUFACTURER	TYPE9CMS	TYPE9CMS
METER_MODEL	TYPE9	TYPE9
METER_MODEL	TYPE9CMS	TYPE9CMS

4.4 B2B Browser

Changes 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. when creating transactions:

Supply Service Works - Adds Type 9 and Type 9 CMS to the Customer Type dropdown.
Meter Fault and Issue Notification - Add CMS Element Fault and Customer Meter Fault to the Reason for Notice dropdown.
Floor or Level Type – Correct Platform enumerations from PL to PLF and PD to PDM.

4.5 ElectricityEnumerations.xsd

ElectricityEnumerations.xsd file contains the following changes.

Element	Changes	Related document
CustomerType	New enumerations: - Type 9 - Type 9 CMS	B2B Procedure: Service Order Process v3.91
ReasonForNotice	New enumerations: - CMS Element Fault - Customer Meter Fault	B2B Procedure: One Way Notification Process v3.91

Element

Changes

4.5.1 B2B transactions

The Customer Type enumerations impact the following Service Order A request to perform specified work, see B2B Procedures: Service Order Process. sub types:

Supply Service Works > Allocated NMI
Supply Service Works > Establish Permanent Supply
Supply Service Works > Establish Temporary Supply
Supply Service Works > Establish Temporary In Permanent
Supply Service Works > Supply Alteration
Metering Service Works > Install Meter
Metering Service Works > Miscellaneous

The new ReasonForNotice enumerations impact the One Way Notification A B2B Procedure defining the standard processes and transaction data requirements for one way messaging transactions between market participants. It provides a process where participants can send messages to other participants for multiple NMIs in a single transaction. transaction. The MeterFaultAndIssueNotification transaction also includes a fileld validation where the Notes field is a mandatory field when:

ReasonForNotice = Other; or
ReasonForNotice = One In All In; or
ReasonForNotice = CMS Element Fault

4.6 Enumerations.xsd

Enumerations.xsd file contains the following changes.

Element	Changes	Related document
AustralianFloorOrLevelType	Corrected enumerations: - PL to PLF - PD Pre-dispatch to PDM	MSR Package 1 Final Report

Element

Changes

4.6.1 B2B transactions

The updated Enumerations.xsd file impacts the following 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. transactions:

Supply Service Works > Allocated NMI > Service Order Address > Floor or Level Type
Metering Service Works > Install Meter > Customer Notification Address > Floor or Level Type
Metering Service Works > Install Meter Isolation Device > Customer Notification Address > Floor or Level Type
Metering Service Works > Move Meter > Customer Notification Address > Floor or Level Type
Metering Service Works > Exchange Meter > Customer Notification Address > Floor or Level Type
Metering Service Works > Remove Meter > Customer Notification Address > Floor or Level Type
Metering Service Works > Meter Reconfiguration > Customer Notification Address > Floor or Level Type
Metering Service Works > Meter Investigation-Inspect > Customer Notification Address > Floor or Level Type
Metering Service Works > Meter Investigation-Test > Customer Notification Address > Floor or Level Type
Metering Service Works > Reseal Device > Customer Notification Address > Floor or Level Type
Metering Service Works > Change Time Switch > Customer Notification Address > Floor or Level Type

AEMO Australian Energy Market Operator does not store transaction Standing Data. If you have a database for B2B Standing Data, you must validate it in your systems.