This document aims to establish best practices in equipment setup and measurement of brake rotor disk thickness variation (DTV) on vehicle.
This SAE Standard establishes a vocabulary and definitions relating to the components used in fuel injection systems for compression ignition (diesel) engines. Definitions are separated into six sections by topic as follows: Section 3--Fuel Injection Pumps Section 4--Fuel Injectors Section 5--Unit Injectors Section 6--Governors Section 7--Timing Devices Section 8--High Pressure Pipes and Connections When the word "fuel" is used in the terms listed it may be omitted providing there can be no misunderstanding.
This document is intended to supplement SAE J2403 by providing the content of Table 1, Table 2, and Table 3 from SAE J2403 in a form that can be sorted and searched for easier use. It is NOT intended as a substitute for the actual document, and any discrepancies between this Digital Annex and the published SAE J2403 document must be resolved in favor of the published document. This document provides the content of Table 1 and Table 2 published in SAE J2403 into the single table in the 'Term' tab, while the 'Recommended Term Definitions' tab provides the content of Table 3 in SAE J2403 and the 'Glossary' tab provides the content of Table 4 in SAE J2403.
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 Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions and EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
This document provides additional guidance on performing lifetime assessments and mitigations for ARP6338. It is intended for use by designers, reliability engineers, and others associated with the design, production, and support of electronic sub-assemblies, assemblies, and equipment used in ADHP applications.
This standard provides performance and test requirements for operator restraint systems provided for off-road self-propelled work machines. This document applies to pelvic restraint systems (Type 1) for off-road, self-propelled work machines fitted with ROPS and commonly used in construction, earthmoving, forestry, and mining as referred to in SAE J1040 and industrial machines fitted with ROPS as referred to in SAE J1042.
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.
Technique for Suspect/Counterfeit EEE Parts Detection by Secondary Ion Mass Spectrometry (SIMS) Test Method
To define capabilities and limitations of SIMS as it pertains to counterfeit detection of EEE parts and suggest possible applications to these ends. Additionally, this document outlines requirements associated with the application of SIMS including: Operator training; Sample preparation; Data interpretation; Equipment maintenance; and Reporting of data.
TECHNIQUES FOR SUSPECT/COUNTERFEIT EEE PARTS DETECTION OF CAPACITORS BY ACOUSTIC MICROSCOPY (AM) TEST METHODS
Acoustic Microscopy Test Methods for Counterfeit Capacitors
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 product includes information on the manufacturer, engine, application, testing location, certified maximum horsepower, certified maximum torque along with the certified curves of horsepower and torque over a wide range of engine RPM speeds.
SAE developed this document and associated spreadsheets at the request of automobile manufacturers to help compare products from multiple suppliers using standard data presentation formats. This document includes several preferred formats for presenting acoustical data on materials, components, systems, or vehicles. These formats cover the range of acoustical tests commonly conducted in the automotive industry. These tests follow SAE and ASTM test practices as well as vehicle specific test methods. For each test, the details of samples and test conditions can be entered into an applicable electronic spreadsheet together with the acoustical results data. These data are then linked to standard graphical display(s) for each test. All manufacturers and suppliers in this industry are encouraged to present data and results in these formats.
Since it is impossible to be all inclusive and cover every aspect of the design/validation process, this document can be used as a basis for preparation of a more comprehensive and detailed plan that reflects the accumulated "lessons learned" at a particular company. The following areas are addressed in this document: 1. Contemporary perspective including common validation issues and flaws. 2. A Robustness Validation (RV) process based on SAE J1211 handbook and SAE J2628. 3. Design checklists to aid in such a RV process.
This interface document SAE J2286 revises the requirements for file formats as were originally described in SAE J1924. This document describes Interface 1 (I/F 1) in SAE J2461. This document does not imply the use of a specific hardware interface, but may be used with other hardware interfaces such as SAE J1939, ISO 15765 or ISO 14229. The requirements of SAE J2286 supersede the requirements defined by SAE J1924. SAE J2461 establishes the requirements for Interface 1 (I/F 1), as a replacement of the file-based interface described by SAE J1924, as shown by Figure 1. Interface 1 (I/F) is a bi-directional link between the OEM Shop Floor Program (CSCI 1) and the Vendor Component Program (CSCI 2). Using I/F 1, the OEM Shop Floor Program communicates the desired parameters and programming limits for an assembly job to the Vendor Component Program (VCP). In response, the VCP returns programming results to the OEM Shop Floor Program (CSCI 1).
This SAE Recommended Practice applies to all portions of the vehicle, but design efforts should focus on components and systems with the highest contribution to the overall average repair cost (see 3.7). The costs to be minimized include not only insurance premiums, but also out-of-pocket costs incurred by the owner. Damageability, repairability, serviceability and diagnostics are inter-related. Some repairability, serviceability and diagnostics operations may be required for collision or comprehensive loss-related causes only, some operations for non-collision-related causes only (warranty, scheduled maintenance, non-scheduled maintenance, etc.), and some for both causes. The scope of this document deals with only those operations that involve collision and comprehensive insurance loss repairs.
Guideline for Development of Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition Systems
This document contains guidance for implementing a counterfeit mitigation program in adherence with AS5553B.
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.
This classification system tabulates the properties of vulcanized rubber materials (natural rubber, reclaimed rubber, synthetic rubbers, alone or in combination) that are intended for, but not limited to, use in rubber products for automotive applications. NOTE 1: The SAE Committee on Automotive Rubber Specifications (CARS) has the sole responsibility for SAE J200. CARS Works closely with and receives input from ASTM Subcommittee D11.30 on Classification of Rubber Compounds with the goal to keep SAE J200 and ASTM D 2000 technically equivalent. Candidate materials presented for development of new tables or for inclusion in Tables A1 or A2 of SAE J200 or Table X1.1 of ASTM D 2000 shall be initiated with the SAE CARS Committee. The procedure to be followed is detailed in Appendix C of SAE J200. NOTE 2: This document may serve many of the needs of other industries in much the same manner as SAE numbered steels.
This SAE Recommended Practice identifies and defines terms specifically related to brake systems.
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 SAE Recommended Practice presents a method and example results for determining the Automotive Safety Integrity Level (ASIL) for automotive electrical and electronic (E/E) systems. This activity is required by ISO 26262-3:2011 , and it is intended that the process and results herein are consistent with ISO 26262:2011 . The technical focus of this document is on vehicle motion control systems. It is limited to passenger cars weighing up to 3.5 metric tons. Furthermore, the scope of this recommended practice is limited to collision-related hazards. ISO 26262:2011  has a wider scope than SAE J2980, covering other functions and accidents (not just motion control or collisions as in SAE J2980).
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.
Historically SAE has been concerned with nomenclature as an integral part of the standards development process. Guidelines for automotive nomenclature were written in 1916, were last revised in 1941, and were included in the SAE Handbook until 1962. The present diversity of groups working on nomenclature in the various ground vehicle committees led to the organization of the Nomenclature Advisory Committee under SAE Automotive Council.
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.