Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Design Philosophy”

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 703 records · Page 39
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Testing for the J-2X Upper Stage Engine

NASA selected the J-2X Upper Stage Engine in 2006 to power the upper stages of the Ares I crew launch vehicle and the Ares V cargo launch vehicle. Based on the proven Saturn J-2 engine, this new engine will provide 294,000 pounds of thrust and a specific impulse of 448 seconds, making it the most efficient gas generator cycle engine in history. The engine's guiding philosophy emerged from the Exploration Systems Architecture Study (ESAS) in 2005. Goals established then called for vehicles and components based, where feasible, on proven hardware from the Space Shuttle, commercial, and other programs, to perform the mission and provide an order of magnitude greater safety. Since that time, the team has made unprecedented progress. Ahead of the other elements of the Constellation Program architecture, the team has progressed through System Requirements Review (SRR), System Design Review (SDR), Preliminary Design Review (PDR), and Critical Design Review (CDR). As of February 2010, more than 100,000 development engine parts have been ordered and more than 18,000 delivered. Approximately 1,300 of more than 1,600 engine drawings were released for manufacturing. A major factor in the J-2X development approach to this point is testing operations of heritage J-2 engine hardware and new J-2X components to understand heritage performance, validate computer modeling of development components, mitigate risk early in development, and inform design trades. This testing has been performed both by NASA and its J-2X prime contractor, Pratt & Whitney Rocketdyne (PWR). This body of work increases the likelihood of success as the team prepares for testing the J-2X powerpack and first development engine in calendar 2011. This paper will provide highlights of J-2X testing operations, engine test facilities, development hardware, and plans.

Buzzell, James C.↗
NASA NTRS2006

NASA's J-2X Engine Builds on the Apollo Program for Lunar Return Missions

In January 2006, NASA streamlined its U.S. Vision for Space Exploration hardware development approach for replacing the Space Shuttle after it is retired in 2010. The revised CLV upper stage will use the J-2X engine, a derivative of NASA s Apollo Program Saturn V s S-II and S-IVB main propulsion, which will also serve as the Earth Departure Stage (EDS) engine. This paper gives details of how the J- 2X engine effort mitigates risk by building on the Apollo Program and other lessons learned to deliver a human-rated engine that is on an aggressive development schedule, with first demonstration flight in 2010 and human test flights in 2012. It is well documented that propulsion is historically a high-risk area. NASA s risk reduction strategy for the J-2X engine design, development, test, and evaluation is to build upon heritage hardware and apply valuable experience gained from past development efforts. In addition, NASA and its industry partner, Rocketdyne, which originally built the J-2, have tapped into their extensive databases and are applying lessons conveyed firsthand by Apollo-era veterans of America s first round of Moon missions in the 1960s and 1970s. NASA s development approach for the J-2X engine includes early requirements definition and management; designing-in lessons learned from the 5-2 heritage programs; initiating long-lead procurement items before Preliminary Desi& Review; incorporating design features for anticipated EDS requirements; identifying facilities for sea-level and altitude testing; and starting ground support equipment and logistics planning at an early stage. Other risk reduction strategies include utilizing a proven gas generator cycle with recent development experience; utilizing existing turbomachinery ; applying current and recent main combustion chamber (Integrated Powerhead Demonstrator) and channel wall nozzle (COBRA) advances; and performing rigorous development, qualification, and certification testing of the engine system, with a philosophy of "test what you fly, and fly what you test". These and other active risk management strategies are in place to deliver the J-2X engine for LEO and lunar return missions as outlined in the U.S. Vision for Space Exploration.

Snoddy, Jimmy R.↗
NASA NTRS2006

Spitzer Pre Launch Mission Operations System - The Road to Launch

Spitzer Space Telescope was launched on 25 August 2003 into an Earth-trailing solar orbit to acquire infrared observations from space. Development of the Mission Operations System (MOS) portion prior to launch was very different from planetary missions from the stand point that the MOS teams and Ground Data System had to be ready to support all aspects of the mission at launch (i.e., no cruise period for finalizing the implementation). For Spitzer, all mission-critical events post launch happen in hours or days rather than months or years, as is traditional with deep space missions. At the end of 2000 the Project was dealt a major blow when the Mission Operations System (MOS) had an unsuccessful Critical Design Review (CDR). The project made major changes at the beginning of 2001 in an effort to get the MOS (and Project) back on track. The result for the Spitzer Space Telescope was a successful launch of the observatory followed by an extremely successful In Orbit Checkout (IOC) and operations phase. This paper describes how the project was able to recover the MOS to a successful Delta (CDR) by mid 2001, and what changes in philosophies, experiences, and lessons learned followed. It describes how projects must invest early or else invest heavily later in the development phase to achieve a successful operations phase.

observatory↗
NASA NTRS2000

Advanced Space Suit Insulation Feasibility Study

For planetary applications, the space suit insulation has unique requirements because it must perform in a dynamic mode to protect humans in the harsh dust, pressure and temperature environments. Since the presence of a gaseous planetary atmosphere adds significant thermal conductance to the suit insulation, the current multi-layer flexible insulation designed for vacuum applications is not suitable in reduced pressure planetary environments such as that of Mars. Therefore a feasibility study has been conducted at NASA to identify the most promising insulation concepts that can be developed to provide an acceptable suit insulation. Insulation concepts surveyed include foams, microspheres, microfibers, and vacuum jackets. The feasibility study includes a literature survey of potential concepts, an evaluation of test results for initial insulation concepts, and a development philosophy to be pursued as a result of the initial testing and conceptual surveys. The recommended focus is on microfibers due to the versatility of fiber structure configurations, the wide choice of fiber materials available, the maturity of the fiber processing industry, and past experience with fibers in insulation applications

Trevino, Luis A.↗
NASA NTRS2008

NASA's Ares I and Ares V Launch Vehicles--Effective Space Operations Through Efficient Ground Operations

The United States (U.S.) is charting a renewed course for lunar exploration, with the fielding of a new human-rated space transportation system to replace the venerable Space Shuttle, which will be retired after it completes its missions of building the International Space Station (ISS) and servicing the Hubble Space Telescope. Powering the future of space-based scientific exploration will be the Ares I Crew Launch Vehicle, which will transport the Orion Crew Exploration Vehicle to orbit where it will rendezvous with the Altair Lunar Lander, which will be delivered by the Ares V Cargo Launch Vehicle (fig. 1). This configuration will empower rekindled investigation of Earth's natural satellite in the not too distant future. This new exploration infrastructure, developed by the National Aeronautics and Space Administration (NASA), will allow astronauts to leave low-Earth orbit (LEO) for extended lunar missions and preparation for the first long-distance journeys to Mars. All space-based operations - to LEO and beyond - are controlled from Earth. NASA's philosophy is to deliver safe, reliable, and cost-effective architecture solutions to sustain this multi-billion-dollar program across several decades. Leveraging SO years of lessons learned, NASA is partnering with private industry and academia, while building on proven hardware experience. This paper outlines a few ways that the Engineering Directorate at NASA's Marshall Space Flight Center is working with the Constellation Program and its project offices to streamline ground operations concepts by designing for operability, which reduces lifecycle costs and promotes sustainable space exploration.

Singer, Christopher E.↗
NASA NTRS2014

Data Used in Quantified Reliability Models

Data is the crux to developing quantitative risk and reliability models, without the data there is no quantification. The means to find and identify reliability data or failure numbers to quantify fault tree models during conceptual and design phases is often the quagmire that precludes early decision makers consideration of potential risk drivers that will influence design. The analyst tasked with addressing a system or product reliability depends on the availability of data. But, where is does that data come from and what does it really apply to? Commercial industries, government agencies, and other international sources might have available data similar to what you are looking for. In general, internal and external technical reports and data based on similar and dissimilar equipment is often the first and only place checked. A common philosophy is "I have a number - that is good enough". But, is it? Have you ever considered the difference in reported data from various federal datasets and technical reports when compared to similar sources from national and/or international datasets? Just how well does your data compare? Understanding how the reported data was derived, and interpreting the information and details associated with the data is as important as the data itself.

DeMott, Diana↗
NASA NTRS1990

Software safety - A user's practical perspective

Software safety assurance philosophy and practices at the NASA Ames are discussed. It is shown that, to be safe, software must be error-free. Software developments on two digital flight control systems and two ground facility systems are examined, including the overall system and software organization and function, the software-safety issues, and their resolution. The effectiveness of safety assurance methods is discussed, including conventional life-cycle practices, verification and validation testing, software safety analysis, and formal design methods. It is concluded (1) that a practical software safety technology does not yet exist, (2) that it is unlikely that a set of general-purpose analytical techniques can be developed for proving that software is safe, and (3) that successful software safety-assurance practices will have to take into account the detailed design processes employed and show that the software will execute correctly under all possible conditions.

Dunn, William R.↗
NASA NTRS1995

Subminiaturization for ERAST instrumentation (Environmental Research Aircraft and Sensor Technology)

We are focusing on the Argus as an example to demonstrate our philosophy on miniaturization of airborne analytical instruments for the study of atmospheric chemistry. Argus is a two channel, tunable-diode laser absorption spectrometer developed at NASA for the measurement of nitrogen dioxide (N2O) (4.5 micrometers) and ammonia (CH3) (3.3 micrometers) at the 0.1 parts per billion (ppb) level from the Perseus aircraft platform at altitudes up to 30 km. Although Argus' mass is down to 23 kg from the 197 kg Atlas, its predecessor, our goal is to design a next-generation subminiaturized instrument weighing less than 1 kg, measuring a few cm(exp 3) and able to eliminate dewars for cooling. Current designs enable use to make a small,inexpensive, monolithic spectrometer without the required sensitivity range. Further work is on its way to increase sensitivity. We are continuing to zero-base the technical approach in terms of the specifications for the given instrument. We are establishing a check list of questions to hone into the best micromachining approach and to superpose on the answers insights in scaling laws and flexible engineering designs to enable more relaxed tolerances for the smallest of the components.

Madou, Marc↗
NASA NTRS1992

Distributed digital signal processors for multi-body flexible structures

Multi-body flexible structures, such as those currently under investigation in spacecraft design, are large scale (high-order) dimensional systems. Controlling and filtering such structures is a computationally complex problem. This is particularly important when many sensors and actuators are located along the structure and need to be processed in real time. This report summarizes research activity focused on solving the signal processing (that is, information processing) issues of multi-body structures. A distributed architecture is developed in which single loop processors are employed for local filtering and control. By implementing such a philosophy with an embedded controller configuration, a supervising controller may be used to process global data and make global decisions as the local devices are processing local information. A hardware testbed, a position controller system for a servo motor, is employed to illustrate the capabilities of the embedded controller structure. Several filtering and control structures which can be modeled as rational functions can be implemented on the system developed in this research effort. Thus the results of the study provide a support tool for many Control/Structure Interaction (CSI) NASA testbeds such as the Evolutionary model and the nine-bay truss structure.

Lee, Gordon K. F.↗
NASA NTRS1998

Human Mars Missions: Cost Driven Architecture Assessments

This report investigates various methods of reducing the cost in space transportation systems for human Mars missions. The reference mission for this task is a mission currently under study at NASA. called the Mars Design Reference Mission, characterized by In-Situ propellant production at Mars. This study mainly consists of comparative evaluations to the reference mission with a view to selecting strategies that would reduce the cost of the Mars program as a whole. One of the objectives is to understand the implications of certain Mars architectures, mission modes, vehicle configurations, and potentials for vehicle reusability. The evaluations start with year 2011-2014 conjunction missions which were characterized by their abort-to-the-surface mission abort philosophy. Variations within this mission architecture, as well as outside the set to other architectures (not predicated on an abort to surface philosophy) were evaluated. Specific emphasis has been placed on identifying and assessing overall mission risk. Impacts that Mars mission vehicles might place upon the Space Station, if it were to be used as an assembly or operations base, were also discussed. Because of the short duration of this study only on a few propulsion elements were addressed (nuclear thermal, cryogenic oxygen-hydrogen, cryogenic oxygen-methane, and aerocapture). Primary ground rules and assumptions were taken from NASA material used in Marshall Space Flight Center's own assessment done in 1997.

Interplanetary Mission↗
NASA NTRS1999

Product Structure, the Heart of Product Definition

This paper describes the LMMSS Product Definition System (PDS) philosophy and approach were the use of each item parts document or software can be traced to a specific end item (EI) serial/tail number of the product. It explains why a part-oriented approach to data organization and configuration management is required. The definition of part-oriented is that all appropriate product definition data products will be collected. Referenced and managed by their linkage/relationship to parts/items, The paper will touch upon how LMMSS store/controls product definition information under each project's top product designator in a two tiered approach. One tier for each product end item and another tier which contain/controls listings of drawings, documents. Specifications and standards that are required for hardware item definition.

DeHoog, C., Jr.↗
NASA NTRS1988

Expert system structures for fault detection in spaceborne power systems

This paper presents an architecture for an expert system structure suitable for use with power system fault detection algorithms. The system described is not for the purpose of reacting to faults which have occurred, but rather for the purpose of performing on-line diagnostics and parameter evaluation to determine potential or incipient fault conditions. The system is also designed to detect high impedance or arcing faults which cannot be detected by conventional protection devices. This system is part of an overall monitoring computer hierarchy which would provide a full evaluation of the status of the power system and react to both incipient and catastrophic faults. An approximate hardware structure is suggested and software requirements are discussed. Modifications to CLIPS software, to capitalize on features offered by expert systems, are presented. It is suggested that such a system would have significant advantages over existing protection philosophy.

Watson, Karan↗
NASA NTRS2005

Assemby, test, and launch operations for the Mars Exploration Rovers

In January of 2004, NASA's twin Mars rovers, Spirit and Opportunity, successfully landed on opposite sides of the Red Planet after a seven month Earth to Mars cruise period. Both vehicles have operated well beyond their 90 day primary mission design life requirements. The Assembly, Test, and Launch Operations (ATLO) program for these missions presented unique technical and schedule challenges to the team at the Jet Propulsion Laboratory (JPL). Among these challenges were a highly compressed schedule and late deliveries leading to extended double shift staffing, dual spacecraft operations requiring test program diversification and resource arbitration, multiple atypical test configurations for airbag/rocket landings and surface mobility testing, and verification of an exceptionally large number of separations, deployments, and mechanisms. This paper discusses the flight system test philosophies and approach, and presents lessons learned.

Assembly, Test, and Launch Operations (ATLO)↗
NASA NTRS2005

Investigation of the Utilization of Modern Industrial Methods, Processes, Ergonomics, and the Internet in the Scientific Environment

On Oct. 1, 2001 Cleveland State University and NASA Glenn Research Center embarked on the above named cooperative agreement. Because NASA's research facilities often exhibit instances where the failure to use state-of-the-art technologies and methods to improve on outmoded systems of interface and control, and this runs contrary to the NASA philosophy of "faster, better, and cheaper", it was deemed an ideal opportunity for this collaboration. The main objectives of the proposed effort were to research and investigate the use of the latest technologies, methods, techniques, etc. which pertain to control and interface with industrial and research systems and facilities. The work was done in large part at NASA Glenn Research Center, using selected research facilities as real-world laboratories; such as certain Microgravity Science Division and Space Station projects. Microgravity Science Division at Glenn Research Center designs and builds experiments to be flown on the Space Shuttle and eventually on the International Space Station. Economy of space, weight, complexity, data storage, ergonomics, and many other factors present problems that also exist in industry. Many of the solutions can come from the same areas of study mentioned above.

Myer, Spencer S., Jr.↗
NASA NTRS2013

Software Tools to Support the Assessment of System Health

This presentation provides an overview of three software tools that were developed by the NASA Glenn Research Center to support the assessment of system health: the Propulsion Diagnostic Method Evaluation Strategy (ProDIMES), the Systematic Sensor Selection Strategy (S4), and the Extended Testability Analysis (ETA) tool. Originally developed to support specific NASA projects in aeronautics and space, these software tools are currently available to U.S. citizens through the NASA Glenn Software Catalog. The ProDiMES software tool was developed to support a uniform comparison of propulsion gas path diagnostic methods. Methods published in the open literature are typically applied to dissimilar platforms with different levels of complexity. They often address different diagnostic problems and use inconsistent metrics for evaluating performance. As a result, it is difficult to perform a one ]to ]one comparison of the various diagnostic methods. ProDIMES solves this problem by serving as a theme problem to aid in propulsion gas path diagnostic technology development and evaluation. The overall goal is to provide a tool that will serve as an industry standard, and will truly facilitate the development and evaluation of significant Engine Health Management (EHM) capabilities. ProDiMES has been developed under a collaborative project of The Technical Cooperation Program (TTCP) based on feedback provided by individuals within the aircraft engine health management community. The S4 software tool provides a framework that supports the optimal selection of sensors for health management assessments. S4 is structured to accommodate user ]defined applications, diagnostic systems, search techniques, and system requirements/constraints. One or more sensor suites that maximize this performance while meeting other user ]defined system requirements that are presumed to exist. S4 provides a systematic approach for evaluating combinations of sensors to determine the set or sets of sensors that optimally meet the performance goals and the constraints. It identifies optimal sensor suite solutions by utilizing a merit (i.e., cost) function with one of several available optimization approaches. As part of its analysis, S4 can expose fault conditions that are difficult to diagnose due to an incomplete diagnostic philosophy and/or a lack of sensors. S4 was originally developed and applied to liquid rocket engines. It was subsequently used to study the optimized selection of sensors for a simulation ]based aircraft engine diagnostic system. The ETA Tool is a software ]based analysis tool that augments the testability analysis and reporting capabilities of a commercial ]off ]the ]shelf (COTS) package. An initial diagnostic assessment is performed by the COTS software using a user ]developed, qualitative, directed ]graph model of the system being analyzed. The ETA Tool accesses system design information captured within the model and the associated testability analysis output to create a series of six reports for various system engineering needs. These reports are highlighted in the presentation. The ETA Tool was developed by NASA to support the verification of fault management requirements early in the Launch Vehicle process. Due to their early development during the design process, the TEAMS ]based diagnostic model and the ETA Tool were able to positively influence the system design by highlighting gaps in failure detection, fault isolation, and failure recovery.

Melcher, Kevin J.↗
NASA NTRS2009

Philosophies Applied in the Selection of Space Suit Joint Range of Motion Requirements

Space suits are the most important tool for astronauts working in harsh space and planetary environments; suits keep crewmembers alive and allow them to perform exploration, construction, and scientific tasks on a routine basis over a period of several months. The efficiency with which the tasks are performed is largely dictated by the mobility features of the space suit. For previous space suit development programs, the mobility requirements were written as pure functional mobility requirements that did not separate joint ranges of motion from the joint torques. The Constellation Space Suit Element has the goal to make more quantitative mobility requirements that focused on the individual components of mobility to enable future suit designers to build and test systems more effectively. This paper details the test planning and selection process for the Constellation space suit pressure garment range of motion requirements.

Aitchison, Lindsway↗
NASA NTRS2017

Utilization of the International Space Station for Crew Autonomous Scheduling Test (CAST)

The United States space policy is evolving toward missions beyond low Earth orbit. In an effort to meet that policy, NASA has recognized Autonomous Mission Operations (AMO) as a valuable capability. Identified within AMO capabilities is the potential for autonomous planning and replanning during human spaceflight operations. That is allowing crew members to collectively or individually participate in the development of their own schedules. Currently, dedicated mission operations planners collaborate with international partners to create daily plans for astronauts aboard the International Space Station (ISS), taking into account mission requirements, ground rules, and various vehicle and payload constraints. In future deep space operations the crew will require more independence from ground support due to communication transmission delays. Furthermore, crew members who are provided with the capability to schedule their own activities are able to leverage direct experience operating in the space environment, and possibly maximize their efficiency. CAST (Crew Autonomous Scheduling Test) is an ISS investigation designed to analyze three important hypotheses about crew autonomous scheduling. First, given appropriate inputs, the crew is able to create and execute a plan in a reasonable period of time without impacts to mission success. Second, the proximity of the planner, in this case the crew, to the planned operations increases their operational efficiency. Third, crew members are more satisfied when given a role in plan development. This paper presents the results from a single astronaut test subject who participated in five CAST sessions. The details on the operational philosophy of CAST are discussed, including the approach to crew training, selection criteria for test days, and data collection methods. CAST is a technology demonstration payload sponsored by the ISS Research Science and Technology Office, and performed by experts in Mission Operations Planning from the Flight Operations Directorate at NASA Johnson Space Center, and researchers across multiple NASA centers. It is hoped the results of this investigation will guide NASA's implementation of autonomous mission operations for long duration human space missions to Mars and beyond.

Healy, Matthew↗
NASA NTRS1993

MIL-H-8501B: Application to shipboard terminal operations

The philosophy and structure of the proposed U.S. Military Specification for Handling Qualities Requirements for Military Rotorcraft, MIL-H-8501B, are presented with emphasis on shipboard terminal operations. The impact of current and future naval operational requirements on the selection of appropriate combinations of basic vehicle dynamics and usable cue environments are identified. An example 'walk through' of MIL-H-8501B is conducted from task identification to determination of stability and control requirements. For selected basic vehicle dynamics, criteria as a function of input/response magnitude are presented. Additionally, rotorcraft design development implications are discussed.

Cappetta, A. N.↗