Material clarity.
Production confidence.
See what's needed, when to release orders, and which components could delay your plan. A transparent, multi-level material requirements planning laboratory.
Demand vs planned receipts
Aggregated units across finished goods · weeks 1 to 8
Procurement concentration
Top material costs · bars relative to largest cost
Priority action queue
Releases that need an earlier start or immediate attention
Planning signals
What this scenario means
Build the production plan.
A time-phased bill-of-materials explosion. Planned receipts meet gross requirements, while release dates incorporate lead times.
Plan configuration
Changes recalculate requirements across all levels of the bill of materials
Time-phased requirements
Choose a material to inspect gross demand, on-hand stock and replenishment orders
Complete material plan
All quantities are simulated; receipts are assumed available on time
Understand every component.
Maintain a multi-level component tree, opening inventories, lead times and unit costs. Changes immediately affect the complete plan.
Material master
Editing is local to this browser · archived items are preserved in your backup
Bill-of-materials relationships
Each parent consumes component quantities when its planned production is released
Test before you commit.
Compare baseline material purchases, release risks and projected inventory with alternative planning assumptions.
Scenario comparison
Changes calculated using the same opening inventory and bill of materials
Demand by finished product
Master production schedule · editable weekly forecast
Interpretation
Limits and decision considerations
Transparent by design.
Understand how this studio calculates its material plan, where assumptions enter and what the model does not prove.
Planning algorithm
1. Topological BOM order. Finished assemblies are processed before their subassemblies and raw materials. A cyclic component relationship is rejected.
2. Gross requirements. Finished goods start with the editable master demand schedule. Child demand is triggered by their parents' planned order releases, multiplied by the bill-of-materials quantity.
3. Inventory netting. At each week, available inventory is deducted from gross need. An order receipt is planned when needed to cover requirements plus the safety stock target.
4. Planned releases. Every receipt is shifted earlier by the material's lead time. Releases prior to week 1 are flagged as pre-horizon and the corresponding children are assumed to require material at the planning boundary.
5. Cost estimate. Planned order receipts multiplied by synthetic per-unit costs, without taxes, freight, MOQ, yields or contract restrictions.
Important limitations
Not connected to ERP. The demo does not see stock, purchase orders, suppliers or factories in real time.
Not an advanced production scheduler. Labor, work-center capacity, waste, variable yields, setup times, calendar holidays and transportation are excluded.
Timing risk is a signal. A pre-horizon release indicates potential infeasibility; it is not a calibrated probability of a late delivery.
Inventory assumption. All planned receipts are presumed on time. There are no unmodeled outstanding orders or backorders.
Privacy. Everything runs locally in this browser. Import only information you are comfortable storing on this device; backups are plain JSON.
Reproducibility. All demo inputs and calculation rules are inspectable in this single HTML file. No API key, login or remote service is required.