Faisal Al-OtaibiSenior Well Test Engineer

Design of Service packages

Surface well testing. Every package is calculated from one input model against the governed assumptions register.
Open the worked example
DOS-SWT-2026-0147 · Rev 2

JBL-0142 · Jubaylah

Saudi Aramco — Post-Stimulation Flowback
Status IN REVIEW
QA 11 pass / 2 caution / 1 fail
Target liquid4,500 bbl/d
H₂S1,850 ppm
Reservoir pressure4,250 psi
Planned start2026-10-06
DOS-SWT-2026-0151 · Rev 0

SHB-003 · Sahba

Kuwait Oil Company — HP/HT Exploration DST
Status DRAFT
QA 11 pass / 1 caution / 2 fail
Target liquid1,200 bbl/d
H₂S12,400 ppm
Reservoir pressure9,850 psi
Planned start2026-10-19
DOS-SWT-2026-0139 · Rev 1

QDM-0221 · Qidam

ADNOC Onshore — Extended Well Test
Status APPROVED
QA 11 pass / 2 caution / 1 fail
Target liquid6,200 bbl/d
H₂S85 ppm
Reservoir pressure3,100 psi
Planned start2026-09-02

What this replacesdemo context

Today each of these packages is assembled from a chain of separate spreadsheets and a Word template: one file for choke sizing, another for separator capacity, a third for the flare layout, each carrying its own copy of the constants and its own author's judgement. Nothing checks that the numbers in one agree with the next, and nothing records which version of which assumption was used.

Here the well is described once. The calculations run in dependency order from that single description, every constant is drawn from a register that is owned and versioned rather than typed in, the design limits are checked automatically against the published standards, and the client document is generated from the same numbers that were checked — not retyped into a template afterwards.