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 433 records · Page 24
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Automating planetary mission operations

In this paper, we describe the elements of a semi-autonomous system designed to provide instrument health, pointing, and data in a cost effective fashion.

automation parallel processing↗
NASA NTRS2006

Asynchronous Message Service for Deep Space Mission Operations

AMS is in early stages of standardization. a) CCSDS "white book" (Proposed Standard) has been published. b) A single implementation has been developed and is being tested. No major obstacles encountered so far. a) Protocol has changed since original concept paper, but not radically. b) Design concepts seem to be sound. AMS capabilities seem to be broadly applicable. a) On-board, proximity, and deep-space communications for spacecraft. b) Suitable underlying messaging protocol for proposed CCSDS Spacecraft Monitor and Control protocols. c) Terrestrial applications designed for operation over a message bus. AMS Working Group within CCSDS is on schedule, so far.

asynchronous message exchanges↗
NASA NTRS2009

OTF Proof of Concept: CCSDS Mission Operations Alert Services

Conclusions: Use of multiple vendor frameworks within a component creates thread lockups and fragility conflicts over the control of the main thread. Avoid closed vendor messaging frameworks. The MAL layer does isolate the data elements from the messaging framework but application work dispatch is heavily dominated by the framework chosen. API Language is a major factor in implementation. Message APIs with timeouts seem unavoidable in some environments (GUI). Language environment needs to support callbacks (or threads) from the messaging framework to deal with pub/sub management messages and status. Statusing of application communications demand a local broker agent per physical system or else the use of the AMSstyle registrar heartbeat.

Reynolds, Walt↗
NASA NTRS2009

CCSDS Mission Operations Action Service Core Capabilities

This slide presentation reviews the operations concepts of the command (action) services. Since the consequences of sending the wrong command are unacceptable, the command system provides a collaborative and distributed work environment for flight controllers and operators. The system prescribes a review and approval process where each command is viewed by other individuals before being sent to the vehicle. The action service needs additional capabilities to support he operations concepts of manned space flight. These are : (1) Action Service methods (2) Action attributes (3) Action parameter/argument attributes (4 ) Support for dynamically maintained action data. (5) Publish subscri be capabilities.

Reynolds, Walter F.↗
NASA NTRS2009

OTF Mission Operations Prototype Status

Reports on the progress of the JSC/OTF prototype of a CCSDS SM&C protocol based communications link between two space flight operations control centers. Varied implementations using software architectures from current web enterprise venues are presented. The AMS protocol (CCSDS Blue Book standard 735.1) was used for messaging and link communications.

Reynolds, Walter F.↗
NASA NTRS2010

CCSDS SM and C Mission Operations Interoperability Prototype

This slide presentation reviews the prototype of the Spacecraft Monitor and Control (SM&C) Operations for interoperability among other space agencies. This particular prototype uses the German Space Agency (DLR) to test the ideas for interagency coordination.

Lucord, Steven A.↗