Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “program managers”

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 1,549 records · Page 86

Navigation and Guidance for the Mars Surveyor 1998 Mission

In December, 1998 and January 1999 NASA will launch two spacecraft to Mars as part of the overall Mars Exploration Program managed at JPL. One is an orbiter that will arrive at Mars in October of 1999 carrying a science payload for remote sensing.

navigation↗

Development and Testing of Pulse Guns for Combustion Instability Testing

To test liquid rocket engines (LREs) for combustion instabilities, devices such as bombs are often used to create pressure wave disturbances. Bombs, while effective, are inherently dangerous, expensive, and difficult to procure. Over the years, pulse guns have been used as a safer and more cost-effective way to generate controlled pressure disturbances in engine chambers. In anticipation of the need for stability testing of prototype LREs at NASA Marshall Space Flight Center (MSFC), a set of pulse guns have been designed, fabricated, tested, and characterized. The pulse gun program is funded by the RS-25 Engine Program managed out of MSFC and funded by NASA’s Space Launch System (SLS) through the MSFC Liquid Engines Office (LEO). A pulse gun is a simple device – like a traditional gun, it has a breech and barrel section. However, unlike a traditional gun, there is no bullet, as the purpose of the pulse gun is strictly to fire a high pressure pulse. Instead of a firing pin and primer that would normally be used in a traditional gun, an initiator is used to activate the gun powder. The initiator is a highly reliable pyrotechnic initiator. For this study, clone versions of the NASA Standard Initiator (NSI) were used. The initiator is used to ignite a pre-measured amount of gun powder loaded into the breech. When the pressure of the burnt gun powder exceeds the set point of a downstream burst disk, the disk ruptures, allowing the high pressure pulse to travel downstream through the barrel section. A ballistic pressure transducer located in the breech section is used to measure the short duration, high pressure pulse. Some configurations of the pulse gun have barrel sections that include one or more additional ballistic pressure transducers. These additional pressure measurements help track the degradation and damping of the pulse as it travels out of the barrel section. The measurements may also be used to determine the velocity of pulse. The objective of this paper is to present the different variants of this newly-developed pulse gun and characterize performance over a range of parameters. The parameters include breech diameter, barrel length, amount of gun powder used, the way the gun powder is packed, and the pressure setting of the burst disk. There are a total of six pulse guns: three with the 0.25 inch breech and three different length barrels, and three with the 0.40 inch breech and three different length barrels. For both breech sizes, the associated barrels are referred to as standard, one-port, and two-port barrels. The standard barrel has no instrumentation and is likely the barrel that will be used for engine stability testing. The one- and two-port barrels were designed specifically for pulse gun component testing to allow measurements of the magnitude and timing of the high pressure pulse as it makes its way through the pulse gun. The burst disks tested were commercially-available burst disks designed to rupture at 8,000, 16,000, and 24,000 psid. Testing was accomplished by firing the pulse gun into a test chamber pressurized with nitrogen at about 2300 psig. A total of four Model 113B23 High frequency ICP® pressure sensors (10k psi) were mounted in the test chamber, in the same plane as the pulse gun. Two of the sensors had “trimmed” adapters, and two did not. Given the symmetrical configuration of the sensors within the test chamber, different amplitudes of pressure measurements are attributed to the use of trimmed versus untrimmed adapters. The untrimmed adapters, with their narrower passages, tended to amplify the pressure amplitudes by as much as 50%. In total, 41 pulse gun tests have been conducted.Data are still being analyzed, but some trends are apparent. For example, measurements taken within the pulse gun are shown in Figures 3 and 4 for Hot-fires (HFs) # 11 and 39, respectively. Both tests were identical in that the 0.40 inch ID breech, two-port barrel, 8,000 psid burst disk, and same amount of gunpowder (6.639 grains for HF# 11, and 6.576 grains for HF# 39) were used, and the back pressure in the nitrogen test chamber was ~2300 psig. Despite keeping all these variables constant, the results from these two tests look quite different. For both tests, the first pressure peak shown in the P2111 trace within the breech is the firing of the initiator. The second peak and any subsequent peaks are from the combustion of the gunpowder. It should be noted that because the sensors are dynamic, the ~2300 psig baseline static pressure is not shown in the figures. For HF# 11, the burst disk clearly ruptured in a little over 0.1 ms from the time the initiator was fired. This is evident from the abrupt rise in pressure for P2112 followed by another abrupt rise in pressure for P2113. The sensors track the movement of the high pressure pulse through the pulse gun. For HF# 39, however, there was nearly 1 ms delay between the initiator firing and the burst disk rupturing. The only difference between these two tests was the way in which the gunpowder was packed within the breech. For HF# 11, the gunpowder was poured directly into the breech, atop the initiator, and held in place with a vegetable fiber wad appropriately sized for the barrel diameter. Once in place, the wad firmly held the gunpowder in place. For HF# 39, the gunpowder was rolled within cigarette paper with the ends of the paper twisted. The rolled gunpowder was gently pushed down into the breech, toward the initiator, and no wad was used. This method of loading the gunpowder consistently produced longer delays in the rupture of the burst disk, presumably because there was a steady, fuller burning of the gunpowder. The burst disk was rated for 8,000 psid, which means that the burst disk should not have opened until the pressure in the breech reached ~10,300 since there was ~2300 psig back pressure in the test chamber. In the case of HF# 11, the breech pressure only reached roughly 4200 psi before there was leakage either through or past the burst disk, but for HF#39, the breech pressure reached 10,600 psi prior to the burst disk opening. The temperature of the burst disk is certainly a factor in determining when the burst disk will rupture. A sharp rise in the burst disk temperature could weaken it and cause it to stray from the designed set point burst pressure. The burst disks are manufactured of Inconel to try to reduce their sensitivity to temperature, but how the burst disks perform above 900°F is not documented. All burst disks were engineered and tested by the manufacturer for ambient temperature conditions. One theory for why rolling the gunpowder in cigarette paper may produce better results is related to a more controlled temperature environment. The cigarette paper may act as a sheath that protects the burst disk from excessive temperatures during the rapid buildup of pressure in the breech. The ultimate benefit of not breeching the burst disk prematurely is shown in Figures 5 and 6, which graphs the resultant pressure pulse produced in the test chamber. For HF #11, the peak pressure on the P2123 trimmed adapter is about 270 psi, while for HF# 39 it is 343 psi, which is about 1.27 times greater in magnitude. In either case, the pressure pulse is ~20 μs in width once it reaches the test chamber. Another pressure rise about 100 μs later can be seen on the sensors located across from the pulse gun port, P2124 and P2121. These pressures are lower due to attenuation of the pressure wave as it moves across the test chamber. After the wave encounters the wall, it reflects back and forth within the chamber until it completely dissipates.

Pulse Gun↗

GA-ASI Final Report and Program Wrap-up for NASA System Integration and Operationalization (SIO)

The NASA SIO demonstration flight of April 3, 2020 represents a successful culmination of 18 months of coordinated effort between GA-ASI, NASA, the FAA, Collins Aerospace, and Honeywell Aerospace to operate a Medium Altitude, Long Endurance (MALE) Unmanned Aircraft System (UAS) safely in the National Airspace System (NAS) using industry leading prototype technologies. The GA-ASI team consisted of technical experts, program managers, engineers, mechanics, flight technicians, flight crews, and numerous other subject matter experts. This final report describes the most significant and potentially impactful aspects of the planning, integration, test, and flight aspects of this effort. GA-ASI successfully integrated the key technologies needed for UAS to fly in the NAS onto our prototype SkyGuardian UAS, which was designed to meet the most stringent airworthiness standards applicable to an aircraft of its size category. A proven Detect and Avoid (DAA) system, developed by GA-ASI and utilizing Honeywell Aerospace technology was integrated onto SkyGuardian for the first time, along with datalink radios from Collins Aerospace that meet the new civil standard for Control and Non-Payload Communication (CNPC) links. GA-ASI also obtained approvals from the FAA and FCC to operate the reconfigured UAS. The SIO demonstration flight represented a commercial aerial surveying operation conducted at medium altitude (>10,000ft above mean sea level). The aircraft’s onboard sensors were used to capture photographic, infrared and radar imagery of public and commercial infrastructure and land, and to subsequently produce the types of data products that would provide business value to potential customers. These survey services would supplement or replace services currently provided by manned airplanes and helicopters, small drones or satellites. A “virtual” mission was also planned, to show what additional survey data could have been captured during the flight if additional sensors had been installed on the aircraft’s external hardpoints. This revision of the final report focuses on information of value to the wider UAS community, and avoids propriety data to facilitate broad dissemination. It also includes a description of GA-ASI’s engagement with the FAA following the SIO flight, which led to the award of an updated Special Airworthiness Certificate in the Experimental Category (SAC-EC) and a Certificate of Waiver or Authorization (COA) allowing operation of the SkyGuardian UAS using its DAA system to satisfy right-of-way rules, instead of a chase plane. The associated operational limitations are described to illustrate the further steps that would be needed to remove those limitations for unhindered commercial operations.

Flight demonstration↗

NASA’s Revised Planetary Protection Policy and Implementation

NASA has updated its planetary protection policy and implementation approach in response to advances in scientific understanding of solar system targets, upcoming mission opportuni-ties for exploration and sample return, and the private sector’s emerging capability to plan missions to Earth’s Moon and Mars. In September 2021, the NASA Procedural Requirements NPR 8715.24, entitled “Planetary Protection Provisions for Robotic Extraterrestrial Missions” was released which repositions planetary protection in existing NASA mission and program management structures, introduces risk-informed decision making, expands on key roles and responsibilities for both programmatic and the Oÿce of Safety and Mission Assurance, updates the categorization process and streamlines the planetary protection documentation approval and schedule. NASA is working on a more detailed technical standard to accompany NPR 8715.24 which will include the detailed technical requirements to address organic contamina-tion, inadvertent impact avoidance, biological control and management, end of mission disposal and restricted Earth-Return sample safety and assurance. This report to the COSPAR com-munity will describe the current NASA planetary protection policy and its alignment with the revised COSPAR planetary protection policy. NASA’s plans for updating the supporting “Handbook for Implementing Planetary Protection Technical Requirements” and future policies for addressing planetary protection of crewed missions will also be presented.

Elaine Seasly↗

NASA’s Revised Planetary Protection Policy and Implementation

NASA has updated its planetary protection policy and implementation approach in response to advances in scientific understanding of solar system targets, upcoming mission opportunities for exploration and sample return, and the private sector’s emerging capability to plan missions to Earth’s Moon and Mars. In September 2021, the NASA Procedural Requirements NPR 8715.24, entitled “Planetary Protection Provisions for Robotic Extraterrestrial Missions” was released which repositions planetary protection in existing NASA mission and program management structures, introduces risk-informed decision making, expands on key roles and responsibilities for both programmatic and the Office of Safety and Mission Assurance, updates the categorization process and streamlines the planetary protection documentation approval and schedule. NASA is working on a more detailed technical standard to accompany NPR 8715.24 which will include the detailed technical requirements to address organic contamination, inadvertent impact avoidance, biological control and management, end of mission disposal and restricted Earth-Return sample safety and assurance. This report to the COSPAR community will describe the current NASA planetary protection policy and its alignment with the revised COSPAR planetary protection policy. NASA’s plans for updating the supporting “Handbook for Implementing Planetary Protection Technical Requirements” and future policies for addressing planetary protection of crewed missions will also be presented.

Planetary Protection↗

NASA’s Revised Planetary Protection Policy and Implementation

NASA has updated its planetary protection policy and implementation approach in response to advances in scientific understanding of solar system targets, upcoming mission opportunities for exploration and sample return, and the private sector’s emerging capability to plan missions to Earth’s Moon and Mars. In September 2021, the NASA Procedural Requirements NPR 8715.24, entitled “Planetary Protection Provisions for Robotic Extraterrestrial Missions” was released which repositions planetary protection in existing NASA mission and program management structures, introduces risk-informed decision making, expands on key roles and responsibilities for both programmatic and the Office of Safety and Mission Assurance, updates the categorization process and streamlines the planetary protection documentation approval and schedule. NASA is working on a more detailed technical standard to accompany NPR 8715.24 which will include the detailed technical requirements to address organic contamination, inadvertent impact avoidance, biological control and management, end of mission disposal and restricted Earth-Return sample safety and assurance. This report to the COSPAR community will describe the current NASA planetary protection policy and its alignment with the revised COSPAR planetary protection policy. NASA’s plans for updating the supporting “Handbook for Implementing Planetary Protection Technical Requirements” and future policies for addressing planetary protection of crewed missions will also be presented.

Elaine Seasly↗

Nasa Pilot Fatigue Research: Past, Present & Future

Pilot fatigue research at NASA Ames has a long history, initiated by a Congressional request to investigate the magnitude of fatigue, sleep loss and circadian disruption in flight operations, and how these factors impact crew performance. Research has been conducted in a broad range of aviation operations, including short-haul, long-haul, rotorcraft, overnight cargo, corporate/business, and regional airlines. Studies have been conducted in the field during actual flight operations, in simulated settings, focus group meetings, and with surveys. Other investigations have examined mitigation strategies including in-flight rest periods and lighting applications. Other activities have included education and training, publications, accident investigation support and the development of research methods and tools. Future research may include further lighting interventions, controlled rest strategies, use of automation, the effectiveness of modeling tools, and implementation of organizational fatigue management programs.

aviation↗

Orbital Debris Quarterly News, October 2023

In this issue: - ISS Maneuvers to Avoid Potential Collisions Twice in August 2023 - Derelict Cosmos Communications Spacecraft Breaks Up in June 2023 - Gene Stansbery, Former NASA Program Manager for Orbital Debris, Passes - HUSIR Radar Measurements of the Orbital Debris Environment: 2022 - Thirty Years Later: A Look Back at the 1993 JSC Perseid Stormwatch Center - IOC II Commences in December 2023 - NASA ODPO and HVIT Abstract - Conference Report - Orbital Debris Environment Plots - Space Missions and Satellite Box Score

Heather Mae Cowardin↗

A Community for Polar Early Career Researchers Engaging With the Interagency Arctic Research Policy Committee

The Interagency Arctic Research Policy Committee (IARPC) is tasked with implementation of the Arctic Research Plan (ARP) by coordinating representatives from federal and state agencies, academic, industry, and Indigenous partners with interests in Arctic research. IARPC is organized into several collaboration teams and discipline-specific communities of practice that interface on the IARPC Collaborations website. The Early Career Community of Practice (ECCoP) is one such community that was established to promote the research of early career researchers (ECR) and increase ECR engagement with the ARP, program managers, collaboration teams, and communities of practice. The ECCoP has grown to develop regular newsletters promoting recent ECR research publications ad sharing training, job, funding, and collaboration opportunities relevant to community members at all life stages that self-identify as ECRs. Within IARPC, the ECCoP continues to promote ECR participation in monthly community of practice meetings and webinars and to report on ECR efforts that contribute to deliverables of the ARP Biennial Implementation Plan. Recent activity of the ECCoP includes developing an annual survey of the ECR cohort on IARPC to follow change in demographics over time and to identify community needs to improve diversity and inclusion in the polar research space and to address gaps in training needs for ECRs.

Katy Smith↗

Demonstration of Rapid Development Through Containerization: OSE-SAT

Modern advancements in spacecraft technology have enabled engineers to develop radically smaller and lighter spacecraft, which has drastically reduced the cost of putting spacecraft into space. Despite these advancements and the shrinking cost to get spacecraft into space, space exploration is still prohibitively expensive. So much so that many space missions prefer to err on the side of caution than take on additional risk by trying newer, unproven technologies. This risk-averse mission design, while very reasonable from a program management point of view, significantly impacts engineers’ ability to solve newer, more complicated problems and limits scientists’ ability to develop more complex experiments that rely on newer technology. Often these new technologies remain stuck at lower technology readiness levels for many years due to the space community's reluctance to take on the additional risks of proving out unproven technology. The Distributed Spacecraft Autonomy (DSA) team at NASA Ames Research Center is developing a containerized solution to enable the rapid development of newer space technologies and accelerate their adoption into space missions. The Opportunistic Software Experiments for Spacecraft Autonomy Testbeds (OSE-SAT) is an on-orbit test bed that aims to reduce the amount of risk associated with newer, unproven space technologies by containerizing each experiment in its own isolated environment and providing a safe, robust, and controlled interface to access spacecraft host resources that is monitored in real time by thoroughly tested Trusted Container developed by DSA. This paper will describe DSA’s implementation of OSE-SAT and discuss the benefits, as well as challenges, of on-orbit containerization.

Aaron J Woodard↗

Modeling NASA’s Procedural Requirement Processes - Implications for Digital Future

The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions). This paper will summarize the approach, scope, parsing patterns applied, metamodel, and associated workflows for the As-Is modeling. It will also summarize the results and insights gleaned during that phase, including the review process. These insights have informed the analysis and will be discussed. The analysis modeling phase will also be summarized including how the stakeholders were engaged, how the common elements were handled and dispositioned, and will also describe some of the plans for the future of NASA NPDs and NPRs.

Systems Engineering↗

How NASA Accounts for Weather Throughout Artemis Mission

Development and operations of NASA spacecraft and launch vehicles are influenced by the natural environment (i.e. weather) across all applicable mission phases. Defining the natural environments provides engineers the applicable factors, along with exposure ranges, that must be accounted for in the hardware design. Effects from exposure to these environments must be addressed through structural design of the hardware, mitigated through operational controls, or accepted as risk by the governing program. Managing and mitigating these environmental factors was crucial to ensure the safe and successful launch of the Space Launch System (SLS) rocket, the transit of the Multi-Purpose Crew Vehicle (MPCV) around the moon and the recovery of MPCV after landing off the California coast in November 2022. A summary of how the Artemis I mission accounts for both the terrestrial and space environments, as well as the impacts, will be provided.

Ryan K Decker↗

Modeling NASA’s Procedural Requirement Processes – Implications for a Digital Future

The National Aeronautics and Space Administration (NASA) has an ongoing Digital Transformation effort and to leverage and showcase the power of Digital Transformation, an effort is underway to develop an integrated, datacentric, model representing NASA’s key process requirements. The task was divided into three phases: As Is modeling, Analysis, and To Be Planning. As part of this effort, a team has completed the first Phase I of the modeling task and is nearing completion of the second phase. This effort will capture the key elements as requirements, responsibilities, allocations, roles, products, and associated lifecycle elements. The scope of modeling included NASA’s NPR 7120.5 (Project and Program Management), NPR 7123.1 (Systems Engineering) and NPRs 8705.2 (Risk classification for Robotic Missions) and 8705.4 (Human-Rating Requirements for Space Missions).

NPR↗

Failure-Tolerant Avionics for Crewed Space Systems Recommended Best Practices

This paper provides an overview of some of the major steps needed to mature and justify the design of an avionics system for crewed spacecraft. It is organized as a collection of artifacts or pieces of evidence that NASA needs to assess the system at design reviews, including a functional failure modes and effects analysis (FFMEA), fault containment region (FCR) definitions, the failure hypothesis, and reliability analysis. This paper is intended as a reference for designers working on NASA crewed spaceflight projects, reliability engineers responsible for avionics system assessments, and program managers wanting to understand what evidence is required at design reviews to ensure crew safety and mission success.

Avionics↗

Design, implementation and migration of security systems as an extreme project.

Decision Trees, algorithms, software code, risk management, reports, plans, drawings, change control, presentations, and analysis - all useful tools and efforts but time consuming, resource intensive, and potentially costly for projects that have absolute schedule and budget constraints. What are necessary and prudent efforts when a customer calls with a major security problem that needs to be fixed with a proven, off-the-approval-list, multi-layered integrated system with high visibility and limited funding and expires at the end of the Fiscal Year? Whether driven by budget cycles, safety, or by management decree, many such projects begin with generic scopes and funding allocated based on a rapid management 'guestimate.' Then a Project Manager (PM) is assigned a project with a predefined and potentially limited scope, compressed schedule, and potentially insufficient funding. The PM is tasked to rapidly and cost effectively coordinate a requirements-based design, implementation, test, and turnover of a fully operational system to the customer, all while the customer is operating and maintaining an existing security system. Many project management manuals call this an impossible project that should not be attempted. However, security is serious business and the reality is that rapid deployment of proven systems via an 'Extreme Project' is sometimes necessary. Extreme Projects can be wildly successful but require a dedicated team of security professionals lead by an experienced project manager using a highly-tailored and agile project management process with management support at all levels, all combined with significant interface with the customer. This paper does not advocate such projects or condone eliminating the valuable analysis and project management techniques. Indeed, having worked on a well-planned project provides the basis for experienced team members to complete Extreme Projects. This paper does, however, provide insight into what it takes for projects to be successfully implemented and accepted when completed under extreme conditions.

99 GENERAL AND MISCELLANEOUS↗

Design implementation and migration of security systems as an extreme project.

Decision Trees, algorithms, software code, risk management, reports, plans, drawings, change control, presentations, and analysis - all useful tools and efforts but time consuming, resource intensive, and potentially costly for projects that have absolute schedule and budget constraints. What are necessary and prudent efforts when a customer calls with a major security problem that needs to be fixed with a proven, off-the-approval-list, multi-layered integrated system with high visibility and limited funding and expires at the end of the Fiscal Year? Whether driven by budget cycles, safety, or by management decree, many such projects begin with generic scopes and funding allocated based on a rapid management 'guestimate.' Then a Project Manager (PM) is assigned a project with a predefined and potentially limited scope, compressed schedule, and potentially insufficient funding. The PM is tasked to rapidly and cost effectively coordinate a requirements-based design, implementation, test, and turnover of a fully operational system to the customer, all while the customer is operating and maintaining an existing security system. Many project management manuals call this an impossible project that should not be attempted. However, security is serious business and the reality is that rapid deployment of proven systems via an 'Extreme Project' is sometimes necessary. Extreme Projects can be wildly successful but require a dedicated team of security professionals lead by an experienced project manager using a highly-tailored and agile project management process with management support at all levels, all combined with significant interface with the customer. This paper does not advocate such projects or condone eliminating the valuable analysis and project management techniques. Indeed, having worked on a well-planned project provides the basis for experienced team members to complete Extreme Projects. This paper does, however, provide insight into what it takes for projects to be successfully implemented and accepted when completed under extreme conditions.

99 GENERAL AND MISCELLANEOUS↗

Argonne National Laboratory's Recycling Pilot Plant

Argonne has a Recycling Pilot Plant designed to save the non-metal portions of junked cars. Here, program managers demonstrate how plastic shredder residue can be recycled. (Currently these automotive leftovers are sent to landfills. For more information, visit Argonne's Transportation Technology R&D Center Web site at http://www.transportation.anl.gov.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Software Technology Readiness for the Smart Grid

Abstract Budget and schedule overruns in product development due to the use of immature technologies constitute an important matter for program managers. Moreover, unexpected lack of technology maturity is also a problem for buyers. Both sides of the situation would benefit from an unbiased measure of technology maturity. This paper presents the use of a software maturity metric called Technology Readiness Level (TRL), in the milieu of the smart grid. For most of the time they have been in existence, power utilities have been protected monopolies, guaranteed a return on investment on anything they could justify adding to the rate base. Such a situation did not encourage innovation, and instead led to widespread risk-avoidance behavior in many utilities. The situation changed at the end of the last century, with a series of regulatory measures, beginning with the Public Utility Regulatory Policy Act of 1978. However, some bad experiences have actually served to strengthen the resistance to innovation by some utilities. Some aspects of the smart grid, such as the addition of computer-based control to the power system, face an uphill battle. It is our position that the addition of TRLs to the decision-making process for smart grid power-system projects, will lead to an environment of more confident adoption.

technology maturity, software technology readiness↗