Refine Your Search

Date

Date

Topic

Topic

Vehicle dynamics AS-1B Aircraft Store Integration Committee Fuel systems Management and Organizations Emissions

Search Results

Viewing 1 to 20 of 34
12Next >Last >>
Sort by title
Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces
2004-06-17
HISTORICAL
AS47642
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.
Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces
2012-07-12
HISTORICAL
AS47642A
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.
Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces
2017-06-28
CURRENT
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.
Standard

Validation Methods for MIL-STD-1760B Aircraft Station Interfaces
2012-07-12
HISTORICAL
AS47641
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.
Standard

Validation Methods for MIL-STD-1760B Aircraft Station Interfaces
2017-06-28
CURRENT
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.
Standard

Technical Architecture for Aircraft, Launcher, and Weapon Interoperability (ALWI TA)
2012-08-27
CURRENT
AIR5720A
The technical architecture defined in this document outlines mandatory, emerging, and needed standards to provide interoperability at key interfaces in the aircraft/store system (including an associated NATO Network Enabled Capability environment), as required to support a future plug-and-play aircraft/store integration capability. These standards relate to services and protocols associated with the subject interfaces. Modeling standards to facilitate the Model Driven Architecture® (MDA®) approach to system definition and implementation are also included. Note that the status of referenced standards as reflected in this document is as of August 2007, and document users should check to see if there has been a subsequent change of status relative to applicable standards.
Standard

Technical Architecture for Aircraft, Launcher, and Weapon Interoperability (ALWI TA)
2008-01-16
HISTORICAL
AIR5720
The technical architecture defined in this document outlines mandatory, emerging, and needed standards to provide interoperability at key interfaces in the aircraft/store system (including an associated NATO Network Enabled Capability environment), as required to support a future plug-and-play aircraft/store integration capability. These standards relate to services and protocols associated with the subject interfaces. Modeling standards to facilitate the Model Driven Architecture® (MDA®) approach to system definition and implementation are also included. Note that the status of referenced standards as reflected in this document is as of August 2007, and document users should check to see if there has been a subsequent change of status relative to applicable standards.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores
2012-08-22
CURRENT
AIR4013C
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores
2005-09-29
HISTORICAL
AIR4013B
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores
1998-01-01
HISTORICAL
AIR4013A
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

MULTIPLEX DATA BUS NETWORKS FOR MIL-STD-1760A STORES
2011-08-10
HISTORICAL
AIR4013
This document will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Interface for Micro Munition (IMM) Handbook
2016-09-16
CURRENT
AIR6114
This document was prepared by the SAE AS-1B1 IMM Task Group to explain and document background information and design decisions made during the development of AS5726. This handbook is published separately to preserve information that is not required or provided in the AS5726 but may be important to system designers to ensure interoperability between the Micro Munition Host and Micro Munition. As a handbook, it cannot be invoked as a requirement in a contract. The structure and numbering of this document mirrors that of AS5726 for the convenience of readers. Headings such as “Requirements” in this handbook should not be interpreted as invoking requirements.
Standard

Interface Standard, Miniature Mission Store Interface
2008-01-08
HISTORICAL
AS5725
This standard defines implementation requirements for the electrical interface between: a aircraft carried miniature store carriage systems and miniature stores b aircraft parent carriage and miniature stores c surface based launch systems and miniature stores The interface provides a common interfacing capability for the initialization and employment of smart miniature munitions and other miniature stores from the host systems. Physical, electrical, and logical (functional) aspects of the interface are addressed.
Standard

Interface Standard, Common Interface Control Plan
2016-01-02
CURRENT
AS6030A
This Common Interface Control Plan (CICP) establishes the methodology for developing, controlling, and managing the technical interfaces between and within systems. An interface defines the interaction at a defined point between entities to achieve a combined system capability. A common interface defines the shared interaction between multiple systems on either side of the interface. The document is not intended to directly control any other aspects of program management, such as matters of contractual, financial, or those of an intellectual property rights nature. Members in the interface control process include: procurement authorities, design authorities, and other related agencies as defined in the specific System Interface Control Plan (SICP). For the purposes of this plan, only the terms Procuring Organization and Producing Organization will be used.
12Next >Last >>
X