Is the Output Module needed for Batching? Will this give me the same features as Output Module did as a stand alone product? What do I get with this accessory to FF Core?
The output management module has the following:
• The new Collect node which aggregates jobs (you woudl use this with Route to sort and aggregate jobs into batching)
• The ability route jobs based on criteria used by Collect to release jobs (this enables the ability to build workflows that will automatically adjust job preparation based on what a given collection of jobs looks like)
• The ability to do load balancing between multiple printer destinations
Note: The ability to do "copy split" is in the Split node which is part of the advanced prepress module (this is typically an output management function but I decided to add it to the advanced prepress module instead)
• The ability the new Job Group Imposition which can enable some forms of automated ganging when used with route and collect.
• The ability to pause / resume submission of jobs to a printer destination (which may be used on its own or with load balancing).
To answer your initial question - yes, the output management module is required for job batching.
THis question was asked over two years ago. At the end of 2016 what is the difference in features between the Core Output Module and FreeFlow Output Manager? I need to know in general but one specific need is to change jobs from one printer on one subnet to another printer on another subnet. Both printers are Xerox FreeFlow PS fronted engines.
In general I think the differences are roughly the same with perhaps some updated positioning:
As to your specific question - if you are distributing the jobs within FFCore, we can change the distribution on the fly based on the job submission regulation. Once the job is sent to the DFE we do not have a way to retrieve it (the DFEs do not support this).
I hope the above helps.
PS> The subnet used for the printer is immaterial to FFCore.