Metering installation type codes

The Metering Installation Type Codes identify the type of Metering Installation as specified in the NER National Electricity Rules. The rules made under the National Electricity Law (NEL). They govern the day-to-day operations of the National Electricity Market (NEM) and provide the framework for network regulation.. They indicate if a Meter is manually or remotely read.

This affects the transfer transaction process flow because:

• If a Meter is manually read, the Metering Data Provider (MDP Meter Data Provider. An organisation which installs, commissions, gathers, and verifies data remotely from meters in the National Electricity Market (NEM).) must supply 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. before the transaction completes.

If manually read (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. flag is set to Y) and the Change Request A transaction submitted by participants in MSATS whenever they want to create or update data held in MSATS. Field Validation Rules As described in the CATS Procedures, they specify, for each Change Reason Code, the fields in MSATS populated at the creation of a transaction or at other times in the life cycle of a transaction. are set up to request a date, MSATS sends requests the nominated party to provide it (for example the new MDP).

For Interval Period over which interval energy data is recorded by the metering installation that corresponds to a TI or submultiples of a TI. meters, the Manually Read Field, indicates MDPs must supply the date of change manually. It does not indicate the Metering type. This confirms the Metering Installation is National Electricity Rules See Relevant Rules or Procedures (NER) compliant.

• If it is remotely read, the transaction completes at the requested transfer date.

Table 127 Meter install type codes

Metering Group	Meter Install Type Code	Description
Type A	BASIC	Accumulation Meter – Type 6
	MRIM without a Meter Read Type of RWD	Manually Read Interval Meter – Type 5
	MRAM	Small customer metering installation – Type 4A
Type B	COMMS1	Interval Meter with communications – Type 1
	COMMS2	Interval Meter with communications – Type 2
	COMMS3	Interval Meter with communications – Type 3
	COMMS4	Interval Meter with communications – Type 4 This code is used for large customer with type 4 metering installations and for small customer type 4 metering installation installed before 1 December 2017
	COMMS4C	CT connected metering installation that meets the minimum services specifications
	COMMS4D	Whole current metering installation that meets the minimum services specifications
	MRIM with a Meter Read Type of RWD	Manually Read Interval Meter – Type 5
	VICAMI	A relevant metering installation as defined in clause 9.9C of the NER.
	SAMPLE	Sample Meter
	PROF	For Profile Setup
Type C	No Meters Exist	n/a
Type D	UMCP	Unmetered Supply – Type 7

 

Allocating metering installation codes

For more details, see DataStreamType in Standing Data for MSATS

Consequences of allocating certain Metering Installation Codes:

1. If the Metering Installation Type Code is COMMSx, COMMS4C, COMMS4D, MRIM, MRAM, VICAMI, or UMCP:

1. If the Datastream Suffix is Nx (for example, N1), the DataStreamType must be I (Interval) or P (P = Profile Area, Sample Meters only).

2. The ProfileName must be NOPROF

2. If the Metering Installation Type Code is BASIC:

1. The DataStreamType must be C.

2. In Victoria, Tasmania, and ACT: The ProfileName must be NSLP.

3. In NSW, QLD, and SA: The ProfileName must be NSLP or the relevant Controlled Load Profile (CLP).

4. The Datastream Suffix must be numeric (for example, 11).