01
Regulatory and receiving requirements
Discharge consents, reuse classifications, receiving-party specifications, product or outlet requirements and any additional conditions for sensitive receptors or controlled uses.
Define what the system must achieve
This work translates the required use, discharge condition or operating objective into measurable capacity, quality, reliability, recovery and monitoring requirements. It defines the receiving duty, fallback conditions and performance checks needed to assess process options, equipment submissions and delivered performance on a consistent basis.
Reuse and savings are developed against actual demand, operating modes, water offsets, disposal implications and site constraints. This keeps the technical requirements and value basis connected whether the assignment concerns design, procurement or review.
The baseline defines the conditions the project must handle. Requirements formalise what the system must achieve, how performance will be assessed and which operating and value assumptions the design must address.
Broad terms such as “TSE quality” or “fit for reuse” leave capacity, reliability, monitoring and fallback conditions open to different interpretations.
Designers, suppliers and operators work to the same duty, and commissioning tests can be linked to the requirements established before procurement.
EnWater defines the process-side requirements that subsequent process development, equipment duties, supplier submissions, integration and performance checks must follow. The output establishes the basis for evaluating the technical options developed next.
Each receiving use or discharge condition places different demands on quality, reliability, storage, distribution, monitoring and acceptance. This view shows how the requirements basis changes across common applications.
Define the receiving-system sensitivities, operating range and monitoring and acceptance criteria that the treatment and supply system must meet.
Cooling-water requirements matrix, operating ranges, monitoring plan and acceptance criteria for design, commissioning and early operation.
Define the intended reuse class, exposure conditions, distribution arrangements and verification requirements for the receiving area.
Landscape reuse duty, distribution conditions, monitoring requirements and acceptance criteria.
Define the health, soil, crop and long-term receiving conditions that the treatment, storage and distribution system must address.
Agricultural reuse requirements and verification plan aligned with receiving conditions and approval needs.
Define the receiving process sensitivities, continuity requirement and control conditions needed for stable operation.
Process reuse duty with continuity, control, monitoring and commissioning requirements.
Define the applicable consent conditions, operating range, sampling and reporting basis for normal, peak and upset conditions.
Discharge requirements, sampling and reporting basis, and value assumptions linked to avoided non-compliance and operating disruption.
Capacity, quality, reliability, reuse or discharge conditions, monitoring and acceptance criteria are formalised before process and equipment options are developed.
The requirements basis combines applicable regulations, receiving-use or outlet conditions, owner and operator needs, project constraints and defined future conditions.
01
Discharge consents, reuse classifications, receiving-party specifications, product or outlet requirements and any additional conditions for sensitive receptors or controlled uses.
02
Capacity, quality, reliability, recovery, operability, reporting and business requirements, together with the conditions the project team must carry into design and procurement.
03
Defined growth, future demand, likely changes in standards and the headroom or fallback provisions needed without inflating the design basis.
The source conditions are linked to the intended use, outlet or discharge condition so the design requirements reflect what the receiving system or party actually needs.
LIQUID
For STP, ETP, greywater, vehicle wash and laundry streams, applications such as cooling make-up, irrigation, washing, process water or discharge establish different quality, storage, distribution, reliability and monitoring requirements.
SOLIDS
For sludge, biosolids and other residuals, the intended product, thermal or disposal route establishes stability, dryness, contaminant, pathogen, storage, transport, testing and outlet acceptance requirements.
The same requirements discipline can be applied across operating plants and new projects handling:
Potential savings are defined from credible water offsets, utility and chemical changes, residuals and logistics, and avoided operating or compliance costs. They remain tied to specific operating modes, demand and fallback conditions.
01
Potential reductions in potable or desalinated water purchases, tanker use, energy, chemicals and network demand, based on available quantity, receiving demand and operating hours.
02
Changes in sludge or residuals volumes, handling, transport, return streams, disposal or outlet costs, including the conditions needed for a viable receiving route.
03
Assumptions, boundaries and sensitivity cases are recorded so internal approvals, lender review and reporting use a transparent basis without overstating savings.
Outputs are structured for process design, procurement, approval and later verification across the project team.
Duty to parameter to normal, peak and upset target to method to acceptance basis.
Capacity, quality, reliability, recovery, monitoring and fallback conditions.
Boundaries, connections, storage, distribution, residuals, utilities, controls and project responsibilities.
Application or outlet requirements, credible offsets, operating assumptions and sensitivity cases.
The completed requirements basis sets the capacity, quality, reliability, recovery, operating, monitoring and acceptance criteria that process and equipment options must address.
Technology and equipment configurations can then be developed or compared against that duty, including site constraints, residuals, operator needs, integration requirements and lifecycle implications.