The first step of working with IntelH2O is an assessment on your own plant. It takes a few weeks, it produces a written result you keep either way, and it starts from documents you already have. This is the list.
What to gather
- A tag list from your SCADA or historian. Any export will do — a spreadsheet, a CSV, the vendor’s own format. Include the tag name, a description, the units and, if you have them, the area or equipment each tag belongs to. Do not clean it up first; how it comes out is part of what we learn.
- Your permit and your most recent monthly report. The assessment measures the month end you have against the month end you could have, so the real report — with its limits, its rows and its signatures — is the yardstick.
- Your alarm log for a typical month, if it is easy to export. It shows what chatters, what is acknowledged without action and what was missed.
- The maintenance backlog and the instrument calibration schedule, in whatever form they exist — a system, a spreadsheet or a notebook.
- A site list with the plants, wellfields, tanks and booster stations, and which of them have a network connection.
Who to invite
An hour each with four people is enough: the operator who is on shift most, the person who signs the monthly report, the technician who owns the instrument schedule, and whoever answers for IT and the network. They do not need to prepare; they need to describe a normal week and a bad one.
What you have at the end
A picture of your plant as one system — sites, areas, equipment, and the instruments that matter to compliance — and a written view of what would change for operations, compliance and maintenance if you went on to a pilot. It is yours whether or not you continue.
What happens next
If the assessment is convincing, the pilot runs on one plant with your operators, on your live data, against your alarms, your report and your backlog. The decision to roll out is made on what your people saw.