SEARCH · Search NASA

Results for “Mission Operations”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 595 records · Page 33

All sources NASA NTRS DOE OSTI

NASA NTRS1973

Study 2.6 operations analysis mission characterization

An analysis of the current operations concepts of NASA and DoD is presented to determine if alternatives exist which may improve the utilization of resources. The final product is intended to show how sensitive these ground rules and design approaches are relative to the total cost of doing business. The results are comparative in nature, and assess one concept against another as opposed to establishing an absolute cost value for program requirements. An assessment of the mission characteristics is explained to clarify the intent, scope, and direction of this effort to improve the understanding of what is to be accomplished. The characterization of missions is oriented toward grouping missions which may offer potential economic benefits by reducing overall program costs. Program costs include design, development, testing, and engineering, recurring unit costs for logistic vehicles, payload costs. and direct operating costs.

Wolfe, R. R.↗

NASA NTRSDate not supplied

IMPACT, A Tool Suite for Crew Health and Performance System Trade Analyses and Decision Support- Transition to Operations

Mission planners, systems engineers, and clinicians that support crew health and performance face very difficult choices on upcoming exploration missions. Given that there will be a heavily constrained mass and volume allocation for a medical system on these missions, what medical capability should be manifested to minimize both medical risk and mission risk? Given that not all promising research and technology proposals can be funded, how can proposals be prioritized so that those funded research investments produce the maximum benefit in reducing overall medical risk? The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project seeks to answer these kinds of questions and others to support upcoming exploration missions. IMPACT enables risk-informed and evidence-based trade space analysis for future space vehicles, missions, and systems. This presentation will discuss the long-term HRP and ExMC vision for the larger ecosystem of tools, which include an updated medical database, consisting of an Evidence Library for medical conditions and a medical item database (MedID) for medical resources, dynamic Probabilistic Risk Assessment (PRA) capabilities, System Modeling Language (SysML) models, and contextual data visualizations of output data. IMPACT is the result of a multi-center collaborative effort. The trade space analyses performed by IMPACT can directly inform mission, vehicle, and habitat development by quantifying medical risk, given a design reference mission, crew attributes and a set of medical capabilities. This presentation will update the audience on the development status of the IMPACT tool suite as it comes out of its System Acceptance Review (SAR) and nears Transition to Operations (TTO). It will review IMPACT’s constituent parts, briefly discuss typical outputs, and outline the plans for transitioning to operations, currently scheduled for later in FY24. Recent development successes on the IMPACT project include the integration of the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) v2.0 to accommodate segmented missions with multiple carriers and medical systems, full onboarding of the IMPACT Medical Database (IMPACT-MD), clustering medical resources and skills into medical capabilities and mutually-dependent bundles, verification of IMPACT-MD, and the ability to perform trade analyses on different medical sets, different design reference missions (DRM), with different crew complements and extra-vehicular activity (EVA) schedules.

IMPACT↗

NASA NTRS1967

AS-206 S-4B restart alternate mission L/V operational flight trajectory, part 3

Saturn S-4B restart alternate mission launch vehicle operational flight trajectory - AS-206 vehicle systems integration

Barrett, B. B.↗

NASA NTRSDate not supplied

Impact, A Tool Suite for Crew Health and Performance System Trade Analyses and Decision to Support - Transition to Operations

IMPACT↗

NASA NTRS2012

Principles to Products: Toward Realizing MOS 2.0

This is a report on the Operations Revitalization Initiative, part of the ongoing NASA-funded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element...) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.

AMMOS↗

NASA NTRS1993

Connecting science and operations: The operations coordinator

For a current space mission under development at the Applied Physics Laboratory, the Mission Operations staff includes a team of 'Operations Coordinators' who have been working with the Mission Science and Spacecraft Development teams since completion of mission conceptual design. The Operations Coordinators are responsible for bringing knowledge of the spacecraft to the Mission Science team and bringing knowledge of the experiment requirements to the Spacecraft Development and Mission Operations teams. Once on-orbit operations begin, the Operations Coordinators will be responsible for implementation of specific science experiments from analysis through scheduling, generation of spacecraft command sequences, delivery of science data to the end user, and operations assessment. The Operations Coordinator concept is proving very effective during the development phase of the current mission.

Marshall, Madeleine H.↗

NASA NTRS2006

Leveraging Existing Mission Tools in a Re-Usable, Component-Based Software Environment

Emerging methods in component-based software development offer significant advantages but may seem incompatible with existing mission operations applications. In this paper we relate our positive experiences integrating existing mission applications into component-based tools we are delivering to three missions. In most operations environments, a number of software applications have been integrated together to form the mission operations software. In contrast, with component-based software development chunks of related functionality and data structures, referred to as components, can be individually delivered, integrated and re-used. With the advent of powerful tools for managing component-based development, complex software systems can potentially see significant benefits in ease of integration, testability and reusability from these techniques. These benefits motivate us to ask how component-based development techniques can be relevant in a mission operations environment, where there is significant investment in software tools that are not component-based and may not be written in languages for which component-based tools even exist. Trusted and complex software tools for sequencing, validation, navigation, and other vital functions cannot simply be re-written or abandoned in order to gain the advantages offered by emerging component-based software techniques. Thus some middle ground must be found. We have faced exactly this issue, and have found several solutions. Ensemble is an open platform for development, integration, and deployment of mission operations software that we are developing. Ensemble itself is an extension of an open source, component-based software development platform called Eclipse. Due to the advantages of component-based development, we have been able to vary rapidly develop mission operations tools for three surface missions by mixing and matching from a common set of mission operation components. We have also had to determine how to integrate existing mission applications for sequence development, sequence validation, and high level activity planning, and other functions into a component-based environment. For each of these, we used a somewhat different technique based upon the structure and usage of the existing application.

Greene, Kevin↗

NASA NTRS2014

The Cassini Solstice Mission: Streamlining Operations by Sequencing with PIEs

The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks, with 6 overlapping processes.

Vandermey, Nancy↗

NASA NTRS2008

Juno Mission Simulation

The Juno spacecraft is planned to launch in August of 2012 and would arrive at Jupiter four years later. The spacecraft would spend more than one year orbiting the planet and investigating the existence of an ice-rock core; determining the amount of global water and ammonia present in the atmosphere, studying convection and deep- wind profiles in the atmosphere; investigating the origin of the Jovian magnetic field, and exploring the polar magnetosphere. Juno mission management is responsible for mission and navigation design, mission operation planning, and ground-data-system development. In order to ensure successful mission management from initial checkout to final de-orbit, it is critical to share a common vision of the entire mission operation phases with the rest of the project teams. Two major challenges are 1) how to develop a shared vision that can be appreciated by all of the project teams of diverse disciplines and expertise, and 2) how to continuously evolve a shared vision as the project lifecycle progresses from formulation phase to operation phase. The Juno mission simulation team addresses these challenges by developing agile and progressive mission models, operation simulations, and real-time visualization products. This paper presents mission simulation visualization network (MSVN) technology that has enabled a comprehensive mission simulation suite (MSVN-Juno) for the Juno project.

space vehicles↗

NASA NTRS2019

Insight Mission: early operations

This paper will describe the InSight mission and science objectives with a focus on the activities since the May 5, 2018 Launch including the InSight Mission Design, Navigation, and Cruise Phase Instrument check-out and the plans for the November Entry, Decent and Landing and Instrument Deployment Phases.

Imken, Travis↗

NASA NTRS2003

A Subjective Assessment of Alternative Mission Architecture Operations Concepts for the Human Exploration of Mars at NASA Using a Three-Dimensional Multi-Criteria Decision Making Model

The primary driver for developing missions to send humans to other planets is to generate significant scientific return. NASA plans human planetary explorations with an acceptable level of risk consistent with other manned operations. Space exploration risks can not be completely eliminated. Therefore, an acceptable level of cost, technical, safety, schedule, and political risks and benefits must be established for exploratory missions. This study uses a three-dimensional multi-criteria decision making model to identify the risks and benefits associated with three alternative mission architecture operations concepts for the human exploration of Mars identified by the Mission Operations Directorate at Johnson Space Center. The three alternatives considered in this study include split, combo lander, and dual scenarios. The model considers the seven phases of the mission including: 1) Earth Vicinity/Departure; 2) Mars Transfer; 3) Mars Arrival; 4) Planetary Surface; 5) Mars Vicinity/Departure; 6) Earth Transfer; and 7) Earth Arrival. Analytic Hierarchy Process (AHP) and subjective probability estimation are used to captures the experts belief concerning the risks and benefits of the three alternative scenarios through a series of sequential, rational, and analytical processes.

Tavana, Madjid↗

NASA NTRSDate not supplied

Goddard Mission Services Evolution Center “GMSEC” Overview

In today's changing satellite mission operations landscape, the need for mission automation and interoperability while containing costs is more important than ever. Enter GMSEC – a flexible and extendible set of software automation tools designed to automate repetitive processes and off-hours alerting, among others. GMSEC is also an API that is open source and supports the OMG C2MS message specification, allowing dissimilar components to communicate with each other. Attendees will learn about the possible use cases for automation that the GMSEC architecture and suite of components enable. The presentation will provide an overview of specific GMSEC software products that provide these automation features such as the GMSEC Generic Extendible Message Utility (GEMU) that enables automation, and GMSEC Services Suite OpenMCT (GSS) that offers enhanced telemetry visualization. This presentation will outline how GMSEC can enable and enhance mission operations automation, enabling efficiencies that can help bring down costs.

James C. Hoffman↗

NASA NTRS1978

Payload integration and operations

Integration and operation of Spacelab payloads presents major challenges to engineering disciplines in areas of ground operations and flight mission operations. The integration of ground operations encompasses activities performed by the instrument developers and principal investigators and by the centralized payload integration site and launch site. The payload will be operated on orbit by a payload crew trained in payload experimentation and by a payload operations control center where investigator science groups and operations personnel are prepared to provide support. The payload mission planning, control center, data processing facility and operations are developed and verified prior to realtime flight operations. The mission management approach to minimize program costs and impacts to payloads and the Space Transportation System/Spacelab accommodations is presented.

Hall, R. R.↗

NASA NTRS2022

Benefits and Challenges of CCSDS File Delivery Protocol as Applied to Europa Clipper

—This paper describes the use of the Consultative Committee for Space Data Systems (CCSDS) File Delivery Protocol (CFDP) on the Europa Clipper mission for both uplink and downlink of files. It includes an overview of CFDP, the history of why CFDP was chosen, how it benefits mission operations, some of the mission scenarios that stress CFDP, operability aspects, the best practices that Clipper adopted from other missions and some of the technical challenges with implementation, and verification and validation. The benefits to mission operations accrue because CFDP reduces the need for manual management of file transfer, including retransmission of missing data, and deletion of files only after confirmation of receipt by the ground. The challenges occur because CFDP is a round-trip protocol – it requires messages in both directions to complete a file transfer, and because it uses timers to ensure that control messages are resent if needed to prevent transactions from going stale. Any situations where communication is restricted to a single direction, interrupted, reordered, or backlogged can pose a challenge. There are also implementation challenges. Europa Clipper is the first mission at the Jet Propulsion Laboratory (JPL) to adopt class 2, fully acknowledged, CFDP for both uplink and downlink. The implementation needed new software, requirements and operational procedures. The experience of the Applied Physics Laboratory (APL) with CFDP from their previous missions was crucial to success for Europa Clipper. Because CFDP relies on timers and messages travel in both directions, verification and validation (V&V) requires new approaches. For certain scenarios, a live ground system talking to a live flight system with realistic simulated one-way light times, data rates and data outages must be used.

Albers, Joshua↗

NASA NTRS2012

Mission Analysis, Operations, and Navigation Toolkit Environment (Monte) Version 040

Monte is a software set designed for use in mission design and spacecraft navigation operations. The system can process measurement data, design optimal trajectories and maneuvers, and do orbit determination, all in one application. For the first time, a single software set can be used for mission design and navigation operations. This eliminates problems due to different models and fidelities used in legacy mission design and navigation software. The unique features of Monte 040 include a blowdown thruster model for GRAIL (Gravity Recovery and Interior Laboratory) with associated pressure models, as well as an updated, optimalsearch capability (COSMIC) that facilitated mission design for ARTEMIS. Existing legacy software lacked the capabilities necessary for these two missions. There is also a mean orbital element propagator and an osculating to mean element converter that allows long-term orbital stability analysis for the first time in compiled code. The optimized trajectory search tool COSMIC allows users to place constraints and controls on their searches without any restrictions. Constraints may be user-defined and depend on trajectory information either forward or backwards in time. In addition, a long-term orbit stability analysis tool (morbiter) existed previously as a set of scripts on top of Monte. Monte is becoming the primary tool for navigation operations, a core competency at JPL. The mission design capabilities in Monte are becoming mature enough for use in project proposals as well as post-phase A mission design. Monte has three distinct advantages over existing software. First, it is being developed in a modern paradigm: object- oriented C++ and Python. Second, the software has been developed as a toolkit, which allows users to customize their own applications and allows the development team to implement requirements quickly, efficiently, and with minimal bugs. Finally, the software is managed in accordance with the CMMI (Capability Maturity Model Integration), where it has been ap praised at maturity level 3.

Sunseri, Richard F.↗

NASA NTRSDate not supplied

Estimation of Timing Performance with Pulsed Laser Links for Small Satellite PNT

Satellite constellations are growing in size and in utility for applications as diverse as providing reliable, low-latency internet service to rural areas orEarth science missions.This expansion of satellite constellations brings attention to the need for responsive and reliable satellite communication.Current research in the PrecisionSpace Systems Laboratory at the University of Florida focuses on using pulsed laser communications as the method of relaying time signals instead of the radio frequency (RF)signals.The upcoming CLICK (CubeSat Laser Infrared CrosslinK) missions (Massachusetts Institute of Technology, University of Florida, NASA Ames Research Center) will demonstrate a spacecraft-to-spacecraft laser communication link and time-transfer.For pre-flight technology assessment of missions such as CLICK, a simulation of a spacecraft constellation in Earth orbit has been created to estimate clock synchronization and precision orbit determination based on measured instrumentation performance.We have developed a novel MATLAB-based numerical simulator to model spacecraft-to-spacecraft laser time-transfer and estimate the offset between the spacecraft clocks over time.This simulation includes timing errors associated with laser pulse generation and detection, as well as non-Gaussian clock drift models.The two on-board clocks modeled are a cesium-based Chip-Scale Atomic Clock (CSAC) and a rubidium-based Miniature Atomic Clock (MAC), both produced by Microchip.An example case of two spacecraft in a circular, low-Earth orbit receiving GPS position, GPS timing, and laser pulse time-of-flight measurements is simulated.The positions and velocities of the two spacecraft at a reference epoch and the constant clock model coefficients are estimated.Polynomial models of different orders were used as clock models. The effect of clock model order on the root-mean-square (RMS) of the clock error is apparent in the case using GPS and lasing measurements, showing that the clock model improves with increasing clock model order. Results compare the estimated clock model of a mission operation that only uses GPS measurements and a mission operation that uses both GPS and laser pulse time-of-flight measurements between spacecraft referenced to their on-board CSACs or on-board MACs. Including lasing measurements reduces the RMS clock model error by approximately 80% of the RMS of the cases with only GPS measurements.This simulation tool can be used to optimize the lasing operations schedule based on mission timing performance objectives. During this presentation, I will discuss the details of the simulation and clock model estimation, as well as discuss the results.I will compare the results of incorporating lasing timing measurements to using only GPS measurements and the outcomes of using different orders of polynomials.

Timing Performance↗

NASA NTRS1993

Magellan spacecraft and memory state tracking: Lessons learned, future thoughts

Numerous studies have been dedicated to improving the two main elements of Spacecraft Mission Operations: Command and Telemetry. As a result, not much attention has been given to other tasks that can become tedious, repetitive, and error prone. One such task is Spacecraft and Memory State Tracking, the process by which the status of critical spacecraft components, parameters, and the contents of on-board memory are managed on the ground to maintain knowledge of spacecraft and memory states for future testing, anomaly investigation, and on-board memory reconstruction. The task of Spacecraft and Memory State Tracking has traditionally been a manual task allocated to Mission Operations Procedures. During nominal Mission Operations this job is tedious and error prone. Because the task is not complex and can be accomplished manually, the worth of a sophisticated software tool is often questioned. However, in the event of an anomaly which alters spacecraft components autonomously or a memory anomaly such as a corrupt memory or flight software error, an accurate ground image that can be reconstructed quickly is a priceless commodity. This study explores the process of Spacecraft and Memory State Tracking used by the Magellan Spacecraft Team highlighting its strengths as well as identifying lessons learned during the primary and extended missions, two memory anomalies, and other hardships encountered due to incomplete knowledge of spacecraft states. Ideas for future state tracking tools that require minimal user interaction and are integrated into the Ground Data System will also be discussed.

Bucher, Allen W.↗

NASA NTRS1998

Beacon Monitor Operations on the Deep Space One Mission

A new approach to mission operations will be flight validated on NASA's New Millennium Program Deep Space One (DS1) mission scheduled to lauch in October 01 1998.

Beacon Monitor Deep Space One DS1↗