SEARCH · Engineering Papers
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.
This paper describes an integrated system for coordinating multiple rover behavior with the overall goal of collecting planetary surface data. The Multi-Rover Integrated Science Understanding System (MISUS) combines techniques from planning and scheduling with machine learning to perform autonomous scientific exploration with cooperating rovers.
During the Acquisition Life Cycle for a program, there are several opportunities for the system in design to be adjusted in accordance with its changing landscape as it is being shaped by evolving policy and organizational culture. Human Systems Integration is integral to identifying these opportunities of change as there are a set number of activities that may account for altered operational states, human performance deviations, and overall component engagement if HSI is enacted early enough in the life cycle. Some changes that occur in the operational environment may not be accounted for since the organizational culture and practices are not currently a part of the HSI focus. Likewise, policy changes themselves from a top-to-bottom analysis may not have the appearance of effecting human performance until having gone through a trail-and-error period. Workarounds to adjust for unforeseen policy affects become the system's solution that usually includes changes in the training and education of the operators, maintainers, and support personnel. A system full of workarounds and off-normal practices, that cause operators to disregard the purpose of the design, coupled with the false notion that these activities are proven for successful system operation, is the very definition of “an accident waiting to happen”. Unforeseen changes in policies and practices that cause new and unusual activities to successfully and keep the system running, should be considered latent factors that may cause a potential mishap, and not part of the resilience that humans provide to the successful operation of the system. This presentation will explore how latent factors may find their way into system operations and how they can be identified and addressed.
The National Aeronautics and Space Administration Unmanned Aircraft Systems Integration in the National Airspace System Project has conducted a series of flight tests intended to support the reduction of barriers that prevent unmanned aircraft from flying without the required waivers from the Federal Aviation Administration. The 2015 Flight Test Series 3, supported two separate test configurations. The first configuration investigated the timing of Detect and Avoid alerting thresholds using a radar equipped unmanned vehicle and multiple live intruders flown at varying encounter geometries.
NASA’s future exploration missions mandate a significant paradigm change for mission planning, spacecraft design, human systems integration, and in-flight medical care due to constraints on mass, volume, power, resupply missions, and medical evacuation capabilities. These constraints require further development of the human health and performance system, which includes the medical, task performance, wellness, data, human and other systems necessary to keep the crew healthy and functioning optimally. The human health and performance system will be tightly integrated with mission and habitat design to provide a sufficient human health and performance infrastructure to enable mission success. A suite of systems engineering tools will aid in the decision making process for the development of such a human health and performance system. This Concept of Operations provides a vision for a tool suite to conduct evaluations of human health and performance system options, inform research prioritization, and provide trade study support, based on evidence, risks, and systems engineering principles. The integrated tool suite under development is IMPACT.
Advancement in technology drives our future. Moreover, the successful implementation of a technology drives its possibilities. The National Aeronautics and Space Administration (NASA) has invested in numerous technologies over the decades. A quote from NASA’s Space Technology Mission Directorates indicates the importance of technology: “Historically, technology has driven humanity’s progress and will continue to define our future. Our nation chooses to invest in new technology not only to maintain our edge in the global economy but also because technology helps us: Redefine the possible; Create a technologically advanced future; and Drive economic growth.” It is difficult for a technology to satisfy these goals unless it can be successfully infused into a system. For a technology to continue to evolve, become a reality, and infuse into NASA’s missions, there must exist a compilation of success-oriented factors for the technology to reach fruition. Understanding these factors could help decrease the complexity of technology infusion and bridge the gap between technology developers and system integrators. Ultimately, the knowledge gained could facilitate the design, development, and infusion of a technology to be more effective and efficient. Successful technology infusion is complex. Even complexity at the interfaces can be daunting when advanced technology’s infuse into complex systems such as a spacesuit. Additionally, unforeseen emergent behavior and challenges can surface upon integration. Overall, there is a need to understand and measure the success of infusing an advanced technology into a complex system. Industry and academia desire to quantify performance benefits of technologies integrated into complex systems. This paper will focus advanced technology infusion into a spacesuit system. This research could help NASA and industry’s project managers and system mangers integrate advanced technologies more effectively and efficiently.
While modern wind turbines have become by far the largest rotating machines on Earth with further upscaling planned for the future, a renewed interest in small wind turbines (SWTs) is fostering energy transition and smart grid development. Small machines have traditionally not received the same level of aerodynamic refinement as their larger counterparts, resulting in lower efficiency, lower capacity factors, and therefore a higher cost of energy. In an effort to reduce this gap, research programs are developing worldwide. With this background, the scope of the present study is 2-fold. In the first part of this paper, an overview of the current status of the technology is presented in terms of technical maturity, diffusion, and cost. The second part of the study proposes five grand challenges that are thought to be key to fostering the development of small wind turbine technology in the near future, i.e. (1) improving energy conversion of modern SWTs through better design and control, especially in the case of turbulent wind; (2) better predicting long-term turbine performance with limited resource measurements and proving reliability; (3) improving the economic viability of small wind energy; (4) facilitating the contribution of SWTs to the energy demand and electrical system integration; (5) fostering engagement, social acceptance, and deployment for global distributed wind markets. To tackle these challenges, a series of unknowns and gaps are first identified and discussed. Based on them, improvement areas are suggested, for which 10 key enabling actions are finally proposed.
Integrated Components Technology Demonstrations (ICTD) is a project under the Ultra-Efficient Engine Technology Program (UEET) as designated in the UEET Program Commitment Agreement. The ICTD Project will provide the opportunity to conduct technology demonstration tests of advanced turbine engine components (e.g., combustor, compressor, turbine, and materials) as part of an integrated system (TRL 6). Initially, the major objectives of the Integrated Components Technology Demonstrations project are to Conduct component technology evaluation and system studies to determine, and prioritize, the most promising propulsion concepts, cycle, and architecture for a propulsion system with a Technology Availability Date of approximately 2010 and Entry Into Service of 2015. Determine the most attractive, cost-effective approaches for conducting the needed demonstration tests. Conduct demonstration tests of selected component technologies (i.e.,2200 F CMC combustor liner and aspirating seal) in partnership with industry.
The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).
A 5 cm structurally integrated ion thruster has been developed for attitude control and stationkeeping of synchronous satellites. With 2-D vectorable grids, thrust is 0.56 mlb at a beam voltage of 1200 V, total mass efficiency is 64%, and electrical efficiency is 46.8%. Nonvectoring thrust of 0.41 is demonstrated at very low specific impulse with dielectric coated grids. Structural integrity is demonstrated with dielectric coated grids for shock (30 G), sinusoidal (9 G), and random (19 G squared/Hz) accelerations. System envelope is 31.6 cm long by 14 cm flange B.C. with a mass of 8.5 kg including 6.2 Kg mercury propellant.
The emphasis on increased aircraft and propulsion control system integration and piloted simulation has created a need for higher fidelity real time dynamic propulsion models. A real time propulsion system modeling technique which satisfies this need and which provides the capabilities needed to evaluate propulsion system performance and aircraft system interaction on manned flight simulators was developed and demonstrated using flight simulator facilities at NASA Ames. A piecewise linear state variable technique is used. This technique provides the system accuracy, stability and transient response required for integrated aircraft and propulsion control system studies. The real time dynamic model includes the detail and flexibility required for the evaluation of critical control parameters and propulsion component limits over a limited flight envelope. The model contains approximately 7.0 K bytes of in-line computational code and 14.7 K of block data. It has an 8.9 ms cycle time on a Xerox Sigma 9 computer. A Pegasus-Harrier propulsion system was used as a baseline for developing the mathematical modeling and simulation technique. A hydromechanical and water injection control system was also simulated. The model was programmed for interfacing with a Harrier aircraft simulation at NASA Ames. Descriptions of the real time methodology and model capabilities are presented.
The emphasis on increased aircraft and propulsion control system integration and piloted simulation has created a need for higher fidelity real time dynamic propulsion models. A real time propulsion system modeling technique which satisfies this need and which provides the capabilities needed to evaluate propulsion system performance and aircraft system interaction on manned flight simulators was developed and demonstrated using flight simulator facilities at NASA Ames. A piecewise linear state variable technique is used. This technique provides the system accuracy, stability and transient response required for integrated aircraft and propulsion control system studies. The real time dynamic model includes the detail and flexibility required for the evaluation of critical control parameters and propulsion component limits over a limited flight envelope. The model contains approximately 7.0 K bytes of in-line computational code and 14.7 K of block data. It has an 8.9 ms cycle time on a Xerox Sigma 9 computer. A Pegasus-Harrier propulsion system was used as a baseline for developing the mathematical modeling and simulation technique. A hydromechanical and water injection control system was also simulated. The model was programmed for interfacing with a Harrier aircraft simulation at NASA Ames. Descriptions of the real time methodology and model capabilities are presented.
Aerospace problems are highly multidisciplinary. Four or more major disciplines are involved in analyzing any particular vehicle. Moreover, the choice of implementation technology of various subsystems can lead to a change of leading domain or reformation of the driving equations. An excellent example is the change of expertise required to consider aircraft built from composite or metallic structures, or those propelled by chemical or electrical thrusters. Another example is in the major reconfiguration of handling and stability equations with different control surface configuration (e.g., canards, t-tail v four-post tail). Combinatorial problems are also commonplace anytime that a major system is to be designed. If there are only 5 attributes of a design to consider with 4 different options, this is already 1024 options. Adding just 5 more dimensions to the study explodes the space to over one million. Even generous assumptions like the idea that only 10% of the combinations are physically feasible can only contain the problem for so long. To make matters worse, the simple number of combinations is only the beginning. Combining the issue of trade space size with the need to reformulate the design problem for many of the possibilities makes life exponentially more difficult. Advances in software modeling approaches have led to the development of model-driven architecture. This approach uses the transformation of models into inferred models (e.g. inferred execution traces from state machines) or the skeletons for code generation. When the emphasis on transformation is applied to aerospace, it becomes possible to exploit redundancy in the information specified in multiple domain models into a unified system model. F1urther, it becomes possible to overcome the combinatorial nature of specifying integrated system behavior by manually combining the equations governing a given component technology. Transformations from a system specification combined with a system-analysis mapping specification enable one-click combination of domain analyses. This is a flexibility that has been missing from many engineering codes, which often entangle design specification and physical examination much more than is required to conduct the analysis. This capability has been investigated and cultivated within the DARPA F6 program by a team of JPL and Phoenix Integration engineers building the Adapatable Systems Design and Analysis (ASDA) framework. By embracing system modeling with SysML and the Query-View-Transformation (QVT) language, the ASDA team has been able to build a flexible, easily reconfigurable framework for building up and solving large tradespaces. Examples of application and lessons learned in building the framework will be described in this paper. In addition, the motivation will be laid for various tool vendors to develop open model description standards while being able to maintain competitive advantage through proprietary algorithms and approaches. These standards will also be compared to the underpinnings of model-driven architecture and the OMG standards of the Meta-Object Facility (MOF), SysML, and QVT.
An integrated modeling tool that couples structural, optical, thermal and control disciplines is discussed.
NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development. The GFAS system integrates the flight software packages of the Orion and SLS with the ground systems and launch countdown sequencers through the 'agile' software development process. A unique approach is needed to develop the GFAS project capabilities within this agile process. NASA has defined the software development process through a set of standards. The standards were written during the infancy of the so-called industry 'agile development' movement and must be tailored to adapt to the highly integrated environment of human exploration systems. Safety of the space systems and the eventual crew on board is paramount during the preparation of the exploration flight systems. A series of software safety characteristics have been incorporated into the development and certification efforts to ensure readiness for use and compatibility with the space systems. Three underlining factors in the exploration architecture require the GFAS system to be unique in its approach to ensure safety for the space systems, both the flight as well as the ground systems. The first are the missions themselves, which are exploration in nature, and go far beyond the comfort of low Earth orbit operations. The second is the current exploration system will launch only one mission per year even less during its developmental phases. Finally, the third is the partnered approach through the use of many different prime contractors, including commercial and international partners, to design and build the exploration systems. These three factors make the challenges to meet the mission preparations and the safety expectations extremely difficult to implement. As NASA leads a team of partners in the exploration beyond earth's influence, it is a safety imperative that the application software used to test, checkout, prepare and launch the exploration systems put safety of the hardware and mission first. Software safety characteristics are built into the design and development process to enable the human rated systems to begin their missions safely and successfully. Exploration missions beyond Earth are inherently risky, however, with solid safety approaches in both hardware and software, the boldness of these missions can be realized for all on the home planet.
Project management and payload integration requirements definition activities are reported. Mission peculiar equipment; systems integration; ground operations analysis and requirement definition; safety and quality assurance; and support systems development are examined for payloads planned for the following missions: EOM-1; SL-2; Sl-3 Astro-1; MSL-2; EASE/ACCESS; MPESS; and the middeck ADSF flight.
The Gravity Recovery And Interior Laboratory (GRAIL) mission was the first Jet Propulsion Laboratory (JPL) project initiated under NASA's revised rules for space flight project management, NPR 7120.5D, "NASA Space Flight Program and Project Management Requirements." NASA selected GRAIL through a competitive Announcement of Opportunity process and funded its Phase B Preliminary Design effort. The team's first major milestone was a JPL institutional milestone, the Project Mission System Review (PMSR), which proved an excellent tune-up for the end-of-Phase-B NASA life-cycle review, the Preliminary Design Review (PDR). Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. For the Project Critical Design Review (CDR), lessons learned from the PDR and updated Standing Review Board (SRB) practices from the Agency were factored into the review preparation effort. Additionally, the review was held at the Principal Investigator's institution, the Massachusetts Institute of Technology, rather than at the project management center (JPL), which necessitated additional cross-country coordination steps. The PMSR, PDR, and CDR were design reviews and largely paper-oriented. For the System Integration Review (SIR), the project needed to transition to a hardware review and deal with paper in a very different manner. While many of the practices employed for the design reviews were modified and retained (e.g., review preparation team, gate products management, pre-reviews, SRB coordination), the review agenda, presentation style, and slide templates were significantly changed. A key success factor concerned the handling of project open paper, which was succinctly and effectively communicated to the SRB in presentations.This paper provides a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project SIR preparation and execution activities, including positive and negative lessons learned and identifies recommendations for future NASA (and non- NASA) project teams.
The Integrated Maintenance Information System (IMIS) will optimize the use of available manpower, enhance technical performance, improve training, and reduce the support equipment and documentation needed for deployment. It will serve as the technician's single, integrated source of all the technical information required to perform modern aircraft maintenance.
Contents include the following: Advanced life support. System integration, modeling, and analysis. Progressive capabilities. Water processing. Air revitalization systems. Why advanced CO2 removal technology? Solid waste resource recovery systems: lyophilization. ISRU technologies for Mars life support. Atmospheric resources of Mars. N2 consumable/make-up for Mars life. Integrated test beds. Monitoring and controlling the environment. Ground-based commercial technology. Optimizing size vs capability. Water recovery systems. Flight verification topics.