Iec 61968 4 2007

INTERNATIONAL STANDARD IEC 61968-4 First edition2007-07 Application integration at electric utilities – System interfaces for distribution management – Part 4: Interfaces for records an

General

The message types defined in IEC 61968-4 are based on a logical partitioning of the DMS business functions and components called the IEC 61968-1 Interface reference model

IEC 61968-1 outlines message types that are derived from a static information model, ensuring uniformity in field names and data types Each message type consists of fields taken from the information model classes, designed to meet the needs of most typical applications However, specific project implementations may require adjustments to the field set, following the methodology described in IEC 61968-1.

Interface reference model

The IEC 61968 series does not aim to dictate the specific applications and systems that vendors must create Instead, it anticipates that a tangible application will deliver the functionalities of one or more abstract components outlined in the standard These abstract components are categorized according to the business functions of the IEC 61968-1 interface reference model.

Records and asset management functions and components

The Records and Asset Management part of the IEC 61968-1 Interface reference model shows those functions and typical components that are applicable to the message types defined in IEC 61968-4

LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.

According to IEC 61968-4, the defined message types are anticipated to have typical abstract components that serve as information producers, while the typical consumers of this information are the components outlined in IEC 61968-1.

Static information model

The information model relevant to records and asset management consists of classes that provide a template for the attributes for each message The classes are defined in detail in

IEC 61970-301 or in future document IEC 61968-11

4 Records and Asset message types

Summary

The records and asset message types describe information for the following types of document:

In accordance with IEC 61968-4, all message types include elements that align with CIM classes, encompassing both native and inherited attributes It is important to note that, unless stated otherwise, all associations between message types are considered simple associations.

Network Data Set message type

Message content

A NetworkDataSet message encompasses data relevant to various segments of a distribution network, which is essential for operational or extension planning studies This message may include information pertaining to one or multiple feeders, representing either the 'As built' network or a proposed network intended for analysis.

A NetworkDataSet message can include references to other documents that hold static reference data, such as TypeAssetCatalogue or AssetCatalogue Additionally, it may reference Assets that fulfill the roles of the related types of PowerSystemResources.

The same is true for other “leaf node” elements such as Organisations, Locations, and

In this context, only the identifier for the referenced data should be included in the message type, while the actual data for these referenced elements is delivered through other message types such as TypeAssetCatalogue, AssetCatalogue, AssetList, and Measurements.

The network's fundamental structure is organized hierarchically, as illustrated in Figure 1 The initial dynamic state, which includes the positions of switches, is represented by a collection of MeasurementValues These values can be modified through the ShowMeasurementList message, as specified in IEC 61968-3.

Message format

Created NetworkDataSet, changed NetworkDataSet, show NetworkDataSet and deleted

NetworkDataSet have the same message formats as shown in Figure 1

Figure 1 – Network Data Set message format (continued on next page)

Change Set message type

Message content

A ChangeSet message type contains updates required in a transaction for an existing

The NetworkDataSet is the primary element referenced in this message type, with each step in the ChangeSet detailed by a separate ChangeItem A ChangeItem specifies the type of change—whether it is an addition, deletion, or modification—and includes a sequence number for that change within the ChangeSet The specifics of the changes are represented in an instance of NetworkDataSet, which is a child element of the ChangeItem Only the identifiers of the relevant NetworkDataSet messages are included in a ChangeSet message, while the actual content is provided in accompanying NetworkDataSet messages.

The basic structure is a hierarchy as shown in the Figure 2.

Message format

Created ChangeSet, changed ChangeSet, show ChangeSet and deleted ChangeSet have the same message formats as shown in Figure 2

Figure 2 – Change Set message format

Presentation message type

Message content

A Presentation message can convey location information for various elements within the Common Information Model, especially those in the distribution network It serves to identify individual assets or power system resources and can accompany the NetworkDataSet with a collection of location data The fundamental structure follows a hierarchical format, as illustrated in Figure 3 For details on utilizing Geography Markup Language (GML), please refer to Annex A.

Message format

Created Presentation, changed Presentation, show Presentation and deleted Presentation have the same message formats as shown in Figure 3

Figure 3 – Presentations message format (continued)

Asset List message type

Message content

An AssetList message can contain various amounts of data for any set of utility assets An

AssetList message may contain references to static reference data such as elements of a

AssetCatalogue or TypeAssetCatlogue It may also contain references to the types of

PowerSystemResources define the specific role of an Asset, indicating whether it is installed or merely in inventory This principle also applies to other "leaf node" elements, including Organisations, Locations, and Measurements, where only the identifier for the referenced data is included in this message type Detailed data for these referenced elements is conveyed through different message types, such as TypeAssetCatalogue.

Message format

Created AssetList, changed AssetList, show AssetList and deleted AssetList have the same message formats as shown in Figure 4

Figure 4 – Asset List message format (continued)

Asset Catalogue message type

Message content

An AssetCatalogue is a comprehensive collection of information about the various types of products and materials utilized for the construction, installation, maintenance, and operation of assets.

Asset(s) Each catagoue item is for a specific product available from a specific supplier An

The AssetCatalogue message may include identifiers for static reference data, such as elements from a TypeAssetCatalogue or Specifications, as well as other "leaf node" elements like Organisations In these instances, only the identifiers of the referenced data are included in this message type, while the actual data for these elements is delivered through different message types, such as TypeAssetCatalogue.

Message format

Created AssetCatalogue, changed AssetCatalogue, show AssetCatalogue and deleted

AssetCatalogue have the same message formats as shown in Figure 5

Figure 5 – Asset Catalogue message format (continued)

Type Asset Catalogue message type

Message content

A TypeAssetCatalog message includes data for various utility asset types, serving as a comprehensive collection of information on generic asset types for design and analysis purposes Notably, a TypeAsset is not linked to any specific manufacturer.

The TypeAssetCatalogue message can reference other documents that contain static reference data, including elements of an AssetCatalogue and other "leaf node" elements like Organisations In these instances, only the identifier for the referenced data is included in the message type, while the actual data for these elements is delivered through different message types, such as AssetCatalogue.

Message format

Created TypeAssetCatalogue, changed TypeAssetCatalogue, show TypeAssetCatalogue and deleted TypeAssetCatalogue have the same message formats as shown in 44444455 Figure 6

Figure 6 – Type Asset Catalogue message format (continued)

Use of the Geography Markup Language (GML)

For presentation purposes (refer to Subclause 4.4), IEC 61968-4 recommends use of the

Geography Markup Language (GML) facilitates the exchange of geographic information related to utility resources and landbase data Additionally, the Presentation message type can be utilized to share basic rendering data about utility resources without the need for GML.

GML offers a comprehensive range of features that are beneficial in various situations When utilizing GML, it's important to use the correct GML elements, which are easily identified by the "Gml" prefix on the CIM elements within the Presentation message type.

This should enable implementations to use these two standards together with only minimal and straightforward transformations being necessary

GML, or Geography Markup Language, is an XML-based format designed for the transport and storage of geographic information, encompassing both the geometry and attributes of geographic features Its foundational concepts for modeling the world are derived from the Open GIS Consortium Abstract Specification.

GML offers various object types for geographic description, including features, coordinate reference systems, geometry, and topology A geographic feature represents a real-world phenomenon linked to a specific location on Earth Thus, a digital representation of reality can be viewed as a collection of these features The state of each feature is characterized by a set of properties, with each property defined as a {name, type, value} triple.

Geographic features with geometry are those with properties that may be geometry-valued

A feature collection is a set of features that can be considered a single feature type, possessing its own unique properties in addition to those of the individual features it includes.

The type definition of a feature determines the number and types of properties it possesses Geographic features with geometry include properties that can hold geometric values A feature collection is essentially a group of features that can also be considered a feature itself, which means it has its own feature type and may possess unique properties in addition to those of the individual features it contains.

A coordinate reference system comprises axes that connect to the Earth via a datum, which defines its size and shape In GML, geometries specify the coordinate reference system used for their measurements.

“parent” geometry element of a geometric complex or geometric aggregate makes this indication for its constituent geometries.

The Geography Markup Language (GML) is an XML-based standard for encoding geographic information, ensuring compliance with ISO 19118 For detailed specifications, refer to the GML standard documentation available at the Open Geospatial Consortium's website The XML schema for GML feature objects can be found in the file feature.xsd, accessible at the provided schema link.

2 Cox, Simpon, Daisey, Paul, Lake, Ron, Portele, Clemens, Whitseside, Arliss 2003 “OpenGIS® Geography

Markup Language (GML) Implementation Specification,” Open GIS Consortium, Inc

Tiêu đề	Interfaces for Records and Asset Management
Trường học	International Electrotechnical Commission
Chuyên ngành	Electrical and Electronic Technologies
Thể loại	Standards Document
Năm xuất bản	2007
Thành phố	Geneva

Định dạng
Số trang	54
Dung lượng	1,41 MB