UNE-EN 61970-452:2017

This standard, IEC 61970-452, is a member of the IEC 61970-450 to 499 series that, taken asa whole, defines at an abstract level the content and exchange mechanisms used for datatransmitted between control centers and/or control center components, such as powersystems applications.The purpose of this document is to rigorously define the subset of classes, class attributes,and roles from the CIM necessary to execute state estimation and power flow applications.The North American Electric Reliability Council (NERC) Data Exchange Working Group(DEWG) Common Power System Modeling group (CPSM) produced the original datarequirements, which are shown in Annex D. These requirements are based on prior industrypractices for exchanging power system model data for use primarily in planning studies.However, the list of required data has been extended to facilitate a model exchange thatincludes parameters common to breaker-oriented applications. Where necessary thisdocument establishes conventions, shown in Clause 5, with which an XML data file mustcomply in order to be considered valid for exchange of models.This document is intended for two distinct audiences, data producers and data recipients, andmay be read from two perspectives.From the standpoint of model export software used by a data producer, the documentdescribes a minimum subset of CIM classes, attributes, and associations which must bepresent in an XML formatted data file for model exchange. This standard does not dictate howthe network is modelled, however. It only dictates what classes, attributes, and associationsare to be used to describe the source model as it exists.Optional and required classes, attributes and associations must be imported if they are in themodel file prior to import. If an optional attribute does not exist in the imported file, it doesnot have to be exported in case exactly the same data set is exported, i.e. the tool is notobliged to automatically provide this attribute. Business processes governing differentexchanges can require mandatory exchange of certain optional attributes or associations.Furthermore, it should be noted that an exporter may, at his or her discretion, produce anXML data file containing additional class data described by the CIM RDF Schema but notrequired by this document provided these data adhere to the conventions established inClause 5.From the standpoint of the model import used by a data recipient, the document describes asubset of the CIM that importing software must be able to interpret in order to import exportedmodels. As mentioned above, data providers are free to exceed the minimum requirementsdescribed herein as long as their resulting data files are compliant with the CIM RDF Schemaand the conventions established in Clause 5. The document, therefore, describes additionalclasses and class data that, although not required, exporters will, in all likelihood, choose toinclude in their data files. The additional classes and data are labeled as required (cardinality1..1) or as optional (cardinality 0..1) to distinguish them from their required counterparts.Please note, however, that data importers could potentially receive data containing instancesof any and all classes described by the CIM RDF Schema.