Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 955 records · Page 53

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↗

Modeling a Miniaturized Scanning Electron Microscope Focusing Column - Lessons Learned in Electron Optics Simulation

This presentation discusses work done to assess the design of a focusing column in a miniaturized Scanning Electron Microscope (SEM) developed at the NASA Marshall Space Flight Center (MSFC) for use in-situ on the Moon-in particular for mineralogical analysis. The MSFC beam column design uses purely electrostatic fields for focusing, because of the severe constraints on mass and electrical power consumption imposed by the goals of lunar exploration and of spaceflight in general. The resolution of an SEM ultimately depends on the size of the focused spot of the scanning beam probe, for which the stated goal here is a diameter of 10 nanometers. Optical aberrations are the main challenge to this performance goal, because they blur the ideal geometrical optical image of the electron source, effectively widening the ideal spot size of the beam probe. In the present work the optical aberrations of the mini SEM focusing column were assessed using direct tracing of non-paraxial rays, as opposed to mathematical estimates of aberrations based on paraxial ray-traces. The geometrical ray-tracing employed here is completely analogous to ray-tracing as conventionally understood in the realm of photon optics, with the major difference being that in electron optics the lens is simply a smoothly varying electric field in vacuum, formed by precisely machined electrodes. Ray-tracing in this context, therefore, relies upon a model of the electrostatic field inside the focusing column to provide the mathematical description of the "lens" being traced. This work relied fundamentally on the boundary element method (BEM) for this electric field model. In carrying out this research the authors discovered that higher accuracy in the field model was essential if aberrations were to be reliably assessed using direct ray-tracing. This led to some work in testing alternative techniques for modeling the electrostatic field. Ultimately, the necessary accuracy was attained using a BEM/Fourier series hybrid approach. The presentation will give background remarks about the MSFC mini Lunar SEM concept and electron optics modeling, followed by a description of the alternate field modeling techniques that were tried, along with their incorporation into a ray-trace simulation. Next, the validation of this simulation against commercially available software will be discussed using an example lens as a test case. Then, the efficacy of aberration assessment using direct ray-tracing will be demonstrated, using this same validation case. The discussion will include practical error checks of the field solution. Finally, the ray-trace assessment of the MSFC mini Lunar SEM concept will be shown and discussed. The authors believe this presentation will be of general interest to practitioners of modeling and simulation, as well as those with a general optics background. Because electron optics and photon optics share many basic concepts (e.g., lenses, images, aberrations, etc.), the appeal of this presentation need not be restricted to just those interested in charged particle optics.

Modeling Miniaturizing Scanning↗

Summary Report for the Technical Interchange Meeting on Development of Baseline Material Properties and Design Guidelines for In-Space Manufacturing Activities

NASA Marshall Space Flight Center (MSFC) and the Agency as a whole are currently engaged in a number of in-space manufacturing (ISM) activities that have the potential to reduce launch costs, enhance crew safety, and provide the capabilities needed to undertake long-duration spaceflight. The recent 3D Printing in Zero-G experiment conducted on board the International Space Station (ISS) demonstrated that parts of acrylonitrile butadiene styrene (ABS) plastic can be manufactured in microgravity using fused deposition modeling (FDM). This project represents the beginning of the development of a capability that is critical to future NASA missions. Current and future ISM activities will require the development of baseline material properties to facilitate design, analysis, and certification of materials manufactured using in-space techniques. The purpose of this technical interchange meeting (TIM) was to bring together MSFC practitioners and experts in materials characterization and development of baseline material properties for emerging technologies to advise the ISM team as we progress toward the development of material design values, standards, and acceptance criteria for materials manufactured in space. The overall objective of the TIM was to leverage MSFC's shared experiences and collective knowledge in advanced manufacturing and materials development to construct a path forward for the establishment of baseline material properties, standards development, and certification activities related to ISM. Participants were asked to help identify research and development activities that will (1) accelerate acceptance and adoption of ISM techniques among the aerospace design community; (2) benefit future NASA programs, commercial technology developments, and national needs; and (3) provide opportunities and avenues for further collaboration.

Prater, T. J.↗

Human Factors Checklist: Think Human Factors - Focus on the People

A quick-look Human Factors (HF) Checklist condenses industry and NASA Agency standards consisting of thousands of requirements into 14 main categories. With support from contractor HF and Safety Practitioners, NASA developed a means to share key HF messages with Design, Engineering, Safety, Project Management, and others. It is often difficult to complete timely assessments due to the large volume of HF information. The HF Checklist evolved over time into a simple way to consider the most important concepts. A wide audience can apply the checklist early in design or through planning phases, even before hardware or processes are finalized or implemented. The checklist is a good place to start to supplement formal HF evaluation. The HF Checklist was based on many Space Shuttle processing experiences and lessons learned. It is now being applied to ground processing of new space vehicles and adjusted for new facilities and systems.

Human Factors; Human Systems Integration↗

An Investigation of Proposed Techniques for Quantifying Confidence in Assurance Arguments

The use of safety cases in certification raises the question of assurance argument sufficiency and the issue of confidence (or uncertainty) in the argument's claims. Some researchers propose to model confidence quantitatively and to calculate confidence in argument conclusions. We know of little evidence to suggest that any proposed technique would deliver trustworthy results when implemented by system safety practitioners. Proponents do not usually assess the efficacy of their techniques through controlled experiment or historical study. Instead, they present an illustrative example where the calculation delivers a plausible result. In this paper, we review current proposals, claims made about them, and evidence advanced in favor of them. We then show that proposed techniques can deliver implausible results in some cases. We conclude that quantitative confidence techniques require further validation before they should be recommended as part of the basis for deciding whether an assurance argument justifies fielding a critical system.

Graydon, Patrick J.↗

SIG: Multiple Views on Safety-Critical Automation: Aircraft, Autonomous Vehicles, Air Traffic Management and Satellite Ground Segments Perspectives

This SIG focuses on the engineering of automation in interactive critical systems. Automation has already been studied in a number of (sub-) disciplines and application fields: design, human factors, psychology, (software) engineering, aviation, health care, games. One distinguishing feature of the area we are focusing on is that in the field of interactive critical systems properties such as reliability, dependability, fault tolerance are as important as usability, user experience or overall acceptance issues. The SIG targets at two problem areas: first the engineering of the user interaction with (partly-) autonomous systems: how to design, build and assess autonomous behavior, especially in cases where there is a need to represent on the user interface both autonomous and interactive objects. An example of such integration is the representation of an unmanned aerial vehicle (UAV) (where no direct interaction is possible), together with aircrafts (that have to be instructed by an air traffic controller to avoid the UAV). Second the design and engineering of user interaction in general for autonomous objects/systems (for example a cruise control in a car or an autopilot in an aircraft). The goal of the SIG is to raise interest in the CHI community on the general aspects of automation and to identify a community of researchers and practitioners interested in those increasingly prominent issues of interfaces towards (semi)-autonomous systems. The expected audience should be interested in addressing the issues of integration of mainly unconnected research domains to formulate a new joint research agenda.

human-automation interaction↗

HSI in NASA: From Research to Implementation

As NASA plans to send human explorers beyond low Earth orbit, onward to Mars and other destinations in the solar system, there will be new challenges to address in terms of HSI. These exploration missions will be quite different from the current and past missions such as Apollo, Shuttle, and International Space Station. The exploration crew will be more autonomous from ground mission control with delayed, and at times, no communication. They will have limited to no resupply for much longer mission durations. Systems to deliver and support extended human habitation at these destinations are extremely complex and unique, presenting new opportunities to employ HSI practices. In order to have an effective and affordable HSI implementation, both research and programmatic efforts are required. Currently, the HSI-related research at NASA is primarily in the area of space human factors and habitability. The purpose is to provide human health and performance countermeasures, knowledge, technologies, and tools to enable safe, reliable, and productive human space exploration beyond low Earth orbit, and update standards, requirements, and processes to verify and validate these requirements. In addition, HSI teams are actively engaged in technology development and demonstration efforts to influence the mission architecture and next-generation vehicle design. Finally, appropriate HSI references have been added to NASA' s systems engineering documentation, and an HSI Practitioner's Guide has been published to help design engineers consider HSI early and continuously in the acquisition process. These current and planned HSI-related activities at NASA will be discussed in this panel.

Whitmore, Mihriban↗

Wind Tunnel Balance Calibration: Are 1,000,000 Data Points Enough?

Measurement systems are typically calibrated based on standard practices established by a metrology standards laboratory, for example the National Institute for Standards and Technology (NIST), or dictated by an organization's metrology manual. Therefore, the calibration is designed and executed according to an established procedure. However, for many aerodynamic research measurement systems a universally accepted standard, traceable approach does not exist. Therefore, a strategy for how to develop a calibration protocol is left to the developer or user to define based on experience and recommended practice in their respective industry. Wind tunnel balances are one such measurement system. Many different calibration systems, load schedules and procedures have been developed for balances with little consensus on a recommended approach. Especially lacking is guidance the number of calibration data points needed. Regrettably, the number of data points tends to be correlated with the perceived quality of the calibration. Often, the number of data points is associated with ones ability to generate the data rather than by a defined need in support of measurement objectives. Hence the title of the paper was conceived to challenge recent observations in the wind tunnel balance community that shows an ever increasing desire for more data points per calibration absent of guidance to determine when there are enough. This paper presents fundamental concepts and theory to aid in the development of calibration procedures for wind tunnel balances and provides a framework that is generally applicable to the characterization and calibration of other measurement systems. Questions that need to be answered are for example: What constitutes an adequate calibration? How much data are needed in the calibration? How good is the calibration? This paper will assist a practitioner in answering these questions by presenting an underlying theory on how to evaluate a calibration based on objective measures. This will enable the developer and user to design calibrations with quantified performance in terms of their capability to meet the user's objectives and a basis for comparing existing calibrations that may have been developed in an ad-hoc manner.

Rhew, Ray D.↗