No.

Requirement

1 Meter Features
1.1 Meter data
record

1.2 Built-in
memory
1.3 Load limit

1.4 Data
communicati
on
1.5 Tamper
detection
1.6 Flexible
configuration

1.7 Basic features

1.8 Communicati
on indication

1.9 Self-
discovery and
self-registry
functionality

1.1 Test output

1.11 Other salient
features

1.12 Self-
diagnostic
feature

2 Load Control: Disconnection and Reconnection

2.1 Disconnect or
reconnect
switch

2.2 Remote
disconnect or
reconnect
switch

2.3 Supply
disconnection

2.4 Connection
status of
meter

2.5 Phase
disconnection

2.6 Remote
programmabil
ity
2.7 Audio-
enabled alarm

2.8 Remote
reconnection

2.9 Automatic
connection or
disconnection

2.1 Event log

2.11 Self-
discovery and
self-registry
functionality

2.12 Connect or
disconnect
indication

2.13 Secure
programmabil
ity
2.14 Reading
frequency

2.15 RTC and time

synchronizati
on

3 Tariff and TOU Programming

3.1 Remote
configuration

3.2 Tariff store

3.3 Tariff seasons

3.4 Season
defined

3.5 Tariff display

3.6 Tariff register
management

4 Meter Data Storage

4.1 Meter internal
memory

4.2 Data storage

4.3 Data security

4.4 Data retrieval

4.5 Data
download

4.6 Meter
integrity

5 Event Log
5.1 Meter event

5.2 Record of
event
5.3 Event
security

5.4 Special
events
5.5 Supply
interruption
registration

6 Self-Check
6.1 Verification
of meter
function

6.2 Firmware
update

7 Meter Firmware Upgrade

7.1 Firmware
upgrade

7.2 Firmware
compatibility

7.3 Local
firmware
upgrade

7.4 Remote
firmware
upgrade

8 Quantities to Be Measured, Monitored, and Stored in Memory

8.1 Measureable
quantities

8.2 Display
modes

8.3 Monitoring
and
memorizable
quantities

9 Prepaid
metering
support
9.1 15 minute
cumulative
energy
consumption
reporting to
HES

10 Security and Tampering

10.1 Firmware
verification

10.2 Access
verification

10.3 First
protection
level
10.4 Second
protection
level

10.5 Third
protection
level

10.6 Tamper
events

10.7 Tamper
sequence

10.8 Tamper time

11 Sealing of the Meter

11.1 Seal
arrangement
11.2 Polycarbonate
plastic
security seals

11.3 Tamper-proof
void seals

11.4 Specifications
of void seal

12 Display of Meter Values

12.1 Character
display

12.2 Data retention

12.3 Parameter
symbol
12.4 Display of
multiple
values

12.5 Persistence
time
12.6 Meter serial
number

13 Maximum Demand
13.1 Maximum
demand (MD)
registration

13.2 Maximum
demand reset

13.3 MD reset
authentication

13.4 MD sealing
provision

13.5 MD count

14 Load Survey Capability

14.1 Load survey
storage

14.2 Load survey

display
 Description

eter Features
The meter shall record data pertaining to billing, load surveys, events and tampering, and instantaneous
demand parameters.

The meter shall have built-in permanent nonvolatile memory to store all relevant meter data, events for
up to 65 days.
The meter shall support remote load management by sending load curtailment signals through direct
display, SMS, or web applications.
This implies compatibility of storage and the capability to communicate requested data at programmed
intervals.

Data on abnormal and tamper events shall be detected, reported, resolved, and stored.

The meter should be flexibly configured to support customized recording of needs such as load profile,
time of use and demand metering.

• Multiple load profile recording, tariff-based prepayment and multi-energy recording

• Full quadrant energy measurement (import or export, lead or lag)
• Net or gross measurement options
• Dedicated cogeneration and off-peak meter variants
• Energy measurement, inclusive or exclusive of harmonic content
• Configurable event logging and tamper detection
• Under frequency load control
• Multiple load control relay configurations
• Independent load control schedules
• Manual and emergency load control override
• Group load control
• Managed load energization
• Programmability and reset capability. The meter should have a manual or automatic, remote or local
programming reset function to record the monthly energy consumption.

Meters should provide onsite indication of communication with the AMI network so that a technician
servicing a meter can determine the success of communication with the AMI network.

Meters shall have self-discovery and self-registry functionality to allow the AMI system to detect and
register the meter within 60 minutes of meter connection and establishment of communication

The meter shall have a test output accessible from the front and be capable of being monitored with
suitable testing equipment. The operation indicator must be visible from the front. Test output device
shall be provided in the form of an LED output device,
for kWh and kVArh measurement. The relation between test outputs shall comply with the marking on the
nameplate or with the indication on display if so provided in addition to details on the name plate (pulse
per kWh/kVArh).
 The meter shall have these other salient features:
• The meter shall have provision for reading in the absence of power through an internal rechargeable
battery
• The meter shall work accurately, irrespective of the phase sequence of the mains supply
• The meter shall remain powered up and functional in the presence of any two wires
• The meter shall continue to record data accurately according to the prevailing electrical conditions,
even if the neutral mode of supply gets disconnected
• The meter shall record correct energy consumption data despite the reversal of one or more phases
• Meter measurement shall not be affected by the injection of
AC voltage, chopped signal, or DC signal and harmonics in any of the outgoing leads of the meter
• The meter shall register accurate energy even if load is drawn down partially or fully through local
earth
• The meter should be programmed for both kVA MD and kW MD. However, other programmable
parameters should be made available according to the IEC.

The meter shall be capable of performing a complete self-diagnostic check to monitor the circuits for any
malfunction and ensure
the integrity of date memory location all the time. The meter shall provide information for unsatisfactory,
nonfunctioning, or malfunctioning of the following:
• Time and date.
• All display segments, as required.
• RTC.
• NVM.
If possible, the details of the malfunctioning shall be recorded in the meter memory and an alarm sent to
HES.

ad Control: Disconnection and Reconnection

All meters shall have a supply disconnect or reconnect switch or contactor for part or full load for both
phase and neutral mode, along with the load limit.

The AMI system shall support the remote disconnection or reconnection of consumer supply only via the
supply contactor.

When the AMI meter performs a disconnect operation, outgoing power circuits from the meter for the
particular phase or neutral mode shall be disconnected.

To confirm the current state of a meter, the AMI system shall support on-demand remote polling of the
meter to determine whether the supply is open or closed, or whether the meter
is energized or not. The meter shall provide clear local visual indication of the status (open or closed) of
the supply contactor, consumption, last bill details.
Phase disconnection or neutral mode shall be adopted in case of the following:
• Overcurrent, or excess of current
• Preprogrammed tamper conditions
• Disconnect signal from the utility control center in such cases as unavailable balance for a prepaid
consumer
Load control limits shall be remotely programmable.
 The meter shall have provision for audio-enabled alarm for low balance (prepaid accounts), load in excess
of preset limit, and others.

Remote reconnection shall be enabled only via a push button if the meter is set by the MDMS in “ready
for reconnection” mode.

The meter shall be capable of automatically disconnecting supply when a decision to disconnect is made,
and reconnecting automatically when a decision to that effect is made.

The special event log shall record entries for up to 10 previous disconnections (reconnections of the
switching module), together with a time stamp and an indication of the switching module status.
Meters shall have self-discovery and self-registry functionality to allow the AMI system to detect and
register the meter within 60 minutes of meter connection and establishment of communication.

Meters shall have provision for the display of connect or disconnect indications:
• Status of relay (connected or disconnected) should be available on display as well as through
communication
• Connection and disconnection should also be logged as events. Up to 20 such events should be
recorded
It should be possible to program parameter limits or values remotely through a sufficiently adequate
security mechanism. Once programmed, the parameters can take effect at a certain date and time.
Meteorology conditions must remain intact and shall not be upgradable from remote locations.
The meter shall support the reading of meter data at a predefined frequency, and should be configurable.
A facility for on-demand meter reading shall also be available.

The meter shall have RTC with a 20-year calendar programmed in memory and provision for time
synchronization.

riff and TOU Programming

Tariff and TOU implementation shall be remotely configurable and robust despite communication
failures.

Total energy register of kWh data shall be stored separately for each tariff.

At least four seasons shall be definable and configurable. Only one season and one tariff shall be in
operation at any time.
A season shall be defined by month and day, shall be in effect starting at 00:00 hours of the defined day
every year, and shall be superseded when the next season becomes effective. Holidays, weekdays, and
special marked days shall be definable during a season.
The meter shall continuously display the current active tariff register, regardless of its display mode.
 Local tariff register management shall be realized via an internal clock. Tariff programmed shall
anticipate the possibility of defining
7 different days, and 1 or 2 different days for holidays. Tariffs may be changed up to three times a day.

eter Data Storage

All meters shall use nonvolatile memory for storing and retaining meter data.

Data storage shall be sufficient to provide redundancy for at least 65 days for at least two channels of
data, at a specified monthly energy consumption (under different TOUs, import or export with critical and
noncritical loads) and in response to maximum demand for a year’s worth of load profile data over 1
month.
Meter data shall be retained without loss or degradation, even without power.

Meter data shall be manually retrievable without the need to remove the meter cover.

The meter shall be capable of retaining data stored in its memory all the time, even under loss of power. It
shall be possible to query historical readings manually and locally, and to download the same for analysis.
Meter data shall be manually retrievable without the need to remove the meter cover.
Meters shall record and signal metering integrity violations (terminal cover opening, parameter change,
strong magnetic field impact on the meter, and others). For each of the indicated events, the event log
shall record with a time stamp when this event occurred.
ent Log
The meter shall memorize events related to metering, adjustment, and handling, and record these in the
special memory registers (organized on the FIFO principle).
A record in the memory shall be generated for each event, specifying the type of event, time stamp, and
meter status when the event occurred. The meter shall register up to 200 events.
Event coding, as well as the types of events entered in the event log, should be organized under the
recommendations given in DLMS or COSEM. The event log is not erasable through external
intervention.
Events recorded in special event logs (events related to electricity quality, metering integrity,
consumption management, and others) are not recorded in the standard event log.
The number and total duration of short-term supply interruptions (shorter than 3 minutes) and long-term
supply interruptions (longer than 3 minutes) shall be recorded in the electricity quality log.
Supply interruptions (short and long term) shall be configurable.

lf-Check
The purpose of this function is to verify the proper execution of basic meter functions. The meter
performs a self-check during network connection (after every supply restoration, or power up).

The meter shall perform a self-check during the application of new firmware. The results of this self-
check will be available on the meter (locally and remotely). New firmware upgrades in the meter may be
done locally or remotely.
eter Firmware Upgrade
 The meter shall support firmware upgrades. The upgrades should not alter in any way the metering
characteristics (metrology) of the meter or data in the meter memory (metering data, status, and others).
Configuration parameters or operational parameters of the meter for all these data shall remain unchanged
even after the firmware upgrade.
The meter, after receiving new firmware, will verify its compatibility; if that verification does not end
positively, the new firmware will
not be executed. The meter will record the time and date of receipt of new firmware, as well as the time
and date of new firmware application, in the event log.
The meter is connected via its local electrical interface with the manual terminal or laptop containing
corresponding software for the installation of the new firmware on the meter. This process is executed in
a way that will not affect the data in the meter at any time. If for some reason the firmware upgrade is not
completed successfully, there is a procedure for restoring automatically the original (previous version)
firmware. The event log shall record all actions.
The meter is connected via its local external communication module with the corresponding software
module in the head-end system for the installation of the new firmware on the meter. The HES role may
be taken over by the concentrators. This process is executed in a way that will not affect the data in the
meter at any time. If for some reason the firmware upgrade is not completed successfully, there
is a procedure for restoring automatically the original (previous version) firmware. The event log shall
record all actions. The meter shall be capable of remotely upgrading the firmware if the NEA wants to
enable or disable prepayment functionality.

antities to Be Measured, Monitored, and Stored in Memory

The meter shall be capable of measuring, monitoring, and storing in memory electrical quantities for pre-
specified time periods for up to four time zones.
• Active energy: absolute cumulative kWh energy
• Reactive energy: cumulative kVArh lag with respect to active energy
• Apparent energy: cumulative absolute kVAh derived vector sum of reactive and active energy
• Maximum demand: highest active MD, kW demand established after last reset
• High resolution mode for kWh, kVAh, kVArh (lag)

The meter shall have three display modes:

• Mode 1 (main mode), for billing and tamper parameters
• Mode 2, for observation parameters like time-of-day zone energy consumption and MD
• Mode 3, for high precision energy readings, to enable accuracy testing onsite
The meter shall keep the following quantities recorded and memorized in its nonvolatile memory chip
forever, so that in the event of failure or damage of the meter, the last reading of billing quantities would
not be lost.
• Cumulative energy from the date of installation
• Cumulative kWh of energy supplied to the consumer
• Cumulative kVArh lag (with respect to export kWh) and Cumulative kVArh lead (with respect to
kWh), both separately with identification
• Cumulative kVAh energy derived from vector summation of active and reactive (lag only) energy
• MD for last power on.
• Billing parameters of 12 billing cycles shall be recorded in meter memory on FIFO principle.
 Every 15 minutes, meters should send value of cumulative energy consumption register value to the HES.

curity and Tampering

The meter shall verify its firmware at power on and prior to activation of the firmware. It shall provide
tampering protection against main and terminal cover removal, and allow magnetic field detection
monitoring.
For data security, locally accessed data must be protected through access verification, with at least three
access levels, and encryption of transferred data.

The first protection level is protection against unauthorized data reading via the optical port, and is
realized through a software package installed on the laptop, linking it to the meter and enabling data
transfer and reading.
The second level of protection is protection against unauthorized changes in meter parameter set, without
removing the terminal cover (violation of DISCOM seal). It is also realized through a software package
installed on the laptop, depending on the user type, as well as through password verification. It enables
the transfer of certain parameter changes to the meter. Parameters that can be changed at this level are
programmed time and tariff.
The third protection level is protection against unauthorized change in the meter firmware and other
meter parameters, as well as against local disconnection or connection of the switching module. These
protective actions on the meter are enabled after the removal of
the terminal cover (violation of DISCOM seal), but only after verification of the user type of software
package installed on the handheld device or laptop, as well as the meter password.
Up to 200 events (occurrence and restoration) of all types of tampering, with the date and time, will be
available in the meter memory, on first-in-first-out basis. Compartments, if any, must be clearly indicated
in the bid. Snapshots of voltage, current, power factor and energy (kWh) readings (numerical values), as
well as the date and time of logging of the occurrence and restoration of tamper events, should be
available.
The tamper events shall be recorded in sequence, on FIFO or rollover basis. The total tamper count to be
displayed and
memorized shall increase with occurrence (not restoration) of tamper events. The total tamper count shall
also be provided on the meter display as well as at the BCS end. “Cover open” and magnetic interference
events shall be communicated back to the base computer center as and when they occur. These tamper
events shall be sent as an alarm to the base computer center, which shall store the same in its database.

The tamper persistence time for logging or registration of an occurrence and tamper restoration shall
conform to IEC standards.
aling of the Meter
Reliable sealing shall be provided to make the meter tamperproof and to prevent fiddling or tampering by
unauthorized persons. For this purpose, there shall be at least two seals on the front of the meter, two on
the meter terminal cover, one on the communication port, and one on the MD reset button (if that button
is provided).
 The bidder shall provide two polycarbonate plastic seals on the body of each meter before dispatching the
meter. The seals shall have the embossed bidder’s logo and the six-digit seal serial number on one side
and “NEA” and the seal serial number on the other.

In addition to the two polycarbonate plastic seals, two other tamper-proof void seals shall be provided on
the meter body to seal both side covers.

• The seal should be digitally printed on white VOID film using nondestructive ink and thermal resin
ribbon technology
• The seal should be waterproof and should withstand all weather conditions. The seal should have an
adhesive of sufficient strength to prevent peeling off under extreme temperature and environmental
conditions.
• The seal, of the sticker type, should be applied on both sides of the meter at the connection between the
body and the box
• If someone lifts the seal, the VOID mark should be transferred onto the meter, and if the seal is put
back, the VOID mark should be readable on the surface of the seal
• The disturbed portion of the seal should glow under UV light if the seal is disturbed at any part
• Bar codes of serial numbers should be printed on the seals and the bar codes should be readable with a
bar code scanner
• The seals should have continuous variable serial numbers along with security codes with the last three
digits of serial numbers printed in black, and the same serial numbers along with code of serial numbers
will also be printed in a vertical semicircular shape and should be visible only under ultraviolet (UV) light
• Two security cuts should be made on the seal on both sides, and if someone tries to lift the seal it
should tear off from the security cuts. The security cuts should be made with a computer- controlled
plotter, which should make the security cuts at the same position on each seal.
• If someone tries to remove the seal by applying heat, this should interfere with the printing, and the
shape of the seal should change if more heat is applied

splay of Meter Values

The measured value(s) shall be displayed on a seven-segment, seven-digit liquid-crystal-display LED or
LCD display with backlight unit, having a minimum character height of 8 mm. Good quality display shall
be used to enable correct reading even from a distance.
Data shall be stored in nonvolatile memory for at least 10 years, even in unpowered condition.

It shall be possible to easily identify the displayed parameters through symbols or legend on the meter
display itself.
If multiple values are presented on a single display, it shall be possible to identify each displayed value or
parameter through a separate symbol or legend to be made available on the display itself.

Persistence time for each parameter shall be 10 seconds.

The serial number of the meter shall be provided, preferably on the display or on the meter nameplate. It
shall also be programmed into the meter memory, for identification through the CMRI or meter- reading
printout.
aximum Demand
 The meter shall monitor and calculate the average demand in kW/kVA, established during prespecified
integration period, set and record or display the maximum registered value, and store the same along with
date and time of occurrence in the meter memo. The integration period shall be 15 minutes and it should
be programmable with due authentication. The MD shall also be available for TOD.

Automatic resetting at the end of a prespecified monthly date

(e.g., 00:00 hours on the first day of every month) shall be possible.

Provision for revising the resetting cycle for modifying the date and time of automatic resetting through
the base computer service center or via handheld meter reading instrument, only after using a protected
password authenticated through the BCS, should be available.
Provision for manual resetting of the monthly maximum demand with adequate sealing arrangement must
be made.

In all MD resets, numbers of counts shall increase on every reset.

ad Survey Capability
The meter shall record load survey data for at least 65 days for average voltage, average current, average
power factor, for all phases, and kWh reading and kVArh lag reading, kVAh reading, average demand in
kW with integration period of 15 minutes. It shall be possible to select either demand or energy view at
the system end.
The load survey data shall be available in the form of bar charts as well as spreadsheets. The system shall
be able to give complete load survey data, both in numeric and in graphic form. The load survey data
must be available in first-in-first-out mode. The load survey data are only for power on days. For billing,
last-12-days reset backup is required for various energy and demand parameters with TOU and average
power factor.
Criticality

Vital

Vital

Vital

Vital

Vital

Essential

Vital

Vital

Vital

Vital
 Vital

Essential

Vital

Vital

Vital

Essential

Vital

Vital
Essential

Vital

Essential

Essential

Vital

Essential

Vital

Vital

Vital

Vital

Vital

Vital

Essential

Vital
Essential

Vital

Vital

Vital

Vital

Vital

Vital

Vital

Essential

Vital

Vital

Essential

Vital

Vital
 Vital

Vital

Vital

Optional

Vital

Essential

Vital
 Vital

Vital

Vital

Vital

Vital

Vital

Vital

Vital

Vital

Essential
Essential

Essential

Essential

Essential

Vital

Essential

Essential

Essential

Vital
 Vital

Vital

Vital

Essential

Vital

Vital

Essential