JP7211675B2 - Information management device and information management method - Google Patents

Description

The present invention relates to an information management apparatus and an information management method for managing information about a controller that monitors or controls equipment installed in a facility in a facility monitoring system.

Conventionally, facility monitoring comprising an engineering device that creates an operation file for monitoring or controlling one or more devices installed in a facility, and a plurality of controllers that download the operation file and monitor or control the device system is known. For example, Patent Literature 1 discloses a management system in which a management device has an engineering tool function for creating a control program to be executed (Patent Literature 1). In Patent Document 1, the "management apparatus" corresponds to the above "engineering apparatus", and the "control program" corresponds to the above "operation file". Moreover, in Patent Document 1, the "control device" corresponds to the above-mentioned "controller".
In a conventional facility monitoring system, information on the configuration of each controller held by each controller is managed on a controller-by-controller basis, and the engineering device uses an engineering tool based on the information on the configuration of each controller to Create an action file and let each controller download the created action file. When there is a change in the configuration of a certain controller, the administrator, etc., will change the information related to the configuration of each controller managed by the facility monitoring system in accordance with the change. conduct.
On the other hand, there is known a facility monitoring system in which a plurality of controllers in the facility monitoring system have a common configuration.

WO2016/157477

In a conventional facility monitoring system represented by the facility monitoring system disclosed in Patent Document 1, even when a plurality of controllers have a common configuration, each controller manages information about the common configuration. I am trying to Therefore, when a change occurs in the common configuration among a plurality of controllers, the administrator or the like has to change the information regarding the common configuration managed for each controller. As a result, there is a problem that work omissions or the like may occur, and information regarding configurations common to controllers, which should be managed with the same content in each controller, is not managed with the same content. For example, when an engineering device creates an operation file, the controller that downloaded the operation file does not operate correctly if the information related to the configuration common among the controllers is not managed with the same content in each controller. can create a problem.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. It is an object of the present invention to provide an information management device capable of centrally managing information on configurations common to a plurality of controllers in a system.

An information management device according to the present invention includes an engineering device that creates an operation file for monitoring or controlling one or more devices installed in a facility, and a plurality of engineering devices that download the operation file and monitor or control the devices. an information management device that manages information about a plurality of controllers in a facility monitoring system comprising a controller, wherein an engineering device receives common configuration information about a common configuration that the plurality of controllers have in common and common configuration information A change instruction for changing a common table defined in association with common configuration information for engineering, which is information converted into a usable data format and used when an engineering device creates an operation file. It comprises a change receiving section for receiving information and a table creation section for creating a post-change reflection common table in which changes are reflected in the common table based on the change instruction information received by the change receiving section.

According to the present invention, in a facility monitoring system having a configuration common to a plurality of controllers that download an operation file created by an engineering device and monitor or control devices in the facility, the present invention relates to a configuration common among the plurality of controllers. Information can be centrally managed.

1 is a diagram showing a configuration example of a facility monitoring system including an information management device according to Embodiment 1; FIG. FIG. 2 is a diagram for explaining an example of the contents of a table that defines information related to the configuration of controllers, managed by the information management device in Embodiment 1; FIG. 1 is a diagram illustrating a configuration example of an information management device according to Embodiment 1; FIG. FIG. 4 is a diagram for explaining an image of an example of a common table before change and a common table after change reflection when a table creation unit creates a change reflection common table in Embodiment 1; FIG. 10 is a diagram for explaining images of other examples of the common table before change and the common table after change reflection when the table creating unit creates the common table after change reflection in Embodiment 1; 4 is a flowchart for explaining an example of the operation of the information management device according to Embodiment 1; FIG. 2 is a diagram showing a configuration example of an information management device when history management is performed on a common table in Embodiment 1; 4 is a diagram showing an example of the contents of a common table stored in a storage unit 15 in an information management device configured to manage history of a common table; FIG. 4 is a flowchart for explaining the operation of the information management device when history management is performed on a common table in Embodiment 1;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
Embodiment 1.
The facility monitoring system according to Embodiment 1, which will be described below, includes a plurality of controllers 3, and the configuration of the plurality of controllers 3 is partly or wholly common among the plurality of controllers 3. It is assumed that Each controller 3 has a common configuration as a basic configuration, and can have a unique configuration by adding other configurations to the basic configuration. In the first embodiment, the "configuration" of the controller 3 refers to the specifications of the controller 3, and the "configuration" refers to the specific specifications of the controller 3, such as the name or model number of the controller 3. items (hereinafter referred to as “configuration items”).

FIG. 1 is a diagram showing a configuration example of a facility monitoring system including an information management device 1 according to Embodiment 1. As shown in FIG.
In Embodiment 1, the facility monitoring system is applied to, for example, a building monitoring system or a plant monitoring system. The facility monitoring system uses BACnet, for example, as a communication network.
The facility monitoring system includes an information management device 1, an engineering device 2, a controller 3, and equipment 4, as shown in FIG.
The information management device 1 is, for example, a server, and is connected to the engineering device 2 and the controller 3 via a network.
Controller 3 is connected to device 4 via a network. The devices 4 are sensors, lights, switches, motors, etc., and are installed in the facility.
In addition, although the facility monitoring system is provided with three controllers 3 in FIG. 1, this is only an example. The facility monitoring system may have two controllers 3 or four or more controllers 3 . The facility monitoring system only needs to have a plurality of controllers 3 . In the following description, the plurality of controllers 3 will also be simply referred to as "controllers 3".
Also, in FIG. 1, two devices 4 are connected to each controller 3, but this is only an example. One or more devices 4 may be connected to the controller 3 . In the following description, one or more devices 4 are also simply referred to as "devices 4".

The information management device 1 manages information regarding the controller 3 .
Specifically, the information management device 1 manages a table defining information about the configuration of the controller 3 . The information management device 1 stores a table (hereinafter referred to as a "common table") that defines information (hereinafter referred to as "common configuration information") regarding a configuration (hereinafter referred to as "common configuration") that the controllers 3 have in common. ) and a table that defines information about the configuration unique to the controller 3 .

Here, FIG. 2 is a diagram for explaining an example of the contents of a table that defines information related to the configuration of the controller 3, managed by the information management device 1 in the first embodiment. FIG. 2 is a diagram for explaining an example of the contents of the common table.
The common table contains common configuration information related to the common configuration held by the controller 3 and information obtained by converting the common configuration information into a data format that can be used by the engineering device 2 (hereinafter referred to as "engineering common configuration information"). , is information that is associated and defined.
As shown in FIG. 2, the common configuration information includes information on one or more configuration items such as device names.
Although not shown in FIG. 2, the common table is provided with information on the creation date and time of the common table.

The engineering common configuration information is used by the engineering device 2 when the engineering device 2 creates an operation file for operating the controller 3 .
The engineering device 2 creates an operation file based on the common configuration information, but since the engineering device 2 and the controller 3 have different hardware, the common configuration information cannot be used as it is when creating the operation file. Therefore, as shown in FIG. 2, in the common table, the common configuration information is defined in association with the common configuration information after being converted into the common configuration information for engineering. Create an action file with the configuration information. The information management device 1 converts the common configuration information into the engineering common configuration information.

As shown in FIG. 2, in the common table, a correspondence flag 201 can be assigned to each configuration item included in the engineering common configuration information. The correspondence flag 201 is information indicating that the configuration item is used when the operation file is created by the engineering device 2 among the configuration items included in the engineering common configuration information. After creating the operation file, the engineering device 2 assigns the correspondence flag 201 to the configuration item of the engineering common configuration information used when creating the operation file.
Also, although not shown in FIG. 2, when the operation file is created, the engineering device 2 stores the information on the created operation file as the configuration item of the engineering common configuration information used when creating the operation file. give it to The version of the action file can be identified from the information on the given action file.

The information management device 1 manages one common table for all controllers 3 in the facility monitoring system. For example, when there is a change in the common configuration in a certain controller 3, the information management device 1 creates a common table reflecting the change in the certain controller 3, and uses the contents of the created common table to convert the current common table to update.
Although the description is omitted here for the sake of simplicity, the information management apparatus 1 includes a table defining information on the configuration unique to the controller 3 in addition to the common table shown in FIG. is also managed.
The details of the configuration of the information management device 1 will be described later.

The engineering device 2 constructs a facility monitoring system. The engineering device 2 is executed by program processing using a CPU based on software.
When constructing a facility monitoring system, the engineering device 2 creates a JOB file recording management information such as configuration information of the controller 3 according to the BACnet standard. Then, the engineering device 2 creates the above-described operation file based on the created JOB file and downloads it to the corresponding controller 3 . Specifically, an administrator or the like creates an operation file from the engineering device 2 and downloads the created operation file to the controller 3 . Note that the engineering device 2 uses an engineering tool when creating an operation file. The engineering tool is appropriately installed in the engineering device 2 by an administrator or the like.
As described above, the engineering device 2 creates an operation file using the engineering common configuration information in the common table. The engineering device 2 associates and holds the operation file and the engineering common configuration information used when creating the operation file.

The controller 3 operates based on the operation file downloaded from the engineering device 2 and monitors or controls the equipment 4 .

FIG. 3 is a diagram showing a configuration example of the information management device 1 according to the first embodiment.
The information management apparatus 1 is executed by program processing using a CPU based on software.
The information management apparatus 1 includes a reception unit 11 , a changeability determination unit 12 , a table creation unit 13 , an output control unit 14 and a storage unit 15 .
The reception unit 11 receives various types of information. The accepting unit 11 includes a change accepting unit 111 .
The change receiving unit 111 receives change instruction information for changing the common table (see FIG. 2).

An administrator or the like can change the common configuration of the controller 3 as appropriate. Note that, in the first embodiment, changing the common configuration includes not only changing the contents of configuration items included in the common configuration, but also adding or deleting configuration items.
The administrator or the like inputs an instruction to change the common configuration of the controller 3 from the engineering device 2, for example. Specifically, for example, an administrator or the like first operates an input device (not shown) such as a mouse or a keyboard to input a configuration change screen display instruction to call the configuration change screen. In the engineering device 2, an operation reception unit (not shown) receives a configuration change screen display instruction input by an administrator or the like, and outputs the fact that the configuration change screen display instruction has been received to a display control unit (not shown). . The display control unit of the engineering device 2 causes the display unit (not shown) of the engineering device 2 to display the configuration change screen. For example, the display control unit of the engineering device 2 may refer to the information in the common table currently managed by the information management device 1 and display it on the display unit of the engineering device 2 . The administrator or the like operates the input device from the configuration change screen displayed by the display control unit of the engineering device 2 to input information about the common configuration of the controller 3 to be changed. The operation reception unit of the engineering device 2 receives the input information about the common configuration, and the transmission unit (not shown) of the engineering device 2 transmits the information about the common configuration received by the operation reception unit as change instruction information, Send to the information management device 1 .
The change receiving unit 111 of the information management device 1 receives change instruction information transmitted by the transmitting unit of the engineering device 2 .

Here, as an example, it is assumed that the administrator or the like inputs an instruction to change the common configuration of the controller 3 from the engineering device 2, and the change reception unit 111 receives the change instruction information transmitted from the engineering device 2. However, this is only an example. For example, the administrator or the like inputs a change instruction for the common configuration from the controller 3, the controller 3 transmits change instruction information to the information management apparatus 1, and the change reception unit 111 receives the change instruction transmitted from the controller 3. Information may be received.
Change acceptance unit 111 outputs the received change instruction information to changeability determination unit 12 and table creation unit 13 .

When the change receiving unit 111 receives the change instruction information, the changeability determination unit 12 determines that the change instruction information is included in the common table in the configuration items included in the common configuration information that are unchangeable ( hereinafter referred to as "unchangeable items"). Items that cannot be changed are set in advance by an administrator or the like. The administrator or the like sets configuration items that, when changed, cause problems in the settings or operations of the controller 3 as non-changeable items. For example, when the facility monitoring system is started up, if a character string is set as the data type permitted in the configuration item "device name", change instruction information for changing the data type of a certain controller 3 to numbers only. is transmitted, and the content of the "device name" in the common configuration information is changed. Then, for example, in the other controllers 3 that have downloaded the operation file created using the "device name", the data type permitted by the "device name" is only numbers. 3, it becomes impossible to set the "device name" with a character string. If the other controller 3 wants to set the "device name" using characters, the above change may cause inconvenience in the other controller 3 . Therefore, the administrator or the like sets configuration items which, if changed, cause problems in the settings or operations of the controller 3 as non-changeable items.
The change propriety determination unit 12 outputs to the table creation unit 13 information about the result of determination as to whether or not the change instruction information is change instruction information for changing an unchangeable item.

When the changeability determination unit 12 determines that the change instruction information is not change instruction information for changing the unchangeable item, the table creation unit 13, based on the change instruction information received by the change reception unit 111, A common table reflecting the indicated change (hereinafter referred to as "common table after change reflection") is created. Specifically, the table creating unit 13 converts the common configuration information of the common table currently stored in the storage unit 15 into the common configuration information reflecting the change instructed by the administrator or the like. to create
At this time, the data conversion unit 131 of the table creation unit 13 converts the common configuration information in the post-change reflection common table into a data format that can be used by the engineering device 2, creates engineering common configuration information, and Associate with common configuration information.
The table creation unit 13 replaces the created common table after change reflection with the common table stored in the storage unit 15 and updates the common table stored in the storage unit 15 .
When the table creating unit 13 creates a post-change reflection common table and stores the post-change reflection common table in the storage unit 15, the change notification unit of the output control unit 14 transmits information indicating that the common table has been changed. 141. The table creating unit 13 may add the information of the content of the common table after change reflection to the information indicating that the common table has been changed, and output the information to the change notifying unit 141 .

When the changeability determination unit 12 determines that the change instruction information is change instruction information for changing a non-changeable item, the table creation unit 13 does not create a post-change reflection common table.

Here, FIGS. 4 and 5 are for explaining an image of an example of a common table before change and a common table after change reflection when the table creation unit 13 creates the common table after change reflection in the first embodiment. is a diagram.

FIG. 4 shows, as an example, the common table before change (FIG. 4) when the change receiving unit 111 receives change instruction information for changing the content of the configuration item "serial number" included in the common configuration of the controller 3. 401 in FIG. 4) and an image of a post-change reflection common table (see 402 in FIG. 4) created by the table creating unit 13 in which the contents of “serial No.” are changed.

FIG. 5 shows, as an example, the common table before change ( FIG. 5 501 in FIG. 5) and an image of the post-change reflection common table (see 502 in FIG. 5) created by the table creating unit 13 to which the “serial No.” is added.

In the above description, it is assumed that the common table already exists, and the table creating unit 13 creates the post-change reflection common table in which the change based on the change instruction information is reflected in the already existing common table. But this is just one example. For example, the table creating unit 13 can create a new common table based on the change instruction information from a state in which no common table exists. In addition, when the facility monitoring system is started up, the administrator or the like shall create and store a common table based on the common configuration of the controllers 3 installed in the facility monitoring system. A common table may always exist.

The change notification unit 141 of the output control unit 14, when the table creation unit 13 creates a common table after the change is reflected, in other words, when information indicating that the common table has been changed is output from the table creation unit 13, Notification information indicating that the common table has been changed is output to the engineering device 2, for example. The change notification unit 141 may include information about the contents of the post-change reflection common table in the notification information.
In the engineering device 2, a receiving section (not shown) receives the notification information output from the change notification section 141 and outputs it to the display control section. The display control unit causes the display unit to display the content of the notification information. For example, an administrator or the like confirms the content of the notification information displayed on the display unit, and controls the controller 3 in the facility monitoring system so that the content of the common configuration defined in the post-change common table becomes common. Make configuration changes.

The storage unit 15 stores a common table (see FIG. 2).
Note that although the storage unit 15 is provided in the information management apparatus 1 in the first embodiment, this is merely an example. The storage unit 15 may be provided outside the information management device 1 at a location accessible by the information management device 1 , the engineering device 2 , and the controller 3 .

The operation of the information management device 1 according to Embodiment 1 will be described.
FIG. 6 is a flow chart for explaining an example of the operation of the information management device 1 according to the first embodiment.
Change accepting section 111 waits until it accepts change instruction information for changing the common table (“NO” in step ST601), and upon accepting the change instruction information (“YES” in step ST601), accepts The change instruction information received is output to the changeability determination unit 12 and the table creation unit 13 .

When the change receiving unit 111 receives the change instruction information in step ST601, the change permission determination unit 12 changes the change-impossible item among the configuration items included in the common configuration information in the common table according to the change instruction information. It is determined whether or not it is change instruction information for changing (step ST602).

In step ST602, when the changeability determination unit 12 determines that the change instruction information is change instruction information for changing an unchangeable item (“YES” in step ST602), the information management device 1 End the process. When the changeability determination unit 12 determines that the change instruction information is change instruction information for changing an unchangeable item, the process is terminated without creating a common table after the change is reflected. 1, when a change occurs in the common configuration in a certain controller 3, for example, by making the change, it is possible to prevent inconvenience from occurring in the other controllers 3. FIG.
When the changeability determination unit 12 determines that the change instruction information is change instruction information for changing an unchangeable item, the output control unit 14 receives the determination result and indicates that the accepted change is not allowed. information may be output to the engineering device 2, for example. The receiving unit of the engineering device 2 receives the received information indicating that the change is not allowed. indicate. By checking the display unit, the administrator or the like can understand that the instructed change of the common configuration of the controller 3 is impossible.

In step ST602, when changeability determination section 12 determines that the change instruction information is not change instruction information for changing an unchangeable item ("NO" in step ST602), table creation section 13 Based on the change instruction information received by the change receiving unit 111 in step ST601, a post-change reflection common table is created (step ST603).
After storing the common table after change reflection in the storage unit 15 , the table creation unit 13 outputs information indicating that the common table has been changed to the change notification unit 141 of the output control unit 14 .

When information indicating that the common table has been changed is output from table creating section 13 in step ST603, change notifying section 141 outputs notification information indicating that the common table has been changed (step ST604).

In this way, the information management device 1 manages one common table for the controller 3 in the facility monitoring system, and reflects the received change instruction information in the one common table. Create a common table.
Thereby, in the facility monitoring system, it is possible to centrally manage the information regarding the configuration common to the plurality of controllers.

In addition to the operations described above, the information management apparatus 1 receives, for example, an instruction to output information about a common table (hereinafter referred to as a “common table information output instruction”), and You can make it output information about the table. Specifically, the receiving unit 11 receives, for example, the common table information output instruction output from the engineering device 2 and outputs information to the effect that the common table information output instruction has been received to the output control unit 14 . For example, a manager or the like operates an input device from the engineering device 2 to input an instruction to output information about the common table. The operation reception unit of the engineering device 2 receives the instruction, and the transmission unit of the engineering device 2 transmits the common table information output instruction to the information management device 1 . The reception unit 11 of the information management device 1 receives the common table information output instruction transmitted from the engineering device 2 .
When the reception unit 11 receives the common table information output instruction, the output control unit 14 acquires information on the common table from the storage unit 15 and outputs the information to the engineering device 2, for example. The receiving unit of the engineering device 2 receives information about the common table, and the display control unit of the engineering device 2 causes the display unit of the engineering device 2 to display the information. A manager or the like can check the display unit and grasp the contents of the common table.

In the first embodiment described above, when there is a change in the common configuration between the controllers 3, the information management apparatus 1 creates a post-change reflection common table that reflects the change, and uses the contents of the post-change reflection common table. , the common table stored in the storage unit 15 is updated. In other words, the information management device 1 manages the latest common table for only one generation.
However, this is only an example, and the information management device 1 may manage the history of the common table. By allowing the information management device 1 to manage the history of the common table, the information management device 1 can, for example, use the common configuration currently held by the controller 3 or the operation file created most recently by the engineering device 2. can provide information that makes it possible to determine at what point in time it corresponds to the common configuration information for engineers. A specific description will be given below.

FIG. 7 is a diagram showing a configuration example of the information management device 1a when history management is performed on a common table in the first embodiment.
In FIG. 7, the same components as those of the information management apparatus 1 described with reference to FIG.
The information management apparatus 1a is different from the information management apparatus 1 described with reference to FIG. It differs in that it includes a unit 142 and an engineering-side determination result notification unit 143 and also includes a comparison unit 16 . The comparison section 16 includes a controller side information comparison section 161 and an engineering side information comparison section 162 .

The information management device 1a manages the history of the common table. Therefore, when the post-change reflection common table is created, the table creation unit 13 does not replace the post-change reflection common table with the common table stored in the storage unit 15, but stores the post-change reflection common table. The common table stored in the unit 15 is additionally stored.
FIG. 8 is a diagram showing an example of the contents of a common table stored in the storage unit 15 in the information management device 1a configured to manage the history of the common table.
In the information management device 1a, the storage unit 15 stores the common table in chronological order. For simplicity of explanation, the common table shown in FIG. 8 omits illustration of the information on the creation date and time of the common table, which is given.

The information management device 1a collects, for example, information about a common configuration (hereinafter referred to as "target common configuration information") currently possessed by a certain controller 3 (hereinafter referred to as "target controller") among the controllers 3 in the facility monitoring system. ), and the received target common configuration information and the common configuration information of the common table stored in the storage unit 15 can be compared. Then, the information management device 1a can output information about the result of comparing the target common configuration information and the common configuration information of the common table.

Specifically, the controller-side information receiving unit 112 receives the target common configuration information that the target controller currently has.
For example, an administrator or the like inputs an instruction to send the target common information from the engineering device 2 . Specifically, the administrator or the like operates the input device to input an instruction to transmit the target common information. When an instruction to send the target common information is input, the operation receiving unit of the engineering device 2 receives the instruction to send the target common information, and the extraction unit of the engineering device 2 extracts the target common information from the target controller. Then, the transmission unit of the engineering device 2 transmits the target common information extracted by the extraction unit to the information management device 1 .
The controller-side information reception unit 112 receives target common information transmitted from the engineering device 2, for example.
The controller-side information reception unit 112 outputs the received target common configuration information to the controller-side information comparison unit 161 of the comparison unit 16 .

When the controller-side information reception unit 112 outputs the target common configuration information, the controller-side information comparison unit 161 compares the received target common configuration information with the common table stored in the storage unit 15 .
For example, the controller-side information comparison unit 161 compares the common configuration information of each common table whose history is managed with the target common configuration information, and from the matched common configuration information, determines the operation file corresponding to the target common configuration information. Determine version. Note that the controller-side information comparison unit 161 may determine the version of the operation file corresponding to the target common configuration information from the engineering common configuration information associated with the target common configuration information. The common configuration information for engineers is provided with information about an operation file created using the common configuration information for engineers.

Further, for example, the controller-side information comparison unit 161 compares the common configuration information of each common table whose history is managed with the target common configuration information, and the common configuration information that matches the target common configuration information is defined. A common table (hereinafter referred to as a "matching common table") is identified, and common configuration information defined in the common tables before and after the matching common table in chronological order is determined. The controller-side information comparison unit 161 can also determine the difference between the common configuration information defined in the common table before and after the matching common table in chronological order and the target common configuration information.

Note that the controller-side information comparison unit 161 compares the target common configuration information and the common configuration information, and determines what kind of determination to make based on the target common configuration information output from the controller-side information reception unit 112. good. The target common configuration information output from the controller-side information reception unit 112 is provided with information that instructs the determination to be performed. When inputting the target common information, the administrator, etc., also inputs information that instructs the determination to be performed. The controller-side information receiving unit 112 adds information input by an administrator or the like, which instructs the determination to be performed, to the target common information, and outputs the information to the controller-side information comparing unit 161 .

The controller-side information comparison unit 161 compares information about the result of comparing the common configuration information in the common table with the target common configuration information (hereinafter referred to as "common configuration comparison result information") as the controller-side determination result of the output control unit 14a. Output to the notification unit 142 .
In the above example, the controller-side information comparison unit 161 compares the information about the version of the operation file corresponding to the target common configuration information, or the information about the difference between the common configuration information and the target common configuration information. As result information, it is output to the controller-side determination result notification unit 142 .

The controller-side determination result notification unit 142 outputs the common configuration comparison result information output from the controller-side information comparison unit 161 to the engineering device 2, for example. The receiving unit of the engineering device 2 receives the common configuration comparison result information, and the display control unit of the engineering device 2 causes the display unit of the engineering device 2 to display the common configuration comparison result information. For example, when information about the result of comparing the common configuration information of the common table and the target common configuration information is displayed as the common configuration comparison result information, the administrator or the like can confirm the current controller 3 by checking the display unit. It is possible to grasp the version of the action file downloaded to the .
Further, for example, when information about the difference between the common configuration information and the target common configuration information is displayed as the common configuration comparison result information, the administrator or the like can check the display section to see what the controller 3 currently has. It is possible to check the history of how the contents of the configuration items of the common configuration that are in use have changed.

Further, the information management device 1a receives, for example, common configuration information for engineers currently possessed by the engineering device 2 in the facility monitoring system (hereinafter referred to as "common configuration information for target engineers"), and The common configuration information can be compared with the engineering common configuration information in the common table stored in the storage unit 15 . The information management device 1a may accept the Kamifuo of the operation file currently held by the engineering device 2 as the common configuration information for the target engineer. Then, the information management device 1a can provide information about the result of comparing the common configuration information for the target engineer and the common configuration information for the engineer in the common table.

Specifically, the engineering-side information receiving unit 113 receives the common configuration information for the target engine that the engineering device 2 currently has.
For example, an administrator or the like inputs an instruction to send the common information for the target engineer from the engineering device 2 . Specifically, the administrator or the like operates the input device to input an instruction to transmit the common information for the target engineer. When an instruction to transmit the common information for the target engineer is input, the operation reception unit of the engineering device 2 receives the instruction to transmit the common information for the target engine, and the extraction unit of the engineering device 2 extracts the common information for the target engine. do. Then, the transmission unit of the engineering device 2 transmits the common information for the target engineer extracted by the extraction unit to the information management device 1 .
The engineering-side information reception unit 113 receives the target engineer common information transmitted from the engineering device 2, for example.
The engineering-side information reception unit 113 outputs the received common configuration information for the target engine to the engineering-side information comparison unit 162 of the comparison unit 16 .

When the engineering-side information receiving unit 113 outputs the common configuration information for the target engine, the engineering-side information comparing unit 162 compares the received common configuration information for the target engine with the common table stored in the storage unit 15. I do.
For example, the engineering-side information comparison unit 162 compares the common configuration information for the engine in each common table whose history is managed with the common configuration information for the target engine, and selects the common configuration information for the target engine from the matching common configuration information for the engine. Determine the version of the action file corresponding to the information.
Further, for example, the engineering-side information comparison unit 162 compares the engineering common configuration information in each common table whose history is managed with the target engine common configuration information, and compares the matching engineering common configuration information. determine the common configuration information that

Further, for example, the engineering-side information comparison unit 162 compares the common configuration information for the engine in each common table whose history is managed with the common configuration information for the target engine, and compares the common configuration information for the target engine. Identify the common table in which the common configuration information is defined (hereinafter referred to as "engineer matching common table"), and furthermore, the engineering common configuration defined in the common table immediately before the engine matching common table in chronological order A difference between the information and the common configuration information for the target engine is determined.

The engineering-side information comparison unit 162 outputs information (hereinafter referred to as "engineer common configuration comparison result information") regarding the result of comparing the common configuration information for engineers in the common table with the common configuration information for the target engine, to the output control unit. 14a to the engineering-side determination result notification unit 143.
In the above example, the engineering-side information comparison unit 162 may include information about the version of the operation file corresponding to the target engine common configuration information, common configuration information associated with the target engine common configuration information, or Information about the difference between the common configuration information for the target engine and the common configuration information for the target engine is output to the engineering-side determination result notification unit 143 as the common configuration comparison result information for the engineer.

The engineering-side information comparison unit 162 compares the target-engine common configuration information with the engine-use common configuration information, and determines what kind of determination is to be made, based on the target-engine common configuration information output from the engineering-side information reception unit 113 . It can be judged from the configuration information. The common configuration information for the target engine output from the engineering-side information reception unit 113 is provided with information for instructing the determination to be performed. When inputting the common information for the target engine, the administrator or the like also inputs information for instructing the determination to be performed. The engineering-side information reception unit 113 adds information input by the administrator or the like and instructing the determination to be performed to the target engineer common information, and outputs the information to the engineering-side information comparison unit 162 .

The engineering-side determination result notification unit 143 outputs the engineering common configuration comparison result information output from the engineering-side information comparison unit 162 to the engineering device 2, for example. The receiving unit of the engineering device 2 receives the common configuration comparison result information, and the display control unit of the engineering device 2 causes the display unit of the engineering device 2 to display the common configuration comparison result information.
For example, when the information about the version of the operation file corresponding to the target engine common configuration information is displayed as the engineering common configuration comparison result information, the administrator or the like can check the display section to confirm the latest operation file. You can know the version.
Further, for example, when the common configuration information corresponding to the target engine common configuration information is displayed as the engine common configuration comparison result information, the administrator can confirm the common configuration corresponding to the latest version of the operation file. . Furthermore, by comparing the displayed common configuration with the common configuration currently possessed by a certain controller 3, the administrator or the like can, for example, download the latest operation file and use the intended function. First, it can be determined whether or not the common configuration of the controller 3 needs to be upgraded.
Further, for example, when information about the difference between the common configuration information for the engineer and the common configuration information for the target engine is displayed as the common configuration comparison result information for the engineer, the administrator or the like can confirm the latest information by checking the display unit. It is possible to check the changes between other operation files, such as what items were changed when the version was upgraded to the operation file of .

Further, the information management device 1a receives a history display instruction to display the information of the common table whose history is managed, acquires the information of the common table from the storage unit 15 based on the received history display instruction, and outputs the information. can also Specifically, for example, a manager or the like operates an input device from the engineering device 2 to input the history display instruction. Note that the administrator or the like may specify a target period for history display. The reception unit 11 a of the information management device 1 a receives the history display instruction, and the output control unit 14 a acquires the information of the common table from the storage unit 15 and outputs the information of the common table to the engineering device 2 .
The receiving unit of the engineering device 2 receives the information of the common table output by the output control unit 14a, and the display control unit of the engineering device 2 causes the display unit of the engineering device 2 to display the information of the common table. By checking the display unit, the administrator or the like can check, for example, the process of changing the configuration information of the controller 3 in the development stage.
The engineering device 2 may create the same action file for different common configurations. That is, in the common table, information about the same operation file may be given to different common configuration information for engineers. In this case, the administrator or the like may not be able to grasp the history of the changed common configuration by referring to the information about the operation file. Therefore, for example, the administrator designates a period during which the common configuration of the controller 3 was frequently changed during the development stage, and causes the common table for that period to be displayed. , you can check the detailed change history.

In this way, the information management device 1a can also manage the history of the common table. By managing the history of the common table, the information management device 1 compares the common configuration currently possessed by the controller 3 or the common configuration for engineering possessed by the engineering device 2 with the history-managed common table. can do. Then, the information management device 1 can output various information such as at what point in time the common configuration of the current controller 3 corresponds to the engineering common configuration information.

FIG. 9 is a flow chart for explaining the operation of the information management device 1a when history management is performed on the common table in the first embodiment.
The information management device 1a also performs the operations shown in the flowchart of FIG. 6 in addition to the operations described below with reference to FIG. Since the operation shown in the flowchart of FIG. 6 has already been described, redundant description will be omitted.

Controller-side information receiving section 112 determines whether or not the target common configuration information currently possessed by the target controller has been received (step ST901).
In step ST901, when controller-side information reception section 112 receives target common configuration information (“YES” in step ST901), controller-side information reception section 112 compares the received target common configuration information with controller-side information comparison. Output to the unit 161 .

When the target common configuration information is output from the controller side information reception unit 112 in step ST901, the controller side information comparison unit 161 compares the received target common configuration information with the common table stored in the storage unit 15. (step ST903).
The controller side information comparison section 161 outputs the common configuration comparison result information to the controller side determination result notification section 142 .

The controller-side determination result notification unit 142 outputs the common configuration comparison result information output from the controller-side information comparison unit 161 in step ST903, for example, to the engineering device 2 (step ST903).

On the other hand, in step ST901, if the controller-side information reception unit 112 has not received the target common configuration information (“NO” in step ST901), the engineering-side information reception unit 113 is It is determined whether or not the common configuration information for the target engine has been received (step ST904).

In step ST904, if the engineering-side information receiving section 113 has not received the common configuration information for the target engine ("NO" in step ST904), the process returns to step ST901.

In step ST904, when the engineering-side information reception unit 113 receives the target engine common configuration information (“YES” in step ST904), the engineering-side information reception unit 113 accepts the received target engine common configuration information as It is output to the engineering side information comparing section 162 .

When the engineering-side information receiving unit 113 outputs the common configuration information for the target engine in step ST904, the engineering-side information comparing unit 162 compares the received common configuration information for the target engine with the common configuration information stored in the storage unit 15. A comparison with the table is performed (step ST905).
The engineering side information comparison section 162 outputs the engineering common configuration comparison result information to the engineering side determination result notification section 143 .

The engineering-side determination result notification unit 143 outputs the engineering common configuration comparison result information output from the engineering-side information comparison unit 162 in step ST905, for example, to the engineering device 2 (step ST906).

Thus, the information management device 1a can manage the history of the common table. By managing the history of the common table, the information management device 1a can combine the history-managed common table with the common configuration information currently held by the controller 3, or the common configuration information for engineering currently held by the engineering device 2. A comparison with configuration information can be made. As a result, the information management device 1 determines that, for example, the common configuration currently held by the controller 3 or the operation file most recently created by the engineering device 2 does not correspond to the common configuration information for engineering at any point in time. It is possible to provide information that can specify whether or not.

In the first embodiment described above, the information management apparatuses 1 and 1a are provided with the changeability determination unit 12, but the information management apparatuses 1 and 1a do not necessarily include the changeability determination unit 12. .
Further, in the first embodiment described above, the information management devices 1 and 1a are assumed to be servers, but this is not the only option. good.

As described above, according to the first embodiment, common configuration information related to a common configuration shared by a plurality of controllers 3 and information obtained by converting the common configuration information into a data format that can be used by the engineering device 2 and a common table defined in association with common configuration information for engineering used when the engineering device 2 creates an operation file; and , based on the change instruction information received by the change receiving unit 111, a table creation unit 13 is provided for creating a post-change reflection common table in which changes are reflected in the common table. Therefore, in a facility monitoring system having a configuration common to a plurality of controllers 3 that download operation files created by the engineering device 2 and monitor or control devices in the facility, information about a configuration common to the plurality of controllers 3 can be centrally managed.

Further, according to the first embodiment, when the change receiving unit 111 receives change instruction information, the information management apparatuses 1 and 1a store the change instruction information in the common table as an item included in the common configuration information, or , change instruction information for changing unchangeable items among items included in the common configuration information for engineers. However, when it is determined that the change instruction information is change instruction information for changing an unchangeable item, the common table is not created based on the change instruction information. As a result, when a change occurs in the common configuration in a certain controller 3, for example, it is possible to prevent inconvenience from occurring in the other controllers 3 due to the change.

Further, according to the first embodiment, when the table creation unit 13 creates a post-change reflection common table that reflects a change, the information management devices 1 and 1a store common configuration information in the post-change reflection common table. , a data conversion unit 131 that converts the data into a data format that can be used by the engineering device 2, creates engineering common configuration information, and associates the common configuration information with the common configuration information. As a result, the common configuration information can be automatically converted into the engineering common configuration information, and can be centrally managed in association with the common configuration information.

It should be noted that, within the scope of the present invention, any component of the embodiment can be modified or any component of the embodiment can be omitted.

1, 1a Information management device 2 Engineering device 3 Controller 4 Device 11, 11a Reception unit 111 Change reception unit 112 Controller-side information reception unit 113 Engineering-side information reception unit 12 Modification propriety determination unit 13 Table creation unit 131 Data conversion unit 14, 14a Output control unit 141 Change notification unit 142 Controller-side determination result notification unit 143 Engineering-side determination result notification unit 15 Storage unit 16 Comparison unit 161 Controller-side information comparison unit 162 Engineering-side information comparison unit

Claims (7)

A facility monitoring system comprising an engineering device that creates an action file for monitoring or controlling one or more devices installed in a facility, and a plurality of controllers that download the action file and monitor or control the device. , an information management device that manages information about the plurality of controllers,
Common configuration information about a common configuration shared by the plurality of controllers, and information obtained by converting the common configuration information into a data format usable by the engineering device, and the engineering device receives the operation file. a change receiving unit that receives change instruction information for changing a common table defined in association with common configuration information for engineers used when creating the common configuration information;
An information management apparatus comprising: a table creation unit that creates a post-change reflection common table in which the change is reflected in the common table based on the change instruction information received by the change reception unit. 2. The information management device according to claim 1, further comprising: a change notification unit that outputs notification information indicating that the common table has been changed when the table creation unit creates the post-change reflection common table. When the change receiving unit receives the change instruction information, the change instruction information cannot be changed among the items included in the common configuration information or the items included in the engineering common configuration information in the common table. A changeability determination unit that determines whether the change instruction information is for changing an item,
The table creation unit
When the changeability determination unit determines that the change instruction information is change instruction information for changing the unchangeable item, the post-change reflection common table is not created based on the change instruction information. 3. The information management device according to claim 1 or 2, wherein the information management device is characterized by: When the table creating unit creates the post-change reflection common table, the common configuration information for engineering is converted into a data format usable by the engineering device in the post-change reflection common table. 4. The information management apparatus according to any one of claims 1 to 3, further comprising a data conversion unit that creates and associates the common configuration information with the common configuration information. a plurality of common tables exist in chronological order;
a controller-side information receiving unit that receives target common configuration information related to a common configuration currently owned by a target controller among the plurality of controllers;
a controller-side information comparing unit that compares the target common configuration information received by the controller-side information receiving unit with the common configuration information defined in the time-series common table;
5. The information management apparatus according to any one of claims 1 to 4, further comprising a controller-side determination result notification unit that transmits information about the comparison result performed by the controller-side information comparison unit. a plurality of common tables exist in chronological order;
an engineering-side information reception unit that receives common configuration information for a target engine currently held by the engineering device;
an engineering-side information comparing unit that compares the common configuration information for the target engine received by the engineering-side information receiving unit with the common configuration information for the engine defined in the time-series common table;
6. The information management device according to any one of claims 1 to 5, further comprising an engineering-side determination result notification unit that transmits information about the comparison result performed by the engineering-side information comparison unit. A facility monitoring system comprising an engineering device that creates an action file for monitoring or controlling one or more devices installed in a facility, and a plurality of controllers that download the action file and monitor or control the device. , an information management method for managing information about the plurality of controllers,
A change receiving unit is common configuration information about a common configuration shared by the plurality of controllers, and information obtained by converting the common configuration information into a data format usable by the engineering device, and the engineering device. a step of receiving change instruction information for changing the common configuration information for engineering used when creating the operation file, and the common table defined in association with the
an information management method, comprising: a table creating unit creating a post-change reflection common table in which the change is reflected in the common table based on the change instruction information received by the change receiving unit;

Images