Skip to main content

Tutorial 7 — Load Cases, the Envelope and the Report

Use any solvable model (the T1 model is perfect). This tutorial is about running and reporting like a production stress check.

1. Understand the case list​

Open the Load Case dropdown and read the hints: DRY, SUS, EXP, OPE, OCC-WIND, OCC-SEIS. The code checks differ per case — SUS against Sh, EXP against SA, occasional against 1.33·Sh. The manual explains each.

2. Single-case runs​

  1. Select SUS → Run Analysis — the weight/pressure state. Note the sagging shape and the support loads.
  2. Select EXP → run — the thermal stress range. The colouring changes; expansion loops and elbows light up.

This is fine for iterating on one problem, but tedious for sign-off…

3. Run All Cases​

  1. Click Run All Cases (n) ▶▶. Every relevant case solves in sequence; the toast reports the governing case and its ratio, and the viewer opens on it.
  2. Now flip the Load Case dropdown between cases: results switch instantly — they're all stored.
  3. Open All Cases ↔ in the results table: per-element ratios across every case, the governing one outlined. Sort out where each case bites: sustained governs long unsupported spans; expansion governs stiff corners and terminal points.

(OCC cases join the list automatically once wind speed or seismic input is configured in Settings — Pro.)

4. Brand the report​

  1. Settings → Report Header: company name, project number P-1234, revision A, prepared-by, checked-by, and upload your logo.

5. Generate the PDF​

  1. Download Report (PDF). Walk its sections: branded cover with 3D snapshot → load case definitions → design parameters → material/section/restraint schedules → the full stress table for the viewed case → All-Load-Cases Envelope (per-case ratios, governing case starred, envelope statement) → displacements → reactions → executive summary with the pass/fail banner.

That envelope page is the "one PDF" a checker wants: every element, every case, one governing statement.

6. CSV for your own spreadsheets​

  1. Download CSV — the raw per-end stress components for every element, ready for pivot tables or company calc sheets.

7. Iterating​

Any model edit invalidates results (viewer returns to pre-analysis). The habit that works: edit → Check Model → Run All → read the envelope. With stored cases, reviewing alternatives is one click per iteration.