Structural Design
User Guide
SDNF Export/Import
:
Technical Information
: Version Numbers
Version Numbers
The management of the attributes relevant to version numbering and revision control, for example. :SDNFREVNO, :SDNFTRANO and :SDNFTRRVNO, are all performed in the AVEVA E3D™ user interface. The values of these attributes are not taken from the SDNF file. The header, Packet 00, is used to transfer the main TransferLetter for the Configuration object, but the individual items can be managed.
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, Source or Target package or client information.
Because of the fact that AVEVA E3D™ may be multi-user and that several users 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, :SDNFTRANO, is actually an index into a character string returning the equivalent character as the TransferLetter.
Note:
The TransferLetter is cycled. As it passes 'Z' it is 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.
There are rules by which the revision numbering is handled by the interface.
1.
Each Transfer has a Letter - A...Z
2.
Each Revision has a Number - 1,2,3...
3.
Each SITE, GENSEC, SCTN and PANE has 3 UDAs attached
4.
A TransferLetter, for example, 'C',
5.
A RevisionNumber, for example, '2'
6.
A TraRevNumber - A character-wise concatenation of the previous two, for example, 'C.2'
On Transfer from Model:
1.
Increment the element's TransferLetter at the SITE level. for example, 'A' to 'B'.
2.
Reset the SITE's RevisionNumber to '0' and generate the new TraRevNumber -> 'B.0'.
3.
If an entity (GENSEC, SCTN or PANE) has not been transferred from AVEVA E3D™ before, its own TransferLetter is set to be the owning SITE's TransferLetter, this is only done once.
On Transfer into Model:
1.
If an entity (GENSEC, SCTN or PANE) has been changed or is new, set its TransferLetter to be that of the owning SITE and note that there is at least 1 changed item.
2.
Update the entity's (GENSEC, SCTN or PANE) RevisionNumber to be the incremented value of that of the owning SITE, because we haven't yet changed the latter.
3.
Increment the SITE's RevisionNumber, for example, '0' to '1' if any imported entities have changed.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
