DATA
Bring production data in from spreadsheets, check it, fix it and allocate it, then send clean history to decline and material balance. Every change is logged, and everything goes back out as CSV, Excel or JSON.
WHAT IT DOES
Most engineering time on production data goes on cleaning it. The Data module reads the spreadsheets you already have, CSV, TSV, text or Excel workbooks, and works out what each column is: it detects the measurement and its units with a confidence and a reason, parses dates and flags mixed date orders, detects the reporting frequency and matches well names. You confirm or change any column before anything is imported.
Imported data are checked by 17 validation rules: duplicates, unit slips, spikes, flatlines, gaps, tubing pressure above bottomhole pressure, and jumps in GOR or water cut, among others. Where a fix is safe, it is one click; where two rows disagree, you choose which to keep. Allocation then distributes measured totals by well test and hours on, with BS&W and shrinkage corrections.
Clean history goes straight to Decline & RTA and Material balance. Machine-learning tools flag anomalies and estimate rates where meters are missing, and the audit trail records every change.
KEY CAPABILITIES
Read the files production teams actually send.
The measurements engineering work needs, per well and day.
Problems found before they reach a forecast.
Distribute measured totals back to the wells.
Help on sparse and noisy data, clearly labelled as such.
Know who changed what, and take the data anywhere.
WORKFLOW
Drop in a CSV or Excel file, or paste a table. Check the detected columns, units and well names.
Review the issues by severity and apply the fixes, or keep rows by hand.
Distribute measured totals by well test and hours on, with BS&W and shrinkage.
Plot rates, pressures, water cut and GOR per well, and exclude points.
Send a well to Decline & RTA, or the field to Material balance.
Download CSV, Excel or JSON, and the audit trail.
VALIDATION
Unit handling on import is a named validation case, because a unit slip is the most expensive data error.
| Check | Reference | Converge | Tolerance |
|---|---|---|---|
| Unit conversion on import, 40 m³/d and 25 barg (V24) | 251.59 bbl/d and 377.29 psia | Matches | Exact to 2 decimals |
Not built yet: historian and production-database connectors, scheduled ingestion and allocation-network modelling. The machine-learning tools are trained and tested on synthetic data.
INPUTS AND OUTPUTS
CONNECTED MODULES
One click sends checked history to the modules that need it.
FAQ
CSV, TSV and text files, Excel workbooks (.xlsx, .xls, .xlsm, .xlsb and .ods), or a pasted table.
Yes. Units are detected from the headers, converted and stored in oilfield units, and shown in field or metric. The conversion is a named validation case.
17 validation rules, including duplicates, unit slips, spikes, flatlines, gaps, tubing pressure above bottomhole pressure, and GOR or water-cut jumps, with one-click fixes where safe.
Yes, at any time: CSV in field or metric units, an Excel workbook, JSON, and the audit trail as CSV.
Not yet. Historian and production-database connectors and scheduled ingestion are not built; import is by file or paste, and the REST API can parse tables.