18-Env-B5 Industrial & Hazardous Waste Management · December 2014
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Reference texts: Nemerow & Dasgupta, Industrial and Hazardous Waste Treatment, 2nd ed.; Metcalf & Eddy, Wastewater Engineering: Treatment and Resource Recovery, 5th ed.; Davis & Cornwell, Introduction to Environmental Engineering, 6th ed.; LaGrega, Buckingham & Evans, Hazardous Waste Management, 2nd ed.; CCME, Guidelines for the Management of Biomedical Waste in Canada (1992); Canadian Environmental Protection Act (CEPA), 1999; provincial Environmental Protection / Hazardous Waste Regulations (e.g. BC's Hazardous Waste Regulation, O.Reg. 347 in Ontario); Montgomery & Runger, Applied Statistics and Probability for Engineers (for Q1–Q5's basic-statistics content).
Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.
An engineer collects data for four principal reasons, each answering a different question about a system. (1) To characterize current conditions — establishing a baseline (e.g. a wastewater stream's average and range of BOD/TSS/flow) so that a design or a regulatory limit is set against real, not assumed, values. (2) To detect change or trend — comparing successive measurements over time reveals whether a process, an effluent, or an environmental medium is improving, degrading, or holding steady, which cannot be judged from a single snapshot. (3) To verify compliance or performance — regulators and plant operators alike need measured data (not design assumptions) to confirm a treatment system is actually meeting its permit limits or its design removal efficiency. (4) To support decision-making and design — sizing new infrastructure, selecting a treatment process, or justifying capital expenditure all require statistically defensible input data rather than a single unrepresentative reading. Underlying all four is the same principle: engineering decisions made on inadequate or unrepresentative data carry a real risk of under- or over-design, and data collection is how that risk is reduced to an acceptable, quantifiable level.
In an industrial or hazardous-waste practice specifically, these four reasons interact: a baseline established for a permit application later becomes the trend record a regulator checks during renewal, and the same monitoring program that verifies day-to-day compliance is usually the dataset an engineer later mines to justify a capital upgrade. Treating data collection as a one-off exercise tied to a single deliverable, rather than a continuing program serving all four purposes at once, is a common and avoidable inefficiency in practice.