Independent engineering assurance

A second opinion from someone who did not sell you the equipment.

Fixed scope, fixed deliverable, fixed fee — enough to know what you are buying before the first conversation.

Why independent

The model is usually verified by whoever wrote it.

In managed pressure drilling the service provider commonly designs the system, supplies it, operates it and verifies its own hydraulic model. That is not misconduct — it is how the market is organised, and the people fluent enough to review such a model are usually the people who built it.

The consequence lands on the operator. Without an in-house pressure-management specialist there is no practical way to challenge the basis of design, the operating envelope, or the assumptions underneath them — so they are accepted, and the first real test of them is the section itself.

That gap is what this practice was built for, and the reason assurance is the lead offer rather than one service among five.

Fixed-scope packages

Four packages, each answering one question.

Defined scope and a defined deliverable, so the engagement can be assessed before it starts rather than discovered as it runs.

6–8 days

MPD hydraulic model assurance

Does the model deserve the authority the operating plan gives it?

What is reviewed

Basis of design, and the assumptions the model actually rests on
Input data quality, units, and reference depths
Operating-envelope derivation and its margins
Model behaviour against measured well response, where data exists
Limits of validity — where the model should not be relied on

Deliverable

A written opinion stating what was checked, what was not, what the conclusion rests on, and what would change it. Findings ranked by materiality rather than by count.

10–14 days

Pre-spud readiness review

Are the well, the equipment, the model and the procedures one coherent system?

What is reviewed

Basis of design and model limits as a single system, not as separate documents
Equipment interfaces and rig integration
Fingerprinting plan, connection and tripping sequences
Well-control interface and contingency logic
Procedures and operational-readiness requirements against all of the above

Deliverable

Prioritised findings with a clear readiness basis, in time to act on them. Each finding states the consequence of not addressing it, so the operator can decide what matters.

8–12 days

Post-well and campaign diagnostic

What actually happened, and what should the next well do differently?

What is reviewed

Measured pressure response against what was predicted
Connection, loss and influx events, separated from model artefacts
Where the operating strategy held, and where it did not
Data and instrumentation quality, including what could not be concluded
Recommendations carried into the next well as specific changes

Deliverable

A diagnostic that separates observation from interpretation from recommendation, so a reader can disagree with the conclusion without losing the evidence.

4–6 days

Mud gas separator capacity assessment

Which limit governs the separator, and how much margin is left?

What is reviewed

Operating pressure: vent losses, elevation and liquid seal together
Gas venting through the as-built vent line and fittings
Gas-liquid separation, and the limits of the sizing method
Liquid handling: carry-under, outlet velocity, liquid level
Sensitivity to mud weight, gas gravity, rates and restrictions

Deliverable

The governing limit and its margin for every case, plus an operating-limit summary for procedures, influx management envelopes and MPD operating matrices. An engineering analysis — not certification or inspection.

Each package is a fixed fee against the scope above — not an hourly estimate that moves. Scope is already defined here, so a quotation needs a short description of the well and the constraint, not a scoping call.

What you receive

An opinion you can act on, and audit afterwards.

What was checked — and what was not

Scope stated explicitly at both ends. The omission a reader is never told about is the one that misleads, so the boundary of the review is part of the deliverable.

The basis, and its limits

What the conclusion rests on, and what would change it. A finding that cannot be traced back to evidence is an opinion wearing a report’s clothes.

Findings ranked by consequence

Ordered by what happens if they are not addressed, not by how many there are. A long list is easy to produce and hard to use.

Observation separated from interpretation

So you can accept the measurement and still disagree with the reading of it. That distinction is most of what makes a second opinion worth commissioning.

Independence standard

The adverse finding still gets written.

Assurance is accepted only where an adverse conclusion can be reached, written, delivered to the party relying on it — and still paid for. No fee depends on the outcome. No contract may let the commissioning party approve, edit or suppress a finding. The practice does not review engineering work its founder delivered, here or in a previous role, and takes no commission, agency fee or financial interest from any vendor whose scope it assures. Where a vendor commissions verification of its own work, the operator is told in writing and receives the full report.

How it runs

Four steps, and no scoping call needed to start.

Describe the decision

The well, the constraint, and what has to be decided. A short written exchange establishes whether this is even the right instrument.

Fixed scope agreed

What is in, what is out, what the deliverable is, and by when — in writing, before any work begins.

Review

Conducted against the agreed scope. Factual corrections are welcome at any point; conclusions are not negotiated.

Opinion delivered

Written, with the basis stated, followed by a working session if that is useful — priced in the same quotation, so there is no second negotiation.

A decision that needs a second opinion?

Describe the well and the constraint. A short exchange is usually enough.

Discuss a requirement