Services/Operations data and decision systems
We turn daily exports, controlled drawings, test reports and correspondence into one record for operations, engineering and management: the current state with its sources, an event log, a profile for each well and a data health report, refreshed on a cadence the field can keep up.
On a large field the answer to a simple question sits in six spreadsheets with three different dates. A status export says flowing. A routing list says shut in. A planning file says the well moved last month. If the newest file wins every argument, you get the wrong answer. If each fact is taken from the most authoritative source for that fact, with its date, you get the right answer and you can see the conflicts that remain.
We build five layers: current (the latest accepted value per field with its date), context (linked tests, work orders, integrity records and limits), history (dated observations and milestones), changes (what moved since the last refresh, including source conflicts) and sources (file, revision, owner, date, authority and confidence). A well profile reads in four views: now, context, history, changes, with the key risks at the end.
The system can be a SQLite and JSON package behind a browser view, a Power BI model, or a hosted database with an API. The software matters less than the rules: keep history, never erase an unrelated domain on refresh, show how fresh each domain is, and never swap a test value for an allocated rate without saying so.
Canonical entities (well, facility, train, manifold, flowline, project, work order, source), aliases and de-duplication, field-level authority and effective-date rules, confidence and conflict flags.
Identity and status, a short summary, routing against home facility, flowline integrity and replacement, operations and interventions, timeline and changes, ranked risks.
Deferral registers, planned against current well rates, facility capacity opportunities on a decline basis, scenario tables and handover schedules.
Facility flow diagrams and P&IDs stitched into one graph. Designed, as-built, temporary, planned, isolated and flowing connections kept distinct, each with its drawing, revision and confidence.
Ingestion by file hash and date. Checks on units, duplicates, mass balance and freshness. Snapshots that are never overwritten. Change events and a data health report with the open conflicts.
Built from your own exports and drawings. We prefer a weekend refresh for most domains, with well status refreshed more often. The data-as-of date is shown separately from the refresh date.
A field data model and browser console joining well status, rates, routing, flowline integrity, service tests, water systems and project delivery, with history kept on every refresh.
Met4 of 4 success criteriaOperator engagementRead the caseMiddle East·Producing field, management reportingA deferral register and weekly facility summaries that keep oil separate from liquid, transfers separate from net gains, and every item with an owner and a date.
Met4 of 4 success criteriaOperator engagementRead the caseMiddle East·Brownfield design reviewA review of a P&ID package against the statement of requirements for new transfer lines between two facilities. The gap found was between the sheets, not on them.
Met4 of 4 success criteriaOperator engagementRead the caseA technical question, a train that will not stabilise, a water balance that will not close, a data room that will not reconcile. Describe it in a paragraph and we will propose the scope.
hello@assostechltd.com · 5 South Charlotte Street, Edinburgh, EH2 4AN