Search NASA⌕ Search

SEARCH · Search NASA

Results for “programmatic”

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 1,225 records · Page 68

Radiation Hardness Assurance (RHA) for Space Systems

This presentation discusses radiation hardness assurance (RHA) for space systems, providing both the programmatic aspects of RHA and the RHA procedure. RHA consists of all activities undertaken to ensure that the electronics and materials of a space system perform to their design specifications after exposure to the space radiation environment. RHA also pertains to environment definition, part selection, part testing, spacecraft layout, radiation tolerant design, and mission/system/subsystems requirements. RHA procedure consists of establishing mission requirements, defining and evaluating the radiation hazard, selecting and categorizing the appropriate parts, and evaluating circuit response to hazard. The RHA approach is based on risk management and is confined only to parts, it includes spacecraft layout, system/subsystem/circuit design, and system requirements and system operations. RHA should be taken into account in the early phases of a program including the proposal and feasibility analysis phases.

Poivey, Christian↗

IC and Component Selection for Space Systems

This viewgraph presentation reviews the integrated circuit (IC) and selections of the IC components for space systems. Included in the discussion are a overview of semiconductors and the evolution of integrated circuit. It also reviews the three different viewpoints of the IC selection: technical, programmatic, and risk. From a radiation perspective there are four criteria for selecting ICs for space systems: guaranteed hardness, historical ground-based data, historical flight usage, and unknown assurance.

Label, Kenneth A.↗

NASA Activities: SpaceWire Working Group Meeting

This brief presentation highlights the efforts of the SpaceWire working group. The European Space Agency (ESA) contracted with the University of Dundee (UoD) to develop a prototype SpaceFibre Codec, which UoD has been demonstrated in hardware. UoD released a SpaceFibre Outline Specification which NASA plans to evaluate using a SpaceFibre sub-orbital demonstration (in development). Comments, questions and recommendations for ESA and UoD are provided here to generate discussion and expand participation. General findings are that the system level behavior of SpaceFibre is missing from the SpaceFibre Outline Specification, there is a need to understand how SpaceWire maps to SpaceFibre (and vice versa), and there is a need to clarify user interface to resolve inconsistencies. Architecture, virtual channel and programmatic recommendations are presented.

Rakow, Glenn↗

Scripting Module for the Satellite Orbit Analysis Program (SOAP)

This add-on module to the SOAP software can perform changes to simulation objects based on the occurrence of specific conditions. This allows the software to encompass simulation response of scheduled or physical events. Users can manipulate objects in the simulation environment under programmatic control. Inputs to the scripting module are Actions, Conditions, and the Script. Actions are arbitrary modifications to constructs such as Platform Objects (i.e. satellites), Sensor Objects (representing instruments or communication links), or Analysis Objects (user-defined logical or numeric variables). Examples of actions include changes to a satellite orbit ( v), changing a sensor-pointing direction, and the manipulation of a numerical expression. Conditions represent the circumstances under which Actions are performed and can be couched in If-Then-Else logic, like performing v at specific times or adding to the spacecraft power only when it is being illuminated by the Sun. The SOAP script represents the entire set of conditions being considered over a specific time interval. The output of the scripting module is a series of events, which are changes to objects at specific times. As the SOAP simulation clock runs forward, the scheduled events are performed. If the user sets the clock back in time, the events within that interval are automatically undone. This script offers an interface for defining scripts where the user does not have to remember the vocabulary of various keywords. Actions can be captured by employing the same user interface that is used to define the objects themselves. Conditions can be set to invoke Actions by selecting them from pull-down lists. Users define the script by selecting from the pool of defined conditions. Many space systems have to react to arbitrary events that can occur from scheduling or from the environment. For example, an instrument may cease to draw power when the area that it is tasked to observe is not in view. The contingency of the planetary body blocking the line of sight is a condition upon which the power being drawn is set to zero. It remains at zero until the observation objective is again in view. Computing the total power drawn by the instrument over a period of days or weeks can now take such factors into consideration. What makes the architecture especially powerful is that the scripting module can look ahead and behind in simulation time, and this temporal versatility can be leveraged in displays such as x-y plots. For example, a plot of a satellite s altitude as a function of time can take changes to the orbit into account.

Carnright, Robert↗

Human Factors Interface with Systems Engineering for NASA Human Spaceflights

This paper summarizes the past and present successes of the Habitability and Human Factors Branch (HHFB) at NASA Johnson Space Center s Space Life Sciences Directorate (SLSD) in including the Human-As-A-System (HAAS) model in many NASA programs and what steps to be taken to integrate the Human-Centered Design Philosophy (HCDP) into NASA s Systems Engineering (SE) process. The HAAS model stresses systems are ultimately designed for the humans; the humans should therefore be considered as a system within the systems. Therefore, the model places strong emphasis on human factors engineering. Since 1987, the HHFB has been engaging with many major NASA programs with much success. The HHFB helped create the NASA Standard 3000 (a human factors engineering practice guide) and the Human Systems Integration Requirements document. These efforts resulted in the HAAS model being included in many NASA programs. As an example, the HAAS model has been successfully introduced into the programmatic and systems engineering structures of the International Space Station Program (ISSP). Success in the ISSP caused other NASA programs to recognize the importance of the HAAS concept. Also due to this success, the HHFB helped update NASA s Systems Engineering Handbook in December 2007 to include HAAS as a recommended practice. Nonetheless, the HAAS model has yet to become an integral part of the NASA SE process. Besides continuing in integrating HAAS into current and future NASA programs, the HHFB will investigate incorporating the Human-Centered Design Philosophy (HCDP) into the NASA SE Handbook. The HCDP goes further than the HAAS model by emphasizing a holistic and iterative human-centered systems design concept.

Wong, Douglas T.↗

Ares I-X Flight Test--The Future Begins Here

In less than two years, the National Aeronautics and Space Administration (NASA) will launch the Ares I-X mission. This will be the first flight of the Ares I crew launch vehicle, which, together with the Ares V cargo launch vehicle, will eventually send humans to the Moon, Mars, and beyond. As the countdown to this first Ares mission continues, personnel from across the Ares I-X Mission Management Office (MMO) are finalizing designs and fabricating vehicle hardware for a 2009 launch. This paper will discuss the hardware and programmatic progress of the Ares I-X mission.

Davis, Stephan R.↗

Parts Selection for Space Systems - An Overview and Radiation Perspective

This viewgraph presentation describes the selection of electronic parts for aerospace systems from a space radiation perspective. The topics include: 1) The Trade Space Involved with Part Selection; 2) Understanding Risk; 3) Technical/Design Aspects; 4) Programmatic Overview; 5) Radiation Perspective; 6) Reliability Considerations; 7) An Example Ad hoc Battle; and 8) Sources of Radiation Data.

LaBel, Kenneth A.↗

Developing Analogy Cost Estimates for Space Missions

The analogy approach in cost estimation combines actual cost data from similar existing systems, activities, or items with adjustments for a new project's technical, physical or programmatic differences to derive a cost estimate for the new system. This method is normally used early in a project cycle when there is insufficient design/cost data to use as a basis for (or insufficient time to perform) a detailed engineering cost estimate. The major limitation of this method is that it relies on the judgment and experience of the analyst/estimator. The analyst must ensure that the best analogy or analogies have been selected, and that appropriate adjustments have been made. While analogy costing is common, there is a dearth of advice in the literature on the 'adjustment methodology', especially for hardware projects. This paper discusses some potential approaches that can improve rigor and repeatability in the analogy costing process.

space mission cost↗

Powering Exploration: The Ares I Crew Launch Vehicle and Ares V Cargo Launch Vehicle

The National Aeronautics and Space Administration (NASA)'s Constellation Program is depending on the Ares Projects to deliver the crew and cargo launch capabilities needed to send human explorers to the Moon and beyond. The Ares Projects continue to make progress toward design, component testing, and early flight testing of the Ares I crew launch vehicle, as well as early design work for Ares V cargo launch vehicle. Ares I and Ares V will form the core space launch capabilities the United States needs to continue its pioneering tradition as a spacefaring nation. This paper will discuss programmatic, design, fabrication, and testing progress toward building these new launch vehicles.

Cook, Stephen A.↗

Ares I-X Flight Test - The Future Begins Here

In less than two years, the National Aeronautics and Space Administration (NASA) will launch the Ares I-X mission. This will be the first flight of the Ares I crew launch vehicle, which, together with the Ares V cargo launch vehicle, will eventually send humans to the Moon, Mars, and beyond. As the countdown to this first Ares mission continues, personnel from across the Ares I-X Mission Management Office (MMO) are finalizing designs and fabricating vehicle hardware for an April 2009 launch. This paper will discuss the hardware and programmatic progress of the Ares I-X mission. Like the Apollo program, the Ares launch vehicles will rely upon extensive ground, flight, and orbital testing before sending the Orion crew exploration vehicle into space with humans on board. The first flight of Ares I, designated Ares I-X, will be a suborbital development flight test. Ares I-X gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack; understand how to control its roll during flight; better characterize the severe stage separation environments that the upper stage engine will experience during future operational flights; and demonstrate the first stage recovery system. NASA also will begin modifying the launch infrastructure and fine-tuning ground and mission operations, as the agency makes the transition from the Space Shuttle to the Ares/Orion system.

Davis, Stephan R.↗

The J-2X Upper Stage Engine: From Heritage to Hardware

NASA's Global Exploration Strategy requires safe, reliable, robust, efficient transportation to support sustainable operations from Earth to orbit and into the far reaches of the solar system. NASA selected the Ares I crew launch vehicle and the Ares V cargo launch vehicle to provide that transportation. Guiding principles in creating the architecture represented by the Ares vehicles were the maximum use of heritage hardware and legacy knowledge, particularly Space Shuttle assets, and commonality between the Ares vehicles where possible to streamline the hardware development approach and reduce programmatic, technical, and budget risks. The J-2X exemplifies those goals. It was selected by the Exploration Systems Architecture Study (ESAS) as the upper stage propulsion for the Ares I Upper Stage and the Ares V Earth Departure Stage (EDS). The J-2X is an evolved version ofthe historic J-2 engine that successfully powered the second stage of the Saturn I launch vehicle and the second and third stages of the Saturn V launch vehicle. The Constellation architecture, however, requires performance greater than its predecessor. The new architecture calls for larger payloads delivered to the Moon and demands greater loss of mission reliability and numerous other requirements associated with human rating that were not applied to the original J-2. As a result, the J-2X must operate at much higher temperatures, pressures, and flow rates than the heritage J-2, making it one of the highest performing gas generator cycle engines ever built, approaching the efficiency of more complex stage combustion engines. Development is focused on early risk mitigation, component and subassembly test, and engine system test. The development plans include testing engine components, including the subscale injector, main igniter, powerpack assembly (turbopumps, gas generator and associated ducting and structural mounts), full-scale gas generator, valves, and control software with hardware-in-the-loop. Testing expanded in 2007, accompanied by the refinement of the design through several key milestones. This paper discusses those 2007 tests and milestones, as well as updates key developments in 2008.

Byrd, THomas↗

The EOS AURA Tropospheric Emission Spectrometer (TES): Status of the Program

This slide presentation is a programmatic overview covering some of the highlights of the mission and serve as an introduction to the accompanying presentations at the workshop. It reviews the goals and the products of the TES experiment, a simplified chemistry of ozone in both the stratosphere and troposphere, a description of the instrument, and the TES operational modes. Included are graphs showing some of the results of TES analysis of the key constituents of the tropospheric chemistry and the inter-regional transport.

Fourier Transform Infrared (FTIR)↗

National Aeronautics and Space Administration Biological Specimen Repository

The National Aeronautics and Space Administration Biological Specimen Repository (Repository) is a storage bank that is used to maintain biological specimens over extended periods of time and under well-controlled conditions. Samples from the International Space Station (ISS), including blood and urine, will be collected, processed and archived during the preflight, inflight and postflight phases of ISS missions. This investigation has been developed to archive biosamples for use as a resource for future space flight related research. The International Space Station (ISS) provides a platform to investigate the effects of microgravity on human physiology prior to lunar and exploration class missions. The storage of crewmember samples from many different ISS flights in a single repository will be a valuable resource with which researchers can study space flight related changes and investigate physiological markers. The development of the National Aeronautics and Space Administration Biological Specimen Repository will allow for the collection, processing, storage, maintenance, and ethical distribution of biosamples to meet goals of scientific and programmatic relevance to the space program. Archiving of the biosamples will provide future research opportunities including investigating patterns of physiological changes, analysis of components unknown at this time or analyses performed by new methodologies.

McMonigal, Kathleen A.↗

The Ares I Crew Launch Vehicle: Human Space Access for the Moon and Beyond

The National Aeronautics and Space Administration (NASA)'s Constellation Program is depending on the Ares Projects to deliver the crew launch capabilities needed to send human explorers to the Moon and beyond. The Ares Projects continue to make progress toward design, component testing, and early flight testing of the Ares I crew launch vehicle (Figure 1), the United States first new human-rated launch vehicle in over 25 years. Ares I will provide the core space launch capabilities the United States needs to continue providing crew and cargo access to the International Space Station (ISS), maintaining the U.S. pioneering tradition as a spacefaring nation, and enabling cooperative international ventures to the Moon and beyond. This paper will discuss programmatic, design, fabrication, and testing progress toward building this new launch vehicle.

Cook, Stephen A.↗

Overview of Key Saturn Probe Mission Trades

Ongoing studies, performed at NASA/JPL over the past two years in support of NASA's SSE Roadmap activities, proved the feasibility of a NF class Saturn probe mission. I. This proposed mission could also provide a good opportunity for international collaboration with the proposed Cosmic Vision KRONOS mission: a) With ESA contributed probes (descent modules) on a NASA lead mission; b) Early 2017 launch could be a good programmatic option for ESA-CV/NASA-NF. II. A number of mission architectures could be suitable for this mission: a) Probe Relay based architecture with short flight time (approx. 6.3-7 years); b) DTE probe telecom based architecture with long flight time (-11 years), and low probe data rate, but with the probes decoupled from the carrier, allowing for polar trajectories I orbiter. This option may need technology development for telecom; c) Orbiter would likely impact mission cost over flyby, but would provide significantly higher science return. The Saturn probes mission is expected to be identified in NASA's New Frontiers AO. Thus, further studies are recommended to refine the most suitable architecture. International collaboration is started through the KRONOS proposal work; further collaborated studies will follow once KRONOS is selected in October under ESA's Cosmic Vision Program.

probes↗

MSL Project Update

Mars Science Lab (MSL) Project activities over the last 3-4 months focused on: a) Payload accommodation; b) Flight system architecture definitization; c) Program architecture support. Baseline project concept is to develop and fly two identical vehicles with launches in 2009 and 2011: a) Significant programmatic uncertainty remains due to NASA strategic issues (Shuttle Return to flight, Hubble servicing, CEV, etc.); b) Final "decisions" on future program not likely for 3-4 months; c) To maintain viability for a 2009 launch, the project must rapidly move into implementation mode despite this uncertainty. Near term activities: a) Converge baseline flight system architecture & instrument accommodation - June; b) Instrument accomodation reviews (IARs) are completed for DAN, MSSS instruments; c) Develop project-wide implementation plan & integrated schedule - June; d) Conduct grassroots cost exercise - July/August; e) Hold Preliminary Mission System Review - September.

Mars↗

Orchestrator Telemetry Processing Pipeline

Orchestrator is a software application infrastructure for telemetry monitoring, logging, processing, and distribution. The architecture has been applied to support operations of a variety of planetary rovers. Built in Java with the Eclipse Rich Client Platform, Orchestrator can run on most commonly used operating systems. The pipeline supports configurable parallel processing that can significantly reduce the time needed to process a large volume of data products. Processors in the pipeline implement a simple Java interface and declare their required input from upstream processors. Orchestrator is programmatically constructed by specifying a list of Java processor classes that are initiated at runtime to form the pipeline. Input dependencies are checked at runtime. Fault tolerance can be configured to attempt continuation of processing in the event of an error or failed input dependency if possible, or to abort further processing when an error is detected. This innovation also provides support for Java Message Service broadcasts of telemetry objects to clients and provides a file system and relational database logging of telemetry. Orchestrator supports remote monitoring and control of the pipeline using browser-based JMX controls and provides several integration paths for pre-compiled legacy data processors. At the time of this reporting, the Orchestrator architecture has been used by four NASA customers to build telemetry pipelines to support field operations. Example applications include high-volume stereo image capture and processing, simultaneous data monitoring and logging from multiple vehicles. Example telemetry processors used in field test operations support include vehicle position, attitude, articulation, GPS location, power, and stereo images.

Powell, Mark↗

Results From the John Glenn Biomedical Engineering Consortium. A Success Story for NASA and Northeast Ohio

The John Glenn Biomedical Engineering Consortium was established by NASA in 2002 to formulate and implement an integrated, interdisciplinary research program to address risks faced by astronauts during long-duration space missions. The consortium is comprised of a preeminent team of Northeast Ohio institutions that include Case Western Reserve University, the Cleveland Clinic, University Hospitals Case Medical Center, The National Center for Space Exploration Research, and the NASA Glenn Research Center. The John Glenn Biomedical Engineering Consortium research is focused on fluid physics and sensor technology that addresses the critical risks to crew health, safety, and performance. Effectively utilizing the unique skills, capabilities and facilities of the consortium members is also of prime importance. Research efforts were initiated with a general call for proposals to the consortium members. The top proposals were selected for funding through a rigorous, peer review process. The review included participation from NASA's Johnson Space Center, which has programmatic responsibility for NASA's Human Research Program. The projects range in scope from delivery of prototype hardware to applied research that enables future development of advanced technology devices. All of the projects selected for funding have been completed and the results are summarized. Because of the success of the consortium, the member institutions have extended the original agreement to continue this highly effective research collaboration through 2011.

Nall, Marsha M.↗