Inter-DB Macros in AVEVA PDMS/E3D

Inter-DB Macros in AVEVA PDMS/E3D

Access to a DB is usually controlled in such a way that only one user can modify the content of that DB at any one time; that is, only one user can have Write access to the DB. Other users may have simultaneous Read access, depending how access rights have been set up in the ADMIN module. 

Inter-DB macros are created in the following situations (For details refer to the PDMS/E3D Help files):

1- A user in DESIGN attempts to make a connection to an element which is in a Design database to which the user does not have write access.

2- A user in DESIGN attempts to make a connection to an element which is in a multi-write Design database to which the user has write access, but the element is already claimed by another user.

3- A user in ISODRAFT updates REVISION and DETAIL attributes, which need to be stored in the Design database, to which the user has no access.

4- A user in ISODRAFT attempts to create an standard isometric when REPEATABILITY is ON in the related option file. When a pipe is detailed which needs splitting over more than one sheet, ISODRAFT automatically generates split points. Normally this data is not stored, and so if the design is altered and the pipe detailed again, the split points may be in different places. Repeatability allows you to save these split points (Split ATTACHMENTs with ATTYPE attribute is XXXX.) in a macro to be run in DESIGN. This macro stores the split point information in the DESIGN database.

As PDMS/E3D administrator, one responsibility is to check when an Inter-DB macro is generated then after a review, he/she must run that macro into the DESIGN. For example, if the current project is sam, the inter-database macros will be created in directory sammac with filename samnnn.mac.

After all above things, Admin must not change any Inter-DB macros from 3 first above categories (   1      2      3    ), but about the fourth one (   4    ), some changes must be made before running, for ex.:

i) Change all "CONN TO" statements into "FCONN TO" statements.

ii) Change all "NEW ATTA ATTY XXXX SELECT ORI" statements into "NEW ATTA ATTY XXXX ORI SELECT WI STYP ...styp of proper attachment....".

In category 4, the most important thing is that in these macros, the full name of elements are using for reference, so when refer to (below snapshot) ATTACHMENT 16 OF BRANCH /SLP-46-028-B1A1-3"-PT/B1 and then create an attachment there, all full names of next attachments will be changed and if another split attachment need to be placed, it will be created in the wrong place. This is the main reason that so many administrators or designers around the globe, ignore this kind of macros and creates split attachment manually.

No alt text provided for this image

For more information and finding a tool or way to take care of this issue, just see below link:

Refernce: AVEVA Help & Borna iDEES Help


To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics