Engineering Papers⌕ Search

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.

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

At least 919 records · Page 51

Maximizing Launch Vehicle and Payload Design Via Early Communications

The United States? current fleet of launch vehicles is largely derived from decades-old designs originally made for payloads that no longer exist. They were built primarily for national security or human exploration missions. Today that fleet can be divided roughly into small-, medium-, and large-payload classes based on mass and volume capability. But no vehicle in the U.S. fleet is designed to accommodate modern payloads. It is usually the payloads that must accommodate the capabilities of the launch vehicles. This is perhaps most true of science payloads. It was this paradigm that the organizers of two weekend workshops in 2008 at NASA's Ames Research Center sought to alter. The workshops brought together designers of NASA's Ares V cargo launch vehicle (CLV) with scientists and payload designers in the astronomy and planetary sciences communities. Ares V was still in a pre-concept development phase as part of NASA?s Constellation Program for exploration beyond low Earth orbit (LEO). The space science community was early in a Decadal Survey that would determine future priorities for research areas, observations, and notional missions to make those observations. The primary purpose of the meetings in April and August of 2008, including the novel format, was to bring vehicle designers together with space scientists to discuss the feasibility of using a heavy lift capability to launch large observatories and explore the Solar System. A key question put to the science community was whether this heavy lift capability enabled or enhanced breakthrough science. The meetings also raised the question of whether some trade-off between mass/volume and technical complexity existed that could reduce technical and programmatic risk. By engaging the scientific community early in the vehicle design process, vehicle engineers sought to better understand potential limitations and requirements that could be added to the Ares V from the mission planning community. From the vehicle standpoint, while the human exploration mission could not be compromised to accommodate other payloads, the design might otherwise be tailored to not exclude other payload requirements. This paper summarizes the findings of the workshops and discusses the benefits of bringing together the vehicle design and science communities early in their concept phases

Morris, Bruce↗

The Right Stuff: A Look Back at Three Decades of Flight Controller Training for Space Shuttle Mission Operations

This paper will summarize the thirty-year history of Space Shuttle operations from the perspective of training in NASA Johnson Space Center's Mission Control Center. It will focus on training and development of flight controllers and instructors, and how training practices have evolved over the years as flight experience was gained, new technologies developed, and programmatic needs changed. Operations of human spaceflight systems is extremely complex, therefore the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center, in Houston, Texas manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. This paper will give an overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified. The training methodology for developing flight controllers has evolved significantly over the last thirty years, while the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. These changes have been driven by many factors including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers will share their experiences in training and operating the Space Shuttle throughout the Program s history. A primary method used for training Space Shuttle flight control teams is by running mission simulations of the orbit, ascent, and entry phases, to truly "train like you fly." The audience will learn what it is like to perform a simulation as a shuttle flight controller. Finally, we will reflect on the lessons learned in training for the shuttle program, and how those could be applied to future human spaceflight endeavors.

Dittemore, Gary D.↗

Risk Management for the International Space Station

The International Space Station (ISS) is an extremely complex system, both technically and programmatically. The Space Station must support a wide range of payloads and missions. It must be launched in numerous launch packages and be safely assembled and operated in the harsh environment of space. It is being designed and manufactured by many organizations, including the prime contractor, Boeing, the NASA institutions, and international partners and their contractors. Finally, the ISS has multiple customers, (e.g., the Administration, Congress, users, public, international partners, etc.) with contrasting needs and constraints. It is the ISS Risk Management Office strategy to proactively and systematically manages risks to help ensure ISS Program success. ISS program follows integrated risk management process (both quantitative and qualitative) and is integrated into ISS project management. The process and tools are simple and seamless and permeate to the lowest levels (at a level where effective management can be realized) and follows the continuous risk management methodology. The risk process assesses continually what could go wrong (risks), determine which risks need to be managed, implement strategies to deal with those risks, and measure effectiveness of the implemented strategies. The process integrates all facets of risk including cost, schedule and technical aspects. Support analysis risk tools like PRA are used to support programatic decisions and assist in analyzing risks.

Sebastian, J.↗

Propulsion Technology Lifecycle Operational Analysis

The paper presents the results of a focused effort performed by the members of the Space Propulsion Synergy Team (SPST) Functional Requirements Sub-team to develop propulsion data to support Advanced Technology Lifecycle Analysis System (ATLAS). This is a spreadsheet application to analyze the impact of technology decisions at a system-of-systems level. Results are summarized in an Excel workbook we call the Technology Tool Box (TTB). The TTB provides data for technology performance, operations, and programmatic parameters in the form of a library of technical information to support analysis tools and/or models. The lifecycle of technologies can be analyzed from this data and particularly useful for system operations involving long running missions. The propulsion technologies in this paper are listed against Chemical Rocket Engines in a Work Breakdown Structure (WBS) format. The overall effort involved establishing four elements: (1) A general purpose Functional System Breakdown Structure (FSBS). (2) Operational Requirements for Rocket Engines. (3) Technology Metric Values associated with Operating Systems (4) Work Breakdown Structure (WBS) of Chemical Rocket Engines The list of Chemical Rocket Engines identified in the WBS is by no means complete. It is planned to update the TTB with a more complete list of available Chemical Rocket Engines for United States (US) engines and add the Foreign rocket engines to the WBS which are available to NASA and the Aerospace Industry. The Operational Technology Metric Values were derived by the SPST Sub-team in the form of the TTB and establishes a database for users to help evaluate and establish the technology level of each Chemical Rocket Engine in the database. The Technology Metric Values will serve as a guide to help determine which rocket engine to invest technology money in for future development.

Robinson, John W.↗

Technology Development for Fire Safety in Exploration Spacecraft and Habitats

Fire during an exploration mission far from Earth is a particularly critical risk for exploration vehicles and habitats. The Fire Prevention, Detection, and Suppression (FPDS) project is part of the Exploration Technology Development Program (ETDP) and has the goal to enhance crew health and safety on exploration missions by reducing the likelihood of a fire, or, if one does occur, minimizing the risk to the mission, crew, or system. Within the past year, the FPDS project has been formalized within the ETDP structure and has seen significant progress on its tasks in fire prevention, detection, and suppression. As requirements for Constellation vehicles and, specifically, the CEV have developed, the need for the FPDS technologies has become more apparent and we continue to make strides to infuse them into the Constellation architecture. This paper describes the current structure of the project within the ETDP and summarizes the significant programmatic activities. Major technical accomplishments are identified as are activities planned for FY07.

Ruff, Gary A.↗

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↗