Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 901 records · Page 50

Contact Graph Routing

Contact Graph Routing (CGR) is a dynamic routing system that computes routes through a time-varying topology of scheduled communication contacts in a network based on the DTN (Delay-Tolerant Networking) architecture. It is designed to enable dynamic selection of data transmission routes in a space network based on DTN. This dynamic responsiveness in route computation should be significantly more effective and less expensive than static routing, increasing total data return while at the same time reducing mission operations cost and risk. The basic strategy of CGR is to take advantage of the fact that, since flight mission communication operations are planned in detail, the communication routes between any pair of bundle agents in a population of nodes that have all been informed of one another's plans can be inferred from those plans rather than discovered via dialogue (which is impractical over long one-way-light-time space links). Messages that convey this planning information are used to construct contact graphs (time-varying models of network connectivity) from which CGR automatically computes efficient routes for bundles. Automatic route selection increases the flexibility and resilience of the space network, simplifying cross-support and reducing mission management costs. Note that there are no routing tables in Contact Graph Routing. The best route for a bundle destined for a given node may routinely be different from the best route for a different bundle destined for the same node, depending on bundle priority, bundle expiration time, and changes in the current lengths of transmission queues for neighboring nodes; routes must be computed individually for each bundle, from the Bundle Protocol agent's current network connectivity model for the bundle s destination node (the contact graph). Clearly this places a premium on optimizing the implementation of the route computation algorithm. The scalability of CGR to very large networks remains a research topic. The information carried by CGR contact plan messages is useful not only for dynamic route computation, but also for the implementation of rate control, congestion forecasting, transmission episode initiation and termination, timeout interval computation, and retransmission timer suspension and resumption.

Burleigh, Scott C.↗

An operations and command systems for the extreme ultraviolet explorer

About 40% of the budget of a scientific spacecraft mission is usually consumed by Mission Operations & Data Analysis (MO&DA) with MO driving these costs. In the current practice, MO is separated from spacecraft design and comes in focus relatively late in the mission life cycle. As a result, spacecraft may be designed that are very difficult to operate. NASA centers have extensive MO expertise but often lessons learned in one mission are not exploited for other parallel or future missions. A significant reduction of MO costs is essential to ensure a continuing and growing access to space for the scientific community. We are addressing some of these issues with a highly automated payload operations and command system for an existing mission, the Extreme Ultraviolet Explorer (EUVE). EUVE is currently operated jointly by the Goddard Space Flight Center (GSFC), responsible for spacecraft operations, and the Center for Extreme Ultraviolet Astrophysics (CEA) of the University of California, Berkeley, which controls the telescopes and scientific instruments aboard the satellite. The new automated system is being developed by a team including personnel from the NASA Ames Research Center (ARC), the Jet Propulsion Laboratory (JPL) and the Center for EUV Astrophysics (CEA). An important goal of the project is to provide AI-based technology that can be easily operated by nonspecialists in AI. Another important goal is the reusability of the techniques for other missions. Models of the EUVE spacecraft need to be built both for planning/scheduling and for monitoring. In both cases, our modeling tools allow the assembly of a spacecraft model from separate sub-models of the various spacecraft subsystems. These sub-models are reusable; therefore, building mission operations systems for another small satellite mission will require choosing pre-existing modules, reparametrizing them with respect to the actual satellite telemetry information, and reassembling them in a new model. We briefly describe the EUVE mission and indicate why it is particularly suitable for the task. Then we briefly outline our current work in mission planning/scheduling and spacecraft and instrument health monitoring.

Muscettola, Nicola↗

A Software Architecture for Automating Operations Processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible outputs through interactive on-screen graphics.

mission↗

Lessons Learned During Implementation and Early Operations of the DS1 Beacon Monitor Experiment

A new approach to mission operations will be flight validated on NASA's New Millennium Program Deep Space One (DS1) mission which launched in October 1998. The Beacon Monitor Operations Technology is aimed at decreasing the total volume of downlinked engineering telemetry by reducing the frequency of downlink and the volume of data received per pass. Cost savings are achieved by reducing the amount of routine telemetry processing and analysis performed by ground staff. The technology is required for upcoming NASA missions to Pluto, Europa, and possibly some other missions. With beacon monitoring, the spacecraft will assess its own health and will transmit one of four beacon messages each representing a unique frequency tone to inform the ground how urgent it is to track the spacecraft for telemetry. If all conditions are nominal, the tone provides periodic assurance to ground personnel that the mission is proceeding as planned without having to receive and analyze downlinked telemetry. If there is a problem, the tone will indicate that tracking is required and the resulting telemetry will contain a concise summary of what has occurred since the last telemetry pass. The primary components of the technology are a tone monitoring technology, AI-based software for onboard engineering data summarization, and a ground response system. In addition, there is a ground visualization system for telemetry summaries. This paper includes a description of the Beacon monitor concept, the trade-offs with adapting that concept as a technology experiment, the current state of the resulting implementation on DS1, and our lessons learned during the initial checkout phase of the mission. Applicability to future missions is also included.

Sherwood, Rob↗

Automated rover sequence report generation

A web-based rover mission operations report and its various elements are described. The system was used for documentation of the Field Integrated Development and Operations (FIDO) rover May 2000 field test and results from the field test are provided. Implementation of automated sequence report generation for the operations report is explained in detail.

rovers mission operations↗

Integrated operations/payloads/fleet analysis. Volume 5: Mission, capture and operations analysis

The current baseline mission model consists of the DOD Option B prepared for space transportation system mission analysis and a NASA model prepared for the integrated operations /payloads/ fleet analysis. Changes from the previous mission model are discussed, and additional benefits of the reusable space shuttle system are identified. The methodology and assumptions used in the capture analysis are described, and satellite and launch vehicle traffic models for the current and low cost expendable launch vehicle systems and the reusable space shuttle system are presented. The areas of fleet sizing, limitations and abort modes, system ground support requirements, and ground support systems assessment are covered. Current and extended launch azimuth limitations used for both ETR and WTR are presented for the current and low cost expendable vehicles and also the reusable space shuttle system. The results of a survey of launch support capability for the launch vehicle fleets are reported.

Source record↗

Design and Certification of the Extravehicular Activity Mobility Unit (EMU) Water Processing Jumper

The Extravehicular Mobility Units (EMUs) onboard the International Space Station (ISS) experienced a failure due to cooling water contamination from biomass and corrosion byproducts forming solids around the EMU pump rotor. The coolant had no biocide and a low pH which induced biofilm growth and corrosion precipitates, respectively. NASA JSC was tasked with building hardware to clean the ionic, organic, and particulate load from the EMU coolant loop before and after Extravehicular Activity (EVAs). Based on a return sample of the EMU coolant loop, the chemical load was well understood, but there was not sufficient volume of the returned sample to analyze particulates. Through work with EMU specialists, chemists, (EVA) Mission Operations Directorate (MOD) representation, safety and mission assurance, astronaut crew, and team engineers, requirements were developed for the EMU Water Processing hardware (sometimes referred to as the Airlock Coolant Loop Recovery [A/L CLR] system). Those requirements ranged from the operable level of ionic, organic, and particulate load, interfaces to the EMU, maximum cycle time, operating pressure drop, flow rate, and temperature, leakage rates, and biocide levels for storage. Design work began in February 2005 and certification was completed in April 2005 to support a return to flight launch date of May 12, 2005. This paper will discuss the details of the design and certification of the EMU Water Processing hardware and its components

Peterson, Laurie J.↗

Constellation Architecture and System Margins Strategy

NASA's Constellation Program (CxP) is responsible for the definition, design, development, and operations of the flight, ground, and mission operations elements being developed by the United States for the human exploration of the Moon, Mars, and beyond. This paper provides an overview of the latest CxP technical architecture baseline, driving requirements, and reference missions for initial capability to fly to the International Space Station (ISS) and to the Moon. The results of the most recent design decisions and analyses supporting the architecture, including the Ares I, Ares V, Orion crew exploration vehicle, and the Altair lunar lander will be presented.

Muirhead, Brian↗

High Performance, Web-Based, Real-Time Telemetry Visualization for Deep Space Mission Support and Operations

The Jet Propulsion Laboratory’s Mission ControlSystems Section and Mobility and Robotic Systems Section havepartnered to developed a high-performance telemetry visualizationsystem, based on our mature, web-based, 3D visualizationsoftware technology, that provides mission trajectory designers,operations personnel and reconstruction analysts with a highlyaccurate, re-usable, multi-mission solution to interactively visualizeresults from Entry, Descent and Landing (EDL) simulations,real-time mission test beds, live telemetry streams during criticalmission events, such as landing, as well as post-event reconstructionanalysis. This work builds on previous mission visualizationsystems that we have deployed for a variety of flight missions andJPL organizations including NASA’s Mars Science Laboratory(MSL), NASA’S Low Density Supersonic Decelerator (LDSD),NASA’s Soil Moisture Active Passive (SMAP), JPL’s MoonRiseLunar sample return proposal. JPL’s mission design teams, JPL’sOffice of Naval Research tasks, and JPL’s Education and PublicOutreach Office.

Wenzel, Sean↗

STEReO 1.0 Overview

STEReO brings together several technologies in Unmanned Aircraft Systems (UAS) Traffic Management (UTM), Autonomy, Communications, Human Factors, and Domain Expertise & Tools, aimed at providing scalability and flexibility, as well as operational resiliency to dynamic changes during a disaster event. Some of the concepts STEReO explores are: collaborative tools to ingest remote sensing information and distribute a common mission operating picture, apply ad-hoc communication networks to facilitate timely information sharing and communication of changes, vehicle-to-vehicle and onboard autonomy technologies ensure the safety and resiliency of operations, and apply NASA’s UAS traffic management system (UTM) as a public safety UAS Service Supplier (USS) to access and coordinate use of the airspace by both manned and unmanned operations. The potential benefits of STEReO include: standardized, cross-platform communication means increased interoperability and ease of cooperation/collaboration, increased situation awareness and common operating picture allow for earlier detection and decision making, and scalable to size and complexity of environment, operations, and mission objectives. This presentation gives an informational overview of the STEReO project to attendees of the System Wide Safety (SWS) Wildland Firefighting Operations Workshop.

emergency response operations↗

Small Business Innovation Research, Post-Phase II Opportunity Assessment

This report outlines current Small Business Innovation Research (SBIR) Post-Phase II opportunity contract award results for the SBIR technology program from 2007 to 2011 for NASA's Aeronautics Research Mission Directorate (ARMD), Human Exploration and Operations Mission Directorate (HEOMD), Science Mission Directorate (SMD), and Space Technology Mission Directorate (STMD). The report provides guidelines for incorporating SBIR technology into NASA programs and projects and provides a quantitative overview of the post-Phase II award patterns that correspond with each mission directorate at NASA Glenn Research Center (GRC). In recent years, one of NASA's goals has been to not only transfer SBIR technologies to commercial industries, but to ensure that NASA mission directorates incorporate SBIR technologies into their program and project activities. Before incorporating technologies into MD programs, it is important to understand each mission directorate structure because each directorate has different objectives and needs. The directorate program structures follow.

infusion process↗

Mission management aircraft operations manual

This manual prescribes the NASA mission management aircraft program and provides policies and criteria for the safe and economical operation, maintenance, and inspection of NASA mission management aircraft. The operation of NASA mission management aircraft is based on the concept that safety has the highest priority. Operations involving unwarranted risks will not be tolerated. NASA mission management aircraft will be designated by the Associate Administrator for Management Systems and Facilities. NASA mission management aircraft are public aircraft as defined by the Federal Aviation Act of 1958. Maintenance standards, as a minimum, will meet those required for retention of Federal Aviation Administration (FAA) airworthiness certification. Federal Aviation Regulation Part 91, Subparts A and B, will apply except when requirements of this manual are more restrictive.

Source record↗

Challenges of Operations in a Dynamic Environment: A Three-Year Perspective of SAGE III

The Stratospheric Aerosol and Gas Experiment~III on the International Space Station (SAGE III/ISS) was delivered to the International Space Station (ISS) on 23 February 2017. The SAGE III/ISS payload was robotically installed external to the ISS and began acquiring science measurements on 17 March 2017. The SAGE III/ISS instrument retrieves vertical profiles of atmospheric ozone, multi-wavelength aerosol extinctions, and other gaseous species. This paper will focus on the improvements made to the operations of the SAGE III/ISS payload. A key focus of the operations team following commissioning was to create robust tools that aide in the operations of the payload. A close collaboration with the SAGE III/ISS ground systems team allowed for the development of web-based tools to continuously monitor the health of the instrument. The mission operations team also worked with the SAGE III/ISS science team to gain a better sense of how the instrument works to maximize the quality and quantity of the science data collected. Another unique aspect of the SAGE III/ISS payload, that will be discussed, is the challenges of operating a hosted payload on the ISS; an active platform that has frequent attitude maneuvers, dockings, and EVA's. This active environment increases the need for the SAGE III/ISS operations team command the payload. Through coordination and teamwork, SAGE III/ISS mission has developed an operations team that has successfully managed the instrument around ISS activities and recovered from multiple instrument upsets. This has led the SAGE III/ISS payload to successfully surpass the acquisition metrics set forth prior to launch, allowing for the continued contribution to studying the atmospheric composition of the stratosphere and how it plays a role in earth’s climate.

SAGE III↗

A Year of Progress: NASA's Space Launch System Approaches Critical Design Review

NASA's Space Launch System (SLS) made significant progress on the manufacturing floor and on the test stand in 2014 and positioned itself for a successful Critical Design Review in mid-2015. SLS, the world's only exploration-class heavy lift rocket, has the capability to dramatically increase the mass and volume of human and robotic exploration. Additionally, it will decrease overall mission risk, increase safety, and simplify ground and mission operations - all significant considerations for crewed missions and unique high-value national payloads. Development now is focused on configuration with 70 metric tons (t) of payload to low Earth orbit (LEO), more than double the payload of the retired Space Shuttle program or current operational vehicles. This "Block 1" design will launch NASA's Orion Multi-Purpose Crew Vehicle (MPCV) on an uncrewed flight beyond the Moon and back and the first crewed flight around the Moon. The current design has a direct evolutionary path to a vehicle with a 130t lift capability that offers even more flexibility to reduce planetary trip times, simplify payload design cycles, and provide new capabilities such as planetary sample returns. Every major element of SLS has successfully completed its Critical Design Review and now has hardware in production or testing. In fact, the SLS MPCV-to-Stage-Adapter (MSA) flew successfully on the Exploration Flight Test (EFT) 1 launch of a Delta IV and Orion spacecraft in December 2014. The SLS Program is currently working toward vehicle Critical Design Review in mid-2015. This paper will discuss these and other technical and programmatic successes and challenges over the past year and provide a preview of work ahead before the first flight of this new capability.

Askins, Bruce↗

Leveraging middleware-based infrastructure for remote exploration

This paper describes middleware systems developed at JPL, shows how leveraging middleware implementation strategies can facilitate building a mission operations system for managing multiple interacting missions on Mars, and proposes an approach to implementing demonstrations as part of a roadmap providing progressively more intelligent remote exploration.

middleware↗

Operations Challenges in a Dynamic Environment: A Three-Year Perspective of SAGE III

The Stratospheric Aerosol and Gas Experiment III on the International Space Station (SAGE III/ISS) was delivered to the International Space Station (ISS) on 23 February 2017. The SAGE III/ISS payload was robotically installed external to the ISS and began acquiring science measurements on 17 March 2017. The SAGE III/ISS instrument retrieves vertical profiles of atmospheric ozone, multi-wavelength aerosol extinctions, and other gaseous species. This paper will focus on the improvements made to the operations of the SAGE III/ISS payload. A key focus of the operations team following commissioning was to create robust tools that aid in the operations of the payload. A close collaboration with the SAGE III/ISS ground systems team allowed for the development of web-based tools to continuously monitor the health of the payload. The mission operations team also worked with the SAGE III/ISS science team to gain a better sense of how the instrument works to maximize the quality and quantity of the science data collected. Another unique aspect of the SAGE III/ISS payload, that will be discussed, is the challenges of operating a hosted payload on the ISS; an active platform that has frequent attitude maneuvers, dockings, and EVAs. This active environment increases the need for the SAGE III/ISS operations team command to the payload. Through coordination and teamwork, SAGE III/ISS mission has developed an operations team, tool, and procedures that have successfully managed the payload around ISS activities and recovered from multiple instrument upsets. This has led the SAGE III/ISS payload to successfully surpass the acquisition metrics set forth prior to launch, allowing for the continued contribution to studying the atmospheric composition of the stratosphere and how it plays a role in Earth’s climate.

SAGE III↗

A MOS for all seasons

From a systems perspective, this paper examines the challenges of a single system to support multiple JPL space exploration missions and the need for unitary responsibility for the system. The focus is a Mission Operations System (MOS), which is effectively a mission management organization with direct authority over data system operations, command sequencing, flight operations control, data management, trajectory determination, telemetry and data acquisition, and spacecraft analysis. Stratagems for training and the approach to processes, procedures, and interfaces to facilitate the transition from the present situation to a truly multimission operational environment are developed. The outcome is a paradigm for a MOS that is achievable, that can effectively support multiple projects, and that can take advantage of technological changes without perturbing the entire system.

Bryant, Larry↗