Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “ground data 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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components.

guidelines↗
NASA NTRS1994

Customizing the JPL Multimission Ground Data System: Lessons Learned

This paper will describe lessons learned in adapting JPL's Multimission Ground Data System (MGDS) to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team with a handful of engineers flying the Galileo Spacecraft flight system model.

ground↗
NASA NTRS2008

Moving Away from Ones and Zeros, Designing a Ground Data System Based on Higher Levels of Abstraction

Previous JPL ground systems have been designed with the Ground Data System (GDS) engineer in mind. The focus on these systems has been on packaging and delivery of low level information (frames, packets, telemetry values) to the end user. It was not that long ago when project teams would be huddled over a workstation, examining crude displays of telemetry bits organized in various ways, trying to determine the status of a spacecraft. Understanding the data often required additional levels of GDS expertise, or worse, transformation of the raw data into alternative formats followed by ingestion into other tools so that the data became meaningful. The primary focus was often to answer these types of questions: "Why did this particular frame fail Reed-Solomon decode? Why did this packet get marked as invalid? Why am I missing a block of telemetry from my query?" -- which are completely valid questions to ask from a GDS Engineer's point of view, and large families of tools have been designed to help answer these questions. But these are not the questions that most users care about - which are more like: "Why is the battery state of charge trending down? Show me a summary image report for the last traverse to the target. Show me a data accountability summary for the last DSN pass." Answers to these questions, which are what users are looking for, requires a higher level of abstraction and supporting tools than mining through ones and zeros. JPL has created a next generation capability called the Mission Data Processing and Control System (MPCS) which is designed to support this higher level of abstraction by providing customizable views of the ground system combining collections of lower level information into more meaningful ways. Instead of examining frames, packets, and individual telemetry data points -- MPCS is capable of providing comprehensive summary reports, product status, overall flight/ground event status, as well as payload health summaries. Based on these higher level views, end users can make tactical or strategic decisions, or drop into detailed analysis as needed. System designers need to continue building systems that support low level GDS troubleshooting - but the basic design of a GDS should be geared towards what end users actually need to see. This paper will describe the capabilities of MPCS that directly support these higher levels of abstraction, and which are being used today in missions such as the Mars Science Laboratory and other NASA missions.

MPCS↗
NASA NTRS1993

Upper Atmospheric Research Satellite (UARS) ground data system - The first operational data system for the Mission to Planet Earth

The initiation of the National Aeronautics and Space Administration (NASA) Mission to Planet Earth was realized with the activation of the Upper Atmosphere Research Satellite (LIARS) in mid-September 1991 following deployment from the Shuttle Transport System (STS) - 48. The UARS provides the first comprehensive study of the chemistry and dynamics of the upper atmosphere. The UARS ground data system provides the capabilities required to support upper atmospheric studies in a timely and flexible manner. The UARS ground data system policy and implementation plan incorporated by the UARS Project team provided the flexibility necessary to be able to respond to changing priorities and requirements and to permit the ground data system to evolve far beyond initial expectations. This paper describes the policies and plans in place during the initial design and implementation phases and provides an overview of the UARS ground data system. The paper then addresses the changing UARS ground data system design and implementation priorities, the early mission experiences instrumental in the achievement of higher than expected goals, and a brief look at the future for UARS, the first Mission to Planet Earth.

Herring, Ellen L.↗
NASA NTRS1993

Applications of CCSDS recommendations to Integrated Ground Data Systems (IGDS)

This paper describes an application of the CCSDS Principle Network (CPH) service model to communications network elements of a postulated Integrated Ground Data System (IGDS). Functions are drawn principally from COSMICS (Cosmic Information and Control System), an integrated space control infrastructure, and the Earth Observing System Data and Information System (EOSDIS) Core System (ECS). From functional requirements, this paper derives a set of five communications network partitions which, taken together, support proposed space control infrastructures and data distribution systems. Our functional analysis indicates that the five network partitions derived in this paper should effectively interconnect the users, centers, processors, and other architectural elements of an IGDS. This paper illustrates a useful application of the CCSDS (Consultive Committee for Space Data Systems) Recommendations to ground data system development.

Mizuta, Hiroshi↗
NASA NTRS2000

Ground Data System Risk Mitigation Techniques for Faster, Better, Cheaper Missions

With the advent of faster, cheaper, and better missions, NASA Projects acknowledged that a higher level of risk was inherent and accepted with this approach. It was incumbent however upon each component of the Project whether spacecraft, payload, launch vehicle, or ground data system to ensure that the mission would nevertheless be an unqualified success. The Small Explorer (SMEX) program's ground data system (GDS) team developed risk mitigation techniques to achieve these goals starting in 1989. These techniques have evolved through the SMEX series of missions and are practiced today under the Triana program. These techniques are: (1) Mission Team Organization--empowerment of a closeknit ground data system team comprising system engineering, software engineering, testing, and flight operations personnel; (2) Common Spacecraft Test and Operational Control System--utilization of the pre-launch spacecraft integration system as the post-launch ground data system on-orbit command and control system; (3) Utilization of operations personnel in pre-launch testing--making the flight operations team an integrated member of the spacecraft testing activities at the beginning of the spacecraft fabrication phase; (4) Consolidated Test Team--combined system, mission readiness and operations testing to optimize test opportunities with the ground system and spacecraft; and (5). Reuse of Spacecraft, Systems and People--reuse of people, software and on-orbit spacecraft throughout the SMEX mission series. The SMEX ground system development approach for faster, cheaper, better missions has been very successful. This paper will discuss these risk management techniques in the areas of ground data system design, implementation, test, and operational readiness.

Catena, John J.↗
NASA NTRS1983

TOPEX ground data system

The TOPEX Project is a proposed oceanographic mission to measure the topography of the sea surface for a period of three years. This mission is sponsored by the National Aeronautics and Space Administration and managed by the Jet Propulsion Laboratory. Measurements of topography are used to study ocean currents, tides, bathymetry and the oceanic geoid. Several of the primary goals of this mission are to process and verify the altimetric data, and distribute them within days to the science investigators. This paper describes the TOPEX end-to-end ground data system. In addition to controlling the TOPEX satellite, the ground data system has been designed to minimize the time from data acquisition to science processing and data distribution. A centralized design supports the favorable response time of the system and also allows for operational efficiencies. Networking of real time and non-real time elements of the data system provides for more effective data processing.

Rosell, S. N.↗
NASA NTRS1993

New approaches to NASA ground data systems

This paper discusses an exploration of approaches to providing ground data system support by NASA/Goddard Space Flight Center for scientific missions. Two architecture concepts are identified to provide full support using a mission specific instantiation concept, with distributed client-server architecture. The alternatives are assessed for impact to operations, and for hardware and software sizing. Evaluation benefits and risks is also provided.

Stottlemyer, A. R.↗
NASA NTRS2009

Using XML Configuration-Driven Development to Create a Customizable Ground Data System

The Mission data Processing and Control Subsystem (MPCS) is being developed as a multi-mission Ground Data System with the Mars Science Laboratory (MSL) as the first fully supported mission. MPCS is a fully featured, Java-based Ground Data System (GDS) for telecommand and telemetry processing based on Configuration-Driven Development (CDD). The eXtensible Markup Language (XML) is the ideal language for CDD because it is easily readable and editable by all levels of users and is also backed by a World Wide Web Consortium (W3C) standard and numerous powerful processing tools that make it uniquely flexible. The CDD approach adopted by MPCS minimizes changes to compiled code by using XML to create a series of configuration files that provide both coarse and fine grained control over all aspects of GDS operation.

Nash, Brent↗
NASA NTRS2012

Engineering a Multimission Approach to Navigation Ground Data System Operations

The Mission Design and Navigation (MDNAV) Section at the Jet Propulsion Laboratory (JPL) supports many deep space and earth orbiting missions from formulation to end of mission operations. The requirements of these missions are met with a multimission approach to MDNAV ground data system (GDS) infrastructure capable of being shared and allocated in a seamless and consistent manner across missions. The MDNAV computing infrastructure consists of compute clusters, network attached storage, mission support area facilities, and desktop hardware. The multimission architecture allows these assets, and even personnel, to be leveraged effectively across the project lifecycle and across multiple missions simultaneously. It provides a more robust and capable infrastructure to each mission than might be possible if each constructed its own. It also enables a consistent interface and environment within which teams can conduct all mission analysis and navigation functions including: trajectory design; ephemeris generation; orbit determination; maneuver design; and entry, descent, and landing analysis. The savings of these efficiencies more than offset the costs of increased complexity and other challenges that had to be addressed: configuration management, scheduling conflicts, and competition for resources. This paper examines the benefits of the multimission MDNAV ground data system infrastructure, focusing on the hardware and software architecture. The result is an efficient, robust, scalable MDNAV ground data system capable of supporting more than a dozen active missions at once.

Mission Design and Navigation (MDNAV)↗
NASA NTRS1993

International collaboration in SAR ground data systems

A set of considerations that are pertinent to future international cooperation in the area of synthetic aperture radar (SAR) ground data systems are presented. The considerations are as follows: (1) success of future spaceborne SAR missions will require multi-agency and/or multi-national collaboration; (2) ground processing is typically performed by each agency for their user base; (3) international standards are required to achieve a uniform data product independent of the processing center; (4) to reduce the aggregate cost of the ground data systems, collaboration is required in design and development; (5) effective utilization of the data by an international user community; (6) commercialization of data products; and (7) security of data systems.

Curlander, John C.↗
NASA NTRS1988

MODIS-HIRIS ground data systems commonality report

The High Resolution Imaging Spectrometer (HIRIS) and Moderate Resolution Imaging Spectrometer (MODIS) Data Systems Working Group was formed in September 1988 with representatives of the MODIS Data System Study Group and the HIRIS Project Data System Design Group to collaborate in the development of requirements on the EosDIS necessary to meet the science objectives of the two facility instruments. A major objective was to identify and promote commonality between the HIRIS and MODIS data systems, especially from the science users' point of view. A goal was to provide a base set of joint requirements and specifications which could easily be expanded to a Phase-B representation of the needs of the science users of all EOS instruments. This document describes the points of commonality and difference between the Level-II Requirements, Operations Concepts, and Systems Specifications for the ground data systems for the MODIS and HIRIS instruments at their present state of development.

Han, D.↗
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 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 NTRS2022

The Mars 2020 Ground Data System Architecture

The Mars 2020 Mission’s primary objective is to collect 20 geographically unique samples during its prime mission of one and a quarter Martian years, or just over 2 Earth years. Mission planners determined the project needed to develop a system that would enable the operations team to analyze engineering and science data, make science decisions, select viable rover targets at a millimeter resolution and validate an uplink bundle for a car sized rover with more complex science instruments than any previous Mars surface mission. All this had to be done within a five hour time frame. Doing this with a small team would be a challenge, but this had to be accomplished by a large team of engineers and scientists located across North America and Europe. Achieving this level of operational efficiency was unheard of in the prime mission. In addition, the mission had another set of requirements that had nothing to do with surface operations; the Mars 2020 Ground Data System (GDS) was also expected to comply with a new set of security requirements to keep up with the ever changing cybersecurity landscape. The Mars 2020 Ground Data System (GDS) is a re-architected version of the Mars Science Laboratory GDS. The primary goal was to integrate the lessons learned from previous Mars surface missions, accommodate a set of new requirements and capabilities required to ensure mission success, and comply with a new set of cybersecurity controls. The new architecture includes several unique qualities including a data lake, language-agnostic system-wide event-based operations, containerization, automated deployment, network segmentation, infrastructure-as-code, API-driven interfaces, and the first Mars surface GDS to operate primarily in the cloud. The new architecture enabled greater access to the system’s data, tighter integration with the operations team, and a higher level of traceability. The availability of the data also enabled a new set of capabilities previously not possible on surface missions. These new capabilities include an autonomous data to information, pipeline for downlink analysis, horizontal scaling of science data processing capabilities, autonomous round trip data tracking of science and engineering data, integration of flight system state into the tactical planning cycle, high fidelity targeting utilizing kinematic data, and hierarchical image and 3d meshes data representations. This paper will introduce the requirements for the Mars 2020 Mission, the heritage architecture, and the rationale for the changes to achieve the new architecture. The paper will continue to describe the fundamental changes made to the GDS architecture, how these changes enabled a more tightly integrated GDS, and the new capabilities that were enabled by the new architecture. The paper will conclude with the lessons learned from the process of rearchitecting a heritage GDS system and from the first 200 days of operations supporting over 800 users from around the world.

Lopez-Roig, Reynaldo↗