Read otc203131.pdf text version

OTC 20313 Management of Commissioning and Start-up Activities into Moho-Bilondo Integrated Project

Vincent Kiehl, TOTAL S.A.

Copyright 2009, Offshore Technology Conference This paper was prepared for presentation at the 2009 Offshore Technology Conference held in Houston, Texas, USA, 4­7 May 2009. This paper was selected for presentation by an OTC program committee following review of information contained in an abstract submitted by the author(s). Contents of the paper have not been reviewed by the Offshore Technology Conference and are subject to correction by the author(s). The material does not necessarily reflect any position of the Offshore Technology Conference, its officers, or members. Electronic reproduction, distribution, or storage of any part of this paper without the written consent of the Offshore Technology Conference is prohibited. Permission to reproduce in print is restricted to an abstract of not more than 300 words; illustrations may not be copied. The abstract must contain conspicuous acknowledgment of OTC copyright.

Abstract As Commissioning and Start-up activities are always marking the final stage of a Project, they must be carefully planned and organized together well in advance. This is particularly relevant when they take place within an integrated Project like MohoBilondo.These activities are divided into several packages including worldwide technology and equipment, subsurface wells completion to surface equipment, and bringing a deep offshore field development to Congo for the first time. The Moho-Bilondo project was a very tightly driven project over a 34 month period, from first contracts signatures to First Oil flowing at Djeno terminal facilities. As a result of this, it was important to set out the main principles that were to be used over the 3 year period by the Field Operations team with the assistance of other project packages in order to fit into the project time schedule. These principles have been based on the three commitments, as follows: 1. The use of ICAPS software

ICAPS is an `'in-house'' Company tool which stands for Integrated Commissioning and Progress System. It is the compulsory software to be used to apply the Company OPERCOM methodology, in order to prepare and execute PreCommissioning and Commissioning activities for EPCC contracts and it also facilitates feedback for statistical information and internal Commissioning database update. Since mid 2006, the project ICAPS database has been progressively built during the so called `Commissioning preparation phase'. This has been prepared by the contractor teams under the close supervision of the Company Commissioning team and has covered the main packages such as UFL, SPS and FPU. For instance, the FPU package preparation phase took around 8 months and the final database was divided into 58 systems, 351 sub-systems with sub-systems ranking sequence optimized to meet the earliest First Oil date. Then, in summer 2007, the `Commissioning execution phase' started in Ulsan and in Kongsberg respectively for the FPU and the SPS packages. Around 112 000 hrs of Commissioning activities were performed over a 6 month period at the Hyundai yard premises including 12 300 tasks including Instrumentation, Electricity, Mechanical, Piping, Structure, Telecom, HVAC...etc. Thanks to ICAPS software, the priorities were set and optimized weekly in order to achieve rapid progress on the critical subsystems path to First Oil. This was made possible by sharing the same tool with the contractors and was primarily managed and controlled by key Company personnel such as punch list coordinator, ICAPS coordinator, Commissioning Site Leader and of course the Commissioning Manager.

Information

1 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

181837


Notice: fwrite(): send of 208 bytes failed with errno=104 Connection reset by peer in /home/readbag.com/web/sphinxapi.php on line 531