Search NASASearch

SEARCH · Search NASA

Results for “system engineering program”

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 199 records · Page 11

Software analysis handbook: Software complexity analysis and software reliability estimation and prediction

This handbook documents the three software analysis processes the Space Station Software Analysis team uses to assess space station software, including their backgrounds, theories, tools, and analysis procedures. Potential applications of these analysis results are also presented. The first section describes how software complexity analysis provides quantitative information on code, such as code structure and risk areas, throughout the software life cycle. Software complexity analysis allows an analyst to understand the software structure, identify critical software components, assess risk areas within a software system, identify testing deficiencies, and recommend program improvements. Performing this type of analysis during the early design phases of software development can positively affect the process, and may prevent later, much larger, difficulties. The second section describes how software reliability estimation and prediction analysis, or software reliability, provides a quantitative means to measure the probability of failure-free operation of a computer program, and describes the two tools used by JSC to determine failure rates and design tradeoffs between reliability, costs, performance, and schedule.

Computer systems design

Intelligent Engine Systems Work Element 1.3: Sub System Health Management

The objectives of this program were to develop health monitoring systems and physics-based fault detection models for engine sub-systems including the start, lubrication, and fuel. These models will ultimately be used to provide more effective sub-system fault identification and isolation to reduce engine maintenance costs and engine down-time. Additionally, the bearing sub-system health is addressed in this program through identification of sensing requirements, a review of available technologies and a demonstration of a demonstration of a conceptual monitoring system for a differential roller bearing. This report is divided into four sections; one for each of the subtasks. The start system subtask is documented in section 2.0, the oil system is covered in section 3.0, bearing in section 4.0, and the fuel system is presented in section 5.0.

Ashby, Malcolm

The environment power system analysis tool development program

The Environment Power System Analysis Tool (EPSAT) is being developed to provide space power system design engineers with an analysis tool for determining system performance of power systems in both naturally occurring and self-induced environments. The program is producing an easy to use computer aided engineering (CAE) tool general enough to provide a vehicle for technology transfer from space scientists and engineers to power system design engineers. The results of the project after two years of a three year development program are given. The EPSAT approach separates the CAE tool into three distinct functional units: a modern user interface to present information, a data dictionary interpreter to coordinate analysis; and a data base for storing system designs and results of analysis.

Jongeward, Gary A.

Economic Metrics for Commercial Reusable Space Transportation Systems

The success of any effort depends upon the effective initial definition of its purpose, in terms of the needs to be satisfied and the goals to be fulfilled. If the desired product is "A System" that is well-characterized, these high-level need and goal statements can be transformed into system requirements by traditional systems engineering techniques. The satisfaction of well-designed requirements can be tracked by fairly straightforward cost, schedule, and technical performance metrics. Unfortunately, some types of efforts, including those that NASA terms "Programs," tend to resist application of traditional systems engineering practices. In the NASA hierarchy of efforts, a "Program" is often an ongoing effort with broad, high-level goals and objectives. A NASA "project" is a finite effort, in terms of budget and schedule, that usually produces or involves one System. Programs usually contain more than one project and thus more than one System. Special care must be taken in the formulation of NASA Programs and their projects, to ensure that lower-level project requirements are traceable to top-level Program goals, feasible with the given cost and schedule constraints, and measurable against top-level goals. NASA Programs and projects are tasked to identify the advancement of technology as an explicit goal, which introduces more complicating factors. The justification for funding of technology development may be based on the technology's applicability to more than one System, Systems outside that Program or even external to NASA. Application of systems engineering to broad-based technology development, leading to effective measurement of the benefits, can be valid, but it requires that potential beneficiary Systems be organized into a hierarchical structure, creating a "system of Systems." In addition, these Systems evolve with the successful application of the technology, which creates the necessity for evolution of the benefit metrics to reflect the changing baseline. Still, economic metrics for technology development in these Programs and projects remain fairly straightforward, being based on reductions in acquisition and operating costs of the Systems. One of the most challenging requirements that NASA levies on its Programs is to plan for the commercialization of the developed technology. Some NASA Programs are created for the express purpose of developing technology for a particular industrial sector, such as aviation or space transportation, in financial partnership with that sector. With industrial investment, another set of goals, constraints and expectations are levied on the technology program. Economic benefit metrics then expand beyond cost and cost savings to include the marketability, profit, and investment return requirements of the private sector. Commercial investment criteria include low risk, potential for high return, and strategic alignment with existing product lines. These corporate criteria derive from top-level strategic plans and investment goals, which rank high among the most proprietary types of information in any business. As a result, top-level economic goals and objectives that industry partners bring to cooperative programs cannot usually be brought into technical processes, such as systems engineering, that are worked collaboratively between Industry and Government. In spite of these handicaps, the top-level economic goals and objectives of a joint technology program can be crafted in such a way that they accurately reflect the fiscal benefits from both Industry and Government perspectives. Valid economic metrics can then be designed that can track progress toward these goals and objectives, while maintaining the confidentiality necessary for the competitive process.

Shaw, Eric J.

Human Factors Interface with Systems Engineering for NASA Human Spaceflights

This paper summarizes the past and present successes of the Habitability and Human Factors Branch (HHFB) at NASA Johnson Space Center s Space Life Sciences Directorate (SLSD) in including the Human-As-A-System (HAAS) model in many NASA programs and what steps to be taken to integrate the Human-Centered Design Philosophy (HCDP) into NASA s Systems Engineering (SE) process. The HAAS model stresses systems are ultimately designed for the humans; the humans should therefore be considered as a system within the systems. Therefore, the model places strong emphasis on human factors engineering. Since 1987, the HHFB has been engaging with many major NASA programs with much success. The HHFB helped create the NASA Standard 3000 (a human factors engineering practice guide) and the Human Systems Integration Requirements document. These efforts resulted in the HAAS model being included in many NASA programs. As an example, the HAAS model has been successfully introduced into the programmatic and systems engineering structures of the International Space Station Program (ISSP). Success in the ISSP caused other NASA programs to recognize the importance of the HAAS concept. Also due to this success, the HHFB helped update NASA s Systems Engineering Handbook in December 2007 to include HAAS as a recommended practice. Nonetheless, the HAAS model has yet to become an integral part of the NASA SE process. Besides continuing in integrating HAAS into current and future NASA programs, the HHFB will investigate incorporating the Human-Centered Design Philosophy (HCDP) into the NASA SE Handbook. The HCDP goes further than the HAAS model by emphasizing a holistic and iterative human-centered systems design concept.

Wong, Douglas T.

Quiet Clean Short-Haul Experimental Engine (QSCEE). Preliminary analyses and design report, volume 1

The experimental propulsion systems to be built and tested in the 'quiet, clean, short-haul experimental engine' program are presented. The flight propulsion systems are also presented. The following areas are discussed: acoustic design; emissions control; engine cycle and performance; fan aerodynamic design; variable-pitch actuation systems; fan rotor mechanical design; fan frame mechanical design; and reduction gear design.

Source record

Software For Computer-Aided Design Of Control Systems

Computer Aided Engineering System (CAESY) software developed to provide means to evaluate methods for dealing with users' needs in computer-aided design of control systems. Interpreter program for performing engineering calculations. Incorporates features of both Ada and MATLAB. Designed to be flexible and powerful. Includes internally defined functions, procedures and provides for definition of functions and procedures by user. Written in C language.

Wette, Matthew

X-33/RLV System Health Management/Vehicle Health Management

To reduce operations costs, Reusable Launch Vehicles (RLVS) must include highly reliable robust subsystems which are designed for simple repair access with a simplified servicing infrastructure, and which incorporate expedited decision-making about faults and anomalies. A key component for the Single Stage To Orbit (SSTO) RLV system used to meet these objectives is System Health Management (SHM). SHM incorporates Vehicle Health Management (VHM), ground processing associated with the vehicle fleet (GVHM), and Ground Infrastructure Health Management (GIHM). The primary objective of SHM is to provide an automated and paperless health decision, maintenance, and logistics system. Sanders, a Lockheed Martin Company, is leading the design, development, and integration of the SHM system for RLV and for X-33 (a sub-scale, sub-orbit Advanced Technology Demonstrator). Many critical technologies are necessary to make SHM (and more specifically VHM) practical, reliable, and cost effective. This paper will present the X-33 SHM design which forms the baseline for the RLV SHM, and it will discuss applications of advanced technologies to future RLVs. In addition, this paper will describe a Virtual Design Environment (VDE) which is being developed for RLV. This VDE will allow for system design engineering, as well as program management teams, to accurately and efficiently evaluate system designs, analyze the behavior of current systems, and predict the feasibility of making smooth and cost-efficient transitions from older technologies to newer ones. The RLV SHM design methodology will reduce program costs, decrease total program life-cycle time, and ultimately increase mission success.

Mouyos, William

Engine Validation of Noise and Emission Reduction Technology Phase I

This final report has been prepared by Honeywell Aerospace, Phoenix, Arizona, a unit of Honeywell International, Inc., documenting work performed during the period December 2004 through August 2007 for the NASA Glenn Research Center, Cleveland, Ohio, under the Revolutionary Aero-Space Engine Research (RASER) Program, Contract No. NAS3-01136, Task Order 8, Engine Validation of Noise and Emission Reduction Technology Phase I. The NASA Task Manager was Dr. Joe Grady of the NASA Glenn Research Center. The NASA Contract Officer was Mr. Albert Spence of the NASA Glenn Research Center. This report is for a test program in which NASA funded engine validations of integrated technologies that reduce aircraft engine noise. These technologies address the reduction of engine fan and jet noise, and noise associated with propulsion/airframe integration. The results of these tests will be used by NASA to identify the engineering tradeoffs associated with the technologies that are needed to enable advanced engine systems to meet stringent goals for the reduction of noise. The objectives of this program are to (1) conduct system engineering and integration efforts to define the engine test-bed configuration; (2) develop selected noise reduction technologies to a technical maturity sufficient to enable engine testing and validation of those technologies in the FY06-07 time frame; (3) conduct engine tests designed to gain insight into the sources, mechanisms and characteristics of noise in the engines; and (4) establish baseline engine noise measurements for subsequent use in the evaluation of noise reduction.

Weir, Don

Multivariable control altitude demonstration on the F100 turbofan engine

The F100 Multivariable control synthesis (MVCS) program, was aimed at demonstrating the benefits of LGR synthesis theory in the design of a multivariable engine control system for operation throughout the flight envelope. The advantages of such procedures include: (1) enhanced performance from cross-coupled controls, (2) maximum use of engine variable geometry, and (3) a systematic design procedure that can be applied efficiently to new engine systems. The control system designed, under the MVCS program, for the Pratt & Whitney F100 turbofan engine is described. Basic components of the control include: (1) a reference value generator for deriving a desired equilibrium state and an approximate control vector, (2) a transition model to produce compatible reference point trajectories during gross transients, (3) gain schedules for producing feedback terms appropriate to the flight condition, and (4) integral switching logic to produce acceptable steady-state performance without engine operating limit exceedance.

Lehtinen, B.

Human Systems Integration in Practice: Constellation Lessons Learned

NASA's Constellation program provided a unique testbed for Human Systems Integration (HSI) as a fundamental element of the Systems Engineering process. Constellation was the first major program to have HSI mandated by NASA's Human Rating document. Proper HSI is critical to the success of any project that relies on humans to function as operators, maintainers, or controllers of a system. HSI improves mission, system and human performance, significantly reduces lifecycle costs, lowers risk and minimizes re-design. Successful HSI begins with sufficient project schedule dedicated to the generation of human systems requirements, but is by no means solely a requirements management process. A top-down systems engineering process that recognizes throughout the organization, human factors as a technical discipline equal to traditional engineering disciplines with authority for the overall system. This partners with a bottoms-up mechanism for human-centered design and technical issue resolution. The Constellation Human Systems Integration Group (HSIG) was a part of the Systems Engineering and Integration (SE&I) organization within the program office, and existed alongside similar groups such as Flight Performance, Environments & Constraints, and Integrated Loads, Structures and Mechanisms. While the HSIG successfully managed, via influence leadership, a down-and-in Community of Practice to facilitate technical integration and issue resolution, it lacked parallel top-down authority to drive integrated design. This presentation will discuss how HSI was applied to Constellation, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers. This presentation will discuss how Human Systems Integration (HSI) was applied to NASA's Constellation program, the lessons learned and best practices it revealed, and recommendations to future NASA program and project managers on how to accomplish this critical function.

Zumbado, Jennifer Rochlis

Coal conversion systems design and process modeling. Volume 1: Application of MPPR and Aspen computer models

The development of a coal gasification system design and mass and energy balance simulation program for the TVA and other similar facilities is described. The materials-process-product model (MPPM) and the advanced system for process engineering (ASPEN) computer program were selected from available steady state and dynamic models. The MPPM was selected to serve as the basis for development of system level design model structure because it provided the capability for process block material and energy balance and high-level systems sizing and costing. The ASPEN simulation serves as the basis for assessing detailed component models for the system design modeling program. The ASPEN components were analyzed to identify particular process blocks and data packages (physical properties) which could be extracted and used in the system design modeling program. While ASPEN physical properties calculation routines are capable of generating physical properties required for process simulation, not all required physical property data are available, and must be user-entered.

Source record

PCACE-Personal-Computer-Aided Cabling Engineering

PCACE computer program developed to provide inexpensive, interactive system for learning and using engineering approach to interconnection systems. Basically database system that stores information as files of individual connectors and handles wiring information in circuit groups stored as records. Directly emulates typical manual engineering methods of handling data, thus making interface between user and program very natural. Apple version written in P-Code Pascal and IBM PC version of PCACE written in TURBO Pascal 3.0

Billitti, Joseph W.

1999 NASA Seal/secondary Air System Workshop

NASA Glenn hosted the Seals/Secondary Air System Workshop on October 28-29, 1999. Each year NASA and our industry and university partners share their respective seal technology development. We use these workshops as a technical forum to exchange recent advancements and "lessons-leamed" in advancing seal technology and solving problems of common interest. As in the past we are publishing two volumes. Volume 1 will be publicly available and volume 2 will be restricted under International Traffic and Arms Regulations (I.T.A.R.). The 1999 NASA Seal/Secondary Air System Workshop was divided into four areas; (i) overviews of the government-sponsored gas turbine programs (NASA Ultra Efficient Engine Technology program and DOE Advanced Turbine System program) and the general aviation program (GAP) with emphasis on program goals and seal needs; (ii) turbine engine seal issues from the perspective of an airline customer (i.e., United Airlines), (iii) sealing concepts, methods and results including experimental facilities and numerical predictions; and (iv) reviews of seal requirements for next generation aerospace vehicles (Trailblazer, Bantam and X-38).

Steinetz, Bruce M.

Seven Key Principles of Program and Project Success: A Best Practices Survey

The National Aeronautics and Space Administration (NASA) Organization Design Team (ODT), consisting of 20 seasoned program and project managers and systems engineers from a broad spectrum of the aerospace industry, academia, and government, was formed to support the Next Generation Launch Technology (NGLT) Program and the Constellation Systems Program. The purpose of the ODT was to investigate organizational factors that can lead to success or failure of complex government programs, and to identify tools and methods for the design, modeling, and analysis of new and more-efficient program and project organizations. The ODT conducted a series of workshops featuring invited lectures from seasoned program and project managers representing 25 significant technical programs spanning 50 years of experience. The result was the identification of seven key principles of program success that can be used to help design and operate future program organizations. This paper presents the success principles and examples of best practices that can significantly improve the design of program, project, and performing technical line organizations, the assessment of workforce needs and organization performance, and the execution of programs and projects.

Bilardo, Vincent J.

Future Model-Based Systems Engineering Vision and Strategy Bridge for NASA

A vision for the future of model-based systems engineering (MBSE) at NASA in 2029 and a strategy bridge towards that future are presented. Strategic thinking and leading change concepts were used to analyze reports and presentations on global trends and visionary thinking about the future of systems and digital engineering. The context, strategic time horizon, stakeholders, strategic challenges, strategic advantages, driving forces, and opportunities were considered. The analysis resulted in a future vision of MBSE that shows what NASA systems engineers and digital machines will do to perform rapid, extraordinary, and unprecedented missions. The NASA systems engineer, in this future vision, works with a global project team in a virtual and collaborative environment, engineers the system, and uses digital approaches as the routine and default way of working. The digital machines provide data-driven and automated mission designs; have a backbone of program and project management, systems engineering, and product life-cycle management; and are a knowledge-sharing infrastructure. The NASA systems engineer and the systems engineering team are envisioned to use digital machines to plan and perform rapid exploration missions, develop a digital twin that lasts across the life cycle, and develop enduring and adaptable systems. NASA has an engineering enterprise and a life-cycle management framework that endure, adapt, and respond. A strategy bridge based on the Baldrige Criteria for Performance Excellence Framework and lessons learned from a recent MBSE initiative illuminates a way forward from today to this desired future. The bridge lays out a strategy for leaders and recommends investments of today for immediate benefits and for benefits in 2029.

model-based systems engineering, digital engineeri