Search NASA⌕ Search

SEARCH · Search NASA

Results for “controller information tool”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

A Risk Assessment Architecture for Enhanced Engine Operation

On very rare occasions, in-flight emergencies have occurred that required the pilot to utilize the aircraft's capabilities to the fullest extent possible, sometimes using actuators in ways for which they were not intended. For instance, when flight control has been lost due to damage to the hydraulic systems, pilots have had to use engine thrust to maneuver the plane to the ground and in for a landing. To assist the pilot in these situations, research is being performed to enhance the engine operation by making it more responsive or able to generate more thrust. Enabled by modification of the propulsion control, enhanced engine operation can increase the probability of a safe landing during an inflight emergency. However, enhanced engine operation introduces risk as the nominal control limits, such as those on shaft speed, temperature, and acceleration, are exceeded. Therefore, an on-line tool for quantifying this risk must be developed to ensure that the use of an enhanced control mode does not actually increase the overall danger to the aircraft. This paper describes an architecture for the implementation of this tool. It describes the type of data and algorithms required and the information flow, and how the risk based on engine component lifing and operability for enhanced operation is determined.

Litt, Jonathan S.↗
NASA NTRSDate not supplied

Managing the Digital Thread for Structural Applications With Fit for Purpose Materials

With the increased emphasis on reducing the cost and time to market of new materials, the need for analytical tools that enable the virtual design and optimization of materials throughout their processing - internal structure - property - performance envelope, along with the capturing and storing of the associated material and model information across its lifecycle, has become critical. This need is also fueled by the demands for higher efficiency in material testing; consistency, quality and traceability of data; product design; engineering analysis; as well as control of access to proprietary or sensitive information. Consequently, at NASA Glenn Research Center a robust information management system that manages the digital thread across the full material life (i.e., capture, analysis, maintenance, and dissemination of data) cycle directed at the design of ‘fit-for-purpose materials’ is under development. To this end the Application Table has been incorporated within NASA Glenn Research Center’s ICME Information Management framework within the ANSYS Granta MI tool. The Application Table provides a place where material and structural application information/requirements can be linked to marry the “design-the-material” (structural engineering) and the “design-with-material” (material science) paradigms and thereby enable application-driven design and optimization of materials and structures. In additional several associated toolsets, specifically: AIMAOS (Automated Information Management Across Organizations and Scales), Py MILab, and JARIMIS (Just A Rather Intelligent Material Interrogation System) are also under development to assist in the judicious automation of this process. AIMOAS offers users an interactive graphical user interface for connecting material information management systems with both commercial and in-house simulation tools at various length scales to enable such automation in the handoff across scales and maintenance of material digital twins and the digital thread. Py MILab, is an automatic framework for the capture, analysis, maintenance, and storage of material test data. Py MILab uses a modular approach for capturing raw data, analyzing the data, and storing the data in a database, interfaced by neutral file structures, to promote plug-and-play capabilities for various analysis types. Finally, JARIMIS is an expert system that integrates various materials informatics tools (e.g., MicroNet, Surrogate ML models, ANSYS Granta MI, etc.) to enable inverse design of materials and facilitate the application of machine learning (ML) and data science with human in the loop decision making to rapidly discover and optimize new materials.

Digital Transformation↗
NASA NTRS2003

Disaster Response and Preparedness Application: Emergency Environmental Response Tool (EERT)

In 2000, the National Aeronautics and Space Administration (NASA) Environmental Office at the John C. Stennis Space Center (SSC) developed an Environmental Geographic Information Systems (EGIS) database. NASA had previously developed a GIS database at SSC to assist in the NASA Environmental Office's management of the Center. This GIS became the basis for the NASA-wide EGIS project, which was proposed after the applicability of the SSC database was demonstrated. Since its completion, the SSC EGIS has aided the Environmental Office with noise pollution modeling, land cover assessment, wetlands delineation, environmental hazards mapping, and critical habitat delineation for protected species. At SSC, facility management and safety officers are responsible for ensuring the physical security of the facilities, staff, and equipment as well as for responding to environmental emergencies, such as accidental releases of hazardous materials. All phases of emergency management (planning, mitigation, preparedness, and response) depend on data reliability and system interoperability from a variety of sources to determine the size and scope of the emergency operation. Because geospatial data are now available for all NASA facilities, it was suggested that this data could be incorporated into a computerized management information program to assist facility managers. The idea was that the information system could improve both the effectiveness and the efficiency of managing and controlling actions associated with disaster, homeland security, and other activities. It was decided to use SSC as a pilot site to demonstrate the efficacy of having a baseline, computerized management information system that ultimately was referred to as the Emergency Environmental Response Tool (EERT).

Smoot, James↗
NASA NTRS2022

Application Table: A Bridge Connecting the Designing “With-The-Material” and “The-Material” Paradigms

Over the last few decades, advances in high-performance computing, new material characterization methods, and, more recently, an emphasis on integrated computational materials engineering (ICME) have been a catalyst for multiscale modeling and simulation-based design of materials and structures in the aerospace industry. In 2016 NASA sponsored a 2040 Vision study (which appeared in 2018) to define the potential 25-year future state required for integrated multiscale modeling of materials and systems (e.g., load-bearing structures) to accelerate the pace and reduce the expense of innovation in future aerospace and aeronautical systems. The study envisions a cyber-physical-social ecosystem comprised of experimentally verified and validated (V & V) computational models, tools, and techniques, along with the associated digital tapestry, that impacts the entire supply chain to enable cost-effective, rapid, and revolutionary design of “fit-for-purpose” materials, components, and systems. Consequently, the development of a robust information management system that incorporates (across the full life cycle) both experimental (real data) and virtual data resulting from the application of various simulation tools (at single or multiple length scales), therefore enabling the virtual design and optimization of materials throughout their processing – internal structure – property – performance envelope, has become critical. This need is also fueled by the demands for higher efficiency in material testing; consistency, quality, and traceability of data; product design; engineering analysis; as well as control of access to proprietary or sensitive information. This is particularly true when attempting to merge ICME practices with recent additive manufacturing technology which will enable production of the resulting 2040 Vision material and structural designs. At NASA Glenn Research Center we are exploring the future of material science through the use of novel characterization methodologies, high performance computing, and recently an emphasis on integrated computational materials engineering (ICME). Herein, recent efforts to incorporate an Application Table within NASA Glenn Research Center’s ICME Granta MI database is presented. The goal is to provide a place where material and structural application information/requirements can be linked so as to marry the “design the-material” and the “design-with-material” paradigms and thereby enable application-driven design and optimization of materials and structures by providing a central location that links material processing at various length scales to the application’s performance requirements. This paper discusses the specifics of this Application Table as well as best practices and key principles for the development of a robust materials information management system to enable the 2040 Vision integrated materials and structures ecosystem. Furthermore, it presents the intended role of the Application Table in the future of ICME design of “fit-for-purpose” materials, showing the need for a well-established framework that can successfully bridge the gap between the design “the material” and design “with-the-material” paradigms.

Materials↗
NASA NTRSDate not supplied

Application Table: A Bridge Connecting the Designing “With-the-Material” and “the-Material”

Over the last few decades, advances in high-performance computing, new material characterization methods, and, more recently, an emphasis on integrated computational materials engineering (ICME) have been a catalyst for multiscale modeling and simulation-based design of materials and structures in the aerospace industry. In 2016 NASA sponsored a 2040 Vision study (which appeared in 2018) to define the potential 25-year future state required for integrated multiscale modeling of materials and systems (e.g., load-bearing structures) to accelerate the pace and reduce the expense of innovation in future aerospace and aeronautical systems. The study envisions a cyber-physical-social ecosystem comprised of experimentally verified and validated (V & V) computational models, tools, and techniques, along with the associated digital tapestry, that impacts the entire supply chain to enable cost-effective, rapid, and revolutionary design of “fit-for-purpose” materials, components, and systems. Consequently, the development of a robust information management system that incorporates (across the full life cycle) both experimental (real data) and virtual data resulting from the application of various simulation tools (at single or multiple length scales), therefore enabling the virtual design and optimization of materials throughout their processing – internal structure – property – performance envelope, has become critical. This need is also fueled by the demands for higher efficiency in material testing; consistency, quality, and traceability of data; product design; engineering analysis; as well as control of access to proprietary or sensitive information. This is particularly true when attempting to merge ICME practices with recent additive manufacturing technology which will enable production of the resulting 2040 Vision material and structural designs. At NASA Glenn Research Center we are exploring the future of material science through the use of novel characterization methodologies, high performance computing, and recently an emphasis on integrated computational materials engineering (ICME). Herein, recent efforts to incorporate an Application Table within NASA Glenn Research Center’s ICME Granta MI database is presented. The goal is to provide a place where material and structural application information/requirements can be linked so as to marry the “design the-material” and the “design-with-material” paradigms and thereby enable application-driven design and optimization of materials and structures by providing a central location that links material processing at various length scales to the application’s performance requirements. This paper discusses the specifics of this Application Table as well as best practices and key principles for the development of a robust materials information management system to enable the 2040 Vision integrated materials and structures ecosystem. Furthermore, it presents the intended role of the Application Table in the future of ICME design of “fit-for-purpose” materials, showing the need for a well-established framework that can successfully bridge the gap between the design “the material” and design “with-the-material” paradigms.

Materials↗
NASA NTRSDate not supplied

Open-Hole Testing of Resin Infused Carbon Composite Laminates to Facilitate Damage Growth and Failure Analysis Tools for Structural Design

In manufacturing of carbon-fiber reinforced composite aircraft structures, resin infusion offers a highly repeatable process for manufacturing structural components with resin content control, low labor requirements, and complex curvatures. To further understand the structural capabilities of res-in infused composites (RIC), this study – as part of the NASA-led Hi-Rate Composite Aircraft Manufacturing project efforts – performed open hole tension (OHT) and open hole compression (OHC) testing on RIC laminates. This testing provides information on the damage morphology and growth characteristics of RICs, which fuels the development and evaluation of analysis tools for progressive damage growth and failure responses. X-ray computed tomography (XCT) was implemented on each OHC and OHT specimen prior to mechanical testing to identify preexisting damage and/or defects. Two OHT and OHC specimens were loaded monotonically to failure and an additional OHT and OHC specimen were loaded intermittently at defined conditions and XCT scanned after each run. From the data obtained in this study, damage mechanisms leading to failure were identified, damage morphology and size were assessed, and damage initiation and failure loads were measured.

HiCAM↗
NASA NTRS1983

Description of data base management activities

ARC's current and future data processing needs have been identified and defined. Requirements for improved data processing capabilities are listed: (1) Centralized control of system data files. Establish a DBA/data base administrator position with responsibility for management of the Centers numerous data bases; (2) Programmer tools to improve efficiency of performance; (3) Direct and timely access to information. Presently, the user submits query requests to the data processing department where they are prioritized with other queries and then batch processed using a report generator; (4) On line data entry. With the merger of the Dryden facility with ARC on line data entry, edit and updates have become mandatory for timely operation and reporting. A DBMS software package was purchased to meet the above requirements.

Source record↗
NASA NTRS1983

The NASA Software Management and Assurance Program

A committee of experienced managers representing each major NASA organization guides a major development effort which seeks to ensure the acquisition of economical and reliable software for more complex future programs. The primary, near-term development objectives of the NASA Software Management and Assurance Program are: (1) to provide the best management and technical guidance available; (2) to facilitate the use of proven tools, techniques, and information; and (3) to maintain a pool of highly qualified software personnel. The software development tasks addressed involve such problems as satellite end-to-end architecture and advanced aircraft guidance and control systems.

Hall, D. L.↗
NASA NTRS1986

Evaluation of reliability modeling tools for advanced fault tolerant systems

The Computer Aided Reliability Estimation (CARE III) and Automated Reliability Interactice Estimation System (ARIES 82) reliability tools for application to advanced fault tolerance aerospace systems were evaluated. To determine reliability modeling requirements, the evaluation focused on the Draper Laboratories' Advanced Information Processing System (AIPS) architecture as an example architecture for fault tolerance aerospace systems. Advantages and limitations were identified for each reliability evaluation tool. The CARE III program was designed primarily for analyzing ultrareliable flight control systems. The ARIES 82 program's primary use was to support university research and teaching. Both CARE III and ARIES 82 were not suited for determining the reliability of complex nodal networks of the type used to interconnect processing sites in the AIPS architecture. It was concluded that ARIES was not suitable for modeling advanced fault tolerant systems. It was further concluded that subject to some limitations (the difficulty in modeling systems with unpowered spare modules, systems where equipment maintenance must be considered, systems where failure depends on the sequence in which faults occurred, and systems where multiple faults greater than a double near coincident faults must be considered), CARE III is best suited for evaluating the reliability of advanced tolerant systems for air transport.

Baker, Robert↗
NASA NTRS1989

Theft of information in the take-grant protection model

Questions of information flow are in many ways more important than questions of access control, because the goal of many security policies is to thwart the unauthorized release of information, not merely the illicit obtaining of access rights to that information. The Take-Grant Protection Model is a theoretical tool for examining such issues because conditions necessary and sufficient for information to flow between two objects, and for rights to objects to be obtained or stolen, are known. These results are extended by examining the question of information flow from an object the owner of which is unwilling to release that information. Necessary and sufficient conditions for such theft of information to occur are derived, and bounds on the number of subjects that must take action for the theft to occur are presented. To emphasize the usefulness of these results, the security policies of complete isolation, transfer of rights with the cooperation of an owner, and transfer of information (but not rights) with the cooperation of the owner are presented; the last is used to model a simple reference monitor guarding a resource.

Bishop, Matt↗
NASA NTRS2000

New Human-Computer Interface Concepts for Mission Operations

The current climate of budget cuts has forced the space mission operations community to reconsider how it does business. Gone are the days of building one-of-kind control centers with teams of controllers working in shifts 24 hours per day, 7 days per week. Increasingly, automation is used to significantly reduce staffing needs. In some cases, missions are moving towards lights-out operations where the ground system is run semi-autonomously. On-call operators are brought in only to resolve anomalies. Some operations concepts also call for smaller operations teams to manage an entire family of spacecraft. In the not too distant future, a skeleton crew of full-time general knowledge operators will oversee the operations of large constellations of small spacecraft, while geographically distributed specialists will be assigned to emergency response teams based on their expertise. As the operations paradigms change, so too must the tools to support the mission operations team's tasks. Tools need to be built not only to automate routine tasks, but also to communicate varying types of information to the part-time, generalist, or on-call operators and specialists more effectively. Thus, the proper design of a system's user-system interface (USI) becomes even more importance than before. Also, because the users will be accessing these systems from various locations (e.g., control center, home, on the road) via different devices with varying display capabilities (e.g., workstations, home PCs, PDAS, pagers) over connections with various bandwidths (e.g., dial-up 56k, wireless 9.6k), the same software must have different USIs to support the different types of users, their equipment, and their environments. In other words, the software must now adapt to the needs of the users! This paper will focus on the needs and the challenges of designing USIs for mission operations. After providing a general discussion of these challenges, the paper will focus on the current efforts of creatin(y an effective USI for one specific suite of tools, SERS (The Spacecraft Emergency Response System), which has been built to enable lights-out operations. SERS is a Web-based collaborative environment that enables secure distributed fault management.

Fox, Jeffrey A.↗
NASA NTRS1997

Development of the Space Operations Incident Reporting Tool (SOIRT)

The space operations incident reporting tool (SOIRT) is an instrument used to record information about an anomaly occurring during flight which may have been due to insufficient and/or inappropriate application of human factors knowledge. We originally developed the SOIRT form after researching other incident reporting systems of this type. We modified the form after performing several in-house reviews and a pilot test to access usability. Finally, crew members from Space Shuttle flights participated in a usability test of the tool after their missions. Since the National Aeronautics and Space Administration (NASA) currently has no system for continuous collection of this type of information, the SOIRT was developed to report issues such as reach envelope constraints, control operation difficulties, and vision impairments. However, if the SOIRT were to become a formal NASA process, information from crew members could be collected in a database and made available to individuals responsible for improving in-flight safety and productivity. Potential benefits include documentation to justify the redesign or development of new equipment/systems, provide the mission planners with a method for identifying past incidents, justify the development of timelines and mission scenarios, and require the creation of more appropriate work/rest cycles.

Minton, Jacquie↗
NASA NTRS1999

Transitioning from Free-Flight to TRACON Airspace: The Ground Perspective of User-Preferred Descents

Free-flight is considered to play a major role in the future air traffic environment. Studies are underway addressing different concepts for free-flight and self separation in enroute airspace. One common opinion throughout the different concepts is that the airspace surrounding major airports, the Terminal Radar Approach CONtrol (TRACON) will not be a free flight area. This means that aircraft in this area are completely controlled by air traffic controllers, who may be supported by decision support system like the Center TRACON Automation System (CTAS). How the transition from the free-flight area (enroute airspace) to the terminal area will take place is currently unclear, This paper describes a study at NASA Ames Research Center addressing the perspective of air traffic controllers handling user-preferred (FMS-optimized) descent trajectories during this transition phase. Two major issues in enabling user preferred descents from the controllers' point of view are predictability and controllability. In an environment in which the air traffic services are highly responsive to user preferences controllers need to know, where and when aircraft will change their trajectory and they need to have appropriate means and procedures at hand to control the aircraft according to the overall traffic situation. Predictability shall be enhanced by: 1) Indicating airspace corridors for descending aircraft; 2) Modify the controller interface; 3) Using a ground based conflict probe; 4) Making use of downlinked intent information from the aircraft FMS; and 5) Requiring to fly pilots on user preferred trajectories coupled to the FMS in the lateral and vertical axis. Additional controllability shall be achieved by supporting the controllers with CTAS center tools: 1) Traffic Management Advisor (TMA); 2) Conflict Probing and Trial Planning (CP/TP); and 3) Enroute Descent Advisor (E/DA). The paper describes the general concept and the modifications to current systems required to enable the concept. It explains the experiment design and discusses the results with regard to controller acceptability and usability. Potential benefits and drawbacks of the overall concept are indicated.

Prevot, Thomas↗
NASA NTRS2011

Visual PEF Reader - VIPER

This software graphically displays all pertinent information from a Predicted Events File (PEF) using the Java Swing framework, which allows for multi-platform support. The PEF is hard to weed through when looking for specific information and it is a desire for the MRO (Mars Reconn aissance Orbiter) Mission Planning & Sequencing Team (MPST) to have a different way to visualize the data. This tool will provide the team with a visual way of reviewing and error-checking the sequence product. The front end of the tool contains much of the aesthetically appealing material for viewing. The time stamp is displayed in the top left corner, and highlighted details are displayed in the bottom left corner. The time bar stretches along the top of the window, and the rest of the space is allotted for blocks and step functions. A preferences window is used to control the layout of the sections along with the ability to choose color and size of the blocks. Double-clicking on a block will show information contained within the block. Zooming into a certain level will graphically display that information as an overlay on the block itself. Other functions include using hotkeys to navigate, an option to jump to a specific time, enabling a vertical line, and double-clicking to zoom in/out. The back end involves a configuration file that allows a more experienced user to pre-define the structure of a block, a single event, or a step function. The individual will have to determine what information is important within each block and what actually defines the beginning and end of a block. This gives the user much more flexibility in terms of what the tool is searching for. In addition to the configurability, all the settings in the preferences window are saved in the configuration file as well

Luo, Victor↗
NASA NTRS2017

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗
NASA NTRS2018

Utilizing Testing Frameworks for Launch Control Systems Continuous Integration

Command and control software is an integral part of the launch procedure. The most important part of this type of software is its ability to communicate well with the user and relay information in a correctly formatted way such that the user can understand the data. There is a tool that aides the communication between the different parts of the system, and effectively, the user. This instrument is capable of taking several complex values and ensuring that they are correctly sorted into their distinctive message values and distributed properly among the different facets of the system. This tool will easily translate and publish the data inside of messages in the system to something that is readable and understandable. The tool also allows for transmission of the recorded data to the user, effectively ensuring the communication between different components of the system. As well as keeping track of messages and ensuring that the information contained within each of them reaches the correct location, this tool has the ability to keep track of its own statistics and determine how many messages passed in were erroneous and how many were successfully transmitted. It is able to check and see what the total message failure count is when an invalid message is given, as well as the number of different messages and their respective types passed into the tool. This tool is of great value to the new Space Launch System (SLS). As such, the tool must be thoroughly tested with test cases that, although improbable, are possible, where the tool may not function properly. Testing an interface this complex is necessary to ensure mission safety and create unlikely scenarios where the tool would work as intended, and stretch its limits to test that even under the most uncommon conditions it would still continue to function. This software will be an important part of the control system for the newest spacecraft which will fly deeper into space than humans have ever travelled. It will fly beyond the moon, into deep space to Mars and perhaps set the groundwork for a manned mission even further to create more opportunities for interplanetary and even interstellar travel by humans. This mission relies heavily on software and hardware to ensure the safety of the humans that will be on board and therefore must be checked, exhausting each and every different situation, such that there is not a doubt surrounding the well-being of the humans aboard the rocket. That is why testing is such an important part of the mission. It provides evidence that the systems aboard the rocket and on the launch pad are safe.

Unit Testing↗
NASA NTRS1992

Coordinating complex problem-solving among distributed intelligent agents

A process-oriented control model is described for distributed problem solving. The model coordinates the transfer and manipulation of information across independent networked applications, both intelligent and conventional. The model was implemented using SOCIAL, a set of object-oriented tools for distributing computing. Complex sequences of distributed tasks are specified in terms of high level scripts. Scripts are executed by SOCIAL objects called Manager Agents, which realize an intelligent coordination model that routes individual tasks to suitable server applications across the network. These tools are illustrated in a prototype distributed system for decision support of ground operations for NASA's Space Shuttle fleet.

Adler, Richard M.↗
NASA NTRS2002

International Space Station (ISS) Nodes 2/3 Thermal Control System Overview and Design

The goals of this viewgraph presentation are to: (1) provide general International Space Station (ISS) Node 2 and 3 information; (2) give an overview of the ISS Thermal Control System (TCS) design, including details on the passive TCS and internal and external TCS; (3) give TCS components examples; and (4) describe the thermal and hydraulic analytical tools.

Clanton, Stephen↗