Step 1: demo instance and database backup
The demo runs on a separate demo instance with its own area, its own locations and transmitters marked with an external identifier, separated from production data. This is the first rule: we do not show anything on an installation where real people work.
Before any data change, make a database backup: a gzip-compressed dump and a check of its size. The evidence is a file larger than zero, read from the directory listing. If something goes wrong during preparation, you return to the state before the changes.
Step 2: hall data and locations
Upload the plant data: the georeferencing of the hall (reference point and rotation angle of the plan relative to north), building shapes and locations with transmitter numbers. On the 2.5D isometric map the buildings, vehicles, workers and work locations should be visible, and the data refreshes cyclically.
Check on the map whether the hall stands in the right place and whether the locations point to the right passages. A wrong rotation angle is visible at once, and once the board has entered, correcting it is troublesome.
Keep in your notes the transmitter numbers assigned to locations, because you will need them when asked about placement without searching. The numbers do not go into public materials.
Timings that matter when running the demo
Step 3: accounts and templates
Set up demo accounts with addresses in a domain reserved for testing, so no notification reaches a real person. Keep the account password as a CI/CD variable, not in the repository or a configuration file. Then prepare permit templates, including the ALARM template for no-movement and the SOS template, and attach the hall locations to them. Without the attachment the alarm exists only in the cache and is not visible on the map.
If you want to shorten the scenario, use a template with automatic approval: the work gets active status at once. Remember that the approval function from the waiting list can approve the oldest waiting work in the whole system, so in the demo you approve by permit identifier.
Step 4: start, scenario, stop
The demo is started and stopped with a start/stop command from one script, and its state is checked with a status command. After starting, check the status, open the map, click it once so the browser allows sound, and only then run the scenario: new permit, SOS, no-movement, visitor registration.
After the first load of the hall the map remembers existing work and does not ring, so create alarms after the map has loaded. A person marker lives in the cache for about 780 s, so movement on the map must be refreshed during the demo.
At the end of this step, show the board the map during movement: vehicles and workers on demo accounts and work locations. The 2.5D isometric map is the most convincing view, because the board recognizes its own hall. Give it a moment of silence to recognize the buildings before you start talking about functions.
Step 5: stop and marker cleanup
After the meeting, stop the demo with the stop command and check the status. The demo deletes only the markers of its own demo accounts, so it does not touch anything else. For a demo longer than two hours, stopping does not remove the markers if the cache tunnel has expired. In that case the markers must be deleted by hand.
Also record the conclusions from the demo, because the pilot decision rests on them. The post-demo checklist describes what to close and what to note.
Checklist
Video
Frequently asked questions
How long does starting the demo take on the day of the meeting?
Starting with the script is quick, but we recommend reserving time for the status check and the sound test before the board enters.
Where should the demo account password be kept?
As a CI/CD variable. We do not put it in the repository or in a configuration file.
What to do if markers remained on the map after the demo?
For a demo longer than two hours, when the cache tunnel has expired, delete the markers of the demo accounts by hand.
Can the demo be run without a database backup?
We do not recommend it. A backup before changing data lets you return to the state before preparation.
Run the demo on your plant's data
We will prepare the demo instance and lead a rehearsal. Book a call about the date.
Let's talk