Jump to content

Framework for structural design learning: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 79: Line 79:
8.      Design verification report
8.      Design verification report
|}
|}
'''Client requirements'''


==== '''Client requirements''' ====
The client requirements that relate to the structure.
The client requirements that relate to the structure.


'''Site information'''
==== '''Site information''' ====
 
This document may include information about:  topography, existing site features, former usage, services, ground conditions, etc.
This document may include information about:  topography, existing site features, former usage, services, ground conditions, etc.


'''Structural design brief'''
==== '''Structural design brief''' ====
 
This is a collection of all requirements that may affect the structural design including information about the processes to be used. If working with the RIBA Paln of Work, it can be viewed as a sub-section of the Project Brief.
This is a collection of all requirements that may affect the structural design.


The Brief established at Stage 1 should not relate to a specific structural form.
The brief is established at Stage 1. At this stage it should, if practical, not relate to a specific structural form.


The Brief is developed at Stage 2 will relate to information from the options analysis..
The brief is developed at Stage 2 based on information from the options analysis..


Changes to the Brief should be avoided, if practical, after Stage 2.
Changes to the brief should be avoided, if practical, after Stage 2.


'''Options analysis Report'''
[https://www.designingbuildings.co.uk/wiki/Project_brief_for_design_and_construction 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.


==== '''Options analysis Report''' ====
A report on how a set of options was developed to a degree of detail sufficient to assess them against the requirements leading to a decision on the form of structure to be used.  
A report on how a set of options was developed to a degree of detail sufficient to assess them against the requirements leading to a decision on the form of structure to be used.  


'''Design Proposal for Stage 4'''
==== '''Design Proposal for Stage 4''' ====
 
This document is similar to the ''[https://www.standardsforhighways.co.uk/prod/attachments/17dadcc6-8e01-455d-b93e-c827d280839a?inline=true Approval in Principle]'' document for bridges and to the ''Basis of Structural Design'' document described for the IStructE Plan of Work.
This document is similar to the ''[https://www.standardsforhighways.co.uk/prod/attachments/17dadcc6-8e01-455d-b93e-c827d280839a?inline=true Approval in Principle]'' document for bridges and to the ''Basis of Structural Design'' document described for the IStructE Plan of Work.


Line 127: Line 125:
        Actions needed at Stage 4 to ensure that all requirements have been properly addressed.
        Actions needed at Stage 4 to ensure that all requirements have been properly addressed.


'''Design verification report'''
==== '''Design verification report''' ====
 
This report demonstrates that the mandatory requirements have been satisfied and how the non-mandatory requirements have been addressed.
This report demonstrates that the mandatory requirements have been satisfied and how the non-mandatory requirements have been addressed.