Search
Advanced Search
of the following are true
(
)

Results

Items (211,955)
This Recommended Practice defines the technical requirements for a terrestrial-based PNT system to improve vehicle (e.g., unmanned, aerial, ground, maritime) positioning/navigation solutions and ensure critical infrastructure security, complementing GNSS technologies.
PNT Position, Navigation, and Timing
This recommended practice describes a process for testing the comprehension of static (i.e., fixed or non-dynamic) symbols for all ground vehicles, for both OEM and aftermarket products. With advancing display technology, it is now possible to display dynamic symbols (e.g., a spinning beach ball to show that a process is ongoing, or a diagram showing energy distribution in hybrid vehicles). Such graphics are outside of the scope of this recommended practice, though extensions of this process may be useful for testing them. However, several symbols which occupy the same space on a display may change state without movement (e.g. play/pause button); these are within the scope of this recommended practice. The process described in this recommended practice includes criteria that are used to identify how well the perceived meaning matches the intended meaning for a representative sample of drivers. The data from this process are analyzed to determine the drivers’ comprehension of the symbol
Driver Vehicle Interface (DVI) Committee
This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).
V2X Core Technical Committee
This document, the JAUS Compliance and Interoperability Policy (ARP6012), recommends an approach to documenting the complete interface of an unmanned system or component in regard to the application of the standard set. While non-SAE AS-4 JAUS documents are referenced in this ARP they are not within the scope of this document and should be viewed as examples only.
AS-4JAUS Joint Architecture for Unmanned Systems Committee
This document establishes recommended practices for the specification of general performance, design, test, development, and quality assurance requirements for the flight control related functions of the Vehicle Management Systems (VMS) of military Unmanned Aircraft (UA), the airborne element of Unmanned Aircraft Systems (UAS), as defined by ASTM F 2395-07. The document is written for military unmanned aircraft intended for use primarily in military operational areas. The document also provides a foundation for considerations applicable to safe flight in all classes of airspace.
A-6A3 Flight Control and Vehicle Management Systems Cmt
This document provides a list of data elements and event triggers for recording of event data relevant to crash investigations for heavy vehicles. The list of data elements includes recommended source(s) and formatting.
Truck and Bus Event Data Recorder Committee
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. Applicability to right-hand drive vehicles and roadway infrastructure would require adjustment to such vehicles and
On-Road Automated Driving (ORAD) Committee
The lane departure warning (LDW) system is a warning system that alerts drivers if they are drifting (or have drifted) out of their lane or from the roadway. This warning system is designed to reduce the likelihood of crashes resulting from unintentional lane departures (e.g., run-off-road, side collisions, etc.). This system will not take control of the vehicle; it will only let the driver know that he/she needs to steer back into the lane. An LDW is not a lane-change monitor, which addresses intentional lane changes, or a blind spot monitoring system, which warns of other vehicles in adjacent lanes. This informational report applies to original equipment manufacturer and aftermarket LDW systems for light-duty vehicles (gross vehicle weight rating of no more than 8500 pounds) on relatively straight roads with a radius of curvature of 500 m or more and under good weather conditions.
Advanced Driver Assistance Systems (ADAS) Committee
This SAE Recommended Practice applies to both Original Equipment Manufacturer (OEM) and aftermarket ITS message-generating systems for passenger vehicles and heavy trucks. The recommended practice describes the method for prioritizing ITS in-vehicle messages and/or displayed information based on a defined set of criteria. Each criterion has a fixed number of levels that are used to rate/rank a given message or information item to determine its prioritization value. The prioritization value is used to determine the priority in which simultaneous, or overlapping, in-vehicle messages are presented to the driver.
Driver Vehicle Interface (DVI) Committee
This SAE Aerospace Recommended Practice (ARP) provides guidance to prepare pilots to participate in simultaneous instrument landing system (ILS) precision runway monitor (PRM) approaches to closely-spaced parallel runways.
G-10G Realistic Training Committee
This Aerospace Information Report (AIR) provides information on systems integration rigs, commonly referred to as “Iron Birds” for aerospace applications. a It includes background historical information including descriptions of Iron Birds produced to date, important component elements and selection rationale, hydraulic system design and operational modes and illustrates the design approaches to be considered. b It provides illustrations of the various systems that should be considered for Iron Bird testing in the development phase and utilization during the production program. c It includes recommendations for simulation, component development tests, system integration and lessons learned.
A-6A3 Flight Control and Vehicle Management Systems Cmt
Items per page:
1 – 50 of 211955