sub-modules
MRP Planning
Plans that survive contact with engineering changes — replan in hours, not weeks.
The plan was perfect until engineering released a revision mid-quarter — then six weeks of procurement unraveled. MRP Planning pins every run to its inputs snapshot and replans affected branches the hour a change lands. Superseded plans stay as evidence; the new plan cites exactly what moved and why.
Planning stages
Each stage below pins its inputs — reruns from the same snapshot reproduce the same plan.
data Viz
data View
section: stages
Explode
Demand explodes through versioned BOMs with effectivity, phantoms flattened, and matrix configurations resolved. Every requirement cites its parent and revision.
Net Against Supply
Gross requirements net against on-hand, reserved, and planned supply with pegging preserved, so every planned order traces to the demand that created it.
Constrain by Capacity
Planned orders load work centers with setup, run, and queue times. Overloads surface with competing jobs named; infeasible stretches return certificates.
Planning guarantees
- Snapshot inputs
- BOM revision, inventory position, and capacity model pinned per run
- Honest infeasibility
- Certificates with sensitivity instead of silent partial plans
- Retained history
- Superseded plans preserved as evidence with lineage to replacements
- section
- capabilities
Planning by industry
Material planning bends per industry — same explosion discipline, different variability stakes.
data Viz
data View
section: industries
Automotive
High-volume repetitive planning with EDI-driven demand and sequenced supply. Engineering changes cut over by effectivity with open orders protected.
Electronics
Long-leadtime component planning with allocation risk flagged early. Revision churn absorbs through effectivity without scrapping healthy stock.
Food and Pharma
Shelf-life-constrained planning with FEFO supply selection and batch minimums honored. Expiry risk plans down before waste happens.
MRP Planning questions
Section 1
What happens when a BOM changes mid-plan?
The active plan invalidates affected branches and replans against the new revision. Superseded plans are retained as evidence, never overwritten.
Section 2
How are capacity constraints handled?
Work-center capacity with setup, run, queue, and wait times constrains the plan. Overloaded resources surface with the jobs competing for them named.
Section 3
Our planners don't trust system plans. How do we earn it?
Start with pegging: every planned order traces to the demand that created it. Trust arrives the first time a planner follows the trace and finds it correct.
data View
section: faqs
content section
value: Every plan carries its inputs snapshot: BOM version, inventory position, capacity model. Infeasible plans return certificates with sensitivity instead of silent partial answers. Superseded plans are retained as evidence, never overwritten.
Section 6
Versioned, effectivity-dated BOM explosion
Section 7
Pegged supply and phantom-item handling
Section 8
Capacity-constrained planning with feasibility verdicts
Section 9
Instant replan on engineering change