New release for TMS

November 27th, 2015

The latest release of TMS ( delivers four main new or improved features.
By clicking the “Progress Continuity Check” menu item TMS exports an Excel file with all the Progress Discontinuities detected in the different Progress Distributions; user can then manually edit the wrong Past Actual Progress for each detected discontinuity.

Another big step forward has been taken towards a deeper integration with Oracle Primavera P6 and Microsoft Project by importing their XML files regarding the Main Weighting Structure and the Schedule Data directly into TMS. Of course, this will save time and prevent errors by defining values only once in your scheduling software and then using them directly in TMS. How to export XML files, how to import them into TMS, the data needed and the different import options are described in detail in the PDF presentation available here.
Lastly, the multiple chart is now available for printing also 3 or 5 charts in the same page, adding a new choice besides the 2, 4 and 6-chart printout.

Have a look at our presentation and see in detail how TMS can help you with a flawless planning!

TMS in the media

November 26th, 2015

Here is the presentation of our TMS software that was published in the September/October issue of ANIMP magazine:

Puma5 upgrades to version 2.9

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:

The Missing Link in Project Management

July 9th, 2015

Last week CLA flew back to Singapore to co-host a Free Technology Sharing Seminar together with TDS Engr Solutions Pte Ltd, who is CLA’s dealer in Singapore, Indonesia, Philippines, Malaysia, Vietnam, Thailand, Brunei, Myanmar, Laos, Cambodia, East Timor. The seminar was named “The Missing Link in Project Management” and it focused on filling the gap between simple Excel reports and document control software used to monitor a project progress, which is troublesome and inefficient sometimes.

The solution is easy: TMS – Technical Monitoring System. During the seminar some of the key features, such as weighting structures and multiple user defined hierarchy were introduced. Various proven methods to view and automate the generation of meaningful project information in a variety of graphs and reports were demonstrated.


The meeting ended with a Q&A session where Engineering Managers, Planners, Project Engineers and Document Controllers shared practical engineering experience with all participants.

New release for Puma5 (2.8)

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

New release for ELENA Server and ELENA Web Client

July 2nd, 2015

ELENA has reached the release No. 01.400.00.00, bringing you something new both for the Server and the Web Client module.

For ELENA server, we would like to focus on the new Formula Interpreter, an implementation that is available for all the plugins. The Formula Interpreter gives you the possibility of executing formulas on the input files and on the files generated in output. It is an expression interpreter that can be configured and used whenever mathematical calculations need to be done, values need to be added or modified in columns of the input and output files and operations need to be carried out on strings. To use the Interpreter, a new configuration file must be set,  rule_formulas.xml, which is valid for all plugins.

Formulas applied on input files can add new columns to input records at runtime; while formulas applied on output files cannot add new columns but only set or modify values in columns which have already been defined in the cata_headers.xml and spec_headers.xml configuration files.

It is available for download from our support portal a detailed document with examples, operators, functions and constants list that can be used for the MATH instruction.

In ELENA Web Client a new panel has been added to the Builder page; here the following information can be read:

  • user that has executed the Builder
  • processing time
  • result of the processing
  • comments entered by the user relating to the execution
  • configuration sets
  • input files
  • execution mode of the Builder

The implementation of this new function implied some modifications: the new “Output” tab has been added in the Builder page. Here a table shows the history of Builder launches with relevant information. A text box has been created to allow User to insert comments relating to the elaboration launch. Due to this, the creation logic of the history packets (zip files) of the configurations and the inputs has been varied: now the content of the history packet refers to the latest files loaded.

This new function can be enabled only on new projects by setting a parameter as described in the “Modifications to the configuration files” paragraph of the document available on our support portal.

New release of TMS

May 19th, 2015

TMS, Technical Monitoring System, has reached the release No. Many processes have been optimized: for example, deleting a TMS project and a subproject, removing the items from the “C3 Item Quantites” form, the “Project Workclass Structure” and “Project Workclass Progress” can be now executed faster.

A new command, “Main Project Settings“, has been added in the main TMS form to configure parameters for the current project.

Upon the creation of a new TMS project a folder with the same name of the project itself is created in the main folder together with its subfolders (Import specs, IO, Reports, Templates). When a TMS project is loaded after a Restore or Copy command, the files related to that project are automatically copied in these subfolders.

Batch Reports” is also a new command that has been added in this release to access the form displaying all batch reports regarding the current TMS project. Here, a batch report can be inserted, removed or modified.

The “Run batch” command runs the report batch showing the operations that are being performed in background; the process can be interrupted at any time by pressing the “Abort” button.

Another important implementation that we like to share is the possibility to zip automatically the reports of each batch (created in Excel and/or in PDF format) and save them in a user defined folder.
PDF’s are created automatically via Excel or with PDF Factory Virtual Printer.

For detailed information, please log into our support portal and read the latest What’s New document. A slide presentation is available as well.

Database Manager improvement for the #Plant suite

May 15th, 2015

The administration console of the #Plant suite, Database Manager, has been improved: the visualization and search of Entry Points is now more organic and intuitive. The Entry Point list is presented grouped by roles, contexts (General, project or Utility) and position within the product menu.

The new features of this form include “Excel like” filters, multiple sorts and groupings.

For more details, see the Database Manager manual for the version of the application, available for download by logging into our support portal.

Publisher, a new function for Spider

May 12th, 2015

A new function, Spider Publisher, has been implemented to create reports autonomously by extracting data that are common to all Spider projects, belonging to revisions of the datasheet. These data are extracted from a pre-defined database and they are set inside the Spider Configurator. Database tables, corresponding to the sheets that are to be exported, are created with a structure having a row for each item and a column for each item property (and some fixed columns for the project name and ID, document, revision, etc.).

Data are published within Spider section dedicated to datasheet revisions. After the publication, data can be examined inside the database.

By executing the ‘Publish to database’ command a table is created inside the destination schema and data of the current revision are published. If the table is already existing – therefore from the second publication onwards – datasheet data relating to the current revision are appended to data already existing in the table. In case of configuration modifications (adding, renaming or deleting fields), the existing table gets updated and the new requested data are appended; old data are never deleted.

Spider Publisher is part of the release No. of Spider and of the release No. of Spider Configurator. These releases include some bug fixing and other implementations, whose full list can be found in the latest What’s New, available for download by logging into our support portal.

New release available for Welding Book

May 8th, 2015

Welding Book has reached the release number, bringing you some brand new features. Let’s see in detail…

When a project has subcontractors, Welding Book now separates the activities regarding the different subcontractors associating them with the jobs they are assigned (that is, giving them their “work package“). For this reason, a registry has been added for each subcontractor to be filled in with all relevant information, together with the work package. A separate file can be exported for each subcontractor.

By accessing the ‘Project Setup’/'Options’ form of the single project a new field, “real sheet“, can be enabled. When active, the real sheet field indicates the precise position of the spool within the pages generated by the CAD modeler (for example, page 2), and not referring to the one-page document generated by the material management system.

Another important implementation is represented by the new import method. Welding Book used to import data from a single file, but user can now import data from different dictionaries (Material types, Joint types, Diameters, etc.) belonging to Access or Excel files.

As usual, bug fixing and minor implementations are part of this release. To find out more, log into our support portal and download the latest What’s new document.