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
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Systems Engineering and Integration for Technology Programs

The Architecture, Habitability & Integration group (AH&I) is a system engineering and integration test team within the NASA Crew and Thermal Systems Division (CTSD) at Johnson Space Center. AH&I identifies and resolves system-level integration issues within the research and technology development community. The timely resolution of these integration issues is fundamental to the development of human system requirements and exploration capability. The integration of the many individual components necessary to construct an artificial environment is difficult. The necessary interactions between individual components and systems must be approached in a piece-wise fashion to achieve repeatable results. A formal systems engineering (SE) approach to define, develop, and integrate quality systems within the life support community has been developed. This approach will allow a Research & Technology Program to systematically approach the development, management, and quality of technology deliverables to the various exploration missions. A tiered system engineering structure has been proposed to implement best systems engineering practices across all development levels from basic research to working assemblies. These practices will be implemented through a management plan across all applicable programs, projects, elements and teams. While many of the engineering practices are common to other industries, the implementation is specific to technology development. An accounting of the systems engineering management philosophy will be discussed and the associated programmatic processes will be presented.

Kennedy, Kruss J.↗
NASA NTRS1997

Toward Mass Customization in the Age of Information: The Case for Open Engineering Systems

In the Industrial Era, manufacturers used "dedicated" engineering systems to mass produce their products. In today's increasingly competitive markets, the trend is toward mass customization, something that becomes increasingly feasible when modern information technologies are used to create open engineering systems. Our focus is on how designers can provide enhanced product flexibility and variety (if not fully customized products) through the development of open engineering systems. After presenting several industrial examples, we anchor our new systems philosophy with two real engineering applications. We believe that manufacturers who adopt open systems will achieve competitive advantage in the Information Age.

Simpson, Timothy W.↗
NASA NTRS2007

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record↗
DOE OSTI2015

A Vision for Systems Engineering Applied to Wind Energy (Presentation)

This presentation was given at the Third Wind Energy Systems Engineering Workshop on January 14, 2015. Topics covered include the importance of systems engineering, a vision for systems engineering as applied to wind energy, and application of systems engineering approaches to wind energy research and development.

17 WIND ENERGY↗
NASA NTRS2015

Systems Engineering

This short course provides information on what systems engineering is and how the systems engineer guides requirements, interfaces with the discipline leads, and resolves technical issues. There are many system-wide issues that either impact or are impacted by the thermal subsystem. This course will introduce these issues and illustrate them with real life examples.

Thermal↗
DOE OSTI2021

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↗
DOE OSTI2021

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↗
NASA NTRS2013

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.↗
DOE OSTI2017

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↗
NASA NTRS2010

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↗
NASA NTRS1999

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↗
NASA NTRS1979

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.↗
NASA NTRS2009

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↗