TECHNICAL INFORMATION

ITEMLIST
CONSTRUCTION ITEM LIST MANAGEMENT

(User Manual)

INT.GC.PRM.4526

Rev. 0

September 2008

Form code: MDT.GG.QUA.0511 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 2 (49)

CONTENTS

1 INTRODUCTION________________________________________________________________ 3
1.1 SICON _____________________________________________________________________ 3
1.2 ITEM LIST – Construction Item List Management ___________________________________ 9

2 DATA MANAGEMENT __________________________________________________________ 10

2.1 Item List Management _______________________________________________________ 10
2.2 Contract Assignment ________________________________________________________ 26

3 REPORTS ____________________________________________________________________ 27
3.1 Defined Items ______________________________________________________________ 27
3.2 Planned Item ______________________________________________________________ 29
3.3 Differences on Item Systems Vs Item list_________________________________________ 30

4 UTILITY _____________________________________________________________________ 31
4.1 Import____________________________________________________________________ 31
4.2 Export ____________________________________________________________________ 42
4.3 Rename Items _____________________________________________________________ 48

5 HELP________________________________________________________________________ 49
5.1 About ____________________________________________________________________ 49
5.2 Help _____________________________________________________________________ 49

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 3 (49)

11 IIN
NTTRRO
ODDU
UCCTTIIO
ONN
11..11 SSIICCO
ONN

SICON (Sistema Informatico della CONstruzione – Italian acronym for Construction Data Processing
System) is software intended for the management and control of all phases of specific on-site
construction activities. The areas involved are the following:

a. planning and monitoring

b. materials (warehouse & piping materials)
c. certification and quality control
d. cost control and works accounting

The SICON main menu is shown in Fig.1.1

Fig. 1.1

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 4 (49)

Clicking on the grey button with the mouse gives access to the corresponding SICON module (see Fig.
1.2)

Fig. 1.2

Any communications from the System Administrator are displayed in the “Messages” box (Fig.1.3).
Using the arrow buttons at the bottom, it is possible to move to the first, previous, next and last
messages respectively. The “Refresh” button is used to update the message list.

Fig. 1.3

To end the program, click of the “Exit from SICON” button (Fig. 1.4).

Fig. 1.4

Each section of the various SICON modules has a work menu as shown in Fig. 1.5. This menu bar
contains links to all of the operations that can be performed on the databases.

Fig. 1.5

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 5 (49)

The specific functions of each button are listed below:

Action
Æ Save: saves the changes that have been made.
Æ Clear All: deletes all fields of all tables.
Æ Print: provides access to print functions.
Æ Exit: exit section.

Edit
Æ Cut: cut the selected part.
Æ Copy: copy the selected part.
Æ Paste: paste a previously cut or copied part.
Æ Edit: allows changes to be made to the selected field.
Æ Display List: opens a pop-up menu that allows certain fields to be filled in by selecting an item
entered in another section.

Query
Æ Enter: allows data to be entered for performing a search.
Æ Execute: executes the search.
Æ Cancel: cancels the search.
Æ Last Criteria: inserts the last search parameters entered.
Æ Count Hits: shows the number of records found.
Æ Fetch Next Set: displays the next set.

Block
Æ Previous: display previous block.
Æ Next: display next block.
Æ Clear: clear the fields in the block.

Record
Æ Previous: move cursor to previous record.
Æ Next: move cursor to next record.
Æ Scroll Up: scroll up the record list.
Æ Scroll Down: scroll down the record list.
Æ Insert: insert a new record.
Æ Remove: remove a record.
Æ Block: block a record against changes.
Æ Duplicate: duplicate a record.
Æ Clear: clear a record.

Field
Æ Previous: move cursor to previous field.
Æ Next: move cursor to next field.
Æ Clear: clear the field.
Æ Duplicate: duplicate the field.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 6 (49)

Help
Æ Help: shows specifications of individual fields (number of characters, size, etc.)
Æ Keys: opens a window containing the shortcut keys.
Æ Display Error: opens a window explaining the last error message.

Window
Æ Cascade: arrange open windows in a cascade.
Æ Tile Horizontally: arrange open windows horizontally.
Æ Tile Vertically: arrange open windows vertically.

Certain buttons are present on the icon menu that function as shortcuts for the more common
operations:

Save

Print

Exit

Cut

Copy

Paste

Enter Query

Execute Query

Cancel Query

Previous Block

Previous Record

Next Record
Next Block

Insert Record

Remove Record

Lock Record

Help

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 7 (49)

Work windows can have a single screen form or be divided into tabbed forms as in Fig. 1.6. To pass
from one form to another it is necessary to click on the respective tab with the mouse.

Fig. 1.6

When compiling the databases, sections might be found where it is necessary to choose from a list of
available options. The option boxes can have various forms, as shown below:

• Drop-down menu: allows the opening and scrolling of a list of possible choices. Only one choice is
allowed.

• Pop-up menu: these are menus that are displayed on the screen by double-clicking on a field or
pressing the F9 key. In some sections, it is also possible to access these menus by clicking on the
button that might be located next to certain fields. The menu shows a list of possible choices
and allows just one choice to be made.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 8 (49)

• Checkbox: these are boxes that may or may not contain a “tick mark”. They serve to indicate the
presence or absence of a given property. They are not mutually exclusive and it is not compulsory
for at least one them to be active in a group. In consequence, they allow multiple choices.

• Radio button: these are “selection indicators”. They indicate which selection has been made
between different possibilities. They are mutually exclusive.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 9 (49)

There are three types of field in the various SICON modules that should filled in manually:
• Numeric fields: only numeric characters can be entered.
• Alphabetic fields: only alphabetic characters can be entered.
• Alphanumeric fields: both numeric and alphabetic characters are allowed.

Each field has a preset character limit that will be indicated each time.

11..22 IITTEEM
M LLIISSTT –– CCoonnssttrruuccttiioonn IItteem
m LLiisstt M
Maannaaggeem
meenntt

The function of the ITEMLIST module consists in making the list of TAGs and respective attributes
available to the various SICON modules.

The ITEMLIST main menu is shown below in Figure 1.7.

Fig.1.7

Exit - Allows the ITEMLIST module to be exited. The user is returned to the SICON main menu. (Fig.
1.1).

Data Management - This section allows the list of TAGs with their respective attributes and the
association with individual contracts and WBS to be entered.

Reports - This section allows the generation of reports on data entered with the application.

Utility - This section contains utilities for importing and exporting item lists.

Help - This section allows the user to display the operating manual of the module being used and the
software version.

Window - This section provides window display management.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 10 (49)

22 DDAATTAA M
MAAN
NAAG
GEEM
MEEN
NTT
The Data Management section is divided into two subsections as shown in Figure 2.1. Each database
will be described individually.

Fig. 2.1

22..11 IItteem
m LLiisstt M
Maannaaggeem
meenntt

This section manages the Item List by job and site.

The job and site of interest can be selected in the first section of the screen form. (Fig. 2.2)

Fig. 2.2

The planning section of the Item List is subdivided into three parts: System, Packages and Items.
At a general level, the value lists that take data from GENANAG regarding item types, work phases,
compositions and rules are filtered according to the value in the obsolete field of the reference job.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 11 (49)

22..11..11 SSyysstteem
m
Systems and Subsystems for the relevant jobs and sites can be created in this subsection. (Fig. 2.3)

Fig. 2.3

Systems
System - The codes identifying the systems should be inserted in this column.
This field is alphanumeric and has a maximum length of 9 characters.

Description - The descriptions of the systems should be inserted in this column.

This field is alphanumeric and has a maximum length of 50 characters.

Ready By - The date by when the system must be ready should be inserted in this column.
The date should be inserted in the format dd-mm-yyyy

Sub Systems
Subsystem - The codes identifying the subsystem should be inserted in this column.
This field is alphanumeric and has a maximum length of 9 characters.

Subsystem Description - Descriptions of the subsystems should be inserted in this column.

This field is alphanumeric and has a maximum length of 50 characters.

Ready By - The date by when the subsystem must be ready should be inserted in this column.
The date should be inserted in the format dd-mm-yyyy

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 12 (49)

22..11..22 PPaacckkaaggeess
The various item packages can be created in this subsection. (Fig. 2.4)

Fig. 2.4

Package - The codes identifying Packages should be inserted in this column.

This field is alphanumeric and has a maximum length of 16 characters.

Description - The descriptions of the Packages should be inserted in this column.

This field is alphanumeric and has a maximum length of 50 characters.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 13 (49)

22..11..33 IItteem
mss
The items that form the Systems, Subsystems and Packages are defined in this subsection. (Fig. 2.5)

Fig. 2.5

Items
The screen form is subdivided into a number of parts. The types of item and their descriptions can be
defined in the first part. (Fig. 2.6)

Fig. 2.6

Item - The codes of the items should be inserted in this column.

This field is alphanumeric and has a maximum length of 16 characters.

Item Description - The descriptions of the items should be inserted in this column.
This field is alphanumeric and has a maximum length of 50 characters.

Main item - The job and site main item code that defines the item should be inserted in this column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. The
encoding of Main items is made in another section of this screen form.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 14 (49)

Type of Item - The code that defines the type of item should be inserted in this column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ Progress MeasurementÆ Type of Items).

Description - The description of the type of item is automatically displayed in this column.

Code Area - The code that defines the item’s erection area should be inserted in this column. The area
code is defined in COPR.

Area Description - The description of the area is automatically displayed in this column.

SubSystem - The code that defines the subsystem to which the item belongs should be inserted in this
column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
ITEMLISTÆ Data ManagementÆ Item List ManagementÆ Systems)

SubSystem description - The description of the subsystem is automatically displayed in this column.

SubSystem Ready by - The date by when the subsystem must be ready is automatically displayed in
this column.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 15 (49)

Several buttons, each with a specific function, are present on the screen (Fig. 2.7). These are described
in detail below.

Fig. 2.7

Main Item Definition

Clicking on this button opens a window in which it is possible to define the Main items. (Fig. 2.8)

Fig. 2.8

Main Item - The codes that identify the main items should be inserted in this column.
This field is alphanumeric and has a maximum length of 16 characters.

Description - The descriptions of main items should be inserted in this column.

This field is alphanumeric and has a maximum length of 50 characters.

Ready By - The date by when the main item must be ready must be inserted in this column.
The date should be inserted in the format dd-mm-yyyy

U.M. - The unit of measurement associated with the main item should be indicated in this column.
This can be inserted by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ GeneralÆ Unit of Measurement).

Quantity - The quantity related to the main item should be inserted in this column.
This field is numeric and has a maximum length of 40 characters.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 16 (49)

Details
Clicking on this button opens a window in which it is possible to define additional item details. (Fig. 2.9)

Fig. 2.9

Item - The code for the item is displayed in this column.

Length - The length of the item should be inserted in this column.

This field is numeric and has a maximum length of 40 characters.

Width - The width of the item should be inserted in this column.

This field is numeric and has a maximum length of 40 characters.

Height - The height of the item should be indicated in this column.

This field is numeric and has a maximum length of 40 characters.

Diameter - The diameter of the item should be inserted in this column.

This field is numeric and has a maximum length of 40 characters.

Weight - The weight of the item should be inserted in this column.

This field is numeric and has a maximum length of 40 characters.

H/V - With this drop-down menu, it can be indicated whether the item is vertical or horizontal.

Status - With this drop-down menu, the status of the item can be indicated.

F/S - With this drop-down menu, it can be indicated whether the item belongs to foundations or
structures.

Notes - Any notes regarding the item should be inserted in this column.
This field is alphanumeric and has a maximum length of 2000 characters.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 17 (49)

Rename
Clicking on this button gives access to a window in which it is possible to rename the item code. (Fig.
2.10)

Fig. 2.10

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 18 (49)

Export
Clicking on this button gives access to a window in which it is possible to carry out export operations on
the item list in CSV format. (Fig. 2.11)

Fig. 2.11

The CSV export file is structured as follows:

Description Data Format Size

1 Job Number Alphanumeric Max 6
2 Site Alphanumeric Max 4
3 Item/Object Alphanumeric Max 16
4 Description Alphanumeric Max 50
5 Main Item Alphanumeric Max 16
6 Type of Item Alphanumeric Max 6
7 WBS Area Alphanumeric Max 4
8 Sub System Alphanumeric Max 9
9 Length Numeric 3 decimals
10 Width Numeric 3 decimals
11 Height Numeric 3 decimals
12 Diameter Numeric 3 decimals
13 Weight Numeric 3 decimals
14 Horizontal / Vertical (H/V) Alphanumeric Max 1
15 New / Existing (N/E) Alphanumeric Max 1
16 Placement Found./Structure Alphanumeric Max 1
17 Note Alphanumeric Max 80

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 19 (49)

18 Work Phase Alphanumeric Max 6

19 Subcontractor Alphanumeric Max 6
20 To be used by PROM Alphanumeric Max 1
21 Composition Alphanumeric Max 15
22 Unit of Measurement Alphanumeric Max 3
23 Quantity / Weight as per u.o.m Numeric 3 decimals
24 Package Alphanumeric Max 16
25 Available From Date
26 Ready By Date
27 Duration Numeric 0 decimals
28 To be used by PCOS Alphanumeric Max 1
29 Rule Alphanumeric Max 10

Six parameters can be use to filter export output:

Type of Item - In this field, it is possible to filter exported data according to type of item. If no selection
is made for this field, the system will export the data for all item types.

Area - In this field, it is possible to filter exported data according to type of area. If no selection is made
for this field, the system will export the data for all areas.

SubSystem - In this field, it is possible to filter exported data according to subsystem. If no selection is
made for this field, the system will export the data for all subsystems.

Type of work - In this field, it is possible to filter exported data according to type of work. If no
selection is made for this field, the system will export the data for all types of work.

Contractor - In this field, it is possible to filter exported data according to contractor. If no selection is
made for this field, the system will export the data for all contractors.

Package - In this field, it is possible to filter exported data according to package. If no selection is made
for this field, the system will export the data for all packages.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 20 (49)

An example of an export file is shown in Fig. 2.12

Fig. 2.12

Import
Clicking on this button gives access to a window in which it is possible to carry out import operations.
(Fig. 2.13)

Fig. 2.13

The data to be imported must be in CSV format and be structured exactly as shown in the layout
below:

Description Data Format Size

1 Job Number Alphanumeric Max 6
2 Site Alphanumeric Max 4

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 21 (49)

3 Item / Object Alphanumeric Max 16

4 Description Alphanumeric Max 50
5 Main Item Alphanumeric Max 16
6 Type of Item Alphanumeric Max 6
7 WBS Area Alphanumeric Max 4
8 Sub System Alphanumeric Max 9
9 Length Numeric 3 decimals
10 Width Numeric 3 decimals
11 Height Numeric 3 decimals
12 Diameter Numeric 3 decimals
13 Weight Numeric 3 decimals
14 Horizontal / Vertical (H/V) Alphanumeric Max 1
15 New / Existing (N/E) Alphanumeric Max 1
16 Placement Found./Structure Alphanumeric Max 1
17 Note Alphanumeric Max 80
18 Work Phase Alphanumeric Max 6
19 Subcontractor Alphanumeric Max 6
20 To be used by PROM Alphanumeric Max 1
21 Composition Alphanumeric Max 15
22 Unit of Measurement Alphanumeric Max 3
23 Quantity / Weight as per u.o.m Numeric 3 decimals
24 Package Alphanumeric Max 16
25 Available From Date
26 Ready By Date
27 Duration Numeric 0 decimals
28 To be used by PCOS Alphanumeric Max 1
29 Rule Alphanumeric Max 10

Character-format data fields must be prefixed with an asterisk “*”.

It is obligatory for the following fields to be specified in the import file:

• Job No.
• Site
• Item/Object
• Type of Item

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 22 (49)

Copy Item
Clicking on this button gives access to a window in which it is possible to duplicate a record. All of the
data in the record is copied except for the item code. The new item code should be entered in the field
in window. (Fig. 2.14)

Fig. 2.14

Planned Items
In this part, it is possible to define the type of work, ITS classification, the contractor responsible and
rules regarding the item. (Fig. 2.15)

Fig. 2.15

Phase of work - The code identifying the work phase should be inserted in this column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ QA/QCÆ Phases)

Phase of work description - The description of the work phase is automatically displayed in this
column.

Contractor - The code for the contractor should be inserted in this column.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 23 (49)

This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ Breakdown StructureÆ Contractors)

Contractor Description - The description of the contractor is automatically displayed in this column.

Used by Prom - This checkbox allows indicating whether the item is used by the PROM module.

Composition - The code of the composition that defines the item should be inserted in this column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ Progress MeasurementÆ Compositions)
The compositions can be of two types:
 defined in GENANAG
 customized for the project and defined in PROM

Composition Description - The description of the composition is automatically displayed in this column.

U.M. - The unit of measurement associated with the composition should be indicated in this column.
This can be inserted by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ GeneralÆ Unit of Measurement).

Quantity - The quantity regarding the item should be inserted in this column.
This field is numeric and has a maximum length of 40 characters.

Used by PCOS - This checkbox allows indicating whether the item is used by the PCOS module.

ITP (Rule) - The related ITP (Inspection Test Protocol) or rule is linked to each phase in this column.
Each of these is defined in GENANAG, or in PCOS if customized for the project. Selection is made via a
predefined table.

ITP Description - The description of the ITP is automatically displayed in this column.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 24 (49)

Two buttons are displayed on the screen, each with a specific function (Fig. 2.16). These are described
in detail below.

Fig. 2.16

Item Details
Clicking on this button gives access to a window in which it is possible to insert specification details
regarding work phases, packages, etc. (Fig. 2.17)

Fig. 2.17

Item - The item code is displayed in this column.

Phase of work - The code identifying the work phase should be inserted in this column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
GENANAGÆ QA/QCÆ Phases)

Package - The code that defines the package to which the item belongs should be inserted in this
column.
This can be entered by manually typing it in or by selecting it from the relevant pop-up menu. (Path:
ITEMLISTÆ Data ManagementÆ Item List ManagementÆ Packages)

Package Description - The description of the package is automatically displayed in this column.

Available From - The planned date when the phase of work will be available on site is inserted in this
column.
The date should be inserted in the format dd-mm-yyyy.

Ready by - The planned date when the phase of work will be erected on site is inserted in this column
The date should be inserted in the format dd-mm-yyyy.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 25 (49)

Duration - The planned duration of erection of the individual phase of work is inserted in this column.
This field is numeric and has a maximum length of 3 characters.

Drawings
Clicking on this button gives access to a window in which it is possible to link drawings to the phases of
work. (Fig. 2.18)

Fig 2.18

Drawing - The names of the drawings should be inserted in this column.

This field is alphanumeric and has a maximum length of 20 characters.

Rev - The revision numbers of the drawings should be inserted in this column.
This field is alphanumeric and has a maximum length of 5 characters.

Note - Any notes regarding the drawings should be inserted in this column.
This field is alphanumeric and has a maximum length of 2000 characters.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 26 (49)

22..22 CCoonnttrraacctt AAssssiiggnnm

meenntt

Pairing between item phase and contract is performed in this section. (Fig. 2.19)

Fig 2.19

The contractor/contract and Wbs data items are modifiable according to the following rules:
Wbs - always modifiable

Contract/contractor - there are two cases:

 If progress already exists for the item/work phase, it is only permitted to change the contract and
not the contractor, as long as the contract is with the same contractor.
 If there is no progress, then selecting a contract automatically changes the contractor as well.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 27 (49)

33 RREEPPO
ORRTTSS
Reports regarding the Construction Item List can be subdivided into reports for defined items and
planned items.

Fig. 3.1

33..11 DDeeffiinneedd IItteem

mss

In this section, it is possible to generate a report of all items defined in the item list regarding a job and
a site. (Fig. 3.2)

Fig. 3.2

Report data can be filtered according to several parameters:

Type of Item - In this field, it is possible to filter the report according to the type of item. If no selection
is made for this field, the report will include all item types.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 28 (49)

The list is based on the item list regarding the job and the site.

Main Item - In this field, it is possible to filter the report according to Main item. If no selection is made
for this field, the report will include all Main items.
The list is based on the item list regarding the job and the site.

Area - In this field, it is possible to filter the report according to Area. If no selection is made for this
field, the report will include all Areas.
The list is based on the item list regarding the job and the site.

System - In this field, it is possible to filter the report according to System. If no selection is made for
this field, the report will include all Systems.
The list is based on the item list regarding the job and the site.

H/V - In this field, it is possible to filter the report according to item’s vertical or horizontal orientation.
If no selection is made for this field, the report will not consider orientation.
The list is based on the item list regarding the job and the site.

Status - In this field, it is possible to filter the report according to the status of item. If no selection is
made for this field, the report will not consider the status of item.
The list is based on the item list regarding the job and the site.

F/S - In this field, it is possible to filter the report according to where the item belongs. If no selection is
made for this field, the report will not consider this fact.
The list is based on the item list regarding the job and the site.

Order by - With this drop-down menu, it is possible to select the order in which information will be
displayed in the report.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 29 (49)

33..22 PPllaannnneedd IItteem

m

In this section, it is possible to generate a report of all the items planned in the item list regarding a job
and a site. (Fig. 3.3)

Fig. 3.3

Report data can be filtered according to several parameters:

Contractor - In this field, it is possible to filter the report according to contractor. If no selection is
made for this field, the report will include all contractors.
The list is based on the item list regarding the job and the site.

Area - In this field, it is possible to filter the report according to Area. If no selection is made for this
field, the report will include all Areas.
The list is based on the item list regarding the job and the site.

Item type - In this field, it is possible to filter the report according to the type of item. If no selection is
made for this field, the report will include all item types.
The list is based on the item list regarding the job and the site.

Composition - In this field, it is possible to filter the report according to the type of composition. If no
selection is made for this field, the report will include all compositions.
The list is based on the item list regarding the job and the site.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 30 (49)

Rule - In this field, it is possible to filter the report according to the type of rule. If no selection is made
for this field, the report will include all rule types.
The list is based on the item list regarding the job and the site.

Main Item - In this field, it is possible to filter the report according to Main item. If no selection is made
for this field, the report will include all Main items.
The list is based on the item list regarding the job and the site.

System - In this field, it is possible to filter the report according to System. If no selection is made for
this field, the report will include all Systems.
The list is based on the item list regarding the job and the site.

Subsystem - In this field, it is possible to filter the report according to Subsystem. If no selection is
made for this field, the report will include all Subsystems.
The list is based on the item list regarding the job and the site.

Flag by PROM - Via these radio buttons, it is possible to filter the report according to the option set for
the items:
• Yes: the report will only contain items used by PROM.
• No: the report will only contain items not used by PROM.
• All: the report will contain all items.

Flag by PCOS - Via these radio buttons, it is possible to filter the report according to the option set for
the items:
• Yes: the report will only contain items used by PCOS.
• No: the report will only contain items not used by PCOS.
• All: the report will contain all items.

33..33 DDiiffffeerreenncceess oonn IItteem

m SSyysstteem
mss VVss IItteem
m lliisstt

This option allows checking for possible discrepancies between data inserted in the ITEM List
Construction module and the Punch List module and regarding the ITEM – System pairing.

Fig. 3.4

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 31 (49)

44 U
UTTIILLIITTYY
This section is divided as shown in Fig. 4.1

Fig. 4.1

44..11 IIm
mppoorrtt

The Import section is subdivided into five forms. The corresponding utilities enable importing
Drawings, Main Items, Systems, SubSystems and Items using an Excel compatible format. (Fig. 4.2)

Fig. 4.2

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 32 (49)

44..11..11 IIm
mppoorrtt DDrraaw
wiinnggss
This utility enables the importation of drawings associated with Items/Work phases. (Fig. 4.3)

Fig. 4.3

Only Check? - This checkbox allows choosing whether to perform the import or just launch its
simulation:
Flag: simulation
No Flag: import

Show File Structure - This button allows the structure of the import file to be displayed.

Import Drawings - Starts the import operation.

During importation, should the description field contain the word “DELETE”, the drawing is deleted,
subject to checking that has not been referenced by accounts, whether estimated or final balance. If it
is referenced, an error is recorded in the log file. Inserted and/or modified drawings are listed in a log
file.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 33 (49)

44..11..22 IIm
mppoorrtt M
Maaiinn IItteem
mss
This utility enables the importation of Main Items. (Fig. 4.4)

Fig. 4.4

Only Check? - This checkbox allows choosing whether to perform the import or just launch its
simulation:
Flag: simulation
No Flag: import

Show File Structure - This button allows the structure of the import file to be displayed.

Import Main Items - Starts the import operation.

During importation, should the description field contain the word “DELETE”, the Main Item is deleted,
subject to checking that has not been referenced by any Item. If it is referenced, an error is recorded in
the log file.
Inserted and/or modified Main Items are listed in a log file. The unit of measurement must be validated
against the units of measurement table. The quantity must be numeric and in the format 9999999.99

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 34 (49)

44..11..33 IIm
mppoorrtt SSyysstteem
mss
This utility enables the importation of Systems. (Fig. 4.5)

Fig. 4.5

Only Check? - This checkbox allows choosing whether to perform the import or just launch its
simulation:
Flag: simulation
No Flag: import

Show File Structure - This button allows the structure of the import file to be displayed.

Format Date - This drop-down menu allows the data format to be selected.

Import Systems - Starts the import operation.

During importation, should the description field contain the word “DELETE”, the system is deleted,
subject to checking that has not been referenced by any Subsystems. If it is referenced, an error is
recorded in the log file. Inserted and/or modified Systems are listed in a log file.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 35 (49)

44..11..44 IIm
mppoorrtt SSuubbSSyysstteem
mss
This utility enables the importation of Subsystems. (Fig. 4.6)

Fig. 4.6

Only Check? - This checkbox allows choosing whether to perform the import or just launch its
simulation:
Flag: simulation
No Flag: import

Show File Structure - This button allows the structure of the import file to be displayed.

Format Date - This drop-down menu allows the data format to be selected.

Import SubSystems - Starts the import operation.

During importation, should the description field contain the word “DELETE”, the Subsystem is deleted,
subject to checking that has not been referenced by any Items. If it is referenced, an error is recorded
in the log file.
Inserted and/or modified Subsystems are listed in a log file.
It is also checked that the reference System is already present in the database: if not, an error is
recorded on the log file.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 36 (49)

44..11..55 IIm
mppoorrtt IItteem
mss
This utility enables the importation of item list and planned item list data. (Fig. 4.7)

Note: any double-quote characters (") present in the “Item” and “Item description” fields will be substituted
with a space character.

Fig. 4.7

Only Check? - This checkbox allows choosing whether to perform the import or just launch its
simulation:
Flag: simulation
No Flag: import

Item List
Show File Structure - Questo pulsante consente di visualizzare la struttura del file di Import.

Load Item List - Questo pulsante permette di caricare l’Item List

Item List by phase

Show File Structure - Questo pulsante consente di visualizzare la struttura del file di Import.

Load Item List by phase - Questo pulsante permette di caricare l’Item List

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 37 (49)

During the item list import operation (“Load Item List” button), the program checks the existence of
the “key” field, the item. If attribute fields are not edited, the program considers the data already
present on the database as valid and does not overwrite it.
The Job, Site, Item Code and Item Type fields are the only obligatory ones.
Checks are carried out on the lines of data, whether they regard a new insertion or modification to an
existing record:
Job-site: both fields are obligatory and are checked. In addition to their existence, the user must be
enabled for the same job/site.
Item code: if the cell value is null, an error is recorded on the log file and the record discarded. The
field is valid if the code is new or already exists.
Item description: freely specified. If the cell value is null, what is on the DB will be left there.
Main item: controlled field. If the code does not exist, an error is recorded on the log file and the
record discarded. If the cell value is null, the field in the DB will be ignored; what is on the DB will be
left there.
Type of item: controlled and obligatory field. If the value is null or the code non-existent, an error is
recorded on the log file and the record discarded.
The item can be modified if it has no associated phases already present in the DB; if not, an error is
recorded on the log file and the record discarded.
Area: controlled field. If a non-existing code is specified, an error is recorded on the log file and the
record discarded. If the cell value is null, the field in the DB will be ignored; what is on the DB will be
left there.
Subsystem: controlled field. If the code does not exist, an error is recorded on the log file and the
record discarded. If the cell value is null, the field in the DB will be ignored; what is on the DB will be
left there.
Length, Width, Height, Diameter and Weight: these are freely specified fields with control of the
format, which must be numeric: 9999999.99. If the cell value is null, the field in the DB will be ignored;
what is on the DB will be left there.
Horizontal or vertical: controlled field: can be H (horizontal) or V (vertical). If the code is different, an
error is recorded on the log file and the record discarded. If the cell value is null, the field in the DB will
be ignored; what is on the DB will be left there.
Status: controlled field: can be C (CONTROL), E (EXITING), N (NEW) or R (REVAMPING). If the code is
different, an error is recorded on the log file and the record discarded. If the cell value is null, the field
in the DB will be ignored; what is on the DB will be left there.
Foundation or structure: controlled field: can be F (foundation) or S (structure). If the code is different,
an error is recorded on the log file and the record discarded. If the cell value is null, the field in the DB
will be ignored; what is on the DB will be left there.
Notes: freely specified. If the cell value is null, the field in the DB is left null.

During the planned item list import operation (“Load Item List by Phase” button), the program must
check the existence of the “key”, the item. If attribute fields are not edited, the program considers the
data already present on the database as valid and does not overwrite it. If an altered field has already
been used, the program records an error message on the log file. In this specific instance, an error
must be generated if the “Composition” or “ITP” fields are altered whilst already exploded.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 38 (49)

If it is wished to change one of the attribute fields, it is necessary to indicate the work phase involved
in addition to the item. The “Qty” field must be updatable even in cases of exploded composition and
associated progress.
The Job, Site and Item Code fields are the only obligatory ones.
Error message layout: when error messages are generated, the number of the line to which the error
or warning refers to will be added as a prefix.
Item: controlled field. Must be in the Construction Item List table; if the field value is not in the items
database, an error is generated and the record discarded. If the item field is null, the following error
message is generated: “Error at line x: Item code is missing”
Phase of work: controlled field. The code must exist in GENANAG for the type of item (and job
standard). Repeated phases for the same item are not permitted (it will be checked that no two lines in
the import file have the same item/work phase pair repeated): in such cases, an error will be recorded
on the log file and the record discarded.
Type of item: that present in the import file is completely ignored and the type of item is taken from
the item list in the database, according to the item code present in the file.
Contractor: controlled field. If the code does not exist, an error will be recorded on the log file and the
record discarded. If the phase value in the input file is null or invalid and the contractor is specified, an
error will be logged and the record discarded. If the item has no progress in PROM, it can be modified,
with the event logged on the log file; if not, an error will be recorded on the log file and the record
discarded. If the cell value is null, the field in the DB will be ignored; what is on the DB will be left there.
Contract: controlled field. If the code does not exist in GENANAG, an error will be recorded on the log
file and the record discarded. If the contractor field in the input file has a null or invalid value, an error
message will be generated and the record discarded. If the item has no progress in PROM, it can be
modified, with the event logged on the log file; if not, an error message will be generated on the log
file and the record discarded. If the cell value is null, the field in the DB will be ignored; what is on the
DB will be left there.
Contractor/contract pair: contract and contractor must be linked to each other.
 If the contract field is specified in the input file, then the contractor field on file is ignored
and the contractor taken from the database is used.
 If the contract is not specified (and is not found on the DB), but the contractor is, then it is
checked whether there exists a single associated contract in GENANAG and if so, this is
used for the update; vice versa, if no association exists or if there are more than one, an
error message is generated. If the contract is found on the DB, then the
contractor/contract pair must be one of those provided in the GENANAG database.
Available to Prom: controlled field: can be Y (YES), N (NO), D (DELETE), or null. If the code is different,
an error message will be generated on the log file and the record discarded.
↑ If flag=’Y’, the cases are as follows:
 if the composition or phase is missing from the input file, the database is checked to see if
the full information can be found; basically, at least the phase must be present or available
from the DB.
 even if the line to insert/modify is not complete from the viewpoint of the presence of
composition and contract, it is possible to proceed with the modification/insertion,
obviously, as long as the phase is present or available (see previous point).
↑ If flag=’N’, the cases are as follows:

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 39 (49)

 if the composition or phase is missing from the input file, the database is checked to see if
the full information can be found; basically, at least the phase must be present or available
from the DB.
 in the case of an exploded item in PROM, even if the composition and the phase are not
completely specified in the file, but where it is possible to find them by cross-referencing
data read from the DB, an error message must still be logged for the impossibility of
modification due to the explosion of the item.
 if the item is not exploded, modification is allowed even if the composition is missing.
There are no limits for inserting new records with the flag set to N.
↑ If flag=’D’, the cases are as follows:
 if the composition or phase is missing from the input file, the database is checked to see if
the full information can be found; basically, at least the phase must be present or available
from the DB.
 if the item is exploded and without progress, it must be de-exploded and made unavailable
to PROM, also logging the fact that the item has been de-exploded in addition to the usual
update message.
 if the item is exploded and has made progress, an error message will be generated on the
log file and the record discarded, obviously leaving the item exploded.
 if no planning exists for the item, an error that there is nothing to de-explode is logged.
Composition: controlled field. If the code does not exist, an error will be recorded on the log file and
the record discarded. If the work phase on the input file is empty or invalid, an error message will be
generated, and the record discarded. It can only be associated once per item (the presence of multiple
records in the import file with the item/composition pair repeated will be checked), otherwise an error
message will be generated on the log file and the record discarded. The uniqueness check on
composition per item must be made on data present on the database as well as that present in the
input file. The validity check on compositions must first of all be made on those belonging to the
standard GENANAG compositions (based on item type and work type associations) and subsequently
on those belonging to the job compositions, which must be deducted from the standard ones (on all
work and item types). If the item is not exploded, it can be modified; if not, an error message will be
generated on the log file and the record discarded. If the cell contains the string “DELETE”, the planning
and any final calculations for the item, if present, will be deleted; the event will be logged on the log
file. The “DELETE” function must only physically delete the phase in cases where it is specified in both
the COMPOSITION and RULE fields. If specified in only one field, the program must limit itself to
deleting progress, de-exploding the item and making it unavailable to PCOS or PROM. Afterwards, any
planning will be removed. The log messages will be different depending on the various cases:
• item explosion with progress cancelled and item made unavailable to PROM
• item de-exploded and made unavailable to PROM
• item just made unavailable to PROM
• phase physically deleted (delete COMP and RULE)
In cases of DELETE on an item without phases, an error for the attempted deletion of an unplanned
item will be issued.
UM: controlled field. If the code does not exist, an error will be recorded on the log file and the record
discarded. If the “work phase” cell has a null value, the value in the “UM” field will be ignored, an error
message will be generated, and the record discarded.
If the cell value is null, the field in the DB will be ignored; what is on the DB will be left there.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 40 (49)

Total quantity: freely specified with control of the field format, which must be numeric: 9999999.99. If
the “work phase” cell has a null value, the value in the “total quantity” field will be ignored, an error
message will be generated, and the record discarded. A value of ZERO is considered invalid; an error
message will be generated and the record discarded. If the cell value is null, the field in the DB will be
ignored; what is on the DB will be left there.
Package: controlled field. If the code does not exist, an error will be recorded on the log file and the
record discarded. If the “work phase” cell has a null value, the value in the field will be ignored, an
error message will be generated, and the record discarded. If the value of the cell is null, the field in
the DB will be ignored; what is on the DB will be left there.
Available from: if the “work phase” cell has a null value, the value in the field will be ignored, an error
message will be generated, and the record discarded. It must be checked that the “ready by” date is
greater than the “available from” date. If the cell value is null, the field in the DB will be ignored; what
is on the DB will be left there.
Ready by: if the “work phase” cell has a null value, the value in the field will be ignored, an error
message will be generated, and the record discarded. If the cell value is null, the field in the DB will be
ignored; what is on the DB will be left there.
Duration: freely specified field, with numeric format: 999. If the “work phase” cell has a null value, the
value in the field will be ignored, an error message will be generated, and the record discarded. It will
be checked that the duration field is greater than ZERO; if not, an error message will be generated and
the record discarded. If the cell is null, the field in the DB will be ignored; what is on the DB will be left
there.
Available to PCOS: controlled field: can be Y (YES), N (NO), D (DELETE), or null. If the code is different,
an error message will be generated on the log file and the record discarded.
↑ If flag=’Y’, the cases are as follows:
 if the ITP or phase is missing from the input file, the database is checked to see if the full
information can be found; that is, at least the phase must be present or available from the
DB.
 even if the line to insert/modify is not complete from the viewpoint of the presence of the
ITP, it is possible to proceed with the modification/insertion, obviously, as long as the
phase is present or available (see previous point).
↑ If flag=’N’, the cases are as follows:
 if the ITP or phase is missing from the input file, the database is checked to see if the full
information can be found; that is, at least the phase must be present or available from the
DB.
 in the case of an exploded item in PCOS, even if the ITP and the phase are not completely
specified in the file, but where it is possible to find them by cross-referencing data read
from the DB, an error message must still be issued for the impossibility of modification due
to the explosion of the item.
 if the item is not exploded, modification is allowed even if the ITP is missing. There are no
limits for inserting new records with the flag set to N.
↑ If flag=’D’, the cases are as follows:
 if the ITP or phase is missing from the input file, the database is checked to see if the full
information can be found; basically, at least the phase must be present or available from
the DB.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 41 (49)

 if the item is exploded and without certification, it must be de-exploded and made
unavailable to PCOS, also logging the fact that the item has been de-exploded in addition
to the usual update message.
 if the item is exploded and has certification, an error message will be generated on the log
file and the record discarded, leaving the item exploded.
 if no planning exists for the item, an error that there is nothing to de-explode is logged.
ITP: controlled field. If the code does not exist amongst the job ITPs, an error message will be
generated on the log file and the record discarded. If the work phase on the input file is empty, an
error message will be generated and the record discarded. It can only be associated once per item (the
presence of multiple records in the import file with the item/ITP pair repeated will be checked),
otherwise an error message will be generated on the log file and the record discarded. The uniqueness
check on ITP per item must be made on data present on the database as well as that present in the
input file. The validity check on ITPs must first of all be made on those belonging to the standard
GENANAG ITPs (based on item type and work type associations and on the job standard) and
subsequently on those belonging to the job ITPs, which must be deducted from the standard ones (on
all work and item types and standards). If the item is not exploded, it can be modified; if not, an error
message will be generated on the log file and the record discarded. If the cell contains the string
“DELETE”, the planning and any final calculations for the item, if present, will be deleted; the event will
be logged on the log file. The “DELETE” function must only physically delete the phase in cases where it
is specified in both the COMPOSITION and RULE fields. If specified in only one field, the program must
limit itself to deleting progress, de-exploding the item and making it unavailable to PCOS or PROM.
Afterwards, any planning will be removed. The log messages will be different depending on the various
cases:
• item explosion with certification cancelled and item made unavailable to PCOS
• item de-exploded and made unavailable to PCOS
• item just made unavailable to PCOS
• phase physically deleted (delete COMPOSITION and RULE)
↑ In cases of DELETE on an item without phases, an error for the attempted deletion of an unplanned
item will be issued.
WBS: controlled field. If the code does not exist in the job database, an error message will be
generated on the log file and the record discarded. If the “work phase” cell has a null value and the
WBS field is edited, an error message will be generated and the record discarded. If the cell contains
the string “DELETE”, the WBS field will be deleted.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 42 (49)

44..22 EExxppoorrtt

The Export section is subdivided into five forms. The corresponding utilities enable exporting Drawings,
Main Items, Systems, SubSystems and Items using an Excel compatible format. (Fig. 4.8)

Fig. 4.8

44..22..11 EExxppoorrtt DDrraaw

wiinnggss
This utility enables the exportation of drawings associated with the Items/Work phases. (Fig. 4.9)

Fig. 4.9

It is possible to filter the export data according to the type of item and work phase via specially
provided fields.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 43 (49)

The checkbox allows choosing between whether to export just the items and phases with drawings or
also include items and work phases without drawings.

Extract Drawings - Starts the export operation.

The data that is extracted is the following:

• Job
• Site
• Item
• Phase of work
• Drawing
• Revision
• Notes

44..22..22 EExxppoorrtt M
Maaiinn IItteem
mss
This utility enables the exportation of Main Items. (Fig. 4.10)

Fig. 4.10

Extract Main Items - Starts the export operation.

The data that is extracted is the following:

• Job
• Site
• Main Item
• Description
• U.M.
• Quantity

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 44 (49)

44..22..33 EExxppoorrtt SSyysstteem

mss
This utility enables the exportation of Systems. (Fig. 4.11)

Fig. 4.11

Extract Systems - Starts the export operation.

The data that is extracted is the following:

• Job
• Site
• System
• Description
• Date

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 45 (49)

44..22..44 EExxppoorrtt SSuubbSSyysstteem

mss
This utility enables the exportation of Subsystems. (Fig. 4.12)

Fig. 4.12

The checkbox allows choosing between whether to export just the Systems that have Subsystems or
also include Systems that do not have Subsystems.

Extract SubSystems - Starts the export operation.

The data that is extracted is the following:

• Job
• Site
• System
• Subsystem
• Description
• Date

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 46 (49)

44..22..55 EExxppoorrtt IItteem

mss
This utility enables the exportation of item list and planned item list data. (Fig. 4.13)

Fig. 4.13

Data regarding the “To Export” radio button on the right hand side of the form is not taken into
consideration when exporting the items. All rows that have the checkbox ticked are exported in
sequence.

An Excel-compatible output format is provided.

The filters that are set are stored with an identification code for subsequent usage. The fields that can
be filtered are the following: Type of Item, Area, System, Subsystem, Phase of work, Contractor,
Package, Main Item, Composition and Rule. In the case of exportation of planned items, an additional
filter is provided by the “Type of work” radio button.

The data that is involved in item list extraction is the following:

• Job
• Site
• Item
• Item Description
• Main Item
• Type of Item
• WBS Area
• System
• Subsystem
• Length

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 47 (49)

• Width
• Height
• Diameter
• Weight
• Horizontal or vertical
• Status
• Foundation or structure
• Notes

The data that is involved in planned item list extraction is the following:
• Job
• Site
• Item
• Item Description
• Type of Item
• Phase of work
• Contractor
• Available to PROM
• Composition
• U.M.
• Total quantity
• Package
• Date available from
• Date ready by
• Duration
• Available to PCOS
• ITP

The meanings of the “Type of work” radio buttons on the right hand side are the following:
• Standard
• “All”: all work phases that might already be present are extracted, while the items are extracted in
any case, even if they have no planned phases in the database.
• “Yes”: only and all work phases already present in the database for the item are extracted (if the
item does not have any phases already planned, it is not extracted).
• “No”: the item is extracted on condition that it does not have any planned work phases.

The check box “to export”

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 48 (49)

44..33 RReennaam
mee IItteem
mss

Fig. 4.14

This section allows an item to be renamed, as long as there are no associated accounting measures or
PUNCH LIST points, and in cases where there is no associated certification in PCOS.

In the case of an input file, the data involved is the following:

• Job
• Site
• Old item
• New Item

A couple of checks are applied: the old item code must exist and the new item code must not.
Three printouts (Html reports) will be available, with one giving details of all renames performed
(UserID, when, procedure, table, etc.), another details of all renames performed today and the last one
being a simple list of the renamed items without details (old item, new item and rename date). For the
first two reports, it is possible to choose, via a checkbox, whether to view all data regarding the
changes made (also that of untouched records) or only the data regarding effectively modified records.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.
 INT.GC.PRM.4526

Rev. 0 Date Sept. 2008

Sheet 49 (49)

55 HHEELLPP

55..11 AAbboouutt

This section gives access to the ITEMLIST “about” box, which shows the current version of the
application.

Fig. 5.1

55..22 HHeellpp

This button allows the module’s operating manual to be displayed.

Form code: MDT.GG.QUA.0516 Sh. 01/Rev. 1.94 File code: inftecbe.dot Data file: itemlist_eng_2.06.00.doc
CONFIDENTIAL document. Sole property of Snamprogetti. Not to be shown to Third parties or used for purposes other than those for which it has been sent.