(U)UAS Integration and Interoperability

Abstract

Common Control System (CCS) budget profile changes are due to program realignment to support CCS development and integration in support of MQ-25 Stingray, MQ-8 Fire Scout and follow on UxS platforms. This PU funds the Unmanned Systems (UxSs) CCS. The primary mission of CCS is to provide common control across the Navy's UxSs portfolio to add scalable and adaptable warfighting capability, implement robust cybersecurity attributes, leverage existing government owned products, eliminate redundant software development efforts, consolidate product support, encourage innovation, improve cost control and enable rapid integration of UxS capabilities across Aviation, Surface, Sub-Surface, and Ground domains. CCS is a ship/shore/airborne/expeditionary based common control system that provides Vehicle Management (VM) and Mission Management/Mission Planning (MM/MP) capabilities for Naval Group 1 through 5 Unmanned Air Vehicles (UAVs) as well as other domain UxSs. VM is the software that allows the operator to control the UxS. MM/MP is the software that allows the operator to create mission plans and control the UxS's sensors and payloads. CCS software is based on the Society of Automotive Engineers (SAE) Unmanned Control Segment (UCS) architecture which is a service oriented open architecture that is modular and scalable to meet evolving Service requirements and is also supportive of safety/airworthiness certification and cybersecurity certification and accreditation. This program defines, develops, and delivers CCS capability that enables the flexibility for Ground Control Systems (GCS) that could be ship, shore, airborne, or expeditionary based to operate multiple and dissimilar Naval UxSs. CCS includes a common framework, user interface, and common components that will also be integrated and tested with legacy platform components. CCS is being developed with an open and modular business model with robust cybersecurity implementation and will be provided as Government Furnished Equipment (GFE) to UxS contractors as required. The CCS acquisition approach provides increasing capability through incremental development for UxS platforms as follows: Increment I delivered initial unmanned vehicle management (VM) functionality for MQ-25 Stingray in FY 2018, which included flight maneuvering and stationing, situational awareness, and health & performance status monitoring, hosted on legacy platform hardware. CCS VM functionality was delivered to MQ-8 Fire Scout in 1Q FY 2019 with another delivery scheduled for 3Q FY 2019. Increment II builds upon CCS Increment I software delivery, adding discrete common MM/MP capabilities as well as maturing VM capabilities. These MM/MP capabilities include route planning, aerial refueling, sensor and payload control, and data processing and dissemination. CCS Increment II software will be hosted on legacy platform hardware. Increment II adds robust cybersecurity controls, key systems safety attributes and core program infrastructure, to include a system integration lab and software support activity (SSA). Additional efforts include developing and executing plans for integration of common CCS VM services already developed under this program into other UxS cross-domain platforms' control stations to reduce department-level Total Ownership Costs for unmanned Ground Control Systems. Increment III provides common hardware for hosting CCS. CCS Increment III software will be developed and delivered with additional capabilities to include cross-domain capabilities and control of multiple dissimilar UxS for further enterprise-level Total Ownership Cost savings. JUSTIFICATION FOR BUDGET ACTIVITY: This program is funded under OPERATIONAL SYSTEMS DEVELOPMENT because it includes development efforts to upgrade systems that have been fielded or have received approval for full rate production and anticipate funding in the current or subsequent fiscal year.

Document Details

• Document Type: R2 Budgetary Justification
• Publication Date: Oct 01, 2020
• Source ID: 0305205N_7_1319_PB_2020
• Change Summary Explanation: FY 2018 and FY 2019 program adjustments delayed and descoped Increment II software requirements and development which resulted in a re-phase of Increment II deliveries across the FYDP. FY 2020 increase in funding supports CCS Increment II and III efforts. Schedule Changes: Added Milestone B 1Q 2019 Changed CCS Increment I Software Development to extend to 3Q 2019 Changed CCS Delivery to MQ-8 from 2Q 2019 to 3Q 2019 to align with platform schedule Changed CCS Increment II Software Development start to 3Q 2019 and extended to 4Q 2024 Changed CCS V2.0 Release from 2Q 2020 to 2Q 2021 Changed CCS V2.1 Release from 1Q 2021 to 4Q 2022 Changed CCS V2.2 Release from 1Q 2022 to 4Q 2023 Changed CCS V2.3 Release from 1Q 2023 to 3Q 2024 Changed CCS DT&E/OT Support from 1Q 2020 to 4Q 2019 Changed CCS Increment III Risk Reduction start 2Q 2020 and extended to 2Q 2023.
• Service Agency Name: Navy

Entities

Organizations

• United States Navy

Tags

Communities of Interest

• Air Platforms
• Cyber
• Ground and Sea Platforms
• Weapons Technologies

DTIC Thesaurus Topics

• Acquisition
• Aircrafts
• Contracts
• Control Systems
• Cross Domain
• Data Processing
• Engineering
• Government Furnished Equipment
• Ground Control Stations
• Product Development
• Software Development
• Systems Engineering
• Test And Evaluation
• Unmanned Aerial Systems
• Unmanned Aerial Vehicles
• Unmanned Systems
• Unmanned Vehicles

Fields of Study

• Computer science

Readers

• Naval Mine Countermeasure Systems Development.

Technology Areas

• Autonomy
• Cyber