In a JDF workflow, the management information system (MIS) sends you a JDF file that represents the job ticket and specifies the imposition requirements in its stripping data. Incoming JDF files can contain enough product intent to autogenerate the Press Runs List via template-signature matching or creation, and you can add or edit details as needed.
The currently loaded profile determines the type of automation that is applied when a JDF file is opened, based on the JDF tab settings in the Preferences dialog box.
When you open an MIS JDF file, the software immediately examines the JDF data (stripping parameters) and attempts to resolve the requirements using a specific sequence, depending on the profile.
Manually matching the source JDF values
You can manually edit the product intent to match the JDF values when:
- The profile is configured for matching only, and no suitable template is found.
- The profile is configured for signature matching or creation, and the JDF data is not complete.
- The original intent needs to be updated with last-minute change requests.
When the product intent is fully defined, you can generate the Press Runs List.
When structural changes are needed
When necessary, you can make structural changes, such as to accommodate an increased page count. Before proceeding, determine whether the customer service representative will send you new or updated JDF data to replace this job, or whether you will change the job manually. The Preps software can manage stock introduced by a JDF without having it added to the stock list. You can edit the on-the-fly stock property, and have it written back to the JDF.
You can manually specify the new product intent in the Assembly view, and create the additional press-run layout in the Press Runs view. Although the printed result might be correct, the new press run will have no association with the original JDF stripping parameters, and the JDF output will contain an unrequested press run.
Tips for optimal results
The JDF data that you receive can vary in structure and content between MIS systems and jobs. Even when the data is very comprehensive, mismatched properties can result if the profile requires several mandatory criteria with a low tolerance for differences.
And even if the JDF data and the profile have minimal requirements and the press-run layouts are easily autogenerated, the impositions might not be suitable. In that case, you might need to compare the JDF values of nonmandatory settings with the autoselected values, and then manually edit the settings to match more of the JDF values.
Here are some suggestions for achieving better results:
- Store suitable JDF settings in custom profiles, so that the generated impositions will be compliant with downstream systems.
- Configure additional profiles, and switch between them as needed.
- For auto signature matching, maintain a well-organized collection of layout resources (templates).
- For more accurate matching, create a profile that uses all or most of the Matching Criteria and a fairly strict Match Tolerance.
- For easier matching (with the risk of unsuitable results), use fewer Matching Criteria and a more lenient Match Tolerance.