outage notification - epri | smartgrid resource …smartgrid.epri.com/usecases/outage...

American Electric Power 4.5 Advanced Metering Infrastructure

Document ID: Use case #

5.4

Title: Outage Notification Use Case

Subject Matter Expert: Author: Reviewed by: Frank Wilhoit and Margaret Goodrich

Bill Mullenmaster Tim Simmons

Copyright © 2011 American Electric Power Company

Outage Notification

Version History Rev. Date Author Change description

A 02/22/2011 Bill Mullenmaster Initial Release

B 03/08/2011 Bill Mullenmaster Updates with internal review comments - based on reviews to include CIS, MDM, and XSD images instead of message definitions.

C 03/10/2011 Bill Mullenmaster Updates with CIS outage integration from OMS

D 3/14/2011 Bill Mullenmaster Changed assumptions for the use case and changed the scope to be OMS centric.

E 08/08/2011 AEP workshop Various updates F 9/9/2011 Tim Simmons Implement various updates

G 10/12/2011 Brian D. Green Add Narrative, Interface Diagram, Notes section and update Actors and steps

H 10/31/2011 Ron Cunningham Final team review

"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."



5.4




of 14 Copyright © 2011 American Electric Power Company Rev. 9

Summary:

This use case addresses the Outage Notification message generated by the Smart Meter and how this message gets generated into a trouble ticket.

Narrative:

Many AMI systems offer endpoints with a “last gasp” message transmission capability to tell the utility that the endpoints have lost power. This last-gasp transmission serves as a surrogate for the customer’s call. AMI systems using thes “last gasp” capabilities work well in helping the Outage Management System (OMS) and dispatcher understand and efficiently respond to widespread outage conditions.

This Use Case is unique as it is initiated at the NIC when it detects a zero voltage event lasting more than a programmed period of time. The NIC will issue a last gasp message that flows back to the enterprise without any request from an enterprise system. The Last Gasp Message is routed through the AMI Network to the AMI Head-End. The AMI Head-End sends the message to the ODS and the Outage Filter. The Outage Filter sorts the message(s) and sends it to the Trouble Ticket System (TTS). TTS sends the message to the OMS and the ODS. The OMS system updates the outage ticket and sends the update to TTS and ODS.



5.4





Interface Diagram:

AMI Head-End

Smart Meter

Operations

Customer

AMI Network

2

3

Trouble Ticket SystemOMSODS

Outage Filter

4029

35 34

44

89

Note(s):

The NIC is a part of the Smart Meter.



5.4





Actor(s):

The list of the actors and the roles that are participating in this use case described in the table below.

Name Role description

AMI Head-End The AMI Head-End is the back office system than controls the Advanced Metering Infrastructure.

NIC AMI network interface component with Meter Metrology Board within the Smart Meter.

ODS Operational Data Store is a sub-system of AEP’s data warehouse, which stores operational data i.e. all metering events and messages.

OMS Outage Management System.

Outage Filter Filters outage messages for OMS and the Trouble Ticket System

Trouble Ticket System Distribution Trouble Ticket System.

Participating Business Functions:

The participating business function, its acronym and what they provide in this use case are detailed in the table below.

Acronym Business Function/Abstract Component Services or Information Provided

NIC The AMI network interface with Meter Metrology Board within the Smart Meter that provides the Last Gasp notification to the AMI system

The Meter provides electrical service to the Utility customer. The Smart Meter has only a short period of time to communicate the loss of service to the AMI system, without a guarantee of notification delivery.

AMI Head-End Provides communications with the Smart Meters in the field and processes last gasp information that is provided from the meter at the time a meter is reporting a zero voltage has been detected.

Provides the event notification that indicates the meter has identified a zero voltage condition, sent through a last gasp event.

Outage Filter The Outage Filter provides filtered Last Gasp event information received from the AMI system to the Trouble Ticket System. This allows filtering of false last gasps and very short term outages.

Filters events received as a result of the AMI Meter reporting a last gasp event, before sending properly vetted events on to the Trouble Ticket System. Such filtering avoids unnecessarily involving the OMS.



5.4





Acronym Business Function/Abstract Component Services or Information Provided

OMS Outage Management System is a system composed of a network model and rules-based apps used to improve the response to reported outages and speed restoration of power to customers.

Notified of outage occurrences as a result of receiving Last Gasp notifications sent from the Trouble Ticket System.

TTS The Trouble Ticket System is responsible for trouble ticket creation and notifying systems with the creation and changes of trouble ticket information

The Trouble Ticket System creates a Trouble Ticket from Last Gasp Notifications sent from the Outage Filter system.

ODS The Operational Data Store stores status information for assets such as a meter asset for meter reading and device status.

Stores messages and events sent from various systems including the AMI Head-End, Trouble Ticket System and OMS.

AMI Advanced Metering Infrastructure for energy monitoring and recording, load control capability, tariff/rate data collection.

Energy monitoring and control, configuration of advanced meters, offers new rate programs, distribution automation, Meter Readings, Meter Events and Alarms.

Assumptions / Design Considerations:

• Standard International Electrotechnical Commission (IEC) 61968 Message Definition format will be followed to provide the Header, Request, Reply, and Payload when defining the messages for the design specifications. For the purpose of the use case identified in this document these have been omited as they are to be provided in the design specification for the OMS use cases.

• The Common Information Model (CIM) IEC 61968 Messages identified in this use case are to follow an asynchronous message format which expects no response as a result of the AMI Head-End, Outage Filter, ODS, OMS, and Trouble Ticket system processing of the messages that are identifed in these use cases. The Created verbs that are used in this use case represent an action that has already occurred in the system from which the message originated, where the systems receiving the message will process the message and have an end result internally as a consequence of the action that has occurred in the system that sent the message.

• The Outage Filter sends the meter energized status change for the Meter Asset to the Trouble Ticket System.

• The OMS provides the outage creation message to the ODS system to be able to track outage restoration information about the Meter Last Gasp. ODS will store the outage and meter relationship for the last gasp status so that the information can be updated accordingly.

• In some Smart Meters, the reporting of lose or restoration of service voltage to the meter is a function of the Meter Metrology Board and it’s sending out specific messages that are then



5.4





forwarded by the NIC Smart Meter component. It is assumed that the Created/EndDeviceEvent message would conform to the same formats as the message from Meter Metrology Board component in the Smart Meter.

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.

Use Case Step

Triggering Event

Description Of Process Information To Be Exchanged

Producer Receiver Message Type

1 NIC detects a loss of meter service voltage

NIC creates an Internal Last Gasp Notification and Meter ID information Message

Internal Last Gasp Notification and Meter ID information

NIC Internal Proprietary

2 NIC sends Last Gasp Notification and Meter ID information Message to AMI Head-End via the AMI Network


NIC AMI Network

Proprietary

3 AMI Network routes Last Gasp Notification and Meter ID information Message to AMI Head-End


AMI Network

AMI Head-End

Proprietary

4 AMI Head-End creates an “EndDevice Event”

Internal AMI Head-End

Internal Created/EndDeviceEvent

5 AMI Head-End sends “EndDeviceEvent” message to Outage Filter

“CreatedEndDeviceEvent” message

AMI Head-End

Outage Filter

Created/EndDeviceEvent

6 AMI Head-End sends “EndDeviceEvent” message to ODS


AMI Head-End

ODS Created/EndDeviceEvent



5.4





Use Case Step

Triggering Event



7 Smart Meter Last Gasp Outage message received

ODS creates the end device status for the NIC (Smart Meter) that sent the Last Gasp notification

Internal ODS Internal Internal Message / Processing

8 Smart Meter Last Gasp Outage message received

Outage Filter discards events that match up (Up Notification with Down Notification) which it receives in a short period of time – no throttling is done,

internal Outage Filter

internal internal

9 Outage Filter sends “EndDeviceEvent” message to the Trouble Ticket System.


Outage Filter

Trouble Ticket System

Created/EndDeviceEvent

10 The Trouble Ticket System creates a trouble ticket as a result of the Last Gasp Outage event for the NIC-ESI (Smart Meter)

Internal Trouble Ticket System

Internal Internal Message / Processing

11 The Trouble Ticket System sends “OutageRecord” message to OMS

“OutageRecord” message


OMS Create/OutageRecord

12 The Trouble Ticket System sends “TroubleTicket” message to ODS

“TroubleTicket” message


ODS Create/TroubleTicket

13 The Trouble Ticket System sends a trouble ticket creation notification for the NIC-ESP (Smart Meter) information to the OMS.

CreateTroubleTicket message


OMS Create/TroubleTicket



5.4





Use Case Step

Triggering Event



14 The OMS System updates the outage and trouble ticket information in OMS.

Internal OMS Internal Internal Message / Processing

15 The Trouble Ticket System gets the updated Trouble Ticket and outage record from OMS

Internal Trouble Ticket System

Internal Internal

16 OMS sends “CreateOutageRecord” message to ODS

CreateOutageRecord message

OMS ODS Create/OutageRecord

17 ODS receives “CreateOutageRecord” message and creates a record for storage.

Internal ODS Internal Internal Message / Processing



5.4







5.4





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.

Actor Interface Points

AMI Head-End • Outage Filter • ODS • NIC

Outage Filter • Trouble Ticket System Trouble Ticket System

• OMS • ODS

OMS • ODS

Pre-conditions: None

Post-conditions: None

Exceptions / Alternate Sequences:

There are no exceptions, unusual events or alternate sequences defined for this use case.

Use Case Step

Triggering Event





5.4





Message Type(s) Diagram:

The following 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.

EndDeviceEvent:



5.4





OutageRecord:



5.4





TroubleTicket:



5.4





References:

Use Cases or other documentation referenced by this use case include:

• 20100625 AEP Ohio Interoperability Plan V1.docx: Section 4.5.5 (Last Gasp Outage Notification); Section 4.5.6 (Outage Management System Ping)

• 20100625 Use Cases EPRI Report_V2.4.docx: Section 5.4.2 (Last Gasp Message); Section 5.5.2 (OMS Ping)

• 61968_9_MeterReadingAndControl_FDIS090428-final.docx: Section 5.2.2.1 (Outage Detection); Annex H (XML Schemas for message payloads) Section H.5 (EndDeviceEvents)

• IEC 61968-3 2003 (57_631e_CDV).pdf: Section 5.4 (OutageRecord, TroubleTicket

Message Types); Section 5.4.1 (Message Format)

Issues: None

ID Description Status

Miscellaneous Notes: None

outage notification - epri | smartgrid resource …smartgrid.epri.com/usecases/outage...

Documents