File Formats
Internal data in the Prinect Manager are exchanged as "JDF" (Job Document Format) and as "JMF" (Job Messaging Format) documents. These formats are based on "XML" (Extended Markup Language) in a form especially designed for prepress. Alongside the job JDF data, the XML format is also used for the data that is required for internal system administration. So the engines, for example, have configuration files in XML format. The templates for sequences or sequence groups are also saved as XML files. XML files are also used for resources such as printing materials or sheet layouts. The JMF format is used for information transfer within the Prinect system.
Note: As of Prinect version 2015, the JDF formats will be filed in a binary structure for performance reasons. Converters are available for converting these binary formats back to XML for analysis purposes.
An MIS system connected to the Prinect Manager, for example, the Prinect Business Manager, provides the job data as JDF files. These JDF files are transmitted to the Prinect Manager via a JDF import interface.
In prepress, certain data, e.g. ink zone control, can be created as CIP4-PPF files and modified in the whole workflow and finally processed by the press. The CIP4 Print Production Format (PPF) is defined and updated by the CIP4 group (www.cip4.org). PPF files are transmitted to the Prinect Manager via a PPF import interface.
The Prinect Manager implements in full scope the concept of the "Job Definition Format" (JDF) defined by the CIP4 consortium as a pressroom workflow system.
This means that, with the exception of the actual content (documents, images), all data belonging to a job is managed in a JDF file. As soon as a new job is defined, a JDF file is generated. All processing steps defined for this job are recorded in the JDF file.
In order for a processing step to be performed by an engine, the corresponding section of the job JDF file is sent to the engine. Once the processing step is complete, this is registered with a comment in the job JDF file. This procedure is then repeated for the next processing step with the corresponding engine and so on...
The JDF file belonging to the job acts as a kind of "information pool", whereby each engine which receives information performs its respective task and documents this in the JDF file. This continues until all defined steps have been performed and job processing is finished. All actions are registered in the job JDF file and can be viewed at any time as a log. In this way, you can have optimal control of the entire workflow.
Communication between the individual engines and, for example, the Prinect Cockpit is regulated by a precisely defined protocol - the "Job Messaging Format" (JMF). The JMF protocol allows network-wide and cross-platform communication.
Since the Job Definition Format and the Job Messaging Format conform to vendor-neutral standards, you can in principle also connect any products from other manufacturers that follow the JDF concept to the Prinect Manager system.
The JDF concept encompasses the entire production process, from collection and management of the customer data through the prepress area and printing to finishing.
The master data store allows central management of master data for the entire Prinect system. Master data is information that can be used at several points in the Prinect workflow. Examples of master data are:
•Customer data
•Printing Materials
•Colors
If you enter customer data (name, address, contact, etc.) in the Prinect Business Manager, for example, this data can be imported into the Master Data Store. When creating a new job, you can select the data from the pool of customers defined in the master data store. This helps avoid redundancies and reduces the number of potential errors.
The JMF Messaging service centrally manages all messages which are exchanged using the Job Messaging Format (JMF) in the Prinect system. This speeds up the flow of messages in the Prinect system. In addition, a log can be made of the messages and they can be checked.
The JMF format defines communication between the workflow participants in the Prinect system.
•Error and event messages
•Engine and process status (progress)
•Queue management
Other functions are:
•All Prinect Cockpits within a Prinect system can only access the JDF job data via the message store. If changes are made to a job at one point, these changes are then visible throughout the Prinect system.
•Checking the access rights for jobs
If a user wishes to access an existing job, the JMF storage checks whether the user has the necessary permissions.
Temporary storage of job attributes
Attributes that can be seen in the job list of the Prinect Cockpit are stored temporarily. This accelerates the flow of messages in the Prinect system because not all the engines involved have to be queried when it comes to displaying or updating a job list. Only the buffered data are used for this. Since each engine transfers the current job status to the JMF messaging service, the temporarily stored information is always up-to-date.
•The temporary storage allows you to search for jobs using specific attributes.