No abstract

The optimal planning, operation, and management of electricity transmission networks requires a wide range of software applications, such as energy management systems, network planning tools, data historians, and asset management applications, which all need to exchange data with each other. Standard data models make these data exchanges possible by formally defining the semantics of the information to be shared among the power system applications. The common information model (CIM) as defined by the International Electrotechnical Commission (IEC) Technical Committee (TC) 57 is the most widely accepted standard data model that promotes interoperability in electricity power systems. This chapter gives an overview of the CIM IEC 61970 transmission series by describing its scope, structure, modeling aspects, exchange formats, integration processes, and tools. Moreover, it presents real case studies showing the benefits of adopting IEC 61970 series in terms of transmission network operation and planning.

No abstract

Abstract--Electricity network resources are frequently identified within different power systems by inhomogeneous names and identities due to the legacy of their administration by different utility business domains. The IEC 61970 Common Information Model (CIM) enables network modeling to reflect the reality of multiple names for unique network resources. However this issue presents a serious challenge to the integrity of a shared CIM repository that has the task of maintaining a resource manifest, linking network resources to master identities, when unique network resources may have multiple names and identities derived from different power system models and other power system applications. The current approach, using CIM 15, is to manage multiple resource names within a singular CIM namespace utilizing the CIM "IdentifiedObject" and "Name" classes. We compare this approach to one using additional namespaces relating to different power systems, similar to the practice used in CIM extensions, in order to more clearly identify the genealogy of a network resource, provide faster model import times and a simpler means of supporting the relationship between multiple resource names and identities and a master resource identity.