Patent Description:
Devices such as image forming devices are designed to print images with coloring materials by mechanical operations such as a motor or clutch, which may require various types of maintenance such as cleaning and replacement of parts. For example, in the case of large-scale image forming devices (such as commercial printers), various maintenance tasks are performed. Some maintenance work is performed manually by a user with respect to the image forming devices, and some maintenance work is performed by an administrator by changing setting values of image forming devices from terminal devices.

A mechanism for an administrator to operate a web browser displayed by a PC (Personal Computer) has been devised in order to perform various settings to image forming devices (see, for example, Patent Document <NUM>). According to such a mechanism, the administrator can change the settings without directly operating the image forming devices.

However, with such a related art mechanism, a user cannot start maintenance from a schedule of tasks related to the maintenance of devices. For example, when an administrator displays a setting screen on the PC for maintenance settings, it is workload for the administrator to check which of multiple setting screens should be opened and operated for each maintenance. In addition, when the administrator performs various maintenance, it is also necessary to manage the work of which maintenance is to be performed and when.

In view of improving the related art mechanism, the present invention is intended to provide an information processing system in which a user can start maintenance from a schedule of tasks related to device maintenance.

[Patent Document <NUM>] <CIT>
<CIT> discloses a job management apparatus for managing a print job for a least one printer.

The invention is defined by the appended independent claims <NUM>, <NUM> and <NUM>. The dependent claims describe advantageous aspects of the invention.

According to an embodiment of the present invention, an information processing system that enables a user to start maintenance from a schedule of tasks related to device maintenance can be provided.

Hereinafter, as an example of an embodiment of the present invention, an information processing method performed by an information processing system, and an information processing system will be described.

According to the present embodiment, an administrator can register various maintenance tasks as "tasks" in a schedule. Tasks include maintenance of the setting change, and the administrator can register tasks for performing the setting change in the image forming device from a task schedule registering screen.

<FIG> illustrates an example of a task. As described above, according to this embodiment, tasks associated with various maintenance modules are registered in DFE (Digital Front End) described later by an administrator. Various maintenance operations are performed in an image forming device. The maintenance operation in <FIG> is "head cap cleaning". At a manageable grain scale, one maintenance task is treated as one task <NUM>. Accordingly, one maintenance task manually performed by a user may be split into multiple tasks.

Further, the task <NUM> includes one or more task components <NUM>. The task component <NUM> is a more detailed maintenance operation to accomplish the task. Then the task <NUM> "Head Cap Cleaning" includes the following task components <NUM>.

The number of task components included in a task is optional. An administrator registers the above-described task in a schedule.

<FIG> is a diagram illustrating an example of a schedule of tasks displayed by the information processing system according to the present embodiment. In <FIG>, a horizontal axis indicates date <NUM> and a vertical axis indicates time <NUM>. An administrator can register a task <NUM> as illustrated in <FIG> in a schedule with specified date and start time.

In a case where an administrator executes registered tasks, the DFE displays the tasks to a terminal device based on the current time. For example, the DFE displays registered tasks according to a display format, such as month, week, and day. The display format in <FIG> is set on a weekly basis. A general user who executes tasks (an administrator may execute tasks) selects a task from the schedule and displays task components of the task. Since the task components each display a screen required for maintenance (including a screen required for setting change) associated with the task components, the general user does not have to select a screen to display the screen required for maintenance.

The administrator can register tasks in the schedule in this manner. The DFE also opens a necessary screen for a task registered at the current time, enabling the general user to proceed with maintenance without searching for a maintenance screen.

Maintenance indicates maintenance, management, and inspection of machinery and structures, or any work required for the maintenance and the like.

Tasks indicate missions or jobs. According to the present embodiment, various types of maintenance registered in the information processing device are referred to as tasks.

A screen relating to execution of a task may, for example, be any screen insofar as a screen enables a user to execute a task, such as the right side of a task execution screen depicted in <FIG> or a task component screen depicted in <FIG>. Execution of a task means that a device performs processing according to the task.

Schedule information associated with a task execution screen means that a user can display a screen from which the user can execute a task from a schedule of the task. Schedules of tasks and screens from which the tasks can be executed may be displayed at the same time. For example, when a task is selected, a screen from which the task can be executed is displayed by the association with the task.

Task-related inputs are information or operations entered by a user when executing a task. The user enters, for example, a setting value or an operation to start executing a task. In addition, a user may enter an operation to enter that task-related work module has been completed or to enter a work module-related memo.

The information on maintenance may be information transmitted by the DFE to the image forming device for maintenance. For example, there are various setting values such as a setting value for improving image quality, a setting value for energy saving, or a setting value for communication setting. Further, a request for operating the image forming device (commands, signals, instructions, and the like) is also information related to maintenance.

When the processing involved is a setting value, the processing according to the maintenance information is to update the setting values, and when the processing involved is a request for an operation, the processing according to the maintenance information is to perform an operation.

<FIG> is a diagram illustrating an example of a system configuration of an information processing system <NUM> according to the present embodiment. The information processing system <NUM> includes a terminal device <NUM>, the DFE <NUM>, and an image forming device <NUM>. A server device <NUM> will be described later.

The terminal device <NUM> and the DFE <NUM> are capable of communicating with each other via a network N. The network includes, for example, a LAN in a facility where the image forming device <NUM> is located, and further includes the Internet where the DFE <NUM> is located on the Internet. The DFE <NUM> and the image forming device <NUM> may be connected on a one-to-one basis via a dedicated line or may be connected via a network. The DFE <NUM> and the image forming device <NUM> may be integrated or detached.

A web browser is operated in the terminal device <NUM>. The web browser accesses a server provided by the DFE <NUM> and displays input operation screens for task creation, schedule registration, and task implementation. The terminal device <NUM> receives operations such as task creation, schedule registration, and task implementation for the input screen from an administrator and requests the DFE <NUM> to execute such operations.

The administrator enters the user ID and password into the terminal device <NUM> to log in to the DFE <NUM>. Since the terminal device <NUM> transmits a user ID and password to the DFE <NUM>, a general user or an administrator is identified in response to authentication by the DFE <NUM> being successful. Displays and items that can be entered differ according to the general user or administrator. An authentication server may authenticate the administrator.

When authentication is successful and the administrator logs in, access right to the task creation, schedule registration, and the task implementation are granted. In the case of general users, access to the task implementation is granted.

The terminal device <NUM> may be, for example, a PC (Personal Computer), a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), a wearable PC (sunglasses, wristwatches, or the like). However, if the application software dedicated to the web browser or DFE <NUM> has a communication function, the application software may operate. For example, a car navigation system, a game machine, a television set, or the like may also be the terminal device <NUM>.

When the web browser is running on the image forming device <NUM>, the administrator can operate the image forming device to request the task creation, schedule registration, and task implementation of the DFE <NUM>.

The DFE <NUM> also displays the input operation screen on the display of its own machine (i.e., the DFE <NUM>) and receives the processing of task creation, schedule registration, and task implementation from the keyboard. In this case, the terminal device <NUM> is not required for the information processing system <NUM>.

The DFE <NUM> is essentially a control device that receives a printing job performed by the image forming device <NUM>, performs image processing (RIP: Raster Image Processor), manages executing progress, and monitors an abnormality. In this embodiment, the DFE <NUM> further receives the processing related to maintenance, and transmits a request for the processing related to maintenance to the image forming device <NUM>. The DFE <NUM> receives the processing of task creation, schedule registration, and task implementation from the terminal device <NUM>. That is, the DFE <NUM> provides the administrator with a user interface (input operation screen) that operates the image forming device <NUM>. The DFE <NUM> includes one or more information processing devices.

The DFE <NUM> generates screen information for a screen displayed by a web browser. Screen information is a program described in HTML, XML, scripting language, and CSS (cascading style sheet). The structure of web pages is mainly specified by HTML, the scripting language defines the behavior of web pages, and CSS identifies the style of web pages. A web application is an application implemented by linking the screen information on the client side with applications and databases on the server side. According to the present embodiment, the terminal device <NUM> and the DFE <NUM> collaborate with each other to execute the web application.

The DFE <NUM> performs processing for registering a task or a task schedule in the database according to a request from the terminal device <NUM> or the image forming device <NUM>, and also performs task implementation processing (changing the device setting, transmitting an operating request, and the like) for the image forming device.

The image forming device <NUM> executes a printing job in response to a request received from the DFE <NUM>. According to the present embodiment, the image forming device <NUM> also receives maintenance and, for example, changes the device setting of the own machine (the image forming device <NUM>) or executes the specified operation according to the task.

The image forming device <NUM> has a function to print an image on a sheet. A system for forming an image includes a laser printer or an ink jet printer. The image forming device <NUM> may have a function of a multifunction printer or MFP (Multi-function Peripheral/Product/Printer). The image forming device <NUM> may be called a printer, a printing device, or the like.

The image forming device <NUM> according to the present embodiment may be a so-called commercial printer. Commercial printers are not used internally by employees to print printed matter, but instead are used for commercial printing. Commercial printing outputs printed materials used in the business activities of ordinary companies and organizations. For example, flyers, pamphlets, posters, catalogs, company brochures, manuals, and the like, may be printed by commercial printers. The image forming device for the office use and the image forming device for commercial use mainly differ in printing speed, image quality, type and size of corresponding sheet, and the like.

The present embodiment can be applied to a device other than the image forming device <NUM>. For example, the device may be a PJ (Projector), an electronic blackboard, a video conference terminal, a digital signage, a HUD (Head Up Display) device, an industrial machine, an imaging device, a sound collector, a medical device, a network home appliance, a game machine, a wearable PC or a desktop PC, and the like.

In the description of <FIG>, the DFE <NUM> has been described as undertaking maintenance related processing (Web app). However, the processing relating to the maintenance may be performed by a server device <NUM>, and for example, the independent server device <NUM> illustrated as (d) in <FIG> may perform the processing relating to the maintenance. In the case illustrated as (d) in <FIG>, the server device <NUM> communicates with the image forming device <NUM> and performs a setting change or a specified operation according to the task.

Further, the image forming device <NUM> may perform the processing related to maintenance. In this case, the image forming device <NUM> has the function of the server device <NUM>.

<FIG> is a diagram illustrating an example of a hardware configuration of the DFE <NUM>. The DFE <NUM> has the same configuration as a computer. The DFE <NUM> includes a CPU <NUM>, a ROM <NUM>, a RAM <NUM>, an HDD/SSD <NUM>, an I/F <NUM>, and an operation unit <NUM>.

The CPU <NUM> uses the RAM <NUM> as a working area and executes a program stored in the ROM <NUM>.

The HDD/SSD <NUM> is used as a storage unit and stores task and schedule information. The information stored in the HDD/SSD <NUM> may be used by the CPU <NUM> when the read program is executed.

The I/F <NUM> is an interface that enables communication with the image forming device <NUM> and the terminal <NUM>.

The operation unit <NUM> has a touch panel and displays the status of the image forming device, the schedule of the task, the contents of the task, and the like on the screen. The operation unit <NUM> also receives inputs from users (administrators and general users) who execute tasks and administrators who create tasks and register schedules.

<FIG> is a schematic diagram illustrating a schematic configuration of the image forming device <NUM> according to the present embodiment. The image forming device <NUM> is, for example, an ink-jet type image forming device, and includes a sheet feeder <NUM>, an image forming unit <NUM>, a dryer <NUM>, a sheet discharger <NUM>, and a control device <NUM>. In the image forming device <NUM>, the image forming unit <NUM> forms an image with ink, which is a liquid for image forming, on sheet P that is a recording material serving as a sheet material fed from the sheet feeder <NUM>. Then, the ink on the sheet is dried in the dryer <NUM>, and the sheet is discharged from the sheet discharger <NUM>.

The sheet feeder <NUM> mainly includes a sheet feed tray <NUM> on which a plurality of sheets P are stacked, a feed device <NUM> on which sheets are fed from the sheet feed tray <NUM> one by one, and a pair of registration rollers <NUM> via which sheets are fed to the image forming unit <NUM>. The sheet feeder <NUM> may be any feeding device with a roller or a roller unit, or any feeding device with an air suction device. The sheet fed from the sheet feed tray <NUM> by the feed device <NUM> is fed to the image forming unit <NUM> by driving the pair of registration rollers <NUM> at a predetermined timing after the front end of the sheet reaches the pair of registration rollers <NUM>. According to the present embodiment, the configuration of the sheet feeder <NUM> is unlimited when the sheet P is fed to the image forming unit <NUM>.

The image forming unit <NUM> mainly includes a receiving cylinder <NUM> for receiving the fed sheet P, a sheet-carrying drum <NUM> for carrying the sheet P on an outer peripheral surface of the sheet-carrying drum <NUM>, an ink ejecting unit <NUM> for ejecting ink toward the sheet P carried by the sheet-carrying drum <NUM>, and a receiving cylinder <NUM> for delivering the sheet P conveyed by the sheet-carrying drum <NUM> to the dryer <NUM>. The front end of the sheet P conveyed from the sheet feeder <NUM> to the image forming unit <NUM> is gripped by a sheet gripper provided on the surface of the receiving cylinder <NUM>, and is conveyed as the surface of the receiving cylinder <NUM> moves. The sheet conveyed by the receiving cylinder <NUM> is passed to the sheet-carrying drum <NUM> at a position facing the sheet-carrying drum <NUM>.

A sheet gripper is also provided on the surface of the sheet-carrying drum <NUM>, and the front end of the sheet is gripped by the sheet gripper. A plurality of suction holes is formed on the surface of the sheet-carrying drum <NUM>, and suction air flow toward the inside of the sheet-carrying drum <NUM> is generated in each suction hole by a suction device <NUM>. The front end of the sheet P passed from the receiving cylinder <NUM> to the sheet-carrying drum <NUM> is gripped by the sheet gripper while the sheet P sucked onto the surface of the sheet-carrying drum <NUM> by the suction air flow is conveyed as the sheet-carrying drum <NUM> moves.

The ink ejecting unit <NUM> according to the present embodiment forms an image by ejecting ink of four colors, namely, C (cyan), M (magenta), Y (yellow), and K (black), and includes individual liquid ejection heads 364C, <NUM>, 364Y, and <NUM> for different inks. If the liquid ejecting heads 364C, <NUM>, 364Y, and <NUM> are for ejecting liquid, the configurations of the liquid ejecting heads 364C, <NUM>, 364Y, and <NUM> are not particularly limited, and any configurations may be employed. If desired, a liquid ejecting head for ejecting special ink, such as white, gold, or silver, or a liquid ejecting head for ejecting a liquid that does not constitute an image, such as a surface coating liquid, may be provided.

The liquid ejecting heads 364C, <NUM>, 364Y, and <NUM> of the ink ejecting unit <NUM> are respectively controlled to ejecting operation by driving signals corresponding to the image information. Respective color inks are discharged from the liquid ejecting heads 364C, <NUM>, 364Y, and <NUM> when the sheet P carried by the sheet-carrying drum <NUM> passes through the area facing the ink ejecting unit <NUM>, and an image corresponding to the image information is formed. In this embodiment, the configuration of the image forming unit <NUM> is not particularly limited and may be any configuration insofar as the image is formed by attaching a liquid to the sheet P.

The dryer <NUM> mainly includes a drying mechanism <NUM> for drying ink adhered to the sheet P by the image forming unit <NUM> and a transport mechanism <NUM> for conveying the sheet P conveyed from the image forming unit <NUM>. The sheet P conveyed from the image forming unit <NUM> is received by the transport mechanism <NUM>, is conveyed to pass through the drying mechanism <NUM>, and is fed to the sheet discharger <NUM>. As the ink passes through the drying mechanism <NUM>, the ink on the sheet P is dried, so that the moisture in the ink evaporates, the ink adheres to the sheet P, and curls of the sheet P are reduced.

The sheet discharger <NUM> mainly includes a discharge tray <NUM> on which a plurality of sheets P are stacked. The sheets P conveyed from the dryer <NUM> are sequentially stacked and retained on the discharge tray <NUM>. According to the present embodiment, the configuration of the sheet discharger <NUM> is not particularly limited insofar as the sheet discharger <NUM> is configured to discharge the sheets P.

The control device <NUM> is an information processing device that controls the image forming device. For example, the control device <NUM> has a CPU, RAM, ROM, SSD (HDD), communication device, or the like. The control device <NUM> communicates with the DFE <NUM> to receive setting values and operating requests according to the task implementation.

<FIG> illustrates functions related to task creation among the functions provided by the DFE <NUM>. Each of the units illustrated in <FIG> is a web application function implemented by a server function in the DFE <NUM> in collaboration with a web browser of the terminal device <NUM>. First, functions for general use regardless of task creation, schedule registration, and task implementation are described. Further, it is assumed that the web browser is operating in the terminal device <NUM>. The processing of the DFE <NUM> may be the same, whether the web browser runs on the DFE <NUM> or the administrator manipulates the DFE <NUM> directly.

As illustrated in <FIG>, the DFE <NUM> includes an input acquiring unit <NUM>, a screen display unit <NUM>, an information updating unit <NUM>, an information acquiring unit <NUM>, and a task-task component-schedule information storage unit <NUM>. These functions provided by the DFE <NUM> are functions or units implemented by the CPU <NUM> executing instructions included in one or more programs installed in the DFE <NUM>.

For example, the input acquiring unit <NUM> acquires information input to a screen displayed by the web browser of the terminal device <NUM> from the terminal device <NUM>.

The screen display unit <NUM> generates screen information according to the operation acquired by the input acquiring unit <NUM>. The screen display unit <NUM> is implemented by the HTML included in the screen information, the JavaScript (registered trademark), and a server program of the DFE <NUM> side, and updates the screen display according to input to the web browser.

The information updating unit <NUM> stores an input result to the web browser and the processing result in the task-task component-schedule information storage unit <NUM>. The information acquiring unit <NUM> acquires requested target information input to the web browser from the task-task component-schedule information storage unit <NUM>.

Next, a task creation function according to the present embodiment will be described with reference to <FIG>.

The input acquiring unit <NUM> acquires (receives) input information input to the terminal device <NUM> by the administrator. When the administrator is operating a web browser displayed by the DFE <NUM>, the administrator acquires the input information input to the operation unit <NUM>.

The task-task component-schedule information storage unit <NUM> stores:.

The task-task component-schedule information storage unit <NUM> further includes information associated the above-described information. Details will be described below.

The estimated task-required time calculator <NUM> of the screen display unit <NUM> calculates an estimated time required to execute a task by summing the estimated task component implementation times in task component information for the task components added to the task acquired by the input acquiring unit <NUM>.

The information updating unit <NUM> updates the task information or the schedule information stored in the task-task component-schedule information storage unit <NUM>.

The information acquiring unit <NUM> acquires the task information, the task component information, or the schedule information stored in the task-task component-schedule information storage unit <NUM> and outputs the obtained information to the screen display unit <NUM>.

The screen display unit <NUM> updates the screen displayed by the terminal device <NUM> by generating screen information. For example, the estimated time required for task implementation is updated.

Next, functions of the terminal device <NUM> will be described. The terminal device <NUM> includes a display controller <NUM>, an operation reception unit <NUM>, and a communication unit <NUM>. These functions of the terminal <NUM> are implemented by a web browser running JavaScript (trademark) included in the screen information and collaborating with the screen display unit <NUM> of the DFE <NUM>.

The display controller <NUM> analyzes screen information and displays a task creation screen, a schedule screen, and a task execution screen to be described later on a display.

The operation reception unit <NUM> receives operations and inputs by an administrator or a general user for the task creation screen, the schedule screen, and the task execution screen.

The communication unit <NUM> mainly communicates with the DFE <NUM> and transmits information entered by an administrator to the DFE <NUM> on the task creation screen, the schedule screen, and the task execution screen.

When the administrator or a general user operates the DFE <NUM>, the DFE <NUM> has a function of the terminal device <NUM>. When the administrator or a general user operates the image forming device <NUM>, the image forming device <NUM> has a function of the terminal device <NUM>.

Next, functions related to the schedule registration function will be described with reference to <FIG> is a functional block diagram illustrating a schedule registration from among the functions provided by the DFE <NUM>. In the description of <FIG>, the difference from <FIG> will be mainly described.

The screen display unit <NUM> of <FIG> includes a scheduled task end time calculator <NUM>, a user-specific mean required time display unit <NUM>, a schedule display updating unit <NUM>, and a task display updating unit <NUM>.

The scheduled task end time calculator <NUM> calculates a scheduled end time from the estimated task-required time of the task information and the scheduled start time of the schedule information.

The user-specific mean required time display unit <NUM> displays the mean time required of the task information on a per user basis. The mean time required of the task information is displayed on a per user basis when an administrator selects a user to perform the task.

The schedule display updating unit <NUM> determines the display format of the schedule according to the schedule display setting (day, week, month) and displays the task in the schedule. When the schedule is changed, the schedule display updating unit <NUM> updates the displayed schedule.

The task display updating unit <NUM> displays the task information. For example, a list of tasks and task components of tasks are displayed. When the task information is updated, the task display updating unit <NUM> updates the displayed tasks.

Next, functions related to the task implementation function will be described with reference to <FIG> is a diagram illustrating functions related to a task implementation function from among the functions provided by the DFE <NUM>. In the description of <FIG>, the difference from <FIG> will be mainly described.

First, the input acquiring unit <NUM> includes a current time acquiring unit <NUM>. The current time acquiring unit <NUM> acquires a current time from the RTC (Real Time Clock) or a time server.

The information updating unit <NUM> includes a task execution result registering unit <NUM>. The task execution result registering unit <NUM> registers a task start time, a task end time, and a task implementation user (a user who has implemented a task) in the schedule information.

The screen display unit <NUM> includes a schedule display updating unit <NUM> and a task display updating unit <NUM>. The schedule display updating unit <NUM> updates the schedule display according to the current time and the schedule display setting. The task display updating unit <NUM> updates the task display according to an implementation status of the task and the current time.

Next, functions of the image forming device <NUM> will be described. The image forming device <NUM> includes a device setting acquiring-updating unit <NUM>, a communication unit <NUM>, a device operation unit <NUM>, and a device setting value information storage unit <NUM>. These functions of the image forming device <NUM> are functions or unit implemented when an instruction included in one or more programs installed in the image forming device <NUM> is executed by the control device <NUM>.

The communication unit <NUM> communicates with the communication unit <NUM> on the DFE <NUM> side. The communication unit <NUM> may be implemented, for example, as a communication interface communicating over TCP/IP, such as a network card, or as a communication program controlling communication over a USB cable.

The device setting value information storage unit <NUM> stores a setting value of the image forming device <NUM>. The device setting acquiring-updating unit <NUM> acquires or updates the setting value of the image forming device <NUM> from the device setting value information storage unit <NUM>. The setting values of the image forming device <NUM> may vary, and may include, for example, a setting value for adjusting the solenoid valve ON timing.

The device operation unit <NUM> performs an operation instructed by the DFE <NUM> on the image forming device <NUM> according to the task. The contents of the operation performed may vary, and may include, for example, printing to detect defective nozzles.

Referring to <FIG>, information stored in the task-task component-schedule information storage unit <NUM> will be described. <FIG> illustrates an example of task component information. The task component information includes the kind of information of a task component has. The task component information includes a task component ID in association with a task component name, module content of the task component, and estimated task component implementation time.

Note that ID stands for Identification, which means identifier or identification information. An ID is a name, code, character string, numeric value, or one or more of these combinations used to uniquely distinguish a particular object from multiple objects.

<FIG> illustrates an example of mean required time information. Mean required time information is the mean time required for each user to execute a task.

<FIG> illustrates an example of task information. Task information is a task component, and the like of each task. Task information corresponds to the task ID, task name, task component ID, task component implementation order, and estimated task-required time.

<FIG> illustrates an example of schedule information. The schedule information has a task registered in the schedule. The schedule information includes a scheduled ID in association with a task to be implemented, a task implementation date, a scheduled start time, a scheduled end time, a scheduled task implementation user, a start time, an end time, a task implementation user, and a repeated period.

<FIG> illustrates an example of implementation status information. The implementation status of a task is recorded per task component in the implementation status information. The implementation status information includes a schedule ID in association with a task component ID of a task in the schedule information. That is, which of task components of the task has been executed so far is registered.

<FIG> illustrates an example of user information. User information is information about a user. User information is associated with a user ID.

The password, affiliation, and the like may be registered in the user information.

Next, a process or an operation flow performed by the information processing system <NUM> will be described with reference to <FIG>.

First, the creation of a task will be described with reference to <FIG> is a diagram illustrating an example of a flowchart representing a procedure or operation by which the DFE <NUM> creates a task according to an operation by an administrator. The terminal device <NUM> communicates with the DFE <NUM>, the image forming device <NUM> communicates with the DFE <NUM>, or an administrator directly operates the DFE <NUM>.

The input acquiring unit <NUM> acquires information that an administrator has made an input to start to create a task (S11).

The information acquiring unit <NUM> acquires task component information from the task-task component-schedule information storage unit <NUM> (S12).

The screen display unit <NUM> uses the task component information to create the screen information of the task creation screen (S13). An example of the task creation screen is illustrated in <FIG>.

Next, the input acquiring unit <NUM> acquires information that an administrator has made an input to add a task component to a task or an input to save a task (S14).

If the input is an input to add the task component to the task (No in S15), step S14 is executed repeatedly. If the input is an input to save the task (Yes in S15), the process proceeds to step S16.

The estimated task-required time calculator <NUM> calculates an estimated task-required time by summing estimated task component implementation times of the task components added to the task (S16).

The information updating unit <NUM> registers the task components and the calculated estimated task-required time in the task information (S17).

The administrator can register a task by combining task components in this manner.

Next, the schedule registration will be described with reference to <FIG> is a diagram illustrating an example of a flowchart representing a procedure or operation in which the DFE <NUM> registers a task in a schedule according to an operation of an administrator. The terminal device <NUM> communicates with the DFE <NUM>, the image forming device <NUM> communicates with the DFE <NUM>, or an administrator directly operates the DFE <NUM>.

The input acquiring unit <NUM> acquires information that the administrator has entered the start of the schedule registration (S21). The input acquiring unit <NUM> receives the selection of a task from the task list of <FIG>, which will be described later.

Accordingly, the information acquiring unit <NUM> acquires task information, schedule information, and mean required time information from the task-task component-schedule information storage unit <NUM> (S22).

First, the schedule display updating unit <NUM> displays a time and date frame according to the display setting (day, week, month) (S23), and the task display updating unit <NUM> displays the created task in association with the time and date frame using the task information (S24). As a result, the task schedule is displayed. <FIG> illustrates an example of a schedule screen. If the display setting is "Day", the current day's implementing task is displayed, if the display setting is "Week", the implementing task in the week including today is displayed, and if the display setting is "Month", the implementing task in the month including today is displayed.

The input acquiring unit <NUM> acquires the task selected by the administrator as a task to be registered in the schedule (S25). For example, the acquired task is a task selected from the task list of <FIG>.

Next, the user-specific mean required time display unit <NUM> displays a user-specific mean time required for the selected task using the mean required time information (S26). The user-specific mean required time display unit <NUM> displays the mean required time of the user ID corresponding to the task ID in association with the user name of the user information. This enables the administrator to select the appropriate scheduled implementation user.

The input acquiring unit <NUM> acquires the scheduled start time, the repeating condition, and the scheduled task implementation user input by the administrator from the terminal device <NUM> (S27).

The scheduled task end time calculator <NUM> adds the mean time required for the task of the scheduled implementation user to the task start schedule time to calculate the scheduled task end time (S28).

Step S29 is executed repeatedly according to the repeating condition.

The information updating unit <NUM> registers a scheduled start time, a scheduled end time, and a scheduled implementation user by the number of repetitions in the schedule information (S29). Duplicate schedules may be registered in the same time range. This is because multiple general users can perform different tasks in parallel in some cases. Alternatively, when duplicate schedules are registered in the same time range, the information updating unit <NUM> may display an error in order to request confirmation from the administrator.

The schedule display updating unit <NUM> updates the schedule display using the schedule information (S30).

The above-described process enables the administrator to register a task in the schedule information.

Next, task implementation will be described with reference to <FIG> and <FIG>. <FIG> and <FIG> illustrates a flowchart representing a procedure or an operation in which the DFE <NUM> causes the image forming device <NUM> to perform a task according to an operation by a general user.

The input acquiring unit <NUM> acquires an input indicating that the general user has opened the task execution screen (S31).

Accordingly, the current time acquiring unit <NUM> acquires the current time from the RTC or the time server (S32).

The information acquiring unit <NUM> acquires the schedule information according to the current time, the task information registered in the schedule, and the task component information associated with the task registered in the schedule from the task-task component-schedule information storage unit <NUM> (S33). The meaning of acquiring such information "according to the current time" indicates acquiring the information in a range of <NUM> day, <NUM> week, <NUM> month, and the like including the current time. The range displayed for a day, a week, or a month depends on the display setting (day, week, month) of the terminal device <NUM>.

The schedule display updating unit <NUM> displays the time and date frame according to the current time and the schedule display setting (day, week, month), and displays the task according to the time and date (S34). The schedule display updating unit <NUM> displays the left side of the task execution screen in <FIG>.

In addition, the task display updating unit <NUM> displays the task information currently scheduled to be executed based on the current time and schedule information (S35). The task currently scheduled to be executed is a most recent task relative to the current time. If the start time is not within a certain period of time, the task does not have to be displayed. The right side of the task execution screen illustrated in <FIG> is displayed. In this way, the task that is likely to be performed relative to the current time is displayed. This reduces the need for general users to select the task. To display task information may mean to display a task, or to display task components of the task.

The input acquiring unit <NUM> acquires information that the general user has entered the task start (S36).

The current time acquiring unit <NUM> acquires the current time (S37).

The task execution result registering unit <NUM> registers the current time as the task start time in the schedule information (S38).

The task display updating unit <NUM> changes the display of the started task component to a display of a currently executed task (S39). The display of a task component is a state of a button (button <NUM>) which represents the implementation status of each task component, as described below. The implementation status of a task component is registered in the implementation status information illustrated in <FIG>. The display of the currently executed task indicates the display of any of the task component that currently is running.

The input acquiring unit <NUM> acquires information that the general user has changed the setting of the image forming device <NUM> based on the task component information registered in the task information or acquires information that the general user has inputted operation execution of the image forming device <NUM> (S40). The task components represent setting items and operation items corresponding to maintenance. Thus, the general user can set and operate a screen corresponding to maintenance without selecting or displaying a screen.

When the task component corresponding to the setting change of the image forming device <NUM> is executed (Yes of S41), the device setting acquiring-updating unit <NUM> updates the setting value of the image forming device <NUM> (S42).

Meanwhile, when the operation execution is performed instead of the task component corresponding to the setting change of the image forming device <NUM> (No in S41), the device operation unit <NUM> operates the image forming device <NUM> to perform a specified operation (S43).

Next, the input acquiring unit <NUM> acquires information that a general user has entered a completion check (S44). Completion check refers to completion of task components. The general user presses a button, for example. The operation reception unit <NUM> of the terminal device <NUM> receives the operation of a general user.

The process returns to step S40 until all task components registered to the task are completed (No in S45).

When all task components registered to the task are completed (Yes in S45), the current time acquiring unit <NUM> acquires the current time (S46).

The task execution result registering unit <NUM> registers the user information and the task end time (current time) of the completed task in the schedule information (S47).

The task display updating unit <NUM> updates the display of the completed task to the end task display (S48).

As described above, since the DFE <NUM> executes the setting change of the image forming device <NUM> as one of the tasks, the user does not need to search for the screen for the setting change.

<FIG> is a diagram illustrating an example of a task creation screen <NUM>. Hereinafter, items of the task creation screen <NUM> will be described.

An SP item <NUM> displays a list of task components for maintenance previously performed by service engineers. <FIG> illustrates an example of the screen when the SP item is clicked. The special item <NUM> is not directly related to the image forming device <NUM> but displays a link to an item used as a task component. Examples include authentication, mail sending, and log acquisition (see <FIG>). An existing task <NUM> is an item for the administrator to register a task already created as a task component. This means that a task is reusable. A free entry item <NUM> is a task component for the user to write precautions. This task component is not subject to implementation (i.e., used as a note) and is handled as a task component having already been executed before the task starts (or button representing implementation status (button <NUM>) is not displayed).

Each task component has an order change button <NUM>. The administrator may press the order change button <NUM> to change the order of implementation of the task components <NUM>.

When the administrator clicks an OK button <NUM>, the task components <NUM> of the task preview <NUM> are registered in the task information.

<FIG> illustrates an example of the SP item screen <NUM> displayed when the SP item <NUM> is pressed. The SP item list <NUM> is displayed on the left side of the SP item screen <NUM>. When the administrator selects one item of the SP item list <NUM>, task components <NUM> corresponding to the selected item of the SP item list <NUM> is displayed on the right side. Each task component <NUM> is associated with a check box <NUM>, allowing the administrator to check any of the check boxes <NUM>. When the administrator clicks an OK button <NUM>, the checked the task components are displayed in task preview <NUM> of <FIG>.

<FIG> is a diagram illustrating an example of a special item list screen <NUM> displayed when a special item <NUM> is pressed. As illustrated in <FIG>, there are general settings, authentication settings, email transmission settings, account manager, printer manager, backup, restore, firmware update, log acquisition, time and date settings, export device information, power manager, limitless discharge, activate timer, paper information, defective nozzle diagnosis and correction, and head cleaning. Each of these can be a task component.

<FIG> is a diagram illustrating an example of a task list screen <NUM>. The task list screen <NUM> displays the task name for each category. These tasks are an administrator's registered tasks (some prearranged tasks). The administrator can select a desired task to be registered in the schedule. The administrator may select a desired task to display the schedule screen <NUM> based on the selection, or a user may display the task list screen <NUM> on the schedule screen <NUM> and select a desired task to be registered.

<FIG> is a diagram illustrating an example of a schedule screen <NUM>. Hereinafter, the items of the schedule screen <NUM> will be described.

When the administrator presses an OK button <NUM>, the same schedule as in the schedule <NUM> is displayed and a newly registered task is displayed in this schedule <NUM>. The scheduled implementation date <NUM> and start time <NUM> may be displayed in the schedule <NUM> in real time.

<FIG> is a diagram illustrating an example of a task execution screen <NUM>. Hereinafter, items of the task execution screen <NUM> will be described.

A task <NUM> ("Paper feeding belt cleaning") that has not been implemented so far is displayed at the top of the task execution screen <NUM>.

The task field <NUM> may also display the one-day task selected in the schedule field <NUM>.

Each task component has a button <NUM>. When the administrator clicks the button <NUM>, the status of the button <NUM> changes as follows (from the input to the task execution screen <NUM> according to the implementation status). For example, the implementation status may be changed from "execute" → "display currently executed task" → "display completed task". Note that upon the button <NUM> being pressed, individual task components or tasks may be completed. When the user presses the button <NUM> while the button <NUM> displays the execution (Execute), for example, a task detail screen as illustrated in <FIG> described later is displayed. Further, when inputting settings, execution, and the like on the detail screen and performing the completion operation and returning to <FIG>, the status of the button <NUM> may change to "Complete". A task (task execution screen <NUM>) may be created only with a task component that does not include a button <NUM>.

<FIG> is a diagram illustrating an example of a task component related to a setting change. <FIG> illustrates an example of a task field <NUM> (a screen corresponding to a task component) of the task execution screen <NUM>. In <FIG>, general users can set a setting value into "Change value" of the item <NUM>, and the terminal device <NUM> can transmit the setting value to the image forming device <NUM> through the DFE <NUM> by pressing the button <NUM>. The device setting acquiring-updating unit <NUM> of the image forming device <NUM> stores the setting value in the device setting value information storage unit <NUM>. The setting value can be changed from the task registered in the schedule in this manner. <FIG> may be a task detail screen displayed when the button <NUM> of <FIG> is pressed.

The task component can display a current setting value to "Current value" of the item <NUM>, which is currently set to the image forming device <NUM>.

The task components that do not change the setting values can be executed by a general user from the schedule. For example, in selecting the special item of "defective nozzle diagnosis and correction", an operating request for "defective nozzle diagnosis and correction" is transmitted to the image forming device <NUM> via the DFE <NUM> by pressing the execution button <NUM>. The device operation unit <NUM> of the image forming device <NUM> performs test printing for detecting a defective nozzle, reads a print result with a scanner, and determines whether a defective nozzle is present. When a defective nozzle is present, correction processing such as cleaning the defective nozzle or excluding the defective nozzle from an ink-ejection operation target is performed. As described above, the image forming device <NUM> can be operated from the task registered in the schedule. In addition, the task field <NUM> of <FIG> or <FIG> may have buttons, check boxes, and the like as a means for inputting that the work of each task component or the entire task has been completed, or may have an additional field capable of inputting a message such as comments input by an operator or worker who carried out the task. An input that does not involve communication from the DFE <NUM> (information processing device) to the image forming device <NUM> (device), such as an input of completion or an input of text, may also be an example of an input related to a task.

As described above, in the information processing system <NUM> according to the present embodiment, the administrator can register a task related to maintenance in a schedule. Further, since the information processing system <NUM> opens the necessary screen for the task registered at the current time, a general user can proceed with maintenance without searching for the screen relating to maintenance.

While the preferred embodiments of the present invention have been described with reference to examples, various modifications and substitutions may be made thereto without departing from the spirit and scope of the invention.

For example, in this embodiment, the terminal device uses a general-purpose web browser, but an application dedicated for the DFE <NUM> may be used.

Further, each of the configuration examples of <FIG>, <FIG>, and <FIG> is divided according to the main functions in order to facilitate understanding of processing performed by the terminal device <NUM>, the DFE <NUM>, and the image forming device <NUM>. The invention according to the present application is not limited by the method of dividing the processing units or by names. The processing of the terminal device <NUM>, the DFE <NUM>, and the image forming device <NUM> can be further divided into more processing units according to the processing contents. Alternatively, one processing unit can be split to include more processing.

Also, the devices described in the examples are merely indicative of one of a plurality of computing environments for carrying out the embodiments disclosed herein. In some embodiments, the DFE <NUM> includes a plurality of computing devices such as a server cluster. The plurality of computing devices is configured to communicate with each other via any type of communication link, including networks, shared memory, and the like, and perform the processes disclosed herein.

Furthermore, the DFE <NUM> can be configured to share various combinations of the disclosed processing steps, such as the flowcharts of <FIG>. For example, a process performed by a predetermined unit may be performed by a plurality of information processing devices having the DFE <NUM>. The DFE <NUM> may also be grouped into a single server device or divided into a plurality of devices.

The functions of the embodiments described above may be implemented by one or more processing circuits. As used herein, a "processing circuit" includes a processor programmed to perform each function by software, such as a processor implemented in electronic circuits, an ASIC (Application Specific Integrated Circuit) designed to perform each function as described above, a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or a conventional circuit module.

The information processing system, the information processing device, the information processing method, the non-transitory computer-readable recording medium, the program, and the device are not limited to the specific embodiments described in the detailed description, and variations and modifications may be made without departing from the spirit and scope of the present invention.

Claim 1:
An information processing device (<NUM>) configured to receive registration of a task related to maintenance of a device (<NUM>), wherein the task comprises a plurality of task components, the task components being maintenance operations for accomplishing the task and representing setting items and operation items, the information processing device (<NUM>) comprising:
a storage unit (<NUM>) configured to store schedule information in which a task related to the maintenance is registered;
a screen display unit (<NUM>) configured to display the schedule information associated with a screen, the screen displaying the task components of the task; and
an input acquiring unit (<NUM>) configured to receive a user input related to a task component, representing a setting item, associated with the screen displayed by the screen display unit (<NUM>) to change a setting of the device (<NUM>).