SEARCH · Search NASA

Results for “Data Reuse”

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 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS2016

Kennedy Space Center Five Year Sustainability Plan

The Federal Government is committed to following sustainable principles. At its heart, sustainability integrates environmental, societal and economic solutions for present needs without compromising the ability of future generations to meet their needs. Building upon its pledge towards environmental stewardship, the Administration generated a vision of sustainability spanning ten goals mandated within Executive Order (EO) 13693, Planning for Federal Sustainability in the Next Decade. In November 2015, the National Aeronautics and Space Administration (NASA) responded to this EO by incorporating it into a new release of the NASA Strategic Sustainability Performance Plan (SSPP). The SSPP recognizes the importance of aligning environmental practices in a manner that preserves, enhances and strengthens NASA's ability to perform its mission indefinitely. The Kennedy Space Center (KSC) is following suit with KSC's Sustainability Plan (SP) by promoting, maintaining and pioneering green practices in all aspects of our mission. KSC's SP recognizes that the best sustainable solutions use an interdisciplinary, collaborative approach spanning civil servant and contractor personnel from across the Center. This approach relies on the participation of all employees to develop and implement sustainability endeavors connected with the following ten goals: Reduce greenhouse gas (GHG) emissions. Design, build and maintain sustainable buildings, facilities and infrastructure. Leverage clean and renewable energy. Increase water conservation. Improve fleet and vehicle efficiency and management. Purchase sustainable products and services. Minimize waste and prevent pollution. Implement performance contracts for Federal buildings. Manage electronic equipment and data centers responsibly. Pursue climate change resilience. The KSC SP details the strategies and actions that address the following objectives: Reduce Center costs. center dot Increase energy and water efficiencies. Promote smart buying practices. Increase reuse and recycling while decreasing waste. Benefit the community. Meet or exceed the EO and NASA SSPP sustainability goals.

Sustainability↗

NASA NTRS1986

Report of the Presidential Commission on the Space Shuttle Challenger Accident, Volume 1

The findings of the Commission regarding the circumstances surrounding the Challenger accident are reported and recommendations for corrective action are outlined. All available mission data, subsequent tests, and wreckage analyses were reviewed and specific failure scenarios were developed. The Commission concluded that the cause of the Mission 51-L accident was the failure of the pressure seal in the aft field joint of the right solid rocket motor. The failure was due to a faulty design unacceptably sensitive to a number of factors. These factors were the effects of temperature, physical dimensions, the character of materials, the effects of reuse, processing, and the reaction of the joint to dynamic loading. In addition to analyzing the material causes of the accident, the Commission examined the chain of decisions that culminated in approval of the launch. It concluded that the decision making process was flawed in several ways including (1) failure in communication resulting in a launch decision based on incomplete and misleading information, (2) a conflict between engineering data and management judgements, and (3) a NASA management structure that permitted flight safety problems to bypass key Shuttle managers.

Rogers, W. P.↗

NASA NTRS1984

Fastener load tests and retention systems tests for cryogenic wind-tunnel models

A-286 stainless steel screws were tested to determine the tensile load capability and failure mode of various screw sizes and types at both cryogenic and room temperature. Additionally, five fastener retention systems were tested by using A-286 screws with specimens made from the primary metallic alloys that are currently used for cryogenic models. The locking system effectiveness was examined by simple no-load cycling to cryogenic temperatures (-275 F) as well as by dynamic and static loading at cryogenic temperatures. In general, most systems were found to be effective retention devices. There are some differences between the various devices with respect to ease of application, cleanup, and reuse. Results of tests at -275 F imply that the cold temperatures act to improve screw retention. The improved retention is probably the result of differential thermal contraction and/or increased friction (thread-binding effects). The data provided are useful in selecting screw sizes, types, and locking devices for model systems to be tested in cryogenic wind tunnels.

Wallace, J. W.↗

NASA NTRS1988

Data system overview

The data system architecture design philosophy for 'SFOC', which is a large-scale distributed system for support of current and future space missions at the JPL, stresses 'design for change' standardization that will permit software-reuse, periodic hardware-changeout, and network-configuration evolution. Multimission capabilities are supported through a buildup of the baseline system with a minimum of special-purpose adaptations. SFOC can accommodate multiple users representing multiple disciplines, and is capable of furnishing near-real time and nonrealtime support to end-users for downlink (telemetry) and uplink (command) functions.

Kahr, Joseph R.↗

NASA NTRS1990

Software For Clear-Air Doppler-Radar Display

System of software developed to present plan-position-indicator scans of clear-air Doppler radar station on color graphical cathode-ray-tube display. Designed to incorporate latest accepted standards for equipment, computer programs, and meteorological data bases. Includes use of Ada programming language, of "Graphical-Kernel-System-like" graphics interface, and of Common Doppler Radar Exchange Format. Features include portability and maintainability. Use of Ada software packages produced number of software modules reused on other related projects.

Johnston, Bruce W.↗

NASA NTRS2004

Reconfigurable Transceiver and Software-Defined Radio Architecture and Technology Evaluated for NASA Space Communications

The NASA Glenn Research Center is investigating the development and suitability of a software-based open-architecture for space-based reconfigurable transceivers (RTs) and software-defined radios (SDRs). The main objectives of this project are to enable advanced operations and reduce mission costs. SDRs are becoming more common because of the capabilities of reconfigurable digital signal processing technologies such as field programmable gate arrays and digital signal processors, which place radio functions in firmware and software that were traditionally performed with analog hardware components. Features of interest of this communications architecture include nonproprietary open standards and application programming interfaces to enable software reuse and portability, independent hardware and software development, and hardware and software functional separation. The goals for RT and SDR technologies for NASA space missions include prelaunch and on-orbit frequency and waveform reconfigurability and programmability, high data rate capability, and overall communications and processing flexibility. These operational advances over current state-of-art transceivers will be provided to reduce the power, mass, and cost of RTs and SDRs for space communications. The open architecture for NASA communications will support existing (legacy) communications needs and capabilities while providing a path to more capable, advanced waveform development and mission concepts (e.g., ad hoc constellations with self-healing networks and high-rate science data return). A study was completed to assess the state of the art in RT architectures, implementations, and technologies. In-house researchers conducted literature searches and analysis, interviewed Government and industry contacts, and solicited information and white papers from industry on space-qualifiable RTs and SDRs and their associated technologies for space-based NASA applications. The white papers were evaluated, compiled, and used to assess RT and SDR system architectures and core technology elements to determine an appropriate investment strategy to advance these technologies to meet future mission needs. The use of these radios in the space environment represents a challenge because of the space radiation suitability of the components, which drastically reduces the processing capability. The radios available for space are considered to be RTs (as opposed to SDRs), which are digitally programmable radios with selectable changes from an architecture combining analog and digital components. The limited flexibility of this design contrasts against the desire to have a power-efficient solution and open architecture.

Reinhart, Richard C.↗

NASA NTRS1994

Software interface verifier

A Telos study of 40 recent subsystem deliveries into the DSN at JPL found software interface testing to be the single most expensive and error-prone activity, and the study team suggested creating an automated software interface test tool. The resulting Software Interface Verifier (SIV), which was funded by NASA/JPL and created by Telos, employed 92 percent software reuse to quickly create an initial version which incorporated early user feedback. SIV is now successfully used by developers for interface prototyping and unit testing, by test engineers for formal testing, and by end users for non-intrusive data flow tests in the operational environment. Metrics, including cost, are included. Lessons learned include the need for early user training. SIV is ported to many platforms and can be successfully used or tailored by other NASA groups.

Soderstrom, Tomas J.↗

NASA NTRS2004

Arc Jet Results on Candidate High Temperature Coatings for NASA's NGLT Refractory Composite Leading Edge Task

In 2000, arc jet testing was conducted on thirteen material systems for possible use on the nose leading edge of the Hyper-X program s X-43A Mach 10 vehicle. Six material systems survived 3, 130- second cycles. To support NASA s Next Generation Launch Technology Programs (NGLT) need for passive refractory composite leading edges with multiple reuse capability at temperatures up to 3600 F, these six materials were subjected to an expanded arc jet test program. This expanded arc jet test program included three phases. The purpose of the first phase was to generate emissivity data as a function of temperature. The purpose of the second phase was to determine if the material systems had any thermal cycling durability, and the third phase was to determine whether the materials could survive an arc jet test of one hour duration. Some of the coating systems were found to have very low emissivities, suggesting that they would not be good candidates for leading edges coating. Other coating systems survived both the second and third phases of the test program and showed potential for use as an oxidation protection coating for leading edges. This presentation summarizes the test program results.

Ohlhorst, C. W.↗

NASA NTRS1995

The Experience Factory: Strategy and Practice

The quality movement, that has had in recent years a dramatic impact on all industrial sectors, has recently reached the system and software industry. Although some concepts of quality management, originally developed for other product types, can be applied to software, its specificity as a product which is developed and not produced requires a special approach. This paper introduces a quality paradigm specifically tailored on the problem of the systems and software industry. Reuse of products, processes and experiences originating from the system life cycle is seen today as a feasible solution to the problem of developing higher quality systems at a lower cost. In fact, quality improvement is very often achieved by defining and developing an appropriate set of strategic capabilities and core competencies to support them. A strategic capability is, in this context, a corporate goal defined by the business position of the organization and implemented by key business processes. Strategic capabilities are supported by core competencies, which are aggregate technologies tailored to the specific needs of the organization in performing the needed business processes. Core competencies are non-transitional, have a consistent evolution, and are typically fueled by multiple technologies. Their selection and development requires commitment, investment and leadership. The paradigm introduced in this paper for developing core competencies is the Quality Improvement Paradigm which consists of six steps: (1) Characterize the environment, (2) Set the goals, (3) Choose the process, (4) Execute the process, (5) Analyze the process data, and (6) Package experience. The process must be supported by a goal oriented approach to measurement and control, and an organizational infrastructure, called Experience Factory. The Experience Factory is a logical and physical organization distinct from the project organizations it supports. Its goal is development and support of core competencies through capitalization and reuse of its cycle experience and products. The paper introduces the major concepts of the proposed approach, discusses their relationship with other approaches used in the industry, and presents a case in which those concepts have been successfully applied.

Basili, Victor R.↗

NASA NTRS1998

Case-Based Capture and Reuse of Aerospace Design Rationale

The goal of this project is to apply artificial intelligence techniques to facilitate capture and reuse of aerospace design rationale. The project applies case-based reasoning (CBR) and concept mapping (CMAP) tools to the task of capturing, organizing, and interactively accessing experiences or "cases" encapsulating the methods and rationale underlying expert aerospace design. As stipulated in the award, Indiana University and Ames personnel are collaborating on performance of research and determining the direction of research, to assure that the project focuses on high-value tasks. In the first five months of the project, we have made two visits to Ames Research Center to consult with our NASA collaborators, to learn about the advanced aerospace design tools being developed there, and to identify specific needs for intelligent design support. These meetings identified a number of task areas for applying CBR and concept mapping technology. We jointly selected a first task area to focus on: Acquiring the convergence criteria that experts use to guide the selection of useful data from a set of numerical simulations of high-lift systems. During the first funding period, we developed two software systems. First, we have adapted a CBR system developed at Indiana University into a prototype case-based reasoning shell to capture and retrieve information about design experiences, with the sample task of capturing and reusing experts' intuitive criteria for determining convergence (work conducted at Indiana University). Second, we have also adapted and refined existing concept mapping tools that will be used to clarify and capture the rationale underlying those experiences, to facilitate understanding of the expert's reasoning and guide future reuse of captured information (work conducted at the University of West Florida). The tools we have developed are designed to be the basis for a general framework for facilitating tasks within systems developed by the Advanced Design Technologies Testbed (ADTT) project at ARC. The tenets of our framework are (1) that the systems developed should leverage a designer's knowledge, rather than attempting to replace it; (2) that learning and user feedback must play a central role, so that the system can adapt to how it is used, and (3) that the learning and feedback processes must be as natural and as unobtrusive as possible. In the second funding period we will extend our current work, applying the tools to capturing higher-level design rationale.

Leake, David B.↗

NASA NTRS1991

Analysis of methods

Information is one of an organization's most important assets. For this reason the development and maintenance of an integrated information system environment is one of the most important functions within a large organization. The Integrated Information Systems Evolution Environment (IISEE) project has as one of its primary goals a computerized solution to the difficulties involved in the development of integrated information systems. To develop such an environment a thorough understanding of the enterprise's information needs and requirements is of paramount importance. This document is the current release of the research performed by the Integrated Development Support Environment (IDSE) Research Team in support of the IISEE project. Research indicates that an integral part of any information system environment would be multiple modeling methods to support the management of the organization's information. Automated tool support for these methods is necessary to facilitate their use in an integrated environment. An integrated environment makes it necessary to maintain an integrated database which contains the different kinds of models developed under the various methodologies. In addition, to speed the process of development of models, a procedure or technique is needed to allow automatic translation from one methodology's representation to another while maintaining the integrity of both. The purpose for the analysis of the modeling methods included in this document is to examine these methods with the goal being to include them in an integrated development support environment. To accomplish this and to develop a method for allowing intra-methodology and inter-methodology model element reuse, a thorough understanding of multiple modeling methodologies is necessary. Currently the IDSE Research Team is investigating the family of Integrated Computer Aided Manufacturing (ICAM) DEFinition (IDEF) languages IDEF(0), IDEF(1), and IDEF(1x), as well as ENALIM, Entity Relationship, Data Flow Diagrams, and Structure Charts, for inclusion in an integrated development support environment.

Mayer, Richard J.↗

NASA NTRS1988

Proceedings of the First NASA Ada Users' Symposium

Ada has the potential to be a part of the most significant change in software engineering technology within NASA in the last twenty years. Thus, it is particularly important that all NASA centers be aware of Ada experience and plans at other centers. Ada activity across NASA are covered, with presenters representing five of the nine major NASA centers and the Space Station Freedom Program Office. Projects discussed included - Space Station Freedom Program Office: the implications of Ada on training, reuse, management and the software support environment; Johnson Space Center (JSC): early experience with the use of Ada, software engineering and Ada training and the evaluation of Ada compilers; Marshall Space Flight Center (MSFC): university research with Ada and the application of Ada to Space Station Freedom, the Orbital Maneuvering Vehicle, the Aero-Assist Flight Experiment and the Secure Shuttle Data System; Lewis Research Center (LeRC): the evolution of Ada software to support the Space Station Power Management and Distribution System; Jet Propulsion Laboratory (JPL): the creation of a centralized Ada development laboratory and current applications of Ada including the Real-time Weather Processor for the FAA; and Goddard Space Flight Center (GSFC): experiences with Ada in the Flight Dynamics Division and the Extreme Ultraviolet Explorer (EUVE) project and the implications of GSFC experience for Ada use in NASA. Despite the diversity of the presentations, several common themes emerged from the program: Methodology - NASA experience in general indicates that the effective use of Ada requires modern software engineering methodologies; Training - It is the software engineering principles and methods that surround Ada, rather than Ada itself, which requires the major training effort; Reuse - Due to training and transition costs, the use of Ada may initially actually decrease productivity, as was clearly found at GSFC; and real-time work at LeRC, JPL and GSFC shows that it is possible to use Ada for real-time applications.

Source record↗

NASA NTRS1998

Vehicle and Mission Design Options for the Human Exploration of Mars/Phobos Using "Bimodal" NTR and LANTR Propulsion

The nuclear thermal rocket (NTR) is one of the leading propulsion options for future human missions to Mars because of its high specific impulse (Isp-850-1000 s) capability and its attractive engine thrust-to-weight ratio (approximately equal 3-10). To stay within the available mass and payload volume limits of a "Magnum" heavy lift vehicle, a high performance propulsion system is required for trans-Mars injection (TMI). An expendable TMI stage, powered by three 15 thousand pounds force (klbf) NTR engines is currently under consideration by NASA for its Design Reference Mission (DRM). However, because of the miniscule burnup of enriched uranium-235 during the Earth departure phase (approximately 10 grams out of 33 kilograms in each NTR core), disposal of the TMI stage and its engines after a single use is a costly and inefficient use of this high performance stage. By reconfiguring the engines for both propulsive thrust and modest power generation (referred to as "bimodal" operation), a robust, multiple burn, "power-rich" stage with propulsive Mars capture and reuse capability is possible, A family of modular "bimodal" NTR (BNTR) vehicles are described which utilize a common "core" stage powered by three 15 klbf BNTRs that produce 50 kWe of total electrical power for crew life support, an active refrigeration / reliquification system for long term, "zero-boiloff" liquid hydrogen (LH 2 ) storage, and high data rate communications. An innovative, spine-like "saddle truss" design connects the core stage and payload element and is open underneath to allow supplemental "in-line" propellant tanks and contingency crew consumables to be easily jettisoned to improve vehicle performance. A "modified" DRM using BNTR transfer vehicles requires fewer transportation system elements, reduces IMLEO and mission risk, and simplifies space operations. By taking the next logical step--use of the BNTR for propulsive capture of all payload elements into Mars orbit--the power available in Mars orbit grows to 150 kWe compared to 30 kWe for the DRM. Propulsive capture also eliminates the complex, higher risk aerobraking and capture maneuver which is replaced by a simpler reentry using a standardized, lower mass "aerodescent" shell. The attractiveness of the "all BNTR" option is further increased by the substitution of the lightweight, inflatable "TransHab" module in place of the heavier, hard-shell hab module. Use of TransHab introduces the potential for propulsive recovery and reuse of the BNTR/ERV. It also allows the crew to travel to and from Mar on the same BNTR transfer vehicle thereby cutting the duration of the ERV mission in half--from approximately 4.7 to 2.5 years. Finally, for difficult Mars options, such as Phobos rendezvous and sample return missions, volume (not mass) constraints limit the performance of the "all LH 2 " BNTR stage. The use of "LOX-augmented" NTR (LANTR) engines, operating at a modest oxygen-to-hydrogen mixutre ratio (MR) of 0.5, helps to increase "bulk" propellant density and total thrust during the TMI burn. On all subsequent burns, the bimodal LANTR engines operate on LH 2 only (MR=0) to maximize vehicle performance while staying within the lift capability of two Magnum launches.

Nuclear thermal rocket↗

NASA NTRS2002

Vehicle and Mission Design Options for the Human Exploration of Mars/Phobos Using "Bimodal" NTR and LANTR Propulsion

The nuclear thermal rocket (NTR) is one of the leading propulsion options for future human missions to Mars because of its high specific impulse (lsp~850-1000 s) capability and its attractive engine thrust-to-weight ratio (~3-10). To stay within the available mass and payload volume limits of a “Magnum” heavy lift vehicle, a high performance propulsion system is required for trans-Mars injection (TMI). An expendable TMI stage, powered by three 15 thousand pounds force (klbf) NTR engines is currently under consideration by NASA for its Design Reference Mission (DRM). However, because of the miniscule burnup of enriched uranium-235 during the Earth departure phase (~10 grams out of 33 kilograms in each NTR core), disposal of the TMI stage and its engines after a single use is a costly and inefficient use of this high performance stage. By reconfiguring the engines for both propulsive thrust and modest power generation (referred to as “bimodal” operation), a robust, multiple burn, “power-rich” stage with propulsive Mars capture and reuse capability is possible. A family of modular “bimodal” NTR (BNTR) vehicles are described which utilize a common “core” stage powered by three 15 klbf BNTRs that produce 50 kWe of total electrical power for crew life support, an active refrigeration / reliquification system for long term, zero-boiloff liquid hydrogen (LH 2 ) storage, and high data rate communications. An innovative, spine-like “saddle truss” design connects the core stage and payload element and is open underneath to allow supplemental “in-line” propellant tanks and contingency crew consumables to be easily jettisoned to improve vehicle performance. A “modified” DRM using BNTR transfer vehicles requires fewer transportation system elements, reduces IMLEO and mission risk, and simplifies space operations. By taking the next logical step—use of the BNTR for propulsive capture of all payload elements into Mars orbit—the power available in Mars orbit grows to 150 kWe compared to 30 kWe for the DRM. Propulsive capture also eliminates the complex, higher risk aerobraking and capture maneuver which is replaced by a simpler reentry using a standardized, lower mass “aerodescent” shell. The attractiveness of the “all BNTR” option is further increased by the substitution of the lightweight, inflatable “TransHab” module in place of the heavier, hard-shell hab module. Use of TransHab introduces the potential for propulsive recovery and reuse of the BNTR / Earth return vehicle (ERV). It also allows the crew to travel to and from Mars on the same BNTR transfer vehicle thereby cutting the duration of the ERV mission in half—from ~4.7 to 2.5 years. Finally, for difficult Mars options, such as Phobos rendezvous and sample return missions, volume (not mass) constraints limit the performance of the “all LH 2 ” BNTR stage. The use of “LOX-augmented” NTR (LANTR) engines, operating at a modest oxygen-to-hydrogen mixture ratio (MR) of 0.5, helps to increase “bulk” propellant density and total thrust during the TMI burn. On all subsequent burns, the bimodal LANTR engines operate on LH 2 only (MR=0) to maximize vehicle performance while staying within the mass limits of two Magnum launches.

Nuclear thermal rocket↗

NASA NTRS2002

The spacecraft onboard interface standardization activity

The Consultative Committee for Space Data Systems (CCSDS) is an international organization of national space agencies (such as NASA in the United States) that is organized to promote the interchange of space related information. Now, CCSDS is branching out to provide new standards for the interchange of information, and the interconnection of subsystems and devices onboard of a spacecraft. This effort is know as Spacecraft Onboard Interface (SOIF). SOIF will publish standards that will allow for the enhanced reuse of spacecraft equipment and software. SOIF expects that these standards will be well known and used within the space community, and that they will be based on or similar to the well-known Internet protocols. This paper will provide a description of the SOIF work by reviewing this work with three orthogonal views. The first of these views is the Protocol view, which describes the protocols and services that are to be implemented in order to provide the users with the advantages of the SOIF architecture. The second of these views is the Services View, which describes the data communications services that are provided to the users. And finally, the Interoperability view provides a description to users how SOIF can be used to interchange between different spacecraft data busses. This paper will give the reader an excellent introduction to the work of the international SOIF team.

spacecraft interfaces standard interfaces CCSDS↗

NASA NTRS2002

The spacecraft onboard interface standardization activity

spacecraft interfaces standard interfaces CCSDS↗

NASA NTRS2011

The Modeling and Simulation Catalog for Discovery, Knowledge and Reuse

The DoD M&S Steering Committee has noted that the current DoD and Service's modeling and simulation resource repository (MSRR) services are not up-to-date limiting their value to the using communities. However, M&S leaders and managers also determined that the Department needs a functional M&S registry card catalog to facilitate M&S tool and data visibility to support M&S activities across the DoD. The M&S Catalog will discover and access M&S metadata maintained at nodes distributed across DoD networks in a centrally managed, decentralized process that employs metadata collection and management. The intent is to link information stores, precluding redundant location updating. The M&S Catalog uses a standard metadata schemas based on the DoD's Net-Centric Data Strategy Community of Interest metadata specification. The Air Force, Navy and OSD (CAPE) have provided initial information to participating DoD nodes, but plans on the horizon are being made to bring in hundreds of source providers.

Stone, George F. III↗

NASA NTRS1972

Space shuttle auxiliary propulsion system design study. Executive summary

The development and characteristics of an auxiliary propulsion system for space shuttle applications are presented. The system design data necessary for selection of preferred system concepts and the requirements for complementing component design and test programs are analyzed. The use of cryogenic oxygen and hydrogen as a propellant combination is explained on the basis of high vehicle impulse requirements, safety factors, reuse, and logistics considerations. The final configurations for the alternate propellant system, with primary emphasis on earth storable propellants is described.

Kelly, P. J.↗