Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ E3D Design

Alternative Item codes for Bolts

  • Last UpdatedAug 19, 2025
  • 2 minute read

Alternative item codes for bolts are taken from UDAs set on DTAB elements, not on the SPCOM like other elements (see Alternative Item Codes).

Note: For additional bolting items such as washers and nuts, the UDA must be set on SPCOM because these items do not have associated DTAB elements.

Alternative item codes for bolts are set up as follows:

  • The SBOLT elements must have NSTD attributes pointing to the DTAB elements.

  • The names of the UDAs on the DTAB elements must be related to the UDAs set for the SPCOM. For example, if the SPCOM UDAs are named: clienta and :clientb, there could be one set of DTAB UDAs named :clienta1,:clienta2, . and another set of UDAs named clientb1, clientb2, .

  • The item codes are stored in the DTAB UDAs as texts separated by spaces. In recent versions of Dabacon, text length in UDAs is effectively unlimited. (Refer to User Defined Attribute Definitions for details.) Historically the limit was 120 characters, which required splitting the list of item codes across multiple UDAs.

  • For example, if each item code is 10 characters in length, then 11 item codes can be stored in each UDA of the set.

  • The number of item codes stored in each set of UDAs (for example, all the UDAs for clientb) should correspond to the number of elements in the BLEN attribute of the DTAB.

    Notes:
    Normally, the user can use the same SBOLT element for bolts with the same geometry, and the material will be defined in the Specification. When bolts of the same geometry but different materials are used, the user will need to create a DTAB for each SBOLT element and an SBOLT for each Bolt SPCOM if they want to set different item codes.

    The user must make sure that a consistent set of UDAs are set up in the Lexicon database.

The following example shows part of a specification and part of a catalogue. Note that Specon cannot output UDAs in tabular format, and so this example is just for illustration.

Part of Specification

TYPE   NAME    ...   BLTREF  :clienta  :clientb

FLAN  */FL100  ...            F100L    FLAN100

BOLT  */BL100  ...   /BL100   unset    unset

Part of Catalog

SBOLT/BL100
   NSTD /M16

DTAB/M16

   BLEN 90 100 110 120 130 140 150 160

   :clientb1 AB99XA AB99ZB AB29ZC CA33QD

   :clientb2 CA99PE JX34YF JY21ZG AC99AH

   :clienta1 B12345 B19432 B21456 B92134 B54321 B45123 B51234 B41592

Related Links
TitleResults for “How to create a CRG?”Also Available in