Assumptions of the scenario
A machinery plant, part of a larger group, is looking for a way to quickly detect when an employee working alone on the shop floor stops moving. This is a conceptual scenario for a plant of the type described above, prepared on the basis of our offer rules, not a report from a completed rollout.
Two parties on the supplier side take part in the talks: a regional partner who knows the plants and the people in the area, and the software manufacturer, who is responsible for the product and rollout support. The plant has one project coordinator on the OHS side and one on the IT side.
Two ways in and why a partner was chosen
Our offer has two ways into a plant. The first is a direct conversation with the plant, a pilot lasting 3 to 6 months and then a full rollout. The second is a rollout by an authorised partner in its region.
The scenario chooses the second way, because the partner knows the local plants and people, and a joint pilot with a partner shortens the path to trust in a new technology. Enquiries recommended by partners also turn into client meetings faster than enquiries from advertisements, which shortens the time from first contact to a demonstration on the shop floor.
Number of transmitters for a 5,000 m2 hall by layout density
Pilot stages step by step
The stages below are a proposed order of work. Actual dates depend on the number of halls, network availability and the plant's decisions.
Stage 1: enquiry and choice of scope
The partner gathers requirements: which workstations are to be covered, where lone working occurs and which zones have poor connectivity. The result is a short pilot scope card with the list of halls, roles and expected alarms.
Stage 2: beacon layout design
The amount of equipment follows a simple rule: in a building, 1 transmitter per 100 to 200 m2, and along plant roads roughly every 100 m. The system calculates position from signals of several transmitters averaged on the map and works without GPS. For a 5,000 m2 hall this gives between 25 and 50 transmitters, which the partner confirms during the site inspection.
Stage 3: installation, configuration and training
The partner installs the equipment and configures roles, the map and stillness alarms, while the manufacturer provides the software and support. Training covers employees and the people who receive the alarm in the control room or at security.
Stage 4: operation under supervision and acceptance
Acceptance of the pilot is based on explicit criteria agreed at the start. The pilot lasts 3 to 6 months. After it ends, a full rollout follows, with a one-off implementation cost and maintenance on subscription.
Which acceptance criteria are worth agreeing
Acceptance criteria should be measurable, not just assessed. Instead of a statement such as the system works well, it is better to agree specific thresholds that the plant team checks against the system report.
The pilot is also an opportunity to test the process after an alarm: who takes the report, how long it takes to confirm it and how escalation works when the first person does not respond.
- coverage of the agreed halls and roads, confirmed by a walk-through with the device
- detection of simulated stillness and delivery of the alarm to the named recipients
- time from the event to confirmation of the alarm by the responsible person
- escalation working up to the next recipient
- system availability during the pilot in line with the maintenance agreement
- no disruption to the plant network
Costs: ranges for the scenario
A typical rollout costs from PLN 12,600 to PLN 34,000 net, one-off, depending on the scope. Licences in the flexible variant cost PLN 80 net per active user per month with a minimum of 10 users. These are indicative ranges from 2025-2026 rollouts; individual quotes apply.
During the pilot the partner invoices everything, including the licences. After moving to a permanent agreement, the licences come from the manufacturer, and the partner continues to invoice the implementation and maintenance.
What a joint pilot gives each side
The plant gets one local contact and access to the manufacturer when a product question has to be settled. The partner builds a reference in its region. The manufacturer gains proof of operation in a new environment, and in past practice 100% of pilots moved on to rollout, out of 20 rollouts and pilots in total.
Video
Frequently asked questions
Does this text describe a completed rollout?
No. It is a rollout scenario prepared for a plant of the type described in the text, based on the rules of our offer.
How long does the pilot last?
From 3 to 6 months. Acceptance is based on explicit criteria agreed at the beginning.
Is GPS needed for the pilot?
No. Position is calculated from signals of several transmitters averaged on the map, so the system also works inside buildings.
Let's plan a pilot for your plant
We will present the scope, the rules for sizing the equipment and the acceptance criteria. Book a call with us or with a partner in your region.
Let's talk