1
PFI - parallel flange I
1
PLTG - plate girder
1
TFI - tapered flange I
2
ANGL - angle - no differentiation
3
ZED - Z profile
4
TFC - tapered flange C
4
CEE - C shape
4
PFC - parallel flange C
5
FBAR - flat bar
6
RBAR - reinforcing bar (solid)
7
CTUB - circular tube
8
RTUB - rectangular tube
8
BOXG - box grinder
q
PFT - parallel flange T
10
TF - tapered flange T
10
TFWT - tapered web and flange T
12
HBAR - hexagonal bar
21
BFLA - bulb flat
1
PFI - parallel flange I
1
PLTG - plate girder
1
TFI - tapered flange I
2
ANGL - angle - no differentiation
3
ZED - Z profile
4
TFC - tapered flange C
4
CEE - C shape
4
PFC - parallel flange C
5
FBAR - flat bar
6
RBAR - reinforcing bar (solid)
7
CTUB - circular tube
8
RTUB - rectangular tube
8
BOXG - box grinder
q
PFT - parallel flange T
10
TF - tapered flange T
10
TFWT - tapered web and flange T
12
HBAR - hexagonal bar
21
BFLA - bulb flat
And the design parameter shapes are:
1
DPFI - Design Parameter Parallel Flange I
1
DPLG - Design Parameter Plate Girder
1
DTWI - Design Parameter Tapered Web I
2
DANG - Design Parameter Equal or Unequal Angle
3
DZED - Design Parameter Z Profile
4
DCEE - Design Parameter Flanged C Profile
4
DPFC - Design Parameter Parallel Flange Channel
5
DFBA - Design Parameter Flat Bar
6
DRBA - Design Parameter Round Bar
7
DCTU - Design Parameter Circular Tube
8
DRTU - Design Parameter Rectangular or Square Tube
8
DBXG - Design Parameter Box Girder
10
DPFT - Design Parameter Parallel Flange Tee
12
DHBA - Design Parameter Hex Bar
13
DCON - Design Parameter Cone
1
DPFI - Design Parameter Parallel Flange I
1
DPLG - Design Parameter Plate Girder
1
DTWI - Design Parameter Tapered Web I
2
DANG - Design Parameter Equal or Unequal Angle
3
DZED - Design Parameter Z Profile
4
DCEE - Design Parameter Flanged C Profile
4
DPFC - Design Parameter Parallel Flange Channel
5
DFBA - Design Parameter Flat Bar
6
DRBA - Design Parameter Round Bar
7
DCTU - Design Parameter Circular Tube
8
DRTU - Design Parameter Rectangular or Square Tube
8
DBXG - Design Parameter Box Girder
10
DPFT - Design Parameter Parallel Flange Tee
12
DHBA - Design Parameter Hex Bar
13
DCON - Design Parameter Cone

1
PFI - parallel flange I
1
PLTG - plate girder
1
TFI - tapered flange I
2
ANGL - angle - no differentiation
3
ZED - Z profile
4
TFC - tapered flange C
4
CEE - C shape
4
PFC - parallel flange C
5
FBAR - flat bar
6
RBAR - reinforcing bar (solid)
7
CTUB - circular tube
8
RTUB - rectangular tube
8
BOXG - box grinder
q
PFT - parallel flange T
10
TF - tapered flange T
10
TFWT - tapered web and flange T
12
HBAR - hexagonal bar
21
BFLA - bulb flat
1
DPFI - Design Parameter Parallel Flange I
1
DPLG - Design Parameter Plate Girder
1
DTWI - Design Parameter Tapered Web I
2
DANG - Design Parameter Equal or Unequal Angle
3
DZED - Design Parameter Z Profile
4
DCEE - Design Parameter Flanged C Profile
4
DPFC - Design Parameter Parallel Flange Channel
5
DFBA - Design Parameter Flat Bar
6
DRBA - Design Parameter Round Bar
7
DCTU - Design Parameter Circular Tube
8
DRTU - Design Parameter Rectangular or Square Tube
8
DBXG - Design Parameter Box Girder
10
DPFT - Design Parameter Parallel Flange Tee
12
DHBA - Design Parameter Hex Bar
13
DCON - Design Parameter Cone


AS
Australia
ASNZ
Australia and New Zealand (shared standards)
BR
Brazil (these profiles are not currently in the catalogue)
BS
British
CA
Canada
CE
Chile
DIN
DIN
EU
Europe
IS
India
JA
Japan
NZ
New Zealand
RU
Russia
SA
South Africa
SW
Sweden
US
America
SB
Solid bar profiles, common to many countries
DPP
Design parameter profiles - generic
FP
Fabricated profiles
CONC
Concrete
MISC
Miscellaneous
AS
Australia
ASNZ
Australia and New Zealand (shared standards)
BR
Brazil (these profiles are not currently in the catalogue)
BS
British
CA
Canada
CE
Chile
DIN
DIN
EU
Europe
IS
India
JA
Japan
NZ
New Zealand
RU
Russia
SA
South Africa
SW
Sweden
US
America
SB
Solid bar profiles, common to many countries
DPP
Design parameter profiles - generic
FP
Fabricated profiles
CONC
Concrete
MISC
Miscellaneous
It must be noted that these lists are not fixed, if you wish to create a new country catalogue, then create a new country abbreviation and then use it consistently. So too with the profile shapes, the lists indicated are related to the supplied catalogues and gtypes.
If you create their own catalogues and GTYPEs, just set up a new meaning, the interface documentation also describes the requirements of catalogues, plines and orientation mapping files that must be satisfied for a successful translation.
AS
Australia
ASNZ
Australia and New Zealand (shared standards)
BR
Brazil (these profiles are not currently in the catalogue)
BS
British
CA
Canada
CE
Chile
DIN
DIN
EU
Europe
IS
India
JA
Japan
NZ
New Zealand
RU
Russia
SA
South Africa
SW
Sweden
US
America
SB
Solid bar profiles, common to many countries
DPP
Design parameter profiles - generic
FP
Fabricated profiles
CONC
Concrete
MISC
Miscellaneous


The source CSV file is of the form:
In the example above, the ';' character is used as a field separator. The converter also allows ',' and the tab character. To manage the file in a spreadsheet program, you will have to tell it which character to use.
There are 6 columns:
COMMENT
If the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.
CATREF
This contains the PDMS/AVEVA E3D 2.1™ Catalogue component name.
SPREF
This contains the PDMS/AVEVA E3D 2.1™ Specification component name.
EXTERNAL
This contains the name, or formula, of the profile in the target external system.
STANDARD
This is the abbreviation chosen to indicate to which standard the profile is related
SHAPE
This defined the profile shape.
COMMENT
If the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.
CATREF
This contains the PDMS/AVEVA E3D 2.1™ Catalogue component name.
SPREF
This contains the PDMS/AVEVA E3D 2.1™ Specification component name.
EXTERNAL
This contains the name, or formula, of the profile in the target external system.
STANDARD
This is the abbreviation chosen to indicate to which standard the profile is related
SHAPE
This defined the profile shape.
The top line of the file must contain these headings, or precisely 6 fields which are taken to be column names.
By using a = in front of the external profile name, the name will be interpreted as a formula that defines value substitution. This means that the formula will be interpreted by replacing the {n} by the n'th group of number of the name contained in second column. Up to 9 substitutions are allowed. The characters that are considered as a number are: 0123456789 and '-' and '/'. The characters '-' and '/' should be enclosed by at least one digit on each side to be consider as part of a number group.
For example:
EPPKORE/508~D12.7
=TUBE{1}*{2}
EPPKORE/L45x45x4x4
=L{1}*{3}
EPPKORE/L50x30x3x3
=L{1}*{2}*{3}
EPPKORE/H496x199x9x14
=JPH{1}*{2}*{3}*{4}
EPPAISC/HSS4-1/2x4-1/2x1/8
=USHSS{1}*{2}*{3}
EPPAISC/14.000~D.625
=TUBE{1}"*{2}"
EPPKORE/508~D12.7
=TUBE{1}*{2}
EPPKORE/L45x45x4x4
=L{1}*{3}
EPPKORE/L50x30x3x3
=L{1}*{2}*{3}
EPPKORE/H496x199x9x14
=JPH{1}*{2}*{3}*{4}
EPPAISC/HSS4-1/2x4-1/2x1/8
=USHSS{1}*{2}*{3}
EPPAISC/14.000~D.625
=TUBE{1}"*{2}"
The new csv file will have the formulas interpreted, in the example:
EPPKORE/508~D12.7
TUBE508*12.7
EPPKORE/L45x45x4x4
L45*4
EPPKORE/L50x30x3x3
L50*30*3
EPPKORE/H496x199x9x14
JPH496*199*9*14
EPPAISC/HSS4-1/2x4-1/2x1/8
JSHSS4-1/2*4-1/2*1/8
EPPAISC/14.000~D.625
TUBE14.000"*.625"
EPPKORE/508~D12.7
TUBE508*12.7
EPPKORE/L45x45x4x4
L45*4
EPPKORE/L50x30x3x3
L50*30*3
EPPKORE/H496x199x9x14
JPH496*199*9*14
EPPAISC/HSS4-1/2x4-1/2x1/8
JSHSS4-1/2*4-1/2*1/8
EPPAISC/14.000~D.625
TUBE14.000"*.625"

COMMENT
If the field in this column begins with a '#' the whole record is ignored. After conversion, a .map.csv file is produced which is re-convertible, but which may contain error messages in this column.
CATREF
This contains the PDMS/AVEVA E3D 2.1™ Catalogue component name.
SPREF
This contains the PDMS/AVEVA E3D 2.1™ Specification component name.
EXTERNAL
This contains the name, or formula, of the profile in the target external system.
STANDARD
This is the abbreviation chosen to indicate to which standard the profile is related
SHAPE
This defined the profile shape.
EPPKORE/508~D12.7
=TUBE{1}*{2}
EPPKORE/L45x45x4x4
=L{1}*{3}
EPPKORE/L50x30x3x3
=L{1}*{2}*{3}
EPPKORE/H496x199x9x14
=JPH{1}*{2}*{3}*{4}
EPPAISC/HSS4-1/2x4-1/2x1/8
=USHSS{1}*{2}*{3}
EPPAISC/14.000~D.625
=TUBE{1}"*{2}"
EPPKORE/508~D12.7
TUBE508*12.7
EPPKORE/L45x45x4x4
L45*4
EPPKORE/L50x30x3x3
L50*30*3
EPPKORE/H496x199x9x14
JPH496*199*9*14
EPPAISC/HSS4-1/2x4-1/2x1/8
JSHSS4-1/2*4-1/2*1/8
EPPAISC/14.000~D.625
TUBE14.000"*.625"
COMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE
#;EU_BF100x7;EU-BF100x7;;EU;21
;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7
;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7
;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7

COMMENT;CATREF;SPREF;EXTERNAL;STANDARD;SHAPE
#;EU_BF100x7;EU-BF100x7;;EU;21
;EU_CF_CHS101.6x2.0;EU-CF-CHS101.6x2.0;=CHS{1}*{2};EU;7
;EU_CF_CHS101.6x2.5;EU-CF-CHS101.6x2.5;=CHS{1}*{2};EU;7
;EU_CF_CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU-CF-CHS101.6x3.0;EU;7
.map.csv
EPPKORE/508~D12.7
=TUBE{1}*{2}
EPPKORE/L45x45x4x4
=L{1}*{3}
EPPKORE/L50x30x3x3
=L{1}*{2}*{3}
EPPKORE/H496x199x9x14
=JPH{1}*{2}*{3}*{4}
EPPAISC/HSS4-1/2x4-1/2x1/8
=USHSS{1}*{2}*{3}
EPPAISC/14.000~D.625
=TUBE{1}"*{2}"
EPPKORE/508~D12.7
TUBE508*12.7
EPPKORE/L45x45x4x4
L45*4
EPPKORE/L50x30x3x3
L50*30*3
EPPKORE/H496x199x9x14
JPH496*199*9*14
EPPAISC/HSS4-1/2x4-1/2x1/8
JSHSS4-1/2*4-1/2*1/8
EPPAISC/14.000~D.625
TUBE14.000"*.625"


For generating mapping files for applications other than AVEVA Bocad, AVEVA E3D 2.1™ or PDMS, there is a folder and file structure you will need to follow. The files for Frameworks will provide a template. However, the TEST mapping file is the only one that has been completed.
There are three separate folders: the source csv files, the resultant mapping files and the supporting data files.

The important file to note is the shapes.txt file, this is a file that links the shape to the file tables in the standard folders below. Below is a sample of the shapes.txt file.

This indicates, for example, that files C.txt (line 7) are related to the shape code 4, which you will see above refers to C shapes. The profile tables related to the external package may then be sorted into folders named according to the standard to which they apply.
This will assist in housekeeping, as this is just a sample data set, the C.txt contains just 1 entry, UNP220. The interface now has enough information to perform the conversion.

csv
shapes.txt
shapes.txt
C.txt
C.txt


The entries are not necessarily in the same order as input, this is because they are sorted on output as well for ease of searching.


Elements cannot be transferred through the AVEVA Bocad Steel Interface if they do not have a valid material associated with them.
The existing base product material description may not be recognized; consequently, there must be a means by which we can translate the material description between systems. This is performed by means of a Material mapping file which relates the base product text description of a material to that output to, or found in, an ABS file.
When the application is started, the Properties database is searched for SOLI elements which may define materials used to fabricate elements in the base product. An internal list is then built for rapid reference.
Materials are usually associated with the base product elements using the Material Reference attribute, MATR, which points to a SOLI element in the Properties database. However, you may want to use the local :FABMGRADE attribute to specify the material. Either of these should be set for the application to be able to export elements successfully.
If the above system is still not specific enough, there is a mechanism by which you can define from where the material information is to be derived. Refer to Error and Log File Messages for further information.
When an element is exported, its material is determined by inspecting the :FABMGRADE attribute first, then the Description attribute of the SOLI element to which the MATR refers. If that fails, the user configurable mechanism is invoked. The text is then transferred locally to the :FABMGRADE attribute on the GENSEC, SCTN or PANE element. The text is then looked up in the Material mapping file to check that there is a translation into the file replacement text. The local material text is still exported.
When an element is to be imported, the file material description is looked up in the material mapping file and translated into the base product equivalent text string. This is then initially copied into the :FABMGRADE attribute of the element before any attempt is made to rationalise the MATR. If a SOLI element with this material text is found, the application will set the MATR to point to the correct SOLI element.
As with the profile mapping file, the first line is an identifier which indicates the external package or system with which the file is associated.
Note:
You can modify and extend the mapping file.

Error and Log File Messages
Note:
Error and Log File Messages
exported
imported


Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the Material Mapping File.
No match for material
The material is not in the Material Mapping File.
Syntax Error
Other, less specific, errors.
Unrecognized Parse
State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the Material Mapping File.
No match for material
The material is not in the Material Mapping File.
Syntax Error
Other, less specific, errors.
Unrecognized Parse
State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.

Multiply defined entries in Material Table
Either a material to be mapped or a mapped profile appears more than once in the Material Mapping File.
No match for material
The material is not in the Material Mapping File.
Syntax Error
Other, less specific, errors.
Unrecognized Parse
State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.

Multiply defined entries in Material Table
No match for material
Syntax Error
Unrecognized Parse
State


User macro nnnn
not found
Cannot find user macro.
Error in user
macro nnnn
PML programming error in user macro.
User macro nnnn
not found
Cannot find user macro.
Error in user
macro nnnn
PML programming error in user macro.

User macro nnnn
not found
Cannot find user macro.
Error in user
macro nnnn
PML programming error in user macro.

User macro nnnn
not found
Error in user
macro nnnn


Below is a sample comma separated mapping (CSV) file to map between the base product materials found in the Properties database and the file targeted at AVEVA Bocad Steel.
AVEVA,BOCAD
"unset","unset"
"TREAD-ALU","TREAD-Aluminum"
"ALUMINIUM","Aluminum"
"GR 420 I","GR 420 I"
"Pyrocrete","Fire concrete"
"Tread Grade","Tread Grade"
"LDPHP-GRADE","LDPHP-GRADE"
"Aluminium, cast","Aluminium, cast"
"Aluminium, wrought","Wrought Aluminium"
"Aluminium, Duralumin","Duralumin"
"Brass, red 80% Cu","Red Brass "
"Brass, yellow 65% Cu","Yellow Brass "
"Brass, cast","Cast Brass"
"Steel, carbon","Carbon Steel"
"Steel, chrome","Chrome Steel"
"Steel, Ni-chrome","Ni Steel"


Using the Profile Orientation Mapping File you can define how the interface translates a profile from the base product format into the Neutral File format on Export, or from it on Import. Refer to the User Guide for further information of how the Neutral File understands default orientations of certain profiles.
If you define their own catalogue profiles, or modify the supplied ones, and need to transform them into or from the neutral format, this mapping file should be used. In all cases an Orientation mapping file should be available, even if it is empty apart from the first line.
Below is an example file:
The first line is the file identification line, described as for the Material or Profile mapping files. The structure of the rest of the mapping file is of a comma or space separated file with four fields per line.
The first two fields provide the identification of the profile for treatment. The first of the identification fields states the steel standard from which the profile is to be taken. The second is the actual profile type (shape) code according to the codes given. Thus, in the example above, you can see that the channels (type 2) and angles (type 4) from the Euronorm, DIN and British Standard catalogues have been identified for special treatment.
The third and fourth fields describe what you want to do with the profile shape. The third is the mirroring flag, which should be set to 1 if the profile is to be reflected about the Y-axis. This will commonly be the case for angle profiles. no mirroring is indicated by a value of 0 in this field.
The last field defines how much additional angular rotation you want to apply to the shape. For example, some catalogues may define the long leg of an unequal angle to be on the horizontal, whereas AVEVA Bocad Steel Interface expects it to be vertical. The rotation angle must be between -180 and +180 degrees.
If, during the Import or Export process, an entry for a specific profile is not found, no action is taken, and no error message is output as it is assumed that you do not want it to receive special treatment.
The following figure illustrates the effect of each operation on different catalogue representations of an angle profile. We re-emphasise the difference in the handedness of the coordinate systems.

AVEVA BOCAD
BRI 2 0 180
BRI 4 1 180
DIN 2 0 180
DIN 4 1 180
EUR 2 0 180
EUR 4 1 180
Note:
Mirroring will change the start and end positions of the linear member. It is therefore advisable that if you can achieve the same result purely by rotation, then the latter is the preferred option. In this way you will avoid confusion in AVEVA Bocad Steel.

Note:


In the base product it is possible to set a mirror flag which implies that the profile is to be mirrored about the local Y axis, while keeping all other geometric attributes unchanged. Also you might wish to define a new arrangement of profile in the catalogue that would need mirroring before being written in the ABS file using the Orientation Mapping File. Under normal circumstances the ABS file would simply transfer a mirror flag, indicating what is required and how to interpret the geometric data.
Unfortunately, AVEVA Bocad Steel cannot handle mirroring, in any form. Therefore the ABSI interface has to handle all this internally before export, and after import. However, it is impossible to completely undo the transformations that have been performed on an element for export when the interface is re-importing the same element. For example: the ends might have been swapped round, or the end connectivity might be changed. In these situations the Compare/Merge might highlight a changed element even though it appears to occupy exactly the same location.


Users who take advantage of the Unicode features of the base product may have issues when exporting and importing a model. The primary danger is where there are catalogue profile or material names in the base product that contain Unicode characters. Therefore, a dictionary file may be written to convert any base product strings that contain Unicode characters into equivalent strings that do not. It is these latter strings that will appear in the file. This might actually be a description of the profile, rather than the known profile name. This could be to inform or alert you of the external application of what the profile is meant to be.
Because there are strings other than the profile names that appear in the file, this Unicode description file should be regarded as a kind of dictionary, a look-up for any string, rather than just a profile name description table. Therefore, its format and use is different from that of the other mapping files. It is used immediately prior to writing out the text strings and it is only to contain the strings that require stripping of Unicode characters. It is also used on file import.

This Unicode description file may be customized for each target system, in the same way as the other mapping tables. This will contain:
So a dictionary for export might look like:
You are not forced to prepare one of these files: the system will cope if one does not exist. It would just mean that the strings would not be translated and you would have to take his chance with the target package. Further, the file can be empty, but if there are any strings requiring description, there must be the ENCODING: statement as the first non comment line in the file.
It should be noted that text fields are of a fixed maximum width. If the resultant text is too long, it will be truncated, and you are warned. Ideally, the translation should succeed with no truncation warnings, and all profiles mapped either by the main mapping file or through using the Unicode description file. If, however, you decide to output in UTF-8 characters, and thereby diverge from the literal interpretation of the format, truncation will not take place.
On import the system will attempt to recognize names in the dictionary, and to translate them back into the original names. This is in addition to the usual profile and material mapping files.
ENCODING:ASCII
# header texts
# non-ASCII profiles
:Γρxνxθ:Corinthian Column, 1 cubit:
# non-ASCII materials
|χάλυβα, ανθρα|Green-veined marble|
An indication of the encoding to be used for the file
Unicode UTF-8 with a Byte Order Mark (BOM):
ENCODING:UTF8BOM
Unicode UTF-8 without BOM:
ENCODING:UTF8noBOM
Force to Default encoding:
ENCODING:DEFAULT
Force to ASCII:
ENCODING:ASCII
A set of string substitutions to be used whenever a quoted-string is written to the file.
As potentially any character can be used in the string, first non-space character of the line is used as a delimiter for that line
Only complete strings would be substituted
Comment lines are indicated by '#'
not every string needs to be in the dictionary - others would be passed through without error (but would trigger a warning if characters were lost in the encoding)
An indication of the encoding to be used for the file
Unicode UTF-8 with a Byte Order Mark (BOM):
ENCODING:UTF8BOM
Unicode UTF-8 without BOM:
ENCODING:UTF8noBOM
Force to Default encoding:
ENCODING:DEFAULT
Force to ASCII:
ENCODING:ASCII
An indication of the encoding to be used for the file
A set of string substitutions to be used whenever a quoted-string is written to the file.
As potentially any character can be used in the string, first non-space character of the line is used as a delimiter for that line
Only complete strings would be substituted
Comment lines are indicated by '#'
not every string needs to be in the dictionary - others would be passed through without error (but would trigger a warning if characters were lost in the encoding)
A set of string substitutions to be used whenever a quoted-string is written to the file.


The Appendix describes the following:
Modification Dates and Times and the Base Product
First Time Export to AVEVA Bocad Steel
Import from AVEVA Bocad Steel
Subsequent Export to AVEVA Bocad Steel
Removal of History Data
Design Parameter Sized Profiles
Managing the Model Limits and Offsets
Initialization of the ABSI Application
Catalog Versions
Application Tools
User Customization.
Modification Dates and Times and the Base Product
Modification Dates and Times and the Base Product
First Time Export to AVEVA Bocad Steel
First Time Export to AVEVA Bocad Steel
Import from AVEVA Bocad Steel
Import from AVEVA Bocad Steel
Subsequent Export to AVEVA Bocad Steel
Subsequent Export to AVEVA Bocad Steel
Removal of History Data
Removal of History Data
Design Parameter Sized Profiles
Design Parameter Sized Profiles
Managing the Model Limits and Offsets
Managing the Model Limits and Offsets
Initialization of the ABSI Application
Initialization of the ABSI Application
Catalog Versions
Catalog Versions
Application Tools
Application Tools
User Customization.
User Customization.

Modification Dates and Times and the Base Product
First Time Export to AVEVA Bocad Steel
Import from AVEVA Bocad Steel
Subsequent Export to AVEVA Bocad Steel
Removal of History Data
Design Parameter Sized Profiles
Managing the Model Limits and Offsets
Initialization of the ABSI Application
Catalog Versions
Application Tools
User Customization
Modification Dates and Times and the Base Product
First Time Export to AVEVA Bocad Steel
Import from AVEVA Bocad Steel
Subsequent Export to AVEVA Bocad Steel
Removal of History Data
Design Parameter Sized Profiles
Managing the Model Limits and Offsets
Initialization of the ABSI Application
Catalog Versions
Application Tools
User Customization


Modification Dates and Times and the Base Product

An important feature of the AVEVA Bocad Steel Interface is the ability to compare and merge elements. In AVEVA Bocad Steel this feature is very dependent on the base product passing the correct modification dates.
In the base product Dabacon database there are three different values that could represent the date/time of modification:
There are also two UDA values that store the internal and external ID; :FABMARK and :FABEMARK respectively. The latter value is passed in the ABS file as the unique identifier (UUID) by which each system can uniquely identify each element.
Further, in order to complete the historical information, the element's Creation date and time are set and passed in the ABS file. As far as the base product is concerned, this is generally the time of the CRDATE or LASTMOD. Once set, the Creation date and time are not modified.
Which Modification date and time values we use for transferring in the ABS file are subject to several conditions.
The :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;
The :FABIDATE and :FABITIME UDA pair representing the Import date/time;
The LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.
The :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;
The :FABMDATE and :FABMTIME UDA pair, representing some nominal modification date/time;
The :FABIDATE and :FABITIME UDA pair representing the Import date/time;
The :FABIDATE and :FABITIME UDA pair representing the Import date/time;
The LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.
The LASTMOD value from the database representing the last time stamp on the Dabacon element. his is set by the SAVEWORK command.

correct


Because any interaction with the database is considered as a change, it is essential to minimize the number of database changes and the time differences between them. For an element that has been created in the base product we have to set at least the Modification date/Time, and the internal and external IDs prior to export. Following export, a SAVEWORK command is executed on the data, as soon as possible after the export, in order to minimize the time difference between the Modification date (the date/time at which the data was extracted from the element), and the time that field was locked on the database by a SAVEWORK. This introduces a time difference - a buffer - between values. The Modification date/time will be the LASTMOD value.

locked


The challenge now is to determine what has changed since the last export. This is the issue. With so many values of date and time, which do we choose? Here is the algorithm.
The value of the buffer is critical. The default value is 3 minutes. However, for larger models, this buffer should be larger, possibly as high as 15 minutes. The buffer does not affect the time difference between export/import transactions, rather it represents the elapsed time of the previous export/import transaction. We cannot store this value in the database, because we do not know to which particular transaction the buffer value would refer. For example, we might import several files of varying size in quick succession, or edit the model outside of the ABSI system.
Therefore, there is a PML global variable that can be changed by hand using the experience of previous transactions. It can be locally changed in the current base product session using the command below, but it will revert to the default value of 3 minutes on session start-up.
There are 3 dates/times IDATE, MDATE, LASTMOD.  (IDATE represents the :FABIDATE and
         :FABITIME UDA values; MDATE similarly; LASTMOD is the last database SAVEWORK date/time)
If MDATE UDA is unset
      Use LASTMOD as MDATE
If IDATE UDA is unset
Use LASTMOD as IDATE
-For comparison, find out TESTDATE
If the IDATE UDA is set
use later of IDATE and MDATE as TESTDATE
else
use MDATE as TESTDATE (Item has not been imported)
if ( (TESTDATE + buffer) > LASTMOD )  item has NOT changed within buffer time of the
         SAVEWORK
!!bocExpTimBuf = (15)
Note:
This can also be configured in the bocuserdata.pmlfnc user configuration command file.

There are 3 dates/times IDATE, MDATE, LASTMOD.  (IDATE represents the :FABIDATE and
         :FABITIME UDA values; MDATE similarly; LASTMOD is the last database SAVEWORK date/time)
If MDATE UDA is unset
      Use LASTMOD as MDATE
If IDATE UDA is unset
Use LASTMOD as IDATE
-For comparison, find out TESTDATE
If the IDATE UDA is set
use later of IDATE and MDATE as TESTDATE
else
use MDATE as TESTDATE (Item has not been imported)
if ( (TESTDATE + buffer) > LASTMOD )  item has NOT changed within buffer time of the
         SAVEWORK
Note:
!!bocExpTimBuf = (15)


There is a facility on the main Import and Export forms to remove the history data on the current element and its children using the menu option below.


When exporting from the base product to Bocad, there must be an entry in the profile mapping file that corresponds to the profile in the base product.
If exporting channels (for example: channel_with_design_parameters) or angles (for example: angle_with_design_parameters) you must make sure the ABSI p-lines in the catalogue have been created otherwise issues with offsets from NA p-line will occur.
If exporting angle profiles, ensure that the required parameters are placed in the export file by correctly giving the order of parameters in the mapping file. If the thickness of the legs are the same, the parameter must be repeated in the Bocad profile name, for example:
Angle_with_design_parametersBLL@1@2@3@3@4@5@6@7@8EUR
If exporting I (sometimes known as H) profiles (for example: Beam_with_design_parameters), all the design parameters must be completed consistently. If the depth between fillets, flange thickness and overall depth are not consistent, it is possible that the geometry in the base product and Bocad will not be the same. This can be avoided by using the BT_Variable profile supplied with the product (run !!boccatadespar() in PARAGONmodule).
Mapping files are primarily used on import. However the shape code is read from the mapping file when exporting from the base product and the Bocad name is ignored when importing design parameter profiles (those that have @ in the Bocad name) into Bocad.For this reason when re-importing profiles from Bocad into the base product the Bocad name can be different to that in the mapping file.
For example BT_Variable might be mapped to BT@3@1@4@2 but be returned as PRS300*50*1000*20.
If you add these names to the mapping file (in our example as PRS@3@1@4@2), you will still be able to export these profiles into the base product.
It is important to reorder the design parameters into the documented order using the mapping file. To see the order in the base product using the Query>Properties window.
When importing from Bocad to the base product, duplicate Bocad names are not allowed in the mapping file.

I
1
BT
BT300*10*500*20
Depth

L
2
BLL

Leg length Y

Z
3
BLZ

Depth

U
4
BLU

Depth

Plate
5
BL,PL

Depth

Full Tube
6
BAR,
ROND,...

Out radius

Tube
7
CHS,
TUBE,
PIPE,...

Out radius

Square Tube
8
MSH,
TUBER,
TUBEC

Depth

C
9
BLC

Depth

T
10
BLT

Width

Cone
13
CONE

Start diam
Table continued:
Par 2
Par 3
Par 4
Par 5
Width
Web thick
Flange thick
Unit weight
Leg length X
Thickness Y leg
Thickness X leg
X-offset
Web thick
Width
Flange thick
X-offset
Width
Web thick
Flange thick
Width
Thick
Unit weight
Thick
Unit weight
Width
Wall thick X
Wall thick Y
Unit weight
Width
Web thick
Flange thick
X-offset
Depth
Web thick
Flange thick
Depth to NA
End diam
Wall thick

Width
Web thick
Flange thick
Unit weight

Leg length X
Thickness Y leg
Thickness X leg
X-offset

Web thick
Width
Flange thick
X-offset

Width
Web thick
Flange thick

Width

Thick
Unit weight

Thick
Unit weight

Width
Wall thick X
Wall thick Y
Unit weight

Width
Web thick
Flange thick
X-offset

Depth
Web thick
Flange thick
Depth to NA

End diam
Wall thick

Table continued:

Root radius
Cross sectional area
Depth between fillets
Nominal depth

Y-offset
Unit weight
Root radius
Toe radius

Unit weight
Root radius
Toe radius
Flange taper

External corner radius
Internal corner radius

Unit weight
Root radius
Toe radius
Flange taper

Unit weight
Root radius
Nominal width
Nominal depth

Table continued:

Nominal width

Backmark for bigger leg
Backmark for smaller leg

Depth between fillets
Nominal depth
Nominal width
Backmark

Depth between fillets
Nominal depth
Nominal width
Backmark

Original depth
Original width
Original weight
Backmark

Table continued:

Section Type
Bocad Profile Type
Bocad Generic Name
Denomination
Par 1
I
1
BT
BT300*10*500*20
Depth
L
2
BLL
Leg length Y
Z
3
BLZ
Depth
U
4
BLU
Depth
Plate
5
BL,PL
Depth
Full Tube
6
BAR,
ROND,...
Out radius
Tube
7
CHS,
TUBE,
PIPE,...
Out radius
Square Tube
8
MSH,
TUBER,
TUBEC
Depth
C
9
BLC
Depth
T
10
BLT
Width
Cone
13
CONE
Start diam
Par 2
Par 3
Par 4
Par 5
Width
Web thick
Flange thick
Unit weight
Leg length X
Thickness Y leg
Thickness X leg
X-offset
Web thick
Width
Flange thick
X-offset
Width
Web thick
Flange thick
Width
Thick
Unit weight
Thick
Unit weight
Width
Wall thick X
Wall thick Y
Unit weight
Width
Web thick
Flange thick
X-offset
Depth
Web thick
Flange thick
Depth to NA
End diam
Wall thick
Par 6
Par 7
Par 8
Par 9
Root radius
Cross sectional area
Depth between fillets
Nominal depth
Y-offset
Unit weight
Root radius
Toe radius
Unit weight
Root radius
Toe radius
Flange taper
External corner radius
Internal corner radius
Unit weight
Root radius
Toe radius
Flange taper
Unit weight
Root radius
Nominal width
Nominal depth
Par 10
Par 11
Par 12
Par 13
Nominal width
Backmark for bigger leg
Backmark for smaller leg
Depth between fillets
Nominal depth
Nominal width
Backmark
Depth between fillets
Nominal depth
Nominal width
Backmark
Original depth
Original width
Original weight
Backmark
Par 14

Query>Properties


Exporting to AVEVA Bocad Steel
Importing from AVEVA Bocad Steel.
Exporting to AVEVA Bocad Steel
Exporting to AVEVA Bocad Steel
Importing from AVEVA Bocad Steel.
Importing from AVEVA Bocad Steel.

Exporting to AVEVA Bocad Steel
Importing from AVEVA Bocad Steel
Exporting to AVEVA Bocad Steel
Importing from AVEVA Bocad Steel


The 3d global limit box of the data to be exported is calculated as the export list is modified. This feedback is for information only to guide you in choosing a suitable model offset for Bocad.

The model offset position and orientation are stored in a special site in the Application Data World, /FABAPPDW. By default the position is at E0 N0 U0 in world space and the default orientation is "Y is North and Z is Up" in world space. This is usually locked to prevent you from accidentally modifying the offset position that has been agreed with the AVEVA Bocad Steel user.

You can modify the header details by inspecting the chosen header and pressing Edit. Press Apply to update the header data or Cancel leave the header data unchanged.

To create a new header block, select New header… from the drop down list.

A new header element is created with default values that can be edited as desired. For convenience it is advised that the header is given a name by which it can be easily identified.

Edit
Apply
Cancel
New header…


Any offset value in the ABS file from Bocad, is taken and set on the offset reference zone.


Sometimes the application might not start up correctly, or even at all. This could be caused by the automatic loading of the configuration file, ABSI.xml. If there are errors in this file, such as certain header elements have been deleted, or options are no longer available, then the initialization might fail. You can delete or rename this file which is found in the user area, the application should then start up with the default settings.


During the lifetime of this application, updates to the Catalog are quite likely. For example a typical change might be the default orientation of an unequal angle. This has been a cause of problems in the past when operating the application on both PDMS12.1 and AVEVA E3D 2.1™.
You can perform a quick check to validate the profile orientation using the following lines either in the command window or as a macro.
Obviously you should change the SPRE to be the profile under investigation. By comparing the view between versions you can see if there is any difference in configuration between versions.
You must be aware that the Catalogue update function might need to be changed to locate the Plines correctly according to the Cardinal Points. Refer to Cardinal Points for further information.
NEW SITE /TestAngleOri
NEW ZONE
NEW STRU
NEW FRMW
NEW GENSEC SPRE /L100x50x10
JUSL SNFG
NEW SPINE
NEW POINSP at E0
NEW POINSP at E500

Cardinal Points
NEW SITE /TestAngleOri
NEW ZONE
NEW STRU
NEW FRMW
NEW GENSEC SPRE /L100x50x10
JUSL SNFG
NEW SPINE
NEW POINSP at E0
NEW POINSP at E500
Cardinal Points


The application is supplied with the following functions:
Managing ABSI UDA visibility
Coloring Phases
Sort members according to leading member UUID
Merging SITES
User Customization
Initialization of the ABSI Application
Catalog Versions.
Managing ABSI UDA visibility
Managing ABSI UDA visibility
Coloring Phases
Coloring Phases
Sort members according to leading member UUID
Sort members according to leading member UUID
Merging SITES
Merging SITES
User Customization
User Customization
Initialization of the ABSI Application
Initialization of the ABSI Application
Catalog Versions.
Catalog Versions.

Managing ABSI UDA visibility
Coloring Phases
Sort members according to leading member UUID
Merging SITES
User Customization
Initialization of the ABSI Application
Catalog Versions
Managing ABSI UDA visibility
Coloring Phases
Sort members according to leading member UUID
Merging SITES
User Customization
Initialization of the ABSI Application
Catalog Versions


For various reasons, the UDAs that are created to manage the ABSI data are normally hidden. If you wish to see them on a one-off basis in the main product you can use the function !!bocshowuda(). To inspect an element, identify and locate the element, type !!bocshowuda() in a command window and the ABSI UDAs listed are listed.
To modify their visibility more permanently in LEXICON use the function !!bocvisibleudas(). This has several arguments because this function also works on OpenSteel UDAs. ABSI UDAs have FAB as their prefix, OpenSteel UDAs have SDNF as their prefix.
!!bocvisibleudas( !prefix, !globalVisibility, !localList)
Where:
!prefix = |SDNF| or |FAB|
For SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL
!globalVisibility = true or false
To set ALL SDNF or FAB UDAs visible or invisible
!localList
A space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|
!prefix = |SDNF| or |FAB|
For SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL
!globalVisibility = true or false
To set ALL SDNF or FAB UDAs visible or invisible
!localList
A space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|
For example:
!!bocvisibleudas( |FAB|, false, |FABEMARK| ), this would hide all ABSI UDAs except :FABEMARK.
!prefix = |SDNF| or |FAB|
For SDNF or FAB - goes to either /SDNF-UWRL or /FAB-UWRL
!globalVisibility = true or false
To set ALL SDNF or FAB UDAs visible or invisible
!localList
A space separated string list of UDAs to be visible whatever, for example: |FABEMARK FABCRDATE|

bocshowuda()
!!bocshowuda()
!!bocvisibleudas()
!!bocvisibleudas( !prefix, !globalVisibility, !localList)
!!bocvisibleudas( |FAB|, false, |FABEMARK| ),


If the imported model has Phase information in the user data from Bocad, you can sort the elements according to Phases.
For the purposes of this example, we assume that Bocad has been configured to export phase data in the fields shown. The example PML function supplied is !!bocuserphasesort().

The user data from Bocad is stored in the UDAs :FABRADATA[1] and :FABTADATA. If the data change, or the location of this information in the user data fields changes, then this function must be modified accordingly. Use the data, the elements will be sorted into FRMW according to their phases.

The function to perform this task is !!bocuserphasesort. You needs to enter the command in the command window and identify the required element to be sorted.
!!bocuserphasesort ( )
For example:
!!bocuserphasesort ( ), this will produce a log file called absiphasesort.txt in C:\temp listing any comments.

This can take a long time, especially for large models, see below. In this case it is recommended to switch into TTY (non-graphical) mode, and perform the operation there.

You can then return to the graphical mode to use the Phase colouring function, refer to Coloring Phases for further information.

Note:
You are free to modify it if required.

Coloring Phases
Note:
!!bocuserphasesort.
!!bocuserphasesort ( )
!!bocuserphasesort ( ),
Coloring Phases


This is a more general function than just colouring phases, it allows you to enhance members and member groups of the current element (CE) in the graphical view.
!!bocusercolour( !level, !startColour )
The !level argument determines how many levels down in the hierarchy you wish to differentiate the members:
Level 1
Colours only the immediate children of the CE.
Level 3
Colours up to 3 levels down.
Phase Sorting
The !startColour is a starting value of the colour number for the colouring sequence.
Level 1
Colours only the immediate children of the CE.
Level 3
Colours up to 3 levels down.
Phase Sorting
The !startColour is a starting value of the colour number for the colouring sequence.
The following sequence shows the effect of different level settings on the colouring. The first image is of the raw state.

Level 1
Colours only the immediate children of the CE.
Level 3
Colours up to 3 levels down.
Phase Sorting
The !startColour is a starting value of the colour number for the colouring sequence.

!!bocusercolour( !level, !startColour )


Sort members according to leading member UUID

This user function is aimed at the situation where the main steelwork has been designed in PDMS, and exported to Bocad for detailing.
The detail plates are added to the model in Bocad and associated with a main member. In Bocad terms this is referred to as the leading member. In this situation a different set of user data is required to associate the new elements with the leading member.

With this information, new elements that have the leading member’s UUID set can be moved into the existing PDMS database hierarchy to be alongside the owning member.

Using the leading member’s UUID and the :FABEMARK, the child element is moved to the right place in the hierarchy. As before, if this data is in another slot in the user data set, then the function must be changed. When at the suitable element in the hierarchy, you can sort the data, to do this, type the following command in the Command Window:
!!bocusersortwuuid( )

For example: the stiffener elements have been moved to be with their leading member in the hierarchy.

Command Window
!!bocusersortwuuid( )


You can import parts of the model into different SITEs and then merge them, to do this type the following command in the Command Window:
!!bocusermergesites( !destination, !source )
The !source and !destination variables are database reference numbers of SITES. The merge process takes the members of the source SITE and relocates them into the destination SITE. The function does not work at a lower level than a SITE, although it could be modified easily.

Command Window
!!bocusermergesites( !destination, !source )
!source
!destination


You can manage the hierarchy using Bocad data, to demonstrate the user customization capabilities of the ABSI interface various functions have been supplied that are easily accessible.


As a demonstration of the export customization, AVEVA have provided a function that will produce a comma separated variable file, a CSV file of the hierarchy on each principal element exported. This might be useful for reporting purposes of for Bocad itself in managing the model. This is accessed by attaching the !!bocpostexport function. From the ABSI Export window, navigate to the ABSI - System Configuration window.

From the ABSI - System Configuration window, select the Macros tab enter the Post export Macro Name.

Following an export procedure, a CSV file is produced alongside the ABSI file, this can then be read by spreadsheet applications that can accept CSV files.

!!bocpostexport
ABSI Export
ABSI - System Configuration
ABSI - System Configuration
Macros
Post export Macro Name


An example of customization is included in the application, this can be accessed by setting the import pre- and post- processing functions to be bocpreimport and bocpostimport respectively.

The pre- import function is called after you have initiated the import process and checks whether the target storage location is empty. This is because there are different processing options depending on whether the target storage location is empty or not.
If the storage location is empty the application sorts all incoming entities according to phases. This is because the model has been created in Bocad. Refer to Sorting into Phases for further information.
If the storage location already has something in it, the data imported from Bocad will be merged into the existing model. In this case, the new details that have been associated with existing members are moved into the same location in the database hierarchy. All members are sorted according to UUID, all other members that have been newly imported from Bocad are sorted into phases. Refer to Sort members according to leading member UUID and Sorting into Phases for further information.

Sorting into Phases
Sort members according to leading member UUID
Sorting into Phases
Sorting into Phases
Sort members according to leading member UUID
Sorting into Phases


The Structural Design User Guide introduces some of the facilities provided by the application for the design and documentation of logically interconnected structures. It explains the main application concepts and the applications that support it, and indicates how to apply these to design projects.
The structural applications offer these key benefits:
Structures is an umbrella to four applications supplied within the AVEVA E3D Design suite. The applications within structures allows you to build up detailed and complex structures within a full 3D environment.
The Structures comprises four applications:
The applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.
Structural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.
When grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.
Temporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.
The applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.
Where possible, the Model applications create and maintain connectivity of the structural network automatically.
Non-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.
Negative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.
Templates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.
Multiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.
Much repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.
Joint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.
Sections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The ‘macrostructure’ (for example, complete areas to be covered) can be designed first and then subdivided into a manageable ‘microstructure’ for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.
Penetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.
Multi-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.
At any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).
The applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.
The applications are designed to use specification data when structural components are selected from the Catalogue database, so that design consistency and conformity to standards are maintained. It is important, therefore, that the structural Catalogue databases are properly maintained.
Structural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.
Structural elements are named in accordance with a predefined set of rules, so that their positions in the database hierarchy are always obvious without the need to input specific texts during the design process.
When grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.
When grid storage mode is used, structural elements are automatically stored in the appropriate hierarchy.
Temporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.
Temporary lists of elements can be set up, so that a design operation can be carried out on all elements within the list simultaneously. A great deal of repetitive work can be avoided when commonly-repeated design modifications are carried out.
The applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.
The applications incorporate a number of geometric design aids, such as 3D reference grids, to make it easy to position structural elements accurately within the 3D model.
Where possible, the Model applications create and maintain connectivity of the structural network automatically.
Where possible, the Model applications create and maintain connectivity of the structural network automatically.
Non-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.
Non-standard structural components, such as complex panels and floor plates, may be created by defining the required shape as a 2D profile and then extruding this to the desired thickness.
Negative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.
Negative primitives and shapes may be used in the structural catalogue to define complex joint geometry and end preparations for structural sections, so that weld preparations and fitting allowances can be modelled easily.
Templates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.
Templates may be used to define the basic structure of built-up girders and similar components, so that the detailed design of such items becomes a matter of inputting the required dimensional and positional data.
Multiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.
Multiple copies of design components may be created by specifying the number of copies required and their relative positions and orientations. For example, a complete roof structure can be created by designing a single roof truss and then, in one operation, making as many copies as are necessary to support the length of the roof, with each truss displaced by a given distance relative to the preceding one.
Much repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.
Much repetitive work can be avoided in symmetrical designs by making copies of interconnected parts of the structure and reflecting them about specified axes, so that the design pattern is repeated as required.
Joint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.
Joint positions may be finely adjusted to make sure they are assembled accurately, using any standard datum line to define the precise alignment of a joint with its attached sections.
Sections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The ‘macrostructure’ (for example, complete areas to be covered) can be designed first and then subdivided into a manageable ‘microstructure’ for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.
Sections and panels (for example, wall plates and floor plates) may be divided at intersections, after the overall size and shape have been defined, without affecting any of their logical interconnections. The ‘macrostructure’ (for example, complete areas to be covered) can be designed first and then subdivided into a manageable ‘microstructure’ for fabrication purposes at a later stage (typically, to make the most efficient use of stock panel sizes). The edges of panels may be notched to fit around section profiles, and the edges of adjacent panels may be shaped such they interlock automatically.
Penetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.
Penetrations may be created as catalogue elements. A penetration can incorporate appropriate sleeving or kick plates, and may be inserted into a structural section or panel as a complete entity, with the dimensions and position of the penetration derived automatically from the dimensions of the pipe/duct/cable tray passing though it.
Multi-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.
Multi-disciplinary clash checks can be carried out at any stage of the design, thus avoiding spatial conflicts within the overall 3D model which can be expensive to rectify at the construction stage. These clash checks are particularly important where different features of the 3Dmodel are under the control of different designers.
At any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).
At any stage of the design, reports can be created listing specified data from the current database. A standard report template can be specified, so that lists of commonly-required information can be derived very quickly, or report format can be designed to suit a particular need. The resultant output, which can include data from any design discipline, sorted as required, can be either displayed on the screen or sent to a file (for storage and/or for printing).
Sections
Plates
Walls and Floors
Stairs Ladders and Handrails
Sections
Sections
Plates
Plates
Walls and Floors
Walls and Floors
Stairs Ladders and Handrails
Stairs Ladders and Handrails

Model


Sets the structural application default options for connectivity tolerances, miter tolerance, joint dominance and connection colours.

The Connectivity Tolerances part of the Structural Settings window sets the default tolerances for structural connections.
Node merge radius
Input a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.
Maximum depth offset
Input a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.
Node merge radius
Input a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.
Maximum depth offset
Input a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.
The miter Tolerance part of the Structural Settings window sets the default tolerances for miterd sections.
Maximum offset
Input a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.
Maximum offset
Input a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.
The Joint Dominance Default part of the Structural Settings window sets the default joint connection properties for connected sections.
False
Select the option button to define created joints as subordinate.
True
Select the option button to define created joints as dominant.
False
Select the option button to define created joints as subordinate.
True
Select the option button to define created joints as dominant.
Refer to Dominant and Subordinate Connections for further information.
The Stair Flight Calculate Mode part of the Structural Settings window sets the default properties for creating edge to calculated position stair flights.
False
Select the option button to turn edge to calculated position stair flight functionality off.
True
Select the option button to turn edge to calculated position stair flight functionality on.
False
Select the option button to turn edge to calculated position stair flight functionality off.
True
Select the option button to turn edge to calculated position stair flight functionality on.
Refer to for further information.
The Section Default Settings part of the Structural Settings window sets the default Memberline property for creating sections.
Select the Default member line to justification line check box to create structural sections with a Memberline property identical to the Justification property defined in the Default Section Specification.

If the Default member line to justification line check box is not selected, the Memberline property of created structural sections is set to NA.

Refer to Default Section Specification for further information.
The Check Connection Colours part of the Structural Settings window sets the default display colours for queried connections.
Both ends connected
Displays the default colour for elements that are connected at both ends.
Click the colour palette to modify the default display colour.
Neither end connected
Displays the default colour for elements that are not connected at either end.
Click the colour palette to modify the default display colour.
One end connected
Displays the default colour for elements that are connected at one end.
Click the colour palette to modify the default display colour.
Both ends connected
Displays the default colour for elements that are connected at both ends.
Click the colour palette to modify the default display colour.
Neither end connected
Displays the default colour for elements that are not connected at either end.
Click the colour palette to modify the default display colour.
One end connected
Displays the default colour for elements that are connected at one end.
Click the colour palette to modify the default display colour.
The Weld Representation part of the Structural Settings window sets the default display settings and tolerances for welds.
Weld Visible
Select the check box to display welds in the 3D view.
Deselect the check box to turn off the display of welds in the 3D view.
Size Proportional to connection
Select the check box to control the display size of welds in proportion to the connection in the 3D view.
Move the Proportional Size slider to define the size of the weld.
Default Size
Input a dimensional value in the field to control the display size of welds in 3D view using an explicit value.
The functionality becomes available when the Size Proportional to connection check box is deselected.
Note:
Inserting a value of 0mm removes the display of welds from the 3D view.
Maximum Tolerance
Input a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.
Weld Visible
Select the check box to display welds in the 3D view.
Deselect the check box to turn off the display of welds in the 3D view.
Size Proportional to connection
Select the check box to control the display size of welds in proportion to the connection in the 3D view.
Move the Proportional Size slider to define the size of the weld.
Default Size
Input a dimensional value in the field to control the display size of welds in 3D view using an explicit value.
The functionality becomes available when the Size Proportional to connection check box is deselected.
Maximum Tolerance
Input a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.
Click Reset to revert to the values applied when the Structural Settings window was opened.
Click Apply to accept the default values.
Node merge radius
Input a dimensional value in the field to define the tolerance at which primary or secondary nodes are merged into a single node upon creation.
Maximum depth offset
Input a dimensional value in the field to define the maximum physical distance between elements that are connected or disconnected using dynamic connectivity. The clasher functionality evaluates the value; if elements are not within the tolerance range, they are not connected. Elements that are outside of the tolerance range when moved are disconnected.
Maximum offset
Input a dimensional value in the field to define the vertical offset tolerance between the justification lines of miterd sections when they are not co-planar.
False
Select the option button to define created joints as subordinate.
True
Select the option button to define created joints as dominant.
False
Select the option button to turn edge to calculated position stair flight functionality off.
True
Select the option button to turn edge to calculated position stair flight functionality on.
Both ends connected
Displays the default colour for elements that are connected at both ends.
Click the colour palette to modify the default display colour.
Neither end connected
Displays the default colour for elements that are not connected at either end.
Click the colour palette to modify the default display colour.
One end connected
Displays the default colour for elements that are connected at one end.
Click the colour palette to modify the default display colour.
Weld Visible
Select the check box to display welds in the 3D view.
Deselect the check box to turn off the display of welds in the 3D view.
Size Proportional to connection
Select the check box to control the display size of welds in proportion to the connection in the 3D view.
Move the Proportional Size slider to define the size of the weld.
Default Size
Input a dimensional value in the field to control the display size of welds in 3D view using an explicit value.
The functionality becomes available when the Size Proportional to connection check box is deselected.
Note:
Inserting a value of 0mm removes the display of welds from the 3D view.
Maximum Tolerance
Input a dimensional value in the field to define the maximum allowed distance for the creation of welds between panel edges or between panel edges and section edges. The default value is 10mm.
Note:
Inserting a value of 0mm removes the display of welds from the 3D view.

Dominant and Subordinate Connections
Default Section Specification
Connectivity Tolerances
Structural Settings
Node merge radius
Maximum depth offset
Tolerance
Structural Settings
Maximum offset
Joint Dominance Default
Structural Settings
False
True
Dominant and Subordinate Connections
Stair Flight Calculate Mode
Structural Settings
False
True

Section Default Settings
Structural Settings
Default member line to justification line
Default member line to justification line
Default Section Specification
Check Connection Colours
Structural Settings
Both ends connected
Neither end connected
One end connected
Weld Representation
Structural Settings
Weld Visible
Size Proportional to connection
Proportional Size
Default Size
Size Proportional to connection
Note:
Maximum Tolerance
Reset
Structural Settings
Apply


All database elements are owned by other elements, therefore elements must be created in a strict order.
The following database elements are common to all Model disciplines:
World
Site
Zone.
World
World
Site
Site
Zone.
Zone.

Model


Below the zone level of the hierarchy, there are three common administrative elements that are only available for selection in the four applications under structures:
Section and panel elements can be created using grid storage mode which allows for the automatic creation of structural hierarchy elements. Refer to Section and Panel Storage for further information.
Elements created in grid storage mode refer to grid planes and are created as FRMW members. FRMW elements are created automatically when required.
STRU elements refer to a reference grid and are automatically created when the first element is positioned on a new reference grid (not associated with a STRU).
If the current element is a World, SITE or ZONE, elements are automatically created when the first element is positioned on a new reference grid (not associated with a STRU).
Structure (STRU)
Framework (FRMW)
Sub-Frame (SBFR).
Structure (STRU)
Structure (STRU)
Framework (FRMW)
Framework (FRMW)
Sub-Frame (SBFR).
Sub-Frame (SBFR).

Section and Panel Storage
Section and Panel Storage


Creates a structure database element.
A structure element is an administrative element that can own a number of framework elements, this allows structures to be separated for ease of modelling and reporting.
Before creating a structure element, the correct database elements must already be present in the Model Explorer, that is a World, Site and Zone must exist. If this is not the case, refer to Getting Started with Plant for a detailed explanation of creating these standard elements.

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.
Purpose
Allows you to input the purpose of the structure element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Structure Properties for further information.
OK
Click OK to create the structure element in the Model Explorer and close the Create Structure window.
Cancel
Click Cancel to discard any inputs and close the Create Structure window.
Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.
Purpose
Allows you to input the purpose of the structure element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Structure Properties for further information.
OK
Click OK to create the structure element in the Model Explorer and close the Create Structure window.
Cancel
Click Cancel to discard any inputs and close the Create Structure window.

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the structure element or select Autoname.
Purpose
Allows you to input the purpose of the structure element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Structure Properties for further information.
OK
Click OK to create the structure element in the Model Explorer and close the Create Structure window.
Cancel
Click Cancel to discard any inputs and close the Create Structure window.

Structure Properties
Name/Autoname
Name
Autoname
Purpose
Attributes
Attributes
Structure Properties
OK
OK
Create Structure
Cancel
Cancel
Create Structure


The Properties window displays the default properties for a structure element, modify as required. Refer to Properties for further information.

The general and positional properties of STRU elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.
Geometry
Grid reference
Displays the name of the associated reference grid.
A Nulref value represents a structure element that is not associated with a reference grid.
Geometry

Grid reference
Displays the name of the associated reference grid.
A Nulref value represents a structure element that is not associated with a reference grid.

Geometry
Grid reference
Displays the name of the associated reference grid.
A Nulref value represents a structure element that is not associated with a reference grid.

Properties
Modify Section Properties
Properties
.
Properties
Modify Section Properties
Geometry
Grid reference
Nulref


Creates a framework database element.
A framework element is an administrative element that can own a number of components that form a structure. A complex structure can be divided into logical frameworks for ease of modelling and reporting.
The database elements that represent physical structural components are:

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.
Purpose
Allows you to input the purpose of the framework element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Framework Properties for further information.
OK
Click OK to create the framework element in the Model Explorer and close the Create Framework window.
Cancel
Click Cancel to discard any inputs and close the Create Framework window.
Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.
Purpose
Allows you to input the purpose of the framework element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Framework Properties for further information.
OK
Click OK to create the framework element in the Model Explorer and close the Create Framework window.
Cancel
Click Cancel to discard any inputs and close the Create Framework window.

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the framework element or select Autoname.
Purpose
Allows you to input the purpose of the framework element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Framework Properties for further information.
OK
Click OK to create the framework element in the Model Explorer and close the Create Framework window.
Cancel
Click Cancel to discard any inputs and close the Create Framework window.
Generic Section (GENSEC)
Panel (PANE)
Stair Flight (STRFLT)
Handrail (HANDRA)
Rung Ladder (RLADDR).
Generic Section (GENSEC)
Generic Section (GENSEC)
Panel (PANE)
Panel (PANE)
Stair Flight (STRFLT)
Stair Flight (STRFLT)
Handrail (HANDRA)
Handrail (HANDRA)
Rung Ladder (RLADDR).
Rung Ladder (RLADDR).

Framework Properties
Name/Autoname
Name
Autoname
Purpose
Attributes
Attributes
Framework Properties
OK
OK
Create Framework
Cancel
Cancel
Create Framework


The Properties window displays the default properties for a framework element, modify as required. Refer to Properties for further information.

The general and specification properties of FRMW elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.
Geometry
Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a framework element that is not associated with a grid plane.
Geometry

Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a framework element that is not associated with a grid plane.

Geometry
Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a framework element that is not associated with a grid plane.

Properties
Modify Section Properties
Properties
Properties
Modify Section Properties
Geometry
Grid reference
Nulref


Creates a sub-frame database element.
A sub-frame element is an optional administrative element that can own a number of components that form a structure. A complex framework can be divided into logical sub-frameworks for ease of modelling and reporting.

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.
Purpose
Allows you to input the purpose of the sub-frame element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Sub-Frame Properties for further information.
OK
Click OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.
Cancel
Click Cancel to discard any inputs and close the Create Sub-Frame window.
Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.
Purpose
Allows you to input the purpose of the sub-frame element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Sub-Frame Properties for further information.
OK
Click OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.
Cancel
Click Cancel to discard any inputs and close the Create Sub-Frame window.

Name/Autoname
Select Name from the drop-down list, this allows you to input the name of the sub-frame element or select Autoname.
Purpose
Allows you to input the purpose of the sub-frame element. The window displays the default option unset.
Attributes
Click to display the Attributes window. Refer to Sub-Frame Properties for further information.
OK
Click OK to create the sub-frame element in the Model Explorer and close the Create Sub-Frame window.
Cancel
Click Cancel to discard any inputs and close the Create Sub-Frame window.

Sub-Frame Properties
Name/Autoname
Name
Autoname
Purpose
Attributes
Attributes
Sub-Frame Properties
OK
OK
Create Sub-Frame
Cancel
Cancel
Create Sub-Frame


The Properties window displays the default properties for a sub-frame element, modify as required. Refer to Properties for further information.

The general and specification properties of SBFR elements are identical to GENSEC properties. Refer to Modify Section Properties for further information.
Geometry
Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a sub-frame element that is not associated with a grid plane.
Geometry

Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a sub-frame element that is not associated with a grid plane.

Geometry
Grid reference
Displays the name of the associated grid plane.
A Nulref value represents a sub-frame element that is not associated with a grid plane.

Properties
Modify Section Properties
Properties
Properties
Modify Section Properties
Geometry
Grid reference
A Nulref


To make sure design consistency and conformity with company standards, the basic definitions of all items which can be used in the structural design are held in a Catalog database. The database holds definitions of all available profiles and materials for structural columns/beams/bracing, all standard types of joint, and all auxiliary fittings. When an item is added to a 3D model, the item position and orientation is stored in the database, but the physical properties of the item are specified by the setting up of a cross-reference (called a Specification Reference or SpecRef) which points to an appropriate entry in the Catalog database.

Catalog
Specification Reference
SpecRef
Catalog


The Sections application allows you to create and modify structural sections. Fittings and joints can be specified and section connections defined.


Before a structure can be designed, various settings must be defined to determine, for example, the default structural components for creation of structural sections.


Sets the default specification for the creation of structural sections. The default specification fields can be populated with values from a picked section. The default specification field values can also be applied to existing sections.
The following default structural components, can be defined:

A series of drop-down lists allows you to define the default section specification.
Structural Classification
Input a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.
Default Material
Input a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.
The materials drop-down list is populated with the materials that are associated with the currently selected specification.
Default Justification
Input a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.
For example, select CTOP from the drop-down list to justify the section to the centre top P-line.
The justification drop-down list is populated with the justification options that are associated with the currently selected profile.
Functionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information
Profile Specification
Input a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.
When a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.
Generic Type
Input a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.
The type drop-down list is populated with the section types that are associated with the currently selected specification.
Profile
Input a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.
The profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.
Profile Properties
Allows you to modify the property values of the default profile. Refer to Modify Properties for further information.

Structural Classification
Input a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.

Default Material
Input a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.
The materials drop-down list is populated with the materials that are associated with the currently selected specification.

Default Justification
Input a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.
For example, select CTOP from the drop-down list to justify the section to the centre top P-line.
The justification drop-down list is populated with the justification options that are associated with the currently selected profile.
Functionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information

Profile Specification
Input a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.
When a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.

Generic Type
Input a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.
The type drop-down list is populated with the section types that are associated with the currently selected specification.

Profile
Input a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.
The profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.

Profile Properties
Allows you to modify the property values of the default profile. Refer to Modify Properties for further information.
Copy Defaults from Existing Profile
Click to populate the default section specification fields with values from a picked section.
You are prompted to Select section
Click to identify a section using a cursor pick in the 3D view.
The Class, Material, Justification, Spec, Type and Profile fields are populated with the default values of the identified section.
Apply Defaults to Existing Profiles
Applies the values in the default section specification fields to pre-selected sections.
The values from the Structural classification, Default material, Default justification, Profile specification, Generic type and Profile fields are applied.
Default values can only be applied to GENSEC or SCTN elements.
If a selected section is locked or claimed by another user, the default section specification values cannot be applied.
Structural Classification
Input a value in the field or select the default structural classification from the drop-down list to be used for the creation of structural sections.
Default Material
Input a value in the field or select the default material from the drop-down list to be used for the creation of structural sections.
The materials drop-down list is populated with the materials that are associated with the currently selected specification.
Default Justification
Input a value in the field or select the default justification from the drop-down list to be used for the creation of structural sections.
For example, select CTOP from the drop-down list to justify the section to the centre top P-line.
The justification drop-down list is populated with the justification options that are associated with the currently selected profile.
Functionality is available to create structural sections with a Memberline property identical to the Justification property. Refer to Structural Defaults for further information
Profile Specification
Input a value in the field or select the default specification from the drop-down list to be used for the creation of structural sections.
When a new default specification is selected, the type and profile drop-down lists are populated with the components that were used when the specification was most recently selected.
Generic Type
Input a value in the field or select the default type from the drop-down list to be used for the creation of structural sections.
The type drop-down list is populated with the section types that are associated with the currently selected specification.
Profile
Input a value in the field or select the default profile from the drop-down list to be used for the creation of structural sections.
The profile drop-down list is populated with the section types that are associated with the currently selected specification. The three profiles that were most recently used in the current session display at the top of the drop-down list.
Profile Properties
Allows you to modify the property values of the default profile. Refer to Modify Properties for further information.
Structural classification
Default material
Default justification
Profile specification
Generic type
Profile
Profile properties
Structural classification
Structural classification
Default material
Default material
Default justification
Default justification
Profile specification
Profile specification
Generic type
Generic type
Profile
Profile
Profile properties
Profile properties
Note:
The prompt does not display if the section element is already selected.

Structural Defaults
Modify Properties
Structural Classification
Default Material
Default Justification
Structural Defaults
Profile Specification
Generic Type
Profile
Profile Properties
Modify Properties
Copy Defaults from Existing Profile
Select section
Note:
Apply Defaults to Existing Profiles


Snap points allow you to position the start point or end point of a created section. Snap points can point to a node, item, Pline or grid. Snap points can also be directional, for example, allowing you to create a section perpendicular to an existing element. You can define the snap points that are available for section creation. Refer to Object Snaps and P-line Filters for further information.

Object Snaps and P-line Filters
Object Snaps and P-line Filters


Stores structural sections or panels in a specific area of the hierarchy. Structural sections or panels can be associated with a grid plane or a framework/sub-framework element.
If a storage area is not defined prior to creation of a section or panel, an error message displays summarizing the problem.

There are two different modes available for the storage of structural elements:
The state of the structural storage setting (grid storage or manual storage) is saved and restored between sessions.
If the structural storage area is locked, then the structure and framework are also saved and restored between sessions.
The serialisation file is stored in the AVEVA_DESIGN_USER directory, and is named structural-storage.pmldat.
Grid Storage
Manual Storage
Grid Storage
Grid Storage
Manual Storage
Manual Storage

Grid Storage
Manual Storage
Grid Storage
Manual Storage


Sets the structure and grid plane that sections and panels are associated with.

The Structures and Grid Plane drop-down lists are populated with the association properties of the currently selected section or panel.
Structures
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Grid Plane
Displays the name of the grid plane that is associated with the currently selected section or panel.
Select from the drop-down list to identify an alternative grid plane.
Grid Plane Selection
Select Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.
Select Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.
Structures
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Grid Plane
Displays the name of the grid plane that is associated with the currently selected section or panel.
Select from the drop-down list to identify an alternative grid plane.
Grid Plane Selection
Select Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.
Select Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.
If a section or panel is moved, the associated grid storage area is updated to reflect the new grid plane.
If a section or panel is copied, the associated grid storage area is updated to reflect the new grid plane.
If multiple sections or panels are moved or copied and one of the grid storage areas is locked, the moved/new sections/panels are all associated with the locked grid storage area.
Structures
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Grid Plane
Displays the name of the grid plane that is associated with the currently selected section or panel.
Select from the drop-down list to identify an alternative grid plane.
Grid Plane Selection
Select Lock from the drop-down list to prevent grid storage area modification. The Structure and Grid Plane drop-down lists become inactive.
Select Unlock from the drop-down list to allow grid storage area modification. The Structure and Grid Plane drop-down lists become active.

Structures
Grid Plane
Structures
Grid Plane
Grid Plane Selection
Lock
Structure
Grid Plane
Unlock
Structure
Grid Plane


Sets the structure and framework/sub-framework elements that sections or panels are associated with.

Select a FRMW or SBFR element in the Model Explorer to populate the Structure and Storage drop-down lists.
Structure
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Storage Area
Displays the name of the FRMW or SBFR element that owns the currently selected section or panel.
Select from the drop down list to identify an alternative FRMW or SBFR.
Storage Selection
Select Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.
Select Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.
Structure
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Storage Area
Displays the name of the FRMW or SBFR element that owns the currently selected section or panel.
Select from the drop down list to identify an alternative FRMW or SBFR.
Storage Selection
Select Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.
Select Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.
If a section or panel is moved, the associated manual storage area is unchanged.
If a section or panel is copied, the new section is associated with the same manual storage area as the original section.
If multiple sections or panels are moved or copied and one of the manual storage areas is locked, the moved/new sections/panels are all associated with the locked manual storage area.
Structure
Displays the name of the STRU element that is associated with the currently selected section or panel.
Select from the drop down list to identify an alternative STRU.
Storage Area
Displays the name of the FRMW or SBFR element that owns the currently selected section or panel.
Select from the drop down list to identify an alternative FRMW or SBFR.
Storage Selection
Select Lock from the drop-down list to prevent storage area modification. The Structure and Storage Area drop-down lists become inactive.
Select Unlock from the drop-down list to allow storage area modification. The Structure and Storage Area drop-down lists become active.

Structure
Storage
Structure
Storage Area
Storage Selection
Lock
Structure
Storage Area
Structure
Storage Area