JP2008117133A - Management system and order processing system using same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a management system for performing stable management without making the management of a whole system complicated even when two or more devices for executing the same type of processing are connected. <P>SOLUTION: This management system is provided with at least one device line configured of a master device which first receives a job ticket in one processing process and at least one sub-device serially connected to the master device for executing the same type of processing as the master device, and configured to manage the execution of a job in the unit of the device line. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a management system that manages execution of a process in a processing system in which two or more apparatuses that execute the same type of process are connected, and an order processing system that uses the management system.

Conventionally, two or more processing apparatuses are connected to one network system, and these apparatuses are properly used to cope with increase / decrease in production lots or on-demand production. For example, in production of printed matter and image reproduction products such as photographic prints, when a production lot is large, an apparatus capable of high-speed processing is used, or a plurality of processing apparatuses are used simultaneously.
As a management method for such a conventional processing system, the management server manages all processing devices connected to the network, and can be performed manually or automatically depending on the contents of processing to be executed and the capabilities and status of the devices. There is a method of selecting a device that executes the processing.

  Further, in Patent Document 1, when print processing is executed by an arbitrary output device among a plurality of output devices, a job ticket for the output device is generated based on the identification information of the output device and the instruction information of the print processing, A print control apparatus that controls print processing by the output device based on the generated job ticket and print data is described. In this print control apparatus, a plurality of print devices are directly connected to the print server, and the print server holds the ID of the print device on which print processing is to be executed in the job ticket. It is inspected whether or not it matches the ID.

JP 2003-323271 A

  In the conventional technique for managing all the plurality of processing devices by connecting them to the management server as described above, there is a problem that the control and management of the entire system becomes complicated as the number of devices constituting the processing system increases.

  In addition, in the above-described conventional technology, after processing information or processing target data is transmitted to a device selected as a processing execution device, the processing device fails, becomes overloaded, or a delivery date is advanced, If you want to reassign the execution of the process to another device with the same capability, select the processing device again and retransmit the processing information or store it from the management server to the device. Therefore, it is necessary to rewrite the processed information and move the processing information and the processing target data to another apparatus, and there is a problem that the system management is complicated and the difficulty of the application is high.

  In addition, when automatically selecting a processing execution device or performing scheduling in the management server, it is necessary to grasp the capabilities and states of all the devices that make up the system. Applications for selecting processing devices and job scheduling There is a problem that is difficult.

  On the other hand, digital image data obtained by photoelectrically reading an image photographed on photographic film or digital image data obtained by photographing with a digital camera is used. Processing is performed to reproduce a photographed image on a photographic print or other product.

In an order processing system that performs such processing, the order image is input by reading a conventional photographic film, reading a recording medium on which photographed image data is recorded by a digital camera, or transferring the image data via a network. It is also done by.
In addition to photographic prints, products to be printed are used in a wide variety such as T-shirts, mugs, calendars, and albums. Various printers such as a silver salt photographic system, an electrophotographic system, and various ink jet systems can be used for outputting images to various products. There is also a service for writing image data after image processing to a recording medium such as a CD or a DVD. And the types of services can be expanded further in the future.
In order to deal with such a wide variety of orders, the order processing system is required to freely connect various devices.

  However, the conventional order processing system is configured to have a control unit dedicated to the system in order to control each device constituting the system. Therefore, even if a device is added or changed to another model in a photo lab shop or the like that has introduced an order processing system, the device is organically connected to the existing system and controlled by the same control unit. This is difficult, and there is a problem that it is difficult to meet the demands of flexibly improving existing systems and expanding processing functions and services that can be provided.

In response to this problem, the present applicant has created a new concept called work instruction information (job ticket) for instructing image reproduction processing across a plurality of processes, and the different processing included in one order is determined by this work instruction information. We are considering to manage the process as a whole. According to this, it is possible to flexibly cope with various order formats, and it is possible to construct an order processing system having excellent flexibility and expandability.
However, in a system that manages and manages different processing steps in this way, the above-described problems that the control and management of the entire system becomes complicated as the number of devices constituting the processing system increases, and countermeasure applications and scheduling in the event of failure, etc. The problem of the difficulty level of the application is even greater.

The first object of the present invention is to solve the above-mentioned problems of the prior art and perform stable management without complicating the management of the entire system even when two or more devices that execute the same type of processing are connected. It is to provide a management system that can be performed.
In addition, the second object of the present invention is a system that can easily cope with changes and additions of devices by using such a management system, has excellent expandability and flexibility, and is stable. To provide an order processing system that can be managed.

In order to solve the above problems, the present invention is a management system that manages the execution of a job based on a job ticket that describes the contents of the job,
One or more device rows each including a master device that first receives the job ticket in one processing step and one or more sub-devices that are connected in series to the master device and execute the same type of processing as the master device. ,
A management system is provided that manages job execution in units of the apparatus row.

Here, each of the master device and the sub device includes an acceptance management unit that manages job acceptance based on a set job acceptance condition.
When the job described in the job ticket satisfies the job acceptance condition, the acceptance management unit receives the job ticket and executes a corresponding processing step of the job, and the job described in the job ticket When the job acceptance condition is not satisfied, the job ticket is preferably transferred to the succeeding sub-device.

Further, it is preferable that the job acceptance condition of each device is set so as not to accept a job when the device is out of order or when the load is exceeded.
Further, the job acceptance condition of each device is set to accept a job whose priority is in a certain range, and at least one of the master device and the one or more sub-devices is the priority of the job to be accepted. It is preferable that the ranges are different.

  In addition, the master device holds capability information of its own device and all the sub devices connected thereto, and executes a device described in the job ticket based on the held capability information. Preferably, if the determined device is the sub device, the job ticket is transferred to the sub device, and if the determined device is the master device, the job ticket is received.

  The master device is preferably determined as the job execution device preferentially from the sub device.

In order to solve the above-mentioned problem, the present invention is an order processing system that accepts an input image and a playback processing order of the input image, and performs playback processing according to the playback processing order.
Job ticket generation for generating one job ticket for each order, which describes the contents of the process for the reproduction process according to the order contents of the reproduction process order, the execution order of the process, and the information indicating the execution destination of the process And
One of the above management systems,
The job ticket generation unit refers to the capability information of the master device, selects the master device in the device row that can execute the step for each step of the job, and selects the selected master device in the step. An order processing system is provided that generates the job ticket described as an execution destination.

Further, the present invention is an order processing system that accepts an input image and a playback processing order of the input image and performs a playback processing according to the playback processing order,
Job ticket generation for generating one job ticket for each order, which describes the contents of the process for the reproduction process according to the order contents of the reproduction process order, the execution order of the process, and the information indicating the execution destination of the process And
One of the above management systems,
The job ticket generation unit refers to capability information of its own device held by the master device and capability information of all the sub devices connected thereto, and can execute the step for each step of the job. An order processing system is provided that selects the master device in a device row and generates the job ticket in which the selected master device is described as an execution destination of the process.

Here, an order receiving unit that receives an order for the reproduction process of the input image;
A list creation unit that creates a list of order contents that can be accepted based on the capability information of its own device held by the master device and the capability information of all the sub devices connected thereto, and presents the list to the order reception unit Are preferably provided.

According to the management system of the first aspect of the present invention, even when two or more devices that execute the same type of processing are connected to the processing system, stable management is performed without complicating the management of the entire system. be able to.
Moreover, according to the order processing system which is the 2nd aspect of this invention, it can respond easily to the change and addition of an apparatus, is excellent in expandability and flexibility, and can perform the stable management.

A management system according to the present invention and an order processing system using the management system will be described below in detail based on preferred embodiments shown in the accompanying drawings.
In the following, an example in which the management system of the present invention is used in an order processing system will be described. However, the management system of the present invention is not limited to this, and is a system in which two or more devices that execute the same type of processing are connected. If it exists, it can be employed in various processing systems. Further, the order processing system of the present invention is not limited to the following image reproduction order processing system, and can be employed in various order processing systems that execute processing according to orders.

  FIG. 1 is a block diagram showing a schematic configuration of an embodiment of an order processing system according to the present invention. The order processing system 10 shown in FIG. 1 has various processes such as print creation, image reproduction on various products such as albums, photobooks, postcards, T-shirts and mugs, and storage of image data on recording media such as CDs. An order processing system that accepts an order for image reproduction processing and performs reproduction processing according to the order for the reproduction processing. The order processing system 10 includes an order receiving unit 12, a workflow layer (Wf layer) 14 that is a management unit, and an activity layer (Ac layer) 16 that is an execution unit. The workflow layer 14 and the activity layer 16 constitute an embodiment of the management system of the present invention.

In FIG. 1, the workflow layer 14 and the activity layer 16 conceptually show the software structure of the order processing system 10.
The order processing system 10 is a distributed system in which a plurality of devices cooperate to execute one order. That is, the order processing system 10 is configured by a plurality of devices having different functions in the hardware structure, and each device shares the functions, so that the workflow layer 14 and the activity layer 16 shown in FIG. Form a software structure consisting of
Specifically, for example, the order processing system 10 includes an order receiving machine that functions as the order receiving unit 12, a controller that shares a plurality of functions in the workflow layer 14 and the activity layer 16, an input machine, an output machine, and the like. can do. Such an apparatus configuration example will be described later.

In FIG. 1, a broken line frame between layers or between components in a layer schematically shows an interface. An interface corresponding to the configuration of each unit may be used as an interface between layers or components.
In order to exchange information between the order receiving unit 12 and the workflow layer 14, an interface conforming to a predefined laboratory information order standard is used. Therefore, any personal computer or the like can function as the order receiving unit 12 by providing or interposing software for generating order information compliant with the laboratory information order standard.

  The order receiving unit 12 is a part that receives an image reproduction processing order such as print creation from a customer. The order receiving unit 12 receives the image data of the order contents and the order target image (input image), sends the order content information (order information) to the workflow layer 14, and sends the order target image data to the order receiving unit 12. Store in an internal or external storage unit (not shown).

  The order receiving unit 12 receives an acceptable list representing orders that can be handled by the order processing system 10 from the workflow layer 14 (workflow server 26 described later) when accepting a customer order, and based on the acceptable list. The menu of the types of orders that can be accepted is displayed on a monitor or the like. Thereby, the customer can select a desired order from orders that can be handled by the order processing system 10.

The workflow layer 14 is a part that functions as a workflow management unit in the order processing system 10, and includes an order management unit 20, an order execution instruction unit 22, and a device public information database 24.
The order management unit 20 includes a workflow server (Wf server) 26, an order information database 28, a production information database 30, and a template library 32.

The workflow server 26 checks the capabilities of the devices in the order processing system 10 by referring to the device public information held in the device public information database 24 to be described later. An acceptable list that is an output list is created, and the acceptable list is sent to the order receiving unit 12. That is, the workflow server 26 functions as an acceptable list creation unit.
The acceptable list can be changed by operator's operation in order to reflect the hardware configuration of the system, installed software, and setting values in the lab that uses the system (such as print size restrictions). Good.

Further, the workflow server 26 receives the order information from the order receiving unit 12, registers it in the order information database 28, and based on the order information and the system status, the job ticket which is work instruction information in the order processing system 10. (Job Ticket) is generated. That is, the workflow server 26 also functions as job ticket generation means. Then, the generated job ticket is sent to the activity layer 16 that executes an image reproduction job (processing work). The activity layer 16 executes the job according to the job ticket.
In addition, the workflow server 26 monitors the execution status of the job defined in the job ticket.

In the present invention, the job ticket corresponds to a so-called work instruction for processing an order in the order processing system 10, and includes an execution order (process flow), processing contents, and execution destination of processes for processing the order. Information defining (device). One job ticket is issued for each order.
The format of the job ticket is standardized so as to be versatile for various apparatuses used in the photo lab.
For example, information described in a job ticket includes process type information such as image data input, verification, synthesis, and output, information on special processing such as red-eye processing, trimming, date printing, and template synthesis, and output products. Output related information such as type, print size, and output resolution can be mentioned, and these information are described in a format conforming to a predetermined standard that can be understood by various processing apparatuses. FIG. 4 shows an example of information described in the job ticket, and FIG. 5 conceptually shows an example of the job ticket.

  The workflow server 26 selects a job ticket template in which a process capable of processing an order is set from a plurality of job ticket templates held in the template library 32, and generates a job ticket using the template. The job ticket generation method is not particularly limited, and may be a method that generates without using a template.

  The order information database 28 is a part that stores information on unprocessed orders currently accepted. The order information sent from the order receiving unit 12 is registered in the order information database 28 by the workflow server 26. The order information registered in the order information database 28 is used for displaying a list of orders in the order execution instructing unit 22 and is used for generating a job ticket in the workflow server 26.

The production information database 30 is a part that stores information related to the job execution status in the activity layer 16. The activity layer 16 includes a plurality of activity components Ac that execute one or more of a plurality of steps necessary for image reproduction processing (an image input step, a verification step, an image processing step such as image composition, a print output step, etc.). The workflow server 26 is notified of production execution information (such as start and end of work) in each activity component Ac as production information, and is recorded in the production information database 30 by the workflow server 26.
The production information recorded in the production information database 30 is used for process management in the order processing system 10.

In the order management unit 20, the workflow server 26 requests production information (process) from a customer (user) or a lab manager (operator) via a user interface connected to the order reception unit 12 or other workflow layer 14. When there is a progress inquiry), the production information can be returned with reference to the production information database 30.
The workflow server 26 refers to the production information database 30 when the order receiving unit 12 receives an order, calculates a delivery date, and replies to the order receiving unit 12.

Further, in the order processing system 10, in addition to the normal process (normal mode, normal delivery process considering allowance time), the process is prioritized by the normal process, so that the delivery time shorter than normal (for example, from the reception of the order) Short delivery time processing (express mode) that performs processing in a few minutes) can be selectively executed. The workflow server 26 refers to the production information database 30 and manages whether each job defined in the job ticket currently being executed in the order processing system 10 is progressing according to the schedule, and is waiting for execution. Considering the processing contents of the job, if a new order is placed, the processing process is also scheduled.
Processing of job ticket generation, acceptance list creation, delivery date calculation, express mode availability determination and scheduling processing by the workflow server 26 will be described in detail later.

The order execution instructing unit 22 is a part for instructing execution of orders for unprocessed orders registered in the order information database 28.
The order execution instructing unit 22 is connected to a display unit (monitor or the like) (not shown), obtains list information of orders (jobs) registered in the order information database 28 via the workflow server 26, and the list information Is displayed on the display. The order execution instruction unit 22 is connected to an instruction input unit (not shown) (a keyboard, a mouse, a touch panel provided in the display unit, etc.), and is executed from an order list by an operator operating the instruction input unit. When is selected, an execution instruction (information) for the selected order is issued and transmitted to the workflow server 26.
Alternatively, the order execution instruction unit 22 may automatically issue an order execution instruction without an order selection by the operator.

The device public information database 24 is a part that holds device public information that represents the capabilities of the respective devices constituting the order processing system 10.
The device public information is various pieces of information that are disclosed to the outside (device users and other devices) by the components of the device constituting the order processing system 10, and the capability information of the activity component Ac belonging to the activity layer 16. Activity information (Ac information). The activity information includes a name for identifying the activity component Ac, a process flow that can be executed by the activity component Ac, potential capability information of the activity component Ac, and current capability information.
As described above, the order processing system 10 is a distributed system in which a plurality of devices cooperate to execute one order. For this reason, in the execution of processing, information exchange between devices is essential. The device public information is used for information exchange between the devices.

The potential information of the activity component Ac is information on the capability potentially held by the activity component Ac (device responsible for the function). In other words, it is information on the capability that can be executed to the maximum in the device specification.
As an example, in the case of the activity component Ac of the print output process, information on the print size that can be output is given as the specification of the corresponding printer.

The current capability information of the activity component Ac is information on the capability that the activity component Ac (device responsible for the function) can currently use by setting the device.
As an example, information on the print size that can be output using the paper size currently set in the printer among the print sizes that can be output as the potential is given.

The device public information held in the device public information database 24 is used in the workflow server 26 to create an acceptable list representing orders that can be handled by the order processing system 10 and to generate a job ticket.
The potential capability information of the activity component Ac is mainly used for creating the acceptable list, and both the current capability information and the potential capability information of the activity component Ac are used for generating the job ticket.

The activity layer 16 functions as an execution unit for image reproduction processing. The activity layer 16 executes various processes on the processing target image according to the job ticket generated by the workflow server 26 of the workflow layer 14.
The activity layer 16 has a plurality of activity components Ac that execute one or more of the plurality of steps necessary for the image reproduction process, and a predetermined process is performed by the predetermined activity component Ac in accordance with the job ticket. Run in the order. FIG. 1 shows three activity components Ac (Ac1, Ac2, Ac3) as an example. The activity component Ac of the activity layer 16 is shared by the above-described plurality of devices constituting the order processing system 10 in hardware.

As described above, the order processing system 10 provides an interface (I / F) between the workflow layer 14 that is the workflow management unit and the activity layer 16 that is the execution unit that executes the workflow to various apparatuses. A job ticket configured according to a standard having versatility, and a plurality of devices that share a plurality of activity components Ac in the activity layer 16 perform jobs based on the job ticket.
By executing and managing jobs in the input machine and output machine that make up the order processing system 10 using common information called job tickets, it is possible to easily cope with changes and additions to the devices that make up the order processing system 10 It is possible to provide a system that is excellent in scalability and flexibility.

  In the activity layer 16, when there are two or more activity components Ac that execute the same kind of processing in one processing step, these activity components are logically daisy chain connected (series connection). An activity component column (hereinafter referred to as Ac column) is formed. The Ac column includes one master Ac (master device) directly connected to the workflow layer 14 and one or more sub Acs (sub devices) connected in series to the master Ac. The master Ac and all the sub Acs may be physically connected in series, or may be physically connected in parallel. Activity components Ac (devices having the Ac) connected in a daisy chain are managed in units of the Ac columns (device columns).

  FIG. 2 is a diagram conceptually showing a work part of each process in job ticket generation and job execution in the workflow layer 14 and the activity layer 16 in FIG. In FIG. 2, the left half shows the functional units inside the workflow server 26 of the workflow layer 14, and the right half shows the activity component Ac of the activity layer 16.

  In the example of FIG. 2, three devices (or activity components) having the same ability to execute the same type of processing for the three types of processing steps A, B, and C are prepared. As an apparatus of processing step A, apparatus A-1 as a master apparatus is connected to workflow layer 14, apparatus A-2 as a sub apparatus is connected to apparatus A-1, and apparatus A-2 is a sub apparatus. Device A-3 is connected. Similarly, in the processing B and the processing C, in the order of the master device B-1, the sub device B-2, and the sub device B-3, or in the order of the master device C-1, the sub device C-2, and the sub device C-3. Are connected in series to form an Ac row.

  From the workflow server 26 (see FIG. 1) of the workflow layer 14 that is a management system, among the activity components that constitute the activity layer 16, the master Ac, the device A-1, the device B-1, and the device C-1 are visible. It is like that. The three activity components Ac1, Ac2, and Ac3 of the activity layer 16 shown in FIG. 1 correspond to the device A-1, the device B-1, and the device C-1, respectively.

  In each Ac column, since the master Ac and the sub Ac have the same ability, the workflow server 26 can generate a job ticket and create an acceptable list if only the master Ac is viewed. it can. As will be described later, in the Ac column, the job queue of the master Ac is emptied to the end. Therefore, if only the master Ac notifies the workflow server 26 of the job execution status (production information) in itself, the workflow server No. 26 can perform delivery date calculation, whether or not express mode is possible, and scheduling.

Each master Ac may hold its own capability information and capability information of all sub-devices connected in series to the master Ac. For example, in the column of the device A, the device A-1 holds the capability information (latency capability information and current capability information) of the device A-2 and the device A-3 in addition to the capability information of the device A-1 itself. May be. In this case, the master Ac publishes the held all ability information as activity information (Ac information) to the workflow layer 14 in FIG.
In addition, the master Ac may notify the workflow server 26 of the work execution status of each activity component in the Ac column as the execution status of the Ac column.

Next, the configuration of the workflow server 26 and the activity layer 16 of the workflow layer 14 and the processing flow thereof will be described.
As shown in FIG. 2, the workflow server 26 of the workflow layer 14 acquires the activity information published by the master Ac as the capability information of the master Ac by the state acquisition / job control unit 34 inside the workflow server 14, and discloses the apparatus. Save in the information database 24. Similarly, the workflow server 26 acquires the execution status information notified from the master Ac by the status acquisition / job control unit 34 as the execution status of the master Ac, and records it in the production information database 30. The workflow server 26 controls the job by using these pieces of information in an apparatus capability analysis unit 35 and a delivery date calculation unit 36 described later.

  The workflow server 26 uses the device capability analysis unit 35 to analyze the device capability by referring to the device public information database 24 (that is, using the master Ac capability information acquired by the status acquisition / job control unit 34). A possible list is created and sent to the order receiving unit 12 (see FIG. 1). Furthermore, the workflow server 26 analyzes the apparatus capability by referring to the production information database 30 (that is, using the execution status of the master Ac acquired by the status acquisition / job control unit 34) in the apparatus capability analysis unit 35, It is determined whether an order can be accepted in the express mode, and if so, the order acceptance unit 12 is notified of that.

The order reception unit 12 in FIG. 1 receives a notification that the express mode is possible, and displays on the order reception screen that the express mode can be selected. A customer who places a new order can select the express mode or the normal mode by looking at the information.
On the other hand, if the job queue of the master Ac is full, the workflow server 26 notifies the order reception unit 12 that the express mode cannot be used. In this case, the order reception unit 12 displays on the order reception screen that the current express mode cannot be received. Alternatively, the express menu selection menu may not be displayed.

  When the contents of the order are input from the order receiving unit 12, the workflow server 26 refers to the production information database 30 by the delivery date calculation unit 36 (that is, the master Ac acquired by the status acquisition / job control unit 34). The delivery date calculation is executed (using the execution status), and the calculated delivery date is returned to the order receiving unit 12.

  Next, the workflow server 26 executes scheduling in the scheduling unit 37. Specifically, with reference to the order information database 28 and the production information database 30, an order will be placed from the processing content of the job currently being executed, the processing status of the job being executed, and the processing content of the job waiting to be executed. Create a schedule by determining the job processing order.

  When an order confirmation instruction is sent from the order receiving unit 12, the workflow server 26 uses the JobTicket generation unit 38 to process one job based on the order information and the device public information database 24 for the one order. Generate a ticket.

  As described above, the workflow server 26 refers to the device public information database 24 and the production information database 30 in each unit of the device capability analysis unit 35, the delivery date calculation unit 36, the scheduling unit 37, and the JobTicket generation unit 38, and the information Based on the above, each process is executed, thereby managing the execution of the process in each activity component. Here, in the apparatus public information database 24 and the production information database 30, capability information and execution status information are recorded only for the first master Ac in the Ac column of each process, and the workflow server 26 is only for the master Ac. You should be conscious of.

  In this way, by configuring a plurality of devices having equivalent capabilities logically or physically connected in a daisy chain and managing them in units of the devices, the workflow server 26 can generate job tickets, Even when there are many activity components that execute the same type of processing when performing scheduling etc., it is not necessary to consider all of them, and the same simplicity as when there is only one activity component for each processing step Thus, the execution of each process can be managed. It is also possible to apply a management function of a system designed by a conventional single device.

  In addition, the functions of each process such as job ticket generation and scheduling can be used as they are, regardless of the number of activity components in each process. Therefore, it is possible to quickly cope with the increase / decrease of the apparatus. When adding an activity component (device), it is only necessary to set the connection to the last device of the daisy chain in the Ac column (device row), and the setting is simple.

The job ticket Job-100 generated by the JobTicket generation unit 38 is first sent to the device A-1 (corresponding to Ac1 in FIG. 1) which is the master device of the process A among the activity components Ac of the activity layer 16. It is done.
Here, it is assumed that the job ticket generated by the JobTicket generation unit 38 is Job-100, and Job-100 is a job ticket for executing the process A, the process B, and the process C.

  In the device A-1, the queue management unit makes a transfer request for the transmitted job ticket Job-100 to the subsequent device A-2. The queue management unit is a part that manages job acceptance. The device A-2 determines whether or not the queue management unit can execute the job of the process A of the job ticket Job-100 with its own device, and indicates that it is acceptable or not acceptable according to the determination result. A response signal is sent to apparatus A-1. If there is an acceptable response, apparatus A-1 transfers job ticket Job-100 to apparatus A-2. If there is an unacceptable response, apparatus A-1 executes the job on its own apparatus.

  The device A-2 determines whether the job can be accepted or not based on a predefined job acceptance condition. Here, the job acceptance condition is set so as not to accept a job when a device malfunctions or a load is exceeded. Therefore, when the device has failed or when the queue of the device A-2 is full, the queue management unit of the device A-2 refuses to accept the job.

  When receiving the job ticket Job-100, the queue management unit of the device A-2 makes a transfer request for the job ticket to the subsequent device A-3. The queue management unit of the device A-3 determines whether or not the job of the process A of the job ticket Job-100 can be executed by its own device, and a response signal indicating that the job is acceptable or not according to the determination result. To device A-2. If there is an acceptable response, apparatus A-2 transfers job ticket Job-100 to apparatus A-3. If there is an unacceptable response, apparatus A-2 executes the job on its own apparatus. The method for determining whether or not to accept the job and the conditions for accepting the job are the same as in the case of apparatus A-2.

  When the process A is completed, the apparatus that executed the process transfers the job ticket to the master apparatus of the next process B. In the process B, the execution apparatus is determined in the same manner as described above. The execution device of the process B transfers the job ticket to the master device of the next process C after executing the process.

  In the example of FIG. 2, in step A, the job ticket Job-100 is transferred to the device A-3, and also in step B, it is transferred to the terminal device B-3. Further, in step C, the queues of the devices C-3 and C-2 are filled and cannot be transferred to the device C-2 because the load is exceeded, and the job ticket Job-100 is sent to the device C-1. Is entered.

  In this way, the job ticket is transferred to the terminal device as much as possible in the Ac column of one process. That is, the job is filled from the end side of the Ac column. With this configuration, the master device is in a state where there is an empty queue in the entire Ac column, so that the workflow server 26 can execute a job by referring to the capability information of the master device in the Ac column. It can be determined whether or not it can be executed immediately. Therefore, the workflow server 26 can determine whether or not the express mode can be accepted, perform delivery date calculation, and schedule by referring to only the capability information of the master device.

  Also, by setting the job acceptance conditions to logically connect devices with the same capacity in a daisy chain and not accept jobs when the device fails or overload, one device fails or overloads Even if a failure such as the above occurs, the upstream device executes the job, so as in the conventional system, select the processing device again and resend the job ticket, or from the management server to the device. Advanced processing such as rewriting the stored processing information and moving the processing information and processing target data to another device is not necessary.

  In this embodiment, job acceptance is autonomously selected by each sub-device based on job acceptance conditions defined for each device, so even if there are many activity components that execute the same process. It is possible to prevent the control from becoming complicated. In addition, since devices having the same capability are logically connected in a daisy chain, job ticket generation need only be conscious of the first master device in the chain. Furthermore, when adding a device, it is only necessary to set the connection to the end device of the daisy chain, and setting is not required in the workflow server 26 as the management unit, so the setting is simple.

  In the above example, in the devices A-2 and A-3 as the sub devices, the job acceptance condition is set so as not to accept the job when the device is faulty or the load is exceeded. In this example, the job queue is sequentially filled from the device A-3. On the other hand, even when the device A-2 and the device A-3 queue are not filled, when the device A-2 fails, the job acceptance condition of the device A-2 is not satisfied, and the device A-1 Since the job ticket cannot be transferred to -2, the job is executed by the device A-1.

On the other hand, as another example, it is also preferable that the job acceptance condition is set so that a job ticket is temporarily received when there is a succeeding apparatus when the apparatus fails. In this example, when apparatus A-2 fails, apparatus A-2 receives a job ticket once in response to a transfer request from apparatus A-1, and receives the job ticket as apparatus A-3. Forward to. Then, the device A-3 executes the job.
If the device A-3 is also in a failure or overload state, the device A-3 may transfer the job ticket to the master device A-1 and select the device again.
Alternatively, the queue management unit of the master device and sub-device can refer to the status of the subsequent sub-device, and if the job ticket cannot be received even if there is a subsequent device, it is set not to receive the job ticket. May be.

  One device by logically connecting devices of the same capability in a daisy chain as in each of the above examples, and setting a job acceptance condition so as not to accept a job when the device fails or is overloaded Even if a failure such as failure or overload occurs, jobs can be transferred without being transferred or automatically transferred to other devices in the device row, making the system highly fault tolerant. be able to. As in the conventional system, the processing device is selected again and the job ticket is retransmitted, or the processing information stored in the device is rewritten from the management server to move the processing information and processing target data to another device. Such advanced processing and advanced applications for that are not necessary.

As a further different example of the present embodiment, a priority may be set for a job, and a job acceptance condition of each device may be set so that a job with a priority within a predetermined range is accepted. The job priority is a degree to which priority should be given to the processing of the order.
For example, the highest priority order for the express mode specified, lower priority for orders without delivery date specification, prioritizing orders from digital image data over orders from photographic film, setting up stores, etc. Priorities can be set for each type of order, such as placing an order from an automated order acceptance machine over an order from the Internet.

  The priority set for the job is written in the job ticket. The queue management unit of each activity component constituting one Ac column compares the priority described in the job ticket with its own acceptance condition, and accepts the job if the acceptance condition is satisfied, and if not, Transfer the job ticket to the subsequent activity component.

In the case of this example, acceptance conditions different from those of other apparatuses are set in at least one of the apparatuses constituting one Ac row.
The process A of FIG. 2 will be described as an example. For example, among the priority levels 0 (high priority level) to 10 (low priority level), only the job with the priority level 0 is the receiving condition of the device A-1. Is set to receive a job having a priority of 1 to 5 in the receiving condition of the device A-2, and a job having a priority of 6 to 10 is received as the receiving condition of the device A-3. Thus, it is possible to set different ranges of priorities for each device. In this example, the device corresponding to the priority of the job executes the job.
Since the job ticket cannot be transferred when the queue of the subsequent device is full, the upstream device may execute the job even if the priority is lower than the reception condition set.

  Further, for example, the reception condition of the device A-1 is set so as to receive only jobs whose priority is within a predetermined range (for example, 0), and the reception condition of the device A-2 and the device A-3 includes the priority. It can also be configured to receive one or more jobs or priority restrictions. Then, for jobs that are not executed by the device A-1, the job execution device may be determined so as to fill the job queue from the device at the end of the Ac column, as in the above example.

In any case, in order to enable the workflow server 26 (see FIG. 1) to determine the execution status of the job by looking only at the master device, only the high priority job is processed by the master device. It is preferable to set to.
Also in this example, it is preferable to use the job acceptance condition in the above-described example, that is, the condition that the job is not accepted when the apparatus is faulty or the load is exceeded.

  Each example of the above embodiment is effective when the Ac column has the same capability and can process the job of the job ticket with any device (activity component).

Next, an embodiment that is effective when the Ac column is composed of a plurality of devices (activity components) having different capabilities will be described.
As long as the Ac column is a device that executes the same kind of processing, it may be configured by devices having different capabilities. In this case, the processing that can be executed by the device is set as the job acceptance condition of each device, the job ticket whose processing content matches the acceptance condition is accepted, and the job is Make it run.

In this embodiment, each master Ac holds its own capability information and capability information of all sub-devices connected in series to the master Ac. For example, in the column of the device A, the device A-1 holds the capability information (latency capability information and current capability information) of the device A-2 and the device A-3 in addition to the capability information of the device A-1 itself. To do. Then, the master Ac publishes the held all ability information to the workflow layer 14 of FIG. 1 as activity information (Ac information) in the Ac column.
In addition, the master Ac notifies the workflow server 26 of the execution status of work in each activity component in the Ac column.
The workflow server 26 in FIG. 1 generates a job ticket and creates an acceptable list based on the capability information of the Ac column released by the master Ac, and also checks the delivery status of the work in the Ac column. Performs calculation, express mode judgment, and scheduling.

  Referring to the configuration of FIG. 2, for example, when the process C is an output process, the apparatus C-1 and the apparatus C-2 can output L size print and 2L size print, and the apparatus C-3 can output L. If the size print can be output but the 2L size print cannot be output, the L size print job ticket is sent to the device C-3 unless the queue of the device C-3 is filled, but the 2L size print job ticket is It cannot be transferred to the device C-3 and is executed by the device C-2.

If the device C-2 cannot output the A4 size print and the device C-3 can, the device C-2 cannot receive the job ticket for the A4 size print and transfers it to the device C-3.
As described above, the queue management unit of the device C-1 that is the master device has the capability information of all the devices in the Ac column, and the job ticket is generated based on the capability information. Orders that cannot be processed by any device in the column should not be entered into the Ac column of device C. That is, the job of the job ticket sent to the Ac column is received by any device in the Ac column, and the process is executed.

  However, if the corresponding device breaks down after receiving the order, or if it becomes overloaded, the job ticket is transferred to the master device after reaching the end of the Ac column, The Ac column is again transferred in order and an execution device is selected or an error signal is issued to prompt the operator to adjust the job.

Next, still another embodiment of the management system of the present invention will be described.
In each of the above-described embodiments, each device constituting the Ac column autonomously determines a job ticket to be accepted based on the job acceptance conditions set in the device. However, each master device has its own device. In the case of a configuration in which capability information of all connected sub-devices is held in addition to capability information, the master device refers to the capability information held, and among the devices in the Ac column It is also possible to determine on which device the job is to be executed. If the determined device is its own device, the master device receives the job ticket with its own device, and if it is a sub device, transfers the job ticket to the corresponding sub device.

Also in this embodiment, when there are two or more apparatuses that can execute the job described in the job ticket, it is preferable that the sub apparatus preferentially determines the job execution apparatus. Of these, it is preferable to preferentially determine the job execution apparatus from the most downstream apparatus as viewed from the master apparatus. By doing so, the queue can be opened in order from the master device side, and it becomes easy to deal with the order in the express mode.
In addition, the master device and the sub-device closer to the master device, that is, the device on the upstream side, has a higher capability so that it can quickly respond to orders in the express mode or orders that require special processing. It is also preferable to arrange them.

Next, an example in which the order processing system 10 of the present invention is applied to a specific apparatus will be described.
As described above, the order processing system 10 of the present invention is composed of components belonging to two layers, the workflow layer 14 and the activity layer 16. These components can be located on multiple devices. However, one order management unit 20 is arranged in one system.

  FIG. 3 is a hardware configuration example of the order processing system 10 shown in FIGS. 1 and 2. The order processing system 40 of FIG. 3 includes an order receiving device 42, a workflow management device 44 that also serves as an image editing device, two image editing devices 46, a film scanner 48, and three printers 50. . Each of these devices is connected by a communication line such as Ethernet (registered trademark).

  In this example, each device is physically connected to the network like a star chain, and logically, the activity component Ac that executes the same kind of processing is daisy-chained as shown in FIG. They are connected in series like a chain. In the case where one process has activity components Ac of two different processes, such as the workflow management apparatus 44 and the image editing apparatus 46 shown in FIG. 3, this configuration is appropriate.

  In the case where one device has only an activity component Ac that processes one process like the printer 50, the devices themselves may be physically connected in a daisy chain. Also, the image editing device 46 is logically and physically a star chain, and the printer 50 is a daisy chain. For each type of device, the daisy chain and the star chain are used separately, and the system includes both connection methods. You may go out.

  The order receiving device 42 has a function as the order receiving unit 12 in the order processing system 10 of FIG. 1, and acquires image data and order information (order information) of an image to be reproduced (order target image, input image). For example, an automatic print order receiving machine installed in a photo lab store or various stores, a system terminal of a photo lab store, an internet order receiving terminal (customer's personal computer or the like). Although not shown, the order reception device 42 temporarily stores instruction input means (keyboard, mouse, touch panel, etc.) for a customer (user) to input order information, a monitor for displaying an order reception screen, and image data of an order target image. A storage unit is provided.

In addition, the order receiving device 42 is connected to a digital drive as a means for acquiring image data, a media drive that reads images from various image recording media, a communication device that receives image data transmitted through a communication line such as the Internet, and a digital camera. It has one or more parts.
The image data acquired by the order receiving device 42 by the image data acquisition means is stored in the storage unit.

The workflow management apparatus (image editing apparatus) 44 includes an order management unit 20 that performs workflow management of the entire order processing system 40 and receives instructions for orders to be executed. The order management unit 20 is the order management unit 20 in the order processing system 10 of FIG. The order management unit 20 also functions as a management unit that manages the acceptance of jobs to the activity components Ac 54 and 56 of the workflow management device 44.
The workflow management device 44 further includes an order execution instruction unit 22A corresponding to the order execution instruction unit 22 in the order processing system 10 of FIG. 1 and a device public information database 24 (not shown).

  The workflow management device 44 identifies and inputs (acquires) image data from the customer stored in the storage unit of the order receiving device 42, and performs a verification process, image synthesis, and the like of the input image data (input image data). It has a function as an image editing device that performs an image processing step and further writes image data after image processing to a recording medium such as a CD-R according to the order contents. These processes are executed by the input / verification / synthesis Ac (54) and the media output Ac (56).

  The image processing device 46 includes a management unit 58 and an input / verification / composition Ac (60), and has the same function as the function of the workflow management device 44 as an image editing device. That is, the management unit 58 manages the acceptance of a job to the input / verification / composition Ac (60), and the input / verification / synthesis Ac (60) is received from the customer stored in the storage unit of the order receiving device 42. The image data is identified and input (acquired), and an image processing process such as an input image data verification process and image composition is performed.

  The film scanner 48 photoelectrically reads an image taken on a photographic film and converts it into image data, and stores the obtained image data in a storage unit (not shown) in the film scanner 48. The film scanner 48 can also perform an image processing process such as an input image data verification process or an image synthesis process, if necessary. These processes are executed by the input / verification / combination Ac (64) under job acceptance management by the management unit 62. The film scanner 48 also has a function of an order execution instructing unit 22B for starting the order process.

The printer 50 has a function of outputting processed image data transferred from the workflow management apparatus (image editing apparatus) 44 or the film scanner 48 as a photographic print.
When the management unit 66 accepts the job, the image data acquired by the order receiving device 42 and edited by the workflow management device (image editing device) 44 or the image data acquired by the film scanner 48 and processed by editing is stored in the printer. The print is stored in a storage unit (not shown) in the print 50, and the print Ac (68) executes print processing.

  The order management unit 20 belonging to the workflow layer 14 of the order processing system 10 in FIG. 1 is provided in the workflow management apparatus 44 in the order processing system 40 in FIG. The order execution instruction unit 22 of the order processing system 10 is provided in the workflow management device 44 (corresponding to the execution instruction unit 22A) and the film scanner 48 (corresponding to the execution instruction unit 22B) of the order processing system 40.

  In addition, each activity component Ac belonging to the activity layer 16 of the order processing system 10 includes a workflow management device 44 (corresponding to input / verification / synthesis Ac (54) and CD-R (media) output Ac (56)), an image. Editing device 46 (supports input / verification / composition Ac (60)), film scanner 48 (corresponds to input / verification / synthesis Ac (64)), and printer 50 (corresponds to print Ac (68)). Is provided.

  As described above, the elements corresponding to the respective layers are distributed to the respective apparatuses, whereby the order processing system 40 in FIG. 2 constitutes the order processing system 10 in FIG. 1 as a whole. These devices cooperate to execute order processing.

Note that the order processing system 40 may include a plurality of devices having the same ability to perform the same processing other than the illustrated one. Moreover, although the same process is performed, you may be provided with the apparatus from which capability differs, and the apparatus which performs a different process even if it is the same process may be provided.
For example, the output device may further include a plurality of devices that reproduce images on various products such as mugs and T-shirts. The image output method is not particularly limited, and a silver salt photographic method, an electrophotographic method, various ink jet methods, and other various methods can be used.

  In addition, the number of devices constituting the order processing system 40 is not limited to the example of FIG. 3, and any one of a plurality of types of activity components that execute processing necessary for an order received by the order processing system 40. The present invention can be applied if more than one type includes a plurality of activity components. For example, the image editing apparatus is the workflow management apparatus 44, does not have the image editing apparatus 46, has a plurality of printers 50 that are output apparatuses, and these are logically or logically and physically connected in series. The present invention may be applied.

  The management system and the order processing system using the management system according to the present invention have been described in detail above. However, the present invention is not limited to the various embodiments described above, and various improvements can be made without departing from the gist of the present invention. Of course, you may make changes.

It is a block diagram which shows schematic structure of one Embodiment of the order processing system of this invention. FIG. 2 is a diagram conceptually showing a work part of each process in job ticket generation and job execution in the workflow layer and activity layer of FIG. 1. It is a hardware structural example of the order processing system shown in FIG. It is a figure which shows the example of the information described in a job ticket. It is a figure which shows the example of a job ticket notionally.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10, 40 Order processing system 12 Order reception part 14 Workflow layer 16 Activity layer 20 Order management part 22 Order execution instruction part 24 Device public information database 26 Workflow server 28 Order information database 30 Production information database 32 Template library 34 Status acquisition / Job control Unit 35 Device capability analysis unit 36 Delivery date calculation unit 37 Scheduling unit 38 JobTicket generation unit 42 Order acceptance device 44 Workflow management device (image editing device)
46 Image Editing Device 48 Film Scanner 50 Printer Ac, 54, 56, 60, 64, 68 Activity Component

Claims (9)

A management system that manages job execution based on a job ticket that describes job details,
One or more device rows each including a master device that first receives the job ticket in one processing step and one or more sub-devices that are connected in series to the master device and execute the same type of processing as the master device. ,
A management system for managing execution of a job in units of the apparatus row. The master device and the sub device each have an acceptance management unit that manages job acceptance based on set job acceptance conditions,
When the job described in the job ticket satisfies the job acceptance condition, the acceptance management unit receives the job ticket and executes a corresponding processing step of the job, and the job described in the job ticket The management system according to claim 1, wherein when the job acceptance condition is not satisfied, the job ticket is transferred to the subsequent sub device.   The management system according to claim 2, wherein the job acceptance condition of each device is set so as not to accept a job when a device malfunctions or a load is exceeded.   The job acceptance condition of each device is set to accept a job whose priority is in a certain range, and at least one of the master device and the one or more sub-devices is within the priority range of the accepted job The management system of Claim 2 or 3 from which different.   The master device retains capability information of its own device and all of the sub devices connected thereto, and determines a device that executes the job described in the job ticket based on the retained capability information. 2. The management system according to claim 1, wherein if the determined device is the sub device, the job ticket is transferred to the sub device, and if the determined device is the master device, the job ticket is received.   The management system according to claim 5, wherein the master device is preferentially determined as the job execution device from the sub devices. An order processing system that accepts an input image and a playback processing order of the input image, and performs playback processing according to the playback processing order,
Job ticket generation for generating one job ticket for each order, which describes the contents of the process for the reproduction process according to the order contents of the reproduction process order, the execution order of the process, and the information indicating the execution destination of the process And
A management system according to any one of claims 1 to 4,
The job ticket generation unit refers to the capability information of the master device, selects the master device in the device row that can execute the step for each step of the job, and selects the selected master device in the step. An order processing system that generates the job ticket described as an execution destination. An order processing system that accepts an input image and a playback processing order of the input image, and performs playback processing according to the playback processing order,
Job ticket generation for generating one job ticket for each order, which describes the contents of the process for the reproduction process according to the order contents of the reproduction process order, the execution order of the process, and the information indicating the execution destination of the process And
A management system according to claim 5 or 6,
The job ticket generation unit refers to capability information of its own device held by the master device and capability information of all the sub devices connected thereto, and can execute the step for each step of the job. An order processing system comprising: selecting the master device in a device row, and generating the job ticket in which the selected master device is described as an execution destination of the process. An order receiving unit for receiving an order for the reproduction processing of the input image;
A list creation unit that creates a list of order contents that can be accepted based on the capability information of its own device held by the master device and the capability information of all the sub devices connected thereto, and presents the list to the order reception unit The order processing system according to claim 8, comprising:

Images