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 181 records · Page 10

About the Complex Natural and Engineered Systems Pillar

Los Alamos National Laboratory is a world leader in applying multi-disciplinary science to complex systems within the Complex Natural and Engineered Systems (CNES) challenge areas. Our search for solutions requires science and technology innovation, as well as an integrated experiment, theory, and modeling and simulation approach. Our research and development spans from improving engineered systems such as nuclear weapons and the power grid, to understanding the interface of human and engineered systems from the subsurface to space, to studying how complex natural systems such as disease and climate impact humanity.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

NuScale Systems Engineering Program Overview and Status

NuScale systems engineering program overview, including technical data management and model-based engineering, product structures, architecture views, and model-based systems engineering. Includes a discussion on technical risk and opportunity management and technical readiness levels, as well as risk-informed performance-based principles and methods.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM).

Johnson, Stephen B.↗

System Engineering Analysis For Improved Scout Business Information Systems

The project uses system engineering principles to address the need of Boy Scout leaders for an integrated system to facilitate advancement and awards records, leader training and planning for meetings and activities. Existing products to address needs of Scout leaders and relevant stakeholders function to support record keeping and some communication functions but opportunity exists for a better system to fully integrate these functions with training delivery and recording, activity planning along with feedback and information gathering from stakeholders. Key stakeholders for the sytem include Scouts and their families, leaders, training providers, sellers of supplies and awards, content generators and facilities that serve Scout activities. Key performance parameters for the system are protection of personal information, availability of current information, information accuracy and information content that has depth. Implementation concepts considered for the system include (1) owned and operated by Boy Scouts of America, (2) Contracted out to a vendor (3) distributed system that functions with BSA managed interfaces. The selected concept is to contract out to a vendor to maximize the likelihood of successful integration and take advantage of the best technology. Development of requirements considers three key use cases (1) System facilitates planning a hike with training needed satisfied in advance and advancement recording real time (2) Scheduling and documenting in-person training, (3) Family interested in Scouting receives information and can request follow-up. Non-functional requirements are analyzed with the Quality Function Deployment tool. Requirement addressing frequency of backup, compatibility with legacy and new technology, language support, software update are developed to address system reliability and intuitive interface. System functions analyzed include update of activity database, maintenance of advancement status, archive of documents, and monitoring of content that is accessible. The study examines risks associated with information security, technological change and continued popularity of Scouting. Mitigation is based on system functions that are defined. The approach to developing an improved system for facilitating Boy Scout leader functions was iterative with insights into capabilities coming in the course of working through the used cases and sequence diagrams.

97 MATHEMATICS AND COMPUTING↗

L-Band Digital Aeronautical Communications System Engineering - Concepts of Use, Systems Performance, Requirements, and Architectures

This NASA Contractor Report summarizes and documents the work performed to develop concepts of use (ConUse) and high-level system requirements and architecture for the proposed L-band (960 to 1164 MHz) terrestrial en route communications system. This work was completed as a follow-on to the technology assessment conducted by NASA Glenn Research Center and ITT for the Future Communications Study (FCS). ITT assessed air-to-ground (A/G) communications concepts of use and operations presented in relevant NAS-level, international, and NAS-system-level documents to derive the appropriate ConUse relevant to potential A/G communications applications and services for domestic continental airspace. ITT also leveraged prior concepts of use developed during the earlier phases of the FCS. A middle-out functional architecture was adopted by merging the functional system requirements identified in the bottom-up assessment of existing requirements with those derived as a result of the top-down analysis of ConUse and higher level functional requirements. Initial end-to-end system performance requirements were derived to define system capabilities based on the functional requirements and on NAS-SR-1000 and the Operational Performance Assessment conducted as part of the COCR. A high-level notional architecture of the L-DACS supporting A/G communication was derived from the functional architecture and requirements.

Zelkin, Natalie↗

System Engineering Issues for Avionics Survival in the Space Environment

This paper examines how the system engineering process influences the design of a spacecraft's avionics by considering the space environment. Avionics are susceptible to the thermal, radiation, plasma, and meteoroids/orbital debris environments. The environment definitions for various spacecraft mission orbits (LEO/low inclination, LEO/Polar, MEO, HEO, GTO, GEO and High ApogeeElliptical) are discussed. NASA models and commercial software used for environment analysis are reviewed. Applicability of technical references, such as NASA TM-4527 "Natural Orbital Environment Guidelines for Use in Aerospace Vehicle Development" is discussed. System engineering references, such as the MSFC System Engineering Handbook, are reviewed to determine how the environments are accounted for in the system engineering process. Tools and databases to assist the system engineer and avionics designer in addressing space environment effects on avionics are described and usefulness assessed.

Pavelitz, Steven↗

Systems engineering overview for regenerative life-support systems applicable to space habitats

The Life-Support Systems Group of the 1977 NASA Ames Summer Study conducted analyses initially to identify areas where partial or complete closure of the life-support system, for various types of space habitats, should be considered, and to develop a sound methodology for identifying, screening, and evaluating alternative closure schemes. Results of these analyses, including the systems engineering considerations that affect technology-development planning and management for regenerative life-support systems, are discussed. A recommended methodology is also presented as a basis for future technology-development activities in this area.

Spurlock, J.↗

Layered Systems Engineering Engines

A notation is described for depicting the relationships between multiple, contemporaneous systems engineering efforts undertaken within a multi-layer system-of-systems hierarchy. We combined the concepts of remoteness of activity from the end customer, depiction of activity on a timeline, and data flow to create a new kind of diagram which we call a "Layered Vee Diagram." This notation is an advance over previous notations because it is able to be simultaneously precise about activity, level of granularity, product exchanges, and timing; these advances provide systems engineering managers a significantly improved ability to express and understand the relationships between many systems engineering efforts. Using the new notation, we obtain a key insight into the relationship between project duration and the strategy selected for chaining the systems engineering effort between layers, as well as insights into the costs, opportunities, and risks associated with alternate chaining strategies.

Vee Diagram↗

Systems engineering, manned space flight.

Systems engineering activities in manned space flight involving design, development, manufacture, test and operation of Mercury, Gemini and Apollo flight systems

Mathews, C. W.↗

Analytical investigation of two hydrogen oxygen rocket engine systems for low-thrust application

Two hydrogen oxygen rocket engine system concepts were analyzed parametrically over a thrust range from 100 to 1000 pounds and a chamber pressure range from 175 to 1000 psia. Both concepts were regeneratively cooled with hydrogen and were pump fed by electric motor driven positive displacement pumps. Electric power was provided by either a turboalternator (turboalternator concept) or some means external to the engine system (auxiliary power concept). The turboalternator concept is discussed. The computer program used to conduct the analyses along with the design characteristics of the major engine system components is described. The feasible design range of the systems over the parametric range of thrust is discussed in terms of allowable chamber pressure. Engine system estimated performance, mass, and dimensional envelope parametric data within the feasible design range are presented.

Scheer, D. D.↗

Use of Systems Engineering in Repurposing Coal-Fired Power Plants with Malta Pumped Thermal Energy Storage System

he electric sector across North America is facing a transition. Both economics and policy decisions have pointed towards a broad retirement of fossil assets across markets. Owners are facing the problem of how to evolve the base of the electric sector from fossil asset to greener alternative. Coal-fired power plants built the modern electricity grid. Their rotating machinery are the beating heart of the grid, providing essential resiliency and reliability services. Power plant retirements are disruptive to plant workforces and cause outsized impacts on surrounding communities. The transition from thermal power plants that use rotating machinery to generate electricity (e.g., coal- and gas-fired plants) to variable, inverter-based generation (e.g., solar and wind) is affecting the reliability of the electric grid. Grid operators and national regulators have issued warnings about known and anticipated risk. In 2021, Malta Inc. was awarded a Department of Energy (DOE) grant to study how to integrate a Malta 100MW Pumped Heat Energy Storage (PHES) system with a retiring coal-fired power plant to meet emissions requirements, retain plant workforces, preserve communities, and maintain grid reliability. This presentation provides a summary of this study, focusing on how systems engineering approach was used to arrive at a proposed design concept that met multiple objectives and requirements. There will be three main parts for this presentation. The first part of the presentation will focus on how different systems engineering was applied for this work. In particular, the following areas: stakeholder engagement, site selection process, developing requirements and use cases for the integrated system, defining the system and its boundary, coming up with different system architecture/option, performing a techno-economic analysis to compare the different options and down selection of the preferred option, will be discusses. For these areas, discussion on the decisions on how much breadth and depth to go into each area will be provided. These discussions provide good insights into how to apply systems engineering. The second part of the presentation will provide a deeper dive into the two recommended integration options that repurpose coal-fired power plants with Malta PHES system. The comparison of the two options and general guidance of how to choose an option will be provided. This is particularly useful for utilities who are facing coal-plant retirements. The two options will be compared based on its performance (such as power output, efficiency), complexity, and cost. The social impact on local communities of the two options will also be discussed. The final part of the presentation will discuss the impact that this work has had, including Malta Inc. being invited to the White House to discuss progress and outcomes of this work with the Interagency Working Group on Coal and Power Plant Communities and Economic Revitalization. In summary, this presentation aims to provide a showcase of how sy

25 ENERGY STORAGE↗

ISO 9000 and/or Systems Engineering Capability Maturity Model?

For businesses and organizations to remain competitive today they must have processes and systems in place that will allow them to first identify customer needs and then develop products/processes that will meet or exceed the customers needs and expectations. Customer needs, once identified, are normally stated as requirements. Designers can then develop products/processes that will meet these requirements. Several functions, such as quality management and systems engineering management are used to assist product development teams in the development process. Both functions exist in all organizations and both have a similar objective, which is to ensure that developed processes will meet customer requirements. Are efforts in these organizations being duplicated? Are both functions needed by organizations? What are the similarities and differences between the functions listed above? ISO 9000 is an international standard of goods and services. It sets broad requirements for the assurance of quality and for management's involvement. It requires organizations to document the processes and to follow these documented processes. ISO 9000 gives customers assurance that the suppliers have control of the process for product development. Systems engineering can broadly be defined as a discipline that seeks to ensure that all requirements for a system are satisfied throughout the life of the system by preserving their interrelationship. The key activities of systems engineering include requirements analysis, functional analysis/allocation, design synthesis and verification, and system analysis and control. The systems engineering process, when followed properly, will lead to higher quality products, lower cost products, and shorter development cycles. The System Engineering Capability Maturity Model (SE-CMM) will allow companies to measure their system engineering capability and continuously improve those capabilities. ISO 9000 and SE-CMM seem to have a similar objective, which is to document the organization's processes and certify to potential customers the capability of a supplier to control the processes that determine the quality of the product or services being produced. The remaining sections of this report examine the differences and similarities between ISO 9000 and SE-CMM and make recommendations for implementation.

Sampson E. Gholston↗

Hubble Space Telescope systems engineering

The role of systems engineering in the Hubble Space Telescope (HST) development program at NASA Marshall is reviewed. The scientific objectives and overall characteristics of the HST are recalled, and particular attention is given to the early identification and correction of problems in the optical system, the pointing-control system (maneuvering and fine guidance), the rate-gyro assembly, reaction-wheel isolation, the battery reconditioning circuit, and optical cleanliness.

Wojtalik, F. S.↗