Ingestion
Vendor reports arrive as PDFs and leave as structured inspection records. Extraction is verified before anything counts.
Upstream oil & gas · Vendor & custody-transferred equipment
Integrity management for assets that move.
Drillstring, tubulars, BOPs, lifting gear, subsea packages — cycling through vendor shops, yards and rig sites, inspected to stricter criteria than fixed plant, with the records scattered across vendor PDFs and email threads. Probe holds every inspection an asset has been through, across vendors and campaigns.
Invited by an operator? Create your account.
Gansar/Well A-2/INS-2291Scheduled
Wellhead christmas tree — pressure & function test
NOI-4471 · Raised 04 Aug 2026 · Regional scope: Sarawak
- Siti Rahman assigned Kumar Devan as third-party inspector · 06 Aug, 09:14
- Hikmah Energy uploaded 4 documents to the scope of work · 07 Aug, 15:02
- Kumar Devan confirmed attendance for 12 August · 08 Aug, 08:41
The gap
Plant AIM stops at the fence.
Inside the fence, integrity management is mature: an asset register, corrosion loops, interval-based inspection plans. The equipment that moves never fits that model — inspections trigger on custody and mobilization, not calendar dates, and the reports are produced by vendors, adjudicated by you. Probe is not a replacement for plant AIM. It is the system of record for everything plant AIM was never built to see.
Origin
Probe was built inside the wells QAQC department of a national oil company — an operator with enterprise AIM fully deployed, still coordinating vendor inspections over email. It proved itself on live projects there, and the regulator now backs its adoption across the industry.
- NOI
- SOW
- TPI
- NCR
- CAPA
- MATCO
- LOADOUT
- DS-1
- API RP
- OCTG
How it works
Adjudication
Acceptance criteria from DS-1 Vol 3 and API RP standards are encoded as structured rules and evaluated deterministically. No LLM sits in the pass/fail path.
Record
One canonical home per operator for every inspection an asset has undergone — across vendors, across campaigns, referenceable at mobilization time.
The chain
From notice to close-out, without leaving the record.
The wells QAQC workflow is where Probe started, and it runs end to end: each stage hands off to the next inside the same inspection. Nobody re-keys a reference into a spreadsheet, and nobody asks which version of the report is current.
Stage 01
Notice of inspection
The vendor files an NOI against a project and well, attaches the scope of work, and the clock starts.
Vendor
Stage 02
Assignment
A coordinator assigns an inspector by region and competency. Everyone named on the record is notified.
TPI coordinator
Stage 03
Attendance
The inspector attends on site and captures findings, readings and photographic evidence against each item.
Third-party inspector
Stage 04
Report
The TPI report is authored in place and submitted inside the 48-hour window. Late submissions are flagged, not buried.
Third-party inspector
Stage 05
Outcome
A pass closes the inspection. A fail raises a non-conformance report against the vendor, on the same record.
Operator
Stage 06
Corrective action
CAPA tracks the fix to close-out, so a non-conformance ends in evidence rather than an email thread.
Vendor & operator
Platform
A quality system built around the inspection.
Every stage of the chain is first class here — the notice, the report, the non-conformance, the corrective action, and the materials that move because of them. Configured to your projects, regions and roles in weeks, not quarters.
Third-party inspections
The full TPI flow — NOI, assignment, scope of work, attendance, report — scoped to a project, a region and a well.
Non-conformance & CAPA
Raise an NCR straight from a failed inspection, assign the corrective action, and hold it open until the evidence lands.
Material coordination
Loadout lists, material requests and delivery orders, so what was inspected and what shipped are the same list.
SLA & performance
Average report time per inspector, pass rate per vendor, and every breach of the 48-hour window — without exporting to a BI tool.
Documents of record
Scopes of work, certificates and evidence attach to the inspection they belong to, versioned, with a PDF export of the whole file.
Vendor self-inspections
A guided wizard for vendor-run inspections against a loadout list, with evidence uploads the operator can audit later.
Who it's for
Four parties, one record, four different views of it.
An inspection is a shared object with unequal rights. Probe models that directly, so what someone can see and change follows from who they are and which project they are on.
Operator
Runs the wells
- Create projects, scope regions, assign the team
- Watch SLA and vendor pass rates in one place
- Raise and close non-conformances
Vendor
Owns the equipment
- File notices of inspection and attach the scope
- Run self-inspections against a loadout list
- Answer an NCR with documented corrective action
Inspector
Attends and reports
- See only the inspections assigned to you
- Capture findings and evidence item by item
- Author and submit the report against the clock
Regulator
Reads everything
- Full visibility across operators and projects
- Reports and non-conformances as filed
- Read-only by design — nothing to edit, nothing to dispute
Assurance
Built for the people who audit the auditors.
- Deterministic adjudication
- Pass/fail is computed from encoded acceptance criteria, not generated. AI extracts and reconciles at the edges; it never judges.
- Verified extraction
- Every structured record extracted from a vendor report is verifiable against the source document it came from.
- Role-based access
- Access is granted per project and per inspection, not per account. A cost controller sees a whole project read-only; an observer sees one inspection.
- Complete audit trail
- Every assignment, upload, edit and status change is attributed and timestamped on the record itself, and exports with it.
- Single sign-on
- SAML and OIDC against your existing directory, with domain-scoped invitations for the vendors and inspectors outside it.
- Data residency
- Regional hosting for operators with in-country data requirements, or a self-hosted deployment inside your own perimeter.
- Exportable by default
- Inspections and reports export as PDF for the file, and the underlying data stays available over an API. Nothing is held hostage.
See it against your own equipment.
Bring one live project. We will walk an inspection through it end to end, in about thirty minutes, and you can decide from there.