The common information model (CIM) is an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration and interoperability of network applications developed independently by different vendors, between entire systems running network applications developed independently, or between a system running network applications and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modelled to the extent necessary to support power system simulation and inter-control centre communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally.

The object classes represented in the CIM are abstract in nature and can be used in a wide variety of applications. The use of the CIM goes far beyond its application in an EMS. This document should be understood as a tool to enable integration in any domain where a common power system model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation.

Due to the size of the complete CIM, the object classes contained in the CIM are grouped into several logical Packages, each of which represents a certain part of the overall power system being modelled. Collections of these Packages are progressed as separate International Standards. This document specifies a Base set of packages which provide a logical view of the functional aspects of Energy Management System (EMS) and power system modelling information within the electric utility enterprise that is shared between all applications. Other standards specify more specific parts of the model that are needed by only certain applications. Subclause 4.3 of this document provides the current grouping of packages into standards documents.