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.

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 SAE Aerospace Information Report (AIR) is to provide information that would be useful to potential users/operators and decision makers for evaluating and quantifying the benefits of an Engine Monitoring Systems (EMS) versus its cost of implementation. This document presents excerpts from reports developed to analyze “actual aircraft cost/benefits results”. These are presented as follows: a First, to outline the benefits and cost elements pertaining to EMS that may be used in performing a cost versus benefits analysis. b Second, to present considerations for use in conducting the analysis. c Third, to provide examples of analyses and results as they relate to the user/operator and decision-maker community. The document encompasses helicopters and fixed wing aircraft and distinguishes between civilian and military considerations.

The report shows how the methodology of measurement uncertainty can usefully be applied to test programs in order to optimize resources and save money. In doing so, it stresses the importance of integrating the generation of the Defined Measurement Process into more conventional project management techniques to create a Test Plan that allows accurate estimation of resources and trouble-free execution of the actual test. Finally, the report describes the need for post-test review and the importance of recycling lessons learned for the next project.

The scope of this document is limited to encompass terminology, symbols, performance criteria and certain elementary test methods reflecting the current status of the technology.