Integrated STAAD.Pro → Advanced Concrete/RCDC Capstone

Learning Objectives

  • Apply the complete course workflow to one three-storey reinforced-concrete building model.
  • Maintain one documented coordinate/unit/design basis from geometry through final deliverables.
  • Build and validate a connected 3D analytical frame and auditable load/mass model.
  • Verify reactions, deformed shape, representative force diagrams and selected advanced-analysis outputs before design.
  • Carry accepted beam/column/wall actions into the supported Advanced Concrete/RCDC workflow.
  • Carry accepted foundation reactions into STAAD Foundation Advanced or another project-approved foundation workflow.
  • Process one coordinated revision and demonstrate how it propagates through analysis, concrete design/detailing, foundations and quantities.
  • Assemble a concise calculation/design package that records verification evidence rather than raw output alone.

Capstone rule

The objective is not to make every software status indicator green. The objective is to create a traceable engineering argument showing why the model, analysis, design and downstream details are reasonable for stated assumptions and the installed software/product scope.

Record the current product map

Before starting, identify the installed STAAD.Pro/STAAD.Pro Advanced, STAAD Advanced Concrete (formerly RCDC), and STAAD Foundation Advanced versions/licenses available. Do not assume legacy RCDC-FE slab/mat workflows or broader STAAD.Pro Advanced entitlements exist in every standalone Advanced Concrete installation.

Project Brief

Teaching structure

Develop a regular three-storey reinforced-concrete moment-frame teaching model. Keep the grid small enough to independently estimate reactions, representative beam moments and basic lateral/dynamic behavior. Clearly state simplifications and do not present the teaching model as a permit-ready building design.

Minimum project metadata

Milestone 1 — Analytical Geometry

Build and validate the frame

  1. Establish grid spacing and three floor elevations.
  2. Create joints at every intended beam-column intersection.
  3. Connect columns and beams with explicit incidences.
  4. Assign base supports representing the teaching superstructure/foundation interface.
  5. Add sections/materials and confirm local-axis orientation.
  6. Run duplicate/disconnected/zero-length and release/support checks.
  7. Record the .std/input geometry as a model-audit artifact.

3D Analytical Model Builder

Create joints in global X-Y-Z space, connect member incidences, assign simple base supports, and inspect the resulting STAAD text model.

1 · Add joint

2 · Add member incidence

3 · Support nodes

Isometric analytical teaching view · Y shown vertical
N1N2N3N4N5N6+X+Y+Z projected

Model health

Nodes
6
Members
6
Supports
2
3D coordinates
Z = 0

A real model still needs member properties, materials, releases, loads, and stability checks. Geometry that looks connected can remain mathematically disconnected if joint coordinates do not actually coincide.

JOINT COORDINATES
1 0.00 0.00 0.00
2 6.00 0.00 0.00
3 0.00 3.00 0.00
4 6.00 3.00 0.00
5 0.00 6.00 0.00
6 6.00 6.00 0.00
MEMBER INCIDENCES
1 1 3
2 2 4
3 3 4
4 3 5
5 4 6
6 5 6
SUPPORTS
1 2 FIXED

Milestone 2 — Loading and Design Basis

Create auditable loading

  1. Define selfweight/dead, superimposed dead, live and lateral teaching cases.
  2. Confirm load arrows, directions and signs before combination.
  3. Define the dynamic/seismic mass source separately from force combinations.
  4. Use FLOOR/element loading consistent with the selected slab analytical idealization.
  5. Create selected service/strength teaching envelopes or code combinations appropriate to the assignment.
  6. Record the standard/edition source for any project code factors used.
  7. Hand-sum at least one floor/gravity load and compare with generated/applied load totals.

Load Sign & Combination Laboratory

Positive D and L act downward. W↑ is entered as a positive uplift magnitude, so it must subtract from downward gravity action.

Teaching combination
Net line load
44.0 kN/m
Net action is downward.
Design-basis note: These three combinations are deliberately limited teaching examples for sign conventions and load-factor mechanics. A real STAAD model must use the project's governing code, edition, load categories, and required combinations.
downward 44.0 kN/m
D
10 kN/m
stabilizing gravity
L
20 kN/m
occupancy/transient
W↑
15 kN/m
upward magnitude
wnet>0w_{net}>0 is drawn downward; wnet<0w_{net}<0 is drawn upward. This explicit sign convention prevents a +W/−W mismatch.

Milestone 3 — Analysis Verification

Analysis acceptance gate

Post-Processing Results Visualizer

10 kN
Max bending moment25.0 kN·m
Max shear force5.0 kN
Beam length10 m
Plot scale: each diagram is normalized to its own maximum ordinate so its theoretical shape remains visible. Read engineering magnitudes from the numeric results/labels, not from pixel height.
Physical ModelP = 10 kN
Bending Moment Diagram (BMD)Mmax = 25.0 kN·m
Shear Force Diagram (SFD)V = 5.0 kNV = -5.0 kN

Milestone 4 — Advanced-Analysis Interpretation

Run an advanced method only to answer a stated engineering question

Use second-order/P-Delta, modal, response-spectrum or teaching time-history work only where the assignment calls for it. Examples: “Does compression materially magnify lateral response?” or “How does changing stiffness affect the first-mode period?” Establish a linear/closed-form benchmark first.

Dynamic Seismic Response — SDOF Newmark Integration

The relative displacement is solved from the same deterministic base-acceleration history shown on the chart.

10 t
100 kN/m
5 %
Natural frequency ω3.16 rad/s
Natural period T1.99 s
Peak |u|71.70 mm
Peak |üg|1.96 m/s²
The ground motion is a deterministic synthetic teaching record, not a recorded earthquake, response-spectrum substitute, or project-specific seismic input. This is one linear SDOF oscillator, not a modal building model.
Loading chart...
m·ü + c·u̇ + k·u = −m·üg(t)   |   Newmark β = 1/4, γ = 1/2

Milestone 5 — Current Advanced Concrete/RCDC Handoff

Move verified concrete entities downstream

  1. Freeze/record the accepted STAAD analysis revision.
  2. Confirm that the intended beam/column/wall or other entity is supported by the installed concrete workflow.
  3. Map representative physical geometry/materials and governing actions.
  4. Set the supported concrete design standard/edition and detailing preferences.
  5. Review required vs provided reinforcement, spacing/layers, grouping and failed checks.
  6. Coordinate at least one beam-column joint or wall interface for constructability.
  7. Produce one representative drawing/schedule/quantity check supported by the installed product.

STAAD Advanced Concrete / RCDC Learning Lab

A product-aware teaching bridge from verified STAAD actions to concrete design/detailing, foundation coordination, and quantity checking.

1
Verify STAAD.Pro analysis
Accept geometry, loading, equilibrium, warnings, actions and source revision.
2
Confirm current product path
Current Advanced Concrete explicitly covers beams/columns/walls; broader STAAD.Pro Advanced and SFA cover additional concrete/foundation workflows.
3
Map physical entities
Check levels, connectivity, dimensions, materials, member identity and governing action envelopes.
4
Set code and detailing basis
Record standard/edition, material grades, cover, preferred bars, spacing criteria and grouping rules.
5
Design and review
Inspect governing cases, failed checks, physical reinforcement, congestion and exceptions.
6
Issue traceable deliverables
Generate/review drawings, reports, schedules and quantities supported by the installed product/version.
Current product boundary
Bentley's current standalone Advanced Concrete page explicitly advertises beams, columns and walls. Slabs/foundations may belong to broader STAAD.Pro Advanced, STAAD Foundation Advanced, or legacy/version-specific RCDC-FE workflows. Verify the installed release/license.
Engineering boundary
Import automation never removes the need to verify model mapping, actions, design basis, warnings and constructability.

Milestone 6 — STAAD Foundation Advanced Coordination

Trace one reaction into a complete foundation workflow

Select one base-column reaction and show the chain from STAAD case/combination → support reaction → preliminary bearing screen → STAAD Foundation Advanced (or approved foundation analysis) → geotechnical/contact/stability checks → structural shear/flexure/punching/force-transfer checks → reinforcement/detailing. Clearly distinguish preliminary P/AP/A sizing from complete foundation design.

STAAD Advanced Concrete / RCDC Learning Lab

A product-aware teaching bridge from verified STAAD actions to concrete design/detailing, foundation coordination, and quantity checking.

Required plan area
5.00 m²
Adopt square screen
2.3 × 2.3 m
Average service bearing
170.1 kPa
P/A screen
within input limit
Foundation coordination—not standalone RCDC design
Current foundation analysis/design is centered on STAAD Foundation Advanced or another validated project workflow. This tab demonstrates reaction provenance and concentric P/A only; it omits eccentric contact, settlement, one-way/punching shear, flexure, force transfer, anchorage and other required checks.
R = 900 kNqavg = 170 kPa

Teaching-panel boundary

The foundation tab above is a reaction and P/AP/A coordination screen. It does not claim that standalone Advanced Concrete performs the full foundation analysis; current dedicated foundation functionality is provided by STAAD Foundation Advanced and broader STAAD-family workflows.

Milestone 7 — Controlled Revision Exercise

Demonstrate downstream propagation

  1. Move one column or revise one structural section for a documented coordination/design reason.
  2. Record the BIM/physical-model change set and ownership decision.
  3. Reconcile analytical connectivity, properties, axes and protected attributes.
  4. Re-run analysis and repeat the verification gate.
  5. Compare old/new reactions, representative forces and advanced-analysis response where relevant.
  6. Refresh affected Advanced Concrete/RCDC beam/column/wall design/detailing.
  7. Refresh STAAD Foundation Advanced checks if foundation reactions or geometry changed.
  8. Regenerate affected drawings/BBS/quantities and mark superseded deliverables.

BIM → Analytical Change-Set Review

Interoperability is not just file transfer. Engineers must inspect changed geometry, mappings, connectivity, releases, loads, supports, and other analysis-critical attributes before accepting a revision.

No universal 50 mm or similar acceptance tolerance is assumed here. Any analytical coordinate change is a change set that must be reviewed against the project basis.

Change-set status

2 review items
  • Section mapping requires review
  • Member-end release has not been mapped
Physical / source model
Continuous objects and authored design intent
physical members with design extents
Accepted analytical model
Nodes, finite members, releases and solver attributes
finite members split at joints

What should be reviewed in a real exchange

member centerlines & connectivity
section/material mapping
local-axis orientation
member releases & offsets
load/support/mass transfer
revision provenance & deletions
After an accepted BIM/analytical revision, the safe workflow is validate → re-run analysis → re-check governing results → refresh concrete/foundation design and issued quantities. Synchronized geometry does not imply synchronized engineering validity.

Final Deliverable

Capstone calculation package

Key Takeaways
  • The strongest software workflow is a connected chain of documented assumptions, product scope and verification evidence.
  • Every downstream concrete/foundation/drawing result depends on an accepted source-analysis revision.
  • A controlled revision should visibly propagate from geometry into analysis actions, reinforcement, foundations and quantities.
  • Independent checks remain useful even when the complete model is too complex to solve manually.
  • Professional output is the smallest report that still makes the engineering reasoning, software scope and revision chain reviewable.