Tender Specification No.

Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
d) NMS function should be able to collect and store monitoring profiles from End Points (NAN/WAN
modules) and network devices for performance evaluation, and troubleshooting purposes. Historical
logs of monitored profiles shall be available analysis through standard reporting tool.
If GIS is enabled, then topology, location (lat/long) and status of all network nodes shall be visible
on GIS map.

1.7. Integration with Utility’s Meter Data Management system (MDM)

Presently, Utility is in the process of developing its ownMeter Data Management System (MDMS) and AMISP
shall integrate its AMI system with the MDM. The details related to Discom MDM is given in Annexure-L.

MDM shall be operated by the representatives of discoms and AMISP will be part of the Command and Control
Center team so that AMISP is aware of the daily AMI operational activities. It shall be noted that AMISP shall
also act as adviser to the discom related to increasing the operational efficiency of the MDM.

The AMISP shall be responsible for proper data exchange among Smart meters, HES and other operational/
requisite software as part of fully functional AMI system including [utility’s] MDM and billing solution.

The HES shall generate MIS / Dashboard / Reports regarding numbers of meters read / unread on daily /
weekly/ monthly and AMISP has to ensure seamless integration with [utility’s] MDM and data available on MDM
will be the basis for the calculation of SLA.

In case,data is not available on MDM and reason is not attributed from HES level then after due approval
fromUtility, calculation of SLA will be done on the data available on HES.

In future, it would be AMISP’s responsibility to integrate new meter or any other application/ equipment as
decided by the Utility. AMISP shall be responsible to ensure connectivity from their cloud infrastructure (i.e.
where HES and other application hosted etc.) to other cloud infrastructure (where UtilityMeter Data management
Solution (MDM) hosted). This includes procurement of additional bandwidth / MPLS line etc. by the AMISP for
seamless integration of HES with [Utility’s] MDM solution.

In case the MDM is unable to perform thetasks as given in subsequent sections, the AMISP shall develop AMI
system to deliver the following tasks.

The key use cases to be enabled by AMISP are provided below. Please note that these are illustrative list of use
cases only and is not an exhaustive list. Further please note that all IS Standards shall be applicable.
Sr. Use Case Activity Description Source Destinatio Info Exchanged
1. Scheduled Meter Read Automatically from Consumer Premises
1.1 At scheduled frequency meter Meter HES Meter Number, reading, date
sends data to HES. Consumption & time, kW, kVA (with date
details including non-critical &time stamping), kWh
(fundamental, total, net
events will be in 15 min block
export), kVAh, PF, Non-
data, and data could be critical Event Code / Date
incremental to what was sent by
meter in preceding instance

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 78
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged
1.2 At scheduled frequency meter Meter HES Meter Number, reading, date
sends billing Data to HES & time, kW, kVA, (with date
&time stamping) kWh
(fundamental, total, net,
export), kVAh (fundamental,
total, net, export
(fundamental, total net
export), PF
1.3 Scheduled meter data reaches HES MDM Meter Number, reading
MDM date& time, kW,
kVA,kWh, kVAh, PF,
Noncritical Event Code /
Date (As above).
2. Remote Meter disconnection / reconnection
2.1 Meter re-connect / disconnect MDM HES Meter Number, group of
operation command meters, instruction to close
switch

2.2 Consumer meter re-connection / HES Meter Meter number, action

Disconnection (reconnect/ disconnect)

2.3 Connection Status Update Meter HES Meter Number, switch

status
2.4 Connection Status Update HES MDM Meter Number, group of
meters, switch status
3. Utility detects tampering at consumer site

3.1 High priority events captured by Meter HES Meter Number, event
Meter sent to HES as and when date & time (occurrences
occurred and restoration) with
snap shot values of
currents and voltages,
event Code /description

3.2 High priority events reach MDM HES MDM Meter Number, event
forfurther action. date & time(occurrences
and restoration) with
snap shot values of
currents and voltages,
event Code /description
3.3 Notify utility personnel for site MDM Email/SMS Consumer number,
Inspection Gateway Meter Number, Tamper
code, address
3.4 On analysis and detection of valid MDM HES Consumer number,
tamper event or malfunction, meter
connection is disconnected.
number, action to be
3.5 HES sends disconnect command HES Meter Meter Number, action
to meter (disconnect)

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 79
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged
3.6 Tamper event shared with CIS. MDM CIS / Billing Meter Number, event
Billing determinants are updated for Determinan date & t i m e , e v e n t
tamper invoicing ts C o d e /description

3.7 Meter re-connection order once MDM HES Meter number, action (re-
tamper issue is resolved connect)
3.8 HES sends re-connect command HES Meter Meter Number, action (re-
to meter connect)
4. Missed interval readings

4.1 On identifying missed interval, HES HES Meter Meter Number, from
will re-acquire data for the missing date & time, to date & time
period from meter (for which data is
missing)
4.2 On receiving data request command, Meter HES Meter Number, reading
meter will send data to HES date & time, kW, kVA,
kWh, kVAh

4.3 Missed Interval and Reads Data HES MDM Meter Number, readings
acquired by MDM with date & time

5. Consumer connection outage/restoration event

5.1 Outage/restore event recorded Meter HES Meter Number, Outage /

by meter is sent to HES as and restoration Date / Time,
when event occurs Power On or Off count
5.2 Outage / Restoration Notification HES MDM Meter Number, Outage /
restoration Date / Time,
Power On or Off count
5.3 Sharing Outage / Restoration MDM OMS/CIS- Meter Number, Outage /
Notification CRM restoration Date / Time,
Power On or Off count

5.4 Meter read request from OMS to OMS MDM Meter Number,
identify service outage / restoration HES

5.5 Meter responds to event poll from Meter HES Meter number, Status
HES (live/dead)

6. Remote firmware upgrades/ meter configuration changes

6.1 Remote firmware upgrade Meter Firmware

HES
6.2 Configuration Commands: Meter Meter number, tariff
Change tariff parameters, HES parameters, registers
Synchronizeclock, Registers reset status, event type and
(status, max, tampering, MD reset priority
date , billing date change, TOD
configuration, change in Meter
display parameters with sequence
setting

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 80
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged
6.3 Status update of Firmware / Meter
Configuration MDM

7. Load monitoring at demand side

7.1 When there is a load violation event Meter HES Meter Number, max
recorded in the meter, MDM demand, date & time
t h e information is sent to the CC of load violation

8. Time synchronization

8.1 Synchronising RTCs of meters / HES DCU/Meter Time Setting

DCUs/ACP
9. Metering network changes

9.1 Change / new installation in Meter / Meter / HES Network identification

DCU Network Hierarchy DCU info including DCUs
9.2 Change / new installation in Meter / HES MDM Network identification
DCU Network Hierarchy info including DCU
10. New consumer connection

10.1 Receive pre & post-paid new CIS-CRM MDM Consumer name,
consumer requests address. Connection
request etc.
10.2 Verify new consumer has paid as per Billing MDM Consumer connection
regulation request, Payment details
10.3 Generate meter installation order MDM CIS-CRM Consumer ID & details
/WFM
10.4 Receive meter installation report WFM MDM Meter number, DT no,
Feeder & reading
10.5 Requesting instant, MDM Meter Number, Reading
interval & events data from meters Meter date & time,
readingparams (kWh,
kVAh, kW etc.)
10.6 Acquire instant, interval / events data HES MDM Meter Number, Reading
from meter by HES which then date & ti m e, r eadi ng
reaches MDM system. params (kWh, kVAh, kW
etc.)
10.7 Once new meter remote read MDM Billing / CIS- Consumer ID,
verification is over, confirm new CRM Consumer address,
connection with other applications Meter Number, initial
reading etc.
11 Migrate post-paid consumer to prepaid mode (As per Requirement)

11.1 Receive migration request CIS-CRM MDM Migration request for

post-paid consumer with
profile

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 81
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged

11.2 Get billing attributes Billing MDM Billing attributes

11.3 Setup prepaid consumer profile in MDM Prepaid Prepaid consumer profile
prepaid engine. If no change in Engine
meter is required, skip next two
steps
11.4 Generate prepaid meter installation MDM CIS-CRM / Consumer ID & details
order if required WFM

11.5 Receive meter installation report WFM MDM Meter number, DT no,
Feeder & reading, date
of installation

11.6 Enable prepaid mode in meter Prepaid Engineering token

engine Meter

11.7 Receive activation confirmation HES MDM Activation status

11.8 Request instant, interval & events MDM Meter Number, Reading
data from meter Meter date & ti m e, r eadi ng
params (kWh, kVAh, kW
etc.)
11.9 Acquire instant, interval / events data HES MDM Meter Number, Reading
from meter by HES which then date & ti m e, r eadi ng
reaches MDM system. params (kWh, kVAh, kW
etc.)
11.10 Once meter remote read MDM Billing / CIS- Prepaid consumer profile
verification is over, share migration CRM
request completion detail with other
modules
12 Migrate prepaid consumer to post-paid mode

12.1 Receive migration request CIS-CRM MDM Migration request for

prepaid consumer with
profile

12.2 Request meter data MDM Meter Number,

Meter Consumer ID

12.3 Acquire instant, interval / events data HES MDM Meter Number, Reading
from meter by HES which then date & ti m e, r eadi ng
reaches MDM system. params (kWh, kVAh, kW
etc.) with balance credit

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 82
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged

12.4 Send meter disconnect command MDM

Meter

Disconnect status with

12.5 Receive connection status HES MDM
date and time stamping

12.6 Enable post-paid mode in meter MDM Engineering token

Meter

Receive activation of post-paid

12.7 HES MDM Activation Status
mode

12.8 Request instant, MDM Meter Number,

interval & events data from meter Meter Consumer ID

12.9 Acquire instant, interval / events data HES MDM Meter Number, Reading
from meter by HES which then date & ti m e, r eadi ng
reaches MDM system. params (kWh, kVAh, kW
etc.)
12.10 Once meter remote read MDM Billing / CIS- Post-paid consumer profile
verification is over, share migration CRM and meter data along
request completion detail with other with credit balance
modules
13. Consumer Registration in Consumer Portal/ App

13.1 Consumer clicks on new user on Portal/ MDM Request for registration
consumer portal/ App, provides App with RMN/email ID
RMN or email ID and submits data

13.2 Utility receives request for MDM Email/Mess OTP

registration and sends OTP after a ge
verification Gateway

Portal/
13.3 Consumer submits OTP MDM
App

13.4 Consumer receives registration MDM Email Login ID and default

detail Gateway password

Consumer submits first login Portal/

13.5 MDM
request App

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 83
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged

13.6 System seeks password change MDM Portal/ App

Consumer changes default Portal/

13.7 MDM
password App

14.
Consumer Access to Consumption, Billing & Profile Data

Portal/
14.1 Consumer logs in to Portal/ App MDM
App

14.2 Consumer Profile for Portal/ App CIS-CRM MDM Name, Account,
Address, Service Points,
App K Number

14.3 Consumption Data MDM Portal/ App Consumption profile

14.4 Billing (post-paid) / Credit Balance Billing Portal/ App Post-paid Billing history
(prepaid) MDM Current Bill, Prepaid
Recharge history

15 Prepaid Consumer Recharge

15.1 Consumer logs into Portal / Mobile Mob App UI Login

App / Portal

15.2 Consumer fills-in required detail in Payment Consumer ID, Recharge

UI and requests recharge Prepaid Gateway amount
App

15.3 Consumer selects payment Payment Net

method Gateway banking
/Credit Card
/ Wallet etc.
15.4 Consumer receives payment Payment Prepaid
acknowledgement Gateway

15.5 Calculate credit balance for prepaid Prepaid Consumer credit balance
consumer & update prepaid meter App r (virtual token)

15.6 Notify credit balance to consumer Prepaid Email/SMS Credit Balance

App Gateway

16. Post-Paid Consumer Bill Payment

16.1 Consumer logs into Portal / Mobile Mob App UI Login

App / Portal

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 84
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged
16.2 Consumer is presented with Billing Billing Portal/ Outstanding Bill
history and current outstanding Bill MDM

16.3 Consumer requests bill payment. Payment

Option to download bill Gateway

16.4 Consumer selects payment Payment Net

method Gateway banking
/Credit Card
/ Wallet etc.
16.5 Consumer receives payment Payment
acknowledgement Gateway Portal/

16.6 Payment acknowledgement Billing Email/SMS Payment

through email/SMS Gateway acknowledgement

17. Consumer Service Request

Portal/
17.1 Consumer logs in to Portal/ App MDM
App

17.2 Consumer requests for service UI MDM Service request

17.3 System assigns SRN & sends MDM Portal/

acknowledgement
Email/SMS
Gateway
17.4 System resolves request & updates MDM Portal/
consumer records
CIS/CRM

17.5 System closes SRN MDM Email/SMS

Gateway

18. Consumer Complaints

Portal/
18.1 Consumer logs into Portal/ App MDM
App

18.2 Consumer registers complaint UI MDM Specific complaint

18.3 System assigns CRN & sends MDM Portal/

acknowledgement
Email/SMS
Gateway

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 85
Tender Specification No. Discom/EZ/Pur/TS-1136 (E-TS-2021_PKVVC_139338_1)
Sr. Use Case Activity Description Source Destinatio Info Exchanged
18.4 System assigns resolution based MDM CIS / OMS
on nature of complaint / WFM

18.5 Target system reports completion of OMS / MDM

complaint WFM

18.6 System updates records and MDM CIS,

closes CRN Email/SMS
Gateway
19. Demand read of meters from consumer premises
19.1 Requesting instantaneous, interval, MDM Meter Number, Reading
load profile & events data from r date & ti m e, r eadi ng
meters params (kWh, kVAh, kW
etc.)
19.2 Acquire instant, interval, load profile MDM Meter Number, Reading
& events data from meters by HES HES date & ti m e, r eadi ng
which then reaches MDM system. params (kWh, kVAh, kW
etc.)
20. Staff User Access to Utility Portal
20.1 User logs in to Portal Portal MDM Login with appropriate
credentials

20.2 User selects available functions MDM

20.3 User logs out Portal MDM
UI

The AMISP shall specify and deliver an initial system that supports the collection and storage of data for
meeting the performance level for no of consumers/ Smart Meters as per Annexure-K with facility of future
expansion.

The MDM shall have the ability to selectively choose which data to be maintained and which to be purged or
archived [as per requirement of Utility (user selectable)].

HES shall preferably be interfaced with MDM on standard interfaces and the data exchange models and
interfaces shall comply with CIM / XML / IEC 61968 or any other open standard. The solution shall be Service
Oriented Architecture (SOA) enabled.

HES shall export all meter data to MDM and pass control commands from MDM. HES should conform to IEC
61968-9 as well as support CIM 2.0 / MultiSpeak v3.0 standards. It may use any other standard interfaces as
outlined in the approach paper, submitted as part of project implementation plan, for integrating with the MDM.
In case, utility has implemented any Service Oriented Architecture (SOA)/ Enterprise Service Bus (ESB)
architecture, the data exchange to and from HES shall be through this ESB. The details of its ESB is provided in
Annexure F.

The data collected by the Network Management function of the HES shall be integrated with overall Data Centre
level NMS module for easy monitoring, analysis and reporting.

Contract agreement for Appointment of Advanced Metering Infrastructure Service Provider (AMISP) for Smart Metering on Design-Build
Finance-Own-Operate-Transfer (DBFOOT) basis on Hybrid OPEX Model
Utility – MPPoKVVCL, Jabalpur 86