The UAS Control Segment (UCS) Architecture is a framework representing the software-intensive capabilities of current and emerging UAS programs in the U.S. Army, Navy, and Air Force inventories. The goal is to develop an architecture, based upon Service Oriented Architecture (SOA) principles, that will be adopted by each of the Services as a common basis for acquiring, integrating, and extending the capabilities of the control systems for UAS. You can find more information in the Objectives section.
Check out the Technical Information section for an overview of the UCS Architecture structure and technologies used.
The UCS Architecture is being developed by the UCS Working Group.
The Army has released a request for information (RFI) for Unmanned Control Station Software, to be compliant with the UAS Control Segment (UCS) architecture. Details of the RFI may be found at this link.
The Navy has released a request for information (RFI) for the Common Control System (CCS), to be compliant with the UAS Control Segment (UCS) architecture. Details of the RFI may be found at this link.
Details on the UCS architecture may be found on the UCS Working Group Sharepoint site. For access to that site, submit a request via the Contacts page on this site.
The UAS Control Segment (UCS) Architecture was recently featured at AUVSI's Unmanned Systems North America 2011 conference in Washington D.C., August 15-19, 2011. A track in the conference program was devoted to providing information on the UCS Architecture, and included:
Slides presented during the technical panel discussion are attached.
UCS Overview, UCS Technical Overview, UCS IWP Overview, UCS MDA ProcessThe following videos provide additional information on the UCS architecture and sample UCS services.
Embracing open architecture concepts from an acquisition standpoint requires modifications to legacy processes. In reference to this, Dr. Carter's Efficiency Memo dated November 3, 2010 states:
"Require open systems architectures and set rules for acquisition of technical data rights. At Milestone B, I will require that a business case analysis be conducted in concert with the engineering trade analysis that would outline an approach for using open systems architectures and acquiring technical data rights to ensure sustained consideration of competition..."
The linked document "Better Buying Power Understanding and Leveraging Data Rights in DoD Acquisitions" provides additional information and references regarding technical data management and rights.
| There are no recent news articles. |