From sensor to decision, in three pieces.
A digitalised network needs three different things, and almost nobody separates them: that everything works together, that everything acts at once, and that someone indicates what to do with that information.
Digitalising a network turns the operator into a systems integrator. That part is ours.
Whoever puts out a telemetry project today ends up doing a job that is not theirs: deciding signals, matching protocols, coordinating six suppliers and taking responsibility when something stops reporting. That work has a name: it is the integration burden, and it is paid for even when it is not in the budget. A field point is five physical layers; we deliver all five, and the burden of each one stays on our side.
Plinth, mast, cabinet and solar bought separately, with panel sizing left to the customer.
They arrive together, and the solar is sized against the worst month at that site.
Consumption, parameters, power and register map. Every brand its own way.
They arrive selected, powered and configured. No datasheet required.
Regulating without breaking anything: water hammer, cavitation and hunting.
They arrive with their control loop and protections already set. And with confirmation that it closed.
The signals are defined one by one, and they have to be right before purchase.
The choice is what to manage and the point comes defined. It decides and acts even if the line drops.
Which technology, how much it draws and which operator covers that chamber. Plus the private network, the credentials and remote updates, left to the customer.
Chosen per site, with tuned consumption and a fallback if the operator drops. As standard: private APN, VPN and signed remote updates.
And the kit does not arrive blank: it arrives with the point already modelled, ready to join the network’s automation. What that software does is the next piece.
One accountable party, from purchase to operation.
ORIONIS builds the equipment. miiwater builds the software. Both sit in the same house, so there are not two suppliers: there is one contract and one point of contact.
- Bought once
The warranty is ours
We build the remotes and the panels, and we warrant them ourselves. For what we buy outside, the manufacturer answers with its warranty as it is. Neither is reduced.
- Commissioned once
Field work, with a certified partner
Installation and maintenance can be done on site by a certified partner. What is bought and who to claim from does not change.
- And from then on, always
One point of contact
One point of contact, not six. And the same engineering team that built the equipment and the platform follows the incident.
Each level contains the one inside it. What is contracted is how far our responsibility reaches.
Monitor, Nebula and SCADA, with day-to-day change requests. This is the scope contracted as Service Desk Standard.
The SIM, the private APN, the VPN and the server where the data arrives. When a point stops communicating, the operator and the machine are our responsibility too.
The RTU and the firmware inside it, with signed remote updates.
The service level for each scope is set in the contract. Service Desk Premium is contracted separately.
Designed for trouble-free operation.
Our equipment is rugged by design, a criterion drawn from field work, not from a catalogue. The experience comes from flooded chambers, canals with no coverage, rooftops at forty degrees and sites only reachable in a 4×4.
What we learned there is not on the datasheet. It is in the product.
- Power
Sized for the worst month, not the best
Solar sizing is done against the least favourable month at that site, not against the annual average. It is the number one cause of silent points in winter.
- Communications
A second communication path
Multi-band cellular switching and fallback. An irrigation network cannot depend on one particular operator having coverage in one particular plot on one particular day.
- Data
Silence raises an alarm too
A point that stops reporting raises an alarm by itself. The absence of data is data — and it is the most expensive kind to ignore.
The typical failure of a telemetered network is not spectacular: it is silent. The battery that does not survive the winter. The antenna that loses coverage when the vegetation grows. The sensor that drifts and nobody notices for eight months. The reading that arrives on time but badly scaled, and on which a whole season is decided. Nine years in the field are worth exactly this: not knowing that it can happen, but having already dealt with it.
The device measures. The network is governed by software.
With the five layers solved, each point does its job on its own. But a network is not the sum of working points: it is all of them doing at the same time what has been decided. No device does that. Software does.
- ON THE POINT ALREADY DELIVERED · PIECE 1
Telemetry
The data arrives, with its timestamp and its unit, from the point to the screen.
- NEEDS TELEMETRY
Remote control
Command capability: open, close, start, stop and change a setpoint from anywhere.
- NEEDS REMOTE CONTROL
Automation
The network acts on its own with the rules set, with nobody having to watch it.
THE RULE THAT RUNS ITSELF
Orchestrating is making one thing depend on another
Good equipment orchestrates nothing on its own. Four rules written once that run unattended:
- The tank calls the pumping station.
- Pressure is modulated with the sector’s demand.
- The hydrant closes if quality goes out of range.
- The pumping station checks the electricity tariff before starting.
The customer sets the rules. We run them and answer for them. If a rule stops doing what it says, that is our responsibility.
Three programs, three jobs, one network: Monitor sees, Nebula plans, SCADA commands.All three, with their screens, in Solutions
Seeing is not deciding. And deciding is worth nothing without action.
A well-orchestrated network provides a reliable screen. The next question is the decisive one: what to do with that information?
A whole network in view: the sectors, the gates, the gauging points and the pumping stations, on one screen. That is seeing. Deciding is what comes next.
- Reading
It works and still generates extra cost
Pumping outside the tariff window, excess pressure, a sector with a steady leak nobody has reviewed. None of the three raises an alarm.
- Recommendation
Not a report: an action
What has to change, what it costs and what is recovered. The three figures, together.
And, if commissioned, we carry it out. The recommendation does not end up in a PDF: it is carried out by the same team that wrote it.
- 20 rules written, 0 live. They are specified by family — water, energy and equipment — and they get built in the order of whoever needs them.
- Advi, in development. It turns the recommendation into a message on the phone: what is happening, where and what to do about it.See Advi in Solutions
How does this translate to your network?
The useful conversation is not about the platform but about the points, signals and integration of each network.
Talk to engineering