Color verification system, method for controlling the color verification system, color verification server, and program

Abstract

Timely notification of work delays. [Solution] A color verification system for managing color verification tasks includes: management means for dividing and managing color verification tasks into two or more phases, including a first phase and a second phase; linking means for linking the first phase to a first work time and the second phase to a second work time; and notification means for notifying the user that the work in the first phase is incomplete if the completion event of the first phase is not detected and the first work time has elapsed.

Description

Technical Field

[0001] The present disclosure relates to a color verification system, a control method for the color verification system, a color verification server, and a program.

Background Art

[0002] In the field of commercial printing for posters, pamphlets, etc., it is important to be able to reproduce the color tone on the printed data highly reproducibly on the printing medium (hereinafter referred to as "color reproducibility"). Conventionally, a color verification system for verifying and managing the color reproducibility of printer devices has been widely known and is also called a Color Management System.

[0003] By adding a schedule management function to the color verification system, it is possible to assist the operator in regularly performing color verification. Although not limited to color verification systems, various technologies have been introduced in conventional schedule management systems to efficiently execute work schedules (hereinafter referred to as "tasks"). For example, Patent Document 1 discloses a technique in which a work management device notifies a notification destination with a message when it determines that work stagnation has occurred in a task.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The work management device according to Patent Document 1 executes a process of determining whether work stagnation has occurred only when a predetermined time such as the end time has arrived or when there is a request from the administrator, and notifies the notification destination with a message.

[0006] There is a need for technology that can notify users of work delays in a timely manner. [Means for solving the problem]

[0007] The color verification system relating to this disclosure is a color verification system for managing a color verification task, and is characterized by comprising: management means for dividing the color verification task into two or more phases including a first phase and a second phase; linking means for linking the first phase to a first work time and the second phase to a second work time; and notification means for notifying the user that the work of the first phase is incomplete if the completion event of the first phase is not detected and the first work time has elapsed. [Effects of the Invention]

[0008] The technology disclosed herein makes it possible to notify of work delays in a timely manner. [Brief explanation of the drawing]

[0009] [Figure 1] Hardware configuration diagram of the color verification system. [Figure 2] Software configuration diagram of the color verification system. [Figure 3] Conceptual diagram of the preparation time for printing the color verification chart and the time required for executing the color verification process. [Figure 4] Notification destination settings screen for various settings applications. [Figure 5] A flowchart showing the notification destination settings screen for various configuration applications. [Figure 6] A flowchart illustrating the process of saving notification destination settings in various configuration applications. [Figure 7] A flowchart of the main loop of a web server. [Figure 8] A diagram showing the data structure of the notification destination list. [Figure 9] This diagram shows the screen of the color verification settings application 291. [Figure 10]Flowchart at the time of screen display of the color verification setting application 291. [Figure 11] Flowchart regarding the color verification setting process. [Figure 12] Diagram showing the data structure of the color verification setting list. [Figure 13] State transition diagram of the color verification task. [Figure 14] Flowchart at the time of saving settings of the color verification setting application 291. [Figure 15] Flowchart of the main loop of the Scheduler Engine. [Figure 16] Flowchart of the color verification preparation start timer signal processing. [Figure 17] Flowchart of the color verification preparation delay detection timer signal processing. [Figure 18] Diagram showing the setting screen of the color measurement application 292. [Figure 19] Diagram showing the color measurement screen of the color measurement application 292. [Figure 20] Flowchart at the time of starting color measurement on the color measurement screen of the color measurement application. [[ID=3l]] [Figure 21] Flowchart at the time of starting color measurement on the color measurement screen of the color measurement application. [Figure 22] Flowchart at the time of completion of color measurement on the color measurement screen of the color measurement application. [Figure 23] Diagram showing examples of various warnings displayed by the device-side UI and warning lights. [Figure 24] Diagram showing an example of superimposing various warnings on the color verification setting application screen. [Figure 25] Diagram showing an example of displaying the state of the phase on the application switching button.

Embodiments for Carrying Out the Invention

[0010] The embodiments of this disclosure will be described below with reference to the attached drawings. The embodiments described below are not limiting to this disclosure, and not all combinations of features described in the embodiments are necessarily essential to the solutions of this disclosure. The same components will be denoted by the same reference numerals. Furthermore, each step in the flowchart will be indicated by a reference numeral beginning with "S".

[0011] [First Embodiment] Figure 1 is a hardware configuration diagram of the color verification system. The color verification system includes a color verification server 101, a database service 102, an account management service 103, and a device management service 104, all of which operate on a cloud computing platform 100.

[0012] The color verification server 101 is a virtual computer (virtual PC) including a CPU 111, RAM 112, Storage 113, and Network Interface 114. The CPU 111 is a central processing unit for executing programs deployed on RAM 112. RAM 112 is a storage area for temporarily storing programs executed by the CPU 111 and data used by those programs. Storage 113 is a storage area for storing programs executed by the CPU 111 and data used by those programs. Storage 113 may be a hard disk drive (HDD) or a solid-state drive (SSD), etc. Network Interface 114 is an interface for communicating with external services or client PCs, etc., of the color verification server 101. For example, it may have multiple Network Interfaces, such as one for connecting to a cloud computing platform and another for connecting to the internet.

[0013] The hardware constituting the color verification server 101 is assumed to be virtualized resources provided from the cloud computing platform 100, and does not need to have a one-to-one correspondence with the hardware. Furthermore, this embodiment is described on the premise that it operates on a cloud environment. However, in order to suitably implement this disclosure, the color verification server 101 does not necessarily have to reside on the cloud computing platform 100. For example, it may be implemented on a dedicated server equipped with a physical CPU and RAM. These hardware configurations can be changed depending on the purpose when implementing this disclosure.

[0014] The Database service 102 is a service for managing the database used by the color verification server 101. In this embodiment, the data managed by the Database service 102 is assumed to be data in JSON format used in NoSQL technology. In implementing this disclosure, relational database technology or the like may be used instead of NoSQL technology. The database (collection) managed by the Database service 102 will be explained in detail in Figure 2.

[0015] The account management service 103 is a service that provides various information about user accounts and notifies user accounts in response to requests from the color verification server 101. In other words, the account management service 103 functions as a notification unit that notifies users of information. For example, if the completion event of the preceding phase is not detected and the work time for the preceding phase has elapsed, the Scheduler Engine 260, described later, receives a signal indicating that a work delay has occurred. The Scheduler Engine 260 requests the account management service 103 to notify the user that a work delay has occurred in the preceding phase. Upon receiving this request from the Scheduler Engine 260, the account management service 103 notifies the user that a work delay has occurred in the preceding phase by sending an email to the user or displaying it on the display 142. Specifically, the account management service 103 can send an email to the Mail Server 124 via the Internet 120 based on the information of the specified user account. Alternatively, the account management service 103 can send a short message to the mobile phone 123 via the Internet 120 and the mobile phone carrier's system 122. In addition, the account management service 103 may send notifications to user accounts via services other than the color verification service, such as a bulletin board service. Furthermore, the account management service 103 may display the notification information on the display 142, the UI 156 of the printer 150, or the UI 161 of the controller 160.

[0016] The device management service 104 is a service for performing input / output control on printer devices and controllers. Specifically, the device management service 104 can obtain various statuses related to printers 150 and 170 from controllers 151 and 160 via the Internet 120 and Gateway 121. In addition, in response to requests from the color verification server 101, the device management service 104 can request controllers 151 and 160 to perform controls such as test chart printing and color adjustment.

[0017] Internet 120 represents the concept of an internet connection. Mobile phone operator 122 represents the concept of an internet connection service managed by a mobile phone operator. Mobile phone 123 represents a mobile device managed by mobile phone operator 122 and contracted with general consumers. The concept of a mobile device also includes concepts such as mobile phones, smartphones, and tablet devices. Here, a mobile phone operator is given as an example of an internet connection service provider for ease of understanding, but this is not the only example for suitably implementing this disclosure. Specifically, if an IoT operator provides an internet connection service using a satellite link service other than a mobile phone, the IoT device can connect to the color verification system via the account management service 103 of this disclosure. The above IoT devices include head-mounted displays, in-vehicle systems, and other devices.

[0018] Gateway Server 121 is a server that connects the Internet 120 (the internet) to Intranet 130. Mail Server 124 is a server that manages email exchanged both inside and outside Internet 120 and Intranet 130. Intranet 130 is an intranet connected to Internet 120 by Gateway Server 121. Color verification client 131, controller 151, and controller 160 are interconnected on Intranet 130.

[0019] The color verification client 131 is a client PC used by the operator performing color verification. The color verification client 131 includes a CPU 132, RAM 133, Storage 134, Network Interface 135, Expansion I / F 136, and a graphics board 139. The CPU 132 is a central processing unit that executes programs deployed in RAM 133 and stores temporary data. Storage 134 is a memory area for storing programs and data deployed in RAM 133. Storage 134 may be a hard disk drive (HDD) or a solid state drive (SSD), etc.

[0020] NetworkInterface135 is an interface for CPU132 to communicate with devices inside and outside the color verification client131. NetworkInterface135 may be connected by a wired network or by a wireless network.

[0021] The expansion I / F 136 is an interface for connecting hardware to the color verification client 131. In this embodiment, a colorimeter 137, a colorimeter 138 with an automatic paper feed function, a keyboard 140, and a mouse 141 are connected to the expansion I / F 136. The colorimeter 137 is a colorimeter that does not have a paper feed function for measuring the color of a test chart. When measuring color using the colorimeter 137, it is necessary to manually specify all patches on the test chart to be measured. The colorimeter 138 is a colorimeter that has a paper feed function for measuring the color of a test chart. When measuring color using the colorimeter 138, once the test chart to be measured is set, all patches on the test chart can be automatically read. The keyboard 140 is a user interface for the operator to input numbers and characters. The mouse 141 is a user interface for the operator to input position or coordinates on the screen and give work instructions.

[0022] The graphics board 139 is an expansion board for outputting video to an externally mounted display 142 from the color verification client 131. The display 142 is a user interface for displaying video to the operator from the color verification client 131. In this embodiment, the keyboard 140, mouse 141, and display 142 are described as separate components, but the system is not limited to this. For example, a touch panel may be used to integrate the input device and the display device.

[0023] Controller 151 is a controller unit for controlling input and output to printer 150. Printer 150 is a printer device for printing on printing media. In this embodiment, the identifier "Printer X" is assigned to printer 150. Printer 150 is a printer device that includes a feeder 152, an engine 153, a finisher 155, and a device UI 156. Feeder 152 is a unit for holding multiple copies of printing media (printing paper) and supplying them to engine 153. Multiple feeder units may be connected to a single engine.

[0024] The engine 153 is a unit that prints on the printing medium supplied from the feeder 152 using colorants and supplies it to the finisher 155. The engine 153 may print using an inkjet method or an electrophotographic method. Furthermore, in this embodiment, the engine 153 includes an inline sensor 154. The inline sensor 154 has the function of measuring the color of the printing result on the transport path (inline) when the engine 153 prints on the printing medium. In this embodiment, the configuration is described as being realized by a single engine, but a configuration in which multiple engines are linked together may also be used.

[0025] The finisher 155 is a unit for performing post-processing such as cutting, folding, or binding on the printed medium printed by the engine 153. Multiple finisher units may be connected to a single engine. The device UI 156 is a user interface that displays a user interface screen (UI screen) for displaying the status of the printer 150. The device UI 156 may have input functions such as buttons, a touch panel, and a keyboard, as well as output functions such as a buzzer and an LCD.

[0026] Controller 160 is a controller unit for controlling printer 170. Here, we will focus on explaining the differences between controller 160, controller 151, and printer 150. Controller 160 includes controller UI 161. Controller UI 161 is a user interface that displays a user interface screen for displaying the status of printer 170.

[0027] In this embodiment, the printer 170 is assigned the identifier "Printer Z". The printer 170 is a printer device for printing on a printing medium, including a feeder 171, an engine 172, an inspection system 173, and a finisher 174. The engine 172 is a unit that prints on the printing medium supplied from the feeder 171 using colorants and supplies it to the inspection system 173. Note that the engine 172 is not equipped with an in-line sensor.

[0028] The inspection system 173 is a unit for verifying and inspecting the contents printed on the printing medium by the engine 153, including color measurement, on the transport path. If the inspection system 173 determines that there is a quality problem as a result of its verification, it notifies the controller 160 of the abnormal condition, and the controller 160 takes action such as stopping printing. If it determines that there is no quality problem, the printing medium is supplied to the finisher 174.

[0029] Figure 2 is a software configuration diagram of the color verification system. In this embodiment, explanations regarding the Operating System (OS), middleware, and device drivers for controlling each device are omitted.

[0030] The Database service 102 includes a color verification settings collection 211, a paper settings collection 222, a color verification criteria settings collection 223, a notification destination settings collection 224, and a color verification results collection 225. The color verification settings collection 211 is a collection for managing color verification settings, including measurement conditions. The paper settings collection 222 is a collection for managing paper settings. The color verification criteria settings collection 223 is a collection for managing color verification criteria settings, including criteria for determining whether the measurement results are suitable for actual printing. The notification destination settings collection 224 is a collection for managing accounts to which various events occurring in the color verification system should be notified, and the notification conditions associated with each account. The color verification results collection 225 is a collection for managing color verification results, which are the results of color verification.

[0031] This section focuses on the color verification server program (RAM) 240, which runs on the color verification server 101. Storage 113 holds the color verification server program 220 and the color verification server resources 230. CPU 111 executes the program by deploying the color verification server program 220 as the color verification server program (RAM) 240 on RAM 112. The color verification server resources 230 store files such as HTML and images that are provided by the color verification client program 290 (described later) upon request. The color verification server program (RAM) 240 includes a Web Server 250 and a Scheduler Engine 260.

[0032] The Web Server 250 includes a backend primarily for processing various requests from outside the color verification server 101, and modules primarily for processing requests from within the color verification server 101. The Web Server 250 includes a color verification setting backend 251, a paper setting backend 252, a color verification criteria backend 253, a notification destination setting backend 254, and a color verification performance backend 255. Each backend has a unique URL defined, and its respective processing is executed by accessing it using methods such as POST, GET, and PUT.

[0033] The color verification settings backend 251 is the backend for retrieving a list of color verification settings from the color verification settings collection 211 and for creating, updating, and deleting color verification settings. The paper settings backend 252 is the backend for retrieving a list of paper settings from the paper settings collection 222 and for creating, updating, and deleting paper settings. The color verification criteria backend 253 is the backend for retrieving a list of color verification criteria settings from the color verification criteria settings collection 223 and for creating, updating, and deleting color verification criteria settings on the color verification criteria settings collection 223. The notification destination settings backend 254 is the backend for retrieving a list of notification destination settings from the notification destination settings collection 224 and for creating, updating, and creating notification destination settings on the notification destination settings collection 224. The color verification results backend 255 is the backend for retrieving a list of color verification results from the color verification results collection 225 and for creating, updating, and deleting color verification results on the color verification results collection 225.

[0034] The Web Server 250 also includes a test chart generation module 256, an account management backend 257, and a device management backend 258. The test chart generation module 256 is a module for generating the necessary test charts based on specified color verification settings. The account management backend 257 is a backend for obtaining information about user accounts from the account management service 103 and issuing notification instructions to user accounts. The device management backend 258 is a backend for obtaining information about devices from the device management service 104 and requesting control over devices.

[0035] The Scheduler Engine 260 is a service that notifies user accounts via the account management service 103 when a specified time arrives. The Scheduler Engine 260 also controls the timers and signals used in this embodiment. The Scheduler Engine 260 receives timer setting requests from CPU 111 and CPU 132 via the Web Server 250, executes the requests, and returns the execution results as a response. This allows both CPU 111 and CPU 132 to set timers to start at specific times and to cancel set timers. The Scheduler Engine 260 can also receive signals when a timer starts and notify CPU 111 and CPU 132. Describing this entire process would be extremely complicated. Therefore, in this embodiment, it is assumed that CPU 111 and CPU 132 can transparently set and cancel timers and receive signals.

[0036] Furthermore, the Scheduler Engine 260 has multiple functions. For example, based on timers and signals controlled by the Scheduler Engine 260, the color verification task is divided and managed into a color verification preparation phase and a color verification execution phase, as shown in Figure 3. Thus, the Scheduler Engine 260 functions as a management unit that divides the color verification task into two or more phases and manages each phase.

[0037] As shown in Figure 3, the color verification preparation time is represented as the driver print preparation time or the direct print preparation time. Similarly, the color verification execution time is represented as the color verification execution time (manual paper feed), the color verification execution time (automatic paper feed), or the color verification execution time (fully automatic). The Scheduler Engine 260 links the color verification preparation phase to the color verification preparation time by controlling timers and signals. Likewise, the Scheduler Engine 260 links the color verification execution phase to the color verification execution time. Therefore, the Scheduler Engine 260 also functions as a linking unit that connects each phase to its corresponding work time.

[0038] Furthermore, the color verification preparation time, such as the driver print preparation time or direct print preparation time, and the color verification execution time, such as the color verification execution time (manual paper feed), color verification execution time (automatic paper feed), or color verification execution time (fully automatic), may be fixed or variable. If the color verification preparation time and color verification execution time are fixed, the Scheduler Engine 260 sets the expiration time of each timer to a fixed value. If the color verification preparation time and color verification execution time are variable, the Scheduler Engine 260 requests the account management service 103 to notify the user of the recommended values ​​for each work time based on the work time stored in the color verification performance backend 255. Upon receiving this request from the Scheduler Engine 260, the account management service 103 notifies the user of the recommended values ​​for each work time by sending an email to the user or displaying them on the display 142. The account management service 103 may also display the recommended values ​​for each work time on the UI 156 of the printer 150 or the UI 161 of the controller 160. Furthermore, Scheduler Engine260 may automatically set the recommended values ​​for each task time to the timer settings that notify the color verification preparation time and color verification execution time. The above functions are part of the functions of the management unit of Scheduler Engine260.

[0039] Next, the color verification client program 290, which operates on the color verification client 131, will be described. The color verification client program 290 is a web application that operates on the web browser 280. The color verification client program 290 includes a color verification setting application 291, a color measurement application 292, a result reference application 293, a result comparison application 294, and various setting applications 295. The color verification setting application 291 is an application for performing color verification settings. The color measurement application 292 is an application for performing color measurement. The result reference application 293 is an application for referencing the results of color verification. The result comparison application 294 is an application for comparing color verification results. The various setting applications 295 are applications for making various settings used in the system. These applications send and receive data related to color verification by sending requests to and receiving responses from the color verification server 101 via network communication.

[0040] Figure 3 is a conceptual diagram of the preparation time for printing the color verification chart and the time required to perform the color verification. In this embodiment, when setting up periodic color verification, the administrator can select the operating mode to use from three operating modes: "manual printing + manual color measurement" mode, "automatic printing + manual color measurement" mode, and "fully automatic" mode.

[0041] In "manual printing + manual color measurement" mode, the operator is expected to load the paper and perform color adjustments during period 301 when the color verification start time arrives, acquire print data for the test chart during period 302, and then print using the printer driver. The time required for these color measurement preparations is referred to as the driver print preparation time.

[0042] In "automatic printing + manual color measurement" mode, the operator loads paper into the feeder and adjusts the engine's color during the preceding period 301. When the color verification start time arrives, it is assumed that the test chart will be automatically printed directly during period 311. The time required for these color measurement preparations is referred to as the direct printing preparation time. Note that, for engines with small color fluctuations, such as inkjet engines, engine color adjustment may be omitted.

[0043] In "manual printing + manual color measurement" mode or "automatic printing + manual color measurement" mode, there are two main methods for measuring the color of the test chart. One method is color measurement by manual paper feeding, which is performed during period 303. In manual paper feeding, the operator manually measures the color of each patch on the test chart. The other method is color measurement by automatic paper feeding, which is performed during period 305. In automatic paper feeding, the operator sets the test chart, the colorimeter automatically feeds the test chart, and then measures the color of the patches on the test chart. Adding the color verification time performed during period 304 to these methods, the total time is defined as the color verification execution time (manual paper feeding) and the color verification execution time (automatic paper feeding), respectively.

[0044] In "fully automatic" mode, the operator loads the paper during period 321 as a preparatory step. When the color verification start time arrives, the color verification system automatically performs a series of steps during period 322: color adjustment, direct printing, color measurement, and color verification. The time taken for this series of color verification tasks is defined as the color verification execution time (fully automatic).

[0045] Figure 4 shows the notification destination setting screen of the various settings application 295. The notification destination setting screen is implemented within the various settings application 295, which is included in the color verification client program 290 running on the color verification client 131. The processing of the notification destination setting screen is executed by the CPU 132. The notification destination setting screen of the various settings application 295 includes an application switching bar 400 and a various settings view 410.

[0046] The application switching bar 400 is a user interface component for switching between applications, commonly provided for each application included in the color verification client program 290. When the CPU 132 detects that a switching button associated with a particular application has been pressed, it displays the view of that application. For example, when the CPU 132 detects that the color verification settings button 401 has been pressed, it displays the color verification settings view 900 of the color verification settings application. When the CPU 132 detects that the color measurement button 402 has been pressed, it displays the color measurement settings view 1800 of the color measurement application. When the CPU 132 detects that the result reference button 403 has been pressed, it displays the view of the result reference application. When the CPU 132 detects that the result comparison button 404 has been pressed, it displays the view of the result comparison application. When the CPU 132 detects that the various settings button 405 has been pressed, it displays the various settings views 410 of the various settings applications.

[0047] The various settings view 410 includes a various settings switching panel 420, a notification destination setting list 430, a notification destination setting command panel 440, and a notification destination setting property 450. The various settings switching panel 420 is a panel for selecting setting items to be set within the various settings application 295. When the CPU 132 detects that the paper setting button 421 is pressed, it displays a screen for creating, editing, and deleting paper settings. When the CPU 132 detects that the color verification standard button 422 is pressed, it displays a screen for creating, editing, and deleting color verification standards. When the CPU 132 detects that the notification destination setting button 423 is pressed, it displays a screen for creating, editing, and deleting notification destination settings. In Figure 4, the following explanation assumes that the notification destination setting button 423 is pressed.

[0048] The notification destination setting list 430 is a list for displaying a list of notification destination settings. When the CPU 132 detects that a button has been pressed on any of the notification destination settings included in the notification destination setting list 430, it determines that the notification destination setting has been selected. The notification destination setting command panel 440 is a panel for issuing various operation commands to the selected notification destination setting. The notification destination setting command panel 440 includes a new creation button 441, an edit button 442, and a delete button 443.

[0049] When CPU 132 detects that the New button 441 is pressed, it displays the notification destination setting properties 450 to create a new notification destination setting. At this time, the ID attribute of the notification destination setting properties 450 is set as an invalid value. When CPU 132 detects that the Edit button 442 is pressed, it displays the notification destination setting properties 450 to edit the selected notification destination setting. At this time, the ID attribute of the selected notification destination setting is set as an valid value in the notification destination setting properties 450. When CPU 132 detects that the Delete button 443 is pressed, it displays a confirmation dialog asking whether it is OK to delete the selected notification destination setting.

[0050] The notification destination setting property 450 is a properties screen used when creating or editing a notification destination setting. Figure 4 shows an example where the notification destination setting "Notification Destination Setting 1" is selected and the edit button 442 is pressed, and the contents of "Notification Destination Setting 1" are being edited.

[0051] The notification destination setting property 450 includes a name text box 451, a driver print preparation time drop-down list 452, and a direct print preparation time drop-down list 453. It also includes a color verification execution time (manual paper feed) drop-down list 454, a color verification execution time (automatic paper feed) drop-down list 455, and a color verification execution time (fully automatic) drop-down list 456. Furthermore, it includes one or more notification conditions 470 and an add notification destination button 475. Finally, it also includes a cancel button 481 and a save button 482.

[0052] The Name text box 451 is a text box for editing the name to be assigned to the notification destination setting currently being edited. The Driver Print Preparation Time dropdown list 452 is a dropdown list for selecting the estimated work time for the notification destination setting currently being edited, assuming that the test chart will be printed from the printer driver. The Direct Print Preparation Time dropdown list 453 is a dropdown list for selecting the estimated work time for the notification destination setting currently being edited, assuming that the test chart will be sent directly to the controller for printing. The Color Verification Execution Work Time (Manual Paper Feed) dropdown list 454 is a dropdown list for selecting the estimated work time for the notification destination setting currently being edited, assuming that the printed test chart will be manually fed and color measured. The Color Verification Execution Work Time (Automatic Paper Feed) dropdown list 455 is a dropdown list for selecting the estimated work time for the notification destination setting currently being edited, assuming that the printed test chart will be automatically fed and color measured. The Color Verification Execution Time (Fully Automatic) dropdown list 456 is a dropdown list for selecting the estimated execution time, assuming that color verification is performed fully automatically in the notification destination settings currently being edited. The concept of estimated execution time has already been explained in Figure 3.

[0053] Notification conditions 470 is a set of settings items for configuring notification conditions for each account. Notification conditions 470 includes a dropdown list of recipient accounts 471, a checkbox for color verification start / completion notification conditions 472, a checkbox for color verification preparation delay / execution incomplete notification conditions 473, a button to remove notification recipients 474, and a button to add notification recipients 475.

[0054] The notification destination account dropdown list 471 is a dropdown list for selecting the account to which notifications will be sent in the account setting. The color verification start / completion notification condition checkbox 472 is a checkbox for selecting whether or not to send a notification to the account when the start or completion of color verification is detected for the color verification setting to which the notification destination setting is selected. The color verification preparation delay / execution incomplete notification condition checkbox 473 is a checkbox for selecting whether or not to send a notification to the account when a delay or incompleteness in color verification preparation is detected for the color verification setting to which the notification destination setting is selected. The notification destination delete button 474 is a button for deleting the account setting from the notification destination setting. The notification destination add button 475 is a button for adding a new account setting to the notification destination setting. As described above, in this embodiment, multiple accounts are maintained by associating notification conditions with a single notification destination setting.

[0055] The Cancel button 481 is used to close the notification destination settings property 450 without saving the notification destination settings. The Save button 482 is used to save the notification destination settings. The process of saving the notification destination settings will be explained in detail in Figure 5.

[0056] Figure 5 is a flowchart of the process for displaying the notification destination settings screen of the various settings application 295. The program that executes the process in this flowchart is implemented within the various settings application 295, and the CPU 132 executes this program.

[0057] In S501, the CPU 132 overlays a Loading component (not shown) onto the various settings views 410. Here, the Loading component is a component that displays "Loading data" and other messages on the screen while data is being loaded. While the Loading component is overlaid, the CPU 132 does not accept any other operations on the components on the various settings views 410. Next, the CPU 132 executes the processes of S511 and S521 in parallel. In S511, the CPU 132 sends a request to the color verification server 101 to obtain a list of notification destination settings. In S512, the CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the list of notification destination settings. In S521, the CPU 132 sends a request to the color verification server 101 to obtain a list of account information. In S522, the CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the list of account information. The operation of the color verification server 101 will be described later in Figure 6. CPU132 waits until both the S512 and S522 processes are completed.

[0058] In S531, the CPU 132 branches the process based on the response to retrieve the list of notification destination settings. If the response to retrieve the list of notification destination settings is normal, the process proceeds to S532. If the response to retrieve the list of notification destination settings is abnormal, the process proceeds to S534. In S532, the CPU 132 retrieves the list of notification destination settings from the response to retrieve the list of notification destination settings. In S533, the CPU 132 updates the notification destination setting list 430 using the retrieved list of notification destination settings. In S534, the CPU 132 displays a notification destination setting list retrieval failure popup on the various setting views 410. Here, a popup is a component for displaying information, warnings, or errors on the screen for a certain period of time. The same applies to popup displays described in the following explanation.

[0059] In S541, the CPU 132 branches the process based on the response to retrieve the list of account information. If the response to retrieve the list of account information is normal, the process proceeds to S542. If the response to retrieve the list of account information is abnormal, the process proceeds to S543. In S542, the CPU 132 retrieves the account information from the response to retrieve the list of account information. This account information is used as the selection item for the notification destination account dropdown list 471. In S543, the CPU 132 displays a popup indicating that the account information list acquisition failed. In S551, the CPU 132 hides the Loading component from the various settings view 410. As a result, the CPU 132 becomes able to accept operations on the components on the various settings view 410.

[0060] Figure 6 is a flowchart of the save process performed on the notification destination setting screen of the various settings application 295. The program that executes the process in this flowchart is implemented within the various settings application 295, and the CPU 132 executes this program.

[0061] In S601, CPU 132 converts the setting value configured on notification destination setting property 450 into JSON format in order to notify notification destination setting backend 254 of the said setting value. In this embodiment, the JSON format, which is widely used as one of the data formats, is used for explanation, but other formats can be used when implementing this disclosure. For example, any format such as XML format or YAML format may be used.

[0062] In S611, CPU132 branches the process based on the ID attribute of the notification destination setting property 450. If the notification destination setting ID is invalid, the process proceeds to S612. If the notification destination setting ID is valid, the process proceeds to S614.

[0063] An invalid notification destination setting ID means that a new notification destination setting needs to be created. In S612, CPU 132 sends a request to the color verification server 101 to create a notification destination setting. In S613, CPU 132 receives a response from the color verification server 101 confirming the creation of the notification destination setting. A valid notification destination setting ID means that an existing notification destination setting needs to be updated. In S614, CPU 132 sends a request to the color verification server 101 to update the notification destination setting. In S615, CPU 132 receives a response from the color verification server 101 confirming the update of the notification destination setting.

[0064] In S621, the CPU 132 branches the process based on the response to create or update the notification destination setting. If the response to create or update the notification destination setting is a normal response, the process proceeds to S622. If the response to create or update the notification destination setting is an abnormal response, the process proceeds to S623. In S622, the CPU 132 displays a notification destination setting creation success popup or a notification destination setting update success popup for the notification destination setting property 450. In S623, the CPU 132 displays a notification destination setting creation failure popup or a notification destination setting update failure popup for the notification destination setting property 450.

[0065] Figure 7 is a flowchart showing the processing of the main loop of the Web Server 250. The program that executes the processing in this flowchart is implemented in the color verification server program (RAM) 240, and the CPU 111 executes this program. The requests from the color verification client 131 to the color verification server 101 and the responses to those requests in the flowcharts in Figures 5, 6, and 7 onward are executed by the processing in this flowchart. For the sake of simplicity, only the important parts will be described in this embodiment.

[0066] In S701, CPU 111 receives WebAPI requests from color verification client 131 using the HTTP protocol or similar. A WebAPI request includes a resource name such as "backend name" and a method specification for that resource. The method specification means, for example, GET means a request to retrieve a list, PUT means a request to create, POST means a request to update, and DELETE means a request to delete. The target of processing is specified by the URL (Uniform Resource Locator) and resource name. For example, the resource name might be " / colortest" for color verification settings or " / substrate" for paper settings. CPU 111 determines the type of request from this resource name and method specification.

[0067] In S702, CPU111 branches the processing based on the type of request. If the request type is a request related to color verification settings, processing proceeds to S711. If the request type is a request related to paper settings, processing proceeds to S712. If the request type is a request related to color verification standard settings, processing proceeds to S713. If the request type is a request related to notification destination settings, processing proceeds to S714. If the request type is a request related to color verification results, processing proceeds to S715. If the request type is a request related to account information, processing proceeds to S716. If the request type is a request related to device information, processing proceeds to S717.

[0068] In S711, CPU 111 executes color verification setting processing. In S712, CPU 111 executes paper setting processing. In S713, CPU 111 executes color verification standard setting processing. In S714, CPU 111 executes notification destination setting processing. In S715, CPU 111 executes color verification results processing. In S716, CPU 111 executes account management processing. CPU 111 obtains necessary information from account management service 103 via account management backend 257 and responds to the obtained information. In S717, CPU 111 executes device management processing. CPU 111 obtains necessary information from device management service 104 via device management backend 258 and responds to the obtained information.

[0069] In S721, CPU111 sends the execution results of each process as various processing result responses to the WebAPI request sender. The content of these responses is set by CPU111 for each process. Specifically, if the process is completed successfully, CPU111 sends a response with a status code indicating success. If the process is not completed successfully, CPU111 sends a response with a status code indicating failure. If the request concerns retrieving a list, CPU111 adds the list retrieval result to the response. Once processing in S721 is complete, CPU111 waits for the arrival of a new WebAPI request.

[0070] Figure 8 shows the data structure of the notification destination setting list. The notification destination setting list can hold multiple notification destination settings. Also, a notification destination setting can hold multiple notification conditions. The id attribute of a notification destination setting is an identifier attribute used to uniquely identify that notification destination setting. The name attribute of a notification destination setting is an attribute that indicates the name information of that notification destination setting, which can be set arbitrarily by the administrator. The driver-print-prepare-time attribute of a notification destination setting indicates the driver print preparation time. The direct-print-prepare-time attribute of a notification destination setting indicates the direct print preparation time. The color-measurement-manual-time attribute of a notification destination setting indicates the color verification execution time (manual paper feed). The color-measurement-autofeed-time attribute of a notification destination setting indicates the color verification execution time (automatic paper feed). The color-validation-fullauto-time attribute of a notification destination setting indicates the color verification execution time (fully automatic). The recipient attribute in the notification settings is an attribute that indicates the notification conditions.

[0071] The `id` attribute of a notification condition is used to uniquely determine the recipient account information. For example, the `id` attribute of a notification condition could be an email address or an account name. The `start_end_trigger` attribute of a notification condition specifies whether or not to send a notification to the account when color verification starts / is completed. The `overdue_unfinished_trigger` attribute of a notification condition is linked to the recipient account information and specifies whether or not to send a notification to the account in case of delays in color verification preparation or incomplete color verification.

[0072] Figure 9 shows the screen of the color verification settings application 291. The color verification settings application screen includes the application switching bar 400 and the color verification settings view 900. The application switching bar 400 has already been explained in Figure 4, so its explanation will be omitted. The explanation of the application switching bar 400 will also be omitted in the explanations of subsequent screens.

[0073] The color verification settings view 900 includes a color verification settings list 910, a color verification settings command panel 920, and color verification settings properties 930. The color verification settings list 910 is a list display unit for displaying a list of color verification settings. When the CPU 132 detects that a button has been pressed on any of the color verification settings included in the color verification settings list 910, it determines that the color verification setting has been selected.

[0074] The color verification settings command panel 920 is a panel for issuing various work instructions to the selected color verification settings. The color verification settings command panel 920 includes a new button 921, an edit button 922, and a delete button 923. When the CPU 132 detects that the new button 921 is pressed, it displays the color verification settings properties 930 to create a new color verification setting for the selected color verification settings. At this time, the ID attribute of the color verification settings properties 930 is set as an invalid value. When the CPU 132 detects that the edit button 922 is pressed, it displays the color verification settings properties 930 to edit the selected color verification settings. At this time, the ID attribute of the selected color verification settings is set as an valid value in the color verification settings properties 930. When the CPU 132 detects that the delete button 923 is pressed, it displays a confirmation dialog to confirm the deletion of the selected color verification settings.

[0075] The Color Verification Settings Properties 930 is a properties screen used when creating or editing the selected color verification settings. It is desirable to toggle the display / hide of the Color Verification Settings Properties 930 according to the instructions on the Color Verification Settings Command Panel 920. For the sake of explanation, Figure 9 shows the state where Color Verification T is selected, the Edit button 922 is pressed, and the Color Verification Settings Properties 930 is displayed.

[0076] The color verification settings property 930 includes a name text box 931, a target printer dropdown list 932, a paper dropdown list 933, and a color verification criteria dropdown list 934. The color verification settings property 930 also includes a notification destination setting dropdown list 935, a colorimeter method dropdown list 936, a colorimeter specification dropdown list 937, and a repeat setting dropdown list 941.

[0077] The color verification setting property 930 has one or more repeating pattern settings 940 if the repeating setting in the repeating setting dropdown list 941 is set to "Yes". The repeating pattern setting 940 includes a pattern setting dropdown list 942, a color verification start time picker 943, and a delete repeating setting button 944. The color verification setting property 930 also includes an add repeating setting button 945, a cancel button 951, and a save button 952.

[0078] The Name text box 931 is a text box for editing the name information to be assigned to the color verification setting currently being edited. The Target Printer dropdown list 932 is a dropdown list for selecting the target printer for the color verification setting currently being edited. The Paper dropdown list 933 is a dropdown list for selecting the target paper for the color verification setting currently being edited. The Color Verification Criteria dropdown list 934 is a dropdown list for selecting the target color verification criteria for the color verification setting currently being edited. The Notification Destination dropdown list 935 is a dropdown list for selecting the notification destination for the color verification setting currently being edited. The Color Measurement Method dropdown list 936 is a dropdown list for selecting the color measurement method to be used for the color verification setting currently being edited. In this embodiment, you can select from "Manual Printing + Manual Color Measurement" mode, "Automatic Printing + Manual Color Measurement" mode, and "Fully Automatic" mode. The Colorimeter Specification dropdown list 937 is a dropdown list for selecting the colorimeter to be used for the color verification setting currently being edited. In this embodiment, the colorimeter to be used can be selected from a colorimeter (manual paper feed), a colorimeter (automatic paper feed), an inline sensor, and an inspection system.

[0079] The Repeat Settings dropdown list 941 is a dropdown list for selecting whether to use a repeat setting in the currently edited color verification setting. The Pattern Settings dropdown list 942 is a dropdown list for selecting what pattern to repeat in the said repeat pattern setting. In this embodiment, it is possible to select the days of the week from Monday to Sunday. The Color Verification Start Time Picker 943 is a picker for specifying the start time in the said repeat pattern setting. The Delete Repeat Setting button 944 is a button for deleting the said repeat pattern setting. The Add Repeat Setting button 945 is a button for adding a new repeat pattern setting to the currently edited color verification setting. The Cancel button 951 is a button for closing the Color Verification Setting Properties 930 without saving the currently edited color verification setting. The Save button 952 is a button for saving the currently edited color verification setting.

[0080] Figure 10 is a flowchart of the color verification setting application 291 when it is displayed on the screen. The program that executes the processes in this flowchart is implemented within the color verification setting application 291, and the CPU 132 executes this program.

[0081] In S1001, the CPU 132 overlays the Loading component onto the color verification settings view 900. While the Loading component is overlaid, the CPU 132 does not accept any operations on other components on the color verification settings view 900. When the Loading component is overlaid, the CPU 132 executes the processes of S1011, S1021, S1023, S1025, and S1027 in parallel.

[0082] In S1011, CPU 132 sends a request to the color verification server 101 to obtain a list of color verification settings. In S1012, CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the color verification settings list. In S1021, CPU 132 sends a request to the color verification server 101 to obtain a list of device information. In S1022, CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the device information list. In S1023, CPU 132 sends a request to the color verification server 101 to obtain a list of paper settings. In S1024, CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the paper settings list. In S1025, CPU 132 sends a request to the color verification server 101 to obtain a list of color verification reference settings. In S1026, CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the color verification reference settings list. In S1027, CPU 132 sends a request to color verification server 101 to retrieve a list of notification destination settings. In S1028, CPU 132 receives a response from color verification server 101 retrieving the list of notification destination settings. Then, CPU 132 waits until all the processes in S1012, S1022, S1024, S1026, and S1028 described above are completed.

[0083] In S1041, the CPU 132 branches the process based on the response to obtain the list of color verification settings. If the response to obtain the list of color verification settings is normal, the process proceeds to S1042. If the response to obtain the list of color verification settings is abnormal, the process proceeds to S1043. In S1042, the CPU 132 obtains the list of color verification settings from the response to obtain the list of color verification settings. In S1043, the CPU 132 reflects the list of color verification settings in the color verification setting list 910. In S1044, the CPU 132 displays a popup indicating that the acquisition of the list of color verification settings failed.

[0084] In S1051, the CPU 132 branches the process based on the response to obtain the list of device information. If the response to obtain the list of device information is normal, the process proceeds to S1053. If the response to obtain the list of device information is abnormal, the process proceeds to S1054. In S1053, the CPU 132 obtains a list of device information from the response to obtain the list of device information. This list of device information is used as the selection item for the target printer dropdown list 932. In S1054, the CPU 132 displays a popup indicating that the device information list acquisition failed.

[0085] In S1061, CPU 132 branches the process based on the response to obtain the list of paper settings. If the response to obtain the list of paper settings is normal, the process proceeds to S1062. If the response to obtain the list of paper settings is abnormal, the process proceeds to S1063. In S1062, CPU 132 obtains the paper setting information from the response to obtain the list of paper settings. This paper setting information is used for the selection item in the paper drop-down list 933. In S1063, CPU 132 displays a popup indicating that the paper setting list acquisition failed.

[0086] In S1071, the CPU 132 branches the process based on the response to obtain the list of color verification criteria settings. If the response to obtain the list of color verification criteria settings is normal, the process proceeds to S1072. If the response to obtain the list of color verification criteria settings is abnormal, the process proceeds to S1073. In S1072, the CPU 132 obtains color verification criteria information from the response to obtain the list of color verification criteria settings. This color verification criteria information is used for the selection item in the color verification criteria dropdown list 934. In S1073, the CPU 132 displays a popup indicating that the acquisition of the list of color verification criteria settings failed.

[0087] In S1081, CPU132 branches the process based on the response to retrieve the list of notification destination settings. If the response to retrieve the list of notification destination settings is normal, the process proceeds to S1082. If the response to retrieve the list of notification destination settings is abnormal, the process proceeds to S1083. In S1082, CPU132 retrieves the notification destination settings from the response to retrieve the list of notification destination settings. These notification destination settings are used as the selection items in the notification destination setting dropdown list 935. In S1083, CPU132 displays a popup indicating that the retrieval of the list of notification destination settings failed.

[0088] In S1091, CPU132 hides the Loading component on the color verification settings view 900. This allows CPU132 to accept operations on the component in the color verification settings view 900.

[0089] Figure 11 is a flowchart relating to the color verification setting process. The program that executes the process in this flowchart is implemented within the color verification setting backend 251, and the CPU 111 executes this program. In S1101, the CPU 111 initializes the response to an abnormal response and the response data to empty. In S1102, the CPU 111 opens the color verification setting collection 211.

[0090] In S1103, CPU111 branches the process based on the open result. If the open result is successful, the process proceeds to S1110. If the open result is unsuccessful, the process proceeds to S1163. In S1110, CPU111 branches the process according to the request type. If the request type is a request to obtain a list of color verification settings, the process proceeds to S1111. If the request type is a request to delete a color verification setting, the process proceeds to S1122. If the request type is a request to create a color verification setting, the process proceeds to S1131. If the request type is a request to update a color verification setting, the process proceeds to S1141.

[0091] In S1111, CPU111 retrieves a list of color verification settings from color verification setting collection 211. In S1112, CPU111 converts the list of color verification settings into JSON format and sets the converted data as response data. In S1161, CPU111 sets the response as a successful response. In S1162, CPU111 closes color verification setting collection 211. In S1163, CPU111 sends the response and response data to the requester.

[0092] In S1122, CPU 111 sends a request to delete the color verification setting to the color verification setting collection 211. In S1123, CPU 111 receives a response to delete the color verification setting. In S1151, CPU 111 branches the process based on the response. If the response is successful, the process proceeds to S1152. If the response is unsuccessful, the process proceeds to S1153. In S1152, CPU 111 sends a schedule update signal to Scheduler Engine 260, and the process proceeds to S1161. The processes described above from S1161 onwards are then performed. In S1153, CPU 111 displays a deletion failure popup, and the process proceeds to S1162. The processes described above from S1162 onwards are then performed.

[0093] In S1131, the CPU 111 interprets the color verification settings in JSON format. In S1132, the CPU 111 sends a request to create the color verification settings to the color verification settings collection 211. In S1133, the CPU 111 receives a response from the color verification settings collection 211 confirming the creation of the color verification settings. The processing described above from S1151 onwards then proceeds.

[0094] In S1141, the CPU 111 interprets the color verification settings in JSON format. In S1142, the CPU 111 sends an update request for the color verification settings to the color verification settings collection 211. In S1143, the CPU 111 receives an update response for the color verification settings from the color verification settings collection 211. The processing described above from S1151 onwards then proceeds.

[0095] Figure 12 shows the data structure of the color verification settings list. The color verification settings list can hold multiple color verification settings. The id attribute of a color verification setting is used to uniquely identify that color verification setting. The name attribute of a color verification setting indicates the name information of that color verification setting, which can be arbitrarily set by the administrator. The printer attribute of a color verification setting indicates the target printer for that color verification setting. The substrate attribute of a color verification setting indicates the paper for that color verification setting. The verification-criteria attribute of a color verification setting indicates the color verification criteria for that color verification setting. The notification attribute of a color verification setting indicates the notification destination setting for that color verification setting. The method attribute of a color verification setting indicates the color measurement method for that color verification setting. The measurement-device attribute of a color verification setting indicates the colorimeter specification for that color verification setting. The short-codes attribute of a color verification setting indicates the short code associated with that color verification setting. Here, a short code is a unique identifier assigned to each color verification task. In this embodiment, short codes are represented as four-digit decimal numbers. Multiple color verification tasks are associated with a single color verification setting, and a portion of the chart data is associated with each color verification task. When performing color measurement, entering a short code links the color verification task with the color verification setting, eliminating the need to input various color measurement conditions. Printing the short code on the chart data links the short code with the color patch printed on the print medium. The scheduled-short-codes attribute of a color verification setting indicates the short codes associated with the chart data generated from the schedule of that color verification setting. The overdue-short-code attribute of a color verification setting indicates the short codes associated with that color verification setting that have exceeded the expected work time.

[0096] The `schedule` attribute indicates the repeat pattern setting for the color validation setting. The `dayOfWeek` attribute of the repeat pattern indicates the pattern of the repeat setting. The `startTime` attribute of the repeat pattern indicates the start time of the color validation for the repeat setting.

[0097] Figure 13 is a state transition diagram of the color verification task in this embodiment. When a color verification setting is created by the administrator, color verification tasks are conceptually generated based on the repeating pattern information registered in that color verification setting. However, in this embodiment, the color verification tasks are described in a configuration in which they are generated using a timer that starts at a specified time, without creating data for each color verification task.

[0098] The initial state of the color verification task is Waiting state 1301. When the scheduled start time for color verification registered in the schedule arrives, the color verification task enters Due state 1311 within the Color Verification Preparation state 1310. When the color verification preparation time for the color verification task in Due state 1311 has elapsed, it enters Overdue state 1312.

[0099] When an operator starts measuring color in a color verification task that is in the color verification preparation state 1310, the state changes to the Processing state 1321 within the color verification execution state 1320. When the color verification execution time for the color verification task in the Processing state 1321 has elapsed, the state changes to Not Finished state 1322.

[0100] In a color verification task that is in the "Color Verification in Progress" state (1320), once color measurement and color verification are complete, the state changes to "Color Verification Completed" (1330). At this time, if the color measurement results meet the color verification criteria, the color verification result is judged as "Passed," and the color verification task changes to the "Passed" state (1331). On the other hand, if the color measurement results do not meet the color verification criteria, the color verification result is judged as "Failed," and the color verification task changes to the "Failed" state (1332).

[0101] The following details the features of this disclosure. This disclosure has two assumed work times: a color verification preparation work time and a color verification execution work time. When the work in the color verification preparation phase and the work in the color verification execution phase begin, a work start event is notified to a designated recipient, and the progress of the work is managed. Furthermore, when the work in the color verification preparation phase and the work in the color verification execution phase are completed within their respective assumed work times, a work completion event is notified to the designated recipient. If the respective assumed work times are exceeded, the system transitions to an abnormal state. In this case, since the work completion event is not notified to the designated recipient, the user is notified that the work in the color verification preparation phase or the work in the color verification execution phase is incomplete.

[0102] Compared to the conventional method of simply judging based on the overall estimated work time, this disclosure allows for more detailed status management. For example, it is possible to manage the situation where color measurement has not started and the situation where color measurement has started but has not been completed as different states. In this way, by dividing the task into phases (subtasks), managers can grasp work delays on a task-by-task basis. Operators can also notice work delays earlier, allowing them to start recovery work on delays sooner.

[0103] Figure 14 is a flowchart showing the settings saving process of the color verification setting application 291. The program that executes the process shown in this flowchart is implemented within the color verification setting application 291, and the CPU 132 executes this program.

[0104] In S1401, CPU132 converts the color validation settings displayed on the color validation settings property 930 into JSON format. In S1411, CPU132 checks the ID of the color validation setting set in the displayed color validation settings property 930. If the ID of the color validation setting is invalid, i.e., a new color validation setting needs to be created, the process proceeds to S1412. If the ID of the color validation setting is valid, i.e., an existing color validation setting needs to be updated, the process proceeds to S1414.

[0105] In S1412, the CPU 132 sends a request to the color verification server 101 to create a color verification setting. In S1413, the CPU 132 receives a response from the color verification server 101 to create a color verification setting. In S1414, the CPU 132 sends a request to the color verification server 101 to update a color verification setting. In S1415, the CPU 132 receives a response from the color verification server 101 to update a color verification setting.

[0106] In S1421, the CPU 132 branches the process based on whether the response is for creating a color verification setting or updating a color verification setting. If the response is normal, the process proceeds to S1422. If the response is abnormal, the process proceeds to S1423. In S1422, the CPU 132 displays a popup indicating success in creating a color verification setting or success in updating a color verification setting. In S1423, the CPU 132 displays a popup indicating failure in creating a color verification setting or failure in updating a color verification setting.

[0107] Figure 15 shows the main loop of the Scheduler Engine 260. The program that executes the processing in this flowchart is implemented within the Scheduler Engine 260, and the CPU 111 executes this program. In S1501, the CPU 111 receives a new signal. If no signals have occurred, the CPU 111 waits until a new signal occurs. Once a new signal is received, processing proceeds to S1502.

[0108] In S1502, CPU111 opens the color verification settings collection. In S1503, CPU111 retrieves a list of color verification settings from the color verification collection. In S1504, CPU111 closes the color verification settings collection. In S1505, CPU111 opens the notification destination settings collection. In S1506, CPU111 retrieves a list of notification destination settings from the notification destination settings collection. In S1507, CPU111 closes the notification destination settings collection.

[0109] In S1510, CPU 111 switches processing according to the type of signal received. If the signal type is a schedule update signal, processing proceeds to S1521. If the signal type is a color verification preparation start timer signal, processing proceeds to S1531. If the signal type is a color verification preparation delay detection timer signal, processing proceeds to S1532. If the signal type is a color verification execution incomplete detection timer signal, processing proceeds to S1571.

[0110] In S1521, CPU 111 pauses all color verification preparation start timers. This schedule update signal is a signal sent from CPU 132 in S1152. In S1522, CPU 111 creates, updates, and deletes schedules that start all color verification preparation start timers based on the color verification settings list. For example, if a new schedule is added, a new color verification preparation start timer is added. If there is an updated schedule, the settings of the color verification preparation start timer are changed. If there is a schedule that is no longer needed, the color verification preparation start timer is deleted. In S1523, CPU 111 starts all color verification preparation start timers, and processing returns to S1501. When the process in S1523 is executed, the color verification preparation start timer signal is activated when the color verification start time arrives. At this time, the color verification preparation start timer is given hint information that links the timer to the color verification settings.

[0111] In S1531, CPU 111 executes the color verification preparation start timer signal processing described later. In S1532, CPU 111 executes the color verification preparation delay detection timer signal processing described later. In S1571, CPU 111 stops the color verification incomplete detection timer corresponding to the received timer signal. In S1572, CPU 111 notifies accounts registered in the notification destination settings that the color verification preparation delay / incomplete notification condition attribute is enabled, via the account management backend 257, that the color verification execution is incomplete.

[0112] Figure 16 is a flowchart of the color verification preparation start timer signal processing. In S1631, the CPU 111 stops the color verification preparation start timer corresponding to the received timer signal. In S1632, the CPU 111 requests the test chart generation module 256 to generate a chart. The test chart generation module 256 assigns a short code as identification information to identify each test chart. The short codes generated in this process are recorded in the scheduled-short-codes attribute of the color verification settings.

[0113] In S1633, the CPU 111 extracts the corresponding color verification setting based on the hint information attached to the signal and branches the processing based on the color measurement method of that color verification setting. If the color measurement method is "manual printing + manual color measurement" mode, the process proceeds to S1634. If the color measurement method is "automatic printing + manual color measurement" mode, the process proceeds to S1642. If the color measurement method is "fully automatic" mode, the process proceeds to S1651.

[0114] In S1634, CPU 111 sets the driver print preparation time specified in the notification destination settings as the color verification preparation work time. In S1635, CPU 111 adds a shortcode to the hint information and activates the color verification preparation work delay detection timer based on the color verification preparation work time. Specifically, the time when the color verification preparation start timer signal is issued is the color verification start time. The color verification preparation delay detection timer is set so that the color verification preparation delay detection timer signal is issued when the color verification preparation work time has elapsed, starting from the time the color verification process started. In S1636, CPU 111 notifies accounts registered in the notification destination settings that have the color verification start / completion notification condition 472 enabled, via the account management backend 257, that color verification has started. In the color verification start notification, the test chart data itself may be notified, or a URL from which the test chart can be downloaded may be notified.

[0115] In S1642, CPU 111 requests the device management backend 258 to automatically print the generated test chart. In S1643, CPU 111 sets the direct print preparation time of the notification destination setting specified in the color verification setting as the color verification preparation work time. In S1644, CPU 111 adds a shortcode to the hint information and activates the color verification preparation work delay detection timer based on the color verification preparation work time. Specifically, the time when the color verification preparation start timer signal is issued is the color verification start time. The color verification preparation delay detection timer is set so that the color verification preparation delay detection timer signal is issued when the color verification preparation work time has elapsed, starting from the time the color verification process started. In S1645, CPU 111 notifies accounts registered in the notification destination setting that have the color verification start / completion notification condition attribute enabled, via the account management backend 257, that color verification has started.

[0116] In S1651, CPU 111 requests fully automated color verification using the generated test chart from the device management backend 258. In S1652, CPU 111 sets the fully automated color verification execution time specified in the notification destination settings in the color verification settings as the color verification execution time. In S1653, CPU 111 adds a shortcode to the hint information and activates the color verification incomplete detection timer based on the color verification execution time. Specifically, the time when the color verification incomplete detection timer signal is issued is the color verification start time. The color verification incomplete detection timer is set so that the color verification incomplete detection timer signal is issued when the color verification execution time has elapsed, starting from the time the color verification process started. In S1654, CPU 111 notifies accounts registered in the notification destination settings that have the color verification start / completion notification condition attribute enabled, via the account management backend 257, that the color verification has started.

[0117] Figure 17 is a flowchart of the color verification preparation delay detection timer signal processing. In S1701, CPU 111 stops the color verification preparation delay detection timer corresponding to the received timer signal. In S1702, CPU 111 opens the color verification settings collection. In S1703, CPU 111 retrieves a list of color verification settings from the color verification collection. In S1704, CPU 111 adds the shortcode associated as hint information for the color verification preparation delay detection timer signal to the overdue-short-code attribute of the color verification setting. In S1705, CPU 111 updates the color verification setting with the color verification setting whose overdue-short-code attribute has been updated. In S1706, CPU 111 closes the color verification settings collection. In S1707, CPU 111 notifies accounts registered in the notification destination settings that have the color verification preparation delay / incomplete execution notification condition attribute enabled, via the account management backend 257, of the color verification preparation delay.

[0118] Figure 18 shows the settings screen for the colorimetric application. The settings screen for the colorimetric application includes an application switching bar 400 and a colorimetric settings view 1800. The colorimetric settings view 1800 includes a Short Code text box 1801, a "Confirm" button 1802, a settings information text box 1813, and a "Next" button 1851.

[0119] The Short Code text box 1801 is a text box for receiving the short code entered by the operator. The "Confirm" button 1802 is a button for verifying whether the short code entered by the operator is valid or not. The configuration information text box 1813 is a text box for displaying various information related to the verified short code. The "Next" button 1851 becomes pressable when the short code entered in the Short Code text box 1801 has been verified using the "Confirm" button 1802. When the CPU 132 detects that the "Next" button 1851 has been pressed, it transitions to the color measurement screen shown in Figure 19.

[0120] Figure 19 shows the color measurement screen of the color measurement application. A detailed explanation of color measurement would be extremely complicated. Therefore, since this embodiment features processing at the start and end of color measurement, we will explain the start and end timings of color measurement.

[0121] Figure 19(a) is the first page of the color measurement screen. In this embodiment, the color measurement preparation is considered complete when the color measurement screen is displayed. When the necessary color measurement is completed on the first page of the color measurement screen, the "Next" button 1911 becomes active. Then, when the CPU 132 detects that the "Next" button 1911 has been pressed, it displays the next page.

[0122] Figure 19(b) is the final page of the color measurement screen. This page includes the "Complete" button 1921. The "Complete" button 1921 is used to confirm that the color measurement is complete. When the CPU 132 detects that the "Complete" button 1921 has been pressed, the CPU 132 executes the processing of the color measurement completion flowchart, which will be described later.

[0123] Figures 20 and 21 are flowcharts of the color measurement application at the start of color measurement. The program that executes the processes in the flowchart is implemented within the color measurement application 292, and the CPU 132 executes this program. In S2001, the CPU 132 obtains the shortcode set on the settings screen from the hint information. In S2002, the CPU 132 stops the color verification preparation delay detection timer associated with the shortcode. Next, the CPU 132 executes the processes in S2003 and S2005 in parallel. In S2003, the CPU 132 sends a request to the color verification server 101 to obtain a list of color verification settings. In S2004, the CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the list of color verification settings. In S2005, the CPU 132 sends a request to the color verification server 101 to obtain a list of notification destination settings. In S2006, the CPU 132 receives a response from the color verification server 101 acknowledging the acquisition of the list of notification destination settings. CPU132 waits until both the S2004 and S2006 processes are completed.

[0124] In S2010, CPU132 branches the process based on the response to the color verification settings list acquisition. If the response is normal, the process proceeds to S2013. If the response is abnormal, the process proceeds to S2011. In S2011, CPU132 displays a color verification settings list acquisition failure popup and terminates the process in this flowchart.

[0125] In S2013, CPU132 branches the process based on the response to retrieve the list of notification destinations. If the response to retrieve the list of notification destinations is normal, the process proceeds to S2015. If the response to retrieve the list of notification destinations is abnormal, the process proceeds to S2014. In S2014, CPU132 displays a notification destination list retrieval failure popup and terminates the process in this flowchart.

[0126] In S2015, CPU132 retrieves a list of color verification settings from the response to retrieve a list of color verification settings. In S2016, CPU132 retrieves a list of notification destination settings from the response to retrieve a list of notification destination settings. In S2020, CPU132 uses the retrieved list of color verification settings to branch the process depending on whether the retrieved shortcode is registered in the scheduled-short-codes attribute of any of the color verification settings. If the retrieved shortcode is registered in the scheduled-short-codes attribute, the process proceeds to S2021. If the retrieved shortcode is not registered in the scheduled-short-codes attribute, the process proceeds to S2051.

[0127] In S2021, CPU132 determines whether the retrieved shortcode is included in the overdue-short-code attribute of any color validation setting. If the retrieved shortcode is included in the overdue-short-code attribute of any color validation setting, the process proceeds to S2022. If the retrieved shortcode is not included in the overdue-short-code attribute of any color validation setting, the process proceeds to S2031.

[0128] In S2022, CPU132 removes the acquired shortcode from the overdue-short-code attribute of the color verification settings list. In S2023, CPU132 sends a color verification settings update request to the color verification server 101 using the updated color verification settings. In S2024, CPU132 receives a color verification settings update response from the color verification server. In S2025, CPU132 branches the process based on the color verification settings update response. If the color verification settings update response is a normal response, the process proceeds to S2026. If the color verification settings update response is an abnormal response, the process proceeds to S2027. In S2026, CPU132 notifies accounts registered in the notification destination settings that have the color verification preparation delay / incomplete notification condition attribute enabled, via the account management backend 257, that color verification preparation recovery is in progress. In S2027, CPU132 displays a color verification settings update failure popup and terminates the process in this flowchart.

[0129] In S2031, CPU132 branches the process based on whether the colorimeter specified in the color verification setting supports automatic paper feeding. At this time, CPU132 identifies the color verification setting associated with the shortcode. Then, CPU132 calculates the color verification execution time based on the various settings in the notification destination setting specified in the color verification setting. If the colorimeter supports automatic paper feeding, the process proceeds to S2033. If the colorimeter does not support automatic paper feeding, the process proceeds to S2032. In S2032, CPU132 determines the color verification execution time based on the color verification execution time (manual paper feeding) in the notification destination setting. In S2033, CPU132 determines the color verification execution time based on the color verification execution time (automatic paper feeding) in the notification destination setting.

[0130] In S2034, CPU132 adds a shortcode to the hint information and activates the color verification incomplete detection timer based on the color verification execution time. Specifically, the color verification incomplete detection timer is set so that a color verification incomplete detection timer signal is issued when the color verification execution time has elapsed, starting from the time the color verification process began. In S2051, CPU132 displays the first page of the color measurement page and terminates the processing of this flowchart.

[0131] In this embodiment, the process of starting the color verification execution incomplete detection timer, which is the process from S2031 to S2034, has been described as being executed on the color verification client 131 side, but this is not limited to this configuration. This process may also be executed on the color verification server 101 side.

[0132] Figure 22 is a flowchart of the color measurement application at the completion of color measurement. The program that executes the processes in this flowchart is implemented within the color measurement application 292, and the CPU 132 executes this program. In S2201, the CPU 132 obtains the shortcode set in the settings screen from the hint information. In S2202, the CPU 132 stops the color verification execution incomplete detection timer associated with the obtained shortcode. In S2203, the CPU 132 converts the color measurement results into JSON format.

[0133] In S2211, CPU 132 sends a request to create a color verification record to color verification server 101. In S2212, CPU 132 receives a response from color verification server 101 indicating that the color verification record has been created. In S2220, CPU 132 branches the process based on the response indicating that the color verification record has been created. If the response indicating that the color verification record has been created is normal, the process proceeds to S2221. If the response indicating that the color verification record has been created is abnormal, the process proceeds to S2222. In S2221, CPU 132 switches the display to the results reference application. In S2222, CPU 132 displays a color verification record creation failure popup.

[0134] The following supplements the features of this disclosure that are evident in the embodiment described above. This disclosure has the feature of dividing a color verification task, which starts from a specified scheduled start time for color verification, into a phase for preparing for color verification and a phase for executing color verification. Each phase must be executed consecutively. Time management is made smooth by calculating the time required for each phase and linking each phase to the corresponding work time. It also has the feature of notifying both inside and outside the equipment if the work time is exceeded. In other words, it is possible to notify delays in work in a timely manner.

[0135] This disclosure offers the advantage of flexible progress management by calculating and managing work time on a phase-by-phase basis. It allows for quick sharing of delays or other issues with managers and other operators while preparing for color measurement for color verification. Furthermore, this disclosure features a mechanism that links the completion of the color verification preparation phase with the start of the color verification execution phase. In conventional technologies, dividing tasks into independent subtasks required manual input by managers or operators for subtasks whose completion could not be detected. In contrast, this disclosure divides tasks into phases that should be executed sequentially. It also features a mechanism that detects the completion of preceding phases, which the system could not detect, by the start of subsequent phases. This eliminates the need for operators to manually input color verification preparation into the color verification system.

[0136] Furthermore, the working time for the color verification preparation phase is switched depending on the method used to print the test chart for color verification. This allows administrators to automatically set the time required for color verification preparation in conjunction with the method used to print the test chart when registering a color verification schedule. In addition, the working time for the color verification execution phase can be switched depending on the method used to measure the color of the test chart. Furthermore, if color verification is to be performed fully automatically, a dedicated working time can be switched. This allows administrators to automatically set the time required for color verification execution in conjunction with the method used to measure the color of the test chart when registering a color verification schedule.

[0137] These improvements eliminate the need for administrators to re-estimate the time required for color verification for each schedule, resulting in more efficient work. Furthermore, if there is a delay in preparing for color verification, the system automatically notifies the relevant administrators and operators that the verification has been recovered when the verification is performed. This allows administrators and operators to share the fact that recovery has begun, even when multiple people are managing a single printer, before all color verification is complete.

[0138] [Second Embodiment] In the first embodiment, a configuration was described in which the driver print preparation time, direct print preparation time, color verification execution time (manual paper feed), color verification execution time (automatic paper feed), and color verification execution time (fully automatic) were set as fixed values ​​in the notification settings. In this embodiment, a configuration is described in which recommended values ​​are presented when setting the notification settings for each of these assumed times, and the notification settings are automatically set when color verification preparation or color verification is performed.

[0139] In Figure 4, the driver print preparation time is an estimated work time that includes the time required for the operator to print the test chart using the printer device. This work time will vary depending on the operator's skill level. Therefore, in S1634, the CPU 132 may sequentially save the time required for color verification preparation in the color verification performance backend 255, and calculate an appropriate recommended value for the driver print preparation time based on this performance. In the "automatic printing + manual color measurement" mode, this work time can be calculated as the difference from the start time of color verification to the time when color measurement starts with manual or automatic paper feeding. In this case, not only a simple average value may be used, but the median or the like may also be used. Various modifications of these are possible as long as they do not deviate from the spirit of this disclosure.

[0140] The direct print preparation time in Figure 4 is an estimated work time that includes the time required for the printer to automatically print the test chart at the specified time. This work time varies depending on the performance and attributes of the printer. For example, the CPU 132 can calculate an appropriate direct print preparation time from the device management service 104 according to the performance and attributes of the engine to be printed. For example, in the case of electrophotographic printing, time may be required for warming up, such as preheating the fuser. Also, in the case of inkjet printing, time may be required for drying after printing. In order to suitably implement this disclosure, the direct print preparation time may be adjusted at the timing of initiating direct printing in S1643, taking into account the attributes and performance of the device.

[0141] The color verification execution time (manual paper feeding) in Figure 4 is an estimated work time that includes the time required for the operator to measure the color of the test chart using a colorimeter and manual paper feeding. In order to suitably implement this disclosure, in S2032, the CPU 132 may sequentially save the time required to execute color verification in the color verification performance backend 255, and calculate an appropriate recommended value for the color verification execution time (manual paper feeding) based on this performance.

[0142] The color verification execution time (automatic paper feeding) in Figure 4 is an estimated work time that includes the time required for the operator to measure the color of the test chart using a colorimeter and automatic paper feeding. In order to suitably implement this disclosure, in S2033, the CPU 132 may sequentially save the time required to execute color verification in the color verification performance backend 255, and calculate an appropriate recommended value for the color verification execution time (automatic paper feeding) based on this performance.

[0143] The color verification execution time (fully automatic) in Figure 4 is an estimated work time that includes the time required for the printer to automatically perform color adjustment, test chart printing, and color measurement using an inline sensor or inspection system at a specified time. This work time varies depending on the performance and attributes of the printer, as well as the performance and attributes of the inline sensor or inspection system. For example, if the printer's printing speed is faster than the inline sensor's color measurement speed, the estimated work time is determined by the inline sensor's color measurement speed. On the other hand, if the printer's printing speed is slower than the inline sensor's color measurement speed, the estimated work time is determined by the printer's printing speed. In order to suitably implement this disclosure, the color verification execution time (fully automatic) may be adjusted at the timing of starting the color verification (fully automatic) in S1652, taking into account the attributes and performance of the device.

[0144] The above-mentioned work time (recommended value) may be displayed as reference information via a pop-up or other means when displaying the notification destination setting screen of the various setting applications 295 in Figure 4, if it does not match the current setting value. In other words, the recommended values ​​for the work time of the color verification preparation phase and the work time of the color verification execution phase may be displayed via a pop-up or other means before the color verification preparation phase is executed.

[0145] Alternatively, when performing the steps to calculate the color verification preparation work time in S1634 and S1643, or the steps to calculate the color verification execution work time in S1653, S2032, and S2033, the above work time may be dynamically replaced with the recommended work time. In other words, when executing the color verification preparation phase, the recommended value for the work time of the color verification preparation phase may be automatically set to the work time of the color verification preparation phase. Similarly, when executing the color verification execution phase, the recommended value for the work time of the color verification execution phase may be automatically set to the work time of the color verification execution phase.

[0146] As described above, the color verification preparation time and color verification execution time in this disclosure can be fixed values ​​set in advance by the administrator, or the color verification system can suggest recommended work times and automatically set the color verification preparation time and color verification execution time.

[0147] [Third Embodiment] In the first embodiment, a method was described in which delays in the preparation of color verification tasks and completion of color verification tasks are notified to a designated account via email. In this disclosure, operators and others can also be notified using notification means other than email.

[0148] In S1707 or S1572, when the CPU 111 requests the account management service 103 to send a notification of delay in color verification preparation or a notification of incomplete color verification execution, it may simultaneously send the same notification to the device management service 104. The device management service 104 requests various warning displays from the controller 151 and controller 160. These variations will be described in detail.

[0149] Figure 23(a) shows examples of various warning displays on the device-side UI. For example, when the controller 151 receives a warning display request, it requests the printer 150 to light up or blink the warning display LED 2302 provided on the device UI 156. This allows an operator who can see the warning display LED 2302 on the printer 150 to notice that some kind of warning has been issued by the printer 150. The controller 151 also requests the printer 150 to display a warning message 2301 on the device UI 156. This allows the operator to understand the details of the warning occurring on the printer 150 via the device UI 156.

[0150] Figure 23(b) shows an example of a display showing various warnings using a device-side warning light. Depending on the installation location, the operator may not be able to see the device UI156 from a distance. Therefore, a warning light 2310 that can be seen from an even greater distance may be installed on the device UI156. The operator may be notified that a warning has been issued by the illumination or flashing of the warning indicator LED 2311.

[0151] The above describes an example of displaying various warnings on the printer's UI. However, this disclosure also allows for displaying various warnings on the controller's UI. For example, a warning display request to controller 160 may be displayed on controller UI 161. These various modifications are applicable without departing from the spirit of this disclosure.

[0152] Figure 24(a) shows an example of displaying a color verification incomplete warning on the color verification settings application screen. When CPU 111 requests a color verification preparation delay notification or a color verification execution incomplete notification from account management service 103 in S1707 or S1572, it may simultaneously send the same notification to color verification client program 290. CPU 132 displays the warning as a pop-up dialog on the screens displayed by various applications.

[0153] The warning popup 2401 is superimposed on the normal color verification settings screen, allowing operators to see the warning even while performing other tasks. The schedule button 2402 is used to switch the color verification settings screen to the schedule mode described later.

[0154] Figure 24(b) shows an example of the display in schedule mode. The color verification setting application 291 may have a schedule mode in order to provide an overview of the scheduled start time of color verification tasks. In schedule mode, the start time and status of color verification tasks are displayed for each time period. Color verification task 2411 is a color verification task whose color verification result is Passed. Color verification task 2412 is a color verification task whose color verification result is Failed. Color verification task 2421 is a color verification task that is in a color verification preparation delay state. Color verification task 2422 is a color verification task that is in a color verification execution incomplete state. In this disclosure, the representation of color verification tasks is separated into color verification preparation delay state and color verification execution incomplete state. This allows the operator to clearly determine what needs to be done for the color verification task when checking the schedule mode.

[0155] Figure 25(a) shows an example of displaying the color verification task status on the application switching button. The status of some color verification tasks may be displayed on the color verification setting button 2610 on the application switching bar 400. For example, the color verification task closest to the current time can be selected for display.

[0156] Figure 25(b) shows an example of the display of the color verification setting button 2510 when there is a delay in color verification preparation. The color verification setting button 2510 includes the target printer 2511, the color verification phase status 2512, and the color verification phase time information 2513. The target printer 2511 displays the name of the printer being targeted for the color verification. The color verification phase status 2512 displays the status of the color verification phase. The color verification phase time information 2513 displays the time when the state of the color verification phase changed. Figure 25(c) shows an example of the display of the color verification setting button 2510 when color verification is not yet complete. Figure 25(c) shows almost the same content as Figure 25(b), so details are omitted. In this way, the progress status of each phase can be displayed in the area that displays supplementary information about the application while the application is running.

[0157] As described above, when displaying the color verification task status on the application switching button, it is possible to display the status in a way that clearly indicates whether the color verification task is experiencing a delay in preparation or whether the color verification is not yet completed.

[0158] In addition to the above, the color verification preparation delay notification and color verification execution incomplete notification in this disclosure may also be sent to an external tool. The Web Server 250 in the first embodiment assumed Web API communication. Other protocols may be supported. The Web Server 250 may support SNMP (Simple Network Management Protocol) or IPP (Internet Printing Protocol), for example. Alternatively, the Web Server 250 may support JMF (Job Messaging Format). Furthermore, the Web Server 250 may support REST API (Representational State Transfer API). Modifications of these format types are extensible as long as they do not deviate from the spirit of this disclosure.

[0159] By leveraging these protocol extensions, for example, a color verification preparation delay notification or a color verification execution incomplete notification can be displayed on a mobile application running on a mobile phone 123 used by an operator. The means of displaying the notified information can be modified as long as it does not deviate from the spirit of this disclosure.

[0160] Furthermore, in the case of manual printing, for example, where print data for a test chart executed during period 302 in Figure 3 is acquired and printed using a printer driver, the color verification system may not detect the completion event of manual printing. In such cases, when the color verification system detects the start of a subsequent phase, such as manual or automatic color measurement, it determines that it has detected the completion event of the preceding phase. That is, if there is no event indicating the completion of the preceding phase, and the color verification system detects an event indicating the start of a subsequent phase, the color verification system considers the preceding phase to be complete. In other words, the start event of a subsequent phase also becomes the completion event of the preceding phase.

[0161] This disclosure can also be implemented by supplying a program that implements one or more of the functions of the embodiments described above to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0162] The above-described embodiments include the following configurations.

[0163] (Configuration 1) A color verification system for managing a color verification task, comprising: management means for dividing the color verification task into two or more phases including a first phase and a second phase; linking means for linking the first phase to a first work time and the second phase to a second work time; and notification means for notifying the user that the work of the first phase is incomplete if the first work time has elapsed and the completion event of the first phase has not been detected.

[0164] (Configuration 2) The color verification system according to Configuration 1, characterized in that the two or more phases are performed consecutively.

[0165] (Configuration 3) The color verification system according to Configuration 1, characterized in that the first phase is a color verification preparation phase, the second phase is a color verification execution phase, and the first phase is executed prior to the second phase.

[0166] (Configuration 4) The color verification system according to Configuration 3, characterized in that if there is no work completion event for the first phase, the start event for the second phase is used as the work completion event for the first phase.

[0167] (Configuration 5) The color verification system according to Configuration 3 or 4, characterized in that when the printing means manually prints the test chart used in color verification, the management means determines the working time of the color verification preparation phase based on the time required for manual printing of the test chart, and when the printing means automatically prints the test chart used in color verification, the management means determines the working time of the color verification preparation phase based on the time required for automatic printing of the test chart.

[0168] (Configuration 6) The color verification system according to Configuration 3 or 4, characterized in that the management means determines the working time of the color verification execution phase based on the time required to measure the test chart by manual feeding if the color measuring means for measuring the test chart used in color verification does not support automatic paper feeding, and determines the working time of the color verification execution phase based on the time required to measure the test chart by automatic paper feeding if the color measuring means supports automatic paper feeding.

[0169] (Configuration 7) The color verification system according to Configuration 3 or 4, characterized in that the management means presents the notification means with recommended values ​​for the working time of the color verification preparation phase and the working time of the color verification execution phase before the color verification preparation phase is executed.

[0170] (Configuration 8) The color verification system according to Configuration 3 or 4, characterized in that the management means automatically sets the recommended value for the work time of the color verification preparation phase to the work time of the color verification preparation phase when executing the color verification preparation phase, and automatically sets the recommended value for the work time of the color verification execution phase to the work time of the color verification execution phase when executing the color verification execution phase.

[0171] (Configuration 9) The color verification system according to Configuration 3, characterized in that, when both the first phase and the second phase are performed automatically, the management means does not divide the color verification task into the first phase and the second phase, but determines the working time of the color verification execution phase based on the time required for automatic color verification.

[0172] (Configuration 10) The color verification system according to any one of Configurations 1 to 8, characterized in that the notification means notifies a registered recipient of a delay in the first or second phase using email.

[0173] (Configuration 11) The color verification system according to any one of Configurations 1 to 8, characterized in that the notification means temporarily displays the delay of the first phase or the second phase on a display device by pop-up while the application is running.

[0174] (Configuration 12) The color verification system according to any one of Configurations 1 to 8, characterized in that the notification means displays the delay of the first phase or the second phase in an area that displays supplemental information of the application while the application is running.

[0175] (Configuration 13) The color verification system according to Configuration 5, characterized in that the notification means displays a user interface screen that notifies of the delay of the first phase or the second phase via a user interface installed on the printing means or on a user interface installed on a controller connected to the printing means.

[0176] (Configuration 14) The color verification system according to Configuration 5, characterized in that the notification means notifies of a delay in the first phase or the second phase by lighting up or flashing an LED or warning light installed on the printing means.

[0177] (Configuration 15) A control method for a color verification system that manages a color verification task, comprising the steps of: dividing the color verification task into two or more phases including a first phase and a second phase and managing them; associating the first phase with a first work time and the second phase with a second work time; and notifying the user that the work of the first phase is incomplete if the completion event of the first phase is not detected and the first work time has elapsed.

[0178] (Configuration 16) A color verification server for managing a color verification task, comprising: management means for dividing the color verification task into two or more phases including a first phase and a second phase; linking means for linking the first phase to a first work time and the second phase to a second work time; and notification means for notifying the user that the work of the first phase is incomplete if the first work time has elapsed and the completion event of the first phase has not been detected.

[0179] (Configuration 17) A program to cause the computer to function as the color verification server described in Configuration 16.

Claims

1. A color verification system for managing color verification tasks, A management means for dividing the aforementioned color verification task into two or more phases, including a first phase and a second phase, A linking means that links the first phase to the first work time and the second phase to the second work time, If the completion event for the first phase is not detected and the first work time has elapsed, a notification means for notifying the user that the work for the first phase is incomplete, A color verification system characterized by having the following features.

2. The color verification system according to claim 1, characterized in that the two or more phases are performed in succession.

3. The first phase is the color verification preparation phase, The second phase is the color verification execution phase, The first phase is performed prior to the second phase. The color verification system according to feature 1.

4. The color verification system according to claim 3, characterized in that if there is no completion event for the first phase, the start event for the second phase is used as the completion event for the first phase.

5. The aforementioned management means is If the printing means manually prints the test chart used in color verification, the working time for the color verification preparation phase shall be determined based on the time required for manual printing of the test chart. When the printing means automatically prints the test chart used in color verification, the working time for the color verification preparation phase is determined based on the time required for automatic test chart printing. The color verification system according to feature 3.

6. The aforementioned management means is If the colorimetric means used to measure the color of the test chart in color verification does not support automatic paper feeding, the working time for the color verification execution phase shall be determined based on the time required to measure the color of the test chart by manual paper feeding. If the colorimetric means supports automatic paper feeding, the working time for the color verification execution phase is determined based on the time required to measure the color of the test chart using automatic paper feeding. The color verification system according to feature 3.

7. The color verification system according to claim 3, characterized in that the management means presents the notification means with recommended values ​​for the working time of the color verification preparation phase and the working time of the color verification execution phase before the color verification preparation phase is executed.

8. The color verification system according to claim 3, characterized in that the management means automatically sets a recommended value for the work time of the color verification preparation phase when executing the color verification preparation phase, and automatically sets a recommended value for the work time of the color verification execution phase when executing the color verification execution phase.

9. If both the first and second phases are performed automatically, The management means determines the working time of the color verification execution phase based on the time required for automatic color verification, without dividing the color verification task into the first phase and the second phase. The color verification system according to feature 3.

10. The color verification system according to claim 1, characterized in that the notification means notifies a registered recipient of the delay in the first or second phase using email.

11. The color verification system according to claim 1, characterized in that the notification means temporarily displays the delay of the first or second phase on a display device by pop-up while the application is running.

12. The color verification system according to claim 1, characterized in that the notification means displays the delay of the first or second phase in an area that displays supplemental information of the application while the application is running.

13. The color verification system according to claim 5, characterized in that the notification means displays a user interface screen that notifies of the delay of the first phase or the second phase via a user interface installed on the printing means or on a user interface installed on a controller connected to the printing means.

14. The color verification system according to claim 5, characterized in that the notification means notifies of a delay in the first phase or the second phase by lighting up or flashing an LED or warning light installed on the printing means.

15. A control method for a color verification system that manages color verification tasks, A process of dividing the aforementioned color verification task into two or more phases, including a first phase and a second phase, and managing them accordingly. A process of linking the first phase to the first work time and the second phase to the second work time, If the completion event for the first phase is not detected and the first work time has elapsed, the process includes notifying the user that the work for the first phase is incomplete. A control method for a color verification system, characterized by having the following features.

16. A color verification server that manages color verification tasks, A management means for dividing the aforementioned color verification task into two or more phases, including a first phase and a second phase, A linking means that links the first phase to the first work time and the second phase to the second work time, If the completion event for the first phase is not detected and the first work time has elapsed, a notification means for notifying the user that the work for the first phase is incomplete, A color verification server characterized by having the following features.

17. A program for causing a computer to function as a color verification server as described in claim 16.

Images