Planning objects, like all objects in the model, are given unique names for easy identification.
Visual Basic Project: [Programming Resources Folder]\Programming\ExampleCode\Planning\Rules\Assembly\Naming\PlnNameRules.vbp
Compiled Rule: [Reference Data Folder]\SharedContent\bin\Planning\Rules\Release\SM3DPlnAssemblyNameRules.dll
Bulkload: Naming Rules Workbook
The following class modules are included in the Visual Basic project:
AssemblyNameRule.cls
Naming rule for an assembly and an assembly block.
Creates a name based on a string (A for assembly, AB for assembly block), Global Workshare location ID, and an index number. For example, the first assembly created at workshare site 1 is called A1000001. If an assembly block is created next, it is called AB1000002.
Assembly and assembly block names do not change when moved from one parent block/assembly to another.
You can modify:
-
The strings included in the name.
-
Fixed-width value of the index number.
BlockNameRule.cls
Naming rule for a block.
Creates a name based on the position of the block in the assembly hierarchy. The name is based on the top level block name (B0) and a combination of Global Workshare location ID and index number for each level in the assembly hierarchy. For example, the first block created below B0 at workshare site 1 is called B0.1-1. the second block created below the new block at workshare site 3 is called B0.1-1.3-2.
Block names change as the assembly hierarchy changes.
You can modify:
-
Variables included in the name.
MirrorAssemblyNameRule.cls
Naming rule for mirrored assemblies.
Gives the target assembly the same name as the source assembly. If no symmetry is found, uses rules similar to AssemblynameRule.cls.
You can modify (for assemblies without symmetry):
-
The strings included in the name.
-
Fixed-width value of the index number.