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.

Advertisements
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.

Untitled

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.

Untitled2

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.

Untitled3

Expanded Wildcard Search of Property Set Data

New in SMC v9.7.15: Component Distance Improvements

In the latest version of Solibri Model Checker (SMC) v9.7.15, enhancements have been made to the Component Distance (SOL/222) rule template.  You can now set the top or bottom surfaces to check when checking for a distance above or below components.  Additionally, when checking distance above and below components, you can set a horizontal offset to the footprint of the source component rather than only checking if components are directly above or below.

The following article will provide a complete detailed explanation of this rule along with these new features. For additional information, please read the online help for this rule:

Component Distance_222 (SOL/222)

You can follow along with this article using the sample model that provides examples of each check through the link below:

Component Distance Examples.smc

The example consists of a model that has a pyramid-like object with several blocks in its vicinity along with rules that check for minimum distances between the pyramid and the blocks.  The following image provides a top, front, and top-front-right view of the model:

In the rule checks, the required minimum distance value is set to a large enough value to cause issues, which thereby provides a visual dimension line that shows how the distance is calculated of the violation.

Horizontal Distance Between Footprints

With the “Horizontal Distance Between Footprints” distance calculation, the distance between components that are next to one another is measured in 2D based on the footprint of the components.

Below, you see the two blocks alongside the pyramid fail the ruleset as they are within 15′ of the footprint of the pyramid.  The red circular visualization shows the area that is within 15′ of the footprint of the pyramid.

Shortest Distance Between Shapes

With the “Shortest Distance Between Shapes” distance calculation, the distance between components is measured in 3D based on the shortest distance between the components’ geometry.

Below you can see the dimension lines that show the shortest distance between the pyramid and the blocks that fail the check.

Facing within Distance

With the “Facing Within” distance calculation, the distance between components that are next to one another is measured in 2D based on the footprint of the components similar to the “Horizontal Distance Between Footprints” distance calculation.  However, only the space that resides in front of edges of the footprint is checked.

Below, you see that only one of the blocks alongside the pyramid fails the check.   Recall, in the “Horizontal Distance Between Footprints” check, there were two blocks that were within 15′ of the pyramid.  However, one of those blocks resides at the corner of the pyramid.  Since that block isn’t in front of the face of the pyramid, it doesn’t create an issue using the “Facing within Distance” distance calculation. The red visualization shows the area that is within 15′ of the faces of the footprint of the pyramid.

Horizontal Alongside

With the “Shortest Distance Between Shapes” distance calculation, the distance between components that are next to one another is measured in 2D.  However, the geometry of the components is used rather than the footprint to calculate the distance.

Below, you see the two blocks that are alongside the pyramid.  Notice the dimension lines showing how the distance is calculated extend to the surfaces of the pyramid.  Since the pyramid narrows at the top, these distances are further than those calculated using the footprint of the pyramid.

Directly Above / Directly Below

In version 9.7.15 of SMC, you can now set either top or bottom surfaces to check when checking for a distance above or below components. Below is an elevation view of two slabs that show how distances are calculated depending on the component surfaces distance calculation.

Below you can see the rule parameters for a check using the “Directly Above” distance calculation using “Top to Bottom” component surfaces.

The pyramid and block component that fail this check are transparent in the views that follow to allow the dimension lines to show through. Below the distance is measured from the top of the pyramid to the bottom of the block using “Top to Bottom” component surfaces setting.

Below the distance is measured from the bottom of the pyramid to the top of the block using “Bottom to Top” component surfaces setting

Below the distance is measured from the top of the pyramid to the top of the block using “Top to Top” component surfaces setting

Below the distance is measured from the bottom of the pyramid to the bottom of the block using “Bottom to bottom” component surfaces setting

Above / and Below within Offset Footprint

New in version 9.7.15 of SMC, when checking distance above and below components, you can set a horizontal offset to the footprint of the source component rather than only checking if components are directly above or below.  For example, there is a required distance a heater should reside below a window. The window is inside the wall, while the heater is attached outside the wall.  Since they aren’t directly above/below one another, you’ll need to specify a horizontal offset.

Below, in the rule parameters, we’ve set the horizontal footprint offset to 15′ for the “Above within Offset Footprint” distance calculations.

Below the distance is measured from the top of the pyramid to the bottom of the block using “Top to Bottom” component surfaces setting. Notice the red visualization of the 15′ footprint offset.  Notice even though the block to the left of the pyramid isn’t directly above it, because it is within the 15′ footprint offset, it fails the check.

Below the distance is measured from the bottom of the pyramid to the top of the block using “Bottom to Top” component surfaces setting. Notice the red visualization of the 15′ footprint offset is now at the base of the pyramid due to the “Bottom to Top” component surface setting.  Notice the two additional blocks alongside the pyramid fail the check due to the 15′ footprint offset is now checked from the bottom of the pyramid.

Below the distance is measured from the top of the pyramid to the top of the block using “Top to Top ” component surfaces setting.  Notice the 15′ footprint offset is at the top of the pyramid so only two blocks above the top of the pyramid are returned.

Below the distance is measured from the bottom of the pyramid to the bottom of the block using “Bottom to Bottom” component surfaces setting.  Again, with the footprint offset being set to the bottom of the pyramid all 4 blocks that are above the base of the pyramid fail the check.

New in SMC v9.7.15: Component Distance Improvements

Overview of New Features of SMC 9.7

Solibri announced Version 9.7 of the Solibri Model Checker (SMC) on August 31st. While this is considered a ‘point release’, there are quite a few enhancements and new capabilities. These capabilities are particularly relevant in the coordination workflow, but are also reflected in multiple layouts throughout the program. Many of the new features support the handling and reporting of issues that are identified via numerous checks. V9.7 adds a lot of capability, without necessarily adding complexity, which means YOU can begin benefitting from these new features, right away. This article will address the following new items:

  • Updated Issue Handling
  • A New View – Issues
  • A New View – Issue Sorter
  • Issue Details
  • Updated 3D View Options
  • SMC Relations
  • Federated Floors
  • Custom Relations
  • Company Extensions
  • Information Takeoff

Updated Issue Handling

The Communication Layout has been reorganized to accommodate the new issue handling enhancements, related to presentations, as described below:

A new view: Issues –A listing of titles of issues provides an easy reference for associating an issue to a particular slide within the presentation. The listing also provides additional relevant information, including status and the responsible party, if known.
uc_01

A new view: Issue Sorter – All issues in the selected presentations are now shown as thumbnails.  In SMC9.7, thumbnails of issues have been moved from the sidebar in the Presentation view to the new ‘Issue Sorter’ view beneath the 3D window.

uc_01_02

The size of the thumbnail pictures displayed in the Issue Sorter view can be changed on the Presentation Tab in SMC Settings.
uc_01_03

Issue Details dialog is now a view – In SMC9.7, the Issue Details popup window has been integrated into the UI as a fixed window. This will allow you to streamline the process of managing issues while increasing visibility into issue details. The result will be significant time-savings, and a smoother process.
uc_01_04

New UI/UX for responsibility values.  Responsible parties are now represented as ‘buttons’, allowing you to quickly assign issues to trades, entities, or individuals, as desired. You can easily add new options, as needed.
uc_01_05

Updated 3D View options.  The bottom of the 3D view in the Communication Tab has been enhanced to allow real time commenting by a user, as well as the ability to add, update, or remove saved viewpoints.
uc_01_07

SMC Relations

v9.7 introduces a new SMC defined relationship: Federated Floors. The relationship between components in different models is generated automatically, allowing for a fast, and extremely efficient way to visualize all components (from multiple IFC files) by the floors defined in architectural models.  The result is a very logical way to manage coordination by location, as you can filter all disciplines by floor, rather than in the entire building, if desired. All components of a specific floor will be joined together under a single ‘Federated Floor’ for easy reference, visualization, and coordination.
uc_01_08a

SMC V9.7 also introduces a new view to see and modify Nearest Spaces and Federated Floor relations – Custom Relations. Nearest Space and Federated Floor of components can be changed using the custom relations view.  This allows you to establish a custom set of relations, or to move any misplaced components onto the correct Federated Floor.
uc_01_09

Custom relations are shown in the Info View -> Relations tab in normal font. Other relations (from IFC files) are shown in Italics
uc_01_10

Custom Relations pop up menu: While viewing the Relations tab, if you select Federated Floors or Nearest Space, you can right-click to open the Custom Relations View for editing.
uc_01_11

Federated floors can be used in ITO templates and in the rule template #231. The Federated Floors property can be used to separate rows of information in ITO, and can be used as a limiter to only designate components of a specific federated floor to be checked.uc_01_13uc_01_12

There is also a new hierarchy in the Model Tree View – Federated floors.  This allows for quick selection of Federated floors by selecting an icon from the model tree.
uc_01_08

Federated floors are also used in the floor list of the Navigation map (you can select a floor from the list in the top of the Navigation map – the list now only includes Federated floors)
uc_01_14

Company Extensions

V9.7 also introduces 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 (or extensions).
uc_01_15

The result is a company-specific package that can be uploaded to the Solibri Solution Center, where it can be used as a custom company extension.  By doing so, all users in a company can start SMC as the same Role, using the same extension, and therefore operate with a consistent SMC environment of Rulesets, Classifications and Information Takeoffs.  All users will see the same content in SMC.
uc_01_16

Information Takeoff

V9.7 makes it possible to report all open Information Takeoff templates at one time.  This improvement is particularly useful for users who may have many different use cases for ITO, and therefore have run many different Takeoffs that are still open.  Before this enhancement, each Takeoff would need to be run individually, then reported one by one.
uc_01_17

ITOs indicate when a model has been changed after information has been taken off.  This enhancement adds an indicator to the takeoff window, signifying when a model change has made a previous takeoff out of date.
uc_01_18

Info View

Properties defined in type instances are shown in italics (properties defined in component instance level are shown in normal font). This is a helpful tool, as you will now know whether a property is defined by the Type of the component, or if it is unique to the individual component.
uc_01_19

If a value defined in the type instance differs from a value defined in the component instance, it is shown as a ‘strike through.’

A new property in the Identification tab: Type name – value of the type instance name (can be different than type of the component, if the component has a value in property psetXCommon: reference).  This more accurately reflects the full level of information available about the component, replacing the instance value ‘reference’ with the correct Type information.
uc_01_20

In conclusion, Solibri Model Checker 9.7 is a release with some impressive new features designed to streamline your workflow, as well as a lot of work behind the scenes and with the User Interface. With the changes to the Communication layout, issues identified in the model are now more efficiently managed to allow for quicker updating and review. New Company Extensions accomplish two major goals – first, allowing for better cohesion amongst teams, ensuring that everyone uses the same set of rules and requirements, and second, opening up SMC to broader audiences, as extensions can be company, project, regional or even national-specific. Finally, the Relations tool for combining (federating) floors from multiple models results in a much more efficient coordination workflow. V9.7 is loaded with enhancements and new capabilities, all intended to make your experience richer. Your investment in Solibri Model Checker continues to yield value and we look forward to your feedback, as well as your suggestions.

Overview of New Features of SMC 9.7