Miguel Marengo Canales

blog/Silodisa AI log

weekly log · issue 9 · the daily Verifier

48 hours of grace: at 6:00 a.m., the AI checks whether we did what it said

Our agents make recommendations every day. Every morning at 6:00, the Verifier looks up each recommended pallet in the WMS, puts it in one of six bins and calculates how much got done, with a 48-hour grace period and no AI.

one plan, three mornings 48 h of grace plansaved 6:00 · day 1in progress 6:00 · day 2in progress 6:00 · day 3now it counts done or not done · the WMS decides
One plan, three morningsThe Verifier checks at 6:00 a.m.; before 48 hours, the move is “in progress.” Illustrative: the time the plan was saved.
in 30 seconds
  • Every morning at 6:00, the Verifier checks in the WMS whether what was recommended actually happened. It runs on its own, once a day.
  • Every move lands in one of six bins; the 48 hours are the grace period. Adherence = done ÷ (done + not done).
  • As of September 30, the screen came out gray: “no plans to measure yet.” I’d rather have a gray that tells the truth than an exact, false 0%.
6:00runs on its own, once a day
48 hof grace before grading
80%for green; under 10 cases, gray
151 of 151matched by the independent auditor

A recommendation nobody checks is just an opinion. In our warehouse, AI agents make recommendations every day: where to put away a pallet, what to re-slot, what to bring closer to the door. The plans get saved, approved and sent to transfers. And then, in almost every system I know, the same thing happens: nobody goes back to ask whether it got done.

That’s why one of our thirteen agents has a different job. The Verifier doesn’t recommend anything. Every morning it checks in the WMS whether what was recommended actually happened.

It runs on its own, once a day

Nobody has to remember to press a button. The first time someone opens the Adherence screen after 6:00 a.m., the Verifier runs on its own. It takes every plan saved in the last 30 days, removes the ones someone discarded (“discard” is how you say “this was never going to happen”) and looks up each pallet in the WMS: where it is today and whether it has moved.

It runs only once a day, with a lock, so two people opening the screen at the same time don’t run it twice. In the log it’s signed as “job,” never with a person’s name. If the manager or the administrator needs the picture sooner, they have a button: “Verify now.”

Six bins, in this order

Every recommended move lands in one of six bins. The order matters: they’re checked top to bottom, and the first one that applies wins.

  1. Sent to TEST. The plan was sent to the test environment; the real WMS will never see it done. Counted separately.
  2. Done. The pallet is where we said.
  3. Shipped. The pallet already left on a truck; the recommendation no longer applies. Also counted separately.
  4. Not done. The pallet moved somewhere else, or it’s still where it was and 48 hours have passed.
  5. In progress. The plan is less than 48 hours old. It doesn’t count yet.
  6. Not verified. The Verifier hasn’t been able to check it, or the pallet doesn’t show up. Gray, with how many there are.
top to bottom · first one wins 1 sent to TESTseparate 2 donecounts for 3 shippedseparate 4 not donecounts against 5 in progress · < 48 hnot yet 6 not verifiedgray only two bins enter the count
Six bins for every moveThey’re checked in this order and the first that applies wins. Only “done” and “not done” enter adherence.

The 48 hours are the grace period. Yesterday’s plan doesn’t get graded: operations have their own rhythm, and not everything moves in the same shift. But at exactly 48 hours, it counts.

There’s one exception I like: if the pallet already moved, but somewhere else, it counts as not done even if the plan is young. There’s nothing left to wait for. And separately, as a data point, the Verifier says how many of those ended up in the same aisle as their destination: missing by one level isn’t the same as missing by half the warehouse.

A formula you can check by hand

Adherence = done ÷ (done + not done).

That’s it. Shipped, in progress, test and not verified don’t count for or against. Green at 80% or more, amber from 60%, and below that, red. And if fewer than 10 moves count, the screen shows gray even if the percentage can be calculated: with three cases, a percentage says nothing.

adherence done ÷ (done + not done) red amber green 0% 60% 80% 100% fewer than 10 that count → gray shipped, in progress and test: out
One formula, three colors and a grayThe green target is a parameter (80%); amber starts 20 points below.

Next to the percentage goes the time: hours to done, the median from when the plan was saved until the pallet reached its destination, against a 24-hour target. And also “9 of 10”: the time within which nine out of ten fall.

An independent auditor, which doesn’t use the app’s code and runs its own queries, recalculated the definition case by case: 151 of 151 matched.

A recommendation nobody checks is just an opinion.

Two alarms, no more

The first: a plan with nothing done. If a plan is past its 48 hours and not one of its moves was done, the alarm says “Plan N: 0 of M done in X days. Do it or discard it,” with a link to the plan. Both ways out are honest. What isn’t acceptable is leaving it there.

The second: the window about to close. Each move is tracked for up to 14 days. If there are pending moves two days or less from no longer being tracked, the alarm warns. After that, a pending move stays not done for good.

When the WMS doesn’t answer

The Verifier reads the WMS, and the WMS sometimes goes down. The rule there is all or nothing: if a plan fails midway through a run, nothing from that run is saved. The screen shows gray with the reason and the time of the last verification that did run. I’d rather have a gray that says “I couldn’t read” than a number built from half the data.

The day gray was the truth

Before writing any code, we counted by hand. As of September 30 there were 33 plans saved in 30 days. 28 had been discarded. The 5 live ones, with 15 moves, had been sent to the test environment.

September 30 33 plans · 30 days 28 discarded 5 live · 15 moves sent to TEST 0% red · 5 alarms gray · nothing to measure first rule · crossed out
The gray that told the truthThe figures are from the hand count on September 30, before any code was written.

With the first version of the rule, once the 48 hours passed, the screen would have shown 0%, red, with 5 alarms. It would have been an exact number, and a false one: those tasks were being done in the test database, which the real WMS was never going to see. We decided to count them separately. The screen came out gray: “no plans to measure yet.”

It’s not the prettiest picture for a blog. But it’s the one that tells the truth, and the one that will change as soon as plans are sent to the real WMS.

What comes next

The Verifier also signs what comes after: how much what actually got done really saved, measured by each pallet’s first outbound pick from its new location once 7 days have passed. Today it’s gray for the same reason: there are no completed moves to measure yet. I’ll share it when there are numbers.

AI recommends; people decide. And someone has to come back the next day to see what happened. BIEN y a Tiempo (done right and on time) also means checking.

In your operation, does anyone go back to ask whether what was recommended got done? Write to me.

Miguel Marengo Canales · Silodisa

weekly loglogisticsagentsadherence

Comments

comments · I answer every one. If you disagree, even better: say it with numbers.

  • loading…