So there we are early in the morning driving down to the EuroTunnel to attend a partner technical meeting for ADAM software discussing the the process of pre-flight and where it fits into the whole business process flow of our production plants.
Lets first look at the term pre-flight: wikipedia describes it as:
The term used in the printing industry to describe the process of confirming that the digital files required for the printing process are all present, valid, correctly formatted, and of the desired type. The term originates from the pre-flight checklists used by pilots. The term was first used in a presentation at the Color Connections conference in 1990 by consultant Chuck Weger.
By definition it would say that the pre in pre-flight is that process of checking before any actions are performed, i.e. before you create the PDF/postscript and not after you have taken the action….. surely that would be post-flight?
But ok, the term pre-flight has become synonymous with the process of checking your files are fit for purpose regardless of where in your workflow you perform it.
Is this correct? Should we be pre-flighting our files at every stage of the process?
Having spent a few hours yesterday with Esko going through what their latest version of there software and asked the presenter…. Surely if you are pre-flighting a PDF you have already generated the file from it’s original components and thus it would be a post-flight.
He thought about the question for a moment, then agreed that actually that was a good point and something that their Instant PDF product tries to address by ensuring that the source documents are correct before generating a Certified PDF.
What options do you have these for checking those source documents you receive on a daily basis? Well it would appear that the only commercial software available outside of the applications is the Markzware Preflight Professional, another option is Freeflight that is provided by the user community and available here; but the problem is that they are both having to reverse engineer the changes in the design applications.
Both Adobe and Quark have added on the fly pre-flight into their applications, Quark by applying Job-Jackets with the ability to test your design to a profile, where Adobe have chosen to use a live pre-flight based on a selected profile….. Are these any good for automating? Not really……
Markzware seem to be the only ones who allow extensive automation through scripting with a number of workflow tools such as Enfocus Switch being able to send files through a selected set of ground controls to sort the good from the bad.
And what of the future? More and more companies now have to find was to automate their incoming pre-media files which now extend beyond those of just the graphic and design file formats and include formats such as HTML, Flash, Video and 3D. Our applications alone provide us with tools to test the files are fit for purpose, but don’t help us provide fully integrated workflow solutions.
Who will raise to the challenge? Or are the pre-media companies still going to have to create home cooked soup!
Author: Gary George