SEARCH · Engineering Papers

Results for “Engineering management”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5

All sources NASA NTRS DOE OSTI

NASA NTRS2005

A Management Model for International Participation in Space Exploration Missions

This paper proposes an engineering management model for NASA's future space exploration missions based on past experiences working with the International Partners of the International Space Station. The authors have over 25 years of combined experience working with the European Space Agency, Japan Aerospace Exploration Agency, Canadian Space Agency, Italian Space Agency, Russian Space Agency, and their respective contractors in the design, manufacturing, verification, and integration of their elements electric power system into the United States on-orbit segment. The perspective presented is one from a specific sub-system integration role and is offered so that the lessons learned from solving issues of technical and cultural nature may be taken into account during the formulation of international partnerships. Descriptions of the types of unique problems encountered relative to interactions between international partnerships are reviewed. Solutions to the problems are offered, taking into consideration the technical implications. Through the process of investigating each solution, the important and significant issues associated with working with international engineers and managers are outlined. Potential solutions are then characterized by proposing a set of specific methodologies to jointly develop spacecraft configurations that benefits all international participants, maximizes mission success and vehicle interoperability while minimizing cost.

George, Patrick J.↗

NASA NTRS1991

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗

NASA NTRS2013

Horizontal Habitability Layout Studies

As our efforts in the 2011-2012 X-Hab Academic Innovation Challenge we designed, developed, constructed and tested a deployable horizontally oriented habitat system for use as an Earth analog. The goals of the project included a short-term goal of an interdisciplinary senior design project to design, build and evaluate a horizontally oriented habitat and a long-term goal to develop capabilities in education, research, and outreach in field of space habitat design. This included both technical engineering and outreach efforts. In the 2011-2012 year, the program involved the following schools at OSU: The Schools of Mechanical and Aerospace Engineering (MAE) and Industrial and Engineering Management (IEM) within the College of Engineering, Architecture and Technology and Design, Housing and Merchandising (DHM) in the College of Human Sciences. We also included the School of Aviation Education (AvED) in the College of Education through the ISNPIRE (Interdisciplinary National Science Project Incorporating Research and Education Experience) program of as part of our outreach efforts.

Jamey D. Jacob↗

NASA NTRS1991

NASA Software Documentation Standard

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗

NASA NTRS1975

Apollo experience report: Safety activities

A description is given of the flight safety experiences gained during the Apollo Program and safety, from the viewpoint of program management, engineering, mission planning, and ground test operations was discussed. Emphasis is placed on the methods used to identify the risks involved in flight and in certain ground test operations. In addition, there are discussions on the management and engineering activities used to eliminate or reduce these risks.

Rice, C. N.↗

NASA NTRS1991

Structured prototyping as risk management

A methodology is presented for integrating the systems-engineering management recommendation of prototyping into the traditional project-management process for developing large-scale systems. The suggested methodology begins with the identification of life-cycle risk areas, outlines the structure and conduct of the prototyping process, and defines the composition of the prototyping team. The methodology includes a step-by-step procedure for creating, executing, and documenting a prototyping test plan to evaluate design alternatives. It is argued that managers who adopt this methodology and apply it rigorously will increase the likelihood that the systems they build will be operationally effective and will be accepted by the intended users.

Hornstein, Rhoda SH.↗

NASA NTRS2005

Key Reliability Drivers of Liquid Propulsion Engines and A Reliability Model for Sensitivity Analysis

This paper is to address the in-flight reliability of a liquid propulsion engine system for a launch vehicle. We first establish a comprehensive list of system and sub-system reliability drivers for any liquid propulsion engine system. We then build a reliability model to parametrically analyze the impact of some reliability parameters. We present sensitivity analysis results for a selected subset of the key reliability drivers using the model. Reliability drivers identified include: number of engines for the liquid propulsion stage, single engine total reliability, engine operation duration, engine thrust size, reusability, engine de-rating or up-rating, engine-out design (including engine-out switching reliability, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction), propellant specific hazards, engine start and cutoff transient hazards, engine combustion cycles, vehicle and engine interface and interaction hazards, engine health management system, engine modification, engine ground start hold down with launch commit criteria, engine altitude start (1 in. start), Multiple altitude restart (less than 1 restart), component, subsystem and system design, manufacturing/ground operation support/pre and post flight check outs and inspection, extensiveness of the development program. We present some sensitivity analysis results for the following subset of the drivers: number of engines for the propulsion stage, single engine total reliability, engine operation duration, engine de-rating or up-rating requirements, engine-out design, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction, and engine health management system implementation (basic redlines and more advanced health management systems).

Huang, Zhao-Feng↗

NASA NTRS1995

Generic Health Management: A System Engineering Process Handbook Overview and Process

Health Management, a System Engineering Process, is one of those processes-techniques-and-technologies used to define, design, analyze, build, verify, and operate a system from the viewpoint of preventing, or minimizing, the effects of failure or degradation. It supports all ground and flight elements during manufacturing, refurbishment, integration, and operation through combined use of hardware, software, and personnel. This document will integrate Health Management Processes (six phases) into five phases in such a manner that it is never a stand alone task/effort which separately defines independent work functions.

Wilson, Moses Lee↗

NASA NTRS1995

Earth Sciences Data and Information System (ESDIS) program planning and evaluation methodology development

An Earth Sciences Data and Information System (ESDIS) Project Management Plan (PMP) is prepared. An ESDIS Project Systems Engineering Management Plan (SEMP) consistent with the developed PMP is also prepared. ESDIS and related EOS program requirements developments, management and analysis processes are evaluated. Opportunities to improve the effectiveness of these processes and program/project responsiveness to requirements are identified. Overall ESDIS cost estimation processes are evaluated, and recommendations to improve cost estimating and modeling techniques are developed. ESDIS schedules and scheduling tools are evaluated. Risk assessment, risk mitigation strategies and approaches, and use of risk information in management decision-making are addressed.

Dickinson, William B.↗

NASA NTRS1991

A design strategy for the use of vortex generators to manage inlet-engine distortion using computational fluid dynamics

A reduced Navier-Stokes solution technique was successfully used to design vortex generator installations for the purpose of minimizing engine face distortion by restructuring the development of secondary flow that is induced in typical 3-D curved inlet ducts. The results indicate that there exists an optimum axial location for this installation of corotating vortex generators, and within this configuration, there exists a maximum spacing between generator blades above which the engine face distortion increases rapidly. Installed vortex generator performance, as measured by engine face circumferential distortion descriptors, is sensitive to Reynolds number and thereby the generator scale, i.e., the ratio of generator blade height to local boundary layer thickness. Installations of corotating vortex generators work well in terms of minimizing engine face distortion within a limited range of generator scales. Hence, the design of vortex generator installations is a point design, and all other conditions are off design. In general, the loss levels associated with a properly designed vortex generator installation are very small; thus, they represent a very good method to manage engine face distortion. This study also showed that the vortex strength, generator scale, and secondary flow field structure have a complicated and interrelated influence over engine face distortion, over and above the influence of the initial arrangement of generators.

Anderson, Bernhard H.↗

NASA NTRS1991

A design strategy for the use of vortex generators to manage inlet-engine distortion using computational fluid dynamics

Anderson, Bernhard H.↗

NASA NTRS1972

GREMEX - A management game for the new public administration.

This is a critique of a new management game being used in the federal government - Goddard Research Engineering Management Exercise (GREMEX). The exercise involves teams of players who act as managers of a research and development project - the orbiting optical observatory - of the National Aeronautics and Space Administration. During this exercise a computer and the referee-instructor together provide the realistic environment within which the team participants make their decisions affecting the course of the project. The article discusses the place of GREMEX in a tradition of games and simulations, and notes the similarities and differences between GREMEX and other management games currently in use for business training. Some of the actual decisions being made by the GREMEX teams are described to illustrate the nature of the exercise.

Mcgregor, E. B.↗

NASA NTRS2018

History and Archives Contribute to the Success of Space Flight Programs

Final Paper, not the Abstract, is attached: This report discusses how history can be used by management, engineering, and operations personnel within space flight programs. Works by professional historians and sociologists inform key decision makers and policy specialists on lessons learned from space flight program management successes and failures, as well as from legislative affairs, policy making, and commercial space efforts. Vehicle engineering history written by engineers for an engineering or operations audience informs project management and technical personnel on lessons learned, best practices, and the rationale behind the design and operation of flight vehicles and supporting ground systems. Archives play a critical role in supporting the efforts of both professional historians and flight program personnel. Suggestions are made concerning how professional historians could leverage the interests and knowledge of flight program personnel to obtain more insight that is needed to support historical research efforts.

Archive↗

NASA NTRS1994

Engineering, technical, and management support services

This report summarizes by task the engineering, technical, and management support services provided by Vitro Corporation to NASA Headquarters Office of Safety, Reliability, Maintainability, and Quality Assurance (now called Office of Safety and Mission Assurance (OSMA)) (Code Q) under Contract Number NASW-4311 from the period February 10, 1994. Each task summary includes significant Vitro accomplishments, conclusions, and recommendations for future efforts in each of the divisions within OSMA.

Source record↗

NASA NTRS2011

SOFIA Program SE and I Lessons Learned

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Ray, Ronald 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↗

NASA NTRS1999

Reusable Rocket Engine Advanced Health Management System. Architecture and Technology Evaluation: Summary

In this study, we proposed an Advanced Health Management System (AHMS) functional architecture and conducted a technology assessment for liquid propellant rocket engine lifecycle health management. The purpose of the AHMS is to improve reusable rocket engine safety and to reduce between-flight maintenance. During the study, past and current reusable rocket engine health management-related projects were reviewed, data structures and health management processes of current rocket engine programs were assessed, and in-depth interviews with rocket engine lifecycle and system experts were conducted. A generic AHMS functional architecture, with primary focus on real-time health monitoring, was developed. Fourteen categories of technology tasks and development needs for implementation of the AHMS were identified, based on the functional architecture and our assessment of current rocket engine programs. Five key technology areas were recommended for immediate development, which (1) would provide immediate benefits to current engine programs, and (2) could be implemented with minimal impact on the current Space Shuttle Main Engine (SSME) and Reusable Launch Vehicle (RLV) engine controllers.

Pettit, C. D.↗

NASA NTRS1981

A case study of the influences of audience and purpose on the composing processes of an engineer

The design and preliminary findings of a study of composing processes (on the job) of engineers, managers, and scientists is presented. The influences of audience and purpose on the composing process of engineers was of concern; specifically, the cognitive processes, physical behaviors, and factors that influence the evoluton of a piece of writing. An overview of the study, related literature, outlines of research design, and preliminary findings from a case study of engineers are given. It is suggested that teaching be adapted to help students learn to represent rhetorical problems to guide composing for effective writing.

Stalnaker, B. J.↗