From a user perspective can someone tell me is Apogee as good as Prinergy. What are the differences?
Thanks
We are currently using ApogeeX version 5, and have been Apogee users since the beginning, over a decade now. 13 years I think.
After this much time, the differences are less than once upon a time. Both workflows are based on Adobe technology, with APPE renderers, which of course consume native PDF, transparency and all. That switch in technology was the real turning point, and at last, put an end to the cart before the horse situation introduced by Illustrator 9 and the then new transparency features. With a workflow that uses an APPE renderer rather than CPSI, that transparency stuff is business-as-usual. Between that and Adobe in-rip trapping, most jobs are fire and forget.
That is the most important thing to consider about any workflow -- is it still PostScript? Apogee and Prinergy are not, so both qualify for a serious look. Fuji has a new one I believe, but the rumor is it's Xitron (not a problem, just nothing new, though they call it new tech). Others like RamPage and the ilk (clinging to CT/LW, if they still are), and non-Adobe clone technology, I would not recommend to any prospective buyers. Once you've used a true PDF-all-the-way workflow, based on Adobe tech, you'll understand.
As for differences between ApogeeX and Prinergy, I couldn't say all of them since I live in the Agfa world, but I have people working for me who have used Prinergy (and RamPage and others) and they say ApogeeX is better. I can only take their word for it. One thing I'm pretty sure is that Prinergy lacks the Preps Template Manager feature of ApogeeX. From what I understand (users please clarify, I invite it), when using Prinergy, the template and a complete dummy job is prepared in Preps, then sent to the workflow as a PJTF. This is the same situation for ApogeeX users who do not purchase the Preps Template Manager option. For those with the option (like us), that PJTF double-work is not required. Within the imposition task processor is a dialog laid out like Preps to select templates and signatures. For any user of Preps, they see the window and say, "Oh, I get that. I've seen all that before." So the option makes the learning curve easier, and in the end, is far more productive than the PJTF solution of making a dummy job just to not do it, and instead feed it's make-up to the workflow. I never did get how that was supposed to be "innovative" and a more efficient way of doing things. Not every bright idea is better, in all cases.
ApogeeX can read Preps templates, but that's where it ends. Under the hood, ApogeeX uses a program formally known as "Orgami." From what I understand, anyway, Agfa bought it, and that code does all the work exactly as Preps would, just tens times as fast. Particularly, how I've setup my system, using two satellites and the server each running two imposition task processors, giving me six total, so six flats are imposed simultaneously. That's productive. Large jobs are imposed in minutes, if not seconds. At any rate, it's all client-server, meaning there are no gas-gauges going past while anything is processed locally. The server (and satellites if added for scaling) do all the work. I'm fairly confident this aspect is no different with Prinergy, and is how all modern workflows should operate.
The best thing is try a job in both workflows. If you're ever in Portland, I'll give you a demo of ApogeeX. Bring a tough job and watch. Just call ahead.