CERM - Business Management Software for Narrow Web …



*** This topic is under construction ***

Checklist for a standard Cerm – Esko Implementation

For CERM - Esko Automation Engine Integration for narrow-web labels v2

The goal of this document is to describe operational test procedures and checklists for every workflow of the ‘White Paper’ implementation of the Cerm - Esko Automation Engine integration. The end target is to have a final approval by the Esko consultant, the Cerm consultant and the customer for all workflows.

|Customer Name : |

|Customer Address : |

|Test date : .......... / ........... / ................... |

Application properties

1 Cerm Software version : _______________________

2 Esko Automation Engine Software version : ______________________

Product workflow

To perform this test, you need 3 PDF sample files for a product

1. PDF-file 1: With a wrong size, and an unexisting color.

2. PDF-file 2: With a correct size, but with a problem that will not pass preflight (e.g. lowres image).

3. PDF-file 3: With correct size and without problems so it passes preflight, but with an other unexisting color.

You should use ‘regular’ operators login, no ‘Administrator’.

1 Test procedure 1-up product workflow :

• Cerm

• Delete 1 unused Pantone color out of the PMS list

• Synchronize Pantone colors, check the re-creation of the deleted pantone color

• Create a new product (and new prepress job) for a customer with a contact ‘approver’ that has your own email address

• Enter some prepress job instruction text during product creation

• Default New Product artwork status = WaitingForFiles

• Send JDF of prepress job to Esko

• Esko

• Job creation

• Info

• Smartnames

• Job Data Zone with subfolders

• EditingInstructions (ticket waits for operator)

• Product creation

• info

• smartnames

• Product Data Zone with subfolders

• Product artwork status = WaitingForFiles

• Ticket launched upon Job Creation : J-CreateWCProject

• Cerm

• Remove prepress job instruction text

• Upload sample PDF-file 1

• Product artwork status change = DigitalArtUploaded

• File is timestamped in uploads subfolder and put in PDZ root

• Esko

• Product artwork status change = DigitalArtUploaded

• Ticket launched = J-Size

• XML for sizecheck is created in hotfolder

• Cerm

• Hotfolder for import product colors is read

• Sizecheck is executed

• Product artwork status change : SizeNOK

• Esko

• Product artwork status change = SizeNOK

• Cerm

• Now upload sample PDF-file 2

• … Product artwork status change = SizeOK

• Esko

• Product artwork status change = SizeOK

• Ticket launched = J-OneUP_WFL

• Preflight fails, Product artwork status change = PreflightError

• Preflight document is created in Web4Labels subfolder of the PDZ

• Cerm

• Product artwork status change = PreflightError

• Preflight document is found in Web4Labels subfolder of the PDZ

• Finally upload sample PDF-file 3

• Esko

• … Product artwork status change = PreflightOK

• XML for colors is created in hotfolder

• JPG thumbnail will be created in PDZ root

• Softproof report will be created in Web4Labels subfolder of the PDZ

• Product artwork status change = PageProofed

• CERM

• Product artwork status change = PageProofed

• Hotfolder for import product colors is read

• Product colors are correct

• JPG thumbnail is shown

• Softproof report is found in Web4Labels subfolder of the PDZ

• Esko

• Open the product PDF in PackEdge (or an other Editor)

• Track Edit Session is started

• Create the unexisting pantone color reference in a color book

• (open the file for at least 1 minute)

• Track Edit Session is closed

• Cerm

• Check the Track Edit Session booking in the prepress job clockings

• Synchronize Pantone colors

• Check colors in product, pantone color thumb should be colorful

• Send softproof email to customer

• Softproof email and attachment should arrive on your own email address

• Product artwork status change = ProofSent

• Esko

• Product artwork status change = ProofSent

• Cerm

• Manually change status to reject the product

• Product artwork status change = PageRejected

• Esko

• Product artwork status change = PageRejected

• Ticket launched = J-OneUP_WFL_Correction

• Cerm

• Approve Product

• Product artwork status change = PageApproved

• Esko

• Product artwork status change = PageApproved

• Cerm

• Take prepress job out of WIP

• Esko

• Prepress job is removed (RemoveJob)

• Cerm

• Change product status to ‘end-of life’

• Product administrative status change = Obsolete

• Esko

• Product status change = Obsolete

• Ticket launched = J-MakeproductObsolete

2 Checklist 1-UP product workflow

Use the checkboxes below to indicate whether a check is done and write the result behind each check:

• Write ‘OK’ if the check was successful

• Write ‘NA’ (non applicable) if the check wasn’t executed and add some comments to explain why it is skipped.

□ Product artwork status synchronization

□ WaitingForFiles

□ DigitalArtUploaded

□ SizeNOK

□ SizeOK

□ PreflightError

□ PreflightOK

□ PageProofed

□ ProofSent

□ PageRejected

□ PageApproved

□ Product administrative status synchronization

□ Obsolete

□ Tickets

□ J-CreateWCProject

□ J-Size

□ J-OneUP_WFL

□ J-OneUP_WFL_Correction

□ RemoveJob

□ J-MakeproductObsolete

□ Hotfolder Product XML

□ Product Data Zone

□ Thumbnail

□ Web4Labels

□ Preflight report

□ Softproof

□ TrackEdit session

□ Synchronisation Pantone Colors

□ Softproof email

□ Prepress Job text = EditingInstructions

□ Webcenter viewer

|Checks performed and results approved on : |

| |Cerm consultant |Esko consultant |Customer |

|Name: | | | |

|Signature: | | | |

S&R workflow digital print

You should use ‘regular’ operators login, no ‘Administrator’.

The procedure below describes the workflow up to printing on a digital HP Indigo press, you have to shorten the procedure and checks if an other type of digital press is used. The features marked with (*) only apply to HP Indigo presses.

1 Test procedure :

• Cerm

• Synchronize JDF parameters of the HP digital press

• Tickets

• Colorstrategies (*)

• Marks (*)

• Digital media

• Create a label job with autoplan

• multiple products

• with some 180° opposite windings-orientation within 1 frame

• on multiple frames

• different quantities per frame

• waste for finishing (to be printed)

• Fill out all necessary JDF parameters of the job (ticket, colorstrategy(*), mark(*) and the paper (digital media) for the digital press

• Send JDF of the job to Esko

• Esko

• Job creation

• Info

• smartnames

• Job Data Zone with subfolders

• Ticket launched J-S&R-Digit-JDF

• Per frame (splitter)

• S&R created

• Bleed

• Marks

• Winding-orientation

• Status

• Die-Cut PDF created

• Inspection tools package created

• Send to digital Hp Indigo press (DFE) task started (*)

• Cerm

• Check job data zone

• Check S&R status

• Esko DFE

• Multiple jobs are created (1 per frame) with

• Color strategy (*)

• Ticket

• Digital media

• Marks (*)

• Rip

• Send to press

• Press

• Print jobs

• Winding

• Marks

• Barcodes on frame (inspection)

• Paper width

• Quantity per frame

• Lilo printing in 1 color

• Cerm

• Check Press clockings

2 Checklist digital S&R and print workflow

Use the checkboxes below to indicate whether a check is done and write the result behind each check:

• Write ‘OK’ if the check was successful

• Write ‘NA’ (non applicable) if the check wasn’t executed and add some comments to explain why it is skipped.

□ S&R

□ Per frame with bleeds, marks and orientation

□ Press selection

□ Inspection

□ Package created

□ Barcode present

□ Die-cut

□ Die-cut ink only

□ PDF is ready (in die-cut repeat length)

□ Digital press parameters

□ Digital Media

□ Job ticket

□ Color Strategy

□ Marks

□ Print result

□ Quantity per frame correct

□ Die-cut ink is not knocked out nor printed

□ Lilo printed in only die-cut color

□ Bleeds, marks and orientation

□ Paper Width

□ Feedback clockings in job

□ Status

□ S&R

|Checks performed and results approved on : |

| |Cerm consultant |Esko consultant |Customer |

|Name: | | | |

|Signature: | | | |

S&R workflow conventional print

You should use ‘regular’ operators login, no ‘Administrator’.

The procedure below describes the workflow up to plate making for a conventional label press.

1 Test procedure :

• Cerm

• Create a label job with autoplan

• multiple products

• with some 180° opposite windings-orientation within 1 frame

• on multiple frames

• Send JDF of the job to Esko

• Esko

• Job creation

• Info

• smartnames

• Job Data Zone with subfolders

• Ticket launched J-S&R-JDF

• Per frame (splitter)

• S&R created

• Bleed

• Marks

• Winding-orientation

• Colour separations

• Status

• Die-Cut PDF created

• Inspection tools created

• Cerm

• Check job data zone

• Check S&R status

• Esko

• Rip

• Check result

2 Checklist conventional S&R workflow

Use the checkboxes below to indicate whether a check is done and write the result behind each check:

• Write ‘OK’ if the check was successful

• Write ‘NA’ (non applicable) if the check wasn’t executed and add some comments to explain why it is skipped.

□ S&R

□ Per frame with bleeds, marks and orientation

□ Press selection

□ Inspection

□ Package created

□ Barcode present

□ Die-cut

□ Die-cut ink only

□ PDF is ready (in die-cut repeat length)

□ Plate result

□ Die-cut ink is not knocked out

□ Bleeds, marks and orientation

□ Image distortion

□ Status

□ S&R

|Checks performed and results approved on : |

| |Cerm consultant |Esko consultant |Customer |

|Name: | | | |

|Signature: | | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download