Extension Manager: Creating and Managing Your Own Company Extensions

Solibri Model Checker version 9.7 introduced a new tool to create, save, export and open company-specific extensions (Extension Manager) from the Rule Set Manager (RSM) view. This new capability makes it possible for more advanced SMC users to build and share company, location, or project-specific rulesets and extensions.

Additional information on the Extension Manager and company extensions can be found here: Extension Manager View

For pricing or other related inquiries, please contact sales@solibri.com.

As you become more familiar with the RSM and running checks in SMC, you’ll create your own specific rulesets based on a role or use case, such as accessibility checking or coordination.  If you have multiple users of SMC at your company, you’ll wish to share these roles, rules, and classification with those users while keeping these resources up-to-date on their machines when changes are made.  Company Extensions provide a simple method to package and store your own extensions in the Solibri Solution Center (SSC) that are available for users to install on their own machines.

In the following text, we’ll walk through creating our own company extension based on the “BIM Validation – Architectural ruleset”.


Open SMC v9.7.

Click File >  Roles > and click the Open button.

Select the “BIM Validation – Architectural.xml” role and click the Open button.

File > Roles > Open Role > BIM Validation - Architectural

By selecting this role, we’ve set the default resources in SMC to automatically load based on the BIM Validation – Architectural.xml role when opening an IFC.  This will also allow these resources to be loaded automatically in the Extension Manager view when creating the company extension. You can reset the interface to ask which role you wish to load upon opening an IFC by marking the “Show Role Selection” box under File > Settings > General.  For more information on roles and role selection, please see: Roles in Solibri Model Checker/

While in the File layout, click “Ruleset Manager.”

File > Ruleset Manager

Select “Extension Manager.”

File > Ruleset Manager > Extension Manager

In the “Account Extensions” view click the  New Company Account Extension button.

Account Extensions

A dialog box will open, asking whether or not you wish to include resources of role “BIM Validation – Architectural.xml”. Click the “Include” button to include the resources that are part of this role.

New Extension - BIM Validation

The “Extension Manager” view will now display the Roles, Rulesets, Information Takeoff Definitions, Classifications, and other templates that are part of the “BIM Validation – Architectural.xml” role.

Extension Manager

Notice the message “Some Links are Broken” at the top of the Extension Manager view.

There are icons to the left of listed resources that indicate whether or not those resources link to other files. A working link is indicated by a   working link icon, while a broken link is indicated by a  broken link icon.

The out-of-the-box General Space Check ruleset is missing a “Building Elements – Uniformat” classification referenced in one of its rules, which is indicated by a  broken link icon.

In the Classifications list, click the  Add Classification button.

Browse to the “Building Elements – Uniformat” classification and click the Open button.

Extension Manager - BIM Validation Fixed

The link to the “Building Elements -Uniformat” classification referenced in the “Space Validation” rule within the “General Space Check” ruleset is no longer broken now that the classification has been added.

In the Rulesets list, click the  Add Rulesets button.

Add the “Egress Analysis.cset” ruleset.

Again, notice the “Some Links are Broken” at the top of the Extension Manager view, along with the  Broken Link icon next to the newly added ruleset.  The Egress Analysis ruleset relies on the “Exits” and “Vertical Access” classification files to determine egress routes.

In the Classifications list, click the  Add Classification button, and add the “Exits” and “Vertical Access” classification files to resolve the issue of broken links.

In the Account Extensions view, click the  Export SRE as a JAR button and save your newly created Extension to your machine.  In this example, we saved the file named “My Extension.jar” to the desktop.

This extension is now able to be uploaded to your company’s Solibri Solution Center (SSC) account.

Login to your SSC account as an administrator at https://solution.solibri.com/

In the Administrator view, click the Company Extensions tab

Click the Add Company Extension button

Solibri Solution Center - Company Extensions

A window will open prompting you to browse to your extension, provide a short description, provide a custom logo, and version number.  Browse to the .jar file of the extension you created, provide a description and version number and click the Generate Extension button.

Add New Extension Window

A window will open stating that the extension will be processed and an email will be sent to your SSC email address once the extension is available.

When completed, you’ll see the extension listed under your company extensions in the SSC.

SSC - Company Extensions - My Extension

You can now assign your company extension to users in your company’s SSC account. Click the License Assignment Tab, select the Extensions radio button,

Click the License Assignment Tab, select the Extensions radio button, Select the newly added “My Extension” extension from the list and click the Refresh button.

Mark the users you wish to have access to your company extension.  For this example, ensure you mark your own user account so that the extension will be available in your install of SMC. Importantly, scroll down in the window and click the Assign button so that the update takes effect.


In SMC, click File > Solution Center.   You’ll find the “My Extension” extension you created available to install.  Click Install.

SMC - Solution Center

Close and reopen SMC.

Click File > Roles and click the Open Button.

Click the Resources tab, and you’ll find the role of your newly created company extension.  This role will include the resources of your company extension.

Open Role

In addition, if you click File > Settings > General and mark the “Show Role Selection” box, when you add a ruleset to a new project, the role of your company extension will be listed.  Notice in the screenshot below, the role BIM Validation – Architectural at the bottom.  This is the role of the company extension.  There is another “BIM Validation – Architecture” role listed above, which was the original role we modified to create our customized company extension from.

Please Choose a Role


Extension Manager: Creating and Managing Your Own Company Extensions

Space Group Containment – SOL/175

Solibri Model Checker (SMC) includes the rule template named Space Group Containment (Rule Template # SOL/175) that is able to check that specific space groups exist in your model and that those space groups contain the correct spaces and counts of those spaces. Since the list of required space groups and their required spaces varies from project to project, you must configure the rule parameters with your own values rather than using default values, as with some other rules in 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 SMC Building.ifc and the “Example Rules” role.  To open this role, select Roles under the File tab, click the Open button, and browse to the Example Rules role.


This role includes examples of all the rules templates in SMC.

After opening the SMC Buidling.ifc, switch to the Checking tab.  When you click to add a ruleset, a window opens that allows you to select rules from the Example Rules role. Please, select the #175 Space Group Containment.


Click the checking button to view the results of the check.

The first category of results listed is “Not enough spaces”.  This category occurs when a space group does not contain a required space.  You can see in the Info view, the Elevator space is not included in the Common Area space group.


Checking the rule parameters of the rule, we see all the required space groups and what spaces are required to be contained in those space groups.  Space Groups named Common Area must contain a single Elevator, Lobby, Stair, and Corridor space.


In the model, the Common Area space groups contain a single Lobby, Stair, and Corridor, but not the required Elevator space, which explains the result previously seen.

The second category of issues is listed as “Too many spaces.”  These issues occur when a space group contains additional spaces that aren’t listed in the requirements.  The Common Area 231 space group includes a Restroom, Gym, Kitchen, and two Corridors instead of a single Corridor, which explains the result and description in the Info view.


The last category of issues is “Inadequate Information.”  These results are listing space groups that were not listed in the requirements.  The requirements in the Rule only allow for space groups named Common Area, Education and Conference Area, Petty Education Inc., Arbor Doves, Inc., Tomorrows Lubrication, Inc. and Biochemical Startup, Inc..

Checking the Classification view, there are two types of Space Groups, Gross Area and Other.  Only the space groups from the Other type are listed in the requirements of the rule.


These results of additional space groups have a low severity denoted by the yellow warning icon, so you could approve their results as non-issues or you’ll need to fill in all the required spaces and their counts for the Gross area on each floor. Alternatively, you could remove gross areas from the classification rules of the Space Grouping classification.






Space Group Containment – SOL/175

Using the Space Validation rule to Ensure Model Accuracy

In Solibri Model Checker (SMC), there are many existing use cases around the idea of space checking.  To take advantage of the rules used for space checking requires correct modeling of spaces, and measuring of interferences or inaccuracies to ensure that results in SMC are correct.  Only when model spaces are detailed to the level that they are an accurate representation of the real world environment will the results of these use cases be valuable.

To ensure space requirements are modeled correctly, SMC uses several different rule templates.  One rule template, Space Validation, will identify several key space issues that are commonly found in AEC models.  These issues pertain to space components not being aligned with bounding surfaces such as walls or floors, as well as areas of a model that do not contain spaces at all.

Using the Space Validation template, you can ensure accuracy so various space checks can then be run, with confidence.

One example use case is if you are aggregating spaces to calculate areas, or total square feet, it would be important to verify that all spaces are correctly modeled to the real as-built square footage.  Any gaps in square footage, or where spaces are missing from the model, or where the space is actually overlapping with another component, will first be caught by the Space Validation rule.  This allows the designer to make the necessary corrections before proceeding with more complicated space checks.   In order to perform any sophisticated space checks, such as code-based checks like Egress Analysis, spaces must not be missing or inaccurate in the model, as that would probably have significant consequences.

Luckily, while this all may sound complicated, the Space Validation template is relatively simple to use, and it does all the hard work:



The acceptable gap or intersection between a bounding component and a space.  If the intersection or gap between a bounding component (walls, floors, ceiling, etc.) and space is more than the tolerance, an issue is created.

Acceptable error in space perimeter

The acceptable length of a space perimeter where the space is not touching any bounding component. If the perimeter segment length is greater than the entered value, an issue is created.

Required Space Height

The minimum acceptable space height. If the space height is less than the required value, an issue is created.

Check Top Surface

If checked, a slab or a roof or the bottom surface of another space has to touch the top surface of the space. Suspended ceilings are not always modeled, and in such a case, this option should be left unchecked.

Check Bottom Surface

If checked, the bottom surface of the space must be touching a slab or another space.

Intersection Components

‘Intersection Components’ are considered by the rule to be those components that shouldn’t generally intersect with spaces. If a space is intersecting with one of these component types an issue is generated and should be visually reviewed.

Check Unallocated Space

When checked, the unallocated spaces (any area that is not occupied by spaces, walls or columns) are checked and flagged as potential areas of the model that are missing modeled components. With very few exceptions, areas of the model should always contain a space or object modeled for an accurate BIM.

Maximum Allowed Unallocated Space

The allowance for interstitial areas between walls and/or utility closets is one exception to the above rule.  In such cases, you can enter a maximum allowed space size that can be ‘excluded’ from future space checks.  These ‘empty’ spaces are allowed by SMC because they can be ignored for the sake of checking things like square footage or egress analysis.  Space between walls should have no bearing on area calculations, just as utility closets should not affect occupancy loads or egress routes.

Result Categorization Method

You can categorize results either by spaces or by problem types. If you categorize results by spaces, each space creates one and only one issue. All problems related to that space are described within the issue. If you instead choose to categorize results by problem type, each individual problem type will appear as a category, regardless of which space they are occurring in.

Use Arrows in Visualization

When checked, arrows are added as a visual aid when reviewing the issues that are generated.

It is crucial when doing space checks in Solibri Model Checker that a model is first checked for accuracy and completeness.  The Space Validation template provides a first step in checking that the required detail has been modeled and should be considered an important element for any ruleset designed for space checking.  Without this first important step for space verification/validation, space checking results might not accurately reflect the real-world conditions of a building.

Using the Space Validation rule to Ensure Model Accuracy

Property Values Must Be from Agreed List – SOL/9

Solibri Model Checker (SMC) includes the rule template named Property Values Must Be from Agreed List (Rule Template # SOL/9) that is able to validate the values of specific properties of specific components based on your own project-based list. Since the list of agreed property values varies from project to project, you must configure the rule parameters with your own values rather than using default values, as with some other rules in 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 a slightly modified version of the SMC Building.smc sample project that comes with SMC, to verify that the names of rooms in a model follow the naming convention of an agreed list from an excel file.

SMC Building – Space Names Must be From Agreed List.smc

After opening the model, click the Information Takeoff Layout.  In the Information Takeoff view, you’ll see a takeoff of all rooms with their corresponding names and counts.  Notice there are 2 rooms named “Restroom” and 6 rooms named “Stair.”


Select the Checking Layout and expand the results of the Room Names Must be from Agreed List rule.  Notice that there are 2 result categories that group the Restroom and Stair spaces.


Right-click the rule in the Ruleset view, and select Rule Parameters to see the parameters of the rule. In the Components to Check filter parameters table, we are checking spaces, but excluding space groups such as Gross Area spaces, since those types of spaces won’t follow a naming convention as that of room names.

In the Allowed Properties Table, notice that there is no “Restroom” listed as an allowed value for the name of a space, as “Toilet” is listed as the agreed value. This explains the result stating that “Restroom” is not an allowed value for the name of a space.

Also, notice that “STAIR” is listed as an allowed value; however, the Case Sensitivity checkbox is marked.  This explains why “Stair” (which is not in all capital letters as in the list) is listed as a result, as well.


If you unmark the Case Sensitivity checkbox and re-run the check, you’ll see only “Restroom” remains as an issue in the Results view and rooms named “Stair” are now accepted.

In the Rule Parameters of the rule, you may have noticed that the row editing buttons row_editing are greyed out.  This is because the table data in the rule parameters is currently locked from editing.  This ensures that the rule is only using information that is consistent with your agreed list, which is imported from an excel sheet, external from SMC. If changes are made to the agreed list of values that the rule links to, you should update the information in the excel sheet and click the Update Imported Data button.

You are able to manually create rows rather than importing an excel sheet; however, importing an external sheet makes the parameter entry process much easier, less prone to introducing errors, and safeguards inconsistency from what SMC is checking, and what was agreed upon as allowed values.

Since the sheet isn’t stored locally on your machine in the same path, to update the table you’ll need to turn on table data editing, remove the existing content in the table, and import an updated sheet.

Click the Allow Table Data Editing allow_table_data_editing button, which will break the link to the excel file and enable the row editing buttons.

Click the Import Excel Worksheet import_excel_worksheet button.

Download the following excel sheet and browse to the file.

Room Names Must Be From Agreed List v2.xlsx

This first page of the import dialog allows you to map the Component, Property, and Acceptable Value parameters to specific columns in an excel sheet.  Since, the columns in the excel sheet were setup to match those same parameters respectively, you can click Next.


The next page of the dialog requires you to hold down the CTRL key and multi-select rows from the sheet. If you simply click Finish, nothing will be imported since nothing is selected.  Notice, the first row was not included in the selection as these values are column headers in the excel sheet.


After clicking Finish, the data table is updated with the values that match those within the model, and the Allowed Properties Values link is now pointing to the new version of the sheet:


If you re-run the check, you’ll find there are no issues, as all room names match those that are in the agreed list.

This is one simple example of this very versatile rule.  Another example worth mentioning and is included in the example rules folder that comes with SMC, is to check components against a list of approved construction types to find those that may have been accidentally introduced into your model that are outside your standardized approved libraries.

Property Values Must Be from Agreed List – SOL/9

What makes SMC Unique? The ability to check for Logic and Behavior

Solibri Model Checker (SMC) allows for simple, discrete, property checks of components and spaces, such as verifying that certain types of components and spaces have a specific property defined (e.g. Fire Rating) and the property is valid (e.g. 2-HR).  These simpler types of property checks are useful for validating information related to COBie, Level of Development (LOD), Quantity Takeoff, etc.  Likewise, you can check a model geometrically to ensure certain types of components or disciplines of models don’t have interference with one another, such as duct and pipe running into structural beams and columns, or a check for required clearances in front of windows or electrical panels.

However, SMC also allows for complex conditional checks that involve logic and behavior to verify that if a component or space has some property, condition, relationship, and/or behavior then that component or space must also pass certain other requirements. In short, knowing that specific information is required to accompany model elements is important, but being able to analyze the IMPACT of that information and how it can affect building performance is where the real value of SMC is established. In this article, we’ll describe how you are able to set up more complex checks in this way.

A Logical check: Plumbing above Electrical Rooms

In the first example, we will focus on a check to ensure that plumbing such as domestic cold or hot water and sewer does not run above electrical rooms, as this could cause serious issues if this plumbing leaks or bursts above spaces containing electrical components.

A logical statement to check against the model is: “IF a space is an electrical room THEN no plumbing system that is of type cold water domestic, hot water domestic, or sanitary should run above that space.”

In order to find spaces in the model that are electrical rooms, classification is used to map those spaces either by their name or some other distinguishing characteristic such as an OmniClass number. Below we see the mapping of any space that starts with “ELEC” to the classification “Electrical”:

Spaces with names that start with "ELEC" map to the Electrical classification
Spaces with names that start with “ELEC” map to the Electrical classification

To check if plumbing is of type Domestic Cold/Hot Water or Sanitary, we need to know what property set/property pair stores that information. Again, using classification allows us to map to that property location and set the Classification to the value of the property automatically.  Below, the “System Type” classification sets a classification name for any component base on the value of the “System Classification” property found under the property set “Mechanical”:

Mapping the System Classification to the value of the Mechinical.System Classification property
Mapping the System Classification to the value of the Mechanical.System Classification property

More information on classification can be found in the articles:

These classifications are used in the rule parameters of the SOL/222 – Component Distance rule template below:

 Plumbing must be a minimum distance of 5' above Electrical rooms
Plumbing must be a minimum distance of 5′ above Electrical rooms

This rule checks that any component that has a System Classification that is classified as Domestic Cold Water, Domestic Hot Water, or Sanitary has a minimum distance of 5′ above any space classified as “Electrical”.

After running a check on a model, there is a result in which a pipe on the Sanitary system is running 3″ inches above the space in the model.

An issue where Sanitary pipe is 3" above Electrical space
An issue where Sanitary pipe is 3″ above Electrical space

Another view shows that the pipe runs above the suspended ceiling across this electrical room that has electrical panels:

Another view of the result
Another view of the result

Advanced Logical Checks using Gatekeeper Rules

Rather than using the name of the space to determine if it is an electrical room, the SOL/225 – Number of Components in Space rule template could be used to return any spaces that contain electrical equipment as a result.  Using this as a Gatekeeper rule, the spaces returned as results are then fed to the sub-rule SOL/222 – Component Distance as the source component to ensure any plumbing has a minimum distance of 5′ above those spaces.

Gatekeeper rules also allow SMC to chain multiple conditions together.  Below is the example from the article Self-Configuring Rulesets: Gatekeeper Rules that checks that any space over 500 sq. ft. and that contains a boiler, incinerator, or furnace must have 2 exit doors.

Gatekeeper Rule with multiple chained sub-rules
Gatekeeper Rule with multiple chained sub-rules

The logical statement based on the chained gatekeeper rules and their results is:

IF a space is more than 500 sq. ft. and IF the space contains a boiler, incinerator, or a furnace THEN that space must reference 2 or more doors.

More information on Self-Configuring/Gatekeeper rules can be found here:


The behavior of door components for accessibility Checks

Door components have an operation property defined. This property defines the behavior of the door as to whether it is a sliding, folding, or swinging door. If it is a swinging door, the operation also states if the door swings left or right.  There is also a behavior on the part of a person opening the door, in terms of pulling or pushing the door open and whether the door is normally approached from the front, latch, or hinge based on their room.

The article, Enhanced in v9.6: Accessible Door Rule – SOL/208, provides a detailed look at modeling doors to have their behavior included and a ruleset can be used to check maneuvering clearance of accessible doors based on the logic of how the door is approached.

Below is a single-swing-right door that has the behavior of how it is approached from the push and pull sides included in the Data property set.  On the push side, it is approached from the front.  On the pull side, it is approached from the latch.

Door with a latch approach on the pull-side
Door with a latch approach on the pull-side

Again, a gatekeeper rule is used as a logical check to return any doors as results IF they have a latch approach on the pull side and IF they have a closer attached. Those door results are then passed to the sub-rule that checks for the clearance areas in front of the door, and past the latch based on that type of approach.

Below you can see a result where there is not enough clearance perpendicular to the door:

Latch Approach, Pull Side Result

What makes SMC Unique? The ability to check for Logic and Behavior

Setting up your basic Model Comparison Check

To conduct a quick model comparison in Solibri Model Checker (without customization), use the ruleset titled “Model Revisions Comparison.” Solibri Model Checker contains 3 version of this ruleset, one for Architectural, one for Structural, and one for MEP models.

To get started, a user must load two versions of the same IFC model, for example, the previous version first, and then the current version.  Do so by loading the previous IFC, and then “Add File” from the File tab to load the current IFC concurrently with the first.


Once both IFCs are loaded, go to the Checking tab.  Here, a window will appear asking which ruleset to use for this check.  Select “Model Revisions Comparison,” then select the “Check” button to run the comparison.


The results of this check are broken into two categories: Components and Spaces.  If there have been changes to the Components in a model, those changes will be listed under the Components rule.  If spaces have been changed, they will be under the Spaces rule.


Select the Component Comparison rule, and the Results window will display Added, Removed, and Modified components.


These results are displayed in real-time in the 3D window/model, and can be reviewed and then saved as a presentation.

Setting up your basic Model Comparison Check

Finding Precise Changes via Model Comparison

The previous article MODEL COMPARISON – SOL/206 provides a detailed introductory explanation on how to compare two versions of a model.  In this article, we focus on tips to partition model comparison checks into more granular pieces, namely results of what components have been added/removed and how they have been modified in terms of their identifiers, quantities, locations, and property sets.

You can follow along with this article using the example file available through the link below:

SMC Building – Model Comparisons.smc

The example linked above was modified using the same IFC files and ruleset from the previous “MODEL COMPARISON – SOL/206” article. The image below shows which rules have been added based on the specific type of comparison to be checked:

Modified Model Revisions Comparison Ruleset
Modified Model Revisions Comparison Ruleset

After running the check for the “Component Comparison” rule, then expanding those results, you’ll find Added and Removed components listed first as a category of results:

Component Comparison - Added/Removed Results
Component Comparison – Added/Removed Results

These Added and Removed results will always be listed if found, and if running checks for other properties, they are listed first before the category of what has been modified.  If you wish to only see what components have been added/removed, you can simply uncheck all Compare checkboxes in Rule Parameters of the Model Comparison rule.  You can see below in the rule parameters of Component Comparison – Only Added/Removed, all checkboxes have been unmarked and the results of the check no longer list any components that have been modified.

Component Comparison - Only Added/Removed
Component Comparison – Only Added/Removed

Next, we’ll look at the Modified results category and the Identifications checkbox parameter of the Model Comparison rule.

In the Results view, after selecting the “Component Comparison” rule, you’ll notice results with “Reported Property” listed last in the sub-category:

Component Comparison - Identification Results
Component Comparison – Identification Results

If you expand the result category “Door: Geometry, Location, Quantity, Reported Property [0/1]”, and select the result “(OLD) Door.0.11 – (NEW) Door.12”, you’ll see a listing of changes to the component in the Info view:

Component Comparison - Door Results and Info Views
Component Comparison – Door Results and Info Views

The last two listings in the Info view (highlighted in the image above) are properties from the Identification category, which was marked in the rule parameters. These Identification properties are the same as the properties listed in the Identification tab of the Info view after selecting a component. In this result, the single swing door in the old file was swapped out for a double door in the new file. This explains why the Type and Operation parameters are listed as being changed.  The other listings of changes pertain to the geometry, quantity properties, and location properties.  If you are only interested in the changes of Identification properties, you can leave only that checkbox marked in the rule parameters of the Model Comparison rule.

Component Comparison - Identification Results and Info View
Component Comparison – Identification – Results and Info View

Notice there are fewer results listed in the Results view to review and the information regarding the change to the door only pertains to identification properties.

Notice again that the Added and Removed categories are still listed in the Results view.  The Compare checkboxes in the rule parameter only determine what will be listed under the Modified category.  If a component is added or removed in the model, it will always be listed regardless of what checkboxes are marked.

When the geometry of a component has changed, it will likely cause a change in the location properties and quantity properties of the component as well.  Notice in the image titled “Component Comparison – Door Results and Info Views”, that the Global X property has changed.  Since the double door is now larger, its Global X location property has shifted along the wall.  Also, its Area, Width, and Frame Length quantity properties are larger as well.

The Location of an object can change without its geometry changing by simply moving it. In the image below, you can see the four sinks in the model were raised by 20 mm, though their geometry remains the same:

Component Comparison - Location Results and Info View
Component Comparison – Location Results and Info View

Lastly, you may wish to only monitor changes in a specific property or set of properties.  For example, many IFC components such as doors and walls have common properties such as Fire Rating.  These are found under a property set named Pset_DoorCommon and Pset_WallCommon respectively.

In the rule PSET Common Properties Comparison, the rule parameters have the Property Sets check box marked and the table is populated with all of the various common property sets in the Property Set Name column.  The Property Name column contains an asterisk to denote that any property found under the property set is to be checked for changes.

PSET Common Properties Comparision
PSET Common Properties Comparison

In the Results view, we see that the Pset_SpaceCommon.GrossPlannedArea property has changed of a space.

PSET Common Properties Comparision - Results and Info View
PSET Common Properties Comparision – Results and Info View

You can create a Model Comparison rule to check for changes of properties of a specific use for the model. In the screenshot below, the property sets table is populated to check only those properties that pertain to COBie information for changes :

Checking Property Sets for COBie Information
Checking Property Sets for COBie Information

More information on COBie and SMC can be found through the link below:



Finding Precise Changes via Model Comparison