Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “system engineering system process”

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 775 records · Page 43

Vehicle Integrated Performance Analysis, the VIPA Experience: Reconnecting with Technical Integration

Today's NASA is facing significant challenges and changes. The Exploration initiative indicates a large increase in projects with limited increase in budget. The Columbia report has criticized NASA for its lack of insight and technical integration impacting its ability to provide safety. The Aldridge report is advocating NASA find new ways of doing business. Very early in the Space Launch Initiative (SLI) program a small team of engineers at MSFC were asked to propose a process for performing a system level assessment of a launch vehicle. The request was aimed primarily at providing insight and making NASA a "smart buyer." Out of this effort the VIPA team was created. The difference between the VIPA effort and many integration attempts is that VIPA focuses on using experienced people from various disciplines and a process which focuses them on a technically integrated assessment. Most previous attempts have focused on developing an all encompassing software tool. In addition, VIPA anchored its process formulation in the experience of its members and in early developmental Space Shuttle experience. The primary reference for this is NASA-TP-2001-210092, "Launch Vehicle Design Process: Characterization, Technical Integration, and Lessons Learned," and discussions with its authors. The foundations of VIPA's process are described. The VIPA team also recognized the need to drive detailed analysis earlier in the design process. Analyses and techniques typically done in later design phases, are brought forward using improved computing technology. The intent is to allow the identification of significant sensitivities, trades, and design issues much earlier in the program. This process is driven by the T-model for Technical Integration described in the aforementioned reference. VIPA's approach to performing system level technical integration is discussed in detail. Proposed definitions are offered to clarify this discussion and the general systems integration dialog. VIPA's capabilities and process can now be used to significantly enhance the development and monitoring of realizable project requirements. This is done through the use of VIPA's V-model. Starting with a given concept, VIPA's assessment validates the concept's stated performance, identifies significant issues either with the concept or the requirements, and then re-integrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program's insight and review process. The VIPA process has been employed successfully on several projects including SLI, Orbital Space Plane (OSP), and several heavy lift concepts for Exploration. It has also been proposed for use on the Jupiter Icy Moon (JIMO) spacecraft. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful. Selected results from these assessments will be presented.

McGhee, David S.↗

Space Shuttle Main Engine Joint Data List Applying Today's Desktop Technologies to Facilitate Engine Processing

Boeing-Rocketdyne's Space Shuttle Main Engine (SSME) is the world's first large reusable liquid rocket engine. The space shuttle propulsion system has three SSMEs, each weighing 7,400 lbs and providing 470,000 lbs of thrust at 100% rated power level. To ensure required safety and reliability levels are achieved with the reusable engines, each SSME is partially disassembled, inspected, reassembled, and retested at Kennedy Space Center between each flight. Maintenance processing must be performed very carefully to replace any suspect components, maintain proper engine configuration, and avoid introduction of contaminants that could affect performance and safety. The long service life, and number, complexity, and pedigree of SSME components makes logistics functions extremely critical. One SSME logistics challenge is documenting the assembly and disassembly of the complex joint configurations. This data (joint nomenclature, seal and fastener identification and orientation, assembly sequence, fastener torques, etc.) must be available to technicians and engineers during processing. Various assembly drawings and procedures contain this information, but in this format the required (practical) joint data can be hard to find, due to the continued use of archaic engineering drawings and microfilm for field site use. Additionally, the release system must traverse 2,500 miles between design center and field site, across three time zones, which adds communication challenges and time lags for critical engine configuration data. To aid in information accessibility, a Joint Data List (JDL) was developed that allows efficient access to practical joint data. The published JDL has been a very useful logistics product, providing illustrations and information on the latest SSME configuration. The JDL identifies over 3,350 unique parts across seven fluid systems, over 300 joints, times two distinct engine configurations. The JDL system was recently converted to a web-based, navigable electronic manual that contains all the required data and illustrations in expanded view format using standard PC products (Word, Excel, PDF, Photoshop). The logistics of accurately releasing this information to field personnel was greatly enhanced via the utilization of common office products to produce a more user-friendly format than was originally developed under contract to NASA. This was done without reinventing the system, which would be cost prohibitive on a program of this maturity. The brunt of the joint part tracking is done within the logistics organization and disseminated to all field sites, without duplicating effort at each site. The JDL is easily accessible across the country via the NASA intranet directly at the SSME workstand. The advent of this logistics data product has greatly enhanced the reliability of tracking dynamic changes to the SSME and greatly reduces engineering change turnaround time and potential for errors. Since the inception of the JDL system in 1997, no discrepant parts have propagated to engine assembly operations. This presentation focuses on the challenges overcome and the techniques used to apply today's desktop technologies to an existing logistics data source.

Jacobs, Kenneth↗

Supplemental knowledge acquisition through external product interface for CLIPS

Traditionally, the acquisition of knowledge for expert systems consisted of the interview process with the domain or subject matter expert (SME), observation of domain environment, and information gathering and research which constituted a direct form of knowledge acquisition (KA). The knowledge engineer would be responsible for accumulating pertinent information and/or knowledge from the SME(s) for input into the appropriate expert system development tool. The direct KA process may (or may not) have included forms of data or documentation to incorporate from the SME's surroundings. The differentiation between direct KA and supplemental KA (indirect) would be the difference in the use of data. In acquiring supplemental knowledge, the knowledge engineer would access other types of evidence (manuals, documents, data files, spreadsheets, etc.) that would support the reasoning or premises of the SME. When an expert makes a decision in a particular task, one tool that may have been used to justify a recommendation, would have been a spreadsheet total or column figure. Locating specific decision points from that data within the SME's framework would constitute supplemental KA. Data used for a specific purpose in one system or environment would be used as supplemental knowledge for another, specifically a CLIPS project.

Saito, Tim↗

Symposium (International) on Combustion, 20th, University of Michigan, Ann Arbor, MI, August 12-17, 1984, Proceedings

The present conference on combustion phenomena considers topics in automotive engine combustion, turbulent reacting flows, the modeling of practical combustion systems, reaction kinetics, combustion-generated particulates, combustion diagnostics, coal combustion process characteristics, fire-related phenomena, explosion/detonation phenomena, spray combustion, ignition/extinction, laminar flames, pollutant formation processes, practical combustor devices, and rocket propellant combustion. Attention is given to the contributions of combustion science to piston engine design, modeling and measurement techniques for turbulent combustion, the specific effects of energy, collisions, and transport processes in combustion chemistry kinetics, the formation of large molecules, particulates and ions in premixed hydrocarbon flames, the application of laser diagnostics to combustion systems, spark ignition energies for dust-air mixtures, the controlling mechanisms of flow-assisted flame spread, the ignition and combustion of coal-water slurries, spontaneous ignition of methane, turbulent and accelerating dust flames, and the temperature sensitivity of double base propellants.

Source record↗

Advanced Environmental Barrier Coating Development for SiC-SiC Ceramic Matrix Composite Components

This presentation reviews the NASA advanced environmental barrier coating (EBC) system development for SiCSiC Ceramic Matrix Composite (CMC) components for next generation turbine engines. The emphasis has been placed on the current design challenges of the 2700F environmental barrier coatings; coating processing and integration with SiCSiC CMCs and component systems; and performance evaluation and demonstration of EBC-CMC systems. This presentation also highlights the EBC-CMC system temperature capability and durability improvements through advanced compositions and architecture designs, as shown in recent simulated engine high heat flux, combustion environment, in conjunction with mechanical creep and fatigue loading testing conditions.

Simulated Engine Test↗

In-Situ Resource Utilization Modeling of a Lunar Water Processing System

A key element of achieving a sustained surface presence, such as defined in NASA’s Artemis plan, is In-Situ Resource Utilization (ISRU). ISRU is the practice of using local resources to provide mission consumables that reduce system launch mass requirements, and regenerate resources (chiefly, water and oxygen) for propulsion and life support supporting both Lunar and Martian missions. ISRU systems require multiple complex processes, such as excavation, chemical reactors, and electrolysis subsystems that must operate in harmony to optimize the overall system process from beginning to end. The Mission Analysis and Integration Tool (MAIT) was previously developed with MATLAB in FY22 to connect individual subsystem models into a customized, flexible framework for the purpose of technology downselect, optimization, and end-to-end process planning. Beginning in FY24, MAIT was updated and became the capital program in the Systems Engineering and Integration (SE&I) ISRU Modeling and Analysis (SIMA) project. Prior work was leveraged and evolved using MATLAB/Simulink due to its ability to communicate with a vast number of other programming languages and makes up the backbone of data flow between inputs and outputs to the subsystem models. MAIT initially evaluated a suite of ISRU-related technologies, including the water processing Lunar Auger Dryer for ISRU (LADI) system with integrated upstream excavation and downstream electrolysis subsystems. With individual models consolidated, the MAIT tool generated over 5,000 cases during its first round of parametric sweeps on the water processing architecture at multiple production targets; the system analysis produced valuable insight into the optimal LADI geometry that minimized energy demands, estimated effects to cold trap size and radiator requirements, and calculated the power dynamics of the electrolysis unit and liquid oxygen storage volume. Additional efforts are being made to demonstrate the ability to scale ISRU technologies supporting the Space Technology Mission Directorate’s (STMD) commercialization strategy and increase the MAIT software capability. Work is ongoing to handle a wide array of ISRU system models beyond the Lunar environment, e.g. production of propellant for a Martian lander.

Avery Carlson↗

In-Situ Resource Utilization Modeling of a Lunar Water Processing System

A key element of achieving a sustained surface presence, such as defined in NASA’s Artemis plan, is In-Situ Resource Utilization (ISRU). ISRU is the practice of using local resources to provide mission consumables that reduce system launch mass requirements, and regenerate resources (chiefly, water and oxygen) for propulsion and life support supporting both Lunar and Martian missions. ISRU systems require multiple complex processes, such as excavation, chemical reactors, and electrolysis subsystems that must operate in harmony to optimize the overall system process from beginning to end. The Mission Analysis and Integration Tool (MAIT) was previously developed with MATLAB in FY22 to connect individual subsystem models into a customized, flexible framework for the purpose of technology downselect, optimization, and end-to-end process planning. Beginning in FY24, MAIT was updated and became the capital program in the Systems Engineering and Integration (SE&I) ISRU Modeling and Analysis (SIMA) project. Prior work was leveraged and evolved using MATLAB/Simulink due to its ability to communicate with a vast number of other programming languages and makes up the backbone of data flow between inputs and outputs to the subsystem models. MAIT initially evaluated a suite of ISRU-related technologies, including the water processing Lunar Auger Dryer for ISRU (LADI) system with integrated upstream excavation and downstream electrolysis subsystems. With individual models consolidated, the MAIT tool generated over 5,000 cases during its first round of parametric sweeps on the water processing architecture at multiple production targets; the system analysis produced valuable insight into the optimal LADI geometry that minimized energy demands, estimated effects to cold trap size and radiator requirements, and calculated the power dynamics of the electrolysis unit and liquid oxygen storage volume. Additional efforts are being made to demonstrate the ability to scale ISRU technologies supporting the Space Technology Mission Directorate’s (STMD) commercialization strategy and increase the MAIT software capability. Work is ongoing to handle a wide array of ISRU system models beyond the Lunar environment, e.g. production of propellant for a Martian lander.

Avery Carlson↗

A New Vision and A More Rational Process Will Advance Space Life Support Through Better Projects

Many space life support assumptions are obviously mistaken but they are generally accepted because they mutually support each other and because they advance a mistaken futuristic vision of closed human ecosystems in space. Many projects have been mistakenly selected to increase life support system closure or reduce launch mass in order to implement this impractical vision. Project members rarely challenge their project’s assumptions and guiding vision. Systems engineering including cost, reliability, risk, and system trade-offs has been very strongly discouraged to prevent rational criticism of these dubious assumptions, the projects, and the ecosystem vision. A more realistic vision can define better near term life support goals and future aspirations that will improve mission support and increase public interest. Given more realistic goals, it will be possible to develop effective technical alternatives, use open rational project selection methods, conduct professional project management, and make swifter progress in the inevitable human advance into space. The current unworkable human space settlement scenario involves moon visits and permanent bases, zero gravity trips to Mars, Mars visits and bases, all leading to extensive human settlements on the moon and Mars. This is unrealistic because the moon and Mars have less than Earth normal gravity and high radiation that can seriously damage human health. A better alternative would use rotating space colonies that produce Earth gravity and are radiation shielded. The attractive fantasy of reproducing terrestrial ecology in space should be replaced by the idea of building a closed system based on advancing technology such as artificial photosynthesis. Past mistaken projects include growing plants for food to replicate terrestrial food sources, recovering small amounts of water from difficult to process waste to achieve high system closure, and using newly designed, lighter, but unreliable hardware to reduce launch mass. The political process supporting the false assumptions, projects, and vision has deliberately prevented the usual systems engineering and cost-benefit analysis. We are going to do much better.

Harry W. Jones↗

Engineering Antifragile Systems: A Change In Design Philosophy

While technology has made astounding advances in the last century, problems are confronting the engineering community that must be solved. Cost and schedule of producing large systems are increasing at an unsustainable rate and these systems often do not perform as intended. New systems are required that may not be achieved by current methods. To solve these problems, NASA is working to infuse concepts from Complexity Science into the engineering process. Some of these problems may be solved by a change in design philosophy. Instead of designing systems to meet known requirements that will always lead to fragile systems at some degree, systems should be designed wherever possible to be antifragile: designing cognitive cyberphysical systems that can learn from their experience, adapt to unforeseen events they face in their environment, and grow stronger in the face of adversity. Several examples are presented of on ongoing research efforts to employ this philosophy.

Jones, Kennie H.↗

Current status of droplet and liquid combustion

The present understanding of spray combustion in rocket engine, gas turbine, Diesel engine and industrial furnace applications is reviewed. In some cases, spray combustion can be modeled by ignoring the details of spray evaporation and treating the system as a gaseous diffusion flame; however, in many circumstances, this simplification is not adequate and turbulent two-phase flow must be considered. The behavior of individual droplets is a necessary component of two-phase models and recent work on transient droplet evaporation, ignition and combustion is considered, along with a discussion of important simplifying assumptions involved with modeling these processes. Methods of modeling spray evaporation and combustion processes are also discussed including: one-dimensional models for rocket engine and prevaporized combustion systems, lumped zone models (utilizing well-stirred reactor and plug flow regions) for gas turbine and furnace systems, locally homogeneous turbulent models, and two-phase models. The review highlights the need for improved injector characterization methods, more information of droplet transport characteristics in turbulent flow and continued development of more complete two-phase turbulent models

Faeth, G. M.↗

Scheduling System Assessment, and Development and Enhancement of Re-engineered Version of GPSS

The objective of this project is two-fold. First to provide an evaluation of a commercially developed version of the ground processing scheduling system (GPSS) for its applicability to the Kennedy Space Center (KSC) ground processing problem. Second, to work with the KSC GPSS development team and provide enhancement to the existing software. Systems reengineering is required to provide a sustainable system for the users and the software maintenance group. Using the LISP profile prototype code developed by the GPSS reverse reengineering groups as a building block, we have implemented the resource deconfliction portion of GPSS in common LISP using its object oriented features. The prototype corrects and extends some of the deficiencies of the current production version, plus it uses and builds on the classes from the development team's profile prototype.

Loganantharaj, Rasiah↗

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗

NASA GRC ICME Schema for Materials Data Management: An Executive Summary

Integrated Computational Materials Engineering (ICME) has received a growing emphasis in attention due its potential impact on rapid material design, reduction in cost and time to market for new applications, and the promise of ‘fit-for-purpose’ materials coupled with recent advances in high performance computing and material characterization tools. However, for an organization to implement ICME practices for material discovery and design, a series of both technical and cultural challenges must be overcome to foster an environment that enables efficient, traceable, and predictive multiscale simulations of material behavior to enable virtual design of materials. In 2016, NASA sponsored a 2040 Vision study to define the potential 25-year future state required for integrated multiscale modeling of materials and systems to improve both the associated time and cost for aerospace and aeronautical innovation. The study envisions a cyber-physical-social ecosystem of experimentally validated computational models, tools, and techniques, along with the associated digital tapestry, that can enable rapid, optimized, ‘fit-for-purpose’ design of materials, components, and systems. A key requirement for such an ecosystem is the development of a robust information management system for materials across their full lifecycle, including material pedigree, experimental (real) and virtual (simulation) data, developed material models, and the implementation of models in engineering applications, such that process-structure-property-performance relationships can be established, thereby enabling the virtual design and optimization of materials. Such an information management system must be able to effectively capture: i) material information at each length scale; ii) test data and analysis; iii) associated material models; and iv) material and model deployment in engineering applications. These systems must also provide traceability between experimental and virtual representations of the material to ensure, when appropriate, the material digital twin is maintained. Additionally, this robust material information management system must be able to seamlessly connect with both commercial and an organization’s in-house software tools, be they analysis tools, other material databases, product lifecycle management (PLM) or simulation data management (SDM) tools, etc., such that automation of the design and analysis of a material across multiple length scales is possible. In this paper, an executive summary of the NASA GRC ICME Schema for materials information management is presented. The database best practices and schema design philosophy specifically for ICME materials data management and an overview description of each element in the schema is given, along with its associated role in an ICME workflow. Additionally, auxiliary tools that interact with the database and provide judicious automation with regards to importing, exporting, and analyzing materials data are presented. Such tools are critical to an ICME ecosystem, not only for their role in enabling optimization, but also in relieving users of tedious manual tasks, thus helping to promote adoption and combat the cultural challenges organizations face in enabling ICME.

Materials↗

Automatic Debugging Support for UML Designs

Design of large software systems requires rigorous application of software engineering methods covering all phases of the software process. Debugging during the early design phases is extremely important, because late bug-fixes are expensive. In this paper, we describe an approach which facilitates debugging of UML requirements and designs. The Unified Modeling Language (UML) is a set of notations for object-orient design of a software system. We have developed an algorithm which translates requirement specifications in the form of annotated sequence diagrams into structured statecharts. This algorithm detects conflicts between sequence diagrams and inconsistencies in the domain knowledge. After synthesizing statecharts from sequence diagrams, these statecharts usually are subject to manual modification and refinement. By using the "backward" direction of our synthesis algorithm. we are able to map modifications made to the statechart back into the requirements (sequence diagrams) and check for conflicts there. Fed back to the user conflicts detected by our algorithm are the basis for deductive-based debugging of requirements and domain theory in very early development stages. Our approach allows to generate explanations oil why there is a conflict and which parts of the specifications are affected.

Schumann, Johann↗

Development of the platelet micro-orifice injector

For some time to come, liquid rocket engines will continue to provide the primary means of propulsion for space transportation. The injector represents a key to the optimization of engine and system performance. The present investigation is concerned with a unique injector design and fabrication process which has demonstrated performance capabilities beyond that achieved with more conventional approaches. This process, which is called the 'platelet process', makes it feasible to fabricate injectors with a pattern an order of magnitude finer than that obtainable by drilling. The fine pattern leads to an achievement of high combustion efficiencies. Platelet injectors have been identified as one of the significant technology advances contributing to the feasibility of advanced dual-fuel booster engines. Platelet injectors are employed in the Space Shuttle Orbit Maneuvering System (OMS) engines. Attention is given to injector design theory as it relates to pattern fineness, a description of platelet injectors, and test data obtained with three different platelet injectors.

La Botz, R. J.↗

The role of the host in a cooperating mainframe and workstation environment, volumes 1 and 2

In recent years, advancements made in computer systems have prompted a move from centralized computing based on timesharing a large mainframe computer to distributed computing based on a connected set of engineering workstations. A major factor in this advancement is the increased performance and lower cost of engineering workstations. The shift to distributed computing from centralized computing has led to challenges associated with the residency of application programs within the system. In a combined system of multiple engineering workstations attached to a mainframe host, the question arises as to how does a system designer assign applications between the larger mainframe host and the smaller, yet powerful, workstation. The concepts related to real time data processing are analyzed and systems are displayed which use a host mainframe and a number of engineering workstations interconnected by a local area network. In most cases, distributed systems can be classified as having a single function or multiple functions and as executing programs in real time or nonreal time. In a system of multiple computers, the degree of autonomy of the computers is important; a system with one master control computer generally differs in reliability, performance, and complexity from a system in which all computers share the control. This research is concerned with generating general criteria principles for software residency decisions (host or workstation) for a diverse yet coupled group of users (the clustered workstations) which may need the use of a shared resource (the mainframe) to perform their functions.

Kusmanoff, Antone↗

Techniques for optimizing human-machine information transfer related to real-time interactive display systems

In recent years the needs of ground-based researcher-analysts to access real-time engineering data in the form of processed information has expanded rapidly. Fortunately, the capacity to deliver that information has also expanded. The development of advanced display systems is essential to the success of a research test activity. Those developed at the National Aeronautics and Space Administration (NASA), Western Aeronautical Test Range (WATR), range from simple alphanumerics to interactive mapping and graphics. These unique display systems are designed not only to meet basic information display requirements of the user, but also to take advantage of techniques for optimizing information display. Future ground-based display systems will rely heavily not only on new technologies, but also on interaction with the human user and the associated productivity with that interaction. The psychological abilities and limitations of the user will become even more important in defining the difference between a usable and a useful display system. This paper reviews the requirements for development of real-time displays; the psychological aspects of design such as the layout, color selection, real-time response rate, and interactivity of displays; and an analysis of some existing WATR displays.

Granaas, Michael M.↗