Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “launch services”

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 631 records · Page 35

STS-114: Discovery L-1 Countdown Status Briefing STS-114/Discovery L-2 Countdown Status Briefing

Bruce Buckingham from NASA Public Affairs introduces Jeff Spaulding, NASA Test Director and Kathy Winters, Shuttle Weather Officer in this L-2 countdown status briefing. Spaulding gives the Space Shuttle launch countdown status before lift-off on July 26th. He expresses that vehicle launch and ground systems are performing well and that there are no significant issues in preparation for the launch. The crew arrival time to the launching pad and the launch window for Discovery is also discussed. He ends his countdown status by expressing that the Discovery Orbiter is the safest Shuttle to date. Kathy Winters gives her weather forecast for the launch day. She presents a satellite picture of tropical storm Franklin and charts showing the STS-114 Tanking Forecast, Launch Forecast, Solid Rocket Booster (SRB) recovery, Continental United States (CONUS) launch, Transoceanic Abort Landing (TAL) launch, 24 and 48 Hour Delay, CONUS 24 and 48 hour delay, and TAL 24 and 48 hr delay. Questions from the news media about the mood of the test engineers as launch day is approached are answered. Jessica Rye from NASA Public Affairs introduces Pete Nikolento, NASA Test Director; Scott Higgenbotham, STS-114 Payload Mission Manager; and Kathy Winters, Space Shuttle Weather Officer in this L-1 Countdown Status Briefing. Nikolento expresses that the completion of the main engine system check-outs and servicing of on-board fuel-cell reactants have been completed. He also talks about pad closeouts and external cryogenic loads prior to launch. Scott Higgenbotham gives the payload status and Kathy Winters talks about her weather forecast for launch. Questions about the ecosensors, TAL sites, weather forecast and thoughts about return to flight are addressed.

Source record↗

Communication satellite services for special purpose users

The present study identifies potential satellite services, examines the technology necessary for efficient implementation of these services, and determines minimum service cost versus user network size. The generic satellite services evaluated comprise TV and radio distribution (for retransmission), video teleconferencing (interactive), audio/facsimile teleconferencing (interactive), multiplexed data/voice (point-to-point), and satellite-supported land mobile. Satellite costs are based on extrapolations from ongoing commercial satellite programs. Production methods, new technology, and effect of production quantities on present and future production costs are examined to provide information on earth station equipment cost versus the variable 'buy'. Six different launch vehicles from a Delta 2914 to a dedicated Shuttle and three frequency bands and both broadcast (no eclipse capability) and fixed service satellites are considered to assess the effect of satellite size on cost and performance. It is assumed that the user pays only for his prorata share of the space segment costs.

Wright, D. L.↗

NASA's Astronant Family Support Office

During the NASA‐Mir program of the 1990s and due to the challenges inherent in the International Space Station training schedule and operations tempo, it was clear that a special focus on supporting families was a key to overall mission success for the ISS crewmembers pre‐, in‐ and post‐flight. To that end, in January 2001 the first Family Services Coordinator was hired by the Behavioral Health and Performance group at NASA JSC and matrixed from Medical Operations into the Astronaut Office's organization. The initial roles and responsibilities were driven by critical needs, including facilitating family communication during training deployments, providing mission‐specific and other relevant trainings for spouses, serving as liaison for families with NASA organizations such as Medical Operations, NASA management and the Astronaut Office, and providing assistance to ensure success of an Astronaut Spouses Group. The role of the Family Support Office (FSO) has modified as the ISS Program matured and the needs of families changed. The FSO is currently an integral part of the Astronaut Office's ISS Operations Branch. It still serves the critical function of providing information to families, as well as being the primary contact for US and international partner families with resources at JSC. Since crews launch and return on Russian vehicles, the FSO has the added responsibility for coordinating with Flight Crew Operations, the families, and their guests for Soyuz launches, landings, and Direct Return to Houston post‐flight. This presentation will provide a summary of the family support services provided for astronauts, and how they have changed with the Program and families the FSO serves. Considerations for future FSO services will be discussed briefly as NASA proposes one year missions and beyond ISS missions. Learning Objective: 1) Obtain an understanding of the reasons a Family Support Office was important for NASA. 2) Become familiar with the services provided for astronauts and their families and how they changed with the Program and family needs.

Beven, Gary↗

Apollo 6, Anomaly Report No. 6: Abnormal Structural Performance During Launch Phase

Approximately 2 minutes 13 seconds after lift-off of the Apollo 6 mission, abrupt changes of strain, vibration, and acceleration measurements were indicated in the S-IVB, instrument unit, adapter, lunar module, and command and service modules; photographs showed objects coming from the area of the adapter. The adapter, however, continued to sustain the required loads with no impairment of the mission. The investigation was first focused upon the understanding of the coupled vibration modes and characteristics of the launch vehicle and spacecraft.' Extensive test programs were conducted. It was eventually concluded that the adapter failure was not caused by vibration. Extensive study of the airborne photography and other evidence indicated that a large area of the adapter had lost inner facesheet from the honeycomb sandwich panels. Loads and stresses resulting from vibration were determined to be insufficient to initiate such a failure. The investigation was then directed toward determining the range of pressures that could have been trapped in the Apollo 6 adapter sandwich panels, and toward determining the tolerance of the panels to withstand pressure with various degrees of flaws such as adhesive voids and facesheet dents. The degradation effects of moisture and heat exposure on the adhesive strength were also studied and tested. These tests and analyses led to the conclusion that pressure internal to the sandwich panels could have caused the failure, if a large flaw existed. The pressure buildup would have been caused by aerodynamic heating effects on air and moisture trapped in the panel. The probable cause of the failure was found in the original ultrasonic inspection scan record of the affected adapter panel. In the center of the region where the adapter failed, horizontally along the station 709 panel splice, the record contained two thick anomalous lines extending several feet. Without an X-ray record of this region, the significance of this particular scan record cannot be fully understood. However, since all other evidence had indicated that the adhesive had to be weakened in a rather large area to initiate the failure, the investigation was focused intently upon the station 709 splices of other adapters. Sufficient information was developed to verify that deficient assembly techniques have consistently resulted in abnormalities in the structure at this station. These abnormalities were identified in adapters 12, 13, 14, 15, and 16. Before the splice abnormalities were pinpointed, corrective action was taken to reduce pressure "buildup in the honeycomb panels and to reduce heat degrading effects on the adhesive. This was done by drilling vent holes in the inner facesheet and covering the outer facesheet with cork. The adapters having identified abnormalities in the station 709 splice are being repaired, and the contractor is investigating ways of avoiding these -abnormalities in panels yet to be bonded.

Source record↗

Volt-VAR Optimization on American Electric Power Feeders in Northeast Columbus

In 2007 American Electric Power launched the gridSMART® initiative with the goals of increasing efficiency of the electricity delivery system and improving service to the end-use customers. As part of the initiative, a coordinated Volt-VAR system was deployed on eleven distribution feeders at five substations in the Northeast Columbus Ohio Area. The goal of the coordinated Volt-VAR system was to decrease the amount of energy necessary to provide end-use customers with the same quality of service. The evaluation of the Volt-VAR system performance was conducted in two stages. The first stage was composed of simulation, analysis, and estimation, while the second stage was composed of analyzing collected field data. This panel paper will examine the analysis conducted in both stages and present the estimated improvements in system efficiency.

Schneider, Kevin P.↗

Build and Execute Environment

At exascale, the challenge becomes to develop applications that run at scale and use exascale platforms reliably, efficiently, and flexibly. Workflows become much more complex because they must seamlessly integrate simulation and data analytics. They must include down-sampling, post-processing, feature extraction, and visualization. Power and data transfer limitations require these analysis tasks to be run in-situ or in-transit. We expect successful workflows will comprise multiple linked simulations along with tens of analysis routines. Users will have limited development time at scale and, therefore, must have rich tools to develop, debug, test, and deploy applications. At this scale, successful workflows will compose linked computations from an assortment of reliable, well-defined computation elements, ones that can come and go as required, based on the needs of the workflow over time. We propose a novel framework that utilizes both virtual machines (VMs) and software containers to create a workflow system that establishes a uniform build and execution environment (BEE) beyond the capabilities of current systems. In this environment, applications will run reliably and repeatably across heterogeneous hardware and software. Containers, both commercial (Docker and Rocket) and open-source (LXC and LXD), define a runtime that isolates all software dependencies from the machine operating system. Workflows may contain multiple containers that run different operating systems, different software, and even different versions of the same software. We will run containers in open-source virtual machines (KVM) and emulators (QEMU) so that workflows run on any machine entirely in user-space. On this platform of containers and virtual machines, we will deliver workflow software that provides services, including repeatable execution, provenance, checkpointing, and future proofing. We will capture provenance about how containers were launched and how they interact to annotate workflows for repeatable and partial re-execution. We will coordinate the physical snapshots of virtual machines with parallel programming constructs, such as barriers, to automate checkpoint and restart. We will also integrate with HPC-specific container runtimes to gain access to accelerators and other specialized hardware to preserve native performance. Containers will link development to continuous integration. When application developers check code in, it will automatically be tested on a suite of different software and hardware architectures.

Guan, Qiang↗

Bringing Low- and Moderate-Income Solar Financing Models to Scale (Final Technical Report (FTR))

In this final report, the Clean Energy States Alliance(CESA) and its project partners describe their work to accelerate the development of solar projects for three distinct subsets of the low- to moderate-income(LMI) solar market: single-family homes, manufactured homes, and community institutions, including multifamily affordable housing. For each market sector, the project team undertook research, outreach, and market-building activities. By advancing promising LMI solar financing innovations for different housing types and spreading them to new locations, the Scaling Up Solar for Under-Resourced Communities project has built momentum to scale up LMI solar. Although the report describes some research pertaining to solar adoption in LMI communities, this project was original in that it focused on two specific models to tackle single-family homes and community institutions. Until this project, very little research dedicated to solar for manufactured homes existed. For each market sector, the project team undertook research, outreach, and market-building activities. For the single-family homes sector, the project encouraged states to adapt a program model based on a successful Connecticut initiative that has brought solar to thousands of LMI homeowners. For manufactured homes, the project analyzed the potential for using solar for that housing sector and worked with states, utilities, and other stakeholders to launch pilot projects or programs. For community institutions, the project team worked with foundations, lenders, and community service organizations to inventory, analyze, and communicate models for philanthropic investment that accelerate the deployment of solar and solar+storage in multifamily affordable housing, health centers, and other LMI-serving community institutions.

14 SOLAR ENERGY↗

MSFC Three Point Docking Mechanism design review

In the next few decades, we will be launching expensive satellites and space platforms that will require recovery for economic reasons, because of initial malfunction, servicing, repairs, or out of a concern for post lifetime debris removal. The planned availability of a Three Point Docking Mechanism (TPDM) is a positive step towards an operational satellite retrieval infrastructure. This study effort supports NASA/MSFC engineering work in developing an automated docking capability. The work was performed by the Grumman Space & Electronics Group as a concept evaluation/test for the Tumbling Satellite Retrieval Kit. Simulation of a TPDM capture was performed in Grumman's Large Amplitude Space Simulator (LASS) using mockups of both parts (the mechanism and payload). Similar TPDM simulation activities and more extensive hardware testing was performed at NASA/MSFC in the Flight Robotics Laboratory and Space Station/Space Operations Mechanism Test Bed (6-DOF Facility).

Schaefer, Otto↗

Basic space payload fastener

A new basic space fastener has been developed and tested by the GSFC. The purposes of this fastener are to permit assembly and servicing in space by astronauts and/or robots and to facilitate qualification of payloads on Earth prior to launch by saving time and money during the systems integration and component testing and qualification processes. The space fastener is a rework of the basic machine screw such that crossthreading is impossible; it is self-locking and will not work its way out during launch (vibration proof); it will not wear out despite repeated use; it occupies a small foot print which is comparable to its machine screw equivalent, and it provides force and exhibits strength comparable to its machine screw equivalent. Construction is ultra-simple and cost effective and the principle is applicable across the full range of screw sizes ranging from a #10 screw to 2.5 cm (1 in) or more. In this paper, the fastener principles of operation will be discussed along with test results and construction details. The new fastener also has considerable potential in the commercial sector. A few promising applications will be presented.

Vranish, J. M.↗

Performance assessment of the TDRSS Onboard Navigation System (TONS) experiment on EP/EUVE

The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) is currently developing an operational Tracking and Data Relay Satellite (TDRS) System (TDRSS) Onboard Navigation System (TONS) to provide onboard knowledge of high-accuracy navigation products autonomously to users of TDRSS and its successor, TDRS-2. A TONS experiment has been implemented on the Explorer Platform/Extreme Ultraviolet Explorer (EP/EUVE) spacecraft, launched June 7, 1992, to flight qualify the TONS operational system using TDRSS forward-link communications services. This paper assesses the performance of the TONS flight hardware, an ultrastable oscillator (USO) and Doppler extractor (DE) card in one of the TDRSS user transponders, and the protoype flight software, based on the TONS experiment results. An overview of onboard navigation via TDRSS is also presented for both the EP/EUVE experiment and for future users of TONS. USO and DE short-term and long-term stability performance has been excellent. TONS Flight Software analysis indicates that position accuracies of better than 25 meters root-mean-square are achievable with tracking every one to two orbits, for the EP/EUVE 525-kilometer altitudes, 28.5-degree inclination orbit. The success of the TONS experiment demonstrates the flight readiness of TONS, which is scheduled to provide autonomous navigation for the Earth Observing System (EOS)-AM mission.

Gramling, C. J.↗

STS-93: Columbia Flight Crew Arrival on FSS 195' Level, Walk Across OAA and Ingress into White Room

The primary objective of the STS-93 mission was to deploy the Advanced X-ray Astrophysical Facility, which had been renamed the Chandra X-ray Observatory in honor of the late Indian-American Nobel Laureate Subrahmanyan Chandrasekhar. The mission was launched at 12:31 on July 23, 1999 onboard the space shuttle Columbia. The mission was led by Commander Eileen Collins. The crew was Pilot Jeff Ashby and Mission Specialists Cady Coleman, Steve Hawley and Michel Tognini from the Centre National d'Etudes Spatiales (CNES). This videotape opens with a view of the shuttle on the launch pad. It then shows the flight crew arrival on the 195 foot level of the fixed service structure (FSS), walks across the orbiter access arm (OAA) into the white room, where the crew is assisted in putting on the final stages of their spacesuits, and then their crawl into the orbiter.

Source record↗

Distributed operations as applied in a large multi-instrument space mission: lessons learned from the Cassini-Huygens Program

Launched in 1997, the Cassini-Huygens Mission sent the largest interplanetary spacecraft ever built in the service of science. Carrying a suite of 12 scientific instruments and an atmospheric entry probe, this complex spacecraft to explore the Saturn system may not have gotten off the ground without undergoing significant design changes and cost reductions.

distributed↗

OSAM-2: Plans and Progress for the First Demonstration of Structural Manufacturing in Space

OSAM-2 began as a NASA Space Technology Mission Directorate Tipping Point project in 2016 in which an investment made in ground development and demonstration and/or flight demonstration will result in: Significant advancement of technology’s maturation High likelihood for utilization of technology in commercially fielded space application Significant improvement in ability to successfully bring space technology to market Topic area was “Robotic In-Space Manufacturing and Assembly of Spacecraft and Space Structures” Made In Space, Inc. (now Redwire) proposed Archinaut One, an in-space robotic precision manufacturing and assembly system for larger-than-deployable structures Manufacturing / assembly in the operational environment allows manufactured parts to be designed for that environment (and not for launch loads and need to deploy) In 2020 NASA budget language, NASA began using On-orbit Servicing, Assembly, and Manufacturing Mission 2 (OSAM-2) for Archinaut One Restore-L + SPIDER (SPace Infrastructure DExterous Robot) became OSAM-1 Note: Slide 7 contains video animation, best viewed in presentation mode, run time 2 mins 25 secs.

In-Space Manufacturing↗

Build and Execute Environment

At exascale, the challenge becomes to develop applications that run at scale and use exascale platforms reliably, efficiently, and flexibly. Workflows become much more complex because they must seamlessly integrate simulation and data analytics. They must include down-sampling, post-processing, feature extraction, and visualization. Power and data transfer limitations require these analysis tasks to be run in-situ or in-transit. We expect successful workflows will comprise multiple linked simulations along with tens of analysis routines. Users will have limited development time at scale and, therefore, must have rich tools to develop, debug, test, and deploy applications. At this scale, successful workflows will compose linked computations from an assortment of reliable, well-defined computation elements, ones that can come and go as required, based on the needs of the workflow over time. We propose a novel framework that utilizes both virtual machines (VMs) and software containers to create a workflow system that establishes a uniform build and execution environment (BEE) beyond the capabilities of current systems. In this environment, applications will run reliably and repeatably across heterogeneous hardware and software. Containers, both commercial (Docker and Rocket) and open-source (LXC and LXD), define a runtime that isolates all software dependencies from the machine operating system. Workflows may contain multiple containers that run different operating systems, different software, and even different versions of the same software. We will run containers in open-source virtual machines (KVM) and emulators (QEMU) so that workflows run on any machine entirely in user-space. On this platform of containers and virtual machines, we will deliver workflow software that provides services, including repeatable execution, provenance, checkpointing, and future proofing. We will capture provenance about how containers were launched and how they interact to annotate workflows for repeatable and partial re-execution. We will coordinate the physical snapshots of virtual machines with parallel programming constructs, such as barriers, to automate checkpoint and restart. We will also integrate with HPC-specific container runtimes to gain access to accelerators and other specialized hardware to preserve native performance. Containers will link development to continuous integration. When application developers check code in, it will automatically be tested on a suite of different software and hardware architectures.

Guan, Qiang↗

COMPASS Final Report: 2008 International Lunar Network (ILN)

The Compass team developed three designs for a soft lander for the International Lunar Network (ILN) using different power systems. These systems included solar arrays and batteries and two radioisotope power system (RPS) options scaled down from previous designs. These are a half Stirling radioisotope generator and a one-eighth Radioisotope Thermoelectric Generator (RTG). The COMPASS design consists of a soft-lander capable of network science (seismic, magnetospheric, laser reflector, and thermal transfer) that can land anywhere on the near side of the Moon and operate for at least six years. The baseline version, using only batteries and solar arrays, requires a very large battery (~80 kg) for the roughly 20 W night-time power requirements. The lander launch mass (with solid rocket breaking motor) is almost 900 kg. With such a large battery, the lander will require a launcher larger than the desired Minotaur V; a Taurus II (being developed for NASA Commercial Orbital Transportation Services (COTS)) or larger (Delta II or Atlas V) would be needed. The two RPS cases, half an Advanced Stirling Radioisotope Generators (ASRG) and one-eighth RTG have much smaller launch masses of 500 and 600 kg respectively. (The one-eighth RTG case lacks the power for the full science package, so a solar array battery is still needed.) Unfortunately, the Minotaur V’s launch capability is still not large enough (~430 kg to trans-lunar injection (TLI)) for the RPS systems. Consequently, a fourth case was developed to fly a limited science floor suite of instruments (seismometer only) which reduced the RPS Lander launch mass to fit on a Minotaur V.

Radioisotope Power Systems↗

Modeling and Evaluation of Cyber-Attacks on Grid-Interactive Efficient Buildings

Grid-interactive efficient buildings (GEBs) are not only exposed to passive threats (e.g., physical faults) but also active threats such as cyber-attacks launched on the network-based control systems. The impact of cyber-attacks on GEB operation are not yet fully understood, especially as regards the performance of grid services. To quantify the consequences of cyber-attacks on GEBs, this paper proposes a modeling and simulation framework that includes different cyber-attack models and key performance indexes to quantify the performance of GEB operation under cyber-attacks. The framework is numerically demonstrated to model and evaluate cyber-attacks such as data intrusion attacks and Denial-of-Service attacks on a typical medium-sized office building that uses the BACnet/IP protocol for communication networks. Simulation results show that, while different types of attacks could compromise the building systems to different extents, attacks via the remote control of a chiller yield the most significant consequences on a building system’s operation, including both the building service and the grid service. It is also noted that a cyber-attack impacts the building systems during the attack period as well as the post-attack period, which suggests that both periods should be considered to fully evaluate the consequences of a cyber-attack.

Fu, Yanyang↗

Evolution of NASA's Near-Earth Tracking and Data Relay Satellite System (TDRSS)

NASA's Tracking and Data Relay Satellite System (TDRSS) is now in its 23rd year of operations and its spacecraft fleet includes three second-generation spacecraft launched since the year 2000; a figure illustrates the first generation TDRSS spacecraft. During this time frame the TDRSS has provided communications relay support to a broad range of missions, with emphasis on low-earth-orbiting (LEO) spacecraft that include unmanned science spacecraft (e.g., Hubble Space Telescope), and human spaceflight (Space Shuttle and Space Station). Furthermore, the TDRSS has consistently demonstrated its uniqueness and adaptability in several ways. First, its S- and K-band services, combined with its multi-band/steerable single-access (SA) antennas and ground-based configuration flexibility, have permitted the mission set to expand to unique users such as scientific balloons and launch vehicles. Second, the bent-pipe nature of the system has enabled the introduction of new/improved services via technology insertion and upgrades at each of the ground terminals; a specific example here is the Demand Access Service (DAS), which, for example, is currently providing science-alert support to NASA science missions Third, the bent-pipe nature of the system, combined with the flexible ground-terminal signal processing architecture has permitted the demonstration/vaIidation of new techniques/services/technologies via a real satellite channel; over the past 10+ years these have, for example, included demonstrations/evaluations of emerging modulation/coding techniques. Given NASA's emerging Exploration plans, with missions beginning later this decade and expanding for decades to come, NASA is currently planning the development of a seamless, NASA-wide architecture that must accommodate missions from near-earth to deep space. Near-earth elements include Ground-Network (GN) and Near-Earth Relay (NER) components and both must efficiently and seamlessly support missions that encompass: earth orbit, including dedicated science missions and lunar support/cargo vehicles; earth/moon transit; lunar in-situ operations; and other missions within approximately 2 million km of earth (e.g., at the sun/earth libration points). Given that the NER is an evolution of TDRSS, one element of this NASA-wide architecture development activity is a trade study of future NER architecture candidates. The present paper focuses on trade study aspects associated with the NER, highlights study elements, and provides representative interim results.

Flaherty, Roger↗

The US re-usable launch system - The Space Shuttle

The NASA Space Shuttle furnishes a range of readily available, and either already planned or yet-to-be-defined services, which already encompass satellite on-orbit servicing, refueling and repair, and satellite retrieval services. A gradual expansion will be made of services that capitalize on the presence of a large crew during commercial and scientific operations, while pursuing the development of automated, standardized procedures for the handling of experiments in order to reduce research costs.

Lee, C. M.↗