By: Erik Vlietinck
Sun, June 13, 2004 - 3:50:00

JDF (Job Definition Format) is a comprehensive XML-based file format/proposed industry standard for end-to-end job ticket specifications combined with a message description standard and message interchange protocol. JDF is designed to streamline information exchange between different applications and systems, intended to enable the entire industry, including media, design, graphic arts, on demand and e-commerce companies to implement and work with individual workflow solutions. JDF will allow integration of heterogeneous products from diverse vendors to seamless workflow solutions.

The basic Idea upon which JDF is based is "to develop an open, extensible, XML-based job ticket standard, as well as mechanism that provides new business opportunities for all individuals and companies involved in the process of creating, managing and producing published documents in the new economy". So it says on the CIP4 (International Cooperation for the Integration of Processes in Prepress, Press and Postpress) web site, and CIP4 is an international, world wide operating standards body located in Switzerland. The purpose of the association is to encourage computer based integration of all processes that have to be considered in the graphic arts industry, in particular the specification of standards, such as JDF. Building on existing technologies of CIP3's PPF and Adobe's PJTF, the Job Definition Format supplies a means for printing businesses to streamline the process of producing printed material.

Any number of articles exists on JDF because JDF is the door opener to the future. It is the key enabler of the Graphic Enterprise -- the new print communications paradigm where technologies converge to deliver a seamless flow of processing data. And technology providers want you to know that their systems, or software, or broadband technology is ready for the Graphic Enterprise.

The Graphic Enterprise is the culmination of the evolution of print - where technology takes its rightful place to create a continuous, uninterrupted flow of data that begins with project creation and ends with its delivery. That is not to say that technology will not continue to improve and advance, but not in such dramatic steps as this. The Graphic Enterprise represents a true paradigm shift -- made possible by JDF technology. And there is no escaping it. That is why your understanding of JDF and how it will change business is so important.

The drivers of the Graphic Enterprise extend beyond JDF technology. In other words, we are not going to change the way we work simply because we can. Economic and competitive pressures also generate the need. Consolidating printing companies, for example, need to merge technology. Clients need to get their projects to market faster, they want shorter runs more frequently, and they want to work with printing companies who can handle the entire project, which may include repurposing, personalisation and fulfilment.

The easiest way to picture the Graphic Enterprise is to imagine dropping a project file into a digital funnel at one end of the workflow then finding it bound and finished at the other end -- in a literature rack, at a trade show or in the client's hands.

Simply put, JDF is all about connectivity -- connecting competitive systems, departments, partners and clients -- all in one location or at multiple sites across a region or around the world.

It is important to note that in JDF terms, connectivity does not simply mean that systems are linked one to another, nor does it refer to the software drivers that send data to specific output systems. JDF connectivity means that all systems understand each other's instructions, exchange data and provide feedback. JDF gives the appearance that all your equipment and software was developed and built by a single source.

JDF enables printers to keep working with legacy products while still being able to enjoy the benefits of new equipment. For example, a new workflow automation system can still make use of an existing Screen CtP system. More importantly, having competing systems that communicate seamlessly, puts the operator in the driver’s seat. Now he can choose the system that best fits his needs without every having to worry if it will work within an existing workflow. And, if one printer’s systems could communicate with another printer’s, the two of them could partner as if they were one high-efficiency operation.

Why would departments have to connect? If prepress can tell press and postpress what to do automatically, then they don’t have to. And if all those tasks can be tracked, with information fed back to MIS, the administrator will know exactly how long it took to do what, and why. MIS will then be able to create accurate estimating models, so the printer won’t lose money anymore on guessed estimates. In addition, once sales or customer service representatives enter client and project data, it will never have to be entered again unless something changes. The customer profile, along with the client’s preferences will follow the project all the way to completion, so the original intent is never compromised and instructions will never fall through the cracks.

Going beyond supply chain management, printers have just the same need to connect with partners. Because if they could connect seamlessly with one another or with a finisher, they would never have to turn down a job that’s too big for their operation. Add to that the convenience for your client if the shipping company knew where a project had to go by when, the minute the data gets entered into the system.

Customer connect

Building strong customer relationships has never been more important, and JDF connectivity will give the power to service customers on a higher level. It will allow to initiate highly efficient online client collaboration. It will also allow printers to produce more than print a job. The entire project can be handled from start to delivery.

There is one catch. For all of these people and systems to connect with each other they have to speak a common language -- JDF -- and understand how to implement the instructions they are given.

JDF is an XML specification. So to understand JDF, you need to understand XML. A markup is a tag or a code that identifies information. In print production, tags such as approval and trapping attached to a page would provide instructions for trapping and tell you that the page needs to be approved before final processing. It could even have instructions where or to whom to send for approval. In this way, when the page is ready it can be sent automatically to the client for approval.

You can add as many tags as you like. In addition, you can supplement them with other files to further define and extend the instructions. This is why you can apply content to a template for a webpage and for print. Both will look different but the elements of the content will go into their proper place. XML understands the difference between text and graphics and treats them accordingly. But in order for competing systems to "interoperate", they must use the same tags -- speak a universal language, if you will. This is what JDF does. It provides standard tags so that all systems and MIS functions speak print fluently. JDF is then written into workflow software, project management systems and other system drivers.

To make tags interoperate, CIP4 groups more than 180 members in 20 working groups. Its primary goal is to develop vendor-independent international standards to extend connectivity beyond production to include business processes, client collaboration and job delivery. To make JDF a truly vendor-neutral data exchange standard it is necessary to work out specific Interoperability Conformance Specification (ICS) and perform Interoperability Testing -- so that all systems use the same definition format.

JDF goes beyond XML in that it includes validation schema. This enables and automates processes such as preflighting. It also allows for a selection of a networking protocol and methods of exchange. It automates online transactions and data exchange.

All told, JDF is the key technology driver of the evolved workflow - the Graphic Enterprise.