IFC model health report

Introduction

Before you share an IFC model, you need to know whether it holds together: spatial structure, identifiers, units, properties, positioning. SeveUp App answers that question in three places. The "Health" tab of a model's page gives a report of generic checks, with no IDS requirement. The "Dashboard" tab summarizes what the revision contains. A Folder's "Models" tab compares each model's base point, levels and grid with the values expected in the setup.

All three views follow the version chosen in the "Displayed version" selector of the model page: the latest revision by default.

IFC health report

The health report runs 49 generic checks on every revision, grouped into 10 categories: "File and units", "Spatial structure", "Element containment", "Identity", "Typing", "Placement and georeferencing", "Properties and quantities", "Materials", "Spaces" and "Systems and groups". Examples include "Unique GlobalIds", "No orphan element", "Consistent storey elevations", "IsExternal and LoadBearing filled in" and "Material assigned to built elements".

To open it:

1. Open the model from the library.
2. Click the Health tab.
3. If needed, pick another revision in "Displayed version".

There is nothing to start. The check runs by itself a few minutes after the model is processed; for an older revision, it runs during the following night. While it runs, the message "Check in progress" is shown and the page updates by itself.

At the top of the report, chips show the IFC schema, the declared model view (MVD), the inferred discipline and the date of the check. An organization administrator can ask for a new run with Run the check again.

Read the score and categories

The gauge shows the health score: the share of applicable checks that pass. A "Not applicable" check is left out of the calculation: it is never counted as "0 issues". The color follows three thresholds: 90% or more, the model is healthy; from 75% to 90%, keep an eye on it; below that, it needs fixing.

Next to the gauge, the heading gives the conclusion. Errors come first, for example "3 errors to fix before release", then warnings. Four tiles count the "Errors", the "Warnings", the "Passed" checks and the model's "Elements", with its number of storeys.

• The "Check breakdown" tile shows the statuses as a ring.
• The "Where the defects are" tile ranks the categories, the most affected first. Click a category to filter the list; Clear filter removes it.
• The "Checks" list first shows defects only. Untick "Issues only" to see everything, or use See all checks.

Each check carries a "normative" badge when it relies on a buildingSMART rule, or "convention" for a good practice. An error means a normative rule is not met, a warning means a convention is not followed. Expand a row to see its source, the details and a preview of the objects involved. For each object, Copy copies its GlobalId, name and class, and View in 3D opens the viewer on that object.

Base point, level and grid checks

A model can be healthy on its own and still be misplaced against the others. This check compares each model of a Folder with the values expected in its setup. It requires a filled-in setup: see Configure a Folder's BIM setup.

1. Open the Folder, then the Models tab.
2. Read the "Base point", "Level" and "Grid" columns. They are shown on a wide screen.
3. Click an underlined value to open the details.

A green dot means a match, orange means partial, red means a gap. With no dot, nothing could be compared: the setup does not define the value, or the revision has not been processed yet.

• Base point: only the X, Y and Z axes defined in the setup are compared, using the setup tolerance (1 cm when none is set). The details show, axis by axis, the "Expected" and "Actual" values. "Local coordinates" means the model sits at the origin and is not georeferenced.
• Levels: each expected level is found by its name, ignoring case, then its elevation is compared according to the mode chosen in the setup. Extra levels are not penalized.
• Grid: the column only appears when the Folder has a reference model. Axes are compared with those of the reference. The details give the "Estimated shift", the "Max. offset at axis end", the "Max. rotation" and the state of each axis: matches, out of tolerance, missing from the model or not in the reference.

In a federated 3D view, the viewer also flags a model that sits away from the others and gives its X, Y and Z offset.

Model dashboard

The Dashboard tab of a model's page summarizes the displayed revision.

• Indicators: the number of "Objects", with the schema, file size and upload date, then the "Spaces", "Storeys" and "Properties".
• Breakdown: "Breakdown by IFC class" and "Elements per storey", as bars.
• Quantities (QTO): "Areas" and "Volumes", summed by quantity name and kept apart by unit, never mixed.
• Data health: the share of "Classified objects", the "Properties per object (avg.)" and the number of proxies (BuildingElementProxy).
• IDS compliance: the score of the IDS requirements checked against the revision, failures first.
• Data completeness: the share of "Objects with properties", "Named objects" and "Classified objects", then the "PSet coverage by class", which gives, for each IFC class, the percentage of objects carrying each Pset.

What can go wrong

• "Model too large for automatic checking (over 600 MB)." No health report is computed for these files. The other tabs remain available.
• "The IFC file could not be read (truncated or invalid file)." Export the model again from your authoring software, then upload a new revision.
• "Technical incident during the check": a new attempt starts automatically within a few hours.
• The Dashboard shows "Building data for this revision…" Processing is not finished. Come back in a few minutes.
• No "Grid" column: the Folder has no reference model in its setup.

FAQ

Does the health report need an IDS file?

No. The checks in the "Health" tab are generic and apply to any IFC model. Compliance with IDS requirements is shown separately, in the Dashboard and in the "IDS %" column.

Why are some checks marked Not applicable?

The model does not contain what the check looks at, for example no space or no grid. These checks are left out of the score.

Who can run a check again?

An organization administrator, with the "Run the check again" button. The new check starts within a minute.

Does the base point check work without a setup?

No. Without an expected value, the "Base point" column only shows the coordinates read from the file, with no conformity dot.