Download Category: Meter Reading

ISSGC Potential Categories and Scenarios
Note: This document will be updated with stakeholder proposed scenarios as they are received.
Page 1 of 36
ISSGC Potential Categories and Scenarios
Category: Meter Reading
One of the major concepts behind Advanced Metering Infrastructure (AMI) is the ability to automatically
and remotely capture energy data from the customer’s premise. The automatic capture of energy data can
be performed on-demand or as scheduled by the systems. The energy data captured through the
advanced metering infrastructure will provide utilities and third parties with more information, which in turn
will allow them to perform better analyses of usage patterns. Also, customers will have the ability to
download the data and perform additional analysis. In addition to capturing and analyzing the energy data,
this use case also focuses on the management in capturing the energy data and the handling of
exceptions (that is, missing energy data).
Scenario: Standard Meter Reading
Included as part of the ‘AMI’ category.
Proposed
This scenario deals with the capture of energy data on the default schedule. Meters must be able to store
interval data for no less than 45 days and the AMI system is expected to capture interval data on at least a
nightly basis for all customers, (residential, commercial, industrial and third-party meters). The AMI Head
End is responsible for scheduling and capturing energy data from the AMI Meters and Devices.
Scenario: On Demand Meter Reading
Proposed
This scenario deals with capturing energy data on-demand. The system shall be capable of performing an
on-demand read of energy data for all customers and business partners (residential, commercial, and
industrial). An on-demand read can be requested from the call center.
Scenario: Automatically receive non-usage (event) messages
Scenario too generic to be useful.
This scenario deals with capturing and handling events raised by the meter. Non-energy data that the AMI
Meter or Device records include: power outage indications, meter removal indications, remote disconnects
and reconnects, tamper detection indicators, self test results, and so on. It is important to note that some
of these non-energy data events will be handled by other use cases. The Meter Data Management
System will receive this data on a daily basis and route it to the appropriate application.
Scenario: Meter Data Management
Proposed
This scenario assumes that additional validating, editing and estimating processes will be performed by
the billing system after initial meter reading validation is performed by the Meter Data Management
System. This scenario also assumes that the billing system will return the processed data including
possible aggregation for storage in the Meter Data Management System. The final functionality of the
Meter Data Management System and its relationship to the billing system has not been determined it this
point in time.
Page 2 of 36
ISSGC Potential Categories and Scenarios
Scenario: Data users successfully retrieve either raw or bill ready usage
This scenario deals with utility users retrieving meter data from the Meter Data Management System for
any utility business process. The data stored in the Meter Data Management System can be either raw
data downloaded from the meter or data that has been processed by the billing system.
Scenario: AMI Head-End manages the meter reading schedule
Assumptions and level of detail not
appropriate for ISSGC.
Level of detail not appropriate for ISSGC.
This scenario deals with both daily and more frequent meter reading schedules. It defines how the AMI
Head End receives AMI Meter or Device details and assigns them to a reading schedule. The AMI Head
End also performs analysis on meter schedule performance and determines how to optimize the process.
Scenario: Third Party Accesses AMI Data
This is a combination of the B1.2 and B1.5 sub-use cases. This scenario deals with enabling third parties
to view and download energy data. The third parties can be demand response aggregators, energy
retailers or third party utilities. The data could be provided through an on-demand request, bulk data (for
example, a whole year), or reading their own meters (sub-meters, resale customer meters, water meters,
and so on).
Scenario: Meter does not communicate remotely during default schedule read
These scenarios deal with meters not communicating. The scenarios do not assume that the meter or
communication system has failed, only that the meter data is not received in the Meter Data Management
System. The scenarios cover the actions that the system should perform in an attempt to restore
communications and retrieve the meter data. The scenarios make no assumption as to the AMI network
technology (wired or wireless) but do recognize that the selection of a specific technology will further
define the processes and requirements.
Scenario: Field Person retrieves data directly from AMI Meter/Device
Will consider third party data access in
Meter Data Management scenario and in
other scenarios as appropriate.
Part of the proposed ‘Meter Reading
Troubleshooting’ scenario.
Level of detail not appropriate for ISSGC.
This scenario deals with a field person capturing energy data directly from an AMI Meter or Device. It is
necessary for the utility to be able to retrieve data directly from the meter by utility personnel in the field
and the Meter Data Management System must be able to capture the meter data from a field or handheld
device.
Scenario: Meter Data Management System issues a communications trouble report for failure to
retrieve billing data
This scenario deals with the need for the Meter Data Management System to interface with the trouble
reporting and work order systems. The Meter Data Management System will be required to create a
trouble report when it continually fails to communicate with a meter. The amount of time before creating
the trouble report will depend on the selection of network technologies and operational experience.
Page 3 of 36
Part of the proposed ‘Meter Reading
Troubleshooting’ scenario.
ISSGC Potential Categories and Scenarios
Scenario: AMI Meter or Device does not respond to an on demand read
This scenario deals with the process for handling a failed on demand read request. The AMI Head End is
required to determine when an on demand request has failed and notify the requesting system or user.
Category: Utility remotely limits usage or connects and disconnects customer
A big advantage of the AMI system is the ability to remotely connect and disconnect Electric AMI Meters
(typically single phase and 200 amps), significantly reducing the field service orders related to meter
disconnections and reconnections. Possible reasons for connecting or disconnecting meters are:routine
move in and move out (improved customer service), lack of customer payment (credit and collections) or
due to a confirmed customer request (improved customer service), reconnection upon payment (credit and
collections), improved outage management processes, improved safety and security processes, and
improved access to utility facilities in secure areas.
Scenario: Meter Switch Disconnection
Part of the proposed ‘Meter Reading
Troubleshooting’ scenario.
Included as part of the ‘AMI’ category.
Proposed
A shut off, is the process of removing the association between the customer and a physical premise. The
customer can schedule a future disconnect date or request an immediate disconnect. The utility can
perform a physical disconnect remotely or perform a “soft” disconnect and monitor the electric AMI Meter
for unreasonable usage.
Scenario: Meter Switch Connection
Proposed
A turn on, is the process of associating the customer to a physical premise and activating the electric AMI
Meter if it has been physically disconnected. The customer can request an immediate connection, or can
schedule a future date for the connection.
Scenario: Meter Switch Disconnection for Non-Payment
Proposed
The utility can perform a physical disconnect on an AMI meter if the customer has failed to pay. The utility
will not disconnect a customer until all regulatory requirements and utility procedures relating to non-pay
disconnections have been met.
Scenario: Utility reconnects customer following credit and collection disconnect
The utility can remotely reconnect a customer following a non-pay disconnection. Once the utility has
received payment, the procedure is identical to a routine service connection.
Scenario: Field person performs local electric service connection/disconnection
Similar to standard connection scenario.
Differences not sufficient to warrant an
additional scenario.
Level of detail not appropriate for ISSGC.
A Field Person at the customer’s premise may perform a disconnection or reconnection using a Field
Device. The Field Device provides a means to authenticate and authorize the Field Person to the AMI
Meter and permit the electric service connection or disconnection. The utility must manage the interactions
between local disconnections and remote reconnections due to possible safety issues.
Page 4 of 36
ISSGC Potential Categories and Scenarios
Scenario: Utility limits customer’s electric service due to credit or collection causes
The utility can establish a demand or usage limit on a customer using the AMI Meter for non-payment. If
the customer exceeds their allowed limit, the AMI Meter disconnects the customer. This scenario provides
the utility an alternative to simply disconnecting non-payment customers.
Category: Utility detects tampering or theft at customer site
Tampering with a utility’s energy infrastructure and associated equipment is a very serious safety risk, not
only for authorized utility employees but for public safety in general. In addition, utilities are very concerned
when customers either use energy without authorization or outright steal it. There is also a large revenue
liability potential if tampering, unauthorized use of energy and theft remain undetected. Energy theft, such
as meter tampering, occurs daily and can go undetected for months, even years. Tampering can be as
simple as inverting the meter to more sophisticated methods such as installing other devices to disrupt
accuracy. With the availability of the new “Smart Meters” and an AMI network, most attempts to remove or
intrude into the internal parts of the meter, including inversion, can be logged by the meter and
communicated with the help of AMI network.
Scenario: Meter Removal
Load limiting scenario considered but not
proposed.
Included as part of the ‘AMI’ category.
Proposed
AMI Meter/Device is removed and re-installed with possibly a jumper or bypass device installed inside the
meter enclosure. Meter removal will be recorded by the meter and information sent to the MDMS. If the
AMI Meter/Device is removed and re-installed, the usage pattern of the meter shall be compared with the
historical usage pattern. If any discrepancy is found, a notification shall be created for a utility
representative or process to analyze the tampering event and take appropriate action (for example, to
create a service order to investigate).
Scenario: Meter is inverted
If the AMI Meter/Device detects inversion or if the meter is removed and re-installed, the usage pattern of
the meter shall be compared with the historical usage pattern. If any discrepancy is found, a notification
shall be created for a utility representative or process to analyze the tampering event and take appropriate
action (for example, to create a service order to investigate).
Scenario: Meter bypass detection at meter
Considered in the proposed ‘Meter
Removal’ scenario.
Proposed
This scenario details the need for the AMI system to provide a means to detect energy theft due to
customers bypassing the meter. The determination of a probable bypass will be performed by many
elements of the AMI system,
Page 5 of 36
ISSGC Potential Categories and Scenarios
Scenario: Physical tamper detection
If the AMI Meter/Device alerts that physical tampering may have occurred, the usage pattern of the meter
shall be compared with the historical usage pattern. If any discrepancy is found, a notification shall be
created for a utility representative or process to analyze the tampering event and take appropriate action
(for example, to create a service order to investigate).
Category: Contact Meter Reading (or Meter Reading for other Utilities)
External utility companies and other customers and business partners operating within the Consumers
Energy’s service territory would like to make use of Consumers Energy’s AMI infrastructure to reduce their
costs and improve their customer services. Consumers Energy would like to increase revenues and
reduce costs by offering opportunities to non-traditional customers by offering them AMI value-added
products and services.
Scenario: Utility Performs Regularly Scheduled Meter Read for External Utility via AMI
Communication Module
An external utility or business partner would like to use Consumers Energy’s AMI system to read their
meters or devices. The meter installed may not be an AMI Meter or Device, but an AMI Communications
Module could be attached to it to enable communication with the AMI system. New customers or business
partners would send Consumers Energy information regarding the location and read schedule of the
meters or devices.
Scenario: Electric Utility Performs an Interval-Based External Utility Meter Read
Considered in the proposed ‘Meter
Removal’ scenario.
Level of detail not appropriate for ISSGC
to include as separate category.
Scenario elements to be discussed in
proposed ‘Standard Meter Reading’
scenario.
Level of detail not appropriate for ISSGC.
An external utility or business partner would like to use Consumers Energy’s AMI system to read their
meters or devices. The meter installed is an AMI Meter or Device and can communicate with the AMI
system. New customers or business partners would send Consumers Energy information regarding the
location and read schedule of the meters or devices so that Consumers Energy can get readings on its
behalf.
Scenario: Utility performs monitoring of External Utility Meter (monitoring request)
Level of detail not appropriate for ISSGC.
An external utility or customer or business partner would like to use Consumers Electric’s AMI solution to
monitor non-usage or status information on its meters or devices. An AMI Communications Module could
be attached to the Meter or Device which enables communication to the AMI System.
Scenario: Utility performs event detection monitoring for External Utility AMI Meter/Device
information (Non-Read – event detection/ alarm)
An external utility or customer or business partner would like to use Consumers Electric’s AMI solution to
monitor alarm event on its meters or devices. An AMI Communications Module could be attached to the
Meter or Device, enabling communication with the AMI system.
Page 6 of 36
Level of detail not appropriate for ISSGC.
ISSGC Potential Categories and Scenarios
Category: Load Curtailment
Utility companies would like to make use of the AMI infrastructure for their load curtailment needs.
Increase in electricity demand on the grid may cause an energy shortage, which results in the need for
utilities to reduce their energy consumption. Under AMI, Utility companies can implement load curtailment
programs that their customers can participate in, to achieve the energy consumption reduction. The AMI
infrastructure can facilitate load reduction at the customer site, when the need arises, by communicating
with the customer’s load reduction devices.
Scenario: Utility initiates a Voluntary Demand Response Event (e.g. Critical Peak Pricing Event)
Included in the ‘Demand Response’
category.
Proposed
In this scenario, the goal of the utility is to reduce demand using price signals or initiating other voluntary
programs. The utility’s demand response system sends notifications to customers prior to the demand
response event. Customers receive the demand response notification through on premise devices
connected through the home area network (HAN) and can choose to participate or opt out of the demand
response event. The utility will be able track the participation of customers.
Scenario: HAN device does not respond to load curtailment event (AMI system detects issue)
An alternate scenario for the case where the customer’s home area network device does not provide
confirmation that it has received the event notification. The AMI system will attempt to resend the demand
response notification to the customer’s device and will log the results.
Scenario: HAN device does not respond to load curtailment event (Customer reports the issue)
The home area network device did not launch or terminate during the curtailment date and time. The
customer notices this and calls the electric company to report the problem. The customer service
representative is capable of and issues a remote meter test.
Category: Customer has access to recent energy usage and cost at their site
The AMI meters are capable enough to display the recent energy usage on the meter or on the customer
display device apart from sending them to the Head End system. This will help the consumers have a
better view of their energy consumption within the billing cycle.
Page 7 of 36
Included as part of the proposed ‘Utility
verifies customer receipt of a demand
response event message’ scenario.
Included as part of the proposed ‘Utility
verifies customer receipt of a demand
response event message’ scenario.
Included in the ‘Customer Interfaces’
category.
ISSGC Potential Categories and Scenarios
Scenario: The customer's HAN Device is provisioned to communicate with the Utility
Proposed
The customer wants a display device at their location which will display data from the AMI meter at their
location. They can order the device from the web portal or customer representative. Once the device is
received, the customer will add the device to their account on the web portal and map it to their meter. A
Utility system sends a test message to the display device to check its connectivity. Once the message is
received on the display device, then the Utility system will send the activation message to the meter to
activate energy and cost information to the display device. The meter will activate the required services
and send the messages to the display device.
Proposed
Scenario: The customer views pricing or energy data on their in-home device
Customers having the AMI meter need to find the energy consumption and generation up to the last
complete interval. They may also want to see the total energy consumed and generated since the last
billing cycle, the peak demand and generation of energy since the last billing cycle. The meter should also
display the current volts, amps and VARs, current date and time, and Utility messages to the customer.
Scenario: The customer is not able to view energy usage data on the AMI meter display or HAN
device
Included in the proposed ‘In Home
Device Troubleshooting’ scenario.
The AMI meter finds a problem with the display on the meter and logs a message. The Head End system
finds the logged event in the meter during the normal scheduled read and sends a reset request back to
the meter. The meter will then send the success or the failure log to the Head End system. If the meter
fails to reset the display, then an alert is sent to other systems.
Scenario: The customer is not able to view energy and/or cost data on their display device
The customer using a display device is not able to receive any messages from the AMI meter. The
customer calls up the customer representative. The representative then tries to send a text message to the
display device through the AMI meter. If this does not work then the representative sends a request to the
AMI meter to transmit the energy and cost information to the customer display device. When the
confirmation is received by the representative, another test message is sent to the display device which is
then received by the device and confirmed by the customer. The customer representative should be able
to detect the issue with the display device, transmit the consumption and cost information to the display,
and test the display device by sending a test message.
Page 8 of 36
Included in the proposed ‘In Home
Device Troubleshooting’ scenario.
ISSGC Potential Categories and Scenarios
Scenario: The customer submits a request to view their energy data up to the current hour via the
Internet
The customer web portal will provide consumption data. Residential customers will be able to view the
previous 2 days KWH energy consumption. Commercial & Industrial (C&I) customers will be able to view
the most recent consumption on the portal. The residential customer will see the latest information
available within the utility’s system while C&I customers can view their consumption up to the last
complete interval. The utility’s system will validate and update the information before displaying it on the
web portal.
Scenario: The customer is not able to retrieve usage data for the previous day on the Internet
Included in the proposed ‘Customer
Views Pricing or Energy Data via the
Internet’ scenario.
Level of detail not appropriate for ISSGC.
The customer logs into the portal to find the previous day usage data. To obtain the requested information
the lookup is performed in the billing system, MDM, Head End and the meter respectively. If the data could
not be found in any of these systems, the web portal shows the message to the customer. Also the Head
End system initiates an on-demand meter test by sending a message to the meter. The meter will execute
the remote meter test and send the results to the Head End system. In case the meter test fails, then an
alert is sent to other systems.
Scenario: The AMI meter/device display is remotely configured according to the customer's
request
Level of detail not appropriate for ISSGC.
Customers having the AMI meter may want to configure the display data on their devices. They either call
the representative or log into portal to configure the settings. The representative will set the messages,
which the customer wants to see and will remove other messages. Once the settings are confirmed, the
messages are sent to the meter through utility systems to the MDM to the Head End system. Once the
settings get configured in the meter the customer confirms the request.
Scenario: The customer requests that the utility sends energy usage and pricing information to
their devices (e.g. text messages on cell phone, satellite or cable station, etc.)
A customer with an AMI Meter/Device wishes to receive the daily messages on his or her mobile phone.
For this, the customer logs into the utility’s portal and registers his or her mobile phone number. A
confirmation number is generated and sent to the mobile phone for verification. The customer then enters
this confirmation number on the portal to confirm the request. Once the mobile phone is registered, the
energy consumption data is sent to the mobile device on a schedule requested by the customer on the
portal.
Page 9 of 36
Level of detail not appropriate for ISSGC.
ISSGC Potential Categories and Scenarios
Scenario: Customer request to move-in from the portal
The customer web portal provides functionality to enable utility customers to perform a move-in to a vacant
premise from the web. The web move-in process should be able to determine if the AMI-metered service
is on or off. If the meter is off, the move-in process must get a confirmation from the customer to connect
the AMI meter and then should remotely connect the meter. If the meter is active, the web move-in
process should be able to get the meter reading and display it to the customer through the portal.
Scenario: Customers requests to move-out from the web portal
Utility customers that are registered on the web portal can request a move out from their existing premise
using the portal. The customer enters information regarding the move-out and the web portal validates the
move-out data. Customers can perform a past, current or future move-out from the web portal. Customers
can only request a move out for premises that are registered to them. The electric service must be read in
real time if the move out date is current or in the past.
Scenario: Customer sign-up for load curtailment program
Level of detail not appropriate for ISSGC.
Scenario elements can be considered in
the ‘Meter Switch Connection’ scenario.
Level of detail not appropriate for ISSGC.
Scenario elements can be considered in
the ‘Meter Switch Disconnection’
scenario.
Level of detail not appropriate for ISSGC.
The customer login into the web portal should be able to view the ongoing load curtailment campaign and
enroll for the same if they wish.
Scenario: Customer applies for Prepayment and views the balance remaining
One of the major advantages of the AMI meter over the conventional meter is its ability to remotely
connect or disconnect. Hence for a customer opting for a prepayment, the system should calculate the
amount in kilowatts that a meter can consume before disconnecting. Also the meter should display
periodically the balance of kilowatts left in the prepayment. The customers who wish to prepay for the
electricity should be able to select for the same from the portal. The AMI meter should then connect
remotely until the balance kilowatt remains in the customer account and then remotely disconnect. The
AMI meter should be capable of periodically displaying the balance of electricity remaining so that, the
customer can decide if he wants further prepayment.
Page 10 of 36
Scenario elements included in the
proposed ‘Customer Pre-Pays for Electric
Service’ scenario.
ISSGC Potential Categories and Scenarios
Scenario: Customers should compare their home consumption.
The residential customers would like to know their consumption pattern based on the weather and across
their neighborhood, so that they can find which appliances are consuming more electricity and take
necessary steps. The utility’s web portal should have the capability to show these analyses to the
consumer. This should include: consumption compared to the same period last year, energy consumed by
different appliances at the home, and the comparison of bill amounts with similar homes within the same
general location.
Category: Customer prepays for electric services
The advanced AMI Meter/Device Infrastructure (AMI) will enable the utility to handle prepayment electric
services for its customers. These services will allow customers to establish electric service without
providing a large upfront deposit and will help enable them to control their energy spending. Other
customers may prefer to prepay for electricity just because they would like to pay for their energy in
advance, or they may want to prepay for electricity at another site for a specific period of time. This
scenario describes the method by which customers enroll in pre-paid electricity services up to the
consequences of failing to make additional prepayment before their prepayment balance expires.
Scenario: The customer prepays for electricity service at his or her site
The customer contacts the utility to prepay for electricity service at his or her home/business. The utility
accesses the customer’s account and confirms the customer’s identity.
Immediate activation: The customer provides the payment amount and payment information to the utility
using various payment methods. The utility verifies funds and applies the prepayment amount on the
customer’s account. The utility uses the AMI to transmit the prepayment information to the AMI
Meter/Device at the customer’s site. The AMI Meter/Device will receive, log, and activate electricity service
at the customer’s site.
Schedule for specific time frame: The customer advises the utility what start and end date and time
(duration) that he or she would like to prepay for electrical service at his or her facility. The utility provides
the customer the estimated energy usage and cost for the prepayment event time frame (based on a
historical consumption profile). The customer provides the payment amount and payment information to
the utility using various payment methods. The utility verifies funds and applies the prepayment amount on
the customer’s account.
Page 11 of 36
Level of detail not appropriate for ISSGC.
Scenario elements included in the
proposed ‘Customer Views Pricing or
Energy Data via the Internet’ scenario.
Level of detail not appropriate for ISSGC.
A scenario is included as part of the
‘Demand Response’ category.
This is the proposed ‘Customer Pre-Pays
for Electric Service’ scenario.
ISSGC Potential Categories and Scenarios
Scenario: The customer prepays for electricity service for their facility
Level of detail not appropriate for ISSGC.
The customer contacts the utility to prepay for electricity service at his or her home/business. The utility
accesses the customer’s account and confirms the customer’s identity.
Immediate activation: The customer provides the payment amount and payment information to the utility
using various payment methods. The utility verifies funds and applies the prepayment amount on the
customer’s account. The utility uses the AMI to transmit the prepayment information to the AMI
Meter/Device at the selected site. The AMI Meter/Device will receive, log, and activate electricity service at
the customer’s selected site.
Schedule for specific time frame: The customer advises the utility what start and end date and time
(duration) that he or she would like to prepay for electrical service at their facility. The utility provides the
customer the estimated energy usage and cost for the prepayment event time frame (based on a historical
consumption profile). The customer provides the payment amount and payment information to the utility
using various payment methods. The utility verifies funds and applies the prepayment amount on the
customer’s account.
Scenario: The customer prepays for electricity service for facilities not owned by the customer for
a specific time frame
Level of detail not appropriate for ISSGC.
The customer contacts the utility to prepay for electricity for a specific event at a facility not owned by the
customer. The utility accesses the requesting customer’s account information and the account of the utility
facility for which he or she wants to prepay for service. The utility confirms the facility that the customer
has identified has enabled prepayment services.
Scenario: The customer’s prepayment balance approaches zero for their site and prepays for
additional electricity
The utility provides the customer various warning messages alerting the customer that the prepayment
balance on the AMI Meter/Device is low and estimates the time remaining before the prepaid account
reaches zero. If equipped, this information is passed onto a display device at the event site. When the
prepayment balance approaches zero at their site, the customer checks this over the portal or at the
display devices. The customer then prepays for additional electricity service. It is necessary for the utility
system to determine a configurable threshold of remaining electricity service on the account. When that
threshold is reached, information about the days and amount remaining will be sent to the MDMS. The
customer will then receive this information via the portal or the in-home display device.
Page 12 of 36
Level of detail not appropriate for ISSGC.
ISSGC Potential Categories and Scenarios
Scenario: The customer’s prepayment balance approaches zero for their site and they do NOT
prepay for additional electricity
Level of detail not appropriate for ISSGC.
The utility provides various warning messages alerting the customer that the prepayment balance on the
AMI Meter/Device is low and there is little time remaining before the prepaid account reaches zero. If
equipped, this information is passed onto a display device at the event site. As the customer’s prepayment
balance approaches zero, the customer may view this over the portal or at the display devices. If
customer does not replenish the account with a further amount, electricity service at the site will be
reduced or limited; or terminated or disconnected. The customer can then opt to switch back to the normal
(postpaid) billing program for the same contract, in case if he or she runs out of money. Exception
processing and handling must be available for all of the interfaces.
Scenario: The customer prepays for electricity service at their site but there is no power
Level of detail not appropriate for ISSGC.
The customer prepays for the electricity, but there is no power in the house. The customer contacts the
call center and reports the problem. The CSR verifies the funds and checks the customer details. If the
CSR finds some problem with the AMI Meter/Device, he or she creates a service order. The field
representative visits the customer site and rectifies the problem, and electric supply is reconnected.
Category: External Clients use the AMI system to interact with devices at the customer site
The Advanced Meter Infrastructure (AMI) will enable third parties, such as energy management
companies, to use the communication infrastructure as a gateway to monitor and control customer
equipment located at the customer’s premise. The AMI will be required to enable on-demand requests
and support a secure environment for the transmission of customer confidential information.
Scenario: Energy Management Company monitor customer equipment – on demand
This scenario describes the simplest use case, in which the third-party energy management company
gathers energy consumption data from customer premises equipment using the AMI.
Scenario: Third Party wants to control (on/off/limit/program) customer equipment
This scenario describes the case in which the third party attempts to control the equipment at the customer
site. The control request may be to turn equipment on or off, to limit the energy demand from the
customer, or to reprogram the customer equipment, among other possibilities.
Page 13 of 36
Level of detail not appropriate for ISSGC.
Category elements will be considered in
‘Customer Interfaces’ and ‘AMI’
Scenario elements to be considered in
‘AMI’, ‘Customer Interfaces’ and ‘Demand
Response’ categories.
Scenario elements to be considered in
‘AMI’, ‘Customer Interfaces’ and ‘Demand
Response’ categories.
ISSGC Potential Categories and Scenarios
Scenario: Program Provisioning
In this scenario, the customer changes the access of the third party to equipment at the customer’s site.
This may occur because the customer has just initiated or discontinued the contract with the third party or
has changed the terms of the contract. Refer also to the scenario “AMI registers customer owned devices
for communication on the HAN”
Scenario: Third Party or Customer reports Third Party monitoring or control failures
Level of detail not appropriate for ISSGC.
Scenario elements may be considered in
‘Customer’s In-Home Device is
Provisioned to Communicate with the
Utility’.
Level of detail not appropriate for ISSGC.
In this scenario, a communications or equipment problem has occurred and either the third party or the
customer reports that the Third Party cannot access the equipment at a customer’s site. This scenario
highlights the requirement that the AMI Network must be able to remotely test the communications path to
the customer equipment.
Scenario: Utility detects third party communication/messaging failure
This scenario differs from the previous scenario in that it is the utility who detects the problem with the
communications path between the third party and the customer device.
Category: Distribution Operations curtails customer load for grid management
A customer is enrolled in a non-price responsive demand-side grid management program (possibly in
exchange for reduced tariffs). This program allows the utility to request an automated load reduction at the
customer site. The customer can override the request in exchange for a possible penalty charge. At least
two levels of advanced warning are envisioned: 1) Predicted energy shortages (long term – 24 hours, and
short term - a few hours notice – these two cases do not develop any different requirements for the AMI
system, but might cause the customer to respond in different ways). 2) Emergency shortage (for example,
a few minutes notice with no possibility of opting out)
Scenario: Load limit for grid management
The utility uses the demand response system to issue messages to customers to reduce load for the
purpose of grid management. Customers will reduce load or be disconnected by their AMI Meter.
Scenario: Emergency Curtailment (in lieu of Rolling Blackout)
Level of detail not appropriate for ISSGC.
.
Included in the ‘Demand Response’
category.
Scenario provides input into proposed
scenario ‘Utility Controls Participating
Customers’ Load Control Devices’.
Scenario considered but not proposed.
The utility uses the AMI system to selectively disconnect customers instead of implementing a rolling
blackout. By selectively disconnecting customers, the utility can reduce load and still provide service to
public service and medical customers.
Page 14 of 36
ISSGC Potential Categories and Scenarios
Scenario: Customer opts out of curtailment for Grid Management
Level of detail not appropriate for ISSGC.
An alternate scenario that covers when the customer decides not to curtail load as requested. The
customer opts out of curtailment by sending a message to the meter and the meter logs the event and
reports back through the AMI system.
Scenario: Load at the customer site is already below threshold
Level of detail not appropriate for ISSGC.
This alternate scenario applies to both normal curtailments and emergency curtailments, and covers the
case where a customer has been asked to reduce load for grid management, but is already below a
specified threshold. Further load reduction will not take place in this situation.
Category: Distribution Engineering or Operations optimize network
based on data collected by the AMI system
Included in the ‘Distribution Automation’
category.
Network optimization is focused on issues with feeder loading, voltage profiles, efficiency, reliability and
quality. An AMI system may provide useful data to both improve customer power quality and reduce
distribution costs to the utility through optimization. Potential AMI outputs include average voltage at
customer site, voltage variations seen by the customer, power consumption by time interval, harmonics
(voltage and/or current), power production by customer-supplied distributed generation, and customer
power factor. Possible uses for this data include warning letter issued to customers (if they are adversely
impacting the network), feeder capacitor bank switching, transformer voltage tap switching, input to load
forecasting models (both short- and long-term), feeder harmonic filter controllers, and feeder switching
decisions. This scenario also includes power quality contract compliance and includes use of the AMI
communications network to provide connectivity to distribution system devices (e.g. IEDs / RTUs, sensors,
fault indicators, etc.) as sub-use cases.
Scenario: Distribution Engineering or Operations optimize network based on voltage Root Mean
Square (RMS) Variation information at the customer site
This scenario involves the use of the AMI meter to detect voltage sag at a customer site, leading to a
request for detailed meter data regarding the event. Distribution personnel will periodically compare the
recorded data with baseline values and perform analysis of the network. The meter collects and
processes usage / power quality / sensor data. The AMI system will not replace the SCADA / DMS
system, it shall add on to these existing systems.
Page 15 of 36
Power quality improvement and analysis
likely has a lower benefit compared to
other scenarios. The lower priority of this
scenario for the ISSGC does not indicate
that it will be excluded from the future
smart grid, only that discussion of the
scenario is less important than others.
ISSGC Potential Categories and Scenarios
Scenario: Distribution Engineering or Operations optimize network based on harmonics data
collected by the AMI system
This scenario involves the use of the AMI meter to detect excessive harmonics in voltage/current at a
customer site, leading to a request for detailed meter data regarding the event. Distribution personnel will
periodically compare the recorded data with baseline values and perform analysis of the network. The
meter collects and processes usage / power quality / sensor data. The AMI system will not replace the
SCADA / DMS system, it shall add on to these existing systems.
Scenario: Capacitor Bank Controller (CBC) uses the AMI infrastructure to optimize customer
voltage/power
This scenario involves the use of the AMI meter to present voltage data communicated across the AMI
infrastructure to another type of “intelligent” device, the Capacitor Bank Controller. The Capacitor Bank
Controller (CBC) controls a bank of capacitors that can be switched on or off, as required to maintain
voltage variations on the system within acceptable limits. The meter collects and processes usage / power
quality / sensor data. The AMI system will not replace the SCADA / DMS system, it shall add on to these
existing systems.
Scenario: Distribution Control and Monitoring System (DCMS) reconfigures feeder after a fault
This scenario involves the use of the AMI infrastructure for communication between remote sensors and
switches to determine adverse system conditions, leading to a loss of power in a circuit, and to reconfigure
the system to restore power. The meter collects and processes usage / power quality / sensor data. The
AMI system will not replace the SCADA / DMS system, it shall add on to these existing systems.
Scenario: RCS devices autonomously reconfigure after a fault
This scenario involves the use of the AMI infrastructure for communication between remote sensors and
switches to determine adverse system conditions, leading to a loss of power in a circuit. This is an
alternate scenario where the remote devices are “intelligent” devices capable of autonomous
communication and action to restore the network to acceptable operating conditions. Authorized
Distribution Personnel (ADP) shall have the capability to query the meter and retrieve detailed harmonic
information as defined in IEEE 1159, both locally and from remote. Local communication has priority over
remote.
Page 16 of 36
Power quality improvement and analysis
likely has a lower benefit compared to
other scenarios. The lower priority of this
scenario for the ISSGC does not indicate
that it will be excluded from the future
smart grid, only that discussion of the
scenario is less important than others.
Included in proposed scenario ‘Capacitor
Bank Controllers Optimize Voltage or
Power Factor’.
Included in proposed scenario
‘Distribution Management System
Reconfigures Distribution Circuits After a
Fault’.
Included in proposed scenario
‘Distribution Circuits Autonomously
Reconfigure After a Fault’.
ISSGC Potential Categories and Scenarios
Category: Customer Provides Distributed Generation
This Use Case describes several scenarios focused on customer-owned generation, which leverage the
AMI infrastructure to enhance installation coordination, metering and address safety issues.
Scenario: Customer delays generation until after DG Program enrollment
This scenario describes the primary DG process where the customer applies for the DG Program, is
qualified to participate, and follows the appropriate procedure before energizing the DG equipment and
providing net generation. It features a web application to support both individual and bulk application for
the program. The AMI system must measure Watt-hrs generated, VAR-hrs generated and VAR-hrs
consumed. All of these quantities shall be independent (e.g. the VAR-hrs are not “netted” by the meter).
These quantities must be able to be gathered from other devices elsewhere on the customer site (e.g., the
generator controller may collect revenue-quality information which must be passed to the AMI system).
This information can be either recorded in the meter or forwarded directly to the Premise Gateway.
Scenario: Customer begins generation before DG Program enrollment
This scenario describes an alternate DG process where the customer applies for the DG Program, but
begins generation before the enrollment process is completed. This sub-use case requires an AMI meter
that can detect reverse energy, assuming there is net generation. Another feature of this alternate
scenario is the “reminder” letter that the customer is to receive to assist in enforcing the procedure.
For the ISSGC, the ‘Distributed
Resource’ category should cover the
described distributed generation topic as
well as distributed generation’s operation
with demand response programs.
Included in proposed scenario ‘Customer
Provides Distributed Resource’.
Elements of this scenario will be included
in proposed scenario ‘Customer Provides
Distributed Resource’.
This sub-use case also incorporates the alternate DG scenario where the customer has not applied for
enrollment in the DG Program, but begins generation unexpectedly. Beside the “reminder” letter featured
in the main scenario, this scenario introduces a “disconnect on detected DG” flag that a CSR could set to
trigger an automatic disconnection by the AMI meter. If the customer is not approved for DG, the AMI
system shall continue to record and report consumption (operate normally) but it will not record nor report
net generation data.
Scenario: Dispatch Generation (Control, Peak Shaving, VAR Management, PQ, Line Safety)
This scenario describes the DG process where the customer allows the Utility to dispatch generation from
the customer’s equipment. There are two scenarios combined in this sub-use case, dispatch with
customers with under 10kW of generation and dispatch with customers with between 10kW and 1mW of
generation. The AMI systems will forward communications from the utility to and from Generation Control
Equipment which is part of the customer’s Building Management System (BMS). Any of these requests
may specify a time period for which to perform the operation, or an “undo” command. This is the
“generation dispatch” functionality.
Page 17 of 36
Included in proposed scenario ‘Utility
Controls Customer’s Distributed
Resource’.
ISSGC Potential Categories and Scenarios
Scenario: Utility Provides Services to DG Customers
This scenario describes the DG process where the customer enrolls in a Utility DG service program for
maintenance, reporting, profitability modeling, operations, and other possible services. This sub-use case
features the concept of a “Business Center” which collects meter data from Meter Data Management
System, DG service data and business process data from customer information systems to produce
reports and profitability studies for the Customer. The Premise Gateway will log all the messages sent
and received from the Utility to and from the Building Management System or customer’s DG device.
Category: Distribution operator locates outage using AMI data and restores service
Lower priority. Considered but not
proposed for the ISSGC.
Included in the ‘AMI’ category.
AMI offers opportunities to expand the range and extent of outage information available for outage
detection and for the confirmation of power restoration following a network outage. This use case involves
the employment of various sources and assets illustrate the outage processes leveraging the AMI
infrastructure to restore power.
Scenario: Lateral outage with a subset of customers not restored after the outage ends
This scenario assumes a network outage in an area that is serviced by the AMI system. Outage
management is able to utilize the AMI infrastructure to detect the outage, to help confirm restoration of
power, and to determine that service is still required to restore power to a subset of customers. The AMI
System will record outage information on a meter by meter basis. Also, the AMI System will record the
duration of outage for later statistical analysis.
Scenario: Collector lost due to outage
This scenario is similar to the lateral outage scenario. In addition to electric meters reporting their outage
status, an AMI network collector device loses power and reports its condition to the outage management
system.
Category: Real time operations curtails or limits load for economic dispatch (ES&M)
Market Operations performs continuous routines simultaneously to establish and maintain a balance
between electric supply and electric demand. These routines include transacting for electric supply in
forward markets beyond-day-ahead, day-ahead, hour-ahead, and real-time. The transacting for electric
supply involves two elements: market transactions and resource dispatch.
This use case proposes a computer system known as the Distributed Resources Availability and Control
System (DRAACS), which would serve as a clearinghouse for demand response requests submitted to the
AMI system. Some of these requests may originate from Market Operations for economic dispatch
purposes, and some may originate from the System Control Center for reliability purposes. This use case
deals specifically with economic dispatch requests.
Page 18 of 36
Included in the ‘Meter Detects and
Reports Outage’ scenario.
Level of detail not appropriate for ISSGC.
Some scenario elements considered in
‘Meter Detects and Reports Outage’
scenario.
Some elements included in the ‘Demand
Response’ category
ISSGC Potential Categories and Scenarios
Scenario: Achieve least cost dispatch
This scenario describes the most common sequence to achieve this economic dispatch. The scenario
addresses the five products (Energy, Replacement reserves, Non-spinning reserves, Spinning reserves
and AGC) as listed above. The steps to achieve a least cost dispatch in some case occur in parallel.
Scenario: Dispatch requirements are not met
This scenario describes what happens when scenario 1 repeats several times, but DRAACS is still unable
to provide sufficient demand response to meet the utility’s needs.
Scenario: Day ahead scenario (essentially the same of the “hour ahead” scenario)
The day-ahead market relies on resource data that is updated daily before trading begins. The data is
presented in hourly detail. The data is gathered over several hours the day before and updates continue
until approximately one-half hour before trading begins. After trading ends, the load and resource data are
transferred over to generate schedules for reporting and clearing through the ISO (Independent System
Operator).
Scenario: Third Party scenario – Aggregator uses AMI data for economic dispatch
This scenario is the same as the first scenario, except for the requirement that requests to DRAACS be
able to specify that the load reduction comes from a particular subset of AMI meters.
Category: Gas Measurement
Included in the proposed ‘Demand
Response Operations for Economic
Dispatch’ scenario.
Level of detail not appropriate for ISSGC.
Some scenario elements considered in
‘Demand Response Operations for
Economic Dispatch’ scenario.
Level of detail not appropriate for ISSGC.
Some scenario elements considered in
‘Demand Response Operations for
Economic Dispatch’ scenario.
Level of detail not appropriate for ISSGC.
Some scenario elements considered in
‘Demand Response Operations for
Economic Dispatch’ scenario.
Considered out of scope for the ISSGC.
The AMI system along with SCADA will provide the ability to snapshot all system (city gates, key regulator
stations, etc) and customer meters for the exact same interval of time. This has not previously been
possible. With sufficient accuracy of volumetric flow, pressure, and ambient temperature, this data will
allow the utility to balance all receipts and deliveries on the system to determine the amount of gas that is
“lost and unaccounted for” (LAUF), reduce the “theoretical unbilled” amounts, and reduce the effort of the
annual “true-up”. For gas transmission and storage, the AMI system may additionally supply gas quality
data for operational and financial purposes.
Scenario: The gas measurement system measures gas consumption to improve lost and
unaccounted for gas (LAUF)
The MDM system stores the gas consumption data from the AMI system. A gas measurement system will
query the MDM and calculate an exception report for LAUF.
Page 19 of 36
Considered out of scope for the ISSGC.
ISSGC Potential Categories and Scenarios
Category: Gas Planning
Considered out of scope for the ISSGC.
Optimizing the network involves issues with gas flow volumes, gas pressure profiles, temperature effects,
efficiency, reliability and quality. The utility uses feedback from the AMI system to reduce distribution
costs, analyze emergency situations, detect gas outages, proper sizing of meters, and determine low
pressure points in the system. In addition, AMI outputs, such as consumption by time interval (hour, day,
month, and year), flows, ambient temperatures, and gas pressure at select locations are used to conduct
load research and profiling, as well as model future uses and losses using simulation tools. For gas
transmission and storage, AMI data may also be used to observe and predict storage field migration and
line packing.
Scenario: Gas field crews use real time data to manage unplanned outages
Considered out of scope for the ISSGC.
This scenario covers when an external construction crew using heavy equipment digs into a gas main and
ruptures it.
Scenario: Auditor retrieves/analyzes customer load profile data for rate selection, equipment
sizing and system studies
Considered out of scope for the ISSGC.
This scenario covers when an Energy Auditor queries interval data repository for customer load profile
data.
Category: Gas Corrosion Control
Considered out of scope for the ISSGC.
The utility uses the AMI system to gather corrosion control data on steel services and main headers. This
also includes using the AMI system to gather data from distribution system devices (e.g. cathodic
protection, current reads, rectifier, AC & DC voltages, reference cells, methane detectors, etc.). Such data
is used to monitor inside meter locations for gas leaks (atmospheric surveys) and monitor outside test
points for gas leaks.
Scenario: Utility uses AMI comm. network to gather voltage and current from rectifiers for
performance & corrosion monitoring
Utility uses AMI communication network to gather data from rectifiers (voltage and “current”) to insure
proper performance of corrosion prevention monitors. Also, the Utility will use the AMI communication
network to gather data from “pipe to soil” test stations to insure proper performance to prove cathodic
protection.
Page 20 of 36
Considered out of scope for the ISSGC.
ISSGC Potential Categories and Scenarios
Scenario: Utility uses AMI system to retrieve methane detection data
Considered out of scope for the ISSGC.
The Utility will use the AMI system to retrieve methane detection data. The MDMS retrieves methane
sensor data periodically from inside meter locations and an alarm application will compare and notify
dispatch when a specified limit is exceeded. Dispatch will then send a first responder to the alarm site to
investigate.
Category: Utility installs, provisions and configures AMI system
Level of detail not appropriate for ISSGC.
To plan, procure, and install an AMI system is a process that involves multiple steps and multiple systems
Many processes are involved, ranging from developing a deployment plan through forecasting and
procurement, installation of individual devices, initialization of tariffs, setting meter operating parameters,
entering and verifying information in inventory, customer and geographic databases, verification of
communications, and other functional testing.
Scenario: Utility provisions the AMI system
Level of detail not appropriate for ISSGC.
Based on the Utilities’ strategy and planning, AMI devices will be purchased from AMI vendors using the
procurement process. A goods receipt of the AMI devices will be done in the inventory management
system. After receiving the AMI devices from vendors, testing will be done.
Scenario: Utility installs and configures AMI system components
Level of detail not appropriate for ISSGC.
After the creation of work orders, the installation of AMI system components will occur. After the
installation is complete and verified as functional, the corresponding status has to be updated in utility
systems and the component-related details communicated to the MDM system.
Scenario: Utility installs and configures AMI system meters
Level of detail not appropriate for ISSGC.
After the creation of work orders, the installation of AMI system will occur by replacing the existing meters.
After the installation is complete and verified as functional, the corresponding status has to be updated in
utility systems and the meter related details communicated to the MDM system.
Scenario: Utility manages end-to-end life-cycle of the meter system
After the installation of AMI devices at customer’s premises, the client has to maintain the new devices
whenever an issue is reported by the AMI meter, AMI Head End or the customer. In addition to fixing the
reported issues, periodic maintenance of all the AMI devices has to be done.
Page 21 of 36
Level of detail not appropriate for ISSGC.
ISSGC Potential Categories and Scenarios
Scenario: AMI meter detects issue
Level of detail not appropriate for ISSGC.
The AMI meter will detect the issue and send it to utility systems via the MDM system. The information will
be filtered and verified, and the process to create a maintenance order will be triggered. As soon as the
problem is resolved, the status of the work order will be updated in the work order system. In the case
where a “Smart Meter” has to be changed, the details of the new “Smart Meter” will be updated in the
MDM and other utility systems. AMI meters will be configured to detect issues and perform self-tests.
Scenario: AMI Head End detects failure
Level of detail not appropriate for ISSGC.
If the AMI Head End detects an issue, it will send it to utility systems via the MDM system. The information
will be filtered and verified, and the process to create a maintenance order will be triggered. As soon as
the problem is resolved, the status of the work order will be updated in the work order system. In the case
where the “Smart Meter” has to be changed, the details of the new “Smart Meter” will be updated in the
MDM and other utility systems. The AMI Head End will be configured to detect issues and perform periodic
investigations of the AMI devices.
Scenario: Customer / Data Retriever detects issue
Level of detail not appropriate for ISSGC.
A customer or data retriever can find an issue and report it through the web portal or call center. After
verification of the problem reported, a work order will be triggered. As soon as the problem is resolved,
the status of the work order will be updated in the work order system. In the case where the “Smart Meter”
has to be changed, the details of the new “Smart Meter” will be updated in the MDM and other utility
systems. The call center can determine the type of device at issue and perform on-line tests to determine
if there is an issue with the AMI meter.
Scenario: Periodic Maintenance of AMI Devices
Level of detail not appropriate for ISSGC.
As part of the periodic maintenance cycle, after verifying the usage and working condition of the AMI
device, work orders will be generated to check the AMI devices. During the checking process, if any meter
is replaced with a new meter, the corresponding data will be updated in the MDM and other utility systems.
Scenario: Maintain load limit threshold value
Level of detail not appropriate for ISSGC.
As part of the lifecycle of an AMI meter, it may be necessary or desirable to change the default load limit
threshold value that is expected to be set at the time of installation. This value is set in the meter to be
used when load-limiting is triggered, as in a move-out scenario. To update this value, a request for update
must be sent through to the Head End. The system must be able to support an update to the load limit
threshold value.
Page 22 of 36
ISSGC Potential Categories and Scenarios
Category: Utility Upgrades AMI to Address Future Requirements
Level of detail not appropriate for ISSGC.
Because of the high capital cost of AMI, the system must be able to adapt to certain kinds of anticipated
changes that may occur. The capability of the system to adapt can reduce the need for future system
upgrades and corresponding significant costs.
Scenario: Vendor Upgrades Field Component Firmware
Level of detail not appropriate for ISSGC.
The meter or communication device vendors may offer product improvement revisions, or the Utility may
request a program modification after the product has been placed into service. This may require an
upgrade to the meter firmware. The upgrade must be able to be scheduled and performed remotely
through the AMI system.
Scenario: Vendor Upgrades Field Component Software
Level of detail not appropriate for ISSGC.
The meter or communication device vendors may offer product improvement revisions, or the Utility may
request a program software modification after the product has been placed into service. This may require
an upgrade to the meter software. The upgrade must be able to be scheduled and performed remotely
through the AMI system.
Scenario: AMI System registers customer owned devices for communication on the HAN
As new HAN technology is developed over the years, a customer may purchase a new device with new
HAN technology which the AMI system does not recognize. The customer will then be notified that they
must either pay the Utility to change the AMI meter (or service gateway) to one that accommodates the
new HAN technology or to install a “bridge” to convert the device to the old HAN technology (if available).
Forward and backward compatibility with the communications technology ensures that both the
Customer’s and Utility’s investment is protected.
Category: AMI system recovers after outage
Elements of this scenario are included in
the proposed ‘Customer’s In Home
Device is Provisioned to Communicate
with the Utility’ scenario.
Level of detail not appropriate for ISSGC.
Power outage may happen due to a communication network issue or a concentrator level issue. The AMI
Head End will be able to recognize these types of failures and communicate back to the MDM and other
utility systems to handle the scenario via a service order as necessary. During power outage or
communication failures AMI meters will be able to continue measuring customer’s power usage.
Page 23 of 36
ISSGC Potential Categories and Scenarios
Scenario: AMI Data Center Concentrator detects individual meter communication failure
Level of detail not appropriate for ISSGC.
Should the AMI Head End detect a communication failure with a meter, it will attempt to reconnect and
update the logs appropriately. If communication cannot be restored within the timeframe configured, an
event will be passed through to utility systems, where the pre-determined business rules will be
processed. If the failure is not resolved remotely, a work order will be created and released for
inspection/repair. If a component is replaced, the system will be updated with the appropriate device and
installation data. After service, the AMI Head End will reestablish communication and update the logs.
Scenario: Meter responds to communication failure
Level of detail not appropriate for ISSGC.
The AMI meter will have the ability to detect communication failures. Should there be a communication
failure, the meter will log the event and await restoration of communications. After communications are
restored, the meter will synchronize with the system, recover data which were not received data, and
transmit any queued data that could not be sent due to the failure. The meter will keep an on-board log of
communications events and continue to store metering data for at least a 45 day period. The meter
should attempt to select an alternate link during a primary communication link failure.
Scenario: AMI Data center concentrator detects failure in an area
Level of detail not appropriate for ISSGC.
In addition to a communications failure or the failure of an individual meter, the loss of a collector can
affect a wide area of the system. This scenario describes the process where a system component other
than an AMI meter malfunctions. It will be necessary for the AMI system to perform data flow control after
a communication or power outage to prevent resources from being overloaded.
Category: Customer uses smart appliances
Smart appliances are being introduced by vendors that will allow customers to minimize and optimize their
energy usage and cost at their site. The smart grid will enable improved communications between the
utility and smart appliances at a customer’s premise by making it possible to remotely transmit energy
usage, cost, and energy related messages to the customer’s smart appliance within the home or business.
Page 24 of 36
Elements of this category will be used in
the ‘Customer Interfaces’ category.
ISSGC Potential Categories and Scenarios
Scenario: Customer installs, configures, and registers smart appliance
The utility needs to support customers with smart appliances by providing registration, enrollment in utility
sponsored smart appliance programs, and commissioning of the smart appliance on the AMI network.
Test messages will be sent over the AMI system to the smart appliance. A smart appliance that is
connected to a customer energy management system may also be registered or enrolled. Smart
appliances not registered or enrolled may still receive utility or public messages over the AMI network or
through other communication channels.
Scenario: Customer uses premise smart appliance to manage and adjust energy use
The utility needs to support customers with delivery of energy related information to smart appliances.
The customer may receive price signal updates, event notices, or other energy related messages at their
smart appliance and use this data to manage and adjust smart appliance energy use. Demand response
event signals sent from the utility or publicly broadcast reliability alerts may be sent to the customer’s
smart appliance for triggering a program that automatically reduces or limits load.
Category: Customer Uses Premise Energy Management System (EMS) or In-home Display (IHD)
AMI will enable improved communications between the utility and its customers by making it possible to
remotely transmit energy usage, cost, and energy related utility messages to the AMI meter and down to
the customer’s control and display devices (e.g. EMS and IHD) within the home or business if equipped
with an energy management system or an in-home display. The types of messages the utility may send
include energy conservation alerts or tips, planned outage, energy usage, current tier level, tariff, and
other energy related information. Information may come from either of two sources: the utility
communication system or directly from the meter.
Scenario: Customer installs, configures, and registers premise EMS or IHD
The customer installs and registers an EMS or IHD to communicate with the utility through the AMI
network or through an alternate communication channel. This may include any authorized representative
of the customer, including third party aggregators that can act on behalf of the customer in registering and
enrolling IHD or EMS.
Scenario: Customer uses premise EMS or IHD to manage and adjust energy use
Customers can access their most recent usage and pricing data with their EMS or IHD display device to
determine how much energy they are using and the associated costs at their site. The utility needs to
support customers with delivery of energy usage and other related information.
Page 25 of 36
Elements of this scenario will be
considered in the more generic
‘Customer’s in home device is
provisioned to communicate with the
utility’ scenario.
Elements of this scenario will be
considered in the more generic
‘Customer views pricing or energy data
on their in home device’ scenario.
Elements of this category will be
considered in the ‘Customer Interfaces’
category.
Elements of this scenario will be
considered in the more generic
‘Customer’s in home device is
provisioned to communicate with the
utility’ scenario.
Elements of this scenario will be
considered in the more generic
‘Customer views pricing or energy data
on their in home device’ scenario.
ISSGC Potential Categories and Scenarios
Scenario: Utility uses premise EMS for load control or load limiting
Customers can participate in programs that allow the utility to send load control signals to their EMS which
will control loads within the customer’s premise to lower the customer’s energy usage.
Category: Load researchers perform analyses using historical AMI meter data
Describes how information gathered, stored and analyzed by the AMI system can help these studies be
faster, less costly, and more accurate. In general, the primary benefit of using AMI data is that load
research will no longer need to deploy a separate monitoring system to acquire the data necessary to
perform these studies.
Scenario: Load research performs studies with data from a designated subset of meters
Load researchers can use AMI data to perform usage studies that currently require the use of specialized
research meters. Load research performs analyses of electric load statistics and usage patterns for any or
all of the utility’s rate groups or customer classes (market segments) using data from a designated subset
of meter samples.
Scenario: Load research performs a study of individual large customers
Elements of this scenario will be
considered in the more generic ‘Utility
controls participating customers’ load
control devices’ scenario.
This category’s lower technical
requirements gave it a lower priority. The
primary policy guidance related to this
category is privacy of customer
information.
Not proposed. Stakeholder input on
customer data privacy is desired.
Not proposed. Stakeholder input on
customer data privacy is desired.
Load researchers can perform an energy efficiency study for a large customer.
Scenario: Load research performs end use studies by customer segments
Load researchers can use interval metering data provided from AMI meters but can gain additional
information from customers who volunteer to have sub-metering devices installed on loads within their
premise. The sub-metering devices communicate their information back to the utility through the AMI
network.
Page 26 of 36
Not proposed. Stakeholder input on
customer data privacy is desired.
Technical requirement to support
communication of sub-metering devices.
ISSGC Potential Categories and Scenarios
Scenario: Load research performs study on distributed generation
Load researchers can use AMI interval data and sub-metering devices on distributed resources to better
understand how customers use their distributed resources.
Scenario: Load research performs a study on the effectiveness of demand response programs
Recorded interval usage data can be marked with an identifier indicating a particular demand response
event was underway when the data was recorded. Post event analysis of the data helps the utility
understand the effectiveness of their demand response programs.
Scenario: Load research performs study of load on individual circuits
Load researchers can sum the interval AMI meter usage data from customers on a circuit to improve their
knowledge of circuit loading.
Scenario: Load research provides dynamic load profiles for customer classes to web site
Customers can view their energy usage compared to anonymously aggregated customers with similar
usage characteristics.
Category: Distribution operator controls the distribution system using AMI data
The operator of the distribution network can use AMI data to make decisions about how to reconfigure the
network. These are not long-term planning scenarios, but situations that affect reliability where a decision
must be made immediately to prevent various types of outages.
Page 27 of 36
Not proposed. Stakeholder input on
customer data privacy is desired.
Technical requirement to support
communication of sub-metering devices.
Not proposed. Stakeholder input on
customer data privacy is desired.
Lower priority. ComEd and Ameren feel
that they already have adequate circuit
load data.
Not proposed. Stakeholder input on
customer data privacy is desired.
This category has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
ISSGC Potential Categories and Scenarios
Scenario: Operator uses historical metering measurements to reconfigure feeders
Each day, the AMI system gathers load profile data and peak load information about individual distribution
transformers and switches by aggregating data from customer meters. When a circuit threshold alarm
occurs, the distribution management system collects and presents an appropriate subset of this
information to the operator, along with current and historical loading information gathered at the circuit
level by the SCADA system. The distribution management system uses this data to calculate and present
a load estimate for all the transformers and switches in the circuit which raised the alarm and on adjacent
circuits. Note that while the distribution management system calculates the load estimates in real time, the
metering data the estimates are based on is historical data gathered the previous day by the AMI system.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
With the help of these estimates and the supporting data, the operator makes a decision to move some
portion of the load to other circuits. This decision can be made faster and more reliably because the
operator is using historical load profile data that is: gathered the previous day, removing the effect of
seasons and recent network changes, gathered from the specific area where the problem is actually
occurring, not averaged or idealized from similar circuits, and aggregated for each particular segment or
transformer point, not just each circuit as a whole.
Scenario: System operator uses AMI data for localized load reduction to relieve circuit overloading
Similar to the previous scenario, but the operator is also provided with estimates of how various demand
response programs would reduce load in the affected area. The operator can then initiate the appropriate
demand response program to reduce load on the affected circuits.
Scenario: System Operator uses AMI technology to perform a planned switching operation
The operator uses AMI based historical load data to shift load to other circuits for planned activities such
as construction, maintenance and inspection activities.
Page 28 of 36
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
ISSGC Potential Categories and Scenarios
Scenario: Control center directs the system operator to control distributed resources for planned
islanding and reconnection to grid
The system operator can use the AMI communications network to determine the appropriate action to take
in an islanding situation. It assumes there is a regulatory environment that permits distributed resource
control and islanding to take place and that distributed resource infrastructure is communicating and
compatible with the AMI communication system. The operator uses historical AMI data in conjunction with
SCADA data to perform switching operations that balance the capacity of the distributed resources with
the load of the surrounding island.
Category: Distribution planner uses AMI data to optimize asset utilization
Using the AMI system, it is possible to know with much greater accuracy how much energy is flowing
through transformers at any given time, and therefore create an actual load profile for that transformer
based on measured data. This capability provides a number of potential benefits, including: proactively
predicting failure and replacing overloaded transformers, knowing whether a transformer is suspect when
investigating voltage complaints, correctly sizing replacement transformers, and reducing unplanned
outages.
Scenario: Utility gathers circuit and transformer load profiles
A utility system uses daily AMI usage data to determine the load profile for circuits and transformers.
Scenario: Planners improve transformer utilization using AMI data
The utility system regularly reports transformer statistics and remaining life predections.
Scenario: Utility uses AMI technology to support condition based predictive asset replacement
programs
The utility uses sensors on the transformers and other distribution equipment communicate alarm
conditions through the metering system to the appropriate organizations in the utility.
Page 29 of 36
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
ISSGC Potential Categories and Scenarios
Scenario: Planners schedule maintenance using AMI meter load data
Planners use exception reports generated from the transformer loading data to schedule maintenance
work.
Category: Planners perform analytics using historical AMI data
System planners can use historical information on the loading of circuits, segments, and branches to
develop long term planning forecasts (1 yr/5 yr/10 yr) and to inform decision making as to which sections
of the distribution system should be targeted and prioritized with investment capital (and which should not)
for upgrades, load growth projects, etc. Additionally, reliability reports and analyzing the impact of
customer choices on the grid, such as demand response participation and integration of distributed
generation is supported.
Scenario: Planners assess load growth and pattern at segment or branch level using meter load
data
Planners and utility systems aggregate customer load information and store peak loading information for
each distribution component in the planning data warehouse. Planners can then query this loading data to
evaluate growth at the segment or branch level.
Scenario: Planners identify capital deferral options by profiling equipment loading based on meter
data
Planners use data similar to the previous scenario but focus on conducting equipment (transformers,
switches, and capacitor banks) rather than particular circuits or segments.
Scenario: Forecaster creates 1, 5 and 10 year residential, commercial, and industrial planning
forecasts using AMI data
Planners use aggregate customer load data to create planning forecasts.
Page 30 of 36
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
ISSGC Potential Categories and Scenarios
Scenario: Utility automatically creates reliability reports from AMI data
A utility engineer can generate reliability reports suitable for submittal to a regulator, derived from power
quality information reported by AMI meters.
Scenario: Planners analyze grid impacts from increasing demand response and distributed
resources using AMI data
Planners can correlate loading patterns with customer characteristics in order to determine how demand
response and distributed resources affect loading.
Category: Utility manages utility owned distributed generation
Utilities stand to benefit from distributed generation. Distributed generation can reduce the peak loading on
the grid. It can also help support line voltage at the end of long distribution circuits. The utility can install
generation to supplement or defer grid upgrades where space, economics, or other constraints prevent the
expansion of substations or the building of new distribution lines. An example of this would be installing
distributed generation to improve service near isolated loads currently supplied by a long transmission line.
Scenario: Utility uses AMI or other network infrastructure to meter power generated by utility
owned distributed generation
The utility uses a network to meter utility owned distributed generation and delivers status and production
data to a variety of users including: the RTO, automatic generation control, grid control center, resource
forecasting and planning, and to validate delivery of renewable energy.
Scenario: Utility uses AMI or other network infrastructure to communicate with utility owned
distributed generation for control and status
The utility exercises real time control and receives status data from the utility owned distributed
generation.
Page 31 of 36
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
This scenario has lower priority for
ComEd and Ameren due to existing
circuit load measurement capability.
Low priority. ComEd and Ameren
indicated low priority for utility owned
distributed resources.
Low priority. ComEd and Ameren
indicated low priority for utility owned
distributed resources.
Low priority. ComEd and Ameren
indicated low priority for utility owned
distributed resources.
ISSGC Potential Categories and Scenarios
Category: Generation dispatch is optimized to balance renewable variability
One of the obstacles to achieving higher penetration of renewable energy such as wind and solar power is
the variable nature of these resources. Monitoring the real-time status of renewable energy resources can
increase the RTO’s and utility’s effectiveness in handling this variability. Possessing real time status
information about renewable resources allows the RTO to fill any energy shortfalls (or address any
surpluses) to preserve grid stability.
Scenario: Renewable generation status is monitored to inform decisions for adjusting use of
energy storage or conventional generation to manage renewable variability
A hypothetical 100MW wind farm connects to the grid and supplies electricity in the scheduled forward
market without causing grid instability in the operating hour. Real time monitoring of this variable resource
allows the RTO to respond to unexpected changes in generation output caused by climatic variability. In
this scenario the wind farm experiences a decrease in generation output, below their scheduled output.
The RTO responds by filling the gap with automatic generation control (AGC) energy and energy from the
real time energy balancing market. One of the ways in which the RTO might balance energy supply and
demand is through the deployment of energy storage resources.
Category: Power system automatically triggers flexible AC transmission system (FACTS) devices
using phasor data to maintain system stability
The utility uses coordinated phasor measurement data and FACTS devices to maintain system stability
following a major destabilizing event. Phasor data measures the physical characteristics of voltage and
current waveforms, including phase angle and frequency oscillation. If frequency oscillation is identified,
the utility’s hypothetical predictive grid control system would calculate an optimal oscillation damping
strategy, and send control messages to FACTS devices to execute the damping strategy.
Scenario: Predictive grid control system maintains grid stability by engaging appropriate FACTS
devices (e.g. static VAR compensators) in response to grid abnormalities detected by the phasor
monitoring system
Phasor measurement units detect and respond to a hypothetical 3-phase line fault that results in a line and
generator trip. The utility’s predictive grid control system (PGCS) analyzes the data and determines whether
power system stabilizing is required. If system stability is required PGCS would then calculate an optimal
strategy for damping the oscillations and send control messages to appropriate FACTS devices.
Page 32 of 36
This category assumes the existence of
economical energy storage devices.
Other requirements may be out of scope
for the ISSGC.
This scenario assumes the existence of
economical energy storage devices.
Other requirements may be out of scope
for the ISSGC.
Transmission system scenarios that have
little or no interface requirements to the
distribution system or customers are
considered to be generally out of scope
for the ISSGC. The ISSGC will discuss
these scenarios at a high level to
understand system wide impacts.
Transmission system scenarios that have
little or no interface requirements to the
distribution system or customers are
considered to be generally out of scope
for the ISSGC. The ISSGC will discuss
these scenarios at a high level to
understand system wide impacts.
ISSGC Potential Categories and Scenarios
Category: Utility uses online dissolved gas monitoring to detect emerging failures of transformer
banks and take corrective action
Deployment of online dissolved gas analysis (DGA) devices could improve the utility’s monitoring,
maintenance, and operation of transmission-level substation transformers. Online DGA allows the utility to
monitor transformer condition levels as frequently as once per hour. The increase in monitoring frequency
would allow the utility to identify transformers in need of repair or replacement prior to failure. It would also
enable the utility to optimize transformer utilization over their life spans. The business value of this
enhanced transformer monitoring includes reduced risk, improved reliability, more efficient use of capital,
and enhanced analytic capabilities.
Scenario: Utility receives indication of preemptive failure from transmission transformer’s onlineDGA device and transfers load off of bank to prevent failure
The utility can use online dissolved gas analysis (DGA) devices to identify substation transformers with
dissolved gas levels at a “critical” state. If certain rule conditions are met EMS sends a “critical” alarm to
the EMS operator who would clear the transformer bank.
Category: Centralized remedial action scheme system monitors grid system status and exerts
control to maintain system stability and prevent overloads
Improved high speed communications and computing can allow the utility to implement a centralized
remedial action scheme architecture that detects and responds to abnormal system conditions in a
coordinated manner. The centralized nature improves upon traditional remedial action schemes which are
limited in their ability to consider system wide operating conditions.
Scenario: Centralized remedial action scheme (CRAS) system detects line outage and arms
appropriate RAS scheme
The CRAS process is initiated by relays which measure the grid condition by capturing “real power” line
flows, load levels, generation output, and the general grid condition (voltage, current, etc.). This data is
transmitted to the CRAS control system, which evaluates the data to determine whether any remedial
action schemes (RAS) require arming. The CRAS control system performs this evaluation on a new data
set every 100 milliseconds. It decides to arm a remedial action scheme if line flows exceed predetermined
thresholds. If a RAS is armed and a relay subsequently detects a line outage, the relay transmits an
outage signal to the CRAS control system which prepares to activate the remedial action scheme. The
CRAS control system determines the amount of generation to be tripped and/or load to be shed for the
armed action scheme, then sends control commands to relays which activate the mitigation strategy.
Page 33 of 36
Level of detail not appropriate for ISSGC.
This category describes a very specific
application of asset management.
Level of detail not appropriate for ISSGC.
This scenario describes a very specific
application of asset management.
Transmission system scenarios that have
little or no interface requirements to the
distribution system or customers are
considered to be generally out of scope
for the ISSGC. The ISSGC will discuss
these scenarios at a high level to
understand system wide impacts.
Transmission system scenarios that have
little or no interface requirements to the
distribution system or customers are
considered to be generally out of scope
for the ISSGC. The ISSGC will discuss
these scenarios at a high level to
understand system wide impacts.
ISSGC Potential Categories and Scenarios
Category: System operator uses condition based monitoring data to determine asset maintenance
needs
Included as part of the ‘Asset
Management’ category.
The utility can use remote sensor devices to proactively monitor equipment in the field to make
maintenance decisions based on the current conditions of those assets. In a condition based maintenance
approach, remote sensors provide operational and non-operational data to utility back office systems both
periodically (e.g. every 10 minutes or every hour), and upon an event occurring. Analyses are
automatically performed on sensor data using rules and algorithms that identify assets in need of repair or
replacement. This approach to monitoring and maintaining assets would enable the utility to identify
equipment needing repair or replacement prior to failure. It would also allow the utility to optimize asset
utilization over the life of the asset. The benefit of condition based monitoring includes reduced risk,
improved reliability, more efficient use of capital, operational improvements and enhanced analytic
capabilities.
Scenario: System operator determines level of severity or risk of impending asset failure and takes
corrective action
Proposed
A hypothetical utility diagnostic system receives data from remote sensors monitoring the condition of
system assets. Asset specific health rules and algorithms are used to calculate metrics for the assets
which determine when to notify the operator and to suggest operational actions. Asset engineers would be
notified of conditions of lesser criticality and would determine maintenance or other actions.
Category: Utility provides services to Plug-in Electric Vehicle (PEV) Customer
Proposed
Plug in electric vehicles will have a significant impact on the future electric system and challenge the utility
and customer to manage vehicle connection and charging. As adoption rates of electric vehicles increase,
the utility will have to handle the new load imposed on the electrical system. Scenarios will consider
customer payment issues regarding mobility, load shifting vehicle charging and the use of electric vehicles
as a distributed resource.
Scenario: Customer connects PEV to energy portal at their premise location
Proposed
Customers could enroll in a utility PEV program which provides incentives to charging their vehicles at
specified times. For this scenario, the customer is attempting to charge a PEV under a selected PEV tariff
that may provide for the opportunity to fuel a vehicle at a lower cost during off peak periods.
Page 34 of 36
ISSGC Potential Categories and Scenarios
Scenario: Utility provides billing services to PEV Customer
The utility may provide billing information that indicates the amount of energy provided to the PEV and not
aggregated with the rest of the premise energy consumption. The utility may also be able to provide PEV
billing charges for other participating utilities that have agreed to exchange information or participate in a
PEV charging clearinghouse program.
Scenario: Customer connects PEV to energy portal at another premise and premise customer pays
for energy use
A customer plugs their PEV into another premise (not their own, but one serviced by the same utility),
where the premise owner is responsible for the cost of energy delivered to the PEV charged at the
premise.
Scenario: Customer connects PEV to energy portal at another premise and PEV customer pays for
energy use
A customer plugs their PEV into another premise (not their own, but serviced by the same utility), where
the PEV operator is responsible for the cost of energy delivered to the PEV charged at the premise.
Scenario: Customer connects PEV to energy portal at another premise outside the enrolled utility’s
service territory
A customer plugs their PEV into another premise (not their own, and not serviced by the same utility (i.e..
roaming utility), where the PEV operator is responsible for the cost of energy delivered to the PEV charged
at the premise.
Scenario: Customer is enrolled in a PEV demand response program (Direct Load Control) and PEV
(or PEV customer) receives and responds to discrete demand response events
Customers could enroll in a PEV demand response program (possibly in exchange for reduced tariffs), this
program would allow the utility to request an automated load reduction at the customer site by issuing
event information to the PEV. The customer could override and opt out of the request in exchange for a
reduced incentive.
Page 35 of 36
Not proposed. Primary scenario
requirements are met by previous
scenario.
Considered to be a sub-scenario of
‘Customer connects hybrid electric
vehicle to energy portal’.
Considered to be a sub-scenario of
‘Customer connects hybrid electric
vehicle to energy portal’.
Considered to be a sub-scenario of
‘Customer connects hybrid electric
vehicle to energy portal’.
Proposed
ISSGC Potential Categories and Scenarios
Scenario: Customer is enrolled in a periodic or hourly pricing price response program and the PEV
receives and responds to periodic or hourly energy prices
Customers could enroll in programs that provide time varying rates for vehicle charging. The rate schedule
could be communicated a day ahead or on some other schedule.
Scenario: Customer uses stored energy to operate premise as an island (Vehicle-to-Home or V2H)
The customer could use the energy storage in their PEV to serve load at their premise during a power grid
outage. Energy storage onboard the PEV could be used by a customer energy management system to
support customer essential loads. The utility does not provide control signals to the PEV in this scenario.
Scenario: Utility controls PEV to supply energy to grid (Vehicle-to-Grid or V2G) by discharging
stored energy
A customer has enrolled in a utility program to enable their PEV to supply energy to the grid. The utility is
given permission to control the discharging of the energy storage onboard the PEV within parameters and
preferences set up by the customer. The utility may use this capability to support grid operations in time of
high energy prices or for economic dispatch or system reliability.
Scenario: Utility controls PEV to supply energy to grid by optimizing charging (V2G)
A customer has enrolled in a utility program to enable PEVs to supply energy to the grid. The Utility is
given permission to optimize the charging of the energy storage onboard the PEV within parameters and
preferences set up by the Customer. The utility may use this capability to support grid operations in time of
high energy prices or for economic dispatch or system reliability.
Page 36 of 36
Proposed. Included in ‘Plug in hybrid
electric vehicle or customer receives and
responds to utility price signals’.
Requirements for this scenario are all on
customer devices. ISSGC can provide
some high level guidance.
Communication and interface
requirements are similar to other
distributed resource and demand
response scenarios. ISSGC can provide
some high level guidance.
A variant of this scenario was proposed
where the customer’s vehicle is charged
on a schedule managed by the utility.