Engineering Papers⌕ Search

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.

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

At least 559 records · Page 31

NASA System Safety Handbook: System Safety Framework and Concepts for Implementation - Volume 1

System safety assessment is defined in NPR 8715.3C, NASA General Safety Program Requirements as a disciplined, systematic approach to the analysis of risks resulting from hazards that can affect humans, the environment, and mission assets. Achievement of the highest practicable degree of system safety is one of NASA's highest priorities. Traditionally, system safety assessment at NASA and elsewhere has focused on the application of a set of safety analysis tools to identify safety risks and formulate effective controls.1 Familiar tools used for this purpose include various forms of hazard analyses, failure modes and effects analyses, and probabilistic safety assessment (commonly also referred to as probabilistic risk assessment (PRA)). In the past, it has been assumed that to show that a system is safe, it is sufficient to provide assurance that the process for identifying the hazards has been as comprehensive as possible and that each identified hazard has one or more associated controls. The NASA Aerospace Safety Advisory Panel (ASAP) has made several statements in its annual reports supporting a more holistic approach. In 2006, it recommended that "... a comprehensive risk assessment, communication and acceptance process be implemented to ensure that overall launch risk is considered in an integrated and consistent manner." In 2009, it advocated for "... a process for using a risk-informed design approach to produce a design that is optimally and sufficiently safe." As a rationale for the latter advocacy, it stated that "... the ASAP applauds switching to a performance-based approach because it emphasizes early risk identification to guide designs, thus enabling creative design approaches that might be more efficient, safer, or both." For purposes of this preface, it is worth mentioning three areas where the handbook emphasizes a more holistic type of thinking. First, the handbook takes the position that it is important to not just focus on risk on an individual basis but to consider measures of aggregate safety risk and to ensure wherever possible that there be quantitative measures for evaluating how effective the controls are in reducing these aggregate risks. The term aggregate risk, when used in this handbook, refers to the accumulation of risks from individual scenarios that lead to a shortfall in safety performance at a high level: e.g., an excessively high probability of loss of crew, loss of mission, planetary contamination, etc. Without aggregated quantitative measures such as these, it is not reasonable to expect that safety has been optimized with respect to other technical and programmatic objectives. At the same time, it is fully recognized that not all sources of risk are amenable to precise quantitative analysis and that the use of qualitative approaches and bounding estimates may be appropriate for those risk sources. Second, the handbook stresses the necessity of developing confidence that the controls derived for the purpose of achieving system safety not only handle risks that have been identified and properly characterized but also provide a general, more holistic means for protecting against unidentified or uncharacterized risks. For example, while it is not possible to be assured that all credible causes of risk have been identified, there are defenses that can provide protection against broad categories of risks and thereby increase the chances that individual causes are contained. Third, the handbook strives at all times to treat uncertainties as an integral aspect of risk and as a part of making decisions. The term "uncertainty" here does not refer to an actuarial type of data analysis, but rather to a characterization of our state of knowledge regarding results from logical and physical models that approximate reality. Uncertainty analysis finds how the output parameters of the models are related to plausible variations in the input parameters and in the modeling assumptions. The evaluation of unrtainties represents a method of probabilistic thinking wherein the analyst and decision makers recognize possible outcomes other than the outcome perceived to be "most likely." Without this type of analysis, it is not possible to determine the worth of an analysis product as a basis for making decisions related to safety and mission success. In line with these considerations the handbook does not take a hazard-analysis-centric approach to system safety. Hazard analysis remains a useful tool to facilitate brainstorming but does not substitute for a more holistic approach geared to a comprehensive identification and understanding of individual risk issues and their contributions to aggregate safety risks. The handbook strives to emphasize the importance of identifying the most critical scenarios that contribute to the risk of not meeting the agreed-upon safety objectives and requirements using all appropriate tools (including but not limited to hazard analysis). Thereafter, emphasis shifts to identifying the risk drivers that cause these scenarios to be critical and ensuring that there are controls directed toward preventing or mitigating the risk drivers. To address these and other areas, the handbook advocates a proactive, analytic-deliberative, risk-informed approach to system safety, enabling the integration of system safety activities with systems engineering and risk management processes. It emphasizes how one can systematically provide the necessary evidence to substantiate the claim that a system is safe to within an acceptable risk tolerance, and that safety has been achieved in a cost-effective manner. The methodology discussed in this handbook is part of a systems engineering process and is intended to be integral to the system safety practices being conducted by the NASA safety and mission assurance and systems engineering organizations. The handbook posits that to conclude that a system is adequately safe, it is necessary to consider a set of safety claims that derive from the safety objectives of the organization. The safety claims are developed from a hierarchy of safety objectives and are therefore hierarchical themselves. Assurance that all the claims are true within acceptable risk tolerance limits implies that all of the safety objectives have been satisfied, and therefore that the system is safe. The acceptable risk tolerance limits are provided by the authority who must make the decision whether or not to proceed to the next step in the life cycle. These tolerances are therefore referred to as the decision maker's risk tolerances. In general, the safety claims address two fundamental facets of safety: 1) whether required safety thresholds or goals have been achieved, and 2) whether the safety risk is as low as possible within reasonable impacts on cost, schedule, and performance. The latter facet includes consideration of controls that are collective in nature (i.e., apply generically to broad categories of risks) and thereby provide protection against unidentified or uncharacterized risks.

Dezfuli, Homayoon↗

Human Systems Integration (HSI) Practitioner's Guide

The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).

Zumbado, Jennifer Rochlis↗

What We Did Last Summer: Depicting DES Data to Enhance Simulation Utility and Use

At Kennedy Space Center (KSC), an important use of Discrete Event Simulation (DES) addresses ground operations .of missions to space. DES allows managers, scientists and engineers to assess the number of missions KSC can complete on a given schedule within different facilities, the effects of various configurations of resources and detect possible problems or unwanted situations. For fifteen years, DES has supported KSC efficiency, cost savings and improved safety and performance. The dense and abstract DES data, however, proves difficult to comprehend and, NASA managers realized, is subject to misinterpretation, misunderstanding and even, misuse. In summer 2008, KSC developed and implemented a NASA Exploration Systems Mission Directorate (ESMD) project based on the premise that visualization could enhance NASA's understanding and use of DES.

Elfrey, Priscilla↗

Requirements management at NASA

Requirements have always been acknowledged as the backbone of any system. However, in many past development efforts, requirements were paid little heed. At NASA, in recent years, the hue and cry for project development has been "Faster, Better, Cheaper and Safer". This has impacted the way we develop software; it has increased the risks to quality, safety and reliability. At NASA, the Software Assurance Technology Center (SATC) is working with projects to emphasize the criticality of requirements throughout development, not just in the initial phases. This emphasis is on requirements relationship to all aspects of quality, including reliability and safety. In this presentation, we will look at some of these relationships through the eyes of quality.

Requirement management↗

Descoping

Explore the source record for details and available documents.

requirements interaction management requirements e↗

Development and Implementation of A Small Satellite Systems Engineering Webinar Series: A Collaboration Between the United Nations Office for Outer Space Affairs and the National Aeronautics and Space Administration

The United Nations Office for Outer Space Affairs (UNOOSA) in collaboration with the National Aeronautics and Space Administration (NASA) established a webinar series on NASA systems engineering standards and practices for the purpose of sharing knowledge in this area. UNOOSA’s “Access to Space for All” initiative provides capacity-building opportunities in space science, technology, and space applications for United Nations member states. Due to the cooperation among established space actors, the United Nations, and emerging space entities, the initiative enables students from developing countries from all over the world to carry out projects using technologies and space applications. Through NASA’s Small Spacecraft Systems Virtual Institute (S3VI), the four-part webinar series was designed to cover basic systems engineering and project management skills that are fundamental to planning, developing, and implementing an experiment or a space project and that serve as critical knowledge for those engaged in space activities, whether as a designer, builder, or manager of space infrastructure and services. The first series of webinars was convened over the course of November 2023 through February 2024.

Systems Engineering↗

Risk Management Implementation Tool

Continuous Risk Management (CM) is a software engineering practice with processes, methods, and tools for managing risk in a project. It provides a controlled environment for practical decision making, in order to assess continually what could go wrong, determine which risk are important to deal with, implement strategies to deal with those risk and assure the measure effectiveness of the implemented strategies. Continuous Risk Management provides many training workshops and courses to teach the staff how to implement risk management to their various experiments and projects. The steps of the CRM process are identification, analysis, planning, tracking, and control. These steps and the various methods and tools that go along with them, identification, and dealing with risk is clear-cut. The office that I worked in was the Risk Management Office (RMO). The RMO at NASA works hard to uphold NASA s mission of exploration and advancement of scientific knowledge and technology by defining and reducing program risk. The RMO is one of the divisions that fall under the Safety and Assurance Directorate (SAAD). I worked under Cynthia Calhoun, Flight Software Systems Engineer. My task was to develop a help screen for the Continuous Risk Management Implementation Tool (RMIT). The Risk Management Implementation Tool will be used by many NASA managers to identify, analyze, track, control, and communicate risks in their programs and projects. The RMIT will provide a means for NASA to continuously assess risks. The goals and purposes for this tool is to provide a simple means to manage risks, be used by program and project managers throughout NASA for managing risk, and to take an aggressive approach to advertise and advocate the use of RMIT at each NASA center.

Wright, Shayla L.↗

Space Shuttle Main Engine (SSME) Options for the Future Shuttle

The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.

Jue, Fred↗

Managing the Software Development Process

The goal of any software development project is to produce a product that is delivered on time, within the allocated budget, and with the capabilities expected by the customer and unfortunately, this goal is rarely achieved. However, a properly managed project in a mature software engineering environment can consistently achieve this goal. In this paper we provide an introduction to three project success factors, a properly managed project, a competent project manager, and a mature software engineering environment. We will also present an overview of the benefits of a mature software engineering environment based on 24 years of data from the Software Engineering Lab, and suggest some first steps that an organization can take to begin benefiting from this environment. The depth and breadth of software engineering exceeds this paper, various references are cited with a goal of raising awareness and encouraging further investigation into software engineering and project management practices.

Lubelczky, Jeffrey T.↗

Configuration Management Process Assessment Strategy

Purpose: To propose a strategy for assessing the development and effectiveness of configuration management systems within Programs, Projects, and Design Activities performed by technical organizations and their supporting development contractors. Scope: Various entities CM Systems will be assessed dependent on Project Scope (DDT&E), Support Services and Acquisition Agreements. Approach: Model based structured against assessing organizations CM requirements including best practices maturity criteria. The model is tailored to the entity being assessed dependent on their CM system. The assessment approach provides objective feedback to Engineering and Project Management of the observed CM system maturity state versus the ideal state of the configuration management processes and outcomes(system). center dot Identifies strengths and risks versus audit gotcha's (findings/observations). center dot Used "recursively and iteratively" throughout program lifecycle at select points of need. (Typical assessments timing is Post PDR/Post CDR) center dot Ideal state criteria and maturity targets are reviewed with the assessed entity prior to an assessment (Tailoring) and is dependent on the assessed phase of the CM system. center dot Supports exit success criteria for Preliminary and Critical Design Reviews. center dot Gives a comprehensive CM system assessment which ultimately supports configuration verification activities.*

Henry, Thad↗

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

Proton exchange membrane fuel cells for space and electric vehicle applications: From basic research to technology development

The proton exchange membrane fuel cell (PEMFC) is one of the most promising electrochemical power sources for space and electric vehicle applications. The wide spectrum of R&D activities on PEMFC's, carried out in our Center from 1988 to date, is as follows (1) Electrode Kinetic and Electrocatalysis of Oxygen Reduction; (2) Optimization of Structures of Electrodes and of Membrane and Electrode Assemblies; (3) Selection and Evaluation of Advanced Proton Conducting Membranes and of Operating Conditions to Attain High Energy Efficiency; (4) Modeling Analysis of Fuel Cell Performance and of Thermal and Water Management; and (5) Engineering Design and Development of Multicell Stacks. The accomplishments on these tasks may be summarized as follows: (1) A microelectrode technique was developed to determine the electrode kinetic parameters for the fuel cell reactions and mass transport parameters for the H2 and O2 reactants in the proton conducting membrane. (2) High energy efficiencies and high power densities were demonstrated in PEMFCs with low platinum loading electrodes (0.4 mg/cm(exp 2) or less), advanced membranes and optimized structures of membrane and electrode assemblies, as well as operating conditions. (3) The modeling analyses revealed methods to minimize mass transport limitations, particularly with air as the cathodic reactant; and for efficient thermal and water management. (4) Work is in progress to develop multi-kilowatt stacks with the electrodes containing low platinum loadings.

Srinivasan, Supramaniam↗

An Educational Multimedia Presentation on the Introduction to Spacecraft Charging

Over the last few decades, significant knowledge has been gained in how to protect spacecraft from charging; however, the continuing technical advancement in the design and build of satellites requires on-going effort in the study of spacecraft charging. A situation that we have encountered is that not all satellite designers and builders are familiar with the problem of spacecraft charging. The design of a satellite involves many talented people with diverse backgrounds, ranging from manufacturing and assembly to engineering and program management. The complex design and build of a satellite system requires people with highly specialized skills such that cross-specialization is often not achievable. As a result, designers and builders of satellites are not usually familiar with the problems outside their specialization. This is also true for spacecraft charging. Not everyone is familiar with the definition of spacecraft charging and the damage that spacecraft charging can cause. Understanding the problem is an important first step in getting everyone involved in addressing the appropriate spacecraft charging issues during the satellite design and build phases. To address this important first step, an educational multimedia presentation has been created to inform the general engineering community about the basics of spacecraft charging. The content of this educational presentation is based on relevant published technical papers. The presentation was developed using Macromedia Flash. This software produces a more dynamic learning environment than a typical slide show , resulting in a more effective learning experience. The end result is that the viewer will have learned about the basics of spacecraft charging. This presentation is available to the public through our website, www.dplscience.com, free of charge. Viewers are encouraged to pass this presentation to colleagues within their own work environment. This paper describes the content of the multimedia presentation.

Lin, E.↗

Terrestrial Environment (Climatic) Criteria Handbook For Use in Aerospace Vehicle Development

An update of the NASA 'Terrestrial Environment (Climatic) Criteria Handbook for Use in Aerospace Vehicle Development' (NASA-HDBK-1001) is currently in the final process of completion for release in late-2004 or early 2005. The current version of the Handbook was approved by the NASA Chief Engineer in 2000 as a NASA Preferred Technical Standard. However, it was based on natural environment criteria developed mostly in the early 1990's. Therefore, a task was approved to completely update the Handbook in order to reflect the current state-of-the-art in the various terrestrial environmental climatic criteria areas. The technical areas include: Winds, atmospheric constituents, thermodynamic parameters/models/extremes, humidity, electricity, precipitation/fog/icing, cloud phenomena/cover, diffusion/toxic release, severe weather/tornado/hurricane, solar/thermal radiation, geologic hazards, and sea state. A summary of this extensive update will be presented along with some key examples of the new contents. Earlier versions of this publication have been extensively used by the aerospace community, especially program managers and design engineers for required natural terrestrial environment inputs to use in mission planning, development studies and trades, plus by those concerned with terrestrial environment descriptions for the major test ranges within the United States.

Johnson, Dale↗

Multi-level Simulation of a Real Time Vibration Monitoring System Component

This paper describes the development of a custom built Digital Signal Processing (DSP) printed circuit board designed to implement the Advanced Real Time Vibration Monitoring Subsystem proposed by MSFC Transportation Directorate in 2000 for the Space Shuttle Main Engine Advanced Health Management System (AHMS). This Real Time Vibration Monitoring System (RTVMS) is being developed for ground use as part of the AHMS Health Management Computer-Integrated Rack Assembly (HMC-IRA). The HMC-IRA RTVMS design contains five DSPs which are highly interconnected through individual communication ports, shared memory, and a unique communication router that allows all the DSPs to receive digitized data from two multi-channel analog boards simultaneously. This paper will briefly cover the overall board design but will focus primarily on the state-of-the-art simulation environment within which this board was developed. This 16-layer board with over 1800 components and an additional mezzanine card has been an extremely challenging design. Utilization of a Mentor Graphics simulation environment provided the unique board and system level simulation capability to ascertain any timing or functional concerns before production. By combining VHDL, Synopsys Software and Hardware Models, and the Mentor Design Capture Environment, multiple simulations were developed to verify the RTVMS design. This multi-level simulation allowed the designers to achieve complete operability without error the first time the RTVMS printed circuit board was powered. The HMCIRA design has completed all engineering unit testing and the deliverable unit is currently under development.

Roberston, Bryan↗

Multi-level Simulation of a Real Time Vibration Monitoring System Component

This paper describes the development of a custom built Digital Signal Processing (DSP) printed circuit board designed to implement the Advanced Real Time Vibration Monitoring Subsystem proposed by Marshall Space Flight Center (MSFC) Transportation Directorate in 2000 for the Space Shuttle Main Engine Advanced Health Management System (AHMS). This Real Time Vibration Monitoring System (RTVMS) is being developed for ground use as part of the AHMS Health Management Computer-Integrated Rack Assembly (HMC-IRA). The HMC-IRA RTVMS design contains five DSPs which are highly interconnected through individual communication ports, shared memory, and a unique communication router that allows all the DSPs to receive digitized data fiom two multi-channel analog boards simultaneously. This paper will briefly cover the overall board design but will focus primarily on the state-of-the-art simulation environment within which this board was developed. This 16-layer board with over 1800 components and an additional mezzanine card has been an extremely challenging design. Utilization of a Mentor Graphics simulation environment provided the unique board and system level simulation capability to ascertain any timing or functional concerns before production. By combining VHDL, Synopsys Software and Hardware Models, and the Mentor Design Capture Environment, multiple simulations were developed to verify the RTVMS design. This multi-level simulation allowed the designers to achieve complete operability without error the first time the RTVMS printed circuit board was powered. The HMC-IRA design has completed all engineering and deliverable unit testing. P

Robertson, Bryan A.↗

TRENDS: The aeronautical post-test database management system

TRENDS, an engineering-test database operating system developed by NASA to support rotorcraft flight tests, is described. Capabilities and characteristics of the system are presented, with examples of its use in recalling and analyzing rotorcraft flight-test data from a TRENDS database. The importance of system user-friendliness in gaining users' acceptance is stressed, as is the importance of integrating supporting narrative data with numerical data in engineering-test databases. Considerations relevant to the creation and maintenance of flight-test database are discussed and TRENDS' solutions to database management problems are described. Requirements, constraints, and other considerations which led to the system's configuration are discussed and some of the lessons learned during TRENDS' development are presented. Potential applications of TRENDS to a wide range of aeronautical and other engineering tests are identified.

Bjorkman, W. S.↗

Vortex generator installation studies on steady state and dynamic inlet distortion

The theoretical and experimental work carried out under the NASA/MOD Joint Aeronautical Program has shown that CFD vortex generator installations designs successfully managed inlet duct flow distortion and that significant benefits in flow unsteadiness at the engine face were also present. The main conclusions to date from the collaborative effort between NASA/Lewis and DRA/Bedford are as follows: (1) vortex generator installations can be designed to be effective over a wide range of inlet operating conditions using Computational Fluid Dynamics and formal optimization procedures, (2) reductions in steady state engine face distortion of up to 80% have been measured in the M2129 inlet S-duct using CFD designed vortex generator installations, (3) reductions in flow unsteadiness of up to 80% have been measured in the W129 inlet S-duct using CFD designed vortex generator installations, and (4) the Reduced Navier-Stokes code RNS3D is a useful tool to design vortex generator installations to manage engine face distortions over a wide range of inlet operating conditions.

Anderson, Bernhard H.↗