Why this data matters

Upstream, midstream, and site operations already run hundreds of sensing points — wellhead and line pressure, natural gas and flare composition, oil density and water cut, produced-water and frac-fluid meters, ambient and environmental monitors, oil and well log curves and related wellbore records, plus inventory and dispense points where they exist. The same accountability applies to land management records and GIS layers that place leases, tracts, and wells on the map. The hard part is not collecting a reading or a polygon — it is making each record decision-grade: attributable, time-stamped, calibrated or CRS-correct, and usable in production, land, HSE, fleet, and accounting systems without manual re-entry or silent gaps.

Data Field Services helps define and bridge those requirements into accountable office views — beside plant control, not as a replacement for it. See LDUX and SCADA. For how we engage on requirements and scope, see the Discovery process.

Data sensors & measurement domains

Industry data models treat sensors as first-class sources. Requirements span many physical domains; inventory and dispense readings are one family among others:

• Pressure & differential — wellhead, casing, tubing, pipeline, vessel, and pump differential; trip and alarm thresholds with hysteresis.
• Natural gas & vapor — volume/energy flow, composition or quality proxies, flare and vent rates, LEL / gas detection where HSE requires it.
• Oil & liquids quality — density / API gravity, water cut, BS&W, viscosity and temperature-corrected volume where custody or allocation depends on it.
• Oil & well log data — wireline and LWD/MWD curve sets (gamma, resistivity, porosity, density, sonic, caliper, and related channels); depth- or time-indexed samples; mud logs and lithology notes; log headers with well, wellbore, run, toolstring, and calibration context so office views can trust which curve set they are looking at.
• Flow & production — multiphase and single-phase meters, allocation inputs, separator and tank battery totals when those feeds exist.
• Water, fracking & produced fluids — source-water and produced-water volumes, frac-fluid and chemical additive totals, injection rates and pressures, recycle and disposal tickets tied to well or pad.
• Environmental & HSE — air quality, emissions proxies, noise, groundwater / surface-water sampling points, weather and site ambient conditions used in compliance and incident context.
• Temperature & process conditions — line, vessel, soil, and equipment temperature that correct other quantities or flag abnormal operation.
• Level, inventory & dispense — tank or vessel level and derived volume, fill and draw events, and pump-side quantity with asset or job context when operations use those instruments.
• Device health — battery, network status, sensor fault, calibration due, and last-heard for every endpoint above.

Land management & GIS

Oil and gas decisions also depend on spatial and contractual land data — often managed beside measurement systems but required in the same office views:

• Land & mineral interests — leases, deeds, surface and mineral rights, working interest / NRI, tracts, units, JOAs, expirations, and obligation calendars tied to legal descriptions and parties.
• GIS features — lease and tract polygons, well spots, pad and ROW footprints, pipelines, seismic outlines, setbacks, and regulatory buffers with documented CRS and accuracy.
• GIS services — map and feature services (view, query, and extract) so land, ops, and HSE consume the same geometries — with role-based access and version identity for which layer revision an office view used.
• Cross-link to field data — well / wellbore IDs on the map must match measurement, log, and production identities so a reading and a lease polygon never disagree on “which asset.”

Core measurement record

Regardless of physical quantity, industry practice expects each sensor sample or event to carry a minimum context set. Open models that name those pieces are listed on open standards & vocabularies.

Event streams beyond snapshots

Continuous and event-driven sensing commonly requires streams that support operations, allocation, and loss or incident investigation:

• Periodic samples — scheduled pressure, density, composition, level, or environmental readings.
• Depth- / time-indexed log curves — well log channels bound to wellbore, run, and measured depth or time index.
• Change / exception events — threshold crossings, rapid draw or pressure collapse, quality out-of-spec.
• Batch & stage context — frac stages, transfers, deliveries, and injection tickets bound to the same asset IDs.
• Alerts & acknowledgements — configurable recipients, severity, and who acknowledged what.
• Health & last-heard — so silent sensors are visible before decisions depend on stale data.

Accuracy, calibration, and provenance

Measurement claims are only as good as the path from transducer to reported number. Requirements typically include:

• Documented calibration, span, and mapping for each sensor class (pressure, density, gas, level, etc.).
• Retention of which calibration applied at the time of each reading.
• Clear separation of raw sensor value vs. derived quantity (e.g. density → corrected volume; level % → capacity).
• An auditable change log when mappings, ranges, or thresholds are updated.

Connectivity & field protocols

Devices must work where pads and remote sites have weak coverage. Industry expectations span local and wide-area paths — without locking the office to one radio stack. For how to choose and stand up those paths — LoRa / LoRaWAN, Bluetooth, mesh, cellular, satellite, and more — see field connectivity & mesh data services.

Integration & back-office use

Measurement data only pays off when it moves without re-keying. Typical consumers:

• Production allocation, well and pad performance, and engineering analysis.
• Land administration and GIS consumers (lease status, acreage, spatial overlays).
• HSE and environmental reporting (thresholds, samples, and incident context).
• Accounting and ERP (job costing, inventory valuation, vendor reconciliation).
• Fleet and maintenance programs when usage or run-hours accompany field quantities.
• Ops portals (current values, history, notifications) with role-based access.

APIs should support authenticated pull/push, stable asset identifiers, and export (CSV / structured records) for analysis — with the same event identity across systems.

Audit & accountability

For regulated and high-stakes environments, “we have a dashboard” is not enough. Requirements that match accountable field practice include:

• Immutable or append-only event history for critical readings, threshold events, and corrections.
• Named accountability for who authorized a transaction, acknowledged an alarm, or published an office report.
• Signed office releases of layouts and summaries so tampering is detectable (open standards).
• Proofs that can start in local private storage and later harden to device-bound stubs — a presentation card is optional, not required to originate the proof.

Industry need: every sensor reading should answer who · what · where · when · how much · how measured — then survive the trip to production, HSE, finance, and audit without losing identity.

How we help

We map your sensors, meters, and back-office systems to these requirements; define the event model and protocol boundaries; and bridge clean data into operator-facing views — SCADA-adjacent and measurement-adjacent, never claiming plant actuation. Engagements typically start with the Discovery process.