The 14-day BOP test cycle, per API STD 53 — every active rig in the GCC, every two weeks, on the chart.

Every active drilling rig in the GCC runs on a clock that the rig manager did not choose. API STD 53 writes that clock — every 14 days the BOP stack comes off well-control duty for a full pressure-test sequence. Skip a cycle and the well-control insurance walks. Run it badly and the operator HSE rep does not sign the chart. The rig does not turn until that signature is on the page.

The test sequence itself is not negotiable: low-pressure phase at 250 — 350 psi held 5 minutes per cavity, high-pressure phase at full rated WP held 10 minutes per cavity, annular tested on every pipe and casing OD in use, blind-shear ram seal plus bore-isolation function, choke and kill manifold per API 16C, wellhead seal, full chart-recorder traces, sour-service test fittings, third-party witness on operator request. Aramco's revised 2023+ Well Control Manual tightened the H₂S clauses; ADNOC SPC and PDO followed inside a year. The work is not getting smaller.

This is the most-bought BOP service in the GCC — by frequency, not by ticket size. Operators do not ring us about the test cycle the way they ring about a recert. They ring us once. They put us on the rotation. From there we live on the rig schedule, not the phone.

A test cycle on a 10K stack typically runs one full day on the rig. We start with the low-pressure phase — 250 — 350 psi held for 5 minutes per cavity — to seat the elastomers and prove the seal at the floor where casual leaks live. Then the high-pressure phase — full rated working pressure (5,000 / 10,000 / 15,000 psi depending on stack class) held 10 minutes per cavity. Every annular preventer is tested on each pipe OD and each casing OD in current use. Blind-shear rams get a seal test and a bore-isolation function. The choke and kill manifold is sequenced through every operating valve per API 16C. Wellhead seal goes through the same envelope. Every step is logged to the chart with timestamps and operator initials.

Test fittings are NACE MR0175 / ISO 15156 sour-service by default — HNBR and FKM elastomers, 316 SS manifold, B7M / L7M bolting on the test cap. The chart recorder is calibrated against a 0.05% full-scale reference dead-weight tester before mobilisation and again on return. When the operator wants TUV, DNV or Lloyd's on the floor for the test, we book the witness inspector through their GCC office and align the test schedule to their availability. Witnessed tests get an extra signature page and a notarised cover sheet.

The chart is the deliverable. Not the seal. The seal is what we tested — the chart is what the auditor reads three years from now when something on the rig went wrong on a different day. "We tested it" is a sentence. "Trust me, the chart shows it" is a document.— Khalid Al Marzouqi · BOP Test Supervisor (IWCF Level 4) · Jebel Ali

Every Indus pressure-test engagement runs through the same four phases. The cycle does not change between operators or stack classes — only the cavity count and the WP envelope.

Below is the standard procedure that governs an Indus pressure-test engagement. The full SOP runs 22 lines plus a calibration annex. This is the abridged set that gets ticked, signed and stapled to the chart on every job.

Across the rolling rotation we run hundreds of cycles per year on stacks across KSA, UAE, Iraq and Oman. The table below is what an Indus crew typically finds and corrects on an in-cycle test of a stack in good service. Three of these are the recurring critical catches — they fail an audit if they go unaddressed and they are the main reason the standard requires the test in the first place.

When an operator places Indus on the pressure-test rotation, the work moves out of the phone log and into the rig schedule. We arrive on the cycle date, run the standard, hand the company man the chart and the PDF before tour change, and the rig is back on well-control duty by the next morning. Across a year a single rig will run roughly 24 — 26 cycles on the 14-day cadence (or 17 — 18 on the 21-day variant under some operator standards). Indus crews typically run 200+ cycles per year across the rotation, which is the volume base under the API STD 53 documentation discipline.