LWD products—logging-while-drilling sensors and tool strings—put formation-evaluation measurements in the bottom-hole assembly while the bit is still turning. They are not a directional-only MWD package, not a surface mud-logging unit, and not a later wireline FE suite. Enquiries stall when they say "send LWD" before anyone writes down the formation decision, the borehole envelope, the BHA/telemetry assumptions, and which scopes stay on separate RFQ lines.
This page is an LWD products selection guide: when formation-evaluation sensor families in the BHA fit a well section—and what to put in the RFQ so offers are comparable. If you still need the full LWD solution/path framing (objective → envelope → BHA/telemetry → data handoff as a hub), start with LWD Products & Tools: When Logging-While-Drilling Fits. This article covers the narrower decision: when LWD products belong on the shortlist for measurement-family selection and RFQ fields.
Who this page is for
- Drilling, geosteering, and formation-evaluation engineers deciding whether LWD sensors in this section answer the open formation question—or whether MWD alone, surface mud logging, or wireline timing is the real object.
- EPC and well-construction teams keeping LWD products, MWD, surface mud logging, and open-hole / cased-hole wireline scopes separate before the RFQ hardens.
- Procurement and operations engineers writing enquiries that name channels, envelope, BHA/telemetry, real-time vs memory, and acceptance evidence—not a bare "need LWD" line and a brochure screenshot.
First principles: what LWD products change
Write down the formation decision before choosing any sensor string. Five facts drive most LWD-product decisions:
- The job is formation evaluation while drilling, not survey alone. Resistivity, gamma, density/porosity-related, and other FE channels (as required) answer rock/fluid questions while the bit is making hole. Directional and drilling-mechanics data are a related but different object (MWD).
- Real-time and memory are different budgets. Selected channels may transmit while drilling; fuller records often stay in memory until after the run. State which decisions need real-time response.
- BHA and telemetry are one system. LWD sensors share power, communication, and collar real estate with any MWD package on the same string—interfaces must be written once for the system.
- Surface cuttings/gas context is a separate line. Mud logging complements LWD; it does not replace downhole FE logs. Keep the surface unit on its own RFQ when that scope is open.
- Proof is usable logs against a written objective, not a catalogue label. Without a written evaluation objective, envelope, channel list, and who owns QC/interpretation boundary, nobody can say the string fitted the job.
The live CNPS path page for LWD Products & Tools: When Logging-While-Drilling Fits frames selection around the formation question, borehole envelope, BHA/telemetry, and data handoff—not invented model names. Whether an offered string fits your well depends on the fields below.
Start with the formation object, not the SKU
Lock these fields before freezing channel lists or telemetry assumptions. Blank fields force the quote to guess—often the wrong measurement object (LWD FE vs MWD-only vs surface mud logging vs wireline-later), not only the wrong collar.
| Condition field | What to capture | Why it matters for LWD products |
|---|---|---|
| Evaluation objective | Geosteering / landing; casing-point; early reservoir / saturation indicator; correlation; other (state) | Defines whether LWD FE sensors fit vs MWD-only or wireline-later |
| Channels | Resistivity; gamma; density/porosity-related; acoustic / NMR / imaging / pressure-related only if required | Matches published measurement-family language—no invented SKUs |
| Real-time vs memory | Which channels must transmit; which can wait for memory download | Sets telemetry budget and surface decode path |
| Borehole envelope | Hole size; inclination / trajectory; mud type/weight; pressure; temperature; shock/vibration; flow | Lets a supplier refuse an unfit string |
| BHA / telemetry | MWD coupling yes/no; placement / spacing needs; power; communication method; surface system | Shared real estate—state once for the system |
| Data / QC | Formats; depth matching; QC ownership; tool-data vs petrophysical interpretation boundary | Avoids "logs arrived, nobody can open them" |
| Adjacent scopes | MWD-only still open; surface mud-logging unit still open; open-hole vs cased-hole wireline timing still open | LWD ≠ MWD ≠ mud-logging unit ≠ wireline phase |
| Evidence owner | Who accepts logs against the written objective; documents you will review | Label alone does not define acceptance |
When LWD products fit
LWD products are worth a serious look when most of the following are true:
- Formation decisions must be supported while drilling—geosteering, landing, casing-point, or early reservoir calls—not only survey.
- The section is high-angle or horizontal, or wireline risk / time is unacceptable for that interval.
- You can state channels (resistivity, gamma, density/porosity-related, or others) and which are real-time vs memory.
- The borehole envelope is written—hole size, mud, pressure/temperature, shock/vibration, flow, inclination—so a supplier can refuse a bad fit.
- BHA and telemetry are treated as one system with any MWD package on the same string.
- Surface cuttings/gas context, if needed, stays on a separate mud-logging line—not forced into the LWD SKU.
- Equipment / service model is explicit—tools only vs tools + field support; spares; destination; required date.
Field check: Only directional control is needed → MWD path (write MWD RFQ fields separately). Surface mud-logging cabin / unit is the object → mud-logging unit path. Borehole-state (open vs cased wireline timing) still undecided → hub first. Full LWD solution/path framing still open → money path page first. Vertical section and FE can wait for wireline → wireline timing may win; incomplete truth beats overselling channels.
When other paths usually win first
| Situation | Look at first | Why a standalone LWD-products RFQ is secondary |
|---|---|---|
| Only directional / survey control is needed | MWD RFQ fields (separate prose path; no MWD page linked here) | MWD answers trajectory; LWD answers formation |
| Surface cuttings / gas / cabin package is the object | Mud Logging Unit: When a Surface Mud-Logging Package Fits Drilling Surveillance (Selection & RFQ Fields) | Surface unit ≠ downhole FE sensors |
| Need mud-logging methods context, not a unit RFQ | Mud Logging: A Comprehensive Guide to Tools, Techniques, and Data Accuracy | Encyclopedia / methods ≠ LWD channel selection |
| Open-hole vs cased-hole borehole state still undecided | Open-Hole vs Cased-Hole Logging: Differences, Tools & When to Use Each | Hub first; LWD after while-drilling FE is chosen |
| Full LWD path / tools selection framing still open | LWD path hub (linked once in the intro as the money page) | Hub owns solution/path; this page owns measurement-family + RFQ blanks |
| No objective, no envelope, no real-time vs memory written down | Write those fields before any catalogue label | Label alone does not define the object |
LWD products vs MWD vs mud logging vs wireline (keep the scopes separate)
The labels overlap in conversation; the objects do not. LWD products on this page means the formation-evaluation sensor-family decision in the BHA only.
| Scope | Typical decision | Acceptance evidence you would expect |
|---|---|---|
| LWD products (this page) | When FE sensor families in the BHA fit while-drilling evaluation | Channels delivered as scoped; envelope within offered limits; RT/memory as agreed |
| MWD | When directional / drilling-mechanics data fit trajectory control | Survey / mechanics deliverables—not FE logs |
| Surface mud logging | When a surface unit / cuttings-gas package fits drilling surveillance | Surface datasets and unit scope—not downhole FE |
| Wireline (open or cased) | When FE can wait for a dedicated logging phase | Program-phase timing and conveyance—not LWD collar real estate |
| LWD path hub | When full solution/path framing is still open | Path fields on the money page—not a second hub rewrite here |
Writing one PO line that mixes "LWD + MWD + mud-logging unit + wireline" without separate data objectives and acceptance tests creates the wrong evidence pack for each scope. Adjacent tools stay on separate RFQs (or clearly nested lines) if needed—do not explode SKUs here.
What the live path page already states (honesty bounds)
As published on the live CNPS path page LWD Products & Tools: When Logging-While-Drilling Fits (post 10124, checked 2026-11-03):
- Path framing: Measure while drilling; lock evaluation objective, borehole (hole size, inclination, fluid, pressure, temperature, vibration), BHA/telemetry, and data handoff before the catalogue label as published.
- Fit language: Lean toward LWD when formation decisions must be supported while drilling; the section is high-angle/horizontal or wireline risk/time is unacceptable; channels (resistivity, gamma, density/porosity-related, or others) and real-time vs memory are stateable; the envelope is written; BHA/telemetry are one system with any MWD package; surface cuttings/gas stays on a separate mud-logging line as published.
- Procurement fields: Well section; operating envelope; measurement objective; real-time vs memory; BHA/telemetry; data/QC; service model; acceptance evidence as published.
- Out-of-scope honesty: You may not need a full LWD suite when the section is vertical and FE can wait for wireline, or when only directional control is needed (MWD alone) as published.
Optional catalogue attribution (not the money href): the published global catalogue page describes resistivity, gamma ray, density, and porosity-family measurements, modular configuration with MWD, and a published high-temperature figure of up to 175°C as published on that page. Attribute those claims only to the catalogue page, and always reconfirm against your well envelope. Prefer the www.cnps.com path page above for how to specify the job.
Honesty bound: Not a certified performance sheet for your well. No invented model numbers, SKUs, DOI/accuracy %, certificate numbers, monogram details, ROI, or extra °C/psi appear here. Unknowns stay flagged as confirm-on-offer.
RFQ fields that keep LWD products quotes comparable
Copy these into the enquiry so replies stay comparable.
| RFQ field | What to write | Honesty bound |
|---|---|---|
| Evaluation objective | Formation decisions while drilling (geosteering, casing-point, correlation, porosity/saturation indicator—state) | Do not hide an open MWD-only or wireline-later debate |
| Channels | Resistivity / gamma / density/porosity-related / other only if required | Measurement families—not invented SKUs |
| Real-time vs memory | Which channels transmit; which wait for memory | Telemetry budget must match surface path |
| Well section | Hole size; MD/TVD if known; inclination / trajectory; mud type | Sets OD, standoff, fluid corrections |
| Operating envelope | Pressure, temperature, shock/vibration, flow window | Lets a supplier refuse an unfit string; catalogue 175°C is evidence only if cited from catalogue |
| BHA / telemetry | MWD coupling; placement; power; communication; surface system | Shared real estate—state once |
| Data / QC | Formats; depth matching; QC ownership; interpretation boundary | Tool data ≠ petrophysical study unless scoped |
| Service model | Tools only vs tools + field support; spares; destination; required date | Commercial scope must match technical brief |
| Acceptance evidence | Published ratings and documents you will review | Catalogue claims are evidence, not a blank cheque |
| Related scopes | Separate RFQs for MWD / mud-logging unit / wireline phase, or "none" | Keep objects separate |
| Project ID + engineer | Who owns log acceptance and logistics | Required for comparable replies |
For live path framing and RFQ language, use the money path page linked in the intro when you are ready to match an offered configuration.
When the fields above are filled in, send them through Request a quotation so the offer is priced against your formation object, not a generic brochure pack.
FAQ
Are LWD products the same as MWD?
No. LWD products focus on formation-evaluation measurements in the BHA while drilling. MWD commonly focuses on drilling mechanics, direction, and trajectory. They are often integrated in one BHA and share telemetry, but they answer different questions—write separate RFQ lines by measurement objective.
Is a surface mud-logging unit a replacement for LWD products?
No. A mud logging unit is surface cuttings/gas/parameter surveillance. It complements LWD and wireline; it does not replace downhole formation logs. Use the mud-logging unit selection path when the cabin/package is the object.
Why use LWD instead of waiting for wireline?
LWD supplies formation data during drilling—useful for geosteering and for wells where wireline is slow or hard to deploy. Wireline may still be required for final high-resolution FE. Timing and conveyance are program choices—state which dataset is the record copy when both are proposed.
Can LWD products be selected from temperature rating alone?
No. Hole size, pressure, shock, vibration, mud system, flow, inclination, BHA compatibility, telemetry, and measurement objectives all matter. Catalogue temperature figures (for example, the published high-temperature figure on the global LWD catalogue page) are evidence to verify—not a blank cheque for every section.
What should I send before an LWD products quote is useful?
Well section, operating envelope, required channels and real-time priorities, BHA/telemetry constraints, data/QC needs, service model, and required date—plus the formation decisions the log must support.
What about older LWD overview pages on this site?
Prefer this selection/RFQ page and the live path page LWD Products & Tools: When Logging-While-Drilling Fits for current enquiry language. Weak older LWD marketing siblings are not refreshed here and are not competing targets.
Talk to engineering
If formation evaluation while drilling is the binding job and LWD products are on the shortlist, start here: Talk to an Engineer. For commercial follow-up, email sales@cnps.com once with the same evaluation-objective note, channel list, envelope, BHA/telemetry assumptions, related-scope list and project ID.
