The Dex Layout tab in the Edit Machine page displays the slot layout received from the Dex file, providing a way to activate/deactivate the slots as planogram selections, or view the details of the Dex layout as opposed to the VMS machine layout. This article will cover some ways in which the Dex Layout tab can appear incorrect or otherwise differ from the VMS planogram/machine layout.
- In some cases, vending machines will send Dex reports with numerous excess columns, which can make the Dex Layout tab appear bulky or erroneous. However, in these cases, the USI/SSI (units/sales since initialization) for the excess slots will typically be 0, since there will be no sales registered from those slots. The correct/incorrect slots can be activated/deactivated as necessary.
- Another common way a Dex Layout can gbecome mismatched is if the VMS machine layout is not mapped with the correct MDB Aliases. On the Dex Layout tab, this will usually display as the blue active slots not showing sales, and grey inactive slots showing sales, either creating duplicate slots side-by-side with their counterparts, or re-creating the entire layout beneath the normal machine layout.
The MDB Aliases vary from machine to machine, so any machine set as MDB Enabled or receiving MDB transactions will need to have the correct MDB Aliases mapped onto the VMS machine layout. You can ask a member of Parlevel Hero Support to assist you in this, or a Manager user can re-map the aliases from the Modify Layout page.
- If the machine has a malfunctioning slot, then its absence in the Dex layout can throw off the VMS machine layout. This is usually caused by a malfunction in the machine itself, with either the slot, coil, or motor cable requiring troubleshooting to be fixed. A fresh Dex should always be sent after troubleshooting to verify that the correct Dex layout was received.
- If an operator decides to move a telemeter from one machine to another without updating the VMS likewise, then the Dex Layout tab will appear incorrectly on the VMS machine. For example, if a device is switched from Machine A to Machine B, then the Dex layout from A will be received by the VMS Machine B, and the system will attempt to apply the layout of A onto B's current planogram, resulting in errors and untracked sales. To prevent this, it's important to track real-life device changes and make sure they are reflected in the VMS.
Special Note: When a Dex layout is received where the Prekit Aliases are different from the VMS machine, they will not automatically update. The incorrect Prekit Aliases will not affect any sales or tracking, but if you would like to update the Prekit Aliases in the VMS to match the physical machine, you can do so via the Edit Planogram page (check off Show slot alias field?, shown in the image above) or the Modify Layout page, accessible to users logged in as Managers.
If there are any questions, concerns, or confusion regarding a machine and its Dex Layout, please feel free to contact Hero Support with the Device or Machine ID, and we will be happy to take a look and assist you in getting everything operational.