An industrial RO project should start with a design basis, not a membrane count or a headline flow rate. The most useful first conversation defines the required permeate use, demand pattern, source-water condition, operating model, and the physical interfaces that sit outside the RO package.
Start with the product-water duty
Permeate demand is not the same as feed flow. A design review should separate average use, peak use, storage strategy, operating hours, future expansion, and any critical uninterrupted loads. This distinction affects the duty profile, redundancy discussion, storage interfaces, and the questions that must be answered before a supplier can prepare a comparable technical concept.
Describe the product-water use in operational terms. Boiler feed, process rinse, cooling-tower makeup, laboratory supply, and other applications can have different quality objectives and continuity requirements. The project team should document the objective rather than assume that one generic RO water quality target applies to every use.
- Required product-water use and quality objective
- Average, peak, and future demand profile
- Operating hours, storage, and critical loads
- Existing treatment and distribution interfaces
Use representative source-water evidence
Source-water chemistry and variability determine the pretreatment questions, membrane operating envelope, cleaning strategy, concentrate planning, and monitoring needs. A single incomplete test can be a starting point, but it should be identified as such. For groundwater, surface water, municipal supply, reclaimed water, or a blended source, record how the source changes by season, operation, or well condition.
The RO review normally needs more than conductivity or TDS. A useful laboratory package explains pH, hardness, alkalinity, iron, manganese, silica, sulfate, chloride, turbidity, SDI where applicable, organics, temperature, and any known disinfectants or process contaminants. Missing parameters should become a clarification item, not an assumed value.
- Source description and sampling location
- Representative laboratory analysis and sampling date
- Known seasonal, operational, or source-switch variation
- Existing treatment and operational records
Define the treatment boundary
An RO skid is only one part of a water-treatment project. The technical boundary may also involve feed storage, pretreatment, chemical containment, power supply, drains, concentrate routing, post-treatment, permeate storage, distribution tie-ins, automation, remote signals, civil works, and ventilation. Each interface should be assigned to an owner before commercial comparison begins.
DuPont’s RO configuration overview describes membranes, pumps, flow, pressure, and concentrate pathways as interacting process elements rather than standalone components.[1] The article should therefore help buyers ask which stages are inside the package and which remain site works, not imply a universal configuration.
- Package-scope and site-work split
- Feed, permeate, concentrate, and drain tie-ins
- Electrical, controls, and communication responsibilities
- Access, ventilation, lifting, and chemical-handling requirements
Turn the inputs into a comparable proposal
A technical proposal can be compared only when each bidder is working from a similar design basis. The request should state the source-water data, treatment objective, duty profile, interfaces, materials expectations, controls, documentation, testing, shipping assumptions, and exclusions. If an input remains unknown, list it as an assumption that must be closed before final design.
Public buyer guidance likewise stresses that demand, feed-water conditions, pretreatment, residuals, maintenance, and long-term operation affect the right RO selection.[2] That is why a price-only comparison can obscure differences in scope and future work.
- Assumption register
- Scope and exclusion schedule
- Testing and documentation requirements
- Clarification route for missing design data
Related Engineering Resources
Frequently Asked Questions
Can an industrial RO system be selected from required flow alone?
No. Required permeate use is important, but final selection also depends on source-water data, duty profile, site interfaces, pretreatment, controls, residuals management, and the approved design basis.
What is the most useful first document for a supplier?
A representative water analysis together with the product-water objective, demand profile, operating hours, site location, available utilities, drawings, and scope expectations.
Sources & Reading Notes
These sources support the engineering context of this guide. Final project decisions remain subject to current water data, owner requirements, applicable rules, and approved design documentation.
- DuPont Water Solutions — Industrial RO Systems and ConfigurationsProcess configuration context.
- Puretec Industrial Water — Industrial RO Buyer’s GuideBuyer-input and lifecycle review context.