Oil and gas operations software, built to your workflow.
Upstream operators, midstream terminals and oilfield service companies use Genwright to replace the spreadsheets and text messages between the wellsite and the office — on a platform whose regulated-filing work in Texas is a matter of public record.
Where operators usually start.
The numbers arrive by text message and leave as a guess
Pumpers send their morning readings by text or radio. Somebody retypes them into a spreadsheet. By the time production reporting is finished the day is over, and the figure that reaches the report has no traceable relationship to the person who read the gauge.
That gap is expensive in three separate ways. Allocation and revenue are calculated from numbers nobody can reconstruct. Downtime is coded after the fact, from memory, so nobody can tell whether a well is losing production to a pump or to a road. And when a state or federal filing needs supporting detail, the supporting detail is a text thread.
Packaged production software fixes this for operators large enough to buy and staff it. Below that line, the spreadsheet wins by default.
Common first builds in upstream and midstream operations
Scoped starting points, not products. Each is built against your well naming, your route structure, your downtime codes and your approval chain.
Daily production & downtime
Route-ordered pumper entry that works without signal, variance flags against expected rate, downtime coded at the point of entry rather than reconstructed at month end.
Tanks, tickets and transfers
Gauge readings, run tickets, water hauls and transfer records tied to the tank and the well, with the entry-level history behind every volume that reaches a report.
Wellsite inspections & HSE
Site inspections, spill and incident records, corrective actions, e-permitting, lockout/tagout and mustering — recorded once, attributable, exportable.
Field service & job tickets
For service companies: job intake, crew and equipment assignment, field ticket capture with signature, and billing-ready records that do not need re-keying.
Contractor management
Contractor onboarding, insurance and credential expiry, safety orientation records, and gate access tied to whether the paperwork is actually current.
Regulated filing workflows
Multi-stage submission and review with role-scoped visibility, pre-population from a system of record, generated PDFs and a defensible status history. See below.
The Railroad Commission of Texas online W-3A system
Knomatic built the online filing system for Form W-3A, the Notice of Intention to Plug and Abandon, for the Railroad Commission of Texas — the state agency with regulatory jurisdiction over Texas oil and gas, pipeline safety and surface mining.
What it replaced
A typed paper form last revised in 1983, mailed or carried to a district office, reviewed by hand, with the operator holding the only copy of what had been submitted until somebody wrote back.
What it does
An operator enters an API number and selects a lease. Roughly twenty fields then pre-populate from Commission records — operator name and P-5 number, district, county, drilling permit and Rule 37 case numbers, lease and well identifiers, field, survey and abstract detail, total depth, usable-quality water strata and the Groundwater Advisory Unit letter date, casing records and perforation records.
From there the filer completes the area review, amends casing and perforation tables, and builds the plugging proposal plug by plug. The filing is routed to the district office covering the well's surface location, reviewed, and either approved or returned for rework.
Platform behaviour, in a regulated workflow
- StagesIn Progress · Pending Review · Under Review · Returned for Rework · Returned · District Approved · Closed
- Row-level accessIn-Progress, Pending Review and Returned filings are visible only to the filer who created them
- Public recordDistrict Approved filings become searchable public record
- IdentityA unique tracking number assigned to every filing at creation
- Pre-population~20 fields drawn from the Commission's system of record
- DocumentsPDFs generated at submission and approval, retained on a Files tab
- Draft safetyIn-progress filings saved automatically; 45-minute session timeout returns work to Drafts
- SearchAcross all filing fields and by stage, with filtering and a customizable grid
- ValidityApproved proposals carry a six-month expiration surfaced in the record and on the PDF
Multi-stage review, role-scoped visibility, pre-population from a system of record, generated documents, retained comments that stay off the public PDF, and a status history that has to survive scrutiny — this is the same shape as a maintenance approval, a permit-to-work, or a settlement dispute. If it holds for a state regulator's plugging notices, it holds for yours.
Form W-3A, the W-3A Online User Guide and Statewide Rule 14 are published by the Railroad Commission of Texas; the process details above are drawn from those public documents. The Railroad Commission of Texas does not endorse, sponsor, approve or recommend vendors. This reference describes a delivered engagement and is published with the agency's written consent.
You are not starting from a blank canvas
Modules already running in production on the Knomatic platform. Genwright starts from the ones that fit and shapes them to your operation.
Field & production
The wellsite and the route.
- Route-based field data capture
- Daily production entry
- Downtime coding & variance flags
- Tank gauges & run tickets
- Offline-tolerant mobile entry
- GPS & asset geolocation
Safety & environmental
What a regulator or insurer asks for.
- Site inspections
- Incident & spill records
- Corrective action tracking
- E-permitting
- Lockout / tagout
- Mustering
- OSHA recordkeeping
Workforce & contractors
Everyone who comes through the gate.
- Applicant tracking
- Onboarding & documents
- Integrated background checks
- Credential & certification tracking
- Compliance monitoring
- Scheduling
- Time & attendance
Commercial
From the ticket to the money.
- Field ticket capture
- Customer portals
- Contract management
- Invoicing
- Vendor settlement
- Automated payables & receivables
Records & oversight
What turns activity into evidence.
- Forms digitization & scanning
- Multi-stage review workflows
- Generated PDFs & document retention
- Dashboards & analytics
- Enforced audit trail
- Integration to existing systems
Oil and gas questions we are asked most
Will pumper entry work without cell coverage?
Yes. Field capture is offline-tolerant. A pumper works the route and enters readings wherever they are; the application synchronizes when signal returns, preserving the original timestamp and author rather than the sync time. That distinction is what makes the volume defensible when someone asks who read the gauge and when.
Does Genwright replace our production accounting system?
Usually not. Most operators keep production accounting and revenue distribution and use Genwright for the capture and operations layer feeding it — field entry, downtime, tickets, inspections and contractor compliance. Applications read from and write to existing systems over documented interfaces.
Can Genwright handle regulated filing workflows?
Yes, and there is public precedent. The Railroad Commission of Texas online W-3A system, built by Knomatic, runs a seven-stage submission and review workflow with role-scoped visibility, pre-population from a system of record, generated PDFs and retained comments. The same platform capabilities apply to permits, approvals and internal sign-off chains.
How do you handle contractor compliance at the gate?
Contractor onboarding, insurance certificates, safety orientation and credential expiry run as connected modules, so access decisions reference whether the paperwork is currently valid rather than whether it was valid when the contractor was first approved. Alerts fire before expiry, not after an inspector finds it.
How long does a first build take?
A scoped pilot covering two to three workflows typically runs four weeks from kickoff to a production pre-flight review. Because the field capture and compliance modules already exist, most of that time goes into fitting them to your well naming, route structure and downtime codes.
How is it priced across a large well count?
Genwright is priced on a platform footprint that scales with deployed users or units under management, not per application and not per field user. Putting every pumper and contractor on it does not multiply the bill, which is deliberate: a field workflow that excludes field users produces an incomplete record.
Bring the number nobody can reconstruct.
A scoping call is a working session. Describe how a volume gets from a gauge to a report today, and you will leave knowing what a first build covers and what it costs.