Insertion of printer operator instructions onto separator pages in a print shop environment

Systems and methods are provided for notifying operators of tasks to perform on printers by inserting operator instructions onto separator pages that are placed between print jobs. One embodiment is a print server that includes a control system and a page generator. The control system is operable to identify a print job, and to identify an operator instruction for the print job indicating a physical task for an operator to perform on a printer before the print job is printed. Also, the control system holds the print job responsive to identifying the operator instruction. The page generator generates a separator page comprising the operator instruction that indicates the physical task to perform on the printer, and transmits the separator page for printing to inform the operator of the task before the print job is printed.

FIELD OF THE INVENTION

The invention relates to the field of printing, and in particular to instructing printer operators in print shop environments.

BACKGROUND

Print shops are typically medium or large scale facilities capable of supplying printing services to meet a variety of customer demands. For example, print shops are often used to print documents used for mass-mailing (e.g., customer bills, advertisements, etc). Because print shops engage in printing on a scale that is hard to match, their customer base is usually varied. Print shop clients may therefore include both large institutional clients (e.g., credit card companies and banks), and small clients (e.g., small businesses and churches).

Print shops are generally arranged to print incoming jobs from clients in a way that is economical, yet fast. Thus, print shops often include a number of high-volume printers capable of printing incoming jobs quickly and at high quality. Print shops also typically include post-processing devices that are used to process the printed documents of each job (e.g., stackers, staplers, cutters, binders, etc.). Because print shops serve a variety of clients, they are often tasked with printing jobs that have varying printing formats, delivery dates, and media requirements. Print shops therefore often use a centralized print server that coordinates activity between printers of the print shop and clients. The print server schedules incoming jobs and forwards them to the printers they are directed to.

The printers of a print shop may be managed by operators who setup printers, oversee print jobs, remove paper jams, stack or cut printed pages of print jobs, or move printed documents of print jobs to various locations within the print shop. These activities may be performed while the printer is still printing jobs from the print server. As the printer is printing, it may be desired to perform tasks on the printer such as loading it with media or ink. However, a printer operator's activities prevent them from constantly monitoring the printer.

Printer operators therefore desire to be informed of upcoming tasks to be performed on a printer while they are engaged in their daily activities. Tasks to be performed may include loading the printer with media or ink, or calibrating a printer before a print job is printed. If a printer is not set up correctly, it may print the documents of a print job using the wrong media or ink. If documents are printed improperly, time and resources are wasted because the print job will be re-printed.

SUMMARY

Embodiments described herein identify operator instructions for a printer that relate to incoming print jobs, and provide these instructions to printer operators. Printer operators may then execute the tasks indicated by the operator instructions to ensure that incoming jobs are printed correctly. Operator instructions may be provided with printed separator pages (printed pages used to separate physical printed documents), or may be provided at a user interface. Thus, a printer operator is informed of tasks to perform on the printer even though they may be unable to continuously monitor it.

One embodiment includes a print server operable to insert operator instructions onto separator pages. The print server includes a control system and a page generator. The control system is operable to identify a print job, and to identify an operator instruction for the print job indicating a physical task for an operator to perform on a printer before the print job is printed. Also, the control system holds the print job responsive to identifying the operator instruction. The page generator generates a separator page comprising the operator instruction that indicates the physical task to perform on the printer, and transmits the separator page for printing to inform the operator of the task.

Another embodiment comprises a print server for displaying operator instructions. The print server comprises a control system, a display generator, and a user interface. The control system is operable to identify a print job, to identify an operator instruction for the print job indicating a physical task for an operator to perform on a printer before the print job is printed, and to hold the print job responsive to identifying the operator instruction. The display generator is operable to generate a display comprising the operator instruction, and to transmit the display. The user interface is operable to receive the transmitted display and to present the display to inform an operator of the physical task to be performed.

Other exemplary embodiments may be described below.

DETAILED DESCRIPTION

FIG. 1is a block diagram illustrating a print shop architecture102in an exemplary embodiment. Print shop architecture102couples one or more clients130-132to one or more printers126-128to provide printing and print workflow services to clients130-132. Print shop architecture102is operable to receive print jobs and job tickets from clients130-132for printing on printers126-128. Clients130-132may include banks, credit card companies, or other entities with printing needs (e.g., monthly bank statements, monthly credit card bills, etc.). Print shop architecture102may receive print jobs from clients130-132in a number of different formats, such as Portable Document Format (PDF), Mixed Object: Document Content Architecture (MO:DCA), etc. Job tickets may be received from clients130-132in a number of different formats, such as Job Definition Format (JDF), Print Production Format (PPF), Portable Job Ticket Format (PJTF), etc. Printers126-128generally include systems for transforming print data onto a suitable printable medium, such as paper, and generally are large production printing systems for high volume printing.

Print shop architecture102includes a print server104having one or more virtual printers106-108. Virtual printers106-108communicate with clients130-132and provide an interface similar to a printer driver to allow clients130-132to set up print jobs and send print jobs (and job tickets associated with the print jobs) to print shop architecture102. When clients130-132send print jobs and job tickets to print shop architecture102, the job tickets are scanned into a database124located in storage120of print shop architecture102. The print jobs are then stored in a print spool122of storage120as open jobs prior to queuing the print jobs for printing. A scheduler116identifies the open jobs located in print spool122and attempts to schedule the jobs at a queue of one or more printer objects110-112. Typically, scheduler116attempts to schedule the open jobs at one of printer objects110-112corresponding with virtual printers106-108that received the print job. For example, if client130transmitted the print job to virtual printer106, then scheduler116may first attempt to place the print job at a print queue of printer object110. Generally, printer objects110-112interface with corresponding printers126-128to queue and process print jobs prior to transmitting the jobs to printers126-128.

A printer operator may use a user interface of print shop architecture102to control and identify the status of jobs at print shop architecture102. For example, user interface118may provide a list of print jobs in queues of printer objects110-112and other general information about the status of open jobs in print spool122.

The printer operator may also use a job ticket editor114to modify job tickets associated with both open and queued print jobs. Using job ticket editor114, the printer operator may modify job tickets to change various print options for a print job associated with the job ticket, such as duplexing, stapling, media type, etc.

Print shop architecture102provides a number of printing and workflow services to clients130-132which will become more readily apparent through the following discussion and related figures.FIGS. 2-6will discuss embodiments of print shop architectures that are able to identify instructions relating to a print job and provide them to a printer operator via a printed separator page or user interface.

FIG. 2is a block diagram including a task instruction system220in an exemplary embodiment. Task instruction system220is implemented in print server104, but could be implemented in other systems or devices. Task instruction system220is operable to identify print jobs from client130and identify operator instructions related to the print jobs. Task instruction system220is also operable to direct printer126to display operator instructions on printed separator pages. By sending instructions to operators via printed separator pages, task instruction system220ensures that operators remain informed of physical tasks to perform in the print shop. Printer operators may then configure printers so that incoming print jobs are properly printed.

In this embodiment, task instruction system220includes a control system222and a page generator224. Control system222comprises any system, device, or component operable to process print jobs and operator instructions. Operator instructions indicate physical tasks to be performed on a printer, which may include adjusting physical settings of printer126(e.g., altering the print quality and/or speed of printer126), calibrating printer126(e.g., aligning or cleaning print heads of printer126), loading printer126with media or ink, replacing the stacker of printer126(stackers are typically storage devices that hold or sort printed pages of a print job), carrying out post-processing operations on printed documents, etc. Page generator224comprises any system, device, or component operable to generate a separator page that includes an operator instruction.

When in operation, print server104receives print jobs from clients130-132. Print server104queues these incoming print jobs at printer objects110-112for printing from printers126-128. At this point, task instruction system220may process the print jobs at printer objects110-112to identify operator instructions related to each job, and to direct printer126to create printed separator page240having operator instructions242.

FIG. 3is a flowchart illustrating a method300for inserting operator instructions onto separator pages in an exemplary embodiment. The steps of method300are described with reference to task instruction system220ofFIG. 2, but those skilled in the art will appreciate that method300may be performed in other systems. The steps of the flowcharts described herein are not all inclusive and may include other steps not shown. The steps described herein may also be performed in an alternative order.

At step302, control system222identifies a print job. Any print job may be identified within a printing queue of printer126. Print jobs may be identified, for example, by an index number associated with the print job.

At step304, control system222identifies one or more operator instructions for the print job indicating a physical task to be performed on printer126before the print job is printed. In one embodiment, control system222identifies an operator instruction by reading input from user interface118that specifies a task to be performed. In another embodiment, control system222identifies an operator instruction by analyzing the properties of incoming print jobs and comparing them to the current configuration of printer126. For example, control system222may identify the number of pages in a print job, and may also identify the number of pages loaded in printer126. Control system222may then determine that there are fewer pages loaded in the printer than are used for the print job. Thus, control system222determines that this difference between the properties of the print job and the configuration of printer126could keep the print job from printing correctly, and generates an operator instruction to load printer126with more paper, based upon this difference.

At step306, control system222holds the print job in response to identifying an operator instruction. Holding a print job is desirable because it prevents the print job from printing on printer126when the printer is not properly configured to print the job. Holding the print job does not necessarily stop all printing on printer126. Instead, printer126can continue printing jobs that are not affected by the instruction (e.g., if an operator instruction indicated that red paper should be loaded, jobs that did not use red paper could still be printed on printer126regardless of whether the task was performed).

At step308, page generator224generates a separator page comprising the operator instruction indicating the task to be performed on printer126. The operator instruction may be generated within the separator page as a textual or graphical element. In one embodiment, page generator224generates the operator instruction so that it is accompanied by a special graphic (e.g., an exclamation point or a print shop letterhead) indicating the nature of the task. In another embodiment, page generator224indicates that the separator page should be printed on media with a different color or size than the print jobs it will be placed before or after. Altering the way that operator instructions are displayed on a printed separator page helps an operator to identify and categorize incoming instructions.

At step310, page generator224transmits the separator page for printing. The separator page may be transmitted just before the print job it relates to, or may be transmitted with other print jobs that will be printed earlier. Transmitting the separator page with earlier print jobs may give a printer operator more time to perform a physical task on printer126.

Generally, page generator224transmits the separator page to printer126. However, printer126may be unavailable to print the separator page (e.g., printer126may encounter a paper jam). Here, page generator224transmits the separator page to printer127for printing. In this case, the operator instructions in the transmitted separator page direct the printer operator to perform the task on printer126.

Printer126receives the separator page and prints printed separator page240, which includes operator instructions242. The printer operator, informed of the physical task, may then complete the task. Once the task indicated by the operator instruction on printed separator page240has been performed, control system222may receive a confirmation that the task has been performed. The printer operator may provide the confirmation, or printer126may provide the confirmation after detecting successful completion of the task. For example, printer126may detect that it has been loaded with new media or ink (as required by an operator instruction) and send a confirmation to control system222.

Control system222may then release the held print job responsive to receiving the confirmation, allowing printer126to print the print job. Thus, according to the embodiments described above, operator instructions are identified that relate to incoming print jobs, and these instructions are provided to printer operators. Printer operators are then informed of tasks to perform (even though they may be continuously monitoring the printer), and may then execute the tasks indicated by the operator instructions to ensure that incoming jobs are printed correctly. At the same time, print jobs related to the operator instructions are held so that they are not sent for printing until the printer is properly configured.

Additional features will now be described in an example of inserting operator instructions onto a separator page. In this example, control system222is incorporated into virtual printer106. Client130provides a print job to control system222. Control system222parses properties of the print job to determine the type of media that the print job uses. Next, control system222queries printer126, and determines that the trays of printer126are loaded with a different type of media than used by the print job. Control system222determines, based on the report, that printer126lacks the media desired by the print job. Thus, control system222generates an operator instruction indicating that media for the print job should be loaded onto printer126before the print job is printed.

Control system222assigns the operator instruction to the print job by associating an index number of the print job with the operator instruction, and holds the print job from being printed. The operator instruction assigned to the print job is then viewed whenever a user selects the print job via user interface118. Page generator224receives the operator instruction from control system222and generates a separator page with the operator instruction indicating that the printer should be loaded with new media. Page generator224transmits the separator page to printer126. Printer126creates printed separator page240having operator instructions242. Printed separator page240uniquely distinguishes itself from print jobs on printer126by having a paper size, paper color, ink color, graphic or watermark that is distinct from the pages of these print jobs.

A printer operator receives printed separator page240, identifies the operator instruction indicating that printer126is to be loaded with new media, and loads printer126with the media. Printer126uses internal sensors to detect that it has been loaded with the appropriate media, and reports that the task has been performed. Upon receiving confirmation that the task specified by the operator instruction has been performed, control system222releases the held print job. Control system222releases the held print job by adding the print job to a queue for printer126, and then transmitting the print job to printer126. As an alternative, task instruction system220may generate a display that comprises the instruction, and display it to the printer operator via user interface118. Additional exemplary details of this alternative will be described below with regard toFIG. 4.

FIG. 4is a block diagram of a task instruction system220that includes a display generator402in an exemplary embodiment. Display generator402creates displays that include operator instructions, and transmits these displays to user interface118. User interface118comprises any system, component, or device operable to receive displays and present them to a user. Further, user interface118is operable to receive a confirmation that an operator has completed a task. Further details of the operation of user interface118will be discussed with regard toFIG. 5.

FIG. 5is a flowchart illustrating a method500for displaying operator instructions at a user interface118in an exemplary embodiment. The steps of method500are described with reference to task instruction system220ofFIG. 2and user interface118ofFIG. 4, but those skilled in the art will appreciate that method500may be performed in other systems.

Steps502-506of method500may be performed in a similar fashion to steps302-306of method300described above. At step502, task instruction system220identifies a print job. Task instruction system220identifies an operator instruction for the print job indicating a task to be performed on a printer at step504. At step506, task instruction system220holds the print job, and at step508, display generator402generates a display that includes the operator instruction. Display generator402transmits the display to user interface118at step510, and at step512the display is presented at user interface118as a notification to a printer operator. User interface118may display the operator instruction as a graphic element, a textual element, or any combination thereof. Furthermore, the graphics displayed at user interface118may indicate the nature or urgency of the task to be performed. In addition to displaying the operator instruction, user interface118provides a dialog allowing the user to indicate that they have successfully completed the task. This dialog may be a simple check-box or button, or may include multiple parameters allowing an operator to indicate how the task was completed (e.g., the number of sheets of paper that have been loaded into the printer, size of the paper, etc.).

In one embodiment, control system222stores print jobs in a printing queue that may be accessed by user interface118. Control system222associates print jobs of the queue with related operator instructions. Control system222then displays the associated operator instruction to a user whenever a print job is selected for viewing via user interface118.

Embodiments disclosed herein can take the form of software, hardware, firmware, or various combinations thereof. In one particular embodiment, software is used to direct a processing system of task instruction system220to perform the various operations disclosed herein.FIG. 6is a block diagram depicting a processing system600that is operable to perform the above operations by executing programmed instructions tangibly embodied computer readable storage medium612. In this regard, embodiments of the invention can take the form of a computer program accessible via the computer readable storage medium612providing program code for use by a computer or any other instruction execution system. For the purposes of this description, a computer readable storage medium612can be anything that can contain or store the program for use by the computer.

The computer readable storage medium612can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor device. Examples of the computer readable storage medium612include a solid state memory, a magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk, and an optical disk. Current examples of optical disks include compactdisk -read only memory (CD-ROM), compact disk-read/write (CD-R/W), and DVD.

The processing system600, being suitable for storing and/or executing the program code, includes at least one processor602coupled to memory elements604through a system bus650. The memory elements604can include local memory employed during actual execution of the program code, bulk storage, and cache memories that provide temporary storage of at least some program code and/or data in order to reduce the number of times the code and/or data are retrieved from bulk storage during execution.

Input/output or I/O devices606(including but not limited to keyboards, displays, pointing devices, etc) can be coupled to the system either directly or through intervening I/O controllers. Network adapter interfaces608may also be coupled to the system to enable the computer system600to become coupled to other data processing systems or storage devices through intervening private or public networks. Modems, cable modems, IBM Channel attachments, SCSI, Fibre Channel, and Ethernet cards are just a few of the currently available types of network or host interface adapters. Presentation device interface610may be coupled to the system to interface to one or more presentation devices, such as printing systems and displays for presentation of presentation data generated by processor602.