Wide Flange User Provided Tables
- Last UpdatedDec 18, 2023
- 5 minute read
In this wide flange example, the same profile is described differently in Staad Pro and in AVEVA E3D Design.
Staad Pro Type: Wide Flange
Example: 400X400PG1
|
0.02925 |
1 |
0.015 |
0.3 |
0.025 |
0.00463734 |
0.000112767 |
4.19375e-006 |
0.015 |
0.01 |
|
AX |
D |
TW |
WF |
TF |
IZ |
IY |
IX |
AY |
AZ |
|
AX |
Cross section area. |
|
D |
Depth of the section. |
|
TW |
Thickness of web. |
|
WF |
Width of the top flange (or both flanges when WF1 is not specified). |
|
TF |
Thickness of top flange (or both flanges when TF1 is not specified). |
|
IZ |
Moment of inertia about local z-axis (usually strong axis). |
|
IY |
Moment of inertia about local y-axis. |
|
IX |
Torsional constant. |
|
AY |
Shear area in local y-axis. If zero, shear deformation is ignored in the analysis. |
|
AZ |
Shear area in local z-axis. If zero, shear deformation is ignored in the analysis. |
|
WF1 |
(Optional) Width of the bottom flange. The width of the top flange will be used if this value is not specified. |
|
TF1 |
(Optional) Thickness of bottom flange. The thickness of the top flange will be used if this value is not specified. |

E3D Type: DPLG
The equivalent AVEVA E3D Design specification reference is /DP-DPLG.
|
DP No. |
Design Parameter Description |
DKEY |
Data Type |
|
DESP 1 |
Depth |
DPTH |
Geometry |
|
DESP 2 |
Top Flange Width |
WIDA |
Geometry |
|
DESP 3 |
Bottom Flange Width |
WIDB |
Geometry |
|
DESP 4 |
Web Thickness |
WTHK |
Geometry |
|
DESP 5 |
Top Flange Thickness |
FTKA |
Geometry |
|
DESP 6 |
Bottom Flange Thickness |
FTKB |
Geometry |
Mapping File
The mapping file must contain two entries for this example.
The following line is required in the mapping file, below the heading USERTABLES:
TABLE 1 D:\Staad\UPT1.upt
The table number can be any number and is relevant. The file must exist in the specified directory. It can be in a centralized location, project specific, or on a local machine.
The following line is required in the mapping file, below the heading MEMBER PROPERTY:
UPTABLE 1 <d1>X<d2>PG1, DP-DPLG,d1 d2 d3 d4 d5 d6,<d2> <d4> <d4> <d3> <d5> <d5>,0,-90,0
The example table name is 400X400PG1
It is possible to have multiple naming conventions for the same UPTABLE, so it is possible to have additional UPTABLES. For example:
UPTABLE 1 <d1>X<d2>X<d5>X<d4>PG,/DP-DPLG,d1 d2 d3 d4 d5 d6,<d2> <d4> <d4> <d3> <d5> <d5>,0,-90,0
The example table name 1000X300X25X15PG.
It is important that the UPTABLE number 1 is the same.
Table Name Formula
In the first example, the formula after the table number is the Staad Pro table name based on the values of d1 and d2, (section depth, flange width) whether they come from AVEVA E3D Design or Staad Pro.
In the second example, the formula after the table number is the Staad Pro table name based on the values of d1, d2, d5 and d3 (section depth, flange width, flange thickness and web thickness) whether they come from AVEVA E3D Design or Staad Pro.
AVEVA E3D Design Specification Reference
The value is the AVEVA E3D Design specification reference. For example, DP-DPLG, in both examples.
AVEVA E3D Design Parameters
The values are the design parameters to be used in the the formula from AVEVA E3D Design.For example, DESP 1 and DESP 2 in example 1, and DESPs 1,2,5 and 4 in example 2.
The AVEVA E3D Design diagram (at the top of the topic) displays the design parameters:
|
DESP 1 |
Depth |
|
DESP 2 |
Top Flange Width |
|
DESP 5 |
Top Flange Thickness |
|
DESP 4 |
Web Thickness |
Staad Pro Parameters
The values are the parameters to be used in the formula from Staad Pro. For example, <d2> <d4> <d4> <d3> <d5> <d5>
1000X300X25X15PG
|
0.02925 |
1 |
0.015 |
0.3 |
0.025 |
0.00463734 |
0.000112767 |
4.19375e-006 |
0.015 |
0.01 |
|
AX |
D |
TW |
WF |
TF |
IZ |
IY |
IX |
AY |
AZ |
<d2> (D) value is plugged into d1 of the table name formula.
<d4> (WF) value is plugged into d2 of the table name formula.
<d5> (TF) value is plugged into d5 of the table name formula.
<d3> (TW) value is plugged into d4 of the table name formula.
User Provided Table File Contents
The user provided table file must contain all the required sizes in AVEVA E3D Design for modelling and Staad Pro for analysis. The file must start with the following lines, the provided example is for a metric project:
UNIT METER KN
WIDE FLANGE
Followed by a list of the required sizes. For example:
400X400PG1
0.0291 0.4 0.015 0.4 0.03 0.00087233 0.00032 7.58e-006 0.006 0.016
400X400PG2
0.0384 0.4 0.02 0.4 0.04 0.00109568 0.00042688 1.792e-005 0.008 0.032
Parameters 1 and 6 onwards are required to be output to Staad Pro in the STD file but are not used in AVEVA E3D Design.
Export
On export, the SAI looks for all ISECTs with the specification reference set to /DP-DPLG and with the same design parameter settings.
The SAI looks at all the design parameter settings in the formula and checks them against the values under each table name, to pick the correct table name.
In the example, the depth and flange width are the same, 400mm and 400mm. The web and flange thicknesses are 15mm and 30mm in the first example, and 20mm and 40mm in the second example. It is important to note that the parameter settings are used to choose the table name, not the table name itself. Therefore, the table that is chosen is based on all the parameters not just the parameters used in the table number code.
If the Staad Pro table name cannot be found, or if the values are not the same, the export functionality outputs an appropriate warning. If all checks are satisfied, the following lines are output to the STD file.
START USERTABLE 2
TABLE 2 %aveva_design_user%\saifiles\UPT2.upt
END
and
MEMBER PROPERTY
20006 20008 UPTABLE 2 400X400PG1
20005 20007 UPTABLE 2 1000X300X25X15PG
Import
On import, the SAI checks that the table code exists in the .upt file, followed by a calculation to set the design parameters.
Looking at the part of the UPTABLE line in the mapping file:
d1 d2 d3 d4 d5 d6,<d2> <d4> <d4> <d3> <d5> <d5>
The SAI plugs the <d2> value into the DESP 1 value of the ISECT, the <d4> value is plugged into DESP 2 value of the ISECT, etc
The SAI checks that all values match a table name in the UPTABLE file.
If the UPTABLE table does not exist in the file, the ISECT is created with specification reference /DP-DPLG and the design parameters are left unset.