BOP Control Selection: Pressure Ratings and Usable Fluid

One pressure column is not enough

A BOP and its control unit can each have more than one pressure-related entry. Putting all of them in a single quotation column called "pressure rating" obscures which boundary the number describes. Before comparing offers, name the equipment, identify the pressure domain and retain the manufacturer's original label.

This guide concerns purchasing documents, not well-control operation, accumulator charging, pressure testing or maintenance. Those activities require qualified personnel and the applicable controlled procedures. The examples below do not approve a stack or specify operating setpoints.

Separate the three document fields

The Rongsheng FH28-70 annular reference lists a wellbore-side working-pressure rating and a distinct rated hydraulic-control working pressure. The FKQ240-3 surface control-unit reference has its own system working-pressure entry. The values and source locations are reproduced in the model-reference table below.

Matching two numbers is not a selection method. A pressure value can describe a rated limit, a system specification or an operating requirement. Their labels and documentary scope determine whether the comparison is meaningful.

Usable fluid is not the bottle size

The control-unit source explicitly identifies nominal usable accumulator fluid. Rewriting that field as total accumulator capacity loses information. Geometric volume and fluid available over a defined operating interval are different quantities.

For a bid review, ask the proposed manufacturer to supply its usable-fluid calculation with the relevant pressure, temperature and precharge assumptions. Also request the actual controlled devices and their documented fluid demands. This guide intentionally provides no universal conversion from bottle volume to usable fluid and no substitute for a stack-specific sizing calculation.

Function count is a screening field

A catalogue function count can help identify the intended control scope, but an equal count does not prove that two stacks require equal fluid or meet the same performance criteria. Keep the named devices, interfaces and required functions visible in the RFQ.

An assumed example illustrates the document issue: two bids each list the same number of functions, but only one identifies the controlled models and provides a calculation basis. The first action is to obtain the missing basis from the other bidder, not to declare either bid technically acceptable. This is a document-review scenario, not a report of a field installation.

Treat certification as an order-specific question

The Rongsheng control-unit page requests the BOP-stack configuration and parameters for selection calculations when API-monogram supply is required. That instruction does not establish current licence coverage for every model or prove that an offered unit is already certified.

Record the required standard and edition, manufacturer identity, product scope and documentary evidence separately. Use the standard-edition checklist for the version check; it does not replace verification of an offered product's actual scope.

A clearer RFQ package

Attach the approved stack schematic, named equipment list, required control functions, site utilities, interface drawings and acceptance requirements. Ask the bidder to return its controlled circuit drawings, sizing basis, deviations and proposed test documentation.

In the comparison sheet, keep columns for the requirement, offered configuration, document revision, open clarification and technical disposition. A missing assumption should remain visible until resolved. Carry the reviewed requirements into the RFQ Builder; attach private project files through the inquiry form rather than publishing them as source material.