Detail of GB/T 43259.302-2023

Introduction of GB/T 43259.302-2023

GB/T 43259.302-2023 Energy management system application program interface (EMS-API) - Part 302: Common information model (CIM) dynamics 1 Scope 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 of energy management system (EMS) applications developed independently by different vendors, between entire EMSs developed independently, or between an EMS 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 communication between control centres. 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. Due to the size of the complete CIM, the object classes contained in the CIM are grouped into a number of logical packages, each of which represents a certain part of the overall power system being modelled. Collections of these packages are being developed as separate International Standards. This particular document specifies a Dynamics package which contains extensions to the CIM to support the exchange of models between software applications that perform analysis of the steady-state stability (small-signal stability) or transient stability of a power system as defined by IEEE / CIGRE Definition and classification of power system stability IEEE/CIGRE joint task force on stability terms and definitions. The model descriptions in this document provide specifications for each type of dynamic model as well as the information that needs to be included in dynamic case exchanges between planning/study applications. The scope of the CIM extensions specified in this document includes: • standard models: a simplified approach to describing dynamic models, where models representing dynamic behaviour of elements of the power system are contained in predefined libraries of classes which are interconnected in a standard manner. Only the names of the selected elements of the models along with their attributes are needed to describe dynamic behaviour. • proprietary user-defined models: an approach providing users the ability to define the parameters of a dynamic behaviour model representing a vendor or user proprietary device where an explicit description of the model is not provided by the standard. The same libraries and standard interconnections are used for both proprietary user-defined models and standard models. The behavioural details of the model are not documented in the standard, only the model parameters. 2 Normative references The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 60050 (all parts) International Electrotechnical Vocabulary IECTS 61970-2 Energy management system application program interface (EMS-API) – Part 2: Glossary IEC 61970-301 Energy management system application program interface (EMS-API) - Part 301: Common information model (CIM) base 3 Terms and definitions For the purposes of this document, the terms and definitions contained in IEC 60050 (for general glossary), IEC 61970-2 (for EMS-API glossary definitions) and the following apply. 3.1 application program interface API set of public functions provided by an executable application component for use by other executable application components 3.2 common information model CIM abstract model that represents all the major objects in an electric utility enterprise typically contained in an EMS information model Note: By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of EMS applications developed independently by different vendors, between entire EMSs developed independently, or between an EMS and other systems concerned with different aspects of power system operations, such as generation or distribution management. 3.3 CIMXML serialisation format for exchange of XML data as defined in this document 3.4 Document Object Model DOM platform- and language-neutral interface defined by the World Wide Web Consortium (W3C) that allows programs and scripts to dynamically access and exchange the content, structure and style of documents 3.5 document type definition DTD specific document for describing the vocabulary and syntax associated with an XML document Note: XML Schema and RDF are other forms that can be used. 3.6 energy management system EMS computer system comprising a software platform providing basic support services and a set of applications providing the functionality needed for the effective operation of electrical generation and transmission facilities so as to assure adequate security of energy supply at minimum cost 3.7 HyperText Markup Language HTML mark-up language used to format and present information on the Web 3.8 model collection of data describing objects or entities real or computed, the semantics of which is defined by profiles (3.9) in the context of CIM Note: In power system analysis, a model is a set of static data describing the power system. Examples of models include the static network model, the topology solution, and the network solution produced by a power flow or state estimator application. 3.9 profile schema that defines the structure and semantics of a model that may be exchanged and is a restricted subset of the more general CIM 3.10 profile document collection of profiles intended to be used together for a particular business purpose 3.11 Resource Description Framework RDF language recommended by the W3C for expressing metadata that machines can process Simply Note: RDF uses XML as its encoding syntax. 3.12 RDF schema schema specification language expressed using RDF to describe resources and their properties, including how resources are related to other resources, which is used to specify an application-specific schema 3.13 real-world objects objects that belong to the real world problem domain as distinguished from interface objects and controller objects within the implementation Note 1: The real-world objects for the EMS domain are defined as classes in IEC 61970-301. Note 2: Classes and objects model what is in a power system that needs to be represented in a common way to EMS applications. A class is a description of an object found in the real world, such as a PowerTransformer, GeneratingUnit, or Load that needs to be represented as part of the overall power system model in an EMS. Other types of objects include things such as schedules and measurements that EMS applications also need to process, analyze, and store. Such objects need a common representation to achieve the purposes of the EMS-API standard for plug-compatibility and interoperability. A particular object in a power system with a unique identity is modelled as an instance of the class to which it belongs.

Contents of GB/T 43259.302-2023