JP2007272762A - Managing device, workflow specifying method, storage medium and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow anybody to easily determine an image formation workflow optimum for an image formation request required from a client. <P>SOLUTION: A process management manager 111 retrieves a system process database and generates a first network workflow showing the entire available workflows to generate a template of a designated product. The process management manager 111 compares a character string in a received job definition file with a character string in the template to specify the final product and eliminates workflows irrelevant to the final product from the first network workflow to generate a second network workflow. Then, the process management manager 111 specifies the only one workflow from the second network workflow by a preset selection condition to generate a process job definition file. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a management apparatus that manages resources of a plurality of devices having different attributes constituting an image forming system and manages a workflow of an image forming system that uses each device.

  Conventionally, a request for creating a printed matter (magazine, newspaper, catalog, advertisement, gravure, etc.) is received from a third party (customer, client). Then, there is a so-called commercial printing industry in which a desired printed matter of the client is created and paid to the client by delivering it to the client.

  In such a commercial printing industry, there is a demand for higher speed and higher image quality of electrophotographic printing apparatuses and inkjet printing apparatuses.

  Along with such high speed and high image quality, there is a digital market called POD that realizes digital printing using electronic data by making maximum use of digital image forming apparatuses such as copiers and digital multifunction peripherals. Has appeared. Here, POD means print-on-demand.

  In such a POD market, an image forming system including digital devices such as a plurality of information processing apparatuses and a plurality of digital image forming apparatuses is used to generate printed matter. The process from the input document provided by the customer to the creation of the printed product as the final product is managed by the computer.

  Generally, in such an image forming system, there are a plurality of steps for creating a printed matter. Therefore, in order to realize the printed matter that satisfies the customer in the most favorable process for the system, it is very important to identify the workflow to be used and which device to use from multiple devices. It becomes important.

  Conventionally, in an image forming system, work for specifying a workflow is performed as follows. That is, a person with special knowledge such as information on the capabilities of the devices constituting the system or information on past workflow usage history operates the workflow setting function of the system.

  However, in the POD market, it is actually difficult to hire skilled workers, and it is desirable to end work at low cost, to conduct business with a small investment, to reduce TCO (Total Cost of Ownership), etc. There is also a request. In this way, automating workflow identification is a major challenge for the entire POD market.

  In order to solve this problem, Patent Document 1 below has been proposed as a method for specifying a workflow for creating a printed matter. Specifically, as described in Patent Document 1 below, “the first target for an unprocessed substrate, such as a process immediately before the final printed matter is used as a starting point, and a process immediately before that,” The process is determined in order from the previous process, and a meshed process flow is generated, and then the route is selected from the viewpoint of whether the machine required for each process exists in the printing shop. The method of determining the manufacturing process is proposed.

Further, as a general method for identifying a workflow, a method for identifying a workflow by analyzing history information of past process branches, for example, Patent Literature 2 and Patent Literature 3 listed below have already been disclosed.
JP 2005-32222 A JP-A-9-259188 Japanese Patent Registration No. 3076554

  However, in the above-described technique, after creating a mesh workflow, it is necessary to select a route and determine a manufacturing process from the viewpoint of whether or not equipment necessary for each process exists in the printing shop.

  For this reason, workflows that cannot be realized originally are included in the network workflow, and there is a problem that an extra load is applied to the generation of the network workflow and the specification of the workflow.

  Further, the above-described technique does not have means for reliably removing a workflow that has been rejected by a customer in the past from the selection target. For this reason, when the operator of the image forming system memorizes the past history and selects the workflow, there is a problem in that the workflow must be manually removed from the selection target.

  Furthermore, the above-described technique has a problem that the use history information of the workflow cannot be taken over because a coping method when the device configuration in the POD system is changed is not considered.

  The present invention has been made to solve the above-described problems, and the object of the present invention is to provide an image forming workflow that is optimal for an image forming request requested by a client, regardless of changes in the system configuration status. It is to provide a mechanism that anyone can easily decide.

  The management apparatus of the present invention that achieves the above object has the following configuration.

A management apparatus that manages resources of a plurality of devices having different attributes constituting an image forming system, and manages a workflow of the image forming system that uses each device, when the new image forming system is started up or existing When a device in the image forming system changes, a product that each device can provide to the outside and a device process file that describes a process for generating the product are obtained from each device to obtain a system process database. Creating means for creating; first generating means for searching the system process database to generate a first reticulated workflow indicating all workflows that can be used to generate a template for a specified product; Job definition in which the product information requested for formation is described in a specific format A receiving means for receiving a file, a character string in the job definition file and a character string in the template are compared to identify a final product, and a workflow not related to the final product is deleted from the first mesh workflow. Second generating means for generating a second reticulated workflow, and third generating means for generating a process job definition file by specifying a unique workflow based on a selection condition preset from the second reticulated workflow,
It is characterized by having.

  The workflow specifying method of the present invention that achieves the above object has the following configuration.

  A workflow specifying method in a management apparatus that manages resources of a plurality of devices having different attributes constituting an image forming system and manages a workflow of an image forming system that uses each device. Alternatively, when a device in an existing image forming system changes, a product that each device can provide to the outside and a device process file that describes a process for generating the product are acquired from each device. A creation step for creating a system process database and a first generation for searching the system process database and generating a first reticulated workflow showing all workflows that can be used to generate a template for a specified product. Step and product information requested for image formation are A receiving step for receiving a job definition file described in a format, and comparing a character string in the job definition file with a character string in the template to identify a final product, and from the first mesh workflow, A second generation step of generating a second reticulated workflow by deleting a workflow not related to the product, and generating a process job definition file by specifying a unique workflow based on a selection condition set in advance from the second reticulated workflow And a third generation step.

  According to the present invention, it is possible to determine which image formation workflow is optimal for an image formation request requested by a client in consideration of the accumulated use history of the workflow without depending on recognition of system configuration information in which workflow management changes. But it can be easily determined.

  In addition, it is possible to automatically generate a workflow for creating printed matter even if there is no person with special knowledge such as information on the capabilities of digital devices in the image forming system and past workflow usage history. It becomes.

  In addition, by determining the workflow based on the past product generation results, it is possible to eliminate the difference in printed matter due to the difference in workflow even if the worker changes, and the client can obtain a stable final product with a certain workflow. Can be provided.

  Therefore, by executing the identified workflow, it is possible to improve the convenience of the user with respect to the image formation request as compared with the conventional case by reducing the cost required for creating the final product.

  Next, the best mode for carrying out the present invention will be described with reference to the drawings.

<Description of system configuration>
[First Embodiment]
Hereinafter, embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

[System overview]
FIG. 1 is a block diagram showing an example of the configuration of an image forming system showing the first embodiment of the present invention. In this system, the case where the process management manager 111 performs various device configurations, workflow creation, management, and the like will be described. It is a range.

  As shown in FIG. 1, the devices constituting the image forming system of this embodiment are connected by a network 101. The network 101 may be a single system or a plurality of systems such as the networks 101a and 101b and the network 101c as shown in the figure.

  In FIG. 1, reference numerals 104, 105, and 106 denote image forming apparatuses having a function of printing electronic data provided from an external device such as a computer. The printer 104 includes a printer having a color printing function, a monochrome printing function, and a function for processing printed recording paper. The printer 105 includes a printer having a color printing function and a monochrome printing function. The printer 106 is a printer having a monochrome printing function.

  The printers 104, 105, and 106 hold the following first to third information as device process data on an internal memory. Here, the first information is a final product that each device can provide to the outside, and an intermediate product generated until the final product is generated. The second information is information on processes that each device processes to generate each product. The third information is information relating to resources input to the process for generating each product. Note that the memory may be anything as long as it is a non-volatile memory such as a hard disk, ROM, or NVRAM. Here, the intermediate product is, for example, a printed recording sheet, a collated recording sheet, or a bound recording sheet.

  Further, when the optional device includes a rewritable memory, the device process data may be updated and registered by changing the processing capability by connecting the optional device.

  Furthermore, the device process data is held as a file on a storage device (memory) in the device.

  Reference numerals 121, 122, 123, and 124 are configured as apparatuses having a sheet processing function for processing recording paper printed by the printers 104 to 106.

  In this embodiment, reference numeral 121 is a collating machine having a function of collating recording sheets (processing for collecting recording sheets in an appropriate page order). A bookbinding machine 122 has a function of performing a stapling process on a collated recording sheet by a staple unit at a central central portion of the recording sheet. Further, the bookbinding machine 122 is a bookbinding machine having a function of bonding the spine portion of the collated recording paper bundle with a special glue and wrapping it with a cover sheet to perform press molding.

  A folding machine 123 has a function of folding saddle stitched recording paper around the center of the recording paper. A cutting machine 124 has a function of cutting the bound recording paper around a predetermined portion of the recording paper (the right end of the recording paper or the upper end portion, the right end portion, and the lower end portion of the recording paper). is there.

  The sheet processing apparatus (the collating machine 121, the bookbinding machine A122, the folding machine 123, and the cutting machine 124) holds the following information regarding resources as device process data.

  Here, the device process data including information regarding resources includes, for example, a final product that each device can provide to the outside. Further, the device process data includes an intermediate product that is generated until the final product is generated. Further, the device process data includes a process that each device processes to produce each product.

  In addition, the device process data includes information about resources input to the process to generate each product.

  Here, the intermediate product is, for example, a collated recording sheet, a bound recording sheet, a folded recording sheet, or a cut recording sheet. The device process data is stored and managed as a file in a storage device in the device.

  In FIG. 1, reference numeral 111 denotes a process management manager. The process management manager 111 includes a database (not shown). The process management manager 111 holds in the database information related to the capabilities of the devices constituting the system, information related to printed materials that can be generated by the system, information related to workflows that can be used to generate printed materials, and workflow usage history information. .

  Then, based on the information received from the client (customer), it has a function of specifying a printed material to be generated, specifying a workflow for generating the printed material, and instructing process execution according to the specified workflow.

  Further, the process management manager 111 manages the processes of all jobs flowing through the computer, the device, or the image forming system. Here, the job includes a running job in which processing such as printing processing is being executed, and a waiting job in which a print request is made and waits for processing to start. Here, each job to be processed in this system includes various statuses such as an end job for which output processing has been completed and an error job in which an error has occurred.

  In this embodiment, the process management manager 111 is configured on a computer system including a control unit including a so-called CPU, ROM, RAM, and an input / output device. Then, the process management manager 111 executes various functional processes by executing a control program (software) shown in a flowchart described later.

  The process management manager 111 is configured to be communicable via a communication unit (NIC) included in itself and a communication unit NIC included in each device (including an image forming apparatus, a sheet processing apparatus, and the like).

  Then, the process management manager 111 acquires information regarding the job acceptance status from each device via each NIC.

  Also, various data such as information relating to the device status (operation status, error status, etc.) and job progress information relating to the job processing status are obtained from each device via a communication medium such as the network 110. Thereby, the process management manager 111 is configured to be able to grasp each device and a job to be processed in this system and manage the process of each job.

  The process management manager 111 functions as a centralized management system called a management information system (MIS = Management Information System). Thereby, the process management manager 111 can support a management plan and management work through collection, processing, and reporting of production related data, accumulate information, and provide it to a necessary department when necessary.

  The process management manager 111 is software in a computer that is the center of this management information system. The process management manager 111 plays a role of centrally managing information by data communication with each device of the system and creation of a database of information by the computer. To fulfill.

  Using the data stored in the external storage device provided in the process management manager 111, the print generation workflow generated by this system is specified, the job is scheduled, and the work process is instructed and managed. Or And the process management manager 111 manages the schedule which raises the production capacity plan of the whole system in an integrated manner.

  Here, the data managed by the process management manager 111 includes, for example, function information and capability information included in each device, and information on a printed matter that can be generated by the system. Further, the data managed by the process management manager 111 includes information regarding a workflow for generating a printed matter, workflow usage history information, status information of each device, status information and progress information of a received job, and the like. .

  Reference numeral 112 denotes an order / submission manager, which receives printed matter information from a user interface unit (for example, a client computer) of a client (customer) via a predetermined communication medium such as the Internet and accepts a printed matter creation request. Here, the print information includes a print document, the number of print copies, a print size, and the like.

  The order / entry manager 112 is a computer that acts as an intermediary for so-called electronic commerce (EC), and is a computer for placing and receiving orders with other devices such as a client computer via a communication medium such as the Internet. .

  Further, when viewed from the user side, the order receiving / inputting manager 112 has an electronic store using a web page on the Internet, and performs user authentication in response to a login request from the client side. Thereafter, a desired file is sent as electronic data together with a desired setting from its own computer to the order / manufacture manager 112 to place an order for a job.

  A proof manager 113 is configured to be capable of data communication with a device such as a client computer via a communication medium such as the Internet.

  Then, an output sample of the printed matter is generated according to the printed matter specified by the process management manager 111 and the workflow for generating the printed matter. Then, it has a function of causing the client (customer) to confirm (proof processing (proofreading processing)) before the actual printing by the image forming apparatus whether or not the generated output sample is as intended by the user.

  The proof manager 113 presents an output sample of the printed matter to the client via the UI of the client computer (client) 102. And when the consent instruction of the processing result is obtained from the client, it has a function of notifying the process management manager 111 that the printed matter and the workflow are specified. In addition, when the approval instruction is not obtained from the client 102, the proof manager 113 requests the client 102 to correct the printed material information. Then, the process management manager 111 is instructed to redo the selection of the printed material and the workflow, and this process (proofing process of the job to be processed) is repeated until an output sample of the printed material that is satisfied by the client (print requester) is obtained. It has a function.

  Reference numeral 114 denotes a print manager, which transfers data via a communication medium such as the network 110 to a device serving as a print output destination included in the system based on a process execution instruction from the process management manager 111. Here, the device is at least one of the printer 104, the printer 105, and the printer 106. The print manager 114 has a function of controlling the print output destination image forming apparatus to execute print output (print processing) of the processed image data.

  A post-processing manager 115 has a function of controlling the collating machine 121, the bookbinding machine 122, the folding machine 123, and the cutting machine 124 based on a process execution instruction from the process management manager 111.

  Specifically, the post-processing manager 115 controls at least one of the devices described above to execute a post-processing (finishing processing) step of the printed material on the recording paper printed by the image forming apparatus. Here, post-processing is a collation processing step, a bookbinding processing step, a paper folding processing step, and a cutting processing step.

  Reference numeral 116 denotes a file storage manager, which is a control that is stored and stored in a storage device including a user job (including image data to be printed on recording paper), or activated by a file server that responds to a reprint request. Configured as a program.

  For example, the file storage manager 116 causes the image data of the job received by the order receipt / submission manager 112 to be printed by one of the image forming apparatuses of the present system in the desired output form of the client. Even after printing, the printed image data is stored and held in a memory unit such as a hard disk provided in the file storage manager 116.

  Then, when the client issues a re-output request instruction for the printed job through the order / submission manager 112, the printed image data held in the memory unit is read from the memory unit. Read again. In addition, the image forming apparatus is configured to be reprintable in any image forming apparatus with a desired output form newly set by the client at the time of a re-output request.

  As described above, the image forming system shown in the present embodiment can improve the reusability of printed image data, and can avoid unnecessary data communication as much as possible by not receiving the same data from the client many times. It is configured like this.

  Reference numeral 117 denotes a delivery / shipment manager, which is configured to be able to perform data communication with other devices via a communication medium such as the Internet. Then, the delivery / shipment manager 117 responds to reception of print completion notification data indicating completion of the printed matter from any one of the devices of this system, for example.

  Then, the delivery / shipment manager 117 delivers the document (printed material) for the operator who operates the device of this system to the client that has sent the print request to the order / submission manager 112. Instruct using UI or the like.

  The delivery / shipment manager 117 also manages delivered delivery slip data (including slip information related to jobs to be delivered), shipping history data (including information related to jobs that have been created and shipped to the client), and so on. Play a role).

  Each of the managers 111 to 117 may be configured by a separate information processing device (for example, a host computer or a server), and one or more of the functions of the managers 111 to 117 may be configured as one information processing device. You may comprise so that it may implement | achieve.

  For example, a single host computer or server that can execute all the functions of the managers 111 to 117 may be incorporated in the system. Further, an individual host computer or server may be incorporated in the system for each of the managers 111 to 117. Furthermore, a plurality of host computers or servers that can execute the functions of some of the plurality of managers may be incorporated in the system. That is, any configuration is possible as long as it is an apparatus configuration and system configuration capable of executing various controls described in this embodiment.

  Each manager is, for example, a computer device (information processing unit) having a CPU, ROM, RAM, HD, etc., and the CPU executes a control program stored in the ROM, HD, or other storage medium to execute each function. Is realized.

  In FIG. 1, reference numeral 102 denotes a client computer (client), which is an information processing apparatus that can access the managers 111 to 117. In the client 102, a predetermined OS is installed in the hard disk device, and the OS is loaded into a RAM or the like to execute various applications. The client 102 is configured to be able to communicate with each of the managers 111 to 117 of this system using a predetermined protocol.

  The client 102 is configured to be able to transmit image data desired to be printed together with the printed matter information to the order reception / submission manager 112 via the network.

  Further, the client 102 is configured to be able to receive sample output data of the printed matter from the proof manager 113 via the network in order to confirm the quality of the document requested for printing.

  Further, the client 102 is configured to be able to receive print completion notification data from the delivery / shipment manager 117 in order to receive a print completion notification, and performs various types of information processing by the user via a UI such as the display of the client. Configured to be executable.

  The system according to this embodiment includes a plurality of types of devices such as an image forming apparatus, an apparatus for post-processing printed recording paper, and an apparatus having various manager functions. Each of the plurality of devices includes a communication unit, and is configured to be able to exchange data via a predetermined communication medium such as the network 101. And the process management manager 111 is comprised so that management of all the following data is possible. Here, the data includes image data, printed material information, workflow information, process execution instruction data, control data, status request data, status data, and the like.

  In the present embodiment, data transferred between each manager and each device is realized by a format called PPF (Print Production Format) in CIP3. Here, CIP stands for International Co-operation for Integration of Prepress Press and Postpress. CIP3 is a collaborative organization for integrating printing workflows for plate making, printing, and post-processing. It is a data standardization format that uses prepress data in all printing processes from the press plate onwards and helps to automate and improve quality.

  CIP4 is realized by a new format of a standard specification for describing a wide range of jobs including printing and e-commerce, called JDF (Job Definition Format) in an expanded version of CIP3.

  PPF is a format for integrating all workflows related to printing in a plurality of devices of this system and exchanging processing and management data between the processes, and is based on PostScript (registered trademark). PPF handles a variety of information such as management information, ink adjustment, and cutting position designation, and postscripts aimed at stabilizing quality, reducing errors, speeding up processing, and operating production equipment efficiently. It is a standard format based on it.

  Here, the whole workflow means prepress → press → postpress. The prepress is a general term for processes up to the start of the printing operation in the image forming apparatus of the present system, and is also called a preprocess. The press means a printing process in the image forming apparatus of this system. Further, the post-press is a sheet processing process as a post-process in the sheet processing apparatus of the present system that is executed after a printing operation by the image forming apparatus of the present system, and is also called a post-process.

  On the other hand, JDF is a format in which prepress work information called PJTF (Portable Job Ticket Format) proposed by Adobe and control attributes are added in addition to the controllability of PPF. In addition, JDF lists information integration of prepress, press, and postpress, cooperation between production and process management manager, and compatibility with existing systems.

  JDF follows an architecture that is used by PJTF to deliver a work instruction called Job Ticket. The JDF is a mechanism in which processing necessary for each process is sequentially executed on the history, work instructions, management information, etc., and transmitted to the next process.

  Further, in JDF, XML (extensible Markup Language) is used as a language for constructing a job ticket (work instruction).

  In JDF, a template that describes an array of XML elements and attributes called a schema is defined, and XML data is rewritten in each step according to the defined schema. This is shown in FIG.

  FIG. 2 is a diagram illustrating an example of a workflow of the image forming system of the present embodiment. This example is an example showing how JDF data is rewritten in each process.

  As shown in FIG. 2, in the present system, the process management manager 111 performs the following processing on the manuscript data submitted to the order reception / submission manager 112 and the printed matter information. That is, the JDF application 2102 in the process management manager 111 specifies the printed material to be generated and the workflow for generating the printed material, and sequentially creates JDF data 2103a to 2103e.

  Furthermore, in the present system, JDF data can be rewritten by, for example, the process management manager 111 and the order / manufacture manager 112 with respect to the JDF data generated by the process management manager 111. Similarly, the proof manager 113, the print manager 114, the post-processing manager 115, the file storage manager 116, and the delivery / shipment manager 117 can rewrite JDF data.

  In the example of FIG. 2, the print manager 114 and the post-processing manager 115 are illustrated, and exchange of JDF data is translated by the JDF parser 2104 (or 2107). In each of the managers of the print manager 114 and the post-processing manager 115, information is added, deleted, and modified under the control of each manager.

  Even if the actual print output (paper output, which is the recording paper that has been printed out by the image forming apparatus of this system) is processed offline, this information is exchanged from each device via the JDF parser. Is written to the JDF data. Then, it is transmitted to the bucket relay system, and each JDF data is sequentially managed by the process management manager 111, so that the status of each job can be viewed in a list.

  The off-line processing referred to here is, for example, that an output printed by an image forming apparatus by an operator is manually carried to a sheet processing apparatus such as the bookbinding machine A in the system, and is transferred to the sheet processing apparatus. It is the processing to set.

  In this system, printed matter information (image data to be printed on recording paper, requester information for creating printed matter, number of copies, print size, cost, delivery date, etc.) submitted by the client via the order / submission manager 112 Various information) is called intent JDF data. A file in which the intent JDF data is described is called an intent JDF.

  In addition to intent JDF data, JDF data including printed matter generation process execution information is referred to as process JDF data. A file in which the process JDF data is described is called a process JDF. Here, the printed matter generation process execution information is various processing conditions set at the time of process execution of each device, such as device information to be used and parameter setting information.

  In the present embodiment, the process management manager 111 adds information necessary for the intent JDF to generate a process JDF.

[Description of processing]
Next, using FIG. 3 to FIG. 18, the image forming system shown in the present embodiment is constructed, and a PDF file that is document data and an intent JDF are obtained from a client (requester). Then, a series of processes from specifying the printed material and the workflow for generating the printed material from the obtained information, generating the process JDF, and generating the printed material will be described.

[Process when constructing image forming system]
At the time of constructing the image forming system, the process management manager 111 generates a first reticulated workflow representing products that can be generated by the system and all the workflows that can be used to generate the products. The flow of this process will be described with reference to FIGS.

  FIG. 3 is a flowchart illustrating an example of a first data processing procedure in the image forming system of the present embodiment. This processing corresponds to a processing procedure executed by the process management manager 111 at the time of system construction. In addition, S601-S610 shows each step. Each step corresponds to a control procedure executed by the process management manager 111 shown in FIG.

  A plurality of devices such as an image forming apparatus, a sheet processing apparatus, and an information processing apparatus having a manager function are connected to a network to construct the image forming system shown in FIG. In step S601, the process management manager 111 requests the printer 104, the printer 105, and the printer 106 to acquire device process data shown in FIGS. 4A to 4C. Similarly, the process management manager 111 requests the collating machine 121, the bookbinding machine 122, the folding machine 123, and the cutting machine 124 to acquire the device process data shown in FIGS. 4A to 4C.

  4A to 4C are diagrams showing device process data in the image forming system shown in FIG.

  In FIG. 4A to FIG. 4C, 201 is device process data of the printer 104. Reference numeral 202 denotes device process data of the printer 105. Reference numeral 203 denotes device process data of the printer 106.

  Reference numeral 204 denotes device process data of the collator 121. Reference numeral 205 denotes device process data of the bookbinding machine 122. Reference numeral 206 denotes device process data of the cutting machine 124. Reference numeral 207 denotes device process data of the folding machine 123.

  As shown in these figures, each device process data is a set of process data. Specifically, the process data includes a product 212 that can be generated, a process 211 for generating the product, and a resource 210 that is input to the process to generate the product. Hereinafter, the structure of the process data will be described with an example.

  In FIG. 4B, in the device process data 203 of the printer 106, the product that can be generated by the printer 106 is “a monochrome high-grade printed cover”. Therefore, the process for generating the product is “PPC1 (monochrome printing by the printer C)”, and the resource input to the process PPC1 to generate the product is 1 in the process data described as “PDF file”. Included.

  Further, in the device process data 207 of the folding machine 123, the product that can be generated by the folding machine 123 is “saddle stitch book”, and the process for generating the product is “POA1 (center folding by folding machine A)”. It is. Therefore, the resource input to the process POA 1 to generate the product includes one process data describing “right-open saddle stitched intermediate product 1”.

  When each device transmits device definition data to the process management manager 111, in step S602, the process management manager 111 combines device process data transmitted from each device. Then, the process management manager 111 constructs system process data shown in FIGS. 9A and 9B, which will be described later, and stores it in the database.

  System process data (SPD) is a set of process data, and the system process data in this embodiment includes, for example, 22 process data.

  Next, in step S603, the process management manager 111 acquires the temporary final product template shown in FIG. 5 generated by the system builder.

  This acquisition of data may be realized by a system builder registering a temporary final product template on a registration screen provided by the process management manager 111. Alternatively, it may be realized by copying a temporary final product template file generated by another information processing apparatus to the process management manager 111.

  In the present embodiment, it is assumed that four temporary final product templates of color leaflet 1, color leaflet 2, manual, and ring binding manual shown in FIG. 5 have been acquired.

  Next, in step S604, the process management manager 111 determines whether or not the acquired temporary final product template can be generated by searching information registered in the SPD.

  Specifically, from the provisional final product template to the first manuscript data as in the process for generating the immediately preceding product for manufacturing it, and the process for generating the previous product A brute force search is performed for information registered in the SPD. The search process is traced back to determine processes in order, and with this determination process, it is determined that the provisional final product template that has reached the manuscript data can be generated by the system.

  On the other hand, in the process of determining the process, it is determined that the previous product or the temporary final product template for which no process is found cannot be generated in the system.

  Note that the product in the determination process is specified by the attribute information of the temporary final product template.

  As an example, the determination procedure in the case of the color flyer 2 in the temporary final product template shown in FIG. 5 will be described.

  As shown in FIG. 5, the attribute information of the color flyer 2 includes “product name: color flyer 2”, “bookbinding method: saddle stitch folding”, “open: right open”, “presence / absence of cover: none”, “ “Text sheet: coated paper”, “text print type: color”, and “finish: standard”.

  First, the color flyer 2 is displayed on the right side of the standard printed text without a cover by the attribute information “binding method: saddle stitch folding”, “open: right open”, “presence of cover: none” and “finish: standard”. Determined to be an open saddle stitch book. Therefore, first, “product: right-open saddle stitch book” is searched from the system process data.

  Then, the process PPA10 and the process POA1 are extracted from FIG. Here, it is recognized that the input resource of the process PPA 10 is “printer A right-open saddle-stitched intermediate part 1”, that is, right-open saddle-stitched intermediate part 1 generated by the printer A. Further, it is recognized that the input resource of the process POA1 is “the right-open saddle stitched intermediate part 1”.

  Here, when “product: right-open saddle-stitched intermediate part 1 generated by printer A” is retrieved from the system process data, process PPA 8 is extracted and the input resource is “printer A color text collated intermediate part” 2 ”is recognized.

  Next, when “product: color text collated intermediate part 2 generated by printer A” is retrieved from the system process data, process PPA 6 is extracted and the input resource is “printer A high-grade printed text”. Is recognized.

  Since this result is inconsistent with the fact that the color flyer 2 is a standard printed body, the process PPA8 that produces the result is determined as an unusable process.

  Next, since the input resource of the process POA1 is “Right-open, saddle-stitched intermediate part 1”, “Product: Right-open, saddle-stitched intermediate part 1” is searched from the system process data. As a result, the process PPA8, the process PSA1, and the process PSA2 are extracted, and it is recognized that the input resource of the process PPA8 is “printer A color text collated intermediate part 2”. Further, it is recognized that the input resource of the process PSA1 is “color cover, monochrome text collated intermediate part 2”. Furthermore, it is recognized that the input resource of the process PSA2 is “intermediate part 2 that has undergone color text collation”.

  Here, the process PPA 8 is determined to be unusable based on the previous search result. Furthermore, the fact that the input resource of the process PSA1 is “color cover, intermediate part 2 with monochrome text collation” contradicts that the color flyer 2 has no cover. Therefore, the process PSA1 that brings about the result is determined as an unusable process.

  Next, since the input resource of process PSA2 is “color text collated intermediate part 2”, when “product: color text collated intermediate part 2” is retrieved from the system process data, process PPA6 and process PCA2 are Extracted. Thereby, it is recognized that the input resource of the process PPA6 is “printer A high-grade printed text”. Further, it is recognized that the input resource of the process PCA2 is “color standard printed body”.

  Here, the fact that the input resource of the process PPA6 is “printer A high-grade printed text” is inconsistent with the fact that the color flyer 2 is a standard printed text, and therefore the process PPA6 that produces the result is an unusable process. It is decided.

  Next, since the input resource of the process PCA2 is “color standard printed text”, the “product color standard printed text” system process data is searched. As a result, the process PPB3 is extracted, and it is recognized that the input resource is “PDF”. Since the input resource reaches the PDF that is the document data, the determination process ends here.

  Based on the above determination, it is determined that the provisional final product template: color flyer 2 can be generated, and the workflow that can be used to generate the product is POA1⇒PSA2⇒PCA2⇒PPB3.

  As another example, a determination procedure in the case of a temporary final product template: a ring binding manual will be described.

  As shown in FIG. 5, the attribute information of the ring binding manual includes “product name: ring binding manual”, “bookbinding method: ring binding folding”, “open: right open”, “presence / absence of cover: present”. It is. The attribute information of the ring binding manual includes “cover paper: thick paper”, “cover print type: color”, “body paper: recycled paper”, “body print type: monochrome”, and “finish: high grade”. Is included.

  First, the attribute information “binding method: ring binding”, “opening: right opening”, “presence of cover: present” and “finish: high grade”, the ring binding manual is a high-grade printed text with a cover. Is determined to be a right-open ring binding book. For this reason, first, “product: right-open ring binding book” is searched from the system process data.

  Then, the process PDA 1 is extracted, and it is recognized that the input resource is “Right-open ring-bound intermediate part 1”.

  Next, when “product: right-open ring-bound intermediate part 1” is retrieved from the system process data, process PSA3 is extracted, and the input resource is “perforated color cover, monochrome text collated intermediate part 2” It is recognized.

  Next, “product: perforated color cover, monochrome text collated intermediate part 2” is searched from the system process data. As a result, it is determined that the process cannot be extracted and the input resource does not reach the PDF, which is the manuscript data, and therefore the temporary final product template: ring binding manual cannot be generated.

  Next, when it is determined in step S605 shown in FIG. 3 that a temporary final product template can be generated, the process proceeds to step S606. In step S606, the process management manager 111 registers the temporary final product template determined to be generated and the workflow for generating the temporary final product in the first mesh workflow shown in FIGS. Advances to step S607.

  On the other hand, if it is determined in step S605 that the temporary final product cannot be generated, the process proceeds to step S607.

  In step S607, the process management manager 111 checks whether all provisional final product templates have been determined, and repeats steps S604 to S607 until all templates have been checked.

  In step S607, when all the provisional final product templates have been determined, the process proceeds to step S608. In step S608, the process management manager 111 stores the completed first mesh workflow shown in FIGS. 6A to 6F in a database secured in the process management manager 111.

  Next, in step S609, the process management manager 111 generates a final product template list shown in FIG. 7 that can be generated by the system, and stores it in a database secured in the process management manager 111.

  At this point, a final product template that can be generated by the system and a workflow for generating each final product template are determined.

  In the present embodiment, as shown in FIG. 7, there are three types of final product templates: a color flyer 1, a color flyer 2, and a manual. Therefore, the workflows for generating the final product template are 15 types of workflows WF1 to WF15 as shown in FIGS. 6A to 6F.

  Finally, in step S612, the process management manager 111 generates a use history table shown in FIG. 8, inputs initial values, and ends the process. Specifically, the process management manager 111 generates the usage history table shown in FIG. 8 as follows. That is, the usage shown in FIG. 8 for registering and storing the workflow usage date in the unit of client (customer) as past usage history information in the workflow unit existing in the first reticulated workflow shown in FIGS. 6A to 6F. Generate a history table.

  In the present embodiment, when the process management manager 111 starts up a new system and recognizes that the device configuration in the image forming system has changed, the first reticulated workflow creation process is performed as follows.

  That is, a system process database is created by combining products (final products and intermediate products) that each device can provide to the outside, and device process files that describe processes for generating the products. Then, the process management manager 111 searches the system process database to determine a final product (resource) template that can be generated by the system. Then, a first reticulated workflow representing all the workflows that can be used to generate the template is generated according to the procedure of the flowchart shown in FIG.

  FIG. 8 is a diagram showing the configuration of a usage history table created and managed by the process management manager 111 shown in FIG.

  In FIG. 8, reference numeral 901 denotes a reticulated workflow generation date storage area, 902 a workflow name storage area, 903 a workflow belonging process storage area, 904 a system workflow usage history storage area, and 905 a customer-specific workflow usage history storage area.

  In the present embodiment, the workflow WF1 to WF15 are stored in the workflow name storage area, and the processes belonging to the workflows WF1 to WF15 are stored in the workflow belonging process storage area as initial values of the usage history table. That is, the reticulated workflow generation date and time January 10, 2004 is stored in the end of the reticulated workflow generation date and time storage.

  In the present embodiment, the products that can be generated by the devices constituting the system, the processes for generating the products, and the resources input to the processes are limited to the device process data shown in FIG. Similarly, although it is limited to those described in the system process data shown in FIGS. 9A and 9B, it is needless to say that a general system is not required to be restricted by the limitation of this embodiment.

  Also, when the first reticulated workflow is changed due to a change in the device configuration in the system (for example, a low-speed monochrome printer is replaced with a high-speed monochrome printer). The process management manager 111 newly creates a use history table. At this time, when the same workflow as the old system exists in the new system, the process management manager 111 transcribes the old use history information of the workflow into the new use history table.

  Similarly, in the present embodiment, the final product template that can be generated by the system is limited to that described in FIG. 7, but a general system need not be restricted by the limitations of the present embodiment. Needless to say.

  Even if the general system exceeds the limit of this embodiment, the first reticulated workflow, the final product template, and the usage history table can be generated by the method described in this embodiment. That is clear.

[Process when a print request is received from a client]
When a print creation request is received from the client, the process management manager 111 analyzes the intent JDF, and executes a process of narrowing down the workflow by deleting unnecessary workflows from the first mesh workflow. The flow of this process will be described below.

  FIG. 10 is a flowchart illustrating an example of a second data processing procedure in the image forming system according to the present exemplary embodiment. This process corresponds to a process in which the process management manager 111 specifies a workflow when a print creation request is received from a client. Note that S1701 to S1717 indicate each step. Each step is realized by a CPU provided in the process management manager 111 loading a control program into a RAM or the like and executing it.

  In this process, the order / submission manager 112 receives a PDF file and an intent JDF file, which are print original data, from a client (customer) via a predetermined communication medium such as the Internet, and a print creation request (Job). Accept. Then, it is started by notifying the process management manager 111 of acceptance of Job.

  First, in step S <b> 1701, the process management manager 111 receives an intent JDF from the order / manufacture manager 112.

  FIGS. 11 to 13 are diagrams showing the configuration of the intent JDF received by the process management manager 111 shown in FIG.

  Here, the intent JDF is a job definition file in which product information requested for image formation is described in a specific format, and has a data structure shown in FIGS.

  As shown in FIGS. 11 to 13, the intent JDF describes a job information section that describes a job identification number, an intent information section that describes customer information, product information, and ordering information, and the type of a submitted manuscript. The submission data section is provided.

  Next, in step S1702, the process management manager 111 compares the product information character string in the intent information section of the intent JDF with the character string of the final product template shown in FIG. 7, and identifies the final product to be generated. To do.

  Specifically, the character string in the first line of the product information of the intent JDF is compared with the character string of the parameter (attribute) of the final product template to search for a partial match. Here, when a plurality of final product templates are searched, the search is repeated using the character string in the next line of the product information of Intent JDF, and the search process is repeated until a single final product template is specified. If the final product template cannot be specified even after searching with the character strings of all lines of the product information of Intent JDF, it is determined that the specification cannot be made.

  When the final product template is specified, the process management manager 111 obtains parameter (attribute) information that has not been determined in the final product template, specifically “number of pages”, “size”, and “number of copies” from the intent JDF. Search for. Then, the process management manager 111 copies to the corresponding area of the final product template. At this point, the final product to be produced is determined.

  In the case of the intent JDF shown in FIG. 11, the final product template: manual is specified by the search by the character string “product name: manual” on the first line.

  In the case of the intent JDF shown in FIG. 12, since the character string “product name:” on the first line does not have a character string corresponding to the product name, the color flyer 1, the color flyer 2, and the manual are searched. Remains. Next, the color flyer 1 and the manual remain in the search by the character string “print quality: high grade” on the second line. Further, the color flyer 1 and the manual remain even in the search by the character string “print type: color printing” on the third line. Then, the template: manual is specified by the search by “bookbinding method: case binding” on the fourth line.

  In the case of the intent JDF shown in FIG. 13, the color flyer 1 and the color flyer 2 remain in the search by the character string “product name: flyer” on the first line. Next, the color flyer 1 and the color flyer 2 remain in the search by the character string “print type: color printing” on the second line. Furthermore, color flyer 1 and color flyer 2 remain in the search by the character string “binding type: saddle stitching” in the third line, and the final product template: flyer 1 is specified by the search in “print quality: high grade” in the fourth line. Is done.

  FIG. 14 is a diagram showing the final product determined by the intent JDF shown in FIG.

  FIG. 15 is a diagram showing the final product determined by the intent JDF shown in FIG.

  FIG. 16 is a diagram showing the final product determined by the intent JDF shown in FIG.

  In step S1703, the process management manager 111 determines whether the final product has been confirmed.

  If the process management manager 111 determines that the final product cannot be determined, the process proceeds to step S1717, and the process management manager 111 determines that the product information of the intent JDF is insufficient. Then, the process management manager 111 attaches the type of information that is lacking to the intent JDF, notifies the order reception / submission manager 112 that the order cannot be received, and ends this processing.

  Upon receiving the notification, the order and submission manager 112 provides the client with information for finalizing the final product, inputs the necessary information, and requests to resubmit the intent JDF. To do.

  As described above, in the present embodiment, the process management manager 111 compares the first character string of the intent product information of the input intent JDF with the character string of the parameter of the final product template. Then, the final product to be matched is searched. When a plurality of final products are searched, a search is performed using the character string of the next product information, and the process is repeated until a single final product is specified.

  When the template of the final product is specified, the unset parameters are determined and the final product is determined. Here, if the product information for specifying the final product is not included in the MIS, it is determined that the intent is insufficient, and a plurality of selection candidates up to the specified location are displayed and mapped in step S1717. Notify error.

  However, the configuration may be such that the following processing is performed. For example, when the intent information is insufficient, the final template is specified by supplementing the information lacking in the intent based on the past information. Alternatively, the most expensive final product template is specified within the budget described in the intent.

(Specific example 1) When the number of pages, size, and number of copies that have not been set in the following intent JDF are not set, the final product manual is determined by the first “manual” search. Then, the number of pages, size, and number of copies, which have not been set, are determined.

  On the other hand, if the final product template can be confirmed in step S1703, the process proceeds to step S1704. In step S1704, the process management manager 111 reads the first reticulated workflow. Then, the process management manager 111 deletes all the workflows that are not involved in the generation of the final product determined from the workflows described in the first mesh workflow and creates the second mesh workflow.

  In the present embodiment, when the intent JDF shown in FIG. 11 is received, the workflows WF10 to WF15 are deleted at this point.

  Next, the process proceeds to step S1705, and the process management manager 111 calculates the estimated operation cost and estimated operation time of the remaining workflow as a result of step S1704.

  This calculation may be realized by obtaining the operation forecast cost, operation forecast process time, and the like of each process belonging to the workflow from the device and totaling them. Alternatively, it may be realized by other methods such as a process management manager predicting based on past workflow operation results.

  Next, the process proceeds to step S1706, and the process management manager 111 compares the budget information described in the order information section of the intent JDF with the cost calculated in step S1705.

  In step S1707, if the process management manager 111 determines that the budget information described in the order information section of the JDF is cheaper than the cost calculated in step S1705, the process proceeds to step S1708. In step S1708, the process management manager 111 deletes the workflow that is expected to cost more than the budget described in the order information section of the JDF from the second mesh workflow, and the process advances to step S1709.

  On the other hand, if the process management manager 111 determines in step S1707 that the budget information described in the JDF order information section has a high cost calculated in step S1705, the process proceeds to step S1709.

  In step S1709, the process management manager 111 determines whether all workflows remaining as a result of the process in step S1704 have been checked. If the process management manager 111 determines that an unchecked workflow remains, steps S1706 to S1709 are repeatedly executed.

  On the other hand, if it is determined in step S1709 that the process management manager 111 has finished checking all workflows, the process advances to step S1710, and the process management manager 111 checks whether there is a workflow that has not been deleted.

  Here, if the process management manager 111 determines that no workflow remains, the process management manager 111 proceeds to process step S1717, and the process management manager 111 notifies the order reception / manufacture manager 112 that an order cannot be received due to over budget, and this process is performed. Exit.

  Upon receiving the notification, the order receipt / submission manager 112 provides the client with information indicating that the budget is insufficient, requests the client to resubmit the intent JDF after changing the budget.

  On the other hand, if it is determined in step S1710 that there is a workflow that has not been deleted, the process proceeds to step 1711. In step 1711, the system operation schedule is adjusted as follows. That is, the process management manager 111 adjusts the system operation schedule using the workflow information, the delivery date information described in the order information section of the intent JDF, and the estimated workflow operation time calculated in step S1705.

  On the other hand, if it is determined in step S1712 that the workflow can be completed within the delivery date as a result of schedule adjustment, the process advances to step S1713. In step S1713, the process management manager 111 deletes the workflow from the second reticulated workflow expected to be completed within the delivery date, and the process proceeds to step S1714.

  In the present embodiment, if the intent JDF shown in FIG. 11 is received and a schedule for which the printer B cannot be used until the delivery date June 1, 2005, the workflows WF5, WF7, WF8, and WF9 are Deleted.

  On the other hand, if it is determined in step S1712 that the workflow can be completed within the delivery date, the process proceeds to step S1714.

  In step S1714, the process management manager 111 determines whether all remaining workflows have been checked. If it is determined that there are unchecked workflows, the process management manager 111 repeatedly executes steps S1711 to S1714.

  On the other hand, if it is determined in step S1714 that all workflows have been checked, the process proceeds to step S1715, and the process management manager 111 checks whether there is a workflow that has not been deleted.

  If the process management manager 111 determines that no workflow remains, the process advances to step S1717. In step S1717, the process management manager 111 notifies the order receiving / managing manager 112 that an order cannot be received due to a schedule adjustment failure, and the process is terminated.

  Upon receiving the notification, the order receipt / submission manager 112 provides the client with information indicating that the schedule is not available, and requests that the intent JDF be resubmitted after changing the delivery date.

  On the other hand, in step S1715, if the process management manager 111 determines that there is a workflow that has not been deleted, the process advances to step S1716. In step S1716, the process management manager 111 stores the second reticulated workflow in the database and ends this process.

  As a result, when an intent is newly entered or modified, a flow that does not match the contents of the intent can be deleted from the first reticulated workflow diagram to narrow down the workflow, and a second reticulated workflow can be generated. it can.

  As described above, in the present embodiment, the process management manager 111 has a function of registering a usage history table in a database that holds a usage date for each customer as past usage history information for each workflow existing in the first reticulated workflow. I have. Here, the usage history table has a data structure shown in FIG.

  Then, the process management manager 111 has a function of registering a workflow corrected during preflight to product generation at a minus point and narrowing down the workflow from the second mesh workflow by the following steps (1) to (4). Yes.

  That is, in step (1), when there is one workflow that the customer has used in the past, the workflow is selected.

  In the procedure (2), when there are a plurality of workflows that the customer has used in the past, the workflow used most recently is selected. In step (3), if there is no workflow used by the customer in the past, the workflow with the highest utilization rate in the system is selected. However, workflows with negative customer usage are excluded from selection candidates.

  In step (4), if there is no workflow that has been used in the past in the system, the workflow with negative usage count is excluded from the selection candidates, and other conditions (cost priority, schedule priority, the same device as much as possible) Use to select a workflow.

  17A to 17C are diagrams illustrating an example of a second mesh workflow managed by the process management manager 111 illustrated in FIG. This example is a second reticulated workflow example generated when the intent JDF shown in FIG. 11 is received and a schedule that the printer B cannot use until the delivery date of June 1, 2005 is planned.

  Next, the process management manager 111 selects one workflow for generating a final product from the second mesh workflow according to the workflow usage history information. The flow of this process will be described using the flowchart shown in FIG.

  FIG. 18 is a flowchart illustrating an example of a third data processing procedure in the image forming system according to the present exemplary embodiment. This process is an example of processing in which the process management manager 111 selects one workflow for generating a final product from the second mesh workflow according to the workflow usage history information. Note that S1801 to S1818 indicate each step. Each step is realized by a CPU provided in the process management manager 111 loading a control program into a RAM or the like and executing it.

  First, in step S1801, the process management manager 111 checks whether there are a plurality of workflows in the second mesh workflow. If it is determined that there are not a plurality of workflows, the process advances to step S1817 to select the only workflow remaining in the second reticulated workflow, and the process ends.

  On the other hand, if it is determined in step S1801 that there are a plurality of workflows, the process proceeds to step S1802, and the process management manager 111 acquires the customer name from the customer information part of the intent JDF.

  In step S1803, the process management manager 111 refers to the workflow use history table stored in the memory to be managed. Then, the process management manager 111 acquires usage history information corresponding to the customer name acquired in step S1802 for each workflow described in the second mesh workflow.

  In step S1804, the process management manager 111 refers to the use history information acquired in step S1803 and checks whether there is a workflow used in the past for the customer acquired in step S1802.

  If the process management manager 111 determines that a workflow exists, the process advances to step S1814, and the process management manager 111 checks whether there are a plurality of workflows used in the past for the customer. If it is determined that there is only one workflow, the process proceeds to step S1815, and the process management manager 111 selects a workflow that has been used in the past, and ends this process.

  On the other hand, if it is determined in step S1814 that there are a plurality of workflows used in the past, the process proceeds to step S1816. In step S1816, the process management manager 111 selects the latest used workflow from the plurality of workflows, and ends this process.

  On the other hand, if it is determined in step S1804 that there is no workflow previously used for the customer, the process proceeds to step S1805. In step S1805, the process management manager 111 refers to the workflow usage history table and acquires system usage history information of each workflow described in the second mesh workflow.

  In step S1806, the process management manager 111 checks whether a workflow used in the past exists in the system. If the process management manager 111 determines that there is a workflow that has been used in the past, the process advances to step S1809.

  Then, in step S1809, the process management manager 111 removes, from the selection candidates, workflows with negative points for the customer acquired in step S1802.

  In step S1810, the process management manager 111 checks whether there is a selection candidate workflow. Here, when the process management manager 111 determines that there is a selection candidate workflow, the process proceeds to step S1813, and the process management manager 111 selects a workflow with the highest number of times the system is used among the selection candidate workflows. This process ends.

  On the other hand, if it is determined in step S1810 that there is no selection candidate workflow, the process proceeds to step S1811. In step S1811, the process management manager 111 notifies the system operator that there are no remaining workflows that can be automatically selected. In step S1812, the process management manager 111 shifts to the workflow manual selection mode and ends the process.

  On the other hand, if the process management manager 111 determines in step S1806 that the workflow used in the past does not exist in the system, the process proceeds to step S1807. In step S1807, the process management manager 111 deletes a workflow having a negative system usage count from the selection candidates.

  In step S1808, the process management manager 111 checks whether there is a selection candidate workflow. If the process management manager 111 determines that there is a selection candidate workflow, the process advances to step S1818. In step S1818, the process management manager 111 selects a unique workflow from the selection candidate workflows according to other constraints, and ends the process. Specifically, the other constraint conditions include, for example, cost priority, schedule priority, or the same device usage priority as much as possible.

  On the other hand, if the process management manager 111 determines in step S1808 that there is no selection candidate workflow, the process proceeds to step S1811. Then, the process management manager 111 notifies the system operator that there is no workflow that can be automatically selected, and in step S1812, the process management manager 111 shifts to the workflow manual selection mode and ends this process.

  After shifting to the workflow manual selection mode, the process management manager 111 provides a workflow selection screen to the system operator, presents all the workflows described in the second mesh workflow, and selects the only workflow. Encourage you to. The system operator selects one workflow according to the instruction from the process management manager 111.

  As described above, in the present embodiment, as the workflow specifying method, the case of automatic specification and the manual specification by the administrator are shown.

  That is, when a plurality of workflow selection branches remain in the second reticulated workflow, the process JDF is generated by automatically specifying the flow according to a preset selection condition. Alternatively, an example is shown in which a plurality of workflows specified by the system administrator are provided (displayed) to prompt flow identification, and the process JDF is generated after the flow identification.

  Hereinafter, a specific example of automatic specification by the process management manager 111 will be described in detail.

  As described above, the process management manager 111 refers to the usage history information of each workflow in the usage history table by executing the procedure shown in FIG. 18 and performs the second network in the following procedures (1) to (4). Identify the unique workflow from the workflow.

(1) If there is one workflow used by the customer in the past, the workflow is selected (step S1815 in FIG. 18).

(2) If there are a plurality of workflows that the customer has used in the past, the most recently used workflow is selected (step S1816 in FIG. 18).

(3) If there is no workflow used by the customer in the past, the workflow with the highest utilization rate in the system is selected. However, workflows with a negative customer usage count are excluded from the selection candidates.

(4) If there is no workflow used in the past in the system, a workflow with a negative use count is excluded from selection candidates (step S1807 in FIG. 18). Then, the workflow is selected based on other conditions (cost priority, schedule priority, and the same device as much as possible).

  FIG. 19 is a diagram showing an example of a workflow use history table managed by the process management manager 111 shown in FIG. This example is an example of a workflow usage history table when a certain time has passed since the system was used.

  In this example, when the first reticulated workflow is generated, a use history table for registering and storing the use date as a past use history information as a past use history information is generated for each workflow existing in the first reticulated workflow diagram. . Then, the usage history table generation date is registered based on the following rules A and B, and the usage record is registered for each product customer when the workflow is used.

  A) Every time the workflow is executed, the use date is registered as a plus point.

  B) The process excluded from the workflow between the preflight and the final decision is an example in which it is regarded as a selection mistake process and registered with a minus point.

  Hereinafter, a workflow selected when the table shown in FIG. 19 is referred will be described.

  The first example is a case where the intent JDF shown in FIG. 11 is received. In this case, the workflows described in the second reticulated workflow are workflows WF1, WF2, WF3, WF4, and WF6.

  In step S1803 shown in FIG. 18, the customer A is acquired as the customer name described in the intent JDF. In step S1804, the workflows used in the past for the customer A are checked in the workflows WF1 to WF4 and WF6. . As a result, it is determined that the workflow WF1 has been used in the past, and the workflow WF1 is selected in step S1815.

  A second example is a case where an intent JDF having the same customer name as customer B is received except for the intent JDF and customer name shown in FIG.

  In this case, the workflows described in the second network workflow are workflows WF1, WF2, WF3, WF4, and WF6.

  In step S1803, customer B is acquired as the customer name described in the intent JDF. In step S1804, the workflow used in the past for customer B is checked among the workflows WF1, WF2, WF3, WF4, and WF6. As a result, it is determined that the workflows WF1 and WF6 have been used in the past, and the workflow WF6 with the latest use date is selected in step S1816.

  A third example is a case where an intent JDF having the same customer name as customer C is received except for the intent JDF and customer name shown in FIG.

  In this case, the workflows described in the second network workflow are workflows WF1, WF2, WF3, WF4, and WF6.

  In step S1803, the customer C is acquired as the customer name described in the intent JDF. In step S1804, the workflow used in the past for the customer C is checked among the workflows WF1, WF2, WF3, WF4, and WF6. As a result, it is found that there is no workflow used in the past.

  Next, when it is checked in step 1805 whether a workflow used in the past exists in the system, it is found that the workflows WF1 and WF6 exist. In step S1809, if workflow WF1 in which the number of uses of customer C is negative is excluded from the selection candidates, workflow WF6 is selected in step S1813.

  A fourth example is a case where an intent JDF having the same customer name as customer D is received except for the intent JDF and customer name shown in FIG.

  In this case, the workflows described in the second reticulated workflow are workflows WF1, WF2, WF3, WF4, and WF6.

  In step S1803, the customer D is acquired as the customer name described in the intent JDF. In step S1804, the workflows used in the past for the customer D are checked among the workflows WF1, WF2, WF3, WF4, and WF6. As a result, it is found that there is no workflow used in the past. In step S1805, when it is checked whether a workflow used in the past exists in the system, it is found that the workflows WF1 and WF6 exist.

  In step S1810, since there is no workflow in which the number of uses of customer D is negative, workflow WF1 is selected in step S1813.

  When a workflow is selected, the process management manager 111 adds the selected workflow information to the intent JDF to generate a process JDF. Then, the process management manager 111 sends it to the print manager 114 and the post-processing manager 115 in order to execute the final product generation JOB.

  The print manager 114 and the post-processing manager 115 control devices in the system, execute jobs according to the process JDF, and generate final products.

  When the final product is generated, the process management manager 111 registers the workflow usage history in the workflow usage history table.

  Specifically, the workflow usage date is registered as a plus point in the customer field that uses the workflow in the workflow customer usage history area, and the total of the customer usage history is recalculated and registered in the workflow system usage history area. .

  Thereafter, in accordance with an instruction from the process management manager 111, the file storage manager 116 stores the PDF file, the intent JDF, and the process JDF that are document data. Then, the delivery / shipment manager 117 receives the notification of the end of the production of the final product from the process management manager 111, and sends the final product to the client for delivery.

  In the present embodiment, the process management manager 111 performs the following processing when an intent having the data structure shown in FIGS. 11 to 13 is newly input or modified. Specifically, the process management manager 111 compares the character string of the intent product information with the character string of the parameter of the final product template in order until the final product is specified, and specifies the final product to be matched.

  Then, the process management manager 111 deletes the workflow not related to the final product from the first mesh workflow and generates the second mesh workflow based on the procedure shown in FIG.

  Then, the process management manager 111 automatically identifies a unique workflow from the generated second mesh workflow based on a preset selection condition, and generates a process JDF. Here, the selection conditions set in advance include past use history priority, cost priority, schedule priority, priority on using the same device as much as possible.

  According to the above-described embodiment, the optimum image forming workflow for the image forming request requested from the client in consideration of the accumulated use history of the workflow without depending on the recognition of the system configuration information in which the workflow management changes. Can be determined dynamically.

  In addition, it is possible to automatically generate a workflow for creating printed matter even if there is no person with special knowledge such as information on the capabilities of digital devices in the image forming system and past workflow usage history. It becomes.

  In addition, by determining the workflow based on the past product generation results, it is possible to eliminate the difference in printed matter due to the difference in workflow even if the worker changes, and the client can obtain a stable final product with a certain workflow. Can be provided.

[Second Embodiment]
[Proof processing]
As described in the first embodiment, the process management manager 111 selects a unique workflow in step S1813 shown in FIG. Then, after the process JDF is generated, the processing when the proof processing is executed according to the client's request will be described.

  If the client wishes to proof at the time of accepting the print creation request, the process JDF is generated by the processing of the first embodiment. Thereafter, the process management manager 111 instructs the order receiving / manufacture manager 112 to send an e-mail to the client 102 notifying that the proof is ready.

  The order / entry manager 112 sends an email, the client 102 confirms the content of the email, the client 102 operates the web browser to confirm the proof, and accesses the proof manager 113, the proof process is started. The

  The client 102 operates the web browser and accesses the proof manager 113. Then, the proof manager 113 generates an output sample of a printed material to be generated by the system by the process JDF generated by the process management manager 111, and displays a proof confirmation screen on the UI of the client computer.

  20 is a diagram illustrating an example of a UI screen displayed on the display device included in the client 102 illustrated in FIG. This screen is an example of a proof confirmation screen displayed on the UI of the client computer by the proof manager 113 performing data communication with a device such as a client computer via a communication medium such as the Internet.

  In FIG. 20, 1901 is a proof approval button, 1902 is a proof NG button, 1903 is a folder screen display area for displaying the file structure of document data, and 1904 is an output sample display area for displaying output samples of printed matter.

  When a specific page is double-clicked in the display area 1903 of the folder screen, or when one page of the output sample display area is double-clicked, a preview image in page units is enlarged and displayed in page units.

  When the proof confirmation screen shown in FIG. 20 is displayed, the client 102 operates the proof confirmation screen, refers to the output sample display area 1904, and determines whether the output sample of the displayed printed matter satisfies the request. . If the client 102 determines that the request is satisfied, the client 102 clicks a proof approval button 1901.

  When the proof approval button 1901 is clicked, the proof manager 113 notifies the process management manager 111 that the output sample of the printed matter has been approved by the client.

  The process management manager 111 sends the process JDF in which the output sample of the approved printed matter is created to the print manager 114 and the post-processing manager 115. Thereafter, the image forming system follows the same procedure as in the first embodiment. To produce the final product.

  On the other hand, when the client 102 determines that the output sample of the displayed printed matter does not satisfy the request, the client 102 clicks the proof NG button 1902.

  When the proof NG button 1902 is clicked, the proof manager 113 instructs the process management manager 111 to redo the workflow selection.

  The process management manager 111 regards the workflow described in the process JDF as a selection mistake workflow, and registers the proof processing date with a minus point in the workflow use history table.

  For example, when customer B rejects an output sample of process JDF in which WF2 is described on February 11, 2005, as shown in the workflow usage history table of FIG. 20050211- "is described.

  Thereafter, the process management manager 111 redoes the selection of the workflow and repeats the proofing process until the client 102 approves it.

If the client 102 does not approve all workflows, the proof manager 113 requests the client to correct the printed material information, and instructs the process management manager to redo the selection of printed materials and workflows.

  Then, the image forming system repeatedly executes the process JDF generation process and the proof process described in the first embodiment until an output sample of the printed matter that the client is satisfied with is obtained.

[Preflight processing]
The process of generating only one printed product after generating the process JDF and generating all the printed products and confirming whether or not the print product desired by the client can be generated is called preflight processing.

  As described in the first embodiment, the process management manager 111 selects a unique workflow in step S1813 shown in FIG. Then, after the process management manager 111 generates the process JDF, the process when the preflight process is executed according to the client's request will be described.

  If the client wishes to perform flip writing at the time of accepting the print creation request, the process JDF is generated by the processing of the first embodiment.

  Then, the process management manager 111 corrects the process JDF, and generates a preflight process JDF instructed to generate only one final printed matter. Then, the process management manager 111 sends to the print manager 114 and the post-processing manager 115 to generate one final product (preflight product).

  Next, the process management manager 111 sends the generated preflight product to the client 102 to the delivery / shipment manager 117.

  The client 102 confirms the preflight product. If there is no problem, the client 102 notifies the process management manager 111 that the preflight product is approved via the order reception / manufacture manager 112.

  When the preflight product is approved, the process management manager 111 sends the created process JDF to the print manager 114 and the post-processing manager 115. Thereafter, the image forming system is the same as in the first embodiment. Produce the final product in the procedure.

  On the other hand, when the process management manager 111 determines that the client 102 has notified that the preflight product is not approved, the following processing is performed. That is, the process management manager 111 regards the workflow described in the process JDF as a selection mistake workflow and registers the current date and time in the workflow use history table with a minus point.

  For example, when the customer B does not approve the preflight product generated according to the preflight process JDF in which the workflow WF2 is described on February 11, 2005, the following processing is performed. That is, as shown in the workflow usage history table of FIG. 22 described later, “20050211-” is described in the usage history column of the customer A of the workflow 2.

  Thereafter, the process management manager 111 repeats the above-described processing until the selection of the workflow is performed again and the client approves.

  If the client does not approve even if all workflows are used, the process management manager notifies the client 102 that the desired printed matter cannot be created via the order / manufacture manager 112, and the printed matter information. Request correction.

  According to the embodiment, it is possible to notify the requester in a timely manner that the requested image formation request needs to be corrected.

[Third Embodiment]
When the image forming apparatus or the sheet processing apparatus constituting the image forming system is changed, added, or deleted, the process management manager 111 displays the system process data, the first reticulated workflow, the final product template, and the workflow use history table. To rebuild.

  As an example, processing when the printer B is replaced with the printer D having the monochrome printing function will be described with reference to FIGS. 21, 22, and 23.

  The process management manager 111 recognizes that the printer 105 has been replaced with a monochrome printer. 4 is combined with the printers 104 to 106, the collating machine 121, the bookbinding machine 122, the folding machine 123, and the cutting machine 124 to generate and store system process data.

  Next, the process management manager 111 uses the provisional final product template (similar to the old system) and the system process data according to the procedure described in the first embodiment to use the new first reticulated workflow and the new final product template. Generate and store.

  FIG. 21A to FIG. 21E are diagrams showing a new first mesh workflow generated by the process management manager 111 shown in FIG.

  Next, the process management manager 111 generates a new workflow usage history table as follows. That is, a new workflow usage history table for registering and saving workflow usage dates in units of clients (customers) as past usage history information in the workflow units existing in the new first reticulated workflow shown in FIGS. 21A to 21E. Is generated.

  At this time, the process management manager 111 refers to the old workflow use history table of the old system. Then, the process management manager 111 determines whether the same information as the information described in the workflow belonging process storage area of the new workflow usage history table is stored in the workflow belonging process storage area of the workflow usage history table of the old system. . Here, when the same information is stored, the process management manager 111 copies the usage history information of the workflow to which the relevant workflow belonging process of the old workflow usage history table belongs to the corresponding area of the new workflow usage history table.

  FIG. 22 is a diagram showing a new workflow use history table managed by the process management manager 111 shown in FIG.

  As shown in FIG. 22, usage history information of workflows WF1, WF2, WF6, WF7, WF8, and WF9 is posted.

  In the present embodiment, June 1, 2005 is stored in the new reticulated workflow generation date storage area as the new reticulated workflow generation date.

  Next, a process when the process management manager 111 selects a workflow for generating a unique final product from the second reticulated workflow after the new system is constructed will be described.

  First, the process management manager 111 checks whether a plurality of workflows exist in the second mesh workflow. If a plurality of workflows do not exist here, the only remaining workflow is selected and the process is terminated.

  On the other hand, when there are a plurality of workflows, the process management manager 111 acquires the customer name from the customer information part of the intent JDF. Then, the process management manager 111 refers to the workflow usage history table and acquires usage history information corresponding to the customer name for each workflow described in the second mesh workflow.

  Next, the process management manager 111 refers to the usage history information and checks whether there are a plurality of workflows used in the past for the customer. Here, when there is one workflow, the table generation date of the new workflow usage history is compared with the most recent usage date and time in the workflow usage history for the customer. Select a workflow.

  On the other hand, if the new workflow generation date / time is newer, the process management manager 111 displays the workflow selection screen shown in FIG. 23 and prompts the system operator to click to select the workflow.

  FIG. 23 is a diagram showing an example of a workflow selection screen displayed by the process management manager 111 shown in FIG. This workflow selection screen is displayed in a browser format, and includes a workflow that can be newly used in accordance with a system change, a workflow that has been used in the old system, and a message that prompts the user to select a workflow.

  When the system operator clicks a workflow on the screen shown in FIG. 23, the process management manager 111 sets the workflow selected by the system operator as the selected workflow.

  On the other hand, when there are a plurality of workflows used in the past, the process management manager 111 selects the latest used workflow from the plurality of workflows. Thereafter, the table generation date of the new workflow usage history is compared with the usage date / time in the latest workflow usage history for the customer, and if the workflow usage history usage date / time is found, the workflow is selected.

  On the other hand, if the new workflow generation date is newer, the process management manager 111 displays the workflow selection screen shown in FIG. 23 and prompts the system operator to select the workflow by clicking it. . In other words, the process management manager 111 compares the generation date of the new usage history with the past usage date of the selected workflow when selecting the workflow after the migration to the new system, and determines whether the selection is the first selection after the migration to the new system.

  In the case of the first selection, the “past usage history” in the old system is displayed in the workflow format. Then, the process management manager 111 prompts selection via the UI screen shown in FIG. 23 whether to use a workflow that has been used in the old system, or to use a workflow that has been newly generated when the system is changed. It is.

  When the system operator clicks a workflow on the screen shown in FIG. 23, the process management manager 111 sets the workflow selected by the system operator as the selected workflow.

  If there is no workflow used for the customer in the past, the workflow is selected in the same procedure as in the first embodiment.

  Thereafter, the process management manager 111 adds the selected workflow information to the intent JDF, generates a process JDF, and sends it to the print manager 114 and the post-processing manager 115 to execute the final product generation JOB. To do.

  The print manager 114 and the post-processing manager 115 control devices in the system, execute jobs according to the process JDF, and generate final products.

  When the final product is generated, the process management manager 111 registers the workflow usage history in the workflow usage history table.

  Specifically, the workflow usage date is registered as a plus point in the customer field that uses the workflow in the workflow customer usage history area, and the total of the customer usage history is recalculated and registered in the workflow system usage history area. .

  Thereafter, in accordance with an instruction from the process management manager 111, the file storage manager 116 stores the PDF file, the intent JDF, and the process JDF that are document data. Then, the delivery / shipment manager 117 receives the notification of the end of the production of the final product from the process management manager 111, and ships and delivers the final product to the client 102.

  If a failure occurs in the image forming apparatus or the sheet processing apparatus during execution of the final product generation job, the process management manager 111 generates a third reticulated workflow as follows. That is, after canceling the job being executed, the process management manager 111 deletes the workflow associated with the failed device from the second mesh workflow, and generates the third mesh workflow. That is, the second mesh workflow to be replaced is selected.

  Then, the unique workflow is identified from the third mesh workflow in the same procedure as the procedure for selecting the unique workflow from the second mesh workflow described in the first embodiment. Then, the process management manager 111 generates the process JDF, executes the final product generation JOB, and recovers the failure error.

  If the workflow related to the device in which the failure has occurred is deleted and no workflow for generating the final product exists, the system operator is notified accordingly.

  In the above embodiment, when the device configuration in the image forming system changes, the process management manager 111 creates a new usage history table that inherits the first network workflow or the system history information before the change on the database. To do.

  Whether the system administrator uses a workflow that has been used in the image forming system before the change or uses a workflow that is newly generated in accordance with the system change. Selection is prompted to the user via, for example, the UI screen shown in FIG.

  Thereby, the system administrator can freely select whether to determine a workflow based on the device configuration before the change or on the basis of the device configuration after the device configuration change. Therefore, the convenience for the workflow determination of the system administrator is improved.

[Fourth Embodiment]
The configuration of a data processing program that can be read by the image forming system according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 24 is a diagram illustrating a memory map of a storage medium that stores various data processing programs that can be read by the image forming system according to the present invention.

  Although not particularly illustrated, information for managing a program group stored in the storage medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, a program for installing various programs in the computer, and a program for decompressing when the program to be installed is compressed may be stored.

  The functions shown in FIGS. 3, 10, and 18 in this embodiment may be performed by a host computer by a program installed from the outside. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a storage medium such as a CD-ROM, a flash memory, or an FD, or from an external storage medium via a network. Is.

  As described above, the storage medium storing the software program code for realizing the functions of the above-described embodiments is supplied to the system or apparatus. It goes without saying that the object of the present invention can also be achieved by the computer (or CPU or MPU) of the system or apparatus reading and executing the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the novel function of the present invention, and the storage medium storing the program code constitutes the present invention.

  Therefore, as long as it has the function of the program, the form of the program such as an object code, a program executed by an interpreter, or script data supplied to the OS is not limited.

  As a storage medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card, ROM, DVD, etc. Can be used.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. Then, 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, an ftp server, and the like that allow a plurality of users to download a program file for realizing the functional processing of the present invention on a computer are also included in the claims of 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 It is also possible to execute the encrypted program by using the key information and install the program on a computer.

  In addition, the functions of the above-described embodiments are not only realized by executing the program code read by the computer. For example, based on an instruction of the program code, an OS (operating system) running on the computer performs part or all of the actual processing. Needless to say, the process includes the case where the functions of the above-described embodiments are realized.

  Further, the program code read from the storage 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. After that, based on the instruction of the program code, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing, and the processing of the above-described embodiment is realized by the processing. Needless to say.

  The present invention is not limited to the above embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these are excluded from the scope of the present invention. is not.

  While various examples and embodiments of the present invention have been shown and described, the spirit and scope of the present invention are not limited to the specific descriptions in the present specification by those skilled in the art.

1 is a block diagram illustrating an example of a configuration of an image forming system illustrating a first embodiment of the present invention. It is a figure which shows an example of the workflow of the image forming system of this embodiment. 5 is a flowchart illustrating an example of a first data processing procedure in the image forming system of the present embodiment. FIG. 2 is a diagram showing device process data in the image forming system shown in FIG. 1. FIG. 2 is a diagram showing device process data in the image forming system shown in FIG. 1. FIG. 2 is a diagram showing device process data in the image forming system shown in FIG. 1. It is a figure which shows an example of the temporary final product template which the process management manager shown in FIG. 2 acquires. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 1st reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the final product template list which the process management manager shown in FIG. 2 produces | generates. It is a figure which shows the structure of the usage log table which the process management manager shown in FIG. 2 produces and manages. It is a figure which shows an example of the system process data which the process management manager shown in FIG. 2 builds. It is a figure which shows an example of the system process data which the process management manager shown in FIG. 2 builds. 10 is a flowchart illustrating an example of a second data processing procedure in the image forming system according to the present exemplary embodiment. It is a figure which shows the structure of the intent JDF which the process management management shown in FIG. 2 receives from an order receipt / input manager. It is a figure which shows the structure of the intent JDF which the process management management shown in FIG. 2 receives from an order receipt / input manager. It is a figure which shows the structure of the intent JDF which the process management management shown in FIG. 2 receives from an order receipt / input manager. It is a figure showing the final product decided by intent JDF shown in FIG. It is a figure showing the final product decided by intent JDF shown in FIG. It is a figure showing the final product decided by intent JDF shown in FIG. It is a figure which shows an example of the 2nd reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 2nd reticulated workflow which the process management manager shown in FIG. 2 manages. It is a figure which shows an example of the 2nd reticulated workflow which the process management manager shown in FIG. 2 manages. 10 is a flowchart illustrating an example of a third data processing procedure in the image forming system according to the present exemplary embodiment. FIG. 3 is a diagram showing an example of a workflow usage history table managed by the process management manager shown in FIG. 2. FIG. 2 is a diagram illustrating an example of a UI screen displayed on a display device included in the client illustrated in FIG. 1. It is a figure which shows the new 1st net-like workflow which the process management manager shown in FIG. 2 produces | generates. It is a figure which shows the new 1st net-like workflow which the process management manager shown in FIG. 2 produces | generates. It is a figure which shows the new 1st net-like workflow which the process management manager shown in FIG. 2 produces | generates. It is a figure which shows the new 1st net-like workflow which the process management manager shown in FIG. 2 produces | generates. It is a figure which shows the new 1st net-like workflow which the process management manager shown in FIG. 2 produces | generates. FIG. 3 is a diagram showing a new workflow usage history table managed by the process management manager shown in FIG. 2. It is a figure which shows an example of the workflow selection screen which the process management manager shown in FIG. 2 displays. It is a figure explaining the memory map of the storage medium which stores the various data processing program which can be read with the image processing apparatus which concerns on this invention.

Explanation of symbols

102 Client 104 to 106 Printer 121 Collating Machine 123 Folding Machine 124 Cutting Machine 111 Process Management Manager 112 Order / Submission Manager 113 Proof Manager 114 Print Manager 115 Post-Processing Manager 116 File Storage Manager 117 Delivery / Dispatch Manager

Claims (22)

A management apparatus that manages resources of a plurality of devices having different attributes constituting an image forming system and manages a workflow of an image forming system that uses each device,
When a new image forming system is started up or when the device configuration in the existing image forming system changes, a device process in which each device can be provided to the outside and a process for generating the product is described Creating means for acquiring a file from each device and creating a system process database;
First generating means for searching the system process database and generating a first reticulated workflow showing all workflows that can be used to generate a template for a specified product;
Receiving means for receiving a job definition file in which product information requested for image formation is described in a specific format;
A character string in the job definition file is compared with a character string in the template to identify a final product, and a workflow that is not related to the final product is deleted from the first mesh workflow to generate a second mesh workflow Second generating means to:
Third generation means for generating a process job definition file by specifying a unique workflow based on a selection condition set in advance from the second reticulated workflow;
A management apparatus comprising:   The third generation unit specifies a workflow to be executed according to a selection condition set in advance from the second mesh workflow when the job definition file is newly received or when the job definition file is modified. 2. The management apparatus according to claim 1, wherein a process job definition file is generated.   3. The management apparatus according to claim 2, wherein the preset selection condition is any one of past use history priority, cost priority, schedule priority, and priority to use the same device as much as possible. Registration means for registering the usage history information of the workflow used in the first reticulated workflow in the usage history table for each customer in a point adjustment method;
The said 3rd production | generation means excludes the workflow registered by the minus point in the said usage history table registered in the said registration means from a workflow selection candidate at the time of workflow selection. Management device.   The third generation means selects the existing workflow when there is one workflow used by the customer in the past, and selects the latest used workflow when there are multiple workflows used by the customer in the past. 2. The management apparatus according to claim 1, wherein when there is no workflow used by the customer in the past, the workflow having the highest utilization rate is selected in the image forming system.   When there is no workflow used in the past in the image forming system, the third generation unit selects a workflow registered under other selection conditions after removing a workflow with a negative use count from the selection candidates. The management apparatus according to claim 1.   2. The management apparatus according to claim 1, wherein the other selection condition is one of selection by cost priority, selection by schedule priority, and selection by using the same device as much as possible. When a device configuration in the image forming system changes, a new usage history table that takes over the history information is created,
2. The third generation unit includes a determination unit that compares the creation date of the usage history table with a workflow usage date to determine whether the selection mode should be shifted to the manual selection mode. Management device. A selection means for selecting whether to use a workflow used in the image forming system before the system change or to use the workflow after the system change when the device configuration in the image forming system changes;
The first generation unit includes all workflows that can be used to generate a template of a specified product corresponding to either the system configuration before or after the change based on a workflow selection instruction by the selection unit. The management apparatus according to claim 1, further comprising: generating a first reticulated workflow indicating   The third generation unit analyzes the use history information of the past workflow registered for each customer by the registration unit, and calculates the usage rate by calculating the number of times the workflow is used. The management device described. A workflow specifying method in a management apparatus that manages resources of a plurality of devices having different attributes constituting an image forming system and manages a workflow of an image forming system that uses each device,
When a new image forming system is started up or when a device in the existing image forming system changes, a device process file that describes a product that each device can provide to the outside and a process for generating the product And a creation step to create a system process database by acquiring from each device,
A first generation step of searching the system process database to generate a first reticulated workflow showing all workflows that can be used to generate a template for a specified product;
A reception step of receiving a job definition file in which product information requested for image formation is described in a specific format;
A character string in the job definition file is compared with a character string in the template to identify a final product, and a workflow that is not related to the final product is deleted from the first mesh workflow to generate a second mesh workflow A second generating step,
A third generation step of generating a process job definition file by specifying a unique workflow based on a selection condition set in advance from the second mesh workflow;
A workflow specifying method characterized by comprising:   In the third generation step, when a job definition file is newly received or when the job definition file is modified, a workflow to be executed according to a selection condition preset from the second mesh workflow is specified. 12. The workflow specifying method according to claim 11, wherein a process job definition file is generated.   13. The workflow specifying method according to claim 12, wherein the preset selection condition is any of past usage history priority, cost priority, schedule priority, and priority on the same device usage as much as possible. A registration step of registering the usage history information of the workflow that exists and used in the first reticulated workflow in the usage history table for each customer in a point adjustment method;
12. The third generation step according to claim 11, wherein when the workflow is selected, the workflow registered as a minus point in the usage history table registered in the registration step is excluded from the workflow selection candidates. Workflow identification method.   In the third generation step, when there is one workflow used by the customer in the past, the existing workflow is selected. When there are a plurality of workflows used by the customer in the past, the latest used workflow is selected. The workflow specifying method according to claim 11, wherein when there is no workflow used by the customer in the past, the workflow having the highest usage rate is selected in the image forming system.   In the third generation step, when a workflow that has been used in the past in the image forming system does not exist, a workflow having a negative use count is excluded from selection candidates, and a workflow registered according to another selection condition is selected. The workflow specifying method according to claim 11.   12. The workflow specifying method according to claim 11, wherein the other selection condition is any one of selection by cost priority, selection by schedule priority, and selection by using the same device as much as possible. When a device configuration in the image forming system changes, a new usage history table that takes over the history information is created,
12. The third generation step includes a determination step of determining whether the selection mode should be shifted to the manual selection mode by comparing a creation date of the use history table with a workflow use date. Workflow identification method. A selection step of selecting whether to use a workflow used in the image forming system before the system change or a workflow after the system change when the device configuration in the image forming system changes;
The first generation step includes all workflows that can be used to generate a template for a specified product corresponding to either the system configuration before or after the change based on a workflow selection instruction in the selection step. The workflow specifying method according to claim 11, wherein a first reticulated workflow is generated.   12. The third generation step of analyzing usage history information of a past workflow registered for each customer in the registration step, calculating a usage rate by calculating the number of times the workflow is used. The workflow identification method described.   A computer-readable storage medium storing a program for causing a computer to execute the workflow specifying method according to claim 11.   A program for causing a computer to execute the workflow specifying method according to any one of claims 11 to 20.

Images