Forum

[almaink]

Should you ROOM or NORM?

This has to do with the RIPing (Raster Image Processing) process. ROOM is RIP once output many. This requires RIPing early in the process. In most cases, however, RIPing has to happen several times in the course of the production process. RIP for proofing, RIP for film or plate making, re-RIP for corrections and plate remakes. By RIPing once early in the process you have no room for error and little flexibility. The need for re-RIPing is unavoidable, even if the slightest change is required.

In the ROOM workflow even if you avoid having to re-RIP, you need a great deal of storage capacity for rasterized files and complex data organization.

The only way to minimize storage capacity and maximize automation is to output a proof just before the last RIPping. This way you will know the file is OK and will not need to be RIPed again. In comparison with the costs of remaking film and/or plates, the extra proof is insignificant.

More recent workflow solutions are based on the NORM concept — normalize once, render many. Such systems work with platform-independent master files — workflow-optimized PDF files. Because they are generated at the start of the workflow, yet remain open, the same file can be used on different output systems as a proof, film, plate or Internet file. Changes can still be made. This open approach saves valuable work time and provides a previously unattainable degree of flexibility.

This process also lets you automate a number of parameters, such as imposition, trapping, screening or proofing using job tickets. Job tickets accompany the job through the various processing stages, greatly reducing the possibility of errors. The NORM concept provides the greatest productivity and security.