Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “corrective actions plan”

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 73 records · Page 4

Operational complexities of real tether systems in space

Some of the major operational concerns that have to be addressed in planning a real tether mission, such as the TTS-1 mission, which is due to fly on the Space Shuttle in the early 1990's, are discussed. Specifically, several operational hazards, such as the tether reel overtorque and the loss of tether system control, are considered from the viewpoint of flight crew, who must be able to detect the presence of a problem and to determine the corrective action to be taken. Various safety measures are discussed.

Hoffman, Jeffrey A.↗

Predictive sufficiency and the use of stored internal state

In all embedded computing systems, some delay exists between sensing and acting. By choosing an action based on sensed data, a system is essentially predicting that there will be no significant changes in the world during this delay. However, the dynamic and uncertain nature of the real world can make these predictions incorrect, and thus, a system may execute inappropriate actions. Making systems more reactive by decreasing the gap between sensing and action leaves less time for predictions to err, but still provides no principled assurance that they will be correct. Using the concept of predictive sufficiency described in this paper, a system can prove that its predictions are valid, and that it will never execute inappropriate actions. In the context of our CIRCA system, we also show how predictive sufficiency allows a system to guarantee worst-case response times to changes in its environment. Using predictive sufficiency, CIRCA is able to build real-time reactive control plans which provide a sound basis for performance guarantees that are unavailable with other reactive systems.

Musliner, David J.↗

Hydrogen Fire in a Storage Vessel

On October 23, 2007, the operations team began a procedure to sample the Liquid Hydrogen (LH2) storage vessels ("tanks"), and associated transfer system. This procedure was being performed to determine the conditions within the system, and if necessary, to purge the system of any excess Gaseous Hydrogen (GH2) in preparation for reactivation of the system. The system had not been used since 2003. The LH2 storage system contains two (2) spherical pressure vessels of 225,000 gallons in volume, with a maximum working pressure (MAWP) of 50 psig. Eight inch transfer piping connects them to the usage point. Operations began with activation of the burnstack for the LH2 storage area. Pneumatic (GN2) systems in the storage area were then activated and checked. Pressurization of storage tank number 1 with gaseous nitrogen (GN2) was initiated, with a target pressure of 10 psig, at which point samples were planned to be taken. At 5 psig, a loud noise was heard in the upper area of tank number 2. Smoke was seen exiting the burnstack and from the insulation on vent lines for both tanks. At this time tank number 1 was vented and the pressurization system was secured. The mishap resulted in physical damage to both storage tanks, as well as to some of the piping for both tanks. Corrective action included repair of the damaged hardware by a qualified contractor. Preventive action included documented organizational policy and procedures for establishing standby and mothball conditions for facilities and equipment, including provisions as detailed in the investigation report recommendations: Recommendation 1: The using organization should define necessary activities in order to place hydrogen systems in long term periods of inactivity. The defined activities should address requirements for rendering inert, isolation (i.e., physical disconnect, double block and bleed, etc.) and periodic monitoring. Recommendation 2: The using organization should develop a process to periodically monitor hazardous systems for proper configuration (i.e., a daily/weekly/monthly check sheet to verify critical purges are active).

Hester, Zena M.↗

Space shuttle maintenance program planning document

A means for developing a space shuttle maintenance program which will be acceptable to the development centers, the operators (KSC and AF), and the manufacturer is presented. The general organization and decision processes for determining the essential scheduled maintenance requirements for the space shuttle orbiter are outlined. The development of initial scheduled maintenance programs is discussed. The remaining maintenance, that is non-scheduled or non-routine maintenance, is directed by the findings of the scheduled maintenance program and the normal operation of the shuttle. The remaining maintenance consists of maintenance actions to correct discrepancies noted during scheduled maintenance tasks, nonscheduled maintenance, normal operation, or condition monitoring.

Brown, D. V.↗

StarPlan: A model-based diagnostic system for spacecraft

The Sunnyvale Division of Ford Aerospace created a model-based reasoning capability for diagnosing faults in space systems. The approach employs reasoning about a model of the domain (as it is designed to operate) to explain differences between expected and actual telemetry; i.e., to identify the root cause of the discrepancy (at an appropriate level of detail) and determine necessary corrective action. A development environment, named Paragon, was implemented to support both model-building and reasoning. The major benefit of the model-based approach is the capability for the intelligent system to handle faults that were not anticipated by a human expert. The feasibility of this approach for diagnosing problems in a spacecraft was demonstrated in a prototype system, named StarPlan. Reasoning modules within StarPlan detect anomalous telemetry, establish goals for returning the telemetry to nominal values, and create a command plan for attaining the goals. Before commands are implemented, their effects are simulated to assure convergence toward the goal. After the commands are issued, the telemetry is monitored to assure that the plan is successful. These features of StarPlan, along with associated concerns, issues and future directions, are discussed.

Heher, Dennis↗

Robot learning and error correction

A model of robot learning is described that associates previously unknown perceptions with the sensed known consequences of robot actions. For these actions, both the categories of outcomes and the corresponding sensory patterns are incorporated in a knowledge base by the system designer. Thus the robot is able to predict the outcome of an action and compare the expectation with the experience. New knowledge about what to expect in the world may then be incorporated by the robot in a pre-existing structure whether it detects accordance or discrepancy between a predicted consequence and experience. Errors committed during plan execution are detected by the same type of comparison process and learning may be applied to avoiding the errors.

Friedman, L.↗

Usability of an Updated Version of the Supplemental Data Service Provider-Consolidated Dashboard for Supporting Uncrewed Aircraft System Traffic Management

The Supplemental Data Service Provider-Consolidated Dashboard (SDSP-CD) is a preflight planning user interface (UI) that serves to aid operators when drafting routes for small uncrewed aircraft systems (sUASs). The primary function of the SDSP-CD is to identify hazards that an sUAS may encounter along a proposed flight path and assess the severity of these risks. A usability study was conducted on an updated version of the SDSP-CD to determine if the most recent iterations made to the system improved objective performance and subjective user experience. There are two main components of the SDSP-CD interface: (1) the dashboard and (2) the interactive map. The dashboard provides users with hazard and vehicle limitations for each sUAS in their fleet while the map contains a graphical representation of each vehicle’s route, hazard details, and geographic information. A series of preflight risk-assessment questions and tasks were developed to examine how participants interact with the updated version of the SDSP-CD. Additionally, a new service that measures vertiport congestion was developed and included as one of the services that was tested. In the present study, participants were trained to use the SDSP-CD and then completed two simulated scenarios during which they performed a variety of tasks, responded to questions, and completed surveys. The two scenarios developed for the present study were the Package Delivery and Hurricane Preparation scenarios. The Package Delivery scenario involved a fleet of four sUASs delivering low-stakes items (e.g., lunches and snacks) to people in a fictitious city. The Hurricane Preparation scenario involved a fleet of 11 sUASs delivering a range of supplies (from medicine to boardgames) to employees stranded at an office park due to road closures caused by an impending hurricane. Participants assumed the role of a fleet manager during both scenarios and were responsible for managing the sUASs in their fleet. Questions included those with objectively correct responses, open-ended strategy responses, and subjective user experience feedback. It was found that participants were largely successful at using the SDSP-CD interface to answer questions with objectively correct responses. Additionally, participants were able to use reasoning and logic based on the information available in the SDSP-CD to determine the cause of various risks and what actions they would consider taking. Finally, although participants reported that there were elements of the UI that could be improved, overall feedback pertaining to user experience suggested that the SDSP-CD concept is viable.

usability testing↗

Integrating Theory and Practice: Applying the Quality Improvement Paradigm to Product Line Engineering

My assertion is that not only are product lines a relevant research topic, but that the tools used by empirical software engineering researchers can address observed practical problems. Our experience at NASA has been there are often externally proposed solutions available, but that we have had difficulties applying them in our particular context. We have also focused on return on investment issues when evaluating product lines, and while these are important, one can not attain objective data on success or failure until several applications from a product family have been deployed. The use of the Quality Improvement Paradigm (QIP) can address these issues: (1) Planning an adoption path from an organization's current state to a product line approach; (2) Constructing a development process to fit the organization's adoption path; (3) Evaluation of product line development processes as the project is being developed. The QIP consists of the following six steps: (1) Characterize the project and its environment; (2) Set quantifiable goals for successful project performance; (3) Choose the appropriate process models, supporting methods, and tools for the project; (4) Execute the process, analyze interim results, and provide real-time feedback for corrective action; (5) Analyze the results of completed projects and recommend improvements; and (6) Package the lessons learned as updated and refined process models. A figure shows the QIP in detail. The iterative nature of the QIP supports an incremental development approach to product lines, and the project learning and feedback provide the necessary early evaluations.

Stark, Michael↗

AEGIS: Autonomous Entity Global Intelligence System for Urban Air Mobility

This paper presents a global intelligence system that synthesizes aerial vehicles’ real-time physical data, planned actions, and historical behavior into engineered data frames representing the collective state of the airspace and suitable for efficient machine learning consumption. These data frames are then learnt by a deep neural net to build a prediction model that estimates the expected evolution path of the current state, thereby identifying potential future conflicts. This approach lends itself to an automated early warning system that the aerial vehicles can implement onboard with a suitable edge computing module more efficiently and effectively than non-AI methods, and eventually take preventive or corrective measures towards self/collaborative resolution of the issues. Contrary to a centralized early warning system where all vehicles’ task-space eventually converges to a global optimum state, the presented distributed global intelligence system brings in a balance between local utility functions of each vehicle and the global operating framework. This contributes to effectively handle the potential massive scaling in urban air mobility in the near future.

Artificial Intelligence↗

Analysis of Improved Navigation Data for NASA Near Space Network (NSN) Direct-to-Earth (DTE) Ground Stations

Spacecraft navigation is a complex concept that requires a collaboration between network entities and constant corrective action to be successful in the highly variable environment. NASA’s Near Space Network (NSN), Direct-to-Earth (DTE) ground station team is constantly exploring methods to provide better service to NASA spacecraft, including providing radiometric tracking data, subject to cost constraints. Navigation teams, such as the Goddard Space Flight Center (GSFC) Flight Dynamics Facility (FDF), use the tracking data to perform orbit determination to assess where a spacecraft has been, identify where a spacecraft is now, and predict where a spacecraft will be in the future. As NASA plans for more missions beyond low Earth orbit (LEO), there is a need for improved navigation performance which can be directly achieved through improvements in the radiometric tracking data. NASA’s new DTE Ka-band antennas have finer autotrack angle resolution, and the availability of low-cost improved off-the-shelf ground station components, which are involved with producing navigation data. NASA formed a team to provide an assessment of the current NSN, DTE spacecraft navigation service (radiometric tracking) performance baseline with the end goal of defining needed future enhancements to meet the needs for spacecraft above LEO. The communications and navigation community is deriving new techniques in an effort to better service the navigation needs of spacecraft using ground station networks. This paper provides an overview Earth-orbit, direct-to-ground navigation techniques and performance, the development of specifications for new antennas, accuracy of data, spacecraft requirements, accuracy of orbit determination, history of challenges, and considerations for improvements. The discussions in this paper may assist ground station, spacecraft, and mission design teams advance navigation capabilities and more effectively meet requirements.

networks↗

Contractors Road Heavy Equipment Area (SWMU 055) 2022 Annual Groundwater Monitoring Report

This document presents a summary of activities completed at the Contractors Road Heavy Equipment (CRHE) Area, located at Kennedy Space Center (KSC), Florida, from June through December 2022. The activities conducted at the CRHE Area include: - Annual groundwater sampling activities associated with sitewide plume monitoring and Underground Injection Control (UIC) monitoring in the former bioremediation Interim Measures (IM) Hot Spot 1 (HS1) area; - Direct push technology (DPT) groundwater investigation; - Semiannual vapor intrusion (VI) evaluation activities. This facility is designated Solid Waste Management Unit (SWMU) Number 055 (SWMU 055) under KSC’s Resource Conservation and Recovery Act (RCRA) Corrective Action program. HydroGeoLogic, Inc. (HGL) prepared this report for the National Aeronautics and Space NASA) under contract number 80KSC019F0096/80KSC019D0012, Technical Directive-03. An Advance Data Package (ADP) presentation of the elements of this report received Team (KSCRT) agreement at the April 5, 2023, KSCRT meeting. The chlorinated volatile organic compound plume appears to be stable vertically and horizontally. Additional DPT groundwater sampling will be completed to support a remedial alternatives evaluation for potential means to expedite groundwater cleanup. There are per- and polyfluorinated alkyl substances in site groundwater, and assessment is planned in the future. Sub-slab soil gas monitoring results do not indicate any concerns with indoor vapor intrusion. Based on the 2022 annual groundwater sampling results, it is recommended that annual sampling continue to alternate with the wet and dry season, with the next sampling event planned for December 2023.

groundwater↗

Improving Operational Acceptability of Dynamic Weather Routes Through Analysis of Commonly Use Routings

The Dynamic Weather Routes (DWR) tool is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to find simple modifications to flight plan routes that can save significant flying time, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. Trials of the DWR system have shown that significant delay savings are possible. However, some DWR advised routes are also rejected by dispatchers or modified before being accepted. Similarly, of those sent by dispatchers to flight crews as proposed route change requests, many are not accepted by air traffic control, or are modified before implementation as Center route amendments. Such actions suggest that the operational acceptability of DWR advised route corrections could be improved, which may reduce workload and increase delay savings. This paper analyzes the historical usage of different flight routings, varying from simple waypoint pairs to lengthy strings of waypoints incorporating jet routes, in order to improve DWR route acceptability. An approach is developed that can be incorporated into DWR, advising routings with high historical usage and savings potential similar to that of the nominal DWR advisory. It is hypothesized that modifying a nominal DWR routing to one that is commonly used, and nearby, will result in more actual savings since common routings are generally familiar and operationally acceptable to air traffic control. The approach allows routing segments with high historical usage to be concatenated to form routes that meet all DWR constraints. The relevance of a route's historical usage to its acceptance by dispatchers and air traffic control is quantified by analyzing historical DWR data. Results indicate that while historical usage may be less of a concern to flight dispatchers accepting or rejecting DWR advised route corrections, it may be important to air traffic control acceptance of DWR routes.

dynamic weather routes↗

Improving Operational Acceptability of Dynamic Weather Routes (DWR) Through Analysis of Commonly Used Routings

The Dynamic Weather Routes (DWR) tool is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to find simple modifications to flight plan routes that can save significant flying time, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. Trials of the DWR system have shown that significant delay savings are possible. However, some DWR advised routes are also rejected by dispatchers or modified before being accepted. Similarly, of those sent by dispatchers to flight crews as proposed route change requests, many are not accepted by air traffic control, or are modified before implementation as Center route amendments. Such actions suggest that the operational acceptability of DWR advised route corrections could be improved, which may reduce workload and increase delay savings. This paper analyzes the historical usage of different flight routings, varying from simple waypoint pairs to lengthy strings of waypoints incorporating jet routes, in order to improve DWR route acceptability. An approach is developed that can be incorporated into DWR, advising routings with high historical usage and savings potential similar to that of the nominal DWR advisory. It is hypothesized that modifying a nominal DWR routing to one that is commonly used, and nearby, will result in more actual savings since common routings are generally familiar and operationally acceptable to air traffic control. The approach allows routing segments with high historical usage to be concatenated to form routes that meet all DWR constraints. The relevance of a routes historical usage to its acceptance by dispatchers and air traffic control is quantified by analyzing historical DWR data. Results indicate that while historical usage may be less of a concern to flight dispatchers accepting or rejecting DWR advised route corrections, it may be important to air traffic control acceptance of DWR routes.

Operational Acceptability↗

Quality Assurance Surveillance Tool Designed for SLS EM-1 Certificate of Flight Readiness

Exploration Mission-1 (EM-1) is an uncrewed mission that is launching on the Space Launch System (SLS) Block 1 vehicle. This is a critical flight test for the agency's human deep space exploration goals. Exploration Ground Systems (EGS) Quality (SA-F2) is responsible for providing Quality Assurance Surveillance Plans (QASPs) for NASA contracts and facilities. A QASP assures products and services are provided to EGS in accordance with the contract requirements. In order to encapsulate the multiple KSC Safety and Mission Assurance surveillance and audit activities that need to be accomplished specifically for EM-1 Certificate of Flight Reediness (CoFR), a QASP tool needed to be implemented. This tool would be able to intuitively track Work Authorization Documents (WADs) under development by Test Operations Support Contract (TOSC), reviewed and accepted WADs, Government Mandatory Inspection Points (GMIPs), Nonconformances (NCs), Material Review Board (MRB) Status, Corrective Actions, Alterations, Deviations, and Waivers for flight hardware and Ground Support Equipment (GSE). This would help ensure that all SLS EM-1 flight hardware and related GSE surveillances and requirements are being recognized and completed with zero constraints identified for the mission.

Morris, Patrick↗

Components Cleaning Facility, SWMU 030 Eastern High-Concentration Plume Area Implementation Work Plan Kennedy Space Center, Florida

This Implementation Work Plan (IWP) presents detailed design elements and coordination specifics to implement an air sparging (AS) Interim Measure (IM) to remediate groundwater at the Components Cleaning Facility (CCF), Eastern High Concentration Plume (HCP) Area located at Kennedy Space Center (KSC), Florida. The objective of the CCF East IM is to remediate groundwater where trichloroethene, cis-1,2-dichloroethene, and vinyl chloride concentrations exceed Florida Department of Environmental Protection Natural Attenuation Default Criteria (NADC) (identified as the HCP) via AS and to transition to monitored natural attenuation. CCF has been designated Solid Waste Management Unit 030 under KSC’s Resource Conservation and Recovery Act Corrective Action Program.

James Lloyd↗

Control Architecture for Robotic Agent Command and Sensing

Control Architecture for Robotic Agent Command and Sensing (CARACaS) is a recent product of a continuing effort to develop architectures for controlling either a single autonomous robotic vehicle or multiple cooperating but otherwise autonomous robotic vehicles. CARACaS is potentially applicable to diverse robotic systems that could include aircraft, spacecraft, ground vehicles, surface water vessels, and/or underwater vessels. CARACaS incudes an integral combination of three coupled agents: a dynamic planning engine, a behavior engine, and a perception engine. The perception and dynamic planning en - gines are also coupled with a memory in the form of a world model. CARACaS is intended to satisfy the need for two major capabilities essential for proper functioning of an autonomous robotic system: a capability for deterministic reaction to unanticipated occurrences and a capability for re-planning in the face of changing goals, conditions, or resources. The behavior engine incorporates the multi-agent control architecture, called CAMPOUT, described in An Architecture for Controlling Multiple Robots (NPO-30345), NASA Tech Briefs, Vol. 28, No. 11 (November 2004), page 65. CAMPOUT is used to develop behavior-composition and -coordination mechanisms. Real-time process algebra operators are used to compose a behavior network for any given mission scenario. These operators afford a capability for producing a formally correct kernel of behaviors that guarantee predictable performance. By use of a method based on multi-objective decision theory (MODT), recommendations from multiple behaviors are combined to form a set of control actions that represents their consensus. In this approach, all behaviors contribute simultaneously to the control of the robotic system in a cooperative rather than a competitive manner. This approach guarantees a solution that is good enough with respect to resolution of complex, possibly conflicting goals within the constraints of the mission to be accomplished by the vehicle(s).

Huntsberger, Terrance↗

Robonaut 2 and Watson: Cognitive Dexterity for Future Exploration

Future exploration missions will dictate a level of autonomy never before experienced in human spaceflight. Mission plans involving the uncrewed phases of complex human spacecraft in deep space will require a coordinated autonomous capability to be able to maintain the spacecraft when ground control is not available. One promising direction involves embedding intelligence into the system design both through the employment of state-of-the-art system engineering principles as well as through the creation of a cognitive network between a smart spacecraft or habitat and embodiments of cognitive agents. The work described here details efforts to integrate IBM's Watson and other cognitive computing services into NASA Johnson Space Center (JSC)'s Robonaut 2 (R2) anthropomorphic robot. This paper also discusses future directions this work will take. A cognitive spacecraft management system that is able to seamlessly collect data from subsystems, determine corrective actions, and provide commands to enable those actions is the end goal. These commands could be to embedded spacecraft systems or to a set of robotic assets that are tied into the cognitive system. An exciting collaboration with Woodside provides a promising Earth-bound testing analog, as controlling and maintaining not normally manned off-shore platforms have similar constraints to the space missions described.

Badger, Julia M.↗

Application of Fault Management Theory to the Quantitative Selection of a Launch Vehicle Abort Trigger Suite

The theory of System Health Management (SHM) and of its operational subset Fault Management (FM) states that FM is implemented as a "meta" control loop, known as an FM Control Loop (FMCL). The FMCL detects that all or part of a system is now failed, or in the future will fail (that is, cannot be controlled within acceptable limits to achieve its objectives), and takes a control action (a response) to return the system to a controllable state. In terms of control theory, the effectiveness of each FMCL is estimated based on its ability to correctly estimate the system state, and on the speed of its response to the current or impending failure effects. This paper describes how this theory has been successfully applied on the National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program to quantitatively estimate the effectiveness of proposed abort triggers so as to select the most effective suite to protect the astronauts from catastrophic failure of the SLS. The premise behind this process is to be able to quantitatively provide the value versus risk trade‐off for any given abort trigger, allowing decision makers to make more informed decisions. All current and planned crewed launch vehicles have some form of vehicle health management system integrated with an emergency launch abort system to ensure crew safety. While the design can vary, the underlying principle is the same: detect imminent catastrophic vehicle failure, initiate launch abort, and extract the crew to safety. Abort triggers are the detection mechanisms that identify that a catastrophic launch vehicle failure is occurring or is imminent and cause the initiation of a notification to the crew vehicle that the escape system must be activated. While ensuring that the abort triggers provide this function, designers must also ensure that the abort triggers do not signal that a catastrophic failure is imminent when in fact the launch vehicle can successfully achieve orbit. That is, the abort triggers must have low false negative rates to be sure that real crew‐threatening failures are detected, and also low false positive rates to ensure that the crew does not abort from non‐crew‐threatening launch vehicle behaviors. The analysis process described in this paper is a compilation of over six years of lessons learned and refinements from experiences developing abort triggers for NASA's Constellation Program (Ares I Project) and the SLS Program, as well as the simultaneous development of SHM/FM theory. The paper will describe the abort analysis concepts and process, developed in conjunction with SLS Safety and Mission Assurance (S&MA) to define a common set of mission phase, failure scenario, and Loss of Mission Environment (LOME) combinations upon which the SLS Loss of Mission (LOM) Probabilistic Risk Assessment (PRA) models are built. This abort analysis also requires strong coordination with the Multi‐Purpose Crew Vehicle (MPCV) and SLS Structures and Environments (STE) to formulate a series of abortability tables that encapsulate explosion dynamics over the ascent mission phase. The design and assessment of abort conditions and triggers to estimate their Loss of Crew (LOC) Benefits also requires in‐depth integration with other groups, including Avionics, Guidance, Navigation and Control(GN&C), the Crew Office, Mission Operations, and Ground Systems. The outputs of this analysis are a critical input to SLS S&MA's LOC PRA models. The process described here may well be the first full quantitative application of SHM/FM theory to the selection of a sensor suite for any aerospace system.

Lo, Yunnhon↗