Who these recommendations are for
We address these recommendations to plant directors, process safety managers, fire protection managers and those responsible for the explosion protection document. They apply to plants with an explosive atmosphere: chemicals, fuels, gas, mills, sugar factories, paint shops and wood processing. We assume the plant already has an explosion risk assessment, a zone classification (gas 0, 1, 2; dust 20, 21, 22) and marked areas in line with the Polish Minister of Economy regulation of 2010 (Journal of Laws 2010 No. 138, item 931).
Seven recommendations
The order follows the order of decisions: from risk inventory to supplier requirements.
1. Start with a risk map, not a product
Mark on the site plan which Ex zones require knowledge of who is present, which roads supplier vehicles use and where people work alone. Only this map tells you how many beacons you need and in which versions.
2. Keep the Ex equipment you already have
Replacing Ex phones and detectors means cost and new certificates. Require the supplier to make location work on the plant's own terminals (in the described case Android 9 or 11, BLE 4.2), and require the app's operation on your phone model to be confirmed on the device before purchase.
3. Check beacon certificates at zone level
The device must have the category appropriate to the zone (Directive 2014/34/EU). The InnerWeb industrial beacon is available in an ATEX version for zones 2 and 22. For zones 1 and 21, certification is commissioned for the needs of the installation, with no promised date, so put that in the schedule.
4. Demand an open description of the position algorithm
Ask the supplier for proof that location works without GPS and for a description of how the position is produced. A solution that averages the signals of many beacons on the map is more resistant to reflections than one that picks the strongest beacon.
5. Treat the system as an overlay independent of the permit system
The permit system authorises work but does not confirm who is actually in the zone. A location overlay adds that knowledge without replacing current systems. Integration should be an option, not a condition for starting, and its scope is agreed when a real need arises.
6. Separate what the system does today from what depends on third parties
Gas readings from detectors depend on the manufacturer's protocol. The evacuation route and assembly point are not functions of the system: the system shows a list of people and their last position. Write these boundaries into the specification.
7. Show the concept on the geometry of your own site
A generic diagram proves nothing. Ask for a demonstration on the outline, roads and buildings of your plant, with an estimate of the number of beacons and the expected deviation. Also establish whether the data should run on the plant's server or in the cloud.
Position deviation in simulation, beacons every 100 m
The most common mistakes when choosing a system
The first mistake is buying beacons before checking what equipment people will use: it then turns out that the plant's Ex phone has an older operating system or limited BLE support. The second is assuming that one supplier should replace all of the plant's systems; complementing and tightening existing solutions is cheaper and faster. The third is failing to agree with the Ex department, which is responsible for installation permits in zones and plans shutdowns.
The fourth mistake is ignoring power and maintenance: battery-powered beacons last several years, but replacing them must have an owner and a date in the inspection plan.
How to start within a month
A practical sequence: one week for the risk map and equipment list, one week for a concept demonstration on the plant plan, two weeks for agreement with the Ex department and choosing the pilot scope. The pilot covers one installation or one access road with a few buildings, so that deviations can be measured and the app checked on the phone in use before the plant decides on covering the whole site.
What these recommendations give you in an audit
Each of the seven recommendations leaves a documentation trail: a risk map, a list of certificates, confirmation of a test on the equipment, a description of the algorithm, the integration scope and a calibration record. Such a set supports meeting the requirement for risk assessment and coordination of work by multiple employers, and provides audit evidence. It does not replace the explosion protection document or the decision of the operations manager.
With distances of kilometres, the scale of deployment also matters: on plant roads beacons are mounted about every 100 m, in buildings 1 per 100–200 m². In a simulation for such spacing the mean deviation was about 15 m and the maximum about 39 m; require similar figures from the supplier for your site.
Checklist
Video
Frequently asked questions
Do we have to change the permit system?
No. Location works as an independent overlay, and integration is done only when the plant has such a need.
Which zones are the beacons for?
The InnerWeb beacon is available in an ATEX version for zones 2 and 22. For zones 1 and 21, certification is commissioned for the needs of the customer's installation.
Does the data have to go to the cloud?
No. The plant chooses where the system runs: its own server or the cloud, and the data stays with the customer.
Sources
Let us talk about Ex zones in your plant
We will go through the risk map and the list of equipment that can stay. Book a conversation with the InnerWeb team.
Let's talk