SEARCH · Search NASA
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.
Production expenses are decreased by embossing encapsulating plastic film to position and secure cells. Electric circuit is printed on plastic film simultaneously with cell encapsulation process. Procedure can be used with standard-contact and wraparound contact cells.
Efficient nickel heat-exchanger cold plates can be fabricated less expensively than stainless steel plates. If adapted to mass production, it is estimated that nickel cold plates might be made for about 30 percent less than stainless-steel plates.
The development of streamlining as a concept, its inclusion in the space transportation system engineering and operations support (STSEOS) contract, and how it serves as an incentive to management and technical support personnel is discussed. The mechanics of encouraging and processing streamlining suggestions, reviews, feedback to submitters, recognition, and how individual employee performance evaluations are used to motivation are discussed. Several items that were implemented are mentioned. Information reported and the methodology of determining estimated dollar savings are outlined. The overall effect of this activity on the ability of the McDonnell Douglas flight preparation and mission operations team to support a rapidly increasing flight rate without a proportional increase in cost is illustrated.
Benefits and rationale for developing a common, modular lunar/Mars space transporation system (STS) based on nuclear thermal rocket (NTR) are presented. The modular NTR is based on three key components including a 50 klbf NERVA-derived engine used in clusters of 2 or 3, two standardized tank sizes developed for the First Lunar Outpost and Mars cargo vehicle applications, and a preintegrated truss/propellant feed system used for transferring LH2 from the drop tanks into the 'in-line' tank. It is concluded that, by using these components in a 'building block' fashion, a variety of single and multi-engine lunar and Mars vehicles can be configured to satisfy particular mission requirements.
The results of integrated systems and mission studies are presented which quantify the benefits and rationale for developing a common, modular lunar/Mars space transportation system (STS) based on nuclear thermal rocket (NTR) technology. At present NASA's Exploration Program Office (ExPO) is considering chemical propulsion for an 'early return to the Moon' and NTR propulsion for the more demanding Mars missions to follow. The time and cost to develop these multiple systems are expected to be significant. The Nuclear Propulsion Office (NPO) has examined a variety of lunar and Mars missions and heavy lift launch vehicle (HLLV) options in an effort to determine a 'standardized' set of engine and stage components capable of satisfying a wide range of Space Exploration Initiative (SEI) missions. By using these components in a 'building block' fashion, a variety of single and multi-engine lunar and Mars vehicles can be configured. For NASA's 'First Lunar Outpost' (FLO) mission, an expendable NTR stage powered by two 50 klbf engines can deliver approximately 96 metric tons (t) to translunar injection (TLI) conditions for an initial mass in low earth orbit (IMLEO) of approximately 198 t compared to 250 t for a cryogenic chemical TLI stage. The NTR stage liquid hydrogen (LH2) tank has a 10 m diameter, 14.5 m length, and 66 t LH2 capacity. The NTR utilizes a UC-ZrC-graphite 'composite' fuel with a specific impulse (Isp) capability of approximately 900 s and an engine thrust-to-weight ratio of approximately 4.3. By extending the size and LH2 capacity of the lunar NTR stage to approximately 20 m and 96 t, respectively, a single launch Mars cargo vehicle capable of delivering approximately 50 t of surface payload is possible. Three 50 klbf NTR engines and the two standardized LH2 tank sizes developed for lunar and Mars cargo vehicle applications would be used to configure the Mars piloted vehicle for a mission as early as 2010. The paper describes the features of the 'common' NTR-based moon/Mars STS, examines performance sensitivities resulting from different 'mission mode' assumptions, and quantifies potential schedule and cost benefits resulting from this modular moon/Mars NTR vehicle approach.
The NASA Space Operations Management Office (SOMO) is presented. The SOMO concept is based on continuing the distributed participation of the various NASA field centers and agencies, while employing consolidated management through a single lead center. The aim is to determine the duplicity and the overlap between the different agencies that independently developed their own operations management approaches in order to enable more cost effective mission operations by providing common services to the NASA programs. The space operations management will be performed in a distributed manner with a greater degree of contractor involvement than in the past. The changes, approaches and anticipated benefits of this approach to operations are discussed.
Flight software (FSW) is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are dealing almost entirely with onboard software. This software, even more than ground/flight communications systems, is expected to perform perfectly at all times during all phases of on-orbit mission life. Due to the fact that FSW can be reconfigured and reprogrammed to accommodate new spacecraft conditions, the on-orbit FSW maintenance team is usually significantly responsible for the long-term success of a science mission. Failure of FSW can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to staffing on-orbit software maintenance, namely: (1) using the original developers, (2) using mission operations personnel, or (3) assembling a Center of Excellence for multi-spacecraft on-orbit FSW support. This paper explains a National Aeronautics and Space Administration, Goddard Space Flight Center (NASA/GSFC) experience related to the roles of on-orbit FSW maintenance personnel. It identifies the advantages and disadvantages of each of the three approaches to staffing the FSW roles, and demonstrates how a cost efficient on-orbit FSW Maintenance Center of Excellence can be established and maintained with significant return on the investment.
Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.
Development of architectures for human exploration missions has been pursued in the international aerospace community for a long time. This paper attempts a different approach and way of looking at architectures. Most of the emphasis is on lunar architectures with a brief look at Mars. The first step is to set forth overarching gods in order to understand origins of requirements. Then, principles and guidelines are developed for architecture formulation. It is argued that safety and cost are the primary factors. Alternative mission profiles are examined for adherence to the principles, and specific architectures formulated according to the guidelines. The guidelines themselves indicate preferred evolution paths from lunar to Mars architectures. Results of example calculations are given to illustrate the process, and an evolution path is recommended. Safety and cost criteria tend to conflict, but it is shown that cost-efficient architectures can be enhanced for good safety ratings at modest cost.
The paper will then propose extending this multi-mission philosophy to skeleton timeline development, science sequencing, and spacecraft sequencing. Finally, the paper will investigate a multi-mission approach to MOS development.
This paper describes the Radio Science Receiver system and the savings it has brought to mission operations. The design and implementation of remote and autonomous operations will be discussed along with the process of including user feedback along the way and lessons learned and procedures avoided.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
The SPICE system of navigation and ancillary data possesses a number of traits that make its use in modern space missions of all types highly cost efficient. The core of the system is a software library providing API interfaces for storing and retrieving such data as trajectories, orientations, time conversions, and instrument geometry parameters. Applications used at any stage of a mission life cycle can call SPICE APIs to access this data and compute geometric quantities required for observation planning, engineering assessment and science data analysis. SPICE is implemented in three different languages, supported on 20+ computer environments, and distributed with complete source code and documentation. It includes capabilities that are extensively tested by everyday use in many active projects and are applicable to all types of space missions - flyby, orbiters, observatories, landers and rovers. While a customer's initial SPICE adaptation for the first mission or experiment requires a modest effort, this initial effort pays off because adaptation for subsequent missions/experiments is just a small fraction of the initial investment, with the majority of tools based on SPICE requiring no or very minor changes.
In applications where stress on a structure may vary widely and have an unknown impact on integrity, a common engineering strategy has been overbuilding to ensure a sufficiently robust design. While this may be appropriate in applications where weight concerns are not paramount, space applications demand a bare minimum of mass, given astronomical per-pound launch costs. For decades, the preferred solution was the tactic of disassembly and investigation between flights. Knowing there must be a better way, Dr. Mark Froggatt, of Langley Research Center, explored alternate means of monitoring stresses and damage to the space shuttle. While a tear-it-apart-and-have-a-look strategy was effective, it was also a costly and time consuming process that risked further stresses through the very act of disassembly and reassembly. An alternate way of monitoring the condition of parts under the enormous stresses of space flight was needed. Froggatt and his colleagues at Langley built an early-warning device to provide detailed information about even minuscule cracks and deformations by etching a group of tiny lines, or grating, on a fiber optic cable five-thousandths of an inch thick with ultraviolet light. By then gluing the fiber to the side of a part, such as a fuel tank, and shining a laser beam down its length, reflected light indicated which gratings were under stress. Inferring this data from measurements in light rather than in bonded gauges saved additional weight. Various shuttle components now employ the ultrasonic dynamic vector stress sensor (UDVSS), allowing stress detection by measuring light beamed from a built-in mini-laser. By measuring changes in dynamic directional stress occurring in a material or structure, and including phase-locked loop, synchronous amplifier, and contact probe, the UDVSS proved especially useful among manufacturers of aerospace and automotive structures for stress testing and design evaluation. Engineers could ensure safety in airplanes and spaceships with a narrower, not overbuilt, margin of safety. For this development, in 1997, Discover Magazine named Froggatt a winner in the "Eighth Annual Awards for Technological Innovation" from more than 4,000 entries.
The goal of this paper is to emphasize the importance of developing complete and unambiguous requirements early in the project cycle (prior to Preliminary Design Phase). Having a complete set of requirements early in the project cycle allows sufficient time to generate a traceability matrix. Requirements traceability and analysis are the key elements in improving verification and validation process, and thus overall software quality. Traceability can be most beneficial when the system changes. If changes are made to high-level requirements it implies that low-level requirements need to be modified. Traceability ensures that requirements are appropriately and efficiently verified at various levels whereas analysis ensures that a rightly interpreted set of requirements is produced.
UNKNOWN