SEARCH · Search NASA

Results for “team building”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

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

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS2006

The Challenges of Integrating NASA's Human, Budget, and Data Capital within the Constellation Program's Exploration Launch Projects Office

Kidd, Luanne↗

NASA NTRS2007

The Challenges of Integrating NASA's Human, Budget, and Data Capital within the Constellation Program's Exploration Launch Projects Office

The U.S. Vision for Space Exploration directs NASA to retire the Space Shuttle in 2010 and replace it with safe, reliable, and cost-effective space transportation systems for crew and cargo travel to the Moon, Mars, and beyond. Such emerging space transportation initiatives face massive organizational challenges, including building and nurturing an experienced, dedicated team with the right skills for the required tasks; allocating and tracking the fiscal capital invested in achieving technical progress against an integrated master schedule; and turning generated data into useful knowledge that equips the team to design and develop superior products for customers and stakeholders. It has been more than 30 years since the Space Shuttle was designed; therefore, the current aerospace workforce has limited experience with developing new designs for human-rated spaceflight hardware. To accomplish these activities, NASA is using a wide range of state-of-the-art information technology tools that connect its diverse, decentralized teams and provide timely, accurate information for decision makers. In addition, business professionals are assisting technical managers with planning, tracking, and forecasting resource use against an integrated master schedule that horizontally and vertically interlinks hardware elements and milestone events. Furthermore, NASA is employing a wide variety of strategies to ensure that it has the motivated and qualified staff it needs for the tasks ahead. This paper discusses how NASA's Exploration Launch Projects Office, which is responsible for delivering these new launch vehicles, integrates its resources to create an engineering business environment that promotes mission success, which is defined by replacing the Space Shuttle by 2014 and returning to the Moon by 2020.

Kidd, Luanne↗

NASA NTRS2010

Mission Operations Directorate - Success Legacy of the Space Shuttle Program

Azbell, Jim↗

NASA NTRS2011

Mission Operations Directorate - Success Legacy of the Space Shuttle Program (Overview of the Evolution and Success Stories from MOD During the Space Shuttle program)

In support of the Space Shuttle Program, as well as NASA's other human space flight programs, the Mission Operations Directorate (MOD) at the Johnson Space Center has become the world leader in human spaceflight operations. From the earliest programs - Mercury, Gemini, Apollo - through Skylab, Shuttle, ISS, and our Exploration initiatives, MOD and its predecessors have pioneered ops concepts and emphasized a history of mission leadership which has added value, maximized mission success, and built on continual improvement of the capabilities to become more efficient and effective. This paper provides specific examples that illustrate how MOD's focus on building and contributing value with diverse teams has been key to their successes both with the US space industry and the broader international community. This paper will discuss specific examples for the Plan, Train, Fly, and Facilities aspects within MOD. This paper also provides a discussion of the joint civil servant/contractor environment and the relative badge-less society within MOD. Several Shuttle mission related examples have also been included that encompass all of the aforementioned MOD elements and attributes, and are used to show significant MOD successes within the Shuttle Program. These examples include the STS-49 Intelsat recovery and repair, the (post-Columbia accident) TPS inspection process and the associated R-Bar Pitch Maneuver for ISS missions, and the STS-400 rescue mission preparation efforts for the Hubble Space Telescope repair mission. Since their beginning, MOD has consistently demonstrated their ability to evolve and respond to an ever changing environment, effectively prepare for the expected and successfully respond to the unexpected, and develop leaders, expertise, and a culture that has led to mission and Program success.

Azbell, Jim A.↗

NASA NTRS2011

Mission Operations Directorate - Success Legacy of the Space Shuttle Program

In support of the Space Shuttle Program, as well as NASA s other human space flight programs, the Mission Operations Directorate (MOD) at the Johnson Space Center has become the world leader in human spaceflight operations. From the earliest programs - Mercury, Gemini, Apollo - through Skylab, Shuttle, ISS, and our Exploration initiatives, MOD and its predecessors have pioneered ops concepts and emphasized a history of mission leadership which has added value, maximized mission success, and built on continual improvement of the capabilities to become more efficient and effective. MOD s focus on building and contributing value with diverse teams has been key to their successes both with the US space industry and the broader international community. Since their beginning, MOD has consistently demonstrated their ability to evolve and respond to an ever changing environment, effectively prepare for the expected and successfully respond to the unexpected, and develop leaders, expertise, and a culture that has led to mission and Program success.

Azbell, James A.↗

NASA NTRS2013

Structural Dynamics and Data Analysis

This project consists of two parts, the first will be the post-flight analysis of data from a Delta IV launch vehicle, and the second will be a Finite Element Analysis of a CubeSat. Shock and vibration data was collected on WGS-5 (Wideband Global SATCOM- 5) which was launched on a Delta IV launch vehicle. Using CAM (CAlculation with Matrices) software, the data is to be plotted into Time History, Shock Response Spectrum, and SPL (Sound Pressure Level) curves. In this format the data is to be reviewed and compared to flight instrumentation data from previous flights of the same launch vehicle. This is done to ensure the current mission environments, such as shock, random vibration, and acoustics, are not out of family with existing flight experience. In family means the peaks on the SRS curve for WGS-5 are similar to the peaks from the previous flights and there are no major outliers. The curves from the data will then be compiled into a useful format so that is can be peer reviewed then presented before an engineering review board if required. Also, the reviewed data will be uploaded to the Engineering Review Board Information System (ERBIS) to archive. The second part of this project is conducting Finite Element Analysis of a CubeSat. In 2010, Merritt Island High School partnered with NASA to design, build and launch a CubeSat. The team is now called StangSat in honor of their mascot, the mustang. Over the past few years, the StangSat team has built a satellite and has now been manifested for flight on a SpaceX Falcon 9 launch in 2014. To prepare for the final launch, a test flight was conducted in Mojave, California. StangSat was launched on a Prospector 18D, a high altitude rocket made by Garvey Spacecraft Corporation, along with their sister satellite CP9 built by California Polytechnic University. However, StangSat was damaged during an off nominal landing and this project will give beneficial insights into what loads the CubeSat experienced during the crash. During the year, the MIHS students generated a SolidWorks (CAD software) geometry model of StangSat. This model will be imported into FEMAP (Finite Element Analysis (FEA) Software) and a finite element model wiiJ be created to predict the loads encountered during the crash of this rocket. This analysis will require learning how to import CAD models into the FEM, mesh and add constraints and concentrated masses to represent components inside the CubeSat frame, such as circuit boards, batteries and accelerometers. During the analysis the loads will be varied, in effort to duplicate the damage to the CubeSat. Results will then be peer reviewed and documented.

Luthman, Briana L.↗

NASA NTRS2016

NASA - Beyond Boundaries

NASA is able to achieve human spaceflight goals in partnership with international and commercial teams by establishing common goals and building connections. Presentation includes photographs from NASA missions - on orbit, in Mission Control, and at other NASA facilities.

McMillan, Courtenay↗

NASA NTRS2017

Dynamic Modeling, Controls, and Testing for Electrified Aircraft

Electrified aircraft have the potential to provide significant benefits for efficiency and emissions reductions. To assess these potential benefits, modeling tools are needed to provide rapid evaluation of diverse concepts and to ensure safe operability and peak performance over the mission. The modeling challenge for these vehicles is the ability to show significant benefits over the current highly refined aircraft systems. The STARC-ABL (single-aisle turbo-electric aircraft with an aft boundary layer propulsor) is a new test proposal that builds upon previous N3-X team hybrid designs. This presentation describes the STARC-ABL concept, the NASA Electric Aircraft Testbed (NEAT) which will allow testing of the STARC-ABL powertrain, and the related modeling and simulation efforts to date. Modeling and simulation includes a turbofan simulation, Numeric Propulsion System Simulation (NPSS), which has been integrated with NEAT; and a power systems and control model for predicting testbed performance and evaluating control schemes. Model predictions provide good comparisons with testbed data for an NPSS-integrated test of the single-string configuration of NEAT.

Connolly, Joseph↗

NASA NTRS2003

NASA's Secured Advanced Federated Environment

In 1999, a NASA-wide team initially set out to create a collaborative environment to enable NASA's scientists and engineers to share information and tools across NASA locations and with world-wide partners. This paper describes the team's development process and solutions in resolving conflicting security issues of building a complex intra/inter-enterprise collaborative system. Based on the federated, hierarchical, compartmentalized principles, the Secured Advanced Federated Environment (SAFE) developed by the team is becoming a foundational element for building a collaborative infrastructure for NASA. This paper also introduces the concept of a Micro Security Domain which can achieve the balance between the need to collaborate and the need to enforce enterprise and local security rules. SAFE'S federated security concepts enables networks to be formed around the functional/security requirements. With the SAFE technologies and approaches, security will not be an afterthought of the enterprise network design.

network designs↗

NASA NTRS1992

Environmental qualification testing of payload G-534, the Pool Boiling Experiment

Payload G-534, the prototype Pool Boiling Experiment (PBE), is scheduled to fly on the STS-47 mission in September 1992. This paper describes the purpose of the experiment and the environmental qualification testing program that was used to prove the integrity of the hardware. Component and box level vibration and thermal cycling tests were performed to give an early level of confidence in the hardware designs. At the system level, vibration, thermal extreme soaks, and thermal vacuum cycling tests were performed to qualify the complete design for the expected shuttle environment. The system level vibration testing included three axis sine sweeps and random inputs. The system level hot and cold soak tests demonstrated the hardware's capability to operate over a wide range of temperatures and gave wider latitude in determining which shuttle thermal attitudes were compatible with the experiment. The system level thermal vacuum cycling tests demonstrated the hardware's capability to operate in a convection free environment. A unique environmental chamber was designed and fabricated by the PBE team and allowed most of the environmental testing to be performed within the hardware build laboratory. The completion of the test program gave the project team high confidence in the hardware's ability to function as designed during flight.

Sexton, J. Andrew↗

NASA NTRSDate not supplied

Lessons Learned in Systems Engineering Availability and Recommendations for Mission Technical Leaders

In spaceflight missions at Goddard Space Flight Center (GSFC), the Mission System Engineer (MSE) is the technical leader of the overall engineering team and also is the Independent Engineering Technical Authority. The responsibility of this role includes the definition of the mission design architecture, concept of operations, and mission requirements, management of risk throughout the development, and verification and validation of the final system performance and function amongst other duties. This responsibility inherently requires time management, enabling focus on a balanced development with appropriate risk. Time is the most valuable resource of the MSE. The system engineer’s availability to interact with the development team (often product or component design leads and technicians, often in different worksites) to discover and mitigate mission risks during development is key to mission success. This paper presents examples from Lunar Reconnaissance Orbiter, Landsat 9, and Neutron star Interior Composition ExploreR (NICER) which represent in-house and out-of-house hardware builds. These examples demonstrate how interactions between the Mission Systems Engineers and other project and partner engineers result in discovery of critical risks, leading to early mitigation with significant cost and performance savings. These three missions would have suffered test failures or on-orbit failures had their MSEs not set aside time to visit engineers and technicians that were working on key pieces of space flight hardware. Availability is more than just time; it is openness to listen to concerns and questions. It begins by building a level of trust in the team that it is safe to ask questions or share concerns without the fear of blame or additional workload. It also requires enabling informal conversations (over lunch, coffee, in the clean room, or at the team members desk, etc.) where key information can be exchanged, and team members may even provide an easy-to-implement mitigation idea for another subsystem. Availability is a highly valuable commodity and completely non-obvious to protect and optimize. The natural tendency of engineers is to keep themselves busy with solving problems that they know about. This paper is encouraging MSEs to resist this tendency to try and solve all the complex problems themselves and actively devote daily time to learning and solving problems that are found with informal communications with other team members.

Lessons Learned↗

NASA NTRS1994

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Mahmot, Ron↗

NASA NTRS2017

Using A Model-Based Systems Engineering Approach For Exploration Medical System Development

NASA's Human Research Program's Exploration Medical Capabilities (ExMC) element is defining the medical system needs for exploration class missions. ExMC's Systems Engineering (SE) team will play a critical role in successful design and implementation of the medical system into exploration vehicles. The team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." Development of the medical system is being conducted in parallel with exploration mission architecture and vehicle design development. Successful implementation of the medical system in this environment will require a robust systems engineering approach to enable technical communication across communities to create a common mental model of the emergent engineering and medical systems. Model-Based Systems Engineering (MBSE) improves shared understanding of system needs and constraints between stakeholders and offers a common language for analysis. The ExMC SE team is using MBSE techniques to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. Systems Modeling Language (SysML) is the specific language the SE team is utilizing, within an MBSE approach, to model the medical system functional needs, requirements, and architecture. Modeling methods are being developed through the practice of MBSE within the team, and tools are being selected to support meta-data exchange as integration points to other system models are identified. Use of MBSE is supporting the development of relationships across disciplines and NASA Centers to build trust and enable teamwork, enhance visibility of team goals, foster a culture of unbiased learning and serving, and be responsive to customer needs. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. Here, we describe the methods and approach to building this integrated model.

Hanson, A.↗

NASA NTRS2004

Development of Columbia Leading Edge Reconstruction System

After the loss of Columbia in 2003, the Columbia Accident Investigation Board and NASA KSC directed personnel at the Launch Equipment Test Facility (LETF) to design and build high fidelity mock-ups of Columbia's left wing leading edges. These leading edge segments, constructed of reinforced carbon-carbon, were a major point of inquiry by the investigation team. The LETF engineers developed a concept of building a clear Lexan panel with an aluminum support structure ten percent larger than the original panel. The leading edge debris are attached to the Lexan panels and both the front and back side of each panel are visible for inspection. The entire assembly can be rotated, to provide visual access to the entire panel. Six carts were fabricated to support the thirteen panels. These carts could be set up in order, next to each other, to provide the desired inspection access. The carts and attached debris are currently located in the Vehicle Assembly Building at KSC.

Trautwein, John↗

NASA NTRS2009

Prototype Common Bus Spacecraft: Hover Test Implementation and Results

In order to develop the capability to evaluate control system technologies, NASA Ames Research Center (Ames) began a test program to build a Hover Test Vehicle (HTV) - a ground-based simulated flight vehicle. The HTV would integrate simulated propulsion, avionics, and sensors into a simulated flight structure, and fly that test vehicle in terrestrial conditions intended to simulate a flight environment, in particular for attitude control. The ultimate purpose of the effort at Ames is to determine whether the low-cost hardware and flight software techniques are viable for future low cost missions. To enable these engineering goals, the project sought to develop a team, processes and procedures capable of developing, building and operating a fully functioning vehicle including propulsion, GN&C, structure, power and diagnostic sub-systems, through the development of the simulated vehicle.

Hine, Butler Preston↗

NASA NTRSDate not supplied

Thinking Inside the Box: A Hands-On Student Activity for Building a Contamination Containment Glovebox to Encourage Problem Solving in a Collaborative Environment

Contamination containment gloveboxes are sealed containers where operators outside the glovebox can safely manipulate hazardous or contamination-sensitive materials inside the glovebox through glove ports on the container. Containment gloveboxes are used in the space industry to study sample materials returned from space such as lunar, asteroid, and comet materials, to manufacture sensitive instruments and space ight hardware, and to perform contamination-sensitive experiments. A hands-on activity has been developed by contamination control engineer and STEM education experts as part of the Virginia Earth System Science Scholars (VESSS) summer academy program to teach high school students about gloveboxes and about problem solving in a collaborative environment. In this activity, student teams are given a list of common household materials (e.g. plastic bags, plastic straws, aluminum foil, tape, disposable gloves, etc.) for building their own glovebox. Students work together to sketch and design their glovebox before being provided a kit of materials, which they must purchase along with any extra materials with a mock team budget. They are given 30 minutes to build their glovebox, however, they do not know what will be placed inside the glovebox or what operations they will need to perform within the glovebox. At the end of the build time, teams are given a small, sealed paper envelope which they place in the glovebox. Each team selects a team member to be designated as the operator, and the operator places their hands in the gloves of the glovebox. The operator uses their gloves to open the envelope in the glovebox, and they discover they have 20 minutes to assemble a jigsaw puzzle. However, the puzzle is \contaminated" with talcum powder. After the 20 minute time period, teams are judged on how well they completed and cleaned the contaminated puzzle. In a post-activity debrief, teams discuss lessons learned such as how the actual built box di ered from the sketched design, the challenge of managing a budget for materials, how the team dealt with surprises, and if their glovebox allowed enough room for the operator to perform the task. This activity has been part of the VESSS summer academy since 2016, and teaches students teamwork, creativity, hands-on experimentation, communication, and reasoning skills. In a demonstration at IAC, a volunteer from the audience will be chosen to assemble a glovebox during the presentation using the same kit of materials and will demonstrate handling puzzle pieces in the completed glovebox.

Elaine Seasly↗

NASA NTRS2007

The Next Giant Leap: NASA's Ares Launch Vehicles Overview

The National Aeronautics and Space Administration (NASA)'s Constellation Program is developing new launch vehicles (Ares) and spacecraft (Orion) to send astronauts to the Moon, Mars, and beyond. This paper presents plans, projections, and progress toward fielding the Ares I and Ares V vehicles, and the Ares I-X test flight in 2009. NASA is building on both new research and aeronautical capabilities, as well as lessons learned from almost 50 years of aerospace experience. The Ares Projects Office (APO) completed the Ares I System Requirements Review (SRR) in 2006 and the System Definition Review in autumn 2007; and will focus on the Preliminary Design Review in 2008. Ares I is currently being refined to meet safety, operability, reliability, and affordability goals. The Ares team is simultaneously testing Ares I elements and building hardware for Ares I-X, while the Ares V is in the early design stage, with the team validating requirements and ensuring commonality with Ares I. Ares I and V are key to opening the space frontier for peaceful endeavors.

Cook, Stephen A.↗

NASA NTRS2008

Ares I Crew Launch Vehicle Upper Stage/Upper Stage Engine Element Overview

The Ares I upper stage is an integral part of the Constellation Program transportation system. The upper stage provides guidance, navigation and control (GN and C) for the second stage of ascent flight for the Ares I vehicle. The Saturn-derived J-2X upper stage engine will provide thrust and propulsive impulse for the second stage of ascent flight for the Ares I launch vehicle. Additionally, the upper stage is responsible for the avionics system of the the entire Ares I. This brief presentation highlights the requirements, design, progress and production of the upper stage. Additionally, test facilities to support J-2X development are discussed and an overview of the operational and manufacturing flows are provided. Building on the heritage of the Apollo and Space Shuttle Programs, the Ares I Us and USE teams are utilizing extensive lessons learned to place NASA and the US into another era of space exploration. The NASA, Boeing and PWR teams are integrated and working together to make progress designing and building the Ares I upper stage to minimize cost, technical and schedule risks.

McArthur, J. Craig↗