Demand Planning Flow

wpe1.jpg (6441 bytes)

The figure above illustrates the overall conceptual flow of the demand plan module.  The server reads data from the IFS database (the demand and forecast model for each part). The demand is aggregated from transactions and collected into periods (typically monthly). All this data is stored in memory on the Demand Plan Server. The Demand Plan Client sends commands to the server; these commands are processed by the server and a response is sent back to the client. As a result of this demand planning client and server interaction, a new forecast is generated. A typical work schedule for developing new demand plans might be:

  1. On beginning of each period(month) when history for the previous period is ready, the demand from the previous month is aggregated.
  2. A new system forecast is created based on the newly aggregated history, forecast is starting in current period(month).
  3. A user adjusts the computer generated forecasts from 2.
  4. If forecast is used for planning production(Masterscheduling): Forecast are imported (after adjusments are done) to MasterScheduling and used to plan production and rawmaterial purchases.
  5. If IPR is used to compute inventory parameters(Safety Stock, Reorder Point, Lot Size) or Safety Stock/Time Phased Safety Stocks: These calculations are normaly done daily (Refresh IPR Data) using the current avalible forecast.
  6. This process repets itself for each forecast period.

The server can be set up to perform the nessecary jobs automatically. See Demand Plan Server/Scheduling.