White!Paper! Integrationof!! EskoAutomation!Engine ... - CERM · Index!! 1.!Intro!&!main!requirements! ... 6.2!Cerm!sends!an!automatic!invitation!to!the!customer!to!approve!in!W4L!(optional!

Integrating Prepress with MIS CERM at NW label printers. An Esko/Cerm White Paper. Last updated 01 September 2014 by [email protected]

1

White Paper

Integration of Esko Automation Engine

with MIS Cerm

for Narrow Web label printers


2

Index 1. Intro & main requirements .............................................................................................. 3 1.1 Overall requirements ................................................................................................. 3 1.2 Requirements on Cerm side ....................................................................................... 3 1.3 Requirements on Esko side ........................................................................................ 3 1.4 Structure of this White Paper ..................................................................................... 4

2. Overview of Standard Integrated Workflow .................................................................... 5 2.1 What is NOT included in this ‘standard’ workflow? ................................................... 5 2.2 What is NOT POSSIBLE, technically? ........................................................................... 5 2.3 What information is exchanged? (overview) ............................................................. 6

Cerm sends 2 types of jobs to Prepress: ............................................................. 6 2.3.1. Esko prepress sends this information back to Cerm: .......................................... 6 2.3.2.

3. Workflow Step 1: a new product is created in Cerm and announced in AE .................... 8 3.1 Concept: ..................................................................................................................... 8 3.2 Note on required logic in the data structure ............................................................ 13

4. Workflow Step 2: artwork file arrives for the new product ........................................... 14 4.1 Design data arrives through Cerm-‐users .................................................................. 14 4.3 Design data enters through Cerm’s Web4Labels ..................................................... 16 4.4 Design data enters through Esko WebCenter .......................................................... 16

5. Workflow Step 3: Esko prepares the product file for approval ..................................... 17 5.1 Automated Preflight in background on AE ............................................................... 17 5.2 Check/Edit of one-‐up prepress file and make proofs ............................................... 20 5.3 What Cerm has received as feedback/proof files: ................................................... 23

6. Workflow step 4: Approval of the one-‐up file ............................................................... 26 6.1 The Cerm user asks for approval (standard workflow) ............................................ 26 6.2 Cerm sends an automatic invitation to the customer to approve in W4L (optional workflow) .......................................................................................................................... 29 6.3 Esko WCR invites the customer to approve (optional workflow) ............................. 30 6.4 When both Web4Labels and WebCenter are used (optional workflow) ................. 30 6.5 The product is approved = End of the prepress job ................................................. 30

7. Workflow step 5: the ‘production job’ ........................................................................... 32 7.1 In Cerm: a sales order becomes a production job .................................................... 32 7.2 The production job in AE (step&repeat and output) ................................................ 37 7.3 LILO in production jobs ............................................................................................. 41

8. Note on ‘End of product Life’ ......................................................................................... 42 9. Note on product statuses .............................................................................................. 43 10. Note on relocation of products ...................................................................................... 44 11. Note on Esko parameter synchronization ...................................................................... 45 12. Work list of the Esko specialist in these 5 days .............................................................. 46 12.1 Tasks that the Esko specialist will do: .................................................................... 46 12.2 Tasks that the Esko specialist will NOT do: ............................................................ 47

13. Confirmation of understanding (please sign) ................................................................. 48


3

Intro & main requirements This White Paper describes the current standard integration between the MIS ‘Cerm’ and Esko’s prepress workflow server ‘Automation Engine’ (AE). It is this integration that can be delivered when the standard Cerm-‐integration solution is purchased from Esko. The integration will be implemented by an Esko specialist. A consultant from Cerm will handle the setup in Cerm. The used applications are

• Cerm v7.11 or higher • Automation Engine 14.0 or higher

1.1 Overall requirements

• The MIS Cerm server and Esko AE server need to be installed within the same network

• Date and time settings on the Esko Automation Engine, the CermBoxx Engine and the end user workstations must all be set to synchronize automatically.

• All clients of both systems need to be able to connect to both servers.

1.2 Requirements on Cerm side

• The MIS Cerm needs to be in use and ready for real production. Cerm users need to be able to create products based on reference calculations, sales orders and production jobs.

• When there is a need to create ‘ganged’ layouts (= multi-‐grid or multi-‐product Step & Repeat’s), then this must be done with the ‘Autoplan’ tool. This tool helps create the high-‐level JDF that enables full automatic step&repeat in Esko.

• When there is need to produce multi size products (like a combination of front, back and neck label) within 1 job it is mandatory to use Cerm “Kit” products. For more info check: http://www.cerm.be/hd/onlinehelp/Modules/products/Kits/Kit_product.htm

1.3 Requirements on Esko side

• The ‘5 days integration package’ will only be used to setup and train the integration.

• What Automation Engine modules do I need?

o Add minimal

§ Job Management Module

§ Layout Module

§ Automation Engine Connect


4

o Advised

§ Viewing & QA Module

§ Reporting & 3D Module

o Optional requirements

§ Processor Module

1.4 Structure of this White Paper

Next in this White Paper, these main chapters are present: • A description of the workflows (first an intro then more detailed).

This will describe the ‘standard’ logic workflow steps. The steps might be different from your current workflow. The steps are not mandatory processes but help to clarify the currently possible integration processes. Cerm and Esko are convinced that this will lead to the best ‘standard’ automation.

• Some extra notes• A description of the actual work tasks that the Solution Architect will do when

on site, including a list (or repeat) of what he will NOT spend time on.• The page we require you to sign when you purchase this integration package.


5

2. Overview of Standard Integrated Workflow

A demo video of the ‘standard’ workflow is available on https://www.youtube.com/watch?v=2NNVLRn-6BY(section software w section ‘workflow integration’). It will help you visualize this integration and its benefits. In the movie you will see that the Cerm web storefront “ Web4Labels” (W4L) and Esko WebCenter (WCR) are used. These optional functionalities are not included in the standard White Paper integration. It is mandatory that the integration between Cerm and Automation Engine is implemented for a while, before W4L and/or WCR can be used. After the Standard Integrated Workflow overview, more details are available about these 2 optional functionalities.

2.1 What is NOT included in this ‘standard’ workflow? As mentioned in the title of the White Paper: this is about narrow-‐web roll-‐fed label production. The following topics cannot be handled in the pre-‐set implementation days that this ‘standard’ package delivers because they are very specific for each different company:

• Communication on multi-‐part products : booklets, multi-‐layer, inprint, …• Communication on multi-‐page artwork : front-‐back, …• Communication on staggered layouts (only manual in Esko tools)• Versioning of products• products that existed before the integration will need to be migrated manually

into the new data structure.The automation and communication on the above topics can of course be discussed during extra service days, possibly at a later stage.

2.2 What is NOT POSSIBLE, technically? Today, the following items are technically not possible to automate through this integration. Or because the concept is not known in Cerm and/or Esko. Some of our customers do have these processes that still need manual tools:

• Non-‐90-‐degree-‐based rotations of stations• Communication on plate/cliché ID/numbers• Communication on Layouts combining labels with different sizes/shapes except

for Cerm “Kits” products.• Communication on Layout for sheet fed printing (only manual in Esko tools)• Ink info from AE to MIS: is to be developed.• Communication on colour details per production method.• Different status for Front/Back Labels: need to be approved as 1 PDF. AE can

only communicate 1 status per product to Cerm.• Exchanging Milestones on job level, other than the standard described in this

White Paper.• Re-‐use of S&R: the Cerm integration process assumes the S&R is always made

again.


6

2.3 What information is exchanged? (overview) All communication between Cerm and Automation Engine is done within a ‘job’: this guarantees that all resulting data and (feedback) info can be stored in the right job-‐context. This then enables correct measuring/statistics. Unless mentioned otherwise, the technique used for the communication is JMF: job Messaging Format (JDF-‐communication over HTTP-‐ports).

Cerm sends 2 types of jobs to Prepress: 2.3.1.• ‘prepress jobs’

‘prepress jobs’ ask the prepress department to create a new product. The new product is based on a technical project (estimate) and probably new artwork is delivered. Prepress makes it print-‐ready and makes proofs. 1 or more approval cycles later the product’s status is ‘Approved/Ready for print’. This is then the end of the ‘prepress job’. When a new product item is created in Cerm, a ‘prepress job’ is automatically created in Esko’s workflow server Automation Engine. Both Cerm and Automation Engine look at the same prepress data, no data is copied. They are both configured to look at the same “product Data Zone” Based on the product status in Cerm, Cerm will automatically start workflow actions on AE. Those workflows will send statuses back to Cerm.

• ‘production jobs’ ‘production jobs’ are more classic jobs: they ask prepress any activity related to the printing of existing products. This is typically plate layout (‘step&repeat’), RIP-‐ing and plate making or direct sending to the digital press. Maybe also some Quality Assurance (QA) steps in that process. Production jobs could also be the re-‐use of an existing plate set (cylinders) from a warehouse.

Esko prepress sends this information back to Cerm: 2.3.2.

• Products Statuses o Confirmation of chosen product status.

An overview of the default product statuses in Cerm:

o And the default product statuses in AE:


7

o All action tags have a “Description” (Cerm) or “NickName” (AE) and can

be localized. For example “DigitalArtArrived” can be shown on screen as “Files Arrived”.

• Product files o Product display files (JPeG, PDF) o Product report files (ReportMaker PDF ; if ReportMaker license if

present) • Product metadata description

o XML file containing all XMP-‐metadata of the Esko production file (PDF or AP):

o Example: often used to report back the real list of ink names (colours) and their ink coverage. Also the real final trim-‐size after prepress editing.

• Job Milestones ( = job level status) o Confirmation of the ‘step&repeat OK’ Milestone of the job. Additional

Milestones can be added on agreement with the Esko specialist and Cerm Consultant.


8

3. Workflow Step 1: a new product is created in Cerm and announced in AE 3.1 Concept:

Whenever a new product is created in Cerm, it is logic that prepress will need to be involved. That is why this action will automatically inform prepress. For every new product that is created, Cerm will automatically create a ‘prepress job’ and send a JDF to Esko AE which will create a ‘prepress job’ with the same ID in AE. The goal of such a prepress job is not to produce but to come to a new and approved product that CAN later be produced. In case of a reprint without any changes to an existing product this step is skipped. In Cerm, a product is often created as a copy of another one. In the picture below is shown how a new Fruit Juice flavour will be based on the previously printed Cherry Juice -‐ typically one of the same ‘production family’ (reference calculation, based on same shape, size, number of colours...).

Upon copy of a product the Cerm software asks whether the new product is a new version of the source product or if it’s a completely new product.

If it concerns a new version of the source product a link is automatically present that refers to that source product ID. By default Cerm always automatically assigns a new product ID. The user enters the new product description, ref. at customer, etc. In this example a new version of the Cherry juice label is created (e.g. because there are some


9

modifications to the ingredients list). If desired, AE can automatically copy the artwork-‐files from the source product into the new product.

If it concerns a brand new product, no link to the source product is made since a completely new artwork is expected. The user enters the data of the new product. In this example a brand new “Tomato Juice” label is added to the Funky Juice series. Since this is a brand new product AE won’t copy any artwork-‐files.

In the next step of the product creation wizard, the initial product status is automatically set to ‘Waiting for Files’. The design files for this new product can arrive in the next


10

seconds or much later (days, weeks…).

The final step creates a prepress job and sends the JDF to AE. The users can also enter a free text instruction for the prepress operator(s). These prepress instructions are send with the job and will show up in an Esko workflow Checkpoint (see later).

Below, the newly created product, with ID 400288, its name and status.

At the same time, a ‘prepress job’ is automatically created with its ID, customer, customer service representative (CSR, in Cerm named ‘job Manager’), etc. This job is used to ask prepress to do something. In this example to make the new Tomato Juice label ready for print.

The same prepress job ID arrives automatically in Esko AE:


11

In the above jobs overview (filtered), the following columns are available:

• Job name : the ID of this prepress job, as assigned by Cerm • Description: job description as entered in Cerm proceeded by the Cerm product ID

to allow a quick search. • Category is ‘Prepress’ (another category is ‘production jobs’) • Creation and Due date • CSR and Customer name. • Much more info is received that is not shown here (Via the fixed job fields tool or

via extra job parameters) • The Project ID is here mapped to the product ID. This is just a trick to immediately

also see this product ID nr in this jobs overview. Below the overview of prepress job ‘025093’ related to the ‘dummy’ product (since no files arrived yet) with the status ‘WatingForFiles’:

The following information is displayed:

• A thumbnail-‐display of the product with some attributes o The product 400288 was created in the AE products database, but the file

hasn’t arrived yet. The thumbnail is therefore still on ‘N/A’: Not Available, yet (we have no graphics file yet to show..)

o This new product is automatically linked to the job (025093). • The Data Zone:

o 400288: the root of the product’s data folder. o 400288.pdf: the product file


12

o All other files stored within the folder 400288 belong to the product and are part of the Data Zone.


13

3.2 Note on required logic in the data structure This integration requires the use of the AE “products” (part of the job management module). This is an extra database that stores the products, their characteristics, their status and also a link to the actual folder on disk where their actual product file is.

A ‘job’ in AE represents a job-‐order, and so by definition a temporary concept. The AE jobs show up as blue folders. Blue means that they are active; they are WIP: work in progress. When a job is done, the job may be deleted from the AE database. It has no function any more.

It is required in this integration that the data belonging to the products are separated from the data belonging to jobs. Below 2 typical file structures:

Option 1: Product and Job ID based (advised method)

It is advised to use a structure only based on the product ID and Job ID, since it avoids data relocation in case products are moved to another customer (e.g. after a merge).

Option 2: Combination of Customer ID with Product ID and Job ID

It is possible to use a structure which holds the customer ID and then the product ID and Job ID. However, in this case data relocation has to be done in case products are moved to another customer (e.g. after a merge).


14

The agreed data structure will be defined in the parameters and is created automatically. Once a structure is chosen, and products and jobs are created for real production, the structure can never be changed again, without help from Cerm and Esko consultants.

4. Workflow Step 2: artwork file arrives for the new product

4.1 Design data arrives through Cerm-‐users When the artwork file arrives at the Cerm-‐users (CSR/CRMs receiving a DVD, FTP or e-‐mail attachment), they will usually go to Cerm’s products module and assign there the new files to the product. When the artwork file is a single PDF file, a simple drag and drop action can do this:


15

This question will appear to confirm:

Note: Cerm uses the term ‘image’ for any graphical representation. The artwork can of course also be graphical data with only ‘line work’. Below is shown how the product’s (Artwork) status is now automatically changed to ‘DigitalArtArrived’ (shown on screen as ‘Files arrived’)

These artwork files will arrive in the product’s subfolder ‘uploads’.

Above an example of an artwork file in the “uploads” folder: The file was automatically renamed to start with a ‘Date & Time stamp’. This procedure guarantees to always have a


16

backup of the different artwork files (when more versions come in later during several approval cycles) that arrived. When the artwork is composed of multiple files (for example an AI file and several external high-‐res pictures), then the Cerm user will use the ‘Explore’ button into the actual product folder that was automatically created and he will drop the design data in the subfolder ‘uploads’. A classic example of such a product folder. These 3 subfolders will already be present:

A copy of the PDF-‐file that arrived in the uploads folder is stored in the product root folder and is automatically renamed to the product ID. The next Workflow Step chapter shows how the prepress workflow will automatically start from this PDF file in the root folder. But first some remarks on different methods of data arrival:

4.2 Design data enters through Prepress department (AE users) When artwork files arrive at the prepress department, the operators need to

• drop the file(s) into the same products ‘uploads’ subfolder and copy it to the product root folder.

• and after that manually change the product status to ‘DigitalArtArrived’ (shown on screen as ‘Files arrived’)

4.3 Design data enters through Cerm’s Web4Labels When Cerm’s Web4Labels is used, the single PDF file enters via the web and that is the only difference: the same processes and exchanges will happen in background between Cerm and AE. The upload of the following file types is supported in Web4Labels (v2.7): pdf, zip, jpg, jpeg, png, gif or bmp. However, only single PDFs result in an automatic workflow launch in AE.

4.4 Design data enters through Esko WebCenter When artwork files arrive through Esko WCR, the files will be ‘forwarded’ automatically to the right job in Automation Engine. They end up in the same products ‘uploads’ subfolder. And the AE workflow will set the product status to ‘DigitalArtArrived’ (shown on screen as ‘Files arrived’) as well. Cerm users will see that same product status and can explore to that same products ‘uploads’ subfolder.


17

5. Workflow Step 3: Esko prepares the product file for approval As soon as Cerm sets or receives the product’s artwork status ‘Files received’ a size check is executed by default. This size check is done by Cerm based on information (xmp) received from Esko AE. Depending on the outcome of the size check Cerm updates the product’s artwork status to SizeOK or SizeNOK. Only after a successful size check (Size OK) the Esko prepress workflow for one-‐up files (J-‐OneUp_WFL) starts automatically. In the image below the standard AE workflow is shown for prepress jobs. The goal is to end the workflow with an approved product. The Esko specialist will bring this workflow ‘ticket’ with him and adapt where necessary. It basically contains these main steps: preflight -‐> check/edit -‐> proof files -‐> Approval. And includes intermediate product statuses.

These are the main steps in this workflow:

5.1 Automated Preflight in background on AE A classic first action is to perform a ‘Preflight’: to check if the file is OK to start with. If the files shows technical defects (e.g. low-‐resolution images, missing fonts,…) the customer will need to send a new artwork file. The workflow is put on hold until the new artwork arrives. Then, the ‘Preflight’ starts again. The preflight tools in AE are included in the ‘Processor’ module (optional module).


18

Below is shown how the ‘Preflight’ task ended in Red/Error and how the workflow then did set the product status to ‘Preflight Error’ / Red.

As mentioned earlier, any product status is communicated in 2 directions, from the moment AE sets this ‘Preflight error’ status for this product, this will also be immediately visible in Cerm. Later a description follows how the workflow continues when the preflight status was OK. But first the process stops with the “PreflightError” status. The product status was automatically communicated in Cerm like shown below:

The next question is always “What is exactly wrong with this file?”. In a PDF preflight report all detected defects are automatically summarized. This report-‐PDF is by default stored in the subfolder ‘web4labels’ (mandatory subfolder name) with a logical name.


19

This report is accessible for AE users, Cerm users and (when applicable) also for W4L users. When WCR is used, it can be automatically published there as well. This report is visible from the AE pilot. As mentioned before, Cerm and AE are looking at the same data structure:


20

An example of such a report PDF. They can be very detailed if needed.

As a next step in the process the customer -‐ after reading the preflight result -‐ sends a new artwork file. The new artwork file can be uploaded through 1 of the procedures described above. This action results again in the status ‘DigitalArtArrived’ (shown on screen as ‘Files arrived’). As a result, the one-‐up prepress workflow is launched again in Automation Engine. The process can have several loops. Remember that “optional” all incoming artwork files will be kept aside with their original data-‐time-‐stamp. So one can always trace back the older artwork files that came in. From the moment the preflight results in the status ‘PreflightOK’, which means no defects are found in the file, the workflow continues.

5.2 Check/Edit of one-‐up prepress file and make proofs The workflow is routed based on the presence of Prepress instructions.


21

Since prepress instructions were send with this job, the workflow automatically holds on the ‘Wait for action’ checkpoint which allows the operator to consult the prepress instructions to make the file ready for print.

The prepress instructions (1) which were entered upon product creation are visible:

The operator is offered a direct link to open the file in the AE Viewer tool (if present). This can be done via the URL (2) or via the ‘View’ icon (3) The prepress operator will now typically

• view the file in the AE Viewer or in Acrobat Reader • view/edit the file in ArtPro or PackEdge or Adobe Illustrator (DeskPack config)

Note: after editing, the opened file needs to be overwritten. To make the AE workflow continue, this Checkpoint needs to be ‘Released’ (4).


22

When the editing needs to be stopped, the operator can abort the workflow. When time is available during the 5 days package, the Esko specialist can help you build an extra side-‐process that needs to be started up when the Checkpoint is ‘Aborted (for example: send e-‐mail to CSR). After the release of the checkpoint or when no prepress instructions are present in the job, the workflow continues and prepares everything that is needed to ask the customer’s Approval for this product: Below is shown how these task-‐actions are now executed:

• If necessary, extra print marks are added to the one-‐up (‘Prepare Station’ task) • A JPeG is created. Cerm will automatically show it inside Cerm • An XML of the metadata is created; Cerm automatically reads it to shows more

product detail in Cerm: more info further down in this document • A product Report (PDF) is created: see an example further in this document. • A subfolder (Die info) is created which contains PDF-‐file and a JPeG of the one-‐up

which only contains the cutter ink (colour). This file can be used for die ordering.

When all above actions are finished the new product status is automatically set to “Proof ready” As always, the modified product status is immediately visible in Cerm as well.


23

5.3 What Cerm has received as feedback/proof files: As mentioned above, the JPeG, PDF and XML files will be written in places where Cerm expects them; no copies are needed. Cerm will have direct access to these export-‐files. The XML with the metadata will be written in a central hot folder configured in Cerm. The JPG and any PDFs will be found within the product’s Data Zone, also with specific rules on naming and subfolders. Cerm shows the JPeG in its product description panel:

The metadata XML is automatically imported in Cerm and results in the ink list (product colours) and the ink coverage in mm/inch and in % for this product.

The Cerm users have access to product soft proof PDF (with legend) both as explorer-‐view and in an own ‘images’ panel):


24

The Images panel offers an Acrobat Reader way to check the PDFs (e.g. page 1 and 2..):

The ReportMaker template in the AE workflow decides on the nr of pages and their content.

In Cerm’s ‘job overview’, the time that prepress operator Tom spent on editing this product in his Esko editor application (here the minimum of 1 minute) is visible. This is the time the file was open in PackEdge or ArtPro.


25


26

6. Workflow step 4: Approval of the one-‐up file The last status mentioned was ‘Proof ready’ ; this means that the Proof (files) are ready to be sent to the customer. Cerm offers different ways to send these files. An overview of the 3 most common proof scenarios:

6.1 The Cerm user asks for approval (standard workflow)

The Cerm user (usually a CSR) selects (all) products with the status ’Proof ready’ and with 1 click have Cerm send e-‐mails to the customer(s) asking their approval. This procedure in Cerm will automatically attach the soft proof PDF (with legend) to the outgoing mails.

As a result, Cerm automatically changes the product status to ‘Proof sent’. This status update is automatically synchronized to AE.

Note: To prevent scheduling problems, Cerm offers the possibility to remind customers automatically via e-‐mail when a product is not approved yet although it is scheduled for printing the next day: see below an example e-‐mail:


27

Next step is to register the response of the customer in Cerm. Therefore, the Cerm user manually changes the product status:

• Case A: the customer rejects the soft proof : o the Artwork status is set to ‘Proof rejected’ o the CSR can enter an additional prepress instruction (with a time stamp)

As a result the Artwork status update and the JDF are both send to AE, where the Correction workflow (J-‐OneUp_WFL_Correction) is automatically launched. This correction workflow automatically holds on the ‘Wait for action’ checkpoint which allows the operator to consult the prepress instructions to know the details on the correction(s) to make. After editing, the opened file needs to be overwritten and to make the AE workflow continue, this


28

Checkpoint needs to be ‘Released’. As a result the Artwork status is updated to ‘Proof ready’ and the approval cycle starts again. Remarks:

§ this option allows to upload a new artwork file provided by the customer, and the operator decides how to continue.

§ there can be of course a loop of several ‘rejections’ of the same product before the customer agrees on the soft proof. (see case B below)

• Case B: the customer approves the soft proof:

o the Artwork status is set to ‘Proof OK’

As a result, the Artwork status update is send to AE and the workflow in AE will automatically continue.


29

6.2 Cerm sends an automatic invitation to the customer to approve in W4L (optional workflow)

In this case, the end-‐customer is invited to approve online on W4L through an e-‐mail:

Also then, Cerm automatically changes the product status in Cerm to ‘proofs sent’. The decision (approval or rejection) in W4L is automatically communicated to Cerm and updated in AE as well.


30

6.3 Esko WCR invites the customer to approve (optional workflow) When WCR is used for online approval, the Esko specialist will -‐ in the AE workflow -‐ insert the action task to publish the file to the correct WCR project (for that product). The ‘Publish to web’ task is used for this purpose. In this setup, the decision (approval or rejection) is made in the WCR Viewer, AE or Cerm Important requirement: As mentioned earlier, when WCR is used for online approval, it is mandatory that the WCR project represents only 1 product !

6.4 When both Web4Labels and WebCenter are used (optional workflow)

If the customer has both these web-‐products, it is usually the case that the WCR Viewer is integrated into the W4L interface. In this setup, the decision (approval or rejection) is actually made in the WCR Viewer, AE, W4L or Cerm. In this workflow WCR captures the approval and informs AE where the workflow will automatically inform Cerm of the updated product status. And Cerm then automatically informs W4L.

6.5 The product is approved = End of the prepress job The updated product status ‘Proof OK’ will be communicated bi-‐directionally between Cerm and Automation Engine.

As mentioned at the beginning, the goal of a ‘prepress job’ was to get a new product approved and ready for production. Now that the product is approved, this prepress job is automatically removed in AE based on a ‘take job out of WIP’ action in Cerm. It makes no sense to keep this prepress job; it only served as a temporary ‘environment’ to work in. Note:


31

Removing a job in AE removes all job data from on disk. However, all data in the product data zone is kept. AE was not designed to keep many thousands of ‘dead’ jobs. jobs are temporary but products are usually long-‐term; this means it’s logic to keep many thousands of products active in the AE products tool/database.


32

7. Workflow step 5: the ‘production job’ Cerm users will turn a sales order into a production job. Typical main actions here are:

• The choice of a production method • Definition of the sheet layout via Cerm Autoplan • Schedule the production

Thanks to the high-‐level integration, all the required steps in Esko (step&repeat – output) can be automated.

7.1 In Cerm: a sales order becomes a production job A production job can be created:

• after all products have been approved or • in parallel, before products have been approved. The AE workflow will only

continue to create the step&repeat once all products on the job are approved (via the Wait for product status ticket)

A quick overview of these steps: The Cerm user creates a new sales order and starts by setting typical attributes like customer, representative and some dates:


33

Then the actual products are chosen and their quantity is entered: Below is shown how our new ‘Tomato Juice’ label is ordered, within the same Order with the existing ‘Paradise Punch’ and ‘Cherry’ juice labels. The Cerm user sees immediately that all these labels are not in stock so they will have to be produced.

The ‘production’ button will now combine the functions ‘Choose press‘ and ‘AutoPlan’ and create a job.

The first screen in the wizard shows a list of possible presses and their cost price.

In this example, the Cerm user decides for the HP Indigo (small order so best price on digital). The second step shows the ‘AutoPlan’ function, where the layout can be decided (step&repeat). The grid-‐options for this press based on the die cut tool are shown. At the bottom there is a representation of the 4 lanes and the 3 ordered quantities. A thumbnail of the selected product is shown on the left side.


34

When the ‘magic wand’ icon is clicked, the tool will automatically propose the most optimal layout for this job. In this case, the process is digital, so a ganged layout is optimal. If it was a flexo press, the proposed layout would offer to print them not ganged (plate changes). The result of pressing this ‘magic wand’ is shown below. 2 lanes are taken by the Tomato label:


35

This tool also offers a thumbnail based preview of the decided layout:

Now that the layout is defined, the last step in the wizard allows to define some more actions. To enable the communication between Cerm and AE, the “JDF creation and sending” is a mandatory action:


36

Finishing the wizard results in the final job creation. In this example job ID 025094, with its delivery date, quantity and kind of job, etc.

Within the job explorer the related products with their thumbnail, current artwork status and reprint status (New, Unchanged, …) are visible.

The production job was also scheduled automatically. The purple block (1) shows the time on the press, the green block (2) shows the time on the die cutter. The status “S&R OK” is a Milestone that already came in from Esko AE since the workflow was launched


37

automatically and step&repeat is created.

7.2 The production job in AE (step&repeat and output)

Because of Cerm’s AutoPlan tool, AE receives the step&repeat parameters and the ‘station assignment’ (the position of each label on the step&repeat). This allows fully automatic step&repeat creation, even for ganged jobs. All this happens without operator intervention.

The production job ‘025708’ automatically entered Automation Engine:

In the details of this production job the 3 products were ‘linked in’ into this job. The tasks monitor at the bottom of the screen shows the workflow that was automatically started by Cerm.


38

The step&repeat PDF-‐files are automatically written in a fixed subfolder (Plate_layout) of the job:

• The Esko PDFPLA file (the original step&repeat file created by the workflow) • The exported PDF (the same step&repeat with all external references embedded) • The die-‐cut file (a step&repeat based on the die-‐cut properties out of Cerm which

only contains the cutter colour).

These step&repeat files can be viewed in the AE Viewer. Notice the small marks on the right side of the layout, automatically inserted here for the die-‐cutter.


39

Obviously, when the job needs to be printed ‘conventionally’ the automatic selected print marks will be different. Let’s have a closer look at these AE workflow tickets that manage this production job: The J-‐S&R-‐JDF workflow is started automatically. The purposes of this flow are:

(1) check whether the different products are approved. The workflow will wait until all products are approved.

(2) find out the type of production: conventional or digital. The type then decides which sub-‐workflow will be used for step&repeat and output.

The conventional workflow (J-‐S&R-‐CONV-‐JDF):

(1) The S&R is based on the JDF coming out of Cerm’s AutoPlan tool. Then a self-‐contained ‘fat’ PDF is made.

(2) Optionally, an extra version is created with only 1 row: this can be useful to feed to inspection systems (this is not included in the standard 5 days implementation).

(3) At the end of the workflow, when all tasks ended successfully, the Milestone ‘Imposition done’ is confirmed. This Milestone confirmation is automatically picked up by Cerm, which updates the job status there as well.


40

The digital workflow (J-‐S&R-‐DIGIT-‐JDF):

(1) The S&R is based on the JDF coming out of Cerm’s AutoPlan tool. The Milestone ‘Imposition done’ is confirmed. This Milestone confirmation is automatically picked up by Cerm, which updates the job status there as well.

(2) The cutter ink (colour) can be extracted from the created step&repeat file and used for die-‐making.

(3) Optionally, an extra version is created with only 1 row: this can be useful to feed to inspection systems (this is not included in the standard 5 days implementation).

(4) Optionally, files are created for the ‘zero-‐setup’ with the AVT camera inspection system.

(5) In case the digital press front-‐end is DFE powered by Esko, the DFE job parameters are filled out automatically based on Cerm JDF information. The level of information that is exchanged will depend on the DFE version.

Once printed on a digital press or when plates are processed, the production job is completed for AE. Similar to prepress jobs, the production data will be automatically removed in AE based on a ‘take job out of WIP’ action in Cerm. It makes no sense to keep all production jobs, since a future reprint will generate a new job anyway. Notes:


41

• Station orientation in step&repeat: Cerm defines the orientation of each label on the web in Autoplan. This will take into account the number of offline finishing’s and final winding of the product.

• Plate distortion: the number of teeth of the print cylinder is communicated by

Cerm through the JDF. AE calculates the appropriate distortion based on a conditional Smartname. The distortion values and all existing print cylinder sizes need to be provided by the customer. The Esko specialist will add them into the system.

• Shrink sleeve distortion: if the shrink sleeve application is part of the customer’s product portfolio, the distortion applied on the web width direction is communicated by Cerm through the JDF.

• S&R orientation: the printing direction of the step&repeat is communicated by Cerm through the JDF. On screen the vertical axis refers to the print direction. No rotation should be applied on the complete step&repeat before ripping. The consequence can be that all mark-‐sets need to be re-‐build.

• DFE training: the Esko specialist won’t have time within the standard 5 days integration to train on digital (DFE) workflows. Manual sending and printing to the digital press should already be in production for a while before this extra DFE integration with Cerm is added.

7.3 LILO in production jobs

The JDF from Cerm can contain extra LILO (Lead In Lead Out) information for the HP DFE. This will print a job info label at the start and the end of the job and/or print additional lead in and lead out labels, which contain only the cutter ink (colour) to save print clicks for offline finishing. The number of LILO sheets is included in the JDF information.


42

.

8. Note on ‘End of product Life’ When a product is never to be produced again, it is marked ‘End of Life’ (EOL) in Cerm. On the AE side, this EOL status automatically starts a workflow (J-‐MakeproductObsolete) on the product which sets the product status to ‘Obsolete’.

If desired, products with the ‘Obsolete’ status can be filtered from the AE products database and deleted manually. Cerm consultants will always advise to create a new product ID for any change on a product that is already produced (printed) once. This will avoid all possible conflicts.


43

9. Note on product statuses As documented above, a significant part of the connectivity is based on the status of the product. A change in product status is indeed typically a signal for a workflow to start or continue. The standard product statuses and related workflows have been described above. However, there are still frequently asked questions related to statuses:

• Can they be renamed? o yes, by Cerm and Esko specialists o typically to more personal phrasings or translations

• Can you add extra ones? o yes, simultaneously by Cerm and Esko specialists o What can NOT be done in the standard 5 days integration package is

extending the workflows based on additional product statuses. However do not hesitate to contact Cerm or Esko to explain this request.


44

10. Note on relocation of products Depending on the implemented file structure for the products (when customer ID is included), it can be necessary to relocate the products when the customer of the product changes (e.g. 2 customers merge into 1). A standard workflow (J-‐Relocate-‐product) exists to relocate the product from the old directory to the new directory with the new customer ID.


45

11. Note on Esko parameter synchronization Between AE and Cerm, a number of parameters can be automatically synchronized through a scheduled task in Cerm:

• Colors • Colorbooks (like Pantone or customer spot colour references) • Colour strategies • Marks (only for use in a DFE) • Media • Job tickets (only for use in a DFE)


46

12. Work list of the Esko specialist in these 5 days

12.1 Tasks that the Esko specialist will do:

• AE job Creation • AE product Creation: this is usually very new and requires quite some time to train • Synchronize product statuses • Handle file reception in AE and the “add to product” step • PDF Pre-‐flight if available • Fully automated step & repeat • If relevant implement a tool to calculate the (flexo) plate distortion • ReportMaker usage based on existing ReportMaker templates • Adjusting existing SmartMark sets for Step & Repeat • Approval to WebCenter, if WebCenter is already used in production • Output workflow to RIPs • Manage the metadata XML file to Cerm with ink and ink coverage information • Manage the JPeG for Cerm • Manage a workflow for new designs based on existing product in Cerm and Esko AE • Manage Combo Press support (the extra ink-‐tags like ‘flexo’ or ‘silk’ and how they

help selecting inks to specific RIPs) • Manage the standard set of AE Tasks launching by Cerm based on product statuses • Manage the text based editing instruction that Cerm users can send to AE

operators • Advise on job Management (clean up jobs in AE when deleted in Cerm) • Manage semi-‐automatic clean-‐up of products based on their latest status in Cerm. • Training of a power user of Automation Engine. • Manage the job relocate workflow. • Manage product end-‐of-‐life workflow • Manage legend on LILO (if applicable)


47

12.2 Tasks that the Esko specialist will NOT do: Within the available time frame for this standard integration, the Esko specialist will NOT be doing these tasks:

• Installation / upgrade / virtualization of software • Migrating old data structures in place before the project started • Multi-‐page (e.g. front/back printing) workflow • Multi-‐part (e.g. booklets or multi-‐layer or inprint) labels workflow • Staggered layouts • product versioning workflows • E-‐mail sending from AE • Create and train extra preflight profiles • Creating extra PDF of layout with only 1 row (used by inspection systems) • WebCenter setup or integration • Creating new SmartMarks • Creating new reports templates • Creating additional DFE workflows • Extending workflowset based on additional product statuses • Automation Engine training not related to the integration • Any other task that is not defined in the above listed task list for standard integrations.

As mentioned earlier: extensions to this standard integration are possible. Solution Architects are often asked to come back and extend the initial workflow. Inform your Esko sales contact with a brief description of what you would like to achieve extra. A Solution Architect can return a quick advise if this request is possible and, if so, what extra days will be required to analyze and implement this.

This concludes the overview of what information is exchanged between Cerm and Automation Engine during a standard integration project. **************************************************************************


48

13. Confirmation of understanding (please sign) When purchasing the ‘Standard integration of Automation Engine with Cerm’ package from Esko, please do sign below and send this page to your sales contact. Thank you very much! Company name: Full Name: job function: Date:

“I have read and understood this White Paper” Signature:

White!Paper! Integrationof!! EskoAutomation!Engine ... - CERM · Index!! 1.!Intro!&!main!requirements! ... 6.2!Cerm!sends!an!automatic!invitation!to!the!customer!to!approve!in!W4L!(optional!

Documents