Recording medium, management assistance device, management system, and management assistance method

By designing management auxiliary programs in the management system and automatically analyzing and generating management information, the problem of cumbersome data setting in the existing technology is solved, and the operation efficiency of the management system is improved.

CN117642703BActive Publication Date: 2024-11-15MITSUBISHI ELECTRIC CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202180100095.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-23
Publication Date
2024-11-15
Estimated Expiration
2041-12-23

AI Technical Summary

Technical Problem

When the existing management system processes a large amount of data, users need to manually set the data, which leads to cumbersome setting of tasks and increases the operation burden.

Method used

A management auxiliary program is designed to connect the computer to the programmable controller to generate management information, receive and analyze the setting information, and determine data attributes, thereby assisting users in setting the management system and reducing manual operations.

Benefits of technology

By automatically determining data attributes and generating management information, the setting work burden of the management system is reduced and the operation efficiency is improved. Users can more easily utilize the functions of the management system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117642703B_ABST
    Figure CN117642703B_ABST
Patent Text Reader

Abstract

A management support device (10) is connected to a PLC (21) and generates management information to be displayed on a management screen for supporting the management of the PLC (21). The program causes the management support device (10) to function as a receiving unit (11) and a generating unit (12). The receiving unit (11) receives setting information (22) pre-set in the PLC (21) in relation to data possessed by the PLC (21) from the PLC (21). The generating unit (12) determines the attribute of the data based on the setting information and generates management information (131) indicating the determined attribute, wherein the attribute of the data indicates the use of the data in the management of the PLC (21).
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to a management assistance program, a management assistance device, a management system and a management assistance method. Background Art

[0002] In a field represented by a factory or large industrial equipment, a management system is sometimes constructed for a control system in which a large number of devices are controlled by a programmable controller, and the control system is used to monitor the control status and control the devices as needed to perform management. As such a management system, for example, a supervisory control system called SCADA (Supervisory Control And Data Acquisition) is known for performing system monitoring and process control in a unified manner (for example, refer to Patent Document 1).

[0003] Patent document 1 describes a technique for creating a device list based on control information obtained from a PLC (Programmable Logic Controller) constituting an existing system, wherein the device list identifies devices including control devices as monitoring and control objects. According to this technique, when a monitoring and control system is constructed for an existing control system, the time required for a user to define monitoring objects can be reduced.

[0004] Patent Document 1: International Publication No. 2019 / 207693 Summary of the invention

[0005] Most management systems have functions such as alarms and log records on the management side, independent of the control system that is the monitored object. In order to utilize the data of the programmable controller to exert such functions, a setting operation is required to select the data to be utilized from the large amount of data processed on the management side. However, such setting operations are complicated and may become an excessive burden on the operator.

[0006] The present invention has been proposed in view of the above-mentioned actual situation, and an object of the present invention is to reduce the burden of setting work related to the management system.

[0007] In order to achieve the above-mentioned purpose, the management assistance program of the present invention enables a computer to function as a receiving unit and a generating unit. The computer is connected to a programmable controller. The computer generates management information displayed in a management screen for assisting the management of the programmable controller. The receiving unit receives setting information pre-set in the programmable controller related to the data possessed by the programmable controller from the programmable controller. The generating unit determines the attributes of the data based on the setting information and generates management information representing the determined attributes. The attributes of the data represent the purpose of the data in the management of the programmable controller.

[0008] Effects of the Invention

[0009] According to the present invention, the receiving unit receives the setting information, and the generating unit determines the attribute indicating the purpose of the data based on the setting information, thereby determining the management side function corresponding to the purpose of the data, thereby reducing the burden of setting work on the management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 It is a diagram showing the configuration of a management system according to an embodiment.

[0011] Figure 2 It is a diagram showing the hardware configuration of the management support device according to the embodiment.

[0012] Figure 3 It is a diagram showing the structure of a receiving unit according to an embodiment.

[0013] Figure 4 It is a diagram showing the structure of a generation unit according to an embodiment.

[0014] Figure 5 This is a diagram showing an example of setting information according to an embodiment.

[0015] Figure 6 This is a diagram showing an example of the first management information according to the embodiment.

[0016] Figure 7 It is a diagram showing an example of the second management information involved in the embodiment.

[0017] Figure 8 It is a flowchart showing the management support processing involved in the embodiment.

[0018] Fig. 9 It is a flowchart showing the receiving process involved in the implementation method.

[0019] Fig.10 This is a flowchart showing the list generation process according to the embodiment.

[0020] Fig.11 It is a diagram for explaining the creation of a registration list and a deletion list according to the embodiment.

[0021] Fig.12 This is a flowchart showing the attribute determination process according to the embodiment.

[0022] Fig.13 This is a flowchart showing the registration process involved in the embodiment.

[0023] Fig.14 It is a diagram showing a first example of a management screen according to the embodiment.

[0024] Fig.15 It is a diagram showing a second example of the management screen according to the embodiment.

[0025] Fig.16 It is a diagram showing a third example of the management screen according to the embodiment.

[0026] Fig.17 It is a diagram showing a fourth example of the management screen according to the embodiment. DETAILED DESCRIPTION

[0027] Hereinafter, a management system according to an embodiment of the present invention will be described in detail with reference to the drawings.

[0028] Implementation

[0029] like Figure 1 As shown, the management system 100 according to the present embodiment is a system for a user to manage a control system 20, and is constructed as a FA (Factory Automation) system in a factory, for example, wherein in the control system 20, a PLC 21 controls a device 23. The management system 100 includes: a management support device 10 that supports a user by generating management information 131; and a control system 20 that is connected to the management support device 10 via an industrial network 30.

[0030] The control system 20 is a system for realizing production lines, processing lines, inspection lines, and other various processing processes. The control system 20 has a plurality of PLCs 21 and devices 23 that are controlled by each of the PLCs 21. The PLCs 21 and the devices 23 are connected via a network, a communication line for performing serial communication, or wiring for transmitting current signals or voltage signals. The network connecting the PLCs 21 and the devices 23 may also be an industrial network 30.

[0031] PLC 21 is a control device also called a programmable controller, and controls the device 23 by executing a control program. Figure 1 2 schematically shows that one PLC 21 is connected to one device 23, but there may be multiple devices 23 connected to each PLC 21. Figure 1 In the figure, the control system 20 includes three PLCs 21, but the number of PLCs 21 constituting the control system 20 is not limited thereto, and may be less than three or more than three.

[0032] For example, PLC21 can also control the rotation speed of the motor shaft of device 23 as a working machine, and control the rotation speed of device 23 as a compressor for conveying waste oil, based on the temperature of the cutting oil in the tank detected by device 23 as a temperature sensor. Such control related to cutting oil is realized by the coordinated control of multiple PLC21. However, the control realized by PLC21 is not limited to the control of cutting oil, and can be control for implementing the detection, processing and qualified product judgment of the conveyed workpiece, or other control. In addition, the control for implementing a series of processes can also be executed by a single PLC21.

[0033] PLC21 controls the device 23 using the data stored in the built-in memory. For example, PLC21 writes the data representing the sensing result received from the sensor into the shared memory shared with other PLC21. Other PLC21 refers to the shared memory, writes the output value determined based on the sensing result into the memory, and outputs the output value to the working machine, thereby operating the working machine. In addition, the data possessed by PLC21 is not limited to the input and output values, but can represent the action mode of PLC21 and the device 23, and can also include intermediate data generated when PLC21 executes the control program. In order to show the control status in the control system 20 in real time, the data possessed by PLC21 is provided to the user of the management system 100 for monitoring the control status. That is, if PLC21 is set as the management object, the control system 20 can be substantially managed.

[0034] The PLC 21 has previously set setting information 22 for managing the control system 20 using data held by the PLC 21. The setting information 22 is provided from the PLC 21 to the management support device 10 in response to a request from the management support device 10. Details of the setting information 22 will be described later.

[0035] The management support device 10 is a computer represented by an industrial PC (Personal Computer) or a server device, and is connected to the PLC 21 via an industrial network. Figure 2 As shown, the hardware structure includes a processor 41, a main storage unit 42, an auxiliary storage unit 43, an input unit 44, an output unit 45, and a communication unit 46. The main storage unit 42, the auxiliary storage unit 43, the input unit 44, the output unit 45, and the communication unit 46 are connected to the processor 41 via an internal bus 47.

[0036] The processor 41 includes a CPU (Central Processing Unit) as a processing circuit. The processor 41 implements various functions of the management support device 10 and performs the processing described below by executing the program P1 stored in the auxiliary storage unit 43. The program P1 corresponds to an example of a management support program.

[0037] The main storage unit 42 includes a RAM (Random Access Memory). The program P1 is loaded from the auxiliary storage unit 43 into the main storage unit 42. The main storage unit 42 is used as a work area for the processor 41.

[0038] The auxiliary storage unit 43 includes a nonvolatile memory represented by an EEPROM (Electrically Erasable Programmable Read-Only Memory) and an HDD (Hard Disk Drive). In addition to the program P1, the auxiliary storage unit 43 also stores various data used for processing by the processor 41. The auxiliary storage unit 43 supplies the data used by the processor 41 to the processor 41 according to the instruction of the processor 41, and stores the data supplied from the processor 41.

[0039] The input unit 44 includes input devices represented by a keyboard and a pointing device. The input unit 44 acquires information input by a user of the management support device 10 and notifies the processor 41 of the acquired information.

[0040] The output unit 45 includes output devices represented by an LCD (Liquid Crystal Display) and a speaker. The output unit 45 presents various information to the user according to the instruction of the processor 41.

[0041] The communication unit 46 has a network interface circuit for communicating with an external device. The communication unit 46 receives a signal from the outside and outputs information indicated by the signal to the processor 41. In addition, the communication unit 46 transmits a signal indicating information output from the processor 41 to an external device.

[0042] The input unit 44 and the output unit 45 correspond to the UI (User Interface) of the management support device 10. However, the management support device 10 may be connected to an external UI device via the communication unit 46, and may obtain information from the user and provide the information to the user via the communication unit 46. When an external UI device is used as the UI of the management support device 10 instead of the input unit 44 and the output unit 45, the input unit 44 and the output unit 45 may be omitted.

[0043] Through the cooperative action of the above hardware structure, the management support device 10 plays a function of supporting the management of the PLC 21. Figure 1 As shown, the management support device 10 includes: a receiving unit 11 that receives setting information 22 from a PLC 21; a generating unit 12 that generates management information 131 based on the setting information 22; a storage unit 13 that stores the management information 131; and an output unit 14 that outputs the management information 131.

[0044] The receiving unit 11 is mainly implemented by the collaborative action of the processor 41, the main storage unit 42 and the communication unit 46. The receiving unit 11 detects the PLC 21 on the industrial network 30. In detail, the receiving unit 11 sends an ARP (Address Resolution Protocol) request frame to the industrial network 30, receives the ARP response frame, and thereby detects all PLCs 21 connected to the industrial network 30. In addition, the receiving unit 11 collects and stores the setting information 22 saved by each PLC 21. The receiving unit 11 is equivalent to an example of a receiving unit that receives setting information pre-set in the programmable controller in relation to the data possessed by the programmable controller from the programmable controller.

[0045] like Figure 3 As shown, the receiving unit 11 includes: a receiving indication unit 111, which indicates the reception of the setting information 22; an information receiving unit 112, which receives the setting information 22 according to the indication; a detection unit 113, which detects the change of the newly received setting information 22 relative to the setting information received in the past; and a storage unit 114, which stores the setting information 22.

[0046] The receiving instruction unit 111 has the authority to start receiving, and instructs the information receiving unit 112 to receive the setting information 22 from all PLCs 21 at any timing determined by the user or at a predetermined period. The information receiving unit 112 detects the PLCs 21 on the industrial network 30 that is the monitoring target in the above manner, and receives and collects the setting information 22 from each of the PLCs 21 at the timing when the instruction is received from the receiving instruction unit 111.

[0047] The detection unit 113 obtains the received setting information 22 from the information receiving unit 112, and determines whether there is a difference between the setting information 22 obtained from each PLC 21 and the setting information 22 stored in the storage unit 114. In addition, the detection unit 113 provides the setting information 22 detected to be changed to the generation unit 12. The storage unit 114 stores the setting information 22 detected to be changed. That is, in the storage unit 114, the past setting information 22 is overwritten with the latest setting information 22, and the setting information 22 is not written again if the content of the setting information 22 has not changed.

[0048] Return to Figure 1 The generation unit 12 is mainly implemented by the cooperation of the processor 41 and the main storage unit 42. The generation unit 12 generates the management information 131 based on the setting information 22 and registers it in the storage unit 13. In addition, the generation unit 12 updates the management information 131 registered in the storage unit 13 based on the newly collected setting information 22.

[0049] like Figure 4 As shown, the generating unit 12 includes: a list generating unit 121, which generates a list of information that should be updated for the management information 131; an attribute determining unit 122, which determines the attribute of the data possessed by the PLC 21 according to the setting information 22; a registering unit 123, which registers the new information as the management information 131 based on the generated list; and a deleting unit 124, which deletes a part of the information from the management information 131 based on the generated list.

[0050] The list generation unit 121 generates a list of information to be newly registered and information to be deleted with respect to the current management information 131 based on the setting information 22 received by the receiving unit 11 and the management information 131 stored in the storage unit 13 .

[0051] Here, the setting information 22 and the management information 131 are described. Figure 5 As shown in the example, the setting information 22 includes information related to the PLC 21 for which the setting information 22 is set, including the device name assigned to the PLC 21, the model of the PLC 21, and the IP (Internet Protocol) address assigned to the PLC 21. Figure 5 In the example shown in FIG. 1 , the device name of one PLC 21 among the plurality of PLCs 21 is set to “PLC1”, the model of the PLC 21 is “R00CPU”, and an IP address of “192.168.1.1” is allocated to the PLC 21 .

[0052] In addition, the setting information 22 shows the description related to the control object and the control object of PLC21. The description related to the control object is a character string arbitrarily set by the user. Figure 5 In the example, the description "for tank control" is added and the "Tank structure" is set as the control object.

[0053] The "Tank structure" is data that shows the label (label) given to one or more data of PLC21, the data type of the data, and the comment in association with each other. Figure 5 In the example, the data to which the label "Temperature Alarm" is assigned is of INT type, and a comment "Hi, 70" is set for the data. The character string "Alarm" in the label indicates that the management support device 10 uses the data to perform the alarm function, and the character string "Temperature" is used to identify the data in the management support device 10. That is, the setting information 22 includes a label assigned to the data of the PLC 21, and the label sometimes indicates the use of the data in the management of the PLC 21.

[0054] The management information 131 includes first management information related to the PLC 21 and second management information related to the control object of the PLC 21. Figure 6 As shown, the first management information shows, for each PLC 21, the device name, model, assigned IP address, description related to the control object, and the number of control objects in association. Figure 6 It can be seen that most of the first management information is related to Figure 5 The number of control objects in the first management information is equal to the number of control objects shown in the setting information 22. Figure 5 In the example, since one control object, "Tank structure", is shown by setting information 22, Figure 6 As shown, the number of control objects of "PLC1" in the first management information is one.

[0055] like Figure 7 As shown, the second management information is information that shows the device name of PLC21 as the upper device, the control object of the upper device, the tag name of the data related to the control object, the attribute of the data, and the detailed information related to the data in association. Since the second management information includes the device name of PLC21, the second management information can also be linked to the first management information and used as management information 131 that summarizes the first management information and the second management information in one table.

[0056] The control object of the second management information corresponds to the control object of the setting information 22. Specifically, a character string such as "Tank" obtained by deleting the "structure" part from the name such as "Tank structure" of the setting information 22 is used as the control object of the second management information. The control object of the second management information may correspond to a physical device subordinate to the PLC 21, may correspond to a logical device set regardless of the physical device structure, or may be obtained by simply grouping data used in the management support device 10 for convenience by the user.

[0057] In addition, the tag name and attribute of the second management information are generated based on the tag of the configuration information 22. The detailed information of the second management information corresponds to the comment of the configuration information 22.

[0058] Return to Figure 4 The list generation unit 121 detects the incompatible parts of the latest setting information 22 obtained from the receiving unit 11 and the management information 131 registered in the storage unit 13. In addition, the list generation unit 121 generates a registration list indicating the latest setting information 22 including the information to be registered in the management information 131, and a deletion list indicating the information not included in the latest setting information 22 and to be deleted from the management information 131. The list generation unit 121 outputs the registration list to the attribute determination unit 122, and outputs the deletion list to the deletion unit 124.

[0059] The attribute determination unit 122 extracts the attribute of the data from the tag included in the setting information 22 acquired in the form of the registration list. The attribute of the data indicates the management purpose of the data in the management support device 10. For example, Figure 7 The data with the tag name "Temperature" shown is used for the alarm function of the management support device 10. Specifically, when the value of the data is "Hi", that is, greater than "70" shown in "Detailed Information", the user is notified that the data value exceeds the threshold. The attribute determination unit 122 outputs the attribute determination result and the registration list to the registration unit 123.

[0060] The registering unit 123 adds information to the management information 131 based on the setting information obtained in the form of the registration list and the attribute determined by the attribute determination unit 122. For example, when the management support device 10 initially receives the setting information 22 indicating the device name "PLC1", the registering unit 123 writes the information corresponding to the setting information 22 as the management information 131 into the storage unit 13. In detail, the registering unit 123 adds Figure 6 The record of the row including "PLC1" in the first management information shown, Figure 7 The record of the row including "PLC1" in the second management information shown.

[0061] The deletion unit 124 deletes part of the management information 131 based on the deletion list. For example, when a PLC 21 with a device name such as "PLC3" is disconnected from the industrial network 30, the setting information 22 from the PLC 21 will not be received by the management support device 10, so the deletion unit 124 deletes the information related to "PLC3" from the management information. Figure 6 The record of the row including "PLC3" in the first management information shown, Figure 7 The record of the row including "PLC3" in the second management information shown is deleted.

[0062] The generating unit 12 corresponds to an example of a generating unit that determines the attribute of data based on the setting information and generates management information indicating the determined attribute, wherein the attribute of the data indicates the use of the data in the management of the programmable controller. The storing unit 13 corresponds to an example of a storing unit that registers the management information.

[0063] Return to Figure 1 The output unit 14 is mainly realized by the output unit 45. The output unit 14 reads the management information 131 stored in the storage unit 13, and displays the management information 131 on a management screen for assisting the user in managing the PLC 21.

[0064] Next, use Figures 8 to 17 The management support process executed by the management support device 10 is described below. The management support process corresponds to an example of a management support method and is started by the management support device 10 executing a program P1. Figure 8 An example of the process of management assistance processing is shown in FIG. Figure 8 For example, the order of the steps constituting the management support process may be appropriately changed, or the steps may be executed in parallel instead of being executed sequentially.

[0065] In management-assisted processing, such as Figure 8 As shown, the receiving unit 11 performs a reception process of the setting information 22 (step S1), the list generating unit 121 of the generating unit 12 performs a list generating process (step S2), the attribute determining unit 122 performs an attribute determining process (step S3), and the registering unit 123 performs a registration process (step S4) in sequence. The details of each of these steps S1 to S4 will be described below.

[0066] exist Fig. 9The flow of the receiving process is shown in FIG. In the receiving process, the receiving instruction unit 111 determines whether the receiving instruction is manually input by the user. When it is determined that the receiving instruction is manually input (step S11: Yes), the processing performed by the receiving unit 11 is transferred to step S13, and the receiving unit 11 immediately receives the setting information 22.

[0067] On the other hand, when it is determined that the receiving instruction is not manually input (step S11; No), the receiving instruction unit 111 determines whether the current time is a predetermined receiving timing (step S12). Specifically, the receiving instruction unit 111 determines whether a predetermined period of time has passed since the last reception of the setting information 22. The length of the period is, for example, 1 minute, 1 hour, or 1 day.

[0068] When it is determined that the current time is the reception timing (step S12; Yes), the reception instruction unit 111 outputs a trigger requesting the reception of the setting information 22 to the information receiving unit 112, and the information receiving unit 112 detects the PLC 21 existing in the industrial network 30 as the management target (step S13). Then, the information receiving unit 112 receives the setting information 22 from each detected PLC 21 (step S14).

[0069] Next, the detection unit 113 determines whether there is a difference between the setting information 22 received from each PLC 21 and the setting information 22 received last time (step S15). Specifically, the detection unit 113 determines whether there is a difference between the setting information 22 received in step S14 and the setting information 22 stored in the storage unit 114 for each PLC 21.

[0070] When it is determined that there is a difference (step S15; Yes), since the setting information 22 has changed, it is necessary to update the management information 131. Therefore, the detection unit 113 outputs the setting information 22 received in step S14 to the generation unit 12 (step S16). In addition, the detection unit 113 updates the setting information 22 stored in the storage unit 114 by overwriting the setting information 22 received in step S14 with the storage unit 114 (step S17).

[0071] If it is determined in step S12 that the current time is not the reception timing (step S12; No), if it is determined in step S15 that there is no difference (step S15; No), and after step S17 is completed, the reception processing is completed, and the processing executed by the management support device 10 returns from the reception processing to Figure 8 Management assistance processing shown.

[0072] exist Fig.102 shows the flow of the list generation process performed after the receiving process. In the list generation process, the list generation unit 121 determines whether the setting information 22 of the PLC 21 has been obtained from the receiving unit 11 (step S201). When it is determined that the setting information 22 has not been obtained (step S201; No), the list generation process ends. On the other hand, when it is determined that the setting information 22 has been obtained (step S201; Yes), the list generation unit 121 substitutes 1 into the variable i and substitutes zero into the variable k (step S202).

[0073] Next, the list generation unit 121 creates a registration list. Specifically, the list generation unit 121 determines whether the value of the variable i is less than or equal to the total number N of the acquired setting information 22 (step S203). Here, the variable i is associated with the number of the acquired setting information 22. Fig.11 The value of variable i when step S203 is first executed is equal to 1 substituted in step S202, so the determination result of step S203 is affirmative.

[0074] When it is determined that the value of the variable i is less than or equal to the total number N (step S203; Yes), the list generating unit 121 determines whether the i-th setting information 22 corresponds to the management information 131 stored in the storage unit 13 (step S204). For example, if the value of the variable i is 1, the list generating unit 121 determines whether the i-th setting information 22 corresponds to the management information 131 stored in the storage unit 13 (step S204). Figure 5 The device name, model, IP address, and number of controlled objects shown in the management information 131 are the same as those in the management information 131. Figure 6 In addition, the list generation unit 121 determines whether the above elements shown in the table are consistent with each other. Figure 5 The tags included in the control object in the setting information 22 are similar to those in the Figure 7 It is determined whether the combination of the tag name and the attribute included in the management information 131 is equal, and it is determined whether the comment of each tag included in the control object of the setting information 22 and the detailed information included in the management information 131 are substantially equal.

[0075] exist Fig.11 In the example, the setting information 22 about the first "PLC1" is equal to the management information. Fig.10 The result of step S204 is affirmative. When it is determined in step S204 that the i-th setting information 22 corresponds to the management information 131 (step S204; Yes), the list generation unit 121 increases the variable k by 1 (step S205). Here, the variable k corresponds to the number of PLC21s that do not need to be updated, and the information contained in the acquired setting information 22 corresponds to the management information 131. Fig.11In the example, when the first "PLC1" is selected, the variable k is incremented from zero to 1.

[0076] Next, the list generation unit 121 increments the variable i by 1 (step S206 ), and repeats the processing of step S203 and thereafter. Thus, the processing of steps S203 to S206 is repeated similarly for the setting information 22 acquired from the next PLC 21 .

[0077] In step S204, when it is determined that the i-th setting information 22 does not correspond to the management information 131 (step S204; No), the list generation unit 121 adds the i-th setting information 22 to the registration list (step S207). Fig.11 In the example, when the value of the variable i is 3, the information related to the third "PLC3" is not included in the management information 131 and does not correspond. Therefore, the setting information 22 related to "PLC3" is added to the registration list. After step S207, step S206 and subsequent processing are repeated.

[0078] In step S203, when it is determined that the variable i is not less than or equal to the total number N (step S203; No), since the comparison with the management information 131 has been completed for all the setting information 22, the registration list has been completed, and therefore the list generation unit 121 creates a deletion list. Specifically, the list generation unit 121 determines whether the value of the variable k is equal to the total number M of the PLC21 shown in the saved management information (step S208). When the variable k is equal to the total number M (step S208; Yes), the information related to all the PLC21 shown in the management information 131 corresponds to the setting information 22, and there is no information that should be deleted from the management information 131, so the list generation process ends.

[0079] On the other hand, when it is determined that the variable k is not equal to the total number M (step S208; No), the list generation unit 121 substitutes 1 into the variable j (step S209). Fig.11 As shown in FIG. 1 , the variable j corresponds to a number consecutively assigned to each of the PLCs 21 shown in the management information 131. Fig.11 In the example, the value of the variable k is counted to 2, which is different from the value of the total number M, 3, so the determination result of step S209 is negative, and 1 is set as the initial value of the variable j.

[0080] Next, the list generation unit 121 determines whether the value of the variable j is less than or equal to the total number M (step S210). The value of the variable j when step S210 is first executed is equal to 1 substituted in step S209, so the determination result of step S210 is affirmative.

[0081] When it is determined that the value of the variable j is less than or equal to the total number M (step S210; Yes), the list generation unit 121 determines whether the information related to the j-th PLC 21 in the management information 131 corresponds to a certain setting information 22 (step S211). The comparison between the setting information 22 and the management information 131 is performed in the same manner as the comparison performed in step S204. Fig.11 In the example of , the value of the variable j is 1, and the information related to the first "PLC1" in the management information 131 corresponds to the setting information 22 obtained from "PLC1", so the determination result of step S211 is affirmative.

[0082] When it is determined that the information related to the j-th PLC 21 corresponds to a certain setting information 22 (step S211; Yes), the list generation unit 121 increases the variable j by 1 (step S212), and repeats the processing of step S210 and thereafter. Thus, the processing of steps S210 to S212 is also repeated for the information related to the next PLC 21 in the management information 131.

[0083] In step S211, when it is determined that the information related to the j-th PLC 21 does not correspond to any of the setting information 22 (step S211; No), the list generation unit 121 adds the information of the part of the management information 131 that does not correspond to the setting information 22 to the deletion list (step S213). Fig.11 In the example, when the value of the variable j is 3, the setting information 22 of the PLC 21 having the device name is not obtained for the third "PLC99" in the management information 131, and it does not correspond to all the setting information 22. Therefore, the information related to "PLC99" is added to the deletion list.

[0084] In addition, the information added to the deletion list is not limited to the information representing each of PLC21, the control object, and the label. For example, the following example is conceivable, that is, when the information related to PLC21 with a device name such as "PLC88" is registered in the management information 131, the setting information 22 is received from the "PLC88", but a part of the control object has been deleted in the newly received setting information 22. In such an example, the part related to the control object in the information of "PLC88" is added to the deletion list. In addition, an example is conceivable that the control object has not changed, but a part of the label has been deleted in the newly received setting information 22. In such an example, the part related to the label is added to the deletion list.

[0085] After step S213, the processing of step S212 and thereafter is repeated. In addition, if it is determined in step S210 that the value of variable j is not less than or equal to the total number M (step S210; No), the list generation unit 121 has completed the comparison with the setting information 22 for all PLCs 21 shown in the management information 131, and the deletion list has been completed, so the list generation process is terminated, and the process executed by the management support device 10 returns from the list generation process to Figure 8 Management assistance processing shown.

[0086] exist Fig.12 3 shows the flow of the attribute determination process performed after the list generation process. In the attribute determination process, the attribute determination unit 122 determines whether the setting information 22 compiled into the registration list by the list generation unit 121 has been acquired (step S301). When it is determined that the setting information 22 has not been acquired (step S301; No), the attribute determination process ends. On the other hand, when it is determined that the setting information 22 has been acquired (step S301; Yes), the attribute determination unit 122 selects one unselected tag from the setting information 22 (step S302).

[0087] Next, the attribute determination unit 122 determines whether the selected tag contains a character string such as "Alarm" (step S303). That is, the attribute determination unit 122 determines whether the tag is assigned to the data in order to use the alarm function in the management support device 10. Here, the character string may be allowed to fluctuate between uppercase and lowercase. In addition, if the word similar to "Alarm" such as "Alert" and "Warning" is included, the determination result of step S303 may also be affirmative.

[0088] When it is determined that the character string "Alarm" is included (step S303; Yes), the attribute determination unit 122 determines whether the alarm function using the data assigned with the tag can be set. Specifically, the attribute determination unit 122 analyzes the annotation associated with the tag (step S304), and determines whether the annotation contains detailed setting information required for setting the alarm function (step S305). For example, it is determined whether the annotation contains a threshold value, and whether the annotation contains a character string "Hi" or "Lo" indicating whether an alarm is issued when the data value exceeds the threshold value or when it falls below the threshold value.

[0089] When it is determined that the comment includes detailed setting information (step S305 ; Yes), the attribute determination unit 122 determines that the attribute of the data to which the tag is assigned is an alarm attribute (step S306 ), and assigns the alarm attribute to the tag.

[0090] On the other hand, when it is determined that the annotation does not include detailed setting information (step S305; No), the attribute determination unit 122 determines that the attribute of the data assigned to the tag is an RT (Real-Time) data attribute (step S307), and assigns the RT data attribute to the tag. The RT data attribute refers to the data of the PLC 21 being directly provided to the user of the management support device 10 as data that expresses the control status in real time.

[0091] If it is determined in step S303 that the tag does not include a character string such as "Alarm" (step S303; No), the attribute determination unit 122 determines whether the tag includes a character string such as "Logging" (step S308). That is, the attribute determination unit 122 determines whether the tag is given to the data in order to use the logging function in the management support device 10. The logging function is a function that saves the history of data and provides it for subsequent verification. In this determination, fluctuations in uppercase and lowercase letters and substitutions to similar terms may also be allowed.

[0092] When it is determined that the tag includes a character string "Logging" (step S308; Yes), the attribute determination unit 122 determines that the attribute of the data to which the tag is assigned is a logging attribute (step S309), and assigns the logging attribute to the tag.

[0093] If it is determined in step S308 that the tag does not include a character string such as "Logging" (step S308; No), the attribute determination unit 122 determines whether the tag includes a character string such as "Dataset" (step S310). That is, the attribute determination unit 122 determines whether the tag is assigned to the data in order to use the data set function in the management support device 10. The data set function refers to a function of displaying the values ​​of a plurality of data to the user at a glance. In this determination, fluctuations in uppercase and lowercase and substitutions to similar terms may also be allowed.

[0094] When it is determined that the tag includes the character string "Dataset" (step S310; Yes), the attribute determination unit 122 determines that the attribute of the data assigned with the tag is a data set attribute (step S311), and assigns the data set attribute to the tag.

[0095] When it is determined in step S310 that the tag does not include the character string "Dataset" (step S310; No), the attribute determination unit 122 determines that the attribute of the data assigned with the tag is the RT data attribute (step S312), and assigns the RT data attribute to the tag.

[0096] After steps S306, S307, S309, S311, and S312, the attribute determination unit 122 determines whether all tags are selected (step S313). If it is determined that all tags are not selected (step S313; No), the attribute determination unit 122 repeats step S302 and subsequent processing. Thus, tags are selected in sequence, and the determination based on the attributes of the tags is performed. If it is determined that all tags are selected (step S313; Yes), the attribute determination processing ends, and the processing performed by the management support device 10 returns from the attribute determination processing to Figure 8 Management assistance processing shown.

[0097] exist Fig.13 The flow of the registration process performed after the attribute determination process is shown in FIG. 4 . In the registration process, the registration unit 123 determines whether the setting information 22 summarized as the registration list and the attribute information indicating the attribute determined by the attribute determination unit 122 have been obtained (step S41). When it is determined that the setting information 22 and the attribute information have not been obtained (step S41; No), the registration process ends. On the other hand, when it is determined that the setting information 22 and the attribute information have been obtained (step S41; Yes), the registration unit 123 initializes the management information 131 and substitutes 1 as the initial value for the variable i (step S42). Initialization of the management information 131 means deleting the currently registered content.

[0098] Next, the registering unit 123 determines whether the value of the variable i is less than or equal to the total number N of the acquired setting information 22 (step S43). Fig.10 The same determination is made as in step S203 shown.

[0099] Next, the registering unit 123 obtains the device information from the i-th setting information 22 (step S44). Here, the device information refers to information related to the PLC 21 and the number of controlled objects, for example, Figure 5 Then, the registration unit 123 adds the device information acquired in step S44 to the first management information (step S45).

[0100] Next, the registering unit 123 obtains tag information from the i-th setting information 22 (step S46). Figure 5 The registering unit 123 then adds the label information acquired in step S46 to the second management information (step S47).

[0101] Next, the registering unit 123 increments the variable i by 1 (step S48 ), and repeats the processes in and after step S43 . Thus, the processes in steps S43 to S48 are executed for each of the setting information 22 .

[0102] If it is determined in step S43 that the value of the variable i is not less than or equal to the total number N (step S43; No), the registration process ends, and the process performed by the management support device 10 returns from the registration process to the Figure 8 Management assistance processing shown.

[0103] After the registration process in step S4, the deletion unit 124 deletes part of the management information 131 stored in the storage unit 13 according to the deletion list created in step S2 (step S5). Thus, the update of the management information 131 based on the registration list and the deletion list is completed.

[0104] Next, the output unit 14 outputs the management information 131 in response to a request from the user (step S6). Specifically, the output unit 14 displays a management screen showing the management information 131. Fig.14 FIG. 1 shows an example in which the system configuration of the control system 20 is displayed on the management screen 141 based on the management information 131. Figure 6 , 7 It can be seen that one or more control objects are subordinate to PLC21, one or more combinations of tag names and attributes are subordinate to each control object, and PLC21, control objects, tag names and attributes are hierarchical in sequence. Fig.14 In the example of , the device name of PLC21, the character string indicating the control object, and the tag name are displayed in a hierarchical manner in the same manner as the management information 131. Thus, the user can easily recognize the system configuration of the control system.

[0105] In addition, if Fig.14 In the management screen of , the user selects the object 142 including the icon and the character string representing the PLC 21. Fig.15 As shown in FIG. 1 , the output unit 14 extracts device information related to the selected PLC 21 from the management information 131 and displays it on the management screen 141. Specifically, Fig.15 The device name, model, IP address and description of the selected PLC 21 are displayed in the management screen 141. Thus, the user can obtain detailed information on a specific PLC 21.

[0106] In addition, if Fig.14 In the management screen 141 of FIG. 14 , the user selects an object 143 including an icon and a tag name representing data possessed by PLC 21. Fig.16As shown in FIG. 1 , the output unit 14 extracts tag information related to the selected data from the management information 131 and displays it on the management screen 141. Specifically, Fig.16 In the management screen 141 of , a setting form for using the alarm function is displayed in correspondence with the attribute of the data, ie, "Alarm", using a character string "Temperature" which is the tag name of the selected data.

[0107] In addition, if Fig.14 In the management screen 141 of FIG. 144, an object 144 representing data of PLC 21 is selected. Fig.17 As shown in FIG. 1 , the output unit 14 extracts tag information related to the selected data from the management information 131 and displays it on the management screen 141. Fig.17 In the management screen 141 of , a setting form for using the logging function is displayed in correspondence with the attribute “Logging” of the data, using the character string “Volume” which is the tag name of the selected data.

[0108] As described above, the receiving unit 11 receives the setting information, and the generating unit 12 determines the attribute indicating the purpose of the data based on the setting information. Thus, the function of the management side corresponding to the purpose of the data is determined, so when the user uses the function of the management support device 10, it is not necessary to select the target data from the large amount of data processed by the management support device 10. Therefore, the burden of the setting operation on the management system 100 can be reduced.

[0109] In addition, the generating unit 12 determines which of the multiple attributes of the data possessed by the PLC 21 is a predetermined attribute. The multiple attributes include an alarm attribute for making a report based on the data, a log record attribute for saving the history of the data, and a data group attribute for displaying multiple data sets in a centralized manner. Therefore, the user of the management support device 10 can easily use the alarm function, the log record function, and the centralized display function of the data.

[0110] In addition, the generator 12 extracts attribute information indicating the attribute of the data possessed by the PLC 21 and the tag name for identifying the data from the tag included in the setting information 22, thereby determining the attribute of the data. Therefore, the setting information 22 set in the PLC 21 may simply include the tag name of the data and the attribute information indicating the management purpose thereof as a tag. Therefore, the setting of the setting information 22 of the PLC 21 becomes easy. In addition, the determination of the attribute performed by the generator 12 is reliably performed in a one-to-one correspondence with the tag name.

[0111] In addition, the generating unit 12 registers the management information 131 in the storage unit 13, and if a change in the setting information 22 received from the PLC 21 is detected, the management information 131 registered in the storage unit 13 is updated based on the changed setting information 22. Thus, even if the configuration of the control system 20 is changed due to the addition or removal of the PLC 21, the user does not need to perform settings on the management support device 10 corresponding to the change. Therefore, the burden of the setting work can be reduced.

[0112] As mentioned above, although embodiment of this invention was described, this invention is not limited to the said embodiment.

[0113] For example, the management support device 10 has the management screen 141, but the present invention is not limited thereto. The output unit 14 of the management support device 10 may send the management information to a UI terminal connected to the management support device 10 via a network and display the management information on the management screen 141 of the UI terminal.

[0114] In addition, an example in which the management information 131 includes a tag name for identifying data possessed by the PLC 21 is described. Usually, on the management side that manages the control system 20, the data of the PLC 21 is mostly processed using the tag name. Therefore, at least in the PLC 21, it is necessary to associate the tag name of the data with the address of the memory storing the data in advance. However, the setting information 22 may also associate the address of the data with the tag assigned to the data, and the tag name and the address may also be associated in the management information 131.

[0115] In addition, the functions of the management support device 10 can be realized by dedicated hardware or by a general computer system.

[0116] For example, the program P1 executed by the processor 41 is distributed by storing it in a non-temporary recording medium that can be read by a computer, and the program P1 is installed in a computer, thereby forming a device that executes the above-mentioned processing. As such a recording medium, for example, a floppy disk, a CD-ROM (Compact Disc Read-Only Memory), a DVD (Digital Versatile Disc), and an MO (Magneto-Optical Disc) can be considered.

[0117] Alternatively, the program P1 may be stored in advance in a disk device of a server device on a communication network such as the Internet, and may be superimposed on a carrier wave and downloaded to a computer, for example.

[0118] Furthermore, the above-described processing can also be realized by transferring the program P1 via a communication network and starting execution of the program P1.

[0119] Furthermore, the above-described processing can also be realized by executing all or part of the program P1 on a server device, and by causing the computer to transmit and receive information related to the processing via a communication network and execute the program.

[0120] Furthermore, when the above functions are realized by sharing with the OS (Operating System) or when the above functions are realized by cooperation between the OS and the application, only the parts other than the OS may be stored in a medium and distributed, or may be downloaded to a computer.

[0121] In addition, the method of realizing the functions of the management support device 10 is not limited to software, and a part or all of them may be realized by dedicated hardware including circuits.

[0122] The present invention can be set to various embodiments and variations without departing from the broad spirit and scope of the present invention. In addition, the above-mentioned embodiments are used to illustrate the present invention and are not intended to limit the scope of the present invention. That is, the scope of the present invention is not represented by the embodiments, but by the claims. Moreover, various variations implemented within the scope of the claims and within the scope of the disclosure equivalent thereto are deemed to fall within the scope of the present invention.

[0123] Industrial Applicability

[0124] The present invention is suitable for the management of a control system including a programmable controller.

[0125] Description of the label

[0126] 100 management system, 10 management support device, 11 receiving unit, 111 receiving instruction unit, 112 information receiving unit, 113 detection unit, 114 storage unit, 12 generation unit, 121 list generation unit, 122 attribute determination unit, 123 registration unit, 124 deletion unit, 13 storage unit, 131 management information, 14 output unit, 141 management screen, 142 to 144 objects, 20 control system, 21 PLC, 22 setting information, 23 equipment, 30 industrial network, 41 processor, 42 main storage unit, 43 auxiliary storage unit, 44 input unit, 45 output unit, 46 communication unit, 47 internal bus, P1 program.

Claims

1. A computer-readable non-temporary recording medium storing a management support program, the management support program causing a computer to function as a receiving unit and a generating unit, the computer being connected to a programmable controller, the computer generating management information displayed on a management screen for supporting management of the programmable controller, The receiving unit receives, from the programmable controller, setting information that is pre-set in the programmable controller in relation to data held by the programmable controller. The generating unit determines an attribute of the data based on the setting information, and generates the management information indicating the determined attribute, wherein the attribute of the data indicates a use of the data in management of the programmable controller. The receiving unit receives the setting information including a tag which is a character string assigned to the data. The generating unit determines the attribute by extracting attribute information which is a character string representing the attribute and a tag name which is a character string for identifying the data from the tag. The management information is information that shows the programmable controller, the control object of the programmable controller, the attributes of the data related to the control object, and the tag name in order of hierarchy.

2. The recording medium according to claim 1, wherein The generating unit determines which of a plurality of predetermined attributes the attribute of the data is. The plurality of attributes include an alarm attribute for issuing a report based on the data, a log record attribute for saving a history of the data, and a data group attribute for displaying the plurality of data sets together.

3. The recording medium according to claim 1 or 2, wherein: The generating unit registers the management information in a storage unit, and upon detecting a change in the setting information received from the programmable controller, updates the management information registered in the storage unit based on the changed setting information.

4. A management support device connected to a programmable controller, generating management information to be displayed on a management screen for supporting management of the programmable controller, The management assistance device has: a receiving unit that receives, from the programmable controller, setting information that is pre-set in the programmable controller in relation to data held by the programmable controller; and a generating unit that determines an attribute of the data based on the setting information and generates the management information indicating the determined attribute, wherein the attribute of the data indicates a use of the data in management of the programmable controller, The receiving unit receives the setting information including a tag which is a character string assigned to the data. The generating unit determines the attribute by extracting attribute information which is a character string representing the attribute and a tag name which is a character string for identifying the data from the tag. The management information is information that shows the programmable controller, the control object of the programmable controller, the attributes of the data related to the control object, and the tag name in order of hierarchy.

5. A management system comprising: Programmable controllers; and The management support device according to claim 4, which generates management information to be displayed on a management screen for supporting management of the programmable controller.

6. A management support method, the method being executed by a management support device connected to a programmable controller, the management support device generating management information to be displayed on a management screen for supporting management of the programmable controller, The management assistance method includes the following steps: The receiving unit of the management support device receives, from the programmable controller, setting information previously set in the programmable controller in relation to data possessed by the programmable controller; and The generation unit of the management support device determines the attribute of the data based on the setting information, and generates the management information indicating the determined attribute, wherein the attribute of the data indicates the use of the data in the management of the programmable controller. The receiving unit receives the setting information including a tag which is a character string assigned to the data. The generating unit determines the attribute by extracting attribute information which is a character string representing the attribute and a tag name which is a character string for identifying the data from the tag. The management information is information that shows the programmable controller, the control object of the programmable controller, the attributes of the data related to the control object, and the tag name in order of hierarchy.