Model Comparison in SMC v9.8

NOTE: The following article contains much of the same content as in the articles Model Comparison – Sol/206 and New in SMC v9.7.15 Model Comparison Improvements but is updated with screenshots of the new interface of Solibri Model Checker (SMC) v9.8. If you are running an earlier version of SMC, please refer to the previously published article(s).



Solibri Model Checker (SMC) has a very powerful rule template named Model Comparison (Rule Template # SOL/206) that is able to compare two versions of an IFC model for differences. This rule template is used in the Model Revisions Comparison – Architecture ruleset found in the Architectural folder of the rulesets included with SMC.

You are able to find information for this rule in the help topics by following the link below to the Solibri Solution Center:

The following article will provide an additional explanation using the Model Revisions Comparison – Architecture ruleset and two versions of the SMC Building sample models that come with SMC.

First, open SMC v9.8 and set your role to BIM Validation – Architectural by clicking File > Roles > Open. By using this role, when you click the Add Rulesets button in the Checking View, the Model Revisions Comparison – Architectural ruleset will be listed in the dialog box that opens, with the default rulesets included in this role.


NOTE: The Model Revisions Comparison – Architectural ruleset will not be loaded automatically when you open an IFC since it is not “Starred.”  If you wish to have the ruleset automatically open in the Checking view, you must “Star” its listing in the Roles window and resave the role (see above).

Now that your role is set, click File > Open Model… and open SMC Building.ifc and SMC Building – modified.ifc found in the Samples\IFC folder. After the IFC models load, leave the Ensure Model Disciplines dialog as it is with both models set to Architectural and click the OK button.

NOTE: The Model Comparison rule template is for comparing IFC models, not SMC models. Solibri Model Checker is unable to load multiple .smc files at the same time.

With the two versions of the same IFC model loaded, you can now open the Model Revisions Comparison – Architecture ruleset.  Select the Checking layout tab at the top of the SMC window, and you’ll notice that the BIM Validation – ArchitecturalGeneral Space Check, and Intersections Between Architectural Components rulesets have already loaded by default using the role you previously selected. If the To-Do dialog opens, you can simply click the X button in the top right corner, as you won’t need to verify any of these tasks to ensure the results are accurate.

Click the OPEN_RULESET_FOR_EDITING Add Rulesets button to add the Model Revisions Comparison – Architectural ruleset.


If you want, you can right-click the other three rulesets listed in the Checking view and select Disable to save time by not running those checks.

Click the Check button in the Checking view and select the Component Comparison rule under the Model Revision Comparison – Architectural ruleset to view its results in the Results view. You may notice a result stating Incorrect Model Timestamps (see below), warning that the Old Model set in the Rule Parameters does not have an earlier Timestamp than the New Model. This is due to the modified IFC being saved prior to the original model. It is important to point this out since with the Old Model and New Model set incorrectly, the rule will incorrectly report components as being added that were actually removed and vice versa.


You can ignore the Incorrect Model Timestamps issue as it is a non-issue

To view the rule’s parameters right-click the rule in the Checking view and select Rule Parameters.  At the top of the Parameters Dialog Bow (see below) you’ll find drop-down boxes for the Old Model and New Model. Set the Old Model drop-down box to SMC Building and the New Model drop-down box to SMC Building – modified (see below).

Notice next to the drop-down boxes, you can set the colors for the Old Model and New Model. By default, the Old Model is set to a red color with 60% transparency and the New Model is set to a blue color with 60% transparency. Therefore, if a component was removed, it will show up as Red, since it only existed in the Old Model. If a component is added, it will show up as blue as it only exists in the New Model. If a component is modified, it exists in both the Old Model and New Model. If the modified component moved to a new location, you’ll see the component in two different locations: one as red and one as blue. However, if only a property was modified for a component, the component will reside in the same location in both the Old Model and New Model, in purple, caused by the overlapping colors of the components.

Below the old and new model drop-down boxes is a checkbox labeled “Identify components only with GUID.”  When marked, SMC ignores the geometry of a component in determining if it was added/removed in the model and relies only on the GUID of the component. For example, if you delete a component in the design application and replace it with a new component, the GUID of the new component will differ from that in the old model.  With the checkbox marked, there will be an “Added” result for the component in the new model and a “Removed” result for the component in the old model.  However, if you leave the checkbox unmarked, SMC will return a “Modified” result for the component stating what has changed (e.g. Geometry, Type, etc.)

Next, you’ll notice under Checked Components, we are checking Any components from an Architectural Model, but Excluding Openings and Spaces. These are excluded since spaces will be checked on their own in the Space Comparison rule and openings are normally created by doors or windows, which will already be compared.

NOTE: By setting the Component column under Checked Components to Any, only components that have geometry will be checked. This doesn’t include container components such as Buildings, Floors, Systems, etc. If you wish to compare container components, you’ll have to add a row to the filter to Include those individual container components as well.

Below the Checked components, is a checkbox labeled “Geometries”. When marked, a result is returned for any component that has had its actual geometry (what you see in the 3D View) modified.

Below that checkbox is the “Compared Properties” list.  Here you can add any property you wish to compare across versions of a model. To add a property, click the ADD_ROW Insert Property button.  A dialog window will open and allow you to select from a one of the property groups.


Lastly, Model Comparison is one of the rule templates in SMC that has a configurable report. The Report section of the Parameters dialog (see above) allows a user to customize what columns are included in the report. The table on the left allows a user to specify which classifying columns to report and their order. These are the left-most columns of the report that will sort the components in the report by their column values. The table on the right in the Report section of the Parameters dialog (see above) allows a user to specify what components and which of their quantity and location properties to report. For example, in the report of this rule, components will first be grouped and sorted by the floor they are located on, then by the component (Door, Wall, etc) they are, and then by their Type. You’ll also notice that Roofs, Slabs, Walls, and Suspended Ceilings will have their Areas reported, though not their Lengths. Only Beams and Columns will have their Lengths reported, but not their Areas.

Set the Old Model and New Model drop-down boxes to SMC Building and SMC Building – modified respectively in the Rule Parameters of the Space Comparison rule in the Checking view as you did for the Component Comparison rule.  Now that the Rule Parameters are better understood and correctly set, click Check in the Checking view to re-run the check.

In the Results view, notice there are three categories of results listed: AddedRemoved, and Modified. Double-click and expand the Added category to zoom to the components that were added in the modified model.


You’ll see that a door, a suspended ceiling, and a wall have been added to the modified model. Again, as these are components that only exist in the New Model, they show in the 3D view as blue.

In the Results view, if you expand the Modified category, scroll to and double-click the result “Wall.0.16 – Wall.0.17,” you’ll see that one of the walls in the New Model was moved and had an opening cut out of it for the door that was added:


You can see that it moved in the 3D view as it is shown in two locations: in red from the Old Model, and in blue from the New Model. Notice the sub-category states “Wall: Geometry, Location, Quantity”.  The results are organized first by what the component is that has changed and then by what has changed about that component.  The Geometry has changed since an opening was cut out of the geometry of the wall for the door that was added. The Location properties have changed since the wall itself has shifted locations. The Quantity properties have changed since the area of the wall is now smaller due to the opening that was cut out of it.

Also notice that when you select the result in the Results view, you see a detailed listing in the Info view of all the properties and their values that have changed.

In the Results view, expand the Removed category until you find the “Double Sash Window 16” result of a window that was removed from the model.  You can see that the window was removed in the modified model as the window only appears red in one location (where the modified wall was later moved to) from the Old Model.


Double-click the REPORT_BUTTON Report icon in the Checking view to open the report of the results of the Component Comparison rule.


You’ll see changes that have been made to components, which are sorted first by the floor that they are located on, then by what component they are, and then by their Type.


For example, when viewing this report we see that 2 Door components of Type Door 16 have been added to the Ground floor level in the modified model.  We can also see that 15.07 sq ft of Wall of Type EW-3 100 have been removed from the Roof level in the modified model; however, 36.06 sq ft of Slab of Type FS-2 200 has been added.

Model Comparison in SMC v9.8

License Error: Associated Version Number (9.7) is Smaller Than Required Version Number (9.8)

If you try registering Solibri Model Checker (SMC) v9.8 and find the following error, it is due to only having a version 9.7 license assigned but not the required 9.8 license:


To resolve the issue:

  1. Log into as an admin user.
  2. Select the License Assignment tab.
  3. Leave the Product radio button marked, and select Solibri Model Checker.
  4. In the version list, select 9.8 and click Refresh.
  5. Mark the checkbox for the users that will be running version 9.8 of SMC.
  6. Click Save Changes.


Those users should then be able to run version 9.8 of SMC.

The info column lists the versions of SMC licenses that are assigned to a user.  Above, you see that the user is only assigned version 9.7, which explains why this user receives the error message.  Also, note has 9.7 and 9.8 licenses assigned and some users have only a 9.8 license assigned.  Since version 9.8 is the latest version, users having only a 9.8 license are still able to run version 9.7 and earlier of SMC regardless of not having those license versions assigned.


License Error: Associated Version Number (9.7) is Smaller Than Required Version Number (9.8)

Creating an SMC Template

The following article provides some simple steps to create an SMC template.  This allows you to save only the model resources (classifications, rules, ITO definitions) along with a basic origin designator as a model.  This can be used as an alternative to creating a role, or anytime you would like to duplicate current conditions of a model without including the model geometry.

For this example, open the SMC Building.smc file that comes with SMC in the examples folder.  In a real-world situation, this would be one of your existing SMC projects that has the same resources you wish to use on a new project.

Notice this SMC file contains the listing of classifications that you would like to include in the template.

We also want to use the same loaded rulesets that currently have results based on the SMC Building model from another project.

Select File > Add, then add the origin model from the link below:

Origin Marker.ifc

An IFC file is required to be present in the Model Tree in order to save an SMC along with its contained resources.  We will delete the existing model from the old project to save space and remove old information…this origin marker will remain and will provide a visual aid to where 0,0,0 is in the model.

To remove the old model, right-click it in the model tree and select Remove from Model.

Notice the results have been removed from the Checking view.

If you created Selection sets in the Selection basket view, you can delete these by right-clicking in the window, selecting the selection set you wish to delete and click Delete in the dropdown.

Click the Communication layout and remove the existing issue slides from the old project by right-clicking them in the Presentation view and selecting remove Presentations.

Click the Information Takeoff layout.  In the Information Takeoff view, the existing data of the old project from the last time takeoff was run exists.  Click the Takeoff dropdown and select Takeoff All ITOs to remove the old information.

With the file stripped of old project information, click File > Save As and save to a new Template file.

Now, you can add whatever new IFC models you would like as the project progresses, or send this template to a colleague running SMC without having to share the original classifications, rulesets, and ITOs independently.  Saving a project template can make sharing project parameters and checking requirements for SMC much easier by keeping these resources contained in a single Template file.

Creating an SMC Template

Missing Components When Exporting Elements Only Visible in View Within Revit

The IFC Exporter in Revit allows you to export only elements that are currently visible in the view.  You can use this option to isolate only the elements you wish to export rather than the entire project.

However, some elements, even though visible in the view, may fail to export in the IFC if the Detail Level of the view is not set to “Fine.”  Below you can see the view with the Detail Level set to Medium.


The following is the resulting IFC loaded in Solibri Model Checker, which has missing pipe fittings in the model.



To work around the issue, ensure that when exporting only elements in the view, you have the Detail Level set to “Fine” as seen below.


The resulting file should no longer have missing elements as seen below where the pipe fittings are present.


Missing Components When Exporting Elements Only Visible in View Within Revit

Transferring your License to Another Machine

Solibri Model Checker makes it easy to transfer a license between your computers.  All that is required is to provide your Solibri Solution Center (SSC) username and password on the other machine when you start SMC. The SSC will register that new machine and unregister the old one.

Welcome to Solibri Model Checker Dialog

However, you are only able to register/run SMC on one computer at a time using your SSC username.  So if you close SMC on your office computer, you should be able to open SMC on your home computer and vice versa. If SMC is already open on another machine, or if you have borrowed a license, you will receive the following error when attempting to open SMC on another computer until SMC is closed or the borrowed license is returned respectively:

Information on borrowing and returning licenses can be found article Borrowing Licenses.

If you wish to run SMC on two machines concurrently, you will need to create two usernames in the SSC, assign licenses to both usernames and register those user names on each computer.  It is important to note that this will reduce your companies available floating licenses by two while both machines have SMC open.  Information on creating users and assigning licenses can be found in the article How to Easily and Efficiently Manage Your SMC Users and Licenses

Transferring your License to Another Machine

Silent Installation and Other Administrator Documentation

System Administrators are able to silently install Solibri Model Checker (SMC) and Solibri Model Viewer (SMV) remotely to the machines of users by running the installer in unattended mode.  This can be done by passing the -q command line argument to the installer.

This information is found in the “Documentation for SMC System Administrators.pdf” document for both PC and MAC users.

This document provides also other useful information outlined below in its table of contents:

  • Super User vs. End User
    • User Profile
    • Roles
    • Shared Resources
    • Specifying Common Layouts
      • Specifying a Video Page for Common Layouts
    • Tasks and Responsibilities of System Administrator
      • Silent Installation for Windows
      • Silent Installation for Mac Os X
      • Setting the User Profile and Shared Resources

You can find this document depending on your machine here:

For PC:

C:\Users\Public\SolibrI\[VERSION OF SOLIBRI SOFTWARE]\Documents\System Administrator

For Mac:

Applications > [VERSION OF SOLIBRI SOFTWARE]\Documents\System Administrator

Silent Installation and Other Administrator Documentation

Expanded Wildcard Search of Property Set Data

The wildcard can be used in various ways throughout Solibri Model Checker (SMC), allowing for more intelligent searching and sorting of components based on some common value. In previous versions of SMC, wildcards could not be used when searching or identifying information from Property Set data.   In the latest version (v9.7.15), this feature has been added so users can now perform extended wildcard queries on the Property Set information that is embedded in a model.

To illustrate this functionality in SMC, refer to the image below, where the “IsExternal” Property will typically reside within one of three Property Sets: Pset_WallCommon, Pset_DoorCommon, or Pset_WindowCommon.


In previous versions, three separate columns were needed for each individual Property Set, making the grouping functionality restricted to each individual component type. This also restricted the ability to “colorize” the components based on a single value (True or False, in this example), since the color scheme will be based on the values returned from each individual column and will then colorize the components based on their unique Property Sets and True/False value.


Now, the asterisk/wildcard is allowed. The three separated columns can therefore be deleted so only the combined “Pset_*Common” value be considered.  Regardless of which property set the True/False value resides in, the components can be grouped together. Users can colorize the components using the single, combined column of information, resulting in the True/False two-color scheme shown below.


Expanded Wildcard Search of Property Set Data