Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “standardized data”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 955 records · Page 53

Space Station-era ground data handling

Planning is underway for the handling of the peak return link data rates ranging from 300 to 1200 Mbps that are associated with the emerging Space Station orbital-systems era. Ground data handling services encompass the enhancement of on-board ancilliary data packets to furnish standard calibrations and transformations not available on-board; remote access to an interactive data base will allow users to select and withdraw specified parameters based on user-defined criteria.

Smith, Gene A.↗

Propeller design - a simple system based on model propeller test data III

This report, the third of a series of four, describes a simple system for designing propellers of a standard form. In this report, the system is based on tests of a family of model propellers of standard Navy form, the data from which have been extended by means of calculations to cover the complete range likely to be found in practice. However, it can be worked out for any family having propellers of one general form.

Wieck, Fred E↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S. Faragalla↗

Kinematic Sensors Evaluation for Spaceflight Exercise Data Collections

INTRODUCTION: On the International Space Station (ISS), exercise feedback from astronauts is very important to diagnose and mitigate any form-related injuries and ensure efficacious exercise prescriptions and systems. Going forward, exploration exercise efforts seek to gain further quantitative data of human and system performance. Currently, methods of collecting in-flight exercise data on the ISS are limited to marker-based motion capture (MoCap) where astronauts must wear reflective markers over their clothes and specialized cameras are used. The main objective of this work was to investigate the following alternative tracking options: markerless video-based MoCap and inertial measurement units (IMUs). These were compared against traditional marker-based MoCap to evaluate kinematic accuracy and inform feasible methods for future exercise data collections on the ISS, especially in support of future Vibration Isolation and Stabilization (VIS) system development. METHODS: Three test subjects performed a variety of flight-like resistance and aerobic exercises using the Miniature Exercise Device (MED-2), Concept-2 rowing ergometer, barbell mockup, bench (e.g., for bench press, hip thruster, and cycling), and a custom structure for dips. These were intended also to represent exercises which could be performed on the multi-modality European Enhanced Exploration Exercise Device (E4D) [1]. The marker-based MoCap data, collected through a 16-camera OptiTrack MoCap system, was regarded as the gold standard to compare the data against. Passive markers were affixed to each subject according to a modified full body Plug-in Gait marker set [2] with 46 total markers. The markerless MoCap data was collected using two GoPro Hero7 cameras and one GoPro Hero11 camera. For the IMU data, a full body set of 17 Xsens DOTs were placed on the subject: 10 upper body and 7 lower body IMUs. Biomechanical modeling and evaluation was conducted through OpenSim [3] (MoCap), OpenSense [4] (IMU), OpenCap [5] (markerless), ENABLE [6] (markerless), and other modeling software. Secondary objectives included comparing the volume of equipment, reducing mass and crew set-up time. RESULTS AND DISCUSSION: While there were issues with initial processing for the IMUs and markerless MoCap, the results aided in the understanding of each sensor, developing end-to-end processes, and identifying future needs. Some observed concerns with the markerless MoCap approaches included being cognizant of a cluttered background, number of people in field of view, camera number and placement. Some challenges with the IMUs included possible sliding, early deactivation possibly due to exercise pose, and large quantity sensor synchronization. Overall, the markerless MoCap option may be the preferred method of data collection and processing as it provides a solution for certain IMU shortcomings and may be least in equipment volume, upmass, and crew setup time. CONCLUSIONS: While this work was mainly focused on ISS data collection, these sensor data along with continued evaluation and development efforts will help to establish best methods for exercise data collection on Gateway, for other Artemis missions, and beyond. Details on the latest end-to-end processing of the data and results will be presented, along with lessons learned and recommended sensor selection and methods.

S Faragalla↗

BEAST: Expanding Sustainable Data Infrastructure for High-Enthalpy Facilities

Reproducible, data-driven thermal protection system (TPS) research requires that experimental records from high-enthalpy testing be consistently structured, traceable, and accessible across campaigns and institutions. In practice, however, arcjet and plasma facilities data remain largely fragmented: raw diagnostics are stored in ad hoc formats, material sample histories are disconnected from test conditions, and metadata standards are absent, precluding systematic cross-campaign analysis and long-term reuse. BEAST (Backend for Experiment Analysis, Storage, and Traceability) is an open-source, web-based platform that addresses these limitations by providing a unified, queryable infrastructure for high-enthalpy ground-test data [1]. First presented at the 15th Ablation Workshop [2], BEAST has since undergone significant development. The platform ingests and structures multi-channel time-series diagnostics, facility configurations, and material property records within a common provenance model, ensuring end-to-end traceability from raw sensor acquisition to reduced experimental quantities. A versioned material library links specimen identity and processing history to the specific runs in which each sample was tested. An integrated modeling workbench enables training and evaluation of regression models directly on archived experimental data, supporting condition interpolation and the construction of empirical material response databases. Beyond its original deployment at NASA Ames Research Center, BEAST has been designed to be facility-agnostic, with ongoing efforts to extend its adoption to other facilities. Its modular architecture accommodates heterogeneous diagnostic setups and facility types, and its future open-source distribution allows institutions to build on a common data standard rather than maintaining isolated, bespoke solutions. BEAST is further integrated within a broader ecosystem of companion tools: arcjetCV [3] extracts recession rates and shock standoff distances from high-speed video using computer vision, and miniSTARscan [4] provides sub-minute, portable photogrammetric surface reconstruction of test articles before and after exposure. All tools share a common data schema, enabling seamless ingestion of surface geometry, imagery, and time-series data into a single, coherent experimental record.

Database↗

BEAST: Expanding Sustainable Data Infrastructure for High-Enthalpy Facilities

Reproducible, data-driven thermal protection system (TPS) research requires that experimental records from high-enthalpy testing be consistently structured, traceable, and accessible across campaigns and institutions. In practice, however, arcjet and plasma facilities data remain largely fragmented: raw diagnostics are stored in ad hoc formats, material sample histories are disconnected from test conditions, and metadata standards are absent, precluding systematic cross-campaign analysis and long-term reuse. BEAST (Backend for Experiment Analysis, Storage, and Traceability) is an open-source, web-based platform that addresses these limitations by providing a unified, queryable infrastructure for high-enthalpy ground-test data [1]. First presented at the 15th Ablation Workshop [2], BEAST has since undergone significant development. The platform ingests and structures multi-channel time-series diagnostics, facility configurations, and material property records within a common provenance model, ensuring end-to-end traceability from raw sensor acquisition to reduced experimental quantities. A versioned material library links specimen identity and processing history to the specific runs in which each sample was tested. An integrated modeling workbench enables training and evaluation of regression models directly on archived experimental data, supporting condition interpolation and the construction of empirical material response databases. Beyond its original deployment at NASA Ames Research Center, BEAST has been designed to be facility-agnostic, with ongoing efforts to extend its adoption to other facilities. Its modular architecture accommodates heterogeneous diagnostic setups and facility types, and its future open-source distribution allows institutions to build on a common data standard rather than maintaining isolated, bespoke solutions. BEAST is further integrated within a broader ecosystem of companion tools: arcjetCV [3] extracts recession rates and shock standoff distances from high-speed video using computer vision, and miniSTARscan [4] provides sub-minute, portable photogrammetric surface reconstruction of test articles before and after exposure. All tools share a common data schema, enabling seamless ingestion of surface geometry, imagery, and time-series data into a single, coherent experimental record.

Database↗

NASA Taxonomies for Searching Problem Reports and FMEAs

Many types of hazard and risk analyses are used during the life cycle of complex systems, including Failure Modes and Effects Analysis (FMEA), Hazard Analysis, Fault Tree and Event Tree Analysis, Probabilistic Risk Assessment, Reliability Analysis and analysis of Problem Reporting and Corrective Action (PRACA) databases. The success of these methods depends on the availability of input data and the analysts knowledge. Standard nomenclature can increase the reusability of hazard, risk and problem data. When nomenclature in the source texts is not standard, taxonomies with mapping words (sets of rough synonyms) can be combined with semantic search to identify items and tag them with metadata based on a rich standard nomenclature. Semantic search uses word meanings in the context of parsed phrases to find matches. The NASA taxonomies provide the word meanings. Spacecraft taxonomies and ontologies (generalization hierarchies with attributes and relationships, based on terms meanings) are being developed for types of subsystems, functions, entities, hazards and failures. The ontologies are broad and general, covering hardware, software and human systems. Semantic search of Space Station texts was used to validate and extend the taxonomies. The taxonomies have also been used to extract system connectivity (interaction) models and functions from requirements text. Now the Reconciler semantic search tool and the taxonomies are being applied to improve search in the Space Shuttle PRACA database, to discover recurring patterns of failure. Usual methods of string search and keyword search fall short because the entries are terse and have numerous shortcuts (irregular abbreviations, nonstandard acronyms, cryptic codes) and modifier words cannot be used in sentence context to refine the search. The limited and fixed FMEA categories associated with the entries do not make the fine distinctions needed in the search. The approach assigns PRACA report titles to problem classes in the taxonomy. Each ontology class includes mapping words - near-synonyms naming different manifestations of that problem class. The mapping words for Problems, Entities and Functions are converted to a canonical form plus any of a small set of modifier words (e.g. non-uniformity NOT + UNIFORM.) The report titles are parsed as sentences if possible, or treated as a flat sequence of word tokens if parsing fails. When canonical forms in the title match mapping words, the PRACA entry is associated with the corresponding Problem, Entity or Function in the ontology. The user can search for types of failures associated with types of equipment, clustering by type of problem (e.g., all bearings found with problems of being uneven: rough, irregular, gritty ). The results could also be used for tagging PRACA report entries with rich metadata. This approach could also be applied to searching and tagging failure modes, failure effects and mitigations in FMEAs. In the pilot work, parsing 52K+ truncated titles (the test cases that were available), has resulted in identification of both a type of equipment and type of problem in about 75% of the cases. The results are displayed in a manner analogous to Google search results. The effort has also led to the enrichment of the taxonomy, adding some new categories and many new mapping words. Further work would make enhancements that have been identified for improving the clustering and further reducing the false alarm rate. (In searching for recurring problems, good clustering is more important than reducing false alarms). Searching complete PRACA reports should lead to immediate improvement.

Malin, Jane T.↗

NASA GeneLab RNASeq Consensus Pipeline: A Nextflow Implementation

The NASA GeneLab project (genelab.nasa.gov) seeks to accelerate space biology research through cataloging and democratizing omics data. Since raw omics data is largely inaccessible to non-bioinformaticians, GeneLab works with the scientific community to develop standard processing pipelines to generate and publish processed data. Unlike raw data, processed data has greater immediate value to a wide range of users with varying technical backgrounds and computational capabilities. Standardizing processing workflows is essential to match the pace of raw data generation, ensure reproducibility, and enable standardized processed data for comparison across datasets. Previously, GeneLab developed a standardized pipeline for processing RNAseq data, referred to as the ‘GeneLab RNAseq Consensus Pipeline (RCP)’, in collaboration with GeneLab’s Analysis Working Groups. The work presented here is a Nextflow implementation of GeneLab’s RCP that automates and accelerates data processing of RNASeq datasets hosted on GeneLab. In addition to the core data processing, the workflow also includes staging of GeneLab raw data and a robust verification and validation (V&V) program that runs after each processing step to identify errors in real-time, stop additional downstream computation, and preserve computational resources. The workflow, including the staging and V&V functionality, is open source for others to reuse and modify at https://github.com/nasa/GeneLab_Data_Processing/tree/master/RNAseq.

Jonathan Dejesus Oribello↗

NASA GeneLab RNASeq Consensus Pipeline: A Nextflow Implementation

The NASA GeneLab project (genelab.nasa.gov) seeks to accelerate space biology research through cataloging and democratizing omics data. Since raw omics data is largely inaccessible to non-bioinformaticians, GeneLab works with the scientific community to develop standard processing pipelines to generate and publish processed data. Unlike raw data, processed data has greater immediate value to a wide range of users with varying technical backgrounds and computational capabilities. Standardizing processing workflows is essential to match the pace of raw data generation, ensure reproducibility, and enable standardized processed data for comparison across datasets. Previously, GeneLab developed a standardized pipeline for processing RNAseq data, referred to as the ‘GeneLab RNAseq Consensus Pipeline (RCP)’, in collaboration with GeneLab’s Analysis Working Groups. The work presented here is a Nextflow implementation of GeneLab’s RCP that automates and accelerates data processing of RNASeq datasets hosted on GeneLab. In addition to the core data processing, the workflow also includes staging of GeneLab raw data and a robust verification and validation (V&V) program that runs after each processing step to identify errors in real-time, stop additional downstream computation, and preserve computational resources. The workflow, including the staging and V&V functionality, is open source for others to reuse and modify at https://github.com/nasa/GeneLab_Data_Processing/tree/master/RNAseq.

Jonathan D Oribello↗

Investigation of Antarctic crust and upper mantle using MAGSAT and other geophysical data

Antarctica is the perfect proving ground for testing data reduction procedures which are alternatives to the standard procedure employing polynomial fitting. Unreduced data (observed values minus corefield model theo each pass) were averaged in 3 degree bins. The resulting map was then high pass filtered using a finite Fourier transform filter so that spectral peaks between 4200 km and 5280 km were diminished by 1/3, peaks corresponding to wavelengths greater than or equal to 5280 km were diminished by 1/2, and the d.c. component was set equal to zero. The surface subtracted in this way differs from the polynomials used in the standard method in that it is static over the 5 north data window. The map produced is presented and the effects of the static model are compared to those of the dynamic mode.

Bentley, C. R.↗

Subsonic Ultra Green Aircraft Research: Phase V – Buffet Test Report

This test report summarizes work performed by the Boeing Subsonic Ultra-Green Aircraft Research (SUGAR) team in the Phase V Transonic Truss-Braced Wing contract task. The task was awarded in September 2020, and ended at the end of September 2022. As a part of the SUGAR Phase V contract task, Boeing developed a wind tunnel test plan, model requirements, then fabricated and conducted a dedicated transonic buffet wind tunnel test. The test focused on the investigation of buffet onset, and the ability to accurately predict buffet onset for the TTBW configuration. This report summarizes the results and post-test analysis of the 9% scale, semispan, Transonic Truss-Braced Wing (TTBW) transonic buffet model tested at the NASA Ames Research Center Unitary Plan Wind Tunnel (UPWT) 11-Foot Transonic Wind Tunnel (11-Ft TWT) facility located at Moffett Field, CA. It was tested from January 24, 2022, through February 18, 2022. The wind tunnel test was successful in capturing buffet onset at the model design dynamic pressure. Multiple configurations were tested starting in the wing-body-strut configuration and ending with the full configuration including wing-body-strut-nacelle/pylon, and flap hinge. The test also measured the effect of control surface deflections (ailerons and spoilers), as well as the effect of an outboard strut flap. Steady data collected during the test included standard force and moment measurements, as well as wing, strut, nacelle, and body (fuselage) static pressures. These data were collected in a standard pitch-pause mode. Unsteady data captured in the test, collected in continuous pitch mode, included wing and strut dynamic pressures, accelerations, and strains. According to test data, previous concerns regarding critical buffet onset on the strut (at low vehicle lift coefficient) and in the wing-strut channel have been mitigated. Buffet onset on the TTBW appears to follow conventional wing-induced buffet onset mechanisms. However, the critical station where buffet onset first occurs has moved inboard to the wing-strut juncture span location (55-60% span) from the typical ~70% span location. Test data obtained by unsteady pressure transducers provided a good match to expected buffet onset modes. An assessment of different tools and methodologies for predicting buffet onset was conducted. Reasonable agreement was found for buffet boundary predictions between most of the methods examined when using a forward trip location, with the greatest discrepancies from the pitching moment break and trailing edge pressure divergence methods. When an aft trip location was used the buffet boundary predictions diverged more significantly from unsteady pressure measurements. In addition, good agreement between the buffet onset trends were found when the Reynolds number, configuration, or spanload was changed.

strut↗

A User-Focused Renovation of CERES Metadata

Production software and public data products for Clouds and the Earth’s Radiant Energy System (CERES) continue to evolve as the project extends its climate data record. The data management team for CERES is currently undertaking major renovations of both code and data products, the latter of which is, of course, in service of improving user experience. A major mode of CERES’ data product improvement is in renovating products’ metadata. Metadata standards have evolved since CERES began producing its data products in 2000. In its twentieth year, CERES essentially asked the question: how would the project design its data products if it could start all over again? With forthcoming editions, this rebirth will be realized. CERES has redesigned its metadata standards to best position itself for data discoverability. The project has used the latest standards being developed in NASA’s Earth Science Data and Information Systems (ESDIS) Project’s Unified Metadata Model (UMM) documentation; collaborated with the Atmospheric Science Data Center (ASDC) to ensure compliance with Common Metadata Repository compatibility, and continued compliance with Climate and Forecast (CF) Conventions. In doing so, the team created its own, internal document for proper metadata creation and metadata verification software that is deployed prior to all code deliveries. This presentation will discuss this redesign process, as well as needs met and those that are still outstanding in the search for an improved user experience with CERES data products.

Kathleen Dejwakh↗

A technique for the determination of Louisiana marsh salinity zone from vegetation mapped by multispectral scanner data: A comparison of satellite and aircraft data

Vegetation in selected study areas on the Louisiana coast was mapped using low altitude aircraft and satellite (LANDSAT) multispectral scanner data. Fresh, brackish, and saline marshes were then determined from the remotely sensed presence of dominant indicator plant associations. Such vegetational classifications were achieved from data processed through a standard pattern recognition computer program. The marsh salinity zone maps from the aircraft and satellite data compared favorably within the broad salinity regimes. The salinity zone boundaries determined by remote sensing compared favorably with those interpolated from line-transect field observations from an earlier year.

Butera, M. K.↗

The Aviation Performance Measuring System (APMS): An Integrated Suite of Tools for Measuring Performance and Safety

This is a report of work in progress. In it, I summarize the status of the research and development of the Aviation Performance Measuring System (APMS) for managing, processing, and analyzing digital flight-recorded data, The objectives of the NASA-FAA APMS research project are to establish a sound scientific and technological basis for flight-data analysis, to define an open and flexible architecture for flight-data analysis systems, and to articulate guidelines for a standardized database structure on which to continue to build future flight-data-analysis extensions. APMS offers to the air transport community an open, voluntary standard for flight-data-analysis software; a standard that will help to ensure suitable functionality and data interchangeability among competing software programs. APMS will develop and document the methodologies, algorithms, and procedures for data management and analyses to enable users to easily interpret the implications regarding safety and efficiency of operations. APMS does not entail the implementation of a nationwide flight-data-collection system. It is intended to provide technical tools to ease the large-scale implementation of flight-data analyses at both the air-carrier and the national-airspace levels in support of their Flight Operations and Quality Assurance (FOQA) Programs and Advanced Qualifications Programs (AQP). APMS cannot meet its objectives unless it develops tools that go substantially beyond the capabilities of the current commercially available software and supporting analytic methods that are mainly designed to count special events. These existing capabilities, while of proven value, were created primarily with the needs-of aircrews in mind. APMS tools must serve the needs of the government and air carriers, as well as aircrews, to fully support the FOQA and AQP programs. They must be able to derive knowledge not only through the analysis of single flights (special-event detection), but also through statistical evaluation of the performance of large groups of flights. This paper describes the integrated suite of tools that will assist analysts in evaluating the operational performance and safety of the national air transport system, the air carrier, and the aircrew.

Statler, Irving C.↗

Digital optical tape: Technology and standardization issues

During the coming years, digital data storage technologies will continue an aggressive growth to satisfy the user's need for higher storage capacities, higher data transfer rates and long-term archival media properties. Digital optical tape is a promising technology to satisfy these user's needs. As any emerging data storage technology, the industry faces many technological and standardization challenges. The technological challenges are great, but feasible to overcome. Although it is too early to consider formal industry standards, the optical tape industry has decided to work together by initiating prestandardization efforts that may lead in the future to formal voluntary industry standards. This paper will discuss current industry optical tape drive developments and the types of standards that will be required for the technology. The status of current industry prestandardization efforts will also be discussed.

Podio, Fernando L.↗

APMS: An Integrated Set of Tools for Measuring Safety

This is a report of work in progress. In it, I summarize the status of the research and development of the Aviation Performance Measuring System (APMS) for managing, processing, and analyzing digital flight-recorded data. The objectives of the NASA-FAA APMS research project are to establish a sound scientific and technological basis for flight-data analysis, to define an open and flexible architecture for flight-data-analysis systems, and to articulate guidelines for a standardized database structure on which to continue to build future flight-data-analysis extensions. APMS will offer to the air transport community an open, voluntary standard for flight-data-analysis software, a standard that will help to ensure suitable functionality, and data interchangeability, among competing software programs. APMS will develop and document the methodologies, algorithms, and procedures for data management and analyses to enable users to easily interpret the implications regarding safety and efficiency of operations. APMS does not entail the implementation of a nationwide flight-data-collection system. It is intended to provide technical tools to ease the large-scale implementation of flight-data analyses at both the air-carrier and the national-airspace levels in support of their Flight Operations and Quality Assurance (FOQA) Programs and Advanced Qualifications Programs (AQP). APMS cannot meet its objectives unless it develops tools that go substantially beyond the capabilities of the current commercially available software and supporting analytic methods that are mainly designed to count special events. These existing capabilities, while of proven value, were created primarily with the needs of air crews in mind. APMS tools must serve the needs of the government and air carriers, as well as air crews, to fully support the FOQA and AQP programs. They must be able to derive knowledge not only through the analysis of single flights (special-event detection), but through statistical evaluation of the performance of large groups of flights. This paper describes the integrated suite of tools that will assist analysts in evaluating the operational performance and safety of the national air transport system, the air carrier, and the air crew.

Statler, Irving C.↗

APMS: An Integrated Suite of Tools for Measuring Performance and Safety

This is a report of work in progress. In it, I summarize the status of the research and development of the Aviation Performance Measuring System (APMS) for managing, processing, and analyzing digital flight-recorded data. The objectives of the NASA-FAA APMS research project are to establish a sound scientific and technological basis for flight-data analysis, to define an open and flexible architecture for flight-data-analysis systems, and to articulate guidelines for a standardized database structure on which to continue to build future flight-data-analysis extensions . APMS will offer to the air transport community an open, voluntary standard for flight-data-analysis software, a standard that will help to ensure suitable functionality, and data interchangeability, among competing software programs. APMS will develop and document the methodologies, algorithms, and procedures for data management and analyses to enable users to easily interpret the implications regarding safety and efficiency of operations. APMS does not entail the implementation of a nationwide flight-data-collection system. It is intended to provide technical tools to ease the large-scale implementation of flight-data analyses at both the air-carrier and the national-airspace levels in support of their Flight Operations and Quality Assurance (FOQA) Programs and Advanced Qualifications Programs (AQP). APMS cannot meet its objectives unless it develops tools that go substantially beyond the capabilities of the current commercially available software and supporting analytic methods that are mainly designed to count special events. These existing capabilities, while of proven value, were created primarily with the needs of air crews in mind. APMS tools must serve the needs of the government and air carriers, as well as air crews, to fully support the FOQA and AQP programs. They must be able to derive knowledge not only through the analysis of single flights (special-event detection), but through statistical evaluation of the performance of large groups of flights. This paper describes the integrated suite of tools that will assist analysts in evaluating the operational performance and safety of the national air transport system, the air carrier, and the air crew.

Statler, Irving C.↗