Search NASA⌕ Search

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.

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

At least 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

NASA Mission Operations Directorate Preparations for the COTS Visiting Vehicles

With the retirement of the Space Shuttle looming, a series of new spacecraft is under development to assist in providing for the growing logistical needs of the International Space Station (ISS). Two of these vehicles are being built under a NASA initiative known as the Commercial Orbital Transportation Services (COTS) program. These visiting vehicles ; Space X s Dragon and Orbital Science Corporation s Cygnus , are to be domestically produced in the United States and designed to add to the capabilities of the Russian Progress and Soyuz workhorses, the European Automated Transfer Vehicle (ATV) and the Japanese H-2 Transfer Vehicle (HTV). Most of what is known about the COTS program has focused on the work of Orbital and SpaceX in designing, building, and testing their respective launch and cargo vehicles. However, there is also a team within the Mission Operations Directorate (MOD) at NASA s Johnson Space Center working with their operational counterparts in these companies to provide operational safety oversight and mission assurance via the development of operational scenarios and products needed for these missions. Ensuring that the operational aspect is addressed for the initial demonstration flights of these vehicles is the topic of this paper. Integrating Dragon and Cygnus into the ISS operational environment has posed a unique challenge to NASA and their partner companies. This is due in part to the short time span of the COTS program, as measured from initial contract award until first launch, as well as other factors that will be explored in the text. Operational scenarios and products developed for each COTS vehicle will be discussed based on the following categories: timelines, on-orbit checkout, ground documentation, crew procedures, software updates and training materials. Also addressed is an outline of the commonalities associated with the operations for each vehicle. It is the intent of the authors to provide their audience with a better understanding of the mission assurance that MOD brings to commercial ventures to the ISS

Shull, Sarah A.↗
NASA NTRS2008

A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

MOS↗
NASA NTRS1992

Mission Operations Report (MOR) for the Solar, Anomalous, and Magnetosphere Particle Explorer (SAMPEX)

MISSION OPERATIONS REPORTS are published for use by NASA senior management, as required by NASA Headquarters Management Instruction HQMI 8610. lC, effective November 26, 1991. The purpose of these reports is to provide a documentation system that represents an internal discipline to establish critical discriminators selected in advance to measure mission accomplishment, provide a formal written assessment of mission accomplishment, and provide an accountability of technical achievement. Prelaunch reports are prepared and issued for each flight project just prior to launch. Following launch, updating (Post Launch) reports are issued to provide mission status and progress in meeting mission objectives. Primary distribution of these reports is intended for personnel having program/project management responsibilities.

Source record↗
NASA NTRS2019

Mission Operations Working Group (MOWG) Report to the Aura Science Team

This presentation provides mission operations status for the Earth Observing System (EOS) Aura satellite to the Aura Science Team community. It is a summary of the splinter meeting held between the Aura Flight Operations Team (FOT) and the Instrument Operations Teams (IOT). The material covers highlights of activities, any significant issues or concerns, and future plans of the mission and instruments.

Fisher, Dominic M.↗
NASA NTRS1992

Shuttle Imaging Radar-C mission operations - Technology test bed for Earth Observing System synthetic aperture radar

The mission operations for the Space Radar Lab (SRL), particularly in the areas of real-time replanning and science activity coordination, are presented. The two main components of SRL are the Shuttle Imaging Radar-C and the X-Band Synthetic Aperture Radar. The Earth Observing System SAR will be a multispectral, multipolarization radar satellite that will provide information over an entire decade, permitting scientists to monitor large-scale changes in the earth's environment over a long period of time.

Trimble, J. P.↗
NASA NTRS2010

Spitzer Mission Operation System Planning for IRAC Warm-Instrument Characterization

This paper will describe how the Spitzer Mission Operations System planned and executed the characterization phase between Spitzer's cryogenic mission and its warm mission. To the largest extend possible, the execution of this phase was done with existing processing and procedures. The modifications that were made were in response to the differences of the characterization phase compared to normal phases before and after. The primary two categories of difference are: unknown date of execution due to uncertainty of knowledge of the date of helium depletion, and the short cycle time for data analysis and re-planning during execution. In addition, all of the planning and design had to be done in parallel with normal operations, and we had to transition smoothly back to normal operations following the transition. This paper will also describe the re-planning we had to do following an anomaly discovered in the first days after helium depletion.

IWIC↗
NASA NTRS2003

Agent-Supported Mission Operations Teamwork

This slide presentation reviews the development of software agents to support of mission operations teamwork. The goals of the work was to make automation by agents easy to use, supervise and direct, manage information and communication to decrease distraction, interruptions, workload and errors, reduce mission impact of off-nominal situations and increase morale and decrease turnover. The accomplishments or the project are: 1. Collaborative agents - mixed initiative and creation of instructions for mediating agent 2. Methods for prototyping, evaluating and evolving socio-technical systems 3. Technology infusion: teamwork tools in mISSIons 4. Demonstrations in simulation testbed An example of the use of agent is given, the use of an agent to monitor a N2 tank leak. An incomplete instruction to the agent is handled with mediating assistants, or Intelligent Briefing and Response Assistant (IBRA). The IBRA Engine also watches data stream for triggers and executes Act-Whenever actions. There is also a Briefing and Response Instruction (BRI) which is easy for a discipline specialist to create through a BRI editor.

Malin, Jane T.↗
NASA NTRS1975

Mission operations and data systems

A communications system for performing the basic functions of mission operations, orbit and attitude determination, and data processing is described. A block diagram is provided to show the relationships of these functions with the spacecraft in orbit and the experiments to be conducted on board the spacecraft. Specific areas of application are discussed as follows: (1) software operating systems for the ATS-F satellite testing and ground support, (2) inversion of the RAE-1 satellite (Explorer 38 satellite) in orbit, (3) ALSEP differential Doppler tracking, (4) minitrack calibration using satellite data, (5) angles-only orbit extraction, and (6) image processing system performance prediction and product quality evaluation techniques. Block diagrams of the various systems are provided to show the steps involved in the operations.

Source record↗
NASA NTRS2012

Designing Mission Operations for the Gravity Recovery and Interior Laboratory Mission

The Gravity Recovery and Interior Laboratory (GRAIL) mission has placed two orbiters in a low altitude polar orbit around the moon to study its internal structure. GRAIL mission to the Moon offered unique challenges to operatiotn: (1) operate twin-orbiters in parallel, (2) numerous maneuvers, (3) short, compact mission with six unique phases, and (4) detailed contingency planning required.

Orbital Period Reduction (OPR)↗
NASA NTRSDate not supplied

Real-Time Science Decisioning During High Tempo-High Intensity Mission Operations and the Role of Analogs

Introduction: NASA’s VIPER mission presents a unique operational paradigm within the history of robotic spaceflight. The proximity of the Moon to the Earth and the terrain elements (surface characteristics, light/shadow dynamics, communication links) of the lunar South Polar landing site create unprecedented operational conditions between these two planetary bodies. Apollo era lunar science and exploration included humans in situ to operate instruments and assimilate observational inputs in real-time. Previous lunar orbital missions have worked to operational timescales, e.g., decisional timelines and communication exchanges, that were weeks in length. Mars rover missions have worked to operational timescales, e.g., decisional timelines and communication exchanges between Mars and Earth, that were hours, days, and weeks in length. In the case of the VIPER mission, our operational decisioning for rover driving and instrument commanding will be compressed to minute-scale timeframes. These operational conditions directly impact the manner and speed with which the VIPER Science Team (VST) is required to synthesize and analyze data and produce timely science-driven decisions throughout surface mission operations. The VST shall provide mission enhancing scientific input to guide rover traverse planning and drill site confirmation and selection throughout surface operations. Further, the VST input will be of vital importance to the mission’s ability to maximize science return and to meet broader NASA objectives for future lunar in-situ resource utilization (ISRU)and exploration activities. The VST co-located in the Mission Science Center (MSC) will be responsive to the tactical operational cadence of the Mission Operations Center (MOC) and will provide further strategic and Long-Term Planning (LTP) guidance to the mission. The VIPER Science Operations & Integration(SO&I)team has developed an architecture that is focused on the infusion of science-decisioning into the operational framework and execution cadence of VIPER. NASA analog research has played a significant role in the construction of the VIPER science operations systems. As an example, the SO&I team has led analog missions that have focused on bringing together expertise in the sciences (natural, applied and social) and in operations in service of learning how to build and hold together interdisciplinary work environments and what tools are needed to support high tempo, high intensity integrated decisioning. These experiences have provided an essential foundation of knowledge to the VIPER team. Those analogs that specifically influenced the VIPER science operations construct were identified through a process of comparative analysis to prioritize those that offered relevance in whole or in part, and those that did not. The analog research output that provided extensibility to the VIPER science operations architecture included remote teams of humans and robots in cooperation (synchronous and asynchronous) with simulated earthbound systems, engineering and science teams, and the integrated assembly of tools that supported scientific analysis and data synthesis and provided infrastructure for the remote testing framework. Analogs which included real-time data monitoring, synthesis, visualization and access in a democratized and operationalized manner were of particular interest to the development of the VIPER MSC toolset both in terms of the technology and the processes used to develop the supporting infrastructure. We anticipate that each subsequent mission to the lunar south pole, whether with robots or humans, will be able to optimize science and exploration return by evolving strategies to infuse real-time collaborative science-decisioning. Furthermore, these efforts will result in a foundation for science operations development in support of human-robotic exploration of deep space and Mars. NASA analogs can continue to provide the opportunity to prepare, test and iterate on the operational concepts and tools that will support these ever-expanding space exploration efforts. Our presentation will include an overview of the VIPER Science Operations & Integration development process and specifics on what aspects of analog research have had a significant impact on our work systems.

D S S Lim↗
NASA NTRS2001

Design-based mission operation

This paper describes the four phases of the VML addressing a major challenge per phase, mission model framework, virtual phototyping, agent-based mission system integration, and virtual mission operation.

Virtual Mission VML↗
NASA NTRS2000

JPL's Multi-Mission Operations Strategy for the Next Decade

This paper will present an overview of the TMOD Standard Services to provide context to the proposed approach for TMOD operations. A presentation of TMOD's Operations Concept extended to the Mission Services level will be provided which in turn will be mapped to the operational needs of Mission Service's.

Multi-Mission Operations JPL Operation Strategy↗
NASA NTRS2014

Using AUTORAD for Cassini File Uplinks: Incorporating Automated Commanding into Mission Operations

As the Cassini spacecraft embarked on the Solstice Mission in October 2010, the flight operations team faced a significant challenge in planning and executing the continuing tour of the Saturnian system. Faced with budget cuts that reduced the science and engineering staff by over a third in size, new and streamlined processes had to be developed to allow the Cassini mission to maintain a high level of science data return with a lower amount of available resources while still minimizing the risk. Automation was deemed an important key in enabling mission operations with reduced workforce and the Cassini flight team has made this goal a priority for the Solstice Mission. The operations team learned about a utility called AUTORAD which would give the flight operations team the ability to program selected command files for radiation up to seven days in advance and help minimize the need for off-shift support that could deplete available staffing during the prime shift hours. This paper will describe how AUTORAD is being utilized by the Cassini flight operations team and the processes that were developed or modified to ensure that proper oversight and verification is maintained in the generation and execution of radiated command files.

Goo, Sherwin↗
NASA NTRS1994

Engineering Analysis Subsystem Environment for Spacecraft Engineering Subsystem Mission Operations

The Engineering Analysis Subsystem Environment (EASE) prototype is a collection of computer programs on networked workstations providing a multimission, multisubsystem environment that enables the operation of several spacecraft simultaneously with fewer analysts. Through the use of automated tools, graphical data visualization and information management, EASE has achieved an increase in mission operations productivity. Recently, a database, a trending tool, and a power sequence expansion tool have been added to EASE. This paper discusses these enhancements and provides an update of the operation experience with the realtime Galileo telemetry data.

EASE↗