SEARCH · Engineering Papers
Results for “ground software GDS”
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.
Multiple views of ground data system
Explore the source record for details and available documents.
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.
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.
Internet Distribution of Spacecraft Telemetry Data
Remote Access Multi-mission Processing and Analysis Ground Environment (RAMPAGE) is a Java-language server computer program that enables near-real-time display of spacecraft telemetry data on any authorized client computer that has access to the Internet and is equipped with Web-browser software. In addition to providing a variety of displays of the latest available telemetry data, RAMPAGE can deliver notification of an alarm by electronic mail. Subscribers can then use RAMPAGE displays to determine the state of the spacecraft and formulate a response to the alarm, if necessary. A user can query spacecraft mission data in either binary or comma-separated-value format by use of a Web form or a Practical Extraction and Reporting Language (PERL) script to automate the query process. RAMPAGE runs on Linux and Solaris server computers in the Ground Data System (GDS) of NASA's Jet Propulsion Laboratory and includes components designed specifically to make it compatible with legacy GDS software. The client/server architecture of RAMPAGE and the use of the Java programming language make it possible to utilize a variety of competitive server and client computers, thereby also helping to minimize costs.
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.
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...
Securing Ground Data System Applications for Space Operations
The increasing prevalence and sophistication of cyber attacks has prompted the Multimission Ground Systems and Services (MGSS) Program Office at Jet Propulsion Laboratory (JPL) to initiate the Common Access Manager (CAM) effort to protect software applications used in Ground Data Systems (GDSs) at JPL and other NASA Centers. The CAM software provides centralized services and software components used by GDS subsystems to meet access control requirements and ensure data integrity, confidentiality, and availability. In this paper we describe the CAM software; examples of its integration with spacecraft commanding software applications and an information management service; and measurements of its performance and reliability.
Astrobee: A New Platform for Free-Flying Robotics on the International Space Station
The Astrobees are next-generation free-flying robots that will operate in the interior of the International Space Station (ISS). Their primary purpose is to provide a flexible platform for research on zero-g freeflying robotics, with the ability to carry a wide variety of future research payloads and guest science software. They will also serve utility functions: as free-flying cameras to record video of astronaut activities, and as mobile sensor platforms to conduct surveys of the ISS. The Astrobee system includes two robots, a docking station, and a ground data system (GDS). It is developed by the Human Exploration Telerobotics 2 (HET-2) Project, which began in Oct. 2014, and will deliver the Astrobees for launch to ISS in 2017. This paper covers selected aspects of the Astrobee design, focusing on capabilities relevant to potential users of the platform.
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.
Adapting a Large-Scale Multi-Mission Ground System for Low-Cost CubeSats
The majority of today's CubeSat fleet consists of Earth-orbiting missions that mostly use existing ground systems developed by universities because of availability, simplicity, and low-cost. The Interplanetary NanoSpacecraft Pathfinder In Relevant Environment (INSPIRE) mission is a revolutionary CubeSat mission that will launch a pair of CubeSats into deep space to study the feasibility of CubeSats beyond low-Earth orbit. This uncovers a new set of systems and software engineering challenges to the development of a robust and reliable ground system in a low-cost environment. In this paper, we discuss the approach to these challenges by using the Jet Propulsion Laboratory's (JPL) Advanced Multimission Operation System (AMMOS) Ground Data System (GDS) as well as the methodologies used to engineer the flight system to work with an existing ground system developed for large-scale missions. Specifically we will focus on the command and telemetry subsystem of AMMOS, the Multimission Data Processing and Control System. We conclude with a retrospective on the challenges encountered and a brief discussion on our efforts to provide AMMOS to support future deep space CubeSat missions.
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
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.
Development and Use of a Web-based Automated Command Request Application in a Distributed Operations Environment for the Cassini Saturn Mission
This paper discusses the evolution of the eCRF software from conception through deployment, challenges encountered and lessons learned, as well as current status and refinements.
Renaissance architecture for Ground Data Systems
The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.
Where's My Data - WMD
WMD provides a centralized interface to access data stored in the Mission Data Processing and Control System (MPCS) GDS (Ground Data Systems) databases during MSL (Mars Science Laboratory) Testbeds and ATLO (Assembly, Test, and Launch Operations) test sessions. The MSL project organizes its data based on venue (Testbed, ATLO, Ops), with each venue's data stored on a separate database, making it cumbersome for users to access data across the various venues. WMD allows sessions to be retrieved through a Web-based search using several criteria: host name, session start date, or session ID number. Sessions matching the search criteria will be displayed and users can then select a session to obtain and analyze the associated data. The uniqueness of this software comes from its collection of data retrieval and analysis features provided through a single interface. This allows users to obtain their data and perform the necessary analysis without having to worry about where and how to get the data, which may be stored in various locations. Additionally, this software is a Web application that only requires a standard browser without additional plug-ins, providing a cross-platform, lightweight solution for users to retrieve and analyze their data. This software solves the problem of efficiently and easily finding and retrieving data from thousands of MSL Testbed and ATLO sessions. WMD allows the user to retrieve their session in as little as one mouse click, and then to quickly retrieve additional data associated with the session.
Astrobee Free Flyers: Integrated and Tested. Ready for Launch!
As of March 2019, four Astrobee free-flying robots have been integrated, tested and shipped to NASA’s Johnson Space Center, Texas, ready to be launched to space. Two of these Astrobee units (Honey and Bumble) will be launched to the International Space Station (ISS) on April 17, 2019, on the Cygnus NG-11 (Northrop Grumman) cargo resupply spacecraft from the Mid-Atlantic Regional Spaceport (MARS) launch facility, at NASA's Wallops Flight Facility, in Virginia, while the third unit (Queen) will be launched in mid-July 2019, with the cargo resupply mission Space-X 18, from Cape Canaveral, at NASA’s Kennedy Space Center. The primary purpose of the Astrobee system is to provide an autonomous and flexible platform for research on zero-g free-flying robotics, with the ability to accommodate guest researchers looking to utilize the unique capabilities of this platform in the microgravity of low earth orbit, and to advance the state of the art of guest science software and research payloads, which range from gecko-inspired adhesives for perching on smooth surfaces, to augmented reality interfaces to help astronauts and robots work together effectively, to RFID reader, performing inventory of RFID tagged items inside the ISS. Astrobee will also serve utility functions, such as free-flying cameras to record video and provide assistance during astronaut activities, and as mobile sensor platforms to conduct surveys of the ISS. In this paper we will give an overview of the status of the Astrobee system, which includes the docking station already launched and mounted in the JAXA JEM module of the ISS, the Astrobee robots, the Astrobee robotic arms, the ground data system (GDS) and the development of the several guest science payloads.
COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover
Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.