Defined checks. Named responsibilities. Documented acceptance.
Planned verification
Make the installed arrangement and its interfaces reviewable.
Connect the physical system to the agreed design.
Review the configuration, flow paths, connections, utilities and boundaries with rig equipment and other services. Document differences from the agreed scope, their disposition and the responsible parties.
Establish the records behind the measurements and indications.
The project determines the verification required for instrumentation and indications. Relevant records, configuration and limitations form part of the operating team’s information.
Agree the checks, witnesses and acceptance evidence.
The project-specific commissioning program establishes methods, responsibilities and criteria. Results are recorded against that program and linked to the configuration reviewed.
A defined decision
Give commissioning a clear place in the work.
Charger commissioning is explicitly scoped and charged.
Agree who accepts the work, what evidence supports acceptance and how findings or unresolved items affect the decision. The handover carries the accepted configuration, relevant records, operating responsibilities and outstanding actions.
Allen brings commissioning experience from offshore operations into Charger’s land work. The application is adapted to the actual rig, service arrangement and project requirements.
API RP 92S addresses subsea-BOP surface-backpressure MPD. Its commissioning context is a reference, not a land-operation requirement.
People and continuity
Keep the next person and the next operation in view.
Agree who installs, commissions, accepts and operates.
A drop-off scope identifies the delivery boundary and the parties who take the equipment forward. Equipment delivery alone does not establish operating readiness.
Connect Charger’s duties with the wider rig team.
Define operating authority, communication paths and coordination among Charger, the operator, the drilling contractor and other services. Make the information needed at each interface clear.
Carry changes, limitations and open actions across the shift.
A useful handover records the relevant system state and changes, the reasoning that matters to the next activity, and the people responsible for outstanding work.
