Search NASA⌕ Search

SEARCH · Search NASA

Results for “Team cohesion”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2012

Astronaut Biography Project for Countermeasures of Human Behavior and Performance Risks in Long Duration Space Flights

This final report will summarize research that relates to human behavioral health and performance of astronauts and flight controllers. Literature reviews, data archival analyses, and ground-based analog studies that center around the risk of human space flight are being used to help mitigate human behavior and performance risks from long duration space flights. A qualitative analysis of an astronaut autobiography was completed. An analysis was also conducted on exercise countermeasure publications to show the positive affects of exercise on the risks targeted in this study. The three main risks targeted in this study are risks of behavioral and psychiatric disorders, risks of performance errors due to poor team performance, cohesion, and composition, and risks of performance errors due to sleep deprivation, circadian rhythm. These three risks focus on psychological and physiological aspects of astronauts who venture out into space on long duration space missions. The purpose of this research is to target these risks in order to help quantify, identify, and mature countermeasures and technologies required in preventing or mitigating adverse outcomes from exposure to the spaceflight environment

Banks, Akeem↗
NASA NTRSDate not supplied

Leveraging Nurse Informaticists for Development of the Impact Tool

The American Nurses Association (ANA) defines nursing informatics as the integration of “nursing science, computer science, and information science to manage and communicate data, information, knowledge, and wisdom in nursing practice. [1]” In additional to nursing education and clinical experience, this field requires additional education in areas of data analysis, database management, and clinical information systems. Nursing informaticists help bridge the communication gap between clinical and technical stakeholders which help align common goals. NASA is currently developing a new medical system trade analysis and decision support tool called IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces). The development team is comprised of multiple specialties including but not limited to clinicians (pharmacists, physicians, and nurse informaticists), software and program developers, human factors experts, and engineers. The nurse informaticists play a significant role in the development, operation, and results interpretation of IMPACT. Their expert knowledge and skills in both clinical nursing, information science, and database management place them in a unique position to collaborate and integrate with the clinical, engineering, and software development members of the team to achieve a cohesive, functional, and user-friendly model.

Lynn Boley↗
NASA NTRS1985

Group structure and group process for effective space station astronaut teams

Space Station crews will encounter new problems, many derived from the social interaction of groups working in space for extended durations. Solutions to these problems must focus on the structure of groups and the interaction of individuals. A model of intervention is proposed to address problems of interpersonal relationships and emotional stress, and improve the morale, cohesiveness, and productivity of astronaut teams.

Nicholas, J. M.↗
NASA NTRS2002

Activation Energy

Teaming is so common in today's project management environment that most of us assume it comes naturally. We further assume that when presented with meaningful and challenging work, project teams will naturally engage in productive activity to complete their tasks. This assumption is expressed in the simple (but false) equation: Team + Work = Teamwork. Although this equation appears simple and straightforward, it is far from true for most project organizations whose reality is a complex web of institutional norms based on individual achievement and rewards. This is illustrated by the very first successful team experience from my early Air Force career. As a young lieutenant, I was sent to Squadron Officer School, which was the first in the series of Air Force professional military education courses I was required to complete during my career. We were immediately formed into teams of twelve officers. Much of the course featured competition between these teams. As the most junior member of my team, I quickly observed the tremendous pressure to show individual leadership capability. At one point early in the course, almost everyone in our group was vying to become the team leader. This conflict was so intense that it caused us to fail miserably in our first outdoor team building exercise. We spent so much time fighting over leadership that we were unable to complete any of the events on the outdoor obstacle course. This complete lack of success was so disheartening to me that I gave our team little hope for future success. What followed was a very intense period of bickering, conflict, and even shouting matches as our dysfunctional team tried to cope with our early failures and find some way to succeed. British physician and researcher Wilfred Bion (Experiences in Groups, 1961) discovered that there are powerful psychological forces inherent in all groups that divert from accomplishing their primary tasks. To overcome these restraining forces and use the potential power of the team, greater emphasis must be placed on establishing and maintaining group cohesiveness. This relationship is expressed in the revised (true) mathematical equation: Team + Work (on the Team) = Teamwork.

Gadeken, Owen↗
NASA NTRS2009

The Habitat Demonstration Unit System Integration

The Lunar Surface System Habitat Demonstration Unit (HDU) will require the project team to integrate a variety of contributions from NASA centers and potential outside collaborators and poses a challenge in integrating these disparate efforts into a cohesive architecture. To accomplish the development of the HDU from conception in June 2009 to rollout for operations in July 2010, the HDU team is using several strategies to mitigate risks and bring the separate efforts together. First, a set of design standards is being developed to define the interfaces between the various systems of HDU and to the payloads, such as the Geology Lab, that those systems will support. Scheduled activities such as early fit-checks and the utilization of a Habitat avionics test bed prior to equipment installation into HDU. A coordinated effort to establish simplified Computer Aided Design standards and the utilization of a modeling and simulation systems will aid in design and integration concept development. Finally, decision processes on the shell development including the assembly sequence and the transportation have been fleshed out early on HDU to maximize the efficiency of both integration and field operations.

Kennedy, Kriss J.↗
NASA NTRS2011

The SDO Education and Outreach (E/PO) Program: Changing Perceptions One Program at a Time

The Solar Dynamics Observatory (SDO) Education and Public Outreach (E/PO) program began as a series of discrete efforts implemented by each of the instrument teams and has evolved into a well-rounded program with a full suite of national and international programs. The SDO E/PO team has put forth much effort in the past few years to increase our cohesiveness by adopting common goals and increasing the amount of overlap between our programs. In this paper, we outline the context and overall philosophy for our combined programs, present a brief overview of all SDO E/PO programs along with more detailed highlight of a few key programs, followed by a review of our results up to date. Concluding is a summary of the successes, failures, and lessons learned that future missions can use as a guide, while further incorporating their own content to enhance the public's knowledge and appreciation of NASA?s science and technology as well as its benefit to society.

Drobnes, E.↗
NASA NTRS2010

The Habitat Demonstration Unit System Integration

The Lunar Surface System Habitat Demonstration Unit (HDU) will require a project team to integrate a variety of contributions from National Aeronautics and Space Administration (NASA) centers and potential outside collaborators and poses a challenge in integrating these disparate efforts into a cohesive architecture. To accomplish the development of the first version of the HDU, the Pressurized Excursion Module (PEM), from conception in June 2009 to rollout for operations in July 2010, the HDU project team is using several strategies to mitigate risks and bring the separate efforts together. First, a set of design standards is being developed to define the interfaces between the various systems of PEM and to the payloads, such as the Geology Laboratory, that those systems will support. Scheduled activities such as early fit-checks and the utilization of a habitat avionics test bed prior to equipment installation into HDU PEM are planned to facilitate the integration process. A coordinated effort to establish simplified Computer Aided Design (CAD) standards and the utilization of a modeling and simulation systems will aid in design and integration concept development. Finally, decision processes on the shell development including the assembly sequence and the transportation have been fleshed out early on HDU design to maximize the efficiency of both integration and field operations.

Gill, Tracy R.↗
NASA NTRSDate not supplied

Artemis Internal Science Team: Mission Planning Update

As eloquently outlined in the Artemis III Science Definition Team (A3SDT) Report, the definitive statement of science priorities for the first crewed landing of the Artemis program, the return of astronauts to the surface of the Moon is expected to yield paradigm-shifting scientific advances across a wide array of scientific disciplines while facilitating the creation of a thriving cislunar economy. To help establish a cohesive management for the Artemis campaign, the NASA Science Mission Directorate (SMD) and the Exploration Systems Development Mission Directorate (ESDMD) have established an Artemis Internal Science Team to complement future competed surface geology and payload science teams while executing critical programmatic functions at the point of hardware element interface decisions. Here, we describe aspects of Artemis III mission planning, specifically the current progress towards selection of candidate exploration regions for the Artemis III mission.

Artemis↗
NASA NTRS2019

A Unified Level of Service Model for NASA Earth Science Data Stewardship

During the past year, the Interagency Implementation and Concepts Team (IMPACT) reviewed existing service models in use at various NASA data centers in an effort to produce a unified, cohesive, and comprehensive Level of Service Model for all of NASA Distributed Active Archive Centers (DAACs). NASA DAACs are responsible for ensuring NASA Earth Science data are accurately and securely ingested, distributed, supported, and preserved. The term “Service" as used here refers to the spectrum of data management activities and outputs provided by DAACs in support of the data cared fo by each data cente. The unified Level-of- Service (LoS) model described in this presentation utilizes both the NASA-defined data product category and the data processing level to easily identify an appropriate level-of-service to be applied to a data product throughout the full data life cycle. This LoS model is to be used by DAACs when appraising incoming data in order to determine the appropriate and required services to provide. The LoS model utilizes a 3-level system in which services build upon previous levels and thereby require greater commitment and effort both on the part of the DAAC personnel and the data producer at the highest level. The LoS model description also contains examples of ways to communicate with data producers and data users what services can be expected, thereby bringing more consistent user experiences across the enterprise. In this presentation, we will outline the features of the LoS model and describe how it relates to the FAIR data practices and the NOAA Maturity Matrix model.

Smith, Deborah↗
NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA’s Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA’s Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V’s desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V’s assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Gerek Whitman↗
NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA's Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA's Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V's desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V's assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Whitman, Gerek↗
NASA NTRS2010

MaROS Strategic Relay Planning and Coordination Interfaces

The Mars Relay Operations Service (MaROS) is designed to provide planning and analysis tools in support of ongoing Mars Network relay operations. Strategic relay planning requires coordination between lander and orbiter mission ground data system (GDS) teams to schedule and execute relay communications passes. MaROS centralizes this process, correlating all data relevant to relay coordination to provide a cohesive picture of the relay state. Service users interact with the system through thin-layer command line and web user interface client applications. Users provide and utilize data such as lander view periods of orbiters, Deep Space Network (DSN) antenna tracks, and reports of relay pass performance. Users upload and download relevant relay data via formally defined and documented file structures including some described in Extensible Markup Language (XML). Clients interface with the system via an http-based Representational State Transfer (ReST) pattern using Javascript Object Notation (JSON) formats. This paper will provide a general overview of the service architecture and detail the software interfaces and considerations for interface design.

Allard, Daniel A.↗
NASA NTRS2010

Integration Process for the Habitat Demonstration Unit

The Habitat Demonstration Unit (HDU) is an experimental exploration habitat technology and architecture test platform designed for analog demonstration activities The HDU project has required a team to integrate a variety of contributions from NASA centers and outside collaborators and poses a challenge in integrating these disparate efforts into a cohesive architecture To complete the development of the HDU from conception in June 2009 to rollout for operations in July 2010, a cohesive integration strategy has been developed to integrate the various systems of HDU and the payloads, such as the Geology Lab, that those systems will support The utilization of interface design standards and uniquely tailored reviews have allowed for an accelerated design process Scheduled activities include early fit-checks and the utilization of a Habitat avionics test bed prior to equipment installation into HDU A coordinated effort to utilize modeling and simulation systems has aided in design and integration concept development Modeling tools have been effective in hardware systems layout, cable routing and length estimation, and human factors analysis Decision processes on the shell development including the assembly sequence and the transportation have been fleshed out early on HDU to maximize the efficiency of both integration and field operations Incremental test operations leading up to an integrated systems test allows for an orderly systems test program The HDU will begin its journey as an emulation of a Pressurized Excursion Module (PEM) for 2010 field testing and then may evolve to a Pressurized Core Module (PCM) for 2011 and later field tests, depending on agency architecture decisions The HDU deployment will vary slightly from current lunar architecture plans to include developmental hardware and software items and additional systems called opportunities for technology demonstration One of the HDU challenges has been designing to be prepared for the integration of presently unanticipated systems Results of the HDU field tests will influence future designs of habitat systems.

Gill, Tracy↗
NASA NTRS1985

Improved turbopump dynamics

A study was initiated to investigate the practicality of increasing rotor critical speeds by changes in manufacturing method. The technique would be to build a pump with an all laser welded shaft and case; such unit to be opened by laser cutting and rebuilt by rewelding the same surface. Use of a split casing, common in industry, would permit assembly of the rotor outside the case. A team was formed to perform the study; however, the work of the team was severely restricted by conflict with higher priority tasks. No manpower was available to evaluate alternate configurations. Thus, much of the synergetic effects of cohesive design modification was lost. Although very limited results were achieved, nothing was found to indicate that the method is not worth further investigation.

Kiefling, L.↗
NASA NTRS2003

Team Software Development for Aerothermodynamic and Aerodynamic Analysis and Design

A collaborative approach to software development is described. The approach employs the agile development techniques: project retrospectives, Scrum status meetings, and elements of Extreme Programming to efficiently develop a cohesive and extensible software suite. The software product under development is a fluid dynamics simulator for performing aerodynamic and aerothermodynamic analysis and design. The functionality of the software product is achieved both through the merging, with substantial rewrite, of separate legacy codes and the authorship of new routines. Examples of rapid implementation of new functionality demonstrate the benefits obtained with this agile software development process. The appendix contains a discussion of coding issues encountered while porting legacy Fortran 77 code to Fortran 95, software design principles, and a Fortran 95 coding standard.

Alexandrov, N.↗
NASA NTRS2011

Integration Process for the Habitat Demonstration Unit

The Habitat Demonstration Unit (HDU) is an experimental exploration habitat technology and architecture test platform designed for analog demonstration activities. The HDU previously served as a test bed for testing technologies and sub-systems in a terrestrial surface environment. in 2010 in the Pressurized Excursion Module (PEM) configuration. Due to the amount of work involved to make the HDU project successful, the HDU project has required a team to integrate a variety of contributions from NASA centers and outside collaborators The size of the team and number of systems involved With the HDU makes Integration a complicated process. However, because the HDU shell manufacturing is complete, the team has a head start on FY--11 integration activities and can focus on integrating upgrades to existing systems as well as integrating new additions. To complete the development of the FY-11 HDU from conception to rollout for operations in July 2011, a cohesive integration strategy has been developed to integrate the various systems of HDU and the payloads. The highlighted HDU work for FY-11 will focus on performing upgrades to the PEM configuration, adding the X-Hab as a second level, adding a new porch providing the astronauts a larger work area outside the HDU for EVA preparations, and adding a Hygiene module. Together these upgrades result in a prototype configuration of the Deep Space Habitat (DSH), an element under evaluation by NASA's Human Exploration Framework Team (HEFT) Scheduled activates include early fit-checks and the utilization of a Habitat avionics test bed prior to installation into HDU. A coordinated effort to utilize modeling and simulation systems has aided in design and integration concept development. Modeling tools have been effective in hardware systems layout, cable routing, sub-system interface length estimation and human factors analysis. Decision processes on integration and use of all new subsystems will be defined early in the project to maximize the efficiency of both integration and field operations. In addition a series of tailored design reviews are utilized to quickly define the systems and their integration into the DSH configuration. These processes are necessary to ensure activities, such as partially reversing integration of the X-Hab second story of the HDU and deploying and stowing the new work porch for transportation to the JSC Rock Yard and to the Arizona Black Point Lava Flow Site are performed with minimal or no complications. In addition, incremental test operations leading up to an Integrated systems test allows for an orderly systems test program. For FY-11 activities, the HDU DSH will act as a laboratory utilizing a new X-Hab inflatable second floor with crew habitation features. In addition to the day to day operations involving maintenance of the HDU and exploring the surrounding terrain, testing and optimizing the use of the new X-Hab, work porch, Hygiene Module, and other sub-system enhancements will be the focus of the FY-11 test objectives. The HDU team requires a successful integration strategy using a variety of tools and approaches to prepare the DSH for these test objectives. In a challenging environment where the prototyping influences the system design, as well as Vice versa, results of the HDU DSH field tests will influence future designs of habitat systems.

Gill, Tracy↗
NASA NTRS2002

Strategic Plan

The purpose of this document is to present the strategic plan and associated organizational structure that the National Space Biomedical Research Institute (NSBRI) will utilize to achieve the defined mission and objectives provided by NASA. Much of the information regarding the background and establishment of the NSBRI by NASA has been provided in other documentation and will not be repeated in this Strategic Plan. This Strategic Plan is presented in two volumes. Volume I (this volume) begins with an Introduction (Section 2) that provides the Institute's NASA-defined mission and objectives, and the organizational structure adopted to implement these through three Strategic Programs: Countermeasure Research; Education, Training and Outreach; and Cooperative Research and Development. These programs are described in Sections 3 to 5. Each program is presented in a similar way, using four subsections: Goals and Objectives; Current Strategies; Gaps and Modifications; and Resource Requirements. Section 6 provides the administrative infrastructure and total budget required to implement the Strategic Programs and assures that they form a single cohesive plan. This plan will ensure continued success of the Institute for the next five years. Volume II of the Strategic Plan provides an in-depth analysis of the current and future strategic programs of the 12 current NSBRI teams, including their goals, objectives, mutual interactions and schedules.

Source record↗
NASA NTRS2016

Graphical Visualization of Human Exploration Capabilities

NASA's pioneering space strategy will require advanced capabilities to expand the boundaries of human exploration on the Journey to Mars (J2M). The Evolvable Mars Campaign (EMC) architecture serves as a framework to identify critical capabilities that need to be developed and tested in order to enable a range of human exploration destinations and missions. Agency-wide System Maturation Teams (SMT) are responsible for the maturation of these critical exploration capabilities and help formulate, guide and resolve performance gaps associated with the EMC-identified capabilities. Systems Capability Organization Reporting Engine boards (SCOREboards) were developed to integrate the SMT data sets into cohesive human exploration capability stories that can be used to promote dialog and communicate NASA's exploration investments. Each SCOREboard provides a graphical visualization of SMT capability development needs that enable exploration missions, and presents a comprehensive overview of data that outlines a roadmap of system maturation needs critical for the J2M. SCOREboards are generated by a computer program that extracts data from a main repository, sorts the data based on a tiered data reduction structure, and then plots the data according to specified user inputs. The ability to sort and plot varying data categories provides the flexibility to present specific SCOREboard capability roadmaps based on customer requests. This paper presents the development of the SCOREboard computer program and shows multiple complementary, yet different datasets through a unified format designed to facilitate comparison between datasets. Example SCOREboard capability roadmaps are presented followed by a discussion of how the roadmaps are used to: 1) communicate capability developments and readiness of systems for future missions, and 2) influence the definition of NASA's human exploration investment portfolio through capability-driven processes. The paper concludes with a description of planned future work to modify the computer program to include additional data and of alternate capability roadmap formats currently under consideration.

Rodgers, Erica M.↗