Post on 13-Feb-2016
description
transcript
JDF
Ove
rvie
w 1
1-Ju
n-03
Dr.
Rai
ner P
rosi
(C) H
eide
lber
ger D
ruck
mas
chin
en A
G JDF- Experience and Challenge
Dr. Rainer ProsiCTO, CIP4Senior Software Architect, Heidelberg
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
JDF on One Slide
• JDF is a Graphic Arts Job Ticket Data 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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JD F N ode O utput (resources)
T im e
Start End
scheduling :
Inpu t (resources)
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
CoverEnd
Sheets
ReaderPages
Book
Contents
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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 1 Child Node 2
Resource 1
Link
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
ConventionalPrinting JDF Node Example
ConventionalPrinting
ExposedMedia(Plate)
Media
Ink
ResourceLinks
Component(including amount)
InkZoneProfile
ParametersLayout
(Control Marks)
NodeInfo•Planned StartTime•Planned EndTime
AuditPoolActual Resource UsageActual Time Summary
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Node Executability Resource ResourceLink JDF Node
Not Executable
Not Available
Available
Available
ResourceLinks
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Node Executability Resource ResourceLink JDF Node
Executable
Available
Available
Available
ResourceLinks
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Node Executability and Networks
Not Available
Available
Available
Not Executable
Links
Waiting
Links
Available
Available
Not Available
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Node Executability and Networks
Not Available
Available
Available
Not Executable
Links
Running
Links
Available
Available
Available
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Node Executability and Networks
Available
Available
Available
Executable
Links
Completed
Links
Available
Available
Available
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Interface Areas in JDF - JDF 1.2 enhancements
Customer Print (Graphic Arts) Shop MIS Production Prepress Press Postpress
Interoperability Conformance Specification definitions
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
Postpress
• Additional Postpress processes added:• Bundling• PrintRoll
• Detailed Waste Definitions• WhiteWaste, ObliqueSheets, Process Specific
• Complex Feeder Definitions
Combined NodeInputComponent
1
Compose output component by taking:
2 items from Input Component 12 items from Input Component 21 items from Input Component 1
InputComponent
2
OutputComponentFeeding Other
Process
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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 (PrinterPaper 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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
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
JDF
Ove
rvie
w 0
11M
ar-0
1 D
r. R
aine
r Pro
si
(C
) Hei
delb
erge
r Dru
ckm
asch
inen
AG
JDF- Experience and Challenge•
Thank you very much for your attention!