Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “team”

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,675 records · Page 93

A Matrix Approach to Software Process Definition

The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

Schultz, David↗

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

Task Analysis Technologies at KSC

Project objective: (1) Form an integrated team of NASA. USA, Boeing, and Dynacs researches. (2) Create a user friendly software prototype that assists an analyst in performing a human factors process failure modes and effects analysis (HF-PFMEA). (3)Perform four task analyses on center: cargo late access task analysis (NASA/Boeing team); payload test and verification system task analysis (NASA/Boeing team); slammer cover installation operations task analysis (NASA/USA team); ATDC LOX pump acceptance test procedure task analysis (NASA/Dynacs team).

Carstens, Deborah S.↗

Unlocking the Mystery of Columbia's Tragic Accident Through Materials Characterization

The wing and underbelly reconstruction of Space Shuttle Columbia took place at the Shuttle Landing Facility Hangar after the accident which destroyed STS-107. Fragments were placed on a grid according to their original location on the orbiter. Some Reinforced Carbon-Carbon (RCC) panels of the left wing leading edge and other parts from both leading edges were recovered and incorporated into the reconstruction. The recovered parts were tracked on a database according to a number and also tracked on a map of the orbiter. This viewgraph presentation describes the process of failure analysis undertaken by the Materials and Processes (M&P) Problem Resolution Team. The team started with factual observations about the accident, and identified highest level questions for it to answer in order to understand where on the orbiter failure occured, what component(s) failed, and what was the sequence of events. The finding of Columbia's MADS/OEX data recorder shifted the focus of the team's analysis to the left wing leading edge damage. The team placed particular attention on slag deposits on some of the RCC panels. The presentation lists analysis techniques, and lower level questions for the team to answer.

Shah, Sandeep↗

Conceptual Design of In-Space Vehicles for Human Exploration of the Outer Planets

During FY-2002, a team of engineers from TD30/Advanced Concepts and TD40/Propulsion Research Center embarked on a study of potential crewed missions to the outer solar system. The study was conducted under the auspices of the Revolutionary Aerospace Systems Concepts activity administered by Langley Research Center (LaRC). The Marshall Space Flight Center (MSFC) team interacted heavily with teams from other Centers including Glenn Research Center, LaRC, Jet Propulsion Laboratory, and Johnson Space Center. The MSFC team generated five concept missions for this project. The concept missions use a variety of technologies, including magnetized target fusion (MTF), magnetoplasmadynamic thrusters, solid core reactors, and molten salt reactors in various combinations. The Technical Publication (TP) reviews these five concepts and the methods used to generate them. The analytical methods used are described for all significant disciplines and subsystems. The propulsion and power technologies selected for each vehicle are reviewed in detail. The MSFC team also expended considerable effort refining the MTF concept for use with this mission. The results from this effort are also contained within this TP. Finally, the lessons learned from this activity are summarized in the conclusions section.

Adams, R. B.↗

Foam on Tile Impact Modeling for the Space Shuttle Program

Following the breakup of the Space Shuttle Columbia during reentry a NASA-wide investigation team was formed to examine the probable damage inflicted on Orbiter Thermal Protection System (TPS) elements by impact of External Tank insulating foam projectiles. Our team was to apply rigorous, physics-based analysis techniques to help determine parameters of interest for an experimental test program, utilize validated codes to investigate the full range of impact scenarios, and use analysis derived models to predict aero-thermal-structural responses to entry conditions. We were to operate on a non-interference basis with the j Team, and were to supply significant findings to that team and to the Orbiter Vehicle Engineering Working Group, being responsive to any solicitations for support from these entities. The authors formed a working sub-group within the larger team to apply the Smooth Particle Hydrodynamics code SPHC to the damage estimation problem. Numerical models of the LI-900 TPS tiles and of the BX-250 foam were constructed and used as inputs into the code. Material properties needed to properly model the tiles and foam were obtained from other working sub-groups who performed tests on these items for this purpose. Two- and three- dimensional models of the tiles were constructed, including the glass outer layer, the densified lower layer of LI-900 insulation, the Nomex felt Strain Isolation Pad (SIP) mounting layer, and the underlying aluminum 2024 vehicle skin. A model for the BX-250 foam including porous compression, elastic rebound, and surface erosion was developed. Code results for the tile damage and foam behavior were extensively validated through comparison with the Southwest Research Institute (SwRI) foam-on-tile impact experiments carried out in 1999. These tests involved small projectiles striking individual tiles and small tile arrays. Following code and model validation we simulated impacts of larger ET foam projectiles on the TPS tile systems used on the wings of the orbiter. Tiles used on the Wing Acreage, the Main Landing Gear Door, and the Carrier Panels near the front edge of the wing were modeled. Foam impacts shot for the CAB investigation were modeled, as well as impacts at larger angles, including rapid rotation of the projectile, and with varying foam properties. General results suggest that foam impacts on tiles at about 500 mph could cause appreciable damage if the impact angle is greater than about 20 degrees. Some variations of the foam properties, such as increased brittleness or increased density could increase damage in some cases. Rapid (17 rps) rotation failed to increase the damage for the two cases considered. This does not rule out other cases in which the rotational energy might lead to an increase in tile damage, but suggests that in most cases rotation will not be an important factor. Similar models will be applied for other impacting materials, other velocities, and other geometries as part of the Return to Flight process.

Stellingwerf, R. F.↗

The Use of LS-DYNA in the Columbia Accident Investigation and Return to Flight Activities

During the launch of the Space Shuttle Columbia on January 16, 2003, foam originating from the external tank impacted the shuttle's left wing 81 seconds after lift-off. Then on February 1st, Space Shuttle Columbia broke-up during re-entry. In the weeks that followed, the Columbia Accident Investigation Board had formed various teams to investigate every aspect of the tragedy. One of these teams was the Impact Analysis Team, which was asked to investigate the foam impact on the wing leading edge. This paper will describe the approach and methodology used by the team to support the accident investigation, and more specifically the use of LS-DYNA for analyzing the foam impact event. Due to the success of the analytical predictions, the impact analysis team has also been asked to support Return to Flight activities. These activities will analyze a far broader range of impact events, but not with just foam and not only on the wing leading edge. The debris list has expanded and so have the possible impact locations. This paper will discuss the Return to Flight activities and the use of LS-DYNA to support them.

Gabrys, Jonathan↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite's White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with and turnaround maintenance performed. The fight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development. NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This recent partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of the X-37 effort, the team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff research and development and provides valuable experience to implement the exploration vision.

Turner, Susan↗

Drinking Water Database

This summer I had the opportunity to work in the Environmental Management Office (EMO) under the Chemical Sampling and Analysis Team or CS&AT. This team s mission is to support Glenn Research Center (GRC) and EM0 by providing chemical sampling and analysis services and expert consulting. Services include sampling and chemical analysis of water, soil, fbels, oils, paint, insulation materials, etc. One of this team s major projects is the Drinking Water Project. This is a project that is done on Glenn s water coolers and ten percent of its sink every two years. For the past two summers an intern had been putting together a database for this team to record the test they had perform. She had successfully created a database but hadn't worked out all the quirks. So this summer William Wilder (an intern from Cleveland State University) and I worked together to perfect her database. We began be finding out exactly what every member of the team thought about the database and what they would change if any. After collecting this data we both had to take some courses in Microsoft Access in order to fix the problems. Next we began looking at what exactly how the database worked from the outside inward. Then we began trying to change the database but we quickly found out that this would be virtually impossible.

Murray, ShaTerea R.↗

Youth Technology Academy

One of the most important aspects of the YTA Program is that students, working with Tri-C instructors, NASA engineers, and technicians, begin to build relationships with professionals with whom they might not normally have contact. These professionals serve as role models for students and help them to apply math, science and problem-solving skills in real time to construct a competition-ready robot, allowing them to experience the satisfaction and challenges of an engineering or technical career by working diligently to solve problems that may never have been thought possible to solve. Transcending school boundaries, YTA is available to all students who are interested and qualified but who may otherwise never get an opportunity to participate because their school does not offer a robotics program. YTA fills an educational void by offering an exciting engineering and technology experience to a greater number of students than have been able to participate in the past. Our students have been working hard and see the long-term rewards for their efforts. The YTA Team 1270 was a finalist at the 2005 FIRST Robotics Florida Regional and took home second- place honors. Mark Poljak, nominated by the students of YTA Team 1270, received the Woodie Flowers Award at the FIRST 2005 Buckeye Regional competition. This award celebrates effective communication in the art and science of engineering and design. The YTA Team was also invited, as one of fifty-four teams, to participate in this year s FIRST VEX Robotics tournament representing Cuyahoga Community College and NASA GRC (Team 26), held at the FIRST Robotics National Competition in Atlanta, GA. Because of our efforts, community colleges from around the country have taken notice and have asked us to become part of the executive board of the RoboEducators, whose mission is to bring technology training to high school students in preparation for the future workforce.

Source record↗

Learning Lessons from the X-37 Project

The X-37 was planned as an automated vehicle capable of flight-testing new aerospace technologies in combined environments that are beyond the capability of existing ground or flight platforms. Flight demonstration with the X-37 architecture and configuration in relevant environments was planned to reduce the risk of developing launch vehicle technologies for sustainable, affordable exploration and other aerospace applications. Current plans are for the X-37 Approach and Landing Test Vehicle (ALTV) to be atmospheric tested in 2005 from Scaled Composite s White Knight carrier aircraft at up to 40,000 feet over California's Mojave Spaceport, with landing and turnaround maintenance performed. The Flight Operations Control Center will conduct the mission, using a streamlined operations concept. Taxi-tow and captive-carry tests will be conducted prior to the atmospheric-test series. Sponsored by the Defense Advanced Research Projects Agency (DARPA) with NASA participation, technical objectives are to: (1) mature Computed Air Data System/Remote Pressure Sensor technology, (2) manage energy during Terminal Area Energy Management/Heading Alignment Cone maneuvers, and (3) validate the aerodatabase. The X-37 Project began in 1999 under a cooperative agreement as an element of NASA's Future X Program and transitioned to a NASA Research Announcement under the Space Launch Initiative. In mid-2004, NASA transferred ownership to DARPA, with its heritage of performing high-risk, high-payoff research and development (R&D). NASA contributes technical expertise, including risk analysis and system integration. The Boeing Company is the prime contractor, with nationwide suppliers. This partnership exemplifies the synergy attainable when NASA Centers, other Government agencies, and industry work together toward a common goal - contributing to the knowledge base for U.S. exploration and other aerospace endeavors. The X-37 team represents a range of space transportation disciplines - from engineering to management. Some members have been with the project since its inception. All have gained priceless experience during the design, manufacturing, and testing of the ALTV, as well as through developing advanced orbital flight technologies, such as state-of-the-art Thermal Protection Systems and hot structures. Throughout this process, the X-37 Project team captures lessons that are directly applicable to other such efforts. The upcoming ALTV flights offer another dimension of data and first-hand experience that will prove invaluable to those designing new generations of reusable spacecraft. And ongoing technology developments will expand the aerospace knowledge base. Delivering prototype hardware is always a risky proposition. During the course of this effort, the X-37 team has experienced many challenging opportunities, delivering significant accomplishments and learning numerous lessons in the process. The ability to manage the risk landscape is key to overcoming obstacles, especially technical hurdles that are encountered in progressing hardware from design to flight. The approach to managing risk under this partnership is evolving but, in general, the team allocates resources to reduce the likelihood of severe-consequence risks, thus maximizing mission success and ensuring that the X-37 Project delivers value to its stakeholders. As the team sharpens its focus on operations, it continues to contribute knowledge to those who would undertake high-risk, high-payoff R&D and provides valuable experience to implement the Vision for Space Exploration.

Turner, Susan↗

Telemetry Monitoring and Display Using LabVIEW

The Measurement Technology Center of the Instrumentation Section configures automated data acquisition systems to meet the diverse needs of JPL's experimental research community. These systems are based on personal computers or workstations (Apple, IBM/Compatible, Hewlett-Packard, and Sun Microsystems) and often include integrated data analysis, visualization and experiment control functions in addition to data acquisition capabilities. These integrated systems may include sensors, signal conditioning, data acquisition interface cards, software, and a user interface. Graphical programming is used to simplify configuration of such systems. Employment of a graphical programming language is the most important factor in enabling the implementation of data acquisition, analysis, display and visualization systems at low cost. Other important factors are the use of commercial software packages and off-the-shelf data acquisition hardware where possible. Understanding the experimenter's needs is also critical. An interactive approach to user interface construction and training of operators is also important. One application was created as a result of a competative effort between a graphical programming language team and a text-based C language programming team to verify the advantages of using a graphical programming language approach. With approximately eight weeks of funding over a period of three months, the text-based programming team accomplished about 10% of the basic requirements, while the Macintosh/LabVIEW team accomplished about 150%, having gone beyond the original requirements to simulate a telemetry stream and provide utility programs. This application verified that using graphical programming can significantly reduce software development time. As a result of this initial effort, additional follow-on work was awarded to the graphical programming team.

graphical user interface LabVIEW graphical program↗

From Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn GDS Team met the SC Sim integration challenge in eight months. The GDS System Engineering approach in response to the SC Simintegration challenge, focused on a set of key practices: decomposition of project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; risk management thru management of expectations; and aggregation of intermediate products into a final product. By maintaining a a system-level focus, the overall systems engineering process unified team GDS Team members with a common goal: the success of the ground system as a whole and not just the success of their individual expert contributions. Incorporation of Agile-type development efforts were aligned with a risk strategy based on team-oriented principles and expectations management, thus achieving a more stable baseline solution without compromising the integrity of the GDS design.

Dawn Mission↗

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, the pace of this process was never intended to be continued indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5-day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

mission operations↗

An Overview of the Space Shuttle Orbiter's Aging Aircraft Program

The Space Shuttle Orbiter has well exceeded its original design life of 10 years or 100 missions. The Orbiter Project Office (OPO) has sponsored several activities to address aging vehicle concerns, including a Corrosion Control Review Board (CCRB), a mid-life certification program, and most recently the formation of the Aging Orbiter Working Group (AOWG). The AOWG was chartered in 2004 as a proactive group which provides the OPO oversight for aging issues such as corrosion, non-destructive inspection, non-metallics, wiring and subsystems. The core team consists of mainly representatives from the Materials and Processes Problem Resolution Team (M&P PRT) and Safety and Mission Assurance (S&MA). Subsystem engineers and subject matter experts are called in as required. The AOWG has functioned by forming issues based sub-teams. Examples of completed sub-teams include adhesives, wiring and wing leading edge metallic materials. Current sub-teams include Composite Over-Wrapped Pressure Vessels (COPV), elastomeric materials and mechanisms.

Russell, Richard W.↗

From ESAS to Ares: A Chronology

Throughout my career, I have observed many launch vehicle efforts come and go. Although it may appear on the surface that those were dead-end streets, the knowledge we gained through them actually informs the work in progress. Following the tragic loss of the Space Shuttle Columbia's crew, the administration took the Columbia Accident Investigation Board's findings to heart and united the Agency behind the Vision for Space Exploration, with clear goals and objectives, including fielding a new generation of safe, reliable, and affordable space transportation. The genesis of the Ares I Crew Launch Vehicle and Ares V Cargo Launch Vehicle activities now under way by a nationwide Government and industry team was the confirmation of the current NASA Administrator in April 2005. Shortly thereafter, he commissioned a team of aerospace experts to conduct the Exploration Systems Architecture Study (ESAS), which gave shape to launch vehicles that will empower America's resurgence in scientific discovery through human and robotic space exploration. In October 2005, I was asked to lead this effort, building the team and forming the partnerships that will, in turn, build America's next human-rated space transportation system. In November 2006, the Ares I team began conducting the System Requirements Review milestone, just 1 year after its formation. We are gaining momentum toward the first test flight of the integrated vehicle system in 2009, just a few short years away. The Agency is now poised to deliver on the commitment this nation has made to advance our interests in space. In its inaugural year, the Ares team has conducted the first human-rated launch vehicle major milestone in over 30 years. Using the Exploration Systems Architecture Study recommendations as a starting point, the vehicle designs have been evolved to best meet customer and stakeholder requirements to fulfill the strategic goals outlined in the Vision for Space Exploration.

Cook, Stephen A.↗

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, there was never an intention of maintaining the pace of this process indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5- day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

Mars exploration↗

Exploration Blueprint: Data Book

The material contained in this report was compiled to capture the work performed by the National Aeronautics and Space Administration's (NASA's) Exploration study team in the late 2002 timeframe. The "Exploration Blueprint Data Book" documents the analyses and findings of the 90-day Agency-wide study conducted from September - November 2002. During the summer of 2002, the NASA Deputy Administrator requested that a study be performed with the following objectives: - Develop the rationale for exploration beyond low-Earth orbit - Develop roadmaps for how to accomplish the first steps through humans to Mars - Develop design reference missions as a basis for the roadmaps - Make recommendations on what can be done now to effect this future This planning team, termed the Exploration Blueprint, performed architecture analyses to develop roadmaps for how to accomplish the first steps beyond LEO through the human exploration of Mars. The previous NASA Exploration Team activities laid the foundation and framework for development of NASA's Integrated Space Plan. The reference missions resulting from the analysis performed by the Exploration Blueprint team formed the basis for requirement definition, systems development, technology roadmapping, and risk assessments for future human exploration beyond low-Earth orbit. Emphasis was placed on developing recommendations on what could be done now to effect future exploration activities. The Exploration Blueprint team embraced the "Stepping Stone" approach to exploration where human and robotic activities are conducted through progressive expansion outward beyond low-Earth orbit. Results from this study produced a long-term strategy for exploration with near-term implementation plans, program recommendations, and technology investments. Specific results included the development of a common exploration crew vehicle concept, a unified space nuclear strategy, focused bioastronautics research objectives, and an integrated human and robotic exploration strategy. Recommendations from the Exploration Blueprint included the endorsement of the Nuclear Systems Initiative, augmentation of the bioastronautics research, a focused space transportation program including heavy-lift launch and a common exploration vehicle design for ISS and exploration missions, as well as an integrated human and robotic exploration strategy for Mars.

Bret G Drake↗