Module
Control Tower
Every exception that needs a decision today, with the arithmetic that found it.
What it produces
- Exception feed ranked by financial impact
- Nineteen KPIs, each computed in SQL with its formula shown
- Approvals and audit trail
- Evidence export for any figure on the page
A worked example
Days inventory outstanding — 61.4 days
average inventory value ₹4,71,20,880
÷ cost of goods sold ₹28,01,44,000
× 365
= 61.4 days · 4,182 rows · as at 31 Jul 2026
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A dashboard shows everything and leaves you to find the problem. On any given morning a few hundred things are slightly wrong and perhaps six of them matter this week, so the difficulty is not display, it is ranking — and most tools rank by recency, or by a colour somebody assigned two years ago. Ranking by the money at stake changes which of the six gets opened. Showing the query that produced the figure changes whether anybody acts on it, because a number a planner cannot defend in a meeting is a number they will not act on.
Opened by the supply chain manager, the owner and the administrator — what each of them sees first.
Said before you ask
What is not finished.
Nothing outstanding. This is the product, it runs against live tenant data, and every figure it shows carries the arithmetic that produced it.
Where this sits
One of 16 modules, on one engine.
Control Tower 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 15 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.