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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

An agent-oriented approach to automated mission operations

As we plan for the next generation of Mission Operations Control Center (MOCC) systems, there are many opportunities for the increased utilization of innovative knowledge-based technologies. The innovative technology discussed is an advanced use of agent-oriented approaches to the automation of mission operations. The paper presents an overview of this technology and discusses applied operational scenarios currently being investigated and prototyped. A major focus of the current work is the development of a simple user mechanism that would empower operations staff members to create, in real time, software agents to assist them in common, labor intensive operations tasks. These operational tasks would include: handling routine data and information management functions; amplifying the capabilities of a spacecraft analyst/operator to rapidly identify, analyze, and correct spacecraft anomalies by correlating complex data/information sets and filtering error messages; improving routine monitoring and trend analysis by detecting common failure signatures; and serving as a sentinel for spacecraft changes during critical maneuvers enhancing the system's capabilities to support nonroutine operational conditions with minimum additional staff. An agent-based testbed is under development. This testbed will allow us to: (1) more clearly understand the intricacies of applying agent-based technology in support of the advanced automation of mission operations and (2) access the full set of benefits that can be realized by the proper application of agent-oriented technology in a mission operations environment. The testbed under development addresses some of the data management and report generation functions for the Explorer Platform (EP)/Extreme UltraViolet Explorer (EUVE) Flight Operations Team (FOT). We present an overview of agent-oriented technology and a detailed report on the operation's concept for the testbed.

Truszkowski, Walt↗
NASA NTRS2012

Mission Operations Assurance

Integrate the mission operations assurance function into the flight team providing: (1) value added support in identifying, mitigating, and communicating the project's risks and, (2) being an essential member of the team during the test activities, training exercises and critical flight operations.

project tracking↗
NASA NTRS1992

Mission operations technology

Developments in the area of spacecraft operations are examined that can be utilized in mission and spacecraft designs to enhance the efficiency of planetary and other mission operations. The technology enhancements described address four major systems: the spacecraft, the tracking and data system, the spaceflight operations center, and the flight projects. Specific technological advances are detailed in the areas of telemetry monitoring and fault analysis, scheduling systems, and scientific data analysis. The Spacecraft Health Automated Reasoning Prototype and the Engineering Analysis Subsystem Environment can provide real-time monitoring and analysis with limited workforce resources. The Multimission Automation for Real-time Verification of Spacecraft Engineering Link, the Operation Mission Planner, and the Sky Image Classification and Archiving Tool are other examples of systems developed by NASA that enhance operations technology by reducing the need for human input.

Varsi, Giulio↗
NASA NTRS2009

Prototype Interoperability Document between NASA-JSC and DLR-GSOC Describing the CCSDS SM and C Mission Operations Prototype

The purpose of the PROTOTYPE INTEROPERABILITY DOCUMENT is to document the design and interfaces for the service providers and consumers of a Mission Operations prototype between JSC-OTF and DLR-GSOC. The primary goal is to test the interoperability sections of the CCSDS Spacecraft Monitor & Control (SM&C) Mission Operations (MO) specifications between both control centers. An additional goal is to provide feedback to the Spacecraft Monitor and Control (SM&C) working group through the Review Item Disposition (RID) process. This Prototype is considered a proof of concept and should increase the knowledge base of the CCSDS SM&C Mission Operations standards. No operational capabilities will be provided. The CCSDS Mission Operations (MO) initiative was previously called Spacecraft Monitor and Control (SM&C). The specifications have been renamed to better reflect the scope and overall objectives. The working group retains the name Spacecraft Monitor and Control working group and is under the Mission Operations and Information Services Area (MOIMS) of CCSDS. This document will refer to the specifications as SM&C Mission Operations, Mission Operations or just MO.

Lucord, Steve A.↗
NASA NTRS2007

A-Train Mission Operations Working Group: CALIPSO Mission Status

This series of viewgraphs presents an introduction to the status of the Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observation (CALIPSO),lessons learned during CALIPSO inclination maneuvers, the planning for CALIPSO's inclination maneuver to take place in 2009, examines a decision whether to precess or not, the plans to change CALIPSO's pitch, and the plans to change CALIPSO's pitch from the viewpoint of the payload.

Cisewski, Michael S.↗
NASA NTRS2009

OTF CCSDS Mission Operations Prototype Parameter Service. Phase I: Exit Presentation

This slide presentation reviews the prototype of phase 1 of the parameter service design of the CCSDS mission operations. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement the Parameter Service (2) Demonstrate interoperability between Houston MCC and a CCSDS Mission Operations compliant mission operations center (3) Utilize Mission Operations Common Architecture. THe parameter service design, interfaces, and structures are described.

Reynolds, Walter F.↗
NASA NTRS2006

Mission Operations of Earth Observing-1 with Onboard Autonomy

Space mission operations are extremely labor and knowledge-intensive and are driven by the ground and flight systems. Inclusion of an autonomy capability can have dramatic effects on mission operations. We describe the past mission operations flow for the Earth Observing-1 (EO-1) spacecraft as well as the more autonomous operations to which we transferred as part of the Autonomous Sciencecraft Experiment (ASE).

hyperspectral images↗
NASA NTRS1987

The Mission Operations Planning Assistant

The Mission Operations Planning Assistant (MOPA) is a knowledge-based system developed to support the planning and scheduling of instrument activities on the Upper Atmospheric Research Satellite (UARS). The MOPA system represents and maintains instrument plans at two levels of abstraction in order to keep plans comprehensible to both UARS Principal Investigators and Command Management personnel. The hierarchical representation of plans also allows MOPA to automatically create detailed instrument activity plans from which spacecraft command loads may be generated. The MOPA system was developed on a Symbolics 3640 computer using the ZetaLisp and ART languages. MOPA's features include a textual and graphical interface for plan inspection and modification, recognition of instrument operational constraint violations during the planning process, and consistency maintenance between the different planning levels. This paper describes the current MOPA system.

Schuetzle, James G.↗
NASA NTRS1987

The mission operations planning assistant

The Mission Operations Planning Assistant (MOPA) is a knowledge-based system developed to support the planning and scheduling of instrument activities on the Upper Atmospheric Research Satellite (UARS). The MOPA system represents and maintains instrument plans at two levels of abstraction in order to keep plans comprehensible to both UARS Prinicpal Investigators and Command Management personnel. The hierarchical representation of plans also allows MOPA to automatically create detailed instrument activity plans from which spacecraft command loads may be generated. The MOPA system was developed on a Symbolics 3640 computer using the ZETALISP and ART languages. MOPA's features include a textual and graphical interface for plan inspection and modification, recognition of instrument operational constraint violations during the planning process, and consistency maintenance between the different planning levels. This paper describes the current MOPA system.

Schuetzle, James G.↗
NASA NTRS1994

Mission Operations for Mars Observer

Mission operations for the Mars Observer project were patterned after the low-cost approach proposed under the Planetary Observer program of the early 1980s.

Mars Observer project mapping spacecraft design sc↗
NASA NTRS2005

Middleware Evaluation and Benchmarking for Use in Mission Operations Centers

Middleware technologies have been promoted as timesaving, cost-cutting alternatives to the point-to-point communication used in traditional mission operations systems. However, missions have been slow to adopt the new technology. The lack of existing middleware-based missions has given rise to uncertainty about middleware's ability to perform in an operational setting. Most mission architects are also unfamiliar with the technology and do not know the benefits and detriments to architectural choices - or even what choices are available. We will present the findings of a study that evaluated several middleware options specifically for use in a mission operations system. We will address some common misconceptions regarding the applicability of middleware-based architectures, and we will identify the design decisions and tradeoffs that must be made when choosing a middleware solution. The Middleware Comparison and Benchmark Study was conducted at NASA Goddard Space Flight Center to comprehensively evaluate candidate middleware products, compare and contrast the performance of middleware solutions with the traditional point- to-point socket approach, and assess data delivery and reliability strategies. The study focused on requirements of the Global Precipitation Measurement (GPM) mission, validating the potential use of middleware in the GPM mission ground system. The study was jointly funded by GPM and the Goddard Mission Services Evolution Center (GMSEC), a virtual organization for providing mission enabling solutions and promoting the use of appropriate new technologies for mission support. The study was broken into two phases. To perform the generic middleware benchmarking and performance analysis, a network was created with data producers and consumers passing data between themselves. The benchmark monitored the delay, throughput, and reliability of the data as the characteristics were changed. Measurements were taken under a variety of topologies, data demands, and data characteristics, using several middleware products. All results were compared to systems using traditional point-to-point socket communication. By comparing performance results under Merent settings, inferences could be made about each middleware's ability to meet certain requirements of the GPM mission. The second phase simulated a middleware-based mission operations center. Actual mission support tools were either used or simulated to create real world demands on the middleware. Network and computer demands were watched closely to verify that no specific idiosyncrasies of mission operations activities would prove unsupportable by the middleware. In our presentation, we will address some commonly accepted misconceptions concerning middleware in mission support architectures. Specifically, we will focus on the perception that middleware solutions are too slow or impose too much overhead for real-time mission operations, and that middleware solutions are too expensive for small

Antonucci, Rob↗
NASA NTRS1990

Small Explorer project: Submillimeter Wave Astronomy Satellite (SWAS). Mission operations and data analysis plan

The Mission Operations and Data Analysis Plan is presented for the Submillimeter Wave Astronomy Satellite (SWAS) Project. It defines organizational responsibilities, discusses target selection and navigation, specifies instrument command and data requirements, defines data reduction and analysis hardware and software requirements, and discusses mission operations center staffing requirements.

Melnick, Gary J.↗
NASA NTRS2007

Integrating Automation into a Multi-Mission Operations Center

NASA Goddard Space Flight Center's Space Science Mission Operations (SSMO) Project is currently tackling the challenge of minimizing ground operations costs for multiple satellites that have surpassed their prime mission phase and are well into extended mission. These missions are being reengineered into a multi-mission operations center built around modern information technologies and a common ground system infrastructure. The effort began with the integration of four SMEX missions into a similar architecture that provides command and control capabilities and demonstrates fleet automation and control concepts as a pathfinder for additional mission integrations. The reengineered ground system, called the Multi-Mission Operations Center (MMOC), is now undergoing a transformation to support other SSMO missions, which include SOHO, Wind, and ACE. This paper presents the automation principles and lessons learned to date for integrating automation into an existing operations environment for multiple satellites.

Surka, Derek M.↗
NASA NTRS1993

Systems engineering and integration processes involved with manned mission operations

This paper will discuss three mission operations functions that are illustrative of the key principles of operations SE&I and of the processes and products involved. The flight systems process was selected to illustrate the role of the systems product line in developing the depth and cross disciplinary skills needed for SE&I and providing the foundation for dialogue between participating elements. FDDD was selected to illustrate the need for a structured process to assure that SE&I provides complete and accurate results that consistently support program needs. The flight director's role in mission operations was selected to illustrate the complexity of the risk/gain tradeoffs involved in the development of the flight techniques and flight rules process as well as the absolute importance of the leadership role in developing the technical, operational, and political trades.

Kranz, Eugene F.↗
NASA NTRS2008

Ensemble: an Architecture for Mission-Operations Software

Ensemble is the name of an open architecture for, and a methodology for the development of, spacecraft mission operations software. Ensemble is also potentially applicable to the development of non-spacecraft mission-operations- type software. Ensemble capitalizes on the strengths of the open-source Eclipse software and its architecture to address several issues that have arisen repeatedly in the development of mission-operations software: Heretofore, mission-operations application programs have been developed in disparate programming environments and integrated during the final stages of development of missions. The programs have been poorly integrated, and it has been costly to develop, test, and deploy them. Users of each program have been forced to interact with several different graphical user interfaces (GUIs). Also, the strategy typically used in integrating the programs has yielded serial chains of operational software tools of such a nature that during use of a given tool, it has not been possible to gain access to the capabilities afforded by other tools. In contrast, the Ensemble approach offers a low-risk path towards tighter integration of mission-operations software tools.

Norris, Jeffrey↗
NASA NTRS1993

Astro-D Prelaunch Mission Operation Report (MOR)

The Prelaunch Mission Operation Report for the Astro-D mission is enclosed for your information. Astro-D is a Japanese-led program involving the United States as a participating partner. The Japanese Institute of Space and Astronautical Science (ISAS) provides overall program management, the launch vehicle, the spacecraft, and two Gas Scintillation Imaging System detectors. NASA is providing four nested, thin-foil, grazing-incidence telescope mirrors and two X-ray charged-coupled device solid-state detectors. NASA also provides telemetry tracking support using Deep Space Network ground stations. In return for its scientific instrument contribution, the U.S. will receive 15 percent of the observing time and will share an additional 25 percent for collaborative U.S./Japan scientific investigations. Launch is scheduled for mid- February 1993 from the ISAS launch center near Kagoshima in southern Japan. This MOR: (a) describes the NASA objectives for the Astro-D mission; (b) provides brief descriptions of the spacecraft and its scientific instruments; (c) provides a chronology of launch and deployment; and (d) describes the ground operation elements that support the mission. .

Source record↗
NASA NTRS1995

The Mission Operations Directorate's International Space Station Alpha Hardware Familiarization Role

The National Aeronautics and Space Administration's Mission Operation Directorate's (MOD) On-Orbit Maintenance Operations Mission Controllers are participating in space station hardware tests and demonstrations in multiple neutral buoyancy facilities. This is part of the controllers' hardware familiarization world in preparation to support the astronauts in the operation and maintenance of the hardware. This paper describes the larger context of Mission Controller hardware familiarization with specifics of participation in the Boeing neutral buoyancy tests. Also covered is what participation has occurred in the past and future plans.

Zingrebe, Kenneth W., II↗