(U)UAS Integration and Interoperability
Abstract
Common Control System (CCS) budget profile changes are due to program realignment and acceleration 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 will be 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. CCS software is based on the OSD 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 will define, develop, and deliver 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 delivers initial unmanned vehicle management (VM) functionality for MQ-25 Stingray in FY18, which includes flight maneuvering and stationing, situational awareness, and health & performance status monitoring, hosted on legacy platform hardware. CCS VM functionality will also be delivered to MQ-8 Fire Scout in FY19 with requirements development initiated in FY17. Additional efforts include developing 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 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. Additionally, 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). Increment III develops 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, 2019
- Source ID
- 0305205N_7_1319_PB_2019
- Change Summary Explanation
- Note 1: FY17 planned Increment II software requirements and development effort deferred one year Note 2: FY17 planned CCS Increment I integration into MQ-8 Fire Scout contract delayed six months Note 3: Schedule updated to show a more detailed breakout of activities of each Increment, including incremental delivery of additional capabilities in periodic software releases. Note 4: Schedule updated to show Increment I completion in FY19. Note 5: Moving Target Indicator (MTI) Speed-to-Fleet effort removed due to direction to allocate all Speed-to-Fleet funds to Geo-intelligence Unified Naval Streaming Systems (GUNNS) in FY17. Note 6: Additional funding ($24.2M) provided in FY19 for CCS program wholeness and MQ-25 acceleration.
- Service Agency Name
- Navy
Entities
Organizations
- United States Navy
Related Documents
- Child Project: Common Control System
- Child Accomplishment: Increment I
- Child Accomplishment: Increment II
- Child Cost Item: 25014b33883165cfb76ce95edf032690
- Child Cost Item: d6669d568e8e222c8ecf1fdd04441984
- Child Cost Item: ee657bd24d4f19f3e8d2a0c13f45f736
- Child Cost Item: 2285b07637c261188645295c31e042cd
- Child Cost Item: 89d4947281b964d2e9b563a482c4ef3a
- Child Cost Item: 9db88ef5a33f2ab5180fb63ddc4039a3
- Child Cost Item: 0d2580273d74ac83571dcbfe2dafc411
- Child Cost Item: baa5b986e9da1aa90df3094ef250ce37
- Child Cost Item: e9a922f08fdc5452d75ef6550c0e2f62
- Child Cost Item: 4f371f89d6d243f654cdad8520700a56
- Child Cost Item: db18096fea475426743e31e2d13607e2
- Child Cost Item: f3f4fe15fccf92d1fd8cf8a3b0c418fa
- Child Cost Item: 82977e1e36b63d38c307b97d5cd3746f
- Child Cost Item: 16cc39f9586fdf56e7208c7f903c3de9
- Child Cost Item: 4a954b1f05765c1760f9ee8b3e848b74
- Child Cost Item: dfdab075160951f453d9a1421f00e196
- Child Cost Item: 7c51dd3f9e8b520d7dcd7782bdd6c11b
- Child Cost Item: 195e4aff353fa97eb2938e055d5beb14
- Child Cost Item: 76c5bf9c78249f820022d2a51cdfa0dc