Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “ARCHITECTS”

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 559 records · Page 31

Design Principles for Smallsat SARs

Synthetic Aperture Radar (SAR) is by now a mature remote sensing technique to obtain spatially-resolved radar measurements of terrain. Currently, SAR image data are readily available from an ever-expanding multitude of SAR satellites in Earth orbit. Many spaceborne SAR systems currently in use or planned for the near-term are multifunctional: their designs tend to maximize the menu of image modes available to the end user. They also follow fairly conventional design principles, laid down decades ago, that lead almost inevitably to large antennas and even larger spacecraft. This raises the question: how does one go about designing a SAR system that fits in a Smallsat (<200 kg) form factor? The design principles for Smallsat SARs outlined in this paper have been developed over a twenty-year period in architecting Earth-orbiting SARs such as NASA/JPL’s NISAR and ESA’s Biomass mission, as well as planetary SAR mission concepts. Example mission concepts following this approach will be presented at the end of the paper. These include an S-Band Smallsat geodetic constellation to measure surface deformation, as called for by the 2018 National Academy Decadal Survey for Earth Observation from Space. Another example is a Ka-band cubesat-sized system designed to detect changes on Earth’s surface.

Freeman, Anthony↗

Refactoring the Curiosity Rover's sample handling architecture on Mars

The Curiosity Mars rover sample handling hardware and software were architected assuming that end-to-end sampling operations would occur in a single rover position, from acquisition of a powdered sample with a scoop or drill, through to the cleaning out of all sample residue in the sample chain. However, after analysis of the first drilled samples in Yellowknife Bay, the science team wanted to iterate with additional experiments on Mars and in laboratories on Earth to better understand their results and increase the value of science returned. With the architecture as conceived, the time needed to do so was in direct competition with the exploration of other targets and satisfaction of success criteria during the prime mission.

Kuhn, Stephen↗

Design of Space Systems to Enable In-space Assembly and Servicing

For several decades, NASA has employed in-space systems to enhance the performance and extend the useful life of operational orbital assets. In at least one case, an operational mission was not only enhanced, but enabled – the International Space Station was made possible by crewed and robotic in-space assembly, and continues to support installation and operation of new science and technology payloads. In several cases (Hubble Space Telescope, Intelsat 401, Westar and Palapa), major operational assets were rescued or repaired soon after launch when otherwise mission-ending anomalies occurred or were detected. In addition to the original rescue, Hubble was upgraded four times, enabling high-demand, world class science over four decades. More recently, two Northrop Grumman Mission Extension Vehicles have captured two Intelsat spacecraft near the end of their life and fuel capacity, to take over maneuvering duties. In spite of these recent operational achievements, and with the exception of large human exploration vehicles and large space telescopes, space architects rarely consider in-orbit servicing and assembly capabilities in their future planning. Technologies such as multi-launch mission architectures (and rendezvous and proximity operations systems), docking systems, external robotics, advanced tools, modular systems and structures, and fluid transfer systems are available today to support these missions. In-space manufacturing will soon be operational to enable resilient missions that recover from on-orbit failures, and expand the utilization of space. We envision a future that includes these capabilities, and discuss the cultural, engineering, and technological challenges to achieving this vision. We discuss the vision, the proverbial chicken and the egg (which came first, the serviceable spacecraft or the servicer?), the cost, risk, and perceptions thereof of in-space operations, a “spectrum” of cooperative servicing design considerations, and the current status of the space industry’s slow but steady march to widespread operational use of on-orbit servicing, assembly, and manufacturing.

Bo Naasz↗

Gateway bi-propellant refueling development testing and model validation activities

The Gateway is an upcoming long term lunar exploration program to be completed by NASA in partnership with ESA and other US and international partners. The system design of the Gateway contains both a high performance Xenon based Solar Electric Propulsion system, as well as a bi-propellant attitude control system. Both propulsion systems are designed for on-orbit refueling to enable long life performance of the Gateway. The ESPRIT-RM is a module which will expand the pressurized volume of Gateway, while also providing refueling capability for both the Xenon and Bipropellant propulsion systems, therefore extending the Gateway life on orbit. As part of the Gateway bi-propellant refueling system development, a simplified fluidic breadboard system was created to evaluate system performance and response using simulant fluids. The test plan includes verification activities with simulant (water, HFE-7100) to verify joined subsystem behavior in the critical operations, including propellant transfer demonstration between modules, transient tests and venting tests. Integrated testing occurred at TASUK in collaboration with NASA to support joint verification activities to de-risk the major functions of the ESPRIT BTS and the overall CONOPS of the refueling of the Gateway chemical propulsion system. Initially collected test data from the system testing is presented, as well as initial model validation, and correlated to collected high frequency test data and system response is shown. Initially collected data has shown the architected system performance is closing initial design assumptions, but much forward work remains to characterize and develop the system.

Christopher Daniel Radke↗

A Robotically Assembled and Serviced Science Station for Earth Observations

In this paper we present the overall architecture of a ”Science Station”, a robotically assembled and serviced persistent platform that can host multiple payloads for Earth observations. Recent decadal survey findings motivate the need to have spatial and temporal concurrency in measurements from multiple instruments. We have architected the science station to simultaneously host up to twelve Earth Venture class instruments at a time. These instruments can be replaced by newer instruments periodically to take advantage of evolving science needs and technology capabilities. The Science Station can also concurrently host science, commercial, defense and other national interest payloads. The Science Station may provide a cost-effective paradigm by mitigating some of the risks and costs associated with multiple free-flyers that may otherwise be needed for the various instruments. It leverages emergent and existent technologies in robotic assembly and servicing, lower cost commercial launch vehicles, secondary launch vehicles, and rendezvous and proximity operations. In this paper, we report the findings of a survey we conducted on the desired performance of the Science Station from various instrument hosting perspectives. We report the various trade studies that we conducted to developed a feasible architecture that meets the goals of the Science Station while also meeting the constraints of a space system. We also report the various considerations in the configuration, thermal system, pointing system, overall concept of operations, and the robotic system of the Science Station architecture. The paper then describes a testbed activity we are undertaking to evaluate the supervised autonomy robotics needed for the Science Station as well as to conduct a riskreduction demonstration of the end-to-end robotics behaviors.

Mukherjee, Rudranarayan↗

The Evolution of Team-X: 25 Years of Concurrent Engineering Design Experience

Established in 1995 in response to NASA’s “Faster, Better, Cheaper” era, Team-X was born from a need to perform rapid space mission design for principal investigator-led competed proposals. The success and sustainability of Team-X over the 25 years that have followed is directly attributable to the Team-X business model and its evolution over time. While dozens of organizations and institutions have emulated the Team-X design process, there are nuances to the Team-X business model that are unique to JPL, and explain why it is different than other concurrent design teams. One of the key components of a business model is the customer segments that are served. Team-X was founded to conduct the Pre-Phase A work necessary to formulate a portfolio of multiple planetary mission concepts, but has since expanded to include the capability to conduct studies for Earth science, astrophysics, and heliophysics missions as well as Human Exploration and Operations missions and space technology development. Team-X delivers value to its clients both in terms of speed and cost. Team-X has also added value by creating teams to enable the development of Instrument and SmallSat Concepts. Value has further been enhanced through a revision of its process for reviews and the addition of pre-design architecting capabilities. Other aspects of the Team-X infrastructure, in addition to study process, have enabled it to succeed for over a quarter century. From our most important resource, the people, our tools, especially for cost estimating, as well as our increasing capable IT infrastructure have contributed to our capability to meet the demands of our clients. The Team-X business model and its evolution over time, position it well for success in the decades to come.

Murphy, Jonathan↗

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗

Joint Development Testing of the Integrated Gateway-Esprit Bipropellant Refuelling System

The Gateway is an upcoming long term lunar exploration program to be completed by NASA in partnership with ESA and other US and international partners. The system design of the Gateway contains both a high performance Xenon based Solar Electric Propulsion system, as well as a bi-propellant attitude control system. Both propulsion systems are designed for on-orbit refuelling to enable long life performance of the Gateway. The ESPRIT-RM is a module which will expand the pressurized volume of Gateway, while also providing refuelling capability for both the Xenon and Bipropellant propulsion systems, therefore extending the Gateway life on orbit. As part of the Gateway bi-propellant refuelling system development, a simplified fluidic breadboard system was created to evaluate system performance and response using simulant fluids. The test plan includes verification activities with simulant (water, HFE-7100) to verify joined subsystem behaviour in the critical operations, including propellant transfer demonstration between modules, transient tests and venting tests. Integrated testing will occur at TASUK in collaboration with NASA to support joint verification activities to de-risk the major functions of the ESPRIT Bipropellant Transfer Subsystem (BTS) and the overall CONOPS of the refuelling of the Gateway chemical propulsion system. Initially collected test data is presented and has shown the architected system performance is closing initial design assumptions, but much forward work is identified to continue to characterize and develop the system.

Sebastian Hill↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability that can spawn a new approach to mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low TRL concepts into workable solutions for issues in trash management, CO2 processing, foam re-processing, and fecal processing. The results of the crowdsourcing activities are summarized along with a roadmap for future technology development work.

Logistics reduction↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

Updating the Thermal Vacuum Chambers at the NASA Johnson Space Center

Chambers A and B are two large thermal vacuum chambers at Johnson Space Center which enable space simulation for unmanned and human-rated missions, respectively. With the resurgence in deep space missions for scientific research and various private commercial ventures, these chambers are expected to be used frequently for at least the next decade. For qualifying the James Webb Space Telescope, upgrades to Chamber A were performed which included the addition of a 12.5 kW refrigeration system with helium shrouds capable of simulating deep space environment and an efficient and reliable LN2 natural flow thermosiphon system for the thermal shield. Continuous improvements since then have focused on ensuring operational readiness by modernizing the data acquisition, recording, controls, and visualization systems for both chambers and clean room. These upgrades will be the focus of this paper. Controlling the Cryochambers was enhanced by moving from a 32-bit SCADA system to a 64-bit architected system. Infrastructural changes involved installing redundant power circuits, adding new servers, network switches, and including load balancing with fail-over between servers to minimize downtime. Instead of distributed servers, 3 redundant servers are used to share configurations. Configurations are now kept in a shared SQL instance making it easy to deploy and maintain. During this upgrade process many sub-systems (PLCs and NI PXI interfaces to sensors) were upgraded from the prior OPC-DA to the more secure OPC-UA protocol. Cryo-system PLCs were updated to allow Ganni cycle floating pressure calculations from any cold box to be sent to any compressor. During the project, the team recreated over 70,000 live data points, 50000 historical data points, and 4000 alarms. Finally, the graphical interfaces were upgraded to support HTML 5 in conjunction shared pages were implemented reducing the total number of webpages by over 75%. These system updates reinvigorated the previous SCADA system which had reached its end of life. The same look and feel was maintained while providing operators with an updated interface to control, troubleshoot, and record. The new system architecture is more robust and easier to maintain creating a path forward to address remaining problem points and implement additional features.

Cody Schaefer↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗

The Internet of Animals: How to Use NASA's Assets and Computing for Biodiversity and Conservation Needs

There are many internal and external drivers of animal movement. For example, where might an animal go if it’s hungry, or how will it move if it’s really windy? The Internet of Animals project aims to combine animal telemetry data with earth observations to better support applied ecological management, architect a next-generation space-based animal tracking system and develop technology that can link to biodiversity and habitats via remote sensing. In this talk, Morgan Gilmour will provide an overview of movement ecology, remote sensing, and how earth observations with NASA’s assets can help inform biodiversity and conservation. Morgan is a Research Scientist at NASA Ames Research Center. Her research focuses on marine animal movement ecology. Some recent projects include investigating animal movement in relation to marine protected areas in the central Pacific and quantifying at-sea habitat use by albatrosses.

animal telemetry↗

The Mars 2020 Ground Data System Architecture

The Mars 2020 Mission’s primary objective is to collect 20 geographically unique samples during its prime mission of one and a quarter Martian years, or just over 2 Earth years. Mission planners determined the project needed to develop a system that would enable the operations team to analyze engineering and science data, make science decisions, select viable rover targets at a millimeter resolution and validate an uplink bundle for a car sized rover with more complex science instruments than any previous Mars surface mission. All this had to be done within a five hour time frame. Doing this with a small team would be a challenge, but this had to be accomplished by a large team of engineers and scientists located across North America and Europe. Achieving this level of operational efficiency was unheard of in the prime mission. In addition, the mission had another set of requirements that had nothing to do with surface operations; the Mars 2020 Ground Data System (GDS) was also expected to comply with a new set of security requirements to keep up with the ever changing cybersecurity landscape. The Mars 2020 Ground Data System (GDS) is a re-architected version of the Mars Science Laboratory GDS. The primary goal was to integrate the lessons learned from previous Mars surface missions, accommodate a set of new requirements and capabilities required to ensure mission success, and comply with a new set of cybersecurity controls. The new architecture includes several unique qualities including a data lake, language-agnostic system-wide event-based operations, containerization, automated deployment, network segmentation, infrastructure-as-code, API-driven interfaces, and the first Mars surface GDS to operate primarily in the cloud. The new architecture enabled greater access to the system’s data, tighter integration with the operations team, and a higher level of traceability. The availability of the data also enabled a new set of capabilities previously not possible on surface missions. These new capabilities include an autonomous data to information, pipeline for downlink analysis, horizontal scaling of science data processing capabilities, autonomous round trip data tracking of science and engineering data, integration of flight system state into the tactical planning cycle, high fidelity targeting utilizing kinematic data, and hierarchical image and 3d meshes data representations. This paper will introduce the requirements for the Mars 2020 Mission, the heritage architecture, and the rationale for the changes to achieve the new architecture. The paper will continue to describe the fundamental changes made to the GDS architecture, how these changes enabled a more tightly integrated GDS, and the new capabilities that were enabled by the new architecture. The paper will conclude with the lessons learned from the process of rearchitecting a heritage GDS system and from the first 200 days of operations supporting over 800 users from around the world.

Lopez-Roig, Reynaldo↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability leading to innovative approaches to space mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low Technology Readiness Level (TRL) concepts into workable solutions for issues in trash management, CO 2 processing, foam reprocessing, and fecal processing. The results of the crowdsourcing activities are summarized along with a discussion for future technology development work.

Logistics reduction↗

Updating the Thermal Vacuum Chambers at the NASA Johnson Space Center

Chambers A and B are two large thermal vacuum chambers at Johnson Space Center which enable space simulation for unmanned and human-rated missions, respectively. With the resurgence in deep space missions for scientific research and various private commercial ventures, these chambers are expected to be used frequently for at least the next decade. For qualifying the James Webb Space Telescope, upgrades to Chamber A were performed which included the addition of a 12.5 kW refrigeration system with helium shrouds capable of simulating deep space environment and an efficient and reliable LN2 natural flow thermosiphon system for the thermal shield. Continuous improvements since then have focused on ensuring operational readiness by modernizing the data acquisition, recording, controls, and visualization systems for both chambers and clean room. These upgrades will be the focus of this paper. Controlling the Cryochambers was enhanced by moving from a 32-bit SCADA system to a 64-bit architected system. Infrastructural changes involved installing redundant power circuits, adding new servers, network switches, and including load balancing with fail-over between servers to minimize downtime. Instead of distributed servers, 3 redundant servers are used to share configurations. Configurations are now kept in a shared SQL instance making it easy to deploy and maintain. During this upgrade process many sub-systems (PLCs and NI PXI interfaces to sensors) were upgraded from the prior OPC-DA to the more secure OPC-UA protocol. Cryo-system PLCs were updated to allow Ganni cycle floating pressure calculations from any cold box to be sent to any compressor. During the project, the team recreated over 70,000 live data points, 50000 historical data points, and 4000 alarms. Finally, the graphical interfaces were upgraded to support HTML 5 in conjunction shared pages were implemented reducing the total number of webpages by over 75%. These system updates reinvigorated the previous SCADA system which had reached its end of life. The same look and feel was maintained while providing operators with an updated interface to control, troubleshoot, and record. The new system architecture is more robust and easier to maintain creating a path forward to address remaining problem points and implement additional features.

Cody Schaefer↗

Considerations For Waste-to-Base Future Research Paths

Developing innovative technologies to reprocess low value waste into high value base products will enable a new “Waste-to-Base” (WtB) capability leading to innovative approaches to space mission design. Systems engineers and mission architects will work together under a new paradigm in logistics planning. Equipment, components, packaging, storage, and structures will be understood not only by functional requirements, but also in terms of useful lifetimes and materials of construction. The advent of a new technical discipline - reprocess engineering - will grow from the intersection between chemical, mechanical, and systems engineering, mission design, and logistics planning. A crowdsourcing approach was employed to gather low Technology Readiness Level (TRL) concepts into workable solutions for issues in trash management, CO2 processing, foam reprocessing, and fecal processing. The results of the crowdsourcing activities are summarized along with a discussion for future technology development work.

Logistics reduction↗

SatCORPS Global Cloud Composite (GCC): the Design and Delivery of A High Quality, High Resolution, Global Cloud Product Available in Near-Real Time

The NASA Satellite ClOud and Radiation Property retrieval System (SatCORPS) supports the development of an analysis ready and cloud-optimized data transformation pipeline and geospatial service enablement of a global cloud composite (GCC) product derived from global geostationary satellite imagery. This geospatial service will be available at high temporal and spatial resolution via the SatCORPS web mapping application for visualization and analysis as well as direct ingestion to common geospatial software and custom programming. The resulting global cloud composite products from the processing pipeline can then be geospatially-service enabled as ArcGIS Image Services and Open Geospatial Consortium (OGC) Web Mapping/Coverage Services for visualization and analysis via a web mapping application and common geospatial software. Near real time global observations are created through the composition of five geostationary satellites that provides modelling and forecasting communities with the capability to provide high quality and timely information to start the projection process. The Global Cloud Composite product combines information from geostationary satellites, GOES-16, GOES-17, Himawari-8, Meteosat-11 and Meteosat-9 to create a single global composite netcdf file and images using the different products within the netcdf file. The SatCORPS team, though our Global Cloud Composite (GCC) product and web-based visualization tools including Geographical Information System (GIS) services provide near real time global cloud product information to both automated processes and traditional web users that is timely and high quality derived from geostationary satellites. The Global Cloud Composite product takes advantage of the scalable processing resources provided by the AWS batch service to provide new composites every thirty minutes. Because information from each of the low earth orbiting satellites is available on schedules tuned to the specific satellite, the processing algorithm temporally composites the final dataset as each satellite’s information becomes available. The SatCORPS team has leveraged our experience using Amazon Web Services (AWS) to build a low latency high availability tool that allows end users both human and automated to acquire high quality and high-resolution Geostationary Earth Orbiting (GEO) information at zero cost to the end user. This presentation will describe how we architected and implemented the service as well as lessons learned based on our experiences both developing and operating the system. The lessons learned include how we integrated multiple services including Amazon Batch, Amazon S3 and Amazon Lambda service to create a low cost but high-performance processing system that is capable of identifying and processing the most appropriate satellite overpass information into global cloud composites. We will also describe our web-based tools including our Geographic Information System that can be used for visualization and analysis. The products from the processing can be geospatially-service enabled as ArcGIS Image Services and Open Geospatial Consortium (OGC) Web Mapping/Coverage Services for visualization and analysis via a web mapping application and common geospatial software. The SatCORPS Global Composite Cloud product provides sophisticated global composited cloud research products with very low latency that we see that as filling a rapidly growing need in the research and modelling community with no up-front nor ongoing costs associated with downloading or using the information.

AWS AMCE SMCE GCC SATCORPS GLOBAL CLOUD COMPOSITE ↗