SEARCH · Search NASA

Results for “programmatic requirements”

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 199 records · Page 11

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Risks Associated with Long-Term Spaceflight

Requirements driving the HHC work and deliverables are derived from the Human Research Program requirements, as well as Agency standards regarding the maintenance of human health and performance and a programmatic review of the existing evidence to support identified risks. Agency human health and performance standards define acceptable risk for each type and duration of exploration mission. It is critical to have the best available scientific and clinical evidence in setting and validating these standards. In addition, it is imperative that the best available evidence on preventing and mitigating human health and performance risks is incorporated into exploration mission and vehicle designs.

Francisco, David↗

NASA NTRS2007

Report of the NASA Science Definition Team for the Mars Science Orbiter (MSO)

NASA is considering that its Mars Exploration Program (MEP) will launch an orbiter to Mars in the 2013 launch opportunity. To further explore this opportunity, NASA has formed a Science Definition Team (SDT) for this orbiter mission, provisionally called the Mars Science Orbiter (MSO). Membership and leadership of the SDT are given in Appendix 1. Dr. Michael D. Smith chaired the SDT. The purpose of the SDT was to define the: 1) Scientific objectives of an MSO mission to be launched to Mars no earlier than the 2013 launch opportunity, building on the findings for Plan A [Atmospheric Signatures and Near-Surface Change] of the Mars Exploration Program Analysis Group (MEPAG) Second Science Analysis Group (SAG-2); 2) Science requirements of instruments that are most likely to make high priority measurements from the MSO platform, giving due consideration to the likely mission, spacecraft and programmatic constraints. The possibilities and opportunities for international partners to provide the needed instrumentation should be considered; 3) Desired orbits and mission profile for optimal scientific return in support of the scientific objectives, and the likely practical capabilities and the potential constraints defined by the science requirements; and 4) Potential science synergies with, or support for, future missions, such as a Mars Sample Return. This shall include imaging for evaluation and certification of future landing sites. As a starting point, the SDT was charged to assume spacecraft capabilities similar to those of the Mars Reconnaissance Orbiter (MRO). The SDT was further charged to assume that MSO would be scoped to support telecommunications relay of data from, and commands to, landed assets, over a 10 Earth year period following orbit insertion. Missions supported by MSO may include planned international missions such as EXOMARS. The MSO SDT study was conducted during October - December 2007. The SDT was directed to complete its work by December 15, 2007. This rapid turn-around was required in order to allow time to prepare an Announcement of Opportunity (AO) for science investigations, to be released in early 2008.

Smith, Michael↗

NASA NTRS1998

Aerothermodynamic Flight Simulation Capabilities for Aerospace Vehicles

Aerothermodynamics, encompassing aerodynamics, aeroheating, and fluid dynamics and physical processes, is the genesis for the design and development of advanced space transportation vehicles and provides crucial information to other disciplines such as structures, materials, propulsion, avionics, and guidance, navigation and control. Sources of aerothermodynamic information are ground-based facilities, Computational Fluid Dynamic (CFD) and engineering computer codes, and flight experiments. Utilization of this aerothermodynamic triad provides the optimum aerothermodynamic design to safely satisfy mission requirements while reducing design conservatism, risk and cost. The iterative aerothermodynamic process for initial screening/assessment of aerospace vehicle concepts, optimization of aerolines to achieve/exceed mission requirements, and benchmark studies for final design and establishment of the flight data book are reviewed. Aerothermodynamic methodology centered on synergism between ground-based testing and CFD predictions is discussed for various flow regimes encountered by a vehicle entering the Earth s atmosphere from low Earth orbit. An overview of the resources/infrastructure required to provide accurate/creditable aerothermodynamic information in a timely manner is presented. Impacts on Langley s aerothermodynamic capabilities due to recent programmatic changes such as Center reorganization, downsizing, outsourcing, industry (as opposed to NASA) led programs, and so forth are discussed. Sample applications of these capabilities to high Agency priority, fast-paced programs such as Reusable Launch Vehicle (RLV)/X-33 Phases I and 11, X-34, Hyper-X and X-38 are presented and lessons learned discussed. Lastly, enhancements in ground-based testing/CFD capabilities necessary to partially/fully satisfy future requirements are addressed.

Miller, Charles G.↗

NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗

NASA NTRS1980

Space Construction System Analysis. Part 2: Executive summary

A detailed, end-to-end analysis of the activities, techniques, equipment and Shuttle provisions required to construct a reference project system is described. Included are: platform definition; construction analysis; cost and programmatics; and space construction experiments concepts.

Source record↗

NASA NTRS1994

A modular approach for automated sample preparation and chemical analysis

Changes in international relations, especially within the past several years, have dramatically affected the programmatic thrusts of the U.S. Department of Energy (DOE). The DOE now is addressing the environmental cleanup required as a result of 50 years of nuclear arms research and production. One major obstacle in the remediation of these areas is the chemical determination of potentially contaminated material using currently acceptable practices. Process bottlenecks and exposure to hazardous conditions pose problems for the DOE. One proposed solution is the application of modular automated chemistry using Standard Laboratory Modules (SLM) to perform Standard Analysis Methods (SAM). The Contaminant Analysis Automation (CAA) Program has developed standards and prototype equipment that will accelerate the development of modular chemistry technology and is transferring this technology to private industry.

Clark, Michael L.↗

NASA NTRS1998

The Aircraft Morphing Program

In the last decade smart technologies have become enablers that cut across traditional boundaries in materials science and engineering. Here we define smart to mean embedded actuation, sensing, and control logic in a tightly coupled feedback loop. While multiple successes have been achieved in the laboratory, we have yet to see the general applicability of smart devices to real aircraft systems. The NASA Aircraft Morphing program is an attempt to couple research across a wide range of disciplines to integrate smart technologies into high payoff aircraft applications. The program bridges research in seven individual disciplines and combines the effort into activities in three primary program thrusts. System studies are used to assess the highest- payoff program objectives, and specific research activities are defined to address the technologies required for development of smart aircraft systems. In this paper we address the overall program goals and programmatic structure, and discuss the challenges associated with bringing the technologies to fruition.

Wlezien, R. W.↗

NASA NTRS2005

EVA Requirements for Exploration EVAs

The exploration program proposed by the President will require extensive extravehicular operations in a wide range of environments. These include Og EVAs in planetary orbits as well as potential contingency EVAs during inter-planetary flight and surface operations on the moon and Mars. The EVA environments and mission requirements are very different for each of these. Commonality among such systems is highly desirable from the programmatic standpoint but the dramatic differences in EVA environments will have a profound impact on EVA system design. This paper will examine the relevant environmental parameters and discuss their impacts on EVA system design. An EVA design philosophy that maximizes EVA system commonality will be discussed.

Webbon, Bruce↗

NASA NTRS2011

Small Rocket/Spacecraft Technology (SMART) Platform

The NASA Goddard Space Flight Center (GSFC) and the Department of Defense Operationally Responsive Space (ORS) Office are exercising a multi-year collaborative agreement focused on a redefinition of the way space missions are designed and implemented. A much faster, leaner and effective approach to space flight requires the concerted effort of a multi-agency team tasked with developing the building blocks, both programmatically and technologically, to ultimately achieve flights within 7-days from mission call-up. For NASA, rapid mission implementations represent an opportunity to find creative ways for reducing mission life-cycle times with the resulting savings in cost. This in tum enables a class of missions catering to a broader audience of science participants, from universities to private and national laboratory researchers. To that end, the SMART (Small Rocket/Spacecraft Technology) micro-spacecraft prototype demonstrates an advanced avionics system with integrated GPS capability, high-speed plug-and-playable interfaces, legacy interfaces, inertial navigation, a modular reconfigurable structure, tunable thermal technology, and a number of instruments for environmental and optical sensing. Although SMART was first launched inside a sounding rocket, it is designed as a free-flyer.

Esper, Jaime↗

NASA NTRS1972

Nuclear applications in manned space station

The zirconium hydride reactor, coupled to a thermo-electric or Brayton conversion system, and the Pu 238 isotope/Brayton system, are considered to be the viable nuclear candidates for the modular space station electrical power system. The basic integration aspects of these nuclear electrical power systems are reviewed, including unique requirements imposed by the buildup and incremental utilization considerations of the modular station. Also treated are the various programmatic aspects of nuclear power system design and selection.

Brooksbank, W. A., Jr.↗

NASA NTRS1981

Materials experiment carrier concepts definition study. Volume 1: Executive summary, part 2

The materials experiment carrier (MEC) is an optimized carrier for near term and advanced materials processing in space (MPS) research and commercial payloads. When coupled with the space platform (SP), the MEC can provide the extended duration, high power and low acceleration environment the MPS payload typically requires. The lowest cost, technically reasonable first step MEC that meets the MPS program missions objectives with minimum programmatic risks is defined. The effectiveness of the initial MEC/space platform idea for accommodating high priority, multidiscipline, R&D and commercial MPS payloads, and conducting MPS payload oprations at affordable funding and acceptable productivity levels is demonstrated.

Source record↗

NASA NTRS1991

Computational needs survey of NASA automation and robotics missions. Volume 1: Survey and results

NASA's operational use of advanced processor technology in space systems lags behind its commercial development by more than eight years. One of the factors contributing to this is that mission computing requirements are frequently unknown, unstated, misrepresented, or simply not available in a timely manner. NASA must provide clear common requirements to make better use of available technology, to cut development lead time on deployable architectures, and to increase the utilization of new technology. A preliminary set of advanced mission computational processing requirements of automation and robotics (A&R) systems are provided for use by NASA, industry, and academic communities. These results were obtained in an assessment of the computational needs of current projects throughout NASA. The high percent of responses indicated a general need for enhanced computational capabilities beyond the currently available 80386 and 68020 processor technology. Because of the need for faster processors and more memory, 90 percent of the polled automation projects have reduced or will reduce the scope of their implementation capabilities. The requirements are presented with respect to their targeted environment, identifying the applications required, system performance levels necessary to support them, and the degree to which they are met with typical programmatic constraints. Volume one includes the survey and results. Volume two contains the appendixes.

Davis, Gloria J.↗

NASA NTRS1991

Computational needs survey of NASA automation and robotics missions. Volume 2: Appendixes

NASA's operational use of advanced processor technology in space systems lags behind its commercial development by more than eight years. One of the factors contributing to this is the fact that mission computing requirements are frequency unknown, unstated, misrepresented, or simply not available in a timely manner. NASA must provide clear common requirements to make better use of available technology, to cut development lead time on deployable architectures, and to increase the utilization of new technology. Here, NASA, industry and academic communities are provided with a preliminary set of advanced mission computational processing requirements of automation and robotics (A and R) systems. The results were obtained in an assessment of the computational needs of current projects throughout NASA. The high percent of responses indicated a general need for enhanced computational capabilities beyond the currently available 80386 and 68020 processor technology. Because of the need for faster processors and more memory, 90 percent of the polled automation projects have reduced or will reduce the scope of their implemented capabilities. The requirements are presented with respect to their targeted environment, identifying the applications required, system performance levels necessary to support them, and the degree to which they are met with typical programmatic constraints. Here, appendixes are provided.

Davis, Gloria J.↗

NASA NTRS1991

Lunar base as a precursor to Mars exploration and settlement

A well planned program of human exploration of the moon is suggested which would provide a base for increasing human capabilities and experience to levels required for Mars exploration. A strategy intended for immediate Mars exploration and settlement is considered to incur serious programmatic risks from current lack of knowledge on human performance on long-duration deep space missions and lack of experience in designing human space systems. The lunar program provides an opportunity to build up space capability in an evolutionary way and to broaden the participation of the educational system in the space exploration.

Mendell, Wendell W.↗

NASA NTRS1992

Space transfer vehicle concepts and requirements study, phase 2

This final report is a compilation of the Phase 1 and Phase 2 study findings and is intended as a Space Transfer Vehicle (STV) 'users guide' rather than an exhaustive explanation of STV design details. It provides a database for design choices in the general areas of basing, reusability, propulsion, and staging; with selection criteria based on cost, performance, available infrastructure, risk, and technology. The report is organized into the following three parts: (1) design guide; (2) STV Phase 1 Concepts and Requirements Study Summary; and (3) STV Phase 2 Concepts and Requirements Study Summary. The overall objectives of the STV study were to: (1) define preferred STV concepts capable of accommodating future exploration missions in a cost-effective manner; (2) determine the level of technology development required to perform these missions in the most cost effective manner; and (3) develop a decision database of programmatic approaches for the development of an STV concept.

Cannon, Jeffrey H.↗

NASA NTRS2015

Comparison of Human Exploration Architecture and Campaign Approaches

As part of an overall focus on space exploration, National Aeronautics and Space Administration (NASA) continues to evaluate potential approaches for sending humans beyond low Earth orbit (LEO). In addition, various external organizations are studying options for beyond LEO exploration. Recent studies include NASA's Evolvable Mars Campaign and Design Reference Architecture (DRA) 5.0, JPL's Minimal Mars Architecture; the Inspiration Mars mission; the Mars One campaign; and the Global Exploration Roadmap (GER). Each of these potential exploration constructs applies unique methods, architectures, and philosophies for human exploration. It is beneficial to compare potential approaches in order to better understand the range of options available for exploration. Since most of these studies were conducted independently, the approaches, ground rules, and assumptions used to conduct the analysis differ. In addition, the outputs and metrics presented for each construct differ substantially. This paper will describe the results of an effort to compare and contrast the results of these different studies under a common set of metrics. The paper will first present a summary of each of the proposed constructs, including a description of the overall approach and philosophy for exploration. Utilizing a common set of metrics for comparison, the paper will present the results of an evaluation of the potential benefits, critical challenges, and uncertainties associated with each construct. The analysis framework will include a detailed evaluation of key characteristics of each construct. These will include but are not limited to: a description of the technology and capability developments required to enable the construct and the uncertainties associated with these developments; an analysis of significant operational and programmatic risks associated with that construct; and an evaluation of the extent to which exploration is enabled by the construct, including the destinations visited and the exploration capabilities provided at those destinations. Based upon the comparison of constructs, the paper will identify trends and lessons learned across all of the candidate studies.

Goodliff, Kandyce↗

NASA NTRS2003

Experiences with Testing the Largest Ground System NASA Has Ever Built

In the 1980s, the National Aeronautics and Space Administration (NASA) embarked upon a major Earth-focused program called Mission to Planet Earth. The Goddard Space Flight Center (GSFC) was selected to manage and develop a key component - the Earth Observing System (EOS). The EOS consisted of four major missions designed to monitor the Earth. The missions included 4 spacecraft. Terra (launched December 1999), Aqua (launched May 2002), ICESat (Ice, Cloud, and Land Elevation Satellite, launched January 2003), and Aura (scheduled for launch January 2004). The purpose of these missions was to provide support for NASA s long-term research effort for determining how human-induced and natural changes affect our global environment. The EOS Data and Information System (EOSDIS), a globally distributed, large-scale scientific system, was built to support EOS. Its primary function is to capture, collect, process, and distribute the most voluminous set of remotely sensed scientific data to date estimated to be 350 Gbytes per day. The EOSDIS is composed of a diverse set of elements with functional capabilities that require the implementation of a complex set of computers, high-speed networks, mission-unique equipment, and associated Information Technology (IT) software along with mission-specific software. All missions are constrained by schedule, budget, and staffing resources, and rigorous testing has been shown to be critical to the success of each mission. This paper addresses the challenges associated with the planning, test definition. resource scheduling, execution, and discrepancy reporting involved in the mission readiness testing of a ground system on the scale of EOSDIS. The size and complexity of the mission systems supporting the Aqua flight operations, for example, combined with the limited resources available, prompted the project to challenge the prevailing testing culture. The resulting success of the Aqua Mission Readiness Testing (MRT) program was due in no small measure to re-structuring the traditional programmatic and technical approach to a more efficient and robust program. Programmatically, it meant gaining the endorsement, commitment, and cooperation of the numerous subsystem element managers and other stakeholder organizations. Technically, it required an MRT program that was agile, could rapidly adapt to requirements changes, and was flexible in its overall approach. Furthermore, this paper addresses the following questions: 1. What are the key ingredients (e.g., test tools, organization) needed to conduct a successful MRT program? 2. What distinguishes EOS MRT from the traditional system testing approach? 3. Where should the focus of testing be since it is infeasible to test every element or subsystem? 4. How can MRT be applied effectively to other systems or missions? To provide answers to these questions, this paper relies heavily on real-life, hands-on experiences ("lessons learned") gained during mission readiness testing of the Terra ground system and, most recently, the Aqua and ICESat missions. Moreover, this paper explores how lessons learned were turned into lessons applied for the upcoming Aura mission. Although derived from the EOS missions, MRT techniques and strategies can be applied to enhance the testing of other missions.

Lehtonen, Ken↗

NASA NTRS2019

Reusing Data and Metadata to Create New Metadata Through Machine-Learning & Other Programmatic Methods

Recent improvements in natural language processing (NLP) enable metadata to be created programmatically from reused original metadata or even the dataset itself. Transfer-learning applied to NLP has greatly improved performance and reduced training data requirements. In this talk, we’ll compare machine-generated metadata to human-generated metadata and discuss characteristics of metadata and data archives that affect suitability for machine-learning reuse of metadata. Where as human-generated metadata is often populated once, populated from the perspective of data supplier, populated by many individuals with different words for the same thing, and limited in length, machine-generated metadata can be updated any number of times, generated from the perspective of any user, constrained to a standardized set of terms that can be evolved over time, and be any length required. Machine-learning generated metadata offers benefits but also additional needs in terms of version control, process transparency, human-computer interaction, and IT requirements. As a successful example, we’ll discuss how a dataset of abstracts and associated human-tagged keywords from a standardized list of several thousand keywords were used to create a machine-learning model that predicted keyword metadata for open-source code projects on code.nasa.gov. We’ll also discuss a less successful example from data.nasa.gov to show how data archive architecture and characteristics of initial metadata can be strong controls on how easy it is to leverage programmatic methods to reuse metadata to create additional metadata.

Gosses, Justin↗