sailing Foudra MRP
Reference manual chevron_rightdemand/index

Demand

Independent demand: what the outside world wants from you, by when. Two boats by December. Fifty bearings for a customer's own repair shop. A forecast of ten kits a quarter.

Each row is one part, a quantity and a due date, either an order (a commitment) or a forecast (planned for but not promised; the run plans for both). Reference is whatever names it on your side: the customer's order number, the project.

Pri is its priority, 1 to 5 as on work orders: an order is 2 and a forecast 3 unless you set otherwise. Set 1 for "this one first": everything made or bought for it, all the way down the bill of materials, is scheduled ahead of other work.

Predicted is when the schedule says it will really be ready, from stock, purchase orders' expected dates, work in progress and each workstation's hours: green when on time, red and marked late when not. The demand's own page says why, following the delay back to where it starts.

The run plans for every open row. A row opens on creation and closes when you say so: Close demand once it has been satisfied, Cancel demand if it never will be. Neither deletes anything, and a closed row no longer drives planning.

Demand is only half of what planning reacts to; a part's reorder point is the other half, and needs no row here. Use demand for what is dated and specific; use reorder points for what you always keep.

Demand that arrived from a channel shows the channel and the channel's own reference, and how much of it has shipped. Shipping is recorded by the channel's adapter through the API, which issues the stock and closes the row when everything has gone; the planning run only counts what is still to ship.

A row opens its edit form while it is open. New demand (planner) records one by hand.