PDF workflow system

Not long ago, several vendors launched the PDF file format to deliver highly flexible and effective workflow tools. Most PDF workflow tools today automate the printing production process from input to output. They provide the flexibility to generate multiple workflows. They tightly rationalize the process through Portable Job Ticket Format (PJTF), which can integrate with the business system to change job status and begin billing.
The PDF file format offers important benefits for the printing industry, including page independence and device independence. Page independence means that all PDF pages contain all the information needed for their print copy, and all pages can be operated separately. Device independence means that PDF files can be output on any Postscript device. In addition, by incorporating job ticket information into the PDF file format, the operator can view the job information and the job itself.
However, in order to get the benefits of these tools, a greater investment in equipment and infrastructure is required. In addition, for many print shops, PDF workflow tools introduce new process protocols, and cultural changes may just as well (if not more) be as expensive as equipment. It is very clear that these systems require a lot of upfront planning. The first step is to evaluate the architecture and components of your system to determine if the PDF workflow is right for you. If appropriate, the next step is to carefully study the existing production process and find the best PDF workflow tools that can be combined with your production environment.
This article outlines the basic architecture of the PDF workflow and existing PDF workflow tools, and then reviews the products of Agfa, HeiDlberg/Creo, Scitex and Screen.
PDF workflow basics
The goal of the PDF workflow system is to deliver electronic documents to film or plate recording devices, or to digital printers or printers with little operator intervention. At the same time, these tools are designed to be flexible enough to facilitate changes or revisions to documents without having to restart them. There are 5 basic steps generally handled by PDF workflows:
PDF normalization
Once the PDF workflow system receives input (most tools receive a variety of formats), the first step is to normalize the input. AdobeNormalizer is the standard across all existing PDF workflow tools. It converts input files to PDF and provides basic preflighting capabilities. Most systems contain additional preflighting functionality to check for missing components, qualify font size, or control the use of color. In addition, most tools can also allow printers and publishers to configure settings to meet their production requirements.
Pre-check
Additional software is often used to check file errors, job settings, and file details that are ignored during the normalization process.
Make up white
Makeup can be done automatically with standard settings, or follow complex rules based on image categories and colors. Adobe provides a Job Ticket Processor (JTP) for Filled White, and each PDF workflow tool vendor provides alternative methods.
Group Edition
Page independence in PDF format allows pages to be reclassified in the middle of the assembly process to meet production requirements. Adobe provides JTP for group editions, and there are many other third-party tools that support group editions via PJTF (portable job ticket format).
Raster image processing
In this step, the files are converted from object-oriented code and mesh line images to mathematically positioned points (bitmaps) that are to be imaged on film or plates, when digital printers or printers are used It is directly imaged on paper. Since the raster image processing sets the resolution, this step is usually performed after specifying a file for a specific output device.
Of course, depending on the requirements of a job, each workflow is different. The PDF workflow tools of Agfa, HeiDelberg/Creo, Scitex, and Screen support basic steps, including options for image replacement, color correction, screening, and proofing. They provide standard and specific solutions for processing job tickets, or provide interfaces for establishing workflows.
The most basic architecture In general, today's PDF workflow solutions that appear on the market, the most basic body structure is a two-tier client/server or three-tier thin client system, the client/server system is the most suitable for such a production environment. That is, everyone in the workflow is in the same position and on the same network.
With the support of distributed functions such as remote soft proofing and Web-based authentication, the thin client system is suitable for a decentralized environment. Many of today's thin client systems even allow several individuals to access workflows via the Internet.
Behind these conditions, each workflow system should have a stable and reliable database. Relational databases are the key to processing hundreds of different types of job-printing production every week. Popular database systems (such as Oracle8i and Microsoft SQL) provide various options for reporting and management tools, and are easily integrated with business systems. The detectability of the workflow is related to its architecture. Even small print jobs require systems that can dispatch different workflow steps across different servers, so that complex refill jobs are not required to block other jobs. In addition, this system should be able to balance load tasks and power up two or more processors to complete a single task.
Apogee
Apogee, published by Agfa in 1997, is a basic client/server system running on Windows NT. The A-pogee workflow system includes a PDF Pilot that normalizes PS and PDF files, a PDFRIP that processes job tickets that are determined by the user, and an Apogee Print Drive that passes RIP-processed files to output devices. The system is subject to Adobe PJTF for job information, and it supports all prepress steps including Image Replacement (OPI). Advanced Apogee OPI processing prior to normalization with PDF Pilot followed by generation of PDF files with embedded high-resolution images. Apogee also includes preflight software from Enfocus. Now, Apogee Priat Drive can only drive a high-end output device and a printer. Agfa plans to drive multiple devices in the future. The system does not have a relational database, which limits its ability to integrate with business systems. For example, job tracking and reporting is handled through a text-based record file, which must be edited to provide a specific report. Future support for XML-based job ticket formats will enable data exchange between Apogee and business systems.
Prinergy
In August 1999, HeiDelberg and Creo jointly released its PDF workflow tool: Prinergy. As an enhanced Windows NT-based client/server system, Prinergy provides a Java-based client interface that is accessible from Windows and Macintosh workstations.
On the server side, Prinergy has two components: Prinergy Refiner and Prinergy RenDerer. Prinergy Refiner standardizes incoming documents, conducts preflight checks, and performs color correction and dew-whitening according to the selected workflow. This process is determined by combining job ticket processors into the Prinergy Process plan. The system directly accepts PS, PDF, copy points and compressed PS files. Through integration with the CEPS link, Priner-gy also accepts TIFF/IT and CT/LW files.
Once the file is processed, PDF pages can be created and sent to Prinergy RenDerer for output to digital proofers or other high-resolution devices. The architecture of the server is hierarchically configurable. Multiple Refiner and Renderer servers can be configured to support job allocation and load balancing.
Prinergy uses Oracle Database to track job information throughout the entire workflow. Relational database systems are responsible for error correction in workflow processing. It can also integrate with third-party reporting and billing systems to support business processing.
BrisqueExtreme
In September 1999, Scitex announced its PDF workflow tool: Brisque Extreme. This workflow solution is a fixed client/server system that supports Windows and Macintosh customers. The system normalizes PS and PDF files, and allows the added Scitex file format and bitmap format to enter the workflow without formalization. ScitexJobTicket is a user-defined workflow template that is set up and saved with graphical interfaces, allowing users to select and sort tasks.
Brisque Extreme integrates many features from other Scitex workflow systems and third-party tools such as Enfocus's pre-check software. The Scitex PDF 2GO module generates a PDF file for observation and commentary output from the RIP. The Impo2GO module generates fully-spun PDF files for viewing and printing. Even after the file is processed by raster images, both of these modules create the conditions for flexibility in workflow processing. The system can output to all Scitex devices, as well as proofers or large format printers.
Brisque Extreme does not have an internal database, but it uses the Im-formix database in conjunction with the Scitex Timna production management system. Timna runs on his own Scitex server. The Brisque Extreme supports up to four processors in the server, which can use these servers to rasterize image processing in parallel for four jobs, or to parallel raster image processing jobs in a single page within one. However, the system cannot balance load across multiple servers.
Trueflow Pro
Screen Company announced its product Ture-flowPro in January 2000. The new product is a Windows NT-based system that can receive files from Windows and Macintosh workstations and Java-capable browser-based clients. The system now receives PS and PDF files. The template is used to maintain the settings of the task and then integrated to create a PJTF job ticket.
Based on the settings in the job ticket, the TrueflowPro system moves the files through preflight, make-up, composition, and proofing steps. The Tra-p editor and the Flat worker are optional tools that are used to edit make up and group multiple jobs onto a single layout. The raster image-processed files can be exchanged using Screen's Taiga Space workflow system. Taiga Space is Screen's high-end production workflow system that runs on a single or multiple processor Sun Unix system.
Trueflow Pro supports servers with more than four processors that can produce output on film or image-based imagesetters. The system lacks the database and storage capabilities of the Taiga SPACE system, but this function will be available in the future.
Consider the future
Although some printing companies have now implemented the PDF workflow system and made it part of the business activities, most print providers are still experimenting with this technology. And there are many reasons: There are many differences between the available tools, there are many limitations in terms of flexibility and scalability, and there are still many places that need to be redeveloped. Now, each PDF workflow system implements PJTF and Adobe JTP differently, which makes it difficult for printers to exchange or integrate most components from different systems.
Recently, Agfa, Adobe, Heidelberg and Creo, and MAN Roland have collaborated to establish an XML-based job specification standard, Job Definition Format JDF. The goal of creating a JDF is to develop a format in which linkable content can be generated until the postpress process can be measured. XML-based job tickets provide easier communication across production systems and production and business systems. Although there is currently no standard to support such job subpoenas, we expect it to emerge as a standard the next year. In short, when the system adopts standards and becomes more measurable and flexible, it is expected that the status of approved PDF workflow tools will improve.