Create Additional AVEVA NET Associations (OtherNames) (Design and Hull Design)

It is possible to create additional AVEVA NET associations on the items being exported from PDMS by creating a PML object file called VNETxmlOtherName<Project Code>.pmlobj and placing it in the settings folder of vnet under the Marine installations PMLLIB folder, see AVEVA NET Export - Settings Window.

It is possible that you may need to associate an object in Marine to another item within the AVEVA NET project, and rather than manually create the required XML, you can add the associations to items as they are exported from Marine. The association must be a valid association known to the AVEVA NET project.

An example would be that the user needs to associate an In-line Instrument FT-506 with the Pipe 3"-15D-O-66006-BBU3.1 that it is in, as well as being labelled with just its Tag. The identifier (Tag) on a P&ID might be of the form O-66006/FT-506 but in the Marine model and in the AVEVA NET project the identifier of the instrument is FT-506. In Marine it is easy to know the owning pipe so the user can set up the required syntax to add the association when the instrument item is exported from Marine. The associated identifier is in the context of PROJECTCONTEXT, because the identifier generated from the P&ID is in the context of the Project, so all you need to do is convert the Pipe name to be the same as the identifier on the P&ID and to concatenate the Instrument tag to it.

Within the file, you can create as many associations as is needed, the result passed back to the main appware is an array which is part of the VNETxmlOtherName<Project Code>.pmlobj object, and it is defined in the top part of the file, see VNETxmlOtherName Example 2.