KR20200082051A - System for managing ontology data of power grid - Google Patents

Abstract

The present invention relates to a power system ontology data managing system, which is to efficiently manage CIM-based power system data. The present invention is to provide a power system ontology data management system which is easy for management, exchange, and inquiry of data between EMSs in an environment to which an IEC61970 standard is applied. According to a desirable embodiment of the present invention, the power system ontology data managing system comprises: a static ontology DB for storing an original CIM-XML for a measurement-related facility; a real-time ontology DB for storing the original CIM-XML for a measurement value; a relational DB for storing a real-time measurement value; a mapping information storage for mapping and storing a facility type, a measurement-related facility mRID, an ontology measurement value key, and a relational DB measurement value key; and a CIM object management unit for managing the static ontology DB, the real-time ontology DB and the relational DB on the basis of mapping information on the facility type, the measurement-related facility mRID, the ontology measurement value key, and the relational DB measurement value key.

Description

Power System Ontology Data Management System {SYSTEM FOR MANAGING ONTOLOGY DATA OF POWER GRID}

The present invention relates to a power system ontology data management system, and more particularly, to a power system ontology data management system for efficient management of CIM-based power system data.

IEC61970 is a data exchange information model standard for power information between power EMSs developed in IEC TC57 WG13. Three standards are defined as CIM (Common Information Model), IEC61970 (transmission and power model), IEC61968 (distribution and metering), and IEC62325 (power transaction).

The standard models (profiles) all logical/physical/behavioral information of a power system based on UML for CIM-based power information data exchange, and expresses the XML format (CIM-XML) of data that exchanges the data and how to express the information. define. The standard excludes lower layer protocols or communication methods for data exchange from the standard.

1 is a schematic diagram of a CIM-XML based data exchange environment according to the prior art.

Referring to FIG. 1, an energy management system (EMS) and a power application generate power information in a CIM format or a vendor-dependent data model and exchange mutual data through CIM-XML.

2 is a process for a method of using a CIM standard information model according to the prior art.

Referring to FIG. 2, a profile such as XSD, RDFS, etc. may be generated using a schema created after extracting only the necessary parts from the UML model. In addition, the EMS can exchange data with external systems using XML documents (CIM-XML) based on the Resource Description Framework (RDF) that keeps the schema.

3 is a process for a data conversion method according to the information storage method of the CIM standard information model.

Referring to FIG. 3, a system using a CIM schema-based DB converts a CIM schema into a CIM profile, and then creates CIM-XML, and a system using a vendor-independent schema-based DB converts a vendor schema into a CIM profile, and then CIM -Write XML.

In the system as shown in FIG. 3, a complex UML structure is applied to the CIM schema, and a module for converting a CIM schema to a CIM profile and a module for converting a vendor schema to a CIM profile should be changed whenever the application standard changes.

4 is a schematic system structure in the case of constructing a relational DB based on a vendor-dependent data model according to the prior art.

Referring to FIG. 4, when data is exchanged between systems A and B, when system A is composed of a vendor-dependent data information model, system A always acquires data from system B and when data is transferred to system B, the vendor model is always used. And a CIM model must be configured. The CIM standard model has been in development since the early 2000s, and data models are constantly being changed and added. As the CIM standard model is constantly changing, continuous modification of the data conversion device is required.

5 is a system structure when constructing a data model with a CIM-based relational DB according to the prior art.

Referring to FIG. 5, when constructing a data model with a CIM-based relational DB, when exchanging data between AB systems, data is converted from CIM-type relational DB stored in the internal system to CIM-XML and from CIM-XML to relational DB. A conversion system is required, and since the data must be stored after organizing complex UML-type information into a relational DB, the relationship between tables becomes complicated. Due to the nature of the CIM data model, it is difficult to express inheritance between tables. And, when constructing a data model with a CIM-based relational DB, conversion between DB information and CIM-XML is easy because it is a CIM schema-based DB, but the relationship between UML is complicated, so performance is slow when querying database information.

6 is an example of a CIM-based model according to the prior art.

When constructing a data model with a CIM-based relational DB, the relational DB is constructed in the form of hundreds of classes with complex relationships based on the relationship in the form shown in FIG. 6. Therefore, it is necessary to go through a complicated inquiry step when acquiring data.

In summary, IEC61970 models power information in a UML manner and has a complex relationship between each model. When developing and operating an application that complies with the IEC61970 standard, when a table of a relational DB is defined using the UML model defined in the standard, a complex relational information table is created. In addition, since the data conversion between the relational DB and the CIM conforms to the standard information model, there is no difficulty in conversion, but when the standard changes, the relational database schema created based on the CIM must be changed. In addition, when the power model is composed of a vendor-independent independent information model, the data conversion device must be configured when exchanging data between systems, and continuous data must be performed when standards change.

[Advanced technical literature]

[Patent Document]

Korean Patent Publication No. 10-2018-0116793 (Invention name: CIM and OPC-UA based data interchange method, published date: 2018.10.26.)

Korean Patent Publication No. 1020160044340 (Invention name: CIM profile management system for exchanging standard data between EMS, Publication date: 2016.04.25.)

An object of the present invention is to provide a power system ontology data management system that facilitates data management, exchange, and inquiry between EMS in an environment to which the IEC61970 standard is applied.

A power system ontology data management system according to an exemplary embodiment of the present invention includes a static ontology DB storing original CIM-XML for a measurement-related facility; A real-time ontology DB that stores original CIM-XML for measured values; A relational DB that stores real-time measurement values; A mapping information store that maps and stores facility type, measurement-related facility mRID, ontology measurement value key, and relational DB measurement value key; And a CIM object management unit managing the static ontology DB, real-time ontology DB, and relational DB based on the mapping information of the facility type, measurement-related facility mRID, ontology measurement value key, and relational DB measurement value key.

The present invention can reduce the search to be made in 4 steps by a direct approach for each step, so that data can be searched. Mapping that manages mapping information between data on the static ontology DB, real-time ontology DB, and relational DB by constructing the DB storing the data retrieved at each stage in parallel with the static ontology DB, real-time ontology DB, and relational DB By providing an information storage, it is possible to easily manage, exchange, and query UML model-based data having complex relationships using mapping information.

1 is a schematic diagram of a CIM-XML based data exchange environment according to the prior art.
2 is a process for a method of using a CIM standard information model according to the prior art.
3 is a process for a data conversion method according to the information storage method of the CIM standard information model.
4 is a schematic system structure in the case of constructing a relational DB based on a vendor-dependent data model according to the prior art.
5 is a system structure when constructing a data model with a CIM-based relational DB according to the prior art.
6 is an example of a CIM-based model according to the prior art.
7 is a schematic diagram of a data management system according to an exemplary embodiment of the present invention.
8 is a process of storing equipment information in a data management system according to an exemplary embodiment of the present invention.
9 is a measurement information storage process in a data management system according to an exemplary embodiment of the present invention.
10 is a process of transferring data to an external system in a data management system according to an exemplary embodiment of the present invention.
11 is a measurement value inquiry process in a data management system according to an exemplary embodiment of the present invention.

The present invention can be applied to various changes and can have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing each drawing, similar reference numerals are used for similar components. In the description of the present invention, when it is determined that a detailed description of related known technologies may obscure the subject matter of the present invention, the detailed description will be omitted.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from other components.

For example, the first component may be referred to as a second component without departing from the scope of the present invention, and similarly, the second component may be referred to as a first component.

The term and/or includes a combination of a plurality of related described items or any one of a plurality of related described items.

When an element is said to be "connected" or "connected" to another component, it is understood that other components may be directly connected or connected to the other component, but other components may exist in the middle. It should be.

On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that no other component exists in the middle.

The terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "include" or "have" are intended to indicate the presence of features, numbers, steps, actions, components, parts or combinations thereof described herein, one or more other features. It should be understood that the existence or addition possibilities of fields or numbers, steps, operations, components, parts or combinations thereof are not excluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person skilled in the art to which the present invention pertains.

Terms, such as those defined in a commonly used dictionary, should be interpreted as having meanings consistent with meanings in the context of related technologies, and should not be interpreted as ideal or excessively formal meanings unless explicitly defined in the present application. Does not.

Hereinafter, a power system ontology data management system according to an exemplary embodiment of the present invention will be described with reference to FIGS. 7 to 11. 7 is a schematic diagram of a data management system according to an exemplary embodiment of the present invention. 8 is a process of storing equipment information in a data management system according to an exemplary embodiment of the present invention. 9 is a measurement information storage process in a data management system according to an exemplary embodiment of the present invention. 10 is a process of delivering data to an external system in a data management system according to an exemplary embodiment of the present invention. 11 is a measurement value inquiry process in a data management system according to an exemplary embodiment of the present invention.

Referring to Figure 7, the data management system CIM object management unit 10, static ontology DB (20, Static Information Ontology DB), real-time ontology DB (30, Real-time Information Ontology DB), relational DB (40), It may include a mapping information storage (50). The data management system can be mounted on the EMS.

The CIM object management unit 10 receives CIM-XML written using RDF grammar, stores CIM-XML itself for power facility information and attribute information in the Stacktack Ontology DB 20, and has high real-time data. For example, the CIM-XML for the measured value is stored in the real-time ontology DB 30, the measured value itself is stored in the relational DB 40 in a historical manner, and the facility type, mRID of the measurement-related facility, and ontology Measurement value keys and relational DB measurement value keys may be stored in the mapping information storage 50.

Here, the meaning of the facility type, the mRID of the measurement-related facility, the ontology measurement value key, and the relational DB measurement value key may be as follows.

Equipment type: Class according to IEC61970 standard

MRID of the measurement-related equipment: mRID of the object related to a specific measurement in the equipment (for example, in the case of a measurement-related equipment on the output side of the circuit breaker, mRID of the circuit breaker, mRID of the primary terminal of the circuit breaker connection, mRID of the secondary terminal of the circuit breaker connection , MRID of measurement information (secondary terminal voltage) to be measured at the breaker, see FIG. 8)

Ontology measured value key: mRID for measured value

Relational DB measurement value key: Identifier for real-time measurement value (index)

The CIM object management unit 10 may store and store the mRID of the measurement-related facility to the facility type, and store the ontology measurement value key by mapping it to the mRID of the hierarchy-related facility, and store the relational DB measurement value key by mapping it to the ontology measurement value key. Can.

The CIM object management unit 10 is based on the mapping information of the facility type, the mRID of the measurement-related facility, the ontology measurement value key, and the relational DB measurement value key, the static ontology DB 20, the real-time ontology DB 30, and the relational DB 40 ) Information can be inquired, and the retrieved information can be provided to an HMI (Human Maching Interface) or an external system by merging.

Referring to FIG. 8, when the CIM object management unit 10 receives CIM-XML data for facility information, it may be determined whether an mRID for a facility on the CIM-XML data is assigned. At this time, if it is determined that the mRID is CIM-XML for a facility to which no mRID is assigned, after the CIM object management unit 10 assigns and registers the mRID for the facility, the mRID for the facility is recorded on the received CIM-XML, CIM-XML itself for mRID-recorded equipment information can be stored (CIM-XML data insert) in the Stacktack ontology DB 20. On the other hand, if it is determined that the mRID is CIM-XML for a facility to which the mRID is assigned, CIM-XML for the facility information is stored in the static ontology DB 20 (CIM-XML data update, at this time, CIM-for the existing facility) XML data is deleted). As seen in FIG. 7, the facility information may include information about the facility type and measurement-related facilities. The CIM object management unit 10 storing CIM-XML for facility information in the static ontology DB 20 in the same manner as described above is based on the facility type (*D, see FIG. 7) and facility type recorded on the CIM-XML. The mapped measurement-related facility mRID (*C, see FIG. 7) may be stored in the mapping information storage 50. 8 illustrates that the equipment type is a breaker, and the measurement-related equipment is a secondary terminal voltage as measurement information to be measured at a circuit breaker, a primary terminal for a circuit breaker connection, a secondary terminal for a circuit breaker, and a circuit breaker.

FIG. 9 illustrates a process of storing measured values for registered equipment information according to the example of FIG. 8. Referring to FIG. 9, when the CIM object management unit 10 receives CIM-XML data for the measured value (step 1), the CIM object management unit 20 receives the facility information associated with the measured value from the static ontology DB 20. You can search (step2).

Then, the CIM object management unit 10 stores the CIM-XML data source itself for the received measurement value in the real-time ontology DB 30 (insert (new storage), update (updates existing information with current information)) (step3), store the measured value on the CIM-XML data for the measured value in the relational DB 40 (insert, store the real-time measured value with Histrocal with time information) (step4) and insert it from the relational DB 40 The index for the measured value can be received (Step 5). At this time, the CIM object management unit 10 generates and registers a new mRID for the measured value when the mRID for the received measurement value is not assigned, and the new generated mRID for the received measurement value for CIM-XML data The original CIM-XML data recorded in the original and the mRID for the measured value can be stored in the real-time ontology DB 30.

Then, the CIM object management unit 10 maps the index (relational DB measurement value key, *B) received from the relational DB 40 to the ontology measurement value key (*A, measurement information mRID) and stores it in the mapping information store 50. Can be done (step 6). At this time, when a new mRID for measurement information is issued, the new mRID may be mapped to a facility type (*D) as a measurement-related facility mRID and stored in the mapping information storage 50.

Referring to FIG. 10, when the facility information and measurement values are managed in the static ontology DB 20, the real-time ontology DB 30, and the relational DB 40 as described above, the measurement values for the external system or the internal system If requested, the CIM-XML for the relevant measurement value related facility information is retrieved from the static ontology DB 20, and the CIM-XML for the corresponding measured value is retrieved from the real-time ontology DB 30, and the retrieved facility information is retrieved. By merging CIM-XML and measurement value CIM-XML, the entire CIM-XML data can be provided to an external system or an internal system.

Referring to FIG. 11, when a request for measurement value information of a facility type (eg, breaker, D*) is made, the CIM object management unit 10 uses the mapping information of the mapping information storage 50 Measurement-related facility mRID (*C) related to type (for example, circuit breaker), ontology measurement value key (*A) related to equipment type (for example, circuit breaker), relational relationship related to equipment type (for example, circuit breaker) All DB measurement value keys (*B) can be obtained from the mapping information storage 50 (step 1).

Then, the CIM object management unit 10 uses measurement-related facilities mRID(*C) to measure-related facilities (for example, circuit breaker, circuit breaker connection primary/secondary terminal, secondary terminal voltage) in the static ontology DB20. Search CIM-XML for and search CIM-XML for measurement values corresponding to measurement-related facility information in real-time ontology DB 30 using ontology measurement value key (*A), and relational DB measurement value key (* B) can be used to retrieve all of the historical data related to the ontology measurement value key (*A) in the relational DB 40 (step 2-1, 2-2, 2-3).

Then, the CIM object management unit 10 may merge the retrieved data and provide it to the system that requested the data in CIM-XML format.

The present invention can reduce the search to be performed in four steps as shown in FIG. 11 by a direct access method for each step so that data can be searched. The DB that stores the data retrieved in each step is built in the form of juxtaposing the static ontology DB (20), real-time ontology DB (30), and relational DB (40), and the static ontology DB (20), real-time ontology DB ( 30), by providing a mapping information store (50) responsible for managing mapping information between data on the relational DB (40), it is easy to manage, exchange, and query UML model-based data having complex relationships using mapping information. Can.

10: CIM object management
20: Static ontology DB
30: Real-time ontology DB
40: Relational DB
50: mapping information store

Claims (1)

Static ontology DB that stores original CIM-XML for measurement-related equipment;
A real-time ontology DB that stores original CIM-XML for measured values;
A relational DB that stores real-time measurement values;
A mapping information store that maps and stores facility type, measurement-related facility mRID, ontology measurement value key, and relational DB measurement value key; And
Power system ontology data management system including a CIM object management unit managing the static ontology DB, real-time ontology DB, and relational DB based on mapping information of the facility type, measurement-related facility mRID, ontology measurement value key, and relational DB measurement value key .

Images