Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Operational Support System”

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 649 records · Page 36

Using the SPICE System to Help Plan and Interpret Space Science Observations

A portable multimission information system named SPICE is used to assemble, archive, and provide easy access to viewing and other ancillary information needed by space scientists to interpret observations of bodies within our solar system. The modular nature of this system lends it to use in planning such observations as well. Since a successful proof of concept on Voyager, the SPICE system has been adapted to several recent JPL spacecraft missions and a variety of ground based operations. Other adaptations are underway. SPICE has been used to support observation planning for moving targets on the Hubble Space Telescope Project. Applications for SPICE on earth science, space physics, and other astrophysics missions are under consideration.

data↗

Coupling Subsurface and Above-Surface Models for Optimizing the Design of Borefields and District Heating and Cooling Systems

Accurate dynamic energy simulation is important for the design and sizing of district heating and cooling systems with geothermal heat exchange for seasonal energy storage. Current modeling approaches in building and district energy simulation tools typically consider heat conduction through the ground between boreholes without flowing groundwater. While detailed simulation tools for subsurface heat and mass transfer exist, these fall short in simulating above-surface energy systems. To support the design and operation of such systems, the study developed a coupled model including a software package for building and district energy simulation, and software for detailed heat and mass transfer in the subsurface. For the first, it uses the open-source Modelica Buildings Library, which includes dynamic simulation models for building and district energy and control systems. For the heat and mass transfer in the soil, it uses the TOUGH simulator. The TOUGH family of codes can model heat and multi-phase, multi-component mass transport for a variety of fluid systems, as well as chemical reactions, in fractured porous media. The study validated the coupled modeling approach by comparing the simulation results with one from the g-function based ground response model. It then looked into effects when the water table and the regional groundwater flow are considered in the ground, from the perspective of heat exchange between borehole and ground, and the electrical consumption of the district heating and cooling systems. To access the simulation models, please find the links in the submission: -- For coupled approach validation: see model Buildings.Fluid.Geothermal.Borefields.Examples.BorefieldsWithTough and Buildings.Examples.DistrictReservoirNetworks.Examples.Reservoir3Variable_TOUGH from the "Modelica Building Library" resource, branch issue1495_tough_interface, commit a2667c0. -- For the study of the effect of water table: see model Buildings.Examples.DistrictReservoirNetworks.Examples.Reservoir3Variable_TOUGH from he "Modelica Building Library" resource, branch issue1495_tough_interface_moreIO, commit 760de49. -- For the study of the effect of regional groundwater flow: see Buildings.Examples.DistrictReservoirNetworks.Examples.Reservoir3Variable_TOUGH from he "Modelica Building Library" resource, branch issue1495_tough_interface_moreIO_3D, commit c2a2d2a. The coupling interface script "GrounResponse.py" can be found from the above links in the folder Buildings/Resources/Python-Sources. Also, the needed files for TOUGH simulation are in the folder Buildings/Resources/Python-Sources/ToughFiles that can be accessed through the above links. A brief description of these files is given below; detailed specifications for the first three files may be found in the TOUGH3 Users Guide (Jung et al., 2018) https://tough.lbl.gov/documentation/tough-manuals/. (1) INCON - initial conditions for each grid block (2) INFILE - main input file with material properties and control parameters (3) MESH - description of the computational grid (4) readsave - Modelica/TOUGH interface program: read the final output of TOUGH simulation after TOUGH time step and prepare for transfer to Modelica for next Modelica time step (5) readsave.inp - input parameters for program readsave (6) writeincon - Modelica/TOUGH interface program: write the output of Modelica after Modelica time step and prepare for transfer to TOUGH as initial conditions for the next TOUGH step (7) writeincon.inp - input parameters for program writeincon

15 GEOTHERMAL ENERGY↗

Recommended techniques for effective maintainability. A continuous improvement initiative of the NASA Reliability and Maintainability Steering Committee

This manual presents a series of recommended techniques that can increase overall operational effectiveness of both flight and ground based NASA systems. It provides a set of tools that minimizes risk associated with: (1) restoring failed functions (both ground and flight based); (2) conducting complex and highly visible maintenance operations; and (3) sustaining a technical capability to support the NASA mission using aging equipment or facilities. It considers (1) program management - key elements of an effective maintainability effort; (2) design and development - techniques that have benefited previous programs; (3) analysis and test - quantitative and qualitative analysis processes and testing techniques; and (4) operations and operational design techniques that address NASA field experience. This document is a valuable resource for continuous improvement ideas in executing the systems development process in accordance with the NASA 'better, faster, smaller, and cheaper' goal without compromising safety.

Source record↗

Advanced transportation system studies. Technical area 2: Heavy lift launch vehicle development: Technical Results - Volume 2

Sections 10 to 13 of the Advanced Transportation System Studies final report are included in this volume. Section 10 contains a copy of an executive summary that was prepared by Lockheed Space Operations Company (LSOC) to document their support to the TA-2 contract during the first-year period of performance of the contract, May 1992 through May 1993. LSOC participated on the TA-2 contract as part of the concurrent engineering launch system definition team, and provided outstanding heavy lift launch vehicle (HLLV) ground operations requirements and concept assessments for Lockheed Missiles and Space Company (LMSC) through an intercompany work transfer as well as providing specific HLLV ground operations assessments at the direction of NASA KSC through KSC funding that was routed to the TA-2 contract. Section 11 contains a copy of a vehicle-independent, launch system health management requirements assessment. The purpose of the assessment was to define both health management requirements and the associated interfaces between a generic advanced transportation system launch vehicle and all related elements of the entire transportation system, including the ground segment. Section 12 presents the major TA-2 presentations provided to summarize the significant results and conclusions that were developed over the course of the contract. Finally, Section 13 presents the design and assessment report on the first lunar outpost heavy lift launch vehicle.

Source record↗

High performance VLSI telemetry data systems

NASA's deployment of major space complexes such as Space Station Freedom (SSF) and the Earth Observing System (EOS) will demand increased functionality and performance from ground based telemetry acquisition systems well above current system capabilities. Adaptation of space telemetry data transport and processing standards such as those specified by the Consultative Committee for Space Data Systems (CCSDS) standards and those required for commercial ground distribution of telemetry data, will drive these functional and performance requirements. In addition, budget limitations will force the requirement for higher modularity, flexibility, and interchangeability at lower cost in new ground telemetry data system elements. At NASA's Goddard Space Flight Center (GSFC), the design and development of generic ground telemetry data system elements, over the last five years, has resulted in significant solutions to these problems. This solution, referred to as the functional components approach includes both hardware and software components ready for end user application. The hardware functional components consist of modern data flow architectures utilizing Application Specific Integrated Circuits (ASIC's) developed specifically to support NASA's telemetry data systems needs and designed to meet a range of data rate requirements up to 300 Mbps. Real-time operating system software components support both embedded local software intelligence, and overall system control, status, processing, and interface requirements. These components, hardware and software, form the superstructure upon which project specific elements are added to complete a telemetry ground data system installation. This paper describes the functional components approach, some specific component examples, and a project example of the evolution from VLSI component, to basic board level functional component, to integrated telemetry data system.

Chesney, J.↗

Space propulsion

Lewis Research Center is developing broad-based new technologies for space chemical engines to satisfy long-term needs of ETO launch vehicles and other vehicles operating in and beyond Earth orbit. Specific objectives are focused on high performance LO2/LH2 engines providing moderate thrusts of 7,5-200 klb. This effort encompasses research related to design analysis and manufacturing processes needed to apply advanced materials to subcomponents, components, and subsystems of space-based systems and related ground-support equipment. High-performance space-based chemical engines face a number of technical challenges. Liquid hydrogen turbopump impellers are often so large that they cannot be machined from a single piece, yet high stress at the vane/shroud interface makes bonding extremely difficult. Tolerances on fillets are critical on large impellers. Advanced materials and fabricating techniques are needed to address these and other issues of interest. Turbopump bearings are needed which can provide reliable, long life operation at high speed and high load with low friction losses. Hydrostatic bearings provide good performance, but transients during pump starts and stops may be an issue because no pressurized fluid is available unless a separate bearing pressurization system is included. Durable materials and/or coatings are needed that can demonstrate low wear in the harsh LO2/LH2 environment. Advanced materials are also needed to improve the lifetime, reliability and performance of other propulsion system elements such as seals and chambers.

Kazaroff, John M.↗

KSC ground operations planning for Space Station

At the Kennedy Space Center (KSC) in Florida, processing facilities are being built and activated to support the processing, checkout, and launch of Space Station elements. The generic capability of these facilities will be utilized to support resupply missions for payloads, life support services, and propellants for the 30-year life of the program. Special Ground Support Equipment (GSE) is being designed for Space Station hardware special handling requirements, and a Test, Checkout, and Monitoring System (TCMS) is under development to verify that the flight elements are ready for launch. The facilities and equipment used at KSC, along with the testing required to accomplish the mission, are described in detail to provide an understanding of the complexity of operations at the launch site. Assessments of hardware processing flows through KSC are being conducted to minimize the processing flow times for each hardware element. Baseline operations plans and the changes made to improve operations and reduce costs are described, recognizing that efficient ground operations are a major key to success of the Space Station.

Lyon, J. R.↗

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↗

Technology Transfer Challenges: A Case Study of User-Centered Design in NASA's Systems Engineering Culture

The Upper Stage (US) section of the National Aeronautics and Space Administration's (NASA) Ares I rocket will require internal access platforms for maintenance tasks performed by humans inside the vehicle. Tasks will occur during expensive critical path operations at Kennedy Space Center (KSC) including vehicle stacking and launch preparation activities. Platforms must be translated through a small human access hatch, installed in an enclosed worksite environment, support the weight of ground operators and be removed before flight - and their design must minimize additional vehicle mass at attachment points. This paper describes the application of a user-centered conceptual design process and the unique challenges encountered within NASA's systems engineering culture focused on requirements and "heritage hardware". The NASA design team at Marshall Space Flight Center (MSFC) initiated the user-centered design process by studying heritage internal access kits and proposing new design concepts during brainstorming sessions. Simultaneously, they partnered with the Technology Transfer/Innovative Partnerships Program to research inflatable structures and dynamic scaffolding solutions that could enable ground operator access. While this creative, technology-oriented exploration was encouraged by upper management, some design stakeholders consistently opposed ideas utilizing novel, untested equipment. Subsequent collaboration with an engineering consulting firm improved the technical credibility of several options, however, there was continued resistance from team members focused on meeting system requirements with pre-certified hardware. After a six-month idea-generating phase, an intensive six-week effort produced viable design concepts that justified additional vehicle mass while optimizing the human factors of platform installation and use. Although these selected final concepts closely resemble heritage internal access platforms, challenges from the application of the user-centered process provided valuable lessons for improving future collaborative conceptual design efforts.

Quick, Jason↗

Turbofan Engine Power Extraction Demonstration Final Report

As GE Aerospace advances toward a revolutionary step change in propulsion efficiency, the integration and demonstration of new engine architectures and technology systems are essential. The NASA Turbofan Engine Power Extraction Demonstration (PEx), conducted through the Hybrid Thermally Efficient Core (HyTEC) project, aims to develop and demonstrate megawatt-class hybrid electric capability on a modern commercial turbofan engine. The hybrid electric system is critical to meeting the needs of the U.S. aviation industry for next-generational propulsion systems with greater efficiency, durability, and range. This supports energy independence and helps ensure the security and resilience of one of America's largest export industries. The PEx project specifically targets three key objectives: mechanically integrating hybrid electric capability into a commercial turbofan engine, integrating electric machine control with turbofan control for advanced power management, and de-risking performance modeling of future hybrid electric architectures. To mature these technologies to Technology Readiness Level (TRL) 6, a series of electric power system component tests and a baseline engine performance test campaign were conducted. These efforts culminated in an integrated hybrid electric turbofan test campaign demonstrating power extraction, power insertion, and power transfer between spools. Tests of the electric power system were completed at GE Aerospace’s Electrical Power Integrated Systems Center in Dayton, Ohio and engine tests were completed at Peebles Test Operation in Peebles, Ohio. Hybrid electric trade studies extended the demonstrated capability to altitude using the validated cycle model from the PEx test campaigns, allowing for comments on expanded mission benefits not demonstrated in the ground campaign. The knowledge gained from PEx also supports GE Aerospace’s Compact Core Demonstrator as part of HyTEC Phase 2 and ultimately informs the implementation of hybrid electric systems in the next generation of GE Aerospace commercial engine products. This report provides a summary of the program background, test campaigns, trade studies, and insights into the technical maturation required to support future commercial products.

Hybrid Electric↗

Predictability of Top of Descent Location for Operational Idle-Thrust Descents

To enable arriving aircraft to fly optimized descents computed by the flight management system (FMS) in congested airspace, ground automation must accurately predict descent trajectories. To support development of the trajectory predictor and its uncertainty models, commercial flights executed idle-thrust descents at a specified descent speed, and the recorded data included the specified descent speed profile, aircraft weight, and the winds entered into the FMS as well as the radar data. The FMS computed the intended descent path assuming idle thrust after top of descent (TOD), and the controllers and pilots then endeavored to allow the FMS to fly the descent to the meter fix with minimal human intervention. The horizontal flight path, cruise and meter fix altitudes, and actual TOD location were extracted from the radar data. Using approximately 70 descents each in Boeing 757 and Airbus 319/320 aircraft, multiple regression estimated TOD location as a linear function of the available predictive factors. The cruise and meter fix altitudes, descent speed, and wind clearly improve goodness of fit. The aircraft weight improves fit for the Airbus descents but not for the B757. Except for a few statistical outliers, the residuals have absolute value less than 5 nmi. Thus, these predictive factors adequately explain the TOD location, which indicates the data do not include excessive noise.

Stell, Laurel L.↗

Design and Development of Functionally Operative and Visually Appealing Remote Firing Room Displays

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA mentor Kurt Leucht. The main focus was on creating remote displays for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays to be used in the Launch Control Center (LCC) on the Firing Room's computer monitors. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the remote displays. After receiving the requirements, the next step was to create a display that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, will need to be included in each respective display for the system to run properly. Then, once the display was created it needed to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it will need to go through further testing and evaluation before deemed suitable for actual use. By the end of the semester long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of display development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in one of the LCC's firing rooms to fill the new Orion spacecraft.

Ground Support Systems↗

Health monitoring system for the SSME - Program overview

This paper considers the design of a health management system (HMS) program for enhancement of the safety of SSME operations during ground tests and space missions. The fault detection techniques based on time series, nonlinear regression, and clustering algorithms were developed and were demonstrated based on data from SSME ground test failures. The fault detection algorithms of the HMS system exhibited 100 percent detection of faults and an extremely low fault alarm rate, and were robust to sensor loss. A preliminary design of hardware architecture capable of supporting real-time operation of the HMS functions is described.

Hawman, Michael W.↗

The X-15/HL-20 operations support comparison

During the 1960's, the United States X-15 rocket-plane research program successfully demonstrated the ability to support a reusable vehicle operating in a near-space environment. The similarity of the proposed HL-20 lifting body concept in general size, weight, and subsystem composition to that of the X-15 provided an opportunity for a comparison of the predicted support manpower and turnaround times with those experienced in the X-15 program. Information was drawn from both reports and discussions with X-15 program personnel to develop comparative operations and support data. Based on the assumption of comparability between the two systems, the predicted staffing levels, skill mix, and refurbishment times of an operational HL-20 appear to be similar to those experienced by the X-15 for ground support. However, safety, environmental, and support requirements have changed such that the HL-20 will face a different operating environment than existed at Edwards during the 1950's and 1960's. Today's operational standards may impose additional requirements on the HL-20 that will add to the maintenance and support burden estimate based on the X-15 analogy.

Morris, W. Douglas↗

Operation Evaluation of the VEGGIE Food Production System in the Habitat Demonstration Unit

The 2010 Desert Research and Technology Studies (DRATS) of the VEGGIE Food Production System in the Habitat Demonstration Unit (HDU) Pressurized Excursion Module (PEM) was the first operational evaluation of salad crop production technology in a NASA analog test. A systematic evaluation of rooting media and nutrient delivery systems were evaluated for three lettuce cultivars that have shown promise as candidates for a surface based food production system. The VEGGIE nutrient delivery system worked well, was able to be maintained by multiple operators with a minimum of training, and supported excellent lettuce growth for the duration of the test. A Hazard Analysis and Critical Control Point (HACCP) evaluation was performed using ProSantm as sanitation agent prior to consumption was approved, and the crew was allowed to consume the lettuce grown using the VEGGIE light cap and gravity based nutrient delivery system at the completion of the 14-day DRAT field test. The DRAT field test validated the crew operations; Growth of all lettuce cultivars was excellent. The operational DRAT field testing in the HDU identified light quality issues related to morphology and pigment development that will need to be addressed through additional testing. Feedback from the crew, ground support personnel, and human factors leads was uniformly positive on the psychological value of having the crop production system in the excursion module. A number of areas have been identified for future work, to minimize the "footprint" of the Food Production system through creative use of unused wall and floor space in the unit.

Stutte, Gary W.↗

Operational Evaluation of VEGGIE Food Production System in the Habitat Demonstration Unit

The 2010 Desert Research and Technology Studies (DRATS) of the VEGGIE Food Production System in the Habitat Demonstration Unit (HDU) Pressurized Excursion Module (PEM) was the first operational evaluation of salad crop production technology in a NASA analog test. A systematic evaluation of rooting media and nutrient delivery systems were evaluated for three lettuce cultivars that have shown promise as candidates for a surface based food production system. The VEGGIE nutrient delivery system worked well, was able to be maintained by multiple operators with a minimum of training, and supported excellent lettuce growth for the duration of the test. A Hazard Analysis and Critical Control Point (HACCP) evaluation was performed using ProSan(tm) as sanitation agent prior to consumption was approved, and the crew was allowed to consume the lettuce grown using the VEGGIE light cap and gravity based nutrient delivery system at the completion of the 14-day DRAT field test. The DRAT field test validated the crew operations; Growth of all lettuce cultivars was excellent. The operational DRAT field testing in the HDU identified light quality issues related to morphology and pigment development that will need to be addressed through additional testing. Feedback from the crew, ground support personnel, and human factors leads was uniformly positive on the psychological value of having the crop production system in the excursion module. A number of areas have been identified for future work, to minimize the "footprint" of the Food Production system through creative use of unused wall and floor space in the unit.

Stutte, Gary W.↗

Thermal Modeling and Correlation of the Space Environments Complex Vacuum Chamber and Cryoshroud

From Presentation: Formerly known as the Space Power Facility (SPF) Located at Plum Brook Station in Sandusky, OH -- Houses large-scale test facilities including the Space Simulation Vacuum Chamber -- Largest vacuum chamber in the world -- 100 ft diameter, 122 ft tall -- Cryoshroud operates between -250 °F and +140 °F -- To be used for Orion EM-1 thermal vacuum test -- Thermal Desktop model of vacuum chamber, cryoshroud, mechanical ground support equipment (MGSE) including fluid model of GN2 -- Primary uses: Predict MGSE temperatures; Predict heat load on GN2 system -- Includes 96 TD Temperature Measures that represent test thermocouples -- Steady state correlation with 3 tests: 2 hot; 1 cold -- Two ISTs performed with no MGSE inside the cryoshroud: Insulated test: operated at 170 °F for 37 hours; Uninsulated test: operated at 170 °F for 14 days -- Only cryoshroud thermocouples were installed

Thermal modeling↗