1 fundamental concept
Meaning
Engineering design is the disciplined process of developing a solution to a defined problem while satisfying technical requirements, performance objectives, constraints, and responsibilities to society. It is more than producing drawings or calculating dimensions. It involves understanding the problem, investigating relevant conditions, evaluating alternatives, predicting performance, identifying uncertainties, and demonstrating that the selected solution is appropriate.
Design as an engineering activity
Problem solving: identifying an existing deficiency or a need for a new infrastructure system.
Synthesis: combining scientific knowledge, materials, components, technologies, and engineering methods into a coherent solution.
Analysis: predicting how the proposed system will behave under expected and reasonably foreseeable conditions.
Evaluation: comparing alternatives against safety, performance, cost, environmental impact, and other requirements.
Verification: checking that calculations, models, drawings, specifications, and design outputs satisfy their stated requirements.
Communication: documenting the design assumptions, decisions, limitations, and requirements so that other project participants can understand and review them.
Design vs analysis
Design
Determines what system or configuration should be developed to meet the project requirements.
Analysis
Examines the expected behaviour and performance of a proposed system using scientific principles, mathematical models, simulations, and engineering judgment.
Relationship
Design and analysis are complementary and iterative. An initial design is analysed, its performance is evaluated, and the design is revised when the results reveal deficiencies or opportunities for improvement.
2 primary design principles
Safety
Explanation
The design must protect people from unacceptable risks during construction, operation, maintenance, modification, and eventual decommissioning. Safety considerations include structural stability, fire protection, traffic safety, occupational hazards, environmental exposure, and emergency conditions.
Engineering application
Engineers identify hazards, establish appropriate performance criteria, apply relevant standards, assess uncertainties, and arrange suitable independent reviews.
Functionality and performance
Explanation
An infrastructure system must perform the functions for which it is intended. A road must provide appropriate mobility, a water distribution system must deliver an adequate supply, and a building must provide usable and appropriate spaces.
Engineering application
Functional requirements are translated into measurable criteria such as capacity, accessibility, operating conditions, service coverage, response time, and permitted performance limits.
Serviceability
Explanation
A system may remain structurally stable yet become unsuitable for normal use because of excessive deformation, vibration, cracking, settlement, leakage, discomfort, or operational difficulties.
Engineering application
Engineers evaluate performance under normal service conditions, not only under extreme conditions associated with structural safety.
Durability
Explanation
Durability is the ability of infrastructure to maintain its required properties and performance over its intended service life despite environmental exposure, material deterioration, repeated loading, and operational conditions.
Engineering application
Material selection, protective systems, drainage, exposure classification, inspection access, maintenance planning, and appropriate detailing contribute to durability.
Reliability and robustness
Explanation
Reliability concerns the likelihood that a system will perform its required function under specified conditions. Robustness concerns its ability to avoid disproportionate consequences when an unexpected local problem or component failure occurs.
Engineering application
Designers consider uncertainty, redundancy, alternative load paths, component dependencies, inspection, and the consequences of possible failures.
Economy and value
Explanation
A design should provide appropriate performance and public value without unnecessary expenditure. The cheapest initial option is not necessarily the most economical over the entire service life.
Engineering application
Engineers compare capital expenditure, operation, maintenance, repair, replacement, environmental costs, and expected service life.
Constructability
Explanation
A technically satisfactory design must also be realistically and safely buildable using available construction methods, equipment, materials, skills, access, and site conditions.
Engineering application
Construction sequencing, temporary conditions, material availability, transportation constraints, and coordination between disciplines are considered during design.
Maintainability
Explanation
Infrastructure should allow inspection, cleaning, servicing, repair, and replacement without unreasonable difficulty or disruption.
Engineering application
Designers consider access routes, inspection spaces, replaceable components, drainage maintenance, utility access, and the availability of spare parts.
Sustainability
Explanation
Sustainable design considers environmental protection, resource efficiency, social outcomes, and long-term economic viability across the infrastructure lifecycle.
Engineering application
Engineers assess material consumption, embodied carbon, operational energy, water use, waste, biodiversity, pollution, adaptability, and opportunities for reuse.
Accessibility and inclusiveness
Explanation
Infrastructure should be usable by people with different abilities, ages, mobility requirements, and social circumstances, subject to the applicable accessibility requirements.
Engineering application
Design considerations may include accessible routes, appropriate gradients, crossings, tactile information, clear circulation, safe public spaces, and inclusive facilities.
Resilience and adaptability
Explanation
Resilient infrastructure can prepare for, withstand, respond to, recover from, and adapt to disruptive events. Adaptable infrastructure can accommodate changing demands, technologies, environmental conditions, and future development.
Engineering application
Designers consider climate hazards, extreme events, changing population patterns, future capacity, repair strategies, and opportunities for phased expansion.
3 design requirements and constraints
Requirements
Definition
Requirements describe what the proposed infrastructure must achieve. They should be sufficiently clear to guide design development and later evaluation.
Categories
| Category | Description |
|---|---|
Functional requirements | Specify the services and activities that the infrastructure must support. |
Performance requirements | Specify measurable expectations for capacity, strength, movement, reliability, service quality, or environmental performance. |
Safety requirements | Establish acceptable safety objectives and applicable protective provisions. |
Regulatory requirements | Identify relevant legislation, planning permissions, technical codes, environmental requirements, and approval conditions. |
Operational requirements | Describe how the asset will be operated, inspected, maintained, and managed. |
Sustainability requirements | Set expectations for environmental performance, resource efficiency, social outcomes, and lifecycle impacts. |
Constraints
Available project budget and funding conditions.
Site dimensions, topography, geology, and existing ground conditions.
Climate, rainfall, temperature, wind, flooding, and other environmental conditions.
Existing roads, buildings, utilities, and neighbouring infrastructure.
Applicable laws, standards, building codes, and planning restrictions.
Availability of materials, equipment, skilled labour, and construction technology.
Project schedule, procurement arrangements, and construction access.
Community needs, land-use conditions, cultural heritage, and environmental protection.
Requirements vs constraints
Requirements describe the outcomes that must be achieved, whereas constraints describe conditions that restrict or influence the available solutions. A design must satisfy its requirements while remaining feasible within its constraints.
4 engineering design methodology
Overview
A structured design methodology reduces the possibility of overlooking important requirements and makes engineering decisions easier to evaluate, communicate, and review. The process is iterative: new information, analysis results, stakeholder feedback, or changed conditions may require earlier decisions to be reconsidered.
Stages
| Stage | Name | Activities | Output |
|---|---|---|---|
1 | Problem identification |
| A clearly stated problem definition and preliminary project justification. |
2 | Stakeholder and requirement analysis |
| A documented set of stakeholder needs and project requirements. |
3 | Investigation and information collection |
| A documented project information base with identified assumptions and uncertainties. |
4 | Concept development |
| A range of conceptual alternatives. |
5 | Feasibility assessment |
| A justified shortlist or preferred concept. |
6 | Preliminary design |
| A preliminary design suitable for comparison and review. |
7 | Detailed design and analysis |
| A coordinated detailed design package. |
8 | Verification and independent review |
| A reviewed and verified design package. |
9 | Approval and construction support |
| An appropriately approved design and documented construction support. |
10 | Commissioning and feedback |
| A documented handover and performance feedback record. |
5 design approaches and methods
Systems engineering
Description
A systems approach treats infrastructure as a collection of interacting components and processes rather than as isolated structures. It examines system boundaries, interfaces, dependencies, performance, and lifecycle requirements.
Application
Useful for transport networks, water supply systems, urban drainage, and large infrastructure programmes.
Performance based design
Description
Performance-based design establishes measurable performance objectives and evaluates whether a proposed solution achieves them. It can complement prescriptive requirements where the applicable regulatory framework permits it.
Application
Used when projects have unusual conditions, complex performance requirements, or a need to compare alternative solutions.
Risk informed design
Description
Risk-informed design uses the likelihood and consequences of possible adverse events to help prioritize investigations, protective measures, reviews, and monitoring.
Application
Useful for flood protection, critical infrastructure, complex structures, and projects with significant uncertainty.
Value engineering
Description
Value engineering is a structured method for improving the relationship between required functions and the resources used to provide them. It examines whether a function can be delivered more effectively without compromising essential safety or performance requirements.
Application
Used to compare alternative layouts, construction systems, materials, operational arrangements, and maintenance strategies.
Design for lifecycle
Description
Lifecycle-oriented design considers the asset from initial planning through construction, operation, maintenance, rehabilitation, adaptation, and eventual decommissioning.
Application
Prevents decisions that reduce initial expenditure but create excessive future operating, repair, or replacement costs.
Human centred and participatory design
Description
This approach considers how people experience and use infrastructure. It involves relevant users and communities in identifying needs, evaluating alternatives, and reviewing the usability of proposed solutions.
Application
Particularly important for public spaces, transport facilities, pedestrian infrastructure, community water systems, and urban development.
Digital and model based design
Description
Digital design uses computer-aided design, building information modelling, geographic information systems, simulation, and other computational methods to coordinate information and evaluate alternatives.
Application
Supports multidisciplinary coordination, visualization, information management, and lifecycle asset planning.
6 design evaluation and decision methods
Multi criteria decision analysis
Description
Multi-criteria decision analysis compares alternatives using several criteria rather than relying on one measure such as initial cost.
Typical criteria
Safety and regulatory compliance.
Technical performance and reliability.
Capital and lifecycle cost.
Construction duration and feasibility.
Environmental impact.
Social benefit and accessibility.
Maintenance requirements and adaptability.
Weighted scoring
Formula
Sᵢ = Σ(wⱼ × rᵢⱼ)
Variables
Sᵢ
Overall evaluation score for alternative i.
Wⱼ
Weight assigned to criterion j.
Rᵢⱼ
Normalized performance rating of alternative i against criterion j.
Conditions
The weights and ratings should be established transparently. The result depends on the selected criteria, scoring method, and assumptions. Weighted scoring must not be used to trade away mandatory safety or legal requirements.
Lifecycle cost analysis
Description
Lifecycle cost analysis estimates the relevant costs of an asset over a defined analysis period, considering the timing of expenditure and, where appropriate, discounting future costs.
Simplified present value
PV = C₀ + Σ[Cₜ / (1 + r)ᵗ]
Variables
PV
Present value of the considered costs, expressed in the selected currency.
C₀
Initial cost at the reference time.
Cₜ
Cost occurring at time t.
R
Discount rate per period, expressed as a decimal.
T
Number of periods from the reference time.
Limitations
Results depend on the analysis period, discount rate, cost forecasts, maintenance assumptions, and treatment of uncertainty. Environmental and social effects may require separate assessment.
Sensitivity analysis
Description
Sensitivity analysis examines how changes in uncertain input values affect design results or project decisions.
Example
A transport project may be evaluated under different future traffic-demand assumptions to understand whether its capacity and economic performance remain acceptable.
Benefit
It identifies assumptions that strongly influence the outcome and helps determine where additional investigation is valuable.
Design review
Description
A design review is a structured examination of design objectives, assumptions, calculations, interfaces, risks, drawings, and specifications by appropriate project participants or independent specialists.
Review questions
Does the design address the actual project need?
Are the design criteria and assumptions clearly stated?
Are the investigation data appropriate and sufficiently reliable?
Have relevant hazards and failure modes been considered?
Are the design disciplines properly coordinated?
Can the proposed asset be constructed, operated, inspected, and maintained?
Are unresolved issues documented and assigned for action?
7 important engineering considerations
Uncertainty
Civil engineering design relies on information that may be incomplete or variable. Soil properties, future demand, material characteristics, environmental conditions, and construction quality cannot always be predicted exactly. Engineers therefore identify uncertainty, use appropriate investigation and modelling methods, and apply the safety and reliability provisions required by the relevant design framework.
Engineering assumptions
Assumptions simplify complex real-world conditions so that engineering analysis can be performed. Every significant assumption should be reasonable, documented, checked against available evidence, and reconsidered when new information becomes available.
Model validation
A mathematical or computational model is a simplified representation of a real system. Its results should be assessed against relevant physical principles, test information, observations, or other suitable evidence.
Interdisciplinary coordination
A design decision in one discipline may affect other disciplines. For example, changing a bridge alignment can influence foundations, road geometry, drainage, utilities, environmental effects, and construction access.
Change management
Design changes should be reviewed and documented. Their effects on requirements, calculations, approvals, construction information, and asset records must be considered.
8 practical case study
Scenario
A community requires a safer pedestrian crossing over a drainage channel that separates residential areas from a school and local services.
Methodology
| Step | Action | Reason | Expected output |
|---|---|---|---|
1 | Define the problem. | Establish why the existing crossing arrangement is inadequate and identify who needs to use the proposed facility. | A documented need for safe and accessible pedestrian connectivity. |
2 | Establish requirements. | Identify pedestrian demand, accessibility needs, flood conditions, environmental constraints, expected service life, and applicable approvals. | Measurable project requirements and constraints. |
3 | Investigate the site. | Obtain appropriate topographic, geotechnical, hydrological, utility, and environmental information. | A reliable basis for comparing possible crossing arrangements. |
4 | Develop alternatives. | Compare different crossing locations and feasible infrastructure concepts, including whether an existing route can be improved. | Several technically plausible alternatives. |
5 | Evaluate alternatives. | Assess safety, accessibility, flood performance, environmental effects, constructability, cost, and maintenance. | A justified preferred concept. |
6 | Develop and review the design. | Qualified professionals develop the necessary engineering design under applicable standards and arrange appropriate technical review. | A coordinated and reviewed design package. |
7 | Plan operation and maintenance. | Ensure that the completed crossing can be inspected, maintained, and managed throughout its service life. | An operation and maintenance plan. |
Learning point
The engineering solution is not selected merely because a bridge can physically span the channel. It must also address the community's actual needs, flood conditions, accessibility, safety, environmental effects, construction feasibility, and long-term maintenance.
9 common mistakes
| Mistake | Why it is problematic | Better approach |
|---|---|---|
Choosing a solution before understanding the problem. | The project may solve the wrong problem or overlook a simpler and more effective alternative. | Define the need and project requirements before committing to a particular design. |
Treating initial cost as the only measure of value. | Low initial expenditure may lead to higher maintenance, operational, or replacement costs. | Compare lifecycle costs and performance. |
Using assumptions without documenting them. | Other engineers cannot reliably review the design basis, and incorrect assumptions may remain undetected. | Maintain a clear design basis and assumption register. |
Ignoring interfaces between engineering disciplines. | A locally acceptable design decision may create problems elsewhere in the infrastructure system. | Coordinate design disciplines and review interfaces throughout the project. |
Assuming software output is automatically correct. | Computational results depend on model assumptions, input quality, boundary conditions, and correct interpretation. | Verify inputs, validate models, review results independently, and use engineering judgment. |
Ignoring operation and maintenance. | The completed asset may be difficult or expensive to inspect, operate, or repair. | Include operators and maintenance requirements in the design process. |
10 learning activities
Conceptual exercise
Choose a familiar infrastructure asset, such as a local road, drainage channel, public building, or water supply system. Identify its users, functions, performance requirements, constraints, and principal lifecycle considerations.
Comparison exercise
Develop three conceptual alternatives for improving a local pedestrian route. Compare them using safety, accessibility, environmental effects, initial cost, maintenance, and constructability. Treat mandatory safety and legal requirements as conditions that every acceptable alternative must satisfy.
Critical thinking questions
Why is engineering design an iterative process rather than a strictly linear sequence?
How can a design be structurally safe but still fail to provide satisfactory service?
Why should maintenance requirements influence early design decisions?
What are the limitations of a weighted decision-making model?
How can stakeholder participation improve infrastructure design?