VANTAGE Plant Design PDMS VPRM Gateway. User Bulletin. Version Issue 2

Transcription

1 VANTAGE Plant Design PDMS VPRM Gateway User Bulletin Version Issue 2

2

3 PLEASE NOTE: AVEVA Solutions has a policy of continuing product development: therefore, the information contained in this document may be subject to change without notice. AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. While every effort has been made to verify the accuracy of this document, AVEVA Solutions shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance or use of this material. This manual provides documentation relating to products to which you may not have access or which may not be licensed to you. For further information on which Products are licensed to you please refer to your licence conditions. Copyright 1991 through 2006 AVEVA Solutions Limited All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of AVEVA Solutions. The software programs described in this document are confidential information and proprietary products of AVEVA Solutions or its licensors. For details of AVEVA's worldwide sales and support offices, see our website at

4

5 Contents CONTENTS 1 INTRODUCTION UPGRADE Options File HELP DESK REMEDY CALLS OTHER CHANGES Multi-Discipline Supports MDS MTO Disciplines MDS Delete / Rename Functionality AVEVA Solutions Ltd User Bulletin (Issue 2) i

6

7 PDMS VPRM Gateway 1 Introduction This release of the PDMS VPRM Gateway comprises applications that give you access to the following interfaces between the PDMS and VPRM products. 1) PDMS to VPRM - PDMS CATREF Masks 2) VPRM to PDMS - Catalogue and Pipe Specification Data 3) PDMS to VPRM - Piping Bulk MTO 4) PDMS to VPRM - Piping Isometric MTO PDMS Maintain Catalogues Export CATREF Masks 1) PDMS CATREF VPRM Import CATREF Mask details Map PDMS and VPRM PDMS Import Catalogue data and Specifications 2) CATS Data & Specifications VPRM Develop and Improve Specs Pipe Specifications PDMS Develop the 3D Model Generate Bulk Mto reports 3) * Multi-Discipline Bulk MTO VPRM Import Bulk Material Take-off Produce Intermediate Mto Material Take-off Reports PDMS Develop the 3D Model Generate Piping Isometrics 4) * Multi-Discipline Drawing MTO VPRM Import Piping Isometric Mto Produce Final Mto Isometric Drawings Material Take-off Reports These interfaces have been upgraded and enhanced to include new functionality and improvements, as described in the following sections. * The disciplines covered by these interfaces currently include Piping and Multi- Discipline Supports AVEVA Solutions Ltd User Bulletin (Issue 2) 1-1

8

9 PDMS VPRM Gateway 2 Upgrade To upgrade from previous versions it is necessary to consider the following points. 2.1 Options File The PDMS VPRM Gateway Configuration File has changed. To upgrade your project from any previous release, you will need to copy the supplied configuration file pdsc01.cfg from location C:\AVEVA\PDMS-VPRM4.2\config_files to your project isometric directory for example %XXXISO% Once copied you will need to configure the new settings to suit your current project as described later in this bulletin AVEVA Solutions Ltd User Bulletin (Issue 2) 2-1

10

11 PDMS VPRM Gateway 3 Help Desk Remedy Calls The following reported fixes have been made at this release. HPD There was an error where multiple sheet MTO files were being overwritten when loaded if time stamp is identical for different sections This has been corrected by writing the Section Number to the Comment field of the $B record as shown in this example. HPD There was an error where the MTO File and Part List do not allocate Weld Allowances to correct Position Number if the Weld is flipped. This was due to an incorrect Loose Flange Allowance Position Number when the option HYPERPLANT was ON HPD There was an error where sometimes no.mto,.cvs,.xls or.ps was being produced This was corrected by adding a Spool Memory initialization. HPD On some occasions when utilising Deliverable Manager to create isometrics, an unexpected stop in the executable PDSC01.exe was experienced. This was corrected by adding a Spool Memory initialization. HPD On some occasions the wrong quantity was reported for a piece of Pipe in the separate Parts List. This has been corrected by removing the tolerance (which had been set at 0.1 metre) when exporting Tube. AVEVA Solutions Ltd User Bulletin (Issue 2) 3-1

12 PDMS & VPRM Interface HPD In certain circumstances parts were cumulated on the separate Parts List even when they had a separate part number. This was corrected by handling the situation where a Field Weld record directly follows an Olet 1st Leg record in the Isodraft Transfer File HPD On some occasions the Batch MTO Files failed when attempting to load it into VPRM. This was corrected by replacing the Construction Area for the Line in the Area field of the Spool Component records (this had been removed at the release when the facility to include the area on the component record was added) HPD On some occasions the MTO file contained the incorrect Section Number. This has been corrected by removing the code used to derive Section No from the bracketed part of Line Number HPD There has been a problem with importing the MTO for multiple sheets This has been solved by correcting the functionality when loading Multiple Section Files. HPD There has been a problem in importing material to VPRM if the project has been renamed. This has been corrected by validating the Batch Header Project Name against the Display Project Name. AVEVA Solutions Ltd User Bulletin (Issue 2) 3-2

13 PDMS VPRM Gateway 4 Other Changes 4.1 Multi-Discipline Support MTO The Gateway currently includes customer-specific functionality that supports the transfer of Multi- Discipline Supports MTO from PDMS to VPRM. This functionality is in the process of being made available to all MDS users but at the moment it requires a special version of MDS and requires consultation with AVEVA before use. So the changes described here apply only to those users of the current functionality. In this release, options have been added to the PDMS-VPRM Gateway configuration file to cater for new features which will be introduced in a future release thus currently, setting these new options has no impact on the functionality offered by the interface. The new options enable the user to specify the VPRM MDS MTO Disciplines to be used and to activate the Delete / Rename interface functionality on a discipline basis VPRM MDS MTO Disciplines Currently, when MDS MTO exported from PDMS is processed into VPRM it will be stored in the single discipline as specified in the configuration file by setting the option VPRM MDS Discipline Code. Thus all support MTO is stored within the selected VPRM discipline irrespective of whether the owning element was Pipe, HVAC or Cable Tray. New functionality is now in the process of being introduced to enable the selection of VPRM MTO disciplines based on the element type that owns the support. It has been designed to recognise that projects may wish to: Place all support material into one VPRM discipline irrespective of the owning element type Place support material in up to 3 different disciplines to reflect the 3 different types of owning element. a. Pipe b. HVAC c. Cable Tray. The first step in introducing this functionality has now been completed, ie the Gateway configuration file has been modified to present new options which will allow the identification of the VPRM discipline code that is to be used for support material which belongs to each potential owning element type. The same VPRM discipline code can be applied to more than one element type to satisfy those projects which do not want to segregate support material by discipline, ie they wish to consolidate like-material irrespective of the owning element type. AVEVA Solutions Ltd User Bulletin (Issue 2) 4-1

14 PDMS & VPRM Interface Whenever MTO for a support is transferred from PDMS to VPRM, it will be placed in an MTO batch with the relevant VPRM Discipline Code set by reference to the setting in the Gateway configuration file for the owning element of the support concerned. The options file editor available in the PDMS module Isodraft has been modified (see foot of form) to include the new VPRM MDS Discipline options, as shown below. Isodraft>Options>VPRM To set the relevant discipline code, click on the displayed Disciplines form. button and choose the code from the At the present time, all MTO will be directed to the discipline identified for piping irrespective of these settings. Note that the disciplines offered are read from the file %pdmsuser%/vprmdata.txt which is created when you enter Isodraft. As the program tests the VPRM access it extracts all of the VPRM disciplines and writes them into this file. AVEVA Solutions Ltd User Bulletin (Issue 2) 4-2

15 PDMS VPRM Gateway MDS MTO Delete / Rename Functionality Currently, the PDMS-VPRM MDS MTO interface includes functionality to cater for supports which are deleted and/or renamed as follows. When a support is deleted, the MDS MTO Extraction Code transfers an MTO batch to VPRM containing a $X delete record for the support concerned When a support is renamed, the MDS MTO Extraction Code transfers an MTO batch to VPRM containing a $X delete record in the name of the old support and $L, etc records in the name of the new support. Because this functionality is totally automatic in that whenever a support is deleted or renamed in MDS, associated MTO details are transferred to VPRM, the situation can occur where a renamed support is transferred into VPRM even though the user had never transferred the original support, nor wished it to be transferred, eg the support materials are to be supplied by others or MTO for the area in which the support is positioned is not yet scheduled to be undertaken. Thus there is potential for unwanted MDS MTO to be stored in VPRM. Consequently, new functionality has been designed: Firstly, to enable the user to state whether or not the delete/rename functionality is required for each owning element type or discipline. Secondly, to ensure that VPRM now checks that the support concerned already exists in VPRM before creating the MTO for the re-named support. The first step in introducing this new functionality has now been achieved by introducing a simple on/off switch for each element type / discipline in the configuration file. Setting the switch to on or off will in the future, activate or deactivate the delete / rename functionality for the element type / discipline concerned. At the present time, MTO details for all deleted / renamed supports is still transferred to VPRM irrespective of how these switches are set. For information about this release and any other described in this document, please contact AVEVA Customer Support for assistance AVEVA Solutions Ltd User Bulletin (Issue 2) 4-3