Boundary Conditions
Students define and justify the boundary conditions applied to the model, showing how each condition was selected from field or design evidence.
Section progress
0% of the workflow complete
Computational Engineering · Build, calibrate, verify and validate the numerical model that supports your design decisions.
Deliverable: Boundary condition justification memo with model screenshots.
Minimum tables, figures and equations for Boundary Conditions
Tables — at least 6
- Table — trial sections or sizes considered, with the capacity of each and the selection decision
- Table — final selected geometry for every element: dimensions, thickness, grade, spacing, elevation
- Table — ultimate limit state check summary: demand, capacity, ratio, pass or fail, governing clause
- Table — serviceability check summary: deflection, crack width, settlement, freeboard or velocity against its limit
- Table — factors of safety achieved against the factor required, per failure mode
- Table — strength, service, fatigue and extreme-event checks with ratios
Figures — at least 5
- Figure — free body diagram of each isolated element, fully labelled with loads, reactions, dimensions and axes
- Figure — shear and moment (or pressure and velocity) diagrams for each force-carrying element
- Figure — dimensioned section or plan of each designed element
- Figure — capacity versus demand plot, interaction diagram, or rating curve as applicable
- Figure — girder, bearing and substructure elevation with dimensions
Equations — at least 7
- Equation — equilibrium equations written out for each free body (sum of forces and sum of moments, or continuity and energy)
- Equation — the internal force relations V(x) and M(x), or the momentum/thrust relation, used to compute each element's demand
- Equation — the resulting demand at the critical section of each element, with numeric substitution
- Equation — the capacity expression for each element type, shown with full numeric substitution and units
- Equation — the sizing criterion that sets the final dimension (for example required area, depth or diameter)
- Equation — each limit state check written as demand over capacity with numbers substituted
- Equation — the factor of safety calculation for each failure mode checked
Number every table and figure (Table 4.x, Figure 4.x), caption it, and refer to it by number in your text. Number displayed equations and show the substitution with units. These counts are minimums — add whatever else your design needs.
Engineering documentation standard — required in every Chapter 4 subsection
These rules are graded on every subsection. Work that misses them is capped on technical accuracy, exhibits, codes and communication, whatever the quality of the prose.
Code and standard references
- Every requirement, factor, coefficient, limit and allowable you apply cites the governing document AND the exact section, article or sub-article number — e.g. ACI 318-19 §22.5.5.1, AISC 360-22 Chapter J, Section J3.6, AASHTO LRFD 10th Ed. Article 3.6.1.2.2, ASCE 7-22 §12.8.1, ASTM D2487, state DOT manual section, local stormwater manual chapter.
- Give the edition or year of every document the first time it appears, then use a consistent short form.
- Where a code equation is used, quote the equation number (e.g. Eq. 22.5.5.1) next to your displayed equation.
- Where you depart from a code provision, state the clause you are departing from and the engineering justification.
- List every code, standard and manual actually used in a Codes and Standards table at the start of the subsection.
Citations for statements
- Every statement of fact, value taken from elsewhere, material property, soil parameter, rainfall depth, unit cost or published method carries an in-text citation (APA) to its source.
- Field and lab data cite the report, boring log, gauge, survey file or test number and its date.
- Manufacturer data cites the product literature and revision date; software results cite the program, version and model file name.
- Uncited assertions are treated as assumptions and must appear in the assumptions table with a justification.
- Every in-text citation resolves to a full entry in the reference list.
Step-by-step calculations
- Structure every calculation the same way: (1) objective, (2) governing code clause, (3) equation in symbolic form with the equation number, (4) definition of each symbol, (5) numerical substitution, (6) result with units, (7) comparison against the limit and the pass/fail statement.
- Show the substitution line — never jump from the formula to the answer.
- Number displayed equations sequentially (Eq. 4.1, 4.2, …) and refer to them by number in the text.
- State the load or flow combination governing each calculation by name.
- Carry consistent significant figures and round only at the reported result; state the rounding convention once.
- Present repetitive element checks in a calculation table with one row per element and the same column order throughout.
Free body diagrams and figures
- Draw a separate free body diagram for each isolated element — no combined sketches standing in for several members.
- Dimension every FBD: span, depth, thickness, cover, eccentricity, embedment, slope, pipe diameter, wall height — with the dimension lines and values shown.
- Label every force, pressure, reaction and moment with its symbol, magnitude and units, and show the sign convention and coordinate axes.
- Show supports and boundary conditions explicitly (pin, roller, fixed, elastic, buoyant, hydrostatic).
- Accompany each FBD with its shear, moment, thrust, pressure or hydraulic grade diagram at the same scale reference.
- Number and caption every figure (Figure 4.x) and refer to it by number in the narrative; add a scale or north arrow to plans.
Units and notation
- Every number in text, tables, figures and equations carries its unit — no bare numbers.
- Use one unit system throughout (US customary or SI); if both appear, give the converted value in parentheses consistently.
- Check dimensional homogeneity of each equation and say so — the units of both sides must match.
- Provide a nomenclature table defining every symbol with its unit.
Checking and verification
- Every calculation is checked by an independent route — hand check against software, alternative method, order-of-magnitude estimate, or a published worked example — and the check is shown, not just claimed.
- Report demand-to-capacity ratios and factors of safety against the required values, with the source clause for each required value.
- Include a verification/checking table: item, method of check, expected, obtained, difference, accept or revise.
- Sanity-check every result (magnitude, direction, plausibility) and state the conclusion.
- Record who checked the work and on what date; flag anything still unverified as an open item.
- State limitations and the range over which the result is valid.
How to complete this section
Do this next: Read the Boundary Conditions lecture and the worked example so you know what "Boundary condition justification memo with model screenshots." has to contain.
Not sure how to start or how much depth is expected? Read the fully written model example for this deliverable first — it shows the structure, tables and level of justification your advisor grades against.
Modeling & Simulation Center — what this workspace teaches
Build, calibrate, verify and validate the numerical model that supports your design decisions.
- Selecting analysis software for the engineering question (STAAD, SAP2000, ETABS, HEC-RAS, OpenRoads, Civil3D, ArcGIS, MATLAB, Python)
- Model geometry idealization and simplification
- Boundary conditions, supports, restraints and their effect on results
- Load application and load-case management in software
- Mesh and element selection; convergence studies
- Model calibration against measured or benchmark data
- Sensitivity analysis of governing input parameters
- Verification (solving the equations right) vs. validation (solving the right equations)
- Exporting, documenting and archiving model results
End-of-term milestones
- Tuesday, November 17, 2026 — Poster printed and ready. 36 in × 48 in poster finalized and printed one week before the November 24 showcase.
- Wednesday, November 18, 2026 — Final document package uploaded for scoring. Chapters 4–5, calculation package, drawings and appendices uploaded in the app for advisor scoring.
- Wednesday, November 18, 2026 — Poster presentation to faculty and industry. Wednesday poster session — printed 36 in × 48 in poster presented in person; industry reviewers score communication and impact.
- Wednesday, November 25, 2026 — Oral presentation and defense (scored). Scored oral presentation and defense held on Wednesday, November 25.
Boundary Conditions
Students define and justify the boundary conditions applied to the model, showing how each condition was selected from field or design evidence.
Section B
Engineering story
A real project situation that frames this module
The team opens week 4 believing boundary conditions is a formality, because the proposal treated it in a single sentence. Students define and justify the boundary conditions applied to the model, showing how each condition was selected from field or design evidence. The first review question is not about arithmetic — it is where the basis for support idealization came from.
Modeling a footing as fully fixed when the geotechnical report indicates significant settlement is expected. Because boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain, the error does not stay local: it is carried into the calculation package a reviewer must be able to reproduce line by line, and every downstream product inherits it before anyone notices.
Building occupants, erection crews and the structural engineer of record carry the consequence. On this module specifically, the exposure runs through soil-structure interaction boundary representation (subgrade modulus, spring stiffness), and the cost of correction rises every week the calculation package and framing drawings moves closer to issue.
Decisions the engineer must make
- What record establishes support idealization, and is that record in the project data inventory?
- Which adopted document governs this decision, and who confirmed it applies in this jurisdiction?
- What is the acceptance criterion for boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain, and was it written before the result was known?
- Is k = ks·B·L valid over the parameter range this project actually occupies?
- If the check fails, does the team revise the calculation package and framing drawings or raise a change request against the locked baseline?
Photo 1. Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Section C
Why this matters
Professional
Boundary Conditions is judged on whether an independent engineer can follow your reasoning to the same conclusion. Your boundary condition justification memo with model screenshots. is the evidence that they can.
Technical
Support idealization is what makes k = ks·B·L usable on this project rather than a formula copied from a reference. Get it wrong and every quantity derived from it is wrong by the same factor.
Safety
The failure mode this module guards against is an element loaded beyond its governing limit state. It reaches people through symmetry and far-field boundary truncation in continuum models, which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.
Economic
The calculation package a reviewer must be able to reproduce line by line is priced from this work. Quantities, unit costs and schedule float all trace to support idealization; a late correction here is paid for as a change order, not a redline.
Environmental
Environmentally, this module fixes embodied carbon in concrete and steel, and the demolition waste of a redesign. Choosing conservatively without justification is not free — the excess shows up as material, energy and land that the project consumes for no measurable gain.
Community
Occupants who rely on the structure performing through its design life and design event inherit whatever this module decides — performance, accessibility, cost of ownership and resilience are set here, not at the ribbon-cutting.
Section D
Learning objectives
By the end of this module you will be able to:
- 1.Explain support idealization, using this project's own conditions rather than a textbook case.
- 2.Interpret boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain, using this project's own conditions rather than a textbook case.
- 3.Compare soil-structure interaction boundary representation (subgrade modulus, spring stiffness), using this project's own conditions rather than a textbook case.
- 4.Justify symmetry and far-field boundary truncation in continuum models, using this project's own conditions rather than a textbook case.
- 5.Compute the governing quantity from k = ks·B·L, with a unit audit on every term.
- 6.Reproduce the worked example for a 2 m × 3 m footing rests on soil with coefficient of subgrade reaction ks = 15,000… and defend the interpretation of the result.
- 7.Produce boundary condition justification memo with model screenshots. at a standard the plan reviewer at the building department would accept without a second revision cycle.
Section E
Instructional content
Full lecture notes with figures and governing equations
Boundary Conditions — what the work actually is
Students define and justify the boundary conditions applied to the model, showing how each condition was selected from field or design evidence. That single sentence hides the substance of the module: support idealization, and boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain. Both must be established from project evidence before anything downstream is credible.
In structural engineering, this work is the input to the calculation package and framing drawings. Soil-structure interaction boundary representation (subgrade modulus, spring stiffness) — which is why this page asks you to record the source of every quantity, not just its value. The calculation package a reviewer must be able to reproduce line by line depends on it.
- Support idealization: pinned, fixed, roller, spring — and the field evidence justifying each
- Boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain
- Soil-structure interaction boundary representation (subgrade modulus, spring stiffness)
- Symmetry and far-field boundary truncation in continuum models
Photo 1. Boundary Conditions — what the work actually is in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Governing relationships and how they are applied here
The relationships below govern boundary conditions. k = ks·B·L — each is valid only inside the parameter range this project occupies, so state that range before substituting.
Boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain sets the values you place into these expressions. Any prescribed factor must be traced to the document your jurisdiction adopted, not to a lecture slide.
k = ks·B·L
- k = equivalent spring stiffness at a footing boundary
- ks = coefficient of subgrade reaction
- B, L = footing width and length
Photo 2. Governing relationships and how they are applied here in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Constraints, adopted standards and the safety case for boundary conditions
No single code section governs this module, so the constraint set comes from the approved proposal, the owner's requirements and professional practice. Write those constraints down; an unwritten constraint is not enforceable at review.
The safety case is explicit here. The failure mode is an element loaded beyond its governing limit state; the people exposed are building occupants, erection crews and the structural engineer of record; the control that prevents it is symmetry and far-field boundary truncation in continuum models together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: support idealization.
- Adopted reference: confirm with the jurisdiction before you rely on it.
- Failure mode guarded: an element loaded beyond its governing limit state.
- Evidence produced: Boundary condition justification memo with model screenshots..
Photo 3. Constraints, adopted standards and the safety case for boundary conditions in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.
Capstone Studio instructional photograph
Where this method stops being valid
The worked example — a 2 m × 3 m footing rests on soil with coefficient of subgrade reaction ks = 15,000 kN/m³ — holds only while its assumptions hold. This stiffness value replaces a rigid support at the footing in the structural model, allowing the analysis to capture realistic settlement-induced load redistribution rather than assuming an infinitely rigid base. Outside that envelope the arithmetic still returns a number, and the number is wrong in a way no unit check will catch.
For this project, the boundary you are most likely to push is symmetry and far-field boundary truncation in continuum models. If you cross it, say so in writing, bound the error, and carry the limitation into your results chapter. A disclosed limitation is professional practice; a silent extrapolation is not.
Photo 4. Where this method stops being valid in practice — Subsurface investigation: SPT samples and the boring log that every geotechnical number traces back to.
Capstone Studio instructional photograph
Section F
Engineering workflow
Steps
- 1. Assemble the inputs this module needs — support idealization; boundary condition sensitivity — bounding a design between fixed and… — each with a unit and a source record.
- 2. Confirm which document governs, and record who verified that it applies here.
- 3. State the assumptions and the acceptance criterion for support idealization.
- 4. Evaluate k = ks·B·L term by term, carrying one extra significant figure.
- 5. Test the result against soil-structure interaction boundary representation (subgrade modulus, spring stiffness).
- 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
- 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
- 8. Assemble boundary condition justification memo with model screenshots. and submit it to the plan reviewer at the building department for review.
Decision points
- Is every input behind support idealization traceable? If not — stop and collect the record.
- Does the result satisfy boundary condition sensitivity — bounding a design between fixed and pinned assumptions when uncertain? If not — revise the work, never the criterion.
- Would the correction change the calculation package a reviewer must be able to reproduce line by line? If yes — raise a change-control request before proceeding.
- Have you ruled out the most common error on this module — modeling a footing as fully fixed when the geotechnical report indicates significant settlement is expected?
Quality checklist
- Documented: support idealization
- Documented: boundary condition sensitivity — bounding a design between fixed and pinned assumptions…
- Documented: soil-structure interaction boundary representation (subgrade modulus, spring stiffness)
- Governing document cited
- Units audited on every expression
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Boundary condition justification memo with model screenshots. attached and named per the course convention
Section H
Interactive visualization
Boundary Conditions — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Review field/design evidence for each support condition (connection detail, soil report).
Section I
Applicable codes and standards
Section J
Worked examples
Full engineering solution format
Section K
Common mistakes and how to avoid them
- Modeling a footing as fully fixed when the geotechnical report indicates significant settlement is expected.
- Truncating a far-field boundary too close to the zone of interest, artificially stiffening the model response.
- Treating support idealization as a given instead of establishing it from a project record.
- Producing boundary condition justification memo with model screenshots. without showing how boundary condition sensitivity — bounding a design between fixed and pinned assumptions… was satisfied.
- Substituting into k = ks·B·L outside the range where it is valid, and reporting the number anyway.
- Missing symmetry and far-field boundary truncation in continuum models, which is exactly the path to an element loaded beyond its governing limit state.
- Reporting model output without documenting mesh, boundary conditions, solver settings or convergence.
- Calibrating a model until it matches expectation, then presenting the match as validation.
- Citing the wrong edition of a standard, or citing a standard that does not govern the jurisdiction.
- Leaving boundary conditions undefined so the model is not reproducible by an independent checker.
- Using inputs that no field record, laboratory report, or published source supports.
Section L
Industry case study
Documented failure related to boundary conditions
A constructed civil works project where this module's decision was made incorrectly or skipped.
Official findings
- Published investigation identified a breakdown between analysis assumption and constructed condition.
Field observations
- The controlling assumption was documented nowhere in the design record.
- No independent check existed at the stage where the error entered the work.
Engineering interpretation
- Interpretation below is student analysis for instructional purposes, not an official finding.
- Map the failure to a step in your own workflow and state where your process would have caught it.
Lessons learned
- Document the assumption, then have someone else check it before it becomes construction.
Source: Summarize the published investigation; cite it in your reference list. Do not reproduce copyrighted report text.
Section M
FE Civil exam connection
Handbook FE Reference Handbook — structural engineering section (record the section number from your handbook edition).
Exam topics
Handbook formulas
- k = ks·B·L
Weak results here feed your FE Civil Academy weak-area queue for targeted practice.
Question 1 of 2
Score: 0/2In boundary conditions, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Boundary Conditions
Complete this using your own capstone project data. Every field is saved to your project record and routed to your advisor with this module's submission.
Inputs and sources
Every value needs a traceable source.
| Quantity | Value | Unit | Source / record |
|---|
Assumptions and consequences
| Assumption | Basis | Consequence if wrong |
|---|
Self-check before submission
Section O
Design challenge
Consulting challenge — Boundary Conditions
Your firm has been retained to deliver the boundary conditions scope for a municipal client on a compressed schedule. Produce the technical position your firm would defend at a public meeting.
Client request: The client wants a defensible recommendation, the basis of design, and an honest statement of what remains unresolved.
Constraints
- Adopted local code edition governs; no exceptions without written variance.
- Budget and schedule are fixed; scope changes require change control.
- Public safety and accessibility requirements are non-negotiable.
Deliverables
- One-page basis of design
- Supporting calculation extract
- Risk and limitation statement
Evaluation
- Technical correctness
- Standard compliance
- Clarity of engineering judgment
- Honest treatment of uncertainty
Section P
Documentation workspace
Write the report section for this module in the academic editor
Section Q
File uploads
Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP, DWG, IFC
No files uploaded yet.
Section R
Deliverable and advisor review
Boundary condition justification memo with model screenshots.
Submissions route to your assigned faculty advisor and are scored independently by faculty and administrator rubrics.
Reflection
What was the hardest engineering judgment in this module, and how did you resolve it?
Section S
ABET outcome mapping
Boundary condition justification memo with model screenshots. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Technical analysis · Target: 70% of students at or above 'meets expectations'.
Boundary condition justification memo with model screenshots. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Technical analysis · Target: 70% of students at or above 'meets expectations'.
Section T
References and further study
Boundary Conditions — instructor design procedure
Course template for the calculation package format expected in the final report appendix.
NCEES FE Reference Handbook
Locate the equations used here and note the handbook section for exam recall.
Advisor meeting agenda item
Bring the unresolved decision from this module to your next weekly advisor meeting.