SEARCH · Engineering Papers

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 865 records · Page 48

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Open Architecture Standard for NASA's Software-Defined Space Telecommunications Radio Systems

NASA is developing an architecture standard for software-defined radios used in space- and ground-based platforms to enable commonality among radio developments to enhance capability and services while reducing mission and programmatic risk. Transceivers (or transponders) with functionality primarily defined in software (e.g., firmware) have the ability to change their functional behavior through software alone. This radio architecture standard offers value by employing common waveform software interfaces, method of instantiation, operation, and testing among different compliant hardware and software products. These common interfaces within the architecture abstract application software from the underlying hardware to enable technology insertion independently at either the software or hardware layer. This paper presents the initial Space Telecommunications Radio System (STRS) Architecture for NASA missions to provide the desired software abstraction and flexibility while minimizing the resources necessary to support the architecture.

Reinhart, Richard C.↗

NASA NTRS2008

James Webb Space Telescope - Applying Lessons Learned to I&T

The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is that core components, such as the command and telemetry system and the project database, should be developed early, used throughout development and testing, and evolved into the operational system. The purpose of applying lessons learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost efficiency, and schedule optimization. In the cited example, the early development and use of the operational command and telemetry system as well as the establishment of the intended operational database will allow these components to be used by the developers of various spacecraft components such that development, testing, and operations will all use the same core components. This will reduce risk through the elimination of transitions between development and operational components and improve end product quality by extending the verification of those components through continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground Segment integration and test program.

Johns, Alan↗

NASA NTRS2006

Systems Engineering and Integration for Technology Programs

The Architecture, Habitability & Integration group (AH&I) is a system engineering and integration test team within the NASA Crew and Thermal Systems Division (CTSD) at Johnson Space Center. AH&I identifies and resolves system-level integration issues within the research and technology development community. The timely resolution of these integration issues is fundamental to the development of human system requirements and exploration capability. The integration of the many individual components necessary to construct an artificial environment is difficult. The necessary interactions between individual components and systems must be approached in a piece-wise fashion to achieve repeatable results. A formal systems engineering (SE) approach to define, develop, and integrate quality systems within the life support community has been developed. This approach will allow a Research & Technology Program to systematically approach the development, management, and quality of technology deliverables to the various exploration missions. A tiered system engineering structure has been proposed to implement best systems engineering practices across all development levels from basic research to working assemblies. These practices will be implemented through a management plan across all applicable programs, projects, elements and teams. While many of the engineering practices are common to other industries, the implementation is specific to technology development. An accounting of the systems engineering management philosophy will be discussed and the associated programmatic processes will be presented.

Kennedy, Kruss J.↗

NASA NTRS2008

Testing Microshutter Arrays Using Commercial FPGA Hardware

NASA is developing micro-shutter arrays for the Near Infrared Spectrometer (NIRSpec) instrument on the James Webb Space Telescope (JWST). These micro-shutter arrays allow NIRspec to do Multi Object Spectroscopy, a key part of the mission. Each array consists of 62414 individual 100 x 200 micron shutters. These shutters are magnetically opened and held electrostatically. Individual shutters are then programmatically closed using a simple row/column addressing technique. A common approach to provide these data/clock patterns is to use a Field Programmable Gate Array (FPGA). Such devices require complex VHSIC Hardware Description Language (VHDL) programming and custom electronic hardware. Due to JWST's rapid schedule on the development of the micro-shutters, rapid changes were required to the FPGA code to facilitate new approaches being discovered to optimize the array performance. Such rapid changes simply could not be made using conventional VHDL programming. Subsequently, National Instruments introduced an FPGA product that could be programmed through a Labview interface. Because Labview programming is considerably easier than VHDL programming, this method was adopted and brought success. The software/hardware allowed the rapid change the FPGA code and timely results of new micro-shutter array performance data. As a result, numerous labor hours and money to the project were conserved.

Rapchun, David↗

NASA NTRS2008

Refinements in the Design of the Ares V Cargo Launch Vehicle for NASA's, Exploration Strategy

NASA is developing a new launch vehicle fleet to fulfill the national goals of replacing the shuttle fleet, completing the International Space Station (ISS), and exploring the Moon on the way to eventual exploration of Mars and beyond. Programmatic and technical decisions during early architecture studies and subsequent design activities were focused on safe, reliable operationally efficient vehicles that could support a sustainable exploration program. A pair of launch vehicles was selected to support those goals the Ares I crew launch vehicle and the Ares V cargo launch vehicle. They will be the first new human-rated launch vehicles developed by NASA in more than 30 years (Figure 1). Ares I will be the first to fly, beginning space station ferry operations no later than 2015. It will be able to carry up to six astronauts to ISS or support up to four astronauts for expeditions to the moon. Ares V is scheduled to be operational in the 2020 timeframe and will provide the propulsion systems and payload to truly extend human exploration beyond low-Earth orbit. (LEO).

Creech, Steve↗

NASA NTRS2007

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↗

NASA NTRS2007

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 NTRS2008

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↗

NASA NTRS2008

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↗

NASA NTRS2009

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.↗

NASA NTRS2007

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

Davis, Stephan R.↗

NASA NTRS2008

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.↗

NASA NTRS2004

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↗

NASA NTRS2008

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.↗

NASA NTRS2008

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.↗

NASA NTRS2008

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↗

NASA NTRS2005

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)↗

NASA NTRS2008

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.↗