Catalog UDAs
- Last UpdatedJan 24, 2023
- 2 minute read
Because the APS and ACP projects are separate projects and the catalogue is a foreign database in the APS project, it is necessary to have two separate groups of UDAs to apply to the relevant data
All UDAs are present in the ACP project:
The Catalogue UDA's are stored in /PSI-CATALOGUE-UDAS
|
UDA Name |
Type |
Element Types |
Description |
|---|---|---|---|
|
:MATNUM |
REAL |
SOLI SMTE |
Used to store the piping material number for transfer to CAESAR II. The configuration defaults will define which one is used. |
|
:TWALL |
REAL |
TUBD |
Used to store the tube wall thickness in the properties database. |
|
:CWALL |
REAL ARRAY[4] |
CMPD |
Used to store an array of component wall thicknesses. For example, reducers and crosses which can have a different wall thickness at each p-point. |
|
:PSIWEIGHT |
REAL |
ALLP, ANCILLARY, LUANCILLARY, TRANCILLARY |
Used to add an override on individual components if the catalogue weight is not available. |
|
:SPWeight |
REAL |
SPCOMPONENT |
Spec component weight. |
The Design UDA's are stored in /PSI-DESIGN-UDAS:
|
UDA Name |
Type |
Element Types |
Description |
|---|---|---|---|
|
:PSISYSTEM |
REF ARRAY |
PIPE BRAN |
Used to store the contents of a stress group. |
|
:PSIDATE |
STRING |
PIPE |
Used to store the data the pipe was sent for stressing. |
|
:PSISifNumber |
REAL |
CATEGORY |
Stores the SIF number. |
|
:NODETYPE |
REAL |
ANCILLARY, ATTACHMENT, BEND, ELBOW, FLANGE, LUANCILLARY, REDUCER, TEE, TRANCILLARY |
Used to store restraint type number to match the CAESAR II support types. |
|
:NODEGAP |
REAL |
ANCILLARY, ATTACHMENT, BEND, ELBOW, FLANGE, LUANCILLARY, REDUCER, TEE, TRANCILLARY |
Used to store the restraint gap. |
|
:NODESTIFF |
REAL |
ANCILLARY, ATTACHMENT, BEND, ELBOW, FLANGE, LUANCILLARY, REDUCER, TEE, TRANCILLARY |
Used to store the restraint stiffness. |
|
:NODEFRICTION |
REAL |
ANCILLARY, ATTACHMENT, BEND, ELBOW, FLANGE, LUANCILLARY, REDUCER, TEE, TRANCILLARY |
Used to store the restraint friction. |
The PSI installation provides macros for building the UDAs depending on the required installation:
For an installation with foreign catalogues like the one described above, there are two macros ‑ one for the catalogue and properties db and one for the design dbs.
These are:
%aveva_design_installed_dir%\asso_products\psi\data\PSICATAUDAS.MAC
%aveva_design_installed_dir%\asso_products\psi\data\PSIDESIGNUDAS.MAC
In a project where the catalogue and design dbs are in the same project, the UDAS can be combined into one Lexicon database. In this case, there is a single macro to build all of the UDAs.
This is:
%aveva_design_installed_dir%\asso_products\psi\data\PSIUDAS.MAC
CAESAR II 2018 and beyond allow the transfer of six different support restraint types, earlier versions allow the transfer of four different support restraint types. To enable the CAESAR II 2018 support restraint type transfer functionality, there is a single macro to update the UDAs in the LEXICON database.
This is:
%aveva_design_installed_dir%\asso_products\psi\data\PSIUDAUPDATE2018.MAC