Purpose
Use this article to understand the VMS Machine Model Engine and its related features, including Selection Maps, Product Sizes, and model inheritance.
Overview
Machine Models in VMS allow operators to manage vending machine model information, and when configured, define rules for machine layouts, product fit, and selection capacity.
The feature supports different levels of setup depending on how much control the operator wants over machine model ownership, layout validation, product selection, and capacity automation.
If the machine model does not have a layout map, the layout is not automatically built.
Process
Levels of Access
Machine Model setup can be customized to the desired level of access.
At the most basic level, operators can create and manage machine model names and basic model details. If no Selection Map or Product Size rules are configured, the system functions close to the existing machine model behavior, while giving the operator control over the machine model names available in the environment.
The Machine Model Engine supports 3 levels of access, which can be set as desired. (If the Operator does not want to enforce selection maps or product sizes, granted in Levels 2 and 3, they do not have to.)
Level 1
Level 1 access grants Basic machine model information - Operators can create and manage machine model names and basic details with the following selections:
- Machine Name: name of the machine model.
- Manufacturer: the machine manufacturer.
- Category: the machine category or type.
- Tier: sets the machine model as a parent, or child of another parent machine model. (For more information, please see the Parent and Child Machine Models section of this article.)
- Remote Price Change: checkbox, which sets whether or not the model is remote-price capable.
Level 2
Level 2 access grants Basic machine model information + Selection map - In addition to basic machine model information, the VMS also validates whether the machine model layout matches the machine layout before the model can be used.
This is enabled via the Selection Map checkbox. (For more information on Selection Maps, please see the Selection Map section of this article.)
Level 3
Level 3 access grants Basic machine model information + Selection Map + Product Sizes - In addition to basic machine model information and selection map, the VMS also validates which products can be placed in machine selections, and can automatically update capacity based on Product Size rules.
This is enabled via the Product Size Enabled checkbox after Selection Map is already enabled. (For more information on Product Sizes, please see the Product Sizes section of this article.)
Parent and Child Machine Models
How to Enable
A child machine model can be tied to a parent machine model. A machine model can be set as either child or parent in the Tier dropdown in the Machine Model Settings.
(For more information on Machine Model settings, please see the Levels of Access section of this article.)
How the Parent and Child Relationship Works
The child model inherits the parent model’s Selection Map and related rules. This avoids rebuilding the same Selection Map and Product Size rules for multiple model variations that share the same physical layout. Use this when model names differ, but the machine layout and product fit are the same.
Example: Let's say there are 20 model variations that only differ by model name. A parent can be made with a selection map and product size rules that are tied to the child models. So when the child models are created, they can just inherit the selection map and product rules from the parent, instead of having to recreate them 20 times.
Selection Map
How to Enable
The Selection Map defines the machine model layout from a row and column perspective. This is enabled via the Selection Map checkbox. (If the Operator does not want to enforce selection maps, they do not have to.)
(For more information on Machine Model settings, please see the Levels of Access section of this article.)
How Selection Maps Work
A Selection Map can define:
- Rows
- Columns
- Selection Width (Single or Double)
When this functionality is enabled, VMS compares the machine model layout to the machine’s DEX layout. If the layouts do not match, the machine model is not available for that machine.
If a valid machine model is assigned and the model layout is later changed, VMS displays a warning that the layout will no longer be in sync with the machine model rules. The user can continue or cancel.
Product Sizes
How to Enable
After the Selection Map is configured, Product Sizes can be enabled on the machine model. (Located under Settings > Warehouse > Product Sizes.)
Product Sizes are enabled via the Product Size Enabled checkbox. (If the Operator does not want to enforce Product Sizes, they do not have to.)
(For more information on Machine Model settings, please see the Levels of Access section of this article.)
How Product Sizes Work
Product Size is a product attribute, used to define what type or size of product fits in a machine selection. A product is assigned a Product Size, and the Product Size is then used by the machine model rules to control product availability in planograms.
Product Sizes can be granular (i.e. 12 oz , 20 oz bottle) or generic (i.e., candy bar, bag of chips) depending on the operator’s needs. Product Size can also define single or double capacity.
Product Sizes cannot be used without a Selection Map.
When enabled, Product Sizes can be turned on or off on an individual basis, by clicking the On and OFF toggles.
Planogram Product Search and Capacity Updates
When Product Size rules are configured, VMS filters product search results in the planogram. Products that do not match the machine model, selection type, Product Size, and capacity rules will not appear in product search.
When a product is changed in a machine selection, the VMS can automatically update the selection capacity based on the Product Size rule configured for the machine model.
For example, if a user changes from a smaller product to a larger product, the capacity can update to match the configured rule.
If the machine model and Product Size rules are configured correctly, users do not need to manually adjust capacity at the planogram level after changing products.
If Product Size enforcement is not used, the VMS functions as it does today, and users can add products broadly.