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 271 records · Page 15

All sources NASA NTRS DOE OSTI

NASA NTRS1993

Using Task Analysis to Understand the Data System Operations Team

The Data System Operations Team (DSOT) currently monitors and controls the Multimission Ground Data System (MGDS) at NASA's Jet Propulsion Laboratory. The MGDS currently supports five spacecraft and within the next five years it will support ten spacecraft simultaneously. The ground processing element of the MGDS consists of a distributed UNIX-based system of over 40 nodes and 100 processes. The MGDS system provides operators with little or no information about the system's end-to-end processing status or end-to-end configuration. The lack of system visibility has become a critical issue in the daily operation of the MGDS. A task analysis was conducted to determine what kinds of tools were needed to provide DSOT with useful status information and to prioritize the tool development...

Holder, Barbara E.↗

NASA NTRS2016

A Day in the Life of the Laser Communications Relay Demonstration (LCRD) Project.

This presentation provides an overview of the planned concept of operations for the Laser Communications Relay Demonstration Project (LCRD), a joint project among NASA's Goddard Space Flight Center (GSFC), the Jet Propulsion Laboratory, California Institute of Technology (JPL), and the Massachusetts Institute of Technology Lincoln Laboratory (MITLL). LCRD will provide at least two years of bi-directional optical communications at user data rates of up to 1.244 Gbps in an operational environment. The project lays the ground work for establishing communications architecture and protocols, and developing the communications hardware and support infrastructure, concluding in a demonstration of optical communications potential to meet NASAs growing need for higher data rates for future science and exploration missions. A pair of flight optical communications terminals will reside on a single commercial communications satellite in geostationary orbit; the two ground optical communications terminals will be located in Southern California and Hawaii. This paper summarizes the current LCRD architecture and key systems for the demonstration, focusing on what it will take to operate an optical communications relay that can support space-to-space, space-to-air, and space-to-ground optical links.

Optical↗

NASA NTRS1993

EOS ground data systems: A description and interface overview

The Earth Observing System (EOS) is planned as a space-based measurement system, earth-science research program, and data and information system (EOSDIS). It will consist of several high data rate spacecraft with multiple earth sensing instruments which provide investigators with a thorough, longterm view of the earth's environment. Up to seven spacecraft may be supported at once, either in operational, checkout, or testing phases; and the average data rate from the EOS satellites in orbit at any one time is expected to be from 18 to 60 Mbps. Providing the data processing and flight operations support for EOS will be the EOSDIS Core System (ECS). The ECS will command and control the spacecraft; process and store the EOS data; provide access to the data for years; and support researchers. The data processing aspects of the ECS consist of a collection of Distributed Active Archive Centers (DAAC's) which perform the product generation, data archive and distribution, and information management services. Flight operations aspects will be provided by the EOS Operations Center, by instrument control centers, and by widely distributed instrument support terminals. The communications and system management aspects will be provided by the EOSDIS Science Network and the System Management Center. In addition to the EOS satellite data, other data sets from earlier earth science missions are also to be added to designated DAAC's. Other ground data systems which will provide support to EOS for acquiring, transporting, processing, and distributing the transformed spacecraft data are currently being defined or are being upgraded for the EOS era. These systems include the Space Network consisting of the Tracking and Data Relay Satellite System (TDRSS), the TDRSS Ground Terminals, and the Network Control Center as well as the night Dynamics Facility, the EOS Data and Operations System, and EOS Communications. This paper briefly describes data handling by the ECS, the support data systems, their interfaces, and their roles.

Smith, Gene↗

NASA NTRS2006

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

This paper details an architectural description of the Mission Data Processing and Control System (MPCS), an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is developed based on a set of small reusable components, implemented in Java, each designed with a specific function and well-defined interfaces. An industry standard messaging bus is used to transfer information among system components. Components generate standard messages which are used to capture system information, as well as triggers to support the event-driven architecture of the system. Event-driven systems are highly desirable for processing high-rate telemetry (science and engineering) data, and for supporting automation for many mission operations processes.

Mission Data Processing and Control System (MPCS)↗

NASA NTRS2005

Support for User Interfaces for Distributed Systems

An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.

Eychaner, Glenn↗

NASA NTRS1992

The Telecommunications and Data Acquisition Report

Archival reports on developments in programs managed by JPL's Office of Telecommunications and Data Acquisition (TDA) are provided. In space communications, radio navigation, radio science, and ground-based radio and radar astronomy, it reports on activities of the Deep Space Network (DSN) in planning, in supporting research and technology, in implementation, and in operations. Also included is standards activity at JPL for space data and information. In the search for extraterrestrial intelligence (SETI), the TDA Progress Report reports on implementation and operations for searching the microwave spectrum. Topics covered include tracking and ground-based navigation; communications, spacecraft-ground; station control and system technology; capabilities for new projects; network upgrade and sustaining; network operations and operations support; and TDA program management and analysis.

Posner, E. C.↗

NASA NTRS2004

CCSDS Spacecraft Monitor and Control Service Framework

This CCSDS paper presents a reference architecture and service framework for spacecraft monitoring and control. It has been prepared by the Spacecraft Monitoring and Control working group of the CCSDS Mission Operations and Information Management Systems (MOIMS) area. In this context, Spacecraft Monitoring and Control (SM&C) refers to end-to-end services between on- board or remote applications and ground-based functions responsible for mission operations. The scope of SM&C includes: 1) Operational Concept: definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of both ground and space segments. 2) Core Set of Services: definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Archiving and Retrieval, Flight Dynamics, Mission Planning and Performance Evaluation. 3) Application-layer information: definition of the standard information set to be exchanged for SM&C purposes.

Merri, Mario↗

NASA NTRS2006

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

This viewgraph presentation reviews the architectural description of the Mission Data Processing and Control System (MPCS). MPCS is an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is designed with these factors (1) Enabling plug and play architecture (2) MPCS has strong inheritance from GDS components that have been developed for other Flight Projects (MER, MRO, DAWN, MSAP), and are currently being used in operations and ATLO, and (3) MPCS components are Java-based, platform independent, and are designed to consume and produce XML-formatted data

Mission Data Processing and Control System (MPCS)↗

NASA NTRS2013

Master Console System Monitoring and Control Development

The Master Console internship during the spring of 2013 involved the development of firing room displays at the John F. Kennedy Space Center (KSC). This position was with the Master Console Product Group (MCPG) on the Launch Control System (LCS) project. This project is responsible for the System Monitoring and Control (SMC) and Record and Retrieval (R&R) of launch operations data. The Master Console is responsible for: loading the correct software into each of the remaining consoles in the firing room, connecting the proper data paths to and from the launch vehicle and all ground support equipment, and initializing the entire firing room system to begin processing. During my internship, I developed a system health and status display for use by Master Console Operators (MCO) to monitor and verify the integrity of the servers, gateways, network switches, and firewalls used in the firing room.

Brooks, Russell A.↗

NASA NTRS1975

Space Tug avionics definition study. Volume 2: Avionics functional requirements

Flight and ground operational phases of the tug/shuttle system are analyzed to determine the general avionics support functions that are needed during each of the mission phases and sub-phases. Each of these general support functions is then expanded into specific avionics system requirements, which are then allocated to the appropriate avionics subsystems. This process is then repeated at the next lower level of detail where these subsystem requirements are allocated to each of the major components that comprise a subsystem.

Source record↗

NASA NTRS1994

Intelligent vehicle control: Opportunities for terrestrial-space system integration

For 11 years the Department of Defense has cooperated with a diverse array of other Federal agencies including the National Institute of Standards and Technology, the Jet Propulsion Laboratory, and the Department of Energy, to develop robotics technology for unmanned ground systems. These activities have addressed control system architectures supporting sharing of tasks between the system operator and various automated subsystems, man-machine interfaces to intelligent vehicles systems, video compression supporting vehicle driving in low data rate digital communication environments, multiple simultaneous vehicle control by a single operator, path planning and retrace, and automated obstacle detection and avoidance subsystem. Performance metrics and test facilities for robotic vehicles were developed permitting objective performance assessment of a variety of operator-automated vehicle control regimes. Progress in these areas will be described in the context of robotic vehicle testbeds specifically developed for automated vehicle research. These initiatives, particularly as regards the data compression, task sharing, and automated mobility topics, also have relevance in the space environment. The intersection of technology development interests between these two communities will be discussed in this paper.

Shoemaker, Charles↗

NASA NTRS1992

Architecture for Survivable Systems Processing (ASSP). Technology benefits for Open System Interconnects

The Architecture for Survivable Systems Processing (ASSP) program is a two phase program whose objective is the derivation, specification, development and validation of an open system architecture capable of supporting advanced processing needs of space, ground, and launch vehicle operations. The output of the first phase is a set of hardware and software standards and specifications defining this architecture at three levels. The second phase will validate these standards and develop the technology necessary to achieve strategic hardness, packaging density, throughput requirements, and interoperability/interchangeability.

Wood, Richard J.↗

NASA NTRS1994

Using virtual reality for science mission planning: A Mars Pathfinder case

NASA's Mars Pathfinder Project requires a Ground Data System (GDS) that supports both engineering and scientific payloads with reduced mission operations staffing, and short planning schedules. Also, successful surface operation of the lander camera requires efficient mission planning and accurate pointing of the camera. To meet these challenges, a new software strategy that integrates virtual reality technology with existing navigational ancillary information and image processing capabilities. The result is an interactive workstation based applications software that provides a high resolution, 3-dimensial, stereo display of Mars as if it were viewed through the lander camera. The design, implementation strategy and parametric specification phases for the development of this software were completed, and the prototype tested. When completed, the software will allow scientists and mission planners to access simulated and actual scenes of Mars' surface. The perspective from the lander camera will enable scientists to plan activities more accurately and completely. The application will also support the sequence and command generation process and will allow testing and verification of camera pointing commands via simulation.

Kim, Jacqueline H.↗

NASA NTRS1994

Max 1991 and beyond

Max '91, a coordinated, broad based observational program, was designed to help maximize the scientific return of solar activity studies. Max '91 benefited from the support of the NOAA space environment laboratory. An important source that increases solar ground based support observations is the solar observing optical network (SOON) solar patrol on tape (SOONSPOT) solar image archival system which has started operations. The past means and the future plans for ground based coordination and communications of Max '91 are summarized. The current status and the future developments of SOONSPOT are presented.

Kiplinger, Alan L.↗

NASA NTRS1993

Mars Observer Orbit Insertion Briefing

Steve Wall is the host of this video entitled, "Return to the Red Planet". Live animation of the Mars Observer orbiting Mars is presented. Steve Wall explains the spacecraft insertion maneuver and also explains the purpose for the Mars Observer launch. Live coverage of the Cape Canaveral launch of the Mars Observer is also presented. Suzanne Dodd, Chief of the Mission Planning team describes the burn start and how the spacecraft will be captured by Mars' gravity. Glenn Cunningham, Mars Observer Project Manager, gives background information on the Mars Observer and describes the organizations behind the Mars Observer Spacecraft, such as the Deep Space Network, the Mission Operation Support Office, Science Investigators, the Flight Engineering Office, Operations Office, and the Ground Data System Office. Dr. William Piotrowski, Acting Director, Solar System Exploration Division, NASA, talks about the purpose of the Mars Pathfinder which is to develop the technology and systems for landing small science packages on Mars. Mr. Roger Gibbs, Former Mars Observer Spacecraft Systems Engineer, tells us how the Mars Observer was built and describes the structural elements on the Mars Observer. The 11-month cruise period for the spacecraft is given by Joseph Beerer, Manager of the Engineering office. The thrust for the Mars Orbit Insertion is described by Ronald Klemetson, Technical Manager, Propulsion Subsystem Jet Propulsion Laboratory (JPL). George Chen, Lead Engineer Attitude and Articulation Subsystem Spacecraft Team, explains the importance of the attitude control engines on the Spacecraft. Marvin Traxler, Manager of Tracking and Data Acquisition, describes how searching for a signal from the Mars Observer works. See NONP-NASA-VT-2000081555 for a continuation of this discussion with Marvin Traxler.

Source record↗

NASA NTRS2008

NASA's Cryogenic Fluid Management Technology Project

The Cryogenic Fluid Management (CFM) Project's primary objective is to develop storage, transfer, and handling technologies for cryogens that will support the enabling of high performance cryogenic propulsion systems, lunar surface systems and economical ground operations. Such technologies can significantly reduce propellant launch mass and required on-orbit margins, reduce or even eliminate propellant tank fluid boil-off losses for long term missions, and simplify vehicle operations. This paper will present the status of the specific technologies that the CFM Project is developing. The two main areas of concentration are analysis models development and CFM hardware development. The project develops analysis tools and models based on thermodynamics, hydrodynamics, and existing flight/test data. These tools assist in the development of pressure/thermal control devices (such as the Thermodynamic Vent System (TVS), and Multi-layer insulation); with the ultimate goal being to develop a mature set of tools and models that can characterize the performance of the pressure/thermal control devices incorporated in the design of an entire CFM system with minimal cryogen loss. The project does hardware development and testing to verify our understanding of the physical principles involved, and to validate the performance of CFM components, subsystems and systems. This database provides information to anchor our analytical models. This paper describes some of the current activities of the NASA's Cryogenic Fluid Management Project.

Tramel, Terri L.↗

NASA NTRS2014

AGSM Intelligent Devices/Smart Sensors Project

This project provides development and qualification of Smart Sensors capable of self-diagnosis and assessment of their capability/readiness to support operations. These sensors will provide pressure and temperature measurements to use in ground systems.

Technology Portfolio System↗

NASA NTRS1994

Taking advantage of ground data systems attributes to achieve quality results in testing software

During the software development life cycle process, basic testing starts with the development team. At the end of the development process, an acceptance test is performed for the user to ensure that the deliverable is acceptable. Ideally, the delivery is an operational product with zero defects. However, the goal of zero defects is normally not achieved but is successful to various degrees. With the emphasis on building low cost ground support systems while maintaining a quality product, a key element in the test process is simulator capability. This paper reviews the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) test tool that is used in the acceptance test process for unmanned satellite operations control centers. The TASS is designed to support the development, test and operational environments of the Goddard Space Flight Center (GSFC) operations control centers. The TASS uses the same basic architecture as the operations control center. This architecture is characterized by its use of distributed processing, industry standards, commercial off-the-shelf (COTS) hardware and software components, and reusable software. The TASS uses much of the same TPOCC architecture and reusable software that the operations control center developer uses. The TASS also makes use of reusable simulator software in the mission specific versions of the TASS. Very little new software needs to be developed, mainly mission specific telemetry communication and command processing software. By taking advantage of the ground data system attributes, successful software reuse for operational systems provides the opportunity to extend the reuse concept into the test area. Consistency in test approach is a major step in achieving quality results.

Sigman, Clayton B.↗