What happens to measurement and alarming when mains power or the network drops?

Measurement points keep recording on their own battery buffer for days, data is stored locally and synchronised afterwards, and alarming uses a path that is independent of the building network, such as automatic mobile failover.

Who is accountable when sensors, software and service come from different suppliers?

One contract, one accountable party for sensors, gateways, software, calibration and support, with purpose-built sensors validated against the platform rather than generic parts bolted on.

What does it cost in time and money to add a second site, a new department or fifty more points?

The same platform scales from one room to a multi-site estate, with central oversight and local ownership, and new points are added without a separate project or a second system.

Can we connect existing equipment, building management and laboratory systems without replacing sensors?

Open interfaces, a documented REST API, support for existing sensor signals and equipment outputs, and export formats your quality system can consume.

Who responds at three in the morning, and to what exactly?

A clear split: the supplier watches the monitoring system itself around the clock and fixes technical failures, while your own on-call team is alerted to asset deviations through automated cascading escalation that keeps calling until somebody acknowledges.

Back to the library

Buyer guides

Compare environmental monitoring systems by vertical

The right evaluation depends on what you are protecting. These guides name the categories of system on the market, the suppliers buyers typically shortlist, and the criteria that decide whether a platform will still fit in five years.

Talk to a XiltriX advisor Browse the full library

Seven criteria that separate systems

Sensor accuracy is a threshold requirement, not a differentiator. The real differences show up under failure, at night, and in front of an auditor.

Independent measurement
Sensors belong to the monitoring system, not to the equipment being watched.
Continuity under failure
Battery-backed points, local buffering and alarming that does not share the same power or network as the equipment.
Escalation, not notification
A chain that keeps reaching the next person until somebody acknowledges the alarm.
Evidence quality
Tamper-evident audit trail, server-side timestamps and exports an auditor can read.
Validation support
IQ/OQ/PQ documentation, traceable calibration and a change-control path that does not force re-validation for every sensor.
Parameter coverage
Temperature, CO₂, O₂, humidity, differential pressure, particles, LN₂ level, door status, air flow, VOC, H₂O₂, light and power.
Who owns the response
XiltriX Resilience watches the monitoring infrastructure 24/7. Your own on-call team responds to asset deviations through automated cascading alerts.

Evaluation checklist

Five questions to ask every supplier on your shortlist

These questions are vendor neutral. Ask them of every system you are reviewing, including ours, and compare the answers side by side. The differences that matter are architectural, and they are visible long before a purchase order.

1
Ask
What happens to measurement and alarming when mains power or the network drops?
What a strong answer looks like
Measurement points keep recording on their own battery buffer for days, data is stored locally and synchronised afterwards, and alarming uses a path that is independent of the building network, such as automatic mobile failover.
What should worry you
Monitoring stops with the power, the gap in the record has to be explained later, or alarming depends entirely on the same LAN and switches as the equipment being watched.
2
Ask
Who is accountable when sensors, software and service come from different suppliers?
What a strong answer looks like
One contract, one accountable party for sensors, gateways, software, calibration and support, with purpose-built sensors validated against the platform rather than generic parts bolted on.
What should worry you
Hardware from one vendor, software from another and installation from a third, so every incident starts with establishing whose responsibility it is.
3
Ask
What does it cost in time and money to add a second site, a new department or fifty more points?
What a strong answer looks like
The same platform scales from one room to a multi-site estate, with central oversight and local ownership, and new points are added without a separate project or a second system.
What should worry you
Each site becomes its own installation with its own database and its own login, and growth is quoted as a new implementation every time.
4
Ask
Can we connect existing equipment, building management and laboratory systems without replacing sensors?
What a strong answer looks like
Open interfaces, a documented REST API, support for existing sensor signals and equipment outputs, and export formats your quality system can consume.
What should worry you
Only the supplier's own sensors are supported, integration is a custom project, or your data can only leave the system as a screenshot or a manual report.
5
Ask
Who responds at three in the morning, and to what exactly?
What a strong answer looks like
A clear split: the supplier watches the monitoring system itself around the clock and fixes technical failures, while your own on-call team is alerted to asset deviations through automated cascading escalation that keeps calling until somebody acknowledges.
What should worry you
Vague promises of round-the-clock monitoring without a written boundary of who acts on which alarm, or notifications that stop after one unanswered message.

Sensor accuracy will look similar across every quotation you receive. Continuity, accountability, scalability, openness and response are where systems genuinely diverge.