JP4795093B2 - Maintenance destination selection method and maintenance destination selection program - Google Patents

Description

  The present invention relates to a maintenance destination selection method and a maintenance destination selection program for receiving a maintenance request for an apparatus and requesting maintenance from a corresponding maintenance company.

  Conventionally, the maintenance management company that manages the company repairs from the related maintenance companies that have contracted in advance if a failure occurs in a computer or other device installed at the customer company and a repair request is received by telephone or e-mail. The most suitable maintenance company was selected and the repair request was made.

In addition, based on the failure information from the network monitoring device, if the failure information is of high importance, the failure recovery and failure location are checked against the location of each maintenance company and the service provision time. There is a technique for selecting an optimal maintenance person from a plurality of maintenance companies registered in advance (Patent Document 1).
Japanese Patent Laid-Open No. 06-237250

  In the former technique described above, select the most suitable maintenance company to repair by telephone, check whether the maintenance company can accept the repair by telephone, and if not, select the next most suitable maintenance company. As a result, there is a problem that it is not easy to find an incentive to improve the service in order to place an order for repair.

  Also, in the latter technique described above, the maintenance company in charge of coordinating calls the maintenance company in charge of the optimal repair to make a repair request, and the related maintenance company is passive, so let's improve the service. There was a problem that the incentive to say was difficult.

  In order to solve these problems, the present invention notifies the maintenance bid request to the area in charge of repair and a qualified maintenance company when the maintenance company accepting a request for repair of the device, etc. When a bid is placed, it asks a maintenance company with a short bidding time for repairs and accumulates the work results.

  The present invention notifies a maintenance bid request to an area in charge of repair and a qualified maintenance company when a maintenance company accepting a request for repair of the device, etc. By requesting repairs, etc., from a short, highly evaluated maintenance company, and accumulating the work results, it is possible to request the maintenance company to make repairs, etc. by bidding, thereby promoting the improvement of the service of the maintenance company .

  The present invention notifies a maintenance bid request to an area in charge of repair and a qualified maintenance company when a maintenance company accepting a request for repair of the device, etc. In addition to requesting repairs, etc., from a short and highly rated maintenance company, the work results were accumulated, and the maintenance company was requested to make repairs by bidding.

FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, a summary server 1 is a server that receives failure information, requests a bid from a corresponding maintenance company, and performs maintenance notification to the maintenance company that has bid. It comprises a distribution means 3, a bid notification means 4, a bid determination means 5, an information DB 11, and the like.

  The accepting means 2 accepts a request for repair of a device such as a personal computer of the customer's company. For example, the failure information (customer's company name, name of the device in which the failure occurred, Fault contents).

  The fault isolation means 3 isolates the fault that has occurred based on the fault information received by the accepting means 2, and for example, classifies the fault type (for example, GP6) or the like (for example, a disk fault). Is.

  The bid notification means 4 notifies a bid request to a maintenance company capable of dealing with the failure model, the failure content, and the location where the failure has occurred, separated by the failure isolation means 3 based on the received failure information. (See FIGS. 2 to 6).

  The bid determining means 5 determines (successfully bids) a bid to the corresponding maintenance company when a bid is made (see FIGS. 2 to 6).

  The information DB 11 stores various tables in an external storage device. Here, the maintenance company information table 12, the extraction condition table 13, the failure information table 14, the maintenance request information table 15, the bid number information table 16, the repeat The failure ratio information table 17, the work history information table 18, the evaluation information table 19, the evaluation condition table 20, the evaluation rank table 21, and the like are stored.

  The maintenance company information table 12 stores information related to the maintenance company (maintenance company name, maintainable area, holding qualification, notification address, etc.) in advance (see FIG. 4).

  The extraction condition table 13 notifies a maintenance request to a maintenance company that can be maintained, and when a bid is made, a time (first predetermined time, second time) for determining to which maintenance company a bid is decided. (Predetermined time) is registered in advance (see FIG. 4).

  The failure information table 14 registers and manages the received failure information (customer company name, failure location, failure model, failure date and time, failure content, etc.) (see FIG. 4).

  The maintenance request information table 15 registers information requested for maintenance (maintenance person flag, maintenance company name, bid reception start time, etc.) and manages the maintenance person state (see FIG. 4).

  The bid count information table 16 manages information such as the number of bids made by the maintenance company (model, cumulative bid count, etc.) (see FIG. 4).

  The repeat failure rate information table 17 registers and manages information (for example, the name of the maintenance company, the model, the number of repeat failures, the total number of failures handled, etc.) maintained by the maintenance company (see FIG. 4). reference).

  The work history information table 18 registers and manages information related to the work history of the maintenance company (for example, model, failure reception number, bid response time, response time, work time, etc.) (see FIG. 4).

  The evaluation information table 19 registers and manages information related to work maintained by the maintenance company (for example, average bid response time, cumulative number of bids, average response time, average work time, repeat failure rate, etc.) (FIG. 4).

  The evaluation condition table 20 registers and manages information (for example, coefficients) for calculating evaluation points based on information registered and managed in the evaluation information table 19 (see FIG. 4).

  The evaluation rank table 21 registers and manages information related to the evaluation rank of the maintenance company (information for calculating rank and rank (average bid response time, number of bids after evaluation, etc.)) (see FIG. 4). ).

The maintenance company terminal 31 is a maintenance company terminal connected to the network 35 for receiving a maintenance request, bidding, inputting work result information, and the like (FIGS. 2 to 6). The bid receiving means 32, the bid means 33, the successful bid receiving means 34, and the like.

  The bid receiving means 32 receives the bid request notified from the summary server 1 (see FIGS. 2 to 6).

  The bid means 33 collects bid information for the bid request received by the bid receiving means 32 and transmits it to the server 1 (see FIGS. 2 to 6).

  The successful bid receiving means 34 receives a successful bid corresponding to the bid made by the bidding means 33 (see FIGS. 2 to 6).

  The network 35 is a network for communicating a plurality of maintenance company terminals 31 and the management server 1 with each other, such as the Internet.

Next, the operation of the configuration of FIG. 1 will be sequentially described in detail according to the order of the flowchart of FIG.
FIG. 2 shows a flowchart for explaining the operation of the present invention.

FIG. 2A shows the operation of the summary server 1.
In FIG. 2A, S1 determines whether fault acceptance information has been input. This is to determine whether or not the accepting means 2 constituting the summary server 1 of FIG. 1 has received the failure information of the apparatus from the customer by telephone, FAX or e-mail. If YES, the process proceeds to S2. If no, wait.

In S2, since it is determined that the failure information has been accepted in S1 YES, it is determined whether there has been a repeat failure in the past at the same location, the same company, the same model, and the same failure content. For example, the failure information received this time for the entry (1) in the failure information table 14 of FIG. 4 (c)-Customer company name: FFF
・ Disability location: Shinjuku-ku 1-2-3 Shinjuku
-Failure model: GP6
(・ Failure date and time: 20060313)
Failure content: As the past failure information same as the disk failure, the entry of (2) in the failure information table 14 of FIG. 4C. Customer company name: FFF
・ Disability location: Shinjuku-ku 1-2-3 Shinjuku
-Failure model: GP6
(・ Failure date and time: 20060113)
Failure content: If there is a disk failure, it has been found that a repeat failure has occurred in the past, so the answer to S2 is YES, and the process proceeds to S3. On the other hand, if no repeat failure has occurred in the past, the new failure is NO in S2, and the process proceeds to S5.

  Since S3 is determined to be a repeat failure at YES in S2, a maintenance request is notified to the company that has been in charge of maintenance before, and is registered in the maintenance request information (for example, in (3) of the maintenance request information table 15 in FIG. 4D). Failure information is registered), and “1” is added to the number of repeat failures of the maintenance company (for example, “1” is added to the number of repeat failures in the entry (4) in the repeat failure rate information table 17 in FIG. 4F). ) And record the cumulative number of repeat failures of the maintenance company.

  In S4, the maintenance charge flag is set to “1”. This clearly indicates (stores) that the maintenance person in charge is set by setting the maintenance person in charge flag of the entry (3) in FIG. 4D registered in S3 to “1”.

  If the failure is accepted by the above S1, S2 YES, S3, and S4, if it is determined that a repeat failure has occurred, a maintenance request (maintenance request information in FIG. It is possible to notify the maintenance request by deciding that the information (failure acceptance number, maintenance flag “1”, maintenance company name) is registered as a maintenance request) in the entry of (3) of the table 15. Then, the maintenance company that has received the maintenance request notification of the repeat failure is YES in S11 of FIG. 2B, performs the maintenance work in S16, inputs the response time and work time in S17, and sends it to the server 1 In the summarizing server 1, it is possible to update the history and the order according to the flowchart of FIG.

Since S5 was found to be a new failure instead of a repeat failure in S2 NO, a maintenance company that has a maintenance area including the location of the failure and also has maintenance personnel with the qualifications necessary to maintain the failed model is extracted. Registered in the maintenance request information. For example, when a new failure of entry (5) in the failure information table 14 of FIG. 4 (c) in FIG. 4 is accepted, the new failure / location: 1-2-3 Roppongi, Minato-ku
-Failure model: GP6
As a maintenance company satisfying the requirements, the maintenance company information table 12 in FIG. 4A is referred to, and the three maintenance companies shown in (6) are extracted. (D) in the maintenance request information table 15 is registered in the entry indicated by (7).

  In S6, the failure acceptance information is disclosed to the extracted maintenance company, a bid request is notified, and the bid start time is registered. In this case, the failure information received by e-mail is disclosed to the three companies extracted in S5, and a bid request is notified, and 3 shown in (7) of the maintenance request information table 15 in (d) of FIG. The bid acceptance start time in one entry is registered (here, registered at 11:30). Then, bid request notifications are respectively transmitted to the terminals of the three companies, and bidding is performed by the processing of S21 to S29 on the maintenance company terminal side of FIG.

  If the received failure is not a repeat failure but a new failure by the above S1, S2 NO, S5, S6, the location of the received failure information (for example, (5) in FIG. 4C) The maintenance company that satisfies the faulty model is extracted and registered (for example, registered as three entries shown in (7) of the maintenance request information table 15 in FIG. 4D), and a bid request is notified to these maintenance companies. It becomes possible to do. Each maintenance company that has received these bid request notifications collects the bids by e-mail or the like and notifies the server 1 where the bidding company is determined by the processing from S21 to S29 in FIG. The maintenance company that has received the notification is YES in S15 in FIG. 2B, performs the maintenance work in S16, inputs the response time and work time in S17, and sends them to the summary server 1, and the summary server 1, it is possible to update the history and the ranking in the flowchart of FIG. Details will be sequentially described below.

FIG. 2B shows the operation of the maintenance company terminal 31.
In FIG. 2B, S11 determines whether a repeat failure response request has been received. In the case of YES, the maintenance work is started in S16, and when the work is completed in S17, the response time and the work time are input and transmitted to the summary server 1. On the other hand, in the case of NO in S11, since it has been determined that the request is not a repeat failure response request, the process proceeds to S12.

  In step S12, it is determined whether a bid request is received. This determines whether the received one is a bid request. If YES, the process proceeds to S13. If NO, the process ends.

  In S13, it is determined whether or not a bid request is registered. This determines whether the bid request is collected and registered in the server 1. If YES, the process proceeds to S14. If NO, the process ends.

  In S14, it is determined whether a successful bid OR OR successful bid notification is received. When a successful bid is received, maintenance work for failure information made a successful bid is started in S16. When the work is completed in S17, the response time and work time are input and sent to the collecting server 1 by e-mail. Updates the order according to the flowchart of FIG. On the other hand, if a successful bid failure is received in S14, the process ends.

FIG. 2C shows processing in the summary server 1.
In FIG. 2C, when a bid request is received, S21 registers a bid response time and adds “1” to the cumulative number of bids. This is because, when the management server 1 receives a bid request from the maintenance company that sent the bid request notification in S6, the bid response time is set in the maintenance request information table 15 in FIG. Register the time (the time from when the bid acceptance start time is received until the bid request is received), and add “1” to the cumulative number of bids of the corresponding maintenance company in the bid number information table 16 in FIG. .

  In S22, it is determined whether or not there is a bid within a certain time (2). It is determined whether or not there is a bid within a certain time (2) (a certain time (2) = 3 minutes in the extraction condition table 13 in FIG. 4B). In the case of YES, if there is a bid from a plurality of companies within a certain time (2) (here, 3 minutes) in S23, the maintenance charge flag “1” is registered in the company with the highest evaluation (in FIG. 4). (D) “1” is registered in the maintenance charge flag column of the maintenance company in the maintenance request information table 15), a successful bid decision notification is transmitted, and a bid rejection notification is sent to the bid companies other than the successful bidder in S 24. Transmit, register a maintenance charge flag of “0”, and end. On the other hand, if NO in S22, the process proceeds to S25.

  S25 is NO in S22, and it has been found that there is no bid even after a certain period of time (2) (for example, 3 minutes) has passed, so a certain period of time (1) (in the extraction condition table 13 of FIG. 4B) It is determined whether there is a bid within a certain time (1) = 10 minutes. In the case of YES, since it was found that there was a bid within a certain time (1) (10 minutes), a successful bid decision notification is transmitted to the company with the earliest bid time in S26 and the process is terminated. On the other hand, in the case of NO in S25, since it was found that there was no bid after a certain time (1) (10 minutes), the maintenance company with the highest evaluation in S27 (for example, the evaluation of (j) in FIG. 4). Request notification to the company with the highest evaluation (ranking 1 maintenance company) in the ranking column in the ranking table 21, and in S28, it is determined whether the acceptance notification has been received. If YES, the maintenance staff flag is registered to “1” in S29. When the answer is NO, a request is sent to the maintenance company with the next highest evaluation at S30, and S28 is repeated.

  As described above, the management server 1 notifies the maintenance company of a bid request, waits for reception of a bid request from the maintenance company, and when a bid is made within a certain time (2) (here, 3 minutes). Will notify the maintenance company with the highest evaluation, and if there is no bid within a certain time (2) and there is a bid within a certain time (1) (here 10 minutes), the maintenance with the earliest bid When a successful bid is notified to the company, and there is no bid after a certain period of time (1), it is possible to notify the maintenance request in order from the highest ranking and notify the maintenance company of the maintenance request. .

FIG. 3 shows a flowchart for explaining the operation of the present invention (rank update, etc.).
In FIG. 3, in S31, it is determined whether there is an input of response time and work time from the maintenance company. This is done by inputting the response time and the work time in S17 of FIG. 2B described above, and determining whether it has been transmitted by e-mail (or input and transmitted from the home page). If YES, the process proceeds to S32. If no, wait.

  In S32, “1” is added to the total failure handling number for the maintained model (“1” is added to the total failure handling number column in the repeat failure rate information table 17 in FIG. 4F).

  In S33, a bid evaluation time for each model and other evaluation items are weighted, and a total evaluation score is calculated and registered. This is shown in the evaluation information table 19 of (h) of FIG. 4 for each item value of model, average bid response time for each company, total number of bids, average response time, average work time, and repeat failure rate. (I) of the evaluation condition table 20 of FIG. 4 is multiplied respectively, and the average bid response time, the cumulative number of bids, the average response time, the average work time, and the repeat failure rate of the evaluation rank table 21 of FIG. After setting in each of the fields, the total of these is obtained and registered in the total evaluation score field.

  In S34, the rank is calculated and updated for each model. This updates the ranks 1, 2, 3... In ascending order of values in the comprehensive evaluation score column for each model calculated in S33.

  As described above, it is possible to register information such as response time and work time notified from the maintenance company that has made a successful bid for the maintenance work and renewed the ranking by recalculating the total evaluation score. As a result, as the average bid response time, average response time, average work time, repeat failure rate, and cumulative number of bids become smaller, the overall evaluation score becomes smaller and the ranking can be improved. It becomes possible to make a successful bid for information.

FIG. 4 shows an example table of the present invention.
FIG. 4A shows an example of a maintenance company information table. The maintenance company information table 12 registers and manages maintenance company information, and registers and manages the following information shown in association with each other.

・ Maintenance company name:
・ Maintenance area:
・ Maintenance qualification:
-Notification destination address Here, the maintenance company name is a name for uniquely identifying the maintenance company. The maintainable area is an area (place) for maintaining the failure occurrence device. The maintenance qualification is a maintenance qualification (for example, a maintenance qualification of the model GP5). The notification destination address is an address for notifying a bid request or the like.

  FIG. 4B shows an example of an extraction condition table. The extraction condition table 13 registers and manages the time used when determining a successful bid in FIG. 2C described above. Here, the following time shown in the figure is registered and managed. Is.

Fixed time (1): 10 minutes Fixed time (2): 3 minutes FIG. 4C shows an example of a failure information table. The failure information table 14 registers and manages the received failure information, and registers and manages the following information shown in association with each other.

・ Handicap number:
・ Customer company name:
・ Fault location:
-Failure model:
-Failure date and time:
·Failure content:
Here, the failure reception number is a unique number assigned to the received failure information. The customer company name is the name of the company where the failure occurred. The failure location, the failure model, the failure date / time, and the failure content are the location of the failure that occurred, the device model, the failure occurrence date / time, and the content of the failure (for example, a disk failure).

  FIG. 4D shows an example of a maintenance request information table. The maintenance request information table 15 is for registering and managing information such as a maintenance company that requests maintenance. Here, the following information shown in FIG.

・ Handicap number:
-Maintenance flag:
・ Maintenance company name:
・ Bid acceptance start time:
・ Bid time:
Here, the failure reception number is the number of the failure assigned at the time of failure reception. The maintenance person in charge flag is set to 1 when a successful bid is determined and the person in charge of maintenance is determined, and is set to 0 when not in charge of maintenance. The maintenance company name, the bid acceptance start time, and the bid response time are the name of the maintenance company notified of the bid request, the time when the bid acceptance was started, the time when the bid request was notified (for example, the bid request is collected from the bid start time and sent to the server 1 Time to arrive).

  (E) of FIG. 4 shows an example of a bid number information table. The bid number information table 16 registers and manages the number of bids and the like for each maintenance company, and here, registers and manages the following information shown in association with each other.

·company name:
・ Model:
・ Total bids:
Here, the company name is the name of the maintenance company that performed the maintenance. The model is the model of the apparatus that has undergone maintenance. The total number of bids is the total number of bids sent to the management server 1 in response to a bid request notification from the management server 1 for bidding.

  FIG. 4F shows an example of a repeat failure rate information table. The repeat failure rate information table 17 registers and manages the number of repeat failures and the like, and here registers and manages the following information shown in association with each other.

·company name:
・ Model:
・ Number of repeat failures:
・ Total number of failures:
Here, the company name is a maintenance company name. The model is the model of the device that performed maintenance of the fault. The number of repeat faults is the cumulative number of times that faults (repeat faults) with the same fault content of the same model are maintained. The total number of failure responses is the total number of failure responses that include repeat failures and new failures.

  FIG. 4G shows an example of a work history information table. The work history information table 18 registers and manages a work history for each model for each maintenance company. Here, the work history information table 18 registers and manages the following information shown in association with each other.

·company name:
・ Model:
・ Handicap number:
・ Bid time:
・ Response time:
·Working hours:
Here, the company name is the name of the maintenance company that performed the maintenance. The model and fault reception number are the model of the maintained device and the reception number assigned to the received fault. The bid response time, response time, and work time are the time from the start of bidding to the bid, the response time, and the time required for the work.

  FIG. 4H illustrates an evaluation information table example. The evaluation information table 19 registers and manages information for calculating an evaluation score. Here, the evaluation information table 19 registers and manages the following information shown in FIG.

・ Model:
·company name:
・ Average bidding time (minutes):
・ Total number of bids (1 / time):
・ Average response time (minutes):
・ Average work time (minutes):
・ Repeat failure rate (%):
Here, the model is the model of the device in which the failure has occurred. The company name is the name of the maintenance company that performed the maintenance. The average bid response time (minutes) is the average bid response time. The total number of bids (1 / time) is the reciprocal of the total number of bids. The average response time is an average of response times. What is the average working time? Average maintenance time. The repeat failure rate is the ratio (%) of repeat failures to all failures.

  (I) of FIG. 4 shows an example of an evaluation condition table. The evaluation condition table 20 registers and manages weights for calculating an evaluation score by multiplying the average bid response time registered in the evaluation information table 19 of FIG. The following weights shown in the figure are registered and managed in association with each other.

・ Evaluation element: Weighting ・ Bid time:
・ Total bids:
・ Response time:
·Working hours:
・ Repeat failure rate:
(J) of FIG. 4 shows an example of an evaluation order table. The evaluation rank table 21 is calculated by multiplying the value of each column of the evaluation information table 19 of (h) of FIG. 4 by the weight value of each column of the evaluation condition table 20 of (i) of FIG. An evaluation score is set, and here, the following information shown in the figure is registered and managed in association with each other.

・ Model:
·company name:
・ Average bid response time:
・ Total bids:
・ Average response time:
・ Working time evaluation points:
・ Repeat failure rate:
・ Total evaluation score:
・ Rank:
Here, the model, company name, average bid response time, cumulative number of bids, average response time, work time evaluation point, repeat failure rate are shown in the values of each column of the evaluation information table 19 in FIG. The evaluation points obtained by multiplying the weight values in the respective columns of the evaluation condition table 20 in (4) are respectively set. The total score is the total score of the evaluation points in each column. The ranks are given ranks 1, 2, 3.4... In ascending order of the total evaluation score.

5 and 6 show examples of screens / messages of the present invention.
FIG. 5A shows a screen example of a maintenance company terminal (in the case of no repeat failure). This is an example of a screen displayed on the display device of the maintenance company terminal 31 in FIG. 1, and here, the following information shown in the figure is displayed.

·message:
“Spot maintenance bid request received.”
・ Fault information:
"Customer company name, failure location, failure model, failure date and time, failure details"
・ "Bid acceptance start time"
・ Bid icon:
"Do you want to bid?"
Worker Schedule Table Here, the message is the content of the received e-mail, and here represents an example of a maintenance bid request. The failure information is failure information for maintenance bidding. The bid reception start time is the time when the bid reception is started.

  To refer to the above information and collect bid requests and send them to the server 1 for bidding, the bidding is automatically performed by pressing the lower bidding button.

  FIG. 5B shows a screen example of the maintenance company terminal. This is an example of a screen when the work result report displayed on the display device of the maintenance company terminal 31 in FIG. 1 is transmitted, and here, the following information shown in the figure is displayed.

・ Work result report:
“Please enter the work time and response time for the trouble reception number.”
(C) of FIG. 5 shows the example of a screen of a summarizing server. This is an example of a screen displayed on the display device of the summary server 1 of FIG. 1, and here, the following information shown in the figure is displayed.

·message:
"Error information has been registered.

We submitted bid requests to the following three companies. "
・ Fault information:
"Customer company name, failure location, failure model, failure date and time, failure details"
・ Bid information disclosure company:
"Oh company Ii company Uu company"
・ Successful bid result:
"Good company"
Here, the message displays the contents of failure information registration and bid request. The failure information is failure information for maintenance bidding. The bid information disclosure destination company displays the name of the maintenance company that has notified the bid information (failure information). The successful bid result displays the name of the maintenance company that has made a successful bid.

  FIG. 6D shows an example of a maintenance request notification mail (repeat failure). Here, since a repeat failure is accepted, an example of transmitting the following information shown in the figure is shown.

・ Yes.
"Please perform maintenance work for failure reception number 5555.

It is a repeat failure with failure reception number 2222. "
Here, yeah company is the name of the maintenance company that caused the repeat failure. The upper part of the message is the failure acceptance number of the failure and the message for requesting maintenance work, and the lower part is the message of the past failure.

  FIG. 6E shows an example of a successful bid notification mail. This shows an example of an e-mail message requesting the maintenance work for which the management server 1 has made a successful bid for the maintenance company “Iisha” and making a successful bid.

  FIG. 6F shows an example of a bid response mail. This shows an example of an e-mail message transmitted to the maintenance company that has made a bid for the management server 1 but has made a bid.

The present invention notifies a maintenance bid request to an area in charge of repair and a qualified maintenance company when a maintenance company accepting a request for repair of the device, etc. A maintenance destination selection method and maintenance destination that encourages improvement of the maintenance company's service by requesting repairs, etc. from a short and highly evaluated maintenance company, accumulating the work results, and requesting maintenance by bidding to the maintenance company It relates to the selection program.

It is a system configuration diagram of the present invention. It is an operation explanation flowchart of the present invention. It is operation | movement explanatory flowchart (order update etc.) of this invention. It is an example table of this invention. It is a screen / message example (the 1) of this invention. It is a screen / message example (the 2) of this invention.

Explanation of symbols

1: Summary server 2: Acceptance means 3: Fault isolation means 4: Bid notification means 5: Bid determination means 11: Information DB
12: Maintenance company information table 13: Extraction condition table 14: Failure information table 15: Maintenance request information table 16: Bid count information table 17: Repeat failure ratio information table 18: Work history information table 19: Evaluation information table 20: Evaluation conditions Table 21: Evaluation ranking table 31: Maintenance company terminal 32: Bid receiving means 33: Bid means 34: Successful bid receiving means 35: Network

Claims (5)

In the maintenance destination selection method that accepts equipment maintenance requests and requests maintenance to the relevant maintenance company,
The means provided in the computer is
Receiving a maintenance request for the device;
For the received maintenance, extracting the maintenance location and a maintenance company capable of maintenance from a table in which information related to the maintenance location and the maintainable device is registered in advance;
Notifying the extracted maintenance company of a bid request;
Receiving a bid from the maintenance company that has notified the bid request and storing the time;
When a bid from the plurality of maintenance companies is received within a preset first predetermined time, a table in which the ranks calculated from the past history are registered among the plurality of maintenance companies is referred to as the highest rank. Selecting a high maintenance company,
When there is no maintenance company that bids within the first predetermined time and there is a bid within a second predetermined time that is longer than the first predetermined time, a step of selecting a maintenance company that has bid first When,
Maintenance destination selection method, wherein the in the selected maintenance company, and a step of notifying maintenance. The means provided in the computer is
When there is no maintenance company bidding within the second predetermined time, a maintenance request is notified in order from the maintenance company with the highest ranking by referring to a table in which rankings calculated from past histories are registered. The maintenance destination selection method according to Item 1. The means provided in the computer is
A rank to be registered in the table, the shorter bid response time, according to claim 1 or claim 2 Service destination selection method wherein high to Rukoto ranking. The means provided in the computer is
As rank to be registered in the table, the larger the bid number, maintenance destination selection method according to any one of claims 1 to 3, wherein high to Rukoto ranking. On the computer,
Receiving a maintenance request for the device;
For the received maintenance, extracting the maintenance location and a maintenance company capable of maintenance from a table in which information related to the maintenance location and the maintainable device is registered in advance;
Notifying the extracted maintenance company of a bid request;
Receiving a bid from the maintenance company that has notified the bid request and storing the time;
When a bid from the plurality of maintenance companies is received within a preset first predetermined time, a table in which the ranks calculated from the past history are registered among the plurality of maintenance companies is referred to as the highest rank. Selecting a high maintenance company,
When there is no maintenance company that bids within the first predetermined time and there is a bid within a second predetermined time that is longer than the first predetermined time, a step of selecting a maintenance company that has bid first When,
A maintenance destination selection program for functioning as a step of notifying the selected maintenance company of maintenance.

Images