ArchHubBABOOMDownload

Structural modelling and analysis exchange

BBM-STD-59 · V0.2 · The structural discipline lead allocates physical modelling, analysis, design review and specialist detailing by element, purpose, stage and exchange

Download WordFormsAll standards

BBM-STD-59-STRUCTURAL_MODELLING-V0.2 | Office standard | 4 November 2026 | V0.2 | Private controlled WIP draft for office review

Revision history

VersionDateChange
V0.12026-10-16Initial controlled WIP draft.
V0.22026-11-04Closed audit row: design code edition taken from the BBM-STD-51 §3 register (DBC as amended / ADIBC edition in force); IMI Framework naming; links to current set versions; spacing fixes (e.g. 'over 6 m', 'load 60 kN').

1 Scope and engineering responsibility#

This standard addresses. The structural discipline lead allocates physical modelling, analysis, design review and specialist detailing by element, purpose, stage and exchange; the competent structural engineer retains design responsibility. A modeller cannot approve analysis assumptions or load paths. Use BoD, EIR and LOIN, coordinates, templates, dictionary, Manual and BEP. The editable structural pack provides Scope, Members, Analysis, Transfer, Rebar, Interfaces, Tests and Acceptance registers with blank counterparts.

Agree whether each object serves concept sizing, spatial coordination, technical documentation, structural analysis or contracted reinforcement/fabrication. Geometry, alphanumeric information and documents are separate LOIN requirements. Record inclusions/exclusions and a source-to-receiver responsibility matrix; an excluded specialist model needs an explicit interface owner and deliverable. Construction-stage temporary works and verified existing-condition assessment are separate appointed engineering scopes. Proposed member dimensions are not certified capacities.

Physical objects describe located size/material/shape and drawing/quantity intent. Analytical members/panels/nodes describe a calculation idealisation with engineering offsets, releases, connectivity and boundary conditions. Retain stable mappings between both; one analytical member may represent several physical segments or vice versa. Revit release behavior differs: modern analytical objects can be independent of physical geometry. Automation creates a candidate requiring engineer checks, not an automatically correct load path. Record exact authoring, analysis solver, exporter/connector and receiver builds/presets before use; no connector compatibility is inferred from a product name.

2 Physical model and member controls#

Start from accepted survey/coordinate control, grid/level register and an approved structural template. Preserve datum, axes and north; use copy/monitor or reference notices only as a prompt to independently resolve changed controls. Member rows require stable ID/native mapping, category, section/profile orientation, material grade/source, level/grid, end offsets/eccentricities, bearing/connection intent, phase and load-bearing function. Model slabs/walls/foundations with correct thickness, extent, voids and constraints; do not use generic solids without an approved category/property/export mapping.

Check joins, cutbacks, slopes, rotations and vertical offsets in plan/section and itemised schedules. A clean visual join may mask noncoincident analytical nodes. Foundations require declared support/soil interface and design-basis source; model geometry does not establish allowable bearing, soil properties or pile capacity. Structural material strength/modulus/density units and source revisions must be verified by the engineer rather than inferred from appearance/name. Link approved material IDs and classifications to BBM-STD-72; no new shared GUID is allocated here. Record quantity deductions at openings and overlaps; architectural finish/core ownership must prevent duplicated structural quantities.

The fictional SYN-STR59 fixture is a simple beam supported at nodes N1=(0,0,3000) and N2=(6000,0,3000), native coordinates mm in an explicitly local right-handed frame. It is a separate arithmetic fixture, not a site survey or substitution for BBM-STD-63's SYN-T63. Physical B01 spans those endpoints; its analytical counterpart A01 has local x from N1 to N2 and local z up, with local y completing the right-handed frame. Section/material values are test inputs chosen by the competent operator, not designed in this document. Any physical eccentricity is recorded separately and not silently absorbed into the analytical span.

3 Analysis and calculation provenance#

For every analytical model record source physical revision/hash, mapping, nodes/members/panels, local/global axes, offsets/rigid links, connectivity, supports, releases, diaphragm/mesh assumptions, loads and combinations, solver method/options, design code edition (a BBM-STD-51 §3 edition register ID: for Dubai the structural provisions of the Dubai Building Code (Decree 45/2021) as amended by DM Administrative Resolution No. 225 of 2024 and any DM amending resolution in force at permit submission; for Abu Dhabi the ADIBC edition published by DMT and in force at project start (2013 edition at 2026-11-04); other jurisdictions as assigned through BBM-STD-57 and BBM-STD-85), material/section dictionary, uncertainty and competent engineer/checker. The engineer approves load cases/combinations, factors, support freedoms, stiffness/release assumptions and applicable result criteria. Undefined engineering inputs hold analysis release. A connected mesh alone does not prove a valid structural idealisation.

For SYN-STR59 only, use a stable simply supported vertical-bending idealisation: one support restrains translations needed for stability, the other permits axial expansion; remaining freedoms/plane restraints must be explicitly defined by the engineer to avoid a mechanism. Ignore self-weight by an explicit solver setting and apply a uniform vertical load of 10 kN/m over 6 m. Expected total vertical load 60 kN, end reactions 30 kN each and maximum sagging bending moment 45 kNm (wL squared/8). These are equilibrium fixtures, not building-design loads or adequacy criteria. The analytical test requires documented local/global sign mapping. Enter actual reactions/moments and measured difference; REQ--E allows <=0.01 kN reaction difference and <=0.01 kNm moment difference for this numerical exercise only. A result with opposite sign may be correct only when its recorded convention reconciles; an unexplained sign/unit difference fails.

Keep calculation input/output files, assumptions, model and solver logs, result tables, warnings and signed/scoped engineering review linked to source revisions/hashes. Do not use screenshot maxima without member, load case, unit and sign context. A revised opening, member or support requires engineer impact assessment and rerun of affected analysis/design checks, followed by independent review.

4 Native to analysis transfer and specialist reinforcement#

Qualify the selected transfer direction and interface on isolated copies. Freeze the physical/analytical baseline; compare member/node counts and stable mapping, coordinates/units, axes, section/material properties, releases, supports, loads/combinations and excluded/unsupported objects before solving. Record any connector remeshing, merged nodes, changed offsets or property substitution. Reimport results or approved geometry only under a reviewed ChangeID; compare against the frozen source and reject unintended changes. An IFC coordination file is not assumed to carry an analysis-ready model. The agreed delivery must explicitly specify native or analysis schema, settings and complementary calculation documents where necessary.

Rebar/detailing is activated only by appointment. The specialist and structural engineer agree bar/mesh/coupler/shape naming, grade, diameter, cover, spacing, hooks/bends/laps/anchorage, host/zone/phase, schedules and fabrication interface. Every numeric criterion needs its BoD/code/manufacturer or approved design source; this standard specifies none as universal. Agree fabrication and placement tolerances for each relevant feature, with value/unit, approved source and edition, measurement method and uncertainty, source/receiver measured deviation and competent acceptance. Missing required tolerance evidence holds the affected fabrication release. Define theoretical versus fabrication length, shape-code edition, rounding and quantity treatment, supported exchange and exclusion of embedded supplier IP. Test native host association, cover constraints, varied geometry, bar marks, schedule totals and receiving fabrication semantics. Identical-looking bars must not merge incompatible shape/grade/diameter data. Uncontracted fabrication detail remains an explicit exclusion, never an implied engineering approval.

The synthetic rebar fixture SYN-RB59 is a data-transfer test only: B01 has two scheduled straight test bars, mark RB01, diameter 16 mm, test length 2000 mm each, total 4 m. These are not reinforcement design, cover or anchorage instructions. Mutate one bar mark to duplicate an incompatible diameter 20 mm: expected Fail grouping/identity; correct grouping and retest. The competent engineer must replace fixture assumptions with approved actual detail before reliance.

5 Openings changes and interfaces#

Architecture/MEP propose openings with unique OpeningID, host member/native ID, coordinates/size/unit, purpose, required date, source revision and engineering consequence. Structural engineer decides permissible opening geometry/reinforcement before the host author creates it; services author confirms required insulation/firestop/access allowances; fire specialist owns rated interface performance. A void visible in a linked model is not approval to cut a beam. Record builder's-work owner, approval state and source-to-sheet/schedule links. Keep rejected and superseded proposals traceable without inserting them into an issued accepted model.

SYN-OP59 requests a service opening intersecting B01. Its initial status is Hold pending engineer review, irrespective of whether a clash checker calls it clear. If the approved design changes the host or opening, record both revisions, update physical/analytical mappings, rerun calculations and coordination, and notify all affected owners under one ChangeID. Recheck structural member quantities and documentation. Preserve prior accepted source and receiver snapshots; rollback uses the compatible preserved baseline, not unsupported save-back from a newer release.

6 Tests and release evidence#

Scope and Members are author/check forms; Analysis and Transfer separate engineering assumptions from transport evidence; Rebar and Interfaces retain conditional specialist responsibilities. Tests records positive and independent adverse cases with expected versus actual outcomes. Mutation cases are missing section/unit mapping, node N2 displaced 10 mm from the declared analytical endpoint, unsupported release, dropped load, duplicate/incompatible bar mark and unapproved opening. For the synthetic geometry fixture REQ--G specifies endpoint residual<=1 mm; 10 mm fails. These values are exercise criteria only. Each correction starts from a preserved baseline; keep failed evidence and separate independent retest, including actual source/output hashes, builds, operator/date and receiver report.

Before issue the competent structural reviewer accepts physical/analytical source and receiver geometry/data, engineering assumptions and calculation adequacy for the stated purpose; coordination and QA reviewers resolve their own checks. Full mandatory field validation and all required engineering checks apply to the scoped objects. A zero-clash or script pass cannot substitute for engineering judgement. Producer check, independent engineering review, authorised submission and recipient scoped acceptance are separate decisions. Actual native fixtures, analysis results, reinforcement files, authority submissions and office adoption remain Not executed by this editorial pack. No remaining unknown required input may be presented as approved structural design.

References#