System and method
The system estimates and provides feedback on maintenance work order using error and historical data, addressing the cumbersome manual recording issue in existing systems, enhancing accuracy and efficiency.
Patent Information
- Application Number
- JP2023081803
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-17
- Publication Date
- 2024-11-28
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing repair location notification systems require service personnel to manually record maintenance work details after resolving errors, which is cumbersome and affects the accuracy of estimating the order of repairs.
A system that estimates the order of device maintenance work based on error data and historical data, providing feedback without requiring manual recording, by using a first work estimating means to determine the target location, content, and priority of the work, and a storage means to store the order of subsequent work performed.
Enables accurate estimation and feedback on the order of maintenance work during the process, improving efficiency and accuracy without manual recording.
Smart Images

Figure 2024165528000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a system and method. [Background technology]
[0002] Conventionally, systems have been developed that manage the information and status of devices such as printers (hereinafter referred to as "devices"). In such systems, when a malfunction or failure occurs in a device, a server receives a notification of the malfunction or failure sent from the device, and the occurrence of the malfunction or failure can be managed. The occurrence of the malfunction or failure can be, for example, the date and time when the malfunction or failure occurred, the device on which the malfunction or failure occurred, and the specific details of the malfunction or failure. Such systems are used to perform appropriate work at an appropriate time when a serviceman visits a customer and performs maintenance work on the customer's device as an after-sales service for the company that sold the device. In addition, such systems are also equipped with a function that allows the details of the work performed by the serviceman for the malfunction or failure to be registered in the system in order to perform the maintenance work smoothly. As a result, the system is developed as a system (hereinafter sometimes referred to as a "repair location notification system") that notifies the location of the malfunction or failure estimated based on the error, that is, the location where repairs should be performed, thereby making the maintenance work more efficient.
[0003] Furthermore, in order to improve the accuracy of the process of estimating the location where repairs should be performed, a mechanism has been proposed that allows a service technician to report the maintenance work they performed after an error has been resolved. For example, Patent Document 1 discloses a system that generates a work sequence that reflects the contents of a maintenance contract in advance and presents it to the user. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2021-33488 Summary of the Invention [Problem to be solved by the invention]
[0005] In addition, when a service technician performs multiple tasks, the later the task is performed, the more likely it is that it will be effective in fixing the error. Therefore, in order to improve the accuracy of the repair point notification system, it is necessary to have the service technician record the order in which they were performed. However, this is cumbersome, as it requires the service technician, whose top priority is solving the error, to register the details of the tasks before the error is resolved.
[0006] In view of the above problems, the present invention aims to provide a system and method that can estimate the order in which device maintenance work is performed by the system without the user having to record it themselves while performing the maintenance work, and that can be used to provide feedback on the estimation regarding the work. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems, the system of the present invention is characterized by comprising: a first task estimation means for estimating, for each of at least one first task required to resolve an error in a device, a location to be subjected to the first task, the content of the first task, and a priority of the first task based on error data indicating the content of an error that has occurred in the device and historical data related to the device; a first task data providing means for providing first task data indicating, for each of the at least one first task, the location to be subjected to the first task, the content of the first task, and the priority of the first task; a second task data receiving means for receiving second task data indicating, for each of at least one second task that is actually performed on the device to resolve the error in the device, the location to be subjected to the second task and the content of the second task; and a storage means for storing the order in which the at least one second task is performed, identified based on the second task data, to be used as feedback for the estimation by the first task estimation means. Effect of the Invention
[0008] According to the present invention, the order in which maintenance work on devices is performed can be estimated by the system without the user having to record it while performing the maintenance work, and the order can be used as feedback for estimation regarding the work. [Brief description of the drawings]
[0009] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a repair location notification server included in the system according to the embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of the hardware configuration of a printer included in the system according to the embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a software configuration of a system according to an embodiment. [Diagram 5] 10 is a flowchart illustrating an example of a repair part estimation process according to the embodiment. [Figure 6] 10 is a flowchart illustrating an example of a repair part estimation process according to the embodiment. [Figure 7] FIG. 13 is a diagram illustrating an example of a graphical user interface of a repair procedure display screen according to the embodiment. [Figure 8] FIG. 13 is a diagram illustrating an example of a graphical user interface of a repair procedure details screen according to the embodiment. [Figure 9] 13 is a diagram illustrating an example of a graphical user interface of a completed procedure list transmission screen according to the embodiment. FIG. [Figure 10] 13 is a flowchart illustrating an example of an implementation order estimation process flow according to the embodiment. [Figure 11] FIG. 13 is a diagram illustrating an example of a graphical user interface of a performance order transmission screen according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims. Also, not all of the combinations of features described in the following embodiments are necessarily essential to the solution of the invention.
[0011] The system according to the embodiment includes a first task estimation means, a first task data providing means, a second task data receiving means, and a storage means. The first task estimation means estimates, for each of at least one first task required to resolve an error in a device, a location to be subjected to the first task, the content of the first task, and a priority of the first task, based on error data indicating the content of an error that has occurred in the device and history data related to the device. The first task data providing means provides first task data indicating, for each of at least one first task, a location to be subjected to the first task, the content of the first task, and a priority of the first task. The second task data receiving means receives second task data indicating, for each of at least one second task that is actually performed on the device to resolve an error in the device, a location to be subjected to the second task and the content of the second task. The storage means stores the order in which the at least one second task specified based on the second task data is performed, in order to use the order as feedback for the estimation by the first task estimation means.
[0012] The storage means may also estimate that the at least one second task is performed in an order according to the priority of the first task.
[0013] The first operation estimation means may estimate a part to be subjected to the first operation. In this case, the storage means may estimate that the first operations for the part will be performed in the order of cleaning the part, adjusting the part, and replacing the part.
[0014] The first operation estimation means may estimate a part that is a target of the first operation, and estimate a priority of the first operation for the part.
[0015] In addition, the system according to the embodiment may include a management means for managing the number of parts replaced in the first operation to resolve an error that occurred in the past in association with information identifying the parts.
[0016] The first task data providing means may provide the first task data indicating the location to be the first task and the content of the first task in order of the priority of the first tasks.
[0017] The storage means may estimate an order in which the second tasks are to be performed based on the contents of the second tasks that have already been performed and a context of the second tasks.
[0018] The device may also be an image processing device with a printing function.
[0019] A device error is an error caused by any of the components related to the printing process in the image processing apparatus.
[0020] Specific examples of the above-mentioned system and method will now be described with reference to the drawings.
[0021] First Embodiment <System configuration> 1 is a diagram showing an example of the overall configuration of a system according to an embodiment. The device management system is configured so that a repair location notification server 101, a printer 102, and a PC (Personal Computer) 103 can communicate with each other via a network 100.
[0022] The network 100 is, for example, a so-called communications network realized by a LAN (Local Area Network) such as the Internet, a WAN (Wide Area Network), a telephone line, or the like, and may be any network capable of transmitting and receiving data.
[0023] The repair location notification server 101 receives error information indicating an error that has occurred in the printer 102 from the printer 102, and estimates information on one or more repair parts to resolve the error. Furthermore, the repair location notification server 101 manages the track record of part replacements carried out in the market in response to similar errors that have occurred in the past as market track record, and determines the priority of repair parts to be treated based on this market track record.
[0024] The printer 102 is an example of an image forming device such as a printer or MFP, and has functions such as printing, faxing, copying, and scanning. When the printer 102 detects an error occurring in itself, it transmits error information including device information to the repair point notification server 101. Note that the printer 102 may be configured to include multiple printers 102.
[0025] The PC 103 is an example of an information processing device, and has a predetermined OS (Operating System) (not shown) installed. A browser 331 (described later) is also installed in the PC 103. A request to acquire repair part information for the printer 102 is sent to the repair part notification server 101 via the browser 331, and the repair part information is received from the repair part notification server 101 and displayed in a graphical user interface (GUI).
[0026] Hereinafter, the function of the repair location notification server 101 described in the present invention may be realized by a single server or a single virtual server, or may be realized as a management system by multiple servers or multiple virtual servers. Alternatively, the function of the repair location notification server 101 may be realized by multiple virtual servers being executed on a single server. In that case, the repair location notification server 101 will be included as one server function in a management system constructed on the Internet. The repair location management system may be designed on a cloud infrastructure based on cloud computing technology. In that case, at least a part of the hardware provided in the computer shown in FIG. 2 is used as the hardware resource provided to the virtual server related to the cloud computing technology.
[0027] Fig. 2 is a diagram showing an example of the hardware configuration of a repair location notification server included in the system according to the embodiment. Specifically, Fig. 2 is a block diagram showing the hardware configuration of the repair location notification server 102 shown in Fig. 1.
[0028] The CPU 201 directly or indirectly controls each device (a ROM (Read Only Memory), a RAM (Random Access Memory), etc., described below) connected via an internal bus, and executes a program for implementing the present invention. The ROM 202 stores a BIOS (Basic Input / Output System). The RAM 203 is a direct storage device, and is used as a work area for the CPU 201 and as temporary storage for loading software modules for implementing the present invention.
[0029] The hard disk drive (HDD) 204 is an indirect storage device, and stores an OS, which is basic software, and software modules. The hard disk drive 204 may be replaced with a solid state drive (SSD). The input device 205 is, for example, a keyboard or a pointing device. The output device 206 is, for example, a display. The I / F 207 is connected to the network 100.
[0030] In these hardware devices, after booting, the BIOS is executed by the CPU 201, and the OS is loaded from the hard disk drive 204 to the RAM 203 in an executable manner. The CPU 201 loads various software modules, described below, from the HDD 204 to the RAM 203 as needed in an executable manner in accordance with the operation of the OS. The various software modules are executed and operated by the CPU 201 in cooperation with the above-mentioned devices. The I / F 207 is connected to the Internet 100 or the local network 101, and is controlled by the CPU 201 in accordance with the operation of the OS to realize communication by the above-mentioned communication means.
[0031] 3 is a diagram showing an example of the hardware configuration of a printer included in the system according to the embodiment. The components excluding the print engine 238 are sometimes called a controller that manages the control system of the printer. Each of the hardware components is connected to a system bus 230.
[0032] The CPU 231 executes control of the entire apparatus and centrally controls access to various devices connected to the system bus 230. This control is based on a control program stored in a ROM 232 or a control program and resource data (resource information) stored in an external memory 236 connected via a disk controller (DKC: Disk Controller) 235. The RAM 233 functions as the main memory, work area, etc. of the CPU 231 and is configured so that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown).
[0033] The storage device 240 is an external storage means that functions as a large-capacity memory. The operation panel (operation unit) 239 displays a screen and accepts user operation instructions via the screen. In addition, buttons and a display unit such as a liquid crystal panel are also provided for performing operations such as setting the operation mode of the printer 103, displaying the operation status of the printer 103, and specifying content data to be printed. The network controller 234 is, for example, a network interface card (NIC: Network Interface Controller), and executes data exchange with external devices via the network controller 234.
[0034] The raster controller 237 is a controller that converts print data described in, for example, a page description language (PDL) into image data. The print engine 238 uses a known printing technique to form an image on a sheet based on image data input from the raster controller 237. Suitable implementations include print engines of an electrophotographic type (laser beam type), an inkjet type, a dye sublimation (thermal transfer) type, and the like. The device I / F 241 is a connection I / F with an external device that can be connected via USB or the like.
[0035] <Software configuration> Below, the operation of each server and printer is explained using a configuration diagram of the repair location notification system. These operations are realized by the CPU executing the programs stored in the memory of each device. These operations are realized by the CPU executing the programs stored in the memory of each device. Note that the table schema and data described below are merely examples, and the table schema and various data formats are not limited to these.
[0036] 4 is a diagram showing an example of the software configuration of the system according to the embodiment. The repair point notification server 101 includes an operation information receiving unit 311, an error determining unit 312, an error history managing unit 313, a priority determining unit 314, a market performance managing unit 315, an estimation result managing unit 316, a repair procedure display unit 317, an implementation order estimating unit 318, and an implementation order estimation result managing unit 319.
[0037] The operation information receiving unit 311 receives operation information from the printer 102. The information received by the operation information receiving unit 311 includes error information indicating an error, operation information of the printer 102, and the like.
[0038] When the error determination unit 312 receives error information from the operation information receiving unit 311, it obtains from the error history management unit 313 an error history, which is information about errors that have occurred in the past in the printer in which the error occurred. Furthermore, the error determination unit 312 identifies one or more repair parts for eliminating the error along with the received error information, and transmits the repair parts along with the error information as a determination result to the priority determination unit 314, which will be described later. At this time, if the error determination unit 312 is unable to identify a repair part for some reason, for example, because it is unable to identify an error for a certain error code, it transmits the determination result as "repair part unable to be identified" to the priority determination unit 314, which will be described later, along with the error information. Furthermore, the error determination unit 312 saves the error information received from the printer 102 as error history in the error history management unit 313.
[0039] The error history management unit 313 saves and manages the error information received from the printer 102 as an error history. Table A shows an example of part of the error history managed by the error history management unit 313.
[0040] [Table 1]
[0041] The error history consists of an error ID that uniquely identifies the error, a device ID that uniquely identifies the printer in which the error occurred, a model number that indicates the type of printer, an error code that indicates the type of error that occurred, a counter value that indicates the number of prints when the error occurred, and the date and time the error occurred.
[0042] When the priority determination unit 314 receives the determination result from the error determination unit 312, it obtains from the market performance management unit 315 market performance data that matches the model number and error code of the error information included in the determination result. The priority determination unit 314 ranks the "repair parts and repair procedures that are more likely to resolve the error" in order of the number of part replacements in the market performance data that matches the repair parts included in the determination result, and stores the ranked repair procedures as estimation results in the estimation result management unit 316. Furthermore, the priority determination unit 314 reflects in the estimation that the later the repair procedures in the implementation order stored in the implementation order estimation result management unit 319 described below, the "repair parts and repair procedures more likely to resolve the error" the more likely they are.
[0043] The market performance management unit 315 holds and manages a summary of the number of parts replaced by model number, error code, and part number for all part replacement work performed by service personnel to resolve errors that have occurred in the past. Table 2 shows an example of some of the market performance managed by the market performance management unit 315.
[0044] [Table 2]
[0045] The market performance consists of a model number indicating the type of machine, an error code indicating the type of error that occurred, a part number indicating the part replaced due to the error, and a number of replacements indicating the number of parts replaced. The estimation result management unit 316 saves and manages the estimation results, which are the prioritized repair procedures created by the priority determination unit 314. Table 3 shows some examples of the estimation results managed by the estimation result management unit 316.
[0046] [Table 3]
[0047] The estimation result includes the device ID, the error ID, the part number of the part to be repaired for the error, and a priority indicating the order of the part to be repaired. In this embodiment, the repair priority is determined to be higher in ascending order of the priority value. An example of the method of calculating the priority will be described later in the explanation of the repair part estimation process in FIG. 4.
[0048] When the repair procedure display unit 317 receives a repair procedure acquisition request including a device ID and an error ID from the browser 331 of the PC 103, it acquires an error history whose device ID and error ID match from the error history management unit 313. The repair procedure display unit 317 also acquires an inference result whose device ID and error ID match from the inference result management unit 316, generates a repair procedure display screen, and returns it to the browser 331. The repair procedure display screen displayed by the repair procedure display unit 317 transitions to a repair procedure details screen 600 (described later) when a transition button 506 (described later) is pressed.
[0049] When an implementation order estimation unit 318 receives an implementation order estimation request including part names and procedures from a browser 331 of the PC 103 , the implementation order estimation unit 318 estimates the implementation order from the priority and the context of the work, and stores the result in an implementation order estimation result management unit 319 .
[0050] The implementation order estimation request includes an action list consisting of a model number indicating the model type, a device ID, an error ID indicating the type of error that occurred, a part number indicating the part replaced for the error, the action taken, and a priority order. Table 4 shows an example of a portion of the action list. The priority order is determined by a threshold value. By replacing the numeric priority order with an alphabetical priority order, the user can intuitively understand which action should be taken first.
[0051] [Table 4]
[0052] The implementation order estimation result includes a model number indicating the model type, a device ID, an error ID indicating the type of error that occurred, a part number indicating the part replaced for the error, the action taken, the priority, and an action list consisting of the implementation order. Table 5 shows some examples of the implementation order estimation result.
[0053] [Table 5]
[0054] The printer 102 includes an operation information transmission unit 321, a job execution unit 322, and a control unit 323. The operation information transmission unit 321 transmits to the repair location notification server 101 error information that has occurred in the printer 102 and that is collected by a control unit 323 (described later).
[0055] The job execution unit 322 executes a job input to the printer 102. For example, when a print job is input, the job execution unit 322 executes a print process based on the print job.
[0056] The control unit 323 detects an error that occurs in the printer 102 , collects error information, and transmits the error information to the repair location notification server 101 via the operation information transmission unit 321 .
[0057] <Repair part estimation process> 5 and 6 are flowcharts showing an example of a repair part estimation process according to the embodiment. The flowchart shown in FIG. 5 and the flowchart shown in FIG.
[0058] In step S401, the control unit 323 of the printer 102 detects whether an error has occurred in the printer 102. In step S402, the operation information control unit 321 of the printer 102 sends error information to the repair location notification server 101 upon detecting the occurrence of an error.
[0059] In step S403, the operation information receiving unit of the repair location notification server 101 receives the error information. The transmitted error information includes the error ID, device ID, model number, error code, counter value, and date and time of error occurrence, as shown in the error history in Table 1.
[0060] In this embodiment, an example is described in which the counter value is included in the error information, but, for example, a method may be used in which the counter value is received from the printer 102 as counter information separate from the error information and linked to the error information.
[0061] In step S404, the error determination unit 312 registers the received error information in the error history management unit 313 as an error history.
[0062] In step S405, the error determination unit 312 obtains an error history that matches the device ID included in the received error information. For example, if the device ID included in the error information is "DEV0000001", the records in the first and third rows of Table 1 can be obtained.
[0063] In step S406, the error determination unit 312 uses the error information received from the printer 102 and the error history acquired from the error history management unit 313 to calculate a list of multiple part numbers representing parts that need to be repaired to resolve the error based on a rule base.
[0064] In addition, in step S406, the error determination unit 312 may be unable to identify the part to be repaired. For example, an error in the rule base may occur when there is no rule. In this case, the error determination unit 312 outputs a list of empty part numbers indicating that the determination could not be made.
[0065] In this embodiment, the error determination unit 312 uses a rule-based method based on the received error information and the history of errors that have occurred in the device in the past, but the method for identifying the repair part is not limited to this. For example, estimation using supervised machine learning including deep learning may be performed.
[0066] In step S407, the priority determination unit 314 obtains market exchange records that match the model number and error code of the error information from the market record management unit 315. For example, if the model number and error code included in the error information are "Model-001" and "E009001", respectively, the records in the first to fifth rows of Table 2 can be obtained.
[0067] In step S408, the priority determination unit 314 checks whether the error determination unit 312 was able to identify the part to be repaired. Specifically, if an empty part number list is output in step S406, the priority determination unit 314 determines that the part could not be identified and executes step S410, which will be described later. If the part number list is not empty, the priority determination unit 314 determines that the part could be identified and executes step S409, which will be described later.
[0068] In step S409, priority determination unit 314 obtains the number of replacements that match the part number from the market performance obtained in step S407 for each part number included in the list of part numbers calculated in step S406. Next, in step S409, priority determination unit 314 associates the priority with the part number as "(number of replacements of repair parts / total number of replacements of all parts replaced for errors) x 100". In other words, priority determination unit 314 calculates the priority on a part-by-part basis so that the sum of the priorities of all parts replaced for an error code that occurs in a certain model is 100%.
[0069] In this embodiment, the priority is calculated as the ratio of the number of replacements of the repair part to the total number of replacements of all repair parts to be treated, but the method of calculating the priority is not limited to the method of this embodiment and any method may be used.
[0070] For example, if the list of part numbers is [Part1-111, Part2-222, Part3-333, Part4-444] and the market performance obtained in step S407 is the first to fifth rows of Table 2, the total number of replaced parts will be 900, which is the sum of the number of replacements in the market performance.
[0071] In this case, the priority of part number "Part1-111" is "(510 / 900) x 100 = 51.0". Similarly, the priorities of other part numbers "Part2-222", "Part3-333", and "Part4-444" are "22.8", "9.2", and "2.0", respectively.
[0072] In step S410, the priority determination unit 314 calculates priorities for all market performance records acquired in step S407 in the same manner as in step S409. For example, the case where the market performance acquired in step S407 is the first to fifth rows of Table 2 will be shown. In this case, priorities are calculated for the five part numbers "Part1-111", "Part2-222", "Part3-333", "Part4-444", and "Part5-555" included in the market performance, and the part numbers and priorities are associated with this as an estimated result. Specific examples of priorities will be omitted here.
[0073] In step S411, the priority determination unit 314 registers the part number and priority calculated in step S409 or step S410 together with the device ID and error ID of the error information as estimation results in the estimation result management unit 316. For example, the first to fourth rows of Table 3 are examples of estimation results for the part number and priority calculated in the example of step S409.
[0074] As one example of a method of realizing this, in the management system, it is possible to implement a server (function) that executes the processing of steps S403 to S404 by repair location notification server 101, a server (function) that executes the processing of steps S405 to S406, and a server (function) that executes the processing of steps S407 to S411 separately (by performing asynchronous processing, for example).
[0075] In this way, it is possible to estimate the repair part for an error that has occurred in the printer 102.
[0076] In this embodiment, the part to be repaired is identified (step S406) and the priority is calculated (step S409 or step S410) when error information is received from the printer 102, but this is not limited to the above. For example, a method may be used in which only the part to be repaired is identified when error information is received, and the priority is calculated when a repair procedure acquisition request is received from the browser 331.
[0077] Furthermore, in this embodiment, a method for determining the display order on a part-by-part basis using the number of part replacements has been described. However, the market performance management unit 315 may also store the number of procedures other than part replacements, such as cleaning and adjustment, and display estimated results ranked by procedure unit (replacement, cleaning, and adjustment) based on the priority of the part and procedure.
[0078] <GUI for repair part display screen> 7 is a diagram showing an example of a graphical user interface of a repair procedure display screen according to the embodiment. The repair procedure display unit 317 of the repair part notification server 101, which has accepted a repair procedure acquisition request including a device ID and an error ID from the browser 331 of the PC 103, returns the request to the browser 331, whereby the screen is displayed on the browser 331. A method for generating a repair part display screen by the repair procedure display unit 317 has already been explained, and will not be described here.
[0079] The repair location notification system of the present invention is a system that displays a repair procedure for solving each error that has occurred. The repair procedure display screen 500 includes a repair procedure for the error specified from the browser 331.
[0080] Repair procedure display screen 500 displays the error history and estimation results managed by repair location notification server 101. Device ID 501 displays the device ID of an error history whose error ID matches the error ID specified in the above-mentioned repair procedure acquisition request among the error histories managed by error history management unit 313. Error code 502 displays the error code of an error history whose error ID matches the error ID specified in the above-mentioned repair procedure acquisition request among the error histories managed by error history management unit 313.
[0081] Occurrence date and time 503 displays the occurrence date and time of an error history whose error ID matches the error ID specified in the repair procedure acquisition request among the error histories managed by error history management unit 313.
[0082] Repair parts 504 displays the inference result where the error ID of the repair procedure acquisition request is located, among the inference results managed by the inference result management unit 316. The repair procedure display unit 317 displays the inference results in the repair parts 504 in descending order of priority, making it possible to present to the user which part they should start repairing.
[0083] In this embodiment, the estimation results are simply displayed in order of priority, but for example, when there are multiple estimation results, an icon or a message may be additionally displayed on the repair procedure display screen 500 to indicate that the part is one that needs to be treated for the estimation results whose priority exceeds a certain threshold value.
[0084] Part number 505 displays the part number of the estimation result managed by the estimation result management unit 316. Transition button 506 is a button for transitioning the screen to a repair procedure details screen 600, which will be described later. As described above, repair parts for resolving an error that has occurred in the printer can be displayed in order of the likelihood that they will resolve the error.
[0085] 8 is a diagram showing an example of a graphical user interface of a repair procedure details screen according to the embodiment. The repair procedure details screen 600 is a screen that includes repair procedures for an error specified from the browser 331, and is sorted by parts with high priority and by actions with high priority for each part.
[0086] A response completion button 604 is pressed by a user who has confirmed that the error has been resolved by the action taken, and causes a transition to a completed action list transmission screen shown in FIG. 9, which will be described later.
[0087] In this way, the parts can be displayed in order of priority, and further, the steps with the highest priority for each part can be displayed.
[0088] FIG. 9 is a diagram showing an example of a graphical user interface of a completed action list transmission screen according to an embodiment. The completed action list transmission screen 700 is a screen including repair procedures for an error specified from the browser 331, and is sorted by parts and the actions for the parts in descending order of priority. The means for displaying the repair parts 701, the priority 702, and the repair procedures 703 have already been described, and therefore will not be described again. The completed action specification check box 704 is a check box with which the user specifies the actions that have been performed until the error is resolved. The completed action list transmission button 705 is a button for creating a list of actions described with reference to Table 4 for the parts specified in the completed action specification check box 704, and including the list in a request for estimating the order of execution and transmitting it to the repair point notification server 101.
[0089] As a result, the user can specify the procedures that have been performed by using the check boxes, and send a request for estimating the order of procedures to the repair location notification server 101.
[0090] FIG. 10 is a flowchart showing an example of an implementation order estimation process flow according to the embodiment. In step S801, it is detected whether or not the user has pressed the completed action list send button 705 on the completed action list send screen displayed on the browser 331. In step S802, when the completed action list send screen 700 detects that the send button has been pressed, it sends an implementation order estimation request including the action list described with reference to Table 4 to the repair location notification server 101. In step S803, the implementation order estimation unit 318 of the repair location notification server 101 receives the implementation order estimation request. In step S804, the implementation order estimation unit 318 sorts the action list included in the implementation order estimation request by parts with high priority, and then by the priority of each action. Table 6 shows an example of the state of the action list after sorting in S804.
[0091] [Table 6]
[0092] In step S805, the implementation order estimation unit 318 sorts the action list included in the implementation order estimation request by the order of actions for the same part. The order of actions is the priority order that is assumed to be generally performed in the order of (1) "cleaning", (2) "adjustment", and (3) "replacement" if the actions to be performed on a part are "replacement", "cleaning", and "adjustment". The order of actions may be other than "cleaning", "adjustment", and "replacement". Furthermore, the order of actions may be specified for each part and stored in a database or the like, or may be referenced.
[0093] Table 7 is an example showing the state of the action list after sorting in step S805.
[0094] [Table 7]
[0095] In step S806, the implementation order estimation unit 318 stores the estimated implementation order (Table 5) in the implementation order estimation result management unit 319.
[0096] As an example of a method of realizing this, in the management system, a server (function) that executes the processing of step S803 by repair location notification server 101, a server (function) that executes the processing of steps S804 to S805, and a server (function) that executes the processing of step S806 can be separated and implemented, for example, by performing asynchronous processing.
[0097] As a result, the received treatment list can be sorted according to priority and the order of treatment, and the order of treatment can be estimated.
[0098] Second Embodiment In the first embodiment, since the user cannot confirm whether the execution order estimation result saved in step S806 is correct or not, improvements such as accumulating corrections and using them to improve the estimation accuracy cannot be made. In the second embodiment, an example will be described in which the estimation result is presented to the user and the user receives corrections. Note that the description of the same parts as in the first embodiment will be omitted. Execution order 901 indicates the order in which each procedure was performed.
[0099] 11 is a diagram showing an example of a graphical user interface of the implementation order transmission screen according to the embodiment. The implementation order transmission screen 900 is a screen to which transition occurs after pressing the performed procedure list transmission button 705, and includes the estimation result by the implementation order estimation unit 318, an example of which is shown in Table 5.
[0100] An implementation order 901 indicates the implementation order. Repair parts 902, priority 903, and repair procedures 904 have already been explained, so their explanations are omitted here. An implementation order editing block 905 is an area that can be moved up and down by operating a browser, and when editing the implementation order presented by the user or the repair location notification system, the implementation order can be edited by rearranging the order of the implementation order editing block 905 and moving it to the position of the implementation order 901.
[0101] The Send Action Order button 906 is a button for creating a action list consisting of the action order 901, repair parts 902, priority 903, and repair procedure 904 for each action, and sending the list together with an action order save request to the repair point notification server 101. Table 8 is an example of a action list modified by the user, in which the user has modified the order of cleaning and replacement from the action order presented in the contents of Table 5.
[0102] [Table 8]
[0103] The process of saving the execution order save request has already been explained in S806, so a detailed explanation is omitted here.
[0104] As a result, the repair location notification system can present an estimated order of actions taken by the user until the device error is resolved and receive corrections, which enables feedback to the estimation process and enables more accurate estimation.
[0105] The present invention includes the following inventions that appropriately combine the above-mentioned features.
[0106] (Configuration 1) a first task estimation means for estimating, for each of at least one first task required to resolve an error in a device, an area to be subjected to the first task, the content of the first task, and a priority of the first task, based on error data indicating the content of an error that has occurred in the device and historical data related to the device; a first task data providing means for providing first task data indicating, for each of the at least one first task, the area to be subjected to the first task, the content of the first task, and the priority of the first task; a second task data receiving means for receiving second task data indicating, for each of at least one second task that is actually performed on the device to resolve the error in the device, the area to be subjected to the second task and the content of the second task; and a storage means for storing an order in which the at least one second task identified based on the second task data is performed, for use as feedback for the estimation by the first task estimation means.
[0107] (Configuration 2) The system according to configuration 1, wherein the storage means estimates that at least one of the second tasks will be performed in an order according to the priority of the first tasks.
[0108] (Configuration 3) The system according to configuration 1 or 2, wherein the first operation estimation means estimates a part that is a target of the first operation, and the storage means estimates that the first operation on the part will be performed in the following order: cleaning of the part, adjustment of the part, and replacement of the part.
[0109] (Configuration 4) The system according to any one of configurations 1 to 3, wherein the first operation estimation means estimates a part that is a target of the first operation, and estimates a priority of the first operation for the part.
[0110] (Configuration 5) The system according to any one of configurations 1 to 4, further comprising a management means for managing the number of parts replaced in the first operation to eliminate an error that occurred in the past in association with information identifying the parts.
[0111] (Configuration 6) The system according to any one of configurations 1 to 5, wherein the first task data providing means provides the first task data indicating the area to be subjected to the first task and the content of the first task in order of the priority of the first task.
[0112] (Configuration 7) The system according to any one of configurations 1 to 6, wherein the storage means estimates an order in which the second tasks will be performed based on the contents of the second tasks that have already been performed and a context of a plurality of the second tasks.
[0113] (Configuration 8) The system according to any one of configurations 1 to 7, wherein the device is an image processing device having a printing function.
[0114] (Configuration 9) The system according to configuration 8, wherein the device error is an error caused by any of the components related to the printing process in the image processing device.
[0115] (Method 1) a method for estimating, for each of at least one first task required to resolve an error in a device, a location to be subjected to the first task, the content of the first task, and a priority of the first task based on error data indicating the content of an error occurring in the device and historical data related to the device; providing first task data indicating, for each of the at least one first task, the location to be subjected to the first task, the content of the first task, and the priority of the first task; receiving second task data indicating, for each of at least one second task that is actually performed on the device to resolve the error in the device, the location to be subjected to the second task and the content of the second task; and storing an order in which the at least one second task identified based on the second task data is performed to use it as feedback for the estimation by the first task estimation means.
[0116] <Other embodiments> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a recording medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit for implementing one or more of the functions, such as an ASIC (Application Specific Integrated Circuit).
[0117] The above describes preferred embodiments of the present invention. However, the present invention is not limited to the above-described embodiments. In other words, the present invention includes embodiments in which various modifications have been made based on the gist of the present invention, and these embodiments are not excluded from the scope of the present invention. [Explanation of symbols]
[0118] 101 Repair notification server 102 Printer 312 Error detection unit 314 Priority judgment unit 315 Market Performance Management Department 316 Estimation Results Management Department 317 Repair procedure display unit 318 Implementation Order Estimation Department 319 Implementation Order Estimation Management Department
Claims
1. a first task estimation means for estimating, for each of at least one first task required to resolve an error in a device, a location to be subjected to the first task, a content of the first task, and a priority of the first task, based on error data indicating the content of the error occurring in the device and history data related to the device; a first task data providing means for providing first task data indicating, for each of at least one of the first tasks, a location to be subjected to the first task, a content of the first task, and a priority of the first task; a second task data receiving means for receiving second task data indicating a location to be subjected to the second task and a content of the second task for each of at least one second task that is actually performed on the device in order to resolve an error of the device; A storage means for storing an order in which at least one of the second tasks is performed, the order being determined based on the second task data, for use as feedback for estimation by the first task estimation means; A system comprising:
2. The storage means estimates that at least one of the second tasks is performed in an order according to the priority of the first tasks.
2. The system of claim 1 .
3. The first operation estimation means estimates a part that is a target of the first operation, The storage means estimates that the first work on the part will be performed in the following order: cleaning the part, adjusting the part, and replacing the part.
2. The system of claim 1 .
4. the first operation estimation means estimates a part that is a target of the first operation, and estimates a priority of the first operation for the part; 2. The system of claim 1 .
5. The system further includes a management unit that manages the number of parts replaced in the first operation to eliminate an error that has occurred in the past in association with information identifying the parts. A system according to any one of claims 1 to 4.
6. the first work data providing means provides the first work data indicating a location to be subjected to the first work and a content of the first work in order of a priority of the first work; A system according to any one of claims 1 to 4.
7. The storage means estimates an order in which the second tasks will be performed based on the contents of the second tasks that have already been performed and a context of the second tasks. A system according to any one of claims 1 to 4.
8. The device is an image processing device having a printing function. A system according to any one of claims 1 to 4.
9. the device error is an error caused by any of the components related to the printing process in the image processing device; 9. The system of claim 8.
10. based on error data indicating the content of an error that has occurred in a device and history data relating to the device, estimating, for each of at least one first task required to resolve an error in the device, a location to be subjected to the first task, the content of the first task, and a priority of the first task; providing first task data indicating, for each of at least one of the first tasks, a location to be subjected to the first task, a content of the first task, and a priority of the first task; receiving second operation data indicating a portion to be subjected to the second operation and a content of the second operation for each of at least one second operation that is actually performed on the device in order to resolve the error of the device; and storing an order in which at least one of the second tasks is performed, the order being determined based on the second task data, for use as feedback for estimation by the first task estimation means; A method comprising:
Citation Information
Patent Citations
Work instruction device and work instruction method
JP2021033488A
