Section Profiles sized by Design Parameters
- Last UpdatedJan 23, 2023
- 2 minute read
To export or import a profile defined by design parameters to AVEVA Bocad Steel, you need to add a line at the bottom of the mapping file as follows:
|
PDMS profile names |
BOCAD profile name |
Standard Key word |
Shape Code |
|
For example: |
|||
|
CATREF SPREF |
PRS@2@4@1@3 |
EUR |
1 |
Where
PDMS profile name gives the Catalogue and Specification names of the profile used in PDMS.
BOCAD profile name is the name of the AVEVA Bocad Steel profile followed by design parameter numbers prefixed by @ symbol
Standard Key word is the country code for the type of standard.
Shape Code is the profile number given by the table above.
If the profile name is not found earlier in the mapping file, the application will try to map the profile to the PDMS profile finding the name that matches the prefix before the first @ in the name.
If a match is found, the order of the parameters will be used to set the corresponding design parameters in PDMS.
Below is an extract of the mapping file for just parameterized profiles.

There are three formats for Profile mapping files, the first two formats may be space or comma separated. And are indicated as such by setting the !!bocProfSep variable as !!bocSpaceSep or !!bocCommaSep.
The first has been described here, each line in the mapping file contains 4 fields - the AVEVA Catalogue™ or specification profile name, the external profile name, the country code and the shape code. Interpretation of the first field depends upon the !!bocProfMapRef variable as 'SPRE' or 'CATR'.
In this format, each line in the mapping file contains 5 fields - the AVEVA Catalogue™ profile name, - the AVEVA specification profile name, the external profile name, the country code and the shape code. Which of the AVEVA columns is picked also depends upon the !!SDNFProfMapRef variable. In order to distinguish this file from the previous format, the header line has an additional "version" field.
For example
|
AVEVA |
FRAMEWORKS |
2 |
The third, and now preferred, format is the Block format, a space separated file that has been pre-processed to facilitate more rapid parsing. Again, each record has 5 fields selectable according to the !!bocProfMapRef variable. This file has a header with more fields describing the column sizes for the file.
For example
|
AVEVA |
FRAMEWORKS |
5 19 19 16 3 3 |
This file type is indicated by setting the !!bocProfSep variable to be !!bocBlockSep, refer to AVEVA ABSI/SDNF Mapping File Convertor for further information.