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 685 records · Page 38
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy Onboard the International Space Station

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control experiment on-board the International Space Station that demonstrated single action intelligent procedures for crew command and control. The target problem was to enable crew initialization of a facility class rack with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as initialization of a medical facility to respond to a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). Utilization of Draper Laboratory's Timeliner software, deployed on-board the ISS within the Command and Control (C&C) computers and the Payload computers, allowed development of the automated procedures specific to ISS without having to certify and employ novel software for procedure development and execution. The procedures contained the ground procedure logic and actions as possible to include fault detection and recovery capabilities. The autonomous operations concept includes a reduction of the amount of data a crew operator is required to verify during activation or de-activation, as well as integration of procedure execution status and relevant data in a single integrated display. During execution, the auto-procedures (via Timerliner) provide a step-by-step messaging paradigm and a high-level status upon termination. This messaging and high-level status is the only data generated for operator display. To enhance situational awareness of the operator, the Web-based Procedure Display (WebPD) provides a novel approach to the issues of procedure display and execution tracking. WebPD is a web based application that serves as the user interface for electronic procedure execution. It incorporates several aspects of the HTML5 standard. Procedures are written in a dialect of XML called Procedure Representation Language (PRL). WebPD tracks execution status in the procedure or procedures being displayed. WebPD aggregates and simplifies the auto-sequence execution status information, and formatted to be easily followed and understood by an operator who is not dedicated to actively monitoring the task. WebPD also provides an integrated data and control interface to pause or halt the execution in order to provide a check point of operation and to examine progress before starting the next sequence of activities. For this demonstration, the procedure was initiated and monitored from the ground. As the Timeliner sequences executed, their high-level execution status was written to PLMDM memory. This memory is read and downlinked via Ku-Band at a 1 Hz rate. The data containing the high-level execution status is de-commutated on the ground, and rebroadcast for WebPD consumption. A future demonstration will be performed onboard, with ISS astronauts initiating the operations instead of ground controllers. The AMO EXPRESS experiment demonstrated activation and de-activation of EXPRESS rack 7, providing the capability of future single button activations and deactivations of facility class racks. The experiment achieved numerous technical and operations 'firsts' for the ISS

Stetson, Howard K.↗
NASA NTRS2009

Satellite Proving Ground for the GOES-R Geostationary Lightning Mapper (GLM)

The key mission of the Satellite Proving Ground is to demonstrate new satellite observing data, products and capabilities in the operational environment to be ready on Day 1 to use the GOES-R suite of measurements. Algorithms, tools, and techniques must be tested, validated, and assessed by end users for their utility before they are finalized and incorporated into forecast operations. The GOES-R Proving Ground for the Geostationary Lightning Mapper (GLM) focuses on evaluating how the infusion of the new technology, algorithms, decision aids, or tailored products integrate with other available tools (weather radar and ground strike networks; nowcasting systems, mesoscale analysis, and numerical weather prediction models) in the hands of the forecaster responsible for issuing forecasts and warning products. Additionally, the testing concept fosters operation and development staff interactions which will improve training materials and support documentation development. Real-time proxy total lightning data from regional VHF lightning mapping arrays (LMA) in Northern Alabama, Central Oklahoma, Cape Canaveral Florida, and the Washington, DC Greater Metropolitan Area are the cornerstone for the GLM Proving Ground. The proxy data will simulate the 8 km Event, Group and Flash data that will be generated by GLM. Tailored products such as total flash density at 1-2 minute intervals will be provided for display in AWIPS-2 to select NWS forecast offices and national centers such as the Storm Prediction Center. Additional temporal / spatial combinations are being investigated in coordination with operational needs and case-study proxy data and prototype visualizations may also be generated from the NASA heritage Lightning Imaging Sensor and Optical Transient Detector data. End users will provide feedback on the utility of products in their operational environment, identify use cases and spatial/temporal scales of interest, and provide feedback to the developers for adjusted or new products.

Goodman, Steven J.↗
NASA NTRS2004

Ground Support Software for Spaceborne Instrumentation

ION is a system of ground support software for the ion and neutral mass spectrometer (INMS) instrument aboard the Cassini spacecraft. By incorporating commercial off-the-shelf database, Web server, and Java application components, ION offers considerably more ground-support-service capability than was available previously. A member of the team that operates the INMS or a scientist who uses the data collected by the INMS can gain access to most of the services provided by ION via a standard pointand click hyperlink interface generated by almost any Web-browser program running in almost any operating system on almost any computer. Data are stored in one central location in a relational database in a non-proprietary format, are accessible in many combinations and formats, and can be combined with data from other instruments and spacecraft. The use of the Java programming language as a system-interface language offers numerous capabilities for object-oriented programming and for making the database accessible to participants using a variety of computer hardware and software.

Anicich, Vincent↗
NASA NTRS2021

System Validation on the Europa Clipper mission in Early Implementation Phase

NASA’s next flag-ship mission - Europa Clipper, will embark on a journey to Jupiter’s icy moon Europa in 2024 to assess its environment and habitability with a highly capable spacecraft. Post Jupiter-Orbit-Insertion, the spacecraft will be commanded to perform intricate, yet meticulously planned Europa flybys to perform science investigations using a suite of instruments, while withstanding Jupiter’s harsh radiation environment. The success of this mission is dependent on a well-coordinated project and its elements such as the flight hardware and software, the ground support and mission operations teams, procedures and other cross-cutting elements. The Europa Clipper project needs to ensure that these elements are realized at a reasonable confidence level prior to launch and other mission critical events. System Validation test and analysis activities exercise and confirm the integrity of the system of all project elements in the expected flight environment with reasonable stressing conditions. These activities go beyond system design requirements verification and are driven by validation objectives that describe the end-to-end functional and operational capabilities required during nominal and off-nominal flight-like scenarios and critical events. The challenges associated with validating that the Europa Clipper project as a whole can function and perform correctly to meet the intended mission objectives with the as-delivered capabilities of all of its elements are daunting. This paper discusses the systematic methodology established in the early implementation phase of the Europa Clipper project for developing System Validation activities and their validation objectives, and addressing any validation-related challenges on the project. Approaches include decomposition of mission objectives using activity timelines in the Mission Design plan for developing nominal scenarios, use of fault trees for exploring off-nominal cases and system boundaries, and use of Model-based Systems Engineering (MBSE) tools for planning and prioritizing these activities.

Wang, Xu↗
NASA NTRS2016

Tailoring NIST Security Controls for the Ground System: Selection and Implementation -- Recommendations for Information System Owners

The National Aeronautics and Space Administration (NASA) invests millions of dollars in spacecraft and ground system development, and in mission operations in the pursuit of scientific knowledge of the universe. In recent years, NASA sent a probe to Mars to study the Red Planet's upper atmosphere, obtained high resolution images of Pluto, and it is currently preparing to find new exoplanets, rendezvous with an asteroid, and bring a sample of the asteroid back to Earth for analysis. The success of these missions is enabled by mission assurance. In turn, mission assurance is backed by information assurance. The information systems supporting NASA missions must be reliable as well as secure. NASA - like every other U.S. Federal Government agency - is required to manage the security of its information systems according to federal mandates, the most prominent being the Federal Information Security Management Act (FISMA) of 2002 and the legislative updates that followed it. Like the management of enterprise information technology (IT), federal information security management takes a "one-size fits all" approach for protecting IT systems. While this approach works for most organizations, it does not effectively translate into security of highly specialized systems such as those supporting NASA missions. These systems include command and control (C&C) systems, spacecraft and instrument simulators, and other elements comprising the ground segment. They must be carefully configured, monitored and maintained, sometimes for several years past the missions' initially planned life expectancy, to ensure the ground system is protected and remains operational without any compromise of its confidentiality, integrity and availability. Enterprise policies, processes, procedures and products, if not effectively tailored to meet mission requirements, may not offer the needed security for protecting the information system, and they may even become disruptive to mission operations. Certain protective measures for the general enterprise may not be as efficient within the ground segment. This is what the authors have concluded through observations and analysis of patterns identified from the various security assessments performed on NASA missions such as MAVEN, OSIRIS-REx, New Horizons and TESS, to name a few. The security audits confirmed that the framework for managing information system security developed by the National Institute of Standards and Technology (NIST) for the federal government, and adopted by NASA, is indeed effective. However, the selection of the technical, operational and management security controls offered by the NIST model - and how they are implemented - does not always fit the nature and the environment where the ground system operates in even though there is no apparent impact on mission success. The authors observed that unfit controls, that is, controls that are not necessarily applicable or sufficiently effective in protecting the mission systems, are often selected to facilitate compliance with security requirements and organizational expectations even if the selected controls offer minimum or non-existent protection. This paper identifies some of the standard security controls that can in fact protect the ground system, and which of them offer little or no benefit at all. It offers multiple scenarios from real security audits in which the controls are not effective without, of course, disclosing any sensitive information about the missions assessed. In addition to selection and implementation of controls, the paper also discusses potential impact of recent legislation such as the Federal Information Security Modernization Act (FISMA) of 2014 - aimed at the enterprise - on the ground system, and offers other recommendations to Information System Owners (ISOs).

GOVERNANCE↗
NASA NTRS2002

Latest Development in Advanced Sensors at Kennedy Space Center (KSC)

Inexpensive space transportation system must be developed in order to make spaceflight more affordable. To achieve this goal, there is a need to develop inexpensive smart sensors to allow autonomous checking of the health of the vehicle and associated ground support equipment, warn technicians or operators of an impending problem and facilitate rapid vehicle pre-launch operations. The Transducers and Data Acquisition group at Kennedy Space Center has initiated an effort to study, research, develop and prototype inexpensive smart sensors to accomplish these goals. Several technological challenges are being investigated and integrated in this project multi-discipline sensors; self-calibration, health self-diagnosis capabilities embedded in sensors; advanced data acquisition systems with failure prediction algorithms and failure correction (self-healing) capabilities.

Perotti, Jose M.↗
NASA NTRS2011

Growth of Three Lettuce Cultivars in NASA's HDU PEM During the 2010 DRATS Test

NASA's 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. Rooting media and slow release fertilizers were evaluated for three lettuce cultivars that had shown promise as candidates for a surface based food production system. These tests involved comparing growth, color and quality of the lettuce cultivars grown under VEGGIE LED array (Orbitec, Madison, WI) or Biomass Production System for Education ((BSEe), Orbitec, Madison, WI) compact fluorescent lamps using a gravity feed water delivery system. Mission relevant conditions of CO2, temperature and RH were maintained using controlled environment chambers (EGC, Chagrin Falls, OH). Growth data was obtained for the two red leaf lettuce cultivars, Outredgeous and Firecracker, and the green Bibb lettuce cultivar, Flandria. Growth and quality was evaluated using different concentrations (7.5 g/L and 15 g/L) of commercial slow release fertilizer (Osmocote Plus 15-9-12, Scotts, Maryville, OH) and Nutricote 18-6-8 (Florikan, Sarasota, FL) in either a peat/vermiculite media (sunshine LP5 MiX, Sungro, Bellview, WA) or calcined montmorillonite clay [(arcillite,)Turface Proleague, Profile LLC, Buffalo Grove, IL]. The commercial peat/vermiculite mix generally resulted in larger plants than those grown in arcillite. Increasing the concentration of Osmocote from 7.5 to 15 g/L increased the height, dry mass, and leaf area of lettuce cultivars. In contrast, there was a decrease in growth parameters when concentration of Nutricote was increased from 7.5 to 15 g/L. The best growth was obtained with the 7.5 g/L Nutricote using a commercial peat/vermiculite mixture. This media was used for field testing VEGGIE plant system in the 2010 DRAT test. 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 14-day test. 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 pressurized excursion module. Data are being used to design a plant atrium with LED lighting to evaluate salad crop growth during NASA's 2011 DRATS test.

Stutte, Gary W.↗
NASA NTRS2017

Human-Autonomy Teaming in a Flight Following Task

The NATO HFM-247 Working Group is creating a summary report of the group's activities on human-autonomy teaming. This chapter is a summary of our at NASA Ames work toward developing a framework for human-autonomy teaming (HAT) in aviation. The purpose of this project was to demonstrate and evaluate proposed tenets of HAT. The HAT features were derived from three tenets and were built into an automated recommender system on a ground station. These tenets include bi-directional communication, automation transparency, and operator directed interface. This study focused primarily on interactions with one piece of automation, the Autonomous Constrained Flight Planner (ACFP). The ACFP is designed to support rapid diversion decisions for commercial pilots in off-nominal situations. Much effort has gone into enhancing this tool not only in capability but also in transparency. In this study, participants used the ACFP at a ground station designed to aid dispatchers in a flight following role to reroute aircraft in situations such as inclement weather, system failures and medical emergencies. Participants performed this task both with HAT features enabled and without and provided feedback. We examined subjective and behavioral indicators of HAT collaborations using a proof-of-concept demonstration of HAT tenets. The data collected suggest potential advantages and disadvantages of HAT.

bi-directional communication↗
NASA NTRS1993

Space Station Freedom ground data system: Design and operations

Over the previous year the Space Station Freedom (SSF) Program (SSFP) ground data distribution system has become independent of a number of data systems that were to have been provided by other National Aeronautics and Space Administration (NASA) programs. Consequently, the SSFP has outlined the basic architecture of a new data system dedicated to supporting SSF requirements. This has been accomplished through a complete redesign of the ground network and a reallocation of selected functions. There are a number of aspects of the new ground data distribution system that are unique among NASA programs. These considerations make SSF ground data distribution one of the most extensive and complex data management challenges encountered in the arena of Space Operations. A description of this system comprises the main focus of the paper.

Dunning, Richard A., Jr.↗
NASA NTRS2010

A Near-Term Concept for Trajectory Based Operations with Air/Ground Data Link Communication

An operating concept and required system components for trajectory-based operations with air/ground data link for today's en route and transition airspace is proposed. Controllers are fully responsible for separation as they are today, and no new aircraft equipage is required. Trajectory automation computes integrated solutions to problems like metering, weather avoidance, traffic conflicts and the desire to find and fly more time/fuel efficient flight trajectories. A common ground-based system supports all levels of aircraft equipage and performance including those equipped and not equipped for data link. User interface functions for the radar controller's display make trajectory-based clearance advisories easy to visualize, modify if necessary, and implement. Laboratory simulations (without human operators) were conducted to test integrated operation of selected system components with uncertainty modeling. Results are based on 102 hours of Fort Worth Center traffic recordings involving over 37,000 individual flights. The presence of uncertainty had a marginal effect (5%) on minimum-delay conflict resolution performance, and windfavorable routes had no effect on detection and resolution metrics. Flight plan amendments and clearances were substantially reduced compared to today s operations. Top-of-descent prediction errors are the largest cause of failure indicating that better descent predictions are needed to reliably achieve fuel-efficient descent profiles in medium to heavy traffic. Improved conflict detections for climbing flights could enable substantially more continuous climbs to cruise altitude. Unlike today s Conflict Alert, tactical automation must alert when an altitude amendment is entered, but before the aircraft starts the maneuver. In every other failure case tactical automation prevented losses of separation. A real-time prototype trajectory trajectory-automation system is running now and could be made ready for operational testing at an en route Center in 1-2 years.

McNally, David↗
NASA NTRS2017

NASA's Space Launch System: Progress Report

After more than four decades exploring the space environment from low Earth orbit and developing long-duration spaceflight operational experience with the International Space Station (ISS), NASA is once again preparing to send explorers into deep space. Development, test and manufacturing is now underway on the launch vehicle, the crew spacecraft and the ground processing and launch facilities to support human and robotic missions to the moon, Mars and the outer solar system. The enabling launch vehicle for these ambitious new missions is the Space Launch System (SLS), managed by NASA's Marshall Space Flight Center (MSFC). Since the program began in 2011, the design has passed Critical Design Review, and extensive development, test and flight hardware has been produced by every major element of the SLS vehicle. Testing continues on engines, boosters, tanks and avionics. While the program has experienced engineering challenges typical of a new development, it continues to make steady progress toward the first SLS mission in roughly two years and a sustained cadence of missions thereafter. This paper will discuss these and other technical and SLS programmatic successes and challenges over the past year and provide a preview of work ahead before first flight.

Cook, Jerry↗
NASA NTRS2022

Overview of NASA’s Extensible Traffic Management (xTM) Research

NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.

air traffic management↗
NASA NTRSDate not supplied

Overview of NASA’s Extensible Traffic Management (xTM) Work

NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.

air traffic management↗
NASA NTRS1993

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↗
NASA NTRS2011

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

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

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↗