Standardising Thickness Monitoring Across a Multi-Site Water Utility
A water and wastewater CML registry gives every monitoring location a common identifier, material, measurement method, baseline basis and confidence tier, so readings taken by different crews at different plants can be compared. Without that structure a utility cannot roll condition data up at all, because a ductile iron main, a prestressed concrete cylinder pipe and a hypochlorite line are not measured the same way.
Water utilities inherit their asset base rather than designing it. A single authority may run two treatment plants, a dozen lift stations, several reservoirs and a chemical feed system built across sixty years by different engineers under different naming conventions, and may have absorbed two neighbouring systems along the way. Nothing here is governed by API 510, 570 or 653, so there is no external programme imposing a common structure. The result is predictable: every site records condition differently, every contractor reports in its own format, and the numbers refuse to roll up. The fix is not a bigger spreadsheet. It is a registry that forces the fields which make comparison legitimate, records what was actually measured and how, and reports confidence alongside condition. That last part matters more than it sounds, because the most damaging output in this sector is a system-wide average corrosion rate computed from a mixture of measured baselines and nominal wall assumptions.
Source: Sources: AWWA D100 welded carbon steel tanks for water storage, D102 coating systems and M42 steel water storage tanks; AWWA C210 and C213 protective linings; AWWA C301 and industry electromagnetic inspection practice for prestressed concrete cylinder pipe; AWWA C652 disinfection of water storage facilities; NSF/ANSI/CAN 61 drinking water system components; AMPP/NACE SP0169 external corrosion control of buried metallic piping; ACI 350 environmental engineering concrete structures and ACI 201.1R condition survey guidance; ASME B31.3 for chemical feed piping and ASME Section VIII with NBIC NB-23 for pressure vessels and repairs; OSHA 29 CFR 1910.146 permit-required confined spaces; ISO 55001 and AWWA G200 for asset management; GASB 34 modified approach reporting.
| Tier | What the record actually contains | What may legitimately be computed from it | What it must never feed |
|---|---|---|---|
| Tier 1, trended | Measured baseline plus two or more dated readings at the same location, same method, same material | Long-term corrosion rate, projected remaining life, renewal year | Nothing further; this is the only tier that supports a published rate |
| Tier 2, measured but untrended | One measured reading against a measured baseline, with method and material recorded | Current condition against minimum acceptable thickness, screening flag | Corrosion rate, remaining life, or any capital forecast |
| Tier 3, assumed baseline | A reading compared against a nominal wall taken from a specification table | Presence or absence of gross loss only | Any rate at all; mill under-tolerance alone can fabricate several mils per year |
| Condition only, non-UT | Concrete surface condition, PCCP wire break count, coating assessment or CCTV grade with survey date | A condition grade for asset management and capital reporting | Thickness arithmetic of any kind |
| Unverified legacy | A reading with no recorded method, material or location detail | Nothing | Any report that leaves the engineering group |
Water and wastewater assets do not inherit an API framework
In refining and petrochemicals, the structure of a thickness monitoring programme is largely handed to you. API 510, 570 and 653 define what a circuit is, how intervals are set, how required thickness is derived and what an inspector must be certified to do. Argument happens at the margins. A water utility gets none of that. Its steel storage tanks reference AWWA D100 and its coating and lining work references AWWA D102, C210 and C213, but those are design and construction standards, not in-service inspection programmes with interval rules and a certified inspector behind them.
The absence is not a gap to be filled by importing API wholesale, because the assets genuinely differ. A treatment plant's inventory includes cement mortar lined ductile iron, prestressed concrete cylinder pipe, environmental concrete structures under ACI 350, PVC and CPVC chemical feed lines, FRP scrubber ducting, HDPE, coated steel in submerged and splash service, and a small number of genuine pressure vessels under ASME Section VIII with repairs governed by NBIC NB-23. A single framework built for carbon steel process piping does not describe most of that.
What the utility does have is an asset management obligation, and increasingly a financial one. ISO 55001 and AWWA's asset management guidance set the expectation that condition is assessed consistently and used to plan renewal. Where a utility reports infrastructure under the GASB 34 modified approach, it has to demonstrate that assets are being preserved at or above a stated condition level, which requires a condition measure that is consistent across the whole system. That obligation, not a code, is what forces standardisation, and it is usually what puts a registry on the capital list.
Eight plants, eight naming conventions, one impossible rollup
The taxonomy problem is the first thing anyone encounters and the last thing anyone fixes. Plant 2 calls a line the sludge header. Plant 4 calls the same function SL-04. The reservoir records use the elevation in the name. The lift stations were documented by whichever consultant did the last upgrade, and three of them were inherited when the authority absorbed a smaller system whose records arrived as a box of drawings. There is no common vocabulary for a site, a system, a line or a component, so there is nothing to group by and no dimension to roll up along.
Utilities usually attempt to fix this by renumbering everything into a new scheme. That fails for a human reason rather than a technical one. Crews who have used a name for twenty years continue to use it, and if the system cannot find an asset under the name the operator actually says out loud, the operator stops using the system. Within one rotation the registry is being maintained by one person in the engineering group and bypassed by everyone else.
The approach that survives is additive. Build a structured identifier from site, system, line and component, apply it consistently to new records, and carry every legacy identifier on the same record as a permanent, searchable alias. Nothing is renumbered and no history is orphaned. Search resolves both ways, so a crew can find the asset by the old name and a report can group by the new structure. The rollup then becomes possible without asking anyone to relearn the plant.
The measurement method is part of the record, not a detail
In a refinery, the default assumption that a thickness reading means a contact ultrasonic measurement on carbon steel holds most of the time. In a water utility it holds for perhaps a third of the asset base, and treating it as a default is how a registry fills with numbers that cannot be compared. Cement mortar lined ductile iron does not present a clean back wall to a contact probe; the reading you get depends on lining condition and coupling and is not equivalent to a reading on bare steel. Prestressed concrete cylinder pipe does not fail by wall loss at all; it fails by prestressing wire breaks, assessed electromagnetically, and the meaningful number is a break count and its distribution, not a thickness.
Concrete structures are assessed by condition survey against ACI guidance, with the wastewater-specific mechanism being biogenic sulfide attack: hydrogen sulfide in the headspace of wet wells, force main discharge points and headworks is oxidised biologically to sulfuric acid, which attacks the concrete crown and any unprotected steel above the waterline. The damage is severe, localised in the vapour space rather than the liquid, and invisible to a thickness programme that only samples submerged steel.
The registry consequence is that material and method must be mandatory fields that constrain what the system will accept and what it will compute. A location recorded as PCCP should not accept a thickness. A location recorded as mortar-lined ductile iron should carry the method used and be excluded from any comparison against bare steel readings. This is not bureaucratic tidiness. It is the only thing preventing a corrosion rate being computed across two measurements that were never measuring the same quantity.
The nominal wall trap that fabricates corrosion across an entire utility
Here is the arithmetic error that does the most damage in this sector, precisely because it is invisible and produces plausible numbers. A utility has thousands of monitoring locations and almost no measured baselines, because nobody ultrasonically mapped the plant when it was commissioned in 1974. So the baseline is taken from a specification table: six inch schedule 40 pipe has a nominal wall of 0.280 inches, therefore that is what was installed.
It very often is not. The common pipe specifications permit a manufacturing under-tolerance of twelve and a half per cent on wall thickness, so the same pipe could legitimately have left the mill at 0.245 inches. Ten years later a technician reads 0.246 inches. Compared against nominal, that is 0.034 inches of loss in ten years, a rate of about 3.4 mils per year, which is enough to drive a renewal decision. Compared against the metal that was actually installed, essentially nothing has happened. Apply that same error across four thousand locations at twelve sites and the utility has manufactured a capital programme out of mill tolerance.
The defence is structural rather than analytical. The registry must record whether a baseline was measured or assumed, and must refuse to compute a corrosion rate from an assumed baseline. An assumed-baseline location can legitimately produce a screening flag when a reading approaches a minimum acceptable thickness, which is useful. It cannot produce a rate, a remaining life or a renewal year, and any system that lets it do so will eventually be used to justify spending that the underlying data does not support.
Potable contact changes what a reading costs
A reading taken inside a clearwell, a finished water reservoir or a treated water storage tank is not the same operation as the same reading on a raw water line, and the difference is regulatory rather than technical. Materials that contact drinking water have to be acceptable for potable service, which governs the couplant used, any coating or repair material applied, and in many utilities the equipment brought through the hatch. After entry, the facility is disinfected and returned to service under AWWA C652, with bacteriological clearance before it goes back into distribution.
That sequence turns what looks like a fifteen-minute task into a planned event with a tank drawdown, a confined space entry permit under 29 CFR 1910.146, a disinfection cycle and a clearance sample. On the wastewater side the constraint is different but no lighter: wet wells and digesters are permit-required confined spaces with an atmospheric hazard that can be immediately dangerous, and the entry team, monitoring and rescue provision are the dominant cost.
For the registry, this means potable contact and confined space entry are attributes of a location, not facts a scheduler is expected to remember. Once they are recorded, the system can group work so that everything needing a single reservoir drawdown happens in that drawdown, and everything needing an entry into a particular wet well happens on one permit. Utilities that add these two fields typically find the immediate saving is not in the inspection at all; it is in the number of drawdowns and entries per year.
There is no turnaround, only redundancy windows
A refinery inspection programme is organised around a large periodic shutdown. A water utility has nothing equivalent, because the discharge permit and the public health obligation require continuous treatment. Work happens in redundancy windows: one of two treatment trains, one of three clarifiers, one of four filters, one of two force mains taken out of service while the others carry the load. The window is short, it is constrained by hydraulic capacity, and it usually cannot be taken during wet weather season when peak flows need every train available.
This produces a completely different work pattern. Instead of one intense campaign a year, the utility runs dozens of small campaigns spread across sites, seasons and crews, often with different contractors on different framework agreements. Each of those campaigns is an opportunity for the data to diverge, because each has its own crew, its own report template and its own assumptions about what to call things.
That is precisely why standardisation is worth more here than in a facility with one annual outage. In a turnaround-driven plant, a single strong inspection coordinator can hold the standard in their head for the duration. In a utility running forty small windows a year across a dozen sites, the standard has to be enforced by the system itself: mandatory fields, constrained vocabularies, method and material required before a reading is accepted, and a rejection path for records that arrive incomplete. A convention that lives in a document is a convention that will be broken by the third contractor of the year.
Making the numbers roll up honestly
The instinct when data finally lands in one place is to compute a headline number: the utility's average corrosion rate, or the percentage of assets in poor condition. Both are traps. An average corrosion rate blends measured trends with fabricated rates from assumed baselines and excludes every asset whose failure mode is not wall loss, which in a water utility is most of them. A single condition percentage hides the fact that the assets driving it may be the ones with the weakest evidence behind them.
What rolls up honestly is a tiered picture. Report how many locations sit in each confidence tier alongside the condition findings, and report them by system so the reader can see where evidence is thin. A statement that sixty per cent of force main monitoring locations have no measured baseline is directly actionable: it identifies the next inspection programme. A system-wide average corrosion rate is not actionable, because nobody can tell which part of it is real.
This framing also changes the conversation with a board or a rate-setting authority. Utilities applying for state revolving fund assistance, or reporting infrastructure under the modified approach, are asked to demonstrate a defensible asset management process rather than a single optimistic number. A tiered condition report with explicit evidence quality is a stronger document in that setting than a confident average, and it converts the next inspection budget into an evidence-improvement plan with a stated end point rather than a recurring cost with no visible finish.
Evaluating a registry before you standardise on it
Test the constraints before the features. Can material and measurement method be made mandatory, and will the system refuse to compute a corrosion rate where the baseline is flagged as assumed? Can it hold non-thickness condition data, such as prestressing wire break counts or a concrete condition grade, in the same asset structure without forcing them into a thickness field? Can it carry unlimited legacy aliases per asset and resolve searches against them? If the answer to any of these is that it can be handled by convention, the answer is no, because convention is exactly what has failed at every site you are trying to standardise.
Then test the reporting. Ask for a rollup that groups by system and by confidence tier simultaneously, using your own data with its gaps intact. A demonstration on complete synthetic data proves nothing, because completeness is the condition you do not have. The useful output is a report that tells you honestly how much of your system you actually know something about.
Finally, test the intake path. Most utility inspection work is executed by contractors, so the question is what happens when a contractor submits a campaign with missing method fields or a location that does not exist in the registry. A system that silently accepts it will degrade to the same state as the spreadsheets it replaced within two years. A system that rejects it with a specific exception list, and makes the contractor resolve it before the campaign is accepted, is the one that still holds a standard in year five. Atlantis will run that intake test against a real contractor submission during a scoping consultation.
Why can't we just average corrosion rates across our sites?
Because the inputs are not the same kind of number. Some locations have a measured baseline and several readings; others have a single reading compared against a nominal wall from a catalogue; others are concrete or prestressed pipe where thickness is not the failure mode at all. Averaging these produces a figure that is stable, plausible and meaningless, and it is usually wrong in the optimistic direction because assumed-baseline locations bias low. Roll up counts by confidence tier instead of blending rates.
How do you handle TMLs on ductile iron, PCCP and FRP?
By making material and measurement method mandatory fields that constrain what the system will accept. Cement mortar lined ductile iron does not give a clean back-wall echo, so a straight contact ultrasonic reading is not comparable to one on bare steel. Prestressed concrete cylinder pipe fails by wire breaks and is assessed electromagnetically, producing a break count rather than a thickness. FRP is assessed for delamination and resin condition. Each belongs in the registry, but none should be silently averaged with steel.
What ID scheme survives a merger of three legacy utilities?
One that namespaces by site and system and never renumbers history. Give each location a new structured identifier built from site, system, line and component, then carry every legacy identifier as a permanent searchable alias on the same record. Field crews who have called something the Plant 2 sludge header for twenty years will keep calling it that, and a registry that cannot find it under the old name will simply be worked around within one crew rotation.
Does UT couplant need NSF/ANSI 61 approval inside a potable tank?
Anything contacting a potable water surface has to be acceptable for that service, which in practice means specifying an appropriate couplant and repair material, and disinfecting the facility to AWWA C652 after entry. That turns a fifteen-minute ultrasonic check inside a clearwell into a planned event with a disinfection and return-to-service sequence attached. Flagging potable-contact locations in the registry lets scheduling see the true cost instead of treating them as ordinary readings.
How do you schedule inspection when nothing can be shut down?
A utility has no turnaround. The discharge permit obliges continuous treatment, so work happens in redundancy windows: one of two trains, one of three clarifiers, one of four filters offline at a time, avoiding wet weather season and, in cold climates, most of the winter. The consequence is dozens of small campaigns spread across the year and across crews, which is exactly why a shared registry with enforced fields matters more here than in a facility with one big annual outage.
Is API 510, 570 or 653 inspector training part of this offer?
No. Those inspector certifications are administered by API under its own examination programme and Atlantis is not an API certification training provider. Atlantis delivers NDT training to ASNT SNT-TC-1A and ISO 9712 across UT, RT, MT, PT, ET, VT, PAUT and TOFD, ASNT Level III consulting, independent report validation, 3D laser scanning, and the inspection management software described here. Utility teams commonly engage the Level III consulting to write procedures their own crews and contractors then follow.
Built for any business that runs on operations
Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.
What you can run on it
- Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
- Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
- Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
- Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
- People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
- Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
- Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.
Affordable, accessible, fully customizable — and we mean each word
Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.
Industries we configure for
Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.
What happens when you get in touch
A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.
Related: business management platform · inspection management software · choosing the right category of software · modules · by industry · asset integrity platform. Book a free consultation.