This SAE Aerospace Information Report (AIR) describes the Architecture Framework for Unmanned Systems (AFUS). AFUS comprises a Conceptual View@ a Capabilities View@ and an Interoperability View. The Conceptual View provides definitions and background for key terms and concepts used in the unmanned systems domain. The Capabilities View uses terms and concepts from the Conceptual View to describe capabilities of unmanned systems and of other entities in the unmanned systems domain. The Interoperability View provides guidance on how to put it all together in a way that supports interoperability. Purpose The purpose of this Aerospace Information Report is to communicate to the unmanned systems community a common set of principles@ terms@ concepts@ patterns@ structures@ and guidance for creating system architectures that include or interact with unmanned systems. Field of Application Fields of application of AFUS include unmanned systems of all classes@ command and control (C2) systems@ and related areas such as communications@ safety@ security@ sensors@ manipulators@ and simulation. How to Use This architecture framework has several uses: ? to provide background information on unmanned systems to a variety of readers; ? to provide a common vocabulary for developing standards@ specifications@ and designs for unmanned systems; ? to provide a common set of semantics for the vocabulary; ? to provide a base set of behavioral states of common unmanned systems for use by developers of standards@ specifications@ and designs of unmanned systems; and ? to provide guidelines for developing standards that promote interoperability. The standards developer can best use AFUS by using the Interoperability View to identify and establish the proper scope for her standard. For standards that deal with unmanned system data exchange and/or behavior@ locate the capabilities in the Capabilities View that best correspond to the standard content. If not found@ draft a section following the style and structure of the section and submit for consideration to AS-4A for inclusion in future revisions of AFUS. Finally@ review the pertinent sections of the Conceptual View and Definitions for consistent vocabulary and semantics. The systems procurer can best use AFUS by selecting from the Interoperability View one or more existing standards from each area to meet the systems' needs. The procurer can gain further understanding of the different areas by reviewing pertinent sections of the Capabilities and Conceptual Views. The systems builder can best use AFUS by locating required standards in the Interoperability View and reviewing the Capabilities and Conceptual Framework sections pertinent to each required standard. Acknowledgements Development of this report was supported in part by U.S. Army Aviation and Missile Research@ Development@ and Engineering Center contract W31P4Q-05-A-0031/0008.