Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Maintenance”

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 451 records · Page 25
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

CAIDA CUI Confirmation for OMRS & LCC SOCRRATES Emulator and iSEE Upgrade, Operations, & Analysis

This internship has focused on providing solutions for the Customer Avionics Interface Development and Analysis (CAIDA) subsystem. The main emulator that has been used during this internship is the Software-Only CEV (Crew Exploration Vehicle) Risk Reduction Analysis and Test Engineering Simulator (SOCRRATES). This emulator uses advanced math and physics methods to simulate specific points in a mission, such as ascent, entry, and orbit. Exploration Ground Systems (EGS) must ensure that all KSC based ground systems can be properly integrated with the flight vehicle software, therefore, the Modeling and Simulation Branch (NE-XM) of the KSC (Kennedy Space Center) Engineering Directorate supports a virtual environment that simulates the interface between ground systems and the flight vehicle. A primary component in assuring that is knowing whether the emulators have incorporated the correct CUIs (Compact Unique Identifiers) into their system, as well as understanding both the static and dynamic responses of the individual CUIs. Also, an effort for verification of Operational Maintenance Requirements Specifications (OMRS) and Launch Commit Criteria (LCC) that are supported by SOCRRATES for the Orion Crew Module were part of the project tasks this semester. This internship also focused on comparing two different simulation Commercial-off-the-shelf (COTS) products and to determine whether or not a COTS package was a viable replacement for the current software that the iSEE (Immersive Simulations and Engineering Environment) lab uses. Upon research and testing, I found that this software was not feasible for the lab. It could not easily load CAD (Computer-Aided Design) or CREO models, give live feedback while the user is in the environment, and was not compatible with a virtual reality headset, all of which are necessary for the lab.

Bundy, Caleb↗
NASA NTRSDate not supplied

Designing a Software Architecture for the Precision Assembly of Space Structures

As NASA’s space exploration and science missions expand in complexity, longevity, anddistance beyond earth’s orbit, Orbital Servicing, Assembly and Manufacturing (OSAM)technologies and concepts have become a critical area of ongoing research and innovation.Artemis’ Moon-to-Mars goals of building sustainable elements on and around the Moon andMars that allow our robots and astronauts to explore and conduct more scientific researchwill demand in situ resource utilization, construction, and maintenance to succeed. In-spaceAssembly (ISA), as a sub-component of OSAM, focuses on the on-orbit building or fabricationof mission infrastructure and payloads. One such ISA application is highlighted by the recentNASA In-Space Assembled Telescope (iSAT) study, which stated that the next generation ofspace observatories will exceed the fairing size of existing or even planned launch vehicles andISA has emerged as a viable approach for observatory assembly. Research efforts at NASALangley Research Center have led to the design of a novel TriTruss structural concept for themodular construction of large complex persistent platforms. The TriTruss design and otherdeveloping OSAM technologies enable larger and persistent space missions that would notbe possible with single-launch-sized structures. For example, 20 meter or larger telescopesor orbital platform applications. However, the increased complexity will require autonomousoperations for the construction and maintenance of long-term infrastructure to achieve missionsuccess. NASA’s Precision Assembly of Space Structures (PASS) project is focused on thestructural and autonomy capabilities required to construct an iSAT in deep space. PASSresearch efforts will develop and validate critical technologies needed for effective efficienton-orbit assembly that can be confidently adopted for future systems. PASS will utilize theTriTruss modules to demonstrate the autonomous modular assembly of a 20m-class iSAT mirrorbackbone structure including simulated mirrors and wiring harness. In this paper, we addressthe software and hardware design considerations, technologies, and challenges of designing arobust robotics framework for assembling modular space structures in support of In SpaceAssembly missions in general as well as for PASS specifically.

Benjamin N Kelley↗
DOE OSTI2025

Twinac: initiation of a community-driven accelerator digital twin framework

We present the initiation of a community-driven framework for the integration of accelerator digital twins into control systems: Twinac. Few facilities have fully integrated accelerator digital twins like at Cornell’s CHESS. Many facilities have active research to employ surrogate models to aid in operational decisions like at Argonne’s ALS, MSU’s FRIB, SLAC’s LCLS-II, and Fermilab’s FAST/IOTA, PIP-II, and main complex. To lower the barrier to entry for all accelerator facilities to build and benefit from a digital twin of their own accelerators, we propose the following software framework. Twinac will provide the capability to compose one’s own digital twin using reusable components engineered at other facilities. With this model in place, Twinac will also support tools for (1) predictive maintenance systems; (2) discovery of correlated but uncontrolled environmental factors, like seasonal temperature variations causing performance changes on power supplies, magnets, etc.; and (3) prototyping and updating sophisticated optimization and controls algorithms. The Twinac framework will enable sharing and simplified deployment of modeled components and control algorithms at all facilities. With an inter-facility team to build and support the Twinac framework, it will be easy to publish and try out the latest advancements at one’s own facility.

Miceli, Tia [Fermilab]↗
NASA NTRS1988

The need for a comprehensive expert system development methodology

In a traditional software development environment, the introduction of standardized approaches has led to higher quality, maintainable products on the technical side and greater visibility into the status of the effort on the management side. This study examined expert system development to determine whether it differed enough from traditional systems to warrant a reevaluation of current software development methodologies. Its purpose was to identify areas of similarity with traditional software development and areas requiring tailoring to the unique needs of expert systems. A second purpose was to determine whether existing expert system development methodologies meet the needs of expert system development, management, and maintenance personnel. The study consisted of a literature search and personal interviews. It was determined that existing methodologies and approaches to developing expert systems are not comprehensive nor are they easily applied, especially to cradle to grave system development. As a result, requirements were derived for an expert system development methodology and an initial annotated outline derived for such a methodology.

Baumert, John↗
NASA NTRS2004

Agent Architecture for Aviation Data Integration System

This paper describes the proposed agent-based architecture of the Aviation Data Integration System (ADIS). ADIS is a software system that provides integrated heterogeneous data to support aviation problem-solving activities. Examples of aviation problem-solving activities include engineering troubleshooting, incident and accident investigation, routine flight operations monitoring, safety assessment, maintenance procedure debugging, and training assessment. A wide variety of information is typically referenced when engaging in these activities. Some of this information includes flight recorder data, Automatic Terminal Information Service (ATIS) reports, Jeppesen charts, weather data, air traffic control information, safety reports, and runway visual range data. Such wide-ranging information cannot be found in any single unified information source. Therefore, this information must be actively collected, assembled, and presented in a manner that supports the users problem-solving activities. This information integration task is non-trivial and presents a variety of technical challenges. ADIS has been developed to do this task and it permits integration of weather, RVR, radar data, and Jeppesen charts with flight data. ADIS has been implemented and used by several airlines FOQA teams. The initial feedback from airlines is that such a system is very useful in FOQA analysis. Based on the feedback from the initial deployment, we are developing a new version of the system that would make further progress in achieving following goals of our project.

Kulkarni, Deepak↗
NASA NTRS2006

Daily Planet Redesign: eZ Publish Web Content Management Implementation

This viewgraph presentation reviews the process of the redesign of the Daily . Planet news letter as a content management implementation project. This is a site that is an internal news site that acts as a communication vehicle for a large volume of content. The Objectives for the site redesign was: (1) Clean visual design, (2) Facilitation of publication processes, (3) More efficient maintenance mode, (4) Automated publishing to internal portal, (5) Better navigation through improved site IA, (6) Archiving and retrieval functionality, (7) Back to basics on fundamental business goals. The CM is a process not a software package

web content management↗
NASA NTRS2004

Software for Automated Testing of Mission-Control Displays

MCC Display Cert Tool is a set of software tools for automated testing of computerterminal displays in spacecraft mission-control centers, including those of the space shuttle and the International Space Station. This software makes it possible to perform tests that are more thorough, take less time, and are less likely to lead to erroneous results, relative to tests performed manually. This software enables comparison of two sets of displays to report command and telemetry differences, generates test scripts for verifying telemetry and commands, and generates a documentary record containing display information, including version and corrective-maintenance data. At the time of reporting the information for this article, work was continuing to add a capability for validation of display parameters against a reconfiguration file.

OHagan, Brian↗
NASA NTRS2002

The Use of Probabilistic Methods to Evaluate the Systems Impact of Component Design Improvements on Large Turbofan Engines

Probabilistic Structural Analysis (PSA) is now commonly used for predicting the distribution of time/cycles to failure of turbine blades and other engine components. These distributions are typically based on fatigue/fracture and creep failure modes of these components. Additionally, reliability analysis is used for taking test data related to particular failure modes and calculating failure rate distributions of electronic and electromechanical components. How can these individual failure time distributions of structural, electronic and electromechanical component failure modes be effectively combined into a top level model for overall system evaluation of component upgrades, changes in maintenance intervals, or line replaceable unit (LRU) redesign? This paper shows an example of how various probabilistic failure predictions for turbine engine components can be evaluated and combined to show their effect on overall engine performance. A generic model of a turbofan engine was modeled using various Probabilistic Risk Assessment (PRA) tools (Quantitative Risk Assessment Software (QRAS) etc.). Hypothetical PSA results for a number of structural components along with mitigation factors that would restrict the failure mode from propagating to a Loss of Mission (LOM) failure were used in the models. The output of this program includes an overall failure distribution for LOM of the system. The rank and contribution to the overall Mission Success (MS) is also given for each failure mode and each subsystem. This application methodology demonstrates the effectiveness of PRA for assessing the performance of large turbine engines. Additionally, the effects of system changes and upgrades, the application of different maintenance intervals, inclusion of new sensor detection of faults and other upgrades were evaluated in determining overall turbine engine reliability.

Packard, Michael H.↗
NASA NTRS1991

Linking medical records to an expert system

This presentation will be done using the IMR-Entry (Intelligent Medical Record Entry) system. IMR-Entry is a software program developed as a front-end to our diagnostic consultant software MEDAS (Medical Emergency Decision Assistance System). MEDAS (the Medical Emergency Diagnostic Assistance System) is a diagnostic consultant system using a multimembership Bayesian design for its inference engine and relational database technology for its knowledge base maintenance. Research on MEDAS began at the University of Southern California and the Institute of Critical Care in the mid 1970's with support from NASA and NSF. The MEDAS project moved to Chicago in 1982; its current progress is due to collaboration between Illinois Institute of Technology, The Chicago Medical School, Lake Forest College and NASA at KSC. Since the purpose of an expert system is to derive a hypothesis, its communication vocabulary is limited to features used by its knowledge base. The development of a comprehensive problem based medical record entry system which could handshake with an expert system while creating an electronic medical record at the same time was studied. IMR-E is a computer based patient record that serves as a front end to the expert system MEDAS. IMR-E is a graphically oriented comprehensive medical record. The programs major components are demonstrated.

Naeymi-Rad, Frank↗
NASA NTRS1993

FASTER - A tool for DSN forecasting and scheduling

FASTER (Forecasting And Scheduling Tool for Earth-based Resources) is a suite of tools designed for forecasting and scheduling JPL's Deep Space Network (DSN). The DSN is a set of antennas and other associated resources that must be scheduled for satellite communications, astronomy, maintenance, and testing. FASTER consists of MS-Windows based programs that replace two existing programs (RALPH and PC4CAST). FASTER was designed to be more flexible, maintainable, and user friendly. FASTER makes heavy use of commercial software to allow for customization by users. FASTER implements scheduling as a two pass process: the first pass calculates a predictive profile of resource utilization; the second pass uses this information to calculate a cost function used in a dynamic programming optimization step. This information allows the scheduler to 'look ahead' at activities that are not as yet scheduled. FASTER has succeeded in allowing wider access to data and tools, reducing the amount of effort expended and increasing the quality of analysis.

Werntz, David↗
NASA NTRS1993

FASTER -- A Tool for DSN Forecasting and Scheduling

FASTER (Forecasting And Scheduling Tool for Earth-based Resources) is a suite of tools designed for forecasting and scheduling of JPL's DSN. The DSN is a set of antennas and other associated resources that must be scheduled for satellite communications, astronomy, maintenance, and testing. FASTER is a MS-Windows based program that replaces two existing programs (RALPH and PC4CAST). FASTER was designed to be more flexible, maintainable, and user friendly. FASTER makes heavy use of commercial software to allow for customization by users. FASTER implements scheduling as a two pass process: the first pass calculates a predictive profile of resource utilization; the second pass uses this information to calculate a cost function used in a dynamic programming optimization step. This information allows the scheduler to "look ahead" at activities that are not as yet scheduled. FASTER has succeeded in allowing wider access to data and tools, reducing the amount of effort expended and increasing the quality of analysis.

forecasting↗
NASA NTRS2012

Automated Performance Characterization of DSN System Frequency Stability Using Spacecraft Tracking Data

This software provides an automated capability to measure and qualify the frequency stability performance of the Deep Space Network (DSN) ground system, using daily spacecraft tracking data. The results help to verify if the DSN performance is meeting its specification, therefore ensuring commitments to flight missions; in particular, the radio science investigations. The rich set of data also helps the DSN Operations and Maintenance team to identify the trends and patterns, allowing them to identify the antennas of lower performance and implement corrective action in a timely manner. Unlike the traditional approach where the performance can only be obtained from special calibration sessions that are both time-consuming and require manual setup, the new method taps into the daily spacecraft tracking data. This new approach significantly increases the amount of data available for analysis, roughly by two orders of magnitude, making it possible to conduct trend analysis with good confidence. The software is built with automation in mind for end-to-end processing. From the inputs gathering to computation analysis and later data visualization of the results, all steps are done automatically, making the data production at near zero cost. This allows the limited engineering resource to focus on high-level assessment and to follow up with the exceptions/deviations. To make it possible to process the continual stream of daily incoming data without much effort, and to understand the results quickly, the processing needs to be automated and the data summarized at a high level. Special attention needs to be given to data gathering, input validation, handling anomalous conditions, computation, and presenting the results in a visual form that makes it easy to spot items of exception/ deviation so that further analysis can be directed and corrective actions followed.

Pham, Timothy T.↗
NASA NTRS2012

Automated Performance Characterization of DSN System Frequency Stability Using Spacecraft Tracking Data

This software provides an automated capability to measure and qualify the frequency stability performance of the Deep Space Network (DSN) ground system, using daily spacecraft tracking data. The results help to verify if the DSN performance is meeting its specification, therefore ensuring commitments to flight missions; in particular, the radio science investigations. The rich set of data also helps the DSN Operations and Maintenance team to identify the trends and patterns, allowing them to identify the antennas of lower performance and implement corrective action in a timely manner. Unlike the traditional approach where the performance can only be obtained from special calibration sessions that are both time-consuming and require manual setup, the new method taps into the daily spacecraft tracking data. This new approach significantly increases the amount of data available for analysis, roughly by two orders of magnitude, making it possible to conduct trend analysis with good confidence. The software is built with automation in mind for end-to-end processing. From the inputs gathering to computation analysis and later data visualization of the results, all steps are done automatically, making the data production at near zero cost. This allows the limited engineering resource to focus on high-level assessment and to follow up with the exceptions/deviations. To make it possible to process the continual stream of daily incoming data without much effort, and to understand the results quickly, the processing needs to be automated and the data summarized at a high level. Special attention needs to be given to data gathering, input validation, handling anomalous conditions, computation, and presenting the results in a visual form that makes it easy to spot items of exception/deviation so that further analysis can be directed and corrective actions followed.

Pham, Timothy T.↗
NASA NTRS1996

Air Quality Monitor

The Stak-Tracker CEM (Continuous Emission Monitor) Gas Analyzer is an air quality monitor capable of separating the various gases in a bulk exhaust stream and determining the amounts of individual gases present within the stream. The monitor is produced by GE Reuter- Stokes, a subsidiary of GE Corporate Research & Development Center. The Stak-Tracker uses a Langley Research Center software package which measures the concentration of a target gas by determining the degree to which molecules of that gas absorb an infrared beam. The system is environmental-friendly, fast and has relatively low installation and maintenance costs. It is applicable to gas turbines and various industries including glass, paper and cement.

Source record↗
NASA NTRS2003

Constraint Maintenance with Preferences and Underlying Flexible Solution

This paper describes an aspect of the constraint reasoning mechanism. that is part of a ground planning system slated to be used for the Mars Exploration Rovers mission, where two rovers are scheduled to land on Mars in January of 2003. The planning system combines manual planning software from JPL with an automatic planning/scheduling system from NASA Ames Research Center, and is designed to be used in a mixed-initiative mode. Among other things, this means that after a plan has been produced, the human operator can perform extensive modifications under the supervision of the automated. system. For each modification to an activity, the automated system must adjust other activities as needed to ensure that constraints continue to be satisfied. Thus, the system must accommodate change in an interactive setting. Performance is of critical importance for interactive use. This is achieved by maintaining an underlying flexible solution to the temporal constraints, while the system presents a fixed schedule to the user. Adjustments are then a matter of constraint propagation rather than completely re-solving the problem. However, this begs the important question of which fixed schedule (among the ones sanctioned by the underlying flexible solution) should be presented to the user.Our approach uses least-change and other preferences as a prism through which the user views the flexible solution.

Bresina, John↗
DOE OSTI2025

COG Software Architecture Design Description Document

This COG Software Architecture Design Description Document describes the organization and functionality of the COG Multiparticle Monte Carlo Transport Code for radiation shielding and criticality calculations, at a level of detail suitable for guiding a new code developer in the maintenance and enhancement of COG. The intended audience also includes managers and scientists and engineers who wish to have a general knowledge of how the code works. This Document is not intended for end-users.

61 RADIATION PROTECTION AND DOSIMETRY↗
NASA NTRS2008

Challenges and Demands on Automated Software Revision

In the past three decades, automated program verification has undoubtedly been one of the most successful contributions of formal methods to software development. However, when verification of a program against a logical specification discovers bugs in the program, manual manipulation of the program is needed in order to repair it. Thus, in the face of existence of numerous unverified and un- certified legacy software in virtually any organization, tools that enable engineers to automatically verify and subsequently fix existing programs are highly desirable. In addition, since requirements of software systems often evolve during the software life cycle, the issue of incomplete specification has become a customary fact in many design and development teams. Thus, automated techniques that revise existing programs according to new specifications are of great assistance to designers, developers, and maintenance engineers. As a result, incorporating program synthesis techniques where an algorithm generates a program, that is correct-by-construction, seems to be a necessity. The notion of manual program repair described above turns out to be even more complex when programs are integrated with large collections of sensors and actuators in hostile physical environments in the so-called cyber-physical systems. When such systems are safety/mission- critical (e.g., in avionics systems), it is essential that the system reacts to physical events such as faults, delays, signals, attacks, etc, so that the system specification is not violated. In fact, since it is impossible to anticipate all possible such physical events at design time, it is highly desirable to have automated techniques that revise programs with respect to newly identified physical events according to the system specification.

Bonakdarpour, Borzoo↗
NASA NTRS2001

A Software Architecture for Intelligent Synthesis Environments

The NASA's Intelligent Synthesis Environment (ISE) program is a grand attempt to develop a system to transform the way complex artifacts are engineered. This paper discusses a "middleware" architecture for enabling the development of ISE. Desirable elements of such an Intelligent Synthesis Architecture (ISA) include remote invocation; plug-and-play applications; scripting of applications; management of design artifacts, tools, and artifact and tool attributes; common system services; system management; and systematic enforcement of policies. This paper argues that the ISA extend conventional distributed object technology (DOT) such as CORBA and Product Data Managers with flexible repositories of product and tool annotations and "plug-and-play" mechanisms for inserting "ility" or orthogonal concerns into the system. I describe the Object Infrastructure Framework, an Aspect Oriented Programming (AOP) environment for developing distributed systems that provides utility insertion and enables consistent annotation maintenance. This technology can be used to enforce policies such as maintaining the annotations of artifacts, particularly the provenance and access control rules of artifacts-, performing automatic datatype transformations between representations; supplying alternative servers of the same service; reporting on the status of jobs and the system; conveying privileges throughout an application; supporting long-lived transactions; maintaining version consistency; and providing software redundancy and mobility.

Filman, Robert E.↗