Running the model
Prior to running the Wine Supply Planning model, it is recommended to ensure the following data has been entered and is up-to-date:
Current Vessel Inventory (managed at Settings/Transactional Data/Vessel Inventory)
Current Bottling Plan (managed at Settings/Transactional Data/Bottling Plan
Known Ship Requests (managed at Shipping/Ship Request Summary)
Known Pickups (managed at Shipping/Pickup Summary)
Known Bulk Wine Purchases (wine coming in to the network - managed at Settings/Transaction Data/Bulk Wine Purchases - see Bulk Wine Movements)
Known Bulk Wine Sales (wine leaving the network - managed at Settings/Transactional Data/ - see Bulk Wine Movements)
Future Harvest intake (managed as a Move of type 'Harvest' - see Locking in Plans)
Note that any of the above can be entered for any date into the future.
Setting the Planning Horizon
Prior to running the model, it is also necessary to determine the Planning Horizon. This determines how far into the future the model is run for.
To access this setting go to Settings/Transactional Data/Planning Horizon Definition
You can then set the start date and duration for the plan. (Note this also drives the BPM dates)
There are 2 ways to run the Wine Supply Planning models.
At the individual unit level
In order to accurately run the plan at an individual level, it is highly recommended to first run the Blend Planning Module for the same unit. This will ensure any blends have been generated to meet future bottling requirements.
To then generate automated Blend Moves and Bottling Moves, select the Blend Moves or Bottling Moves links in the top right of the Wine Supply Planning view.
Blend Moves
Running the 'Blend Moves' process will look at the blend plan for the planning unit/EUR, and determine whether wine needs to be moved to the blending location in order to meet the blend plan. If a move is required, and wine exists within the network, the move will be generated and visible in the 'Moves' section of the view (bottom left). During the process, any 'locked in plans' including ship requests, pickups, and firm moves (refer to Locking in Plans). Automatically generated blending moves will be of type 'wsp-blending_moves'.
Bottling Moves
Running the 'Bottling Moves' process will look at the bottling plan for the planning unit/EUR, and determine whether wine needs to be moved to the bottling location in order to meet the blend plan. If a move is required, and wine exists within the network, the move will be generated and visible in the 'Moves' section of the view (bottom left). During the process, any 'locked in plans' including ship requests, pickups, and firm moves (refer to Locking in Plans). Automatically generated blending moves will be of type 'wsp-bottling_moves'.
Across all planning units
The planning model can also be run across all planning units/EURs.
To access this functionality, go to Settings/Workflows/Refresh Plan
The 'Refresh Plan Workflow' is then shown.
The steps are listed in the order that it is recommended they be run.
Planning Horizon Definition - confirm how far out the model should run (see Setting the Planning Horizon description above)
Import vessel inventory and bottling plans (note this is not required if this data is already provided via interface or entered via the Transactional Data settings menu.)
Run BPM - this will run the Blend Planning Module across all planning units
Run WSP - Blends - this will generate recommended blending moves for all planning units
Run WSP - Bottling - this will generate recommended bottling moves for all planning units
Run WSP - Summary
Run WSP - Bulk Wine Inventory Projections - this will determine the projected inventory position for each week of the planning horizon, at each location, based on all data inputted into the model.
The projections will then be available via the 'Inventory Projections' API.
Last updated
