The problem: a demo that shows emptiness
A typical demo environment has a few accounts, one gate and no history. When the evacuation list is shown, an empty table appears; for working time there are no entries; for training there are no dates. The assessor does not know how the system behaves with thousands of events, because they see none of them.
For an integrator and the IT department this is an important signal. An environment without data does not allow checking the performance of views, the correctness of reports or the logic that only becomes readable with real traffic.
What a demo installation with real traffic is
A demo installation can be filled with a year of realistic plant traffic on accounts that already exist: gate passages, absences with reasons and an ongoing training cycle. Without this the evacuation list and working time show emptiness.
The data is synthetic, but has a structure similar to the real one: shift rhythm, holiday and sick-leave absences, training with expiry dates. As a result the assessor sees how the system shows the status of people on site and what reports match the plant's process.
- gate passages: entries and exits following the shift rhythm over a year
- absences with reasons: holidays, sick leave, business trips
- training cycle: expiry dates and overdue items
- evacuation list: status of people on site at a chosen moment
What the integrator checks: gate traffic and integration with access control
The integrator first asks where the system gets the passages from. InnerWeb does not manufacture access control readers, but integrates with the customer's existing system and receives card passage events from the access control system. The demo environment should therefore show passages as events from an external system, not as an own reader.
It is worth checking whether gate data is linked to people's accounts, because this decides the correctness of the evacuation list. If a passage has no assigned person, the list will show an error. An environment with history lets you see how the system reacts to such gaps.
What the IT department checks: equivalence with production
The security department of a buyer that asked 12 questions about the reporting system expected a demonstration environment equivalent to production. This is good practice for any buyer: the demo environment has the same security settings, the same login method and the same code as production.
In the demo environment each customer has an isolated instance with its own database, so demo data does not mix with the data of other plants. IT can verify this by asking about the database, the mail system and the administrative accounts.
How to assess the quality of history in a demo
History is useful when its structure is close to a real plant. The assessor should check four things: whether the rhythm of passages matches the shifts, whether absences have reasons, whether training has expiry dates and whether reports contain data from the whole year, not just a few days.
A control question: after choosing a date from half a year ago, does the evacuation list show a realistic number of people? If so, the history works.
Good practice: how to request a demo and how to run it
The buyer should describe in the tender what the demo environment should contain: the scope of the year, the shift rhythm, the number of people and the types of absences. The supplier confirms this in writing and states which data is synthetic.
- ask for an environment equivalent to production, not a special showcase version
- indicate the scope of history: e.g. a year of passages, absences and training
- check the evacuation list for a date in the past
- ask about the source of passages: whether they are events from the access control system
- ask which data is synthetic and which is real
- record the conclusions of IT and the integrator in one document
Checklist
Video
Frequently asked questions
Is the data in the demo environment real?
It is synthetic, but its structure is similar to the real one. The supplier should state which data is synthetic, so that the assessment is fair.
Does InnerWeb provide access control readers for the demonstration?
No. InnerWeb integrates with the customer's access control system and receives card passage events, so the demo shows passages as events from an external system.
Why is a year of history needed?
Without history the evacuation list and working time show emptiness. A year of data lets you assess reports, view performance and the system's behaviour when a passage has no assigned person.
Want to assess a demo environment with history?
We will show an installation with a year of gate traffic, absences and training, and answer the questions of the integrator and the IT department.
Let's talk