JP2024041463A - Engineering device - Google Patents

Abstract

To provide an engineering device capable of estimating a resource usage situation of a device.SOLUTION: In an embodiment of the present invention, an engineering device comprises an input unit that receives input of device information and tag information regarding a control system that is scheduled to be changed. The engineering device further comprises: a calculation unit that calculates a resource usage situation in a device in the control system when the control system is changed based on the device information and tag information, and outputs a calculation result of the resource usage situation.SELECTED DRAWING: Figure 2

Description

Embodiments of the present invention relate to engineering devices.

Cloud control systems using cloud servers are widely used at manufacturing sites and the like. However, when data processing is concentrated, cloud servers and networks are under a high load, causing delays in processing and communication. Manufacturing sites require rapid data processing and real-time control, so edge cloud control systems using edge computing technology have been adopted in recent years.

In edge computing technology, edge devices that accumulate, process, and analyze data are installed near manufacturing sites and the like. The edge device performs some of the processing in the control system and sends only the necessary data to the cloud server. Edge devices can distribute the load on cloud servers and networks, avoiding processing and communication delays.

Furthermore, in an edge cloud control system, for continuous operation of a manufacturing site or the like, the user needs to understand the load status of resources such as arithmetic units, main storage devices, and auxiliary storage devices in each edge device. For example, if the load factor on the arithmetic device is always high or if the capacity of the auxiliary storage device has reached its upper limit, the user may consider updating or adding an edge device.

On the other hand, because the edge cloud control system has a complex system configuration, it is difficult to understand how the operating status of the system changes when updating or expanding edge devices.

For example, when an edge device is updated or expanded, it affects the load status of an upper server, network, etc. In order to smoothly update or expand the edge cloud control system, it is necessary to have a means of understanding the impact of updating or expanding edge devices in advance.

Embodiments of the present invention provide an engineering apparatus capable of estimating resource utilization of a device.

According to one embodiment, the engineering device includes an input unit that receives input of device information and tag information regarding a control system to be changed. The engineering device further calculates the resource usage status of devices in the control system when the control system is changed based on the device information and tag information, and outputs the calculation result of the resource usage status. The calculation unit is provided with a calculation unit that performs the calculation.

1 is a diagram illustrating an example of a system configuration diagram of an edge cloud control system in a first embodiment; FIG. FIG. 2 is a diagram showing an example of a system block diagram of the engineering device 1 in the first embodiment. It is a figure which shows the example of the input screen of the change schedule information 13 in 1st Embodiment. It is a figure which shows the example of the input screen of the tag information to be changed in 1st Embodiment. FIG. 3 is a diagram illustrating an example of system configuration information to be changed in the first embodiment. It is a figure which shows the example after input of the change schedule information 13 in 1st Embodiment. It is a figure showing an example of existing information 14 in a 1st embodiment. FIG. 3 is a diagram illustrating an example of reference device information stored in reference information 15 in the first embodiment. It is a figure which shows the example of the tag information for reference stored in the information for reference 15 in 1st Embodiment. FIG. 3 is a diagram illustrating an example of estimation results of resource usage status in the first embodiment. It is a figure showing an example of a flow chart of estimation in a 1st embodiment. FIG. 2 is a diagram showing a hardware configuration diagram of an engineering device 1 in a second embodiment.

Embodiments of the present invention will be described below with reference to the drawings. In FIGS. 1 to 12, the same components are denoted by the same reference numerals, and redundant explanations will be omitted.

(First embodiment)
FIG. 1 is an example of a system configuration diagram of an edge cloud control system in the first embodiment.

This control system is constructed across a manufacturing site 200 having a plurality of manufacturing lines 100 and a management center 400 that manages the manufacturing site 200. Specifically, this control system includes an engineering device 1, an edge device 2, a controller 3, a global network 40 and a local network 50 shown in FIG. 1, a controlled device described below, and the like.

In FIG. 1, there is a controlled device (not shown) for each manufacturing line 100, and the controlled device is automatically controlled by the controller 3 and the edge device 2. The controller 3 is, for example, a programmable controller (also referred to as PLC (Programmable Logic Controller)). The edge device 2 is, for example, an edge controller. Furthermore, the engineering device 1 is installed in the management center 400 as a cloud server. This engineering device 1 remotely monitors the controller 3 and edge device 2. In this embodiment, the edge device 2 collects statistical data regarding tags necessary for edge computing and transmits it to other edge devices 2. Although this diagram shows a configuration in which the edge device 2 is placed above the controller 3, the controller 3 may be placed above the edge device 2.

The engineering device 1 and the edge device 2 are connected through a global network 40. Furthermore, the edge device 2 and the controller 3 are connected via a local network 50. An example of global network 40 is the Internet, and an example of local network 50 is an intranet. These networks enable communication between the engineering device 1, the edge device 2, and the controller 3. These networks may be wired lines or wireless lines. Further, the local network 50 may be used instead of the global network 40, and the global network 40 may be used instead of the local network 50, and necessary networks are constructed to realize the control system.

FIG. 2 is a system block diagram of the engineering device 1 in the first embodiment.

The engineering device 1 can be realized, for example, by installing a program (engineering tool) for the engineering device 1 on a PC (Personal Computer). In this embodiment, the engineering device 1 has a function of monitoring the controller 3 and the like, as well as a function of estimating the usage status of resources in the edge device 2 in the control system when the control system is changed. Here, changing the edge device 2 includes updating, adding, and deleting the edge device 2. Examples of resources are arithmetic units such as a CPU (Central Processing Unit) of the edge device 2, main storage devices such as RAM (Random Access Memory), and auxiliary storage devices such as HDD (Hard Disc Drive). For example, the functions of the input unit 10, storage unit 11, and calculation unit 12 for estimation are realized by the CPU in the PC executing the program of the engineering device 1.

Furthermore, the storage unit 11 includes an area for storing change schedule information 13, existing information 14, and reference information 15. The storage unit 11 is constructed, for example, on an auxiliary storage device such as an HDD.

Furthermore, an input device 20 and a display device 30 are electrically connected to the engineering device 1 . Examples of the input device 20 are a keyboard and a mouse. An example of the display device 30 is an LCD (Liquid Crystal Display) monitor. Below, details of each functional block of the engineering device 1 will be explained.

The input unit 10 provides a user interface such as an input screen that accepts input of change schedule information 13 and the like. This input screen is displayed on the display device 30, for example, and the user uses the input device 20 to input the change schedule information 13 and the like.

The storage unit 11 includes a database that stores various information. The change schedule information 13 is a database that stores device information, tag information, and system configuration information that are scheduled to be changed. Furthermore, the existing information 14 is a database that stores existing device information, tag information, and system configuration information. Further, the reference information 15 is a database that stores reference device information and tag information. These databases will be explained below using the drawings.

The calculation unit 12 calculates, as an estimate, the usage status of resources in the edge device 2 in the control system when the control system is changed, based on the device information scheduled to be changed and the tag information input by the user. The calculated resource usage status can be output to the display device 30 and presented to the user, for example.

FIG. 3 is an example of an input screen for the change schedule information 13 in the first embodiment.

The engineering device 1 provides a user interface for receiving input of change schedule information 13 from the user. This user interface is provided by the input unit 10. The edge device 2 scheduled to be changed refers to the edge device 2 that is scheduled to be introduced after the change. Here, an example will be described in which the name of the edge device 2 is changed (updated) to "device (a)". Further, in this embodiment, the edge device 2 or the controller 3 controls the controlled device based on a collection of data called a tag. Various processes for controlling one controlled device, such as reading sensor data necessary to control the controlled device and writing values to the controlled device, are associated with one type of tag. In this embodiment, each edge device 2 collects and transmits statistical data regarding a predetermined tag in order to monitor or control a plurality of lower-level controllers 3 in addition to monitoring or controlling a device to be controlled based on the tag. Let me explain by giving an example. The data handled by the edge device 2 is not limited to tags, but may handle data necessary for estimating the usage status of resources.

In the input screen of FIG. 3, the user inputs the edge device 2 to be changed in the row for the device information to be changed. The user registers information on "device (a)" in the "device 1" column. Here, an example is shown in which the user selects "device (a)" from the pull-down menu. The information input here is not limited to the name of the edge device 2. Other identification information such as a number or alphabet can be used to identify the edge device 2 to be changed. Furthermore, input of device information to be changed is not limited to selection from a pull-down menu. The user may directly input the input device information using the input device 20 such as a keyboard.

The user inputs information about the tag handled by "device (a)" in the row of tag information to be changed. Since the edge device 2 to be changed may handle multiple tags, in this example, the tag information to be changed is input on a separate screen. The system configuration information to be changed is automatically updated based on the input device information and tag information to be changed. Details of these will be described later.

FIG. 4 is an example of an input screen for tag information to be changed in the first embodiment.

This example shows an input screen that changes when "detailed input" of the tag information to be changed in FIG. 3 is pressed. On this input screen, the user inputs details regarding the tag processing to be handled for each edge device 2 to be changed. In this example, "device 1", that is, "device (a)" handles "tag (a)" and "tag (b)". The user enters "Processing 1", which is the content related to the processing of "Device (a)" based on "Tag (a)", in the "Tag (a)" field, and enters "Processing 1" in the "Tag (b)" field. , "Processing 2", which is the content related to the processing of "Device (a)" based on "Tag (b)", is input. For example, the user inputs information regarding tag processing, such as the number of tag processings. Further, the tag information to be changed may be any input other than the content of tag processing as long as it is data for calculating resource usage status. In addition to manual input by the user, the input unit 10 may also receive input by a method such as selection from a pull-down menu. Furthermore, the engineering device 1 may accept uploading of a configuration file such as a CSV (Comma Separated Value) file. When the user completes input regarding tag processing and presses the OK button, input to the tag information input section is completed.

When the user inputs the device information and tag information to be changed, the engineering apparatus 1 updates the system configuration information to be changed.

FIG. 5 is an example of system configuration information to be changed in the first embodiment.

FIG. 5 shows an example of a screen that changes when "Confirm details" of the system configuration information scheduled to be changed in FIG. 3 is pressed. In this example, the input unit 10 generates system configuration information to be changed, which is a list of collected data and transmission data, based on the device information and tag information to be changed inputted by the user in FIGS. 3 and 4. do. For example, it is conceivable that the input unit 10 determines data that needs to be collected or transmitted from tag information that is scheduled to be changed, and generates system configuration information that is scheduled to be changed. This allows the user to check the collected data and transmitted data for statistical data in each edge device 2.

FIG. 6 is an example of the change schedule information 13 after input in the first embodiment.

After the input in FIGS. 3 and 4, when the user presses the input confirmation button, the input unit 10 can store the device information, tag information, and system configuration information scheduled to be changed in the database of the scheduled change information 13. . FIG. 6 shows an example in which "device 1" is scheduled to be changed to "device (a)" and "device 2" is scheduled to be changed to "device (b)."

FIG. 7 is an example of the existing information 14 in the first embodiment.

Existing information 14 stores existing device information, tag information, and system configuration information. The existing device information is information on the existing edge device 2 within the control system. Furthermore, the existing tag information and system configuration information are tag information and system configuration information of the existing edge device 2, respectively. FIG. 7 shows an example in which, as existing edge devices 2, "device (b)" is registered in "device 1" and "device (c)" is registered in "device 2." Further, existing tag information and existing system configuration information are omitted because the user interface is the same as that in FIG. 4 or 5. The existing information 14 may be manually registered by the user in the input unit 10 before the estimate is made, or a configuration file such as a CSV (Comma Separated Value) file may be uploaded to the engineering device 1. Furthermore, the engineering device 1 may have a function of automatically collecting the existing information 14 from each edge device 2.

FIG. 8 is an example of reference device information stored in the reference information 15 in the first embodiment.

The reference device information stores information regarding the performance of the arithmetic unit, main storage device, and auxiliary storage device in each edge device 2 in the control system. The reference device information serves as a list regarding the performance of resources in each edge device 2. In this example, "device (a)" is equipped with CPU type A, and the capacities of the memory and HDD are 4 GB and 500 GB, respectively. In addition to the CPU type, the reference device information may include other reference device information such as GPU, depending on the resource for which estimation is required. Furthermore, the device information for reference may be manually registered by the user in the input unit 10 or uploaded to the engineering apparatus 1 by a configuration file such as a CSV (Comma Separated Value) file. The engineering device 1 may have a function of collecting device information from each edge device 2 and the like.

FIG. 9 is an example of reference tag information stored in the reference information 15 in the first embodiment.

The reference tag information stores information regarding the load on the arithmetic unit, main storage device, and auxiliary storage device when the edge device 2 operates based on the tag. The reference tag information serves as a list regarding the load of each tag. This example indicates that the edge device 2 equipped with "CPU type A" can process "60,000" tags (a) handled by the edge device 2 in one day. Furthermore, the value in parentheses represents the number of recommended tags processed. In this case, the "number of recommended tags processed" by CPU type A is "30,000" in one day. Further, the edge device 2 equipped with "CPU type B" is similarly capable of processing "30,000" "tags (a)" in one day. Further, the number of recommended tags processed is "15,000" in one day.

Also, according to the "memory usage status", in this example, for "tag (a)" handled by edge device 2, edge device 2 requires "1 KB" of memory capacity for one tag to operate. represents.

Also, according to the "HDD usage status", in this example, for "tag (a)" handled by the edge device 2, the edge device 2 needs an HDD capacity of "1 MB" for one tag to operate. It represents that.

In addition to the CPU type, the reference tag information may also store the load status of other arithmetic devices such as GPUs, depending on the resources that require estimation. Further, depending on resources other than memory and HDD that need to be estimated, resource load conditions related to other main storage devices and auxiliary storage devices may be stored.

The tag information for reference may be manually registered by the user in the input unit 10 before the estimate is made, or a configuration file such as a CSV (Comma Separated Value) file may be uploaded to the engineering device 1. Furthermore, the engineering apparatus 1 may have a function of automatically collecting reference device information from each edge device 2.

FIG. 10 is an example of the result of estimating the resource usage status in the first embodiment.

In this example, the calculation unit 12 determines the usage status of "CPU load", "memory load", and "HDD load" based on the presence or absence of changes in the device information, tag information, and system configuration information of each edge device 2. Calculate as an estimate. For example, the estimate result is calculated by pressing the "output estimate" button in the change schedule information 13. Further, the calculated result is output to the display device 30 or the like.

In this example, the name of the edge device 2 before and after the change is displayed in the device information item. FIG. 10 shows that "device 1" has been changed from "device (b)" to "device (a)." Along with this, the tag information and system configuration information indicate that they have been changed. Regarding the tag information, the calculation unit 12 can check whether there is any change by comparing the tag information to be changed in the change schedule information 13 and the existing tag information in the existing information 14. Further, regarding the system configuration information, the calculation unit 12 can check whether there is any change by comparing the system configuration information to be changed in the change schedule information 13 with the existing system configuration information in the existing information 14. . Similarly, for "Device 2", FIG. 10 shows that the edge device 2 has been changed from "Device (c)" to "Device (d)", and the tag information and system configuration information have been changed to "Device (d)". "Changes have been made." Further, FIG. 10 shows that "device 3" was not registered before the change, and shows that "device (e)" has been added after the change. Accordingly, FIG. 10 shows that "tag information" and "system configuration information" have become "changed".

Next, the method by which the calculation unit 12 calculates the estimation result will be explained using the changed "device 1" as an example. The calculation unit 12 acquires the information on “device 1” stored in the change schedule information 13. From the information acquired here, it can be seen that the edge device 2 to be changed is "device (a)". The calculation unit 12 reads out the "CPU type", "memory capacity" and "HDD capacity" regarding "device (a)" which is the edge device 2 to be changed from the reference device information. As shown in FIG. 8, the calculation unit 12 calculates that the "CPU type" for "device (a)" is "CPU type A", the "memory capacity" is "4 GB", and the "HDD capacity" is "500 GB". ” is read out.

Further, the calculation unit 12 reads out the "tag information" in the "device (a)" from the change schedule information 13. From the information acquired here, the calculation unit 12 reads that the tags handled by "device (a)" are "tag (a)" and "tag (b)." The calculation unit 12 reads information regarding the performance of "device (a)" for "tag (a)" and "tag (b)" from the reference tag information. Specifically, the calculation unit 12 reads out that for "tag (a)", "CPU type A" can process "60,000 tags" in one day. The calculation unit 12 also reads out that "1 KB" of memory capacity is required for "tag (a)" to operate as one tag. Further, the calculation unit 12 reads out that "1 MB" of HDD capacity is required for "tag (a)" to operate as one tag. Similarly, the calculation unit 12 reads out that for "tag (b)", "CPU type A" can process "30,000 tags" in one day. The calculation unit 12 also reads out that "1.5 KB" of memory capacity is required for "tag (b)" to operate as one tag. Further, the calculation unit 12 reads out that when "tag (b)" operates as one tag, "500 KB" is required for the HDD capacity.

In this way, the calculation unit 12 can read reference device information corresponding to the device information in the edge device 2 scheduled to be changed. Further, the calculation unit 12 can read reference tag information corresponding to the tag information in the edge device 2 that is scheduled to be changed.

Further, the calculation unit 12 reads out, from the tag information to be changed, the content related to the processing of each tag handled by the device to be changed. The calculation unit 12 compares the read processing-related content with reference device information and tag information to calculate the resource load situation. For example, if it is determined from "Processing 1" that the number of "tags (a)" to be processed in one day is 6,000, the CPU load on CPU type A is calculated as 10%. It is possible that Further, the calculation unit 12 can calculate the required capacity of the memory or HDD based on the number of "tags (a)" to be processed. In this way, the calculation unit 12 can calculate the resource usage status by comparing the device information and tag information to be changed with the reference device information and tag information.

FIG. 10 displays the calculated resource usage status in three levels: "low," "medium," and "high." For example, for each resource, the calculation unit 12 determines "low" if the load ratio is less than 20%, "medium" if it is 20% or more and less than 80%, and "high" if it is 80% or more. It is conceivable to classify each value using a threshold value. This threshold value is not limited to the above-mentioned value, and any value can be adopted. For example, this threshold value may be set by a user in a setting section (not shown) of the engineering device 1.

In this way, the calculation unit 12 calculates the resource usage status of the edge device 2 in the control system when the control system is changed based on the device information and tag information to be changed, and outputs the result. can do.

Further, in FIG. 10, the calculation unit 12 also calculates the resource usage status of the existing edge device 2 in the control system based on the existing device information and tag information. These usage statuses can be calculated in the same manner as the method for calculating the usage status of the edge device 2 after the change. For example, reference device information and tag information are read based on existing device information and tag information. Furthermore, it is possible to calculate the usage status of each resource based on the content related to processing in existing tag information, and output the results.

In the present embodiment, an example in which the calculation unit 12 calculates an estimate of the resource usage status has been described using an example in which the edge device 2 is updated or added. However, in the case where only the tag information is changed due to a system configuration change without updating the edge device 2, etc., the calculation unit 12 similarly calculates an estimate of the resource usage status and outputs the result. be able to. Similarly, when deleting the edge device 2, the calculation unit 12 can calculate the resource usage status and output the result.

Further, the calculation unit 12 can include "system configuration information" in calculating the estimate. When each edge device 2 collects and transmits statistical data regarding tags, it is conceivable to include this information in the estimate if the usage status of resources changes significantly. For example, information regarding the load on the arithmetic unit, main storage device, and auxiliary storage device during the transmission and reception of statistical data regarding the tag is added to the reference tag information. The calculation unit 12 can calculate the resource usage status using the system information to be changed and reference tag information, and can output the result.

Further, in the same manner as described above, the calculation unit 12 can calculate the resource usage status of the controller 3 instead of the edge device 2. For example, information regarding the controller 3 is stored in advance in the device information and tag information for reference. Based on the device information and tag information of the controller 3 that is scheduled to be changed based on user input, and the device information and tag information for reference, the calculation unit 12 calculates the resource usage status of the controller 3 and outputs the result. It is possible to do so.

FIG. 11 is an example of a flowchart of estimation in the first embodiment.

In step S10, the input unit 10 receives an input of device information to be changed from the user on the input screen for the change plan information 13. In step S11, the input unit 10 receives an input of tag information to be changed from the user on the input screen for the change planned information 13. In step S12, the calculation unit 12 reads information regarding the performance of the arithmetic unit, main storage device, and auxiliary storage device corresponding to the input device information to be changed from the reference device information. In step S13, the calculation unit 12 reads information regarding the loads of the arithmetic unit, main storage device, and auxiliary storage device corresponding to the input tag information to be changed from the reference tag information. In step S14, the calculation unit 12 calculates the resource usage status based on the read reference device information and tag information.

According to the present embodiment, the calculation unit 12 can estimate the resource usage status of the edge device 2 based on the scheduled change system information and tag information. This allows the user to check in advance the system usage status of the resources of the edge device 2 that is scheduled to be changed.

In addition, the user can check in advance the impact on the higher-level engineering device 1, lower-level controller 3, etc. due to changes to the edge device 2 through the estimate, and can smoothly perform the change. .

Furthermore, since the resource usage status can be estimated in advance, the user can optimize the resource usage status.

Furthermore, by listing the resource usage status of the existing edge device 2 and the usage status of the edge device 2 after the change, the user can easily compare the resource usage status before and after the edge device 2 is changed.

Furthermore, by displaying the estimated resource usage status values as multiple classes, the user can intuitively grasp the usage status.

(Second embodiment)
FIG. 12 is a hardware configuration diagram of the engineering device 1 in the second embodiment.

The engineering device 1 in FIG. 12 includes an arithmetic unit 52 such as a CPU, a main storage device 53 such as a RAM, an auxiliary storage device 54 such as an HDD, a network interface 55 such as a LAN (Local Area Network) board, and a memory slot. and a device interface 56 such as a memory port, and a bus 57 that connects these devices to each other. The engineering device 1 is, for example, a computer such as a PC, and includes an input device 20 such as a keyboard and a mouse, and a display device 30 such as an LCD monitor.

In this embodiment, a program for causing a computer to execute information processing of the engineering device 1 is installed in the auxiliary storage device 54. The engineering device 1 expands this program into the main storage device 53 and executes it by the arithmetic device 52. Thereby, the functions of each block shown in FIG. 2 are realized within the engineering device 1, and the above-mentioned estimation becomes possible. Note that the data generated by this information processing is temporarily held in the main storage device 53 or stored and saved in the auxiliary storage device 54.

This program can be installed, for example, by attaching an external device 58 recording this program to the device interface 56 and storing this program from the external device 58 into the auxiliary storage device 54. An example of the external device 58 is a computer-readable recording medium or a recording device containing such a recording medium. Examples of recording media are CD-ROM (Compact Disk Read Only Memory), CD-R (Compact Disk Recordable), flexible disk, DVD-ROM (Digital Versatile Disk Read Only Memory), and DVD-R (Digital Versatile Disk Recordable). Yes, and an example of a recording device is an HDD. Further, this program can be installed, for example, by downloading this program via the network interface 55.

This allows the functions of the engineering device 1 to be realized by software.

Although several embodiments have been described above, these embodiments are presented only as examples and are not intended to limit the scope of the invention. The engineering device 1 described herein can be implemented in various other forms. Further, various omissions, substitutions, and changes can be made to the form of the engineering device 1 described in this specification without departing from the gist of the invention. The appended claims and their equivalents are intended to cover such forms and modifications as fall within the scope and spirit of the invention.

1: Engineering equipment, 2: Edge device, 3: Controller,
10: input section, 11: storage section, 12: calculation section, 13: change schedule information, 14: existing information,
15: Reference information, 20: Input device, 30: Display device,
40: Global network, 50: Local network,
52: Arithmetic device, 53: Main storage device, 54: Auxiliary storage device,
55: network interface, 56: device interface, 58: external device,
100: Production line, 200: Manufacturing site, 400: Management office

Claims (10)

an input unit that receives input of device information and tag information that are scheduled to be changed regarding the control system that is scheduled to be changed;
a calculation unit that calculates the resource usage status of devices in the control system when the control system is changed based on the device information scheduled to be changed and the tag information, and outputs a calculation result of the resource usage status; and,
Engineering equipment equipped with. The engineering device according to claim 1, wherein the calculation result of the resource usage status is output to a screen of a device other than the engineering device. The resource includes at least one of an arithmetic unit, a main storage device, and an auxiliary storage device in a device within the control system,
The calculation unit calculates a load status of at least one of the arithmetic unit, the main storage device, and the auxiliary storage device as the usage status of the resource.
The engineering device according to claim 1. further comprising a storage unit that stores reference device information and tag information regarding the control system,
The calculation unit reads the reference device information and tag information from the storage unit based on the device information and tag information to be changed,
The calculation unit calculates the usage status of the resource based on the reference device information and tag information.
The engineering device according to claim 1. The reference device information includes information regarding the performance of at least one of an arithmetic unit, a main storage device, and an auxiliary storage device in a device in the control system.
The engineering device according to claim 4. The reference tag information includes information regarding a load on at least one of a computing device, a main storage device, and an auxiliary storage device when a device in the control system operates based on the tag.
The engineering device according to claim 4. The calculation unit calculates the usage status of the resource by comparing the device information and tag information to be changed with the reference device information and tag information.
The engineering device according to claim 4. further comprising a storage unit that stores existing device information and tag information regarding the control system,
The engineering apparatus according to claim 1, wherein the calculation unit calculates the usage status of the resource based on the device information and tag information to be changed and the existing device information and tag information. The engineering device according to claim 1, wherein the resource usage status is classified into a plurality of classes by comparing a value representing the resource usage status with a threshold value. The engineering device according to claim 1, wherein the device is an edge device interposed between the engineering device and a controller.

Images