A fixed-scope evaluation
Evaluate one subsurface workflow on a real asset.
For upstream E&P operations and subsurface teams with a well or survey in mind and one operational friction point to examine. Start with a narrow scope, agree on the inputs and review method, then evaluate the in-scope outputs over 90 days.
Request a demoFixed-scope, 90-day evaluation · 1–5 wells · one basin
Permian pilot: evidence and gaps
What the readiness finding verifies—and what still depends on your data
The finding “Validate Orogen's readiness for the researched Permian pilot workflow” is not available in the materials for this page. No Permian workflow capability is presented here as verified by that finding.
A fit assessment for your workflow depends on the customer data and access available. The Permian walkthrough is explicitly illustrative; it does not establish that the researched workflow has been validated for your operation.
Readiness checklist
Ready to discuss the researched Permian workflow?
The completed readiness review is not available here, so its criteria cannot be listed accurately.
Permian workflow · research scenario
A researched workflow, presented as a hypothesis
The named capability-readiness finding is unavailable; no Permian workflow capability here is presented as verified.
Permian / Delaware / Wolfcamp geology and WITSML / SCADA are research and workflow context, not evidence of Orogen capability. Each step depends on customer data and access; the sequence is not a validated milestone plan or a promise of outputs or dates.
- Day 1
Proposed connection
Assess the operator’s existing WITSML store or stream
Example surface and downhole pressure, flow rate, ESP load, and SIBR channels would be aligned to a shared time index.
Confirm channel names, formats, cadence, and access with the operator. Orogen’s WITSML connection is not verified.
- Days 2–3
Proposed review
Review the first 48 hours
Proposed per-curve rolling baselines, including an A-annulus casing-pressure window using the operator’s offset-well data.
~40 psi · illustrative basin-noise assumption
250 psi · illustrative existing SCADA-alarm assumption
Both are unverified assumptions—not measurements, Orogen thresholds, or recommendations.
The baseline review and any threshold envelope are proposed and depend on operator data and review.
- Day 5
Hypothetical scenario
Review a possible A-annulus change
A hypothetical +80 psi above a 90-minute rolling baseline, below the example 250 psi SCADA alarm; compare sustained drift with a spike-and-recovery pattern.
A candidate for operator review only—not a verified detection, diagnosis, field measurement, or intervention instruction.
- Week 2
Possible operator review
Triage alerts with the night foreman
A possible 30-minute operator/night-foreman review of false positives, suppressed or escalated alerts, and threshold changes by tens of psi.
Operator sign-off comes before any change. The review, alerts, and changes are illustrative—not verified or promised.
- Week 4
Proposed report
Summarize the prior seven days
A proposed one-page report could cover the production trend, water-cut delta, casing pressure, possible agent commentary, and raw trace windows.
Illustrative and customer-data/access dependent—not a verified or promised output or date.
How the pilot is scoped
A defined question, agreed inputs, and a reviewable measure.
- 01
Choose the workflow
Identify the well or survey, the operational friction point, and the team member who will review the outputs. A focused starting scope is one well, one survey, and one friction point.
- 02
Agree on data and access
Together, identify the relevant source data and context, then confirm formats, access, and handling before any proprietary files are shared. The exact technical inputs depend on the selected workflow.
- 03
Run the fixed-scope evaluation
Evaluate the agreed workflow within the Pilot tier's single-basin, 1–5-well scope over the published 90-day window. The proposal defines the included work and review process.
- 04
Review outputs against a rubric
Use an agreed rubric to review the in-scope outputs with the buyer. Set what counts as useful or actionable and the numeric target before the pilot begins.
What to bring
Start with context, not an upload.
The request-demo form collects your basin, well-count band, and a short monitoring note. It does not accept technical data uploads; do not send proprietary files through it.
A candidate well or survey
Name the asset or survey you would like to evaluate and the basin it belongs to.
One operational friction point
Describe the decision, handoff, or monitoring question you want the pilot to examine.
Relevant data and context, agreed in scoping
Exact source types, formats, access, and handling are confirmed with the team before the pilot. This page does not assume a particular feed or connector.
Proposed success measure
A proposed measure is the share of reviewed, in-scope workflow outputs the buyer accepts as useful or actionable during the agreed evaluation window.
Proposed acceptance rate
Outputs accepted by the buyer ÷ in-scope outputs reviewed
Agree on the review rubric, evaluation window, and numeric target before the pilot begins. This is a measurement method to propose, not a guaranteed result.
Buyer FAQ
What to clarify before you scope the pilot.
The answers below combine the published Pilot boundaries with a qualified Permian workflow walkthrough. The research examples show one possible shape of the work; they are not customer commitments or guaranteed outcomes.
Start with a scoping conversation
Bring the basin, well band, and workflow question.
Request a demo to discuss fit and define the pilot scope. The form is for scoping only; technical files and data-access details are handled separately if you proceed.