22-Mec-B5 Product Design and Development · December 2013
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Paper format. National Exams, December 2013 — 07-Mec-B5, Product Design and Development. Three hours; open book; no calculator is permitted. Question 1 is compulsory and carries 40 marks; four of the remaining six questions are chosen, each worth 15 marks, for 100 marks in total, and only the first five questions appearing in the answer book are marked. Note 5 of the paper states that most questions require an answer in essay format or the use of tables, figures and charts, and that clarity and organisation of the answer carry marks; Note 1 invites the candidate to state any assumption made where a question is open to interpretation, and that licence is used several times below with every use flagged. All seven printed questions are worked here — 130 marks of material against the 100 marks a candidate would actually attempt — so that the set serves as a complete study resource. Because no calculator is allowed, every figure quoted below is one a candidate could reach by hand or by slide-rule-grade estimation; the arithmetic is nonetheless.
Reference texts. Ulrich & Eppinger, Product Design and Development (McGraw-Hill) — the framework text for this exam code and the source of the generic development process, the needs-to-metrics translation, concept screening and concept scoring used throughout; Dieter & Schmidt, Engineering Design (McGraw-Hill) for the specification, problem-definition and materials/process-selection material; Pahl & Beitz, Engineering Design: A Systematic Approach (Springer) for the function structure and systematic concept generation; Boothroyd, Dewhurst & Knight, Product Design for Manufacture and Assembly (CRC) for the DFMA rules and the design-for-assembly index; Ashby, Materials Selection in Mechanical Design (Butterworth-Heinemann) and Kalpakjian & Schmid, Manufacturing Engineering and Technology (Pearson) for the process-selection charts and unit-cost models; Cross, Engineering Design Methods (Wiley) for the design-versus-art material. Canadian context is taken from CSA B651 Accessible design for the built environment and CSA/ISO 21542, the Accessible Canada Act (2019) and provincial accessibility statutes, the Canada Consumer Product Safety Act, the Canadian Environmental Protection Act and its prohibited-substances regulations, ISO 4210-8 (cycle pedal and drive-system testing) as adopted in Canada, and Engineers Canada / EGBC guidance on professional practice.
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.
(1) Computer-aided design: geometry and product definition. Parametric, feature-based three-dimensional solid modelling is the backbone application. Its real contribution is not drafting speed but the creation of a single, unambiguous, associative definition of the product: features carry design intent as constraints and relations, assemblies carry mating conditions from which interference and clearance can be computed, and drawings, bills of material and downstream models all update from the same source. Model-based definition takes this a step further by placing tolerances and annotations on the solid model itself, so that the model rather than the drawing becomes the legal definition of the part. Around the modeller sits product data management, which controls revisions, releases and change orders — without it the model is merely a file, and a design office with several hundred files and no control has no product definition at all.
(2) Computer-aided engineering: analysis and simulation. Finite element analysis for stress, deflection, vibration, buckling and fatigue; computational fluid dynamics for flow and thermal performance; multibody dynamics for mechanisms; injection-moulding flow simulation for filling, warpage and weld lines; and tolerance-stack and reliability simulation for statistical performance. The purpose is to replace an expensive, slow physical iteration with a cheap, fast numerical one, so that far more of the design space is explored before metal is cut. The discipline that makes it useful is validation: an analysis is only evidence once its model has been checked against a physical test or a closed-form result on a case where both are available.
(3) Computer-aided manufacturing and the digital thread to production. Toolpath generation and post-processing for CNC machining, tooling and mould design driven directly off the part model, additive manufacturing for prototypes, tooling inserts and increasingly for production parts, coordinate-measuring-machine inspection programmes generated from the same model, and the ERP and MRP link that turns the bill of material into purchase orders and production schedules. This is the application that closes the loop: the geometry the designer creates is the geometry that is made and the geometry that is inspected, and the elimination of re-interpretation between those steps is where most of the historic scrap and rework went.
Five shifts are visible and are worth naming individually. From document to model to digital twin. The centre of gravity has moved from the drawing to the model and is now moving to a live instrumented model of the particular unit in service, fed by sensor data, which lets designers see how the product is actually used and how it actually degrades rather than how they assumed it would.
From desktop to cloud and to genuine concurrency. Modelling and analysis increasingly run as services on rented compute, which removes the licence and workstation barrier to large simulations, makes multi-site and supplier collaboration on one dataset routine, and permits the kind of overnight thousand-run design-of-experiments study that was a research activity twenty years ago. It also raises real questions of data residency and control that a Canadian practitioner must consider when the design data of a client sits on servers in another jurisdiction.
From analysis to synthesis. The historic pattern was that a human proposed geometry and the computer evaluated it. Topology optimisation and generative design invert that: the engineer specifies the load cases, the constraints, the keep-out volumes and the objective, and the software proposes the geometry — often organic forms that only additive manufacturing can make. Machine-learned surrogate models are now fast enough to put an approximate simulation inside the modelling loop, so the designer sees a stress estimate update as the geometry is dragged.
From batch analysis to integrated, real-time simulation, including immersive review in virtual and augmented reality for ergonomics, maintenance access and human-factors assessment before a prototype exists; and from performance-only to lifecycle-aware tools, with cost estimation, manufacturability checking and life-cycle environmental assessment built into the modeller so that a material substitution shows its cost and carbon consequence immediately.
The designer's role narrows in the areas the tools have absorbed and deepens in the areas they cannot. What the computer does not do is decide what problem to solve. Framing an ill-structured situation as a design problem, identifying who the stakeholders are and what they actually need, choosing which requirements are negotiable, and recognising that the specification itself is wrong — these remain human. Generative design will optimise faithfully against the objective it is given and will do so most impressively when the objective is mis-stated.
Second, the designer owns judgement under uncertainty and accountability for the outcome. Analysis output is not truth: meshes, boundary conditions, material models and failure criteria all embed assumptions, and someone must decide whether the result is credible. In Canadian practice this is not merely good sense but a legal obligation — under the provincial engineering Acts the engineer who seals the work takes professional responsibility for it, and that responsibility cannot be transferred to a software vendor. EGBC's guidance on the use of software is explicit that the practitioner must understand the tool's limitations and verify its results.
Third, the designer supplies synthesis, empathy and ethical weighing — integrating a manufacturing constraint, a regulatory limit, a cost target and a user's dignity into one artefact, and deciding what should be built and not merely what can be. Fourth, the designer curates the tools themselves: choosing methods, validating models, and maintaining the discipline that keeps a digital thread trustworthy. The realistic summary is that computers have raised the level of abstraction at which designers work, much as calculators and then solvers did before them, and have correspondingly raised the penalty for a designer who has lost the physical intuition needed to recognise a wrong answer.
