search
close
For example "Webinars"

Data Maturity Before AI: What Oilfield Services Need

Data maturity decides what AI can do for an oilfield service company. AI needs your data at Level 3 or higher on a five-level scale, and the road there starts at the field ticket. That was the message RigER CEO Michael Maltsev took to the main stage at Future AI | Oil & Gas in Houston on November 17, 2026. His session title put it in one line: “AI Can’t Fix What the Field Never Captured.”
Why the field ticket decides what AI can do
We started RigER in 2012 to digitize oilfield services and rentals. Fourteen years and more than 200 field implementations later, the job is the same. Capture the work in the field, move it to the cloud, and turn it into numbers an owner can act on.
The field ticket is still the core record. It holds the equipment, consumables, people and location for a job, and the invoice and utilization reports are built on top of it.
“If the ticket is wrong or late, every report built on it is wrong or late,” Michael told the room. An AI tool working from those reports inherits the same errors.
From field to boardroom
Michael walked the audience through the path a job’s data takes:
  • Technicians capture tickets on a phone, online or offline.
  • The office runs dispatch, approvals and invoicing.
  • Owners see the dashboards.
In a lot of companies, those steps still live in different places. The quote sits in email, the job on a whiteboard, the ticket in a truck and the invoice in the accounting system.
What is data maturity?
Data maturity is how far a company’s data has moved from paper and memory toward structured, governed records that software and AI can work with. Michael’s model splits that path into five stages.
image
The five-level data maturity model
Each level below shows what the data looks like and the kind of AI it can support:
Level 1: Paper and memory. Carbon-copy tickets, whiteboard dispatch, pricing in people’s heads. AI can do nothing here.
Level 2: Digitized, not structured. PDFs and photos, spreadsheets, group texts. AI still can do nothing.
Level 3: Structured and connected. Mobile tickets, master data, a price book on the ticket. AI can do descriptive analytics.
Level 4: Governed and integrated. Data owners, validation, audit trail, ERP integration, KPI tracking. AI can run predictive models and assistants.
Level 5: AI-ready and agentic. Event-level history of jobs, assets and crews. AI can run agentic workflows with human control.
What it takes to reach Level 3
Mobile tickets, master data and a price book on the ticket get a company to Level 3. Michael added two more things: one asset ID and one person accountable for data quality.
Trace one job before you buy AI
To find where your own data breaks, Michael suggests a simple exercise in his article Before You Buy AI, Just Trace One Job , first published in Future Digital Twin on November 16, 2026.
  • Pick a job you invoiced last month.
  • Trace it through quote, job, ticket, invoice and payment.
  • On one sheet, write down the date, the time and the person at each step.
  • Take the sheet to your next management meeting.
  • Find the longest gap between two dates and fix that handoff first.
A typical sheet shows 30 to 60 days between the signed ticket and cash in the bank, with four or five people keying the same job into different files.
Start narrow, and build for the crew
Once the data holds up, Michael’s advice is to start with narrow AI: one tool doing one job while a person checks the result. In RigER, AI reads a photo or PDF of a handwritten paper ticket and drafts the documents that ticket needs. A dispatcher or operations manager reviews the drafts, and nothing posts until a person approves it. The RigER 14.0 Austin release has the details.
The best narrow tool still fails if crews don’t use it. With the RigER mobile app, crews can complete tickets and collect signatures at the wellsite without a signal, and the data syncs when the connection comes back.
Capture, connect, decide: our roadmap
Our product roadmap follows the same order as the maturity levels.
Capture (live). Digital field tickets, dispatch, sales and approvals on the phone, online or offline.
Connect (live). One chat per job, with the ticket flowing to accounting and e-invoicing.
Decide (concept). CoDispatch: AI proposes crews, units and times, and a person approves.
Fix the data first. Then add AI. The field ticket is still the core record: the equipment, consumables, people and location. If that ticket is wrong or late, every report built on it is wrong or late too, and AI can’t fix that. So the work starts in the field, with mobile tickets, master data and a price book on the ticket. Add one asset ID and one person accountable for data quality, and the company reaches Level 3, the minimum AI needs.

Recent posts

Show all
close
Subscribe to blog