How to Specify a Mud Logging Unit: Sensors, Gas Detection, Data Acquisition, and Site Integration

Start With the Decisions the Unit Must Support

Do not begin with a supplier’s standard equipment list. Begin with the decisions that the drilling and geology teams expect to make from the data.

Surface data logging commonly combines drilling information, wellbore-condition indicators, geology, and hydrocarbon-fluid analysis. The exact service scope varies by project. A basic unit may record selected rig parameters, total gas, chromatographic gas components, rate of penetration (ROP), lithology, and sample descriptions. Another project may need additional engineering calculations, remote data delivery, advanced gas analysis, or dedicated geological workspaces.

Your specification should therefore define the service objectives in plain language. Examples include:

• maintain a time- and depth-indexed record of selected drilling parameters;
• support the geologist’s correlation of cuttings and gas data with drilled depth;
• identify changes in gas trends and designated drilling indicators for review by authorized personnel;
• provide agreed displays, alarms, reports, and data exports;
• preserve a traceable record of calibration, downtime, edits, and data quality;
• transmit approved data to the rig network, operator office, or another authorized system.

These objectives also establish the system boundary. A mud logging unit can provide observations and alarms specified by the project, but it should not be presented as a replacement for the rig’s well-control equipment, the drilling contractor’s control system, a fixed fire-and-gas system, personal gas detectors, or the operator’s emergency procedures. Responsibility for interpreting information and taking action must remain defined in the drilling program and site procedures.

Before requesting a configuration, record at least the following project inputs:

• onshore or offshore location, rig type, well type, and expected drilling phases;
• drilling-fluid systems and any changes expected between hole sections;
• expected formation fluids and project-specific gas-analysis objectives;
• H2S or other toxic-gas risk controls defined by the site;
• rig sensor sources, available signal types, approved connection points, and data ownership;
• operator reporting format, units, time zone, depth reference, and naming convention;
• hazardous-area classification and the physical locations of cabin, sensors, junction boxes, and sample equipment;
• electrical power, earthing, uninterruptible power supply (UPS), network, and communications interfaces;
• ambient temperature, humidity, dust, vibration, marine exposure, and other environmental conditions;
• transport, lifting, space, weight, access, escape-route, and maintenance constraints;
• governing regulations, client specifications, certification expectations, and document language.

This input set prevents a common error: purchasing a nominally complete unit without confirming whether it can connect to the actual rig and project data environment.

Build a Channel Register Instead of a Generic Sensor List

A list such as “pressure, temperature, pit level, flow, torque, gas” is not yet a specification. Each channel needs a measurement purpose, installation point, performance requirement, signal path, data treatment, calibration method, and acceptance criterion.

Build a channel register during the RFQ stage. The register should include both sensors supplied with the unit and measurements received from third-party rig systems. It should also identify calculated channels and manual entries so that users can distinguish measured values from derived or entered values.

Typical measurement groups may include:

Drilling mechanics. Depending on the rig and service scope, inputs may cover hole depth, bit depth, ROP, block position, hook load or weight-related measurements, rotary speed, torque-related measurements, standpipe pressure, pump strokes, and status signals. The approved source of each input matters. A value read from a rig data system has a different interface and responsibility chain from a dedicated sensor installed by the mud logging contractor.

Circulating system. Possible inputs include active-pit levels or volumes, flow in, flow out, pump rate, mud temperature, mud density, and conductivity. Do not assume that every property is continuously measured or that a sensor output is interchangeable with a manual mud check. ISO 10414-1, for example, describes field testing of water-based drilling fluids across properties such as density, viscosity and gel strength, filtration, composition, and chemical characteristics. Your measurement plan should state which results come from continuous instruments, which come from field tests, who owns each value, and how discrepancies are handled.

Gas and geological observations. Common data may include total gas, selected hydrocarbon components, gas-system status, sample depth, lithology description, show descriptions, fluorescence observations where applicable, and sample inventory. The exact analyzer and sample program must follow the geological objectives and fluid environment.

System-health channels. Include power status, UPS status, communication health, analyzer flow or status indications, sensor fault states, storage capacity warnings, and other signals needed to distinguish a genuine process change from an instrumentation problem.

The table below illustrates how to turn a broad requirement into an auditable register. It is a structure, not a set of universal values.

For every analog or digital input, define the expected signal type, isolation, power arrangement, connector or termination, cable responsibility, scaling, engineering unit, normal state, failure state, update or sampling behavior, and calibration approach. For a network-delivered value, specify the source system, protocol, access method, cybersecurity constraints, reconnection behavior, and who resolves data conflicts.

Avoid using “high accuracy” or “fast response” as acceptance criteria. Replace them with project-approved values and test methods. The correct range and accuracy depend on the expected operating envelope and the decision supported by the measurement. A narrow range may improve usefulness in one application but become unsuitable in another. The specification should require the supplier to declare actual performance and the purchaser to approve it.

Specify the Gas and Sample Path as a Complete System

Gas measurement begins before the analyzer. Gas and cuttings reach the surface with the circulating drilling fluid, and a gas trap or extractor at the returns releases gas for transport to the logging unit. The sample line and conditioning components then affect what reaches the detector. Your specification should treat this as one measurement chain and define how returned samples are related to drilled depth.

Your RFQ should describe the complete sample path:

1. Return-flow and extraction point. Identify the intended location at the shale shaker/header box or other project-approved point. Confirm access, mounting, representative exposure to returns, maintenance access, and interfaces with rig operations.
2. Extraction method. Define whether the project requires a particular gas-trap concept or operating control. Record the power supply, status feedback, cleaning method, and spares.
3. Sample transport. Specify the route, approximate length, tubing material, protection, fittings, expected ambient exposure, and responsibility for installation. Address water or condensate management, blockage, leakage checks, and safe discharge.
4. Flow conditioning and monitoring. Define pumps, filters, separators, regulators, flow indication, fault detection, and maintenance access as applicable to the selected method.
5. Analysis scope. State whether the project requires total-gas trend measurement, separation and quantification of specified hydrocarbon components, or another defined analysis. Name required outputs, units, ranges, detection or quantification expectations, cycle time, and calibration method in the project data sheet.
6. Calibration and verification. Identify approved reference materials, certificates, frequencies, pass/fail criteria, drift handling, records, and the response when a verification fails.
7. Vent and safety arrangement. Define where analyzed gas is discharged, how the route is protected, and which site safety requirements apply. The arrangement must be reviewed for the specific location and hazards.

Total-gas detection and chromatographic analysis answer different questions. A total-gas channel provides a combined trend according to the detector and extraction system. A chromatograph separates specified components according to its configured method. The RFQ should not use “gas detector” as a catch-all term; it should identify the required analytical result and how it will be checked.

Lag management is equally important. The time required for cuttings and entrained fluids to travel from the bit to surface changes with circulation conditions and well geometry. A specification should define the lag calculation method, input data, pump-efficiency assumptions if used, treatment of pump changes or interruptions, verification routine, and audit trail for manual corrections. The objective is not merely to display a lag number. It is to maintain a defensible relationship between observed samples, gas trends, time, and depth.

If the well changes between water-based, oil-based, synthetic, foam, air, or another circulating medium, ask the supplier and service team to explain how sampling, cleaning, gas extraction, cuttings preparation, and interpretation procedures change. Do not assume that one procedure is valid for every fluid system.

Define Data Acquisition, Software, and Data Exchange

“Real-time monitoring” is too broad for procurement. A complete data specification explains what is acquired, how it is synchronized, what users see, what is stored, and what leaves the unit.

Start with the data model. For every channel, define:

• unique name and description;
• measured, calculated, received, or manually entered status;
• engineering unit and permitted unit conversions;
• time index, depth index, or both;
• source timestamp and system timestamp behavior;
• sample rate, update rate, aggregation, filtering, and rounding as applicable;
• valid range, quality flag, missing-data representation, and sensor-fault state;
• alarm thresholds, delays, latching, acknowledgement, suppression, and event records;
• storage frequency, retention period, backup, restoration, and export format;
• user permissions and audit history for edits or annotations.

Then define displays and reports by user task. A driller-facing display, a geology workspace, a morning report, and a remote operations feed may need different data and refresh behavior. Provide example layouts or required fields, not only a statement that screens are “customizable.” Specify who can change channel configuration or alarm settings and how changes are recorded.

Time synchronization deserves its own requirement. The DAQ, analyzers, rig source systems, workstations, and receiving platforms should use an agreed time source and time-zone treatment. The SAT should verify timestamp behavior after a restart or communications interruption. Depth reconciliation also needs an agreed reference and a documented process for corrections.

If the operator requires WITSML, name the implementation requirement precisely. Energistics identifies WITSML as a standard for well-data exchange, including drilling, logging, and mud logging data. Its current developer information lists WITSML v2.1 with ETP v1.2. However, a version name alone does not prove interoperability.

The interface specification should state:

• WITSML and ETP versions, or another required protocol and version;
• client/server roles and endpoint ownership;
• required objects, channels, mnemonics, units, indexes, timestamps, and quality fields;
• authentication, encryption, certificates, firewall rules, and approved network route;
• live-update and historical-retrieval behavior;
• buffering and recovery after connection loss;
• expected load and retention;
• an agreed test dataset and end-to-end acceptance procedure.

Also define data ownership, permitted remote access, support access, removable-media controls, software patching responsibility, antivirus or application-control requirements, account management, backups, and incident handling. These requirements should align with the operator’s cybersecurity rules. A mud logging supplier should not be asked to invent a site policy at mobilization.

Integrate the Cabin With the Rig and Site

The cabin is part laboratory, part operations room, and part equipment enclosure. Its design must fit the actual location rather than a generic “land/offshore” label.

Provide a layout showing workstations, sample examination and preparation areas, gas-analysis equipment, DAQ cabinets, storage, doors, emergency exits, windows, HVAC components, cable entries, sample-line entries, utility connections, and service clearances. Review walking routes and maintenance access with the equipment installed. If chemicals, calibration gases, or pressurized cylinders are used, define their storage and handling requirements under the project safety system.

Mechanical and logistics inputs should include overall dimensions, operating and transport weights, center of gravity, lifting points, forklift provisions if applicable, tie-down or sea-fastening interfaces, stacking restrictions, transport envelope, and inspection of lifting accessories. Offshore projects may require project- or jurisdiction-specific structural, lifting, fire, material, or certification documentation. Do not accept a general “offshore suitable” statement in place of the required documents.

Electrical requirements should identify supply voltage, frequency, phases, maximum and normal load, connector, distribution arrangement, protection, isolation, earthing/bonding, UPS loads and autonomy requirement, emergency isolation interface, and restart behavior after power loss. Separate essential loads from convenience loads. Confirm whether external sensors need barriers, isolators, or dedicated supplies and who provides them.

Where equipment is installed in or connected to a classified hazardous area, the project must provide the area classification and applicable rules. IEC 60079-14:2024 covers design, selection, installation, and initial inspection of electrical installations associated with explosive atmospheres, including documentation and personnel competency. Its applicability depends on the jurisdiction and contract, and it does not address toxic-gas hazards. Therefore, the RFQ should request the exact protection concept, marking, certificate, equipment schedule, installation method, and verification documents required for each location—not a generic “Ex certified” claim.

Ventilation and pressurization, if required, should be defined through the project’s area-classification and safety design. Specify alarms, interlocks, purge/pressurization behavior, intake and discharge locations, filter maintenance, environmental limits, and failure response. Fire detection, gas detection, shutdown, and communications interfaces should be coordinated with the rig or facility systems and clearly assigned to a responsible party.

Finally, issue an interface responsibility matrix. For every power cable, network cable, sensor, bracket, junction box, sample tube, gas exhaust, calibration bottle, regulator, mounting point, and test activity, name the supplying party, installing party, testing party, and approving party. This small document prevents significant wellsite delay.

Verify the System Through FAT, SAT, and Commissioning

A factory acceptance test (FAT) should demonstrate more than successful power-up. The strongest approach tests representative and critical paths from the originating input to the final user output.

Set the FAT Basis Before Testing

Before FAT, approve the system architecture, general arrangement, bill of materials, channel register, I/O drawings, power load, data-interface document, alarm matrix, software list, certificate register, and test procedure. Record open technical queries so that FAT does not become the first detailed design review.

Test the Complete Measurement Chain During FAT

During FAT, test as applicable:

• identification, calibration status, and traceability of sensors and analyzers;
• analog and digital inputs at defined points across their approved ranges;
• scaling, units, timestamps, quality flags, calculated channels, and displays;
• alarm initiation, delay, acknowledgement, latching, suppression, and event history;
• gas analyzer response and sample-system status using approved reference materials and safe procedures;
• reports, exports, user roles, configuration audit trail, backup, and restoration;
• required WITSML or other data transfer using the agreed receiver and test dataset;
• network interruption, buffer behavior, reconnection, and missing-data handling;
• power failure, UPS operation, controlled shutdown, restart, and configuration retention;
• system-health indications, fault simulation, and recovery procedures;
• document accuracy against the as-tested configuration.

Use a punch list with owners and due dates. A closed item should have evidence, not only a verbal confirmation. Material substitutions and software-version changes after FAT should trigger a documented impact review and, when necessary, retesting.

Verify Site Interfaces During SAT

The site acceptance test (SAT) confirms the installed system with actual rig and site interfaces. Repeat channel mapping and polarity checks, verify sensor locations and labels, inspect cabling and sample lines, confirm area and electrical interfaces, validate network routes, and compare received data at the destination. Check the lag workflow with approved well and circulation inputs. Confirm displays, reports, time synchronization, backup, user accounts, communications, and shift-handover processes.

Establish the Commissioning Baseline

Commissioning should end with an approved baseline: final configuration, calibration and test records, open-item disposition, as-built drawings, software and license record, backup image, spares inventory, training record, contact and escalation list, and signed acceptance. This baseline makes later troubleshooting and change control possible.

Mud Logging Unit RFQ and Acceptance Checklist

Use the following list as a starting point. Add project-specific requirements rather than deleting detail behind a statement such as “complete package.”

The checklist is not a design standard. Its purpose is to expose missing interfaces before award and to create objective acceptance evidence before the system reaches the wellsite.

Frequently Asked Questions

Which sensor channels are mandatory in a mud logging unit?

There is no universal list that fits every rig and well. Start with the drilling, geological, gas-analysis, reporting, and safety-interface decisions defined by the project. Then specify the channels required to support those decisions. Common groups include depth and ROP, selected drilling mechanics, pump activity, pit and flow measurements, gas channels, fluid properties, sample records, and system-health signals. The final list must be approved against the rig interfaces and well program.

Why is lag time important in mud logging?

Cuttings and formation fluids take time to travel from the bit to the surface in the circulating fluid. Lag management helps associate a surface observation with the drilled interval it represents. Because circulation conditions and well geometry can change, the specification should define the calculation inputs, update process, verification method, and audit trail for corrections.

Are total-gas detection and gas chromatography the same requirement?

No. A total-gas detector reports a combined response according to its detection and extraction system. A chromatographic system separates and reports specified components according to its method and configuration. A project may require one or both, but the RFQ should name the expected analytical outputs, units, range, cycle or response requirements, calibration method, and acceptance test.

Can a mud logging unit replace rig safety or well-control systems?

No. Mud logging data can support situational awareness and project-defined alarms, but the unit should not replace the rig’s well-control equipment, drilling controls, fixed fire-and-gas system, personal detectors, or emergency procedures. The operator and drilling contractor must define who monitors each alarm, who has authority to act, and how the mud logging service communicates observations.

When should WITSML be included in the specification?

Include WITSML when the operator or receiving platform requires standardized well-data exchange. State the required WITSML and ETP versions, objects, channels, units, indexes, timestamps, quality flags, authentication, buffering, and end-to-end test. If a simpler approved interface meets the project need, specify that interface instead. Avoid accepting “WITSML compatible” without a tested mapping.

What documents should be approved before mobilization?

The exact register is contractual, but it commonly includes the system architecture, general arrangement, equipment list, channel register, I/O and wiring drawings, data-interface document, power load, alarm matrix, software/version list, hazardous-area certificate register where applicable, calibration certificates, FAT record, manuals, spares list, lifting documents, SAT procedure, training plan, and open-item status. Request final as-built versions at handover.

Prepare a Project-Specific Specification

A strong mud logging unit specification connects every requirement to an operating decision, a physical or digital interface, and a testable result. Define the well and rig basis first. Build a channel register. Treat the gas sample path, DAQ, software, cabin, utilities, and external data exchange as one system. Then verify the complete measurement chain during FAT and SAT.

CNPS presents a configurable system overview on its mud logging unit page. Before requesting a configuration, prepare your rig type, well program, required channels, gas-analysis scope, fluid systems, data-interface requirements, area classification, utilities, environmental conditions, documentation list, and acceptance criteria. These inputs allow both parties to review the actual project scope instead of relying on a generic package description.

References

• ISO 10414-1: Field Testing of Water-Based Drilling Fluids
• IEC 60079-14:2024: Electrical Installations in Explosive Atmospheres
• Energistics: WITSML Developers & Users
• Energistics: What Is WITSML?