Greensea OPENSEA: Open-Architecture Control Systems and the Future of ROV Piloting

For most of the ROV industry's history, control system architecture has been a closed shop. Schilling's MISO, Forum's VMAX, and similar proprietary platforms each dictate the sensor suite, autopilot algorithms, and operator interface on the vehicles that run them. Greensea Systems' OPENSEA platform represents a deliberate break from this model — an open-architecture control framework that has attracted adoption from NOAA, MBARI, the US Navy, and a growing number of commercial operators. Understanding what OPENSEA actually does, and how it differs from incumbent proprietary systems, is increasingly relevant for pilots working outside the conventional North Sea and Gulf of Mexico work-class fleet.

What Open Architecture Means in Practice

OPENSEA is built on a publish-subscribe middleware framework based on MOOS-IvP from MIT that treats every sensor, actuator, and algorithm as a module communicating over a standardized internal network. In a proprietary system like MISO, adding a new sensor or changing an autopilot behavior requires working within Schilling's update cycle and software licensing constraints. In OPENSEA, a third-party developer or an operator's engineering team can write a new module, publish it to the OPENSEA internal bus, and have it interact with any other system component without access to the source code of existing modules. This matters practically when operators want to integrate novel sensors, custom inspection algorithms, or autonomous behavior that the original system designer did not anticipate.

Auto-Altitude, Heading, and Depth Hold

• OPENSEA implements altitude hold using an acoustic altimeter fused with DVL (Doppler Velocity Log) vertical velocity data — the fusion gives smoother altitude hold than altimeter-only implementations at low altitude
• Heading hold uses a fiber optic gyro (FOG) in the standard configuration, with optional integration of ship-referenced USBL heading for surface-tethered vehicles — this approach outperforms magnetic compass heading hold in magnetically complex environments such as jacket structures
• Depth hold is pressure-sensor based with a vertical velocity damping loop; where depth rating permits, the sensor is an absolute pressure transducer rather than gauge pressure for greater stability
• Unlike MISO's auto-functions which are tuned to Schilling's own thruster and vehicle geometry, OPENSEA's autopilot gains are configured per-vehicle using an onboard system identification procedure — the auto-functions can be tuned to any vehicle hull form
• Pilots transitioning from MISO to OPENSEA report that altitude hold on OPENSEA is noticeably more stable in the 1-3 meter altitude band used for pipeline inspection, due to the DVL fusion

Station Keeping and Dynamic Positioning

Station keeping — maintaining the ROV's position in three dimensions without continuous pilot input — is where OPENSEA's architecture shows its most significant operational advantage over first-generation proprietary systems. OPENSEA's station keeping module accepts position reference inputs from USBL, LBL, DVL dead-reckoning, SLAM-derived position estimates, or any combination thereof, weighted by a user-configurable Kalman filter. The pilot interface presents a single hold-position command regardless of which position reference sources are active. This means the vehicle can maintain station during periods when one reference degrades — USBL multipath, for example — by automatically increasing reliance on DVL dead-reckoning until the USBL signal recovers, transparently to the pilot. Schilling's MISO station keeping, by contrast, requires the pilot to manually manage the transition between reference sources when signal quality degrades.

OPENSEA Compared to Schilling MISO and Forum VMAX

• MISO strength: mature, extensively proven platform with a large global technician base; factory integration with Schilling UHD vehicles is seamless; torque and force control for Titan 4 manipulator is deeply integrated
• MISO limitation: closed architecture limits operator customization; system updates follow Schilling's release cycle; adding non-Schilling sensors requires interface boxes and custom code
• Forum VMAX strength: strong track record on Forum Triton XL and Quantum vehicles; good multi-ROV control capability; intuitive pilot interface
• Forum VMAX limitation: proprietary and closed like MISO; custom sensor integration requires Forum engineering involvement; limited autopilot configurability
• OPENSEA strength: genuinely open — operators can develop and deploy custom modules; best-in-class multi-sensor position fusion; strong autonomous capability for scientific and survey applications
• OPENSEA limitation: smaller global technician base than MISO; requires more engineering investment to commission on a new vehicle; not currently available as a factory option on Schilling or Forum vehicles
• Commercial uptake is accelerating — several North Sea IRM operators have begun OPENSEA evaluation programs on vehicle refits

Adoption by NOAA and MBARI

The early adoption of OPENSEA by NOAA's Office of Ocean Exploration (on ROV Deep Discoverer) and MBARI (Monterey Bay Aquarium Research Institute, on Doc Ricketts and other platforms) established its credibility in technically demanding scientific operations. These operators demand capabilities that commercial work-class systems were not designed to provide: integration with acoustic communication modems for supervisory control, custom science sensor packages, long-endurance autonomous survey modes, and real-time science data overlay on the pilot interface. MBARI's adoption in particular — an institution with sophisticated ROV engineering capacity — validated OPENSEA's architecture at an organizational level that carries weight with commercial operators evaluating a departure from proprietary systems.

What This Means for Working Pilots

For pilots currently operating on MISO or VMAX platforms, OPENSEA represents a different paradigm rather than a direct replacement in most commercial contexts. The auto-functions feel familiar — altitude hold is altitude hold — but the interface philosophy differs. OPENSEA's pilot interface presents more sensor data and more control over autopilot behavior than proprietary systems typically expose to the pilot. Pilots with a technical background or an interest in understanding the vehicle's behavior at a systems level tend to engage with this positively. The configurable interface is a direct answer to information density concerns: operators can strip the display to essentials or expose the full sensor fusion status depending on pilot preference and task type.

OPENSEA and the Autonomous ROV Trajectory