SEARCH · Search NASA
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.
The Hubble Space Telescope Project at Goddard Space Flight Center has the overall HST Mission Operations responsibility. In carrying out this responsibility, the functions of mission operations are to fly the spacecraft properly, manage the HST support systems, monitor vehicle health and safety, and conduct the science program in the most efficient manner.
The joint NASA/Russian Space Agency mission program is discussed, considering the lessons learned. The initial Shuttle Mir science program and the NASA Mir program are described. The NASA Mir program is organized into ten distinct working groups which are co-chaired by representatives from the two cooperating nations. The NASA component is managed from the Johnson Space Center (TX). The support provided by NASA for long-duration missions and Mir expeditions is described. The scope of the scientific research carried out within the framework of the joint program is considered. The NASA Mir training approach is discussed and the mission operations are reviewed with emphasis on the Mir 21/NASA 2 mission.
NASDA has recently developed a new tracking and control system as a basis for future satellite mission operation. It is named type-I Space Operations and Data Systems (type-I SODS). The software of this system is separated into three parts: operation and control system, network system, and support and information system. The operation control system treats telemetry and command operations. The network system controls the communication line and ground station equipments to connect the satellite and the operation control system. The support and information system provides to other systems necessary information. JERS-1 which was launched in February of this year is the first satellite operated by type-l SODS. We explain the architecture and operation methods of this system using JERS-1 mission operations.
SmallSats have come a long way since the Huntsville Operations Support Center (HOSC) at NASA’s Marshall Space Flight Center supported its first “minisatellite” mission in 2010. And just as SmallSats themselves have evolved in those 12 years, so too has the HOSC’s mission support for SmallSats. Marshall Space Flight Center has a long history with payload and mission operations, including support for the Apollo missions to the moon, the Space Shuttle program, and 21 years of continuous around-the-clock science operations support for research aboard the International Space Station. Today, the HOSC is a multi-tenant facility, supporting not only ISS, but also NASA’s Commercial Crew program, the Space Launch System, the Hubble and Chandra observatories and others – including multiple SmallSat missions. Two SmallSat solar sail missions will be among those taking advantage of the HOSC’s resources for planning, training for and executing mission operations – the Near Earth Asteroid (NEA) Scout and Solar Cruiser missions. One of 10 6U CubeSats manifest on the Artemis I launch of NASA’s Space Launch System rocket this year, NEA Scout’s three-year mission will be supported through a more traditional operations concept, with a dedicated Flight Controller staff operating within the HOSC. Scheduled to launch as part of the Interstellar Mapping and Acceleration Probe (IMAP) in February 2025, Solar Cruiser’s 11-month mission will take a next-generation approach to operations by utilizing a multi-mission flight controller concept, as well as Marshall’s Telescience Resource Kit (TreK). TreK provides a suite of software applications and libraries that allow the Mission Operations Center to serve as an in-house ground system which incorporates remote and automation capability options for engineers and scientists. This presentation will compare the approaches the HOSC will use to support these two missions as a way of demonstrating the array of options NASA MSFC offers for operations support for CubeSat and SmallSat missions.
Spitzer Space Telescope was launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Development of the Mission Operations System (MOS) portion prior to launch was very different from planetary missions from the stand point that the MOS teams and Ground Data System had to be ready to support all aspects of the mission at launch (i.e., no cruise period for finalizing the implementation). For Spitzer, all mission-critical events post launch happen in hours or days rather than months or years, as is traditional with deep space missions. At the end of 2000 the Project was dealt a major blow when the Mission Operations System (MOS) had an unsuccessful Critical Design Review (CDR). The project made major changes at the beginning of 2001 in an effort to get the MOS (and Project) back on track. The result for the Spitzer Space Telescope was a successful launch of the observatory followed by an extremely successful In Orbit Checkout (IOC) and operations phase. This paper describes how the project was able to recover the MOS to a successful Delta (CDR) by mid 2001, and what changes in philosophies, experiences, and lessons learned followed. It describes how projects must invest early or else invest heavily later in the development phase to achieve a successful operations phase.
The focus of this paper is on the data analysis tools for the Mars Observer Attitude and Articulation Control Subsystem (AACS). Four different categories of analysis tools are presented, with details offered for specific tools. These same tools, and extensions thereof, have been adopted by the Galileo mission operations, and are being designed into Cassini and other future spacecraft mission operations.
As light time delays increase, the number of such situations in which crew autonomy is the best way to conduct the mission is expected to increase. However, there are significant open questions regarding which functions to allocate to ground and crew as the time delays increase. In situations where the ideal solution is to allocate responsibility to the crew and the vehicle, a second question arises: should the activity be the responsibility of the crew or an automated vehicle function? More specifically, we must answer the following questions: What aspects of mission operation responsibilities (Plan, Train, Fly) should be allocated to ground based or vehicle based planning, monitoring, and control in the presence of significant light-time delay between the vehicle and the Earth?How should the allocated ground based planning, monitoring, and control be distributed across the flight control team and ground system automation? How should the allocated vehicle based planning, monitoring, and control be distributed between the flight crew and onboard system automation?When during the mission should responsibility shift from flight control team to crew or from crew to vehicle, and what should the process of shifting responsibility be as the mission progresses? NASA is developing a roadmap of capabilities for Autonomous Mission Operations for human spaceflight. This presentation will describe the current state of development of this roadmap, with specific attention to in-space inspection tasks that crews might perform with minimum assistance from the ground.
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.
My main project was to determine and implement updates to be made to MODEAR (Mission Operations Data Enterprise Architecture Repository) process definitions to be used for CST-100 (Crew Space Transportation-100) related missions. Emphasis was placed on the scheduling aspect of the processes. In addition, I was to complete other tasks as given. Some of the additional tasks were: to create pass-through command look-up tables for the flight controllers, finish one of the MDT (Mission Operations Directorate Display Tool) displays, gather data on what is included in the CST-100 public data, develop a VBA (Visual Basic for Applications) script to create a csv (Comma-Separated Values) file with specific information from spreadsheets containing command data, create a command script for the November MCC-ASIL (Mission Control Center-Avionics System Integration Laboratory) testing, and take notes for one of the TCVB (Terminal Configured Vehicle B-737) meetings. In order to make progress in my main project I scheduled meetings with the appropriate subject matter experts, prepared material for the meetings, and assisted in the discussions in order to understand the process or processes at hand. After such discussions I made updates to various MODEAR processes and process graphics. These meetings have resulted in significant updates to the processes that were discussed. In addition, the discussions have helped the departments responsible for these processes better understand the work ahead and provided material to help document how their products are created. I completed my other tasks utilizing resources available to me and, when necessary, consulting with the subject matter experts. Outputs resulting from my other tasks were: two completed and one partially completed pass through command look-up tables for the fight controllers, significant updates to one of the MDT displays, a spreadsheet containing data on what is included in the CST-100 public data, a tool to create a csv file with specific information from spreadsheets containing command data, a command script for the November MCC-ASIL testing which resulted in a successful test day identifying several potential issues, and notes from one of the TCVB meetings that was used to keep the teams up to date on what was discussed and decided. I have learned a great deal working at NASA these last four months. I was able to meet and work with amazing individuals, further develop my technical knowledge, expand my knowledge base regarding human spaceflight, and contribute to the CST-100 missions. My work at NASA has strengthened my desire to continue my education in order to make further contributions to the field, and has given me the opportunity to see the advantages of a career at NASA.
The Telecommunications and Mission Operations Directorate (TMOD) of the Jet Propulsion Laboratory is responsible for development, maintenance and operation of flight operations systems for several classes of science missions planned for the next several years.
The Advanced Multimission Operations System (AMMOS) at NASA's Jet Propulsion Laboratory is based on a highly adaptable multimission ground data system (MGDS) for mission operations. The goal for MGDS is to support current flight project science and engineering personnel and to meet the demands of future missions while reducing associated operations and software development costs. MGDS has become a powerful and flexible mission operations system by using a network of heterogeneous workstations, emerging open system standards, and selecting an adaptable tools-based architecture. Challenges in developing adaptable systems for mission operations and the benefits of this approach are described.
This presentation provides an updated status of Earth Observing 1 operations status for the 2016 Mission Operations Working Group.
This presentation at the Earth Science Constellation Mission Operations Working Group meeting at KSC in December 2017 to discuss EOS (Earth Observing System) Aqua Earth Science Constellation status. Reviewed and approved by Eric Moyer, ESMO (Earth Science Mission Operations) Deputy Project Manager.
No abstract available
Functional description of launch vehicle, tracking and data acquisition, spacecraft, and mission operations of Surveyor mission
Introduction presentation to the Earth Science Constellation Mission Operations Working Group (MOWG) meeting planned as a virtual meeting from September 29 - October 2, 2020.
The NASA Goddard Space Science Mission Operations project (SSMO) is performing a technical cost-benefit analysis for centralizing and consolidating operations of a diverse set of missions into a unified and integrated technical infrastructure. The presentation will focus on the notion of normalizing spacecraft operations processes, workflows, and tools. It will also show the processes of creating a standardized open architecture, creating common security models and implementations, interfaces, services, automations, notifications, alerts, logging, publish, subscribe and middleware capabilities. The presentation will also discuss how to leverage traditional capabilities, along with virtualization, cloud computing services, control groups and containers, and possibly Big Data concepts.
This paper will discuss the concept of developing a space mission operations concept; the benefits of starting this system engineering task early; the neccessary inputs to the process; and the products that are generated.