cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Miker
FreeFlow User

FF Core Output Module

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?

Labels (1)
0 Kudos
4 Replies
Account Deactivated

Re: FF Core Output Module

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.

0 Kudos
richardr New Member
New Member

Re: FF Core Output Module

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.

 

Merci!

0 Kudos
Account Deactivated

Re: FF Core Output Module

In general I think the differences are roughly the same with perhaps some updated positioning:

  • Collect has been enhanced to allow more dynamic job batching (aka batching based on properties)
  • We have added a new "Distribute" node that load balanced between workflow branches (this lets you build print clusters while using different imposition and other prepress for each device)
  • We have added a number of JMF commands to allow upstream components to control job routing and distribution in FFCore
  • We have added more job status signals - including signals letting upstream systems track jobs after we hand them off to the DFE
  • We have added additional "job submission regulation" criteria which are used with load balancing to dynamically alter the distribution of jobs by automatically pausing and resuming submission to a DFE based on selected criteria (e.g. the number of active jobs at the DFE)
  • We have also added print failover which also leverages the "job submission regulation" mentioned above
  • We have added more print engine information (when available) to the FFC UI (ink, trays, output bin information)
  • Split has been significantly enhanced to enable job, page, quantity, record splitting (each in multiple ways)

 

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.

 

0 Kudos
richardr New Member
New Member

Re: FF Core Output Module

Merci monsieur!!

0 Kudos