Business problem
Inventory & Working Capital
What you're holding, why it's there, and what it costs to hold it.
Inventory is three questions wearing one coat: how much is on hand, why it is there, and what holding it costs. Most inventory dashboards answer only the first, because the other two are authored decisions rather than sums over a ledger — which stock counts as excess, whether a reorder point is compared against on-hand or against inventory position, whether age is a mean or a distribution. The definitions here fix those choices explicitly, the dashboard pattern shows the star schema underneath, and the reference build runs the whole set over a frozen year of simulated daily ledger data so the arithmetic is visible rather than asserted.
Metric definitions
Computable definitions from the KPI Dictionary — every decision switch made explicit, with the formula and the source tables in each ERP.
Dashboard patterns
A wireframe paired with the star schema underneath it: fact grain, measures with their additivity rules, and the source tables per reference.
Cross-ERP guides
Modeling guides that hold across every source system rather than inside one.
Reference builds
Working implementations of the definitions and patterns above, running over frozen, simulated data. Not a resource and not a case study — no client data, and no client named.
Simulated data, frozen snapshot — not a live client system.
In the references
Where this data lives in each source system. A way into the ERP references, not an index of them — every reference landing lists all of its modules.
The other business problems
- Demand Planning & Forecasting — How wrong the forecast is, in which direction, and where the error is worth fixing.
- Customer Service & Fulfillment — Whether the order arrived complete, on the date you committed to.
- Procurement & Supply — What's on order, when it lands, and how the supplier actually performs.
- Manufacturing & Production — Whether the plant built what the plan said it would build.
- Data Foundation & Governance — Landing ERP data in a lakehouse without losing deletes, history, or control of who reads it.