Explained twice. Once plainly, once properly.
The person who signs for this and the person who has to live with it are rarely the same person. So everything below is written both ways — switch between them wherever you see the toggle.
From the thing in the pipe to the phone in your hand
Five links. Everything else on this page is detail about one of them.
Something that can sense
A pressure sensor on a pipe, a level sensor in a tank, a meter on a supply, a protection relay on a motor. Often you already own most of them. Where one is missing, we specify and fit it.
A small unit in your panel
It reads every instrument continuously, runs the automatic rules on site, operates the pumps and valves you allow it to, and keeps its own record — so even if the internet drops, nothing stops and nothing is lost.
A one-way door outward
The unit reaches out to us over mobile data, network cable or Wi-Fi. Nothing at your site sits waiting for the internet to call it. That is the single most important sentence on this page.
Where the memory lives
Every reading is stored permanently, compared against the limits you set, and analysed for the slow drifts a person would never spot. When something crosses a line, it raises an alert.
The app, the alerts, and the control
Each person on your team gets their own login, their own permissions and their own place in the record. They see the live site, the history behind it, and the controls they are allowed to use — from anywhere.
Signal types accepted
4–20 mA (loop- or externally powered) · 0–10 V · 0–5 V · pulse and reed-switch · volt-free contacts · 110–420 V AC opto-isolated status · I²C, SPI and 1-Wire on the local bus · RS-485 multi-drop.
Instruments are ranged and calibrated to the application. Loops are galvanically isolated; calibration records are handed over at commissioning.
Acquisition, logic and autonomy
16-bit ADC with programmable gain · relay outputs · analogue speed reference out to VFDs · battery-backed RTC · local buffering to SD · multi-core real-time execution.
Control logic executes on the controller, not in the cloud — connectivity loss degrades visibility, not operation. Buffered data backfills on reconnection.
Outbound-initiated, encrypted
Cellular LTE · Ethernet · Wi-Fi · MQTT over TLS · HTTPS · no inbound listening ports at site · no port forwarding or inbound NAT rules required on your network.
Where cable will not reach — remote wells, reservoirs, outbuildings — battery-powered mesh nodes over an AES-128 self-healing link report into a site gateway.
Ingest, archive, analysis
Telemetry ingest · full-resolution historical archive · threshold and escalation engine · assisted trend analysis · role-based access control · encryption in transit and at rest.
The platform is our own rather than resold, so a change you need at the ingest, the alerting or the analysis layer is a development item rather than a vendor request.
Access and accountability
Native iOS and Android apps · desktop administration console · MFA on login · permissions scoped by user, department and zone · complete audit trail of every command, setpoint change and configuration edit, exportable for review.
Your facility already speaks several languages
A single-protocol controller forces you to buy new instruments. Carrying all of them at once is what lets a 1990s mechanical meter, a BACnet chiller, an energy meter and a gas detector head appear on one screen at one site.
| Interface | What it connects | Typical equipment |
|---|---|---|
| 4–20 mA · 0–10 V · 0–5 V | Analogue field instruments, isolated loops, 16-bit acquisition | Pressure and level transmitters, flow meters, gas detector heads, valve and damper actuators |
| Modbus RTU (RS-485) | Multi-drop serial networks, bulk register reads | Motor protection relays, variable-speed drives, power and energy meters, water-quality analysers |
| Modbus TCP/IP | Networked devices and third-party register maps | PLCs, existing SCADA gateways, networked meters |
| BACnet/IP | Building-automation objects and properties, device discovery | Chillers, air handling units, VAV controllers, third-party BMS head-ends |
| Pulse & dry contact | Counting and state, including volt-free contacts | Mechanical water meters, float switches, fire panels, door and occupancy contacts |
| 110–420 V AC opto | Isolated mains-voltage status sensing | Motor run and trip status, contactor state, starter feedback |
| Relay outputs | Switched control, within safe limits | Pump start/stop, lighting contactors, gates and barriers, ventilation |
| Wireless mesh | AES-128 self-healing field mesh, 20–200 nodes per facility | Battery sensor nodes and zone gateways where cable cannot reach |
| Cellular · Ethernet · Wi-Fi | Outbound-only uplink over MQTT and HTTPS/TLS | The site's connection to the platform — no inbound ports opened |
The practical test. If the equipment in your plant room or on your roof has terminals, a serial port or a network connection, the answer is almost always yes — and we tell you plainly at survey stage if it is not.
Security at the forefront
Security here is not a feature added at the end. It runs through every link of the chain above — and underneath all of it sits protection that does not depend on software, the network, or us.
Identity
Multi-factor authentication on every login. Permissions granted by user, department and zone, so each person reaches exactly what their role requires. No shared accounts, no shared passwords on a whiteboard.
Network posture
Connections are encrypted and always initiated outward from your site. Nothing at the facility listens for inbound traffic, so there is no exposed port for anyone to find — including us.
Accountability
Every command, setpoint change and configuration edit is recorded with who, what, when and from where — a complete audit trail, exportable for OSHA, ISO or internal compliance review.
Protection in physics, not only in software
Beneath everything above sits independent hardware protection — motor protection relays, pressure switches, a physical kill-switch and a LOCAL/REMOTE selector. Turn the selector to LOCAL and the site is yours alone, regardless of what any network, platform or person does next. Plant and people stay safe even in the scenario nobody plans for.
A dedicated InCon Security Brief is available on request.
What actually happens, in order
Site survey
We walk the facility with your team, catalogue every instrument, panel, drive and protection device installed, and identify which signals can be read today and which need an instrument added. Typically half a day to a day.
Parameter & integration plan
A written scope: which parameters go live, over which interfaces, what ties into your existing systems, what is added, what it costs, and what it will do for you. You read this before committing to anything.
Panel, instrumentation and install
Enclosure, protection, signal isolation and wiring by our own electrical engineers. Work is planned around your operation — most installations are done without taking plant out of service.
Commissioning & calibration
Every loop verified end to end, every alarm tested, every automatic action proven, calibration recorded and handed over. Nothing goes live on an assumption.
Training & handover
Your team gets their logins, their permissions and the training to use them — including the people who will be woken at 2 a.m., because they are the ones who matter most.
Managed engineering
We stay. Thresholds get tuned as you learn what normal looks like, and our engineers watch the system alongside yours as the facility changes.
The things people actually ask
Do we have to replace our existing control system?
No, and we would usually advise against it. We read what is already installed and add what it never provided — mobile access, alerting and history — without altering the control logic that keeps your plant running. Replacement is a last resort, not a starting position.
Do we need a SCADA team or an IT department to run this?
No. The system is designed to be used by the people who already run your facility, from a phone. Configuration, tuning and updates are handled by us as part of the managed engineering layer.
What happens if the internet goes down?
Nothing at the facility stops. Control logic runs on the equipment at your site, not in the cloud — so pumps keep being controlled and protection keeps working. Readings are stored locally and fill back in automatically when the link returns. You lose visibility for that period, not operation.
Does this open our site up to being hacked?
The site never accepts an inbound connection. Equipment reaches outward over an encrypted link, which means there is no open port for anyone to find or attack. Add to that multi-factor login, permissions by role and zone, a complete audit trail — and, underneath all of it, hardware protection and a physical LOCAL/REMOTE selector that works whatever the network does.
How disruptive is the installation?
Most work is done alongside normal operation. Where a shutdown is genuinely unavoidable, it is identified in the written plan before you commit, and scheduled around you rather than around us.
Can we start small?
Yes, and most clients should. A single pump set, plant room, chiller or floor can go live first to prove the return, then extend across the property on the same system with nothing thrown away.
Are we charged per sensor or per point?
No. There is no per-tag or per-point licence to renegotiate as the system grows. Adding parameters, zones and sites is an engineering decision, not a commercial event.
Are you tied to one manufacturer's equipment?
No. Where our own platform is the right answer we use it, and where third-party PLC or control hardware suits your standards, your existing estate or the process better, we specify that instead — then integrate the two into a single view. Both are industrial-grade; the difference is fit, not quality. Being able to combine them is usually what produces the stronger result.
Ask us for a working demonstration
Not a slide deck — a live facility on a phone, showing real pressures, temperatures and plant status, updating while you watch. It is the fastest way to understand all of the above.