.png)
From Flow Meter to Dashboard: Building a Connected Flow Monitoring System
A connected flow system does not start with a dashboard. It starts with a pipe, a fluid, and a measurement problem that needs to be solved without adding new failure points.
A meter can be perfectly accurate on the bench and still perform poorly in the field if the flow profile is disturbed, the output does not match the controller, or the alarm logic creates noise instead of useful warnings. The strongest projects treat the meter, signal, communications layer, dashboard, and alarm strategy as one measurement chain.
That is where ProSense can add value beyond supplying a flow meter. The right support covers application review, technology selection, signal choice, installation details, connectivity, and the way operators will use the data after it leaves the pipe.
Start with the measurement outcome
Before choosing a meter, define what the system must prove or control. Flow measurement can serve many jobs, and each one pushes the design in a different direction.
Common goals include:
Monitoring water or chemical consumption
Confirming pump operation
Dosing additives into a process
Detecting leaks or blocked lines
Recording batch totals
Feeding flow data into a SCADA, PLC, or cloud dashboard
Triggering alarms when flow moves outside safe limits
A simple pump run confirmation may only need a switch or pulse output. A dosing application may need a more stable analogue signal or digital data. A compliance or usage dashboard may need totalised flow, timestamps, and remote access.
The early question is not “Which meter do we like?” It is “What decision will this measurement support?”
That answer sets the standard for accuracy, response time, signal type, connectivity, and alarm handling.
Choose the right flow technology for the application
No single flow technology suits every fluid and pipe condition. The first design decision is the sensing method.
Flow technology | Best suited to | Main checks before selection |
Paddle wheel or turbine | Clean, low-viscosity liquids such as water | Fluid cleanliness, flow velocity, wear, required straight pipe |
Magnetic flow | Conductive liquids, wastewater, process water, many chemicals | Minimum conductivity, full pipe, liner and electrode compatibility |
Ultrasonic | Many water and liquid monitoring tasks, including some retrofit work | Pipe material, installation position, air bubbles, signal quality |
Vortex | Steam, gas, and some liquids in stable process conditions | Reynolds number, vibration, straight run, process temperature |
Positive displacement | Low flow rates, viscous liquids, batching | Pressure drop, fluid cleanliness, maintenance access |
Thermal mass | Air and gases, especially compressed air monitoring | Gas type, temperature range, pressure effects, pipe profile |
Clean water in a utility line might work well with a paddle wheel, turbine, magnetic, or ultrasonic meter, depending on budget and accuracy needs. A conductive chemical stream may favour magnetic flow if the wetted materials suit the fluid. A compressed air line points the design toward thermal mass or another gas-suitable technology.
This is where application support matters. ProSense can help narrow the options by looking at the process, not only at the pipe size. That includes the fluid, expected range, required signal, installation limits, and what the data needs to become later.
A good selection process avoids two common mistakes.
The first is oversizing. A large meter on a low-flow line may spend most of its life near the bottom of its range, where readings are less useful.
The second is choosing a meter only because it fits the pipe. Physical fit is not enough. The meter also needs the correct measurement principle, wetted materials, pressure rating, temperature rating, and output type.
Confirm the pipe and process conditions
Once the technology looks right, check the installation details. These details often decide whether the final system feels reliable or frustrating.
Pipe size and material affect velocity, pressure drop, installation fittings, and grounding requirements. In many flow applications, velocity matters more than nominal pipe size. A meter must see enough flow to measure accurately, but not so much that it causes wear, noise, or pressure loss.
Pipe condition matters as well. Corrosion, scale, lining, or old pipework can affect internal diameter and flow profile. For clamp-on or insertion-style solutions, the condition of the pipe can have a major impact on signal quality and repeatability.
Straight pipe run is another key point. Pumps, elbows, valves, reducers, and tees can twist or distort the flow before it reaches the meter. Some technologies tolerate disturbed flow better than others, but none should be installed without checking the manufacturer’s guidance.
Process conditions need the same care:
Minimum, normal, and maximum flow rate
Line pressure and possible pressure spikes
Fluid temperature during normal and upset conditions
Viscosity and density where relevant
Solids, bubbles, foam, or entrained air
Chemical compatibility with wetted parts
Cleaning cycles and washdown exposure
Hazardous area needs, if applicable
Power supply should be confirmed at this stage too. Some meters need loop power. Others need separate DC or AC supply. Some field locations limit what can be added, especially where trenching, conduit, or cabinet space is difficult.
A connected system only works well if the primary measurement is stable. If the meter is fighting poor pipe conditions, the dashboard will only display unreliable data faster.
Choose the signal that fits the control system
After selecting the meter and confirming the installation, choose how the measurement leaves the device. The signal type affects wiring, resolution, diagnostics, and how much data the system can carry.
Pulse output works well for totals and simple counting
A pulse signal is often used when the main requirement is total flow. Each pulse represents a known volume. A counter, PLC input, remote telemetry unit, or data logger can add those pulses and display a total.
Pulse is useful for:
Batch totals
Water usage monitoring
Pumped volume confirmation
Simple remote counting
Pulse outputs are usually simple and cost-effective, but they provide limited live process detail unless the receiving device calculates rate from pulse frequency. Long cable runs and electrical noise also need care.
4–20 mA is a strong choice for live flow rate
The `4–20 mA` signal remains common because it is simple, proven, and widely accepted by PLCs, indicators, recorders, and remote I/O.
In most flow applications, 4 mA represents the low end of the scaled range, and 20 mA represents the high end. The receiving system reads the current and converts it into engineering units such as L/min, m³/h, or kg/h where the process supports mass-based values.
Use `4–20 mA` when the system needs:
Continuous flow rate
Compatibility with existing analogue inputs
Simple scaling in a PLC or display
A stable signal over longer cable runs
The scaling must match the real process range. If the meter is scaled for 0 to 1,000 L/min but the process usually runs from 30 to 80 L/min, the dashboard will have poor resolution. ProSense application support can help set a practical operating range before commissioning.
Modbus carries more data over fewer wires
`Modbus` is useful when the system needs more than one value from the device. Depending on the meter and configuration, it may carry flow rate, total flow, diagnostics, status bits, device settings, or alarm states.
Use Modbus when the project needs:
Multiple data points from one meter
Digital values without analogue scaling drift
Easier integration into suitable PLC, SCADA, or gateway systems
Device status and diagnostic information
The design still needs discipline. Baud rate, addressing, register mapping, termination, cable type, and polling rates need to be documented. A digital network can be powerful, but it is not self-explanatory after the installer leaves.
Add the right wired or wireless communications
The meter output gets the data out of the pipe. The communications layer gets it to the people and systems that need it.
Wired communication is often the best choice when the site already has control infrastructure nearby. It suits permanent installations, harsh environments, time-critical control, and locations where cable routes are easy to run.
Common wired paths include:
Direct cable to PLC input cards
Local display with retransmission
Remote I/O into a control network
Gateway from serial or analogue signals to Ethernet-based systems
SCADA integration through existing plant networks
Wireless communication can make sense when cabling is expensive, disruptive, or impractical. It can work well for tank farms, remote pump stations, temporary monitoring, utilities, and spread-out sites.
Wireless choices should be matched to the site. Options may include industrial radio, cellular gateways, Wi-Fi where suitable, or low-power wide-area networks. The best option depends on distance, data frequency, power availability, local signal conditions, and how critical the measurement is.
Battery-powered wireless devices need special attention. Frequent updates use more power. Low update rates save battery life but may miss fast changes. Alarm applications may need a different setup from daily usage logging.
Security and access also matter. Keep control functions separate from casual viewing where needed. Use suitable authentication, sensible user roles, and documented network settings. For wider plant systems, involve the controls or IT team early so the flow project does not become a late integration problem.
Configure dashboards that operators can trust
A dashboard should make the measurement easier to use, not simply add graphs. The best screens answer practical questions quickly.
For a connected flow-monitoring system, useful dashboard elements often include:
Current flow rate in clear engineering units
Totalised flow for shift, day, batch, or billing period
Trend charts for recent performance
Pump state or valve state where available
High-flow and low-flow alarms
No-flow alarms when equipment should be running
Communication status
Sensor fault or out-of-range indications
Avoid overcrowding the first screen. Put the most important values at the top. Use trends to show behaviour over time, not decoration. A short trend can reveal pump cycling, valve hunting, filter blockage, or unexpected after-hours usage.
Dashboards also need consistent units. In Australia, many water and process systems use L/min, kL, m³/h, or ML depending on scale. Pick units that operators already use on the plant floor and in reports. Do not force people to mentally convert while they are responding to a fault.
For multi-site systems, naming is critical. A tag such as `FM-102` may suit a control drawing, but the dashboard may need a plain label as well, such as “Bore Pump 2 Discharge Flow”. Good naming reduces wrong assumptions during alarms.
Build alarms that help rather than annoy
Alarm design is often rushed. That is a mistake because poor alarms teach people to ignore the system.
Set alarm limits around real process behaviour. If normal flow varies by product, season, pump selection, or valve position, a single fixed alarm may create too many false alerts. Some applications need different alarm thresholds for running and stopped states.
Useful flow alarm types include:
Low flow while pump is commanded on
No flow after valve open command
High flow suggesting leak, bypass, or failed valve
Flow below expected dosing rate
Total volume above daily target
Reverse flow where the meter supports direction
Loss of signal or communications fault
Add time delays where the process allows. A pump may take a few seconds to prime. A valve may create a brief spike. Without sensible delay settings, these normal events become nuisance alarms.
Alarm priority also matters. A flow deviation that risks product quality, pump damage, or environmental release should not look the same as a mild usage warning. Separate urgent alarms from advisory alerts.
Record alarm history where possible. Repeated low-flow alarms may point to a blocked strainer, worn pump, unstable suction, or incorrect setpoint. The value is not only in the alert, but in the pattern it reveals.
Treat ProSense as part of the full measurement chain
A flow meter is only one part of the system. The chain starts with the primary sensing point and ends with a person or control system making a better decision.
ProSense can support that chain by helping match each layer:
System layer | What needs to be decided | How ProSense can support it |
Process review | Fluid, pipe, flow range, pressure, temperature | Help define the application and rule out poor-fit technologies |
Meter selection | Measurement principle, size, materials, rating | Recommend suitable flow meter options for the duty |
Signal output | Pulse, 4–20 mA, Modbus, or switching | Match the output to PLCs, displays, gateways, or counters |
Installation | Mounting, straight run, wiring, power, protection | Provide guidance so the meter can perform as expected |
Communications | Wired or wireless path to the next system | Help choose practical ways to move the data |
Visualisation | Dashboard values, tags, totals, trends | Support clear display of rate, total, status, and history |
Alarms | Thresholds, delays, priorities, fault states | Help make alarms useful and manageable |
This joined-up approach reduces rework. It also makes commissioning easier because the design has already answered the key questions: what is being measured, how the signal behaves, where it goes, who uses it, and what should happen when the value changes.
For new projects, this can shape the design from the start. For existing sites, it can help modernise older flow points by adding better outputs, gateways, remote visibility, or alarms without replacing more equipment than necessary.
What a good connected flow system looks like
A connected flow-monitoring system should feel simple when it is finished. That simplicity comes from careful choices early in the project.
The meter suits the fluid and pipe. The process conditions sit inside the meter’s working range. The output matches the control or logging system. The wired or wireless path is reliable enough for the job. The dashboard shows values people can act on. The alarms warn early without creating noise.
When each layer is designed as part of one chain, flow data becomes more than a number on a screen. It becomes a practical tool for running pumps, protecting equipment, tracking usage, improving batches, and spotting problems before they grow.
