Why the plant's data changes the assessment of the system
When the director sees their own hall on screen, the assessment stops being aesthetic and becomes practical. The question is no longer whether the map is pretty, but whether the loading gate is in the same place, whether the inspection route passes where people actually walk, and whether the location of an employee in the paint shop makes sense.
Preparing plant data requires less work from the team than is assumed. Most materials already exist: hall plans, lists of roles, hazardous-work procedures. The task is to identify them and share them in a form that can be loaded into the system.
Floor plan of halls and buildings
The basis of the demo is the floor plan. The online plant map in a 2.5D isometric view shows building volumes, vehicles, employees and work locations. It also contains building interiors with a floor selector and a view of a single employee. To use this, the system needs building outlines, floors and the placement of gates.
A drawing, a scan or a file from the technical office is enough. The plant does not need to correct it, because the first version of the map serves to assess the concept, not as an execution design. If the plan is confidential, a simplified version with outlines only and marked zones can be shared.
- plant plan with the outlines of buildings and roads
- floor plans for multi-storey halls
- location of gates, entrances, gatehouses and assembly points
- marking of special zones: paint shop, chemical store, Ex zones
Split of materials to prepare before the demo (example)
Roles and people appearing in the demo
The system only makes sense when each viewer sees their own role. The plant team should indicate who will play the director, OHS, maintenance, security, the dispatcher, the external company coordinator and the guest. For each role the system shows the matching view and permissions.
Roles do not have to be real employee accounts. Demonstration accounts named after the roles are enough. This way the demo does not reveal personal data, and the plant sees how the system divides permissions.
Three real scenarios instead of a catalogue of functions
Good practice is to choose two or three situations that the plant knows from its own experience. These can be hazardous work on a line with an external company, a guest entering with registration at a kiosk using a QR code in the invitation, or an emergency situation: a lone worker motionless, SOS, indicating a location on the map.
Each scenario is described in three sentences: who, where, what happens. The presenter replays the situation on the map and shows what data the dispatcher sees, who receives the notification and what document is created in the system.
- hazardous work: permit from a template, risks assigned to the location
- guest: invitation with QR code, registration at a kiosk, safety briefing
- alarm: SOS or a motionless person on the map, dispatcher view
- delivery traffic: vehicle paths, dwell time at the gate
Seven days of movement and the scope of history
The system recording can replay 7 days of plant operation in 2 minutes: delivery routes, hazardous work and four counters (vehicles, people, permits, minutes of stoppage). For such a recording to make sense, the plant can indicate a typical working week or share data on vehicle movements and permits from that period.
Entry into the implementation starts with people and gates, without beacons. That is why data on gate passages and lists of people is often the first thing the team can provide if it wants to see the demo with real traffic.
What stays with the plant and what with us
It is worth agreeing the division of responsibilities in writing before the meeting. The plant provides the plan, the roles and the scenario descriptions and appoints a coordinator. The supplier builds the map, the demonstration accounts and the demo script, and after the meeting deletes or archives the data as agreed.
It is also worth agreeing who from the IT department asks questions and how they are recorded. IT questions are often decisive for a pilot, so it is better to have them written down than remembered.
Mistakes that spoil a demo on plant data
The most frequent mistakes are delivering the plan too late, too many scenarios and no coordinator responsible for the data. The demo then falls back to sample data and the value of the preparation disappears.
The second mistake is expecting that everything will be shown. It is better to show three situations in detail than ten superficially, because the director will remember what they understood.
Checklist
Video
Frequently asked questions
Does the demo require real personal data of employees?
No. Demonstration accounts named after roles are enough. Personal data appears only in the pilot, after the scope and the legal basis for processing are agreed.
How detailed must the floor plan be?
A drawing with the outlines of buildings, gates and zones is enough. A simplified plan lets you assess the concept, and details can be added during the pilot.
How many scenarios should be shown?
Two or three. Each should have a description of who, where and what happens, so that the director recognises the situation from their own plant.
Let's prepare a demo on your plant's data
Send us the floor plan and a description of two situations. We will build the map and the demo script, and you will assess the system on your own site.
Let's talk