MelmacFive oil and gas workflows. One runtime.
Melmac runs the work between the field data and the filing: air compliance, allocation, produced water, AFE audit and lease title. Each workflow has a named input, a reviewable output and one price.
Illustrative.
The data is in the field, the contracts and the scanner.
The filing is built by hand.
The exception is found too late.
What we scope, who it is for, what you get.
These are the entry points we scope first. Each one starts small and returns something a person can check.
Air compliance and gas capture
Builds LDAR, flaring and venting filings from the operator's data and keeps Texas, New Mexico and Colorado consistent.
You get: a filing-ready record with exceptions flagged.
Scope this workflow →Allocation and settlement
Reconciles producer statements against meter data each month and flags imbalances and fee errors.
You get: a monthly reconciliation with the variances called out.
Scope this workflow →Produced water forecasting
Forecasts water by well from the completion plan and schedules disposal against injection limits.
You get: a water forecast by well and a disposal schedule.
Scope this workflow →AFE and field ticket audit
Checks every ticket against the AFE and contract rates, flags overbilling and reports up by portfolio company.
You get: a ticket-level audit and a portfolio rollup.
Scope this workflow →Lease and title extraction
Reads scanned leases, division orders and JOAs, pulls the terms that matter and matches owners across documents.
You get: a terms and ownership register, with mismatches queued for review.
Scope this workflow →Bring the backlog
Tell us what is piling up. We will map it to one of the five workflows, or say it is not a fit.
You get: a scoped first run and a price.
How engagements work →Reads. Checks. Returns.
The workflow is not a prompt. It is a set of inputs, rules and an output a reviewer can defend.
| Workflow | Reads | Checks | Returns |
|---|---|---|---|
| Air compliance | Production and field data, flare and vent readings, state rules. | Completeness, thresholds, cross-state consistency. | Filing-ready records and an exception queue. |
| Allocation and settlement | Producer statements, meter data, contracts. | Volumes, imbalances, fee rates. | Monthly reconciliation and variance list. |
| Produced water | Completion plans, well data, disposal capacity. | Water by well, injection limits. | Forecast by well and disposal schedule. |
| AFE and field tickets | AFEs, contracts, field tickets. | Rates, approvals, overbilling. | Ticket-level findings and portfolio rollup. |
| Lease and title | Leases, division orders, JOAs. | Terms, owners, obligations. | Terms and ownership register with a review queue. |
Many items. One board. A person on the exceptions.
A workflow is not one long chat. It is a queue of small tasks, each claimed by an agent, checked against the rules, and posted back with its evidence.
- Claim the next item.An agent takes one ticket, statement or lease before it starts.
- Post the result and the evidence.The output lands on the board with the source it came from.
- Stop the run that will not finish.Controller stops it early and sends the item to another model.
- Score the output.Evaluation checks it against the workflow's rules and returns a verdict.
- Review the exceptions.A person sees the flagged items, not the whole pile.
- Keep the record.What was claimed, checked, changed and approved stays on the board.
A workflow, not a platform migration.
One workflow
Start with the filing, reconciliation or forecast that hurts most. Leave the rest alone until the first one works.
One output
A record a person can review, with the exceptions separated from the clean items.
One price
Quoted before the run. Paid when the output is delivered. No token meter.
Air, allocation, water, AFE and lease title. Pick one.
Controller stops a run that is not going to finish.
A missing reading or term is not filled with a plausible guess.
Agreed up front. Paid on delivery.
What changes when the workflow has a record.
| The question | A generic document tool | A Melmac workflow |
|---|---|---|
| A filing | Extracts text and leaves the judgement to you. | Builds the record and separates the exceptions. |
| A missing reading | Filled in by the model. | null, with a flag for review. |
| A monthly close | A spreadsheet reconciliation. | Every statement, meter and fee checked against the rules. |
| A lease file | A scan in a folder. | Terms and owners extracted, mismatches queued. |
| The invoice | Per page, per token. | One quote, paid on completion. |
What the reviewer actually sees.
Two of the five workflows, shown the way a reviewer sees them. Illustrative, on synthetic records.
AFE and field ticket audit
Every ticket checked against the AFE and contract rates. Only the exceptions need a person.
| Ticket | Billed | Allowed | Check |
|---|---|---|---|
| T-1042 | $18,400 | $16,900 | Rate variance |
| T-1043 | $4,250 | $4,250 | Clean |
| T-1044 | $9,800 | $8,100 | Missing approval |
Lease and title extraction
Terms and owners pulled from scans, with confidence on each and a queue for the mismatches.
| Document | Owner | Interest | Score |
|---|---|---|---|
| Lease 2231 | M. Alvarez | 1/8 | 96% |
| DO 88-14 | H. Chen | 1/16 | 91% |
| JOA 4-2 | Talon LLC | — | Review |
Illustrative. Synthetic records. Not client data.
What oil and gas teams ask.
What are the five oil and gas workflows?
Air compliance and gas capture for producers, allocation and settlement for midstream, produced water forecasting for water handlers, AFE and field ticket audit for operators and sponsors, and lease and title extraction for producers.
Are these workflows live products or scoped engagements?
They are scoped workflows on the live Melmac runtime. We start with one workflow, one data source and one output, then quote the work before it runs.
What does the air compliance workflow produce?
It builds LDAR, flaring and venting filings from the operator's data, keeps the rules consistent across Texas, New Mexico and Colorado, and returns a filing-ready record with exceptions flagged for review.
How does allocation and settlement reconciliation work?
It reconciles producer statements against meter data each month, checks volumes and fee rates, and flags imbalances and fee errors instead of letting them through.
Can Melmac forecast produced water by well?
Yes. The workflow forecasts water by well from the completion plan and well data, then schedules disposal against injection limits.
What does the AFE and field ticket audit check?
It checks every ticket against the AFE and contract rates, flags overbilling, and rolls the findings up by portfolio company.
What does lease and title extraction return?
It reads scanned leases, division orders and JOAs, pulls the terms that matter, matches owners across documents and sends mismatches to a review queue.
How do we start an oil and gas workflow?
Pick one workflow and one data source. We run a dry run so you can see the schema or the rules before anything is processed, then agree a single price. You pay when the output is delivered.
Bring one workflow. See the output.
One price, agreed before anything runs. You pay when the output is delivered.