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.
Space Research Project Management Can Benefit from Engineering Technology Selection Methods
No abstract available
Technical Basis for Engineering Feasibility and Thermal Management.
Abstract not provided.
Technical Basis for Engineering Feasibility and Thermal Management.
Abstract not provided.
CONFIG: Qualitative simulation tool for analyzing behavior of engineering devices
To design failure management expert systems, engineers mentally analyze the effects of failures and procedures as they propagate through device configurations. CONFIG is a generic device modeling tool for use in discrete event simulation, to support such analyses. CONFIG permits graphical modeling of device configurations and qualitative specification of local operating modes of device components. Computation requirements are reduced by focussing the level of component description on operating modes and failure modes, and specifying qualitative ranges of variables relative to mode transition boundaries. Simulation processing occurs only when modes change or variables cross qualitative boundaries. Device models are built graphically, using components from libraries. Components are connected at ports by graphical relations that define data flow. The core of a component model is its state transition diagram, which specifies modes of operation and transitions among them.
Planetary Protection is Not a One Size Fits All Missions Approach: Enabling the Planetary Protection Programmatic and Engineering Process
Missions have a wide range of variables that change their management and engineering structure (e.g., competed vs directed missions, multiple NASA centers, international partnerships, increased commercial collaborations, etc.). Why would an identical planetary protection approach and structure for each mission make sense in this evolving landscape? Missions do not fit in a one-size-fits-all approach, likewise their planetary protection process should not be a one-size-fits-all approach. During the significant update to NPR 8715.24 and NASA-STD-8719.27 planetary protection policies, the programmatic execution and engineering implementation processes were changed to provide clarification, streamlining, and expansion to include alternative approaches. From a programmatic perspective, these changes include the flexibility in timing and combination of gate products in addition to providing varying levels of technical depth commensurate and appropriate with the mission categorization. From a technical perspective, these changes include the ability to A) leverage either a performance-based and/or a prescriptive-based approach, B) identify applicable international consensus standards for verification, and C) propose alternative methods that adhere to sound scientific and engineering consensus. This presentation will directly highlight the culture shift in planetary protection, areas of flexibility available to the technical community for mission program and engineering execution, and feature some of the specific mission scenarios that have already leveraged such processes.
Probabilistic Study Conducted on Sensor-Based Engine Life Calculation
Turbine engine life management is a very complicated process to ensure the safe operation of an engine subjected to complex usage. The challenge of life management is to find a reasonable compromise between the safe operation and the maximum usage of critical parts to reduce maintenance costs. The commonly used "cycle count" approach does not take the engine operation conditions into account, and it oversimplifies the calculation of the life usage. Because of the shortcomings, many engine components are regularly pulled for maintenance before their usable life is over. And, if an engine has been running regularly under more severe conditions, components might not be taken out of service before they exceed their designed risk of failure. The NASA Glenn Research Center and its industrial and academic partners have been using measurable parameters to improve engine life estimation. This study was based on the Monte Carlo simulation of 5000 typical flights under various operating conditions. First a closed-loop engine model was developed to simulate the engine operation across the mission profile and a thermomechanical fatigue (TMF) damage model was used to calculate the actual damage during takeoff, where the maximum TMF accumulates. Next, a Weibull distribution was used to estimate the implied probability of failure for a given accumulated cycle count. Monte Carlo simulations were then employed to find the profiles of the TMF damage under different operating assumptions including parameter uncertainties. Finally, probabilities of failure for different operating conditions were analyzed to demonstrate the importance of a sensor-based damage calculation in order to better manage the risk of failure and on-wing life.
ISO 9000 and/or Systems Engineering Capability Maturity Model?
For businesses and organizations to remain competitive today they must have processes and systems in place that will allow them to first identify customer needs and then develop products/processes that will meet or exceed the customers needs and expectations. Customer needs, once identified, are normally stated as requirements. Designers can then develop products/processes that will meet these requirements. Several functions, such as quality management and systems engineering management are used to assist product development teams in the development process. Both functions exist in all organizations and both have a similar objective, which is to ensure that developed processes will meet customer requirements. Are efforts in these organizations being duplicated? Are both functions needed by organizations? What are the similarities and differences between the functions listed above? ISO 9000 is an international standard of goods and services. It sets broad requirements for the assurance of quality and for management's involvement. It requires organizations to document the processes and to follow these documented processes. ISO 9000 gives customers assurance that the suppliers have control of the process for product development. Systems engineering can broadly be defined as a discipline that seeks to ensure that all requirements for a system are satisfied throughout the life of the system by preserving their interrelationship. The key activities of systems engineering include requirements analysis, functional analysis/allocation, design synthesis and verification, and system analysis and control. The systems engineering process, when followed properly, will lead to higher quality products, lower cost products, and shorter development cycles. The System Engineering Capability Maturity Model (SE-CMM) will allow companies to measure their system engineering capability and continuously improve those capabilities. ISO 9000 and SE-CMM seem to have a similar objective, which is to document the organization's processes and certify to potential customers the capability of a supplier to control the processes that determine the quality of the product or services being produced. The remaining sections of this report examine the differences and similarities between ISO 9000 and SE-CMM and make recommendations for implementation.
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.
Evaluation of Howard A. Hanson Dam Juvenile Fish Passage and Survival Study: Downstream Passage and Survival (Acoustic Telemetry) (Task Final Report)
The Downstream Passage and Survival (Acoustic Telemetry) task was one of several tasks for the Evaluation of Howard A. Hanson Dam (HAHD) Juvenile Fish Passage and Survival study. For this task, a juvenile fish passage and survival study was conducted at HAHD from March 10, 2024 through June 27, 2024 for arrays in the HAHD Reservoir and Green River, and through July 9, 2024 for the arrays in the Duwamish River. Fish releases occurred over four times from March through May. Active tag (acoustic telemetry) technology was used to provide biological baseline information for the passage and survival of juvenile Puget Sound (PS) Chinook salmon (Oncorhynchus tshawytscha). Results will be used by biologists, engineers, resource managers, and regional decision-makers to inform the engineering design of the new fish passage facility (FPF) at HAHD. However, hatchery sub-yearling PS Chinook salmon of the appropriate size for tag implantation during the study period (> 95 mm in fork length, Geist et al. 2018) were unavailable. Therefore, yearling Coho salmon (O. kisutch) were used as a surrogate species for this acoustic telemetry study.
User's Manual for the Naval Interactive Data Analysis System-Climatologies (NIDAS-C), Version 2.0
This technical note provides the user's manual for the NIDAS-C system developed for the naval oceanographic office. NIDAS-C operates using numerous oceanographic data categories stored in an installed version of the Naval Environmental Operational Nowcast System (NEONS), a relational database management system (rdbms) which employs the ORACLE proprietary rdbms engine. Data management, configuration, and control functions for the supporting rdbms are performed externally. NIDAS-C stores and retrieves data to/from the rdbms but exercises no direct internal control over the rdbms or its configuration. Data is also ingested into the rdbms, for use by NIDAS-C, by external data acquisition processes. The data categories employed by NIDAS-C are as follows: Bathymetry - ocean depth at
Recommendations on the Use of Commercial-Off-The-Shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) Parts for NASA Missions - Phase II
This assessment had two Phases. Phase I captured NASA Centers’ current practices for commercial-off-the-shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) parts 1 used in spaceflight systems and ground support equipment (available at https://ntrs.nasa.gov/citations/20205011579) [ref. 1]. The Phase II report provides guidance for selecting and using COTS parts in NASA missions. The approaches proposed in this report differ from current agency practices. This top-level executive summary touches on these new approaches for using COTS parts but does not provide the detailed information that is critical in understanding the rationale behind these new approaches. Readers will need to read the entire report to gain full understanding and effectively use the recommendations herein. NASA’s historical approach to selecting and applying parts has been to define certain parts, primarily specific classes of military specification (MIL-SPEC) parts, as “standard”, leaving all others, including COTS parts, as nonstandard. Standard parts typically are used without further testing (“use-as-is”). Nonstandard parts are subjected to initial screening and subsequent lot acceptance testing of representative samples from each procured lot per MIL-SPEC or similar requirements. Decades later, top-tier commercial part manufacturers have evolved significant manufacturing, statistical control, and technological improvements that can now provide parts as reliable or more reliable than MIL-SPEC parts, when used within their datasheet limits. Concurrently, the space science and exploration community’s needs demand technological advances unavailable with MIL-SPEC parts. This ongoing change necessitates using COTS parts for space missions. Properly selected COTS parts in appropriate applications can offer performance and supply availability advantages compared to MIL-SPEC parts. Their utility and demonstrated reliability result from large volumes and automated production and testing processes. However, careful review and a thorough understanding of their specifications (i.e., datasheet limitations) is needed, and verifying that manufacturer specifications and reliability meet space hardware application needs are necessary. This report recommends MIL-SPEC screening and non-radiation-related lot acceptance testing be reduced or eliminated in cases where evidence of sufficient quality and reliability exists for COTS parts. The extent of NASA's insight into COTS manufacturers and the amount and nature of the needed evidence will differ by mission and will likely be driven by a mission's resources and associated risk posture. To facilitate this goal, two new terminologies have been defined and described: “Industry Leading Parts Manufacturer (ILPM)” and “Established COTS parts.” An ILPM is a COTS manufacturer that produces high quality and reliable parts. Some parts produced by ILPMs, defined as Established COTS parts, do not need any additional MIL-SPEC or NASA screening and lot acceptance testing to be used in space applications. This report provides guidance for selecting, procuring, and applying COTS parts and for performing part-, board-, and system-level COTS parts verification. The recommendation to select Established COTS parts from ILPMs will assure those COTS parts will have comparable quality to corresponding MIL-SPEC parts. Selecting, applying, and verifying Established COTS parts from ILPMs requires a holistic team approach, engaging parts engineers, circuit designers, quality, reliability, and systems engineers, procurement specialists, radiation specialists, avionics leads, and program/project managers. A mission-specific approach tailored to a project’s Mission, Environment, Applications and Lifetime (MEAL) [ref. 2] requirements should be developed and approved by program/project managers. Any associated risks should be clearly identified, quantified, mitigated, and/or accepted. Different approaches are recommended according to program/project Risk Classes A, B, C, and D [ref. 3] and human-rated missions [ref. 4]: 1. Recommend Classes A and B and human-rated missions consider a “MIL-SPEC parts- based design” approach. ”MIL-SPEC parts-based design” approach is one in which most parts are MIL-SPEC parts and Established COTS parts from ILPMs are used only when an equivalent MIL-SPEC part does not meet functional or size, weight, and power (SWaP) or performance requirements, or is not available. 2. Recommend Classes D and Sub-D missions consider a “System of COTS” approach. “System of COTS” approach is one which most parts are Established COTS parts from ILPMs. 3. Recommend Class C missions determine which approach is the best for their projects; that is, use either a “MIL-SPEC parts-based design” approach, “System of COTS” approach, or a combined approach utilizing elements of both. This report intends to provide guidance in using COTS parts for NASA missions with risk classifications of A through D and human-rated missions; but it does not address the costs of using COTS parts. Costs of using COTS parts in different NASA mission classes can vary significantly even if the same parts are used in different risk postures, due to differing verification levels needed. The guidance does not distinguish between critical or non-critical systems, and a given project will need to apply the appropriate guidance based on their risk posture. The intended audience of this report are NASA personnel and commercial practitioners who support NASA’s spaceflight missions, including spaceflight program or project managers, parts engineers, parts manufacturers, radiation engineers, avionics engineers, system engineers, circuit design engineers, reliability engineers, safety and mission assurance (SMA) personnel, and parts procurement specialists. The NEPP Program will perform a pathfinder study to explore implementing the guidance in this NESC report. An ILPM verification process is not the same as conventional vendor qualification processes performed according to military standards and specifications. This NESC report intends to provide guidance in utilizing available parts data from ILPM manufacturers for parts assurance assessments needed for NASA missions. The report also captured the current practices from DoD and Federal Aviation Administration (FAA) in Section 10. Note each DoD and FAA report was provided by the corresponding agencies regarding their practices, which are independent from the NESC recommendations in the report.
NASA-JAXA Joint Management Approach for Upper Stage Engine System Development
Define an overarching set of agreements, approaches, and assumptions to manage the NASA/JAXA collaboration in the form of a joint implementation plan.
Use of Soft Computing Technologies For Rocket Engine Control
The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to further improve overall engine system reliability and performance. Specifically, this will be presented by enhancing rocket engine control and engine health management (EHM) using SCT coupled with conventional control technologies, and sound software engineering practices used in Marshall s Flight Software Group. The principle goals are to improve software management, software development time and maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control and EHM methodologies, but to provide alternative design choices for control, EHM, implementation, performance, and sustaining engineering. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion, software engineering for embedded systems, and soft computing technologies (i.e., neural networks, fuzzy logic, and Bayesian belief networks), much of which is presented in this paper. The first targeted demonstration rocket engine platform is the MC-1 (formerly FASTRAC Engine) which is simulated with hardware and software in the Marshall Avionics & Software Testbed laboratory that
Management techniques - A compilation
Engineering, finance, and personnel management methods and computer techniques for cost reduction and reliability in project planning
Transient Optimization for the Betterment of Turbine Electrified Energy Management
Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.
General purpose simulation system of the data management system for space shuttle mission 18
The simulation program of the science and engineering data management system for the space shuttle is presented. The programming language used was General Purpose Simulation System V (OS). The data flow was modeled from its origin at the experiments or subsystems to transmission from the space shuttle. Mission 18 was the particular flight chosen for simulation. First, the general structure of the program is presented and the trade studies which were performed are identified. Inputs required to make runs are discussed followed by identification of the output statistics. Some areas for model modifications are pointed out. A detailed model configuration, program listing and results are included.
Transient Optimization for the Betterment of Turbine Electrified Energy Management
Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.