![]() |
WaterWare Reference & User Manual | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Last modified on: Thursday, 20-May-10 18:22 CEST |
WRM web version: Treatment nodesA WRM scenario can include any number of treatment nodes. A treatment node represents a water or wastewater treatment plant; its primary purpose is to modify the quality of its constrained through-flow. The treatment node includes an implicit bifurcation: inflow that exceeds its hydraulic capacity is automatically routed to a bypass, untreated. The following data are defined for a treatment node:
Node functionalityA TREATMENT node is neutral in respect to flow; its role is to modify water quality. From a hydraulic point of view, it operates like a geometry node (completely passive).Effect on water quality:a the node reduces pollutant concentration in its inflow according to the specified removal efficiencie - up to its hydraulic capacity ! Inflow beyond hydraulic capacity (e.g., due to stormwater runoff) is asssumed to bypass the treatment node, leading to a mixture of treated and untreated water in its outflow. Dynamic Output Time Series:
Development Notes:NOT YET IMPLEMENTED; will need a simple economic model for operating costs, sludge generated, etc.
|
