18-Env-B1 Environmental Assessment and Management Systems · May 2017
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Reference texts: Mihelcic & Zimmerman, Environmental Engineering: Fundamentals, Sustainability, Design; Davis & Cornwell, Introduction to Environmental Engineering (6th ed.); ISO 14001:2015, Environmental Management Systems — Requirements with Guidance for Use; ISO 14040/14044, Life Cycle Assessment — Principles and Framework; Canadian Environmental Protection Act, 1999 (CEPA); Impact Assessment Act, 2019 (Canada); World Commission on Environment and Development, Our Common Future (the Brundtland Report), 1987.
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.
(i) Legislation example — the BC Environmental Management Act (provincial) — and its compliance, abatement and enforcement elements. 1. Compliance. The Act requires dischargers to hold and operate within a permit or approval (effluent, air emission or waste-discharge permits) that sets specific numeric and operational conditions, giving the regulator a clear, auditable baseline against which routine self-monitoring and reporting confirm the facility is operating as authorized. 2. Abatement. Where a discharge is found to be causing or about to cause pollution, the Act empowers the regulator to issue an abatement order requiring the responsible party to reduce, control or cease the discharge and remediate any resulting contamination, providing a corrective mechanism that operates faster than a full prosecution. 3. Enforcement. Inspection powers, administrative monetary penalties and prosecution provisions for non-compliance give the compliance and abatement elements real consequence — without an enforcement mechanism, permit conditions and abatement orders would be voluntary in practice, undermining the framework's ability to ensure environmental protection.
(ii) Two EIA indicators to mitigate flooding/erosion in a wetland from upstream residential intensification, technical vs. non-technical.
| Indicator | Approach type | How it mitigates flooding/erosion & cost-benefit |
|---|---|---|
| Impervious-surface area / peak-runoff-coefficient change in the upstream catchment | Technical (GIS/hydrologic modelling) | Quantifies how much the intensification increases peak stormwater discharge and reduces infiltration, directly predicting the added flood/erosion loading on the wetland; higher upfront modelling cost but gives a defensible, design-basis number for sizing detention and setting development conditions. |
| Community-reported wetland water-level/erosion observation and traditional-use monitoring | Non-technical (community/citizen-science observation) | Local and Indigenous observation of shoreline erosion, changed water levels and habitat condition captures real-world change across the full wetland extent at very low cost, and often flags a problem before an instrumented gauge network (which only samples specific points) would detect it, though it is less precise for setting a numeric design threshold. |
Comparing technical vs. non-technical effectiveness. The technical (impervious-area/runoff) indicator is more effective at establishing a quantified, defensible causal link between the upstream intensification and the wetland's flood/erosion risk, and is what a stormwater-management bylaw or detention-sizing requirement must ultimately be based on — but it is costly to model at fine spatial detail and only as good as the land-use assumptions fed into it. The non-technical, community-based indicator is far lower cost and covers the full wetland extent continuously, catching real change (an eroding bank, a shifted water regime) that a coarse model might miss between updates, but cannot by itself set an enforceable numeric development condition. The strongest EIA uses both together: community observation flags where and what to investigate, and the technical runoff/hydrologic model turns that observation into an enforceable stormwater-detention or development-setback requirement.
