Results
The purpose of this document is to provide guidance for the implementation of DVI for momentary intervention-type LKA systems, as defined by ISO 11270. LKA systems provide driver support for safe lane keeping operations via momentary interventions. LKA systems are SAE Level 0, according to SAE J3016. LKA systems do not automate any part of the dynamic driving task (DDT) on a sustained basis and are not classified as an integral component of a partial or conditional driving automation system per SAE J3016. The design intent (i.e., purpose) of an LKA system is to address crash scenarios resulting from inadvertent lane or road departures. Drivers can override an LKA system intervention at any time. LKA systems do not guarantee prevention of lane drifts or related crashes. Road and driving environment (e.g., lane line delineation, inclement weather, road curvature, road surface, etc.) as well as vehicle factors (e.g., speed, lateral acceleration, equipment condition, etc.) may affect the
This SAE Recommended Practice (RP) establishes uniform powered vehicle-level test procedure for forward collision warning (FCW) and automatic emergency braking (AEB) used in trucks and buses greater than 10000 pounds (4535 kg) GVWR equipped with pneumatic brake systems for detecting, warning, and avoiding potential collisions. This RP does not apply to electric powered vehicles, trailers, dollies, etc., and does not intend to exclude any particular system or sensor technology. These FCW/AEB systems utilize various methodologies to identify, track, and communicate data/information to the operator and vehicle systems to warn, intervene, and/or mitigate in the momentary longitudinal control of the vehicle. This specification will test the functionality of the FCW/AEB (e.g., ability to detect objects in front of the vehicle), its ability to indicate FCW/AEB engagement and disengagement, the ability of the FCW/AEB to notify the human machine interface (HMI) or vehicle control system that an
This SAE Aerospace Information Report (AIR) discusses past and present approaches for monitoring the landing gear structure and shock absorber (servicing), opportunities for corrosion detection, methods for transient overload detection, techniques for measuring the forces seen by the landing gear structure, and methods for determining the fatigue state of the landing gear structure. Landing gear tire condition and tire pressure monitoring are detailed in ARP6225, AIR4830, and ARP6137, respectively. Aircraft Brake Temperature Monitoring Systems (BTMS) are detailed in AS1145.
This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural Model and how to use this model within the EA modeling tool environment. The purpose of the EA version of the UCS Architectural Interface Control Document (ICD) model is to provide a working model for Enterprise Architect tool users and to serve as the source model for the Rational Software Architect (RSA) and Rhapsody models (AIR6516 and AIR6517). The AIR6515 EA Model has been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service, and Non-Functional Properties Models
This SAE Information Report provides a compendium of terms, definitions, abbreviations, and acronyms to enable common terminology for use in engineering reports, diagnostic tools, and publications related to active safety systems. This information report is a survey of active safety systems and related terms. The definitions offered are descriptions of functionality rather than technical specifications. Included are warning and momentary intervention systems, which do not automate any part of the dynamic driving task (DDT) on a sustained basis (SAE Level 0 as defined in SAE J3016), as well as definitions of select features that perform part of the DDT on a sustained basis (SAE Level 1 and 2).
This brief User Guide recaps the content of the AS6518B UCS Architectural Model. The purpose of the UCS Architecture Model is to provide the authoritative source for other models and products within the UCS Architecture as shown in the AS6512B UCS Architecture: Architecture Description.
The primary focus of this document is to provide information on the impacts hard landings and abnormal load conditions on landing gear and related systems. However, because hard landings potentially affect the entire aircraft, this document also includes information for non-landing gear areas. The document may be considered to be applicable to all types of aircraft. This document does NOT provide recommended practices for hard landing inspections, nor does it provide recommendations on the disposition of damaged equipment. Refer to ARP4915 and ARP5600 for information on dispositions relating to landing gear components or wheels involved in accidents/incidents.
This Recommended Practice, Operational Definitions of Driving Performance Measures and Statistics, provides functional definitions of and guidance for performance measures and statistics concerned with driving on roadways. As a consequence, measurements and statistics will be calculated and reported in a consistent manner in SAE and ISO standards, journal articles proceedings papers, technical reports, and presentations so that the procedures and results can be more readily compared. Only measures and statistics pertaining to driver/vehicle responses that affect the lateral and longitudinal positioning of a road vehicle are currently provided in this document. Measures and statistics covering other aspects of driving performance may be included in future editions. For eye glance-related measures and statistics, see SAE J2396 (Society of Automotive Engineers, 2007) and ISO 15007-1 (International Standards Organization, 2002).
This Aeronautical Standard covers Automatic Pilots intended for use on aircraft to automatically operate the aerodynamic controls to maintain flight and/or to provide maneuvering about the three axes through servo control.
The scope of this SAE Aerospace Information Report (AIR) is to discuss factors affecting visibility of aircraft navigation and anticollision lights, enabling those concerned with their use to have a better technical understanding of such factors, and to aid in exercising appropriate judgment in the many possible flight eventualities.
The purpose of this SAE Aerospace Information Report (AIR) is two-fold: to inform the reader of the extent of effort that went into the development of the Joint Architecture for Unmanned Systems (JAUS); and to capture for posterity the domain analysis that provides the underpinnings for the work by the AS-4 Committee (Unmanned Systems).
This specification established (1) the common requirements for hydraulic units capable of functioning as starters and as pumps suitable for use in aircraft and missiles and (2) the methods to be used for demonstrating compliance with these requirements.
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 Technical Governance is part of the SAE UCS Architecture Library and is primarily concerned with the UCS Architecture Model (AS6518) starting at Revision A and its user extensions. Users of the Model may extend it in accordance with AS6513 to meet the needs of their UCS Products. UCS Products include software components, software configurations and systems that provide or consume UCS services. For further information, refer to AS6513 Revision A or later. Technical Governance is part of the UCS Architecture Framework. This framework governs the UCS views expressed as Packages and Diagrams in the UCS Architecture Model.
This SAE Recommended Practice presents a method and example results for determining the Automotive Safety Integrity Level (ASIL) for automotive motion control electrical and/or electronic (E/E) systems. The ASIL determination activity is required by ISO 26262-3, and it is intended that the process and results herein are consistent with ISO 26262. The technical focus of this document is on vehicle motion control systems. The scope of this SAE Recommended Practice is limited to collision-related hazards associated with motion control systems. This SAE Recommended Practice focuses on motion control systems since the hazards they can create generally have higher ASIL ratings, as compared to the hazards non-motion control systems can create. Because of this, the Functional Safety Committee decided to give motion control systems a higher priority and focus exclusively on them in this SAE Recommended Practice. ISO 26262 has a wider scope than SAE J2980, covering other functions and accidents
This SAE Aerospace Recommended Practice (ARP) sets forth design and operational recommendations concerning the human factors/crew interface considerations and criteria for vertical situation awareness displays. This is the first of two recommended practice documents that will address vertical situation awareness displays (VSAD). This document will focus on the performance/planning types of display (e.g., the map display) and will be limited to providing recommendations concerning human factored crew interfaces and will not address architecture issues. This document focuses on two types of VSAD displays: a coplanar implementation of a profile display (side projection) and a conventional horizontal map display; and a 3D map display (geometric projection). It is intended for head down display applications. However, other formats or presentation methods, such as HUDs, HMDs and 3D audio presentations may become more feasible in the future. Even though the relationship of the vertical
This SAE Aerospace Information Report (AIR) describes the Architecture Framework for Unmanned Systems (AFUS). AFUS comprises a Conceptual View, a Capabilities View, and an Interoperability View. The Conceptual View provides definitions and background for key terms and concepts used in the unmanned systems domain. The Capabilities View uses terms and concepts from the Conceptual View to describe capabilities of unmanned systems and of other entities in the unmanned systems domain. The Interoperability View provides guidance on how to design and develop systems in a way that supports interoperability.
This document describes a manufacturing method for processing unidirectional carbon fiber/epoxy resin impregnated sheet and tape into multi-ply broadgoods and tape produced on an automated cross-plying machine. Broadgoods or tape of two or more ply configurations may be processed, where ply orientations of 0°, 45°, 90°, and 135° (as examples) may be automatically layed in a programmed sequence. In all configurations, the 0° ply direction is parallel to the length of the broadgoods roll or sheet, or tape.
The terms and definitions in this document describe the functions performed within an ADS, as defined in SAE J3016. Where possible we have attempted to capture the language that is already in use within the automated driving development community. Where needed, we have added new terms and definitions, including clarifying notes to avoid ambiguity. SAE J3131 deals primarily with Level 4 and Level 5 ADS features.
The purpose of this SAE Recommended Practice is to offer simplified and prioritized guidelines for collecting and preserving on-scene data related to motor vehicle crashes. It is intended that these guidelines improve the effectiveness of data collection, which will assist subsequent analysis and reconstruction of a particular crash. This document is intended to guide early data collectors whose objectives include documenting information related to the crash. It may be used by law enforcement personnel, safety officials, insurance adjusters and other interested parties. This document identifies categories of scene physical features that deteriorate relatively quickly and recommends documentation task priorities. Detailed methods of collecting data are not part of this document. However, some widely used methods are described in the references in Section 2.
This information report is applicable to the reliability characteristics of unmanned ground vehicles.
This document defines a set of standard application layer interfaces called JAUS Mobility 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 Mobility Services represent the vehicle platform-independent capabilities commonly found across all domains and types of unmanned systems (referred to as UxVs). At present, over 15 services are defined in this document many of which were updated in this revision to support Unmanned Underwater Vehicles (UUVs). Some examples include: Pose Sensors: Determine the instantaneous position and orientation of a platform in global or local coordinates Velocity State Sensor: Determines the instantaneous velocity of a platform Acceleration State Sensor: Determines the instantaneous acceleration of a platform Primitive Driver: Performs basic mobility for a platform based on force/torque efforts Vector Drivers: Perform closed loop mobility for
This document applies to laser proponents involved with the use of laser systems outdoors. It may be used in conjunction with AS4970, ARP5535, and ARP5572 and the ANSI Z136 series of laser safety standards.
This is a guide intended to aid the user in the proper selection and application of rivets as a fastening means. It consists of general information on the advantages of riveting, various methods of riveting, selection of rivets and design considerations.
This document sets forth design and operational recommendations concerning the human factors issues and criteria for airborne collision and avoidance systems. The visual and aural characteristics are covered for the display of traffic information as well as the escape maneuver display on conventional and electronic flight decks. System utilization philosophy and flight deck integration considerations are also presented.
This standard defines the data interfaces between a host aircraft (“platform”) and an Electro-Optic/Infrared (EO/IR) sensor. These data interfaces cover various types of data including: imagery, metadata, command, status, and responses (CSR), geospatial postion, time, test and maintenance, and hand-controller. This standard does not cover mechanical or electrical interfaces.
Items per page:
50
1 – 50 of 211948