Archive for the ‘#Plant’ Category

New features for TMS

Thursday, December 21st, 2017

Our Technical Monitoring System has now reached the release No., meaning new features and many improvements. We would like to recap a few of them here.
New options have been added in the “Quantity Production Chart” report: it is now possible to represent a specific time window in the Data Table; also, you can make the Chart start after an “X” number of periods following its actual beginning.

A new command – “Get Missing Dates from P6” – has been added into the “Work Class Progress” context: it allows to retrieve the Actual dates of each Deliverable automatically from Primavera but it also prevents the manual input of Actual dates in case the progress cumulated at the date of each deliverable is inserted massively (for the first time). This new command and the existing “Get Missing Progress from P6″ command guarantee a complete reconstruction of the history, which has not been archived yet, in coherence with the Schedule.

Not only fresh stuff, but also improvement of the existing lot…
A better readability has been given to the “OTP Report“: two separate columns now show the “Milestone Status Index” calculation and the “OTP Index” calculation.

The algorithm calculating the automatic distribution of the Progress Actual between two non-consecutive Updates has been improved, making it homogeneous in all “Import Schedule Data” contexts (Import XML and Import XLS, both for Primavera and MS Project).
Last but not least, the “Out of Range” dates check, performed during the Import Schedule Data phase, has been improved with the specific indication of the activities involved in the “Inconsistency Check” report.
For a complete overview and all the technical details, log in our Customer Care portal and download the latest What’s New document.

Meet Spider ‘Reverse’

Monday, November 30th, 2015

Spider Reverse is the core of the news for the latest release of Spider, belonging to #Plant version
Starting from a configuration already existing, Spider Reverse allows the automatic generation of configuration files; this function is particularly useful when important modifications need to be applied to the configuration, without using the interactive functions of Spider Configurator.

The whole process for the massive modification of the configuration is performed in three steps:

  • execution of the “reverse” of Spider current configuration to extract Excel configuration files;
  • modification of the files generated at the previous step;
  • loading of modified configuration files, by using the “Loader” function.

Data requested to perform this process are only two: the path to the directory where the ‘Reverse’ folder is located (the configuration files are generated and saved here) and the colour palette to be used for the template colouring (each type of cell will have its own colour).
For more details on Spider Reverse, please check our documentation available for download in our support portal.

New release for TMS

Friday, 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

Thursday, November 26th, 2015

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

The Missing Link in Project Management

Thursday, 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 of TMS

Tuesday, 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

Friday, 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

Tuesday, 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

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

New releases of Spider and SpiderConfigurator

Wednesday, November 26th, 2014


Brand new releases of Spider ( and of SpiderConfigurator ( are now available for download from our support portal. Log in or register at and get your copy!

Many features have been implemented to make Microsoft Excel users even more comfortable with Spider, by adding Excel-like filters on GRID documents, by hiding or displaying sheet of a Spider document just like Excel does… and this is to name a few.

New tools have been added for Administrators: they can define a structured procedure for issuing a revision of one or more types of datasheet, setting the status (Prepared, Checked, Approved etc.), the sequence and roles of the users who have the right to make the acceptance workflow advance or block the revision itself.



What else? Many many more… for example, Spider document tree now displays full or empty folders depending on documents being in the folder or not.



Text cells can now pick pre-defined values from a “Suggestion list”, which can be later modified manually. On these cells, the tooltip displays the associated list name; by right-clicking and selecting “Suggestion list…” (also by pressing Alt + Arrow down) a selection window is shown, similar to the Global list cells window. A suggestion list for a particular cell can be set in SpiderConfigurator.



Formula results of an Excel sheet can now be saved in the database history and therefore they can also be published in the relevant documents of the data workflow and they will be available for calculation in plugins and report creation.

A format check is performed on dates and numbers: when these data are pasted and Spider cannot recognize the original format, a pop-up asks to insert the date format or the decimal separator in order to read the copy & paste input. This setting is kept for the whole Spider session but it can be modified in the menu command Edit → Number and date format.



Speaking of date format, also SpiderConfigurator has some check performed when converting a text format into date format; slightly different rules apply for Oracle, SqlServer and Postgres (see the full “What’s new” document for more details).

Attribute domains can now be displayed and changed in the “Modify cell” form.



Find out the rest of implementations, new features and bug fixing in the full “What’s new” document, available from our support portal (