Professional Documents
Culture Documents
"Acknowledgment: This material is based upon work supported by the Department of Energy
under Award Number DE-OE0000193."
Disclaimer: "This report was prepared as an account of work sponsored by an agency of the
United States Government. Neither the United States Government nor any agency thereof,
nor any of their employees, makes any warranty, express or implied, or assumes any legal
liability or responsibility for the accuracy, completeness, or usefulness of any information,
apparatus, product, or process disclosed, or represents that its use would not infringe
privately owned rights. Reference herein to any specific commercial product, process, or
service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute
or imply its endorsement, recommendation, or favoring by the United States Government or
any agency thereof. The views and opinions of authors expressed herein do not necessarily
state or reflect those of the United States Government or any agency thereof."
Version History
Rev. Date Author Change description
1.6 4-6-2010 Brian D. Green Clean-Up
2.0 4-10-2010 John Simmins Fill in blanks and narrative and description
3.3 4-22-2010 Brian D. Green Add AEP comments and diagrams
Summary:
Advanced Metering Infrastructure (AMI) is a transforming technology that has broad impact on the energy
market and its consumers. AMI allows utilities to balance supply, demand, and capacity making a smarter,
more efficient, grid by pushing aspects of grid monitoring and control out to the endpoints of delivery.
Stakeholders are implementing the systems and technologies required to deploy AMI today.
Advanced Metering Infrastructure (AMI) is a two-way communication system that can reach every device
in the distribution space. The industry focus in embracing AMI as opposed to Automatic Meter Reading
(AMR) is that the communication system is not dedicated to a single application. Instead, AMI is a flexible,
general-purpose communication system that can be used for many applications – including meter reading,
distribution automation, connect/disconnect, and others.
AMI systems promise to provide advanced energy monitoring and recording, sophisticated tariff/rate
program data collection, and load management command and control capabilities. Additionally, these
powerful mechanisms will enable consumers to better manage their energy usage, and allowing the grid
to be run more efficiently from both a cost and energy delivery perspective. These advanced capabilities
will also allow utilities to provision and configure the advanced meters in the field, offering new rate
programs, and energy monitoring and control.
Narrative:
This Use Case handles the transfer of any data element from the AMI Head-End to the Smart Meter. It is
intended to be an intermediary Use Case, called and reused by many other Use Cases, The Use Case
provides for scenarios such as meter to meter, relay to meter, and relay to relay to meter communications
paths. It hides the complexity of the Access Point sending messages directly to a Smart Meter NIC and
to a Smart Meter through a combination of Relays and Smart Meters.
Interface Diagram:
Operations
AMI-Head End
AMI Head-End 1 DR Application
39
50
Distribution
Access Point 51
Relay 53 Relay
52
54 54 54
54
56 56 56 56
Smart Meter
Smart Meter Smart Meter Smart Meter Smart Meter
Customer
Customer
Note(s):
The interface between the AMI Head-End and the Access Point includes: LAN, Firewall/DMZ,
Backhaul Router, Backhaul Network, Backhaul Gateway.
Message relaying / routing may occur amongst various combinations of Access Point, Relays and
NICs.
Actor(s):
The list of the actors and the roles that are participating in this use case described in the table below.
The participating business function, its acronym and what they provide in this use case are
detailed in the table below.
• Standard International Electrotechnical Commission (IEC) 61968 Message Definition format will
be followed to provide the Header, Request, Reply, and payload used when defining the
messages for the design specifications. For the purpose of the use cases identified in this
document these have been omitted as they are to be provided in the design specification for the
AMI Network use case.
Normal Sequence:
The sequences of events, showing the order in which they ocurr during the typical progression of
this use case are provided in the table below. The Sequence Diagram that graphically depicts
the events is presented immediately following the table.
1.1 Data needs AMI Head-End sends Data Elements AMI LAN
to be sent Data Elements to the that need to be Head-
from AMI LAN sent to the End
Head-End Smart Meter
to Smart
Meter
1.2 LAN sends Data Data Elements LAN Firewall/
Elements to the that need to be DMZ
Firewall/DMZ sent to the
Smart Meter
1.3 Firewall/DMZ sends Data elements Firewall/ Backhaul
Data Elements to the that need to be DMZ Router
Backhaul Router sent to the
Smart Meter
1.4 Backhaul Router sends Data elements Backhaul Backhaul
Data Elements to the that need to be Router Network
Backhaul Network sent to the
Smart Meter
1.5 Backhaul Network Data elements Backhaul Backhaul
sends Data Elements to that need to be Network Gateway
the Backhaul Gateway sent to the
Smart Meter
1.6 Backhaul Gateway Data elements Backhaul Access
sends Data Elements to that need to be Gateway Point
the Access Point sent to the
Smart Meter
1.7A. Access Point sends Data elements Access NIC
1 Data Elements to NIC that need to be Point
sent to the
Smart Meter
1.7B. Access Point sends Data elements Access Relay
1 Data Elements to Relay that need to be Point
sent to the
Smart Meter
Integration Scenarios
Adapters will use the Common Information Model (CIM) in Extensible Markup Language (XML) to send
and receive messages and events.
The following are the points of integration that must be tested for this use case. Other non-CIM message
interfaces may be testable in this use case.
Pre-conditions:
The following conditions that MUST be met before this use case can occur.
• All elements of the AMI Network are proprietary in nature and are part of a whole; thus cannot
work in isolation of each other.
• Telecomm links are required between AMI Network elements and these links are implemented
differently depending on geography, availability, coverage and throughput (private, public, land-
line, wireless).
Post-conditions: None
The following events or actions that may happen after or be caused by the completion of the normal use
case events, as well as the exceptions or alternative sequences are:
There are no exceptions, unusual events or alternate sequences defined for this use case.
An XML Schema Definition (XSD) diagram shows the normative and informative parts of the
message. Not all of the International Electrotechnical Commission’s (IEC) – CIM message
optional elements must or will be used in the use of IEC – CIM for this specific use case.
References:
Issues: None
ID Description Status