Puma5 Elena Cosmo5 Epc
Puma5 Elena Cosmo5 Epc
Puma5 Elena Cosmo5 Epc
Page 1 of 16
PUMA5 .................................................................................................................................................... 3
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
2.
ELENA ...................................................................................................................................................... 9
3.
COSMO5 ................................................................................................................................................ 12
3.1
3.2
3.3
Page 2 of 16
1. PUMA5
PUMA5 is a software for the management of piping bulk materials. This application is designed for
piping departments in EPC, chemical, petrochemical, pharmaceutical, thermal plant power
generation and similar companies.
This application solves the problems related to the development of the following activities:
Process data (fluid list, line list)
Piping classes
Piping material take-off
Material requisitions
Welding list
Weight calculation
Insulation and painting calculation
Mechanical tests
PUMA5 is provided with starting databases which include:
Piping components
Materials
Engineering practice and standards
Tables with allowable stresses from ANSI B31.3
Weights
Stud, bolt and nut dimensions list
Painting and insulation surface list
Configurations for exporting piping classes to various 3D CAD systems
These databases usually cover 90%-95% of the needs of a piping department. In fact, only minor
modifications are requested to new clients in order to start loading piping specifications. This
directly translates in reduced start-up time, which is now measured in weeks and not in months.
PUMA5 is not designed for the management of purchasing, expediting, logistics and all other
activities which are downstream from piping department. However, we do have an application for
the management of warehouses on construction sites (COSMO5).
PUMA5 is organized in modules, most of which can be purchased separately. For relations between
modules, see the diagram here below and following you will find the modules descriptions.
Page 3 of 16
Page 4 of 16
Page 5 of 16
Surplus Tables: The user can create and apply his own surplus tables according to his project
requirements. These tables will automatically increase the quantities of the calculated materials in
order to balance the construction and assembly scraps.
Bill of Materials List: From the Bill of Materials List the user can automatically obtain the
documents for: site assembly weights (prefabrication material), welding quantities, construction,
component traceability and historical data for planning and management control. All these
documents are essential for a correct management of the piping materials. The user can set filters
and printing form.
Shop/Field Fabrication: According to his own project requirements the user can define his own
divisions between prefabrication and assembly materials and obtain the relative documents for a
site and workshop check.
Subprojects and purchase locations: PUMA5 can manage subprojects with different purchase
locations.
Automatic assignments: Rules for automatic assignments of attributes can be easily implemented
in PUMA5, for example the distribution of materials between shop/field.
1.4 PROCESS
Fluids List: This project document describes the process fluids in their phases, indicating the
maximum conditions of pressure, temperature and the main characteristics of the lines (basic
material, rating and flange coupling).
Lines List: This project document describes the conditions of pressure and temperature, the main
characteristics of the lines (basic material, rating and flange coupling). Design conditions in the
project piping classes are checked on the basis of this document.
Fluids List and Lines List Checks: The application checks the design conditions present in the fluids
list and the piping classes, and between the lines list and the piping classes. The check of the design
conditions is performed by the application between the fluids list and piping classes, and between
the lines list and piping classes.
Page 6 of 16
the component code does not change from project to project. Until recently there was not
much request for universal codification, but as EPC started to use ERP systems (SAP, Baan,
J.D. Edwards etc.) the need for it has increased (otherwise, after a few projects, the ERP
system would explode due to the enormous number of components; and also statistics,
price lists maintenance etc. are needed).
There are three methods to implement Universal codification in PUMA5:
a) A completely structured code; it is generally a 14-18 characters long code in which
each position has a defined code representing the specific characteristics
of the components. This is the classical way, but it has two main disadvantages:
1. all combinations of the components and their attributes shall be foreseen;
2. a long time is required to implement it.
Customer shall develop the codification, then the organization of components in PUMA5
database is adjusted accordingly and it gets implemented in Composer.
b) Mixed system, the combination of a structured code and a sequentially generated
number. In this case one part of the code is structured, based on main attributes like
component code, diameters, type of material etc. and the second part is a sequentially
generated number. These are custom-made modules, extra to PUMA5 at a relatively low
cost. This solution is not as elegant as method a), but implementation times are
practically zero and no investment is required in codification development.
It is used by most of our Customers needing universal codification.
c) For Customers already having codification and associated descriptions loaded in
ERP, PUMA5 exports descriptions (with quantities) matching ERP descriptions. The
advantage is that there is no overhead in PUMA5 and management is simplified; however,
there are discrepancies in codes between various documents, i.e. orders and isometrics
have different codes, such custom modules have been created for Customers like Saipem
and Technip.
Based on our experience, solution b) is the simplest way to go because of the easy setup,
the low cost (additional modules customized according to Customers needs generally have
a low cost, sometimes being free) and the low additional overhead in PUMA5.
Page 8 of 16
2. ELENA
ELENA is a software system which allows the integration of heterogeneous 3D CAD systems with
heterogeneous material management systems.
It is a platform based on plugins: each plugin contains the specific requirements for each CAD and
for each material management software.
ELENA has been designed to work with any material management system. For example, all the
supported plugins must be configured by means of a series of Excel workbooks that contain the
mappings between the material management system (for example our PUMA5) and the relevant
CAD definitions, here below a simple schema which represents the plugin based system.
The structure and layout of the various outputs to be produced by means of templates are properly
formatted for the production of the specific CAD needs. During its operation the program reads the
configuration workbooks, receives as input a series of neutral files in CSV format (from the material
management system), and always outputs a series of Excel workbooks in XML format, the catalog
and the piping classes will be then loaded into the CAD system by means of their own loader.
In the event that the material management system, to which the ELENA plugin is wished to be
connected, does not manage the dimensional data of the piping components, ELENA is also capable
of manage a dimensional catalog. ELENA envisages that every project may have its own
configuration files or it is referred to general configuration files. It is also possible to parametrically
define the relevant attributes to configure the mappings between the material management system
and a supported 3D model, and the relevant attributes that determine the search keys in the
dimensional catalog.
Page 9 of 16
After the first loading of the output files, the CAD system usually requires subsequent loadings to be
loaded by difference. At each new generation, the interface takes care of managing the new
records, the modified records and the records to be deleted, generating the output files for each of
the cases required by the loading program.
ELENA has been built with the following strong open source technologies: business logics developed
with the Python language, Berkeley DB is the database used. The latter is an embedded database
alternative to relational databases which is extremely robust, high performing and scalable;
furthermore, it does not need any "server side" service and needs no administration services.
The database is organized by project and against every new issue, the information is memorized in a
separate Berkeley DB. This approach allows the facilitation of user management and, in the event
that it is wished to eliminate an issue, it is sufficient to cancel the related Berkeley DB file.
The interface can run with the Windows 2000, Windows XP Professional, Windows Vista, Windows 7
and all operating systems that support Python 2.5 and later.
Page 10 of 16
ELENA can be used as a local installation for simple configurations, e.g. installed on a desktop or for
Companies that have multiple offices located in different cities or even different Continents, ELENA
can be installed in a client/server configuration where the configuration and dimensional files are
located in the server side (master) and the clients will communicate through the XML-RPC protocol
and get the results from the server.
Page 11 of 16
3. COSMO5
COSMO5 is the software for managing the yard warehouse and the activities of prefabrication and
assembly. Information regarding the components features and their location on the lines are
extracted from PUMA5 through the import functions.
These data, together with information coming from the Purchasing dept. (i.e. request of offer, P.O.,
packing slip) and with data regarding the available material in stock, allow to analyse piping lines
feasibility.
Note:
This application can work also independently from PUMA5; in this case, requested data can
be inserted manually or they can be imported from an .xls/txt file duly structured.
Page 12 of 16
3.2
DOCUMENT MANAGEMENT
COSMO5 can manage the documents regarding the lifecycle of the piping materials, making it
possible to check the purchasing situation; this ensures the traceability and status check of the
purchasing order for each component during its whole lifecycle (quantity in Take-Off, requested
quantity and ordered quantity, foreseen quantity to be delivered, delivered quantity, etc.).
Page 13 of 16
The Activities can be used in more than a Workstep (or activities collection); the Workclasses must
be configured in the following menu:
During the configuration of Workclasses, besides listing how these activities are made, the relative
weight of each activity must be given; the total of the activities shall add up to 100%.
Page 14 of 16
In turn Workstep will be collected in the workflow, representing the complete cycle in which the
materials are involved; the following example is an erection and insulation workflow, composed by
2 worksteps.
Page 15 of 16
The materials (in this case the spools) will be associated with the workflow and their progress will be
monitored until the end of the construction; the following form shows the assignment of the spools
to the Workflow, after all the settings are completed, the progress of individual activities will be
monitored in the period established by each client; the period is usually weekly but the application
has no limits, a complete reporting via a convenient report generator completes the application.
Page 16 of 16