InnerWeb
Skip to main content

Checklist before a safety system demo for the plant board

On demo day the presenter has a few dozen minutes to check the things that shape the board's impression: network, accounts, templates, sound, database copy, server resources and the scenario. This checklist puts those checks in the order they are performed and explains why each item matters. Print it or keep it beside the computer.

5.3 s
SOS siren, one playback
Source: card
780 s
lifetime of a person marker
Source: card

Why a checklist and not memory

The demo is short, and every fault the board sees stays in memory longer than the features do. The most common failures repeat: no siren sound, a template without a location attached, too little server headroom. All of them can be checked in a dozen or so minutes before the meeting, which is why the list is mandatory, not optional.

The demo is a rollout scenario on a separate demo instance with plant data. The checklist does not touch the plant's production systems and needs no one's approval beyond the host of the room.

Network, accounts and data

Start with what blocks everything else. Check that the presentation computer can reach the demo instance, that the demo accounts log in and that the map loads the hall. The accounts use addresses in a domain reserved for testing, so no message from the demo reaches a real person.

Also check the database copy: a gzip-compressed dump made before the changes should exist and its size should be greater than zero. This is proof that you can return to the starting state if something goes wrong.

Parameters to check before the demo

Parameters to check before the demoHorizontal bar chart: feed 3 s, siren 5.3 s, person marker 780 s.0200400600800sFeed pollingFeed polling: 3 s3SOS sirenSOS siren: 5.3 s5.3Person markerPerson marker: 780 s780
Source: Feature card: map and demo parameters

Templates, alarms and sound

Stillness is drawn on the map only for a permit from the template named ALARM, and SOS for the template named SOS. Without a location attached to the template, the alarm exists only in the cache and is not visible. Check that both templates have the hall location and that the SOS template has sound playback on the map enabled.

Sound requires a user gesture. After opening the map, click on it, then run a test alarm and check that the siren can be heard in the room. The SOS siren lasts 5.3 s and repeats twice. After the test, clear the leftover tasks so the board does not see remnants.

Server and resources

A demo lasting several hours needs server headroom on the demo server. If the meeting is expected to run long, check the load level and free resources before starting. Run the status command from the single start/stop script and make sure all components are running.

A person marker on the map lives in the cache for about 780 s, so employee traffic has to be refreshed during the demo. The demo deletes only the markers of its own demo accounts, so real data is not at risk.

Scenario and presenters

Write the scenario down in order: map, permit, SOS, stillness, visitor. Decide who presents and who records the questions. Prepare an answer to the question whether this is a deployment: no, it is a rollout scenario on plant data. The company figures that may be quoted: 20 deployments and pilots, and a 100% conversion rate from pilot to deployment.

A spare device with the accounts already logged in cuts the time to recover from a failure to one minute. After the demo, carry out the items on the post-demo checklist so the pilot decision has a basis.

Checklist

Video

Frequently asked questions

How long does going through the list before the demo take?

A dozen or so minutes on a working instance. Check the sound and templates the day before and repeat the check on the day of the meeting.

What if the test alarm did not sound?

Click on the map after opening it, check the template and make sure the alarm was created after the map loaded, not before.

Does the list apply only to a demo held at the plant?

It applies to every demo on the demo instance, including one run remotely.

Make the demo run without surprises

We will run the rehearsal with you and go through the list with your team. Book a call about the date.

Let's talk