Site management system

Abstract

To reduce unnecessary distribution to a site without requiring an update program, and determination of a manager for avoiding the unnecessary distribution, and reduce consumption of a communication resource and human loads, in distribution of the update program for a site.SOLUTION: A site management system includes a center server for managing a site, and a database for holding configuration information of the site. The center server extracts a site to which the update program should be distributed, on the basis of the configuration information held on the database, when receiving the update program of a computer program, and distributes the update program to the extracted site.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a site management system for managing a plurality of sites.

Background Art

[0002] There is known a site management system configured to manage a plurality of sites. Each of the sites to be managed is provided with various devices such as sensor devices, processing devices, measuring devices, control devices, communication devices, and computers, and is provided with a site server installed at the site for managing the various devices. The site server is managed by a center server connected via a network. The center server and the site server jointly grasp the operating status of the various devices to be managed, detect abnormalities in their operations, and execute control according to the detection results. The various devices in the site operate under the control of a computer program.

[0003] Update programs may be created for maintaining the quality, adding functions, ensuring security, and fixing defects of various devices, and installed on the various devices. In this specification, the term "update program" is used in the meaning that includes, in addition to application software, update programs for middleware, firmware, and operating system (OS) unless otherwise specified. In the conventional system, when an update program is created, the update program is distributed to and installed on various devices by the following procedure, for example.

[0004] (1) A service provider that has created an update program or received an update program from the developer of the device / software sends a notice of the update program to the site administrator. The site administrator contacts the service provider to permit the update. (2) The service provider registers the update program in the center server. (3) The center server distributes the update program to the site server related to the update permission. (4) The site administrator determines whether there is any device to which the distributed update program is to be applied. If there is, the administrator performs the installation operation of the update program on the target device. (5) The site administrator checks (post - health check) whether various devices are operating normally after applying the update program to the devices on which the update program has been installed. If there is an abnormal operation, an operation to restore the state before the start of the update operation (rollback) is executed, and the fact is reported to the center server.

[0005] However, in the conventional system, the service provider does not grasp information such as the number and type of devices at the site and the update status of the update program, and cannot determine whether there is a device to which the update program is to be applied at each site where there are multiple target devices. For this reason, regardless of the necessity of the update program at each of the multiple sites, the center server sends a notice of the update program to multiple sites all at once, or distributes the update program itself to multiple sites all at once. This means that communication resources are consumed uselessly. Also, for the site administrator, it is necessary to determine the necessity of the update program when there is a notice of the update program. After the update program is distributed to the site server, the site administrator etc. have to perform installation operations manually. Manual installation operations are difficult to avoid operation mistakes such as operation errors due to operation mistakes.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] The present invention has been made in view of the above problems, and in the distribution of update programs to sites, it reduces unnecessary distribution to sites that do not require the update program, the judgment of whether to apply the update by the site administrator, etc., and can reduce waste of communication resources and human load. The purpose is to provide a site management system.

Means for Solving the Problems

[0008] To solve the above problems, a site management system according to one aspect of the present invention includes a center server that manages sites and a database that holds configuration information of the sites. When the center server receives an update program for a computer program, it extracts the sites to which the update program should be distributed based on the configuration information held in the database, and distributes the update program to the extracted sites.

[0009] Further, a site management system according to another aspect of the present invention includes a center server that manages sites, a site server that manages management target devices arranged in the sites, and a database that holds configuration information of the sites. When the center server receives an update program for a computer program, it extracts the sites to which the update program should be distributed based on the configuration information held in the database, and distributes the update program to the extracted sites. The site server transmits the update program provided by the center server to the management target devices.

Effects of the Invention

[0010] According to the present invention, in the distribution of update programs to sites, it is possible to provide a site management system that reduces unnecessary distribution to sites that do not require the update program, the judgment of whether to apply the update by the site administrator, etc., and can reduce waste of communication resources and human load.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Modes for Carrying Out the Invention

[0012] Hereinafter, this embodiment will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may sometimes be denoted by the same reference numeral. Although the accompanying drawings show embodiments and implementation examples in accordance with the principles of the present disclosure, these are for the purpose of understanding the present disclosure and are not used to limit the interpretation of the present disclosure in any way. The description in this specification is merely a typical example and does not limit the scope of the claims or the application examples of the present disclosure in any sense.

[0013] In this embodiment, although the description is made in sufficient detail for those skilled in the art to implement the present disclosure, other implementations and forms are possible, and it is necessary to understand that configuration and structural changes and replacement of various elements can be made without departing from the scope and spirit of the technical idea of the present disclosure. Therefore, the following description should not be construed as being limited thereto.

[0014] [First Embodiment] Next, the site management system 1 according to the first embodiment will be described with reference to FIG. 1. This site management system 1 is composed of a center server 10 and site servers 20 (20-1, ··· 20-N), and manages the management target devices 30 (30-1, ··· 30-N) installed in each site S (S1, ··· SN). The site management system 1 also includes a site management database 11 and a site configuration database 12. In the illustrated example, N site servers 20 and N sets of management target devices 30 are shown, but the number of N is not limited to a specific number and may be 1 or more. The center server 10 and the site servers 20 are connected via a network NW and are configured to be able to transmit and receive various information, requests, and commands. The center server 10 manages the site servers 20 and also manages the management target devices 30 via the site servers 20. Hereinafter, when referring to a plurality of sites collectively, it is called "site S", and when referring to an individual site, it is called with a suffix such as "site S1, S2...". The same applies to the site servers 20. When referring to a plurality of site servers, it is called "site server 20", and when referring to an individual site server, it is called like "site server 20-1, 20-2...".

[0015] Site servers 20-1, ···, 20-N are arranged at respective sites S1, ···, SN, manage the devices to be managed 30 (30-1, ···, 30-N) arranged at sites S1, ···, SN, and are configured to transmit the update program provided from the center server 10 to the devices to be managed 30.

[0016] The center server 10 is connected to a site management database 11 and a site configuration database 12. The site management database 11 is a database that manages information regarding each site. The site configuration database 12 is a database that holds and manages site configuration information including the number, type, attributes, status, etc. of the devices to be managed 30 installed at respective sites S1, ···, SN. The center server 10 identifies the sites to which the created update program should be distributed according to the information stored in the site management database 11 and the site configuration database 12, and distributes the update program.

[0017] The devices to be managed 30 include, as an example, sensor devices, processing devices, measuring devices, control devices, computers, and the like. As an example, the device to be managed 30-N includes an HMI (Human Machine Interface) station 31, a distributed control system (DCS (Distributed Control System)) 32, a plant resource manager (PRM) 33, a general-purpose computer 34, a router 35, a switch 36, and various devices (sensors, valves, etc.) 37, 38. The illustrated example of the device to be managed 30-N is specifically shown as an example for understanding the device to be managed 30, and it goes without saying that it is not intended to limit the number, configuration, type, etc. of the device to be managed 30. The devices to be managed 30 other than the device to be managed 30-N may adopt another configuration according to the required specifications at respective sites S1 to SN-1.

[0018] The HMI station 31 is a computer that provides an interface for transmitting commands and information between humans and machines. The distributed control system 32 is a computer responsible for controlling various devices 37 arranged within site S. Also, the plant resource manager 33 is a computer responsible for adjusting the operating conditions of various devices 38 arranged within site S, fault diagnosis, etc. The general-purpose computer 34 is a computer for managing and recording various operations within site S. Further, the router 35 and the switch 36 are an example of communication devices for providing a wireless communication network within site S30-N.

[0019] Many of the various devices installed within site S operate under the control of a computer program, and that computer program needs to be appropriately updated by an update program for quality maintenance, function addition, defect correction, etc. When an update program is generated by a service provider, the update program is distributed from the service provider to the center server 10, and provided from the center server 10 to site S via the site server 20. At this time, the center server 10 refers to the data managed in the databases 11 and 12, determines (extracts) the site S that requires the update program, and distributes the update program only to the site server 20 where that site S is arranged.

[0020] Figure 2 shows an example of the data structure of information regarding sites under the management of this system 1, which is stored in the site management database 11. In the example of this Figure 2, as information for each site, information regarding the site ID, site name, and whether there is automatic update (yes / no) at each site is stored and managed. For a site where the "Automatic Update" item is set to "Yes", when an update program required for that site is generated, the installation work of the update program at that site can be automatically started without the operation of the administrator of the site server 20. For a site where the "Automatic Update" item is set to "No", even when an update program is generated, the distribution of the update program is not started, and the installation is executed based on the guidance of the generation of the update program and the judgment and installation work of the site administrator.

[0021] Figure 3 shows an example of a data structure diagram of information regarding the configuration of site S under the management of this system 1, which is stored in the site configuration database 12. In the example of this Figure 3, regarding various devices, the site ID of site S where the device is arranged, the name of the device, the name of the operating system (OS) installed on the device, the name of software (application, middleware, firmware, etc.), the name of the applied update program, and others are stored and managed. This is just an example, and as long as it includes device identification information for identifying devices included in site S, software identification information for identifying software included in any of the devices arranged in one site S, and applied update data regarding the applied updates regarding the update program. Also, in addition to or instead of the illustrated information, information such as the IP address, MAC address, and manufacturing lot number of various devices may be stored in the site configuration database 12.

[0022] The stored data in the site management database 11 is rewritten when a new site is newly established and when there is a change in whether there is automatic update at each site.

[0023] The stored data in the site configuration database 12 is rewritten when there are changes to various devices at each site S (such as new installation, expansion, replacement, repair, component replacement, maintenance, disposal, new introduction of computer programs, installation of update programs, etc.). The rewriting of the stored data in the site configuration database 12 is executed by storing the rewrite information in the site server 20 arranged at the site S and then transmitting the rewrite information to the center server 10. The rewrite operation may be manually executed by the administrator of the center server 10, or may be automatically executed by an automatic registration program stored in the center server 10 or a resource management computer (not shown) separate from the center server 10.

[0024] With reference to the flowchart of FIG. 4, an example of the procedure for distributing the update program by the present site management system 1 will be described. When an update program PG1 newly generated by a service provider or the like is registered in the center server 10 (step S11), the necessity of distributing the update program PG1 is sequentially determined for N sites S1 to SN (steps S12, S17, S18). First, it is determined based on the data in the site management database 11 whether the site Sn to be determined (n = 1 to N) is a site where automatic update of the update program is set (step S13).

[0025] For the site Sn, if the "Automatic Update" item in the site management database 11 is set to "Yes", the device / software to be updated according to the update program PG1 is searched for in the site configuration database 12 (step S14). If the corresponding data is found, it is determined that the device to be updated by the update program PG1 exists in the site Sn (Yes in step S15), and the update program PG1 is distributed to the site server 20 of the site Sn (step S16). Even if it is determined in steps S14 and S15 that the device to be updated exists in the site Sn, if another update program PG2 has already been applied to the device and it is determined that the current update program PG1 under judgment cannot coexist with it, it is possible to determine that the device to be updated does not exist and the site Sn is not extracted as a target for transmitting the update program.

[0026] In step S13, if it is determined that the site Sn is not a site with automatic update set (No), the update program is not distributed to the site Sn (the site Sn is not extracted), and the procedure proceeds to step S17, and the above procedure is repeated for the next site (n = n + 1). In this case, the update program PG1 is distributed to the site Sn when permission for update is separately obtained by the site administrator. Also, in step S15, if it is determined that the site Sn has automatic update set but does not have a device to which the update to be applied according to the update program under judgment is applicable (No), similarly, the update program is not distributed to the site Sn, and the procedure proceeds to step S17, and the above procedure is repeated for the next site (n = n + 1).

[0027] As described above, according to the site management system 1 of this first embodiment, in the distribution of the update program to the site, it is possible to provide a site management system that can reduce unnecessary distribution of the update program to sites where the update program is not required, as well as the administrator's judgment to avoid it, and can reduce waste of communication resources and human load.

[0028] [Second Embodiment] Next, the site management system of the second embodiment will be described with reference to the configuration diagram of FIG. 5 and the data structure diagram of FIG. 6. The basic configuration of the site management system 1 of this second embodiment differs from that of the system of the first embodiment in that a new database is added. In FIG. 5, the same components as those in the first embodiment (FIG. 1) are denoted by the same reference numerals as in FIG. 1, and thus redundant descriptions will be omitted below.

[0029] As shown in FIG. 5, the site management system 1 of the second embodiment includes, in addition to the site management database 11 and the site configuration database 12, an update progress database 13. The update progress database 13 is a database that manages information on what stage the update progress of the update program is in and information on completion / failure of the update, etc., in the process from the generation to the distribution of the update program. By providing the update progress database 13 in this second embodiment, various situations after the reception of the update program can be grasped by the center server 10 and used for the management of the site S after the update program is distributed.

[0030] FIG. 6 shows an example of the data structure of the information on the update status of the update program stored in this update progress database 13. This data structure of FIG. 6 shows the update status of the update program for one site, and for each of a plurality of sites, data like that in FIG. 6 can be stored individually. In the example of FIG. 6, it includes an ID (update device / software ID) for specifying the device or software to be updated, the name of the update program, the update status of the update program at each site, and the detailed data thereof. It goes without saying that this data structure is just an example and is not limited thereto.

[0031] In FIG. 6, the data of "update status" can include, for example, the following items. It is not necessary to include all of the following items, and items other than those listed below may be included. "Site Delivery in Progress", indicating that the update program is being delivered to the site server 20 "Site Delivery Completed", indicating that the delivery of the update program to the site server 20 has been completed "Pending Approval for Application", indicating that the center server 10 has sent an inquiry to the site server 20 regarding whether the application of the update program to the site is permitted and is waiting for a reply "Approval for Application Received", indicating that the site has replied to the center server 10 that the application of the update program is permitted and the reply has been received "Device Backup in Progress", indicating that the update program is being backed up on the device targeted for application "Update Applied", indicating that the update program has been delivered to and installed (updated) on the corresponding device "Restarting", indicating that the update program has been delivered to and installed on the corresponding device, and the device is restarting "Post - installation Health Check in Progress", indicating that the update program has been delivered to and installed on the corresponding device, and a "post - installation health check" is being executed to test whether the operation after installation is sound "Rollback in Progress", indicating that the update operation of the update program is abnormal, and as a result, the rollback operation has been started and is in progress "Rollback Completed", indicating that the update operation of the update program is abnormal, and as a result, the rollback operation has been started and completed

[0032] Next, referring to the flowchart of FIG. 7, an example of the procedure for registering information regarding the reception operation of the update program by the site management system 1 in this second embodiment and the subsequent update progress of the update progress status will be described. The operations from the registration of the update program on the center server 10 to its delivery to the site server 20 are performed in the same manner as in the first embodiment.

[0033] In the same manner as in the first embodiment, when the update program PG1 is distributed from the center server 10 (step S21) and received by the site server 20 (step S22), the site server 20 requests the site administrator for permission to apply the update program PG1 to the target device (step S23). When update permission is received in the target device (Yes in S24), distribution of the update program PG1 to the target device is started (step S25).

[0034] When distribution of the distribution program PG1 to the target device is started, a backup operation of the distribution program is executed in the target device (step S26), and update application is started in the target device (step S27). The progress status of the update such as receipt of permission, distribution of the update program, start of backup, and start of update application in the target device is notified to the center server 10 as appropriate (step S28), and the notification content is stored in the update progress database 13 as update progress status data. Note that the update program itself may be stored in the update progress database 13.

[0035] The procedure executed after completion of the update application of the update program will be described with reference to the flowchart of FIG. 8. When the update application of the update program to the target device is completed, a post-update sanity check is performed on the target device to which the update program has been applied (step S31).

[0036] As a result of the post-update sanity check, if the sanity of the post-update operation is recognized and the update operation is recognized as successful (Yes in step S32), an update completion notification notifying the update completion is transmitted to the center server 10 (step S35). On the other hand, if an abnormality is recognized in the post-update operation and the update operation is recognized as failed (No in step S32), a rollback operation for restoring the state before the start of the update operation is started (step S33), and when the state before the start of the update operation is restored, the rollback operation is completed (step S34).

[0037] Information on the progress and results of the post - integrity check and the progress of the rollback operation is also notified to the center server 10 as data on the update progress status and stored in the update progress database 13 (steps S36, S37).

[0038] Referring to FIG. 9, the detailed procedures of the post - integrity check and the details of the update of the update progress database 13 related to the post - integrity check will be described. In the post - integrity check, first, data collection and confirmation regarding the update program for which the update application has been completed are performed (step S41). It is confirmed whether there is an error in the collected and confirmed data (step S42). If there is no error, the process proceeds to step S43. If an error is found, the process moves to step S47, and it is recorded that an error has been found as the confirmation result of the post - integrity check, and an error log or the like, which is a record of the error, is recorded in the site server 20. Note that when the confirmation result at step S47 is recorded, the above - mentioned rollback operation is started.

[0039] When it is determined in step S42 that there is no error, in step S43, it is determined whether the collected data is normal. If it is normal, the process moves to step S44. If there is an abnormality, the process moves to step S47, and it is recorded that there is an abnormality in the collected data as the confirmation result of the post - integrity check, and data regarding the content and degree of the abnormality is recorded in the site server 20.

[0040] In step S44, it is determined whether the required time for step 41 is within the standard. If it is within the standard, the process moves to step S45. If it exceeds the standard, the process moves to step S47, and the time required for data collection is recorded as the post - integrity check result. In step S45, the performance of the update program (CPU usage rate, memory usage rate, network traffic, storage usage amount, etc.) and various characteristics obtained regarding the update program are checked. If the check result is good, the update of the update program is completed (step S46). If the check result is inappropriate, the process moves to step S47 and the result is recorded.

[0041] As described above, according to the site management system 1 of the second embodiment, data regarding the post-soundness check after the distribution of the update program and the progress of the rollback operation is stored in the update progress database 13 as data indicating the update progress status. The update progress status data stored in this update progress database 13 can be referred to when investigating the cause when the application of the update program fails, or when correcting the problem location of the device and the problem location of the update program and redistributing the update program. Thereby, in the distribution of the update program to the site, it becomes possible to quickly grasp the update status of the update program and execute the update operation quickly and accurately. Further, when the application of the update program fails, detailed information at the time of failure is stored in the update progress database, enabling the service provider to investigate the cause without waiting for the site administrator to investigate the cause and notify the investigation results, and as a result, reducing the time and human load.

[0042] Note that the present invention is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail for easy understanding of the present invention and are not necessarily limited to those having all the configurations described. Also, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, for a part of the configuration of each embodiment, it is possible to add, delete, or replace other configurations. For example, in the above-described embodiment, a system having a center server and a site server has been exemplarily described, but it is also possible to directly manage the devices at the site by the center server and omit the site server.

Explanation of Reference Numerals

[0043] 10…Center server, 11…Site management database, 12…Site configuration database, 13…Update progress database, 20…Site server, S…Site, 30…Devices to be managed, 31…HMI (Human Machine Interface) station, 32…Distributed control system (DCS (Distributed Control System)), 33…Plant resource manager (PRM), 34…General-purpose computer, 35…Router, 36…Switch, 37, 38…Various devices (sensors, valves, etc.).

Claims

1. A center server for managing sites, A database for storing the configuration information of the sites, Comprising: When the center server receives an update program of a computer program, based on the configuration information stored in the database, it extracts the sites to which the update program should be distributed, and distributes the update program to the extracted sites. The database includes a site configuration database that manages information related to the number and types of managed devices included in the site as the configuration information. The site configuration database Includes device identification information for identifying the managed devices arranged at the site, software identification information for identifying the software included in the site, and applied update data related to the applied updates regarding the update program at the site. The applied update data describes information listing the update programs that have been applied to the managed devices. The center server identifies, based on the applied update data, among the sites to which the update program should be distributed, those having the managed devices to which the update program should be applied, and distributes the update program only to the sites having the identified managed devices. A site management system, characterized by the above.

2. The database includes a site management database for managing information related to the site. The site management system according to claim 1, characterized by the above.

3. The site management database stores automatic update setting information regarding whether the site is a site that executes automatic update of the update program. The center server extracts the sites to which the update program should be distributed according to the automatic update setting information. The site management system according to claim 2.

4. A center server for managing sites, A site server for managing the managed devices arranged at the site, A database for storing the configuration information of the site, Comprising: When the center server receives an update program of a computer program, based on the configuration information stored in the database, it extracts the sites to which the update program should be distributed, and distributes the update program to the extracted sites. The site server transmits the update program provided by the center server to the device to be managed. The database includes, as the configuration information, a site configuration database that manages information on the number and types of devices to be managed included in the site. The site configuration database includes device identification information for identifying devices to be managed arranged at the site, software identification information for identifying software included in the site, and applied update data regarding applied updates related to the update program at the site. The applied update data describes information listing the update programs that have been applied to the devices to be managed. The center server identifies, based on the applied update data, among the sites to which the update program is to be distributed, those having the devices to which the update program is to be applied, and distributes the update program only to the sites having the identified devices to be managed. A site management system, characterized by the above.

5. The database includes a site management database that manages information regarding the site. The site management system according to claim 4, characterized by the above.

6. The site management database holds automatic update setting information regarding whether the site is a site that executes automatic update of the update program. The site management system according to claim 5, wherein the center server extracts sites to which the update program is to be distributed according to the automatic update setting information.

Images