How does Bildstak join data across different systems?

The fundamental challenge of construction data federation is the join problem: a wall in the BIM model, a clash raised against it in BCF, the RFI it triggered in Procore, the cost line in SAP, and the Primavera activity that installs it are all described in different systems using different identifiers. Making them queryable together requires a stable key they all share.

For BIM projects — the IFC GlobalID: Every element in an IFC model carries a GlobalID, a stable 22-character identifier that does not change across revisions or tool migrations. Bildstak indexes the entire project by GlobalID. Any record in any connected system that references an element by its ID — a BCF topic, a Procore RFI, a COBie row, a cost line — is automatically joined to that element. The result is a queryable model where clicking a wall shows everything ever recorded about it across every system.

For non-BIM and heavy civil projects: When there is no BIM model, Bildstak joins on the identifiers those projects do use: Primavera P6 activity IDs (linking schedule to cost and documents), WBS codes (linking budget structure to actuals), cost codes (linking ERP lines to quantities), and document references (linking contract correspondence to programme events).

What this enables: - Cross-source questions that would previously require manual reconciliation by an analyst. - The Element Inspector: every linked record for any selected model element. - Claims evidence chains: from a delay event through the RFI trail to programme impact to cost quantum. - Portfolio comparisons: cost codes and WBS hierarchies made consistent across projects.