Engineer-it - User contributions [en-gb]

https://eit.engineers.scot/api.php?action=feedcontributions&feedformat=atom&user=Liam Engineer-it - User contributions [en-gb] 2026-06-13T04:57:43Z User contributions MediaWiki 1.38.4 https://eit.engineers.scot/index.php?title=Structural_design_processes&diff=1568 Structural design processes 2022-10-21T19:26:59Z

<p>Liam: </p> <hr /> <div><br /> Structural design requires the use of system planning where the overal process and the sub-processes need to be optimised. This article demonstates how system planning is applied in structural engineering design.<br /> <br /> Since every strucuture is different and innovatiion may be needed, a flexible approach to the processes is needed. <br /> <br /> Figure 1 shows how, in the creation of a structure, one starts with a set of requirements that represent the objecties and constraints forthe structure. This is transformed by a design process into design output, i.e. into information about what the structure will be and justification for the design decisions.. A construction process then transforms the design output into the physical structure. In this article, processes used in structural design are discussed<br /> [[File:Structure-process.png|none|thumb|600x600px|Figure 1 Stages in the creation of a structure]]<br /> <br /> === A basic model of the design process === <br /> [[File:Structure-process-2.png|thumb|400x400px|Figure 2 Design process stages]]<br /> Figure 2 shows a model of the design process as an instance of the [[Top-down strategy]]. The 'system model' is information about the stucture being designed and about its context.<br /> <br /> The process is not normally linear. Iterations and revisions are made based on continuous review activity,<br /> <br /> At the the InceptionStage, requirements for the performance of the stucture and for the design process are established and information about, for example, the site is identified.<br /> <br /> At the Conception Stage, investigations are carried leading to a decisoin about the general form of the structre to be adopted.<br /> <br /> At the Production Stage, the chosen form of structure is developed to produce drawings and specifications to be passed on to the construction stage. Other outcomes include documents that justify the decisions taken.<br /> <br /> === Process mapping === <br /> The Institution of Structural Egineers publishes a [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 Structural Plan of Work] that sets out an overall process for structural engineers working on the design of a building. <br /> <br /> The stages in the IStructE Plan of Work are shown in Figure 3.<br /> <br /> [[File:ISE-PlanofW-2.png|center|thumb|800x800px|Figure 3 Stages in the IStructE Plan of Work]]<br /> <br /> A process map for structural design based on the IStructE Plan of Work is shown in Table 1.<br /> [[File:Des-proc-2.png|center|thumb|800x800px|Table 1 Simplified process map for structural design]]<br /> <br /> The work starts at the top left of the map with the definition of requirements and moves across the stages and down the sub-processes to achieve the basic project outcomes In the case of stuctural design, the basic outcome is in the form of drawings and specifications that define what the structure will be. Other outcomes are required that, for example, justify the choices made or show how risk was controlled. <br /> <br /> Table 1 only indicates some of the complexity of the system plan. It does not show iterations that are common, especially at the concept stage, nor does it show interactions among the sub-processes.<br /> === Controlling Risk === <br /> Reducing risk, e.g. risks of collapse, inadequate performance, cost escalations, etc, is a fundamental strategy in engineered processes. A structural collapse can have serious consequences and all structural engineering activities should be treated as being, to some degree [[Risk#Safety-critical systems|safety critical]].<br /> <br /> Structural egineers have a duty of care to ensure that what they design will be safe to use. <br /> <br /> Naval architect, Stephen Payne, designer of the Queen Mary 2, said (at a talk given to the Institution of Engineers in Scotland in 2020). "When designing a cruise liner, the regulations represent the starting point for my safety assessment. The Titanic met the then current regulations." Hundreds of people might drown if a passenger liner was lost at sea. There are equivalent risks in structural design e.g. for a long span bridge or the roof of a sports stadium. Use of the principle that the ''starting'' point for design should be the regulations should be adopted in all strutural designs. This requires [[critical thinking]] by all participants.<br /> <br /> Structural design briefs should require that consideration should be given to the issues that are not covered by standards and that analysis models should be validated [reference needed].<br /> <br /> === Design Programme=== <br /> The work of the project is controlled by a programme where tasks are defined and allocated and timelines are established.<br /> <br /> Items in such a programme include:<br /> *Task descriptions<br /> *Task schedules.<br /> *Manpower schedules<br /> *Reviews<br /> Core actions in preparing a project programe include:<br /> *Break down the work into tasks.<br /> *Estimate the time it will take to complete each task.<br /> *Define the precedence of the tasks, i.e. decide which tasks can be carried out in parallel and which need to be handled consecutively.<br /> *Identify any lead times needed for starting the tasks - e.g. where one needs to wait for information to be delivered.<br /> *Identify critical tasks, i.e. those which if not done on time will cause delay in the overall completion<br /> *Draw up a schedule for the work, typically using a bar chart which shows when each task should start and finish. Leave some slack in the system to allow for unforeseen circumstances.<br /> * Record progress and update the task times as the work proceeds.<br /> ====Task Assignment==== <br /> When assigning a task, take account of (a) the competence of the person who is to carry out the task and (b) the need to train people to do the task.<br /> ====Reviews==== <br /> ''Regular review meetings'' should be included in the schedule to address:<br /> *Progress in relation to the programme.<br /> *Progress in relation to meeting the [https://eit.engineers.scot/index.php?title=Top-down_strategy#Requirements requirements]<br /> ''Milestone reviews'' Two major reviews in the design plan are:<br /> <br /> # At the end of the concept stage the state of the design is reviewed to ensure that what is proposed has the potential to satisfy the requirements i.e. that the design is valid. This results in a Design Proposal for agreement by the client.<br /> # The final review assessesm the outcomes against the requirements.<br /> <br /> === Review and revise ===<br /> [[Critical thinking]] is a key attribute in review work. Constantly asking reflective questions and responding to them is essential for ensuring successful outcomes. Key reflective questions are:<br /> <br /> * ''Validation'': Is the process suited to the context?<br /> * ''Verification'': Has the process been correctly implemented?<br /> <br /> === Inception Stage ===<br /> <br /> ==== Structural design brief ====<br /> This is a collection of all requirements that may affect the structural design including information about the processes to be used. At Stage 1, it should, if practical, not relate to a specific structural form so as not to limit the scope of the options to be considered. <br /> <br /> The brief starts with the client requirements and is developed at the Concept Stage based on information from the options analysis. At the end of Stage 2, a Stage 2 Design Brief should be issued and therafte changes to the brief should be avoided, if practical.<br /> <br /> 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." <br /> <br /> ==== Establishing the design brief ====<br /> To establish the requirments, design issues should be identified and expressed in the form of requirements. Figure 4 shows generic structural design issues.<br /> [[File:Issues-1.png|none|thumb|700x700px|Figure 4 Generic structural design issues]]<br /> <br /> '''Principles'''<br /> * Work to a process for establishing the brief<br /> * Ensure that all requirements have been identified and adequately stated in the brief<br /> <br /> '''Recommended verbal forms to be used in the brief''' (from [https://www.standardsforhighways.co.uk/prod/attachments/7b057727-55ee-48e5-98ff-bc3084ef807c?inline=true GG 101]-page 4)<br /> <br /> * The verb ’must’ indicates a statutory or legislative requirement.<br /> * The verb ’shall’ indicates a requirement of the Overseeing Organisation.<br /> * The verb ’should’ indicates advice expressed as a recommendation.<br /> * The verb ’may’ indicates advice expressed as a permissible approach.<br /> * 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.<br /> '''Using the design brief'''<br /> * Work to a process for ensuring that the reqirements will be satisfied<br /> <br /> * Be vigilant throughout the design process about requirements conformance<br /> * At design review meetings have requirements conformance on the agenda.<br /> *Ensure that that the mandatory requirements have been satisfied. <br /> <br /> * Explain why any non-mandatory requirements have not been fully implemented.<br /> <br /> ==== Site information ====<br /> This document may include information about: topography, existing site features, former usage, services, ground conditions, etc.<br /> <br /> === Conception Stage ===<br /> <br /> ==== Option analysis ====<br /> <br /> 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.<br /> <br /> '''Principles for the options analsis'''<br /> <br /> * At the outset, all options should be 'on the table'.<br /> * Select a set of 'candidate options' that have potential to meet the requirements<br /> * Carry out partial designs for these options to provide information adequate for assessing their relative merits.<br /> * Assess the options using [https://eit.engineers.scot/index.php?title=Critical_thinking#Proposal_testing proposal testing] principles.<br /> * Consider using a multi-criteria assessment [https://eit.engineers.scot/images/d/db/Ch2_evaluating-design-options.pdf method]<br /> <br /> ==== Design brief - Stage 2 ====<br /> The design brief should be updated taking account of the decisions made as a result of the options analysis. For example a detailed list of codes of the relevatn codes of practice should be added to the brief.<br /> <br /> ==== Design proposal - Stage 2 ====<br /> <br /> 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 recommended in the [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 IStructE Plan of Work].<br /> <br /> It is recommended that the Design Proposal - stage 2 includes:<br /> <br /> 1. A project description<br /> <br /> 2. Reference to documents:<br /> <br /> * Site Information<br /> * Options Analysis Report<br /> * Structural Design Brief (Stage 2)<br /> <br /> 3. Information about the proposed structure - what has been decided at the end of the Concept Stage (this may part of the Options Analysis Report)<br /> <br /> 4. Statements in relation to:<br /> <br /> * The requirements that have been addressed at the end of Stage 2. <br /> * Actions/processes needed at the Production Stage to ensure that all requirements will be properly addressed.<br /> * Issues to be addressed that are not included in codes of practice. This is especially important in innovative contexts. See, for example, the [[Structural design failures|Ronan Point Collapse]]<br /> <br /> === Production Stage ===<br /> <br /> ==== Technical assessment ====<br /> Technical assessment is the combined use of analysis modelling and performance criteria to seek to ensure that the structure will satisfy the technical requirements set out in the Design Brief - Stage 2. The main structural engineering standards used in the UK are the Eurocodes [[https://www.bsigroup.com/en-GB/our-services/standards-subscription-services/Eurocodes-Plus/what-are-eurocodes/ [1], [[:en:Eurocodes|2]] ]. A main requirement of technical assessment is to ensure that the strucutre will be stable i.e. that it will not be close to collapse. <br /> <br /> '''Analysis modelling'''<br /> <br /> Analysis modelling (i.e. structural analysis) is the use of mathematical models to predict structural behaviour. <br /> <br /> There is significant risk that errors in the modelling will cause the structure to be unsafe and therefore a fit for purpose [[analysis modelling process]] must be used. <br /> <br /> ==== Conformace to technical criteria ====<br /> '''Validation of technical criteria''' <br /> <br /> It is essential that all the relevant code of practice critera are addresses. It is also very important to be vigilant for issues that are not covered by codes of practice and may not have been identified in the Design Proposal - Stage 2 document.<br /> <br /> '''Performing the calculations'''<br /> <br /> Code of practice rules should be processed using software that has been subject to rigorous QA assessment.<br /> <br /> Hand calculators should only be used in preliminary work and back-of-an-envelope checks. They should not be used for final calculations because of the increased risk of errors when values are being keyed-in.<br /> <br /> '''Input checking'''<br /> <br /> A process is needed for checking that:<br /> <br /> * the input to calculations is correct,<br /> * the calculations has been correctly implemented <br /> * all criteria have been satisfied. <br /> <br /> ==== Drawings and specifications ====<br /> <br /> A process is needed to verify that the decisions made are correctly implemented in the drawings and specifications that are used to construct the structure and for other purposes.<br /> ==== Design verification report ====<br /> This report should: <br /> <br /> * demonstrate that the mandatory requirements have been satisfied and show how the non-mandatory requirements have been addressed.<br /> * record the validation of the processes used and how theys were verified.<br /> * serve as a record for archiving purposes of what has been done .<br /> <br /> Typical contents of a verification report:<br /> <br /> 1. Modelling<br /> <br /> * Description of the models used.<br /> * Modelling reviews: model validation, results verification<br /> <br /> 2. Code of practice calculations.<br /> <br /> * Record of calculations<br /> * Record of verification processes<br /> <br /> 3. Stability and Robustness report.<br /> <br /> 4. Sustainability Report<br /> <br /> 5. Access and Maintenance strategy<br /> <br /> 6. Cost analysis<br /> <br /> 7. Construction Methods statement<br /> *</div>

Liam https://eit.engineers.scot/index.php?title=Structural_design_processes&diff=1567 Structural design processes 2022-10-21T19:25:47Z

<p>Liam: </p> <hr /> <div><br /> Structural design requires the use of system planning where the overal process and the sub-processes need to be optimised. This article demonstates how system planning is applied in structural engineering design.<br /> <br /> Since every strucuture is different and innovatiion may be needed, a flexible approach to the processes is needed. <br /> <br /> Figure 1 shows how, in the creation of a structure, one starts with a set of requirements that represent the objecties and constraints forthe structure. This is transformed by a design process into design output, i.e. into information about what the structure will be and justification for the design decisions.. A construction process then transforms the design output into the physical structure. In this article, processes used in structural design are discussed<br /> [[File:Structure-process.png|none|thumb|600x600px|Figure 1 Stages in the creation of a structure]]<br /> <br /> === A basic model of the design process === <br /> [[File:Structure-process-2.png|thumb|400x400px|Figure 2 Design process stages]]<br /> Figure 2 shows a model of the design process as an instance of the [[Top-down strategy]]. The 'system model' is information about the stucture being designed and about its context.<br /> <br /> The process is not normally linear. Iterations and revisions are made based on continuous review activity,<br /> <br /> At the the InceptionStage, requirements for the performance of the stucture and for the design process are established and information about, for example, the site is identified.<br /> <br /> At the Conception Stage, investigations are carried leading to a decisoin about the general form of the structre to be adopted.<br /> <br /> At the Production Stage, the chosen form of structure is developed to produce drawings and specifications to be passed on to the construction stage. Other outcomes include documents that justify the decisions taken.<br /> <br /> === Process mapping ===<br /> The Institution of Structural Egineers publishes a [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 Structural Plan of Work] that sets out an overall process for structural engineers working on the design of a building. <br /> <br /> The stages in the IStructE Plan of Work are shown in Figure 3.<br /> <br /> [[File:ISE-PlanofW-2.png|center|thumb|800x800px|Figure 3 Stages in the IStructE Plan of Work]]<br /> <br /> A process map for structural design based on the IStructE Plan of Work is shown in Table 1.<br /> [[File:Des-proc-2.png|center|thumb|800x800px|Table 1 Simplified process map for structural design]]<br /> <br /> The work starts at the top left of the map with the definition of requirements and moves across the stages and down the sub-processes to achieve the basic project outcomes In the case of stuctural design, the basic outcome is in the form of drawings and specifications that define what the structure will be. Other outcomes are required that, for example, justify the choices made or show how risk was controlled. <br /> <br /> Table 1 only indicates some of the complexity of the system plan. It does not show iterations that are common, especially at the concept stage, nor does it show interactions among the sub-processes.<br /> === Controlling Risk ===<br /> Reducing risk, e.g. risks of collapse, inadequate performance, cost escalations, etc, is a fundamental strategy in engineered processes. A structural collapse can have serious consequences and all structural engineering activities should be treated as being, to some degree [[Risk#Safety-critical systems|safety critical]].<br /> <br /> Structural egineers have a duty of care to ensure that what they design will be safe to use. <br /> <br /> Naval architect, Stephen Payne, designer of the Queen Mary 2, said (at a talk given to the Institution of Engineers in Scotland in 2020). "When designing a cruise liner, the regulations represent the starting point for my safety assessment. The Titanic met the then current regulations." Hundreds of people might drown if a passenger liner was lost at sea. There are equivalent risks in structural design e.g. for a long span bridge or the roof of a sports stadium. Use of the principle that the ''starting'' point for design should be the regulations should be adopted in all strutural designs. This requires [[critical thinking]] by all participants.<br /> <br /> Structural design briefs should require that consideration should be given to the issues that are not covered by standards and that analysis models should be validated [reference needed].<br /> <br /> === Design Programme===<br /> The work of the project is controlled by a programme where tasks are defined and allocated and timelines are established.<br /> <br /> Items in such a programme include:<br /> *Task descriptions<br /> *Task schedules.<br /> *Manpower schedules<br /> *Reviews<br /> Core actions in preparing a project programe include:<br /> *Break down the work into tasks.<br /> *Estimate the time it will take to complete each task.<br /> *Define the precedence of the tasks, i.e. decide which tasks can be carried out in parallel and which need to be handled consecutively.<br /> *Identify any lead times needed for starting the tasks - e.g. where one needs to wait for information to be delivered.<br /> *Identify critical tasks, i.e. those which if not done on time will cause delay in the overall completion<br /> *Draw up a schedule for the work, typically using a bar chart which shows when each task should start and finish. Leave some slack in the system to allow for unforeseen circumstances.<br /> * Record progress and update the task times as the work proceeds.<br /> ====Task Assignment====<br /> When assigning a task, take account of (a) the competence of the person who is to carry out the task and (b) the need to train people to do the task.<br /> ====Reviews====<br /> ''Regular review meetings'' should be included in the schedule to address:<br /> *Progress in relation to the programme.<br /> *Progress in relation to meeting the [https://eit.engineers.scot/index.php?title=Top-down_strategy#Requirements requirements]<br /> ''Milestone reviews'' Two major reviews in the design plan are:<br /> <br /> # At the end of the concept stage the state of the design is reviewed to ensure that what is proposed has the potential to satisfy the requirements i.e. that the design is valid. This results in a Design Proposal for agreement by the client.<br /> # The final review assessesm the outcomes against the requirements.<br /> <br /> === Review and revise ===<br /> [[Critical thinking]] is a key attribute in review work. Constantly asking reflective questions and responding to them is essential for ensuring successful outcomes. Key reflective questions are:<br /> <br /> * ''Validation'': Is the process suited to the context?<br /> * ''Verification'': Has the process been correctly implemented?<br /> <br /> === Inception Stage ===<br /> <br /> ==== Structural design brief ====<br /> This is a collection of all requirements that may affect the structural design including information about the processes to be used. At Stage 1, it should, if practical, not relate to a specific structural form so as not to limit the scope of the options to be considered. <br /> <br /> The brief starts with the client requirements and is developed at the Concept Stage based on information from the options analysis. At the end of Stage 2, a Stage 2 Design Brief should be issued and therafte changes to the brief should be avoided, if practical.<br /> <br /> 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." <br /> <br /> ==== Establishing the design brief ====<br /> To establish the requirments, design issues should be identified and expressed in the form of requirements. Figure 4 shows generic structural design issues.<br /> [[File:Issues-1.png|none|thumb|700x700px|Figure 4 Generic structural design issues]]<br /> <br /> '''Principles'''<br /> * Work to a process for establishing the brief<br /> * Ensure that all requirements have been identified and adequately stated in the brief<br /> <br /> '''Recommended verbal forms to be used in the brief''' (from [https://www.standardsforhighways.co.uk/prod/attachments/7b057727-55ee-48e5-98ff-bc3084ef807c?inline=true GG 101]-page 4)<br /> <br /> * The verb ’must’ indicates a statutory or legislative requirement.<br /> * The verb ’shall’ indicates a requirement of the Overseeing Organisation.<br /> * The verb ’should’ indicates advice expressed as a recommendation.<br /> * The verb ’may’ indicates advice expressed as a permissible approach.<br /> * 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.<br /> '''Using the design brief'''<br /> * Work to a process for ensuring that the reqirements will be satisfied<br /> <br /> * Be vigilant throughout the design process about requirements conformance<br /> * At design review meetings have requirements conformance on the agenda.<br /> *Ensure that that the mandatory requirements have been satisfied. <br /> <br /> * Explain why any non-mandatory requirements have not been fully implemented.<br /> <br /> ==== Site information ====<br /> This document may include information about: topography, existing site features, former usage, services, ground conditions, etc.<br /> <br /> === Conception Stage ===<br /> <br /> ==== Option analysis ====<br /> <br /> 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.<br /> <br /> '''Principles for the options analsis'''<br /> <br /> * At the outset, all options should be 'on the table'.<br /> * Select a set of 'candidate options' that have potential to meet the requirements<br /> * Carry out partial designs for these options to provide information adequate for assessing their relative merits.<br /> * Assess the options using [https://eit.engineers.scot/index.php?title=Critical_thinking#Proposal_testing proposal testing] principles.<br /> * Consider using a multi-criteria assessment [https://eit.engineers.scot/images/d/db/Ch2_evaluating-design-options.pdf method]<br /> <br /> ==== Design brief - Stage 2 ====<br /> The design brief should be updated taking account of the decisions made as a result of the options analysis. For example a detailed list of codes of the relevatn codes of practice should be added to the brief.<br /> <br /> ==== Design proposal - Stage 2 ====<br /> <br /> 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 recommended in the [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 IStructE Plan of Work].<br /> <br /> It is recommended that the Design Proposal - stage 2 includes:<br /> <br /> 1. A project description<br /> <br /> 2. Reference to documents:<br /> <br /> * Site Information<br /> * Options Analysis Report<br /> * Structural Design Brief (Stage 2)<br /> <br /> 3. Information about the proposed structure - what has been decided at the end of the Concept Stage (this may part of the Options Analysis Report)<br /> <br /> 4. Statements in relation to:<br /> <br /> * The requirements that have been addressed at the end of Stage 2. <br /> * Actions/processes needed at the Production Stage to ensure that all requirements will be properly addressed.<br /> * Issues to be addressed that are not included in codes of practice. This is especially important in innovative contexts. See, for example, the [[Structural design failures|Ronan Point Collapse]]<br /> <br /> === Production Stage ===<br /> <br /> ==== Technical assessment ====<br /> Technical assessment is the combined use of analysis modelling and performance criteria to seek to ensure that the structure will satisfy the technical requirements set out in the Design Brief - Stage 2. The main structural engineering standards used in the UK are the Eurocodes [[https://www.bsigroup.com/en-GB/our-services/standards-subscription-services/Eurocodes-Plus/what-are-eurocodes/ [1], [[:en:Eurocodes|2]] ]. A main requirement of technical assessment is to ensure that the strucutre will be stable i.e. that it will not be close to collapse. <br /> <br /> '''Analysis modelling'''<br /> <br /> Analysis modelling (i.e. structural analysis) is the use of mathematical models to predict structural behaviour. <br /> <br /> There is significant risk that errors in the modelling will cause the structure to be unsafe and therefore a fit for purpose [[analysis modelling process]] must be used. <br /> <br /> ==== Conformace to technical criteria ====<br /> '''Validation of technical criteria''' <br /> <br /> It is essential that all the relevant code of practice critera are addresses. It is also very important to be vigilant for issues that are not covered by codes of practice and may not have been identified in the Design Proposal - Stage 2 document.<br /> <br /> '''Performing the calculations'''<br /> <br /> Code of practice rules should be processed using software that has been subject to rigorous QA assessment.<br /> <br /> Hand calculators should only be used in preliminary work and back-of-an-envelope checks. They should not be used for final calculations because of the increased risk of errors when values are being keyed-in.<br /> <br /> '''Input checking'''<br /> <br /> A process is needed for checking that:<br /> <br /> * the input to calculations is correct,<br /> * the calculations has been correctly implemented <br /> * all criteria have been satisfied. <br /> <br /> ==== Drawings and specifications ====<br /> <br /> A process is needed to verify that the decisions made are correctly implemented in the drawings and specifications that are used to construct the structure and for other purposes.<br /> ==== Design verification report ====<br /> This report should: <br /> <br /> * demonstrate that the mandatory requirements have been satisfied and show how the non-mandatory requirements have been addressed.<br /> * record the validation of the processes used and how theys were verified.<br /> * serve as a record for archiving purposes of what has been done .<br /> <br /> Typical contents of a verification report:<br /> <br /> 1. Modelling<br /> <br /> * Description of the models used.<br /> * Modelling reviews: model validation, results verification<br /> <br /> 2. Code of practice calculations.<br /> <br /> * Record of calculations<br /> * Record of verification processes<br /> <br /> 3. Stability and Robustness report.<br /> <br /> 4. Sustainability Report<br /> <br /> 5. Access and Maintenance strategy<br /> <br /> 6. Cost analysis<br /> <br /> 7. Construction Methods statement<br /> *</div>

Liam https://eit.engineers.scot/index.php?title=Structural_engineering&diff=1566 Structural engineering 2022-10-21T18:22:31Z

<p>Liam: </p> <hr /> <div>[[File:Building-construction.png|center|thumb|850x850px]] <br /> <br /> {| class="wikitable"<br /> |+<br /> |[[Main Page|Engineer-it main page]]<br /> |}<br /> <br /> <br /> The Sructural Engineering module is for learners in structural engineering at all stages of education and career. <br /> <br /> ===<big>Case studies</big>===<br /> {| class="wikitable" <br /> <br /> |- style="vertical-align:top;"<br /> ! style=" width:200px; text-align:left;" |<big>Design cases</big><br /> ! style=" width:200px; text-align:left;" |<big>Performace cases</big><br /> <br /> |- style="vertical-align:top;"<br /> |[[Structural design of a footbridge|Footbridge]]<br /> <br /> |'''[[Structural design failures|Failures]]'''<br /> <br /> '''Successes'''<br /> <br /> [https://engineers.scot/office/resources/publications/ies-journal-2018-qfbridge.pdf Queensferry Bridge]<br /> <br /> |}<br /> <br /> ===<big>Design Guidance</big>===<br /> {| class="wikitable" <br /> <br /> |- style="vertical-align:top;"<br /> | style=" width:200px; text-align:left;" |[[Structural design processes]]<br /> [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 IStructE plan of work]<br /> <br /> [http://stempedia.com/wp-content/uploads/Eurocode-guidance.doc Use of codes of practice]<br /> <br /> [[Integrity]]<br /> <br /> | style=" width:200px; text-align:left;" |[https://eit.engineers.scot/images/5/57/Modelling-proces.pd Modellling process]<br /> [http://stempedia.com/wp-content/uploads/Eit-guidance-stabilityIM-1.pdf Stability]<br /> <br /> [https://eit.engineers.scot/images/d/db/Ch2_evaluating-design-options.pdf Option evaluation]<br /> <br /> Sustainability:<br /> <br /> [https://www.steelconstruction.info/Sustainability#Recycling_and_reuse Steel construction]<br /> <br /> |}<br /> <br /> ===<big>Structural data</big>===<br /> {| class="wikitable"<br /> |[https://www.academia.edu/31442448/Cobb_Fiona_Structural_Engineers_Pocket_Book_Book_ZZ_org Structural Engineers Pocket Book] by Fiona Cobb<br /> [https://www.steelforlifebluebook.co.uk/ Steel Sections Tables] (the Blue Book)<br /> |}<br /> <br /> ===<big>Dictionary of structural engineering</big>===<br /> {| class="wikitable"<br /> |[[Dictionary Structural engineering|Dictionary structural engineering]]<br /> |}<br /> <br /> ===<big>Structural mechanics</big>===<br /> An information resource for structural mechanics was developed as [http://stempedia.com/test/about-the-resource/ Stempedia] The Stempedia files are being converted to Mediawiki format.<br /> {| class="wikitable"<br /> |[[Framework for structural mechanics learning]]<br /> [[Structural Analysis:|Structural analysis]]<br /> <br /> [[Strength and Stiffness of Materials|Strength and stiffness of materials]]<br /> |}</div>

Liam https://eit.engineers.scot/index.php?title=Structural_engineering&diff=1565 Structural engineering 2022-10-21T18:22:19Z

<p>Liam: </p> <hr /> <div>[[File:Building-construction.png|center|thumb|850x850px]] <br /> <br /> {| class="wikitable"<br /> |+<br /> |[[Main Page|Engineer-it main page]]<br /> |}<br /> <br /> <br /> The Sructural Engineering module is for learners in structural engineering at all stages of education and career. <br /> <br /> __TOC__<br /> <br /> ===<big>Case studies</big>===<br /> {| class="wikitable" <br /> <br /> |- style="vertical-align:top;"<br /> ! style=" width:200px; text-align:left;" |<big>Design cases</big><br /> ! style=" width:200px; text-align:left;" |<big>Performace cases</big><br /> <br /> |- style="vertical-align:top;"<br /> |[[Structural design of a footbridge|Footbridge]]<br /> <br /> |'''[[Structural design failures|Failures]]'''<br /> <br /> '''Successes'''<br /> <br /> [https://engineers.scot/office/resources/publications/ies-journal-2018-qfbridge.pdf Queensferry Bridge]<br /> <br /> |}<br /> <br /> ===<big>Design Guidance</big>===<br /> {| class="wikitable" <br /> <br /> |- style="vertical-align:top;"<br /> | style=" width:200px; text-align:left;" |[[Structural design processes]]<br /> [https://www.istructe.org/sitefiles/handlers/DownloadFile.ashx?productId=9746 IStructE plan of work]<br /> <br /> [http://stempedia.com/wp-content/uploads/Eurocode-guidance.doc Use of codes of practice]<br /> <br /> [[Integrity]]<br /> <br /> | style=" width:200px; text-align:left;" |[https://eit.engineers.scot/images/5/57/Modelling-proces.pd Modellling process]<br /> [http://stempedia.com/wp-content/uploads/Eit-guidance-stabilityIM-1.pdf Stability]<br /> <br /> [https://eit.engineers.scot/images/d/db/Ch2_evaluating-design-options.pdf Option evaluation]<br /> <br /> Sustainability:<br /> <br /> [https://www.steelconstruction.info/Sustainability#Recycling_and_reuse Steel construction]<br /> <br /> |}<br /> <br /> ===<big>Structural data</big>===<br /> {| class="wikitable"<br /> |[https://www.academia.edu/31442448/Cobb_Fiona_Structural_Engineers_Pocket_Book_Book_ZZ_org Structural Engineers Pocket Book] by Fiona Cobb<br /> [https://www.steelforlifebluebook.co.uk/ Steel Sections Tables] (the Blue Book)<br /> |}<br /> <br /> ===<big>Dictionary of structural engineering</big>===<br /> {| class="wikitable"<br /> |[[Dictionary Structural engineering|Dictionary structural engineering]]<br /> |}<br /> <br /> ===<big>Structural mechanics</big>===<br /> An information resource for structural mechanics was developed as [http://stempedia.com/test/about-the-resource/ Stempedia] The Stempedia files are being converted to Mediawiki format.<br /> {| class="wikitable"<br /> |[[Framework for structural mechanics learning]]<br /> [[Structural Analysis:|Structural analysis]]<br /> <br /> [[Strength and Stiffness of Materials|Strength and stiffness of materials]]<br /> |}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=1564 MediaWiki:Mobile.js 2022-10-09T18:36:01Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>Modules</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Strategies_for_system_planning" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for System Planning</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Energy_planning" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Energy Planning</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=1562 MediaWiki:Mobile.js 2022-10-08T18:13:14Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>View Chapters</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Energy_planning" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Energy Planning</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=1561 MediaWiki:Mobile.js 2022-10-08T18:11:54Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>View Chapters</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Energy_planning" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Energy Planning</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> // $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> // $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=User:Liam&diff=1167 User:Liam 2021-10-29T18:03:57Z

<p>Liam: </p> <hr /> <div>My name is Liam Guermache. I'm a second year Civil Engineering student at the University of Glasgow and helping develop Engineer-it.</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=1166 MediaWiki:Vector.css 2021-10-29T14:57:58Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Modules-label {font-weight: bold; font-size: 1em}<br /> #p-Modules {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=1101 MediaWiki:Sidebar 2021-10-02T09:32:02Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Categories<br /> ** Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Global Issues|Global Issues<br /> ** mainpage|Second Link to Main Page<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=Chapter_1:Strategies_for_engineered_outcomes&diff=1100 Chapter 1:Strategies for engineered outcomes 2021-10-02T09:29:23Z

<p>Liam: Liam moved page Chapter 1:Strategies for engineered outcomes to Strategies for engineered outcomes over redirect</p> <hr /> <div>#REDIRECT [[Strategies for engineered outcomes]]</div>

Liam https://eit.engineers.scot/index.php?title=Strategies_for_system_planning&diff=1099 Strategies for system planning 2021-10-02T09:29:22Z

<p>Liam: Liam moved page Chapter 1:Strategies for engineered outcomes to Strategies for engineered outcomes over redirect</p> <hr /> <div>'''An ''Engineer-it'' chapter managed by the Institution of Engineers in Scotland '''([http://www.engineers.scot/ www.engineers.scot])<br /> <br /> {| class="wikitable" style=" margin-right: 30px; background-color:#DEF6FE; paddng-left:15px; width:200px; vertical-align:top; text-align:left; float:left; margin-left: 10px;"<br /> |- <br /> |'''<big>Strategies</big>'''<br /> [[Critical thinking]]<br /> <br /> [[Top-down strategy]]<br /> <br /> [[Risk]] <br /> <br /> [[Leadership]]<br /> <br /> [[Planning]]<br /> <br /> [[Quantify]]<br /> <br /> [[Governance]]<br /> <br /> [[Integrity]]<br /> |-<br /> |'''Papers'''<br /> <br /> [http://www.iesis.org/toengineer/To-Engineer.pdf To Engineer]<br /> |- <br /> |'''Case Studies'''<br /> <br /> [https://engineers.scot/news/2021-04-08-opinion-the-government-must-use-engineered-processes-in-its-response-to-the-pandemic The UK Covid-19 Task Force] A successful government project <br> <br /> <br /> [http://info.iesis.org/papers/Journal+V156_web_secure.pdf The development of an optical scanner] (p22) How to develop an innovative product<br /> |}<br /> <br /> [[File:Engprocess-6.png|alt=|thumb|500x500px|Figure 1 Features of an 'engineered' process]] <br /> An engineered outcome results from the use of a range of control strategies that are appropriate in situations of complex uncertainty. The strategies used have universal application in complex problem solving. It is not only engineers who use them: Scientists 'engineer' the development of a drug; professional engineers will engineer the design and development of an aircraft. Businesses are 'engineered' (or 're-engineered'). <br /> <br /> The strategies form the basis of a 'engineered process' that is used to control the risk of unsatisfactory outcomes.<br /> <br /> Figure 1 shows some features of an engineered process.<br /> <br /> Key issues are ''competence'', i.e. the skills of those inolved and ''[[governance]]'', i.e. how responsibility, authority and accountabiliy are allocated.<br /> <br /> Competence is shown as having two main components:<br /> <br /> * Disciplinary expertise i.e. the abilities of those involved to carry out specific tasks. It is common to require expertise from several disciplines<br /> * Ethos - the principles that guide the actions of the participants.<br /> <br /> Whereas 'what you know' might be described in term of disciplinary expertise, ethos is 'how you think'. <br /> <br /> [[Critical thinking]] may be the most important feature of an engineered process. Critical thinkers identify and use guiding principles that lead to engineered outcomes.<br /> <br /> Deep collaboration within the project team with unswerving commitment to the project goals are also key features of an engineered process.<br /> <br /> Closely related to commitment is the requirement that the process is underpinned by the highest levels of professional integrity.<br /> <br /> All this needs to be inspired by democratic [[leadership]].<br /> <br /> === Learning to use engineered processes ===<br /> See [[Index.php?title=Critical thinking#Learning%20for%20critical%20thinking|Learning for critical thinking]]</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=1098 MediaWiki:Vector.css 2021-10-02T09:24:09Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Categories-label {font-weight: bold; font-size: 1em}<br /> #p-Categories {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=1097 MediaWiki:Sidebar 2021-10-02T09:22:09Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Categories<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes Test Change<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Global Issues|Global Issues<br /> ** mainpage|Second Link to Main Page<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=1096 MediaWiki:Sidebar 2021-10-02T09:20:58Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes Test Change<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Global Issues|Global Issues<br /> ** mainpage|Second Link to Main Page<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=1095 MediaWiki:Sidebar 2021-10-02T09:20:05Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes Test Change<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Global Issues|Global Issues<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=895 MediaWiki:Mobile.js 2021-07-19T17:02:46Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>View Chapters</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_3:Global_Issues" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Global Issues</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Common.css&diff=718 MediaWiki:Common.css 2021-06-26T21:22:48Z

<p>Liam: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> .mw-editsection { display:none!important; }<br /> <br /> * Infobox template style */<br /> .infobox {<br /> border: 1px solid #a2a9b1;<br /> border-spacing: 3px;<br /> background-color: #f8f9fa;<br /> color: black;<br /> /* @noflip */<br /> margin: 0.5em 0 0.5em 1em;<br /> padding: 0.2em;<br /> /* @noflip */<br /> float: right;<br /> /* @noflip */<br /> clear: right;<br /> font-size: 88%;<br /> line-height: 1.5em;<br /> width: 22em;<br /> }<br /> <br /> /* not strictly certain these styles are necessary<br /> * just replicating the module faithfully<br /> */<br /> .infobox-subbox {<br /> padding: 0;<br /> border: none;<br /> margin: -3px;<br /> width: auto;<br /> min-width: 100%;<br /> font-size: 100%;<br /> clear: none;<br /> float: none;<br /> background-color: transparent;<br /> }</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Common.css&diff=717 MediaWiki:Common.css 2021-06-26T21:20:46Z

<p>Liam: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> .mw-editsection { display:none!important; }<br /> <br /> /* infobox css */<br /> <br /> .infobox {<br /> font-family: sans-serif;<br /> direction: ltr;<br /> border: 1px solid #a2a9b1;<br /> border-spacing: 3px;<br /> background-color: #f8f9fa;<br /> color: black;<br /> margin: 0.5em 0 0.5em 1em;<br /> padding: 0.2em;<br /> float: right;<br /> clear: right;<br /> font-size: 88%;<br /> line-height: 1.5em;<br /> width: 22em;<br /> }</div>

Liam https://eit.engineers.scot/index.php?title=Template:Infobox_Test&diff=716 Template:Infobox Test 2021-06-26T21:18:41Z

<p>Liam: </p> <hr /> <div><table class="infobox"><tbody><tr><th colspan="2" class="infobox-above" style="background-color: #ddbbee">{{{Name}}}</th></tr><tr><td colspan="2" class="infobox-subheader"><i><a href="/wiki/Drug_class" title="">Drug class</a></i></td></tr><tr><td colspan="2" class="infobox-image">[[File:{{{Image}}}|frameless|alt={{{Alt}}}|upright=1.25|{{{Alt}}}]]<div class="infobox-caption">{{{Caption}}}</div></td></tr><tr><th scope="row" class="infobox-label">Pronunciation</th><td class="infobox-data">{{{Pronounce}}} </td></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/Synonym" title="Synonym">Synonyms</a></th><td class="infobox-data">{{{Synonyms}}}<br /> --&gt;</td></tr><tr><th colspan="2" class="infobox-header" style="background: #e8e8e8;">Clinical data</th></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/Drugs.com" title="Drugs.com">Drugs.com</a></th><td class="infobox-data">{{{Drugs.com}}}</td></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/Consumer_Reports" title="Consumer Reports">Consumer Reports</a></th><td class="infobox-data"><span class="reflink plainlinks nourlexpansion"><a rel="nofollow" class="external text" href="http://www.consumerreports.org/health/best-buy-drugs/{{{Consumer_Reports}}}.htm">Best Buy Drugs</a></span></td></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/WebMD" title="WebMD">WebMD</a></th><td class="infobox-data"><span class="reflink plainlinks nourlexpansion"><a rel="nofollow" class="external text" href="http://www.medicinenet.com/{{{medicinenet}}}/article.htm">MedicineNet</a></span>&nbsp; <span class="reflink plainlinks nourlexpansion"><a rel="nofollow" class="external text" href="http://www.rxlist.com/script/main/art.asp?articlekey={{{rxlist}}}">RxList</a></span></td></tr><tr><th colspan="2" class="infobox-header" style="background: #e8e8e8;">External links</th></tr><tr><th scope="row" class="infobox-label"><a href="/wiki/Medical_Subject_Headings" title="Medical Subject Headings">MeSH</a></th><td class="infobox-data"><span class="reflink plainlinks nourlexpansion"><a rel="nofollow" class="external text" href="https://www.nlm.nih.gov/cgi/mesh/2011/MB_cgi?field=uid&amp;term={{{MeshID}}}--">&gt; {{{MeshID}}}--&gt;</a></span></td></tr><tr><td colspan="2" class="infobox-below" style="background: #e8e8e8; text-align: center"><a href="https://www.wikidata.org/wiki/Q8143283" class="extiw" title="d:Q8143283">In Wikidata</a></td></tr></tbody></table></div>

Liam https://eit.engineers.scot/index.php?title=Template:Infobox_Test&diff=715 Template:Infobox Test 2021-06-26T21:15:50Z

<p>Liam: Created page with "{{infobox | abovestyle = background-color: {{#if:{{{Background|}}}|{{{Background|}}} |#ddbbee }} | above = {{#if:{{{Name|}}} |{{{Name|}}} |{{PAGENAME}}}} | subheader =..."</p> <hr /> <div>{{infobox<br /> | abovestyle = background-color: {{#if:{{{Background|}}}|{{{Background|}}} |#ddbbee }}<br /> | above = {{#if:{{{Name|}}} |{{{Name|}}} |{{PAGENAME}}}}<br /> <br /> | subheader = ''[[Drug class]]''<br /> | image = {{#invoke:InfoboxImage|InfoboxImage|image={{{Image|}}}|size={{{Width|}}}|sizedefault=frameless|upright=1.25|alt={{{Alt|}}}}}<br /> | caption = {{{Caption|}}}<br /> <br /> | headerstyle = background: #e8e8e8;<br /> | header1 = {{#if:{{{Use|}}}{{{ATC_prefix|}}}{{{Biological_target|}}}{{{Target_mechanism|}}}{{{Chemical_class|}}}|Class identifiers}}<br /> <br /> | label2 = Pronunciation<br /> | data2 = {{#if:{{{pronounce|{{{Pronounce|{{{Pronunciation|{{{pronunciation|}}}}}}}}}}}}{{{pronounce comment|}}} |{{{pronounce|{{{Pronounce|{{{Pronunciation|{{{pronunciation|}}}}}}}}}}}}{{{pronounce ref|}}}&#x20;{{{pronounce comment|}}} }}{{#if:{{{pronounce 2|}}} |<br/>{{{pronounce 2|}}} }}<br /> <br /> | label3 = [[Synonym]]s<br /> | data3 = {{{Synonym|{{{synonym|{{{Synonyms|{{{synonyms|}}}}}}}}}}}}<br /> <br /> | label4 = Use<br /> | data4 = {{{Use|}}}<br /> <br /> | label5 = [[Anatomical Therapeutic Chemical Classification System|ATC code]]<br /> | data5 = {{#if:{{{ATC_prefix|}}}|[[ATC_code_{{{ATC_prefix}}}|{{{ATC_prefix}}}]] }}<br /> <br /> | label6 = [[Mode of action]]<br /> | data6 = {{{Mode_of_action|}}}<br /> <br /> | label7 = [[Mechanism of action]]<br /> | data7 = {{{Mechanism_of_action|}}}<br /> <br /> | label8 = [[Biological target]]<br /> | data8 = {{{Biological_target|}}}<br /> <br /> | label9 = [[Chemical classification|Chemical class]] <br /> | data9 = {{{Chemical_class|}}}<br /> <br /> | header10 = {{#if:{{{Drugs.com|}}}{{{Consumer_Reports|}}}{{{medicinenet|}}}{{{rxlist|}}}|Clinical data}}<br /> <br /> | label11 = [[Drugs.com]]<br /> | data11 = {{{Drugs.com|}}}<br /> <br /> | label12 = [[Consumer Reports]]<br /> | data12 = {{#if:{{{Consumer_Reports|}}}|<span class="reflink plainlinks nourlexpansion">[http://www.consumerreports.org/health/best-buy-drugs/{{{Consumer_Reports}}}.htm Best Buy Drugs]</span>}}<br /> <br /> | label13 = [[WebMD]]<br /> | data13 = {{#if:{{{medicinenet|}}}|<span class="reflink plainlinks nourlexpansion">[http://www.medicinenet.com/{{{medicinenet}}}/article.htm MedicineNet]</span>&nbsp;}} {{#if:{{{rxlist|}}}|<span class="reflink plainlinks nourlexpansion">[http://www.rxlist.com/script/main/art.asp?articlekey={{{rxlist}}} RxList]</span>}}<br /> <br /> | header14 = {{#if:{{{MeshID|}}}|External links}}<br /> <br /> | label15 = [[Medical Subject Headings|MeSH]]<br /> | data15 = {{#if:{{{MeshID|}}}|<span class="reflink plainlinks nourlexpansion">[https://www.nlm.nih.gov/cgi/mesh/{{{MeshYear|2011}}}/MB_cgi?field=uid&term={{{MeshID|}}} {{{MeshID}}}]</span>}}<br /> <br /> |belowstyle = background: #e8e8e8; text-align: center<br /> |below = {{#if:{{wikidata|label|raw}} |[[d:{{wikidata|label|raw}} |In Wikidata]]}}<br /> }}<noinclude>{{Documentation}}</noinclude></div>

Liam https://eit.engineers.scot/index.php?title=Main_Page&diff=714 Main Page 2021-06-26T21:15:26Z

<p>Liam: </p> <hr /> <div>[[File:Bridges.png|alt=|center|800x800px]]<br /> <br /> == Welcome to Engineer-it ==<br /> <br /> {| class="wikitable" style="margin-left: auto; margin-right: 0px; background-color:#DEF6FE; width:200px; vertical-align:top; text-align:left; float:right; margin-left: 10px;"<br /> !<big>References</big><br /> |-<br /> |'''Chapters'''<br /> '''[[Chapter 1:Strategies for engineered outcomes|Strategies]]'''<br /> <br /> '''[[Chapter 2:Structural engineering|Structural engineering]]'''<br /> <br /> |- style="height:300px;vertical-align:top; " |-<br /> |'''About'''<br /> [[About Engineer-it|About]] Engineer-it<br /> |}<br /> '''Note:''' This resource is under development (May 2021). It has not yet been launched. Please do not make a link to it from another website. <br /> <br /> The ''Engineer-it'' resource, for learners of all ages, provides information about how to 'engineer' successful outcomes particularly in situations of complex uncertanty. 'Engineering' is viewed as an overarching strategy widely used beyond engineering. <br /> <br /> The resource was established in 2021 by the Institution of Engineers in Scotland ([http://www.engineers.scot/ IES]). <br /> <br /> While Engineer-it relates closely to STEM learning (Science, Technology, Engineering and Mathematics) it is not confined to these subject areas. <br /> <br /> Engineer-it is uses the MediaWiki software platform but it is not 'wiki' i.e. there are limited editing rights. However, it is a 'live' resource that is expected to be continually extended and modified. <br /> <br /> For more information about Engineer-it see [[Engineer-it:About|About]]<br /> <br /> <br /> Testing infobox [[Template:Infobox Test]] <br /> <br /> ===Structure of the resource===<br /> The resource is divided into 'chapters'. <br /> <br /> There is no fixed process for 'engineering' a problem but there is a range of strategies that are adopted by people to achieve success in situations of complex uncertainty. For example, those who seek to address the complex problems of the modern world - sustainability, inequality, energy, climate change, waste, etc. - must use these strategies where they are appropriate. All who have, or aspire to have, a responsible role in society should discipline their minds to use them.<br /> <br /> The [[Strategies for engineered outcomes|Strategies Chapter]] outlines a conceptual framework that can be used in a wide range of situations, not only in engineering. The other chapters give instances of the use of the framework in specific contexts.<br /> <br /> At present (May 2021) one other chapter - [[Chapter 2:Structural engineering|Structural Engineering]] - is under development<br /> <br /> === Learning strategies ===<br /> When learning,to use technical methods, some people like start with examples and work from there to theory and basic principles. Others like to do it the other way around. A main principle behind Engineer-it is that information is provided that can satisfy both of these strategies.<br /> {| class="wikitable"<br /> |'''Instances Conceptual information'''<br /> |-<br /> |Other chapters Strategies chapter<br /> |-<br /> |''' Applications Examples Explanations Theory Basic principles'''<br /> |}<br /> The table above shows a spectrum of types of document from full applications on the left to mainly conceptual information on the right.</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=713 MediaWiki:Sidebar 2021-06-26T20:40:59Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Global Issues|Global Issues<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=712 MediaWiki:Sidebar 2021-06-25T17:47:34Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3 Name Change:Global Issues|Global Issues<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=Energy_planning&diff=710 Energy planning 2021-06-25T17:46:37Z

<p>Liam: Liam moved page Chapter 3 Name Change:Hello to Chapter 3 Name Change:Global Issues: rename</p> <hr /> <div><br /> {{NAMESPACE}}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=661 MediaWiki:Sidebar 2021-06-07T19:44:21Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3 Name Change:Hello|Global Issues<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=660 MediaWiki:Sidebar 2021-06-07T19:42:11Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Hello|Global Issues<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=615 MediaWiki:Mobile.js 2021-05-21T07:20:39Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>View Chapters</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_3:Hello" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Hello from Chapter 3</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=614 MediaWiki:Mobile.js 2021-05-21T07:18:42Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-minerva-watchlist"> \<br /> <span>View Chapters</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_3:Hello" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Hello from Chapter 3</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=613 MediaWiki:Mobile.js 2021-05-21T07:17:27Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-minerva-watchlist"> \<br /> <span>Dropdown Links</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_3:Hello" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Hello from Chapter 3</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> '<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=612 MediaWiki:Mobile.js 2021-05-21T07:16:36Z

<p>Liam: </p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-mf-expand mw-ui-icon-small"> \<br /> <span>Dropdown Links</span> \<br /> </a> \<br /> </li> \<br /> <ul class="level2"> \<br /> <li> \<br /> <a href="/wiki/Link_1" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-minerva-download"> \<br /> <span>Link 1</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/wiki/Link_2" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-minerva-mapPin"> \<br /> <span>Link 2</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/wiki/Link_3" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-wikimedia-bellOutline-base20"> \<br /> <span>Link 3</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul>\<br /> <ul> \<br /> <li> \<br /> <a href="/wiki/Second_Link" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-wikimedia-star-base20"> \<br /> <span>Second Link</span> \<br /> </a> \<br /> </li> \<br /> </ul>'<br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Mobile.js&diff=611 MediaWiki:Mobile.js 2021-05-21T07:13:04Z

<p>Liam: Created page with "/* All JavaScript here will be loaded for users of the mobile site */ var timer = setInterval(function() { if ($('.menu ul:first').length) { console.log("mo..."</p> <hr /> <div>/* All JavaScript here will be loaded for users of the mobile site */<br /> <br /> var timer = setInterval(function() {<br /> if ($('.menu ul:first').length) {<br /> console.log("mobile menu exists");<br /> clearInterval(timer);<br /> $('.menu ul:first').after(<br /> '<ul class="level1"> \<br /> <li> \<br /> <a href="#" \<br /> class="mw-ui-icon mw-ui-icon-before mw-ui-icon-minerva-watchlist"> \<br /> <span>Dropdown Links</span> \<br /> </a> \<br /> </li> \<br /> <ul class ="level2"> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_1:Strategies_for_engineered_outcomes" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Strategies for Engineered Outcomes</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_2:Structural_engineering" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Structural Engineering</span> \<br /> </a> \<br /> </li> \<br /> <li> \<br /> <a href="/index.php?title=Chapter_3:Hello" \<br /> class="mw-ui-icon mw-ui-icon-before"> \<br /> <span>Hello from Chapter 3</span> \<br /> </a> \<br /> </li> \<br /> </ul> \<br /> </ul> \<br /> <br /> );<br /> $(".menu").find(".level2").hide(); // hide level2 until level1 is clicked<br /> $(".level1").click(function(event){ <br /> $(this).find(".level2").slideToggle(500);<br /> }); // if level1 is clicked, dropdown level2<br /> }<br /> }, 100); // check every 100ms</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Common.css&diff=609 MediaWiki:Common.css 2021-05-19T15:31:45Z

<p>Liam: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> .mw-editsection { display:none!important; }</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=608 MediaWiki:Vector.css 2021-05-19T15:17:31Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold; font-size: 1em}<br /> #p-Chapters {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=607 MediaWiki:Vector.css 2021-05-19T15:16:30Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold; font-size: 1em}<br /> #n-Strategies-for-Engineered-Outcomes {font-weight: bold}<br /> #p-navigation {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=606 MediaWiki:Vector.css 2021-05-19T15:14:01Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold; font-size: 1em}<br /> #n-Strategies-for-Engineered-Outcomes {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=605 MediaWiki:Vector.css 2021-05-19T15:13:41Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold; font-size: 1em}<br /> #vector-menu-content-list {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=604 MediaWiki:Vector.css 2021-05-19T15:12:35Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold; font-size: 1em}<br /> #p-tb-label {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=603 MediaWiki:Vector.css 2021-05-19T15:10:37Z

<p>Liam: </p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {font-weight: bold}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Vector.css&diff=602 MediaWiki:Vector.css 2021-05-19T14:47:19Z

<p>Liam: Created page with "/* All CSS here will be loaded for users of the Vector skin */ #p-Chapters-label {color: red}"</p> <hr /> <div>/* All CSS here will be loaded for users of the Vector skin */<br /> <br /> #p-Chapters-label {color: red}</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Common.css&diff=601 MediaWiki:Common.css 2021-05-19T14:41:49Z

<p>Liam: </p> <hr /> <div>/* CSS placed here will be applied to all skins */<br /> <br /> /* .mw-editsection { display:none!important; } */</div>

Liam https://eit.engineers.scot/index.php?title=Chapter_2:Structural_engineeering&diff=178 Chapter 2:Structural engineeering 2021-02-24T15:01:16Z

<p>Liam: Liam moved page Chapter 2:Structural engineeering to Chapter 2:Structural engineering</p> <hr /> <div>#REDIRECT [[Chapter 2:Structural engineering]]</div>

Liam https://eit.engineers.scot/index.php?title=Structural_engineering&diff=177 Structural engineering 2021-02-24T15:01:15Z

<p>Liam: Liam moved page Chapter 2:Structural engineeering to Chapter 2:Structural engineering</p> <hr /> <div>=== Structural design ===<br /> <br /> === [[Structural Analysis:|Structural analysis]] ===<br /> <br /> === [[Application Sheets:|Applications]] ===</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=176 MediaWiki:Sidebar 2021-02-24T15:00:34Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for engineered outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Hello|Hello from Chapter 3<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=175 MediaWiki:Sidebar 2021-02-24T14:58:35Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Strategies for Engineered Outcomes|Strategies for Engineered Outcomes<br /> ** Chapter 2:Structural engineering|Structural Engineering<br /> ** Chapter 3:Hello|Hello from Chapter 3<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=Structural_engineeering&diff=174 Structural engineeering 2021-02-24T14:57:56Z

<p>Liam: Liam moved page Structural engineeering to Chapter 2:Structural engineeering</p> <hr /> <div>#REDIRECT [[Chapter 2:Structural engineeering]]</div>

Liam https://eit.engineers.scot/index.php?title=Structural_engineering&diff=173 Structural engineering 2021-02-24T14:57:55Z

<p>Liam: Liam moved page Structural engineeering to Chapter 2:Structural engineeering</p> <hr /> <div>=== Structural design ===<br /> <br /> === [[Structural Analysis:|Structural analysis]] ===<br /> <br /> === [[Application Sheets:|Applications]] ===</div>

Liam https://eit.engineers.scot/index.php?title=Strategies_for_system_planning&diff=171 Strategies for system planning 2021-02-24T14:57:17Z

<p>Liam: Liam moved page Strategies for engineered outcomes to Chapter 1:Strategies for engineered outcomes</p> <hr /> <div>For a basic introduction see ''[http://www.iesis.org/toengineer/To-Engineer.pdf To Engineer]''<br /> <br /> ===[https://eit.engineers.scot/index.php%3Ftitle=Critical_thinking Critical thinking]===<br /> Critical thinking represents the thought processes and guiding principles that may be used when working with complex uncertainty.</div>

Liam https://eit.engineers.scot/index.php?title=MediaWiki:Sidebar&diff=170 MediaWiki:Sidebar 2021-02-24T14:56:54Z

<p>Liam: </p> <hr /> <div>* navigation<br /> ** mainpage|Main Page<br /> ** Special:ArticlesHome|Blog Posts<br /> ** Special:AllPages|Page List<br /> * Chapters<br /> ** Chapter 1:Introduction|Strategies for Engineered Outcomes<br /> ** Chapter 2:Welcome|Structural Engineering<br /> ** Chapter 3:Hello|Hello from Chapter 3<br /> * TOOLBOX</div>

Liam https://eit.engineers.scot/index.php?title=Main_Page&diff=160 Main Page 2021-02-24T01:13:57Z

<p>Liam: </p> <hr /> <div>== Welcome to Engineer-it ==<br /> ''Engineer-it'' is a resource for information about how to achieve engineered solutions, how to address situations of complex uncertainty. ''Engineering'' is viewed as an overarching concept in such endeavour. The principles used have wide applicability e.g. businesses are ‘re-engineered’..<br /> <br /> == New feature: Chapters ==<br /> Using custom namespaces, we've been able to give chapters their own space to create and educate on Engineer-it. You'll find the links to their intro pages on the left sidebar.</div>

Liam