Utility Operations & Best Practices The CIM: What it is and how it s being used

Size: px

Start display at page:

Download "Utility Operations & Best Practices The CIM: What it is and how it s being used"

Delphia Jennings
6 years ago
Views:

1 Utility Operations & Best Practices The CIM: What it is and how it s being used Ricardo Lopez Sr. Product Manager Itron Enterprise Edition Meter Data Management

2 The CIM What It Is and How It s Being Used Ricardo Lopez Product Manager, IEE

3 Topics Covered in This Presentation Overview of the CIM How the CIM is being used Using the CIM to interface within the enterprise Resources

4 You all have experience with common models What often triggers standardization? Safety Communication Efficiency??

5 Point-to-point communication Point to point communication is easy, understandable, and often the only means possible or the path of least resistance Imagine if traffic signs worked this way The results would be disastrous

6 Point-to-point interfaces Since software is easy it has become all too easy to create our own tower of Babel

7 What about solving this with an ESB?? The Enterprise Service Bus!= Magic School Bus MDMS OMS Head End Work Mgmt If the data models are different, you still end up having point to point Asset Mgmt CIS You just route them through some central bus.

8 Is the solution to this problem just fictional? How did Dr. Who, James T Kirk, and Arthur Dent solve this need for a common information model TARDI S Universal Translator Babelfish

9 Our Universal Translator = CIM A set of standards to enable system integration and information exchange based on a common information model Provides a general information model and message/file schemas for messages/files exchanged between systems A key differentiator: The CIM standards are based on a Unified Modeling Language (UML) based information model representing real-world objects and information entities exchanged within the value chain of the electric power industry Provides common semantics for all information exchanges Referred to as Model-Driven Integration (MDI) Not tied to a particular application s view of the world But permits same model to be used by all applications to facilitate information sharing between applications Maintained by IEC in Sparx Enterprise Architect modeling tools Many tools available generating design artifacts and documentation Enable data access to enterprise data warehouse in a standard way

10 Use of the CIM in Meter Reading and Control International Standard IEC has been prepared by Working Group 14, of IEC technical committee 57: Power System Control and Associated Communications. Part 9 focuses on Meter Readings and Control Key Interface and protocol details of the Service Point are outside the scope of IEC Part 9 Service Point Defined by other Parts Outside the scope of Readings, events and status Tokens Controls and signals Peak Price (2) Data Collection Metering System Control and Reconfiguration Scheduled Read Scheduled Read Peak Price (1) Load Reduction Network Operations Meter Data Management Load Reduction Peak Price (1) Meter Administration Peak Price (1) Exchange Portal Customer Information and Billing Scheduled Read Scheduled Read

11 All of these Interfaces are in scope for Part 9

12 IEE CIM Mapping IEE Interface Readings XML Program Based Config Device Event API Device Comm API Task API/Readings Manager Transform CIM Payload MeterReadings CustomerMeterDataSet EndDeviceEvents EndDeviceControls Meter Reading Request Compatible (NOT Compliant )

13 IEE Roadmap Plans for CIM Support A lot of effort into participation in Part 9 standards group (years!) Driving the development of Part 2 nd Edition Enumerations for Event Codes, Quality Codes, and UOMs Joint Task Force with other MDM vendors to develop the configuration interface Setting up meters, accounts, service points, meter swaps, etc. This is a major piece of work that needs to be done _fast_ Two new interfaces are planned to have CIM formats High Volume Data Export, Enhance Device Event API

14 A common model facilitates common payloads With standardized payloads, enterprise systems can standardize on the information that is sent between systems. Internally each system may have its own model, but they can all understand CIM Payloads A good example is a meter: each system may store a representation of meter. Each system may need a sub set of properties defined on the Meter Model Head MDMS End CIS

15 CIM Example of Meter Model

16 CIM Example of Meter Model Class Name something that exists (i.e. a meter) Associations connect classes and are assigned a role that describes the relationship Attributes -describe our object Specialization - a Meter is a type of EndDeviceAsset. It just has a few specific attributes

17 Using the CIM to Derive Messages CIM In the end the key goal is to get interoperable messages between systems. In a simple sense the The Concrete Message is a XML file We can send this file to all systems that have a CIM adapter Concrete Message Conforms to CIM Conforms to Profile Conforms to Message Assembly Conforms to Syntax Restricts/Narrows CIM Profile Message XML Schema Is assembled as Is mapped to

18 Each Vendors Data Model may be different Vendors store data in their own data model and table structures

19 What matters is harmonization of data transfer Profile Standard Payload Vendor 1 (MDMS) Data Model Vendor 2 (CIS) Data Model

20 The CIM Meter Readings Payload One of the most core message payloads in the CIM Handles the transfer of bulk meter readings, on demand contingency reads, interactive reads for display on a portal

21 On Demand Meter Reading Use Case This is all done with messages defined in Part 9 of CIS requests a read from MDM. MDM interrogates the meter The metering system returns the data to the MDM The MDM returns the data to the CIS

22 Meter System Health (Publishing Events) In this use case the metering system is publishing events out to multiple systems Alarms are sent to whomever is listening for them MDM, OMS, etc. can all import the events or ignore them

23 Identifying Objects in CIM Object identification needs to be unambiguous for all system involved in the exchange Meter123 needs to be uniquely identifiable in both a MDMS and a AMI Head End system for example Two approaches mrid = A GUID-like identifier that is globally unique A locally unique Name triplet Name = (name, name type, naming authority) OpenWay Electric Endpoint ID

24 Identifying Objects in the CIM Objects should be given a name by the system of record by using one of the naming elements. In some cases, the utility must identify which application they want to have serve as the system of record for given class. If a neutral ID service is available to broker a globally unique ID for the object, it enables use of the mrid attribute as the authoritative name. If such a service is not available, the name attribute will be used as the authoritative name For uniqueness, it may be necessary to also populate the pathname attribute with the list of classes from the top to the named object (e.g. the xpath). The tradition is to name each class from the top to the bottom of the hierarchy, by listing them left to i ht ti th b l h /

25 Practical Aspects of making Standards Usable There are non-modeling aspects that need to be addressed to make a Standard practical in every day use Much of the information in Part 9 1 st Edition were informative For standards to be interoperable and for actual vendors to use the standard these need to be normative A large effort of Part 2 nd Edition has focused around making this type of information clearly defined and required for vendors to support Units of Measure (Readings Type) Device Event Codes Reading Quality Codes

26 Enumerations Ed. 1 contains: Annex A (informative) Description of message type verbs...96 Annex B (informative) Recommended message structure...99 Annex C (informative) Recommended procedure for the generation of a ReadingType Annex D (informative) Recommended quality code enumerations Annex E (informative) Recommended EndDeviceEvent category enumerations Annex F (informative) Recommended EndDeviceControl code enumerations Annex G (informative) Recommended procedure for maintaining relationships between objects Annex H (normative) XML Schemas for message payloads Annex I (informative) Mappings to ebix Annex J (informative) Request parameters

27 Representation of Readings Part 9 allows for two ways to represent readings IntervalBlocks is a compact way to take advantage of evenly spaced time intervals. Readings can also be represented as individual reads Flexibility in representation comes at a price.

28 ReadingType Examples Name.name :12.0:0.0.3:1:7 Name.description :12.0:0.0.3:1:7 60-minute DeltaData Net Energy (kwh) :12.0:0.0.3:1:7 BulkQuantity Net Energy (kwh) :11.0:0.0.0:0:1 BulkQuantity Net Energy (kvarh) 11 BulkQuantity Energization (count)

29 Part 9 Message change to support intervals Block.intervalSize specifies the periodic spacing between timestamps and nothing more.

30 Part 9 2 nd Edition Annex D - ReadingQualities Optionally returned with the reading. Indicates: Which type of system assigned the code A code category A specific code index.

31 Part 9 2 nd Edition, Reading Quality Source New codes: System Identifier Code Description Normative Status 0 Not Applicable N 1 End Device N Metering system (data N 2 collection) network Meter Data Management N 3 System 4 Other system (not listed) N 5 Externally specified (see accompany data) I

32 Ed.2 Example Quality Categories Category Description Comment 0 Valid Data valid 1 Diagnostics related 2 Power quality related issues at the data collection point 3 Tamper / Revenue Protection related 4 Data collection related The equipment producing or handling the data has identified a diagnostics related issue which may have some effect on this value. The equipment producing the data has identified power quality related issues which may have some effect on the veracity of the data. A system identifies that the data is questionable due to tamper or revenue-protection related reasons. A significant event or condition has occurred (which is not tamper related, power quality related, or diagnostics related) which may effect the veracity of the data. 5 Failed reasonability testing Data at first blush appears to be invalid. 6 Failed validation testing Data fails one or more validation rules. 7 Edited Replaced or approved by a human. 8 Estimated Replaced by a machine computed value based on analysis of historical data using the same type of measurement.

33 IEC Message Structure

34 Message Header

35 Resources and Next Steps The CIM is a very large model. You only use the parts that you need As long as the data is modeled in the CIM, it should be possible to use in exchange between two systems The IEC standard provide normative reference for payloads that can be exchange between vendors that adhere to the standard New Payloads can be created as the standard evolves Look for resources within your organization Someone may already be part of SDO efforts, involved in Open Smart Grid, or members of UCA groups Become familiar with the tools and resources Join up To network with business users and influence requirements and best practices, join the OpenSG To network with implementers and seek training, join the CIMug To be involved with the development of the industry standards, join the appropriate SDO

36 Training is out there..

37 Buy the standard

39 Interface Adoption/Interop When can IEE customers/partners take advantage of CIM support

IEC Implementation Profiles for IEC 61968

IEC Implementation Profiles for IEC 61968 IEC 61968-100 Implementation Profiles for IEC 61968 Overview CIM University UCAIug Summit New Orleans, LA 22 October 2012 Agenda Introduction A look at the purpose, scope and key terms and definitions.