Results for “Process Systems Engineering” — Page 23

NASA NTRS1991

Intelligent systems/software engineering methodology - A process to manage cost and risk

A systems development methodology is discussed that has been successfully applied to the construction of a number of intelligent systems. This methodology is a refinement of both evolutionary and spiral development methodologies. It is appropriate for development of intelligent systems. The application of advanced engineering methodology to the development of software products and intelligent systems is an important step toward supporting the transition of AI technology into aerospace applications. A description of the methodology and the process model from which it derives is given. Associated documents and tools are described which are used to manage the development process and record and report the emerging design.

Friedlander, Carl↗

NASA NTRS2010

General Pressurization Model in Simscape

System integration is an essential part of the engineering design process. The Ares I Upper Stage (US) is a complex system which is made up of thousands of components assembled into subsystems including a J2-X engine, liquid hydrogen (LH2) and liquid oxygen (LO2) tanks, avionics, thrust vector control, motors, etc. System integration is the task of connecting together all of the subsystems into one large system. To ensure that all the components will "fit together" as well as safety and, quality, integration analysis is required. Integration analysis verifies that, as an integrated system, the system will behave as designed. Models that represent the actual subsystems are built for more comprehensive analysis. Matlab has been an instrument widely use by engineers to construct mathematical models of systems. Simulink, one of the tools offered by Matlab, provides multi-domain graphical environment to simulate and design time-varying systems. Simulink is a powerful tool to analyze the dynamic behavior of systems over time. Furthermore, Simscape, a tool provided by Simulink, allows users to model physical (such as mechanical, thermal and hydraulic) systems using physical networks. Using Simscape, a model representing an inflow of gas to a pressurized tank was created where the temperature and pressure of the tank are measured over time to show the behavior of the gas. By further incorporation of Simscape into model building, the full potential of this software can be discovered and it hopefully can become a more utilized tool.

Servin, Mario↗

NASA NTRSDate not supplied

Ground Test Technology Demonstration for Nuclear Thermal Propulsion Engines

Nuclear Thermal Propulsion (NTP) engines have been deemed a key technology to enable human missions to Mars due to their high efficiency, also known as specific impulse (Isp). Ground testing the NTP engine is critical in maturing the technology and increasing the design’s Technology Readiness Level (TRL), thus mitigating risk from NTP engine performance/operations. NTP engine development began with open-air ground testing through the Rover/NERVA program back in the 1960s when regulatory requirements were not as stringent as they are today. Due to the formation of regulatory bodies, increase in oversight and environmental requirements, the exhaust gas released from NTP engines must be captured or processed to gain approval in the case that the exhaust gas contains fission products from the nuclear fuel elements within the reactor. Ground test campaigns following Rover/NERVA focused on the certification of a full scale NTP engine, which led to exhaust processing systems such as the Rocket Exhaust Capture System (RECS) and Real Time (RT) exhaust processing. These systems were deemed favorable for regulatory compliance but have a high initial investment cost. Reassurance on the feasibility of ground testing and the NTP engine technology likely need to be achieved before NASA invests in these systems. Recently the objectives for NTP engine ground testing have shifted from certification testing of a full scale engine to demonstration testing of a subscale engine. The shift to demonstration testing allows for a shorter testing duration and a lower operational thrust (for demo testing purposes only) to demonstrate the NTP engine (5k-12.5k lbf). Due to these factors, the infrastructure, consumables, total footprint, and exhaust system complexity are able to be drastically reduced, thus reducing cost significantly. The High-pressure Exhaust Capture System (HECS) concept was designed for a NTP engine ground test demonstration. The HECS concept greatly reduces cost compared to previous concepts and suggests favorable regulatory acceptance due to its ability to capture all of the exhaust gas from the NTP engine.

Nuclear Thermal Propulsion↗

NASA NTRSDate not supplied

Nuclear Thermal Propulsion Engine Technology Demonstration Testing

Nuclear Thermal Propulsion (NTP) engines have been deemed a key technology to enable human missions to Mars due to their high efficiency, also known as specific impulse (Isp). Ground testing the NTP engine is critical in maturing the technology and increasing the design’s Technology Readiness Level (TRL), thus mitigating risk from NTP engine performance/operations. NTP engine development began with open-air ground testing through the Rover/NERVA program back in the 1960s when regulatory requirements were not as stringent as they are today. Due to the formation of regulatory bodies, increase in oversight and environmental requirements, the exhaust gas released from NTP engines must be captured or processed to gain approval in the case that the exhaust gas contains fission products from the nuclear fuel elements within the reactor. Ground test campaigns following Rover/NERVA focused on the certification of a full scale NTP engine, which led to exhaust processing systems such as the Rocket Exhaust Capture System (RECS) and Real Time (RT) exhaust processing. These systems were deemed favorable for regulatory compliance but have a high initial investment cost. Reassurance on the feasibility of ground testing and the NTP engine technology likely need to be achieved before NASA invests in these systems. Recently the objectives for NTP engine ground testing have shifted from certification testing of a full scale engine to demonstration testing of a subscale engine. The shift to demonstration testing allows for a shorter testing duration and a lower operational thrust (for demo testing purposes only) to demonstrate the NTP engine (5k-12.5k lbf). Due to these factors, the infrastructure, consumables, total footprint, and exhaust system complexity are able to be drastically reduced, thus reducing cost significantly. The High-pressure Exhaust Capture System (HECS) concept was designed for a NTP engine ground test demonstration. The HECS concept greatly reduces cost compared to previous concepts and suggests favorable regulatory acceptance due to its ability to capture all of the exhaust gas from the NTP engine.

Nuclear Thermal Propulsion↗

NASA NTRS1964

On certain functionals of normal processes Technical report no. 1

Probabilistic modeling and stochastic process investigations to provide measures of quality of performance and reliability for systems engineering - Chebyshev approximation

RELIABILITY↗

NASA NTRS1999

Aerospace Engineering Systems

Continuous improvement of aerospace product development processes is a driving requirement across much of the aerospace community. As up to 90% of the cost of an aerospace product is committed during the first 10% of the development cycle, there is a strong emphasis on capturing, creating, and communicating better information (both requirements and performance) early in the product development process. The community has responded by pursuing the development of computer-based systems designed to enhance the decision-making capabilities of product development individuals and teams. Recently, the historical foci on sharing the geometrical representation and on configuration management are being augmented: Physics-based analysis tools for filling the design space database; Distributed computational resources to reduce response time and cost; Web-based technologies to relieve machine-dependence; and Artificial intelligence technologies to accelerate processes and reduce process variability. Activities such as the Advanced Design Technologies Testbed (ADTT) project at NASA Ames Research Center study the strengths and weaknesses of the technologies supporting each of these trends, as well as the overall impact of the combination of these trends on a product development event. Lessons learned and recommendations for future activities will be reported.

VanDalsem, William R.↗

NASA NTRS1993

Advanced rocket propulsion

Existing NASA research contracts are supporting development of advanced reinforced polymer and metal matrix composites for use in liquid rocket engines of the future. Advanced rocket propulsion concepts, such as modular platelet engines, dual-fuel dual-expander engines, and variable mixture ratio engines, require advanced materials and structures to reduce overall vehicle weight as well as address specific propulsion system problems related to elevated operating temperatures, new engine components, and unique operating processes. High performance propulsion systems with improved manufacturability and maintainability are needed for single stage to orbit vehicles and other high performance mission applications. One way to satisfy these needs is to develop a small engine which can be clustered in modules to provide required levels of total thrust. This approach should reduce development schedule and cost requirements by lowering hardware lead times and permitting the use of existing test facilities. Modular engines should also reduce operational costs associated with maintenance and parts inventories.

Obrien, Charles J.↗

NASA NTRS2004

Engineering Complex Embedded Systems with State Analysis and the Mission Data System

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer s intent, potentially leading to software errors. This problem is addressed by a systems engineering methodology called State Analysis, which provides a process for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using State Analysis and how these requirements inform the design of the system software, using representative spacecraft examples.

mission data systems↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗

NASA NTRS1981

Relations between information system engineering and software engineering

This paper examines some of the relations between information system engineering and software engineering. A model for the development process of an information system is presented that focuses on problems common to both disciplines. The concepts of complexity, multiplicity of view, distortion in communication, and concurrency and iteration in implementation are treated. A set of design constructs for the description of an information system is presented. The role of project management is treated. The issue of how to characterize requirements analysis is answered by making it a design activity from the point of view of a user of the product system.

Callender, E. D.↗

NASA NTRS1973

Report to the administrator by the NASA Aerospace Safety Advisory Panel on the Skylab program. Volume 1: Summary report

Contractor and NASA technical management for the development and manufacture of the Skylab modules is reviewed with emphasis on the following management controls: configuration and interface management; vendor control; and quality control of workmanship. A review of the modified two-stage Saturn V launch vehicle which focused on modifications to accommodate the Skylab payload; resolution of prior flight anomalies; and changes in personnel and management systems is presented along with an evaluation of the possible age-life and storage problems for the Saturn 1-B launch vehicle. The NASA program management's visibility and control of contractor operations, systems engineering and integration, the review process for the evaluation of design and flight hardware, and the planning process for mission operations are investigated. It is concluded that the technical management system for development and fabrication of the modules, spacecraft, and launch vehicles, the process of design and hardware acceptance reviews, and the risk assessment activities are satisfactory. It is indicated that checkout activity, integrated testing, and preparations for and execution of mission operation require management attention.

Source record↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗

NASA NTRS2002

Comparisons of Kinematics and Dynamics Simulation Software Tools

Kinematic and dynamic analyses for moving bodies are essential to system engineers and designers in the process of design and validations. 3D visualization and motion simulation plus finite element analysis (FEA) give engineers a better way to present ideas and results. Marshall Space Flight Center (MSFC) system engineering researchers are currently using IGRIP from DELMIA Inc. as a kinematic simulation tool for discrete bodies motion simulations. Although IGRIP is an excellent tool for kinematic simulation with some dynamic analysis capabilities in robotic control, explorations of other alternatives with more powerful dynamic analysis and FEA capabilities are necessary. Kinematics analysis will only examine the displacement, velocity, and acceleration of the mechanism without considering effects from masses of components. With dynamic analysis and FEA, effects such as the forces or torques at the joint due to mass and inertia of components can be identified. With keen market competition, ALGOR Mechanical Event Simulation (MES), MSC visualNastran 4D, Unigraphics Motion+, and Pro/MECHANICA were chosen for explorations. In this study, comparisons between software tools were presented in terms of following categories: graphical user interface (GUI), import capability, tutorial availability, ease of use, kinematic simulation capability, dynamic simulation capability, FEA capability, graphical output, technical support, and cost. Propulsion Test Article (PTA) with Fastrac engine model exported from IGRIP and an office chair mechanism were used as examples for simulations.

Yeu-Sheng Paul Shiue↗

NASA NTRS2006

Application of State Analysis and Goal-Based Operations to a MER Mission Scenario

State Analysis is a model-based systems engineering methodology employing a rigorous discovery process which articulates operations concepts and operability needs as an integrated part of system design. The process produces requirements on system and software design in the form of explicit models which describe the behavior of states and the relationships among them. By applying State Analysis to an actual MER flight mission scenario, this study addresses the specific real world challenges of complex space operations and explores technologies that can be brought to bear on future missions. The paper describes the tools currently used on a daily basis for MER operations planning and provides an in-depth description of the planning process, in the context of a Martian day's worth of rover engineering activities, resource modeling, flight rules, science observations, and more. It then describes how State Analysis allows for the specification of a corresponding goal-based sequence that accomplishes the same objectives, with several important additional benefits.

mission planning↗

NASA NTRS1989

Composite sizing and ply orientation for stiffness requirements using a large finite element structural model

A NASTRAN bulk dataset preprocessor was developed to facilitate the integration of filamentary composite laminate properties into composite structural resizing for stiffness requirements. The NASCOMP system generates delta stiffness and delta mass matrices for input to the flutter derivative program. The flutter baseline analysis, derivative calculations, and stiffness and mass matrix updates are controlled by engineer defined processes under an operating system called CBUS. A multi-layered design variable grid system permits high fidelity resizing without excessive computer cost. The NASCOMP system uses ply layup drawings for basic input. The aeroelastic resizing for stiffness capability was used during an actual design exercise.

Radovcich, N. A.↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Program Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the moon. This time, with the help of commercial and international partners, the program’s objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, more onboard systems autonomy and functionality will be needed to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with-audio, video, lighting, and crew controls. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program-especially crew controls which is the focus of this paper. How does NASA ensure crew controls are reliable to control complex systems and prevent a catastrophic event due to human error-especially when the astronauts could be physiologically and/or psychologically impaired? NASA’s approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls is through a holistic system engineering and Human System Integration methodology that embraces NASA’s Human-Rating Requirements-ensuring human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering, and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

Human-Rating↗

NASA NTRS2015

Decision Making and Communications Process Assessment of NASA Using Three Change Requests from the Space Launch System Program

This thesis investigated the communication and decision making process as part of the Systems Engineering practices at the NASA/Marshall Center to determine its level of effectiveness. Data was collected across three change requests to assess how decisions were made, how the decisions were communicated, and whether a process mattered in the formulation and dissemination of those decisions. Data results revealed the comprehensive decision making process for the technical change requests to be effective. Evidence revealed that the process was sufficiently tailored to accommodate the need of each individual technical change which promoted effective communication amongst the stakeholders in the formulation of the strategic decision recommendations elevated to upper management. However, data results also revealed the dissemination of the final decision and approval of the change requests from the higher organizational level down to all stakeholders was less effective. An establishment of a culmination meeting at the end of the change request decision process in which to close the communication loop with all entities would be beneficial.

Hicks, Karen Campbell↗

NASA NTRSDate not supplied

Discovering Digital Engineering Needs Through Human-Centered Approaches

Digital engineering has the power to transform organizations in profound ways, but digitizing legacy workflows and infusing new technologies into existing practices may not yield the intended results or address the underlying problems or bottlenecks. This paper describes the human-centered approaches used to understand stakeholder challenges and identify digital engineering needs during the design-build-test portion of the systems development lifecycle. Through a series of interactive stakeholder workshops and need-finding activities, key stakeholder needs were identified to help guide the integration of digital engineering technologies. The overarching need was for downstream system development steps to be considered further upstream in the project lifecycle in a manner that allows for proactive and interactive co-constructive idea exploration, problem resolution, and requirements considerations in a collective engagement with engineers and technicians from multiple disciplines to increase efficiency and reduce risks while offering opportunities to improve the final engineered system. Supporting this need was a wide-ranging desire from stakeholders for digital and non-digital support structures for efficient rapid iteration during system development. This work yielded several improvements for system development processes and for digital engineering infusion.

Human-centered Design↗