MPS and MRP: translating demand into production and material proposals

Planning compares demand with existing stock and incoming supply to propose what must be produced and when. MPS focuses on finished goods; MRP also explodes component requirements. A proposal is a planning result, not a physical stock movement or an instruction to bypass review.

DNA Planning Run lets the planner choose mode, strategy, horizon, plant or warehouse, item scope, demand sources, lot sizing and lead-time source. Results include planned orders, exceptions and pegging, which traces the demand a supply proposal serves.

Different planning questions

The master production schedule concerns the finished output the business intends to supply. Material requirements planning translates that demand through recipes and supply information to understand what supporting materials or production are needed.

The result depends on scope and assumptions. Demand sources, existing stock, incoming supply, lead times, lot-sizing rules, and the planning horizon can all affect the proposals. A precise output from a planning run is only as credible as those inputs.

Quantity and timing

Demand is 100 assemblies, usable stock is 20 and relevant incoming supply is 30. A simple net requirement is 50 before safety stock, lot-sizing and timing rules. If the incoming 30 arrives after the demand date, timing can still create a shortage even though total quantities appear sufficient.

The example shows why a period total can conceal a date-specific shortage. Supply arriving after the need cannot necessarily satisfy the earlier commitment. Planning needs to connect quantities with the dates on which they become useful.

DNA's planning choices

DNA's documented planning run supports mode, strategy, horizon, plant or warehouse, item scope, demand sources, lot sizing, and lead-time source. These options define the business question being asked.

A narrow item scope answers a different question from a broader component plan. A short horizon may miss later demand but provide a focused near-term view. The selected strategy should reflect the intended planning purpose rather than be chosen only because it produces fewer exceptions.

What a selected planning input proves

The inclusion switches express what the planner requests. They are not confirmation that the necessary data exists or was included. A completed run can report configuration exceptions explaining that a requested source was unavailable. For example, a run can request forecasts but report that it planned firm demand only because no forecast source was available. Similarly, a safety-stock option can generate no demand when the required values are absent. The run's exceptions and results are the evidence for its actual scope.

Proposals and commitments

A planning proposal is not evidence of physical stock and does not mean production has begun. The planner needs to understand the recommended quantities, timing, dependencies, and exceptions before creating an execution commitment.

Existing firm decisions also matter. Planning should be interpreted alongside commitments the company has already made, rather than assuming every rerun should freely replace the operational plan.

A useful planning result

The result should explain what is proposed, which demand it supports, when it is needed, and which assumptions or exceptions deserve attention. DNA's planned orders and pegging relationships help organise that explanation.

The value of planning is earlier visibility of needs and constraints. It gives purchasing and production time to respond before a customer commitment becomes an immediate shortage.