SEARCH · Engineering Papers

Results for “PERSONNEL”

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.

SourceResearch connectionFrom yearThrough year

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

At least 469 records · Page 26

All sources NASA NTRS DOE OSTI

NASA NTRS2013

Neural Network Back-Propagation Algorithm for Sensing Hypergols

Fast, continuous detection of a wide range of hazardous substances simultaneously is needed to achieve improved safety for personnel working with hypergolic fuels and oxidizers, as well as other hazardous substances, with a requirement for such detection systems to warn personnel immediately upon the sudden advent of hazardous conditions, with a high probability of detection and a low false alarm rate. The primary purpose of this software is to read the voltage outputs from voltage dividers containing carbon nano - tube sensors as a variable resistance leg, and to recognize quickly when a leak has occurred through recognizing that a generalized pattern change in resistivity of a carbon nanotube sensor has occurred upon exposure to dangerous substances, and, further, to identify quickly just what substance is present through detailed pattern recognition of the shape of the response provided by the carbon nanotube sensor.

Perotti, Jose↗

NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

NASA NTRS2013

NASA Technology Evaluation for Environmental Risk Mitigation Remediation Technology Collaboration Development

NASA is committed to finding solutions to agency cleanup problems that are better, cheaper, and more effective than the status quo. Unfortunately, some potential solutions involve innovative technologies for which NASA remediation managers may not have a high level of understanding or confidence. Since 2004, NASA's Stennis Space Center (SSC) in Mississippi has been pumping groundwater contaminated with trichloroethylene (TCE) and other halogenated volatile organic compounds (HVOC) from their cleanup location designated "Area G" through extraction wells to an aboveground treatment system. Over time, however, the effectiveness of this treatment strategy has diminished and an alternative approach is needed. In 2012, professionals from NASA's Principal Center for Technology Evaluation for Environmental Risk Mitigation (TEERM) introduced SSC managers to an innovative technology for enhancing the performance of SSC's existing pump and treat system. The technology, generally referred to as in situ chemical oxidation (ISCO), involves slowly and continuously injecting a strong but safe chemical oxidant into the groundwater. Treatment is enhanced by a "surfactant-type effect" which causes residual contamination from saturated soil to be released into the dissolved-phase where it can be readily oxidized. Any dissolved-phase contamination that was not oxidized can be collected by the extraction well network and treated aboveground. SSC was not familiar with the technology so to increase their confidence, TEERM identified a contractor who was willing to demonstrate their product and process at a significantly reduced price. An initial, small-scale demonstration of ISCO began at sse in March 2012 and completed in August 2012. This successful demonstration was followed by three larger-scale ISCO demonstrations between August and December 2012. The contractor's innovative Continuous Injection System (CIS) incorporated "green" and sustainable technologies and practices. A slow injection rate was maintained autonomously by the CIS, eliminating the need for multiple mobilizations of personnel and powered equipment. The CIS was calibrated to deliver only as much reagent as the formation would accept without "short circuiting", minimizing material waste. Public utility water pressure was used to mix, dilute, and inject the reagent. NASA personnel were trained to operate and maintain the system and remote monitoring and injection control capabilities were developed, further reducing the need for contractor mobilizations to the site. An integrated solar photovoltaic panel was used to power the control valves and web monitoring telemetry. SSC provided hydrogen peroxide for the process using their existing supplier for the aboveground pump and treat systems. The only consumable required from the contractor was their proprietary activator to catalyze SSC's peroxide.

Romeo, James↗

NASA NTRS2013

Wireless Integrated Microelectronic Vacuum Sensor System

NASA Stennis Space Center's (SSC's) large rocket engine test facility requires the use of liquid propellants, including the use of cryogenic fluids like liquid hydrogen as fuel, and liquid oxygen as an oxidizer (gases which have been liquefied at very low temperatures). These fluids require special handling, storage, and transfer technology. The biggest problem associated with transferring cryogenic liquids is product loss due to heat transfer. Vacuum jacketed piping is specifically designed to maintain high thermal efficiency so that cryogenic liquids can be transferred with minimal heat transfer. A vacuum jacketed pipe is essentially two pipes in one. There is an inner carrier pipe, in which the cryogenic liquid is actually transferred, and an outer jacket pipe that supports and seals the vacuum insulation, forming the "vacuum jacket." The integrity of the vacuum jacketed transmission lines that transfer the cryogenic fluid from delivery barges to the test stand must be maintained prior to and during engine testing. To monitor the vacuum in these vacuum jacketed transmission lines, vacuum gauge readings are used. At SSC, vacuum gauge measurements are done on a manual rotation basis with two technicians, each using a handheld instrument. Manual collection of vacuum data is labor intensive and uses valuable personnel time. Additionally, there are times when personnel cannot collect the data in a timely fashion (i.e., when a leak is detected, measurements must be taken more often). Additionally, distribution of this data to all interested parties can be cumbersome. To simplify the vacuum-gauge data collection process, automate the data collection, and decrease the labor costs associated with acquiring these measurements, an automated system that monitors the existing gauges was developed by Invocon, Inc. For this project, Invocon developed a Wireless Integrated Microelectronic Vacuum Sensor System (WIMVSS) that provides the ability to gather vacuum-gauge measurements automatically and wirelessly, in near-real time - using a low-maintenance, lowpower sensor mesh network. The WIMVSS operates by using a self-configuring mesh network of wireless sensor units. Mesh networking is a type of networking where each sensor or node can capture and disseminate its own data, but also serve as a relay to receive and transmit data from other sensors. Each sensor node can synchronize with adjacent sensors, and propagate data from one sensor to the next, until the destination is reached. In this case, the destination is a Network Interface Unit (NIU). The WIMVSS sensors are mounted on the existing vacuum gauges. Information gathered by the sensors is sent to the NIU. Because of the mesh networking, if a sensor cannot directly send the data to the NIU, it can be propagated through the network of sensors. The NIU requires antenna access to the sensor units, AC power, and an Ethernet connection. The NIU bridges the sensor network to a WIMVSS server via an Ethernet connection. The server is configured with a database, a Web server, and proprietary interface software that makes it possible for the vacuum measurements from vacuum jacketed fluid lines to be saved, retrieved, and then displayed from any Web-enabled PC that has access to the Internet. Authorized users can then simply access the data from any PC with Internet connection. Commands can also be sent directly from the Web interface for control and maintenance of the sensor network. The technology enabled by the WIMVSS decreases labor required for gathering vacuum measurements, increases access to vacuum data by making it available on any computer with access to the Internet, increases the frequency with which data points can be acquired for evaluating the system, and decreases the recurring cost of the sensors by using off-the-shelf components and integrating these with heritage vacuum gauges.

Krug, Eric↗

NASA NTRS2013

Alternative to Nitric Acid for Passivation of Stainless Steel Alloys

Corrosion is an extensive problem that affects the Department of Defense (DoD) and National Aeronautics and Space Administration (NASA). The deleterious effects of corrosion result in steep costs, asset downtime affecting mission readiness, and safety risks to personnel. Consequently, it is vital to reduce corrosion costs and risks in a sustainable manner. The DoD and NASA have numerous structures and equipment that are fabricated from stainless steel. The standard practice for protection of stainless steel is a process called passivation. Typical passivation procedures call for the use of nitric acid; however, there are a number of environmental, worker safety, and operational issues associated with its use. Citric acid offers a variety of benefits including increased safety for personnel, reduced environmental impact, and reduced operational cost. DoD and NASA agreed to collaborate to validate citric acid as an acceptable passivating agent for stainless steel. This paper details our investigation of prior work developing the citric acid passivation process, development of the test plan, optimization of the process for specific stainless steel alloys, ongoing and planned testing to elucidate the process' resistance to corrosion in comparison to nitric acid, and preliminary results.

Lewis, Pattie L.↗

NASA NTRS2014

Monitoring for Renal Stone Recurrence in Astronauts With History of Stone

After an initial stone episode persons are at increased risk for future stone formation. A systematic approach is required to monitor the efficacy of treatment and preventive measures, and to assess the risk of developing new stones. This is important for persons working in critical jobs or austere environments, such as astronauts. A literature review of the current standards of care for renal stone monitoring and imaging was done. Military and civil aviation standards were also reviewed, as well as the medical precedents from the space program. Additionally, a new, more effective, renal stone ultrasound protocol has been developed. Using this work, a monitoring algorithm was proposed that takes into consideration the unique mission and operational environment of spaceflight. The approach to imaging persons with history of renal stones varies widely in the literature. Imaging is often done yearly or biannually, which may be too long for mission critical personnel. In the proposed algorithm astronauts with a history of renal stone, who may be under consideration for assignment, are imaged by a detailed, physiciandriven, ultrasound protocol. Unassigned personnel are monitored by yearly ultrasound and urine studies. Any positive ultrasound study is then followed by low-dose renal computed tomography scan. Other criteria are also established. The proposed algorithm provides a balanced approach between efficacy and reduced radiation exposure for the monitoring of astronauts with a renal stone history. This may eventually allow a transition from a risk-averse, to a risk-modifying approach that can enable continued service of individuals with history of renal stone that have adequately controlled risk factors.

Reyes, David P.↗

NASA NTRS2012

Performance Data Errors in Air Carrier Operations: Causes and Countermeasures

Several airline accidents have occurred in recent years as the result of erroneous weight or performance data used to calculate V-speeds, flap/trim settings, required runway lengths, and/or required climb gradients. In this report we consider 4 recent studies of performance data error, report our own study of ASRS-reported incidents, and provide countermeasures that can reduce vulnerability to accidents caused by performance data errors. Performance data are generated through a lengthy process involving several employee groups and computer and/or paper-based systems. Although much of the airline indUStry 's concern has focused on errors pilots make in entering FMS data, we determined that errors occur at every stage of the process and that errors by ground personnel are probably at least as frequent and certainly as consequential as errors by pilots. Most of the errors we examined could in principle have been trapped by effective use of existing procedures or technology; however, the fact that they were not trapped anywhere indicates the need for better countermeasures. Existing procedures are often inadequately designed to mesh with the ways humans process information. Because procedures often do not take into account the ways in which information flows in actual flight ops and time pressures and interruptions experienced by pilots and ground personnel, vulnerability to error is greater. Some aspects of NextGen operations may exacerbate this vulnerability. We identify measures to reduce the number of errors and to help catch the errors that occur.

countermeasures↗

NASA NTRS2014

Native Fluorescence Detection Methods and Detectors for Naphthalene and/or Other Volatile Organic Compound Vapors

Naphthalene, benzene, toluene, xylene, and other volatile organic compounds have been identified as serious health hazards. This is especially true for personnel working with JP8 jet fuel and other fuels containing naphthalene as well as other hazardous volatile organic compounds (VOCs). Embodiments of the invention are directed to methods and apparatus for near-real-time in-situ detection and accumulated dose measurement of exposure to naphthalene vapor and other hazardous gaseous VOCs. The methods and apparatus employ excitation of fluorophors native or endogenous to compounds of interest using light sources emitting in the ultraviolet below 300 nm and measurement of native fluorescence emissions in distinct wavebands above the excitation wavelength. The apparatus of some embodiments are cell-phone-sized sensor/dosimeter "badges" to be worn by personnel potentially exposed to naphthalene or other hazardous VOCs. The badge sensor of some embodiments provides both real time detection and data logging of exposure to naphthalene or other VOCs of interest from which both instantaneous and accumulated dose can be determined. The badges employ a new native fluorescence based detection method to identify and differentiate VOCs. The particular focus of some embodiments are the detection and identification of naphthalene while other embodiments are directed to detection and identification of other VOCs like aromatic hydrocarbons such as benzene, toluene, and xylene.

Hug, William F.↗

NASA NTRS2013

U.S. Naval Observatory VLBI Analysis Center

This report summarizes the activities of the VLBI Analysis Center at the United States Naval Observatory for the 2012 calendar year. Over the course of the year, Analysis Center personnel continued analysis and timely submission of IVS-R4 databases for distribution to the IVS. During the 2012 calendar year, the USNO VLBI Analysis Center produced two VLBI global solutions designated as usn2012a and usn2012b. Earth orientation parameters (EOP) based on this solution and updated by the latest diurnal (IVS-R1 and IVS-R4) experiments were routinely submitted to the IVS. Sinex files based upon the bi-weekly 24-hour experiments were also submitted to the IVS. During the 2012 calendar year, Analysis Center personnel continued a program to use the Very Long Baseline Array (VLBA) operated by the NRAO for the purpose of measuring UT1-UTC. Routine daily 1-hour duration Intensive observations were initiated using the VLBA antennas at Pie Town, NM and Mauna Kea, HI. High-speed network connections to these two antennas are now routinely used for electronic transfer of VLBI data over the Internet to a USNO point of presence. A total of 270 VLBA Intensive experiments were observed and electronically transferred to and processed at USNO in 2012.

Boboltz, David A.↗

NASA NTRS2015

Minimum deltaV Burn Planning for the International Space Station Using a Hybrid Optimization Technique, Level 1

The International Space Station's (ISS) trajectory is coordinated and executed by the Trajectory Operations and Planning (TOPO) group at NASA's Johnson Space Center. TOPO group personnel routinely generate look-ahead trajectories for the ISS that incorporate translation burns needed to maintain its orbit over the next three to twelve months. The burns are modeled as in-plane, horizontal burns, and must meet operational trajectory constraints imposed by both NASA and the Russian Space Agency. In generating these trajectories, TOPO personnel must determine the number of burns to model, each burn's Time of Ignition (TIG), and magnitude (i.e. deltaV) that meet these constraints. The current process for targeting these burns is manually intensive, and does not take advantage of more modern techniques that can reduce the workload needed to find feasible burn solutions, i.e. solutions that simply meet the constraints, or provide optimal burn solutions that minimize the total DeltaV while simultaneously meeting the constraints. A two-level, hybrid optimization technique is proposed to find both feasible and globally optimal burn solutions for ISS trajectory planning. For optimal solutions, the technique breaks the optimization problem into two distinct sub-problems, one for choosing the optimal number of burns and each burn's optimal TIG, and the other for computing the minimum total deltaV burn solution that satisfies the trajectory constraints. Each of the two aforementioned levels uses a different optimization algorithm to solve one of the sub-problems, giving rise to a hybrid technique. Level 2, or the outer level, uses a genetic algorithm to select the number of burns and each burn's TIG. Level 1, or the inner level, uses the burn TIGs from Level 2 in a sequential quadratic programming (SQP) algorithm to compute a minimum total deltaV burn solution subject to the trajectory constraints. The total deltaV from Level 1 is then used as a fitness function by the genetic algorithm in Level 2 to select the number of burns and their TIGs for the next generation. In this manner, the two levels solve their respective sub-problems separately but collaboratively until a burn solution is found that globally minimizes the deltaV across the entire trajectory. Feasible solutions can also be found by simply using the SQP algorithm in Level 1 with a zero cost function. This paper discusses the formulation of the Level 1 sub-problem and the development of a prototype software tool to solve it. The Level 2 sub-problem will be discussed in a future work. Following the Level 1 formulation and solution, several look-ahead trajectory examples for the ISS are explored. In each case, the burn targeting results using the current process are compared against a feasible solution found using Level 1 in the proposed technique. Level 1 is then used to find a minimum deltaV solution given the fixed number of burns and burn TIGs. The optimal solution is compared with the previously found feasible solution to determine the deltaV (and therefore propellant) savings. The proposed technique seeks to both improve the current process for targeting ISS burns, and to add the capability to optimize ISS burns in a novel fashion. The optimal solutions found using this technique can potentially save hundreds of kilograms of propellant over the course of the ISS mission compared to feasible solutions alone. While the software tool being developed to implement this technique is specific to ISS, the concept is extensible to other long-duration, central-body orbiting missions that must perform orbit maintenance burns to meet operational trajectory constraints.

Brown, Aaron J.↗

NASA NTRS2013

Challenges of Integrating NASAs Space Communication Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Reinert, Jessica M.↗

NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗

NASA NTRS2013

Challenges of Integrating NASA's Space Communications Networks

Systems Integration↗

NASA NTRS2015

Portable Virtual Training Units

The Mission Operations Lab initiated a project to design, develop, deliver, test, and validate a unique training system for astronaut and ground support personnel. In an effort to keep training costs low, virtual training units (VTUs) have been designed based on images of actual hardware and manipulated by a touch screen style interface for ground support personnel training. This project helped modernized the training system and materials by integrating them with mobile devices for training when operators or crew are unavailable to physically train in the facility. This project also tested the concept of a handheld remote device to control integrated trainers using International Space Station (ISS) training simulators as a platform. The portable VTU can interface with the full-sized VTU, allowing a trainer co-located with a trainee to remotely manipulate a VTU and evaluate a trainee's response. This project helped determine if it is useful, cost effective, and beneficial for the instructor to have a portable handheld device to control the behavior of the models during training. This project has advanced NASA Marshall Space Flight Center's (MSFC's) VTU capabilities with modern and relevant technology to support space flight training needs of today and tomorrow.

Malone, Reagan↗

NASA NTRS2008

Designing the Ares I Crew Launch Vehicle Upper Stage Element and Integrating the Stack at NASA's Marshall Space Flight Center

Fielding an integrated launch vehicle system entails many challenges, not the least of which is the fact that it has been over 30 years since the United States has developed a human-rated vehicle - the venerable Space Shuttle. Over time, whole generations of rocket scientists have passed through the aerospace community without the opportunity to perform such exacting, demanding, and rewarding work. However, with almost 50 years of experience leading the design, development, and end-to-end systems engineering and integration of complex launch vehicles, the National Aeronautics and Space Administration's (NASA's) Marshall Space Flight Center offers the in-house talent - both junior- and senior-level personnel - to shape a new national asset to meet the requirements for safe, reliable, and affordable space exploration solutions. The technical personnel are housed primarily in Marshall's Engineering Directorate and are matrixed into the programs and projects that reside at the rocket center. Fortunately, many Apollo-era and Shuttle engineers, as well as those who gained valuable hands-on experience in the 1990s by conducting technology demonstrator projects such as the Delta-Clipper Experimental Advanced, X-33, X-34, and X-37, as well as the short-lived Orbital Space Plane, work closely with industry partners to advance the nation's strategic capability for human access to space. The Ares Projects Office, resident at Marshall, is managing the design and development of America's new space fleet, including the Ares I, which will loft the Orion crew capsule for its first test flight in the 2013 timeframe, as well as the heavy-lift Ares V, which will round out the capability to leave low-Earth orbit once again, when it delivers the Altair lunar lander to orbit late next decade. This paper provides information about the approach to integrating the Ares I stack and designing the upper stage in house, using unique facilities and an expert workforce to revitalize the nation's space exploration resources.

Otte, Neil E.↗

NASA NTRS2015

NGSLR Safety Handbook

NASA's Next Generation Satellite Laser Ranging (NGSLR) station is the prototype for NASA's Satellite Laser Ranging (SLR) systems which will be deployed around the world in the coming decade. The NGSLR system will be an autonomous, photon-counting SLR station with an expected absolute range accuracy of better than one centimeter and a normal point (time-averaged) range precision better than one millimeter. The system provides continuous (weather permitting), 24 hour tracking coverage to an existing constellation of approximately two dozen artificial satellites equipped with passive retroreflector arrays, using pulsed, 532 nm, class IV laser systems. Current details on the approved laser systems can be found in the Appendix 1 of this document. This safety plan addresses the potential hazards to emitted laser radiation, which can occur both inside and outside the shelter. Hazards within the shelter are mitigated through posted warning signs, activated warning lights, procedural controls, personal protective equipment (PPE), laser curtains, beam blocking systems, interlock controls, pre-configured laser control settings, and other controls discussed in this document. Since the NGSLR is a satellite tracking system, laser hazards exist outside the shelter to personnel on the shelter roof and to passing aircraft. Potential exposure to personnel outside the system is mitigated through the use of posted warning signs, access control, procedural controls, a stairwell interlock, beam attenuation/blocking devices, and a radar based aircraft detection system.

satellite laser ranging↗

NASA NTRS2016

NASA and ESA Collaboration on Alternative to Nitric Acid Passivation: Parameter Optimization of Citric Acid Passivation for Stainless Steel Alloys

National Aeronautics and Space Administration (NASA) Headquarters chartered the Technology Evaluation for Environmental Risk Mitigation Principal Center (TEERM) to coordinate agency activities affecting pollution prevention issues identified during system and component acquisition and sustainment processes. The primary objectives of NASA TEERM are to: Reduce or eliminate the use of hazardous materials or hazardous processes at manufacturing, remanufacturing, and sustainment locations. Avoid duplication of effort in actions required to reduce or eliminate hazardous materials through joint center cooperation and technology sharing. Corrosion is an extensive problem that affects the National Aeronautics and Space Administration (NASA) and the European Space Agency (ESA). The damaging effects of corrosion result in steep costs, asset downtime affecting mission readiness, and safety risks to personnel. Consequently, it is vital to reduce corrosion costs and risks in a sustainable manner. NASA and ESA have numerous structures and equipment that are fabricated from stainless steel. The standard practice for protection of stainless steel is a process called passivation. Passivation is defined by The American Heritage Dictionary of the English Language as to treat or coat (a metal) in order to reduce the chemical reactivity of its surface. Passivation works by forming a shielding outer (metal oxide) layer that reduces the impact of destructive environmental factors such as air or water. Consequently, this process necessitates a final product that is very clean and free of iron and other contaminants. Typical passivation procedures call for the use of nitric acid; however, there are a number of environmental, worker safety, and operational issues associated with its use. Citric acid is an alternative to nitric acid for the passivation of stainless steels. Citric acid offers a variety of benefits including increased safety for personnel, reduced environmental impact, and reduced operational cost. The primary objective of this effort is to qualify citric acid as an environmentally-preferable alternative to nitric acid for the passivation of stainless steel alloys. While citric acid use has become more prominent in industry, there is little evidence that citric acid is a technically sound passivation agent, especially for the unique and critical applications encountered by NASA and ESA.

citric acid passivation↗

NASA NTRS2016

Successful Completion of the JWST OGSE2 Cryogenic Test at JSC Chamber-A While Managing Numerous Challenges

The James Webb Space Telescope (JWST) Optical Telescope Element (OTE) assembly is the largest optically stable infrared-optimized telescope currently being manufactured and assembled, and scheduled for launch in 2018. The JWST OTE, including the primary mirrors, secondary mirror, and the Aft Optics Subsystems (AOS) are designed to be passively cooled and operate at near 45 degrees Kelvin. Due to the size of its large sunshield in relation to existing test facilities, JWST cannot be optically or thermally tested as a complete observatory-level system at flight temperatures. As a result, the telescope portion along with its instrument complement will be tested as a single unit very late in the program, and on the program schedule critical path. To mitigate schedule risks, a set of 'pathfinder' cryogenic tests will be performed to reduce program risks by demonstrating the optical testing capabilities of the facility, characterizing telescope thermal performance, and allowing project personnel to learn valuable testing lessons off-line. This paper describes the 'pathfinder' cryogenic test program, focusing on the recently completed second test in the series called the Optical Ground Support Equipment 2 (OGSE2) test. The JWST OGSE2 was successfully completed within the allocated project schedule while faced with numerous conflicting thermal requirements during cool-down to the final cryogenic operational temperatures, and during warm-up after the cryo-stable optical tests. The challenges include developing a pre-test cool-down and warm-up profiles without a reliable method to predict the thermal behaviors in a rarified helium environment, and managing the test article hardware safety driven by the project Limits and Constraints (L&C's). Furthermore, OGSE2 test included the time critical Aft Optics Subsystem (AOS), a part of the flight Optical Telescope Element that would need to be placed back in the overall telescope assembly integrations. The OGSE2 test requirements included the strict adherence of the project contamination controls due to the presence of the contamination sensitive flight optical elements. The test operations required close coordination of numerous personnel while they being exposed and trained for the 'final' combined OTE and instrument cryo-test in 2017. This paper will also encompass the OGSE2 thermal data look-back review.

JWST OGSE2 Cryogenic Test↗