Methodology & Checks

Interoperability risk: what can go wrong when someone imports your file

Summary

An IFC file is handed over to be used somewhere else: in a contractor’s coordination tool, a GIS, an asset management system or the next designer’s software. It is only worth what arrives there. Interoperability risk is forensicBIM’s judgement of how likely it is that something goes wrong on that journey, and in particular of the things that go wrong without anyone noticing.

The report shows it as a traffic light, not as a score:

  • High risk: fix before import: at least one finding will make objects land in the wrong place, merge with each other, or not load.
  • Medium risk: import with care: no blockers, but some information is likely to drop out or arrive changed in some software.
  • Low risk: ready to import: nothing was found that breaks or drops out on import.

It sits on the Scores page next to the overall quality score and the Forensic BIM score™, and it answers a different question. Those two scores ask whether the data is rich and well organised enough to reuse. Interoperability risk asks whether what is in the file arrives at all, in the right place and unchanged.

Why it matters: losses you don’t see

Most problems that matter on import are not errors in the file. A file can be valid IFC and still lose the link to its maintenance manual because that manual sits on the author’s laptop, or lose a bearing whose shape the receiving software cannot rebuild. Passing the buildingSMART validation tells you the file follows the rules of the standard; it does not tell you that everything in it reaches the people who use it next.

These losses are silent. The import succeeds, the model looks complete in a viewer, and nobody misses the document link, the moved barrier or the merged pump until a work order, a survey or a cost estimate depends on it. By then the data has been copied into other systems and the team that made the model has moved on.

That is why the timing matters. At delivery, most of these problems are a re-export by the people who made the model. After acceptance, the owner pays for them: rework, quantities that end up in estimates, assets in the wrong place in a GIS, maintenance links that point nowhere. Data that cannot be imported reliably also cannot deliver the savings in operation that justify keeping it (see operate and maintain savings).

What the three levels mean and what to do

LightWhat it meansWhat to do
High risk: fix before importAt least one blocker: a finding that makes objects land in the wrong place, merge or not load.Don’t import the file into a system of record yet. Send the blockers to whoever delivered it; most are fixed with a corrected export. Upload the new file with Examine new file to confirm.
Medium risk: import with careNo blockers, but one or more warnings: information that some software drops or changes without saying so.Import, then check the listed items in the receiving software: are the documents there, do the flagged elements look right, are the quantities plausible? Ask for fixes in the next delivery.
Low risk: ready to importNo blockers and no warnings.Import as usual. Low risk says nothing breaks or drops out; whether the data is rich enough for your purpose is what the overall quality score tells you.

The light follows the weakest step. One blocker is enough for red, however good the rest of the file is, and one warning is enough for amber. Notes are there for information. Notes never change the light.

The four steps

The card What can go wrong when someone imports this file? at the bottom of the Scores page follows a file through four steps. Each step shows its blockers, warnings and notes, what passed, and a link to the page with the detail. Files without alignments have three steps.

1. Opens: will the file load in other software?

  • Blocker: parts of the file cannot be read (parse errors), including objects written with an entity the declared schema does not define (an IFC2X3 entity in an IFC4 file, for example) and references that point to such missing objects: readers skip them without an error, so they disappear unnoticed; the file structure is broken, for example shapes that are not linked to their elements; or the buildingSMART validation reports STEP syntax as invalid.
  • Warning: the file declares a pre-release IFC 4.3 schema identifier, such as IFC4X3 instead of the official IFC4X3_ADD2. Some software refuses or misreads these files. Or the buildingSMART validation reports the IFC schema, header syntax or prerequisites as invalid: most software still opens such a file, but some may refuse it or interpret parts of it differently.
  • Notes: the buildingSMART validation has not been run, so the step shows Passed · not confirmed; and IFC 4.3 files need software that supports IFC 4.3.

2. Lands in place: right size, right place, same identity?

  • Blocker: the file has no length unit, so other software has to guess between millimetres and metres, a factor of 1,000; or objects share a GlobalId, so other software merges or overwrites them (see GlobalIds and duplicates).
  • Warning: the file is not georeferenced, or is georeferenced to a template default location, a map conversion origin at 0, 0, or coordinates outside the area of its coordinate system (see georeferencing); or one file holds more than one site.
  • Note: only latitude and longitude, the most IFC2X3 can store: enough for a pin on a map, not for precise placement.

3. Follows the alignment: do objects placed along an alignment land where they should?

This step appears for IFC 4.3 files with alignments. Roads, railways and bridges are often modelled along an alignment: piers, barriers and signs are placed at a distance along it. If two segments of the alignment do not join up, objects placed by their distance along it can end up in a different place in software that rebuilds the alignment from its segments.

  • Blocker: a gap of 1 cm or more between two segments, in the horizontal layout, the vertical profile or the cant.
  • Warning: a gap between 5 mm and 1 cm, or an alignment that has design parameters but no geometry.

Smaller gaps are not reported here; the Alignment page lists every joint against a much tighter tolerance. In the bridge example report, Road under the bridge has six gaps between segments, the largest 31.4 cm, which is why that file is high risk. The alignment check explains the joints in detail.

4. Arrives complete: does everything come across, or does some of it drop out unnoticed?

Everything in this step is a warning, never a blocker, however many elements it affects. The rest of the model still arrives correctly, so the right response is to check these items after import, not to reject the file.

  • Document and library references: links from objects to manuals, certificates, drawings or product libraries. They are official IFC, but not every tool imports document and library references, so they are reported whenever a file has them, not only when a link is broken. Broken links, and links to local files on the author’s computer, never arrive at all.
  • Risky geometry: CSG, booleans and advanced B-reps, which some importers cannot rebuild. Those elements can arrive broken or not at all (see geometry types and import risks).
  • Over-detailed and heavy geometry: elements modelled in far more detail than needed, or more than 600 triangles per object on average. Importers may simplify, slow down on or skip them (see geometric weight).
  • Image textures: they often arrive without their image, and textures stored as a path on the author’s computer never do.
  • Quantities: values in the wrong unit, or more than 25% off the element’s own geometry. They import as if they were right, and go straight into cost estimates and maintenance budgets (see the quantity check).
  • Property relations without a property set: a link between objects and their properties that names no property set. The attribute is required, and many readers then fail on all property sets of the objects involved, so their data looks empty after import.
  • Notes: faceted B-reps or complex profiles, which usually import but are heavy; no quantities to compare with the geometry; and elements without geometry, which are invisible after import (element assemblies, whose parts carry the geometry, are not counted).

Where you see it in the report

PlaceWhat it shows
Scores page, top cardThe traffic light next to the two scores, the level, a short reason such as Gaps of up to 31.4 cm in 2 alignments., and a link to the four steps.
Scores page, card What can go wrong when someone imports this file?The number of blockers and warnings, a summary in plain words, and the four steps with every finding.
Geometry page, card Geometry interoperability riskThe elements with risky constructs and which construct each one uses.
Alignment pageEvery joint of every alignment, with the size of each gap.
Consistency page, card External referencesEvery document and library reference: reachable, broken or a local file, and which objects use it.
Markdown export for AI chat (Pro)The same four steps, in section 3.1.

How it relates to the scores

Interoperability risk is not part of the overall quality score or the Forensic BIM score™, and it is not an average. A file with an overall quality of 80 can still be high risk because of one alignment gap, and a simple geometry-only model with a low quality score can be low risk because everything in it arrives intact. Whether the data means something, and whether there is enough of it, stays with the scores.

How the light and the two scores fit together, and which one answers which question, is explained in Overall quality, Forensic BIM score™ and interoperability risk.

That is also why it is shown as a light and not as a third percentage: a percentage would average a broken alignment away against a hundred things that are fine. Several findings also lower a check score, for example duplicate GlobalIds, broken links and georeferencing, so fixing them often improves both.

Frequently asked questions

My file passes the buildingSMART validation. Why is it not low risk?

The validation checks that the file follows the rules of IFC. A link to a manual on the author’s laptop, or a bearing built from boolean operations, is valid IFC; the question is whether it arrives in the software of the next user. See Passing the buildingSMART validation is not the same as good data.

Why are document references a warning even when every link works?

Because not every tool imports them. The documents stay behind without a message, and whoever relies on them finds out later. After import, check that the links are there, or hand the documents over separately. As a result, a file with document or library references is at least medium risk.

Almost all elements have risky geometry. Why is that not a blocker?

Findings in Arrives complete stay warnings however large the share. The rest of the model still lands where it should, so the right step is to check the affected elements after import and ask for a better export, not to reject the file.

Does the light depend on the software I use?

No. It is the same for everyone and is based on what commonly goes wrong between IFC tools. Your software may handle a particular construct well; the light tells you what to check, not that your tool will fail.

Can I use it in my delivery requirements?

Yes. A simple rule such as “no blockers, and every warning explained by the supplier” is easy to check with Examine new file before you accept a delivery.