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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 667 records · Page 37

All sources NASA NTRS DOE OSTI

NASA NTRS1987

NASA Marshall Space Flight Center atomic oxygen investigations

An overview of the MSFC atomic oxygen investigations is provided, including descriptions of flight studies, ground-based testing, contractual efforts, and future focus. Summary results of flight experiments on STS-5, STS-8, and STS 41-G are presented. The development of the MSFC Atomic Oxygen Resistive Monitor for the upcoming EOIM-3 (Evaluation of Oxygen Interaction with Materials 3) flight experiment is reviewed. Materials characterization work and ground-based testing are described. Contractual efforts, such as the development of atomic oxygen resistant coatings for the space station, are discussed. Future emphasis is placed on ground-based testing via the development and operation of a state-of-the-art atomic oxygen simulation system and on the continuation of flight studies in support of multi-programs.

Source record↗

NASA NTRS1988

Research and development for Onboard Navigation (ONAV) ground based expert/trainer system: Preliminary user's guide

The purpose is to present procedures for preparation, operation, monitoring, and recovery of the Shuttle Entry phase expert system that is part of the Onboard Navigation (ONAV) Ground Based Expert System Trainer System for aircraft/space shuttle navigation. This user's guide is primarily intended for functional users of the system. It includes procedures for system operation in support of training activities as well as operational tasks. In addition, information is provided which enables maintenance personnel to handle updates, modifications, etc. to the system.

Bochsler, Daniel C.↗

NASA NTRS1991

Space station control center architecture

The Space Station control center (SSCC) is under the cognizance of the Johnson Space Center and is located adjacent to the Shuttle's mission control center. Responsibility for design, development, and operations of the control center is the responsibility of the mission operations directorate at JSC. Space Station Ground Systems Division is responsible for design and development of the control center systems which is currently in process under the mission support contractor team led by Loral Space Information Systems. It is early in the life cycle of the SSCC project. System functional design review was completed. Subsystem requirements are now being developed and reviewed. A new facility will be available for development activities.

Schmalz, Karen↗

NASA NTRS1994

Efficient mission control for the 48-satellite Globalstar Constellation

The Globalstar system is being developed by Globalstar, Limited Partnership and will utilize 48 satellites in low earth orbit (See Figure 1) to create a world-wide mobile communications system consistent with Vice President Gore's vision of a Global Information Infrastructure. As a large long term commercial system developed by a newly formed organization, Globalstar provides an excellent opportunity to explore innovative solutions for highly efficient satellite command and control. Design and operational concepts being developed are unencumbered by existing physical and organizational infrastructures. This program really is 'starting with a clean sheet of paper'. Globalstar operations challenges can appear enormous. Clearly, assigning even a single person around the clock to monitor and control each satellite is excessive for Globalstar (it would require a staff of 200! . Even with only a single contact per orbit per satellite, data acquisitions will start or stop every 45 seconds! Although essentially identical, over time the satellites will develop their own 'personalities'and will re quire different data calibrations and levels of support. This paper discusses the Globalstar system and challenges and presents engineering concepts, system design decisions, and operations concepts which address the combined needs and concerns of satellite, ground system, and operations teams. Lessons from past missions have been applied, organizational barriers broken, partnerships formed across the mission segments, and new operations concepts developed for satellite constellation management. Control center requirements were then developed from the operations concepts.

Smith, Dan↗

NASA NTRS2003

Case for Deploying Complex Systems Utilizing Commodity Components

This viewgraph representation presents a study of the transition of computer networks and software engineering at the Huntsville Operations Support Center (HOSC) from a client/server UNIX based system to a client/server system based on commodity priced and open system components. Topics covered include: an overview of HOSC ground support systems, an analysis for changes to the existing ground support system, an analysis of options considered for the transition to a new system, and a consideration of goals for a new system.

Bryant, Barry S.↗

NASA NTRS2015

Customer Avionics Interface Development and Analysis (CAIDA) Lab DEWESoft Display Creation

The Customer Avionics Interface Development and Analysis (CAIDA) Lab supports the testing of the Launch Control System (LCS), NASA's command and control system for the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and ground support equipment. The objectives of the year-long internship were to support day-to-day operations of the CAIDA Lab, create prelaunch and tracking displays for Orion's Exploration Flight Test 1 (EFT-1), and create a program to automate the creation of displays for SLS and MPCV to be used by CAIDA and the Record and Playback Subsystem (RPS).

DEWESoft↗

NASA NTRS2018

Customer Avionics Interface Development and Analysis (CAIDA): Software Developer for Avionics Systems

The Customer Avionics Interface Development and Analysis (CAIDA) supports the testing of the Launch Control System (LCS), NASA's command and control system for the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and ground support equipment. The objective of the semester-long internship was to support day-to-day operations of CAIDA and help prepare for verification and validation of CAIDA software.

Mitchell, Sherry L.↗

NASA NTRSDate not supplied

Overview of Crew Operations for Transit to Mars

Crewed Mars missions are estimated to be 700-1,200 days in length which is two to three times longer than any continuous human spaceflight mission to date. When architecting a Mars mission there are numerous resources that must be considered, evaluated, and planned for, including—but not limited to—mass, cost, performance, and risk. Crew time is a limited resource that will need to be appropriately allocated during future Mars missions. NASA’s “Moon to Mars Objectives” specifically recognizes as Recurring Tenets the need to return crews safely to Earth while mitigating adverse impacts to crew health and maximizing crew time available for science and engineering activities within planned mission durations. Crew operations and the crew time allocation for a Mars missions will likely be different than current operational planning aboard the ISS due to communication delays, crew health and performance needs, transportation system needs, potential vehicle dormancy, and mass ejection. Crew will need to operate much more Earth independently and potentially be responsible for more operations since traditional Earth ground support will be delayed. Incidents requiring immediate crew action will therefore either be the responsibility of the crew or an automated feature of the transit vehicle. This paper discusses the operational challenges of a Mars transit mission and the associated activities that will need to take place during each operational phase of transit to and from Mars.

Crew Time↗

NASA NTRSDate not supplied

Overview of Crew Operations for Transit to Mars

Crew Time↗

NASA NTRS2017

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current International Space Station (ISS) medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable an increasingly autonomous crew than the current ISS paradigm. The MDA will develop capabilities that support automated data collection, and the necessary functionality and challenges in executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. To attain this goal, the first year of the MDA project focused on reducing technical risk, developing documentation and instituting iterative development processes that established the basis for the first version of MDA software (or Test Bed 1). Test Bed 1 is based on a nominal operations scenario authored by the ExMC Element Scientist. This narrative was decomposed into a Concept of Operations that formed the basis for Test Bed 1 requirements. These requirements were successfully vetted through the MDA Test Bed 1 System Requirements Review, which permitted the MDA project to begin software code development and component integration. This paper highlights the MDA objectives, development processes, and accomplishments, and identifies the fiscal year 2017 milestones and deliverables in the upcoming year.

Data management↗

NASA NTRS2011

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗

NASA NTRS1973

Some considerations for Space Tug launch site support operations.

The study reported was undertaken to investigate the requirements placed on the Space Tug by the ground operations. On the basis of the results obtained, it will be possible to consider in future Tug systems studies the full spectrum of both ground and flight operations requirements in defining selected Tug configurations. The central core of the study consists of a functional analysis of ground operations during the Tug turnaround. Electronic system studies were initiated concurrently with the functional analysis study phase to evaluate interrelationships between ground and vehicle checkout and fault isolation capability.

Heald, D. A.↗

NASA NTRS2008

Impact of Pilot Delay and Non-Responsiveness on the Safety Performance of Airborne Separation

Assessing the safety effects of prediction errors and uncertainty on automationsupported functions in the Next Generation Air Transportation System concept of operations is of foremost importance, particularly safety critical functions such as separation that involve human decision-making. Both ground-based and airborne, the automation of separation functions must be designed to account for, and mitigate the impact of, information uncertainty and varying human response. This paper describes an experiment that addresses the potential impact of operator delay when interacting with separation support systems. In this study, we evaluated an airborne separation capability operated by a simulated pilot. The experimental runs are part of the Safety Performance of Airborne Separation (SPAS) experiment suite that examines the safety implications of prediction errors and system uncertainties on airborne separation assistance systems. Pilot actions required by the airborne separation automation to resolve traffic conflicts were delayed within a wide range, varying from five to 240 seconds while a percentage of randomly selected pilots were programmed to completely miss the conflict alerts and therefore take no action. Results indicate that the strategicAirborne Separation Assistance System (ASAS) functions exercised in the experiment can sustain pilot response delays of up to 90 seconds and more, depending on the traffic density. However, when pilots or operators fail to respond to conflict alerts the safety effects are substantial, particularly at higher traffic densities.

Consiglio, Maria↗

NASA NTRS1989

Space station Simulation Computer System (SCS) study for NASA/MSFC. Volume 4: Conceptual design report

The Simulation Computer System (SCS) is the computer hardware, software, and workstations that will support the Payload Training Complex (PTC) at Marshall Space Flight Center (MSFC). The PTC 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. In the first step of this task, a methodology was developed to ensure that all relevant design dimensions were addressed, and that all feasible designs could be considered. The development effort yielded the following method for generating and comparing designs in task 4: (1) Extract SCS system requirements (functions) from the system specification; (2) Develop design evaluation criteria; (3) Identify system architectural dimensions relevant to SCS system designs; (4) Develop conceptual designs based on the system requirements and architectural dimensions identified in step 1 and step 3 above; (5) Evaluate the designs with respect to the design evaluation criteria developed in step 2 above. The results of the method detailed in the above 5 steps are discussed. The results of the task 4 work provide the set of designs which two or three candidate designs are to be selected by MSFC as input to task 5-refine SCS conceptual designs. The designs selected for refinement will be developed to a lower level of detail, and further analyses will be done to begin to determine the size and speed of the components required to implement these designs.

Source record↗

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↗