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

Abstract

To provide an information management device capable of centrally managing information relating to a configuration common to a plurality of controllers.SOLUTION: The information management device includes: a change receiving unit 111 that receives change instruction information for changing a common table defining common configuration information on a common configuration that a plurality of controllers 3 have in common, and common configuration information for an engine, which is obtained by converting the common configuration information into a data format usable by an engineering device 2 and which is used by the engineering device 2 when creating an operation file, in association with each other; and a table creating unit 13 that creates a common table reflecting changes in the common table based on the change instruction information received by the change receiving unit 111.SELECTED DRAWING: Figure 3

Description

The present invention relates to an information management device 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 is provided with 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. The system is known. For example, Patent Document 1 discloses a management system having a function of an engineering tool for creating a control program to be executed by a management device (Patent Document 1). In Patent Document 1, the "management device" corresponds to the "engineering device" and the "control program" corresponds to the "operation file". Further, in Patent Document 1, the "control device" corresponds to the above-mentioned "controller".
In the conventional facility monitoring system, the information about the configuration of each controller that each controller has is managed for each controller, and the engineering device uses an engineering tool based on the information about the configuration of each controller. An operation file is created, and each controller is made to download the created operation file. When there is a change in the configuration of a certain controller, the administrator, etc., changes the information related to the configuration of each controller managed by the facility monitoring system in accordance with the change. Do.
On the other hand, there is known a facility monitoring system in which a plurality of controllers in a facility monitoring system have a common configuration among the plurality of controllers.

International Publication No. 2016/157477

In the 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, information on the common configuration is managed for each controller. I try to do it. Therefore, when a change occurs in a 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 on a configuration common to the controllers, which should be managed by the same controller, may not be managed by the same content. If the information about the configuration common to the controllers is not managed in the same content in each controller, for example, when the engineering device creates the operation file, the operation file that the controller that downloaded the operation file does not operate correctly. The problem of creating a file can occur.

The present invention has been made to solve the above-mentioned problems, and facility monitoring has a configuration in which a plurality of controllers that monitor or control equipment in a facility by downloading an operation file created by an engineering device are common. An object of the present invention is to provide an information management device capable of centrally managing information on a configuration common to a plurality of controllers in a system.

The 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 information management devices that download an operation file to monitor or control the devices. In a facility monitoring system equipped with the above controllers, an information management device that manages information about a plurality of controllers, and an engineering device obtains common configuration information regarding a common configuration and common configuration information that the multiple controllers have in common. Change instruction to change the common table defined in association with the information converted into a usable data format and the common configuration information for the engine used when the engineering device creates the operation file. It is equipped with a change reception unit that accepts information and a table creation unit that creates a common table after the changes are reflected in the common table based on the change instruction information received by the change reception unit.

According to the present invention, in a facility monitoring system having a configuration in which a plurality of controllers that monitor or control equipment in a facility by downloading an operation file created by an engineering device are common, the configuration is related to a configuration common to the plurality of controllers. Information can be centrally managed.

It is a figure which shows the configuration example of the facility monitoring system provided with the information management apparatus which concerns on Embodiment 1. FIG. It is a figure for demonstrating an example of the contents of the table which defines the information about the configuration which the controller has, which is managed by the information management apparatus in Embodiment 1. FIG. It is a figure which shows the configuration example of the information management apparatus which concerns on Embodiment 1. FIG. It is a figure for demonstrating the image of an example of the common table before change and the common table after change reflection when the table creation part creates the common table after change reflection in Embodiment 1. FIG. It is a figure for demonstrating the image of other examples of the common table before change and the common table after change reflection when the table creation part creates the common table after change reflection in Embodiment 1. FIG. It is a flowchart explaining an example of the operation of the information management apparatus which concerns on Embodiment 1. FIG. It is a figure which shows the configuration example of the information management apparatus in the case where the common table is history-managed in Embodiment 1. It is a figure which shows an example of the contents of the common table which a storage unit 15 stores in the information management apparatus which manages the history of a common table. It is a flowchart for demonstrating the operation of the information management apparatus when history management of a common table is made in Embodiment 1. FIG.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
Embodiment 1.
The facility monitoring system according to the first embodiment described below includes a plurality of controllers 3, and the configuration of the plurality of controllers 3 is common to a part or all of the configurations among the plurality of controllers 3. It is assumed that it is. Each controller 3 has a common configuration as a basic configuration, and can have its own configuration by adding another configuration 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" specifically represents the specifications of the controller 3, such as the name or model number of the controller 3. Items (hereinafter referred to as "components") are included.

FIG. 1 is a diagram showing a configuration example of a facility monitoring system including the information management device 1 according to the first embodiment.
In the first embodiment, the facility monitoring system is applied to, for example, a building monitoring system or a plant monitoring system. The facility monitoring system uses, for example, BACnet as the communication network.
As shown in FIG. 1, the facility monitoring system includes an information management device 1, an engineering device 2, a controller 3, and a device 4.
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.
The controller 3 is connected to the device 4 via a network. The device 4 is a sensor, a lighting, a switch, a motor, etc., and is installed in the facility.
In FIG. 1, the facility monitoring system is provided with three controllers 3, but this is only an example. The facility monitoring system may include two controllers 3 or may include four or more controllers 3. The facility monitoring system may be provided with a plurality of controllers 3. In the following description, the plurality of controllers 3 will also be simply referred to as "controller 3".
Further, in FIG. 1, it is assumed that 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 will be simply referred to as "device 4".

The information management device 1 manages information about the controller 3.
Specifically, the information management device 1 manages a table in which information regarding the configuration of the controller 3 is defined. The information management device 1 is referred to as a table (hereinafter referred to as "common table") in which information (hereinafter referred to as "common configuration information") relating to a configuration (hereinafter referred to as "common configuration") commonly possessed by the controller 3 is defined. ) And a table that defines information about the configuration that the controller 3 has independently.

Here, FIG. 2 is a diagram for explaining an example of the contents of the table in which the information regarding the configuration of the controller 3 managed by the information management device 1 is defined in the first embodiment. FIG. 2 is a diagram illustrating an example of the contents of the common table.
The common table contains common configuration information about 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 "common configuration information for engineering"). , 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 a device name.
Further, although the description is omitted in FIG. 2, information on the creation date and time of the common table is given to the common table.

The common configuration information for engineering 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 hardware of the engineering device 2 and the controller 3 are different, 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 converted into the common configuration information for the engine and then defined in association with the common configuration information, and the engineering device 2 is common for the engine. Create an operation file using the configuration information. The information management device 1 converts the common configuration information into the common configuration information for the engine.

As shown in FIG. 2, in the common table, the corresponding flag 201 may be added to each configuration item included in the engine common configuration information. Correspondence flag 201 is information indicating that among the configuration items included in the common configuration information for engineering, it is the configuration item used when the operation file is created by the engineering device 2. When the engineering device 2 creates the operation file, the corresponding flag 201 is added to the configuration items of the common configuration information for engineering used when creating the operation file.
Further, although not shown in FIG. 2, when the operation file is created, the engineering device 2 uses the information about the created operation file as a configuration item of the common configuration information for the engine used when creating the operation file. It is given to. The version of the operation file can be specified from the information about the given operation file.

The information management device 1 manages one common table for all the 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 that reflects the change in the certain controller 3, and the contents of the created common table are the current common table. To update.
Although the description is omitted here for the sake of brevity, the information management device 1 is a table in which information on the configuration unique to the controller 3 is defined in addition to the common table as 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 a program process using a CPU based on software.
When constructing a facility monitoring system, the engineering device 2 creates a JOB file that records management information such as configuration information of the controller 3 in accordance with the BACnet standard. Then, the engineering device 2 creates the above-mentioned operation file based on the created JOB file, and downloads it to the corresponding controller 3. Specifically, the administrator or the like creates an operation file from the engineering device 2, and downloads the created operation file to the controller 3. 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 common configuration information for the engine of the common table. The engineering device 2 holds the operation file in association with the common configuration information for engineering used when the operation file is created.

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

FIG. 3 is a diagram showing a configuration example of the information management device 1 according to the first embodiment.
The information management device 1 is executed by program processing using a CPU based on software.
The information management device 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 information. The reception unit 11 includes a change reception unit 111.
The change receiving unit 111 receives change instruction information for changing the common table (see FIG. 2).

The administrator or the like can appropriately change the common configuration of the controller 3. In the first embodiment, the change of the common configuration includes not only the change of the contents of the component items included in the common configuration but also the addition or deletion of the component items.
For example, the administrator or the like inputs an instruction to change the common configuration of the controller 3 from the engineering device 2. 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 and call up the configuration change screen. In the engineering device 2, the operation reception unit (not shown) receives the configuration change screen display instruction input by the administrator or the like, and outputs to the display control unit (not shown) that the configuration change screen display instruction has been received. .. 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 the information 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, and inputs information regarding the common configuration of the controller 3 to be changed. The operation reception unit of the engineering device 2 receives the input information on the common configuration, and the transmission unit (not shown) of the engineering device 2 uses the information on the common configuration received by the operation reception unit as change instruction information. It is transmitted to the information management device 1.
The change receiving unit 111 of the information management device 1 receives the change instruction information transmitted by the transmitting unit of the engineering device 2.

Here, as an example, the administrator or the like inputs a change instruction of the common configuration of the controller 3 from the engineering device 2, and the change receiving unit 111 receives the change instruction information transmitted from the engineering device 2. However, this is just one example. For example, the administrator or the like inputs a change instruction of the common configuration from the controller 3, the controller 3 transmits the change instruction information to the information management device 1, and the change reception unit 111 sends the change instruction from the controller 3. Information may be accepted.
The change reception unit 111 outputs the received change instruction information to the change possibility determination unit 12 and the table creation unit 13.

When the change acceptance unit 111 receives the change instruction information, the changeability determination unit 12 determines that the change instruction information cannot be changed among the configuration items included in the common configuration information in the common table. Hereinafter, it is determined whether or not the information is change instruction information for changing (referred to as “unchangeable item”). Items that cannot be changed are preset by the administrator or the like. The administrator or the like sets the configuration items that cause inconvenience in the setting or operation of the controller 3 as non-changeable items when the changes are made. For example, when a character string is set for the data type permitted in the configuration item "device name" when the facility monitoring system is started, change instruction information for changing the data type to only numbers for a certain controller 3. Is transmitted, and the content of the "device name" of the common configuration information is changed. Then, for example, in the other controller 3 that downloaded the operation file created by using the "device name", the data type permitted by the "device name" is only a number, and the other controller In step 3, it becomes impossible to set the "device name" in the character string. If you want to set the "device name" in characters on the other controller 3, the above change may cause inconvenience on the other controller 3. Therefore, the administrator or the like sets the configuration items that cause inconvenience in the setting or operation of the controller 3 as non-changeable items when the changes are made.
The changeability determination unit 12 outputs information regarding the determination result as to whether or not the change instruction information is the change instruction information for changing the non-changeable item to the table creation unit 13.

When the changeability determination unit 12 determines that the change instruction information is not the change instruction information for changing the non-changeable item, the table creation unit 13 is common based on the change instruction information received by the change reception unit 111. Create a common table (hereinafter referred to as "common table after change reflection") that reflects the specified changes in the table. Specifically, the table creation unit 13 uses the common configuration information of the common table currently stored in the storage unit 15 as the common configuration information reflecting the changes 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 into a data format that can be used by the engineering device 2 in the common table after the change is reflected, and creates the common configuration information for the engine. Correspond to common configuration information.
The table creation unit 13 replaces the created common table after reflecting the changes with the common table stored in the storage unit 15, and updates the common table stored in the storage unit 15.
When the table creation unit 13 creates a common table after reflecting the changes and stores the common table after reflecting the changes in the storage unit 15, the change notification unit of the output control unit 14 sends information indicating that the common table has been changed. Output to 141. The table creation unit 13 may add the information of the contents of the common table after the change is reflected to the information indicating that the common table has been changed and output the information to the change notification unit 141.

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

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

FIG. 4 shows, as an example, a common table before the change (FIG. 4) when the change receiving unit 111 receives the change instruction information for changing the content of the configuration item “serial No.” included in the common configuration of the controller 3. (Refer to 401) and the image of the common table (see 402 in FIG. 4) created by the table creation unit 13 after the content of the "serial number" is changed and reflected.

FIG. 5 shows, as an example, a common table before the change (FIG. 5) when the change receiving unit 111 receives the change instruction information for adding the “serial number” to the configuration items included in the common configuration of the controller 3. (See 501) and the image of the common table (see 502 in FIG. 5) created by the table creation unit 13 after the change is reflected with the addition of the “serial number”.

In the above description, the common table already exists, and the table creation unit 13 creates the common table after the change is reflected, which reflects the change based on the change instruction information for the existing common table. But this is just one example. For example, the table creation unit 13 can create a new common table based on the change instruction information from the state where the common table does not exist. In addition, when the facility monitoring system is started up, the administrator, etc. shall create and store a common table based on the common configuration of the controller 3 installed in the facility monitoring system. The common table may always exist.

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

The storage unit 15 stores a common table (see FIG. 2).
In the first embodiment, the storage unit 15 is provided in the information management device 1, but this is only an example. The storage unit 15 may be provided in a place outside the information management device 1 where the information management device 1, the engineering device 2, and the controller 3 can be referred to.

The operation of the information management device 1 according to the first embodiment will be described.
FIG. 6 is a flowchart illustrating an example of the operation of the information management device 1 according to the first embodiment.
The change receiving unit 111 waits until it receives the change instruction information for changing the common table (in the case of "NO" in step ST601), and when it receives the change instruction information (in the case of "YES" in step ST601), it accepts it. The change instruction information is output to the changeability determination unit 12 and the table creation unit 13.

When the change reception unit 111 receives the change instruction information in step ST601, the changeability determination unit 12 changes the non-changeable item among the configuration items included in the common configuration information in the common table. It is determined whether or not the change instruction information is to be used (step ST602).

In step ST602, when the changeability determination unit 12 determines that the change instruction information is the change instruction information for changing the non-changeable item (when “YES” in step ST602), the information management device 1 sets the information management device 1. End the process. When the changeability determination unit 12 determines that the change instruction information is the change instruction information for changing the non-changeable item, the information management device ends the process without creating the common table after the change is reflected. No. 1 can prevent inconvenience from occurring in another controller 3 when, for example, the change occurs in a common configuration in a certain controller 3.
When the changeability determination unit 12 determines that the change instruction information is the change instruction information for changing the non-changeable item, the output control unit 14 receives the determination result and the change received is impossible. Information may be output to, for example, the engineering device 2. The receiving unit of the engineering device 2 receives the information that the received change cannot be made. For example, the display control unit of the engineering device 2 sends a message such as "change not possible" to the display unit of the engineering device 2. indicate. By checking the display unit, the administrator or the like can grasp that the instructed change of the common configuration of the controller 3 is not possible.

In step ST602, when the changeability determination unit 12 determines that the change instruction information is not the change instruction information for changing the non-changeable item (when “NO” in step ST602), the table creation unit 13 determines. Based on the change instruction information received by the change receiving unit 111 in step ST601, a common table is created after the changes are reflected (step ST603).
When the table creation unit 13 stores the common table in the storage unit 15 after the change is reflected, 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 the change notification unit 141 outputs information indicating that the common table has been changed from the table creation unit 13 in step ST603, the change notification unit 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, reflects the received change instruction information on the one common table, and after the change is reflected. Create a common table.
As a result, in the facility monitoring system, it is possible to centrally manage information regarding a configuration common to a plurality of controllers.

In addition to the operations described above, the information management device 1 receives, for example, an instruction to output information about the common table (hereinafter referred to as "common table information output instruction"), and is stored in the storage unit 15. Information about the table can be output. Specifically, the reception 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, the administrator or the like operates the input device from the engineering device 2 to input an instruction to output information about the common table. The operation receiving unit of the engineering device 2 receives the instruction, and the transmitting 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 about the common table from the storage unit 15 and outputs it to, for example, the engineering device 2. The receiving unit of the engineering device 2 receives the information regarding the common table, and the display control unit of the engineering device 2 displays the information on the display unit of the engineering device 2. The administrator or the like can check the display unit and grasp the contents of the common table.

In the above-described first embodiment, when the common configuration between the controllers 3 is changed, the information management device 1 creates a common table after reflecting the change reflecting the change, and uses the contents of the common table after reflecting the change. , The common table stored in the storage unit 15 is updated. That is, 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 causing the information management device 1 to manage the history of the common table, the information management device 1 has, for example, a common configuration currently possessed by the controller 3 or an operation file most recently created by the engineering device 2. Can provide information that can determine at what point in time the common configuration information for engineering is associated with. Hereinafter, a specific description will be given.

FIG. 7 is a diagram showing a configuration example of the information management device 1a when the common table is history-managed in the first embodiment.
In FIG. 7, the same reference numerals are given to the same configurations as those of the information management device 1 described with reference to FIG. 1, and duplicate description will be omitted.
The information management device 1a is the information management device 1 described with reference to FIG. 1. The reception unit 11a includes a controller-side information reception unit 112 and an engineering-side information reception unit 113, and the output control unit 14a notifies the controller-side determination result. The difference is that the unit 142 and the engineering side determination result notification unit 143 are provided, and the comparison unit 16 is provided. The comparison unit 16 includes a controller-side information comparison unit 161 and an engineering-side information comparison unit 162.

The information management device 1a manages the history of the common table. Therefore, when the table creation unit 13 creates the common table after the change is reflected, the table creation unit 13 does not replace the common table after the change is reflected with the common table stored in the storage unit 15, but stores the common table after the change is reflected. It is added to the common table stored in the part 15 and stored.
FIG. 8 is a diagram showing an example of the contents of the common table stored by the storage unit 15 in the information management device 1a in which the history of the common table is managed.
In the information management device 1a, the storage unit 15 stores the common table in chronological order. For the sake of simplicity, in the common table shown in FIG. 8, the information on the creation date and time of the common table is not shown.

The information management device 1a is, for example, information on a common configuration currently possessed by a certain controller 3 (hereinafter referred to as “target controller”) among the controllers 3 in the facility monitoring system (hereinafter referred to as “target common configuration information”). ) Is received, and the received target common configuration information can be compared with the common configuration information of the common table stored in the storage unit 15. Then, the information management device 1a can output information regarding 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 currently held by the target controller.
For example, an administrator or the like inputs a transmission instruction of target common information from the engineering device 2. Specifically, the administrator or the like operates the input device to input the transmission instruction of the target common information. When the transmission instruction of the target common information is input, the operation reception unit of the engineering device 2 receives the transmission instruction of 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 receiving unit 112 receives, for example, the target common information transmitted from the engineering device 2.
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 target common configuration information is output from the controller side information receiving unit 112, 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 matching common configuration information, the operation file corresponding to the target common configuration information. Determine the version. The controller-side information comparison unit 161 may determine the version of the operation file corresponding to the target common configuration information from the engine common configuration information associated with the target common configuration information. Information about the operation file created by using the common configuration information for the engine is added to the common configuration information for the engine.

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 defines the common configuration information that matches the target common configuration information. The common table (hereinafter referred to as "match common table") is specified, and further, the common configuration information defined in the common table before and after the match common table is determined in time series. 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 time series and the target common configuration information.

Note that the controller-side information comparison unit 161 compares the target common configuration information with the common configuration information, and determines what kind of determination is made from the target common configuration information output from the controller-side information reception unit 112. Good. Information instructing the determination to be executed is added to the target common configuration information output from the controller side information receiving unit 112. When inputting the target common information, the administrator or the like also inputs the information instructing the determination to be executed. The controller-side information receiving unit 112 adds information input by the administrator or the like to instruct the determination to be executed to the target common information, and outputs the information to the controller-side information comparison unit 161.

The controller-side information comparison unit 161 uses the controller-side determination result of the output control unit 14a to obtain information regarding the result of comparing the common configuration information of the common table with the target common configuration information (hereinafter referred to as "common configuration comparison result information"). Output to the notification unit 142.
In the above example, the controller-side information comparison unit 161 compares the common configuration with information on the version of the operation file corresponding to the target common configuration information, information on the difference between the common configuration information and the target common configuration information, and the like. As the 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, for example, the engineering device 2. 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 displays the common configuration comparison result information on the display unit of the engineering device 2. For example, when the information related to 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 confirms the display unit to check the current controller 3 You can know the version of the operation file downloaded to.
Further, for example, when the information regarding 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 unit so that the controller 3 currently has it. You can check the history of how the contents of the component items of the common configuration have changed.

Further, the information management device 1a receives, for example, the common configuration information for the engine (hereinafter referred to as "common configuration information for the target engine") currently possessed by the engineering device 2 in the facility monitoring system, and is used for the received target engine. It is possible to compare the common configuration information with the engineering common configuration information of the common table stored in the storage unit 15. The information management device 1a may accept the upper cloth man of the operation file currently possessed by the engineering device 2 as the common configuration information for the target engine. Then, the information management device 1a can provide information regarding the result of comparing the common configuration information for the target engine and the common configuration information for the engine of the common table.

Specifically, the engineering side information receiving unit 113 receives the common configuration information for the target engine currently possessed by the engineering device 2.
For example, an administrator or the like inputs a transmission instruction of common information for the target engine from the engineering device 2. Specifically, the administrator or the like operates an input device to input a transmission instruction of common information for the target engine. When the transmission instruction of the common information for the target engine is input, the operation reception unit of the engineering device 2 receives the transmission instruction of the common information for the target engine, and the extraction unit of the engineering device 2 extracts the common information for the target engine. To do. Then, the transmission unit of the engineering device 2 transmits the common information for the target engine extracted by the extraction unit to the information management device 1.
The engineering side information receiving unit 113 receives, for example, the target engine common information transmitted from the engineering device 2.
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 comparison unit 162 outputs the target engine common configuration information from the engineering side information reception unit 113, the engineering side information comparison unit 162 compares the received target engine common configuration information with the common table stored in the storage unit 15. I do.
For example, the engineering side information comparison unit 162 compares the engine common configuration information of each common table whose history is managed with the target engine common configuration information, and from the matching engine common configuration information, the target engine common configuration Determine the version of the action file that corresponds to the information.
Further, for example, the engineering side information comparison unit 162 compares the engine common configuration information of each common table whose history is managed with the target engine common configuration information, and associates them with the matching engine common configuration information. Judge the common configuration information.

Further, for example, the engineering side information comparison unit 162 compares the common configuration information for the engine of each common table whose history is managed with the common configuration information for the target engine, and for the engine that matches the common configuration information for the target engine. Specify the common table in which the common configuration information is defined (hereinafter referred to as "engine match common table"), and further, the common configuration for the engine defined in the common table immediately before in the time series of the engine match common table. Determine the difference between the information and the common configuration information for the target engine.

The engineering side information comparison unit 162 outputs information regarding the result of comparing the engine common configuration information of the common table and the target engine common configuration information (hereinafter referred to as "engine common configuration comparison result information"). It is output to the engineering side determination result notification unit 143 of 14a.
In the above example, the engineering side information comparison unit 162 has information on the version of the operation file corresponding to the common configuration information for the target engine, the common configuration information associated with the common configuration information for the target engine, or the engine. Information regarding the difference between the common configuration information for the 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 engine.

The engineering side information comparison unit 162 compares the target engine common configuration information with the engine common configuration information, and determines what kind of determination is made by the target engine common configuration output from the engineering side information reception unit 113. It may be judged from the configuration information. Information for instructing the determination to be executed is added to the common configuration information for the target engine output from the engineering side information receiving unit 113. When inputting the common information for the target engine, the administrator or the like also inputs the information instructing the determination to be executed. The engineering side information receiving unit 113 adds information input by the administrator or the like to instruct the determination to be executed to the common information for the target engine, 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, for example, the engineering device 2. 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 displays the common configuration comparison result information on the display unit of the engineering device 2.
For example, when the information about the version of the operation file corresponding to the common configuration information for the target engine is displayed as the common configuration comparison result information for the engine, the administrator or the like can check the display unit to display 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 or the like can confirm the common configuration corresponding to the latest operation file version. .. Further, the administrator or the like can compare the displayed common configuration with the common configuration currently possessed by a certain controller 3, for example, to download the latest operation file and use the target function. In addition, it is possible to determine whether or not it is necessary to upgrade the common configuration of the controller 3.
Further, for example, when the information regarding the difference between the common configuration information for the engine and the common configuration information for the target engine is displayed as the common configuration comparison result information for the engine, the administrator or the like can check the display unit to obtain the latest information. You can check the changes with other operation files, such as what items have changed when you upgraded to the operation file of.

Further, the information management device 1a receives a history display instruction for displaying the information of the common table whose history is managed, and acquires and outputs the information of the common table from the storage unit 15 based on the received history display instruction. You can also do it. Specifically, for example, an administrator or the like operates an input device from the engineering device 2 to input the history display instruction. The administrator or the like may specify a target period for displaying the history. The reception unit 11a of the information management device 1a receives the history display instruction, the output control unit 14a 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 displays the information of the common table on the display unit of the engineering device 2. By checking the display unit, the administrator or the like can confirm, for example, the process of changing the configuration information of the controller 3 at the development stage.
The engineering device 2 may create the same operation file for different common configurations. That is, in the common table, information about the same operation file may be added to the common configuration information for different engines. 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 or the like specifies a period during which the common configuration of the controller 3 is frequently changed during the development stage, and displays the common table for the period to display the common configuration. You can check the detailed change history of.

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 existing controller 3 corresponds to the common configuration information for the engine.

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

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

When the target common configuration information is output from the controller side information receiving 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 unit 161 outputs the common configuration comparison result information 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 in step ST903 to, for example, the engineering device 2 (step ST903).

On the other hand, in step ST901, when the controller side information receiving unit 112 does not receive the target common configuration information (when “NO” in step ST901), the engineering side information receiving unit 113 is currently possessed by the engineering device 2. It is determined whether or not the common configuration information for the target engine has been accepted (step ST904).

In step ST904, when the engineering side information receiving unit 113 has not received the common configuration information for the target engine (when “NO” in step ST904), the process returns to step ST901.

In step ST904, when the engineering side information receiving unit 113 receives the target engine common configuration information (when “YES” in step ST904), the engineering side information receiving unit 113 receives the received target engine common configuration information. It is output to the engineering side information comparison unit 162.

When the engineering side information comparison unit 162 outputs the target engine common configuration information from the engineering side information reception unit 113 in step ST904, the engineering side information comparison unit 162 receives the target engine common configuration information and the common configuration information stored in the storage unit 15. Comparison with the table is performed (step ST905).
The engineering side information comparison unit 162 outputs the engineering common configuration comparison result information to the engineering side determination result notification unit 143.

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

In this way, 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 has the common table for which history is managed, the common configuration information currently possessed by the controller 3, or the common configuration information currently possessed by the engineering device 2 for engineering. It is possible to compare with the configuration information. As a result, in the information management device 1, for example, the common configuration currently possessed by the controller 3 or the operation file recently created by the engineering device 2 does not correspond to the common configuration information for the engine at any time. It is possible to provide information that can identify the file.

In the above-described first embodiment, the information management devices 1 and 1a are provided with the changeability determination unit 12, but the information management devices 1 and 1a are not required to include the changeability determination unit 12. ..
Further, in the above-described first embodiment, the information management devices 1 and 1a are assumed to be servers, but the present invention is not limited to this, and for example, the information management devices 1 and 1a may be provided in the engineering device 2. Good.

As described above, according to the first embodiment, the common configuration information regarding the common configuration commonly possessed by the plurality of controllers 3 and the information obtained by converting the common configuration information into a data format that can be used by the engineering device 2. And the change reception unit 111 that receives the change instruction information for changing the common configuration information for engineering used when the engineering device 2 creates the operation file, and the common table defined in association with the engine. , The table creation unit 13 for creating the common table after the change is reflected in the common table based on the change instruction information received by the change reception unit 111 is provided. Therefore, in a facility monitoring system having a configuration common to a plurality of controllers 3 that download an operation file created by the engineering device 2 to monitor or control equipment in the facility, information on a configuration common to the plurality of controllers 3. Can be centrally managed.

Further, according to the first embodiment, in the information management devices 1, 1a, when the change receiving unit 111 receives the change instruction information, the change instruction information is included in the common configuration information in the common table, or The table creation unit 13 includes a changeability determination unit 12 for determining whether or not the items included in the common configuration information for engineering are change instruction information for changing an unchangeable item, and the table creation unit 13 is a changeability determination unit 12. However, when it is determined that the change instruction information is the change instruction information for changing the non-changeable item, the common table based on the change instruction information is not created. As a result, when a change occurs in the common configuration in a certain controller 3, for example, it is possible to prevent an inconvenience from occurring in another controller 3 by making the change.

Further, according to the first embodiment, when the table creation unit 13 creates the common table after the change is reflected in the information management devices 1 and 1a, the common configuration information is provided in the common table after the change is reflected. , The engineering device 2 is converted into a usable data format to create common configuration information for engineering, and a data conversion unit 131 associated with the common configuration information is provided. As a result, the common configuration information can be automatically converted into the common configuration information for the engine, and can be centrally managed in association with the common configuration information.

In the present invention, within the scope of the invention, it is possible to modify any component of the embodiment or omit any component of the embodiment.

1,1a Information management device 2 Engineering device 3 Controller 4 Equipment 11, 11a Reception unit 111 Change reception unit 112 Controller side information reception unit 113 Engineering side information reception unit 12 Changeability judgment unit 13 Table creation unit 131 Data conversion unit 14, 14a Output control unit 141 Change notification unit 142 Controller side judgment result notification unit 143 Engineering side judgment 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 including 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. An information management device that manages information related to the plurality of controllers.
The common configuration information regarding the common configuration commonly possessed by the plurality of controllers and the information obtained by converting the common configuration information into a data format that can be used by the engineering device, and the engineering device converts the operation file. A change reception unit that accepts change instruction information for changing the common configuration information for engineering used when creating, and a common table defined in association with
An information management device including a table creation unit that creates a common table after the change is reflected in the common table based on the change instruction information received by the change reception unit. 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 a common table after reflecting the changes. 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 common configuration information for the engine in the common table. It is equipped with a changeability judgment unit that determines whether or not it is change instruction information 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 non-changeable item, it is determined that the common table after the change is reflected based on the change instruction information is not created. The information management device according to claim 1 or 2. When the table creation unit creates the common table after the change is reflected, the common configuration information is converted into a data format that can be used by the engineering apparatus in the common table after the change is reflected, and the common configuration information for the engine is used. The information management device according to any one of claims 1 to 3, which is provided with a data conversion unit associated with the common configuration information. Multiple said common tables exist in chronological order
A controller-side information receiving unit that receives target common configuration information regarding a common configuration currently possessed by the target controller among the plurality of controllers.
A controller-side information comparison unit that compares the target common configuration information received by the controller-side information reception unit with the common configuration information defined in the time-series common table.
The information management device according to any one of claims 1 to 4, further comprising a controller-side determination result notification unit for transmitting information regarding a comparison result performed by the controller-side information comparison unit. Multiple said common tables exist in chronological order
The engineering side information receiving unit that receives the common configuration information for the target engine currently held by the engineering device, and
An engineering side information comparison unit that compares the target engine common configuration information received by the engineering side information reception unit with the engineering common configuration information defined in the time-series common table.
The information management device according to any one of claims 1 to 5, further comprising an engineering-side determination result notification unit for transmitting information regarding a comparison result performed by the engineering-side information comparison unit. A facility monitoring system including 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. Is an information management method for managing information related to the plurality of controllers.
The change receiving unit is information on common configuration information regarding a common configuration commonly held by the plurality of controllers and information obtained by converting the common configuration information into a data format that can be used by the engineering apparatus, and the engineering apparatus. A step of receiving change instruction information for changing a common configuration information for engineering used when creating the operation file, and a common table defined in association with the operation file.
An information management method comprising a step of creating a common table after the change is reflected in the common table based on the change instruction information received by the change reception unit.

Images