Starting point: an offer, a group and one meeting
The plant makes agricultural machinery and belongs to a global group, so every decision on a new system goes through several levels: the plant director, OHS, maintenance, security and, for network and data topics, the IT department. The offer is complex, and the buyer asks for a demo before deciding on a pilot.
This is a demo concept for a plant of this type. The plant is not yet a user of the system, so the scenario contains no implementation results, only a plan of what will be shown and which decisions the viewer can make after 45 minutes.
Principle: the plant's floor plan instead of sample data
The most common demo mistake is a generic presentation on someone else's data. The director sees an attractive map but not their own hall, their own gates and their own zones, so they cannot judge whether the system fits the plant. That is why the demo starts with a floor plan supplied by the plant, not with a slide about the company.
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. For a production hall this means the director immediately sees the buildings, not an abstract grid of points.
- the plan of the halls and gates as a drawing or scan that the plant can share without risk to confidentiality
- a list of roles to be shown: director, OHS, maintenance, security, dispatcher
- 2-3 real situations from the plant, e.g. hazardous work on a line and entry of an external company
- agreement on which data is simulated and which comes from the plant
Time budget of the 45-minute demo
The 45-minute plan: six blocks with a time budget
Time is the shortest resource in a meeting, so the plan must have a minute budget. The split below is an example calculation for a demo in which the director is to see three things: the map, movement over time and the procedure for a person in danger. The remaining minutes serve questions, because questions show what the plant really assesses.
Minutes 0-5: meeting goal and floor plan
The opening takes five minutes and ends with showing the plant's floor plan. The presenter asks about three points the director wants to see first and records them on screen. This sets the rest of the demo and gives the viewer a sense of influence.
Minutes 5-15: isometric map and interiors
For ten minutes we show the 2.5D view: hall volumes, vehicles, employees and work locations. The presenter changes the floor of a building, opens the view of one employee and shows how the path looks in the last minutes. The position results from signals of several beacons averaged on the map, and the system works without GPS, which matters inside halls.
Minutes 15-25: replaying seven days in two minutes
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 the director this is the moment when scattered events become one story, and a question about queues at the gate gets a numerical answer, not an opinion.
Entry into the implementation starts with people and gates, without beacons. This is an important argument for a plant that does not want to invest in a beacon network right away.
Minutes 25-35: permits, roles, guest and emergency
In this block we show hazardous-work permits from templates, risks assigned to locations, guest registration at a kiosk with a QR code in the invitation, and SOS and motionless-person alerts on the map with the dispatcher view. Each of these elements is described as an option for the plant, not as a ready set for a specific customer.
Minutes 35-45: questions, risks and the next step
The last ten minutes are for questions and agreeing the next step. The presenter records the IT department's questions, because their answers will go into a separate document and will not be improvised during the demo.
What to show the director and what to leave to specialists
The plant director assesses business risk and visibility, so they do not need protocol details. They want to know whether the system shows the plant in real time, whether it reduces the risk of accidents during hazardous work and whether the pilot can be closed without stopping production. Network, SSO and addressing details go to a separate meeting with IT.
The system works as an independent layer supplementing the customer's existing systems: access control, working time, HR and ERP. The presenter should say this at the start, because a group director will ask about conflicts with systems that already have their owners.
Scale and credibility: what to say about references
A group plant asks about scale, so the presenter gives company figures that are confirmed: 16,000 beacons in installations, 20 implementations and pilots, 531 ha of monitored areas and 100% of pilots moving to implementation. We do not give customer names or figures concerning a specific plant, because they are subject to confidentiality.
It is worth adding that InnerWeb is the producer of software and of industrial beacons with ATEX design for zones 2/22, while auxiliary equipment is purchased and integrated. It does not manufacture access control readers, so it does not compete with the plant's access control supplier.
Conclusions from the concept: five decisions after the demo
A good demo ends with a decision, not a thank-you. In the scenario for a type M plant, after 45 minutes the director has five possible decisions, and each has a person assigned on the plant side and a response deadline.
- approval of a pilot on one hall or one inspection route
- handover of the architecture document and the list of questions to the IT department
- delivery of the plant floor plan for a working version of the map
- naming a coordinator on the OHS and maintenance side
- decision whether the first stage covers people and gates, or also beacons
Checklist
Video
Frequently asked questions
Can the whole system be shown in 45 minutes?
No, and it should not be attempted. The demo covers the map, the recording of movement, permits and the emergency situation, and the other modules are described at the end. A pilot plant assesses the system on a few scenarios, not on a catalogue of functions.
Does the demo require beacons to be installed at the plant?
No. The demo works on the floor plan and on simulated or previously collected data, and entry into the implementation can start with people and gates without a beacon network.
Who should be in the room on the plant side?
The director, OHS, maintenance and security. It is better to invite the IT department to a separate meeting that covers the network, accounts and the architecture document.
Want to see the system on your own floor plan?
We will prepare a 45-minute demo on your plant's floor plan, with three scenarios chosen together with OHS and maintenance.
Let's talk