Search Results

AS9131 - This standard defines the common nonconformance data definition and documentation that an internal or external supplier or sub-tier supplier must submit when informing a customer of a nonconformity. The requirements shall be are applicable for reporting a nonconforming product to the owner/operator (i.e., end item user), if specified by contract. Reporting of nonconformance data, either electronically or conventionally on paper, is subject to the terms and conditions of the contract. This also includes, where applicable, data access under export control regulations.

The purpose of this standard is to provide a source of definitions of terms and acronyms commonly used in the air transport maintenance community for test and evaluation with an emphasis on terms applicable to BITE.

The difficulty in locating crash sites has prompted international efforts for alternatives to quickly recover flight data. This document describes the technical requirements and architectural options for the Timely Recovery of Flight Data (TRFD) in commercial aircraft. ICAO and individual Civil Aviation Authorities (CAAs) levy these requirements. The ICAO Standards and Recommended Practices (SARPs) and CAA regulations cover both aircraft-level and on-ground systems. This report also documents additional system-level requirements derived from the evaluation of ICAO, CAA, and relevant industry documents and potential TRFD system architectures. It describes two TRFD architectures in the context of a common architectural framework and identifies requirements. This report also discusses implementation recommendations from an airplane-level perspective.

This document defines an open encoding format for obstacle databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Obstacle Databases (ObsDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

This document defines an open encoding format for terrain databases. This format, when designed and implemented, will enable a quick, economic, and efficient use of Terrain Databases (TerrDBs). However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.

Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969B) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.

Enhanced License for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Terms can be reviewed prior to purchase once item is added to the cart. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) This data dictionary provides a mathematically coherent set of definitions for quantity types used in data models for unmanned systems. In this data dictionary, a quantity is defined as a property of a phenomenon, substance, or body whose value has magnitude.

Enhanced License and UML Model for Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969) allowing for greater usage as outlined in the terms of the Enhanced License. Data Dictionary for Quantities Used in Cyber Physical Systems (AS6969A) This data dictionary provides definitions for quantities commonly used in the command and control of cyber physical systems. It defines mathematical and logical terms, quantities, measurement units, reference systems, measurands, and measurements. It also defines common quantity modalities. The dictionary is structured to be convenient to data modelers. It is also extendable so that users can create their own quantity domains.

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.

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.

This Aerospace Informational Report (AIR) provides guidance on using environmental, electrochemical, and electrical resistance measurements to monitor environment spectra and corrosivity of service environments, focusing on parameters of interest, existing measurement platforms, deployment requirements, and data processing techniques. The sensors and monitoring systems provide discrete time-based records of 1) environmental parameters such as temperature, humidity, and contaminants; 2) measures of alloy corrosion in the sensor; and 3) protective coating performance in the sensor. These systems provide measurements of environmental parameters, sensor material corrosion rate, and sensor coating condition for use in assessing the risk of atmospheric corrosion of the structure.

The SAE E-32 Committee is requested to develop standards for Commercial Aircraft Engine Monitoring to support the Continued Airworthiness of aircraft in general, with particular emphasis on the ETOPS (Extended Operations) to support the regulations. 14CFR A33.3 (c) ETOPS Requirements. For an applicant seeking eligibility for an engine to be installed on an airplane approved for ETOPS, the Instructions for Continued Airworthiness must include procedures for engine condition monitoring. The engine condition monitoring procedures must be able to determine prior to flight, whether an engine is capable of providing, within approved engine operating limits, maximum continuous power or thrust, bleed air, and power extraction required for a relevant engine inoperative diversion. For an engine to be installed on a two-engine airplane approved for ETOPS, the engine condition monitoring procedures must be validated before ETOPS eligibility is granted.

The ARP shall cover the objectives and activities of Verification & Vallidation Processes required to assure high quality and/or criticality level of an IVHM Systems and Software.

The processes outlined in this document cover the entire aircraft for both commercial and military applications. In addition to on-board systems, it covers on-ground elements as well. The practical application of this standardized process is detailed in the form of a checklist. As in all HM-1 documents, the scope of this document covers sensing and acquisition systems, typically on board, data transmission systems and processes, methods and hardware for data analysis, and finally, maintenance actions. The on-board aspects relating to safety of flight, pilot notification, etc., are addressed by the other SAE Committees standards and documents. To help explain the process and the use of the checklist, some high-level use cases related to maintenance credit applications are included.

AS9131 - This standard defines the common nonconformance data definition and documentation that an internal or external supplier or sub-tier supplier must submit when informing a customer of a nonconformity. The requirements shall be are applicable for reporting a nonconforming product to the owner/operator (i.e., end item user), if specified by contract. Reporting of nonconformance data, either electronically or conventionally on paper, is subject to the terms and conditions of the contract. This also includes, where applicable, data access under export control regulations.