New horizons in systems engineering
Explore the source record for details and available documents.
SEARCH · Search NASA
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.
Explore the source record for details and available documents.
One of NASA's goals within human exploration is to determine how to get humans to Mars safely and to live and work on the Martian surface. To accomplish this goal, several smaller missions act as stepping-stones to the larger end goal. NASA uses these smaller missions to develop new technologies and learn about how to survive outside of Low Earth Orbit for long periods. Additionally, keeping a cadence of these missions allows the team to maintain proficiency in the complex art of bringing spacecraft to fruition. Many of these smaller missions are robotic in nature and have smaller timescales, whereas there are others that involve crew and have longer mission timelines. Given the timelines associated with these various missions, different levels of risk and rigor need to be implemented to be more in line with what is appropriate for the mission. Thus, NASA has four different classifications that range from Class A to Class D based on the mission details. One of these projects is the Resource Prospector (RP) Mission, which is a multi-center and multi-institution collaborative project to search for volatiles in the polar regions of the Moon. The RP mission is classified as a Class D mission and as such, has the opportunity to more tightly manage, and therefore accept, greater levels of risk. The requirements for Class D missions were at the forefront of the design and thus presented unique challenges in vehicle development and systems engineering processes. This paper will discuss the systems engineering process at NASA and how that process is tailored for Class D missions, specifically the RP mission.
In 1995, The University of Texas at El Paso (UTEP) responded to the suggestion of NASA Jet Propulsion Laboratory (NASA JPL) to form a consortium comprised of California State University at Los Angeles (CSULA), North Carolina Agricultural and Technical University (NCAT), and UTEP from which developed the Minority Universities Systems Engineering (MUSE) Program. The mission of this consortium is to develop a unique position for minority universities in providing the nation's future system architects and engineers as well as enhance JPL's system design capability. The goals of this collaboration include the development of a system engineering curriculum which includes hands-on project engineering and design experiences. UTEP is in a unique position to take full advantage of this program since UTEP has been named a Model Institution for Excellence (MIE) by the National Science Foundation. The purpose of MIE is to produce leaders in Science, Math, and Engineering. Furthermore, UTEP has also been selected as the site for two new centers including the Pan American Center for Earth and Environmental Sciences (PACES) directed by Dr. Scott Starks and the FAST Center for Structural Integrity of Aerospace Systems directed by Dr. Roberto Osegueda. The UTEP MUSE Program operates under the auspices of the PACES Center.
The currently common sequential design process for engineering systems is likely to lead to suboptimal designs. Recently developed decomposition methods offer an alternative for coming closer to optimum by breaking the large task of system optimization into smaller, concurrently executed and, yet, coupled tasks, identified with engineering disciplines or subsystems. The hierarchic and non-hierarchic decompositions are discussed and illustrated by examples. An organization of a design process centered on the non-hierarchic decomposition is proposed.
The currently common sequential design process for engineering systems is likely to lead to suboptimal designs. Recently developed decomposition methods offer an alternative for coming closer to optimum by breaking the large task of system optimization into smaller, concurrently executed and, yet, coupled tasks, identified with engineering disciplines or subsystems. The hierarchic and non-hierarchic decompositions are discussed and illustrated by examples. An organization of a design process centered on the non-hierarchic decomposition is proposed.
This paper examines four primary methods of working across disciplines during R&D and early design of large-scale complex engineered systems such as aerospace systems. A conceptualized framework, called the Combining System Elements framework, is presented to delineate several aspects of cross-discipline and system integration practice. The framework is derived from a theoretical and empirical analysis of current work practices in actual operational settings and is informed by theories from organization science and engineering. The explanatory framework may be used by teams to clarify assumptions and associated work practices, which may reduce ambiguity in understanding diverse approaches to early systems research, development and design. The framework also highlights that very different engineering results may be obtained depending on work practices, even when the goals for the engineered system are the same.
The Soil Moisture Active Passive (SMAP) mission, scheduled for launch by the end of 2014, is being developed to measure the soil moisture and soil freeze/thaw state on a global scale over a three-year period. The accuracy, resolution, and global coverage of SMAP measurements are invaluable across many science and applications disciplines including hydrology, climate, carbon cycle, and the meteorological, environment, and ecology applications communities. The SMAP observatory is composed of a despun bus and a spinning instrument platform that includes both a deployable 6 meter aperture low structural frequency Astromesh reflector and a spin control system. The instrument section has engendered challenging mechanical system issues associated with the antenna deployment, flexible antenna pointing in the context of a multitude of disturbances, spun section mass properties, spin control system development, and overall integration with the flight system on both mechanical and control system levels. Moreover, the multitude of organizations involved, including two major vendors providing the spin subsystem and reflector boom assembly plus the flight system mechanical and guidance, navigation, and control teams, has led to several unique system engineering challenges. Capturing the key physics associated with the function of the flight system has been challenging due to the many different domains that are applicable. Key interfaces and operational concepts have led to complex negotiations because of the large number of organizations that integrate with the instrument mechanical system. Additionally, the verification and validation concerns associated with the mechanical system have had required far-reaching involvement from both the flight system and other subsystems. The SMAP instrument mechanical systems engineering issues and their solutions are described in this paper.
The purpose of the Preliminary Research in AerodyNamicDesign to Lower Drag (PRANDTL-D) project is to show that birds fly using a "bell" shaped spanload rather than using an elliptical shaped spanload and to demonstrate the extensive benefits of this alternative spanload. This validation is done by flying a research glider with a twenty five foot wingspan that collects a range of parameters in flight. To ensure the data collection computers and suite of sensors work together and mesh well with the aircraft, systems engineering principles are applied. Needs for new one-off parts require a systems engineering approach as all the criteria of the plane, such as aerodynamics, structures, and avionics, must be taken into account when making decisions. The result of this approach were effective solutions that had a minimal negative impact on other systems that were not related to the original problem.
Work at the JPL in systems engineering is surveyed with the emphasis on practical experience with large hardware and software systems. Systems concepts in lunar and planetary projects, in the Morgantown project, and in the Urban Health Systems Task are discussed. Goal definition, problem statement, objective and criteria development, and synthesis, analysis, selection and implementation of systems are considered as successive steps in the optimization of the overall system.-
An added challenge for the designers of large scale systems such as Space Station Freedom is the appropriate incorporation of intelligent system technology (artificial intelligence, expert systems, knowledge-based systems, etc.) into their requirements and design. This presentation will describe a view of systems engineering which successfully addresses several aspects of this complex problem: design of large scale systems, design with requirements that are so complex they only completely unfold during the development of a baseline system and even then continue to evolve throughout the system's life cycle, design that involves the incorporation of new technologies, and design and development that takes place with many players in a distributed manner yet can be easily integrated to meet a single view of the requirements. The first generation of this methodology was developed and evolved jointly by ISX and the Lockheed Aeronautical Systems Company over the past five years on the Defense Advanced Research Projects Agency/Air Force Pilot's Associate Program, one of the largest, most complex, and most successful intelligent systems constructed to date. As the methodology has evolved it has also been applied successfully to a number of other projects. Some of the lessons learned from this experience may be applicable to Freedom.
Feasibility analyses and systems engineering studies for a 20,000 tons per day medium Btu (MBG) coal gasification plant to be built by TVA in Northern Alabama were conducted. Major objectives were as follows: (1) provide design and cost data to support the selection of a gasifier technology and other major plant design parameters, (2) provide design and cost data to support alternate product evaluation, (3) prepare a technology development plan to address areas of high technical risk, and (4) develop schedules, PERT charts, and a work breakdown structure to aid in preliminary project planning. Volume one contains a summary of gasification system characterizations. Five gasification technologies were selected for evaluation: Koppers-Totzek, Texaco, Lurgi Dry Ash, Slagging Lurgi, and Babcock and Wilcox. A summary of the trade studies and cost sensitivity analysis is included.
NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine(OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging f rom STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.
NASA's Orion spacecraft transports humans and cargo into cislunar space for the Artemis program. The European Service Module (ESM), supplied by ESA and its European industry partners, provides Orion with power and in-space propulsion. The Orion-ESM propulsion system is a bipropellant hypergolic propulsion system using monomethyl hydrazine (MMH) and nitrogen tetroxide (MON-3). Primary translational propulsion is provided by the Orbital Maneuvering System Engine (OMS-E), with backup translational propulsion provided by eight Auxiliary thrusters (AUX). Attitude control and small translational maneuvers are provided by twenty-four Reaction Control System (RCS) engines. The 2022 Artemis I mission was the first integrated flight test of the Orion-ESM spacecraft and its propulsion system. The OMS-E used on Artemis I was a refurbished Space Shuttle OMS-E that previously flew on nineteen missions ranging from STS-41G in 1984 to STS-112 in 2002. The Auxiliary engines are modified Aerojet Rocketdyne R4D-11 engines produced specifically for the Orion program. The RCS engines are Ariane Group engines originally used for the Automated Transfer Vehicle (ATV) program. This paper will discuss the unique operational requirements for each engine on Orion and the development and qualification effort sat both the engine and system-level that were completed to enable a successful Artemis I mission. Next the paper will evaluate the in-f light performance of the engines during the Artemis I mission showing nominal performance as expected. Additionally, comparisons to models will be presented showing very good correlation. Finally, the paper will address the plan for the engines on future Orion missions and the evolution of the system operation.
This paper is organized into four parts. In the Gestation Phase, I describe the process of starting a new mission and establishing its rough boundaries. Next I show how the scientific experiments are selected. Then we enter the Preliminary Design Phase, where we incorporate the scientist's instruments into the systems engineering process. Finally, I show how the Preliminary Design Review (PDR) assures NASA management and the scientists that the scientific requirements have been incorporated into the systems engineering process to everyone's satisfaction.
This is a report from the CEOS Systems Engineering Office for the Strategic Implementation Team Meeting
A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.
Pattern Language describes the morphology and functionality of a system in the absence of design particulars. Harnessing this capability will provide the Systems Engineering discipline a means of managing the development of increasingly complex systems with increasingly distributed design teams while capturing and retaining knowledge for future generations. Pattern Language is a syntax for describing, and structurally relating, design patterns. Design patterns contextually describe the application of domain knowledge in the engineered solution to the force balance problem. The parallels between pattern recognition and application, as a fundamental stage of human learning, and pattern observation within a complex system, suggests pattern language may be a valuable tool in the capture and dissemination of knowledge. Pattern application has enjoyed considerable study over the last several decades, however much of this work has focused on the replication of design particulars. This work returns to the roots of Pattern Language and explores the utility of patterns as an architectural description and guide, and knowledge capture method, for complex system development beginning with the identification of a time proven design pattern.
This report has been developed by the National Aeronautics and Space Administration (NASA) Exploration Systems Mission Directorate (ESMD) Risk Management team in close coordination with the Systems Engineering Team. This document provides a point-in-time, cumulative, summary of key lessons learned derived from the SE RFP Development process. Lessons learned invariably address challenges and risks and the way in which these areas have been addressed. Accordingly the risk management thread is woven throughout the document.