Search Results

This SAE Aerospace Standard (AS) provides the general performance, design, installation, test, development, and quality assurance requirements for the flight control related functions of the Vehicle Management Systems (VMS) of military piloted aircraft. It also provides specification guidance for the flight control interfaces with other systems and subsystems of the aircraft.

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 design and develop systems in a way that supports interoperability.

This SAE Aerospace Recommended Practice (ARP) provides the technical terms and nomenclature, together with their definitions and abbreviations/acronyms that are used in aerospace fluid power, actuation and control systems. NOTE: ARP490 and ARP4493 are sources for definitions specifically for electrohydraulic servovalves.

This Technical Governance is part of the SAE UCS Architecture Library and is primarily concerned with the UCS Architecture Model (AS6518) starting at Revision A and its user extensions. Users of the Model may extend it in accordance with AS6513 to meet the needs of their UCS Products. UCS Products include software components, software configurations and systems that provide or consume UCS services. For further information, refer to AS6513 Revision A or later. Technical Governance is part of the UCS Architecture Framework. This framework governs the UCS views expressed as Packages and Diagrams in the UCS Architecture Model.

This User Guide describes the content of the Rational Software Architect (RSA) version of the UCS Architectural Model and how to use this model within the RSA modeling tool environment. The purpose of the RSA version of the UCS Architectural Interface ICD model is to provide a model for Rational Software Architect (RSA) users, derived from the Enterprise Architect (EA) ICD model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6516 RSA Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models

This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural Model and how to use this model within the EA modeling tool environment. The purpose of the EA version of the UCS Architectural Interface Control Document (ICD) model is to provide a working model for Enterprise Architect tool users and to serve as the source model for the Rational Software Architect (RSA) and Rhapsody models (AIR6516 and AIR6517). The AIR6515 EA Model has been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service, and Non-Functional Properties Models

Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.

This standard is applicable to reciprocating engines powering unmanned aerial vehicles (UAV) that have rated power values less than 22.4 kW and are not to be used for human transport. This standard only covers engines designed for 150 hours of operation or higher.

The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Department of Defense Unmanned Control Segment (UCS) Architecture. This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. This information is produced from a script run against the System Use Case Model contained in the UCS Architecture Model AS6518-MODEL.eap configuration item. The System Use Case Model includes, at its lowest level of elaboration, use cases Level 2/3 (L2/L3) that describe specific scenarios of message exchanges between Actors and internal system Participants via ServiceInterfaces. These message exchanges provide a way to create detailed traces that answer the question: “What UCS service interfaces must my components implement to satisfy functional requirements represented by a given Level 2/3 UCS use case?”

This platform specific Interface Control Document (ICD) provides an example mapping to the Object Management Group’s (OMG) Data Distribution Service (DDS) infrastructure middleware. The mapping is based on the Unmanned Systems (UxS) Control Segment (UCS) Architecture: Model, AS6518. A series of non-normative implementation choices have been made that are specific to this ICD. These implementation choices may not be appropriate for different system implementations. The machine readable ICD and result of this mapping and implementation choices are provided with AIR6521. Use and understanding of this document assumes a working knowledge of the UCS Architecture, the model structure and its contents.

This revision of AS6513 concerns conformance to the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Revision B, designated AS6512B (or later). The superseded AS6513A concerned conformance to the previous UCS Architecture, designated AS6512A. This document is the authoritative specification within the UCS Architecture for establishing conformance requirements for UCS products. The conformance of UCS products is determined by assessing the conformance of the UCS Product Description to the UCS Architecture. The UCS Product Description includes test artifacts.

This interface control document (ICD) specifies all software services in the Unmanned Systems (UxS) Control Segment Architecture, including interfaces, messages, and data model.

The UCS Architecture Model is the authoritative UML model of the UCS Architecture as defined in AS6512B

This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Library Revision B or, simply, the UCS Architecture. The architecture is expressed by a library of publications as referenced herein. The other SAE publications in the UCS Architecture Library Revision B are AS6513B and AS6518B. The library also includes the government-owned Autonomous Ground Vehicle Reference Architecture (AGVRA) Data Model Framework Version 3.1A.

This data dictionary provides definitions for quantities, measurement units, reference systems, measurands, measurements, and quantity modalities commonly used in the command and control of cyber-physical systems. A cyber-physical system is an engineered system that is built from, and depends upon, the seamless integration of computational algorithms and physical components. Cyber-physical systems are often interconnected via data links and networks. The term encompasses intelligent vehicles and devices that operate in any environment, including robotic and autonomous systems.

This Aerospace Information Report provides an overview of published data on different methods for designing electromechanical actuators with a very low probability of jam or disconnect.

This project will create an Aerospace Recommended Practice that provides comprehensive guidelines for the design and specifications for rotary and linear mechanical actuators for use in aircraft mechanically distributed actuation systems including but not limited to flap, slat , cargo door, and weapons bay door actuators.

This Aerospace Recommended Practice (ARP) provides general requirements for a generic, integrated rudder and brake pedal unit, incorporating a passive force-feel system that could be used for fixed-wing fly-by wire transport and business aircraft.This ARP addresses the following:- The functions to be implemented- The mechanical interconnection between captain and F/O station- The geometric and mechanical characteristics- The mechanical, electrical, and electronic interfaces- The safety and certification requirements

This document defines a set of standard application layer interfaces called JAUS Mobility Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Mobility Services represent the vehicle platform-independent capabilities commonly found across all domains and types of unmanned systems (referred to as UxVs). At present, over 15 services are defined in this document many of which were updated in this revision to support Unmanned Underwater Vehicles (UUVs).

The scope of this SAE Aerospace Information Report (AIR) is first to establish applicable definitions and terms prior to considering the application domain and use cases in HVDC applications. Then it will identify commanded switching technologies to be considered for aerospace applications and provide rationale for their selection.