Checking Interferences - Intergraph Smart 3D - 2019 - Help

Intergraph Smart 3D Point Cloud

English (United States)
Intergraph Smart 3D
Point Cloud
Search by Category
Smart 3D Version
12.1 (2019)

Interference checking (IFC) ensures that parts do not occupy the same volumetric space and that each part meets the design criteria for clearance. A successful interference check ensures that there is sufficient space around the parts so that they can operate properly, be serviced properly, and be easily installed or removed when necessary. The IFC process can look at all model data, including data from a referenced 3D model, referenced MicroStation and 3D AutoCAD files, and Point Clouds from third-party software with valid connections.

There are two methods for interference checking:

The major differences between the two methods are:

Database Detect

Local Detect

Runs continuously (System Administrator choice)

Works only within the current session

A dedicated server takes care of the IFC process, minimizing impact on users and improving performance

Provides immediate graphical feedback (works immediately after commit.)

Creates persistent interferences that are stored in the Model database

Creates temporary interference markers in a user session, which are not stored in the Model database. After you refresh the workspace, the temporary markers are removed

Based on administrator settings (controlled by permission groups)

Based on individual user settings

Provides feedback on how much has been checked in the entire model

Checks only created and modified objects in a session

Interference markers associate and come into the workspace along with the object participating in the interference

Clears dynamic interferences after refreshing workspace

The Smart 3D - External Data option only checks Smart 3D objects against external objects.

Smart 3D - External Data only checks for interference between two R3D external objects.

IFC finds interference between R3D and R3D objects that belong to different R3D projects that participates in IFC.

Smart 3D - Point Cloud option only checks objects against point clouds and Smart 3D.

Finds interferences involving attached Reference 3D models (with option Interference Detection set to Participate) and objects in inserted 3D files (MicroStation dgn or AutoCAD dwg) in the workspace without requiring a specific setting.

Includes a referenced point cloud when the Smart 3D Point Cloud Compare option is selected in the Project Management interference checking settings.

Receives the point cloud specification via the File > Define Workspace workflow in Smart 3D when the Smart 3D Point Cloud Compare option is selected.

The Database interference checking objects, or markers, appear in the model until other objects are moved so the interferences no longer exist, or the aspects for the interference process are changed. It is not possible to delete an interference object in the same way you can delete other objects in the model. However, you can tailor the display to hide acceptable interferences.

Interference checking can be used with rules in the reference data. The delivered rules include post- processing rules and clearance rules. For more information about the delivered IFC rules, see Interference Checking Reference Data.

How Interference Checking Results Appear

The Database Detect process marks any persistent interference with a spherical interference mark at the location of the interference. For example, the Database Detect service found an interference between this pipe and this beam, so it placed a spherical interference marker at that location.

The Local Detect process marks any interference it finds with a cube interference marker. For example, the software finds an interference and places a cube interference marker where there is an interference between a pipe and the floor.

For both processes, the color of the marker indicates the type of the interference: red for severe, green for clearance, and yellow for optional. You can modify the default interference marker colors with the Format > Surface Style Rules command. You can change the size of both the Database Detect and Local Detect interference markers using the Marker size option on the Interference Server Setting dialog box in Project Management task and the Interference Checking Settings dialog box in the Common task, respectively.

Severe Interference

Clearance Interference

Optional Interference

You can clear the acceptable interferences from your workspace by changing the required action on the Interference List Dialog, and then editing the display properties on the Interference Checking Settings Dialog Box.

In general, the software checks the parts involved in interfering objects to find and report the interferences. For example, if you have a pipe run that consists of a pipe, an elbow, and a pipe, each intersecting another pipe. The interfering pipe intersects the pipe run at each of the three positions. The software generates three interferences, and then displays them in the Interference List dialog box.

If an object has an interference with two other objects, these interferences are listed as two separate interferences in the Interference List. You can view all possible associated interferences (selected aspects) of an interference by right-clicking the interference row in the List view. This action opens the Interference Settings dialog box, and you can then click Other Aspects to see a list of all the aspects at the interfering location.

When an object is brought into the workspace, all of its associated interferences appear, even if they are not part of the filter used to define the workspace.

If an object has a very large range, or if it is located in a dense area of the model, it may take longer to process all of its clash interferences. If the number of parts that the object has to check for clash interferences is greater than 2000, the object is categorized as a delayed part. During the processing phase, these delayed parts are skipped, and then they are reprocessed. If the number of parts that the object has to check for clash interferences is greater than 20,000, the object is categorized as a bad part. The delayed and bad parts are listed in the S3D Error log file.

An object is also categorized as a bad part if its range or geometry information are unobtainable for the aspects configured for clash detection. The Properties dialog box for the clash object describes why the part is bad, and how to resolve any discrepancies. For example, you may have to update the object or process a To Do List item for the object.

The range of values that determine whether an object is a delayed part are defined by the RangeIntersectionObjCountMin and RangeIntersectionObjCountMax registry entries. The registry entries are located in the Intergraph\Applications\Environments\FoulCheck\Settings\Remote folder. You can edit these values to fit your needs. However, editing these values may cause a significant lag in the interference checking process.

Review the delayed and bad parts for modeling issues and any errors that can result from the displayed object ranges for the aspects selected for interference checking.

Role of the Administrator

An Administrator can limit the access to interference checking to the proper permission groups. An Administrator sets up the options for the background interference checking at the beginning of the project and is the only one permitted to change these options. This capability requires that an Administrator have read access to all objects in the database for the background interference checking to work properly. Users do not need to have access to all objects.

The server-based interference checking process can only be started from a client machine on which both the Project Management and the Database Interference Detection Process options are installed. The Administrator can run the detection process on more than one model simultaneously on the interference server. When an Administrator starts Database Detect, progress and statistical information is displayed on the Status tab of the dialog box.

  • Only an Administrator can start the Interference Detection Service (IfcNtSvc) on the system and set up the Interference Detection process (IFCProcess).

  • While working in a global workshare environment, you can only run and monitor IFC status from the host location.

Interference Checking License Management

The interference checking process consumes one license to process five models. It releases a license for every five models that stop processing. For example, IFC consumes two licenses to process ten models, one license for processing Model1 through Model5, and then another for processing Model6 through Model10. Similarly, it releases a license after the sixth model stops processing, and then another after the remaining models stop processing.

  • The IFC service does not consume a license when it starts. It consumes a license only while processing the model.

  • IFC consumes a license for every five models.

  • IFC cannot process a new model if a new license is not available.

  • You cannot set a number for processing models in the registry.

See Also

Check Interference Command
Common Interference Checking Tasks
Display the interference status
Set interference checking parameters on a workstation