Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission operations system”

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 91 records · Page 5

Mission operations concepts for Earth Observing System (EOS)

Mission operation concepts are described which are being used to evaluate and influence space and ground system designs and architectures with the goal of achieving successful, efficient, and cost-effective Earth Observing System (EOS) operations. Emphasis is given to the general characteristics and concepts developed for the EOS Space Measurement System, which uses a new series of polar-orbiting observatories. Data rates are given for various instruments. Some of the operations concepts which require a total system view are also examined, including command operations, data processing, data accountability, data archival, prelaunch testing and readiness, launch, performance monitoring and assessment, contingency operations, flight software maintenance, and security.

Kelly, Angelita C.↗

Utilization of the Space Vision System as an Augmented Reality System For Mission Operations

Augmented reality is a technique whereby computer generated images are superimposed on live images for visual enhancement. Augmented reality can also be characterized as dynamic overlays when computer generated images are registered with moving objects in a live image. This technique has been successfully implemented, with low to medium levels of registration precision, in an NRA funded project entitled, "Improving Human Task Performance with Luminance Images and Dynamic Overlays". Future research is already being planned to also utilize a laboratory-based system where more extensive subject testing can be performed. However successful this might be, the problem will still be whether such a technology can be used with flight hardware. To answer this question, the Canadian Space Vision System (SVS) will be tested as an augmented reality system capable of improving human performance where the operation requires indirect viewing. This system has already been certified for flight and is currently flown on each shuttle mission for station assembly. Successful development and utilization of this system in a ground-based experiment will expand its utilization for on-orbit mission operations. Current research and development regarding the use of augmented reality technology is being simulated using ground-based equipment. This is an appropriate approach for development of symbology (graphics and annotation) optimal for human performance and for development of optimal image registration techniques. It is anticipated that this technology will become more pervasive as it matures. Because we know what and where almost everything is on ISS, this reduces the registration problem and improves the computer model of that reality, making augmented reality an attractive tool, provided we know how to use it. This is the basis for current research in this area. However, there is a missing element to this process. It is the link from this research to the current ISS video system and to flight hardware capable of utilizing this technology. This is the basis for this proposed Space Human Factors Engineering project, the determination of the display symbology within the performance limits of the Space Vision System that will objectively improve human performance. This utilization of existing flight hardware will greatly reduce the costs of implementation for flight. Besides being used onboard shuttle and space station and as a ground-based system for mission operational support, it also has great potential for science and medical training and diagnostics, remote learning, team learning, video/media conferencing, and educational outreach.

Maida, James C.↗

The MARS pathfinder end-to-end information system: A pathfinder for the development of future NASA planetary missions

The development of the Mars pathfinder is considered with emphasis on the End-to-End Information System (EEIS) development approach. The primary mission objective is to successfully develop and deliver a single flight system to the Martian surface, demonstrating entry, descent and landing. The EEIS is a set of functions distributed throughout the flight, ground and Mission Operation Systems (MOS) that inter-operate in order to control, collect, transport, process, store and analyze the uplink and downlink information flows of the mission. Coherence between the mission systems is achieved though the EEIS architecture. The key characteristics of the system are: a concurrent engineering approach for the development of flight, ground and mission operation systems; the fundamental EEIS architectural heuristics; a phased incremental EEIS development and test approach, and an EEIS design deploying flight, ground and MOS operability features, including integrated ground and flight based toolsets.

Cook, Richard A.↗

The Advanced Technology Operations System: ATOS

Mission control systems supporting new space missions face ever-increasing requirements in terms of functionality, performance, reliability and efficiency. Modern data processing technology is providing the means to meet these requirements in new systems under development. During the past few years the European Space Operations Centre (ESOC) of the European Space Agency (ESA) has carried out a number of projects to demonstrate the feasibility of using advanced software technology, in particular, knowledge based systems, to support mission operations. A number of advances must be achieved before these techniques can be moved towards operational use in future missions, namely, integration of the applications into a single system framework and generalization of the applications so that they are mission independent. In order to achieve this goal, ESA initiated the Advanced Technology Operations System (ATOS) program, which will develop the infrastructure to support advanced software technology in mission operations, and provide applications modules to initially support: Mission Preparation, Mission Planning, Computer Assisted Operations, and Advanced Training. The first phase of the ATOS program is tasked with the goal of designing and prototyping the necessary system infrastructure to support the rest of the program. The major components of the ATOS architecture is presented. This architecture relies on the concept of a Mission Information Base (MIB) as the repository for all information and knowledge which will be used by the advanced application modules in future mission control systems. The MIB is being designed to exploit the latest in database and knowledge representation technology in an open and distributed system. In conclusion the technological and implementation challenges expected to be encountered, as well as the future plans and time scale of the project, are presented.

Kaufeler, J.-F.↗

Mission operations computing systems evolution

As part of its preparation for the operational Shuttle era, the Goddard Space Flight Center (GSFC) is currently replacing most of the mission operations computing complexes that have supported near-earth space missions since the late 1960's. Major associated systems include the Metric Data Facility (MDF) which preprocesses, stores, and forwards all near-earth satellite tracking data; the Orbit Computation System (OCS) which determines related production orbit and attitude information; the Flight Dynamics System (FDS) which formulates spacecraft attitude and orbit maneuvers; and the Command Management System (CMS) which handles mission planning, scheduling, and command generation and integration. Management issues and experiences for the resultant replacement process are driven by a wide range of possible future mission requirements, flight-critical system aspects, complex internal system interfaces, extensive existing applications software, and phasing to optimize systems evolution.

Kurzhals, P. R.↗

Modular space station Phase B extension preliminary performance specification. Volume 2: Project

The four systems of the modular space station project are described, and the interfaces between this project and the shuttle project, the tracking and data relay satellite project, and an arbitrarily defined experiment project are defined. The experiment project was synthesized from internal experiments, detached research and application modules, and attached research and application modules to derive a set of interface requirements which will support multiple combinations of these elements expected during the modular space station mission. The modular space station project element defines a 6-man orbital program capable of growth to a 12-man orbital program capability. The modular space station project element specification defines the modular space station system, the premission operations support system, the mission operations support system, and the cargo module system and their interfaces.

Source record↗

An operations concept methodology to achieve low-cost mission operations

Historically, the Mission Operations System (MOS) for a space mission has been designed last because it is needed last. This has usually meant that the ground system must adjust to the flight vehicle design, sometimes at a significant cost. As newer missions have increasingly longer flight operations lifetimes, the MOS becomes proportionally more difficult and more resource-consuming. We can no longer afford to design the MOS last. The MOS concept may well drive the spacecraft, instrument, and mission designs, as well as the ground system. A method to help avoid these difficulties, responding to the changing nature of mission operations is presented. Proper development and use of an Operations Concept document results in a combined flight and ground system design yielding enhanced operability and producing increased flexibility for less cost.

Ledbetter, Kenneth W.↗

Space Mission Operations Ground Systems Integration Customer Service

The facility, which is now the Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center in Huntsville, AL, has provided continuous space mission and related services for the space industry since 1961, from Mercury Redstone through the International Space Station (ISS). Throughout the long history of the facility and mission support teams, the HOSC has developed a stellar customer support and service process. In this era, of cost cutting, and providing more capability and results with fewer resources, space missions are looking for the most efficient way to accomplish their objectives. One of the first services provided by the facility was fax transmission of documents to, then, Cape Canaveral in Florida. The headline in the Marshall Star, the newspaper for the newly formed Marshall Space Flight Center, read "Exact copies of Documents sent to Cape in 4 minutes." The customer was Dr. Wernher von Braun. Currently at the HOSC we are supporting, or have recently supported, missions ranging from simple ISS payloads requiring little more than "bentpipe" telemetry access, to a low cost free-flyer Fast, Affordable, Science and Technology Satellite (FASTSAT), to a full service ISS payload Alpha Magnetic Spectrometer 2 (AMS2) supporting 24/7 operations at three operations centers around the world with an investment of over 2 billion dollars. The HOSC has more need and desire than ever to provide fast and efficient customer service to support these missions. Here we will outline how our customer-centric service approach reduces the cost of providing services, makes it faster and easier than ever for new customers to get started with HOSC services, and show what the future holds for our space mission operations customers. We will discuss our philosophy concerning our responsibility and accessibility to a mission customer as well as how we deal with the following issues: initial contact with a customer, reducing customer cost, changing regulations and security, and cultural differences, to ensure an efficient response to customer issues using a small Customer Service Team (CST) and adaptability, constant communication with customers, technical expertise and knowledge of services, and dedication to customer service. The HOSC Customer Support Team has implemented a variety of processes, and procedures that help to mitigate the potential problems that arise when integrating ground system services for a variety of complex missions and the lessons learned from this experience will lead the future of customer service in the space operations industry.

Roth, Karl↗

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↗

The Comet Rendezvous Asteroid Flyby project

The Comet Rendezvous Asteroid Flyby (CRAF) spacecraft will be provided by the first Mariner Mark II (MMII). The MMII is a modular spacecraft which can be inexpensively reconfigured for different missions beyond the inner solar system. The rationale for a comet rendezvous mission are discussed, taking into account the probability that comets alone retain evidence of the chemical and physical conditions under which all solar system bodies were formed. A description of the rationale for the study of asteroids on the Comet Rendezvous Asteroid Flyby Mission is also presented. On its way to the rendezvous with a comet, the spacecraft will fly by one or more asteroids. It is assumed that the target asteroids will include moderately large main-belt objects several tens to perhaps 100 kilometers in diameter. Attention is also given to mission details, the spacecraft system, and the missions operations system.

Draper, R. F.↗

An intelligent position-specific training system for mission operations

Marshall Space Flight Center's (MSFC's) payload ground controller training program provides very good generic training; however, ground controller position-specific training can be improved by including position-specific training systems in the training program. This report explains why MSFC needs to improve payload ground controller position-specific training. The report describes a generic syllabus for position-specific training systems, a range of system designs for position-specific training systems, and a generic development process for developing position-specific training systems. The report also describes a position-specific training system prototype that was developed for the crew interface coordinator payload operations control center ground controller position. The report concludes that MSFC can improve the payload ground controller training program by incorporating position-specific training systems for each ground controller position; however, MSFC should not develop position-specific training systems unless payload ground controller position experts will be available to participate in the development process.

Schneider, M. P.↗

Modeling Systems-Of-Systems Interfaces with SysML

Space data systems are inherently complex. They are systems-of-systems, typically composed of spacecraft and mission operations systems (MOS) belonging to one (or more) organizations, and multi-mission communication assets belonging to other organizations. In many cases, the spacecraft contain sub-systems and instruments provided by different organizations, and MOS systems that may be developed and operated by other organizations. The point of greatest leverage in system architecting is at the interfaces. We have developed a set of methods for using SysML to model systems-of-systems and their interfaces. This paper describes how to apply this method to space data systems at a variety of levels of detail, from abstract systems and subsystems down to hardware and software components, including the details of their interfaces and protocol designs.

Shames, Peter M.↗

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↗

The Nation's Vision for Exploration: An Update

I.Current key activities: a) Constellation Level2-System Engineering. b) Lunar Architecture Team (LAT)2-technology assessment and architectural option for the lander. c) Mars Architecture Team-system engineering support, Science integration, precursor program planning. d) Lunar Lander Project Core Team-GN&C and Flight system engineering. e) Technology program-supporting multiple projects in robotics, power systems, aero entry technology. f) Mission Operation Project-Mission operations system engineering. g) Advanced Environmental Monitoring Instruments. H. Lunar Reconnaissance Orbiter instrument (Diviner). II. Mission Proposals a) Lunar Sample return. b) Lunar Gravity field mapper.

space exploration↗

Increases in Efficiency and Enhancements to the Mars Observer Non-stored Commanding Process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a Mission Operations System which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for the mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from Total Quality Management (TQM). This tool is known as a Process Action Team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's non-stored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was to, in fact, increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. The results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures. This paper will describe in detail the enhancements recommended by the PAT for the non-stored command generation process on Mars Observer. This will be contrasted with the process used by the flight team prior to implementation of these improvements. Finally, there will be a discussion of the applicability of the techniques devised by the PAT for enhancement of the non-stored command process to present and future projects.

Process↗

The Planetary Observer Program

An overview is presented of NASA's plans for the Planetary Observer Program, whose key element is to control the cost of each mission while establishing a long-term, stable base for the planetary sciences. The SSEC (Solar System Exploration Committee) has endorsed the view that many high science priority inner solar system missions are possible through the use of spacecraft derived from existing earth-orbital spacecraft. It has also recommended the application of space hardware such as that used on the Voyager and Galileo missions, development of both a new modular spacecraft for outer planet, comet, and main-belt asteroid missions (Mariner Mark II Program), and a multi-mission operations system to support future missions after the Venus Radar Mapper (VRM), and Galileo. A set of missions for the SSEC's Core Program has been recommended; they include: the VRM, the Mars Geoscience/Climatology Observer, the Comet Rendezvous/Asteroid Flyby, the Lunar Geoscience Orbiter, the Near-Earth Asteroid Rendezvous, the Venus Atmosphere Probe, the Mars Aeronomy Orbiter, the Mars Surface Probe, and the Comet Intercept Sample Return.

Blume, W. H.↗

Increases in efficiency and enhancements to the Mars Observer non-stored commanding process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a mission operations system which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from total quality management (TQM). This tool is known as a process action team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's nonstored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was, in fact, to increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. These results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures.

Brooks, Robert N., Jr.↗