Suppose you have one restaurant in Cardiff and another in London. You would like to show the same special offer sign at both restaurants, but because of geographical price differences, the price for a Super Saver Meal is £3.00 in Cardiff but £3.50 in London.
One solution is to have two separate signs with different prices, and deploy one to Cardiff and the other to London. However, maintaining two almost-identical signs is not very convenient. Nor is it very scalable if you have hundreds or even thousands of restaurants, and several sets of prices!
A more elegant solution is to use ‘data objects’. A data object allows you to define multiple ‘tiers’ of pricing (or other data). You can then define a single sign with placeholders for the prices. When you deploy the sign to devices in a location, you also deploy a ‘tier’ of data appropriate for that location. Devices in that location will then substitute the placeholders for the actual price data in that tier.
Defining a Data Object
Consider the following pricing structure for meals:
Standard Restaurants (including Cardiff):
PRODUCT CODE | PRODUCT NAME | PRICE |
---|---|---|
376 | Super Saver Meal | £3.00 |
432 | Meal Deal | £3.45 |
441 | Kids Meal | £2.60 |
499 | Deluxe Meal | £4.50 |
London Restaurants:
PRODUCT CODE | PRODUCT NAME | PRICE |
---|---|---|
376 | Super Saver Meal | £3.50 |
432 | Meal Deal | £3.95 |
441 | Kids Meal | £2.90 |
499 | Deluxe Meal | £5.10 |
In SignStix terminology, this would be one ‘data object’ (Meal Prices) with three ‘columns’ (Product Code, Product Name and Price) and two ‘tiers’ (Standard and London), and four data ‘items/rows’ (Meal Deal and so on).
- Log into SignStix Director
- Navigate to Modules > Data Objects.
- Click the plus (+) button near the top.
- In the resulting window, enter a name for your data object e.g. ‘Meal Prices’.
- Set the ‘Base Tier name’ to ‘Standard Restaurants’.
- Leave the ‘Data source’ as ‘No source’.
- Click the ‘Add Columns’ button.