SEARCH · Search NASA
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.
The Earth Observing System (EOS) SAR ground data system
NASA, in association with ESA and NASDA, will launch the Space Station Freedom in 1993. As a complement to the Space Station, several unmanned Polar-Orbit Platforms (POPs) will be developed, built and launched with suites of instruments devoted to remote-sensing for earth surface and atmosphere observations or to planetary and deep-space studies. Attention is presently given to the POPs-associated Earth Observing System SAR Ground Data System, which encompasses a SAR processor, a postprocessing subsystem, a geophysical processor, and a data management and control subsystem.
Third International Symposium on Space Mission Operations and Ground Data Systems, part 2
Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The symposium papers focus on improvements in the efficiency, effectiveness, and quality of data acquisition, ground systems, and mission operations. New technology, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations. This volume covers expert systems, systems development tools and approaches, and systems engineering issues.
Third International Symposium on Space Mission Operations and Ground Data Systems, part 1
Under the theme of 'Opportunities in Ground Data Systems for High Efficiency Operations of Space Missions,' the SpaceOps '94 symposium included presentations of more than 150 technical papers spanning five topic areas: Mission Management, Operations, Data Management, System Development, and Systems Engineering. The papers focus on improvements in the efficiency, effectiveness, productivity, and quality of data acquisition, ground systems, and mission operations. New technology, techniques, methods, and human systems are discussed. Accomplishments are also reported in the application of information systems to improve data retrieval, reporting, and archiving; the management of human factors; the use of telescience and teleoperations; and the design and implementation of logistics support for mission operations.
Customizing the JPL Multimission Ground Data System: Lessons learned
The Multimission Ground Data System (MGDS) at NASA's Jet Propulsion Laboratory has brought improvements and new technologies to mission operations. It was designed as a generic data system to meet the needs of multiple missions and avoid re-inventing capabilities for each new mission and thus reduce costs. It is based on adaptable tools that can be customized to support different missions and operations scenarios. The MGDS is based on a distributed client/server architecture, with powerful Unix workstations, incorporating standards and open system architectures. The distributed architecture allows remote operations and user science data exchange, while also providing capabilities for centralized ground system monitor and control. The MGDS has proved its capabilities in supporting multiple large-class missions simultaneously, including the Voyager, Galileo, Magellan, Ulysses, and Mars Observer missions. The Operations Engineering Lab (OEL) at JPL has been leading Customer Adaptation Training (CAT) teams for adapting and customizing MGDS for the various operations and engineering teams. These CAT teams have typically consisted of only a few engineers who are familiar with operations and with the MGDS software and architecture. Our experience has provided a unique opportunity to work directly with the spacecraft and instrument operations teams and understand their requirements and how the MGDS can be adapted and customized to minimize their operations costs. As part of this work, we have developed workstation configurations, automation tools, and integrated user interfaces at minimal cost that have significantly improved productivity. We have also proved that these customized data systems are most successful if they are focused on the people and the tasks they perform and if they are based upon user confidence in the development team resulting from daily interactions. This paper will describe lessons learned in adapting JPL's 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 of a handful of engineers flying the Galileo Spacecraft flight system model.
Telemetry Metrics: Monitoring Data Quality in the Spacecraft Ground Data System
During the launch of Mars Odyssey, ground data system (GDS) engineers experienced a glitch in the ground data system that caused us to re-evaluate how we looked at spacecraft telemetry, particularly during the spacecraft development period and for critical spacecraft events in flight. Spacecraft telemetry told the subsystem and instrument engineers about the health and status of the spacecraft, but there was surprisingly little information about how well the ground data system was doing in getting information from the spacecraft to the engineers.The problem for the Mars Odyssey launch was with a single channel not updating as often as expected. Spacecraft engineers considered calling off the Launch but eventually decided that this particular channel did not provide information that was crucial for launch. It was only after the post launch acquisition of the Odyssey signal that ground data system engineers heard there had been a concern about the channel....
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Using Quality Attributes to Bridge Systems Engineering Gaps : A Juno Ground Data Systems Case Study
The Juno Mission to Jupiter is the second mission selected by the NASA New Frontiers Program. Juno launched August 2011 and will reach Jupiter July 2016. Juno's payload system is composed of nine instruments plus a gravity science experiment. One of the primary functions of the Juno Ground Data System (GDS) is the assembly and distribution of the CFDP (CCSDS File Delivery Protocol) product telemetry, also referred to as raw science data, for eight out of the nine instruments. The GDS accomplishes this with the Instrument Data Pipeline (IDP). During payload integration, the first attempt to exercise the IDP in a flight like manner revealed that although the functional requirements were well understood, the system was unable to meet latency requirements with the as-is heritage design. A systems engineering gap emerged between Juno instrument data delivery requirements and the assumptions behind the heritage flight-ground interactions. This paper describes the use of quality attributes to measure and overcome this gap by introducing a new systems engineering activity, and a new monitoring service architecture that successfully delivered the performance metrics needed to validate Juno IDP.
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Customizing the JPL Multimission Ground Data System for Improved Productivity
The Multimission Ground Data System was designed as a generic data system to meet the needs of multiple missions and avoid re-inventing capabilities for each new mission and thus reduce costs.
Ground data systems resource allocation process
The Ground Data Systems Resource Allocation Process at the Jet Propulsion Laboratory provides medium- and long-range planning for the use of Deep Space Network and Mission Control and Computing Center resources in support of NASA's deep space missions and Earth-based science. Resources consist of radio antenna complexes and associated data processing and control computer networks. A semi-automated system was developed that allows operations personnel to interactively generate, edit, and revise allocation plans spanning periods of up to ten years (as opposed to only two or three weeks under the manual system) based on the relative merit of mission events. It also enhances scientific data return. A software system known as the Resource Allocation and Planning Helper (RALPH) merges the conventional methods of operations research, rule-based knowledge engineering, and advanced data base structures. RALPH employs a generic, highly modular architecture capable of solving a wide variety of scheduling and resource sequencing problems. The rule-based RALPH system has saved significant labor in resource allocation. Its successful use affirms the importance of establishing and applying event priorities based on scientific merit, and the benefit of continuity in planning provided by knowledge-based engineering. The RALPH system exhibits a strong potential for minimizing development cycles of resource and payload planning systems throughout NASA and the private sector.
Conducting Efficient Remote Science and Planning Operations for Ocean Exploration Using Exploration Ground Data Systems (xGDS)
NASA Ames’ Exploration Ground Data Systems (xGDS) supports rapid scientific decision making by synchronizing information in time and space, including video and still images, scientific instrument data, and science and operations notes in geographic and temporal context. We have deployed xGDS at multiple NASA field analog missions over the past decade. In the last two years, we have participated in SUBSEA, a multi-institution collaborative project*. SUBSEA used the research ship E/V Nautilus along with its two remotely operated vehicles (ROVs), Hercules and Argus, to explore deep ocean volcanic vents as an analog for ocean worlds (e.g. Enceladus). This work allowed us to compare the existing oceanographic operations methods and technologies used for ocean exploration with corresponding tools and approaches developed and used at NASA. In the first year of SUBSEA we observed existing remote science operations from the Inner Space Center (ISC)**. In the second year, we deployed xGDS at ISC to complement existing capabilities with xGDS tools designed to support remote Nautilus science operations from the ISC. During operations, video, ROV position and instrument telemetry were streamed from the ship to the ISC. As the science team watched dive operations, they could annotate the data with observations that were relevant to their work domain. Later, the team members could review the data at their own pace to collaboratively develop a dive plan for the next day, which had to be delivered on a fixed daily schedule. The opportunity to compare operations under different conditions enabled us to make several key observations about conducting remote science and planning operations efficiently: (i) Reviewing data collaboratively and interactively with temporal and spatial context was critical for the remote science team’s ability to plan dive operations on the Nautilus. (ii) Science team members were actively engaged with the remote dive operations because they could interact with the collected data and visualize it as they desired. (iii) Being able to replay past events at accelerated speeds, and jump to points in time and spaced based on search results, provided efficient access to critical points of interest in a massive volume of data, so the remote science team could deliver plans on time. * SUBSEA (Systematic Underwater Biogeochemical Science and Exploration Analog) is a multi-institution collaboration supported by NASA, NOAA’s Office of Exploration Research (OER), the Ocean Exploration Trust (OET) and the University of Rhode Island’s Graduate School of Oceanography (GSO).
Using Quality Attributes to Bridge Systems Engineering Gaps : a Juno Ground Data Systems Case Study
No abstract available
Achieving Lights-Out Operation of SMAP Using Ground Data System Automation
The approach used in the SMAP ground data system to provide reliable, automated capabilities to conduct unattended operations has been presented. The impacts of automation on the ground data system architecture were discussed, including the three major automation patterns identified for SMAP and how these patterns address the operations use cases. The architecture and approaches used by SMAP will set the baseline for future JPL Earth Science missions.
Development of the Cassini Ground Data System in a multimission environment
As baselined, the Cassini Ground Data System (GDS) will be composed of Project specific and multimission elements. The former will be developed by the Cassini Project and the latter by two JPL institutional organizations, the Telecommunications and Data Acquisition Office (TDA) and the Multimission Operations Systems Office (MOSO). The GDS will be developed in three principal phases: Spacecraft Test, Launch-cruise, and Science Tour, with a significant part of the development deferred until the post-launch period. New capabilities are being introduced that are key to the achievement of more cost effective operations. Successful development of the system will require careful planning and will involve participation of diverse disciplines. This paper introduces the Cassini Project from the Ground Data System perspective and discusses development approaches expected to produce systems which meet functional and performance requirements and which will be delivered on schedule and within budget.
Multiple views of ground data system
Explore the source record for details and available documents.
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. The Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create an 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...