InnerWeb
Skip to main content

Demo traffic data on the gate before a demo

A board demo with an empty panel does not convince anyone, and with invented people on the evacuation list it can be dangerous. This guide describes how a vendor or integrator prepares a realistic year of gate traffic, keeping the data clearly marked and fully removable.

12 months
range of realistic traffic in the demo data
Source: karta

Why a year of data in a demo

The first question from the board is usually about trends: how many people enter, what a week and a month look like, who has trainings about to expire. A panel with one day of data does not answer any of these. That is why a demo needs a history of gate traffic covering the whole year.

At the same time a demo must not pretend to be production. Demo data must be recognisable to the vendor's team and removable without a trace, so that after the demo the installation returns to its original state.

What the command that fills the installation does

For demonstrations there is a command that fills the installation with a year of realistic gate traffic, absences and a training cycle. It works on existing user accounts, so it does not create new people who would have to be explained during the demo.

The data is marked, and the whole set can be removed in one step. This is the key point for safety: marking lets you tell a demo entry apart from a real one, and removal returns the installation to its state before the demo.

Panel content: before and after loading demo data

Panel content: before and after loading demo dataBefore and after chart: 0 months of history before loading, 12 months after loading demo data.02.557.51012.5months of historyBefore loading: 0 months of history0Before loadingAfter loading demo data: 12 months of history12After loading demo data
Source: Documentation of the demo command: a year of realistic gate traffic

Rule: nobody invented on the evacuation list

The evacuation list is a safety document. Invented people on that list would mislead the coordinator in the event of a real alarm. That is why demo data is based on existing accounts and is marked, and the demo is run on an installation where there is no real traffic.

If the demo takes place on an installation with a working gate, clearly establish that demo data and real entries are kept apart, and that the evacuation list shown to the board covers only entries marked as demo.

Step-by-step demo preparation plan

The sequence below reduces the risk of mistakes and takes the vendor's team about one working day before the meeting.

  • Choose the demo installation and confirm that it does not handle real traffic
  • Review the existing accounts on which the demo traffic will rest
  • Run the command that fills the year of traffic, absences and the training cycle
  • Check in the panel that the entries are marked as demo
  • Rehearse the demo scenario: entry, refusal, exit, list of people on site
  • After the demo, remove the demo data completely and verify that the register is empty

Evidence for the client that the data is marked

The client receives clear information that the data is for demonstration. It is enough that during the demo the panel shows a marker or a filter for demo data, and the presenter mentions removal after the meeting.

After the demo it is worth giving the client a short note: what was generated, when it was removed and on which installation. This builds trust that the vendor leaves nothing in the system that the client does not recognise.

Checklist

Video

Frequently asked questions

Does demo data create new users?

No. The command works on existing accounts, so it does not add invented people.

How do you tell demo data from real data?

The data is marked, so it can be filtered and removed in full.

What does a year of traffic contain?

Realistic gate traffic, absences and a training cycle.

Prepare the demo on real history

Book a demonstration of the security panel with a year of marked data, without leaving any traces in production.

Let's talk