What each scenario must contain
A scenario has five fields: goal, input data, steps, pass criterion and evidence. The goal describes the decision it concerns, for example whether a guest enters without the gatehouse's involvement. Input data are the accounts and plant data the demo runs on. The pass criterion is a verifiable statement: yes or no, with a number or a time. Evidence is a screenshot, a printout, an entry in the event log or a recording.
Without a pass criterion the demo turns into a presentation. Write it down before the supplier sees the scenario, so the criterion is not adjusted to what the system does.
Scenario 1: guest entry
Goal: check that a guest invited by an employee completes registration without involvement of security. Steps: invitation, guest registration, entry and exit. Criterion: the guest appears on the list of people present within a time shorter than the set threshold, and after leaving disappears from the list.
Evidence: the view of the list of people present before and after, and the entry for the exit. For a plant where additional declarations apply at entry, add a declaration step and the criterion that without it entry is blocked.
Demo elements in numbers
Scenarios 2 and 3: permit and alarm
Permit: a request from an external company, acceptance, activation and closure. Criterion: the permit has a status consistent with the step, and the hazards are assigned to the workplace. Evidence: the permit card and the history of status changes.
Alarm: an SOS signal or the stillness of a lone worker shown on the isometric 2.5D map, which displays building volumes, vehicles, workers and work locations, along with building interiors with a floor selector. Criterion: the dispatcher sees the location and the floor, and the recipient receives a notification. If the network blocks outbound traffic, webhooks are stored in the queue and collected by the poller, so set the delivery time as an acceptable range rather than a fixed value.
Scenario 4: report and reconstruction of events
The system can reconstruct 7 days of plant work in 2 minutes: supply routes, dangerous work and four counters (vehicles, people, permits, minutes of stoppage). Use this as a reporting scenario: choose a day when something happened that the buyer knows about, and check whether the report agrees with what the buyer knows.
Criterion: the report points to the event at the right time and place, and the counters match a manual count. Evidence: the report export and a screenshot of the reconstruction.
Demo data and the minutes
A demo on an empty installation proves nothing. 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.
One person keeps the minutes. For each scenario they record: passed or failed, the evidence and a remark. A failed scenario with a justification is more valuable than a passed one without evidence, because it shows what the supplier must improve before deployment.
Checklist
Video
Frequently asked questions
How many scenarios are enough?
Four: guest entry, permit, alarm and report. For plants with Ex zones add a scenario for that zone.
Must the demo use the plant's data?
Yes, because a demo on the supplier's data only proves the supplier's data. Plant data means the plant floor plan, accounts, scenarios and devices.
What to do when a scenario is not passed?
Record the result and the evidence in the minutes, agree the fix and the date of a repeat demo. A failed scenario does not invalidate the whole demo.
Let's run the demo on your scenarios
Send us your four scenarios with criteria, and we will prepare a demo on plant data and minutes with the evidence.
Let's talk