Examples
Overview · Rule Patterns · Profile Examples · Name Examples · Common Examples
Name Rule Examples
- Overview
- Recognised assembly Names set Prefix and Class
- Welded part Names should not be Main Parts
- Name determines valid Profile
- Vertical part Names require correct Rotation
The NAME column is one of the most commonly used subject columns when auditing model data.
These rules typically define:
- which object names are recognised
- how certain names affect assembly behaviour
- when certain parts must not be used as main parts
- when additional checks should apply to specific object types
Because the name of a part often reflects its modelling purpose, these rules allow audit behaviour to adapt based on the type of object being modelled.
For example:
- assemblies such as Beam, Column, or Loose Cleat may define expected assembly prefixes or class values
- welded secondary parts such as Plate or Channel should not be the main part of an assembly
- vertical members such as Column, Stub Column, or Dropper may require additional orientation checks
The examples below demonstrate several common rule patterns using the NAME subject.
These patterns can be used to design additional rules for other modelling conventions.
System File Reference
The rules used in these examples are based on the system audit file:
This file contains the complete set of name-based audit rules installed with ObChecked.
Related Documentation
- Core Concepts → Subject Node
- Core Concepts → Match Node
- Core Concepts → Target Node
- Core Concepts → Condition Node
- User Interface → Audit Definition Editor