User-Defined Identifiers for PDMS Objects (Design, Hull Design and Isodraft)

It is possible to override the default naming by modifying the code in the PML object file VNETxmlOrigName<Project Code>.pmlobj (see AVEVA NET Export - Settings Window).

It is possible that the identifier of an object in PDMS does not match the identifier of the same object in another system, or the identifier which is being used project wide. For example, the identifier of a pipeline on a P&ID might be of the form 6"-AI-502100-AB3-PP-30IS while the pipe in PDMS is called 6"-AI-502100-AB3, but on the project the Pipe is known as AI-502100. In this situation, the name exported from PDMS can be changed to produce the project wide identifier.

The export process assigns two identifiers to each PDMS object. The main identifier is the PDMS name without the leading slash for example, 6&amp;-AI-502100-AB3. It is given a context of PROJECTCONTEXT which is replaced by the name of the ‘Top Object during processing by the VNET Import Controller.

The second identifier is the original PDMS name for example, /6&amp;-AI-502100-AB3. This is given the context VPD in the context of PROJECTCONTEXT. This is needed by AVEVA NET for picking to work with PDMS documents. All documents referring to the original PDMS name, with a slash, also have the extra PDMS context.

It is the main identifier that can be modified, by including a file in the %PMLLIB%\vnet\setting directory called VNETxmlOrigName<Project Code>.pmlobj, if this file does not exist then the original name will be used.