1
0
-1

In the ideal world, all the presses (and linked prepress jobs) are planned well in advance.

And if there would be change later, MIS would send a ResubmitQueueEntry with all the changes and imposition/plates are recalculated.

But larger printers (with larger jobs/high quantity) may want to change presses last minute (e.g. from one 128 page press, to 2x 64 page presses) when needed. They do not want the resubmit scenario since that requires checking all impositions again, making proofs etc which takes too much time.

They are willing to invest in the extra preparation/costs to create the two scenarios in prepress (and verify imposition/proofs etc) till the last step: platemaking. The final press decision is then very fast and without risks.

Question

Is there a way in JDF to specify these two paralell scenarios into one job?

Having a Product tree and then 2 Production trees linked to the same final output?

Is a bit like versioning but then for the production part imposition/output press.

Putting one graybox on hold using 'Completed' status does not work for the prepress gray boxes since they need to work for both.

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      there are "late binding" JDF solutions available in the market which achieve the desired functionality by applying the correct JDF last minute, rather than having multiple JDF's in the same instance (I haven't listed product as it would be inappropriate in this forum).

      1. Koen Van de Poel

        Hi Martin, technically it is possible to change it last minute with a ResubmitQueueEntry. and that is also the easiest way. Or do you refer to a different way?

        The issue is that these are expensive jobs that may run for a full day or so. Making sure the imposition / proofs are correct, is a painstaking job that can take hours, paper is optimized till the last mm. And only done during the day shift.

        So it is preferred to spend 2x 2 hours checking the proofs/tuning for both scenarios to allow for the last minute decision shift without thinking.

        Creating two separate jobs (another way) is not possible here since the content should be approved / changed in one location only. And the scenario might be for only one part of a job.

      CommentAdd your comment...