Inside JDF Experience and Challenge Dr. Rainer Prosi CTO, CIP4 Senior Software Architect, Heidelberg

Outline Architectural Overview of JDF Experience with JDF 1.1 Outline of JDF 1.2 Activities  Areas of activity (Who and What)  Cooperation with other standards  Timeline for JDF 1.2  JDF Interoperability Status

JDF on One Slide JDF is a Graphic Arts Job Ticket Data Interchange Format Specification - JDF is not an Application or System JDF is encoded in XML Content is referenced, not embedded JDF is extensible JDF is based on semantic structures defined by: Adobe PJTF CIP3 PPF JDF Job Definition + JMF Messaging define the JDF Framework

The Building Blocks of the JDF Framework JDF Node Description of a Process, Process Group or Product JDF Resource Description of a parameter set or physical entity JDF ResourceLink Link between JDF Nodes (processes) and Resources JDF Capabilities Descriptions Limitation of a JDF interface JMF Messages Real time data interchange format

The JDF Node Description of a generic Process The “Verb” in JDF Do something at a given time Structured container for Scheduling and Auditing One JDF node type for Products and Processes Less Precise Product Intent at the Job Root Node Workflow Group nodes “ProcessGroup” in between Detailed individual or combined Processes in the Leaf Nodes

Product Intent vs. Process Modeling Goal of Product Intent Description Customers view of the “thing” that he wants to have manufactured Contract Negotiation Process Independent Goal of Process Modeling Interface between production and management information systems Process interdependencies Manufacturing Instruction Details Cover End Sheets Reader Pages Book Contents

JDF Resources Specification of Parameters of Product Intent description Logical Entities, e.g RIP Parameters, Imposition setup Physical Entities, e.g. Media, Devices, Plates Based on Adobe PJTF and CIP3 PPF Intent Resources for product intent nodes Prepress : Adobe PJTF Press, Finishing: CIP3 PPF Internal to JDF or External Links to well-defined Formats Thumbnails Preview Files ICC Profiles Content Data

ResourceLink Bind a Resource to a Node Define Resource Usage (input or output) Link to a Subset / Part of a Resource E.g. Cyan Plate of the Front of Sheet #1 Define the Amount Allow reuse of Resources by multiple processes One resource may be linked by multiple ResourceLinks Defines a process network Parent Node Child Node 1Child Node 2 Resource 1 Link

ConventionalPrinting JDF Node Example ConventionalPrinting ExposedMedia (Plate) Media Ink Resource Links Component (including amount) InkZoneProfile Parameters Layout (Control Marks) NodeInfo Planned StartTime Planned EndTime AuditPool Actual Resource Usage Actual Time Summary

Node Executability Not Executable Not Available Resource Links Resource ResourceLink JDF Node

Node Executability Executable Available Resource Links Resource ResourceLink JDF Node

Node Executability and Networks Not Available Not Executable Waiting Links Available Not Available Links

Node Executability and Networks Not Available Not Executable Running Links Available Links

Node Executability and Networks Available Executable Links Completed Links Available

Capabilities Descriptions Mapping from Product Intent to Process Networks Set up Communication between Controllers and Devices Define User Interface Constraints Allow planning systems to automatically schedule jobs to the optimal available device. Enable load balancing between devices. JMF messages for Capabilities Integration (Plug&Play)

Messaging with JMF Small XML Structures Synchronized with JDF Used for: Plug + Play Bootstrapping Snapshots of Job / Device Status Dynamic Job update Queue Support Capabilities interchange

Experience with JDF 1999: Adobe, Agfa, MAN and Heidelberg form the GAT initiative with the goal of defining a job ticket for the Graphic Arts that also integrates MIS. 2000: The CIP3 Consortium takes ownership of the standard. 2001: JDF 1.0 is released. 2002: JDF 1.1 is released. Ambiguities/Bugs found in implementation were removed Additional Processes were added Consistency between diverse areas was enhanced

Experience with JDF - Advantages JSingle grammar for specifying job data in the graphic arts industry JIntegration of Production, Customer and MIS JDefinition of production networks JCombined Processes JDefined communication protocol, not only data structures JExtensible Model JInteraction with other Standards in GA

Experience with JDF - Challenges / Obstacles KNumber of processes in the graphic arts LCreative JPrepress JPress JFinishing LFulfillment LComplexity of the standard LSize of the Specification LMoving from the Abstract Idea to a Concrete Implementation LFlexibility of the Specification LUnclear Role of Production networks in Interfacing Lprivate extensions LDefinition of abstract coordinate systems KLegacy System Longevity

JDF 1.2 enhancements  Backwards Compatible Extensions of JDF 1.1a  Customer  Print (Graphic Arts) Shop  MIS  Production  Prepress  Press  Postpress  Communication / JMF Messaging  Capabilities  Interoperability Conformance Specification definitions

Customer  Print (Graphic Arts) Shop  Product Intent Definition  Minor Cleanup / Clarifications  Add a “generalized” CustomerMessage element  Add Channel definitions for  Instant Messaging  SMS  Add extensible reason and message content definitions

MIS  Production  Definition of the MIS  Imposition interface  MIS consumes product intent  Imposition Software outputs flattened page positions  Missing Interface from MIS to Imposition Software Support of multiple customer jobs on a sheet

Prepress  Preflight  Define extensible JDF definition of  Preflight Profiles  Preflight Reports  Asset Transfer  Define a Process for Digital Artwork Delivery  Proofing  Define an integrated combined proofing process

Press  Digital Printing Interoperability Conformance Specifications  3 Levels of ICS  Desktop Printers  Department Printers  Graphic Arts Digital Presses  Conventional Printing  Additional Previews for Quality Control

Postpress  Additional Postpress processes added:  Bundling  PrintRoll  Detailed Waste Definitions  WhiteWaste, ObliqueSheets, Process Specific  Complex Feeder Definitions

JMF Messaging  Added Additional Device  MIS messages  Enhanced Ability to dynamically request input resources (Replace a plate that’s broken…)  Added JMF File Protocol for exchange between very dumb devices/controllers  Clarify JDF/JMF Transport and Packaging

Capabilities  Add Abstract User Interface Definitions  Add Localization  Add Constraints definitions  Full Boolean logic for device constraints

Interoperability Conformance Specifications Define a set of Interoperability Conformance Specifications – ICS The term “JDF Compliant” does not immediately imply that two arbitrary applications will communicate. Sending RIP instructions to a Folding Machine is not useful… Two applications that comply with a given ICS will communicate in a meaningful way. CIP4 Working groups are defining various ICS documents. Base ICS for various communication levels Domain ICS for well defined interfaces

Standards Bodies that Cooperate with CIP4 CIP4 Appointed Members extract CGATS: Graphic arts standards DDAP: Advertising Workflow E.R.A: European Rotogravure Association Euprima: European MIS vendors consortium GATF: Graphic Arts Technical Foundation ICC: Color workflow IFRA IFRATrack: Messaging for Newspaper production IDEAlliance Papinet: Paper Procurement (Printer  Paper Vendor) Additional IDEAlliance Standards interfaces are under investigation. NPES: Industry Association PODI: Variable Data Content Layout Definition PrintTalk: Internet Print Procurement TAGA: Technical Association of the Graphic Arts UP3I: Inline Real Time Finishing and Paper Handling Full list at:

Preliminary JDF 1.2 Time Line Consolidation of miscellaneous Changes Definition + Discussion 11/03 Tech Writing : Q4/03 Integration of Preflight Q4/03 Internal CIP4 publication 3 Month intellectual property due diligence period Official Publication Date ~ Q1/04

Interoperability Event Status CIP4 hosted Interoperability test events in May and September 2003 Previous One was last week in Darmstadt, Germany Goals were: Integration of products from various vendors Pinpoint ambiguous areas in the specification Engineering team building May: 9 Companies with 16 Products (including Prototypes) September: 18 Companies with 23 Products 2 Further events are scheduled this and early next year Events are closed door Goal is to enhance the standard and enable interoperability NOT to find scapegoats / heroes Avoid multiple, incompatible JDF Dialects

JDF- Experience and Challenge Thank you very much for your attention!