JP6589470B2 - Schedule update device and schedule update program - Google Patents

Description

  The present invention relates to a schedule update device and a schedule update program.

  Patent Document 1 includes information acquisition means for acquiring internal information of a target device, and determination means for determining whether or not the target device is in a failure sign state based on the internal information acquired by the information acquisition means. In the failure sign notification system provided, the failure risk determination means for performing a failure risk determination process for determining the magnitude of failure risk that the target device may fail after the determination means is determined to be in a failure sign state, There is disclosed a failure sign notification system characterized by comprising notification means for notifying the determination result of the failure risk determination means.

JP 2010-091840 A

  The present invention relates to a schedule update device capable of updating a maintenance work schedule of an apparatus so that the maintenance work can be efficiently performed as compared with a case where a maintenance work is immediately performed when a sign is detected, and The purpose is to provide a schedule update program.

The schedule update apparatus according to claim 1 , wherein when there are a plurality of coping operations for coping with the failure in which the sign is detected, the acquisition unit performs the sign when the at least one of the plurality of coping operations is not performed. The estimated occurrence time at which the occurrence of the detected failure is estimated is acquired for each of the unexecuted coping operations among the plurality of coping operations, and the updating means is configured to determine whether the estimated occurrence time is in the schedule. For a countermeasure operation that has not yet been performed after the scheduled maintenance operation date, an implementation with the scheduled date as the scheduled execution date is added to the schedule, and the estimated occurrence time is the scheduled maintenance task execution date in the schedule. For coping operations that have not been performed before, the schedule is updated by adding to the schedule an implementation with a scheduled date before the scheduled date. To.

According to a second aspect of the present invention, there is provided the schedule update apparatus according to the first aspect , wherein the update unit adds the execution with the scheduled date of handling of the handling work before the scheduled date of execution to the schedule. When the schedule is updated, and the scheduled date of execution of the maintenance work similar to the handling work is ahead of the scheduled date of handling of the handling work, the similar scheduled maintenance date of the maintenance work in the schedule is set. The schedule is updated by changing the scheduled date for handling the handling work.

According to a third aspect of the present invention, there is provided the schedule update apparatus according to the first or second aspect , wherein the update means estimates the occurrence of a failure detected for the predictor, which is obtained for each of the unexecuted coping operations. The schedule is updated by setting the earliest estimated occurrence time of the estimated occurrence times as the estimated occurrence timing of the failure in which the sign is detected, and the acquisition unit is configured to update the failure of the failure in which the sign is detected. The estimated occurrence time updated by the updating means is acquired as the estimated occurrence time.

According to a fourth aspect of the present invention, there is provided the schedule update device according to the third aspect , wherein the update means changes the schedule in the schedule when the earliest estimated occurrence time is changed by updating the schedule. The schedule is updated by setting the earliest estimated occurrence time as the estimated occurrence time of the failure in which the sign is detected.

According to a fifth aspect of the present invention, in the schedule update device according to any one of the first to fourth aspects, the update means is a failure in which the acquired sign is detected for each of the unexecuted countermeasures. In the case where the estimated occurrence time at which the occurrence of occurrence is estimated is after the scheduled maintenance work execution date in the schedule, the scheduled execution date of the countermeasure work in the schedule is the earliest scheduled execution date of the scheduled execution dates Thus, the schedule is updated.

The schedule update apparatus according to claim 6 is the invention according to any one of claims 1 to 4 , wherein the update unit detects a failure in which the acquired sign is detected for each of the unexecuted countermeasures. If the estimated occurrence time estimated to occur is after the scheduled maintenance work implementation date in the schedule, the scheduled response date of the countermeasure work in the schedule is most likely to be the estimated occurrence time of the scheduled execution dates. The schedule is updated by setting the scheduled execution date close.

According to a seventh aspect of the present invention, in the schedule update device according to any one of the first to fourth aspects, the update means is a failure in which the acquired sign is detected for each of the unexecuted countermeasures. The estimated occurrence time is after the scheduled maintenance work execution date in the schedule, the work amount in the scheduled execution date is the smallest in the schedule. The schedule is updated by setting the scheduled execution date.

The schedule update device according to claim 8 is the invention according to any one of claims 1 to 4 , wherein the update means detects a failure in which the acquired sign is detected for each of the unexecuted countermeasures. If the estimated occurrence time when the occurrence of the failure is estimated is after the scheduled maintenance work execution date in the schedule, the countermeasure to the apparatus at the time of occurrence of the failure in which the sign is detected in the schedule is high. The schedule is updated so that work is given priority.

The schedule update program according to a ninth aspect causes a computer to function as each means constituting the schedule update apparatus according to any one of the first to eighth aspects.

According to the first and ninth aspects of the invention, the maintenance work schedule of the apparatus is more efficiently performed as compared with the case where all the coping works for dealing with the failure in which the sign is detected are performed simultaneously. Can be updated.

According to the second aspect of the present invention, the maintenance work schedule of the apparatus is updated so that the maintenance work can be performed more efficiently than when all the coping works are performed simultaneously regardless of the type of the coping work. Can do.

According to the invention of claim 3 , for a plurality of coping operations, the sign of failure is detected more accurately than when the sign of failure is detected without considering the estimated occurrence time when the occurrence of the failure is estimated. be able to.

According to the fourth aspect of the present invention, it is possible to detect a sign of failure more accurately than when the estimated occurrence time when the occurrence of the failure is estimated when the maintenance work schedule of the device is updated is not updated. .

According to the invention of claim 5 , the maintenance work schedule of the apparatus is compared with the case where the countermeasure work for dealing with the failure whose sign is detected is set as the scheduled maintenance execution date other than the earliest periodic maintenance. It can be updated to prevent outbreaks early.

According to the sixth aspect of the present invention, the maintenance work schedule of the apparatus, the coping work for dealing with the failure in which the sign is detected, the periodic maintenance other than the periodic maintenance immediately before the estimated occurrence time when the occurrence of the failure is estimated It can be updated so that the number of maintenance operations is reduced compared to the case where the scheduled date of execution is used.

According to the invention of claim 7 , when the maintenance work schedule of the apparatus is set to the scheduled work execution date of the periodic maintenance other than the periodic maintenance with the minimum work amount, the countermeasure work for dealing with the failure in which the sign is detected In comparison, it can be updated so that the load of the maintenance work on each regular maintenance execution work day is leveled.

According to the eighth aspect of the present invention, the maintenance work schedule of the apparatus is more serious than the case where the scheduled date for coping work is determined without considering the degree of influence on the apparatus when a failure occurs. It can be updated to avoid the occurrence of a failure in advance.

It is a block diagram which shows the electrical structure of the schedule update apparatus which concerns on embodiment. It is a block diagram which shows the functional structure of the schedule update apparatus which concerns on embodiment. It is a schematic diagram which shows an example before the update of the failure sign table which concerns on embodiment. It is a schematic diagram which shows an example after the update of the failure sign table which concerns on embodiment. It is a schematic diagram which shows an example of the maintenance work table which concerns on embodiment. It is a schematic diagram which shows an example of the information of the work amount table which concerns on embodiment. It is a schematic diagram which shows an example of the policy table which concerns on embodiment. It is a schematic diagram which shows an example before the update of the maintenance work schedule table which concerns on embodiment. It is a schematic diagram which shows an example after the update of the maintenance work schedule table which concerns on embodiment. It is a flowchart which shows the flow of the program of the update process which concerns on embodiment. It is a flowchart which shows the flow of the subroutine of the program of the 1st process which concerns on embodiment. It is a flowchart which shows the flow of the subroutine of the program of the 2nd process which concerns on embodiment. It is a flowchart which shows the flow of the subroutine of the program of the 3rd process which concerns on embodiment. It is a flowchart which shows the flow of the subroutine of the program of the 4th process which concerns on embodiment.

  Hereinafter, the schedule update apparatus according to the present embodiment will be described with reference to the accompanying drawings.

  As shown in FIG. 1, a schedule update device (hereinafter also simply referred to as “update device”) 10 according to the present embodiment includes a controller 12 that controls the entire device. The controller 12 also includes a CPU (Central Processing Unit) 14 that executes various processes including an update process, which will be described later, and a ROM (Read Only Memory) 16 that stores programs used for the processes of the CPU 14 and various information. ing. The controller 12 includes a RAM (Random Access Memory) 18 that temporarily stores various data as a work area of the CPU 14 and a non-volatile memory 20 that stores various information used for processing of the CPU 14. Further, the controller 12 includes an I / O interface 22 for inputting / outputting data to / from an external device connected to the update device 10. Connected to the I / O interface 22 are an operation unit 24 operated by a user, a display unit 26 that displays various types of information, and a communication unit 28 that communicates with an external device.

  When a sign of failure (hereinafter, also referred to as “failure sign”) is detected in a general image forming apparatus, a countermeasure work that is a maintenance work for dealing with the failure in which the sign is detected is performed each time. To be implemented. However, every time when a failure sign is detected, the operation of the image forming apparatus is stopped, so that the print job is not executed as planned or the work efficiency of the operator is reduced. Or the operating rate of the image forming apparatus may decrease.

  Here, the failure sign in the image forming apparatus means that the image forming apparatus is not self-healing, such as the toner runs out, a part failure occurs, or the printing paper runs out. It is a precursor to an event that requires it.

  On the other hand, in general image forming apparatuses, regular maintenance is performed in which maintenance work is performed according to a schedule planned in advance, such as every month or every day of the week.

  Therefore, the update device 10 according to the present embodiment, when a failure sign occurs, out of the work to cope with the failure in which the sign has been detected, the work that can be postponed is already registered Incorporate as new maintenance work on the scheduled date of implementation. As a result, maintenance work for dealing with a failure in which a sign is detected is efficiently performed.

  In other words, it is assumed that the update apparatus 10 detects a failure sign for an image forming apparatus in which maintenance work is performed according to a previously planned schedule. In this case, the update device 10 acquires the estimated occurrence time when the occurrence of the failure in which the sign is detected is estimated when the countermeasure work for dealing with the failure in which the sign is detected is not performed. In addition, when the estimated occurrence time of the unfinished countermeasure work is after the scheduled maintenance work implementation date in the schedule, the update apparatus 10 adds the execution of the unfinished countermeasure work with the scheduled date as the scheduled implementation date to the schedule. Update.

  In addition, when the estimated occurrence time of the unfinished countermeasure work is before the scheduled maintenance work implementation date in the schedule, the update apparatus 10 temporarily performs the unimplemented countermeasure work with the scheduled date before the scheduled implementation date. Updates to be added to the schedule as maintenance.

  The nonvolatile memory 20 stores a failure sign table 20A, a maintenance work table 20B, a work amount table 20C, a policy table 20D, and a maintenance work schedule table 20E as information for updating the maintenance work schedule.

  In the failure sign table 20A, as shown in FIG. 3A as an example, a failure sign ID, a failure sign name, and an estimated occurrence time indicating a time when the occurrence of the failure is estimated are associated with each other and stored.

  As shown in FIG. 4 as an example, the maintenance work table 20B includes a maintenance work ID, a work name, a failure sign ID requiring maintenance work, an estimated occurrence time of a failure requiring maintenance work, and a failure occurrence time. The degree of influence on each device is stored in association with each other.

  As shown in FIG. 5 as an example, the work amount table 20C stores a scheduled maintenance or temporary maintenance scheduled execution date and a periodic maintenance or temporary maintenance work amount in association with each other. Note that each time the maintenance work schedule is updated, the work amount on each scheduled maintenance date or regular maintenance is recalculated, and the work amount table 20C is updated.

  As shown in FIG. 6 as an example, the policy table 20D stores policy IDs, policy contents, and selections indicating which policies are selected in association with each other. In the selection item, 1 is set for the selected policy, and 0 is set for the policy that is not selected.

In the present embodiment, the following first policy to fourth policy are registered as a plurality of predetermined policies.
(1) First policy (advanced)
When incorporating the coping work into the regular maintenance, the coping work is incorporated in order from the regular maintenance with the earliest scheduled date of implementation.
(2) Second policy (postponed)
When incorporating coping operations into regular maintenance, coping operations are incorporated in order starting from the regular maintenance whose scheduled execution date is closest to the estimated occurrence time of the failure.
(3) Third policy (leveling)
When the coping work is incorporated into the regular maintenance, the coping work is incorporated so that the amount of work on the scheduled maintenance implementation date is equalized.
(4) Fourth policy (high priority of impact)
When the coping work is incorporated into the regular maintenance, the coping work is incorporated so that priority is given to the coping work that has a high influence on the image forming apparatus when the trouble occurs.

  When updating the maintenance work schedule, the update apparatus 10 according to the present embodiment updates the maintenance work schedule according to the policy selected from the plurality of policies described above.

  As shown in FIG. 7A as an example, the maintenance work schedule table 20E stores the execution ID, the type of maintenance work to be performed, the scheduled date of execution, and the maintenance work ID of the maintenance work to be performed in association with each other. Has been. As the type of maintenance work, “periodic” is set for scheduled maintenance, and “temporary” is set for temporary maintenance to deal with a failure in which a sign is detected. The

  In addition to the various tables described above, the non-volatile memory 20 previously stores correspondence information in which a failure sign and a coping operation for dealing with a failure corresponding to the failure sign are associated with each other. Each failure sign is associated with an estimated occurrence time and stored. On the other hand, each coping work is stored in association with an estimated occurrence time when the occurrence of a failure is estimated when the coping work is not performed. Then, the estimated occurrence time of the failure sign is sequentially updated so as to be the earliest estimated occurrence time among the estimated occurrence times of the coping work associated with the failure sign. In addition, information indicating the degree of influence described above is associated with each coping operation. In the present embodiment, when a failure sign is detected, a countermeasure work for coping with the failure for which the sign is detected is acquired from this correspondence information, and if necessary, the estimated occurrence timing and influence of the countermeasure work are obtained. Degree etc. are acquired.

  The non-volatile memory 20 stores similar information associated with each other such as similar maintenance work, for example, similar group A = {maintenance work A, maintenance work B, maintenance work C}. Yes. Based on the similarity information, it is determined whether each maintenance work is similar to each other maintenance work. In the present embodiment, as described above, similar information in which similar maintenance work is associated with each other is stored, but the present invention is not limited to this. For example, each maintenance operation is stored in the nonvolatile memory 20 with attribute information indicating similar maintenance operations added, and each maintenance operation is performed based on this attribute information. It may be determined whether or not it is similar to work.

  In addition, as illustrated in FIG. 2, the update device 10 according to the present embodiment includes a sign detection unit 30, a maintenance work extraction unit 32, a calculation unit 34, a maintenance work schedule unit 36, and a display control unit 38.

  The sign detection unit 30 detects a failure sign of the image forming apparatus, attaches a failure sign ID to the detected failure sign, and includes a failure sign name of the detected failure sign, and an estimated occurrence time of the failure according to the detected failure sign Register in the failure sign table 20A. In the present embodiment, for a failure that may occur in each part of the image forming apparatus, an event that is a failure sign and the failure sign are set in advance and stored in the nonvolatile memory 20. Then, when an event that is a failure sign occurs, each unit of the image forming apparatus notifies the sign detection unit 30 of a failure sign notification indicating the sign of the failure that has occurred. The sign detection unit 30 detects a failure sign of the image forming apparatus by receiving a failure sign notification from each part of the image forming apparatus. As described above, the estimated occurrence time of the failure sign is registered to be the earliest estimated occurrence time among the estimated occurrence times of the coping work that is a maintenance work for dealing with the failure according to the failure sign. The

  The maintenance work extraction unit 32 is an example of an acquisition unit. The maintenance work extraction unit 32 extracts a countermeasure work that is a maintenance work for dealing with a failure according to the failure sign registered in the failure sign table 20A. Therefore, the countermeasure work that has not been performed is registered in the maintenance work table 20B. In the present embodiment, the maintenance work extraction unit 32 acquires a countermeasure work for dealing with a failure according to the failure sign registered in the failure sign table 20A based on the above-described correspondence information, and the acquired countermeasure work Then, the countermeasure work that has not been performed is registered in the maintenance work table 20B.

  The calculation unit 34 is an example of an updating unit, and for each maintenance work registered in the maintenance work table 20B, the maintenance work scheduled date and the other maintenance work scheduled date do not perform the maintenance work. The effect on the estimated occurrence time of the failure sign of the failure that occurs in the case of failure is calculated. Further, the calculation unit 34 transmits the calculation result to the maintenance work schedule unit 36. Specifically, the calculation unit 34 determines whether or not a change occurs in the estimated occurrence time of the failure according to the failure sign by changing the scheduled execution date of the maintenance work. Then, when a change occurs in the estimated occurrence time of the failure according to the failure sign, the calculation unit 34 calculates the estimated occurrence time after the change as an influence on the estimated occurrence time of the failure according to the failure sign.

  The maintenance work schedule unit 36 is an example of an update unit, receives the calculation result by the calculation unit 34, incorporates the maintenance work registered in the maintenance work table 20B into the schedule according to the selected policy, and performs the maintenance work schedule table 20E. Update. Specifically, the maintenance work schedule unit 36, when the estimated occurrence time of the maintenance work is after the scheduled execution date of the earliest maintenance work in the schedule, performs the maintenance with the scheduled date as the scheduled maintenance execution date of regular maintenance or temporary maintenance. Add work to schedule. In addition, the maintenance work schedule unit 36, when the estimated occurrence time of the maintenance work is before the scheduled date of the earliest maintenance work in the schedule, sets the scheduled date before the scheduled date of the scheduled maintenance or temporary maintenance. Add the implementation to the schedule.

  The display control unit 38 causes the display unit 26 to display the contents registered in the maintenance work schedule table 20E.

  Here, a specific example of an update method when updating the schedule by setting the scheduled date for handling each maintenance work using the various tables shown in FIGS. 3A, 3B, 4, 7A, and 7B ( 1) to (5) are shown. In the specific examples (1) to (5), it is assumed that the third policy is selected. In addition, it is assumed that the reference date of specific examples (1) to (5) is “2015/3/15”.

(1) As shown in FIG. 3A, it is assumed that a failure sign “component Z failure” (failure occurrence time: 2015/5/12) with a failure sign ID “100001” is detected by the sign detection unit 30. In this case, as shown in FIG. 4, the maintenance work extraction unit 32 registers the maintenance work with the maintenance work ID “200001” (“part Z replacement”) in the maintenance work table 20B.

  The estimated occurrence time “2015/5/12” of the failure sign of the failure sign ID “100001” is later than the scheduled maintenance execution date “2015/4/15” of the execution ID “300001” which is the earliest periodic maintenance. It is. Therefore, as shown in FIG. 7A, the maintenance work with the maintenance work ID “20001” is added to the periodic maintenance on the scheduled execution date “2015/4/15”.

(2) As shown in FIG. 3A, it is assumed that a failure sign (estimated occurrence time: 2015/7/20) with a failure sign ID “100002” is detected by the sign detection unit 30. In this case, four maintenance works are extracted by the maintenance work extraction unit 32, and the maintenance works with the maintenance work IDs “20002” to “200005” are registered in the maintenance work table 20B as shown in FIG.

  Further, as shown in FIG. 7A, four regular maintenances with implementation IDs “300001” to “300004” are performed by the estimated occurrence time “2015/7/20” of the failure sign with the failure sign ID “100002”. . Therefore, as shown in FIG. 7A, for example, the maintenance work with the maintenance work IDs “200002” and “200003” is assigned to the periodic maintenance with the execution ID “300002”. Further, for example, the maintenance work with the maintenance work IDs “200004” and “200005” is assigned to the work execution with the execution ID “300003”. As a result, the schedule is updated so that the four maintenance operations for coping with the failure corresponding to the failure predictor ID “100002” are divided and executed on the scheduled dates of the two regular maintenance.

(3) As shown in FIG. 3A, it is assumed that a failure sign (estimated occurrence time: 2015/8/10) with a failure sign ID “100003” is detected by the sign detection unit 30. In this case, the maintenance work extraction unit 32 extracts three maintenance works, and the maintenance works with the maintenance work IDs “200006” to “200008” are registered in the maintenance work table 20B as shown in FIG.

  As shown in FIG. 7A, four regular maintenances with execution IDs “300001” to “300004” are performed by the estimated occurrence time “2015/8/10” of the failure sign. Here, the maintenance work already registered in the regular maintenance may include a maintenance work similar to the maintenance work registered in the maintenance work table 20B. For example, the maintenance work with the maintenance work ID “200006” (“image quality adjustment C”) is similar to the maintenance work with the maintenance work ID “200003” already registered in the regular maintenance (“image quality adjustment B”). To do. In this case, as shown in FIG. 7A, the maintenance work with the maintenance work ID “200006” is assigned to the periodic maintenance with the execution ID “300002” in which the maintenance work with the maintenance work ID “200003” is registered. Further, for example, the maintenance work with the maintenance work ID “200007” (“Drum 2 replacement”) is similar to the maintenance work with the maintenance work ID “200005” already registered in the regular maintenance (“Drum 1 replacement”). Suppose that In this case, as shown in FIG. 7A, the maintenance work with the maintenance work ID “200007” is assigned to the regular maintenance with the execution ID “300003” in which the maintenance work with the maintenance work ID “200005” is registered. Further, it is assumed that a maintenance work similar to the maintenance work ("Part Y exchange") with the maintenance work ID "200008" is not registered in the regular maintenance. In this case, as shown in FIG. 7A, the maintenance work with the maintenance work ID “200008” (“part Y replacement”) is assigned to the regular maintenance with the execution ID “300004”, for example, according to the selected policy.

(4) As shown in FIG. 3A, it is assumed that a failure sign (estimated occurrence time: 2015/4/13) of the failure sign ID “100004” is detected by the sign detection unit 30. In this case, as shown in FIG. 4, the maintenance work extraction unit 32 registers the maintenance work with the maintenance work ID “200009” (“toner (K) replenishment”) in the maintenance work table 20B.

  As shown in FIG. 7A, in the maintenance work schedule table 20E, the periodic maintenance is not registered until the estimated occurrence time “2015/4/13” of the failure sign with the failure sign ID “100004”. Therefore, as shown in FIG. 7A, the maintenance work schedule unit 36 can add the work execution of the execution ID “300006” as a temporary maintenance to the maintenance work schedule table 20E and implement the scheduled execution date earliest. It is assumed that the date is “2015/4/10”. Then, as shown in FIG. 7A, the maintenance work with the maintenance work ID “200009” is assigned to the temporary maintenance with the execution ID “300006”.

  Note that the feasible date in this embodiment is a day on which maintenance work can be physically performed, for example, a business day of a company that performs maintenance work, a day that a worker performing maintenance work can handle, etc. .

  At this stage, as shown in FIG. 7A, the maintenance work with the maintenance work ID “20001” (“part Z replacement”) is the regular maintenance with the execution ID “300001” (scheduled implementation date: 2015/4/15). Assigned to. However, as illustrated in FIG. 7B, the maintenance work with the maintenance work ID “20001” is reassigned to the temporary maintenance with the execution ID “300006” performed prior to the regular maintenance with the execution ID “300001”.

(5) As shown in FIG. 3A, it is assumed that a failure sign (estimated occurrence time: 2015/3/31) of the failure sign ID “100005” is detected by the sign detection unit 30. In this case, as shown in FIG. 4, the maintenance work extraction unit 32 performs maintenance work with the maintenance work ID “200010” (“part X1 replacement”) and maintenance work with the maintenance work ID “200011” (“part X2 replacement”). Is registered in the maintenance work table 20B.

  As shown in FIG. 7A, in the maintenance work schedule table 20E, the regular maintenance is not registered by the estimated occurrence timing “2015/3/31” of the failure sign. Here, as shown in FIG. 4, the estimated occurrence time of the maintenance work with the maintenance work ID “200010” is “2015/3/31”, but the estimated occurrence time of the maintenance work with the maintenance work ID “200011” is “ 2015/4/22 ". The calculation unit 34 sets the maintenance work with the maintenance work ID “200010” among the maintenance works with the maintenance work IDs “200010” and “200011” registered in the maintenance work table 20B by the estimated occurrence time “2015/3/31”. Assume that it has been completed. In this case, the calculation unit 34 calculates that the estimated occurrence timing of the failure sign of the failure sign ID “100005” can be postponed to “2015/4/22” as shown in FIG. 3B.

  Therefore, as shown in FIG. 7A, the maintenance work schedule unit 36 can add the work execution of the execution ID “300007” as the temporary maintenance to the maintenance work schedule table 20E and perform the scheduled execution date earliest. It is assumed that the date is “2015/3/27”. Then, as shown in FIG. 7A, the maintenance work with the maintenance work ID “200010” is assigned to the temporary maintenance with the execution ID “300007”, which is the temporary maintenance. Further, the maintenance work with the maintenance work ID “200011” is assigned to the regular maintenance with the execution ID “300001”, which is the regular maintenance, for example. Further, as shown in FIG. 3B, the maintenance work schedule unit 36 updates the estimated occurrence timing of the failure sign of the failure sign ID “100005” to “2015/4/22” in the failure sign table 20A.

  Next, the flow of processing when performing the update processing executed by the CPU 14 of the update device 10 according to the present embodiment will be described with reference to the flowcharts shown in FIGS.

  FIG. 8 is a flowchart showing the overall flow of the update process. FIG. 9 is a flowchart showing the flow of the first process which is a subroutine executed when the update process is executed, and FIG. 10 shows the flow of the second process which is a subroutine executed when the update process is executed. It is a flowchart. FIG. 11 is a flowchart showing a flow of a third process which is a subroutine executed when the update process is executed, and FIG. 12 shows a flow of a fourth process which is a subroutine executed when the update process is executed. It is a flowchart.

  In the present embodiment, the update processing program is stored in the nonvolatile memory 20 in advance, but is not limited thereto. For example, the update processing program may be received from an external device via the communication unit 28 and executed. Further, the update process may be executed by reading a program of the update process recorded on a recording medium such as a CD-ROM via the I / O interface 22 by a CD-ROM drive or the like.

  In this embodiment, the update processing program is executed every time a fixed period (for example, 0.1 seconds) elapses while the update apparatus 10 is operating, but the execution timing is not limited to this. It may be executed when an execution instruction is input through the operation unit 24.

  In step S101, the sign detection unit 30 determines whether or not a failure sign has occurred. In this embodiment, the sign detection unit 30 determines that a failure sign has occurred when failure sign information is received from each part of the image forming apparatus. If it is determined in step S101 that a failure sign has occurred (S101, Y), the process proceeds to step S103, and if it is determined that a failure sign has not occurred (S101, N), execution of the program for this update process is terminated. To do.

  In step S <b> 103, the sign detection unit 30 acquires failure sign information related to the failure sign that has occurred. In the present embodiment, the sign detection unit 30 acquires a failure sign name and an estimated occurrence timing of the generated failure sign as the failure sign information based on the failure sign information received from each unit of the image forming apparatus. Then, the sign detection unit 30 attaches a failure sign ID to the generated failure sign, and registers the failure sign name and estimated occurrence time of the generated failure sign in the failure sign table 20A in association with the failure sign ID.

  In step S105, the maintenance work extraction unit 32 extracts a maintenance work for coping with a failure in which a sign is detected, and registers the maintenance work in the maintenance work table 20B. In the present embodiment, the maintenance work extraction unit 32 extracts a maintenance work corresponding to the failure sign that has occurred from the correspondence information described above.

  In step S107, the maintenance work schedule unit 36 acquires the currently selected policy. In the present embodiment, the maintenance work schedule unit 36 acquires the currently selected policy from the policy table 20D, but the policy acquisition method is not limited to this. For example, the maintenance work schedule unit 36 may display a plurality of selectable policies on the display unit 26 and allow the user to select using the operation unit 24 to acquire the selected policy.

  In step S109, the maintenance work schedule unit 36 determines whether or not the selected policy is the first policy. If it is determined that the policy selected in step S109 is the first policy (S109, Y), the process proceeds to step S111. If it is determined that the policy is not the first policy (S109, N), the process proceeds to step S113.

  In step S111, the maintenance work schedule unit 36 performs a first process for updating the maintenance work schedule according to the first policy. The first process will be described later.

  In step S113, the maintenance work schedule unit 36 determines whether or not the selected policy is the second policy. If it is determined that the policy selected in step S113 is the second policy (S113, Y), the process proceeds to step S115. If it is determined that the policy is not the second policy (S113, N), the process proceeds to step S117.

  In step S115, the maintenance work schedule unit 36 performs a second process of updating the maintenance work schedule according to the second policy. The second process will be described later.

  In step S117, the maintenance work schedule unit 36 determines whether or not the selected policy is the third policy. If it is determined that the policy selected in step S117 is the third policy (S117, Y), the process proceeds to step S119. If it is determined that the policy is not the third policy (S117, N), that is, the fourth policy. If determined, the process proceeds to step S121.

  In step S119, the maintenance work schedule unit 36 performs a third process of updating the maintenance work schedule according to the third policy. The third process will be described later.

  In step S121, the maintenance work schedule unit 36 performs a fourth process of updating the maintenance work schedule according to the fourth policy. The fourth process will be described later.

  Here, a flow of a subroutine when the maintenance work schedule unit 36 performs the first process will be described with reference to a flowchart shown in FIG. The first processing is performed according to a first policy for the purpose of performing maintenance work ahead of schedule. The first process is a process for incorporating maintenance work in order from the earliest regular maintenance when incorporating a new maintenance work into the regular maintenance.

  In step S <b> 201, the maintenance work schedule unit 36 acquires the scheduled date for performing regular maintenance or temporary maintenance. In the present embodiment, the scheduled execution date of the periodic maintenance or the temporary maintenance with the closest date among the periodic maintenance or the temporary maintenance already registered in the maintenance work schedule table 20E is acquired.

  In step S <b> 203, the maintenance work schedule unit 36 acquires the estimated occurrence timing of each coping work that is a maintenance work for coping with a failure in which a sign is detected. For example, when a failure sign with a failure sign ID “100002” occurs, the estimated occurrence timing of each maintenance work with the maintenance work IDs “200002” to “200005” is acquired.

  In step S205, the maintenance work schedule unit 36 selects one coping work from the coping works for which the estimated occurrence time has been acquired.

  In step S207, the maintenance work schedule unit 36 determines whether or not the scheduled execution date of the periodic maintenance or the temporary maintenance with the earliest scheduled execution date is before the estimated occurrence time of the coping work selected in step S205. When it is determined in step S207 that the scheduled execution date is before the estimated occurrence time of the coping work (S207, Y), the process proceeds to step S209, and when it is determined that the scheduled execution date is not before the estimated occurrence time of the coping work (S207). , N) proceeds to step S211.

  In step S209, the maintenance work schedule unit 36 sets the scheduled date of handling of the handling work selected in step S205 as the scheduled date of implementation of the earliest periodic maintenance or temporary maintenance. In addition, if the work to be performed is added to the scheduled date for the earliest scheduled maintenance or temporary maintenance, and the amount of work on the scheduled date exceeds the workable amount, the scheduled date for handling the next scheduled work The scheduled date for scheduled or temporary maintenance.

  In step S211, the scheduled maintenance date for the coping work selected in step S205 by the maintenance work scheduling unit 36 is a date before the estimated occurrence time of the coping work selected in step S205, and regular maintenance or temporary maintenance is performed. A date other than the scheduled date. In the present embodiment, the maintenance work schedule unit 36 sets the scheduled action date for the handling work selected in step S205 as the earliest possible implementation date.

  In step S213, the maintenance work schedule unit 36 confirms whether there is a maintenance work similar to the selected work to be performed, and the maintenance work for the regular maintenance or the temporary maintenance already registered in the maintenance work schedule table 20E. To get. In this embodiment, the maintenance work after the scheduled action date of the selected action is acquired.

  In step S215, the maintenance work schedule unit 36 determines whether the maintenance work acquired in step S213 includes a maintenance work similar to the coping work selected in step S205. In the present embodiment, based on the similar information described above, if there is a maintenance work associated with the coping work selected in step S205 among the maintenance work acquired in step S213, there is a similar maintenance work. judge. If it is determined in step S215 that the acquired maintenance work includes a maintenance work similar to the selected countermeasure work (S215, Y), the process proceeds to step S217, and the acquired maintenance work includes If it is determined that maintenance work similar to the selected coping work is not included (S215, N), the process proceeds to step S219.

  In step S217, the maintenance work schedule unit 36 changes the scheduled maintenance work execution date similar to the selected response work to the scheduled response date of the selected response work.

  In step S219, the maintenance work schedule unit 36 determines whether or not there is a handling work that has not been selected in step S205 among the handling works for which the estimated occurrence time has been acquired. If it is determined that there is a coping work not selected in step S219 (S219, Y), the process returns to step S205, the coping work not selected in step S205 is selected, and the processes in steps S207 to S219 are performed again. When it is determined that there is no coping work not selected in step S219 (S219, N), that is, when the processes of steps S207 to S219 are performed for all coping work, the first process is terminated, and the step of FIG. The process proceeds to S123.

  Next, the flow of a subroutine when the maintenance work schedule unit 36 performs the second process will be described with reference to the flowchart shown in FIG. The second process is performed according to a second policy for the purpose of performing maintenance work in a postponed manner. The second process is a process of incorporating maintenance work in order from the periodic maintenance close to the estimated occurrence time of the failure when incorporating a new maintenance work into the regular maintenance.

  In step S <b> 301, the maintenance work schedule unit 36 acquires a scheduled date for performing regular maintenance or temporary maintenance. In the present embodiment, the scheduled execution date of each regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E is acquired.

  In step S303, as in step S203, the maintenance work schedule unit 36 acquires the estimated occurrence timing of each of the handling work, which is a maintenance work for dealing with a failure in which a sign has been detected.

  In step S305, as in step S205, the maintenance work schedule unit 36 selects one coping work from the coping works for which the estimated occurrence time has been acquired.

  In step S307, as in step S207, the maintenance work schedule unit 36 determines whether or not the scheduled execution date of the periodic maintenance or the temporary maintenance with the earliest scheduled execution date is before the estimated occurrence time of the countermeasure work selected in step S305. Determine whether. When it is determined in step S307 that the scheduled execution date is before the estimated occurrence time of the coping work (S307, Y), the process proceeds to step S309, and when it is determined that the scheduled execution date is not before the estimated occurrence time of the coping work (S307). , N) proceeds to step S311.

  In step S309, the maintenance work schedule unit 36 sets the scheduled date of handling of the handling work selected in step S305 as the scheduled date of scheduled periodic maintenance or temporary maintenance immediately before the estimated timing of the handling work. In the present embodiment, the regular maintenance or the temporary maintenance immediately before the estimated occurrence time of the coping work means that the scheduled execution date is earlier than the estimated occurrence time of the coping work, and the scheduled execution date is closest to the estimated occurrence time of the coping work. Regular maintenance or temporary maintenance. For example, it is assumed that the maintenance work with the maintenance work ID “200002” is a countermeasure work. In this case, the estimated occurrence time of coping work is 2015/7/20. For this reason, the scheduled maintenance date of the scheduled maintenance work for the execution ID “300004” that is the closest to the estimated occurrence date and whose scheduled execution date is before the estimated occurrence time of the regular maintenance or the temporary maintenance is set as the scheduled action date 2015 / 7/15. In addition, if a countermeasure work is added on the scheduled execution date of regular maintenance or temporary maintenance immediately before the estimated occurrence time of the countermeasure work, the work amount on the scheduled execution date may exceed the workable amount. In this case, the scheduled date of handling of the handling work is set as the scheduled date of scheduled periodic maintenance or temporary maintenance next to the estimated occurrence time.

  In step S311, the maintenance work schedule unit 36 sets the scheduled date of handling of the handling work selected in step S305 to a date before the estimated occurrence time of the handling work selected in step S305 and other than the scheduled date of implementation. To do. In the present embodiment, the maintenance work schedule unit 36 sets the scheduled action date of the countermeasure work selected in step S305 as the feasible date closest to the estimated occurrence time and before the estimated occurrence time.

  In step S313, as in step S213, the maintenance work schedule unit 36 acquires maintenance work for regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E. In this embodiment, the maintenance work after the scheduled action date of the selected action is acquired.

  In step S315, as in step S215, the maintenance work schedule unit 36 determines whether the maintenance work acquired in step S313 includes a maintenance work similar to the countermeasure work selected in step S305. . If it is determined in step S315 that the acquired maintenance work includes a maintenance work similar to the selected countermeasure work (S315, Y), the process proceeds to step S317, and the acquired maintenance work includes If it is determined that the maintenance work similar to the selected coping work is not included (S315, N), the process proceeds to step S319.

  In step S317, similar to step S217, the maintenance work schedule unit 36 changes the scheduled maintenance work execution date similar to the selected response work to the scheduled response date of the selected response work.

  In step S319, the maintenance work schedule unit 36 determines whether there is a coping work that has not been selected in step S305. If it is determined that there is a coping work not selected in step S319 (S319, Y), the process returns to step S305, the coping work not selected in step S305 is selected, and the processes of steps S307 to S319 are performed again. If it is determined in step S319 that there is no coping work not selected (S319, N), that is, if the processes of steps S307 to S319 are performed for all coping work, the second process is terminated, and step S123 of FIG. Migrate to

  Next, the flow of a subroutine when the maintenance work schedule unit 36 performs the third process will be described with reference to the flowchart shown in FIG. The third process is performed according to a third policy for the purpose of performing maintenance work while leveling. The third process is a process for incorporating maintenance work so that the amount of work on the scheduled execution date of each regular maintenance is equalized when a new maintenance work is incorporated into the regular maintenance.

  In step S <b> 401, the maintenance work schedule unit 36 acquires the scheduled date for performing regular maintenance or temporary maintenance. In the present embodiment, the scheduled execution date of each regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E is acquired.

  In step S403, as in step S203, the maintenance work schedule unit 36 acquires the estimated occurrence timing of each of the handling work, which is a maintenance work for dealing with a failure in which a sign has been detected.

  In step S405, as in step S205, the maintenance work schedule unit 36 selects one coping work out of coping works for which the estimated occurrence time has been acquired.

  In step S407, as in step S207, the maintenance work schedule unit 36 determines whether the scheduled maintenance execution date of the periodic maintenance or the temporary maintenance with the earliest scheduled execution date is before the estimated occurrence time of the countermeasure work selected in step S405. Determine whether. When it is determined in step S407 that the scheduled execution date is before the estimated occurrence time of the coping work (S407, Y), the process proceeds to step S409, and when it is determined that the scheduled execution date is not before the estimated occurrence time of the coping work (S407). , N) proceeds to step S413.

  In step S409, the scheduled execution date of each regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E and the workload on the scheduled execution date are acquired from the work amount table 20C. In the present embodiment, the work amount stored in the work amount table 20C is acquired, but is not limited thereto. For example, the work amount of each scheduled execution date may be calculated using the scheduled execution date and maintenance work of each regular maintenance or temporary maintenance registered in the maintenance work schedule table 20E. In this case, the work amount of each maintenance work is stored in advance in the non-volatile memory 20, and the work amount of each maintenance work performed on the scheduled execution date is integrated to obtain each scheduled work date. The amount of work is required.

  In step S411, the maintenance work schedule unit 36 sets the scheduled handling date of the handling work selected in step S405 as the scheduled execution date before the estimated occurrence time of the handling work and with the least amount of work. For example, in the example illustrated in FIG. 5, for example, when the estimated occurrence time of the coping work is after August, the day with the smallest work amount is “2015/4/13”. , “2015/4/13”.

  In step S413, as in step S211, the maintenance work schedule unit 36 sets the scheduled date for handling of the coping work selected in step S405, which is a date before the estimated occurrence time of the coping work dealt in step S405, and is executed. A date other than the scheduled date.

  In step S415, as in step S213, the maintenance work schedule unit 36 acquires maintenance work for regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E. In this embodiment, the maintenance work after the scheduled action date of the selected action is acquired.

  In step S417, as in step S215, the maintenance work schedule unit 36 determines whether the maintenance work acquired in step S415 includes a maintenance work similar to the countermeasure work selected in step S405. . If it is determined in step S417 that the acquired maintenance work includes a maintenance work similar to the selected countermeasure work (S417, Y), the process proceeds to step S419, and the acquired maintenance work includes When it is determined that the maintenance work similar to the selected coping work is not included (S417, N), the process proceeds to step S421.

  In step S419, as in step S217, the maintenance work schedule unit 36 changes the scheduled maintenance work execution date similar to the selected handling work to the scheduled handling date of the selected handling work.

  In step S421, the maintenance work schedule unit 36 determines whether there is a coping work that has not been selected in step S405. When it is determined that there is a coping work that has not been selected in step S421 (S421, Y), the process returns to step S405, a coping work that is not selected in step S405 is selected, and the processes of steps S407 to S421 are performed again. If it is determined that there is no coping work not selected in step S421 (S421, N), that is, if the processes of steps S407 to S421 are performed for all coping work, the third process is terminated, and step S123 of FIG. Migrate to

  Next, the flow of a subroutine when the maintenance work schedule unit 36 performs the fourth process will be described with reference to the flowchart shown in FIG. Note that the fourth process is performed according to a fourth policy for the purpose of giving priority to maintenance work from those having a large influence. In the fourth process, when a new maintenance work is incorporated into the regular maintenance, the maintenance work is prioritized so that the priority is given to the maintenance work having a high influence on the image forming apparatus when the failure corresponding to the maintenance work occurs. Incorporation process.

  In step S <b> 501, the maintenance work schedule unit 36 acquires a scheduled date for performing regular maintenance or temporary maintenance. In the present embodiment, the scheduled execution date of each regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E is acquired.

  In step S503, as in step S203, the maintenance work schedule unit 36 acquires the estimated occurrence timing of each of the handling work, which is a maintenance work for dealing with the failure in which the sign is detected.

  In step S505, the maintenance work schedule unit 36 selects one coping work from the coping works for which the estimated occurrence time has been acquired, and obtains the influence level of the selected coping work. In the present embodiment, when acquiring the degree of influence of the selected coping work, the degree of influence associated with the selected coping work is obtained from the maintenance work table 20B.

  In step S507, as in step S207, the maintenance work schedule unit 36 determines whether the scheduled maintenance execution date for the periodic maintenance or the temporary maintenance with the earliest scheduled execution date is before the estimated occurrence time of the countermeasure work selected in step S305. Determine whether. When it is determined in step S507 that the scheduled execution date is before the estimated occurrence time of the coping work (S507, Y), the process proceeds to step S509, and when it is determined that the scheduled execution date is not before the estimated occurrence time of the coping work (S507). , N) proceeds to step S511.

  In step S509, the maintenance work schedule unit 36 sets the scheduled date of handling of the handling work selected in step S505 as the scheduled date of execution of regular maintenance or temporary maintenance before the estimated occurrence time of the handling work and according to the degree of influence. To do. In the present embodiment, the scheduled action date for the handling work is determined so that the scheduled action date becomes earlier as the degree of influence increases. For example, when the degree of influence is higher than a predetermined first threshold, the earliest scheduled maintenance date for temporary maintenance or temporary maintenance may be used. In addition, when the degree of influence is lower than a predetermined second threshold (<first threshold), the scheduled maintenance date may be the regular maintenance or the temporary maintenance immediately before the estimated occurrence time of the coping work.

  In step S511, similar to step S211, the maintenance work schedule unit 36 sets the scheduled action date for the coping work selected in step S405, which is the day before the estimated occurrence time of the coping work selected in step S505. A date other than the scheduled date.

  In step S513, as in step S213, the maintenance work schedule unit 36 acquires maintenance work for regular maintenance or temporary maintenance already registered in the maintenance work schedule table 20E. In this embodiment, the maintenance work after the scheduled action date of the selected action is acquired.

  In step S515, as in step S215, the maintenance work schedule unit 36 determines whether the maintenance work acquired in step S513 includes a maintenance work similar to the coping work selected in step S505. . If it is determined in step S515 that the acquired maintenance work includes a maintenance work similar to the selected countermeasure work (S515, Y), the process proceeds to step S517, and the acquired maintenance work includes If it is determined that maintenance work similar to the selected coping work is not included (S515, N), the process proceeds to step S519.

  In step S517, as in step S217, the maintenance work schedule unit 36 changes the scheduled maintenance work execution date similar to the selected response work to the scheduled response date of the selected response work.

  In step S519, the maintenance work schedule unit 36 determines whether there is a coping work that has not been selected in step S505. When it is determined that there is a coping work not selected in step S519 (S519, Y), the process returns to step S505, a coping work not selected in step S505 is selected, and the processes of steps S507 to S519 are performed again. If it is determined in step S519 that there is no coping work not selected (S519, N), that is, if the processes of steps S507 to S519 are performed for all coping work, the fourth process is terminated, and step S123 of FIG. Migrate to

  In step S123 of FIG. 8, the maintenance work schedule unit 36 updates the estimated occurrence time of the failure in which the sign is detected in the sign of failure sign table 20A shown in FIGS. 3A and 3B. In the present embodiment, the earliest estimated occurrence time is updated as the estimated occurrence time of the failure among the estimated occurrence times of each of the coping operations that are maintenance operations for coping with the failure.

  In step S125, the display control unit 38 performs control to display the maintenance work schedule table 20E on the display unit 26, and ends the execution of the program for the update process.

  As described above, in this embodiment, when a failure sign is detected, the maintenance work is not performed every time, but when the periodic maintenance is performed before the estimated occurrence time of the failure according to the failure sign. Incorporate new maintenance work on the scheduled maintenance implementation date. Thus, the maintenance work schedule is updated so that the maintenance work is performed efficiently.

  Further, in the present embodiment, when a failure according to the failure sign occurs, there may be a plurality of maintenance operations for dealing with the failure. In such a case, when each of the plurality of maintenance works can be performed separately, the work execution date is set for each of the plurality of maintenance works according to the selected policy. As a result, the maintenance work schedule is updated so that the schedule reflects the user's intention.

  In addition, when there are a plurality of similar maintenance operations, a work execution date is set for each of the plurality of maintenance operations so that a plurality of similar maintenance operations are performed on the same scheduled execution date. As a result, even if the worker in charge of the work is a worker who can only perform maintenance work on a specific part, a plurality of maintenance work is efficiently performed.

  Further, if at least one estimated occurrence time of the maintenance work for dealing with the failure in which the sign is detected is before the scheduled date of the earliest periodic maintenance, a new temporary maintenance is registered. In addition, when a new temporary maintenance is registered, the maintenance work that can be incorporated into the temporary maintenance among other maintenance work is collectively incorporated. As a result, even when the operation of the image forming apparatus is stopped unscheduled by performing temporary maintenance, other maintenance work is also performed, and a plurality of maintenance work is efficiently performed.

  Further, in the present embodiment, there is a case in which the estimated occurrence time of the failure in which the sign is detected is before the earliest scheduled scheduled maintenance date and there are a plurality of maintenance operations for dealing with the failure. In this case, if a part of the plurality of maintenance work is performed, the estimated occurrence time of the failure may be postponed before the scheduled scheduled maintenance date. In such a case, a part of maintenance work is incorporated as a temporary maintenance on a new scheduled execution date, and the remaining maintenance work is incorporated on a scheduled maintenance execution date.

  For example, there are four states A to D ([A: Unusable] → [B: Usable after 2 hours] → [C: Usable after one week] → [D: Perfect]) as printer states of the image forming apparatus. Define. If a failure sign is detected when the estimated occurrence time of the failure is 2 hours later, if three maintenance work among a plurality (for example, eight) of maintenance work for dealing with the failure with the detected sign is performed, [ It is assumed that B: usable after 2 hours] to [C: usable after 1 week]. In that case, if the scheduled date of scheduled maintenance is one week later, three maintenance tasks will be incorporated into the new scheduled date as temporary maintenance, and the remaining maintenance will be performed in the scheduled maintenance after one week. As a result, the operation stop time of the image forming apparatus is suppressed.

  In this embodiment, the update process is performed according to any one of the first to fourth policies. However, the present invention is not limited to this, and the update process is performed according to a policy that combines two or more of the first to fourth policies. You can go. For example, the third policy and the fourth policy are combined, the maintenance work of a failure having a high influence on the image forming apparatus is incorporated in the earliest periodic maintenance, and the other maintenance work is incorporated on the scheduled execution date with a small amount of work. The amount of work on the scheduled implementation date may be leveled.

  In this embodiment, the update process for updating the maintenance work schedule of the image forming apparatus has been described. However, the target apparatus is not limited to the image forming apparatus, and any apparatus can be used as long as it performs periodic maintenance. It doesn't matter. Examples of the target device include an image reproduction device, an image recording device, an information processing device, an automobile, a motorcycle, and a lighting device.

  In this embodiment, the update process for updating the maintenance work schedule of one image forming apparatus has been described. However, a plurality of target apparatuses may be used. When a plurality of devices are targeted, an update process for updating the entire schedule including the maintenance work for each device is performed so that the maintenance work for each device can be efficiently performed as a whole.

  In the present embodiment, the schedule is updated on a daily basis, such as “scheduled implementation date”. However, the schedule is not limited to this, and the schedule may be updated on a monthly, weekly, or hourly basis.

10 device 12 controller 14 CPU
16 ROM
18 RAM
DESCRIPTION OF SYMBOLS 20 Nonvolatile memory 20A Failure sign table 20B Maintenance work table 20C Work volume table 20D Policy table 20E Maintenance work schedule table 22 I / O interface 24 Operation part 26 Display part 28 Communication part 30 Prediction detection part 32 Maintenance work extraction part 34 Calculation part 36 Maintenance work schedule section 38 Display control section

Claims (9)

When a failure sign is detected for a device for which maintenance work is performed according to a pre-planned schedule, there are a plurality of countermeasures for dealing with the failure for which the sign is detected , and at least one of the plurality of countermeasures An acquisition means for acquiring an estimated occurrence time at which the occurrence of a failure with the detected sign is estimated for each of the unexecuted coping operations among the plurality of coping operations ,
When the estimated occurrence time of the unexecuted coping work is after the scheduled execution date of the maintenance work in the schedule, the execution of the unimplemented coping work with the scheduled date as the scheduled execution date is added to the schedule And
If the estimated occurrence time of the unexecuted coping work is before the scheduled execution date of the maintenance work in the schedule, the schedule of performing the unexecuted coping work with the scheduled date before the scheduled execution date Updating means for updating the schedule by adding to
Schedule update device provided. The updating means updates the schedule by adding to the schedule an implementation with the scheduled date of handling of the handling work before the scheduled date of execution, and the maintenance work similar to the handling work. When the scheduled execution date is earlier than the scheduled date of handling of the handling work, the schedule is updated by changing the scheduled maintenance date of the similar maintenance work in the schedule to the scheduled date of handling of the handling work. The schedule update device according to claim 1 . The update means detects the earliest estimated occurrence time of the estimated occurrence times obtained for each of the unexecuted coping operations and estimated to be the occurrence of the failure with the detected sign. Update the schedule by assuming the estimated occurrence time of the failure,
It said acquisition means as an estimated occurrence time of failure the sign is detected, schedule update apparatus according to claim 1 or 2, wherein obtaining the estimated occurrence time updated by the updating means. The update means, when the schedule is updated and the earliest estimated occurrence time is changed, the earliest estimated occurrence time after the change in the schedule is estimated and the failure is detected. The schedule update apparatus according to claim 3 , wherein the schedule is updated by setting the time. When the estimated occurrence time at which the occurrence of a failure in which the acquired sign is detected is estimated for each of the unsettled work is after the scheduled maintenance work execution date in the schedule, The schedule update device according to any one of claims 1 to 4 , wherein the schedule is updated by setting the scheduled date of handling of the handling work in the schedule as the scheduled date of implementation among the scheduled dates of implementation. When the estimated occurrence time at which the occurrence of a failure in which the acquired sign is detected is estimated for each of the unsettled work is after the scheduled maintenance work execution date in the schedule, the any one of claims 1 to 4 by the closest the implementation date of the estimated occurrence time updating the schedule of the implementation date to deal date of the addressing operations in the schedule Schedule update device. When the estimated occurrence time at which the occurrence of a failure in which the acquired sign is detected is estimated for each of the unsettled work is after the scheduled maintenance work execution date in the schedule, , said any one of claims 1 to 4, the amount of work of the implementation date to deal date coping operation to update the schedule by the above-described date is minimal in the schedule Schedule update device. When the estimated occurrence time at which the occurrence of a failure in which the acquired sign is detected is estimated for each of the unsettled work is after the scheduled maintenance work execution date in the schedule, The schedule according to any one of claims 1 to 4 , wherein the schedule is updated so that priority is given to the coping operation that has a high degree of influence on the device when a failure in which the sign is detected in the schedule occurs. Update device. The schedule update program for functioning a computer as each means which comprises the schedule update apparatus in any one of Claims 1-8 .

Images