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 757 records · Page 42

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

Introduction to Space Station Freedom

NASA field centers and contractors are organized to develop 'work packages' for Space Station Freedom. Marshall Space Flight Center and Boeing are building the U.S. laboratory and habitation modules, nodes, and environmental control and life support system; Johnson Space Center and McDonnell Douglas are responsible for truss structure, data management, propulsion systems, thermal control, and communications and guidance; Lewis Research Center and Rocketdyne are developing the power system. The Canadian Space Agency (CSA) is contributing a Mobile Servicing Center, Special Dextrous Manipulator, and Mobile Servicing Center Maintenance Depot. The National Space Development Agency of Japan (NASDA) is contributing a Japanese Experiment Module (JEM), which includes a pressurized module, logistics module, and exposed experiment facility. The European Space Agency (ESA) is contributing the Columbus laboratory module. NASA ground facilities, now in various stages of development to support Space Station Freedom, include: Marshall Space Flight Center's Payload Operations Integration Center and Payload Training Complex (Alabama), Johnson Space Center's Space Station Control Center and Space Station Training Facility (Texas), Lewis Research Center's Power System Facility (Ohio), and Kennedy Space Center's Space Station Processing Facility (Florida). Budget appropriations impact the development of the Space Station. In Fiscal Year 1988, Congress appropriated only half of the funds that NASA requested for the space station program ($393 million vs. $767 million). In FY 89, NASA sought $967 million for the program, and Congress appropriated $900 million. NASA's FY 90 request was $2.05 billion compared to an appropriation of $1.75 billion; the FY 91 request was $2.45 billion, and the appropriation was $1.9 billion. After NASA restructured the Space Station Freedom program in response to directions from Congress, the agency's full budget request of $2.029 billion for Space Station Freedom in FY 92 was appropriated. For FY 93, NASA is seeking $2.25 billion for the program; the planned budget for FY 94 is $2.5 billion. Further alterations to the hardware configuration for Freedom would be a serious setback; NASA intends 'to stick with the current baseline' and continue planning for utilization.

Kohrs, Richard↗

The LANDSAT/global positioning system project

A GPSPAC/LANDSAT-D Interface (GLI) Ground Support System was built to validate the performance and to calibrate the accuracy of the experimental navigation package, GPSPAC, flown on the LANDSAT-4 and 5 spacecraft. Although the GLI system operated successfully to give the orbit information needed to validate the GPSPAC, it also detected two anomalies: one is characteristic of the GLI system and the other is characteristic of the pre-operational phase of GPS. Several methods were applied to resolve or reduce the anomalies. This paper presents a description of the problems, the methods applied to resolve or reduce them, and the results.

Wood, Terri↗

Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 1: Overview and summary

NASA's Space Station Freedom Program (SSFP) planning efforts have identified a need for a payload training simulator system to serve as both a training facility and as a demonstrator to validate operational concepts. The envisioned Marshall Space Flight Center (MSFC) Payload Training Complex (PTC) required to meet this need will train the space station payload scientists, station scientists, and ground controllers to operate the wide variety of experiments that will be onboard the Space Station Freedom. The Simulation Computer System (SCS) is the computer hardware, software, and workstations that will support the Payload Training Complex at MSFC. The purpose of this SCS study is to investigate issues related to the SCS, alternative requirements, simulator approaches, and state-of-the-art technologies to develop candidate concepts and designs. This study was performed August 1988 to October 1989. Thus, the results are based on the SSFP August 1989 baseline, i.e., pre-Langley configuration/budget review (C/BR) baseline. Some terms, e.g., combined trainer, are being redefined. An overview of the study activities and a summary of study results are given here.

Source record↗

Space Station Simulation Computer System (SCS) study for NASA/MSFC. Volume 2: Baseline architecture report

NASA's Space Station Freedom Program (SSFP) planning efforts have identified a need for a payload training simulator system to serve as both a training facility and as a demonstrator to validate operational concepts. The envisioned MSFC Payload Training Complex (PTC) required to meet this need will train the Space Station payload scientists, station scientists, and ground controllers to operate the wide variety of experiments that will be onboard the Space Station Freedom. The Simulation Computer System (SCS) is the computer hardware, software, and workstations that will support the Payload Training Complex at MSFC. The purpose of this SCS Study is to investigate issues related to the SCS, alternative requirements, simulator approaches, and state-of-the-art technologies to develop candidate concepts and designs.

Source record↗

Logistics Operations Management Center: Maintenance Support Baseline (LOMC-MSB)

The Logistics Operations Management Center Maintenance Support Baseline is defined. A historical record of systems, applied to and deleted from, designs in support of future management and/or technical analysis is provided. All Flight elements, Ground Support Equipment, Facility Systems and Equipment and Test Support Equipment for which LOMC has responsibilities at Kennedy Space Center and other locations are listed. International Space Station Alpha Program documentation is supplemented. The responsibility of the Space Station Launch Site Support Office is established.

Kurrus, R.↗

The Gateway as a Building Block for Space Exploration and Development

The Gateway, which will be a small, human-tended space station in orbit around the Moon, is an example of the building block approach to space exploration and development. The National Aeronautics and Space Administration (NASA) leads the Gateway Program and serves as the integrator of the spaceflight capabilities and contributions of U.S. commercial partners and international partners. Gateway is a cornerstone of deep space human exploration, one critical element of the strategies and architectures that will enable human exploration of the solar system. This paper will outline: 1) The concept of operations and describe how Gateway is a multipurpose space station, supporting lunar surface missions, cis-lunar research, and as a proving ground for human missions to Mars; 2) Gateway’s international partnerships as an expansion of the partnerships of the “second generation of space programmes,” namely the International Space Station (ISS); and 3) Future commercial, scientific, and technology demonstration opportunities that this infrastructure building block provides. Lastly, the strategies and architectures for future space exploration and development must include thoughtful approaches to the management and business operations of government space programs. This includes planning for limited outyear growth in budgets, partnership and acquisition strategies, pursuing public-private partnerships and the use of firm-fixed price contracts, enabling vendor-to-vendor relationships, the use of multilateral interoperability standards, and incorporating key lessons learned from prior governmental Programs. This paper will discuss the strategies and approaches undertaken when establishing the Gateway Program at the NASA Johnson Space Center in 2019 and the current operational status of this new, lean, and efficient Program.

Gateway↗

Developmental Flight Instrumentation: Review of Space Shuttle, Ares I-X, and Artemis I

Ascent vehicles in the developmental stages of the program are instrumented with Developmental Flight Instrumentation (DFI) sensors. These sensors establish a link between a vehicle and engineers on the ground to communicate conditions experienced during the ascent. These data are then compared to pre-flight predictions used in the design process. The aerodynamic, acoustic, thermal, and structural data are either telemetered to ground stations during the ascent or stored on the vehicle for post-flight recovery and archived at the Huntsville Operations Support Center (HOSC). Following NASA's Artemis I Space Launch System (SLS) launch on November 16, 2020, data from three separate programs are available at the HOSC: Space Shuttle Program (Space Transport System (STS)), Constellation Program (Ares I-X), and Artemis Program (SLS). Availability of these data presents a unique opportunity to examine DFI data from three distinct vehicles and analyze the broad impact of the DFI data on the understanding of transonic aerodynamics. Classical spectrogram and Empirical Mode Decomposition techniques were used to present data in aerodynamically analogous regions on each vehicle. On the SLS and Ares I-X, a region downstream of the Launch Abort System motors was chosen. Comparing SLS and the STS, a region downstream of booster Froward Attach Hardware was selected as analogous flow region. Some other regions of interest were also identified. Although similarities in flow features on three vehicles were identified, some challenges in the comparison were also encountered, especially due to poor temporal and spatial resolution of Shuttle measurements.

Space Shuttle↗

Developmental Flight Instrumentation: Review of Space Shuttle, Ares I-X, and Artemis I

Ascent vehicles in the developmental stages of the program are instrumented with Developmental Flight Instrumentation (DFI) sensors. These sensors establish a link between a vehicle and engineers on the ground to communicate conditions experienced during the ascent. These data are then compared to pre-flight predictions used in the design process. The aerodynamic, acoustic, thermal, and structural data are either telemetered to ground stations during the ascent or stored on the vehicle for post-flight recovery and archived at the Huntsville Operations Support Center (HOSC). Following NASA's Artemis I Space Launch System (SLS) launch on November 16, 2020, data from three separate programs are available at the HOSC: Space Shuttle Program (Space Transport System (STS)), Constellation Program (Ares I-X), and Artemis Program (SLS). Availability of these data presents a unique opportunity to examine DFI data from three distinct vehicles and analyze the broad impact of the DFI data on the understanding of transonic aerodynamics. Classical spectrogram and Empirical Mode Decomposition techniques were used to present data in aerodynamically analogous regions on each vehicle. On the SLS and Ares I-X, a region downstream of the Launch Abort System motors was chosen. Comparing SLS and the STS, a region downstream of booster Froward Attach Hardware was selected as analogous flow region. Some other regions of interest were also identified. Although similarities in flow features on three vehicles were identified, some challenges in the comparison were also encountered, especially due to poor temporal and spatial resolution of Shuttle measurements.

Space Shuttle↗

Enabling a Larger Deep Space Mission Suite: A Deep Space Network Queuing Antenna for Demand Access

The advent of deep space small spacecraft, as exemplified by the Mars Cubesat One (MarCO), Lunar Trailblazer, Janus, the Escape and Plasma Acceleration and Dynamics Explorers (EscaPADE), and the thirteen Artemis 1 missions, opens the possibility that a much larger number of deep space spacecraft may be launched over the next 10 years and beyond. While scientifically exciting, the prospect of a (much) larger mission suite raises significant challenges for the current approach to ground stations and mission operations. We have been investigating an integrated approach for ground stations and missions operations to enable new modes of operation while maintaining the capabilities of the current operational techniques. This integrated approach is built around three core capabilities: (1) A queuing antenna that enables monitoring the status of a much larger number of spacecraft, and allows spacecraft to transmit requests for telemetry with NASA’s Deep Space Network (DSN); (2) a flexible scheduling system that expands the current DSN scheduling services to enable allocating time on DSN antennas in near real-time; and (3) a cloud-based ground data system that can be spun up and down according to how tracks are assigned by the flexible scheduling system. We shall show that an 18 meter DSN queuing antenna equipped with cyrogenic receivers would enable use of the DSN Demand Access Service for small spacecraft throughout the inner Solar System, thus providing service to a large mission suite. We first discuss the architecture of the queuing antenna and its supporting systems, including, for instance, the service required to generate the schedule for the queueing antenna (which dictates how it slews to monitor multiple spacecraft in a day of operations). Next, we describe the signaling scheme used to encode a request, which is inherited from the already operational DSN Beacon Tone Service, and describe two alternative ways to detect the incoming tone at the ground station, one based on maximum likelihood estimation (MLE), and another one based on Fast-Fourier Transfer (FFT) processing. We then use these results to estimate the maximum range at which a request can be reliably detected as a function of the spacecraft and ground station communication capabilities. Finally, the last part of this part of this paper briefly describes the prototyping effort undertaken at Morehead State University (MSU) and JPL to demonstrate the viability of this new DSN demand access. In particular, we describe the suite of tests conducted using MSU’s 21 meter ground station to validate its use a queuing antenna.

Mattle, Emily↗

Charter for Systems Engineer Working Group

This charter establishes the International Space Station Program (ISSP) Mobile Servicing System (MSS) Systems Engineering Working Group (SEWG). The MSS SEWG is established to provide a mechanism for Systems Engineering for the end-to-end MSS function. The MSS end-to-end function includes the Space Station Remote Manipulator System (SSRMS), the Mobile Remote Servicer (MRS) Base System (MBS), Robotic Work Station (RWS), Special Purpose Dexterous Manipulator (SPDM), Video Signal Converters (VSC), and Operations Control Software (OCS), the Mobile Transporter (MT), and by interfaces between and among these elements, and United States On-Orbit Segment (USOS) distributed systems, and other International Space Station Elements and Payloads, (including the Power Data Grapple Fixtures (PDGFs), MSS Capture Attach System (MCAS) and the Mobile Transporter Capture Latch (MTCL)). This end-to-end function will be supported by the ISS and MSS ground segment facilities. This charter defines the scope and limits of the program authority and document control that is delegated to the SEWG and it also identifies the panel core membership and specific operating policies.

Suffredini, Michael T.↗

A Sounding-based Severe Weather Tool to Support Daily Operations at Kennedy Space Center and Cape Canaveral Air Force Station

People and property at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) are at risk when severe weather occurs. Strong winds, hail and tornadoes can injure individuals and cause costly damage to structures if not properly protected. NASA's Launch Services Program and Ground Systems Development and Operations Program and other KSC programs use the daily and weekly severe weather forecasts issued by the 45th Weather Squadron (45 WS) to determine if they need to limit an activity such as working on gantries, or protect property such as a vehicle on a pad. The 45 WS requested the Applied Meteorology Unit (AMU) develop a warm season (May-September) severe weather tool for use in the Meteorological Interactive Data Display System (MIDDS) based on the late morning, 1500 UTC (1100 local time), CCAFS (XMR) sounding. The 45 WS frequently makes decisions to issue a severe weather watch and other severe weather warning support products to NASA and the 45th Space Wing in the late morning, after the 1500 UTC sounding. The results of this work indicate that certain stability indices based on the late morning XMR soundings can depict differences between days with reported severe weather and days with no reported severe weather. The AMU determined a frequency of reported severe weather for the stability indices and implemented an operational tool in MIDDS.

Hail↗

The NASA Mission Operations and Control Architecture Program

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Ondrus, Paul J.↗

An Ejectable Data Recorder Subsystem for the Ascent Abort-2 Test Flight of the Orion Launch Abort System

The Ejectable Data Record (EDR) subsystem was a unique development opportunity at NASA with challenges that necessitated innovation. EDR employed a “skunkworks” development approach in which we designed, built, and delivered 47 end items, not including ground support equipment. We used as many COTS components as possible, we looked for process efficiencies to meet our tight deadlines, and the EDR team was involved in the flight operations of the AA-2 test flight and responsible for the recovery operations of the ejected payloads. This paper will discuss the design and development of the EDR subsystem, as well as the results of the system performance during the AA-2 test flight.

Rojdev, Kristina↗

Citric Acid Alternative to Nitric Acid Passivation

The Ground Systems Development and Operations GSDO) Program at NASA John F. Kennedy Space Center (KSC) has the primary objective of modernizing and transforming the launch and range complex at KSC to benefit current and future NASA programs along with other emerging users. Described as the launch support and infrastructure modernization program in the NASA Authorization Act of 2010, the GSDO Program will develop and implement shared infrastructure and process improvements to provide more flexible, affordable, and responsive capabilities to a multi-user community. In support of the GSDO Program, the purpose of this project is to demonstratevalidate citric acid as a passivation agent for stainless steel. Successful completion of this project will result in citric acid being qualified for use as an environmentally preferable alternative to nitric acid for passivation of stainless steel alloys in NASA and DoD applications.

Technology↗

Integration Test and Evaluation (IT&E) Flight Test Series 6 Live Virtual Constructive - Distributed Environment (LVC-DE) Test Report

The goals of the Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) (also UAS-NAS) Project are to reduce the barriers for UAS access and its integration into the NAS. The UAS-NAS project and industry stakeholders conducted a series of flight tests integrating technologies from the Modeling & Simulation (M&S), Human Systems Integration (HSI), and Communication and Control (C2), and Integration, Test & Evaluation (IT&E) research areas. The last of the flight test series, Flight Test Series 6 (FT6) was conducted in late 2019 and focused on evaluating the interaction of the airborne non-cooperative surveillance system and the Detect and Avoid (DAA) technology. The DAA system generated conflict alert and guidance for pilots using a Research Ground Control System (RGCS) to avoid intruder aircraft. The conflict alerting and guidance information was presented on the RGCS’s display using symbology developed by the human factors team. The objective of FT6 was to investigate the interoperability of Low Size, Weight, and Power (Low SWaP) sensors with the DAA alerting, guidance, and display requirements. To support this goal, the distributed test environments (DTE) were developed at Ames Research Center (ARC) and Armstrong Flight Research Center (AFRC) and securely linked over a Virtual Private Network (VPN). These environments took advantage of existing Live Virtual Constructive (LVC) technologies to support research observation at both Centers with the insertion of live UAS and manned intruder aircraft into a simulated NAS environment with Air Traffic Control (ATC) and constructive manned aircraft. The experiment was distributed between AFRC flight operations and research facilities and the Distributed Simulation Research Laboratory (DSRL) and Software Development Laboratory (SDL) in building N243 at ARC. The Air Traffic Controller and pseudo pilots operated from the DSRL and SDL, respectively, using the Multi-Aircraft Control System (MACS). The test subject and researchers operated from the Research Ground Control Station (RGCS) at AFRC using the Vigilant Spirit Control Station (VSCS) and associated DAA software and displays. Flight Operation for the unmanned aircraft (UA) and manned intruder traffic was conducted at AFRC. Virtual traffic was managed by ARC. Voice distribution was accomplished using a combination of disparate communication systems at ARC and AFRC. The purpose of this document is to record the development, design, and execution of activities in support of the FT6 efforts from the perspective of the ARC IT&E team. Furthermore, the Armstrong IT&E team has published a thorough FT6 Test Report, with emphasis on flight test support, facilities and vehicle development; this report complements the Armstrong report. Analysis of collected FT6 data will be conducted and reported by the M&S and HSI teams and will be published in separate reports.

UAS-NAS↗

NASA Langley's AirSTAR Testbed: A Subscale Flight Test Capability for Flight Dynamics and Control System Experiments

As part of the Airborne Subscale Transport Aircraft Research (AirSTAR) project, NASA Langley Research Center (LaRC) has developed a subscaled flying testbed in order to conduct research experiments in support of the goals of NASA s Aviation Safety Program. This research capability consists of three distinct components. The first of these is the research aircraft, of which there are several in the AirSTAR stable. These aircraft range from a dynamically-scaled, twin turbine vehicle to a propeller driven, off-the-shelf airframe. Each of these airframes carves out its own niche in the research test program. All of the airplanes have sophisticated on-board data acquisition and actuation systems, recording, telemetering, processing, and/or receiving data from research control systems. The second piece of the testbed is the ground facilities, which encompass the hardware and software infrastructure necessary to provide comprehensive support services for conducting flight research using the subscale aircraft, including: subsystem development, integrated testing, remote piloting of the subscale aircraft, telemetry processing, experimental flight control law implementation and evaluation, flight simulation, data recording/archiving, and communications. The ground facilities are comprised of two major components: (1) The Base Research Station (BRS), a LaRC laboratory facility for system development, testing and data analysis, and (2) The Mobile Operations Station (MOS), a self-contained, motorized vehicle serving as a mobile research command/operations center, functionally equivalent to the BRS, capable of deployment to remote sites for supporting flight tests. The third piece of the testbed is the test facility itself. Research flights carried out by the AirSTAR team are conducted at NASA Wallops Flight Facility (WFF) on the Eastern Shore of Virginia. The UAV Island runway is a 50 x 1500 paved runway that lies within restricted airspace at Wallops Flight Facility. The facility provides all the necessary infrastructure to conduct the research flights in a safe and efficient manner. This paper gives a comprehensive overview of the development of the AirSTAR testbed.

Jordan, Thomas L.↗

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↗