Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engineered systems”

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 1,567 records · Page 87
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

Executable Architecture Research at Old Dominion University

Executable Architectures allow the evaluation of system architectures not only regarding their static, but also their dynamic behavior. However, the systems engineering community do not agree on a common formal specification of executable architectures. To close this gap and identify necessary elements of an executable architecture, a modeling language, and a modeling formalism is topic of ongoing PhD research. In addition, systems are generally defined and applied in an operational context to provide capabilities and enable missions. To maximize the benefits of executable architectures, a second PhD effort introduces the idea of creating an executable context in addition to the executable architecture. The results move the validation of architectures from the current information domain into the knowledge domain and improve the reliability of such validation efforts. The paper presents research and results of both doctoral research efforts and puts them into a common context of state-of-the-art of systems engineering methods supporting more agility.

Tolk, Andreas↗
NASA NTRSDate not supplied

Nancy Grace Roman Space Telescope Observatory Implementation and Challenges

NASA’s Nancy Grace Roman Space Telescope (Roman), previously referred to as Wide Field Infrared Survey Telescope (WFIRST), was named after Dr. Nancy Grace Roman, an astronomer and NASA pioneer of modern space-based astronomy who is known as the “mother of the Hubble Space Telescope”. Roman is a deep space infrared observatory with a Hubble-sized telescope and wide field of view instrument (greater than 100 times that of Hubble’s) that will conduct a high latitude time-domain survey, a high latitude imaging and spectroscopic survey, and a galactic bulge time-domain survey to characterize dark energy and expand the census of exoplanets in our galaxy while allowing a broad range of astrophysics research. Roman will also demonstrate exoplanet coronagraphy with active wave front control technology and provide general investigator programs for the science community. Roman is finishing the critical design phase and is planning for launch in 2026. It will operate in a quasi-halo orbit about Sun-Earth L2, 1.5 million kilometers from Earth, for a five-year primary mission life. The Observatory features an Optical Telescope Assembly with an existing, repurposed 2.4m primary mirror, a Wide Field Instrument with a focal plane array comprised of 18 HgCdTe near-infrared detectors and a grism, prism and filter elements for imaging and spectroscopy in support of the primary surveys, as well as a Coronagraph instrument technology demonstration with starlight suppression technology for direct imaging and spectroscopy of exoplanets. The telescope is mounted to the Instrument Carrier composite truss structure which also optically meters each instrument, includes a Launch Load and Vibration Isolation System to provide passive isolation of spacecraft jitter sources while also supporting the payload during launch and is attached to the Spacecraft Bus. The Spacecraft also includes a Solar Array Sunshield ,Deployable Aperture Cover, Lower Instrument Sunshade, High Gain Antenna System, and Outer Barrel Assembly. Figure 1 shows an overview of the Roman Observatory. When fully integrated, Roman will be the largest Observatory assembled and tested at NASA’s Goddard Space Flight Center. Figure 1. Roman Observatory Overview Development of scientific satellites is challenging by nature, as the pursuit to broaden scientific knowledge always pushes the boundary of what has come before. The implementation of the Roman mission is a prime example and expected challenges have been augmented by the foundational decision to use the existing telescope components, developed in the early 2000s by another Government agency for a different application. Other unique aspects of the Roman mission, such as its survey nature, the vast amount of data required to meet science objectives, and packaging of the Observatory elements around the existing telescope components, create constrained design spaces that drive competing requirements across Observatory subsystems. Given these challenges, systems engineering has been a critical discipline in balancing implementation decisions for the Roman mission and will continue to play a key role going forward. This paper will discuss details of the Roman Observatory configuration, as well as some of the systems engineering challenges and the decision-making process used to mature the Roman Space Telescope preliminary design to implementation.

Lisa Ml Bartusek↗
NASA NTRS2008

Reaching for the APEX at Ames

The multidimensional design of the APEX program is the result of an extensive research and development effort dating back nearly a decade. "In the late 1990s and early 2000, we were pretty successful at getting new research and technology projects here at the center," Johnson says, "and we had a lack of critical mass of project managers. We were taking people who were primarily researchers and putting them in the position of managing projects." Smith and Johnson held a series of workshops across the center during 2000 and 2001 to gather feedback about how to address this issue. When they briefed the center's senior management on their findings, one of the top recommendations was to establish a project manager development program at Ames. At that point, they cast a wide net for ideas and information. "We did centerwide needs assessment, we did focus groups, we did surveys," Smith says. "We came up with a proposal for what a program would look like, tying in what we knew about the Academy of Program1 Project Leadership (now the Academy for Program/Project and Engineering Leadership, or APPEL), what we've seen at other centers, what other centers have tried. We were always checking to make sure our program mapped to APPEL. We also looked at the PMI [Project Management Institute] model, INCOSE [International Council on Systems Engineering], CMMI [Capability Maturity Model Integration], you name it." "We had a lot of conversations with the Jet Propulsion Lab and Goddard," Johnson adds. "We saw those centers as models for what Ames was aspiring to be in terms of a center for managing space flight missions." Their research confirmed what they already knew-that strong practitioner involvement would be critical to their program design process. 'XPEX is for the practitioner by the practitioner," Smith says. "They have to be a part of designing it. Otherwise there's no way we could design a program that meets their needs." At the same time that they worked at the grassroots level, they also solicited feedback from the center's senior management. "We recognized that in order for anything to succeed here, we needed to have a champion at the center management level," Johnson said. "You have to have champions, and you have to listen to what the senior managers are saying. They have their own ideas." In the case of APEX, one of those ideas fundamentally reshaped the program. "When we originally started, it was a project management development program," Johnson says, "but in our meeting with our center director, he said, 'Project management is important, but we also need to strengthen our systems engineering.' So we basically added that component to the program based on what he wanted."

Kohut, Matthew↗
NASA NTRSDate not supplied

Nancy Grace Roman Space Telescope Observatory Implementation and Challenges

NASA’s Nancy Grace Roman Space Telescope (Roman) is a deep space infrared observatory with a Hubble-sized telescope and wide field of regard with a boresight view greater than 200 times that of the Hubble Wide Field Camera 3infrared field of view, that will conduct a suite of science surveys to characterize dark energy and expand the census of exoplanets in our galaxy. Roman will also demonstrate exoplanet coronagraphy with active wavefront control technology and provide general investigator opportunities for the science community. Roman is finishing the critical design phase and is planning for launch in 2026. It will operate at the second Sun-Earth-Moon Lagrange for a five-year primary mission life. The Observatory features a telescope with an existing, repurposed 2.4m primary mirror, a Wide Field Instrument with a near-infrared detector focal plane array and optical elements for imaging and spectroscopy, as well as a Coronagraph instrument technology demonstration for direct imaging and spectroscopy of exoplanets. The telescope and instruments are mounted to an Instrument Carrier for optical metering and isolation from Spacecraft-induced disturbances. The Spacecraft includes a Bus, Solar Array Sunshield, Deployable Aperture Cover, Outer Barrel Assembly, and Star Tracker/Inertial Reference Unit Bench. When fully integrated, Roman will be the largest Observatory assembled and tested at NASA’s Goddard Space Flight Center. The development of scientific satellites is challenging and pushes engineering boundaries to broaden scientific knowledge. The Roman mission implementation is a prime example and expected challenges have been amplified by the foundational decision to use existing, repurposed telescope components. Other unique aspects of the Roman mission, including its survey nature, large data volume, and Observatory packaging, create constrained design spaces that drive competing requirements across Observatory subsystems. Given these challenges, systems engineering has been a critical discipline in balancing implementation decisions and will continue to play a key role in the development of the Roman mission. This paper will discuss details of the Roman Observatory configuration, systems engineering challenges and the decision-making process used to mature the Roman Space Telescope from preliminary design to implementation.

Lisa M L Bartusek↗
DOE OSTI2023

Multidisciplinary design optimization in Architecture, Engineering, and Construction: a detailed review and call for collaboration

The design of buildings has become a complex and multidisciplinary problem involving multiple conflicting objectives as architects and designers address competing technical, economic, environmental, and societal concerns. This has been driving research in Architecture, Engineering, and Construction (AEC) toward rigorous multidisciplinary decision-making frameworks that generate and evaluate numerous design alternatives using multi-objective optimization in concert with simulation and analysis models of varying fidelity and computational expense. While such frameworks are well known and widely employed in the aerospace and systems engineering domains, efforts by design professionals and researchers in the AEC field are scattered at best. In this paper, we provide a detailed review of recent developments in optimization frameworks in the AEC field and subsequently highlight how such developments are largely compartmentalized into separate domains such as structural, energy, daylighting, and other performance factors. Herein, we further discuss the technical challenges involved in concurrent coupled multidisciplinary design optimization (MDO) in the AEC field such as interoperability issues between Building Information Modeling (BIM) environments, analysis/simulation tools, and optimization frameworks. We conclude by outlining research needed for more unified modeling and simulation-based optimization frameworks to aid in complex and multidisciplinary building design processes. We also highlight the need for the identification and development of multi-fidelity simulation tools for use across multiple design phases. As such, this paper contributes a novel roadmap to leverage aerospace and systems engineering research in MDO into the field of AEC, along with a call for researchers in the MDO community to seek collaborations in AEC field.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2025

INTEGRATION OF DATA ANALYTICS WITH SYSTEM HEALTH PROGRAMS

Industry equipment reliability and asset management programs are essential elements that help ensure the safe and economical operation of nuclear power plants. The effectiveness of these programs is addressed in several industry developed and regulatory programs. However, these programs have proven to be labor intensive and expensive. There is an opportunity to significantly enhance the collection, analysis, and use of this information to provide more cost-effective plant operation. Additionally, there is an acute industry need to leverage advanced technology to reduce costs and improve operational effectiveness. The goal of this paper is to provide effective and efficient analytical methods and tools to support risk-informed decisions for the equipment reliability and asset management programs at nuclear power plants. This is accomplished by creating a direct bridge between component health/lifecycle data and decision making (e.g., maintenance scheduling and project prioritization). Here we are supporting typical system engineer decisions regarding maintenance activity scheduling and component ageing management. This is performed in a risk-informed context where herein the term “risk” is broadly constructed to include both plant reliability and economics. This framework combines data analytics tools to analyze equipment reliability data with risk-informed methods designed to support system engineer decisions (e.g., maintenance and replacement schedules, optimal maintenance posture) in a customizable workflow. A challenge is that the structure of this workflow strongly depends on the decision that needs to be made, the type of data available, and the constraints that need to be considered. Current methods are designed to provide specific answers to specific problems; however, these methods might prove to be inadequate even when problem settings slightly change (e.g., different types of requirements, additional dependencies between system reliability and economics). We tackled this challenge by designing framework in a flexible and modular fashion such that the user can assemble and customize his/her own workflow that integrates SSC economic lifecycle models (e.g., maintenance and replacement costs), system reliability models, and optimization methods.

97 - MATHEMATICS AND COMPUTING↗
NASA NTRS1987

Antimisting kerosene JT3 engine fuel system integration study

An analytical study and laboratory tests were conducted to assist NASA in determining the safety and mission suitability of the modified fuel system and flight tests for the Full-Scale Transport Controlled Impact Demonstration (CID) program. This twelve-month study reviewed and analyzed both the use of antimisting kerosene (AMK) fuel and the incorporation of a fuel degrader on the operational and performance characteristics of the engines tested. Potential deficiencies and/or failures were identified and approaches to accommodate these deficiencies were recommended to NASA Ames -Dryden Flight Research Facility. The result of flow characterization tests on degraded AMK fuel samples indicated levels of degradation satisfactory for the planned missions of the B-720 aircraft. The operability and performance with the AMK in a ground test engine and in the aircraft engines during the test flights were comparable to those with unmodified Jet A. For the final CID test, the JT-3C-7 engines performed satisfactorily while operating on AMK right up to impact.

Fiorentino, A.↗
NASA NTRS2009

The Functional Breakdown Structure (FBS) and Its Relationship to Life Cycle Cost

The Functional Breakdown Structure (FBS) is a structured, modular breakdown of every function that must be addressed to perform a generic mission. It is also usable for any subset of the mission. Unlike a Work Breakdown Structure (WBS), the FBS is a function-oriented tree, not a product-oriented tree. The FBS details not products, but operations or activities that should be performed. The FBS is not tied to any particular architectural implementation because it is a listing of the needed functions, not the elements, of the architecture. The FBS for Space Transportation Systems provides a universal hierarchy of required functions, which include ground and space operations as well as infrastructure - it provides total visibility of the entire mission. By approaching the systems engineering problem from the functional view, instead of the element or hardware view, the SPST has created an exhaustive list of potential requirements which the architecture designers can use to evaluate the completeness of their designs. This is a new approach that will provide full accountability of all functions required to perform the planned mission. It serves as a giant check list to be sure that no functions are omitted, especially in the early architectural design phase. A significant characteristic of a FBS is that if architecture options are compared using this approach, then any missing or redundant elements of each option will be ' identified. Consequently, valid Life Cycle Costs (LCC) comparisons can be made. For example, one architecture option might not need a particular function while another option does. One option may have individual elements to perform each of three functions while another option needs only one element to perform the three functions. Once an architecture has been selected, the FBS will serve as a guide in development of the work breakdown structure, provide visibility of those technologies that need to be further developed to perform required functions, and help identify the personnel skills required to develop and operate the architecture. It also wifi allow the systems engineering activities to totally integrate each discipline to the maximum extent possible and optimize at the total system level, thus avoiding optimizing at the element level (stove-piping). In addition, it furnishes a framework that wifi help prevent over or under specifying requirements because all functions are identified and all elements are aligned to functions.

DeHoff, Bryan↗
NASA NTRS2013

Virtual Construction of Space Habitats: Connecting Building Information Models (BIM) and SysML

Current trends in design, construction and management of complex projects make use of Building Information Models (BIM) connecting different types of data to geometrical models. This information model allow different types of analysis beyond pure graphical representations. Space habitats, regardless their size, are also complex systems that require the synchronization of many types of information and disciplines beyond mass, volume, power or other basic volumetric parameters. For this, the state-of-the-art model based systems engineering languages and processes - for instance SysML - represent a solid way to tackle this problem from a programmatic point of view. Nevertheless integrating this with a powerful geometrical architectural design tool with BIM capabilities could represent a change in the workflow and paradigm of space habitats design applicable to other aerospace complex systems. This paper shows some general findings and overall conclusions based on the ongoing research to create a design protocol and method that practically connects a systems engineering approach with a BIM architectural and engineering design as a complete Model Based Engineering approach. Therefore, one hypothetical example is created and followed during the design process. In order to make it possible this research also tackles the application of IFC categories and parameters in the aerospace field starting with the application upon the space habitats design as way to understand the information flow between disciplines and tools. By building virtual space habitats we can potentially improve in the near future the way more complex designs are developed from very little detail from concept to manufacturing.

space architecture↗
DOE OSTI2025

Bridging Equipment Reliability Data and Risk Informed Decisions in a Plant Operation Context

Industry equipment reliability and asset management programs are essential elements that help ensure the safe and economical operation of nuclear power plants. The effectiveness of these programs is addressed in several industry-developed and regulatory programs. The Risk-Informed Asset Management (RIAM) project is tasked to develop tools in support of the equipment reliability and asset management programs at nuclear power plants. These tools are designed to create a direct bridge between component health/lifecycle data and decision making (e.g., maintenance scheduling and project prioritization). The goal of this article is to provide a guide for specific use cases that the RIAM project is targeting. We have grouped uses cases into three main areas. The first area focuses on the analysis of equipment reliability data with a particular emphasis on condition-based data, such as test/surveillance reports and component monitoring data. The second area focuses on the integration of equipment reliability into system/plant reliability models to determine system/plant health and identify the components that are critical to maintain an operational system. Lastly, the third area manages plant resources, such as maintenance activities and replacement scheduling using optimization methods. Here the primary focus is on supporting typical system engineer decisions regarding maintenance activity scheduling and component aging management. This is performed in a risk-informed context where the term “risk” is broadly constructed to include both plant reliability and economics. This framework combines data analytics tools to analyze equipment reliability data with risk-informed methods designed to support system engineer decisions (e.g., maintenance and replacement schedules, optimal maintenance posture) in a customizable workflow.

97 - MATHEMATICS AND COMPUTING↗
NASA NTRS1964

Lunar exploration.

Ranger and Surveyor spacecraft systems engineering in terms of lunar exploration objectives, system design and flight experience

UNMANNED SPACECRAFT↗
NASA NTRS2011

Jupiter Europa Orbiter Architecture Definition Process

The proposed Jupiter Europa Orbiter mission, planned for launch in 2020, is using a new architectural process and framework tool to drive its model-based systems engineering effort. The process focuses on getting the architecture right before writing requirements and developing a point design. A new architecture framework tool provides for the structured entry and retrieval of architecture artifacts based on an emerging architecture meta-model. This paper describes the relationships among these artifacts and how they are used in the systems engineering effort. Some early lessons learned are discussed.

requirements analysis↗
NASA NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗
NASA NTRSDate not supplied

Assessing Engine Hot Fire Data for Human Spaceflight Applications

Development and certification of liquid engine systems for human spaceflight missions requires exhaustive analysis to meet the NASA’s requirements for engine health, reliability, and performance. The techniques used to assess requirement conformance and test-to-test engine health pose many unique challenges including the unusually large scale of data, complex component and system analysis, and rigorous engineering judgement standards. To address these challenges, NASA Marshall Space Flight Center’s Engine Systems branch has developed and maintained a robust software suite and operational processes that satisfy programmatic requirements levied on engines and the 7 Elements of Flight Rationale. Analysis at a systems level includes subsystem assessment of components such as turbomachinery and combustion devices as well as structural and fluid dynamics and transient and steady-state assessment at a systems level. Some of the most important tools to accomplish this analysis are automated script databases, creation of historical and statistical comparisons, and parameters calculated at the full data rate. These tools greatly simplify the crucial processes of anomaly investigation, limit monitoring, health assessment, and timely communication of key conclusions drawn from hot fire testing and flight data analysis.

Data Assessment↗
NASA NTRSDate not supplied

Assessing Engine Hot Fire Data for Human Spaceflight Applications

Development and certification of liquid engine systems for human spaceflight missions requires exhaustive analysis to meet the NASA’s requirements for engine health, reliability, and performance. The techniques used to assess requirement conformance and test-to-test engine health pose many unique challenges including the unusually large scale of data, complex component and system analysis, and rigorous engineering judgement standards. To address these challenges, NASA Marshall Space Flight Center’s Engine Systems branch has developed and maintained a robust software suite and operational processes that satisfy programmatic requirements levied on engines and the 7 Elements of Flight Rationale. Analysis at a systems level includes subsystem assessment of components such as turbomachinery and combustion devices as well as structural and fluid dynamics and transient and steady-state assessment at a systems level. Some of the most important tools to accomplish this analysis are automated script databases, creation of historical and statistical comparisons, and parameters calculated at the full data rate. These tools greatly simplify the crucial processes of anomaly investigation, limit monitoring, health assessment, and timely communication of key conclusions drawn from hot fire testing and flight data analysis.

Data Assessment↗
NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗
DOE OSTI2021

WISDEM® v3.4.1(Wind Plant Integrated System Design and Engineering Model) [SWR-14-05]

The Wind Plant Integrated System Design and Engineering Model (WISDEM®) is a set of models for assessing overall wind plant cost of energy (COE). The models use wind turbine and plant cost and energy production as well as financial models to estimate COE and other wind plant system attributes. WISDEM® is accessed through Python, is built using OpenMDAO, and uses several sub-models that are also implemented within OpenMDAO. These sub-models can be used independently but they are required to use the overall WISDEM® turbine design capability. Please install all of the pre-requisites prior to installing WISDEM® by following the directions below. For additional information about the NWTC effort in systems engineering that supports WISDEM® development, please visit the official NREL systems engineering for wind energy website. https://www.nlr.gov/wind/systems-engineering

Dykes, Katherine↗