JP5367130B2 - Data processing apparatus, data processing method, and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To adaptively use an in-line finisher and a near line finisher. <P>SOLUTION: In a case where a user sets to prioritize a use of a near line finisher 106, when processing a print job using an in-line finisher 205, the data processing device divides the print job using the in-line finisher 205 into a print job to be executed in the in-line finisher 205, and a print job to be executed in the near-line finisher 106. On the other hand, in a case where the user sets to prioritize a use of the in-line finisher 205, when processing a print job using the near line finisher 106, the data processing device integrates a part to be executed in the in-line finisher 205 with a part to be executed in the near line finisher 106 and converts the print job into one for the in-line finisher 205. <P>COPYRIGHT: (C)2013,JPO&amp;INPIT

Description

The present invention relates to a data processing apparatus, a data processing method, and a computer program, and is particularly suitable for use in post-processing after printing.

In recent years, with the increase in the speed and image quality of electrophotographic printing apparatuses and inkjet printing apparatuses, a print generation method called Print On Demand has been developed against the conventional offset printing industry. It is rising. This print-on-demand (referred to as POD in the following description) can handle a job of a relatively small lot compared to a job handled by a conventional offset printing apparatus with a short delivery time without using a large-scale apparatus or system. Is aimed at.
The POD market realizes digital printing using electronic data by making the best use of digital image forming devices such as digital copiers and digital multifunction peripherals, and uses the final product obtained by digital printing as a product. It is a market. In such a POD market, compared with the conventional printing industry, digitization has been integrated into the system, and management and control using a computer have been permeating.

The following system is considered as a POD system for the purpose of integrating such digitization with existing printing apparatuses.
That is, a POD system including an inline finisher and a nearline finisher is considered. An inline finisher is a finishing device provided in a digital multi-function peripheral (physically connected to (for example, built-in) the digital multi-function peripheral), and automatically outputs the output from the digital multi-function peripheral without user assistance. This is a finishing apparatus that performs a post process. On the other hand, the nearline finisher is a finishing device that is not included in the digital multi-function peripheral (not physically connected to the digital multi-function peripheral) but can communicate with the digital multi-function peripheral. When the output product from the digital multi-function peripheral is set manually by the user, the nearline finisher performs a post-process on the output product.
In such a POD system, when a post-process such as case binding specified by a print job cannot be performed with the function and capability of the inline finisher, the user usually carries a paper document to the nearline finisher apparatus.

As a conventional technology of a system using a nearline finisher, there is a technology for physically printing a job ticket described in advance so that an operator can understand a work instruction on the nearline finisher device on an output from a digital multifunction peripheral. .
In addition, a job ID for uniquely identifying a job is drawn and output on a physical sheet with a barcode. There is a technique in which a barcode drawn on a physical sheet is read by a barcode reader attached to the nearline finisher device, and a job ID based on the barcode is compared with a job ID previously sent to the nearline finisher.

  Further, there is a technique described in Patent Document 1 as a technique for using a digital multi-function peripheral equipped with an inline finisher and a nearline finisher in combination. In this technique, the work load of inline finishing of a digital multi-function peripheral is distributed / represented to one or a plurality of near-line finishers connected to a network to improve the overall work efficiency.

JP 2006-309319 A

However, the conventional technology described above has the following problems when it is intended to generate a printed material that has been subjected to a post-process such as case binding as a final product.
In other words, the output product from the inline finisher is configured to obtain the only product that is bound and bound. For this reason, a job generated with the intention of performing a post-process by a post-processing machine (inline finisher) included in the digital multi-function peripheral includes data on the cover and the text. Therefore, in the conventional technique, it is impossible to generate two products, a cover and a body, from the job, and change the product to a job to be post-processed by the nearline finisher. That is, there is a problem in that a job once generated with the intention of processing with an inline finisher cannot be changed to processing using a nearline finisher.

  For example, when the case binding process is performed, the final product is a result of the case binding process. For this reason, it is instructed that a product generated from a job created with the intention of an inline finisher provided in the digital multi-function peripheral is a single final product, and a single paper discharge destination. On the other hand, in order to create a product that has been subjected to the case binding process with the near-line finisher, the operator needs to set the near-line finisher by distinguishing the cover and the text and perform the case binding process. For this reason, the output from the digital multifunction peripheral needs to be correctly classified into the cover and the body. However, as described above, in the prior art, a job generated with the intention of processing with an inline finisher cannot be changed to processing using a nearline finisher. For this reason, when a job using an inline finisher is generated, there is a problem that it is difficult to execute the job with a nearline finisher.

  Further, conversely, the “delivered product from a digital multi-function peripheral” in a job intended to generate a final product using a nearline finisher is two deliverables consisting of a cover and a body. Therefore, in the prior art, this job cannot be converted into a job for an inline finisher that requires only one final product. For this reason, when a job using the nearline finisher is generated, there is a problem that it is difficult to execute the job with the inline finisher.

  The present invention has been made in view of such a problem, and it is possible to adaptively use a post-processing device (inline finisher) included in the printing apparatus and a post-processing device (near line finisher) not included in the printing apparatus. The purpose is to.

  The data processing apparatus of the present invention may use a selection unit that selects whether or not to use a post-processing device that is not connected to a printing device via a paper conveyance path, and the post-processing device is used by the selection unit. If selected, a setting screen for selecting both a cover discharge destination and a body discharge destination is displayed, and if the use of the post-processing device is not selected by the selection unit, Display control means for displaying on the display device a setting screen for selecting a delivery destination for the deliverable for which the post-processing has been executed, and printing when the selection means uses the post-processing device. When the job is transmitted to the printing apparatus and the post-processing job is transmitted to the post-processing apparatus, and the use of the post-processing apparatus is not selected by the selection unit, the post-processing content and the print processing content are described. Taji Characterized in that it comprises transmitting means for transmitting the blanking to the printing apparatus.

  According to the present invention, a post-processing device that performs post-processing on an output product from a printing device without helping the user and an output product from the printing device are set by the user according to settings by the user. This makes it possible to adaptively use a post-processing device that performs post-processing on the output product.

1 is a diagram illustrating an exemplary configuration of a printing system according to an exemplary embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a workflow of a printing system according to an exemplary embodiment of the present invention. 1 is a block diagram illustrating an example of a configuration of a JDF job controller according to an embodiment of the present invention. FIG. 6 is a diagram conceptually illustrating an example of a job ticket (JDF job) when instructing case binding printing according to the embodiment of this invention. FIG. 4 is a diagram schematically illustrating a job ticket (JDF job) from the aspect of process processing according to the embodiment of this invention. It is a figure which shows embodiment of this invention and shows the 1st example of the user interface which a user interface part outputs. It is a figure which shows embodiment of this invention and shows the 2nd example of the user interface which a user interface part outputs. It is a figure which shows embodiment of this invention and shows an example of the table which stores a setting value. 6 is a flowchart illustrating an example of an overall outline of processing performed by a JDF job controller according to the embodiment of this invention. 10 is a flowchart illustrating an example of details of job interpretation processing in step S701 according to the embodiment of this invention. It is a flowchart which shows embodiment of this invention and demonstrates an example of the detail of the conversion method determination process of step S702. It is a flowchart which shows embodiment of this invention and demonstrates an example of the detail of the JDF edit process of step S703. 12 is a flowchart illustrating an example of details of job transmission processing in step S704 according to the embodiment of this invention. FIG. 9 is a diagram conceptually illustrating an example of a procedure of a pre-stage process of a process of dividing a print job (job ticket) according to the embodiment of this invention. 5 is a diagram illustrating an example of a JDF job (job ticket) transmitted to the MFP 103 and an example of a JDF job (job ticket) transmitted to the nearline finisher 106 according to the embodiment of this invention. FIG. FIG. 5 is a diagram illustrating an example of a cover job ticket and a body job ticket according to an embodiment of the present invention. FIG. 10 is a diagram conceptually illustrating an example of a processing procedure for integrating the near-line finisher process group into the in-line finisher 205 process group according to the embodiment of this invention. 2 is a diagram illustrating an example of a hardware configuration of a job generation PC, a workflow management server, and an MFP. FIG.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram illustrating an example of the configuration of a printing system.
In FIG. 1, the printing system includes a job generation PC 101, a workflow management server 102, a digital multi-function peripheral (referred to as MFP in the following description) 103, and a nearline finisher system 104.
The job generation PC 101 is a computer for generating a print job desired by the user. The workflow management server 102 divides the print job received from the job generation PC 101 into each work process for completing the print job, and transmits the print job for each work process to the MFP 103 and the nearline finisher system 104. The print job includes print data (for example, content data such as PDF) used for printing and setting information (for example, JDF) used for printing / post-processing. The print data may be acquired by the MFP 103 from the reference destination described in the JDF.

  Here, the MFP 103 is a print device such as a monochrome MFP or a color MFP, and plays a role of printing out in accordance with a print job work instruction received from the workflow management server 102. Further, the MFP 103 itself can perform post-processes such as case binding processing. However, when the functions and capabilities of the inline finisher provided in the MFP 103 (for example, built in the MFP 103) are insufficient, post-processing (for example, case binding processing) can be performed using the nearline finisher 106.

  The nearline finisher system 104 includes a nearline finisher control server 105 and a nearline finisher 106 such as a case binding machine. The nearline finisher control server 105 is a computer that performs overall management of post-processing steps. Based on the print job instruction received from the workflow management server 102, the nearline finisher control server 105 instructs the nearline finisher 106 in a post-processing (finishing process) process as requested. In general, the nearline finisher control server 105 exchanges information with the workflow management server 102 and exchanges information with each nearline finisher 106 based on the internal command and status of the nearline finisher 106. The workflow management server 102 can obtain information on the nearline finisher 106 through the nearline finisher control server 105.

  The near-line finisher 106 executes post-processing steps performed on a paper document printed by an image forming apparatus such as the MFP 103 as various sheet processing processes on the output document, and the printed paper document is converted into a desired bookbinding form. Control to process. Examples of the post-processing process include a cutting process process, a saddle stitch bookbinding process process, a case binding process process, a paper folding process process, a punching process process, an enclosing process process, and a bookbinding process process.

  The workflow management server 102 centrally manages the workflow of the printing system by instructing the MFP 103 and the nearline finisher system 104 to perform work. Specifically, the workflow management server 102 plays a role of receiving a print job from the above-described job generation PC 101 and assembling work in each process as a workflow based on the designation of the print job.

  The job generation PC 101, workflow management server 102, MFP 103, and nearline finisher system 104 exchange information using JDF (Job Definition Format) or the like. JDF is a description format in a job ticket or the like that describes a work instruction for a print job. The job generation PC 101, workflow management server 102, MFP 103, and nearline finisher system 104 use JDF to transfer print jobs and issue control commands. As a result, the workflow management server 102 uses the MFP 103 and the nearline finisher system 104 to realize a total workflow automation.

FIG. 18 is a diagram illustrating an example of a hardware configuration of each device according to the present embodiment. In FIG. 18, the job generation PC 101 and the workflow management server 102 are collectively referred to as a host computer.
The job generation PC 101 and the workflow management server 102 execute a document processing in which graphics, images, characters, tables (including spreadsheets), etc. are mixed based on a document processing program stored in the ROM 1803 or the external memory 1811. Is provided. In the job generation PC 101 and the workflow management server 102, the CPU 1801 comprehensively controls each device connected to the system bus 1804. The program ROM in the ROM 1803 or the external memory 1811 stores an operating system program that is a control program for the CPU 1801. The font ROM or external memory 1811 in the ROM 1803 stores font data used in the document processing, and the data ROM or external memory 1811 in the ROM 1803 stores various data used in the document processing. Data is stored. The RAM 1802 functions as a main memory, work area, and the like for the CPU 1801.

  A keyboard controller (KBC) 1805 controls key input from a keyboard 1809 or a pointing device (not shown). A CRT controller (CRTC) 1806 controls display on a CRT display (CRT) 1810. A disk controller (DKC) 1807 controls access to an external memory 1811 such as a hard disk (HD) or a flexible disk (FD) that stores files. The stored files include a boot program, various applications, font data, a user file, an edit file, a printer control command generation program (hereinafter referred to as a printer driver), and the like. A printer controller (PRTC) 1808 is connected to the MFP 103 via a bidirectional interface (interface) 1821 and executes communication control processing with the MFP 103. The NC 1812 is connected to the network and executes communication control processing with other devices connected to the network.

  The CPU 1801 executes, for example, an outline font development (rasterization) process on the display information RAM set on the RAM 1802 to enable WYSIWYG on the CRT 1810. Further, the CPU 1801 opens various windows registered based on commands instructed by a mouse cursor (not shown) on the CRT 1810 and executes various data processing. When executing printing, the user opens a window regarding print settings, and can set the print processing method for the printer driver, including setting of the MFP 103 and selection of a print mode.

  The MFP 103 is controlled by the CPU 1912. The CPU 1912 outputs an image signal as output information to a printing unit (printer engine) 1917 connected to the system bus 1915 based on a control program stored in the ROM 1913 or a control program stored in the external memory 1914. The program ROM in the ROM 1913 stores a control program for the CPU 1912 and the like. The font ROM in the ROM 1913 stores font data used when generating the output information. The data ROM in the ROM 1913 stores information used on the job generation PC 101 and the workflow management server 102 in the case of the MFP 103 without the external memory 1914 such as a hard disk.

  The CPU 1912 can communicate with the job generation PC 101 and the workflow management server 102 via the input unit 1918, and can notify the job generation PC 101 and the workflow management server 102 of information in the MFP 103. The RAM 1919 is a RAM that functions as a main memory of the CPU 1912, a work area, or the like, and is configured such that the memory capacity can be expanded by an optional RAM connected to an expansion port (not shown). The RAM 1919 is used as an output information expansion area, environment data storage area, NVRAM, and the like. Access to the above-described external memory 1914 such as a hard disk (HD) or IC card is controlled by a memory controller (MC) 20. The external memory 1914 is connected as an option and stores font data, an emulation program, form data, and the like. Further, the operation panel 1921 described above is provided with switches for operation, LED indicators, and the like.

Further, the external memory 1914 described above is not limited to one, and a plurality of external memories 1914 are provided. In addition to the built-in font, a plurality of external memories storing an option card and a program for interpreting printer control languages having different language systems can be connected. May be. Further, an NVRAM (not shown) may be provided, and printer mode setting information from the operation panel 1921 may be stored.
The nearline finisher control server 105 has almost the same hardware configuration as the workflow management server 102, and the nearline finisher 106 has almost the same hardware configuration as the MFP 103. However, the nearline finisher 106 does not have a hardware configuration related to printing.

FIG. 2 is a diagram illustrating an example of a workflow of the printing system.
A JDF job generation application 202 operating on the job generation PC 101 generates a JDF job 212, which is a print job in which work instructions in a workflow are described, from an order receipt job 201 received an order from a customer based on an instruction from an operator of the printing system. create.
The JDF job 212 is transmitted to the JDF job controller 203 operating on the workflow management server 102. Upon receiving the JDF job 212, the JDF job controller 203 divides the JDF job 212 in accordance with each work instruction (prepress, press, postpress, etc.) described in the JDF job 212. The JDF job controller 203 generates a work instruction for the MFP 103 and the nearline finisher system 104 based on the divided contents, and transmits the work instructions to the MFP 103 and the nearline finisher system 104 as JDF jobs 213 and 214.

When the JDF job 213 is transferred to the MFP 103, the printer controller 204 interprets the JDF job 213 and executes print processing. The JDF job 213 includes, for example, work instructions for press processing to be processed by the MFP 103. In this work instruction, attributes such as paper feed stage information, output paper size, double-sided / single-sided printing, and N-up are specified as setting parameters for the press instruction, and print processing is performed according to the contents of the JDF job 213. Is executed, and an output product 206 is obtained.
If the JDF job 213 is designated with post-press instructions such as case binding, saddle stitch binding, and cutting, the MFP 103 uses the inline finisher 205 to perform post-processing after printing according to the contents of the JDF job 213. It is also possible to execute.

On the other hand, when the JDF job 214 is transferred to the nearline finisher system 104, the nearline finisher controller 207 interprets the JDF job 214 and executes post-processing. The JDF job 214 includes, for example, a work instruction for post-press processing to be processed by the nearline finisher 106. Also, attributes such as case binding, saddle stitch binding, and cutting are specified for the JDF job 214, and the nearline finisher 106 executes post-processing after printing in accordance with the contents of the JDF job 214, and outputs the output 208. obtain.
In the nearline finisher system 104, a paper document is required for post-processing. Normally, the user manually carries the output product 206 from the MFP 103 and sets it on the nearline finisher 106.
Thus, although the work instruction itself is performed via the network, the actual paper document is not electronically transmitted from the MFP 103 to the nearline finisher 106. For this reason, when post-processing is performed by the nearline finisher 106, the operator carries a paper document and performs post-processing by the nearline finisher 106.

  Here, in the printing system shown in FIG. 1, when the inline finisher 205 (post-processing device) included in the MFP 103 is used to implement case binding printing, the press processing and the post press processing are performed in the JDF job 213. And send it to the MFP 103. As a result, a case-bound printed product that is the only product (output product) from the MFP 103 is obtained. On the other hand, when bookbinding is performed by a case binding machine that is a nearline finisher (post-processing apparatus) that the MFP 103 does not have, a cover document and a body document are output separately by the digital printing machine. Then, the user carries the cover document and the main document to the case binding machine, sets the cover document and the main document in the paper feed stage of the case binding machine, and performs the case binding creation work. As described above, in the case binding machine of the nearline finisher, it is usually necessary to perform processing by distinguishing the cover original and the main original.

FIG. 3 is a block diagram illustrating an example of the configuration of the JDF job controller 203.
The components 301 to 312 illustrated in FIG. 3 are realized by the steps of the flowchart described later with reference to FIGS. 9 to 13 under the overall control of the control unit 300 executed by the CPU 1801.
The JDF reception unit 301 receives a print job (JDF job 212) from the JDF job generation application 202 shown in FIG. The received print job is stored in the received job storage unit 302.

The JDF interpretation unit 303 analyzes “description contents by JDF” in the received print job (JDF job 212), and recognizes the print setting applied to the print job. The JDF editing unit 304 edits a print job (JDF job 212) for transmission to the MFP 103 and the nearline finisher system 104. The job ticket generation unit 305 generates a job ticket to be printed at the top of the page constituting the print job when the JDF editing unit 304 edits the print job (JDF job 212). The edited print job (JDF job 212) is stored in the JDF storage unit 306.
A conversion method determination unit 307 determines which conversion method is to be used as a print job conversion method when the received print job (JDF job 212) is transmitted to the MFP 103 and the nearline finisher system 104.

The device management unit 308 manages the MFP 103 and the nearline finisher system 104 connected in the subsequent stage. The JDF transmission unit 309 plays a role of transmitting print jobs (JDF jobs 213 and 214) to the MFP 103 and the nearline finisher system 104.
The setting management unit 310 manages “operation settings of the workflow management server 102” set by the user from the user interface unit 311. The operation setting value is stored in the setting value storage unit 312.

FIG. 4 is a diagram conceptually illustrating an example of a job ticket (JDF job) when instructing case binding printing.
The job ticket 400 is described in, for example, JDF (XML format) and is expressed by a hierarchical structure of nodes.
In FIG. 4, it is shown that the entire book 401, which is a case-bound printed matter, has been completed through various processes such as making a cover 402, making a body (contents) 404, and binding them. Yes.

In JDF, the process of forming a physical output product when composing the output product is called a product node (in FIG. 4, the entire book 401, the cover 402, and the body 404). In addition, a process for forming a product node is called a process node. The process node is an intermediate stage element for creating a product node. A collection of several process nodes is called a process group node. Thus, JDF distinguishes each process.
In FIG. 4, a cover output 403 is an aggregate of processes for generating the cover 402, and the process is realized by a number of process groups 407.
As a specific example, in FIG. 4, the process group that performs the output 405 of the main body includes a RIP process 408 and a print process 409. Further, the process group that performs the bookbinding process 406 of the entire book includes a case binding process 410 and a cutting process 411.

FIG. 5 is a diagram schematically showing the job ticket 400 (JDF job) shown in FIG. 4 from the side of process processing.
FIG. 5A is a diagram illustrating an example of the overall configuration of the job ticket 400. The job ticket 400 describes overall information of the job ticket 400 (entire information 501) and a work process (process structure 502).
FIG. 5B specifically shows the job ticket 400 shown in FIG.
The prepress process 504 is for instructing how to process and arrange the content data (print data) such as PDF. Here, a plurality of Prepress processes 504 exist.
The press process 505 is for instructing how to output the image data created in accordance with the instruction of the prepress process 504 to a document (paper). Here, a plurality of Press processes 505 exist.

  The Postpress processing 506 is for instructing how to post-process the original output according to the instruction of the Press processing 505, such as case binding. Here, a plurality of Postpress processes 506 exist. Here, the Combined Process process 503 combines the Prepress process 504, the Press process 505, and the Postpress process 506 into one process. Normally, in the MFP 103 or the like that controls digital printing, a bookbinding result obtained by completing the execution of the Prepress process, the Press process, and the Postpress process for a single print job input is the only product 507 (output). As described above, the Combined Process 503 is used when it is desired to sequentially process the Prepress process, the Press process, and the Postpress process for a single input of data, and to output only one product 507. The When an instruction is given to a digital image forming apparatus such as an MFP that performs at least two processes of the Prepress process, the Press process, and the Postpress process, the Combined Process process is always used.

The Prepress process 504 corresponds to, for example, the RIP process 408 that is the process node of the body output 405 shown in FIG. The press process 505 corresponds to a print process 409 that is a process node of the body output 405. The Postpress processing 506 corresponds to the case binding processing 410, which is a process node of the bookbinding processing 406 of the entire book, the cutting processing 411, and the like.
In addition, parameter groups 508a, 508b, and 508c that define operations are input to the process nodes 504, 505, and 506, respectively.

FIG. 5C is a diagram illustrating a specific example of parameters input to the process node.
In FIG. 5C, the original document information 509 indicating the information of the original document to be processed is input to the prepress process 504. In the press process 505, paper feed stage information 510 indicating the paper feed destination of the physical paper is input. In the PostPress process 506, paper discharge stage information 511 indicating a paper discharge destination after post-pressing is input.
FIG. 5D is a diagram illustrating details of a specific example of parameters input to the process node.
FIG. 5D shows that information for processing PDF data “Input.pdf” is input to the prepress processing 504 as the original document information 509. Further, as the paper feed stage information 510 in the press process, information indicating that the cover is fed from “Tray1” and the body is fed from “Tray2” is input to the press process 505. Further, it is indicated that information indicating that the sheet is discharged to Stacker 1 ″ after the post press is input to the PostPress process 506.

6 and 7 are diagrams illustrating an example of a user interface output by the user interface unit 311. FIG. The setting value set by the user interface unit 311 is stored in the setting value storage unit 312 under the management of the setting management unit 310.
In FIG. 6, a process conversion method setting field 1201 displays a radio button 1202 that gives priority to the nearline finisher. When the radio button 1202 is turned on, the nearline finisher 106 is preferentially used for the print job (JDF job 212) generated by the JDF job generation application 202.
In the process conversion method setting field 1201, a radio button 1203 "prioritize inline finisher 205" is displayed. When the radio button 1203 is turned on, the inline finisher 205 is preferentially used for the JDF job 212 generated by the JDF job generation application 202.
The shown radio buttons 1202 and 1203 operate exclusively.

An output destination setting column 1204 is an area for setting an output product from the MFP 103.
FIG. 6 shows a display example of the output destination setting column 1204 when the “priority to nearline finisher” radio button 1202 is turned on in the process conversion method column 1201.
A combo box 1205 is used by the user to select an output destination of a cover that is output from the MFP 103 when the nearline finisher 106 is used.
A combo box 1206 is used by the user to select a real output destination output from the MFP 103 when the nearline finisher 106 is used.
As described above, in this embodiment, the user can individually select the output destination of the cover and the output destination of the body. Normally, different output destinations for the cover and the body are selected, but the same output destination may be selected as the output destination for the cover and the body depending on the desire of the user.
A check box 1207 is used by the user to select whether or not a job ticket is issued (granted) to an output product. The user can select whether or not to issue a job ticket for each of the two products (cover and body) from the MFP 103.

FIG. 7 shows a display example of the output destination setting column 1204 when the “prioritize inline finisher 205” radio button 1203 is turned on.
In FIG. 7, a combo box 1301 is for the user to select an output destination of an output product output from the MFP 103 when the inline finisher 205 is used.
As described above, the setting value set by the user interface shown in FIGS. 6 and 7 is stored in the setting value storage unit 312.

FIG. 8 is a diagram illustrating an example of a table for storing setting values. FIG. 8A shows a table in which no set value is stored, and FIGS. 8B and 8C show tables in a state in which the set value is stored.
In FIG. 8, a column 1401 stores setting items in the user interface shown in FIGS. A column 1402 stores setting values for each setting item. The setting value 1402 includes a priority conversion setting 1403, a cover output destination 1404, a body output destination 1405, a job ticket output 1406, and a final output destination 1407.

Hereinafter, an example of processing of the JDF job controller 203 will be described with reference to the flowcharts of FIGS. 9 to 13.
FIG. 9 is a flowchart for explaining an example of the overall outline of the processing of the JDF job controller 203.
First, in step S <b> 700, the JDF reception unit 301 receives a print job from the JDF job generation application 202. This print job is stored in the received job storage unit 302.
In the present embodiment, for example, an example of an acquisition unit is realized by executing the process of step S700.
Next, in step S701, the JDF interpretation unit 303 executes job interpretation processing. The job interpretation process determines whether the attribute of the received print job is a print job created with the intention of using the inline finisher 205 or a print job created with the intention of using the nearline finisher 106 It is processing to do. Details of step S701 will be described later with reference to FIG.

  Next, in step S702, the conversion method determination unit 307 executes a conversion method determination process. The conversion method determination process is a process for determining a conversion method for a JDF job. The conversion method means, for example, conversion from a job that uses the inline finisher 205 to a job that uses the nearline finisher 106. Details of step S702 will be described later with reference to FIG.

Next, in step S703, the JDF editing unit 304 executes JDF editing processing. The JDF editing process is a process for editing a JDF job in accordance with the conversion method determined in step S702. Details of step S703 will be described later with reference to FIG.
Next, in step S704, the device management unit 308 executes job transmission processing. The job transmission process is a process for transmitting a JDF job via the JDF transmission unit 309 to at least one of the subsequent MFP 103 and the nearline finisher system 104 managed by the JDF job controller 203.

  FIG. 10 is a flowchart illustrating an example of details of the job interpretation processing in step S701. In the job interpretation process, whether the received print job attribute is a print job created with the intention of using the inline finisher 205 or a print job created with the intention of using the nearline finisher 106 is JDF interpreted. This process is determined by the unit 303.

First, in step S <b> 801, the JDF interpretation unit 303 analyzes “JDF description contents (JDF structure)” included in the received JDF job 212.
Next, in step S802, the JDF interpretation unit 303 reads the job ticket 400 (process map) as shown in FIG. 5 based on the analysis result in step S801.
In step S <b> 803, the JDF interpretation unit 303 determines whether or not the above-described combined process process 503 is included in the job ticket 400. If the result of this determination is that the Combined Process 503 is included, the process proceeds to step S804.

  In step S804, the JDF interpretation unit 303 determines whether the combined process process 503 includes a press process 505 and a postpress process 506. As a result of the determination, if the Press process 505 and the PostPress process 506 are included, the process proceeds to step S805. In step S805, the JDF interpretation unit 303 interprets the received print job (JDF job) as a JDF job that uses the inline finisher 205.

If the combined process process 503 is not included in the job ticket 400 in step S803, the process proceeds to step S806. Also, in step S804, when the Press process 505 and the PostPress process 506 are not included in the Combined Process process 503, the process also proceeds to Step S806.
In step S806, the JDF interpretation unit 303 interprets the received JDF job 212 as a JDF job that uses the inline finisher 205.
As described above, in the present embodiment, for example, an example of the first determination unit is realized by executing the processing in steps S803 and S804.

  In this example, a determination method such as steps S803 and S804 is used as a method for determining a job attribute. However, as a method for determining a job attribute, the job attribute may be determined by analyzing a part described in JDF other than the parts shown in steps S803 and S804. .

FIG. 11 is a flowchart illustrating an example of details of the conversion method determination process in step S702. As described above, the conversion method determination process is a process in which the conversion method determination unit 307 determines the conversion method of the JDF job.
First, in step S901, the conversion method determination unit 307 reads the value of the priority conversion setting 1403 from the setting management unit 310 among the setting values 1402 that define the operation of this program (see FIG. 8). The set value 1402 is set in advance by the user.

Next, in step S902, the conversion method determination unit 307 determines whether or not the setting of the priority conversion setting 1403 read in step S901 corresponds to the setting that gives priority to the nearline finisher 106.
Thus, in the present embodiment, for example, an example of the second determination unit is realized by executing the process of step S902.
As a result of this determination, if the setting of the priority conversion setting 1403 corresponds to the setting that gives priority to the nearline finisher 106, the process proceeds to step S903. In step S903, the conversion method determination unit 307 determines in step S701 whether the received JDF job 212 is determined to be a job that uses the inline finisher 205 by the processing in FIG.

As a result of this determination, if it is determined that the received JDF job 212 is a job that uses the inline finisher 205, the process advances to step S904. In step S904, the conversion method determination unit 307 determines to convert a job that uses the inline finisher 205 into a job that uses the nearline finisher 106.
On the other hand, if it is determined in step S903 that the received JDF job is not a job that uses the inline finisher 205 by the processing of FIG. 10, the process proceeds to step S907. In step S907, the conversion method determination unit 307 determines that the (process) conversion of the JDF job 212 is not performed.

If it is determined in step S902 that the setting of the priority conversion setting 1403 read in step S901 does not prioritize the nearline finisher 106 but corresponds to prioritize the inline finisher 205, the process proceeds to step S905. In step S905, the conversion method determination unit 307 determines in step S701 whether the received JDF job 212 is determined to be a job that uses the nearline finisher 106 by the processing of FIG.
If it is determined as a result of this determination that the received JDF job 212 is a job that uses the nearline finisher 106, the process advances to step S906. In step S906, the conversion method determination unit 307 determines to convert a job that uses the nearline finisher 106 into a job that uses the inline finisher 205.

  On the other hand, if it is not determined in step S905 that the received JDF job 212 is a job that uses the nearline finisher 106, the process advances to step S907. In step S905, the conversion method determination unit 307 determines not to perform (process) conversion of the JDF job 212.

FIG. 12 is a flowchart for explaining an example of details of the JDF editing process in step S703. As described above, the JDF editing process is a process in which the JDF editing unit 304 edits a JDF job according to the conversion method determined in step S702.
First, in step S1001, the JDF editing unit 304 determines the conversion method determined in step S702.
As a result of this determination, when the conversion of the JDF job 212 is not performed, the processing according to the flowchart of FIG.
On the other hand, if it is determined in the process of FIG. 11 that the job using the inline finisher 205 is converted to the job using the nearline finisher 106, the process proceeds to step S1002. In step S 1002, the JDF editing unit 304 reads the setting of the cover output destination 1404 from the setting management unit 310.

In step S <b> 1003, the JDF editing unit 304 reads the setting of the main output destination 1405 from the setting management unit 310.
In step S1004, the JDF editing unit 304 performs pre-stage processing of JDF job process division processing. A specific example of this process will be described later.
In step S <b> 1005, the JDF editing unit 304 sets the contents of the read output destinations 1404 and 1405 as the output destination of the output product from the MFP 103 in the JDF job.

In step S <b> 1006, the JDF editing unit 304 converts the JDF job in which the output destination of the output product from the MFP 103 is set in the contents of the output destinations 1404 and 1405, the JDF job for the MFP 103, and the nearline finisher 106. Divide into JDF jobs.
In step S1007, the JDF editing unit 304 reads the setting of the job ticket output 1406.
In step S1008, the JDF editing unit 304 determines whether the setting of the job ticket output 1406 is a setting for outputting a job ticket. As a result of this determination, if the setting of the job ticket output 1406 is not a setting for outputting a job ticket, the processing according to the flowchart of FIG.

On the other hand, if the setting of the job ticket output 1406 is a setting for attaching a job ticket, the process advances to step S1009. In step S1009, the JDF editing unit 304 determines whether the setting of the job ticket output 1406 is a setting for attaching the job ticket to the cover. As a result of this determination, if the setting of the job ticket output 1406 is not a setting for attaching the job ticket to the cover, the process proceeds to step S1011 described later.
On the other hand, if the setting of the job ticket output 1406 is a setting for attaching the job ticket to the cover, the process proceeds to step S1010. In step S1010, the job ticket generation unit 305 generates a cover job ticket, and the JDF editing unit 304 performs setting to add a cover job ticket to the top of the cover content. Then, the process proceeds to step S1011.

In step S1011, the JDF editing unit 304 determines whether the setting of the job ticket output 1406 is a setting for attaching a job ticket to the body. As a result of the determination, if the setting of the job ticket output 1406 is not a setting for attaching the job ticket to the body, the processing according to the flowchart of FIG.
On the other hand, if the setting of the job ticket output 1406 is a setting for attaching the job ticket to the body, the process proceeds to step S1012. In step S1012, the job ticket generation unit 305 generates a body job ticket, and the JDF editing unit 304 performs setting to add the body job ticket to the head of the body content.

If it is determined in step S1001 that a job using the nearline finisher 106 is converted to a job using the inline finisher 205, the process advances to step S1013. In step S1013, the JDF editing unit 304 performs processing for integrating the process group for the nearline finisher 106 into the process group for the inline finisher 205. A specific example of this process will be described later.
In step S <b> 1014, the JDF editing unit 304 reads the setting of the final output destination 1407 from the setting management unit 310.
Next, in step S1015, the JDF editing unit 304 sets the information of the output destination 1407 of the final product read in step S1014 as the setting information of the output destination of the JDF job in which the process group is integrated by the process of step S1013. .
As described above, in the present embodiment, for example, an example of a setting unit is realized by executing the flowchart of FIG.

FIG. 13 is a flowchart illustrating an example of details of the job transmission process in step S704. As described above, the job transmission process is a process in which the device management unit 308 transmits JDF jobs 213 and 214 to at least one of the MFP 103 and the nearline finisher system 104 via the JDF transmission unit 309.
First, in step S1101, the device management unit 308 determines whether or not the JDF jobs 213 and 214 (jobs to be transmitted) are jobs that use the nearline finisher 106. This determination is performed using the determination result in step S703.
If it is determined that the JDF jobs 213 and 214 are jobs that use the nearline finisher 106, the process advances to step S1102. In step S1102, the device management unit 308 transmits, for example, the JDF job for the MFP 103 among the JDF jobs divided in step S703 to the MFP 103 via the JDF transmission unit 309.

In step S1103, for example, the device management unit 308 transmits the JDF job for the nearline finisher 106 among the JDFs divided in step S703 to the nearline finisher control server 105 via the JDF transmission unit 309.
If it is determined in step S1101 that the JDF jobs 213 and 214 are jobs for the inline finisher 205 instead of jobs that use the nearline finisher 106, the process advances to step S1104. In step S1104, the device management unit 308 transmits, for example, the JDF job in which the process group is integrated in step S703 to the MFP 103 via the JDF transmission unit 309.
If the job is not converted, the JDF job is transmitted according to the contents of the original JDF job.

(First specific example)
Hereinafter, a first specific example of the present embodiment will be described.
In this example, it is assumed that the user setting as shown in FIG. 6 is made as a precondition. The contents of the table stored in the set value storage unit 312 at this time are as shown in FIG. Further, it is assumed that the JDF job generation application 202 has sent a JDF job 212 (job ticket 400) for the inline finisher 205 as shown in FIG. 5D to the JDF job controller 203.

The operation at this time will be described with reference to the flowcharts of FIGS.
First, in step S700 of FIG. 9, the JDF receiving unit 301 receives the JDF job 212 (job ticket 400) for the inline finisher 205 shown in FIG. 5D from the JDF job generation application 202.
Next, in step S801 in FIG. 10, the JDF interpretation unit 303 analyzes “JDF description contents (JDF structure)” included in the received JDF job 212 (job ticket 400), and Read process structure 502.

  In step S803, the JDF interpretation unit 303 determines that the read process structure 502 includes the above-described combined process process 503. In step S804, the JDF interpretation unit 303 determines that the combined process process 503 includes a press process 505 and a postpress process 506. Accordingly, in step S805, the JDF interpretation unit 303 determines that the received JDF job 212 is a job that uses the inline finisher 205.

Next, in step S901 in FIG. 11, the conversion method determination unit 307 reads the value of the priority conversion setting 1408 from the setting management unit 310 among the setting values 1402 that define the operation of this program (FIG. 8B). reference).
In step S902, the conversion method determination unit 307 determines that the priority conversion setting 1408 read in step S901 corresponds to the priority given to the nearline finisher 106. Further, in step S903, the conversion method determination unit 307 determines in step S701 (step S805) that the received JDF job 212 is determined to be a job that uses the inline finisher 205. Therefore, in step S <b> 904, the conversion method determination unit 307 determines to convert a job that uses the inline finisher 205 into a job that uses the nearline finisher 106.

  Next, in step S1001 in FIG. 12, the JDF editing unit 304 determines that the job using the inline finisher 205 has been determined to be converted into a job using the nearline finisher 106, and the process proceeds to step S1002. In step S1002, the JDF editing unit 304 reads information on the cover output destination 1409, and in step S1003 reads information on the main output destination 1410.

In step S1004, the JDF editing unit 304 performs a pre-stage process of the JDF job (job ticket) process division process.
FIG. 14 is a diagram conceptually illustrating an example of a procedure of a pre-stage process of a print job (job ticket) process division process.
First, the JDF editing unit 304 moves the PostPress process 506 included in the Combined Process process 503 in the JDF job (job ticket 400) of FIG. 14A outside the Combined Process process 503 as shown in FIG. 14B. put out.
Next, as illustrated in FIG. 14C, the JDF editing unit 304 adds a cover component 1602 and a body component 1603 as an output product (delivery product) from the Press process 505.

  Next, as illustrated in FIG. 14D, the JDF editing unit 304 adds setting information 1604 such as case binding settings to the process of the PostPress processing 506. Here, a process boundary line 1606 indicates a boundary between a job performed in the MFP 103 and a job performed in the nearline finisher system 104. In other words, the cover component 603 and the body component 604 output from the MFP 103 are set in the JDF job to be input to the PostPress processing 506 in the nearline finisher system 104.

  In step S <b> 1005, the JDF editing unit 304 updates the output destination of the output product from the MFP 103 with the setting contents of the read output destinations 1409 and 1410. Here, the setting parameters for the Press process 505 are updated with the information on the cover output destination 1409 and the information on the main output destination 1410. Specifically, as shown in FIG. 14E, the setting parameter for the press process 505 is updated to the output destination information 1605 where the output destination of the cover is “StackerA” and the output destination of the body is “StackerB”. The

In step S <b> 1006, the JDF editing unit 304 transmits a JDF job (job ticket) whose output destination is updated to the settings of the output destinations 1404 and 1405 to the job to be sent to the MFP 103 and the nearline finisher 106. Divide into jobs.
FIG. 15 is a diagram illustrating an example of a JDF job (job ticket 400 a) transmitted to the MFP 103 and a JDF job (job ticket 400 b) transmitted to the nearline finisher 106.

In step S1008, the JDF editing unit 304 determines whether the setting of the job ticket output 1411 is a setting for attaching a job ticket. In step S1009, the JDF editing unit 304 determines that the setting of the job ticket output 1411 is a setting for attaching a job ticket to the cover. In step S1010, the job ticket generation unit 305 generates a cover job ticket, and the JDF editing unit 304 performs setting to add a cover job ticket to the top of the cover content.
Next, in step S1011, the JDF editing unit 304 determines that the setting of the job ticket output 1411 is a setting for attaching a job ticket to the body. In step S1012, the job ticket generation unit 305 generates a body job ticket, and the JDF editing unit 304 performs setting to add the generated body job ticket to the head of the body content.

FIG. 16 is a diagram illustrating an example of a cover job ticket and a body job ticket created by the MFP 103.
FIG. 16A is a diagram showing an example of a cover job ticket printed on the upper surface of the cover output, and FIG. 16B is a book job ticket printed on the upper surface of the body output. It is a figure which shows an example. For example, a cover sheet is printed after a sheet with a cover job ticket as shown in FIG. 16A is output, and a sheet with a body job ticket as shown in FIG. 16B is output. After printing, the body is printed.
FIG. 16 shows an example in which job IDs 1501 and 1504 are displayed as barcodes.
A cover ID 1502 for identifying the cover and a thumbnail image 1503 of the first page of the cover are printed on the upper surface of the output on the cover as a display job ticket together with the job ID 1501. On the other hand, the cover ID 1505 printed on the upper surface of the output body as a body job ticket is the ID of the cover corresponding to the cover of the body, and the same ID as the cover ID 1502 printed on the upper surface of the output object on the cover. . Together with the display ID 1502 and job ID 1504, a thumbnail image 1506 of the head page of the body is printed on the upper surface of the body output as a body job ticket.

Proceeding to the description of FIG. 13, in step S <b> 1101, the device management unit 308 determines that the JDF job to be transmitted is a job that uses the nearline finisher 106. This is because the processing of steps S1002 to S1012 in FIG. 12 is performed and the job for the inline finisher 205 is converted to the job for the nearline finisher 106.
In step S1102, the device management unit 308 transmits the JDF job for the MFP 103 (the JDF job (job ticket) illustrated in FIG. 15A) to the MFP 103 via the JDF transmission unit 309.
In step S1103, the device management unit 308 transmits the JDF job for the nearline finisher 106 (the JDF job (job ticket) in FIG. 15B) to the nearline finisher control server 105 via the JDF transmission unit 309. To do.

(Second specific example)
Hereinafter, a second specific example of the present embodiment will be described.
In the first specific example, the processing for changing a job intended to use the inline finisher 205 to a job intended to use the nearline finisher 106 has been described. On the other hand, in this specific example, a process for changing a job intended to use the nearline finisher to a job using the inline finisher 205 will be described.

  In this example, it is assumed that the user setting as shown in FIG. 7 is made as a precondition. The contents of the table stored in the set value storage unit 312 at this time are as shown in FIG. Further, it is assumed that the JDF job generation application 202 has sent a JDF job (job ticket 400) for nearline finisher as shown in FIG. 17A to the JDF job controller 203. In the description of this example, the portions described in the first specific example are denoted by the same reference numerals as those in FIG.

The operation at this time will be described with reference to the flowcharts of FIGS.
First, in step S700 of FIG. 9, the JDF receiving unit 301 receives the JDF job 212 (job ticket 400) for the nearline finisher shown in FIG. 17A from the JDF job generation application 202.
Next, in step S801 in FIG. 10, the JDF interpretation unit 303 analyzes “JDF description contents (JDF structure)” included in the received JDF job 212 (job ticket 400), and Read process structure 502.

  In step S803, the JDF interpretation unit 303 determines that the read process structure 502 includes the above-described combined process process 503. In step S804, the JDF interpretation unit 303 determines that the combined process process 503 includes only the press process 505 and does not include the press process 505 and the post press process 506. Accordingly, in step S806, the JDF interpretation unit 303 determines that the received JDF job 212 is a job that uses the nearline finisher 106.

Next, in step S901 in FIG. 11, the conversion method determination unit 307 reads the value of the priority conversion setting 1412 from the setting management unit 310 among the setting values 1402 that define the operation of this program (FIG. 8C). reference).
Next, in step S902, the conversion method determination unit 307 determines that the setting of the priority conversion setting 1408 read in step S901 corresponds to the priority given to the inline finisher 205.
In step S905, the conversion method determination unit 307 determines that the received JDF job 212 is determined to be a job that uses the nearline finisher 106 in step S701 (step S806). Therefore, in step S906, the conversion method determination unit 307 determines to convert a job that uses the nearline finisher 106 into a job that uses the inline finisher 205.

Next, in step S1001 of FIG. 12, the JDF editing unit 304 determines that it is determined to convert a job that uses the nearline finisher to a job that uses the inline finisher 205, and the process advances to step S1013. Then, the JDF editing unit 304 performs processing for integrating the process group for the nearline finisher 106 into the process group for the inline finisher 205.
FIG. 17 is a diagram conceptually illustrating an example of a processing procedure for integrating the process group for the nearline finisher 106 into the process group for the inline finisher 205.
First, the JDF editing unit 304 deletes the discharge destination information 1605 and the like set in the press process 505 of the JDF job (job ticket 400) for the nearline finisher 106 shown in FIG.
Next, as shown in FIG. 17C, the JDF editing unit 304 deletes the cover component 1602 and the body component 1603 that are intermediate output components.
Next, the JDF editing unit 304 integrates the PostPress process 506 into the Combined Process process 503 (see FIG. 17D).

Returning to the description of FIG. 12, in step S1014, the JDF editing unit 304 reads the setting of the output destination 1413 of the final product from the setting management unit 310 (see FIG. 8C).
In step S1015, the JDF editing unit 304 updates the output destination setting information of the JDF job (job ticket) integrated in step S1013 to the information on the final output destination 1413 read in step S1014. To do. In the example shown in FIG. 17E, output destination setting information 1704 is set as an input parameter to the PostPress process 506.

Here, the job for the nearline finisher 106 is converted into a job for the inline finisher 205. Therefore, in step S1101 of FIG. 13, the device management unit 308 determines that the JDF job to be transmitted is a job that uses the inline finisher 205.
In step S1104, the device management unit 308 transmits the JDF job obtained in step S1015 (the JDF job (job ticket) illustrated in FIG. 17E) to the MFP 103 via the JDF transmission unit 309. .

  As described above, in this embodiment, when processing a print job that uses the inline finisher 205, when it is determined that the user has set priority to use the nearline finisher 106, the print job is set to the nearline finisher. Convert for 106. That is, a print job using the inline finisher 205 is divided into a print job (process) executed by the inline finisher 205 and a print job (process) executed by the nearline finisher 106. At this time, information on the output from the inline finisher 205 (components 1602 and 1603) and information on the paper discharge destination 1605 in the inline finisher 205 are set in a print job (process) to be executed by the inline finisher 205. Further, post-processing of the information of the output product (the cover component 1602 and the body component 1603) in the inline finisher 205 is set in a print job (process) executed by the nearline finisher 106.

  Therefore, when a job generated with the intention to perform post-processing by the inline finisher 205 is post-processed by the near-line finisher 106, the output from the MFP 103 can be discharged correctly into the cover and the body. . Therefore, the work process in the nearline finisher 106 by the worker can be facilitated. Even when a job generated with the intention of performing post-processing by the inline finisher 205 is input, the near-line finisher 106 can easily perform post-processing.

  In this embodiment, when a job generated with the intention of performing post-processing by the inline finisher 205 is post-processed by the near-line finisher 106, a physical job ticket for associating the cover and the body with each other is represented by a physical job ticket. Added to. Specifically, the job ID 1501, the cover ID 1502 for identifying the cover, and the thumbnail image 1503 of the first page of the cover are printed as a display job ticket on the upper surface of the output on the cover. Also, a job ID 1504, a cover ID 1505 that is the same ID as the cover ID 1502, and a thumbnail image 1506 of the first page of the body are printed on the upper surface of the output body as a body job ticket. Therefore, the worker can easily recognize the cover and the body corresponding to each other.

  On the other hand, when processing a print job that uses the nearline finisher 106, if it is determined that the user has set priority to use the inline finisher 205, the print job is converted for the inline finisher 205. . That is, the process executed by the inline finisher 205 and the process executed by the nearline finisher 106 are integrated, and the print job is converted for the inline finisher 205. Specifically, the discharge destination information 1605 in the inline finisher 205 and the output material information (the cover component 1602 and the body component 1603) in the inline finisher 205 are deleted from the print job. Further, the paper discharge destination information 1704 in the nearline finisher 106 is set in the print job. Then, it is set in the print job that the printed cover and body are post-processed collectively by the inline finisher 205.

Therefore, jobs generated with the intention of performing post-processing by the nearline finisher 106 can be integrated, and the output from the MFP 103 can be the only product. Therefore, even when a job generated with the intention of performing post-processing by the near-line finisher 106 is input, post-processing can be easily performed by the in-line finisher 205.
As described above, in the present embodiment, the inline finisher 205 and the nearline finisher can be adaptively used according to the user's intention.

In this embodiment, the cover job ticket and the body job ticket are generated. However, if the cover and the body can be associated with each other, either the cover job ticket or the body job ticket is generated. Only one may be generated. For example, when the thumbnail image of the first page of the body is printed by the cover job ticket, it is not always necessary to generate the body job ticket.
Further, post-processing (post-process) is not limited to case binding. When case binding is performed, the MFP 103 outputs the printed matter separately for the cover and the body, and the printed matter is post-processed by the nearline finisher 106 (case binding machine). However, when bookbinding is performed by other methods, the MFP 103 outputs the printed matter separately according to the post-processing (bookbinding) method. That is, the MFP 103 can output the printed material in a plurality of parts (part and other parts) according to a post-processing (bookbinding) method.

(Other embodiments of the present invention)
Each unit constituting the print job management apparatus and each step of the print job management method in the embodiment of the present invention described above can be realized by operating a program stored in a RAM or ROM of a computer. This program and a computer-readable recording medium recording the program are included in the present invention.

  In addition, the present invention can be implemented as, for example, a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system including a plurality of devices. The present invention may be applied to an apparatus composed of a single device.

  In the present invention, a software program (in the embodiment, a program corresponding to the flowcharts shown in FIGS. 9 to 13) for supplying the functions of the above-described embodiments is supplied directly or remotely to a system or apparatus. Including. The present invention also includes a case where the system or apparatus computer achieves this by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  Examples of the recording medium for supplying the program include a floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. There are also magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R) and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded from the homepage by downloading it to a recording medium such as a hard disk.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let me. It is also possible to execute the encrypted program by using the downloaded key information and install the program on a computer.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  It should be noted that each of the above-described embodiments is merely a specific example for carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner. . That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

101 Job generation PC
102 workflow management server 103 MFP
104 Near-line finisher system 105 Near-line finisher control server 106 Near-line finisher 202 JDF job generation application 204 Printer controller 205 In-line finisher 207 Near-line finisher controller

Claims (12)

A selection means for selecting whether or not to use a post-processing device that is not connected to the printing device via a paper transport path;
When the selection unit selects to use the post-processing apparatus, a setting screen for selecting both a cover discharge destination and a body discharge destination is displayed, and the selection unit displays the post-processing device. Display control means for displaying, on the display device, a setting screen for selecting a delivery destination for the deliverable for which the post-processing has been performed when the use of the processing device is not selected;
When the use of the post-processing device is selected by the selection unit, a print job is transmitted to the printing device and a post-processing job is transmitted to the post-processing device, and the post-processing device is used by the selection unit. A data processing apparatus comprising: a transmission unit configured to transmit a job in which post-processing content and print processing content are described to the printing apparatus when the selection is not made.   The apparatus according to claim 1, further comprising: a receiving unit that receives a designation as to whether or not to print a job ticket on which an image of a first page is printed when the selection unit selects to use the post-processing device. The data processing apparatus according to 1.   When it is specified by the accepting means that both a cover job ticket and a body job ticket are printed, the same identification information is printed on both the cover job ticket and the body job ticket. The data processing apparatus according to claim 2.   The accepting unit selects whether or not to use the post-processing device and prints the job ticket on which the image of the first page is printed via the setting screen displayed by the display control unit. 4. The data processing apparatus according to claim 2 or 3, wherein both are received. A selection step for selecting whether or not to use a post-processing device that is not connected to the printing device via a paper transport path;
If the use of the post-processing device is selected in the selection step, a setting screen for selecting both a cover discharge destination and a body discharge destination is displayed. A display control step of displaying on the display device a setting screen for selecting a delivery destination for the deliverable for which the post-processing has been performed, when using the processing device is not selected;
When it is selected to use the post-processing device in the selection step, a print job is transmitted to the printing device and a post-processing job is transmitted to the post-processing device, and the post-processing device is used in the selection step. A data processing method comprising: a transmission step of transmitting, to the printing apparatus, a job in which post-processing content and printing processing content are described when the selection is not made.   2. The method according to claim 1, further comprising a reception step of receiving designation of whether or not to print a job ticket on which an image of the first page is printed when the use of the post-processing device is selected in the selection step. 5. The data processing method according to 5.   When it is specified by the receiving step that both a cover job ticket and a body job ticket are printed, the same identification information is printed on both the cover job ticket and the body job ticket. The data processing method according to claim 6.   The accepting step selects whether or not to use the post-processing device and whether or not to print a job ticket on which the image of the first page is printed via the setting screen displayed by the display control step. The data processing method according to claim 6 or 7, wherein both of the designation and the designation are accepted. A selection means for selecting whether or not to use a post-processing device that is not connected to the printing device via a paper transport path;
When the selection unit selects to use the post-processing apparatus, a setting screen for selecting both a cover discharge destination and a body discharge destination is displayed, and the selection unit displays the post-processing device. Display control means for displaying, on the display device, a setting screen for selecting a delivery destination for the deliverable for which the post-processing has been performed when the use of the processing device is not selected;
When the use of the post-processing device is selected by the selection unit, a print job is transmitted to the printing device and a post-processing job is transmitted to the post-processing device, and the post-processing device is used by the selection unit. A computer program that causes a computer to function as a transmission unit that transmits a job in which post-processing content and printing processing content are described to the printing apparatus when selection is not made.   When the use of the post-processing device is selected by the selection unit, the computer further functions as a reception unit that receives designation as to whether or not to print a job ticket on which an image of the first page is printed. The computer program according to claim 9.   When it is specified by the accepting means that both a cover job ticket and a body job ticket are printed, the same identification information is printed on both the cover job ticket and the body job ticket. The computer program according to claim 10.   The accepting unit selects whether or not to use the post-processing device and prints the job ticket on which the image of the first page is printed via the setting screen displayed by the display control unit. The computer program according to claim 10, wherein both of the designation and the designation are accepted.

Images