Section 6.

Project Requirements 212

6 Analytics and Reports

6.1 Analytics including Energy Audit

The MDM shall have analysis capability based on configurable business rules including but not limited
to the following:
a) Energy Audit: Perform DT/Feeder/ Sub-Division/ Division/ Circle wise energy audit for
configurable period. These energy audit reports shall clearly bring out the technical and commercial
losses through detailed analysis of supply side energy data and corresponding aggregated
consumption data of connected consumers. In this analysis it must factor in data of energy export
from net-metered consumers. The automated audit should include but not limited to:
I. A daily automatic feeder loss (Feeder Head reading minus summation of all DT meters
readings)
II. Automatic LT Energy loss (DT meter reading minus summation of readings of all those
consumer meters served by the selected DT) would be reported
III. Billing and collection efficiency
IV. Identify the top [X] best as well as worst performing feeders and DTs
b) Display consumption/load profiles by configurable period (15/30 min, hour, day, month, year etc.)
day type (weekday, weekend, holiday, festival wise etc.) and by tariff, consumer type (hospitals,
schools, govt. offices, multiplexes, commercial, residential, industrial etc.), or any user specified
collection of meters.
c) Generate peak & off-peak load patterns by aggregating all loads of consumer group/consumer
type/DT/Feeder over configurable period/day type.
d) Perform load analysis for different groups and categories of consumers in different weather
conditions.
e) Ability to provide the data to load forecasting, load research or demand response applications (based
on use cases provided in Annexure H) and perform error management such as missed reads and
intermittent meter reads before sharing data with load forecasting, load research or demand response
f) Ability to configure the system to effectively visualize consumption trends, identify unusualpatterns,
and visualize load analysis to understand which assets are being over utilized.
g) Analyzing data to identify new patterns of usage, Setting fraud alert / transformer overload alerts /
demand supply gap alert etc.
h) Ability to receive and store outage and restoration event data from Smart Meters and outage systems
and to log all such events for analysis and also support calculation of compensation payments for
sustained outages. Five reliability indices shall be calculated,
i. System Average Interruption Duration Index (SAIDI), which is sum of all consumer
interruption durations in a given period over total number of consumers served.
ii. System Average Interruption Frequency Index (SAIFI), which is the total number of
sustained interruptions in a given period over total number of consumers served.

212
Section 6. Project Requirements 213

iii. Consumer Average Interruption Duration Index (CAIDI), which is sum of all consumer
interruption durations in a given period over the total number of sustained interruptions in
that given period
iv. Consumer Average Interruption Frequency Index (CAIFI), which is the total number of
sustained interruptions in a given period over the total number of distinct consumers
interrupted in that given period
v. Momentary Average Interruption Frequency Index (MAIFI), which is the total number of
consumer interruptions less than the defined time (1 or 5 minutes) over the total number of
consumers served
These reliability indices shall be calculated for each month, for individual feeders and aggregated
annually for the whole utility. The source data for outage shall be last gasp / first breath messages
from DT/Feeder level meters or the power outage/restoration events logged by these meters. These
computations shall be independent of similar computations made by any OMS application.
i) Ability to alerts on DT/ Feeder level overvoltage & back-to normal event and under-voltage and
back-to-normal events. Based on these alerts the system should calculate the duration in which the
DT/Feeder remained outside the nominal zone of defined voltage. Similar calculations should be
allowed for power factor and current unbalance.
j) Identify & visualize poor performing assets such as feeder/DT on multiple criteria such as energy
losses, outage duration etc. through appropriate colour coding depending on severity thresholds.
k) Analyze data of net-metering consumers to identify patterns of energy export to grid on
hourly/weekly/monthly/yearly basis.
6.2 Reporting Function

The Report function shall enable the Utility to deliver reports in standard digital format such as PDF,
Excel, etc. All queries for report generation shall be made through user driven drop down menu through
GUI of Utility user interface (refer to Clause 2.5.1 of this Section for more details). The AMISP shall
provide example queries to support internal report generation needs. The GUI shall haveprovisions to
set up or change report delivery to configurable email addresses, network file directories, ftp sites or
printer systems without modifying source program code and without any proprietary language skills.
6.2.1 The MDM shall generate following reports (an indicative list only). Utility may request for
additional reports as well during the contract period.
i. Daily data collection report
ii. Usage exceptions
iii. VEE validation failures
iv. Missing interval Read date and times (on hourly, daily, weekly & monthly basis) and their
trends
v. Physical meter events (install, remove, connect, disconnect) & meter reset report
vi. Meter flags
vii. Meter inventory
viii. Defective meters
ix. AMI performance measurements

213
Section 6. Project Requirements 214

x. Threshold exception
xi. DT condition monitoring
xii. MIS reports and analytical reports including but not limited to following:
1) Payment collection summary and details in a day/week/month/year or as per user
selectable period and trends
2) Number / list of disconnected consumers due to inadequate prepaid account balance
3) Prepaid consumers running low on account balance
4) Connected consumers
5) Critical notifications sent to consumers
6) Revenue analytics as per consumption pattern of consumers (in terms of money and
energy units). This shall also include automatic compensation payments by Utility to
consumers for sustained outages, if implemented
7) Data-driven Analytics reports by leveraging AI/ML based technologies
6.2.2 Following high level reports for Utility Management shall be generated automatically at specified
frequencies to help management with business decisions. <Below is an example of reports0 that may
be generated. These reports should be defined and agreed by the utility

Category Report Frequency

Energy Audit Report (DT/ Feeder / Sub-
Division/ Division/ Circle wise) in contiguous
electrical locations:
A daily automatic feeder loss report
(Feeder Head reading minus summation of Daily, Monthly and User
all DT meters readings) Selectable Time Period with
Energy Audit Automatic LT Energy loss report (DT configurable near real time alerts
meter reading minus summation of for exceeding defined loss
readings of all those consumer meters threshold
served by the selected DT) would be
reported
Billing and collection efficiency
Identify the top [X] best as well as worst
performing feeders and DTs
SAIFI and SAIDI; CAIFI and CAIDI; MAIFI
of the feeder(s) and connected consumers
Daily, Monthly and User
Reliability Indices would be tracked to measure the improvement
Selectable Time Period
in the same overtime and establishing
reference levels
Daily, Monthly and User
DT Loading (Categorize DT as overloaded,
Selectable Time Period with
optimally loaded, near optimal, under loaded)
configurable near real time alerts
Load Management
Load recording (Consumers): Actual Daily, Monthly and User
consumption recorded higher than the Selectable Time Period with
sanctioned load identifying the top [X] configurable near real time alerts

0 These reports shall be generated provided the corresponding DT/ Feeder data is available as part of the AMI system
being installed.

214
Section 6. Project Requirements 215

Category Report Frequency

consumers
Load Management Report (Identify top Monthly and User Selectable
overloaded DTs) and load rise trend Time Period
Daily, Monthly and User
Voltage Deviation Index and Frequency
Selectable Time Period with
Deviation Index (DT/ Feeder)
configurable near real time alerts
Daily, Monthly and User
POWER QUALITY Low Power Factor (DT/ Feeder) Selectable Time Period with
configurable near real time alerts
Daily, Monthly and User
Meter Current Unbalance (DT/ Feeder) Selectable Time Period with
configurable near real time alerts

Tamper Alert: as per IS 15959 Part 2

Comparison Consumption (system used to Daily, Monthly and User

Loss Analytics detect & track theft suspects) Selectable Time Period with
configurable near real time alerts
Consumption lower than the expected pattern
(pattern of previous year applied to the
monthly average) or monthly average
Summary report on top [X] high loss DTs/
Feeders, top overloaded DTs/ Feeders, Top
Management feeders/ DTs with most outages (number and
<Monthly and User Selectable
Summary Report duration), Top feeders with most power
Time Period>
(Dashboards) quality issues (over voltage, under voltage,
current unbalance, out of band frequency),
DTs with high failure rate

6.2.3 The utility interface should have ability to generate reports on critical and non-critical information
received from the HES to the MDM as per Clause 2.3.3 of this Section.
6.2.4 The utility interface shall have feature to generate report related to SLAs being mentioned in
Clause 7.7 of this Section.
6.2.5 Ability to generate various analytics reports as per Clause 6.1 of this Section.
6.2.6 AMISP shall submit a detailed report on data being shared as per Clause 2.7.8 on a yearly basis.
AMISP shall submit detailed report on any exception in general data sharing on monthly basis.
Further, AMISP shall also submit a detailed report for any other time period as requested by utility

215
 Section 6. Project Requirements 216

7 Operation and Maintenance

7.1 Scope and period

The operation, maintenance, and support services start after the successful completion of the operational
go-live of the system as per Clause 9.6 of this Section. Operation, maintenance and support services
shall extend up to end of Total Meter-months from Operational Go-Live. The scope of work under
operation and maintenance services shall include,
a) Comprehensive maintenance of all the software (including licensing, version upgrades if any and
annual technical support cost)
b) Comprehensive maintenance of all hardware at the Operation and Monitoring Centre, along with
field devices (like Smart Meters, DCUs etc.) provided by AMISP under the project
c) Comprehensive maintenance of all equipment under leased service like cloud data centre, MPLS
band width etc.
d) Comprehensive maintenance of NAN / WAN communication infra between field devices and the
cloud data centre
e) Day to day operations of the AMI system under supervision and authority of the Utility. These
shall include among others,
i. New meter installation
ii. Changeover of consumer meters from post-paid to prepaid mode and vice versa
iii. Firmware update of remote devices (Meters and DCUs) as required
iv. Update of tariff slabs
v. Ensuring completion of recharge cycle of prepaid consumer meters
vi. Connecting, disconnecting or reducing licensed load under approval from the
Utility
vii. Initiating resolution of consumer trouble tickets raised by utility CCS
viii. Ensuring availability of BP, LP, interval data and event notifications from meters in time
schedules as agreed with the utility
ix. Ensuring scheduled completion of billing determinant calculations
x. Ensuring daily reports from the AMI system as per agreed list, are made available to utility
xi. Ensuring Consumer Portal is kept updated
xii. Ensuring smooth data traffic between the MDM and utility systems
xiii. Patch management of AMI applications at cloud data centre
xiv. Provide backup data to support SLA and AMISP invoicing
xv. Carry out performance checks of various functions as per agreed schedule or on demand

As part of their Operation and Maintenance responsibilities, the AMISP shall develop a compendium
of Operation and Maintenance Manuals covering the areas mentioned in serial number e), Clause 7.1
of this Section. These manuals shall be kept updated as often as necessary to reflect best practices being
employed in the project.

The AMISP is to hand hold the Utility team to take over operation, maintenance and support services
after completion of contract period. The project/ system devices should allow their functionalities to
be upgraded without disruption to the existing functionalities by downloading new software and
configuration information.

216