SEARCH · Search NASA

Results for “Mission Operations”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 631 records · Page 35

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

SAGE III on ISS: Mission Update and Science Milestone Results and Future Plans

The Stratospheric Aerosol and Gas Experiment III on the International Space Station (SAGE III/ISS) has been collecting data on the stratosphere almost continuously for 4 years since the first light milestone was achieved on March 17, 2017. In that time, the SAGE III/ISS data products have withstood robust assessments both internal and external, using comparisons to data sets both in-situ and spaceborne, and incorporated improvements into the retrieval algorithm and the science data products themselves. With the new v5.2 release of the SAGE III/ISS science data product algorithm, improvements made to the aerosol and water vapor products have produced better correlations with both MLS and balloonsonde data. At this 4-year milestone, we will look back on the last 4 years of data collection highlighting SAGE III/ISS ozone and aerosol data from 2017-2020 in a 6-minute video highlighting the SAGE III mission. An overview of mission operations and the challenges of operating a science mission on the ISS will highlight lessons learned and the mission science objectives completed during the first three years of the mission. The future goals for the SAGE III/ISS mission, as we continue operations and science collection, will round out the presentation.

Marilee M Roell↗

NASA NTRS2002

Converging voice and data over mission-critical networks

The U.S. National Aeronautics and Space Administration (NASA) Deep Space Network ?? DSN - is an international network of antennas that supports interplanetary spacecraft missions and radio and radar astronomy observations for the exploration of the solar system and the universe. The network also supports selected Earth-orbiting missions. This paper describes the ground communications network of the DSN and ways network infrastructure costs are being reduced by the introduction of new technology. Fundamentally, the DSN ground network architecture is a star network, and the hub is at JPL in Pasadena, California. Communications to customer sites are designed to minimize NASA costs and may be either shared IP backbone networks or dedicated circuits. One of the primary features of the network is its ability to support real-time data, voice, and video communications among antenna stations, an automated multi-mission operations systems facility at JPL (AMMOS), and mission operations centers (MOCs) at NASA and non-NASA facilities. Funding for advanced engineering to reduce ground network infrastructure costs was provided by the NASA Office of Space Science.

ground communications networks Internet voice VOIP↗

NASA NTRS2012

Cloud Computing for Mission Design and Operations

The space mission design and operations community already recognizes the value of cloud computing and virtualization. However, natural and valid concerns, like security, privacy, up-time, and vendor lock-in, have prevented a more widespread and expedited adoption into official workflows. In the interest of alleviating these concerns, we propose a series of guidelines for internally deploying a resource-oriented hub of data and algorithms. These guidelines provide a roadmap for implementing an architecture inspired in the cloud computing model: associative, elastic, semantical, interconnected, and adaptive. The architecture can be summarized as exposing data and algorithms as resource-oriented Web services, coordinated via messaging, and running on virtual machines; it is simple, and based on widely adopted standards, protocols, and tools. The architecture may help reduce common sources of complexity intrinsic to data-driven, collaborative interactions and, most importantly, it may provide the means for teams and agencies to evaluate the cloud computing model in their specific context, with minimal infrastructure changes, and before committing to a specific cloud services provider.

cloud computing↗

NASA NTRS1994

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Mahmot, Ron↗

NASA NTRS2006

Advances in Distributed Operations and Mission Activity Planning for Mars Surface Exploration

A centralized mission activity planning system for any long-term mission, such as the Mars Exploration Rover Mission (MER), is completely infeasible due to budget and geographic constraints. A distributed operations system is key to addressing these constraints; therefore, future system and software engineers must focus on the problem of how to provide a secure, reliable, and distributed mission activity planning system. We will explain how Maestro, the next generation mission activity planning system, with its heavy emphasis on portability and distributed operations has been able to meet these design challenges. MER has been an excellent proving ground for Maestro's new approach to distributed operations. The backend that has been developed for Maestro could benefit many future missions by reducing the cost of centralized operations system architecture.

Mars Exploration Rover (MER)↗

NASA NTRS2014

Low-Cost, Class D Testing of Spacecraft Photovoltaic Systems Can Reduce Risk

The end-to-end verification of a spacecraft photovoltaic power generation system requires light! Specifically, the standard practice for doing so is the Large Area Pulsed Solar Simulation (LAPSS). A LAPSS test can characterize a photovoltaic system's efficiency via its response to rapidly applied impulses of simulated sunlight. However, a Class D program on a constrained budget and schedule may not have the resources to ship an entire satellite for a LAPSS test alone. Such was the case with the Lunar Atmospheric and Dust Environment Explorer (LADEE) program, which was also averse to the risk of hardware damage during shipment. When the Electrical Power System (EPS) team was denied a spacecraft-level LAPSS test, the lack of an end-to-end power generation test elevated to a project-level technical risk. The team pulled together very limited resources to not only eliminate the risk, but build a process to monitor the health of the system through mission operations. We discuss a process for performing a low-cost, end-to-end test of the LADEE photovoltaic system. The approach combines system-level functional test, panel-level performance results, and periodic inspection (and repair) up until launch. Following launch, mission operations tools are utilized to assess system performance based on a scant amount of data. The process starts in manufacturing at the subcontractor. The panel manufacturer provides functional test and LAPSS data on each individual panel. We apply an initial assumption that the per-panel performance is sufficient to meet the power generation requirements. The manufacturer's data is also carried as the performance allocation for each panel during EPS system modeling and initial mission operations. During integration and test, a high-power, professional theater lamp system provides simulated sunlight to each panel on the spacecraft, thereby permitting a true end-to-end system test. A passing test results in a step response to nearly full-rated current at the appropriate solar array switch in the power system. A metal-halide bulb, infrared imagers, and onboard spacecraft measurements are utilized to minimize risk of thermal damage during test. Data is provided to support test results for both passing and marginal panels. Prior to encapsulation in the launch vehicle, each panel is inspected for damage by the panel manufacturer. Cracked cells or other damage is amended on-site. Because the photovoltaic test system is inexpensive and portable, each repaired panel can be re-verified immediately. Post-launch, the photovoltaic system is again characterized for per-panel deviations from the manufacturer's performance test. This proved especially tricky as the LADEE spacecraft performs only one current measurement on the entire array. The algorithm for Matlab tools to assess panel performance based on spacecraft attitude is discussed. While not as precise and comprehensive as LAPSS, the LADEE approach leverages minimal resources into an ongoing assessment program that can be applied through numerous stages of the mission. The project takes a true Class D approach in assessing the technical value of a spacecraft level performance test versus the programmatic risk of shipping the spacecraft to another facility. The resources required are a fraction of that for a LAPSS test, and is easy to repeat. Further, the test equipment can be handed down to future projects without building an on-site facility.

photovoltaic↗

NASA NTRS2016

Asteroid Redirect Mission Proximity Operations for Reference Target Asteroid 2008 EV5

NASA's Asteroid Redirect Mission (ARM) is composed of two segments, the Asteroid Redirect Robotic Mission (ARRM), and the Asteroid Redirect Crewed Mission (ARCM). In March of 2015, NASA selected the Robotic Boulder Capture Option1 as the baseline for the ARRM. This option will capture a multi-ton boulder, (typically 2-4 meters in size) from the surface of a large (greater than approx.100 m diameter) Near-Earth Asteroid (NEA) and return it to cis-lunar space for subsequent human exploration during the ARCM. Further human and robotic missions to the asteroidal material would also be facilitated by its return to cis-lunar space. In addition, prior to departing the asteroid, the Asteroid Redirect Vehicle (ARV) will perform a demonstration of the Enhanced Gravity Tractor (EGT) planetary defense technique2. This paper will discuss the proximity operations which have been broken into three phases: Approach and Characterization, Boulder Capture, and Planetary Defense Demonstration. Each of these phases has been analyzed for the ARRM reference target, 2008 EV5, and a detailed baseline operations concept has been developed.

Reeves, David M.↗

NASA NTRS2014

OPALS: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

In spring 2014, the Optical PAyload for Lasercomm Science (OPALS) will launch to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a 90-day baseline mission, OPALS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) in Wrightwood, California. To achieve mission success, interfaces to the ISS payload operations infrastructure are established. For OPALS, the interfaces facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes such as pointing prediction and data processing satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The tests have provided valuable insight into operational considerations on the ISS.

Abrahamson, Matthew J.↗

NASA NTRS1994

(abstract) Science-Project Interaction in the Low-Cost Mission

Large, complex, and highly optimized missions have performed most of the preliminary reconnaisance of the solar system. As a result we have now mapped significant fractions of its total surface (or surface-equivalent) area. Now, however, scientific exploration of the solar system is undergoing a major change in scale, and existing missions find it necessary to limit costs while fulfilling existing goals. In the future, NASA's Discovery program will continue the reconnaisance, exploration, and diagnostic phases of planetary research using lower cost missions, which will include lower cost mission operations systems (MOS). Historically, one of the more expensive functions of MOS has been its interaction with the science community. Traditional MOS elements that this interaction have embraced include mission planning, science (and engineering) event conflict resolution, sequence optimization and integration, data production (e.g., assembly, enhancement, quality assurance, documentation, archive), and other science support services. In the past, the payoff from these efforts has been that use of mission resources has been highly optimized, constraining resources have been generally completely consumed, and data products have been accurate and well documented. But because these functions are expensive we are now challenged to reduce their cost while preserving the benefits. In this paper, we will consider ways of revising the traditional MOS approach that might save project resources while retaining a high degree of service to the Projects' customers. Pre-launch, science interaction can be made simplier by limiting numbers of instruments and by providing greater redundancy in mission plans. Post launch, possibilities include prioritizing data collection into a few categories, easing requirements on real-time of quick-look data delivery, and closer integration of scientists into the mission operation.

mission operation science community interaction co↗

NASA NTRS2006

Advances in distributed operations and mission activity planning for Mars surface exploration

Shams, Khawaja↗

NASA NTRS2004

Data Management for Mars Exploration Rovers

Data Management for the Mars Exploration Rovers (MER) project is a comprehensive system addressing the needs of development, test, and operations phases of the mission. During development of flight software, including the science software, the data management system can be simulated using any POSIX file system. During testing, the on-board file system can be bit compared with files on the ground to verify proper behavior and end-to-end data flows. During mission operations, end-to-end accountability of data products is supported, from science observation concept to data products within the permanent ground repository. Automated and human-in-the-loop ground tools allow decisions regarding retransmitting, re-prioritizing, and deleting data products to be made using higher level information than is available to a protocol-stack approach such as the CCSDS File Delivery Protocol (CFDP).

Mars missions↗

NASA NTRS2014

Extravehicular Activity Asteroid Exploration and Sample Collection Capability

One of the challenging primary objectives associated with NASA's Asteroid Redirect Crewed Mission (ARCM) is to demonstrate deep space Extravehicular Activity (EVA) and tools and to obtain asteroid samples to return to Earth for further study. Prior Shuttle and International Space Station (ISS) spacewalks have benefited from engineered EVA interfaces which have been designed and manufactured on Earth. Rigid structurally mounted handrails, and tools with customized interfaces and restraints optimize EVA performance. For ARCM, EVA complexity increases due to the uncertainty of the asteroid properties. The variability of rock size, shape and composition, as well as behavior of the asteroid capture mechanism will complicate EVA translation, tool restraint, and body stabilization. The unknown asteroid hardness and brittleness will complicate tool use. The rock surface will introduce added safety concerns for cut gloves and debris control. Feasible solutions to meet ARCM EVA objectives were identified using experience gained during Apollo, Shuttle, and ISS EVAs, terrestrial mountaineering practices, NASA Extreme Environment Mission Operations (NEEMO) 16 mission, and during Neutral Buoyancy Laboratory testing in the Modified Advanced Crew Escape Suit (MACES) suit. This paper will summarize the overall operational concepts for conducting EVAs for the ARCM mission including translation paths and body restraint methods, potential tools used to extract the samples, design implications for the Asteroid Redirect Vehicle (ARV) for EVA, and the results of early development testing of potential EVA tasks.

Sipila, Stephanie A.↗

NASA NTRS2014

Extravehicular Activity Asteroid Exploration and Sample Collection Capability

Sipila, Stephanie A.↗

NASA NTRS2003

Designing Facilities for Collaborative Operations

A methodology for designing operational facilities for collaboration by multiple experts has begun to take shape as an outgrowth of a project to design such facilities for scientific operations of the planned 2003 Mars Exploration Rover (MER) mission. The methodology could also be applicable to the design of military "situation rooms" and other facilities for terrestrial missions. It was recognized in this project that modern mission operations depend heavily upon the collaborative use of computers. It was further recognized that tests have shown that layout of a facility exerts a dramatic effect on the efficiency and endurance of the operations staff. The facility designs (for example, see figure) and the methodology developed during the project reflect this recognition. One element of the methodology is a metric, called effective capacity, that was created for use in evaluating proposed MER operational facilities and may also be useful for evaluating other collaboration spaces, including meeting rooms and military situation rooms. The effective capacity of a facility is defined as the number of people in the facility who can be meaningfully engaged in its operations. A person is considered to be meaningfully engaged if the person can (1) see, hear, and communicate with everyone else present; (2) see the material under discussion (typically data on a piece of paper, computer monitor, or projection screen); and (3) provide input to the product under development by the group. The effective capacity of a facility is less than the number of people that can physically fit in the facility. For example, a typical office that contains a desktop computer has an effective capacity of .4, while a small conference room that contains a projection screen has an effective capacity of around 10. Little or no benefit would be derived from allowing the number of persons in an operational facility to exceed its effective capacity: At best, the operations staff would be underutilized; at worst, operational performance would deteriorate. Elements of this methodology were applied to the design of three operations facilities for a series of rover field tests. These tests were observed by human-factors researchers and their conclusions are being used to refine and extend the methodology to be used in the final design of the MER operations facility. Further work is underway to evaluate the use of personal digital assistant (PDA) units as portable input interfaces and communication devices in future mission operations facilities. A PDA equipped for wireless communication and Ethernet, Bluetooth, or another networking technology would cost less than a complete computer system, and would enable a collaborator to communicate electronically with computers and with other collaborators while moving freely within the virtual environment created by a shared immersive graphical display.

Norris, Jeffrey↗

NASA NTRS1993

Lessons Learned--MO&DA at JPL

The basic questions addressed in this paper are how to avoid future surprise growth in Mission Operations and Data Analysis (MO&DA) costs, and how to minimize total MO&DA costs for planetary missions. The context of this paper and its conclusions is in the arena of JPL mission operations support. The fundamental conclusion is that there is no simple, single solution: the entire Project life-cycle must be addressed.

MO&DA↗

NASA NTRS1975

IUS/TUG Orbital Operations and Mission Support Study: Executive Summary - Volume 1

The space transportation system (STS) is discussed which will include a propulsive stage that is carried into low earth orbit by the space shuttle. Data were accumulated from the analyses of various stage concepts, operating modes, and projected missions (space tug systems studies, growth stage studies, engine studies, and critical area studies). The foundation formulated by these studies aided in establishing a tentative two-phase approach for the extension of the STS operating regime beyond the space shuttle including plane changes, higher orbits, geosynchronous orbits and beyond. The orbital operations study, was conducted to provide the generation and analysis of operational plans, requirement, and concepts for the utilization of these vehicles. Primary emphasis was placed on methods and techniques to provide a sound technical approach to operations at reduced cost for the STS mission period.

Source record↗

NASA NTRS2013

Model-based Systems Engineering: Creation and Implementation of Model Validation Rules for MOS 2.0

Model-based Systems Engineering (MBSE) is an emerging modeling application that is used to enhance the system development process. MBSE allows for the centralization of project and system information that would otherwise be stored in extraneous locations, yielding better communication, expedited document generation and increased knowledge capture. Based on MBSE concepts and the employment of the Systems Modeling Language (SysML), extremely large and complex systems can be modeled from conceptual design through all system lifecycles. The Operations Revitalization Initiative (OpsRev) seeks to leverage MBSE to modernize the aging Advanced Multi-Mission Operations Systems (AMMOS) into the Mission Operations System 2.0 (MOS 2.0). The MOS 2.0 will be delivered in a series of conceptual and design models and documents built using the modeling tool MagicDraw. To ensure model completeness and cohesiveness, it is imperative that the MOS 2.0 models adhere to the specifications, patterns and profiles of the Mission Service Architecture Framework, thus leading to the use of validation rules. This paper outlines the process by which validation rules are identified, designed, implemented and tested. Ultimately, these rules provide the ability to maintain model correctness and synchronization in a simple, quick and effective manner, thus allowing the continuation of project and system progress.

Model-based Systems Engineering (MBSE)↗

NASA NTRS2006

Stardust Entry: Landing and Population Hazards in Mission Planning and Operations

The 385 kg Stardust mission was launched on Feb 7, 1999 on a mission to collect samples from the tail of comet Wild 2 and from interplanetary space. Stardust returned to Earth in the early morning of January 15, 2006. The sample return capsule landed in the Utah Test and Training Range (UTTR) southwest of Salt Lake City. Because Stardust was landing on Earth, hazard analysis was required by the National Aeronautics and Space Administration, UTTR, and the Stardust Project to ensure the safe return of the landing capsule along with the safety of people, ground assets, and aircraft. This paper focuses on the requirements affecting safe return of the capsule and safety of people on the ground by investigating parameters such as probability of impacting on UTTR, casualty expectation, and probability of casualty. This paper introduces the methods for the calculation of these requirements and shows how they affected mission planning, site selection, and mission operations. By analyzing these requirements before and during entry it allowed for the selection of a robust landing point that met all of the requirements during the actual landing event.

Desai, P.↗