Search
Advanced Search
of the following are true
(
)

Results

Items (211,955)
This SAE Aerospace Standard (AS) specifies minimum performance standards for Electronic Flight Information System (EFIS) displays that are head-down and intended for use in the flight deck by the flight crew in all 14 CFR Part 23, 25, 27, and 29 aircraft. This document is expected to be used by multiple regulatory agencies as the basic requirement for a technical standard order for EFIS displays. The requirements and recommendations in this document are intended to apply to, but are not limited to, the following types of display functions: Primary Flight and Primary Navigation displays, including vertical situation and horizontal situation functions. Displays that provide flight crew alerts, which may include engine instrument, aircraft systems information/control. Control displays including communication, navigation and system control displays. Information displays, which may include navigation displays used for situation awareness only, supplemental data, and maintenance and
A-4EFIS Electronic Flight Instrument System Display
This specification applies to a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services for all seven protocol layers. In the layer 7 specification, it includes a description of the types of messages used by applications to exchange application and network management data.
AS-3 Fiber Optics and Applied Photonics Committee
This SAE Aerospace Information Report (AIR) discusses characteristics of data communications for the Joint Architecture for Unmanned Systems (JAUS). This document provides guidance on the aspects of transport media, unmanned systems and the characteristics of JAUS itself that are relevant to the definition of a JAUS transport specification.
AS-4JAUS Joint Architecture for Unmanned Systems Committee
This document defines a set of standard application layer interfaces called JAUS Unmanned Ground Vehicle Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Unmanned Ground Vehicle Services represent the platform-specific capabilities commonly found in UGVs, and augment the Mobilty Service Set [AS6009] which is platform-agnostic. At present ten (10) services are defined in this document. These services are categorized as:
AS-4JAUS Joint Architecture for Unmanned Systems Committee
This document is intended for the application of color to cathode-ray-tube (CRT) displays, liquid crystal displays (LCD) and other types of display technologies such as projection displays. Emerging color display technologies other than those noted above, may not be adequately covered by these recommendations. Color recommendations will not address Night Vision Devices (NVD), Head-Up Displays (HUD) or Head or Helmet Mounted Displays (HMD). This document is applicable to aircraft as understood in 14 CFR Parts 23, Part 25, Part 27 and Part 29, and EASA CS-23, CS-25. CS-27 and CS-29 certification standards.
G-10D Color Display Committee
This standard is for use by organizations that procure and integrate EEE parts. These organizations may provide EEE parts that are not integrated into assemblies (e.g., spares and/or repair EEE parts). Examples of such organizations include, but are not limited to: original equipment manufacturers; contract assembly manufacturers; maintenance, repair, and overhaul organizations; value-added resellers; and suppliers that provide EEE parts or assemblies as part of a service. The requirements of this standard are generic. These requirements are intended to be applied (or flowed down as applicable) through the supply chain to all organizations that procure EEE parts and/or systems, subsystems, or assemblies, regardless of type, size, and product provided. The mitigation of counterfeit EEE parts in this standard is risk-based and these mitigation steps will vary depending on the criticality of the application, desired performance and reliability of the equipment/hardware. The requirements
G-19 Counterfeit Electronic Parts Committee
Scope is unavailable.
E-25 General Standards for Aerospace and Propulsion Systems
SCOPE IS UNAVAILABLE.
E-25 General Standards for Aerospace and Propulsion Systems
This SAE Recommended Practice establishes a test procedure for the evaluation of lane departure warning (LDW), lane keeping assistance (LKA), and lane centering assistance systems used in passenger vehicles and light trucks. This test procedure does not intend to exclude any particular system or sensing technology. The recommended practice can be used to test the functionality and performance of LDW, LKA, and lane centering assistance systems by assessing their ability to (1) warn (LDW) or control (LKA, lane centering assistance) in response to an unintended lane departure, and (2) the ability to indicate a system disengagement. The human machine interface (HMI) is not addressed herein but is considered in SAE J2808. The recommended practice specifies lane markers to enable lane departure testing, or road edges, to enable testing of road departure mitigation systems. The document is separated into two tiers. Tier One establishes a recommended minimum set of performance criteria for LDW
Active Safety Systems Standards Committee
This document reviews current aerospace software, hardware, and system development standards used in the certification/approval process of safety-critical airborne and ground-based systems, and assesses whether these standards are compatible with a typical Artificial Intelligence (AI) and Machine Learning (ML) development approach. The document then outlines what is required to produce a standard that provides the necessary accommodation to support integration of ML-enabled sub-systems into safety-critical airborne and ground-based systems, and details next steps in the production of such a standard.
G-34 Artificial Intelligence in Aviation
This report provides the process for developing a flexible test framework to support the creation of system-level cooperative driving automation (CDA) Feature test procedures, which are intended to be objective, repeatable, and transparent, and enable collaborative testing of the Feature. Utilizing a Feature’s functional and logical scenario details, it provides the building blocks necessary to develop cooperative automated driving system (C-ADS)-equipped vehicle (C-ADS-V) and CDA infrastructure (CDA-I) system diagrams, identify the interfaces to and from the systems, and identify the set of functional test support components specific to the CDA Feature. Utilizing these details, along with the Feature-specific concrete scenarios, a method for developing a test scope and system level use-case-focused test procedures is provided.
Cooperative Driving Automation(CDA) Committee
This document addresses the operational safety and human factors aspects of unauthorized laser illumination events in navigable airspace. The topics addressed include operational procedures, training, and protocols that flight crew members should follow in the event of a laser exposure. Of particular emphasis, this document outlines coping strategies for use during critical phases of flight. Although lasers are capable of causing retinal damage, most laser cockpit illuminations, to date, has been relatively low in irradiance causing primarily startle reactions, visual glare, flashblindness and afterimages. Permanent eye injuries from unauthorized laser exposures have been extremely rare. This document describes pilot operational procedures in response to the visual disruptions associated with low to moderate laser exposures that pilots are most likely to encounter during flight operations. With education and training, pilots can take actions that safeguard both their vision and the
G-10OL Operational Laser Committee
Forward Collision Warning (FCW) systems are onboard systems intended to provide alerts to assist drivers in avoiding striking the rear end of another moving or stationary motorized vehicle. This SAE Information Report describes elements for a FCW operator interface, as well as requirements and test methods for systems capable of warning drivers of rear-end collisions. This information report applies to original equipment and aftermarket FCW systems for passenger vehicles including cars, light trucks, and vans. This report does not apply to heavy trucks. Furthermore, this document does not address integration issues associated with adaptive cruise control (ACC), and consequently, aspects of the document could be inappropriate for an ACC system integrated with a FCW system.
Advanced Driver Assistance Systems (ADAS) Committee
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.
Driver Vehicle Interface (DVI) Committee
This standard defines the mechanical interface and specifies provisions for the electrical and environmental connectors between the host aircraft (“platform”) and a turreted electro-optic/infrared (EO/IR) sensor.
AS-1C Avionic Subsystems Committee
Following a number of high-visibility collisions between aircraft on the airport surface, overall taxi operations have been brought under greater scrutiny. In addition, observation of taxi operations and the results of associated research programs have revealed that the efficiency of taxi operations could be significantly improved with available technologies and by applying a human centered design approach. Surface operations displays have been tested in prototype form and a number of manufacturers are moving toward product definition. This document provides guidance on the design of elements, which may be part of surface operations displays whose objectives would be to enhance safety and to improve overall efficiency of aircraft operations on the airport surface. Such efficiency increases should be realized not only in day-to-day operations, but should also be manifested in training for surface operations. This document sets forth functional and design recommendations concerning the
G-10EAB Executive Advisory Group
This document specifies the minimum recommendations for Blind Spot Monitoring System (BSMS) operational characteristics and elements of the user interface. A visual BSMS indicator is recommended. BSMS detects and conveys to the driver via a visual indicator the presence of a target (e.g., a vehicle), adjacent to the subject vehicle in the “traditional” Adjacent Blind Spot Zone (ABSZ). The BSMS is not intended to replace the need for interior and exterior rear-view mirrors or to reduce mirror size. BSMS is only intended as a supplement to these mirrors and will not take any automatic vehicle control action to prevent possible collisions. While the BSMS will assist drivers in detecting the presence of vehicles in their ABSZ, the absence of a visual indicator will not guarantee that the driver can safely make a lane change maneuver (e.g., vehicles may be approaching rapidly outside the ABSZ area). This document applies to original equipment and aftermarket BSMS systems for passenger
Advanced Driver Assistance Systems (ADAS) Committee
Create and publish a list of terms relevant to electrified propulsion aircraft with summary text descriptions. The terms and descriptions will not provide full explanations, diagrams, and other detailed technical descriptions. These deeper descriptions will be addressed in other documents. This document defines the relevant terms and abbreviations related to the design, development, and use of electrified propulsion in aircraft. This definition is provided to enable a consistent use of technical language throughout the standards developed by the E-40 committee.
E-40 Electrified Propulsion Committee
This document covers the recommended lighting performance and design criteria for: a Left Forward Navigation Position Lights (Red) b Right Forward Navigation Position Lights (Green) c Rear Navigation Position Lights (White) d Anticollision Lights (1) Red Flashing Lights Top and Bottom Fuselage (2) White Flashing Strobe Lights Wing Tips and/or Tail (3) Red Flashing Beacon Light on Top of Vertical Tail
A-20B Exterior Lighting Committee
This document provides preliminary1 safety-relevant guidance for in-vehicle fallback test driver training and for on-road testing of vehicles being operated by prototype conditional, high, and full (Levels 3 to 5) ADS, as defined by SAE J3016. It does not include guidance for evaluating the performance of post-production ADS-equipped vehicles. Moreover, this guidance only addresses testing of ADS-operated vehicles as overseen by in-vehicle fallback test drivers (IFTD). These guidelines do not address: Remote driving, including remote fallback test driving of prototype ADS-operated test vehicles in driverless operation. (Note: The term “remote fallback test driver” is included as a defined term herein and is intended to be addressed in a future iteration of this document. However, at this time, too little is published or known about this type of testing to provide even preliminary guidance.) Testing of driver support features (i.e., Levels 1 and 2), which rely on a human driver to
On-Road Automated Driving (ORAD) Committee
This Aerospace Recommended Practice (ARP) provides guidance on developing requirements for systems that include Integrated Vehicle Health Management (IVHM) capability [REF1], [REF18]. IVHM is increasingly being implemented on military and commercial aircraft. Some examples include the F-35 Joint Strike Fighter (JSF) [REF1] and the AH-64 Apache [REF3] in the military domain, and the B787 [REF4] and A350XWB [REF5] in the commercial domain. This document provides a systematic approach for developing requirements related to the IVHM capabilities of a vehicle system. This document is not intended to repeat general guidelines on good requirements writing [REF13], [REF20]. Instead, the focus is on the unique elements, which need to be considered for IVHM and the resulting specific guidelines that will help define better requirements and hence better systems. The multi-faceted nature of IVHM should include the process of requirements gathering. Therefore, this document presents some guidance
HM-1 Integrated Vehicle Health Management Committee
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