61968 Messages (Part 3, 6, 8, 9) - UCAIugcimug.ucaiug.org/Meetings/Melbourne2014... · 61968 Messages (Part 3, 6, 8, 9) CIM University Margaret Goodrich, Manager, Systems Engineering

61968 Messages (Part 3, 6, 8, 9) CIM University

Margaret Goodrich, Manager, Systems Engineering SISCO, Inc. 6605 19½ Mile Road Sterling Heights, MI 48314 USA Tel: +1-903-477-7176 Fax: +1-903-489-0063 E-Mail: [email protected]

Introduction • Information Model & Reference Model • Part 3 Network Operations

– Scope – Outage and FLISR Work Flows

• Part 6 Maintenance and Construction – Scope – Reference Model – Work Management System (WMS) Messages

• Part 8 – Scope – Reference Model – Customer Interface System (CIS) Work Flows

• Part 9 Meter Reading and Control – Scope – Reference Model – Metering Messages

Information Model for all Parts

• Classes for all Parts in the 61968 standard series are contained in IEC61968-Part 11 and IEC61970-301

• The classes and attributes may come from one or more of the packages contained in these documents.

WG14 Messaging Reference Model - Full

Key Outside the scope of 61968

61968 Part 9

Defined by other 61968 Parts

Service

Point

Metering System

Data Collection

Control and

Reconfiguration

[ 18 ]

[ 3 ]

Meter Maintenance

and

Asset Management

[ 2 ]

Meter

Data

Management

Customer

Information

and

Billing

[ 9 ]

[ 20 ]

[ 15 ]

{ 8 }

{ 14 }

[ 19 ]

[ 17 ]

{ 16 }

{ 11 }

Interface and protocol details of the

Service Point are outside the scope of

IEC 61968-9

[ 5 ]

[ 21 ]

[ 1 ]

Planning

and

Scheduling

[ 7 ]

[ 7 ][ 6 ]

[ 4 ]

[ 13 ]

[ 12 ]

{ 23 }

[ 22 ]

61968-3

61968-8

61968-5

[ 7 ][ 6 ]

[ 18 ]

[ 13 ]

{ 12 }

{ 12 }

[ 1 ] Account information

[ 2 ] Configuration, installation etc.

[ 3 ] Controls and signals

[ 4 ] Customer data set

[ 5 ] Data obtained by special read

[ 6 ] Demand response signals

[ 7 ] Disconnect/reconnect, demand reset

{ 8 } Install, remove, repair, disconnect, reconnect

[ 9 ] Load curves, Measurement history, etc.

[ 10 ] Load scenarios

{ 11 } Meter health and tamper detection

{ 12 } Meter history

[ 13 ] Meter readings

{ 14 } Meter service request

[ 15 ] On request read

[ 16 ] Outage and restoration verification

[ 17 ] Power reliability and quality events

[ 18 ] Readings, events and status

[ 19 ] Special read

[ 20 ] Tariffs, parameters

[ 21 ] Transaction information

[ 22 ] Transaction records

{ 23 } Tokens

Network

Operations

Work

Management

61968-6

Outage

Management

61968-3

[ 3 ]

Point

of

Sale

61968-10

[ 12 ]

{ 14 }

Load

Management

System

Load Analysis

Load Control

[ 10 ]

End-to-End Use Cases and Messages

Use Cases:

1. Initialize network

2. Non-telemetered fuse trips

3. Telemetered breaker trips

4. Tap for new subdivision

5. Maintenance on transformer

6. Meter replacement

Normal

State

Normal

State

Normal & asset

changes

Proposed normal

changes

Recommended normal

changes

Build Switching

Plan

Substation

IED

IED

IED

Device out &

fault dataDevice out &

fault data

Meters

down

Device out &

fault dataDevice Out

Device out

Energize

Switching Plan to energize

Fault location isolation steps

Restoration steps

AMI/

MDM

SCADA

OMS DMS

GIS Planning

Predict to

outage device Current

State

Current

State

Normal

State

Normal

StateCIS

WMS

MWF

Meter service

request

Meter service

order

Meter info &

complete

status

WMS

MWF

Isolation Steps

FLISR = Fault Location, Isolation,

and Restoration

Scope:

A - Outage Management

B - Network Model Synchronization

C - Maintenance

IEC61968 2011 Scope

Work

order

Current

State

Part 3 Scope

• An outage can be detected by: – AMI – Customer Call – Field Crew – SCADA

• An outage must be communicated between network operations systems, including trouble location, devices in abnormal state, and customers affected.

• Other Network Operations Fault Location, Isolation, and Supply Restoration (FLISR). – Fault location refers to the observations, signals, and analysis

necessary to identify the true cause of the outage. – Isolation is the process of switching and cutting that allows the fault

location to be safely isolated for repairs. – The process of restoring power to healthy islands of network around

the isolated area is referred to as supply restoration. • Other areas will be added to Part 3 as Use Cases are defined.

Outage Notification from a Field Crew

sd Outage Notification from Field Crew

«Fault Mgmt»

Part 3 - Network

Operation::NO-FLT

«Outage Analysis»

Part 3 - Network

Operation::NO-OA

«Trouble Call M...

Part 8 - Customer

Support::CS-TCMField Crew

Report Outage()

Created(Outage)

Created(Outage)

Outage Notification from a Field Crew

from to message description/payload

Field

Crew

NO-OA Report Outage

Field crew reports confirmed outage at known

location.

NO-OA NO-FLT Created

Outage

Notification of predicted outage at a specific

protective device in the network. This is a

confirmed protective device outage because it is

reported by a crew.

Payload:

- Protective Device ID

- Time of outage

- Status of device (phases on)

NO-OA CS-

TCM

Created

Outage

Notification of the customers out due to an outage.

Payload:

- Customer ID and time of outage for each

customer out.

- Estimated time of restoration of the outage.

Outage Notification from an AMI

sd Outage Notification from Meters

«Fault Mgmt»

Part 3 - Network

Operation::NO-FLT

«Outage Analysis»

Part 3 - Network

Operation::NO-OA

«Trouble Call M...

Part 8 - Customer

Support::CS-TCM

«AMI»

Part 9 - Meter

Reading and

Control::MR-AMIField Crew

Created(EndDeviceEvent)

Confirm Outage()

Outage Confirmed()

Created(Outage)

Created(Outage)

Outage Notification from an AMI from to message description/payload

MR-AMI NO-OA Created

EndDeviceEvent

AMI notifies of power off event at meter.

Payload: Meter ID, new meter status, and timestamp for change in meter

status.

NO-OA Field

Crew

Confirm Outage

Request field crew to confirm outage location.

Field

Crew

NO-OA Outage Confirmed

Field crew confirms outage location.


Outage

Notification of a confirmed outage at a specific protective device in the

network.

Payload:


- Time of outage


- Confirmed status (yes in this case)

NO-OA CS-TCM Created

Outage


Payload:

- Customer ID and time of outage for each customer out.


Outage Notification from a Customer

sd Outage Notification from Trouble Call

«Trouble Call M...

Part 8 - Customer

Support::CS-TCM

«Fault Mgmt»

Part 3 - Network

Operation::NO-FLT

«Outage Analysis»

Part 3 - Network

Operation::NO-OA Field Crew

Created(Outage)

Confirm Outage()

Outage Confirmed()

Created(Outage)

Updated(Outage)

Outage Notification from a Customer from to message description/payload

CS-TCM NO-OA Created

Outage

Notification of customer-reported outage.

Payload:

- ID and time of outage for each customer.

NO-OA Field

Crew

Confirm Outage

Request field crew to confirm outage location.

Field

Crew

NO-OA Outage Confirmed

Field crew confirms outage location.


Outage

Notification of a confirmed outage at a specific protective

device in the network.

Payload:


- Time of outage


- Confirmed status (yes in this case)

NO-OA CS-TCM Updated

Outage


Payload:

- Customer ID and time of outage for each customer out.


Part 6 Scope

• Specifies the information content for messages used to support business functions related to Maintenance and Construction.

• Typical uses of Part 6 messages include: – Planned Maintenance (Work Request)

– Meter Change Out (Service Order)

– Device Maintenance (Maintenance Order)

• Message types defined in other Parts of IEC61968 may also be relevant to these use cases.

Part 6 Reference Model

Operational

Planning &

Optimization

Network Operation

Simulation

(OP-SIM)

Network Operations

Fault Management

(NO-FLT)

Maintenance &

Construction - Field

Recording

(MC-FRD)

Mobile Workforce

[ 10 ]

[ 12 ]

Network Monitoring

NO-NMON

[ 1 ]

Customer Support

(CS)

Customer Service

CSRV

[ 11 ] Available / Used Materials

[ 12 ] Bill Of Materials / Material Status

[ 13 ] Crew Composition

[ 14 ] Actual Labor Cost

[ 15 ] Failure Event

[ 16 ] New/Updated or get Asset

[ 17 ] Special Read Request / Response

[ 18 ] Install, Remove, Repair, Connect and Disconnect

[ 19 ] Meter History

[ 20 ] Map

[ 21 ] Outage Notification from Field Crew

[ 22 ] Outage Confirmation Request

[ 1 ] SCADA Measurements, failures, conditions

[ 2 ] Switching Plan

[ 3 ] Request for Service

[ 4 ] Materials Reservation

[ 5 ] Request for Planned Maintenance/Inspection Work

[ 6 ] Request for Unplanned Work

[ 7 ] Follow-up Work

[ 8 ] Switching Order

[ 9] Work Request from Network Operations

[10 ] Work Order

[ 11 ]

[ 7 ]

[ 3 ]

Records & Asset

Management (AM)

General Inventory

Management (GINV)

Equipment hierarchy

[ 13 ]

[ 6 ]

Work Mgt Planning

[ 5 ]

Materials

Management

Crew

Composition

[ 4 ]

[ 16 ]

[ 2 ]

61968 Part 6


Key

[ 14 ]

[ 8 ]

{ 15 }

Scheduling & Dispatch

[ 13 ]

[ 10 ]

Maintenance & Construction

Maintenance and Inspection

(MC-MAI)

Preventive Maintenance

Conditional Maintenance

[ 9 ]

Meter Reading &

Control

(MR&C)

[ 17 ]

[ 18 ]

{ 19 }

[ 20 ]

[ 12 ]

[ 12 ]

[ 16 ]

[ 10 ]

[ 21 ]

[ 22 ]

Part 6 Business Functions and Components Business Functions Business

Sub-Functions

Abstract Components

Maintenance and

Construction (MC)

Maintenance and Inspection

(MAI)

Maintenance Orders

Maintenance Rules

Inspection/Maintenance History

Work Procedures

Construction (CON) Work Flow

Cost Reconciliation

Work Approval

Permits

Customer Billing

Tracking

Project Costing

Design (DGN) Construction Engineering

Estimating

Bill of Materials

Compatible Units

Field Recording (FLD) As-built Reporting

Time Reporting

Asset Condition

Scheduling and Dispatching

(SCHD)

Resource Management

Work Planning

Work Allocation

Material Requisitioning

Planned Maintenance Use Case

• Triggered by maintenance and inspection, or by periodic schedule for work.

• Example activity is tree trimming or major maintenance on a power transformer.

• Uses Work Request message

Planned Maintenance Use Case

sd Carry out planned maintenance with temporary equipment

Part 6 - Maintenance

and

Construction::MC-MAI

«Work Sched & Di...


and

Construction::MC-SCHD

«Subst. & Network ...

Part 4 - Records and

Asset

Management::AM-EINV

«Geographic Inv.»

Part 4 - Records and

Asset

Management::AM-GINV

«Field Recording»


and

Construction::MC-FRD

«Network Ctrl»

Part 3 - Network

Operation::NO-CTL

Create(WorkRequest)

Create(OutageBooking)

Created(BookedOutage)

Create(MaintenanceOrder)

Get(Map)

Reply(Map)

Get(Asset)

Reply(Asset)

Create(MaintenaceOrder)

Execute(WorkOrder)

Changed(MaintenanceOrder)

Close(MaintenanceOrder)

Closed(WorkRequest)

Work Request Message

Meter Change Out Use Case

• May include one or more Meter Service Work items

• Each item may refer to a max of two meters to provide a means to replace a meter.

• Meter readings can be obtained as a part of the work.

• A Meter Service Request occurs due to:

– Change out a Meter due to a Problem (Alarm, Complaint or other event)

– Change out a Meter for Recalibration

Meter Change Out Use Case

• When a Meter Change-Out is performed the following steps must occur: – Send a MeterServiceRequest to the WMS

– Send a Meter Technician to:

• Take the final Meter Reading

• Remove the old Meter

• Install the new Meter

• Take the new Meter Reading

– The following messages are sent/received to Configure the Meter:

• EndDeviceConfig

• CustomerMeterDataSet

• MeterConfig

• MeterReadSchedule

Change-Out Meter Work Flow

Service Order Message

Part 8 Scope

• Specifies the information content for messages used to support business functions related to Customer Service and Trouble Call Management.

• Typical uses of Part 8 messages include:

– Trouble Ticket

– Incident Information

– Service Request

– Customer Agreement

• Message types defined in other Parts of IEC61968 may also be relevant to these use cases.


Part 8 Customer Support (CS)

Customer

service (CSRV)

Trouble Call

Management

(TCM)

(3) Trouble Call

Management

(NO)

(6) Maintenance

and construction

(MC)

Other Systems

61968 Parts 3-9

(1) (2) (3) (5)

1. Trouble Ticket

2. Incident Information

3. Service Request

4. Work Request

5. Customer Agreement

6. Service Request

(4)

(6)

Part 8 Business Functions and Components Customer Support (CS)

Customer service (CSRV)

Service requests

Construction billing inquiry

Billing inquiry

Work status

Self-service inquiry

Customer connection

Turn on, turn off

Line losses

Service level agreements

Customer information analysis

Customer Information

management

Customer relationship

management

Trouble call management (TCM) Outage calls

Power quality

Planned outage notifications

Media communication

Performance indices

Restoration

projection/confirmation

Outage history

Point of sale (POS)

Trouble Ticket Use Case

sd Trouble Ticket

CS-TCM

(from Approved Actors)

NO-FLT


Call taker takes all

the relevent info

from the customer

and enters the

calls in the call

tracking

application()

Created(TroubleTicket)

Obtain connectivity topology ()

Reply(TroubleTicket)

Trouble Ticket XSD

Incident Information Use Case

sd Incident Information

NO-FLT


CS-CSRV


Update(IncidentInformation)

Update associated trouble ticket()

Incident Information XSD

Service Request Work Flow

sd Serv ice Request

MC-SCHD


CS-TCM


Customer or person creates a

service request()

CreatedServiceRequest()

Service Request XSD

Customer Agreement Use Case

sd Customer Agreement

Customer Support

(from Approved

Actors)

EXT-SAL

(from Approved

Actors)

CreatedCustomerAgreement()

Customer Agreement XSD

Part 9 Scope

• To Define the exchange of information between a Metering System and other systems within the Utility enterprise

• Specifies the information content of a set of message types that can be used to support many of the business functions related to Meter Reading and Control.

• Typical uses of the message types include: – Meter Event Messages

– Meter Control Messages

– Meter Reading Messages

Part 9 Scope

Enterprise

Applications

Head End

SystemsPAN

PAN

Device

PAN

Device

PAN

PAN

Device

PAN

Device

Meter

Meter or

Gateway

Meter or

Gateway

PAN

Device

Utility

Enterprise Integration

Infrastructure

(e.g. ESB, SOA, …)

Standard or Proprietary

Communication

Infrastructures

Messages defined by IEC

61968-9 and based upon

IEC CIM, conveyed using a

variety of integration

technologies

IEC 61968-9 Messages

Messages defined by

relevant standards or

vendors. May use a wide

variety of communication

technologies

Messages defined

by PAN/HAN

specifications

Mappings, translations

and/orforwardiing as

needed Mapping, translations

and/or forwarding as

needed

Customer

Customer

Customer

Area of Direct Impact

using IEC 61968-9

Area Causally/Indirectly

Impacted by or impacting

IEC 61968-9

Part 9 Reference Model - Partial

Key

Service

Point

Metering System

Data Collection

Control and

Reconfiguration

Readings, events

and status

Controls and signals

Meter

Data

Management

Scheduled

Read

Interface and protocol details of the

Service Point are outside the scope of

IEC 61968-9

Outside the scope of 61968

61968 Part 9


Scheduled

Read

Tokens

Network

Operations

61968-3

Scheduled

Read

Customer

Information

and

Billing

61968-8

Exchange

Portal

Scheduled

ReadPeak

Price

(1)

Peak

Price (1)Load

Reduction

Peak

Price (1)

Load

Reduction

Peak

Price

(2)

Meter

Administration


• The Reference Model provides examples of the logical components and data flows related to this standard.

• The Meter is treated as an “end device”

• An End Device: – Has a unique identity

– Is managed as a physical asset

– May issue events

– May receive control requests

– May collect and report measured values

– May participate in utility business processes

• The Reference Model describes the flows between the components.

Part 9 Business Functions and Components Business Functions Business

Sub-Functions

Abstract Components

Meter Reading and Control (MR) Metering System (MS) Data collection

End point controls

End point reconfiguration

Disconnect/reconnect

Demand reset

On request read

Point of sale

Outage detection and restoration verification

Power reliability and quality events

Metering system events

Meter Maintenance and Asset Management End point install, configure, remove, repair,

disconnect, reconnect

End point asset history

End point reconfiguration

Special read

Meter service request

Tariffs

Meter Data Management (MDM) Meter data repository

Usage history

Validation, estimation and editing

Customer billing data

End device controls and events

Demand Response

(DR)

Real-time pricing

Emergency reductions

Economic reductions

Program registration

Load Management (LM) Load analysis

Load control

Demand response

Performance measurements

Risk management

Part 9 Metering Messages

• There are currently 63 Metering Messages

• End Device Event Messages (includes PAN Messages)

• End Device Control Messages (includes PAN Messages)

• Meter Reading Messages

EndDeviceEvent Messages

• EndDeviceEvent Messages Convey events related to:

– Sustained and Momentary Outage Detection

– Low and High Voltage Threshold Detection

– Meter Health

– Tamper Detection

– Revenue Event

EndDeviceEvent Use Case for Outage Detection Event

EndDeviceEvent Message

EndDeviceEventType Enumerations

• EndDeviceEventType enumerations defines the event using four parts:

EndDeviceEventType := <EndDeviceType>.<EndDeviceDomain>.<EndDeviceSubdomain>.<EndDeviceEventorAction>

Where:

<EndDeviceType> = a numeric value from the EndDeviceType enumeration. Example: 3 is Electric Meter, 5 is a Gateway, 12 is a PAN Device, etc.

<EndDeviceDomain> = a numeric value from the EndDeviceDomain enumeration. Example: 26 is Power, 15 is Load Control, etc.

<EndDeviceSubdomain> = a numeric value from the EndDeviceSubdomain enumeration. Example: 0 is N/A, 28 is Power Quality, etc.

<EndDeviceEventorAction> = a numeric value from the EndDeviceEventorAction enumeration. Example: 85 is Failed, 81 is Opted-Out, etc.

Message Organization – Event Type Enumerations

EndDeviceEventType Description

3.26.0.85 Power off alarm

3.26.0.216 Power on

3.26.38.150 Low voltage

3.26.38.93 High voltage

3.26.38.37 Voltage Imbalance Cleared

3.12.1.38 Unauthorized Access attempt

3.12.0.257 Tamper detection

3.8.0.215 Demand reset occured

3.31.0.68 Disconnected

3.31.0.42 Connected

EndDeviceEvent XML Message Example Meter Power Off Event: Electric, Power, N/A, Failed

<ns1:EndDeviceEvents

xmlns:ns1="http://iec.ch/TC57/2011/EndDeviceEvents#">

<ns1:EndDeviceEvent>

<ns1:createdDateTime>2009-11-04T18:52:50.001-

05:00</ns1:createdDateTime>

<ns1:EndDeviceEventType ref=“3.26.0.85”/>

<ns1:description>Power off alarm</ns1:description>

<ns1:Assets>

<ns1:mRID>3dc53ee5-777e-50b4-8699-

a1c224f45f3d</ns1:mRID>

<ns1:Names>

<ns1:name>Meter23253</ns1:name>

</ns1:Names>

</ns1:Assets>

</ns1:EndDeviceEvent>

</ns1:EndDeviceEvents>

End Device Control Messages

• The EndDeviceControl message issues control commands related to:

– Load Control

– Demand Reset

– Connect/Disconnect

– Real-Time Pricing

EndDeviceControls Use Case – Remote Disconnect

EndDeviceControls Message

EndDeviceControlType Enumerations

• EndDeviceControlType enumerations defines the event using four parts:

EndDeviceControlType := <EndDeviceType>.<EndDeviceDomain>.<EndDeviceSubdomain>.<EndDeviceEventorAction>

Where:

<EndDeviceType> = a numeric value from the EndDeviceType enumeration. Example: 3 is Electric Meter, 5 is a Gateway, 12 is a PAN Device, etc.

<EndDeviceDomain> = a numeric value from the EndDeviceDomain enumeration. Example: 31 is RCDSwitch, 26 is Power, 15 is Load Control, etc.

<EndDeviceSubdomain> = a numeric value from the EndDeviceSubdomain enumeration. Example: 0 is N/A, 28 is Power Quality, etc.

<EndDeviceEventorAction> = a numeric value from the EndDeviceEventorAction enumeration. Example: 23 is Disconnect, 85 is Failed, 81 is Opted-Out, etc.

Message Organization – Control Type Enumerations

EndDeviceControlType Description

3.8.0.214 Demand reset

3.15.6.242.0 Load control started

3.15.6.243.1 Load control stopped

3.31.0.18 Close remote Connect/Disconnect Switch

3.31.0.22 Disable RCD Switch

3.31.0.23 Open remote connect/disconnect switch

3.31.0.26 Enable RCD switch

3.20.9.82 Price signal

EndDeviceControl XML Message Example - Meter Disconnect by Group: Electric, RCD Switch, N/A, Disconnect

<?xml version="1.0" encoding="UTF-8"?>



<m:EndDeviceControls

xsi:schemaLocation="http://iec.ch/TC57/2010/EndDeviceControls#

EndDeviceControls.xsd" xmlns:m="http://iec.ch/TC57/2010/EndDeviceControls#"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<m:EndDeviceControl>

<m:type>3.31.0.23</m:type>

<m:EndDeviceGroup>

<m:mRID>3dc53ee5-777e-50b4-8699-

a1c224f45f3d</m:mRID>

</m:EndDeviceGroup>

<m:scheduledInterval>

<m:start>2011-05-05T09:30:00.0Z</m:start>

</m:scheduledInterval>

</m:EndDeviceControl>

</m:EndDeviceControls>

Meter Reading Messages

• Examples of these types of Messages are:

– MeterReadSchedule

– MeterReading Message for the following types of requests: • Manual MeterRead

• On-Request/On-Demand Meter Read

• Historical Meter Data Access

• Billing Inquiry

• Bulk Readings

MeterReadings Message

• MeterReadings message allows for:

– Readings from one or more meters

– Reading values each have an associated reading type, timestamp and value

– Many Quality values can be associated with each reading value

– Readings can be supplied in the form of interval blocks if the common reading types are grouped together.

– Event Histories are returned with meter readings.


• The request for meter reading should specify:

– A meter or group of meters

– A type of reading to collect

– A frequency

– A Duration of interest

• The scheduled frequency may consist of regular or irregular periods.


• The MeterReadings request may be initiated by any of the following:

– The CIS (in an effort to collect billing determinants).

– A Planning and Scheduling application (in an effort to acquire engineering data about the distribution network).

– An OMS (in order to verify if a customer is affected by an outage or has been restored)

– An MDM system (in an effort to broker data for any or all of the above applications).

– The MS itself may also directly initiate a meter read

MeterReadings Use Case - Billing Inquiry


Questions & Contacts

• Margaret Goodrich –

–Home Office: 903-489-1494

–Cell: 903-477-7176

–Email: [email protected]

Documents

61968 Messages (Part 3, 6, 8, 9) - UCAIugcimug.ucaiug.org/Meetings/Melbourne2014... · 61968 Messages (Part 3, 6, 8, 9) CIM University Margaret Goodrich, Manager, Systems Engineering