Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Information Automation”

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 973 records · Page 54

Robots as man-extension systems in space

The main topic of the paper is sensing and computer based automation and man-machine interface devices and techniques which permit task-level and 'intelligent' two-way communication between human operator and remote robot in earth orbit. General considerations are presented on control and information problems in teleoperation and on the characteristics of earth orbital teleoperation. Specific control and information display devices and techniques are discussed and exemplified with development results obtained at the Jet Propulsion Laboratory (JPL) in recent years.

Bejczy, A. K.↗

Development of life prediction capabilities for liquid propellant rocket engines. Post-fire diagnostic system for the SSME system architecture study

This system architecture task (1) analyzed the current process used to make an assessment of engine and component health after each test or flight firing of an SSME, (2) developed an approach and a specific set of objectives and requirements for automated diagnostics during post fire health assessment, and (3) listed and described the software applications required to implement this system. The diagnostic system described is a distributed system with a database management system to store diagnostic information and test data, a CAE package for visual data analysis and preparation of plots of hot-fire data, a set of procedural applications for routine anomaly detection, and an expert system for the advanced anomaly detection and evaluation.

Gage, Mark↗

Automated Management Of Documents

Report presents main technical issues involved in computer-integrated documentation. Problems associated with automation of management and maintenance of documents analyzed from perspectives of artificial intelligence and human factors. Technologies that may prove useful in computer-integrated documentation reviewed: these include conventional approaches to indexing and retrieval of information, use of hypertext, and knowledge-based artificial-intelligence systems.

Boy, Guy↗

The RadarSAT-MAMM automated mission planner

The RadarSAT Modified Antarctic Mapping Mission (MAMM) ran from September to November 2000. It consisted of over 2400 synthetic aperture radar (SAR) data takes over Antarctica that had to satisfy coverage and other scientific criteria while obeying tight resource and operational constraints. Developing these plans is a time and knowledge intensive effort. It required over a work-year to manually develop a comparable plan for AMM-1, the precursor mission to MAMM. This paper describes the automated mission planning system for MAMM, which dramatically reduced mission-planning costs to just a few workweeks, and enabled rapid generation of 'what-if' scenarios for evaluating mission-design trades. This latter capability informed several critical design decisions and was instrumental in accurately costing the mission.

RadarSAT Modified Antarctic Mapping Mission (MAMM)↗

Scheduling Onboard Processing for the Proposed HyspIRI Mission

The proposed Hyspiri mission is evaluating a X-band Direct Broadcast (DB) capability that would enable data to be delivered to ground stations virtually as it is acquired. However the HyspIRI VSWIR and TIR instruments will produce 1 Gbps data while the DB capability is 15 M bps for a ~60x oversubscription. In order to address this data volume mismatch a DB concept has been developed thatdetermines which data to downlink based on both: 1. The type of surface the spacecraft is overflying and 2. Onboard processing of the data to detect events. For example when the spacecraft is overflying polar regions it might downlink a snow/ice product. Additionally the onboard software will search for thermal signatures indicative of a volcanic event or wild fire and downlink summary information (extent, spectra) when detected. The process of determining which products to generate when, based on request prioritization and onboard processing and downlink constraints is inherently a prioritized scheduling problem - we describe work to develop an automated solution to this problem.

visible shortwave infrared (VSWIR)↗

Knowledge Base for Distributed Spacecraft Mission Design Using the Trade-Space Analysis Tool for Constellations (TAT-C)

Opportunities for multi-point measurements, greater revisit frequency, failure robustness, and improved cost effectiveness motivate consideration of Distributed Spacecraft Missions (DSMs) for future Earth science missions. However, careful analysis is required to assess the distributed sensing capabilities of a constellation compared to more mature monolithic spacecraft while also considering other important dimensions such as cost and risk. The large combinatorial DSM design space limits existing mission analysis tools and exploration methods which emphasize monolithic design variables. The Trade-space Analysis Tool for Constellations (TAT-C) under development at Goddard seeks to enumerate and evaluate alternative mission architectures to minimize cost and maximize scientific return for pre-defined goals during pre-phase A analysis.Similar to other model-centric engineering efforts, efficient data management is a significant challenge for DSM mission analysis. In TAT-C, a Knowledge Base (KB) is envisioned as a cumulative central repository of information and meta-information about DSMs. Initial KB concepts store related data for reuse within or across mission analyses; however, over time, the KB is envisioned to be an important layer to coordinate actions of both human analysts and automated design agents to search a large design space for desirable mission alternatives. Preliminary KB research builds on a modern web technology stack to provide the following functionality: 1) storage of trade-space search requests which set requirements and constraints for DSM concepts, 2) storage of analysis results which quantify performance metrics for evaluated DSM concepts, 3) a RESTful application programming interface (API) for scripted access to data from TAT-C modules, 4) web-based graphical user interface (GUI) for manual access to underlying data, and 5) access control and management restrictions relevant to data protection and security. These efforts have culminated in a prototype KB used by the research team during TAT-C development to assess opportunities for future work.

Pattern Recognition↗

Field Evaluations of Sampling, Interviewing, and Flight Tracking of NASA's Low Boom Flight Demonstrator Aircraft

The first year’s effort identified sampling and interviewing as the principal risks to assessment of prompt reactions to overflights producing low-amplitude sonic booms. It also 1) established the utility of geo-information system-based route planning for LBFD flight missions, 2) developed and demonstrated a prototype of a geographically-distributed, Internet-enabled instrumentation system capable of wide-area tracking of LBFD aircraft in near-real time. The latter system permits synchronizing the conduct of interviews in multiple overflown communities with arrival times of shock waves at interviewing sites; and of measuring, archiving, and processing their acoustic signatures. Means were also recommended for constructing representative, telephone-based samples of eligible respondents living in households within carpet boom corridors adjacent to LBFD flight tracks, and for conducting interviews with cross-sectional (independent) samples of such respondents about their prompt reactions to exposure to low-amplitude sonic booms. A detailed study design was prepared and accepted by NASA for a set of single-contact attempt telephone interviews with a nationally representative sample of households. The study design focused on testing automated and live agent interview completion rates obtainable without callbacks. A minimal (two monitoring station) version of the aircraft tracking system was built and installed near a civil airport in a successful demonstration of the system’s ability to detect and track aircraft movements. The field exercise also demonstrated the ability of the system to capture the acoustic emissions of departing aircraft, and to serve aircraft position and sound level information to remote, geographically-distributed analysts in near-real time. Upon approval of OMB and IRB of the detailed study plan, a stratified, nationally representative sample of landline and wireless telephone-subscribing households was constructed. A total of 12,734 telephone interview contact attempts of the sort required by a straightforward cross-sectional study design were then made. These contact attempts demonstrated the impracticality of conducting a time-critical, cross-sectional study of prompt community response to low-amplitude sonic booms by means of “independent” (single contact attempt per respondent for each LBFD flight mission) telephone samples of respondents. The observed interview completion rates for these single telephone contact attempts were so low (~ 1% to 3% for automated and live agent interviews, respectively) that: 1) the representativeness of collected opinions would be susceptible to intuitive challenge as inadequate, even absent conclusive evidence of non-representativeness. Refuting challenges to representativeness would have to demonstrate that the composition of the actual sample did not differ from that of the target population, a task that is tantamount to proving a negative; 2) the information required to refute allegations of non-representativeness would require a questionnaire considerably lengthier than that required simply to determine the prevalence of boom-induced startle and annoyance. Such a questionnaire would have to inquire about potentially sensitive and intrusive matters, including respondents’ age, gender, education, employment, home ownership, income, ethnicity, family size, and other demographic factors; and 3) unreasonable numbers of attempts would be required to re-contact households with unsuccessful initial contact attempts, given the limited time available for doing so. For example, if about 500 completed interviews were desired in a supersonically overflown community, approximately 50,000 automated interview attempts would have to be made within ten to fifteen minutes of each LBFD overflight. Such large numbers of contact attempts could well exceed the numbers of households available for interview in areas of similar boom exposure levels in some communities near LBFD flight tracks. Such large numbers of interviews could be cost-effectively undertaken only by means of automated (i.e., outgoing interactive voice response) interviewing, a data collection method ill-suited for complex and sensitive questionnaire items. The infeasibility of independent sampling for evaluating prompt responses to LBFD overflights in a cross-sectional study is due in large part to simple non-response: that is, potential respondents – particularly those contacted on wireless telephones – refusing to answer calls with unfamiliar caller IDs. It is also due in part, however, to 1) the lack of time to attempt to contact the same respondent more than once within a few minutes after the arrival of a shock wave at the respondent’s location; and 2) the need to place calls during weekday/daytime hours, when response rates are notably lower than during evenings and weekends. Despite the poor interview completion rates achieved under the above constraints, cross sectional assessments of delayed reactions to LBFD overflights could still be feasible, if multiple attempts could be made to contact respondents during evening and weekend time periods, over extended time periods. Detailed plans for a longitudinal (panel) sample were developed as an alternative to a cross sectional sample design.

Fidell, Sanford↗

A Geometry Based Infra-Structure for Computational Analysis and Design

The computational steps traditionally taken for most engineering analysis suites (computational fluid dynamics (CFD), structural analysis, heat transfer and etc.) are: (1) Surface Generation -- usually by employing a Computer Assisted Design (CAD) system; (2) Grid Generation -- preparing the volume for the simulation; (3) Flow Solver -- producing the results at the specified operational point; (4) Post-processing Visualization -- interactively attempting to understand the results. For structural analysis, integrated systems can be obtained from a number of commercial vendors. These vendors couple directly to a number of CAD systems and are executed from within the CAD Graphical User Interface (GUI). It should be noted that the structural analysis problem is more tractable than CFD; there are fewer mesh topologies used and the grids are not as fine (this problem space does not have the length scaling issues of fluids). For CFD, these steps have worked well in the past for simple steady-state simulations at the expense of much user interaction. The data was transmitted between phases via files. In most cases, the output from a CAD system could go to Initial Graphics Exchange Specification (IGES) or Standard Exchange Program (STEP) files. The output from Grid Generators and Solvers do not really have standards though there are a couple of file formats that can be used for a subset of the gridding (i.e. PLOT3D data formats). The user would have to patch up the data or translate from one format to another to move to the next step. Sometimes this could take days. Specifically the problems with this procedure are:(1) File based -- Information flows from one step to the next via data files with formats specified for that procedure. File standards, when they exist, are wholly inadequate. For example, geometry from CAD systems (transmitted via IGES files) is defined as disjoint surfaces and curves (as well as masses of other information of no interest for the Grid Generator). This is particularly onerous for modern CAD systems based on solid modeling. The part was a proper solid and in the translation to IGES has lost this important characteristic. STEP is another standard for CAD data that exists and supports the concept of a solid. The problem with STEP is that a solid modeling geometry kernel is required to query and manipulate the data within this type of file. (2) 'Good' Geometry. A bottleneck in getting results from a solver is the construction of proper geometry to be fed to the grid generator. With 'good' geometry a grid can be constructed in tens of minutes (even with a complex configuration) using unstructured techniques. Adroit multi-block methods are not far behind. This means that a million node steady-state solution can be computed on the order of hours (using current high performance computers) starting from this 'good' geometry. Unfortunately, the geometry usually transmitted from the CAD system is not 'good' in the grid generator sense. The grid generator needs smooth closed solid geometry. It can take a week (or more) of interaction with the CAD output (sometimes by hand) before the process can begin. One way Communication. (3) One-way Communication -- All information travels on from one phase to the next. This makes procedures like node adaptation difficult when attempting to add or move nodes that sit on bounding surfaces (when the actual surface data has been lost after the grid generation phase). Until this process can be automated, more complex problems such as multi-disciplinary analysis or using the above procedure for design becomes prohibitive. There is also no way to easily deal with this system in a modular manner. One can only replace the grid generator, for example, if the software reads and writes the same files. Instead of the serial approach to analysis as described above, CAPRI takes a geometry centric approach. This makes the actual geometry (not a discretized version) accessible to all phases of the analysis. The connection to the geometry is made through an Application Programming Interface (API) and NOT a file system. This API isolates the top-level applications (grid generators, solvers and visualization components) from the geometry engine. Also this allows the replacement of one geometry kernel with another, without effecting these top-level applications. For example, if UniGraphics is used as the CAD package then Parasolid (UG's own geometry engine) can be used for all geometric queries so that no solid geometry information is lost in a translation. This is much better than STEP because when the data is queried, the same software is executed as used in the CAD system. Therefore, one analyzes the exact part that is in the CAD system. CAPRI uses the same idea as the commercial structural analysis codes but does not specify control. Software components of the CAD system are used, but the analysis suite, not the CAD operator, specifies the control of the software session. This also means that the license issues (may be) minimized and individuals need not have to know how to operate a CAD system in order to run the suite.

Haimes, Robert↗

Vista goes online: Decision-analytic systems for real-time decision-making in mission control

The Vista project has centered on the use of decision-theoretic approaches for managing the display of critical information relevant to real-time operations decisions. The Vista-I project originally developed a prototype of these approaches for managing flight control displays in the Space Shuttle Mission Control Center (MCC). The follow-on Vista-II project integrated these approaches in a workstation program which currently is being certified for use in the MCC. To our knowledge, this will be the first application of automated decision-theoretic reasoning techniques for real-time spacecraft operations. We shall describe the development and capabilities of the Vista-II system, and provide an overview of the use of decision-theoretic reasoning techniques to the problems of managing the complexity of flight controller displays. We discuss the relevance of the Vista techniques within the MCC decision-making environment, focusing on the problems of detecting and diagnosing spacecraft electromechanical subsystems component failures with limited information, and the problem of determining what control actions should be taken in high-stakes, time-critical situations in response to a diagnosis performed under uncertainty. Finally, we shall outline our current research directions for follow-on projects.

Barry, Matthew↗

Mission Evaluation Room Intelligent Diagnostic and Analysis System (MIDAS)

The role of Mission Evaluation Room (MER) engineers is to provide engineering support during Space Shuttle missions, for Space Shuttle systems. These engineers are concerned with ensuring that the systems for which they are responsible function reliably, and as intended. The MER is a central facility from which engineers may work, in fulfilling this obligation. Engineers participate in real-time monitoring of shuttle telemetry data and provide a variety of analyses associated with the operation of the shuttle. The Johnson Space Center's Automation and Robotics Division is working to transfer advances in intelligent systems technology to NASA's operational environment. Specifically, the MER Intelligent Diagnostic and Analysis System (MIDAS) project provides MER engineers with software to assist them with monitoring, filtering and analyzing Shuttle telemetry data, during and after Shuttle missions. MIDAS off-loads to computers and software, the tasks of data gathering, filtering, and analysis, and provides the engineers with information which is in a more concise and usable form needed to support decision making and engineering evaluation. Engineers are then able to concentrate on more difficult problems as they arise. This paper describes some, but not all of the applications that have been developed for MER engineers, under the MIDAS Project. The sampling described herewith was selected to show the range of tasks that engineers must perform for mission support, and to show the various levels of automation that have been applied to assist their efforts.

Pack, Ginger L.↗

Value added data archiving

Researchers in the Molecular Sciences Research Center (MSRC) of Pacific Northwest Laboratory (PNL) currently generate massive amounts of scientific data. The amount of data that will need to be managed by the turn of the century is expected to increase significantly. Automated tools that support the management, maintenance, and sharing of this data are minimal. Researchers typically manage their own data by physically moving datasets to and from long term storage devices and recording a dataset's historical information in a laboratory notebook. Even though it is not the most efficient use of resources, researchers have tolerated the process. The solution to this problem will evolve over the next three years in three phases. PNL plans to add sophistication to existing multilevel file system (MLFS) software by integrating it with an object database management system (ODBMS). The first phase in the evolution is currently underway. A prototype system of limited scale is being used to gather information that will feed into the next two phases. This paper describes the prototype system, identifies the successes and problems/complications experienced to date, and outlines PNL's long term goals and objectives in providing a permanent solution.

Berard, Peter R.↗

Fault Tree Based Diagnosis with Optimal Test Sequencing for Field Service Engineers

When field service engineers go to customer sites to service equipment, they want to diagnose and repair failures quickly and cost effectively. Symptoms exhibited by failed equipment frequently suggest several possible causes which require different approaches to diagnosis. This can lead the engineer to follow several fruitless paths in the diagnostic process before they find the actual failure. To assist in this situation, we have developed the Fault Tree Diagnosis and Optimal Test Sequence (FTDOTS) software system that performs automated diagnosis and ranks diagnostic hypotheses based on failure probability and the time or cost required to isolate and repair each failure. FTDOTS first finds a set of possible failures that explain exhibited symptoms by using a fault tree reliability model as a diagnostic knowledge to rank the hypothesized failures based on how likely they are and how long it would take or how much it would cost to isolate and repair them. This ordering suggests an optimal sequence for the field service engineer to investigate the hypothesized failures in order to minimize the time or cost required to accomplish the repair task. Previously, field service personnel would arrive at the customer site and choose which components to investigate based on past experience and service manuals. Using FTDOTS running on a portable computer, they can now enter a set of symptoms and get a list of possible failures ordered in an optimal test sequence to help them in their decisions. If facilities are available, the field engineer can connect the portable computer to the malfunctioning device for automated data gathering. FTDOTS is currently being applied to field service of medical test equipment. The techniques are flexible enough to use for many different types of devices. If a fault tree model of the equipment and information about component failure probabilities and isolation times or costs are available, a diagnostic knowledge base for that device can be developed easily.

Iverson, David L.↗

Design and Development of Responder: a Notification-Acknowledgment Android OS Phone Application

This paper discusses the design and development of the Android phone application Responder and how it assists Flight Operation Team (FOT) members in handling alerts from a Short Message Service (SMS) text message and email based notification system. The FOT needed a simplified and more powerful tool for receiving, storing, and acknowledging notifications sent from the ground systems automated notification software called Attention! (Registered Trademark). The previous system was to rely on a text message application that comes on a phone. This way was slow, inefficient, and did a poor job of keeping FOT members informed on the state of a situation when multiple notifications are being sent out by Attention! (Registered Trademark). Responder is designed to provide easier viewing and acknowledging of multiple messages. It gives the user a quick look at all recently received messages in an organized and clean manner that prevents notifications from being lost during a large burst of messages. It makes it easier to find and review old messages received and Responder was designed to give the user more flexibility in setting up how and what alerts will notify them when they are received by the phone. Since the implementation of Responder the FOT members are more informed and are able to focus more on problem solving the reason a notification was received then trying to keep up with sending cumbersome acknowledgements over text message or email. Responder is only able to receive and send SMS text messages but by using email to text services provided by the cellular carrier it is able to send and receive emails.

notification↗

A Practical Approach to Uncertainty Quantification Using Probability Boxes

To date, while the use of CFD for aerospace vehicle design and development is prevalent, the documentation of uncertainties associated with the simulations are rare. Instead, the current state-of-the-art relies heavily on the experience of the CFD practitioner to estimate the uncertainty associated with their simulations through simple sensitivity studies or subject matter expertise. This practice will have to be replaced with a formal uncertainty quantification (UQ) process if CFD is to play an expanded role in the research and engineering design community, test and evaluation community, and ultimately certification for flight. Accounting for uncertainties in a formal manner is a tedious process. Moreover, the typical CFD practitioner is not likely to be familiar with formal UQ methods. These factors have prevented the adoption of UQ methods in the engineering design and development cycle. This presentation will outline a credible approach to UQ using Probability Boxes that is straightforward to apply, and can readily be automated using existing UQ tool sets such as the DAKOTA packaged developed at Sandia. The added expense incurred when moving away from a deterministic CFD process to a stochastic one that captures uncertainties to enable risk-informed decision making will be discussed, as well as effective ways to reduce the computational costs.

Uncertainty Quantification↗

Human-In-The-Loop Investigation of Interoperability Between Terminal Sequencing and Spacing, Automated Terminal Proximity Alert, and Wake-Separation Recategorization

A human-in-the-loop simulation study addressed terminal-area controller-workstation interface variations for interoperability between three new capabilities being introduced by the FAA. The capabilities are Terminal Sequencing and Spacing (TSAS), Automated Terminal Proximity Alert (ATPA), and wake-separation recategorization, or 'RECAT.' TSAS provides controllers with Controller-Managed Spacing (CMS) tools, including slot markers, speed advisories, and early/late indications, together with runway assignments and sequence numbers. ATPA provides automatic monitor, warning, and alert cones to inform controllers about spacing between aircraft on approach. ATPA cones are sized according to RECAT, an improved method of specifying wake-separation standards. The objective of the study was to identify potential issues and provide recommendations for integrating TSAS with ATPA and RECAT. Participants controlled arrival traffic under seven different display configurations, then tested an 'exploratory' configuration developed with participant input. All the display conditions were workable and acceptable, but controllers strongly preferred having the CMS tools available on Feeder positions, and both CMS tools and ATPA available on Final positions. Controllers found the integrated systems favorable and liked being able to tailor configurations to individual preferences.

ATD-1↗

Machine Learning for Predicting Team Functioning in HERA Missions

Team functioning is integral to success in future long term space exploration missions. Proactively detecting declines in team functioning can mitigate conflict and ensure mission success. This project developed a speech-based artificial intelligence (AI) system that unobtrusively predicts degradation in team functioning, including performance and cohesion, in the Human Exploration Research Analog (HERA) Campaigns 4 and 5. The AI system conducted automated analysis of the prosodic (tone of voice) and linguistic (language content) components of speech, modeling interpersonal dynamics at both the turn-taking and day-wide levels. We investigated team functioning via observing structured interactions (i.e., multi-mission space exploration vehicle-extra vehicular activity [MMSEV-EVA], team interaction battery [TIB]) and unstructured interactions before the MMSEV-EVA task. We developed machine learning models to predict team functioning (objective task accuracy, self reported team efficacy and self reported team cohesion) by analyzing OpenSmile acoustic features, linguistic descriptors extracted via the linguistic inquiry and word count (LIWC) dictionary, and semantic embeddings. In the TIB, static models using logistic regression and random forests were not able to predict task accuracy, but predicted team efficacy and cohesion during both the decision making and relational tasks to a moderate level (60-70%). Majority voting on the individual turns to predict day long team efficacy further increased accuracies (70-80%). Finally, long short-term memory (LSTM) models showed the best performance across all variables (80-91%), including task performance. In the MMSEV-EVA, static models achieved an accuracy of 60% with majority voting, which increased to 80% through the incorporation of mission day as a variable, accounting for the learning effect. A key finding across both tasks was the "team-dependent" nature of these interactions; models achieved much higher accuracy when trained on prior days of the same team's data rather than attempting to generalize across entirely different teams, with even 1-2 days of prior data per team achieving 5-15% improvement over team-independent models. In addition, the incorporation of pre-task data from the same team also improves model performance, e.g., incorporating data from the decision-making task of the TIB, which preceded the relational task, improved the prediction of team efficacy and cohesion during the latter. We compared model performance when trained on machine-generated data compared to data that had been further corrected by human annotators. Overall, models trained on human-corrected data exhibited a modest improvement in performance, particularly when acoustic features were used. We found no significant correlation between word error rate (WER) and model accuracy (r(55) = -0.08, p = 0.51), but model’s accuracy was significantly higher for medium/high quality transcription (0.74 (SD = 0.48)) compared to the low-quality group (0.64 (SD = 0.36)) (t(63)=2.82, p = 0.006). Based on these, several design recommendation emerge, that could inform Standards at NASA. Models predicting team functioning should incorporate at least one to two days of historical interaction data, include brief pre-task discussions, and explicitly model temporal learning effects, especially for longer operational tasks. Minimum quality standards for automated speech-processing pipelines are needed, given the performance gains observed with manually corrected acoustic data. Finally, systems should leverage both acoustic features and language embeddings in complementary ways, with modality choices and fusion strategies tailored to mission context, task demands, and data quality requirements.

Shrivatsa Mishra↗

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗