SEARCH · Engineering Papers
Results for “Ground Support System”
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.
Space programs summary no. 37-44, volume III FOR the period January 1, 1967 to February 28, 1967. The deep space network
Tracking and navigation, communications R&D, ground support equipment, and computer programming for deep space network
Evaluation of a ground based manned demonstration as a milestone in CELSS development
The requirements for a ground based manned controlled ecological life support system demonstration are summarized for the following: nutrition and food processing, food production, waste processing, systems engineering and modeling, and ecology-systems safety.
Rolling Beam Umbilical System
The decision to make the Centaur Vehicle a Space Transportation System (STS) payload meant that new ground support equipment provisions at Launch Pads Pads 39A and 39B were required. These new equipment provisions were needed to service the Centaur vehicle while it was installed in the Orbiter's payload bay prior to launch. This paper describes the design of a new rolling beam umbilical syste (RBUS) being added to the pad fixed service structure (FSS) in order to provide the primary functions of liquid hydrogen (LH2) fill, drain, and vent. The carrier plate itself is a Government-furnished equipment item and of necessity became a T-O disconnect. This permits quick offloading in the event of an abort prior to lift-off. In addition to the rolling beam structure, mechanisms, and fluid lines, it was necessary to design and build a carrier plate simulator to support early development testing of the mast at the Launch Equipment Test Facility at Kennedy Space Center. The RBUS is designed to be compatible with the rotating service structure (RSS) to the extent that the umbilical may be deployed with the RSS mated with the vehicle. It is also designed to clear the RSS as the RSS rotates back out of the way. Accessibility to the Orbiter aft compartment via the 50-1 door had to be maintained.
Identifying atmospheric monitoring needs for Space Station Freedom
The atmospheric monitoring needs for Space Station Freedom were identified by examining the following from an industrial hygiene perspective: the experiences of past missions; ground based tests of proposed life support systems; the unique experimental and manufacturing facilities; the contaminant load model; metabolic production; and a fire. A target list of compounds to be monitored is presented and information is provided relative to the frequency of analysis, concentration ranges, and locations for monitoring probes.
Identifying atmospheric monitoring needs for Space Station Freedom
The monitoring needs for Space Station Freedom were identified by examining: the experiences of past missions; ground based tests of proposed life support systems; a contaminant load model; metabolic production from an 8-person crew; and a fire scenario. Continuous monitoring is recommended for components critical for life support, and that intermittent analysis be provided for all agents that may exceed one-half the spacecraft maximum allowable concentration. The minimum monitoring effort recommended includes continuous monitoring for: N2, O2, CO2, CO, H2O, H2, CH4, nonmethane hydrocarbons, aromatic hydrocarbons, refrigerants, and halons. Information on over 70 compounds is presented on the rationale for monitoring the frequency of analysis, and concentration ranges.
Renaissance architecture for Ground Data Systems
The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.
Goddard's New Approach to Information Technology: The Information Systems Center an Overview
The Information Center (ISC) at Goddard was created as part of the Goddard reorganization and was located within the Applied Engineering and Technology (AET) Directorate. The creation of ISC was to: (1) focus expertise and leadership in information system development; (2) Promote organizational collaboration, partnerships, and resource sharing; (3) Stimulate design/development of seamless end-to-end flight and ground systems; (4) Enable flexibility to effectively support many simultaneous projects by improved access to critical mass of discipline expertise; (5) Enhance career growth and opportunities including multi-disciplinary opportunities; and (6) to improve communications among information system professionals. This paper presents a general overview of the Information Systems Center as well as the role of the Software Engineering Laboratory within the center.
The Search for Nonflammable Solvent Alternatives for Cleaning Aerospace Oxygen Systems
Oxygen systems are susceptible to fires caused by particle and nonvolatile residue (NVR) contaminants, therefore cleaning and verification is essential for system safety. . Cleaning solvents used on oxygen system components must be either nonflammable in pure oxygen or complete removal must be assured for system safety. . CFC -113 was the solvent of choice before 1996 because it was effective, least toxic, compatible with most materials of construction, and non ]reactive with oxygen. When CFC -113 was phased out in 1996, HCFC -225 was selected as an interim replacement for cleaning propulsion oxygen systems at NASA. HCFC-225 production phase-out date is 01/01/2015. HCFC ]225 (AK ]225G) is used extensively at Marshall Space Flight Center and Stennis Space Center for cleaning and NVR verification on large propulsion oxygen systems, and propulsion test stands and ground support equipment. . Many components are too large for ultrasonic agitation - necessary for effective aqueous cleaning and NVR sampling. . Test stand equipment must be cleaned prior to installation of test hardware. Many items must be cleaned by wipe or flush in situ where complete removal of a flammable solvent cannot be assured. The search for a replacement solvent for these applications is ongoing.
Maintenance Modernization in the Era of Artemis An RCM Journey
The NASA Artemis Program mission to return humans to the moon requires it ground test facilities to meet today’s performance and throughput demands. The NASA Ames Arc Jet Complex (AJC) at Ames Research Center is the Agency’s sole ground test facility supporting reentry thermal protection system testing and was developed to support Apollo era spacecraft. The research and development required to meet current and future mission demands continually grows, but the maintenance upkeep to ensure safe and reliable operations holds stagnant. This paper presents the journey and subsequent industry relatable story that includes the challenges, lessons learned, and testimonials to the AJC’s approach to the modernization of maintenance using RCM at NASA.
Expert system decision support for low-cost launch vehicle operations
Progress in assessing the feasibility, benefits, and risks associated with AI expert systems applied to low cost expendable launch vehicle systems is described. Part one identified potential application areas in vehicle operations and on-board functions, assessed measures of cost benefit, and identified key technologies to aid in the implementation of decision support systems in this environment. Part two of the program began the development of prototypes to demonstrate real-time vehicle checkout with controller and diagnostic/analysis intelligent systems and to gather true measures of cost savings vs. conventional software, verification and validation requirements, and maintainability improvement. The main objective of the expert advanced development projects was to provide a robust intelligent system for control/analysis that must be performed within a specified real-time window in order to meet the demands of the given application. The efforts to develop the two prototypes are described. Prime emphasis was on a controller expert system to show real-time performance in a cryogenic propellant loading application and safety validation implementation of this system experimentally, using commercial-off-the-shelf software tools and object oriented programming techniques. This smart ground support equipment prototype is based in C with imbedded expert system rules written in the CLIPS protocol. The relational database, ORACLE, provides non-real-time data support. The second demonstration develops the vehicle/ground intelligent automation concept, from phase one, to show cooperation between multiple expert systems. This automated test conductor (ATC) prototype utilizes a knowledge-bus approach for intelligent information processing by use of virtual sensors and blackboards to solve complex problems. It incorporates distributed processing of real-time data and object-oriented techniques for command, configuration control, and auto-code generation.
Linear Covariance Techniques to Analyze a Multi-Vehicle, Multi-GN&C System with Applications to Rendezvous in a Near Rectilinear Halo Orbit
Typically for a rendezvous and docking scenario, only a single vehicle is considered the active vehicle. As a result, the target vehicle’s GN&C system is typically not a factor in the integrated performance analysis as it assumes a passive role. However, for upcoming NASA Artemis missions the active vehicle is both the chaser and target spacecraft. In addition, both vehicles are cooperating with one another, sharing telemetry data, and relying on data extracted from the GN&C system of the other. The process also includes a team of ground support personnel in mission control are tracking and monitoring each spacecraft uplinking state estimates and targeting solutions to support mission operations and enhance the onboard flight system performance. Being able to quickly analyze the impact of both vehicles with two different GN&C systems that also interact with the ground that does its own navigation and targeting uploads is critical. This paper outlines how to perform this rapid analysis using linear covariance techniques and applies them to a rendezvous scenario initiated in low lunar orbit and completed in a Near Rectilinear Halo Orbit (NRHO) representative of the NASA Artemis III mission.
NASA's Low-Cost Optical Terminal (LCOT) Free-Space Optical Subsystem (FSOS): Concept, Design, Build, & Test
We present the status of ongoing work at NASA’s Goddard Space Flight Center (GSFC) to build a prototype, low-cost-of-production, flexibly-configured ground terminal for space optical communication. For laser telecommunication to be cost effective for future missions, a wide-spread global network of operationally responsive optical terminals should be established. There has been a decades-old need for a single modular open systems approach (MOSA) ground terminal architecture capable of supporting multiple space missions ranging from LEO to Lunar distances with 2-way laser communications. At the heart of LCOT’s design concept is the Free-Space Optical Subsystem (FSOS). The major subassemblies of LCOT/FSOS that address most optical common configurations are : (1) Single 700mm F/12 Nasmyth folded Rx R-C Telescope, (2) Four independent 150mm diameter high-power all-reflective Tx beam directors (XOA), (3) Non-coherent direct detection Rx bench on starboard side of telescope (SOB), and (4) Coherent (possibly Quantum) optical communications bench on port side (POB). The Low-Cost Optical Terminal (LCOT) research and development (R&D) prototype is designed to be a generalized system that can be quickly field-reconfigured to support a wide variety of laser communications missions past, present, & future.
Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center
Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.
A Preliminary Assessment of Phase Separator Ground-Based and Reduced-Gravity Testing for ALS Systems
A viewgraph presentation of phase separator ground-based and reduced-gravity testing for Advanced Life Support (ALS) systems is shown. The topics include: 1) Multiphase Flow Technology Program; 2) Types of Separators; 3) MOBI Phase Separators; 4) Experiment set-up; and 5) Preliminary comparison/results.
NASA's LCOT (Low-Cost Optical Terminal) FSOS (Free-Space Optical Subsystem): Concept, Design, Build, & Test
We present the status of ongoing work at NASA’s Goddard Space Flight Center (GSFC) to build a prototype, low-cost-of-production, flexibly-configured ground terminal for space optical communication. For laser telecommunication to be cost effective for future missions, a wide-spread global network of operationally responsive optical terminals should be established. There has been a decades-old need for a single modular open systems approach (MOSA) ground terminal architecture capable of supporting multiple space missions ranging from LEO to Lunar distances with 2-way laser communications. At the heart of LCOT’s design concept is the Free-Space Optical Subsytem (FSOS). The major subassemblies of LCOT/FSOS that address most optical comms configurations are : (1) Single 700mm F/12 Nasmyth folded Rx R-C Telescope, (2) Four independent 150mm diameter high-power all-reflective Tx beam directors (XOA), (3) Non-coherent direct detection Rx bench on starboard side of telescope (SOB), and (4) Coherent (possibly Quantum) optical communications bench on port side (POB). The Low-Cost Optical Terminal (LCOT) research and development (R&D) prototype is designed to be a generalized system that can be quickly field-reconfigured to support a wide variety of laser communications missions past, present, & future.
System security in the space flight operations center
The Space Flight Operations Center is a networked system of workstation-class computers that will provide ground support for NASA's next generation of deep-space missions. The author recounts the development of the SFOC system security policy and discusses the various management and technology issues involved. Particular attention is given to risk assessment, security plan development, security implications of design requirements, automatic safeguards, and procedural safeguards.
Operational Assessment of Apollo Lunar Surface Extravehicular Activity
Quantifying the operational variability of extravehicular activity (EVA) execution is critical to help design and build future support systems to enable astronauts to monitor and manage operations in deep-space, where ground support operators will no longer be able to react instantly and manage execution deviations due to the significant communication latency. This study quantifies the operational variability exhibited during Apollo 14-17 lunar surface EVA operations to better understand the challenges and natural tendencies of timeline execution and life support system performance involved in surface operations. Each EVA (11 in total) is individually summarized as well as aggregated to provide descriptive trends exhibited throughout the Apollo missions. This work extends previous EVA task analyses by calculating deviations between planned and as-performed timelines as well as examining metabolic rate and consumables usage throughout the execution of each EVA. The intent of this work is to convey the natural variability of EVA operations and to provide operational context for coping with the variability inherent to EVA execution as a means to support future concepts of operations.