Module
SupplierGuard
See a supplier failing before the line stops, not after.
Watch demo
A supplier slipped two days, then four, then short. Nobody joined the dots.
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
- OTIF, on-time and in-full separately, per supplier and trending
- Lead-time variance and confirmation reliability
- An explainable risk score — every point of it attributable
- Production exposure in rupees, per supplier
- Early-warning backtest: how many days ahead it actually called the delay
A worked example
Supplier ABC — risk HIGH, ₹42.00 L exposed
OTIF 91% → 78% → 64% over three quarters
lead time +6.4 days against contract
12 materials affected, 3 with no alternate source
→ expedite PO 45001823; qualify a second source for RM-8821
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A supplier rarely fails suddenly. They slip — two days late, then four, then a short shipment nobody logged as short. By the time it is obvious, the line has already stopped once. The difficulty is that on-time delivery averaged across a quarter hides precisely the trend that matters: a supplier drifting is invisible in a mean and unmistakable in a run of deliveries. Variability is the signal, not the average, which is why lead-time spread is measured per supplier rather than reported as one number for all of them.
Opened by the procurement lead and the supply chain manager — 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.
The score measures your suppliers against what they agreed with you — contracted lead time comes in on the suppliers template, so drift is scored against a real commitment rather than a guess. One thing we say plainly: single-sourcing is read from your purchase history, so a material you buy from one supplier out of habit and one you can only buy from them look alike until you say which is which. We would rather show you the pattern than assert a reason your records do not state.
Where this sits
One of 36 modules, on one engine.
SupplierGuard 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.