Search NASA⌕ Search

SEARCH · Search NASA

Results for “Practitioner”

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 937 records · Page 52

Development of Human System Integration at NASA

Human Systems Integration seeks to design systems around the capabilities and limitations of the humans which use and interact with the system, ensuring greater efficiency of use, reduced error rates, and less rework in the design, manufacturing and operational deployment of hardware and software. One of the primary goals of HSI is to get the human factors practitioner involved early in the design process. In doing so, the aim is to reduce future budget costs and resources in redesign and training. By the preliminary design phase of a project nearly 80% of the total cost of the project is locked in. Potential design changes recommended by evaluations past this point will have little effect due to lack of funding or a huge cost in terms of resources to make changes. Three key concepts define an effective HSI program. First, systems are comprised of hardware, software, and the human, all of which operate within an environment. Too often, engineers and developers fail to consider the human capacity or requirements as part of the system. This leads to poor task allocation within the system. To promote ideal task allocation, it is critical that the human element be considered early in system development. Poor design, or designs that do not adequately consider the human component, could negatively affect physical or mental performance, as well as, social behavior. Second, successful HSI depends upon integration and collaboration of all the domains that represent acquisition efforts. Too often, these domains exist as independent disciplines due to the location of expertise within the service structure. Proper implementation of HSI through participation would help to integrate these domains and disciplines to leverage and apply their interdependencies to attain an optimal design. Via this process domain interests can be integrated to perform effective HSI through trade-offs and collaboration. This provides a common basis upon which to make knowledgeable decisions. Finally, HSI must be considered early in the requirements development phase of system design and acquisition. This will provide the best opportunity to maximize return on investment (ROI) and system performance. HSI requirements must be developed in conjunction with capability ]based requirements generation through functional. HSI requirements will drive HSI metrics and embed HSI issues within the system design. After a system is designed, implementation of HSI oversights can be very expensive. An HSI program should be included as an integral part of a total system approach to vehicle and habitat development. This would include, but not limited to, workstation design, D&C development, volumetric analysis, training, operations, and human -robotic interaction. HSI is a necessary process for Human Space Flight programs to meet the Agency Human ]System standards and thus mitigate human risks to acceptable levels. NASA has been involved in HSI planning, procedures development, process, and implementation for many years, and has been building several internal and publicly accessible products to facilitate HSI fs inclusion in the NASA Systems Engineering Lifecycle. Some of these products include: NASA STD 3001 Volumes 1 and 2, Human Integration Design Handbook, NASA HSI Implementation Plan, NASA HSI Implementation Plan Templates, NASA HSI Implementation Handbook, and a 2 ]hour short course on HSI delivered as part of the NASA Space and Life Sciences Directorate Academy. These products have been created leveraging industry best practices and lessons learned from other Federal Government agencies.

Whitmore, Mihriban↗

Cognitive Systems Modeling and Analysis of Command and Control Systems

Military operations, counter-terrorism operations and emergency response often oblige operators and commanders to operate within distributed organizations and systems for safe and effective mission accomplishment. Tactical commanders and operators frequently encounter violent threats and critical demands on cognitive capacity and reaction time. In the future they will make decisions in situations where operational and system characteristics are highly dynamic and non-linear, i.e. minor events, decisions or actions may have serious and irreversible consequences for the entire mission. Commanders and other decision makers must manage true real time properties at all levels; individual operators, stand-alone technical systems, higher-order integrated human-machine systems and joint operations forces alike. Coping with these conditions in performance assessment, system development and operational testing is a challenge for both practitioners and researchers. This paper reports on research from which the results led to a breakthrough: An integrated approach to information-centered systems analysis to support future command and control systems research development. This approach integrates several areas of research into a coherent framework, Action Control Theory (ACT). It comprises measurement techniques and methodological advances that facilitate a more accurate and deeper understanding of the operational environment, its agents, actors and effectors, generating new and updated models. This in turn generates theoretical advances. Some good examples of successful approaches are found in the research areas of cognitive systems engineering, systems theory, and psychophysiology, and in the fields of dynamic, distributed decision making and naturalistic decision making.

Norlander, Arne↗

Exploring the Use of Computer Simulations in Unraveling Research and Development Governance Problems

Understanding Research and Development (R&D) enterprise relationships and processes at a governance level is not a simple task, but valuable decision-making insight and evaluation capabilities can be gained from their exploration through computer simulations. This paper discusses current Modeling and Simulation (M&S) methods, addressing their applicability to R&D enterprise governance. Specifically, the authors analyze advantages and disadvantages of the four methodologies used most often by M&S practitioners: System Dynamics (SO), Discrete Event Simulation (DES), Agent Based Modeling (ABM), and formal Analytic Methods (AM) for modeling systems at the governance level. Moreover, the paper describes nesting models using a multi-method approach. Guidance is provided to those seeking to employ modeling techniques in an R&D enterprise for the purposes of understanding enterprise governance. Further, an example is modeled and explored for potential insight. The paper concludes with recommendations regarding opportunities for concentration of future work in modeling and simulating R&D governance relationships and processes.

Balaban, Mariusz A.↗

Proceedings of the 2011 Space Cryogenics Workshop: "Poised for the Future, Reflecting on the Past"

The 24th Space Cryogenics Workshop was held at the Best Western Coeur d Alene Inn and Conference Center, Coeur d Alene, Idaho, June 8-10, 2011. The workshop was organized and sponsored by NASA Kennedy Space Center and NASA Marshall Space Flight Center, with a theme of "Poised for the Future, Reflecting on the Past." Over 100 scientists and engineers from around the world came together to discuss space applications for cryogenics, renew old acquaintances, and meet new practitioners in the field of space cryogenics.

Johnson, W. L.↗

Biomechanics of the Treadmill Locomotion on the International Space Station

Exercise prescriptions completed by International Space Station (ISS) crewmembers are typically based upon evidence obtained during ground-based investigations, with the assumption that the results of long-term training in weightlessness will be similar to that attained in normal gravity. Coupled with this supposition are the assumptions that exercise motions and external loading are also similar between gravitational environments. Normal control of locomotion is dependent upon learning patterns of muscular activation and requires continual monitoring of internal and external sensory input [1]. Internal sensory input includes signals that may be dependent on or independent of gravity. Bernstein hypothesized that movement strategy planning and execution must include the consideration of segmental weights and inertia [2]. Studies of arm movements in microgravity showed that individuals tend to make errors but that compensation strategies result in adaptations, suggesting that control mechanisms must include peripheral information [3-5]. To date, however, there have been no studies examining a gross motor activity such as running in weightlessness other than using microgravity analogs [6-8]. The objective of this evaluation was to collect biomechanical data from crewmembers during treadmill exercise before and during flight. The goal was to determine locomotive biomechanics similarities and differences between normal and weightless environments. The data will be used to optimize future exercise prescriptions. This project addresses the Critical Path Roadmap risks 1 (Accelerated Bone Loss and Fracture Risk) and 11 (Reduced Muscle Mass, Strength, and Endurance). Data were collected from 7 crewmembers before flight and during their ISS missions. Before launch, crewmembers performed a single data collection session at the NASA Johnson Space Center. Three-dimensional motion capture data were collected for 30 s at speeds ranging from 1.5 to 9.5 mph in 0.5 mph increments with a 12-camera system. During flight, each crewmember completed up to 6 data collection sessions spread across their missions, performing their normal exercise prescription for the test day, resulting in varying data collection protocols between sessions. Motion data were collected by a single HD video camera positioned to view the crewmembers' left side, and tape markers were placed on their feet, legs, and neck on specific landmarks. Before data collection, the crewmembers calibrated the video camera. Video data were collected during the entire exercise session at 30 Hz. Kinematic data were used to determine left leg hip, knee, and ankle range of motion and contact time, flight time, and stride time for each stride. 129 trials in weightlessness were analyzed. Mean time-normalized strides were found for each trial, and cross-correlation procedures were used to examine the strength and direction of relationships between segment movement pattern timing in each gravitational condition. Cross-correlation analyses between gravitational conditions revealed highly consistent movement patterns at each joint. Peak correlation coefficients occurred at 0% phase, indicating there were no lags in movement timing. Joint ranges of motion were similar between gravitational conditions, with some slight differences between subjects. Motion patterns in weightlessness were highly consistent at a given speed with those occurring in 1G, indicating that despite differing sensory input, subjects maintain running kinematics. The data suggest that individuals are capable of compensating for loss of limb weight when creating movement strategies. These results have important implications for creating training programs for use in weightlessness as practitioners can have greater confidence in running motions transferring across gravitational environments. Furthermore, these results have implications for use by researchers investigating motor control mechanisms and investigating hypotheses related to movement strategies when using sensory input that is dependent upon gravity.

DeWitt, John↗

Interdisciplinary Interactions During R&D and Early Design of Large Engineered Systems

Designing Large-Scale Complex Engineered Systems (LaCES) such as aircraft and submarines requires the input of thousands of engineers and scientists whose work is proximate in neither time nor space. Comprehensive knowledge of the system is dispersed among specialists whose expertise is in typically one system component or discipline. This study examined the interactive work practices among such specialists seeking to improve engineering practice through a rigorous and theoretical understanding of current practice. This research explored current interdisciplinary practices and perspectives during R&D and early LaCES design and identified why these practices and perspectives prevail and persist. The research design consisted of a three-fold, integrative approach that combined an open-ended survey, semi-structured interviews, and ethnography. Significant empirical data from experienced engineers and scientists in a large engineering organization were obtained and integrated with theories from organization science and engineering. Qualitative analysis was used to obtain a holistic, contextualized understanding. 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. For example, organization culture is an important underlying factor that guided researchers more toward individual sovereignty over cross-disciplinarity. The organization structure and the engineered system architecture also serve as constraints to the engineering work. Many differences in work practices were observed, including frequency and depth of interactions, definition or co-construction of requirements, clarity or creation of the system architecture, work group proximity, and cognitive challenges. Practitioners are often unaware of these differences resulting in confusion and incorrect assumptions regarding work expectations. Cognitively, the enactment and coconstruction of knowledge are the fundamental tasks of the interdisciplinary interactions. Distributed and collective cognition represent most of the efforts. Argument, ignorance, learning, and creativity are interrelated aspects of the interactions that cause discomfort but yield benefits such as problem mitigation, broader understanding, and improved system design and performance. The quality and quantity of social interrelations are central to all work across disciplines with reciprocity, respectful engagement, and heedful interrelations being significant to the effectiveness of the engineering and scientific work.

McGowan, Anna-Maria Rivas↗

Using Generic Data to Establish Dormancy Failure Rates

Many hardware items are dormant prior to being operated. The dormant period might be especially long, for example during missions to the moon or Mars. In missions with long dormant periods the risk incurred during dormancy can exceed the active risk contribution. Probabilistic Risk Assessments (PRAs) need to account for the dormant risk contribution as well as the active contribution. A typical method for calculating a dormant failure rate is to multiply the active failure rate by a constant, the dormancy factor. For example, some practitioners use a heuristic and divide the active failure rate by 30 to obtain an estimate of the dormant failure rate. To obtain a more empirical estimate of the dormancy factor, this paper uses the recently updated database NPRD-2011 [1] to arrive at a set of distributions for the dormancy factor. The resulting dormancy factor distributions are significantly different depending on whether the item is electrical, mechanical, or electro-mechanical. Additionally, this paper will show that using a heuristic constant fails to capture the uncertainty of the possible dormancy factors.

Reistle, Bruce↗

Developing IVHM Requirements for Aerospace Systems

The term Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable sustainable and safe operation of components and subsystems within aerospace platforms. However, very little guidance exists for the systems engineering aspects of design with IVHM in mind. It is probably because of this that designers have to use knowledge picked up exclusively by experience rather than by established process. This motivated a group of leading IVHM practitioners within the aerospace industry under the aegis of SAE's HM-1 technical committee to author a document that hopes to give working engineers and program managers clear guidance on all the elements of IVHM that they need to consider before designing a system. This proposed recommended practice (ARP6883 [1]) will describe all the steps of requirements generation and management as it applies to IVHM systems, and demonstrate these with a "real-world" example related to designing a landing gear system. The team hopes that this paper and presentation will help start a dialog with the larger aerospace community and that the feedback can be used to improve the ARP and subsequently the practice of IVHM from a systems engineering point-of-view.

IVHM↗

The Federation of Earth Science Information Partners ESIP

A broad-based, distributed community of science, data and information technology practitioners. With over 150 member organizations, the ESIP Federation brings together public, academic, commercial, and nongovernmental organizations to share knowledge, expertise, technology and best practices to improve opportunities for increasing access, discovery, integration and usability of Earth science data.

ESIP↗

Test Driven Development of Scientific Models

Test-Driven Development (TDD), a software development process that promises many advantages for developer productivity and software reliability, has become widely accepted among professional software engineers. As the name suggests, TDD practitioners alternate between writing short automated tests and producing code that passes those tests. Although this overly simplified description will undoubtedly sound prohibitively burdensome to many uninitiated developers, the advent of powerful unit-testing frameworks greatly reduces the effort required to produce and routinely execute suites of tests. By testimony, many developers find TDD to be addicting after only a few days of exposure, and find it unthinkable to return to previous practices.After a brief overview of the TDD process and my experience in applying the methodology for development activities at Goddard, I will delve more deeply into some of the challenges that are posed by numerical and scientific software as well as tools and implementation approaches that should address those challenges.

Overview of TDD Process↗

Space Architecture: The Role, Work and Aptitude

Space architecture has been an emerging discipline for at least 40 years. Has it arrived? Is space architecture a legitimate vocation or an avocation? If it leads to a job, what do employers want? In 2002, NASA Headquarters created a management position for a space architect whose job was to "lead the development of strategic architectures and identify high level requirements for systems that will accomplish the Nation's space exploration vision." This is a good job description with responsibility at the right level in NASA, but unfortunately, the office was discontinued two years later. Even though there is no accredited academic program or professional licensing for space architecture, there is a community of practitioners. They are civil servants, contractors and academicians supporting International Space Station and space exploration programs. In various ways, space architects currently contribute to human spaceflight, but there is a way for the discipline to be more effective in developing solutions to large scale complex problems. This paper organizes contributions from engineers, architects and psychologists into recommendations on the role of space architects in the organization, the process of creating and selecting options, and intrinsic personality traits including why they must have a high tolerance for ambiguity.

Griffin, Brand↗

Mobilization Protocols for Hybrid Sensors for Environmental AOP Sampling (HySEAS) Observations

The protocols presented here enable the proper mobilization of the latest-generation instruments for measuring the apparent optical properties (AOPs) of aquatic ecosystems. The protocols are designed for the Hybrid Sensors for Environmental AOP Sampling (HySEAS) class of instruments, but are applicable to the community of practice for AOP measurements. The protocols are organized into eleven sections beyond an introductory overview: a) cables and connectors, b) HySEAS instruments, c) platform preparation, d) instrument installation, e) cable installation, f) test deployment, g) test recovery, h) maintenance, i) shipping, j) storage, and k) smallboat operations. Each section concentrates on documenting how to prevent the most likely faults, remedy them should they occur, and accomplishing both with the proper application of a modest set of useful tools. Within the twelve sections, there are Socratic exercises to stimulate thought, and the answers to these exercises appear in Appendix A. Frequently asked questions (FAQs) are summarized in a separate section after the answers to the exercises in Appendix B. For practitioners unfamiliar with the nautical terms used throughout this document plus others likely encountered at sea, an abbreviated dictionary of nautical terms appears in Appendix C. An abbreviated dictionary of radiotelephone terms is presented in Appendix D. To ensure familiarity with many of the tools that are presented, Appendix E provides a description of the tools alongside a thumbnail picture. Abbreviated deployment checklists and cable diagrams are provided in Appendix F. The document concludes with an acknowledgments section, a glossary of acronyms, a definition of symbols, and a list of references.

Mobilizarion↗

Constructing the 'Best' Reliability Data for the Job - Developing Generic Reliability Data from Alternative Sources Early in a Product's Development Phase

Reliability practitioners advocate getting reliability involved early in a product development process. However, when assigned to estimate or assess the (potential) reliability of a product or system early in the design and development phase, they are faced with lack of reasonable models or methods for useful reliability estimation. Developing specific data is costly and time consuming. Instead, analysts rely on available data to assess reliability. Finding data relevant to the specific use and environment for any project is difficult, if not impossible. Instead, analysts attempt to develop the "best" or composite analog data to support the assessments. Industries, consortia and vendors across many areas have spent decades collecting, analyzing and tabulating fielded item and component reliability performance in terms of observed failures and operational use. This data resource provides a huge compendium of information for potential use, but can also be compartmented by industry, difficult to find out about, access, or manipulate. One method used incorporates processes for reviewing these existing data sources and identifying the available information based on similar equipment, then using that generic data to derive an analog composite. Dissimilarities in equipment descriptions, environment of intended use, quality and even failure modes impact the "best" data incorporated in an analog composite. Once developed, this composite analog data provides a "better" representation of the reliability of the equipment or component. It can be used to support early risk or reliability trade studies, or analytical models to establish the predicted reliability data points. It also establishes a baseline prior that may updated based on test data or observed operational constraints and failures, i.e., using Bayesian techniques. This tutorial presents a descriptive compilation of historical data sources across numerous industries and disciplines, along with examples of contents and data characteristics. It then presents methods for combining failure information from different sources and mathematical use of this data in early reliability estimation and analyses.

Kleinhammer, Roger K.↗

A Comparison and Evaluation of Real-Time Software Systems Modeling Languages

A model-driven approach to real-time software systems development enables the conceptualization of software, fostering a more thorough understanding of its often complex architecture and behavior while promoting the documentation and analysis of concerns common to real-time embedded systems such as scheduling, resource allocation, and performance. Several modeling languages have been developed to assist in the model-driven software engineering effort for real-time systems, and these languages are beginning to gain traction with practitioners throughout the aerospace industry. This paper presents a survey of several real-time software system modeling languages, namely the Architectural Analysis and Design Language (AADL), the Unified Modeling Language (UML), Systems Modeling Language (SysML), the Modeling and Analysis of Real-Time Embedded Systems (MARTE) UML profile, and the AADL for UML profile. Each language has its advantages and disadvantages, and in order to adequately describe a real-time software system's architecture, a complementary use of multiple languages is almost certainly necessary. This paper aims to explore these languages in the context of understanding the value each brings to the model-driven software engineering effort and to determine if it is feasible and practical to combine aspects of the various modeling languages to achieve more complete coverage in architectural descriptions. To this end, each language is evaluated with respect to a set of criteria such as scope, formalisms, and architectural coverage. An example is used to help illustrate the capabilities of the various languages.

Evensen, Kenneth D.↗

Fault Management Practice: A Roadmap for Improvement

Autonomous fault management (FM) is critical for deep space and planetary missions where the limited communication opportunities may prevent timely intervention by ground control. Evidence of pervasive architecture, design, and verification/validation problems with NASA FM engineering has been revealed both during technical reviews of spaceflight missions and in flight. These problems include FM design changes required late in the life-cycle, insufficient project insight into the extent of FM testing required, unexpected test results that require resolution, spacecraft operational limitations because certain functions were not tested, and in-flight anomalies and mission failures attributable to fault management. A recent NASA initiative has characterized the FM state-of-practice throughout the spacecraft development community and identified common NASA, DoD, and commercial concerns that can be addressed in the near term through the development of a FM Practitioner's Handbook and the formation of a FM Working Group. Initial efforts will focus on standardizing FM terminology, establishing engineering processes and tools, and training.

Fesq, Lorraine M.↗

Enabling Innovation and Collaboration Across Geography and Culture: A Case Study of NASA's Systems Engineering Community of Practice

In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited personnel from sharing experiences and ideas. Mission failures and new directions for the agency demanded better collaborative tools. In addition, with the push to send astronauts back to the moon and to Mars, NASA recognized that systems engineering would have to improve across the agency. Of the ten field centers, seven had not built a spacecraft in over 30 years, and had lost systems engineering expertise. The Systems Engineering Community of Practice came together to capture the knowledge of its members using the suite of collaborative tools provided by the NASA Engineering Network (NEN.) The NEN provided a secure collaboration space for over 60 practitioners across the agency to assemble and review a NASA systems engineering handbook. Once the handbook was complete, they used the open community area to disseminate it. This case study explores both the technology and the social networking that made the community possible, describes technological approaches that facilitated rapid setup and low maintenance, provides best practices that other organizations could adopt, and discusses the vision for how this community will continue to collaborate across the field centers to benefit the agency as it continues exploring the solar system.

NEN↗

Developing the Next Generation of Science Data System Engineers

At Goddard, engineers and scientists with a range of experience in science data systems are needed to employ new technologies and develop advances in capabilities for supporting new Earth and Space science research. Engineers with extensive experience in science data, software engineering and computer-information architectures are needed to lead and perform these activities. The increasing types and complexity of instrument data and emerging computer technologies coupled with the current shortage of computer engineers with backgrounds in science has led the need to develop a career path for science data systems engineers and architects.The current career path, in which undergraduate students studying various disciplines such as Computer Engineering or Physical Scientist, generally begins with serving on a development team in any of the disciplines where they can work in depth on existing Goddard data systems or serve with a specific NASA science team. There they begin to understand the data, infuse technologies, and begin to know the architectures of science data systems. From here the typical career involves peermentoring, on-the-job training or graduate level studies in analytics, computational science and applied science and mathematics. At the most senior level, engineers become subject matter experts and system architect experts, leading discipline-specific data centers and large software development projects. They are recognized as a subject matter expert in a science domain, they have project management expertise, lead standards efforts and lead international projects. A long career development remains necessary not only because of the breadth of knowledge required across physical sciences and engineering disciplines, but also because of the diversity of instrument data being developed today both by NASA and international partner agencies and because multidiscipline science and practitioner communities expect to have access to all types of observational data.This paper describes an approach to defining career-path guidance for college-bound high school and undergraduate engineering students, junior and senior engineers from various disciplines.

Next Generation of Science↗

Meningitis and Climate: From Science to Practice

Meningococcal meningitis is a climate sensitive infectious disease. The regional extent of the Meningitis Belt in Africa, where the majority of epidemics occur, was originally defined by Lapeysonnie in the 1960s. A combination of climatic and environmental conditions and biological and social factors have been associated to the spatial and temporal patterns of epidemics observed since the disease first emerged in West Africa over a century ago. However, there is still a lack of knowledge and data that would allow disentangling the relative effects of the diverse risk factors upon epidemics. The Meningitis Environmental Risk Information Technologies Initiative (MERIT), a collaborative research-to-practice consortium, seeks to inform national and regional prevention and control strategies across the African Meningitis Belt through the provision of new data and tools that better determine risk factors. In particular MERIT seeks to consolidate a body of knowledge that provides evidence of the contribution of climatic and environmental factors to seasonal and year-to-year variations in meningococcal meningitis incidence at both district and national scales. Here we review recent research and practice seeking to provide useful information for the epidemic response strategy of National Ministries of Health in the Meningitis Belt of Africa. In particular the research and derived tools described in this paper have focused at "getting science into policy and practice" by engaging with practitioner communities under the umbrella of MERIT to ensure the relevance of their work to operational decision-making. We limit our focus to that of reactive vaccination for meningococcal meningitis. Important but external to our discussion is the development and implementation of the new conjugate vaccine, which specifically targets meningococcus A

Mineral dust↗