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.
Nuclear science and nuclear power systems engineering - IEEE Conference, San Francisco, October 1969
The education of system engineers with emphasis on designing systems for space applications is discussed. System engineers determine the functional requirements, performance needs, and implementation procedures for proposed systems and their education is based on aeronautics and mathematics. Recommendations from industry for improving the curriculum of system engineers at the undergraduate and graduate levels are provided. The assistance provided by companies to the education of system engineers is examined.
Systems engineering as applied to space exploration
There has been much discussion of late in the NASA systems engineering community about the fact that systems engineering cannot be just about process and technical disciplines. The belief is that there is both an art and science to systems engineering, and that both aspects are necessary for designing and implementing a successful system or mission. How does one go about differentiating between and characterizing these two aspects? Some say that the art of systems engineering is about designing systems that not only function well, but that are also elegant, beautiful and engaging. What does that mean? How can you tell when a system has been designed with that holistic "art" component? This paper attempts to answer these questions by exploring various ways of looking at the Art and Science of Systems Engineering.
This paper investigates the oversimplification of the inherently complex systems engineering process in space life support. The standard systems engineering process steps are described. The International Space Station (ISS) life support system is explained with its goals and performance criteria. Although it is not usually emphasized, the essential function of developing a hierarchy of systems and subsystems is to simplify the design process. The System Complexity Metric (SCM) shows how this di-vide-and-conquer approach also reduces the system complexity. The complete systems engineering process has many detailed steps. It is often simplified because of the effort required and the human limitations on working memory and decision span. Systems analysis demands slow, logical, and fo-cused thinking but is often bypassed in favor of quick, intuitive, subconscious “gut feel.” A study of 100 system designs found examples of 12 specific mental mistakes, such as ignoring stakeholder needs, and these mistakes are essentially oversimplifications of the systems engineering process. An analysis of space life support goals, options, criteria, and processes found 11 examples of oversimplifications in systems engineering, such as neglecting safety and cost. All these 11 oversimplifications could be traced to one or more of the 12 previously identified mental mistakes or other well-known ones, such as ig-noring sunk costs. Oversimplification of the systems engineering process is rarely noticed but is a common and harmful problem. A study of failures in 50 different space systems found that problems in systems engineering caused failures and often led to errors in design, development, and test that further contributed to failure. It seems that more diligent systems engineering could prevent many project problems and failures, but projects seem to be more guided by “gut feel” based on tradition, authority, and consensus than on the logical, rational systems engineering approach.
Second Chance (SECC) was a bare bones version of Mars Science Laboratory's (MSL) Entry Descent & Landing (EDL) flight software that ran on Curiosity's backup computer, which could have taken over swiftly in the event of a reset of Curiosity's prime computer, in order to land her safely on Mars. Without SECC, a reset of Curiosity's prime computer would have lead to catastrophic mission failure. Even though a reset of the prime computer never occurred, SECC had the important responsibility as EDL's guardian angel, and this responsibility would not have seen such success without unparalleled systems engineering. This paper will focus on the systems engineering behind SECC: Covering a brief overview of SECC's design, the intense schedule to use SECC as a backup system, the verification and validation of the system's "Do No Harm" mandate, the system's overall functional performance, and finally, its use on the fateful day of August 5th, 2012.
Second Chance (SECC) was a bare bones version of Mars Science Laboratory’s (MSL) Entry Descent & Landing (EDL) flight software that ran on Curiosity’s backup computer, which could have taken over swiftly in the event of a reset of Curiosity’s prime computer, in order to land her safely on Mars. Without SECC, a reset of Curiosity’s prime computer would have lead to catastrophic mission failure. Even though a reset of the prime computer never occurred, SECC had the important responsibility as EDL’s guardian angel, and this responsibility would not have seen such success without unparalleled systems engineering. This paper will focus on the systems engineering behind SECC: Covering a brief overview of SECC’s design, the intense schedule to use SECC as a backup system, the verification and validation of the system’s “Do No Harm” mandate, the system’s overall functional performance, and finally, its use on the fateful day of August 5th, 2012.
The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.
The National Aeronautics and Space Administration (NASA) delivers space transportation solutions for America's complex missions, ranging from scientific payloads that expand knowledge, such as the Hubble Space Telescope, to astronauts and lunar rovers destined for voyages to the Moon. Currently, the venerable Space Shuttle, which has been in service since 1981, provides U.S. capability for both crew and cargo to low-Earth orbit to construct the International Space Station, before the Shuttle is retired in 2010, as outlined in the 2006 NASA Strategic Plan. I In the next decade, NASA will replace this system with a duo of launch vehicles: the Ares I Crew Launch Vehicle/Orion Crew Exploration Vehicle and the Ares V Cargo Launch Vehicle/Altair Lunar Lander. The goals for this new system include increased safety and reliability, coupled with lower operations costs that promote sustainable space exploration over a multi-decade schedule. This paper will provide details of the in-house systems engineering and vehicle integration work now being performed for the Ares I and planned for the Ares V. It will give an overview of the Ares I system-level test activities, such as the ground vibration testing that will be conducted in the Marshall Center's Dynamic Test Stand to verify the integrated vehicle stack's structural integrity against predictions made by modern modeling and simulation analysis. It also will give information about the work in progress for the Ares I-X developmental test flight planned in 2009 to provide key data before the Ares I Critical Design Review. Activities such as these will help prove and refine mission concepts of operation, while supporting the spectrum of design and development tasks being performed by Marshall's Engineering Directorate, ranging from launch vehicles and lunar rovers to scientific spacecraft and associated experiments. Ultimately, the work performed will lead to the fielding of a robust space transportation solution that will carry international explorers and essential payloads for sustainable scientific discovery beyond planet Earth.
The Data Engineering System (DES) is a computer-based system that organizes technical data and provides automated mechanisms for storage, retrieval, and engineering analysis. The DES combines the benefits of a structured data base system with automated links to large-scale analysis codes. While the DES provides the user with many of the capabilities of a computer-aided design (CAD) system, the systems are actually quite different in several respects. A typical CAD system emphasizes interactive graphics capabilities and organizes data in a manner that optimizes these graphics. On the other hand, the DES is a computer-aided engineering system intended for the engineer who must operationally understand an existing or planned design or who desires to carry out additional technical analysis based on a particular design. The DES emphasizes data retrieval in a form that not only provides the engineer access to search and display the data but also links the data automatically with the computer analysis codes.
During the Formulation phases of the NASA Project Life Cycle, communication systems engineers are responsible for designing space communication links and analyzing their performance to ensure that the proposed communication architecture is capable of satisfying high-level mission requirements. Senior engineers with extensive experience in communications systems perform these activities. However, the increasing complexity of space systems coupled with the current shortage of communications systems engineers has led to an urgent need for expedited training of new systems engineers. A pilot program, in which college-bound high school and undergraduate students studying various engineering disciplines are immersed in NASA s systems engineering practices, was conceived out of this need. This rapid summerlong training approach is feasible because of the availability of advanced software and technology tools and the students inherent ability to operate such tools. During this pilot internship program, a team of college-level and recently-hired engineers configured and utilized various software applications in the design and analysis of communication links for a plausible lunar sortie mission. The approach taken was to first design the direct-to-Earth communication links for the lunar mission elements, then to design the links between lunar surface and lunar orbital elements. Based on the data obtained from these software applications, an integrated communication system design was realized and the students gained valuable systems engineering knowledge. This paper describes this approach to rapidly training college-bound high school and undergraduate engineering students from various disciplines in NASA s systems engineering practices and tools. A summary of the potential use of NASA s emerging systems engineering internship program in broader applications is also described.
Model-Based Systems Engineering (MBSE) promotes increased consistency between a system's design and its design documentation through the use of an object-oriented system model. The creation of this system model facilitates data presentation by providing a mechanism from which information can be extracted by automated manipulation of model content. Existing MBSE tools enable model creation, but are often too complex for the unfamiliar model viewer to easily use. These tools do not yet provide many opportunities for easing into the development and use of a system model when system design documentation already exists. This study creates a Systems Modeling Language (SysML) Document Traceability Framework (SDTF) for integrating design documentation with a system model, and develops an Interactive Visualization Engine for SysML Tools (InVEST), that exports consistent, clear, and concise views of SysML model data. These exported views are each meaningful to a variety of project stakeholders with differing subjects of concern and depth of technical involvement. InVEST allows a model user to generate multiple views and reports from a MBSE model, including wiki pages and interactive visualizations of data. System data can also be filtered to present only the information relevant to the particular stakeholder, resulting in a view that is both consistent with the larger system model and other model views. Viewing the relationships between system artifacts and documentation, and filtering through data to see specialized views improves the value of the system as a whole, as data becomes information
The design of large-scale complex engineered systems (LaCES) such as an aircraft is inherently interdisciplinary. Multiple engineering disciplines, drawing from a team of hundreds to thousands of engineers and scientists, are woven together throughout the research, development, and systems engineering processes to realize one system. Though research and development (R&D) is typically focused in single disciplines, the interdependencies involved in LaCES require interdisciplinary R&D efforts. This study investigates the interdisciplinary interactions that take place during the R&D and early conceptual design phases in the design of LaCES. Our theoretical framework is informed by both engineering practices and social science research on complex organizations. This paper provides preliminary perspective on some of the organizational influences on interdisciplinary interactions based on organization theory (specifically sensemaking), data from a survey of LaCES experts, and the authors experience in the research and design. The analysis reveals couplings between the engineered system and the organization that creates it. Survey respondents noted the importance of interdisciplinary interactions and their significant benefit to the engineered system, such as innovation and problem mitigation. Substantial obstacles to interdisciplinarity are uncovered beyond engineering that include communication and organizational challenges. Addressing these challenges may ultimately foster greater efficiencies in the design and development of LaCES and improved system performance by assisting with the collective integration of interdependent knowledge bases early in the R&D effort. This research suggests that organizational and human dynamics heavily influence and even constrain the engineering effort for large-scale complex systems.
JPL is implementing an initiative to significantly upgrade our systems engineering capabilities. This Systems Engineering Upgrade Initiative [SUI] has been authorized by the highest level technical management body of JPL and is sponsored with internal funds. The SUI objective is to upgrade system engineering at JPL to a level that is world class, professional and efficient compared to the FY04/05 baseline. JPL system engineering, along with the other engineering disciplines, is intended to support optimum designs; controlled and efficient implementations; and high quality, reliable, cost effective products. SUI technical activities are categorized into those dealing with people, process and tools. The purpose of this paper is to describe the rationale, objectives/plans and current status of the JPL SUI.
Operating a gaseous fuel engine system includes combusting a mixture containing a gaseous hydrogen fuel and air in a cylinder of an engine, varying an operating parameter of the engine to which a crown surface temperature of a piston within the cylinder is responsive, and populating a temperature model based on a value of the varied operating parameter. Operating a gaseous fuel engine system further includes operating an oil spray apparatus to spray oil onto the piston based on the populated temperature model, and maintaining the crown surface temperature of the piston between a high temperature limit and a pre-ignition mitigation temperature limit based on the operating of the oil spray apparatus. Related apparatus and control logic is also disclosed.
The basic elements of a systems engineering process are given along with a detailed description of what the safety system requires from the systems engineering process. Also discussed is the safety that the system provides to other subfunctions of systems engineering.
NASA's Marshall Space Flight Center (MSFC) management feels that sound system engineering practices are essential for successful project management, NASA studies have concluded that recent project failures could be attributed in part to inadequate systems engineering. A recent survey of MSFC project managers and system engineers' resulted in the recognition of a need for training in Systems Engineering Practices, particularly as they relate to MSFC projects. In response to this survey, an internal pilot short-course was developed to reinforce accepted practices for system engineering at MSFC. The desire of the MSFC management is to begin with in-house training and offer additional educational opportunities to reinforce sound system engineering principles to the more than 800 professionals who are involved with system engineering and project management. A Systems Engineering Development Plan (SEDP) has been developed to address the longer-term systems engineering development needs of MSFC. This paper describes the survey conducted and the training course that was developed in response to that survey.
NASA’s Model-Based Systems Engineering (MBSE) Infusion and Modernization Initiative (MIAMI) chartered a strategy group comprising early to mid-career NASA subject matter experts with diverse experiences to look into the future of systems engineering at NASA. The purpose of the group was to provide a vision for the future state of systems engineering practices and to develop a strategic plan to enable the evolution of the art up to 20 years in the future. The group used a design thinking approach to gather ideas and obtained insight into current engineering processes and domain outlook by interviewing engineers of varying expertise and experiences who had worked on teams of different sizes for missions large and small. The group built a roadmap to highlight future needs, projected capabilities, and technology and competency gaps and developed a strategic plan to ensure the expedient introduction of these capabilities. The resulting strategic plan recommends capability development and workforce strategies and provides guidance for Agency-wide SE policy. Artifacts, details, and raw data from the strategy team’s work are contained in NASA/TM-20205002911/SUPPL, Strategic Perspectives on the Future of Systems Engineering at NASA: Supplemental Information: Appendixes A to K.