Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Se”

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 91 records · Page 5

Best Practices for Evaluating Flight Deck Interfaces for Transport Category Aircraft with Particular Relevance to Issues of Attention, Awareness, and Understanding CAST SE-210 Output 2 Report 6 of 6

Attention, awareness, and understanding of the flight crew are a critical contributor to safety and the flight deck plays a critical role in supporting these cognitive functions. Changes to the flight deck need to be evaluated for whether the changed device provides adequate support for these functions. This report describes a set of diverse evaluation methods. The report recommends designing the interface-evaluation to span the phases of the device development, from early to late, and it provides methods appropriate at each phase. It describes the various ways in which an interface or interface component can fail to support awareness as potential issues to be assessed in evaluation. It summarizes appropriate methods to evaluate different issues concerning inadequate support for these functions, throughout the phases of development.

Billman, Dorrit O.↗

Factors that Influenced Airplane State Awareness Accidents and Incidents: CAST SE-210 Output 2: Report 2 of 6

This report is part of a series of reports that address flight deck design and evaluation, written as a response to loss of control accidents. In particular, this activity is directed at failures in airplane state awareness in which the pilot loses awareness of the airplane’s energy state or attitude and enters an upset condition. The Commercial Aviation Safety Team (CAST) created a team to analyze a set of incidents and accidents associated with the flight crew’s loss of awareness of aircraft attitude or energy state. The CAST activity focused on a set of 18 loss of control (LOC) accidents and incidents. In those events, the pilot seemed to lose awareness of the state of the airplane, especially related to its energy state or its attitude. To understand the roots of that loss of awareness, we analyzed the events in relation to a set of factors that were present in many of them. We show how these factors contributed to lost awareness. Then, we use that understanding to identify potentially useful changes to the flight deck interface and how those flight deck changes could be evaluated.

commercial aviation↗

Evaluation Issues for a Flight Deck Interface; CAST SE-210 Output 2: Report 4 of 6

This report is part of a series of reports that addresses flight deck design and evaluation, written as a response to loss of control accidents. In particular, this activity is directed at failures in airplane state awareness, in which the pilot loses awareness of the airplane’s energy state or attitude and enters an upset condition. Another report in this series of reports speaks directly to flight deck evaluation methods and metrics for the types of attention and awareness issues that were revealed from the airplane state awareness events. In this report, we describe a wide range of flight deck evaluation issues tied to flight crew performance. The objectives are to establish a framework for thinking about how the flight deck interface should support the performance of the flight crew, and to aid the Federal Aviation Administration (FAA) in identifying relevant human performance issues during the evaluation/certification process. Issues are broken out into sections that cover physical ergonomics, design for usability, data integration and display content, attention and task management, flight crew problem solving, and flight crew teaming. For each issue, we recommend specific ways that the flight deck interface should support the flight crew. For each, we also identify existing 14 CFR Part 25 rules and guidance that are relevant to the issue. This allows the FAA to determine what current regulatory materials can support them in raising the issue with the applicant.

commercial aviation↗

Mixed-Domain Charge Transport in S-Se Alloys as a Li-S Battery Cathode Material

Lithium-sulfur batteries are emerging candidate systems for the next-generation long-range electric aircraft application owing to their potential to deliver high energy density per weight. Their cathodes are to be made primarily with sulfur, but sulfur by itself has much too low electron conductivity to serve as a useful cathode. An idea that has been suggested to overcome this bottleneck is to alloy sulfur with selenium in the hope that electron mobility, which is thought to improve charge transport at some expense of increased weight and reduced energy density. However, understanding of these alloy structures and their transport mechanism is insufficient, and electron mobility at varying degrees of selenium content is not well charted, which are critical for determining the optimum selenium content and testing whether this strategy is generally feasible. The difficulty of computationally characterizing these alloy systems is rooted in the structure. The structures of both sulfur and selenium exhibit eight-atom rings that pack together in various orientations to form their respective crystals. For one, because these crystals (and presumably their alloys as well) feature multiple polymorphs such that their structural coherence is rather unclear. Secondly, these are also relatively large systems (32 atoms per cell) with low-symmetry, which complicate computation both in terms of accuracy and efficiency. Thirdly, such semi-molecular, semi-crystalline structures lead to a combination of band-transport characteristics and hopping-transport characteristics, each of which is a domain with its own physics and set of computational, theoretical challenges. In addition, there is a general dearth of experimental transport data for sulfur-selenium alloys. In this study, we make a comprehensive attempt to tackle this problem using a wide array of first-principles methods. We generate special quasirandom structures to simulate alloy structures, and compute their first-principles Raman spectra for comparison with experimental data to ensure their structural soundness. We then proceed to use recently developed, state-of-the-art tool (AMSET) in order to efficiently compute electronic mobilities under band transport of pure sulfur, pure selenium, as well as their alloys of various compositions at a reasonable accuracy. We then sample numerous dimer configurations of nearest-neighbor eight-atom-ring-pairs and compute electronic hopping rates between them, which yields hopping mobility. A combination of these efforts lead to a general mapping of electron transport behaviors throughout the alloy range. Preliminary results show that introduction of selenium into sulfur initially damages electron mobility due to disorder but eventually improves it beyond that of pure sulfur with additional selenium content, ultimately peaking at the pure-selenium limit. Band transport dominates for holes in sulfur and electrons in selenium, but in all other cases, hopping transport is dominant. Ongoing efforts include determination of charge concentration and conductivity, as well as performing multiphysics modeling to determine the optimum selenium content for best tradeoff between conductivity and energy density for aircraft range.

Junsoo Park↗

Open-source Wireless Sensor Network (Wi-Se Net) for Flexible Deployment

Wireless sensors, especially if battery powered, have a number of advantages over wired sensors for flexible or temporary diagnostic deployment in a field or lab setting. Recent advances in wireless technology and microprocessor boards have produced a variety of inexpensive off-the shelf chips which can communicate wirelessly with simple protocols. This paper describes the design and implementation of a highly customizable wireless sensor network (called WiSe Net) using inexpensive open-source hardware components as wireless nodes. These wireless sensor nodes can transmit data at a rate <250 Hz, can be battery powered, and have a small footprint (2x5 cm). In addition, a preliminary over-the-air programming system was developed to allow for simple wireless configuration when active. The network performance was demonstrated by taking distributed and electrically isolated temperature measurements on a high-voltage lab apparatus. Although this test case is in a laboratory setting, this network architecture could be easily repurposed for various other forms of monitoring

Wireless Sensor Network↗

Open-source Wireless Sensor Network (Wi-Se Net) for Flexible Deployment

Wireless sensors, especially if battery powered, have a number of advantages over wired sensors for flexible or temporary diagnostic deployment in a field or lab setting. Recent advances in wireless technology and microprocessor boards have produced a variety of inexpensive off-the shelf chips which can communicate wirelessly with simple protocols. This paper describes the design and implementation of a highly customizable wireless sensor network (called WiSe Net) using inexpensive open-source hardware components as wireless nodes. These wireless sensor nodes can transmit data at a rate <250 Hz, can be battery powered, and have a small footprint (2x5 cm). In addition, a preliminary over-the-air programming system was developed to allow for simple wireless configuration when active. The network performance was demonstrated by taking distributed and electrically isolated temperature measurements on a high-voltage lab apparatus. Although this test case is in a laboratory setting, this network architecture could be easily repurposed for various other forms of monitoring.

Wireless Sensor Network↗

Autonomous Constrained Control for Arbitrary Configurations of Gimbaling Thrusters in SE(3)

In order to develop robust autonomy in spacecraft, it is desirable to develop methods for controlling a spacecraft in various configurations with any combination of thrusters of various types and both for static RCS thrusters and gimbaling thrusters. In the case of a stuck thruster imposing unplanned and undesired motion both translational and rotational or in the case of a malfunctioning thruster, it is desirable for that spacecraft to have the ability to identify and overcome that problem without human intervention. To that end, a spacecraft must be able to rapidly and autonomously reconfigure thruster firing histories and update guidance protocols. In this paper, a method for a spacecraft to autonomously select thrusters of any configuration is presented. The residual motion imposed by off-nominal or not-fully-controllable thruster configurations is identified by the spacecraft and solved for, both for static reaction control systems and gimbaling engines.

Matthew M. Witta↗

Organizational Considerations for Implementing Systems Engineering and Integration in the Ares Projects Office

Systems Engineering and Integration (SE&I) is a critical discipline in developing new space systems. In 2005, NASA performed an internal study of 24 agency and Department of Defense (DoD) programs to evaluate methods of integrating SE&I practices and determine their effectiveness. The goal of the study was to determine the best SE&I implementation strategy for the Ares Projects Office. The study identified six SE&I organizational structures: 1. Lead systems integrator (LSI) with SE&I responsibility and government technical insight. 2a. Integration contractor with government SE&I responsibility (government insight). 2b. Integration contractor with government SE&I responsibility (government oversight). 3a. Prime contractor with SE&I responsibility (government insight). 3b. Prime contractor with SE&I responsibility (government oversight). 3c. Prime contractor with SE&I responsibility (government/industry partnership). 4a.Prime contractor with government SE&I responsibility (government insight). 4b. Prime contractor with government SE&I responsibility (government oversight). 4d.Prime contractors with total system performance responsibility (TSPR). 5. Prime contractor with government SE&I responsibility and integration products through a Federally Funded Research and Development Center (FFRDC). 6. Government/FFRDC in-house development with SE&I responsibility and function. The organizational structure used most often was number 4, using a prime contractor with government SE&I responsibility and government technical insight. However, data analyses did not establish a positive relationship between program development costs and specific SE&I organizational types, nor did it positively determine the relationship between successful programs or projects and their SE&I structure. The SE&I study reached the following conclusions: (1) Large, long-duration, technically complex programs or projects reach their technical goals, but rarely meet schedule or cost goals. NASA's recent successes have been smaller, short-duration development projects using heritage hardware/software, focused technology development, technical oversight and stable external factors. (2) Programs and projects have failed or been terminated due to lack of technical insight, relaxing of SE&I processes, and unstable external factors. (3) The study did not find a single, clear optimum SE&I organization type to fit all projects. However, while any organizational structure can be made to work, the fewer complexities in the program, the better the likelihood of success. (4) The most common successful SE&I organization structure type in the study was type 4b, where the government maintained integration responsibility, with the prime contractor providing SE&I products and the government providing technical oversight. This study was instrumental in helping the APO select organization structure 4, following the same SE&I and oversight process used during humanlund7s last voyages to the Moon.

Thomas, LeAnn↗

Introduction of an Agile Systems Engineering Process to the NASA Armstrong Flight Research Center

This paper will provide background on the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD) ARMD Test Data Portal (ATDP) effort along with the rationale that motivated the ATDP team to consider implementing an agile systems engineering (SE) process. The primary motivation for using this new SE process was based on the desire to mitigate a major risk to project success. Since the agile SE process had never been used before at the NASA Armstrong Flight Research Center (AFRC), utilizing this new SE process required a trailblazing effort to introduce it to NASA AFRC leadership. As a result, the ATDP team chose to adhere to the agile SE process in addition to the trusted classical waterfall SE process on ATDP. Through successful execution of this hybrid SE process during Phase I, along with demonstrating the value and rigor of the agile SE process, NASA AFRC leadership ultimately permitted the ATDP project to solely use the agile SE process for developments beyond Phase I. While it is the opinion of the authors that the classical SE process is more effective for most projects at NASA AFRC, some projects may deem that the agile SE process is more advantageous. Although this paper is focused on introducing the agile SE process to NASA AFRC, lessons learned will be valuable to other organizations as well. Details of how the ATDP team implemented the agile SE process during Phase I will be summarized, along with how the team met all required classical SE milestones. Lessons learned throughout Phase I of this effort will also be highlighted.

Daniel S. Jones↗

System Engineering on the Use for Ares I,V - the Simpler, the Better

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt & Whitney Rocketdyne Company. The J-2X is an improved higher power version of the original J-2 engine used during the Apollo program. With higher power and updated requirements for safety and performance, the J-2X becomes a new engine using state-of-the-art design methodology, materials and manufacturing processes. The implementation of Systems Engineering (SE) principles enables the rapid J-2X development program to remain aligned with the ARES I and V vehicle programs, Meeting the aggressive development schedule is a challenge. Coordinating the best expertise thai NASA and PWR have to offer requires effectively utilizing resources at multiple sites. This presents formidable communication challenges. SE allows honest and open discussions of issues and problems. This simple idea is often overlooked in large and complex SE programs. Regular and effective meetings linking SE objectives to component designs are used to voice differences of opinions with customer and contractor in attendance so that the best mutual decisions can be made on the shortest possible schedule. Regular technical interchange meetings on secure program wide computer networks and CM processes are effective,in the "Controlled Change" process that exemplifies good SE. Good communication is a key effective SE implementation. The System of Systems approach is the vision of the Orion program which facilitates the establishment of dynamic SE processes at all levels including the engine. SE enables requirements evolution by facilitating organizational and process agility. Flow down and distribution of requirements is controlled by Allocation Reports which breakdown numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements helps eliminate redundancy and potential mistakes inherent m separated systems. Another tool, the Architecture Design Description, is being used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof is in successful program accomplishment. The SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. The Ares I SE system of systems has delivered according to expectations thus far. All major design reviews (SRR. PDR, CDR) have been successfully conducted to satisfy overall program objectives using SE as the basis for accomplishment. The paper describes SE tools and techniques utilized to achieve this success.

Kelly, William↗

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM). This methodology and corresponding model, known as a Goal-Function Tree (GFT), provides a means to represent, decompose, and elaborate system goals and functions in a rigorous manner that connects directly to design through use of state variables that translate natural language requirements and goals into logical-physical state language. The state variable-based approach also provides the means to directly connect FM to the design, by specifying the range in which state variables must be controlled to achieve goals, and conversely, the failures that exist if system behavior go out-of-range. This in turn allows for the systems engineers and SHM/FM engineers to determine which state variables to monitor, and what action(s) to take should the system fail to achieve that goal. In sum, the GFT representation provides a unified approach to early-phase SE and FM development. This representation and methodology has been successfully developed and implemented using Systems Modeling Language (SysML) on the NASA Space Launch System (SLS) Program. It enabled early design trade studies of failure detection coverage to ensure complete detection coverage of all crew-threatening failures. The representation maps directly both to FM algorithm designs, and to failure scenario definitions needed for design analysis and testing. The GFT representation provided the basis for mapping of abort triggers into scenarios, both needed for initial, and successful quantitative analyses of abort effectiveness (detection and response to crew-threatening events).

Patterson, Jonathan D.↗

How ExMC Communicates a System Model to Non-Modelers

NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and mission planners. Many of these stakeholders have neither access to MBSE modeling tools nor experience with SE modeling techniques. The challenge faced by ExMC SE team was how to present the content in the model to non-modelers in a way they would understand the content with limited training in MBSE and without using the modeling tool. ExMC SE team created a Hypertext Markup Language (HTML) report that shows key model content and is accessible to anyone with a browser. When creating the HTML report, the ExMC SE received stakeholder feedback on what content they wanted and how to display this content. Incorporating this feedback, the report arranges the content in a way that directs readers through the SE process taken to derive the requirements and helps them to understand the fundamental steps in an SE approach. The report includes links to source information (e.g., NASA documentation that describes levels of care) and other SE products (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This presentation outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

J. Cohen↗

Changes of snow cover, temperature, and radiative heat balance over the Northern Hemisphere

Contemporary large-scale changes in satellite-derived snow cover were examined over the Northern Hemisphere extratropical land (NEL) areas. These areas encompass 55% of the land in the Northern Hemisphere. Snow cover (S) transient regions, the 'centers of action' relative to interannual variations of snow cover, were identified for the years 1972-1992. During these years a global retreat in snow cover extent (SE) occurred in the second half of the hydrologic year (April-September). Mean annual SE has decreased by 10% (2.3 x 10(exp 6) sq km). Negative trends account for one-third to one-half of the interannual continental variance of SE. The historical influence of S on the planetary albedo and outgoing longwave radiation (OLR) is investigated. The mean annual response of the S feedback on the radiative balance (RB) is negative and suggests a largescale heat redistribution. During autumn and early winter (up to January), however, the feedback of S on the planetary RB may be positive. Only by February does the cooling effect of S (due to albedo increase) dominate the planetary warming due to reduced OLR over the S. Despite a wintertime maximum in SE, the feedback in spring has the greatest magnitude. The global retreat of spring SE should lead to a positive feedback on temperature. Based on observed records of S, changes in RB are calculated that parallel an observed increase of spring temperature during the past 20 years. The results provide a partial explanation of the significant increase in spring surface air temperature observed over the land areas of the Northern Hemisphere during the past century. The mean SE in years with an El Nino and La Nina were also evaluated. El Nino events are generally accompanied by increased SE over the NEL during the first half of the hydrological year. In the second half of the hydrologic year (spring and summer), the El Nino events are accompanied by a global retreat of SE.

Groisman, Pavel YA.↗