Beam Cut Lengths Drift After Copy/Monitor
A 12-story steel building uses a linked architectural model. The structural team copy/monitors gridlines and levels only, then models W24x76 floor beams independently. During a coordination review, the contractor reports that beam ends at grid B/3 show a 38 mm gap to the column face on level 4 but sit flush on level 5. The columns are 50 mm larger on the architectural link than in the structural model because the architect updated cladding zones last week. The structural model was last reloaded three days ago. The team wants to fix level 4 quickly without touching the other ten floors, and the project lead asks whether copy/monitoring the columns would have prevented this.
1. Diagnose why the gap appears on level 4 but not level 5, and recommend a repair that does not disturb other floors.
Read the worked answer
The gap is a synchronization artifact, not a modeling error. The architectural link changed column sizes, and the structural model's last reload predates that change, so the visible geometry in the link no longer matches what the structural beams were drawn against. Level 4 differs from level 5 because the beam-to-column relationship on level 4 was adjusted after the last reload, or the level 4 beams were placed before the size change while level 5 beams were placed after it. Either way the underlying cause is stale link data combined with beams constrained to a face that has since moved.
Repair sequence:
- Reload the architectural link and review the coordination alert list before editing anything.
- Isolate level 4 in a 3D view with a section box and confirm which beam ends actually moved.
- Use the join/cut geometry and beam-end extension tools to reset the affected ends, or drag the analytical/geometric end back to the column face if the beam is not auto-constrained.
- Avoid a global 'reload latest' followed by mass edits; that risks shifting all twelve floors at once.
- Record the change in the coordination log with the link version timestamp.
The key judgment is to fix the data source first, then the geometry, and to scope edits to the affected level.
2. Should the team copy/monitor the architectural columns? Justify with coordination consequences.
Read the worked answer
Copy/monitoring columns would have surfaced the size change as a coordination alert rather than a silent geometric drift, so it is defensible. But it also introduces coupling: monitored elements can be updated or reverted by the monitor, and the structural engineer may lose control of sizes that are genuinely structural decisions.
A better judgment is to copy/monitor only the elements the structural model must obey, typically grids and levels, and to rely on interference checking plus a scheduled link-reload cadence for columns. If the team does monitor columns, they should set the copy/monitor options so that size changes generate a reviewable alert instead of an automatic update, and they should assign an owner for resolving each alert.
The exam-relevant reasoning is that copy/monitor is a coordination contract, not a convenience. Monitoring more elements increases alert volume and the chance of unintended overwrites; monitoring too few leaves drift undetected. The answer depends on who owns the column size and how often the link changes, not on a fixed rule.