While there has been substantial discussion on the subject of both automation and optionally manned ships, they have largely been treated as separate topics. While this makes sense from a historical perspective, the underlying technologies are largely the same.

The software under development for the operation of unmanned surface vehicles (USVs) is being integrated with the Aegis Common Source Library. It stands to reason that this software will be available to all vessels using the Aegis Combat System or COMBATSS 21. This creates two broad categories of opportunity: it can be used as enhanced automation to assist the crew and it can allow large ships to be used as optionally manned vessels.

How the fleet uses this software will naturally require extensive discussion across all levels, as well as wargaming and experimentation to determine what works and what does not. This article simply aims to provide ideas for further discussion.

Assisting the Crew

Integrating USV software into the fleet will allow the crew to hand over routine tasks like open-ocean navigation to the computer. This offloading will allow them to focus on other tasks such as training and rest. Considering insufficient training and fatigue were major factors in recent collisions, the time freed from routine or monotonous activities would create opportunities to improve crew readiness and safety.

Optional Manning

While the importance of a crew to fight a ship and perform damage control cannot be overstated, there are cases where a commander may make the deliberate choice to sacrifice a ship, so removing the crew makes sense. Such situations include using obsolete ships pulled out of mothballs, placing modern ships in high-risk situations, or even the hard decision by a commander to sacrifice a ship to achieve larger goals. In these cases, it makes sense for the ship to be able to operate unmanned.

To provide a tactical example, obsolete ships acting as USVs would be ideally suited to launch a diversionary attack against a critical enemy position. The enemy would almost certainly sink these ships, but since there would be no one on board the obsolete ships, this exchange of expendable hardware for a major strategic opportunity could lead to a decisive victory. As some of our Aegis ships approach the end of their service lives, this may become a viable alternative to mothball and eventual scrapping. If budget management is a concern, such modifications can be relegated to a post-reactivation refit as needed.

On the other side, the Navy could find itself in a position similar to the famous Battle off Samar in which it may be prudent to have ships operating unmanned to reduce casualties in the face of an overwhelming attack. Additionally, in the age of networked warfare, a forward ship could greatly enhance the survivability of the larger force with its sensor data at the cost of greatly increased risk to itself. In either case the ships are likely to be more modern, but it may be prudent to remove the crews to reduce casualties while maintaining combat effectiveness.

There is great potential in optional manning software on large platforms in the future. Extensive discussion and experimentation will be required to bring this potential into reality. The USS Freedom (LCS-1) and USS Fort Worth (LCS-3) are already equipped with COMBATSS 21 and dedicated to testing, making them ideal candidates for near-to-immediate application and providing a fast track to the fleet.