WO2019190035A1

WO2019190035A1 - Data linkage system

Info

Publication number: WO2019190035A1
Application number: PCT/KR2019/000612
Authority: WO
Inventors: 이광엄
Original assignee: 엘에스산전 주식회사
Priority date: 2018-03-26
Filing date: 2019-01-15
Publication date: 2019-10-03
Also published as: KR102131669B1; KR20190112544A

Abstract

The present specification relates to a controller data linkage system. A data linkage system according to one embodiment of the present specification comprises: a main editing module for generating a data linkage project; a sub-editing module for converting SCADA system information on a SCADA system into a common application programming interface (API) through API wrapping, and delivering the common API to the main editing module; a main runtime module for performing a server function for data linkage between the SCADA system and a client; and a sub-runtime module for delivering a tag value and state information of the SCADA system to the main runtime module through a shared memory.

Description

Data linkage system

This specification relates to a data linkage system.

A remote monitoring or supervisory control and data acquisition (SCADA) system uses analog or digital signals on a communication path to collect, receive, record, and record status information data from a remote device to a remote terminal unit. The central control system monitors the remote device by displaying it.

In general, SCADA systems are used to centrally monitor and control various types of remote facilities such as power generation, transmission and distribution facilities, petrochemical plants, steel processing facilities, and factory automation facilities.

In addition, the SCADA system receives a function alarm function of a surveillance system that performs a predetermined operation according to an alarm condition of a remote device, a monitoring control function of selectively operating a remote external device manually and automatically, and receives status information of the remote device. Perform the display function of the monitoring system to display / record.

1 is a diagram illustrating a configuration of a data linkage system of a client and a SCADA system using a conventional standard protocol.

Referring to FIG. 1, in a conventional SCADA system and a client data linkage system, the server application 10 performs data linkage between the SCADA system 12 and the plurality of clients 14 through each standard protocol 16. do.

A typical SCADA system receives and records an element having a unique identification value (ID) in a system indicating a monitoring / control object, that is, a value collected from a tag or a point. For example, when there is any device A to be monitored / controlled by the SCADA system, the output current, output voltage, temperature, etc. of the device A become tags or points of the device A, The system collects the actual output current value, output voltage value and temperature value of the device A.

At this time, each tag or point is assigned an address according to the address scheme of the standard protocol for communication between the SCADA system and the client. Here, the address means an identifier for identifying a tag or a point assigned to each client or client by the system when the communication between the system and the client is performed.

A server application that performs data association between the Skada system and the client using a standard protocol generally includes an editor 101 and a runtime 102.

The user may set mapping information and other necessary information corresponding to the addresses of tags and protocols provided from the SCADA system through the UI (User Interface) of the editor 101.

Meanwhile, the runtime 102 performs a server function for data linkage by using configuration information generated through the editor 101. Such a server function may be performed based on a comparison table of tags and protocol addresses of the SCADA system included in the configuration information.

2 is a diagram illustrating a configuration of a data linkage system of a client and a SCADA system using a conventional standard protocol.

Referring to FIG. 2, when data linkage is made in a conventional SCADA system, each

data linkage system

21 and 22 is configured to support a standard protocol used by each SCADA system A or B. Each system (A, B) uses a separate application to support the protocol.

For example, the data linkage system 21 for linking A-Skada system and the client's data uses an editor and runtime dedicated to the A-Skada system, and the data linkage system for linking the B-Skada system with the client's data. Reference numeral 22 uses a B-Skada system-specific editor and runtime that is distinct from the A-Skada system-specific editor and runtime.

In other words, due to the differences in each protocol, a dedicated editor and runtime must be created separately for each SCADA system. Even if each SCADA system uses the same protocol, the APIs are different for each SCADA system, so an editor and runtime specific to each SCADA system must be produced.

Eventually, according to the prior art, as the number of SCADA systems increases, the number of dedicated editors and runtimes required for data linkage also increases. Accordingly, there is a problem in that the development scope, development period, and development cost of the application program increase, and system operation efficiency decreases.

The present specification uses a dual editor and runtime to link the data of the Skada system with the client, thereby providing a data linkage system that can reduce the scope of application development, development period and development cost, and improve system operation efficiency. For the purpose of

The objects of the present specification are not limited to the above-mentioned objects, and other objects and advantages of the present specification which are not mentioned above may be understood by the following description, and more clearly understood by the embodiments of the present specification. In addition, it will be readily appreciated that the objects and advantages of the present disclosure may be realized by the means and combinations thereof indicated in the claims.

The data linkage system according to an aspect of the present specification converts the skada system information for the main editing module and the skada system to generate a data linkage project into a common application programming interface (API) through API wrapping. A sub-editing module for transmitting to the main editing module, a main runtime module performing a server function for data linkage between the SCADA system and a client; And a sub runtime module for transmitting tag values and state information of the SCADA system to the main runtime module through a shared memory.

In one embodiment of the present specification, the scarda system information may include information about a tag list.

In addition, in an embodiment of the present disclosure, the main editing module receives skada system information for each skada system from the sub-editing module, and uses the tag list and the protocol address included in the skada system information. You can create a data lineage project.

In addition, in one embodiment of the present specification, the main runtime module and the sub runtime module may perform inter-process communication through the shared memory 39 having a preset memory structure.

In addition, in one embodiment of the present specification, the main runtime module may perform a server function by updating a protocol address based on tag and state information stored in the shared memory 39.

In addition, in one embodiment of the present specification, the main editing module is a project file including information on the data linkage project, a mapping file including mapping information of a tag and a protocol address of a Skada system, and modeling of the data linkage address system. You can create a modeling file that contains information.

In an embodiment of the present disclosure, the main runtime module may perform the server function using the project file, the mapping file, and the modeling file.

In addition, in one embodiment of the present specification, the sub runtime module may map a tag and a protocol address of each SCADA system to each other using the project file, the mapping file, and the modeling file.

In addition, in one embodiment of the present specification, the sub-editing module may be a dynamic library.

In addition, in one embodiment of the present specification, the data linkage project means a unit of work of data linkage work between the SCADA system and the client.

According to the present specification, by linking the data of the client and the Skada system using the dual editor and the runtime, it is possible to reduce the development scope, development period and development cost of the application and improve the system operation efficiency.

3 is a diagram illustrating a configuration of a data linkage system according to an exemplary embodiment of the present specification.

4 is a diagram illustrating an initial screen of a main editing module according to an embodiment of the present specification.

5 is a diagram illustrating a data linkage project generation screen of the main editing module according to an embodiment of the present specification.

6 is a diagram illustrating a data source list screen of the main editing module according to an embodiment of the present specification.

7 is a diagram illustrating a sub UI setting screen of the main editing module according to an embodiment of the present specification.

8 is a diagram illustrating a tag list screen of a main editing module according to an embodiment of the present specification.

9 is a diagram illustrating a mapping information screen of a main editing module according to an embodiment of the present specification.

10 is a diagram illustrating a format of a file generated by a main editing module according to an embodiment of the present specification.

The above objects, features, and advantages will be described in detail with reference to the accompanying drawings, and accordingly, those skilled in the art to which the present disclosure belongs may easily implement the technical idea of the present disclosure. In describing the present specification, when it is determined that the detailed description of the known technology related to the present specification may unnecessarily obscure the subject matter of the present specification, the detailed description will be omitted. Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals are used to indicate the same or similar components.

For reference, the module of the present specification refers to one software element that separates the functions of the program into independent units or one hardware element that is designed to be installed, replaced, and used independently.

That is, in the present specification, the module means one component that is independent of other components of the entire system and system, and is not limited to any one of a software component or a hardware component.

In addition, in the present specification, 'data linkage' means processing, converting, editing, and generating data so that various data collected by the SCADA system can be recognized by the client device. In the present specification, the 'data linkage project' refers to a unit of such data linkage work, and a file corresponding to a specific data linkage project is referred to as a 'project file'. The project file contains all the information about the corresponding data linking project.

Referring to FIG. 3, the data linkage system according to an exemplary embodiment of the present specification includes a main editing module 31, a sub editing module 32, a main runtime module 33, and a sub runtime module 34. For reference, the main editing module 31, the sub editing module 32, the main runtime module 33, and the sub runtime module 34 illustrated in FIG. 3 may be embedded in the SCADA system 35 in software form. Each may be implemented in the form of a separate module or server.

The main editing module 31 creates a data linkage project.

In the present specification, the data linkage project includes identification information of the Skada system 35 used as a data source, and information on a correspondence relationship between the tag list 351 which is a list of tags of the Skada system 35 and the protocol address. .

According to one embodiment of the present specification, the main editing module 31 receives the scarda system 35 information for each scarda system 35 from the sub-editing module 32, and the scarda system 35 information. A data linkage project is created using the tag list 351 included in the protocol address and the protocol address. The scarda system 35 information includes information regarding a tag list.

That is, the main editing module 31 receives the identification information and the tag list information of the skada system 35 from the skada system 35 that is the data ties to generate the data linking project, and the user UI 311. Mapping information and other necessary information corresponding to the tag and protocol address of the Skada system 35, which is a data linkage object, may be generated based on the command input through the data.

According to one embodiment of the present specification, the main editing module 31 may include a project file including information on a data linkage project, a mapping file including a mapping information of a tag and a protocol address of the SCADA system 35, and a protocol. A modeling file including modeling information of an address system is generated (38).

The main editing module 31 may generate and manage a data linking project matching the mapping file and the modeling file as a project file.

Such a project file, a mapping file, and a modeling file are used for the operation of the main runtime module 33 and the sub runtime module 34 to be described later.

The sub-editing module 32 transmits the skadar system 35 information on the skadar system 35 to the main editing module 31.

According to the exemplary embodiment of the present specification, the main editing module 31 and the sub editing module 32 use a common application programming interface (API), and the sub editing module 32 is main through API wrapping. Delivers the Scarda system 35 information to the editing module 31. Here, API wrapping refers to APIs used by the sub-editing module 32 and data related to the APIs and APIs used by the sub-editing module 32 so that data related to the APIs can be accessed by the main editing module 31. The operation of adding specific data or code.

In this case, the sub-editing module 32 may be formed of a dynamic linking library (DLL) to reflect the characteristics of each SCADA system 35.

An API is an interface that allows you to control the functionality provided by an operating system or programming language for use in an application, and includes subfunctions and protocols for creating an application.

Thus, the main editing module 31 and the sub editing module 32 can use the same subfunctions and protocols. In addition, the sub-editing module 32 may process the information of the external library format to correspond to backward compatibility through API wrapping and deliver it to the main editing module 31.

As a result, the sub-editing module 32 transmits the information of the skadar system 35 of each skadar system 35 in charge to the main editing module 31. In addition, the main editing module 31 may generate a data linking project based on the information of the SCADA system 35 received from the sub editing module 32.

As such, the data linkage system of the present specification performs a function associated with the characteristics of each scarda system 35 through the sub-editing module 32, and a common function of the entire skida system 35 is the main edit module 31. Do it through. Accordingly, the system operation efficiency is increased and the development scope of the application program is reduced.

The main runtime module 33 performs a server function for data linkage between the SCADA system 35 and the client 36 via the protocol 37.

According to one embodiment of the present specification, the main runtime module 33 updates a protocol address based on a tag and state information stored in the shared memory 39 to perform a server function through each protocol 37.

In order to update such a protocol address, the main runtime module 33 may include a separate protocol address storage space 331 for storing and managing each protocol address.

The sub runtime module 34 transmits the tag value and state information of the scarda system 35 to the main runtime module 33 through the shared memory 39.

According to one embodiment of the present specification, the main runtime module 33 and the sub runtime module 34 perform inter-process communication through the shared memory 39 having a preset memory structure.

In this specification, the shared memory 39 is a memory that can be accessed by several applications at the same time, and means a memory that can be used when sharing or transferring data between applications.

Therefore, since the inter-process communication method through the shared memory 39 shares the memory itself unlike other inter-process communication methods, it is possible to improve the data processing speed by preventing the occurrence of unnecessary overhead such as data copying. There is this.

According to one embodiment of the present specification, the main runtime module 33 performs a server function using a project file, a mapping file, and a modeling file generated by the main editing module 31.

The server function of the main runtime module 33 may be performed through setting information received from the main editing module 31.

As described above, the main editing module 31 includes a project file including information on a data linkage project, a mapping file including mapping information of tags and protocol addresses of the Skada system 35 and a modeling of the data linkage address scheme. You can create a modeling file that contains information.

That is, the main runtime module 33 uses the project file, the mapping file, and the modeling file generated by the main editing module 31, and the scarda system 35 and the client 36 corresponding to the data linkage project through the standard protocol. Perform data linkage between them.

On the other hand, the sub runtime module 34 uses the project file, the mapping file, and the modeling file generated by the main editing module 31 to map the tag and protocol address of each SCADA system 35 to each other.

That is, the sub runtime module 34 identifies the skid system 35 to be used as a data source based on the project file generated by the main editing module 31, and maps information of the tag and protocol address included in the mapping file, For example, a tag and a protocol comparison table 341 and the like are used to map tags and protocol addresses of each SCADA system 35 to each other.

The sub runtime module 34 checks each tag value and protocol address corresponding to each tag of the SCADA system 35 used as a data source, and then displays each tag value and the SCADA system 35 in the shared memory 39. Status information and the like are stored in the shared memory 39. The main runtime module 33 performs data linkage with the client 36 through each protocol 37 using the information stored in the shared memory 39.

As a result, mapping of the protocol address corresponding to each tag for each SCADA system 35 is performed in the sub runtime module 34, and data linkage with the client 36 is performed in the main runtime module 33.

As such, the data linkage system of the present disclosure may use the dual editor and the runtime to link the data of the multi-skada system 35 and the client 36 to prevent redundant development of an application program.

That is, the data linkage system of the present disclosure can reduce the development period and development cost of the data linkage system, and can also improve the system operation efficiency.

Hereinafter, the functions of the main editing module according to the exemplary embodiment of the present specification will be described with reference to FIGS. 4 to 10.

4 is a diagram illustrating an initial screen of a main editing module according to an embodiment of the present specification, and FIG. 5 is a diagram illustrating a data linkage project generation screen of a main editing module according to an embodiment of the present specification.

4 and 5, the main editing module according to an embodiment of the present specification may set a name and a storage path of a data linking project and set a path of a mapping file and a modeling file corresponding to each other.

As described above, the main editing module may store and manage information about the data linking project as a project file, and the project file may be stored in a storage path of the data linking project.

The main editing module can manage the list of scarda systems to be used as data sources in multiple scarda systems.

In other words, the main editing module can add, modify, or delete a skadar system to be used as a data source in multiple skadar systems.

Referring to FIG. 6, the main editing module manages a list of scarda systems including an A scarda system and a B scarda system to be used as data sources. At this time, each SCADA system corresponds to a sub-editing module composed of a dynamic library (DLL) to reflect the characteristics of each SCADA system.

The main editing module can access and retrieve information from a specific SCADA system to use as a data source.

Referring to FIG. 7, the main editing module may display data source information, that is, an IP address of the A SCADA system and an assigned project name, through a sub UI setting screen of the A SCADA system to be used as a data source.

The user may access the A SCADA system by operating a connection button included in the sub UI setting screen of the main editing module.

The main editing module can read the tag list of each SCADA system to be used as a data source after setting up the data source.

FIG. 8 shows a tag list listing tags of an A Scada system used as a data source.

Each tag included in the tag list includes information on a tag name, tag type, and a communication channel of the tag.

The main editing module can select a tag to be used for data linkage among each tag included in the tag list during data linkage project creation.

Referring to FIG. 9, the main editing module according to an embodiment of the present specification may manage a list of SCADA systems (eg, SCADA_A, SCADA_B) to be used as data sources, and may be used for data linkage of each SCADA system. It is possible to manage the Tag Name of the Protocol (Item Address) and the tag of each SCADA system.

The main editing module contains information about the data linkage project, the project file with the PJT extension, the mapping information of the tag and protocol address of the SCADA system, the mapping file with the extension of the XML, and the modeling of the data linkage address scheme. You can create modeling files that contain information and have an XML extension.

As described with reference to FIG. 5, the main editing module according to an embodiment of the present specification sets a name and a storage path of a data linkage project, and sets a path of a mapping file and a modeling file corresponding to each other, and establishes a data linkage project. Can be generated.

Such a data linkage project may be managed as a project file, and the generated project file may be used to perform a mapping function of a sub runtime module and a server function of a main runtime module.

The above-described configuration and functions may be variously substituted, modified, and changed without departing from the technical spirit of the present specification by those skilled in the art to which the present disclosure belongs, the above-described embodiments and the accompanying drawings. It is not limited by.

Claims

A main editing module for generating a data linking project;

A sub-editing module for converting skada system information on a skada system into a common application programming interface (API) through API wrapping and transferring the skada system information to the main editing module;

A main runtime module performing a server function for data linkage between the SCADA system and a client; And

A sub runtime module for transmitting tag values and status information of the SCADA system to the main runtime module through a shared memory;

Data Lineage System.
The method of claim 1,

The SCADA system information is

Contains information about the tag list

Data linkage system
The method of claim 2,

The main editing module

Receive Skada system information for each Skada system from the sub-editing module, and generate the data linkage project using a tag list and a protocol address included in the Skada system information.

Data Lineage System.
The method of claim 1,

The main runtime module and the sub runtime module perform inter-process communication through a shared memory having a preset memory structure.

Data linkage system
The method of claim 1,

The main runtime module

Performing a server function by updating a protocol address based on tag and state information stored in the shared memory

Data Lineage System.
The method of claim 1,

The main editing module

A project file including information about the data linked project;

A mapping file including mapping information of tags and protocol addresses of the SCADA system; And

To generate a modeling file that contains modeling information for the data-driven addressing scheme.

Data Lineage System.
The method of claim 6,

The main runtime module

Performing the server function using the project file, the mapping file, and the modeling file

Data Lineage System.
The method of claim 6,

The sub runtime module

By using the project file, the mapping file and the modeling file to map tags and protocol addresses of each SCADA system to each other.

Data Lineage System.
The method of claim 1,

The sub editing module

Made up of dynamic libraries

Data Lineage System.
The method of claim 1,

The data link project

Means a unit of work of data linkage work between the SCADA system and the client

Data Lineage System.