Additive upload: non-forecasted, propagated driver type

This driver type supports only one data version for the same week, month, regardless of the date of the upload.
  • There is one data version for the month: January, February, March 2018.
  • One data version for week: W01-01/01/18, W02-01/08/18 regardless of the data of the upload.
  • The same principle is applied for other supporting planning frequencies.

Values for non-forecasted, but propagated drivers are uploaded for the forecast periods defined in the source files and their matching periods. In addition, their values from the latest forecast period are propagated/copied to all remaining periods in the configuration set. The result is that the latest uploaded value for the selected week, or month, is valid unless it is changed by the user. For example, the source file includes data for forecast period 35 and 36:

WDDPERIOD: period_035 - WDDFORECAST_PERIOD: forecast_period_035
WDDPERIOD: period_036 - WDDFORECAST_PERIOD: forecast_period_036

Added or overwritten values are propagated/copied from period 36 through the last period in the configuration set.

WDDPERIOD: period_037 - WDDFORECAST_PERIOD: forecast_period_037
WDDPERIOD: period_038 - WDDFORECAST_PERIOD: forecast_period_038
...

Continuing until the last forecast period in the configuration set.

If new uploaded values are for different data area than the previous upload, the new values are added to existing data and from the latest date period propagated/copied to all remaining forecast periods in the configuration set.

If new uploaded values are for the same data area, the existing values are overwritten and from the latest date period propagated/copied to all remaining forecast periods in the configuration set. For example, there is only data version for production standard times for week W01-01/01/18. The standard times are valid unless changed. The standard times are used for the following weeks. For example, W02-01/08/18, W03-01/15/18, unless there is a change in production times. If date information is missing in the new source file, values are uploaded for the forecast period that corresponds with the current date and values are propagated/copied from there.

One example of such a driver is standard times. The standard times for all production activities need to be uploaded only once in the system and the same standard times are used in calculations, regardless of when the calculation is done. You must upload new value only if there is a business use case for it.