InnerWeb
Skip to main content

Safety system demo for the board of an agricultural machinery plant

The board of an agricultural machinery plant, part of a global group, does not need another slide deck. It needs proof that the system works on its own shop floor. We describe a demo scenario on an isometric map with the plant's own data, designed to lead to a pilot discussion. This is a concept and implementation scenario, not a production deployment.

7
steps of the permit wizard shown in the demo
3 s
polling interval of the work feed by the map
Source: IsoMap SOS function documentation
100%
conversion from pilot to implementation in company history
Source: company records

Starting point: the plant, the group and the board's question

A plant producing agricultural machinery, part of a global group, already runs access control, time and attendance, HR and resource planning systems. The board therefore asks one question: what extra value does a system bring that collects signals from transmitters and shows them on the hall map. A slide answer is not convincing, because every vendor promises similar things.

That is why the scenario assumes a demo on a separate demonstration instance, loaded with data from this specific plant. The board sees its own hall, its own building shapes and its own points, not a generic mock-up. The conversation shifts from judging the presenter to judging the product.

Important caveat: we describe a concept for a plant of this type. The demo is not a production deployment and does not touch any operational data of the plant.

What is prepared before the demo

The demo runs on a demonstration instance, separated from production data. It has its own area, its own locations and transmitters marked with an external identifier, so after the demo they can be removed without risk to anything else.

The plant data is limited to three groups: georeferencing of the hall, building shapes and locations with transmitter numbers. Georeferencing is the reference point and the rotation angle of the plan relative to north. Without it the isometric map will not line up with the real site.

  • a separate demonstration instance with its own area and locations,
  • hall georeferencing: reference point and rotation of the plan relative to north,
  • building shapes and locations with transmitter numbers,
  • demonstration accounts in a domain reserved for testing, so no notification reaches a real person,
  • starting and stopping the whole demo with one script that checks the state.

Why a separate instance

A group board will ask about data security within the first minute. The answer is simple: the demo has no access to anything that belongs to the plant, and the demo data is marked and removable.

Sample split of a 30-minute demo

Sample split of a 30-minute demoHorizontal bar chart of a 30-minute demo split into five thematic blocks02468minMap orientationMap orientation: 4 min4Permit in the hallPermit in the hall: 7 min7SOS and stillnessSOS and stillness: 8 min8Visitor and kioskVisitor and kiosk: 5 min5Pilot decisionPilot decision: 6 min6
Source: Sample calculation: time plan of the demo proposed by the author

Demo flow: from the map to the alarm

The demo opens with the isometric 2.5D map in the browser. It shows building shapes, vehicles, employees and work locations, and the data refreshes cyclically. The presenter spends the first two minutes on orientation: where the gate, the assembly hall and the warehouse are.

Next, a work permit is created for the chosen hall. The wizard has seven steps: basic data, dangerous work, tasks, risks, employees, notifications and a summary with a print preview. Risks are assigned to locations, so once the hall is selected the board immediately sees the risks of that place, without manual entry.

The climax is the alarm. The siren and the SOS or stillness marker appear on the map within seconds, because the work feed is polled every 3 s. The plant director sees with his own eyes how fast the information reaches the dispatcher.

Outcome: a pilot conversation instead of a presentation talk

The measure of a successful demo is not the number of compliments, but a change in the questions. After slides the board asks about price and competitors. After a demo on its own data it asks about scope: how many halls, how many employees, which access control system to integrate with, and when it can start.

InnerWeb is an independent system that complements the client's existing systems: access control, time and attendance, HR and resource planning. Localization works without GPS, using signals from several transmitters averaged on the map. This message is worth delivering at the end of the demo, because it removes the fear of replacing the current systems.

To build credibility the presenter may mention company indicators: 20 implementations and pilots and a 100% conversion rate from pilot to implementation. These are general company figures, not a promise for this plant.

Conclusions for presenters of similar demos

The scenario for the agricultural machinery plant leads to a few practical rules. The plant's own data matters more than a striking animation. A separate instance and accounts in a test domain remove security objections. A few short scenes matched to the roles of the participants work better than a full tour of 18 modules.

The most common mistake is overloading the demo. The board decides on direction, not on configuration details, so the details are kept for the pilot.

Video

Frequently asked questions

Is the demo a deployment in the plant?

No. The demo runs on a separate demonstration instance with plant data, separated from production data. It is a deployment scenario meant to support the decision to start a pilot.

What plant data is needed for the demo?

Georeferencing of the hall, meaning a reference point and the rotation angle of the plan relative to north, building shapes, and locations with transmitter numbers.

Does the demo require integration with our systems?

No. Integration with access control, time and attendance or resource planning is discussed only after the demo, within the pilot scope.

Plan a demo on your plant's data

Book a conversation with InnerWeb. We will agree the data scope, the scenario and the date of the demo for your board.

Let's talk