top of page

Produced Water Treatment Systems: How to Design for the “Bad Hours”

  • Writer: Joseph Clarke
    Joseph Clarke
  • Mar 27
  • 4 min read


Produced water treatment systems rarely fail because “the technology doesn’t work.” More often, they fail because the system was engineered for average conditions—while the plant lives and dies by the bad hours: oil-in-water spikes, solids slugs, emulsion events, chemical upsets, and operating mode changes.


At PSI Energy & Offshore Services, our approach to produced water treatment engineering is built around a simple principle: design for the operating envelope, prove performance by test, and protect the facility through excursions. If you get those three right, you reduce rework, reduce downtime, and create a more stable path to commissioning and acceptance.


modular-containerized-produced-water-treatment-system


Why “Average Conditions” Cause Produced Water Treatment Failures


Most produced water treatment scopes begin with historical data—sometimes limited or inconsistent. It’s tempting to engineer around the mean. But in the real world, what causes performance degradation is the tail: variability and excursions.


Typical examples:


  • A sudden increase in oil-in-water (OIW) due to separator performance changes, production upsets, or slugging.

  • A rise in TSS/solids from corrosion products, sand production, or tank disturbances.

  • Emulsions triggered by shear, chemical interactions, or changes in crude composition.

  • Startup/shutdown transient conditions, especially in brownfield sites.



When systems are designed around average values, they are often under-protected—leading to fouling, trips, or downstream impacts (including injection system damage where reinjection is the outlet).


Define the Inlet Envelope Before You Choose Technology

The correct starting point isn’t “We want UF” or “We want flotation.” It’s:


  • What is the inlet envelope we must tolerate?

  • What is the required outlet quality (and how is it measured)?

  • What are the constraints (footprint, utilities, tie-ins, shutdown windows)?

  • What is the operating philosophy (manned/unmanned, maintenance approach, spares strategy)?



A practical inlet envelope definition includes:


  • Flow range (normal, minimum, maximum)

  • OIW range (normal and worst-case)

  • Solids (TSS/particle size distribution, if available)

  • Temperature and salinity

  • Presence of scaling risk, corrosion products, polymers, demulsifiers, biocides

  • Gas content and entrainment risk

  • Target run time between interventions (cleaning/backwash/maintenance)



This envelope becomes the foundation for selecting and sizing each stage—and for defining what constitutes an “excursion.”



Excursion-Resilient Architecture: Treat Excursions as an Operating Mode


Explore the sidebar on the left. You can add media to add color to your post. You can also change the cover image, optimize the SEO Settings, add categories or tags, and much more. Spend some time discovering each tab and learn how you can enhance your future posts.

 

The key to surviving the bad hours is to treat excursions as a known operating mode—not a surprise. Your design should include the ability to:


  1. detect excursions early,

  2. protect sensitive downstream equipment, and

  3. recover in a controlled way.



1) Monitoring at the Right Points


Online instrumentation isn’t optional if you want stable performance and predictable acceptance. The “right points” vary, but a common approach includes:


  • Feed monitoring at the treatment inlet header

  • Intermediate monitoring to validate stage performance (e.g., after flotation)

  • Final outlet monitoring before discharge/injection header


Instrumentation should be tied to the operating philosophy—alarm limits and action limits must align with what you can reasonably do on site (automated diversion vs manual intervention).


2) Automated Diversion / Equalization for Off-Spec Water


One of the most practical protections for produced water trains—especially polishing stages—is an off-spec diversion concept:


  • When inlet or intermediate conditions exceed protection limits, divert to an equalization/storage route.

  • When conditions normalize, reprocess gradually to avoid re-shocking the train.


This does three things:


  • Protects sensitive units from irreversible fouling or overload

  • Preserves outlet quality stability

  • Provides a clear operational response that can be tested and documented


3) Controlled Recovery (Not a “Back to Normal” Switch)


Recovery from an excursion is often where plants struggle. The correct approach typically includes:


  • staged ramp-up of flow

  • staged chemical dosing adjustments (if used)

  • controlled backwash/cleaning sequence

  • gradual reintroduction of diverted volumes


This requires that your controls and operating procedures treat recovery as part of the design—not a field improvisation.

 


Controls & Interlocks: Protect Performance and Asset Integrity


A well-engineered produced water system has defined interlocks tied to measurable conditions. Examples:


  • High OIW → divert / reduce load / protect downstream

  • High DP across a filter/membrane → initiate backwash or cleaning cycle

  • Low flow or pump trip → safe-state response to prevent damage

  • High turbidity → divert or adjust operating mode


The goal is not to “automate everything,” but to define predictable protective actions that reduce operator burden, reduce human error, and preserve equipment life.



Brownfield Reality: Integration and Constructability Make or Break Delivery


Even the best process design can fail on integration if you don’t plan for:


  • tie-in constraints

  • limited shutdown windows

  • utility availability and capacity

  • footprint and lifting route constraints

  • instrument cable routing and panel integration

  • mechanical completion and turnover requirements


This is why PSI emphasizes constructability during engineering—because the system must be installable, commissionable, and maintainable in your actual facility conditions.

 


Prove Performance: Acceptance Testing Must Match the Contract


Many disputes happen because acceptance criteria were not clearly defined upfront. A strong acceptance approach includes:


  • defined inlet envelope assumptions

  • test duration and sampling frequency

  • sampling points and methods

  • stability criteria (what “stable” means)

  • statistics basis (daily max vs average, if applicable to permits)

  • excursion response requirements and exclusion conditions



A produced water system is only “bankable” when performance is measurable and testable.



PSI’s Approach


PSI provides produced water treatment engineering and EPC delivery support built around:


  • envelope-driven design

  • excursion resilience architecture

  • controls and interlock discipline

  • integration planning for brownfield environments

  • documentation-led QA/QC and turnover readiness



Next Step

 

If you share your flow range, produced water quality snapshot, and target outlet requirement, PSI can structure a practical concept approach and execution path.



 
 
 

Comments


bottom of page