Criteria

Text:
Content:
Display:

Results

Viewing 241 to 270 of 1276
CURRENT
2016-03-30
Standard
J2945/1_201603
This standard specifies the system requirements for an on-board vehicle-to-vehicle (V2V) safety communications system for light vehicles1, including standards profiles, functional requirements, and performance requirements. The system is capable of transmitting and receiving the Society of Automotive Engineers (SAE) J2735-defined Basic Safety Message (BSM) [1] over a Dedicated Short Range Communications (DSRC) wireless communications link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 suite and IEEE 802.11 standards [2] – [6].
CURRENT
2016-03-30
Standard
J2735_201603
This SAE Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”) communications systems. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
HISTORICAL
2016-03-05
Standard
AS8049/1A
This SAE Aerospace Standard (AS) defines Minimum Performance Standards (MPS), qualification requirements, and minimum documentation requirements for side-facing seats in civil rotorcraft, transport aircraft, and general aviation aircraft. The goal is to achieve comfort, durability, and occupant protection under normal operational loads and to define test and evaluation criteria to demonstrate occupant protection when a side-facing seat/occupant/restraint system is subjected to statically applied ultimate loads and to dynamic test conditions set forth in Title 14, Code of Federal Regulations (CFR) Part 23, 25, 27, or 29. While this document addresses system performance, responsibility for the seating system is divided between the seat supplier and the installation applicant. The seat supplier’s responsibility consists of meeting all the seat system performance requirements and obtaining and supplying to the installation applicant all the data prescribed by this document.
2016-03-03
WIP Standard
EIA649C
When effectively and consistently applied, Configuration Management (CM) provides a positive impact on product quality, cost, and schedule. This standard is intended to assist in establishing, performing, or evaluating CM systems. CM is an integrated system of processes that ensure consistency of a product's performance, functional and physical attributes with its requirements, design, and operational information. The essence of CM, as portrayed in this consensus standard, is the common application of CM functions and their underlying fundamental principles, which have universal applicability across the broad spectrum of commercial and government enterprises. The standard provides an understanding of what to do, why a customer/suppler should do it, and when it is necessary to tailor the application of CM functions. This standard fulfills the important function of providing a rational basis upon which to apply good judgment in both planning for and executing CM across the enterprise.
2016-03-03
WIP Standard
EIA649_1A
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.
CURRENT
2016-03-02
Standard
J1698/1A_201603
SAE J1698-1A creates an appendix to SAE J1698-1. The appendix contains EDR Record parameters and definitions related to light duty passenger vehicle pedestrian protection systems.
CURRENT
2016-03-01
Standard
GEIAHB649A
This handbook is intended to assist the user to understand the ANSI/EIA-649B standard principles and functions for Configuration Management (CM) and how to plan and implement effective CM. It provides CM implementation guidance for all users (CM professionals and practitioners within the commercial and industry communities, DoD, military service commands, and government activities (e.g., National Aeronautics and Space Administration (NASA), North Atlantic Treaty Organization (NATO)) with a variety of techniques and examples. Information about interfacing with other management systems and processes are included to ensure the principles and functions are applied in each phase of the life cycle for all product categories.
CURRENT
2016-02-24
Standard
GEIAHB0005_1A
This handbook is designed to assist a program in assuring the performance, reliability, airworthiness, safety, and certifiability of product(s), in accordance with GEIA-STD-0005-1, “Performance Standard for Aerospace and High Performance Electronic Systems Containing Pb-free Solder”. Please note that the program manager, and managers of systems engineering, Supply Chain and Quality Assurance (along with their respective organizations), and the appropriate enterprise authority need to work together in ensuring that all impacts of Pb-free technology insertion are understood and risks mitigated accordingly. Herein “program management (or manager), supplier chain management (or manager), quality assurance management (or manager) and systems engineering management (or manager) and/or the appropriate enterprise authority” shall be defined as “responsible manager” throughout the remaining document (see Section 3, Terms and Definitions).
HISTORICAL
2016-02-24
Standard
AS1814D
This list of terms, with accompanying photomicrographs where appropriate, is intended as a guide for use in the preparation of material specifications.
HISTORICAL
2016-02-24
Standard
J1939DA_201602
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use. The J1939 Digital Annex, introduced in August 2013, offers key J1939 technical data in an Electronic Spreadsheet that can be easily searched, sorted, and adapted to other formats. J1939DA contains all of the SPNs (parameters), PGNs (messages), and other J1939 data previously published in the SAE J1939 top level document. J1939DA also contains all of the SLOTs, Manufacturer ID Codes, NAME Functions, and Preferred Addresses previously published in the SAE J1939 top level and the J1939-71 document. J1939DA contains the complete technical details for all of the SPNs and PGNs previously published in the SAE J1939-71 document. It also includes the supporting descriptions and figures previously published in the SAE J1939-71 document.
2016-02-19
WIP Standard
J3061
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.
HISTORICAL
2016-02-18
Standard
J2403DA_201602
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.
HISTORICAL
2016-02-18
Standard
J1939/81_201602
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. Network management is concerned with the management of source addresses and the association of those addresses with an actual function and with the detection and reporting of network related errors. Due to the nature of management of source addresses, network management also specifies initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
2016-02-15
WIP Standard
AS6171/16
Netlist Assurance Test Methods exist to assess microcircuit designs for maliciously added, removed, or modified functions detrimental to system operation. In the context of the Microcircuit fabrication design process, these methods will be used to analyze a computer aided design (CAD) representation of the microcircuit. The Netlist Assurance Test Methods discover vulnerabilities, undisclosed functions (e.g. "kill switch", paths to leak passwords, or triggers of malicious activity) and changes from the original specifications of the devices. These methods are intended to be used with standard verification methods that the implemented design has remained unchanged through the many transformations in the design flow.
2016-02-04
WIP Standard
J3131
SAE J3131 defines an automated driving reference architecture that contains functional modules supporting future application interfaces for Levels 3 through 5 (J3016). The architecture will model scenario-driven functional and nonfunctional requirements, automated driving applications, functional decomposition of an automated driving system, and relevant functional domains (i.e., functional groupings). Domains include, but are not limited to, automated driving (i.e., automation replacing the human driver), by-wire and active safety, and those related to automated recovery from faults and system failures (e.g., system bringing the vehicle to a safe state). The architecture will address Tier 1 and Tier 2 functional groupings. The document will include one example instantiation being divides the functionality into two functionality groupings, and will detail the functional and information interface between the groups.
2016-02-03
WIP Standard
AS6171/15
Non-conformance and now Suspect counterfeit packaging represents a hazard to electrostatic discharge (ESD) sensitive devices or components through cross contamination during transport and storage while generating high voltage discharges to ESD sensitive devices during in shipping, the inspection process, handling and manufacturing. Several aerospace related issues involve long-term storage supplier non-conformance with antistatic foams, antistatic bubble, antistatic pink poly, vacuum formed antistatic polymers, Type I moisture barrier bags and Type III static shielding bags have posed issues. The late John Kolyer, Ph.D. (Boeing, Ret.) and Ray Gompf, P.E., Ph.D. (NASA-KSC, Ret.) were advocates in the utilization of a formalized physical testing material qualification process. Today, however, prime contractors and CMs rely heavily upon a visual inspection process for ESD packaging materials.
2016-01-26
WIP Standard
ARIR446
The intent of this standard is to provide guidance so the documentation provided with the Flight Simulation Training Device (FSTD) reflects and describes the delivered FSTD, including the description and definition of third party equipment and content. In the context of documentation guidance found in this report, the term FSTD is meant to include all levels of flight simulation devices. The documentation described herein is required for the operator to independently support the FSTD in the maintenance, operation, and update of the device throughout the lifetime of the device. This report describes a superset of a possible range of documentation involved in the initial delivery or an update of a FSTD. The deliverable documentation set for a particular FSTD may vary depending on the level of device (e.g., flat panel trainer versus a full flight simulator) as well as issues related to intellectual property, export compliance, technical requirements, and/or contractual agreements.
HISTORICAL
2016-01-19
Standard
J2735_201601
This SAE Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”) communications systems. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
CURRENT
2016-01-14
Standard
J3061_201601
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.
CURRENT
2016-01-02
Standard
AS1614D
This SAE Aerospace Standard (AS) specifies the interface requirements for tow bar attachment fittings on the nose gear (when towing operations are performed from the nose gear) of conventional tricycle type landing gears of commercial civil transport aircraft with a maximum ramp weight higher than 50,000 kg (110,000 pounds), commonly designated as “main line aircraft”. Its purpose is to achieve tow bar attachment fittings interface standardization by aircraft weight category (which determines tow bar forces) in order to ensure that one single type of tow bar with a standard connection can be used for all aircraft types within or near that weight category, so as to assist operators and airport handling companies in reducing the number of different tow bar types used.
CURRENT
2016-01-02
Standard
AS1990D
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.
2015-12-31
WIP Standard
J670
The vehicle dynamics terminology presented herein pertains to passenger cars and light trucks with two axles and to those vehicles pulling single-axle trailers. The terminology presents symbols and definitions covering the following subjects: axis systems, vehicle bodies, suspension and steering systems, brakes, tires and wheels, operating states and modes, control and disturbance inputs, vehicle responses, and vehicle characterizing descriptors. The scope does not include terms relating to the human perception of vehicle response.
CURRENT
2015-12-19
Standard
AS6163
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).
2015-12-17
WIP Standard
AS6171/17
This document defines capabilities and limitations of LSM and CLSM as they pertain to suspect/counterfeit EEE part detection. Additionally, this document outlines requirements associated with the application of LSM and CLSM including: operator training, sample preparation, various imaging techniques, data interpretation, calibration, and reporting of test results. This test method is primarily directed to analyses performed in the visible to near infrared range (approximately 400nm to 1100nm). The Test Laboratory shall be accredited to ISO/IEC 17025 to perform the LSM and CLSM Test Methods as defined in this standard. The Test Laboratory shall indicate in the ISO/IEC 17025 Scope statement, the specific method being accredited to: Option 1: All AS6171/17 Test Methods, or Option 2: All AS6171/17 Test Methods except CLSM. If SAE AS6171/17 is invoked in the contract, the base document, AS6171 General Requirements shall also apply.
CURRENT
2015-12-17
Standard
J1698/3_201512
This SAE Recommended Practice defines procedures intended to be used to validate that relevant EDR output records conform within specified limits to measured sensor input to the device.
CURRENT
2015-12-03
Standard
J3077_201512
This document provides a summary of the activities to-date of Task Force #1 - Research Foundations – of the SAE’s Driver Vehicle Interface (DVI) committee. More specifically, it establishes working definitions of key DVI concepts, as well as an extensive list of data sources relevant to DVI design and the larger topic of driver distraction.
2015-11-25
WIP Standard
J3115
This document aims to establish best practices in equipment setup and measurement of brake rotor disk thickness variation (DTV) on vehicle.
CURRENT
2015-11-24
Standard
J830_201511
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 NOTE: When the word fuel is used in the terms listed it may be omitted providing there can be no misunderstanding.
CURRENT
2015-11-24
Standard
J1949_201511
This SAE Standard specifies the dimensional requirements for the assembly of high-pressure pipe connections for compression-ignition (diesel) engine fuel injection equipment. It applies to 60 deg female cones with external threaded connectors types 1 and 2, and to the internal threaded tube nuts and male cone type end assembly of high- pressure pipe connections for tubes with diameters up to 12 mm inclusive.
2015-10-21
WIP Standard
GEIASTD0007C
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.
Viewing 241 to 270 of 1276