Rules are the basic building blocks of Solibri Model Checker (SMC). A rule can check a model from a single aspect (e.g. duplicate walls are not allowed) or from some specific point of view (e.g. usage of correct construction types). Some rules also report a key characteristic (e.g. list of window types and sizes) of a building.
Overall checking results are displayed in Rule Tree Table. Detailed checking results, on the other hand, are displayed in the Issues in Results View. Issues are part of a structure, which contains also categories and associated components.
As a result of checking the rules in Checking View, rules generate issues and optional reports. Issues are grouped into categories, which makes it easier to understand and deal with them. Issues also have associated components.
Rules are parametric, which means that you can control their behavior by setting the parameter values. This makes the system extremely flexible; rules can be configured to check, for example, project specific issues. Its important to understand that the rules do not change the model; they only find potential problems. It is always up to the user to decide, which issues are important and what actions to take.
Results are expressed in Results View in a hierarchical form. Results consist of Categories, sub-categories,Issues and components, see snapshot below.
1 Category is '0.Ground floor [0/1]'.
2 Issue is 'Too Few Close Components in Space.1.16 : Restroom[0/1]'.
3 Component having the actual problem.
4 'Related Components' add more information and description to the issue.
A single problem with components associated to it. As examples a few issues are presented here:
|•||Too Few Close Components in Space.1.16 : Restroom [0/1] (as shown in the above snapshot).|
|•||Component Wall.1 is inside component Wall.2|
|•||Both walls are attached to the issue|
|•||Walls, whose length is less than 200 mm (the rule requires, that minimum length walls is 200 mm)|
|•||Wall with the length and construction type are same are attached to the issue|
|•||There is an issue for each wall length under 200 mm|
|•||There is own category for each construction type including walls, of whose length is less than 200 mm|
|•||Space 1 doesn't touch slab surface below itself|
|•||The space is attached to the issue|
|•||All possible slabs, which are neat space bottom surface), are attached to the issue as Information|
|•||Information components are those components which help user to understand the issue, but aren't really part of the problem|
Issue types, and number of components attached to them, depends on the rule. Each rule has an own way to create and organize issues.
As presented above, a Category is a group of issues, which have something in common. There can be e.g. all components with the same construction type, or component located in the same building storey. Categories can be nested, so a category can have subcategories. All categories have issues or subcategories. A category has a name.
Issues and categories of a rule can be browsed in Results View.
1 Category states the problem in general and also indicates the total number of issues in the category.
2 Sub-category specifies the problem e.g. with a particular attribute of the component such as Type.
3 Issue states the real problem exactly.
4 Component having the actual problem.
Every issue has a severity set by the rule during checking. Possible severities are:
Symbol of the category is a folder with most important severity symbol, e.g. a symbol of the category with critical problems is
The user can make a decision (Reject , Accept , Undefined or Unhandled) to any component, issue or category. In some cases, a rule (intersection rule) rejects a component automatically.
Decisions are used in filtering just like severities. Symbol of a category contains Accepted symbol , when all issues in the category are accepted. If all issues have a decision, and at least one of them is rejected, the category symbol contains Rejected symbol
Importing Data from External Data Sources
Some table parameters in rules allow users to read external data from Excel files to them. In these cases, parameter panel is enabled for the ruleset and it includes a possibility to import external data, which can be used in the rules in the set. Each different external data type has an own panel in the Rule Parameter panel.
Allowed Construction Types and Layers
You can add construction types and layers used in the project to the list. The data table contains three columns:
The data can be used by the rule Layer of the Components Must Be from Agreed List
Escape Route General Requirements
You can add a table with general requirements of escape routes to the list. Typically the requirements changes by various areas and states. The data table contains five columns:
The data can be used by the rule Building Escape Routes
Escape Route Minimum Widths
You can add a table with minimum escape route widths to the list. Typically the minimum widths changes by various areas and states. The data table contains five columns:
|•||Total Door Width|
|•||Total Passageways Width|
|•||Min. Door Width|
|•||Min. Passageway Width|
The data can be used by the rule Building Escape Routes
Fire Compartment Areas
You can add a table about allowed areas of fire compartments. Typically the requirements changes by various areas and states. The data table contains four columns:
|•||Building Fire Rating|
|•||Fire Compartment Type|
|•||The data can be used by the rule Fire Compartment Must Be within Limits|
Fire Resisting Structure Types
You can add a table about fire resisting structure types for walls, doors, and windows. The data table contains three columns:
Each column has an individual list of construction types. The data can be used by the rule Fire Walls Must Have Correct Wall, Door, and Window Types
You can add a list of spaces, which should be ignored in rule checking normal residential rooms (like a living room, or a bedroom, no like a corridor). The data table contains three columns:
Light Opening Areas
You can specify light opening areas of windows and balcony doors by adding type of the window/door and its width and height to the list. The data table contains four columns:
|•||Light Opening Area|
The data can be used by the rule Spaces Must Have Enough Window Area
Space Area Limit Values
You can add a list of space area limit values to the table. The data table contains five columns:
The data can be used by the rule Space Area
Space Group Containment
You can add a requirements for space groups like apartment to the table. The data table contains seven columns:
|•||Space Group Type|
|•||Space Group Name|
|•||Space Group Number|
The data can be used by the rule Space Group Containment
You can add a space requirement to the table. The data table contains six columns:
The data can be used by the rule Space Requirements
Space Count on Each Floor
You can add required space count to the table. The data table contains six columns:
The data can be used by the rule Space Count on Each Floor
Distance Between Spaces
The data can be used by the rule Distance Between Spaces.