Section 6.

Project Requirements 163

troubleshooting purposes. Historical logs of monitored profiles shall be available analysis

through standard reporting tool.
e) If GIS is enabled, then topology, location (lat./long) and status of all network nodes shall
be visible on GIS map.
2.2.3 Network Protection & Security
The AMI Network shall have adequate cyber security measures not limited to the measures as
described below. The network security would be extended to all the interfaces also.
Secure Access Controls: The system shall include mechanisms for defining and controlling user
access to the applications environment. Best practices from enterprise security including password
strength, password aging, password history, reuse prevention etc. must be followed foraccess
control.
Authorization Controls: A least-privilege concept such that users are only allowed to use or
access functions for which they have been given authorization shall be available.
Logging: Logs must be maintained for all attempts to log on (both successful and unsuccessful),
any privilege change requests (both successful and unsuccessful), user actions affecting security
(such as password changes), attempts to perform actions not authorized by the authorization
controls, all configuration changes etc. Additionally, the access to such logs must be controlled
in accordance with the least-privilege concept mentioned above, so that entries may not be deleted,
accidentally or maliciously.
The overall cyber security policy and implementation shall account for:
a) Prevent unauthorized users from reading or writing data or files, executing programs or
performing operations without appropriate privileges.
b) Document all user sign on procedure
c) Record all network traffic for detecting unauthorized activity, unusual activity and attempts to
defeat system security (AMISP to propose and document what constitutes normal
activity/traffic)
d) A user authentication scheme consisting of at least a user identification and password shall
be required for the user to request a connection to any network node.
e) GUI to provide role-based access based on user identity and user role. Shall have following
types of users:
i. Administrator
ii. Operator
iii. Field staff
iv. Viewer/Guest
2.2.4 Communication Network Elements
Following sections provide detail on both DCU based communication network and router-based
RF mesh network. The AMISP shall select relevant parts as applicable for designing and
establishing communication infrastructure. The network shall be horizontally and vertically
scalable to accommodate future meter installations. <Utility to define the scalability level required
for the network>. The network elements may be comprised of the following.

163
Section 6. Project Requirements 164

2.2.4.1 Data Concentrator Unit (DCU) based Communication Network (<to be kept as redundant item
if required, otherwise the entire section is to be deleted>)
The Data Concentrator Unit is a gateway for communication of data between the Smart Meters
and the HES. The Data Concentrator Unit receives information from the Smart Meter on a
scheduled / need basis and passes it on to HES / MDM.
The DCU provides the central link between Smart Meters and HES, enabling
continuous/periodic meter-read and control. DCU shall exchange data from Smart Meters on RF
/ PLCC communication and with HES on WAN.
2.2.4.1.1 Hardware & Power Supply of DCU
a) Enclosure/box of DCU shall be IP65 or better compliant. A suitable mounting
arrangement required for DCU installation shall also be provided.
b) A suitable and optimum power supply shall be provided keeping in view that even in
case of outage in one or two phases, DCU can be powered. DCU should be capable of
withstanding surges & voltage spikes of 6 kV. Power supply shall be terminated on
suitable sized Miniature Circuit Breaker (MCB) to facilitate isolation during on-site
maintenance.
c) DCU shall have battery with backup for 1(one) hour for normal meter reading, to push
tamper event, carry out on demand reading and the network health status/ connectivity
continuity & check. DCU should have the suitable feature to send power outage and
restoration message to the HES.
d) DCU shall have built-in Real Time Clock (RTC) with separate battery backup. It shall
have self- diagnostic feature for RTC, memory, battery, communication module, etc.
2.2.4.1.2 Configuration, Functionality & Interface of DCU
DCU shall have following configuration functionalities / tools:
a) Configuring the communication with underlying nodes/meters.
b) Communication of data from the field devices and push the data at configured intervals
to the HES. It should also support the HES in pulling data from the field devices/meters.
The data acquisition (Push/Pull) frequency shall be configurable. DCUshall be capable
to prioritize control commands.
c) DCU shall ensure a secure communication to HES and shall have internal memory for
storing interval data for at least 5 (five) days. This storage shall be in non-volatile
memory as opposed to battery backed memory.
d) DCU shall support on demand read and ping of individual/group of meters.
e) It shall support IPv6 network addressing.
f) DCU shall push events such as tamper, power off etc. to HES immediately on
occurrence/receipt from field devices/meters.
g) The equipment shall be weatherproof, dustproof and constructed for outdoor installation
on poles (minimum rating: IP65). A suitable mounting provision shall be made for the
equipment.

164
Section 6. Project Requirements 165

h) Enclosure: Provision for security sealing shall be provided and in case the gasket of
the cover is used for protection against moisture, dust and insects, the gasket shall be
made of weather and aging resistant material.
i) The list of standards followed in all the devices/equipment used in communication
network shall be furnished
j) The communication network shall have dynamic & self-healing capability. If one of the
communication elements fails, then nodes connecting to that element shall switch to
best available element for communication of data to HES.

2.2.4.1.3 DCU Communication

a) The DCU shall ensure the appropriate backhaul for secure transfer of data to HES either
via cellular or Fiber Optic communication. In case of cellular backhaul, it shall support
SIM card / e-SIM with dynamic/static IP as the architecture demands from anyservice
provider. It shall have Wide Area Network (WAN) connectivity to the HES through
suitable means. Best available link shall be used to connect to HES.
b) DCU shall be able to communicate with meters through a secured, standard
communication protocol between meter and DCU.
c) DCU shall periodically monitor meter reads/downstream commands and shall retry and
reconnect in case of failed events/reads.
d) It shall push events such as tamper, power off etc. to HES immediately on
occurrence/receipt from field devices/meters. DCU shall be able to acquire and send
data to HES for full capacity (as per designed for no. of meters/field devices) to ensure
the performance level. Full capacity of DCU is required to be indicated in the offer.
e) On restoration of power supply, DCU shall establish communication with underlying
devices as well as upstream application automatically.
f) DCU shall be able to communicate with the nearest meters.
g) Remote firmware upgrade: The DCU shall support remote firmware upgrades as well
as remote configuration from the Network Operation cum Monitoring Centre (NOMC)
h) DCU shall facilitate recording of minimum of the following events at HES (for 7
days):
i. No of packet failures
ii. Retry attempts
iii. Missed periodic readings
iv. Failure to connect
v. Tamper events

2.2.4.2 Gateway/ Router/ Access Point based RF Mesh Network

In this type of communication network, different network nodes including end points (Smart
Meters) shall interconnect with each other using RF mesh network and they shall communicate
with nearby gateways/ routers to transfer the data to access points. If any gateways/ routers/

165
Section 6. Project Requirements 166

repeaters/ access points fail, then nodes connected on that device shall automatically
reconfigure the mesh with available nearby nodes.
2.2.4.2.1 General Requirement of RF Mesh Network:
a) The communication network shall have dynamic & self-healing capability. If one of the
communication elements such as gateways/ routers/ access points fails, then nodes
connecting to that element shall switch to best available element for communication of
data to HES.
b) It shall support IPv6 network addressing.
c) Each node shall keep a track of best available nearby nodes or access points.
d) The communication network equipment shall use Unlicensed or Licensed frequency
band as permitted by WPC/Statutory Bodies as applicable.
e) All the communication network equipment shall be as per WPC guidelines, Government
of India for operation in licensed / license free frequency band.
f) Suitable NMS shall be available to monitor the performance of the communication
network round the clock. The NMS shall provide viewing of all the networkingelements
deployed at site and enable configuration, parameterization of the networkingdevices
and the nodes.
g) It shall support remote firmware upgrading
h) It shall be secure enough to avoid all cyber threats
i) The communication network shall ensure secure communication of data to HES.
j) The equipment shall be weatherproof, dustproof and constructed for outdoor installation
on poles (minimum rating: IP65). A suitable mounting provision shall be made for the
equipment.
k) The list of standards followed in all the devices/equipment used in communication
network shall be furnished.
l) Gateway/ Router/ Access Point shall have battery with backup for 1(one) hour for
normal meter reading, to push tamper event, carry out on demand reading and the
network health status/ connectivity continuity & check etc. during battery operations
also. It should have the suitable feature to send power outage and restoration message
to the HES even during battery back-up.
2.2.4.2.2 Configuration, Functionality & Interface
Access points shall have following configuration functionalities:
a) It shall be able to configure the communication with underlying nodes/end points.
b) It shall support on demand read and ping of individual/group of meters.
c) It shall push events such as tamper, power off etc. to HES immediately on
occurrence/receipt from field devices/meters.
d) It shall have Wide Area Network (WAN) connectivity to the HES through suitable
means.

166
Section 6. Project Requirements 167

e) It shall communicate with gateways/ routers/ nodes/ end points/ access points on RF
mesh network (Unlicensed or Licensed frequency band as permitted by WPC/Statutory
Bodies in country of deployment as applicable).
f) It shall periodically monitor meter reads/downstream commands and shall retry and
reconnect in case of failed events/reads.
g) After power Interruption, on restoration of power supply, it shall establish
communication with underlying devices as well as upstream application (HES)
automatically.
h) Access point shall facilitate recording of minimum of the following events at HES (for
seven (7) days):
i. No of lost packets
ii. Retry attempts
iii. Missed periodic reading
iv. Failure to connect
v. Tamper events
i) It shall be capable to handle interval data of suitable nos. of any type of Smart Meter.
Access point shall be able to acquire and send data to HES for full capacity (No. of
meters/field devices it is designed for) within a suitable time period to achieve the
performance level. Full capacity of access point is required to be indicated in the offer.
j) Gateway / Router / Access point shall support remote firmware upgrades as well as
remote configuration from the Network Operation cum Monitoring Centre.
k) The Gateway / Router / Access Points shall have provision to maintain the time and
date information and shall always be in Time synchronization to the HES server via
NTP to sub second accuracy. The Gateway / Router / Access Points shall support time
distribution to each Mesh Node.
2.3 Head End System (HES)
The main objective of HES is to acquire meter data automatically avoiding any human intervention and
monitor parameters acquired from meters.
The AMISP shall provide a HES which is suitable to support the collection and storage of data as per
performance level for a defined no. of Smart Meters with facility of future expansion as per the
requirement specified in this document.
<NOTE: The no of Smart Meters/future expansion may be provided by utility as per their requirement>
HES shall be responsible for discovery of all Smart Meters once deployed in the field, the periodic
collection of all meter data as well as the processing of all alarms and commands such as
connect/disconnect for those meters.
HES would perform all the requisite functions as per the defined functionalities of AMI and it is the
responsibility of the AMISP to supply the requisite software and hardware to achieve the defined
functionalities of AMI. HES shall ensure data integrity checks, for example, checksum, time check,
pulse, overflow, etc. on all metered data.
HES shall be developed on open platform based on distributed architecture for scalability without
degradation of the performance using additional hardware. The scalability shall ensure the ability to

167