What does it mean to federate construction data?
To federate construction data means to query your project's separate systems — BIM, schedule, cost, RFIs, documents — as if they were one, without moving or copying anything. Bildstak federates those sources live, joining records by stable identifiers so every answer spans the full picture.
Federation is a query model: instead of extracting data out of all your systems and loading it into a central warehouse, you leave data where it lives and query across the sources simultaneously. The federation layer understands how to read each source and how to join records between them.
In construction, that matters because the tools teams use are intentionally specialised. Primavera P6 is built for scheduling, not for storing RFIs. Procore manages documents and RFIs, not cost ledgers. SAP holds costs, not geometry. No single tool should try to replace the others — but someone or something has to be able to answer questions that span all of them.
What federation means in practice: - Bildstak connects to each source in its native format or API — it reads IFC files, queries the Procore API, pulls Primavera XER exports, reads SAP cost journals. - Records are joined using stable identifiers: the IFC GlobalID for BIM elements, P6 activity IDs and WBS/cost codes for civil projects, document references for contracts. - A question like 'what is the cost exposure from overdue RFIs on this zone?' is answered by running against the joined model, not by asking someone to reconcile four exports. - Every answer cites the source records it used — so the result is auditable, not just convenient.
Federation also means your data does not have to move. Bildstak can query in-place, run in your own VPC, or operate fully air-gapped. The data stays yours.
Updated 2026-06-19