Display:

Results

Viewing 1 to 30 of 1987
2017-08-29
Book
This is the electronic format of the Journal.
2017-01-19
WIP Standard
ARP6283/2
Provide user information on best practice methods and processes for the in-service inspection, evaluation and cleaning of expanded beam fiber optic interconnect components, test equipment, and test leads based on the information provided in AIR6031. This document provides the user with a decision making tool to be able to determine if the fiber optic components are acceptable for operation with multi-fiber fiber optic termini.
CURRENT
2017-01-18
Standard
AS5506C
This standard defines a language for describing both the software architecture and the execution platform architectures of performance-critical, embedded, real-time systems; the language is known as the SAE AADL. An AADL model describes a system as a hierarchy of components with their interfaces and their interconnections. Properties are associated to these constructions. AADL components fall into two major categories: those that represent the physical hardware and those representing the application software. The former is typified by processors, buses, memory, and devices, the latter by application software functions, data, threads, and processes. The model describes how these components interact and are integrated to form complete systems. It describes both functional interfaces and aspects critical for performance of individual components and assemblies of components. The changes to the runtime architecture are modeled as operational modes and mode transitions.
2017-01-17
WIP Standard
AIR4543/1A
This SAE Aerospace Information Report (AIR) contains Lessons Learned from aerospace actuation, control and fluid power systems technologies. The lessons were prepared by engineers from the aerospace industry and government services as part of the work of SAE Committee A-6, Aerospace Actuation, Control and Fluid Power Systems. Each lesson was presented to the appropriate A-6 technical panel. The technical topics are organized into five sections covering systems, actuation, hydraulic components, electrical components and miscellaneous, each further divided into subsections. The information topics are presented in a concise format of Problem, Issue, Solution and Lesson Learned, often with accompanying descriptive diagrams and illustrations for clarity and understanding.
CURRENT
2017-01-12
Standard
AS5609A
This SAE Aerospace Standard (AS) defines the editorial format and policies necessary for the publication of Interface Control documents. The Common Interface Control Document Format Standard defines a common format for aircraft/store interface documents to foster increased interoperability. It is designed with the versatility to serve differing “ICD” philosophies and organizations. This aerospace standard defines the common technical data sections for the Common Interface Control Document Format down to the third header level for the majority of sub-sections. The Common Interface Control Document Format Aerospace Standard provides a structured document format in appendixes supported by example paragraphs, drawings, etc.
2016-12-21
WIP Standard
ARP6915
This Aerospace Recommended Practice (ARP) offers best practice regarding the implementation of IVHM systems taking into account Human Factors, both the vehicle crew and the maintenance staff. The document will include considerations regarding both military and civil fixed wing aircraft. Safety implications will also be addressed.
CURRENT
2016-12-20
Standard
AIR6520
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.
CURRENT
2016-12-20
Standard
AS6522
The UCS technical governance comprises a set of policies, processes, and standard definitions to establish consistency and quality in the development of architecture artifacts and documents. It provides guidance for the use of adopted industry standards and modeling conventions in the use of Unified Modeling Language (UML) and Service Oriented Architecture Modeling Language (SoaML), including where the UCS Architecture deviates from normal UML conventions. This document identifies the defining policies, guidelines, and standards of technical governance in the following subjects: - Industry standards adopted by the AS-4UCS Technical Committee: These are the industry standards and specifications adopted by AS-4UCS in the generation and documentation of the architecture. - UCS Architecture Development: UCS specific policies on the development of the UCS Architecture. The AS-4UCS Technical Committee governance policies are intentionally minimal.
CURRENT
2016-12-20
Standard
AS6513
This document is the authoritative specification within the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture for establishing conformance requirements for UCS products. The UCS products addressed by this specification are UCS software components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more UCS services. 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.
CURRENT
2016-12-20
Standard
AS6512
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture. This AD serves as the official designation of the UCS Architecture - SAE AS6512. The UCS Architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library are: AS6513, AIR6514, AIR6515, AIR6516, AIR6517, AS6518, AIR6519, AIR6520, AIR6521, and AS6522.
CURRENT
2016-12-20
Standard
AIR6519
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?”
CURRENT
2016-12-20
Standard
AIR6514
This interface control document (ICD) specifies all software services in the Unmanned Systems (UxS) Control Segment Architecture, including interfaces, messages, and data model.
CURRENT
2016-12-20
Standard
AIR6521
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.
CURRENT
2016-12-20
Standard
AIR6517
This User Guide describes the content of the Rhapsody version of the UCS Architectural Model and how to use this model within the Rhapsody modeling tool environment. The purpose of the Rhapsody version of the UCS Architectural Interface Control Document (ICD) model is to provide a model for Rhapsody users, derived from the Enterprise Architect (EA) model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6517 Rhapsody 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
CURRENT
2016-12-20
Standard
AIR6515
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
CURRENT
2016-12-20
Standard
AIR6516
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
CURRENT
2016-12-20
Standard
AS6518
This brief User Guide recaps the content of the AS6518 UCS Architectural Model described in detail in AS6512 UCS Architecture: Architecture Description. The purpose of the UCS Architecture Model is to provide the authoritative source for other models and products within the UCS Architecture as shown in the AS6512 UCS Architecture: Architecture Description.
2016-11-23
WIP Standard
AS407E
To specify minimum requirements for Fuel Flowmeters for use primarily in reciprocating engine powered civil transport aircraft, the operation of which may subject the instruments to the environmental conditions specified in Section 3.3. This Aeronautical Standard covers two basic types of instruments, or combinations thereof, intended for use in indicating fuel consumption of aircraft engines as follows: TYPE I - Measure rate of flow of fuel used. TYPE II - Totalize amount of fuel consumed or remaining.
CURRENT
2016-11-18
Standard
AIR6234
This Handbook is intended to provide useful information on the application of AS5716A. It is for use by System Program Offices, aircraft prime contractors, avionics and store system designers, system integrators and equipment manufacturers and users. This Handbook was prepared to provide users of the standard of the rationale and principles considered during the development of the standard. It is anticipated that the handbook will serve to assist developers in introducing new technology to achieve compliance with the standard and the underlying principles of the standard. It is intended that the Handbook be used alongside the standard, as it does not contain significant extracts of the standard.
CURRENT
2016-11-18
Standard
ARP6379
This document describes a process for use by ADHP integrators of EEE parts and sub-assemblies (items) that have been targeted for other applications. This document does not describe specific tests to be conducted, sample sizes to be used, nor results to be obtained; instead, it describes a process to define and accomplish application-specific qualification; that provides confidence to both the ADHP integrators, and the integrators’ customers, that the item will performs its function(s) reliably in the ADHP application.
2016-10-25
Technical Paper
2016-36-0377
Alain Giacobini Souza, Luiz Carlos Gadelha Souza
Abstract In designing of the Attitude Control System (ACS) is important take into account the influence of the structure’s flexibility, since they can interact with the satellite rigid motion, mainly, during translational and/or rotational maneuver, damaging the ACS pointing accuracy. In the linearization and reduction of the rigid-flexible satellite mathematic model, usually one loses some important information associated with the satellite true dynamical behavior. One way to recovery this information is include to the ACS design parametric and not parametric uncertainties of the system. The H infinity control method is able to take into account the parametric uncertainty in the control law design, so the controller becomes more robust. This paper presents the design of a robust controller using the H infinity control technique to control the attitude of a rigid-flexible satellite.
CURRENT
2016-10-21
Standard
AIR4271A
This Aerospace Information Report (AIR) has been prepared by the Systems Applications and Requirements Subcommittee of SAE Committee AS-2. It is intended to provide guidance primarily, but not exclusively, for specifiers and designers of data communication systems for real time military avionics applications within a platform. The subject of high speed data transmission is addressed from two standpoints: (1) the influence of developments in technology on avionics architectures as a whole and (2) the way in which specific problems, such as video, voice, closed loop control, and security may be handled. While the material has been prepared against a background of experience within SAE AS-2 relating to the development of a family of high speed interconnect standards, reference to specific standards and interconnect systems is minimized.
CURRENT
2016-10-21
Standard
AIR4295A
This document contains guidance for using SAE publications, AS4112 through AS4117 (MIL-STD-1553 related Test Plans). Included herein are the referenced test plan paragraphs numbers and titles, the purpose of the test, the associated MIL-STD-1553 paragraph, commentary concerning test methods and rationale, and instrumentation requirements.
CURRENT
2016-10-21
Standard
AIR4886A
The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.
CURRENT
2016-10-21
Standard
AIR5683A
MIL-STD-1553 establishes requirements for digital command/response time division multiplexing (TDM) techniques on military vehicles, especially aircraft. The existing MIL-STD-1553 network operates at a bit rate of 1 Mbps and is limited by the protocol to a maximum data payload capacity of approximately 700 kilobits per second. The limited capacity of MIL-STD-1553 buses coupled with emerging data rich applications for avionics platforms plus the expense involved with changing or adding wires to thousands of aircraft in the fleet has driven the need for expanding the data carrying capacity of the existing MIL-STD-1553 infrastructure.
CURRENT
2016-10-21
Standard
AS15532A
The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the documentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines established in this standard in order to ease future standardization of these words and messages. The standard word formats presented represent a composite result of studies conducted by the U.S.
CURRENT
2016-10-21
Standard
AS4074/1B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: The physical media interface: This slash sheet specifies the characteristics of the optical interface to the physical bus media. The minimum and maximum timing requirements for operation of this implementation of the LTPB. The data coding used to encode and decode the data for transmission. The default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
CURRENT
2016-10-21
Standard
AS4074/2B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: The physical media interface: This slash sheet specifies the characteristics of the optical interface to the physical bus media. The minimum and maximum timing requirements for operation of this implementation of the LTPB. The data coding used to encode and decode the data for transmission. The default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
Viewing 1 to 30 of 1987

Filter