Rules evaluating a single object - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D Interference Checking

Language
English
Product
Intergraph Smart 3D
Subproduct
Interference Checking
Search by Category
Administration & Configuration
Smart 3D Version
13

Evaluates a single object. Use these rules in the <IgnoreObjectsForClashChecking> section, and under <ByIndividualObjectRules> in both the <IgnoreClashesBetweenObjects> section and the <SetClashProperties> section. See Configuration File Format.

Rule Tag

Details

ByObjectType

Decision based on object's Type (BOC user name)

Attributes

List - ObjectTypes in a comma-separated list

Examples

  • For piping welds:

    <ByObjectType List="Piping Welds"/>

  • For member parts, piping parts, and welds:

    <ByObjectType List="Member Part *, Piping *"/>

ByName

Decision based on object's Name

Attributes

Equals - exact match

Like - wild card match

The attribute must specify a matching value

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

Examples

  • For objects that have 'Road' in the name:

    <ByName Like="*Road*"/>

  • For objects that have 'Road' in the name; limited to equipment:

    <ByName Like="*Road*" LimitToObjectTypes="Equipment"/>

  • For objects that have 'Road' in the name, excluding slabs:

    <ByName Like="*Road*" ExcludeObjectTypes="Slab"/>

ByObjectPG

Decision based on the object's PG

Attributes

List - must specify one or more PG names in a comma-separated list

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

  • RelationNavigationPath

Examples

  • For piping parts in SpecTest PG:

    <ByObjectPG List="Testing,GHOST"/>

  • For objects in Testing or GHOST PGs:

    <ByObjectPG List="SpecTest" LimitToObjectTypes="Pipes, Piping Components, Piping Instruments, Piping Specialty Items"/>

  • For any object in SpecTest PG except for MemberParts:

    <ByObjectPG List="SpecTest" ExcludeObjectTypes="Member Part Linear, Member Part Curve"/>

ByRangeDiagonalLimit

Decision based on object's range diagonal size

Attributes

Value - specify the limit of the range diagonal (for example, Value="100m")

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

Examples

  • For slabs with a range greater than 100 meters:

    <ByRangeDiagonalLimit LimitToObjectTypes = "Slab" Value = "100m"/>

  • For any object except for pipes that are greater than 100m in range:

    <ByRangeDiagonalLimit ExcludeObjectTypes = "Pipes" Value = "100m"/>

  • For any object that is larger than 200m in range:

    <ByRangeDiagonalLimit Value = "200m"/>

BySystemPath, ByParentSystemPath, ByAssemblyPath, ByParentAssemblyPath

Decision based on object's system path, system hierarchy parent's system path, assembly path, or assembly hierarchy parent's assembly path

Attributes

  • Equals - exact match

  • Like - wild card match

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

  • RelationNavigationPath

Example

  • For all objects under \Existing Roads in the system hierarchy:

    <BySystemPath Like = "*\ExistingRoads\*"/>

ByInterfaces

Decision based on object implementing the specified interfaces per metadata

Attributes

List - specify one or more interface names in a comma-separated list; '*' is allowed

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

  • RelationNavigationPath

Examples

  • For sleeve-type specialty parts:

    <ByInterfaces List="IJUASleeve" LimitToObjectTypes="Piping Specialty Items"/>

  • For all parts, except for footings, that implement IJUACircularPlatform:

    <ByInterfaces List="IJUACircularPlatform" ExcludeObjectTypes="Footing"/>

ByAttribute

Decision based on a single attribute value of the object

Attributes

  • Interface - the name of the interface that has the attribute

  • Attribute - the attribute name in Smart 3D

  • Operator - defines the comparison between the value in the configuration file and the value on the Smart 3D object; you must use one of the symbols or the equivalent text listed below:

    Symbol

    Equivalent Text

    =

    EQ

    >

    GT

    >=

    GE

    <

    LT

    <=

    LE

    <>
    !=

    NE

    ~

    Like

    !~

    NOT Like

Because the greater-than (>) and less-than symbols (<) require an escape in XML, we recommend that you use the equivalent text (GT and LT)

  • Value - the value of the attribute to match; you can specify multiple values separated by a pipe symbol (|) for operators (EQ, NE, Like, or NOT Like)

  • For codelisted attributes, specify either the short string values or codelist numbers (a codelist number must be preceded by a colon ':')

  • You must specify units for united attributes

  • Tolerance - only applicable for numeric values; use with units if applicable, or use DB units in comparison

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

  • RelationNavigationPath

Examples

  • For objects where ConstructionRequirement = Existing:

    <ByAttribute Interface="IJConstructionInfo"

    Attribute="ConstructionRequirement"

    Operator="EQ" Value=":3" />

    For pumps with a shaft diameter less than 0.5in, optimized to only process equipment

    <ByAttribute LimitToObjectTypes="Equipment"
    Interface="IJUAShaftDims"
    Attribute="ShaftDia"
    Operator="LT" Value="0.5in"
    Tolerance="1mm" />

  • For all piping parts of NPD less than or equal to 0.5 in.:

    <ByAttributes LimitToObjectTypes=
    "Piping Components, Pipes,
    Pipe Instruments, Pipe Specialty Items"

    RelationNavigationPath="IJRtePathGenPart%Owner[1]"
    Interface1="IJRtePipeRun"
    Attribute1="NPD"
    Operator1="LE" Value1="0.5"
    Interface2="IJRtePipeRun"
    Attribute2="NPDUnitType"
    Operator2="EQ" Value2="in"/>

ByAttributes

Decision based on multiple attribute values of the object

Attributes

  • Interface - the name of the interface that has the attribute

  • Attribute - the attribute name in Smart 3D

  • Operator - the value in the config file and the value of the Smart 3D object

  • This rule is similar to ByAttribute; for each Smart 3D attribute, you must specify the Interface, Attribute, Operator Value, and Tolerance (optional)

  • To check two attribute values, specify the following XML attributes:

    • Interface1, Attribute1, Operator1, Value1, RelationNavigationPath1

    • Interface2, Attribute2, Operator2, Value2, RelationNavigationPath2

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

  • RelationNavigationPath

Example

Specifies that ContructionType = Temporary and No-MTO objects:

<ByAttributes Interface1="IJConstructionInfo"
Attribute1="ConstructionType"
Operator1="EQ" Value1=":6"
Interface2="IJMTOInfo"
Attribute2="ReportingType"
Operator2="EQ" Value2=":2"
Comment="Ignore ‘Temporary’and ‘No MTO’ objects" />

ByFilePath

Decision based on a file path for ignoring foreign reference files (DGN, R3D, and so forth). The ByFilePath rule is only used in the IgnoreObjectsForClashChecking section.

  • For DWG files, ACAD must be mentioned in codeless rules.

    <ByFilePath Like="*" Type="ACAD"/>

  • For DGN files, MSTN must be mentioned in codeless rules.

    <ByFilePath Like="*" Type="MSTN"/>

  • For R3D files, R3D must be mentioned in codeless rules.

    <ByFilePath Like="*" Type="R3D"/>

Attributes

Equals or Like - specify a FilePath value to match

Type - specify the fileType value to match (DGN, for example)

Examples

  • For attached DGN type reference files with \Roads\ contained in the path:

    <ByFilePath Like="*\Roads\*" Type="DGN" />

  • For attached DGN type reference files with the exact path, RefFiles\Grade\Ground.dgn:

    <ByFilePath Equals="RefFiles\Grade\Ground.dgn"
    Type="DGN"/>

ByR3DProject, ByR3DFile

Decision based on R3D objects that are based on the R3D project name or R3D file name

Attributes

Equals or Like - specify a FilePath value to match

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

Example

For R3D objects from a TestR3D project:

<ByR3DProject Equals="TestR3D"/>

ByRulesCombination

Decision based on a combination of single object rules

  • You can group any of the single object rules under ByRulesCombination

  • This rule is evaluated if all rules included under the ByRulesCombination tag are evaluated

Control

  • LimitToObjectTypes

  • ExcludeObjectTypes

Example

For underground pipes and components where the construction status is equal to Existing to be reused in place:

<ByRulesCombination
LimitToObjectTypes="Pipes, Piping *">
<ByObjectPG List="Underground Piping"/>
<ByAttribute Interface="IJConstructionInfo"
Attribute="ConstructionType"
Operator="EQ" Value=":17"/>
</ByRulesCombination>