JP5743510B2 - Preventive maintenance management system - Google Patents

Description

  The present invention manages hardware and software configuration information, develops preventive maintenance information including hardware and software correction information provided by a vendor for preventing failures, and displays the results of preventive maintenance. The present invention relates to a preventive maintenance management system to be managed.

  In recent years, the frequency of the release of correction information for hardware (firmware) and software, which is important for preventing accidents related to preventive maintenance services, early countermeasures in the event of failures, and shortening the time to resolve failures, is an important aspect of security measures. It has been on an increasing trend. In order to manage whether or not such correction information is applied, it is effective to manage with a system configuration (by an information processing apparatus) having a function for managing configuration information and a function for managing application results.

  Therefore, as a well-known technique related to such a system configuration, for example, in order to quickly and reliably and honestly perform preventive maintenance services for software of customer systems, it is burdened on the user by providing only unapplied correction information. "Preventive maintenance service management system and management method" (see Patent Document 1) that reduces the number of steps for selecting correction information to be corrected.

  In addition, in the preventive maintenance service for customer system software, only the appropriate information is provided to reduce the burden on the customer (manual man-hours for selecting correction information), and the application status of the customer system configuration information and correction information is managed by a database. In addition, there is a “preventive maintenance method (preventive maintenance system)” (see Patent Document 2) in which only correction information to be applied is automatically extracted and notified to the user.

JP 2003-85317 A JP 2005-99967 A

  According to the preventive maintenance technology disclosed in Patent Document 1 and Patent Document 2 described above (particularly Patent Document 2), management of configuration information of customer systems, optimal extraction of correction information, and management of application results of correction information However, since it does not have a method for confirming whether correction information needs to be applied or a support function related to it, the user can check the application status of the latest correction information for each customer system. Since it is necessary to grasp and select whether or not it should be applied, the number of man-hours for selecting correction information by the user increases under such usage conditions.

  Therefore, it is not possible to reduce the number of man-hours for selecting correction information that is borne by the user regardless of the usage status, and as a result, preventive maintenance information for preventing failures cannot be effectively deployed. There is a problem that the results of preventive maintenance cannot be managed properly.

  More specifically, for example, in the case of correction information such as replacing an application DLL, the user accesses the folder in which the application DLL is stored, compares the DLL update date and time with the DLL update date and time to be applied, and stores it. For example, if the DLL being used is older, it takes time to replace (update) it with the DLL of the correction information. Also, it is necessary to manually deal with correction information such as disabling services and executing commands, and there is the inconvenience that the user must deal with these tasks by the number of customer systems x applications. is there. Furthermore, if the environment of the customer system changes, the means for confirming whether or not correction information has been applied is different. Therefore, it is necessary to investigate how to confirm each time and determine whether or not to apply it. For this reason, such trouble is complicated.

  The present invention has been made to solve such problems, and its technical problem is to reduce the number of man-hours for selecting correction information to be borne by the user regardless of the use situation, and to prevent troubles in advance. An object of the present invention is to provide a preventive maintenance management system capable of effectively deploying preventive maintenance information and appropriately managing the results of preventive maintenance.

In order to solve the above technical problem, the preventive maintenance management system of the present invention manages release information of correction information on hardware and software for a predetermined number of customer systems connected by a network provided by a vendor as preventive maintenance information. A preventive maintenance management system based on a server function configuration, including a customer system information management unit for managing customer information and configuration information for each customer system, and batch import of software information for each customer system, and corresponding to each customer system Customer information and configuration information can be registered and searched on a case-by-case basis, and release information of correction information can be acquired from a vendor as preventive maintenance information, and the correction information can be registered for each customer system. Preventive maintenance that can be retrieved by storing the status of the application results of the correction information when applied A multicast controlling section, automatically and generates automatically or manually applied to the tool for confirmation and correction to be subjected to the correction information, modify confirms whether to apply the correction information by automated information management unit And.

  In addition, one embodiment of the preventive maintenance management system includes a file storage unit that stores a data file that is used to apply correction information and that is used for batch data acquisition of software information for each customer system. Features.

Furthermore, other embodiments of the above Ki予 proof maintenance system, the correction information management unit, for those online that is at least the network connections of the customer system, whether to apply the correction information in automatic It is characterized by automatically confirming.

In addition, in another embodiment of the preventive maintenance management system, the customer system information management unit stores a customer information management table that stores and manages customer information, and person-in-charge information that stores and manages person-in-charge information for the customer A management table; a configuration information management table that stores and manages configuration information; and a customer-specific correction information management table that stores and manages correction information for each customer. A data batch import unit that collects information collectively, a customer information registration unit that registers and stores customer information in the customer information management table, a customer information search unit that searches for customer information stored in the customer information management table, A correction information registration unit that stores and registers the release information of the correction information in a correction information management table provided in the correction information management unit; A correction information application result search unit that searches for customer-specific correction information stored in the customer-specific correction information management table indicating the status of the correction information application result when applied to each system, and the customer to apply the correction information It is configured to include, and the correction information request mail creation unit that creates an e-mail a message to the effect that a request to each system, the file storage unit, check and correction tools, as well as the script for acquiring the software information has stored the software for information acquisition script file with the file, modify information management unit, automatically check generate and modify and modify information management table for storing and managing the correction information, the check and correct for tool A tool automatic generation unit and an automatic confirmation check unit that performs automatic confirmation. The correction information registration unit in the preventive maintenance information control unit As a customer-specific modification information to be stored in register with another modification information management table, characterized in that it reflects the implementation results of a result of applying circumstances preventive maintenance.

According to the preventive maintenance management system of the present invention, in addition to managing the details of the correction information required when applying the correction information and the configuration information for each customer system, the correction information can be automatically or manually applied. A function to confirm whether or not to apply correction information automatically is created while automatically generating the confirmation / correction tool to be provided. As a result, the number of man-hours for selecting correction information to be borne by the user can be significantly reduced, preventive maintenance information for preventing failures can be effectively deployed, and the status of application results (preventive maintenance) Implementation results) can be managed appropriately.

1 is an overall schematic diagram including an operation environment of a preventive maintenance management system according to a first embodiment of the present invention. 1 is a sequence for explaining preventive maintenance management in the preventive maintenance management system shown in FIG. 1, including registration of customer information and registration of configuration information, and acquisition and registration of correction information distributed from a vendor to each customer system. It is the flowchart which showed the operation | movement process until it applies. It is the figure which illustrated the contents (table-format data) of the customer information management table with which the customer system information management part of the preventive maintenance management system shown in FIG. 1 is equipped. It is the figure which illustrated the structure content (data of a table format) of the structure information management table with which the customer system information management part of the preventive maintenance management system shown in FIG. 1 is equipped. It is the figure which illustrated the composition content (table format data) of the correction information management table with which the correction information management part of the preventive maintenance management system shown in FIG. 1 is equipped. It is the figure which illustrated the contents of composition of the preventive maintenance information management table used in the preventive maintenance information control part of the preventive maintenance management system shown in FIG. 1 (data of level information which is preventive maintenance information in the table format). The correction information stored in the correction information management table provided in the correction information management unit of the preventive maintenance management system shown in FIG. 1 is illustrated as a correction information registration screen displayed on the display screen of the attached display device. FIG. It is the figure which illustrated the structure content (data of a table format) of the correction information management table classified by customer with which the customer system information management part of the preventive maintenance management system shown in FIG. 1 is equipped. It is the figure which showed typically the flow of the correction information application process by the preventive maintenance information control part of the preventive maintenance management system shown in FIG.

  Hereinafter, the preventive maintenance management system of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is an overall schematic diagram including an operational environment of a preventive maintenance management system 100 according to a first embodiment of the present invention.

  The operational environment of the preventive maintenance management system 100 includes a predetermined number of customer systems 11 (including those connected to the network 10 and those not connected offline) via the network 10 such as the Internet, and client terminals. (Client PC) 12 is connected. Here, a plurality of customer systems 11 and client terminals (client PCs) 12 may be provided. In the following, in order to simplify the description, each customer system 11 will be described as having functional processing including a client terminal (client PC) 12.

The preventive maintenance management system 100 itself has a server function configuration that manages release information of correction information on hardware and software for each customer system 11 connected by a network 10 provided by a vendor as preventive maintenance information. Customer system information management unit 101 for managing customer information and configuration information for each 11 and batch acquisition of software information for each customer system 11, and registering customer information and configuration information corresponding to each customer system 11 in units of 1 As a preventive maintenance information, the release information of correction information can be acquired and registered from a vendor, and the status of the application result of correction information when the correction information is applied to each customer system 11 Preventive maintenance information control unit 102 that can be stored and searched, and is used for applying correction information Both the file storage unit 103 that stores data files to be used for all data capture software information for each customer system 11, a tool for checking and correcting to be subjected to the application of automatic or manual correction information automatically And a correction information management unit 104 that generates and confirms whether to apply correction information automatically .

  Incidentally, the preventive maintenance management system 100 described above, each customer system 11 and the client terminal (client PC) 12 are stored by a simplified CPU, main memory, auxiliary storage unit (HDD), etc., as is well known. The information processing apparatus includes an input / output device such as a device, a display device, and a keyboard / mouse.

  Among these, the customer system information management unit 101 stores a customer information management table 101a for storing and managing customer information, a person-in-charge information management table 101b for storing and managing person-in-charge information for customers, and configuration information. Configuration information management table 101c to be managed by the customer, and correction information management table 101d for each customer to store and manage the correction information (reflecting the implementation result of the preventive maintenance that is the status of the application result). Composed. The tables 101a to 101d here may be regarded as being stored and held in various databases (DB) in a table format.

  The preventive maintenance information control unit 102 collects software information (data) in a lump (also applicable to customer information capture) and stores and registers customer information in the customer information management table 101a. The customer information registration unit 102b, the customer information search unit 102c for searching the customer information stored in the customer information management table 101a, and the release information of the correction information stored in the correction information management table 104a provided in the correction information management unit 104. The correction information registration unit 102d to be registered, and the customer-specific correction information stored in the customer-specific correction information management table 101d indicating the status of the correction information application result when the correction information is applied to each customer system 11 are searched. The correction information application result search unit 102f that requests the customer system 11 to apply the correction information And the correction information request mail creation unit 102e to create an e-mail a message to the effect that, configured to include a. The correction information registration unit 102d displays the application result status (preventive maintenance execution result) as customer-specific correction information registered and stored in the customer-specific correction information management table 101d provided in the customer system information management unit 101. reflect.

File storage unit 103 stores the software for information acquisition script file 103b with a script file in order to get the check and correction tools 103a and software information,.

Correction information management unit 104, a modification information management table 104a for managing the correction information, and the confirmation and correction tool automatic generation unit 104b that automatically generates confirmation and modification tools 103a, out of the customer system 11 It is configured to include an automatic confirmation check unit 104c that automatically confirms whether or not correction information is automatically applied for at least an online state connected by the network 10.

  FIG. 2 is a sequence for explaining preventive maintenance management in the preventive maintenance management system 100, including registration of customer information and registration of configuration information. The customer system 11 acquires and registers correction information distributed from a vendor. It is the flowchart which showed the operation | movement process until it applies to every.

  As the contents of preventive maintenance management, first, the management department or the department in charge registers customer information in the preventive maintenance management system 100 on a case-by-case basis.

  FIG. 3 is a diagram illustrating the configuration contents (table format data) of the customer information management table 101 a provided in the customer system information management unit 101 of the preventive maintenance management system 100.

  The customer information here is defined by the details of the customer name, address, telephone number, E-mail address, person in charge on the table by the function of the customer information registration unit 102b of the preventive maintenance information control unit 102. Registered and managed. At the same time, the person-in-charge information is also registered and managed in the person-in-charge information management table 101b of the customer system information management unit 101. This customer information (including person-in-charge information) is registered by the user directly entering one item at a time on the display screen (customer information registration screen) of the display device attached to the management department or the department in charge (method) 1) Or, by using the data batch fetch function of the data batch fetch unit 102a provided in the preventive maintenance information control unit 102, as a data batch fetch data creation, the data batch fetch (method 2) is performed and fetched at one time and registered. It ’s good.

  Next, the management department or the department in charge registers the configuration information for each customer system 11 by hardware or software in the configuration information management table 101c of the preventive maintenance management system 100 on a case-by-case basis.

  FIG. 4 is a diagram illustrating the configuration content (table format data) of the configuration information management table 101c provided in the customer system information management unit 101 of the preventive maintenance management system 100.

  The configuration information here is defined by registering the details of items such as customer name, classification, product name, model / model number / version, manufacturing number, quantity on the table by the function of the preventive maintenance information control unit 102, It is something to manage. This configuration information is entered by the user directly on the display screen (configuration information registration screen) of the display device attached to the management department or the department in charge (configuration information registration screen), or the preventive maintenance information. Processing for downloading a script file to the customer system 11 using the software information acquisition script file 103b stored in the file storage unit 103 by the control unit 102, and registering an output file of the result executed by each customer system 11 in the system When performing the above, it is only necessary to perform batch data capture (method 2) and register using the data batch fetch function of the data batch fetch unit 102a. Incidentally, the software information acquisition script file 103b used in the method 2 is a tool that acquires software information displayed when an application AP is added or deleted, and outputs the software information in a list as a CSV file.

  That is, in the method 2, when the user executes the script file on the customer system 11 and the output file as a result is input to the system, the configuration information of the software information is transferred to the configuration information management table 101c by the data batch import process. be registered. The hardware configuration information for each customer system 11 is directly input on the display screen of the display device according to the method 1 and registered in the configuration information management table 101c.

  Furthermore, since hardware and software correction information is irregularly sent from the vendor to the management department, the management department obtains the sent correction information (step S201), and then is provided in the preventive maintenance management system 100. Registration of correction information is performed (step S202) by registering in the correction information management table 104a of the correction information management unit 104.

  FIG. 5 is a diagram illustrating the configuration content (table format data) of the correction information management table 104a provided in the correction information management unit 104 of the preventive maintenance management system 100.

  The correction information here is the product name, the correction version, and the correction date that indicates the date when the correction information is released on the table by the operation of the correction information registration unit 102d of the preventive maintenance information control unit 102. Correction information (classification, correction content, level as an element for determining whether to apply), correction method (type, method, confirmation for determining how to check and correct correction content -The contents of items such as correction tool names) are specifically defined, registered, and managed.

  Each of these pieces of information becomes original information when a confirmation / correction tool (script file or exe file) is automatically generated by the confirmation / correction tool automatic generation unit 104b. The level is automatically determined and set by a preventive maintenance information management table (level information table).

  FIG. 6 is a diagram illustrating the configuration content of the preventive maintenance information management table used in the preventive maintenance information control unit 102 of the preventive maintenance management system 100 (level information data as preventive maintenance information in a table format).

  The level information defines the criteria for determining the level according to the content of the correction information. As shown in FIG. 6, the specific criteria of the determination criteria shown for each classification of the correction information (hardware, software, network) are shown. The target level (L1 to 4) is determined according to the target content. For each level, “L1”, “l2”, “L3”, and “L4” are divided into four levels. For example, level “L1” may lead to “personal accidents / combustion, and emergency response is required” The “thing” and the level “L2” define the significance of the level degree such as “thing requested by the vendor (thing that needs to be dealt with)”.

  In the type and method of the correction method, the type of contents to be confirmed based on the correction information sent from the vendor and the method of confirmation / correction are defined in detail. As an example, there is a phenomenon in which the time of the log output by the software operating on the product A is also displayed with a shift of 8 hours because the time of the hardware product A is displayed with a shift of 8 hours. If it is described in the correction information that "It can be avoided by updating the hardware registry value", the type of correction method is "Registry", and the method is "Registry key: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ TimeZoneInformation" In this case, it is confirmed whether or not the value of “ActiveTimeBias” of “” is “fffffde4”, and if the value is different, the content is defined to be reset with the value. As another example, in the case of correction information indicating that the DLL file of the software product has been upgraded, “file” is defined as the type of correction method, and the storage location of the software product in which the DLL file is stored in the method The "date and time of update of the DLL file currently stored" is compared with the "date and time of update of the latest DLL file provided in the correction information", and the date and time of "the DLL file provided in the correction information" is compared. If the method is newer, there is a case where the confirmation method of overwriting (updating) with the file and the application method are described together.

  In any case, registration of the correction information (step S202) is performed on the display screen (correction information registration screen) of the display device provided by the user via the management department by the processing function of the correction information registration unit 102d.

  7 illustrates the correction information stored in the correction information management table 104a provided in the correction information management unit 104 of the preventive maintenance management system 100 as a correction information registration screen displayed on the display screen of the attached display device. FIG.

  The display of the correction information registration screen is controlled by the correction information registration unit 102d of the preventive maintenance information control unit 102.

  The items on the correction information registration screen are changed according to the type of confirmation / correction method. For example, in the case of a registry, keys, entries, values, and deletion are set, and in the case of files. , File path, target file name, update date and time, and screen configuration to set deletion.

  When the correction information is registered / updated from the screen, the confirmation / correction tool automatic generation unit 104b performs a process of automatically generating the confirmation / correction tool 103a from the correction information confirmation method (step S203), and the file storage unit 103 stores the correction information. The generated confirmation / correction tool 103a is stored. The name of the generated confirmation / correction tool 103a is registered in the confirmation / correction tool name in the correction method of the correction information management table 104a. The confirmation / correction tool 103a obtained here is downloaded from the correction information registration screen and used in the processing described later.

  The newly registered customer-specific correction information is stored and registered in the customer-specific correction information management table 101d by the correction information registration unit 102d.

  FIG. 8 is a diagram illustrating the configuration contents (table format data) of the customer-specific correction information management table 101 d provided in the customer system information management unit 101 of the preventive maintenance management system 100.

  Here, the customer-specific correction information is the product update history for each customer system 11 on the table by the function of the correction information registration unit 102d of the preventive maintenance information control unit 102, and the customer name, hardware (ware) or software (ware ) Classification, product name, model / model number / version, serial number, quantity, modification application version that manages the version to which the modification information is applied to the product, and the modification application date of the date to which the modification information is applied Defined, registered, and managed.

  Therefore, the target to which the correction information is applied based on the customer-specific correction information newly stored and registered in the customer-specific correction information management table 101d and the correction information stored and registered in the correction information management table 104a. The customer system 11 is extracted and correction information application processing is performed.

  FIG. 9 is a diagram schematically showing a flow of correction information application processing by the preventive maintenance information control unit 102 of the preventive maintenance management system 100.

  This correction information application process shows a procedure until the application of the correction information, and extracts a target product from the customer-specific correction information management table 101d based on the correction information for each registered product. In the case of the example shown in FIG. 9, the customer-specific correction information for the four A products, B products, C products, and D products as new product names on the customer-specific correction information management table 101d is newly added. This is the case when registered by company. Therefore, the A product, B product, C product, and D product of the target product name are extracted from the customer-specific correction information management table 101d, and the correction information management table for these A product, B product, C product, and D product is extracted. The modification version in 104a is compared with the modification application version indicating the modification information application status in the customer-specific modification information management table 101d. If the modification version is larger than the modification application version as a comparison result, the modification version is an application target. For example, the C product of the customer name A company uses up to version 01-10, and the latest correction information for each customer is 01-10, which means that it has already been applied. From such a comparison result, three pieces of correction information to be applied are A product, B product, and D product.

  Therefore, in the correction information application process, the automatic confirmation check unit 104c determines whether or not online connection with the customer system 11 is performed on the sequence shown in FIG. 2 (step S204). As a result of this determination, if online connection is established, the correction information is automatically applied to each customer system 11 related to the target A product, B product, and D product using the generated confirmation / correction tool 103a ( After performing the process of step S205), the process of updating the application completion flag (step S206) is performed. Thereafter, as in the case where the connection is not online (in the offline state), unapplied correction information is stored. The process proceeds to determination of presence / absence (step S207).

  For example, by using a confirmation / correction tool 103a for each target product (A product, B product, D product) generated by the preventive maintenance management system 100 by a user in the management department or the department in charge, to each customer system 11 corresponding to them. Apply correction information. When the confirmation / correction tool 103a is executed on the customer system 11, the automatic confirmation check unit 104c automatically determines whether correction information needs to be applied. Depending on the option of the confirmation / correction tool 103a, the necessity of applying the correction information is automatically confirmed and judged. If application is required (when connected to the customer system 11 online), the correction information can be applied. Is performed automatically. The application result of the correction information (the execution result of the preventive maintenance that is the situation) is updated for each customer system 11 to be described later (step S210), and is stored for each customer stored in the customer-specific correction information management table 101d. It is reflected in the data of correct correction information.

  Furthermore, if there is no unapplied correction information as a result of determining whether there is unapplied correction information (step S207), the process of updating the correction information history for each customer system 11 (step S210). After completing the operation process. If there is unapplied correction information, the correction information request mail creation unit 102f performs correction information application request mail generation and transmission (step S208) processing, and the user in the management department or the department in charge confirms / corrects the tool 103a. Is sent to the corresponding customer system 11 so as to manually apply the process of applying correction information (step S209), and then the process of updating the correction information history for each customer system 11 (step S210) is performed. The operation process ends. The update result of the correction information history at this time is also reflected in the customer-specific correction information stored in the customer-specific correction information management table 101d.

  Incidentally, in the correction information application request mail generation by the correction information request mail creation unit 102f, a message for requesting the corresponding customer system 11 to apply the correction information manually is created by e-mail. The mail format is automatically generated. Therefore, the user sets a destination for each corresponding customer system 11, and transmits a message to the effect that the correction information is applied using the confirmation / correction tool 103a.

  In the preventive maintenance management system 100 described above, hardware and software configuration information is registered in the customer system information management unit 101 in units of information for each customer system 11 by the operation of each part of the preventive maintenance information control unit 102, and the vendor Since the correction information of the hardware and software provided by is collected and held as needed, the customer information, the configuration information for each customer system 11 or the correction information can be managed appropriately.

  Further, if the administrator registers the correction information provided by the vendor in detail as the customer-specific correction information in the customer-specific correction information management table 101d of the customer system information management unit 101, the confirmation / management of the correction information management unit 104 is confirmed. Based on the correction information registered in the correction information management table 104a and the customer-specific correction information registered in the customer-specific correction information management table 101d by the processing function of the correction tool automatic generation unit 104b, each operating system (OS) The confirmation / correction tool 103a can be automatically generated. Based on the correction information provided by the vendor, the correction information for each customer, and the configuration information for each customer system 11, which correction information is currently applied is compared and verified for each customer system 11. When unapplied correction information is extracted, the customer system 11 is requested to apply the correction information manually, and when the confirmation / correction tool 103a is applied or provided for each customer system 11, the correction information Since it is automatically determined whether or not application is necessary (it can be applied in some cases), it is possible to reduce the number of man-hours for selecting whether or not to apply correction information burdened on the user.

  As described above, according to the preventive maintenance management system 100 according to the first embodiment, in addition to managing the details of the correction information required when applying the correction information and the configuration information for each customer system 11, the correction information is stored. Since the function that supports the method for confirming whether or not it is necessary to apply is constructed, it is possible to accurately confirm the correction information to be applied for each customer system 11, and as a result, it is burdened on the user. The number of man-hours for selecting corrective information is remarkably reduced, preventive maintenance information for preventing failures can be effectively deployed, and the status of application results (preventive maintenance results) can be managed appropriately. .

10 network 11 customer system 12 client terminal (client PC)
DESCRIPTION OF SYMBOLS 100 Preventive maintenance management system 101 Customer system information management part 101a Customer information management table 101b Person in charge information management table 101c Configuration information management table 101d Customer-specific correction information management table 102 Preventive maintenance information control part 102a Data batch acquisition part 102b Customer information registration part 102c Customer information search unit 102d Correction information registration unit 102e Correction information application result search unit 102f Correction information request mail creation unit 103 File storage unit 103a Confirmation / correction tool 103b Software information acquisition script file 104 Correction information management unit 104a Correction information management Table 104b Confirmation / correction tool automatic generation unit 104c Automatic confirmation check unit

Claims (4)

A preventive maintenance management system with a server function configuration that manages release information of correction information on hardware and software for a predetermined number of customer-connected network systems provided by a vendor as preventive maintenance information,
Including a customer system information management unit for managing customer information and configuration information for each customer system, and batch acquisition of software information for each customer system, one customer information and configuration information corresponding to each customer system It is possible to register and search by unit, and as the preventive maintenance information, the release information of the correction information can be acquired and registered from the vendor, and the correction information is applied to each customer system. The preventive maintenance information control unit that can store and search the status of the application result of the correction information and the confirmation / correction tool for automatic or manual application of the correction information are automatically generated and the correction is performed. A preventive maintenance management system comprising: a correction information management unit for confirming whether or not information is automatically applied .   The preventive maintenance management system according to claim 1, further comprising a file storage unit that stores a data file that is used to apply the correction information and that is used to collect data of the software information for each customer system. Preventive maintenance management system characterized by 3. The preventive maintenance management system according to claim 2 , wherein the correction information management unit determines whether to apply the correction information automatically for at least the network-connected online state of the customer systems. Preventive maintenance management system characterized by automatic confirmation. 4. The preventive maintenance management system according to claim 3, wherein the customer system information management unit stores and manages the customer information and a person information management table that stores and manages person information for the customer. A configuration information management table for storing and managing the configuration information, and a customer-specific correction information management table for storing and managing the correction information for each customer.
The preventive maintenance information control unit includes a data batch fetch unit that batch fetches the software information, a customer information registration unit that registers and stores the customer information in the customer information management table, and stores the customer information in the customer information management table A customer information search unit for searching the customer information, a correction information registration unit for storing and registering release information of the correction information in a correction information management table provided in the correction information management unit, and the correction information A correction information application result search unit that searches the customer-specific correction information stored in the customer-specific correction information management table indicating the status of the application result of correction information when applied to each customer system; and applying the correction information A correction information request mail creating unit that creates a message to request for each customer system by e-mail,
The file storage section may store before Ki確 sure-correction tools, as well as the software for information acquisition script file with the script file in order to get the pre-SL software information,
The correction information management unit, and the correction information management table for storing and managing the said correction information, and the confirmation and correction tool automatic generation unit for automatically generating the check and correction tools, the automatic confirmation And an automatic confirmation check unit for performing,
The correction information registration unit in the preventive maintenance information control unit reflects the execution result of preventive maintenance that is the status of the application result as the customer-specific correction information registered and stored in the customer-specific correction information management table. Preventive maintenance management system characterized by that.

Images