BSI BS EN 61970-456:2013+A1:2016

Withdrawn Consolidated
Energy management system application program interface (EMS-API) -- Solved power system state profiles

Best Price Guarantee Feb 29, 2016 English 42 Pages

This Document Has Been Superseded

A newer publication replaces it: BSI BS EN IEC 61970-456


Sub Total (1 Item(s)) $ 0.00
Estimated Shipping $ 0.00
Total (Pre-Tax) $ 0.00

You own the digital copy of this edition

View in Library
or
British Standards Institution Logo

BSI BS EN 61970-456:2013+A1:2016

Energy management system application program interface (EMS-API) -- Solved power system state profiles

PUBLISH DATE 2016
PAGES 42
BSI BS EN 61970-456:2013+A1:2016

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 control centers and/or control center components.

The purpose of this part of IEC 61970 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 standard.

This standard is intended for two distinct audiences, data producers and data recipients, and may be read from those two perspectives. From the standpoint of model export software used by a data producer, the standard describes 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 standard describes what that importing software must be able to interpret in order to consume solution cases.

There are many different use cases for which use of this standard is expected and they differ in the way that the standard will be applied in each case. Implementers should consider what use cases they wish to cover in order to know the extent of different options they must cover.

As an example, this standard 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.

Loading...

Failed to load document history.

Publish Date Document Id Type View