ArchHubBABOOMDownload

Federation reference links and model boundaries

BBM-STD-64 · V0.2 · The BIM Coordinator owns the declared federation baseline and run

Download WordFormsAll standards

BBM-STD-64-FEDERATION-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 rows: 'Shared/S1' replaced by SU-COORD, IFC validation report and ISO 21597 ICDD option in the manifest; third control SYN-H3; IMI Framework naming; current set links; spacing fixes + cross-doc pointer pass.

1 Scope partitions and ownership#

This standard covers and implements BEP §8.1/8.5 and Manual §3.3/10.2. The BIM Coordinator owns the declared federation baseline and run; each task team owns one authoritative source for its scoped objects; discipline designers retain technical responsibility; independent coordination/coordinate reviewers verify the package and receiving use. Follow EIR and LOIN, coordinates, templates, dictionary, clash matrix, Manual and BEP. Use the editable federation matrix and manifest.

Before modelling establish intended federation uses, required disciplines/buildings/zones/levels/systems and explicit exclusions linked to EIR/LOIN/delivery IDs. Allocate scope by a stated primary rule or documented mix; worksets aid loading/borrowing and are not security permissions or permanent responsibility ownership. Record model boundaries and interface/handoff owners. One object has one accountable authoritative model even when another discipline carries a deliberate reference/proxy. Displaying it twice does not create two quantities or two accepted design sources. BEP's 300 MB investigation trigger is a prompt to measure performance/splitting needs, not a universal model-size acceptance ceiling.

SYN-FED64 R01 is a fictional coordination package, exchange SYN-EX64 R01, with three sources: ARC64, STR64 and MEP64 covering Z01/L01 and the Z01/Z02 interface at local X=10000 mm. Z01 owns the left-side architectural scope; the adjacent Z02 scope is explicitly outside this small fixture except the declared handoff. Structural member STR-S01 crosses the plane and remains wholly owned by STR64; MEP route MEP-P01 crosses through proposed opening SYN-OP64 whose host remains STR-S01. No artificial split or duplicate structural body is authorised merely to match the zone line. This is a scope/identity fixture, not design or a complete real project.

2 Source register and readiness#

Register each source with stable SourceID, exact external container identity, native/internal IDs, author/task team, revision, source/hash, Shared approval decision, suitability/permitted use, scope/boundaries, datum/frame/units, dependency revisions, software/build, exchange profile and the IDS check record for that exchange (BBM-STD-89 §5). Use approved immutable snapshots, never newest filesystem timestamps or a link to a live central/cloud model. Revision, suitability, CDE state and gate A/B/C remain distinct. A Shared/SU-COORD coordination source (codes in BBM-STD-93) is not approved construction or project design acceptance.

Synthetic external containers are CLI-OFF-P064-Z01-L01-M3-A-0001 for ARC64, -S-0001 for STR64 and -M-0001 for MEP64, each R01 with.rvt native and the explicitly selected IFC variant. Code lists and exact format support must be adopted through BBM-STD-51/65; these are illustrative identities only. Record separate native/export hashes and generation provenance; do not invent file digests. Every source/dependency needed for the declared use must have an actual available permitted snapshot before a real federation run. Missing/unsupported required sources hold affected coverage; zero detected clashes from an unloaded discipline is not a pass.

Confirm source geometry completeness, phase/option, requisite property/identity validity and author/check/share evidence before aggregation. Required survey/unit or source-authority uncertainty holds placement under BBM-STD-63. Preserve worksharing live models/locals/caches and another person's ownership; federation never permits force-relinquish, acquiring/publishing shared coordinates or editing a source merely to make an overlay look correct.

3 Links transforms visibility and controlled changes#

The link register records parent and child SourceID/revision, link/native reference ID, intended direct/nested relationship, overlay/attachment or tool-equivalent behavior, source/receiver units, transform direction/matrix/source, path type/relative bundle location, pinned/locked placement where supported, loading group/workset, visibility/phase mapping and update notification. Analyse all nested dependencies and reject cycles, unintended recursion, double loading and stale references. Tool semantics differ; verify in actual build and receiving application rather than assuming a Revit setting applies to a review viewer or CAD xref.

In SYN-FED64 the root has three direct links; ARC64 also records a structural reference for authoring. The federation profile intends STR64 to be represented once. Direct references use declared overlay behavior with ARC64's nested STR reference suppressed/excluded from the aggregate; the receiver must demonstrate exactly one structural source representation. If it cannot honour the selected nesting behavior, create an explicitly approved flattened package from the same frozen snapshots and manifest, preserving identity and evidence. Do not bind/merge CAD or Revit references without a scoped approved mapping of object IDs, layers/properties and dependencies. CAD xrefs separately record attachment/overlay, insertion/units, clipping and any bind decision under BBM-STD-66.

Visibility is explicit for required models/categories, load state, worksets, phases/options, crop/section box and discipline/detail. A hidden required object remains within validation scope even if a view excludes it for a defined presentation. The run coverage report states actual loaded/checked and intentionally excluded objects/regions with approval. Never use unloaded worksets or clipped views to claim complete clash or boundary coverage. Read-only/pinning settings prevent accidental motion but are not proof of correct coordinates or information access controls.

Real projects use the CRS record ID from BBM-STD-86 §2/§6 for every source. Coordinate normalization in this fixture uses BBM-STD-63's SYN-T63 R01 only: convert source model mm to local m, apply one 30 degree counterclockwise rotation, offsets E5000/N7000/H100m, unit scale after conversion 1 and right-handed axes. In formulas E=5000+x cos 30-y sin 30; N=7000+x sin 30+y cos 30; H=100+z. Source-to-shared applies once; federation placement is identity when incoming geometry is already expressed in that shared frame. Record export/georeferencing representation and receiver transform explicitly to prevent a double offset/rotation. Native internal units/origin/project/shared frames are documented separately; no claim is made that a native Revit storage unit is mm.

When a source/dependency/transform/boundary changes, issue one ChangeID with old/new revisions/hashes, reason, affected models/properties/interfaces/rules/sheets/delivery rows and recipient notification/acknowledgment. Revalidate altered source checks and placement before replacing the frozen baseline; preserve prior accepted snapshots. Do not reload a changed source during a running review and retain the old result label. New R02 content cannot silently coexist in an R01 manifest.

4 Identity boundary and alignment reconciliation#

Use SourceID+native UniqueId as a scoped native key and explicitly map exported IFC GlobalId/operational Asset_ID; none are interchangeable strings. Record duplicate semantic objects even where their GUIDs differ, and identity collisions even where geometry differs. Approved proxy/reference representations have an explicit authoritative source link and count/use exclusion. Do not auto-delete overlaps, mint new GUIDs to conceal cloned content or sum quantities across duplicated discipline models.

Before clash tests verify required model list, source revisions and loaded scope, object counts by source/class/zone, repeated native/exchange/asset identities, semantic duplicate ownership, overlap/gap regions and required boundary interfaces. Inspect matched sections/controls and object/itemised property reports. SYN-OP64 must match its STR host and service/architectural request by source revision/coordinates/size/unit; unapproved cut/design adequacy remains with the competent designers. A gap or conflict at the handoff is assigned to the actual owner before affected issue, regardless of which model displays the more detailed object.

Use the independent controls from BBM-STD-63 (at least three well-distributed horizontal controls plus a benchmark), not only the point used to establish the transform. H1 local (10000,0,0)mm expects shared (5008.660254,7005,100)m; H2 local (0,20000,0)mm expects (4990,7017.320508,100)m; H3 local (-10000,10000,0)mm expects (4986.339746,7003.660254,100)m; BM1 local (0,0,2000)mm expects (5000,7000,102)m. Retain north/inverse checks and declared uncertainty. For this arithmetic fixture only REQ- uses horizontal residual<=0.002 m and vertical<=0.001 m with assumed combined uncertainty<=0.0005 m; actual survey accuracy/criteria must be sourced separately. Actual native/receiver residuals are unmeasured. A coincident screen overlay or attractive north arrow cannot replace these tests.

5 Frozen manifests and intelligible receiving package#

Freeze FederationID/ExchangeID/revision, intended use, required coverage, all source/native/export/dependency hashes, source share decisions, transform/units, full authoring/export/coordination/receiving builds and presets, issue/rule configuration and result evidence. Include a human-readable readme with scope, identity/code/phase/axis/unit legends, load order, reference paths, known exclusions, contact functions and acceptance procedure. Package source variants, agreed self-contained review derivative, coordinates/control record, properties/identity crosswalk and issue register/evidence as required by the selected use. A review NWD or similar derivative alone does not prove editable native or semantic IFC receipt. The manifest also lists one IFC validation report per IFC file (buildingSMART IFC Validation Service, schema and specification conformance) and the IDS check report with checker and version (check sequence per BBM-STD-89 §5). Where the receiver supports it, the package may be an ISO 21597-1/-2:2020 ICDD container carrying the linked models, CRS record and issue register; otherwise use the folder and readme specified here.

Use portable bundle-relative paths such as Models/<exact-container>.rvt and Exports/<exact-container>.ifc; verify all required dependencies, textures and permissions with the original live/author machine paths unavailable. Remote/cloud references need an explicitly supported receiving access route, immutable version reference and actual authorised/denied access evidence; do not assume a pasted URL is a portable package. Apply Manual §9.4 sensitivity and aggregation review to the recipient scope, retaining required design information through an authorised route. A manifest lists its contents; compute its own digest in the external transmittal/receipt rather than recursively hashing itself.

Receiver opens the frozen package in the named full build, checks required sources/coverage and source hashes, no missing or doubled nested references, controls/north/units, boundary objects, identities/properties and agreed issue/viewpoint interpretation. Record actual source/export/receiver values and screenshots/reports, operator/date and scoped acceptance. Re-extracting objects from the sender's live path is not receiving proof. Unsupported formats or missing mandatory fields hold acceptance until a qualified complementary profile or approved requirement change resolves the gap.

6 Fixtures rejection and release#

The workbook Scope, Sources, Links, Boundaries, Controls, Manifest, Tests and Acceptance provide the federation matrix, reusable blanks and populated synthetic fixture. Native RVT/IFC/review bundles are specifications awaiting execution. Tests independently omit MEP64, apply source units/transform twice, allow the nested structural source twice, clone an object at the handoff, substitute R02 into an R01 manifest and remove a required relative dependency. Expected failures and corrected independent retests are recorded separately with actual hashes/builds and measurements to be supplied.

Run alignment/identity/boundary checks before the approved BBM-STD-50 clash tests. Declare complete coverage only for the stated accepted scope, with no hidden required model or mandatory gap. Producer/source QC, independent coordination/coordinate review, discipline design approvals, delegated submission authorisation and recipient scoped acceptance remain separate. Retain a compatible complete baseline and rehearse reopening/rechecking controls on rollback; changes propagate to EIR/LOIN/BEP/TIDP/MIDP and affected recipients. A good script result, source file presence or a green clash count cannot certify a federation. Actual native setup, clash execution, receiver acceptance and office/authority adoption are Not executed by this editorial pack.

References#