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.
We describe the current mission operations flow for the Earth Observing-1 spacecraft as well as the more autonomous operations to which we are transitioning as part of the Autonomous Sciencecrat Experiment (ASE).
The purpose of this tutorial is to provide an introduction to various space mission types, link together the various mission systems engineering concepts which go into the design and development of a space mission with the ground system architecture. Attendees will learn about: Types of satellite missions and characteristics of them, Types of satellite orbits and why a particular mission is in a particular orbit, Characteristics of different satellite operators (commercial, DoD, civil), Mission drivers, Mission operations concepts and how various challenges have been addressed, Space mission data standards, How to deliver data, General ground system and Mission Operations Center design.
The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the missions science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the SRC lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis.Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together space craft, instrument and operations scenarios. The project implemented lessons learned from other small body missions: APLNEAR, JPLDAWN and ESARosetta. The key lesson learned was expected the unexpected and implement planning tools early in the lifecycle. In preparation to PDR, the project changed the asteroid arrival date, to arrive one year earlier and provided additional time margin. STK is used for Mission Design and STKScheduler for instrument coverage analysis.
The purpose of the paper is twofold: (1) to present an overview of the processes comprising planetary mission operations as conducted at the Jet Propulsion Laboratory, and (2) to present a project-specific and historical context within which this evolving process functions. In order to accomplish these objectives, the generic uplink and downlink functions are described along with their specialization to current flight projects. Also, new multimission capabilities are outlined, including prototyping of advanced-capability software for subsequent incorporation into more automated future operations. Finally, a specific historical ground is provided by listing some major operations software plus a genealogy of planetary missions beginning with Mariner 2 in 1962.
This will be presented at the Earth Science Constellation Mission Operations Work Group meeting June 13-15, 2017 to discuss EOS Aqua status.
Introduction: NASA is preparing to land the first woman and first person of color on the Moon within the next decade, and ensuring the success of these missions will depend on our preparation on the ground in multiple ground-based lunar environment analogs. To achieve this, NASA has used full mission class analogs, of which NASA Extreme Environment Mission Operations (NEEMO) is the longest continuously running example. Discussion: NEEMO is NASA’s long-standing undersea high-fidelity spaceflight mission analog. It focuses on exploration science, EVA techniques and tools, and maturing ISS IVA flight hardware and operations concepts. NEEMO crews are composed of groups of US and International Partner (IP) astronauts, engineers and scientists who live, work and explore in a challenging environment analogous to the environment experienced currently on ISS and what is expected for future deep space exploration destinations. NEEMO missions are conducted at Aquarius Reef Base (ARB), which includes a shore base in Tavernier, FL, and the world's only undersea research station, the Aquarius habitat, which is located 5.4 miles (9 kilometers) off Key Largo in the Florida Keys National Marine Sanctuary. ARB is owned and operated by Florida International University (FIU). Aquarius was selected due to its remote and extreme location and its ability to provide the unique isolation and risk factors that spaceflight presents. NEEMO missions allow for evaluations of end-to-end EVA and Science exploration concepts of operations with a crew that is in situ in a true extreme environment. They also allow for evaluations of flight hardware and ops tools that are either pondered or destined for ISS or Gateway in the near future. NEEMO missions feature flight-like interactions between the crew and a Mission Control Center (MCC )and Science Team, which in turn allows evaluation of mission and science operations decision making and communications techniques. One reason NEEMO missions are of such high fidelity is that so many of the participants are experienced human space flight end operators. The majority of crewmembers are trained astronauts, and many of the MCC operators have credentials as current or former certified ISS MCC operators (e.g., CapCom, EVA Officer, etc.). Mission products are generated daily by the ground team and are modeled on ISS products (but modified as needed). A planning team manages the constantly evolving mission timelines in response to the ever-changing constraints and opportunities. During NEEMO missions, suited EVA crewmembers (using diving helmets) have clear voice communications with each other, the habitat, and the MCC and Science Team back on shore. Each EVA crewmember also sends helmet cam video to the habitat and MCC and Science Teams. Appropriate communications latencies are inserted for the destination being simulated as well. NEEMO missions are made possible by a broad collaboration of participants. Astronauts from all of the ISS partner agencies are eligible for crew assignment. Often the crew includes a NASA scientist, doctor or engineer with a particular skill to contribute. Sometimes crewmembers come from external entities–generally institutes or universities. Objectives come from a wide variety of sources as well, from within NASA, IPs, government agencies, academia, commercial companies and research institutes. A typical NEEMO mission is a collaboration between at least 5 NASA centers. To date, 23 NEEMO missions have been conducted since 2001, and NEEMO 24 is planned for 2022. Conclusion: NEEMO is a high-fidelity mission analog conducted in an extreme subsea environment. It features experienced end-operators in human spaceflight, from the astronaut crewmembers to key personnel staffing Mission Control. Acknowledgments: The authors wish to thank FIU and NASA’s HEO SEI/Strategic Analysis and Exploration Integration and Science Directorate organizations for the continued support that makes the NEEMO Project possible.
Hypermedia, hypertext and Intelligent Tutoring System (ITS) applications to support all phases of mission operations are investigated. The application of hypermedia and ITS technology to improve system performance and safety in supervisory control is described - with an emphasis on modeling operator's intentions in the form of goals, plans, tasks, and actions. Review of hypermedia and ITS technology is presented as may be applied to the tutoring of command and control languages. Hypertext based ITS is developed to train flight operation teams and System Test and Operation Language (STOL). Specific hypermedia and ITS application areas are highlighted, including: computer aided instruction of flight operation teams (STOL ITS) and control center software development tools (CHIMES and STOL Certification Tool).
The effort of compiling a collection of Best Practices for use in Space Mission Operations was initiated within a subcommittee of the American Institute of Aeronautics and Astronautics (AIAA) Space Operations and Support Technical Committee (SOSTC). The idea was to eventually post a collection of Best Practices on a website so as to make them available to the general Space Operations community. The effort of searching for available Best Practices began in the fall of 1999. As the search progressed, it became apparent that there were not many Best Practices developed that were available to the general community. Therefore, the subcommittee decided to use the SOSTC Annual Workshop on Reducing Space Mission Costs as a forum for developing Best Practices for our purpose of sharing them with a larger audience. A dedicated track at the April 2000 workshop was designed to stimulate discussions on developing such Best Practices and forming working groups made up of experienced people from various organizations to perform the development. These groups were solicited to help outside the workshop to bring this effort to fruition. Since that time, biweekly teleconferences have been held to discuss the development of the Best Practices and their posting.
This paper will examine the issues and solutions to these challenges. First, a brief survey of the current FPGA technology and the process to reconfigure these devices will be provided. Second, the avionics architectural support to facilitate the inflight reconfiguration will be discussed. Third, the mission operation procedures and uplink/downlink process to reconfigure the spacecraft in-orbit will be described.
This paper describes a collaborative multiagent modeling and simulation approach for designing work systems. The Brahms environment is used to model mission operations for a semi-autonomous robot mission to the Moon at the work practice level. It shows the impact of human-decision making on the activities and energy consumption of a robot. A collaborative work systems design methodology is described that allows informal models, created with users and stakeholders, to be used as input to the development of formal computational models.
The Remote Agent (RA) is an Artificial Intelligence (AI) system which automates some of the tasks normally reserved for human mission operators and performs these tasks autonomously on-board the spacecraft. These tasks include activity generation, sequencing, spacecraft analysis, and failure recovery. The RA will be demonstrated as a flight experiment on Deep Space One (DSI), the first deep space mission of the NASA's New Millennium Program (NMP). As we moved from prototyping into actual flight code development and teamed with ground operators, we made several major extensions to the RA architecture to address the broader operational context in which PA would be used. These extensions support ground operators and the RA sharing a long-range mission profile with facilities for asynchronous ground updates; support ground operators monitoring and commanding the spacecraft at multiple levels of detail simultaneously; and enable ground operators to provide additional knowledge to the RA, such as parameter updates, model updates, and diagnostic information, without interfering with the activities of the RA or leaving the system in an inconsistent state. The resulting architecture supports incremental autonomy, in which a basic agent can be delivered early and then used in an increasingly autonomous manner over the lifetime of the mission. It also supports variable autonomy, as it enables ground operators to benefit from autonomy when L'@ey want it, but does not inhibit them from obtaining a detailed understanding and exercising tighter control when necessary. These issues are critical to the successful development and operation of autonomous spacecraft.
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.
NASA Goddard Space Flight Center (GSFC) manages many of NASA s earth and space science satellite missions. A wide variety of commercial products and GSFC-developed software components are typically integrated into a unique system configuration for each mission. Independent development of the many mission operations center systems has led to systems that are expensive to integrate, difficult to infuse with new capabilities developed for other programs, and cumbersome to maintain. This traditional approach becomes even more problematic as NASA moves towards satellite constellations, new operations concepts, and even further budgets reductions. The GSFC Mission Services Evolution Center (GMSEC) is creating a new architecture for future missions at GSFC. Instead of selecting the best-in-class components and creating a standard control center system, GMSEC is developing component interface standards so that multiple products can plug-and-play into the configuration. Missions can then select the best components based on the merits of the product and not simply based on recent integration history at NASA. The GMSEC system utilizes a publish/subscribe information bus and standard XML-based key message interfaces. Functional components can either match directly to the interface standard, or adapters can be developed to match the product's interface to the GMSEC standard with out impacting the source product. Applications Program Interfaces (API's) are being developed to isolate the underlying middleware from the applications software and to allow the middleware product to be switched if necessary. Interface Control Documents (ICDs) between each pair of communicating components is replaced by a single message/API specification document. New applications must simply match to the information bus standards and need not worry about all of the other applications in the system. For legacy software, adapters can be developed to facilitate communications between the application and the information bus. As the approach has matured, it has become apparent that it can provide innovative solutions to some of the multi-satellite challenges facing GSFC.
Mariner 9 orbital operations and extended mission events are discussed. Spacecraft observations for standard mapping and sun and earth occultations are outlined.
We are entering a new era in space exploration. Reduced operating budgets require innovative solutions to leverage existing systems to implement the capabilities of future missions. Custom solutions to fulfill mission objectives are no longer viable. Can NASA adopt international standards to reduce costs and increase interoperability with other space agencies? Can legacy systems be leveraged in a service oriented architecture (SOA) to further reduce operations costs? The Operations Technology Facility (OTF) at the Johnson Space Center (JSC) is collaborating with Deutsches Zentrum fur Luft- und Raumfahrt (DLR) to answer these very questions. The Mission Operations and Information Management Services Area (MOIMS) Spacecraft Monitor and Control (SM&C) Working Group within the Consultative Committee for Space Data Systems (CCSDS) is developing the Mission Operations standards to address this problem space. The set of proposed standards presents a service oriented architecture to increase the level of interoperability among space agencies. The OTF and DLR are developing independent implementations of the standards as part of an interoperability prototype. This prototype will address three key components: validation of the SM&C Mission Operations protocol, exploration of the Object Management Group (OMG) Data Distribution Service (DDS), and the incorporation of legacy systems in a SOA. The OTF will implement the service providers described in the SM&C Mission Operation standards to create a portal for interaction with a spacecraft simulator. DLR will implement the service consumers to perform the monitor and control of the spacecraft. The specifications insulate the applications from the underlying transport layer. We will gain experience with a DDS transport layer as we delegate responsibility to the middleware and explore transport bridges to connect disparate middleware products. A SOA facilitates the reuse of software components. The prototype will leverage the capabilities of existing legacy systems. Various custom applications and middleware solutions will be combined into one system providing the illusion of a set of homogenous services. This paper will document our journey as we implement the interoperability prototype. The team consists of software engineers with experience on the current command, telemetry and messaging systems that support the International Space Station (ISS) and Space Shuttle programs. Emphasis will be on the objectives, results and potential cost saving benefits.
Model-Based System Engineering (MBSE) is an increasingly popular methodology for designing complex engineering systems. As the use of MBSE has grown, it has begun to be applied to systems that are less hardware-based and more people- and process-based. We describe our approach to incorporating MBSE as a way to streamline development, and how to build a model consisting of core resources, such as requirements and interfaces, that can be adapted and used by new and upcoming projects. By comparing traditional Mission Operations System (MOS) system engineering with an MOS designed via a model, we will demonstrate the benefits to be obtained by incorporating MBSE in system engineering design processes.
Mars Observer, planned for launch in September 1992, will be the first deep space planetary mission to fully utilize a distributed operations concept for science instrument control. In addition, several of the other concepts proposed by the Mission Operations and Information Systems Subcommittee of the Solar System Exploration Committee have been adopted for the purpose of improving the efficiency and reducing the costs of Deep Space Mission Operations.
The scheduling of Space Station Freedom must satisfy four major requirements. It must ensure efficient housekeeping operations, maximize the collection of science, respond to changes in tasking and available resources, and accommodate the above changes in a manner that minimizes disruption of the ongoing operations of the station. While meeting these requirements the scheduler must cope with the complexity, scope, and flexibility of SSF operations. This requires the scheduler to deal with an astronomical number of possible schedules. The Operations Mission Planner (OMP) is centered around minimally disruptive replanning and the use of heuristics limit search in scheduling. OMP has already shown several artificial intelligence based scheduling techniques such as Interleaved Iterative Refinement and Bottleneck Identification using Process Chronologies.