Oil & gas: operators, drilling, oilfield services, midstream and land
Oil and gas runs on documented work across the whole industry. Operators, drilling contractors, service companies, midstream and land firms all run on years of daily reports, AFEs, field tickets, dispatch, maintenance, safety and regulatory workflows, the kind of real operational record AI labs are asking for.
Opens the fit check on historypays.com in a new tab. No files are collected on this site.
Oil & gas owner? Dan also runs BlackGoldData.com (opens in a new tab), a separate site written just for operators, mineral and royalty businesses, energy accounting and title-opinion firms.
Who's the desk team
Oil and gas companies often have far more people in the field than at a desk. Office, engineering, dispatch and field-office staff are where the documented work lives, and contractors in your company's email and software may count too, depending on the provider. Rig hands and field crews who don't work in your systems aren't the desk team.
That still leaves room for a lot of companies. Many service companies with large field workforces have real desk teams in dispatch, field offices, billing, engineering and safety. Requirements vary by provider, and the provider confirms fit.
What a provider looks at
- A desk team: employees and contractors who work at a desk in your company's email and software. Field and hourly crews who aren't in the systems aren't the desk count.
- Several years of history in your systems.
- Work across systems, such as email, chat, file storage, CRM, tickets and billing.
- Requirements vary by provider, sector and dataset, and the provider confirms fit.
Operators and E&P companies
Independents and mid-size producers run on a busy office: land, geology and geoscience, engineering, regulatory, accounting, HSE and the operations and field-office staff who keep the wells moving.
Who fits
- Independent E&P companies and mid-size producers
- Private-equity-backed and family-owned operators
- Office teams in land, geology and geoscience, and engineering (drilling, completions, reservoir and production)
- Regulatory, accounting (JIB, revenue and division orders) and HSE staff
- Operations and field-office desk staff, such as production clerks and coordinators, who work in company systems every day
Records that count
- Daily drilling, completion and workover reports, and morning reports
- AFEs and well files
- Production reporting and allocation workflows
- Regulatory filing workflows (for example, Texas RRC)
- JIB, revenue distribution and division order workflows
- Field ticket review and approval, procurement and vendor communication
- HSE incidents, JSAs and permits
- SOPs and training
- Email, Teams and SharePoint
Good to know
- Working-interest partners and joint operating agreements (JOAs) can put confidentiality terms on shared well data. That's normal, and the provider's review sorts out what's yours to license.
- Seismic and other licensed data belongs to its licensor, and reservoir data, interpretations and trade secrets aren't assumed licensable without review. Your team's own workflow around them usually is.
- Royalty owner, lessor and partner personal details are handled as the agreement specifies.
Software these teams use
Well & production data
- WellView (Peloton)
- SiteView (Peloton)
- ProdView (Peloton)
- OpenWells (Halliburton)
- Quorum On Demand Well Operations (formerly WellEz)
Accounting, JIB & revenue
- Quorum Accounting (On Demand and My Quorum)
- IFS BOLO (formerly P2 BOLO)
- IFS Excalibur (formerly P2 Excalibur)
- IFS ProCount (formerly P2 Merrick)
- Enertia
- W Energy Software
- SAP S/4HANA
Geoscience, engineering & reserves
- Petrel (SLB)
- Kingdom (now SLB)
- Petra (now SLB)
- ARIES (Halliburton)
- PHDwin
- ComboCurve
- Spotfire
Spend & field tickets
- OpenInvoice (Enverus)
- OpenTicket (Enverus)
Drilling and rig contractors
Rig crews work in the field, but a drilling company's office runs on daily reports, scheduling, maintenance, safety and recruiting, and that's where the desk headcount usually is.
Who fits
- Land drilling contractors and rig fleets
- Operations and rig-management office staff
- Dispatch, rig-move and logistics coordinators
- Maintenance planners and equipment managers
- HSE, training, recruiting, HR and payroll staff
- Sales, contracts administration and accounting
Records that count
- IADC daily drilling reports (tour sheets) and morning reports
- Rig move and scheduling workflows
- Maintenance work orders and equipment history
- HSE incidents, near misses, JSAs and permits
- Crew training, certifications and onboarding
- Procurement and vendor communication
- Invoicing workflows, SOPs, email and Teams
Good to know
- Rig sensor and EDR data held in a vendor's system (such as Pason or a data platform) may belong to the vendor or the operator under the contract. Your own reports, maintenance records and emails are usually yours.
- Records about an operator's well may be the operator's under the drilling contract, and drilling contracts themselves are excluded as client agreements.
- Export-controlled drilling technology isn't a fit. Crew personal details are handled as the agreement specifies.
Software these teams use
Daily reporting
- TourNet (SLB)
- RIMDrill
Rig data & analytics
- Pason (EDR and DataHub)
- NOV RigSense
- Corva
- RigCLOUD (Nabors)
Maintenance & ERP
- IBM Maximo
- SAP S/4HANA
Oilfield and well services
Service companies often have big field workforces and still a real desk team in dispatch, field offices, billing, engineering and safety. That office team is where the documented work lives.
Who fits
- Completions and frac, wireline, cementing, coiled tubing, and flowback and testing
- Well servicing and workover rigs
- Water hauling and disposal, trucking and hot oiling
- Rentals, chemical, and other well-site services
- Desk staff in dispatch and job scheduling, field-office coordination, sales, billing and field-ticket processing
- Engineering and technical support, HSE and compliance, maintenance and fleet, HR, recruiting and payroll
Records that count
- Field tickets and service tickets (these count as operational records)
- Dispatch and job scheduling
- Job, completion and workover reports
- Maintenance work orders and fleet and equipment records
- HSE incidents, JSAs and permits
- Operator prequalification and compliance workflows
- Quotes, invoicing workflows, procurement and vendor communication
- SOPs, training, email and Teams
Good to know
- Records about an operator's well, such as job data and logs, may belong to the operator under the MSA. Your own tickets, dispatch, maintenance and emails are usually yours, and the provider's review sorts it out.
- Proprietary technology, such as chemical formulations, isn't assumed licensable without review, and export-controlled technology isn't a fit.
- Driver and crew personal details are handled as the agreement specifies.
Software these teams use
Field ticketing & operations
- FieldCap
- OpsReady
- Enverus OSS
- OpenTicket (Enverus)
Maintenance, accounting & ERP
- IBM Maximo
- QuickBooks
- NetSuite
- SAP S/4HANA
Midstream: gathering, pipeline and marketing
Gathering and processing companies, pipeline operators and marketers keep detailed desk workflows for scheduling, measurement, settlements and compliance.
Who fits
- Gathering and processing companies
- Pipeline operators, including water midstream
- Crude, gas and NGL marketers
- Gas control, scheduling and measurement staff
- Settlements, accounting, regulatory, integrity, right-of-way and HSE staff
Records that count
- Nominations and scheduling workflows
- Measurement, allocation and balancing workflows
- Maintenance and integrity work orders
- Right-of-way and easement work
- Regulatory workflows (for example, PHMSA and Texas RRC)
- Settlement and invoicing workflows
- Operator qualification and training, email and Teams
Good to know
- Shipper and customer contracts are excluded as client agreements. Trading positions and pricing are commercially sensitive and are reviewed before anything is included.
- Security-sensitive details about pipeline systems aren't a fit.
Software these teams use
Measurement & pipeline
- FLOWCAL (Quorum)
- My Quorum Pipeline (QPTM)
- My Quorum TIPS
- W Energy Software
Marketing & trading
- Quorum eONE
- ION Allegro
- ION Endur (formerly Openlink)
Land and mineral work: contractors in your systems
Land work runs on years of email, title research, project tracking and mapping, and much of it is done by contract landmen working inside the firm's own systems.
Who this fits
- Lease brokers
- Land services firms
- Title and curative teams: runsheets, ownership reports and curative work
- Operators' land departments
- In-house GIS and mapping teams, which most brokers and land firms have
Why a small staff can still be worth a look
A broker with a handful of employees but many contract landmen working in its company email, Teams, Dropbox, billing and land or mapping software has a lot of documented work. Whether contractors count is up to the provider.
- A desk team: employees and contractors who work at a desk in your company's email and software. Field and hourly crews who aren't in the systems aren't the desk count.
- Several years of history in your systems.
- Work across systems, such as email, chat, file storage, CRM, tickets and billing.
- Requirements vary by provider, sector and dataset, and the provider confirms fit.
Records that can count
- Lease and title workflow emails with lessors, mineral owners, clients and contract landmen
- Project tracking: prospects, tract and lease status, title and curative progress
- Invoicing and billing workflows
- GIS mapping work: tract maps, lease and ownership maps, unit or spacing plats
- Runsheets and title databases, including Microsoft Access
- Land and mapping software history
Good to know
Work done for operator clients under master service agreements may belong to the client, not your firm. That doesn't rule you out; the provider's review sorts out what your firm has the right to license. How mineral owner and lessor personal details are handled belongs in the agreement, and passwords, financial reports and statements, and client agreements are excluded upfront. Workflow data from billing, QuickBooks, NetSuite and HR systems still counts.
Usually not a fit anywhere: data involving minors, export-controlled or classified data, mostly paper records with little digital history, or records you don't have the rights to license.
Land software your team already uses
Enverus and Quorum lead the list; most land teams are plugged into both every day.
Mapping & market intelligence
- Enverus (formerly Drillinginfo)
- Tobin
- Basinfoundry
- Greenbriar
- Canvas
- ArcGIS
Operator land systems & portals
- Quorum Land (Landdox)
- Peloton LandView
Lease acquisition & brokerage
- Landboss
- IFS iLandMan
- Bluetick LMS
- Pandell LandWorks
Courthouse & title research
- CourthouseDirect.com
- TitleTrackr
- Landman.ai
- MineralScout
- Microsoft Access (runsheet databases)
What counts is your team's own work in and around these tools: the emails, runsheets, notes, tract and lease tracking, the maps your GIS team builds, and your billing. Licensed third-party content, like Enverus well and production data, Tobin maps or courthouse images, belongs to those vendors and isn't yours to license. Work done inside a client's portal, such as an operator's Quorum system, may belong to the client. Your own emails, tracking and billing around that work are usually yours, and the provider's review sorts it out.
Product names are trademarks of their respective owners and are listed for reference only; no affiliation or endorsement is implied.
More for oil & gas owners and land firms: BlackGoldData.com (opens in a new tab).
Dan Smedstad has been a petroleum landman for 35+ years, so he speaks your language.
Good to know
- Working-interest partners and JOAs, operator-owned data on service jobs, and vendor data (such as EDR feeds or licensed well data) all come up in oil and gas. None of them rules you out; the provider's review sorts out what your company has the right to license.
- Reservoir data, seismic, interpretations and trade secrets aren't assumed licensable without review, and export-controlled technology isn't a fit.
- Kept out unless a review and the agreement say otherwise: privileged material and client matter files, health information and biometric data, payment card and bank account numbers, passwords and credentials, data about minors, export-controlled or classified information, another party's data or licensed third-party content, and sensitive personnel, safety or critical infrastructure details. Scope is a choice, so you can leave out anything else, such as pricing or trade secrets.
- Revenue statements count as financial statements and are excluded. Field tickets, invoicing, JIB and revenue distribution workflows, and QuickBooks, NetSuite and HR workflow data still count.
- Usually not a fit anywhere: data involving minors, export-controlled or classified data, mostly paper records with little digital history, or records you don't have the rights to license.
- This site doesn't ask for raw files, passwords, client examples or exports. If you sign an agreement, the agreed material is prepared and transferred under that document. How personal details are removed or replaced belongs in the agreement, and the provider's review sorts out what's licensable. When in doubt, it's worth a conversation.
See If You Qualify
A few quick questions. No files needed, and we never ask for passwords.
Opens the fit check on historypays.com in a new tab. No files are collected on this site.