Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Reusability”

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 721 records · Page 40
All sourcesNASA NTRSDOE OSTI
NASA NTRS1998

Lifting Body Flight Vehicles

NASA has a technology program in place to build the X-33 test vehicle and then the full sized Reusable Launch Vehicle, VentureStar. VentureStar is a Lifting Body (LB) flight vehicle which will carry our future payloads into orbit, and will do so at a much reduced cost. There were three design contenders for the new Reusable Launch Vehicle: a Winged Vehicle, a Vertical Lander, and the Lifting Body(LB). The LB design won the competition. A LB vehicle has no wings and derives its lift solely from the shape of its body, and has the unique advantages of superior volumetric efficiency, better aerodynamic efficiency at high angles-of-attack and hypersonic speeds, and reduced thermal protection system weight. Classically, in a ballistic vehicle, drag has been employed to control the level of deceleration in reentry. In the LB, lift enables the vehicle to decelerate at higher altitudes for the same velocity and defines the reentry corridor which includes a greater cross range. This paper outlines our LB heritage which was utilized in the design of the new Reusable Launch Vehicle, VentureStar. NASA and the U.S. Air Force have a rich heritage of LB vehicle design and flight experience. Eight LB's were built and over 225 LB test flights were conducted through 1975 in the initial LB Program. Three LB series were most significant in the advancement of today's LB technology: the M2-F; HL-1O; and X-24 series. The M2-F series was designed by NASA Ames Research Center, the HL-10 series by NASA Langley Research Center, and the X-24 series by the Air Force. LB vehicles are alive again today.

Barret, Chris↗
NASA NTRS1997

NASA X-34 Technology in Motion

The X-34 technology development program is a joint industry/government project to develop, test, and operate a small, fully-reusable hypersonic flight vehicle. The objective is to demonstrate key technologies and operating concepts applicable to future reusable launch vehicles. Integrated in the vehicle are various systems to assure successful completion of mission objectives, including the Main Propulsion System (MPS). NASA-Marshall Space Flight Center (MSFC) is responsible for developing the X-34's MPS including the design and complete build package for the propulsion system components. The X-34 will be powered by the Fastrac Engine, which is currently in design and development at NASA-MSFC. Fastrac is a single-stage main engine, which burns a mixture of liquid oxygen (LOX) and kerosene(RP-1). The interface between the MPS and Fastrac engine are critical for proper system operation and technologies applicable to future reusable launch vehicles. Deneb's IGRIP software package with the Dynamic analysis option provided a key tool for conducting studies critical to this interface as well as a mechanism to drive the design of the LOX and RP-1 feedlines. Kinematic models were created for the Fastrac Engine and the feedlines for various design concepts. Based on the kinematic simulation within Envision, design and joint limits were verified and system interference controlled. It was also critical to the program to evaluate the effect of dynamic loads visually, providing a verification tool for dynamic analysis and in some cases uncovering areas that had not been considered. Deneb's software put the X-34 technology in motion and has been a key factor in facilitating the strenuous design schedule.

Beech, Geoffrey↗
NASA NTRS2000

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗
NASA NTRS2001

The Launch Systems Operations Cost Model

One of NASA's primary missions is to reduce the cost of access to space while simultaneously increasing safety. A key component, and one of the least understood, is the recurring operations and support cost for reusable launch systems. In order to predict these costs, NASA, under the leadership of the Independent Program Assessment Office (IPAO), has commissioned the development of a Launch Systems Operations Cost Model (LSOCM). LSOCM is a tool to predict the operations & support (O&S) cost of new and modified reusable (and partially reusable) launch systems. The requirements are to predict the non-recurring cost for the ground infrastructure and the recurring cost of maintaining that infrastructure, performing vehicle logistics, and performing the O&S actions to return the vehicle to flight. In addition, the model must estimate the time required to cycle the vehicle through all of the ground processing activities. The current version of LSOCM is an amalgamation of existing tools, leveraging our understanding of shuttle operations cost with a means of predicting how the maintenance burden will change as the vehicle becomes more aircraft like. The use of the Conceptual Operations Manpower Estimating Tool/Operations Cost Model (COMET/OCM) provides a solid point of departure based on shuttle and expendable launch vehicle (ELV) experience. The incorporation of the Reliability and Maintainability Analysis Tool (RMAT) as expressed by a set of response surface model equations gives a method for estimating how changing launch system characteristics affects cost and cycle time as compared to today's shuttle system. Plans are being made to improve the model. The development team will be spending the next few months devising a structured methodology that will enable verified and validated algorithms to give accurate cost estimates. To assist in this endeavor the LSOCM team is part of an Agency wide effort to combine resources with other cost and operations professionals to support models, databases, and operations assessments.

Prince, Frank A.↗
NASA NTRS2001

Survey of Advanced Booster Options for Potential Shuttle Derivative Vehicles

A never-ending major goal for the Space Shuttle program is to continually improve flight safety, as long as this launch system remains in operational service. One of the options to improve system safety and to enhance vehicle performance as well, that has been seriously studied over the past several decades, is to replace the existing strap-on four segment solid rocket boosters (SRB's) with more capable units. A number of booster upgrade options have been studied in some detail, ranging from five segment solids through hybrids and a wide variety of liquid strap-ons (both pressure and pump fed with various propellants); all the way to a completely reusable liquid fly back booster (complete with air breathing engines for controlled landing and return). All of these possibilities appear to offer improvements in varying degrees; and each has their strengths and weaknesses from both programmatic and technical points of view. The most beneficial booster upgrade/design, if the shuttle program were to continue long enough to justify the required investment, would be an approach that greatly increased both vehicle and crew safety. This would be accomplished by increasing the minimum range/minimum altitude envelope that would readily allow abort to orbit (ATO), possibly even to zero/zero, and possibly reduce or eliminate the Return to Launch Site (RTLS) and even the Trans Atlantic Landing (TAL) abort mode requirements. This paper will briefly survey and discuss all of the various booster'upgrade options studied previously, and compare their relative attributes. The survey will explicitly discuss, in summary comparative form, options that include: five segment solids; several hybrid possibilities; pressure and/or pump-fed liquids using either LO2/kerosene, H2O/kerosene and LO2/J2, any of which could be either fully expendable, partly or fully reusable; and finally a fully reusable liquid fly back booster system, with a number of propellant and propulsion system options. Performance and configuration comparison illustrations and tables will be included to provide a comprehensive survey for the paper.

Sackheim, Robert L.↗
NASA NTRS2001

I(sup STAR), NASA's Next Step in Air-Breathing Propulsion for Space Access

The United States' National Aeronautics and Space Administration (NASA) has established a strategic plan for future activities in space. A primary goal of this plan is to make drastic improvements in the cost and safety of earth to low-earth-orbit transportation. One approach to achieving this goal is through the development of highly reusable, highly reliable space transportation systems analogous to the commercial airline system. In the year 2000, NASA selected the Rocket Based Combined Cycle (RBCC) engine as the next logical step towards this goal. NASA will develop a complete flight-weight, pump-fed engine system under the Integrated System Test of an Airbreathing Rocket (I(sup STAR)) Project. The objective of this project is develop a reusable engine capable of self-powering a vehicle through the air-augmented rocket, ramjet and scramjet modes required in all RBCC based operational vehicle concepts. The project is currently approved and funded to develop the engine through ground test demonstration. Plans are in place to proceed with flight demonstration pending funding approval. The project is in formulation phase and the Preliminary Requirements Review has been completed. The engine system and vehicle have been selected at the conceptual level. The I(sup STAR) engine concept is based on an air-breathing flowpath downselected from three configurations evaluated in NASA's Advanced Reusable Technology contract. The selected flowpath features rocket thrust chambers integrated into struts separating modular flowpath ducts, a variable geometry inlet, and a thermally choked throat. The engine will be approximately 220 inches long and 79 inches wide and fueled with a hydrocarbon fuel using liquid oxygen as the primary oxidizer candidate. The primary concept for the pump turbine drive is pressure-fed catalyzed hydrogen peroxide. In order to control costs, the flight demonstration vehicle will be launched from a B-52 aircraft. The vehicle concept is based on the Air Breathing Launch Vehicle 4 (ABLV4) lifting body configuration which has design heritage from NASA's NASP Program. The vehicle will be designed to accelerate from Mach 0.8 to Mach 7 and will be equipped with landing gear for horizontal landing. The complete vehicle, including the engine, will be designed for 25 flights and will be approximately 33 feet long with a total vehicle weight of approximately 25000 lbs.

Hutt, John J.↗
NASA NTRS2002

Cost Per Pound From Orbit

Traditional studies of Reusable Launch Vehicle (RLV) designs have focused on designs that are completely reusable except for the fuel. This may not be realistic with current technology . An alternate approach is to look at partially reusable launch vehicles. This raises the question of which parts should be reused and which parts should be expendable. One approach is to consider the cost/pound of returning these parts from orbit. With the shuttle, this cost is about three times the cost/pound of launching payload into orbit. A subtle corollary is that RLVs are much less practical for higher orbits, such as the one on which the International Space Station resides, than they are for low earth orbits.

Merriam, M. L.↗
NASA NTRS2002

Manufacturing Process Simulation of Large-Scale Cryotanks

NASA's Space Launch Initiative (SLI) is an effort to research and develop the technologies needed to build a second-generation reusable launch vehicle. It is required that this new launch vehicle be 100 times safer and 10 times cheaper to operate than current launch vehicles. Part of the SLI includes the development of reusable composite and metallic cryotanks. The size of these reusable tanks is far greater than anything ever developed and exceeds the design limits of current manufacturing tools. Several design and manufacturing approaches have been formulated, but many factors must be weighed during the selection process. Among these factors are tooling reachability, cycle times, feasibility, and facility impacts. The manufacturing process simulation capabilities available at NASA's Marshall Space Flight Center have played a key role in down selecting between the various manufacturing approaches. By creating 3-D manufacturing process simulations, the varying approaches can be analyzed in a virtual world before any hardware or infrastructure is built. This analysis can detect and eliminate costly flaws in the various manufacturing approaches. The simulations check for collisions between devices, verify that design limits on joints are not exceeded, and provide cycle times which aid in the development of an optimized process flow. In addition, new ideas and concerns are often raised after seeing the visual representation of a manufacturing process flow. The output of the manufacturing process simulations allows for cost and safety comparisons to be performed between the various manufacturing approaches. This output helps determine which manufacturing process options reach the safety and cost goals of the SLI.

Babai, Majid↗
NASA NTRS2003

RS-84 Engine

The RS-84 is the first reusable hydrocarbon staged combustion liquid rocket engine. This engine is being developed to meet NASA s crew safety goals with a highly reliable and low cost main engine as a part of the NASA Space Launch Initiative program for the next generation reusable launch system. The NASA-MSFC and Rocketdyne team brings over 50 years of successful rocket engine development experience to meet the challenges of this new program. This team s extensive design database has been anchored with almost five decades of hydrocarbon rocket engine development and flight operations experience including Delta, Atlas, and Saturn vehicles and nearly three decades of successfully operating the world s only reusable pump-fed rocket engine, the Space Shuttle Main Engine. The team also fully benefits from the proven and experienced engineering staffs that recently completed the successful MC-1 FASTRAC , XRS-2200, and RS-68 engine development programs and the ongoing IPD and RS-76 technology development. Advances in integrated parametric design and analysis tools, advanced materials knowledge base, and state-of-the-art fabrication processes anchored and refined during the recent engine development programs are already being used by the team to design this engine.

Stegman, E.↗
NASA NTRS2004

Measuring Permeability of Composite Cryotank Laminants

This paper describes a test method developed to identify whether certain materials and material systems are suitable candidates for large pressurized reusable cryogenic tanks intended for use in current and future manned launch systems. It provides a quick way to screen numerous candidate materials for permeability under anticipated loading environments consistent with flight conditions, as well as addressing reusability issues. cryogenic tank, where the major design issue was hydrogen permeability. It was successfully used to evaluate samples subjected to biaxial loading while maintaining test temperatures near liquid hydrogen. After each sample was thermally preconditioned, a cyclic pressure load was applied to simulate the in-plane strain. First permeability was measured while a sample was under load. Then the sample was unloaded and allowed to return to ambient temperature. The test was repeated to simulate reusability, in order to evaluate its effects on material permeability.

Oliver, Stanley T.↗
NASA NTRS2003

Manufacturing Process Simulation of Large-Scale Cryotanks

NASA's Space Launch Initiative (SLI) is an effort to research and develop the technologies needed to build a second-generation reusable launch vehicle. It is required that this new launch vehicle be 100 times safer and 10 times cheaper to operate than current launch vehicles. Part of the SLI includes the development of reusable composite and metallic cryotanks. The size of these reusable tanks is far greater than anything ever developed and exceeds the design limits of current manufacturing tools. Several design and manufacturing approaches have been formulated, but many factors must be weighed during the selection process. Among these factors are tooling reachability, cycle times, feasibility, and facility impacts. The manufacturing process simulation capabilities available at NASA.s Marshall Space Flight Center have played a key role in down selecting between the various manufacturing approaches. By creating 3-D manufacturing process simulations, the varying approaches can be analyzed in a virtual world before any hardware or infrastructure is built. This analysis can detect and eliminate costly flaws in the various manufacturing approaches. The simulations check for collisions between devices, verify that design limits on joints are not exceeded, and provide cycle times which aide in the development of an optimized process flow. In addition, new ideas and concerns are often raised after seeing the visual representation of a manufacturing process flow. The output of the manufacturing process simulations allows for cost and safety comparisons to be performed between the various manufacturing approaches. This output helps determine which manufacturing process options reach the safety and cost goals of the SLI. As part of the SLI, The Boeing Company was awarded a basic period contract to research and propose options for both a metallic and a composite cryotank. Boeing then entered into a task agreement with the Marshall Space Flight Center to provide manufacturing simulation support. This paper highlights the accomplishments of this task agreement, while also introducing the capabilities of simulation software.

Babai, Majid↗
NASA NTRS2002

Oxidation Behavior of GRCop-84 Copper Alloy Assessed

NASA's goal of safe, affordable space transportation calls for increased reliability and lifetimes of launch vehicles, and significant reductions of launch costs. The areas targeted for enhanced performance in the next generation of reusable launch vehicles include combustion chambers and nozzle ramps; therefore, the search is on for suitable liner materials for these components. GRCop-84 (Cu-8Cr-4Nb), an advanced copper alloy developed at the NASA Glenn Research Center in conjunction with Case Western Reserve University, is a candidate. The current liner of the Space Shuttle Main Engine is another copper alloy, NARloy-Z (Cu-3Ag-0.1Zr). It provides a benchmark against which to compare the properties of candidate successors. The thermomechanical properties of GRCop-84 have been shown to be superior, and its physical properties comparable, to those of NARloy-Z. However, environmental durability issues control longevity in this application: because copper oxide scales are not highly protective, most copper alloys are quickly consumed in oxygen environments at elevated temperatures. In consequence, NARloy-Z and most other copper alloys are prone to blanching, a degradation process that occurs through cycles of oxidation-reduction as the oxide is repeatedly formed and removed because of microscale fluctuations in the oxygen-hydrogen fuel systems of rocket engines. The Space Shuttle Main Engine lining typically degraded by blanching-induced hot spots that lead to surface roughening, pore formation, and coolant leakage. Therefore, resistance to oxidation and blanching are key requirements for second-generation reusable launch vehicle liners. The rocket engine ambient includes H2 (fuel) and H2O (combustion product) and is, hence, under reduced oxygen partial pressures. Accordingly, our studies were expanded to include oxygen partial pressures as low as 322 parts per million (ppm) at the temperatures likely to be experienced in service. A comparison of 10-hr weight gains of GRCop-84, NARloy-Z, and pure copper in 0.032, 2.2, and 100 percent oxygen from 550 to 750 C is shown. In 2.2 vol% and higher oxygen content, GRCop-84 oxidation was slower than that of NARloy-Z or Cu, but that advantage was lost or diminished in 322-ppm O2. Over longer (50-hr) exposures in 1.0 atm O2, however, the advantage of GRCop-84 increased significantly, its oxidation rate becoming approximately 10 times slower than those of Cu and NARloy-Z from 500 to 700 C. Weight gains were moderate and the kinetics parabolic for all three materials in 2.2 vol% and higher oxygen content; however, in 322-ppm O2, the scales were nonprotective below about 650 C, as reflected in linear kinetics and large weight gains. The superior oxidation resistance of GRCop-84 is likely related to the kinetics of extra oxygen consumption to form the additional oxides of Cr and Nb detected beneath the GRCop-84 oxide layer. While we continue to evaluate the blanching resistance of GRCop-84 in other tests, these oxidation results indicate that GRCop-84 is suitable as a reusable launch vehicle liner, and in applications where it is desired to use a copper alloy but without the risk of oxidative failure. Three bar charts comparing overall specific weight gains by each of the three materials studied. The top chart is for oxidation in 1.0 atm of oxygen, the middle is for 2.2% oxygen (balance argon), and the bottom is for 0.0322% oxygen. GRCop-84 outperforms the other two materials, showing the least weight gain in nearly all cases.

Thomas-Ogbuji, Linus U.↗
NASA NTRS2006

BAE Systems Radiation Hardened SpaceWire ASIC and Roadmap

An Application Specific Integrated Circuit (ASIC) that implements the SpaceWire protocol has been developed in a radiation hardened 0.25 micron CMOS, technology. This effort began in March 2003 as a joint development between the NASA Goddard Space Flight Center (GSFC) and BAE Systems. The BAE Systems SpaceWire ASlC is comprised entirely of reusable core elements, many of which are already flight-proven. It incorporates a 4-port SpaceWire router with two local ports, dual PC1 bus interfaces, a microcontroller, 32KB of internal memory, -and a memory controller for additional external memory use. The SpaceWire ASlC is planned for use on both the Geostationary Operational Environmental Satellites (GOES)-R and the Lunar Reconnaissance Orbiter (LRO). Engineering parts have already been delivered to both programs. This paper discusses the SpaceWire protocol and those elements of it that have been built into the current SpaceWire reusable core. There are features within the core that go beyond the current standard that can be enabled or disabled by the user and these will be described. The adaptation of SpaceWire to BAE Systems' On Chip Bus (OCB) for compatibility with the other reusable cores will be discussed. Optional configurations within user systems will be shown. The physical imp!ementation of the design will be described and test results from the hardware will be discussed. Finally, the BAE Systems roadmap for SpaceWire developments will be discussed, including some products already in design as well as longer term plans.

Berger, Richard↗
NASA NTRS2007

A One Chip Hardened Solution for High Speed SpaceWire System Implementations. Session: Components

An Application Specific Integrated Circuit (ASIC) that implements the SpaceWire protocol has been developed in a radiation hardened 0.25 micron CMOS technology. This effort began in March 2003 as a joint development between the NASA Goddard Space Flight Center (GSFC) and BAE Systems. The BAE Systems SpaceWire ASIC is comprised entirely of reusable core elements, many of which are already flight-proven. It incorporates a router with 4 SpaceWire ports and two local ports, dual PC1 bus interfaces, a microcontroller, 32KB of internal memory, and a memory controller for additional external memory use. The SpaceWire cores are also reused in other ASICs under development. The SpaceWire ASIC is planned for use on the Geostationary Operational Environmental Satellites (GOES)-R, the Lunar Reconnaissance Orbiter (LRO) and other missions. Engineering and flight parts have been delivered to programs and users. This paper reviews the SpaceWire protocol and those elements of it that have been built into the current and next SpaceWire reusable cores and features within the core that go beyond the current standard and can be enabled or disabled by the user. The adaptation of SpaceWire to BAE Systems' On Chip Bus (OCB) for compatibility with the other reusable cores will be reviewed and highlighted. Optional configurations within user systems and test boards will be shown. The physical implementation of the design will be described and test results from the hardware will be discussed. Application of this ASIC and other ASICs containing the SpaceWire cores and embedded microcontroller to Plug and Play and reconfigurable implementations will be described. Finally, the BAE Systems roadmap for SpaceWire developments will be updated, including some products already in design as well as longer term plans.

Marshall, Joseph R.↗
NASA NTRS2011

Designing the Space Shuttle Propulsion System

The major elements of the Space Shuttle Main Propulsion System include two reusable solid rocket motors integrated into recoverable solid rocket boosters, an expendable external fuel and oxidizer tank, and three reusable Space Shuttle Main Engines. Both the solid rocket motors and space shuttle main engines ignite prior to liftoff, with the solid rocket boosters separating about two minutes into flight. The external tank separates after main engine shutdown and is safely expended in the ocean. The SSME's, integrated into the Space Shuttle Orbiter aft structure, are reused after post landing inspections. Both the solid rocket motors and the space shuttle main engine throttle during early ascent flight to limit aerodynamic loads on the structure. The configuration is called a stage and a half as all the propulsion elements are active during the boost phase, and the SSME's continue operation to achieve orbital velocity approximately eight and a half minutes after liftoff. Design and performance challenges were numerous, beginning with development work in the 1970 s. The solid rocket motors were large, and this technology had never been used for human space flight. The SSME s were both reusable and very high performance staged combustion cycle engines, also unique to the Space Shuttle. The multi body side mount configuration was unique and posed numerous integration and interface challenges across the elements. Operation of the system was complex and time consuming. This paper discusses a number of the system level technical challenges including development and operations.

Owen, James↗
NASA NTRS2011

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.

Ingalls, John↗
NASA NTRS2003

CLARAty Functional-Layer Software

Functional-layer software for the Coupled Layer Architecture for Robotics Autonomy (CLARAty) is being developed. [CLARAty was described in Coupled-Layer Architecture for Advanced Software for Robots (NPO-21218), NASA Tech Briefs, Vol. 26, No. 12 (December 2002), page 48. To recapitulate: CLARAty was proposed to improve the modularity of robotic software while tightening the coupling between planning/execution and control subsystems. Whereas prior robotic software architectures have typically contained three levels, the CLARAty architecture contains two layers: a decision layer and a functional layer.] Just as an operating system provides abstraction from computational hardware, the CLARAty functional-layer software provides for abstraction for the different robotic systems. The functional-layer software establishes interrelated, object-oriented hierarchies that contain active and passive objects that represent the different levels of system abstrations and components. The functional-layer software is decomposed into a set of reusable core components and a set of extended components that adapt the reusable set to specific hardware implementations. The reusable components (a) provide behavior and interface definitions and implementations of basic functionality, (b) provide local executive capabilities, (c) manage local resources, and (d) support state and resource queries by the decision layer. Software for robotic systems can be built by use of these components.

Nesnas, Issa↗
NASA NTRS2011

Shuttle Propulsion Overview - The Design Challenges

The major elements of the Space Shuttle Main Propulsion System include two reusable solid rocket motors integrated into recoverable solid rocket boosters, an expendable external fuel and oxidizer tank, and three reusable Space Shuttle Main Engines. Both the solid rocket motors and space shuttle main engines ignite prior to liftoff, with the solid rocket boosters separating about two minutes into flight. The external tank separates, about eight and a half minutes into the flight, after main engine shutdown and is safely expended in the ocean. The SSME's, integrated into the Space Shuttle Orbiter aft structure, are reused after post landing inspections. The configuration is called a stage and a half as all the propulsion elements are active during the boost phase, with only the SSME s continuing operation to achieve orbital velocity. Design and performance challenges were numerous, beginning with development work in the 1970's. The solid rocket motors were large, and this technology had never been used for human space flight. The SSME s were both reusable and very high performance staged combustion cycle engines, also unique to the Space Shuttle. The multi body side mount configuration was unique and posed numerous integration and interface challenges across the elements. Operation of the system was complex and time consuming. This paper describes the design challenges and key areas where the design evolved during the program.

Owen, James W.↗