Energy management system application program interface (EMS-API) – Part 456: Solved power system state profiles
Introduction: This document is one of several parts of the IEC 61970 series that defines common information model (CIM) datasets exchanged between application programs in energy management systems (EMS). The IEC 61970-300 series specifies the common information model (CIM). The CIM is an abstract model that represents the objects in an electric utility enterprise typically needed to model the operational aspects of a utility. This document is one of the IEC 61970-400 series of component interface standards that specify the semantic structure of data exchanged between components (or applications) and/or made publicly available data by a component. This document describes the payload that would be carried if applications are communicating via a messaging system, but the standard does not include the method of exchange, and therefore is applicable to a variety of exchange implementations. The examples in this document are based on the exchanged data formatted specified in IEC 61970-552 CIM XML model exchange standard. This document specifies three profiles: The Steady State Hypothesis (SSH) profile that describes power flow application input variables such as voltage set points, switch statuses etc. The topology profile (TP) that describes a bus-branch model. A topology model may be created by a network model builder from a node-breaker model with SSH as inputs using topology processing or by a tool where a user interactively builds a topology model. Therefore, a topology model is defined as
Scope: This part of IEC 61970 belongs to the IEC 61970-450 to IEC 61970-499 series that, taken as a whole, defines at an abstract level the content and exchange mechanisms used for data transmitted between power system analyses applications, control centres and/or control centre components. The purpose of this document is to rigorously define the subset of classes, class attributes, and roles from the CIM necessary to describe the result of state estimation, power flow and other similar applications that produce a steady-state solution of a power network, under a set of use cases which are included informatively in this document. This document is intended for two distinct audiences, data producers and data recipients, and can be read from those two perspectives. From the standpoint of model export software used by a data producer, the document defines how a producer may describe an instance of a network case in order to make it available to some other program. From the standpoint of a consumer, the document defines what that importing software must be able to interpret in order to consume power flow cases. There are many different use cases for which use of this document is expected and they differ in the way that the document will be applied in each case. Implementers are expected to consider what use cases they wish to cover in order to know the extent of different options they must cover. As an example, the profiles defined in this document will be used in some cases to exchange starting conditions rather than solved conditions, so if this is an important use case, it means that a consumer application needs to be able to handle an unsolved state as well as one which has met some solution criteria.
Contents:
- FOREWORD
- INTRODUCTION
- Scope