InnerWeb
Skip to main content

Checklist the day before a system demo on plant data

A demo on plant data is often the first chance to see the system on your own floor plan. If the day before a plan, accounts, scenarios or network access is missing, the demo ends with explaining the gaps. Below is a checklist with comments that the coordinator can go through in an hour.

9
checklist points for the day before the demo
Source: sample calculation

How to use the list

Go through the list the day before the demo with a person from health and safety, IT and security. Mark each point as ready or to be completed, and for an open point record who closes it and by when. The list concerns preparation on both sides: the plant is responsible for data and access, the supplier for the instance and devices.

Floor plan and map

The system shows the plant on an online map in an isometric 2.5D view, with building volumes, vehicles, workers and work locations, as well as building interiors with a floor selector. That is why site plans are needed before the demo: the floor plan of the hall, the floors and the places that will be the heroes of the scenarios.

Position results from signals from many beacons averaged on the map, and a demo usually needs a route with about 100 beacons, that is 1 per about 200 m2. Confirm that the installation points are accessible and that the demo route is current.

Checklist points by area

Checklist points by areaChart: 2 points for the floor plan and route, 3 for accounts and data, 2 for devices and network, 2 for running the demo and minutes.0123pcsFloor plan and routeFloor plan and route: 2 pcs2Accounts and dataAccounts and data: 3 pcs3Devices and networkDevices and network: 2 pcs2Running and minutesRunning and minutes: 2 pcs2
Source: Sample calculation: division of the checklist points on this page

Accounts, data and scenarios

Accounts must exist beforehand: the employee issuing an invitation, security, the dispatcher, the coordinator of an external company. The demonstration installation can be filled with a year of realistic plant traffic on accounts that already exist: gate badge swipes, absences with reasons and a running training cycle. Without this the evacuation list and working time show emptiness.

Scenarios should be written down and agreed: guest entry, permit, alarm, report. For each one set the pass criterion and the evidence for the minutes.

Devices and network

Check the mobile devices, their battery charge and access to the instance. No inbound ports are opened on the plant network, and outbound traffic is limited to HTTPS 443 towards the instance address. If the network blocks outbound traffic, webhooks are stored in the queue and collected by the poller through a working inbound channel, so during the demo an alarm may be delayed by one polling cycle.

A good practice is to test the connection earlier from the place where the demo will take place, not only from the office.

Running the demo and the contingency plan

Set the order, time and role of each person. Prepare a contingency plan: the system recording reconstructs 7 days of plant work in 2 minutes, so it can be shown if connectivity fails. Record who keeps the minutes and who may stop the demo when something needs explaining.

Checklist

Video

Frequently asked questions

How long does it take to go through the list?

About an hour with people from health and safety, IT and security, if the plans and accounts are prepared. Missing data extends the preparation.

Does the list also apply to a remote demo?

Yes, except for the points concerning devices on the plant floor. The plan, accounts, data and scenarios remain necessary.

What to do when the floor plan is missing?

Ask the plant maintenance department for the plan or use the evacuation plan. Without a plan the demo will not be on plant data.

Let's prepare the demo on your data

We will go through this list together with your coordinator and prepare a demonstration installation with realistic plant traffic.

Let's talk