A cuttings weighing system is not “another pit-level sensor with a different label,” and it is not a drop-in substitute for a full mud-logging unit RFQ. It is a surface monitoring path that continuously weighs cuttings returned over the shale shakers so the drilling team can judge hole cleaning and wellbore-stability trends in near real time—especially when sanding, cavings, or collapsing intervals are the open risk. Operators, EPC/project teams, and procurement engineers lose time asking for “mud logging sensors” before they lock the monitoring object (cuttings return vs pits vs gas vs full unit), shaker layout, communication mode, cleaning/maintenance constraints, and evidence scope.
This page is a selection and RFQ framing guide for a cuttings weighing system. It does not reprint every product bullet as a universal guarantee, and it does not rewrite the published mud-logging system pillar. Use the money page to match an offered configuration; use this article when the open question is still whether cuttings-return weight monitoring fits.
Who this page is for
- Drilling / wellsite engineers deciding whether real-time cuttings-return weight data belongs in the hole-cleaning and wellbore-stability surveillance plan.
- EPC / project teams keeping cuttings weighing, full mud-logging unit, and broader sensor taxonomy scopes separate before the RFQ hardens.
- Procurement engineers writing RFQs that name operating conditions, shaker layout, communications, and evidence, not only “send cuttings scale” as a label.
Start with the operating condition (not the SKU)
Lock these fields before freezing a module count or wireless/wired preference. Blank fields force the quote to guess—often the wrong monitoring object (cuttings return vs pits vs full mud logging), not only the wrong cable type.
| Condition field | What to capture | Why it matters for a cuttings weighing system |
|---|---|---|
| Monitoring object / job | Wellbore cleanliness / hole cleaning, sanding or cavings detection, collapse-risk intervals, or related cuttings-return surveillance | Defines whether cuttings weighing is the right object vs pit level, gas, or a full mud-logging unit |
| Well / section risk | Oil, shale-gas, or gas drilling sections where sanding, cavings, or hole instability is intentional to watch as framed on the live product page | Live page frames high-risk intervals needing real-time sanding/collapse monitoring as published—confirm project risk notes on the offer |
| Surface layout | Number of shale shakers / screens in scope; space and vibration environment; whether modules must stay compact | Live page frames modular multi-module layout and vibration isolation themes as published |
| Data path | Who consumes the curve (mud logging cabin, drilling office, both); historical + real-time curve needs | Separates “weight number on a display” from “usable cleanliness trend” |
| Communications | Wireless preference, RS-485 preference, high-interference zones, antenna / cable constraints | Live page publishes wireless + RS-485 dual-mode framing as published—confirm site RF/EMI reality |
| Cleaning / maintenance | Water availability at the shakers; preference for onboard self-clean vs external wash; crew load | Live page frames pneumatic self-clean without external pressurized water as published—verify offered cleaning path |
| Evidence already held | Prior hole-cleaning incidents, cavings events, lag between cuttings observations and fluid adjustments | Separates “missing sensor” from “missing procedure or lag in response” |
| Adjacent paths | Full mud-logging unit still open; LWD / downhole sensors still open; pit-level / flow-out sensors still open | Cuttings weighing ≠ full unit ≠ downhole LWD |
If the open question is still how to build the overall mud-logging system around a data objective, start with Build the mud logging system around the data objective. If the open question is downhole LWD tools rather than surface cuttings return, use What Are LWD Products? Oilfield Logging-While-Drilling Sensors and Tools Explained. This article sits on a different object: when a cuttings weighing system is the shortlist item.
When a cuttings weighing system fits
Lean toward a cuttings weighing discussion when most of the following are true:
- The monitoring job is cuttings return / hole cleaning / wellbore cleanliness — not only tank volume, not only chromatograph gas, and not only a generic “add more sensors” ask.
- Sanding, cavings, or collapse risk is intentional to watch — the live product page frames petroleum, shale-gas, and gas drilling scenes, especially high-risk intervals needing real-time sanding or collapse monitoring as published.
- You can state surface layout — how many shakers/screens need weighing modules, and whether the package must stay compact/modular for the wellsite.
- Real-time + historical curve use is ownable — someone will act on weight trends (mud properties, ROP, sweep program), not only archive a number.
- Communications constraints are discussable — wireless, RS-485, or both, including interference notes for the location as framed on the live page.
- Cuttings-weighing scope is separate from a full mud-logging unit RFQ — do not collapse “send mud logging” into one PO line that mixes unit cabin, gas system, pit sensors, and cuttings weighing without separate acceptance criteria.
Field check: If the team only needs a full surface mud-logging unit (data acquisition + chromatography + alarm architecture), stay on the mud-logging pillar / unit path until the cuttings-return object is written down. If the need is downhole formation sensors, stay on the LWD path. If the need is a broad “which oilfield sensor family,” use the sensors taxonomy sister—not a silent swap for cuttings weighing.
When other paths usually win first
| Situation | Lean other path first | Why cuttings weighing is secondary |
|---|---|---|
| Need is a full mud-logging unit (cabin, gas, integrated DAQ) | Mud-logging pillar / SLS unit money page (adjacent; not linked as second money CTA here) | Unit ≠ single cuttings-weighing object |
| Need is downhole LWD / formation questions | LWD products sister | Downhole tools ≠ surface cuttings return |
| Need is broad sensor taxonomy (MWD/LWD/pressure/level/gas) before object choice | Oilfield sensors sister | Taxonomy first; cuttings weighing later |
| Only tank volume / spill risk is open | Pit-level / fluid-level monitoring path | Pit level ≠ cuttings weight over the shaker |
| No hole-cleaning or cavings driver; visual cuttings checks already meet the program | Stay on procedure until the monitoring driver is written | Do not force hardware for label alone |
| Only a generic “mud logging sensors” catalogue label is known | Still split cuttings vs pits vs gas vs unit scopes + fill project fields | Label alone does not define the object |
For a wider map of MWD, LWD, pressure, temperature, level, and gas sensing families before you lock the cuttings-return object, use Oilfield Sensors Explained: MWD, LWD, Pressure, Temperature, Level and Gas Sensing for Modern Drilling and Production once.
Cuttings weighing vs full mud logging vs downhole LWD (keep the scopes separate)
A cuttings weighing system is the surface cuttings-return / hole-cleaning monitoring decision. It is not a full mud-logging unit RFQ and not a downhole LWD tool string by itself.
| Scope | Typical decision | Sister / money page |
|---|---|---|
| Cuttings weighing system (this page + PDP) | When cuttings-return weight monitoring fits; shaker layout; comms; cleaning; evidence | This article + live PDP (linked once below) |
| Mud-logging system architecture | Data objective → surface logging system design | Mud-logging pillar (linked above) |
| Full mud-logging unit | Cabin / chromatography / integrated DAQ package | Unit money page — keep as adjacent scope; do not dual-money this closing |
| Downhole LWD products | Formation / logging-while-drilling tools | LWD sister (linked above) |
| Broader sensor taxonomy | Which sensor family before object choice | Oilfield sensors sister (linked above) |
Field check: Writing one PO line that mixes “mud logging unit + cuttings weighing + LWD” without separate data objectives, acceptance tests, and interfaces creates the wrong evidence pack for each scope.
What the live product page already frames (honesty bounds)
As published on the live CNPS product page for Cuttings Weighing System:
- Product-family framing: intelligent solution for real-time monitoring of wellbore cleanliness and wellbore stability during oil and gas drilling by continuously measuring the weight of returned cuttings as published (page body currently carries Chinese product copy; English title/metadesc frame the same object).
- Application framing as published: petroleum, shale-gas, and gas drilling—especially high-risk intervals needing real-time sanding or collapse monitoring.
- Design themes as published: compact modular design; wireless and RS-485 communication; hanging/suspended weighing design with pneumatic vibration isolation framing; automatic sampling / automatic discharge / self-cleaning themes; onboard pneumatic water-jet cleaning of the collection pan without external pressurized water.
- Multi-module framing as published: each setup supports up to three weighing modules, each tied to a separate shale shaker, with synchronized real-time monitoring language.
- Peer-comparison themes as published (selection language to verify on the offer—not competitive guarantees invented here): compact/modular vs bulky global models; wireless + RS-485 redundancy vs wired-only peers; pneumatic self-clean vs missing auto-clean.
- FAQ themes as published: no external wash water required for cleaning (onboard pneumatic boost pump language); wireless vs RS-485 selectable via control-board DIP / software COM and baud settings as published.
Honesty bound: Do not treat a blog selection page as a certified accuracy sheet. Exact weighing accuracy percentages, Kuwait deployment as a project guarantee for your well, MTBF, or invented ppm/kg resolution belong in engineering review and the formal offer—as offered / as published. Do not invent certificate seals, API mud-logging badge claims, or ROI % the live page does not publish as universal guarantees. Prefer “as published / as offered” when quoting module count, communications, and self-clean language.
RFQ fields that keep cuttings weighing system quotes comparable
Copy these into the enquiry so quotes stay comparable and do not collapse into a vague “send mud logging sensors” ask—or a silent swap for a full unit.
| RFQ field | What to write | Honesty bound |
|---|---|---|
| Monitoring-object intent | Cuttings weighing / cuttings-return monitoring intentional (hole cleaning / sanding / cavings / collapse watch — state which) | Do not hide an open full-unit vs cuttings-only debate |
| Well / section identity | Field/well ID; hole section; fluid system notes; risk intervals | Unknown is better than invented geology |
| Surface layout | Number of shakers/screens in scope; space/vibration notes | Confirm offered module count (PDP frames up to three modules as published) |
| Data consumers | Mud-logging cabin, drilling office, historian/SCADA notes | Wrong consumer → wrong interface assumption |
| Communications | Wireless, RS-485, or both; interference / antenna / cable constraints | Live page lists dual-mode framing as published—match on offer |
| Cleaning / utilities | Preference for onboard self-clean; note if external wash water is unavailable | Confirm offered cleaning path—no assumed utility map |
| Integration / software | DIP/COM/baud expectations; curve display / alarm ownership | Confirm offered software scope |
| Evidence docs | FAT/SAT expectations, packing, destination, spare modules as required | No fake certificate numbers |
| Related scopes | Separate RFQs for full mud-logging unit / LWD / pit sensors if any (or “none”) | Keep objects separate |
| Project ID + engineer | Who owns duty and acceptance | Required for comparable replies |
For live catalogue framing and the published modular / communications / self-clean / multi-module notes, use Cuttings Weighing System once you are ready to match an offered configuration.
FAQ
Is a cuttings weighing system the same as a full mud-logging unit?
No. A full mud-logging unit typically bundles cabin/data acquisition, gas analysis, and a broader surface-sensor set. A cuttings weighing system is the cuttings-return weight monitoring object tied to shale-shaker layout. Specify cuttings weighing vs full unit explicitly. Use the mud-logging pillar when the system architecture is still open; use this page when the cuttings weighing path is open.
Does this replace pit-level or flow-out sensors?
No. Pit volume / spill surveillance and flow-out kick/loss cues answer different questions than cuttings weight over the shakers. Many programs need more than one surface measurement—keep RFQs and acceptance criteria separate.
Does the live page guarantee a specific weighing accuracy % for every wellsite?
No. The live product page frames high weighing accuracy and vibration isolation themes as published, without a universal accuracy percentage reprinted here as a project guarantee. Confirm offered accuracy, calibration, and acceptance tests on the formal quote.
Why does the page emphasize wireless and RS-485 together?
The live page frames dual communication—high-power directional wireless plus RS-485 redundancy for high-interference areas—and FAQ language about DIP/software selection as published. Treat that as site-fit selection language to verify for your RF/EMI and cable plan—not a blanket claim that every location can run wireless-only.
Where do I see live product framing?
On the live product page titled Cuttings Weighing System (linked once above)—catalogue scope and published modular / communications / self-clean / multi-module notes there; fit and RFQ framing here.
Talk to engineering
If hole-cleaning or wellbore-stability surveillance is intentional and a cuttings weighing system is on the shortlist, start here: Talk to an Engineer. For commercial follow-up, contact sales@cnps.com once with the same monitoring-object note, well/section risk, shaker/module layout, communications preference, cleaning/utilities note, evidence-scope note, and project ID.
