Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission management ground data systems”

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 NTRSDate not supplied

Information Systems for Crew-Led Operations Beyond Low-Earth Orbit

On past and present human space missions, the management of vehicle health and status has primarily been executed from Earth. Missions such as Apollo, Space Shuttle, and ISS have relied on a safety net of ground-based experts with access to real-time telemetry data, broad and deep systems expertise, and powerful analytical and computing capabilities. The ground team monitors and manages the vehicle’s health in real-time and responds quickly to critical situations and malfunctions. Ground operators also provide real-time oversight and verbal guidance to flight crew members, especially during complex procedure execution and high-risk activities like extra-vehicular activities. However, this operational paradigm, in place for 60 years, will not transfer to long duration exploration missions beyond low Earth orbit (LEO). Lunar and deep-space crewed missions will encounter delayed communications that prohibit real-time operational and medical support. Additionally, there will be infrequent resupply and a diminished capacity to evacuate or rescue crew members. A small crew must operate independently, managing the vehicle’s state, responding to time-critical events, and executing complex procedures, all without the safety net of real-time support.

data representation↗
NASA NTRS2003

Multi-mission ground data systems - breakthroughs and challenges

Given the cost-constrained nature of JPL Flight Projects, especially Discovery Class missions, there is more and more pressure to reduce the costs associated with mission operations, particularly the costs for the Ground Data System. This paper explores the successes (and failures) of using the Mission Management Office (MMO) GDS team to provide a common set of services, tools, procedures, and products to JPL Flight Projects.

GDS↗
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 NTRS2008

Advancing NASA's Satellite Control Capabilities: More than Just Better Technology

This viewgraph presentation reviews the work of the Goddard Mission Services Evolution Center (GMSEC) in the development of the NASA's satellite control capabilities. The purpose of the presentation is to provide a quick overview of NASA's Goddard Space Flight Center and our approach to coordinating the ground system resources and development activities across many different missions. NASA Goddard's work in developing and managing the current and future space exploration missions is highlighted. The GMSEC, was established to to coordinate ground and flight data systems development and services, to create a new standard ground system for many missions and to reflect the reality that business reengineering and mindset were just as important.

Smith, Danford↗
NASA NTRS1994

Autonomous mission planning and scheduling: Innovative, integrated, responsive

Autonomous mission scheduling, a new concept for NASA ground data systems, is a decentralized and distributed approach to scientific spacecraft planning, scheduling, and command management. Systems and services are provided that enable investigators to operate their own instruments. In autonomous mission scheduling, separate nodes exist for each instrument and one or more operations nodes exist for the spacecraft. Each node is responsible for its own operations which include planning, scheduling, and commanding; and for resolving conflicts with other nodes. One or more database servers accessible to all nodes enable each to share mission and science planning, scheduling, and commanding information. The architecture for autonomous mission scheduling is based upon a realistic mix of state-of-the-art and emerging technology and services, e.g., high performance individual workstations, high speed communications, client-server computing, and relational databases. The concept is particularly suited to the smaller, less complex missions of the future.

Sary, Charisse↗
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 NTRS1996

Development of an automated control center for the EUVE mission

The Automated Project Operations Control Center (APOCC) was developed to enable automated data acquisition, ground system management and spacecraft health and safety monitoring. The control center will be used for the Extreme Ultraviolet Explorer (EUVE) project to reduce operations staffing from three to one shift per day, while maintaining the science return and performing routine health and safety monitoring activities. The staff reduction is expected to yield a cost reduction of 250,000 dollars per year in comparison with a fully staffed, 24 hour/day operation. The APOCC infrastructure was designed to be reusable and extensible. Configurable data items are stored in data bases and spacecraft-specific information is stored in a health and safety monitoring knowledge base.

Penafiel, Catherine↗
NASA NTRS1985

Systematic analysis of EOS data system for operations

A data management analysis methodology is being proposed. The objective of the methodology is to assist mission managers by identifying a series of ordered activities to be systematically followed in order to arrive at an effective ground system design. Existing system engineering tools and concepts have been assembled into a structured framework to facilitate the work of a mission planner. It is intended that this methodology can be gainfully applied (with probable modifications and/or changes) to the EOS payloads and their associated data systems.

Moe, K. L.↗
NASA NTRS1993

Management of information for mission operations using automated keyword referencing

Although millions of dollars have helped to improve the operability and technology of ground data systems for mission operations, almost all mission documentation remains bound in printed volumes. This form of documentation is difficult and timeconsuming to use, may be out-of-date, and is usually not cross-referenced with other related volumes of mission documentation. A more effective, automated method of mission information access is needed. A new method of information management for mission operations using automated keyword referencing is proposed. We expound on the justification for and the objectives of this concept. The results of a prototype tool for mission information access that uses a hypertextlike user interface and existing mission documentation are shared. Finally, the future directions and benefits of our proposed work are described.

Davidson, Roger A.↗
NASA NTRSDate not supplied

A Technical Overview of the Mission Engagement Onboarding Process Managed by the Mission Engagement Working Group (MEWG)

NASA's intricate network, encompassing the Near Space Network (NSN) and Deep Space Network (DSN), plays a pivotal role in supporting an array of space missions. These range from those in Low Earth Orbit (LEO) and Geosynchronous Orbit (GEO), to the more distant Cislunar and Deep Space endeavors. To manage the vast communications needs, we utilize multiple ground stations globally, coupled with the Tracking and Data Relay Satellite System (TDRSS). The Mission Engagement Working Group (MEWG), within the Commercialization, Innovation, and Synergies (CIS) division, stands as the primary gateway for all Space Communications and Network (SCaN) communication and navigation requests. This includes not only NASA's internal missions but also extends to other governmental agencies and commercial sector endeavors. How does the MEWG Process Work? - Initial Contact : Clients initiate their interaction with the NSN by submitting their service requirements through a dedicated online portal. - Preliminary Assessment by MEWG: Upon submission, MEWG embarks on a primary screening of the request. This involves evaluating the client's identity and the foundational concept of their mission. - Detailed Analysis by the NSN Team: Parallelly, the NSN team conducts a comprehensive review of the service request. This often necessitates additional clarification from the requester, ensuring that the final assessment is both thorough and accurate. - Coordination & Streamlining: MEWG's overarching objective is to effectively log, classify, orchestrate, and guarantee that pertinent actions are delegated based on initial client interactions. Acting as the central hub for these primary contacts, MEWG ensures that each request is sufficiently detailed for an in-depth evaluation. - Feedback & Remediation: If a request is deemed unsuitable or lacking, MEWG doesn't merely reject it. Instead, the team discerns the reasons for the inadequacy and suggests potential rectification strategies. This approach ensures that feedback delivered to clients is precise, prompt, constructive, and actionable. Conclusion: This plenary presentation will detail the efforts of the MEWG resulting in a greatly streamlined and refined onboarding process for space communication Direct-To-Earth (DTE) and Space Relay (SR) support requests. By centralizing the preliminary interactions and assessments, we've reduced the complexity for clients, ensuring they engage with a singular, efficient, and responsive point of contact. This initiative, we believe, fortifies NASA's commitment to fostering effective and synergistic collaborations with its partners.

Devin L Bitner↗
NASA NTRSDate not supplied

A Technical Overview of the Mission Engagement Onboarding Process Managed by the Mission Engagement Working Group (MEWG)

NASA's intricate network, encompassing the Near Space Network (NSN) and Deep Space Network (DSN), plays a pivotal role in supporting an array of space missions. These range from those in Low Earth Orbit (LEO) and Geosynchronous Orbit (GEO), to the more distant Cislunar and Deep Space endeavors. To manage the vast communications needs, we utilize multiple ground stations globally, coupled with the Tracking and Data Relay Satellite System (TDRSS). The Mission Engagement Working Group (MEWG), within the Commercialization, Innovation, and Synergies (CIS) division, stands as the primary gateway for all Space Communications and Network (SCaN) communication and navigation requests. This includes not only NASA's internal missions but also extends to other governmental agencies and commercial sector endeavors. How does the MEWG Process Work? - Initial Contact : Clients initiate their interaction with the NSN by submitting their service requirements through a dedicated online portal. - Preliminary Assessment by MEWG: Upon submission, MEWG embarks on a primary screening of the request. This involves evaluating the client's identity and the foundational concept of their mission. - Detailed Analysis by the NSN Team: Parallelly, the NSN team conducts a comprehensive review of the service request. This often necessitates additional clarification from the requester, ensuring that the final assessment is both thorough and accurate. - Coordination & Streamlining: MEWG's overarching objective is to effectively log, classify, orchestrate, and guarantee that pertinent actions are delegated based on initial client interactions. Acting as the central hub for these primary contacts, MEWG ensures that each request is sufficiently detailed for an in-depth evaluation. - Feedback & Remediation: If a request is deemed unsuitable or lacking, MEWG doesn't merely reject it. Instead, the team discerns the reasons for the inadequacy and suggests potential rectification strategies. This approach ensures that feedback delivered to clients is precise, prompt, constructive, and actionable. Conclusion: This plenary presentation will detail the efforts of the MEWG resulting in a greatly streamlined and refined onboarding process for space communication Direct-To-Earth (DTE) and Space Relay (SR) support requests. By centralizing the preliminary interactions and assessments, we've reduced the complexity for clients, ensuring they engage with a singular, efficient, and responsive point of contact. This initiative, we believe, fortifies NASA's commitment to fostering effective and synergistic collaborations with its partners.

Devin Bitner↗
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 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 NTRS2002

Systems Architecture for Fully Autonomous Space Missions

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Esper, Jamie↗
NASA NTRS2014

Exploration Medical System Demonstration

BACKGROUND: Exploration class missions will present significant new challenges and hazards to the health of the astronauts. Regardless of the intended destination, beyond low Earth orbit a greater degree of crew autonomy will be required to diagnose medical conditions, develop treatment plans, and implement procedures due to limited communications with ground-based personnel. SCOPE: The Exploration Medical System Demonstration (EMSD) project will act as a test bed on the International Space Station (ISS) to demonstrate to crew and ground personnel that an end-to-end medical system can assist clinician and non-clinician crew members in optimizing medical care delivery and data management during an exploration mission. Challenges facing exploration mission medical care include limited resources, inability to evacuate to Earth during many mission phases, and potential rendering of medical care by non-clinicians. This system demonstrates the integration of medical devices and informatics tools for managing evidence and decision making and can be designed to assist crewmembers in nominal, non-emergent situations and in emergent situations when they may be suffering from performance decrements due to environmental, physiological or other factors. PROJECT OBJECTIVES: The objectives of the EMSD project are to: a. Reduce or eliminate the time required of an on-orbit crew and ground personnel to access, transfer, and manipulate medical data. b. Demonstrate that the on-orbit crew has the ability to access medical data/information via an intuitive and crew-friendly solution to aid in the treatment of a medical condition. c. Develop a common data management framework that can be ubiquitously used to automate repetitive data collection, management, and communications tasks for all activities pertaining to crew health and life sciences. d. Ensure crew access to medical data during periods of restricted ground communication. e. Develop a common data management framework that allows for scalability, extensibility, and interoperability of data sources and data users. f. Lower total cost of ownership for development and sustainment of peripheral hardware and software that use EMSD for data management. g. Provide a better standard of healthcare for crew members through reductions in the time required by crew and ground personnel to provide medical treatment and the number of crew errors experienced during treatment.

Rubin, D. A.↗
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. 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...

ground data system (GDS)↗
NASA NTRS2019

Medical System Concept of Operations for Mars Exploration Mission-11: Exploration Medical Capability (ExMC) Element - Human Research Program

NASA’s exploration missions to Mars will have durations of 2-3 years and will take humans farther away from Earth than ever before. This will result in a paradigm shift for mission planning, spacecraft design, human systems integration, and in-flight medical care. Constraints on real-time communication, resupply, and medical evacuation are major architectural drivers. These constraints require medical system development to be tightly integrated with mission and vehicle design to provide crew autonomy and enable mission success. This concept of operations provides a common vision of medical care for developing a medical system for Mars exploration missions. It documents an overview of the stakeholder needs and goals of a medical system and provides examples of the types of activities the system will be used for during the mission. Development of the concept of operations considers mission variables such as distance from Earth, duration of mission, time to definitive medical care, communication protocols between crewmembers and ground support, personnel capabilities and skill sets, medical hardware and software, and medical data management. The information provided in this document informs the ExMC Systems Engineering effort to define the functions to be provided by the medical system. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions. This document is applicable to the ExMC Element Systems Engineering process and may be used for collaboration within the Human Research Program.

Urbina, Michelle↗