Application and Analysis of JDF Based on XML in Printing Digitalization Workflow (3)
We are a big printing company in Shenzhen China . We offer all book publications, hardcover book printing, papercover book printing, hardcover notebook, sprial book printing, saddle stiching book printing, booklet printing,packaging box, calendars, all kinds of PVC, product brochures, notes, Children's book, stickers, all kinds of special paper color printing products, game cardand so on.
For more information please visit
http://www.joyful-printing.com. ENG only
http://www.joyful-printing.net
http://www.joyful-printing.org
email: info@joyful-printing.net
MIS--body
It takes a lot of effort to coordinate the equipment of different manufacturers. Although the XML language has the ability to encode multiple languages, it is not completely usable. Moreover, the biggest and most important obstacle in the print workflow is the communication between the management information system (MIS) responsible for planning and control work and the production service system responsible for operations. In other words, there is no automatic, coordinated and effective two-way communication between these two aspects. All information enumerating plans, arrangements, processing results, work status and work tracking must be passed from the production department to the MIS, and the MIS can process the information providing instructions.
JDF provides a mechanism for controlling and tracking jobs for natural production systems, while providing information transfer services between MIS and production. During the execution of the job, the results of each process are stored for better tracking. The architecture defines a set of standard information, information formats, and device implementation agreements. It also provides a range of information. The minimum acceptance is zero. In the absence of information selection, the controller must check the JDF to determine the outcome of the process. In addition to the information capacity, JDF includes different audit records for each process, which provides details of the processing plan and actual results. Most devices will choose to support different levels of information capacity.
The device must support the command function. If the device selects the command function, the controller can issue commands to interrupt the current work, restart a job or change the priority of the work. In addition to communication, JDF can also support the controller to collect each process. The execution data is transmitted to the tracking system for use by the job accounting system.
In addition, the entire work information can be transferred to the job accounting system, and the system checks the audit records to determine the cost of the entire job. Each individual project manager selects one or more operations to complete each individual job. At the beginning of the first version, JDF was not related to the equipment provider, which ensured that all providers can use the JDF development system, and no provider is at a disadvantage in the competition.
JDF defines a message architecture that includes message formats, semantics, and communication protocols that JDF drives use to communicate information with systems that control production equipment. System providers also have greater flexibility in choosing messaging mechanisms. JDF provides a good opportunity for MIS integration.
JDF library and simulator
In collaboration with Wuppertal University and Heidelberg, the Java class library for writing and interpreting JDF has been implemented. The library will be published by the CIP4 Alliance as a shared repository for CIP4 members, and agents, controllers and devices based on open source code libraries can be effectively developed.
At the top of the library is a Java-based simulation tool for modeling JDF workflows. This tool was also developed by Wuppertal University. Users can put JDF into the hot folder as the output information of the simulator through the WEB interface. Transferred to different production resources through JDF, these simulation resources can be processed on a single computer or as a distributed system (based on TCP/IP). When the simulator runs discrete events, the generated production status, error information, etc. will be used as work messages. It is sent to the controller and in the future even "real" JDF controllers are integrated into the simulation environment for testing.
As a result, advanced methods for testing new agents, new controllers, and new devices will be implemented so that early testing eliminates the need for a real production environment.
Conclusion and outlook
XML can realize the automatic transmission of data between independent computer systems, thus reducing the amount of work information flow from quotation, live delivery, work order arrangement, production, work order tracking, product delivery, invoicing to collection process. Complete re-entry of data, the purpose of exposing XML and JDF standards is to make workflow integration easier, although we now see that these process-sides are only implemented on a single provider device, such as Heinburg's Prinect, Agfa's Apogee and screen company's TrueNet, etc., JDF is still committed to paving the way for multiple providers to work together, but it is easier said than done.
It is difficult to ensure that all equipment providers will develop devices that adapt to the same JDF, that is, only when both systems are compliant with the JDF standard can they be successfully connected. So, two years ago, Creo announced the formation of Networked Graphic Producion (NGP), the founding members of the organization will be committed to defining, developing, testing and providing JDF-based integration between their systems, in order to ensure better implementation of different providers. The integration, NGP members decided to define and use a standard set of JDF interfaces.
We expect more providers to join the JD Alliance and new products come out, expecting JDF based on XML standards to bring more opportunities to the printing and publishing industry.