Search Results

This SAE Aerospace Standard (AS) establishes guidelines for the use of IEEE-1394-2008 Beta (formerly IEEE-1394b) as a data bus network in military and aerospace vehicles. It encompasses the data bus cable and its interface electronics for a system utilizing S400 over copper medium over extended lengths. This document contains extensions/restrictions to “off-the-shelf” IEEE-1394 standards, and assumes that the reader already has a working knowledge of IEEE-1394. This document does not identify specific environmental requirements (electromagnetic compatibility, temperature, vibration, etc.); such requirements will be vehicle-specific and even LRU-specific. However, the hardware requirements and examples contained herein do address many of the environmental conditions that military and aerospace vehicles may experience. One should refer to the appropriate sections of MIL-STD-461E for their particular LRU, and utilize handbooks such as MIL-HDBK-454A and MIL-HDBK-5400 for guidance.

This recommended practice has been developed for use in any EEE system used in the AADHP industries. RPA is especially important to AADHP systems, which are often safety critical applications that must operate for long times in rugged environments. These EEE systems often use EEE components that were originally designed and produced for more benign consumer applications. Although the focus of this recommended practice is on AADHP applications, the process described herein is not limited to AADHP and may be used for EEE systems and components in any industry.

This SAE Aerospace Information Report (AIR) is prepared for stakeholders seeking information about the evolution, integration, and approval of SHM technologies for military aircraft systems. The report provides this information in the form of (a) two military organizations’ perspectives on requirements, and (b) general SHM challenges and industry perspectives. The report only provides information to generate awarness of prespectives for military aircraft and, hence, assists those who are involved in developing SHM systems understanding the broad range of regulations, requirements, and standards published by military organizations that are available in the public domain from the military organizations.

This Aerospace Standard (AS) is to be used as a supplement to SAE AS7109. In addition to the requirements contained in AS7109, the requirements contained herein shall apply to suppliers seeking NADCAP Coatings accreditation who are engaged in thermal spray.

This Aerospace Standard (AS) is to be used as a supplement to SAE AS7109. In addition to the requirements contained in AS7109, the requirements contained herein shall apply to suppliers seeking NADCAP Coatings accreditation who are engaged in stripping of coated material.

This Aerospace Standard (AS) establishes the requirements for suppliers of Nonconventional Machining Services to be accredited by the National Aerospace and Defense Contractors Accreditation Program (NADCAP). NADCAP accreditation is granted in accordance with SAE AS7003 after demonstration of compliance with the requirements herein. The requirements may be supplemented by additional requirements specified by the NADCAP Nonconventional Machining and Surface Enhancement (NMSE) Task Group. Using the corresponding Audit Criteria (PRI AC7116) will ensure that accredited Nonconventional Machining suppliers meet all of the requirements in this standard and all applicable supplementary standards. The purpose of this audit program is to assess a supplier's ability to consistently provide a product or service that conforms to the technical specifications and customer 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).

This Handbook is intended to accompany or incorporate AS5643, AS5643/1, AS5657, AS5706, and ARD5708. In addition, full understanding of this Handbook also requires knowledge of IEEE-1394-1995, IEEE-1394a, and IEEE-1394b standards. This Handbook contains detailed explanations and architecture analysis on AS5643, bus timing and scheduling considerations, system redundancy design considerations, suggestions on AS5643-based system configurations, cable selection guidance, and lessons learned on failure modes.

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.

This document includes a standard set of management practices that can be used, or espoused, by the OEMs for use during the design and development of electronic systems to mitigate the effects of future Diminishing Manufacturing Sources and Material Shortages (DMSMS). While this document focuses primarily on microelectronic devices, the methods described here may also apply to other commodities.

This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc. This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems.

This recommended practice provides guidance on vehicle Cybersecurity and was created based off of, and expanded on from, existing practices which are being implemented or reported in industry, government and conference papers. The best practices are intended to be flexible, pragmatic, and adaptable in their further application to the vehicle industry as well as to other cyber-physical vehicle systems (e.g., commercial and military vehicles, trucks, busses). Other proprietary Cybersecurity development processes and standards may have been established to support a specific manufacturer’s development processes, and may not be comprehensively represented in this document, however, information contained in this document may help refine existing in-house processes, methods, etc. This recommended practice establishes a set of high-level guiding principles for Cybersecurity as it relates to cyber-physical vehicle systems.

This document defines the characteristics necessary to standardize the airborne recorder download file format in order to facilitate data import, transcription, and exchange. A standardized data format will reduce the variety of readout equipment required for airborne recorder data transcription. This document defines the detailed architecture of the Recorder Standard Output (RSO) file. The architecture is a tagged file structure within which many different files and their formats can be supported. The structure is necessary to support newer recording requirements for flight data, data link, audio, and image recording. This structure is intended for use with all civil recorders and should support use with military recorders.