11-CS-4 Engineering Law and Professional Liability · May 2013
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
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.
Effective scheduling begins not with dates but with a disciplined breakdown of the work. The central measure is to construct a Work Breakdown Structure (WBS) that decomposes the total scope hierarchically into progressively smaller, manageable work packages until each package is small enough to estimate, assign, and control. This requires that the scope first be clearly and completely defined, so that the decomposition is exhaustive and non-overlapping; each work package should have a defined deliverable and an identifiable owner. Once the packages exist, the activities within them are listed, their logical sequence and dependencies are established, and the resources and durations required for each are estimated. Milestones are then defined to mark significant completion points. The measures, in short, are: define scope precisely, decompose logically into work packages, assign responsibility, identify dependencies, and set measurable milestones—these convert an amorphous project into a controllable network of activities.
Accuracy of the resulting schedule depends on honestly accounting for the factors that govern how long work actually takes. Resource availability is primary: a schedule is only credible if the people, equipment, and facilities it assumes are genuinely available when needed. Task dependencies determine which activities must precede others and thereby fix the critical path along which any delay extends the whole project. Duration estimates must be realistic and reflect the skill levels and productivity of the assigned staff, including learning-curve effects on repetitive or novel work. Constraints such as fixed deadlines, budget limits, and equipment or workspace availability must be respected, and contingency or buffer time must be included to absorb the inevitable variability and risk. Calendar effects—holidays, shifts, and weather for field work—also affect achievable durations. Ignoring any of these produces a schedule that is precise on paper but wrong in practice.
Beyond the broad philosophy of Total Quality Management, several more specific quality techniques are used. Six Sigma applies the data-driven DMAIC cycle (Define, Measure, Analyze, Improve, Control) to reduce process variation toward a defect rate below 3.4 per million opportunities. Statistical Process Control (SPC) uses control charts to distinguish normal common-cause variation from special-cause variation that requires action. ISO 9000-series quality-management systems provide a documented, auditable framework for consistent processes. Quality Function Deployment (QFD) translates the voice of the customer into engineering requirements, and Failure Mode and Effects Analysis (FMEA) systematically anticipates and prioritizes potential failures before they occur. Complementary techniques include Lean waste elimination, poka-yoke (mistake-proofing), quality circles, benchmarking, and cost-of-quality analysis. These are largely compatible and are often combined, for example as "Lean Six Sigma."
A project engineer commissioning a water-treatment upgrade would build a WBS separating civil, mechanical, and controls work into work packages, sequence them so that tank construction precedes pump installation, and load realistic crew productivities and a weather buffer. During operation, SPC charts on effluent turbidity would separate normal variation from genuine excursions, while an FMEA performed during design would already have mitigated the highest-risk failure modes.
