A new Puma5 release has just been made available. This is what you can find in the latest Puma5 version No. 02.950.04.00:
The ‘Material category’ has been added to associate the IOGP standard to the material codes used for component definition. Of course, this new attribute can be used also for other definitions than the IOGP standard. Using the ‘material category’ is optional. The following modifications have been applied:
Sketch revision synchronization
It is now possible to synchronize the sketch revisions between two different managements: ‘Isometric Sketch list’ (= type “A”) and ‘Sketch material – Status & Revision management’ (= type “B”). Type “A” is the management that has always been inside the application, with a ‘Sketch revision indexes’ dictionary that contains the ‘revision index’ code, the date, the description and information relating to the staff who performed the issue. Type “B” is the management which was added to the application a few years ago and it also allows the archiving of the take-off by associating them with revision codes. Thanks to the synchronization of sketch revisions the management indexes of type “B” are copied to the management indexes of type “A” so that:
A full description of the new functions is available for download from our support portal.
Component catalog delete OLD component
The ‘Component catalog delete OLD component’ function has been added. With this function it is possible to delete components that do not comply with the piping class any more (“OLD”). The cancellation deletes the component for the piping class and any links to the “Bolts linked components” and “Gasket linked component” tables, and the entries in the “upgrade operation log” table. Regardless of the filter applied, the component selection – and therefore its cancellation – can only take place for components of “OLD” type and with no reference in the following tables: Assemblies, Branches, Take-off level 1, Take-off revisions, Take-off history, Material requisition, Tracing. After deleting the components of “OLD” type for the relevant piping classes, it is also possible to delete any components that are not referred to any piping class: to do this, use the ‘Filter’ form to set the filter option ‘Piping class = No’.
Update project custom code with custom code taken from general catalog
The ‘General custom code’ item has been added in the selection box of the ‘Custom code filling options’ field (settings); this option refers to the values of the ‘custom code’ field of the ‘general catalog’ table. The options ‘Overwrite not empty values’ and ‘Ignore lock’ are also available for use in this field.
For a complete overview of the new features added in the latest version of Puma5, please log into our support portal and download the latest “what’s new” document stored in the Puma5 section.
The latest version of Puma5 application (02.950.02.00.) shows some important modifications applied to the Alternative Thickness management and to the Composer table structure.
Alternative thickness management – Previously, the function of copying piping classes between different projects did not transfer the link between the piping classes and the ‘alternative thickness’ table code; this resulted in the loss of the thickness settings of some components of the piping class, such as, for example, ”Nipple” type objects.
Now the ‘Piping class copy’ form has a new option named ‘Move data to new Alternative thickness table’;
when the option is enabled, the thickness measurements of the Alternative thickness table linked to the component get appended to the new ‘Alternative thickness’ section of the same component.
The ‘Piping classes’ menu also introduces another new feature: ‘Alternative thickness move’.
This new function “moves” the thickness measurements from the “alternative thickness” table associated with the component, into the “Piping class component – Alternative thickness” section of the component itself. The code of the previous ‘Alternative thickness’ table will be removed from the definition of the piping class component.
Composer – it is now possible to create more than one set of assignment rules for the same ‘Composer context’ code. Therefore different groups of rules can be used on different projects and it will be possible to repeat in a ‘composer group’ the same ‘assignments’ already present in another group.
The table structure has changed. Two keys now identify records:
The ‘composer group’ field is now mandatory. The procedure that updates the application to this version introduces a value in the ‘composer group’ field, in case this field is empty. The new ‘composer group code’ values are automatically generated through the text “SysGrp” followed by a progressive number, for example “SysGrp0006”.
A new type of report has been created in the Take-Off module of Puma5: it is called “BILL OF MATERIAL LIST (3) Export only” and it produces an ‘output’ which is almost equal to the report called “BILL OF MATERIAL LIST (1)”. The main differences are:
For a complete overview of the new features of this Puma5 release, please log into our support portal and download the latest documentation.
WARNING: this new release upgrades Puma5 from any version to 2.95; to avoid any problems during the installation, please make sure that you ask for the new database license by opening a ticket on our support portal before running the upgrade (http://support.cla-it.com/).
Two main improvements have been made to the automatisms generating the component catalogue:
bolts and gaskets generation on the second diameter of a component – you can enable the function through the ‘2nd size joint’ field in the ‘Components’ section of the ‘Piping class’ form (this field is active only for those components having the bolts and gaskets generation enabled). During the ‘Component catalog upgrading’ procedure, for those components having the ‘2nd size joint’ indicator activated, bolts and gaskets will be generated by using the second diameter value (branch);
new ‘Object-Finish’ table in the Object-Finish dictionary – the table has been added to allow the creation of links between gasket-type objects and the ‘finish’ attribute. These links are used only for those gasket-type components that are defined without the ‘finish’ code in the piping classes.
During the ‘Component catalog upgrading’ procedure, for gaskets with no ‘finish’ code, a link is created with the flanged objects by using the ‘finish’ code of the ‘object-finish’ dictionary.
Other improvements refer to the general environment:
project grouping functions – in order to manage the grouping of different projects, new functions have been added. These functions allow the creation of links between different projects of the same database (read the “what’s new” document available for download from the support portal for more details);
filter setting – the ‘filter setting’ management has been added; it is now possible to save all filter fields values of a form into the database. This new function is described in the document named WHAT’S_NEW_PUMA5_02.950.00.00_Detail_EN.pdf, available for download from the support portal.
Component weight on General Catalog – A new major feature has been added: the component weight is now available in the general catalog.
Previously, the component weight was stored for the specific project only; now it is possible to add component weights that are ready to be used for any project inserted in Puma5.
Weights for the single component are divided into weight groups, and for each one of these groups a dictionary has been added.
Data flow between the General Catalog and the component catalog of the single project is bidirectional: values of the project component catalog can populate the General Catalog or the weight values of the General Catalog can be inserted into the project component catalog.
Update of the component catalog attributes – Speaking of the project component catalog, there is a new function that allows the update of some fields by using a two-column Excel file; the file needs only one column with the component ID (=mark) and one column with the value to be updated.
The function is restricted to the following fields:
More detailed information can be found in the “What’s new” document available for download by logging into our support portal
Actually, there are a few nice new features you will be interested in. Let’s start with the Piping Class module and with a new procedure taking place at the end of the mechanical check of internal thicknesses. Up to now, you would end the process and get a report showing which thicknesses are suitable and which are not. Starting from this release – if you choose to – at the end of the check procedure, a form will be displayed allowing User to modify the unsuitable thicknesses.
The version 2.91 patch 5 (02.910.05.00) of our Puma5 software brings some big news to the Piping Class and the Mechanical Checks modules.
As usual, you will find the complete details in the What’s New document available for download from our Customer Care portal, however we give you here a glimpse of what you will find in Puma5 latest release.
Piping Class module – Piping Class form
There is a new ‘Copy’ button here and it is used to copy thickness tables among different classes belonging to the project in use (note: this can be done only among piping classes, whose associated ‘base material’ belongs to the same ‘Material subtypes (S2)’ section of the thickness dictionary).