Check for database interferences - Intergraph Smart 3D - Administration & Configuration

Intergraph Smart 3D Project Management

Language
English
Product
Intergraph Smart 3D
Subproduct
Project Management
Search by Category
Administration & Configuration
Smart 3D Version
12.1 (2019)

Unlike the traditional file-based method of manually defining groups of parts to check against each other, Check Interference is a separate software process that runs directly on the model database. Smart 3D provides two methods for using interference checking: Server-based interference checking (database detect) and Interactive interference checking (local detection). The table below lists the main differences between the two methods.

Database Detect

Local Detect

Runs continuously.

Works only within the current session.

Dedicated server minimizes impacts on users and improves performance.

Provides immediate graphical feedback.

Creates persistent interferences that are stored in the model database.

Creates temporary interference markers in a user session that are not stored in the model database.

Based on administrator settings and controlled by permission groups.

Based on individual settings.

Provides feedback about how much has been checked in the entire model.

Checks only created and modified items in the current session.

For more information about using Local Detect, see Interactive Interference Checking (Local Detect) in the Common Help.

Server-based interference checking

In order to monitor interferences, you must install Database Interference Detection Service on the same computer that Project Management is installed. You set database detection options using the tools in Project Management. You can also start and stop the interference database detection process in Project Management.

Interference detection requires disk space for the file cache that temporarily stores the interference data. Before starting the interference process, the interference server checks to see if enough space exists in the TMP location for the file cache. The server also checks to see if you have the proper permissions to write, read, and delete files in the TMP location. During the process, if the space becomes too low, the software stops IFC, and then displays an error message. These checks primarily apply to the server-based interference process. Although, they can apply to the local checking process if extremely low or no disk space is available for the temporary folder on the local computer.

Configure automatic disk defragmentation in order to free space for the file cache.

After you start the process, use the Status tab on the Interference Server Settings dialog to monitor the start time, progress of the interference checking, time when the last part was modified, and the status of the checking. A box at the top of the dialog box identifies the model that you are checking.

The software automatically checks new or modified objects apart from existing objects. When you create or modify an object, the software checks for interference against all objects in the Model database. The interferences generated by this process are persistent; that is, the interferences are stored in the database like any other objects in the software. You can also modify these objects by changing the properties. Interferences are also assigned to a permission group; thereby the entire process is under the control and restrictions of an administrator.

You can interrupt the automatic interference checking process during a work session without forcing a recheck of all parts in the database when the process is brought back online. When you restart the interference check process, the software begins checking where it left off when the process went offline. However, if you change any of the options on the Interference Server Settings dialog for Database Detect, you are given an option to perform a warm reboot so that all the approved interferences are preserved.

The server-based interference checking runs continuously. Therefore, you can perform an interference check at any time and view the interferences of interest that result from the background check by refreshing the workspace. After you have reviewed the interferences, you can remove an interference automatically from the database by editing the objects so that the interference no longer exists. You can then see the results of your edit by refreshing the workspace. Because certain types of interferences are allowable, you also have the capability to mark such interferences as acceptable.

Be aware that there is a four-minute interval between the time you make your edits and the time that the database detect service rechecks the objects. After the database detect process reaches 100%, the software issues a query only every two minutes to locate newly modified objects. Therefore, it is possible that there is a six-minute delay before a modified object is processed. We do not recommend changing the default four-minute interval. However, if you are in Project Management with the Interference Server Settings dialog open, press CTRL+SHIFT+F12 to change the default four-minute interval.

You must run the Database Detect process before running an interference report. The report is not intended to run on local interferences.

IFC permission requirements

You must install the Database Interference Detection Service option to monitor interferences. See Smart 3D Installation for information about installing and configuring this service.

 The user account running the IFC Windows service must have at least Read access to the SharedContent folder. Otherwise, IFC generates a bad part marker with clashes against structural fireproofing.

A Smart 3D Interference Detection Service icon is placed under the model node in the Project Management tree. After the proper access permissions are configured, you can start and stop the Database Detect process from any computer on which the Project Management option is installed.

The Smart 3D database hierarchy is comprised of a model configuration that consists of the model and catalog databases. For the IFC Database Detection process to run correctly, permissions must be set on the model and model permission groups according to the following guidelines:

Log on privileges for the IFC Administrator include:

  • Write access to the model database at a minimum.

  • Full Control permissions or access on a minimum of one permission group.

    SHARED Tip In the Project Management task, create a new permission group folder and permission group under the model icon to store the IFC results. For example, type IFC Permission Group Folder and IFC Permission Group in the New Permission Group Folder and New Permission Group dialogs, respectively. See Create IFC permission group folder and permission group.

  • Read access on all other model database permission groups at a minimum.

What do you want to do?