Académique Documents
Professionnel Documents
Culture Documents
ENGINEERING MANUAL
Integrated
Commissioning
And
Progress
System
ICAPS
ENGINEERING MANUAL
Index Description Date Issued by
1 ICAPS R3 10/2005 Capgemini
2 ICAPS R3.10.02 11/2007 Capgemini
1. Introduction________________________________________________________3
1.1. Aims of the Engineering Manual _________________________________3
1.2. OPERCOM Methodology ______________________________________3
1.3. ICAPS______________________________________________________4
2. Engineering Import-Export Module _____________________________________5
2.1. Main Principles of the Module ___________________________________5
2.1.1 Introduction____________________________________________5
2.1.2 Data format ____________________________________________5
2.1.3 Database code __________________________________________5
2.1.4 Automatic numbering ____________________________________5
2.1.5 Revision Types _________________________________________6
2.1.6 Log report _____________________________________________6
2.1.7 Users groups ___________________________________________6
2.1.8 Import / Export SYSTAL _________________________________7
2.1.9 Punch List Import _______________________________________7
2.2. Man Machine Interface (MMI) __________________________________8
2.3. Importing Engineering Data _____________________________________9
2.3.1 Introduction____________________________________________9
2.3.2 Import of Items _________________________________________9
3. Engineering Import Format Examples __________________________________11
4. Revision Types ____________________________________________________12
5. Glossary _________________________________________________________13
6. Appendix_________________________________________________________14
6.1. Appendix 1: The Typical Phases of a Project ______________________14
6.2. Appendix 2: OPERCOM Methodology ___________________________14
6.3. Appendix 3 – Project breakdown ________________________________17
6.4. Appendix 5 - Import Log Report ________________________________19
6.5. Functional Specifications of Import / Export Module ________________19
The OPERCOM methodology has been developed to handle the preparation and
the execution works of both the precommissioning and the commissioning. Its
main objective is to allow a smooth transfer of the installation from the
Construction to the Operator, as quickly as possible, in full confidence, and with
all the required safety.
The APPENDIX 3 gives the architecture of the software. It shows the main
hierarchies and links involved in the model, which are:
- The physical hierarchy for the equipment breakdown,
- The task hierarchy for the associated completion tasks.
The transfer of engineering data is done using the IMPORT / EXPORT module.
2.1.1 Introduction
The IMPORT / EXPORT module is an easy tool to allow to :
- Import all the engineering data required by ICAPS to create the
OPERCOM database.
- Import / export parts or complete OPERCOM database (Status Index,
Technical DataBase,…) during the completion activities (revised
lists,…).
In order to allow import, it is necessary to fix the engineering list formats, which
is the main target of this document.
From import:
When tasks are created in the local database, the users groups must be empty. The
task number is automaticaly created and the user group is the users group of the
connected user.
When tasks are created in a remote database and then imported in the local
database, the users groups must be given in the import files.
There is no export/import facilities for the users groups. However, during a task
import in order to merge two database, if the users group of a task does not exist
while it is in the import file, it is automatically created by the system before the
task creation.
Security:
A user can create/modify/delete tasks and associated punch lists of his group.
A user can modify/delete tasks and associated punch lists of another group only if
his access level is 4.
A user with a level 4 access can create tasks of another group if he imports tasks
from another database.
ICAPS R3.10 includes a new concept : management Punch List Actors with
ICAPS login.
A user who is not a ‘Punch List User’ can’t import PunchLists even if user with
level 4.
The import user interface is shown on the following screen view (FIGURE 1) :
Among the several possible importing facilities, this document presents only the
import of Items which concern the Engineering preparation.
2.3.1 Introduction
The two engineering data importing formats are presented in the following
paragraphs.
It is strongly recommended to comply with those 2 formats from the
beginning of the engineering data list preparation in order to avoid a later
conversion to the data formats required by ICAPS.
In any case, the Engineering team is in charge of the data file conversion
to the ICAPS file formats.
Some of the imported data are mandatory in the engineering equipment
lists as they are necessary to use ICAPS. All the other data are optional,
however, it is recommended to supply them as they are used during the
execution and it is appropriate to gather them at this time, when they are
available.
ICAPS database includes all technical and organizational data for P/Com and Com
activity preparation and follow-up during execution. All data inside one ICAPS
database must be related to a unique project.
Equipment Progress
Branch Branch
Project Project Seq
System Stage
Subsystem
Tasks
Tasks Substage
Tasks
Item
Users Group
Punch
Lists
General order of execution for different Task Activities is defined below (bottom
corresponds to first tasks and upper part is for latest tasks.)
Commissioning
(PVP)
Operational Tests
Tasks
(OTS)
Functional Tests
(FTS)
Preliminary Checks
(PRC)
PreCommissioning
Static Tests
(STS)
Tasks
Piping Tests
(PIP)
Conformity Checks
(CCK)