Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission systems”

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 145 records · Page 8

Pointing, Acquisition, and Tracking for the TBIRD Cubesat Mission: System Design and Pre-Flight Results

The Terabyte InfraRed Delivery (TBIRD) program will establish a communication link from a nanosatellite in low-Earth orbit to a ground station at burst rates up to 200 Gbps. The TBIRD payload is currently in the process of integrating with the 6-U CubeSat host bus and pre-flight testing has been completed. An overview of the pointing, acquisition, and tracking system for TBIRD is provided as well as a summary of results from pre-flight testing. TBIRD relies on the spacecraft bus to implement fine pointing corrections supplied by its quad sensor at a rate of 10 Hz. The measured accuracy of pointing feedback is about 10μrad RMS per axis. A custom optical assembly was designed for transmitter/receiver alignment stability which was measured to be within 25μrad two-axis through environmental testing. With TBIRD feedback in the loop, single axis pointing accuracy of the downlink is predicted to be about 30μrad RMS.

space communications↗

Model-Based Systems Engineering for Capturing Mission Architecture System Processes with an Application Case Study - Orion Flight Test 1

Model-based Systems Engineering (MBSE) is an emerging methodology that can be leveraged to enhance many system development processes. MBSE allows for the centralization of an architecture description that would otherwise be stored in various locations and formats, thus simplifying communication among the project stakeholders, inducing commonality in representation, and expediting report generation. This paper outlines the MBSE approach taken to capture the processes of two different, but related, architectures by employing the Systems Modeling Language (SysML) as a standard for architecture description and the modeling tool MagicDraw. The overarching goal of this study was to demonstrate the effectiveness of MBSE as a means of capturing and designing a mission systems architecture. The first portion of the project focused on capturing the necessary system engineering activities that occur when designing, developing, and deploying a mission systems architecture for a space mission. The second part applies activities from the first to an application problem - the system engineering of the Orion Flight Test 1 (OFT-1) End-to-End Information System (EEIS). By modeling the activities required to create a space mission architecture and then implementing those activities in an application problem, the utility of MBSE as an approach to systems engineering can be demonstrated.

Orion Flight Test 1 (OFT-1)↗

Open-Source Science-led Development of the Atmosphere Observing System (AOS) Mission Science Data System (SDS)

The Earth System Observatory (ESO) Atmosphere Observing System (AOS) mission will provide space-based and suborbital observations of collocated cloud, dynamic, precipitation and aerosol processing leading to improved weather, air quality, and climate predictions. The AOS Science Data System (SDS) will be a system of systems developed within the Cloud to manage the research and operational processing of AOS mission orbital and suborbital sensors and curate these data for reprocessing (e.g., in near real-time or by collection) and transfer them to a NASA Distributed Active Archive Center (DAAC) for long-term storage. Further, AOS SDS will follow guidelines provided by NASA Earth Science Data Systems (ESDS) program including standard conventions for data file formats, naming, and metadata to improve data interoperability, interpretability, usability, discovery, provenance, and spatiotemporal representativeness. The AOS mission follows NASA’s lead in making a commitment to Open-Source Science (OSS) including the sharing of data, software, and knowledge in an open and timely manner. Each of the AOS SDS system components will be developed with open-source concepts including components of SDS itself as well as AOS mission algorithms. Further, the AOS SDS assumes the role to lead and facilitate OSS activities for the AOS mission. This presentation describes the framework of the AOS SDS and its integral part in facilitating OSS within the AOS mission.

David Giles↗

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗

Analyses of the dynamic docking test system for advanced mission docking system test programs

Results are given of analytical studies performed in support of the design, implementation, checkout and use of NASA's dynamic docking test system (DDTS). Included are analyses of simulator components, a list of detailed operational test procedures, a summary of simulator performance, and an analysis and comparison of docking dynamics and loads obtained by test and analysis.

Gates, R. M.↗

Alpha: A real-time decentralized operating system for mission-oriented system integration and operation

Alpha is a new kind of operating system that is unique in two highly significant ways. First, it is decentralized transparently providing reliable resource management across physically dispersed nodes, so that distributed applications programming can be done largely as though it were centralized. And second, it provides comprehensive, high technology support for real-time system integration and operation, an application area which consists predominately of aperiodic activities having critical time constraints such as deadlines. Alpha is extremely adaptable so that it can be easily optimized for a wide range of problem-specific functionality, performance, and cost. Alpha is the first systems effort of the Archons Project, and the prototype was created at Carnegie-Mellon University directly on modified Sun multiprocessor workstation hardware. It has been demonstrated with a real-time C(sup 2) application. Continuing research is leading to a series of enhanced follow-ons to Alpha; these are portable but initially hosted on Concurrent's MASSCOMP line of multiprocessor products.

Jensen, E. Douglas↗

Habitat Demonstration Unit Project Leadership and Management Strategies

This paper gives an overview of the National Aeronautics and Space Administration (NASA) led multi-center Habitat Demonstration Unit (HDU) project leadership and management strategies. The HDU project team constructed and tested an analog prototype lunar surface habitat/laboratory called the Pressurized Excursion Module (PEM) during 2010. The prototype unit subsystems were integrated in a short amount of time, utilizing a tiger team approach that brought together over 20 habitation-related technologies and innovations from a variety of NASA centers. This paper describes the leadership and management strategies as well as lessons learned pertaining to leading and managing a multi-center diverse team in a rapid prototype environment. The PEM configuration went from a paper design to an operational surface habitat demonstration unit in less than 12 months. The HDU project is part of the strategic plan from the Exploration Systems Mission Directorate (ESMD) Directorate Integration Office (DIO) and the Exploration Mission Systems Office (EMSO) to test destination elements in analog environments. The 2011 HDU-Deep Space Habitat (DSH) configuration will build upon the PEM work, and emphasize validity of crew operations (remote working and living), EVA operations, mission operations, logistics operations, and science operations that might be required in a deep space context for Near Earth Object (NEO) exploration mission architectures. The 2011 HDU-DSH will be field-tested during the 2011 Desert Research and Technologies Studies (DRaTS) field tests. The HDU project is a "technology-pull" project that integrates technologies and innovations from multiple NASA centers. This project will repurpose the HDU 2010 demo unit that was field tested in the 2010 DRaTS, adding habitation functionality to the prototype unit. This paper will describe the strategy of establishing a multi-center project management team that put in place the key multi-center leadership skills and disciplines to enable a successful tiger team approach. Advocacy was established with key stakeholders and NASA Headquarters (HQ) by defining a strategic vision, mission, goals and objectives for the project and team. As a technology-pull testbed capability the HDU project was able to collaborate and leverage the Exploration Technology Development Program (ETDP) and individual NASA center investments which capitalized on their respective center core competencies and skills. This approach enable the leveraging of over $7.5m of value to create an operational habitat demonstration unit 2010 PEM configuration.

Kennedy, Kriss J.↗

Habitat Demonstration Unit Project: Leadership and Management Strategies for a Rapid Prototyping Project

This paper gives an overview of the National Aeronautics and Space Administration (NASA) led multi-center Habitat Demonstration Unit (HDU) project leadership and management strategies being used by the NASA HDU team for a rapid prototyping project. The HDU project team constructed and tested an analog prototype lunar surface habitat/laboratory called the Pressurized Excursion Module (PEM) during 2010. The prototype unit subsystems were integrated in a short amount of time, utilizing a tiger team rapid prototyping approach that brought together over 20 habitation-related technologies and innovations from a variety of NASA centers. This paper describes the leadership and management strategies as well as lessons learned pertaining to leading and managing a multi-center diverse team in a rapid prototype environment. The PEM configuration went from a paper design to an operational surface habitat demonstration unit in less than 12 months. The HDU project is part of the strategic plan from the Exploration Systems Mission Directorate (ESMD) Directorate Integration Office (DIO) and the Exploration Mission Systems Office (EMSO) to test destination elements in analog environments. The 2011 HDU-Deep Space Habitat (DSH) configuration will build upon the PEM work, and emphasize validity of crew operations (remote working and living), EVA operations, mission operations, logistics operations, and science operations that might be required in a deep space context for Near Earth Object (NEO) exploration mission architectures. The 2011 HDU-DSH will be field-tested during the 2011 Desert Research and Technologies Studies (DRaTS) field tests. The HDU project is a "technology-pull" project that integrates technologies and innovations from multiple NASA centers. This project will repurpose the HDU 2010 demo unit that was field tested in the 2010 DRaTS, adding habitation functionality to the prototype unit. This paper will describe the strategy of establishing a multi-center project management team that put in place the key multi-center leadership skills and disciplines to enable a successful tiger team approach. Advocacy was established with key stakeholders and NASA Headquarters (HQ) by defining a strategic vision, mission, goals and objectives for the project and team. As a technology-pull testbed capability the HDU project was able to collaborate and leverage the Exploration Technology Development Program (ETDP) and individual NASA center investments which capitalized on their respective center core competencies and skills. This approach enable the leveraging of over $7.5m of value to create an operational habitat demonstration unit 2010 PEM configuration.

Kennedy, Kriss J.↗

Mariner Mars 1971 project. Volume 3: Mission operations system implementation and standard mission flight operations

The Mariner Mars 1971 mission which was another step in the continuing program of planetary exploration in search of evidence of exobiological activity, information on the origin and evolution of the solar system, and basic science data related to the study of planetary physics, geology, planetology, and cosmology is reported. The mission plan was designed for two spacecraft, each performing a separate but complementary mission. However, a single mission plan was actually used for Mariner 9 because of failure of the launch vehicle for the first spacecraft. The implementation is described, of the Mission Operations System, including organization, training, and data processing development and operations, and Mariner 9 spacecraft cruise and orbital operations through completion of the standard mission from launch to solar occultation in April 1972 are discussed.

Source record↗

A mission planning concept and mission planning system for future manned space missions

The international character of future manned space missions will compel the involvement of several international space agencies in mission planning tasks. Additionally, the community of users requires a higher degree of freedom for experiment planning. Both of these problems can be solved by a decentralized mission planning concept using the so-called 'envelope method,' by which resources are allocated to users by distributing resource profiles ('envelopes') which define resource availabilities at specified times. The users are essentially free to plan their activities independently of each other, provided that they stay within their envelopes. The new developments were aimed at refining the existing vague envelope concept into a practical method for decentralized planning. Selected critical functions were exercised by planning an example, founded on experience acquired by the MSCC during the Spacelab missions D-1 and D-2. The main activity regarding future mission planning tasks was to improve the existing MSCC mission planning system, using new techniques. An electronic interface was developed to collect all formalized user inputs more effectively, along with an 'envelope generator' for generation and manipulation of the resource envelopes. The existing scheduler and its data base were successfully replaced by an artificial intelligence scheduler. This scheduler is not only capable of handling resource envelopes, but also uses a new technology based on neuronal networks. Therefore, it is very well suited to solve the future scheduling problems more efficiently. This prototype mission planning system was used to gain new practical experience with decentralized mission planning, using the envelope method. In future steps, software tools will be optimized, and all data management planning activities will be embedded into the scheduler.

Wickler, Martin↗

Mission telemetry system monitor: A real-time knowledge-based system

The Galileo Mission Telemetry System (MTS) has a cluster of computer subsystems configured as a star network. The MTS handles the real-time processing of spacecraft telemetry and ground monitor data. Large volumes of status and fault messages are generated as a result of changes in the system environment. These messages are triggered by the conditions that exist on any one particular subsystem or device. The order of message generation is in time sequence and does not always correlate to the function sequence of active processes. A significant number of messages provide context with varying degrees of uncertainty. As such, highly skilled telemetry controllers are required to regularly go through high volumes of messages generated by the MTS to identify, diagnose, and isolate faults. A knowledge-based system prototype is being developed to monitor the Galileo Mission Telemetry System performance. The system design approach features temporal reasoning, uncertainty management, and intelligent graphic user interfaces.

Mouneimne, Samih A.↗

A Titan Explorer Mission Utilizing Solar Electric Propulsion and Chemical Propulsion Systems

Mission and Systems analyses were performed for a Titan Explorer Mission scenario utilizing medium class launch vehicles, solar electric propulsion system (SEPS) for primary interplanetary propulsion, and chemical propulsion for capture at Titan. An examination of a range of system factors was performed to determine their affect on the payload delivery capability to Titan. The effect of varying the launch vehicle, solar array power, associated number of SEPS thrusters, chemical propellant combinations, tank liner thickness, and tank composite overwrap stress factor was investigated. This paper provides a parametric survey of the aforementioned set of system factors, delineating their affect on Titan payload delivery, as well as discussing aspects of planetary capture methodology.

Cupples, Michael↗

Mars Exploration: Mission and System Analysis of the Split Sprint Mission

The information presented in this report provides detailed mission and system analysis of the Split Sprint Mission to Mars. These data were generated from September 1987 through July 1988 and involved numerous individuals within Program Development. This mission derives its name from the fact that the total mission payload is split between two vehicles, a cargo vehicle, and a piloted vehicle. The cargo vehicle carries the Mars lander and propellant for the piloted vehicle return to Earth. Then approximately 1 1/2 years later, the piloted vehicle carries the crew on a higher energy "sprint” trajectory to Mars. The advantages of the Split Sprint Mission is that the payload for the piloted vehicle is minimized and the crew would be in space for only 14 months. Mission and system data are presented for a Sprint Mission in the year 2004. Many important aspects of the mission were studied in detail. These include orbital lighting and lifetime analysis, Mars parking orbit selection, Earth departure window analysis, lander descent and ascent performance, vehicle aerobraking requirements, mission orbital maneuvers, and many other analyses listed in the Table of Contents. Emphasis was placed on vehicle performance analysis which ranged from recovery of the Earth departure stages to aerocapture of the Earth Return Capsule. There is also a section describing the computer programs that were used for this study. These programs provide many useful tools for future studies of manned planetary missions. This introductory section will give an overall view of the Split Sprint Mission and describe the orbital operations and vehicles that were studied.

Mars Architecture Team↗

Grand Challenge Problems in Real-Time Mission Control Systems for NASA's 21st Century Missions

Space missions of the 21st Century will be characterized by constellations of distributed spacecraft, miniaturized sensors and satellites, increased levels of automation, intelligent onboard processing, and mission autonomy. Programmatically, these missions will be noted for dramatically decreased budgets and mission development lifecycles. Current progress towards flexible, scaleable, low-cost, reusable mission control systems must accelerate given the current mission deployment schedule, and new technology will need to be infused to achieve desired levels of autonomy and processing capability. This paper will discuss current and future missions being managed at NASA's Goddard Space Flight Center in Greenbelt, MD. It will describe the current state of mission control systems and the problems they need to overcome to support the missions of the 21st Century.

Pfarr, Barbara B.↗