BUNDLE Statement
- Last UpdatedDec 03, 2025
- 1 minute read
Syntax
|
BUNDLE <part_type> (2... ) ; |
||
|
<part_type>::=/PLATE | |
||
|
/BRACKET | |
||
|
/CLIP | |
||
|
/DOUBLING | |
||
|
/SPIGOT | |
||
|
/STIFFENER | |
||
|
/BPROFILE | |
||
|
/FLANGE | |
||
|
/PILLAR |
||
|
/FUN=<number> |
||
The interpretation of the part types is in most cases obvious. BPROFILE means profiles (stiffener or flange/face plate) on a bracket. FLANGE identifies only welded flanges (face plates). FUN, functional description, is given a valid functional description number.
By default parts of a certain type are compared only to other parts of the same type. However, often some part types are sorted together, for example, all profiles independent of the way they have been modelled. The BUNDLE statement is used group a number of part types to be treated as one type.
Example
BUNDLE /STI /FLA /PIL /BPRO;
Several BUNDLE statements may be given. The same bundling will be applied for all cases.
Notes: It is in principle possible to group types together, neglecting natural restrictions,
for example, profiles and plates. This may give unwanted results in production output.
Be certain to specify (see below!) that parts grouped together should have position
numbers in the same series of numbers. In case of contradiction between the bundling
and specification of the number series the bundling will take over and the result
may become unpredictable.