CIM Standards Overview And Its Role in the Utility Enterprise - Part 2
CIM Users Group Ljubljana, Slovenia Terry Saxton Presentation Contents – Part 2
• Layer 2 - Profiles for defining system interfaces – IEC 61970 network model exchange – IEC 61968 message payloads for system integration • Layer 3 - Implementation syntax of instance data – CIM expressed in XML and RDF Schema • Value of an Enterprise Semantic Model (ESM) based on the CIM • Case studies • Where to get more CIM information
2 Next - Context Layer
Information and Semantic Models
Information Model • Generalized model of all utility objects and their CIM UML relationships • Application independent, but defines all concepts needed for any application
Context Contextual layer restricts information model Profiles • Specifies which part of CIM is used for given profile • Mandatory and optional • Restrictions • But cannot add to information model
Message Syntax Message/File Message syntax describes format for instance data Format • Can re-label elements (XSD, RDF • Change associations to define single structure for message payloads Schema, OWL) • Mappings to various technologies can be defined
3 How the CIM is Applied to Specific Information Exchanges • The interfaces defined under CIM are defined by Profiles – A profile specifies the information structure of exchanged information by creating contextual semantic models • Contextual semantic models are a subset of the overall CIM information model (i.e., they inherit their structure from the CIM UML model) – There is typically a family of related interfaces defined within a profile – Products implement support for profiles in the form of CIM/XML import/export software or ESB run-time adapters – Testing occurs against profiles – “CIM compliance” is defined against profiles – otherwise the term is meaningless
• Note: We saw that the CIM Information Model is partitioned into sub-domains by IEC WGs – But these groups work hard to ensure there is a single, unified semantic model over the whole utility domain – That means any part of the whole UML model can be used to define a system interface
4 Presentation Contents
• Profiles for business context – WG13 61970 Profiles for Network Analysis and Power System Network Model Management and Exchange – WG14 61968 Message Payloads for System Integration
5 The Network Model Portion of the CIM . A set of 61970 standards • 301 & 302 - model • 400 series – profiles • 500 series – serialization of profiles using RDF Schema . The most mature portion of the CIM • Interoperability tests • Deployments . Has grown over time • Equipment/connectivity (typically breaker/node) • Topology (bus/branch) • Diagram layout • Dynamics • HVDC . Continues to grow • Changes (projects, outages) • Frames, assembly of model parts into cases • ICCP configuration • DER, congestion management, etc. 6 Basic Concepts around CIM Network Modeling 1. Power Grid Model 2. Steady State Hypothesis • Defines how the network is built. • Defines specific steady-state condition for • Shared by all studies. • the network. • Past, present network: • Varies with the kind of study. • Defined by construction process. • Some data come from specialized sources. • Validated by state estimation. • For example… • Plans: • Load forecasting • Defined as result of TSO planning • Market outcomes process. • Most data created by the participants in the • Submitted by other participants. analytical process. • Input or outcomes of one case are used in setup of other similar cases.
3. Distributed Model Authority 4. Time • Grid ownership is split among many • The physical model has a time dimension. different entities. • Studies are based on points in time. • Analytical models are assembled from • The entire picture evolves as new their contributions. decisions are made. 5. Object Identification • Local naming conventions and requirements conflict. 7 Model Part Types in a Network Analysis Case
Network Model Management Network Analysis Case Model Part Types
Equipment Dynamics (DY) (EQ) Short Circuit (SC)
- Equipment Diagram Layout (DL) Physical model parts are developed - Containment - Connectivity from engineering design and asset - Measurement Locations Normal Operations (OP) - Controls information sources. - SIPS
TP SSH -TopologyNodes -association to - Status conducting equipment - Switch status - In Service - Branch end - Tap positions SV
Steady-state hypothesis model parts - Voltage targets Topology & - Energized State - Flow targets - Island Topology are developed from sources like load - Monitoring Network - BusVoltage forecasting and markets – and from - Operating limits Solution - Bus Injections Algorithm - Terminal flows - Energy Injections - Controls other cases. - Trans Source - Violations - Solar - Wind - Storage - Traditional Load - DR - etc,
8 WG13 Ref Model for a Network Analysis Case
Physical Network Model Parts Repository Equipment Short Circuit (SC) (EQ) Dynamics (DY) CIM Standard Datasets Incremental Physical Model - Equipment Diagram Layout (DL) in a Model Parts Select / Edit - Containment - Connectivity Network Full Model - Controls Geo Location (GL) Parts - SIPS Analysis Case Model Part Types: - Equipment Rating - Normal operations Normal Operations (OP) • EQ • DY - Energy allocation • SC • DL • OP • GL
Steady-State Topology Hypothesis (TP) Measurement Outage (SSH) -TopologyNodes Sources Schedules Device Status - Status -association to - Switch status conducting equipment Initialization/Edit - In Service - Branch end State Variables Energy Initialization/Edit - Control settings (SV) Sources - Flow regulation - Energized State Schedules - SIPS Topology & - Island Topology - Monitoring Network Solution - BusVoltage - Bus Injections Monitoring - Other Algorithm Initialization/Edit - Energy Injections - Controls SSH Model Parts Repository - Bulk generation - Violations - Solar - Wind Energy Injection - Storage - Traditional Load Full Model Initialization/Edit Incremental - DR Parts - etc, Model Parts
9 61970 Profiles Currently Defined Part 452 Static Transmission Part 456 - Solved Power Network Model Profiles System State Profiles Also known as Common Power • Steady State Hypothesis System Model (CPSM) (SSH) • Equipment (EQ) – Measurements – Specifies the physical – Status characteristics of the network SS model equipment such as – Controls impedance and connectivity – Limits • Operation (OP) – Energy distribution – Specifies data pertaining to how the system is normally • Topology (TP) operated such as limits and – The result of topology voltage regulation processing. i.e. description of how equipment is connected • ShortCircuit (SC) at a particular point in time – Specifies additional electrical characteristics necessary to • State Variables (SV) execute Short Circuit studies – Result of a state estimator or • 61968-13 distribution model power flow, or the starting (CDPSM) based on Part 452 conditions of state variables with some extensions
10 61970 Profiles
• Part 457 - Dynamics (DY) – Specifies exchange models representing dynamic behavior of the majority of power system components in common use today by utilities to perform system simulation studies for system dynamic assessment, contingency analysis, and planning purposes – Adds dynamics to static network model specified in Part 452 • Part 453 - Diagram Layout (DL) – Describes how equipment objects in EQ profile are placed on one-line schematic diagrams for display purposes
In Development
• Part 451 – Measurement/SCADA Date Exchange – (on hold) • Part 459 - Framework for managing shared network model information • Part 460 - Projects
11 Assembly of Model Parts
• Model Part is a set of CIM data that can be composed with other model parts to create a complete model • Starts with 61970-452 static transmission network model Profile (CPSM) • 61968-13 distribution model (CDPSM) based on these profiles as well
Measurement Specifications
61970-452 Equipment Profiles Model
Connectivity Schedules
12 Add 61970-451 SCADA Data Exchange and 61970-456 Solved System State Profiles
61970-451 61970-456 Profiles Profile Adds steady state Adds SCADA State SSH solution of power Variables system case Measurement produced by and Control Topology power flow applications
Measurement Specifications Dependencies via 61970-452 Equipment references to Profiles Model CPSM Part 452
Connectivity Schedules
13 Plus 61970-457 Dynamic Models
61970-451 61970-456 Profiles Profile State SSH Variables Measurement and Control Topology
Measurement Adds dynamic Specifications models used in system simulation 61970-452 Equipment Profiles Model Dependencies via references to Connectivity Schedules CPSM Part 452
14 Plus 61970-453 Diagram Layout Profile
61970-456 Profiles Future 61970- 457 Profile State SSH Variables Dynamic Models
Measurement Topology Set
Adds diagram 61970-453 layout info for Measurement Profile Specifications schematic data 61970-452 Equipment Diagram Profiles Model Layout Dependencies Boundary Objects via reference Common Schedules to CPSM Part Objects 452
15 Typical Workflow for Model Exchange
State Equipment Topology Variables
E1 T1 S1
S2
T1.1 S3
Time E1.1 S4 Instances T1.2 or S5 Versions
T1.3 S6
Profile S7 Full model Incremental (Differential) Model S8 Predecessor DependsOnModel
16 Model Partitioning by the Responsible Source
Model parts are maintained once …
TSO A Unified Grid Model
TSO B A B C D Study Type 1
E F G H Study Type 2 Formal specification of modeling I J K L responsibility. Formal specification of study assembly O O O O M N O P
process. O O O
Q R S T
TSO W U V W X Study Type n
TSO X
… and used in many different study case
assemblies. 17 Presentation Contents
• Profiles for business context – WG13 61970 Profiles for Power System Network Model Exchange – WG14 61968 Message Payloads for System Integration
18 Abstract Information/ Model From Semantic Information Model Model to Syntactic Model Context/ Profiles
Message UML World Assembly
XML Syntactic World
Information: http://www.ucainternational.org/ http://www.iec.ch
20 The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For Identifying Information Exchange Requirements Among Utility Business Functions
All IEC 61968 Activity Diagrams and Sequence Diagrams are organized by the IRM
External Systems: • Energy Trading (ET) Records & Operational Maintenance Network • Retail (RET) Asset Planning & & Operation • Sales (SAL) Management Optimization Construction (NO) • Stakeholder Planning & Management (SPM) (AM) (OP) (MC) • Supply chain and logistics (SC) • Human Resources (HR)
IEC 61968-3 IEC 61968-4 IEC 61968-5 IEC 61968- 6 Applicable parts of IEC 61968 Series
Enterprise Application Integration and Enterprise Service Bus Middleware
IEC 61970 & Applicable parts of IEC 62325 & IEC 61968 Series IEC 61968-7 IEC 61968-8 IEC 61968-9 Applicable parts of Applicable parts of IEC 61968 Series IEC 61968 Series External Systems: Network Meter • Customer Account Customer Bulk Energy Extension Reading & Management (ACT) Inquiry Management Market • Planning Control Financial (FIN) (CS) Operations • (NE) (EMS) Business Planning and (MR) Reporting (BPR) • Premises (PRM)
Utility Electric Network Planning, Constructing, Enterprise Resource Planning, Supply Maintaining, and Operating Chain, and General Corporate Services
21 The Business Sub-Function Level of the IRM for IEC 61968 Scope
Network Operations Records & Asset Management Network Operations Operation Statistics Substation & Network Operational Planning Maintenance and Monitoring (NMON) & Reporting (OST) Inventory (EINV) & Optimization Construction Network Control Network Calculations Geographical Network Operation Maintenance & Scheduling (CTL) - Real Time (CLC) Inventory (GINV) Simulation (SIM) Inspection (MAI) & Dispatch (SCH) Fault Management Dispatcher Training General inventory Switch Action Construction WMS Field (FLT) (TRN) management (GIM) Scheduling (SSC) (CON) Recording (FRD)
Operational Feedback Asset Investment Power Import Sched. Design & Analysis (OFA) Planning (AIP) & Optimization (IMP) Estimate (DGN)
Application Integration Infrastructure
Network Extension Customer Meter Reading & Control External Systems Planning Support Meter Reading Meter Data (RMR) Network Customer Service Management IMDM) Calculations (NCLC) (CSRV) Advanced Metering Metering System Infrastructure (AMI) Project Definition Trouble Call (MS) Management (TCM) (PRJ) Demand Response Meter Maintenance (DR) (MM) Construction Point Of Sale (POS) Supervision (CSP) Load Control Meter Data (MD) (LDC) Compliance Management (CMPL) Meter Operations (MOP)
22 Ed. 3 IRM
. IEC 61968-1 . IEC 61970-1 . IEC 62325 business 2) IRM Overview - Status
Network Operation (NO) Fault Management (FM) Network Model Engineering Design Management Asset Management (AM) Work Order Management (WOM) End Device Operation (EDO) Customer Support (CS) Management (NMM) (EDM)
Real-Time Operation Operation Reporting Fault Identification (FI) Maintaining As-Built Conceptual Design Construction Work A sse t De ci si o n Asset Monitoring Work Dispatching Work Execution (WE) End Device End-Device Data Customer Installation (RT) (OR) Model Parts Development (CDD) Management (CWM) Support (ADS) (AM) (WD) Configruation (EDC) Acquisition Management (CIM) (MSBMP)
Forecasting & Operator Training (OT) Restoration Operation Maintaining Model Detailed Engineering Design Model Asset Record Asset Management Work Scheduling Work Recording End Device Data Initating Demand and Customer Scheduling (FS) Planning (ROP) Projects (MMP) (DE) Management (DMM) Management (ARM) Planning (AMP) (WS) (WR) Historian (EDH) Response (IDR) Relationship Management (CRM)
Committed Operation Design Model Analysis Catalogue Management End Device Control Customer Account Planning (OP) (DMA) (CM) (EDC) Management (ACT)
Information Exchange
Predicted Operation Planning System Development Planning Energy Forecasting (EF) Market Operation (MO) Market Development Settlement (S) Retail Market Operation External to CIM (EXT) (POP) (SDP) (MD) (RMO)
Availability Power Scheduling Capacity Transient Stability Energy Forecasting (EF) Market Forecasting Market Operation Energy Trading (ET) Grid Settlement Market Settlement Financial Business Planning & Planning (AP) (PS) Calculation Analysis Analysis (TSA) (MF) (GS) (MS) Management (FM) Reporting (BPR) (CCA)
Operational Security Switch Action Protection Analysis Voltage Stability Environment Environment Market Market Monitoring Shadow Market Transit Settlement Human Resources Project Management (OS) Scheduling (SCC) (PA) Analysis (VSA) Forecast (ENV) Observability (EO) Configuration Settlement (SMS) (TS) Management (HR) (PM)
Acquiring Payment Relability Short-Circuit Calculation Analysis Analysis (SCA) (RCA)
23 23 IEC 61968-9: Interface Standard for Meter Reading and Control
26 Scope/Purpose
• 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 Merter Reading and Control. • Typical uses of the message types include: – Meter Reading and Meter Control – Meter Events – Customer Data Synchronization and Customer Switching
27 Scope of Part 9
Area Causally/Indirectly Area of Direct Impact Impacted by or impacting using IEC 61968-9 IEC 61968-9
Customer Electric Utility Standard or Proprietary Meter Communication Enterprise Integration Infrastructures Infrastructure (e.g. ESB, SOA, …) Customer PAN Device
Meter or Enterprise Head End PAN IEC 61968-9 Messages Gateway Applications Systems PAN Device
Messages defined by IEC 61968-9 and based upon Customer PAN IEC CIM, conveyed using a Device variety of integration technologies Messages defined by Meter or PAN relevant standards or Gateway vendors. May use a wide PAN variety of communication Device
technologies PAN Device Mappings, translations and/orforwardiing as Messages defined needed Mapping, translations by PAN/HAN and/or forwarding as specifications needed
28 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.
29 Part 9 Reference Model
Power reliability and quality events Planning Outage and Management Scheduling
Interface and protocol details of the Meter are outside the scope of IEC 61968-9 Outage and restoration verification
Special read Readings and status Meter Meter Meter Meter Data Collection readings Data history Management
Metering System Tokens Control and Reconfiguration Controls and signals Customer Data Set Configuration, Readings installation, etc. and status On request read Customer Information Transaction records and Meter health and Billing tamper detection Disconnect/reconnect, Meter Maintenance demand reset Demand response signals (e.g. load control, price signals)
Install, Tariffs, parameters Network Load curves, Remove, Measurement history, etc. Disconnect, Operations Reconnect Data obtained by special read Meter service request Work Management Transaction information
Point Account information 61968 Part 9 of Defined by other 61968 Parts Sale Key Outside the scope of 61968
30 Part 9 Message Types
31 Typical Message Payload Definition - EndDeviceEvent Message
EndDeviceEvent Messages Convey events related to: • Sustained Outage Detection • Momentary Outage Detection • Low Voltage Threshold Detection • High Voltage Threshold Detection • Distortion Meter Health • Tamper Detection • Revenue Event
32 Next – Message Syntax
Information and Semantic Models
Information Model • Generalized model of all utility objects and their CIM UML relationships • Application independent, but defines all concepts needed for any application
Context Contextual layer restricts information model Profiles • Specifies which part of CIM is used for given profile • Mandatory and optional • Restrictions • But cannot add to information model
Message Syntax Message/File Message syntax describes format for instance data Format • Can re-label elements (XSD, RDF • Change associations to define single structure for message payloads Schema, OWL) • Mappings to various technologies can be defined
33 Xtensible Markup Language (XML)
• Universal format for structured documents and data • Provides a syntax for exchange of information • CIM uses for exchange of message payloads between systems, such as an Outage message from an Outage Management System (OMS) to a Customer Information System (CIS), which are actually XML documents • Can be transported over multiple, different types of communication infrastructure, such as an Enterprise Service Bus (ESB) or the Internet • XML uses “tags” that are based on the CIM UML class attributes to denote elements within documents
34 Mapping CIM Class Structure to XML using XML Schema (XSD)
• An XML Schema of the CIM can be autogenerated from UML models with third party tools – A list and description of available tools is on the CIMug SharePoint site • The CIM classes and attributes are used to define tags • Then the CIM can be shown in XML as well as UML
Example of use of XML Schema • Mapping Proprietary EMS Interfaces to the CIM – Provide enterprise system access to transformer data
35 Mapping EMS Interfaces to the CIM – User access to transformer data
• EMS Native Interface attributes: – TRANS_NAME – The Transformer’s name – WINDINGA_R – The Transformer’s primary winding resistance – WINDINGA_X – The Transformer’s primary winding reactance – WINDINGB_R – The Transformer’s secondary winding resistance – WINDINGB_X – The Transformer’s secondary winding reactance – WINDINGA_V – The Transformer’s primary winding voltage – WINDINGB_V – The Transformer’s secondary winding voltage
36 Transformer Class Diagram in CIM Simplified (Pre-Release 15 model)
37 CIM Interface Mapping - Beginnings of Profile/Message Payload Definition “name” from IdentifiedObject Two different interface Aggregation changed attributes (WINDINGA_R and from 0..n to 2 WINDINGB_R) map to same CIM attribute Multiplicity changed from 0..1 to 1
Multiplicity changed from 0..1 to 1
38 Message Payload in UML
Note: Associations changed to aggregations Parent classes removed Not required in actual message content Parent classes already known by both sender and receiver Corollary: Only those parts of the CIM used in message exchange need to be supported by interface applications End result – modified class structure Example of application of business context to information model
39 XML Schema for Transformer Message
40 40 Sample Transformer Interface Message Payload in XML
41 XML Implementation Technologies
• XML Schema – Used for generation of message payloads for system interfaces in system integration use cases • RDF Schema – Used for exchange of power system models
42 Resource Description Framework (RDF)
• RDF provides a framework for data in an XML format by allowing relationships to be expressed between objects • RDF Syntax – With a basic XML document there is no way to denote a relationship between two elements that are not a parent or a child • Ex: an association or aggregation/containment, as between Substation and VoltageLevel) – Within an RDF document each element can be assigned a unique ID attribute (RDFID) under the RDF namespace – Adding a resource attribute to an element allows references to be made between elements by having its value refer to another element’s ID
43 RDF Schema
• While RDF provides a means of expressing simple statements about the relationship between resources, it does not define the vocabulary of these statements • The RDF Vocabulary Description Language, known as RDF Schema (RDFS) provides the user with a means of describing specific kinds of resources or classes • RDFS does not provide a vocabulary for a specific application's classes, but instead allows the user to describe these classes and properties themselves and indicate when they should be used together – Semantics contained in the CIM UML model provide the vocabulary • RDF combined with RDF Schema – Provides a mechanism for expressing a basic class hierarchy as an XML schema by specifying the basic relationship between classes and properties – This allows a set of objects to be expressed as XML using a defined schema that retain their relationships and class hierarchy
44 References
• RDF (Resource Description Framework) – For more information: http://www.w3.org/RDF – Status: W3C Recommendation 2004-02-10 – List of documents at: http://www.w3.org/standards/techs/rdf • RDF Schema – Status: W3C Recommendation 2004-02-10 • http://www.w3.org/TR/PR-rdf-schema • Namespaces – Provides a simple method for qualifying element and attribute names used in XML documents by associating them with namespaces identified by URI references – Status: WC3 Recommendation 2009-12-08 • http://www.w3.org/TR/REC-xml-names • URI (Uniform Resource Identifiers) – Provides a simple and extensible means for identifying a resource – Status: Internet RFC August 1998 • http://www.w3.org/Addressing/
45 Mapping CIM Class Structure to XML using RDF Schema
• Commonly referred to as “CIM/XML” but correct reference is CIM RDF XML • 61970-501 specifies the mapping between CIM UML model defined in 61970-301 into a machine readable format as expressed in the XML representation of that schema using the RDF Schema specification language – The resulting CIM RDF schema supports CIM Model Exchange profiles, as presented in IEC 61970-452 and others – Allows CIM data objects to be mapped, one-to-one, into RDF instance data. • Part 501 specifies the subset of RDF used for CIM RDF XML – Any RDF parser can be used to read CIM RDF XML – CIM community developed tools to auto-generate the CIM RDF XML from the CIM UML model
46 Simple Network Example
SS2
400KV SS1-SS2 SS1 Cable1 Cable2 12345 MW
Cable3 12345 KV BB1 12345 MW SS4 T1
110KV
47 Simple Network Connectivity Modelled with CIM Topology
T1 T2 SS 2 400KV BB1 Volts SS1-SS2 (KV) P1 SS 1 (M W)
Cable1 CN2 Cable2 CN5 DC2 CN4 BR1 CN3 CN1
BR3 Cable3 P2 (M W) CN6
TW 1 CN8 T 1
TW 2 SS 4
CN7 BDD-RSK2 110KV
48 Siemens 100 Bus Network Model in RDF
Top of RDF Schema version of Siemens 100 bus model
49 ACLineSegment in RDF Siemens 100 bus model - RDF schema 50 ACLineSegment in RDF Siemens 100 bus model - RDF schema 51 Implementation Syntax – WG13 61970 • Part 552 describes the CIM XML format at a level for implementation to support the model exchange requirements in IEC 61970-452 – This standard relies upon the CIM RDF Schema of IEC 61970- 501 – Includes Difference model – Includes file header specification with file dependencies for importer to ensure all prerequisite models exist prior to importing 54 Basics: Schema from CIM CIM Power (in UML) System Data CIM as Exporter Enterprise XML/RDF specifies Architect Schema UML Power to RDF System Data Transformers as XML/RDF 55 How Are CIM Standards Used? • Unlike most standards we use – Ex: IEC 60870-6 ICCP/TASE.2 Communication Protocol standard – Fixed functionality, very stable, easy to test compliance, but inflexible • CIM standards can also be strictly applied and tested for compliance – Ex: CIM/XML Power system network model exchange – Product interfaces are developed and tested for compliance – Subject of several EPRI-sponsored interoperability tests (IOPs) for specific interface definition – ENTSO-E is best example of the need for strict compliance testing of power system network models and related information exchanges (such as congestion forcasts) via IOPs 56 ENTSO-E is THE European TSO platform • Founded 19 December 2008 and fully operational since 1 July 2009 • Represents TSOs from 44 countries • 532 million citizens served • 880 GW net generation • 305,000 Km of transition lines managed by the TSOs • 3,200 TWh/year demand • 380 TWh/year exchanges • Replaced former TSO organisations: ATSOI, BALTSO, RTSO, NORDEL, UCTE, UKTSOA • Migrated to CIM-based network protocols after close liaison with WG13/16 and extensive IOPs with multiple vendors and TSOs • CGMES (Common Grid Model Exchange Specification) is based on CIM to meet EU Network Codes 57 Example: Power Flow Network Model Exchange Information and Semantic Models Information Model Defines all concepts needed for exchange Conforms to of operational load flow models IEC 61970-301 Base CIM CIM UML – Reused parts and -302 if dynamics are needed – New extensions Context Contextual layer restricts information model Specifies which part of CIM is used for Conforms to Power System static/dynamic model exchange IEC 61970-452, 453, Mandatory and optional 456, others Model Profile Restrictions Model Exchange Group But cannot add to information model Profile File syntax Message Syntax Can re-label elements Conforms to Change associations to define single IEC 61970-501 and -552 CIM/RDF structure for message payloads CIM XML Model Exchange Format Schema Mappings to various technologies can be defined 58 How Are CIM Standards Used? • Unlike most standards that we are used to – Ex: IDDP/TASE.2 Communication Protocol standard – Fixed functionality, very stable, easy to test compliance, but inflexible • CIM standards can be strictly applied and tested for compliance – Ex: CIM/XML Power system model exchange – Product interfaces can be developed and tested for compliance – Subject of several EPRI-sponsored interoperability tests for specific interface definition • CIM can also be used as a starter kit – Basis for an Enterprise Semantic Model (ESM) which includes other models/semantics from other sources – Ex: Sempra Information Model (SIM) – Interfaces are usually project-defined, so no standard tests – System interfaces are managed and tested for each project 59 Enterprise Semantic Models – CIM + Other Industry Standards Private UML Merge – resolve Other CIM UML semantic Information Extensions differences Models Context Contextual layer restricts information model Constrain or modify data types Profile Cardinality (may make mandatory) Cannot add to information model Message Syntax Message/data syntax describes format for instance Schemas data XSD, RDFS, Can re-label elements DDL Change associations to define single structure for message payloads Mappings to various technologies can be defined 60 Building and Using an ESM for Generating Canonicals (XSDs, DDLs, others) Semantic Formalization Semantic Consistency Existing Terminology and Metadata ClassA ClassB ClassC 3) Generate Canonicals 1) Establish Vocabulary 2) Develop ESM Syntactically and semantically Control Content Model using vocabulary terms consistent canonical models Collaborate Refine context Identify and refine semantics Context Refinement Complements Xtensible MD3i 61 Role of Enterprise Semantic Model Application Process Business Open Information Integration Intelligence Standards BPM/Workflow Enterprise Semantic Enterprise Integration Platforms Business Model Definitions Applications Metadata 62 Let’s Apply to a Utility Project - Interface Architecture CIM UML Other CIM UML Bridge Information Extensions Models Context Profile 1 System System System Interface ProfileSystem 1 Interaction Interaction Interaction Design Profile 2 Profile 3 Document Profile 1 Interface Syntax Message CIM/RDF DDL XML Schema Schema 63 Ex: Project Interaction Test Conforms to Enterprise Semantic Model Utility ESM ESM • Defines all concepts needed for Enterprise – Reused parts – New extensions for project Contextual layer restricts ESM Conforms to Specifies which part of ESM is used for Concrete Profiles defined specific system interaction Message for each Profile Mandatory and optional system interaction Restrictions But cannot add to information model File syntax Conforms to Can re-label elements Change associations to define single WSDLs and Message XML Schema structure for message payloads XML Schemas Mappings to various technologies can be defined 64 Project Integration Architecture 65 Data Architecture – Model CIS REFEFENCE CIM OTHER MODELS SEMPRA Semantic Model MODEL MESSAGES Business Business Business Entity Entity Entity SCHEMAS DB Schema XML Schema 66 Use of ESM to Implement a Service Oriented Architecture (SOA) • CAISO designed a new power market system – Multi-year program that involved many vendors, new systems, as well as numerous legacy systems • Includes EMS, Full Network Model, Outage Management, PI Historian, Market Systems, many others • External interfaces to Market Participants included • Integration Competency Center decided on a Service Oriented Architecture (SOA) for the integration framework – Require all new applications and systems to be “Integration Ready” with service-enabled interfaces – Use only standard CAISO-defined services – Payloads based on the CIM – Based on Web services – CIM and Model Driven Integration (MDI) methodology used to define information exchange 67 Interface Examples: Interface Type Example Implemented Utilized by Description by Information submitBid(XML) Vendor Enterprise These interfaces are for creating Creation or modifying information within a system of record. Information publishCleanBidSet(XML) CAISO Vendor These interfaces are for Transfer transferring information and releasing custody. Information receiveCleanBidSet(XML) Vendor EAI These interfaces are implemented Interest by vendors to allow systems to receive information as it becomes available. This indicates a subscription type interest in data. Information getResourceInfo(XML) Vendor Enterprise These interfaces are implemented Sharing XML by the vendors to surface information currently within custody to the enterprise. (Slide from Stipe Fustar, PowerGrid 360) 68 Typical Web Services System A Integration Layer WS receiveMarketMeterData WS broadcastMarketMeterData retrieveMarketMeterData WS PI WS receiveMarketMeterData WS broadcastMarketMeterData BITS retrieveMarketInterchange WS Bid Interchange Transaction Scheduling system broadcastInvoiceData WS receiveInvoiceData WS WS broadcastStatusInvoiceData broadcastGeneralLedgerData WS receiveGeneralLedgerData WS MC (Slide from Stipe Fustar, PowerGrid 360) 69 (Slide from Stipe Fustar, PowerGrid 360) 70 (Slide from Stipe Fustar, PowerGrid 360) 71 CAISO Project Statistics 22 Systems OASIS • Dispatch System Default Energy Bids • MP Report Interface Interchange Scheduling System • Load Forecast Real Time Metering Congestion Revenue Rights • Transmission Capacity Adjusted Metering Intermittent Resources Calculator Market Participants Compliance • Real Time Nodal System – Bidding RMR Validation • Settlement and Market – Market Results Generation Outage Scheduling Clearing – Settlement Transmission Outage Scheduling – Outage Scheduling Market Quality System • Bid Interface and – Dispatch Signals Validation (ATF updates) Forward Market Nodal System 7 Vendors • Siemens - Market Systems EMS • ABB - EMS system • Areva - Settlement System • Legacy - CAISO system • Nexant - Congestion Revenue Rights System Appr 130 integrations between the 22 systems • MCG - Interchange Appr 75 message schemas Scheduling System Appr 175 service definitions • Potomac - Default Energy Appr 450 publisher/consumer testable data transfers Bids between systems 72 Other Case Stories* • The Green Button Standard – Green Button leverages CIM standards in the creation of a common way to share and view energy consumption data • Consumers Energy – Consumers Energy leverages IEC CIM for Enterprise Integration and an enterprise semantic model • Long Island Power Authority – Long Island Power Authority (LIPA) leverages IEC CIM for Enterprise Information Management and semantic integration initiatives • Sempra Energy – Sempra Energy uses CIM to support their OpEx 20/20 and Smart Metering programs, reducing the cost of systems integration, maintenance, and support *These are described in some detail in the Third Edition CIM Primer 73 OpenFMB Distributed Intelligence Vision Framework for distributed intelligent nodes (IoT) interacting with each other • 2015 Phase 1 scope was MicroGrid optimization and islanding transitions • 2016 Phase 2 added new use cases: DER Circuit Segment Management and Circuit Segment Optimization • 2017 Phase 3 extending CIM data model to include 61850, focus on Management Services and new use cases 74 Overall OpenFMB Design Process 75 CIM Acceptance • In use at hundreds of utilities throughout world – Used at TSOs, RTO/ISOs, IOUs, and Distribution Utilities – In Europe now being adopted by ENTSO-E and TOs • Many applications support CIM standards • Many suppliers sell application/products based on CIM • Endorsed and used by other standards organizations – Multispeak, Zigbee, HAN, ENTSO-E, NASBE, OASIS, etc. • Foundation for information exchange between utilities and/or other external organizations • Foundation for Model-Driven Integration (MDI) architecture based on an Enterprise InformatiSemantic Model (ESM) within an enterprise • Key building block in Smart Grid to achieve interoperability – 61968/70 are top 2 of 5 priority standards recognized by NIST & FERC in North America • CIM User Group to deal with questions and issues arising from increased use 76 Where to Get More Information About the CIM and Related Standards • Visit CIM User Group (CIMug) Web Site – cimug.ucaiug.org or www.cimug.org – Single site for gaining access to information about the CIM and related standards • Includes all draft standards being developed by IEC TC57 Working Groups 13, 14, 16, and 19 for CIMug members • Published IEC CIM standards available from online store at www.iec.ch – Now provide access to: • EPRI CIM Primers free from EPRI • Webinars streamed via YouTube • Announcements of CIM-related activities and events • Past meeting presentations • CIM electronic UML model in various formats • Lists of CIM-related tools and access to open source tools • Membership in various Groups, Projects, and Focus Communities • CIM issues lists and status of resolution • Help desk • Links to other CIM-related sites • IEEE PES Power and Energy magazine - CIM Special Edition Jan-Feb 2016 • Gartner/EPRI CIM Survey report – see 2016 Atlanta CIMug meeting 77 Addressing Objections to the Use of the CIM Standards • Claim: CIM is not stable – Fact: The CIM UML model is evolving as new applications are identified – Fact: Only small part of CIM information model is used for a given interface, so change of information model unlikely to affect specific interface. – Solution: Version control - tie interface designs to project specifications, not directly to standard • CIM is to complex too learn and contains many parts I do not need – Fact: The overall CIM UML model is large and complex – Reality: A typical interface requires only very small subset of information model • CIM creates too much overhead in message content – Fact: Only instantiated concrete class/attributes are actually sent in a message instance – Reality: Message payload is no larger than any XML formatted message • I don’t want to add in an extra step of converting to CIM for system integration – Fact: There is an extra step of mapping to CIM for one connection – Reality: Consequence of not mapping to a common language is solution that does not scale: • n(n-1) instead of 2n connection mappings • I can’t expect my vendors to adopt the CIM model for their interface – Fact: Only a few parts of the CIM need to be “Known” by the vendor – Reality: Approach is to specify the mappings to a common language (CIM) as part of the interface contract • I don’t want to convert all my metadata to the CIM – Fact: CIM is a starter kit – Reality: Use CIM as appropriate for building your own ESM – far better than starting from scratch • CIM does not contain everything I need or in the form I need for my interfaces – Fact: CIM UML is extensible – Reality: Many utilities still use the CIM as a starting point, using namespaces to maintain traceability 79 Concluding Remarks • Bottom line: CIM standards are different and much more powerful – Can be applied in many ways – Support many types of functions/applications through combination of reuse and extension – Architecture supports future, unknown applications Questions • For more info, contact: – Terry Saxton, Xtensible Solutions – [email protected] : +1 612 396 7099 80