SEARCH · Engineering Papers
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.
This Instruction establishes responsibilities for managing the system whereby operational support requirements are levied for support of manned flight missions including associated payloads. This management system will ensure that support requirements are properly requested and responses are properly obtained to meet operational objectives.
Operational ground support equipment for Voyager project, including data handling system, launch complex equipment, system test complex, and mission dependent equipment
Life Cycle Cost (LCC) estimates during the proposal and early design phases, as well as project replans during the development phase, are heavily focused on hardware development schedules and costs. Operations (phase E) costs are typically small compared to the spacecraft development and test costs. This, combined with the long lead time for realizing operations costs, can lead to de-emphasizing estimation of operations support requirements during proposal, early design, and replan cost exercises. The Discovery and New Frontiers (D&NF) programs comprise small, cost-capped missions supporting scientific exploration of the solar system. Any LCC growth can directly impact the programs' ability to fund new missions, and even moderate yearly underestimates of the operations costs can present significant LCC impacts for deep space missions with long operational durations. The National Aeronautics and Space Administration (NASA) D&NF Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that 4 out of the 5 missions studied had significant overruns at or after launch due to underestimation of the complexity and supporting requirements for operations activities; the fifth mission had not launched at the time of the mission. The drivers behind these overruns include overly optimistic assumptions regarding the savings resulting from the use of heritage technology, late development of operations requirements, inadequate planning for sustaining engineering and the special requirements of long duration missions (e.g., knowledge retention and hardware/software refresh), and delayed completion of ground system development work. This paper updates the D&NF LCC study, looking at the operations (phase E) cost drivers in more detail and extending the study to include 2 additional missions and identifies areas for increased emphasis by project management in order to improve the fidelity of operations estimates.
During the 1960's, the United States X-15 rocket-plane research program successfully demonstrated the ability to support a reusable vehicle operating in a near-space environment. The similarity of the proposed HL-20 lifting body concept in general size, weight, and subsystem composition to that of the X-15 provided an opportunity for a comparison of the predicted support manpower and turnaround times with those experienced in the X-15 program. Information was drawn from both reports and discussions with X-15 program personnel to develop comparative operations and support data. Based on the assumption of comparability between the two systems, the predicted staffing levels, skill mix, and refurbishment times of an operational HL-20 appear to be similar to those experienced by the X-15 for ground support. However, safety, environmental, and support requirements have changed such that the HL-20 will face a different operating environment than existed at Edwards during the 1950's and 1960's. Today's operational standards may impose additional requirements on the HL-20 that will add to the maintenance and support burden estimate based on the X-15 analogy.
The key heating, ventilation, and air-conditioning (HVAC) modifications implemented at the Mars Deep Space Station's Operation Support Building at Jet Propulsion Laboratories (JPL) in order to reduce energy consumption and decrease operating costs are described. An energy analysis comparison between the computer simulated model for the building and the actual meter data was presented. The measurement performance data showed that the cumulative energy savings was about 21% for the period 1979 to 1981. The deviation from simulated data to measurement performance data was only about 3%.
Real-time auxiliary computing facility for operational support of Apollo 5 flight
To support the medical research and the maintenance of crew health during the three Skylab missions, a medical operational support team was organized. The functions of this team ranged from medical data management to medical systems engineering monitoring during the flights. The capability to expand preflight and postflight medical research and analysis was supplied through the use of the Skylab mobile laboratories. These mobile laboratories were not only capable of being transported to the recovery ship for postflight use, but also served as a preflight test area for gathering crewman baseline data. The laboratories contained experiment hardware identical to that of the flight orbital workshop and a laboratory diagnostic facility that duplicated many of the capabilities of ground-based clinical laboratories.
The James Webb Space Telescope (JWST) was launched from Kourou Spaceport on December 25, 2021, at 12:20 UTC on an Ariane 5 launch vehicle. The launch vehicle inserted JWST into a 30-day transfer trajectory to the Sun-Earth-Moon (SEM) Lagrange point L2 region. JWST executed three mid-course correction maneuvers (MCCs) to insert the spacecraft into a quasi-halo orbit about SEM L2; JWST will maintain its trajectory about L2 for at least 5.5 years, with a goal of at least 10.5 years. This paper summarizes the flight dynamics support for JWST, including the prelaunch nominal trajectory design, the launch window analysis, contingency planning for trajectory-related anomalies, mission operations support for the first 6 months, and a comparison of the planned and achieved actual JWST trajectory results. The orbit determination strategy, both planned and executed, will be summarized, and the method of addressing the anomalies as they occurred will be included.
The James Webb Space Telescope (JWST) was launched from Kourou Spaceport on December 25, 2021, at 12:20 UTC on an Ariane 5 launch vehicle. The launch vehicle inserted JWST into a 30-day transfer trajectory to the Sun-Earth-Moon (SEM) Lagrange point L2 region. JWST executed three mid-course correction maneuvers (MCCs) to insert the spacecraft into a quasi-halo orbit about SEM L2; JWST will maintain its trajectory about L2 for at least 5.5 years, with a goal of at least 10.5 years. This paper summarizes the flight dynamics support for JWST, including the prelaunch nominal trajectory design, the launch window analysis, contingency planning for trajectory-related anomalies, mission operations support for the first 6 months, and a comparison of the planned and achieved actual JWST trajectory results. The orbit determination strategy, both planned and executed, will be summarized, and the method of addressing the anomalies as they occurred will be included.
This Air Sparge (AS) System Performance Monitoring Report (PMR) presents the findings, observations, and results for Year 3 of operation, maintenance, and monitoring activities for the AS Interim Measure (IM) at the Launch Complex 39A Operations Support Building Area (AOSB) at Kennedy Space Center (KSC), Florida. This report was presented as an Advance Data Package during the October 2024 KSC Remediation Team (KSCRT) meeting. The reporting period for activities covered under this PMR is from August 2023 through October 2024.
The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX
This paper presents first results of the project 'Technologien fuer die intelligente Kontrolle von Raumfahrzeugen' (TIKON). The TIKON objective was the demonstration of feasibility and profit of the application of artificial intelligence in the space business. For that purpose a prototype system has been developed and implemented for the operation support of the Roentgen Satellite (ROSAT), a scientific spacecraft designed to perform the first all-sky survey with a high-resolution X-ray telescope and to investigate the emission of specific celestial sources. The prototype integrates a scheduler and a diagnosis tool both based on artificial intelligence techniques. The user interface is menu driven and provides synoptic displays for the visualization of the system status. The prototype has been used and tested in parallel to an already existing operational system.
The International Space Station (ISS) design is a very large and complex orbiting structure with thousands of Extravehicular Activity (EVA) worksites. These worksites are used to assemble and maintain the ISS. The challenge facing EVA designers was how to design, verify, and operationally support such a large number of worksites within cost and schedule. This has been solved through the practical use of computer aided design (CAD) graphical techniques that have been developed and used with a high degree of success over the past decade. The EVA design process allows analysts to work concurrently with hardware designers so that EVA equipment can be incorporated and structures configured to allow for EVA access and manipulation. Compliance with EVA requirements is strictly enforced during the design process. These techniques and procedures, coupled with neutral buoyancy underwater testing, have proven most valuable in the development, verification, and on-orbit support of planned or contingency EVA worksites.
Versions of Scheduling and Planning Interface for Exploration (SPIFe) have supported a variety of mission operations across NASA. This software tool has evolved and matured over several years, assisting planners who develop intricate schedules. While initially conceived for surface Mars missions, SPIFe has been deployed in other domains, where people rather than robotic explorers, execute plans. As a result, a diverse set of end-users has compelled growth in a new direction: supporting real-time operations. This paper describes the new needs and challenges that accompany this development. Among the key features that have been built for SPIFe are current time indicators integrated into the interface and timeline, as well as other plan attributes that enable execution of scheduled activities. Field tests include mission support for the Lunar CRater Observation and Sensing Satellite (LCROSS), NASA Extreme Environment Mission Operations (NEEMO) and Desert Research and Technology Studies (DRATS) campaigns.
The Earth Observing System (EOS) is planned as a space-based measurement system, earth-science research program, and data and information system (EOSDIS). It will consist of several observatories with multiple earth sensing instruments to provide investigators with a thorough, long-term view of the earth's environment. Providing the data handling and flight operations support for EOS will be the EOSDIS Core System (ECS). The ECS will command and control the observatories consisting of core service platforms and science instruments, and it will transport, process, and store the EOS data, provide access to the data for years, and support researchers. EOS and EOSDIS are briefly described to provide a context for a description of the ECS.
Airway management techniques are necessary to establish and maintain a patent airway while treating a patient undergoing respiratory distress. There are situations where such settings are suboptimal, thus causing the caregiver to adapt to these suboptimal conditions. Such occurrences are no exception aboard the International Space Station (ISS). As a result, the NASA flight surgeon (FS) and NASA astronaut cohorts must be ready to adapt their optimal airway management techniques for suboptimal situations. Based on previous work conducted by the Medical Operation Support Team (MOST) and other investigators, the MOST had members of both the FS and astronaut cohorts evaluate two oral airway insertion techniques for the Intubating Laryngeal Mask Airway (ILMA) to determine whether either technique is sufficient to perform in suboptimal conditions within a microgravity environment. Methods All experiments were conducted in a simulated microgravity environment provided by parabolic flight aboard DC-9 aircraft. Each participant acted as a caregiver and was directed to attempt both suboptimal ILMA insertion techniques following a preflight instruction session on the day of the flight and a demonstration of the technique by an anesthesiologist physician in the simulated microgravity environment aboard the aircraft. Results Fourteen participants conducted 46 trials of the suboptimal ILMA insertion techniques. Overall, 43 of 46 trials (94%) conducted were properly performed based on criteria developed by the MOST and other investigators. Discussion The study demonstrated the use of airway management techniques in suboptimal conditions relating to space flight. Use of these techniques will provide a crew with options for using the ILMA to manage airway issues aboard the ISS. Although it is understood that the optimal method for patient care during space flight is to have both patient and caregiver restrained, these techniques provide a needed backup should conditions not present themselves in an ideal manner.
The conceptual design of a comprehensive support system for operators of complex systems is presented. Key functions within the support system architecture include information management, error monitoring, and adaptive aiding. One of the central knowledge bases underlying this functionality is an operator model that involves a 'matrix' of algorithmic and symbolic models for assessing and predicting an operator's activities, awareness resources, intentions, and performance. Functional block diagrams are presented for the overall architecture as well as the key elements within this architecture. A variety of difficult design issues are discussed and ongoing efforts aimed at resolving these issues are noted.
Kennedy Space Center (KSC) is developing knowledge-based systems to automate critical operations functions for the space shuttle fleet. Intelligent systems will monitor vehicle and ground support subsystems for anomalies, assist in isolating and managing faults, and plan and schedule shuttle operations activities. These applications are being developed independently of one another, using different representation schemes, reasoning and control models, and hardware platforms. KSC has recently initiated the EXODUS project to integrate these stand alone applications into a unified, coordinated intelligent operations support system. EXODUS will be constructed using SOCIAL, a tool for developing distributed intelligent systems. EXODUS, SOCIAL, and initial prototyping efforts using SOCIAL to integrate and coordinate selected EXODUS applications are described.