JDF- Experience and Challenge

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

2. 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

3. JDF on One Slide • JDF is a Graphic Arts Job TicketData Interchange Format Specification- JDF is not an Application or System • Encoded in XML • Extensible • Based on semantic structures defined by: • Adobe PJTF • CIP3 PPF • JDF Job Definition + JMF Messaging define the JDF Framework

4. 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

5. 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

6. Book Contents Cover Reader Pages End Sheets 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

7. 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

8. Parent Node Resource 1 Child Node 1 Child Node 2 Link 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

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

10. Node ExecutabilityResource ResourceLink JDF Node Not Available Not Executable Available Resource Links Available

11. Node ExecutabilityResource ResourceLink JDF Node Available Executable Available Resource Links Available

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

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

14. Node Executability and Networks Completed Available Available Links Executable Available Links Available Available Available

15. 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

16. 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

17. 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

18. Experience with JDF - Advantages • Single grammar for specifying job data in the graphic arts industry • Integration of Production, Customer and MIS • Definition of production networks • Integration of Customer Intent and Production • Extensible Model

19. Experience with JDF - Challenges / Obstacles • Number of processes in the graphic arts • Creative • Prepress • Press • Finishing • Fulfillment • Complexity of the standard • Size of the Specification • Moving from the Abstract Idea to a Concrete Implementation • Unclear Role of Production networks in Interfacing • private extensions • Legacy System Longevity

20. Interface Areas in JDF - JDF 1.2 enhancements • Customer  Print (Graphic Arts) Shop • MIS  Production • Prepress • Press • Postpress • Interoperability Conformance Specification definitions

21. 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

22. 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 • Enhancements of Capabilities • UI Definitions • Constraints definitions • JMF Enhancements • Added Additional Device  MIS messages • Added JMF File Protocol for exchange between very dumb devices/controllers

23. 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

24. Press • Digital Printing Interface Conformance Specifications • 3 Levels of ICS • Desktop Printers • Department Printers • Graphic Arts Digital Presses • Conventional Printing • Additional Previews for Quality Control

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

26. 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: http://www.cip4.org/members/members_e.php

27. Preliminary JDF 1.2 Time Line • Consolidation of miscellaneous Changes • Definition + Discussion 06/03 • Tech Writing : Q3/03 • Integration of Preflight Q3/03 • Internal CIP4 publication • 3 Month intellectual property due diligence period • Official Publication Date

28. Interoperability Status • CIP4 hosted an Interoperability test event in May • Goals were: • Proof of concept of the event • Integration of products from various vendors • Pinpoint ambiguous areas • Engineering team building • 3 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 / heros

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