Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “technical support”

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 955 records · Page 53
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Guidelines of the Design of Electropyrotechnic Firing Circuit for Unmanned Flight and Ground Test Projects

The NASA Langley Research Center, Engineering Directorate, Electronic System Branch, is responsible for providing pyrotechnic support capabilities to Langley Research Center unmanned flight and ground test projects. These capabilities include device selection, procurement, testing, problem solving, firing system design, fabrication and testing; ground support equipment design, fabrication and testing; checkout procedures and procedure?s training to pyro technicians. This technical memorandum will serve as a guideline for the design, fabrication and testing of electropyrotechnic firing systems. The guidelines will discuss the entire process beginning with requirements definition and ending with development and execution.

Gonzalez, Guillermo A.↗
NASA NTRS2016

U.S. Spacesuit Knowledge Capture Accomplishments in Fiscal Year 2015

The NASA U.S. Spacesuit Knowledge Capture (SKC) Program continues to capture, share, and archive significant spacesuit-related knowledge with engineers and other technical staff and invested entities. Since its 2007 inception, the SKC Program has hosted and recorded more than 65 events. By the end of Fiscal Year (FY) 2015, 40 of these were processed and uploaded to a publically accessible NASA Web site where viewers can expand their knowledge about the spacesuit's evolution, known capability and limitations, and lessons learned. Sharing this knowledge with entities beyond NASA can increase not only more people's understanding of the technical effort and importance involved in designing a spacesuit, it can also expand the interest and support in this valuable program that ensures significant knowledge is retained and accessible. This paper discusses the FY 2015 SKC events, the release and accessibility of the approved events, and the program's future plans.

Chullen, Cinda↗
NASA NTRS2016

U.S. Spacesuit Knowledge Capture Accomplishments in Fiscal Year 2015

The NASA U.S. Spacesuit Knowledge Capture (SKC) Program continues to capture, share, and archive significant spacesuit-related knowledge with engineers and other technical staff and invested entities. Since its 2007 inception, the SKC Program has hosted and recorded more than 75 events. By the end of Fiscal Year (FY) 2015, 40 of these were processed and uploaded to a publically accessible NASA Web site where viewers can expand their knowledge about the spacesuit's evolution, known capabilities and limitations, and lessons learned. Sharing this knowledge with entities beyond NASA can increase not only more people's understanding of the technical effort and importance involved in designing a spacesuit, it can also expand the interest and support in this valuable program that ensures significant knowledge is retained and accessible. This paper discusses the FY 2015 SKC events, the release and accessibility of the approved events, and the program's future plans.

Chullen, Cinda↗
NASA NTRS2019

Recommendation for a Medical System Concept of Operations for Gateway Missions

NASA’s exploration missions to cis-lunar space will establish a permanent gateway to future transport missions to Mars. These missions mandate a significant paradigm change for mission planning, spacecraft design, human systems integration, and in-flight medical care due to constraints on mass, volume, power, resupply, and medical evacuation capability. These constraints require medical system development to be tightly integrated with mission and habitat design to provide a sufficient medical infrastructure and enable mission success. This concept of operations provides a vision of medical care needs that will be used to guide the development of a medical system for the cis-lunar Gateway Habitat. This medical system will serve as the precursor to what is implemented in future exploration missions to Mars. This concept of operations documents an overview of the stakeholder needs and system goals of a medical system and provides examples of the types of activities for which the system will be used during the mission. This concept of operations informs the ExMC systems engineering effort to define the Gateway Habitat Medical System by documenting the medical activities and capabilities relevant to Gateway missions, as identified by the ExMC clinician community. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions.

Rubin, David↗
NASA NTRSDate not supplied

Small Spacecraft Systems Virtual Institute - Presentation to the Committee of the Review of Progress Toward Implementing the Decadal Survey Vision and Voyages for Planetary Science

The Small Spacecraft Systems Virtual Institute (S3VI) was established in 2017 to leverage the growing small spacecraft community, promote innovation, identify emerging technology opportunities, and provide an efficient channel for communication about small spacecraft systems with industry, academia, and other government agencies. This presentation offers an overview of the S3VI’s strategy to provide the first one-stop shop for technical knowledge in the rapidly burgeoning small spacecraft technology fields and outlines how the institute can support the planetary science decadal survey efforts.

Small spacecraft↗
NASA NTRSDate not supplied

Three Dimensionally Woven Mid-Density Carbon Phenolic (3MDCP) is a Novel Single Piece Ablative TPS for Extreme Entry Environments

Three Dimensionally Woven Mid-Density Carbon Phenolic (3MDCP) is robust, single piece, carbon phenolic ablative thermal protection system under development at NASA Ames Research Center initially for the Mars Sample Return Earth Entry System (MSR EES). The MSR EES requirements drove the need for TPS with no seams, capable of surviving the highest entry conditions for any NASA Earth return capsule with heat fluxes >2000 W/cm2 and pressures >1.5 atmospheres. To produce 3MDCP required development of new weaving infrastructure to enable weaving of preforms large enough to form into a single piece heatshield. It required development of forming techniques to transform a flat woven panel into a sphere cone shape and enhanced infusion processes to support larger scale infusion of resin into the formed preforms. A rigorous performance testing campaign was conducted to develop and validate the materials thermal response model used to determine the required material thickness and to demonstrate the material can survive the extreme entry conditions. The end of the development effort (end of FY26) will result in a TPS at Technical Readiness Level (TRL) 6 and Manufacturing Readiness Level (MRL) 6+ for the MSR EES mission and a mature system ready to support other missions. This poster will provide a snapshot of where 3MDCP is in its development phase.

Ablator↗
NASA NTRS1984

Space Station active thermal control technical considerations

A description of recent and planned thermal control technology developments at the Johnson Space Center and the other NASA Centers in support of Space Stations is presented. The program is centered around satisfying the needs of the users. Preliminary results of proof-of-concept high capacity heat pipes and two-phase devices are included which indicate that large amounts of energy (100 kW) can be transported long distances (50 m) with very small temperature differences. The presentation summarizes preparations for an 'evolutionary test bed' for advanced development of thermal technology which will provide data on components and systems for incorporation into the Space Station designs in the late 1980s. The results of the recently flown Heat Pipe Experiment aboard STS-8 are presented.

Ellis, W. E.↗
NASA NTRS1994

The NASA Mission Operations and Control Architecture Program

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Ondrus, Paul J.↗
NASA NTRS2005

The Systems Engineering Process for Human Support Technology Development

Systems engineering is designing and optimizing systems. This paper reviews the systems engineering process and indicates how it can be applied in the development of advanced human support systems. Systems engineering develops the performance requirements, subsystem specifications, and detailed designs needed to construct a desired system. Systems design is difficult, requiring both art and science and balancing human and technical considerations. The essential systems engineering activity is trading off and compromising between competing objectives such as performance and cost, schedule and risk. Systems engineering is not a complete independent process. It usually supports a system development project. This review emphasizes the NASA project management process as described in NASA Procedural Requirement (NPR) 7120.5B. The process is a top down phased approach that includes the most fundamental activities of systems engineering - requirements definition, systems analysis, and design. NPR 7120.5B also requires projects to perform the engineering analyses needed to ensure that the system will operate correctly with regard to reliability, safety, risk, cost, and human factors. We review the system development project process, the standard systems engineering design methodology, and some of the specialized systems analysis techniques. We will discuss how they could apply to advanced human support systems development. The purpose of advanced systems development is not directly to supply human space flight hardware, but rather to provide superior candidate systems that will be selected for implementation by future missions. The most direct application of systems engineering is in guiding the development of prototype and flight experiment hardware. However, anticipatory systems engineering of possible future flight systems would be useful in identifying the most promising development projects.

Jones, Harry↗
NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗
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 NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗
NASA NTRS2019

Implementation of Human System Integration Workshop at NASA for Human Spaceflight

The human is a key element in the complex system of systems underlying space exploration missions. As a critical system, its operating bands and requirements need to be characterized and integrated with other systems. Optimal integration of the human system with hardware and software elements has an impact on multiple aspects of mission execution, including human health and performance, risk mitigation, effective design and functionality, enhanced safety, and reduced lifecycle costs. The field of Human Systems Integration (HSI) represents an interdisciplinary and comprehensive cross-cutting approach encompassing technical and management processes for integrating human as a system consideration and objective within and across all other system components and multiple domains. In addition to human activities, HSI covers training, operations and support dimensions. Moreover, HSI is an essential enabler to systems engineering practice, emphasizing human system aspects toward optimizing fully integrated system of systems performance while systematically infusing the needs of all users during the earliest stages of development. Consistent with the National Space Exploration Campaign, NASA is developing the Gateway, a lunar orbiting platform that will serve as astronaut habitat, support transit to deep space, validate new technologies and systems, and function as a science laboratory and communications hub, among other uses. It is an essential element of a phase that will extend human exploration into deep space through evolvable infrastructure and advanced technology, supporting assembly and logistics of other exploration architecture elements. In an effort to explore the current status and forward plan of HSI implementation in the mission (system of systems) lifecycle, the HSI Employee Resource Group conducted an HSI workshop using the Gateway Program as a case study. It revealed how different organizations at the Johnson Space Center incorporate HSI in their processes in preparation for the development and operation of the Gateway. The workshop focused on HSI methodology for implementation of the six NASA HSI domains: Human Factors Engineering, Operations Resources, Habitability and Environment, Maintainability and Supportability, Safety, and Training. Results from the workshop are reported on this paper, as well as some historical background of HSI at NASA, and the success in using an Employee Resource Group to promote technical knowledge. The authors hope that this information can be used to disseminate best practices for translational applications to other space exploration systems.

Silva-Martinez, Jackelynne↗
NASA NTRS2019

Implementation of Human System Integration Workshop at NASA for Human Spaceflight

The human is a key element in the complex system of systems underlying space exploration missions. As a critical system, its operating bands and requirements need to be characterized and integrated with other systems. Optimal integration of the human system with hardware and software elements has an impact on multiple aspects of mission execution, including human health and performance, risk mitigation, effective design and functionality, enhanced safety, and reduced lifecycle costs. The field of Human Systems Integration (HSI) represents an interdisciplinary and comprehensive cross-cutting approach encompassing technical and management processes for integrating human as a system consideration and objective within and across all other system components and multiple domains. In addition to human activities, HSI covers training, operations and support dimensions. Moreover, HSI is an essential enabler to systems engineering practice, emphasizing human system aspects toward optimizing fully integrated system of systems performance while systematically infusing the needs of all users during the earliest stages of development. Consistent with the National Space Exploration Campaign, NASA is developing the Gateway, a lunar orbiting platform that will serve as astronaut habitat, support transit to deep space, validate new technologies and systems, and function as a science laboratory and communications hub, among other uses. It is an essential element of a phase that will extend human exploration into deep space through evolvable infrastructure and advanced technology, supporting assembly and logistics of other exploration architecture elements. In an effort to explore the current status and forward plan of HSI implementation in the mission (system of systems) lifecycle, the HSI Employee Resource Group conducted an HSI workshop using the Gateway Program as a case study. It revealed how different organizations at the Johnson Space Center incorporate HSI in their processes in preparation for the development and operation of the Gateway. The workshop focused on HSI methodology for implementation of the six NASA HSI domains: Human Factors Engineering, Operations Resources, Habitability and Environment, Maintainability and Supportability, Safety, and Training. Results from the workshop are reported on this paper, as well as some historical background of HSI at NASA, and the success in using an Employee Resource Group to promote technical knowledge. The authors hope that this information can be used to disseminate best practices for translational applications to other space exploration systems.

Silva-Martinez, Jackelynne↗
NASA NTRS1999

Main Chamber and Preburner Injector Technology

This document reports the experimental and analytical research carried out at the Penn State Propulsion Engineering Research Center in support of NASA's plan to develop advanced technologies for future single stage to orbit (SSTO) propulsion systems. The focus of the work is on understanding specific technical issues related to bi-propellant and tri-propellant thrusters. The experiments concentrate on both cold flow demonstrations and hot-fire uni-element tests to demonstrate concepts that can be incorporated into hardware design and development. The analysis is CFD-based and is intended to support the design and interpretation of the experiments and to extrapolate findings to full-scale designs. The research is divided into five main categories that impact various SSTO development scenarios. The first category focuses on RP-1/gaseous hydrogen (GH2)/gaseous oxygen (GO2) tri-propellant combustion with specific emphasis on understanding the benefits of hydrogen addition to RP-1/oxygen combustion and in developing innovative injector technology. The second category investigates liquid oxygen (LOX)/GH2 combustion at main chamber near stoichiometric conditions to improve understanding of existing LOX/GH2 rocket systems. The third and fourth categories investigate the technical issues related with oxidizer-rich and fuel-rich propulsive concepts, issues that are necessary for developing the full-flow engine cycle. Here, injector technology issues for both LOX/GH2 and LOX/RP-1 propellants are examined. The last category, also related to the full-flow engine cycle, examines injector technology needs for GO2/GH2 propellant combustion at near-stoichiometric conditions for main chamber application.

Santoro, Robert J.↗