Image processing apparatus, method, and program
The image processing device simplifies maintenance registration by generating direct access links to reduce manual data entry, enhancing user efficiency in reporting device failures and actions.
Patent Information
- Application Number
- JP2023072676
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-26
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing maintenance management systems require service personnel to manually input detailed information about device failures and maintenance actions, which is burdensome.
An image processing device that generates and outputs access information, such as a QR code or email, to directly link to maintenance registration screens based on device and failure identification, reducing the need for manual data entry.
Reduces the burden on users by allowing them to register maintenance details more efficiently without complex manual input.
Smart Images

Figure 2024157970000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an image processing device, method, and program. [Background technology]
[0002] Conventionally, systems have been developed that manage information and status of equipment (hereinafter referred to as devices) such as digital multifunction peripherals known as MFPs (Multi Function Peripherals). Such systems can manage the occurrence of a failure by having a server receive a failure notification sent from a device in which a failure has occurred. Examples of the occurrence of a failure include the device in which the failure has occurred and the type of failure that has occurred in the device. Such systems are used by service personnel who visit customers as part of the after-sales service of the device sales company and perform maintenance work on the devices, taking appropriate measures at the appropriate time.
[0003] Furthermore, in order to facilitate device maintenance work, a system for streamlining the maintenance work (hereinafter referred to as a repair location notification system) has been developed. The repair location notification system has a function for reporting or registering the contents of the measures taken by a serviceman in response to a malfunction that has occurred to the system, thereby notifying the malfunction location of the device, i.e., the location that needs to be repaired, and thus streamlining the maintenance work.
[0004] Here, a mechanism has been proposed for a serviceman to input the details of the maintenance work into a system as a method for the serviceman to report the details of the maintenance work. Patent Document 1 discloses a maintenance management method in which a serviceman who has visited a device to perform maintenance work inputs the details of the maintenance work into the device itself. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2017-46147 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, the maintenance management method disclosed in Patent Document 1 requires the service person (hereinafter referred to as the user) to input the details of the malfunction (hereinafter referred to as the error) that was the subject of the maintenance work, the details of the measures taken to resolve the malfunction, etc., one by one, which is troublesome for the user.
[0007] SUMMARY OF THE PRESENT EMBODIMENTS In view of the above, an object of the present invention is to provide an image processing apparatus, method, and program that can reduce the burden on a user of the task of registering details related to device maintenance work. [Means for solving the problem]
[0008] In order to solve the above-mentioned problems, the image processing device of the present invention is an image processing device that is managed by a system that manages the results of work performed for maintenance of each of a plurality of image processing devices, and is characterized in having a generation means that generates access information for accessing a screen provided by the system for registering information related to the work for the image processing device as results, based on identification information of the image processing device and either the identification information or information indicating a fault that has occurred in the image processing device, and an output means that outputs the access information. Effect of the Invention
[0009] According to the present invention, it is possible to reduce the burden on the user of registering details related to device maintenance work. [Brief description of the drawings]
[0010] [Figure 1] 1 is a diagram showing an overall configuration of a repair location notification system according to a first embodiment; [Diagram 2] 1 is a diagram illustrating a hardware configuration of a repair location notification system according to a first embodiment. [Diagram 3]FIG. 2 is a diagram showing a software configuration of the repair location notification system according to the first embodiment. [Figure 4] 3 is a diagram showing the configuration of a screen displayed on a graphical user interface of the repair location notification system according to the first embodiment. FIG. [Diagram 5] FIG. 2 is a diagram showing the configuration of a screen displayed on a browser according to the first embodiment. [Figure 6] 5 is a flowchart showing a process executed by the image forming apparatus according to the first embodiment. [Figure 7] 5 is a diagram showing a configuration of a process registration screen presented by the image forming apparatus according to the first embodiment; FIG. [Figure 8] 6 is a flowchart showing a process in which the image forming apparatus according to the first embodiment presents a process registration screen. [Figure 9] 10 is a flowchart showing a process in which an image forming apparatus according to a second embodiment presents a process registration screen. [Figure 10] 13 is a diagram showing the configuration of a process registration screen presented by an image forming apparatus according to a second embodiment. FIG. [Figure 11] 13 is a flowchart showing a process in which an image forming apparatus according to a third embodiment presents a process registration screen. [Figure 12] FIG. 13 is a diagram showing the configuration of a process registration screen presented by an image forming apparatus according to a third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, the embodiments of the present invention will be described with reference to the drawings. Note that the configuration for realizing the present invention is not limited to the configuration described in the embodiment. A part of the configuration described in the embodiment may be omitted or replaced with an equivalent within the scope of obtaining the same effect.
[0012] For example, an embodiment of the present invention is an image processing device that is managed by a system that manages the results of maintenance work performed on at least one image processing device. The image processing device has a generation unit and an output unit.
[0013] The generation means generates access information for accessing a screen provided by the system for registering information regarding work for the image processing device as achievements, based on either the identification information of the image processing device or both the identification information and information indicating a fault that has occurred in the image processing device.
[0014] The output means outputs the access information. For example, the output means converts the access information into a one-dimensional or two-dimensional code and outputs it according to the item selected via the screen generated by the generation means. Alternatively, the output means accesses a screen for registering information on the work for the image processing device as a track record according to the item selected via the screen generated by the generation means, and displays a screen obtained from the access information. Alternatively, the output means writes the access information in an email according to the item selected via the screen generated by the generation means, and sends the email to a specified email address. Below, examples of embodiments for carrying out the present invention will be described.
[0015] First Embodiment In this embodiment, a method will be described in which a URL to an error details screen is generated when an error is resolved, and a means for accessing the screen without performing complicated operations is presented.
[0016] <System configuration> 1 is a diagram showing the overall configuration of a repair location notification system according to the first embodiment. The repair location notification system is configured so that a repair location notification server 101, an image forming device 102, and an information processing device 103 can communicate with each other via a network 100.
[0017] The network 100 is a so-called communications network realized by, for example, a local area network (LAN) such as the Internet, a wide area network (WAN), or a telephone line, and may be any network capable of transmitting and receiving data.
[0018] The repair location notification server 101 receives error information indicating an error that has occurred in the image forming device 102 from the image forming device 102, and estimates information on one or more repair parts to resolve the error. The repair location notification server 101 also manages the track record of part replacements carried out in the market in response to similar errors in the past as market track record, and determines the priority of the repair parts to be treated based on this market track record. Furthermore, the repair location notification server 101 receives information on the treatment carried out on the image forming device 102 from the browser 331 launched by the information processing device 103, and manages the details of the treatment.
[0019] The image forming device 102 is a digital multifunction device called a printer or MFP, and has functions such as printing, facsimile, copying, and scanning. When the image forming device 102 detects an error occurring in itself, it transmits error information including device information to the repair point notification server 101. Note that the image forming device 102 may be configured as a plurality of devices.
[0020] The information processing device 103 is a smartphone, a personal computer (PC), or the like, and has a predetermined operating system (OS) (not shown) installed. The information processing device 103 also has a browser 331 installed. When the information processing device 103 transmits a request to obtain the device status of the image forming device 102 or a request to obtain error details to the repair location notifying server 101, the information processing device 103 receives information corresponding to the request from the repair location notifying server 101 and displays the information in a graphical user interface (GUI) that can be viewed and operated on the browser 331.
[0021] <Hardware configuration> In order to realize the above-mentioned system, each device has the following configuration. Fig. 2 is a diagram showing the hardware configuration of the repair location notification system according to the first embodiment. Fig. 2(A) is a block diagram showing the hardware configuration of the repair location notification server 101 shown in Fig. 1.
[0022] The CPU 201 directly or indirectly controls each device such as the ROM 202 and the RAM 203 connected via an internal bus, and executes a program for implementing the invention according to the first embodiment. The ROM 202 stores a BIOS (Basic Input Output System). The RAM 203 is a direct storage device that is used as a work area for the CPU 201 and as a temporary storage device for loading software modules for implementing the invention according to the first embodiment.
[0023] The HDD 204 is an indirect storage device that stores the OS, which is basic software, and software modules. The HDD 204 may be an indirect storage device such as an 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 an interface for connecting to the network 100.
[0024] In the hardware shown in Fig. 2(A), after booting, the BIOS is executed by the CPU 201, and the OS is loaded from the HDD 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. In addition, 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.
[0025] Fig. 2(B) is a block diagram showing the hardware configuration of the information processing device 103 shown in Fig. 1. The components shown in Fig. 2(B) excluding the print engine 238 are sometimes called a controller that manages the control system of the image forming device 102. Each of the hardware components is connected to a system bus 230.
[0026] The CPU 231 executes control of the entire device 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 stored in an external memory 236 connected via a disk controller (DKC: Disk Controller) 235. The RAM 233 functions as a 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). The storage device 240 is an external storage means that functions as a large-capacity memory. The operation panel 239 displays a screen and accepts instructions input by a user via the screen. The operation panel 239 also has buttons and a display unit such as a liquid crystal panel 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.
[0027] The network controller 234 is, for example, a network interface card (NIC), and executes data exchange with an external device via the network controller 234. The raster controller 237 is, for example, a controller that converts print data described in a page description language (PDL) into image data. The print engine 238 forms an image on a sheet based on image data input from the raster controller 237 using a printing technique. The print engine 238 is preferably, for example, a print engine of an electrophotographic type such as a laser beam type, a dye sublimation type, a thermal transfer type, or the like. The device I / F 241 is an interface that complies with USB (Universal Serial Bus) or the like and can be connected to an external device.
[0028] <Software configuration> Below, the module configuration and operation of the repair location notification server 101 and image forming device 102 will be explained using a configuration diagram of the repair location notification system. These configurations and operations are realized by the CPU executing 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.
[0029] 3 is a diagram showing the software configuration of the repair location notification system according to the first embodiment. First, the software configuration of the repair location notification server 101 will be described. The repair location notification server 101 is made up of an operation information transmitting / receiving unit 311, an error determination unit 312, an error history management unit 313, a priority determination unit 314, a market performance management unit 315, an estimation result management unit 316, a treatment content receiving unit 317, a treatment history management unit 318, a device status display unit 319, and an error details display unit 320.
[0030] The operation information transmitting / receiving unit 311 receives operation information from the image forming apparatus 102. The information received by the operation information transmitting / receiving unit 311 includes error information indicating an error, operation information of the image forming apparatus 102, and the like.
[0031] When the error determination unit 312 receives error information from the operation information transmission / reception unit 311, it acquires the error history of the image forming apparatus in which the error occurred from the error history management unit 313. The error history is information on errors that occurred in the past. Then, the error determination unit 312 identifies one or more repair parts for eliminating the error together with the received error information, and transmits the repair parts together with the error information as a determination result to the priority determination unit 314 described later. At this time, if the error determination unit 312 is unable to identify a repair part for some reason, for example, because an error cannot be identified for a certain error code, it transmits the determination result to the priority determination unit 314 described later together with the error information as "repair part cannot be identified". In addition, the error determination unit 312 saves the error information received from the image forming apparatus 102 as an error history in the error history management unit 313.
[0032] The error history management unit 313 saves and manages error information received from the image forming apparatus 102 as an error history. Table 1 is an example of a portion of the error history managed by the error history management unit 313. Each record in the error history shown in Table 1 consists of an error ID that uniquely identifies the error, a device ID that uniquely identifies the device in which the error occurred, a model number that indicates the type of device, an error code that is the type of error that occurred, a counter value that is the number of prints when the error occurred, and the date and time of the error occurrence.
[0033] [Table 1]
[0034] When the priority determination unit 314 receives the determination result from the error determination unit 312, it obtains market results whose model number and error code match those of the error information included in the determination result from the market result management unit 315. The priority determination unit 314 ranks the "repair parts that are likely to resolve the error" in descending order of the number of part replacements in the market results whose part numbers match those of the repair parts included in the determination result, and stores the ranked repair procedures in the estimation result management unit 316 as estimation results.
[0035] Market performance management unit 315 holds and manages, as market performance, a compilation of the number of parts replaced by model number, error code, and part number for part replacement work performed by a serviceman to resolve errors that have occurred in the past. Table 2 is an example of a portion of the market performance managed by market performance management unit 315. Each record of the market performance shown in Table 2 consists of a model number indicating the model type, an error code which is the type of error that has occurred, a part number which is the part replaced to resolve the error, and a number of replacements which is the number of parts replaced in the past.
[0036] [Table 2]
[0037] The estimation result management unit 316 saves and manages the estimation results, which are repair procedures prioritized by the priority determination unit 314. Table 3 is an example of some of the estimation results managed by the estimation result management unit 316. Each record of the estimation result shown in Table 3 consists of an error ID that uniquely identifies the error, a part number of the repair part for the error, and a priority that indicates the order of the parts to be repaired. In this embodiment, the repair priority is determined in ascending order of the priority number.
[0038] [Table 3]
[0039] The treatment content receiving unit 317 receives treatment information applied to the image forming apparatus 102 from the browser 331 activated by the information processing apparatus 103. The information received by the treatment content receiving unit 317 includes device information capable of identifying the image forming apparatus 102, error information indicating an error occurring in the image forming apparatus 102, treatment contents applied to resolve the error, etc. In addition, the treatment content receiving unit 317 stores the treatment information received from the browser 331 activated by the information processing apparatus 103 in the treatment history management unit 318 as treatment history.
[0040] The action history management unit 318 saves and manages the action information received from the action content receiving unit 317 as an action history. Table 4 is an example of part of the action information managed by the action history management unit 318. Each record of the action content shown in Table 4 consists of an error ID that uniquely identifies the error, a device ID that uniquely identifies the device in which the error occurred, an error code that is the type of error that occurred, the part number on which action was taken to resolve the error, the action content taken to resolve the error, and the date and time when the action was completed (the error was resolved and no longer notified). Note that there are also actions in each record that do not include an error code value.
[0041] [Table 4]
[0042] When the repair location notification server 101 accepts a device status acquisition request including a device ID, the device status display unit 319 acquires operation information from the image forming apparatus 102 that matches the device ID received by the operation information transmission / reception unit 311. The device status display unit 319 also acquires all error histories that match the device ID from the error history management unit 313. The device status display unit 319 also acquires all treatment histories that match the device ID from the treatment history management unit 318. The device status display unit 319 generates a device status confirmation screen that is configured from the acquired operation information, error history, and treatment history. The details of the device status confirmation screen will be described later. The generated device status confirmation screen can be accessed from a browser 331 started by the information processing device 103.
[0043] When the repair location notification server 101 accepts an error details acquisition request including an error ID, the error details display unit 320 acquires the error history with the matching error ID from the error history management unit 313. In addition to this process, the error details display unit 320 also acquires the inference result with the matching error ID from the inference result management unit 316. Furthermore, in addition to these two processes, the error details display unit 320 acquires the treatment history with the matching error ID from the treatment history management unit 318. As described above, an error details screen is generated that is composed of the acquired error history, inference result, and treatment history. The details of the error details screen will be described later. The generated error details screen can be accessed from a browser 331 launched by the information processing device 103.
[0044] Next, a description will be given of the software configuration of the image forming apparatus 102. The image forming apparatus 102 includes an operation information transmitting / receiving unit 321, a job executing unit 322, a control unit 323, and a display unit 324.
[0045] The operation information transmitting / receiving unit 321 transmits error information generated in the image forming apparatus 102, collected by a control unit 323 described later, to the repair point notifying server 101. Furthermore, when an update occurs in the repair point notifying server 101, the operation information transmitting / receiving unit 321 receives the update information from the repair point notifying server 101. An example of an update occurring in the repair point notifying server 101 is when there is a change in the URL for accessing the device status confirmation screen generated by the device status display unit 319.
[0046] The job execution unit 322 executes a job input to the image forming apparatus 102. For example, when a print job is input, the job execution unit 322 executes a print process based on the print job.
[0047] The control unit 323 detects an error that occurs in the image forming apparatus 102 , collects error information, and transmits the error information to the repair location notification server 101 via the operation information transmitting / receiving unit 321 .
[0048] The display unit 324 generates a URL of a screen based on each ID from a device ID based on the device serial number of the image forming device 102 and an error ID based on the error code of the resolved error. In addition, in response to a device ID and an error ID designated by the user, the display unit 324 presents the URL of the screen based on the ID.
[0049] <Screen Configuration> When the repair location notification server 101 accepts a request, the screen generated by the device status display unit 319 and the error details display unit 320 becomes the screen shown in Fig. 4. Fig. 4 is a diagram showing the configuration of a screen displayed on the graphical user interface of the repair location notification system according to the first embodiment.
[0050] 4A is an example of a device status confirmation screen 400. The device status confirmation screen 400 is generated uniquely for each device ID included in the device status acquisition request received by the repair point notification server 101, and is configured from operation information from the image forming apparatus 102 that matches the device ID, the error history of the error history management unit 313, and the treatment history of the treatment history management unit 318.
[0051] Here, the device serial number, device ID, and product name of the operation information are displayed as device information 401. The error ID, error code, and occurrence date and time of the error history are displayed as error history list 402. The error ID, part number, treatment, and treatment date and time of the treatment history are displayed as treatment history list 403. When the user selects specific error history information in error history list 402 on device status confirmation screen 400, the screen transitions to an error details screen for that error ID. Also, when the user presses the add button in treatment history list 403, a record may be added in which any treatment content can be registered by user input.
[0052] 4(B)-1 and (B)-2 are examples of error details screens. A unique error details screen is generated for each error ID included in the error details acquisition request received by the repair location notification server 101, and is composed of the estimation result of the estimation result management unit 316 and the treatment history of the treatment history management unit 318 that match the error ID. Here, FIG. 4(B)-1 is an error details screen 440 unique to the error ID of the error history information 421. Also, FIG. 4(B)-2 is an error details screen 441 unique to the error ID of the error history information 422. Also, of the estimation results, the part number and priority are displayed as treatment target 442 and priority 443, respectively, and the treatment in the treatment history that matches the part number of the estimation result is displayed as treatment content 444.
[0053] FIG. 4(B)-1 shows an error details screen 440 for an error for which there is no processing history matching the error ID included in the error details acquisition request, i.e., an error for which no processing has been applied yet. In this case, the error details screen 440 has a screen configuration for allowing the user to select and register which processing has been applied to which part to be processed. The contents registered on this screen, i.e., the part number and processing content, are sent to the processing content receiving unit 317 as processing information together with the error ID from which this screen was generated and the device ID linked to the error ID. Thereafter, the processing information is newly saved as processing history in the processing history management unit 318 by processing of the processing content receiving unit 317.
[0054] On the other hand, FIG. 4(B)-2 shows an error details screen 441 for an error for which there is a processing history that matches the error ID included in the error details acquisition request, i.e., an error for which processing has already been performed. In this case, the screen is configured to prompt the user to confirm whether the part to be processed and the processing performed are correct, and to correct any errors. The contents corrected on this screen, i.e., the part number and processing contents, are sent to the processing contents receiving unit 317 as processing information together with the error ID that generated this screen and the device ID linked to the error ID. Thereafter, the processing information is overwritten and saved in the processing history of the processing history management unit 318 that matches the error ID by processing of the processing contents receiving unit 317.
[0055] The error history list 402, the action history list 403, and the error details screen 440 displayed on the device status confirmation screen 400 display the latest status in accordance with the contents of the error history management unit 313 and the action history management unit 318, which are updated every time the operation information transmitting / receiving unit 311 and the action content receiving unit 317 receive information. Similarly, the action target 442, the priority 443, and the action content 444 displayed on the error details screen 441 display the latest status in accordance with the contents of the error history management unit 313 and the action history management unit 318, which are updated every time the operation information transmitting / receiving unit 311 and the action content receiving unit 317 receive information.
[0056] Furthermore, when the device status check screen 400 and the error details screens 440 and 441 are displayed in the GUI on the browser 331, they are scaled and only a partial area is displayed according to the window size, and a scroll bar is provided for moving the display area as necessary. FIG. 5 shows examples of the device status check screen 400 and the error details screen 440 displayed in the GUI on the browser 331. FIG. 5 is a diagram showing the configuration of a screen displayed in the browser according to the first embodiment. FIG. 5(A) and FIG. 5(B) are examples of screens in which the screen examples shown in FIG. 4(A)-1 and FIG. 4(B)-1 are scaled and only a partial area is displayed according to the GUI window size, and a scroll bar is provided.
[0057] <Operation of image forming device> 6 is a flowchart showing processing executed by the image forming apparatus according to the first embodiment. This processing is realized by the CPU 231 reading out a controller program recorded in the storage device 240, expanding the program in the RAM 233, and executing the program. This processing starts when the image forming apparatus 102 is powered on.
[0058] In step S501, display unit 324 generates and stores a URL of a device status check screen based on the device ID of image forming apparatus 102. The URL is generated by combining, as a directory name, the protocol name, host name, and domain name of the device status check screen previously stored in storage device 240, and the device ID of image forming apparatus 102. The device ID is generated based on the device serial number of image forming apparatus 102. Thereafter, CPU 231 starts steps S502 to S507 and steps S508 to S511 as separate processes.
[0059] First, the process of steps S502 to S507 will be described. In step S502, the control unit 323 transmits operation information of the image forming apparatus 102 to the repair location notifying server 101 via the operation information transmitting / receiving unit 321.
[0060] In step S503, control unit 323 detects the occurrence of an error in image forming apparatus 102 and determines whether an error has occurred. If control unit 323 determines that an error has occurred (step S503: YES), control unit 323 proceeds to step S504. On the other hand, if control unit 323 determines that an error has not occurred (step S503: NO), control unit 323 proceeds to step S507.
[0061] In step S 504 , the control unit 323 collects information about the error whose occurrence was detected in step S 503 , and transmits the error information to the repair location notifying server 101 via the operation information transmitting / receiving unit 321 .
[0062] In step S505, the control unit 323 determines whether the error detected in step S503 has been resolved. If the control unit 323 determines that the error has been resolved (step S505: YES), the control unit 323 proceeds to step S506. On the other hand, if the control unit 323 determines that the error has not been resolved (step S505: NO), the control unit 323 proceeds to step S507.
[0063] In step S506, the display unit 324 generates a URL for an error details screen based on the error ID of the error determined to have been resolved in step S505. The URL is generated by combining the error ID of the error determined to have been resolved in step S505 as a subdirectory name with the URL of the device status confirmation screen generated and stored in step S501. The error ID is the device ID generated based on the device serial number of the image forming apparatus 102 in the error history managed by the error history management unit 313 of the repair location notification server 101, and the error ID of the error history that matches the error code of the resolved error.
[0064] In step S507, control unit 323 determines whether or not to end the process. When control unit 323 determines to end the process (step S507: YES), it ends the process. An example of such a case is a predetermined action to end the process, such as the user turning off the power of image forming apparatus 102. On the other hand, when control unit 323 determines not to end the process (step S507: NO), it advances the process to step S502 or step S508.
[0065] Next, the process of steps S508 to S511 will be described. In step S508, the display unit 324 accepts a user operation. The user operation is, for example, an operation of displaying functions executable by the image forming apparatus 102, such as copy, scan, and print, on the screen of the operation panel 239, and instructing the user to execute a desired process via the screen. FIG. 7 is a diagram showing the configuration of a process registration screen presented by the image forming apparatus according to the first embodiment. FIG. 7(A) is an example of a screen in a state in which a maintenance worker logs in as a user and a system administrator mode is selected by a mode selection function (not shown). The example screen of FIG. 7(A) displays copy, scan, print, FAX, settings (checking and changing settings of the image forming apparatus 102), and treatment registration as functions executable by the image forming apparatus 102. Here, treatment registration is a function of generating a screen for transmitting treatments performed on the image forming apparatus 102 to the repair location server 101, and executing a process of presenting the screen to the user (hereinafter, referred to as treatment registration screen presentation process). Details of the treatment registration screen presentation process will be described later.
[0066] In step S509, the display unit 324 determines whether or not a user operation has been accepted in step S508. If the display unit 324 determines that a user operation has been accepted in step S508 (step S509: YES), the process proceeds to step S510. On the other hand, if the display unit 324 determines that a user operation has not been accepted in step S508 (step S509: NO), the process proceeds to step S511.
[0067] In step S510, the job execution unit 322 executes the process instructed by the user in step S508.
[0068] In step S511, the display unit 324 determines whether or not to end the process. When it is determined that the process is to be ended (step S511: YES), the display unit 324 ends the process. An example of such a case is a predetermined operation to end the process, such as the user turning off the power of the image forming apparatus 102. On the other hand, the display unit 324 advances the process to step S508.
[0069] <Treatment registration screen presentation process> Next, a process of presenting a process registration screen by the image forming apparatus 102 will be described. Fig. 8 is a flowchart showing a process of presenting a process registration screen by the image forming apparatus according to the first embodiment. This process starts when the user instructs execution of a process registration function via the operation panel 239 of the image forming apparatus 102 in step S507 in the operation process flowchart of the image forming apparatus 102 shown in Fig. 6.
[0070] In step S601, the display unit 324 acquires the URL of the device status check screen generated in step S501 and the URL of the error details screen generated in step S506 in the operation processing flowchart of the image forming apparatus 102 shown in Fig. 6. Note that one device-specific URL for the device status check screen can be acquired, and as many URLs for the error details screen as the number of resolved errors can be acquired.
[0071] In step S602, the display unit 324 generates a screen on the operation panel 239 that displays a list of device IDs, IDs of resolved errors, and resolution dates and times, and allows the user to select a desired item via the screen. An example of the screen displayed by the operation panel 239 is shown in Fig. 7(B). Fig. 7(B) is an example of a screen that displays a list of device IDs, IDs of resolved errors, and resolution dates and times, any of which can be selected. Note that an error code or error name may be displayed together with the error ID.
[0072] In step S603, the display unit 324 accepts a user operation on the screen generated in step S602. Note that the user operation is, for example, a selection of any item from the list of the displayed device IDs and resolved error IDs, an instruction to execute another function, etc.
[0073] In step S604, the display unit 324 accepts the user's operation in step S603 and determines whether any item has been selected from the list of device IDs and resolved error IDs. If the display unit 324 determines that any item has been selected (step S604: YES), the process proceeds to step S605. On the other hand, if the display unit 324 determines that no item has been selected (step S604: NO), the process proceeds to step S606.
[0074] In step S605, the display unit 324 displays a URL corresponding to the item selected by the user in step S603 on the screen of the operation panel 239. If the selected item is a device ID, the display unit 324 displays the URL of a device status confirmation screen. If the selected item is an error ID, the display unit 324 displays the URL of the error details screen. Examples of screens displayed by the operation panel 239 are shown in Figs. 7(C) and 7(D). Fig. 7(C) is an example of a screen displaying the URL of a device status confirmation screen. Fig. 7(D) is an example of a screen displaying the URL of an error details screen. As shown in Figs. 7(C) and 7(D), it is preferable to convert the URL into a QR code (registered trademark) by a known technology and display it. By converting the URL into a QR code, the URL can be read by a camera (not shown) mounted on an information processing device 103 such as a smartphone carried by the user, and the contents of the action can be registered in the browser 331 of the information processing device 103.
[0075] In step S606, the display unit 324 determines whether or not to end the treatment registration screen presentation process. When the display unit 324 determines that the treatment registration screen presentation process is to be ended (step S606: YES), the display unit 324 ends the process. An example of such a case is when the user performs a predetermined operation to end the process, such as an instruction to execute another function. On the other hand, when the display unit 324 determines that the treatment registration screen presentation process is not to be ended (step S606: NO), the process proceeds to step S603.
[0076] As described above in the first embodiment, when an error is resolved, the image forming apparatus 102 generates a URL to an error details screen on which the error details are displayed and the taken action details can be registered. The image forming apparatus 102 also converts the generated URL into a QR code, displays it on the screen of the operation panel 239, and presents it to the user. When the user reads the QR code via the information device 103 that the user carries, the user can register the action details in the browser 331 of the information processing device 103. This allows the user to register the action details taken for the error without having to perform the cumbersome operation of typing in the error details one by one.
[0077] Second Embodiment In this embodiment, a method for accessing an error details screen on an image forming apparatus without performing complicated operations will be described. The system configuration of the second embodiment is the same as that of the first embodiment except for the characteristic parts. Therefore, the same components are denoted by the same reference numerals and detailed descriptions thereof will be omitted.
[0078] <Treatment registration screen presentation process> A process for presenting a process registration screen by the image forming apparatus 102 in this embodiment will be described. Fig. 9 is a flowchart showing a process for presenting a process registration screen by the image forming apparatus according to the second embodiment. This process starts when the user instructs execution of a process registration function via the operation panel 239 of the image forming apparatus 102 in step S507 in the operation process flowchart of the image forming apparatus 102 shown in Fig. 6.
[0079] The processes from step S601 to step S604 are the same as the process steps with the same reference numerals in the flowchart of Fig. 8. Here, in step S604, the display unit 324 accepts the user's operation in step S603 and determines whether or not any item has been selected from the list of device IDs and resolved error IDs. If the display unit 324 determines that any item has been selected (step S604: YES), the process proceeds to step S801. On the other hand, if the display unit 324 determines that no item has been selected (step S604: NO), the process proceeds to step S606.
[0080] In step S801, the display unit 324 starts a browser (not shown) installed in the image forming apparatus 102, and accesses the URL corresponding to the item selected by the user in step S603.
[0081] In step S802, the display unit 324 displays the display screen of the browser started in step S801 on the operation panel 239 and accepts a user operation. If the item selected in step S604 is a device ID, the operation panel 239 displays a device status confirmation screen. If the item selected is an error ID, the operation panel 239 displays the error details screen. FIG. 10 is a diagram showing the configuration of a process registration screen presented by the image forming apparatus according to the second embodiment. FIGS. 9C and 9D show examples of screens displayed by the operation panel 239. Both of FIGS. 10B and 10C are examples of screens in a state in which a browser (not shown) installed in the image forming apparatus 102 is started. FIG. 10B is an example of a screen that displays a device status confirmation screen on the browser, and has the same configuration as the device status confirmation screen 400 shown in FIG. 4A. FIG. 10D is an example of a screen that displays an error details screen on the browser, and has a screen configuration that allows the user to select which action has been taken on which part to be treated and to register it. As shown in FIGS. 10C and 10D, the contents of the treatment can be registered via a screen displayed on a browser (not shown) installed in the image forming apparatus 102.
[0082] In step S803, the display unit 324 determines whether or not to close the browser launched in step S802. If the display unit 324 determines that the browser launched in step S802 is to be closed (step S802: YES), the display unit 324 ends the display of the browser and proceeds to step S603. An example of such a case is when the user performs a predetermined operation to close the browser. On the other hand, if the display unit 324 determines that the browser launched in step S802 is not to be closed (step S802: NO), the process proceeds to step S802.
[0083] The process in step S606 is the same as the process step having the same reference numeral in the flowchart of FIG.
[0084] As described above in the second embodiment, when an error is resolved, the image forming apparatus 102 generates a URL to an error details screen on which the error content is displayed and the implemented action content can be registered. The generated URL is also displayed on the screen of the operation panel 239 and presented to the user. When the user accesses the URL via the operation panel 239, the action content can be registered on the browser of the image forming apparatus 102. This allows the user to register the action content implemented for the error via the image forming apparatus 102, even in a situation where the information device 103 cannot be used, without having to perform the cumbersome operation of typing in the error content one by one via the information device 103.
[0085] <Third embodiment> In this embodiment, a method of notifying the URL of the error details screen by email will be described. The configuration of the system in the third embodiment is the same as that in the first embodiment except for the characteristic parts. Therefore, the same components are denoted by the same reference numerals and detailed description thereof will be omitted.
[0086] <Treatment registration screen presentation process> A process for presenting a process registration screen by the image forming apparatus 102 in this embodiment will be described. Fig. 11 is a flowchart showing a process for presenting a process registration screen by the image forming apparatus according to the third embodiment. This process starts when the user instructs execution of a process registration function via the operation panel 239 of the image forming apparatus 102 in step S507 in the operation process flowchart of the image forming apparatus 102 shown in Fig. 6.
[0087] The process of S601 is the same as the process step having the same reference numeral in the flowchart of FIG.
[0088] In step S1001, the display unit 324 generates a screen on the operation panel 239, which displays a list of device IDs, IDs of resolved errors, and resolution dates and times, and allows the user to select and confirm multiple desired items via the screen. FIG. 12 is a diagram showing the configuration of a process registration screen presented by an image forming apparatus according to the third embodiment. FIGS. 12(B) and 12(C) show examples of a screen displayed by the operation panel 239. FIG. 12(B) is an example of a screen displaying a list of device IDs, IDs of resolved errors, and resolution dates and times, from which multiple items can be selected. FIG. 12(C) is an example of a screen on which a confirmation instruction can be issued by scrolling down the example screen shown in FIG. 12(B). Note that an error code or an error name may be displayed together with the error ID.
[0089] In step S1002, the display unit 324 accepts a user operation on the screen generated in step S1001. Note that the user operation is, for example, a selection of one or more items from the list of the displayed device IDs and resolved error IDs, a decision instruction by pressing the decision button, an instruction to execute another function, etc.
[0090] In step S1003, the display unit 324 accepts the user's operation in step S1002, and determines whether or not one or more items have been selected from the list of device IDs and resolved error IDs and a confirmation instruction has been given. If the display unit 324 determines that one or more items have been selected from the list of device IDs and resolved error IDs and a confirmation instruction has been given (step S1003: YES), the process proceeds to step S1004. On the other hand, if the display unit 324 determines that one or more items have not been selected from the list of device IDs and resolved error IDs and a confirmation instruction has not been given (step S1003: NO), the process proceeds to step S606.
[0091] In step S1004, the display unit 324 generates a screen on which an email address can be input or an email address can be retrieved from a preregistered address book, and displays the screen on the operation panel 239 to accept user operations. An example of the screen displayed by the operation panel 239 is shown in FIG. 12(D).
[0092] In step S1005, the display unit 324 determines whether or not the user has input or called an email address and issued a confirmation instruction via the screen displayed in step S1004. If the display unit 324 determines that the user has input or called an email address via the screen displayed in step S1004 and issued a confirmation instruction (step S1005: YES), the process proceeds to step S1006. On the other hand, if the display unit 324 determines that the user has input or called an email address via the screen displayed in step S1004 and has not issued a confirmation instruction (step S: NO), the process proceeds to step S1004.
[0093] In step S1006, the display unit 324 sends an email to the email address input or called in step S1004. In the body of the email, the URL of the device status confirmation screen corresponding to the device ID selected by the user in step S1002 and the URL of the error details screen corresponding to the error ID are described. After the email is sent, the display unit 324 generates a screen notifying the completion of the email transmission (hereinafter, referred to as an email transmission completion notification screen) and displays it on the operation panel 239. An example of the email transmission completion notification screen displayed by the operation panel 239 after the email is sent is shown in FIG. 12(e), and an example of the email to be sent is shown in FIG. 12(f). FIG. 12(f) is an example of an email in which the URL of the screen corresponding to the selection items shown in FIG. 12(B) and FIG. 12(C) is described in the body, and the email address shown in FIG. 12(D) is set as the destination. The display unit 324 sends the mail, generates a mail sending completion notification screen, displays it on the operation panel 239 for a predetermined period of time, and then the process proceeds to step S1002.
[0094] The process in step S606 is the same as the process step having the same reference numeral in the flowchart of FIG.
[0095] As described above in the third embodiment, when an error is resolved, the image forming apparatus 102 generates a URL to an error details screen on which the error content is displayed and the action taken can be registered. The generated URL is then sent to the user by email. This allows the user to register the action taken for the error by accessing the URL later in the email, even if the user is unable to register the action immediately after the maintenance work, without having to perform the cumbersome operation of typing in the error content one by one.
[0096] The present invention includes the following inventions that appropriately combine the above-mentioned features.
[0097] (Configuration 1) An image processing device is managed by a system that manages the results of work performed for maintenance of each of a plurality of image processing devices, the image processing device being characterized in having: a generation means for generating access information for accessing a screen provided by the system for registering information regarding the work for the image processing device as results, based on either identification information of the image processing device or the identification information and information indicating a fault that has occurred in the image processing device; and an output means for outputting the access information.
[0098] (Configuration 2) The image processing device according to configuration 1, wherein the output means converts the access information into a one-dimensional or two-dimensional code in accordance with an item selected via the screen generated by the generation means and outputs the code.
[0099] (Configuration 3) The image processing device according to configuration 1 or 2, characterized in that the output means accesses a screen for registering information regarding the work for the image processing device as a track record in accordance with an item selected via the screen generated by the generation means, and displays a screen obtained from the access information.
[0100] (Configuration 4) The image processing device according to any one of configurations 1 to 3, wherein the output means includes the access information in an email in accordance with an item selected via the screen generated by the generation means, and sends the email to a specified email address.
[0101] (Method 1) A method for controlling an image processing device that is managed by a system that manages the results of work performed for maintenance of each of a plurality of image processing devices, the method comprising: generating access information for accessing a screen provided by the system for registering information regarding the work for the image processing device as results, based on either identification information of the image processing device or the identification information and information indicating a fault that has occurred in the image processing device; and outputting the access information.
[0102] (Program 1) A program for controlling an image processing device that is managed by a system that manages the results of work performed for maintenance of each of a plurality of image processing devices, the program generating access information for accessing a screen provided by the system for registering information regarding the work for the image processing device as results based on either identification information of the image processing device or the identification information and information indicating a fault that has occurred in the image processing device, and outputting the access information.
[0103] <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).
[0104] 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]
[0105] 101 Repair location notification server 102 Image forming device 313 Error History Management Unit 318 Treatment History Management Department 319 Device Status Display 320 Error details display section 324 Display section 400 Device status check screen 440 Error details screen for errors that have not yet been dealt with 441 Error details screen for errors that have already been dealt with
Claims
1. An image processing device that is managed by a system that manages records of maintenance work performed on each of a plurality of image processing devices, a generating means for generating access information for accessing a screen provided by the system for registering information related to the work for the image processing device as a record based on one of identification information of the image processing device and the identification information and information indicating a fault occurring in the image processing device; an output means for outputting the access information; 13. An image processing device comprising:
2. the output means converts the access information into a one-dimensional or two-dimensional code in response to an item selected via the screen generated by the generation means and outputs the code.
2. The image processing device according to claim 1,
3. the output means accesses a screen for registering information on the work for the image processing device as a record in accordance with an item selected via the screen generated by the generation means, and displays a screen obtained from the access information.
2. The image processing device according to claim 1,
4. the output means writes the access information in an email in accordance with an item selected via the screen generated by the generation means, and transmits the email to a specified email address.
2. The image processing device according to claim 1,
5. 1. A method for controlling an image processing device that is a managed object of a system that manages records of maintenance work performed on each of a plurality of image processing devices, comprising: generating access information for accessing a screen provided by the system for registering information related to the work for the image processing device as a record based on one of identification information of the image processing device and the identification information and information indicating a fault occurring in the image processing device; outputting the access information; A method comprising:
6. A program for controlling an image processing device that is a management target of a system for managing records of maintenance work performed on each of a plurality of image processing devices, comprising: generating access information for accessing a screen provided by the system for registering information related to the work for the image processing device as a record based on one of identification information of the image processing device and the identification information and information indicating a fault occurring in the image processing device; outputting the access information; A program characterized by:
Citation Information
Patent Citations
Maintenance management system and maintenance management method
JP2017046147A
Cited By
Agricultural harvesters with improved steering structure
KR1020240131587A
