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

AVEVA™ E3D Design

Version Numbering

  • Last UpdatedApr 24, 2023
  • 2 minute read

The management of the attributes relevant to version numbering and revision control, that is :FABREVNO, :FABTRANO and :FABTRRVNO, is all performed in the base product user interface. The values of these attributes are not taken from the file. The header is used to transfer the main TransferLetter from the Configuration object, but the individual items are managed as described below.

The Configuration object should not be confused with the Header object. The former is used to store transfer indices - counts of Transfer Numbers and Revision numbers. These are for the whole database. The latter is used to store specific information pertaining to the transfer in question - for example: client information.

Because of the fact that the base product may be multi-user and that several user’s may be concurrently accessing the design databases at any one time, there may be several Configuration objects, one for each possible MDB:User combination. At the start of the Export or Import process, a poll is taken of ALL these Configuration objects to determine which is the highwater mark. That is, which is the highest Transfer Number, or Revision Number. We then take that and modify the Configuration object for the current MDB:User. In this way, by polling all objects, we can determine the latest values.

The rules of precedence for the Transfer and Revision numbers are that a Transfer is higher. So that "A.2" is later than "A.1" and "B.1" is later than "A.9".

Note:
The UDA, :FABTRANO, is actually an index into a character string returning the equivalent character as the TransferLetter.

Note:
This TransferLetter is cycled. As it passes 'Z' it will be succeeded by 'A'.

If there are more than 26 Transfers, the letter is recycled so that there may be slight problems at the wrap around.

Below are the rules by which the revision numbering is handled by the interface.

  • Each Transfer has a Letter - A...Z

  • Each Revision has a Number - 1,2,3...

  • Each SITE, GENSEC, SCTN and PANE has 3 UDAs attached

  • A TransferLetter for example: 'C',

  • A RevisionNumber for example: '2'

  1. A TraRevNumber - A character-wise concatenation of the previous two, for example: 'C.2'

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