NAVAL POSTGRADUATE SCHOOL Monterey, California TECHNICAL REPORT “SEA ARCHER” Distributed Aviation Platform by Faculty Members Charles Calvano David Byers Robert Harney Fotis Papoulias John Ciezki Robert Ashton Student Members LT Joe Keller, USN LCDR Rabon Cooke, USN CDR(sel) James Ivey, USN LT Brad Stallings, USN LT Antonios Dalakos, Helenic Navy LT Scot Searles, USN LTjg Orhan Okan, Turkish Navy LTjg Mersin Gokce, Turkish Navy LT Ryan Kuchler, USN LT Pete Lashomb, USN Ivan Ng, Singapore December 2001 Approved for public release, distribution unlimited REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188) Washington DC 20503. 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED December 2001 Technical Report 4. TITLE AND SUBTITLE: 5. FUNDING NUMBERS “Sea Archer” Distributed Aviation Platform 6. AUTHOR(S) Charles Calvano, Robert Harney, David Byers, Fotis Papoulias, John Ciezki, LT Joe Keller, LCDR Rabon Cooke, CDR (sel) James Ivey, LT Brad Stallings, LT Scot Searles, LT Ryan Kuchler, Ivan Ng, LTjg Orhan Okan, LTjg Mersin Gokce, LT Antonios Dalakos, LT Pete Lashomb. 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING Naval Postgraduate School ORGANIZATION REPORT Monterey, CA 93943-5000 NUMBER 9. SPONSORING / MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING / MONITORING N/A AGENCY REPORT NUMBER 11. SUPPLEMENTARY NOTES The views expressed in this thesis are those of the author and do not reflect the official policy or position of the Department of Defense or the U.S. Government. 12a. DISTRIBUTION / AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE Approved for public release, distribution unlimited Currently, no system exists that provides a sea-based distributed aviation platform capability. The emergence of Unmanned Air Vehicles (UAVs) / Unmanned Combat Air Vehicles (UCAVs), the continued U.S. Navy focus on the littorals, the desire for force distribution, the need for operational cost reductions, and the advent of Network Centric Warfare (NCW) all combine to support the requirement to re-evaluate how littoral operations will be conducted in the future. Given this background, a bottom-up design of a ship supporting a primarily UAV / UCAV air wing in a low to medium threat environment, is of significant interest. SEA ARCHER meets this interest. This report outlines a design that meets the future needs for distributed aviation with a high-speed, highly automated platform. Large gains in reduced manning through automated systems for both operation and damage control help meet the demanding needs for the future of the Navy at reduced operational costs. The report will outline both the Mission Needs Statement (MNS) and Operational Requirements Document (ORD) for the ship that was developed. The analysis of alternatives that was conducted to determine relative size requirements for the ships is presented in the next section. The concept design that resulted as a result of the Total Ship Systems Engineering process is then presented. Finally, a detailed look at the analysis and trade studies that were conducted is presented in order to show the more detailed analysis that was conducted in designing the ship. 14. SUBJECT TERMS Ship Design, Total Ship Systems Engineering, SEA ARCHER, Distributed 15. NUMBER OF Aviation, Littoral Warfare ship PAGES 16. PRICE CODE 17. SECURITY 18. SECURITY 19. SECURITY 20. LIMITATION CLASSIFICATION OF CLASSIFICATION OF THIS CLASSIFICATION OF OF ABSTRACT REPORT PAGE ABSTRACT Unclassified Unclassified Unclassified UL NSN 7540-01-280-5500 Standard Form 298 (Rev. 2-89) Prescribed by ANSI Std. 239-18 THIS PAGE INTENTIONALLY LEFT BLANK ii This report outlines the results of a two quarter Total Ship Systems Engineering (TSSE) Capstone design project undertaken by the students at the Naval Postgraduate School. The project was under the direction of Professors C.N. Calvano and R.Harney. The design team consisted of: LT Joe Keller, USN; LCDR Rabon Cooke, USN; CDR (sel) James Ivey, USN; LT Brad Stallings, USN; LT Scot Searles, USN; LT Ryan Kuchler, USN; Ivan Ng, Singapore Defense Science and Technology Agency; LTjg Orhan Okan, Turkish Navy; LTjg Mersin Gokce, Turkish Navy; LT Antonios Dalakos, Helenic Navy; LT Pete Lashomb, USN. ABSTRACT Currently, no system exists that provides a sea-based distributed aviation platform capability. The emergence of Unmanned Air Vehicles (UAVs) / Unmanned Combat Air Vehicles (UCAVs), the continued U.S. Navy focus on the littorals, the desire for force distribution, the need for operational cost reductions, and the advent of Network Centric Warfare (NCW) all combine to support the requirement to re-evaluate how littoral operations will be conducted in the future. Given this background, a bottom-up design of a ship supporting a primarily UAV / UCAV air wing in a low to medium threat environment, is of significant interest. SEA ARCHER meets this interest. This report outlines a design that meets the future needs for distributed aviation with a high-speed, highly automated platform. Large gains in reduced manning through automated systems for both operation and damage control help meet the demanding needs for the future of the Navy at reduced operational costs. The report will outline both the Mission Needs Statement (MNS) and Operational Requirements Document (ORD) for the ship that was developed. The analysis of alternatives that was conducted to determine relative size requirements for the ships is presented in the next section. The concept design that resulted as a result of the Total Ship Systems Engineering process is then presented. Finally, a detailed look at the analysis and trade studies that were conducted is presented in order to show the more detailed analysis that was conducted in designing the ship. iii THIS PAGE INTENTIONALLY LEFT BLANK iv FACULTY COMMENTS By Professors C. N. Calvano, and R. C. Harney, NPS TSSE PROGRAM A purpose of the TSSE capstone design project is to give experience in the design process as applied to a large, complex system, using a Navy ship as the system of interest. An additional major goal is to require the students to develop and exercise the leadership and cooperative skills needed to perform a complex task as a team. It is also hoped that the design produced will be interesting, innovative and, possibly, spur discussion and thought in Navy and industry circles. The program is made up of students enrolled in three curricula: Mechanical Engineering, Electrical and Computer Engineering, and Combat Systems. The faculty strives to ensure that all design projects provide an opportunity for students from each of these curricula to apply what they have learned in their individual domains while participating in a wider-scope team design. The 2001 capstone design project was the 10th since the program’s inception, but the first to be run within a broader, campus-wide collaborative environment. The project grew out of a Naval War College initiative exploring a concept called CORSAIR, a small aviation-capable ship carrying STOVL JSFs for littoral operations. CORSAIR was envisioned as contributing to a USN capability to defeat an adversary’s access-denial capability and, in this role, would essentially be providing air cover for small littoral combatants, such as the SEA LANCE, which was the subject of the 2000 TSSE capstone project, a response to another NWDC initiative. CAMPUS-WIDE COLLABORATIVE PROJECT The lead in the operational aspects of this collaborative project went to students in the Systems Engineering and Integration curriculum. They were tasked to explore the concept operationally, and their analysis resulted in a FORCE-level approach that had the following salient features: v • The FORCE was intended for operation in low to moderate threat areas in the littorals (where it could relieve or substitute for a CVBG that was needed elsewhere where the threat was high). • Unmanned air vehicles (UCAVs and UAVs), were employed exclusively to permit exploration of their utility. The air vehicles provide a primarily reconnaissance, surveillance, and target acquisition (RSTA) mission capability, though it was seen as useful to give the UCAVs the ability to carry a limited amount of ordnance. • The aviation capability of the force would be widely distributed across a number of platforms (notionally quantified as eight). The loss or incapacitation of any platform would not result in the loss of a major part of the aviation capability. • Because strike capability was not a major part of the force’s purpose and because the aviation capability of the FORCE was the capability of interest, individual platforms would not conduct high-tempo air ops (if several aircraft needed to be launched or recovered in a short period of time, several of the eight platforms would share the task). • Survivability of the FORCE’s capability is the survivability characteristic of interest. The individual platforms would be looked upon as “combat consumable”. (This, of course, played a big part in the thinking that minimum manning was needed. And, frankly, the idea of considering individual platforms to be “combat consumable” arose when it was hoped the aviation ships would be less than 8000 MT; our design showed that size to be unachievable, given the requirements.) • The force would be capable of significantly higher speed than current forces, with exploration of a 60 knot maximum speed capability as a prime feature of interest. • The force would consist of 8 aviation platforms carrying a combination of UCAVs, UAVs and, in very small numbers, helos.