Overview

UCS Logo

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.

SAE Aerospace Electronics and Avionics Systems Conference (2012)

The SAE Aerospace Electronics and Avionics Systems Conference will be held in Phoenix, AZ October 30 through November 1, 2012. Members of the UCS WG will present an overview of the UCS architecture and its current development status.

AUVSI Conference (2012)

auvsi

The AUVSI Conference North America will be held in Las Vegas, NV August 6-9, 2012. Members of the UCS WG will present the current status of the UCS architecture development effort.

Military Aerospace Electronics 2011-07

Members of the Unmanned Control Systems, Control Segment (UCS) working group-run by the Office of the Secretary of Defense (OSD) are developing an architecture for future UAV control stations that will be not only embrace open standards, but meet critical safety and security certification requirements, as well. "The architectural approach for a common ground control segment is an open, flexible, scalable, and partitioned platform that addresses both information assurance and safety," says Chip Downing, director of military and aerospace at Wind River Systems in Alameda, Calif. "Designers then would be able to take existing functions and services which reside on federated platforms and migrate them to an open, partitioned environment which suit their mission needs." Hie MILS, multiple independent levels of security, approach is being adopted for this architecture. "MILS enables a common secure foundation that supports different levels of security domains on one hardware platform, allowing the connection of diverse security domains, like the U.S. Army and coalition partners, on one shared device," Downing says

http://military-machine.blogspot.com/2011/07/military-aerospace-electronics-2011-07.html

Army RFI

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.

Navy RFI

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.

AUVSI Conference (2011)

auvsi

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:

  • An overview of the architecture by Mr. Rich Ernst
  • A panel discussion on the Services use of UCS, featuring Mr. Dyke Weatherington, Mr. Tim Owings, Mr. Michael Paul, and LTC David Kacmarynski
  • A panel discussion providing technical details of the UCS architecture, featuring Mr. Doug Gregory, Mr. Brian Schechter, Dr. Parag Batavia, and Mr. Jim Albers

Slides presented during the technical panel discussion are attached.

UCS Overview, UCS Technical Overview, UCS IWP Overview, UCS MDA Process

UCS Videos

The following videos provide additional information on the UCS architecture and sample UCS services.


Government Moving to Open Architecture

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.

What's New!

There are no recent news articles.

News Archive