JP2011197894A - Server device and maintenance method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a maintenance date in accordance with a customer's request and to provide a method for extending the life of an apparatus up to the maintenance date.SOLUTION: A server device, regarding a day for maintenance when an apparatus can be stopped, receives input by a customer, receives a physical value indicating the status of a component acquired by a component controller, and predicts the lifespan of the component on the basis of the received physical value to determine if the predicted lifespan is shorter than a predetermined amount of time. If the predicted lifespan is determined to be shorter than the predetermined amount of time, a day on which to perform maintenance on the component is selected from the received days for maintenance to determine if the lifespan determined to be shorter than the predetermined amount of time is shorter than the amount of time until the selected day for maintenance, and if the lifespan determined to be shorter than the predetermined amount of time is shorter than the amount of time until the selected day for maintenance, a method is acquired for extending the lifespan of the component which has been determined to be of a lifespan shorter than the amount of time until the selected maintenance day.

Description

  The present invention relates to a server device, and more particularly to a server device connected to a device to be maintained.

  In order to always operate equipment such as a gas engine, an elevator, or a printer, regular maintenance work by a maintenance company is essential. In order to reduce the cost of maintenance work, the maintenance company needs to make the maintenance work interval as long as possible by reducing the number of maintenance work. However, if the time interval for performing maintenance work is too long, there is a high possibility that the device will break during that time, so the maintenance contractor needs to perform the maintenance work as soon as the lifetime of the parts that make up the device falls below a certain level. There is.

  In order to use up the equipment until the end of its life, the following technique using a technique for predicting the life of each part constituting the equipment has been proposed.

  There is a technology that predicts the time of component damage, performance degradation, or malfunction, covers possible failure events, and determines the optimal maintenance work interval by risk-based cost evaluation (For example, refer to Patent Document 1).

  In addition, there is a technology that provides life extension control that extends the life of parts constituting the device or the time until the next maintenance or reduces the number of parts that need to be replaced (for example, see Patent Document 2).

JP 2003-303243 A JP 2005-267633 A

  Conventional technologies using component life represented by Patent Document 1 and Patent Document 2 extend the life of equipment parts, extend the maintenance schedule interval of equipment operated by customers, and reduce maintenance costs. By doing so, the profit of the maintenance company side was improved. Therefore, even if the maintenance company has a customer's request to postpone the maintenance work at a later date even on the day when it is determined that the apparatus is optimally maintained, the maintenance company has to delay the maintenance work.

  For example, a customer who needs to operate equipment all day may request maintenance on weekdays in order to delay maintenance work until a holiday. However, when the maintenance work is delayed in response to a request from the customer, there is a problem that a part whose life has been shortened is broken, the operation of the device is stopped, and there is a high possibility of causing a loss to the customer.

  According to a typical embodiment of the present invention, a server device connected to a component controller that obtains a physical quantity from components included in a device used by a customer, wherein the server device is capable of stopping the device. And receiving an input by the customer, receiving a physical quantity in the part acquired by the parts controller, predicting a lifetime of the part based on the received physical quantity, and the predicted lifetime is a predetermined time If it is determined whether or not the predicted life is shorter than a predetermined time, a date on which a part for which the life is determined to be shorter than the predetermined time is to be maintained is set as the accepted maintenance. It is determined whether the life determined to be shorter than the predetermined time is shorter than the time until the selected maintenance date. When it is determined that the specified life is shorter than the time until the selected maintenance date, a method for extending the life of the part determined to have a life shorter than the time until the selected maintenance date is obtained. To do.

  According to an embodiment of the present invention, it is possible to acquire a maintenance date in accordance with a customer's request when maintaining a device, and to acquire a method for extending the life of the device until the acquired maintenance date.

It is a block diagram which shows the physical structure of embodiment of this invention. It is explanatory drawing which shows the maintenance possible day table of embodiment of this invention. It is explanatory drawing which shows the components kind ID table of embodiment of this invention. It is explanatory drawing which shows the component life extension sequence table of embodiment of this invention. It is a flowchart which shows the whole process of embodiment of this invention. It is a flowchart which shows the initial input process of the maintenance possible day of embodiment of this invention. It is a flowchart which shows the process which searches the maintenance possible day of embodiment of this invention. It is a flowchart which shows the process which searches the life extension sequence of embodiment of this invention. It is explanatory drawing which shows the example of an input screen of the maintenance possible day displayed on the display of embodiment of this invention. It is explanatory drawing which shows the example of an error screen displayed on the display of embodiment of this invention. It is explanatory drawing which shows the example of a result screen displayed on the display of embodiment of this invention. It is explanatory drawing which shows another example of a result screen displayed on the display of embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings of FIGS.

  FIG. 1 is a diagram showing the overall configuration of the present invention. FIGS. 2 to 4 show the structure of a data table stored in each database provided in the server shown in FIG. FIG. 9 and FIG. 10 show examples of screens displayed to a user such as a customer or a maintenance company.

  FIG. 1 is a block diagram showing a physical configuration of an embodiment of the present invention.

  The system according to the present embodiment includes a serviceable date input device 1000, a server 3000, an HDD 2000, a component controller 5100, a component 6100, a maintenance company server 6500, a maintenance company display 6800, and a display 7000.

  The serviceable date input device 1000 is a device for inputting a serviceable date of equipment to the server 3000 by a customer. The maintenance possible date is a date when the operation of the device may be stopped and maintenance work may be performed, and the customer inputs the maintenance possible date to the server 3000 at the start of operation of the device. Here, the device is a device including the component 6100 and is a device used by a customer.

  The maintenance day input device 1000 may be any device such as a keyboard, a mouse, or a device capable of voice input as long as it can be input to the server 3000. In the present embodiment, an example of an input screen in the maintainable date input device 1000 for inputting a maintainable date using a mouse will be described later.

  The HDD 2000 shown in FIG. 1 is a hard disk capable of recording a large amount of data. In addition to the hard disk, an SSD or the like that can record data even when the power is stopped may be used. The HDD 2000 holds at least a serviceable day database 2100 and a component life information database 2200.

  The serviceable date database 2100 is a database that stores date and time data input using the serviceable date input device 1000. The serviceable date database 2100 holds a serviceable date table 2110 shown in FIG.

  FIG. 2 is an explanatory diagram illustrating the serviceable day table 2110 according to the embodiment of this invention.

  The maintenance possible date table 2110 includes a date / time column 2113 and a maintenance enable / disable column 2116. The date / time column 2113 indicates the date / time that is a candidate for the maintenance date. The maintenance possible / impossible column 2116 indicates whether or not maintenance is possible at the date and time indicated by 2113. The server 3000 can check whether or not the date / time is a maintainable date by searching 2113 and referring to the corresponding maintainable / unavailable column 2116.

  The component life information database 2200 has a component type ID table 2230 and a component life extension sequence table 2260. The component type ID table 2230, the component life extension sequence table 2260, and the data in the table are stored in advance by the device maintenance company or the manufacturer before the device is shipped to the customer.

  FIG. 3 is an explanatory diagram illustrating the component type ID table 2230 according to the embodiment of this invention.

  The component type ID table 2230 includes a component ID column 2233 and a component type ID column 2236. The component ID column 2233 indicates an identifier for identifying each component 6100 (1 to N), and the component type ID column 2236 indicates what type of component 6100 (1 to N) the component ID column 2233 indicates. This indicates the type of component such as the pump or what kind of electronic component it is. The server 3000 can obtain the component type ID of the component 6100 (1 to N) by searching the component type ID table 2230 using 2233 as a search key.

  FIG. 4 is an explanatory diagram illustrating the component life extension sequence table 2260 according to the embodiment of this invention.

  The component life extension sequence table 2260 includes a component type ID column 2262, a lifetime extension column 2265, and a component lifetime extension sequence column 2267. The component type ID column 2262 indicates an identifier for uniquely identifying the type of the component 6100. The component type ID column 2262 in the component life extension sequence table 2260 corresponds to the component type ID column 2236 in the component type ID table 2230.

  The life extension time column 2265 indicates a range of time for extending the life of the component 6100. Further, the component life extension sequence column 2267 indicates a predetermined life extension means for the lifetime of the component 6100 according to the type of the component 6100 and the life extension time.

  The server 3000 uses the component life extension sequence table 2260 to search for the component type ID 2236 acquired from the component type ID table 2230 and the life extension time calculated based on the serviceable time, and the value 2267 of the corresponding record. By referring to, it is possible to acquire the part 6100 and the life extension means of the part 6100 that is optimal for the life extension time. The value 2267 is stored in a description (eg, XML) that can be interpreted by the program so that it can be executed by the program.

  The component life extension sequence table 2260 illustrated in FIG. 4 may indicate a life extension time column 2265 and a component life extension sequence column 2267 for each component ID column 2233 instead of for each component type ID column 2262.

  A server 3000 shown in FIG. 1 includes a CPU 3100 and a RAM 4000, and is connected to a maintenance day input device 1000, an HDD 2000, and a component controller 5100, and is connected to a maintenance company server 6500 via a network.

  The server 3000 receives a physical quantity indicating the state of the component 6100 (1 to N) from the controller of the components 1 to N included in the component controller 5100, and sends a signal for controlling the component 6100 (1 to N) to the component 6100. I / O port for sending to. In addition, a communication port such as a LAN port for transmitting the result of the life extension process of the device described later to the maintenance company is provided.

  The CPU 3100 is a device for executing the program of this embodiment. That is, the CPU 3100 is an arithmetic unit for executing the data input program 4100, the component life prediction program 4200, the life extension sequence search program 4300, the serviceable date search program 4400, the maintenance date determination program 4500, and the component life extension sequence execution program 4600. is there.

  The RAM 4000 holds programs such as a data input program 4100, a component life prediction program 4200, a life extension sequence search program 4300, a serviceable date search program 4400, a maintenance date determination program 4500, and a component life extension sequence execution program 4600. Also, the output results of these programs are temporarily held.

  The data input program 4100 is a program for storing data such as a serviceable date input by the customer using the serviceable date input device 1000 in the serviceable date database 2100. This is executed by the CPU 3100 every time the customer inputs data.

  The component life prediction program 4200 obtains the physical quantity indicating the state of the component 6100 from the component controller 5100 (1 to N) connected to the component 6100 (1 to N), and thereby the lifetime of the component 6100 (1 to N). Is a program for predicting each part 6100. The physical quantity indicating the state of the component 6100 includes, for example, the surface temperature or the rotational speed.

  Various methods have been proposed for predicting the lifetime according to the type of component 6100. For example, although the turbine is consumed due to friction generated during rotation, there is a method of predicting the life of the turbine based on the amount of iron scrap generated by friction or the resistance value during rotation (for example, Japanese Patent Laid-Open 10-293049). In addition, there is a method for evaluating damage from the surface temperature of an operating device and the like and predicting the lifetime (see, for example, JP-A-2001-32724).

  The life extension sequence search program 4300 is a program for searching for an optimum method for extending the life of the part 6100 by searching the part life information database 2200 based on the part type ID 2262 and the life extension time 2265.

  The maintenance date search program 4400 searches the maintenance date database 2100 to obtain whether or not the specified date is a date that can be maintained by the customer.

  The maintenance date determination program 4500 instructs the maintenance date search program 4400 to search, determines a maintenance date based on the search result acquired by the maintenance date search program 4400, and displays the determined maintenance date on the display 7000. It is a program to be displayed.

  The component life extension sequence execution program 4600 is a program that interprets the life extension means acquired by the life extension sequence search program 4300 and outputs a control instruction for extending the life to the component controller 5100 (1 to N). The control instruction for extending the life is, for example, instructing to lower the output voltage of the component 6100 when the component 6100 to extend the life is an electronic component, or to reduce the pressure when the component 6100 is a pump. It is. By sending such a control instruction to the component 6100, the load on the component 6100 can be reduced, and the output of the component 6100 can be suppressed, thereby extending the life of the component 6100.

  The parts 6100 (1 to N) are parts included in the maintenance target device, and are, for example, parts such as a pump, a motor, or a circuit.

  The component controller 5100 (1 to N) measures a state parameter (a current value when the component is an electronic component, a pressure value when the component is a pump, etc.) indicating each state of the component 6100 (1 to N). Further, the apparatus is a device that transmits the measured result to a program held in the server 3000, or conversely controls the component 6100 (1 to N) according to the program held in the server 3000.

  Each component controller 5100 (1 to N) stores a component ID of a component 6100 (1 to N) controlled by each component 6100 (1 to N), such as a ROM provided in the component controller 5100 (1 to N). Hold on the medium. When the state parameters measured in the parts 6100 (1 to N) are transmitted to the program held in the server 3000, the part controller 5100 (1 to N) determines which state parameter in which part 6100 (1 to N). In order to indicate whether or not is measured, a part ID and a state parameter are transmitted as a set.

  When the parts 6100 (1 to N) are controlled according to the program held in the server 3000, the server 3000 sends an instruction in which a part ID and a control command are paired to the part controller 5100, thereby corresponding to the part ID. The parts 6100 (1 to N) are controlled according to the control signal.

  The maintenance company server 6500 is a server for the maintenance company to receive a result of a life extension process described later sent from the server 3000.

  The maintenance company-side display 6800 is a display device for displaying the life extension processing result of the device operated by the customer, which is the result received from the server 3000 by the maintenance company server 6500. For example, a liquid crystal panel or a printer may be used.

  The display 7000 is a display device for displaying a data input screen and a maintenance date for a customer who operates the device. For example, a liquid crystal panel or a printer may be used.

  Hereinafter, the life extension process and the maintenance date determination process for the component 6100 by the program held in the RAM 4000 shown in FIG. 1 will be described with reference to the flowcharts of FIGS.

  FIG. 5 is a flowchart showing the overall processing of the embodiment of the present invention.

  In FIG. 5, S4100 is a subroutine for inputting a maintainable date that the customer performs only once as an initial input when the device is introduced. A detailed flow of S4100 is shown as a subroutine SUB01 in FIG.

  FIG. 6 is a flowchart showing an initial input process of a serviceable day according to the embodiment of the present invention. SUB01 shown in FIG. 6 corresponds to S4100 (SUB01) shown in FIG.

  The data input program 4100 displays an input screen, which will be described later, on the display 7000 in order to allow the customer to input a maintenance possible date, that is, a date on which the maintenance operation can be performed for the customer's convenience (S4105). ).

  Next, the customer inputs a maintenance available date using the maintenance available date input device 1000 (S4110).

  Next, the data input program 4100 receives the date and time and the value indicating whether or not the date and time can be maintained as the maintenance date data input by the customer (S4115).

  Next, the data input program 4100 determines whether or not the range of date and time when maintenance is not possible exceeds the maximum time that can be extended based on the maintenance date data input at S4105 (S4117).

  When the range of date and time when maintenance is not possible exceeds the maximum time that can extend the life, the data input program 4100 displays an error screen 7200 described later, and then returns to S4105 to prompt the customer to re-enter the maintenance date. If the range of date and time that cannot be maintained is equal to or shorter than the maximum time that can be extended, the data input program 4100 proceeds to S4120.

  Here, the maximum prolongable life is the maximum number of days stored in the life extension column 2265 of the component life extension sequence table 2260 shown in FIG. 4, and is a constant determined at the time of device design. Therefore, the maximum time that can be extended is stored as program data in the RAM 4000 in advance.

  SUB01 is complete | finished above and it transfers to S4200 of FIG.

  In S4200 and S4250, the part life prediction program 4200 predicts each life of the parts 6100 (1 to N). First, the component life prediction program 4200 requests the component controller 5100 (1 to N) for a set of the component ID and the state parameter of the component 6100, and the state parameter of the component 6100 sent from the component controller 5100 (1 to N). (S4200).

  Then, the component life prediction program 4200 predicts the component life t of each 6100 using the received state parameter and the life prediction model of the component 6100 incorporated in the program (S4250). When all the lifetimes of the parts 6100 (1 to N) can be predicted, the process proceeds to S4300.

  Note that S4200 and S4250 may be performed periodically after a certain period of time.

  Here, the life prediction model is a model for predicting the life from the resistance value or surface temperature of the component 6100 as described above, and is stored in the RAM 4000 in advance.

  Next, the server 3000 determines whether or not there is a component life t that is less than the limit life among the component lifetimes t predicted in S4250 (S4300). If there is no part life t less than the limit life, the process returns to S4200.

  In S4300, when there is even one component life t that is less than the limit life, the process proceeds to S4350. Then, the part ID of the part 6100 corresponding to the part life t less than the limit life is stored in the RAM 4000 (S4350), and the process proceeds to S4400.

  The limit life value is a life value at which the probability that the part 6100 will fail and become inoperable when the life becomes shorter than this is the life value. This is a constant determined by the maintenance company's operation policy of whether to allow.

  In order to determine the maintenance date for replacing the part 6100 whose service life is less than the limit life, the serviceable date search program 4400 finds the serviceable date / time at the date / time closest to the current time, and obtains the number of days from the current time ( S4400). A detailed flow of S4400 is shown in FIG. 7 as a subroutine SUB02.

  FIG. 7 is a flowchart showing a process for searching for a maintenance possible date according to the embodiment of the present invention. SUB02 shown in FIG. 7 corresponds to S4400 shown in FIG.

  The maintainable day search program 4400 obtains the current time using a function such as the OS of the server 3000 (S4410).

  Next, the maintenance date search program 4400 searches the maintenance date availability table 2110 based on the current time acquired in S4410, and determines whether the current time is maintainable (S4415). For example, when the current time is 2010/01/01/00: 00, the maintenance date search program 4400 can determine that maintenance is not possible from the value in the maintenance availability / inhibition column 2116 of the maintenance availability date table 2110.

  If it is determined in S4415 that the current time is maintainable, the maintainable day search program 4400 stores the current time in the RAM 4000 (S4117), and ends SUB02. If it is determined in S4415 that maintenance is not possible, the process moves to S4420.

  In S4420 and S4425, the maintainable day search program 4400 searches for a date that is closest to the current time and that can be maintained.

  Next, the maintainable date search program 4400 searches for information in the date / time column 2113 that is one ahead of the date / time previously searched in the maintainable date table 2110 (S4420). For example, if the date / time column 2113 searched in S4415 is 2010/01/01/00: 00 and the processing shifts from S4415 to S4420, the date / time column 2113 searched previously in S4420 is searched in S4415. The current time is 2010/01/01/00: 00. Therefore, the maintainable date search program 4400 searches the date / time column 2113 that is one step down from the date / time column 2113 searched in S4415, and obtains the value 2010/01/02/00: 00.

  Next, the maintenance date search program 4400 determines whether or not the date acquired in S4420 is maintainable (S4425). If maintenance is possible, the process proceeds to S4427. If maintenance is not possible, the process returns to S4220.

  For example, if the current time searched in S4415 is 2010/01/01/00: 00: 00 by the loop of S4420 and S4425 described above, 2010/01 is set as the closest maintainable date / time in the maintainable date table 2110 shown in FIG. 01/04/00: 00 is acquired.

  Next, the maintainable date search program 4400 stores the closest maintainable date and time acquired by the loop of S4420 and S4425 in the RAM 4000 (S4227).

  Further, the maintainable day search program 4400 calculates a time T from the current time acquired in S4415 to the closest maintainable day. Therefore, a time T from the current time to the nearest maintainable date acquired in S4227 is calculated, and the calculated time T is stored in the RAM 4000 (S4430).

  Thereafter, SUB02 ends, and the process proceeds to S4500 in FIG.

  Next, the server 3000 determines whether maintenance work is possible before the lifetime of the component 6100 acquired in S4300 is exhausted (S4500). In S4500, the server 3000 compares the remaining component life t at the current time with the length T of time from the current time acquired in S4400 to the nearest serviceable day.

  When t <T, since the maintenance work cannot be performed before the lifetime of the part 6100 is exhausted, the server 3000 determines that the life extension process is necessary for the part 6100, and the process proceeds to S4600. When t ≧ T, maintenance work can be performed before the life of the part 6100 is exhausted, so the server 3000 determines that the life extension process is unnecessary for the part 6100, skips the life extension process, and proceeds to S4800.

  Next, the life extension sequence search program 4300 searches for the optimum life extension means for the part 6100 determined to require life extension processing in S4500 (S4600). A detailed flow of S4600 is shown in FIG. 8 as a subroutine SUB03.

  FIG. 8 is a flowchart illustrating processing for searching for a life extension sequence according to the embodiment of this invention.

  The life extension sequence search program 4300 reads the component ID of the component 6100 that has been stored in the RAM 4000 in S4350 shown in FIG. Then, the life extension sequence search program 4300 searches the component type ID table 2230 shown in FIG. 3 using the component ID as a search key. A search is performed using the component ID column 2233 of the component type ID table 2230 as a search condition, and the value of the component type ID column 2236 of the search result is acquired (S4640).

  Next, the life extension sequence search program 4300 reads the time T until the maintenance possible date stored in the RAM 4000 in S4430, and sets the time T as the life extension time (S4650).

  Next, the life extension sequence search program 4300 searches the component life extension sequence table 2260 based on the value of the component type ID column 2236 acquired in S4640, and is acquired in S4650 out of the life extension time 2265 corresponding to the value of 2236. The component life extension sequence 2267 corresponding to the life extension time T is acquired (S4660). The acquired 2267 is stored in the RAM 4000.

  Thereafter, SUB03 ends, and the process proceeds to S4700 shown in FIG.

  The server 3000 executes the life extension sequence indicated by 2267 acquired in S4600 for the parts 6100 (1 to N) that need to have a life extension. That is, the server 3000 reads 2267 stored in the RAM 4000 in S4700.

  The component life extension sequence execution program 4600 interprets the read 2267. Based on the interpretation result, the component life extension sequence execution program 4600 instructs the component controller 5100 corresponding to the component 6100 that requires life extension to perform control for reducing the component ID and the component load for extending the life. The component controller 5100 performs control to reduce the component load on the component 6100 that requires life extension. As a result, the lifetime of the component 6100 is extended for a period necessary to operate the device until the maintenance date (S4700).

  Next, the maintenance date determination program 4500 reads the maintenance possible date closest to the current time stored in the RAM 4000 in S4427. Then, the maintenance possible date is displayed on the display 7000 on the customer side that operates the device as shown by 7300 in FIG. 10 (S4800).

  Next, the maintenance date determination program 4500 uses the communication function of the server 3000 to transmit the maintenance possible date and information on the component 6100 that has performed the life extension sequence to the maintenance company. Information transmitted from the server 3000 is received by the maintenance company server 6500 and displayed on the maintenance company display 6800 (S4850).

  FIG. 9A is an explanatory diagram illustrating an example of a maintenance day input screen displayed on the display 7000 according to the embodiment of this invention.

  In the input screen 7100 shown in FIG. 9A, a check box indicating whether the date and time can be maintained is arranged in the left column, and whether the date and time can be maintained or not is arranged in the center and right columns. Information is input to the check box by the maintenance day input device 1000 such as a mouse. The input screen 7100 is displayed in S4105 shown in FIG.

  FIG. 9B is an explanatory diagram illustrating an example of an error screen displayed on the display 7000 according to the embodiment of this invention.

  6 is an example of an error screen 7200 displayed on the display 7000 when the non-maintenable date and time range exceeds the maximum time that can be extended in S4117 shown in FIG.

  FIG. 10A is an explanatory diagram illustrating an example of a result screen displayed on the display 7000 according to the embodiment of this invention.

  The screen example shown in FIG. 10A is a result screen 7300 displayed in S4800 shown in FIG.

  FIG. 10B is an explanatory diagram illustrating another result screen example displayed on the display 7000 according to the embodiment of this invention.

  The screen example shown in FIG. 10B is another result screen 7400 displayed in S4800 shown in FIG. The screen displayed in S4800 may display information on the maintenance possible date and the life extension sequence as in the result screen 7400.

  The purpose of the conventional technology is to improve the profits of the maintenance company by extending the life of parts and extending the maintenance schedule interval of customer equipment to reduce maintenance costs. For this reason, there is a problem that even if it is determined that the maintenance contractor is optimal, it is impossible to cope with a customer request to postpone maintenance work at a later date.

  With respect to this problem, in the present invention, the customer stores the maintenance available date on which the apparatus may be stopped and maintenance work may be performed in the apparatus when the apparatus is introduced. The device of the present invention continues to predict the lifetime of parts 1 to N constituting the device every day.

  When the life of a part becomes below a certain level, a part life extension sequence corresponding to the type of each part and the time until the nearest serviceable date is searched, and the searched part life extension sequence is executed. The part life extension sequence allows the machine to continue to operate without failure until the maintenance request date and time.

  The present invention reduces maintenance costs by performing maintenance work on equipment such as gas engines, elevators, and printers on a schedule that meets the demands of customers who operate such equipment, and extending the life of equipment until the maintenance date. It is for aiming at. The present invention can be applied to devices that require maintenance work and systems that manage maintenance work.

1000 Maintenance input device 2000 HDD
3000 server 5100 parts controller 6100 parts 6500 maintenance company server 6800 maintenance company side display 7000 display 2100 serviceable day database 2200 parts life information database 4100 data input program 4200 part life prediction program 4300 life extension sequence search program 4400 serviceable day search program 4500 maintenance Date determination program 4600 Component life extension sequence execution program 2110 Maintenance available date table 2230 Component type ID table 2260 Component life extension sequence table 3100 CPU
4000 RAM

Claims (10)

A server device connected to a component controller that acquires a physical quantity from a component included in a device used by a customer,
The server device
Accepting input by the customer for a maintenance date when the equipment can be stopped,
Receiving a physical quantity in the part acquired by the part controller;
Based on the received physical quantity, predict the life of the part,
Determining whether the predicted lifetime is shorter than a predetermined time;
When it is determined that the predicted life is shorter than a predetermined time, a day for maintaining the part determined to have the life shorter than the predetermined time is selected from the received maintenance date,
Determining whether the life determined to be shorter than the predetermined time is shorter than the time until the selected maintenance date;
If it is determined that the life determined to be shorter than the predetermined time is shorter than the time until the selected maintenance date, the part of the part determined to have a life shorter than the time until the selected maintenance date A server device characterized by acquiring a method for extending the service life. The server device
If it is determined that the predicted lifetime is shorter than a predetermined time, obtain the current time;
Select the maintenance date closest to the acquired current time among the maintenance dates input by the customer as the date for maintaining the parts,
Calculate the time from the current time to the selected maintenance date,
Whether the life determined to be shorter than the predetermined time by comparing the predicted life and the calculated time to the maintenance date is shorter than the time to the selected maintenance date. The server device according to claim 1, wherein the server device is determined. The server device
Holding information including the method of extending the life of the part and the time extended by the method;
The server apparatus according to claim 1, further comprising: acquiring a method for extending the life of a part determined to have a life shorter than a time until the selected maintenance date based on the held information. The method of extending the life of the component is determined in advance by the type of the component,
The server device
Holding information including a component ID uniquely indicating the component and a component type ID uniquely indicating the type of the component;
Receiving the physical quantity acquired by the parts controller and the part ID corresponding to the physical quantity;
The server apparatus according to claim 3, wherein the component type ID included in the held information is searched based on the received component ID. The server device
Holding information including the component type ID, a method of extending the life of the component corresponding to the component type ID, and a time extended by the method;
By searching for the component type ID included in the held information by the component ID of the component determined to have a life shorter than the time until the selected maintenance date,
Searching for the extended time from the stored information such that the part is extended for the time until the selected maintenance date,
The method according to claim 4, further comprising: obtaining a method for extending the lifetime of a component included in the held information based on the retrieved component type ID and the retrieved extended life time. Server device. A maintenance method of the device by a server device connected to a component controller that acquires a physical quantity from a component included in a device used by a customer,
The method
The server device accepts input by the customer for a maintenance date when the device can be stopped, and
The server device receives a physical quantity in the component acquired by the component controller;
The server device predicts the lifetime of the component based on the received physical quantity;
A procedure for the server device to determine whether the predicted lifetime is shorter than a predetermined time;
When it is determined that the predicted life is shorter than a predetermined time, the server device selects a date on which to maintain a component determined to have the life shorter than the predetermined time from the received maintenance date. Procedure and
A procedure for determining whether the server device has a life determined to be shorter than the predetermined time than a time until the selected maintenance date;
If the server apparatus determines that the life determined to be shorter than the predetermined time is shorter than the time until the selected maintenance date, the server apparatus determines that the life is shorter than the time until the selected maintenance date. And a procedure for obtaining a method for prolonging the life of the manufactured parts. The procedure for selecting the maintenance date from the maintenance date entered by the customer includes:
The server device obtains the current time;
The server device includes a procedure for selecting the maintenance date closest to the acquired current time among the acquired maintenance dates as a date for maintaining the component,
The procedure for determining whether the life determined to be shorter than the predetermined time is shorter than the time until the selected maintenance date,
The server device calculates a time from the current time to the selected maintenance date;
The maintenance method according to claim 6, wherein the server device includes a procedure for comparing the predicted lifetime with the calculated time until the maintenance date. The server device holds information including a method for extending the lifetime of the component, and a time to be extended by the method,
The procedure for obtaining a method for extending the life of the component is as follows:
The server apparatus includes a procedure of acquiring a method for extending the life of a part determined to have a life shorter than a time until the selected maintenance date based on the held information. Item 7. The maintenance method according to item 6. The method of extending the life of the component is determined in advance by the type of the component,
The server device stores information including a component ID that uniquely indicates the component and a component type ID that uniquely indicates the type of the component,
The procedure for receiving a physical quantity in a part from the part controller is as follows:
The server device includes a procedure of receiving the component ID corresponding to the physical quantity;
The procedure for obtaining a method for extending the life of the component is as follows:
The maintenance method according to claim 8, further comprising a procedure for the server device to search for the component type ID included in the held information based on the received component ID. The server device holds information including the component type ID, a method for extending the life of the component corresponding to the component type ID, and a time extended by the method,
The procedure for obtaining a method for extending the life of the component is as follows:
The server device searches for a component type ID included in the held information based on the component ID of a component determined to have a life shorter than the time until the selected maintenance date;
The server device retrieves the extended time from the stored information such that the component is extended for the time until the selected maintenance date,
The server device includes a procedure for acquiring a method for extending the lifetime of a component included in the held information based on the retrieved component type ID and the retrieved time to be extended. The maintenance method according to claim 9, wherein:

Images