Connect BIM objects to project costs without losing revision history

Identify the model, authoring source, agreed exchange format and version, project, discipline and intended workflow. A model used for coordination may not contain the information or measurement basis required for procurement or commercial assessment. State which purpose the integration supports.

Record the relevant object identifiers alongside model and revision identity. buildingSMART's published IFC4 ADD2 TC1 IfcRoot definition includes GlobalId and optional OwnerHistory. It illustrates the difference between an object's identifier and other history information. Use the actual schema and implementation agreement for your project; a GUID alone is not a complete revision audit.

Agree what happens when an authoring or export process changes identifiers. A new identifier may represent replaced geometry, a split object or an export behaviour rather than wholly new physical scope. Do not let the connector decide that distinction from the identifier alone.

In this fictional example, Revision A contains one object with a proposed measured length of 100 metres. Revision B replaces it with three objects measuring 40, 35 and 25 metres on the same stated basis. Their total is still 100 metres.

The mapping review records the one-to-three relationship and supersedes the old link for the new revision. If the connector retains the old 100 metres and adds the new 100 metres, it reports 200 metres and double-counts the same proposed scope. Keep the original revision's mapping for historical reports while preventing it from contributing again to the current revision.

Now suppose a later reviewed model proposes 40, 35 and 30 metres. The new total is 105 metres, a five-metre proposed change from the earlier basis. The quantity surveyor still needs to assess the measurement rules, scope and commercial treatment. A changed model quantity is not automatically an approved variation or certified bill.

Connect the project and model revision to object identity, classification, BOQ or work-package reference, cost code, unit and relevant scope. One object may relate to several commercial items, while several objects may contribute to one item. Record those relationships rather than forcing a single lookup column to do every job.

Avoid counting both an assembly and its included components unless the agreed measurement basis requires that treatment. Record whether quantities are net, gross, estimated or derived under a specified method. The BIM and commercial owners should approve the definitions before a report combines values.

For unmapped objects, retain their count and relevant quantity in an exceptions view. Do not drop them from coverage reporting. A report can legitimately exclude unresolved quantities from a commercial proposal while still explaining how much source scope remains unreviewed.

buildingSMART's BCF introduction describes exchanging model-linked issues and topics, including references to elements and viewpoints. That is different from transferring the complete model and establishing its quantities or commercial acceptance.

A coordination issue marked closed may show that a particular discussion was resolved. It does not necessarily approve a model revision for every purpose or authorise the corresponding ERP transaction. Preserve the relevant review statuses and their scopes instead of translating every closed issue into an accepted quantity.

The integration can link an issue or technical decision to affected mappings. When the model changes, the responsible owner can then assess whether earlier decisions remain applicable. Keep that assessment explicit rather than carrying approval forward because the object name looks familiar.

A native connector may be effective when the systems share suitable definitions and support the required revision handling. A mapping layer can provide clearer staging, transformations and exception review when identities or commercial structures differ. A controlled reviewed import may be enough for a small, infrequent exchange.

Compare these approaches using the same split-object example. Ask where mappings are approved, how units are checked, how historical revisions are retained and what happens when a source object disappears. Include licensing, API access, source-version support and ongoing ownership in the decision.

Start with read-only source access and a staging output where practical. The connector should propose associations for review before writing consequential ERP records. Automatic purchase, budget or billing actions require their own scope, authority and recovery controls; they are not implied by a successful quantity import.

Use a small package with unchanged, added, deleted, split and renamed objects. Include a changed unit, a remapped cost code and a repeated or interrupted import. Reconcile the source objects and quantities to mapped, excluded and unresolved records for each run.

Give every run a stable identity, source revision, mapping version and validation result. A retry should not create another copy of the same proposed quantity. If the mapping changes, preserve the earlier result and explain the replacement. The responsible reviewers need to distinguish a source change from an integration correction.

Stop the affected output if quantities cannot be reconciled or a mapping changes without the required review. Retain the last accepted snapshot with its actual date and use the agreed manual process while resolving the issue. Do not present a stale snapshot as a current model position.

The BIM lead validates object relationships, engineering confirms the relevant model basis, the quantity surveyor reviews commercial quantities and IT maintains the exchange. The master-data guide covers the related ownership and historical-identity decisions.

A successful evaluation lets another reviewer trace the 105-metre proposal through the three objects, source revision, mapping and approved measurement basis. It also shows why the old 100-metre object is not counted again. That is a useful integration outcome even before any transactional automation is considered.

1. Select one model package and define the intended quantity or cost decision.
2. Agree identifiers, versions, units, measurement basis and mapping ownership.
3. Reconcile a split, deletion, changed unit and repeated import in staging.
4. Authorise the reviewed output only when source coverage and historical relationships can be reproduced.