KR20230136043A - Method, system and non-transitory computer-readable recording medium for managing facility data - Google Patents

Abstract

According to one aspect of the present invention, there is provided a method for managing equipment data, comprising: obtaining a data set associated with equipment data, and corresponding to the data set being comprised of a plurality, at least some of the plurality of data sets. A method is provided including the step of dynamically joining based on the equipment data.

Description

Method, system and non-transitory computer-readable recording medium for managing facility data {METHOD, SYSTEM AND NON-TRANSITORY COMPUTER-READABLE RECORDING MEDIUM FOR MANAGING FACILITY DATA}

The present invention relates to a method, system, and non-transitory computer-readable recording medium for managing equipment data.

In the past, the software architecture required to collect data from numerous facilities in industrial sites such as manufacturing and logistics and perform control based on it was generally structured in a monolithic form.

However, this monolithic architecture had a significantly slow development speed, poor scalability, and could not guarantee stability, so there were fatal limitations in using it as an architecture for collecting and controlling facility data.

In addition, this monolithic architecture is also used to construct an interface (or software) to implement business processes in industrial sites such as manufacturing and logistics, and the interface constructed in this way can evolve organically according to changes in business needs. There was a limitation in that complicated code had to be managed at the user level to make difficult and small changes.

The purpose of the present invention is to solve all the problems of the prior art described above.

Another purpose of the present invention is to configure a software architecture for collecting and controlling equipment data in the form of a microservice within a Kubernetes cluster.

Another purpose of the present invention is to enable an interface (or software) for implementing a business process in an industrial field to be implemented in a no-code environment.

A representative configuration of the present invention to achieve the above object is as follows.

According to one aspect of the present invention, there is provided a method for managing equipment data, comprising: obtaining a data set associated with equipment data, and corresponding to the data set being comprised of a plurality, at least some of the plurality of data sets. A method is provided including the step of dynamically joining based on the equipment data.

According to another aspect of the present invention, there is provided a system for managing equipment data, comprising: an acquisition unit for acquiring a data set associated with equipment data; and, corresponding to the plurality of data sets, at least one of the plurality of data sets. A system including a connection management unit that allows some to be dynamically joined based on the equipment data is provided.

In addition, another method for implementing the present invention, another system, and a non-transitory computer-readable recording medium for recording a computer program for executing the method are further provided.

According to the present invention, a software architecture for collecting and controlling equipment data can be configured in the form of a microservice within a Kubernetes cluster.

Additionally, according to the present invention, an interface (or software) for implementing a business process in an industrial field can be implemented in a no-code environment.

1 is a diagram showing a schematic configuration of an entire system for managing equipment data according to an embodiment of the present invention.
Figure 2 is a diagram showing in detail the internal configuration of a management system according to an embodiment of the present invention.
Figure 3 is a diagram illustrating a first embodiment for managing equipment data according to an embodiment of the present invention.
Figure 4 is a diagram illustrating a second embodiment for managing equipment data according to an embodiment of the present invention.

The detailed description of the present invention described below refers to the accompanying drawings, which show by way of example specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different from one another but are not necessarily mutually exclusive. For example, specific shapes, structures and characteristics described herein may be implemented with changes from one embodiment to another without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description described below is not to be taken in a limiting sense, and the scope of the present invention should be taken to encompass the scope claimed by the claims and all equivalents thereof. Like reference numbers in the drawings indicate identical or similar elements throughout various aspects.

Equipment as used in this specification may be a general term for machines, devices, etc. used in industrial sites such as manufacturing and logistics.

Additionally, equipment data as used herein may be a general term for various types of data related to equipment or its operation. For example, facility data may include data on facility production, operating rates, failures, etc.

Additionally, the facility controller as used herein may refer to a control device that is linked to each facility to control the facility. For example, the equipment controller may include a Programmable Logic Controller (PLC).

Hereinafter, several preferred embodiments of the present invention will be described in detail with reference to the attached drawings in order to enable those skilled in the art to easily practice the present invention.

Configuration of the entire system

1 is a diagram showing a schematic configuration of an entire system for managing equipment data according to an embodiment of the present invention.

As shown in FIG. 1, the entire system according to an embodiment of the present invention may include a communication network 100, a management system 200, and a device 300.

First, the communication network 100 according to an embodiment of the present invention can be configured regardless of communication mode, such as wired communication or wireless communication, and can be used as a local area network (LAN) or a metropolitan area network (MAN). ), and a wide area network (WAN). Preferably, the communication network 100 referred to in this specification may be the known Internet or World Wide Web (WWW). However, the communication network 100 is not necessarily limited thereto and may include at least a portion of a known wired or wireless data communication network, a known telephone network, or a known wired or wireless television communication network.

For example, the communication network 100 is a wireless data communication network, including WiFi communication, WiFi-Direct communication, Long Term Evolution (LTE) communication, 5G communication, and Bluetooth communication (Bluetooth Low Energy (BLE). It may implement, at least in part, conventional communication methods such as (including Bluetooth Low Energy) communication, infrared communication, ultrasonic communication, etc. For another example, the communication network 100 is an optical communication network and may implement at least a portion of a conventional communication method such as LiFi (Light Fidelity).

Next, the management system 200 according to an embodiment of the present invention may perform communication with a device 300, which will be described later, through the communication network 100. In addition, the management system 200 according to an embodiment of the present invention links the equipment controller to the gateway using at least one communication method and uses MQTT (Message Queuing Telemetry Transport) containerized within a Kubernetes cluster. By using a broker, the function of relaying data communication between a controller of a facility linked to a gateway and at least one module for managing the facility can be performed. In addition, the management system 200 according to an embodiment of the present invention acquires a data set associated with equipment data, and in response to the fact that the acquired data set consists of a plurality of data sets, at least some of the plurality of data sets are It can perform a function to dynamically join based on equipment data. Meanwhile, this management system 200 may be a digital device equipped with a memory means and a microprocessor equipped with computing power. For example, it may be a server system operated on the communication network 100.

The configuration and functions of the management system 200 according to an embodiment of the present invention will be discussed in detail through the detailed description below.

Next, the device 300 according to an embodiment of the present invention is a digital device that includes a function to communicate after accessing the management system 200, and may be used as a smartphone, tablet, smart watch, smart band, or smart glass. Any digital device equipped with a memory means and equipped with a microprocessor, such as a desktop computer, a laptop computer, a workstation, a PDA, a web pad, a mobile phone, etc., and has computing power can be adopted as the device 300 according to the present invention. there is.

Additionally, according to one embodiment of the present invention, the device 300 may further include an application program for performing functions according to the present invention. These applications may exist in the form of program modules within the device 300. The nature of this program module includes the linking unit 210, relay unit 220, acquisition unit 230, connection management unit 240, communication unit 250, and control unit 260 of the management system 200, which will be described later. It may be similar overall. Here, at least part of the application may be replaced with a hardware device or firmware device that can perform substantially the same or equivalent functions as necessary.

Configuration of the management system

Below, we will look at the internal configuration of the management system 200 and the function of each component, which performs important functions for implementing the present invention.

FIG. 2 is a diagram illustrating in detail the internal configuration of the management system 200 according to an embodiment of the present invention.

As shown in Figure 2, the management system 200 according to an embodiment of the present invention includes an interlocking unit 210, a relay unit 220, an acquisition unit 230, a connection management unit 240, and a communication unit 250. ) and a control unit 260. According to an embodiment of the present invention, the linking unit 210, relay unit 220, acquisition unit 230, connection management unit 240, communication unit 250, and control unit 260 of the management system 200 are the At least some of them may be program modules that communicate with an external system (not shown). These program modules may be included in the management system 200 in the form of an operating system, application program module, or other program module, and may be physically stored in various known storage devices. Additionally, these program modules may be stored in a remote storage device capable of communicating with the management system 200. Meanwhile, such program modules include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc. that perform specific tasks or execute specific abstract data types according to the present invention.

Meanwhile, although the management system 200 has been described as above, this description is illustrative, and at least some of the components or functions of the management system 200 are stored in the device 300 or the server (not shown) as needed. It is obvious to those skilled in the art that it may be realized in or included in an external system (not shown).

First, the interlocking unit 210 according to an embodiment of the present invention can perform a function of linking a facility controller to a gateway using at least one communication method.

Specifically, the linkage unit 210 according to an embodiment of the present invention can link a facility controller to a gateway using a wireless communication method. For example, a wireless transmitter may be installed in a facility's controller, and a wireless receiver may be installed in a gateway (or the gateway itself may operate as a wireless receiver). Alternatively, a wireless receiver may be installed in the facility's controller, and a wireless transmitter may be installed in the gateway (or the gateway itself may operate as a wireless transmitter). The interlocking unit 210 according to an embodiment of the present invention is capable of forming a wireless communication channel (such a wireless communication channel may be based on WIFI or LTE) between the wireless transmitter and the wireless receiver, Through this, the equipment controller can be linked to the gateway.

Additionally, the interlocking unit 210 according to an embodiment of the present invention may link a facility controller to a gateway using a wired communication method. For example, the linking unit 210 according to an embodiment of the present invention can link a facility controller to a gateway using methods such as Ethernet, RS-232, and RS-485.

The linking unit 210 according to an embodiment of the present invention can use a driver library provided (or built-in) in the gateway when linking the equipment controller to the gateway. According to an embodiment of the present invention, this driver library may collectively include a plurality of drivers that enable interworking with various types of controllers. For example, these driver libraries include LSIS XGT-Ethernet, LSIS Drivers such as Mitsubishi MC Serial may be included collectively. However, according to one embodiment of the present invention, the types of drivers included in the driver library are not necessarily limited to the above example, and may be changed in various ways within the scope of achieving the purpose of the present invention.

The present invention enables external communication even with existing equipment (or the equipment's controller) that is not equipped with an external communication function by linking the equipment's controller to the gateway using the above driver library along with the linkage method described above. there is.

Meanwhile, the interlocking unit 210 according to an embodiment of the present invention can enable a gateway to perform data communication with a facility controller using a promise pattern. Specifically, the interlocking unit 210 according to an embodiment of the present invention serves as a pattern for asynchronous processing when the gateway receives equipment data from the equipment controller or transmits data for managing the equipment to the equipment controller. You can use JavaScript's promise pattern. According to one embodiment of the present invention, the promise pattern is excellent at concurrency processing and can compensate for the shortcomings of other patterns for asynchronous processing of JavaScript, such as callback patterns. As a result, the present invention can improve bottlenecks that may occur during data communication between a facility's controller and a gateway, and further minimize delay time.

Next, the relay unit 220 according to an embodiment of the present invention uses a containerized MQTT (Message Queuing Telemetry Transport) broker within a Kubernetes cluster to control the controller and equipment of the equipment linked to the gateway. It may perform a function of relaying data communication between at least one module for managing.

Specifically, the relay unit 220 according to an embodiment of the present invention uses the MQTT protocol (the MQTT protocol is a messaging protocol based on topic publication and subscription, and corresponds to a known protocol, so detailed description will be omitted). An MQTT broker (e.g., HiveMQ, etc.) running in can be containerized within a Kubernetes cluster. In addition, the relay unit 220 according to an embodiment of the present invention, like an MQTT broker, includes at least one module for managing equipment (e.g., controlling and monitoring equipment based on equipment data). can be containerized within a Kubernetes cluster.

As a first embodiment related to this, referring to FIG. 3, the relay unit 220 according to an embodiment of the present invention includes a containerized MQTT broker 403 and at least one module 404, 405, 406, and 407. It can be operated in this cloud environment (B). According to an embodiment of the present invention, this cloud environment (B) may include a public cloud environment and a private cloud environment.

Specifically, the relay unit 220 according to an embodiment of the present invention allows the controller 401 and the gateway 402 to operate in an on-premise environment (A), and the MQTT broker 403 and At least one module (404, 405, 406, and 407) can be operated in a cloud environment (B) rather than an on-premise environment (A).

Here, the relay unit 220 according to an embodiment of the present invention transmits the topic issued by the controller 401 (the topic may include facility data) to the MQTT broker 403 via the gateway 402. It can be transmitted, and the MQTT broker 403 can transmit (or forward) the topic to at least one module (404, 405, 406, and 407) or SCADA (Supervisory Control and Data Acquisition) 408. . In addition, the relay unit 220 according to an embodiment of the present invention provides a topic issued by at least one module 404, 405, 406, and 407 (the topic may include data for managing facilities). It can be transmitted to the MQTT broker 403, and the MQTT broker 403 can transmit the topic to the controller 401 through the gateway 402. In addition, the relay unit 220 according to an embodiment of the present invention allows the topic issued by the SCADA 408 (the topic may include data for managing the facility) to be transmitted to the MQTT broker 403. This can be done, and the MQTT broker 403 can transmit the topic to the controller 401 through the gateway 402. According to the above topic transmission path, the gateway 402 is the only path for transmitting (or delivering) a topic issued by at least one module (404, 405, 406, and 407) or the SCADA (408) to the controller (401). It can operate as . However, it should be noted that the topic transmission path according to an embodiment of the present invention is not necessarily limited to the path described above or shown in FIG. 3, and may be changed in various ways within the scope of achieving the purpose of the present invention. .

Meanwhile, according to an embodiment of the present invention, at least one module 404, 405, 406, and 407 includes a first module 404, a second module 405, a third module 406, and a fourth module ( 407) may be included, and the functions performed by each module are as follows. (1) The first module 404 extracts equipment data from the topic received from the MQTT broker 403 and performs preprocessing on the extracted equipment data, such as normalization and roll up. You can. (2) The second module 405 may perform the function of storing preprocessed equipment data or processed data as described later in storage. Here, the storage where the above data is stored may be distributed storage. (3) The third module 406 can perform the function of processing preprocessed equipment data to suit a predetermined purpose. (4) The fourth module 407 can function as an API and can link with the SCADA 408 to provide data stored in the storage to the SCADA 408. Here, the data provided by the fourth module 407 can be used as metadata to configure the SCADA (408).

As a second embodiment, referring to FIG. 4, the relay unit 220 according to an embodiment of the present invention includes a containerized MQTT broker 503 and at least one module 504, 505, 506, and 507. It can be operated in a premises environment (C).

Specifically, the relay unit 220 according to an embodiment of the present invention has all components including the MQTT broker 503 and at least one module (504, 505, 506, and 507) in the on-premise environment (C). You can make it work. In this case, the gateway 402 in the first embodiment can be replaced by a containerized module within the Kubernetes cluster, that is, a fifth module 502. That is, according to one embodiment of the present invention, the gateway 402 corresponds to the MQTT broker 503 and at least one module 504, 505, 506, and 507 operating in the on-premise environment (C), It may be replaced by the fifth module 502. According to one embodiment of the present invention, the fifth module 502 can perform all functions performed by the gateway 402 in the same manner.

Here, the relay unit 220 according to an embodiment of the present invention transmits the topic issued by the controller 501 (the topic may include facility data) through the fifth module 502 to the MQTT broker 503. ), and the MQTT broker 503 can transmit (or deliver) the topic to at least one module (504, 505, 506, and 507) or SCADA (508). In addition, the relay unit 220 according to an embodiment of the present invention includes topics issued by at least one module 504, 505, 506, and 507 (the topic may include data for managing facilities). It can be transmitted to the MQTT broker 503, and the MQTT broker 503 can transmit the topic to the controller 501 through the fifth module 502. In addition, the relay unit 220 according to an embodiment of the present invention allows the topic issued by the SCADA 508 (the topic may include data for managing the facility) to be transmitted to the MQTT broker 503. This can be done, and the MQTT broker 503 can transmit the topic to the controller 501 through the fifth module 502. According to the above topic transmission path, the fifth module 502 is for transmitting (or delivering) a topic issued by at least one module 504, 505, 506, and 507 or the SCADA 508 to the controller 501. It can operate as a unique path. However, it should be noted that the topic transmission path according to an embodiment of the present invention is not necessarily limited to the path described above or shown in FIG. 4, and may be changed in various ways within the scope of achieving the purpose of the present invention. .

Meanwhile, according to an embodiment of the present invention, at least one module 504, 505, 506, and 507 includes a first module 504, a second module 505, a third module 506, and a fourth module ( 507) may be included (the fifth module 502 is not included in at least one module mentioned here), and the functions performed by each module are as follows. (1) The first module 504 extracts equipment data from the topic received from the MQTT broker 503 and performs preprocessing on the extracted equipment data, such as normalization and roll up. You can. (2) The second module 505 may perform the function of storing preprocessed equipment data or processed data as described later in storage. Here, the storage where the above data is stored may be distributed storage. (3) The third module 506 can perform the function of processing preprocessed equipment data to suit a predetermined purpose. (4) The fourth module 507 can function as an API and can link with the SCADA 508 to provide data stored in the storage to the SCADA 508. Here, the data provided by the fourth module 507 can be used as metadata to configure the SCADA 508.

According to the first and second embodiments described above, the present invention allows a software architecture for managing equipment data in a cloud environment or on-premise environment to be configured in the form of a microservice within a Kubernetes cluster. .

Next, the acquisition unit 230 according to an embodiment of the present invention may perform a function of acquiring a data set associated with facility data.

Specifically, the acquisition unit 230 according to an embodiment of the present invention can acquire the above data set from the management interface. Here, according to an embodiment of the present invention, the management interface is an interface (or software) for implementing business processes in industrial sites and may be an interface implemented based on a spreadsheet. According to one embodiment of the present invention, this management interface may be included in the SCADA (408, 508) in the first or second embodiment described above. According to one embodiment of the present invention, at least one sheet can be created in the management interface as needed, and a data set consisting of a row (low) and a column (column) can be created in each sheet. . According to one embodiment of the present invention, this data set may be associated with equipment data (equipment data may be included in topics issued by the equipment's controller, as described above), such as work schedules at industrial sites, work instructions, quality control, etc. Data on various activities at industrial sites, such as work performance statistics, may be included.

Next, the connection management unit 240 according to an embodiment of the present invention dynamically connects at least some of the plurality of data sets based on equipment data, in response to the fact that the data sets obtained as above are comprised of multiple data sets ( join) function can be performed.

Specifically, the connection management unit 240 according to an embodiment of the present invention connects a plurality of devices based on a field determined with reference to equipment data (equipment data may be included in a topic issued by the equipment controller, as described above). You can link some or all of the data sets, resulting in a linked data set.

According to one embodiment of the present invention, the connected data set created in this way can be synchronized in real time with each data set included in the connected data set, and as the contents of each data set changes, the connected data set is changed. The content can also change dynamically. Additionally, according to one embodiment of the present invention, this connected data set may be created from an existing sheet created in the management interface or may be created from a new sheet separate from the existing sheet. Additionally, according to one embodiment of the present invention, this linked data set can be stored in a database and loaded from the database as needed (loading privileges may be granted only to some users). For example, when a new data set is created in the management interface, the connection data set stored in the database is loaded to determine whether a connection is possible between each data set included in the connection data set and the newly created data set. You can. In addition, according to one embodiment of the present invention, this connected data set can be visualized in various forms (e.g., tables, graphs, etc.) within the management interface, and can be output as it is visualized (i.e., with WYSIWYG). WYSIWYG; What You See Is What You Get)).

Meanwhile, the connection management unit 240 according to an embodiment of the present invention provides field properties for data sets that are not included in the connection data set among the plurality of data sets obtained from the management interface, that is, data sets that are not connected. Connections can be made by redefining the field name, data type, order, etc.

Continuing, the connection manager 240 according to an embodiment of the present invention can enable connections between data sets according to logic implemented in a no-code environment. According to one embodiment of the present invention, as the connection logic is implemented in this no-code environment, there is an advantage that there is no need to manage the code for implementing the connection logic at the user level and the logic is easy to change. According to one embodiment of the present invention, apart from the connection logic, logic to implement other functions executed within the management interface can also be implemented in a no-code environment. For example, the logic for correlation analysis, which will be described later, can also be implemented in a no-code environment.

Meanwhile, the connection management unit 240 according to an embodiment of the present invention establishes a connection relationship between each data set included in the connected data set that is created as a result of a connection between the data sets. Can be represented by at least one graphic element. For example, the connection management unit 240 according to an embodiment of the present invention displays the connection relationship between each data set included in the connection data set using graphics such as arrows (two-way arrows, one-way arrows, etc.), straight lines, dotted lines, etc. It can be expressed as an element.

On the other hand, the connection management unit 240 according to an embodiment of the present invention determines the correlation between each data set included in the connected data set, which is created as a result of a connection between the data sets. It can be analyzed. According to one embodiment of the present invention, the results of this correlation analysis can be stored in a database and loaded from the database as needed (loading privileges may be granted only to some users). In addition, according to one embodiment of the present invention, the results of correlation analysis can be visualized in various forms (e.g., tables, graphs, etc.) within the management interface, and can be output as they are visualized (i.e., WYSIWYG (WYSIWYG; What You See Is What You Get)).

On the other hand, the connection management unit 240 according to an embodiment of the present invention analyzes the correlation between the connected data set created as a result of a connection between data sets and each data set included in the connected data set. At least one of the results can be shared among multiple users. For example, the connection manager 240 according to an embodiment of the present invention may allow the management interface (or SCADA 408, 508 in the first or second embodiment) to be linked with the cloud environment, , At least one of the connection data sets and correlation analysis results stored in the database can be shared among a plurality of users in the corresponding cloud environment.

Next, the communication unit 250 according to an embodiment of the present invention functions to enable data transmission and reception from/to the linking unit 210, relay unit 220, acquisition unit 230, and connection management unit 240. can be performed.

Finally, the control unit 260 according to an embodiment of the present invention controls the flow of data between the linking unit 210, the relay unit 220, the acquisition unit 230, the connection management unit 240, and the communication unit 250. It can perform the function: That is, the control unit 260 according to the present invention controls the data flow from/to the outside of the management system 200 or the data flow between each component of the management system 200, thereby controlling the interlocking unit 210, the relay unit ( 220), the acquisition unit 230, the connection management unit 240, and the communication unit 250 can each be controlled to perform their own functions.

The embodiments according to the present invention described above can be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention, or may be known and usable by those skilled in the computer software field. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magneto-optical media such as floptical disks. medium), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include not only machine language code such as that created by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. A hardware device can be converted into one or more software modules to perform processing according to the invention and vice versa.

In the above, the present invention has been described in terms of specific details, such as specific components, and limited embodiments and drawings, but this is only provided to facilitate a more general understanding of the present invention, and the present invention is not limited to the above embodiments. Anyone with ordinary knowledge in the technical field to which the invention pertains can make various modifications and changes from this description.

Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and the scope of the patent claims described below as well as all scopes equivalent to or equivalently changed from the scope of the claims are within the scope of the spirit of the present invention. It will be said to belong to

100: communication network
200: Management system
210: Linkage part
220: relay unit
230: Acquisition department
240: Connection management unit
250: Department of Communications
260: control unit
300: device

Claims (15)

As a method for managing equipment data,
obtaining a data set associated with facility data, and
In response to the fact that the data sets are comprised of a plurality of data sets, at least some of the plurality of data sets are dynamically joined based on the equipment data.
method. According to paragraph 1,
The equipment data is included in the topic issued by the equipment controller.
method. According to paragraph 1,
The data set is created from an interface implemented based on a spreadsheet.
method. According to paragraph 1,
In the connection step, the connection is made according to logic implemented in a no-code environment.
method. According to paragraph 1,
In the connection step, with respect to the connected data set generated as a result of the connection, the connection relationship between each data set included in the connected data set is represented by at least one graphic element.
method. According to paragraph 1,
In the connection step, analyzing the correlation between each data set included in the connected data set for the connected data set generated as a result of the connection.
method. According to paragraph 1,
In the connection step, the connection data set generated as a result of the connection is shared between a plurality of users.
method. A non-transitory computer-readable recording medium recording a computer program for executing the method according to claim 1. As a system for managing equipment data,
an acquisition unit that acquires a data set associated with equipment data, and
In response to the fact that the data sets are comprised of a plurality of data sets, including a connection management unit that allows at least some of the plurality of data sets to be dynamically joined based on the equipment data.
system. According to clause 9,
The equipment data is included in the topic issued by the equipment controller.
system. According to clause 9,
The data set is created from an interface implemented based on a spreadsheet.
system. According to clause 9,
The connection management unit ensures that the connection is made according to logic implemented in a no-code environment.
system. According to clause 9,
The connection management unit represents, with at least one graphic element, a connection relationship between each data set included in the connected data set generated as a result of the connection.
system. According to clause 9,
The connection management unit analyzes the correlation between each data set included in the connected data set generated as a result of the connection.
system. According to clause 9,
The connection management unit allows the connection data set generated as a result of the connection to be shared between a plurality of users.
system.

Images