|
SAFEBUCK Phase II: Objectives
Much progress was achieved during Phase I of the SAFEBUCK JIP. For the first time all the disparate
disciplines that are required within lateral buckling design have been collated and presented to a consistent level.
The guideline provides a foundation for the safe development of future projects. However, in developing the Phase I
guideline a number of important issues were raised which could not be fully addressed within the original JIP workscope.
More importantly, under increasingly severe operating conditions it becomes difficult to demonstrate an acceptable level
of pipeline integrity.
The aim of SAFEBUCK Phase II is to build on the solid foundations of Phase I, to extend and optimise
the guideline so that projects involving the most challenging of operating environments can confidently adopt the on-bottom
design solution. The aim is to reduce the conservatisms that were necessarily introduced into the guideline as a result
of the novel nature of the undertaking. This will allow the integrity of a pipeline system to be clearly demonstrated
under increasingly severe operating conditions. Thus the JIP will be an enabling technology for many upcoming HPHT
developments.
The areas where further research is required to achieve this aim are:-
- Enhancement and optimisation of the design approach through use of structural reliability techniques;
- Experimental evaluation of pipeline walking and the underlying pipe-soil mechanism;
- Improved definition of key limit states;
- Soils testing to extend the database of lateral and axial soils response.
Each of the SAFEBUCK JIP participants will receive a "Lateral Buckling Design Guideline" package. This will consist of the following:
- Engineering reports on:
- Structural reliability analysis of lateral buckling;
- Local buckling under combined loads;
- Pipeline walking.
- A full report on the fatigue testing;
- A full report on the pipe-soil interaction testing;
- Phase II generic on-bottom, lateral buckling design guideline;
- Website (containing all document deliverables) and a unique access code.
|