Why pipeline data is different
Pipelines stretch measurement across miles of right-of-way, stations, and product cycles. The office must reconcile SCADA-adjacent tags with commercial batches, integrity work, and GIS corridor layers — without confusing a control setpoint with an accountable information view. Data Field Services helps define those data requirements and bridge them into attested office views. See field measurement, field connectivity, LDUX and SCADA, and the Discovery process.
Core pipeline measurement domains
- Line & station pressure — suction/discharge, MAOP-related operating envelopes, differential across filters and meters; alarm and event history with hysteresis.
- Flow & energy — volume and mass rates, cumulative throughput, temperature and compressibility corrections for gas; meter proving and factor history.
- Product & batch — commodity / grade, batch ID, interface detection, density or quality proxies, and shipper or ticket context for liquids lines.
- Composition & quality — gas chromatograph or quality feeds, H2S / water / contaminant limits where tariffs or safety require them.
- Equipment state — pump / compressor status, valve position (as reported), ESD and station health as information — actuation stays in OT.
Integrity, leak detection & ROW
- Integrity data — ILI / pig run results, anomaly features, dig tickets, coating and CP readings, and remediation status bound to stationing or milepost.
- Leak detection inputs — mass/volume balance segments, pressure-wave or CPM-related signals, and alarm acknowledgements with named operator identity.
- Corridor / GIS — centerline, ROW polygons, class locations, HCA/MCA context, crossings, and setbacks with CRS and layer version — same GIS service expectations as land management.
- Third-party / excavation — one-call tickets, patrol findings, and encroachment events linked to segment and time.
Core pipeline data record
Regardless of tag or document, industry practice expects each sample or event to carry:
| Dimension | What must be captured |
|---|---|
| Who | Operator, controller, or system identity for human-initiated or acknowledged events. |
| What | Line, segment, station, meter, valve, batch, pig run, or GIS feature ID; product / commodity. |
| Where | Stationing / milepost, station name, or geometry (centerline offset) with CRS when spatial. |
| When | Trusted timestamp; lag noted for store-and-forward or delayed integrity uploads. |
| How much | Quantity with unit: pressure, rate, volume, density, CP voltage, anomaly size, etc. |
| Why / job | Ticket, nomination, work order, dig package, or shipper account when commercial or maintenance requires it. |
| How measured | Device / tag ID, config revision, calibration or proving factor, ILI tool and run ID. |
Commercial & scheduling context
Pipeline data often feeds nominations, allocations, and imbalance views. Requirements typically include stable batch and meter identities across SCADA-adjacent feeds and back-office systems, so tickets and measured throughput do not disagree on “which barrel.”
Connectivity & interchange
Stations may use fiber, cellular, microwave, or satellite; remote valves and sensors may use LPWAN or mesh. Office interchange commonly expects MQTT, Modbus, OPC UA-adjacent feeds, and HTTPS APIs — with store-and-forward and duplicate detection. Detail: field connectivity and open standards.
Audit & accountability
- Append-only history for critical alarms, acknowledgements, and integrity decisions.
- Named accountability for who published an office summary or closed a dig ticket.
- Signed releases of corridor maps and operational views so tampering is detectable.
- Clear boundary: LDUX and office views do not actuate pumps or ESDs — see LDUX and SCADA and field to verifiable view.
Industry need: every pipeline reading and integrity record should answer who · what · where · when · how much · how measured — then survive the trip to control-room information views, land/GIS, commercial, and audit without losing identity.
How we help
We map your line, station, integrity, and GIS systems to these requirements; define event and segment identity; and bridge clean data into operator-facing views. Engagements typically start with the Discovery process.