Espoo, Parikshit Kulkarni F

Transcription

1 HELSINKI UNIVERSITY OF TECHNOLOGY Laboratory of Media Technology Department of Forest products technology Exploiting JDF between customer and print-shop Espoo, Parikshit Kulkarni F i

2 TABLE OF CONTENTS 1 INTRODUCTION BACKGROUND OBJECTIVE E-JOB DELIVERY FORMATS CIM IN PRINTING INDUSTRY PUBLICATION OF E-JOB TICKETS CIP3 / PPF Adobe PJTF PrintTalk IfraTrack AdsML CIP4/ JDF JDF Vs PPF Vs PJTF XML XML DOCUMENT STRUCTURE DOCUMENT TYPE DECLARATION XML NAMESPACES XML SCHEMA XPATH CONTENT VS METADATA JDF BASICS FOUR C S OF JDF JDF WORKFLOW MIS JMF/ Job Messaging Format JDF ARCHITECTURE JDF SYSTEM COMPONENTS Common JDF Node Types NETWORK IN JDF JDF NODE ELEMENT JDF node attributes and sub-elements AncestorPool element CustomerInfo element NodeInfo element StatusPool element Resource Element ResourceLink element AuditPool element JDF Extensibility element ii

3 JDF versioning element ICS NETWORKING IN PRINT PRODUCTION CUSTOMER INTEGRATION PROCESS MODELING UML Flowcharts Simulation Activity based costing Petri Net IDEF MODELING OF INTEGRATION OF CUSTOMER IN PRINT PRODUCTION INTEGRATED JDF MIS SYSTEMS PRESENT STATUS OF JDF STANDARD STATUS OF JDF ENABLED SYSTEMS SURVEY OF PRINTING COMPANIES BACKGROUND INFORMATION OF COMPANIES Channel to get RFQ Channel to get proof approval information Channel to delivery instructions Channel to get Customer feedback KEY FINDINGS FROM THE SURVEY CUSTOMER AND PRINTSHOP COMMUNICATION PROBLEMS TESTING OF JDF FILES ECONOMY OF JDF IN CUSTOMER INTEGRATION CONVENTIONAL PROCESS VS JDF BASED PROCESS Data inputs prior JDF implementation COST BENEFIT Cost benefit in terms of time RETURN ON INVESTMENT STEP BY STEP JDF IMPLEMENTATION HOW TO PROCEED FOR INTEGRATION CONCLUSION REFERENCES iii

4 HELSINKI UNIVERSITY OF TECHNOLOGY ABSTRACT OF THE MASTER S THESIS Author, student number, topic and credits Parikshit Kulkarni, 59057F. Exploiting JDF between Customer and Printshop (20 cr) Date: 09/06/2006 Number of pages: 91 Department, professorship Department of Forest Products Technology Course AS-75 Graphic Arts Technology Laboratory of Media Technology Instructor Senior research scientist Olli Kuusisto Supervisor Professor. Dr. Pirkko Oittinen JDF- Job Definition Format is designed to exchange information between different applications, devices and systems along the entire supply chain in graphic arts industry. Job definition format is encoded in XML (Extensible Markup Language). JDF is comprehensive. JDF have good connectivity, communication and better control over all area of JDF workflow. JDF, a job ticket is flexible and has ability to carry print job from genesis through completion. JDF has ability to communicate all devices through MIS (Management Information System). JDF can track job status and device status with the help of JMF (Job messaging Format). With ICS (Interoperability Conformance Specification), JDF can integrate with different JDF enabled products from different vendors to create seamless workflow solutions. The objective of this thesis was to exploit possibility of implementing JDF between customer and printshop, finding deficiencies in current format in the area between customer and printshop and cost benefit analysis in the implementation of JDF. Study shows that there is no system available exclusively made for the integration between customer and printshop. Printer and customer have to make customized systems according to their requirements. Time consuming processes are accelerated and production cost is saved per job in terms of time. If customer wants to know status of job, it depends on if printer has already installed JDF in production processes or if printer gives access of system to customer inside the production department. JDF is still an evolving standard. Many printers are implementing JDF enabled systems in their printshops mainly in production processes. JDF is a promising future change for graphic arts industry. In coming years many printers will fully implement JDF network in the printshops. Keywords- Automation in printing industry, JDF, XML in printing, Process modeling, ROI in JDF 1

5 1 INTRODUCTION 1.1 Background In recent years print processes became fully digitized with the use of computer. With fierce competition and low margins, customer expects high quality and prompt delivery. Lowering production cost and management cost with increase in the quality, integration of processes, color management are some of the challenges faced by printers today. In order to cope with this situation the whole supply chain in print production need to be restructured with the use of computer. JDF Job Definition Format gives answer to all of these questions. Process automation is facilitated by JDF. JDF is open, vendor independent, graphic arts job ticket data interchange format specification. Job definition format gives fully integrated workflow solution along entire logistics chain in print production. 1.2 Objective The objective of the thesis is to find out present status of JDF and how it can be applied in commercial printing between customer and print shop. On the basis of this study, JDFcode will be created and pilot evaluation will be carried out with the CheckJDF Server of CIP4. Along with this, estimation of investment costs and potential benefits will be carried out. Work is limited to commercial printing, specifically magazines and advertising matter. Customer Print Buyer Negotiation & Quote Sales Rep Customer Service Rep Product Description Production Production Scheduling Scheduling Limited Process Limited Process Prepress Manager(s) Prepress Operator Prepress Prepress Create Create JDF JDF Intent Intent Create Document Creative Professional Job Creation Product Description (with ranges) Product Description (Actual values) Estimating Estimating & & Limited Order Order Entry Entry Process Base MIS MIS Extended Print Shop Manager Print Shop Management Press Press Manager(s) Press Operator Postpress Manager(s) Postpress Operator Press Press Press Postpress Postpress Customer Facility Print Shop Figure 1. The reference model of JDF [1] 2

6 Job Definition Format (JDF) is encoded in XML. JDF is supported by PDF document format. JDF is an extensive format which comprises workflow/ supply chain in print production. Job definition format is an evolving specification. At this moment JDF focuses on process automation in pre-press, press, and post press. Customer JDF MIS JDF JDF JDF Planning Pre-press Press Post-Press Figure 2. Schema of JDF Workflow [1] Main focus is on exploring possibilities and advantages in application of JDF between customer and print shop. The main possible advantage in the implementation of JDF is an easier and faster production and better job tracking, which results in better economy and cost efficiency. It will help printer to focus more on quality and value addition to the product rather than loosing energy in ensuring that the present multi-channel communication (about modifications on the work order) between customer and printer finds its way both to the process and to the systems involved. 3

7 2 E-JOB DELIVERY FORMATS Printing process was traditionally craft based i.e. creating a design from artwork from the ideas of graphic artist up to printing art work on the paper. Many times designers made their designs at different locations, author gave content separately and printer printed that content as per demand. There was no real communication between pre-press, content provider and print shop [3]. Competition, growth of other media, fast delivery with extraordinary print demands while keeping best quality gives printers extra cost pressures. To make shorter print run, fast delivery with acceptable quality to customer, print shop owners shift towards CIM i.e. computer integrated manufacturing [3]. 2.1 CIM in printing industry The term computer integrated manufacturing (CIM) was surfaced in late 70 s. CIM is defined as the integration of total manufacturing enterprise by the use of integrated systems and data communications coupled with new managerial philosophies that improve organizational and personal efficiency [4]. CIM is used for quality, customer satisfaction and continuous improvement. Use of single computer database to store all product information, removing communication barriers between all production departments and integration of enterprise resources are some of the features of computer integrated manufacturing [5]. CIM is divided in two categories - flow based manufacturing such as PC manufacturing, automobile manufacturing or production of gasoline, steel etc. and second one is job-based manufacturing. Print production comes under job based manufacturing. In printing, production line for every job is reconfigured according to the nature of job. The path of the job is programmed according the job and documented in the job ticket. The ideal job ticket carry all the necessary information required to manufacture and deliver the job. Job ticket also contains information about customer, business agreement and exact description of customer defined quality. CIM has management practices based on ISO 9000, Six Sigma, and TQM. Management information system provides material to CIM [5] [6] With the integration of computer in print manufacturing traditionally manual operation are now controlled automatically.[6] Benefits of CIM - 1. Reduction in operator errors due to few operator inputs. 2. Increase in production efficiency. 3. Enhanced production planning and scheduling. 4. Better understanding of production cost result in better decision making of job costing which results in higher profit margins. 4

8 5. Better analysis of processes suits for the equipments in hand, reduce wastage. 2.2 Publication of E-job tickets E-job ticket publication in graphic arts industry PJTF IfraTrack CIP4 PPF Figure 3. Publication of e-job ticket specification [1] CIP3 / PPF CIP3 consortium officially stands for International Cooperation for the Integration of Prepress, Press and Post-press. Around 1998 CIP3 consortium s Print Production Format (PPF) was accepted widely and printing industry truly got the status of manufacturing industry. PPF is mainly dealing with technical data such as ink key settings [4] [8]. Print production format uses PostScript language syntax to store pre-press, press and post press data. Print production format is applicable to the press and post press. PPF was first step towards open standard and interoperability between print vendors. The main of aim of PPF was to avoid repetition of entering the same information regarding prepress, press and post-press operations on the same production line. It gives lesser errors and save production time and most importantly machine is controlled directly from the data given in the file. Although PPF uses postscript language model, all postscript commands were not used. Only static description is included in PPF. All data is stored hierarchically i.e. in the same order in which print process executes. Some of the standard content in format included registration marks, color control data, folding marks, and preview image. Private data can be included in the format and vendor can write his own data [4] [8]. Production planning and Imposition Plate Making RIPing Printing Delivery Figure 4. CIP3 workflow [9] 5

9 2.2.2 Adobe PJTF Portable Job Ticket Format (PJTF) initiative is taken by Adobe in the year Portable job ticket format is based on PDF standard. It is an extension to the Adobe s postscript level3 format. PJTF is applicable to pre-press workflow. However content of the page is defined by PDF and how that content will be processed is defined in PJTF. That means PJTF has more control over data while integration of creation and print production was carried by PDF [10] [11] PDF Digital data Digital Master Rasterizing Prepress Creation PJTF Prepress Figure 5. Adobe Portable Job Ticket Format Workflow [11] PrintTalk A consortium was formed by printing industry professionals mainly to communicate business information (business objects) in graphic arts industry and it was called by PrintTalk. The objective of PrintTalk consortium was to recommend common and open interface to connect e-commerce to print management systems (PMS). In February 2005 it formally joined CIP4 [12]. Open XML standard for graphic arts industry is used first time in the PrintTalk format. PrintTalk format initiated communication of business objects and print specifications between printers and buyers. Business transactions in practice are called business objects (BO). cxml Commerce extensible Markup Language is used to build the PrintTalk format. Printers, print equipment manufactures, ecommerce professionals and print system developers contributed to this format [12]. The main emphasis of PrintTalk is on business management system. These business objectives are given below [12] 6

10 Request for Quote (RFQ) Quote When a customer comes with a new order or to change the old order he always asks for new quote. New quote sent in reply for RFQ from printer. It may contain detailed information about printing processes that are going to be used for new job or it may contain very basic information such as price and billing information. Purchase Order In response to a quote print buyer sends an order to printer containing a list of finished good items. Order Confirmation Cancellation Refusal Confirmation of order is sent by the printer to print buyer as a receipt of acknowledgement. Cancellation of the whole job can be sent to buyer from printer or vice versa. If a part of the job is cancelled the RFQ is sent. If order is declined either by printer or buyer then refusal is sent. Order Status Request Request by either buyer or printer about the status of order. Proof Approval request Approval of a soft proof from the buyer is necessary, so printer send a request for proof approval. Proof Approval Response Invoice Response from the buyer for the approval or denial of the proof. Printer sends a bill when job is delivered or certain part is completed. 7

11 Figure 6. PrintTalk workflow [12] 8

12 PrintTalk format structure is divided into three parts, head information, request information and JDF root node. cxml is used to describe this information [12] <XML> <PrintTalk> <Header> <From> <Credential> <To> <Credential> <Sender> <Credential> <Request> <JDF> <AuditPool> <ResourcePool> <Intents> <ResourceLinkPool> <IntentLinks> </JDF> IfraTrack Ifra working group developed IfraTrack specification. IfraTrack serves newspaper industry. IfraTrack specification is used to share order management status and information in local and global production management systems in newspaper production. First IfraTrack specification1.0 was published in the year IfraTrack specification is a tracking message exchange method. Newspaper production is a complex production process from production planning to distribution of newspaper. Objective of IfraTrack specification is to get real time information throughout the supply chain along newspaper production line by integrating economy control and production management. General workflow for IfraTrack is same as newspaper production workflow [13]. Global Production Management System Local production management system Production Planning Prepress Plate making Press Post-press Figure 7. IfraTrack workflow [13] 9

13 Ifra released latest specification version IfraTrack 3.0 in the year IfraTrack specification is based on newspaper production processes and use semantics, syntax and message exchange mechanism [13]. Semantics is content and extent of data to be included for message communication Syntax is way to describe the data and encoding method for tracking messages. Message exchange mechanism is a method to exchange messages that we defined in syntax. Tracking of production process is made easy by tracking object classes. Object classes are defined to identify the area for exchanging messages or use of IfraTrack in the modeling of workflow in newspaper production. Some general object classes are prepress, press, postpress and delivery. In specifications 1.0 and 1.1 of IfraTrack, working group decided to use simple text string which is the easy way to analyze and understand the incoming and outgoing messages. Time, message sender, object identifier, object data should be included in tracking messages. In lining with JDF standard, IfraTrack working group in the year , decided to use XML language schemas as a new message format. Different types of message exchanging methods are used to track production. More commonly used methods are TCP/IP, file exchanging, centralized SQL based database, time synchronization approach [13] AdsML AdsML specification is used to create a framework for global standard in advertising workflow. AdsML is supported by Ifra and Newspaper Association of America. AdsML is a method to enhance the data exchange between all types of advertising through all stages of life cycle of advertisement. AdsML facilitates integration of data [14] AdsML 1.0 specification was released in the year This specification describes the advertising markup language based on XML schema definition which is used for encoding and routing messages. CREST- US standard for classified advertisement, AdConnexionused for transactional data to display advertisement in Europe and SpiceXML- a general standard for media advertising, are the basis used to build AdsML 1.0 specification. AdsML framework is not only used to exchange content data or process workflow but also to exchange business data among advertisers, media distributors along the whole logistics chain. [14][15] In April 2005, CIP4 and AdsML jointly decided to cooperate on international standard development for advertising production workflow in print media. [15] 10

14 2.3.6 CIP4/ JDF CIP4 an international consortium stands for International cooperation for integration of processes in Prepress, Press and Postpress. CIP4 is a standard development organization working on the development of Job Definition Format (JDF) [16]. CIP4 was formed in September CIP4 was formerly known as CIP3 which was formed in Heidelberg in Print Job ticket known as Job Definition Format (JDF) was initially developed by four big player of print and publishing industry Adobe, MAN Roland, Agfa and Heidelberg. JDF is an evolutionary extension of PPF by CIP3, Adobe s Portable Job Ticket Format (PJTF). Job Definition Format is metadata exchange format encoded in XML language. In 2001 JDF specification was handed over to CIP4 for future development. JDF 1.0 was published in the same year. This was followed by the release of JDF 1.1 and JDF 1.1a specification in the year In April 2004, version 1.2 was released [1] [16] Principles in development of JDF [1] [16] Creation of metadata by collecting information from various production processes (PP) and business objects ( BO) Structuring of metadata for easy movement of metadata files. Use of XML for encoding metadata in a structured format. Keeping JDF specification open to all. 11

15 2.3.7 JDF Vs PPF Vs PJTF JDF- Job Definition Format PPF- Print Production Format PJTF- Portable Job Ticket Format 1. JDF is applied to logistics chain in print production. 2. JDF is an extensive and open standard format. 3. XML is used for encoding JDF. 1. CIP3/PPF was mainly applied in press and postpress department and in particular ink-key presettings. 2. PPF was proprietary format. 3. Post Script is used for encoding PPF. 1. PJTF was mainly applicable to pre-press department. 2. PJTF was developed by Adobe. 3. PDF or Post Script 3 was used for PJTF syntax. Table 1. Difference between JDF, PPF and PJTF 12

16 3 XML Use of XML for encoding JDF specification is one of revolutionary changes in printing and publishing industry. Main advantages in using XML in graphic arts industry are [17] - Compatibility with cross media publishing and e-commerce. - Format independence and conversion capability - Optimum use of content management XML stands for extensible Markup Language. XML 1.0 recommendation was first introduced in February 1998 by World Wide Web (W3C) consortium. XML is metalanguage. XML is derived from SGML and it is as simple as HTML. XML is used to structure, store content data. XML doesn t have any functionality. XML doesn t have predefined tags like HTML. Tag is a text enclosed in < and > signs. XML allows users to define user s own tags [18] XML has physical as well as logical structure. Physical structure has units called entities. Entities consist of content. Content can be an image, text, audio and video. Entities can be parsed or unparsed. Parsing of XML is carried out by processor and the content of parsed entity is XML data. Entity that contains non XML data is called unparsed entity. Logical structure of XML is defined by markup tags. Markup tags comprise content data. Document Type Definition (DTD) file is a grammar which helps to define logical building blocks. XML document has two properties well-formed ness and validity. Data in XML document can be well formed but may or may not be valid, but valid XML document is well-formed [18]. For Valid XML document, following statements are true 1. It contains one or more documents. 2. It fulfils all well formed ness constraints including e.g. how identifiers must be declared, what the constraints on entity reference are, and how a binary entity can be referenced. 3. There is exactly one element called root, or document element, no part of which appears in the content of any other element. For all other elements, if the start tag is in content of another element, the end tag can be in the content of the different element. 4. Each of the parsed entities which are referenced directly or indirectly within the document is well-formed. Apart from this, XML document is valid if it is well formed and it has an associated document type definition and complies with the constraints expressed in DTD. 13

17 Comparing with HTML, XML syntax is structured. In XML, all elements must have end tags, all the attribute values have to be quoted and overlapping of elements is not allowed. All elements and attributes are case sensitive. 3.1 XML document structure XML document always start with XML declaration in the following form: <? xml version= 1.0, encoding= iso ?> This is xml version 1.0 and encoding is set to iso , encoding data is necessary so that xml parser can decide what kind of character set it can use. Default character set is Unicode; UTF-8 [19]. Six markup tags are used to define xml document structure. These markups are elements, comments, processing instructions, character data and entity references and document type declaration [19] Element names and attribute names are called by XML names. XML names may contain alphanumeric characters from a to z and A to Z (case sensitive), numbers from 0 to 9 or non English numbers, special characters and ideograms. It may contain underscore (_) or hyphen (-) and period (.). XML names should not contain characters such as (,,, $, ;, ^, %). Like HTML, XML element tag starts with less than sign (<) and ends with greater than sign (>) for e.g. <document>. Content of the element is written between start tag <document> and ends with end tag </document>. Some elements can be kept empty and can be written like </document>. This indicates XML element is just occurred and no matching tag should be sought. Elements may have attribute values and can be written inside start tag after the element name. < Date format= dd-mm-yy > [18] [19]. To give information about markup is always a good design practice, so that the people who read that markup can understand it easily. The comments are given in the following way <!--comment.--!>. Parser can ignore it and continue to next tag. Double hyphen should not appear in between until comment is complete [18] [19]. Processing instruction is used to process application. Processing instruction tells the application how to process the information between question marks. E.g. <?name PIdata?> The name called PI data is identified by the application. [18] Character data can be any type of number, text or letter. Blank space can be treated as a character data. Some parsers ignore the blank spaces. An element also contains character data with other elements. Character data is denoted by CDATA [18]. Entity references are references to most characters, text or media. It can be expanded further when XML document is parsed. Entities are used mostly to represent special characters. Entity must have a unique name that is referred to when using entity. Entity references have alternative ways to represent as content. There are five pre defined entities 14

18 &lt, &amp, &gt, &quot, &apos. While using less than and greater than sign as entity, it is obligatory to use in predefined way [18]. 3.2 Document Type Declaration Document type declaration provides grammar for the XML markup language called as DTD or Document Type Definition. DTD is defined outside the XML document. This declaration contains element type declaration, attribute list declaration, entity declaration, or notation declaration [18]. Element type declarations identify the name of element and describe their content. For e.g. <! ELEMENT book (toc, chapter*, references+)> The first part of element defines the name of the element; second part describes the content model. Values separated by commas indicate that particular element must occur in succession. Vertical bar between values, may indicate an or relationship. Punctuation after element name indicates whether value occurs at least once (+), zero or more time (*) or optionally once (?). A name with no punctuation occurs exactly once. [40, 42] Element content can be described using symbols such as #PCDATA, EMPTY, ANY. # PCDATA is reserved for indicating character data, EMPTY indicates element, does not hold any content and ANY indicates that any content is allowed [18][19] DTD must declare attribute list for each element. This is done by the value ATTLIST. <ATTLIST book name ID #REQUIRED> There are three default attribute values; #REQUIRED, #FIXED and #IMPLIED. If value is given by #REQUIRED then attribute value is obligatory. If attribute value is given by #FIXED then attribute must have specified value. If the attribute value is given by #IMPLIED then it is optional. #CDATA is the most common attribute type given as plain text. The other possible attribute types are [18]. #ID Uniquely identify individual elements in a document means all ID values in the document must be different. #IDREF OR IDREFS- The value of IDREF must be the value of a single ID attribute on some element in the document. IDREFS may contain multiple reference values separated by white space. #NMTOKEN or NMTOKENS- Token attribute is a restricted form of string attribute. NMTOKEN attribute must contain single word. NMTOKEN must contain multiple NMTOKEN values separated by white space. [18] #ENTITY OR ENTITIES- The value of ENTITY must be the name of a single entity. ENTITIES may contain multiple entity values separated by white space. 15

19 3.3 XML Namespaces If two different XML documents contain same tags in different context, it poses problem of recognition and collision if two documents added together. XML namespaces solve this problem by allowing using same tag in different context. Definition of XML namespace is a collection of names, identified by URI reference, which are used in XML documents as element names and attribute names. XML namespaces recommendation was announced in January 1999 [20]. XML namespaces are declared at the beginning of XML document by combining identifier and the URL of the namespace. Identifier is added as a prefix to any element name in the document, that element is belonging to the namespace specified with the URL. By declaring a default namespace at the start of the document, any tags without prefixes are assumed to be in the default namespace [20]. 3.4 XML schema XML schemas (XSD) are vocabularies used by system to follow rule. XML schemas provide structure, content and semantics to XML document. Like DTD it provides data type of each element and attribute. Theses elements and attributes can be used for validity of well formed ness of XML document. There are clear advantages in using XML schema over DTD [21] Unlike DTD, XML schema is written in same syntax like XML. XML schemas have a object oriented approach. XML schemas have more flexibility; we can define more elements with same name but with different content i.e. supports namespaces. More information can be added to XML schema comparing with DTD. Schema declaration has complex and richer structure than DTD. XML schema declaration provides additional data types over default data types such as Boolean, strings, number, etc. Developer can build own library of interchangeable data types. First schema recommendation was given by World Wide Web consortium on March 2001 [21][22] 3.5 XPath XPath is a language used to find information within the XML document. XPath navigates through the elements and attributes in the XML document. XPath syntax which is compact and different from XML, is used to manipulate strings, numbers and Boolean [23] XPath is a major element in XSLT Extensible Stylesheet Language Transformation. XPath describes the document in tree structure. In tree structure element node, attribute node, text node, namespace, processing instruction, comment and document root node are seven types of nodes used by XPath. String value for each node can be calculated with the help of XPath syntax. XPath supports XML Namespaces. Context expression used in XPath to use in XSLT and XPointer consists of context node, a pair of non-zero positive integers i.e. context position and context size, a set of variable bindings, a function library, 16

20 the set of namespace declarations. Context position is always less than or equal to context size [23][24] One important expression used in XPath is location path. Location path is used to select nodes relative to context node. Location path can be used to filter the set of nodes. Relative location path and absolute location path are two types of path expressions used by XPath. Relative location path consists of one or more location steps separated by forward slash /. Absolute path expression consists of forward slash / followed by relative path expression. XPath expression always returns a node-set, a string, a Boolean or a number [23][24]. XPath syntax uses path expression for e.g. /Book/Chapter [16], means expression selects first chapter element which is child of Book element. 3.6 Content Vs Metadata Content data is the data in the print media such as newspaper. Content data is written by author or publisher. Content data is stored in database which is used to produce the print or used in electronic media. Portable document format (PDF) is used to describe and exchange content data. JDF is a metadata language for the workflow in print production. Metadata is used by software applications to define the processes. JDF purely contains production data and management data. XML is used to write JDF metadata. In JDF content data is given by URL links [19][33]. 17

21 4 JDF BASICS Definition of Job Definition Format (JDF) is given as A set of open, scalable process control definition which controls and manages entire workflow in the product life cycle of a print job [28].Standards like CIP3/PPF, PJTF, IfraTrack and AdsML are either customized i.e. applicable to a particular product such as newspaper and advertising or limited to printing processes such as prepress, press or post-press. In PPF or PJTF, ability to control and track job from start to finish was not provided. CIP4/JDF is the first standard which is applicable to each department in print production. JDF has three significant features which make distinction with other job tickets such as PPF or PJTF [17] [26] Applicability of JDF from inception of a design or content to delivery of a job to print buyer. Communication with Management Information System (MIS) Greater Interoperability. JDF is called a next generation open standard. System integration is a key to faster production, better quality and curbing production costs. When all production processes are connected together they work as one machine [27]. The advantages of networking are Organized and centralized data Smooth flow of data from sales to production Accurate information about work in progress. Integration of front office system with production and workflow. JDF facilitates networking. Job planning and controlling is done by Management Information System (MIS). JDF integrates production system with management information system. JDF communication is bi-directional. While Computer Integrated Manufacturing (CIM) is a concept, JDF gives comprehensive and flexible solution for computer integrated manufacturing. [17][27][28] 18

22 Design studio Database E-business Customer Delivery Sales representative Production Storage and communication media Figure 8. Product life cycle and JDF [29] 4.1 Four C s of JDF Comprehensive, connectivity, control and communication are four main benefits of JDF. 1. Comprehensive- Job definition format is so extensive that it is applicable throughout product lifecycle in print production. Before development of JDF there was many islands in automation where automation was applied either prepress department or printing department or post-press department. But JDF is compliant with any part of workflow. JDF is the first open standard in graphic arts industry [17] [28] 2. Connectivity- Connectivity comes first while talking about JDF. Two systems, host and clients are not only connected locally but can be connected globally. JDF enables e- commerce by connecting B2B and B2C in e-commerce and e-business [28] [29]. 3. Control- By controlling all areas of workflow JDF gives fast production with high quality and better job tracking. Process monitoring gives better system performance. More controlling means more automation and more automation leads to high efficiency [28]. 4. Communication- JDF is encoded in XML and therefore do not restrict length of character string of communication data. Understanding instructions and exchange of data 19

23 between different JDF enabled applications is possible like never before. It allows compatibility with internet based workflows [29] [2]. 4.2 JDF workflow Management Information System (MIS) Order management JMF Production planning and control JMF Production resources JDF JMF Creation Prepress Press Finishing PJTF PPF PPF JDF Figure 9. JDF workflow [2] Integration between management information system (MIS) and print production processes is most important feature of JDF. Horizontal integration is carried out with the help of PJTF and PPF for print production processes. Order management and print production processes are integrated vertically. With cooperation between IfraTrack and AdsML, CIP4 has now enabled integration with newspaper printing and commercial printing such as advertising MIS Management Information System (MIS) is a heart of any manufacturing process. In general, definition of management information system is given by a system consisting network of all communication channels used within an organization. Collection, manipulation and dissemination of data are the tasks carried out by MIS. Information system comprises of hardware such monitors, software which is connected to communicating lines such as telephone or internet. [30]. In JDF enabled print production, management information system plays important role. MIS manages billing, accounting and inventories as well as controls and tracks processes. New management information systems have Graphical User Interface (GUI) which is easy to work on the system [16] [27] [20]. 20

24 MIS consists of three different layers i.e. order management, production planning and control and production resources. When customer comes with an order, a front office person enters required product details in the system. All the job data is send to the production planning and control layer. In the production planning layer, all process structure and product structure is being mapped. In second case operator manually plans the process and product structure using electronic planning board. All the information related to the print job planning is relayed all over the network to production planning tool. This procedure occurred in real time, means operator can see the status of the job. If error occurs, he can make necessary changes by stopping the system. With available information from the process data MIS calculates the actual process resources available and required resources. Required time for process execution is also calculated, e.g. time in prepress, time in plate making. All data is used for costing, statistical evaluation and job planning. All messages are carried by JMF in MIS [11] [18] [20] JMF/ Job Messaging Format Messaging task is accomplished by Job messaging format (JMF). Messages are transferred across all parts of production system and MIS in real time. XML is used to write messages in JMF. JMF can be unidirectional or bidirectional depending on the user what he prefers in the system. JMF can control devices on the shop floor or can change the job queue order. JMF has an ability to command one controller via another [16][27] Three capabilities given by JMF are no messaging- in this case controller checks JDF and decides further action. Second capability is notification- the messages coming to the controller devices can complete some basic procedures with in the job. Notifications are unidirectional. Third capability is queries- devices which support queries give current status of job. Queries are bidirectional communication. HTTP transfer protocol is used by JMF to transfer and receive messages [16][27]. 21

25 5 JDF ARCHITECTURE Print production involves many complex processes and when customer gets integrated in the logistics chain the whole chain becomes extensive. The whole print production process is characterized in JDF as a tree structure called as a JDF tree. Tree structure is represented by hierarchical pyramid [2][33] Product Intent (+ Customer Profile) Process Group Individual Processes Figure 10. JDF Pyramid Structure [34] Data used to describe JDF framework consists of master data, product structure data, process structure data and process resource data. Master data- Customer contact details with customer profile are stored in master data. Job details given by the customer are stored with customer information. Quotation can be written with the help of job data given by the customer. The data regarding paper grades, print quality, finishing parameters is stored in master data [2] Product structure data- Product description can be created with the help of data given by the customer about the product, required material and parameters, Product structure description is then transferred to order management system. Product description is used to create tree structure in JDF. JDF templates can be created with product data for frequently used products [2] Process structure data- process structure data is created in order management system. Process structure data describe the production processes which are used to create the desired product. The detailed process hierarchy is written in the sequence of production [2] Process resource data- required ink and paper, waste material information is stored as resources with resource data such as ICC profiles, PDF files and machine parameters. Approved proof with customer s digital signature can be stored as resource data [2] 22

26 Product Node Magazine Cover Content Process group node Cover production Content production CTP Press Cutting Post Presss CTP Press Cutting Final product Indivisual process node Figure 11. JDF tree structure [16] 23

27 5.1 JDF System Components JDF is divided in three components JDF Node, JDF Resources and JDF ResourceLink Common JDF Node Types Information about the job is stored logically in blocks called nodes. Nodes are constructed in hierarchical format and encoded in XML. Single node describes a specific part of a process to produce the end product. Node carries elements, sub elements and attributes. Each element and attribute in the node gives characteristics which helps to give location and usefulness about that particular node. As described in section 3.3, elements are standard XML syntax and attributes defined as data types such as strings, time, date etc. JDF node gives three basic characteristics [16] Name Identity is given by the name to the element. Data Type - Data types are applied to elements. A short text element is called telem. Description- The details about attributes or elements are given by description. Input (Resources) JDF Node Output (Resources) Start End Scheduling Time Figure 12. JDF Node and Resource Interaction [33] A single or multiple processes as well as resources are defined by a JDF node. Resources can be physical material or data regarding job. Broadly nodes are defined in two main categories Product intent node and Process Group node. [16][27] Product intent node- Top level nodes are used to provide product details or master data. Process data is not contained in product intent node. Intent resources, customer profile and product information is included in product intent node. Future possible and acceptable processes and their resources are given in product intent nodes. Each resource element may have a set of sub elements. Each product intent node is linked to resource intent by one resource link. Each part of the product has its own product intent node. [16] Process group node- The group of processes are defined in process group node. Process group node is placed in intermediate level of pyramid. Process group node is used to describe multiple steps in process chain having common resources. There is flexibility in 24

28 grouping the processes and logic of the author who creates the workflow. One process group contains child process group or single process node or mixture of both. According to the seniority in the group, process nodes are arranged hierarchically from first to last. Higher the level of process group, larger the number of processes incorporated in the group. [16] JDF does not require a particular workflow. Flexibility of JDF workflow allows it to model existing standard workflows as well as highly customized ones in interlinking the required nodes for printing a product. JDF is equally as effective with a simple system using a single controller-agent and device as it is with a completely automated industrial press workflow with integrated pre-press and post-press operations. [16] JDF provides four basic process-routing mechanisms: [16] RIP Press Finishing RIP Press Finishing Serial processing- Subsequent processing, represented by a single process chain. Overlapping processing- simultaneous processing with the help of pipe definitions RIP Press Finishing Parallel processing- Parts of the JDF tree are spawned for independent processing and merged back. Press Touch up Editing Iterative processing- Repeated circular processing. Layout Figure 13. Processing types [11] 25

29 5.2 Network in JDF Exposed media (Plate) Media Ink Node Info -Planned start time -Planned end time Audit Pool Actual Resource usage Actual Time Summary Conventional Printing InkZone profile Parameters Layout(Control marks) Resource Links Component (Including Amount) Figure 14. Sample JDF Node [1] Each process has minimum one input node and one output node. Nodes do not operate until they get all the necessary resources. Nodes are executed in well defined sequence. In the hierarchy of JDF nodes which are in the upper level describe brief operations that means they represent components in the product while the nodes which are present in the lower level of hierarchy represent detailed description of processes i.e. they describe the instructions for the device to perform operation. The combination of hierarchical nesting of nodes and lateral linking allows complex process networks to be constructed. [16] parent JDF node A Figure 15. Hierarchical tree structure of JDF nodes [16] Identical nodes are linked to their respective process resources in the process chain. Output resource of one node represents the input resource of following respective node. It is called as resource linking. This characteristic helps to form complex networks in JDF. Linking of 26

30 processes is not defined in JDF. Dependency of node on the input resource defines the process execution. If one resource output has many possible routings then MIS used in the system gives the solution for linking of processes with resources depending on local constrains [16] Figure 16. JDF process chain linked by input and output resources [16] 5.3 JDF node element Top level of instance written in JDF file is called JDF element. JDF element can be nested to another JDF element. A single JDF element is called node. Each node has attributes and subelements. Subelements in JDF node element are <BestEffortExceptions?>, <CommentURL?>, <DescriptiveName?>, <MustHonorException?>, <OperatorInterventionException?>, <SettingsPolicy?>. Most common subelements of Comment (telem) element are <Attribute?>, <Box?>, <Language?>, <Name?>, <Path?>.[16] Any JDF node element BestEffortExceptions? CommentURL? DescriptiveName? MustHonorException? OperatorInterventionException? SettingsPolicy? Comment Attribute? Box? Language? Name? Path? Table 2. Structure of JDF contents [16] 27

31 Comment Ancester Pool Customer Info JDF Node Info Resource Pool ResourceLinkPool Audit Pool Status Pool Figure 17. JDF node and child elements [16] JDF node attributes and sub-elements Type is the most important attribute in the JDF node. Type defines the node type as well as the process or product represented by JDF node. All other nodes are optional in a sense that they will be required in certain circumstances. Some of the attributes are Activation, Category, ICSversion, JobID, NamedFeatures, etc. [16] AncestorPool element When job is finished, AncestorPool element is created. AncestorPool element contains information about job context which need to identify the family which job belongs to. It helps job to correctly merge with its parent. [16] CustomerInfo element CustomerInfo node contains information about the customer who orders the job. CustomerInfo element is specified in job root node. It can help to provide information to customer about the status of the job. [16] NodeInfo element NodeInfo elements help MIS to plan, schedule and invoice the jobs and job parts. [16] StatusPool element StatusPool element describes the status of individual part of the JDF node where processes partitioned resources. [16] 28

32 5.3.6 Resource Element Resources are categorized in physical resources and conceptual resources. Physical resource can be paper, ink, digital data, etc. and conceptual resource can be statistical parameters, number of colors, trim size, etc. Every process either consumes or produces resources. Class attribute is most important attribute in resource element. Class attribute gives information about how the particular resource should be used. Resource element is placed in ResourcePool element or in JDF node which is closer to JDF root node. It is good to place resource element near to node that is reference to resource. Some of resource sub elements are intent resources, parameter resources, PlaceHolder resources, Pipe resources, etc.[16] ResourceLink element ResourceLink element links node to resource. ResourceLink element gives information about what resource a node may use. They help in calculating node dependency. ResourceLink element resides in ResourceLinkPool element. ResourceLink element defines which is output or input resource which in terns provide conceptual link between execution elements of JDF nodes. ResourceLink element s attribute may select a part of or all resources. ResourceLink element may be used for process control. [16] AuditPool element After the completion of job; information such as job history, process execution, quality control, troubleshooting, is stored in AuditPool element AuditPool element is static and it can not be modified once process is aborted or completed. Creation of JDF node, spawning and merging of resource copying, errors in wrong linking, actual data of production and resource consumption, process phase times, process scheduling data and any modification of JDF node are recorded by Audit element. Audit information may be used by MIS for evaluation or invoicing. [16] JDF Extensibility element JDF is open specification and can be used by any printer, print machine manufacturer, customer. XML Namespace is used for encoding JDF extensibility element. With JDF extensibility element vendor can add his own specific data. Vendor can add his own XML elements and attributes. [16] JDF versioning element JDF recommendation is evolving. It is growing towards maturation and JDF recommendation is already available in different versions of specification. Different workflow solutions are supported with different devices. This is the reason to add JDF versioning element in JDF node. JDF definition, JDF specification version, JDF schema version, JDF application version, JDF agent version, JDF device/controller version can be included as elements in JDF versioning element [16] 29

33 5.4 ICS JDF specification is very large due to its application in all areas of print production. It is very unlikely that each JDF enabled product is implemented with all JDF specification. For instance a printer might not have his printing machine enabled for JDF prepress specification as he provides only printing service or an image setter need not facilitate preflighting. In this case interoperability is impossible between all JDF enabled products. To solve this problem CIP4 has come up with Interoperability Conformance Specifications called as ICS. ICS specifications contain well specified subsets to define interface between all JDF enabled products. ICS specifications specify what exactly individual classes of devices need to do. ICS documents are continuously developing. CIP4 have plans to use ICS documents as the basis for JDF certification testing and if product vendors apply ICS specifications in its product, that product can be endorsed with a mark JDF certified. [1] ICS documents specify interoperable interface between manager of a job and the worker. JDF enabled devices, for e.g. workflow system, management information system, called as a manager and software that performs the job is called as a worker. ICS documents define a role for manager and worker to read and write JDF and to support JMF. It also gives information about how job files can be exchanged or identifies and supports particular processes or resources. ICS documents are not additions to JDF specification but it works as a subset, specific to the interface that is defined in the respective ICS. [1] CIP4 has published eight documents including the base ICS document which covers interfaces for binding, MIS, MIS to Prepress, Prepress to conventional printing, MIS to conventional sheet-fed printing, integrated digital printing and Layout creator to imposition ICS. [1] Base ICS- This document defines conformance requirements which are common to all other specific ICS s. MIS ICS- This document specifies conformance requirements for the communication of MIS with production equipments and describes requirements for all production processes such as prepress, press and post-press. Binding ICS- This document defines conformance requirements binding devices such as saddle stitching, soft cover and hard cover. Conformance requirements specify JDF instances, JDF messages and processes. MIS to Prepress ICS- This document specifies interface between MIS and prepress system. It defines processes for prepress workflow system to produce proofs, plates and previews for conventional printing. Prepress to conventional printing ICS- This document specifies interface between prepress workflow system and conventional printing press controller and describes how prepress workflow system dynamically communicates with press controller to deliver previews used to evaluate ink zone settings and information about plates. 30

34 MIS to conventional printing ICS- This document specifies conformance requirements for an implementation of JDF device that accepts job ticket for sheet-fed offset printing. Integrated digital printing ICS- This document is useful for black and white and limited color integrated digital printing systems with in-line finishing operations. Layout creator to Imposition ICS- This document defines interface between layout creation tool and consumer of a fully populated layout resource such as prepress workflow system. 31

35 6 NETWORKING IN PRINT PRODUCTION The networked graphic production is a need in today s graphic art industry. JDF is one of the solutions for networking in graphic arts industry. Networking is needed for the integration of print buyer, printer with production. Networking in the sense of integrating customer and printer with production means to make process more transparent and faster [2] [35] In JDF based networking system the logical components in networking architecture are [2] Agents- A task of writing JDF file is given to agent. Existing agent can be modified or extended. Controllers- Controller gives direction to JDF data to a specified location. Devices- Device is an interface between software application and machine. Devices interpret JDF data at specified node and control the specified machine. Machines- Machines are components of the workflow that carry out the processes. The agents, controllers and devices provide bi-directional communication mechanism for messaging with JMF interface. Two basic architectural designs for process integration are Decentralized architecture and Centralized architecture. [2] Decentralized Architecture Order mangement systems Pre press Press Post press Figure 18. Decentralized architecture [2] In decentralized networking, data or message is exchanged from one software application to another sequentially. JDF file is saved in database by respective software application. [2] 32

36 Centralized Architecture Order management system Pre press Master JDF Post press Press Figure 19. Centralized Architecture [2] In centralized architecture, server plays elaborate role. Master JDF file is stored centrally in server database. Database management application allows simultaneous access of master JDF data by other process applications. [2] Apart from cost and quality advantages of networked graphic production and process integration over traditional print production approach are [36] - Increased collaboration between buyer, printer and creative professional such as online communication regardless of geographical location, better job tracking and more control over production, online collaboration is fast and flexible. [36] - Sharing of job information is bi-directional which improves planning and accuracy and reduces errors in data entry, up to date data is available for reference, job estimates can be drawn with available reference data with less margin. [36] - Enhanced integration of process data and management data helps to track real time job costs and stored for future knowledge, customer order revision is collected automatically. Data transfer takes place digitally, material wastage can be reduced. [36] -Time consuming processes are streamlined and accelerated automatically. Collaboration between customer and printer improves customer satisfaction which leads to long-term business relationship. [36] 33

37 6.1 Customer Integration Unlike many other manufacturing processes, printers have direct link with customer. It creates special relationship between customer and the printer. Within competitive environment business objective is not only to create new customer base, but also more important to retain customer. Close relationship enables printer to adapt to customer defined quality. Sophisticated new technologies in the printing industry make it possible to meet or even exceed customer expectations. Customer centric business practice helps to maintain reputation of any printing organization [35] [37] Supplier Post-press Order mangament Press Customer Pre- press Sales Figure 20. Customer centric workflow [38] 34

38 6.2 Process modeling Process is defined as naturally occurring or a desired sequence of operations or events possibly taking up time, space, expertise or resources and produces some outcome [30]. Basic definition of process modeling is a graphical representation of processes with rectangles or arrows depicting processes, process resources, logic and movement of information between systems [39]. Process modeling shows the way process would be or should be occurred. The aims of process modeling are descriptive, prescriptive and explanatory. Descriptive means it records what happens during the process and give the information from the observer s point of view regarding the process performance and improvements in the system. Prescriptive means it defines the process and tells how the process could be or should be performed. It defines rules, guidelines and behavior patterns. Explanatory means it gives explanation for the basis of process and explores and evaluates possible actions. A process modeling is applicable to business processes, computing systems, chemical processes, manufacturing. [30]. Process modeling plays two important roles [39] 1. Record existing process structurally, representing activities and related elements. 2. Represent related processes in order to evaluate the performance. UML, Flowcharts, Petri Nets, Simulation, Activity based costing (ABC) and IDEF diagram are some of the basic methods used in process modeling UML The Unified Modeling Language (UML) is a general purpose visual modeling language used to specify, construct and document artifacts. Although UML is generally used to design software system, it is also used to for business process modeling. It helps to understand, design, browse, configure, maintain and control information about the system. UML includes semantics concepts, notation and guidelines to develop a model. UML has static, dynamic, environmental and organizational parts. UML modeling technique applies through life cycle of the product from the description of the product by the user up to the finished product. UML modeling is divided in different areas- structural classification, dynamic behavior, physical layout and model management. UML uses nine types of diagram or graphs to describe the modeling, from which seven types are used in business modeling with explanatory comments or can be explained in plain spoken language. [40] Class diagram is built on classes and relationships. It describes structure of the system. Classes represent products, documents, information and organizations. Object diagram developed with combination of special classes. Object diagram is same as class diagram. [40] Statechart diagram- Statechart diagram explains possible states of the system. It describes entire life cycle of the object and the system. It tells how different event can change the view of the system over a period of time. [40] 35

39 Activity diagram- Business processes can be described with activity diagrams. Activity diagrams describe activities and actions occurring in a sequence. Input and output parameters of an activity can be shown with process flow by connecting activity and object nodes. [40] Sequence diagram- This diagram describes sequences of messages in set of objects. Order and timing is important in describing the sequence and it is written on the diagram. Messages can be synchronous or asynchronous depending upon process. [40] Collaboration diagram- It presents sequence of collaborating object like sequence diagram but difference is collaborating objects have more complex relations and interactions. [40] Use case diagram- Use cases models the functionality of a system with the help of agents called as actors. Use case is a functionality expressed as a transaction among actors and the system.[40] Component Diagram- Component diagrams are mainly used to structure in the software system. It is not used on business process modeling. Deployment diagram- This diagram represents deployment of an artifact or physical component such as hardware with in software. Deployment diagrams are not used in business modeling. [40] UML is mainly used for software modeling. Some of the tools used for UML modeling are Altova s UModel, Honeywell s Dome, Microsoft Visual studio, etc. As there are not specific rules in UML for business modeling, so UML is not popularly used in business modeling in its current form. [40] Flowcharts Flowcharting is a process modeling technique used for tracking steps involved in process. A flows chart describes business process graphically with the help of boxes, diamonds and other shapes connecting by arrows right from the inception to completion of the process. Each symbol represents a step in the business process. Business process flowcharts can be divided into following categories- Document flowcharts describes flow of documents and information, internal control flowcharts describe and evaluates internal control, system flowcharts describe input, output and processing information of system, program flowchart describes logical operations performed by computer while executing program and computer configuration flowchart describes arrangement of hardware components in the system. [41][42] Symbols used in flow charts are Process Decision Delay Link to page 36

40 Input or Output Document Start End Thought flow charts is easiest technique to model a process some disadvantages are that they can not be used for big process as flow chart gets mode complex, do not support parallel processing and represent weak description of data. Some tools used to draw flowchart are Microsoft Visio, Corel Flow, Etc. [42] Simulation Simulation is a way to imitate the actual process or certain features of system without disturbing the real system or environment. Model of a simulated process gives insight into the operations of those systems or processes. Computer simulation is important part of modeling. To make an actual model, computer first creates a mathematical model of a process then creates sample representative scenario. Simulation attempts to predict the behavior of the process from a set of parameters and conditions. Simulated process model diagram can be drawn with the help of boxes and arrows. [30] [43] Simulation can be done in two different ways a. Discrete event simulation- This technique describes discrete processes in sequence of events relative to time. Beginning and ending point is measured by time so called as time step simulation. Variables in terms of time measure simulated process. Discrete event simulation structures a process through building blocks or flowchart which requires lot of efforts. It requires computational capability. [43] b. Continuous event simulation- This technique describes continuous process with mathematical expression e.g. partial differentiation. IN this technique time is controlled by variables expressed in terms of differential expression. Weakness of continuous event simulation is in the application of mathematical expression fits for the particular process. If applied expression doesn t fit well for the respective process simulated model gives unknown errors. [43] Some tools used for simulation modeling are LabVIEW, Matlab, and Simulink etc Activity based costing Activity Based Costing (ABC) method is an accounting technique to model the process. ABC technique can be used in manufacturing or service sectors. ABC method identifies activity centers called as cost pools in an organization, thus it helps to reduce the overhead costs per unit or assign those costs to that particular product. Activity based costing is continuous improvement process which analyze cost and remove or add non value added or value added activities respectively for greater success in business. [44] 37

41 In activity based costing costs are presented in terms of resources, activities and products. In activity based costing costs are assigned in two steps. First is to assign resource costs to the activities or processes that consume that costs and in the second step assign activity costs to the actual products delivered called as cost objects. Some of the benefits of activity based costing are [44] - Identify actual profitable and loss making customers, products and activities or processes. - It can identify real contributors to the business or activity in terms of costs consumes and performance. - Accurately predicts costs, resources in relation with product volume and organizational structure. - It can identify main causes of bad financial performance. Some tools used for ABC modeling are Bench marker Plus, AI0 WIN, Extend BPR, etc Petri Net Petri net is a mathematical representation and graphical representation of a system or process. Model consists of places (P or P-elements) represented in terms of circles, transitions (T or T-elements) represented in terms of rectangles or squares, arcs represented by arrows and tokens are unstable components in the process or system. Tokens are represented by dots inside places. Real world entities interpreted as passive elements such as conditions, resources, channels etc. are represented by Places and real world entities interpreted as active elements such as events, actions, execution of statements, transmission of messages etc. are represented by transitions. [45] T P P Figure 21. Generic Petri net Diagram [45] Transitions are active components of Petri net and transitions are used to model actions taking place in processes. Objects are modeled by tokens. Places are the states in which objects can be placed. Arcs show the way where objects change the state or created or destroyed and arcs connect places with transition. [45] Two basic strategies are used to build the net. One is bottom up modeling strategy where models are built by combining subsystems in one complex model. Subsystems are combined until desired model is obtained. Second strategy is top down modeling where one big system is divided into small subsystems and then these subsystems are modeled as 38

42 nets. Small and nets which are hierarchically lower in the system are combined to form larger nets or larger nets are decomposed into smaller one according to need. In three ways Petri net s can be modeled State oriented approach, Event oriented approach and Object oriented approach. Petri net modeling is used to represent concurrent, asynchronous, distributed, parallel, nondeterministic and stochastic systems. [45] IDEF IDEF means Integrated definition methodology or computer aided manufacturing definition. IDEF is developed in four categories IDEFø, IDEF1, IDEF1X, IDEF3, IDEF4 and IDEF5. IDEF3, IDEF4 and IDEF5 are called next generation modeling methods. IDEF was first developed by Integrated Computer Aided Manufacturing program in 1970 s. [47] Basic syntax of IDEF modeling is Box and arrow used in graphics. English text labels to describe boxes and arrows. Glossary and text to define precise meaning of diagram elements. Hierarchical structure with major functions on top with successive levels revealing well bounded detail breakout. Node chart to provide quick indexing for locating details within hierarchic structure of diagrams. Limitation of details with maximum six sub functions on each successive functions. Figure 22. IDEF notations [48] 39

43 In IDEFø diagram process is represented graphically by inputs, outputs, controls and mechanism. Inputs are resources consumed or transformed by the process. Outputs are things created by consumption or transformation of resources. Controls are the things or rules guiding the process. Mechanisms are the agents who do the actual work. IDEFø is function or activity modeling method. [47] Figure 23. IDEFø diagram [47] IDEF1 and IDEF1X diagram is represented graphically by entity, relations between entities and entity and relation classes. Entity is information available in the organization about physical and conceptual objects. Relations are association between entities. Classes are templates between entities and relations. IDEF1x mainly supports data modeling by explaining logical view of process. [47] IDEF3 diagram is most extensively used to model manufacturing process. IDEF3 uses two methods for modeling, process flow description and object state transition network. IDEF3 diagram is used for colleting and documenting process description. Process flow description gives information about how organization works while object state transition method gives information about allowable transitions of an object inside the process. IDEF3 technique captures logical events, design object oriented applications and record the results. [47] Main features of IDEF3 diagram are recording of raw data by analyzing system activities, tells how the information resources affect the operations in the system, documentation of critical data such as manufacturing data, maintenance data, analysis of system design and to help to generate simulation modeling. Both process flow description and object state transition description gives information about the whole process. IDEF3 uses boxes, circles and arrows to describe the process. Show Units of Behavior (UOB) represents activities, processes, actions, 1 and operations. Circle represents transition steps or product state in the process. 40

44 Junction boxes are used when process diverges or converges. Arrows are used to link processes. Figure 24. IDEF3 notations [47] Figure 25. Process flow description [47] 1 2 Figure 26. Object state transition network [47] IDEF4 technique uses object oriented design approach and explicitly used for object oriented software designing and implementation. IDEF5 technique is mainly used for create, modify and maintain ontology s by two main languages schematic language and elaboration language. [47] One of the main advantages of IDEF diagram is simplicity and descriptive power of a process. Basic components of IDEF modeling are boxes and arrows. Functions are denoted by boxes and interfaces, to and from the functions are denoted by arrows. [47][48] 41

45 6.3 Modeling of integration of Customer in print production Economic factors, globalization, competition, quality and use of computer integrated manufacturing in print production, urge print manufacturers to think about modeling of the production or changing the flow of work to achieve greater success. [39] [40]. Print job can be manufactured in many different ways. Some print shops have all the facilities under one roof such as studio for artwork creation, pre-press, plate-making, binding etc. Some print shops have only printing facility or any of the above process department combinations. For the process model shown below, business process interaction between customer and the printer is taken into consideration. Assumption made for model is that print shop is having all the necessary facilities required to produce finished printed product such as magazine or brochure or commercial print product. Due to simplicity and descriptiveness of modeling with specific logic, IDEF3 diagram is used to describe the production workflow for the print production process right from customer place an order till he gets delivery of finished product. Process workflow shown below has seven nodes such as customer, sales person, planning department, pre-press department, plate-making department, press department and post-press or delivery department. 42

46 Sales person/printer 2 Production Planning 1a 1b 1c 1d Pre-press 3b 3a Customer 4a 4b Imposition Print Shop Press 5a 5b Post-press/ Delivery Figure 27. Customer to printer workflow modeling [12] 1a Request for Quote (RFQ) 1b Quote (Q) 1c Purchase Order (PO) 3a Proof approval request 3b - Proof approval response from customer 4a Job status request 1d- Invoice or billing information 4b Job status response 2 Order confirmation or Cancellation 5a- Delivery/Packaging instructions Or change of order 5b- Delivery confirmation Each process or business transaction between customer and printer is represented by business object (BO). Interaction between customer and print shop can take place through sales person [12][16]. Business transaction is initiated by Request for Quote. Customer or sales person requests a quote from the print shop for the desired product. RFQ also gives specifications about the product. RFQ may contain material and methods desired by the customer. For new product new RFQ is prepared or old RFQ can be used to for re-quote [12][16]. This request is denoted by 1a. 43

47 In response to the customer request, quote (Q) is given by the printer or sales person to the customer. Quote contains detailed price and billing information or may also contain specific information regarding the process with respect of pricing [12][16]. Quote is denoted by 1b. Purchase order (PO) is placed by the customer via sales person to print shop. Purchase order may be defined in terms of printer-customer business relations [12][16]. In the above model purchase order is denoted by 1c. Invoice or billing information is sent to customer once product is shipped or with delivery confirmation and denoted by 1d. Order confirmation is sent by print shop to customer for the given purchase order as an acknowledgement. Order cancellation is given by both printer as well as customer (via sales person) [12][16]. It is denoted by number 2. Once the final order is placed to print shop, customer gives the content to pre press or graphic artist creates content for the desired product. Once pre-press prepares layout design with the given art work and content, prepress department sends layout to customer for the approval before plate making. Customer either approves the layout or sends it back for desired changes. Response is given back to customer by prepress department [12][16]. In the above model artwork approval request is denoted by 3a and response from the prepress department is denoted by 3b. Once soft proofs are accepted by the customer, final plates are sent to press for the printing. Customer may request a status of the job. It is denoted by 4a. In response to the customer request press sends a response or vice versa [12][16]. It is denoted by 4b. Delivery instructions or packaging information can be given directly by customer to postpress department. This communications is denoted by 5a. Once job is shipped printshop sends delivery confirmation to customer. It is denoted by 5b. 6.4 Integrated JDF MIS systems Choosing the MIS system is difficult decision. There are many companies provide JDF enabled applications and management information systems. Many of the products are applicable to particular process such as pre-press or press, etc. Compatibility of different applications with different machines is also difficult. CIP4 has published JDF marketplace booklet which gives latest information about JDF enabled products. Network Graphic Production TM (NGP) group is formed by companies who provides JDF enabled products. The aim of NGP is automation of printing industry and to establish efficient network between NGP partner companies and printing machine manufacturers. [50][51] Steps within the company before purchasing right JDF enabled management information system are [51] I. Formation of group of end users- Users or employees of print shop who will use the system can tell their requirements and give suggestions to improve workflow. 44

48 II. Identifying business goals- Lists those capabilities with what kind of expansion company can do and in what areas. Lists the management information systems which can full all the capabilities and expectation. MIS system which can be easily upgradeable is the best choice. Here is a list of some JDF enabled MIS systems [49] [50]. 45

49 Company Name Product Name Customer reference Arvato systems GmbH Cerm nv PMS - Cerm DiMS EFI DiMS MIS EFI Hagen OA TM, EFI Logic SQL, EFI PSI, RR Donnelly, Lerchmüller- Germany, Lithotech-S.A, NSD labeling group- NL, Roto smeets, WS packaging- US. LAgraphico-US, McCormik- Armstrong-US, Omaha Print, Jeff the printer-us, Graphisoft Goss International Heidelberg Druckmaschinen AG INTEGRAL MIS - Goss omni Link TM - Prinace - Hiflex GmbH Hiflex factory MIS Kraft printing and publishing-ger, Tanghe printing BVBA-GER, Thai Vatana Panich press-bangkok, Huttegger Inc- Austria 46

50 i-teba SolPrint BMRB International, New International, Mill group, Simpson print, Tasker & Stone, British Council, City University Novavision Software A/C Océ Print Vis MIS - OcePRISMA Production, OcePRISMA satellite, - Optichrome Optimus 2020 Colin clapp printing- UK, bishops printer- UK, Cit creative print- UK, J Thompson color printers- UK, MPG books Ltd- UK Olive Inc. PrintSapiens - ppi Media GmbH Pragma Informationssystems GmbH Printnet Croma JP/Politikens Hus, Stibo Graphic, Petit press, Berliner verlag,oklahoma publishing, Clausen & Bose-GER, Bechtle Verlag und Druck- GER, Mannheimer Morgen Großdruckerei & Verlag- GER, BASF AG- 47

51 Prism Radius Solutions, Inc. Prism WIN Enterprise 32 PECAS Vision Paragon labels- UK, Wall Printing- US, Interforms printing group- AU, Fintech- NZ, Flexoprint- SA. Moore Wallace, Nordic Printing & Packaging Inc, Berlin Industries, Decorating Technologies Systeemhuis Compri Xgram - Table 3. Integrated JDF MIS system 48

52 6.5 Present status of JDF standard JDF is an evolving standard. In September 2005, CIP4 published new version, JDF 1.3. JDF standard is applicable from small sized printshops to big printshops. JDF standard is applicable to any printing and packaging product from job creation to delivery of finished product. JDF standard is supported by IfraTrack, AdsML, ICC, Idealliance, PODi, PrintTalk, UP3i and CGATS SC6. Figure 28. Support for JDF standard [1] JDF standard is applicable to press, conventional press and Postpress. In JDF 1.2 version additional new features are Asset delivery which controls movement of digital files between customers and printshop. Preflight functionality controls preflight processes on digital files. Standardized preflight profiles and preflight reports enable integration of preflighting in all steps of workflows. File naming specification and using MIME encoding. More detailed quality controlled parameters and measurements with improved quality control reporting. Detailed color management functionality with in detail color correction and color conversion methods. Improved JMF messaging with additional JMF messages and message details. 49

53 Improved device capability definitions including language localization. CIP4 organization created working groups to write specifications for different device interfaces and different processes. Currently there are following working groups advertising, capabilities, conventional printing, device messaging or job tracking, digital printing, finishing, ICS, MIS, Newspapers, Origination and prepress, packaging and label, PrintTalk, Product certification, Product description, Schema maintenance, system behavior and interoperability, tools and infrastructure, tradeshow demonstration, web and rotary printing. Prepress to Conventional Printing ICS MIS Prepress ICS MIS Sheet Conventio nal Print ICS MIS Binding ICS MIS Integrated Digital Print ICS TBD MIS DOMAIN ICS MIS Base ICS Base ICS JDF Specification Figure 29. ICS Document structure Single most important capability of JDF 1.2 is interoperability or handshake between two different devices manufactured by two different companies. Interoperability Conformance Specification (ICS) was published in March Currently available ICS documents are for integrated digital printing, layout creator to imposition, prepress to conventional printing, MIS to sheet-fed offset, MIS to prepress, MIS. Future publication of ICS documents are publishing to prepress, imposition, prepress manager to prepress, striping, format conversion and intent to imposition. Before release of ICS specification for JDF 1.2 version, interoperability was difficult and dependant on systems of two different vendors which can or can not be interconnected. JDF 1.2 specification supports sheet fed printing and digital printing. The new version JDF 1.3 has some improvements. Now JDF 1.3 version is applicable to web offset printing, advertising and packaging printing. JDF 1.3 is capable of tracking individual elements in the page rather than only page. 50

54 Figure 30. Future applicability of JDF 1.3 Standard [1] 6.6 Status of JDF enabled systems JDF marketplace gives latest information about JDF enabled products and services available in the market today. There are today 184 products and services from 61 companies available till March Up to 3000 JDF systems are installed around the world. Two different JDF enabled systems from two different vendors can be made interoperable with the help of ICS specification. Till today there are many successful JDF enabled systems installed in print production process. CIP4 has announced International Print Production Innovation awards called as CIPPI award. CIPPI award winning case studies for year 2005 are Action Printing, Wisconsin USA. Objective Achieved- Streamlining saddle stitching operations by automating machine setup of saddle stitcher. Equipments used- Muller Martini, Prima with AMRYS saddle stitcher, Creo Upfront software. 51

55 Druckhuas Berlin Mitte GmbH, Berlin, Germany. Objective achieved- Process optimization between press and MIS to improve order processing, efficient production planning and production. Equipments Used- Hiflex MIS and MAN Roland Druckmaschinen with PECOM system. Druckerei Bauer KG, Vienna, Austria. Objective achieved- Optimizing production in press and postpress department with JDF enabled MIS system Equipments used- MAN Roland presses with PECOM system, Muller Martini saddle stitcher with AMRYS, Hiflex MIS. Williamson printing corporation, Dallas, Texas. Objective achieved- Reducing prepress operator time by eliminating manual imposition and automated stitcher setup. Equipments used- Esko-Graphics scope workflow version 1.0, Creo up front version 3.0 and Heidelberg cutters. Lavigne, Inc. Worcester, USA. Objective achieved- Automating order processing and prepress. Equipments used- Printable Technologies, PrintOne customer center, HP/Indigo production flow version

56 Kraft Druck und Verlag, GmbH, Germany. Objective achieved- Efficient order management Equipments used- Incorporated Kodak (Creo) Prinergy Workflow System 2.3, Creo Synapse Link 2.0, MAN Roland presses running the PECOM system, Hiflex MIS System CIP4 case studies also include following companies- - Westdale press Limited, UK. Objective achieved- Increasing efficiency in prepress system. Equipments used- Prinect Color Solution consisting of Prinect Printready System 2.0, Prinect Meta Dimension 4.1, Prinect Prepress Interface, Prinect Image Control, Prinect Calibration Toolbox, and Prinect Profile Toolbox. -Donnel & Nagel GmbH, Essen, Germany. Objective achieved- Process optimization in prepress and press. Equipments used- Heidelberg Prinect Printready System Color Gruppe, Munich, Germany. Objective achieved- Production automation and optimization Equipments used- Heidelberg Prinect Prinace 4.5 (MIS), Prinect Data Control 6.0, and Prinect Printready System 2.0. Many of the companies installed JDF systems in the print production processes. From CIPPI award winning companies, Lavigne Inc, was the company who installed JDF between customer and printshop. Results from Lavigne showed 92% of improvement in order processing costs with increased order processing with more customers using system. There is no system available in the market for the implementation between customer and MIS. Lavigne s customers were using Printable s PrintOne system for order while Lavigne is using HP s Indigo system for digital printing. With the help HP and Printable, Lavigne developed customized JDF interface between customer and printshop. Some of the companies which produce JDF enabled systems have formed two groups. One is Networked Production Group (NGP) and another Print City. Following figure shows status of JDF systems from the companies which are part of NGP. Some systems are already installed; some are available for installation and under development. 53

57 Figure 31. NGP system integration status [36] 54

58 7 SURVEY OF PRINTING COMPANIES The questionnaire was developed on the basis of workflow between customer and printshop. Process model in figure 27 shows integration of customer in print production process. Customer interaction takes place with sales person. Request for quote, Response to RFQ (Quote), Purchase order, Order confirmation, Proof approval request/response, Job status request/response, delivery instructions and customer feedback come under business communication called as business objects. Questionnaire was sent to printing companies which are having either pre-press, press and post-press or any combination facilities. Their products varied from small labels to newspapers. Research area was limited to commercial printing only. Nine companies replied to questionnaire. 7.1 Background information of companies Work areas of the companies Other Work Area Post-press Press Pre-press Total responded companies Figure 32. Work area of company Products printed by companies Products Other Stickers Posters Stationary Packaging Advertise News Periodical Book Total responded companies 5 6 Figure 33. Products of responded companies 55

59 Employee strength Total number of Companies Number of employees Figure 34. Employee strength in responded companies Summary All the respondent companies have press department. Seven out of nine companies have pre-press and post-press facilities. 66% of the companies are in advertisement printing and some of the companies print labels and stickers, book, poster, stationary, newspapers, packaging and periodicals. Five out of nine companies are having employee strength from 0 to 100. Four out of nine companies are having employee strength from 101 to 250 plus Channel to get RFQ Customers are mainly using (55%) and telephone (24%) for sending request for quote to printshop. Customers are also using post, internet and fax to send RFQ. Average 5.6% 5.6% 24% Ph 55% 1.8% Fax Post Internet Figure 35. Channel to get RFQ/Order in companies 56

60 7.1.2 Channel to get proof approval information Proof approval request/response is received through (35,5%) and post (10%) and also phone and fax. No respondent is using internet to send/receive proof approval. Companies Ph (%) Fax (%) (%) Post (%) Internet (%) Company Company Company Company Company Company Company Company Company 9 - = companies responded positively without giving any percentage Table 4. Channel to get proof approval Channel to delivery instructions Companies use and excel (spreadsheet) to give delivery instructions. Very few customers give delivery instructions by internet and post. 57

61 Companies Ph (%) Fax (%) (%) Post (%) Internet (%) Company Company Company Company Company Company Company Company Company = companies responded positively without giving any percentage Table 5. Channel to get delivery instructions Channel to get Customer feedback Printshops use telephone to get customer feedback. , post and fax is also used to get customer feedback. Some printshops do not archive feedback into the system, some put feedback into the system. 58

62 Companies Ph Fax Post Internet Company 1 Company 2 Company 3 Company 4 Company 5 Company 6 Company 7 Company 8 Company 9 = companies responded positively without giving any percentage Table 6. Channel to get customer feedback 7.2 Key findings from the survey Customers and printshops use more often to communicate for RFQ, Quote, proof approval, delivery instructions and customer feedback. Telephone is also used for communication. Printshops are not taking advantage of Internet for order processing. Very few printshops confirm orders from customers (or approximately 5%). In some cases job comes for rerun and communication regarding proof approval may not take place. Five out of nine printers already have PPF installed in the printshop. Use of PPF mainly depends on the size of the printshop. Printshops having employee strength from 100 to 250 plus have PPF system. PPF is used in press department for machine and ink-key settings. Large printers have MIS system installed in printshop. Some printers did not use all features of MIS system. Printshops create quote and enter customer requests manually into the system. Printers receive delivery instructions on Excel (spreadsheet) from customers. Many respondents do not have clear idea about JDF or how it can help in business and in which areas it can be effective. Printshops are keen for system integration of all departments, especially production which will also help in accurate billing. Archiving business information such as order processing, billing, proofing and customer feedback is important for printers. Archived order processing and billing information can help printer 59

63 for accurate accounting. Archived job data can help printer in faster machine set up if the same job comes for rerun. Valuable suggestions from customer feedback can help improving quality or improving smooth job processing. 7.3 Customer and printshop communication problems Customer Request for quote Quote Purchase Order Order confirmation Delivery status /Invoice Proof approval request Proof approval response Printshop Sales person Imposition and Planning Pre-press Job status request Job status response Packing instructions Packing confirmation Press Post-press Delivery Figure 36. Customer Printshop Communication Some of the problems found in communication between customer and printshop are Request for Quote Companies receive RFQ mainly by or phone. Sales person or concerned person has to write down customer requirements regarding product in detail. Sales person should be knowledgeable enough about production process so that required product details can be asked to customer. If information given by the customer lacks one has to call again the customer. When customer clearly mentions what to print and gives minimum product details precisely, sales person does not need to contact customer again. 60

64 Quote Quote is sent by . Quote information can be made with the help of MIS if printer already has the system. If customer changes the order, printshops either make changes manually in original quote or make a new quote. Purchase order Customer sends purchase order by , post or fax. Unless printshop receives purchase order, printshop can not send order confirmation. If purchase order is changed from the original quote, printshop may not get the changes. It may take time to send new quote based on the new purchase order. Order Confirmation Printshops mainly depend on or telephone to get order confirmation. Very few printshops send order confirmation after the quote is accepted by the customer. If customer changes his order, it is communicated by phone. In conventional process sales person has to write down the new change of order separately with out any reference to original request or order. In many cases printshops do not keep record for change of order. Sometimes printer does not feed the new changes into the system and has to communicate changes with production department orally. Proof approval is used more to receive proof from customer. Post is also used for proof delivery. Printshops accept approved proofs in the form of PDF to avoid changes later. It can save time for make ready or follow-ups. Job status Sales person gets to know job status mainly from production department, customer service orally and sometimes from the system. Precise job status can not be received. Customer contacts sales person or customer service if needed. Delivery or packaging instructions and status of delivery Delivery or packaging information is sent by . Excel is used to send delivery information. Once delivery is complete, printshop send confirmation through phone, fax or . Customer feedback Customer feedback is job specific in many cases unless printshop ask feedback for every job. Telephone is used to get feedback. Only one concerned person knows the feedback. In weekly meetings feedback is discussed. 61

65 Sometimes communication between customer and printshop is not precise and depends on the sales person. There is great deal of need for the integration of customer with printshop. Unclear or incomplete requests can lead to follow-ups and misinterpretation. Communication can be time consuming which can affect business. JDF can help to make communication precise. Integrating customer with printshop through MIS, customer can feed minimum required job data with interactive form or web browser and submit it to the printshop immediately. Printshop can answer to the request immediately through the same system. Communication between customer and printer can be archived in the server for the future use. There will be no need for manually feeding data into the system and received data is editable as needed. In business transactions, customer as well as printer can get confirmed acknowledgement as both parties can receive messages in time. Printshop can save current market prices of materials in the system and quote can be sent immediately to customer on the basis of current market prices. Current market prices can be handled through management information system if supplier integrates with the MIS.. General feedbacks as well as job specific feedback can be received from the customer. JDF is also supported by print-talk. Print Talk is now managed by CIP4 organization. As JDF is extensive, it is suitable for defining comprehensive job parameters including business objects with accurate data. By encoding precise business information in the intent resource JDF removes ambiguity with respect to job data. With precise data, job processing becomes efficient and make-ready time can be saved. For printshop it is easy to archive customer profile along with job history which can help in rerun of job. With automated JDF workflow, in case of rerun pre-setting process works smoothly. JDF supports PDF and PDF is used to store content data. Content data, job data and process data can be saved in MIS. For the printshops who already have MIS and PPF installed, it is easy to upgrade to CIP4/JDF. With JDF system optimization of the production can be achieved. Main benefits from printshop and customer integration are 1. It saves overall process time and process cost. 2. Makes the business more transparent which increases customer faith. 3. Round the clock availability to take orders from customers without any physical presence. 62

66 8 TESTING OF JDF FILES By the time when thesis started in May 2005, CIP4 has released JDF 1.2 version. In September 2005, CIP4 published new version JDF 1.3. JDF intent resource defines elements used in describing the product in order management such as RFQ. In intent resource many of the elements are optional, in the sense that if customer does not specify additional information regarding the product in RFQ, JDF takes default value for that particular element and if specific feature of that product is not given then that feature is not needed. In defining business objects in intent resource using JDF, business metadata is placed between <NodeInfo> / <BusinessInfo> </BusinessInfo>/</NodeInfo>. PrintTalk Example <PrintTalk xmlns=" <Header> Standard CXML header </Header> <Request> <RFQ AgentDisplayName="Mike Peterson" AgentID="Mike" BusinessID="RFQ_ID" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "> <jdf:jdf xmlns:jdf=" ID="ScreenTest" JobID="ScreenJob" Status="Waiting" Type="Product" Version="1.2"> <jdf:nodeinfo LastEnd=" T06:02:42+01:00"/> </jdf:jdf> </RFQ> </Request> </PrintTalk> Equivalent pure JDF Example <JDF xmlns=" ID="ScreenTest" JobID="ScreenJob" Status="Waiting" Type="Product" Version="1.2"> <NodeInfo LastEnd=" T06:02:42+01:00"> <BusinessInfo> <pt:rfq xmlns:pt=" AgentDisplayName="Lara Garcia- Daniels" AgentID="Lara" BusinessID="RFQ_ID" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "/> </BusinessInfo> </NodeInfo> </CustomerInfo> </AuditPool> </JDF> </ResourceLinkPool> </ResourcePool> </JDF> RFQ business object RFQ business object in BusinessInfo Node JDF node JDF Node 63

67 Sample Request for Quote To Address: Sutra Printers 6 Date: Kitarakuja, 22 Helsinki Phone: Fax: RFQ_ID005 3 Contact Person: Gary Ackerman. 5 gary.ackerman@sutraprinters.com Customer ID Sutra_55 Job Name and Job ID Brochure, 2 ABC_ Size mm 9 Inks 4 color 10 Paper Glossy, 250 gsm 8 Print Quantity 3000 Pages 2 pages Date of delivery Language English Content data type PDF file 7 Binding Left side, adhesive 11 Additional Information Delivery directly to company s customers.12 Preferred by Post13 64

68 Deatils of the Company: Company name Business Area ABC Consultants Job consultant Street address Jämerantaival 7C, 361 Post Espoo Phone Contact Person Jim Anderson 65

69 QUOTE "Sutra Printers" Kitarakuja, 22 Helsinki Phone: Fax: DATE: EXPIRATION DATE To Jim Anderson ABC consultants Jämerantaival 7C, 361 Espoo Customer ID [ ABC_23BC ] Quantity Description Unit price Line total 3000 Brochures Delivery charges Total 700 Quotation prepared by: Gary Ackerman. This is a quotation on the goods named, subject to the conditions noted below: (Describe any conditions pertaining to these prices and any additional terms of the agreement. You may want to include contingencies that will affect the quotation.) To accept this quotation, sign here : Thank you for your business! 66

70 Sample JDF_RFQ file:- <? xml version= 1.0 encoding= UTF-8?> <JDF ID="ID_ _173004" Type="Product" Status="Waiting" Version="1.2" xsi:type="product" JobPartID="1" JobID="ABC_0212" MaxVersion="1.2" 1 ICSVersions="Base_L1-1.0" 2 DescriptiveName="Brochure"xsi:schemaLocation=" 1 <!--JDF ID is unique ID for the RFQ message--> <NodeInfo> <BusinessInfo> 3 <pt:rfq BusinessID="RFQ_ID005" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "/> 4 <Comment>brochure of ABC consultant</comment> </BusinessInfo> Business object RFQ is </NodeInfo> defined in BusinessInfo <CustomerInfo CustomerID="Sutra_55"> node <Contact ID="ID_ " ContactTypes="Customer"> Customer ID <Person JobTitle="Sales Representative" FirstName="Gary" FamilyName="Ackerman" NamePrefix="Mr"> 5 <ComChannel Locator=" " ChannelType="Phone" ChannelUsage="Business" ChannelTypeDetails="Landline"/> <ComChannel Locator=gary.ackerman@sutraprinters.com ChannelType=" "/> </Person> <Company OrganizationName="Sutra Printers"/> 6 <Address City="Helsinki" Region="Uusimma" Street="Kitarakuja 22" Country="Finland" PostalCode="00510"/> </Contact> </CustomerInfo> <!--ResourcePool node specifies the resources required to print 2 page brochure--> <ResourcePool> <Component ID="OutputComponent" Class="Quantity" Status="Unavailable" ComponentType="FinalProduct" DescriptiveName="Brochure"/> <Component ID="ID_ " Class="Quantity" Status="Unavailable" ProductType="Body" ComponentType="PartialProduct" DescriptiveName="Page Section" ReaderPageCount="2"/> </ResourcePool> <ResourceLinkPool> <ComponentLink rref="outputcomponent" Usage="Output" Amount="3000"/> <ComponentLink rref="id_ " Usage="Input" Amount="3000"/> </ResourceLinkPool> <AuditPool> <Created AgentName="Adobe JDFProdDef" TimeStamp=" T17:30:04+02:00" AgentVersion="1.0"/> </AuditPool> JDF Root node with unique ID Contact details of customer Unique component ID of paper required to print Author of JDF file <JDF ID="ID_ " Type="Product" Status="Waiting" xsi:type="product" JobPartID="1.1" DescriptiveName="Page Section"> <ResourceLinkPool> <ComponentLink rref="id_ " Usage="Output"/> 67

71 <ArtDeliveryIntentLink rref="id_ " Usage="Input"/> <MediaIntentLink rref="id_ " Usage="Input"/> <LayoutIntentLink rref="id_ " Usage="Input"/> <ColorIntentLink rref="id_ " Usage="Input"/> Input resources <BindingIntentLink rref="id_ " Usage="Input"/> described in <DeliveryIntentLink rref="id_ " Usage="Input"/> ResourcePool node </ResourceLinkPool> <ResourcePool> <ArtDeliveryIntent ID="ID_ " Status="Unavailable" Class="Intent"> 7 <ArtDelivery ArtDeliveryType="DigitalFile"> <Method DataType="NameSpan" Preferred=" "/> </ArtDelivery> </ArtDeliveryIntent> <MediaIntent ID="ID_ " Class="Intent" Status="Available" DescriptiveName="paper for brochure"> <MediaType DataType="EnumerationSpan" Preferred="Paper"/> <Grade DataType="IntegerSpan" Preferred="1"/> <Weight DataType="NumberSpan" Preferred="250"/> 8 <MediaColor DataType="EnumerationSpan" Preferred="White"/> <StockType DataType="NameSpan" Preferred="Cover"/> <FrontCoatings DataType="EnumerationSpan" Preferred="Glossy"/> </MediaIntent> <LayoutIntent ID="ID_ " Class="Intent" Status="Available" Sides="TwoSidedHeadToFoot"> Layout description <FinishedDimensions DataType="ShapeSpan" Preferred=" "/> 9 </LayoutIntent> <ColorIntent ID="ID_ " Class="Intent" Status="Available"> 10 <ColorStandard DataType="NameSpan" Preferred="CMYK"/> </ColorIntent> <BindingIntent ID="ID_ " Class="Intent" Status="Unavailable"> <BindingType DataType="EnumerationSpan" Preferred="Adhesive"/> <BindingSide DataType="EnumerationSpan" Preferred="Left"/> 11 </BindingIntent> Binding description <DeliveryIntent ID="ID_ " Status="Unavailable" Class="Intent"> <Method DataType="NameSpan" Preferred="Posti"/> <DropIntent> <DropItemIntent Amount="3000"/> <Required DataType="TimeSpan" Preferred=" T15:00:00+02:00"/> Brochure delivery </DropIntent> description <Contact ContactTypes="Delivery" DescriptiveName="Delivery to all 12 customers of ABCconsultant "> <Company OrganizationName="Posti"/> <Address Country="Finland"/> </Contact> </DeliveryIntent> </ResourcePool> </JDF> </JDF> 13 Description of Art delivery Media description Inks required 68

72 Figure 37. Process tree view of RFQ business object Sample JDF_Quote file- <?xml version="1.0" encoding="utf-8"?> <JDF ID="ID_ _173005" Type="Product" xmlns=" Status="Waiting" Version="1.2" xsi:type="product" JobPartID="1" xmlns:xsi=" MaxVersion="1.2" ICSVersions="Base_L1-1.0" DescriptiveName="Brochure" xsi:schemalocation=" <NodeInfo> <BusinessInfo> <pt:quote xmlns:pt=" BusinessID="QUOTE_ID" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "/> <Comment>Quotation for brochure of ABC consultant</comment> </BusinessInfo> </NodeInfo> <CustomerInfo CustomerID="ABC_23BC"> <Contact ID="ID_ " ContactTypes="Customer"> <Person JobTitle="Administrator" FirstName="Jim" FamilyName="Andersson" NamePrefix="Mr"> <ComChannel Locator=" " ChannelType="Phone" ChannelUsage="Business" ChannelTypeDetails="Landline"/> <ComChannel ChannelType=" "/> </Person> <Company OrganizationName="ABC Consultants"/> <Address City="Espoo" Region="Uusimma" Street="Jämerataival 7C 361" Country="Finland" PostalCode="02150"/> </Contact> </CustomerInfo> <ResourcePool> <Component ID="OutputComponent" Class="Quantity" Status="Unavailable" ComponentType="FinalProduct" DescriptiveName="Product"/> <Component ID="ID_ " Class="Quantity" Status="Unavailable" ProductType="Body" ComponentType="PartialProduct" DescriptiveName="Page Section" ReaderPageCount="2"/> </ResourcePool> <ResourceLinkPool> <ComponentLink rref="outputcomponent" Usage="Output" Amount="3000"/> <ComponentLink rref="id_ " Usage="Input" Amount="3000"/> </ResourceLinkPool> <AuditPool> Requested and expiery date Business object Quote is defined 69

73 <Created AgentName="Adobe JDFProdDef" TimeStamp=" T17:30:04+02:00" AgentVersion="1.0"/> </AuditPool> <JDF ID="ID_ " Type="Product" Status="Waiting" xsi:type="product" JobPartID="1.1" DescriptiveName="Page Section"> <ResourceLinkPool> <ComponentLink rref="id_ " Usage="Output"/> <ArtDeliveryIntentLink rref="id_ " Usage="Input"/> <MediaIntentLink rref="id_ " Usage="Input"/> <LayoutIntentLink rref="id_ " Usage="Input"/> <ColorIntentLink rref="id_ " Usage="Input"/> <BindingIntentLink rref="id_ " Usage="Input"/> <DeliveryIntentLink rref="id_ " Usage="Input"/> </ResourceLinkPool> <ResourcePool> <ArtDeliveryIntent ID="ID_ " Status="Unavailable" Class="Intent"> <ArtDelivery ArtDeliveryType="DigitalFile"> <Method DataType="NameSpan" Preferred=" "/> </ArtDelivery> </ArtDeliveryIntent> <MediaIntent ID="ID_ " Class="Intent" Status="Available" DescriptiveName="paper for brochure"> <MediaType DataType="EnumerationSpan" Preferred="Paper"/> <Grade DataType="IntegerSpan" Preferred="1"/> <Weight DataType="NumberSpan" Preferred="250"/> <MediaColor DataType="EnumerationSpan" Preferred="White"/> <StockType DataType="NameSpan" Preferred="Cover"/> <FrontCoatings DataType="EnumerationSpan" Preferred="Glossy"/> </MediaIntent> <LayoutIntent ID="ID_ " Class="Intent" Status="Available" Sides="TwoSidedHeadToFoot"> <FinishedDimensions DataType="ShapeSpan" Preferred=" "/> </LayoutIntent> <ColorIntent ID="ID_ " Class="Intent" Status="Available"> <ColorStandard DataType="NameSpan" Preferred="CMYK"/> </ColorIntent> <BindingIntent ID="ID_ " Class="Intent" Status="Unavailable"> <BindingType DataType="EnumerationSpan" Preferred="Adhesive"/> <BindingSide DataType="EnumerationSpan" Preferred="Left"/> </BindingIntent> <DeliveryIntent ID="ID_ " Status="Unavailable" Class="Intent"> <Method DataType="NameSpan" Preferred="Posti"/> <Pricing Item="Brochure" Price="600.00"> <Comment>Price including delivery charges</comment> </Pricing> <DropIntent> <DropItemIntent Amount="3000"> <Pricing Item="Delivery" Price="100.00"/> </DropItemIntent> </DropIntent> <Contact ContactTypes="Delivery" DescriptiveName="Delivery to all customers of ABCconsultants by posti"> Delivery description <Company OrganizationName="Posti"/> <Address Country="Finland"/> </Contact> </DeliveryIntent> </ResourcePool> </JDF> </JDF> Delivery method Quoted price for printing brochure 70

74 Figure 38. Process tree view of QUOTE business object Sample JDF_Purchase Order - <?xml version="1.0" encoding="utf-8"?> <JDF ID="ID_ _173006" Type="Product" xmlns=" Status="Waiting" Version="1.2" xsi:type="product" JobPartID="1" xmlns:xsi=" MaxVersion="1.2" ICSVersions="Base_L1-1.0" DescriptiveName="Product" xsi:schemalocation=" <NodeInfo> <BusinessInfo> PurchaseOrder Object defined <pt:purchaseorder xmlns:pt=" BusinessID="PO_ID" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "/> <Comment>Quotation for brochure of ABC consultant</comment> </BusinessInfo> </NodeInfo> <CustomerInfo CustomerID="Sutra_55"> <Contact ID="ID_ " ContactTypes="Customer"> <Person JobTitle="Sales Representative" FirstName="Gary" FamilyName="Ackerman" NamePrefix="Mr"> <ComChannel Locator=" " ChannelType="Phone" ChannelUsage="Business" ChannelTypeDetails="Landline"/> <ComChannel Locator="gary.ackerman@sutraprinters.com" ChannelType=" "/> </Person> <Company OrganizationName="Sutra Printers"/> <Address City="Helsinki" Region="Uusimma" Street="Kitarakuja 22" Country="Finland" PostalCode="00510"/> </Contact> </CustomerInfo> <ResourcePool> <Component ID="OutputComponent" Class="Quantity" Status="Unavailable" ComponentType="FinalProduct" DescriptiveName="Product"/> <Component ID="ID_ " Class="Quantity" Status="Unavailable" ProductType="Body" ComponentType="PartialProduct" DescriptiveName="PageSection" ReaderPageCount="2"/> </ResourcePool> <ResourceLinkPool> <ComponentLink rref="outputcomponent" Usage="Output" Amount="3000"/> <ComponentLink rref="id_ " Usage="Input" Amount="3000"/> </ResourceLinkPool> <AuditPool> <Created AgentName="Adobe JDFProdDef" TimeStamp=" T17:30:04+02:00" AgentVersion="1.0"/> </AuditPool> <JDF ID="ID_ " Type="Product" Status="Waiting" xsi:type="product" JobPartID="1.1" DescriptiveName="Page Section"> 71

75 <ResourceLinkPool> <ComponentLink rref="id_ " Usage="Output"/> <ArtDeliveryIntentLink rref="id_ " Usage="Input"/> <MediaIntentLink rref="id_ " Usage="Input"/> <LayoutIntentLink rref="id_ " Usage="Input"/> <ColorIntentLink rref="id_ " Usage="Input"/> <BindingIntentLink rref="id_ " Usage="Input"/> <DeliveryIntentLink rref="id_ " Usage="Input"/> </ResourceLinkPool> <ResourcePool> <ArtDeliveryIntent ID="ID_ " Status="Unavailable" Class="Intent"> <ArtDelivery ArtDeliveryType="DigitalFile"> <Method DataType="NameSpan" Preferred=" "/> </ArtDelivery> </ArtDeliveryIntent> <MediaIntent ID="ID_ " Class="Intent" Status="Available" DescriptiveName="paper for brochure"> <MediaType DataType="EnumerationSpan" Preferred="Paper"/> <Grade DataType="IntegerSpan" Preferred="1"/> <Weight DataType="NumberSpan" Preferred="250"/> <MediaColor DataType="EnumerationSpan" Preferred="White"/> <StockType DataType="NameSpan" Preferred="Cover"/> <FrontCoatings DataType="EnumerationSpan" Preferred="Glossy"/> </MediaIntent> <LayoutIntent ID="ID_ " Class="Intent" Status="Available" Sides="TwoSidedHeadToHead"> <FinishedDimensions DataType="ShapeSpan" Preferred=" "/> </LayoutIntent> <ColorIntent ID="ID_ " Class="Intent" Status="Available"> <ColorStandard DataType="NameSpan" Preferred="CMYK"/> </ColorIntent> <BindingIntent ID="ID_ " Class="Intent" Status="Unavailable"> <BindingType DataType="EnumerationSpan" Preferred="Adhesive"/> <BindingSide DataType="EnumerationSpan" Preferred="Left"/> </BindingIntent> <DeliveryIntent ID="ID_ " Status="Available" Class="Intent"> <Comment>Price including Tax</Comment> <Pricing Item="Total Amount" Price="854.00"/> <Contact ContactTypes="Delivery" DescriptiveName="Delivery to all customers of ABCconsultant by posti"> <Company OrganizationName="Posti"/> <Address Country="Finland"/> </Contact> <DropIntent> <DropItemIntent> <Pricing> <Payment> <PayTerm>10 percent of total payment, net payment within 30 days</payterm> </Payment> </Pricing> </DropItemIntent> </DropIntent> </DeliveryIntent> </ResourcePool> </JDF> </JDF> Payment term is described in details 72

76 Figure 39. Process tree view of Purchase order business object Sample JDF_Invoice - <?xml version="1.0" encoding="utf-8"?> <JDF ID="ID_ _173007" Type="Product" xmlns=" Status="Completed" Version="1.2" xsi:type="product" JobPartID="1" xmlns:xsi=" MaxVersion="1.2" ICSVersions="Base_L1-1.0" DescriptiveName="Brochure" xsi:schemalocation=" <NodeInfo> <BusinessInfo> <pt:invoice xmlns:pt=" BusinessID="RFQ_ID" Currency="EUR" Estimate="false" Expires=" T " RequestDate=" T "/> <Comment>Invoice to ABC consultant</comment> </BusinessInfo> </NodeInfo> <CustomerInfo CustomerID="ABC_23BC"> <Contact ID="ID_ " ContactTypes="Customer"> <Person JobTitle="Administrator" FirstName="Jim" FamilyName="Andersson" NamePrefix="Mr"> <ComChannel Locator=" " ChannelType="Phone" ChannelUsage="Business" ChannelTypeDetails="Landline"/> <ComChannel Locator="jim.andersson@abcconsultants.com" ChannelType=" "/> </Person> <Company OrganizationName="ABC Consultants"/> <Address City="Espoo" Region="Uusimma" Street="Jämerantaival 7C 361" Country="Finland" PostalCode="02150"/> </Contact> </CustomerInfo> <ResourcePool> <Component ID="OutputComponent" Class="Quantity" Status="Complete" ComponentType="FinalProduct" DescriptiveName="Product"/> <Component ID="ID_ " Class="Quantity" Status="Complete" ProductType="Body" ComponentType="PartialProduct" DescriptiveName="Page Section" ReaderPageCount="2"/> </ResourcePool> <ResourceLinkPool> <ComponentLink rref="outputcomponent" Usage="Output" Amount="3000"/> <ComponentLink rref="id_ " Usage="Input" Amount="3000"/> </ResourceLinkPool> <AuditPool> <Created AgentName="Adobe JDFProdDef" TimeStamp=" T17:30:04+02:00" AgentVersion="1.0"/> </AuditPool> <JDF ID="ID_ " Type="Product" Status="Completed" xsi:type="product" JobPartID="1.1" DescriptiveName="Page Section"> 73

77 <ResourceLinkPool> <ComponentLink rref="id_ " Usage="Output"/> <DeliveryIntentLink rref="id_ " Usage="Input"/> </ResourceLinkPool> <ResourcePool> <DeliveryIntent ID="ID_ " Status="Complete" Class="Intent"> <DropIntent> <Contact ContactTypes="Delivery" DescriptiveName="Delivery to all customers of ABCconsultant by posti"> <Company OrganizationName="Posti"/> <Address Country="Finland"/> </Contact> <DropItemIntent> <Pricing Item="Total Amount" Price="854.00"/> </DropItemIntent> </DropIntent> </DeliveryIntent> </ResourcePool> </JDF> </JDF> Total amount including delivery charges Figure 40. Process tree view of invoice business object 74