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,279 records · Page 71

Space Shuttle Ascent Flight Design Process: Evolution and Lessons Learned

The Space Shuttle Ascent Flight Design team is responsible for defining a launch to orbit trajectory profile that satisfies all programmatic mission objectives and defines the ground and onboard reconfiguration requirements for this high-speed and demanding flight phase. This design, verification and reconfiguration process ensures that all applicable mission scenarios are enveloped within integrated vehicle and spacecraft certification constraints and criteria, and includes the design of the nominal ascent profile and trajectory profiles for both uphill and ground-to-ground aborts. The team also develops a wide array of associated training, avionics flight software verification, onboard crew and operations facility products. These key ground and onboard products provide the ultimate users and operators the necessary insight and situational awareness for trajectory dynamics, performance and event sequences, abort mode boundaries and moding, flight performance and impact predictions for launch vehicle stages for use in range safety, and flight software performance. These products also provide the necessary insight to or reconfiguration of communications and tracking systems, launch collision avoidance requirements, and day of launch crew targeting and onboard guidance, navigation and flight control updates that incorporate the final vehicle configuration and environment conditions for the mission. Over the course of the Space Shuttle Program, ascent trajectory design and mission planning has evolved in order to improve program flexibility and reduce cost, while maintaining outstanding data quality. Along the way, the team has implemented innovative solutions and technologies in order to overcome significant challenges. A number of these solutions may have applicability to future human spaceflight programs.

Picka, Bret A.↗

Employing Geodatabases for Planetary Mapping Conduct - Requirements, Concepts and Solutions

Planetary geologic mapping has become complex in terms of merging and co-registering a variety of different datasets for analysis and mapping. But it has also become more convenient when it comes to conducting actual (geoscientific) mapping with the help of desktop Geographic Information Systems (GIS). The complexity and variety of data, however, are major issues that need to be taken care of in order to provide mappers with a consistent and easy-to-use mapping basis. Furthermore, a high degree of functionality and interoperability of various commercial and open-source GIS and remote sensing applications allow mappers to organize map data, map components and attribute data in a more sophisticated and intuitional way when compared to workflows 15 years ago. Integration of mapping results of different groups becomes an awkward task as each mapper follows his/her own style, especially if mapping conduct is not coordinated and organized programmatically. Problems of data homogenization start with various interpretations and implementations of planetary map projections and reference systems which form the core component of any mapping and analysis work. If the data basis is inconsistent, mapping results in terms of objects georeference become hard to integrate. Apart from data organization and referencing issues, which are important on the mapping as well as the data-processing side of every project, the organization of planetary geologic map units and attributes, as well as their representation within a common GIS environment, are key components that need to be taken care of in a consistent and persistent way.

vanGasselt, Stephan↗

Space Telecommunications Radio System (STRS) Architecture Standard. Release 1.02.1

This document contains the NASA 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.

Reinhart, Richard C.↗

Propulsion Controls and Diagnostics Research in Support of NASA Aeronautics and Exploration Mission Programs

The Controls and Dynamics Branch (CDB) at National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) in Cleveland, Ohio, is leading and participating in various projects in partnership with other organizations within GRC and across NASA, the U.S. aerospace industry, and academia to develop advanced propulsion controls and diagnostics technologies that will help meet the challenging goals of NASA programs under the Aeronautics Research and Exploration Systems Missions. This paper provides a brief overview of the various CDB tasks in support of the NASA programs. The programmatic structure of the CDB activities is described along with a brief overview of each of the CDB tasks including research objectives, technical challenges, and recent accomplishments. These tasks include active control of propulsion system components, intelligent propulsion diagnostics and control for reliable fault identification and accommodation, distributed engine control, and investigations into unsteady propulsion systems.

Garg, Sanjay↗

Deep Space Habitat Team: HEFT Phase 2 Effects

HEFT was a NASA-wide team that performed analyses of architectures for human exploration beyond LEO, evaluating technical, programmatic, and budgetary issues to support decisions at the highest level of the agency in HSF planning. HEFT Phase I (April - September, 2010) and Phase II (September - December, 2010) examined a broad set of Human Exploration of Near Earth Objects (NEOs) Design Reference Missions (DRMs), evaluating such factors as elements, performance, technologies, schedule, and cost. At end of HEFT Phase 1, an architecture concept known as DRM 4a represented the best available option for a full capability NEO mission. Within DRM4a, the habitation system was provided by Deep Space Habitat (DSH), Multi-Mission Space Exploration Vehicle (MMSEV), and Crew Transfer Vehicle (CTV) pressurized elements. HEFT Phase 2 extended DRM4a, resulting in DRM4b. Scrubbed element-level functionality assumptions and mission Concepts of Operations. Habitation Team developed more detailed concepts of the DSH and the DSH/MMSEV/CTV Conops, including functionality and accommodations, mass & volume estimates, technology requirements, and DDT&E costs. DRM 5 represented an effort to reduce cost by scaling back on technologies and eliminating the need for the development of an MMSEV.

Toups, Larry D.↗

Things That Work: Roles and Services of SPDF

The current Heliophysics Science Data Management Policy (HpSDMP) defines the roles of the Space Physics Data Facility (SPDF) project as a heliophysics active Final Archive (aFA), a focus for critical data infrastructure services and a center of excellence for data and ancillary information services. This presentation will highlight (1) select current SPDF activities, (2) the lessons we are continuing to learn in how to usefully serve the the heliophysics science community and (3)SPDF's programmatic emphasis in the coming year. In cooperation with the Heliophysics Virtual discipline Observatories (VxOs), we are working closely with current, and with upcoming missions such as RBSP and MMS, to define effective approaches to ensure the long-term availability and archiving of mission data, as well as how SPDF services can complement active mission capabilities. We are working to make the Virtual Space Physics Observatory (VSPO) service comprehensive in all significant and NASA relevant heliophysics data. We will highlight a new CDAWeb interface, a faster SSCWeb, availability of our data through VxO services such as Autoplot, a new capability to easily access our data from within IDL and continuing improvements to CDF including better handling of leap seconds.

McGuire, R. E.↗

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↗

Managing Challenges in a Multi Contractor Project

The presentation provides a project description, describes the integrated product team, and review project challenges. The challenges include programmatic, technical, basic drop tests, heavy drop tests, C-17 envelope expansion, and Ares I-X.

King, Ron↗

Ares I-X Range Safety Analyses Overview

Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.

Starr, Brett R.↗

Ares I-X Range Safety Flight Envelope Analysis

Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.

Starr, Brett R.↗

Exhaust System Experiments at NASA's AeroAcoustic Propulsion Lab

This presentation gives an overview of the planned testing in the AeroAcoustic Propulsion Lab (AAPL) in the coming 15 months. It was stressed in the presentation that these are plans that are subject to change due to changes in funding and/or programmatic direction. The first chart shows a simplified schedule of test entries with funding sponsor and dates for each. In subsequent charts are pages devoted to the Objectives and Issues with each test entry, along with a graphic intended to represent the test activity. The chart for each test entry also indicates sponsorship of the activity, and a contact person.!

Bridges, James↗

Space Studies Board Annual Report, 2005

The National Academy of Sciences (NAS) was chartered by Congress, under the leadership of President Abraham Lincoln, to provide scientific and technical advice to the government of the United States. Over the years, the advisory program of the institution has expanded, leading to the establishment of the National Academy of Engineering (NAE) and the Institute of Medicine, and of the National Research Council (NRC), the operational arm of the National Academies. The original charter of the Space Science Board was established in June 1958, three months before NASA opened its doors. The Space Science Board and its successor, the Space Studies Board (SSB), have provided expert external and independent scientific and programmatic advice to NASA on a continuous basis from NASA's inception until the present. The Board has also provided such advice to other agencies, including the National Oceanic and Atmospheric Administration, the National Science Foundation, the U.S. Geological Survey, and the Department of Defense, and responds to requests from Congress. Early in 2005, the leadership of NASA changed, and with it new emphases emerged. Some of the early interpretations of the 2004 Vision for Space Exploration, in which only certain aspects of space science were encouraged, disappeared and a broader mandate for science emerged. But what also emerged was fiscal reality, which precluded many of the exciting activities that were planned for NASA's science programs. In this environment of change, there has been a continuing need to evaluate NASA's plans against the strategies for science that have been laid down in the various NRC decadal surveys, and to assist NASA in determining how best to proceed given the reduced level of resources it will have. Coupled with this has been a continuing need to provide Congress with the assessments of NASA's plans that it requests.

National Research Council (NRC)↗

Current Status of the Nitrogen Oxygen Recharge System

This paper presents an overview of the Nitrogen Oxygen Recharge System (NORS) to date and the current development status of the system. NORS is an element of the International Space Station (ISS) Environmental Control and Life Support Systems (ECLSS) used to resupply the ISS with Nitrogen and Oxygen following the impending retirement of the Space Shuttle. The paper will discuss why NASA is developing NORS, including a summary of other concepts considered, and other related concepts currently being developed by NASA. The current system architecture will be described, along with a summary of the current design of the NORS. The overall programmatic schedule of the NORS in the context of the upcoming shuttle retirement and future launch vehicle development will also be presented. Finally, the paper will examine the significant technical challenges encountered during the requirements and preliminary design phase of NORS development. A key challenge to the development of NORS is the international shipment - and associated regulations - of pressurized Oxygen, which is necessary due to the use of launch vehicles based in Japan and French Guiana to send NORS gasses to the ISS. The storage and use of relatively large quantities of high pressure (41,000 kPa) Oxygen and Nitrogen within the ISS, which is unprecedented both on the ISS and other space vehicles, has had a significant impact on the design and architecture of the system. The high pressure of the system also poses unique thermal considerations, which has led to the development of a heater system for thermal conditioning of high pressure gas to avoid thermal impacts on downstream hardware. The on-orbit envelope allocated to the NORS has changed (gotten smaller) and has impacted both the design and architecture of the system. Finally, the balance of safety considerations associated with these high pressure gasses, particularly high pressure Oxygen, with the functionality of the system has profoundly impacted the form of the system and will be discussed.

Dick, Brandon↗

An Overview of NASA's Current Materials Development Efforts for Mars EDL

Current roadmaps point to landing heavy masses (cargo, followed by manned vehicles) on Mars in the 2030's and the existing entry, descent and landing (EDL) technology will not be sufficient to facilitate such missions. In 2009 the Exploration Technology Development Program (ETDP) established the Entry, Descent and Landing Technology Development Project (EDL TDP), to be managed programmatically at Langley Research Center (LaRC) and technically a Ames Research Center (ARC). The purpose of the project is to further the technologies required to land heavy (approximately 40 metric ton) masses on Mars to facilitate exploration. The EDL TDP contains three technical elements. They are: 1) Thermal Protection Systems (TPS) development 2) Modeling and Tools (MAT) development 3) Supersonic Retropropulsion (SRP) development The primary goals of the EDL TDP TPS element is to design and develop TPS materials capable of withstanding the severe aerothermal loads associated with aerocapture and entry into the Martian atmosphere while significantly decreasing the TPS mass fraction contribution to the entry system. Significant advancements in TPS materials technology are needed in order to enable heavy mass payloads to be successfully landed on the Martian surface for robotic precursors and subsequent human exploration missions. The EDL TDP TPS element is further divided into two different TPS concepts for Mars EDL those being: 1) Rigid TPS for a mid L/D aeroshell with the capability to withstand dual pulsed heating environments as high as 500 W/square cm for aerocapture and 130 W/square cm for entry 2) Flexible TPS for a deployable aerodynamic decelerator with the capability to withstand dual pulsed heating environments as high as 120 W/square cm for aerocapture and 30 W/square cm for entry NASA, along with its vendors, has begun developing and testing materials for each of the deceleration approaches. These include multi-layer rigid ablators and flexible ablative materials. In order to model the response of these types of materials, new and improved modeling techniques will be required. This presentation will outline the types of materials that are under development and illustrate the need for advancement in modeling of ablative materials.

Beck, Robin A.↗

Development of NASA's Models and Simulations Standard

From the Space Shuttle Columbia Accident Investigation, there were several NASA-wide actions that were initiated. One of these actions was to develop a standard for development, documentation, and operation of Models and Simulations. Over the course of two-and-a-half years, a team of NASA engineers, representing nine of the ten NASA Centers developed a Models and Simulation Standard to address this action. The standard consists of two parts. The first is the traditional requirements section addressing programmatics, development, documentation, verification, validation, and the reporting of results from both the M&S analysis and the examination of compliance with this standard. The second part is a scale for evaluating the credibility of model and simulation results using levels of merit associated with 8 key factors. This paper provides an historical account of the challenges faced by and the processes used in this committee-based development effort. This account provides insights into how other agencies might approach similar developments. Furthermore, we discuss some specific applications of models and simulations used to assess the impact of this standard on future model and simulation activities.

simulation↗

Pros, Cons, and Alternatives to Weight Based Cost Estimating

Many cost estimating tools use weight as a major parameter in projecting the cost. This is often combined with modifying factors such as complexity, technical maturity of design, environment of operation, etc. to increase the fidelity of the estimate. For a set of conceptual designs, all meeting the same requirements, increased weight can be a major driver in increased cost. However, once a design is fixed, increased weight generally decreases cost, while decreased weight generally increases cost - and the relationship is not linear. Alternative approaches to estimating cost without using weight (except perhaps for materials costs) have been attempted to try to produce a tool usable throughout the design process - from concept studies through development. This paper will address the pros and cons of using weight based models for cost estimating, using liquid rocket engines as the example. It will then examine approaches that minimize the imp~ct of weight based cost estimating. The Rocket Engine- Cost Model (RECM) is an attribute based model developed internally by Pratt & Whitney Rocketdyne for NASA. RECM will be presented primarily to show a successful method to use design and programmatic parameters instead of weight to estimate both design and development costs and production costs. An operations model developed by KSC, the Launch and Landing Effects Ground Operations model (LLEGO), will also be discussed.

Joyner, Claude R.↗

Assessment of NPP VIIRS Ocean Color Data Products: Hope and Risk

For several years, the NASA/Goddard Space Flight Center (GSFC) NPP VIIRS Ocean Science Team (VOST) provided substantial scientific input to the NPP project regarding the use of Visible Infrared Imaging Radiometer Suite (VIIRS) to create science quality ocean color data products. This work has culminated into an assessment of the NPP project and the VIIRS instrument's capability to produce science quality Ocean Color data products. The VOST concluded that many characteristics were similar to earlier instruments, including SeaWiFS or MODIS Aqua. Though instrument performance and calibration risks do exist, it was concluded that programmatic and algorithm issues dominate concerns. Keywords: NPP, VIIRS, Ocean Color, satellite remote sensing, climate data record.

Turpie, Kevin R.↗

ISS Solar Array Alpha Rotary Joint (SARJ) Bearing Failure and Recovery: Technical and Project Management Lessons Learned

The photovoltaic solar panels on the International Space Station (ISS) track the Sun through continuous rotating motion enabled by large bearings on the main truss called solar array alpha rotary joints (SARJs). In late 2007, shortly after installation, the starboard SARJ had become hard to turn and had to be shut down after exceeding drive current safety limits. The port SARJ, of the same design, had been working well for over 2 years. An exhaustive failure investigation ensued that included multiple extravehicular activities to collect information and samples for engineering forensics, detailed structural and thermal analyses, and a careful review of the build records. The ultimate root cause was determined to be kinematic design vulnerability coupled with inadequate lubrication, and manufacturing flaws; this was corroborated through ground tests, metallurgical studies, and modeling. A highly successful recovery plan was developed and implemented that included replacing worn and damaged components in orbit and applying space-compatible grease to improve lubrication. Beyond the technical aspects, however, lie several key programmatic lessons learned. These lessons, such as running ground tests to intentional failure to experimentally verify failure modes, are reviewed and discussed so they can be applied to future projects to avoid such problems.

DellaCorte, Christopher↗