Current solution: 16D BOP calculationRIGLOGICOS / SOLUTION 001
Solution 01 / Well control

16D BOP
calculation.

Check that a BOP control unit can close the stack it serves. Describe the preventers and the accumulator bottles in familiar units, and get a clear result benchmarked against API Annex 16D references. This page is intentionally concise while the product details are finalized.

Review offering Product spec in progress
How the 16D check worksClick a step or the highlighted equipment
API 16D
Drilling rig with the BOP stack and its control unit highlighted Side view of a land rig. Under the rig floor, the BOP stack sits on the wellhead. To the left, an accumulator control unit feeds hydraulic lines to the annular and ram preventers. The mast and choke manifold are drawn in grey because the 16D check does not cover them. WELLBORE 3,000 psi Mast & hoisting Choke manifold
Step 1 of 3 · Describe the BOP

Start with the BOP stack you actually have.

List each preventer on the stack, the annular and every ram, with the hydraulic fluid it takes to close and open, and the pressure it needs to close against the well.

You enter
  • Annular and ram preventers
  • Close / open volumes (gal)
  • Closing ratios
  • Choke and kill valves
Step 2 of 3 · Describe the control unit

Add the accumulator unit that closes it.

The control unit stores hydraulic fluid in nitrogen-charged bottles. As fluid is used, pressure drops, so bottle size and pressures decide how much of the stack the unit can close.

You enter
  • Bottle count and size
  • Nitrogen precharge
  • System and minimum operating pressure
Step 3 of 3 · Run the API 16D check

Can the unit close the BOP when it counts?

RigLogicOS works out the usable fluid in the bottles, runs the functions API 16D requires, and confirms pressure stays above the minimum operating pressure.

You get
  • Usable fluid volume
  • Margin against the requirement
  • Pass / fail with references
Covered by the 16D check On the roadmap Example values for illustration

A dedicated calculation path for BOP engineering.

RigLogicOS currently has one solution: a 16D BOP calculation. It is built for drilling and well-control engineers who need a faster, repeatable way to size and check BOP control systems, using the volumes and pressures they already work with.

The final production page can later replace these overview notes with the exact inputs, validation rules, benchmark evidence, and commercial details.

API Annex 16D benchmarkPositioned around API Annex 16D reference checks and benchmarked calculation behavior.
BOP-focused inputsPreventers, closing volumes and ratios, accumulator bottles, and operating pressures.
Clear calculation resultUsable fluid, margin, and pass / fail, laid out for engineering review.
Expandable product pageCopy is intentionally light so the final product specification can be added later.

From BOP inputs to benchmarked result.

Four steps, in the gallons and psi engineers already use.

01 / Describe

Enter the stack

Annular, rams, and hydraulic valves with their close and open volumes and closing ratios.

02 / Size

Add the control unit

Accumulator bottles, nitrogen precharge, system pressure, and minimum operating pressure.

03 / Check

Run the 16D check

Usable fluid is calculated and checked against what the stack's functions require.

04 / Review

Use the result

Pass / fail, margin, and the references behind each number, ready for review.

A result engineers can read at a glance.

Inputs and results stay in familiar units. Values shown are illustrative; the final input list, validation rules, and report format will follow the product specification.

Example calculationIllustrative values

Surface BOP control unit

Inputs
Accumulator bottles
10 × 15 gal
Nitrogen precharge
1,000 psi
System pressure
3,000 psi
Minimum operating pressure
1,200 psi
Fluid required by BOP functions
60.0 gal

Result

Fluid required by BOP functions60.0 gal
Usable fluid available75.0 gal
Pass · 15.0 gal marginPressure after closing: 1,364 psi, above the 1,200 psi minimum
Product note: required inputs, units, validation rules, supported standards editions, benchmark methodology, result fields, and availability should be updated here once the product is finalized.