The purpose of this SAE Aerospace Standard (AS) is to provide a description of the temper nomenclature system for aluminum alloys used in the aerospace industry by combining information from different sources for the benefit of the user.
This SAE Aerospace Standard (AS) defines the minimum performance standard to demonstrate compliance with the regulatory design, test and operational requirements for a Temperature Controlled Container (TCC).
This standard defines logistics product data generated during the requirements definition and design of an industry or government system, end item or product. It makes use of the Extensible Markup Language (XML) through the use of entities and attributes that comprise logistics product data and their definitions. The standard is designed to provide users with a standard set of data tags for all or portions of logistics product data and customer defined sub-sets of logistics product data. The standard can be applied to any indsutry or government product, system or equipment acquisition program, major modification program, and applicable research and development projects. This standard is for use by both industry and government activities. As used in this standard, the requiring authority is generally the customer and the customer can be a government or industry activity. The performing activity may be either a industry or government activity.
This handbook is intended to provide additional information on the use and tailoring of the data in GEIA-STD-0007. The standard provides a new approach to Logistics Support Analysis Record (LSAR) (i.e., MIL-STD-1388-2B) data with emphasis on data transfer (e.g., XML Schemas) versus data storage (e.g., relational tables). GEIA-STD-0007 identifies the range of logistics product data that is generated during the development and acquisition of a system or end item. It does not prescribe the supportability analyses required to generate logistics product data. How the data is generated via analysis techniques/tools, how it is stored and processed, and how the data is used to generate specific logistics support products, is left to the performing activity. GEIA-STD-0007 is a data transfer standard implementing the logistics data concepts of GEIA-STD-927, Common Data Schema for Complex Systems.
This Standard specifies the minimum derating requirements for using electronic components in moderately severe environments. These environments are assumed to include Airborne Inhabited Cargo (AIC), Airborne Inhabited Fighter (AIF), Ground Mobile (GM), and Naval Sheltered (NS) environments specified in MIL-HDBK-217. This Standard is intended to supersede the derating limits contained in Defense Standardization Program Office (DSPO) Standardization Directive SD-18, Naval Standard TE000-AB-GTP-010, and Air Force ESD-TR-85-148. It is intended that a future revision of this Standard will include additional requirements for derating for other environments (e.g. Airborne Uninhabited Cargo). Since this Standard specifies the minimum derating requirements, (sub)contractors may derate in excess of these requirements.
This Technical Bulletin covers the following areas of concern. Prevention: Actions recommended for procuring parts and materials with a full warranty; Actions recommended for minimizing risks and protecting your Program from counterfeiting; Actions recommended when buying from a non-authorized supplier. Detection: Actions recommended when procuring parts from an unauthorized supplier or otherwise suspect that a part or material at risk of being counterfeit has been procured. Risk Mitigation: Actions recommended when no reasonable alternatives exist (e.g., a redesign is required, an unacceptable schedule delay will result, the program or customer cannot bear the additional cost) and the decision has been made to procure from a non-authorized supplier.
This Standard is intended to enable an enterprise to strengthen its competitiveness in global markets by engineering and producing quality systems, and by delivering its products on time at an affordable price or cost. The focus, therefore, is on conceptualizing, creating and realizing a system and the products that make up a system. This Standards was developed as a joint project of the Electronic Industries Alliance (EIA) and the International Counci on Systems Engineering (INCOSE). This effort was chartered by the G-47 Systems Engineering Committee of EIA and has been designed as Project PN-3537. this Standard has been approved by the EIA Engineering Department Executive Committee.
The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae] JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (see Figure 1). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.
The primary focus of this standard is information of interest to Configuration Management (CM) practitioners related to the performance of CM functions as products are conceived, proposed, defined, developed, produced, operated, maintained, modified, and disposed. This information is stored when generated and, from time to time, must be moved or shared with others. This standard, through the use of the Data Dictionary, defines real world things of interest to the CM practitioner, which are the foundation of the following CM functional areas, and are needed for effective data exchange and interoperability: Configuration Management Planning and Management; Configuration Identification; Configuration Change Management; Configuration Audit; Configuration Verification; Configuration Status Accounting.
This standard defines uniform quality and technical requirements relative to metallic parts marking performed using "data matrix symbology" within the aviation, space, and defense industry. ISO/IEC 16022 specifies general requirements (e.g., data character encodation, error correction rules, decoding algorithm). In addition to ISO/IEC 16022 specification, part identification with such symbology is subject to the requirements in this standard to ensure electronic reading of the symbol. The marking processes covered by this standard are as follows: - Dot Peening - Laser - Electro-Chemical Etching Further marking processes will be included, if required. Unless specified otherwise in the contractual business relationship, the company responsible for the design of the part shall determine the location of the data matrix marking. Symbol position should allow optimum illumination from all sides for readability. This standard does not specify information to be encoded.
This document describes requirements for standardized processes (and associated technologies) that ensure type design data are retrievable and usable for the life of a type certificate (50+ years). These processes are primarily concerned with, but not limited to, digital type design data retained in threedimensional representations and associated data that is required for complete product definition, such as tolerances, specification call-outs, product structure and configuration control data, etc. This process standard includes process requirements for managing the evolution of technologies required to ensure the availability of the data for the life of the product. This data must be available to meet regulatory, legal, contractual and business requirements. This process standard is not intended to incorporate every company specific requirement and does not dictate specific organizational structures within a company.
Fibre Channel is the primary avionics bus on many modern military aircraft. It is also the defined High-Speed bus for MIL-STD-1760E weapons applications. Profiled Ethernet networks are the primary avionics bus in many commercial aircraft and Commercial Ethernet is an ever increasing presence in modern military aircraft as well. This network standard is a convergence of Fibre Channel and Ethernet into a unified network standard which will provide a seamless approach to integrating end systems from either technology into a merged network structure. This work is based upon the commercial data storage market industry’s work on the Converged Data Storage Network or FCoE (Fibre Channel over Ethernet). This effort will look at profiling the FCoE work done in the commercial industry and adding information where necessary to affect a networking standard that will seamlessly integrate end systems from Commercial Ethernet, Fibre Channel, or FCoE enhanced devices.
This standard only defines interconnect, electrical and logical (functional) requirements for the interface between a Micro Munition and the Host. The physical and mechanical interface between the Micro Munition and Host is undefined. Individual programs will define the relevant requirements for physical and mechanical interfaces in the Interface Control Document (ICD) or system specifications. It is acknowledged that this does not guarantee full interoperability of Interface for Micro Munitions (IMM) interfaces until further standardization is achieved.
Fraudulent/Counterfeit Electronic Parts: Avoidance, Detection, Mitigation, and Disposition - DistributorsCounterfeit Electronic Parts; Avoidance Protocol, Distributors
This SAE Aerospace Standard standardizes practices to: a. identify reliable sources to procure parts, b. assess and mitigate risk of distributing fraudulent/counterfeit parts, c. control suspect or confirmed fraudulent/counterfeit parts, d. and report suspect and confirmed fraudulent/counterfeit parts to other potential users and Authority Having Jurisdiction.
The aviation, space, and defense industries rely on the development and manufacture of complex products comprised of multiple systems, subsystems, and components each designed by individual designers (design activities) at various levels within the supply chain. Each design activity controls various aspects of the configuration and specifications related to the product. When a change to design information is requested or required, the change has to be evaluated against the impacts to the higher-level system. Proposed changes to design information that the design activity identifies to be minor and have no effect on their product requirements or specifications have the potential to be concurrently implemented and approved, where authorized to do so. Changes that affect customer mandated requirements or specifications must be approved prior to implementation.
This SAE Standard is intended to describe the basic types of felling heads, including those with bunching capabilities, that are attachments to a self-propelled machine. Only the major components that are necessary to describe the functions to the felling head, and to apply the principles of the recommended practice are included. Illustrations used are not intended to include all existing felling heads or to describe any particular manufacturer's variation.
This standard defines the minimum requirements for conducting Measurement Systems Analysis (MSA) for variable and attribute assessment on characteristics as defined on the drawing or specification. It does not define the detailed analytical methods for each type of study as these can be found in existing published texts (see Section 2 for guidance).
The standard applies to aero engine suppliers operating a self-release process as a delegated activity from the delegating organization. While primarily developed around the aero engine supply chain requirements, this standard can also be used in other industry sectors where a self-release process may be of benefit.
This SAE Aerospace Standard (AS) provides classical propulsion system performance parameter names for aircraft propulsion systems and their derivatives, and describes the logical framework by which new names can be constructed. The contents of this document were, originally, a subset of AS755E. Due to the growing complexity of station numbering schemes described in AS755, and a desire to expand the original document's nomenclature section to include a fuller representation of "classical" (legacy use) names, a decision was made to separate its "station numbering" and "nomenclature" content into two separate documents. This document, then, was created using the "nomenclature" half of AS755E. Both documents will continue to be improved and revised as industry needs dictate. The parameter naming conventions presented herein are for use in all communications concerning propulsion system performance such as computer programs, data reduction, design activities, and published documents.
Bolts and Screws, Nickel Alloy UNS N07718, Classification: 185 ksi/1200 °F, Procurement Specification
This procurement specification covers bolts and screws made from a corrosion and heat resistant, age hardenable nickel base alloy of the type identified under the Unified Numbering System as UNS N07718.
Definition of Commonly Used Day Types (Atmospheric Ambient Temperature Characteristics Versus Pressure Altitude)
"Hot Day ", "Tropical Day ", "Standard Day ", "Polar Day " and "Cold Day " are part of the lexicon of the aircraft industry. These terms are generally understood to refer to specific, generally accepted characteristics of atmospheric temperature versus pressure altitude. There are also other, less well-known days, defined by their frequency of occurrence, such as "1% Hot Day ", "10% Cold Day ", or "Highest Recorded Day ". These temperature characteristics have their origins in multiple sources, including U.S. military specifications which are no longer in force.
This document discusses the work done by the U.S. Army Corps of Engineers and the Waterways Experiment Station (WES) in support of SAE A-5 Committee activity on Aerospace Landing Gear Systems. It is an example of how seemingly unrelated disciplines can be combined effectively for the eventual benefit of the overall aircraft systems, where that system includes the total airfield environment in which the aircraft must operate. In summary, this AIR documents the history of aircraft flotation analysis as it involves WES and the SAE.
This SAE Aerospace Standard (AS) will specify what type night vision goggles are required, minimum requirements for compatible crew station lighting, aircraft exterior lighting such as anticollision lights and position/navigation lights that are "NVG compatible." Also, this document is intended to set standards for NVG utilization for aircraft so that special use aircraft such as the Coast Guard, Border Patrol, Air Rescue, Police Department, Medivacs, etc., will be better equipped to chase drug smugglers and catch illegal immigrants, rescue people in distress, reduce high-speed chases through city streets by police, etc. Test programs and pilot operator programs are required. For those people designing or modifying civil aircraft to be NVG compatible, the documents listed in 2.1.3 are essential.
This document is used for placing Configuration Management Requirements on Defense Contracts after being tailored by the Acquirer. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. The planning and execution of Configuration Management (CM) is an essential part of the product development and life cycle management process. It provides control of all configuration documentation, physical parts and software representing or comprising the product. Configuration Management's overarching goal is to establish and maintain consistency of a product's functional and physical attributes with its requirements, design and operational information throughout its life cycle. When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule.
This standard is applicable to all phases of the system acquisition life cycle. It is intended for use on all programs with manufacturing content. It requires proven manufacturing management practices with the goal of delivering affordable and capable systems to the extent that it is invoked contractually. The term “organization” as used in this document refers to the company or facility that is implementing this standard, such as when imposed contractually by the customer. NOTE: The term “shall” is used wherever the criterion for conformance with the specific recommendation requires that there be no deviation. The term “should” is used wherever noncompliance with the specific recommendation is permissible.
This Recommended Practice (RP) document will provide guidance on performing a non-handbook reliability prediction for automotive electronic products by utilizing field return data. It will include a description of what kind of data is required, possible sources of data, how to collect it, and the methodology of how to process these data to obtain failure rates. This document will also include the existing failure rate data Delphi Electronics & Safety is currently using for reliability prediction and the Excel-based tool for these types of calculations.
Solid chemical oxygen supplies of interest to aircraft operations are 'chlorate candles' and potassium superoxide (KO 2 ). Chlorate candles are used in passenger oxygen supply units and other emergency oxygen systems, such as submarines and escape devices. Potassium superoxide is not used in aircraft operations but is used in closed-cycle breathing apparatus. Characteristics and applications of both are discussed, with emphasis on chlorate candles.
The aviation, space, and defense industries rely on the development and manufacture of complex products comprised of multiple systems, subsystems, and components each designed by individual designers (design activities) at various levels within the supply chain. Each design activity controls various aspects of the configuration and specifications related to the product. When a change to design information is requested or required, the change has to be evaluated against the impacts to the higher-level system. Proposed changes to design information that the design activity identifies to be minor and have no effect on their product requirements or specifications have the potential to be concurrently implemented and approved, where authorized to do so. Changes that affect customer mandated requirements or specifications shall be approved prior to implementation.
This standard requires the developers and customer/user's working as a team to plan and implement a reliability program that provides systems/products that satisfy the user's requirements and expectations. The user's requirements and needs are expressed in the form of the following four reliability objectives: The developer shall solicit, investigate, analyze, understand and agree to the user's requirements and product needs. The developer, working with the customer and user, shall include the activities necessary to ensure that the user's requirements and product needs are fully understood and defined, so that a comprehensive design specification and Reliability Program Plan can be generated; The developer shall use well-defined reliability- and systems-engineering processes to develop, design, and verify that the system/product meets the user's documented reliability requirements and needs.