Pilot — RO/CIP Monitoring
Prove RO/CIP monitoring on one skid
before standardizing it.
A fixed-scope pilot on hardware you own, priced from the public price list, run entirely on your network — ending in a decision gate, not a renewal trap. Site review, I/O map, labeled install, cleaning-cycle records, operator handoff.
IN PRODUCTION — the same stack monitors RO membrane-cleaning skids at Falcon Water Technologies, Conroe TX · since 2025 · now Phase 3, OEM-in-BOM
Fit Criteria
This pilot fits if three things are true.
If they are, the deployment is boring — in the good way. If one isn't, the site review will say so before you spend anything on hardware.
An RO or CIP skid with 4-20 mA instruments
The pilot reads the loop instruments you already have — pressure, flow, temperature, conductivity. Terminal Indi wires directly to 4-20 mA transmitters.
On-site Wi-Fi/LAN — or willingness to add an AP
Terminal Indi talks to the Base Station over your private 2.4 GHz Wi-Fi or LAN. No cloud, no SIM cards. One access point near the skid is usually enough if coverage is thin.
Mains power at the skid
Terminals take 9-36 V industrial power from the skid. No battery logistics, no power run across the yard.
Not sure what the platform does on a skid? Start with the CIP Monitoring Skill.
Scope
What the pilot delivers.
Site review
A structured review of the skid, its instruments, and the network — remote first, confirmed on-site.
I/O map
Every monitored loop documented: instrument, range, Terminal channel, and label. This document is yours.
Base Station on your network
One on-site ARM64 server running the full stack — dashboards, alerting, historian, RBAC — with no cloud dependency.
Labeled Terminal install
Terminals mounted on the skid, wired to your instruments, labeled to match the I/O map.
Cleaning-cycle dashboard + records
Stage-aware monitoring — Clean, Soak, Flush, Rinse — with per-vessel state, overpressure/overtemp banners, alerts, and logged cycle records.
Operator handoff
A working session with your operators on the dashboard, alerts, and records — not a PDF and a phone number.
Worked Example
Priced from the public price list.
No pilot-special pricing.
Example: one skid, three Terminals covering six 4-20 mA instrument points. Your point count sets your Terminal count — the arithmetic is the same either way, and it matches the pricing page.
Excluded: sensors and transmitters, cabling and conduit, travel, tax, and shipping. Services beyond the fixed scope are agreed before work starts.
Timeline
Days on-site — once the network and instruments are confirmed.
The honest version: the install is fast because the scoping is done first. Wiring to your instruments and confirming your network is real work — we do it up front, not on the invoice afterward. See how deployment works.
Scope
Site review and I/O map, mostly remote. We confirm instruments, network, and power before anything ships.
Install
Days on-site once network and instruments are confirmed — Base Station on your network, Terminals mounted, wired, and labeled.
Baseline
An agreed window of normal cleaning cycles, logged stage by stage, with operators using the dashboard.
Decision gate
A review against the success criteria set at kickoff. Standardize, expand, or stop.
Responsibilities
Who does what.
Modulink
- Site review and I/O map
- Base Station configuration on your local network
- Terminal mounting, wiring to existing instruments, labeling
- Cleaning-cycle dashboard, alerts, and records setup
- Operator handoff session
Your team
- Site access and an operator contact
- On-site Wi-Fi/LAN reaching the skid (or one added access point)
- Mains power at the skid
- Instrument documentation (or access to read nameplates)
- New sensors, loop wiring, or conduit, if the I/O map calls for them
Safety Boundary
Non-safety-critical control. Stated plainly.
Modulink is monitoring and non-safety-critical control. Where a Terminal actuates a valve or motor, safety trips live in the Terminal's firmware, local to the device — they never depend on the radio, the network, or the Base Station. Your existing safety interlocks, relief valves, and shutdown hardware stay exactly where they are.
More on posture: security and data ownership.
Decision Gate
The pilot ends in a decision,
not a renewal trap.
Success criteria are set at kickoff and reviewed at the gate — for example: every cleaning cycle in the baseline window logged stage by stage, operators using the dashboard unprompted, and alerts firing on the conditions you defined. Then you pick one of three paths.
Roll the same design across the rest of your skids — the I/O map and install pattern are the template.
Add points, Terminals, or integrations on the same Base Station — Modbus TCP to an existing SCADA/PLC runs at the Base Station.
Keep the hardware you bought and your data. Exports stay open — MQTT, REST, Prometheus. If the Skill license lapses, it goes read-only; the platform never bricks.
FAQ
The questions a controls engineer asks first.
How many instrument points can a pilot cover?
Each Terminal Indi reads two 4-20 mA loop instruments and drives one H-bridge output for valve or motor actuation. A typical single-skid pilot runs two to four Terminals — four to eight instrument points. Larger skids are scoped the same way, Terminal by Terminal.
Do we need new instruments?
No. The pilot is designed around the 4-20 mA transmitters already on your skid — pressure, flow, temperature, conductivity. If the I/O map identifies a loop that needs a new sensor, that sensor and its wiring are excluded from the pilot price and quoted separately.
What does the network requirement actually mean?
Terminal Indi talks to the Base Station over your on-site 2.4 GHz Wi-Fi or LAN — a private, local connection. No cloud, no SIM cards. If the skid area has no coverage, adding one access point is usually enough, and we flag that during the site review.
Who does the install?
We do, as part of the pilot: Base Station setup on your local network, Terminal mounting, wiring to existing instruments, and labeling. Your team provides site access and an operator contact. New loop wiring, conduit, or instrument changes are handled by your electrician, or by us at $200/hr.
How do we get data out?
The Base Station exposes MQTT, a REST API, and Prometheus metrics on your local network. Modbus TCP to an existing SCADA/PLC is available as a Base Station integration. Everything stays on-site unless you send it somewhere.
What is the fail-safe state?
Modulink is monitoring and non-safety-critical control. Safety trips live in Terminal firmware, local to the device — they never depend on the radio, the network, or the Base Station. Your existing safety interlocks and relief hardware stay exactly where they are.
What happens at the decision gate?
You standardize, expand, or stop. There is no lock-in: the platform runs on hardware you own, the data is yours, and exports stay open via MQTT, REST, and Prometheus. If you stop and a Skill license lapses, the Skill goes read-only — the platform never bricks.
Are there hidden services fees?
No. The price example on this page lists its exclusions up front — sensors, cabling, travel, tax, and shipping. Any services beyond the fixed pilot scope are billed at $200/hr and agreed before work starts.
One skid. Fixed scope. Your network.
Tell us about the skid, the instruments, and the network. The site review tells you whether this fits before you spend anything on hardware.