Planning Cycle in M3 DMP

The Forecast Cycle Management is used for controlling access to data in a structured way. For example, the administrator cannot create new phantoms, import new data, export updated forecasts, and so on, while forecasters have access to the data. Forecast cycle management secures data integrity and consistency at any given point in the forecast cycle.

Forecasters do not have access to databases while administrators are preparing data (version status = closed). Equally so when forecasters are granted access to a database, then administrators access is limited (version status = open).

The illustration below represents the main activities in a forecast cycle. The yellow colored arrows denote that the version is closed and the green arrows signify that the version is open.

When a forecast version shifts from closed to open, the forecast cycle number is updated. Updates from forecast packages are validated against the actual cycle number to prevent forecast updates with reference to previous forecast cycles.

The forecast cycle concept ensures that the administrator has unshared access to the database while maintaining the data. The concept also ensures that administrative tasks are being performed in a consistent manner, and that updates from the forecasters are based on data from the same forecasting cycle when working with distributed process flow. Updates from previous forecast cycles are rejected by the M3 DMP Server, unless the Bypass switch is set for the forecast version.

The Bypass switch is intended as a safeguard, which makes it possible to receive updates to a closed forecast version. The switch should only be enabled, if updates to the server were overlooked during a forecast cycle.

Note: The bypass function only works on updates from the forecast cycle immediately prior to the closing of the database.

The process flow concept is based on forecast data being open for updates or closed for updates. The tasks of opening and closing versions are supported through functions in Version Control. Use the Open Version button to change a database status from Closed to Open. The database is closed using the Close Version button in Version Control.