Enfocus Community

What method do you guys recommend for naming and keeping a log of what jobs go into an imposed layout?

Right now we have been moving away from manual setups and doing more with Switch and Griffin Auto.

However, the layouts that come out of Griffin I have named with a date and the 5-digit identifier Switch generates.

This has caused some (admittedly justified) complaining from people in the shop.

Before, they had:

29806 - Acme Co. Name Tags.pdf

and

29806 - Acme Co. Name Tags-CUT.pdf



but now with things moving through Griffin they have:


Plastic-Name-Tag-Layout-2025-06-25-05UTN.pdf

and

Plastic-Name-Tag-Layout-2025-06-25-05UTN-CUT.pdf



I can understand why they would like a more readable naming convention.

However, it's hard to do this because now with Griffin it imposes all different tags and items from multiple jobs. Rarely is a layout ever just from one customer anymore.

Also this does make it more difficult to go back and see what job was printed when. I can't really search for them.

I was thinking of grabbing job names from the files submitted to the Switch imposition flow and adding them to private data, then throwing on into the filename just so they have something to go on.

Is there a best practice in this case?

Thanks for any help!

It sounds like it might be a good idea to take a step back and rethink the workflow. Software delivers the best results when you first sketch out the workflow you want, before building it in Switch. A great starting point is to involve the press operators and ask what information they need in the file names or logs to do their jobs effectively.

Often, the best approach is to ”sketch the workflow in reverse”, start by defining the end result you want (for example, file names, imposition summary, logs, traceability) and then work backwards to see how that information can be collected and carried through the entire flow.

There are many possible ways to solve this issue, but it’s hard to give specific advice because your problem description is a bit too vague.

What information do the operators really need to see in the file name?

What information could instead live in logs or production systems?

Do you need to track individual jobs, combined layouts, or both?

Once you have clarified your needs, you can build a Switch flow that strikes the right balance between automation and clarity for your team.

Totally agree with Magnus,

When I was working in print-on-demand (POD), I found with my press operator that the best aproach is to made sure that file names reflected the production order, to make processing easier on press software.

For example, I used a structured naming format like this:

[TAG]_[YYYY-MM-DD]_[size]_[weight]_[batch]

Examples:

With this in mind, with a simple sort, you'll be able to see priority

Ok, this makes sense.

I've already implemented Magnus' suggestion and opened up a dialogue with each concerned party, with the goal of building a flow from the ground up with all the desired functionality.

Some things I hadn't considered have been brought up, so it's already been fruitful.

I'm not sure I'll be able to actually do all the things on the various "wish lists" I've received, but I've been able to bang out a list of desired features, and now the owners are deciding what is the top priority.

Thanks guys for the responses.