floWyse turns every connected pump into a self-optimising asset — control and protection at the panel, second-by-second telemetry in the cloud, and energy analytics that pay for the hardware.
One controller sits in the panel, speaks Modbus to the drive, reads the field sensors, and keeps a single source of truth in the cloud. No gateway boxes, no SCADA licence, no rip-and-replace.
Ultrasonic level, float switches, pressure, current and temperature read straight off the field wiring.
floWyse runs the logic locally — setpoints, schedules, dry-run and over-current trips. Internet optional.
Frequency and start/stop over Modbus RTU where there is a drive, or direct contactor switching where there is not.
Every datapoint streams to your own cloud — no third-party IoT tenancy, no per-device subscription.
Dashboard, PWA and push alerts. Change a setpoint from anywhere and watch the drive respond.
Six surfaces built from the same telemetry stream — the same ones running today at dashboard.flowyse.in.
Ultrasonic depth, float positions and refill rate — with the exact same animated column the operators see on the HMI.
kWh, active power, power factor and tariff-aware cost per shift — exported to CSV or a signed PDF report.
Read and write drive parameters, duty/standby rotation, ramp profiles and soft-start limits — brand agnostic.
Dry run, over-current, phase loss, tank overflow, comms fail — with the reason code, a timestamp and a push to every linked phone.
Spot short-cycling before it kills a bearing. Hours run, starts per hour and duty balance across the whole fleet.
Super admin, OEM partner and end user each see their own slice. QR onboarding links a device to a customer in seconds.
Every floWyse unit builds a picture of what normal looks like for that one pump, scores its health out of 100, and runs an assistant that answers questions about it. The model runs on your own server — no API credits, and no telemetry leaving your cloud.
Based on 42 days of run history
Short-cycling pattern, weekly run-time trend, and today's runtime against the normal it learned for this pump.
floWyse Assistant
LOCAL MODEL · YOUR SERVER
For the first stretch after commissioning the controller watches instead of judging — building the hour-by-hour baseline for this pump, this tank and this building before it starts calling anything abnormal.
A pump that suddenly runs longer at 3 a.m. than it ever has is telling you something — a leaking line, a stuck float, a failing foot valve. floWyse catches the pattern days before the bill does.
Short-cycling trends, creeping current draw and drifting run-times become a graded alert with a reason attached — so the maintenance visit happens before the motor decides the date for you.
Installable as a PWA, works offline on the last-known state, and syncs the moment the link is back.
DIN-mount, 3-phase native, and designed to be commissioned by an electrician with a phone — not a laptop and a licence dongle.
A single controller driving up to two VFDs over Modbus RTU — or a direct starter — with dry contacts, float inputs, 4–20 mA and a CT for true current.
A local screen that keeps working when the site loses internet — same modes, same limits, same trip history as the cloud.
Ultrasonic sensor on the overhead tank, reporting depth continuously so the controller stops the pump before an overflow or a dry run.
You build the pump, floWyse supplies the controller, the cloud and the app — plus an OEM console that tracks every unit you have shipped, long after it leaves the factory.
If it speaks Modbus RTU, it works. Keep the drive, keep the starter, keep the wiring — add the intelligence in one DIN slot.
Overflow, dry runs, 2 a.m. burnouts and a bill nobody can explain. floWyse gives the facility team the one screen that answers all of it.
And most of them still run flat out against a throttled valve. Variable speed plus closed-loop control is the cheapest efficiency win in the building.
The installed base of VFD panels dwarfs new builds. A DIN-rail controller that speaks to what's already there addresses the whole market, not the 3% shipping this year.
Hardware gets copied. Years of labelled trip, runtime and energy data across a live fleet does not — and it is what makes the next feature obvious.
Send us a photo of the panel and the pump details. We'll tell you exactly what it takes to retrofit — usually one controller and an afternoon.