Optimizing TMS Launch and Recovery: Reducing Nonproductive Time Offshore
Practical strategies for experienced ROV pilots to minimize TMS launch and recovery NPT: weather windows, heave compensation, garage operations, A-frame vs moonpool trade-offs.
Launch and recovery operations are where campaigns win or lose time. An ROV that is in the water working is generating value; an ROV sitting in the hangar waiting for a weather window, or recovering slowly due to a poorly optimized procedure, is burning vessel day rate. For experienced pilots and supervisors, the focus should be on the controllable variables — the preparation, sequencing, and decision-making that determine how efficiently the TMS and ROV move through the water column, regardless of conditions.
Pre-Launch Preparation That Actually Saves Time
The time saved in pre-launch preparation is always larger than the time spent on it. A full system function test completed before the deck crew is standing by, a fiber check done while the deck is being rigged, tooling configurations verified against the work pack before the crane is engaged — each of these steps eliminates a delay that would otherwise occur at the worst possible moment. Experienced teams develop a pre-launch checklist that is specific to their system and their vessel, not a generic OEM list, and they execute it consistently regardless of how routine the dive appears.
Weather Windows: Quantitative Decision Making
The transition from 'launch when it looks acceptable' to 'launch when the numbers say it is safe' is one of the key cognitive shifts for an experienced supervisor. Your TMS has a design limit for sea state, usually expressed in significant wave height. But the operational limit depends on vessel motion, which depends on vessel heading relative to swell, which depends on the job you are doing. A moonpool launch is far less sensitive to wave period than an A-frame stern launch. A good pre-campaign exercise is to get the vessel motion data for your specific vessel in the expected sea states and translate those into practical go/no-go criteria for launch and recovery. Generic sea state limits from the OEM are a starting point, not an operating envelope.
Heave Compensation: Using It Correctly
Active heave compensation on modern LARS systems is not a substitute for good seamanship — it is a tool that extends the operational envelope. The common misuses are: activating heave compensation too late in the water entry phase, where the ROV is already in the splash zone and the compensation system is trying to catch up with a dynamic load; and relying on heave compensation to manage a TMS that is too heavy for the sea state, instead of addressing the sea state as a genuine constraint. Heave compensation also has a bandwidth limit — it can handle slow, predictable vessel motion effectively, but fast irregular motion from crossing swells in confused sea states will exceed the system's ability to compensate. Know your system's actual performance envelope, not the theoretical one.
Garage Mode Operations: Sequencing for Efficiency
- Complete all ROV-side function checks before entering the garage — checks after the ROV is docked add time at a critical phase
- Establish communications and USBL lock on the ROV before garage release — loss of comms immediately after release is common and wastes time reestablishing
- Brief the decision point for aborting the launch before the garage opens — once committed to water entry, decision-making under pressure degrades
- In TMS garage operations, standardize the docking approach heading relative to TMS orientation — inconsistent approaches increase docking time and risk damage
- Log the actual time from deck to depth and depth to deck on every dive — trend analysis reveals whether your procedures are improving or degrading
- Have a clear procedure for a failed dock on the first attempt — improvising this procedure while the TMS is moving is not the time to think it through
A-Frame vs. Moonpool: Optimizing for Your Vessel
If you have a choice of LARS configuration, the decision depends on your operating environment and task type. Moonpool operations are generally superior for deepwater work in open ocean conditions — the vessel hull shields the TMS from surface wave action during water entry and recovery, and the controlled environment reduces weather dependency. A-frame stern launches give better access for deck operations, easier camera visibility during recovery, and are standard on many multi-purpose vessels where a moonpool is not available. Supervisors who have operated both configurations develop a preference, but the real skill is adapting your procedures to work efficiently with whatever configuration the vessel provides.
Common Delays and Systematic Prevention
- TMS tether management: pre-rig tether deployment before launch rather than paying out during descent
- Communication checks failing after splash: eliminate by doing a full comms check at the quayside or before deck handover
- Deck crane availability: coordinate with the deck team and crane operator before the dive, not during
- Tooling not function-tested before deployment: run a full tooling function test as part of pre-dive checks every time
- USBL not tracking before water entry: configure and confirm USBL lock at surface before committing to launch
- Recovery delayed by current: identify the current direction before recovery begins and plan the approach accordingly
- Night operations without adequate deck lighting: identify lighting gaps during daylight and address before you need them
Logging Launch and Recovery Data for Campaign Analysis
Every launch and recovery generates data that can improve the next one. Total LARS time, water entry time, time to working depth, recovery time, and any delays with their causes should be systematically logged for every dive. Over a campaign, this data reveals where time is being lost and allows you to target specific improvements. Supervisors who track this data in structured dive logs — rather than relying on memory or rough notes — consistently demonstrate measurable reductions in NPT over the campaign duration.