Search Results

This SAE Standard provides performance and general design requirements and related test procedures for a combination tail and floodlamp for use on industrial wheeled equipment that may be operated on public roads.

This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.

This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.

ARINC 800 is the first industry standard intended for characterization of aviation-grade high-speed (Gbps) Ethernet links. The test methods are based on realistic representation of cabin networks. The notional cabling architecture is based on IFE seat distribution using multiple intermediate disconnects. Sequential testing is supported by building up number of connectors in the link. Test guidelines for mixed intermediate cable lengths are provided.

This document defines a secure Wi-Fi distribution network installed in the aircraft passenger cabin for passenger and crew use. Carry-on Portable Electronic Devices (PEDs) such as smart phones, tablets, and laptops may use this network to access public internet services provided on the aircraft.

This report defines the requirements and recommended practices for production testing of aircraft passenger seats and seat groups. Production testing is performed at the seat manufacturers' facilities prior to the shipment of the seats to the airframe manufacturers, Maintenance, Repair, and Overhaul (MRO), or airlines/operators for installation in the aircraft. Using this guidance, rework is minimized and schedules remain minimally affected.

ARINC 661 defines logical interfaces to Cockpit Display Systems (CDS) used in all types of aircraft installations. The CDS provides graphical and interactive services to user applications within the flight deck environment. When combined with data from user applications, it displays graphical images to the flight deck crew. The document emphasizes the need for independence between aircraft systems and the CDS. This document defines the interface between the avionics equipment and display system graphics generators. This document does not specify the "look and feel" of any graphical information, and as such does not address human factors issues. These are defined by the airline flight operations community. Supplement 7 adds the definition of: Selector Widget, Tree Widget, New FormatString options, Readouts available in MapItems, Provisions for Touch Screen Displays.

This document establishes techniques for validating that a mission store complies with the interface requirements contained in MIL-STD-1760 Revision D.

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.

Create a method/procedure to measure build up and concentration of CO2 in the passenger compartment.

• Define sub-roles within the primary J3016 roles • Define different human capabilities and list what those are (including definition of “capability”) • Frame issues • Document open questions

This SAE Recommended Practice applies to both Original Equipment Manufacturer (OEM) and aftermarket message-generating systems for light and heavy vehicles. The recommended practice covers both message prioritization and presentation (including simultaneous display of messages) for visual and auditory modalities. In addition, this recommended practice will consider temporal aspects of external events (e.g. merging into heavy traffic, time-to-collision) and their impact on temporal presentation and format (including multi-modal) of messages.

This SAE Standard applies to equipment to be used to recovery R-152a refrigerant only. Refrigerant recovery equipment is required to ensure adequate refrigerant recovery to reduce emissions and provide safe and accurate service of the AC system. Equipment shall be certified to meet all performance requirements outlined in this document.

This SAE standard applies to refrigerant identification equipment to be used for identifying an acceptable level of R-152a purity in a refrigerant tank or vehicle MAC system labeled as containing R-152a, and not misidentify other refrigerants.

This SAE Standard applies to equipment to be used with R-152a refrigerant only. It establishes requirements for equipment used to recharge R-152a to an industry accepted accuracy level and purity levels defined in SAE J2099. Refrigerant service equipment is required to ensure adequate refrigerant recovery to reduce emissions and provide for accurate recharging of mobile air conditioning systems. Equipment shall be certified to meet all performance requirements outlined in this document and international/regional construction and safety requirements as outlined in this document.

This SAE Standard provides testing and functional requirements to meet specified minimum performance criteria for electronic probe-type leak detectors suitable for use with R-152a, an A2 flammable refrigerant. The equipment specified here will identify smaller refrigerant leaks when servicing motor vehicle air conditioning systems, including those engineered with improved sealing and smaller refrigerant charges to address environmental concerns and increase system efficiency.

This SAE Aerospace Recommended Practice (ARP) provides guidance to develop and assure validation and verification of IVHM systems used in autonomous aircraft, vehicles and driver assistance functions. IVHM covers a vehicle, monitoring and data processing functions inherent within its sub-systems, and the tools and processes used to manage and restore the vehicle’s health. The scope of this document is to address challenges and identify recommendations for the application of integrated vehicle health management (IVHM) specifically to intelligent systems performing tasks autonomously within the mobility sector. This document will focus on the core aspects of IVHM for autonomous vehicles that are common to both aerospace and automotive applications. It is anticipated that additional documents will be developed separately to cover aspects of this functionality that are unique to each application domain.