18-Env-A1 Principles of Environmental Engineering · December 2019
Question 2 of 7: Engineering Ethics and Water/Wastewater Source Design Principles
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Notes on this paper
National Exams — December 2019 — 18-Env-A1 / Principles of Environmental Engineering. 3 hours duration; closed book with a candidate-prepared 8.5×11 in double-sided aid sheet; Casio or Sharp approved calculator only. Any five questions constitute a complete paper (first five answers marked); all seven are solved below for completeness. Each question is worth 20 marks.
Reference texts. Davis & Cornwell, Introduction to Environmental Engineering (6th ed.); Metcalf & Eddy, Wastewater Engineering: Treatment and Resource Recovery (5th ed.); MWH’s Water Treatment: Principles and Design (3rd ed.); Sawyer, McCarty & Parkin, Chemistry for Environmental Engineering and Science; Guidelines for Canadian Drinking Water Quality (Health Canada); Canadian Council of Ministers of the Environment (CCME) water-quality and municipal solid-waste guidelines; Canadian Environmental Protection Act, 1999 (CEPA) and Canadian Environmental Assessment Act (CEAA 2012); Bies & Hansen, Engineering Noise Control; Andrews, Canadian Professional Engineering and Geoscience (professional ethics).
(i) Ethical Actions for the Contracted Filter-Performance Engineer
The engineer’s paramount duty is to public health and safety, not to the commercial interest of the supplier who engaged the contract, so the finding that E. coli log-reduction is inadequate at high flow triggers a defined escalation sequence rather than a discretionary choice:
Document the finding rigorously and immediately. Record the tested flow rates, measured E. coli log-reduction versus the target, and the resulting risk that filtered water will fail the bacteriological criteria for potable water at high flow — a clear factual record is the basis for every subsequent ethical action and protects both the public and the engineer’s own professional position.
Report the finding fully and promptly to both the supplier and the municipality, per principle (b). The engineer was hired to report on filter effectiveness, and that reporting obligation is not satisfied by reporting only the favourable TSS result to the paying client (the supplier); the E. coli shortfall directly affects potable-water bacteriological compliance and must be communicated to the municipality as the party responsible for public health, not withheld or softened at the supplier’s request.
Recommend a specific remedy or interim safeguard, not merely flag the problem. Under principle (a) (health, safety and welfare paramount), the engineer should recommend concrete next steps — a supplementary disinfection barrier at high flow, a flow limit until the filter is upgraded, or additional monitoring — so the municipality is not left with a known risk and no path forward.
Escalate within professional/regulatory channels if the supplier or municipality does not act. If, after being informed, neither the supplier nor the municipality takes adequate corrective action and a significant unresolved risk to public health remains, the engineer has a professional obligation to escalate — first through the responsible regulatory authority (e.g., the drinking-water regulator) — consistent with principle (b)’s statement that the engineer may ethically make the concern known publicly when a significant risk remains unresolved.
Making the concern known publicly is a last resort, not a first step. Public disclosure is ethically available only once internal reporting and regulatory escalation have failed to resolve a genuine, significant, unresolved risk — acting to protect public health while still respecting the professional obligation to pursue proper channels first.
(ii) Three Design/Operational Principles: Surface Water Versus Groundwater Sources
Surface water and groundwater differ fundamentally in raw-water quality variability, pathogen/turbidity risk and available quantity, so a treatment facility drawing on one versus the other must be designed around different governing principles:
Raw-water quality variability and required treatment train (quality). Surface water quality (turbidity, pathogen load, organics, temperature) varies significantly with season, storm events and upstream land use, so a surface-water plant must be designed with a full multi-barrier train — coagulation/flocculation, filtration and disinfection — sized for worst-case turbidity/pathogen spikes. Groundwater is typically far more stable in quality (naturally filtered by the aquifer matrix) and often needs only disinfection, though it may require dedicated treatment for aquifer-specific dissolved constituents (iron, manganese, arsenic, or hardness) not usually present in surface supplies.
Pathogen risk profile and disinfection design basis (quality). Surface water is directly exposed to fecal contamination and carries a credible Giardia/Cryptosporidium risk, so disinfection (and often filtration) must be designed to a specific log-removal/inactivation target for these protozoa. Groundwater is generally presumed pathogen-free unless it is under the direct influence of surface water (GUDI), in which case it must be treated as if it were surface water — a key operational determination that changes the entire design basis.
Source yield, reliability and withdrawal management (quantity). Surface-water intakes must be sized for a design low-flow condition (to guarantee the source remains available during drought) and require intake-screening/fish-protection design tied to the water body’s ecology. Groundwater withdrawal must instead be managed against sustainable aquifer yield and drawdown — over-pumping can permanently reduce aquifer capacity, cause land subsidence, or draw in saline intrusion near coastal aquifers — so long-term well-field yield testing and drawdown monitoring take the place of surface low-flow analysis.