Limited published evidence · Oil and gas
Well-report extraction and well-history preparation
Petoro and SLB
Implemented applications with preliminary user testing reported; broad production rollout is not established.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
What the source reports
SLB describes Well Schematic Extractor and Well History applications for well planning. LLM-based agentic workflows extract engineering information from reports and logs, with deterministic checks and visual quality control.
Reported technology: SLB; underlying model provider not specified. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
- Systems and tools
- Proposed: Use a controlled well-document workspace, extraction tools and an engineering review interface.
- Data and state
- Proposed: Preserve well identity, document revisions, casing/completion information, units and source locations.
- People and handoffs
- Proposed: Drilling or reservoir specialists validate the extracted representation before planning use.
- Rules and authority
- Proposed: Keep extraction separate from authority to approve a well plan or operate field equipment.
- Normal and exception cases
- Proposed: Include illegible logs, inconsistent depths, mixed units and conflicting historical documents.
- Reset and replay
- Proposed: Freeze document bundles and reference schematics so revised extraction can be compared.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Extract a well-history package from inconsistent reports and prepare a traceable schematic for engineering review.
Review gate: Specialists can reconcile material values, units and provenance, with unresolved discrepancies explicitly held for review.
Challenge the result: Supply two incompatible depth references; a confident merged schematic must fail the engineering check.
What needs checking
- Proposed: reconcile extracted fields against engineer-approved schematics and source references.
- Proposed: test depth/unit consistency and missing-information escalation independently of a fluent well-history summary.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- User count, test duration, extraction accuracy and production deployment breadth are not supplied.
- The page displays 06/05/2026; its numeric date convention was not resolved, so no exact publication date is asserted.
- This is an early or limited-evidence example, not proof of autonomous drilling, field control or operating approval.