ProQuest Text Only Interface Return to RIT Wallace Library  |  Live Chat with RIT Librarian  |  Help  
Basic Search Advanced Search Topic Guide Publication Search
: 0 documents
Interface language:

Databases selected:  Multiple databases... New scholarly features & content!

Document View « Back to Marked List  Document   1 Publisher Information  
Print     Email Mark Document Abstract AbstractFull Text Full Text

Everything you ever wanted to know about JDF...
Barney CoxPrintweekLondon: Feb 19, 2004. pg. 22, 2 pgs
 »Jump to full text  Full text
 » Translate document into: Spanish Portuguese
Subjects:
Classification Codes8690 Publishing industry,  8670 Machinery industry,  5240 Software & systems,  9175 Western Europe
Locations:United Kingdom,  UK
Author(s):Barney Cox
Document types:Feature
Publication title:Printweek. London: Feb 19, 2004.  pg. 22, 2 pgs
Source type:Periodical
ProQuest document ID:573256571
Text Word Count1801
Document URL:http://proquest.umi.com/pqdweb?did=573256571&Fmt=3&clientId=3589&RQT=309&VName=PQD
 More Like This  »Show Options for finding similar documents

Abstract (Document Summary)

Despite the potential offered by JDF to automate and integrate production there is cynicism in the market. One of the biggest criticisms levelled at JDF is that not all equipment will be JDF-enabled for years, or for some finishing kit possibly decades. But that maybe missing the point. Just because some bits of equipment in one part of the factory can't be directly linked by JDF doesn't mean there aren't benefits to be had from using it in parts where it can help improve overall efficiency....

Full Text (1801   words)
Copyright Haymarket Business Publications Ltd. Feb 19, 2004
[Headnote]
... but were afraid to ask. Barney Cox reveals how this year's principal Drupa theme is set to transform print production

"It's going to save you money" is the blunt answer to why you should care about JDF from Martin Bailey, chief executive of CIP4, the organisation responsible for looking after the three little letters that will be causing the biggest fuss at Drupa.

Those three letters have been adopted by the industry as a mantra for this year's show, which has even been officially called "the JDF Drupa". JDF is a handle to peg the big themes that are emerging onto. A few years back PDF was the big thing and in both cases the file formats are something easy to grab onto, but the underlying issue is workflow. PDF was all about more efficient and automated pre-press workflow. JDF expands that beyond pre-press to cover all production, and even further to cover the business aspects too.

Workflow has come to be a shorthand term for the pre-press workflow, as this has, up to now, been the area where the arrival of digital data has had the biggest impact and has led to automation or elimination of many manual tasks and processes.

The big picture

The term workflow is now being extended to cover the entire process from the moment a customer asks for a quote or places an order to its delivery and invoicing. It makes sense to consider the process in its entirety rather than as separate islands, but that needs a universal means of communicating across the factory floor and into the offices upstairs, which is where JDF comes in.

A JDF file is the digital equivalent of a job bag. It contains all the information needed for a job to be produced, and can have notes and instructions added to it, either by operators or automatically by the equipment used at each stage. Being digital it has a huge advantage over a physical job bag in that at any point anyone who needs to access the details, and amend them, can.

Before JDF came along there were attempts to come up with job tickets and electronic job bags, such as Adobe's Portable Job Ticket Format (PJTF), a sister to PDF for pre-press job instructions, and the Print Production Format (PPF) for taking information from pre-press into the press room and bindery. PPF was a success and is widely used for press presetting, but all these formats confined themselves to production.

Streamlining production only goes so far in improving the efficiency of a business and cutting costs, there is also the need for management to monitor production to make sure it is operating efficiently and that costs are accurately allocated and to keep customers informed of the status of the job.

It was these requirements that led to the development of JDF to provide a single store for all the details that make up a job. In effect it is to ensure that everyone is singing off the same hymn sheet, cutting the duplication of tasks and the need to re-enter information relating to the job in each department.

A common file with all the details of a job should allow the Customer Service Rep (CSR) to see where a job is and tell the client or, if the system allows it, allow the customer to check the status themselves. The financial director can look at the quote and the production costs to make sure the job is profitable and the production director should be able to see all stages of production and to react or even pre-empt potential problems.

A big question hanging over their adoption is where in the process and what will control and manage the JDF files?

"People consider the controller to be an MIS, but it's more likely to be a prepress workflow management system," says Bailey. "Much has been written about how JDF only works with MIS, but only 20-30% of firms can afford MIS. For small sites imposition software is used as control station for workflow. The guy controlling the imposition controls the workflow. This small and simple workflow is popular and very widespread. Today it relies on process control information being sent using PostScript. That's not so with PDF, so this workflow has not moved to PDF - JDF enables that to happen."

Drupa will be a chance to see how JDF can be used in different workflows - it's early days yet - but there are signs that there will be a range of options for how JDF is used and many will fit in with existing equipment and methods, if required. For users JDF should be transparent. Worrying about XML syntax or the JDF schema or any other jargon shouldn't bother anyone involved, all they should see is more automation, better visibility of what stage a job is at and hopefully a more healthy bottom line.

Time constraints

Despite the potential offered by JDF to automate and integrate production there is cynicism in the market. One of the biggest criticisms levelled at JDF is that not all equipment will be JDF-enabled for years, or for some finishing kit possibly decades. But that maybe missing the point. Just because some bits of equipment in one part of the factory can't be directly linked by JDF doesn't mean there aren't benefits to be had from using it in parts where it can help improve overall efficiency. Rejecting JDF out of hand because it won't work with everything is throwing the baby out with the bathwater.

Even if you can't network a particular piece of kit that doesn't mean there aren't ways around that. "If it is relevant you can put consoles next to equipment that is not JDF enabled," says Bailey. It may not be quite so elegant as the totally automated factory where data flows seamlessly from process to process, but a PC in the bindery providing details on the jobs coming in and taking information on jobs running through is huge benefit.

One of the most encouraging things about JDF is that it will make its biggest impact where it is implemented first and most rapidly - in pre-press and MIS. Both of these processes are reliant on software, which can be easily updated to handle JDF. You may find that your equipment is JDF-enabled by default with the next software update. As jobs become more complicated and runs get shorter, prepress and administration account for an increasing proportion of a jobs costs. So the savings achieved make a bigger contribution to the bottom line.

If you remain unconvinced then Drupa will provide a golden opportunity to see JDF in action both in dedicated areas and on the showfloor. CIP4 and Drupa organiser Messe Dusseldorf will co-organise a series of events. There will be five different events and activities dedicated to promoting the application of JDF at the show.

A "Compass Session" will provide an insight into the applications of JDF; presentations in the Innovation Arena will highlight where to find JDF on the show floor; a JDF cafe will provide demonstrations and a chance to meet with representatives from CIP4. And of course firms will be showing their own products, whether it is the one-stop shop approach of Heidelberg under the Prinect banner in halls one and two or the multi-vendor workflows shown by NGP members and in PrintCity.

"My only message to cynics is to come and see it at Drupa," says Bailey. "They will be flabbergasted by the number of JDF products."

[Sidebar]
History of JDF
At Drupa 1995 the Print Production Format (PPF), the first attempt at a standardised way of communicating digital data between different parts of the print production process, was launched. Spearheading the development of PPF was Heidelberg, which founded the initiative at the start of 1995 in co-operation with German organisation the Fraunhofer Institute for Computer Graphics.
PPF was always intended to be an industry standard and to support its development independent of any one manufacturer the CIP3 (International Cooperation for integration in Pre-press, Press and Post-press) was formed with its membership made up of interested firms across the supplier sector.
The remit of PPF was production. It started with pre-press data and could pass details from pre-press to the press such as ink-duct presetting, register control and colour specification, and to finishing including folding, collecting, inserting and binding.
As the industry got swept up in dotcom mania, one of the benefits to emerge of the e-commerce rush was the understanding that business and management information needed to be integrated with production information. In February 2000 Adobe, Agfa, Heidelberg and MAN Roland announced at Seybold that they were working jointly on the development of the next generation of jobtickets-JDF. Describing the reason for JDF at the launch, Agfa marketing manager image processing Systems John Harrison said: "PDF and PJTF provide a foundation while CIP3 handles technical workflow. They do not cover business and management relevant information."
The four firms pledged to complete the specification in time for Drupa 2000 and then to pass the project to a standards body. On 14 July 2000 JDF was handed to CIP3, which by adding Processes to its title became CIP4.
The first version of JDF was released in April 2001 and version 1.2 is expected next month. At Drupa products will be JDF-enabled and there will be many opportunities to see workflows making use of JDF to transfer data through the print process.
Jargon buster
JDF Job Definition Format: the file that holds the management and production details of a job
JMF Job Messaging Format: the little brother of JDF, created by equipment to provide feedback on its status or on an operation carried out on a job to the central controller and repository of the JDF
JDF XML eXtensible Mark Up Language: A language that allows communication between different computer platforms and software. It is the underlying language of JDF and is used in many other industries too, making translation of instructions and information between businesses automatic
CIP3 International Co-operation for integration in Pre-press, Press and Post-press: Independent body that was set up to control PPF development
CIP4 International Co-operation for integration of Processes in Pre-press, Press and Post-press: Oversees the development of JDF. Made up of interested equipment vendors, businesses and trade bodies, it's what the CIP3 became when it took on JDF from the original developers in 2000
PPF Print Production Format: Original file for automatic transfer of job info from pre-press to press and finishing, most commonly ink key pre-setting from ripped data, often referred to as CIP3 data
NGP Networked Graphic Production: An initiative set up by Creo to speed up the development and adoption of integrated workflows. Its 34 members include Adobe, KBA, Muller Martini, Shuttleworth and Xerox


^ Back to Top « Back to Marked List  Document   1 Publisher Information  
Print     Email Mark Document Abstract AbstractFull Text Full Text
Copyright © 2005 ProQuest Information and Learning Company. All rights reserved. Terms and Conditions
Text-only interface

From ProQuest Company Access provided by RIT Library