Whats new in the latest 2.

7 release
Gian Mario Tagliaretti June 2014

A new filter has been added in the components form of the piping class, when you
add components in the piping class, the material selection is now limited to the same
material type as specified in the piping class header, you can disable the filter if
needed by pressing the material filter button

The correlation between objects and construction has been added, if correctly
configured it will prevent users to insert into the piping class any wrong combination
of objects and construction, you will find a new tab in the object definition

A new filter has been added in the components form of the piping class, when you
add components in the piping class, the construction selection is now limited to the
combination specified in the object definition, you can disable the filter by pressing on
the By obj filter near the construction field.

A new report has been added, while printing the piping class you can choose to print
the valve datasheets (extended) which also contains the field Equipment collection
note

A new report has been added, while printing the piping class you can choose to print
the piping class detail (extended) which also contains the project tag text, the project
tag field has also been extended to 100 characters

The list of materials associated with a particular construction has been added to the
construction form in the general dictionaries, now its easy to cross-check if the
materials are associated with the correct construction type

A new compatibility view has been added, through this view you can add the
compatibility of the End connections for each Object/Standard pair, this will allow less
errors while creating a piping class, during the compatibility checks functions the
warning number 575 will highlight if a piping class contains a not compatible
combination of attributes.

Its now possible to change the equipment collection type to a datasheet, this was
previously not possible, a new button change has been added to the form.
Warning: If you change the equipment collection type the data detail will be lost.

Its now possible to define default values for location and location type on each area,
during the Take-off level 2 upgrading if components inside an area have the location
or location type attribute different from the default will be highlighted in a new
warning.

10

Directly from the Take-Off input form its now possible to define the process data
while creating new lines

11

Its now possible to use the thickness of components while setting a category of goods
(Material requisition category), the thickness must be entered in millimeters.

12

Its now possible to use set which condition(s) shall be used for tracing calculation, if
more than one condition have the flag set to true, the highest operating temperature
will be used during the tracing generation

13

Its now possible to define a rule to automatically build the line code using the line
parameters, the line code structure can be defined into a new composer context
called Line tag, while adding the line data the line number will be automatically
generated.

14

It is not sufficient to create a Line tag into the composer, the new line tag needs to be
set in the project setup where a new field has been added in this release.

15

The Catref map has been moved from the general section to the project section, this is
very useful in case you are working on another company database and you have to
upload your own Catref map, being on the project section you can now have the
permission to set your own Catrefs

16

Its now possible to set different design conditions on the piping class for different size
ranges, you can still use the old method by setting the design conditions in the default
tab of the design conditions form

17

Its now possible to use the project TAG field (piping class components) in the
composer in order to use it while creating custom codes and descriptions

18

Its now possible to use the Equipment collection long description field in the
composer in order to create custom descriptions.
Warning: If the resulting description will be too long it will be truncated

19

During the component code generation through the composer (like the ENI code) its
possible to avoid the warning for duplicate codes if one of the components is old on
the project catalogue, this will avoid false positives in the warning 625.

20

We have added a new attribute Take-Off sub-project to the objects in the MTO
module, the new attribute should not be confused with the sub-project existing
field which is used to define how to split the Material Requisitions.
A dictionary of Take-Off sub-project can be defined in the project structure menu

21

One of the values can be set at project level as a default for the Take-Off, such as what
happens with the existing object attributes.
The default can be setup directly from the MTO module without switching back and
forth from the piping class module

22

Once the default has been set, in the Take-Off level 1 input this is automatically set on
all the objects added to the Take-Off, of course the default can be changed anytime.

23

The new attribute can be later on used to generate reports from the Take-Off
summaries since its now a field group by and filter in the report generator

24

The new attribute can also be used in the purchase location assignment, making it
useful to assign purchase locations and Material Requisition Sub-projects (as a
consequence).
This new field should be used by who is more comfortable setting the sub-project
prior to generate the Material Take-Off and not later on using the material mechanical
attributes or geographical locations.
Please remember that this is an additional attribute and if you dont wish to use it
Puma5 will work as usual.
The new attribute can also be imported/exported through DRIE

25

Similar to the Take-Off sub-project attribute we have also added a new WBS code to
the isometrics in the MTO module.
A dictionary of WBS codes can be defined in the project structure menu

26

The WBS code is part of the isometric attributes that you can set in the MTO input,
there is no project default for the WBS codes

27

The new attribute can be later on used to generate reports from the Take-Off
summaries since its now a field group by and filter in the report generator.
The new attribute can also be imported/exported through DRIE.

28

29