Wireless that works on site – because we measure it first.
Private LoRaWAN networks for pharma, chemicals and industry: measured on site, with two redundant gateways and mobile connectivity from two different carriers. No intervention in the corporate network or control system – and documented so it fits into a qualification.
LoRaWAN radio brings readings out of rooms where you don’t want to – or may not – run a cable. The sensor measures right at the point of interest, the gateway transmits independently of the plant network – no wall penetration, no cable tray, no change to the control system.
Why wireless – and not cable?
With cable
Cable route through ATEX zones – ignition protection and Ex documentation
Penetrations into cleanrooms – approvals, requalification, possibly downtime
Interface in the control system – engineering and change control
Weeks to months of lead time
With wireless sensors
Battery-powered sensor right at the measuring point
No penetration, no cable route, no change to the control system
Autonomous gateway – independent of the plant network
Ready to measure in days
Field record: 3 years of control-room monitoring data
3
years of continuous use
2
min interval
around the clock
788,400
payloads per sensor
3 × 365 × 24 h × 30/h
1.58
million readings
temperature + humidity
15
limit violations
reliably detected and reported
Every violation arrived as an email – before it could turn into a failure.
Where LoRaWAN works
Through walls and ceilingsThe 868 MHz signal penetrates masonry and concrete slabs – even across several floors.
Basements, shafts, technical roomsEven where Wi-Fi and mobile coverage are weak: control rooms, sub-distributions, utility shafts.
Sites and outdoor areasRanges from a few hundred metres indoors up to kilometres outdoors – several buildings on one network.
Cleanrooms and ATEX areasNo wall penetration, no cable tray through the zone. We check sensor suitability for each area per project.
Cold rooms and refrigerationProbe at the measuring point, radio module outside – seals and insulation stay untouched.
Without power or networkBattery-powered sensors with long runtimes, gateway with its own LTE link – no IT approval needed.
How it works
Five steps to a running wireless network
1
Survey the building
We measure radio coverage on site at every planned measuring point – signal strength and quality, even in basements and behind reinforced concrete.
Walkdown
2
Document everything
Readings, gateway locations and antenna planning go into a report. It is the basis for installation – and for qualification in GMP.
Radio report
3
Order the starter kit
The kit arrives pre-configured in a case: gateway, sensors and accessories, neatly packed and ready to go.
In a case
4
Plug in & place
Plug the gateway in – the LTE link is up. Mount sensors by magnet, bracket or cable tie exactly where it’s critical.
Plug & play
5
Log in
Sign in at monicore.one: live readings, set limits, activate email alerts. Done.
Live data
More safety
One gateway to start – redundant when it matters
The number of gateways depends on the building and criticality. Every sensor transmits to all gateways in range; if one fails, the others take over automatically.
1gateway
Start & pilot
Ideal for getting started, one room or one floor.
2gateways
Redundant
Two gateways with SIM cards from two different carriers – our standard for critical areas.
3gateways
Large building
Several floors or long buildings: every measuring point is heard by at least two gateways.
4gateways
Campus & highest availability
Several buildings or a site – coverage with reserve, even while one gateway is serviced.
We deliver it all – from the starter kit in a case to a redundant network ready for qualification.
Alarm e-mail with location, value, duration, max/min and 24 h trend; pre- and main alarm
Review of a silent air-conditioner failure: moment visible in the trend to the minute
Service package from walkdown via FAT/SAT to DQ/IQ/OQ/PQ and training
On-site measurement, network planning
Walkdown report
Reference measurement with mobile gateway on a tripod and test node at every point
LoRaWAN result: all nodes better than −100 dBm = good
Mobile network without external antenna only medium – hence external LTE antenna
Mounting rules for nodes, gateways and antennas; coverage checked near the border
Basics of radio planning
LoRa guide
dB, RSSI, SNR and preamble explained
Link budget example with 151 dB
Attenuation of typical building materials, Fresnel zone, spreading factor and ADR
System components: sensor, gateway, server, application
Own measurement per radio packet
Current measurement & battery life
13.8 mAs (SF7) to 81.7 mAs (SF12) per transmission at 14 dBm
Calculated ≈ 18 years at SF7, ≈ 3 years at SF12 (D cell, every 2 min)
M1 Node therefore designed for up to 10 years
Conclusion: good gateway position = low SF = long life
Walkdowns and reports via QR code
Scan & Forget – QR concept
Identify devices uniquely by QR code
Document safety rounds (e.g. emergency showers) via QR
Fault and maintenance reports straight to the responsible team
Inspection records retrievable instead of paper lists
Sketches based on photos from pilot and starter kit
SketchStarter kit: gateway with LoRa ground-plane and LTE antenna on mounting plateSketchStarter kit with gateway and two wireless sensors with PT100 probeSketchSensor with PT100 probe on a refrigeration unitSketchMounting on a strut channel in a technical roomSketchM1 Node with humidity probe and PT100 cable
Symbolic illustration based on photos from our pilot projects. Series design may differ.
Basics
LoRaWAN explained in five minutes.
LoRaWAN (Long Range Wide Area Network) is an open radio standard of the LoRa Alliance for sensors that send small amounts of data over long distances – battery-powered, for years. It is ideal for industrial sites: signals pass through walls and ceilings, and sensors need neither cables nor network sockets.
Star topology
Each sensor (node) transmits directly to the gateways in range. If one node fails, the others are unaffected – there is no mesh that needs to rebuild.
Licence-free, but regulated
Transmission takes place in the 863–870 MHz SRD band. Each device may transmit at most 1 % of the time (duty cycle) – 36 seconds per hour – at max. 25 mW.
Encrypted
Every message is end-to-end encrypted with AES-128. Each node gets its own keys; without them nobody can read or inject data.
Very low transmit power
Typically 10 mW, max. 25 mW – Wi-Fi transmits at 100 mW to 1 W, mobile networks above 1 W. And a node only transmits for fractions of a second, e.g. every 2 minutes.
Spreading factor: range versus airtime
The spreading factor (SF7 to SF12) “stretches” the radio signal. More stretching means more range – but longer airtime, more battery use and fewer messages allowed per hour. The goal of good planning: the lowest possible SF, i.e. placing gateways so that sensors can use SF7.
Guide values for a short payload at 125 kHz bandwidth. Theoretically up to 5 km (SF7) or 16 km (SF12) – much less in reinforced-concrete buildings. That is exactly why we measure on site.
Choose SF
Airtime per message
max. messages per hour (1 % duty cycle)
Range (relative)
calculated battery life (D cell 19 Ah, every 2 min, 14 dBm)
Life from our own current measurement per radio packet (13.8 mAs at SF7 to 81.7 mAs at SF12) plus sleep current – without self-discharge and temperature effects. That is why we design for 10 years and place gateways so that SF7 is enough.
Radio planning in detail
Why we calculate – and then measure anyway.
A radio network can be described by three properties: range, data rate and energy consumption. In practice, at most two can be optimised. LoRaWAN goes for range and low energy – with a small data rate. Exactly right for readings every few minutes.
Decibels in one sentence
3 dB more = double the power, 10 dB = ten times, 20 dB = a hundred times.
Double the distance = 6 dB more free-space loss.
dB simply add up: 14 dBm transmit power − 2 dB cable + 2 dBi antenna = 14 dBm radiated.
Example link budget
Transmit power14 dBm
Bandwidth 125 kHz10·log(125,000) = 51 dB
Receiver noise figure6 dB
SNR limit at SF12−20 dB
Sensitivity−174 + 51 + 6 − 20 = −137 dBm
Link budget14 − (−137) = 151 dB
151 dB covers very long distances in open terrain. On site, walls, slabs and metal eat up this margin – that is why measuring on site matters.
Fresnel zone
Even with line of sight, the space around the direct line matters: an obstacle in the first Fresnel zone – a pipe bridge, a roof structure – noticeably lowers the level. So gateways go high and free.
What walls cost: typical attenuation at 900 MHz
Glass 6 mm0.8 dB
Glass 13 mm2 dB
Wood 76 mm2.8 dB
Brick 89 mm3.5 dB
Brick 178 mm5 dB
Brick 267 mm7 dB
Concrete 102 mm12 dB
Stone wall 203 mm12 dB
Brick-concrete 192 mm14 dB
Stone wall 406 mm17 dB
Concrete 203 mm23 dB
Reinforced concrete 89 mm27 dB
Stone wall 610 mm28 dB
Concrete 305 mm35 dB
Guide values. Reinforced concrete, metal containers and tank farms can attenuate much more – the walkdown measures the real value.
Adaptive data rate (ADR)
The network automatically sets each sensor’s spreading factor: well-received sensors transmit faster and save battery. Good gateway positions are the prerequisite.
Our planning rules
The link budget sets the maximum range – attenuation is subtracted from it.
Reflections from ground and obstacles affect the level; sensors usually sit close to the ground.
Obstacles in the first Fresnel zone shorten the range.
Sensitivity depends on SNR, noise figure and bandwidth.
In the EU: max. 14 dBm transmit power (ERP 25 mW) and 1 % airtime in the 868 MHz band.
Why at all?
Critical infrastructure often runs blind.
Control, server and infrastructure rooms house PLCs, power supplies, switches and SIL cards – the basis of all production. Yet they are rarely measured. This is what we have seen in many plants:
Split responsibility
Air conditioning, control cabinets and access often belong to different departments. When cooling fails, nobody feels directly responsible.
No fast alarm chain
Maintenance by external contractors, unclear reporting paths – hours or days pass before the right person is on site.
Undefined states
Overheated electronics fail sporadically – from single signal channels to the entire control system. SIL cards can no longer be relied upon.
Alarm flood instead of information
Central collective alarms without clear assignment get acknowledged and forgotten. Room temperature is not a process alarm and does not belong to the operator.
No access, no visibility
Shift staff are usually not allowed into control or server rooms. A problem is only noticed when the control system HMI fails.
Ageing through heat
Permanently high temperature and humidity accelerate component ageing and promote condensation – long before anything fails.
Pilot cases from practice
Three rooms, three causes – reported in time every time.
From our pilot projects in control rooms (since 2022). Each case shows a different radio challenge – and why measuring on site is decisive.
Pilot 1 · Distance
Situation
Room temperatures above +43 °C, sporadic failures of two fixed air conditioners and unmonitored mobile units. The room was not accessible to operations.
Radio challenge
Radio path approx. 400 m line of sight without visibility – across several buildings and a tank farm with metal and reinforced concrete. WirelessHART or Wi-Fi would not have managed it.
Result
Several overtemperatures reliably alarmed, fault service called directly, production losses and component damage avoided.
Pilot 2 · Metal enclosure
Situation
A new air conditioner was switched off manually during a winter inspection – and not switched on again. In spring the temperature rose sharply.
Radio challenge
Several closed rooms made entirely of metal containers – a Faraday cage. Here the problem was not distance but the attenuation of the enclosure.
Result
Overtemperature alarmed in spring before another communication module failed; 24/7 monitoring since then without additional staff.
Pilot 3 · Silent failure
Situation
An air conditioner stopped cooling but kept running without a fault message. Nothing was visible on site.
Radio challenge
A thermostat would only have delivered a switching contact – no trend, no analysis, possibly acknowledged in the control system.
Result
Temperature rise detected and reported by e-mail; the trend shows the moment cooling failed to the minute.
What every alarm e-mail contains
Where: plant, room, sensor with equipment tag
What: current value and exceeded limit
When: start of the deviation and return to the target range
How long and how far: duration plus highest/lowest value
Trend: average, maximum and minimum of the last 24 h
Levels: pre-alarm (warning) and main alarm to defined recipients
What a project includes
On-site walkdown with individual signal measurement of all points
Hardware: nodes, gateways, antennas, SIM cards
Dashboard in MoniCore.one with alerting
FAT (hardware and software) at egatti, SAT at the customer
Qualification documents based on the walkdown report
Commissioning, final report and training
Optional spare parts (nodes/gateway) and extensions
Support throughout the entire term
Approach in pharma
From walkdown to qualification – seven steps.
In regulated environments it is not enough that it works – it must demonstrably work. Many of our FAT and SAT checks are exactly the activities required in installation and operational qualification (IQ/OQ).
01
Requirements & use cases
Which rooms and plants are business-critical? Which measurands, limits, pre-alarms and main alarms? Who is informed when? Is the measuring point GMP-relevant, ATEX-relevant, is a UPS needed?
URS / specification
02
Walkdown on site
Site survey with building plans: measuring points, node and gateway positions and 230 V connections are defined. Reference measurement with a mobile gateway on a tripod and a test node – at every measuring point. Plus mobile network measurement per carrier. Photos and equipment tagging according to customer standards.
Walkdown report = basis of the DQ
03
Network planning
Gateway locations and antenna orientation according to the building structure, at least two gateways per building, SIM cards from different carriers, power supplies on separate circuits. Each node should be received by both gateways.
Network plan, device list
04
FAT at egatti
The entire network is commissioned at our premises first: gateways, nodes, keys, limits, alarm recipients and dashboard. Only after a passed factory acceptance test do we go to the customer.
FAT protocol
05
Installation & SAT
Installation according to specifications, individual signal measurement of each node at both gateways, test of limit alarms, gateway redundancy (one gateway is deliberately switched off) and the e-mail alarm chain.
SAT protocol
06
Qualification (if GMP)
DQ via the walkdown report, IQ for installation and documentation, OQ for function within limits, PQ under real conditions – e.g. limit alarms, gateway redundancy, alarming and optional audit trail.
DQ · IQ · OQ · PQ
07
Operation & support
Watchdog (“last seen”) per node, monitoring of all gateways, battery voltage measured under load once a day, remote configuration and updates, staff training, final report.
Final report, training
Nodes
How we bring sensors into a pharma plant.
A node is a battery-powered wireless sensor directly at the measuring point. It measures, encrypts and transmits – and needs no cable tray, no wall penetration and no interface in the control system. This keeps process alarms and infrastructure monitoring cleanly separated.
Measuring point and equipment tag are defined together during the walkdown – the tag appears on the device, in the dashboard and in every alarm e-mail.
Mounting height from approx. 1.5 m for good range, but max. 1.80 m – so service is possible without a ladder.
Antenna approx. 20 cm from the wall, free of metal housings and reinforced concrete directly at the device; use openings such as windows or doors.
Fixing with magnet, cable tie or screw – without drilling into cleanroom envelopes; temporary measurements are possible at any time.
Each node is checked individually: signal strength (RSSI) and signal-to-noise ratio (SNR) at both gateways, documented in the SAT.
For especially critical points: two independent sensors at the same position (sensor redundancy).
Monitored in operation: last message (watchdog), battery voltage under load, signal strength, packet counter and error status.
Mounting dimensions from our walkdown guidelines
Walkdown: mobile gateway on a tripod, test node at the planned measuring point
Gateway design & resilience
Two gateways, two carriers, two circuits.
The gateway is the heart of the network – so with us there is never just one. Per building we plan at least two independent gateways, each covering the entire building. If one fails or is serviced, the other takes over – without losing a single reading.
Normal operation – both paths active
Network A down – data via network B
Circuit 2 off – gateway 1 takes over
Two independent gateways
Every node is received by both. We show this in the walkdown with measurements at both gateways – not with an assumption.
SIM cards from different carriers
Each gateway has its own LTE SIM from a different provider. If one mobile network fails, data flows through the other.
Separate circuits
The power supplies are on different circuits – optionally on the UPS, so measuring and alarming continue during a power failure.
No intervention in the corporate network
The gateways transmit via mobile network. No firewall rules, no VLAN and no interface in the control system are needed.
External antennas, mounted indoors
LoRa and LTE antennas external to the gateway, installed inside the building – so no lightning protection assessment is needed.
Monitored and remotely maintainable
All gateways are visible in the dashboard; a failure is reported. Settings and updates are possible remotely – important for hard-to-access rooms.
Orienting the antenna correctly
One level
Antenna vertical, gateway as central as possible in the area.
Several floors
Gateway in the middle of the building, antenna horizontal – the “donut” pattern radiates up and down.
From outside
Gateway outside, antenna vertical: windows attenuate less than reinforced-concrete slabs.
Border region
In the DE/CH/FR tri-border area, Swiss cell towers can interfere. We check coverage per carrier in advance.
Measurements, not assumptions
Excerpt from a real walkdown report.
This is what the result of an on-site measurement looks like (anonymised). Each sensor is measured at both gateways – and where one gateway is further away, the other is close. That is intentional.
Measuring point
Gateway 1
Gateway 2
Rating
Control room 1
−56 dBm · SNR 10.25 dB
−77 dBm · SNR 9.75 dB
good
Control room 2
−79 dBm · SNR 10.25 dB
−56 dBm · SNR 9.0 dB
good
Mobile network at gateway location
RSRP −101 dBm · RSRQ −13.5 dB · SINR 4 dB
medium – measured without external antenna → external LTE antenna planned
RSSI
Received signal strength in dBm. The closer to 0, the better. Walkdown rule: all nodes better than −100 dBm = GOOD.
SNR
Signal-to-noise ratio in dB. Positive values are very good; LoRa can even decode signals below the noise floor.
RSRP / RSRQ / SINR
Mobile network indicators at the gateway. They decide whether an external LTE antenna or a different carrier is needed.
Demonstrator 2022–2025
DataDOT ONE – three years of demo in continuous operation.
Note
The DataDOT ONE was our demonstrator in the pilot project. It ran in continuous operation for three years and is not a current product. The platform and solution are called MoniCore.one; the experience from the demo flows into our own sensor family MoniCore M1+.
What the demo showed in real operation – in control rooms of a production building, measuring every 2 minutes:
Temperature and humidity at the measuring point, plus an external PT100 probe (4-wire) with wire-break monitoring
Optional autonomous local alarm with bright LED and buzzer (> 100 dB) – works even if the radio link or gateway fails
Battery voltage measured under load once a day – the real battery condition, not just the open-circuit voltage
Status values online: signal strength, SNR, packet counter, internal temperature/humidity, error status; configuration by remote command
Transmitting at SF7 – thanks to good gateway positions short airtime and long battery life
No. The gateways transmit via mobile network (LTE) directly to MoniCore.one. There is no implementation in the corporate network and no interface in the control system. Connection to your own servers is possible on request.
What happens if a gateway or mobile network fails?
Each sensor is received by two gateways that use SIM cards from different carriers and are connected to separate circuits. If one path fails, data flows through the other. The failure itself is reported in the dashboard.
Is radio exposure an issue?
LoRaWAN nodes typically transmit at 10 mW (max. 25 mW) and only for fractions of a second – at most 1 % of the time, in practice usually below 0.03 %. That is orders of magnitude less than Wi-Fi or a mobile phone.
How long do the batteries last?
It depends on the transmit interval and spreading factor. With good gateway planning (low SF), several years are common. Battery voltage is monitored, so replacement can be planned.
Can the system be qualified?
Yes. Walkdown report (DQ), FAT and SAT provide the basis for IQ and OQ; the PQ tests e.g. limit alarms, gateway redundancy and the alarm chain. We agree the scope with your quality assurance.
Does it work in ATEX zones?
Ex areas require approved devices. Whether and how a measuring point in a zone can be implemented is checked in the project – often it is enough to place the sensor outside and route a probe inside.
Shall we survey your site?
A walkdown with a mobile gateway shows within a few hours how many gateways you need and where – with measurements for every point.