JP4932188B2 - Maintenance management system, maintenance management method, and maintenance management program - Google Patents

Description

In the present invention, for example, a maintenance company makes a maintenance contract (maintenance execution permission contract) with each manufacturer or each OEM vendor (for example, a distributor) that is an object of OEM production. maintenance management system for managing the presence or absence in recent years of maintenance management way in conformity with the managed maintenance of performing maintenance and relates to the maintenance and management methods, and maintenance management program.

  With the progress of technology, many different devices such as computer devices and peripheral devices have become related to the management targets. For maintenance management of management targets, it is required to shorten the processing period when upgrading the version of an application and to deliver replacement parts. For this reason, various systems for managing maintenance of management targets have been proposed in order to improve the efficiency of maintenance operations.

  In the conventional example, for example, BIOS version management information is updated, for example, remote maintenance costs are settled at the time of contract conclusion in the case of an annual plan, and updated in the case of individual contracts for each work A maintenance system is known in which a charge is made each time work is performed (see, for example, Patent Document 1). For example, a worker support system is known in which, for example, parts number and quantity data are transmitted, inventory information is received by a portable terminal, and when an order is transmitted, the parts are delivered. (For example, refer to Patent Document 2).

JP 2002-23877 A JP 2002-222280 A

  By the way, in recent years, OEM production of producing one device (equipment) or system device from each part produced by a plurality of manufacturers has been actively performed, and OEMs are generally widely used also by vendors such as distributors. Has been done.

  Maintenance contractors have maintenance contracts and license contracts with OEM producers or OEM vendors (sellers, etc.) to expand the scope of management targets to related management targets and operate maintenance operations over a wide range. The system of doing is generalized.

  That is, for example, in factory production systems, hospital systems, home systems, security systems, etc., we have built a system to control the controlled devices and peripheral devices using computer equipment that is the center of control, During maintenance, the occurrence of failures in various devices may be confirmed through computer devices, for example. At that time, the maintenance contractor must first confirm whether or not the faulty device is a device for which a maintenance contract or license contract has been signed, and then the maintenance work is carried out after that. .

  In the conventional examples described in Patent Documents 1 and 2, there is no way to confirm whether or not the faulty device is a device that has a maintenance contract or license contract. It is very difficult, and it is necessary to perform a very troublesome procedure for the inside such as inquiring the inside of the maintenance company.

  That is, in the conventional example described in Patent Document 1, in the case of maintenance, when the remote maintenance cost is settled for an annual plan, it is billed collectively when the contract is concluded, and in the case of individual contracts for each work, each update work is performed. However, this is only to improve the efficiency of in-house operations, and from the viewpoint of efficiently managing and supporting maintenance of each device of OEM production and each device between OEM vendors. It is insufficient.

  In the conventional example described in Patent Document 2, the part number and the number of pieces of data are transmitted, the inventory information is received by the portable terminal, the order is transmitted, and the maintenance part is arranged. It is difficult to know whether or not each maintenance part has a maintenance contract. From the viewpoint of efficiently managing and supporting the maintenance of each equipment of OEM production and each equipment between OEM vendors. It is insufficient.

The present invention solves the above-mentioned problems of the conventional technology, allows maintenance personnel to quickly know whether the management target is a maintenance contract or a license contract, and has no maintenance contract or license contract. both possible and the maintenance management system to obtain the information needed to be managed by maintaining revealing the vendor location, maintenance method, and to provide a managed maintenance program, and an object.

In order to achieve the above object, the present invention sets various computer devices to which an identification key is added and their peripheral devices as management targets for maintenance, and manages the presence / absence of maintenance and the corresponding contents of each management target via a network. A maintenance management server comprising a CPU and a memory, and an application for setting a plurality of maintenance management functions executed on the CPU;
Notification that is a failure notification means for detecting the failure of one of the management targets and recognizing the failure content, and then transmitting the identification key of the management target and the failure content related to the failure occurrence to the maintenance management server System,
A maintenance worker terminal having a display screen that operates based on a request from the maintenance management server made via the network and requests a maintenance worker to repair a device to be managed in response to the occurrence of the failure. A maintenance management system,
The components of each managed, identification key, and advance and registered comprising device information management database information relating to sales vendor along with repair information, the device that is contracted as a target of the fault tolerance comprises the managed A contract information management database registered in advance together with the contents of the trouble that can be dealt with is provided alongside the maintenance management server via the network.

This maintenance management server uses an identification key recorded in the contract information management database as a function set by the application on the CPU as to whether or not the management target related to the fault is previously contracted as a fault countermeasure target. The contract information determination function for determining based on the presence / absence of a failure, and whether or not the management target is repairable when it is determined that the contract has been made as a target for the failure countermeasure is recorded in the contract information management database A failure response determination function for determining based on the maintenance contract information.

The requested if the respective determining function by the management target device is determined as serviceable contract a target device and, with respect to the maintenance terminal, the management object of repair by the maintenance worker previously registered fault condition in the device information management database as the information necessary for the repair as well as, identification key, maintenance procedures, or the repair request processing function of transmitting the maintenance part management information, the maintenance management server comprises Yes.
This maintenance management server further
Operates when the management object related to the failure is determined as a failure countermeasure target by the contract information determination function, and is stored in advance from the identification key and stores vendor information that is the shipping source of the management target A vendor search unit that searches the database and searches for managed vendors related to the failure;
If that could search for the vendor, the managed the assumption that the subject of the fault tolerance, vendor name of the managed based on the device name and identification key, maintenance contents registered in advance how certain set transmission, maintenance procedures, maintenance route, associated user information, and maintenance of parts management information, to the device information management and retrieval from the database the maintenance terminal and pre-instrumented parts management server via the network And a maintenance content specifying transmission section. (Claim 1)

Further, the repair, which is a countermeasure against the failure of the management target device, includes device replacement (claim 2).

Here, the above-described maintenance management server sends information on parts to be managed for repair, including device replacement, to the component management server installed in advance, information relating to the management target device that is the target of failure countermeasures, and A component information management function including a component delivery request function for transmitting and requesting a maintenance component management number, etc., and the component management server preliminarily equipped with an identification key for a maintenance component that operates and arranges in response to the component delivery request. It is good also as a structure provided with the function which searches from a database and transmits to the said maintenance management server (Claim 3) .

(Delete)

(Delete)

(Delete)

(Delete)

(Delete)

Moreover, the vendor database described above, other more conservative procedures for component management number and maintenance of the managed devices of the information to the management target device is recorded (claim 4).

The maintenance management server functions when the maintenance operator terminal reports that a repair as a countermeasure against the management target device has been executed, and sets the identification key of the management target device to a new one after the maintenance repair. It is good also as a structure provided with the information update part updated to a new identification key and preserve | saved as a next recognition object apparatus (Claim 5 ).

In addition, the maintenance worker terminal server receives from the maintenance worker the identification key of the management target device and the replacement maintenance component, and whether or not the replacement maintenance component is used, as a completion report of repair work that is a countermeasure against the failure of the management target device. It functions when it is input, and has a function of transmitting these to the maintenance management server. The maintenance management server also includes a management target device and a substitute maintenance component sent together with a report from the maintenance worker terminal server. An identification key confirmation function is provided for confirming whether or not each identification key matches the identification key sent from the component management server.
And when each identification key corresponds, it is good also as a structure provided with the function which registers the said work report to the work history management database equipped separately beforehand (Claim 6 ).

Further, the maintenance management server performs consistency check periodically for the contract information management database, the device information management database, and the vendor database, and performs consistency check for new additions and change items. It is good also as a structure provided with (Claim 7 ).

Here, the component management server described above receives at least information on the identification key of the device to be managed, and confirms whether the device or component corresponding to the identification key is in stock based on the recorded contents of the component information management database. A delivery arrangement processing unit that arranges delivery of the device and parts, and a delivery instruction recognition unit that recognizes an instruction result of delivery arrangement by the delivery arrangement processing unit and transmits the instruction result to the maintenance management server. It is good also as a structure (Claim 8 ).

(Delete)

(Delete)

(Delete)

In order to achieve the above object, a maintenance management method according to the present invention uses various computer devices to which an identification key is added and their peripheral devices as maintenance management targets, and indicates whether or not each management target has maintenance and the corresponding contents. A maintenance management server having a CPU and a memory to be managed via the CPU and an application for setting a plurality of maintenance management functions executed on the CPU, and detecting when a failure occurs in one of the management targets A notification system which is a failure notification means for transmitting to the maintenance management server the identification key of the management target related to the occurrence of the failure and the failure content after recognizing the failure content, and the maintenance management server formed via the network Display screen for requesting maintenance personnel to repair the managed device that is operated based on the request from the operator and that causes the failure In the maintenance management system and a maintenance terminal equipped with,
When a failure occurs in one device to be managed, the notification system as the failure notification means detects the failure, and the maintenance management server uses the detected failure content and identification key of the management target as failure information. (Failure detection notification process),
The maintenance operator terminal requests the maintenance operator to perform a repair as a countermeasure against the failure of the managed device that operates based on a request from the maintenance management server (repair request processing step). ,
Prior to requesting a repair to the maintenance worker using this maintenance worker terminal,
The maintenance management server determines whether or not the management target related to the fault is a contract target apparatus that has been contracted in advance as a fault countermeasure target based on the contents recorded in the contract information management database separately provided (contract information) Judgment process),
When it is determined that the management target related to the fault is contracted as the target of the fault countermeasure, whether or not the management target is repairable is determined based on the recorded contents of the contract information management database. The server determines (failure response determination process),
If this the managed than the result of the determination shall serviceable contract a target device and, the maintenance management server, requesting the managed repair by the maintenance worker to the maintenance terminal while, failure status is information necessary maintenance work relating to the repair, identification key, maintenance procedures, or maintenance parts management information registered beforehand and the failure status from the hotel to the apparatus information management database in the maintenance server The identification key, the maintenance procedure, or the maintenance part management information is extracted and transmitted to the maintenance worker terminal (repair request processing step).
The maintenance management server determines whether or not the management target related to the failure is a contract target device, and functions when the management target related to the failure is determined to be a non-contract as a target for the failure countermeasure and is equipped in advance Based on the identification key of the management target related to the failure by the vendor search unit of the maintenance management server, the vendor of the management target that is not contracted related to the failure from the vendor database storing the vendor information that is the shipping source of the management target. Explore
When the vendor can be searched by the maintenance management server, it is pre-registered based on the vendor name, device name and identification key of the management target on the assumption that the management target is the target of the failure countermeasure. The maintenance content specifying transmission unit of the maintenance management server retrieves the setting method, maintenance procedure, maintenance route, related user information, and maintenance parts related information as the maintenance content from the device information management database and retrieves it via the network. The information is transmitted to the maintenance worker terminal and a parts management server installed in advance (claim 9).

(Delete)

Here, when it is determined in the determination step by the maintenance management server described above that the management target device is a contract target device and can be repaired, the maintenance worker terminal to the maintenance worker terminal Prior to the request for repair of the management target device, the maintenance management server inquires the device information management database to collect information such as the maintenance procedure and maintenance part management number related to the management target device, and collects information on the collected management target device. Send such information to the parts management server and execute a substitute parts arrangement request (parts delivery request process)
Subsequently, the information on the identification key of the arranged maintenance parts and the delivery instruction result sent from the parts management server are received,
It is good also as a structure which performs the said repair request regarding the said management object apparatus after that (Claim 10 ).

(Delete)

(Delete)

(Delete)

(Delete)

Furthermore, it functions when the maintenance operator inputs each identification key of the management target device and the replacement maintenance part, and whether or not the use of the replacement maintenance part is input from the maintenance worker as a completion report of repair work that is a countermeasure against the management target device. These are transmitted by the maintenance operator terminal server to the maintenance management server (repair completion report transmission step),
Whether the identification key of the management target device and the replacement maintenance component sent together with the report from the maintenance worker terminal server matches the identification key sent from the component management server is the maintenance management. Server confirms (identification key confirmation process)
If the identification keys match, the maintenance management server may register the work report in a work history management database separately provided in advance (work history registration step) (claim 11 ).

In order to achieve the above object, a maintenance management program according to the present invention targets various computer devices and their peripheral devices to which an identification key is added as maintenance management targets, and indicates whether or not each management target is maintained and the corresponding contents. A maintenance management server having a CPU and a memory to be managed via the CPU and an application for setting a plurality of maintenance management functions executed on the CPU, and detecting when a failure occurs in one of the management targets A notification system which is a failure notification means for transmitting to the maintenance management server the identification key of the management target related to the occurrence of the failure and the failure content after recognizing the failure content, and the maintenance management server formed via the network Request maintenance personnel to repair the managed device that operates based on the request from In the maintenance management system and a maintenance terminal having a 示画 surface,
It functions when the failure information is sent from the notification system that has detected a failure in one of the managed devices, and the management target related to the failure is contracted in advance as a failure countermeasure target A contract information determination processing function for determining whether or not it is a contract target apparatus based on the recorded contents of a contract information management database equipped in advance,
Failure handling determination processing function for determining whether or not the management target can be repaired based on the recorded contents of the contract information management database when the management target related to the fault is contracted as a target for fault countermeasures ,
When each of the determination processing functions determines that the management target is a contract target device and can be repaired, the maintenance worker terminal requests the maintenance worker to repair the management target , and The failure status, identification from the device information management database in which the failure status, identification key, maintenance procedure, or maintenance parts management information, which is information necessary for the maintenance work related to repair, is registered in advance and attached to the maintenance management server in advance. key, maintenance procedures, or repair request processing capability for transmitting removed maintenance component management information to the maintenance terminal,
In determining managed according to the failure of whether contracted device, shipped managed according to the failure to function when it is determined that the non-contract as the object of the fault tolerance, equipped pre Me of the managed the vendor retrieves the vendor database storing the vendor information is based according to the managed device according unsigned in the fault, the vendor specific processing function identified based on the identification key of the managed according to the fault,
If the vendor is specified, the maintenance contents registered in advance based on the vendor name, device name, and identification key of the management target, assuming that the management target is the target of the failure countermeasure. The setting method, maintenance procedure, maintenance route, related user information, and maintenance parts management information are retrieved from the device information management database and sent to the maintenance operator terminal and the parts management server equipped in advance via the network . Provide repair information transmission processing function to send,
Each of these processing functions is realized by a computer provided in the maintenance management server (claim 12).

Here, when it is determined that the management target device is a contract target device and can be repaired by executing the contract information determination processing function and the failure handling determination processing function described above, Prior to requesting repair of the management target device to the maintenance worker, the management target is collected and information such as a maintenance procedure and a maintenance part management number related to the management target device is collected by inquiring to the device information management database. Parts delivery request processing function that sends information related to the device to the parts management server and executes replacement parts arrangement requests,
And when receiving the information on the arranged maintenance part identification key and the delivery instruction result sent from the parts management server, the computer receives the repair request processing function related to the management target device. (Claim 13 ).

(Delete)

(Delete)

In addition, the maintenance operator terminal server determines whether or not the identification key of the management target device and the replacement maintenance part, and whether or not the replacement maintenance component is used, are input by the maintenance worker as a completion report of repair work as a countermeasure against the failure of the management target device. A repair completion report reception processing function for receiving and processing this when it is transmitted to the maintenance management server via
Whether the identification keys of the management target device and alternative maintenance parts sent together with the report from the maintenance worker terminal server match the identification keys related to the management target equipment sent separately from the parts management server Identification key confirmation processing function to confirm whether or not,
And a work history registration processing function for registering the work report related to the device to be managed in a work history management database separately provided in advance when these identification keys match, and causing the computer to realize them. You may make it (Claim 14 ).

(Delete)

(Delete)

(Delete)

According to the present invention, the maintenance staff can quickly know via the display unit of the maintenance worker terminal whether the management target is a maintenance contract or a license contract, and at the same time, the maintenance contract or license without the agreement, it is possible to obtain information necessary for maintenance managed by clarifying the vendor destination work maintenance server as mentioned above, moreover, as a result, the maintenance server maintenance contentspecific transmission It is also possible to arrange the delivery of equipment and parts for maintenance and replacement to be managed, thereby improving the reliability of various information to be acquired and maintaining maintenance management of the management target. An excellent effect that reliability and convenience can be improved can be obtained .

  DESCRIPTION OF EMBODIMENTS Hereinafter, an embodiment of a maintenance management system to be managed according to the present invention will be described with reference to the drawings. The management target maintenance management system according to the present embodiment is configured so that when the maintenance management server that constitutes the maintenance management unit receives information necessary for maintenance work including a failure status of the management target and an identification key, the maintenance target contract of the management target The maintenance management server searches for the vendor to be managed from the identification key, identifies the maintenance target device or part corresponding to the identification key from the vendor name of the vendor, and performs maintenance for the maintenance target. Is to make arrangements.

FIG. 1 is a conceptual diagram showing a conceptual configuration of the maintenance management system of the present embodiment, and FIG. 2 is a functional block diagram showing the main points of the functional configuration of the maintenance management system of the present embodiment. As shown in FIG. 1, a plurality of managed networks 11 are joined to the network Nw, and the maintenance management system 1 that manages the maintenance of each managed object 12 in each managed network 11 is connected via the network Nw. The plurality of vendor databases 41, the management network 21, the parts delivery network 51 , and the maintenance worker terminal 61 are configured to be communicable.

  The managed network 11 includes, for example, various computer devices in a company, a factory, a hospital, or various groups distributed in a wide area as a device having one or more computer devices as a central device, peripheral devices thereof, In this configuration, various devices to be controlled by the computer device are connected to each other via a network such as a LAN or an intranet.

  The various computer devices, various peripheral devices, and various devices (including control targets) in the management target network 11 are all management targets, and each has information (such as a serial number) for uniquely identifying itself. Hereinafter, this information is referred to as an identification key (serial number or the like).

  As shown in FIG. 2, when the failure of each management target 12 occurs, information necessary for maintenance work including the failure status and identification key (device name, serial number of part name, etc.) is input to the management target network 11 A notification system 14 that constitutes the maintenance request transmission means 13 for transmission is installed through the network such as a LAN or an intranet.

  The notification system 14 monitors operation states of various computer devices, various peripheral devices, and various devices (including control targets) that are the management target 12 through a network such as a LAN or an intranet in the management target network 11, The generated device or device (management object 12) is detected. The notification system 14 includes the device name, device (component) name and identification key (device name, serial number of the component name), and failure status information of the device or device (management target 12) that is the maintenance target when the detected failure occurs. Are transmitted to the maintenance management server 24 constituting the maintenance management means 23 described later in the management network 21 via the network Nw.

  The notification system 14 monitors the management target 12 and automatically inputs information necessary for maintenance work including the device (part) name of the management target 12, an identification key (device name, serial number of the part name, etc.), and the failure status. Thus, there is a mode in which the information is automatically transmitted to the maintenance management server 24 together with the maintenance request information. When the notification system 14 automatically inputs information necessary for the maintenance work, there is a configuration in which it is automatically input directly from the management target 12, or a configuration in which it is automatically input from a computer device that manages the management target 12. Alternatively, there is also a configuration in which various device (part) names and identification keys (device names, serial numbers of component names, etc.) of various management objects 12 are stored in advance in the notification system 14 and read out from here. Which of these configurations is selected is based on the production concept at the time of production.

However, in the notification system 14, the operation status of the various management targets 12 is converted into information and stored one by one, and the operation abnormality (failure occurrence) of the management target 12 is detected from the information, and the operation abnormality When a device is detected, information required for maintenance work including the device (part) name, identification key (device name, part number serial number, etc.), and failure status is automatically entered and maintained in any of the above configurations. You may employ | adopt the combination of the 2nd structure of transmitting with respect to the management server 24. FIG. In that case, the notification system 14, for example a CPU, first above CPU, it may be configured that includes a second application for realizing each component.

  On the other hand, if a failure occurs in any of the management targets 12 in the notification system 14, a person in charge at the site or a maintenance worker manually inputs information necessary for the maintenance work by key operation, for example, and requests a maintenance. A mode in which a manual call is made to the maintenance management server 24 may be adopted. This is advantageous for reducing production costs.

  In any case, the notification system 14 receives the device (part) name, identification key (device name, serial number of the component name, etc.), information necessary for maintenance work including the failure status, and maintenance request. When transmitting information (commands) to the maintenance management server 24, for example, hypertext format (WWW) and TCP / IP, that is, transmission from a Web browser, predetermined file transfer (FTP), shell connection, etc. Any transmission method may be used.

  When the notification system 14 acquires failure status information, the notification system 14 itself analyzes the failure status based on log information or the like, or the notification system 14 sends the device name, log information, and the like via the network Nw. There is a mode in which a failure analysis is performed by transmitting to a failure analysis server (not shown), and a failure analysis result is acquired from the failure analysis server. However, a mode in which a maintenance worker directly performs failure analysis by referring to log information or using an inspection device or the like may be employed.

  On the other hand, as shown in FIG. 2, the management network 21 shown in FIG. 1 specifically includes a reception system 22 and a maintenance management server 24 constituting the maintenance management means 23 via a network such as a LAN or an intranet. It is the composition prepared. Although not shown in detail, the maintenance management server 24 may include a vendor database server described later.

  The reception system 22 is an information reception unit or transmission / reception unit connected to the network Nw, and has a security function, for example. When the reception system 22 receives information necessary for maintenance work including the failure status of the management target 12 and the identification key (device name, serial number of the part name, etc.) from the notification system 14, the reception system 22 determines this. Transfer to the maintenance management server 24.

  The reception system 22 is information required for maintenance work including the device name, part name, identification key (device name, serial number of the part name, etc.) of the management target (maintenance target) 12 from the notification system 14 and the failure status. It is possible to correspond to any transmission method for automatic transmission and manual call.

  On the other hand, as shown in FIGS. 2 and 3, the maintenance management server 24 first includes a maintenance contract confirmation unit 25, a vendor search unit 26, a maintenance content identification unit 27, a maintenance content transmission unit 28, An information update unit 29 and a consistency check unit 30 are provided, and secondly, a contract information management database 31, an apparatus information management database 32, and a work history management database 33 are provided. In the maintenance management server 24 shown in FIG. 2, the information update unit 29, the consistency check unit 30, and the various management databases 31, 32, and 33 are not shown. However, this is for convenience of drawing. Actually, it has the same configuration as each configuration shown in FIG.

  A maintenance contract confirmation unit 25, a vendor search unit 26, a maintenance content identification unit 27, a maintenance content transmission unit 28, an information update unit 29, and a consistency confirmation unit 30 provided in the maintenance management server 24 are, for example, a CPU that executes a predetermined application Is functionally realized from time to time. Note that the maintenance content identification unit 27 and the maintenance content transmission unit 28 are collectively referred to as the maintenance content identification transmission unit 44 according to claim 2. On the other hand, the maintenance content transmission unit 28 can also share the information transmission / reception unit of the reception system 22.

  The maintenance contract confirmation unit 25 of the maintenance management server 24 receives the device name, part name, and identification key (device name, part number serial number, etc.) of the management target (maintenance target) 12 from the notification system 14 via the reception system 22. When the information necessary for the maintenance work including the failure status is received, the contract information management database 31 is searched and the maintenance contract status of the management target 12 (maintenance contract information: maintenance execution permission contract, license contract) is obtained. Confirm and record in a memory such as a RAM.

  As shown in FIG. 4, the contract information management database 31 stores each contract number and contract information. In particular, the contract information area includes user information, device name (parts) for each contract number. Name), identification key, license information, maintenance contract information, and contract update history.

  The maintenance contract confirmation unit 25 of the maintenance management server 24 uniquely identifies the maintenance contract status (maintenance contract information: maintenance execution permission contract, license contract) of the management target 12 by searching the contract information management database 31. Can do. As a result, it is possible to easily determine whether or not a maintenance contract has been concluded, and how to deal with the contract contents (that is, repair, sending of an alternative device, or inability to repair).

  On the other hand, the maintenance contract confirmation unit 25 of the maintenance management server 24 cannot confirm the maintenance contract status (maintenance contract information: maintenance execution permission contract, license contract) of the management target 12 even after searching the contract information management database 31 ( In other words, the maintenance target 12 does not require the management target 12 to refer the information of the device (part) name and identification key (device name, part number serial number, etc.) of the management target (maintenance target) 12 to the vendor search unit 26. Information indicating maintenance non-contract is recorded in a memory such as a RAM, and the process is terminated.

  The vendor search unit 26 of the maintenance management server 24 receives the device name, the component name, and the identification key (device name, serial number of the component name, etc.) of the management target (maintenance target) 12 from the notification system 14 via the reception system 22. When the information necessary for the maintenance work including the failure status is received, the confirmation contents of the maintenance contract confirmation unit 25 are recognized from the RAM, and if the maintenance is not contracted, the apparatus is based on the information necessary for the maintenance work. The information management database 32 or each vendor database 41 is searched to search for the vendor name of the vendor 12 to be managed, and the search result is recorded in a memory such as a RAM.

  In the apparatus information management database 32, as shown in FIG. 5, for example, each contract number and apparatus information are stored in the first area. In particular, in the apparatus information area, for each contract number, User information, device name (part name), identification key, device configuration information, setting information, and maintenance procedure are stored. In the device information management database 32, for example, each reference number and device information are stored in the second area. In particular, in the device information area, a maintenance part management number, a sales vendor ( Vendor name) and repair route are stored.

  That is, the vendor search unit 26 of the maintenance management server 24 searches the device information management database 32 to find the company name, address, and inquiry destination (for example, telephone) of the sales vendor (or production vendor) of the management target 12. Number, fax number, IP address, etc.) can be uniquely identified. If the vendor search unit 26 cannot identify the vendor of the management target 12 even after searching the device information management database 32, the vendor search unit 26 at least the device (part) name of the management target 12 and its identification key (device) The vendor database 41 for each vendor is sequentially searched based on the information of the name, the serial number of the part name, etc.), and the vendor name of the vendor 12 to be managed is uniquely specified from any vendor database 41. .

  When the maintenance contract is confirmed from the contents of the RAM or when the maintenance contract is not confirmed and the vendor name of the management target (maintenance target) 12 has been searched, The device information management database 32 is searched based on the information necessary for the maintenance work, and the device name (maintenance target), part name (maintenance target), identification key (device name, part number serial number, etc.) of the management target 12 The maintenance content (setting information, maintenance procedure, repair route, etc.), maintenance part management number, and user information are specified and recorded in a memory such as a RAM.

  That is, the maintenance content specifying unit 27 of the maintenance management server 24 searches the device information management database 32 shown in FIG. 5 to obtain the user information, the device name (part name) of the management target 12, It is possible to uniquely identify an identification key (such as a serial number), its device configuration, its setting method, its maintenance procedure, and its repair route.

  The maintenance content transmission unit 28 of the maintenance management server 24 includes a device name (maintenance target), a part name (maintenance target), an identification key (device name, serial number of the component name: A new identification key before shipment), information on the above-mentioned maintenance contents, and user information are acquired from, for example, a RAM and transmitted to the maintenance worker terminal 61 together with information on maintenance requests via the network Nw. The information is transmitted together with the information to the component management server 53 constituting the component delivery arrangement means 52 of the component delivery network 51. When transmitting to the parts management server 53, the maintenance parts management number is also included.

  The maintenance content transmitting unit 28 of the maintenance management server 24 requests the maintenance worker terminal 61 to maintain the above information when receiving the information on the contents of the delivery instruction contents of the apparatus and the parts related to the maintenance from the parts management server 53. You may employ | adopt the aspect of transmitting with this information.

  The information update unit 29 of the maintenance management server 24 receives information from the parts management server 63 such as the name of the device to be replaced for maintenance, the name of the component, and its new identification key (device name, serial number of the component name, etc.). At the time of reception, at least the device name, the part name, the information of the new identification key, etc. are recorded in the corresponding areas of the contract information management database 31, the device information management database 32, and the work history management database 33. Update.

  That is, the information update unit 29 of the maintenance management server 24, specifically, when the maintenance of the management target 12 is executed or when the maintenance is finished, the contract information management database 31, the device information management database 32, and the work The contents of the corresponding area of the history management database 33 are updated to the information of the device name, the component name, and the new identification key (device name, serial number of the component name, etc.) acquired from the component management server 53.

  Although not shown in detail in the work history management database 33, the contract number for each management target, user information, the device name of the management target, its identification key, past failure history, maintenance work history, and identification key history of used parts Is stored.

  When the information update unit 29 of the maintenance management server 24 updates the contents of the work history management database 33 with the recognition of the end of maintenance, the information update unit 29 updates the work history management database 33 with, for example, a management target 12 contract number, user information, the device name of the management target 12, and its identification key (new identification key) are additionally registered, and the failure status of the current management target 12 is additionally registered in the past failure history, In addition, the main points of the maintenance work of the current management target 12 are additionally registered in the maintenance work history, and further, the identification key (new identification key: new identification key: used in the maintenance of the current management target 12 in the used part identification key history) A series of processes of registering additional serial numbers and the like) is performed.

  As an example of the update time, the maintenance management server 24 acquires, for example, information on an identification key (serial number, etc.) of a device name (part name) used for maintenance from the device information management database 32 or the vendor database 41. Later, with the maintenance completion of the maintenance worker, a new identification key (device name, serial number of the component name, etc.) relating to maintenance execution from the maintenance worker terminal 61 described later or from the component management server 53 described later is provided. There is a mode in which the time when the reception of information or the like is confirmed is set as the update time.

  On the other hand, the consistency confirmation unit 30 of the maintenance management server 24 performs date and time counting, etc., and relates to the above identification key and other various identification keys (serial number, etc.) held in the contract information management database 31 and the like. Maintenance contract status information, various identification keys (serial number, etc.) held in the device information management database 32, various device information, various parts information, various setting methods as maintenance contents, maintenance procedures, repair routes, etc. The consistency with the information of the identification key held by each vendor database 41 and information of other various identification keys (serial number, etc.) is periodically checked, for example, every predetermined day.

  If the result of the consistency check is not possible, the consistency check unit 30 of the maintenance management server 24, for example, stores each of the units 25, 26, 27, and 28 in the maintenance management server 24 and each vendor database 41. By confirming the operation history and determining whether or not there is a match of information comprehensively, information such as a regular identification key (such as a serial number) is determined, and based on the information, the contract information management database 31, The apparatus information management database 32, the work history management database 33, and the vendor database 41 each establish information consistency of various items (that is, match information).

  That is, for example, the consistency check unit 30 of the maintenance management server 24, for example, repeatedly determines whether there is a match between each operation history and information and searches for a recording destination (that is, a terminal or a database) of erroneous information. , The rewrite request (command) of the incorrect information to the correct information is output to the recording destination together with the correct information, the self correction is performed, and the normal correction is made by returning the information after the rewrite. A mode (processing method) of confirming and completing the establishment of consistency is also executed.

  However, the consistency establishment process of the consistency confirmation unit 30 is not limited to the above-described process, and other arbitrary methods (processing methods) may of course be used.

  The management network 21 can also be considered to correspond to the concept of the center. The management network 21 automatically collects information held by the plurality of vendor databases 41 and collects the information in a batch. A configuration including a vendor database (not shown) is also preferable.

  On the other hand, the vendor database 41 shown in FIGS. 1 and 2 is, for example, a database system configured by a hard disk or the like provided in each computer device (not shown) having a communication function managed by a sales vendor that sells a management target. It is.

  Although not shown in detail in each vendor database 41, the sales history of the same device as the management target sold in the past, the sales destination user information, the name of the device (part), its identification key (serial number, etc.), and the vendor Stores contract information (maintenance contract information: maintenance execution permission contract, license contract) and the like. However, the concept of the identification key (serial number, etc.) for each device (each part) includes the identification key (serial number, etc.) of the device (part) name already shipped (sold), and the inventory device ( Component) name identification key (serial number, etc .: hereinafter referred to as a new identification key). The vendor database 41 may be configured as a comprehensive vendor database server (not shown) installed in a predetermined center or the like.

  For example, a sales vendor can perform maintenance (repair) only on devices and parts sold by the company, and when receiving a maintenance request, the vendor database 41 has registered information such as identification key information. By checking, it is determined whether or not maintenance of the management target 12 is performed.

  When the vendor database 41 receives a search request related to maintenance management from the maintenance management server 24, which will be described later, for example, the vendor database 41 receives the search request device (part) name and identification key (serial number, etc.) from its hard disk or the like. Corresponding to the above-mentioned sales history of the same device as the management target sold in the past, sales user information, various device names, various component names, various identification keys (device names, serial numbers of component names, etc.), and The vendor contract information (maintenance contract information: maintenance execution permission contract, license contract) and the like are searched, and the search contents are transmitted to the maintenance management server 24.

  That is, the vendor database 41 receives, for example, information on a specific device (part) name of the management target (maintenance target) 12 and an identification key (serial number, etc.) of the device (part) name from the maintenance management server 24 described later. When it is received, it recognizes the information to that effect, searches whether or not its vendor handles the management object 12 in the present and the past, and retrieves (ie, confirms) that the vendor deals with the present and the past. In this case, information on a new identification key (such as a serial number) associated with an unshipped apparatus (part) name for maintenance replacement corresponding to the apparatus (part) name is transmitted to the maintenance management server 24 and updated. In the case of updating, information on a new identification key (serial number, etc.) attached to the name of the device (part) for maintenance replacement has been sold at a predetermined timing (for example, at the start of delivery or after the end of maintenance). Move to the device (parts) name column, and enter each new identification key (serial number, etc.) that accompanies various maintenance replacement or sales device names in the unsold (stock) device (parts) name column. Advance all information. Next time, the information of the identification key at the head of the inventory (serial number or the like: new identification key) becomes the search target when the above-mentioned search request from the maintenance management server 24 is made.

  When the vendor database 41 receives a consistency check request from the maintenance management server 24, which will be described later, the vendor database 41 stores the sales history, sales destination user information, each sold and each inventory of the same device as the management target sold in the past. Check the consistency of the device name, part name, identification key (device name, part number serial number, etc.), and each vendor contract information (maintenance contract information: maintenance execution permission contract, license contract). That is, the vendor database 41 confirms whether or not the information in the maintenance management server 24 matches the related information (for example, identification key: serial number) in the vendor database 41. Both the information is matched with the server 24 and the consistency of both is adjusted.

  On the other hand, as shown in FIG. 2, the parts delivery network 51 shown in FIG. 1 includes a parts management server 53, a parts management database 58, and computer equipments in various parts of the parts delivery center 54 (see FIG. 2). For example) via a network such as a LAN or an intranet. However, the parts delivery center is not installed only in the parts delivery network 51, but is also installed in each of a plurality of remote locations. Therefore, the parts management server 53 has a component in each location in the remote locations. It is also possible to perform information communication (communication of a device for maintenance / replacement or parts delivery request, etc.), which will be described later, with a computer device in the delivery center.

  As shown in FIGS. 2 and 6, the component management server 53 includes a transmission / reception unit 55 for various information, a delivery arrangement unit 56, a delivery instruction recognition unit 57, and a component management database 58.

  The various information transmission / reception unit 55 of the parts management server 53 includes a maintenance management server 24, computer equipment (not shown) at various locations in the parts delivery center 54, and computer equipment (not shown) at locations in the remote parts delivery center. Or predetermined information can be transmitted / received to / from a maintenance worker terminal 61 to be described later via the network Nw.

  The delivery arrangement unit 56 of the component management server 53 firstly has at least the device name and component name of the management target 12 from the maintenance management server 24, and a new identification key for maintenance (device name, serial number of the component name, etc.). When the user information and the component request information are received, the component management database 58 is searched based on the user information, a new identification key (serial number, etc.), etc. Determine if the part is in stock. Secondly, if the device or part is in stock, computer equipment (not shown) in each part of the parts delivery center 54 or the location of the user (of the management object 12) is used to arrange the delivery of the device or part. Instructions for delivery of the devices and parts are given to computer equipment (not shown) at various locations within the remote parts delivery center closest to the location.

  On the other hand, although not shown in detail in the parts management database 58, the storage status and storage location of various maintenance and replacement devices and maintenance and replacement parts, a new identification key (device name, Information necessary for component management and delivery, such as a serial number of the component name: a new identification key before shipment), is stored.

  The delivery arrangement unit 56 of the parts management server 53 searches the parts management database 58, and new identification keys (devices, parts serial numbers, etc.) associated with the current maintenance / replacement equipment and parts based on the maintenance parts inventory information. ), And the storage status and storage location of the device or component, and whether it is most appropriate to output the delivery instruction information to which computer equipment in which delivery center. It is possible to recognize.

  At the time of delivery instruction executed by the delivery arrangement unit 56 of the parts management server 53, at least the device name and part name of the management target 12 based on the maintenance parts inventory information, and a new identification key for maintenance replacement (device name and part name) User information including serial number, etc. (new identification key before shipment) and delivery instruction information (command), that is, user company name, affiliation, location, contact information (telephone number, FAX number, Information such as an IP address) is output to a computer device or the like at any of the appropriate distribution centers.

  The delivery instruction recognition unit 57 of the component management server 53 records the contents of the delivery instruction (delivery instruction result) in a memory such as a RAM, for example, and after the delivery instruction is completed, for example, in the delivery center that is the current target. When the delivery instruction confirmation information is received from the computer device or the like, the contents of the delivery instruction are read from the memory and transmitted to the maintenance management server 24 via the network Nw. In addition, it is preferable that the delivery instruction result information includes the delivery date and time of the apparatus and parts related to the maintenance.

  On the other hand, the maintenance worker terminal 61 shown in FIGS. 1 and 2 is a mobile terminal such as a mobile phone, a mobile computer, and a PDA, and a mobile phone is exemplified in the present embodiment.

  The maintenance worker terminal (mobile phone) 61 receives a new identification key (device name) of at least the device name and component name of the management target 12 from the maintenance management server 24, and the device (component) name before shipment (for maintenance replacement). The serial number of the part name, etc.), maintenance contents (setting method, maintenance procedure, repair route, etc.), and information such as the above-mentioned user information related to the management target 12 are received via the network Nw, and the information is maintained. It is displayed as text in a predetermined format on a display unit such as a liquid crystal display device of the worker terminal 16.

  By referring to the information displayed on the display unit of the maintenance worker terminal (mobile phone) 61, the maintenance worker can easily and clearly recognize the specific maintenance work content and procedure of the management target 12, In addition, the location, contact information, and the like of the management target 12 are recognized, so that accurate maintenance work can be performed efficiently. When the maintenance worker finishes the maintenance work on the management target 12, the maintenance worker sends an identification key (serial number or the like: a new identification key) of the newly replaced device or part to the maintenance management server 24 to perform the maintenance work. Notify the end and ask for confirmation that the replaced devices and parts are correct.

  The maintenance worker terminal (cellular phone, mobile computer, PDA or the like) 61 can also be used as a substitute for the notification system 14 that constitutes the maintenance request transmission means 13.

  Next, an example of the maintenance management method of the management target of this embodiment will be described. The maintenance management method of this example is: 1. maintenance request transmission process, 2. maintenance contract confirmation process, 3. vendor search process, 4. maintenance content specifying process, 5. maintenance content transmission process, 6. delivery arrangement process, 7. Each process of the delivery instruction recognition process is performed sequentially.

  That is, first, in the maintenance request transmission step, information necessary for maintenance work including the failure status of the management target 12 and the identification key (serial number, etc.) is input to the notification system 14, and the notification system 14 performs the maintenance work. Necessary information is transmitted to the maintenance management server 24 via the network Nw.

  When the reception system 22 of the maintenance management network 21 receives the information necessary for the maintenance work from the notification system 14 and the reception system 22 recognizes that, for example, the reception system 22 is necessary for the maintenance work received this time. The information is transferred to the maintenance management server 24.

  When the maintenance management server 24 receives from the reception system 22 information necessary for maintenance work including the failure status of the management target 12 and the identification key (serial number, etc.), then in the maintenance contract confirmation process, the maintenance management server 24 Activates the maintenance contract confirmation unit 25, searches the contract information management database 31 based on the device (part) name of the management target 12 and its identification key (serial number, etc.), etc., and displays the maintenance contract status of the management target 12 Check. As a result, when it is confirmed that a maintenance contract is concluded for the management object 12, a maintenance content specifying step and a maintenance content transmission step, which will be described later, are sequentially performed.

  However, if it is confirmed in the maintenance contract confirmation process that the management object 12 is not concluded with a maintenance contract, then in the vendor search process, the maintenance management server 24 activates the vendor search unit 26 to perform the maintenance work. Among the necessary information, the vendor of the management target 12 is searched from the device information management database 32 based on the device name of the management target 12 and its identification key (serial number, etc.). As a result, when the vendor of the management target 12 can be searched, the maintenance content specifying step described later is performed. When the vendor of the management target 12 cannot be searched, the vendor search unit 26 continues each vendor. For each vendor database 41 managed by the system, the device name, part name, identification key (serial number, etc.) of the management target 12 among the information necessary for the maintenance work, in sequence, through the network Nw, and Search request information (command) as to whether there is matching information or not is searched for the vendor name of the actual vendor of the management target 12.

  Thus, if the vendor name of the vendor of the management target 12 can be searched, then in the maintenance content specifying step, the maintenance management server 24 activates the maintenance content specifying unit 27, and the vendor name and device (part) name. And the setting method, maintenance procedure, maintenance route, user information of the management target 12, maintenance part management number, etc. as the maintenance content of the management target 12 from the device information management database 32 based on the identification key (serial number, etc.) To do.

  Next, in the maintenance content transmission step, the maintenance management server 24 activates the maintenance content transmission unit 28, and manages the vendor name, device name, component name, and identification key (device name, device name) of the management target 12 searched by the vendor search unit 37. (Part number serial number, etc.), and in particular, part request information (command) including user information and maintenance part management number is transmitted to the part management server 53 via the network Nw.

  When the transmission / reception unit 55 of the component management server 53 receives the information (command) from the maintenance management server 24, the component management server 53 activates the delivery arrangement unit 56 and arranges the delivery arrangement in the next delivery arrangement process. In order to do this, from the parts management database 58 based on the information of the vendor name, device name (part name) of the management target 12 and its identification key (device name, part number serial number, etc.) It is recognized whether 12 maintenance replacement devices and parts are in stock. If it is not in stock, information indicating “out of stock” is transmitted to the maintenance management server 24. If it is in stock, secondly, a device for maintenance replacement of the current management target 12 is retrieved from the parts management database 58. And a new identification key (device, part serial number, etc.) associated with the part, the storage status of the part or the part, and the storage location. Thirdly, it is determined whether it is most appropriate to output the information of the delivery instruction to which computer device or the like in which delivery center including the information of the recognition result, and the determination destination The information on the request for delivery of the maintenance / replacement device and parts is transmitted together with the user information.

  Next, in the delivery instruction recognition process, the parts management server 53 activates the delivery instruction recognition unit 57 to recognize the delivery arrangement instruction result performed in the delivery arrangement process from a memory such as a RAM, and the delivery arrangement instruction result. Is sent to the maintenance management server 24 via the network Nw.

  On the other hand, when the maintenance management server 24 receives the information on the delivery arrangement instruction result from the parts management server 53, the maintenance management server 24 records the information in a memory or a hard disk, while the maintenance replacement device (parts) of the management target 12 is recorded. The name, a new identification key (device name, part number serial number) associated therewith, information on the maintenance content, and user information are transmitted to the maintenance worker terminal 61 together with information on the maintenance request.

  In the maintenance management method to be managed in this example, next, the 8 update process, the 9 registration process, and the 10 consistency check process are performed. That is, in the update process, in the case of this example, the maintenance management server 24 performs a maintenance replacement device (part) from the maintenance worker terminal (mobile phone) 61 in accordance with the maintenance execution of the management target 12 (that is, the maintenance end). When information such as a name and a new identification key (serial number, etc.) associated with the device (part) is received, the information update unit 29 is activated, and a contract information management database 31, a device information management database 32, and The corresponding information in the work history management database 33 is updated.

  When updating the information, the information on the identification key before maintenance replacement in the contract information management database 31, the device information management database 32, and the work history management database 33 is replaced with information on a new identification key (serial number, etc.) after maintenance replacement. However, other necessary information is also updated. In the work history management database 33, various contents relating to the current maintenance work are recorded.

  On the other hand, in the registration process, the vendor database 41 related to this time registers the new identification key (serial number, etc.) associated with the maintenance replacement device (part) of the current management target 12 as a shipped identification key. In addition, the information of each new identification key (serial number, etc.) associated with the same unshipped (inventory) same device (part) is advanced.

  On the other hand, in the consistency confirmation step, the maintenance management server 24 activates the consistency confirmation unit 30 when a predetermined time elapses or when a predetermined date and time elapses (arrival), and the identification key held in the contract information management database 31 And various other identification keys (such as serial numbers), maintenance contract status information related thereto, various identification keys (such as serial numbers) held in the device information management database 32, various device information, various parts information, and Consistency confirmation is performed between information such as various maintenance procedures as maintenance contents and information on the identification key held by each vendor database 41 and other various identification keys (such as a serial number).

  When the result of the consistency check is not possible, the consistency check unit 30 checks the operation history of each of the units 35, 36, 37, 38 and each vendor database 41 in the maintenance management server 24, for example. Information such as a legitimate identification key (serial number, etc.) and a vendor name is determined by comprehensively determining whether or not there is a match between the information. Based on the information, the contract information management database 31 and the device information are determined. The consistency of information of various items held in the management database 32, the work history management database 33, and each vendor database 41 is established (that is, the information is matched).

  Next, an example of an information update method related to maintenance management of a management target according to the present embodiment will be described. In the information update method of this example, the following steps are sequentially performed: 1) vendor name acquisition process, 2 information update process, 3 consistency check process, and 4 consistency establishment process.

  That is, first, in the vendor name acquisition process, the maintenance management server 24 searches, for example, the device information management database 32 based on information such as an identification key (serial number) attached to the device (part) name of the management target 12. The vendor name of the vendor of the management target 12 is searched through a search request of each vendor database 41, and a new identification key (serial number or the like) at the time of maintenance replacement of the management target 12 is acquired.

  Next, in the information update process, the maintenance management server 24 obtains the above information in the recording area of all possessed information related to the management object 12, that is, the recording area of the vendor name of the management object 12 in the device information management database 32 and the work history database 43. The vendor name information is recorded and updated, and the new identification key (serial number and the like) information acquired is recorded and updated in the identification key recording area of the management target 12.

  Next, in the consistency check step, the maintenance management server 24 detects, for example, the arrival of a predetermined time or regular predetermined date and time, and among the all possessed information related to the management target 12 possessed by the maintenance management server 24, the identification key ( Serial number, etc.) and new identification key (serial number, etc.) information, shipped identification keys (serial numbers, etc.) and new inventory identification keys (serial numbers, etc.) individually owned by a plurality of vendor databases 41 ) Information exchange and information retrieval (retrieval of information integrity when exchanging information) is performed to confirm consistency.

  When the consistency check is impossible, for example, the vendor name, the identification key (serial number, etc.), and the new identification key among all the possessed information related to the management target 12 held by the maintenance management server 24 (Serial number, etc.) information, or information on a shipping identification key (serial number, etc.) held by each vendor database 41 and a new identification key (serial number, etc.) of inventory (not shipped, not sold) Then, in the consistency establishing step, the maintenance management server 24 performs information communication including a predetermined command for correcting the error with each vendor database 41 etc. Requests rewriting of information, thereby establishing consistency. The consistency establishment may be performed in the contract information management database 31, the device information management database 32, and the work history management database 33 in the maintenance management server 24. By checking the consistency or establishing the consistency, it is possible to deal with management information changes (contract renewal / cancellation / new installation / removal / new sales, etc.) of the management target 12 other than during maintenance work.

  On the other hand, FIG. 7 is a flowchart showing the operation of the notification system 14 when a CPU is included. When the CPU of the notification system 14 first recognizes that a failure has occurred in any of the management targets 12 in step 701, it recognizes the failure content in step 702. For the recognition of the failure content, a failure analysis function built in the notification system 14 may be used, or a failure analysis may be performed on the failure analysis server via the network Nw for reception.

  Next, in step 703, the CPU of the notification system 14 recognizes information such as the device name, maintenance component name, and identification key (device name, serial number of the component name, etc.) of the current management target (maintenance target) 12. Information on the identification key (serial number, etc.) may be input directly from the current management target (maintenance target) 12, input from a computer device that manages the entire management target network 11, or manually input. is there.

  Next, in step 704, the CPU of the notification system 14 obtains the device name, maintenance component name, identification key (device name, serial number of the component name, etc.) of the current management target (maintenance target) 12 acquired this time, and the fault content ( (Failure status) information is transmitted to the maintenance management server 24. Then, this flow ends.

On the other hand, FIG. 8 is a flow chart showing an example of an application for operating the maintenance management server 24 (i.e., maintenance management program).
First, in step 801, the CPU of the maintenance management server 24 receives the device (part) name of the management target 12 from the notification system 14 via the reception system 22, its identification key (device name, serial number of the component name, etc.), and upon receiving the information required for the maintenance work including the fault situation, etc., followed in step 802, you check the maintenance contract status of searches contract information management database 31 managed 12.

If it is confirmed in step 802 that the management target 12 has “maintenance contract”, the CPU of the maintenance management server 24 then searches the device information management database 32 in step 803 to perform the maintenance work from the notification system 14. Maintenance target name (device name or part name for maintenance / replacement) corresponding to information required for maintenance, setting method as maintenance content, maintenance procedure, repair route, etc., and maintenance / replacement apparatus (parts) ) a new identification key associated with the name (serial number, etc.), user information, and identify the service parts management number that recorded in the memory such as RAM.

If “no maintenance contract” is confirmed for the management target 12 in step 802, the CPU of the maintenance management server 24 is the sales vendor of the current management target 12 for each vendor database 41 in step 804. Whether the management object 12 has been handled in the past or the present is transmitted in sequence. As a result, if it is determined in step 805 that the vendor (vendor name) is “specified”, the process proceeds to step 803. On the contrary, if it is determined that the vendor (vendor name) is “not specified”, this time managed 12 you exit this flow it is determined that the maintenance can not be performed.

On the other hand, after the above-described processing in step 803, the CPU of the maintenance management server 24 then, in step 806, at least the maintenance target name and maintenance content (setting method, maintenance procedure, repair route, etc.) of the management target 12 specified and recorded this time. , And the information of the new identification key (serial number, etc.) are transmitted to the maintenance worker terminal 61 together with the information of the maintenance request, and in particular, the information of the parts request (command) including the user information and the maintenance part management number ) with that it sends to the component management server 53.

  Next, in step 807, the CPU of the maintenance management server 24 has received the result of the delivery instruction of the device (part) name corresponding to the maintenance target name of the management target 12 from the parts management server 53, that is, whether the delivery instruction result information has been received. If it is determined that “the delivery instruction result has been received”, then in step 808, the fact and information on the delivery instruction result are recorded in a memory such as a RAM.

Next, in step 809, the CPU of the maintenance management server 24 performs maintenance of the management target 12, that is, specifically, when the maintenance work ends, from the maintenance worker terminal 61 to the device after the maintenance replacement of the current management target 12. If the reception of the information of the new identification key (serial number, etc.) of the (component) name is recognized, then in step 810, the information of the replaced identification key is obtained from the vendor database 41, the component management server 53, etc. It is determined whether or not it matches the acquired new identification key. If it is determined in step 810 that the identification key from the maintenance worker terminal 61 is “no match”, in step 811, a retransmission request for the identification key is transmitted to the maintenance worker terminal 61, and step 810 is repeated. If it is determined in step 810 that the identification key from the maintenance worker terminal 61 is “matched”, for example, in the contract information management database 31, the device information management database 32, and the work history management database 33 in step 812. Of the various types of information, all information related to the current maintenance is updated and stored. The updated information, primarily, management vendor name of the target 12, and including the information of the new identification key associated with the maintenance and replacement of equipment and parts (serial number, etc.).

Next, when the CPU of the maintenance management server 24 detects a predetermined periodic date and time in step 813, for example, in step 814, the CPU of the maintenance management server 24, each vendor database 41, and the parts management server 53 stores various information. Check consistency. In other words, in step 814, various identification keys to be confirmed in the first procedure and maintenance contract status information related to the new various identification keys, various device information to be identified and recorded in the third procedure, various components Information, various maintenance procedures as maintenance contents, the various identification keys, the new various identification keys, the information on the various vendor names, the various identification keys held by the vendor databases 41, and the new various identification keys Check the consistency with the information. This consistency check, management information change of the managed 12 except during maintenance work as well in (contract renewal, discontinued and new installation, removal and new sales, etc.) Ru rooms available Der.

  On the other hand, FIG. 9 is a flowchart showing an example of an application for operating the vendor database 41, that is, a maintenance management program according to claim 17. First, when the CPU of the vendor database 41 detects reception of predetermined information or a command in step 901, in step 902, the CPU recognizes the content of the information received this time.

  In step 902, the information received this time is information including the name of the device that is the maintenance target of the management target 12 from the maintenance management server 24, the part name, its identification key (device name, serial number of the part name, etc.), and the like. If it has been recognized, in step 903, the device, apparatus, or component related to the device name and identification key (device name, serial number of the component name, etc.) has been handled by the vendor in the past and present (produced, or It is determined by searching whether or not it corresponds to (sold).

In step 903, the device name of the management target 12 that is the maintenance target, its identification key (device name, serial number of the part name, etc.), or the part has been handled by the vendor in the past and present (produced, or If it is determined that the item corresponds to “sold”, in step 904, information relating to the new identification key (device name, part number serial number, etc.) at the time of replacement of the management target 12 is retrieved. and, in step 905, after transmitting (returning) to the maintenance management server 24 together with information located corresponding to the search results, Ru returns to step 901.

However, in step 903, the device name, the device, or the component related to the device name and the identification key (device name, serial number of the component name, etc.) handled by the vendor in the past and present (produced) In step 906, information indicating “not applicable”, that is, information indicating that it is not handled by its own vendor is transmitted (returned) to the maintenance management server 24. after, Ru returns to step 901.

On the other hand, if it is determined in step 902 that the information received this time is information (command) for consistency confirmation from the maintenance management server 24, for example, sold by the vendor (vendor database 41) owned by the vendor in step 907. Information including various device names, various component names, various identification keys (device names, serial numbers of component names, etc.), and various device names in stock, various component names, various identification keys (device names, component names Search for information including serial number etc.) and check consistency. Then, in step 908, after transmitting the results of the information of the integrity check to the maintenance management server 24, Ru returns to step 901.

On the other hand, in step 902, when information (command) for requesting rewriting of specific information (for example, sold identification key: serial number) is established to establish consistency, in step 909, the corresponding field is displayed. after the integrity of established rewriting the information was performed, in step 910, transmits information indicating the processing result with respect to the maintenance management server 24, Ru returns to step 901.

FIG. 10 is a flowchart showing an example of an application for operating the parts management server 53, that is, a maintenance management program according to claim 18. The CPU of the component management server 53 first recognizes the content of the received information in step 1001. If it is confirmed in step 1001 that the information of the inventory confirmation request is received together with the information of at least the device (part) name of the management target 12 and the identification key (serial number, etc.) from the maintenance management server 24, the management is performed in step 1002. the apparatus of the subject 12 (part) name, and intends that line the inventory check of identification key maintenance target corresponding to the (serial number, etc.) (exchange equipment and replacement parts managed 12).

In step 1002, when it is confirmed (searched) that the device (part) of the management target 12 is “out of stock”, the fact is transmitted to the maintenance management server 24 and this flow is ended. However, when it is confirmed (searched) that the device (part) of the management target 12 is “in stock” in step 1002, the delivery arrangement of the device or part of the management target (maintenance target) 12 is performed in step 1003. That is, in order to arrange the delivery of the apparatus and parts, it is closest to the computer equipment (not shown) in each place in the parts delivery center 54 shown in FIGS. 1 and 2 or the location of the user (location of the management target 12). various places in the computer equipment of remote parts delivery in the center (not shown) to intends rows delivery instruction of the device or component.

Next, in step 1004, the CPU of the parts management server 53 sends the information on the delivery arrangement instruction result together with information on a new identification key (such as a serial number) attached to the maintenance replacement apparatus (part) to the maintenance management server 24. Send to. Step 1004 corresponds to a third procedure described in claim 18 . Its to, and the flow ends.

On the other hand, FIG. 11 is a flowchart showing an example of an update program for information related to each maintenance management described in claims 21 and 22, that is, each application for operating the maintenance management server 24 or the vendor database 41. First, in step 1101, the CPU of the maintenance management server 24 sequentially transmits a vendor inquiry request including a vendor search request (vendor search request for the management target 12) to each vendor database 41 managed for each vendor. In addition, after sending the inquiry request, in step 1102, information on the vendor name of the vendor of the management target 12 as a search result from the corresponding vendor database 41, and an apparatus (part) at the time of maintenance replacement of the management target 12 We get the information of the new identification key associated with the name (serial number, etc.).

Next, in step 1103, the CPU of the maintenance management server 24 manages, for example, among the recording areas of all possessed information related to the management target 12 in the contract information management database 31, the device information management database 32, and the work history management database 33. The acquired vendor name is recorded and updated in the vendor name recording area of the target 12, and the acquired new identification key (serial number, etc.) information is recorded in the identification key recording area of the management target 12. you updated.

Next, in step 1104, the CPU of the maintenance management server 24 detects the periodic date and time, for example, all of the management targets 12 in the contract information management database 31, the device information management database 32, and the work history management database 33. Consistency confirmation request information is sequentially transmitted to the predetermined vendor database 41 together with information on the identification key before the maintenance execution and the new identification key (serial number and the like) after the maintenance execution. As a result, the CPU of each vendor database 41, in step 1105, the information on the shipping identification key and the new identification key (serial number etc.) of the inventory held in its own vendor database 41 and the above-mentioned information of the maintenance management server 24. each database 31, 32 and 33 that sends to the maintenance management server 24 information check consistency check results by performing a check consistency between the information held.

Next, in step 1106, the CPU of the maintenance management server 24 receives the information of the confirmation result of the consistency check from the vendor database 41 and records it in a memory such as a RAM, and the maintenance management server 24 itself, for example, a contract information management database 31, the device information management database 32, and compared with the respective information in the work history management database 33, intends row to confirm both the integrity and records the result of the comparison in a memory such as a RAM.

Next, in step 1107, the CPU of the maintenance management server 24 determines whether or not all of the processes 1104, 1105, and 1106 have been performed until there is no access destination vendor database 41. If the access destination vendor database 41 still exists, the process then returns to step 1104 and, similarly to the above, out of all possessed information related to the management target 12 in the maintenance management server 24, the identification key before maintenance execution and maintenance execution Information on the consistency check request is transmitted to the next predetermined vendor database 41 together with information on the new identification key (serial number and the like) later. Then, by repeating the processing of steps 1104 and 1106, it is possible to clarify the location where there is an error in storing information such as an identification key (serial number or the like). Next, in step 1108, the CPU of the maintenance management server 24 specifies an error destination of the stored information based on all the comparison results in step 1106. Next, in step 1109, the consistency cannot be confirmed, and consistency with the storage destination of the incorrect information (that is, each of the management databases 31, 32, 33 or any one of the vendor databases 41 in the maintenance management server 24). establishment request information (command) along with the regular information (output) that sends.

If the CPU of the maintenance management server 24 determines that the consistency establishment request is addressed to itself in step 1110, “Yes” means that the CPU of the maintenance management server 24 then, in step 1111, for example, the contract information management database 31 and the device information Incorrect information in the management database 32 or the work history management database 33 is rewritten with regular information. Then, in step 1112, the CPU of the maintenance management server 24 confirms the information after rewriting, and then returns to step 1101.
On the other hand, if the output of consistency establishment request information is not recognized in step 1110, “No” is determined. In step 1113, the destination of the current consistency establishment request information is any vendor database 41. It is determined whether or not. If the determination result of step 1113 is "Yes", the process proceeds to step 1116 which will be described later, when "No", the process of this consistency establishment is not required, it terminates this flow.

On the other hand, when the specific vendor database 41 recognizes the consistency establishment request information (command) together with the regular information in step 1114, the vendor database 41 then converts the incorrect information to the regular information in step 1115. The error is corrected and the consistency is established, and the consistency establishment information and the corrected information are transmitted to the maintenance management server 24. Then, CPU maintenance server 24, in step 1116, which receives the information after the modification, after checking the content, it terminates this flow.

  Next, the overall flow of the management target maintenance management system 1 according to the present embodiment will be described with reference to the overall flowcharts shown in FIGS. First, when a failure occurs in the management target 12 (step A1201), the notification system 14 provides information necessary for maintenance work such as the device (part) name of the management target 12, its identification key (serial number, etc.), failure status, and the like. Is notified to the reception system 22 of the management network 21 and a repair response request (failure call) is made (A1202). The means used for the notification may be any of automatic notification using a computer network such as the Internet by the monitoring system, manual call using a telephone network by human hands, and the like.

  The reception system 22 that has received the notification transmits to the maintenance management server 24 information necessary for maintenance work such as the device name received from the notification system 14, its identification key (serial number, etc.), and the failure status.

As a result, the maintenance management server 24 makes an inquiry to the contract information management database 31 based on the current device name and its identification key (serial number, etc.), and whether or not the management target 12 is registered in the contract information management database 31. (Step A1203 ).

When the current management target 12 is registered in the contract information management database 31 (step A1203 “with registration”), the maintenance management server 24 confirms the maintenance contract information corresponding to the management target 12 and whether or not a maintenance contract has been concluded. In addition, it is determined whether or not the management object 12 is a repairable contract (step A1204). If the contract is a contract of impossible repair (step A1204 "impossible"), the procedure goes no to step A1209.

If a maintenance contract is concluded and repairs are possible (step A1204 “possible”), the maintenance management server 24 searches and collects device information. That is, the maintenance management server 24 makes an inquiry to the device information management database 32 based on the device name of the current management target 12 and its identification key (serial number, etc.), and the contract number, user information, device name, and identification key thereof. (Serial number, etc.), configuration information, setting information, maintenance procedure, maintenance part management number, sales vendor information, repair route information, etc. are retrieved and collected (step A1205 ).

After searching the device information management database 32, the maintenance management server 24 makes an arrangement request for replacement parts and confirms an identification key (such as a serial number).
That is, the maintenance management server 24 transmits user information and a maintenance parts management number to the parts management server 53 of the parts delivery network 51, makes a parts delivery request, and confirms the identification key (step A1206). The parts management server 53 searches the parts management database 58 for an identification key (such as a serial number) of the arranged maintenance parts, and transmits it to the maintenance management server 24 together with information on the delivery instruction result .

In addition, the maintenance management server 24 instructs maintenance work to the maintenance worker terminal 16 possessed by the maintenance worker.
That is, the maintenance management server 24 performs maintenance work such as contract number, user information, device name, identification key (serial number, etc.), configuration information, setting information, maintenance procedure, maintenance parts management information, sales vendor information, repair route information, etc. Information necessary for the maintenance is transmitted to the maintenance worker terminal 61, the repair work of the management target 12 is requested, and a work instruction is given to the maintenance worker (step A1207) .

On the other hand, when the management target 12 is not registered in the contract information management database 31 (step A1203 “No registration”), the maintenance management server 24 determines that the management target 12 is not contracted and confirms the shipping source. Then, an inquiry is made to the vendor database 41 based on the current identification key (serial number or the like) to determine whether or not the current management target 12 is registered in the vendor database 41. At this time, if a plurality of shipping sources can exist, a plurality of vendor databases 41 exist for each vendor, and the above inquiry is made for all of them (step A1208) .

  If the current management target 12 is not registered in the vendor database 41 (step A1208 “No registration”), it is determined that the management target 12 is not shipped from any of the vendors and cannot be serviced ( Step A1209), this flow ends.

When the current management target 12 is registered in the vendor database 41 (step A1208 “Registered”), the current management target 12 is determined to have been shipped from the vendor, and the maintenance management server 24 An inquiry is made to the device information management database 32 based on the device name of the management target 12 and the vendor information, and the component management number to be used, the maintenance procedure, etc. are searched (step A1205). As a result, even for the management target 12 not registered in the contract information management database 31, it becomes possible to clarify the sales vendor and search for the corresponding maintenance part number and the like. Implementation becomes possible .

After searching the device information management database 32, the maintenance management server 24 then transmits the user information and the maintenance part management number to the parts management server 53 of the parts delivery network 51 to make a parts delivery request (step A1206). As a result, parts management server 53, and search identification key of maintenance parts to arrange a (serial number, etc.) from the component management database 58, sent along with the information of the delivery instruction result for the maintenance management server 24. The maintenance management server 24 also performs maintenance work such as contract number, user information, device name, identification key (serial number, etc.), configuration information, setting information, maintenance procedure, maintenance parts management information, sales vendor information, repair route information, etc. The information necessary for the maintenance is transmitted to the maintenance worker terminal 61, the repair work of the management target 12 is requested, and a work instruction is given to the maintenance worker (step A1207). Step A1206 and step A1207 are the same as those described above.

The parts management server 53 that has received the parts delivery request from the maintenance management server 24 searches the parts management database 58 from the user information and the parts management number, and stores each warehouse (remote location in each area, the vicinity of the location of the management target 12, etc.). Check the stock status of maintenance parts. And, most preferably, to deliver the service component related to the current maintenance closest warehouse on the location of the user, it intends row and instructions to the component delivery center 54.

  Thus, the maintenance worker can manage the contract number, user information, device name, identification key (serial number, etc.), configuration information, setting information, maintenance procedure, maintenance parts management displayed on the display unit of the maintenance worker terminal 61. By referring to text information necessary for maintenance work such as information, sales vendor information, repair route information, etc., appropriate maintenance work of the management target 12 is performed (step A1210).

  After the maintenance work is completed, the maintenance worker reports the work completion report, that is, the work result report, the management target 12, the replacement maintenance part identification key (serial number, etc.), and information on whether or not the maintenance replacement part is used. From the operator terminal 61 to the maintenance management server 24 (step A1211).

  The maintenance management server 24 that has received the work completion report from the maintenance worker terminal 61 receives information on the identification key (serial number and the like) of the reported management target 12 and the new identification key (serial number and the like) of the replacement maintenance part. It is determined whether or not it matches the information transmitted from the notification system 14 and the component management server 53 (step A1212).

  If the identification keys (serial number, etc.) are different (step A1212 “mismatch”), the maintenance management server 24 again sends the identification key (serial number, etc.) of the management target 12 and alternative maintenance to the maintenance worker terminal 61. Instruction information indicating confirmation (registration) of a new identification key (serial number or the like) of the component is transmitted (step A1213).

If the identification keys (serial numbers and the like) match (step A1212 “match”), the maintenance management server 24 updates the information in the management databases 31, 32, and 33 (step A1214) .

  That is, if the identification keys (serial number, etc.) match (step A1212 “match”), the maintenance management server 24 registers the current work report in the work history management database 33, and sets it as one. Confirms whether or not the replacement maintenance part is used, that is, determines whether or not the current management object 12 has been replaced with the replacement part, and if it is replaced, an identification key (such as a serial number) is entered in the work history management database 33. The change is registered, the identification key (serial number etc.) registered in the contract information management database 31 and the device information management database 32 is rewritten (updated), and the change history is added (step A1214).

  After the rewriting of the identification key (serial number, etc.) is completed, the maintenance management server 24 requests that the vendor database 41 related to the current time update, that is, that the current management target 12 is replaced with a replacement part. In order to inform the sales vendor, the predetermined information such as the identification key (serial number, etc.) before and after the exchange and device information is transmitted to the vendor database 41 (step A1215).

  As a result, the vendor database 41 related this time updates the information of the management target 12 managed by the vendor database 41 (step A1216). If this update causes further processing, it is the vendor's responsibility to do so.

In addition, the contract information management database 31, the device information management database 32, and the vendor database 41 periodically check the consistency of information in each of the management databases 31, 32, and 41 to confirm new addition / change items. Ru preparative integrity. With this operation, it is possible to cope with management information change (contract renewal / cancellation / new installation / removal / new sales etc.) of the management object 12 other than during maintenance work.

  In the present embodiment, a maintenance worker can quickly know whether the management target 12 is a maintenance contract or a license contract, and the vendor destination even without a maintenance contract or a license contract. Information necessary for maintenance of the management target 12 can be obtained, and as a result, it is possible to arrange the delivery and maintenance of devices and parts for maintenance and replacement of the management target 12. In maintenance management, it is possible to improve the reliability of various information to be acquired and improve the reliability and convenience of maintenance management.

  That is, first, since the maintenance contract information of the management target 12 is searched from the contract information management database 31 in advance and transmitted to the maintenance worker together with a work instruction (maintenance request), the maintenance worker It is possible to easily check the maintenance contract information and license information of the management target 12 on the display unit 61 and perform maintenance work according to the contract.

  In addition, if the maintenance service provision method differs depending on the maintenance contract, or there is a management target that requires a license for repairs after concluding a license contract with a sales maker, generally maintenance contract information and licenses are required locally during maintenance work. Although it was difficult to check the information, etc., it was possible to send such information to the maintenance worker terminal 61 in advance, so that the maintenance worker was confused in judging the maintenance work on site. It does not occur, and it is possible to prevent the execution of non-contract work in advance.

  Secondly, since the substitute maintenance part number of the management object 12 is retrieved from the device information management database 32 in advance and transmitted to the parts management server 53 and the maintenance worker terminal 61, the substitution of the management object 12 used for the maintenance work is performed. Maintenance parts can be clearly indicated, and the convenience of maintenance work can be improved.

  In many cases, a sales maker accepts maintenance repairs only for the devices that it sells, but it is difficult for maintenance workers to confirm locally from which sales vendor the management target 12 is sold during maintenance work. For this reason, it is assumed that the replacement maintenance parts and the sales vendors of the management target 12 are different and the maintenance cannot be accepted. However, the management information of the management target 12 and the management numbers of the alternative maintenance parts is previously managed. Since it is registered in the database 32, it is possible to effectively prevent a situation in which, for example, sales vendors are different and it is necessary to take complicated procedures inside and outside the maintenance company.

  In addition, even when the management object 12 is not registered in the device information management database 31, the vendor can be clarified because an inquiry is made to the vendor database 41 based on the identification key (serial number or the like). It is possible to search for an alternative maintenance part management number for the vendor from the device information management database 32 based on the vendor name, and to arrange the delivery of the alternative maintenance part, thereby improving the convenience of maintenance work. it can.

  Third, the maintenance management server 24 obtains the identification key (serial number, etc.) of the management object 12 from the notification system 22 and the management databases 31, 32, 33 in the maintenance management server 24, and identifies the replacement maintenance parts. Recognizing and changing whether or not the replacement maintenance device has been replaced during the maintenance work by obtaining the key (serial number, etc.) from the parts management server 53 and obtaining the result of the maintenance work from the maintenance worker terminal 61 The subsequent identification key (serial number, etc.) can be easily recognized, and as a result, various information (identification key, etc.) can be easily registered and changed in the management databases 31, 32, 33 and the vendor database 41. In the maintenance management of the management object 12, the reliability of various information obtained (acquired) is improved and the maintenance management reliability is improved. It is possible to improve the fine convenience.

  Since an identification key (such as a serial number) is often associated with maintenance contract information and license information, when an exchange operation of the management target 12 occurs during maintenance work, an identification key (such as a serial number) is generally used. However, the change of the identification key (serial number, etc.) is automatically registered (updated) in the management databases 31, 32, 33 in the maintenance management server 24. Therefore, there is no fear of information update (change) omission, and also from this point of view, the reliability of various information to be obtained (acquired) during maintenance management of the management target 12 is improved and the reliability of maintenance management is also improved. In addition, convenience can be improved.

  Fourthly, when the management object 12 is exchanged during the maintenance work, a change (update) of the identification key (serial number, etc.) is automatically made to the management databases 31, 32, 33 in the maintenance management server 24. In order to be reflected, the consistency check of various information including various identification keys (serial numbers, etc.) held by both of the management databases 31, 32, 33 and the vendor database 41 is automatically performed periodically. Therefore, it is always possible to maintain the consistency of information between sales vendors and maintenance companies, and from this point of view, the reliability of various information obtained (acquired) during maintenance management of the management target 12 In addition, the reliability and convenience of maintenance management can be improved.

  Fifth, the maintenance management server 24 searches for the vendor of the management target 12, acquires a new identification key (serial number, etc.) at the time of maintenance replacement of the management target 12, and acquires the device information management database 32 and the vendor database. The contents of 41 are updated, and information such as each identification key (serial number, etc.) held by the maintenance management server 24 and the shipments individually held by a plurality of vendor databases 41 when a predetermined date / time comes regularly And the information update method related to the maintenance management in this example of confirming the consistency with information such as an inventory identification key (serial number, etc.), and the like. In addition to improving the reliability of various types of information acquired during maintenance management, it is possible to improve the reliability and convenience of maintenance management without the need for manual work. That.

It is a conceptual diagram which shows the conceptual structure of the maintenance management system which concerns on embodiment of this invention. It is a block diagram which shows the function structure of the said maintenance management system. It is a block diagram which shows the detailed structure of the said maintenance management system. It is explanatory drawing explaining the content of the contract information management database which concerns on the said embodiment. It is explanatory drawing explaining the content of the apparatus information management database which concerns on the said embodiment. It is a block diagram which shows the detailed structure of the components management server which concerns on the said embodiment. It is a flowchart which shows operation | movement of the notification system which concerns on the said embodiment. It is a flowchart which shows an example of the maintenance management program which operates the said maintenance management server. It is a flowchart which shows an example of the maintenance management program which operates the vendor database which concerns on the said embodiment. It is a flowchart which shows an example of the maintenance management program which operates the said components management server. It is a flowchart which shows an example of the maintenance management program which operates the said maintenance management server or the said vendor database. It is a flowchart which shows the process of the front | former stage of the whole flow of the said maintenance management system. It is a flowchart which shows the latter process of the whole flow of the said maintenance management system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Maintenance management system 11 Management object network 12 Management object 13 Maintenance request means 14 Notification system 21 Management network 22 Reception system 23 Maintenance management means 24 Maintenance management server 25 Maintenance contract confirmation part 26 Vendor search part 27 Maintenance content specification part 28 Maintenance content transmission Unit 29 Information Update Unit 30 Consistency Confirmation Unit 31 Contract Information Management Database 32 Device Information Management Database 33 Work History Management Database 41 Vendor Database 44 Maintenance Content Specific Transmission Unit 51 Parts Delivery Network 52 Parts Delivery Arrangement Means 53 Parts Management Server 54 Delivery Center 55 Transmission / Reception Unit 56 Delivery Arrangement Unit 57 Delivery Instruction Recognition Unit 58 Parts Management Database 61 Maintenance Worker Terminal Nw Network

Claims (14)

Various computer devices and their peripheral devices to which an identification key has been added are subject to maintenance management, and are provided with a CPU and a memory for managing the presence or absence of maintenance of each management target and the corresponding contents via a network, and executed on the CPU A maintenance management server having an application for setting a plurality of maintenance management functions,
Notification that is a failure notification means for detecting the failure of one of the management targets and recognizing the failure content, and then transmitting the identification key of the management target and the failure content related to the failure occurrence to the maintenance management server System,
A maintenance worker terminal having a display screen that operates based on a request from the maintenance management server made via the network and requests a maintenance worker to repair a device to be managed in response to the occurrence of the failure. A maintenance management system,
The components of each managed, identification key, and advance and registered comprising device information management database information relating to sales vendor along with repair information, the device that is contracted as a target of the fault tolerance comprises the managed A contract information management database that is registered in advance together with the contents of the trouble that can be dealt with is provided alongside the maintenance management server via the network,
An identification key recorded in the contract information management database as to whether or not the management target related to the fault is previously contracted as a fault countermeasure target as a function set by the application on the CPU. The contract information determination function for determining based on the presence / absence of a failure, and whether or not the management target is repairable when it is determined that the contract has been made as a target for the failure countermeasure is recorded in the contract information management database It has a failure response determination function to determine based on maintenance contract information,
If this respective determination function by the management target device is determined as serviceable contract a target device and, with respect to the maintenance terminal, as well as requesting the managed repair by the maintenance worker the pre-registered fault condition in the device information management database as information required for repair, identification key, maintenance procedures, or the repair request processing function of transmitting the maintenance part management information, the maintenance management server comprises,
This maintenance management server further
Operates when the management object related to the failure is determined as a failure countermeasure target by the contract information determination function, and is stored in advance from the identification key and stores vendor information that is the shipping source of the management target A vendor search unit that searches the database and searches for managed vendors related to the failure;
If that could search for the vendor, the managed the assumption that the subject of the fault tolerance, vendor name of the managed based on the device name and identification key, maintenance contents registered in advance how certain set transmission, maintenance procedures, maintenance route, associated user information, and maintenance of parts management information, to the device information management and retrieval from the database the maintenance terminal and pre-instrumented parts management server via the network Maintenance content specific transmitter to be
Maintenance management system characterized by having. In the maintenance management system according to claim 1,
2. The maintenance management system according to claim 1, wherein the repair, which is a countermeasure against the failure of the management target device, includes device replacement. In the maintenance management system according to claim 2,
The maintenance management server provides information on the management target device that is a target of failure countermeasures and a maintenance component management number for delivery of parts or devices required for repair including device replacement to a pre-equipped component management server The parts management server searches from a parts information management database equipped in advance with an identification key for a maintenance part that operates and arranges in response to the parts delivery request. A maintenance management system comprising a function of transmitting to the maintenance management server. In the maintenance management system according to claim 1,
A maintenance management system, wherein the vendor database includes a part management number of the management target device and a maintenance procedure manual for maintenance in addition to information related to the management target device. In the maintenance management system according to any one of claims 1 to 4,
The maintenance management server functions when a report indicating that repair as a countermeasure against the failure of the management target device has been performed is received from the maintenance worker terminal, and the identification key of the management target device is updated after the maintenance repair. A maintenance management system comprising an information updating unit for updating to a new identification key and storing it as a next recognition target device. In the maintenance management system according to claim 1,
The maintenance worker terminal server receives, from the maintenance worker, an identification key for each of the management target device and the replacement maintenance component, and whether or not the replacement maintenance component is used, as a completion report of repair work that is a countermeasure against the failure of the management target device. And the function of transmitting these to the maintenance management server, and the maintenance management server identifies each of the management target device and replacement maintenance parts sent together with the report from the maintenance worker terminal server. An identification key confirmation function for confirming whether the key and the identification key sent from the parts management server match,
A maintenance management system comprising a function of registering the work report in a work history management database separately provided in advance when the identification keys match. In the maintenance management system according to claim 4,
The maintenance management server has a consistency check function for periodically checking the consistency of the contract information management database, the device information management database, and the vendor database to ensure consistency for newly added or changed items. A maintenance management system characterized by In the maintenance management system according to claim 3,
The component management server receives at least information on an identification key of the device to be managed, checks whether there is a device corresponding to the identification key and whether the component is in stock based on the recorded contents of the component information management database, and the device A delivery arrangement processing unit that arranges delivery of parts and parts, and a delivery instruction recognition unit that recognizes an instruction result of delivery arrangement by the delivery arrangement processing unit and transmits the instruction result to the maintenance management server. A featured maintenance management system. Various computer devices and their peripheral devices to which an identification key has been added are subject to maintenance management, and are provided with a CPU and a memory for managing the presence or absence of maintenance of each management target and the corresponding contents via a network, and executed on the CPU A maintenance management server having an application for setting a plurality of maintenance management functions,
Notification that is a failure notification means for detecting the failure of one of the management targets and recognizing the failure content, and then transmitting the identification key of the management target and the failure content related to the failure occurrence to the maintenance management server System,
A maintenance worker terminal having a display screen that operates based on a request from the maintenance management server made via the network and requests a maintenance worker to repair a device to be managed in response to the occurrence of the failure. In the maintenance management system,
When a failure occurs in one device to be managed, the notification system as the failure notification means detects the failure, and the maintenance management server uses the detected failure content and identification key of the management target as failure information. Notify
The maintenance operator terminal requests the maintenance operator via the display screen to perform repair that is a countermeasure against the failure of the managed device that operates based on the request from the maintenance management server,
Prior to requesting a repair to the maintenance worker using this maintenance worker terminal,
The maintenance management server determines whether or not the management target related to the fault is a contract target apparatus that has been previously contracted as a fault countermeasure target, based on the content recorded in the contract information management database separately provided,
When it is determined that the management target related to the fault is contracted as the target of the fault countermeasure, whether or not the management target is repairable is determined based on the recorded contents of the contract information management database. The server determines,
If this the managed than the result of the determination shall serviceable contract a target device and, the maintenance management server, requesting the managed repair by the maintenance worker to the maintenance terminal while, failure status is information necessary maintenance work relating to the repair, identification key, maintenance procedures, or maintenance parts management information registered beforehand and the failure status from the hotel to the apparatus information management database in the maintenance server The identification key, the maintenance procedure, or the maintenance part management information is extracted and transmitted to the maintenance worker terminal,
The maintenance management server determines whether or not the management target related to the failure is a contract target device, and functions when the management target related to the failure is determined to be a non-contract as a target for the failure countermeasure and is equipped in advance Based on the identification key of the management target related to the failure by the vendor search unit of the maintenance management server, the vendor of the management target that is not contracted related to the failure from the vendor database storing the vendor information that is the shipping source of the management target. Explore
When the vendor can be searched by the maintenance management server, it is pre-registered based on the vendor name, device name and identification key of the management target on the assumption that the management target is the target of the failure countermeasure. The maintenance content specifying transmission unit of the maintenance management server retrieves the setting method, maintenance procedure, maintenance route, related user information, and maintenance parts related information as the maintenance content from the device information management database and retrieves it via the network. A maintenance management method characterized by transmitting to the maintenance worker terminal and a parts management server equipped in advance. The maintenance management method according to claim 9,
If it is determined that the management target is a contract target device and can be repaired during the determination operation by the maintenance management server, the maintenance worker terminal requests the maintenance worker to repair the management target. Prior to
The maintenance management server makes an inquiry to the device information management database to collect maintenance procedure and maintenance part management number information related to the management target, and the maintenance management server collects information about the collected management target device. Send to the parts management server to execute a substitute parts arrangement request,
Subsequently, the maintenance management server receives the information regarding the identification key of the arranged maintenance parts and the delivery instruction result sent from the parts management server,
A maintenance management method characterized in that the maintenance management server executes the repair request for the management target thereafter. The maintenance management method according to claim 9,
It functions when the maintenance operator inputs each identification key of the management target and the replacement maintenance part, and whether or not the use of the replacement maintenance part is input from the maintenance worker as a completion report of repair work that is a countermeasure against the management target. The maintenance worker terminal server transmits to the maintenance management server,
The maintenance management server determines whether or not the identification keys of the management object and the replacement maintenance parts sent together with the report from the maintenance worker terminal server match the identification keys sent from the parts management server. Confirms
A maintenance management method, wherein the maintenance management server registers the work report in a work history management database separately provided in advance when the identification keys match. Various computer devices and their peripheral devices to which an identification key has been added are subject to maintenance management, and are provided with a CPU and a memory for managing the presence or absence of maintenance of each management target and the corresponding contents via a network, and executed on the CPU A maintenance management server having an application for setting a plurality of maintenance management functions,
Notification that is a failure notification means for detecting the failure of one of the management targets and recognizing the failure content, and then transmitting the identification key of the management target and the failure content related to the failure occurrence to the maintenance management server System,
A maintenance worker terminal having a display screen that operates based on a request from the maintenance management server made via the network and requests a maintenance worker to repair a device to be managed in response to the occurrence of the failure. In the maintenance management system,
It functions when the failure information is sent from the notification system that has detected a failure in one of the managed devices, and the management target related to the failure is contracted in advance as a failure countermeasure target A contract information determination processing function for determining whether or not it is a contract target apparatus based on the recorded contents of a contract information management database equipped in advance,
Failure handling determination processing function for determining whether or not the management target can be repaired based on the recorded contents of the contract information management database when the management target related to the fault is contracted as a target for fault countermeasures ,
When each of the determination processing functions determines that the management target is a contract target device and can be repaired, the maintenance worker terminal requests the maintenance worker to repair the management target , and The failure status, identification from the device information management database in which the failure status, identification key, maintenance procedure, or maintenance parts management information, which is information necessary for the maintenance work related to repair, is registered in advance and attached to the maintenance management server in advance. key, maintenance procedures, or repair request processing capability for transmitting removed maintenance component management information to the maintenance terminal,
In determining managed according to the failure of whether contracted device, shipped managed according to the failure to function when it is determined that the non-contract as the object of the fault tolerance, equipped pre Me of the managed the vendor retrieves the vendor database storing the vendor information is based according to the managed device according unsigned in the fault, the vendor specific processing function identified based on the identification key of the managed according to the fault,
If the vendor is specified, the maintenance contents registered in advance based on the vendor name, device name, and identification key of the management target, assuming that the management target is the target of the failure countermeasure. The setting method, maintenance procedure, maintenance route, related user information, and maintenance parts management information are retrieved from the device information management database and sent to the maintenance operator terminal and the parts management server equipped in advance via the network . Provide repair information transmission processing function to send,
A maintenance management program characterized in that each processing function is realized by a computer provided in the maintenance management server. The maintenance management program according to claim 12,
When it is determined by execution of the contract information determination processing function and the failure handling determination processing function that the management target is a contract target device and can be repaired, the maintenance worker terminal is contacted by the maintenance worker terminal. Prior to the repair request for the management object,
Inquiries to the device information management database to collect maintenance procedure and maintenance part management number information related to the management target, and send the collected information related to the management target to the parts management server to request replacement parts Provide a parts delivery request processing function to be executed,
When the information regarding the identification key of the arranged maintenance parts and the delivery instruction result is sent from the parts management server, the information is received, and then the repair request processing function for the management target is sent to the computer. A maintenance management program characterized by being realized. The maintenance management program according to claim 12,
As the completion report of the repair work that is a countermeasure against the failure of the management target, the identification key of the management target and the replacement maintenance part by the input of the maintenance worker, and the presence / absence of the use of the replacement maintenance part are sent via the maintenance worker terminal server Repair completion report reception processing function to receive this when it is sent to the maintenance management server,
Whether the identification keys of the management object and the replacement maintenance part sent together with the report from the maintenance worker terminal server match the identification key related to the management object sent separately from the parts management server Confirmation key confirmation processing function,
And a work history registration processing function for registering the work report related to the device to be managed in a work history management database separately provided in advance when these identification keys match, and causing the computer to realize them. A maintenance management program characterized by doing so.

Images