Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Processing”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

NASA Manned Launch Vehicle Lightning Protection Development

Historically, the National Aeronautics and Space Administration (NASA) relied heavily on lightning avoidance to protect launch vehicles and crew from lightning effects. As NASA transitions from the Space Shuttle to the new Constellation family of launch vehicles and spacecraft, NASA engineers are imposing design and construction standards on the spacecraft and launch vehicles to withstand both the direct and indirect effects of lightning. A review of current Space Shuttle lightning constraints and protection methodology will be presented, as well as a historical review of Space Shuttle lightning requirements and design. The Space Shuttle lightning requirements document, NSTS 07636, Lightning Protection, Test and Analysis Requirements, (originally published as document number JSC 07636, Lightning Protection Criteria Document) was developed in response to the Apollo 12 lightning event and other experiences with NASA and the Department of Defense launch vehicles. This document defined the lightning environment, vehicle protection requirements, and design guidelines for meeting the requirements. The criteria developed in JSC 07636 were a precursor to the Society of Automotive Engineers (SAE) lightning standards. These SAE standards, along with Radio Technical Commission for Aeronautics (RTCA) DO-160, Environmental Conditions and Test Procedures for Airborne Equipment, are the basis for the current Constellation lightning design requirements. The development and derivation of these requirements will be presented. As budget and schedule constraints hampered lightning protection design and verification efforts, the Space Shuttle elements waived the design requirements and relied on lightning avoidance in the form of launch commit criteria (LCC) constraints and a catenary wire system for lightning protection at the launch pads. A better understanding of the lightning environment has highlighted the vulnerability of the protection schemes and associated risk to the vehicle, which has resulted in lost launch opportunities and increased expenditures in manpower to assess Space Shuttle vehicle health and safety after lightning events at the launch pad. Because of high-percentage launch availability and long-term on-pad requirements, LCC constraints are no longer considered feasible. The Constellation vehicles must be designed to withstand direct and indirect effects of lightning. A review of the vehicle design and potential concerns will be presented as well as the new catenary lightning protection system for the launch pad. This system is required to protect the Constellation vehicles during launch processing when vehicle lightning effects protection might be compromised by such items as umbilical connections and open access hatches.

McCollum, Matthew B.↗
NASA NTRS2010

Constellation Program Electrical Ground Support Equipment Research and Development

At the Kennedy Space Center, I engaged in the research and development of electrical ground support equipment for NASA's Constellation Program. Timing characteristics playa crucial role in ground support communications. Latency and jitter are two problems that must be understood so that communications are timely and consistent within the Kennedy Ground Control System (KGCS). I conducted latency and jitter tests using Alien-Bradley programmable logic controllers (PLCs) so that these two intrinsic network properties can be reduced. Time stamping and clock synchronization also play significant roles in launch processing and operations. Using RSLogix 5000 project files and Wireshark network protocol analyzing software, I verified master/slave PLC Ethernet module clock synchronization, master/slave IEEE 1588 communications, and time stamping capabilities. All of the timing and synchronization test results are useful in assessing the current KGCS operational level and determining improvements for the future.

McCoy, Keegan S.↗
NASA NTRS2013

Determining Component Probability using Problem Report Data for Ground Systems used in Manned Space Flight

During the shuttle era NASA utilized a failure reporting system called the Problem Reporting and Corrective Action (PRACA) it purpose was to identify and track system non-conformance. The PRACA system over the years evolved from a relatively nominal way to identify system problems to a very complex tracking and report generating data base. The PRACA system became the primary method to categorize any and all anomalies from corrosion to catastrophic failure. The systems documented in the PRACA system range from flight hardware to ground or facility support equipment. While the PRACA system is complex, it does possess all the failure modes, times of occurrence, length of system delay, parts repaired or replaced, and corrective action performed. The difficulty is mining the data then to utilize that data in order to estimate component, Line Replaceable Unit (LRU), and system reliability analysis metrics. In this paper, we identify a methodology to categorize qualitative data from the ground system PRACA data base for common ground or facility support equipment. Then utilizing a heuristic developed for review of the PRACA data determine what reports identify a credible failure. These data are the used to determine inter-arrival times to perform an estimation of a metric for repairable component-or LRU reliability. This analysis is used to determine failure modes of the equipment, determine the probability of the component failure mode, and support various quantitative differing techniques for performing repairable system analysis. The result is that an effective and concise estimate of components used in manned space flight operations. The advantage is the components or LRU's are evaluated in the same environment and condition that occurs during the launch process.

Monaghan, Mark W.↗
NASA NTRS2008

Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.

Leucht, Kurt W.↗
NASA NTRSDate not supplied

Methodology and Development of SLS Ascent Loads

The methodology and development of the Space Launch System (SLS) Block 1 Boost and Core phase Ascent loads will be presented in this paper. As is common practice, a series of fixed time/mass Finite Element Models of the vehicle were developed for the purpose of evaluating the structural loads and accelerations for particular Mach or time ranges associated with the Boost and Core phases of flight. Load contributors, which vary between bins, include the flight mechanic induced portion of the loads (e.g., Static-Elastic (STEL) or Vehicle Load Indicator (VLI) tool results), gust loads, buffet loads, Solid Rocket Booster thrust oscillations, Core Stage Engine thrust oscillations, maneuvering loads, thrust vector-related dispersions, and Programmed Test Input induced loads. Each of these load contributors will be examined in this paper, as well as the Loads Combination Equations used to generate the final loads. In addition to the typical coupled loads analysis, an Ascent loads evaluation is included in the SLS Artemis 1 Day of Launch process; a summary of this evaluation will also be presented in this paper.

SLS↗
NASA NTRS2001

Launch Vehicle Design Process: Characterization, Technical Integration, and Lessons Learned

Engineering design is a challenging activity for any product. Since launch vehicles are highly complex and interconnected and have extreme energy densities, their design represents a challenge of the highest order. The purpose of this document is to delineate and clarify the design process associated with the launch vehicle for space flight transportation. The goal is to define and characterize a baseline for the space transportation design process. This baseline can be used as a basis for improving effectiveness and efficiency of the design process. The baseline characterization is achieved via compartmentalization and technical integration of subsystems, design functions, and discipline functions. First, a global design process overview is provided in order to show responsibility, interactions, and connectivity of overall aspects of the design process. Then design essentials are delineated in order to emphasize necessary features of the design process that are sometimes overlooked. Finally the design process characterization is presented. This is accomplished by considering project technical framework, technical integration, process description (technical integration model, subsystem tree, design/discipline planes, decision gates, and tasks), and the design sequence. Also included in the document are a snapshot relating to process improvements, illustrations of the process, a survey of recommendations from experienced practitioners in aerospace, lessons learned, references, and a bibliography.

Blair, J. C.↗
NASA NTRS1999

Information Flow in the Launch Vehicle Design/Analysis Process

This paper describes the results of a team effort aimed at defining the information flow between disciplines at the Marshall Space Flight Center (MSFC) engaged in the design of space launch vehicles. The information flow is modeled at a first level and is described using three types of templates: an N x N diagram, discipline flow diagrams, and discipline task descriptions. It is intended to provide engineers with an understanding of the connections between what they do and where it fits in the overall design process of the project. It is also intended to provide design managers with a better understanding of information flow in the launch vehicle design cycle.

Humphries, W. R., Sr.↗
NASA NTRS2012

Mass Analyzers Facilitate Research on Addiction

The famous go/no go command for Space Shuttle launches comes from a place called the Firing Room. Located at Kennedy Space Center in the Launch Control Center (LCC), there are actually four Firing Rooms that take up most of the third floor of the LCC. These rooms comprise the nerve center for Space Shuttle launch and processing. Test engineers in the Firing Rooms operate the Launch Processing System (LPS), which is a highly automated, computer-controlled system for assembly, checkout, and launch of the Space Shuttle. LPS monitors thousands of measurements on the Space Shuttle and its ground support equipment, compares them to predefined tolerance levels, and then displays values that are out of tolerance. Firing Room operators view the data and send commands about everything from propellant levels inside the external tank to temperatures inside the crew compartment. In many cases, LPS will automatically react to abnormal conditions and perform related functions without test engineer intervention; however, firing room engineers continue to look at each and every happening to ensure a safe launch. Some of the systems monitored during launch operations include electrical, cooling, communications, and computers. One of the thousands of measurements derived from these systems is the amount of hydrogen and oxygen inside the shuttle during launch.

Source record↗
NASA NTRS1995

Launch Site Computer Simulation and its Application to Processes

This paper provides an overview of computer simulation, the Lockheed developed STS Processing Model, and the application of computer simulation to a wide range of processes. The STS Processing Model is an icon driven model that uses commercial off the shelf software and a Macintosh personal computer. While it usually takes one year to process and launch 8 space shuttles, with the STS Processing Model this process is computer simulated in about 5 minutes. Facilities, orbiters, or ground support equipment can be added or deleted and the impact on launch rate, facility utilization, or other factors measured as desired. This same computer simulation technology can be used to simulate manufacturing, engineering, commercial, or business processes. The technology does not require an 'army' of software engineers to develop and operate, but instead can be used by the layman with only a minimal amount of training. Instead of making changes to a process and realizing the results after the fact, with computer simulation, changes can be made and processes perfected before they are implemented.

Sham, Michael D.↗
NASA NTRS2007

Enhancing the NASA Expendable Launch Vehicle Payload Safety Review Process Through Program Activities

The safety review process for NASA spacecraft flown on Expendable Launch Vehicles (ELVs) has been guided by NASA-STD 8719.8, Expendable Launch Vehicle Payload Safety Review Process Standard. The standard focused primarily on the safety approval required to begin pre-launch processing at the launch site. Subsequent changes in the contractual, technical, and operational aspects of payload processing, combined with lessons-learned supported a need for the reassessment of the standard. This has resulted in the formation of a NASA ELV Payload Safety Program. This program has been working to address the programmatic issues that will enhance and supplement the existing process, while continuing to ensure the safety of ELV payload activities.

Palo, Thomas E.↗
NASA NTRS1986

Orbital transfer vehicle launch operations study. Processing flows. Volume 3

The Orbit Transfer Vehicle (OTV) processing flow and Resource Identification Sheets (RISs) for the ground based orbit transfer vehicle and for the space based orbit transfer vehicle are the primary source of information for the rest of the Kennedy Space Center (KSC) OTV Launch Operations Study. Work is presented which identifies KSC facility requirements for the OTV Program, simplifies or automates either flow though the application technology, revises test practices and identifies crew sizes or skills used. These flows were used as the primary point of departure from current operations and practices. Analyses results were documented by revising the appropriate RIS page.

Source record↗
NASA NTRS2017

Trajectory Dispersed Vehicle Process for Space Launch System

The Space Launch System (SLS) vehicle is part of NASA's deep space exploration plans that includes manned missions to Mars. Manufacturing uncertainties in design parameters are key considerations throughout SLS development as they have significant effects on focus parameters such as lift-off-thrust-to-weight, vehicle payload, maximum dynamic pressure, and compression loads. This presentation discusses how the SLS program captures these uncertainties by utilizing a 3 degree of freedom (DOF) process called Trajectory Dispersed (TD) analysis. This analysis biases nominal trajectories to identify extremes in the design parameters for various potential SLS configurations and missions. This process utilizes a Design of Experiments (DOE) and response surface methodologies (RSM) to statistically sample uncertainties, and develop resulting vehicles using a Maximum Likelihood Estimate (MLE) process for targeting uncertainties bias. These vehicles represent various missions and configurations which are used as key inputs into a variety of analyses in the SLS design process, including 6 DOF dispersions, separation clearances, and engine out failure studies.

Statham, Tamara↗
NASA NTRS2006

Crew Launch Vehicle (CLV) Upper Stage Configuration Selection Process

The Crew Launch Vehicle (CLV), a key component of NASA's blueprint for the next generation of spacecraft to take humans back to the moon, is being designed and built by engineers at NASA s Marshall Space Flight Center (MSFC). The vehicle s design is based on the results of NASA's 2005 Exploration Systems Architecture Study (ESAS), which called for development of a crew-launch system to reduce the gap between Shuttle retirement and Crew Exploration Vehicle (CEV) Initial Operating Capability, identification of key technologies required to enable and significantly enhance these reference exploration systems, and a reprioritization of near- and far-term technology investments. The Upper Stage Element (USE) of the CLV is a clean-sheet approach that is being designed and developed in-house, with element management at MSFC. The USE concept is a self-supporting cylindrical structure, approximately 115' long and 216" in diameter, consisting of the following subsystems: Primary Structures (LOX Tank, LH2 Tank, Intertank, Thrust Structure, Spacecraft Payload Adaptor, Interstage, Forward and Aft Skirts), Secondary Structures (Systems Tunnel), Avionics and Software, Main Propulsion System, Reaction Control System, Thrust Vector Control, Auxiliary Power Unit, and Hydraulic Systems. The ESAS originally recommended a CEV to be launched atop a four-segment Space Shuttle Main Engine (SSME) CLV, utilizing an RS-25 engine-powered upper stage. However, Agency decisions to utilize fewer CLV development steps to lunar missions, reduce the overall risk for the lunar program, and provide a more balanced engine production rate requirement prompted engineers to switch to a five-segment design with a single Saturn-derived J-2X engine. This approach provides for single upper stage engine development for the CLV and an Earth Departure Stage, single Reusable Solid Rocket Booster (RSRB) development for the CLV and a Cargo Launch Vehicle, and single core SSME development. While the RSRB design has changed since the CLV Project's inception, the USE design has remained essentially a clean-sheet approach. Although a clean-sheet upper stage design inherently carries more risk than a modified design, it does offer many advantages: a design for increased reliability; built-in extensibility to allow for commonality/growth without major redesign; and incorporation of state-of-the-art materials, hardware, and design, fabrication, and test techniques and processes to facilitate a potentially better, more reliable system. Because consideration was given in the ESAS to both clean-sheet and modified USE designs, this paper will highlight the advantages and disadvantages of both approaches and provide a detailed discussion of trades/selections made that led to the final upper stage configuration.

Davis, Daniel J.↗
NASA NTRS2002

Rocket Noise and Vibration Shuttle/Payload Processing and ISS: Launch Pad Vibroacoustics Research at NASA/KSC

This viewgraph presentation provides information on the effects of noise of the SSME Space Shuttle Main Engine upon liftoff from Kennedy Space Center. It covers both effects experienced by astronauts within the Shuttles, and effects on the surrounding environment. The presentation then makes recommendations for design methods which take into account vibroacoustics.

Margasayam, Ravi↗
NASA NTRS2010

Launchable and Retrievable Tetherobot

A proposed robotic system for scientific exploration of rough terrain would include a stationary or infrequently moving larger base robot, to which would be tethered a smaller hopping robot of the type described in the immediately preceding article. The two-robot design would extend the reach of the base robot, making it possible to explore nearby locations that might otherwise be inaccessible or too hazardous for the base robot. The system would include a launching mechanism and a motor-driven reel on the larger robot. The outer end of the tether would be attached to the smaller robot; the inner end of the tether would be attached to the reel. The figure depicts the launching and retrieval process. The launching mechanism would aim and throw the smaller robot toward a target location, and the tether would be paid out from the reel as the hopping robot flew toward the target. Upon completion of exploratory activity at the target location, the smaller robot would be made to hop and, in a coordinated motion, the tether would be wound onto the reel to pull the smaller robot back to the larger one.

Younse, Paulo↗