Search Results

The design and location of rear-viewing mirrors or systems, and the presentation of the rear view to the driver can best be achieved if the designer and the engineer have adequate references available on the physiological functions of head and eye movements and on the perceptual capabilities of the human visual system. The following information and charts are provided for this purpose. For more complete information of the relationship of vision to forward vision, see SAE SP-279.

This standard provides the guideline for enhancements to adaptive cruise control (ACC) by the addition of wireless communication from relevant vehicles (V2V) and/or the infrastructure (I2V) to augment the ACC active sensing capability. The CACC system operates under driver responsibility and supervision and is limited to the following: Does only longitudinal control of the vehicle. Uses time gap control strategy similar to ACC. Motor vehicles covered in the scope of this document include light and heavy vehicles. The message elements to realize CACC and platooning are part of the scope. The initial release covers definitions for CACC and platooning and requirements for CACC, while a subsequent release will cover the platooning requirements.

This document provides a high-level ontology and lexicon for describing on-road ADS-operated vehicle behavioral competencies and driving maneuvers that comprise routine/normal performance of the complete DDT, as defined in SAE J3016. It provides definitions of behavior, maneuver, scenario, and scene. This initial high-level lexicon and ontology are developed for ADS driving behaviors, including considerations for hierarchy of behaviors, and relationships among maneuvers, operational design domain (ODD) elements, and object and event detection and response (OEDR). Considerations for describing scenarios using this lexicon and ontology are discussed. This document describes ADS-operated vehicle motion control maneuvers during routine/normal operation. Maneuvers of other road users are not evaluated. This document assumes left-hand drive vehicles and road infrastructure.

This document describes a systematic and rigorous process to: (1) identify and evaluate standard names and definitions for driving automation system features, and (2) identify a “user vocabulary” of terms and descriptions that [human] drivers use to describe driving automation system features. The process described in this document includes selection criteria and trade-offs that can be used to select an approach to testing that matches the constraints and objective of a particular evaluation. The data from this process are analyzed to determine users’ name preferences for driving automation system features and what they would expect a specific feature to do, based on the name given to the features. The data generated by this naming methodology can provide guidance regarding the names that may support accurate understanding of the feature’s capabilities and limitations.

These general guidelines and precautions apply to personnel operating directional drilling tracking equipment when used with Horizontal Earthboring Machines as defined in SAE J2022.

This document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities. The cooperation supports or enables performance of the dynamic driving task (DDT) for a subject vehicle with driving automation feature(s) engaged. Other participants may include other vehicles with driving automation feature(s) engaged, shared road users (e.g., drivers of manually operated vehicles or pedestrians or cyclists carrying personal devices), or road operators (e.g., those who maintain or operate traffic signals or workzones). Cooperative driving automation (CDA) aims to improve the safety and flow of traffic and/or facilitate road operations by supporting the movement of multiple vehicles in proximity to one another. This is accomplished, for example, by sharing information that can be used to influence (directly or indirectly) DDT performance by one or more nearby road users.

This SAE Information Report classifies and defines a harmonized set of safety principles intended to be considered by ADS and ADS-equipped vehicle development stakeholders. The set of safety principles herein is based on the collection and analysis of existing information from multiple entities, reflecting the content and spirit of their efforts, including: SAE ITC AVSC Best Practices CAMP Automated Vehicle Research for Enhanced Safety - Final Report RAND Report - Measuring Automated Vehicle Safety: Forging a Framework U.S. DOT: Automated Driving Systems 2.0 - A Vision for Safety Safety First for Automated Driving (SaFAD) UNECE WP29 amendment proposal UNECE/TRANS/WP.29/GRVA/2019/13 On a Formal Model of Safe and Scalable Self-Driving Cars (Intel RSS model) SAE J3018 This SAE Information Report provides guidance for the consideration and application of the safety principles for the development and deployment of ADS and ADS-equipped vehicles.

This document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities. The cooperation supports or enables performance of the dynamic driving task (DDT) for a subject vehicle with driving automation feature(s) engaged. Other participants may include other vehicles with driving automation feature(s) engaged, shared road users (e.g., drivers of manually operated vehicles or pedestrians or cyclists carrying personal devices), or road operators (e.g., those who maintain or operate traffic signals or workzones). Cooperative driving automation (CDA) aims to improve the safety and flow of traffic and/or facilitate road operations by supporting the movement of multiple vehicles in proximity to one another. This is accomplished, for example, by sharing information that can be used to influence (directly or indirectly) DDT performance by one or more nearby road users.

This SAE Standard provides a table of textual messages meeting the requirements for expressing “Radio Data Systems” (RDS) phrases commonly used in the ITS industry. They can be used both over the RDS subcarrier transmission media as part of a 37-bit long “Group 8a message” as well as being used to provide a common content list of phrases used in a wide number of other media and applications. This document SHALL define the normative index values to be used, extending the CEN established list to provide phrases needed by US practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This document SHALL follow the formats and rules established in SAE J2540 in the expressions, manipulations, and use of such tables. It should be pointed out that within the rules established by this document a variety of final table are all considered “compliant” with the document, and may vary as fits the needs of implementers.

This SAE Information Report provides a comparative summary between the various messages found in the SAE ATIS standards work (notably SAE J2313, J2353, J2354, J2369 and J2374) and that found in the GATS standard (Global Automotive Telematics Standard). GATS is a message set meant to be deployed on mobile phone systems based on the GSM (Global System for Mobile Communication) phone system which is being deployed in European markets and which the SAE may need to harmonize with as part of the World Standards activities of TC204. This document provides an overview of the various types of supported messages and how they compare with US terms and messages. Some selected features of the GATS work are recommended for assimilation into the next revision of ATIS standards. No attempt at determining a U.S. policy in this regard is provided. This document seeks to provide the reader familiar with SAE ATIS with a high level overview of technical knowledge of the GATS approach in similar areas.

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a Methods and Data Elements for handling indexes and strings in ATIS applications and message sets b Message Sets to support the delivery and translations of tables used in such strings c Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.

This Aerospace Recommended Practice (ARP) provides criteria for operational characteristics to be considered in the design of individual, inflatable life preservers intended for air transport safety.

This document provides design guidelines, test procedure references, and performance requirements for omnidirectional and selective coverage optical warning devices used on authorized emergency, maintenance, and service vehicles. It is intended to apply to, but is not limited to, surface land vehicles.

This SAE Recommended Practice establishes a uniform, powered vehicle test procedure and minimum performance requirement for lane departure warning systems used in highway trucks and buses greater than 4546 kg (10000 pounds) GVW. Systems similar in function but different in scope and complexity, including Lane Keeping/Lane Assist and Merge Assist, are not included in this document. This document does not apply to trailers, dollies, etc. This document does not intend to exclude any particular system or sensor technology. The specification will test the functionality of the LDWS (e.g., ability to detect lane presence, and ability to detect an unintended lane departure), its ability to indicate LDWS engagement, its ability to indicate LDWS disengagement, and determine the point at which the LDWS notifies the Human Machine Interface (HMI) or vehicle control system that a lane departure event is detected.

This document defines requirements for digital, command/ response time division multiplexing (data bus) techniques for fiber optic implementation. The concept of operation and information flow on the multiplex data bus and the functional formats to be employed are also defined.

This SAE Recommended Practice applies to a decorative lamp(s) installed on the front of motor vehicles. This lamp(s) is intended only to be decorative and is not to impair the effectiveness of any required lighting device. This recommended practice establishes uniformity in use guidelines for the performance, installation, activation and switching of a front decorative lamp(s).

This SAE Recommended Practice defines key terms used in the description and analysis of video based driver eye glance behavior, as well as guidance in the analysis of that data. The information provided in this practiced is intended to provide consistency for terms, definitions, and analysis techniques. This practice is to be used in laboratory, driving simulator, and on-road evaluations of how people drive, with particular emphasis on evaluating Driver Vehicle Interfaces (DVIs; e.g., in-vehicle multimedia systems, controls and displays). In terms of how such data are reduced, this version only concerns manual video-based techniques. However, even in its current form, the practice should be useful for describing the performance of automated sensors (eye trackers) and automated reduction (computer vision).

The information contained in this document is based on line experience with current systems. It should be used as a basis for ongoing research and development including the human factors aspects of future flight management systems and their interaction with the ATC environment.

The design and location of rear-viewing mirrors or systems, and the presentation of the rear view to the driver can best be achieved if the designer and the engineer have adequate references available on the physiological functions of head and eye movements and on the perceptual capabilities of the human visual system. The following information and charts are provided for this purpose. For more complete information of the relationship of vision to forward vision, see SAE SP-279.

This SAE Recommended Practice specifies recommendations for rear view mirror systems to provide the operator with a clear view to the rear. It is intended as a supplement to the requirements for motorcycle mirrors given in 49 CFR 571.111.