Three people called in sick on Wednesday
On Thursday morning a truck was 29 minutes late at a retailer’s dock. A note on the small dependencies inside every week of meat, and how we have started to draw them.
JordanOsakaThree people from the slaughter crew called in sick on Wednesday morning. Nobody thought much of it. The line still ran; it ran at 268 pigs an hour instead of 300, which is the kind of number a supervisor shrugs at and writes on a whiteboard.
On Thursday, at twelve minutes past nine, a refrigerated truck reached a retailer’s distribution centre 29 minutes after its unloading window had closed. The retailer charges €2,500 for a missed window, per load. There were three loads.
It would be tidy to blame the cold. It would not be quite true. With the whole crew at work the truck would still have been fifteen minutes late. The plan had been a little too tight since Monday, and nobody could see it, because the slaughter time lived in one spreadsheet and the dock window in another. The cold only made it worse. Nobody on the truck had done anything wrong, and nobody at the plant had either.
The week is invented, and so are the plant and the retailer. I have seen the shape of it in every meat business I know.
A week of pigs
Take an integrated pork business of a fairly ordinary size: four farms, one slaughter line, a cutting room, a fleet of livestock trucks and another of reefers, and five customers who each want their pork cut differently. About 6,600 pigs go through in a week, in ten batches.
A batch is not a thing that happens on one day. Feed comes off sixteen hours before slaughter. The livestock trucks need a free hour and a driver. The pigs rest in lairage before the line. The line runs one batch after another, 05:00 to 15:00, at whatever speed its crew allows. Every carcass then needs at least sixteen hours in the chiller before it can be cut, and the chillers hold a fixed number. The cutting room cuts to each customer’s specification, and the reefer leaves when cutting is done. At the other end there is a dock window of ninety minutes.
Each of those steps has its own clock and, usually, its own person. The farm manager knows the weights. The slaughter planner knows the line. The transport planner knows the trucks and the windows. Each of them is good at their column. The week happens in the gaps between the columns.
Everything is upstream of something
Our three sick people are a gentle example. In the same invented week, one batch was planned for slaughter 24 hours before its medicine withdrawal period ended, which downgrades the whole batch: about €16,000. Another would reach the line 0.4 kg over its customer’s weight band. A feed silo at one farm would sit empty for 22 hours, with 4,950 pigs waiting under it. Wednesday needed eleven livestock trucks at once and the company had eight. The chillers would be 300 carcasses over capacity on Wednesday night.
Not one of those is a disaster. Together they put about €36,000 at stake, in a week whose margin, with everything going right, is around €9 a pig. Pork does not leave much room for €36,000.
The hard part is not that problems exist. It is that the fixes touch each other. Slaughter the overweight batch on Thursday night instead of Friday morning and it makes its weight band, but now it runs into overtime. Move another batch from Wednesday to Thursday morning and two problems disappear at once, the truck shortage and the chiller overflow, because they were never two problems. They were the same batch, seen from two columns.
A change that is good in one column is often bad two columns later, and the person who made it never sees the second column.
Where the week lives today
In most companies I know, the week lives in a slaughter plan in one spreadsheet, a transport plan in another, a feed order in the feed mill’s system, a crew list on paper, and a great deal of it in the heads of three or four people who phone each other. It works, mostly, because those people are very good. When it fails, it fails like Wednesday: quietly, a day early, in a place nobody was looking.
Nobody can hold all of that in their head. The people who come closest are the ones a company can least afford to lose, and they go on holiday.
One thread per batch
So we have been drawing it. The picture is simple: stages from top to bottom, time from left to right, and every batch as one thread running down through all of them. When everything is on one picture, a dependency stops being a phone call and becomes something you can see. Here is our Wednesday, cut down to one batch and two days.
Late delivery€7,500 at riskFixedOn time
The plan was already tight, and on Wednesday three of the slaughter crew are off sick, so the line runs at 268 pigs an hour, not 300. B05 still needs its 16 hours in the chiller, then cutting, then four hours on the road. It reaches Brava 29 minutes after its window closes.
Suggested fixSlaughter B05 at 05:00 instead of 06:00. The first hour of the shift is free, and nothing else moves.
In the full version every batch is on the screen at once, all ten of them. Hover over one and its thread lights up from the farm to the dock. Drag a slaughter slot and everything below it moves with it: the chillers fill or empty, the trucks re-book, the crew sheet changes, the money is counted again. Under the picture sits a list of what is wrong, sorted by how much it costs.
You can try the whole week for yourself in the pork example. The companies are invented and the numbers are made up, but they are made up carefully: prices, line speeds, chill times and truck sizes are close to what the trade actually runs on.
The part the AI does
For every problem on the list, the software looks for a way out. It tries moves: a batch an hour earlier, two orders swapped, a truck booked, a delivery of feed brought forward. For every move it runs the whole week again, not just the part that hurt, because the point is to catch the fix that solves one problem and starts another. Then it writes down the move it would make, in a sentence, with what it gains, what it clears, and what it adds.
It does not apply anything. A person reads the sentence and presses Apply, or does not. That is not modesty. The software does not know that the cutting room foreman would rather not start at five, or that the retailer forgives one late truck a month and never two. People know those things. What the software knows is arithmetic, quickly, across every column at once, and that turns out to be the part people were missing.
It does not know that three people will call in sick, either. It knows the moment someone types it in, and then, a day early, it can tell you about Thursday.
Not only pigs
Once we had drawn pork, we kept drawing. The words change from trade to trade. The shape does not. There is always something perishable, a clock it runs on, a bottleneck everyone shares, and a window at the end that does not move.
- Beef: a kill week at an Irish processor, with cattle arriving one lorry at a time and Christmas orders at the far end.
- Chicken: an integrator’s week from the broiler houses through catching, chilling and cut-up to the retail dock and the export container.
- Salmon: a harvest week in Norway, where a storm holds the well-boats and a flight to Seoul wants bigger fish than the pens can give.
- Citrus: a packer’s week near Valencia, where Tuesday’s rain stops the picking crews and the degreening rooms fill up on Wednesday.
- Dairy: a cooperative’s week, where milk from hundreds of farms merges into silos and splits again into milk, yogurt, cheese, butter and powder.
- Rice and pulses: an importer’s six months, where a ship sent around the Cape becomes an empty shelf in January.
Each one is a single page, with an invented company and the same idea: one thread per thing that moves, every problem priced, and a suggested fix you can apply and take back.
The fix for our Wednesday, by the way, was to start the batch an hour earlier, at five, when the line was free. It works with the sick crew and without them, and it would have cost nothing. It was only ever hard to see because the line was in one column and the truck in another.