Search NASA⌕ Search

SEARCH · Search NASA

Results for “Programmatic safety requirements”

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.

60 records · Page 4

Searching for 'Unknown Unknowns'

The NASA Engineering and Safety Center (NESC) was established to improve safety through engineering excellence within NASA programs and projects. As part of this goal, methods are being investigated to enable the NESC to become proactive in identifying areas that may be precursors to future problems. The goal is to find unknown indicators of future problems, not to duplicate the program-specific trending efforts. The data that is critical for detecting these indicators exist in a plethora of dissimilar non-conformance and other databases (without a common format or taxonomy). In fact, much of the data is unstructured text. However, one common database is not required if the right standards and electronic tools are employed. Electronic data mining is a particularly promising tool for this effort into unsupervised learning of common factors. This work in progress began with a systematic evaluation of available data mining software packages, based on documented decision techniques using weighted criteria. The four packages, which were perceived to have the most promise for NASA applications, are being benchmarked and evaluated by independent contractors. Preliminary recommendations for "best practices" in data mining and trending are provided. Final results and recommendations should be available in the Fall 2005. This critical first step in identifying "unknown unknowns" before they become problems is applicable to any set of engineering or programmatic data.

Parsons, Vickie S.↗

22 N HPGP Thruster Life Testing

In the ever-changing paradigm of efficient and capable spacecraft design, scientific missions continue pushing the envelope enabling spacecraft subsystems to deliver effective solutions to meet challenging new mission/spacecraft needs. From an in-space storable liquid chemical propulsion perspective, monopropellant hydrazine has been, and continues to be, a dependable propellant with considerable flight heritage, a variety of engine thrust classes available from multiple vendors, with repeatable and reliable performance. Additionally, the space propulsion industry has learned to successfully handle hydrazine, its regulations, the safety protocols, the personnel protective equipment, and the unique training standards–all requisite for loading spacecraft propulsion systems with toxic hypergolic hydrazine. The question now arises as to “what is next for in-space chemical propulsion?” Further, with the evolution and concrete advancements in innovative in-space green propellant technologies, capable of providing realizable benefits to scientific missions, concern over the reliability and availability of this higher performing and safer to handle class of propellants is waning. As science missions move forward with the potential flight in fusion of High Performance Green Propulsion (HPGP), NASA and its industry partners are working to address any gaps in system reliability, performance, or unique operational considerations. Propellant technology that offers both higher performance and significant reduction in personnel hazards compared to hydrazine presents an attractive propulsion subsystem design opportunity. Increased propulsion subsystem performance can result in lower spacecraft launch mass, larger scientific payloads, or extended on-orbit lifetimes. Mission trades using green propulsion technologies have been documented on multiple NASA Goddard Space Flight Center (GSFC) mission classes, examining various parameters and requirements to support mission architectures in Low Earth Orbit (LEO), High Earth Orbit (HEO), geostationary, lunar, planetary, and Quasi-halo orbit around Sun-Earth Lagrange point (L2). The results of these trade studies show promising, attainable benefits. The perceived programmatic risk of flying a newer propulsion technology has, unfortunately, not outweighed the benefits to date. To take advantage of the improved performance and mitigate programmatic risk, HPGP engines must demonstrate life testing at higher propellant throughputs than have currently been demonstrated. In an effort to proactively address the challenges with technology infusion into a risk-averse community, NASA and the Swedish National Space Agency (SNSA) outlined a collaborative Implementing Arrangement (IA) for the respective agencies to pursue increased HPGP technology maturation. This initial IA effort began in 2013, fresh off the heels of the successful PRISMA HPGP technology demonstration mission. The IA targeted objective is to reduce risk to potential future HPGP missions and fully characterize the LMP-103S propellant and associated engine performance. Over the past eight years, HPGP has flown in propulsion systems on twenty-five(25) spacecraft from seven(7) different Launch Ranges around the globe and on seven (7) different Launch Vehicles. Six(6) of these launches involved multiple loading operations for multiple spacecraft. For U.S. Range operations, nine (9) HPGP systems have been processed at Vandenberg Space Force Base(VSFB):six(6) in 2017, and three (3) in 2018. Six (6) more have been processed at Cape Canaveral Air Force Station (CCAFS)in May 2020, with three (3) systems launched in June 2020 and the remaining three (3) system were left loaded and ready until their launch in August of 2020. Three (3) more systems have been processed at Wallops Flight Facility(WFF)and launched in June 2021. In addition, these propulsion subsystems employed heritage propulsion subsystem component such as valves, filters, and pressure transducers, and have further demonstrated nominal functionality in both diaphragm and Propellant Management Device (PDM) propellant tanks. Based on these successes, HPGP technology continues to be considered for NASA Science Mission Directorate missions at GSFC. The work presented herein represents many years of development and collaborative efforts to successfully align higher performance, low toxicity hydrazine alternatives into scientific missions. NASA GSFC Propulsion Engineering, in collaboration with Bradford ECAPS, has developed mission specific thruster design and testing requirements to establish GSFC’s desired test conditions and firing sequences.In2017, the first flight-like 22N HPGP thruster Engineering Qualification Model (EQM-1)was designed and built by Bradford ECAPS to prove out the thruster design, materials, build process, and test campaign with respect to NASA GSFC critical component and mission requirements. This test program was developed to comprehensively test the thruster, the technology, and ultimately increase the 22N HPGP Technology Readiness Level(TRL). EQM-1was tested to environmental qualification levels prior to hot fire performance testing to represent the relevant end-to-end environment (launch to on-orbit operation)with required margin. This thruster demonstrated steady-state and pulse mode operational capability with propellant thruster throughput up to~53kg.At this throughput level, the EQM-1 engine began to present off-nominal performance and the test campaign was halted to allow for non-destructive testing and identify the root cause for the an omalous performance. Capitalizing on the successful elements of the EQM-1 campaign, an upgraded 22N HPGP EQM-2 has been manufactured by Bradford ECAPS to meet the complete GSFC requirements. The EQM-2 thruster’s test campaign has further demonstrated the robustness of the HPGP propulsion technology and increased the Technology Readiness Level (TRL) by undergoing a full acceptance test program, then proceeding into qualification, including environmental testing (vibration and shock to qualification levels),as well as hot-fire life testing, operating at steady-state and pulse modes with increased propellant thruster throughput to~150kg. The HPGP thruster performance testing enables effective HPGP thruster readiness evaluation to meet NASA candidate mission requirements in the future.

High↗

Orion Heat Shield Manufacturing Producibility Improvements for the EM-1 Flight Test Program

This paper describes how the Orion program is incorporating improvements in the heat shield design and manufacturing processes reducing programmatic risk and ensuring crew safety in support of NASA’s Exploration Missions. The Orion program successfully completed the EFT-1 flight test in 2014 and is currently developing the EM-1 spacecraft to meet the test objectives of an orbital mission to the moon and return to earth in 2019. Lessons learned from the EFT-1 manufacturing and flight test experience are being incorporated into a wide variety of vehicle systems and manufacturing processes to reduce risk to the Orion missions and flight crew. A critical contributor to crew safety is the heat shield that protects the crew capsule during re-entry through the earth’s atmosphere for return from deep space. The first flight test vehicle, EFT-1, was manufactured and tested in the Neil Armstrong Operations and Checkout (O&C) facility at KSC to demonstrate early risk reduction including the functionality of the Thermal Protection Systems (TPS) for capsule safe return to earth. The approach for the EFT-1 heat shield utilized a low risk approach using Apollo heritage design and manufacturing processes using an Avcoat TPS ablator with a honeycomb substrate to provide a one piece heat shield to meet the mission re-entry heating environments. The manufacturing processes used honeycomb cell injection guns which were redeveloped from the Apollo Lunar Program processes to build the EFT-1 heat shield. The completed heat shield was transported across the country by aircraft to the O&C at KSC for installation onto the capsule. The EFT-1 heat shield successfully performed its mission and experienced ~80% of the re-entry velocity (50% heating rate) for a lunar return for an Exploration Mission. The second flight test vehicle is the EM-1 mission which will have additional flight systems installed to fly to the moon and return. Heat shield design and producibility improvements have been incorporated in the EM-1 vehicle to meet deep space mission and programmatic requirements. The design continues to use the Avcoat material, but in a “block” configuration to enable improvements in the application processes as well as additional improvements in the carrier structure design and manufacturing operations. Incorporating flight test results and producibility improvements from EFT-1 for the heat shield system design and processes have improved the thermal protection capability, improved the producibility, and cost for EM-1 flight test.

Producibility↗

Mars Sample Return (MSR) Sample Receiving Facility (SRF) Assessment Study (MSAS)

NASA, in partnership with the European Space Agency (ESA), is seeking to return Martian geological and atmospheric samples to Earth for scientific study in the early 2030s. Due to the possibility that the samples could contain extraterrestrial life, Mars Sample Return (MSR) is classified as a Category V: Restricted Earth Return mission by the NASA Planetary Protection Office. As a result of this classification, a MSR Sample Receiving Facility (SRF) must not only provide a pristine environment to ensure samples are protected from terrestrial contamination for scientific investigations, it must also provide high-containment (biosafety level 4 [BSL-4]-equivalence) to isolate the samples from Earth’s biosphere until the samples are deemed safe for release and/or sterilized. The nominal utilization period for a SRF is anticipated to be 2-5 years and is intended to enable curation activities, biohazard assessment, select early science activities, and the rapid release of samples to the scientific community. However, to account for possible delays in schedule or the identification of extant life, this anticipated period of time must be flexible to accommodate schedule extensions and contingency plans. Due to requirements for high-level biological containment and cleanliness, a traditional receiving/curation facility cannot be utilized for MSR. Therefore, beginning in 2022, NASA Johnson Space Center is performing a MSR SRF Assessment Study (MSAS) to investigate the most optimal facility modality for a MSR SRF, as well as start to define programmatic early estimate of costs and schedules before the initial design phase begins. NASA is partnering with industry contractors (architectural and engineering firms with BSL-4 and cleanroom technology experience, as well as other contracted infrastructure and construction specialists) along with selected experts from NASA, ESA, existing U.S. BSL-4 facilities, and other U.S. government agencies, to carry out the assessment study. The MSAS should also aid in the future refinement of the science requirements (e.g., contamination control, equipment accommodations) before site-specific design would commence. As part of the MSAS, NASA is planning to assess an array of possibilities for a MSR SRF. One of the main considerations is the facility modality and whether an existing BSL-4 facility can be utilized (for some or all functions); or, if new constructure would be required, would a traditional fixed facility or a modular facility the best choice. MSAS will also investigate the ability of the modalities to accommodate two different facility capability endmembers: 1) a minimal facility focusing on biohazard assessment and curation tasks with a small footprint, and 2) an enhanced facility with additional capabilities to enable expedited processing and the completion of time-sensitive and (some) sterilization-sensitive science. The assessment is intended to generate information that will inform the selection of facility modalities for high-level conceptual design development. While the assessment study will focus on SRF requirements for accommodating curation, science, and sample safety assessment infrastructure, it will also consider an array of other factors, such as ease of access for international users, decommissioning, repurposing, future sale or lease following MSR’s use of the facility, and uncontained preparatory laboratory spaces. Upon completion of the study, the preferred modality and refined requirements would be utilized for site-specific design but will not be finalized until NASA’s completion of the National Environmental Policy Act (NEPA) process.

A.D. Harrington↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗