gearOG Cloud Platform

Every meter streams oil, gas, water and sand rates into the platform continuously, alongside line pressure, temperature and differential pressure. The live view shows the current state of every well on one screen, with the whole installed base visible at a glance and any single well one click away.

Because the data arrives continuously rather than in monthly test batches, changes in well behaviour surface as they happen. A rising water cut, a step change in gas fraction or the onset of sand production all become visible within hours rather than at the next scheduled test.

Views are configurable per user. A production engineer watching six wells and an operations manager watching two hundred need different screens, and both get one.

Instantaneous rate is what the meter reads. Cumulative volume is what gets invoiced, allocated and reported, and the two are not the same job.

The platform totals production continuously across every period that matters: contract hour, daily, weekly, monthly and quarterly. Contract-hour accumulation is the important one. Where a rental or service agreement runs on measured hours rather than calendar days, the platform tracks against the contract clock directly, so commercial reconciliation uses the same numbers as the engineering record.

Totals are broken down by phase and by well, roll up to pad, field and operator level, and export to CSV or through the API into whatever allocation system you already run.

Alarms are configured per meter and per phase, on both absolute thresholds and rate of change. A water cut crossing a limit, a gas fraction stepping unexpectedly, sand appearing where there was none, differential pressure drifting outside its expected band, or a meter simply going quiet all raise an event.

Every event carries a severity, a timestamp, the data window around it and an assigned owner. Events acknowledge, escalate and close, and the full history stays attached to the meter, so a recurring fault is visible as a pattern rather than as a series of unconnected incidents.

Alarm fatigue is the failure mode that kills monitoring systems. Thresholds are tuned per well during commissioning rather than applied as a global default, so what reaches a person is worth reading.

Every meter carries its own maintenance schedule in the platform: inspection intervals, verification checks, consumable replacement and annual calibration. Tasks appear ahead of their due date, are assigned to a person, and are signed off with notes and attachments when complete.

The value is the record. When a measurement is disputed, or an audit asks what maintenance the instrument has had, the answer is a complete dated history against that serial number rather than a search through email. Overdue tasks escalate automatically, so a meter cannot quietly fall out of its maintenance regime.

Every meter ships with a durable QR code on its enclosure, tied to that serial number. Scan it with any phone camera and the platform opens that meter’s live page directly: current rates, recent trend, open alarms, calibration status and maintenance history.

This solves a specific field problem. An operator standing at a wellhead does not know the asset tag, does not want to log into a desktop system, and needs to know whether the meter is healthy before touching anything. The QR code removes every step between the person and the data.

Access still respects permissions. Scanning identifies the meter, but the user still authenticates, and only sees the wells they are entitled to see.

Every calibration event is recorded against the meter: date, type, who performed it, the as-found and as-left condition, the reference used and the resulting certificate stored as an attachment.

The platform shows calibration status on the meter’s live page, flags instruments approaching their due date, and retains the full history for the life of the asset. Where measurement feeds allocation or commercial settlement, that unbroken record is what makes the number defensible when a partner questions it.

Continuous measurement produces something a monthly well test never can: a dataset dense enough to model.

The platform trends every phase over any period, fits decline behaviour against production history, and flags deviation from the expected curve. Water breakthrough shows as a trend inflection rather than as a surprise. Sand onset is caught as it begins. Meter health is modelled from the instrument’s own diagnostic data, so degradation is flagged before it becomes a measurement error.

The output is a ranked list of wells that need attention and why, which is what a production engineer with two hundred wells and limited time actually needs.

Select any group of wells and compare them on the same axes: rate by phase, water cut, gas fraction, cumulative volume and decline behaviour. Compare across a pad, across a field, or the same well against its own history.

This is where measurement turns into a decision. Wells drilled into the same formation on the same pad should behave similarly, and the ones that do not are the ones worth investigating. Ranking by deviation from field average puts the outliers at the top of the list.

Comparison views export directly into reporting and are available through the API for integration with existing production systems.

Reports are generated on a schedule or on demand, drawing directly from measured data rather than from a spreadsheet someone assembled by hand.

A daily production summary, a weekly well performance review, a monthly allocation statement or a quarterly field report is produced with the figures, charts and commentary already in place: what changed, which wells moved, which alarms fired and what is trending. The engineer reviews and issues it rather than building it.

Report templates are configurable per customer, branded, and delivered as PDF or Excel by email or straight to the platform.

A retrieval-based assistant trained on the meter’s own documentation, configuration, maintenance history and operating data.

Ask why a reading changed last Tuesday, what the recommended action is for a specific alarm, when the meter was last calibrated and by whom, or what the installation manual says about a particular fault code, and get an answer grounded in that meter’s actual record rather than a generic response.

The intent is to give a field operator at two in the morning the same answer a senior engineer would give, without waiting for the senior engineer.