Your Destination for Mobility Engineering Resources
Announcements for SAE Mobilus
Browse AllRecent SAE Edge™ Research Reports
Browse All 177Latest Journal Issues
Browse All 16
Recent Books
Browse All 720Recently Published
Browse AllThis SAE Aerospace Information Report (AIR) developed by a broad cross section of personnel from the aviation industry and government agencies is offered to provide state-of-the-art information for the use of individuals and organizations designing new or upgraded turboshaft engine test facilities. This document is also applicable to turboprop engines tested with a dynamometer as load absorption device, as they are basically tested as turboshaft engines. For propeller-equipped turbofan testing facilities design considerations, see 2.1.7.
The intent of this specification is for the procurement of 7781 glass fabric epoxy prepreg product with 250 °F (121 °C) cure for aerospace applications; therefore, no qualification or equivalency threshold values are provided. Users that intend to conduct a new material qualification or equivalency program must refer to the production quality assurance section (see 4.3).
The purpose of this SAE Aerospace Information Report (AIR) is to provide management, designers, and operators with information to assist them to decide what type of power train monitoring they desire. This document is to provide assistance in optimizing system complexity, performance, and cost effectiveness. This document covers all power train elements from the point at which energy in a turbine or electric engine is converted via a gear train to mechanical energy for propulsion purposes. The document covers aircraft engine driven transmission and gearbox components, their interfaces, drivetrain shafting, drive shaft hanger bearings, and associated rotating accessories, propellers, and rotor systems as shown in Figure 1. For guidance on monitoring additional engine components not addressed herein (e.g., main shaft bearings and compressor/turbine rotors), refer to ARP1839. This document addresses rotary and fixed wing applications for rotor, turboprop, turbofan, prop fan, and lift fan
Since 2019, sex equity in traffic crashes has been a highly debated topic in vehicle safety, especially following the 2019 study by Forman et al. (1) claiming that female occupants face a 73 percent greater risk of serious injury in frontal crashes compared to male occupants. This was soon followed by a Consumer Reports Article by Keith Barry (2), which attempted to identify underlying factors contributing to the higher risk. These have been embraced by several parties since 2019. Firstly, it was alleged that vehicle design practice over the last four decades considered safety for the male population only and ignored that of the female as evidenced by the exclusive use of the mid-sized male Anthropomorphic Test Devices (ATDs) in Regulatory and Safety Ratings tests and not with an average sized female ATD. The absence of such an ATD for testing of vehicles “set the course for four decades’ worth of car safety design, with deadly consequences” (2). Secondly, although there is a
This document presents criteria for flight deck controls and displays for Airborne Collision Avoidance Systems.
This document establishes the minimum training and qualification requirements for ground-based aircraft deicing methods and procedures. All guidelines referred to herein are applicable only in conjunction with the applicable documents. Due to aerodynamic and other concerns, the application of deicing fluids shall be carried out in compliance with engine and aircraft manufacturers’ recommendations. The scope of training should be adjusted according to local demands. There are a wide variety of winter seasons and differences of the involvement between deicing operators, and therefore, the level and length of training should be adjusted accordingly. However, the minimum level of training shall be covered in all cases. As a rule of thumb, the amount of time spent in practical training should equal or exceed the amount of time spent in classroom training.
This specification covers an aluminum alloy in the form of sheet 0.040 to 0.249 inch (1.02 to 6.32 mm) in nominal thickness (see 8.7).
This Surface Vehicle & Aerospace Recommended Practice offers best practices and a methodology by which IVHM functionality relating to components and subsystems should be integrated into vehicle or platform level applications. The intent of the document is to provide practitioners with a structured methodology for specifying, characterizing and exposing the inherent IVHM functionality of a component or subsystem using a common functional reference model, i.e., through the exchange of design-time data and the application of standard vehicle data communications interfaces. This document includes best practices and guidance related to the specification of the information that must be exchanged between the functional layers in the IVHM system or between lower-level components/subsystems and the higher-level control system to enable health monitoring and tracking of system degradation severity. The intent is to provide an IVHM system that can robustly report the degradation of a given
The importance of reliability in design engineering has significantly grown since the early 1960’s. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance
This SAE standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a. The supplier shall ascertain customer requirements b. The supplier shall meet customer requirements c. The supplier shall assure that customer requirements have been met
SAE JA6097 (“Using a System Reliability Model to Optimize Maintenance”) shows how to determine which maintenance to perform on a system when that system requires corrective maintenance to achieve the lowest long-term operating cost. While this document may focus on applications to Jet Engines and Aircraft, this methodology could be applied to nearly any type of system. However, it would be most effective for systems that are tightly integrated, where a failure in any part of the system causes the entire system to go off-line, and the process of accessing a failed component can require additional maintenance on other unrelated components.
This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle.
In 1994 the SAE G-11 Reliability, Maintainability, Supportability, and Logistics (RMSL) Division chartered a software committee, G-11SW, to create several software standards and guidance documents across the RMSL spectrum, including a software supportability program standard. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has attempted to develop a standard that is consistent with a SAE G-11 system level supportability program standard and augmented by necessary software-specific support information. The G-11SW committee believes this document reflects the best current commercial practices, and meets the objectives of the United States Department of Defense Acquisition Reform initiative. This document is performance based and is intended to be used by industries to address market demands for supportable software products that facilitate system evolution, time to market, and implementation of
This SAE Standard establishes the requirement for suppliers to plan a reliability program that satisfies the following three requirements: a. The supplier shall ascertain customer requirements; b. The supplier shall meet customer requirements; c. The supplier shall assure that customer requirements have been met. This document applies to the specification, design and development, and assurance of any product. This document does not specify the method to be included in the program. Rather, the content of each program must be tailored to satisfy customer requirements using the most appropriate means.
In 1994, the SAE G-11 Reliability, Maintainability, Supportability and Logistics (RMSL) Division chartered a software committee, G-11SW, to create several software standards and guidance documents across the RMSL spectrum, including a software reliability program standard and implementation guidelines. The committee was formed as a cross section of international representatives from commercial industries and governments. The G-11SW committee has developed a standard (JA1002) and these implementation guidelines (JA1003) that are consistent with a SAE G-11 system level reliability program standard (JA1000) and guidelines (JA1000-1), augmented by necessary software-specific information. The G-11SW committee believes these documents reflect the best current commercial practices, and meet the objectives of the United States Department of Defense Acquisition Reform initiative and the North Atlantic Treaty Organization (NATO) Reliability Program. The JA1002 program standard is intended to be
The importance of reliability in design engineering has significantly grown since the early Sixties. Competition has been a primary driver in this growth. The three realities of competition today are: world class quality and reliability, cost-effectiveness, and fast time-to-market. Formerly, companies could effectively compete if they could achieve at least two of these features in their products and product development processes, often at the expense of the third. However, customers today, whether military, aerospace, or commercial, have been sensitized to a higher level of expectation and demand products that are highly reliable, yet affordable. Product development practices are shifting in response to this higher level of expectation. Today, there is seldom time, or necessary resources to extensively test, analyze, and fix to achieve high quality and reliability. It is also true that the rapid growth in technology prevents the accumulation of historical data on the field performance
This document identifies recommended practices for the implementation of a supportability program for software within an overall systems engineering framework. Guidelines for implementation of a Software Supportability Plan and associated Software Supportability Case are presented. Recommended practices are described for establishing a software supportability program through selection of life cycle activity tasks tailored for the application. Recommended models and process methods to achieve the life cycle activity tasks are briefly reviewed and/or referenced. The recommended practices are applicable to all projects incorporating software. The target audience for this document includes software acquisition organizations, logisticians, developers, supporters, and customers. This document is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software.
Historically, the supportability aspects of software have been given a very low priority in the overall program requirements. This was particularly prevalent during the acquisition phase, where funding and timing constraints were usually the top priorities. The result was inadequate product supportability, inadequate support funding, lack of good field data, and no meaningful analysis and optimization of possible support alternatives. In order to alleviate these historical concerns, this document presents a top-level structured overview of an overall software support concept and the information associated with it. This document was developed by the Supportability Subcommittee of the Society of Automotive Engineers (SAE) G-11 Reliability, Maintainability, Supportability, and Logistics (RMSL) Software Committee (G-11SW). G-11SW and its different Subcommittees plan to develop several more detailed reports that together will form an integrated task guide for analyzing software