Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 1,009 records · Page 56
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

ISS Operations Cost Reductions Through Automation of Real-Time Planning Tasks

In 2007 the Johnson Space Center s Mission Operations Directorate (MOD) management team challenged their organizations to find ways to reduce the cost of operations for supporting the International Space Station (ISS) in the Mission Control Center (MCC). Each MOD organization was asked to define and execute projects that would help them attain cost reductions by 2012. The MOD Operations Division Flight Planning Branch responded to this challenge by launching several software automation projects that would allow them to greatly improve console operations and reduce ISS console staffing and intern reduce operating costs. These tasks ranged from improving the management and integration mission plan changes, to automating the uploading and downloading of information to and from the ISS and the associated ground complex tasks that required multiple decision points. The software solutions leveraged several different technologies including customized web applications and implementation of industry standard web services architecture; as well as engaging a previously TRL 4-5 technology developed by Ames Research Center (ARC) that utilized an intelligent agent-based system to manage and automate file traffic flow, archive data, and generate console logs. These projects to date have allowed the MOD Operations organization to remove one full time (7 x 24 x 365) ISS console position in 2010; with the goal of eliminating a second full time ISS console support position by 2012. The team will also reduce one long range planning console position by 2014. When complete, these Flight Planning Branch projects will account for the elimination of 3 console positions and a reduction in staffing of 11 engineering personnel (EP) for ISS.

Hall, Timothy A.↗
NASA NTRS1972

Fan noise and performance

Tradeoffs between aerodynamic and acoustic properties of various fan configurations led to the selection of a variety of fans that produce noise levels in the range of 100 to 120 PNdb. Fan configuration and design pressure ratio required for specific mission operations depend in part on the type of mission to be performed. Noise data obtained for single-stage low speed fans, single-stage high speed fans, and two-stage fan engines are presented in table form.

Kramer, J. J.↗
NASA NTRS1985

The Orbital Maneuvering Vehicle - Extending the reach of the space transportation system

This paper describes the Orbital Maneuvering Vehicle (OMV) concept and its intended role. It recaps the past activities leading up to the current concept and summarizes the present status and plans. The various types of missions, operating modes, and performance capability are described. Typical mission scenarios for servicing missions from both the Shuttle and the Space Station are described.

Bekey, I.↗
NASA NTRS1990

CLEAR: Automating control centers with expert system technology

The Communications Link Expert Assistance Resource (CLEAR) is a fault-isolation expert system to be utilized in the operational environment of the Cosmic Background Explorer (COBE) Mission Operations Room (MOR). CLEAR will assist the COBE Flight Operations Team (FOT) during periods of real-time data acquisition by isolating faults in the spacecraft communication link with the Tracking and Data Relay Satellite (TDRS), providing advice on how to correct them, and logging the events for post-pass evaluation. After a brief introduction to the problem domain, the system requirements, tool selection, development approach, system operation and lessons learned during the transformation of the system from the prototype to the delivered, operation system are described.

Hughes, Peter M.↗
NASA NTRS1988

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↗
NASA NTRS1994

Grand mission versus small OPS team: Can we have both?

Space Missions are growing more ambitious, but resources are getting smaller. Is this is a contradiction in terms, or is it a healthy challenge? This paper offers the author's point of view as a member of a small Mission Operations Team that carries out an ambitious international mission (Ulysses ESA/NASA).

Garcia-Perez, Raul↗
NASA NTRS1994

The navigation toolkit

This report summarizes the experience of the authors in managing, designing, and implementing an object-oriented applications framework for orbital navigation analysis for the Flight Design and Dynamics Department of the Rockwell Space Operations Company in Houston, in support of the Mission Operations Directorate of NASA's Johnson Space Center. The 8 person year project spanned 1.5 years and produced 30,000 lines of C++ code, replacing 150,000 lines of Fortran/C. We believe that our experience is important because it represents a 'second project' experience and generated real production-quality code - it was not a pilot. The project successfully demonstrated the use of 'continuous development' or rapid prototyping techniques. Use of formal methods and executable models contributed to the quality of the code. Keys to the success of the project were a strong architectural vision and highly skilled workers. This report focuses on process and methodology, and not on a detailed design description of the product. But the true importance of the object-oriented paradigm is its liberation of the developer to focus on the problem rather than the means used to solve the problem.

Rich, William F.↗
NASA NTRS2010

Exploration Roadmap Working Group (ERWG) Data Collection, NASA's Inputs

This slide presentation reviews four areas for further space exploration: (1) Human Exploration of Mars Design Reference Architecture (DRA) 5.0, (2) Robotic Precursors targeting Near Earth Objects (NEO) for Human Exploration, (3) Notional Human Exploration of Near Earth Objects and (4) Low Earth Orbit (LEO) Refueling to Augment Human Exploration. The first presentation reviews the goals and objectives of the Mars DRA, presents a possible mission profile, innovation requirements for the mission and key risks and challenges for human exploration of Mars. The second presentation reviews the objective and goals of the robotic precursors to the NEO and the mission profile of such robotic exploration. The third presentation reviews the mission scenario of human exploration of NEO, the objectives and goals, the mission operational drivers, the key technology needs and a mission profile. The fourth and last presentation reviews the examples of possible refueling in low earth orbit prior to lunar orbit insertion, to allow for larger delivered payloads for a lunar mission.

Drake, Bret↗
NASA NTRS2014

Trades Between Opposition and Conjunction Class Trajectories for Early Human Missions to Mars

Candidate human missions to Mars, including NASA's Design Reference Architecture 5.0, have focused on conjunction-class missions with long crewed durations and minimum energy trajectories to reduce total propellant requirements and total launch mass. However, in order to progressively reduce risk and gain experience in interplanetary mission operations, it may be desirable that initial human missions to Mars, whether to the surface or to Mars orbit, have shorter total crewed durations and minimal stay times at the destination. Opposition-class missions require larger total energy requirements relative to conjunction-class missions but offer the potential for much shorter mission durations, potentially reducing risk and overall systems performance requirements. This paper will present a detailed comparison of conjunction-class and opposition-class human missions to Mars vicinity with a focus on how such missions could be integrated into the initial phases of a Mars exploration campaign. The paper will present the results of a trade study that integrates trajectory/propellant analysis, element design, logistics and sparing analysis, and risk assessment to produce a comprehensive comparison of opposition and conjunction exploration mission constructs. Included in the trade study is an assessment of the risk to the crew and the trade offs between the mission duration and element, logistics, and spares mass. The analysis of the mission trade space was conducted using four simulation and analysis tools developed by NASA. Trajectory analyses for Mars destination missions were conducted using VISITOR (Versatile ImpulSive Interplanetary Trajectory OptimizeR), an in-house tool developed by NASA Langley Research Center. Architecture elements were evaluated using EXploration Architecture Model for IN-space and Earth-to-orbit (EXAMINE), a parametric modeling tool that generates exploration architectures through an integrated systems model. Logistics analysis was conducted using NASA's Human Exploration Logistics Model (HELM), and sparing allocation predictions were generated via the Exploration Maintainability Analysis Tool (EMAT), which is a probabilistic simulation engine that evaluates trades in spacecraft reliability and sparing requirements based on spacecraft system maintainability and reparability.

Mattfeld, Bryan↗
NASA NTRS2015

Multi-Spacecraft Autonomous Positioning System

As the number of spacecraft in simultaneous operation continues to grow, there is an increased dependency on ground-based navigation support. The current baseline system for deep space navigation utilizes Earth-based radiometric tracking, requiring long-duration observations to perform orbit determination and generate a state update. The age, complexity, and high utilization of the ground assets pose a risk to spacecraft navigation performance. In order to perform complex operations at large distances from Earth, such as extraterrestrial landing and proximity operations, autonomous systems are required. With increasingly complex mission operations, the need for frequent and Earth-independent navigation capabilities is further reinforced. The Multi-spacecraft Autonomous Positioning System (MAPS) takes advantage of the growing interspacecraft communication network and infrastructure to allow for Earth-autonomous state measurements to enable network-based space navigation. A notional concept of operations is given in figure 1. This network is already being implemented and routinely used in Martian communications through the use of the Mars Reconnaissance Orbiter and Mars Odyssey spacecraft as relays for surface assets. The growth of this communications architecture is continued through MAVEN, and future potential commercial Mars telecom orbiters. This growing network provides an initial Marslocal capability for inter-spacecraft communication and navigation. These navigation updates are enabled by cross-communication between assets in the network, coupled with onboard navigation estimation routines to integrate packet travel time to generate ranging measurements. Inter-spacecraft communication allows for frequent state broadcasts and time updates from trusted references. The architecture is a software-based solution, enabling its implementation on a wide variety of current assets, with the operational constraints and measurement accuracy determined by onboard systems.

Anzalone, Evan↗
NASA NTRS2017

XTCE (XML Telemetric and Command Exchange) Standard Making It Work at NASA. Can It Work For You?

The XML Telemetric and Command Exchange (XTCE) standard is intended as a way to describe telemetry and command databases to be exchanged across centers and space agencies. XTCE usage has the potential to lead to consolidation of the Mission Operations Center (MOC) Monitor and Control displays for mission cross-support, reducing equipment and configuration costs, as well as a decrease in the turnaround time for telemetry and command modifications during all the mission phases. The adoption of XTCE will reduce software maintenance costs by reducing the variation between our existing mission dictionaries. The main objective of this poster is to show how powerful XTCE is in terms of interoperability across centers and missions. We will provide results for a use case where two centers can use their local tools to process and display the same mission telemetry in their MOC independently of one another. In our use case we have first quantified the ability for XTCE to capture the telemetry definitions of the mission by use of our suite of support tools (Conversion, Validation, and Compliance measurement). The next step was to show processing and monitoring of the same telemetry in two mission centers. Once the database was converted to XTCE using our tool, the XTCE file became our primary database and was shared among the various tool chains through their XTCE importers and ultimately configured to ingest the telemetry stream and display or capture the telemetered information in similar ways.Summary results include the ability to take a real mission database and real mission telemetry and display them on various tools from two centers, as well as using commercially free COTS.

CCSDS↗
NASA NTRS2017

FY18 SSC Agile-Seedling Fund Opportunities

The attached charts provide some background on an SSC (Stennis Space Center) initiative to support employees who may have ideas for technology development efforts but haven't been engaged in writing proposals to sources such as the Center Innovation Fund and other STMD (NASA Space Technology Mission Directorate) or HEOMD (NASA Human Exploration and Operations Mission Directorate) solicitation calls.

Travis, Ramona↗
NASA NTRS2018

Increased Operational Availability and Simplified Operations Using Dither Gyro Scale Factor Calibration

The traditional approach to on-orbit gyro scale factor calibration has been to perform large angle rotations about each gyro axis. The maneuvers require the science instruments to be taken offline, reducing operational availability and require a significant amount of interaction from the ground. To increase operational availability and to reduce the burden on mission operators, a novel approach to gyro scale factor calibration was developed, modeled and successfully demonstrated on the Geostationary Operational Environmental Satellite (GOES-16) to estimate gyro scale factor errors to within 1500 parts per million (ppm) without taking the science instruments offline.

Reth, Alan D.↗
NASA NTRS2018

Training for Mars

Spaceflight training for Apollo era and Space Shuttle missions was designed to train crew on specific tasks for their short duration missions. The training mottos included "practice, practice, practice" and "hammering it in." However, training for longer duration ISS (International Space Station) missions has been more challenging. There is clear documentation that tasks and skills trained pre-flight are not all retained throughout the mission, and this lack of training retention is augmented with real-time ground support. NASA does not currently have a training design that supports semi-autonomous to autonomous mission operations. The current design of a manned Mars mission calls for a 32-month long mission and asynchronous communication involving long delays.

Barshi, Immanuel↗
NASA NTRS2006

Medical Operations Console Procedure Evaluation: BME Response to Crew Call Down for an Emergency

International Space Station (ISS) Mission Operations are managed by multiple flight control disciplines located at the lead Mission Control Center (MCC) at NASA-Johnson Space Center (JSC). ISS Medical Operations are supported by the complementary roles of Flight Surgeons (Surgeon) and Biomedical Engineer (BME) flight controllers. The Surgeon, a board certified physician, oversees all medical concerns of the crew and the BME provides operational and engineering support for Medical Operations Crew Health Care System. ISS Medical Operations is currently addressing the coordinated response to a crew call down for an emergent medical event, in particular when the BME is the only Medical Operations representative in MCC. In this case, the console procedure BME Response to Crew Call Down for an Emergency will be used. The procedure instructs the BME to contact a Surgeon as soon as possible, coordinate with other flight disciplines to establish a Private Medical Conference (PMC) for the crew and Surgeon, gather information from the crew if time permits, and provide Surgeon with pertinent console resources. It is paramount that this procedure is clearly written and easily navigated to assist the BME to respond consistently and efficiently. A total of five BME flight controllers participated in the study. Each BME participant sat in a simulated MCC environment at a console configured with resources specific to the BME MCC console and was presented with two scripted emergency call downs from an ISS crew member. Each participant used the procedure while interacting with analog MCC disciplines to respond to the crew call down. Audio and video recordings of the simulations were analyzed and each BME participant's actions were compared to the procedure. Structured debriefs were conducted at the conclusion of both simulations. The procedure was evaluated for its ability to elicit consistent responses from each BME participant. Trials were examined for deviations in procedure task completion and/or navigation, in particular the execution of the Surgeon call sequence. Debrief comments were used to analyze unclear procedural steps and to discern any discrepancies between the procedure and generally accepted BME actions. The sequence followed by BME participants differed considerably from the sequence intended by the procedure. Common deviations included the call sequence used to contact Surgeon, the content of BME and crew interaction and the gathering of pertinent console resources. Differing perceptions of task priority and imprecise language seem to have caused multiple deviations from the procedure s intended sequence. The study generated 40 recommendations for the procedure, of which 34 are being implemented. These recommendations address improving the clarity of the instructions, identifying training considerations, expediting Surgeon contact, improving cues for anticipated flight control team communication and identifying missing console tools.

Johnson-Troop↗
NASA NTRS1993

Distributed science operations for JPL planetary missions

Advances in spacecraft, flight instruments, and ground systems provide an impetus and an opportunity for scientific investigation teams to take direct control of their instruments' operations and data collection while at the same time, providing a cost effective and flexible approach in support of increasingly complex science missions. Operations of science instruments have generally been integrated into planetary flight and ground systems at a very detailed level. That approach has been successful, but the cost of incorporating instrument expertise into the central mission operations system has been high. This paper discusses an approach to simplify planetary science operations by distributing instrument computing and data management tasks from the central mission operations system to each investigator's home center of observational expertise. Some early results of this operations concept will be presented based on the Mars Observer (MO) Project experience and Cassini Project plans.

Benson, Richard D.↗
NASA NTRS2014

Usability of Operational Performance Support Tools - Findings from Sea Test II

Sea Test II, aka NASA Extreme Environment Mission Operations 17(NEEMO 17) took place in the Florida Aquarius undersea habitat. This confined underwater environment provides a excellent analog for space habitation providing similarities to space habitation such as hostile environment, difficult logistics, autonomous operations, and remote communications. This study collected subjective feedback on the usability of two performance support tools during the Sea Test II mission, Sept 10‐14, 2013; Google Glass and iPAD. The two main objectives: - Assess the overall functionality and usability of each performance support tool in a mission analog environment. - Assess the advantages and disadvantages of each tool when performing operational procedures and Just‐In‐Time‐Training (JITT).

Byrne, Vicky↗
NASA NTRSDate not supplied

Lessons Learned from Medical System Foundation Development for Long-Duration Lunar Orbit and Lunar Surface Missions

The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has been tasked with the development of Medical System Foundations for Level of Care IV for both short-duration lunar orbital missions and, subsequently, long-duration lunar orbital and surface operations missions. These Medical System Foundations serve as a framework to aid in early medical system design and mission planning. The content of both Foundation models is similar, consisting of a concept of operations, functional decomposition, clinical content (medical conditions, capabilities, and resources), technical requirements (interface, non-functional, and functional), and traces between these components and to the NASA standards documents and parent-level (Program- and Vehicle habitat system-level) requirements. Additionally, the development of both Foundations employed systems engineering principles and a model-based systems engineering (MBSE) approach. Throughout the development of these Foundations, ExMC has strived to improve the efficiency and robustness of its processes and to be more responsive to change (i.e., in design reference mission parameters and assumptions) and to stakeholders’ feedback. The most significant improvements made between the short- and long-duration Foundation models during this transformation process are the following: • Replacement of the traditional document-based ConOps with a model-based ConOps according to MBSE principles, which facilitated more efficient understanding of the material and the consolidation of all relevant information into a centralized location. • Utilization of an agile approach with tasks organized into sprints. This approach enabled solicitation of more frequent usability feedback from stakeholders, incorporation of more human factors reviews into the sprints, and more efficient tasking of team members. This presentation will discuss the journey of developing both Foundation models, as well as the lessons learned and resulting improvements made between the Short- and Long-Duration models.

M Kaetzer↗