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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Automated Generation of Fault Management Artifacts from a Simple System Model

Our understanding of off-nominal behavior - failure modes and fault propagation - in complex systems is often based purely on engineering intuition; specific cases are assessed in an ad hoc fashion as a (fallible) fault management engineer sees fit. This work is an attempt to provide a more rigorous approach to this understanding and assessment by automating the creation of a fault management artifact, the Failure Modes and Effects Analysis (FMEA) through querying a representation of the system in a SysML model. This work builds off the previous development of an off-nominal behavior model for the upcoming Soil Moisture Active-Passive (SMAP) mission at the Jet Propulsion Laboratory. We further developed the previous system model to more fully incorporate the ideas of State Analysis, and it was restructured in an organizational hierarchy that models the system as layers of control systems while also incorporating the concept of "design authority". We present software that was developed to traverse the elements and relationships in this model to automatically construct an FMEA spreadsheet. We further discuss extending this model to automatically generate other typical fault management artifacts, such as Fault Trees, to efficiently portray system behavior, and depend less on the intuition of fault management engineers to ensure complete examination of off-nominal behavior.

Spinup and Orient↗
NASA NTRS2015

Closed Loop Requirements and Analysis Management

Effective systems engineering involves the use of analysis in the derivation of requirements and verification of designs against those requirements. The initial development of requirements often depends on analysis for the technical definition of specific aspects of a product. Following the allocation of system-level requirements to a product's components, the closure of those requirements often involves analytical approaches to verify that the requirement criteria have been satisfied. Meanwhile, changes that occur in between these two processes need to be managed in order to achieve a closed-loop requirement derivation/verification process. Herein are presented concepts for employing emerging Team center capabilities to jointly manage requirements and analysis data such that analytical techniques are utilized to effectively derive and allocate requirements, analyses are consulted and updated during the change evaluation processes, and analyses are leveraged during the design verification process. Recommendations on concept validation case studies are also discussed.

Lamoreaux, Michael↗
NASA NTRS1991

Configuration management plan. System definition and project development. Repository Based Software Engineering (RBSE) program

This is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.

Mckay, Charles↗
NASA NTRS2010

Integrated System Health Management: Pilot Operational Implementation in a Rocket Engine Test Stand

This paper describes a credible implementation of integrated system health management (ISHM) capability, as a pilot operational system. Important core elements that make possible fielding and evolution of ISHM capability have been validated in a rocket engine test stand, encompassing all phases of operation: stand-by, pre-test, test, and post-test. The core elements include an architecture (hardware/software) for ISHM, gateways for streaming real-time data from the data acquisition system into the ISHM system, automated configuration management employing transducer electronic data sheets (TEDS?s) adhering to the IEEE 1451.4 Standard for Smart Sensors and Actuators, broadcasting and capture of sensor measurements and health information adhering to the IEEE 1451.1 Standard for Smart Sensors and Actuators, user interfaces for management of redlines/bluelines, and establishment of a health assessment database system (HADS) and browser for extensive post-test analysis. The ISHM system was installed in the Test Control Room, where test operators were exposed to the capability. All functionalities of the pilot implementation were validated during testing and in post-test data streaming through the ISHM system. The implementation enabled significant improvements in awareness about the status of the test stand, and events and their causes/consequences. The architecture and software elements embody a systems engineering, knowledge-based approach; in conjunction with object-oriented environments. These qualities are permitting systematic augmentation of the capability and scaling to encompass other subsystems.

Figueroa, Fernando↗
NASA NTRS2016

Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)

The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.

Vipavetz, Kevin↗
NASA NTRS2018

Turbine Electrified Energy Management (TEEM) For Enabling More Efficient Engine Designs

NASA is investing in Electrified Aircraft Propulsion (EAP) research as part of an effort to assist industry in meeting the future needs of a global aviation market. The integration of electric machines into traditional turbine-based propulsion provides opportunities to change system architectures effecting radical improvements in propulsive efficiency. However, less consideration has been afforded to the utilization of these electrical machines to improve the thermal efficiency and performance of the gas turbine engine. Noting this deficit, a novel operability concept is proposed and is referred to as Turbine Electrified Energy Management (TEEM). The concept is a transient control technology that supplements the main fuel control for the suppression of the natural off-design dynamics associated with changes in engine operating state. Here the electric machines, used as engine actuators during the transient, add or extract torque from the engine shafts to maintain the speed-flow characteristics of steady-state design operation. This greatly reduces the need to maintain transient stall margin stack in the compressors, among other potential benefits. This paper demonstrates the feasibility of the concept in dynamic simulation using a Numerical Propulsion System Simulation (NPSS) engine model of a NASA hybrid electric propulsion concept known as the Parallel Hybrid Electric Turbofan (hFan).

Culley, Dennis E.↗
NASA NTRS1985

R and D Productivity: New Challenges for the US Space Program

Various topics related to research and development activities applicable to their U.S. space program are discussed. Project management, automatic control technology, human resources, management information systems, computer aided design, systems engineering, and personnel management were among the topics covered.

Otis W Baskin↗
NASA NTRS1988

STS-26 Preflight Press Briefing: Shuttle Systems Changes (2)

This NASA KSC video release presents part of a press conference held prior to Discovery flight STS-26, the first shuttle mission flown following the 51-L Challenger accident. The video includes presentations by Gerald Smith (Solid Rocket Booster (SRB) Project Manager) and Joe Lombardo (Space Shuttle Main Engine (SSME) Project Manager) discussing the major changes that were made to the SRB and SSME between 51-L and STS-26. Mr. Smith's talk centered on the changes and redesigns made to the solid rocket motor field joint, the case to nozzle joint, the SRB aft skirt, and the ET aft attach ring. Mr. Lombardo discusses test data evaluation, SSME inspections and the SSME heat exchanger in particular.

Source record↗
NASA NTRS2013

Exploring Mission Concepts with the JPL Innovation Foundry A-Team

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts called the A-Team. The A-Team combines innovative collaborative methods with subject matter expertise and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an A-Team study. Methods are grouped by Concept Maturity Level (CML), from 1 through 3, including idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for each CML are presented, and the key team roles are described from two points of view: innovative methods and technical expertise. A-Team roles for providing innovative methods include the facilitator, study lead, and assistant study lead. A-Team roles for providing technical expertise include the architect, lead systems engineer, and integration engineer. In addition to these key roles, each A-Team study is uniquely staffed to match the study topic and scope including subject matter experts, scientists, technologists, flight and instrument systems engineers, and program managers as needed. Advanced analysis and collaborative engineering tools (e.g. cost, science traceability, mission design, knowledge capture, study and analysis support infrastructure) are also under development for use in A-Team studies and will be discussed briefly. The A-Team facilities provide a constructive environment for innovative ideas from all aspects of mission formulation to eliminate isolated studies and come together early in the development cycle when they can provide the biggest impact. This paper provides an overview of the A-Team, its study processes, roles, methods, tools and facilities.

Team Eureka↗
NASA NTRS2004

Advanced Health Management System for the Space Shuttle Main Engine

Boeing-Canoga Park (BCP) and NASA-Marshall Space Flight Center (NASA-MSFC) are developing an Advanced Health Management System (AHMS) for use on the Space Shuttle Main Engine (SSME) that will improve Shuttle safety by reducing the probability of catastrophic engine failures during the powered ascent phase of a Shuttle mission. This is a phased approach that consists of an upgrade to the current Space Shuttle Main Engine Controller (SSMEC) to add turbomachinery synchronous vibration protection and addition of a separate Health Management Computer (HMC) that will utilize advanced algorithms to detect and mitigate predefined engine anomalies. The purpose of the Shuttle AHMS is twofold; one is to increase the probability of successfully placing the Orbiter into the intended orbit, and the other is to increase the probability of being able to safely execute an abort of a Space Transportation System (STS) launch. Both objectives are achieved by increasing the useful work envelope of a Space Shuttle Main Engine after it has developed anomalous performance during launch and the ascent phase of the mission. This increase in work envelope will be the result of two new anomaly mitigation options, in addition to existing engine shutdown, that were previously unavailable. The added anomaly mitigation options include engine throttle-down and performance correction (adjustment of engine oxidizer to fuel ratio), as well as enhanced sensor disqualification capability. The HMC is intended to provide the computing power necessary to diagnose selected anomalous engine behaviors and for making recommendations to the engine controller for anomaly mitigation. Independent auditors have assessed the reduction in Shuttle ascent risk to be on the order of 40% with the combined system and a three times improvement in mission success.

Davidson, Matt↗
NASA NTRS2012

Architecting the Human Space Flight Program with Systems Modeling Language (SysML)

The next generation of missions in NASA's Human Space Flight program focuses on the development and deployment of highly complex systems (e.g., Orion Multi-Purpose Crew Vehicle, Space Launch System, 21st Century Ground System) that will enable astronauts to venture beyond low Earth orbit and explore the moon, near-Earth asteroids, and beyond. Architecting these highly complex system-of-systems requires formal systems engineering techniques for managing the evolution of the technical features in the information exchange domain (e.g., data exchanges, communication networks, ground software) and also, formal correlation of the technical architecture to stakeholders' programmatic concerns (e.g., budget, schedule, risk) and design development (e.g., assumptions, constraints, trades, tracking of unknowns). This paper will describe how the authors have applied System Modeling Language (SysML) to implement model-based systems engineering for managing the description of the End-to-End Information System (EEIS) architecture and associated development activities and ultimately enables stakeholders to understand, reason, and answer questions about the EEIS under design for proposed lunar Exploration Missions 1 and 2 (EM-1 and EM-2).

scheduling↗
NASA NTRS2024

NASA Engineering and Safety Center Lunar Rover Design Concepts Assessments

Mass is a significant risk to programs and projects as they transition from formulation to implementation, especially in larger human space systems where delivery mass or volume can be a constrained commodity. • Concepts developed without an adequate systems-engineering basis, including design and operations experience, may miss significant functionality and subsequent mass required for integration or operations. • Further uncertainty can be associated with not fully understanding design best practices and standards that drive mass, such as design for minimum risk or fault tolerance.1 • Finally, the appropriate systems engineering mass properties management rigor and technical discipline insight are required to set the mass baseline, including appropriate mass growth allowance (MGA) to ensure program success. Mass is a key quantity that should be constantly monitored by the systems engineer and the program/project management stakeholder to ensure mission compatibility throughout the project life cycle. In addition, mass is a key programmatic performance metric monitored by the NASA Chief Financial Officer for current and future program cost estimating. NASA Exploration Systems sought an assessment of reasonableness with respect to different potential rover concepts that balances mass needs and human-class cargo lander capabilities. Appropriate systems engineering mass properties management rigor and technical discipline insight were used, and are required to set the mass baseline, including appropriate MGA to ensure program success. Two independent Lunar rover concepts were evaluated, with a goal to understand concept credibility and the Lunar rover designs potential extensibility for Mars surface operations. A notional generic rover concept is shown in Figure 1.

Systems Engineering↗
NASA NTRS1995

NASA Systems Engineering Handbook

This handbook brings the fundamental concepts and techniques of systems engineering to NASA personnel in a way that recognizes the nature of NASA systems and environment. It is intended to accompany formal NASA training courses on systems engineering and project management when appropriate, and is designed to be a top-level overview. The concepts were drawn from NASA field center handbooks, NMI's/NHB's, the work of the NASA-wide Systems Engineering Working Group and the Systems Engineering Process Improvement Task team, several non-NASA textbooks and guides, and material from independent systems engineering courses taught to NASA personnel. Five core chapters cover systems engineering fundamentals, the NASA Project Cycle, management issues in systems engineering, systems analysis and modeling, and specialty engineering integration. It is not intended as a directive. Superseded by: NASA/SP-2007-6105 Rev 1 (20080008301).

Shishko, Robert↗
NASA NTRS1992

Health management and controls for earth to orbit propulsion systems

Fault detection and isolation for advanced rocket engine controllers are discussed focusing on advanced sensing systems and software which significantly improve component failure detection for engine safety and health management. Aerojet's Space Transportation Main Engine controller for the National Launch System is the state of the art in fault tolerant engine avionics. Health management systems provide high levels of automated fault coverage and significantly improve vehicle delivered reliability and lower preflight operations costs. Key technologies, including the sensor data validation algorithms and flight capable spectrometers, have been demonstrated in ground applications and are found to be suitable for bridging programs into flight applications.

Bickford, R. L.↗
NASA NTRSDate not supplied

Open-Source Data Engineering at NASA: CCMC's Approach to Managing Petabyte-Scale Heliophysics Data

The Community Coordinated Modeling Center (CCMC) at NASA Goddard Space Flight Center (GSFC) leads heliophysics research by providing open access to numerous models and their outputs. Our resources are available on-demand and continuously updated with real-time data, covering sun-earth interactions across multiple domains. These domains include coronal, heliosphere, inner and global magnetosphere, ionosphere, thermosphere, and lower atmosphere interactions. Operating in a hybrid environment, CCMC utilizes both self-owned hardware and Amazon Web Services (AWS) cloud infrastructure. Managing petabytes of data across multiple locations necessitates robust data engineering solutions. To address this challenge, CCMC has adopted industry-standard and open-source tools. We use Apache Airflow as our primary data engineering platform, Python for scripting and data processing, and GitLab for version control and CI/CD. Additionally, we employ Kubernetes for containerized services, Grafana and Prometheus for metrics and monitoring, and Terraform and Puppet for reproducible infrastructure as code. This presentation will discuss lessons learned from our data engineering experiences, platforms evaluated but found unsuitable for our scientific data requirements, and specific techniques developed to enhance data transfer speed and reliability. By using these technologies effectively, CCMC continues to advance heliophysics research through efficient data management and open-access modeling.

space weather↗
NASA NTRS2006

Observations, Ideas, and Opinions: Systems Engineering and Integration for Return to Flight

This presentation addresses project management and systems engineering and integration challenges for return to flight, focusing on the Thermal Protection System Tile Repair Project (TRP). The program documentation philosophy, communication with program requirements flow and philosophy and planned deliverables and documentation are outlined. The development of TRP 'use-as-is' analytical tools is also highlighted and emphasis is placed on the use flight history to assess pre-flight and real-time risk. Additionally, an overview is provided of the repair procedure, including an outline of the logistics deployment chart.

Gafka, George K.↗
NASA NTRS2010

NASA's Evolutionary Xenon Thruster (NEXT) Prototype Model 1R (PM1R) Ion Thruster and Propellant Management System Wear Test Results

The results of the NEXT wear test are presented. This test was conducted with a 36-cm ion engine (designated PM1R) and an engineering model propellant management system. The thruster operated with beam extraction for a total of 1680 hr and processed 30.5 kg of xenon during the wear test, which included performance testing and some operation with an engineering model power processing unit. A total of 1312 hr was accumulated at full power, 277 hr at low power, and the remainder was at intermediate throttle levels. Overall ion engine performance, which includes thrust, thruster input power, specific impulse, and thrust efficiency, was steady with no indications of performance degradation. The propellant management system performed without incident during the wear test. The ion engine and propellant management system were also inspected following the test with no indication of anomalous hardware degradation from operation.

VanNoord, Jonathan L.↗
NASA NTRS1985

Improving engineering effectiveness

Methodologies to improve engineering productivity were investigated. The rocky road to improving engineering effectiveness is reviewed utilizing a specific semiconductor engineering organization as a case study. The organization had a performance problem regarding new product introductions. With the help of this consultant as a change agent the engineering team used a systems approach to through variables that were effecting their output significantly. Critical factors for improving this engineering organization's effectiveness and the roles/responsibilities of management, the individual engineers and the internal consultant are discussed.

Fiero, J. D.↗