Cloud Nester Settings
The Cloud Nester creates nested proposals which is mentioned as nest. When a nest is submitted, automatically or manually, we mention this as a Job. The preview of the nests only contain thumbnails of the Document. Cutting markers, labels and color bars aren't visible on the preview. They are applied when the Job enters the RIP.
Preset
Settings
- Positioning
Where you want the resulting nest to be positioned on the media - Butt-up
Nests items without spacing. Where Cutcontours overlap a single Cutcontour will be generated. This prevents unnecessary cutting time. - Spacing
The distance between the Parts in the nest. For Stack Nesting the Bounding box is used, for TrueShape Nesting the NestShape in the Document is used - Multi-copy pages
Returns the amount of copies that should be printed of the page.
How it works: When all Parts in the Nesting Bucket have been nested and the result contains equal pages we created Copies instead of individual pages. The Copies are shown in the Nest-info UI.
What to expect in the Job: We sent the amount of Copies that have to be printed of the Job-page to the RIP. For direct driven Printers we print (spool) the Job-page as many times as Copies requested. For printers with a folder output we print (spool) the Job-page once. In this case the Copies can't be sent, but can be found on the Job Bag. Available from PF6.8.2 on request.
Triggers
When multiple triggers are enabled they'll be treated as an "Or"function.
- Maximum Job Age
When Parts are added to the Nester a CreationDate-Time as set. When the CreationDate-Time of the last added Part is bigger then the minutes set, the nest is triggered. This is checked every 2 minutes. - Maximum Media Length
When a new Part enters the Nest which will exceed the maximum set length of a Page it will be triggered with the latest added Part. Jobs will never get longer then the length set. - Min. Efficiency
The Nest will be triggered when when the efficiency set is met or exceeded.
How it works with PrintDeadlines: The efficiency calculation is based on all Nested Parts of the earliest PrintDeadline group. When you're using Fill-up these Parts are not taking into account for the trigger. In the preview we do show the efficiency including Parts that are used for Fill-up as well as the efficiency for the earliest PrintDeadline group. For a Media defined as a Roll the efficiency is based on the length of the latest place Part. For a Media defined as a Sheet the whole length of the Media is used. - Number of Pages/Tiles
Maximum amount of Parts that can be placed on a Nest. When the amount set is met, it will be triggered. - Print Deadline
When enabled and Nest contains Part with expired PrintDeadlines it will be triggered. - Expires at (24h)
It will give all incoming Parts the next available Day and Time set. They will be nested together on that Deadline. When the Deadline expires the nest will be triggered. This function is typically used when added a PrintDeadline isn't possible. These way you can keep Parts together based on added DateTime
Fill-up
Fill-up only works for Parts that contain a PrintDeadline.
- Fill-up with not expired jobs (hours)
Gives the Nester the opportunity to use Parts from a later PrintDeadline, up until the hour set, based on the earliest PrintDeadline in the nest to make it more efficient. Earliest PrintDeadline is based on all Parts in the Nesting Queue not Page individual. - Fill-up to extend Roll length
Gives the Nester te opportunity to make the nest longer than the end of the last placed Parts of the earliest PrintDeadline. This doesn't always mean that the nest becomes more efficient, but it increases the length of the nest when you have a small amount of Parts for the earliest PrintDeadline in the nest. - Fill-up with complete Jobs
We only place the Parts when all Copies and Pages of the Document can be placed on the same page. This makes sure Parts from the same do not end up in several pages.
Queue
Output
- Name
Name of the Nesting Queue - Description
Additional information to describe the Nesting Queue. It shown on Nesting-Setting-Queue overview page. - Email notifications
When a Job is created from a nest an email is sent with a link to the Job bag. You can add multiple mail addresses by separating them with a ";". - Print Policy (only applied when Nest are triggered automatically)
- Round Robin
Will send each following triggered nest prioritized Printer from the available Printers. - Highest priority
will always send each triggered nest to the highest prioritized Printer from all available once. Priority "1" is highest. When a Printer is disabled in app.printfactory.cloud it automatically switches to next prioritized Printer. - Job Queue Length
The nest will be submitted to the Printer which has the least amount of length to be printed (spooled). This function only works correct for Printers which are directly driver by the RIP. For Printer that output to a folder we don't have this information available. - Hold printing
When enabled the nest will be RIPped, but spooling will be set to hold. When disabled and you want directly driven Printers also to print automatically, "Automatic start automation Jobs" option in the driver settings in the RIP must be enabled. - Reference profile
Selected reference profile will be applied on the nest. - Printer list (all fields are mandatory)
- Printer
Shows a list of all available printers from all sites (SerialNumbers) of your Organizations. Deleted Printers are marked as Deleted and nests can't be created anymore. If other Printers are available in the list they can be used. - Queue
A Queue must be created in the RIP on the Printer and selected here. Settings that can't be set in the Nesting Queue can be set in the RIP Queue. All settings set in the Nesting Queue will be honored by the RIP. - Media Type - Mode - Variant
These are the settings of the PMM which will be applied on this Printer when a Job is created. - Priority
1 is the highest priority. On automatic triggered nests this printer will be used in the Job when Print Priority is set to Highest priority. When a nest is manually submitted the highest priority is listed at the top of the list. - Cutting
- Registration marks
Shows a list of all your Cutting marks. Selected marks are applied on the nest and the space they need are taking into account during nesting. - Cutter list (all fields are mandatory)
When multiple cutters are selected a Cut Job will be created for each Cutter. This way you can for example receive a .zcc Job for your Zünd and a .oxf for a Optiscout driven cutter so you can decide later on which device your want to cut the Job.
You can only select one Registration mark. - Cutter
Shows a list of available cutters from all your sites (SerialNumbers) of your Organization. When Cutters are deleted from the RIP they will be marked as deleted. Jobs won't be created for deleted Cutters. - Queue (mandatory)
A Queue must be created in the RIP on the Cutter and selected here. Settings that can't be set in the Nesting Queue can be set in the RIP Queue. All settings set in the Nesting Queue will be honored by the RIP. - Job name formatting
You can use free text and/or choose variables from the pulldown list. This will be used for the Job Name of the submitted nest. - Job label
Shows a list of your labels. This label will be placed at the left bottom of the created Job. It's applied on the Job not on the Parts in the Job. When Part/Item labels are applied to the Parts, from Workflow for example, Job label selected will be ignored. Combining these 2 labels is not possible. - Color bars
Choose position and size here. Instruction will be applied in the RIP when the Job is submitted and taking into account during nesting.
Buckets
How do Buckets work.
Bucket are part of the Nesting Queue and you can define multiple Buckets in a Nesting Queue. When your adding Parts to the Nesting Queue, the Nest Queue adds them to all manual created Buckets. This gives you the opportunity to generate multiple proposals, e.g. different Media sizes and/or Nesting Presets. When a Job is created from Bucket the used Parts in this Job will also be removed from the other Buckets.
On automatic triggering the Bucket which meets the criteria first will be submitted.
Bucket are part of the Nesting Queue and you can define multiple Buckets in a Nesting Queue. When your adding Parts to the Nesting Queue, the Nest Queue adds them to all manual created Buckets. This gives you the opportunity to generate multiple proposals, e.g. different Media sizes and/or Nesting Presets. When a Job is created from Bucket the used Parts in this Job will also be removed from the other Buckets.
On automatic triggering the Bucket which meets the criteria first will be submitted.
- Play
Disabled means the Bucket is on hold. This Bucket will not be re-nested not will it accept new incoming Parts. - Star
You can mark your manual created Bucket. It can help you identify these Buckets when other Buckets are generated by Group Id. - Bucket Name
This is a free text field and will be used in the the Nesting overview page. - Preset
Shows a list of Nesting Presets you've created. Select the one here you want to be applied on your Bucket - Media
Shows a list of default and manual created media's. The selected one will be applied during nesting on that Bucket. - Group ID
When Parts are being added to the Nesting Queue and they contains a variable PhysicalGroupID a copy of the manual created Buckets is created and Parts are only added to those Buckets. E.g. when you print on vinyl you probably deliver them with and without laminate. If you want them to be nested separately you can add this Group ID. You can also add this Group ID when you want specific Jobs to be nested together.
Buckets with a Group ID automatically deleted when they aren't used for a week and the Bucket is empty. A new copy will be generated when re-adding Parts with a deleted Bucket.
Working with Printdeadlines
A PrintDeadline can be added as Variable in Workflow to the Part being added to the Cloud Nester. During the nesting process the PrintDeadline will be the first priority group we make, earliest PrintDeadlines first. All Parts with the same PrintDeadline will be nested on one page, if they don't fit we created a second page and so on. Then we nest the next PrintDeadline group etc.
Fill-up setting, from the Nesting Preset, can only be applied when PrintDeadlines are used.
Fill-up setting, from the Nesting Preset, can only be applied when PrintDeadlines are used.
Working with LogisticGroupID's
LogisticGroupID's can be added as a variable in Workflow to the Parts. being added to the Cloud Nester. You can add different Parts with the same LogisticGroupID and they will end up in the same Group. From the Parts with the same Group a separate Nest is created, using the whole width of the Media, and placed on the Media. Group are alphabetically prioritized and placed below each other. Placed Group will not be re-nested or rotated, they are placed as they are.
When a Group doesn't fit on one page we resume on the following page.
Parts without a LogisticGroupID will be used to fill the gaps in the groups.
When a Group doesn't fit on one page we resume on the following page.
Parts without a LogisticGroupID will be used to fill the gaps in the groups.
PrintDeadlines and LogisticGroupID's
When having a PrintDeadline and a LogisticGroupID in the Parts they will be grouped on PrintDeadline first and then on LogisticGroupID.
Fill-up and LogisticGroupId
Depending on your Fill-up setting in the Nesting Preset, Groups can be used to fill-up the Page with Groups from later PrintDeadlines.
Nester prioritization while placing Parts
- PrintDeadline and LogisticGroupID's
- Place parts without LogisticGroupID and the same PrintDeadline
- Fill-up with LogisticGroupID's
- Fill-up with Parts without LogisticGroupID's
Related Articles
How to Setup Cloud Nesting from Start to Finish
How to Set Up a Cloud Nest Queue in PrintFactory This guide walks you through the full setup of a Cloud Nest Queue in PrintFactory, including preparing the RIP , creating nesting presets, and the nest queue, and then connecting everything through the ...Nest overview page
Explanation Headers, Buttons and other function Example overview Nesting queue, name of the Nesting Queue Bucket Name, name of the Bucket. Clicking on the name of the Bucket open the Nest Preview (info) page Criteria, triggering Criteria('s) set in ...Nest info page
Explanation Headers and Buttons Available from version 6.91.0 This shows you a Preview of the Nest result which we call a Candidate. A Candidate is not a Job, so it's not Submitted to the RIP manually or automatically yet. Example of Media Type ...Multi-page submission behaviour Cloud Nester
Multi-page submission behaviour Available from version 6.91.0 There are 2 ways to submit Multiple page from the Nesting Bucket. Multi-page Jobs can only be created by Manual Submission. Automatic triggered Job will always be submitted one at a time ...Release notes Cloud
Cloud release notes Current version can be found in app.printfactory.cloud in the footer. Version 6.106.0 - 2025-06-26 Loading speed Nest Queue settings improved "Region format" added to Regional Setting to determine Date/Time format Performance ...