Why the protocol should contain measurements
Coverage measurements are carried out after installation and attached to the acceptance protocol. Without them, acceptance rests on the contractor's declaration, and the inspector has nothing to check.
The protocol does not promise compliance with any requirement. It provides evidence for an audit: what was measured, where, when and with what result, so that after a year someone can repeat the measurement and compare.
What to measure: three groups of measurements
The first group is the inventory: the number of installed beacons, their identifiers and their positions recorded in the database. Agreement of the record with reality is a condition for a correct route, because the route is a path between positions recorded in the database.
The second group is audibility: at control points along the traffic routes, record how many beacons the phone or watch receives and with what strength. The third is position deviation, that is the difference between the position shown in the system and the known position of the control point.
- inventory: number, identifiers, positions in the database
- audibility: number of audible beacons at the control points
- position deviation: difference from a known point
- control routes: continuity of the walk without jumps
- cellular network or Wi-Fi coverage, because the device sends signals every few seconds
- date, contractor, measurement conditions
Position deviation in a simulation for beacons spaced 100 m apart
How to read the deviation: an example from a simulation
In a simulation for beacons placed every 100 m, the average position deviation was 15 m and the maximum 39 m. This is an assumption for plant roads over a large area, not a value for a hall with a dense grid.
The protocol does not copy such figures as a requirement. Instead, the acceptance threshold is agreed with the client before installation, and the simulation is treated as a point of reference. A deviation above the threshold does not prove an error; it only indicates the places to densify.
Density as the context of the result
On plant roads beacons are placed about every 100 m, and inside buildings at a density of 1 beacon per 100 to 200 m2. The measurement result has to be set against this density, because a deviation in a hall with a 15 m grid and on a road with 100 m spacing means different things.
For a hall, the adopted design assumption is 1 point per 225 m2 (15 m grid, minimum 4), and for mezzanines 1 point per 15 m of length. The rules require validation in the field, and the acceptance protocol is exactly such a moment of validation.
Sample calculation: threshold and control points
Assume a hall with 24 beacons and 12 control points. The client and the contractor agree that at 10 of the 12 points the deviation should not exceed the working threshold. These are sample assumptions, not normative values.
If the measurement shows 9 compliant points and 3 outside the threshold, the protocol records the result as 9 out of 12 and indicates three places for correction. After densifying the grid in these places, the measurement is repeated only for them, which shortens acceptance.
Checklist
Video
Frequently asked questions
Does the acceptance protocol have a required template?
The template is set in the contract with the client. The content of this page is best practice that helps the inspector check the result.
Is a 15 m deviation a requirement?
No. It is the result of a simulation for a 100 m spacing. The acceptance threshold is agreed with the client for a specific hall and grid density.
Who carries out the measurement?
Usually the integrator together with maintenance, while the supervising engineer verifies selected points. It is important that the method is repeatable.
Let us prepare the acceptance protocol together
Talk to the InnerWeb team about acceptance measurements for a beacon network. We will help set the control points and the acceptance threshold.
Let's talk