CIM Standards Overview And Its Role In The Utility .

CIM Standards OverviewAnd Its Role in the UtilityEnterprise - Part 2CIM Users GroupAmsterdam, NetherlandsTerry 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 information2

Next - Context LayerInformation and Semantic ModelsInformation ModelCIM UML Generalized model of all utility objects and theirrelationships Application independent, but defines all conceptsneeded for any applicationContextProfilesMessage SyntaxMessage/FileFormat(XSD, RDFSchema, OWL)Contextual layer restricts informationmodel Specifies which part of CIM is used for given profileMandatory and optionalRestrictionsBut cannot add to information modelMessage syntax describes format forinstance data Can re-label elements Change associations to define single structure formessage payloads Mappings to various technologies can be defined3

How the CIM is Applied to SpecificInformation Exchanges The interfaces defined under CIM are defined by Profiles– A profile specifies the information structure of exchangedinformation by creating contextual semantic models Contextual semantic models are a subset of the overall CIMinformation model (i.e., they inherit their structure from the CIM UMLmodel)– There is typically a family of related interfaces defined within aprofile– Products implement support for profiles in the form of CIM/XMLimport/export software or ESB run-time adapters– Testing occurs against profiles– “CIM compliance” is defined against profiles – otherwise the termis meaningless Note: We saw that the CIM Information Model is partitioned into sub-domains by IECWGs––But these groups work hard to ensure there is a single, unified semantic model over the wholeutility domainThat 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 Power System Network Model Exchange– WG14 61968 Message Payloads for System Integration5

WG13 Reference Diagram for Power Flow Cases66

61970 Profiles Currently DefinedPart 452 Static TransmissionNetwork Model Profiles Equipment (EQ)– Identifies equipment, basiccharacteristics, and electricalconnectivity of steady statenetwork model– Also known as CommonPower System Model (CPSM) Many Interoperability (IOP)tests since year 2000 In use in many countries 61968-13 distribution model(CDPSM) based on EQ withsome extensionsPart 456 - Solved PowerSystem State Profiles Steady State olsLimits– Energy distribution Topology (TP)– The result of topologyprocessing. i.e. description ofhow equipment is connectedat a particular point in time State Variables (SV)– Result of a state estimator orpower flow, or the startingconditions of state variables7

61970 Profiles Part 457 - Dynamics (DY)– Adds dynamics to static network model for running system simulations Part 453 - Diagram Layout (DL)– Describes how equipment objects are placed on schematic diagrams fordisplay purposes8

61970-452 Static TransmissionNetwork Model Profiles Also known as Common Power System Model (CPSM) Many Interoperability (IOP) tests since year 2000 In use in many countries 61968-13 distribution model (CDPSM) based on these profiles as well9

Plus 61970-451 Measurement and Controland -456 Solved System State Profiles61970-451Profile61970-456 ProfilesStateVariablesMeasurementand 52ProfilesConnectivityEquipmentModelSchedulesAdds SCADAAdds steady statesolution of powersystem caseproduced bypower flowapplicationsDependencies viareferences toCPSM Part 45210

Plus 61970-451 Measurement and Controland -456 Solved System State Profiles61970-451Profile61970-456 ProfilesStateVariablesMeasurementand ControlSSHTopologyAdds dynamicmodels used insystem esConnectivityEquipmentModelSchedulesDependencies viareferences toCPSM Part 45211

Plus 61970-453 Diagram LayoutProfile61970-456 ProfilesStateVariablesMeasurementSetFuture 61970457 surementSpecifications61970-452ProfilesAdds diagramlayout info nObjectsDependenciesvia referenceto CPSM Part452DiagramLayoutSchedules12

Typical Workflow for rofileFull 813

TC57 CIM Standardsfor Power System Model ExchangeInformation and Semantic ModelsInformation ModelConforms toIEC 61970-301 CIMCIM UML Generalized model of all utility objects and theirrelationships Application independent, but defines all conceptsneeded for any applicationContextConforms tocollection ofStandard4xx ProfilesMessage SyntaxConforms toIEC 61970-552 and -501CIM XML Model Exchange FormatProfilesMessage/FileFormat(XSD, RDFSchema, OWL)Contextual layer restricts informationmodel Specifies which part of CIM is used for given profileMandatory and optionalRestrictionsBut cannot add to information modelMessage syntax describes format forinstance data Can re-label elements Change associations to define single structure formessage payloads Mappings to various technologies can be defined14

Presentation Contents Profiles for business context– WG13 61970 Profiles for Power System Network Model Exchange– WG14 61968 Message Payloads for System Integration15

FromInformationModel toSyntactic /ProfilesUML WorldMessageAssemblyXML Syntactic WorldMessageSyntax ?xml version "1.0" encoding "UTF-8"? xsd:elementname « MT EnergyTransaction" xsd:sequence xsd:elementname « EnergyTransaction"/ xsd:sequence xsd:element name « Name"/ xsd:element name « Type"/ /xsd:sequence /xsd:element SyntacticModel16

Working Group 14:Establishing A Common Language For Enterprise ApplicationIntegration In the IEC 61968 Series of StandardsUtility istribution AutomationAutomationNetworkOperationRecords& AssetManagementSubstationSubstation Protection,Protection,MonitoringMonitoring andand yIEC structionMeterReading &Control(ERP, Billing,Energy trading,other systems)CorporateLANOperationalPlanning al.org/http://www.iec.chRTURTU CommunicationsCommunications17

Smart Grid Interoperability Ability of systems to operate in coordination– Ability to exchange and use information appropriately Requires standard interface definitions– Governed by open industry working groups Provides Benefits– Promotes loosely-coupled integration Allows incremental functional enhancements Creates market for reusable, compatible components– Only one integration instead of many To an open, public, standard interface– Instead of each proprietary vendor or utility interface18

Smart Grid Challenges Requires Integration – LOTS of integration– Onslaught of new applications and technologies AMI, MDMS, HAN, DR, ADE, etc. In a complex IT environment– Many custom systems, legacy technologies– Typically departmentally controlled – within “silos” Need ability to govern, manage, and share resources– at the Enterprise level and beyond (external services)– Aging / outsourced systems and IT workforce– Historically, extremely low R&D expenditures Must ramp up capabilities quickly19

The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For IdentifyingInformation Exchange Requirements Among Utility Business FunctionsAll IEC 61968 Activity Diagrams and Sequence Diagrams are organized by the IRMNetworkOperation(NO)IEC 61968-3Records &AssetManagement(AM)IEC 61968-4OperationalPlanning nal Systems:Energy Trading (ET)Retail (RET)Sales (SAL)Stakeholder Planning & Management (SPM)Supply chain and logistics (SC)Human Resources (HR)IEC 61968-5IEC 61968- 6Applicable parts ofIEC 61968 SeriesEnterprise Application Integration and Enterprise Service Bus MiddlewareIEC 61968-7NetworkExtensionPlanning(NE)IEC 61968-8CustomerInquiry(CS)IEC 61968-9MeterReading &Control(MR)IEC 61970 &Applicable parts ofIEC 61968 SeriesBulk EnergyManagement(EMS)Utility Electric Network Planning, Constructing,Maintaining, and OperatingIEC 62325 &Applicable parts ofIEC 61968 SeriesMarketOperationsApplicable parts ofIEC 61968 SeriesExternal Systems:Customer AccountManagement (ACT)Financial (FIN)Business Planning andReporting (BPR)Premises (PRM)Enterprise Resource Planning, SupplyChain, and General Corporate Services20

The Business Sub-Function Level of theIRM for IEC 61968 ScopeNetwork OperationsRecords & AssetManagementNetwork OperationsMonitoring (NMON)Operation Statistics& Reporting (OST)Network Control(CTL)Network Calculations- Real Time (CLC)GeographicalInventory (GINV)Network OperationSimulation (SIM)Maintenance &Inspection (MAI)Scheduling& Dispatch (SCH)Fault Management(FLT)Dispatcher Training(TRN)General inventorymanagement (GIM)Switch ActionScheduling (SSC)Construction WMS(CON)FieldRecording (FRD)Asset InvestmentPlanning (AIP)Power Import Sched.& Optimization (IMP)Design &Estimate (DGN)Operational FeedbackAnalysis (OFA)Substation & NetworkInventory (EINV)Operational Planning& OptimizationMaintenance andConstructionApplication Integration InfrastructureNetwork s (NCLC)Customer Service(CSRV)Project Definition(PRJ)Trouble CallManagement (TCM)ConstructionSupervision (CSP)Point Of Sale(POS)ComplianceManagement (CMPL)Meter Reading & ControlMeter Reading(RMR)Meter DataManagement IMDM)Advanced MeteringInfrastructure (AMI)Metering System(MS)Demand Response(DR)Meter Maintenance(MM)Load Control(LDC)Meter Data (MD)External SystemsMeter Operations(MOP)21

The IEC 61968 Basic Message Structure22

Message Header23

IEC 61968-9: Interface Standard for MeterReading and Control24

Scope/Purpose To Define the exchange of information between aMetering System and other systems within the Utilityenterprise Specifies the information content of a set of messagetypes that can be used to support many of thebusiness functions related to Merter Reading andControl. Typical uses of the message types include:– Meter Reading and Meter Control– Meter Events– Customer Data Synchronization and Customer Switching25

Scope of Part 9Area Causally/IndirectlyImpacted by or impactingIEC 61968-9Area of Direct Impactusing IEC 61968-9CustomerElectric UtilityStandard or ProprietaryCommunicationInfrastructuresEnterprise IntegrationInfrastructure(e.g. ESB, SOA, )MeterCustomerPANDeviceEnterpriseApplicationsIEC 61968-9 MessagesMessages defined by IEC61968-9 and based uponIEC CIM, conveyed using avariety of integrationtechnologiesMappings, translationsand/orforwardiing asneededMeter orGatewayHead EndSystemsPANPANDeviceCustomerPANDeviceMessages defined byrelevant standards orvendors. May use a widevariety of communicationtechnologiesMapping, translationsand/or forwarding asneededMeter orGatewayPANPANDevicePANDeviceMessages definedby PAN/HANspecifications26

Reference Model The Reference Model provides examples of the logicalcomponents and data flows related to this standard. The Meter is treated as an “end device” An End Device:––––––Has a unique identityIs managed as a physical assetMay issue eventsMay receive control requestsMay collect and report measured valuesMay participate in utility business processes The Reference Model describes the flows between thecomponents.27

Part 9 Reference Model28

Part 9 Message Types29

Typical Message Payload Definition EndDeviceEvent MessageEndDeviceEventMessages Conveyevents related to: Sustained OutageDetection Momentary OutageDetection Low VoltageThreshold Detection High VoltageThreshold Detection Distortion MeterHealth Tamper Detection Revenue Event30