pdms 11.6.sp1 release bulletin - cadfamily.com · 3.12 add to drawlist tool bar sp1 ... 3.14 hvac...

PDMS User Bulletin

Version 11.6.sp3

pdI

ms1163/PDMS Bulletin ssue 150506

www.cadfamily.com EMail:[email protected] document is for study only,if tort to your rights,please inform us,we will delete

www.cadfamily.com

VANTAGE PDMS Version 11.6.sp3 ii User Bulletin

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 1974 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 http://www.aveva.com


http://www.aveva.com/engineeringit/world

www.cadfamily.com

VANTAGE PDMS Version 11.6.sp3 Revision history-i User Bulletin

Revision History

Issue Notes 181104 Final draft for PDMS 11.6.0 140705 Final amendments for PDMS 11.6.sp1 – marked *sp1* 261005 Amendments for PDMS 11.6.sp2 – marked *sp2* 281005 Amendments & additions for defects 150506

Amendments for PDMS 11.6.sp3 – marked *sp3*. Along with program corrections and minor enhancements (see chapter 8), changes include:

Piping Application Enhancements Other Design Enhancements (see chapter 3) Changes to support Global 2.4 Support for AutoCAD 2005, 2006 in AutoDRAFT

In addition page headers have been corrected.


www.cadfamily.com

VANTAGE PDMS Version 11.6.sp3 Contents-i User Bulletin

Contents 1 Introduction...................................................................................................1-1 1.1 Overview....................................................................................................................1-1 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-4

1.6 Documentation *sp1* *sp2*.................................................................................1-5 1.7 Operating System and Hardware Environment .....................................................1-5 1.8 Upgrading from previous releases ...........................................................................1-6 1.9 Compatibility (update) *sp3*.............................................................................1-7 1.10 Notice of change in support status *sp3*...............................................................1-7

1.10.1 PDMS 11.4 and earlier ...............................................................................1-7 1.10.2 PDMS 11.5...................................................................................................1-7

1.11 Future considerations ...............................................................................................1-7 1.11.1 AutoCAD integration..................................................................................1-7 1.11.2 Windows versions *sp3* .......................................................................1-7 1.11.3 Use of UNIX servers ...................................................................................1-8 1.11.4 PML features (update) *sp3* ..............................................................1-8

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


www.cadfamily.com

Contents

VANTAGE PDMS 11.6.sp3 Contents-ii User Bulletin

3 PDMS Design Changes ................................................................................3-1 3.1 General GUI improvements .....................................................................................3-1 3.2 Element Selection .....................................................................................................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-5 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-9 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-10 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 Design Database additions – initially for Marine product only *sp1* ..........3-12

3.15.1 Design grid – for ship coordinate system.................................................3-12 3.15.2 Fabrication machine definitions ..............................................................3-12 3.15.3 Pipe pieces & pipe spools ..........................................................................3-12

3.16 Laser model and its manipulation *sp2* .............................................................3-12 3.17 Check Isometrics .....................................................................................................3-13 3.18 Look Explicit *sp3* ..........................................................................................3-14 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 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


www.cadfamily.com

Contents

VANTAGE PDMS 11.6.sp3 Contents-iii User Bulletin

5.2 Use of the 3D features in DRAFT – updated at *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-11 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-13 5.5 Background processes .............................................................................................5-13 5.6 AutoCAD integration with Final Designer............................................................5-13 5.7 UNDO/REDO *sp1* .........................................................................................5-14 6 Customisation...............................................................................................6-1 6.1 Application switching................................................................................................6-1 6.2 Forms & Menus (PML) Enhancements ...................................................................6-1 6.3 Further PML (Forms & Menus) changes *sp1* .....................................................6-3

6.3.1 Gadget layout management ............................................................................6-3 6.3.2 Form enhancements ........................................................................................6-4 6.3.3 New SLIDER gadget........................................................................................6-4 6.3.4 New radio group facility ..................................................................................6-4 6.3.5 List gadget enhancements...............................................................................6-5 6.3.6 Option gadget enhancements..........................................................................6-5 6.3.7 Miscellaneous ...................................................................................................6-5

6.4 Internationalisation ..................................................................................................6-6 6.5 Localisation ...............................................................................................................6-6 7 Summary of non-upwards compatible PML changes................................7-1 7.1 Functional changes at 11.6.......................................................................................7-1 7.2 Layout changes at 11.6 .............................................................................................7-2 7.3 Functional changes *sp1* ...................................................................................7-3

7.3.1 Multi-selection list – Extra Start and Stop meta-events...............................7-3 7.4 Layout changes *sp1* .........................................................................................7-4 8 Product Faults and User Requests .............................................................8-1 8.1 Known faults and Outstanding Issues.....................................................................8-1

8.1.1 Windows fault – correction available..............................................................8-1 8.1.2 Windows faults – file locking...........................................................................8-1 8.1.3 Microsoft .NET Framework Hotfixes KB886903 & KB886904 .....................8-1


www.cadfamily.com

Contents

VANTAGE PDMS 11.6.sp3 Contents-iv User Bulletin

8.1.4 PDMS faults & limitations – corrections planned in future..........................8-3 8.2 Faults corrected and minor enhancements .............................................................8-4 8.3 Faults corrected and minor enhancements *sp1* ................................................8-17 8.4 Faults corrected and minor enhancements *sp2* ................................................8-22 8.5 Faults corrected and minor enhancements *sp3* ................................................8-28


www.cadfamily.com

VANTAGE PDMS Version 11.6.sp3 1-1 User Bulletin

1 Introduction

This bulletin describes the new and enhanced functionality available in the third service pack (sp3) 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: *sp1*, *sp2*, *sp3*.

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.


www.cadfamily.com

Introduction


• 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.

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

Editor, for Piping & Equipment • 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 the ‘Customisation’ chapter of this document. There are many other minor improvements throughout the product and much of the documentation has been updated.


www.cadfamily.com

Introduction


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.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.


www.cadfamily.com

Introduction


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.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 will also be made available, later in 2006, for users of PDMS 11.5, in conjunction with a new service pack SP2 for the latter. However, those which depend on additional database attributes will not be available.

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 8.5.


www.cadfamily.com

Introduction


1.6 Documentation *sp1* *sp2*

This bulletin outlines the major changes at both the original PDMS 11.6 release and its service packs. 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.

1.7 Operating System and Hardware Environment

PDMS 11.6 is supported for use on Microsoft Windows 2000 SP4 and Windows XP Service Pack (SP) 1 1. There is no UNIX version of PDMS 11.6. PDMS 11.6 requires the installation of Microsoft’s .NET Framework 1.1, which it uses for the graphical user interface. This is supplied on the CD-ROM and installed if necessary.

1 PDMS 11.6 will run on Windows XP SP2, but 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.


www.cadfamily.com

Introduction


PDMS 11.6 should run successfully on Windows NT4, but it has not been tested under Windows NT4 and is no longer supported in that environment. Please note that Microsoft no longer offers mainstream 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.8 Upgrading from previous releases

PDMS 11.6.sp3 is fully compatible with earlier releases of PDMS 11.6 and requires no upgrade. 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 new application switching mechanism. Please see section 6 Customisation. 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.


http://www.aveva.com/engineeringit/world/

www.cadfamily.com

Introduction


1.9 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.10 Notice of change in support status *sp3*

1.10.1 PDMS 11.4 and earlier

PDMS 11.4 will change to ‘inactive’ support status in June 2006, which means that it will not normally be supported with releases of any kind. At the same time, all earlier versions will be ‘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.10.2 PDMS 11.5

PDMS 11.5.sp1 will be superseded by a further service pack sp2 later in 2006. This will be accompanied by an updated version of Global 2.2: both should be used together and will be treated as fully supported, with previous versions of 11.5 moving to ‘inactive’ support.

1.11 Future considerations

1.11.1 AutoCAD integration

Final Designer interfaces with AutoCAD and will supersede some of the older AutoDRAFT functions. The latter will be withdrawn at the next major release. The DXF output feature is unaffected and will remain.

1.11.2 Windows versions *sp3*

Microsoft now expects to release the next versions of Windows, Vista, around the end of 2006. AVEVA expects to start supporting it soon after its release, possibly for PDMS 12.0, and will drop support of Windows 2000 around the same time. Almost all development at AVEVA is now


http://support.aveva.com/support/United_Kingdom/index.htm

www.cadfamily.com

Introduction


carried out using Windows XP (service pack 1 or 2), which is currently the preferred option. PDMS 12.0 will definitely require the installation of Microsoft’s .NET Framework 1.1 service pack 1 or later.

1.11.3 Use of UNIX servers

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 will not be supported from the next major release. This is because of changes planned to allow larger PDMS databases. Testing for PDMS 11.6 has used Samba 2.2.8a. The improvements being made to PML to provide a more powerful customisation environment, which complies better with Windows standards, mean that certain older features can no longer be supported. The following deprecated features will be removed at PDMS12: this may well necessitate changes to some users’ PML applications.

1.11.4 PML features (update) *sp3*

Various changes are anticipated at the next major release, PDMS 12. Those writing PML applications should particularly note the following:

RADIO gadget This gadget has been deprecated and has not been documented for several years. It will no longer be 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.

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.

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 gadget’s SELECT call-back will not be run (a SELECT event is NOT notified to PML).


www.cadfamily.com

Introduction


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.

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.

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.


www.cadfamily.com


2 PDMS GUI – General changes

PDMS 11.6 uses the Microsoft .NET environment including the latest 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 menu, which provides a method of switching to it.

CE “Current Element” – the single PDMS object that is acted upon by the PDMS command line and by many


www.cadfamily.com

PDMS GUI – General changes


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 locale. 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.


www.cadfamily.com



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. Note. Some toolbar tools cannot be displayed when a toolbar is docked 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.


www.cadfamily.com


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 Representation and P-point Representation forms.

VANTAGE PDMS Ve 2-4 rsion 11.6.sp3 User Bulletin


www.cadfamily.com


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.



www.cadfamily.com



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. For a copy to be valid the following must be true:


www.cadfamily.com



• 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.

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. • Copied elements and all their child elements are copied.


www.cadfamily.com



• 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.

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.

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

either to an existing Collection or as an orphan


www.cadfamily.com



• 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 information about all elements currently added to the 3D View. It allows


www.cadfamily.com



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.


www.cadfamily.com


3 PDMS Design Changes

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


www.cadfamily.com

PDMS Design Changes


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


www.cadfamily.com

PDMS Design Changes


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

3.2 Element Selection

At PDMS 11.5, element selection behaviour was different when in Model Editor mode. At PDMS 11.6, the selection method and the graphic feedback are always similar: the selection set is highlighted at all times. However, 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, with the 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. When in Modify mode with object(s) selected, a handle appears on the selection, which denotes the current interaction mode, and quickly guides the user into the possible operation in this mode. The mode is revised whenever an object is added to or removed from the selection. There are two ways that the user can enter Modify mode. The first way is to click on the Modify button, when the system will start in the most likely interaction mode. The second way is to right click, when all possible interaction modes are offered on the pop-up menu. The system then switches into the selected interaction mode and presents the user with the appropriate handle. At any time in modify mode, the user can change the current interaction mode by right clicking and selecting a new mode from the list of options. To leave Edit mode, the user must click on the Modify button to toggle it off, at which point the current handle is removed. To aid the user in making selections, related objects are selected by default: at the moment this only affects piping components, but may be extended to cover other types of objects at a later date. 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. N.B. 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.


www.cadfamily.com

PDMS Design Changes


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.


www.cadfamily.com

PDMS Design Changes


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 8.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


www.cadfamily.com

PDMS Design Changes


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?


www.cadfamily.com

PDMS Design Changes


• 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

BRIARE/A Branch internal area. BREARE/A 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

RANANG/LE Range of available angles. (Optional noun argument) RANRAD/II Range of available radii. (Optional noun argument) 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”.


www.cadfamily.com

PDMS Design Changes


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. AQANG 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

LQANG 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

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

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

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

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

AQBORE Returns true if the bore between a branch component and its previous component is the same. Does not consider TUBI.

LQBORE Returns true if the bore between a branch component and its next component is the same. Does not consider TUBI.

PQANG <int> Angle between specified P-point of a branch component and its adjacent component. Calculates angle between the P-point directions and also with


www.cadfamily.com

PDMS Design Changes


the vector between the P-points and uses the greater. SPKBRK FALSE ATTAs are ignored. Attribute is valid for Branches. For branch members, only the arrive & leave P-points are valid.

PQOFF <int> The offset between specified P-point of a branch component and its adjacent component. Returned in distance units. SPKBRK FALSE ATTAs are ignored. Attribute is valid for Branches. For branch members, only the arrive & leave P-points are valid.

PQCON <int> Return true if the connection between a branch component and its adjacent component is correct. Is also valid when CE is TUBI. Attribute is valid for Branches. For branch members, only the arrive & leave P-points are valid.

PQBORE <int> Return true if the bore between a branch component and its adjacent component is the same. Does not consider TUBI. Attribute is valid for Branches. For branch members, only the arrive & leave P-points are valid.

3.10 New Attributes for Material Management

The following attributes have been added, primarily to facilitate integration with VANTAGE Project Resource Management (VPRM).

3.10.1 Status attribute for use in MTO output

A new attribute, FSTATUS, has been added to the following elements: PIPE, STRU, EQUI, REST, ZONE, PCOM, ATTA, SPLDRG, SPEC

3.10.2 Additional attributes for spool MTO

The following attributes have been added to the SPLDRG element: FAREA, FPLINE, FDRAWING, FREVISION, FRDRAWING


www.cadfamily.com

PDMS Design Changes

3.10.3 Additional attributes for Piping Specifications

The following attributes have been added to the SPEC element: FISSUE, FINPUTBY

3.11 Extract Refresh

Modifications in PDMS can cause the Spatial map for an Extract to change, resulting in the Map being updated on entry to Design. As a result the User will now need to do a SAVEWORK to save the changes before an EXTRACT REFRESH command can be executed.

3.12 Add to Drawlist tool bar *sp1*

This enables the user to specify the visual properties of items added to the drawlist, for example by dragging from the Explorer to the 3D view. The options are Auto (rule-based) or Specific (colour, translucency and edges on or off).

3.13 Piping component (e.g. flange) alignment *sp1*

This development allows piping components to be connected so that by default their Z directions are aligned. This is particularly useful for ducting and cable trays etc. – or where flanges need to be aligned. The following changes have been made:

• A PZAXIS attribute has been added to various ppoint elements in the catalogue.

• New pseudo attributes allow it to be queried in the design. • The connect command has been enhanced to use the PZAXIS if set. • Appropriate Datacon checks have been added.

3.13.1 New attribute for PTCA, PTAX, PTMI, PTPOS

PZAXIS – Z direction



www.cadfamily.com

PDMS Design Changes


3.13.2 New pseudo attributes for branch members

• PZDIR – Alignment direction for specified ppoint. • AZDIR – Alignment direction for arrive ppoint. • LZDIR – Alignment direction for leave ppoint. • PQAANG – Angle between alignment direction for specified ppoint

and adjacent component. • AQAANG – Angle between alignment direction for arrive ppoint

and previous component. • LQAANG – Angle between alignment direction for leave ppoint

and next component.

3.13.3 Connection Command

The syntax of the command is unchanged, but it now uses valid alignment directions in place of a default orientation. It checks that a PZAXI is set for the relevant ppoint of the current element and for the ppoint it is connecting to. If the element being connected to is a gasket or a weld and does not have a set PZAXI then the ppoint of the next element is used instead. If there are either one or two unset alignment directions, then the connection command functions exactly as before. If an orientation is specified, e.g. CONNECT AND P3 IS UP, then this will override the alignment direction.

3.13.4 New Datacon warning messages

The following warnings can now be generated. They are not output if the branch is badly routed.

D850 BAD ARRIVE ALIGNMENT GEOMETRY, ANGLE IS 15 D850 BAD LEAVE ALIGNMENT GEOMETRY, ANGLE IS 45

3.14 HVAC application – new components *sp1*

The range of components supplied with the standard application has been increased.


www.cadfamily.com

PDMS Design Changes


3.15 Design Database additions – initially for Marine product only *sp1*

3.15.1 Design grid – for ship coordinate system

A new top level element GRIDWL has been added – but this is not used in PDMS at present.

3.15.2 Fabrication machine definitions

A new top level element FMWL has been added – but this is not used in PDMS at present.

3.15.3 Pipe pieces & pipe spools

New elements PPLIST (Pipe Part list) & PSLIST (Pipe Spool list) have been added – but are not used in PDMS at present.

3.16 Laser model and its manipulation *sp2*

These options are only useful when the new Laser Model Interface is installed. Details are available in its documentation. The links to this external geometry are stored in new database elements XGEOM, XLCTN, XCELS. This enables the point cloud model to be visualized, measured and clash checked alongside the PDMS model.


www.cadfamily.com

PDMS Design Changes

3.17 Check Isometrics

Check Isometrics can now be produced from within Design and Spooler. Extra syntax has been added to the command line:

• Isodraftmode switches into the Isodraft syntax. • Exit returns the user to the Design/Spooler syntax.

The Utilities menu has been extended in the Design Pipework discipline. (A similar capability has been added to the Spooler module). Selecting Pipe Isometric… or System Isometric… at a Pipe, Branch, Spldrg, Spool or Field element will display a preview isometric (processed using a predetermined options file, which may be replaced by the user). There is a button to display the process time messages. Selecting Show Pipe System… at a pipe or branch element will highlight the connected system for that element in the 3D view. A Windows printing mechanism is also provided: it is possible to print single sheets using or all sheets using . There are similar icons for previewing single or multiple drawings and for saving them to file.



www.cadfamily.com

PDMS Design Changes

3.18 Look Explicit *sp3*

The Explicit view direction option has been reintroduced in Design, on the Limits CE Options popup menu. The user can enter the required angle for the view direction, for example looking along a structural member.

The Look – 3D View form has a popup menu for setting view direction; this allows the user to use the orientation of picked graphical items to populate the Direction field.

VANTAGE PDMS 3-14 Version 11.6.sp3 User Bulletin


www.cadfamily.com


4 Piping Isometric Enhancements

In addition to the new check isometric facility in DESIGN and SPOOLER, a number of improvements have been made to the ISODRAFT module, some involving data set up in other parts of PDMS. They are listed here for convenience.


ISODRAFT has a new Office 2003 style GUI, based on Microsoft’s .NET. This includes many new features such as window and toolbars docking, tabbing etc. Please refer to section 2.2 Application Framework for further details.

4.2 Parameterised MTOL & MTOQ

It is now possible to parameterise MTOL & MTOQ – for example, the following is now possible:

MTOQ (PARA[3] + DESPAR[2] )

4.3 Use of temperature and pressure for selection

The temperature and pressure attributes from the owning branch can now be used as Spec selectors for choosing bolting items in ISODRAFT. Spec answers may use a specific value or give a range.

4.3.1 Standard Bolt Hole DB Change

The bolt set BTSE now has some of the same attributes as a BLTP: BTHK, BDIA, BTYP as well as a new attribute: NOFF (number off), which is defined as for the SBOL element. If these entries are set, the program automatically creates an array with NOFF members which are the default bolts for this connection.


www.cadfamily.com

Piping Isometric Enhancements


This enables a drastic reduction in the amount of data that is required to define bolt requirements. However, if the new attributes are not set, the existing methods continue to work in exactly the same manner. BLTPs should still be used as members of a BTSE for those numbers where there is a deviation from the standard bolt as defined in the BTSE or if the bolt hole numbering is non continuous. Note that Jacking bolts must always be defined using BLTPs.

4.4 User-defined Material Lists

The restrictions on users defining their own material list format have been eased. It is no longer necessary to be using the PARTNUMBERS FROMDB option in order to do this. See MATERIALLIST command in the VANTAGE PDMS ISODRAFT Reference Manual.

4.5 Spooler – Pulled bend numbering *sp1*

A new option has been added to the PARTNO command, for each of its CREATE, CHECK and UPDATE <gid> options, e.g.

PARTNO CREATE <gid> PARTNO

This PBEND option (at the end of each command) will result in bends having unique part numbers and will ensure implied tube either side of the bend will have the same part number. Not all bends will be numbered using this syntax; zero length bends will not be numbered.

4.6 Isodraft – Pulled bend numbering *sp1*

The syntax for PARTNO has been modified to include a new option for pulled bends:

PBENDNUMBER ON PARTNO

This will use the part number rather than the bend number as the source of the Bend number on the drawing – and in the bend table if shown.


www.cadfamily.com


5 Drawing Production Enhancements

For the PDMS Draft user, PDMS 11.6 provides access to a 3D colour shaded graphical view for use in the definition of drawings. The user can use it to define the contents of a drawing or to set the direction and limits of a 2D view. This feature has been refined at PDMS 11.6.sp1. For the PDMS Draft user, PDMS 11.6 provides access to a 3D colour shaded graphical view for use in the definition of drawings. The user can use it to define the contents of a drawing or to set the direction and limits of a 2D view. This provides a highly intuitive and productive user interface that will help to reduce drawing production times and enable users to work in a familiar 3D environment. Users can create and manipulate section planes in the 3D graphical view using direct graphical interaction, and apply these section planes to any view on the drawing. This displays in 3D the position of each part of the section plane and is therefore simple to use, even for complex stepped section planes. Further productivity improvement is achieved through the introduction of a dockable database explorer and presentation of key annotation features in a common application, removing the need for the user to switch applications when adding basic annotation to drawings. Isometric creation is typically performed as a batch job. However, for the piping designer it is highly beneficial to produce a check isometric or system isometric at various stages in the design process. PDMS 11.6 will allow the piping designer to produce a standard isometric or system isometric from within PDMS Design or PDMS Spooler, allowing the designer to stay focussed on the piping design whilst generating isometrics to assist in the design process. For further information, please refer to the section on Design.


A new Office 2003 style GUI, based on Microsoft’s .NET, is now used in Draft. This includes many new features such as window and toolbars docking, tabbing etc. Please refer to section 2.2 Application Framework for further details. In addition the Draft applications have been rationalised with the various sub applications merged into a unified environment.


www.cadfamily.com

Drawing Production Enhancements


5.1.1 Merged sub-applications

Dimensioning, Labels and 2D draughting applications have been merged into one General application, so that all utilities are available to the user without changing application or swapping menus. DRAFT applications maintain the layer options (on the main window) to enable the creation, in the appropriate place, of any 2D element, dimension or label. The Main Draft Menu has changed to remove the working sheet selection and add a new members list explorer, with a mouse shortcut menu to add a sheet to the 2D. The Dimensioning, Labelling and 2d draughting applications have been removed, as they are now all merged into the general application. The Utilities from the 2D Draughting menu have been added to the General Utilities menu, which is similar to the application utilities in DESIGN. Changes have been made to the Create and Modify menus as part of merging the applications, with all the 2D draughting menus added to the main menu.

Layers The user can select a layer, but the application will select an appropriate one, if required, before creating any element. The layer gadget new has ALL the layers pertaining to the current sheet listed, and this gadget can be filtered by using the new gadget Filter, to list only those of the application the user is working on. If the user changing from Dimensioning to Labelling, the application will switch the layer gadget to list labels and select the first label type layer. The user can re-select a different layer if required. The Layer gadget will always change within the currently selected view, so if the user creates a dimension in view 1 and then creates a label, the layer will switch to a labelling layer in view 1. Navigation around the DRAFT db automatically exchanges the layer selection if a different view is selected. Clicking on a view has the same effect as navigation to it. Navigation to a dimension automatically changes the layer to a dimension layer and highlights the view to which the dimension belongs. This makes it easier to know where you are on the drawing and where you are likely to create the next element.


www.cadfamily.com



Database Hierarchy Sheets may now be added to or removed from the 2D window from the Explorer. This means it is necessary to check the position in the hierarchy before adding something to the 2D window. If the user is too high, i.e. above drawing level, then an error informs the user that the “REGI/DEPT is not a valid working sheet”. However, if the user is at drawing level, ALL the sheets are now added, even if there is more than one. A message is displayed to inform the user that there are several sheets, so they should check that they require them all to be added.

5.1.2 User utility menu

A User application utility menu is now available in DRAFT, under the general application. This utility allows the user to create menus for his own use. The functionality is similar to that in DESIGN.

5.1.3 Dimension and 2D drawing forms

These forms have been changed so that dimensioning and 2D draughting can be called from either form or toolbar. Some of the dimensioning functionality has been moved from the utility menu and put under the modify menu, to make it easier to find.

5.1.4 Labelling rationalisation

Labels have been rationalised and made dockable wherever possible. This affects the Autotagging, Labelling and Gaps forms. The autotagging form has been redesigned in order to reduce its size and make it dockable. The regenerate tag button has been removed and replaced with a toggle, so that the update button is the only button used to execute the form. Checking the regenerate toggle and pressing update regenerates the tags. The labelling forms for SLAB (symbolic labels) and GLAB (General Labels) have been combined and redesigned to be dockable, so that they can be displayed all the time without obscuring the user’s view of the 2D drawing canvas. The main menu has been rationalised to show the new form, with the modify menu reduced and some of the attribute settings removed, as they are all covered in the new form.


www.cadfamily.com



5.2 Use of the 3D features in DRAFT – updated at *sp1*

A 3D volume view is now available in DRAFT: it has similar properties to that in Design. This can be used to explore the 3D model and identify objects for drawing production. There are also 2 database browsers: for Draft and Design databases. The Design browser has a mouse shortcut menu option to add elements to the 3D view. You can also Drag-and-drop from the Design browser to the 3d view. Various improvements have been made to the usability of the 3D View at sp1, notably to the behaviour of the view frame and section plane features.

5.2.1 3D Commands

DESADD & DESREM commands allow the Addition and Removal of Design elements to a 3D view gadget. These are similar to the ADD & REM commands in Design. The GENERATE MODEL command allows capture of a 2D view content and colour for addition to the 3D view. The GENERATE MODEL command allows capture of a 2D view content and colour for addition to the 3D view. A new IDLIST object is now available to transfer the 3D contents to the 2D IDLIST (ADDE and REME elements). A new SELECTION object provides a graphical aid of a 3D selection box. This is called using the mouse secondary button in the 3D view. A new VIEWFINDER object provides a graphical aid that represents the 2D view position, size and direction in the 3D view to allow interactive positioning of the 2D view through point and view direction.

5.2.2 3D user interface

The new 3D view is similar to the 3D views in Design and may be initiated from these menus: 3D View... from the shortcut menu for the 2D view or Display > 3D View… from the main menu.


www.cadfamily.com


Associated View

5.2.3 Managing 3D view content (Drawlist)

(ToolTip 'Add to View') adds elements to the 2D Idlist and the 3D view. The Draft idlist ADDE elements are created at this time. This is done to help workflow so the user does not have to do an UPDATE DESIGN at this time. Updates could be done at anytime, even as a background process or overnight job. The element added to the idlist will generally be the current element, unless there is a multi selection active, when the selection will be added. Elements added to the ID List will be displayed in colour specified in the view representation rules.

(Tooltip ‘Remove from View’) removes elements from the 2D Idlist and the 3D view. The Draft idlist REME elements are created at this time The element removed from the idlist will generally be the current element, unless there is a multi selection active, when the selection will be removed.

(Tooltip ‘Show View Content...' ) Show a form displaying the 2d view Idlist (An UPDATE DESIGN may or not have been performed on this) . This button is a toggle button to show or hide the ID List Contents form.

VANTAGE PDMS n 11.6.sp3 5-5 VersioUser Bulletin


www.cadfamily.com


This toggle gadget on the form, when ticked, means that the Idlist will be amended appropriately when an element is added to (or removed from) the 3D view directly from the Design Explorer. This is seen in the 3D view in the correct representation colour. If the gadget is unticked, this means that the element is added to the 3D view only and the 2D Idlist is unchanged. Such items are added to the 3D view in grey colour. Therefore the significance of coloured items in the 3D view is that these items have been added to the idlist. Grey items in the 3D view indicates these items are in the 3D view but are not in the 2d idlist so even an Update Design will not recognise these elements.

5.2.4 Multi Selection

The + and – buttons will add or remove the current element unless a Multi-selection has been made using the CTRL+pick or by dragging out a frame. A primary mouse button drag on the 3D view gadget will initiate a selection box as shown below. This allows the user to multi pick elements within or partially within a volume. The box can be resized by movement arrows indicated on each side of the box. The box can also be used as a clip box. Two separate examples are captured below.



www.cadfamily.com


The following menu is presented when doing a secondary mouse button drag:-

When the box is displayed it appears as above. The box can be resized by dragging the arrows. Picking the arrows on the displayed selection box with a mouse click the following menu is shown.

VANTAGE PDMS 5-7 Version 11.6.sp3 User Bulletin


www.cadfamily.com


The background also has the following menu addition Clipping Planes On – This clips the graphics to the content of the selection box.

5.2.5 Scale control

The view scale can be specified using direct input or form. Any change of scale will be reflected in the 2D and 3D immediately. The Scale gadget displays a standard scale dialog to maintain a consistent feel in Draft.

5.2.6 UNDO/REDO

Database marks have been included: 1. When an element is added to the View – The View Content form will be updated. 2. When an element is removed from the View – The View Content form will be updated.

5.2.7 Modify Star

When the 3D View form initiates any database change such as: Change in scale; Add to View; Remove from View; Move viewfinder, (which modifies view through position) the form title changes from ‘3D View’ to ‘3D View*’

The * indicates that an Update Design is required using the button. Once the Update Design is done the * indicator is removed.

5.2.8 3D to 2D (Update Design)

(Tooltip 'Update 2D View from 3D view (i.e Update Design)') The Elements displayed in the 3D view that are in the IDlist can be transferred to a 2D view by simply pressing this button. At this time the user may be asked if he wishes to do an Update Design and warned that this can take a while. An Update can be done at this time or later by using the Background Process Manager.



www.cadfamily.com


5.2.9 2D to 3D

(Tooltip ‘Update 3D View from 2D View’) The contents of the current 2D view can be displayed in the 3D view by pressing this button. The associated view name is displayed next to this gadget.

(Tooltip ‘Pick 2D View to associate to the 3D View’) This button can be used to retain the current 3D view contents, to be associate it to a different 2D view. The user is asked to identify a 2d view. This is useful when different views of similar content are required (e.g. Plan and Elevations)

5.2.10 Display of 2D view frame in the 3D view gadget

The limits of the associated 2D view are represented in the 3D view using the VIEWFINDER. This is shown in the above snap shot by the purple rectangle. The colour is, by default, the same as the highlight colour of the 2d view – but can be changed. The view finder is a core object that can be:

Figure 1 Figure 2

1. Graphically dragged to reposition the view through point. 2. Graphically rotated using the corner blobs. 3. Graphically resized using the arrows shown in the Figure 2. In each case the 2D database is changed. Note that a view can be inverted or turned through 90 degrees by using the popup ‘Rotate Frame>’ options.



www.cadfamily.com


Similarly to switch between the Normal mode shown in Figure 1 and the Resize mode shown in Figure 2 use the popup ‘Resize Frame’ toggle.

5.2.11 Update control

It is PDMS User interface philosophy not to have hidden UPDATE DESIGN operations. It is usually exposed so the user is aware that this is going to happen, because this can take some time to update. Therefore we have continued to separate this operation.

The Update Gadget has 3 options: ‘On Demand’ meaning UPDATE DESIGN when the 3D to 2D button is pressed. ‘Background’ meaning UPDATE DESIGN as On Demand, by using the Background Process Utility . ‘Auto Update’ meaning UPDATE DESIGN dynamically when the 2D view changes (i.e. View Content, Scale, Direction, View Type, etc)

5.2.12 View Type

In the frame for update there is an option gadget to specify the type of view to be generated in the 2D. The options in the gadget are the full PDMS list of view types, ranging from Universal Hidden Line to Wireline. Selecting one of these will change the database. Note that section planes do not clip in wireline views.

5.2.13 Section Planes

(Tooltip 'Show Section Planes') This toggle button activates the section planes and displays the Section Planes form. Note that section planes can be individually hidden or shown, so check settings on form..

(Tooltip ‘Indicate Section Plane clipping') This toggle indicates the clipping side of the section plane by graphically displaying a series of perpendicular lines behind the section plane.



www.cadfamily.com



5.2.14 Representation in 3D view

It is possible to change the 3D representation, such as holes on/off, for 3D elements as in Design.

5.2.15 Viewfinder Shortcut menu.

Align Frame with 3D View – Used to modify the view direction. Adjust the 3d view to the desired view direction then use this option; and the view finder will snap to this new direction. Update Frame from 2D View – If the view has been changed using 2D appware the 3D could be out of date. Use this option to update the 3d view. Center Frame – Centres the frame in the centre of the view gadget. Rotate Frame > – Options for Up, Down, Left, Right which allow the view to be instantly inverted or turned through 90degrees. Resize Frame – (Toggle) Changes the mode of the View Finder so that is can be resized. (See the above section ‘Display of the 2D View in the 3D View gadget’ ) Lock Frame – This is a toggle that locks or unlocks the frame to prevent accidental movement of the view frame. There is always an undo option but the user may not be aware he has moved the frame. Hide Frame – Hides the frame by making it invisible. To reshow the frame there is a Show Frame option on the view background menu. Auto Update – If this toggle is on then each time the frame is moved, an Update Design is done. This should be used sensibly depending on view content because large data will take a long time to process. Frame Colour > White,Orange,Blue,Green,Magenta,Cyan,Yellow – Changes the frame colour to the selected colour toggle. The current colour will be ticked. Translucent Frame – Gives the frame a background translucency or no background. A translucent frame is easier to pick but can partially obscure some of the content..

5.2.16 3D view Shortcut menu additions related to view finder.

Look >Through View Finder – This is a quick way to change the 3d view direction to look squarely through the view finder.


www.cadfamily.com



View Finder>Show Frame – Reshows the view finder frame (The hide option is on the view finder menu itself) Highlight Frame – Highlights the view finder frame by flashing it. Similar to the Highlight CE in 2D view. Center Frame – Centres the frame in the centre of the view gadget.

5.3 Template drawings

Create>New Drawing from Template… utility. Key Features: • The utility does not require the input of a name for the new drawing. • If the user is not at the correct hierarchal position, the system will

attempt to navigate to an appropriate place to create a drawing, and ask the user to confirm if necessary.

• Templates made from DRWG or DRTMPL are valid. • The Selection of the Template is more visual. • Once the drawing has been created, the user can then utilise the 3D

view to define the view contents. See below. • New ‘Drawing’ creation and New ‘Drawing Sheet’ creation are

allowed. • Default names or user names are allowed.

5.4 Section planes

The User can now create, edit and view section planes in a 3D model window from within Draft, before adding these to a drawing view. This makes it easier for the user to work with section planes, but does not affect the existing working methods. It does improve the presentation of section plane information and their effect on the drawing. The Section Planes window is initiated from the 3D View window. It enables the creation and editing of section planes, both simple and stepped, and their associated clipping lists.


www.cadfamily.com



5.4.1 Improvements for *sp3*

Several improvements have been made to the operation of section planes, including: • Planes are now shown on the 2D view at same time as on the 3D view. • There is now a new menu option (keyboard shortcut C) to cause an

extra step to close the stepped plane profile. • The axes and the drag plane can now be used to align the section

plane to a feature. • The Modify Section form now updates the 3D view when Apply is

pressed. For example, if the plane is flipped, this is now shown in the 3D view.

5.5 Background processes

Certain PDMS commands may take a long time to complete. PDMS 11.6 introduces a background process manager (BPM) for managing the UPDATE DESIGN command. This technology may be extended to other processes in future releases of PDMS. When the background process is updating a particular view, it is possible for the user to edit another view on the same sheet. That is, there is no contention between the foreground and background processes. The BPM does NOT need to be active at the same time as the main PDMS session. For example, the user can submit any number of UPDATE DESIGN jobs and then exit before the BPM is started. The two processes are completely independent so that the BPM can run overnight, for example. However, once a BPM job has completed a PDMS session must of course be started to refresh the updated element. Picture files are not updated directly by the BPM.

5.6 AutoCAD integration with Final Designer

PDMS 11.6 will bring a new option for the final production of AutoCAD drawings: first release is expected with the next service pack of PDMS 11.6. The new Final Designer product enables users to export their Draft drawing sheets to AutoCAD with links to the Draft database maintained. It is anticipated that users will continue to develop drawing sheets in PDMS Draft and make use of the automation features: when a drawing sheet is ready for final design it will be exported to AutoCAD.


www.cadfamily.com



An exported drawing sheet can be accessed through PDMS Draft by navigating to the sheet and opening it. The sheet is displayed in an AutoCAD session for viewing or further editing. Within AutoCAD, users can add dimensions, labels, intelligent text and 2D primitives. Where applicable, annotation can be attached to P-points or P-lines enabling the annotation to be updated when the design graphics change. If Design graphics change, they can be updated in the same way as standard Draft views: the changes are shown on the AutoCAD sheet. Creation, deletion and modification of annotation in AutoCAD are communicated to PDMS Draft so that the database links are maintained, however, full details of the definition are not communicated. This means that, for annotation created or modified in AutoCAD, the AutoCAD sheet stores the up-to-date definition. Automation features in PDMS Draft should continue to work on AutoCAD sheets with the exception of any commands that require interaction with the Draft picture file such as ID commands.

5.7 UNDO/REDO *sp1*

This is now available in DRAFT.


www.cadfamily.com


6 Customisation

6.1 Application switching

The application switching mechanism in Design, Draft and Paragon has been changed to remove the need to swap the main form when changing application and to make it easier for the user to make additions to the appware. An object provides more control over the display of forms in different applications. PML add-ins are available in PDMS 11.6. An add-in can: • appear as an application on the main PDMS menu bar; • define menus and toolbars; • add menu fields and toolbars to applications; • remove menu fields from applications; • cause functions to be run when starting or switching between

applications. Each existing application is implemented as a PML add-in. It is important to make a distinction between an add-in that defines an application and other add-ins. An application appears on the Applications menu and can be switched to, whereas an add-in simply provides a means of adding functionality to the module. Information on how a user may upgrade existing applications and define PML add-ins and control form display/reloading can be found in the PDMS Software Customisation Guide Chapter 24 – PML Add-ins.

6.2 Forms & Menus (PML) Enhancements

An improved Gadget Set for PDMS 11.6 provides: • Docking forms in the PDMS Application Framework • Definition of intelligent resizable forms • Toolbar definition in the PDMS Application Framework • Tabbed multi-page form definition • User-defined menu field names


www.cadfamily.com

Customisation


• Menu and menu bar editing enhancements • Other miscellaneous enhancements. 1. DIALOG forms are floating by default, but may be declared docking. Docking dialogs are necessarily resizable and can be docked to an edge of the PDMS Application Framework. Docked dialogs can be specified as docked, or can appear floating and then be docked interactively. 2. DOCUMENT forms are MDI children by default, and as such will be constrained within the PDMS Application Framework MDI client frame. However they may be interactively floated outside the MDI so that they can be dragged off onto the second screen of a twin screen installation. Similarly a floating dialog can be interactively ‘unfloated’, i.e. once again constrained within the MDI frame. 3. The layout of resizable forms has been improved by exposing WinForms properties Dock and Anchor on most F&M gadgets. In particular, a frame gadget itself has Dock and Anchor properties, and may own other frame gadgets. The gadget Dock and Anchor attributes permit the definition of intelligent position and resize behaviour when its container gadget resizes. The net effect is to allow multiple resizable gadgets on a form and predictable and potentially complex resize behaviour. Existing resize behaviour has been maintained. 4. The Frame gadget is now a genuine container for all gadgets defined within its scope. This permits easy management of properties such as visibility for all its children. It also supports various frame types, which allow the definition of toolbars in Main forms and Tabbed Pages within Dialogs and Documents. 5. Menu field names and Menu and Menu bar enhancements are supported as a basis for menu editing for sub-applications and Add-ins.

• to support PML defined main menus for Add-ins • to support PDMS core-code to take over main menus • to support enhanced menu editing • to support enhanced Bar-menu editing

5. Miscellaneous enhancements • Every gadget has a VISIBLE property, which can be queried and

set via PML. • Graphical view gadgets now have BACKGROUND and

HIGHLIGHT methods to query the view background and highlight colours as colour-name strings.

• Previously only pix-mapped buttons supported toggle behaviour, i.e. on/off state with visual differentiation: this has been extended to allow toggle button behaviour for all buttons.


www.cadfamily.com

Customisation


6.3 Further PML (Forms & Menus) changes *sp1*

Further improvements to PML forms & menus capability for this service pack are noted here: full details are given in the two PDMS Software Customisation Manuals, which have been updated and expanded.

6.3.1 Gadget layout management

It is difficult to predict the extent of gadgets which have a displayed Tag attribute, because the size depends on the particular tag string. This is made worse for gadgets whose content is also defined by a string (or strings) rather than by an explicit width and height specification, e.g. TEXT, OPTION, RGROUP. Determining the width as the number of characters in a string multiplied by the grid size (notional character size for the font) is not satisfactory because typically a mostly lower case string of 10 characters say, only occupies about 60-70% of the 10 X notional character spaces. Thus it usually results in lots of blank space, but for pictorial fonts, such as Korean and Japanese, where the characters tend to be wide it may cause truncation or wrap-round of the displayed string.

Tagwidth and ButtonWidth attributes The introduction of an optional Tag width specification for TEXT, OPTION, RGROUP and TOGGLE gadgets and ButtonWidth attribute for RGROUP gives the user (and F&M) more control over the size of gadgets, independent of any string content and is upwards compatible. This allows the Appware writer the possibility of removing the unwanted ‘empty’ space in gadget tags and radio groups and greatly improves alignment possibilities with other gadgets.

Relative Gadget Extent specification Form layout syntax has been extended to allow gadget size specification relative to the size of previously defined gadgets on the form. This mechanism makes it easier to construct forms in which the widths and/or heights of various gadgets need to be the same as one another. The combination of tag width specification and gadget relative size specification greatly improves the ability to produce predictable form layouts. This is particularly important for the construction of intelligent resizable forms, where the static layout must be correct, but may never actually be seen because of resizing during the first display.


www.cadfamily.com

Customisation


Button Width and Height specification New Button Width and Height specification allows the Appware writer to remove the unwanted ‘empty’ space in Buttons and greatly improves alignment possibilities with other gadgets.

New ‘No gadget auto-alignment’ property for Forms Traditionally PML Forms have the notion of a set of linear gadgets, namely BUTTON, TOGGLE, TEXT, OPTION, single line PARGRAPH and horizontal RGROUP with no tag. These are gadgets which fit within 1 vertical grid unit, and which are pseudo-centre-aligned with each other when displayed. This pseudo-alignment gives sensible layout for simple forms for PATH RIGHT (the default) and PATH LEFT, but introduces small errors in all other circumstances. A new form setup keyword noalign has been introduced, which prevents this (historical) gadget auto-alignment from happening. If proper centre-alignment of gadgets is required for horizontal layout paths then the VALIGN CENTRE command should be used, which applies accurately to all gadget types. This NoAlign setting is recommended when designing new PML forms.

6.3.2 Form enhancements

New QUIT callback Forms now have a QUIT callback which allows intelligent support of the Quit/Close icon on the title bar of forms and the main application window.

6.3.3 New SLIDER gadget

This allows the interactive generation of an integer value in a specified range (see the border controls on 3D views). Vertical and horizontal sliders are supported.

6.3.4 New radio group facility

It has become apparent that quite a lot of Appware overlays the radio group gadgets (RGROUP and the deprecated RADIO) with other gadgets e.g. toggles, texts, buttons, options to allow qualification of the selected option. The Customisation User Guide and Reference Manual warn repeatedly that overlaying gadgets is bad practice and unpredictable, but it is not possible to include other gadgets within an existing radio group gadget. We have extended the Frame gadget to have a radio group


www.cadfamily.com

Customisation


property, and introduced a new radio button gadget, the Rtoggle, which can only be added to Frames. The totality of radio buttons defined within the Frame will act as a radio group. Any other gadgets can be added to the Frame in the normal way.

6.3.5 List gadget enhancements

Multi-selection list – new Start_Batch and Stop_Batch events Multi-selection lists may now generate a batch of events. The meta-events START and STOP are now raised to bracket the set of UNSELECT and the set of SELECT meta-events. Any programmatic modification to the list’s content or selections should only be made at the STOP batch event.

New ADD methods for List and Selector gadgets The methods ADD have been added to allow a single new entry to be appended to the current set.

6.3.6 Option gadget enhancements

Scrolling of text within display field Option gadgets The current value for a textual option gadget, shown within the display field, can now be scrolled so that all of it can be seen. This enables users to specify a gadget display width smaller than the drop-down list string lengths.

New ADD methods for the Option gadget The methods ADD have been added to allow a single new entry to be appended to the Option gadget’s drop-down list.

6.3.7 Miscellaneous

New FMSYS method to load/get a Form by name Allows force loading of form definition and/or the ability to get a form object from its name.

New Modified event for Text gadgets The Text gadget now supports a MODIFIED event (action string).


www.cadfamily.com

Customisation


Control of RGROUP radio-button active status The methods setActive have been added to allow control of the active (greyed-in) status of individual radio buttons of the RGROUP gadget.

Query background colour name using the .Background() method. Most gadgets now support this method.

‘SHOWN’ event for tabbed forms For frames which are tabbed pages within a Tabset frame, F&M now generates a ‘SHOWN’ event whenever the user interactively selects a new tab. The event is only fired for tabbed page frames which have a PMLOpen callback defined. This is so that we don’t upset the current use of the frame as Rgroup SELECT event, which can be applicable to tabbed pages but can be handled via a simple (non-Open) callback. If you want to manage tabbed pages which also contain RToggles, then you must supply an open callback so that you can differentiate the SELECT (rtoggle) event and the (page) SHOWN event.

6.4 Internationalisation

Several improvements have been carried out to improve the availability of local language support in PDMS. Further work is planned for future releases, when the whole handling of local languages is due to be updated in line with Windows standards including Unicode UTF8 character handling throughout. At this stage, the languages supported are as PDMS 11.5: details are given in the Installation guide. However, the new .NET GUI does work in a slightly different manner, so some of the recommendations are now more important. Use of local languages is supported for use in PDMS names and text, but not for PDMS word attributes – this affects things such as SKEY, PKEY, COCO etc. – or for username or password. They are not recommended for use in filenames: if used, macros are more likely to work if run using this syntax: $M ‘<filename>’

rather than: $M /<filename>

6.5 Localisation

Many of the PDMS user interface gadgets are now defined using Microsoft’s .NET, so they may be handled by some of the new tools.


www.cadfamily.com

Customisation


Localisation deals with customizing data and resources for a specific culture or locale language. All .NET Add-ins (Explorer, Explorer Settings, Reference List, DrawList, and My Data) are localizable in that all text and context menu strings are defined in a binary resource file. This file is called PDMSResources.resources and lives alongside PDMSResources.dll i.e. the %PDMSEXE% directory. It is created from the xml file PDMSResources.resx using the .Net utility RESGEN. PDMSResources.resources is the default resource name. This is the resource file that the .NET runtime will look for when running PDMS - if there are no language-specific resource files available. If there is a resource file that matches the current culture then PDMS will use this. In order to customise the Add-ins the user can either modify the default resource or create a resource file for the intended culture. For example, to create a resource file for UK English culture (culture Name: en-GB) copy the default resource file PDMSResources.resx to PDMSResources.en-GB.resx and modify the copied file.


www.cadfamily.com


7 Summary of non-upwards compatible PML changes

Great effort has been made to maintain upwards compatibility between the current and previous versions, while introducing major changes. The following are known potentially non-upwards compatible changes.

7.1 Functional changes at 11.6

The button gadget method !button.val returns type Boolean rather than type String. Note this is in line with the documented behaviour, but is a change from the previous actual behaviour. A menu can no longer be referenced from several different places in the Main menu system, i.e. the menu bar hierarchy of a form. If users have made use of this, they will need to duplicate the shared menus. This should be restricted to the form definition and is essentially a cut and paste job. An attempt to reference a menu more than once will cause an error alert to be raised. The restriction on the Shortcut menu system is that a given menu can be called from different shortcut trees, but cannot be used more than once in a single shortcut tree. Infringing this will cause an error alert to be raised. A menu cannot now be used both as a Shortcut menu and as a Main menu. If users have made use of this, they will need to duplicate the shared menus. Infringing this will cause an error alert to be raised. Remember the recommendation to set the menu usage mode of all shortcut menus to ‘POPUP’. We have removed the unpublished menu and menu bar Marker field facility. The Marker is an invisible field which acts as a reference point for the Clear methods of Bar and Menu. If this facility has been used then it should be replaced by use of the named menu fields and the Menu and Bar editing enhancements. The ability to assign a user defined Shortcut menu to the TEXT gadget has been withdrawn, because it clashes with the default ‘Edit’ shortcut which allows standard cut, copy and paste actions on the text field.


www.cadfamily.com

Incompatible PML changes


7.2 Layout changes at 11.6

The spacing between radio buttons within the RGROUP gadget must now be set explicitly rather than being derived from the VDIST and HDIST setting in operation at the point of definition. We have switched to using variably spaced fonts to improve the overall appearance of the user interface. This has produced various layout changes, because the form co-ordinate grid size is determined by the ‘nominal’ character size for the font. The actual size of a given character is rarely equal to this nominal size. Most lower case characters are smaller than the nominal size (a, e, i, o, u, j, l, p etc.) whilst a few lower case characters, numerics and upper case characters are often bigger than the nominal size (m, W, M, K, 2, 3 etc.). In particular the space character may well be relatively small. These relationships also differ for different font families. Thus, for a string of, say, 10 characters, the actual display length is generally shorter than 10 grid spaces, but may be longer if most of the character are Big (i.e. larger than the font nominal size). This has a number of repercussions: 1. The 'Width' specification for a gadget is the number of grid units

assigned to the gadget, not the number of characters that it can hold. Often the gadget will be able to accommodate more characters than ‘width’, but if the characters are all Big then it will accommodate fewer than ‘width’. Some adjustment may be needed to existing Appware to reflect this change.

2. A similar situation exists for gadget Tag text. The space assigned for the tag text is determined as (number of tag characters multiplied by the grid unit size), not by the actual size of the tag string. This supports the use of padding tags with trailing spaces to achieve left alignment of a column of gadgets, i.e. all the gadgets to be aligned should be given tags with the same number of characters in their tag texts. For existing Appware, there may be a few cases where gadget tags have a high proportion of Big characters, and additional trailing spaces will need to be added to prevent tht displayed tag being truncated or wrapping round.

3. A similar situation exists for paragraph gadgets whose width is set by the ‘Text’ keyword, e.g. para .p1 Text|WAM|. In this example it is probable that an extra trailing space will need to be added to the string to prevent truncation.

4. The form title no longer contributes to the extent of the form, so forms with long titles may now be shorter.

5. The menu bar size calculation is factored down because menu fields tend to have few upper case and numeric characters. The menu bar contributes to the form extent, so forms with long menu bars may now be shorter. For dialog forms with a menu bar only and no gadgets, it is recommended to declare the form ‘Resizable’ if possible, or to pre-


www.cadfamily.com



specify its minimum size to ensure that all the menu bar fields actually appear.

7.3 Functional changes *sp1*

7.3.1 Multi-selection list – Extra Start and Stop meta-events.

At PDMS11.6 we introduced support for Extended Selection Mode for multi-selection lists, whereby CTRL and SHFT keys can qualify the list selection. As a result a whole set of UNSELECT events followed by a whole set of SELECT events can result from a single (atomic) user action. These events are presented in sequence, but Appware cannot tell where the sequence starts or ends. At PDMS11.6, problems may arise if a multi-selection list is programmatically changed during the list callback. Modifying the list content or its selection during the sequence can cause unexpected results or even software crashes. At PDMS11.6Sp1 we nave introduced new START and STOP batch actions to bracket the sequence of UNSELECT and SELECT event actions. For maximum upwards compatibility, the START and STOP batch actions are only notified to PML if the user has assigned an open callback, since this is the only way that different event types (actions) can be differentiated. Please see the PDMS Software Customisation manuals for more information. Appware which used simple callbacks and worked at PDMS11.6 will continue to work because START and STOP events will not be notified to it. Appware which used open callbacks and worked at PDMS11.6 will continue to work if the SELECT and UNSELECT meta-events were explicitly differentiated in the callback, as shown below, because the new START and STOP events will be ignored.

Define method .listSelectionChanged( !list is GADGET, !action is STRING ) . . . if( !action eq ‘SELECT’ ) then . . . elseif( !action eq ‘UNSELECT’ then . . . endif . . . endmethod


www.cadfamily.com



If you experience a change in behaviour, then you may need to rewrite your callback to explicitly handle the new START and STOP events and modify the list content or its selection only on receiving the STOP event action. For newly written Appware we strongly advise the use of open callbacks to service multi-selection list gadgets!

7.4 Layout changes *sp1*

The following changes may well not be apparent for most forms which have been defined by relative gadget placement (as recommended) The start position for an OPTION gadget has moved left by 1 grid unit. The width of an OPTION gadget with unspecified width and content has decreased. The extent of a TEXT gadget with no tag has decreased by 1 grid unit. The extent of an RGROUP gadget set by a long title (rather than by the size of its included buttons) has decreased.


www.cadfamily.com


8 Product Faults and User Requests

8.1 Known faults and Outstanding Issues

8.1.1 Windows fault – correction available

ToolTips may not work properly, on computers with accelerated OpenGL video adapter drivers, after starting PDMS 11.6. This is due to a fault in Windows XP which is corrected in Service Pack 2: see http://support.microsoft.com/?id=814135 and http://support.microsoft.com/default.aspx?kbid=811113.

8.1.2 Windows faults – file locking

There are faults in some versions of Windows related to file locking, which is used for PDMS databases. These typically manifest themselves as ‘MCD errors’ or a PDMS session ‘hanging’. Hotfixes are available from Microsoft for some versions of Windows and they are corrected in the latest service pack of Windows XP. Full details and the latest advice are given on the PDMS support pages on the Internet.

8.1.3 Microsoft .NET Framework Hotfixes KB886903 & KB886904

Microsoft Windows Operating System Hotfixes (patches) KB886903 & KB886904 for the .NET Framework can cause problems with PDMS. These are security updates, so Microsoft recommends installation at the earliest opportunity. For more details, please see: http://support.microsoft.com/default.aspx?scid=kb;en-us;895242. The version of the .NET Framework supplied with PDMS, which was used by AVEVA for testing, is 1.1 for which the hotfix is KB886904. However, users have reported problems with PDMS when this hotfix is applied. PDMS Design and other modules fail to initialise and give a series of errors, starting with: System.InvalidOperationException: Unable to generate a temporary

class (result=1).

The simple solution is to uninstall the patch and reboot, after which PDMS should start normally.


http://support.microsoft.com/?id=814135

http://support.microsoft.com/default.aspx?kbid=811113

http://support.microsoft.com/default.aspx?scid=kb;en-us;895242

www.cadfamily.com

Software Change Requests


An alternative solution, which removes the vulnerability, is to upgrade to .NET Framework 1.1 Service Pack 1 (SP1) and then apply the correct hotfix: KB886903.


www.cadfamily.com



8.1.4 PDMS faults & limitations – corrections planned in future

Unless otherwise indicated, the following faults will be corrected, if possible, by the time of the next service pack.

Reference Description Module Although use of international languages has been

improved for PDMS 11.6 & 11.6.sp1, there are still various issues to be addressed in PDMS 12.

General

(1533) PDMS cannot, in general, handle spaces in file names or directories. This is due to the way in which its commands are processed and cannot easily be resolved, without some incompatibility. Changes are being considered for PDMS 12.

General

(3777) Centreline length output to file is incorrect in Imperial (English) units.

Isodraft

(4366) The extract control form did not handle deleted sites correctly and cannot delete a site if one or more sites are controlled by a DAC.

General

(4509) (4510)

The Equipment application Option list selections are not handled correctly. Planned for PDMS 12.

Design

(4863) Under some circumstances, the General Model Editor handle is incorrectly used in place of the Pipe Component Modification handle. Planned for PDMS 12.

Design

(5087) The use of proportional fonts makes some screen reports difficult to read: they will be changed to use columns.

General

(5285) Member elements are not always correctly moved when a PNODE is moved or rotated. Improvements have been made to positioning but rotation is still not correct. Planned for PDMS 12.

Design

HPD 28284 (6989)

PDMS sometimes runs slowly when using a thin client implementation. This is being investigated but can be improved by placing PMLLIB on each client.

Design (and elsewhere)


www.cadfamily.com



8.2 Faults corrected and minor enhancements

This section briefly describes some of the most significant corrections and improvements since PDMS 11.5 but not necessarily documented elsewhere. Many of these will have been back-ported to earlier releases: where this information was available at the time of writing, this is noted. Please note that this list is not exhaustive: many other minor corrections have been made. Users responsible for raising specific Software Change Requests (SCRs) resulting in changes to PDMS should already have been notified individually. N.B. References in (brackets) are AVEVA internal numbers.

Reference Description First Released

HPD 17392 HPD 17432 HPD 15676

Performance improvements on entering Design. Corrected setting of back references on CRFAs.

Design 11.5.0.1

Full Service pack

See User Bulletin for details: • Updated AISC steel profiles catalogue to

Version 3.01. • Admin MDB Form performance enhancements • DABACON default buffer size increased • Nominal BDIA and BLEN for Bolts and

Hangers • Units option for height input to SPECON • Upwards of 50 minor improvements & fault

corrections

PDMS 11.5.sp1

HPD 14056 A set of gridlines (modelled by SCTNs with null SPREF) was drawn if the only content of a View but could disappear when other Design items were added.

Draft 11.5.sp1

HPD 18376 Selection of a SCTN and then Goto>SPREF from the members form used to navigate using the SPREF NAME rather than the SPREF reference. This caused incorrect navigation in the unusual case of multiple SPREFs with the same name in the MDB – this is now corrected.

Design 11.5.sp1


www.cadfamily.com




HPD 18378 Corrected a spurious error condition when deleting members of a ZONE, when DACS are on, using Delete>Members >All.

Design 11.5.sp1

HPD 21137 (3701)

The numbering of spool drawings that did not start at a GASK or FLAN has been corrected. This could lead to unset BOLTPARTNUMBERS.

Spooler 11.5.SP1.1 Isodraft 11.5.SP1.2

HPD 18208 Ability to add MTOLENGTH on a case by case basis

Design 11.5.sp1.3 Isodraft 11.5.sp1.3

HPD 20676 (3683)

Wireline representation was faint with some graphics cards. This has been resolved by making anti-aliasing (introduced at PDMS 11.5) optional. It is now off by default but can be turned on by setting the environment variable SGL_ANTIALIAS=ON

Design 11.5.sp1.4

HPD 16464 HPD 15743

No longer leaves phantom users in DARS and design

DARs 11.5.sp1.5

HPD 22854 (3883)

Upgrading a project directly from 11.2 did not set the database extract number

Admin 11.5.sp1.6

HPD 21916 HPD 22215 HPD 22899 HPD 22729 HPD 21274 HPD 22017 (3938)

Flanges on the upstream and downstream side of a component with MTOC and MTOT attribute set to DOTU or DOTD are no longer flipped. Flanged tees in the material list with the same code and bores had different entries in the material list but only one part number on the isometric Weld Bores were not shown as Nominal Bores on the weld table when using Imperial Bores. Spooler part numbering now checks LOFF to ensure that OLETs do not split implied tube into 2 parts.

Spooler 11.5.SP1.7 Isodraft 11.5.SP1.7 Isodraw 11.5.SP1.7

HPD 22534 When the "MTOC" attribute is set to DOTD on flanges, the bolt item was still created in "COMPIPE”" export file, even though it was not shown on the isometric drawing

Isodraw 11.5.SP1.8


www.cadfamily.com




HPD 23077

Corrected wrong dimension (OLET – TEE) if a Text ATTA and a WELD have the same position and an OLET is the previous fitting.

Isodraw 11.5.SP1.9

HPD 23143 (4011)

Panels & Plates application amended to create a single penetration for a section through a panel correctly.

Design 11.5.SP1.10

HPD 18109 HPD 23699

Corrected fault in restoring display from binary dump files. Enhanced drawlist query (for MDS).

Design 11.5.SP1.11

HPD 23868 HPD 21581 HPD 23772 (4190) HPD 23891

Tapered SCTNs with SPREF containing SREC geometry were drawn prematurely shortened if the tapering was more than around half the original size. Desclash now correctly records long names for its clash reports. Corrected Desclash failure with a very large obstruction ( >20M in X, Y, Z axis)

Design 11.5.SP1.12

HPD 24237 HPD 23756 (4249) HPD 24305 (4353)

Partnumber now 0 for bend with SKEY TB*D Bolts now correctly reported at out of spec valve to nozzle (no gasket) connection Corrected transformation applied to the graphics of OLAY elements when these were defined by external plotfile - potentially affected DXF & DGN file export from DRAFT. Pseudo attribute DACMOD did not work when used within a collection

Design 11.5.SP1.13 Draft 11.5.SP1.13 Isodraft 11.5.SP1.13

HPD 24095 HPD 24526 HPD 23649

Corrected operation of extracts: it previously caused a DICE check to give the message: “Element n has an inconsistent entry in the name table. Name exists in the table but a different name exists on the element.” This was caused by renaming an element in an extract, creating another element with the original name and then flushing or issuing the renamed element. Global Extract Flush/Issue/Release used to lead to inconsistent errors due to only part of a command being executed when the local daemon was not

Design 11.5.SP1.14 Draft 11.5.SP1.14 Admin 11.5.SP1.14


www.cadfamily.com




running. PDMS did the child extract action, but the parent extract action was lost. Following Flush/Issue commands failed with a 613; Releases had inconsistent claimlists resulting in error messages: ”Element n needs clearing from extract from claimlist in parent extract.” ”Element n needs to be marked in parent extract, as being claimed to this extract in parent extract” ”Element n is claimed to extract n, not a child” ”The child part of the extract is now undone if the local daemon is not running. The command will have to be resubmitted once the daemon is back up.”

HPD 24817

DICE reported a corruption where an element was not registered in its owners member list: Element =n/n is not in the member's list of its owner =n/n For example, this sequence: In Master Create /PIPE1 Create /BRAN In Extract Create /PIPE2 Move /BRAN to /PIPE2 Flush /BRAN Meant that /BRAN was not in the member list of /PIPE2. DICE can now patch this fault.

Design 11.5.SP1.15 Draft 11.5.SP1.15 Admin 11.5.SP1.15

HPD 20482 HPD 22731 (3834) HPD 24054 HPD 25141 HPD 23330 HPD 24636 (4709)

Axes and element name (Query>AXES option) are now correctly displayed on the graphical view, even when clipping is turned on. Print view distorts the view on the printer Updating or checking numbering of a SPLDRG results in termination with DB error 41

Design 11.5.SP1.16

HPD 23773 Amended relative movement form when used Design


www.cadfamily.com




HPD 25939 (4756) HPD 25723 HPD 25083 HPD 25860 HPD 25563

WRT element itself. Position Explicit (AT) with LOAP gave the following incorrect error message: (2,211) Attribute ORI cannot be evaluated for LOAPOINT /1210-10-1/ANCHOR - max.level of nesting exceeded' Q P1 BOLT TOTAL did not work with one branch with a flange connected to PTAIL and a second branch connected to the first. The second branch had a gasket and flange connected to PHEAD. Choose form did not output HEIGHT values with the correct units Selection of Tee with ARRIVE 3(!) and LEAVE 1 or 2 sometimes incorrectly gave error message: (61,164) SPEC does not contain elements matching given criteria.

11.5.SP1.17 Isodraft 11.5.SP1.17

(3123) Database 'Marks' are now cleared by GETWORK 11.6.sp2 HPD 22229 HPD 26241

Global Extract ranges could not be applied using the GUI. Corrected Expunge User Process form: the date was incorrect for most of the entries.

Admin 11.6

HPD 15174 HPD 20154 HPD 22250 HPD 24115 (4153) HPD 26286

Corrected occasional WIGWAM Primitive Group overflow (error 21) typically on company logos composed of 1000s of STRAs. (SKE ORIG ALL IN gid or SKE POIN ALL IN gid). RENAME text gadget on COPY form now works correctly with or without the / preceding the name. #PROJ^DESC corrected for Global projects. DATE field now correct when creating e a DRWG from a TEMPLATE. Code words such a #P^POS & #PK^POSS did not work for TEXPs of VNOTs. Customer specific set-up file for configured DXF-output did not correctly set up DRAFT Utilities > DXFout > Configured.

Draft 11.6


www.cadfamily.com




HPD 11795 (3277) HPD 14470 HPD 18365 HPD 19125 HPD 22572 (4013) HPD 23149 HPD 24304 HPD 24504 HPD 25367 HPD 25368 HPD 26863

The Export of some panels to Review was incorrect, so they appeared black. This was due to an incorrect calculation of the normal to the end surface of extrusions, which now always point outwards. List Gadgets now correctly grey out when inactive. Q MTBE or Q BRCOG used to crash with DABACON 18 error when the CE was implied tube of hanger. 3DView.shaded boolean now returns correct value Copy with Offset form failed to display if it had been used to refer to a deleted element: it now defaults to /*. Error fixed that caused syntax error when modifying the position line or joint line of a joint (MODIFY>JOINTS>POSITION LINE). Macro error corrected for Modify>Joints>Joint Like. Corrected macro error for Modify Sections Merge and then selecting “Sections in List”. Trying to modify the position line of a fitting on a section gave syntax errors in line 119 of Macro %PDMSUI%/DES/CLIB/GPLINE Tidy Gtypes macro on SCTN’s with template fittings gave errors: (2,752) Array element 7 does not exist In line 49 of Macro %PDMSUI%/DES/STLWRK/MSETGTYPE A steelwork joint with an associated plotfile but no editable properties now correctly displays the plot.

Design 11.6

HPD 18490 HPD 24072 HPD 25430

Error removing weld symbol from FLANGE when P-point 2 PSKEY set to PLAIN. Incorrect continuation nozzles no longer drawn when using FTUBS ISODRAFT now handles explicitly set BTHK

Isodraft 11.6


www.cadfamily.com




(5508) HPD 26118 HPD 26213 HPD 26562

values of BLTPs of BTSE for wafer components. Using universal keys caused a splash fatal error in certain cases. Redefinition of Spec Break ATEXT caused information to be missed off drawing. See Remedy call for details. Isometrics with no material list had incorrect spool numbers with Spool Number PREFIX ‘*K’

HPD 15643 (2985)

EXTRACT CLAIM LATEST gets the latest claimlist for all writable DBs. This entails going through a share lock on each DB. For large projects this can be time-consuming so the syntax has been extended to allow: ‘EXTRACT CLAIM LATEST DB <dbname>/ALL’ and allow specific db to be given. In ADMIN it is no longer permitted to say just ‘EXTRACT CLAIM LATEST’ – specifying a db is compulsory. Elsewhere it is optional.

General

HPD 14636 (3399)

Improved performance when merging large number of sessions.

General

HPD 18268 (3402)

OUTPUT now correctly adds quotes when an STEX string begins with ‘(’ .

Paragon

(3413) Increased the max insulation thickness from 150 to 300mm.

Design

HPD 18402 (3420)

Now handles a user doing PARTNO CREATE CE when another user has just created the spool drawing & still has it claimed.

Spooler

HPD 18641 (3431)

The following pseudo attributes may not be used in catalogue expressions: ATLE, LTLE, AGRD, LGRD, FITLEN, MTLE, STLE, STAP & MTCL. Use of ATLE previously caused a crash in Design when the item using such a ppoint was drawn.

Design

HPD 18874 (3464)

CONN PH to P4 of /PAD4 now correctly sets CRFA of /PAD4 if initially unset.

Design


www.cadfamily.com




(3520) Element with duplicated names in two extracts of the same database caused problems on flushing back to the parent database.

Design 11.6

HPD 18959 (3529)

Data listings are now always output in ‘forwards’ mode: previously numbering could get confused.

Design

HPD 14758 HPD 16772 (3541)

Resolved a problem with Report formatting with subtotalling. If a value results from several values being subtotalled, then it no longer appears on a new line in the report.

Design

HPD 20176 (3628)

Modify>Sub Equipment Origin>ID Point now clears the SUBE name is after the user accepts the location of new origin point.

Design

HPD 20222 (3648)

Text strings in DXF output are no longer limited to 128 chars, as expanded text from DRAFT can be up to 180 chars.

Draft

HPD 20167 (3651)

UDAs with non alpha names now work in PML2 expressions, e.g. !XX = !!CE.:UDA-LIST

General

HPD 19946 (3653)

The ACBORE on a CMPD is no longer treated as a nominal bore, so when set to 38.14 it is not changed to 40!

Propcon

HPD 20364 (3660)

Query !!ce.inth now returns ZERO (0) were insulation is unset for a component.

Design

HPD 20798 (3682)

Q BRWEI no longer crashes if the CE is a pipe which owns restraints.

Design

HPD 20968 (3699)

!X = !!CE.PTCDIR now works correctly. General

HPD 21379 (3724)

RESELECT now works for tees & reducers Design

HPD 21328 (3809)

Data output command no uses a greater precision (1/8192”) with FINCH DIST.

Design

HPD 22751 (3837)

PDMS no longer crashes when the Explorer “ADD CONNECTED” option is used with the connected branch deleted.

Design

HPD 23033 Several improvements have been made to the Design


www.cadfamily.com




HPD 23039 (4008) (4009)

behaviour when creating and modifying ring GENSECS, using the Create Ring and Modify Section (Ring) forms.

HPD 23041 (4010)

Deletion of CURVE element of SPINE using Modify Section (Curve) form produces error message and does not complete deletion. If a CURVE element is deleted using the Delete button on the Modify Section (Curved) form an error message is displayed, see attachment, and the deletion is not carried out.

Design

HPD 22577 (4012)

If you set the frame of reference to the SCTN that you are trying to move, the resulting position is no longer incorrect (by a long way!)

Design

(4033) A number of improvements have been made to SP1 to ensure that a list, option gadget and textbox with the same width specified in the form definition now have the same overall width. Many other improvements have been made to forms & menus layout, visibility etc.

General

(4062) With 2D views, the ‘arrow’ keys seem to be locked to the horizontal scroll bars and do not work properly.

GUI

HPD 23467 (4084)

Lists/Collections form, using Add>Selection… ALL types no longer outputs a syntax error.

General

HPD 23523 (4106)

Dice can now patch the case where elements have been lost from the member list of their owners.

Admin

HPD 23609 (4117)

Error D800 is now included in the Design Ref pt 4 manual.

Design

(4186) Dice now outputs highest session number. Dice 11.6 HPD 23891 (4206)

Clashes are no longer missed when a very large object is checked against a small obstruction item.

Design

(4300) Dice no longer crashes on corrupt database Dice 11.6 HPD 24095 HPD 24526 (4408/4410)

Out of sync name tables (possibly caused by a bug in extract flush) are now patched by Dice.

Admin 11.6 11.5.sp1


www.cadfamily.com




(4430) (4433)

Problem opening these other Databases will no longer cause DICE to fall over. MODE FULL and MAXERROR of 0 are now the default settings on entry to Admin.

Admin 11.6

HPD 24237 (4346)

There is now no Partnumber for bend with SKEY TB*D

Design

(4474) Correct precision now displayed in GUI for imperial units.

Draft

HPD 24998 (4543)

Options>Modify form: Select Component Tags… now includes FILT.

Isodraft

(4568) The ‘Head’ and ‘Tail’ type markers do not resize during an ‘align with feature’ operation when the view is zoomed in.

Design

(4471) The View manipulation for the Draft 3D View window has been improved for SP1.

Draft

HPD 19944 HPD 18705 HPD 24431 (4757)

Amended unwanted clipping when rotating the view around an element.

Design

HPD 24648 (4760)

When adding Routing Planes as a constraint to a branch, the form in Design now shows all the RPLA’s in the MDB, not just the current database.

Router

HPD 24557 HPD 24531 (4761)

Global Stand alone Project creation using the upgrade option adds unnecessary lines in inmacro that creates a loss of catalogue references: the last section must be removed for it to work correctly.

Admin

HPD 25281 (4783)

Modification of ACR GROUPS using the application has been amended.

Admin

HPD 25293 (4804)

MicroStation (.DGN) files have been corrected to enable DGN file export.

Draft

HPD 22623 (4819)

The case of an unset filename for File on the DATACON form is now handled better.

Design

HPD 25357 (4874)

Corrected an error causing some primitives of a catalog component to be omitted from the display.

Design


www.cadfamily.com




(SGL errors were also output)

HPD 24880 (4908)

The Utilities>Pipe penetration application no longer leaves the aid axes behind.

Design

HPD 20192 (4918)

The Create Extrusion form no longer creates two slashes (//).

Design

HPD 25539 (4919)

The Nozzle Specification (FNOZZPEC) form has been amended.

Design

(4926) Corrected a problem on entry to PDMS with Korean mdb name.

Monitor 11.6

(4933) Query>Project>DBs now gives correct details for those with Korean names.

Admin

(4980) Resolved a problem merging Extract Databases containing sessions that point to a base session in the owner. Previously an error meant that running Dice on the Child Extract gave a Bad Block FATAL error, with the rest of the database not being checked.

Admin 11.6

HPD 25083 (4994)

Error in bolt querying corrected. Q P1 BOLT TOTAL did not always work correctly with branches connected together.

Design

(5015) UNDO now works more reliably with the model editor handle position.

Design

(5016) Corrected an error with Project form for project descriptions containing Korean characters.

Admin

HPD 25602 (5020)

An error causing memory to ‘leak’ in PML (TCTL) has been corrected.

Design

(5035) The Reselect command is now available outside the model editor from SP1.

Design

(5154) With a sheet consisting of more than one view, the preview for offset section planes is not clear.

Draft

HPD 25723 (5208)

Position>Explicit (At) Form corrected when used with loadpoint LOAP. The following error message used to appear: (2,211) Attribute ORI cannot be evaluated for


www.cadfamily.com




LOAPOINT /1210-10-1/ANCHOR – max.level of nesting exceeded.

(5212) An AREADE element containing an ABOX does not correctly copy – it fails to copy the ABOX and gives a misleading error message.

Design

HPD 25563 (5228)

Resolved a problem with selection with a TEE with ARRIVE 3(!) and LEAVE 1 or 2, using the syntax: !Select = SELECT LSTUBE WITH SHOP TRUE

(5284) A docking form that is undocked will not show ToolTips on pixmap buttons.

GUI

(5370) Can now save the Define Purpose file using the SaveAs option.

Design

HPD 26241 (5382)

Correct dates now shown on the Expunge User Process form.

Admin

HPD 22229 (5384)

When setting the Global Extract range for an uninitialised location, the user is asked if he wants to initialise the location. A ‘No’ answer is now handled correctly.

(Global) Admin

(5387) The list gadget allows data as strings to be added as columns separated by a TAB character. The expression object used for columns, tables and report objects at SP1 allows the tab character to be used so that the data can be added directly to a list from a table/report.

General

(5427) (5428)

Some PDMS blocking forms prevent the user from accessing other applications, including MS Office etc.

General

(5459) If the ADMIN/PADD DB is deferred when the user tries to display the 3D View window, Draft would crash with Dabacon 41 error. This is handled properly in SP1.

Draft

(5550) The ‘+’ and ‘-‘ keys have been implemented in SP1 such that ‘+’ increases the offset or clearance from the plane defined by the feature, ‘-‘ decreases this value.

Design


www.cadfamily.com




(5555) An error when producing Check ISO’s of unnamed spool elements has been corrected.

Design

(5559) Correction of an error causing the message “(2,751) Variable !!REALFMT does not exist” when querying attributes.

General

(5613) Certain changes are treated incorrectly during reconfiguration of extracts

Admin

(5625) Direction of movement of a component at the tail of the branch using the GUI has been corrected.

Design

(5698) Resolved a problem when flushing any element would result in a Dabacon 534 error.

General

HPD26626 (5704)

The default value DPRO is now used to evaluate a text property. It is used for the real equivalent RPROP.

Design

HPD 27087 (5716)

A correction has been made to avoid an incorrect message: (99,532) Undefined UDA name when using long uda names.

(5719) Form now tracks the problem item on the Data Consistency Form.

Design

HPD 27082 (5726)

Correction to allow concatenation of a method to a UDA value.

General

(3287) DICE now increments the session when it patches a database, thus ensuring that Global correctly recognises and distributes any necessary changes, including claim lists.

Dice 11.6.0

(5791) Invalid entries in name tables (i.e. invalid references) are now corrected if possible.

Dice

(5793) A partial flush will now ignore any invalid table attributes and carry on.

General


www.cadfamily.com



8.3 Faults corrected and minor enhancements *sp1*

Please note that this list is not complete: many corrections were made to faults discovered during internal testing and early evaluation. Some of these may also have been back-ported to earlier releases.

Reference Description Module HPD 23235 (4130)

The axis is no longer left the object being created/modified after leaving the HVAC application.

Design 11.6.sp1

HPD 25543 (5051)

Export does not export leave rod from hangers. Design 11.6.sp1

HPD 26315 (5406) HPD 26936 (5680)

Wigwam overflow crashes with a very large number of EXTRUsions or error messages, e.g. Error 21s (Primitive Group too long) from GOPPLN, when drawing large models created using ImPLANT. Existing checks need to be extended. Splitting or simplifying the model will usually help.

Draft 11.6.sp1

HPD 26447 (5477)

Connect button is no longer greyed out to prevent connection of ph to first mem after it was connected to a PT.

Design 11.6.sp1

HPD 26802 (5625)

Creation of a component starting from the tail of the branch with a spool between the TAIL and the component now goes in the correct direction.

Design 11.6.sp1

HPD 26863 (5634)

A steelwork joint with an associated plotfile but no editable properties will no longer have the plotfile button greyed out on the Joint Spec form.

Design 11.6.sp1

HPD 22396 (5725)

Corrected a possible SPLASH crash for GLAB (& probably SLAB) with invalid DDNM when repositioning using command AT @.

Draft 11.6.sp1

HPD 27043 (5732)

Text evaluation of a selection now adds brackets around a VTEXT variable.

General 11.6.sp1

HPD 19575 (5754)

Modify>Component>Connection Ref. now works correctly for a CROS.

Design 11.6.sp1

HPD 23235 The axis is no longer left at the object being Design


www.cadfamily.com



Reference Description Module (4130) created or modified after leaving the HVAC

application 11.6.sp1

HPD 19243 (5756)

Access control methods are now properly invoked before creating a ADDE/REME element, ensuring that the ADD command does not create a new ADDE under an IDLI when it is not claimed.

Draft 11.6.sp1

HPD 27197 (5747)

Component selection form no longer shows an error if component is in LIMBOSPEC

Design 11.6.sp1

HPD 19602 (5752)

Settings>Storage Areas option Create>Level brings up the buildings level form: this now works better if the Apply button is used without giving a name.

Design 11.6.sp1

HPD 19630 (5763)

A PML error caused by deletion of the PLOO element of a rectangular panel has been corrected.

Design 11.6.sp1

HPD 27430 (5775)

Resolved problem of losing the temporary graphics after popping up the modify labels menu if the cursor is off the graphics window.

Draft 11.6.sp1

HPD 26914 HPD 27671 (5780)

Corrected quantity for bolt material if there are more than 100 bolts in one flanged connection.

Isodraft 11.6.sp1

HPD 27469 (5800)

Corrected a calculator error when using Delete range of piping components button in imperial units.

Design 11.6.sp1

HPD 27468 (5801)

A correction has been made for mixed pipe bore handling when using Quick Pipe Router.

Design 11.6.sp1

HPD 27553) (5764/5809)

Datal output for "BACK" now correctly outputs certain ‘cascaded’ attributes such as SIZE, XYPS if they are set.

Draft 11.6.sp1

HPD 27472 (5811) HPD 27766 (6697)

Improved equality check for two PML variables of data type BORE. This means that components will be correctly matched.

General 11.6.sp1

HPD 27191 (5817)

Member .detail of AVEVA object GPHPOSITION corrected to work with Imperial FINCH units.

Design 11.6.sp1

HPD 27893 Plotfiles in tabbed frames no longer make PDMS Design


www.cadfamily.com



(6707) crash or hang. 11.6.sp1 HPD 27884 (6708)

It is no longer necessary to set dock or anchor for tabbed frames to create a scrollbar, as they are now treated as Dock Fill.

Design 11.6.sp1

HPD 27883 (6709)

It is now possible to give tabbed frames tags after they have been created.

Design 11.6.sp1

HPD 27882 (6710)

It is now possible to make tabbed frames invisible.

Design 11.6.sp1

HPD 27946 (6729)

Branch weight of first tubi now gives correct weight.

Design 11.6.sp1

HPD 27956 (6734)

comPropData.pmlobj corrected for nozzles Design 11.6.sp1

HPD 27987 (4422) (6741)

Unhandled Exception error message is no longer when Auto-hide option is used on the Command Line.

Monitor, Admin

HPD 27623 (6763)

PDMS will no longer crash when checking pipe with missing references on hangers.

Design 11.6.sp1

HPD 16869 (6774)

Correction for tube weights in material list. Isodraft 11.6.sp1

HPD 28142 (6786)

If PML discovers an incomplete DO loop on an ENDMETHOD, it now issues an error message as well as tidying up.

General 11.6.sp1

HPD 28030 (6829)

Picking of REST/HANG elements now works correctly when representation for insulation is set to translucent.

Design 11.6.sp1

HPD 28292 (6834)

Corrected a problem closing sheet, after a deletion. This led to an error messages (2,109) Undefined name and afterwards (47,15) CP: Syntax error for any activity.

Draft 11.6.sp1

HPD 28331 (6840)

Components created using the new component creation form will no longer always have the SHOP set to FALSE, regardless of the spec.

Design 11.6.sp1

HPD 28434 (6875)

Improved visibility of Zoom box on plot view. Isodraft 11.6.sp1

HPD 28280 Setting obstruction to anything but OFF no Design


www.cadfamily.com



(6879) longer makes all the steel section disappear. 11.6.sp1 HPD 28394 (6886)

Correction to allow the steelwork joints on the MTO.

Draft 11.6.sp1

HPD 28478 (6893)

Corrected an error when LOCKing the WORLD! No longer gives a Runtime error with the error message 'Unhandled Database Error 10 from DGOTO, invalid external reference'

Draft 11.6.sp1

HPD 28515 (6906)

Moving a branch no longer navigates to a different element.

Design 11.6.sp1

HPD 28528 (6923)

PRESSURE and TEMP are not showing on the iso properly; they are being converted with the UNIT (showing as FEET and INCHES).

Isodraft 11.6.sp1

HPD 28407 (3525/6924)

Improved the speed of GETWORK in Draft. Draft 11.6.sp1

HPD 28587 (6925)

Resolved text problems with Cyrillic fonts in DXF output.

Draft 11.6.sp1

HPD 23469 (6972)

Corrected an error in the description for 1" 90deg elbows.

11.6.sp1

HPD 23470 (6973)

Corrected various problems with Spec Breaks: 1. At some breaks no break marker boxes were shown. 2. Only one marker box was shown at CONT.ON (REC -30). 3. Marker for a single spec instrument was missed out. 4. In some cases, the lines for the positioning were too long.

Isodraft 11.6.sp1

HPD 28468 (6990)

Corrected a problem with the component mouse pointer when using modify mode to rotate or move a piping component.

Design 11.6.sp1

HPD 28583 (6993)

The case where a JOIS or JOIE attribute on a SCTN element was an invalid ref (as correctly noted by DICE) was not being handled by CHECK (Datacon). This situation is now trapped, and an error 'Structural Geometry Error - JOIS (/JOIE) reference invalid' will be produced.

Design 11.6.sp1

HPD 28470 (6996)

Modify Mode now correctly moves the Pipe Head or Pipe Tail, when there is a connection across a

Design 11.6.sp1


www.cadfamily.com



pair of flanges. HPD 28762 (7162)

Itemcode from UDA now works correctly when the number of UDAs exceeds 30.

Isodraft 11.6.sp1

HPD 28912 (7173)

Utilities > Export > Dump Attributes utility now works correctly when is a BRAN component that has an unset or bad SPREF.

Design 11.6.sp1

HPD 28933 (7298)

Creating Corner Posts with the ASL Modeller application now locates the corner posts correctly with an imperial project.

Design 11.6.sp1

HPD 28965 (7398)

Can now modify floor fittings. Design 11.6.sp1

HPD 27131 (7520)

Module switch will no longer crash when there is an instance of user defined object with member(s) of type EXPRESSION. PML will now not attempt to save any objects which have any C++ members, such as the Expression object. This is because any such PML object is not saved over a module switch.

General 11.6.sp1

HPD 28477 (7539)

Q BREARE now gives the correct result for a TUBI after a REDU.

Design 11.6.sp1

HPD 28477 (7661)

Highlighted elements are no longer displayed wrongly. Formerly, if you identified a portion of tube in the graphical view and then moved to another item in the view, the portion of line that you have identified previously would change to dotted (in wireline) like there is an error on that portion of pipe.

Design 11.6.sp1


www.cadfamily.com




This lists the most important corrections in Service Pack 2, at the time of writing (October 2005).

Reference Description Module HPD 16305 (2879) HPD 29325 (7908) HPD 29632 (7929)

Dice sometimes incorrectly showed errors in large Dabacon tables.

Dice 11.6.sp2

(3418) Pline Definition window now correctly displayed on selecting Modify mode, deleting the created Pline and then re-calling the form in Create mode.

Paragon 11.6.sp2

HPD 23332 (4127)

A POHEDRON of zero thickness now Exports to Review correctly.

Design 11.6.sp2

(4495/8458/8229)

Dice now correctly handles errors in tables due to corrupt data, rather than crashing.

Admin 11.6.sp2

HPD 24925 (4758)

Corrected an error causing report templates to fail thus: WARNING – Data too long for variable. Data truncated. This was due to inconsistent limitations in passing arguments between macros.

Reporting 11.6.sp2 (also fix for 11.5)

(5254) Form layouts improved, e.g. relative offset Design 11.6.sp2

(5377) Exception error when using UNDO and Quick Pipe Router

Design 11.6.sp2

(5457) Relative move form now shown correctly after deleting equipment

Design 11.6.sp2

HPD 30534 (6711/8171)

Many improvements were made to robustness, when used on damaged databases, including: Deletion of a primary element in a master database could lead to errors when modifying it in a variant.

DICE 11.6.sp2


www.cadfamily.com



Reference Description Module HPD 29571 (7999) (6728)

Option to allow a partial flush to work with deleted elements with the same name.

11.6.sp2

HPD 25316 (6757)

SKEYs WLR and WLC have been added for use to show lugs. The default symbol for both is the same as a NIPL OLET, but without the bore data and elevation messages.

Isodraft 11.6.sp2

HPD 25340 (6981)

Limitation in DACs condition setting form corrected.

Admin 11.6.sp2

HPD 27267 (7089)

Modifications to prevent excessive database growth during issuing or flushing.

(Dabacon) 11.6.sp2

HPD 29068 (7431)

Group reference list now allows for element appearing more than once – caused crash

Design 11.6.sp2

HPD 29217 (7589)

Corrected spurious cut length number for elbow upstream welded attachment.

Isodraft 11.6.sp2

(7670) Plines can now be highlighted or selected on Gensecs, as on Sections.

Design 11.6.sp2

(7709) Pipework Pipe Component Selection form now shows Spec correctly after a change.

Design 11.6.sp2

HPD 29394 (7768)

Corrected OLET Item Numbers display in the isometric graphics area, for specific options including user defined columns.

Isodraft 11.6.sp2

HPD 29404 (7769)

New option to suppress continuation notes, giving the number of the sheet, across sheets of a drawing. This command controls only the arrowed continuation message; other aspects of the continuation are unchanged. Examples: CONTS OFF: Continuation notes between sheets are suppressed. CONTSHEET ON: Continuation notes between sheets are switched on.

Isodraft 11.6.sp2

HPD 29415 HPD 29847 (7777/7990)

Corrected Dabacon error 23 or 10 on flushing an extract Database containing differing length UDAs.

11.6.sp2

HPD 29468 (7804)

The customary warning when a licence is due to expire shortly is now working again.

General


http://defectlog.aveva.com/change_SW_defect.asp?Defect+ID=7089

http://defectlog.aveva.com/change_SW_defect.asp?Defect+ID=7089

www.cadfamily.com



Reference Description Module (7807) Pipe and branch names are now displayed

correctly in the Component Creation form Design 11.6.sp2

(7808) Bore text is now displayed correctly in the Component Creation form

Design 11.6.sp2

HPD 29292 (7699) (7813) (7814) (7818) (7828) (7833) (7847)

Bores are now correctly handled for both imperial and metric projects when creating components.

Design 11.6.sp2

HPD 29556 (7877)

Clashes are not detected if implied tube is badly aligned, i.e. is shown dotted in the 3D graphics, as it is not included in the spatial map. Under some circumstances, this could be misleading: for example, if different tolerances are used for drawing and for building the map. Rather than a bad alignment message, new D860 & E860 (for Arrive & Leave tube) error messages are now issued when data checking when the tube is not in the map. These state: TUBE DOES NOT EXIST IN THE SPATIAL MAP, NO CLASH WILL BE DETECTED

Design 11.6.sp2 (also 11.6.sp1.5)

(7888) An error causing an exception when using the 3D view has been corrected. Features were not being rotated with the model, so they appeared in the wrong place, and could not then be associated with the model. Placing the cursor in the 3d window then caused a crash.

Draft 11.6.sp2

(7894) An attempt to rotate a deleted selection will no longer cause an Unhandled Exception error.

Design 11.6.sp2

(7895) Labels now snap to the origin of the label in modify mode with snap to grid turned on.

Draft 11.6.sp2

HPD 29591 (7915)

Resolved Dabacon crash with certain data when querying ‘PQAANG’ – this caused a Runtime Error when Branch Reconnection or Data Check was carried out.

Design 11.6.sp6 (and 11.6.sp1.1)


www.cadfamily.com



Reference Description Module (7917) Use of model editor on HVAC branch no longer

causes a null reference exception error. Design 11.6.sp2

(7918) Resolved occasional exception error, due to operations being attempted on a closed 3D view.

Design 11.6.sp2

(7919) Various uses of the Reference Definition Application form while in Model editor mode caused a run time error. These have been corrected.

Design 11.6.sp2

HPD 29726 HPD 29860 (7939)

Corrected poor form layout when using some Asian languages

Design 11.6.sp2

HPD 29529 (7945)

Improved Equipment Positioning on Panel surfaces.

Design 11.6.sp2

(7951) Resolved a fault causing Dabacon errors such as Unhandled Database error 41 in Extract databases.

11.6.sp2

HPD 29776 (7965)

Resolved ERROR in SPLASH routine HADDIA when detailing an Equipment Trim.

Isodraft 11.6.sp2

HPD 29886 (8017)

SPLASH Error in routine HGETI1 when floating a second Graphics window has been corrected.

Design 11.6.sp2

HPD 29206 (8048)

The PREPROCESS and POSTPROCESS commands have been modified to use the maximum string length of 250 characters before processing, e.g. for embedded quotation marks.

Isodraft 11.6.sp2

(8052) Corrected spurious message: (160,9) File %PDMSUSER%/frame-coords.txt does not exist. This occurred on the first attempt to list the attributes of an element in the explorer.

Design 11.6.sp2

HPD 30077 (8147) (8206)

System incorrectly called for Final Designer license feature. This also caused many errors in the log-file when there was no such license.

Draft 11.6.sp2

(8162) Corruption in Name table now prevented when name of element (deleted in variant) is re-used in owning extract.

11.6.sp2

(8183) Dice will now correct reports errors of the form: Next bucket is 6 but bucket 6 found in extract 3.

Dice 11.6.sp2

Comment [PJEB1]: Need to change appware as well


www.cadfamily.com



Reference Description Module (8184) Crash in Dice when doing a check db with patch

on. Dice 11.6.sp2

(8208) Extracts no longer created with wrong team using Admin GUI.

Admin 11.6.sp2

(8221) Resolved a fault causing Dabacon error 41 when doing "extract refresh”.

11.6.sp2

(8228) Entries were being left in the Spatial Map when elements no longer existed: a Dice check reported this problem. Now handled correctly.

11.6.sp2

(8233) In a global project, all changed extract files must be propagated after compaction before databases are used. To ensure this is done, Dabacon now checks and handles this situation by checking the ‘compaction count’.

11.6.sp2

(8246) Co-fitting now correctly applies referenced negative geometry, when splitting a panel.

Design 11.6.sp2

(8306) A SBFI (sub-fitting) can use the ARRIVE attribute to specify a P-point of the owning CMFI (compound fitting) to alter the frame of reference for its geometry and orientation. In this case, the system now correctly uses the design points of a CMFI defined as a TMPL in place of the P-points of one using a catalogue definition.

Design 11.6.sp2

(8308) The EDG measure utility now works correctly when in graphics mode.

Design 11.6.sp2

(8328) In certain circumstances, the Commands form 'Request' panel became 'see-through' – now corrected.

Design 11.6.sp2

(8360) Dice now handles transaction databases better, to avoid misleading error messages due to the databases growing whilst DICE is running its checks.

Admin 11.6.sp2

(8383) Corrected a fault with linear grids, causing a run time error when clicking any point on the dotted line.

Design 11.6.sp2

HPD 29073 HPD 30189

Clicking on a ROD element no longer causes a crash after a message “Unhandled Exception:

Design 11.6.sp2


www.cadfamily.com



Reference Description Module (8376) System.NullReferenceException”. HPD 30284 (8427)

Certain PML forms could cause an error (61,564) “F&M Cursor functions not allowed during Tracking updates” is raised and then a program crash. This did not happen at PDMS 11.5. The error will now be trapped properly. This was caused by a form with Tracking on executing a cursor function from a button and causing the system to become recursive.

Design 11.6.sp2

(8446) Under certain circumstances, claims were being lost, resulting in the following DICE error: ‘Element ATTACHMENT /name needs to be marked in parent extract, as being claimed to this extract in parent extract’

11.6.sp2

(8448) Crash in MyData corrected. It was caused by adding an element to MyData in one session, changing the element’s name in another session, and then savework, getwork in the first session.

11.6.sp2

(8464) Dice no longer hangs, when encountering a particular severe corruption in the sessions of a database.

Admin 11.6.sp2

(8465) Dice now copes better with databases containing lots of 406 errors.

Admin 11.6.sp2

(8476) Switching names on two elements no longer causes corruption if done twice in conjunction with flushwithout.

11.6.sp2

(8479) Dabacon error 41 on deleting an extract – now handled correctly

Admin 11.6.sp2

(8504) Dice now handles extracts missing at the current location differently. Previously, a DICE check on a level 2 extract might give an error 'Unable to search index table in extract 3' because Extract 3 was non-propagating, and therefore not present at the current location. This error is now treated like the 'Lost bucket' error in a global project, which outputs a warning about non-primary databases.

Admin 11.6.sp2


www.cadfamily.com




This lists the most important corrections in Service Pack 3, at the time of writing (April 2006). In some cases, these may also have been made available in fix releases for previous versions of PDMS.

Reference Description Module (3887) The Extract claim hierarchy form has been

improved: among other things, it now indicates when a claim exists at a lower hierarchy.

Design 11.6.sp3

(4658) Corrected display of Bore in Query>attributes form for mm Bore units setting.

Design 11.6.sp3

HPD 24740 (4759) HPD 28023 (7292)

Improved DACs error handling in several places in the GUI by using a new test rather than a dummy move (“BY E 0 mm”). This resolves a problem with the GUI when adding an ATTA to a cable tray which contains a MDS support.

Design 11.6.sp3

(4915) (8939)

Spooler no longer changes the session units. Output dimensions and MTO units in Isometric preview in Spooler are now shown in the current session units.

Spooler 11.6.sp3

HPD 26603 (5591) HPD 30819 (8701)

Query>General has been added back due to popular demand. This enables, for example, the Querying of BOLT info for piping components.

Design 11.6.sp3

(5518) Resolved an Unhandled Exception (Object reference not set to an instance of an object) caused by an UNDO after moving an object using the locator handles and then deleting the 3D View.

Design 11.6.sp3

HPD 27480 (5807)

Data listing of DRWG improved. Problems occurred at a DPOINTS with DTOF. This was corrected treating DPOIs like DPPTs, so that their critical attribute (POS) is not initialised on creation.

Draft 11.6.sp3

HPD 20209 (6772)

A combination of ATTA, Sheet break, ATTA in a particular sequence caused a dimensioning error.

Isodraft 11.6.sp3

HPD 27992 (6850)

Query attributes at a SPEC, SPCO, SELE in Paragon no longer gives an error.

Paragon 11.6.sp3


www.cadfamily.com



HPD 28432 (6874)

Unnecessary rectangle no longer plotted for OLET in certain circumstances.

Isodraft 11.6.sp3

HPD 28541 (7034)

Support (trunnion) dimension on elbow no longer shows cut length rather than distance to elbow’s P0.

Isodraft 11.6.sp3

HPD 77267 (7089)

Achieved a significant reduction in number of database pages written on a ‘Flush with Refresh’. This takes effect only on a such a Flush, when no changes have been made in the parent extract.

General 11.6.sp3 (also 11.5.sp1.45)

HPD 28795 (7141)

Merge Changes did not correctly update pointers between session pages, resulting in subsequent flushing corrupting the Database. The command EXTRACT FLUSH RESET also led to a Product crash. These faults have now been corrected.

Admin 11.6.sp3

HPD 28871 (7199)

The presence in sequence of additional MTO records caused welds attached to a support ATTA to appear incorrectly in the weld report.

Isodraft 11.6.sp3

HPD 16673 (7314)

Resolved problems with the dimensioning of a skew box on a pipe that is modelled in a non-orthogonal direction.

Isodraft 11.6.sp3

HPD 25281 (7268)

Resolved a problem modifying ACR GROUPS.

Admin 11.6.sp3

(7413) The Design Pipework application (Modify Pipe form) had a fault causing the options to be lost and an error “Array element 0 does not exist”. This forced the user to close the form and reopen it. This has been corrected.

Design 11.6.sp3

(7786) HPD 31108 (8812)

Corrected a fault causing Utilities>Send Message for a GLOBAL project to give an error '(61,680) F&M: Cannot access column data for gadget !!ADMMESS.LOCN, it is not multi-column'.

Admin 11.6.sp3

HPD 29892 (8020)

Corrected Iso Dimensions and Error message when using user defined SKEY.

Isodraft 11.6.sp3

HPD 29954 (8047)

Corrected dimensioning in certain circumstances around ATTA.

Isodraft 11.6.sp3

HPD 29964 (8053) HPD 30475 (8532)

Confusing layout of the HVAC modify form corrected.

Design 11.6.sp3


www.cadfamily.com



HPD 30008 (8119)

Corrected dimensioning when using SPECBREAK BRANCH around ATTA.

Isodraft 11.6.sp3

HPD 30026 (8144)

A combination of dotted lines and hangers caused an incorrect dimension.

Isodraft 11.6.sp3

(8154) Corrected an error with Design Explorer –navigating to an element and selecting Query > Attributes

Design 11.6.sp3

(8186) While creating ADP view with limits set to drawlist, an error “illegal values for attribute VSCA” appeared and the view was not generated.

Draft 11.6.sp3

(8214) ATTEXT command now enables the addition of extra text to the material list for tube as well as fittings.

Isodraft 11.6.sp3

HPD 30171 (8320)

The Cutpiece number table did not match the cutpiece numbers on the iso for split drawings. This was becasue the bends had no SKEY set.

Isodraft 11.6.sp3

HPD 30009 (8327)

Field Weld labels were shifted to the next weld. and Cut piece lengths after field welds were wrong, when the welds were followed by a Tee.

Isodraft 11.6.sp3

HPD 30200 (8334), HPD 31094 (8796)

New pipe creation form no longer lists wrong sizes for inch bores.

Design 11.6.sp3

HPD 30195 (8335)

Splash error no longer given when the user selects a menu entry and drags the cursor into the main display.

Design 11.6.sp3

HPD 30231 (8374) HPD 30387 (8508)

PZAXIS (& other axis attributes) may now be reset to ‘unset’.

Paragon 11.6.sp3

HPD 30048 HPD 30254 (8401)

Corrected dimensioning on isometrics with "dime comp on" and Tolerance Offset 2mm :

Isodraft 11.6.sp3

(8402) (8601)

A form handling fault meant that manipulation of a View gadget could cause another gadget to reappear in an inactive state. The system now ensures that a view's form is displayed before allowing refresh of status line label widgets.

Design, Paragon 11.6.sp3

HPD 30094 (8434)

Corrected GUI error in setting MTO length and Quantity of Detail Text.

Paragon 11.6.sp3


www.cadfamily.com



HPD 30037 (8435) HPD 31361 (8931) (8595)

PLINEs are now drawn and the filter works correctly.

Design 11.6.sp2.1

(8494) Corrected a problem causing a memory error to be reported. This was caused by some databases in an extract tree having been compacted, while others hadn't.

DICE 11.6.sp3

(8496) Lug SKEYs – WLR and WLC – are now user definable.

Isodraft 11.6.sp3

HPD 30320 (8515)

AutoDRAFT will now work with AutoCAD 2004, 2005, 2006.

Draft 11.6.sp3

HPD 30350 (8521)

Translucent obstruction now works with holes on. Design 11.6.sp3

HPD 30470 HPD 30393 (8529)

Background Process Manager did not run the jobs for certain users/passwords, for example if the username was only one character. It has been updated and now also copes properly with characters with an ASCII value less than 32.

Draft 11.6.sp3

(8557) (8869)

Reselecting components out of spec in the Design Pipework application, now works correctly.

Design 11.6.sp3

HPD 30349 (8534) (8855)

The 3D display has been corrected to show the ‘teeth’ of the section planes in the correct direction. In the 3D view, the teeth indicate which side of the plane the objects will be kept, and the display changes when the user flips it. The Planes are now shown on the 2D view at the same time as the 3D view. In the 2D view, the shaded area indicates where the plane itself is, and does not change when the user switches between 'in front' and 'behind'.

Draft 11.6.sp3

HPD 30367 (8535)

PDMS no longer shuts down if Windows/Forms for Explorer, Command Window and Drawlist are in one set and moved together.

General 11.6.sp3

HPD 30485 (8538)

Improved display of the alert input form with long text – it no longer gets cut off.

General 11.6.sp3


www.cadfamily.com



(8544) (8572)

Highlighting on ppoints (& plines) for picking, e.g. if you use Q IDP @ when you select the item, was not working, though there was feedback in the prompt space for the ppoint passed over.

Design 11.6.sp3

HPD 30327 (8564)

Output in some Draft Admin forms has been improved so that it no longer shows as an exponential number.

Draft 11.6.sp3

HPD 30649 (8613)

SAVEWORK from the menu corrected to work for Model Management projects with a missing default file des-userdefinedhook.pmlmac.

Design 11.6.sp3

HPD 30074 (8615)

A floating window no longer causes PDMS to crash – on a machine with two screens.

Design 11.6.sp3

HPD 30730 (8664)

Corrected a WELD symbol error caused by the sequence TUBE WELD, zero length BEND, TUBE.

Isodraft 11.6.sp3

HPD 30740 (8669)

Precision in Draft Admin increased. Draft 11.6.sp3

HPD 30819 (8701)

General option added back to Query menu Design 11.6.sp3

HPD 30019 (8702)

Bolt diameter units were incorrect in the material list when Vessel/Equipment Trim is chosen.

Isodraft 11.6.sp3

HPD 30852 (8745) HPD 31127 (8808)

New Component Creation form no longer places a 90 degree elbow in place of a 45 deg one.

Design 11.6.sp3

HPD 30234 (8754)

Corrected errors with reference dimensions at the mid point of a tee.

Isodraft 11.6.sp3

HPD 31124 (8787)

Corrected error in Merge Changes handling of Table pages that caused DICE errors or a crash in an extract hierarchy.

General 11.6.sp3

HPD 31125 (8790)

Corrected fault causing Reconfigurer to crash with kerror 41.

General 11.6.sp3

HPD 31132 (8805)

Corrected a fault that caused a crash when deleting a DPSE under a ZONE.

Design 11.6.sp3


www.cadfamily.com



HPD 30984 (8838)

Corrected a fault causing partnumbers to be missed from the drawing – they were on the material list. This was traced to the fact that Spooler gave new part numbers to components across Branches, but Isodraft did not consolidate them when outputting part numbers FROMDB.

Isodraft 11.6.sp3

HPD 31174 (8840)

Resolved a fault causing a SPLASH error message when running a piping system isometric.

Isodraft 11.6.sp3

HPD 31076 (8842)

Can now use the GUI to modify the origin of a piece of equipment when using Ppoints On, Numbers Settings.

Design 11.6.sp3

HPD 31187 (8844)

The Purpose field on the Create Site form now shows the correct data.

Design 11.6.sp3

(8848) In Annotation Modify Mode, the box can no longer be resized to make the size smaller than the minimum permitted view size.

Draft 11.6.sp3

(8849) Various improvements to the operation of the Viewfinder and 3D view: (1) The 3D view always does reflect the VIEW direction. There is now an extra option on viewfinder menu to 'look through' view finder (same as on 3D view popup menu), which may help user to orientate himself. (2) The OK button on the modify view form now updates the 3D view graphics. (3) On UNDO the system now issues an alert if UPDATE DESI required. (4) There is a new option on the orientation menu to reset the angle to zero. (5) Moving the view frame with the secondary mouse button & selecting cancel now clears the 2D view temporary graphics. (6) Resize hotspots are now be cleared for a new view.

Draft 11.6.sp3

HPD 29872 (8867)

Isodraft no longer creates a slope arrow with the wrong slope direction (where the start/end of a tapped fitted branch was incorrectly treated as if it is on the main pipe).

Isodraft 11.6.sp3


www.cadfamily.com



(8871) The Equipment application utility to control graphical navigation (selecting Equipment, Sub-equipment or Primitive) did not work at 11.6 and has been changed so that it works better: • The toolbar Navigate button is now a toggle:

On allows equipment and primitive level picking using EDG as before… Off means that Model Editor mode is used.

• The Model Editor mode button is inactive when in any EDG mode.

Design 11.6.sp3

HPD 30916 (8876)

Unpinned docked windows are no longer animated: they now appear and disappear instead of sliding back and forth.

Design 11.6.sp3

HPD 31216 (8890)

The Dimension line for the Valve was incorrectly extended to include a connected Flange. (Flange was MTOC OFF – MTOC DOTU – MTOC DOTD – the flanges, gaskets and valve were all SHOP FALSE.)

Isodraft 11.6.sp3

AID text now has a background colour to make it more easily visible, especially on point clouds.

Design 11.6.sp3

HPD 31252 (8897)

A long piece of pipe was incorrectly split in two in the MATC file under certain circumstances.

Isodraft 11.6.sp3

(8909) Flush can now handle elements in secondary lists which no longer exist.

Design 11.6.sp3

HPD 31351 (8920)

Spool number was missing at a bypass. Isodraft 11.6.sp3

HPD 30657 (8932)

Spool numbers greater than 99 are now handled. Isodraft 11.6.sp3

HPD 31213 (8949)

Corrected a fault causing a 'twisted' pipe drawing with the option FALLSKEW TWODBOX ON.

Isodraft 11.6.sp3

HPD 31405 (8952)

When showing existing pipe by setting the MTOC, MTOH and MTOT attributes of the existing components and/or branches to DOTD, spool numbers are no longer shown for these items.

Isodraft 11.6.sp3

HPD 31401 (8955)

The OUTC command now displays a REAL UDA correctly according to its settings.

Isodraft 11.6.sp3

HPD 31439 (8965)

Corrected the bend curvature appearance on the drawing isometric. (This was the first bend in a spool drawing, right after a flange.)

Isodraft 11.6.sp3


www.cadfamily.com



HPD 31448 (8974)

The Draft GUI will now output the results of queries more accurately.

Draft 11.6.sp3

(8976) Corrected a spatial map inconsistency error shown by DICE after a merge. This could result in a Dabacon error 534 in DESIGN

General 11.6.sp3

HPD 31489 (9001)

Corrected an error in composite dimensions when insulation is set for a zero length pulled bend which is followed immediately by a Tee in-leg.

Isodraft 11.6.sp3

(9008) Speed improvement when adding a large XGEOM to the Design Explorer.

Design 11.6.sp3

HPD 31554 (9021)

Report template width field extended.

Design 11.6.sp3

HPD 31611 (9061)

Corrected a crash caused by a catalogue item having more than 100 visible ppoints.

Design 11.6.sp3

HPD 31658 (9062)

Corrected a missing item number on Iso for an instrument that should be marked correctly with both item number and the name of the item (because of an OUTCOM element).

Isodraft 11.6.sp3

HPD 31463 (9065)

The drawing of Venturi (PCOM with SKEY based on SGPL) with 3 offline legs has been improved. Currently, Isodraft restricts the number of tapping points on a PCOM to 3 – 2 end points and 1 middle point. If a tapping is not close to the centre, it is pushed to the nearest end – this tolerance has been relaxed but users are advised to place the middle tappings as close to the centre as possible.

Isodraft 11.6.sp3

(9083) Improved SaveWork speed by reducing the dynamic memory allocated.

General 11.6.sp3

HPD 31711 (9091)

Corrected dimensional errors on branches. Isodraft 11.6.sp3

HPD 31743 (9092)

Corrected an error causing file write locks to be left when a flush generated error.

General 11.6.sp3

HPD 31744 (9095)

Corrected an error causing a name clash not being detected on Flush.

General 11.6.sp3

HPD 31687 (9097)

Corrected a Dimension problem with set-on tees with no spool – the dimension was from the HPOS instead from the centre line of the main branch.

Isodraft 11.6.sp3


www.cadfamily.com



HPD 31763 (9104)

The number of welds at LUGs has been corrected. Spooler 11.6.sp3

HPD 31859 (9131)

Corrected the replicate macro so that it does not insert a $ at the end of a long line as a continuation in the middle of a text string.

Admin 11.6.sp3

HPD 31901 (9161)

Corrected a crash when setting attributes to rules. Design 11.6.sp3

HPD 31902 (9164)

Corrected a crash when navigating to Draft elements in Design.

Design 11.6.sp3

(9219) Corrected a crash when making a relative move (BY…) using Positioning Control (Graphics option) and picking the "marker" cone at the branch TAIL.

Design 11.6.sp3

(9236) Corrected viewfinder operations to prevent an error message “Variable!!DRA3DVIEWSECTIONS does not exist”.

Draft 11.6.sp3

HPD 32018 (9259)

Fixed error querying attributes of SCOM, or using Show Attribute).

Paragon 11.6.sp3


www.cadfamily.com

pdms 11.6.sp1 release bulletin - cadfamily.com · 3.12 add to drawlist tool bar *sp1* ... 3.14 hvac...

Documents

pdms 11.6.sp1 release bulletin - cadfamily.com · 3.12 add to drawlist tool bar sp1 ... 3.14 hvac...