Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “systems engineering”

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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRS1966

Looking ahead in systems engineering

Five areas that are discussed in this paper are: (1) the technological characteristics of systems engineering; (2) the analytical techniques that are giving modern systems work its capability and power; (3) the management, economics, and effectiveness dimensions that now frame the modern systems field; (4) systems engineering's future impact upon automation, computerization and managerial decision-making in industry - and upon aerospace and weapons systems in government and the military; and (5) modern systems engineering's partnership with modern quality control and reliability.

Feigenbaum, Donald S.↗
NASA NTRS1975

Oxygen systems engineering considerations

Special considerations for oxygen systems engineering with respect to system design, fabrication, and use are studied. The concerns for oxygen systems include the problems of leakage and erosion, difficulties that arise from dynamic processes, and the sensitivity of oxygen systems to contamination and cleaning requirements.

Source record↗
DOE OSTI2016

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

The genesis for this systematic literature review was to search for industry case studies that could inform a decision of whether or not to support the change process, investment, training, and tools needed to implement an MBSE approach across the engineering enterprise. The question asked was, how the change from a document - based systems engineering approach (DBSE) to a model-based systems engineering approach (MBSE) is justified? The methodology employed for this systematic literature review was to conduct a document search of electronically published case studies by authors from the defense, space, and complex systems product engineering industries. The 67 case studies without metrics mainly attributed success to completeness, consistency, and communication of requirements. The 21 case studies with metrics on cost and schedule primarily attributed success to the ability of an MBSE approach to improve defect prevention strategies. The primary conclusion is that there is a significant advantage to project performance by applying an MBSE approach. An MBSE approach made the engineering processes on a complex system development effort more efficient by improving requirements completeness, consistency, and communication. These were seen in engineering processes involved in requirements management, concept exploration, design reuse, test and qualification, Verification and Validation, and margins analyses. An MBSE approach was most effective at improving defect prevention strategies. The approach was found to enhance the capability to find defects early in the system development life cycle (SDLC), when they could be fixed with less impact and prevented rework in later phases, thus mitigating risks to cost, schedule, and mission. However, if a program only employed an MBSE approach for requirements management, advantages from finding defects early could not be leveraged in later phases, where the savings in cost and schedule from rework prevention is realized. Significant performance success was achieved when the systems engineer (SE) held a leadership role over engineering process es. A number of the case studies addressed a general lack of skilled MBSE engineers as a major hindrance to implementing an MBSE approach successfully.

42 ENGINEERING↗
DOE OSTI2017

A Practical Application of Integrated Systems Engineering and Project Management on a Complex EPC Project - 17207

This paper introduces how an integrated set of Systems Engineering (SE) and Project Management (PM) processes were applied in a practical way, to address the challenges on a complex, highly technical, Engineering Procurement Construction project within the nuclear field. This approach was inspired by: - the principles contained in a Community of Practice on Lean in Program Management jointly established in May 2012 by MIT, PMI and INCOSE; - an opportunity to apply international standard ISO/IEC 15288:2008(E) Systems and software engineering - System life cycle processes on a real-life situation; - and the belief that there is great value in applying Systems Engineering and Project Management in an integrated manner on a project. The project offering this opportunity was the Detail Engineering, Procurement, Construction and Cold Commissioning (EPC) of the Silo Direct-encapsulation Plant (SDP). This project was undertaken by the Joint Venture (JV) formed by Areva, Mace and Atkins (a.m.a. Nuclear Ltd). Unfortunately, early termination of the project, at a stage when only a part of the processes and tools were being implemented, did not allow this integrated approach to be demonstrated in full. However, the benefits achieved in the early stages in aligning and forming an integrated project execution team, showed potential for great benefits. This paper covers an introductory analysis of the situation, the successes and benefits achieved from implementing an integrated SE - PM approach up to the stage when the project was terminated, and possible path forward had the project continued. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1993

Management issues in systems engineering

When applied to a system, the doctrine of successive refinement is a divide-and-conquer strategy. Complex systems are sucessively divided into pieces that are less complex, until they are simple enough to be conquered. This decomposition results in several structures for describing the product system and the producing system. These structures play important roles in systems engineering and project management. Many of the remaining sections in this chapter are devoted to describing some of these key structures. Structures that describe the product system include, but are not limited to, the requirements tree, system architecture and certain symbolic information such as system drawings, schematics, and data bases. The structures that describe the producing system include the project's work breakdown, schedules, cost accounts and organization.

Shishko, Robert↗
NASA NTRS1993

Nuclear Engine System Simulation (NESS) version 2.0

The topics are presented in viewgraph form and include the following; nuclear thermal propulsion (NTP) engine system analysis program development; nuclear thermal propulsion engine analysis capability requirements; team resources used to support NESS development; expanded liquid engine simulations (ELES) computer model; ELES verification examples; NESS program development evolution; past NTP ELES analysis code modifications and verifications; general NTP engine system features modeled by NESS; representative NTP expander, gas generator, and bleed engine system cycles modeled by NESS; NESS program overview; NESS program flow logic; enabler (NERVA type) nuclear thermal rocket engine; prismatic fuel elements and supports; reactor fuel and support element parameters; reactor parameters as a function of thrust level; internal shield sizing; and reactor thermal model.

Pelaccio, Dennis G.↗
NASA NTRSDate not supplied

Using Systems Engineering to Develop an Integrated Crew Health and Performance System to Mitigate Risk for Human Exploration Missions

New space exploration missions are currently being designed to take humanity beyond Low EarthOrbit (LEO) to cis-lunar space, the lunar surface, and eventually to Mars. These missions carryincreased risks due to a number of factors, including distance from Earth, exposure to deep spacehazards, reduced capacity and ability to resupply and evacuate, and increased communication delays.As distance from Earth grows and mission length increases, a growing proportion of overall missionrisk can be attributed to the “human system.” Almost twenty years ago, the Institute of Medicine in theUnited States recommended the early and complete integration of the human system into thespacecraft and mission design process to mitigate this increased risk inherent in exploration missions.Exploration missions will require increasing levels of crew self-sufficiency that will challenge thecurrent operational paradigms established in LEO. Enabling progressive Earth independence requiresmanagement of the increasingly complex interactions among spacecraft systems and integration of allthe data and functions that affect human health and performance into one coordinated system – theCrew Health and Performance (CHP) system. This system is a critical spacecraft system that isanalogous to other systems such as propulsion, guidance and navigation, or avionics. Design andintegration of the CHP system requires the evidence-based merger of typically disparate disciplinessuch as medicine, human factors, and physiological support system design, using systems engineering(SE) practices. The approach described here enables spacecraft and mission designers to align thescope of a CHP system with mission specific requirements, decrease risk to the crew, and increase theprobability of mission success.

Kerry Mcguire↗
DOE OSTI2017

Grid Integration Science, NREL Power Systems Engineering Center

This report highlights journal articles published in 2016 by researchers in the Power Systems Engineering Center. NREL's Power Systems Engineering Center published 47 journal and magazine articles in the past year, highlighting recent research in grid modernization.

2016 Power Systems Engineering Center↗
NASA NTRS2008

Enabling Innovation and Collaboration Across Geography and Culture: A Case Study of NASA's Systems Engineering Community of Practice

In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited personnel from sharing experiences and ideas. Mission failures and new directions for the agency demanded better collaborative tools. In addition, with the push to send astronauts back to the moon and to Mars, NASA recognized that systems engineering would have to improve across the agency. Of the ten field centers, seven had not built a spacecraft in over 30 years, and had lost systems engineering expertise. The Systems Engineering Community of Practice came together to capture the knowledge of its members using the suite of collaborative tools provided by the NASA Engineering Network (NEN.) The NEN provided a secure collaboration space for over 60 practitioners across the agency to assemble and review a NASA systems engineering handbook. Once the handbook was complete, they used the open community area to disseminate it. This case study explores both the technology and the social networking that made the community possible, describes technological approaches that facilitated rapid setup and low maintenance, provides best practices that other organizations could adopt, and discusses the vision for how this community will continue to collaborate across the field centers to benefit the agency as it continues exploring the solar system.

NEN↗
NASA NTRS1986

Systems Engineering of Electric and Hybrid Vehicles

Technical paper notes systems engineering principles applied to development of electric and hybrid vehicles such that system performance requirements support overall program goal of reduced petroleum consumption. Paper discusses iterative design approach dictated by systems analyses. In addition to obvious peformance parameters of range, acceleration rate, and energy consumption, systems engineering also considers such major factors as cost, safety, reliability, comfort, necessary supporting infrastructure, and availability of materials.

Kurtz, D. W.↗
NASA NTRSDate not supplied

ExMC Systems Engineering Developments

The Exploration Medical Capability (ExMC) Element within the Human Research Program (HRP) applies systems engineering (SE) principles along with the use of Model-Based Systems Engineering (MBSE) tools to identify and communicate the requirements for medical and crew health and performance (CHP) systems. In the past fiscal year, the MBSE approach sought to advance the digital engineering toolset for medical and CHP system representation. These digital artifacts provide enhanced views of the relationships among requirements, standards, functions, and capabilities, to name a few, that is best suited for a user’s objectives. The MBSE tools and SE practices were applied to the development of the revised Earth Independent Medical Operations (EIMO) medical system and the Artemis III and IV CHP System models. In addition, a System of Systems concept was integrated into the EIMO model to facilitate the identification of system interfaces that interact with the medical system. Finally, the ExMC SE team has initiated several efforts to bring operationally relevant digital engineering practices to the Human Health and Performance Directorate (HHPD). This included the development of a pilot program within the directorate to help foster utilization of tools such as MagicDraw for system modeling and Power BI for visualizing extracted data in an easily accessible dashboard format. Additionally, with the increase in complexity of the integration effort for Artemis missions, ExMC has endeavored to bring digital engineering strategies to potentially increase efficiency in review processes. This talk will provide a high-level overview of the ExMC SE team accomplishments since the last Investigators’ Workshop, an introduction to upcoming SE talks, and the ongoing systems engineering work.

systems engineering↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a focused design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

systems engineering↗
NASA NTRS2013

Towards Requirements in Systems Engineering for Aerospace IVHM Design

Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or 'band-aid' solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design.

Requirements↗
NASA NTRS1993

Nuclear Engine System Simulation (NESS). Version 2.0: Program user's guide

This Program User's Guide discusses the Nuclear Thermal Propulsion (NTP) engine system design features and capabilities modeled in the Nuclear Engine System Simulation (NESS): Version 2.0 program (referred to as NESS throughout the remainder of this document), as well as its operation. NESS was upgraded to include many new modeling capabilities not available in the original version delivered to NASA LeRC in Dec. 1991, NESS's new features include the following: (1) an improved input format; (2) an advanced solid-core NERVA-type reactor system model (ENABLER 2); (3) a bleed-cycle engine system option; (4) an axial-turbopump design option; (5) an automated pump-out turbopump assembly sizing option; (6) an off-design gas generator engine cycle design option; (7) updated hydrogen properties; (8) an improved output format; and (9) personal computer operation capability. Sample design cases are presented in the user's guide that demonstrate many of the new features associated with this upgraded version of NESS, as well as design modeling features associated with the original version of NESS.

Pelaccio, Dennis G.↗
DOE OSTI2016

System Engineering Applied: A Case Study in the Implementation of Successful Systems

The application of Systems Engineering (SE) principles has emerged to manage complex systems from a concept to the successful realization and implementation of the system. Multiple Research and Development (R&D) programs at Sandia National Laboratories (SNL) have implemented these principles and have maximized their efforts in the realization of successful systems. The Primary Standards Laboratory (PSL) at SNL has avoided the full implementation of such principles which has stalled the development of new and efficient calibration systems. The objective of this project is to introduce SE to the PSL and develop a framework of best practices that can be utilized to expedite the development and deployment of accurate and efficient testing systems throughout the PSL. A Case Study will be presented for the principles of the SE development lifecycle in a R&D environment to maximize the PSL’s efforts in a requirements-driven environment.

42 ENGINEERING↗