Automation changes who does what on the press floor
# Automation changes who does what on the press floor The job sat in a list called review, and the review list had nobody's name on it. It was a short carton run, under the quantity that sends work to the digital press, on a board the digital press had fed before. Friday morning the
Automation changes who does what on the press floor
The job sat in a list called review, and the review list had nobody's name on it. It was a short carton run, under the quantity that sends work to the digital press, on a board the digital press had fed before. Friday morning the screen showed it released. The digital operator started. By late morning he had a sheet, and the brand green was the same wrong green as the trial three weeks earlier. He parked the job the way he had been taught to park a job the press couldn't close. He pressed exception. The sheet stayed on the bench with a pencil line under the bar. The ticket left his queue.
Across the hall the offset board didn't show the job at all. Prepress hadn't plated it, because plating followed the route, and the route had said digital. The day lead on offset felt the small relief of a schedule that had already been decided. At the break the digital operator said the green was in review. He thought review meant a person. It had meant a person, before the workflow went in. She used to walk both queues at mid-morning and catch the oddities. After go-live that walk was described as the old way. Her hours moved to estimating, which was where the plant was short, because the system was now doing the routing. The list remained. It didn't call anyone.
There were three jobs on it by the afternoon. This carton. A file whose dieline had failed preflight. A reprint with no colour aim stored against it. Three exceptions, and a handover at six that happened where handover had always happened, beside the offset console. The day lead said it was in the system. The night lead asked if anything was stuck. He was told no. Stuck, in that conversation, meant stopped on a press. A job in a review list isn't stopped on a press. It's stopped nowhere, which is harder to see, and the offset schedule in front of him was full of work the system had been trusted to choose.
The buyer rang after the office had emptied. They wanted sheets for a packing trial, the short run that had been sold as the easy one. The night lead looked at the offset board, then the digital queue, then the done list. The estimator, still in the car park, remembered her own note. Offset. Spot colour. Don't send this to digital. She had written it on the job and in the mail the buyer had been copied on, after the trial sheet had looked close in the office and wrong beside the pack. The router had never read it. The router read quantity and stock code. Notes are sentences. Rules like fields. The login that could force the job back to offset belonged to the planner, who had left at four. They plated it on Saturday from a standing start, with a minder phoned in to mix the spot. The sheets left late. The waste was a digital makeready, a Saturday plate set, and a customer who had been told the workflow made short runs simple.
The ordinary path really does get lighter
Be fair about the ordinary path before you hang the whole Friday on the software. On a job that fits the fields, the new workflow takes real work off real people. Prepress spends less of the morning building the same imposition for the same trimmed size. The digital press receives a file that has already passed the checks you bothered to encode: a picture that's actually there, a bleed, a font that is embedded, a stock code that exists in the library. Offset receives a plate order without someone retyping the colour names from a PDF. The planner doesn't rebuild the day from phone calls. A complete ticket moves, and the moving is the point of the money.
People who still want to touch every ordinary job are often protecting a task. The task felt like care, because for years care and typing were the same hour. They aren't the same hour now. A standard booklet, a known stock, a quantity inside the rule, a preflight that passes: let it go. The skill has moved. It sits in the rule you wrote, and in the exception the rule can't see. If you keep a person in the middle of the easy jobs "just to be sure", you spend the wage on the work the software already does, and you still lose Friday, because that person is busy being sure about the easy ones when the review list fills up.
The hours you get back are genuine. Plants lie to themselves in both directions. One lie is that nothing has changed and every job still needs a craftsman's hands on it. The other lie is that the people are now free, as if the work had evaporated rather than changed shape. Count a week before the workflow and a week after, on the same sort of job mix. You'll see fewer minutes on repeat imposition and on rebuilding lists. You should also see a thicker pile of oddities, arriving later in the day, with less of a story attached, because nobody handled them on the way in. If the oddities aren't thicker, your rules are timid and your people are still doing the routing by hand under another name. If the oddities are thicker and nobody's diary shows time for them, you have spent the saved hours twice.
What the rule took, and what it left
The tasks that leave are the ones you can say as fields. Quantity. Size. Stock code. Colour count. Due time. A preflight result you've defined as pass or fail. The tasks that stay are the ones that break the sentence. A spot the digital press already missed. A board that feeds and still looks wrong under the buyer's light. A dieline that passes because the lines are present, and fails in the hand because the glue flap is short. A customer who approved a proof and then spoke to their own marketing people. Automation doesn't remove those. It concentrates them. The ordinary hours get quieter. The exceptions get denser, and they turn up with less warning.
That concentration is the real change in who does what. The digital operator used to print what planning handed over. Now they print a queue, and they're the first person to discover that a queued job is impossible. That's a new duty, and it isn't written on the old job description. They need a place to put the impossible job that isn't a void, and a name that picks it up before the shift changes. The offset minder used to be asked. Now they aren't asked about the jobs that never arrive, which is a relief, right up until a job should have arrived and the plates aren't made. Silence from the other process isn't the same as a decision you were in.
The planner used to own the route as a list they could defend job by job. Now they own the rules, which is a different craft. A rule is a decision you make once and then suffer in bulk. Writing it wants the estimator in the room, and the minders, and a look at last month's reprints. A rule written by the vendor on install day, from a slide about quantities, will do exactly what Friday did. The estimator owns the promise, and the promise often lives in a note, because the form they were given has no slot for "we already failed this green". Prepress owns the file, and also owns the moment a preflight fail becomes a conversation rather than a red icon. Finishing owns the late discovery that the route was possible and the carton isn't, once the crease, the glue or the varnish shows itself. Somebody has to be able to say, in the middle of the day, that the route was wrong. If that sentence has no home, the queue has become the manager.
The handover failed because the exception was homeless
Nobody in this story was lazy in the way a telling-off needs. The digital operator followed a released status, and when the colour wouldn't close he used the button the training had given him. He wasn't given a person to park the job onto. The day lead heard "exception" and heard a category. Categories don't ring customers. The estimator's note was correct, and it was invisible to the only system that was allowed to choose the press. The night lead asked the question handover is for. He was answered with a status that was true and useless. Saturday happened because Friday's handover confirmed a picture that looked complete if you didn't open the review list.
Look at where they stood. The offset console is a sensible place to hand over a hall that is mostly offset, with a digital press as a side room you remember to mention. It stops being sensible when the risk has moved into a list that console doesn't show. The night lead's attention was on a full board. Full boards feel like the work. An empty-looking digital queue feels like success, even when the missing jobs are sitting in another tab under a word nobody reads aloud. "It's in the system" is an easy sentence because it can't be disproved. The job was in the system. What the sentence retired, without anyone deciding to retire it, was "it's in a person's hand".
You can see the same failure on a quieter week, which is how it becomes normal. A dieline fail sits until Monday because Friday's handover didn't name it. A reprint waits for an aim that lives in a drawer in the office. Each one is small. The plant tells itself the workflow works, because the ordinary jobs flowed, and the ordinary jobs are most of the count. The buyer's phone call is what makes one of the small ones large. By then the person who could have overridden the route has gone home, and the night shift can search, and searching isn't routing. A night minder can mix a spot if you phone them in. They can't invent a permission the software has locked to a day login.
The repair isn't a new slogan about ownership. It's a name on each shift, written where the roster is written, whose work includes opening that list at a set time. One name, and a deputy for holidays, also written. The list is either empty of surprises or each job on it has a next action said out loud: plate it, ring the buyer, send it back, or accept that the proof was a favour and the order isn't yours. "It's in the system" isn't one of the actions. While you're at it, turn the estimator's warning into a field the rule can see. Force offset. Force digital. Ask a person. A sentence in the margin is a diary. A diary doesn't steer.
Overrides should be ordinary and recorded, with a reason, on the job. If an override feels like breaking the system, people will run the rule and wear the reprint rather than be the one who clicked. Count the overrides. A rule that is forced every week isn't a rule you should be proud of. It's a rule that needs the estimator's category added to it. Friday's spot colour was knowable. It had already failed once. The failure of the plant was to leave that knowledge in a place the new process had been built to ignore.
What you can hand the router, and what you still say at six
The router can be handed a quantity, a stock code the digital library actually contains, a due time, and a preflight result you've defined. It can be handed a forced route that a person chose. It can be handed a login, so next month you can see who overrode what. It can't be handed a margin note, an email, a memory of a trial, or the buyer's tone. If those things change the press, they have to become a field or a named task before the shift changes. Otherwise you've automated the easy path, and you've also automated the loss of the warning.
The people change with that boundary. You need fewer hours on ordinary impositions and ordinary lists. You need those hours back on the exceptions, on the rules, and on a handover that stands in front of the list rather than in front of the familiar console. A plant that takes the saved hours and spends them only on more estimates will run this Friday again. The estimate will look tidy. The review list will still have no name. The night lead will still be told it's in the system. The system will be telling the truth. The job will be nowhere, and the packing trial will be waiting on a phone that nobody in the hall is holding.