Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations”

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 505 records · Page 28

Shared mission operations concept

Historically, new JPL flight projects have developed a Mission Operations System (MOS) as unique as their spacecraft, and have utilized a mission-dedicated staff to monitor and control the spacecraft through the MOS. NASA budgetary pressures to reduce mission operations costs have led to the development and reliance on multimission ground system capabilities. The use of these multimission capabilities has not eliminated an ongoing requirement for a nucleus of personnel familiar with a given spacecraft and its mission to perform mission-dedicated operations. The high cost of skilled personnel required to support projects with diverse mission objectives has the potential for significant reduction through shared mission operations among mission-compatible projects. Shared mission operations are feasible if: (1) the missions do not conflict with one another in terms of peak activity periods, (2) a unique MOS is not required, and (3) there is sufficient similarity in the mission profiles so that greatly different skills would not be required to support each mission. This paper will further develop this shared mission operations concept. We will illustrate how a Discovery-class mission would enter a 'partner' relationship with the Voyager Project, and can minimize MOS development and operations costs by early and careful consideration of mission operations requirements.

Spradlin, Gary L.↗

The feasibility study and evaluation of applying expert system techniques to the mission operations for the AXAF-I spacecraft

Advanced X-ray Astrophysics Facility - Imaging (AXAF-I) is a spacecraft for X-ray emitting sources observation and has been tentatively scheduled for a space shuttle launch in late 1998 at the Kennedy Space Center. Its main objectives are 'to determine the nature of astronomical objects ranging from normal stars to quasars, to understand the nature of the physical processes which take place in and between astronomical objects, and to add to our understanding of the history and evolution of the universe.' The AXAF-I will have an expected five year life time for the science mission phase. During the science mission phase, the monitoring and management operation of the flight and ground systems is personnel intensive, requiring system experts on duty around the clock. The purpose of the expert system presented in this report is intended to reduce the level of expertise, training, and personnel requirement for the mission operation. The telemetry data from the spacecraft can be divided into two categories: the science observation data and the engineering status data. The science data contains the outputs from the X-ray sensing devices and will be forwarded to the AXAF-I Science Center for interpretation; while the engineering status data will be monitored by the Operation Control Center (OCC) for the operation diagnosis of the spacecraft. The expert system is designed to assist the operation controllers at the OCC to perform the daily mission operations. Since there are hundreds of engineering telemetry data points and the interpretation of the telemetry depends on many factors, e.g., sun or eclipse, the monitoring of the AXAF-I is not a trivial task. In this phase of expert system development, the focus has been limited to the engineering data interpretation, i.e., warnings will be provided to the operation controllers to signal any anomaly. The system is hosted in a Silicon Graphics Indigo-2 workstation running the IRIX operating system. The expert system tool used is the G2 system from Gensym (Gensy).

Chang, Kai H.↗

Payload Operations

The objective of this paper is to provide the future ISS scientist and/or engineer a sense of what ISS payload operations are expected to be. This paper uses a real-time operations scenario to convey this message. The real-time operations scenario begins at the initiation of payload operations and runs through post run experiment analysis. In developing this scenario, it is assumed that the ISS payload operations flight and ground capabilities are fully available for use by the payload user community. Emphasis is placed on telescience operations whose main objective is to enable researchers to utilize experiment hardware onboard the International Space Station as if it were located in their terrestrial laboratory. An overview of the Payload Operations Integration Center (POIC) systems and user ground system options is included to provide an understanding of the systems and interfaces users will utilize to perform payload operations. Detailed information regarding POIC capabilities can be found in the POIC Capabilities Document, SSP 50304.

Cissom, R. D.↗

Mission Operations with an Autonomous Agent

The Remote Agent (RA) is an Artificial Intelligence (AI) system which automates some of the tasks normally reserved for human mission operators and performs these tasks autonomously on-board the spacecraft. These tasks include activity generation, sequencing, spacecraft analysis, and failure recovery. The RA will be demonstrated as a flight experiment on Deep Space One (DSI), the first deep space mission of the NASA's New Millennium Program (NMP). As we moved from prototyping into actual flight code development and teamed with ground operators, we made several major extensions to the RA architecture to address the broader operational context in which PA would be used. These extensions support ground operators and the RA sharing a long-range mission profile with facilities for asynchronous ground updates; support ground operators monitoring and commanding the spacecraft at multiple levels of detail simultaneously; and enable ground operators to provide additional knowledge to the RA, such as parameter updates, model updates, and diagnostic information, without interfering with the activities of the RA or leaving the system in an inconsistent state. The resulting architecture supports incremental autonomy, in which a basic agent can be delivered early and then used in an increasingly autonomous manner over the lifetime of the mission. It also supports variable autonomy, as it enables ground operators to benefit from autonomy when L'@ey want it, but does not inhibit them from obtaining a detailed understanding and exercising tighter control when necessary. These issues are critical to the successful development and operation of autonomous spacecraft.

Pell, Barney↗

Operational Considerations when Designing New Ground Systems

The Hubble Space Telescope (HST) launched in April of 1991 with a nominal 15-year old mission. Since then, the HST mission life has been extended to 2010. As is true for all NASA missions, HST is being asked to decrease its operational costs for the remainder of its mission life. Various techniques are being incorporated for cost reductions, with one of the core means being the design of a new and more efficient ground system for HST operations. This new ground system, "Vision 2000", will reduce operational and maintenance costs and also provide the HST Project with added flexibility to react to future changes. Vision 2000 began supporting HST Operations in January of 1999 and will support the mission for the remainder of the mission life. Upgrading a satellite's ground system is a popular approach for reducing costs, but it is also inherently risky. Validating a new ground system can be a severe distraction to a flight team while operating a satellite. Mission data collection and health and safety requirements are rarely, if ever, relaxed during this validation period, forcing flight teams to undertake an additional task while operating the satellite. Additionally, flight teams must usually undergo extensive training to effectively utilize the new system. Once again, this training usually occurs as an additional task, in addition to the nominal satellite operations. While operating the spacecraft, the Flight Team typically assists in the design, validation, and verification of a new ground system. This is a distraction and strain on the Flight Team, but the benefit of using the Flight Team in all phases of ground system development far outweigh the negative aspects. Finally, above the cost of the new system, the integration into the facility with the current control center system are resources and costs not normally taken into account in the design phase of the new system. In addition to the standard issues faced by a Project when upgrading its ground system, the HST Project also must continue to support Space Shuttle servicing missions, which occur approximately every two to three years. This paper will address many of the issues common to all missions when re-hosting ground systems, and those faced by the HST Project in particular.

Walyus, Keith↗

ISS Payload Operations: The Need for and Benefit of Responsive Planning

International Space Station (ISS) payload operations are controlled through implementation of a payload operations plan. This plan, which represents the defined approach to payload operations in general, can vary in terms of level of definition. The detailed plan provides the specific sequence and timing of each component of a payload's operations. Such an approach to planning was implemented in the Spacelab program. The responsive plan provides a flexible approach to payload operations through generalization. A responsive approach to planning was implemented in the NASA/Mir Phase 1 program, and was identified as a need during the Skylab program. The current approach to ISS payload operations planning and control tends toward detailed planning, rather than responsive planning. The use of detailed plans provides for the efficient use of limited resources onboard the ISS. It restricts flexibility in payload operations, which is inconsistent with the dynamic nature of the ISS science program, and it restricts crew desires for flexibility and autonomy. Also, detailed planning is manpower intensive. The development and implementation of a responsive plan provides for a more dynamic, more accommodating, and less manpower intensive approach to planning. The science program becomes more dynamic and responsive as the plan provides flexibility to accommodate real-time science accomplishments. Communications limitations and the crew desire for flexibility and autonomy in plan implementation are readily accommodated with responsive planning. Manpower efficiencies are accomplished through a reduction in requirements collection and coordination, plan development, and maintenance. Through examples and assessments, this paper identifies the need to transition from detailed to responsive plans for ISS payload operations. Examples depict specific characteristics of the plans. Assessments identify the following: the means by which responsive plans accommodate the dynamic nature of science programs and the crew desire for flexibility; the means by which responsive plans readily accommodate ISS communications constraints; manpower efficiencies to be achieved through use of responsive plans; and the implications of responsive planning relative to resource utilization efficiency.

Nahay, Ed↗

Efficient Merge and Insert Operations for Binary Heaps and Trees

Binary heaps and binary search trees merge efficiently. We introduce a new amortized analysis that allows us to prove the cost of merging either binary heaps or balanced binary trees is O(l), in the amortized sense. The standard set of other operations (create, insert, delete, extract minimum, in the case of binary heaps, and balanced binary trees, as well as a search operation for balanced binary trees) remain with a cost of O(log n). For binary heaps implemented as arrays, we show a new merge algorithm that has a single operation cost for merging two heaps, a and b, of O(absolute value of a + min(log absolute value of b log log absolute value of b. log absolute value of a log absolute value of b). This is an improvement over O(absolute value of a + log absolute value of a log absolute value of b). The cost of the new merge is so low that it can be used in a new structure which we call shadow heaps. to implement the insert operation to a tunable efficiency. Shadow heaps support the insert operation for simple priority queues in an amortized time of O(f(n)) and other operations in time O((log n log log n)/f (n)), where 1 less than or equal to f (n) less than or equal to log log n. More generally, the results here show that any data structure with operations that change its size by at most one, with the exception of a merge (aka meld) operation, can efficiently amortize the cost of the merge under conditions that are true for most implementations of binary heaps and search trees.

Kuszmaul, Christopher Lee↗

Enabling Advanced Automation in Spacecraft Operations with the Spacecraft Emergency Response System

True autonomy is the Holy Grail of spacecraft mission operations. The goal of launching a satellite and letting it manage itself throughout its useful life is a worthy one. With true autonomy, the cost of mission operations would be reduced to a negligible amount. Under full autonomy, any problems (no matter the severity or type) that may arise with the spacecraft would be handled without any human intervention via some combination of smart sensors, on-board intelligence, and/or smart automated ground system. Until the day that complete autonomy is practical and affordable to deploy, incremental steps of deploying ever-increasing levels of automation (computerization of once manual tasks) on the ground and on the spacecraft are gradually decreasing the cost of mission operations. For example, NASA's Goddard Space Flight Center (NASA-GSFC) has been flying spacecraft with low cost operations for several years. NASA-GSFC's SMEX (Small Explorer) and MIDEX (Middle Explorer) missions have effectively deployed significant amounts of automation to enable the missions to fly predominately in 'light-out' mode. Under light-out operations the ground system is run without human intervention. Various tools perform many of the tasks previously performed by the human operators. One of the major issues in reducing human staff in favor of automation is the perceived increased in risk of losing data, or even losing a spacecraft, because of anomalous conditions that may occur when there is no one in the control center. When things go wrong, missions deploying advanced automation need to be sure that anomalous conditions are detected and that key personal are notified in a timely manner so that on-call team members can react to those conditions. To ensure the health and safety of its lights-out missions, NASA-GSFC's Advanced Automation and Autonomy branch (Code 588) developed the Spacecraft Emergency Response System (SERS). The SERS is a Web-based collaborative environment that enables secure distributed fault and resource management. The SERS incorporates the use of intelligent agents, threaded discussions, workflow, database connectivity, and links to a variety of communications devices (e.g., two-way paging, PDA's, and Internet phones) via commercial gateways. When the SERS detects a problem, it notifies on-call team members, who then can remotely take any necessary actions to resolve the anomalies.The SERS goes well beyond a simple '911' system that sends out an error code to everyone with a pager. Instead, SERS' software agents send detailed data (i.e., notifications) to the most appropriate team members based on the type and severity of the anomaly and the skills of the on-call team members. The SERS also allows the team members to respond to the notifications from their wireless devices. This unique capability ensures rapid response since the team members no longer have to go to a PC or the control center for every anomalous event. Most importantly, the SERS enables safe experimentation with various techniques for increasing levels of automation, leading to robust autonomy. For the MIDEX missions at NASA GSFC, the SERS is used to provide 'human-in-the-loop' automation. During lights-out operations, as greater control is given to the MIDEX automated systems, the SERS can be configured to page remote personnel and keep them informed regarding actions taking place in the control center. Remote off-duty operators can even be given the option of enabling or inhibiting a specific automated response in near real time via their two-way pagers. The SERS facilitates insertion of new technology to increase automation, while maintaining the safety and security of mission resources. This paper will focus on SERS' overall functionality and how SERS has been designed to handle the monitoring and emergency response for missions with varying levels of automation. The paper will also convey some of the key lessons learned from SERS' deployment across of variety of missions, highlighting this incremental approach to achieving 'robust autonomy'.

Breed, Julie↗

An Experimental Study of the Operating Temperature in a Loop Heat Pipe with Two Evaporators and Two Condensers

This paper presents a comprehensive experimental study of the loop operating temperature in a loop heat pipe (LHP) which has two parallel evaporators and two parallel condensers. In a single evaporator LHP, it is well known that the loop operating temperature is a function of the heat load, the sink temperature and the ambient temperature. The objective of the present study emphasizes on the stability of the loop operating temperature and parameters that affects the loop operation. Tests results show that the loop operating temperature is a function of the total system heat load, sink temperature, ambient temperature, and beat load distribution between the two evaporators. Under most conditions, only one compensation chamber (CC) contains two-phase fluid and controls the loop operating temperature, and the other CC is completely filled with liquid. Moreover, as the test condition changes, control of the loop operating temperature often shifted from one CC to another. In spite of complex interactions between various components, the test loop has demonstrated very robust operation even during fast transients.

Ku, Jentung↗

Handling Qualities Influences on Civil Tiltrotor Terminal Operating Procedure Development

The potential for tiltrotor aircraft as civil transports has been well recognized. Realization of that potential requires development of operating procedures tailored to take advantage of the tiltrotor's capabilities, including thrust vectoring independent of body pitch attitude and good low-speed control. While the tiltrotor shares flight characteristics with both fixed wing airplanes and helicopters, it must convert between those flight modes, typically within the context of precise terminal operations. A series of piloted simulation experiments has been conducted on the NASA Ames Research Center Vertical Motion Simulator (VMS) to investigate the influence of tiltrotor cockpit design features on developing certification and operating criteria for civil tiltrotor transports. Handling qualities evaluations have shaped cockpit design guidelines and operating procedure development for a civil tiltrotor. In particular, four topics demonstrate the interplay of handling qualities and operations profile in the development of terminal operating procedures and cockpit or control equipment for a civil tiltrotor: conversion (airplane to helicopter mode), final approach path angle, operating profile speeds and speed changes (particularly under instrument conditions), and one engine inoperative operational considerations.

Decker, William A.↗

Extending ACTS Operations Through a University-Based Consortium

The Advanced Communications Technology Satellite (ACTS) program was slated for decommissioning in October 2000 as was announced at the 6th Ka-band Utilization Conference in May 2000. Quite a celebration was had at that event too centering on the decommissioning of this very successful technology program. With plans in place to move the spacecraft to an orbital graveyard and then shut the system down, NASA was challenged to consider the feasibility of extending operations for education and research purposes provided that an academic organization would be willing to cover operations costs. Continuing operations of the system was determined viable and in the fall of 2000, an announcement was made by NASA to consider extending operations. Plans are now in place to continue the operations of ACTS through a university-based consortium led by Ohio University, Athens, Ohio. Initial plans are for two more years of operations, with options to extend up to a total of four years. This paper will present the change in plans to continue operations of ACTS. A description of the multi-month transition of the spacecraft to its new and final orbital location is provided. With the spacecraft at this new location, an update on its performance is presented as well as estimates of long-term performance. The consortium development will be presented along with its organization, membership, and operations plans for using ACTS.

Bauer, Robert↗

Potential Operating Orbits for Fission Electric Propulsion Systems Driven by the SAFE-400

Safety must be ensured during all phases of space fission system design, development, fabrication, launch, operation, and shutdown. One potential space fission system application is fission electric propulsion (FEP), in which fission energy is converted into electricity and used to power high efficiency (Isp greater than 3000s) electric thrusters. For these types of systems it is important to determine which operational scenarios ensure safety while allowing maximum mission performance and flexibility. Space fission systems are essentially nonradioactive at launch, prior to extended operation at high power. Once high power operation begins, system radiological inventory steadily increases as fission products build up. For a given fission product isotope, the maximum radiological inventory is typically achieved once the system has operated for a length of time equivalent to several half-lives. After that time, the isotope decays at the same rate it is produced, and no further inventory builds in. For an FEP mission beginning in Earth orbit, altitude and orbital lifetime increase as the propulsion system operates. Two simultaneous effects of fission propulsion system operation are thus (1) increasing fission product inventory and (2) increasing orbital lifetime. Phrased differently, as fission products build up, more time is required for the fission products to naturally convert back into non-radioactive isotopes. Simultaneously, as fission products build up, orbital lifetime increases, providing more time for the fission products to naturally convert back into non-radioactive isotopes. Operational constraints required to ensure safety can thus be quantified.

Houts, Mike↗

Potential Operating Orbits for the SAFE-400

Safety must be ensured during all phases of space fission system design, development, fabrication, launch, operation, and shutdown. One potential space fission system application is fission electric propulsion (FEP), in which fission energy is converted into electricity and used to power high efficiency (Isp is greater than 3000s) electric thrusters. For these types of systems it is important to determine which operational scenarios ensure safety while allowing maximum mission performance and flexibility. Space fission systems are essentially non-radioactive at launch, prior to extended operation at high power. Once high power operation begins, system radiological inventory steadily increases as fission products build up. For a given fission product isotope, the maximum radiological inventory is typically achieved once the system has operated for a length of time equivalent to several half-lives. After that time, the isotope decays at the same rate it is produced, and no further inventory builds in. For an FEP mission beginning in Earth orbit, altitude and orbital lifetime increase as the propulsion system operates. Two simultaneous effects of fission propulsion system operation are thus (1) increasing fission product inventory and (2) increasing orbital lifetime. Phrased differently, as fission products build up, more time is required for the fission products to naturally convert back into non-radioactive isotopes. Simultaneously, as fission products build up, orbital lifetime increases, providing more time for the fission products to naturally convert back into non-radioactive isotopes. Operational constraints required to ensure safety can thus be quantified.

Houts, Mike↗

New Directions in Space Operations Services in Support of Interplanetary Exploration

To gain access to the necessary operational processes and data in support of NASA's Lunar/Mars Exploration Initiative, new services, adequate levels of computing cycles and access to myriad forms of data must be provided to onboard spacecraft and ground based personnel/systems (earth, lunar and Martian) to enable interplanetary exploration by humans. These systems, cycles and access to vast amounts of development, test and operational data will be required to provide a new level of services not currently available to existing spacecraft, on board crews and other operational personnel. Although current voice, video and data systems in support of current space based operations has been adequate, new highly reliable and autonomous processes and services will be necessary for future space exploration activities. These services will range from the more mundane voice in LEO to voice in interplanetary travel which because of the high latencies will require new voice processes and standards. New services, like component failure predictions based on data mining of significant quantities of data, located at disparate locations, will be required. 3D or holographic representation of onboard components, systems or family members will greatly improve maintenance, operations and service restoration not to mention crew morale. Current operational systems and standards, like the Internet Protocol, will not able to provide the level of service required end to end from an end point on the Martian surface like a scientific instrument to a researcher at a university. Ground operations whether earth, lunar or Martian and in flight operations to the moon and especially to Mars will require significant autonomy that will require access to highly reliable processing capabilities, data storage based on network storage technologies. Significant processing cycles will be needed onboard but could be borrowed from other locations either ground based or onboard other spacecraft. Reliability will be a key factor with onboard and distributed backup processing an absolutely necessary requirement. Current cluster processing/Grid technologies may provide the basis for providing these services. An overview of existing services, future services that will be required and the technologies and standards required to be developed will be presented. The purpose of this paper will be to initiate a technological roadmap, albeit at a high level, of current voice, video, data and network technologies and standards (which show promise for adaptation or evolution) to what technologies and standards need to be redefined, adjusted or areas where new ones require development. The roadmap should begin the differentiation between non manned and manned processes/services where applicable. The paper will be based in part on the activities of the CCSDS Monitor and Control working group which is beginning the process of standardization of the these processes. Another element of the paper will be based on an analysis of current technologies supporting space flight processes and services at JSC, MSFC, GSFC and to a lesser extent at KSC. Work being accomplished in areas such as Grid computing, data mining and network storage at ARC, IBM and the University of Alabama at Huntsville will be researched and analyzed.

Bradford, Robert N.↗

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

Constellation Program Mission Operations Project Office Status and Support Philosophy

The Constellation Program Mission Operations Project Office (CxP MOP) at Johnson Space Center in Houston Texas is preparing to support the CxP mission operations objectives for the CEV/Orion flights, the Lunar Lander, and and Lunar surface operations. Initially the CEV will provide access to the International Space Station, then progress to the Lunar missions. Initial CEV mission operations support will be conceptually similar to the Apollo missions, and we have set a challenge to support the CEV mission with 50% of the mission operations support currently required for Shuttle missions. Therefore, we are assessing more efficient way to organize the support and new technologies which will enhance our operations support. This paper will address the status of our preparation for these CxP missions, our philosophical approach to CxP operations support, and some of the technologies we are assessing to streamline our mission operations infrastructure.

Smith, Ernest↗

Preliminary Results of the Determination of Inlet-Pressure Distortion Effects on Compressor Stall and Altitude Operating Limits of the J57-P-1 Turbojet Engine

During an investigation of the J57-P-1 turbojet engine in the Lewis altitude wind tunnel, effects of inlet-flow distortion on engine stall characteristics and operating limits were determined. In addition to a uniform inlet-flow profile, the inlet-pressure distortions imposed included two radial, two circumferential, and one combined radial-circumferential profile. Data were obtained over a range of compressor speeds at an altitude of 50,000 and a flight Mach number of 0.8; in addition, the high- and low-speed engine operating limits were investigated up to the maximum operable altitude. The effect of changing the compressor bleed position on the stall and operating limits was determined for one of the inlet distortions. The circumferential distortions lowered the compressor stall pressure ratios; this resulted in less fuel-flow margin between steady-state operation and compressor stall. Consequently, the altitude operating Limits with circumferential distortions were reduced compared with the uniform inlet profile. Radial inlet-pressure distortions increased the pressure ratio required for compressor stall over that obtained with uniform inlet flow; this resulted in higher altitude operating limits. Likewise, the stall-limit fuel flows required with the radial inlet-pressure distortions were considerably higher than those obtained with the uniform inlet-pressure profile. A combined radial-circumferential inlet distortion had effects on the engine similar to the circumferential distortion. Bleeding air between the two compressors eliminated the low-speed stall limit and thus permitted higher altitude operation than was possible without compressor bleed.

Wallner, L. E.↗

Operational Considerations and Comparisons of the Saturn, Space Shuttle and Ares Launch Vehicles

The United States (U.S.) space exploration policy has directed the National Aeronautics and Space Administration (NASA) to retire the Space Shuttle and to replace it with a new generation of space transportation systems for crew and cargo travel to the International Space Station, the Moon, Mars, and beyond. As part of the Constellation Program, engineers at NASA's Marshall Space Flight Center in Huntsville, Alabama are working to design and build the Ares I, the first of two large launch vehicles to return humans to the Moon. A deliberate effort is being made to ensure a high level of operability in order to significantly increase safety and availability as well as reduce recurring costs of this new launch vehicle. It is the Ares Project's goal to instill operability as part of the requirements development, design and operations of the vehicle. This paper will identify important factors in launch vehicle design that affect the operability and availability of the system. Similarities and differences in operational constraints will also be compared between the Saturn V, Space Shuttle and current Ares I design. Finally, potential improvements in operations and operability for large launch vehicles will be addressed. From the examples presented, the paper will discuss potential improvements for operability for future launch vehicles.

Cruzen, Craig↗