Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Center Planning & Development”

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 217 records · Page 12

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol (Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

Kanefsky, Bob↗

Filtration of Spaceflight Propulsion and Pressurant Systems

NASA has provided little guidance for determining and implementing appropriate filtration of spaceflight propulsion and pressurant systems. Additionally, industry standards typically used for building and verifying filter performance are antiquated and lack applicability to propulsion systems. The NASA Engineering and Safety Center (NESC) was requested to perform a gap analysis, identify risks, and develop a mitigation plan for spaceflight propulsion filtration. This report contains the outcome of the NESC analysis.

Propulsion System↗

GLOBAL REFERENCE ATMOSPHERIC MODELS FOR AEROASSIST APPLICATIONS

Aeroassist is a broad category of advanced transportation technology encompassing aerocapture, aerobraking, aeroentry, precision landing, hazard detection and avoidance, and aerogravity assist. The eight destinations in the Solar System with sufficient atmosphere to enable aeroassist technology are Venus, Earth, Mars, Jupiter, Saturn, Uranus, Neptune, and Saturn's moon Titan. Engineering-level atmospheric models for five of these targets - Earth, Mars, Titan, Neptune, and Venus - have been developed at NASA's Marshall Space Flight Center. These models are useful as tools in mission planning and systems analysis studies associated with aeroassist applications. The series of models is collectively named the Global Reference Atmospheric Model or GRAM series. An important capability of all the models in the GRAM series is their ability to simulate quasi-random perturbations for Monte Carlo analysis in developing guidance, navigation and control algorithms, for aerothermal design, and for other applications sensitive to atmospheric variability. Recent example applications are discussed.

Duvall, Aleta↗

Energy Management of Manned Boost-Glide Vehicles: A Historical Perspective

As flight progressed from propellers to jets to rockets, the propulsive energy grew exponentially. With the development of rocket-only boosted vehicles, energy management of these boost-gliders became a distinct requirement for the unpowered return to base, alternate landing site, or water-parachute landing, starting with the X-series rocket aircraft and terminating with the present-day Shuttle. The problem presented here consists of: speed (kinetic energy) - altitude (potential energy) - steep glide angles created by low lift-to-drag ratios (L/D) - distance to landing site - and the bothersome effects of the atmospheric characteristics varying with altitude. The primary discussion regards post-boost, stabilized glides; however, the effects of centrifugal and geopotential acceleration are discussed as well. The aircraft and spacecraft discussed here are the X-1, X-2, X-15, and the Shuttle; and to a lesser, comparative extent, Mercury, Gemini, Apollo, and lifting bodies. The footprints, landfalls, and methods developed for energy management are also described. The essential tools required for energy management - simulator planning, instrumentation, radar, telemetry, extended land or water range, Mission Control Center (with specialist controllers), and emergency alternate landing sites - were first established through development of early concepts and were then validated by research flight tests.

Day, Richard E.↗

Institutionalizing Lessons Learned

The NASA Integrated Action Team (NIAT) was formed by the NASA Administrator in March 2000. The purpose of this team was to identify the actions that NASA must take to address systemic findings reported in 4 different anomaly investigations. Team membership represented senior managers from all the field centers and NASA Headquarters. NIAT report addressed 165 findings and developed 17 action plans that are described in five themes: people and teams, technology, risk, formulation rigor, and communications. The NIAT actions present a systems solution for strengthening formulation and implementation of programs and improving the environment for their support. NIAT results included: enhancing success by avoiding failures that could have been prevented through good planning and sound practice; ensuring that prudent risks do not compromise safety; and ensuring that mission risks are objectively assessed, appropriately mitigated and consciously accepted by the program team and customers. Definitions of Faster, Better, Cheaper and Success Criteria were also developed and included as part of the NIAT report. As a result of the NIAT report, program and project management process changes were incorporated into NASA's quality system documentation, including NPG 7120.513, "NASA Program and Project Management Processes and Requirements. This paper describes the NIAT results and the resulting updates to NPG 7120.5 that keep this program and project management description a living process.

McBrayer, Robert O.↗

Artificial Gravity as a Multi-System Countermeasure to Bed Rest Deconditioning: Pilot Study Overview

Efficient, effective, multi-system countermeasures will likely be required to protect the health, safety, and performance of crews aboard planned exploration-class space flight missions to Mars and beyond. To that end, NASA, DLR, and IMBP initiated a multi-center international project to begin systematically exploring the utility of artificial gravity (AG) as a multi-system countermeasure in ground based venues using test subjects deconditioned by bed rest. The goal of this project is to explore the efficacy of short-radius, intermittent AG as a countermeasure to bone, muscle, cardiovascular, and sensory-motor adaptations to hypogravity. This session reports the results from a pilot study commissioned to validate a standardized protocol to be used by all centers involved in the project. Subject selection criteria, medical monitoring requirements, medical care procedures, experiment control procedures, and standardized dependent measures were established jointly. Testing was performed on 15 rigorously screened male volunteers subjected to 21 days of 6deg HDT bed rest. (All provided written consent to volunteer after the nature of the study and its hazards were clearly explained to them.) Eight were treated with daily 1hr AG exposures (2.5g at the feet decreasing to 1.0g at the heart) aboard a short radius (3m) centrifuge, while the other seven served as controls. Multiple tests of multiple dependent measures were made in each of the primary physiological systems of interest during a 10 day acclimatization period prior to HDT bed rest and again during an 8 day recovery period after the bed rest period was complete. Analyses of these data (presented in other papers in this session) suggest the AG prescription had salutary effects on aspects of the bone, muscle, and cardiovascular systems, with no untoward effects on the vestibular system, the immune system, or cognitive function. Furthermore, treatment subjects were able to tolerate 153/160 centrifuge sessions over the 21 day deconditioning protocol, suggesting that tolerance was unaffected by deconditioning. These positive results set the stage for full implementation of the planned multi-center international AG project. Future work will be devoted to developing optimization techniques for AG prescriptions (likely supplemented by exercise) to provide maximum physiological protection across all systems subject to space flight deconditioning in both men and women with minimum time and/or side effects. While a continuous AG solution (rotating vehicle) would likely be more efficient, this study suggests that intermittent AG could be an effective multi-system countermeasure.

Paloski, William H.↗

ELV Payload Safety Program Workshop Green Propulsion Update

MSFC is engaged on the system solution: thrusters and power units; GRC is working plume diagnostics/modeling and independent thruster testing on GPIM.; GSFC is working slosh characteristics on GPIM tank.; JPL and ARC continually interested to infuse green propellant as potential replacement to hydrazine.; Mike Gazarik, AA of STMD, has requested MSFC lead the development of an Agency-level green propellant roadmap involving multiple Centers., Tentatively planned for August 2015 in Huntsville.

Robinson, Joel↗

Affordable Development and Demonstration of a Small Nuclear Thermal Rocket (NTR) Engine and Stage: How Small Is Big Enough?

The Nuclear Thermal Rocket (NTR) derives its energy from fission of uranium-235 atoms contained within fuel elements that comprise the engine's reactor core. It generates high thrust and has a specific impulse potential of approximately 900 specific impulse - a 100 percent increase over today's best chemical rockets. The Nuclear Thermal Propulsion (NTP) project, funded by NASA's Advanced Exploration Systems (AES) program, includes five key task activities: (1) Recapture, demonstration, and validation of heritage graphite composite (GC) fuel (selected as the Lead Fuel option); (2) Engine Conceptual Design; (3) Operating Requirements Definition; (4) Identification of Affordable Options for Ground Testing; and (5) Formulation of an Affordable Development Strategy. During fiscal year (FY) 2014, a preliminary Design Development Test and Evaluation (DDT&E) plan and schedule for NTP development was outlined by the NASA Glenn Research Center (GRC), Department of Energy (DOE) and industry that involved significant system-level demonstration projects that included Ground Technology Demonstration (GTD) tests at the Nevada National Security Site (NNSS), followed by a Flight Technology Demonstration (FTD) mission. To reduce cost for the GTD tests and FTD mission, small NTR engines, in either the 7.5 or 16.5 kilopound-force thrust class, were considered. Both engine options used GC fuel and a common fuel element (FE) design. The small approximately 7.5 kilopound-force criticality-limited engine produces approximately157 thermal megawatts and its core is configured with parallel rows of hexagonal-shaped FEs and tie tubes (TTs) with a FE to TT ratio of approximately 1:1. The larger approximately 16.5 kilopound-force Small Nuclear Rocket Engine (SNRE), developed by Los Alamos National Laboratory (LANL) at the end of the Rover program, produces approximately 367 thermal megawatts and has a FE to TT ratio of approximately 2:1. Although both engines use a common 35-inch (approximately 89-centimeters) -long FE, the SNRE's larger diameter core contains approximately 300 more FEs needed to produce an additional 210 thermal megawatts of power. To reduce the cost of the FTD mission, a simple one-burn lunar flyby mission was considered to reduce the liquid hydrogen (LH2) propellant loading, the stage size and complexity. Use of existing and flight proven liquid rocket and stage hardware (e.g., from the RL10B-2 engine and Delta Cryogenic Second Stage) was also maximized to further aid affordability. This paper examines the pros and cons of using these two small engine options, including their potential to support future human exploration missions to the Moon, near Earth asteroids (NEA), and Mars, and recommends a preferred size. It also provides a preliminary assessment of the key activities, development options, and schedule required to affordably build, ground test and fly a small NTR engine and stage within a 10-year timeframe.

Spacecraft design↗

NASA Agile Community of Practice

This 2023-2024 report provides a comprehensive summary of the products and activities executed by the NASA Agile Community of Practice over its first year from being formally stood up. The report highlights the community's ongoing efforts to advance Agile values and principles, improve practices, and foster innovation within teams across NASA centers. The report delves into key initiatives, including the development of a strategic plan, executive summary, and best practice guidelines; as well as the facilitation of knowledge-sharing events such as webinars with internal and external speakers, workshops, and technical interchange meeting.

Agile↗

Carbon Storage Monitoring, Verification, and Accounting (MVA)

Fact sheet about carbon storage monitoring, verification, and accounting (MVA). Includes background on MVA, the Energy & Environmental Research Center, and Plains CO 2 Reduction (PCOR) Partnership Initiative plans for MVA strategy development.

01 COAL, LIGNITE, AND PEAT↗

Advanced communications technology satellite high burst rate link evaluation terminal power control and rain fade software test plan, version 1.0

The Power Control and Rain Fade Software was developed at the NASA Lewis Research Center to support the Advanced Communications Technology Satellite High Burst Rate Link Evaluation Terminal (ACTS HBR-LET). The HBR-LET is an experimenters terminal to communicate with the ACTS for various experiments by government, university, and industry agencies. The Power Control and Rain Fade Software is one segment of the Control and Performance Monitor (C&PM) Software system of the HBR-LET. The Power Control and Rain Fade Software automatically controls the LET uplink power to compensate for signal fades. Besides power augmentation, the C&PM Software system is also responsible for instrument control during HBR-LET experiments, control of the Intermediate Frequency Switch Matrix on board the ACTS to yield a desired path through the spacecraft payload, and data display. The Power Control and Rain Fade Software User's Guide, Version 1.0 outlines the commands and procedures to install and operate the Power Control and Rain Fade Software. The Power Control and Rain Fade Software Maintenance Manual, Version 1.0 is a programmer's guide to the Power Control and Rain Fade Software. This manual details the current implementation of the software from a technical perspective. Included is an overview of the Power Control and Rain Fade Software, computer algorithms, format representations, and computer hardware configuration. The Power Control and Rain Fade Test Plan provides a step-by-step procedure to verify the operation of the software using a predetermined signal fade event. The Test Plan also provides a means to demonstrate the capability of the software.

Reinhart, Richard C.↗

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗

Implementation Plan for the NASA Center of Excellence for Structures and Materials

This report presents the implementation plans of the Center of Excellence (COE) for Structures and Materials. The plan documented herein is the result of an Agencywide planning activity led by the Office of the Center of Excellence for Structures and Materials at Langley Research Center (LaRC). The COE Leadership Team, with a representative from each NASA Field Center, was established to assist LaRC in fulfilling the responsibilities of the COE. The Leadership Team developed the plan presented in this report.

Harris, Charles E.↗

Multi Sector Planning Tools for Trajectory-Based Operations

This paper discusses a suite of multi sector planning tools for trajectory-based operations that were developed and evaluated in the Airspace Operations Laboratory (AOL) at the NASA Ames Research Center. The toolset included tools for traffic load and complexity assessment as well as trajectory planning and coordination. The situation assessment tools included an integrated suite of interactive traffic displays, load tables, load graphs, and dynamic aircraft filters. The planning toolset allowed for single and multi aircraft trajectory planning and data communication-based coordination of trajectories between operators. Also newly introduced was a real-time computation of sector complexity into the toolset that operators could use in lieu of aircraft count to better estimate and manage sector workload, especially in situations with convective weather. The tools were used during a joint NASA/FAA multi sector planner simulation in the AOL in 2009 that had multiple objectives with the assessment of the effectiveness of the tools being one of them. Current air traffic control operators who were experienced as area supervisors and traffic management coordinators used the tools throughout the simulation and provided their usefulness and usability ratings in post simulation questionnaires. This paper presents these subjective assessments as well as the actual usage data that was collected during the simulation. The toolset was rated very useful and usable overall. Many elements received high scores by the operators and were used frequently and successfully. Other functions were not used at all, but various requests for new functions and capabilities were received that could be added to the toolset.

Prevot, Thomas↗

Update on Technology Development Plan for a Low Temperature Hybrid Mars Ascent Vehicle Concept

Technology development to mature a hybrid rocket option for a potential Mars Ascent Vehicle has been underway at the Jet Propulsion Laboratory and Marshall Space Flight Center. A conceptual design was completed in 2016 and has been used to determine the motor size for risk reduction development. The task plan for the FY17 testing, actually completed in mid FY18, is discussed. The major achievement of this effort was successful full scale hotfire testing with a representative ambient Earth storable propellant combination: SP7/MON3. A near term plan, through July 2019 is briefly discussed.

Prince, Andrew↗

Application of the CIRSSE cooperating robot path planner to the NASA Langley truss assembly problem

A method for autonomously planning collision free paths for two cooperating robots in a static environment was developed at the Center for Intelligent Robotic Systems for Space Exploration (CIRSSE). The method utilizes a divide-and-conquer type of heuristic and involves non-exhaustive mapping of configuration space. While there is no guarantee of finding a solution, the planner was successfully applied to a variety of problems including two cooperating 9 degrees of freedom (dof) robots. Although developed primarily for cooperating robots the method is also applicable to single robot path planning problems. A single 6 dof version of the planner was implemented for the truss assembly east, at NASA Langley's Automated Structural Assembly Lab (ASAL). The results indicate that the planner could be very useful in addressing the ASAL path planning problem and that further work along these lines is warranted.

Weaver, Jonathan M.↗