How to Specify LWD Tools: Measurements, Limits, Data Quality, and Integration

Define the LWD Specification Around the Decision

Before you request a quotation, answer these eight questions:

1. What drilling or formation-evaluation decision must the data support?
2. Which measurements are required, and which are optional?
3. What accuracy, repeatability, vertical resolution, depth of investigation, and update rate do you need?
4. What hole size, BHA, mud, temperature, pressure, shock, vibration, and dogleg conditions apply?
5. How will downhole data be transmitted, checked, stored, and delivered?
6. How will the LWD modules connect to MWD, power, telemetry, surface systems, and third-party software?
7. What must the supplier provide for installation, testing, field support, spares, and documentation?
8. Which records will prove that the delivered configuration meets the agreed requirements?

If an input is not final, mark it as to be confirmed. Ask the supplier to list the assumption used in its offer. This is safer than letting an unknown condition become a hidden design decision.

Define the Well Objective and Required Output

Start with the decision, not the tool name. “Provide LWD” does not tell a supplier what the data must achieve. Your objective should identify the geological uncertainty, the person who will use the result, the time available to decide, and the minimum acceptable output.

Name the user of each output. A directional driller, geosteering team, drilling engineer, and petrophysicist may need different data rates, formats, and quality information. A curve that supports a steering cue may not be suitable for final quantitative interpretation.

Select LWD Measurements by Their Required Output

Separate the measurement principle from the commercial module that carries it. Request a channel list and a configuration drawing for the offered tool string.

For every measurement, define:

• the decision it supports and the expected formation range;
• the sensor type, frequency, or spacing where relevant;
• range, units, accuracy, and repeatability under stated conditions;
• vertical resolution and depth of investigation;
• azimuthal, sector, or image capability, if required;
• memory sampling interval and transmitted update interval;
• environmental corrections and required input channels;
• expected response in the planned mud system and hole size; and
• raw, quality-controlled, and interpreted deliverables.

For resistivity, do not specify only a maximum range. Ask which channels use phase or attenuation, which frequencies and spacings are available, and how hole size, mud properties, invasion, and tool position affect the response.

For gamma ray, state whether you need total, spectral, or azimuthal output and how you will use it. For density and neutron measurements, define standoff and borehole-correction needs. For sonic or imaging measurements, define the processing and QC deliverables as well as the sensor.

Do not assume that every measurement is available in one configuration. Require the supplier to identify module order, sensor offsets, connection limits, and any measurement trade-offs in writing.

Define the Downhole and Drilling Limits

Give the supplier the complete operating envelope. Include normal, expected maximum, design, and contingency conditions where they are relevant.

Do not apply one maximum rating to the full string. Sensors, electronics, batteries, seals, pulsers, connectors, and collars may have different limits. Ask which component controls each limit.

Duration also matters. A short survival rating is not the same as continuous operation. Ask how combined temperature, pressure cycling, shock, vibration, and mud flow were covered by the qualification basis.

Set Measurable LWD Data-Quality Criteria

Replace words such as “accurate,” “high resolution,” and “real time” with criteria that you can check.

• Accuracy is closeness to an agreed reference under stated conditions.
• Repeatability is agreement when the same measurement is repeated under the same conditions.
• Vertical resolution describes the smallest bed-scale change that the response can distinguish under defined conditions.
• Depth of investigation describes how far the measurement is sensitive into the formation. It is not the same as resolution.
• Sampling interval tells you how often the tool records a value downhole.
• Telemetry update interval tells you how often selected data reaches the surface.
• Data latency includes sensing, downhole processing, transmission, decoding, QC, and display.

For real-time decisions, list the transmitted channels in priority order. Define compression, averaging, retransmission behavior, and the required update interval for rotary, sliding, and pumps-off modes. A nominal bit rate does not tell you how often a usable curve or directional update will appear.

For recorded data, specify memory capacity, clock accuracy, sampling interval, depth matching, retrieval method, file format, units, channel mnemonics, calibration metadata, correction parameters, missing-data flags, and version control.

Require a method for reconciling rig depth, surface time, MWD data, mud-logging data, and downhole memory data. The final dataset should show what changed, who approved the change, and which version was delivered.

Define LWD, MWD, Power, and Surface Interfaces

LWD measurements depend on the rest of the drilling system. Define the interfaces even when different suppliers provide different parts.

Confirm:

• mechanical connections and dimensional stack-up;
• module order, sensor offsets, stabilizer positions, and near-bit spacing;
• power source, voltage and current demand, battery allocation, and endurance assumptions;
• mud-pulse, electromagnetic, wired, or other telemetry interface;
• downlink or command method and required surface equipment;
• tool-mode logic for rotating, sliding, pumps-off, and connection periods;
• surface decoding, alarms, displays, reports, and network interfaces;
• time and depth synchronization with rig systems;
• data export formats and third-party software compatibility;
• communications access and cybersecurity responsibilities; and
• fallback behavior after a sensor, pulser, battery, or surface-link failure.

Use the CNPS LWD tools page as the commercial reference for the LWD inquiry. Review the CNPS MWD system page when your package depends on directional, telemetry, or surface-system interfaces. If surface logging data must be exchanged, define the channels, timestamps, depth basis, and ownership with the CNPS mud logging unit or the project system.

Do not assume that every listed function can be combined in one tool string. The quotation should confirm the exact configuration.

Define the Supplier's Scope and Responsibilities

Avoid the phrase “complete system” unless the contract explains what complete means. Put the responsibility boundary in the RFQ and ask the supplier to mark every exclusion.

Also state who monitors data quality, who may change the transmitted sequence, who approves configuration changes, who issues the final log, and who keeps the audit trail.

Verify the LWD Package Through Staged Acceptance

Qualification, calibration, FAT, SAT, commissioning, and post-run checks answer different questions. Give each stage its own acceptance criteria and record.

Establish the Acceptance Basis Before Testing

Approve the offered configuration, revision-controlled datasheets, interface list, test procedures, and acceptance limits before testing starts. Record all assumptions and deviations. The tested hardware, firmware, and surface software must be identifiable.

Verify the Assembled Measurement Chain During FAT

Use FAT to check the assembled configuration before mobilization. The procedure should cover power, communication, sensor response, memory, telemetry or simulator interface, decoding, configuration files, clocks, alarms, and data export.

Require signed results that identify the serialized modules, firmware, procedure revision, test equipment, acceptance limits, actual results, deviations, and disposition. State which steps you will review, witness, or hold.

Verify Rig-Site Interfaces During SAT

Use SAT or the agreed pre-job test to check the field installation. Confirm transport condition, serial numbers, connections, seals, battery status, surface communication, time and depth synchronization, configuration backup, spares, recovery arrangements, and contingency modes.

Record every change made after FAT. A passed factory test does not prove that the rig interface is correct.

Establish the Operating Baseline During Commissioning

Before drilling the target interval, record the active tool configuration, transmitted sequence, surface-software version, clock reference, depth reference, alarm settings, and data path. Confirm who can authorize changes and how they will be logged.

The commissioning record becomes the baseline for later troubleshooting and final data reconciliation.

Close the Quality Record After the Run

After the run, record tool condition, downloaded memory, data completeness, faults, shock or vibration events, drift checks where required, repair disposition, and readiness for reuse. If performance was unacceptable, the investigation should separate formation response, drilling dynamics, telemetry loss, surface-system issues, mechanical damage, and sensor failure.

Control LWD Quality With Traceable Records

Link each requirement to an owner, an acceptance criterion, and a record. A generic certificate is not enough if it cannot be linked to the delivered configuration.

Ask for a clause-by-clause compliance matrix. Each “complies” response should point to a controlled drawing, datasheet, procedure, report, or written engineering statement. Silence is not compliance.

Prepare the LWD RFQ Package

Include these inputs with your inquiry:

• well objectives and decisions to be supported;
• target formations, expected property ranges, offset-log examples, and uncertainty;
• hole section, trajectory, BHA, bit, collar, stabilizer, and connection details;
• drilling-fluid program, solids, contamination, and LCM plan;
• temperature, pressure, flow, shock, vibration, dogleg, and run-duration profiles;
• required measurements, channels, resolution, DOI, accuracy, and update intervals;
• real-time and memory data priorities, formats, latency, and retention;
• MWD, telemetry, power, surface, network, and software interfaces;
• supplier scope, site support, spares, special tools, and training;
• qualification, calibration, FAT, SAT, witness, and hold-point requirements;
• documentation schedule and final data-book index; and
• required assumptions, exclusions, and deviations list.

Ask the supplier to return the completed compliance matrix with the quotation. This gives you a clear basis for technical clarification and final acceptance.

Avoid Common LWD Specification Mistakes

Choosing from a sensor list. Two packages can name the same measurements but differ in response, resolution, DOI, placement, corrections, telemetry, and data delivery.

Using one maximum temperature or pressure. The value may apply to one module or a short survival condition. Ask for the controlling limit and exposure duration for every proposed component.

Ignoring drilling dynamics. Shock, vibration, stick-slip, dogleg, washout, and standoff can affect tool survival and measurement quality. Include them in the operating envelope and acceptance discussion.

Treating real time as a yes/no feature. Define which channels reach the surface, how often they update, what latency applies, which QC flags appear, and what happens after lost transmission.

Leaving integration until the rig. Agree channel names, units, clocks, depth references, file formats, access, and decision ownership before mobilization.

Accepting untraceable QA records. Calibration and test records should identify the serialized modules, configuration, procedures, dates, limits, results, and approval.

Answer Common LWD Procurement Questions

Which Measurements Should You Include in an LWD Package?

Include only the measurements required by the well objectives. Options may include gamma ray, resistivity, density, neutron porosity, sonic, borehole imaging, annular or formation pressure, and specialized sampling. For each selected channel, define the decision, expected range, quality criteria, and delivery method.

How Should You Separate LWD and MWD Requirements?

Use LWD requirements for formation-evaluation measurements. Use MWD requirements for directional, drilling-mechanics, and telemetry functions. Then define the shared BHA, power, telemetry, clock, depth, and surface interfaces. The offered configuration must show which system owns each function.

Can You Apply One Temperature Rating to Every LWD Module?

Only with written configuration-specific confirmation. Sensors, batteries, electronics, seals, pulsers, connectors, and collars may have different operating and survival limits. Require the supplier to state the limiting component, exposure duration, derating, and recovery restrictions.

Why Should You Specify Both Resolution and Depth of Investigation?

They describe different measurement behavior. Resolution concerns the scale of a change the response can distinguish. Depth of investigation concerns how far into the formation the measurement is sensitive. A deeper-reading channel is not automatically a higher-resolution channel.

What Drilling-Fluid Data Should You Provide?

Provide the base fluid, density, rheology, salinity or conductivity, oil-water ratio, solids, additives, expected contamination, and LCM type, size, and concentration. These inputs may affect pressure loss, telemetry, compatibility, borehole response, and environmental corrections.

What Evidence Shows That an LWD Tool Is Ready for the Job?

Look for an approved configuration, controlled datasheets, applicable qualification evidence, current channel-specific calibration, passed FAT, serialized maintenance records, an endurance calculation, passed site checks, verified surface communication, and a documented contingency plan.

What Information Should You Send With an LWD RFQ?

Send the well objective, hole and trajectory plan, BHA interfaces, mud program, environmental profiles, required measurements, data-quality criteria, telemetry and surface interfaces, run duration, service scope, acceptance tests, and required documents. Ask the supplier to identify every assumption and exception.