Label printing utilises the concept of
lanes when laying up the run imposition for production.
To enable this we have included a lanes calculator into our quote templates.
In this example we have x3 kinds of label
at a size of 100mm x 100mm.
QTYS REQUIRED:
Version A: x18,000
Version B: x36,000
Version C: x9000
When starting the quote, the ‘Versions’ are
entered at the top of the screen.
When using Advanced Kinds, the kind name will auto-populate with a
placeholder (Version A).
If you don't enter anything in this text box, and only enter a quantity, it
will use the default placeholder name.
If you enter text, your entered text will be used as the version / kind name.
This is configurable under Customise > Settings > Global:
Now click on the ‘Runs Calculator’:
RUNS/LANES LOGIC:
The calculator screen will drop down. Multiple
fields are available for manual entry:
Number of Lanes: This is manually entered or pulled from the number across of
the linked die.
Labels Per Roll: This is optional but is used in the calculation when entered.
It will round the print runs up to the entered qty. For our example we have a
3up die linked and require 3000 qty per roll.
Max Overs per kind: You can enter a max number of overs if required. This can
be set by a number or a %
Optmize for: This can be set to either ‘Least Waste’ or ‘Least Runs’ depending
on your requirements
Limit kind to a single run: Check this ON to make sure a kind is not spread out
onto multiple runs. For example if printing digitally, you may want this OFF as
plates are of no concern.
Per kind: this will auto place each kind only its own run
When we click ‘Calculate’, printIQ will
calculate the run splits.
Here we have calculated 2 runs producing zero overs:
To use the layouts calculated, select ‘Save
& Close’:
A
grid will show in the section outlining the breakdown:
Finish the quote by adding any other required job or section-based operation and click ‘Get Price’:
This will calculate the quote and split
each run into its own production section:
NOTE: If any overs are produced as part of
the calculation, they will be flagged, showing the kinds and quantity of overs
produced for each kind:
This lets you change the ‘Run Quantity’:
Add Kind to Run:
This lets you add any ‘kind’not currently attached to this run:
Remove Lane:
Lets you delete the entire run from the list:
Remove Kind:
Lets you remove that kind from the run:
New Run:
Lets you add an additional run to the quote:
The custom quote will open and the kinds will display. You need to enter a quantity against each item and click the green ‘tick’:
You can also add additional items as required:
If any of the items are setup using PMS notes, Product Item Notes or Internal Notes, you will be flagged on the screen:
Click the box to see the notes:
The PMS notes will also show in the ‘Runs Calculator’:
You can click ‘Calculate’ to have printIQ auto impose the runs or you can manually select what items you would like to calculate on each run as you go. This allows you to control how the runs are built. Use the checkbox to select the items to calculate:
This will build the run:
Keep selecting the items until all items are added to runs:
If you want each kind to be assigned its own run, click on the ‘Per Kind’ checkbox and ‘Calculate’:
Each item will be assigned its own run:
In the job details, you can see the kinds assigned to each run/section:
In this example we have 2 runs. Run 1 contains ALAB & BLAB. Run 2 contains DLAB & ELAB:
Due to the label colours, we want to
reconfigure to have Run 1 containing ALAB & ELAB and Run 2 to
contain BLAB & DLAB.
Click the ‘Runs Calculator’ button to open the modal:
The ‘Runs Calculator’ modal will show:
Select the kinds for the first run:
Click ‘Calculate’ to include the calculated run:
And ‘Calculate’ to add:
Click ‘Save & Close’:
From the modal, select ‘Confirm’:
If you try to do an edit and create less or more section on the existing job, you will get an error:
*Edits requiring changes to the number of runs generated use ‘Version Quote’ workflow:
XML
The lanes configuration is included in the xml: