Search NASA⌕ Search

SEARCH · Search NASA

Results for “system engineering program”

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 595 records · Page 33

Managing External Relations: The Lifeblood of Mission Success

The slide presentation examines the role of customer and stakeholder relations in the success of space missions. Topics include agency transformation; an overview of project and program experience with a discussion of positions, technical accomplishments, and management lessons learned; and approaches to project success with emphasis on communication. Projects and programs discussed include the Space Shuttle Main Engine System, DC-XA Flight Demonstrator, X-33 Flight Demonstrator, Space Launch Initiative/2nd Generation Reusable Launch Vehicle, X-37 Flight Demonstrator, Constellation (pre Dr. Griffin), Safety and Mission Assurance, and Exploration Launch Projects.

Dumbacher, Daniel L.↗

Building Operations Efficiencies into NASA's Ares I Crew Launch Vehicle Design

The U.S. Vision for Space Exploration guides the National Aeronautics and Space Administration's (NASA's) challenging missions that expand humanity's boundaries and open new routes to the space frontier. With the Agency's commitment to complete the International Space Station (ISS) and to retire the venerable Space Shuttle by 2010, the NASA Administrator commissioned the Exploration Systems Architecture Study (ESAS) in 2005 to analyze options for safe, simple, cost-efficient launch solutions that could deliver human-rated space transportation capabilities in a timely manner within fixed budget guidelines. The Exploration Launch Projects (ELP) Office, chartered by the Constellation Program in October 2005, has been conducting systems engineering studies and business planning to successively refine the design configurations and better align vehicle concepts with customer and stakeholder requirements, such as significantly reduced life-cycle costs. As the Agency begins the process of replacing the Shuttle with a new generation of spacecraft destined for missions beyond low-Earth orbit to the Moon and Mars, NASA is designing the follow-on crew and cargo launch systems for maximum operational efficiencies. To sustain the long-term exploration of space, it is imperative to reduce the $4 billion NASA typically spends on space transportation each year. This paper gives toplevel information about how the follow-on Ares I Crew Launch Vehicle (CLV) is being designed for improved safety and reliability, coupled with reduced operations costs. These methods include carefully developing operational requirements; conducting operability design and analysis; using the latest information technology tools to design and simulate the vehicle; and developing a learning culture across the workforce to ensure a smooth transition between Space Shuttle operations and Ares vehicle development.

Dumbacher, Daniel L.↗

Software for Managing Inventory of Flight Hardware

The Flight Hardware Support Request System (FHSRS) is a computer program that relieves engineers at Marshall Space Flight Center (MSFC) of most of the non-engineering administrative burden of managing an inventory of flight hardware. The FHSRS can also be adapted to perform similar functions for other organizations. The FHSRS affords a combination of capabilities, including those formerly provided by three separate programs in purchasing, inventorying, and inspecting hardware. The FHSRS provides a Web-based interface with a server computer that supports a relational database of inventory; electronic routing of requests and approvals; and electronic documentation from initial request through implementation of quality criteria, acquisition, receipt, inspection, storage, and final issue of flight materials and components. The database lists both hardware acquired for current projects and residual hardware from previous projects. The increased visibility of residual flight components provided by the FHSRS has dramatically improved the re-utilization of materials in lieu of new procurements, resulting in a cost savings of over $1.7 million. The FHSRS includes subprograms for manipulating the data in the database, informing of the status of a request or an item of hardware, and searching the database on any physical or other technical characteristic of a component or material. The software structure forces normalization of the data to facilitate inquiries and searches for which users have entered mixed or inconsistent values.

Salisbury, John↗

What Reliability Engineers Should Know about Space Radiation Effects

Space radiation in space systems present unique failure modes and considerations for reliability engineers. Radiation effects is not a one size fits all field. Threat conditions that must be addressed for a given mission depend on the mission orbital profile, the technologies of parts used in critical functions and on application considerations, such as supply voltages, temperature, duty cycle, and redundancy. In general, the threats that must be addressed are of two types-the cumulative degradation mechanisms of total ionizing dose (TID) and displacement damage (DD). and the prompt responses of components to ionizing particles (protons and heavy ions) falling under the heading of single-event effects. Generally degradation mechanisms behave like wear-out mechanisms on any active components in a system: Total Ionizing Dose (TID) and Displacement Damage: (1) TID affects all active devices over time. Devices can fail either because of parametric shifts that prevent the device from fulfilling its application or due to device failures where the device stops functioning altogether. Since this failure mode varies from part to part and lot to lot, lot qualification testing with sufficient statistics is vital. Displacement damage failures are caused by the displacement of semiconductor atoms from their lattice positions. As with TID, failures can be either parametric or catastrophic, although parametric degradation is more common for displacement damage. Lot testing is critical not just to assure proper device fi.mctionality throughout the mission. It can also suggest remediation strategies when a device fails. This paper will look at these effects on a variety of devices in a variety of applications. This paper will look at these effects on a variety of devices in a variety of applications. (2) On the NEAR mission a functional failure was traced to a PIN diode failure caused by TID induced high leakage currents. NEAR was able to recover from the failure by reversing the current of a nearby Thermal Electric Cooler (turning the TEC into a heater). The elevated temperature caused the PIN diode to anneal and the device to recover. It was by lot qualification testing that NEAR knew the diode would recover when annealed. This paper will look at these effects on a variety of devices in a variety of applications. Single Event Effects (SEE): (1) In contrast to TID and displacement damage, Single Event Effects (SEE) resemble random failures. SEE modes can range from changes in device logic (single-event upset, or SEU). temporary disturbances (single-event transient) to catastrophic effects such as the destructive SEE modes, single-event latchup (SEL). single-event gate rupture (SEGR) and single-event burnout (SEB) (2) The consequences of nondestructive SEE modes such as SEU and SET depend critically on their application--and may range from trivial nuisance errors to catastrophic loss of mission. It is critical not just to ensure that potentially susceptible devices are well characterized for their susceptibility, but also to work with design engineers to understand the implications of each error mode. -For destructive SEE, the predominant risk mitigation strategy is to avoid susceptible parts, or if that is not possible. to avoid conditions under which the part may be susceptible. Destructive SEE mechanisms are often not well understood, and testing is slow and expensive, making rate prediction very challenging. (3) Because the consequences of radiation failure and degradation modes depend so critically on the application as well as the component technology, it is essential that radiation, component. design and system engineers work togetherpreferably starting early in the program to ensure critical applications are addressed in time to optimize the probability of mission success.

DiBari, Rebecca↗

Developing a Medical System Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

A goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including a mission with lunar orbital and long duration surface operations. The medical system concept of operations (ConOps) is the starting point of creating a foundation for a medical system that meets Level of Care IV requirements, as defined by NASA’s space flight human-system standards. This ConOps illustrates how NASA can provide a Level of Care IV medical system for crews within the various cis-lunar orbit and lunar surface habitat environments. The use case scenarios included in this ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. This discussion will focus on how this concept of operations was constructed – by utilizing the lessons learned from ExMC’s existing Short-Duration Lunar Orbit Medical System Concept of Operations, by employing Model-Based Systems Engineering, and by collaborating with stakeholders in order to ensure the necessary assumptions were made.

M. Kaetzer↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

M Kaetzer↗

Implementation of a SysML Model-Based Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

One goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including orbital and surface operations for long duration lunar missions. This is accomplished through the development of a Medical System Foundation, which communicates medical system requirements, capabilities, conditions, and resources that define a starting point for a medical system that meets the specification for design reference missions and associated Levels of Care (as defined by NASA-STD-3001). The starting point for creating this Medical System Foundation Model is the development of a Concept of Operations (ConOps) that describes the operation of the system from the point of view of the users. It includes a comprehensive and thoroughly vetted list of the users, their specific needs, the goals of the system, key assumptions about the system, and definitions of the system’s operational environments. The use case scenarios included in the ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. For this “Long Duration” Medical System Foundation development effort, ExMC replaced the traditional document-based ConOps with a model-based ConOps using model-based systems engineering. This approach has several advantages, including the facilitation of more efficient understanding of the material through information-dense images with less opportunity for misinterpretation than text alone, the roll-out of changes to the ConOps to stakeholders in real-time as they are approved, and the consolidation of all salient information into one centralized location. This discussion will focus on both how the model represents the ConOps content and how the SE team utilized lessons learned in an agile environment to improve the way this information was created and presented to stakeholders.

Mary Susan Kaetzer↗

NASA Crew and Cargo Launch Vehicle Development Approach Builds on Lessons from Past and Present Missions

The United States (US) Vision for Space Exploration, announced in January 2004, outlines the National Aeronautics and Space Administration's (NASA) strategic goals and objectives, including retiring the Space Shuttle and replacing it with new space transportation systems for missions to the Moon, Mars, and beyond. The Crew Exploration Vehicle (CEV) that the new human-rated Crew Launch Vehicle (CLV) lofts into space early next decade will initially ferry astronauts to the International Space Station (ISS) Toward the end of the next decade, a heavy-lift Cargo Launch Vehicle (CaLV) will deliver the Earth Departure Stage (EDS) carrying the Lunar Surface Access Module (LSAM) to low-Earth orbit (LEO), where it will rendezvous with the CEV launched on the CLV and return astronauts to the Moon for the first time in over 30 years. This paper outlines how NASA is building these new space transportation systems on a foundation of legacy technical and management knowledge, using extensive experience gained from past and ongoing launch vehicle programs to maximize its design and development approach, with the objective of reducing total life cycle costs through operational efficiencies such as hardware commonality. For example, the CLV in-line configuration is composed of a 5-segment Reusable Solid Rocket Booster (RSRB), which is an upgrade of the current Space Shuttle 4- segment RSRB, and a new upper stage powered by the liquid oxygen/liquid hydrogen (LOX/LH2) J-2X engine, which is an evolution of the J-2 engine that powered the Apollo Program s Saturn V second and third stages in the 1960s and 1970s. The CaLV configuration consists of a propulsion system composed of two 5-segment RSRBs and a 33- foot core stage that will provide the LOX/LED needed for five commercially available RS-68 main engines. The J-2X also will power the EDS. The Exploration Launch Projects, managed by the Exploration Launch Office located at NASA's Marshall Space Flight Center, is leading the design, development, testing, and operations planning for these new space transportation systems. Utilizing a foundation of heritage hardware and management lessons learned mitigates both technical and programmatic risk. Project engineers and managers work closely with the Space Shuttle Program to transition hardware, infrastructure, and workforce assets to the new launch systems, leveraging a wealth of knowledge from Shuffle operations. In addition, NASA and its industry partners have tapped into valuable Apollo databases and are applying corporate wisdom conveyed firsthand by Apollo-era veterans of America s original Moon missions. Learning from its successes and failures, NASA employs rigorous systems engineering and systems management processes and principles in a disciplined, integrated fashion to further improve the probability of mission success.

Dumbacher, Daniel L.↗

A Status of the Advanced Space Transportation Program from Planning to Action

A Technology Plan for Enabling Commercial Space Business was presented at the 48th International Astronautical Congress in Turin, Italy. This paper presents a status of the program's accomplishments. Technology demonstrations have progressed in each of the four elements of the program; (1) Low Cost Technology, (2) Advanced Reusable Technology, (3) Space Transfer Technology and (4) Space Transportation Research. The Low Cost Technology program element is primarily focused at reducing development and acquisition costs of aerospace hardware using a "design to cost" philosophy with robust margins, adapting commercial manufacturing processes and commercial off-the-shelf hardware. The attributes of this philosophy for small payload launch are being demonstrated at the component, sub-system, and system level. The X-34 "Fastrac" engine has progressed through major component and subsystem demonstrations. A propulsion system test bed has been implemented for system-level demonstration of component and subsystem technologies; including propellant tankage and feedlines, controls, pressurization, and engine systems. Low cost turbopump designs, commercial valves and a controller are demonstrating the potential for a ten-fold reduction in engine and propulsion system costs. The Advanced Reusable Technology program element is focused on increasing life through high strength-to-weight structures and propulsion components, highly integrated propellant tanks, automated checkout and health management and increased propulsion system performance. The validation of rocket based combined cycle (RBCC) propulsion is pro,-,ressing through component and subsystem testing. RBCC propulsion has the potential to provide performance margin over an all rocket system that could result in lower gross liftoff weight, a lower propellant mass fraction or a higher payload mass fraction. The Space Transfer Technology element of the program is pursuing technology that can improve performance and dramatically reduce the propellant and structural mass of orbit transfer and deep space systems. Flight demonstration of ion propulsion is progressing towards launch. Ion propulsion is the primary propulsion for Deep Space 1; a flyby of comet West-kohoutek-lkemura and asteroid 3352 McAuliffe. Testing of critical solar-thermal propulsion subsystems have been accomplished and planning is continuing for the flight demonstration of an electrodynamic tether orbit transfer system. The forth and final element of the program, Space Transportation Research, has progressed in several areas of propulsion research. This element of the program is focused at long-term (25 years) breakthrough concepts that could bring launch costs to a factor of one hundred below today's cost or dramatically expand planetary travel and enable interstellar travel.

Lyles, Garry↗

Component-Based Visualization System

A software system has been developed that gives engineers and operations personnel with no "formal" programming expertise, but who are familiar with the Microsoft Windows operating system, the ability to create visualization displays to monitor the health and performance of aircraft/spacecraft. This software system is currently supporting the X38 V201 spacecraft component/system testing and is intended to give users the ability to create, test, deploy, and certify their subsystem displays in a fraction of the time that it would take to do so using previous software and programming methods. Within the visualization system there are three major components: the developer, the deployer, and the widget set. The developer is a blank canvas with widget menu items that give users the ability to easily create displays. The deployer is an application that allows for the deployment of the displays created using the developer application. The deployer has additional functionality that the developer does not have, such as printing of displays, screen captures to files, windowing of displays, and also serves as the interface into the documentation archive and help system. The third major component is the widget set. The widgets are the visual representation of the items that will make up the display (i.e., meters, dials, buttons, numerical indicators, string indicators, and the like). This software was developed using Visual C++ and uses COTS (commercial off-the-shelf) software where possible.

Delgado, Francisco↗

Development and Testing of Pulse Guns for Combustion Instability Testing

To test liquid rocket engines (LREs) for combustion instabilities, devices such as bombs are often used to create pressure wave disturbances. Bombs, while effective, are inherently dangerous, expensive, and difficult to procure. Over the years, pulse guns have been used as a safer and more cost-effective way to generate controlled pressure disturbances in engine chambers. In anticipation of the need for stability testing of prototype LREs at NASA Marshall Space Flight Center (MSFC), a set of pulse guns have been designed, fabricated, tested, and characterized. The pulse gun program is funded by the RS-25 Engine Program managed out of MSFC and funded by NASA’s Space Launch System (SLS) through the MSFC Liquid Engines Office (LEO). A pulse gun is a simple device – like a traditional gun, it has a breech and barrel section. However, unlike a traditional gun, there is no bullet, as the purpose of the pulse gun is strictly to fire a high pressure pulse. Instead of a firing pin and primer that would normally be used in a traditional gun, an initiator is used to activate the gun powder. The initiator is a highly reliable pyrotechnic initiator. For this study, clone versions of the NASA Standard Initiator (NSI) were used. The initiator is used to ignite a pre-measured amount of gun powder loaded into the breech. When the pressure of the burnt gun powder exceeds the set point of a downstream burst disk, the disk ruptures, allowing the high pressure pulse to travel downstream through the barrel section. A ballistic pressure transducer located in the breech section is used to measure the short duration, high pressure pulse. Some configurations of the pulse gun have barrel sections that include one or more additional ballistic pressure transducers. These additional pressure measurements help track the degradation and damping of the pulse as it travels out of the barrel section. The measurements may also be used to determine the velocity of pulse. The objective of this paper is to present the different variants of this newly-developed pulse gun and characterize performance over a range of parameters. The parameters include breech diameter, barrel length, amount of gun powder used, the way the gun powder is packed, and the pressure setting of the burst disk. There are a total of six pulse guns: three with the 0.25 inch breech and three different length barrels, and three with the 0.40 inch breech and three different length barrels. For both breech sizes, the associated barrels are referred to as standard, one-port, and two-port barrels. The standard barrel has no instrumentation and is likely the barrel that will be used for engine stability testing. The one- and two-port barrels were designed specifically for pulse gun component testing to allow measurements of the magnitude and timing of the high pressure pulse as it makes its way through the pulse gun. The burst disks tested were commercially-available burst disks designed to rupture at 8,000, 16,000, and 24,000 psid. Testing was accomplished by firing the pulse gun into a test chamber pressurized with nitrogen at about 2300 psig. A total of four Model 113B23 High frequency ICP® pressure sensors (10k psi) were mounted in the test chamber, in the same plane as the pulse gun. Two of the sensors had “trimmed” adapters, and two did not. Given the symmetrical configuration of the sensors within the test chamber, different amplitudes of pressure measurements are attributed to the use of trimmed versus untrimmed adapters. The untrimmed adapters, with their narrower passages, tended to amplify the pressure amplitudes by as much as 50%. In total, 41 pulse gun tests have been conducted.Data are still being analyzed, but some trends are apparent. For example, measurements taken within the pulse gun are shown in Figures 3 and 4 for Hot-fires (HFs) # 11 and 39, respectively. Both tests were identical in that the 0.40 inch ID breech, two-port barrel, 8,000 psid burst disk, and same amount of gunpowder (6.639 grains for HF# 11, and 6.576 grains for HF# 39) were used, and the back pressure in the nitrogen test chamber was ~2300 psig. Despite keeping all these variables constant, the results from these two tests look quite different. For both tests, the first pressure peak shown in the P2111 trace within the breech is the firing of the initiator. The second peak and any subsequent peaks are from the combustion of the gunpowder. It should be noted that because the sensors are dynamic, the ~2300 psig baseline static pressure is not shown in the figures. For HF# 11, the burst disk clearly ruptured in a little over 0.1 ms from the time the initiator was fired. This is evident from the abrupt rise in pressure for P2112 followed by another abrupt rise in pressure for P2113. The sensors track the movement of the high pressure pulse through the pulse gun. For HF# 39, however, there was nearly 1 ms delay between the initiator firing and the burst disk rupturing. The only difference between these two tests was the way in which the gunpowder was packed within the breech. For HF# 11, the gunpowder was poured directly into the breech, atop the initiator, and held in place with a vegetable fiber wad appropriately sized for the barrel diameter. Once in place, the wad firmly held the gunpowder in place. For HF# 39, the gunpowder was rolled within cigarette paper with the ends of the paper twisted. The rolled gunpowder was gently pushed down into the breech, toward the initiator, and no wad was used. This method of loading the gunpowder consistently produced longer delays in the rupture of the burst disk, presumably because there was a steady, fuller burning of the gunpowder. The burst disk was rated for 8,000 psid, which means that the burst disk should not have opened until the pressure in the breech reached ~10,300 since there was ~2300 psig back pressure in the test chamber. In the case of HF# 11, the breech pressure only reached roughly 4200 psi before there was leakage either through or past the burst disk, but for HF#39, the breech pressure reached 10,600 psi prior to the burst disk opening. The temperature of the burst disk is certainly a factor in determining when the burst disk will rupture. A sharp rise in the burst disk temperature could weaken it and cause it to stray from the designed set point burst pressure. The burst disks are manufactured of Inconel to try to reduce their sensitivity to temperature, but how the burst disks perform above 900°F is not documented. All burst disks were engineered and tested by the manufacturer for ambient temperature conditions. One theory for why rolling the gunpowder in cigarette paper may produce better results is related to a more controlled temperature environment. The cigarette paper may act as a sheath that protects the burst disk from excessive temperatures during the rapid buildup of pressure in the breech. The ultimate benefit of not breeching the burst disk prematurely is shown in Figures 5 and 6, which graphs the resultant pressure pulse produced in the test chamber. For HF #11, the peak pressure on the P2123 trimmed adapter is about 270 psi, while for HF# 39 it is 343 psi, which is about 1.27 times greater in magnitude. In either case, the pressure pulse is ~20 μs in width once it reaches the test chamber. Another pressure rise about 100 μs later can be seen on the sensors located across from the pulse gun port, P2124 and P2121. These pressures are lower due to attenuation of the pressure wave as it moves across the test chamber. After the wave encounters the wall, it reflects back and forth within the chamber until it completely dissipates.

Pulse Gun↗

A review and forecast of engine system research at the Army Propulsion Directorate

An account is given of the development status and achievements to date of the U.S. Army Propulsion Directorate's Small Turbine Engine Research (STER) programs, which are experimental investigations of the physics of entire engine systems from the viewpoints of component interactions and/or system dynamics. STER efforts are oriented toward the evaluation of complete turboshaft engine advanced concepts and are conducted at the ECRL-2 indoor, sea-level engine test facility. Attention is given to the results obtained by STER experiments concerned with IR-suppressing engine exhausts, a ceramic turbine-blade shroud, an active shaft-vibration control system, and a ceramic-matrix combustor liner.

Bobula, George A.↗

2005 NASA Seal/Secondary Air System Workshop, Volume 1

The 2005 NASA Seal/Secondary Air System workshop covered the following topics: (i) Overview of NASA s new Exploration Initiative program aimed at exploring the Moon, Mars, and beyond; (ii) Overview of the NASA-sponsored Propulsion 21 Project; (iii) Overview of NASA Glenn s seal project aimed at developing advanced seals for NASA s turbomachinery, space, and reentry vehicle needs; (iv) Reviews of NASA prime contractor, vendor, and university advanced sealing concepts including tip clearance control, test results, experimental facilities, and numerical predictions; and (v) Reviews of material development programs relevant to advanced seals development. Turbine engine studies have shown that reducing high-pressure turbine (HPT) blade tip clearances will reduce fuel burn, lower emissions, retain exhaust gas temperature margin, and increase range. Several organizations presented development efforts aimed at developing faster clearance control systems and associated technology to meet future engine needs. The workshop also covered several programs NASA is funding to develop technologies for the Exploration Initiative and advanced reusable space vehicle technologies. NASA plans on developing an advanced docking and berthing system that would permit any vehicle to dock to any on-orbit station or vehicle. Seal technical challenges (including space environments, temperature variation, and seal-on-seal operation) as well as plans to develop the necessary "androgynous" seal technologies were reviewed. Researchers also reviewed tests completed for the shuttle main landing gear door seals.

Steinetz, Bruce M.↗

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record↗

Liquid hydrogen and liquid oxygen feedline passive recirculation analysis

The primary goal of the National Launch System (NLS) program was to design an operationally efficient, highly reliable vehicle with minimal recurring launch costs. To achieve this goal, trade studies of key main propulsion subsystems were performed to specify vehicle design requirements. These requirements include the use of passive recirculation to thermally condition the liquid hydrogen (LH2) and liquid oxygen (LO2) propellant feed systems and Space Transportation Main Engine (STME) fuel pumps. Rockwell International (RI) proposed a joint independent research and development (JIRAD) program with Marshall Space Flight Center (MSFC) to study the LH2 feed system passive recirculation concept. The testing was started in July 1992 and completed in November 1992. Vertical and sloped feedline designs were used. An engine simulator was attached at the bottom of the feedline. This simulator had strip heaters that were set to equal the corresponding heat input from different engines. A computer program is currently being used to analyze the passive recirculation concept in the LH2 vertical feedline tests. Four tests, where the heater setting is the independent variable, were chosen. While the JIRAD with RI was underway, General Dynamics Space Systems (GDSS) proposed a JIRAD with MSFC to explore passive recirculation in the LO2 feed system. Liquid nitrogen (LN2) is being used instead of LO2 for safety and economic concerns. To date, three sets of calibration tests have been completed on the sloped LN2 test article. The environmental heat was calculated from the calibration tests in which the strip heaters were turned off. During the LH2 testing, the environmental heat was assumed to be constant. Therefore, the total heat was equal to the environmental heat flux plus the heater input. However, the first two sets of LN2 calibration tests have shown that the environmental heat flux varies with heater input. A Systems Improved Numerical Differencing Analyzer and Fluid Integrator (SINDA/FLUINT) model is currently being built to determine if this variation in environmental heat is due to a change in the wall temperature. During the third set of calibration tests, a faulty reference junction was found. Based on this anomaly with the reference junction, the heat flux calculations from the first two calibration sets are now considered questionable.

Holt, Kimberly Ann↗

Future earth orbit transportation systems/technology implications

Assuming Space Shuttle technology to be state-of-the-art, projected technological advances to improve the capabilities of single-stage-to-orbit (SSTO) derivatives are examined. An increase of about 30% in payload performance can be expected from upgrading the present Shuttle system through weight and drag reductions and improvements in the propellants and engines. The ODINEX (Optimal Design Integration Executive Computer Program) program has been used to explore design options. An advanced technology SSTO baseline system derived from ODINEX analysis has a conventional wing-body configuration using LOX/LH engines, three with two-position nozzles with expansion ratios of 40 and 200 and four with fixed nozzles with an expansion ratio of 40. Two assisted-takeoff approaches are under consideration in addition to a concept in which the orbital vehicle takes off empty using airbreathing propulsion and carries out a rendezvous with two large cryogenic tankers carrying propellant at an altitude of 6100 m. Further approaches under examination for propulsion, aerothermodynamic design, and design integration are described.

Henry, B. Z.↗

An Historical Perspective of the NERVA Nuclear Rocket Engine Technology Program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗

An historical perspective of the NERVA nuclear rocket engine technology program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗