Intergraph Smart 3D and PDS Codelist Value Mapping - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Construction Version
8
Smart Materials/Smart Reference Data Version
10.1

The Intergraph Smart 3D codelists are different from the PDS codelists. Thus, you cannot export the same specification to PDS and Smart 3D.

The PDS 10.15 PDS S3D Codelist Value Mapping screen can be used to specify the mapping of Smart 3D codelists with PDS codelists.

In the Codelist Name box at the top of the screen, you select the codelist that you want to edit from the drop-down list. The related data is displayed. By default, the CL400 codelist is displayed when you open the screen. The available codelists are:

  • CL400 Option Code

  • CL330 End Preparation

  • CL332 Schedule/ Thickness

  • CL576 Table Suffix/ End Standard (Green)

  • CL577 Table Suffix/ End Standard (Red)

  • CL575 Geometry Standard

  • CL550 Operator/ Actuator type

  • CL145 Materials Grade

  • CL578 Weight Code

  • CL180 Fabrication Category

  • CL499 Piping Notes

Enter the Smart 3D value in the S3D Value box and the corresponding PDS value in the PDS Value box. You can type a description or comment in the Comment box. Optionally, enter a short code in the Short Code box. The short code is only used for CL400 Option Code codelists.

The mapping defined on PDS 10.15 is project dependent. The PDS procedure INGR_PDS_S3D_OPTION_CODE uses this mapping. If the same Smart 3D value is mapped to different PDS values in the product group and project and you are logged in to a project, the project relationship is used. When you are logged in to a product group, the product group setting is used.

The procedure can easily be copied and modified in order to update other codelist numbers that appear in the PCD. Only the cl_name value and the field name where the value should be stored need to be updated. For example, in the case of the green end standard, the cl_name needs to be CL576 instead of CL400, and the column name in the PCD table is ts1 instead of opt. Likewise, the other values can be updated in a similar way.