AC-37 - Step and Repeat
Labels, Sleeves, Flexibles
Keith LaBombard
Manager of Software Training Integration, Americas
Jason Vitaletti
Application Sales Manager
May 21, 2013
1
AC-37 – Step and Repeat – Labels, Sleeves, Flexibles
● Automation Engine Tickets – Layout Module
– Step and Repeat Cad based
– Step and Repeat Template based
– Step and Repeat Tabular
● Automated Layout – Single SKU
● Automated Layout – Multiple SKU (Combo Run)
2
AC-37 – Step and Repeat – Labels, Sleeves, Flexibles
● This diagram and a
written explanation can
be found in:
– Plato Help, keywords
predefined
parameters
● A written explanation
only can be found in:
– Pilot Help, Reference
Guide, keyword
Formulas
● LEARN THESE!!!!!
– These same
SmartNames are used
in SmartMarks
3
AC-37 – Tickets: CAD Based
● Step and Repeat Cad based
– Common Folding Carton solution, but can work for Web fed products
– Utilizes a Stepped CAD file to create layout (CFF2 and MFG)
•
•
Places graphics based on the design name OR print item label
CAD file MUST contain stepping data, not a manually stepped design file
– Task is launched on the CAD file, NOT the graphics file
– SmartMarks should apply with no modification required
– Solution for Combination runs if CAD department is “in-house”
•
No additional work required in pre-press, but the CAD department must determine the
positions for each SKU
– Esko’s Smart Flapping creates intelligent masking based on structure
4
AC-37 – Tickets: CAD Based
● Folder for the Stations
– Files must match the
one-up Design Name from
the MFG or the Print Item
name
● Error Handling
● SmartMarks
● Optionally set bleed
limit
5
AC-37 – Tickets: CAD Based
● Sheet size determined
by MFG file
● Plate sizes can be
hardcoded or chosen via
SmartNames if you have
multiple plate sizes
● Position and Gripper
specifications can be
hardcoded or chosen via
SmartNames
● Distortion support for
Flexo
● Screen Registration
6
AC-37 – Tickets: CAD Based
● Mapping is strictly for DXF
layer and line type
mapping
● CAD Style is a filter than
can be created using
PackEdge or Plato
● The Style controls line
types/weights/colours
7
AC-37 – Tickets: Template Based
● Step and Repeat Template based
– Common Folding Carton solution (but may require Plato for combination runs)
– Utilizes previously created PDFPLA (Plato file) and substitutes Artwork
•
•
Requires use of previous layout or prebuilt template file
Templates are NOT Plato templates (they must be located on a container)
– Optionally it can utilize MFG files for use as a template
– Task is launched on the Graphics File (npdf)
– SmartMarks update to reflect new artwork
– The “go to” option for organizations that must customize every layout
– Excellent solution for Combination runs if equipped with Plato
– Utilizing SmartNames and XML enables WorkFlow Automation
– Graphics masking is based upon the template file used
8
AC-37 – Tickets: Template Based
● Template, specify the
template file to use to
create the new layout
● In the Stations list, you
will see a list of the
Stations in the template
file, you specify which
stations are to get
replaced and which file to
use.
● Both the template and the
station selection can be
chosen via SmartNames,
this facilitates automation
in a WorkFlow
9
AC-37 – Tickets: Template Based
● Same options as the
Cad Based Ticket, but
only available when using
an MFG as your template
● Not required if the
template is a PDFPLA
10
AC-37 – Tickets: Template Based
● Same options as the
Cad Based Ticket, but
only available when using
an MFG as your template
● Not required if the
template is a PDFPLA
11
AC-37 – Tickets: Tabular
● Step and Repeat Tabular
– Most common option used in Web Printing
– Task is launched on the Graphics File (npdf)
– Grid Based
•
Stepping information for each row/column required
– All aspects of the layout can be controlled via SmartNames and Formulas
– Incredibly dynamic and easy to automate
12
AC-37 – Tickets: Tabular, Single SKU
● This is what I call the
“Perfect Stepping Ticket”
– Works 100% of the time
for any single SKU layout
– Using SmartNames to
determine Marks
allowance, Distortion
choices, etc. allows this
ticket to work for multiple
presses
– The demonstration is based
on Job Parameters,
however, Db queries,
AutoJob Creation or JDF
eliminates the need to
enter the data
– Job Parameters can be
applied using Job
Templates
13
AC-37 – Tickets: Tabular, Single SKU
● This is what I call the
“Perfect Stepping Ticket”
– Works 100% of the time
for any single SKU layout
– Using SmartNames to
determine Marks
allowance, Distortion
choices, etc. allows this
ticket to work for multiple
presses
– The demonstration is based
on Job Parameters,
however, Db queries,
AutoJob Creation or JDF
eliminates the need to
enter the data
– Job Parameters can be
applied using Job
Templates
14
AC-37 – Tickets: Tabular, Single SKU
● This is what I call the
“Perfect Stepping Ticket”
– Works 100% of the time
for any single SKU layout
– Using SmartNames to
determine Marks
allowance, Distortion
choices, etc. allows this
ticket to work for multiple
presses
– The demonstration is based
on Job Parameters,
however, Db queries,
AutoJob Creation or JDF
eliminates the need to
enter the data
– Job Parameters can be
applied using Job
Templates
15
AC-37 – Tickets: Tabular, Single SKU
16
AC-37 – Tickets: Tabular, Multiple SKU
● You can create a ticket
with many grids. If used
as a stand alone ticket,
you can populate it with
you maximum number of
grids
● Remove [File] SmartName
● The system will only
populate as many Grids as
the ticket receives
(doesn’t function this way
in a WorkFlow)
● Formulae will need to be
re-worked to properly
position the layout
17
AC-37 – Tickets: Tabular, Multiple SKU
● You can create a ticket
with many grids. If used
as a stand alone ticket,
you can populate it with
you maximum number of
grids
● Remove [File] SmartName
● The system will only
populate as many Grids as
the ticket receives
(doesn’t function this way
in a WorkFlow)
● Formulae will need to be
re-worked to properly
position the layout
18
AC-37 – Tickets: Tabular, Multiple SKU
● You can create a ticket
with many grids. If used
as a stand alone ticket,
you can populate it with
you maximum number of
grids
● Remove [File] SmartName
● The system will only
populate as many Grids as
the ticket receives
(doesn’t function this way
in a WorkFlow)
● Formulae will need to be
re-worked to properly
position the layout
19
AC-37 – Tickets: Tabular, Multiple SKU
● You can create a ticket
with many grids. If used
as a stand alone ticket,
you can populate it with
you maximum number of
grids
● Remove [File] SmartName
● The system will only
populate as many Grids as
the ticket receives
(doesn’t function this way
in a WorkFlow)
● Formulae will need to be
re-worked to properly
position the layout
20
AC-37 – Tickets: Tabular, Multiple SKU
21
AC-37 – Automated Layouts – Single and Multiple SKU
22
AC-37 – Automated Layouts – Single and Multiple SKU
23
AC-37 – Automated Layouts – Single and Multiple SKU
24
AC-37 – Automated Layouts – Single and Multiple SKU
25
AC-37 – Automated Layouts – Single and Multiple SKU
26
AC-37 – Automated Layouts – Single and Multiple SKU
27
AC-37 – Automated Layouts – Single and Multiple SKU
28
AC-37 – Automated Layouts – Single and Multiple SKU
29
30