Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 85
CURRENT
2017-08-15
Standard
AS4115A
This test plan consists of two major sections for testing of MIL-STD-1553B data bus systems: Bus Network and System Integration Tests.
CURRENT
2017-08-14
Standard
AS4116A
This Aerospace Standard (AS) defines the test requirements for determining that bus monitors meet the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
CURRENT
2017-08-14
Standard
AS4114A
This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.
CURRENT
2017-08-10
Standard
AS4112A
This test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.
CURRENT
2017-08-10
Standard
AS4111A
This SAE Aerospace Standard (AS) contains a sample test plan for AS15531 or MIL-STD-1553B Remote Terminals (RT) that may serve several different purposes. This document is intended to be contractually binding when specifically called out in a specification, Statement of Work (SOW), or when required by a Data Item Description (DID). Any and all contractor changes, alterations, or testing deviations to this section shall be separately listed for easy review.
CURRENT
2017-08-10
Standard
AS4117A
This test plan defines the requirements of data bus components which comply with the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
2017-08-09
WIP Standard
AS42702
This document establishes techniques for verifying that a Mission Store Interface (MSI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.
2017-08-01
WIP Standard
ARP7208
This ARP establishes guidelines for the use of IEEE-802.3 as a data bus network in military and aerospace vehicles. It encompasses the data cable and its connections for a system utilizing 10Base-T, 100Base-T, 1000BASE-T and 10GBASE-T over copper medium dependent interfaces (MDI). This document contains extensions/restrictions to “off-the-shelf” IEEE-802.3 standards, and assumes that the reader already has a working knowledge of IEEE-802.3.
CURRENT
2017-07-12
Standard
AIR5451A
The landing gear system is a major and safety critical airframe system that needs to be integrated efficiently to meet the overall aircraft program goals of minimizing the penalties of weight, cost, dispatch reliability and maintenance. As the landing gear system business develops and large-scale teaming arrangements and acquisitions become increasingly common, it may be desirable in some instances to procure an Integrated Landing Gear System. This document provides guidelines and useful references for developing an integrated landing gear system for an aircraft. The document structure is divided into four sections: • Landing Gear System Configuration Requirements (Section 3) • Landing Gear System Functional Requirements (Section 4) • Landing Gear System Integrity Requirements (Section 5) • Landing Gear System Program Requirements (Section 6) The landing gear system encompasses all landing gear structural and subsystem elements.
CURRENT
2017-06-28
Standard
AS47641A
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
CURRENT
2017-06-28
Standard
AS47642B
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
CURRENT
2017-06-27
Standard
AS4764A
This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.
CURRENT
2017-06-27
Standard
AS4270A
This document establishes techniques for validating that a mission store complies with the interface requirements delineated in MIL-STD-1760.
CURRENT
2017-06-27
Standard
AIR6027A
The information presented in this AIR is intended to provide designers of armed unmanned systems with guidelines that may be applied to ensure safe integration and operation of weapons on unmanned platforms. The guidelines have been developed from experiences gained in the design and operation of weapons on manned aircraft that have been accepted by relevant safety authorities in the USA and Europe and proven effective over many years. Whilst the guidelines have been developed from experience with aircraft operations, the concepts are considered equally applicable to non-aircraft systems, such as those used on the surface or undersea environments.
2017-05-23
WIP Standard
AS5680B
This interface standard applies to fuzes used in airborne weapons that use a 3-in fuze well. It defines: - Physical envelope of the fuze well at the interface with the fuze. - Load bearing surfaces of the fuze well. - Physical envelope of the fuze and its connector. - Mechanical features (e.g., clocking feature). - Connector type, size, location and orientation. - Retaining ring and its mechanical features (e.g., thread, tool interface). - Physical envelope of the retaining ring at the interface with the fuze. - Physical space available for installation tools. - Torque that the installation tool shall be capable of providing. This standard does not address: - Materials used or their properties. - Protective finish. - Physical environment of the weapon. - Explosive interface or features (e.g., insensitive munitions (IM) mitigation). - Charging tube. - Torque on the retaining ring or loads on the load bearing surfaces.
CURRENT
2017-05-09
Standard
EIASTD4899C
This document applies to the development of Plans for integrating and managing electronic components in equipment for the military and commercial aerospace markets; as well as other ADHP markets that wish to use this document. Examples of electronic components, as described in this document, include resistors, capacitors, diodes, integrated circuits, hybrids, application specific integrated circuits, wound components, and relays. It is critical for the Plan owner to review and understand the design, materials, configuration control, and qualification methods of all “as-received” electronic components, and their capabilities with respect to the application; identify risks, and where necessary, take additional action to mitigate the risks. The technical requirements are in Clause 3 of this standard, and the administrative requirements are in Clause 4.
CURRENT
2017-03-21
Standard
AS15531A
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration, that is functionally equivalent to MIL-STD-1553B with Notice 2. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
CURRENT
2017-03-09
Standard
J1939/81_201703
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. Network management is concerned with the management of source addresses and the association of those addresses with an actual function and with the detection and reporting of network related errors. Due to the nature of management of source addresses, network management also specifies initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
CURRENT
2017-02-21
Standard
AS4074B
This standard specifies the characteristics of the SAE Linear Token Passing Bus (LTPB) Interface Unit. The LTPB provides a high reliability, high bandwidth, low latency serial interconnection network suitable for utilization in real time military and commercial applications. Multiple redundant data paths can be implemented to enhance reliability and survivability in those applications which require these attributes. The token passing and data exchange protocols are optimized to provide low latency and fast failure detection and correction. Physical configurations with bus lengths up to 1000 m can be accommodated. This specification defines the following: General Description (3.1): An overview of the LTPB protocol. Physical Media Interface (3.2): This portion of the standard defines the physical interface to both optical and electrical bus media.
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.
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.
CURRENT
2016-10-21
Standard
AS4074/3B
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 electrical 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
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
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-06-16
Standard
EQB1
Scope is unavailable.
CURRENT
2016-06-16
Standard
EQB3
The Electronic Industries Association (EIA) G-47 Effectiveness QuantificationCommittee has a basic task to quantify system effectiveness. Since the support parameters underly any prime parameter quantification, the topic of support system analysis is a fundamental one to this basic committee task. The charts contained in this bulletin were developed and used for presentations to aircraft support engineering groups, to comunicate the logic and scope of system analysis applied to support system optimization.
CURRENT
2016-06-16
Standard
EQB4
This report on quantification of Essentiality (W) and Utilization (U) terms extends the scope of the basic expression for system effectiveness (Es = ADC) to include the additional "W" and "U" paramenters needed for the quantification of multi-functioned and multi-missioned systems. Methods and procedures for applying these terms to system effectiveness quantification are discussed and simple examples to demonstrate the principles of usage are included. The need to look at the system being quantified in terms of its level in the mission/function hierarchical tree is explained. The relationships between system elements (hardware, software, and personnel) and performance functions are discussed and illustrated with examples. Two methods for applying the "W"'and "U" weight factors, LOGIC AND (weak link model) and LOGIC OR (degraded operational modes model) are described and examples are shown for these cases.
Viewing 1 to 30 of 85

Filter

  • Standard
    85