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 541 records · Page 30

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

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↗

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

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

MIKA: Manager for Intelligent Knowledge Access Toolkit for Engineering Knowledge Discovery and Information Retrieval

Repositories of safety reports are often underutilized and only analyzed manually by trained experts, despite safety management systems requiring reports. These collections of documents contain a wealth of information from past projects and operations that could improve system safety and design. Advances in natural language processing techniques have improved information extraction and retrieval in consumer technology, biomedicine, and finance, for instance, but have not been applied to engineering documents on the same scale. To this end, the Manager for Intelligent Knowledge Access (MIKA) open-source toolkit has been developed for rapid knowledge discovery and information retrieval in safety engineering applications. The MIKA toolkit uses state-of-the-art natural language processing algorithms and allows a user to apply these methods to their own dataset. This paper describes the MIKA toolkit and its two primary capabilities, knowledge discovery and information retrieval, and demonstrates the toolkit via a case study on National Transportation Safety Board (NTSB) reports.

Machine Learning↗

MIKA: Manager for Intelligent Knowledge Access Toolkit for Engineering Knowledge Discovery and Information Retrieval

Repositories of safety reports are often underutilized and only analyzed manually by trained experts, despite safety management systems requiring reports. These collections of documents contain a wealth of information from past projects and operations that could improve system safety and design. Advances in natural language processing techniques have improved information extraction and retrieval in consumer technology, biomedicine, and finance, for instance, but have not been applied to engineering documents on the same scale. To this end, the Manager for Intelligent Knowledge Access (MIKA) open-source toolkit has been developed for rapid knowledge discovery and information retrieval in safety engineering applications. The MIKA toolkit uses state-of-the-art natural language processing algorithms and allows a user to apply these methods to their own dataset. This paper describes the MIKA toolkit and its two primary capabilities, knowledge discovery and information retrieval, and demonstrates the toolkit via a case study on National Transportation Safety Board (NTSB) reports.

Systems Engineering↗

Advanced Health Management System for the Space Shuttle Main Engine

Pratt & Whitney Rocketdyne, Inc., in cooperation with NASA-Marshall Space Flight Center (MSFC), has developed a new Advanced Health Management System (AHMS) controller for the Space Shuttle Main Engine (SSME) that will increase the probability of successfully placing the shuttle into the intended orbit and increase the safety of the Space Transportation System (STS) launches. The AHMS is an upgrade o the current Block II engine controller whose primary component is an improved vibration monitoring system called the Real-Time Vibration Monitoring System (RTVMS) that can effectively and reliably monitor the state of the high pressure turbomachinery and provide engine protection through a new synchronous vibration redline which enables engine shutdown if the vibration exceeds predetermined thresholds. The introduction of this system required improvements and modification to the Block II controller such as redesigning the Digital Computer Unit (DCU) memory and the Flight Accelerometer Safety Cut-Off System (FASCOS) circuitry, eliminating the existing memory retention batteries, installation of the Digital Signal Processor (DSP) technology, and installation of a High Speed Serial Interface (HSSI) with accompanying outside world connectors. Test stand hot-fire testing along with lab testing have verified successful implementation and is expected to reduce the probability of catastrophic engine failures during the shuttle ascent phase and improve safely by about 23% according to the Quantitative Risk Assessment System (QRAS), leading to a safer and more reliable SSME.

Davidson, Matt↗

Ames Engineering Directorate

The Ames Engineering Directorate is the principal engineering organization supporting aerospace systems and spaceflight projects at NASA's Ames Research Center in California's Silicon Valley. The Directorate supports all phases of engineering and project management for flight and mission projects-from R&D to Close-out-by leveraging the capabilities of multiple divisions and facilities.The Mission Design Center (MDC) has full end-to-end mission design capability with sophisticated analysis and simulation tools in a collaborative concurrent design environment. Services include concept maturity level (CML) maturation, spacecraft design and trades, scientific instruments selection, feasibility assessments, and proposal support and partnerships. The Engineering Systems Division provides robust project management support as well as systems engineering, mechanical and electrical analysis and design, technical authority and project integration support to a variety of programs and projects across NASA centers. The Applied Manufacturing Division turns abstract ideas into tangible hardware for aeronautics, spaceflight and science applications, specializing in fabrication methods and management of complex fabrication projects. The Engineering Evaluation Lab (EEL) provides full satellite or payload environmental testing services including vibration, temperature, humidity, immersion, pressure/altitude, vacuum, high G centrifuge, shock impact testing and the Flight Processing Center (FPC), which includes cleanrooms, bonded stores and flight preparation resources. The Multi-Mission Operations Center (MMOC) is composed of the facilities, networks, IT equipment, software and support services needed by flight projects to effectively and efficiently perform all mission functions, including planning, scheduling, command, telemetry processing and science analysis.

Small Satellites↗

NEXT Single String Integration Test Results

As a critical part of NASA's Evolutionary Xenon Thruster (NEXT) test validation process, a single string integration test was performed on the NEXT ion propulsion system. The objectives of this test were to verify that an integrated system of major NEXT ion propulsion system elements meets project requirements, to demonstrate that the integrated system is functional across the entire power processor and xenon propellant management system input ranges, and to demonstrate to potential users that the NEXT propulsion system is ready for transition to flight. Propulsion system elements included in this system integration test were an engineering model ion thruster, an engineering model propellant management system, an engineering model power processor unit, and a digital control interface unit simulator that acted as a test console. Project requirements that were verified during this system integration test included individual element requirements ; integrated system requirements, and fault handling. This paper will present the results of these tests, which include: integrated ion propulsion system demonstrations of performance, functionality and fault handling; a thruster re-performance acceptance test to establish baseline performance: a risk-reduction PMS-thruster integration test: and propellant management system calibration checks.

Soulas, George C.↗

An Historical Perspective of the NERVA Nuclear Rocket Engine Technology Program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗

An historical perspective of the NERVA nuclear rocket engine technology program

Nuclear rocket research and development was initiated in the United States in 1955 and is still being pursued to a limited extent. The major technology emphasis occurred in the decade of the 1960s and was primarily associated with the Rover/NERVA Program where the technology for a nuclear rocket engine system for space application was developed and demonstrated. The NERVA (Nuclear Engine for Rocket Vehicle Application) technology developed twenty years ago provides a comprehensive and viable propulsion technology base that can be applied and will prove to be valuable for application to the NASA Space Exploration Initiative (SEI). This paper, which is historical in scope, provides an overview of the conduct of the NERVA Engine Program, its organization and management, development philosophy, the engine configuration, and significant accomplishments.

Robbins, W. H.↗

Space vehicle design and operation for efficient use of Nuclear Thermal Propulsion

Nuclear Thermal Propulsion (NTP) is a high-leverage, and possibly enabling, propulsion choice for sending humans to Mars. Important performance gains are expected for NTP Mars transfer vehicle over their counterparts, the conventional chemical systems. These gains come in spite of vehicle unique requirements for NTP engine development and operations: expected higher development costs, prelaunch and in-space handing safeguards, extra propellant for reactor cool-down after engine burns, and safe, managed disposal of spent NTP engines. Prior studies have also shown that these NTP engines and stages, sized for Mars missions, could increase delivered payloads for some piloted lunar mission as well.

Stancati, Mike L.↗

Medical surveillance and biological monitoring of lead exposed employees

Employee health protection is an employer responsibility. The multi-faceted aspects of employee protection from the potentially harmful effects of inorganic lead sometimes stress the relationships of several employer units. These include supervision and management, safety, operations and maintenance, engineering, environmental health, environmental management, and occupational medicine. The administrative aspects of program development are discussed. The purpose is to emphasize the opportunity for cooperation by all of the employee health components in developing an optimum surveillance and protection program.

Ferguson, E. B.↗

A PPE Use Case on Configuration Management Approach for MBSE

Systems engineers worldwide have been working to implement Model-based Systems Engineering (MBSE) environments, tools, and methodologies. MBSE is a formalized application of modeling to support systems engineering, including requirements, design, analysis, verification, and validation activities over the project’s lifecycle[1]; MBSE captures the system data into a digital environment. Significant benefits of MBSE includes a reduction in the time in performing systems engineering activities and an improvement higher fidelity data production. As more Systems Engineers are using MBSE, the models it produces are becoming the source of truth for Systems Engineering artifacts. As we move towards using these models as the source of truth, a more rigorous Configuration Management (CM) infrastructure is needed. Many of the MBSE tools provide CM options but utilizing them efficiently and effectively can be challenging. More rigorous methods and tools are needed to assist with keeping track of changes in the model, making sure inadvertent changes to baseline data did not occur, visibility of changes in the different model versions, and the impacts of changes to the models. System engineers and configuration management personnel from the Power and Propulsion Element (PPE) project at NASA Glenn Research Center have been working to develop a modeling construct that allows models to be the source of truth and maintain a configuration managed baseline. This paper presents a process that leverages the existing CM tools and describes how PPE used this process to manage changes more rigorously. It will describe the process behind building the model architecture that utilizes the MBSE tool capabilities and the configuration management process. It will contain some of the advantages and disadvantages of the architecture that the PPE project had settled upon utilizing, as well as some enhanced capabilities that the PPE MBSE team has developed.

MBSE↗

NASA Systems Engineering Handbook

The update of this handbook continues the methodology of the previous revision: a top-down compatibility with higher level Agency policy and a bottom-up infusion of guidance from the NASA practitioners in the field. This approach provides the opportunity to obtain best practices from across NASA and bridge the information to the established NASA systems engineering processes and to communicate principles of good practice as well as alternative approaches rather than specify a particular way to accomplish a task. The result embodied in this handbook is a top-level implementation approach on the practice of systems engineering unique to NASA. Material used for updating this handbook has been drawn from many sources, including NPRs, Center systems engineering handbooks and processes, other Agency best practices, and external systems engineering textbooks and guides. This handbook consists of six chapters: (1) an introduction, (2) a systems engineering fundamentals discussion, (3) the NASA program project life cycles, (4) systems engineering processes to get from a concept to a design, (5) systems engineering processes to get from a design to a final product, and (6) crosscutting management processes in systems engineering. The chapters are supplemented by appendices that provide outlines, examples, and further information to illustrate topics in the chapters. The handbook makes extensive use of boxes and figures to define, refine, illustrate, and extend concepts in the chapters.

ENGINEERING MANAGEMENT; HANDBOOKS; MANAGEMENT METH↗

Identity Federation and Its Importance for NASA's Future: The SharePoint Extranet Pilot

My project at Kennedy Space Center (KSC) during the spring 2013 Project Management and Systems Engineering Internship was to functionalJy test and deploy the SharePoint Extranet system and ensure successful completion of the project's various lifecycle milestones as described by NASA Procedural Requirement (NPR) 7 120.7. I worked alongside NASA Project Managers, Systems Integration Engineers, and Information Technology (IT) Professionals to pilot this collaboration capability between NASA and its External Partners. The use of identity federation allows NASA to leverage externally-issued credentials of other federal agencies and private aerospace and defense companies, versus the traditional process of granting and maintaining full NASA identities for these individuals. This is the first system of its kind at NASA and it will serve as a pilot for the Federal Government. Recognizing the novelty of this service, NASA's initial approach for deployment included a pilot period where nearby employees of Patrick Air Force Base would assist in testing and deployment. By utilizing a credential registration process, Air Force users mapped their Air Force-issued Common Access Cards (CAC) to a NASA identity for access to the External SharePoint. Once the Air Force stands up an Active Directory Federation Services (ADFS) instance within their Data Center and establishes a direct trust with NASA, true identity federation can be established. The next partner NASA is targeting for collaboration is Lockheed Martin (LMCO), since they collaborate frequently for the ORION Program. Through the use of Exostar as an identity hub, LMCO employees will be able to access NASA data on a need to know basis, with NASA ultimately managing access. In a time when every dollar and resource is being scrutinized, this capability is an exciting new way for NASA to continue its collaboration efforts in a cost and resource effective manner.

Baturin, Rebecca R.↗

Assessment of the Orion-SLS Interface Management Process in Achieving the EIA 731.1 Systems Engineering Capability Model Generic Practices Level 3 Criteria

NASA is currently developing the next generation crewed spacecraft and launch vehicle for exploration beyond earth orbit including returning to the Moon and making the transit to Mars. Managing the design integration of major hardware elements of a space transportation system is critical for overcoming both the technical and programmatic challenges in taking a complex system from concept to space operations. An established method of accomplishing this is formal interface management. In this paper we set forth an argument that the interface management process implemented by NASA between the Orion Multi-Purpose Crew Vehicle (MPCV) and the Space Launch System (SLS) achieves the Level 3 tier of the EIA 731.1 System Engineering Capability Model (SECM) for Generic Practices. We describe the relevant NASA systems and associated organizations, and define the EIA SECM Level 3 Generic Practices. We then provide evidence for our compliance with those practices. This evidence includes discussions of: NASA Systems Engineering Interface (SE) Management standard process and best practices; the tailoring of that process for implementation on the Orion to SLS interface; changes made over time to improve the tailored process, and; the opportunities to take the resulting lessons learned and propose improvements to our institutional processes and best practices. We compare this evidence against the practices to form the rationale for the declared SECM maturity level.

Jellicorse, John J.↗