Support for multiple Event types

The Forecast engine can now support multiple event types in the engine definition when Perform Event Modeling is set to On, or the Event Only algorithm is used. This supports mapping different historical promotional events and marketing campaigns, such as media advertising and instore promotion.

This functionality calculates an average event size for each event type defined. It is now possible to separate different event types and statistically model the impact.

It is only possible to have a single event type for each history bucket, at the period level of forecasting; so that the impact of an event can be determined. If multiple events run throughout a history period, a new event type or profile must be configured.

Existing forecast engine definitions when Perform Event Modeling is set to On, or the Event Only algorithm is used, the forecast engine continues to work as normal. However, it is not possible to mix the previous event mapping with the new event profiles. If additional event types are required, these event types must be mapped using the new Event Profile definition.

Standard forecast engine definitions (enabled with event modelling) are updated to use a single event profile based on the new definition. These changes are available after appending the base template (base.zip) and the demand template (dpls.zip) for this version.

Note: 
  • Currently, no content is defined that uses multiple event types.
  • By default, this feature is enabled. No additional role or privilege is required to access this feature.