IT that keeps pumps reporting, bills going out, the board informed.IT that keeps pumpsreportingbillsgoingouttheboardinformed
Office IT, operator workstations and the SCADA boundary, managed by people who know a lift station isn't a server room.
Water & wastewater
The plant runs on pumps. The utility runs on IT.
Treatment happens in tanks and basins, but permits, alarms, billing and board packets all move through computers. Here's how a small utility's day depends on IT, where it tends to break, what we change and what it looks like once the boring parts are handled properly.
01 · The pressure
Small staff, big obligations
A typical morning: the chief operator checks overnight alarms on the SCADA screen, the office runs meter reads through the billing system, and someone is pulling lab results for the monthly operating report. If the operator workstation won't boot or billing goes down during a cycle, there's no IT department to call. It's usually the general manager, a part-time contractor or the integrator who's two hours away. Customers still expect accurate bills and the state still expects reports on time.
- SCADA HMIs and historians at the plant
- Billing and CIS data for every account
- Regulatory reports with hard deadlines
Ignition by Inductive AutomationAVEVA InTouch HMIGE iFIXTyler Technologies IncodeSensus FlexNet AMIBadger Meter BEACONMicrosoft 365
02 · How it breaks
Remote access left wide open
The pattern repeats across the sector. A remote desktop tool was installed years ago so the integrator could log in after hours, and it still uses a shared password. An operator checks personal email on the HMI workstation. The billing clerk gets a convincing invoice from a chemical vendor that's really a phishing page. The business network and the control network share a flat switch, so anything that lands on a front-office PC can see the plant. Backups exist, but nobody has tried a restore.
- Shared vendor logins on remote tools
- Flat networks between office and plant
- Untested backups of billing data
Ignition by Inductive AutomationAVEVA InTouch HMIGE iFIXTyler Technologies IncodeSensus FlexNet AMIBadger Meter BEACONMicrosoft 365
03 · What we change
A real boundary and real accounts
We start with an inventory of what's connected, then put a managed firewall between the business network and the SCADA network with only the traffic your integrator says is needed. Vendor access moves to named accounts with MFA through a jump host, logged and time-limited. Operator workstations get locked down, patched on a schedule agreed with operations, and kept off email. Billing and file data go to immutable, offsite backups that we restore-test. Any change inside SCADA stays with your integrator.
- Firewall and segmentation at the IT/OT edge
- Named, MFA-protected vendor access
- Immutable backups with restore tests
Ignition by Inductive AutomationAVEVA InTouch HMIGE iFIXTyler Technologies IncodeSensus FlexNet AMIBadger Meter BEACONMicrosoft 365
04 · The after
Answers ready for the board
Once it's in place, the general manager can tell the board exactly who can reach the plant remotely and how. When it's time to update the AWIA risk assessment or emergency response plan, the asset list, network diagram and access records already exist. Insurance renewal questions about MFA and backups get yes answers you can back up. Operators stop babysitting cranky PCs, and the billing office knows a bad cycle can be restored instead of rebuilt.
- Documented access for board and insurer
- AWIA updates start from current records
- Operators focused on treatment, not PCs
Ignition by Inductive AutomationAVEVA InTouch HMIGE iFIXTyler Technologies IncodeSensus FlexNet AMIBadger Meter BEACONMicrosoft 365