Data from the STD File

It is assumed that an STD file, named D:\Staad\model.std, must be imported into AVEVA E3D Design. The STD file contains (in the example, some text has been removed for visual representation):

START JOB INFORMATION

ENGINEER DATE 1-Jan-11

END JOB INFORMATION

UNIT METER kN

INPUT WIDTH 79

JOINT COORDINATES

3 7.785 8.930 1.510

4 7.785 5.880 1.510

.......

MEMBER INCIDENCES

10044 45 22

........

DEFINE MATERIAL START

ISOTROPIC STEEL

……

END DEFINE MATERIAL

START USER TABLE

TABLE 1 D:\Staad\map1.txt

TABLE 2 D:\Staad\map2.txt

END

MEMBER PROPERTY BRITISH

10001 10004 10007 10010 10013 10016 10019 TABLE ST UC305X305X240

......

MEMBER PROPERTY

31 50 33 51 36 52 53 38 54 55 40 56 57

UPTABLE 1 H1800X400X30X40

43 58 59 60 44 45 61 46 62 47 63 49 64 -

65 10044 UPTABLE 2 90_OD_5

In this STD file, find the records after the keyword "START USER TABLE":

START USER TABLE

TABLE 1 D:\Staad\map1.txt

TABLE 2 D:\Staad\map2.txt

END

The STD file references two USER PROVIDED TABLEs: D:\Staad\map1.txt and D:\Staad\map2.txt.

The data in the file D:\Staad\map1.txt is:

UNIT METER KN

Wide Flange

H2000X400X20X40

0.0704 2 0.02 0.4 0.04 0.0425336 0.000427947 2.21867e-005 0.04 0.02112

H1800X400X30X40

0.0836 1.8 0.03 0.4 0.04 0.0375062 0.000430537 3.25467e-005 0.054 0.02112

H1600X400X30X40

0.0776 1.6 0.03 0.4 0.04 0.0282526 0.000430087 3.07467e-005 0.048 0.02112

……

The data in the file D:\Staad\map2.txt is:

UNIT METER KN

PIPE

90_OD_5

0.0905 0.0055 0.000729 0.000729

114_OD_6

0.114 0.00602 0.001021 0.001021

……

D:\Staad\map1.txt describes the H sections using a name value, for example, "H1800X400X30X40". D:\Staad\map2.txt describes the PIPE sections using a name value, for example, "90_OD_5".

Note:
The interface uses a single mapping configuration file for importing STD files and exporting AVEVA E3D Design models. A "strong" naming convention must be used for profiles in Staad Pro, rules using parameters can then be set up in a clear and simple way, achieving "one-to-one" mapping.

Note:
In cases when the profile naming rules result in a N-to-One mapping from STD profiles to AVEVA E3D Design specifications, incorrectly mapped profile names may be present. When the model is exported, the interface uses the first rule applicable.