PDMS Bulletin116sp5

User Bulletin

User Bulletin

Version 11.6.SP5 Version 11.6.SP5

 AVEVA SOLUTIONS

 AVEVA SOLUTIONS MAKES NO MAKES NO WARRANTY OF WARRANTY OF ANY KIND ANY KIND WITH REGARD WITH REGARD TOTO THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

PURPOSE.

While every effort has been made to verify the accuracy of this document, AVEVA 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, Solutions shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance incidental or consequential damages in connection with the furnishing, performance or use of this material.

or use of this material.

This manual provides documentation relating to products to which you may 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 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. on which Products are licensed to you please refer to your licence conditions.

 All rights reserved.

 All rights reserved. No part of No part of this document may be this document may be reproduced, stored in reproduced, stored in a retrievala retrieval system or transmitted, in any form or by any means, electronic, mechanical, system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of AVEVA photocopying, recording or otherwise, without prior written permission of AVEVA Solutions.

Solutions.

The software programs described in this document are confidential The software programs described in this document are confidential informatio

information and proprietary products of AVEVA Solutions or n and proprietary products of AVEVA Solutions or its licensors.its licensors.

For details of AVEVA's worl

For details of AVEVA's worldwide sales and suppodwide sales and support offices, see our website atrt offices, see our website at http://www.aveva.com

http://www.aveva.com

Copyright 1974 through 2008

181104

181104 Final Final draft draft for for PDMS PDMS 11.6.011.6.0 140705

140705 Final Final amendments amendments for for PDMS PDMS 11.6.SP1 11.6.SP1 – – marked marked *sp1**sp1* 261005

261005 Amendments Amendments for for PDMS PDMS 11.6.SP2 11.6.SP2 – – marked marked *sp2**sp2* 281005

281005 AmendmentAmendments s & & additions additions for for defectsdefects 150506

150506 AmendmentAmendments s for for PDMS PDMS 11.6.SP3 11.6.SP3 – – marked marked *sp3*.*sp3*.  Along with p

 Along with program corrogram corrections and rections and minor enhanminor enhancementscements (see chapter 8), changes

(see chapter 8), changes include:include:

Piping Application Enhancements Piping Application Enhancements

Other Design Enhancements (see chapter 3) Other Design Enhancements (see chapter 3) Changes to support Global 2.4

Changes to support Global 2.4 Support for AutoCAD 2005, 2006

Support for AutoCAD 2005, 2006 in AutoDRAFTin AutoDRAFT In addition page headers have been corrected.

In addition page headers have been corrected.

130207

130207 Amendments Amendments for for PDMS PDMS 11.6.SP4 11.6.SP4 – – marked marked *sp4*.*sp4*.  Along with p

 Along with prorogram corrections and minor enhancementsgram corrections and minor enhancements (see chapter

(see chapter 1111), major enhancements include:), major enhancements include:

•

• Pipe bending checks & pipe sketchesPipe bending checks & pipe sketches •

• Parameterised Property Attributes (new Parameterised Property Attributes (new ChapterChapter 66)) •

• Weights on IsometricsWeights on Isometrics •

• New options for flow arrows New options for flow arrows on Isometricson Isometrics

•

• IntellectualIntellectual P Property protection for PML applicationsroperty protection for PML applications

 A new chapter

 A new chapter 1010 covers updates to standard projects: covers updates to standard projects:

•

•  Australian Steel Cat Australian Steel Cataloguealogue •

• MDS Lexicon databaseMDS Lexicon database

Chapter 1 (Introduction) has also been updated, notably the Chapter 1 (Introduction) has also been updated, notably the sections on ‘Support status’ and ‘Future considerations’, along sections on ‘Support status’ and ‘Future considerations’, along with minor corrections and improvements throughout.

with minor corrections and improvements throughout. Improvements related to Global 2.4.sp1 are also detailed in Improvements related to Global 2.4.sp1 are also detailed in this document:

this document:

•

• QueryQuery GloGlobal Network status from all modulesbal Network status from all modules

(section (section 2.82.8))

•

•  Admin queries  Admin queries for for Remote Remote dadatatabases and purgingbases and purging

transaction commands (Chapter transaction commands (Chapter 77)) 311008

311008 Amendments Amendments for for PDMS PDMS 11.6.SP5 11.6.SP5 – – marked marked *sp5**sp5*

Includes enhancements to Isodraft, Admin (primarily for Includes enhancements to Isodraft, Admin (primarily for Global) and an additional section on fixed defects.

1.2 Summary of Changes at PDMS 11.6...1-2 1.3 Summary of Changes at PDMS 11.6.SP1 *sp1*... 1-3 1.4 Summary of Changes at PDMS 11.6.SP2 *sp2*... 1-3 1.4.1 Support for Final Designer...1-3 1.4.2 Support for Laser Model Interface...1-3 1.4.3 Miscellaneous Improvements...1-4 1.5 Summary of Changes at PDMS 11.6.SP3 *sp3*... 1-4 1.5.1 Piping application ... 1-4 1.5.2 Draft 3D view...1-4 1.5.3 Support of Global 2.4 ... 1-4 1.5.4 Miscellaneous Improvements...1-5 1.6 Summary of Changes at PDMS 11.6.SP4 *sp4*... 1-5 1.6.1 Pipe bending checks & sketches...1-5 1.6.2 Parameterised Property Attributes ... 1-5 1.6.3 Weights on Isometrics...1-6 1.6.4 Australian Steel Catalogue ... 1-6 1.6.5 Intellectual Property protection for PML applications...1-6 1.6.6 Changes to related products...1-6 1.7 Summary of Changes at PDMS 11.6.SP5 *sp5*... 1-6 1.7.1 Isodraft Enhancements ... 1-7 1.7.2 Changes to related products...1-7 1.8 Documentation *sp1* *sp2* *sp5* ... 1-7 1.9 Operating System and Hardware Environment *sp4* ... 1-8 1.10 Upgrading from previous releases *sp5* ... 1-9 1.11 Compatibility (update) *sp3*... 1-10 1.12 Notice of change in support status (update) *sp4*...1-10

1.12.1 PDMS 11.4 and earlier ... 1-10 1.12.2 PDMS 11.5 (update) *sp4* ... 1-10 1.13 Future considerations ... 1-10

1.13.1  AutoCAD integration (update) *sp4*... 1-10 1.13.2 Windows versions (update) *sp5* ... 1-10 1.13.3 Use of UNIX servers (update) *sp5*... 1-11 1.13.4 PML features (update) *sp5* ... 1-11 1.13.5 Design Comparison with Schematics *sp5* ... 1-12 1.13.6 ISODRAFT symbol files *sp5* ... 1-12

2 PDMS GUI – General changes ...2-1

2.1 Glossary ... 2-1 2.2  Application framework... ... 2-3 2.2.1 Toolbars ... 2-3 2.2.2 Dockable Windows ... 2-3 2.2.3 Floating Windows ... 2-3 2.2.4 Status Bar ... 2-3 2.2.5 Session Settings ... 2-4 2.3 Tabbed Graphics form...2-4 2.4 Database Explorers...2-5

2.4.1 History...2-5 2.4.2 Explorer Settings ... 2-6 2.4.3 Filters ... 2-6 2.4.4 Copy rules...2-6 2.4.5 Drag-and-drop...2-7 2.4.6 Mouse Actions ... 2-9 2.4.7 ToolTips ... 2-9 2.4.8 Updates...2-9 2.5 Drawlist ... 2-9 2.6 My Data ...2-10 2.7 UNDO / REDO ... 2-10 2.8 Information about Global network status *sp4* ... 2-10

3 PDMS Design Changes ...3-1

3.1 General GUI improvements ...3-1 3.2 Element Selection (update) *sp4* ... 3-3 3.3 Quick Pipe Routing ... 3-4 3.3.1 Improvements for PDMS 11.6.sp3 *sp3*... 3-4 3.4 Pipe Component modification...3-5 3.5 Pipe Component creation...3-6 3.6 Pipe Component Reselection ... 3-6 3.7 Equipment Editing...3-6 3.8 Design Areas...3-6 3.9 New Piping Pseudo Attributes ... 3-7 3.9.1 Branch Surface Area...3-7 3.9.2 Range of Angles or Radii ... 3-7 3.9.3 Data Consistency ... 3-8 3.10 New Attributes for Material Management ... 3-9

3.10.1 Status attribute for use in MTO output ... 3-9 3.10.2  Additional attributes for spool MTO... 3-10 3.10.3  Additional attributes for Piping Specifications ... 3-10 3.11 Extract Refresh ... 3-10 3.12  Add to Drawlist tool bar *sp1* ... 3-10 3.13 Piping component (e.g. flange) alignment *sp1* ... 3-10

3.13.1 New attribute for PTCA, PTAX, PTMI, PTPOS...3-11 3.13.2 New pseudo attributes for branch members ... 3-11 3.13.3 Connection Command...3-11 3.13.4 New Datacon warning messages...3-11 3.14 HVAC application – new components *sp1*... 3-11 3.15 Pipe bending checks *sp4*... 3-12

3.15.1 Definitions...3-12 3.15.2 Design Database additions (update) *sp4*... 3-12 3.15.3 Production Pipes Check Form...3-13 3.15.4 Setting up Production Checks...3-16 3.15.5 Running a Production Check...3-17 3.15.6  Automatic Flange Alignment ... 3-20 3.16 Laser model and its manipulation *sp2* ... 3-21 3.17 Check Isometrics ... 3-21 3.18 Look Explicit *sp3* ... 3-22

4 Piping Isometric Enhancements ...4-1

4.1 General GUI improvements ...4-1 4.2 Parameterised MTOL & MTOQ...4-1 4.3 Use of temperature and pressure for selection...4-1 4.3.1 Standard Bolt Hole DB Change ... 4-1 4.4 User-defined Material Lists...4-2 4.5 Spooler – Pulled bend numbering *sp1*... 4-2 4.6 Isodraft – Pulled bend numbering *sp1* ... 4-2 4.7 Weights on Isometrics *sp4* ... 4-2 4.7.1 User Interface ... 4-3 4.7.2 Command Syntax...4-3 4.7.3 OUTPUT...4-3 4.7.4 Example Material List...4-4 4.8 Flow Arrow settings *sp4*... 4-5 4.9 Isodraft SKEY Enhancements *sp5* ... 4-5 4.9.1 New UNBW SKEY...4-5 4.9.2 New FY** SKEY ... 4-6 4.9.3 Tee/Olet SKEY Enhancement...4-6 4.10 Improved Continuation Sheet Options *sp5*... 4-7 4.10.1 New Annotation Options ... 4-7 4.11 Placing of Dimension Labels *sp5* ... 4-9 4.12 Improved Dimensioning – Oriented Welds *sp5* ... 4-10

5 Drawing Production Enhancements ...5-1

5.1 General GUI improvements ...5-1 5.1.1 Merged sub-applications...5-2 5.1.2 User utility menu...5-3 5.1.3 Dimension and 2D drawing forms ... 5-3 5.1.4 Labelling rationalisation ... 5-3 5.2 Use of the 3D features in DRAFT (update) *sp1* ... 5-4 5.2.1 3D Commands...5-4 5.2.2 3D user interface...5-4 5.2.3 Managing 3D view content (Drawlist)...5-5 5.2.4 Multi Selection ... 5-6 5.2.5 Scale control ... 5-8 5.2.6 UNDO/REDO ... 5-8 5.2.7 Modify Star...5-8 5.2.8 3D to 2D (Update Design)...5-8 5.2.9 2D to 3D...5-9 5.2.10 Display of 2D view frame in the 3D view gadget ... 5-9 5.2.11 Update control...5-10 5.2.12  View Type ... 5-10 5.2.13 Section Planes ... 5-10 5.2.14 Representation in 3D view ... 5-10 5.2.15  Viewfinder Shortcut menu. ... 5-11 5.2.16 3D view Shortcut menu additions related to view finder. ... 5-11 5.3 Template drawings...5-12 5.4 Section planes...5-12 5.4.1 Improvements for *sp3* ... 5-12

5.5 Background processes...5-13 5.6  AutoCAD integration with Final Designer... 5-13 5.7 UNDO/REDO *sp1* ... 5-14 5.8 Pipe Sketch ADP *sp4*... 5-14 5.8.1 Producing Pipe Sketches ... 5-14 5.8.2 How to Use the Pipe Sketches Form...5-14 5.8.3 Pipe Sketch Administration ... 5-17 5.8.4 Styles ... 5-19 5.8.5 Common Object ... 5-19 5.8.6 Log Messages ... 5-20 5.8.7 Table Definition Example...5-20 5.8.8 Dimensions...5-21 5.8.9 Tags ... 5-21

6 Parameterised Property Attributes ...6-1

6.1 Introduction *sp4*...6-1 6.2 Property attributes affected *sp4* ... 6-1 6.3 Upgrade Requirement *sp4* ... 6-2

7 Admin enhancements for Global...7-1

7.1 Querying Remote databases *sp4*... 7-1 7.2 Purge Transaction commands *sp4*... 7-4 7.3 User Interface enhancements *sp5* ... 7-5 7.3.1   Admin elements Form ... 7-5 7.3.2  DB Allocation (By Location/By Database) Forms ... 7-5 7.3.3  Create DB Form...7-5 7.3.4  Create Location Form...7-6 7.3.5  Extract Control Form ... 7-6 7.3.6  Main Tool bar ... 7-6 7.3.7  DICE Form...7-6 7.3.8  Transaction Command Timings Form...7-6 7.3.9  Create MDB Form ... 7-6

8 Customisation...8-1

8.1  Application switching... 8-1 8.2 Forms & Menus (PML) Enhancements ... 8-1 8.3 Further PML (Forms & Menus) changes *sp1* ... 8-3 8.3.1 Gadget layout management ... 8-3 8.3.2 Form enhancements ... 8-4 8.3.3 New SLIDER gadget...8-4 8.3.4 New radio group facility ... 8-4 8.3.5 List gadget enhancements...8-5 8.3.6 Option gadget enhancements...8-5 8.3.7 Miscellaneous...8-5 8.4 Internationalisation ... 8-6 8.5 Localisation ...8-6 8.6 PML Encryption *sp4*... 8-7 8.6.1 Decryption ... 8-7 8.6.2 Encryption...8-7 8.6.3 Buffering...8-8

9 Incompatible PML changes...9-1

9.1 Summary ... 9-1 9.2 Functional changes at 11.6...9-1 9.3 Layout changes at 11.6 ... 9-2 9.4 Functional changes *sp1*... 9-3 9.4.1 Multi-selection list – Extra Start and Stop meta-events...9-3 9.5 Layout changes *sp1* ... 9-4 9.6 Parameterised Property attributes *sp4*... 9-4

10 Updates to standard projects ...10-1

10.1 Supports catalogue for MDS *sp4* ... 10-1 10.2  Australian Steel Catalogue *sp4* ... 10-1

11 Product Faults and User Requests ...11-1

11.1 Known faults and Outstanding Issues...11-1 11.1.1 Windows fault – correction available...11-1 11.1.2 Windows faults – file locking...11-1 11.1.3 Microsoft .NET Framework Hotfixes KB886903 & KB886904... 11-1 11.1.4 PDMS faults & limitations – future corrections (update) *sp4* ... 11-2 11.2 Faults corrected and minor enhancements ... 11-4 11.3 Faults corrected and minor enhancements *sp1* ... 11-17 11.4 Faults corrected and minor enhancements *sp2* ... 11-22 11.5 Faults corrected and minor enhancements *sp3* ... 11-28 11.6 Faults corrected and minor enhancements *sp4* ... 11-38 11.6.1 Corrections to Global 2.4.SP1 (issued with PDMS 11.6.sp4)...11-46 11.7 Faults corrected and minor enhancements *sp5* ... 11-47

11.7.1 Corrections consolidated from previous fix releases:...11-48 11.7.2 Corrections to Global 2.4.SP2 (issued with PDMS 11.6.SP5)...11-52

This bulletin describes the new and enhanced functionality available in the fifth service pack (SP5) for PDMS 11.6, including information about the earlier releases of PDMS 11.6. It gives an overview of the major changes at 11.6, which are described in full in new and revised User Documentation. Minor changes and enhancements are also described in this Bulletin.

There are no major changes to PDMS itself in the various service packs. There are, however, changes in some of the related products, together with corrections, small changes and enhancements, and revisions to some of the User Documentation.

The most significant changes in this document for the various service packs are indicated as appropriate: .

1.1 Overview

PDMS has long led the way for 3D Plant Design. It has always been

object-based, using the concept of building a computer model of the plant, in order to ensure that the design works in every detail. Deliverables are always consistent as they are derived from this model. Interaction with this model has used realistic colour-shaded images for over 15 years. PDMS 11.5 introduced the first steps of a programme to build the Next Generation  user interface for PDMS, based on the latest Windows

technology. PDMS 11.6 brings a further leap forward in the graphical user interface. Major new features introduced at PDMS 11.6 include:

• Use of the latest Microsoft .NET technology to provide Windows

graphical user interface (GUI) standards for familiarity and ease of integration. This gives an appearance, and many GUI features, similar to Microsoft’s Office 2003.

•  A simpler mechanism for the various add-in applications for DESIGN,

both those produced by AVEVA and by customers.

• Extension of the new Model Editor, introduced at PDMS 11.5, and

provision of a new Plant Editor for Piping and Equipment. Refer to the VANTAGE PDMS Version 11.6 Graphical Model Manipulation Guide for details. Future work will provide further specialist

discipline-oriented ‘Editors’ to support the workflow for engineering design.

•  A new GUI for DRAFT, including a 3D view, to simplify the creation

and annotation of drawings.

The first service pack provided improvements, based on early use of some of these new features, notably in DRAFT. In addition, there were many enhancements made to ease migration of PML applications to PDMS 11.6 and the .NET environment.

PDMS 11.6.SP1 also shared technology with AVEVA’s new VANTAGE Marine Outfitting product.

PDMS 11.6.SP2 enabled the use of two new add-on products: Final Designer 1.3 and Laser Model Interface. These both integrate PDMS with a third party product.

Final Designer  enables the use of AutoCAD as an alternative editor for PDMS Draft drawings. Its use is described in its on-line help and in its Getting Started with Final Designer  manual.

The Laser Model Interface  enables PDMS Design to link to third party laser model software to enable the point cloud survey data to be

visualised, measured and checked for clashes.

PDMS 11.6.SP3 brings further refinements, particularly to the new piping application, as well as various priority enhancements and corrections. It also adds support for the updated release of Global, version 2.4.

PDMS 11.6.SP4 brings further improvements, as well as various priority enhancements and corrections. Particular attention has been paid to performance of the system, and in particular graphical picking. This document also notes a few refinements in Global, in its first service pack since the release of version 2.4.

PDMS 11.6.SP5 is provided to consolidate defect corrections and to support a further update to Global, Global 2.5. This has many GUI improvements as well as a major boost to update performance – please see separate bulletin.

1.2

Summary of Changes at PDMS 11.6

The changes fall into 3 main categories:

• The PDMS Application Framework, with its new .NET GUI. This

brings improved ways of integrating users’ GUI customisation.

• PDMS Design, with its enhanced Design Explorer and a new Plant

• PDMS Draft, with its new .NET GUI, 3D View and provision for

integration with AutoCAD.

Further work has been carried out on support of international languages, though further improvements are planned for future releases. Details are given in chapter 8 of this document.

There are many other minor improvements throughout the product and much of the documentation has been updated.

1.3

Summary of Changes at PDMS 11.6.SP1

*sp1*

The changes fall into 3 main categories:

• PDMS Design, with a new Add to Drawlist  tool bar to specify the

colour of objects added using the Design Explorer.

• PDMS Draft, with improvements to the usability of the new 3D View,

including section planes, and implementation of UNDO/REDO.

• The PDMS customisation environment (PML Forms & Menus) has

further improvements for the definition of user interface gadgets. In addition, changes have been made to support new releases of the other  VANTAGE Plant Design products, notably:

 VANTAGE Plant Design Router 2.4  VANTAGE Plant Design Global 2.3

 VANTAGE Multi-Discipline Supports 11.6

Corrections and improvements for many issues raised by customers in PDMS 11.6 and earlier releases are also included in the service pack.

1.4

Summary of Changes at PDMS 11.6.SP2

*sp2*

1.4.1 Support for Final Designer

The new VANTAGE Plant Design Final Designer  product provides a fully integrated AutoCAD editor for DRAFT, thus enabling its use on

drawings produced directly from the PDMS model.

1.4.2 Support for Laser Model Interface

This new product enables point clouds from laser surveys to be used in PDMS Design, thus enabling them to be viewed, measured and clash checked alongside the PDMS model. It requires the use of a third party

system from the specialist survey company, with which it integrates closely. The system is designed to be open, but is expected to become available initially from BitWyse, Leica (Cyra), Mensi/Trimble,

Quantapoint and Zoller+Fröhlich (Z+F). There is a reference manual explaining the new commands associated with the interface, but for full details it is necessary to consult the appropriate third party vendor.

1.4.3 Miscellaneous Improvements

Corrections and improvements for many issues raised by customers in PDMS 11.6 and earlier releases are also included in the service pack.

1.5

Summary of Changes at PDMS 11.6.SP3

*sp3*

1.5.1 Piping application

In addition to correction of issues raised by customers in their use of earlier releases of PDMS 11.6, there have been various improvements to the usability of the piping application. These are noted in section 3.3.1.

1.5.2 Draft 3D view

 A number of enhancements to the new 3D view in Draft, notably to the use of stepped section planes. See section 5.4.1.

1.5.3 Support of Global 2.4

PDMS 11.6.SP3 supports the use of a new release of Global; use with Global 2.3 is not supported. This new release uses additional features in the Global daemon (2.4) to allow a number of significant enhancements. These include several aimed at providing better feedback to users, as well as some giving additional control of Global functions. The robustness of the daemon itself has been improved to minimize the number of

occasions it needs to be re-started.

The new features in Global are fully documented in a release bulletin and updated versions of its other manuals.

Please note that many of the features of Global 2.4 are also available in Global 2.2.SP2 for users of PDMS 11.5, in conjunction with a new service pack SP2 for the latter. However, those which depend on additional

1.5.4 Miscellaneous Improvements

Corrections and improvements for many issues raised by customers in PDMS 11.6 and earlier releases are also included in the service pack. These are noted in section 11.5.

1.6

Summary of Changes at PDMS 11.6.SP4

*sp4*

This service pack addresses a number of points raised during the use of earlier releases of PDMS 11.6, along with corrections to faults found during testing and use of earlier releases of PDMS. Details of these changes can be found in Section 11.6.

In addition, there are some additional features, which are summarised here and described in more detail in separate sections of this document. The sample projects have also been updated, to include a steel catalogue for Australia & New Zealand (see Section 1.6.4) and a dictionary

database for MDS (MASTER/MDSDICT) – please see Chapter 10.

SP4 is accompanied by updates of some of the add-on products, notably:  VANTAGE Plant Design Router 2.4.SP4

 VANTAGE Plant Design Global 2.4.SP1 (see Section 1.1.1.1)

 VANTAGE Multi-Discipline Supports 11.6.SP4 (see Section 1.1.1.2)

1.6.1 Pipe bending checks & sketches

 Allow the designer to check that a given pipe spool may be manufactured by a particular machine, if such a machine has been defined in the

database. These pipes may then be detailed for fabrication using scal e drawings complete with fabrication information. Please see Sections 3.15 and 5.8.

1.6.2 Parameterised Property Attributes

This allows attributes in the property database to use parameters in their definition, which can simplify the calculation of properties such as weight. Please see Chapter 6.

1.6.3 Weights on Isometrics

This allows the user to add a weight column to the isometric material list and provide a summary total for the fabrication and erection material s plus an overall total for isometric material weight. Please see Section 4.7

1.6.4 Australian Steel Catalogue

This is a new catalogue in the standard project, structured in a similar manner to the AISC one. Please see Chapter

1.6.5 Intellectual Property protection for PML applications

 A separate utility is available to encrypt PML macros. Encrypted macros are automatically detected and decrypted as required. Please see Section 8.6.

1.6.6 Changes to related products

Improvements to the user interface include:

• Remote database session querying in ADMIN • Transaction purging appware in ADMIN

In addition, Network status is now available in all modules. Please note that there are also corrections noted in section 11.6.1.

1.1.1.2 MDS

MDS 11.6.SP4 provides an interface to the design applications provided by various pipe support vendors: Lisega, Carpenter & Paterson, Pipe Supports Ltd. Please refer to MDS documentation for details.

1.7

Summary of Changes at PDMS 11.6.SP5

*sp5*

This service pack addresses a number of points raised during the use of earlier releases of PDMS 11.6, along with corrections to faults found during testing and use of earlier releases of PDMS. Details of these changes can be found in Section 11.6.

Error Reference source not found..

In addition, there are many enhancements to Admin, mostly aimed at simplifying the use of Global. The changes mean that it is important to use Global 2.5.

1.7.1 Isodraft Enhancements

Significant Isodraft enhancements have been made since PDMS 11.6.SP4; they were first issued in PDMS 11.6.SP4.11.

• SKEY Enhancements

• Improved “Continuation Sheet” Functionality •  Alternate Placing of Dimension Labels

These are documented in sections 4.9, 4.10, 4.11.

 A further enhancement was included in PDMS 11.6.SP4.12.

• Control component dimensioning on either side of a weld

This is documented in section 4.12.

1.7.2 Changes to related products

Global 2.5 has many improvements, notably to update performance and to the handling of offline satellites.

Please note that the performance improvements have necessitated a change to the format of the data passed between locations, so 2.5 cannot be mixed with versions of 2.4.

1.7.2.2 PDMS Nuclear Applications

There are two new product options available with PDMS 11.6.sp5:

Nuclear Concrete Design  and Nuclear Room Manager . At present, these applications are shipped and documented separately.

1.8

Documentation

*sp1* *sp2* *sp5*

This bulletin outlines the major changes at both the original PDMS 11.6 release and its service packs: it is updated for each service pack.

Most of the manuals were updated for PDMS 11.6; many had significant changes that are noted on a Revision History page at the front of the manual.

The Pipework design using VANTAGE PDMS  manual, which was not included in the original release, was updated for PDMS 11.6.SP1. The following manuals were also updated for SP1:

• PDMS Installation Guide

• Drawing Production Using VANTAGE PDMS 11.6 • PDMS Software Customisation Guide

• PDMS Software Customisation Reference Manual

Many of the other manuals had minor amendments and corrections. For PDMS 11.6.SP2, there were again amendments to 4 manuals:

• Drawing Production Using VANTAGE PDMS 11.6

• PDMS DESIGN Reference Manual Part 1:General Commands 11.6 • PDMS ISODRAFT User Guide 11.6

• PDMS ISODRAFT Reference Manual 11.6

The release also contains updated Design and Draft online help files: updates were also supplied as a fix release PDMS11.6.SP1.2.

PDMS 11.6.SP5 also includes updates to some of the manuals, notably for Admin.

1.9

Operating System and Hardware Environment *sp4*

PDMS 11.6 is supported for use on Microsoft Windows 2000 SP4 and Windows XP Service Pack (SP) 1, 2 or 3. It is not supported on the new Windows Vista – please see section 1.13 below. There is no UNIX version of PDMS 11.6.

Windows XP SP2 requires changes to the default settings. The Internet Connection Firewall (ICF) should be turned off or configured to enable access to the database & licence servers. In addition, Group Policy changes (which alter the registry) are required for users of Global projects to ensure that RPC requests do not require authentication. Details are given in the Installation Guide.

PDMS 11.6 requires Microsoft’s .NET Framework 1.1, which is supplied on the CD-ROM and installed if required. This is used for the PDMS graphical user interface. Please note that PDMS 11.6 is not compatible with .NET Framework version 2.0 or later; if later versions are required for other applications, it is necessary to install them in addition to

version 1.1. Further information is available on Microsoft’s web-site, for example, see http://msdn2.microsoft.com/en-us/library/s80xxs7s.aspx.

PDMS 11.6 should run successfully on Windows NT4, but it has not been tested under Windows NT4 and is

support for either Windows NT4 or Windows 2000; it no longer offers even extended support for NT4.

 A minimum of 512 MB of memory is recommended for this release. PDMS 11.6 will operate with less, but system performance will be

compromised. A screen resolution of at least 1024x768 is recommended. Users running Windows XP are recommended to use the XP rather than Classic theme. These should be set using Display Properties.

Due to the rapidly changing list of hardware-accelerated OpenGL graphics cards commercially available, an up-to-date list of supported graphics cards is not included in the documentation released with PDMS. However, the AVEVA Web pages (http://www.aveva.com) contain a

current list of both tested and supported graphics cards.

1.10 Upgrading from previous releases

*sp5*

PDMS 11.6.SP5 is fully compatible with earlier releases of PDMS 11.6 and requires no upgrade. Please note, however, that Global should be upgraded at the same time – see above. PDMS 11.6 itself requires no change to the PDMS database structure from that used at PDMS 11.4 & 11.5. Upgrade scripts are provided to upgrade projects from all previous releases of PDMS 11 on the Windows platform, i.e. 11.2, 11.3, 11.4 & 11.5.

The upgrade scripts take account of a change at PDMS 11.4SP1, when the standard database definition files were moved to the PDMS

executable directory (PDMSEXE). This simplified the upgrade process required to add new attributes and elements to databases. It is no longer necessary to copy these files (also known as virgin database files) to the project data areas in order to gain access to new elements and attributes. Users’ own PML customisation and applications from PDMS 11.4 or 11.5 should continue to work, after being amended to use the n ew application switching mechanism. Please see Customisation chapter 8. It is possible that some form layouts will be adversely affected by the change to the standard Windows proportional screen fonts, though this depends on the way the forms have been defined. There is also scope for enhancement by using the new facilities offered by PML, such as toolbars and docking forms. Many of the AVEVA applications have been upgraded in this way, so users who have revised the AVEVA applications should review their changes in the light of this work.

no longer supported in that

1.11 Compatibility

(update) *sp3*

PDMS 11.6.SP3 AutoDRAFT and DXF output functions have been

designed and tested with AutoCAD® _{2004, 2005 and 2006. Final Designer}

(version 1.3) is compatible with AutoCAD® _{2005 and 2006.}

1.12 Notice of change in support status (update) *sp4*

1.12.1 PDMS 11.4 and earlier

PDMS 11.4 changed to ‘inactive’ support status in June 2006, which means that it is not normally be supported with releases of any kind.  At the same time, all earlier versions were ‘withdrawn’, which means

that customers no longer have the right to use them. In exceptional circumstances AVEVA may be prepared to negotiate continued use and critical problem support.

Full definitions of support status can be found on

http://support.aveva.com/support/United_Kingdom/index.htm  in the section on PDMS releases.

1.12.2 PDMS 11.5

(update) *sp4*

PDMS 11.5.SP1 was superseded by 11.5.SP2 during summer 2006. It was accompanied by an updated version of Global, 2.2.SP2: both should be used together and are fully supported, with previous versions of 11.5 now at ‘inactive’ support status.

1.13 Future considerations

1.13.1 AutoCAD integration

(update) *sp4*

Final Designer interfaces with AutoCAD and may provide an improved method of performing some of the older AutoDRAFT functions. However, there is no longer any plan to withdraw AutoDRAFT. The DXF output feature is also unaffected, though it may be less necessary in future.

1.13.2 Windows versions

(update) *sp5*

Microsoft Vista is not supported for PDMS 11.6: it is a major upgrade and will require some significant changes, at least to installation

for PDMS 12.1.SP1 (target May 2009) and subsequent releases. We will drop support of Windows 2000 at the same release. Almost all

development at AVEVA is now carried out using Windows XP (service pack 1, 2 or 3), which is currently the preferred option.

1.13.3 Use of UNIX servers

(update) *sp5*

 AVEVA has been supporting the use of Samba on IRIX servers to allow users the opportunity to use their old servers for an interim period. This is still supported for PDMS 11.6 but is not supported at the next major release, PDMS 12.0, because of changes to allow larger PDMS databases. Testing for PDMS 11.6 has used Samba 2.2.8a.

1.13.4 PML features

(update) *sp5*

 Various changes are included in the next major release, PDMS 12. The improvements to provide a more powerful customisation environment, which complies better with Windows standards, mean that certain older features can no longer be supported and will be removed: this may well necessitate changes to some users’ PML applications. Those writing PML applications should particularly note the following:

1.13.4.1 RADIO gadget

This gadget has been deprecated and has not been documented for several years. It is no longer available in the PDMS 12 release. Any usage should be replaced by the new FRAME and RTOGGLE gadgets, which include its features and should offer a simple upgrade path.

1.13.4.2 RGROUP gadget

The RGROUP gadget, which replaced the RADIO gadget, has itself been superseded by the radio group capability of the FRAME gadget in

conjunction with RTOGGLE gadgets. It still exists and continues to work, but its use is discouraged; it will be removed in a future release.

1.13.4.3 Toolbar based OPTION gadget field reselection

Reselection of the selected field of an Option gadget on a toolbar will no longer constitute a change of value. This provides better conformance with expected behaviour in a Windows style GUI. The effect is that the PDMS 12.0 also requires the installation of Microsoft’s .NET Framework, in this case version 2.0. We expect to be using later versions of .NET for subsequent releases.

gadget’s SELECT call-back will not be run (a SELECT event is NOT notified to PML).

1.13.4.4 Form based OPTION gadget field reselection

Reselection of the selected field will no longer necessarily constitute a change of value. There will be an optional attribute ‘NoReselection’, which is the recommended behaviour (as for Toolbar option gadgets above). However, the default is ‘Reselection’, for upwards compatibility.

1.13.4.5 LIST gadget field Reselection

Reselection of the selected field no longer necessarily constitutes a change of value. There will be an optional attribute ‘NoReselection’, which is the recommended behaviour (as for OPTION gadgets above). However, the default is ‘Reselection’, for upwards compatibility.

1.13.4.6 SAVE and RESTORE using .bin files

Binary save and restore is to be replaced by the combination of session layout serialisation files and view content (.disp) files.

1.13.5 Design Comparison with Schematics

*sp5*

PDMS 12 offers a new option for integration and comparison of 3D designs with schematic diagrams, such as P&IDs, from a variety of systems. This initially covers equipment, piping, and HVAC and will be extended in future to cover electrical cable. As a result, the old Design Compare option (Compare module) has been removed.

1.13.6 ISODRAFT symbol files

*sp5*

PDMS 12 has a change to the format of ISODRAFT symbol files generated by DRAFT. Those used in version 11 or earlier will not be readable by ISODRAFT, so they will need to be regenerated from the DRAFT database. Manually created symbol files are not affected.

PDMS 11.6 uses the Microsoft .NET environment including WinForms based user interface components. Using this state-of-the-art technology enables docking forms and toolbars in PDMS and provides a robust

foundation for the future provision of standard application programming interfaces.

 All modules with a graphical user interface (GUI) now use this new technology, which is presented in an Application Framework and has several new or updated components. The use of docking windows and toolbars means that PDMS will appear more familiar to users of

Microsoft Windows XP and Office and reduce the number of dialogs obstructing the 3D graphical view, enabling more effective use of screen space. Many windows are now resizable, simply by dragging their edges or corners in the usual Windows manner.

PDMS 11.6 also enhances the database explorer and drawlist with the addition of filters and a more intuitive interface and – at SP1 – a colour picker for objects dragged from the explorer.

The use of .NET has a significant impact on the number of program files that comprise each PDMS module. For example, Design now consists of the following files: des.exe, des.dll, wrappers.dll and these make use of a large number of other files, including a large number of other .dll files. This will have an impact on the way that bug fixes are issued: in future, it is likely that fix releases will be cumulative. For example, fix release 11.6.0.5 will include all the changes in the preceding 4 fix releases.

Further information is given in the PDMS Installation Guide.

2.1 Glossary

The new Application Framework introduces some new concepts and terminology, which are introduced here, along with other terms used in this document. PDMS terminology is covered in the Getting Started with PDMS manual.

 Add-in An add-in provides a means of adding functionality.  An add-in application appears on the Applications

CE “Current Element” – the single PDMS object that is acted upon by the PDMS command line and by many of the user interface gadgets. See Selection.

Combo box Standard Windows control that combines a text box and interdependent list box.

Culture The .NET term for the various local settings for language etc. – similar to the Windows

Docking Dockable

This describes windows and menu bars that can be attached in appropriate places to the frame of the main PDMS window.

Drag-and-drop Select with mouse and then drag (holding the mouse button down) to a different place.

Form Input window – see window.

MDI Multiple document interface: a set of child windows constrained to a single primary or parent window. Menu bar A horizontal bar below the title bar containing menus. My Data A new storage area for remembering PDMS data for

future use. Typically used for IDLists to copy from one module to another.

Selection Many of the user interface gadgets can now work on a selection of objects defined using the 3D graphical view.

Shortcut menu This context sensitive pop-up menu is activated by use of the secondary (usually right-hand) mouse button.

Tab control Tabbed form

 Allows multiple, usually related, forms (windows) to be overlaid, with a simple switching mechanism similar in appearance to a notebook or file divider. Title bar The top, containing a title, of any particular window,

which can also be used to drag the window.

Toolbar A frame containing controls, typically icons, to trigger GUI actions

ToolTip A small pop-up window containing descriptive text, which typically appears when hovering over an icon. Window A separately controlled area of the screen. PDMS has

one primary or main window and many secondary windows: some of these are often called forms.

2.2

Application framework

The PDMS 11.6 application framework provides the primary or main application window with its associated main menu bar and toolbars as well as support for docking windows. The framework also allows for

applications to be extended via the use of “Add-ins”, such as the Explorer, and provides a GUI, based on the Microsoft Office 2003 look and feel.

2.2.1 Toolbars

The application framework supports toolbars, which can be floating or docked to any of the sides of the primary window. Picking the title bar of a toolbar and dragging away from the window frame will undock it.

Dragging it back to an appropriate place will re-dock it. The position and state of toolbars and other windows are automatically saved between sessions.

vertically.

2.2.2 Dockable Windows

The application framework supports the creation of dockable windows. These may be dragged in a manner similar to toolbars and docked on any side of the primary window. They may also be unpinned, so that they auto-hide when not in use.

2.2.3 Floating Windows

Graphical views are contained in windows that can be floated via a shortcut menu on their title bar. These floating windows can then be placed on a different screen to the primary window.

2.2.4 Status Bar

The status bar consists of the following items:

•  An area for user prompts

•  A number of buttons to allow quick activation of MDI windows. • Current Date

• Current Time.

2.2.5 Session Settings

 Various user interface settings for each PDMS module are automatically saved in files in the directory defined by the PDMSUSER environment variable. They can thus be restored on the next entry to that module, even between PDMS sessions. These settings can safely be reset to the default value by deleting the relevant file. This process is called

Serialisation in Microsoft’s .NET environment and includes:

• Layout of windows including their docking state • Explorer Settings

• Element History including the CE

In general, the position and state of forms will be saved on exit from a module and restored next time the user enters the module. This does not apply to the contents of the main windows such as the 3D view, for which the existing display binary save and restore mechanism may be used. There are other exceptions: for example, the 3D view is not shown in Draft until required, though its position is saved.

2.3

Tabbed Graphics form

The user interface for Graphics has been completely overhauled using a standard Windows tabbed dialogue form to replace the original forms. Many minor improvements have also been incorporated.

The new Graphics Settings form contains options previously on the 3D  View Options, Colours, Representation, Steelwork Representation, P-line

The Load Settings and Save Settings buttons load from and save to the options files stored in %PDMSUSER%.

The Design bar menu has been changed to remove references to old forms and to call the new one. The Graphics Settings form is accessible from Settings > Graphics…

2.4

Database Explorers

Explorer views have now been extended from the Design Database to cover other modules and databases. The Application Framework manages their layout and dockability. They provide a consistent tree view of each database and module specific context menus.

 An important feature of the Explorers is the ability to allow flexibility in the presentation of the database hierarchy through the use of filters. These are different sets of filters for different Databases. Additional filters and other Explorer options are available on an Explorer Settings form. The user may Drag-and-drop elements within and outside the Explorer.

There is now a separate Toolbar Add-in, which shows the current Element History.

Explorers are available in the Design, Draft, Spooler and Isodraft

modules, and replace the PML-based Members Lists. They are available from the Main Menu>Display menus in each module. Each Explorer is restricted to Elements of a particular database type.

2.4.1 History

The History Add-in appears on the main toolbar in Design, Draft, Spooler and Isodraft. It displays the current element (CE), regardless of the

database.

The user can set the CE either by typing the element name into the combo box, selecting a previously typed in element from the drop-down list, navigating through the CE history one element at a time using the backwards and forwards buttons or by selecting elements from the CE history list using drop-downs on the backwards/forwards buttons.

When typing into the combo box the system attempts to auto complete the name by scanning the open databases for the first 15 matches and displaying them in a pop-up list. The user can then either carry on typing or select an element from the list. When docked vertically the toolbar displays only the backwards and forwards buttons; the combo box is not displayed.

2.4.2 Explorer Settings

The Explorer Settings form is used to configure the behaviour of the Explorer and set additional filters. It can be found, where appropriate, from the Main Menu: Settings > Explorer…

The settings are remembered between sessions for each user and module.  All options are turned off by default apart from “Expand to CE” which

causes the Explorer tree to expand, if required, to show the CE whenever the CE changes. A very useful option is “Auto Collapse Tree”, which applies to all active Explorers. If this is on, any expanded node not containing the CE is collapsed whenever the user changes CE.

The remaining options apply to either the Design Explorer or the Draft Explorer. They control the visibility of elements: they can set elements as always hidden (e.g. non-writeable Template Worlds and LIBY’s) or allow previously hidden elements to be shown in the hierarchy (e.g. TUBI, ROD and Point Worlds).

2.4.3 Filters

 A predefined set of database filters is available to reduce the volume of information presented in the Explorers. These can be selected and

turned on and off from each Explorer. When filtering is off the complete database hierarchy is displayed in the Explorer. Only one system filter can be active at any given time for each Explorer. Additional preset filters are provided via the Explorer Settings Form (see above) for “special case” elements. These can be toggled on/off regardless of whether the system filters have been set.

2.4.4 Copy rules

 An element (source) may be copied within the Explorer either by Drag-and-drop, context menus or the keyboard shortcuts CTRL+C / CTRL+V

either beside or below another element (target). Paste beside copies the element after the target.

• The relevant MEMBER attribute is settable: with that of the target

element (if below) or its owner (if beside).

• The source element type is an allowable member type for its new

owner.

If either of these rules is broken, the Paste is invalid. TUBI elements cannot be copied or moved since they are implied by the system.

Users may add their own additional checks by adding code to the following PML function:

• IsCreatable.pmlfnc

This logical function is stored in %PMLLIB%\common\functions directory and is called before the Copy.

2.4.5 Drag-and-drop

The Explorer supports Drag-and-drop within the Explorer to copy

elements, Drag-and-drop into the 3D view to add elements to the Draw List and Drag-and-drop into My Data  to add elements to it.

2.4.5.1 Drag-and-drop within the Explorer

Selecting an element and dragging it, with either the primary or secondary mouse button down, initiates Drag-and-drop.

• Single elements may be moved or copied within the Explorer using

Drag-and-drop (apart from TUBI if they are shown)

• Copy rules are applied to validate the Copy (see above) • Hovering over a node causes it to auto-expand.

• The mouse pointer icon changes to notify the user of an invalid copy

(e.g. between databases)

•  All child elements are transferred with the dragged item.

• The Drag-and-drop action can be cancelled by pressing ESC at any

time before dropping.

•  A divider bar appears between elements to show where the dragged

element will be inserted if dropped, i.e. before, after or below.

• Dropping directly onto an element assumes that the dragged

elements are to be added to the beginning of the element’s child list.

• Pressing CTRL whilst dragging performs a “copy” action. • Copy Drag-and-drop is indicated by an “arrow + plus” icon.

•  All connectivity attributes are lost in the copied elements.

• The names of all copied elements which are named are prefixed with

“Copy-(n)-of-” (including copies of copies) where n >=2 (the first copy will have the prefix “Copy-of-“.

• Copy and Paste are available on the Explorer context menus.

 After selecting an element and doing a Copy, the user may select a valid owning element and add the Copied element to it using Paste or select a valid sibling element and insert the Copied element after it using Paste Before or Paste After. Paste is greyed out if the Copy is invalid

•  Alternatively the user can perform Drag-and-drop with the secondary

mouse button down. On mouse up, a context menu appears from which the user can select a valid Copy or Cancel.

• Finally, the user can use the CTRL+C and CTRL+V shortcuts to Copy

and Paste respectively.

2.4.5.2 Drag-and-drop into the 3D view

This allows the user to add elements in the Explorer to the Design drawlist by Drag-and-dropping from the Explorer to the 3D view.

• The user can select only single elements for drag & drop.

•  All significant elements will be added to the drawlist along with the

dragged element.

• The elements can be dropped anywhere within the 3D view. • Elements cannot be dropped into place; they will appear in their

correct 3D positions.

• The mouse pointer icon changes to notify the user of invalid moves • The Drag-and-drop action can be cancelled at any time before

dropping, by pressing ESC.

2.4.5.3 Drag-and-drop into My Data

This allows the user to add elements to My Data  by Drag-and-dropping from the Explorer into either the Collections or Contents grids in My Data  (q.v.)

• The user can select only single elements for Drag-and-drop.

• Dropping into My Data  is equivalent to the “Add to My Data” context

menu.

• Depending on where it is dropped, the dropped element is added

• Child elements will not be added to My Data .

2.4.6 Mouse Actions

Primary mouse click:

Selects element, sets CE, (also expands/contracts tree if on node icon) Primary mouse double click:

Selects element, sets CE, expands/contracts tree below element Secondary mouse click:

Selects element, sets CE, displays context menu.

2.4.7 ToolTips

Name, Type and Description are shown in ToolTips over each Element.

2.4.8 Updates

The Explorers are kept in step with the database and CE. So, whenever the user does the following the Explorer is updated:

• Change CE

• Create/Delete element • Rename element

• Reorder / Include element (Copy/Paste) • UNDO / REDO

• Getwork • MDB Update • Claim

•  Anything else that changes the state in the Explorer.

2.5 Drawlist

The Drawlist at 11.6 is a separate dockable window, managed by the application framework, and replaces the previous Drawlist, which was part of the Explorer.

It appears only in the Design and Spooler modules and provides

modification of the visual properties of the displayed elements, such as visibility, translucency and colour. It also allows the user to add selected Elements to My Data either from context menus or Drag-and-drop.

2.6

My Data

The “My Data” Add-in is a dockable window, managed by the Application Framework, which provides a place for users to gather, organise and

perform operations on all the data they require to complete their tasks. It contains collections of PDMS database Elements and single Elements. My Data is particularly useful for the transfer of Design Drawlist

elements into Draft for the population of Drawings.

The user can add items to My Data in a number of ways: via context menus on other components or via Drag-and-drop from other

components. The contents of My Data are persistent and are

reconstructed each time the user logs in. It is available in Design, Draft and Spooler modules from the Main Menu>Display menus.

It consists of 3 components, namely a Collections Grid, an Actions Group and a Contents Grid. The Actions Group and Contents Grids are

collapsible.

2.7

UNDO / REDO

The operation of UNDO and REDO has now been extended and is now available to PML programmers for use in their applications. For details of the latter, please refer to PDMS Software Customisation Guide  section 8.3.7 UNDO and REDO.

Please note that UNDO is not yet available in modules other than DESIGN & DRAFT.

2.8

Information about Global network status

*sp4*

It is now possible to Query the communications status of remote Global locations in Design, Draft and Spooler. A form similar to that for

Remote > Locking and Isolation  in Admin allows the user to query Communication status  and Project Lock and Isolation .

They result in the following forms, which behave in a manner similar to the admin forms.

The user can ping locations by selecting them and using the  Apply  button and then Sort  and Filter  results. Results are appended until the Clear Results  button is pressed.

The user can check locations by selecting them, toggling Lock , Isolation  or both and pressing the Apply  button. The status will be displayed below.

The Locator Handle, which manipulates the 3D model, has been enhanced to work in a variety of ways in a context sensitive manner.

The new Piping editor includes a Pipe Routing Handle. Piping designers can route pipes interactively by dragging this Handle in the 3D graphics view and snapping to element features. The interface includes extensive graphical feedback to assist the designer and makes the pipe routing process easy to learn and use, and very quick in operation.

The Locator Handle also provides features specific to piping components. For example:

• constraining the movement of piping components to the route of

the pipe

• intelligent connection to nozzles and other piping components • moving groups of connected piping components.

Piping designers can now create piping components through a new

interface that uses docking windows to improve use of screen space. The new interface allows rapid creation and placement of components in a highly intuitive way, by interacting with the 3D graphics view. They can also produce check isometrics (on screen or paper) from within Design, thus simplifying the process of ensuring that the correct documentation will be produced.

PDMS 11.6 extends graphical interaction to primitives below equipment and sub equipment, thus enabling the manipulation of, for example, nozzles using the Locator Handle.

In addition, many of the Design forms have been improved by using the new facilities of the PDMS Workspace, such as tabbed forms.

3.1

General GUI improvements

Many forms in Design have been improved, for example:

The Query form is opened by selecting Query > Attributes from the main bar. It has been made docking and resizable to allow easier viewing of query results. The Query > General form has been removed.

The Query Project  form is a tabbed form that replaces the existing User List , Team List , DB List , MDB and Stamp List forms. It contains a tab

that shows the information that was previously shown on each individual form.

The alpha view in the Data Consistency Check  form no longer receives the I/O requests channel when it’s not needed. The layout of the forms has been improved.

The View Control form has been made dockable – the menu bar has been replaced by buttons, with some of the functions, changing the

background colour of views and deleting views, available on a shortcut menu.

The layout of the Report Template form has been tidied up and tabs are now used instead of spaces to align columns in the list. After input from users, minor changes have been made: the form is not closed when a report is saved; the user is asked to confirm before overwriting the

current data when modifying/creating a report; the user is asked whether they want to quit without saving the current template when clicking on the close icon.

The Penetration Defaults form now uses tabs for its three sections. The Template Browser form has been made dockable. If open when

Design exits, it’s now opened when Design restarts. The Control > Select CE TMPL menu option has been replaced by the CE TMPL button and the Display > Selected Template has been replaced by the Display button.

 A new form, Data Access Control , has been created to replace the User Rights  form and add information previously found only on the Element Data Access Control (DAC) Errors List  form in the Model Management product. The form has two tabs, displaying the information previously shown on the two forms. The first, User Rights, shows the Access Control Rights that apply to the current user, and information about their scopes and roles. The second, Element Access, allows the user to specify an element; for each attribute, it displays whether the user can modify that attribute and the error message that occurs if not. It also shows the operations (Claim, Issue, Drop, Create, Delete) the user is allowed to carry out on that element. The form is shown by selecting Query > Data Access Control from the bar menu.

Toolbars have been added to the Hangers & Supports application to replace the current forms: the Utilities > Toolboxes > General and

Utilities > General > Support Creation menus now indicate whether the toolbars are shown and toggle their visibility.

The Router forms, PDMS Router , Routing Messages  and Branch Detail , have been made resizable. This means there is no longer a need for a

means of resizing the forms by rebuilding them, so the forms associated with that have been removed.

3.2

Element Selection

(update) *sp4*

Unlike PDMS 11.5, element selection behaviour is similar whether or not Model Editor (Modify) mode is in use: the graphical selection set is

highlighted at all times. [Note: this selection set is not necessarily the same as the Current Element  or the object highlighted in the Explorer.] The highlighting differs according to the element’s Read/Write status: the default edge highlighting being Dashed Green for Read/Write and Dotted Red for Read only. When in Navigate mode (Model Editor not being

used), the selected objects cannot be changed, so all objects appear in the Read/Write highlighting, even if they are Read only.

 A more detailed description of selection is given in the Graphical Model Manipulation Guide  – Chapter 2.

Model Editor button – toggles between Navigate & Modify modes There are two options for entering Modify mode. The first way is to click on the Modify button; the second is to use the pull-down menu

Edit>Model Editor. The same two options are used to leave Modify mode. When in Modify mode with object(s) selected, a handle appears on the selection, which denotes the current interaction mode and guides the user to possible operations. The most appropriate handle is chosen whenever the selection changes. Where an alternative handle is available, the pop-up menu will allow the user to change from (for example) to a 3D handle from the constrained one.

The objects selected by a graphical pick depend on the application, the Navigate/Modify mode and on various settings.

Navigate to Element button – toggles Equipment selection level This toggle is available in Navigate mode only: when selected, the pick will select objects at equipment primitive level. When not selected, the selection will be at Equipment level.

If you wish to edit the equipment, there is a fu rther popup menu ‘Edit Equipment’ while in Model Editor mode – see below.

In the piping application, related objects are selected by default. For example, if a user selects a valve, the system by default selects the flanges and gaskets connected to the valve. If only a single object is required, the shortcut menu option “Select CE” can be used.

 A status bar prompt (e.g. Identify Nozzle) appears when the system expects a 3D pick. If you wish to escape from this, it is necessary first to click in the 3D window.

3.3

Quick Pipe Routing

The quick pipe routing function allows the user to define the path of a pipe wherever there is an ill-defined route within a branch, i.e. where the dotted line is displayed instead of implied tube.

In defining a route the system will allow the user to perform the following:

• Orthogonal and non orthogonal leg definition • Positioning:

o Increment snapping

o Explicit positioning

o Feature snapping

 Centre line

 Offsetting by OD of tube (including insulation)

•  Automatic completion of route

o Where completion is predictable

• UNDO/REDO changes

Where an extremity of a route is undefined, the system will allow the user to assign the end to the last defined point within the route or to designate an appropriate element to which the extremity is connected. Note:

Where a component can not be selected from the spec, the shows a ‘blob’ to alert the user but does not display any other error alert.

3.3.1 Improvements for PDMS 11.6.sp3

*sp3*

Several usability improvements have been made to Quick Pipe Routing. These include the following.

Connection errors are handled better.

The router tries to resolve the appropriate configuration of components when it creates a component, e.g. creating a flange will try and create the gasket as well. Under some circumstances, where the router cannot

connect and position a component with the minimum spool length, the system will now return: Incompatible Connection error.

Set Branch option now sets the current spec of the branch into the form, so that all component Selection is from the branch spec.

Equal size tees with PBOR3 set to E in the relevant column of the spec no longer give a warning message.

See also fault corrections – section 11.5.

3.4

Pipe Component modification

The pipe component modification function allows the user easily to rotate or position a single component or selection of connected components

within the constraints of a pipe route.

In modifying a component or components, the system offers the following functionality:

• Rotation about the tube centre line

• Constrained positioning along the path of the pipe route:

o Increment Snapping

o Feature Snapping

• Components can only be repositioned where there is sufficient space to

fit them in the route

•  Automatic reorder of the elements within the hierarchy to suit the new

position within the pipe route

• The ability to reposition the handle within the constraints of the

component selection set (along the centre line of the pipe)

• The initial orientation of a selection is maintained where possible • UNDO/REDO of changes

The system does not try to resolve any inconsistencies that may occur from the repositioning of a component, e.g. if a reducer is moved into another leg of a branch, the components and tube between its original position and new position in the branch will remain the same.

3.5

Pipe Component creation

The new pipe component creation form allows the user to create a component or component group that is either connected or positioned along the route of a pipe.

The system will automatically try to create a set of predetermined

adjacent component types when certain component types are created, e.g. creating a valve will try to create the appropriate adjacent gaskets and flanges. This allows the pipe designer to define the major components of the pipe route, with the system creating the secondary components

automatically.

Once a component (or group of components) has been created the system will automatically select it, allowing the user, when in “Modify Mode”, to modify the component’s position or rotation.

3.6

Pipe Component Reselection

Pipe components may be individually reselected using the reselection form.

3.7

Equipment Editing

Equipment primitives may now be repositioned using the Equipment editing mode of Model Editor. This involves “drilling down” the

hierarchy to the template, sub-equipment, primitive or negative primitive required.

This mode can be entered by selecting an equipment item and using the pop-up menu to pick Edit Mode > Equipment Editing.

To help selection, when an element in the equipment hierarchy is

selected it is drawn solid, together with its children, and the rest of the drawlist is made translucent. When a positive primitive is selected, any negative primitives that it owns are drawn in wireline, which allows them to be picked: this would not be possible in HOLES ON mode.

3.8

Design Areas

These are 3D volumes encompassing a portion of the plant model. For example, they might encompass a process or part process that can be worked on in isolation. In some industries, they are usually regularly

shaped and aligned with major plant axes; in other cases, they are more likely to be irregularly shaped, positioned and orientated.

New Design Database elements (top level AREAWL, AREASET,

 AREADEF, ABOX, ACYLI, ACONE, ADISH, ASLCY, ACTOR, APYRA and ASNOU) have been added for modelling Design Areas. These

primitives are defined in a similar manner to the normal equipment primitives. Clash detection may be used to determine the contents of these areas.

• Which plant item origins are in a given Area? • For a given item, which Area(s) contain its origin?

Collections have been enhanced to reference Areas: some of the geometric operations have been improved, including an EXCLUSIVE option for WITHIN.

These Areas will be used in future PDMS applications and for improved integration with VANTAGE Project Resource Management.

3.9

New Piping Pseudo Attributes

Several new pseudo attributes are now available for piping.

3.9.1 Branch Surface Area

Branch internal area. Branch external area.

These provide an approximate inside & outside surface area for piping and are valid for PIPE, BRANCH, BRANCH members and SPOOL elements. The following assumptions are made:

•  A Bend or Elbow is treated as a torus; any other Branch Element

is treated as a cylinder or cone.

• If the CMPR on the SPCO is set, the OUTD (Outside Diameter) or

 ACBO (Actual Bore) will be used, otherwise P-Arrive and P-Leave bores and outside diameters will be used.

• Insulation is ignored.

3.9.2 Range of Angles or Radii

Range of available angles. (Optional noun argument) Range of available radii. (Optional noun argument) BRIARE/A

BREARE/A

RANANG/LE RANRAD/II

These pseudo attributes, valid for branch and branch members, provide a list of available angles or radii for selecting bends and elbows. The

information is derived from the branch PSPE and the bore of the previous element in the branch (head bore if the first element). The result comes from the “ANGL” or “RADI”, if appropriate – or is returned “unset”.

3.9.3 Data Consistency

This set of attributes gives a measure of the quality of the pipe route: bores, connection types, offset and angle between a P-point and its neighbour are checked.

 Angle between a branch component and its previous component. Calculates angle between the P-point directions and also with the vector between the P-points and uses the greater.

SPKBRK FALSE ATTAs are ignored

 Angle between a branch component and its next component. Calculates angle between the P-point directions and also with the vector between the P-points and uses the greater.

SPKBRK FALSE ATTAs are ignored

The offset between a branch component and its previous component. Returned in distance units. SPKBRK FALSE ATTAs are ignored.

The offset between a branch component and its next component. Returned in distance units.

SPKBRK FALSE ATTAs are ignored.

Returns true if the connection between a branch component and its previous component is correct. Is also valid when CE is TUBI.

Returns true if the connection between a branch component and its next component is correct. Is also valid when CE is TUBI.

Returns true if the bore between a branch component and its previous component is the same.

Does not consider TUBI. AQANG LQANG AQOFF LQOFF AQCON LQCON AQBORE