15.03.2018 Views

BAKER HUGHES - Drilling Fluids Reference Manual

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Baker Hughes <strong>Drilling</strong> <strong>Fluids</strong><br />

Using these screening parameters will yield a designed drill-in fluid that will create a filter cake which<br />

will mechanically seal off all pore openings exposed to the well bore, remain intact during the<br />

completion phase, and be easily removed for the production (or injection) of oil and/or gas.<br />

The Proposed Drill-In and Completion Program<br />

Prior to testing and recommending a drill-in fluid, fundamental details about an operator’s reservoir<br />

must be known. Recording information on the items listed below will assist those involved to decide<br />

what application exists and which fluid should be selected for that application.<br />

Local Environmental Regulations<br />

Reservoir Characteristics<br />

Reservoir fluid composition (oil, gas, or formation water)<br />

Lithology (sandstone, limestone, etc.)<br />

Cementation (consolidated, unconsolidated, fractured)<br />

Quantity and type of clays present<br />

Operator Recommendation/Plan<br />

Slim or large hole<br />

Completion technique (gravel pack, non-gravel pack)<br />

Hole geometry (horizontal, vertical, or high-angle)<br />

Note:<br />

To learn more about the effects of a drill-in fluid on a particular type of completion, refer to<br />

the Baker Hughes <strong>Drilling</strong> <strong>Fluids</strong> Drill-In <strong>Fluids</strong> <strong>Manual</strong><br />

As previously listed, the drill-in fluid must be subjected to the following testing to ensure adequate<br />

protection of a producing reservoir.<br />

Baker Hughes <strong>Drilling</strong> <strong>Fluids</strong><br />

<strong>Reference</strong> <strong>Manual</strong><br />

Revised 2006 1-35

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!