Framework for structural design learning
The framework is a collection of ideas/information that may be used in structural engineering design
Features of the framework include ethos, examples, guidance and processes.
There is a focus on the use of a structural design brief. See also here. Identifying all requirements and ensuring that they are properly addressed are key actions in reducing the risk of unsatisfactory outcomes.
Ethos
Ethos is about how you think, about the principles that guide your actions, about being a critical thinker, Critical thinkers use the strategies described in Chapter 1. They submit to a discipline for establishing outcomes that best satisfy the goals. For ideas about learning to be a critical thinker see this paper.
Examples
It is very useful for learners to have available examples of typical outcomes - see Footbridge example..
Guidance
See here.
Processes
Working with processes and seeking to improve them is a core issue in good design. Analys for validation (is the process appropriate?) and for verification (has the process been correctly implemented?) need to be regularly carred out.
The Structural Design Process
See here.
Process mapping
The Institution of Structural Egineers publishes a Structural Plan of Work that sets out an overall process for structural engineers working on the design of a building. It is based on the Royal Institute of British Architects (RIBA) Plan of Work
The stages in the IStructE Plan of Work are shown in Figure 1.
A simpler form of the Plan of Work for design is shown in Table 1..
Design Programme
In any complex operation, it is important to work to a project programme
The modelling process
See here.
Control strategies
See here
Design Documents
Key output documents are shown in Table 2
| Stage | Activities | Design documents | |
| 0 | Strategic definition | Receive client brief and initial site information. | Client requirements |
| 1 | Preparation and briefing | Develop the Structural Design Brief.
Develop the Site Information Document. |
Structural Design Brief - stage 1
Site information document |
| 2 | Concept design | Carry out an options analysis.
Decide on the option to be used. Develop a partial design for the structure. |
Structural Design Brief - stage 2
Options Analysis Report Design Proposal - stage 2 |
| 4 | Technical design | Ensure that all requirements have been adequately adddressed. | Design verification |
| 4.5 | Production information | Prepare drawings | Drawings and specifications |
Client requirements
The client requirements that relate to the structure.
Site information
This document may include information about: topography, existing site features, former usage, services, ground conditions, etc.
Structural design brief
This is a collection of all requirements that may affect the structural design including information about the processes to be used.
The brief is established at the Inception Stage. At this stage it should, if practical, not relate to a specific structural form.
The brief is developed at te Concept Stage based on information from the options analysis.
Changes to the brief should be avoided, if practical, after the Concept Sstage
This guidance about the project brief in the RIBA plan of work states that: "The project brief is likely to be presented as a report, however, where possible, information and requirements should be scheduled in a database or spreadsheet format that will be easy to expand and will be easy to use to test whether proposals satisfy requirements later in the project." Such a schedule can be viewed as a design process map or an extended plan of work. Use of a schedule of this type for the structural design is reoommended.
Recommended Verbal forms to be used in the brief (from GG 101-page 4)
• The verb ’must’ indicates a statutory or legislative requirement.
• The verb ’shall’ indicates a requirement of the Overseeing Organisation.
• The verb ’should’ indicates advice expressed as a recommendation.
• The verb ’may’ indicates advice expressed as a permissible approach.
• The verb ’can’ or verbs expressed in the present tense other than ’must’, ’shall’, ’should’ and ’may’ are used to introduce notes, which provide a short clarification of a concept or statement of fact.
Options analysis Report
This reports describes an assessment of options for the structure against the requiremets and proposes a form of structure to be adopted.
Design Proposal - stage 2
This document is similar to the Approval in Principle document for bridges and to the Basis of Structural Design document recommended in the IStructE Plan of Work.
It is recommended that the Design Proposal - stage 2 includes:
1. Project description
2. Reference to documents:
- Design Brief - Stage 2
- Site Information
- Options Analysis Report
- Structural Design Brief (Stage 2)
3. Information about the proposed structure - what has been decided at the end of the Concept Stage.
4. Statements in relation to:
- The requirements that have been addressed at the end of Stage 2.
- Actions/processes needed at the Production Stage to ensure that all requirements will be properly addressed.
- Issues to be addressed that are not included in codes of practice.
Design verification report
This report demonstrates that the mandatory requirements have been satisfied and how the non-mandatory requirements have been addressed.
It records validation of the processes used and how the processes were verified.
It serves as a record of what has been done for archiving purposes.
Typical contents of a verification report:
1. Modelling
Description of the models used.
Modelling reviews: model validation, results verification
2. Code of practice calculations.
Record of calculations
Record of verification processes
3. Stability and Robustness report.
4. Sustainability Report
5. Access and Maintenance strategy
6. Cost analysis
7. Construction Methods statement