Model assurance & calibration
Compare models with operational evidence, identify material input assumptions, recalibrate responsibly and communicate limitations.
Technology
Build the decision layer around existing engineering systems.
The industry does not need another generic AI promise. It needs traceable engineering tools that solve identifiable operational problems.
Direction
Drilling Engineering Intelligence
A focused category combining physics, engineering models, operational data, engineering rules, specialist knowledge and carefully governed AI assistance.
01
Observe
Organize relevant signals, operating state and data quality.
02
Contextualize
Connect data to well conditions, engineering models and execution constraints.
03
Interpret
Apply engineering rules and specialist judgment while preserving uncertainty.
04
Act
Provide clear, traceable recommendations with measurable triggers.
Diagnostics & surveillance
Structure connection, fingerprinting, loss/influx, tripping and operating-window analysis into repeatable, reviewable workflows.
Engineering workflow QA
Support calculation traceability, document consistency, risk review and explicit separation of observation, interpretation and action.
Decision support
Encode measurable triggers, engineering logic and operational trade-offs without hiding the assumptions behind an opaque interface.
Technology principles
Engineering accountability stays visible.
01
Traceable calculations
Inputs, assumptions, methods and limitations remain reviewable.
02
Human technical authority
Tools support judgment; they do not conceal or replace engineering responsibility.
03
Fit-for-purpose scope
Every workflow begins with a defined decision, user and operating context.
Application portfolio
Software built for a decision that was being made without evidence.
Each application exists because an engineering judgement was being made on something other than the measurement that could have settled it.
Data shown
Screenshots use synthetic or published data. No client record, well, result or proprietary method appears in any image on this page.
01Model assurance
Anadromiki
Turns a real drilling record into a simulator batch schedule, then grades the simulation against what the well actually did.
A transient hydraulics model sets the pressure targets a narrow-margin section is drilled to. Whether the model deserved that authority is usually answered afterwards, by eye, from a simulated curve laid over a measured one — which is an impression rather than a result. The loop between what was predicted and what the well did is rarely closed, and almost never closed the same way twice.
01
Import the record
A time-indexed LAS, or a CSV export from a rig-data system. Channels are mapped to roles automatically, and a built-in profile takes over where a name match reaches the wrong answer.
02
Build the schedule
The record is segmented into rig states, cropped to the simulator’s starting bit depth, and written as a batch grid that goes straight into the simulator.
03
Grade the run
The measured PWD is scored against the simulation — bottomhole pressure, ECD, standpipe pressure, downhole and return temperature — split by pump state. Several runs are held at once, so a calibration is a series of trials rather than a single answer.
Where it refuses to help
It will not let a bad sample become a trend
A PWD frame reporting 32,562 psi is held forward across roughly 115 rows by ordinary gap-filling, and six such readings moved a graded bias by more than half. A sample is dropped only if it is statistically absurd, physically material for its unit, and returns to where it came from — so connections and pump shutdowns, which are the point of the analysis, survive untouched.
It will not assume a unit
A torque channel declared in 1000 ft·lbf written into a column headed lbf-ft is a thousand-fold error that nothing downstream would notice. Units are converted at the door and an unrecognised one is reported, never guessed.
It will not average away the event
After segmenting, each run is asked what it still conceals, and the ones hiding a real change are split at their steepest transition. An MPD connection sweeping the choke over five minutes becomes a staircase rather than one averaged row.
It will not quietly correct anything
Where the simulation and the PWD tool report at different depths, the difference is measured from the loaded files and stated — in psi and in ppg — and no number is adjusted. The engineer decides what to do about it.
Hydraulic model calibrationPWD interpretationRig-state segmentationPost-well review
A workflow worth improving?