Set up codeless IFC rules - Intergraph Smart 3D - Administration & Configuration

You must configure Codeless IFC Rules on one machine on which Project Management is installed.

1. Using Windows Explorer, navigate to [SymbolShare]\xml\Interference\. Copy the Sample.CodelessIFCRules.config file to a file called [YourModelName].CodelessIFCRules.config.

2. Edit the [YourModelName].CodelessIFCRules.config file to configure the Clash Management Rules.

3. In Project Management, click Stop on the IFC Database Detect tab, and wait until the process finishes.

4. Navigate to [Product Folder]\CatalogData\BulkLoad\DataFiles, and open IFCRule.xls.

5. In the IFCPostProcessorRule worksheet on line 6, column A, replace the exclamation point (!) with the letter M.

   The RuleProgID column in line 6 displays InterferenceRules.CodelessIFC.

6. Bulkload the [Product Folder]\CatalogData\BulkLoad\DataFiles\IFCRule.xls file in AMD mode to set your model to use the CodelessIFCRules functionality.

We recommend that you verify the ProgID available under Catalog task > InterferenceRules > ProcessorRule if the Codeless IFC rule fails to run after performing the setup instructions. The ProgID under Catalog task > InterferenceRules > ProcessorRule must be InterferenceRules.CodelessIFC for Smart 3D Codeless IFC rule to run. If not, perform the following instructions:

1. Navigate to <Product Folder>\CatalogData\BulkLoad\DataFiles and open IFCRules.xls

2. In the IFCPostProcessorRule worksheet on line 6, Column A, replace the exclamation mark(!) with a letter M.

3. Bulkload the file in AMD mode.

Configuration File

After you modify the configuration file and bulkload the IFCRule.xls file, you can use the configuration file to specify which objects to ignore for clash checking during pre-processing. The configuration file allows you to specify the following post-processing rules for interference checking:

• Clashes to ignore based on the two objects involved in the clash

• Interface type (ignore, hard, or soft) for new or modified interferences

  You can augment the codeless IFC rule logic to invoke your own code-based custom IFC rule for pre-processing and post-processing. The software only runs the custom IFC rule if no rule in the configuration file is evaluated.

The configuration file is in XML format. Make sure you follow the guidelines listed below when you modify the file:

• The syntax is valid XML. XML tags are case sensitive.

• Tags and attributes use the format described in Configuration File Format.

  Notepad++ has an XMLTools plugin for detecting formatting errors.