Homepage>ČSN EN IEC 61970-456 ed. 3 - Rozhraní aplikačního programu pro systémy řízení elektrické energie (EMS-API) - Část 456: Profily řešení stavu napájecí soustavy
Sponsored link
Vydáno: 01.08.2022
ČSN EN IEC 61970-456 ed. 3
Rozhraní aplikačního programu pro systémy řízení elektrické energie (EMS-API) - Část 456: Profily řešení stavu napájecí soustavy
Format
Availability
Price and currency
Anglicky Hardcopy
In stock
41.80 €
S účinností od 2025-01-19 se nahrazuje ČSN EN IEC 61970-456 ed. 2 (33 4910) z listopadu 2018, která do uvedeného data platí souběžně s touto normou.
Označení normy:
ČSN EN IEC 61970-456 ed. 3
Třídící znak:
334910
Počet stran:
116
Vydáno:
01.08.2022
Harmonizace:
Norma není harmonizována
Katalogové číslo:
514769
DESCRIPTION
ČSN EN IEC 61970-456 ed. 3
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.