This activity is used to specify:
Some description of the fields avaible in Demand Plan Server, General tab as follows,
Max Historic Length: The maximum number of historical periods for the server to read into memory. The length of each period is determined by the period version. If the period version is monthly, then each period is a month's duration. This is a mandatory field.
Number Of Forecast Periods: How far ahead the forecasts should extend, in periods. The length of each period is determined by the period version. This is a mandatory field.
Forecast Error Periods: The number of periods to go backward from the last historical demand if you are calculating MAE, MAPE, ME, and Value of MAE.
Measurement Periods: The number of periods to go backward from the last historical demand if you are calculating Their.
Copy Rule: When moving from one period to the next, the system creates a new system forecast. The following alternatives exist as initial settings for the adjusted forecast:
From System means that the adjusted forecast is set to the system forecast for each new forecast made.
To Zero means that the adjusted forecast is always set to 0 for each new forecast made.
From Previous Adjusted means that all periods that were adjusted in the previous forecast are copied to the new forecast, while periods not adjusted are copied from the system forecast. Note that events are not set as fixed adjustments, so for periods with event adjustments will follow the system forecast with the event added.
From Previous means that all adjusted values from the previous forecast are copied to the new forecast adjusted values.
Enable Machine Learning: This is used to enable the machine learning forecasting model in Demand Planner. Only one Demand Plan Server per environment can be configured for Machine Learning.
Setting up of basic data (example: Longitude and Latitude for Base Flows) is only possible once this is enabled.
Once this is enabled following setup needs to be in placed as well,
Note: Even this is enabled and if the customer has not setup the Machine Learning functionality, the machine learning forecasting model wouldn't work.
Default Forecast Model: The global default forecast model, used when there are no standard models set on a forecast part. See Forecast Models.
Default Alpha: The default alpha is used when no alpha value is specified on a part. This is a mandatory field. See Forecast Models.
Default Beta: The default beta is used when no beta is specified on a part. This is a mandatory field. See Forecast Models.
Default Rho: The default rho is used when no rho is specified on a part. This is a mandatory field. See Forecast Models.
Default Moving Average Periods: The default number of periods used in the moving average model when no value is specified on a part. This is a mandatory field. See Forecast Models.
Default Delta: The default delta is used when no delta is specified on a part. This is a mandatory field. See Forecast measurements.
Default Season Profile: Whether a season profile is used for the part. The default season profile (Yes) is used when no season profile is specified on a part. If No is selected, no season profile is used for the part. This is a mandatory field. The default season profile, also called automatic, is the system profile for the part's historical pattern. Note that the part must pass the season profile test to have a profile assigned. See Season Profiles. (Automatic Generation of Season Indexes is the has season profile test).
Group 1...6: Connects group 1 to an IFS Cloud group field. Using the Demand Plan Server, it is possible to view and modify forecasts on groups of parts. For example, you can modify the total forecasts made for all the parts belonging to a specific product family. It is also possible to combine two or more groups, i.e., to see the total forecast for all parts within a specific product family and a specific ABC Class. Max six different group fields can be selected.
The following fields can be used to group parts: Part Product Code, ABC Class, Type Code, Lead Time Code, Planner Buyer, Asset Class, Prime Commodity, and Second Commodity. It is possible to add other fields from other IFS tables; see Release Notes.
A demand server id should be choosen or entered.
There are no system effects until the server is started.