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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Mission Data System Java Edition Version 7

The Mission Data System framework defines closed-loop control system abstractions from State Analysis including interfaces for state variables, goals, estimators, and controllers that can be adapted to implement a goal-oriented control system. The framework further provides an execution environment that includes a goal scheduler, execution engine, and fault monitor that support the expression of goal network activity plans. Using these frameworks, adapters can build a goal-oriented control system where activity coordination is verified before execution begins (plan time), and continually during execution. Plan failures including violations of safety constraints expressed in the plan can be handled through automatic re-planning. This version optimizes a number of key interfaces and features to minimize dependencies, performance overhead, and improve reliability. Fault diagnosis and real-time projection capabilities are incorporated. This version enhances earlier versions primarily through optimizations and quality improvements that raise the technology readiness level. Goals explicitly constrain system states over explicit time intervals to eliminate ambiguity about intent, as compared to command-oriented control that only implies persistent intent until another command is sent. A goal network scheduling and verification process ensures that all goals in the plan are achievable before starting execution. Goal failures at runtime can be detected (including predicted failures) and handled by adapted response logic. Responses can include plan repairs (try an alternate tactic to achieve the same goal), goal shedding, ignoring the fault, cancelling the plan, or safing the system.

Reinholtz, William K.↗
NASA NTRS1995

A Systems Engineering Approach to the Analysis of a Planetary Mission Ground System in Terms of Science Objectives

The most fundamental objective of all planetary missions is to return data. To accomplish this, a spacecraft is fabricated and built, software is planned and coded, and a ground system is designed and implemented. However, a systems engineering approach to determine how the collection of data drives ground system capabilities has received little attention.This paper defines a technique by which science objectives can be quantitatively evaluated. For illustrative purposes, it will be applied to NASA's Cassini Mission. This mission, to be launched in 1997, is an international endeavor designed to orbit Saturn for four years.The results of this systems engineering approach will show which science objectives drive specific ground system capabilities. In addition, this technique can assist system engineers in the selection of the science payload during pre-project mission planning; ground system designers during ground system development and implementation; and operations personnel during the mission.

systems engineering, ground systems↗
NASA NTRS1993

Mission operations update for the restructured Earth Observing System (EOS) mission

The National Aeronautics and Space Administration's (NASA) Earth Observing System (EOS) will provide a comprehensive long term set of observations of the Earth to the Earth science research community. The data will aid in determining global changes caused both naturally and through human interaction. Understanding man's impact on the global environment will allow sound policy decisions to be made to protect our future. EOS is a major component of the Mission to Planet Earth program, which is NASA's contribution to the U.S. Global Change Research Program. EOS consists of numerous instruments on multiple spacecraft and a distributed ground system. The EOS Data and Information System (EOSDIS) is the major ground system developed to support EOS. The EOSDIS will provide EOS spacecraft command and control, data processing, product generation, and data archival and distribution services for EOS spacecraft. Data from EOS instruments on other Earth science missions (e.g., Tropical Rainfall Measuring Mission (TRMM)) will also be processed, distributed, and archived in EOSDIS. The U.S. and various International Partners (IP) (e.g., the European Space Agency (ESA), the Ministry of International Trade and Industry (MITI) of Japan, and the Canadian Space Agency (CSA)) participate in and contribute to the international EOS program. The EOSDIS will also archive processed data from other designated NASA Earth science missions (e.g., UARS) that are under the broad umbrella of Mission to Planet Earth.

Kelly, Angelita Castro↗
NASA NTRS2005

Solar Electric and Chemical Propulsion for a Titan Mission

Systems analyses were performed for a Titan Explorer Mission characterized by Earth-Saturn transfer stages using solar electric power generation and propulsion systems for primary interplanetary propulsion, and chemical propulsion for capture at Titan. An examination of a range of system factors was performed to determine their effect on the payload delivery capability to Titan. The effect of varying launch vehicle type, solar array power level, ion thruster number, specific impulse, trip time, and Titan capture stage chemical propellant choice was investigated. The major purpose of the study was to demonstrate the efficacy of applying advanced ion propulsion system technologies like NASA's Evolutionary Xenon Thruster (NEXT), coupled with state-of-the-art (SOA) and advanced chemical technologies to a Flagship class mission. This study demonstrated that a NASA Design Reference Mission (DRM) payload of 406 kg could be successfully delivered to Titan using the baseline advanced ion propulsion system in conjunction with SOA chemical propulsion for Titan capture. In addition, the SEPS/Chemical system of this study is compared to an all- chemical NASA DRM mission. Results showed that the NEXT- based SEPS/Chemical system was able to deliver the required payload to Titan in 5 years less transfer time and on a smaller launch vehicle than the SOA chemical option.

Cupples, Michael↗
NASA NTRS2012

NASA's Solar Dynamics Observatory (SDO): A Systems Approach to a Complex Mission

The Solar Dynamics Observatory (SDO) includes three advanced instruments, massive science data volume, stringent science data completeness requirements, and a custom ground station to meet mission demands. The strict instrument science requirements imposed a number of challenging drivers on the overall mission system design, leading the SDO team to adopt an integrated systems engineering presence across all aspects of the mission to ensure that mission science requirements would be met. Key strategies were devised to address these system level drivers and mitigate identified threats to mission success. The global systems engineering team approach ensured that key drivers and risk areas were rigorously addressed through all phases of the mission, leading to the successful SDO launch and on-orbit operation. Since launch, SDO's on-orbit performance has met all mission science requirements and enabled groundbreaking science observations, expanding our understanding of the Sun and its dynamic processes.

systems engineering↗
NASA NTRS2012

NASA's Solar Dynamics Observatory (SDO): A Systems Approach to a Complex Mission

The Solar Dynamics Observatory (SDO) includes three advanced instruments, massive science data volume, stringent science data completeness requirements, and a custom ground station to meet mission demands. The strict instrument science requirements imposed a number of challenging drivers on the overall mission system design, leading the SDO team to adopt an integrated systems engineering presence across all aspects of the mission to ensure that mission science requirements would be met. Key strategies were devised to address these system level drivers and mitigate identified threats to mission success. The global systems engineering team approach ensured that key drivers and risk areas were rigorously addressed through all phases of the mission, leading to the successful SDO launch and on-orbit operation. Since launch, SDO s on-orbit performance has met all mission science requirements and enabled groundbreaking science observations, expanding our understanding of the Sun and its dynamic processes.

Ruffa, John A.↗
NASA NTRS1990

Hypersonic aircraft design

A hypersonic aircraft is designed which uses scramjets to accelerate from Mach 6 to Mach 10 and sustain that speed for two minutes. Different propulsion systems were considered and it was decided that the aircraft would use one full scale turbofan-ramjet. Two solid rocket boosters were added to save fuel and help the aircraft pass through the transonic region. After considering aerodynamics, aircraft design, stability and control, cooling systems, mission profile, and landing systems, a conventional aircraft configuration was chosen over that of a waverider. The conventional design was chosen due to its landing characteristics and the relative expense compared to the waverider. Fuel requirements and the integration of the engine systems and their inlets are also taken into consideration in the final design. A hypersonic aircraft was designed which uses scramjets to accelerate from Mach 6 to Mach 10 and sustain that speed for two minutes. Different propulsion systems were considered and a full scale turbofan-ramjet was chosen. Two solid rocket boosters were added to save fuel and help the aircraft pass through the transonic reqion. After the aerodynamics, aircraft design, stability and control, cooling systems, mission profile, landing systems, and their physical interactions were considered, a conventional aircraft configuration was chosen over that of a waverider. The conventional design was chosen due to its landing characteristics and the relative expense compared to the waverider. Fuel requirements and the integration of the engine systems and their inlets were also considered in the designing process.

Alkamhawi, Hani↗
NASA NTRS2011

MOS 2.0: Modeling the Next Revolutionary Mission Operations System

Designed and implemented in the 1980's, the Advanced Multi-Mission Operations System (AMMOS) was a breakthrough for deep-space NASA missions, enabling significant reductions in the cost and risk of implementing ground systems. By designing a framework for use across multiple missions and adaptability to specific mission needs, AMMOS developers created a set of applications that have operated dozens of deep-space robotic missions over the past 30 years. We seek to leverage advances in technology and practice of architecting and systems engineering, using model-based approaches to update the AMMOS. We therefore revisit fundamental aspects of the AMMOS, resulting in a major update to the Mission Operations System (MOS): MOS 2.0. This update will ensure that the MOS can support an increasing range of mission types, (such as orbiters, landers, rovers, penetrators and balloons), and that the operations systems for deep-space robotic missions can reap the benefits of an iterative multi-mission framework.12 This paper reports on the first phase of this major update. Here we describe the methods and formal semantics used to address MOS 2.0 architecture and some early results. Early benefits of this approach include improved stakeholder input and buy-in, the ability to articulate and focus effort on key, system-wide principles, and efficiency gains obtained by use of well-architected design patterns and the use of models to improve the quality of documentation and decrease the effort required to produce and maintain it. We find that such methods facilitate reasoning, simulation, analysis on the system design in terms of design impacts, generation of products (e.g., project-review and software-delivery products), and use of formal process descriptions to enable goal-based operations. This initial phase yields a forward-looking and principled MOS 2.0 architectural vision, which considers both the mission-specific context and long-term system sustainability.

ground support systems↗
NASA NTRS2003

Reuniting the Solar System: Integrated Education and Public Outreach Projects for Solar System Exploration Missions and Programs

The Solar System Exploration Education Forum has worked for five years to foster Education and Public Outreach (E/PO) cooperation among missions and programs in order to leverage resources and better meet the needs of educators and the public. These efforts are coming together in a number of programs and products and in '2004 - The Year of the Solar System.' NASA's practice of having independent E/PO programs for each mission and its public affairs emphasis on uniqueness has led to a public perception of a fragmented solar system exploration program. By working to integrate solar system E/PO, the breadth and depth of the solar system exploration program is revealed. When emphasis is put on what missions have in common, as well as their differences, each mission is seen in the context of the whole program.

Lowes, Leslie↗
NASA NTRS1996

Pluto Express Sciencecraft System Design

A number of mission system architectures have been studied for a Pluto flyby mission, with the goal of achieving the most cost effective means of meeting a well defined set of science and technology objectives. The results of this trade study have been coupled with a new development implementation approach to create a highly integrated concurrently engineered mission system called a

Pluto↗
NASA NTRS1991

Design of mission operations systems for scientific remote sensing

The present work describes the mission operations system (MOS) design process for remote-sensing missions. A MOS is defined as the system required to perform, monitor, and control an operation, encompassing personnel, hardware, software and/or documentation. Attention is given to telecommunications and remote-sensing instrumentation, MOS definition program phases and reviews, and MOS organization, management, and staffing. Also treated are the uplink and downlink processes, anomalies and contingency plans, the illustrative case of the MOS for the Magellan radar sensing mission, and a projection of future MOSs incorporating AI.

Wall, Stephen D.↗
NASA NTRS2017

Smashing the Stovepipe: Leveraging the GMSEC Open Architecture and Advanced IT Automation to Rapidly Prototype, Develop and Deploy Next-Generation Multi-Mission Ground Systems

Satellite/Payload Ground Systems - Typically highly-customized to a specific mission's use cases - Utilize hundreds (or thousands!) of specialized point-to-point interfaces for data flows / file transfers Documentation and tracking of these complex interfaces requires extensive time to develop and extremely high staffing costs Implementation and testing of these interfaces are even more cost-prohibitive, and documentation often lags behind implementation resulting in inconsistencies down the road With expanding threat vectors, IT Security, Information Assurance and Operational Security have become key Ground System architecture drivers New Federal security-related directives are generated on a daily basis, imposing new requirements on current / existing ground systems - These mandated activities and data calls typically carry little or no additional funding for implementation As a result, Ground System Sustaining Engineering groups and Information Technology staff continually struggle to keep up with the rolling tide of security Advancing security concerns and shrinking budgets are pushing these large stove-piped ground systems to begin sharing resources - I.e. Operational / SysAdmin staff, IT security baselines, architecture decisions or even networks / hosting infrastructure Refactoring these existing ground systems into multi-mission assets proves extremely challenging due to what is typically very tight coupling between legacy components As a result, many "Multi-Mission" ops. environments end up simply sharing compute resources and networks due to the difficulty of refactoring into true multi-mission systems Utilizing continuous integration / rapid system deployment technologies in conjunction with an open architecture messaging approach allows System Engineers and Architects to worry less about the low-level details of interfaces between components and configuration of systems GMSEC messaging is inherently designed to support multi-mission requirements, and allows components to aggregate data across multiple homogeneous or heterogeneous satellites or payloads - The highly-successful Goddard Science and Planetary Operations Control Center (SPOCC) utilizes GMSEC as the hub for it's automation and situational awareness capability Shifts focus towards getting GS to a final configuration-managed baseline, as well as multi-mission / big-picture capabilities that help increase situational awareness, promote cross-mission sharing and establish enhanced fleet management capabilities across all levels of the enterprise.

GMSEC↗
NASA NTRS2012

Scalable Integrated Multi-Mission Support System Simulator Release 3.0

The Scalable Integrated Multi-mission Support System (SIMSS) is a tool that performs a variety of test activities related to spacecraft simulations and ground segment checks. SIMSS is a distributed, component-based, plug-and-play client-server system useful for performing real-time monitoring and communications testing. SIMSS runs on one or more workstations and is designed to be user-configurable or to use predefined configurations for routine operations. SIMSS consists of more than 100 modules that can be configured to create, receive, process, and/or transmit data. The SIMSS/GMSEC innovation is intended to provide missions with a low-cost solution for implementing their ground systems, as well as significantly reducing a mission s integration time and risk.

Kim, John↗