Archive for the ‘Puma’ Category

A quick Puma5 update

Wednesday, December 21st, 2016

It’s been quite a while since we last gave you an update about our Puma5 software. Hard work has been going on to improve the system; as usual, we’ve also listened to your requests and enhanced the software accordingly.

In the “Piping class component” form, for example, the ‘Copy to…’ command button has been added; this button is associated with the function that copies components from one piping class to the other. By using the ‘Check’ button, it is possible to check for the existence of the selected components in the destination piping class.

Changes have been made also in the “Component catalog – custom description” form:

  • fields have been positioned on 5 rows;
  • the ‘filters’ form has been added;
  • for the copy function (‘Copy values’ button), the value of the ‘mark’ field can be used as the source of the copy;
  • the ‘Empty values’ function has been added, so it is now possible to set the ‘null’ value for the selected field in the ‘From code’ text box;
  • the ’sign’ field and the ‘Select all’ and ‘Select none’ buttons have been added, so that all the operations are now carried out only on the selected records.

A better visibility, especially for screens in landscape mode, has been given to controls and fields of the “Piping class Components” form:

  • controls that were in the section located under the fields with the diameter intervals have been moved to the right-hand section of the form;
  • the ‘Object Alias’ and ‘Tag filter’ fields have been moved to the right-hand section of the form;
  • the switches that act as filters for the ‘End’, ‘Rating’, ‘Construction’ and ‘Material’ values are on the right of the relevant fields.

Also, in the “PDMS Production Export”, the descriptions written with UNICODE characters are now exported; for example, it is possible to export Arabian, Cirillic, Greek, etc. characters.

CLA at “Planning Oil&Gas plants” university master

Friday, December 4th, 2015

The second level university master, “Planning Oil&Gas plants“, has become a pleasant tradition for CLA. The master is promoted by ENI, Tecnomare and ENI corporate university and it is held at Bologna university.

As every year, last week CLA dressed as professor to teach students the “Work flow & tools for Piping Management”. First of all the basic concepts of a piping class were explained, then the components were reviewed in detail (pipes, flanges, type of fittings, valves, gaskets, bolts, type of materials, etc.). This introduction allowed the presentation of our Puma5 (SPC PUMA) and ELENA software and the interaction of both applications to manage ENI’s projects in the piping management and the subsequent generation of the component catalogue.
Many jobs examples were analyzed and this raised interesting questions among the students attending.

Looking forward to seeing you again next year in Bologna!

Puma5 upgrades to version 2.9

Monday, September 14th, 2015

WARNING: this new release upgrades Puma5 from version 2.x to 2.9; 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 (

New Material Take-off attributes, Weight management split by Vendors and a restyling of the Piping class header: this is part of the news coming from the latest release of Puma5 software by CLA. Let’s see in detail.
The new three attributes (take-off erection area, take-off module and take-off package) are created directly from the project structure menu and they are attributes at component level (i.e. each component on an isometric can have different attributes). They can be used while doing a manual input of the Take-Off level 1 and they can also be imported from DRIE (Take-Off level 1 context). These attributes are available while running the Take-Off summaries as “group by” clause and as filters.

Another big improvement regards the Weight management: now you can store the weight table series split by vendor, which guarantees that the correct weight is assigned to the objects, coming from the vendor which supplies these goods. The final result is a weight table linked to each component (with its standard), based on the vendor catalogue. This functionality can be very useful to split the weight for different projects that may have different goods suppliers.

Last but not least, the piping class header form has been revamped: the Service and Note fields can now be edited separately; the field Service has also been extended to 65.000 characters.

As usual, more details can be found by logging into our support portal (
More features are explained by following this link:

New release for Puma5 (2.8)

Monday, July 6th, 2015

This 2.8 release of Puma5 is so packed with new features and improvements that we have created a slide presentation to show you in detail all the work that has been done. The slide presentation file can be viewed (and downloaded) at this link ( ) but here we sum up the main points.

Project selection form – redesigned; it is filtered, so you now see only those projects you have been assigned (if the role management is ON) and it is easier to search & edit.

Multiple client codes against unique code – it is now possible to save multiple client codes against the same unique code (Mark); an unlimited number of series can be saved, too. Client codes can be copied or swapped between the custom code columns.

Material Take-Off enhancements - multiple versions of the same isometric can now be saved and a status field can be set to any value for each revision; at the first edit, the default status for the project is used and the revision is set to zero, then you can start editing, save your isometric when you think it is ok and create a new revision: you can now proceed with more editing but the previous revision is safely saved. Previous versions of an isometric can be deleted or restored.

There is also a new interface for managing revisions:

Material Take-Off Sub-project enhancementsTake-Off subproject (at component level) and Sketch subproject (at isometric level) are the new subproject attributes that have been added to divide the material among subprojects (if any) when going to the material requisition and they can be used to assign Purchase locations.

Trace the Marks in the component catalog – enabled by a flag in the project setup form, this function tracks new Marks (MNW), marks that have become old (MBO) and marks that were old but have become valid again (MBV), with new reports to be generated.

Unique MR number and auto-number – Material requisitions have now a unique numbering which can be activated by ticking its checkbox in the project setup form. When the flag is on, also the auto-numbering feature can be enabled. Now you can easily see in which MR and how many items have been already requisitioned.

Run ELENA directly from Puma – this new setting has been added to allow running ELENA directly from the dimensional catalog module of Puma:

And the following operations are now automated:

  • upload files into Elena “input” section
  • run Elena build operation
  • make Elena save the output into Puma default folder.

Do you want to know more? Log into our support portal ( ) and download the new documentation or view the complete presentation ( ).

Puma5 upgrades to 02.700.00.00

Wednesday, February 12th, 2014

WARNING: this new release upgrades Puma5 from version 2.6.x to 2.7.x; 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 (

Sections, buttons, functions, warnings… many new features have been added to the latest release of Puma5, following Customers’ requests and our developers’ wish of giving you a more flexible and helpful application.

Let’s see some of them in detail…

Category of goods assignment
The screenshot below refers to the Category of goods assignment form. The red rectangle marks the new columns giving User the chance of adding a thickness range. Data here is optional, but if you’re using it, remember to insert dimensions in millimeters.

Design conditions

Up to now the design conditions were unique for each piping class; now, as you can see in the second screenshot, the design conditions form has been divided into two sections: “default” and “by size”.

Under the “by size” tab, design conditions can be inserted specifically for each diameter range and they will be taken into account before the default section. In fact, the default section will be used only if no data is compiled under the “by size” section.

Object – Constructions

Another screenshot, another implementation.

Have a look at the following image:

Yes, there is a new section in the “objects” form. Thanks to the “Constructions” section User can now insert those construction codes that are compatible with the object. Filling in this list of Object – Construction values will turn to be very useful when using the “Piping class components” form: the “By Obj” button has been added on the side of the “construction”  field; it narrows the list of constructions that can be inserted down to the constructions present in the “Object – Constructions” list.

As usual, there is a lot more to describe, but the full list of new features is available for download from our support portal.

Puma5 new user manual

Tuesday, December 17th, 2013

The new user manual for Puma5 version 2.6 is now available! Log into our support portal and download your copy!

Server Maintenance

Monday, December 2nd, 2013
Due to sever maintenance on the ENI Citrix installation (Name:, the applications SPC Puma, Drie and Tools will be unavailable from 8:00 AM to 2:00 PM (UTC+1) on Wednesday December 4th, 2013.
A causa di manutenzione del server ENI Citrix (Name:, le applicazioni SPC Puma, Drie e Tools non saranno disponibili dalle 8:00 alle 14:00 (UTC+1) di Mercoledì 4 dicembre 2013.

02.600.00.00: the latest Puma5 release has been issued

Thursday, October 31st, 2013

WARNING: this new release upgrades Puma5 from version 2.5.x to 2.6.x; 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 (

The main aim accomplished through this new release is the full compatibility of Windows 64-bit systems, having Office 64-bit version installed, with our Puma5 software.

As usual, we took the chance to add a few new implementations, such as a new “Surplus table/type copy” menu item within the “Projects/Tables” menu category, giving users the chance to copy the tables of the ‘Surplus tables’ and ‘Surplus types’ contexts in just one operation.

Some new automatisms in the Dimensional Catalog Export and the ‘Project tag code’ field of the Composer, that can now be used for creating codes and descriptions of the component catalog, have been added… hoping to make your job a little bit easier!

Log into our support portal to get the full list of implementations and changes:

New Puma5 release (02.500.09.00)

Wednesday, July 17th, 2013

A new Puma5 release (02.500.09.00) has just been published with new features and some bug fixing; the complete list of modifications is available on our support portal, where you can download the full “What’s New” version.

This article will briefly present changes made to two main items of this issue: the “Composer setup” and the “Dimensional catalog export”.

Two new options have been added to the Composer setup: the first gives now the possibility to use values of the “mechanical code” and the “mechanical code description” fields as a description for the ‘mark’ field. With the second new option Users are given the chance to use the content of the “Equipment collection group” and of the “Equipment collection type” fields in the following contexts: Component custom description, Component custom description 2-5, Custom code 2-5, User Component Description, User componentT code.

Another important modification relates to the export of the Dimensional Catalog to Elena. In this release the function has been moved into the “dimensional catalog export” of the “dimensional catalog” module. Two settings have been created to manage the operations included in the ‘Export to Elena’ function of the ‘import/export’: “Export Elena tables” and “Elena direct”.

The first option, “Export Elena tables”, enables the export for Elena of tables which are exported to Drie; by enabling the “Elena direct” option, instead, the export will create text files directly into the default export folder of the application.
The export function has been modified as follows:

  • the exported data are related to the selected Piping Class components;
  • the ‘GasketObjects.csv’ file has been added and it lists the ‘Gasket’ objects;
  • the ‘BranchObjects.csv’ file has been added: it includes the list of the branch objects contained in the new “Branch List” table.

Moreover a new “Project/export/Branch list” form has been added, giving the chance to insert in it some particular branch objects which can be used for the export of the “BranchObjects.csv” table to Elena application.

Get the full update details by logging into our support portal and download our last Puma5 “What’s New”.

Puma5: new update!

Tuesday, April 16th, 2013

Release 2.5 patch 8 build 0

CLA released a bunch of improvements to Puma5 software last Thursday, 11th April 2013; keep on reading to find out what’s new with the software or log on to our Support Portal to download the technical specification.
These last changes refer to 4 main topics:
  • Composer and component catalogue
  • bug fixing
  • export to Elena
  • Material Requisition.
Composer and component catalogue

First of all, two new “composer sequence number (decimal)” and “composer sequence number (hexadecimal)” fields have been added to represent the “mark” code. These values are progressive number, independent from the project code, associated with each component when using the “component catalog upgrading” function.
Furthermore, Users can now select a new type of report, thanks to the “report type” control. These are the kind of reports you can choose from:
  • Type 1 (the report already existing in Puma5): data are grouped according to the operation type and to the piping class; they are organized per revision.
  • Type 2 (the new default report): data are grouped according to the piping class and they are organized per revision and operation type.
Bug fixing
The first problem solved is the error that would come up if, during the insertion of a counting, the selected line had no piping class code.
The other bug regarded the warning alerting Users about the corrosion thicknesses; it read: “There are 0 missing thicknesses into ‘corrosion allowance by project’ table”.

Export to Elena
Two modifications have been made to the data export to Elena:
  • the “BranchesTables.csv” file has been renamed into “PipeBranch.csv”
  • the total number of holes can now be exported.
Material requisition
The ‘Old’ field has been added to the form to show whether a component is not valid (‘Old’) for all the piping classes it belongs to.
Two new confirmation windows have been created to execute the delete functions. These new elements allow Users to differentiate the permissions to use the main form from the permissions of the two delete functions. When the installation is complete, permissions can be set on these two sheets:
  • “Projects – Material requisitions – Print / Delete – RDAD_Form – RDAD_delMR”
  • “Projects – Material requisitions – Print / Delete – RDAD_Form – RDAD_delRev”.
Did you find this useful? We are waiting for your feedback and… stay updated!