JP5658065B2 - Maintenance parts arrangement method and system - Google Patents

Description

  The present invention relates to a method and system for arranging maintenance parts, and more particularly, when a critical trouble report is received from a customer's system with a maintenance contract and an important replacement part is not in stock in the parts warehouse, for other matters. Parts that have already been paid out and stored by other maintenance personnel and parts that can be transferred to this case from among parts that have already been paid out to resolve other cases and that are requested to be transferred The present invention relates to an arrangement method and system.

  When a failure occurs, a system has been devised that predicts the cause of the failure, identifies the suspected component, and has a stock of suspected components and requests shipping to a component warehouse near the failure site. However, if the parts warehouse is not in stock, new parts must be ordered or shipped from a parts warehouse at a long distance, and it may take time to recover from the failure.

  On the other hand, although it has already been paid out from the parts warehouse in order to solve a problem, there are cases where the parts are not used and are present at the maintenance staff because the cause of the problem is different from the prediction. In this case, it will be returned to the parts warehouse at a later date, but may have been left at the maintenance personnel for a long period of time. In such a case, there is no parts inventory in the parts warehouse, but it would be convenient if the unused parts at hand of the maintenance staff could be diverted immediately.

  In addition, when a failure occurs, the cause of the failure is predicted and the suspected component is specified. However, the suspected component is not usually brought with a single type, but usually the suspected component use prediction accuracy of 70%, the suspected component usage prediction In many cases, a plurality of parts are taken, such as parts with an accuracy of 30%. For example, the phenomenon that the power cannot be turned on is most likely to be recovered by replacing the power supply device, but there may be a problem with the fan or the power cable. For that purpose, it is desirable to bring not only the power supply device but also all possible replacement parts such as fans and power cables to the site.

  For example, for a case with a low use prediction accuracy for case A, the case with a high use prediction accuracy in case of suspected parts use is higher than the case (B case) in another failure case (B case) (B case) It would be more convenient to divert the part to. Therefore, even if the suspected part is being delivered by a truck of a shipping company, it may be better to change the notification destination.

  In this type of conventional system, when a failure occurs in the user computer 10, failure information is notified from the user computer 10 to the failure analysis system 20 via the communication network 100, and failure analysis is performed based on the notified information. As a result of the analysis, there is known a system that notifies the parts management system 30 of necessary suspicious parts information, arranges suspicious parts, and sends them to the user (for example, Patent Document 1).

JP 2001-306360 A (paragraphs 0011 to 0017, FIG. 1)

  The present invention has been made in view of such a problem, and there are no parts required for failure recovery in the parts warehouse. However, when the parts are in the hands of other maintenance personnel, Therefore, if it is considered that the part should be applied with priority to the current trouble case, the part can be repaid for the current trouble recovery. It is an object of the present invention to provide a maintenance part arrangement method and system capable of realizing a simple mechanism.

  In order to solve the above-described problems, the present invention has the following configuration.

(1) The invention described in claim 1 is a failure reception server, a database for storing various tables connected to the failure reception server, a failure reception means for receiving a failure notification, a parts supplier company server, and a failure importance level A fault acceptance table in which fault acceptance information including a fault is registered, a fault response part table in which a replacement part is predicted to be replaced according to the content of the fault, and a parts search for searching the inventory by predicting the replacement part and means, connected to the said part supply company server, and parts warehouse management table for storing the payout destination and inventory of the replacement part, and the part arrangement means for parts of the arrangements, to dispensing destination at which maintenance personnel component transport and parts transfer request means for transmitting a shipment request of the parts, and the delivery company server, and the customer system that emits a failure notification in the event of a failure, and the maintenance staff mobile terminal, the parts Te That a transportation Okukuruma terminal is mounted on the transporter, but more systems connected to each other via a network, maintenance parts arrangement method Oite for managing maintenance parts in order to arrange the parts in the fault occurrence point, the fault accepted Means for receiving a failure notification from the customer system and registering failure reception information including failure importance in the failure reception table; and referring to the failure handling component table, the component search means is replaced from a failure phenomenon a step of predicting the component, and a step of arranging the replacement part in which the component arrangement section is predicted when the failure is less the fault severity registered in reception table, registered in the failure reception table the in case of a high fault severity, the component the component arrangement section when referring to contents of the warehouse management table is in stock the replacement part to the parts warehouse Search a step of arranging, the if there is no component inventory parts referring to the contents of the warehouse management table parts warehouse, a payout destination the component search means for said replacement parts and same components the predicted the replacement part a step of, the payout destination retrieved the Ri other maintenance personnel der, if the fault severity in matters where the same part is assigned is low, part transfer request means of said other maintenance personnel And a step of transmitting a request for shipping the same part to the maintenance worker portable terminal .

(2) The invention according to claim 2 is a payout parts management table for managing whether the state of the parts being paid out is being stored by another maintenance staff or being transported for other work, and the other Parts arrival time comparison means that calculates and compares the arrival time to the point of failure due to parts delivery from the maintenance staff and the arrival time to the point of failure due to the change of the delivery destination of the parts being transported, and paying out In a system further connected to a delivery destination change request means for transmitting a delivery destination change request for the part to a transport vehicle that is transporting the parts, the maintenance parts are managed so as to arrange the parts at the failure occurrence point. A method for arranging maintenance parts, wherein the status of the same parts is stored by another maintenance staff at the delivery destination with reference to the contents of the delivered parts management table, or is being transported for other work Before A step component search unit searches, said payout destination at which other maintenance personnel have to store the same components, when the fault severity in matters where the same part is assigned is low, the other a step of the arrival time from the maintenance personnel to arrive in failure occurrence point and ships the same component the component arrival time comparison means for calculating, the same parts are transportation Okunaka for other operations, the same When the failure importance is low in another work item to which a part is assigned, the part arrival time comparison means calculates the arrival time until the delivery destination of the part being transported changes and arrives at the failure occurrence point. compares the process of calculation, and the arrival time of up to failure point by the dispatch of parts from the other maintenance personnel, and the arrival time of up to failure point by the destination change of parts during transportation by the transport vehicle In response to the step of determining the parts arrival time comparing means to arrive in any one of the short time, and the sending determined to arrive at the failure occurrence point in any of the short times, the parts transfer requesting means, Transmitting a parts dispatch request to the maintenance staff portable terminal of another maintenance staff or transmitting a delivery destination change to the transport vehicle terminal .

(3) The invention described in claim 3 is a failure reception server, a database for storing various tables connected to the failure reception server, a failure reception means for receiving a failure notification, a parts supplier company server, and a failure importance level A fault acceptance table in which fault acceptance information including a fault is registered, a fault response part table in which a replacement part is predicted to be replaced according to the content of the fault, and a part search means for predicting the replacement part and searching for inventory When it is connected to the component supply company server, and parts warehouse management table for storing the payout destination and inventory of the replacement part, and the part arrangement means for parts of the arrangements for maintenance personnel a payout destination component and parts transfer request means for transmitting a shipment request of the parts, and the delivery company server, to transport and customer system that emits a failure notification in the event of a failure, and the maintenance staff mobile terminal, the parts And transportation Okukuruma terminal is mounted on the transporter, but are connected via a network, respectively, keep maintenance parts dispatch system for managing maintenance parts in order to arrange the parts in the fault occurrence point, the fault receiving unit, the customer When receiving the failure notification from the system, the aforementioned fault register the fault reception information including the failure severity in reception table, the component search means refers to the failure handling parts table predicts the replacement part from failure symptom, The parts warehouse management table is referenced to search for a parts warehouse that holds the inventory of the replacement parts, and when there is no inventory in the parts warehouse, the payout destination is searched for the same parts as the replacement parts, and the parts arrangement means , the have rows of parts arranged for predicted the replacement part when failure the fault severity registered in the reception table is low, the failure reception table Even when high the fault severity registered in the if there is a part with reference to inventory parts and contents of the warehouse management table, rows that have the component arrangement, the component transfer request means is retrieved the payout destination other maintenance personnel der was is, if the fault severity in matters where the same part is assigned is low, sending the same part in the maintenance staff mobile terminal of the other maintenance personnel to send a request, and wherein a call.

  According to the present invention, the following effects can be obtained.

  (1) According to the first aspect of the present invention, there are no parts required for failure recovery in the parts warehouse, but the parts are already in the hands of other maintenance personnel or have already been paid for solving other trouble cases. Realized a mechanism that allows the parts to be repaid for recovery from the current failure when it is considered that the parts should be preferentially applied to the current failure case. can do.

  (2) According to the invention described in claim 2, when there is no maintenance part in the warehouse, and when another maintenance person has the part, the maintenance person transfers the part. Compare the arrival time and the arrival time when the delivery destination is changed when the part is being delivered, and select the method to reach the fault occurrence point earlier. Supply can be performed promptly.

  (3) According to the invention described in claim 3, there are no parts required for failure recovery in the parts warehouse, but the parts are already in the hands of other maintenance personnel or have already been paid for solving other trouble cases. Realized a mechanism that allows the parts to be repaid for recovery from the current failure when it is considered that the parts should be preferentially applied to the current failure case. can do.

It is a block diagram which shows one Example of this invention. It is a figure which shows the structural example of a customer table. It is a figure which shows the structural example of an important fault judgment table. It is a figure which shows the structural example of a maintenance worker table. It is a figure which shows the structural example of a parts warehouse address table. It is a figure which shows the structural example of a parts warehouse management table. It is a figure which shows the structural example of a payout components management table. It is a figure which shows the structural example of a failure reception table. It is a figure which shows the structural example of a failure response component table. It is a figure which shows the structural example of a transfer time comparison table. It is a figure which shows the structural example of a components allocation management table. It is a figure which shows the structural example of a transport vehicle management table. It is a flowchart which shows operation | movement of a failure reception server. It is a flowchart which shows operation | movement of a failure reception server. It is a flowchart which shows operation | movement of a failure reception server. It is a flowchart which shows operation | movement of a delivery company server.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of the present invention. In the figure, 1 is a customer system, and 2 is a failure reception server that receives failure information from the customer system 1 and performs failure reception control. The failure reception server 2 includes a failure reception unit 21, a component search unit 22, a component arrival time comparison unit 23, a component arrangement unit 24, a component transfer request unit 25, and a delivery destination change request unit 26.

  A database (DB) 3 is connected to the failure reception server 2 and stores various tables. The database 3 includes a customer table 31, an important fault determination table 32, a maintenance staff table 33, a parts warehouse address table 34, a payout parts management table 35, a fault reception table 36, a fault handling parts table 37, a transfer time comparison table 38, parts. It consists of an allocation management table 39 and a transport vehicle management table 40.

  Reference numeral 4 denotes a parts supplier company server that performs parts supply processing, and reference numeral 5 denotes a parts warehouse management table that stores management information of parts in a warehouse connected to the parts supplier company server 4. 6 is a maintenance worker portable terminal, 7 is a delivery company server, and 8 is a transport vehicle terminal. Reference numeral 10 denotes a network for connecting these components. As the network 10, for example, the Internet, an ISDN network, a LAN, or the like is used. The delivery company server 7 includes transport status management means 71, and the transport vehicle terminal 8 includes a GPS device 81. For example, a personal computer is used as the failure reception server 2, the parts supplier company server 4, and the delivery company server 7.

  Next, the configuration of various tables stored in the database 3 will be described. FIG. 2 is a diagram illustrating a configuration example of the customer table 31. As shown in the figure, it comprises a customer name, a customer rank, a system scale, a customer address, and a customer e-mail address. Here, the customer rank is distinguished by, for example, the amount of transaction. For example, a distinction is made between “normal customers” and “royal customers”. Royal customers are high volume customers.

  FIG. 3 is a diagram showing a configuration example of the critical fault determination table 32. As shown in the figure, it is composed of a customer rank, a system scale, and a failure importance. Here, the system scale is the scale of the system, and is classified into a “normal system” that is a normal scale and a “social system” that is a large scale. FIG. 4 is a diagram illustrating a configuration example of the maintenance staff table 33. As shown in the figure, it is composed of a maintenance staff name, an e-mail address, and a section address.

  FIG. 5 is a diagram showing a configuration example of the parts warehouse address table 34. As shown in the figure, it is composed of a warehouse name, a jurisdiction area, and an address. FIG. 6 is a diagram showing a configuration example of the parts warehouse management table 5. As shown in the figure, it is composed of the part name, part type name, target device type name, warehouse name where the part is stocked, part manufacturing NO, inventory availability, payout date, and payout destination. Has been.

  FIG. 7 is a diagram showing a configuration example of the payout part management table 35. As shown in the figure, it is composed of a part name, a part model name, a target device model name, a manufacturing NO, a failure reception number, a prediction accuracy, a maintenance engineer, a status, and a current location. . Here, the prediction accuracy refers to the possibility that the part is a replacement part. The status indicates what state the part is currently in.

  FIG. 8 is a diagram illustrating a configuration example of the failure reception table 36. As shown in the figure, it is composed of a failure reception number, a reception date, a reception time, a customer name, a device model name, a failure phenomenon, and a failure importance. FIG. 9 is a diagram illustrating a configuration example of the failure handling component table 37. As shown in the figure, it is composed of a phenomenon, replacement parts, and prediction accuracy. For example, when the phenomenon is “abnormal sound”, “fan” and “main board” can be considered as replacement parts, and the corresponding probability (predictive accuracy) of these “fan” and “main board” is “fan”. In the case of “main board”, it is low.

FIG. 10 is a diagram illustrating a configuration example of the transfer time comparison table 38. As shown in the figure, it is composed of a failure reception number, a part model name, a manufacturing NO, a maintenance staff possession transfer time, and a parts transfer time during transportation. Here, the maintenance worker possession transfer time, if the maintenance personnel had the part, said at the time it takes until reclassified to the failure point, transport in the part transfer time, the failure of the part during transport Indicates the time taken to transfer to a point .

FIG. 11 is a diagram illustrating a configuration example of the component allocation management table 39. As shown in the figure, the failure reception number, the replacement part circle 1, the manufacturing NO (part round 1), the replacement part round 2, the manufacturing NO (part round 2), the replacement part round 3, and the manufacturing NO (parts) 3). As is apparent from the figure, the manufacturing NO is assigned to each replacement part. In the figure, the replacement part circle 2 is the manufacturing NO “F11111” of the part circle 2 for “FAN506” and the replacement part circle 1 is the replacement part circle. The case where “FAN506”, which is 1, is applied. FIG. 12 is a diagram illustrating a configuration example of the transport vehicle management table 40. As shown, it is composed of a failure receipt number, and transportation Okukuruma number, and transportation Okukuruma E-mail.

  The operation of the system shown in FIG. 1 configured as described above will be described as follows. 13 to 15 are flowcharts showing details of the operation of the failure reception server 2, and FIG. 16 is a flowchart showing the operations of the delivery company server. First, the operation of the failure reception server 2 in FIGS. 13 to 15 will be described.

  When the failure reception means 21 receives the failure notification mail from the customer system 1 (S1), the failure reception information is registered in the failure reception table 36 (S2). After that, the parts search means 22 searches the failure handling parts table 37, determines the parts required according to the failure phenomenon, and refers to the parts warehouse management table 5 from the parts supplier company server 4 for the parts concerned. The corresponding parts warehouse that holds is searched (S3).

  Then, it is checked whether there is a stock part in the warehouse (S4). If there are parts in stock, the parts arrangement means 24 requests parts arrangement (S7). In step S4, if there is no inventory part, it is checked whether or not the matter is an important failure (S5). If it is not an important failure, the parts arrangement means 24 requests parts arrangement (S7). If the case is an important fault, the fault receiving server 2 checks whether the part has high prediction accuracy of the critical fault judgment (S6). If it is not a part with high prediction accuracy, a part arrangement request is made (S7). If the part has high prediction accuracy, the process skips to step S16. When making a parts arrangement request in step S7, the parts arrangement unit 24 checks whether or not all the predicted replacement parts have been arranged (S8). If all predicted replacement parts have been arranged, the process ends (to circle 4). If all predicted replacement parts have not been arranged, the process skips to step S3.

  If it is determined in step S1 that the failure notification mail has not been received, it is checked whether or not a component delivery notification has been received from the component supplier server 4 (S9). When there is a notification of part delivery, the part is registered as information in the delivery part management table 35, and the status is set to [in transit] (see FIG. 7). Next, information is registered in the transport vehicle management table 40 (S11).

  Next, in step S9, when there is no notification of component delivery, it is checked whether there is a notification of the completion of the component transportation from the component supplier server 4 (S12). When there is a notification of the completion of the transportation of the parts, the maintenance staff will receive the parts, so the status of the paid-out parts management table 35 is updated to [maintaining maintenance staff] (S13).

  In step S12, if there is no notification of the completion of the transportation of the component from the component supplier server 4, it is checked whether or not there is a status change notification of the component being stored from the maintenance staff (S14). If there is a status change notification, the status of the payout component management table 35 is updated to [corresponding] (S15).

  In step S6, when it is a component with high prediction accuracy, it skips to step S16. In step S16, it is searched whether there is the same part stored by the maintenance staff (S16). Then, it is checked whether there is the same replacement part among the available parts stored by the maintenance staff (S17). If there is not, the parts arranging means 24 searches whether there is the same part as the part that is being transported for other work (S22). If there is, it is checked whether or not the case to which the part is assigned is an important failure (S18).

  If it is not an important failure in step S18, the parts arrangement unit 24 checks whether the prediction accuracy of the parts in the case is high (S19). Whether or not the prediction accuracy is high is determined by searching the payout parts management table 35 in the database 3. If the prediction accuracy is high, the process skips to step S22 and shifts to processing for searching for the same part for parts in the transport vehicle.

  In step S19, when the predicted accuracy of the part is low, the part arrival time comparison means 23 calculates the time required for the maintenance staff to transport the part to the failure site, and stores it in the transfer time comparison table 38. Register (S20). Thereafter, it is checked whether all calculations for the same part have been performed (S21). If not completed, the process skips to step S17 and repeats the operation of checking whether there is the same replacement part.

  When searching for a part that the part is transporting for other work (S22), the part searching means 22 checks whether there is the same part being transported (S23). If there is no identical item, skip to step S29. If there is the same replacement part, it is checked whether or not the matter to which the part is assigned is an important fault with reference to the important fault judgment table 32 (S24).

  If it is an important failure, the process skips to step S28. If it is not an important failure, it is checked whether or not the prediction accuracy of the part in the case is high (S25). If the prediction accuracy is high, the process returns to step S24. When the prediction accuracy is low, the failure reception server 2 inquires the delivery company server 7 about the current time point of the vehicle being transported and updates the latest information (S26). Next, the time until the parts arrive is calculated and registered in the transfer time comparison table 38 (S27).

  Next, it is checked whether all calculations for the same part have been performed (S28). If all calculations for the same part have not been performed, the process returns to step S24. If all calculations for the same part have been performed, the process proceeds to step S29.

  In step S29, it is checked whether there is data registered in the failure handling component table 37 of the database 3 (S29). If there is no data registered in the failure handling parts table 37, the parts arranging unit 24 arranges the parts (S35). If there is data in the failure handling parts table 37, the parts arrival time comparison means 23 compares the case of shipping from the parts being stored by the maintenance staff (* 1) and the case of shipping from the transport vehicle (* 2). Thus, the route with the shortest estimated arrival time is determined (S30).

If the determined route is shipping from a part being stored by the maintenance staff, the parts transfer request means 25 transmits a parts shipping request mail to the maintenance staff (S31). If the determined route is shipping from the transport vehicle, the parts transfer request means 25 performs parts delivery destination change processing (S32). Thereafter, the delivery destination change request means 26 transmits a delivery destination change mail to the transport vehicle terminal 8 of the transport vehicle driver (S33). Exports Okukuruma terminal 8 receives this email.

  Thereafter, the part transfer process information is registered in the part allocation management table 39 (S36). Taking the case of the table shown in FIG. 11 as an example, the part having the manufacturing NO of replacement part (2) F11111 is moved to the place of the manufacturing NO of replacement part (1) being F11111. This completes the part transfer process. Next, the failure reception server 2 checks whether or not all the predicted replacement parts have been arranged (S37). When all the predicted replacement parts have been arranged, the process returns to step S1. That is, a series of processing is completed. If all of the predicted replacement parts have not been arranged, the process returns to step S3, and the parts warehouse is searched for the parts that are required according to the failure phenomenon.

  FIG. 16 is a flowchart showing the operation of the delivery company server 7. First, current position information is acquired from a transport vehicle at regular intervals (S1). Next, it is checked whether or not there is an inquiry about the current position of the transport vehicle (S2). When there is an inquiry, the current position information of the transport vehicle is returned to the failure reception server 2 (S3). When the failure reception server 2 receives this information, the component arrival time comparison means 23 uses it as position information for calculating the time for delivering the component to the failure site of the system.

  In the above-described embodiment, the case where the maintenance parts are arranged has been described. However, the present invention is not limited to this, and the present invention can be similarly applied to the case where the goods at a certain point or the goods are out of stock. it can.

  As described above, according to the present invention, the parts required for the failure recovery are not in the parts warehouse, but the parts are already paid out to solve other trouble cases when the parts are in the hands of other maintenance personnel. It is possible to realize a mechanism that allows the parts to be paid out again for the current fault recovery when the parts are considered to be applied in preference to the current fault case. .

  In addition, if there are no maintenance parts in the warehouse, and other maintenance personnel have the parts, the arrival time when the parts are transferred from the maintenance staff and the parts being delivered When there is such a part, it is possible to quickly supply the maintenance part by comparing the arrival time when the delivery destination is changed and selecting a method of reaching the failure occurrence point earlier.

DESCRIPTION OF SYMBOLS 1 Customer system 2 Fault reception server 3 Database 4 Parts supplier company server 5 Parts warehouse management table 6 Maintenance worker portable terminal 7 Delivery company server 8 Transport vehicle terminal 10 Network

Claims (3)

Fault reception server in which fault reception server, database for storing various tables connected to the fault reception server, fault reception means for receiving fault notification, parts supplier company server, fault reception information including fault severity are registered Connected to the parts supplier server , the parts corresponding to the trouble part table in which the spare parts to be replaced according to the contents of the trouble are registered, the parts search means for predicting the replacement parts and searching the inventory , A parts warehouse management table that stores the inventory of the replacement parts and a payout destination, a parts arrangement means for arranging parts, and a parts transfer that sends a dispatch request for the parts to the maintenance staff that is the payout destination of the parts and request means, and the delivery company server, and the customer system that emits a failure notification in the event of a failure, and the maintenance staff mobile terminal, transportation Okukuruma to be attached to the transport vehicles to transport the parts End and, but more systems connected to each other via a network, maintenance parts arrangement method Oite for managing maintenance parts in order to arrange the parts in the fault occurrence point,
A step of receiving a failure notification from the customer system by the failure reception means and registering failure reception information including a failure importance level in the failure reception table ;
A step of referring to the failure handling component table and predicting a replacement component from the failure phenomenon by the component search means ;
A step of arranging the replacement part parts transfer request means is predicted when the failure severity registered in the failure reception table is low,
In the case where the failure importance level registered in the failure reception table is high, if the replacement parts are in stock in the parts warehouse with reference to the contents of the parts warehouse management table, the parts transfer request means is predicted. and a step to arrange a replacement part,
When there is no inventory part in the parts warehouse with reference to the contents of the parts warehouse management table, the parts search means searches for a payout destination for the same parts as the replacement parts;
The payout destination retrieved the Ri other maintenance personnel der, if the fault severity in matters where the same part is assigned is low, the the component transfer request means other maintenance personnel the maintenance personnel the portable Sending a shipment request for the same part to the terminal ;
A method for arranging maintenance parts, comprising: Discharge part management table for managing whether the state of parts being paid out is being stored by other maintenance personnel or being transported for other work, and failure occurs due to the delivery of parts from the other maintenance staff Parts arrival time comparison means to calculate and compare the arrival time to the point and the arrival time to the point of failure due to the change of the delivery destination of the parts being transported, and the parts being paid out to the transporting vehicle being transported In a system further connected to a delivery destination change request means for sending a delivery destination change request for the part, a maintenance parts arrangement method for managing maintenance parts to arrange a part at a failure occurrence point,
With reference to the contents of the dispensed part management table, the parts retrieval means retrieves whether the state of the same part is being stored by another maintenance staff at the delivery destination or being transported for another work. Process,
Said and other maintenance personnel are payout destination and store the same components, when the fault severity in matters where the same part is assigned a low, ships the same component from the other maintenance personnel The process of calculating the arrival time until the arrival at the failure occurrence point by the parts arrival time comparison means ;
The same parts are transportation Okunaka for other operations, if the fault severity in other work projects the same component is assigned a low, change the destination of the part during the transportation failure A step of calculating the arrival time until arrival at the point of occurrence by the parts arrival time comparison means ;
Compare the arrival time to the point of failure due to the delivery of parts from the other maintenance staff and the arrival time to the point of failure due to the change of the delivery destination of the parts being transported by the transport vehicle. The part arrival time comparing means determining an incoming shipment; and
In response to the dispatch determined to arrive at the failure occurrence point in any short time, the parts transfer request means transmits a parts dispatch request to the maintenance staff mobile terminal of the other maintenance staff or Sending a delivery address change to the transport vehicle terminal ;
The method for arranging maintenance parts according to claim 1, further comprising: Fault reception server in which fault reception server, database for storing various tables connected to the fault reception server, fault reception means for receiving fault notification, parts supplier company server, fault reception information including fault severity are registered A table, a failure response part table in which replacement parts that are predicted to be replaced according to the content of the failure are registered, a part search unit that predicts the replacement parts and searches for inventory, and the parts supplier company server , A parts warehouse management table that stores the inventory of the replacement parts and the payout destination, a parts arrangement means for arranging parts, and a parts transfer request for sending a dispatch request for the parts to the maintenance staff that is the payout destination of the parts means and, and the delivery company server, and the customer system that emits a failure notification in the event of a failure, and the maintenance staff mobile terminal, transportation Okukurumatan to be attached to the transport vehicles to transport the parts When, but are connected via a network, respectively, keep maintenance parts dispatch system for managing maintenance parts in order to arrange the parts in the fault occurrence point,
The failure acceptance means is
Upon receipt of the failure notification from the previous SL customer system, it registers a fault acceptance information, including the failure importance to the failure reception table,
The component search means includes
When a replacement part is predicted from a failure phenomenon by referring to the failure correspondence part table, a part warehouse holding the replacement part stock is searched by referring to the part warehouse management table, and the part warehouse has no stock Search for the payout destination for the same part as the replacement part ,
The parts arranging means is
The have rows of parts arranged for predicted the replacement part when failure is low the fault severity registered in the reception table,
Wherein in a case fault the fault severity registered in the reception table is high, the if there is a part with reference to inventory parts and contents of the warehouse management table rows that have a component arrangements,
The parts transfer request means
The payout destination retrieved the Ri other maintenance personnel der, if the fault severity in matters where the same part is assigned is low, the same parts in the maintenance staff mobile terminal of the other maintenance personnel Send a shipping request for
Maintenance parts dispatch system, wherein a call.

Images