Most facility managers we speak to already know they need better data. They've had the overflow incident, the 2 AM pump failure call, or the audit that exposed gaps in their water usage records. The technology case is clear to them. What stops them isn't scepticism about whether monitoring works — it's anxiety about what getting there actually involves.
Three specific fears come up in almost every pre-purchase conversation: the installation will disrupt operations, remote sites won't have reliable connectivity, and the new data won't integrate with existing software without a major IT project. All three are understandable concerns rooted in real experiences with older technology. All three have been largely solved by how modern monitoring systems are actually built. Let's work through each one.
Barrier 1: "The Installation Process Will Disrupt Production"
The Fear
The mental image most facility managers carry into this conversation is based on how sensor installations used to work: scaffolding, welding brackets onto pressurised vessels, draining tanks before any hardware could go in, and production halts while the work got done. That was a real constraint for an older generation of hardwired, contact-based monitoring equipment.
The Reality
Modern non-contact sensors — radar and ultrasonic units designed specifically for retrofit deployment — mount externally on top of the tank without any contact with the water or the internal tank structure. No draining. No cutting into the tank wall. No plumbing modifications. The sensor attaches to the tank exterior, the connectivity module clips into place, and the unit is live.
The Solution
A typical single-tank installation for a Water Tank Monitoring System runs between two and four hours for an experienced installation team, including initial configuration and connectivity testing. Multi-tank sites scale proportionally. Most deployments we've managed have been completed during a standard working day without any production stoppage — the installation happens alongside normal operations, not instead of them.
The honest exception: hardwired systems in facilities with specific industrial requirements do occasionally need more involved installation. But wireless, battery-powered sensor setups — which cover the majority of commercial and industrial use cases — simply don't carry the disruption risk that's keeping facilities on manual monitoring longer than makes sense.
Barrier 2: "My Sites Are Too Remote for Reliable Connectivity"
The Fear
This is the most technically grounded of the three concerns, and it's the one where real-world experience with consumer IoT products causes the most damage to expectations. Wi-Fi-based smart home sensors genuinely do fail in environments with thick concrete walls, metal tank structures, and rooftop or basement installations. If that's your reference point for "IoT connectivity", remote site anxiety makes complete sense.
The Reality
Wi-Fi was never the right connectivity choice for industrial monitoring environments. The protocols built specifically for this application operate on completely different physics.
LTE-M and NB-IoT are cellular standards designed explicitly for IoT devices in environments where standard 4G data connections are unreliable or unavailable. They operate at lower frequencies than standard cellular, which means better penetration through building materials and significantly extended range in areas with weak signals. Battery efficiency is dramatically better than standard cellular too — LTE-M devices can run for years on a single battery because the protocol is built for low-data, low-power transmission cycles rather than continuous streaming.
LoRaWAN operates on unlicensed sub-gigahertz frequencies that penetrate concrete, metal, and complex building structures at ranges that standard Wi-Fi can't approach. For a campus with multiple tanks distributed across several buildings, a single LoRaWAN gateway positioned appropriately can serve every sensor on the site — including basement sumps, rooftop tanks, and any structure between them.
The Solution
For genuinely remote sites with limited cellular infrastructure, Remote Water Tank Monitoring with 4G using LTE-M is typically the most reliable path — these devices connect to the same cellular towers that standard mobile networks use but communicate more efficiently and at a longer effective range. For multi-tank campus environments, a Water Tank Level Sensor with a LoRa setup eliminates per-device cellular dependency entirely. The right choice depends on your specific site topology, which is exactly why a pre-deployment site compatibility check matters before hardware selection.
Barrier 3: "Integrating the New Data Into My Old Dashboard"
The Fear
"Dashboard overload" is a real operational problem in facilities that have accumulated monitoring tools over the years — one system for energy, another for HVAC, a third for access control, and now potentially a fourth for water. Staff already overwhelmed by multiple platforms don't need another screen to check, and IT teams don't want another bespoke integration project sitting in the backlog indefinitely.
The Reality
This concern accurately describes first-generation IoT monitoring platforms, many of which were designed as standalone products that generated their own proprietary dashboards with no external integration capability. That design philosophy has largely been abandoned by serious industrial monitoring vendors because it became the primary reason customers didn't renew.
The Solution
API-first design means the monitoring platform is built to feed clean, structured data into whatever system your team already uses — BMS, ERP, SCADA, or CMMS — rather than competing with it for attention. The water data shows up in your existing operational console as one more data source, not a new destination everyone has to remember to navigate to separately.
The practical test to apply to any vendor during evaluation: ask specifically whether the platform supports MQTT data streaming and REST API access, whether there are documented integration guides for your existing software stack, and whether they've deployed integrations with your specific BMS or ERP before. Vendors with genuine API-first architecture will answer these questions directly. Those still selling standalone, proprietary dashboards will deflect.
How to Conduct a Low-Risk Pilot Test
The single most effective way to overcome all three barriers simultaneously is to stop trying to solve them theoretically and run a bounded pilot instead.
Pick one tank — specifically the one causing the most operational problems currently, whether that's the most overflow-prone, the one driving the most emergency pump calls, or the one on the site with the most connectivity uncertainty. Deploy a single sensor on that tank and run it for 60-90 days before making any broader commitment.
This approach proves the installation timeline against your actual site conditions, validates connectivity in your specific environment rather than on a spec sheet, and gives your IT team a contained integration to test against your existing software stack without a full deployment on the line. The ROI case from a single problematic tank over 90 days is almost always sufficient to justify the broader rollout — and if it isn't, you've learned that at minimal cost rather than after a facility-wide commitment.
Building the Team's Buy-In
The human dimension of technology adoption in facilities is consistently underweighted in deployment planning, and it's the factor that most often determines whether a system gets used properly after installation.
Maintenance teams that have built their professional routines around manual rounds — checking, logging, verifying — can reasonably experience monitoring automation as a threat to those routines rather than a tool that helps them. Framing matters considerably here. The relevant message isn't "We're installing sensors so management can see what's happening without sending you." It's "We're eliminating the three hours a week you spend checking tanks so you can spend that time on work that actually needs your expertise."
Staff who understand that automated monitoring removes the most tedious parts of their job — and that alerts will be going to them first, giving them more lead time to address problems before they escalate — typically become the system's strongest internal advocates rather than its sceptics.
FAQ
Can sensors really be installed without draining the tank first?
For non-contact external mounting, yes — the sensor never enters the tank interior, so there's nothing about the installation process that requires the tank to be empty or offline. Older contact-based sensor types that mount internally did require draining, which is part of why that design has been largely superseded for retrofit applications.
What happens to monitoring if the cellular network goes down temporarily?
Quality systems store data locally on the device during connectivity gaps and sync automatically when the connection restores, so brief outages don't create monitoring holes in the historical record. For safety-critical applications, edge-processing capability ensures local automated cutoffs continue functioning regardless of cloud connectivity status.
How long does it actually take to integrate sensor data with an existing ERP?
For platforms with mature API documentation and standard integration patterns, a basic connection to common ERP systems typically takes an IT team a few days to a week. Custom integrations with older or highly modified legacy systems take longer and benefit from direct vendor support during the process.
Does the pilot approach work for multi-site portfolios or only single facilities?
It works at both scales — for a portfolio, the pilot is typically one entire site rather than one tank, which gives you the integration and multi-sensor deployment experience you need to template the rollout across remaining sites.
What's the warranty and support expectation for industrial-grade sensors?
Enterprise-grade sensors typically carry 2-5 year hardware warranties, with OTA firmware updates included. Confirm specifically what the support response time commitment is for connectivity or hardware issues before purchase — particularly for remote sites where a slow support response has real operational impact.
Conclusion
The barriers that keep facilities on manual monitoring longer than makes sense aren't really about the technology anymore – they're about the version of the technology people encountered five or ten years ago, before wireless deployment, industrial-grade connectivity protocols, and API-first integration design became standard. The implementation experience today is genuinely different. Technology is only as good as its implementation, and when you choose the right partner, installation becomes the easiest part of the journey.
Not sure how your site layout handles connectivity? Request a Free Site Compatibility Check today and get a clear picture of what deployment actually looks like for your specific infrastructure.
Top comments (0)