Structural design process: Difference between revisions

From Engineer-it
No edit summary
No edit summary
Line 18: Line 18:
* The degree to which the context is [[Risk#Safety-critical systems|safety-critica]]<nowiki/>l.  Most structures are safety-critical to some degree.  The safety of the users of the structure should be treated as the responsibility of all involved in the design including the client.  Safety criteria must be accepted as non-negotiable when making decisions.  [Refer to case studies of failures:  Tay Bridge, Edinburgh schools, Grenfell Tower Fire, Florida Bridge]
* The degree to which the context is [[Risk#Safety-critical systems|safety-critica]]<nowiki/>l.  Most structures are safety-critical to some degree.  The safety of the users of the structure should be treated as the responsibility of all involved in the design including the client.  Safety criteria must be accepted as non-negotiable when making decisions.  [Refer to case studies of failures:  Tay Bridge, Edinburgh schools, Grenfell Tower Fire, Florida Bridge]


'''''Plan'''''  Work to a plan for the design work
'''''Plan'''''  Work to a plan for the design activities.


'''''Review and revise'''''  The process is not normally linear. There may be backtracking.  It is essential (a) to shedule regular meetings to review progress and to check outcomes against requirements and (b) to be  constantly alert for unforseen circumstances, faults, erors.
'''''Review and revise'''''  The process is not normally linear. There may be backtracking.  It is essential (a) to shedule regular meetings to review progress and to check outcomes against requirements and (b) to be  constantly alert for unforseen circumstances, faults, erors.
Line 30: Line 30:
'''''Option analysis''' ''Develop a set of options to a degree of detail sufficient to assess them against the requirements. Compare them against the requirements and decide on the form of the structure to be used.
'''''Option analysis''' ''Develop a set of options to a degree of detail sufficient to assess them against the requirements. Compare them against the requirements and decide on the form of the structure to be used.


'''''Refine the design'''''  Carry out technical assessment (assess against codes of practice) and carry out further checks against all requirements.
'''''Refine the design'''''  Carry out technical assessment (mainly using codes of practice) and carry out further checks against all requirements.


'''''Design output''''' Produce drawings, specifications, etc.
'''''Design output''''' Produce drawings, specifications, etc.

Revision as of 10:56, 24 May 2021

Figiure 1 shows how, when creating a structure, one starts with a requirements statement that defines the performance of the structure. This is transformed by a design process into design output, i.e. into information about what the structure will be. A construction process then transforms the design output into the physical structure.

File:Des-proc-1.png
Figure 1 Engineering a structure


Figure 2 Structural design process

The structural design process (Figure 2) is an instance of the Top-down strategy.

Design activities

Main design activities include:

Resource allocation A budget for the design work needs to be established. This depends on:

  • What the client is prepared to pay for
  • Whether the design is innovative. Innovation increases the risk of unsatisfactory outcomes and requires more detailed attention to design process activiites.
  • Whether the context is familiar to the members of the design team, Experience can allow some decisions to be made with less attention to detail.
  • The degree to which the context is safety-critical. Most structures are safety-critical to some degree. The safety of the users of the structure should be treated as the responsibility of all involved in the design including the client. Safety criteria must be accepted as non-negotiable when making decisions. [Refer to case studies of failures: Tay Bridge, Edinburgh schools, Grenfell Tower Fire, Florida Bridge]

Plan  Work to a plan for the design activities.

Review and revise The process is not normally linear. There may be backtracking. It is essential (a) to shedule regular meetings to review progress and to check outcomes against requirements and (b) to be constantly alert for unforseen circumstances, faults, erors.

Gather information - about the site, about the regulatory framework, etc.

Establish the requirements. Based on a client brief and  a list of design issues (see diagram below), establish a requirements statement. Seek to ensure that the requirements are all identified at the start of the design process because adding requirement later can result in re-work and extra cost - but, if at a later stage important further requirements are identified, add them to the list.

Use the requirements  Make a checklist of the requirements and keep checking that you are satisfying them as the work proceeds.

Option analysis Develop a set of options to a degree of detail sufficient to assess them against the requirements. Compare them against the requirements and decide on the form of the structure to be used.

Refine the design Carry out technical assessment (mainly using codes of practice) and carry out further checks against all requirements.

Design output Produce drawings, specifications, etc.

Structural design issues

Figure 3 illustates some of the issues that may need to be considered in structural design.

Figure 3 Structual desing issues

Working with other disciplines

Adopt a holistic view (i.e. address all relevant issues) both in the structural context and in relation to the other disciplines that may be involved in the project, i.e. actively collaborate with contractors, architects, building services engineers, environmental specialists, etc.


Critical thinking principles needed in the design process

[to be drafted]