Professional Documents
Culture Documents
User Bulletin
Version 11.6.sp4
pdms1164/PDMS Bulletin
Issue 130207
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.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
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
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.
This service pack addresses a number of points raised during the use of
earlier releases of PDMS 11.6, along with corrections to faults found
during testing and use of earlier releases of PDMS. Details of these
changes can be found in Section 11.6.
In addition, there are some additional features, which are summarised
here and described in more detail in separate sections of this document.
The sample projects have also been updated, to include a steel catalogue
for Australia & New Zealand (see Section 1.6.4) and a dictionary
database for MDS (MASTER/MDSDICT) – please see Chapter 10.
SP4 is accompanied by updates of some of the add-on products, notably:
VANTAGE Plant Design Router 2.4.sp4
VANTAGE Plant Design Global 2.4.sp1 (see Section 1.6.6.1)
VANTAGE Multi-Discipline Supports 11.6.sp4 (see Section 1.6.6.2)
1.6.6.2 MDS
MDS 11.6.sp4 provides an interface to the design applications provided
by various pipe support vendors: Lisega, Carpenter & Paterson, Pipe
Supports Ltd. Please refer to MDS documentation for details.
This bulletin outlines the major changes at both the original PDMS 11.6
release and its service packs: it is updated for each service pack.
Most of the manuals were updated for PDMS 11.6; many had significant
changes that are noted on a Revision History page at the front of the
manual.
The Pipework design using VANTAGE PDMS manual, which was not
included in the original release, was updated for PDMS 11.6.sp1. The
following manuals were also updated for sp1:
• PDMS Installation Guide
• Drawing Production Using VANTAGE PDMS 11.6
• PDMS Software Customisation Guide
• PDMS Software Customisation Reference Manual
Many of the other manuals had minor amendments and corrections.
For PDMS 11.6.sp2, there were again amendments to 4 manuals:
• Drawing Production Using VANTAGE PDMS 11.6
• PDMS DESIGN Reference Manual Part 1:General Commands 11.6
• PDMS ISODRAFT User Guide 11.6
• PDMS ISODRAFT Reference Manual 11.6
The release also contains updated Design and Draft online help files:
updates were also supplied as a fix release PDMS11.6.SP1.2.
PDMS 11.6 is supported for use on Microsoft Windows 2000 SP4 and
Windows XP Service Pack (SP) 1 or 2. It is not supported on the new
Windows Vista – please see section 1.12 below. There is no UNIX version
of PDMS 11.6.
Windows XP SP2 requires changes to the default settings. The Internet
Connection Firewall (ICF) should be turned off or configured to enable
access to the database & licence servers. In addition, Group Policy
changes (which alter the registry) are required for users of Global
projects to ensure that RPC requests do not require authentication.
Details are given in the Installation Guide.
PDMS 11.6 requires Microsoft’s .NET Framework 1.1, which is supplied
on the CD-ROM and installed if required. This is used for the PDMS
graphical user interface. Please note that PDMS 11.6 is not compatible
with .NET Framework version 2.0 or later; if later versions are required
for other applications, it is necessary to install them in addition to
version 1.1. Further information is available on Microsoft’s web-site, for
example, see http://msdn2.microsoft.com/en-us/library/s80xxs7s.aspx.
PDMS 11.6 should run successfully on Windows NT4, but it has not been
tested under Windows NT4 and is no longer supported in that
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.
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).
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
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.
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.
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…
Explorer views have now been extended from the Design Database to
cover other modules and databases. The Application Framework
manages their layout and dockability. They provide a consistent tree
view of each database and module specific context menus.
An important feature of the Explorers is the ability to allow flexibility in
the presentation of the database hierarchy through the use of filters.
These are different sets of filters for different Databases. Additional
filters and other Explorer options are available on an Explorer Settings
form. The user may Drag-and-drop elements within and outside the
Explorer.
There is now a separate Toolbar Add-in, which shows the current
Element History.
Explorers are available in the Design, Draft, Spooler and Isodraft
modules, and replace the PML-based Members Lists. They are available
from the Main Menu>Display menus in each module. Each Explorer is
restricted to Elements of a particular database type.
2.4.1 History
The History Add-in appears on the main toolbar in Design, Draft, Spooler
and Isodraft. It displays the current element (CE), regardless of the
database.
The user can set the CE either by typing the element name into the
combo box, selecting a previously typed in element from the drop-down
list, navigating through the CE history one element at a time using the
backwards and forwards buttons or by selecting elements from the CE
history list using drop-downs on the backwards/forwards buttons.
When typing into the combo box the system attempts to auto complete
the name by scanning the open databases for the first 15 matches and
displaying them in a pop-up list. The user can then either carry on
typing or select an element from the list. When docked vertically the
toolbar displays only the backwards and forwards buttons; the combo box
is not displayed.
2.4.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.5 Drag-and-drop
The Explorer supports Drag-and-drop within the Explorer to copy
elements, Drag-and-drop into the 3D view to add elements to the Draw
List and Drag-and-drop into My Data to add elements to it.
2.4.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
2.6 My Data
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.
The user can ping locations by selecting them and using the Apply button
and then Sort and Filter results. Results are appended until the Clear
Results button is pressed.
The user can check locations by selecting them, toggling Lock, Isolation
or both and pressing the Apply button. The status will be displayed
below.
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
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.
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.
connect and position a component with the minimum spool length, the
system will now return: Incompatible Connection error.
Set Branch option now sets the current spec of the branch into the form,
so that all component Selection is from the branch spec.
Equal size tees with PBOR3 set to E in the relevant column of the spec
no longer give a warning message.
See also fault corrections – section 11.5.
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.
The new pipe component creation form allows the user to create a
component or component group that is either connected or positioned
along the route of a pipe.
The system will automatically try to create a set of predetermined
adjacent component types when certain component types are created, e.g.
creating a valve will try to create the appropriate adjacent gaskets and
flanges. This allows the pipe designer to define the major components of
the pipe route, with the system creating the secondary components
automatically.
Once a component (or group of components) has been created the system
will automatically select it, allowing the user, when in “Modify Mode”, to
modify the component’s position or rotation.
shaped and aligned with major plant axes; in other cases, they are more
likely to be irregularly shaped, positioned and orientated.
New Design Database elements (top level AREAWL, AREASET,
AREADEF, ABOX, ACYLI, ACONE, ADISH, ASLCY, ACTOR, APYRA
and ASNOU) have been added for modelling Design Areas. These
primitives are defined in a similar manner to the normal equipment
primitives. Clash detection may be used to determine the contents of
these areas.
• Which plant item origins are in a given Area?
• For a given item, which Area(s) contain its origin?
Collections have been enhanced to reference Areas: some of the geometric
operations have been improved, including an EXCLUSIVE option for
WITHIN.
These Areas will be used in future PDMS applications and for improved
integration with VANTAGE Project Resource Management.
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”.
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).
PDMS 11.6.sp4 allows you to check pipe pieces and pipe spools for
production readiness against welding machines, bending machines, pipe
cut lengths on drawings and reports, and defined stock-lengths of tubing.
• Fabrication checks run against available stock length and fabrication
machines.
• Fabrication machines are currently limited to bending and auto
welding.
These checks rely on a number of changes to the Design database that
were introduced at PDMS 11.6.sp1. They were initially introduced for the
marine product.
Pipes designed and checked in this way may be detailed using the new
pipe-sketch facility – but not yet with Isodraft. Please see section 5.8.
3.15.1 Definitions
Pipe Piece
A pipe-piece is the lowest level of fabricated item in the pipe. It relates to
a continuous piece of pipe tube that can be fabricated from stock
material.
The pipe piece holds references to the components at the start and end of
the piece. The system derives pipe-pieces: users cannot create or delete
them. Note that components on the end of the pipe pieces are not part of
the pipe piece, but are referenced by it.
Pipe Spool
A pipe spool is a prefabricated part of a pipe or branch, often welded
together in a workshop before being sent to the ship to be fitted on-site.
Pipe spools typically comprise a bent pipe with welded flanges at each
end, but they can also be more complicated fabrications with branches,
reducers and other components.
The system derives spools: users cannot create or delete spools. PDMS
11.6 does not include gaskets in the spool.
Design grid
New top level element GRIDWL: used for ship coordinate system but not
used in PDMS 11.6.
Once this is done, the main form will be displayed: it has five sections
that allow you to control different aspects of the production check on the
pipe and its spools:
• Spools for the currently selected pipe
• Tasks relating to the entire pipe
• Tasks relating to the currently selected spool
• Navigation relating to the currently selected spool
• Options for setting up production checks.
Pipe Tasks
Option Function
Validate Pipe Runs production checks against entire
pipe. The checks run for each spool in
the pipe that requires validating
View Production Information Displays the production information
currently associated with each pipe
spool and pipe-piece
Remove Machine Info Removes machine fabrication
information from all pipe spools and
pipe-pieces in the pipe
Spool Tasks
Option Function
Validate Spool Runs production checks against the
selected spool
View Production Information Displays production information
currently associated with the spool and
its pipe-pieces
Remove Machine Info Removes machine fabrication
information from the selected spool
Navigation
Option Function
View Spool in Graphics Sets up 3D View so the selected spool
fits in it
Select the machine you want to use and click Apply; if you want to cancel
the operation, click Back.
To avoid choosing incompatible machines, you can pick out fabrication
machines that can handle the pipe tubing in the selected spool. The
system checks the bore, material, and length of the tubes to see which
machines can handle the spool. To do this click For Spool x, (where x is the
number of the selected spool) and the lower pane changes to display a list
of the machines that can handle the pipe tube in the selected spool.
Select the machines you want to use from the list and then either append
them to the current default machine list by clicking Append to Default
Machine List, or replace the entire list by clicking Replace Default Machine
List.
Clicking Back will take you back to the previous screen.
The lower part of the form shows the results for each pipe-piece of the
selected spool.
A list of pipe-pieces shows the production check results per piece, and each
piece has one of the three states above associated with it.
Selecting a pipe-piece from the list displays the detailed results of the
check below the pipe-piece list. The information displayed in this part of
the form depends on the results of the check. Some examples of different
results follow.
You can add your own end-excess by entering a value in the User Defined
text box.
Click Accept Changes to accept the new value.
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.
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.
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.
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.
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.
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.
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.
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.
This new feature allows the user to add a weight column to the isometric
material list and provide a summary total for the fabrication and erection
material plus an overall total for isometric material weight.
4.7.3 OUTPUT
• For the total weights, a new text element is optionally placed below each
material column.
• All of the above texts have been given a text number and added to the
alternative text list so that they may be modified to a different language.
• If a component does not have a weight, a ‘---‘ character string is output to
indicate that no weight can be found.
• The weight column and extra weight text is output to the
MATLISTFILENAME file if selected.
Isodraft places flow arrows on the isometric with their direction governed
by the BRANCH attribute FLOWDirection. The function is controlled
using the FLOWARROWS command (please see ISODRAFT Reference
Guide). The arrows can be placed automatically or positioned using
ATTAchments with their ATTYpe attribute set to FLOW.
The settings for FLOWD are either BACK for flow from tail to head or
FORW for flow from head to tail.
Two new settings are now handled by Isodraft: OFF to allow the arrows
to be turned off or BOTH to indicate a two-way flow. Any other setting
will continue to be treated as forward.
Examples of 2-way flow arrows are shown below:
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.
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.
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.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.
Associated
View
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.
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.
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.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)
Figure 1 Figure 2
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.
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.
• 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.
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.
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.
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
Search Results
This list is a collection of all the pipe spool elements of the of the root element, filtered
by the criteria above. The system processes only pipe spools selected in this list when
you click Create Sketches.
The results should be self-explanatory; however, the list also has a pop-up menu,
accessed by clicking the secondary mouse button anywhere in the list area:
Create Sketches
The Create Sketches button sets the process in action.
A message should appear in the status bar to record progress, e.g. ‘Generate Pipe
Sketch n of N’.
When the system has created the pipe sketches it adds them to the Draft Explorer.
Backing Sheet
The Pipe Sketch references the Backing Sheet, which is generally user-
defined. It is a standard backing sheet containing the drawing title block,
with drawing data displayed via intelligent text,
e.g. #DATE<FR DRWG> and #:UDA_Name etc.
In addition to the standard title block, the backing sheet is used to
identify and locate ‘TABLES’ that are used on the Pipe Sketch.
These tables are identified by:
MaterialTakeOff function ‘MTO’ SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
Bending Table function ‘BENDING’ SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
Bending Activities function ‘BENDINGA SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
Welding function ‘WELDING SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
Assembly function ‘ASSEMBLY SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
End Points function ‘ENDPOINT SpPurpose ‘TABLE’ or SpPurpose ‘CELLS’
Tables
In database terms the Table is a NOTE of the Backing Sheet (BACK).
There are two notes required, one for the Table headings and one for the
Table cells. Both notes are positioned at the same point. For example:
BACK named /DRA/MAS/BACKS/PipeSketch/A4 SETST
NOTE named */ExampleTable function ‘ENDPOINT SpPurpose ‘TABLE’
NOTE named */ExampleCells function ‘ENDPOINT SpPurpose ‘CELLS’
The example below is a table defined on a backing sheet. Although this
table is visible in the view, it will in practice have its visibility flag
(LVIS) set to false. The reason is that this table is copied onto the Pipe
Sketch Drawing then the cells of the table are populated with data from
the actual Pipe Spool.
XYPOS of the
Tables (NOTE)
The figure below shows the table in situ on the final pipe Sketch Drawing.
MTO Tables
The figure shows the MTO/Material Take-off tables on the backing sheet. On this type
of table the ‘cells’ data need to be attributes of the Pipe Spool elements, e.g. DTXR and
MTXR attributes as used in the Description and Material columns.
Other Tables
Bending, Bending Activities, Automatic Welding, Assembly Activities
and End Points tables are similar.
5.8.4 Styles
All Drawing Styles and Representations are inherited from the template
drawing. These include the View Representations, text colours and font
size for Labels and Dimensions.
Key Members:
Member Type Comment
!!pipeSketch.createIn DBREF Must be an existing Registry –
REGI element
!!pipeSketch.selectedTemplate DBREF Must be an existing Drawing –
DRWG element
!!pipeSketch.pipeSpool DBREF Must the an existing Pipe Spool –
PSPOOL element
Optional members
Member Type Comment
!!pipeSketch.logFile FILE The Form or User must write and
read this file
!!pipeSketch..drawingPrefix STRING Default is ‘DR’
!!pipeSketch..sheetPrefix STRING Default is ‘S’
NB. The */ColumnLine1 direction of ‘From Point’ and ‘To Point’ defines the direction of the rows.
5.8.8 Dimensions
Dimensioning is controlled from the Template Drawing:
A VIEW will be dimensioned only if it has a LAYER with a PURPose of
‘DIMA’. If this layer exists, the dimensions go into that layer. The style of
the dimension will be cascaded from the owning layer.
5.8.9 Tags
Tagging is controlled from the Template Drawing:
A VIEW will be tagged only if it has a LAYER with a PURPose of ‘LABA’.
If this layer exists, the tags will go into that layer. The style of the tag
will be cascaded from the owning layer, or taken from a symbol template
in the case of component tags.
A typical symbol may look like this:
Weight and Centre of Gravity calculations use CWEI & UWEI attributes
in the Property Database. Until PDMS 11.6.SP4, these attributes were of
type literal; they have now been extended to allow the use of Design
Parameters. This should be especially useful for highly parameterised
catalogues, such as those used typically for HVAC & Pipe Supports.
The Remote File Details and Remote Last Session form can be invoked in
two ways:
Either Or
From Admin Main Query menu bar: Popup menu in Admin Element form:
Query>Project>Remote Filedetails… Query>Remote Filedetails…
Remote Last Session… Remote Last Session…
Figure 1 Figure 2
Selecting the Remote Last Session option displays a similar form with
results relevant to the last session:
In both forms, the Location option lists all the online (not offline)
locations. On selecting a location, all the databases of that location will
be listed. If the Daemon of the selected location is not working, the Apply
button is de-activated and the status of daemon will appear adjacent to
the button. While the system establishes connection with the Daemon of
the selected location, the status file informs the user. Select one or more
databases from the list and press the Apply button. Now the resulting
file detail or session detail of the selected database(s) is listed on the
right of the form, along with the database name – see below.
Results can be stored by entering a file name and pressing the Report
button.
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.
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.
8.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.
8.4 Internationalisation
8.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.
PML encryption is a new option available to use with PDMS 11.6.sp4 and
future releases of PDMS. It is intended to allow PML developers to issue
their applications for general use without disclosing the ‘source code’ and
hence the details of the techniques used.
8.6.1 Decryption
PDMS 11.6.sp4 onwards can run PML files that are encrypted using
AVEVA’s pmlencrypt utility. The resulting PML files can no longer be
read or edited but no special action is required to run them in PDMS.
8.6.2 Encryption
The pmlencrypt utility is a separate program that encrypts PML files. It
is up to the user to decide which file(s) he wishes to protect in this way,
though it should be used only on PML functions, objects forms and
macros and not, for example, images that might be stored in the same
directory. It requires a PML Publisher licence in the license file (the
feature name is VPD-PMLPUBLISHER). Please refer to the user guide
for full details.
8.6.3 Buffering
Decrypting a PML file takes longer than reading a plain-text version, and
in some circumstances PML files may be re-read many times during a
session. (A new command PML STATISTICS displays information on the
numbers of times each file has been read and some extra information
useful to AVEVA when testing the Published PML facilities).
In order to reduce the time taken to re-read the files Published PML files
may contain a buffering directive in the header-line (the first line in the
file). If a dash and a number are included directly after the three-digit
encryption algorithm id, then PDMS will retain the file in memory
indefinitely once it has been read that many times.
You may wish to edit heavily used files to add buffering to the header by
hand, or may use the –buffer 5 option of pmlencrypt.exe to include a
“buffer after five reads” tag in each file encrypted.
A value of five is a good number to start with. Many files are read
precisely once during module start up: there is little benefit in buffering
those files, and a value of five will avoid that, but apply to all heavily
used files.
If a file you are actively developing has a header including buffering, it
will not be re-read as often as you are used to. To force all buffered files
to be cleared from memory if they are not in current use you can issue
the PML REHASH or PML INDEX commands, or switch modules.
9.1 Summary
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.
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-
specify its minimum size to ensure that all the menu bar fields
actually appear.
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.
Applications may need adjustment if this new option (at SP4) is used –
see also note on upgrades to DARs programs.
the name of the SPRF with appropriate spaces inserted. The Description
attribute may be used in Draft to label a SCTN or GENSEC by setting
the label intelligent text to #DESC<FROM CATREF>.
The relevant Australian and New Zealand Standards do not specify
bolting cross-centre and backmark dimensions. The values given are
based on existing PDMS catalogue values for similar shape sizes from
other Standards.
Level and Obstruction attributes have been set for all shape geometry
elements in accordance with the following table:
Drawing Obstruction
Representation
Levels Value
Simple Draft 0-3 0
Detailed 4-8 2
Obstruction 9 - 10 1
Note:
Simple Draft representations have no root or toe radii included, where
applicable. Obstruction volumes have been constructed such that they do
not cover the detailed profile shape.
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.
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.
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.
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.
pair of flanges.
HPD 28762 Itemcode from UDA now works correctly when Isodraft
(7162) the number of UDAs exceeds 30. 11.6.sp1
HPD 28912 Utilities > Export > Dump Attributes utility now Design
(7173) works correctly when is a BRAN component that 11.6.sp1
has an unset or bad SPREF.
HPD 28933 Creating Corner Posts with the ASL Modeller Design
(7298) application now locates the corner posts correctly 11.6.sp1
with an imperial project.
HPD 28965 Can now modify floor fittings. Design
(7398) 11.6.sp1
HPD 27131 Module switch will no longer crash when there is General
(7520) an instance of user defined object with member(s) 11.6.sp1
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.
HPD 28477 Q BREARE now gives the correct result for a Design
(7539) TUBI after a REDU. 11.6.sp1
HPD 28477 Highlighted elements are no longer displayed Design
(7661) wrongly. 11.6.sp1
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.
This lists the most important corrections in Service Pack 2, at the time of
writing (October 2005).
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.
HPD 30349 The 3D display has been corrected to show the Draft
(8534) ‘teeth’ of the section planes in the correct direction. 11.6.sp3
In the 3D view, the teeth indicate which side of the
(8855)
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'.
HPD 30367 PDMS no longer shuts down if Windows/Forms for General
(8535) Explorer, Command Window and Drawlist are in 11.6.sp3
one set and moved together.
HPD 30485 Improved display of the alert input form with long General
(8538) text – it no longer gets cut off. 11.6.sp3
(8544) Highlighting on ppoints (& plines) for picking, e.g. Design
(8572) if you use Q IDP @ when you select the item, was 11.6.sp3
not working, though there was feedback in the
prompt space for the ppoint passed over.
HPD 30327 Output in some Draft Admin forms has been Draft
(8564) improved so that it no longer shows as an 11.6.sp3
exponential number.
HPD 30649 SAVEWORK from the menu corrected to work for Design
(8613) Model Management projects with a missing default 11.6.sp3
file des-userdefinedhook.pmlmac.
HPD 30074 A floating window no longer causes PDMS to crash Design
(8615) – on a machine with two screens. 11.6.sp3
HPD 30730 Corrected a WELD symbol error caused by the Isodraft
(8664) sequence TUBE WELD, zero length BEND, TUBE. 11.6.sp3
HPD 30740 Precision in Draft Admin increased. Draft
(8669) 11.6.sp3
HPD 30819 General option added back to Query menu Design
(8701) 11.6.sp3
HPD 30019 Bolt diameter units were incorrect in the material Isodraft
(8702) list when Vessel/Equipment Trim is chosen. 11.6.sp3
HPD 31216 The Dimension line for the Valve was incorrectly Isodraft
(8890) extended to include a connected Flange. (Flange 11.6.sp3
was
MTOC OFF – MTOC DOTU – MTOC DOTD – the
flanges, gaskets and valve were all SHOP FALSE.)
AID text now has a background colour to make it Design
more easily visible, especially on point clouds. 11.6.sp3
HPD 31252 A long piece of pipe was incorrectly split in two in Isodraft
(8897) the MATC file under certain circumstances. 11.6.sp3
(8909) Flush can now handle elements in secondary lists Design
which no longer exist. 11.6.sp3
HPD 31351 Spool number was missing at a bypass. Isodraft
(8920) 11.6.sp3
HPD 30657 Spool numbers greater than 99 are now handled. Isodraft
(8932) 11.6.sp3
HPD 31213 Corrected a fault causing a 'twisted' pipe drawing Isodraft
(8949) with the option FALLSKEW TWODBOX ON. 11.6.sp3
HPD 31405 When showing existing pipe by setting the MTOC, Isodraft
(8952) MTOH and MTOT attributes of the existing 11.6.sp3
components and/or branches to DOTD, spool
numbers are no longer shown for these items.
HPD 31401 The OUTC command now displays a REAL UDA Isodraft
(8955) correctly according to its settings. 11.6.sp3
HPD 31439 Corrected the bend curvature appearance on the Isodraft
(8965) drawing isometric. (This was the first bend in a 11.6.sp3
spool drawing, right after a flange.)
HPD 31448 The Draft GUI will now output the results of Draft
(8974) queries more accurately. 11.6.sp3
(8976) Corrected a spatial map inconsistency error shown General
by DICE after a merge. This could result in a 11.6.sp3
Dabacon error 534 in DESIGN
HPD 31489 Corrected an error in composite dimensions when Isodraft
(9001) insulation is set for a zero length pulled bend 11.6.sp3
which is followed immediately by a Tee in-leg.
(9008) Speed improvement when adding a large XGEOM Design
to the Design Explorer. 11.6.sp3
This lists the most important corrections in Service Pack 4, at the time of writing
(January 2007). Please note that the list is not complete; some other internally
reported issues have also been corrected.