Home / News / Sneak Preview: March/April DC takes operator MWD/LWD criticism, challenges to service companies

 This new tool will measure formation pressure and fluid temperature, as well as support real-time identification of reservoir fluid properties and recover fluid samples. Read about it in the March/April DC.

In an article in the forthcoming March/April DC, assistant managing editor Linda Hsieh brings operator criticisms of current MWD & LWD systems to two service companies. DC surveyed several operators and reports their anonymous challenges of these systems, some of the most advanced in the drilling industry.

Several trends emerged. Downhole vibration and shock topped the list, operators noting that ultra-ERD and deepwater operations exacerbate the issue. Real-time vibration and bending monitoring is a real need the industry must address.

Sneak Preview: March/April DC takes operator MWD/LWD criticism, challenges to service companies

Not only can vibration educe ROP, it can “twist” the borehole, producing “false” images through the LWD, an operator said.

While today’s MWD/LWD systems work even in the upper range of well temperatures and pressures, cutting-edge HPTP projects will demand even better performance – to as high as 200°C (400°F) and 35,000 psi.

However, service companies point out that the niche status of HTHP wells increases R&D cost and risk.

Fluid sampling is another item on operator wish lists, for which one manufacturer says it may soon introduce a “game-changing” solution.

Finally, reliability. “The biggest value impact from LWD/MWD/DD is to get it right the first time,” one operator noted. Reliability can suffer from component failures, QA/QC and human error.

Read the entire article in the March/April DC, available later this month.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>