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

Transcription

1 The Standards Based Integration Company Systems Integration Specialists Company, Inc Messages (Part 3, 6, 8, 9) CIM University Margaret Goodrich, Manager, Systems Engineering SISCO, Inc ½ Mile Road Sterling Heights, MI USA Tel: Fax:

2 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 2

3 Information Model for all Parts Classes for all Parts in the standard series are contained in IEC61968-Part 11 and IEC The classes and attributes may come from one or more of the packages contained in these documents. 3

4 WG14 Messaging Reference Model - Full Outage Management Planning and Scheduling Interface and protocol details of the Service Point are outside the scope of IEC [ 19 ] [ 17 ] [ 12 ] Service Point [ 18 ] Data Collection [ 13 ] Meter Data Management [ 2 ] { 23 } [ 3 ] { 11 } Metering System Control and Reconfiguration { 16 } [ 22 ] [ 15 ] [ 7 ] [ 4 ] [ 12 ] Customer Information and Billing [ 9 ] [ 13 ] Meter Maintenance and Asset Management [ 21 ] [ 1 ] { 8 } { 12 } [ 20 ] [ 6 ] [ 7 ] Network Operations [ 10 ] [ 7 ] [ 6 ] Load Analysis Point of Sale [ 3 ] [ 18 ] { 12 } Load Management System Load Control { 14 } Work Management [ 5 ] { 14 } [ 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 Part 9 [ 22 ] Transaction records Defined by other Parts { 23 } Tokens Key Outside the scope of

5 End-to-End Use Cases and Messages Meter service request Meter service order 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 Scope: A - Outage Management B - Network Model Synchronization C - Maintenance CIS WMS MWF Meter info & complete status AMI/ MDM Meters down Predict to outage device OMS Current State Normal State IEC Scope Device Out SCADA Current State Normal State Device out Energize Fault location isolation steps Restoration steps Switching Plan to energize Device out & fault data Device out & fault data DMS Current State Normal State Isolation Steps Substation MWF WMS Work order Device out & fault data FLISR = Fault Location, Isolation, and Restoration IED IED IED Normal & asset changes Build Switching Plan GIS Proposed normal changes Recommended normal changes Planning Normal State 5

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

7 Outage Notification from a Field Crew sd Outage Notification from Field Crew Field Crew «Outage Analysis» Part 3 - Network Operation::NO-OA «Fault Mgmt» Part 3 - Network Operation::NO-FLT «T rouble Call M... Part 8 - Customer Support::CS-T CM Report Outage() Created(Outage) Created(Outage) 7

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

9 Outage Notification from an AMI sd Outage Notification from Meters «AMI» Part 9 - Meter Reading and Control::MR-AMI «Outage Analysis» Part 3 - Network Operation::NO-OA Field Crew «Fault Mgmt» Part 3 - Network Operation::NO-FLT «Trouble Call M... Part 8 - Customer Support::CS-TCM Created(EndDeviceEvent) Confirm Outage() Outage Confirmed() Created(Outage) Created(Outage) 9

10 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. NO-OA NO-FLT Created Outage NO-OA CS-TCM Created Outage Notification of a confirmed outage at a specific protective device in the network. Payload: - Protective Device ID - Time of outage - Status of device (phases on) - Confirmed status (yes in this case) 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. 10

11 Outage Notification from a Customer sd Outage Notification from Trouble Call «Trouble Call M... Part 8 - Customer Support::CS-TCM «Outage Analysis» Part 3 - Network Operation::NO-OA Field Crew «Fault Mgmt» Part 3 - Network Operation::NO-FLT Created(Outage) Confirm Outage() Outage Confirmed() Created(Outage) Updated(Outage) 11

12 Outage Notification from a Customer from to message description/payload CS-TCM NO-OA Created Outage NO-OA Field Crew Field Crew Confirm Outage Notification of customer-reported outage. Payload: - ID and time of outage for each customer. Request field crew to confirm outage location. NO-OA Outage Confirmed Field crew confirms outage location. NO-OA NO-FLT Created Outage NO-OA CS-TCM Updated Outage Notification of a confirmed outage at a specific protective device in the network. Payload: - Protective Device ID - Time of outage - Status of device (phases on) - Confirmed status (yes in this case) 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. 12

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

14 Part 6 Reference Model Network Monitoring NO-NMON [ 9 ] General Inventory Management (GINV) Records & Asset Management (AM) Equipment hierarchy [ 12 ] [ 11 ] Materials Management [ 18 ] [ 12 ] [ 1 ] [ 6 ] Work Mgt Planning [ 20 ] [ 7 ] [ 4 ] [ 16 ] [ 16 ] [ 12 ] Preventive Maintenance Maintenance & Construction Maintenance and Inspection (MC-MAI) Conditional Maintenance [ 13 ] Crew Composition [ 3 ] [ 10 ] [ 13 ] Scheduling & Dispatch [ 10 ] Maintenance & Construction - Field Recording (MC-FRD) Mobile Workforce [ 5 ] [ 17 ] [ 10 ] [ 8 ] [ 2 ] Network Operations Fault Management (NO-FLT) Customer Support (CS) Customer Service CSRV Operational Planning & Optimization Network Operation Simulation (OP-SIM) Meter Reading & Control (MR&C) [ 14 ] [ 22 ] [ 21 ] { 15 } { 19 } Key Part 6 Defined by other Parts [ 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 ] 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 14

15 15 Part 6 Business Functions and Components Business Functions Maintenance and Construction (MC) Business Sub-Functions Maintenance and Inspection (MAI) Construction (CON) Design (DGN) Field Recording (FLD) Scheduling and Dispatching (SCHD) Abstract Components Maintenance Orders Maintenance Rules Inspection/Maintenance History Work Procedures Work Flow Cost Reconciliation Work Approval Permits Customer Billing Tracking Project Costing Construction Engineering Estimating Bill of Materials Compatible Units As-built Reporting Time Reporting Asset Condition Resource Management Work Planning Work Allocation Material Requisitioning

16 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 16

17 Planned Maintenance Use Case sd Carry out planned maintenance with temporary equipment «Network Ctrl» Part 3 - Network Operation::NO-CTL Part 6 - Maintenance and Construction::MC-MAI «Work Sched & Di... Part 6 - Maintenance 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» Part 6 - Maintenance and Construction::MC-FRD 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) 17

18 Work Request Message 18

19 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 19

20 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 20

21 Change-Out Meter Work Flow 21

22 Service Order Message 22

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

24 Part 8 Reference Model Parts 3-9 Other Systems (6) Maintenance and construction (MC) (3) Trouble Call Management (NO) (5) (3) (4) (2) (1) (6) Customer service (CSRV) Trouble Call Management (TCM) Part 8 Customer Support (CS) 1. Trouble Ticket 2. Incident Information 3. Service Request 4. Work Request 5. Customer Agreement 6. Service Request 24

25 25 Part 8 Business Functions and Components Customer Support (CS) Customer service (CSRV) Trouble call management (TCM) Point of sale (POS) 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 Outage calls Power quality Planned outage notifications Media communication Performance indices Restoration projection/confirmation Outage history

26 Trouble Ticket Use Case sd Trouble Ticket CS-TCM 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) (from Approved Actors) (from Approved Actors) 26

27 Trouble Ticket XSD 27

28 Incident Information Use Case sd Incident Information NO-FLT CS-CSRV Update(IncidentInformation) Update associated trouble ticket() (from Approved Actors) (from Approved Actors) 28

29 Incident Information XSD 29

30 Service Request Work Flow sd Serv ice Request CS-T CM MC-SCHD Customer or person creates a service request() CreatedServiceRequest() (from Approved Actors) (from Approved Actors) 30

31 Service Request XSD 31

32 Customer Agreement Use Case sd Customer Agreement EXT-SAL Customer Support CreatedCustomerAgreement() (from Approved Actors) (from Approved Actors) 32

33 Customer Agreement XSD 33

34 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 34

35 Part 9 Scope Area of Direct Impact using IEC Area Causally/Indirectly Impacted by or impacting IEC Utility Enterprise Integration Infrastructure (e.g. ESB, SOA, ) Standard or Proprietary Communication Infrastructures Meter Customer Customer PAN Device Enterprise Applications IEC Messages Head End Systems Meter or Gateway PAN PAN Device Messages defined by IEC and based upon IEC CIM, conveyed using a variety of integration technologies Mappings, translations and/orforwardiing as needed Messages defined by relevant standards or vendors. May use a wide variety of communication technologies Mapping, translations and/or forwarding as needed Meter or Gateway Customer PAN PAN Device Messages defined by PAN/HAN specifications PAN Device PAN Device 35

36 Part 9 Reference Model - Partial Interface and protocol details of the Service Point are outside the scope of IEC Meter Administration Service Point Readings, events and status Tokens Controls and signals Data Collection Metering System Control and Reconfiguration Scheduled Read Scheduled Read Peak Price (1) Load Reduction Meter Data Management Peak Price (1) Scheduled Read Load Reduction Exchange Portal Network Operations Peak Price (1) Scheduled Read Part 9 Peak Price (2) Customer Information and Billing Defined by other Parts Key Outside the scope of

37 Part 9 Reference Model 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. 37

38 Part 9 Business Functions and Components Business Functions Business Abstract Components Sub-Functions 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 38 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) Load Management (LM) Real-time pricing Emergency reductions Economic reductions Program registration Load analysis Load control Demand response Performance measurements Risk management

39 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 39

40 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 40

41 EndDeviceEvent Use Case for Outage Detection Event 41

42 EndDeviceEvent Message 42

43 EndDeviceEventType Enumerations EndDeviceEventType enumerations defines the event using four parts: EndDeviceEventType := <EndDeviceType>.<EndDeviceDomain>.<EndDeviceSubdomain>.<EndDevic eeventoraction> 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. 43

44 Message Organization Event Type Enumerations EndDeviceEventType Description * Power off alarm * Power on * Low voltage * High voltage * Voltage Imbalance Cleared * Unauthorized Access attempt * Tamper detection * Demand reset occured * Disconnected * Connected 44

45 45 EndDeviceEvent XML Message Example Meter Power Off Event: Electric, Power, N/A, Failed <ns1:enddeviceevents xmlns:ns1=" <ns1:enddeviceevent> <ns1:createddatetime> t18:52: :00</ns1:createddatetime> <ns1:enddeviceeventtype ref= /> <ns1:description>power off alarm</ns1:description> <ns1:assets> <ns1:mrid>3dc53ee5-777e-50b a1c224f45f3d</ns1:mrid> <ns1:names> <ns1:name>meter23253</ns1:name> </ns1:names> </ns1:assets> </ns1:enddeviceevent> </ns1:enddeviceevents>

46 End Device Control Messages The EndDeviceControl message issues control commands related to: Load Control Demand Reset Connect/Disconnect Real-Time Pricing 46

47 EndDeviceControls Use Case Remote Disconnect 47

48 EndDeviceControls Message 48

49 EndDeviceControlType Enumerations EndDeviceControlType enumerations defines the event using four parts: EndDeviceControlType := <EndDeviceType>.<EndDeviceDomain>.<EndDeviceSubdomain>.<EndDevic eeventoraction> 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. 49

50 Message Organization Control Type Enumerations EndDeviceControlType Description Demand reset Load control started Load control stopped Close remote connect/disconnect switch Disable RCD Switch Open remote connect/disconnect switch Enable RCD switch Price signal 50

51 EndDeviceControl XML Message Example - Meter Disconnect by Group: Electric, RCD Switch, N/A, Disconnect <?xml version="1.0" encoding="utf-8"?> <!--Scheduled Disconnect on an End Device Group--> <m:enddevicecontrols xsi:schemalocation=" EndDeviceControls.xsd" xmlns:m=" xmlns:xsi=" <m:enddevicecontrol> <m:type> </m:type> <m:enddevicegroup> <m:mrid>3dc53ee5-777e-50b a1c224f45f3d</m:mrid> </m:enddevicegroup> <m:scheduledinterval> <m:start> t09:30:00.0z</m:start> </m:scheduledinterval> </m:enddevicecontrol> </m:enddevicecontrols> 51

52 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 52

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

54 MeterReadings Message 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. 54

55 MeterReadings Message 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 55

56 MeterReadings Use Case - Billing Inquiry 56

57 MeterReadings Message 57

58 Questions & Contacts Margaret Goodrich Home Office: Cell: