Search NASA⌕ Search

SEARCH · Search NASA

Results for “organizational learning”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

Evidence Report: Risk of Performance Errors Due to Training Deficiencies

Substantial evidence supports the claim that inadequate training leads to performance errors. Barshi and Loukopoulos (2012) demonstrate that even a task as carefully developed and refined over many years as operating an aircraft can be significantly improved by a systematic analysis, followed by improved procedures and improved training (see also Loukopoulos, Dismukes, & Barshi, 2009a). Unfortunately, such a systematic analysis of training needs rarely occurs during the preliminary design phase, when modifications are most feasible. Training is often seen as a way to compensate for deficiencies in task and system design, which in turn increases the training load. As a result, task performance often suffers, and with it, the operators suffer and so does the mission. On the other hand, effective training can indeed compensate for such design deficiencies, and can even go beyond to compensate for failures of our imagination to anticipate all that might be needed when we send our crew members to go where no one else has gone before. Much of the research literature on training is motivated by current training practices aimed at current training needs. Although there is some experience with operations in extreme environments on Earth, there is no experience with long-duration space missions where crews must practice semi-autonomous operations, where ground support must accommodate significant communication delays, and where so little is known about the environment. Thus, we must develop robust methodologies and tools to prepare our crews for the unknown. The research necessary to support such an endeavor does not currently exist, but existing research does reveal general challenges that are relevant to long-duration, high-autonomy missions. The evidence presented here describes issues related to the risk of performance errors due to training deficiencies. Contributing factors regarding training deficiencies may pertain to organizational process and training programs for spaceflight, such as when training programs are inadequate or unavailable. Furthermore, failure to match between tasks on the one hand, and learning and memory abilities on the other hand is a contributing factor, especially when individuals' relative efficiency with which new information is acquired, and adjustments made in behavior or thinking, are inconsistent with mission demands. Thus, if training deficiencies are present, the likelihood of errors or of the inability to successfully complete a task increases. What's more, the overall risk to the crew, the vehicle, and the mission increases.

Barshi, Immanuel↗
NASA NTRS2011

Accident Case Study of Organizational Silence Communication Breakdown: Shuttle Columbia, Mission STS-107

This report has been developed by the National Aeronautics and Space Administration (NASA) ESMD Risk and Knowledge Management team. This document provides a point-in-time, cumulative, summary of key lessons learned derived from the official Columbia Accident Investigation Board (CAIB). Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document. This report is accompanied by a video that will be sent at request

Lessons Learned↗
NASA NTRS2024

The Knowledge-based Digital Platform Concept for Advanced Air Mobility Research and Development

National Aeronautics and Space Administration (NASA) Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers (SE) together across organizational boundaries. The overarching vision for the KbDP Concept for AAM R&D is a substantial undertaking. The initial concept and implementation will focus on UAM operations to tractably learn and adjust the concept with a manageable database. Lessons learned and best practices with a smaller scope will enable successful scalability to AAM R&D or even to the entire modes of transportation and logistics. The UAM vision is one in which advanced technologies and new operational procedures enable practical and cost-effective air transport as an integrated mode of movement of people and goods throughout metropolitan areas. Initial implementation of three KbDP concepts of use shows promising benefits to NASA’s Air Traffic Management-Exploration (ATM-X) UAM Airspace Subproject. It is envisioned that the KbDP will manage an information database defined by mathematical, data science, and system engineering principles. AIML algorithms play a vital role in this KbDP concept by extracting meaningful knowledge from the information database, which the human user leverages to improve the efficiency and effectiveness of their research greatly.

ATM↗
NASA NTRS2017

Cleared for Launch - Lessons Learned from the OSIRIS-REx System Requirements Verification Program

Requirements verification of a large flight system is a challenge. It is especially challenging for engineers taking on their first role in space systems engineering. This paper describes our approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from developing systems engineers embroiled in this process. We begin with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including our implementation for managing the thousands of program and element level requirements and associated verification data. We discuss both successes and methods to improve the managing of this data across multiple organizational interfaces. Our approach to verifying system requirements at multiple levels of assembly is presented using examples from our work at instrument, spacecraft, and ground segment levels. We include a discussion of system end-to-end testing limitations and their impacts to the verification program. Finally, we describe lessons learned that are applicable to all emerging space systems engineers using our unique perspectives across multiple organizations of a large NASA program.

Requirements Verification↗
NASA NTRS2014

MDO and Cross-Disciplinary Practice in R&D: A Portrait of Principles and Current Practice

For several decades, Multidisciplinary Design Optimization (MDO) has served an important role in aerospace engineering by incorporating physics based disciplinary models into integrated system or sub-system models for use in research, development, (R&D) and design. This paper examines MDO's role in facilitating the integration of the researchers from different single disciplines during R&D and early design of large-scale complex engineered systems (LaCES) such as aerospace systems. The findings in this paper are summarized from a larger study on interdisciplinary practices and perspectives that included considerable empirical data from surveys, interviews, and ethnography. The synthesized findings were derived by integrating the data with theories from organization science and engineering. The over-arching finding is that issues related to cognition, organization, and social interrelations mostly dominate interactions across disciplines. Engineering issues, such as the integration of hardware or physics-based models, are not as significant. Correspondingly, the data showed that MDO is not the primary integrator of researchers working across disciplines during R&D and early design of LaCES. Cognitive focus such as analysis versus design, organizational challenges such as incentives, and social opportunities such as personal networks often drove the human interactive practices among researchers from different disciplines. Facilitation of the inherent confusion, argument, and learning in crossdisciplinary research was identified as one of several needed elements of enabling successful research across disciplines.

Rivas McGowan, Anna-Maria↗
NASA NTRS2007

A Return to Innovative Engineering Design, Critical Thinking and Systems Engineering

I believe we are facing a critical time where innovative engineering design is of paramount importance to the success of our aerospace industry. However, the very qualities and attributes necessary for enhancing, educating, and mentoring a creative spirit are in decline in important areas. The importance of creativity and innovation in this country was emphasized by a special edition of the Harvard Business Review OnPoint entitled: "The Creative Company" which compiled a series of past and present articles on the subject of creativity and innovation and stressed its importance to our national economy. There is also a recognition of a lack of engineering, critical thinking and problem-solving skills in our education systems and a trend toward trying to enhance those skills by developing K-12 educational programs such as Project Lead the Way, "Science for All Americans", Benchmarks 2061 , etc. In addition, with respect to spacecraft development, we have a growing need for young to mid-level engineers with appropriate experience and skills in spacecraft design, development, analysis, testing, and systems engineering. As the Director of Engineering at NASA's Johnson Space Center, I realized that sustaining engineering support of an operational human spacecraft such as the Space Shuttle is decidedly different than engineering design and development skills necessary for designing a new spacecraft such as the Crew Exploration Vehicle of the Constellation Program. We learned a very important lesson post Columbia in that the Space Shuttle is truly an experimental and not an operational vehicle and the strict adherence to developed rules and processes and chains of command of an inherently bureaucratic organizational structure will not protect us from a host of known unknowns let alone unknown unknowns. There are no strict rules, processes, or procedures for understanding anomalous results of an experiment, anomalies with an experimental spacecraft like Shuttle, or in the conceptual design of a spacecraft. Engineering design is as much an art as it is a science. The critical thinking skills necessary to uncover lurking problems in an experimental design and creatively develop solutions are some of the same skills necessary to design a new spacecraft. Thus, I believe engineers unfamiliar with or removed from design and development need time to transition and develop the required skill set to be effective spacecraft designers. I believe the creative process necessary in design can be enhanced and even taught as early as grades K-12 and should continue to be nurtured and developed at the university level and beyond. I am going to present a strategy for developing learning teams to address complex multidisciplinary problems and to creatively develop solutions to those problems rapidly at minimal cost. I will frame a real problem, the development of on-orbit thermal protection system repair of the Space Shuttle, and step through the series of skills necessary to enhance the creative process. The case study I will illustrate is based on a real project, the R&D Reinforced Carbon-Carbon (RCC) Repair Team's development of on-orbit repair concepts for damaged Space Shuttle RCC nose cap and/or leading edges.

Camarda, Charles J.↗
NASA NTRS2010

Making Games Not Work: Paradoxes Embedded in Game-Based Training and Concepts for Overcoming Them

An interest in game-based training solutions is natural. All one has to do is watch someone fully engaged in a modern game to see the potential of harnessing that attention for training. However, the reality of game-based training has not fully satisfied these expectations. This paper explains two paradoxes that must be overcome for games to support training. These paradoxes are a result of the realities of the basic human condition clashing with the requirements of learning theory. 80th paradoxes arise from the concept of "engagement" that is central to games. The first comes from a more robust definition of engagement, which is the condition of Flow or Optimal Experience. Flow is the state game developers want to see in users. One aspect of Flow is loss of sense of self as the individual becomes immersed in the experience. The paradox arises because this loss of self directly contradicts the learning requirement of self-reflection. The second paradox comes from theories of play, which state in part that play requires a level of individual freedom. The contradiction arises when game-based play must be harnessed to an organizational training program or regimen. The paper will discuss these paradoxes in the context of an effort to design a game-based training modality to train combat medics and will close with a review of compensating strategies identified by the designers. The paper will provide information important to anyone interested in conceptualizing and designing game-based training.

Jones, Phillip N.↗
NASA NTRS2012

Elements of Engineering Excellence

The inspiration for this Contract Report (CR) originated in discussions with the director of Marshall Space Flight Center (MSFC) Engineering who asked that we investigate the question: "How do you achieve excellence in aerospace engineering?" Engineering a space system is a complex activity. Avoiding its inherent potential pitfalls and achieving a successful product is a challenge. This CR presents one approach to answering the question of how to achieve Engineering Excellence. We first investigated the root causes of NASA major failures as a basis for developing a proposed answer to the question of Excellence. The following discussions integrate a triad of Technical Understanding and Execution, Partnership with the Project, and Individual and Organizational Culture. The thesis is that you must focus on the whole process and its underlying culture, not just on the technical aspects. In addition to the engineering process, emphasis is given to the need and characteristics of a Learning Organization as a mechanism for changing the culture.

Blair, J. C.↗
NASA NTRSDate not supplied

NASA Earth Systems Digital Twins (ESDT)

"Similarly to artificial intelligence, which is now revolutionizing many aspects of our daily lives, Earth system digital twin technologies have the potential to revolutionize the way Earth Science research will be conducted in the future, and how results and knowledge from this research will provide information to support decision making and yield impactful societal benefits. An Earth System Digital Twin or ESDT is a dynamic and interactive information system that first provides a digital replica of the past and current states of the Earth or Earth system as accurately and timely as possible; second, allows for computing forecasts of future states under nominal assumptions and based on the current replica; and third, offers the capability to investigate many hypothetical scenarios under varying impact assumptions. In other words, an ESDT provides the integrated What-Now, What-Next, and What-If pictures of the Earth or Earth system, by continuously ingesting newly observed data and by leveraging multiple interconnected models, machine learning as well advanced computing and visualization capabilities. Digital twins have been developed in engineering since 2002, but the interest in digital twins for the Earth domain is more recent and stems from the convergence of several developments: - The huge amount of diverse data that has now been collected continuously for more than 50 years, and that is becoming more and more difficult to access, understand, and utilize. - At the same time, because of climate change and its impacts the information produced by all of this data is becoming of interest to many new non-traditional users for analyzing and predicting various phenomena. - Because of advances in computational and visualization capabilities and the parallel unprecedented development of machine learning (ML), extracting relevant information from these large amounts of data and running complex models faster has become possible. As a result, it is becoming necessary and possible to build intuitive and interactive frameworks that will enable users with various skill levels and/or organizational hierarchy levels to easily access large amounts of targeted information along with the relevant tools and models (Earth system and human activity models), to support them in analyzing and visualizing this information, to help them understand interactions among models, to visualize the potential outcomes of various impacts, and to support decision or policy making. The full power of digital twins is that, through an integrated representation and standardized tools and software technologies, the same digital replica can address the needs of multiple users at various resolutions (spatial and temporal) and for various applications (science, economic, policy, etc.) – “from farmer to scientist”. With all these interests at stake, the challenges of building optimal digital twins are many and complex. The first challenge is to determine if a Digital Twin should be global or local, and multi-domain or thematic. For example, some domains such as Climate or Weather will require a global Digital Twin or Digital Twin capabilities while science areas such as Biodiversity might be more local. We can also envision that multiple thematic ESDTs, e.g., Air Quality, Wildfires, Hydrology could be federated or provide input to other ESDTs, either on a regional level or to a more global ESDT. Overall, we can imagine a future “web” of Digital Twins co-existing in a hierarchy or in a network, and capable of being connected or federated depending on the needs. This last point brings up the very important challenge of interoperability, including standards and protocols that will need to be built into these systems from the beginning. Each individual digital twin would have full flexibility in internal construction but would need standards-based interfaces (input and output) or hooks to make it compatible with others. Another challenge when building digital twins will be to decide how to organize each digital replica. Based on the applications targeted by the DT under implementation, various amounts and types of raw data, Analysis Ready Data (ARD) and information will need to be incorporated. Depending on the required latencies and needs of the users, various solutions can be considered, including Data Cubes, Data Lakes, pointers, or computing information on demand. We envision that each ESDT will choose a solution adapted to its specific objectives. Another important challenge is the type(s) of visualization that will be used, as well as the level of interactivity and refresh rate that will be required. Again, this will depend on the objectives of the ESDT, but also on the various users’ needs. In most cases, several types of visualizations and human interfaces will need to be offered depending on the projected users of that system. In parallel to the challenges highlighted above, there are also many tools and technologies that will need to be developed or improved for all types of digital twins. Among those are improved machine learning technologies, for example providing explainability, but also ML techniques for causality and providing a better integration of physics models. Additionally, reliable uncertainty quantification methods will be needed for all ESDT components, from validating data fusion and assimilation to assessing the accuracy of ML models and weighing the values of decisions supported by those systems. This presentation introduces the ESDT concept, presents several ESDT use cases, and a proposed ESDT architecture framework, as well as various technologies being developed by the Advanced Information Systems Technology (AIST) Program."

Earth Science Remote Sensing; Information Systems↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Journey to Developing a Concept of Operations

Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.

Jeffrey Robert Cohen↗
NASA NTRS2004

A Multiagent Modeling Environment for Simulating Work Practice in Organizations

In this paper we position Brahms as a tool for simulating organizational processes. Brahms is a modeling and simulation environment for analyzing human work practice, and for using such models to develop intelligent software agents to support the work practice in organizations. Brahms is the result of more than ten years of research at the Institute for Research on Learning (IRL), NYNEX Science & Technology (the former R&D institute of the Baby Bell telephone company in New York, now Verizon), and for the last six years at NASA Ames Research Center, in the Work Systems Design and Evaluation group, part of the Computational Sciences Division (Code IC). Brahms has been used on more than ten modeling and simulation research projects, and recently has been used as a distributed multiagent development environment for developing work practice support tools for human in-situ science exploration on planetary surfaces, in particular a human mission to Mars. Brahms was originally conceived of as a business process modeling and simulation tool that incorporates the social systems of work, by illuminating how formal process flow descriptions relate to people s actual located activities in the workplace. Our research started in the early nineties as a reaction to experiences with work process modeling and simulation . Although an effective tool for convincing management of the potential cost-savings of the newly designed work processes, the modeling and simulation environment was only able to describe work as a normative workflow. However, the social systems, uncovered in work practices studied by the design team played a significant role in how work actually got done-actual lived work. Multi- tasking, informal assistance and circumstantial work interactions could not easily be represented in a tool with a strict workflow modeling paradigm. In response, we began to develop a tool that would have the benefits of work process modeling and simulation, but be distinctively able to represent the relations of people, locations, systems, artifacts, communication and information content.

Sierhuis, Maarten↗
NASA NTRS2004

Spitzer Space Telescope in-orbit checkout and science verification operations

Spitzer Space Telescope, the fourth and final of NASA's great observatories, and the first mission in NASA's Origins Program was launched 25 August 2003 into an Earth-trailing solar orbit. The observatory was designed to probe and explore the universe in the infrared. Before science data could be acquired, however, the observatory had to be initialized, characterized, calibrated, and commissioned. A two phased operations approach was defined to complete this work. These phases were identified as In-Orbit Checkout (IOC) and Science Verification (SV). Because the observatory lifetime is cryogen-limited these operations had to be highly efficient. The IOC/SV operations design accommodated a pre-defined distributed organizational structure and a complex, cryogenic flight system. Many checkout activities were inter-dependent, and therefore the operations concept and ground data system had to provide the flexibility required for a 'short turn-around' environment. This paper describes the adaptive operations system design and evolution, implementation, and lessons-learned from the completion of IOC/SV.

space verification↗
NASA NTRS2012

Space Environments and Spacecraft Effects Concept: Transitioning Research to Operations and Applications

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while expanding its mission to explore the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. NASA has established numerous organizations specializing in specific space environments disciplines that will serve to enable these missions. To complement these existing discipline organizations, a concept is presented focusing on the development of a space environment and spacecraft effects organization. This includes space climate, space weather, natural and induced space environments, and effects on spacecraft materials and systems. This space environment and spacecraft effects organization would be comprised of Technical Working Groups (TWG) focusing on, for example: a) Charged Particles (CP), b) Space Environmental Effects (SEE), and c) Interplanetary and Extraterrestrial Environments (IEE). These technical working groups will generate products and provide knowledge supporting four functional areas: design environments, environment effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Environment effects focuses on the material, component, sub-system and system-level selection and the testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather observations to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA and other federal agencies to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lesson learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support the mission phases of mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and spacecraft effects organization are suitable for use in anomaly investigations. This paper will describe the organizational structure for this space environments and spacecraft effects organization, and outline the scope of conceptual TWG's and their relationship to the functional areas.

Edwards, D. L.↗
NASA NTRS1996

Software Engineering Program: Software Process Improvement Guidebook

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Source record↗
NASA NTRS2009

Turning Operational Lessons Learned into Design Reality

The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.

Brady, David A.↗
NASA NTRSDate not supplied

Safety Culture at the World’s Premier Multi-User Spaceport

NASA’s Agency-wide Safety Culture is implemented at the Kennedy Space Center (KSC) using a unique strategy due an unparalleled approach in making human spaceflight history. Kennedy Space Center, the world’s premier multi-user spaceport, enables U.S. government and commercial space access, while providing the world a resource to allow the exploration of and the ability to work in space. A consistently healthy safety culture at KSC is imperative for mission success: desired achievements, protection of space flight hardware, and ultimately, the preservation of human life requires the support of a healthy safety culture. Emphasis on the NASA Agency-wide development of Safety Culture began with the conception of the NASA Agency Safety Culture Working Group. After the devastating loss of life and mission of the Space Shuttle Colombia, a broken safety culture was identified as an organizational cause by the Columbia Accident Investigation Board Report. Thus, the Agency Safety Culture Working Group was developed in 2009 to assess the status of the Agency’s Safety Culture, while addressing safety culture concerns at the NASA Center-level. A Five-factor model was developed to serve as the guiding principles for Safety Culture: 1) Reporting Culture, 2) Just Culture, 3) Flexible Culture, 4) Learning Culture, and 5) Engaged Culture. These five factors are included in the NASA Safety Culture logo, which was intentionally designed as a DNA double helix to prompt the permeation of safety into day-to-day work. KSC specifically implements the NASA Agency-wide Safety Culture principles in a tailored approach that is relevant to the diversity of work being performed. An emphasis is placed on the implementation to include safety at home, not exclusively at work. This emphasis is a KSC-specific element that has been intentionally added to promote a closed loop Safety Culture. To advertise the safety culture, various safety and health events are held throughout the calendar year, providing innovative speakers and engaging activities, while also promoting a wide range of curated safety initiatives. Development and continuous improvement of the KSC safety tracking database, allows for advanced tracking-to-closure, along with providing data sets used to identify areas of emphasis. Other safety initiatives rely solely on employee participation, such as the photo challenges; participants are encouraged to identify and capture themselves, coworkers, or family members participating in safe or healthy activities to share with others within the Center and at Agency levels. Fabrication of exclusive videos and graphics are utilized to advertise and inform employee of safety initiatives, upcoming safety events, and general dispersion of safety information. In addition, an anonymous Agency-wide Safety Culture Survey is advertised, administered, and analyzed at Kennedy Space Center, with the purpose of receiving basic feedback on Safety Culture perceptions to help prevent future incidents from occurring. Through these briefly identified means, and many other forms of employee engagement, Kennedy Space Center aims to maintain safety in the forefront, while creating an environment where everyone trusts that safety is a priority.

Larrin E. Moody↗
NASA NTRS2001

Developing Distributed Collaboration Systems at NASA: A Report from the Field

Web-based collaborative systems have assumed a pivotal role in the information systems development arena. While business to customers (B-to-C) and business to business (B-to-B) electronic commerce systems, search engines, and chat sites are the focus of attention, web-based systems span the gamut of information systems that were traditionally confined to internal organizational client server networks. For example, the Domino Application Server allows Lotus Notes (trademarked) uses to build collaborative intranet applications and mySAP.com (trademarked) enables web portals and e-commerce applications for SAP users. This paper presents the experiences in the development of one such system: Postdoc, a government off-the-shelf web-based collaborative environment. Issues related to the design of web-based collaborative information systems, including lessons learned from the development and deployment of the system as well as measured performance, are presented in this paper. Finally, the limitations of the implementation approach as well as future plans are presented as well.

Becerra-Fernandez, Irma↗
NASA NTRS2012

Space Environments and Spacecraft Effects Organization Concept

The National Aeronautics and Space Administration (NASA) is embarking on a course to expand human presence beyond Low Earth Orbit (LEO) while also expanding its mission to explore the solar system. Destinations such as Near Earth Asteroids (NEA), Mars and its moons, and the outer planets are but a few of the mission targets. Each new destination presents an opportunity to increase our knowledge of the solar system and the unique environments for each mission target. NASA has multiple technical and science discipline areas specializing in specific space environments disciplines that will help serve to enable these missions. To complement these existing discipline areas, a concept is presented focusing on the development of a space environments and spacecraft effects (SENSE) organization. This SENSE organization includes disciplines such as space climate, space weather, natural and induced space environments, effects on spacecraft materials and systems and the transition of research information into application. This space environment and spacecraft effects organization will be composed of Technical Working Groups (TWG). These technical working groups will survey customers and users, generate products, and provide knowledge supporting four functional areas: design environments, engineering effects, operational support, and programmatic support. The four functional areas align with phases in the program mission lifecycle and are briefly described below. Design environments are used primarily in the mission concept and design phases of a program. Engineering effects focuses on the material, component, sub-system and system-level selection and the testing to verify design and operational performance. Operational support provides products based on real time or near real time space weather to mission operators to aid in real time and near-term decision-making. The programmatic support function maintains an interface with the numerous programs within NASA, other federal government agencies, and the commercial sector to ensure that communications are well established and the needs of the programs are being met. The programmatic support function also includes working in coordination with the program in anomaly resolution and generation of lessons learned documentation. The goal of this space environment and spacecraft effects organization is to develop decision-making tools and engineering products to support all mission phases from mission concept through operations by focusing on transitioning research to application. Products generated by this space environments and effects application are suitable for use in anomaly investigations. This paper will describe the scope of the TWGs and their relationship to the functional areas, and discuss an organizational structure for this space environments and spacecraft effects organization.

Edwards, David L.↗