Module
Delivery Waterfall
Why the deliveries that missed, missed — with the order numbers, not a recollection.
Watch demo
“OTIF was eighty-seven. What happened?” Nobody in the room can answer it.
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- A waterfall decomposing the OTIF gap into named causes, by value
- Every missed line with its cause and the record that proves it
- The share of missed value nothing on file explains, stated plainly
- Lines that could not be assessed at all, and what is missing
A worked example
From the demonstration tenant, on the month just closed
promised inside its own lead time · 13.2 points · ₹30.50 L · 7 lines
production late · 2.3 points · ₹5.24 L · 1 line
carrier late · 0.1 points · ₹35,795 · 1 line
unexplained · 3.6 points · ₹8.23 L · 5 lines — 18.6% of the miss
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
OTIF reported as a single percentage hides which half went wrong, and the two halves have different causes: late is usually planning or transport, short is usually stock or quality. Splitting them is the easy part. The harder part is the waterfall — tracing each miss back to the stage that caused it, with the order numbers attached — because without that the monthly meeting argues about whose recollection is right rather than about what to change. A number nobody can trace is a number everybody can dispute.
Opened by the supply chain manager, the logistics manager and the planner — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
Every cause points at a record and nothing is inferred: no model, no “most likely”. A line whose miss nothing on file explains is counted as unexplained, in full, and that number sits above the chart rather than below it — a waterfall that explains everything has started guessing. Three of the six causes need history a tenant may not hold, and each refuses rather than guesses: a lead time is measured from realised receipts and needs three of them, stock at a past date is walked back through the movements and is refused unless that walk reconciles to what is on hand, and a carrier is named only where one identified consignment carried the order. Where a record is missing the line lands in unexplained and the page says which record it was.
Where this sits
One of 36 modules, on one engine.
Delivery Waterfall reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.