Unmanned Carrier Aviation Mission Control System

Abstract

The Unmanned Carrier Aviation (UCA) Mission Control System (UMCS) program builds, integrates, and installs control systems required to operate the MQ-25A. The UMCS program includes what was previously identified as the Control System & Connectivity (CS&C) and Carrier Vessel, Nuclear (CVN) Integration (CVNI) Segments previously captured under the MQ-25 Development PU 3278. The Unmanned Carrier Aviation (UCA) Mission Control System (UMCS) program, PU 3279, is the system-of-systems required for MQ-25 vehicle and payload control both shipboard and shore based. The UMCS consists of all ground and ship based hardware, software, and networks associated with the planning and execution of flight operations and tactical missions; including the Ground Control Stations (GCSs), displays, computers, and servers as well as line of sight (LOS) communications and beyond line of sight (BLOS) satellite communications (SATCOM). Additionally, UMCS contains the human interface for Air Vehicle Operators (AVOs) with the MQ-25A Air Vehicle (AV) and external C4I systems. The new GCS hardware will streamline software development, readily support multiple classification levels, and position the MQ-25A for interoperability with other DoD systems. UMCS develops GCS software and integrates that software with MQ-25A unique software. UMCS modifies CVN spaces in order to install the GCS, auxiliary communications systems, and VidMS. The UMCS integrates with existing NAVWAR C4I systems to provide network paths for AV and mission payload data using a variety of wideband and narrowband communication paths. UMCS builds the following hardware: MQ-25A GCS, Video Management System (VidMS), ARC-210 Radio Communication System (RCS), and Ashore Routing Communication System (ARCS). The new GCS has three variants, with the nomenclature of MD-5: one for CVNs (MD-5C), one for shore sites (MD-5D), and an embarkable system (MD-5E). The GCS consists of the following components: air vehicle operator (AVO) workstations, server racks, network interface racks, integrated communication system (ICS), Data Transfer System (DTS), and software. The ship variant (MD-5C) will leverage shore system components but will have slight manufacturing differences to account for the CVN environment. The VidMS provides MQ-25A AVOs with situational awareness video and displays of the CVN environment. The ARC-210 and Mobile User Objective System (MUOS) radio systems provide narrowband command and control (C2) and communications between the GCS and the MQ-25A Air Vehicle (AV). An ICS 1/2 rack integrates the GCS with existing carrier communication systems. The ARCS provides an interface between the shore sites and the Command, Control, Communication, Computers, and Intelligence (C4I) networks to enable wide-band LOS and BLOS communications with the MQ-25A. The UMCS program is leveraging NAVWAR baseline systems on board the CVNs and at the MQ-25A shore sites. UMCS leads development, modification, engineering, and integration activities, facilitating seamless voice, data, and C2 exchanges with the MQ-25A AV, local networks, voice networks, C2 networks, tactical networks, intelligence systems, and launch and recovery systems. To accomplish this, the UMCS Program works closely with existing NAVWAR Programs of Record (PoRs). UMCS modifies CVN spaces to install GCS and communication hardware mentioned above, as well as the embarkable GCS (MD-5E), to support MQ-25A test events aboard select NIMITZ class carriers. The Naval Sea Systems Command (NAVSEA) Navy Modernization Process (NMP) provides guidance for CVN installation activities. This process identifiesschedules and deadlines for documentation, drawings, and hardware availability to support CVN modifications. The CVN availability schedule (revised at least twice per year) identifies pre-planned maintenance periods for NIMITZ and FORD-Class CVNs. Changes to the maintenance periods could drive changes to the UMCS installation schedule. The process consists of multiple phases. Phase 1 is characterized by the development of technical data packages (TDPs), general installation guidance documents, and the Ship Change Documents (SCDs); this phase begins approximately three years, or more, before the start of the CVN maintenance period. Phase 2 is characterized by the performance of hull specific Ship Checks, development of hull specific Ship Installation Drawings (SIDs), and the purchase of Ground Control Station (GCS), VidMS, and LOS/BLOS subsystems; this phase begins two years before the start of the CVN maintenance period. Phase 3 is characterized by the approval of the SIDs, development of installation schedules, completion of cybersecurity and logistics documentation, and the integration and testing of the GCS and associated subsystems. This phase begins approximately one year prior to the start of the CVN maintenance period. Phase 4 is characterized by the modification of the CVN infrastructure, installation of the GCS and associated subsystems, and completion of the System Operational Verification Testing (SOVT); tasking is scheduled based on the number of SCDs being installed and the length of the planned CVN Maintenance Availability period. When availability periods are only six months long, activities will begin at the start of the CVN maintenance period. Due to the size and complexity of the UMCS modifications, a minimum of two 6-month maintenance periods is required for a full installation.

Document Details

• Document Type: Project
• Publication Date: Oct 01, 2022
• Source ID: 3279_0605414N_5_1319_PB_2022

Tags

Readers

• Naval Mine Countermeasure Systems Development.
• Tactical Satellite Communications Systems Engineering.

Technology Areas

• Autonomy
• Cyber
• Fully Networked C3
• Fully Networked C3 - Command and Control
• Space