Automation Engine

Introducing AE

11 - 2018

Automation Engine

Contents1. What is Automation Engine?.................................................................................................................. 3

1.1. Client-Server Architecture.................................................................................................................31.2. Data Management and Central Resources.....................................................................................41.3. Multi-site Environments ('Enterprise')............................................................................................. 41.4. Scalability and Security.....................................................................................................................41.5. The Automation Engine Viewer....................................................................................................... 51.6. Integration with Other Applications................................................................................................ 51.7. Scripting............................................................................................................................................. 61.8. More Help?.........................................................................................................................................6

2. File Formats, Normalization and XMP.................................................................................................. 82.1. File Types and How they are Recognized....................................................................................... 82.2. Normalized PDF in Automation Engine........................................................................................ 12

2.2.1. Introduction...........................................................................................................................122.2.2. What Makes a Normalized PDF Special?............................................................................ 122.2.3. Which Tasks Require PDF Normalization?.......................................................................... 132.2.4. How do PDF Tasks Work with Normalized PDF Files?........................................................142.2.5. How Do Normalized PDF Tasks Work With Regular PDF Files?.........................................152.2.6. PDF Normalization and Step and Repeat...........................................................................17

2.3. XMP Metadata................................................................................................................................. 18

3. Important Concepts and Work Modes................................................................................................203.1. Containers (introduction)............................................................................................................... 203.2. Jobs (introduction)...........................................................................................................................213.3. Products (introduction)...................................................................................................................223.4. Page Workflow Views and Tools (introduction)............................................................................ 22

ii

1Automation Engine

1. What is Automation Engine?

Automation Engine serves to increase productivity of prepress workflows. It does this throughautomated workflows, data management and quality control tools.

Automation Engine is part of the Esko Software Platform, which contains many other types ofapplications for various segments of the printing industry.

1.1. Client-Server ArchitectureThe Automation Engine Server is where all background actions are executed. This is also wherethe main configuration and databases are stored. This server is a powerful computer runningWindows.

The most known client application is the Automation Engine Pilot. You can install a Pilot onMac or Windows computers in the LAN network of the Server. The Pilot is the main interfacefor most users. This is where they inspect files and launch and manage tasks on the server.Depending on the user's Access Rights, more setup and configuration tools become available.

Some customers prefer to use the client application Shuttle. This tool offers a more limitedinterface where you can simply drag and drop files to launch the same kind of workflows onthe Server.

Operators that use interactive editors from Esko (ArtPro, PackEdge/Plato, DeskPack) can alsolaunch tasks from within those applications on the file that they currently work on.

Most server activity can also be started directly by external systems. Automation Engine offersmany tools for a two way integration with non-Esko tools like business systems.

Tip: Learn more about its architecture in the online interactive Learning Module. 

 

Attention: Detailed technical requirements for server and client computers aredescribed on http://www.esko.com/systemrequirements.

3

1 Automation Engine

1.2. Data Management and Central Resources

Data Management and Central Resources

The (prepress) data that Automation Engine can work with does not have to be stored on theAutomation Engine server, it can also be stored on a dedicated file server. Automation Enginecan work with any data that is stored on network shares that you configured on AutomationEngine. These places are called Containers.

Automation Engine offers databases to structure, manage and quickly access to files. Learnmore in the Jobs and Products concepts. The database server software is automatically installed.You have the option to use a different database server. Learn more in the chapter Pre-Install ITRequirements Guide.

The Automation Engine server also stores its Central Resources. These are for example filesrelated to fonts, color management or RIP'ing (curves, screening files).

1.3. Multi-site Environments ('Enterprise')Automation Engine itself is restricted to work with data within the same LAN.

• Access Points enable up and downloading data from (S)FTP or cloud storage sites to yourAutomation Engine.

• Esko WebCenter, a web platform for packaging project management, can also be used toshare data between multiple sites.

1.4. Scalability and Security

More Functionality

Automation Engine is a very modular product. The sales modules that you purchased orsubscribed to decide the licenses on your server. For example, the "Layout" module enablesthe licences for the "Step & Repeat" tasks.

For more info, check the available sales modules with your Esko sales contact.

More Power and Usage

The more powerful your Automation Engine server computer is, the faster it will process thebackground tasks and the faster it will react to requests from Pilot users.

Attention: It is important to check the minimal requirements for server and clientcomputers on http://www.esko.com/systemrequirements.

4

1Automation Engine

• Processing Channels: How many tasks your server will process at the same time is alsodecided by licenses. A sales module so decides whether your server is allowed to process 1,2, 4, 8 or 16 tasks at the same time ("concurrent"). 16 is the maximum. It is also possible toreserve some processing channels for specific tasks.

• Maximum Client Users: This same sales module also defines how many client applicationscan be used at the same time. For example: a maximum of 20 Pilot users logged in at thesame time.

Note: Learn more in the chapter Automation Engine Server Management.

Fail Safety

Automation Engine offers tools to automatically backup your software configuration anddatabases.

Learn more in the chapter Automation Engine Server Management.

More Power combined with More Fail Safety

You can add Automation Engine Assistants to your Automation Engine Master Server.

• An Automation Engine Assistant is another computer that helps out by also executing tasks(maybe a specific type of tasks).

• An Assistant can also be stand-by to become the Master Server when your Master server isdown because of a serious problem. There are many scenarios for disaster recovery. Thesedepend on where the data server is and where the database server is.

Note: Learn more in the chapter Pre-Install IT Requirements Guide.

1.5. The Automation Engine Viewer

The Automation Engine Viewer is a tool that your start from the Pilot to view and inspect files.It offers powerful features to view, measure and compare files, even when they are differentfile formats or have different sizes. Even staff in your customer service department can forexample install a Pilot for this reason only.

Each file that you open in this Viewer is a stream of pixels sent by the Automation Engineserver to your local Pilot. These pixels can be created by the server on-the-fly , or they couldhave been prepared before, also by the server. This is why the use of the Viewer can have asignificant impact on the load of your server.

Learn more in the chapter Quality Control Tools.

1.6. Integration with Other Applications

External Applications bundled with Automation Engine

5

1 Automation Engine

Automation Engine also offers licenses for tasks that use these built-in applications:

• The Preflight technology from Enfocus PitStop Server.

• Several file Inspection tasks from Global Vision.

Learn more in Quality Control tools.

Integrating with other Esko Applications

Automation Engine offers a bi-directional communication with most other Esko applications:

• Esko Editors can link with the Automation Engine server. This way, they use the samecentral resources (color data, fonts etc.) and can also launch tasks on the file that theoperator has open in the Editor. Learn more in Launching Tasks from Editors.

• Esko RIP and Proof software (Imaging Engine, FlexRip).

• the Front End application of an Esko CDI (DFS or Grapholas) or an Esko Kongsberg table (iPC).

• Integration with Esko WebCenter. Learn more in the dedicated chapter Integrating withWebCenter.

Integrating with External Systems

Apart from classic tools like integration via Hot Folders or exchanging data via FTP, AutomationEngine offers a wide range of integration capabilities with external systems. These tools canuse XML, JDF or even direct database interaction.

Learn more in the dedicated chapter Integrating with External Systems.

1.7. Scripting

Although Automation Engine already offers a broad set of tools to create custom workflows,it is still possible that you miss some functionality or that the available functionality does notsupport the native graphics format that you want to run them on.

This is why Automation Engine also offers custom scripting: you can write scripts (smallprograms) that typically represent actions that operators do interactively in their graphicdesktop applications..

Learn more in Using Scripts.

1.8. More Help?

Next to this elaborate documentation set, these tools can also help:

• Tool Tips: In many places in the Pilot, hover your mouse over a button or text to get a shortexplanation.

• In each dialog of a task Ticket (and some other places), click on to open the onlinedocumentation page for that topic.

6

1Automation Engine

• Keyboard Shortcuts: They are listed in the Pilot's Help menu.

• This online documentation also offers interactive Learn Modules about several basicconcepts.

• Esko's Knowledge Base contains information that is not part of this documentation. Itcontains articles about temporary topics, very technical topics, tips and tricks or specificerror messages.

7

2 Automation Engine

2. File Formats, Normalization and XMPWe here list the types of files that Automation Engine recognizes and explain how that is done.

We then elaborate on the concept of normalizing PDF in Automation Engine.

We also describe why XMP metadata is added to specific files.

2.1. File Types and How they are Recognized

Supported File Types

Automation Engine recognizes most of the standard file formats in the printing and packagingindustry (graphics, CAD and communication standards). It also supports Esko native formatslike ArtPro (AP) and ArtiosCAD (ARD, MFG).

Most graphics functionality runs on PDF.

• Learn more about benefits of 'normalization' in Normalized PDF in Automation Engine onpage 12.

• Learn more about use of PDF/X-4 in the separate document available on the AutomationEngine documentation page, in the section "Related documentation".

When your production file format is ArtPro, you can also choose to execute background taskson the native AP format by using ArtPro Action Lists.

Table: File types offered by the Pilot's 'Filter' tool

File Type FileExtension

Description

A3D A3D 3D format of Esko ArtiosCAD

AdobeIllustrator 8.0

AI These old AI files can still be read with the task thatnormalizes PostScript data.

AdobeIllustrator

AI Since v9, AI files can be the native AI format, whichAutomation Engine cannot read/normalize, or they can besaved as PDF compatible. The Pilot checks and shows the realformat.

ARD ARD Native CAD format of Esko ArtiosCAD (one-up)

ArtPro AP Native format of Esko ArtPro

CT CT Contone file (Esko legacy picture format)

JS JS 'Job Sheet' (used in TIFF/IT workflow)

LC LC Esko legacy contour (vector)

LP LP Esko legacy bitmap

Plato Plate PLA Esko Plato layout file, referring to legacy GRS files

BMP BMP Bitmap image

8

2Automation Engine

File Type FileExtension

Description

CDI LEN, VIEW RIP'ed (view) file for Esko CDI (flexo CTP)

CorelDRAW CDR CorelDraw native graphics

CFF2 CF2 Packaging CAD format

CSV CSV Comma Separated Value, typically exported from aspreadsheet or database

CTD CTD Preview data of CT file

Collada DAE Format for interactive 3D applications, XML version

DAT DAT Archive file of all impositions and page lists of a Job (Esko pageworkflow)

DCS EPS, DCS Desktop Color Separation, a collection of EPS files

MicrosoftWord 97- 2003

DOC Old native MS Word document

MicrosoftWord

DOCX Native MS Word document

DXF DXF CAD format

EPS EPS Encapsulated PostScript file

Flat - Item in Esko page workflow (set of plates)

AdobeFrameMaker

FM Native file

GRA GRA Legacy Esko format (page graphics)

GRC GRC Legacy Esko format (label or packaging graphics)

GRI GRI Legacy Esko format (imposition output)

GRO GRO Legacy Esko format (generic output)

GRQ GRQ Legacy Esko format (QuickStep layout)

GRR GRR Legacy Esko format (layout)

GRS GRS Legacy Esko format (graphics)

GRT GRT Legacy Esko format (tiles)

GRV GRV Legacy Esko format (view data)

GRZ GRZ Legacy Esko format (ZIP'ed)

HTML HTM, HTML Web page

Imposition File IMP Imposition created by Esko FastImpose

Imposition File(GRS)

IMP Imposition created by Esko FastImpose, referring to legacyGRS files,

Imposition - Item in Esko page workflow

AdobeInDesign

INDD Native graphics format

9

2 Automation Engine

File Type FileExtension

Description

JDF JDF Job Definition Format (www.cip4.org)

JMF JMF Job Messaging Format, HTTP version of JDF

JPEG JPG Picture

Layer - Item in Esko page workflow (layer of an Imposition)

MFG MFG Esko ArtiosCAD manufacturing file (CAD layout)

MJM MJM JMF Mime Package

PAF PAF Legacy version of Packed Archive Format.

PDF PAF PAFSC Packed Archive Format. Esko native format to exchangegraphics files.

PAG PAG Legacy Esko FastImpose "page" file

Page - Item in Pages View (Esko page workflow)

PageSlot - Empty item in Pages View (Esko page workflow)

PDF PDF Portable Document Format

PDF Plato PDFPLA Esko Plato layout (PDF with references)

NormalizedPDF

PDF PDF checked by Esko for print-ability, enriched with XMPmetadata, allowing external references

PDF Station PDFSTA Esko Plato "station" file

PICT PICT, PCT Old file format often used for screenshots

PLA PLA Legacy Esko FastImpose "plate" file

AdobePageMaker

PMD Native file

PNG PNG Portable Network Graphic (picture)

PPF PPF Print Production Format (CIP3 ink key settings)

PPML PPML Personalized Print Markup Language, XML-based standard forVariable Data Printing

PostScript PS PostScript file

PSD PSD Adobe Photoshop file

MicrosoftPublisher

PUB Native file

QuarkXpress QXD, QXP Native file

Rich TextFormat

RTF Text format

RTL RTL Old pixel format for HP proofers

RunList Runlist List of required page or station files (imposition and layoutworkflow)

Section - Item in Esko page workflow

10

2Automation Engine

File Type FileExtension

Description

Sheet - Item in Esko page workflow

Sheet Side - Item in Esko page workflow

SIG SIG Legacy Esko signature file (page workflow)

STA STA Legacy Esko Plato "station" file, GRS format

TCP TCP Esko legacy Trapping Color Pair

Tiff TIF, TIFF Tagged Image File Format

TIFF/IT TIF, TIFF, LW,CT...

Version of TIFF, bitmap separations

TXT TXT Simple text format

U3D U3D 3D graphics format, supported by Acrobat

VRML WRL 3D graphics format

MicrosoftExcel 97 - 2003

XLS Older version of spreadsheet file

MicrosoftExcel

XLSX Spreadsheet file

XML XML Extensible Markup Language

ZAE ZAE Format for interactive 3D applications, full version

ZIP ZIP Archive file

Automatic File Type Determination

Several Views in the Pilot show a column File Type. The shown file type determines thefunctionality that the Pilot offers on that file.

Several steps are used to determine the correct file type:

1. The Pilot immediately shows the file type based on the file's extension.2. In the next second, for some files, a second check is done. This can change the shown

file type. For example: The file type of a file with an extension .AI that was saved as PDFcompatible, will so change from "Adobe Illustrator file" to "PDF file".

Note: This extra check is not done for all file formats. To manually change the file type ,right-click the file and choose "Change File Type". This can for example be necessary toenable launching a specific task on that file.

3. When a task is started, the task does an extra check as well, to make sure it is worthlaunching that task on this file. This for example also happens when Access Points receivefiles with an extension that you cannot control.

11

2 Automation Engine

2.2. Normalized PDF in Automation Engine

2.2.1. Introduction

Document ConventionsIn this document, PDF files that have not gone through normalization will be referred to as“PDF”. PDF files that have been normalized will be referred to as “Normalized PDF”.

Normalization in Automation Engine 16 and later

There are 2 types of tasks in Automation Engine:

• PDF tasks: These tasks can process PDFs directly without prior normalization.

• Normalized PDF tasks: These tasks require a PDF to be normalized before furtherprocessing.

These 2 types of tasks can be mixed in a workflow:

• PDF tasks will process Normalized PDFs.• Normalized PDF tasks will automatically normalize regular PDFs.

2.2.2. What Makes a Normalized PDF Special?

Normalized PDFs are to a large extent regular PDF 1.6 files, except in a number of specificareas.

OverviewNormalized PDF differs from regular PDF 1.6 in these areas:

• External references• Color space• Document level metadata• Object level metadata

External referencesA Normalized PDF is not always self-contained. It can refer to images or other PDFs that arenot embedded in the PDF itself. Making use of references instead of embedding images and/orgraphics can have several advantages in the workflow.

The main advantage is that it allows for “late binding”. For example: an image can be colorcorrected. After the color correction all PDFs that refer to this image will automatically containthe corrected version of the image without the need to open and rewrite all those PDFs. 

Working with Normalized PDFs with external referenced can also lead to faster processing,especially when the Normalized PDF refers to large amounts of external image data.

12

2Automation Engine

Although referring to external files is a standard PDF feature (for example used in the PDF/X-5),most PDF applications do not support this. To guarantee that a PDF can be processed correctlyby a PDF application (like Adobe Acrobat), it has to be made self-contained (embedding all thereferred components like images). A self-contained Normalized PDF is 100% PDF compatible.

Color spaceA Normalized PDF can only contain objects in the final printing color space. This final printingcolor space can have any number of separations but in most cases this will be CMYK and somespot colors. The PDF object model allows objects to be defined in RGB and CIE based colorspaces. This is not possible in Normalized PDF. During normalization such objects are colorconverted to CMYK.

The fact that Normalized PDF cannot contain objects in RGB or CIE based color spaces is itsbiggest limitation. On the positive side, it makes the workflow more predictable. It avoidslate and often somewhat hidden color conversions (for example in the RIP) that can lead toproblems in printing.

Document level metadataA Normalized PDF contains XMP metadata. The schema of the XMP data is Esko specific, butthe specification is public. The XMP metadata serves 2 purposes. It contains info about thefile that can be extracted by 3th party applications and used for example for quality controlor asset management. The XMP metadata are also used by Esko applications like AutomationEngine to retrieve information from a PDF in an efficient way (for example the number ofseparations).

Object level metadataA Normalized PDF contains metadata for specific objects like barcodes. Object level metadataare added to allow modification of those objects using an Esko application. Object levelmetadata are stored using a proprietary mechanism and format.

2.2.3. Which Tasks Require PDF Normalization?

The table below lists the Automation Engine tasks...

• that require normalization and will normalize regular PDFs automatically (Normalized PDFTasks),

• that do not require normalization (PDF tasks).

Note: The exact list of tasks available on your Automation Engine Server depends on thelicenses you have, so some tasks in the list below may not be visible in your Pilot.

Normalized PDF Tasks PDF Tasks

Add Ink Eaters Adjust PDF Screening

Check Job Parameters Compare PDF

Check Print Rules (PRC) Create PDF File from RunList

Convert CMYK Colors Extract Inks

Convert Colors with Equinox Optimize PDF Document

Create Design (DesignWizard) Optimize PDF Separations

13

2 Automation Engine

Normalized PDF Tasks PDF Tasks

Create PAF/JPG/XML (LinkEdge) Preflight with PitStop

Create Report (ReportMaker) Process PDF Spreads

Enrich Black Resize PDF for Output

Export to 3D Resolve OPI

Export to ArtPro File Split Pages

Export to EPS/DCS File Version PDF

Export to PDF File Image to Screened Separations

Export to PostScript File Image to Unscreened Proof

Export to VRML File Image to Unscreened Separations

FastVariants (all tasks) Inspect Artwork

Manage Colors Inspect Barcodes

Optimize and Clean (PSFix) Inspect Braille

Outline Fonts Inspect Spelling

PowerTrapper Inspect Text

Prepare Station Merge PDF Files

RIP (all tasks) Proof for Content Approval

Trap (all tasks) Proof for Contract Approval

Check Product Parameters Step and Repeat Tabular (Dynamic)

Create Cad Sheet Step and Repeat Template (Dynamic)

Create Tiles Verify Certification

Load Structural File

Prepare for Viewer

Prepare Graphics for Nesting

Step and Repeat CAD based

Step and Repeat Tabular

Step and Repeat Template based

2.2.4. How do PDF Tasks Work with Normalized PDF Files?

Important: The PDF tasks require self-contained input files and will therefore automaticallyembed all external references where needed.

The example workflow described here takes a file, removes the separation named “Cut” andtraps the file. It can be used with both Normalized and regular PDF documents.   

14

2Automation Engine

 We here describe how Automation Engine processes a Normalized PDF input file in thisworkflow:

Task Task Type Description

Optimize PDFSeparations

PDF task The task checks whether the Normalized PDF input filecontains any external references to images or otherNormalized PDFs:

• if there are external references, the "OptimizePDF Separations" task will first make the NormalizedPDF input file self-contained (by embedding all theexternal references).

• if there are no external references, the task willprocess the Normalized PDF directly.

The task also updates the XMP document metadata.

Trap withPowerTrapper

Normalized PDFtask

The task traps the Normalized PDF file.

2.2.5. How Do Normalized PDF Tasks Work With Regular PDF Files?

We here describe how Automation Engine processes a regular PDF input file in our sampleworkflow. 

 

 

Task Task Type Description

Optimize PDFSeparations

PDF task The PDF is processed directly, because "Optimize PDFSeparations" is a PDF task.

Trap withPowerTrapper

Normalized PDFtask

The task detects that the input file is a regular PDFdocument, and automatically normalizes it. After that,the file is trapped and a self-contained NormalizedPDF is produced.

15

2 Automation Engine

The ticket that is used for this Automatic Normalization can be configured in theConfigure tool (In the Pilot, go Tools > Configure > Processing Preferences > AutomaticNormalization).

 

 

By default, Automation Engine uses the ticket named “OnDemand”, a ticket of the NormalizePostScript/PDF/Illustrator 8.0 File task. From this ticket, only the settings in its tab “ColorManagement” are taken into account. All other settings of the auto-normalization are forcedto fixed default settings. For example, automatic normalization will always embed all images.

 

16

2Automation Engine

 

2.2.6. PDF Normalization and Step and Repeat

The step and repeat tasks from Automation Engine 12 onwards can handle PDF, NormalizedPDF or a mix of both at the input. The resulting output depends on a setting in the step andrepeat ticket.

Output formatsDepending on your choice in the Output Format list of the Step & Repeat ticket, the format ofthe resulting document can be:

• PDFPLA• a self-contained Normalized PDF• a regular PDF

 

 

PDFPLAWhen you choose this option, the output of the step and repeat task will be a PDFPLA file. A PDFPLA is a Normalized PDF with external references to the one-ups. It can be loaded and

17

2 Automation Engine

modified in Plato. It can be RIP'ed directly by Esko Imaging Engine and FlexRip. To send it to anon-Esko system, the PDFPLA first needs to be exported to a PDF using the Export PDF task.

Note: PDFPLA output can only be generated if all the inputs are Normalized PDFs. The taskwill fail if a one-up at the input is not normalized beforehand.

This format is the recommended output format when the primary purpose of the step andrepeat file is to send it to Imaging Engine or FlexRip.

Normalized PDF (embed all)When you choose this option, the output of the step and repeat task is a self-containedNormalized PDF. The one-ups are embedded in the PDF using "PDF forms" so that the file sizeremains compact. The file can not be modified in Plato. It can be RIP'ed directly by an ImagingEngine or FlexRip. It can also be sent to a non-Esko system.

Normalized PDF inputs will be embedded in the output. PDF inputs will be auto normalizedand then embedded in the output.

This format is recommended when further processing is needed on the output, forexample by the "Optimize PDF Separations" task before sending it to Imaging Engine orFlexRip.

PDFWhen you choose this option, the output of the step and repeat task is  a PDF. The one-upsare embedded in the PDF using "PDF forms" so that the file size remains compact. The file cannot be modified in Plato. Imaging Engine or FlexRip can not RIP this file directly ; they will firstautomatically normalize the step and repeat file. This file can be sent to a non-Esko system.

Normalized PDF inputs will be embedded in the output. PDF inputs will be embedded in thePDF “as is”.

This format is recommended when the primary purpose of the step and repeat file is tosend it to a third-party, a non-Esko RIP.

2.3. XMP MetadataXMP stands for ‘eXtensible Metadata Platform’. XMP is a technology that allows embeddingdata about a file, known as metadata, into the file itself ,in the format of XML. It is a standarddefined by Adobe.

Adobe uses XMP in its own applications like the Creative Cloud applications (Acrobat,Illustrator, InDesign, Photoshop,…) and has defined a number of XML schema. The XMPframework was designed to be extensible so that other vendors like Esko can define additionalschema and add their XMP metadata to the file as well.

When Esko applications "normalize" data, they also add XMP to the resulting PDF file. Filescreated by an Esko RIP also contain XMP.

An example: In the Pilot, the Info dialog shows you the XMP of the selected file (here anormalized PDF): 

18

2Automation Engine

 

Some advantages of XMP:

• By only reading the XMP, you can learn a lot about the file without really opening the file.• Quality control tools can read the metadata and compare specifications against actual

values.• Asset management applications can read the metadata and use this information to

catalogue digital files for fast search and retrieval.

Learn more in the separate document "XMP Metadata". Find this PDF next to the AutomationEngine documentation, as part of the "Related Documentation".

19

3 Automation Engine

3. Important Concepts and Work ModesWe here introduce some important terms that we use in the next chapter Getting Started.

Note: This is a good time to check the interactive Learn Module that introduces the Pilot. Findit next to the documentation on Automation Engine's documentation web page.

3.1. Containers (introduction)A Container is a network share that contains data that Automation Engine can work with.Containers can be located on your Automation Engine server or on another computer in thesame LAN (Local Area Network).

You can create a Container by using (part of) an existing network share or you can haveAutomation Engine create the network share while creating a Container. To manageContainers, go to Tools > Containers.

The installation of Automation Engine by default creates an "ExampleJobContainer" on thedisk drive where you installed the server software.

You can add many more Containers. You can see and browse through them in the Pilots’Containers mode. An example:

 

 

Looking at Files or Looking at Database Items

As a Pilot user, you can choose to

• Use the Files view, where you see and manage data by browsing through Containers.This is a classic way of accessing data, but if you combine it with using SmartNames andWorkflows, you can also get a high level of automation.

• Use one or multiple Pilot Views that offer faster and smarter ways to access and managedata.

• Jobs: a database representation of "jobs to do". Each Job has it's specific parameters.One of those is the folder containing the data for that specific Job. In the Pilot, these JobFolders show up as a blue folder.

• Products: a database representation of one-up assets, easily linked to Job where they playa part in. This is typically used at packaging and labels sites that do print re-runs. Usingthis Products tool significantly improves their data management.

20

3Automation Engine

Many more Pilot Views focus on a specific type of workflow or output. All these Views areintroduced in Pilot Views and Tools. Some are described in detail in dedicated chapters.

3.2. Jobs (introduction)

What is a Job?In Automation Engine, a Job represents work that has to be done. A Job contains all the filesand information related to a specific job-order. A Job has a unique name. Depending onyour type of business, your Job could be to create a specific asset or to physically producesomething, or a combination of both.

A Job represents a job-order and is therefor also "WIP": Work In Progress. This also means that,in Automation Engine, you should remove Jobs that are finished. The Jobs database can hold afew thousands Jobs, but having that many Jobs means that there is something wrong with howyou use this tool.

A Job is an item in the Automation Engine Jobs database, its Job folder is displayed as a bluefolder .

In the Containers mode and Files view, you can see the location of Jobs in their Container: 

 

Once a Job is open ("Last used Job mode"), you can see its subfolders and files. 

 

Job Metadata (Job Setup Parameters)A Job can have an extended set of metadata: inks, barcodes or layouts to use, customerinformation, categorizations or any other custom parameter. This metadata is also stored inthe Jobs database, and can be used when launching tasks on files that are present in the Jobfolder of Job.

21

3 Automation Engine

Ideally, these Job Setup parameters are not set manually but came in automatically when theJob was created by your business system.

Job based Automation

Automation Engine is very Job-centric. Workflow tasks can take their settings from the JobSetup. They can even be launched automatically when the Job reaches a certain status (forexample: all the expected files have been delivered, the Milestone changed to 'Approved'etc...).

Note: When you choose not to work with the Jobs tool, you can still get a similar level ofautomation by using alternative tools like Workflow Parameters.

Job Folders

Each Job has a Job Folder. Job Folders are located somewhere in a Container and typically havea similar substructure, for example specific subfolders for artwork, production file(s), proof orother output file(s).

Learn more in the dedicated chapter Jobs.

3.3. Products (introduction)

A Product represents a production asset. The Products database stores their location and theirmetadata, for example their status.

The Products view is a user-friendly, searchable view on the Products database. You can use itto create new Products, search them and link them to Jobs.

Customers doing a lot of print re-runs use the Products tool to easily re-link production filesthat they printed earlier to the new Job (the one representing the order where the product wasre-ordered).

Learn more in the dedicated chapter Products.

3.4. Page Workflow Views and Tools (introduction)

Customers with page (imposition) workflows typically combine the Jobs tool with the 3 Views inthe category "Commercial Print":

• The Pages view allows to build page lists, monitor incoming pages and their individual stateof approval.

• The Proofs view shows the proof data that was made of the imposition and its status.

• The Plates view shows the status of the expected plates for that Job.

Impositions can be created with Esko FastImpose or with non-Esko applications.

Automation Engine is fully equipped to serve high automated JDF workflows.

22

3Automation Engine

Learn more in the dedicated document on "Commercial Print (Page) workflows in AutomationEngine". Find it next to this "Complete Manual" on https://www.esko.com/Support/Product?id=Automation%20Engine.

23