SEARCH · Engineering Papers

Results for “Design decisions”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRS1998

Multidisciplinary Design Technology Development: A Comparative Investigation of Integrated Aerospace Vehicle Design Tools

This research effort is a joint program between the Departments of Aerospace and Mechanical Engineering and the Computer Science and Engineering Department at the University of Notre Dame. Three Principal Investigators; Drs. Renaud, Brockman and Batill directed this effort. During the four and a half year grant period, six Aerospace and Mechanical Engineering Ph.D. students and one Masters student received full or partial support, while four Computer Science and Engineering Ph.D. students and one Masters student were supported. During each of the summers up to four undergraduate students were involved in related research activities. The purpose of the project was to develop a framework and systematic methodology to facilitate the application of Multidisciplinary Design Optimization (N4DO) to a diverse class of system design problems. For all practical aerospace systems, the design of a systems is a complex sequence of events which integrates the activities of a variety of discipline "experts" and their associated "tools". The development, archiving and exchange of information between these individual experts is central to the design task and it is this information which provides the basis for these experts to make coordinated design decisions (i.e., compromises and trade-offs) - resulting in the final product design. Grant efforts focused on developing and evaluating frameworks for effective design coordination within a MDO environment. Central to these research efforts was the concept that the individual discipline "expert", using the most appropriate "tools" available and the most complete description of the system should be empowered to have the greatest impact on the design decisions and final design. This means that the overall process must be highly interactive and efficiently conducted if the resulting design is to be developed in a manner consistent with cost and time requirements. The methods developed as part of this research effort include; extensions to a sensitivity based Concurrent Subspace Optimization (CSSO) MDO algorithm; the development of a neural network response surface based CSSO-MDO algorithm; and the integration of distributed computing and process scheduling into the MDO environment. This report overviews research efforts in each of these focus. A complete bibliography of research produced with support of this grant is attached.

Renaud, John E.↗

NASA NTRS1992

Domain specific software design for decision aiding

McDonnell Aircraft Company (MCAIR) is involved in many large multi-discipline design and development efforts of tactical aircraft. These involve a number of design disciplines that must be coordinated to produce an integrated design and a successful product. Our interpretation of a domain specific software design (DSSD) is that of a representation or framework that is specialized to support a limited problem domain. A DSSD is an abstract software design that is shaped by the problem characteristics. This parallels the theme of object-oriented analysis and design of letting the problem model directly drive the design. The DSSD concept extends the notion of software reusability to include representations or frameworks. It supports the entire software life cycle and specifically leads to improved prototyping capability, supports system integration, and promotes reuse of software designs and supporting frameworks. The example presented in this paper is the task network architecture or design which was developed for the MCAIR Pilot's Associate program. The task network concept supported both module development and system integration within the domain of operator decision aiding. It is presented as an instance where a software design exhibited many of the attributes associated with DSSD concept.

Keller, Kirby↗

NASA NTRS2001

Outline Of A Twenty-Five Year Plan For Development And Deployment Of a Catapult For a Third Generation Space Shuttle

This report reviews the rationale for catapult assist in the launching of a third generation space shuttle. It then furnishes lists of early design decisions, questions whose answers are prerequisite to later design decisions, preliminary inventories of carriage levitation and carriage propulsion concepts, phases of the project and major milestones, and some sources of expertise to support the project.

Russell, John M.↗

NASA NTRS2002

Outline of a Twenty-Five Year Plan for Development and Deployment of A Catapult for A Third Generation Space Shuttle

This report reviews the rationale for catapult assist in the launching a third generation space shuttle. It then furnishes lists of early design decisions, questions whose answers are prerequisite to later design decisions, preliminary inventories of carriage levitation and carriage propulsion concepts, phases of the project and major milestones, and some sources of expertise to support the project.

Russell, John M.↗

NASA NTRS1991

Decomposing Systems Into Subsystems For Design

Interactions among systems displayed in concise format. DeMAID (Design Manager's Aide for Intelligent Decomposition) is knowledge based software system for automating sequencing of subprocesses in design process and identifying possible multilevel structure for synthesis problem. Reorders and groups modules of equipment being designed on basis of links among modules, helping design manager make design decisions early in design cycle. Written in FORTRAN 77.

Rogers, James L., Jr.↗

NASA NTRS2005

Exploration-Related Research on ISS: Connecting Science Results to Future Missions

In January, 2004, the U.S. President announced The Vision for Space Exploration, and charged the National Aeronautics and Space Administration (NASA) with using the International Space Station (ISS) for research and technology targeted at supporting U.S. space exploration goals. This paper describes: What we have learned from the first four years of research on ISS relative to the exploration mission; The on-going research being conducted in this regard; and Our current understanding of the major exploration mission risks that the ISS can be used to address. Specifically, we discuss research carried out on the ISS to determine the mechanisms by which human health is affected on long-duration missions, and to develop countermeasures to protect humans from the space environment. These bioastronautics experiments are key enablers of future long duration human exploration missions. We also discuss how targeted technological developments can enable mission design trade studies. We discuss the relationship between the ultimate number of human test subjects available on the ISS to the quality and quantity of scientific insight that can be used to reduce health risks to future explorers. We discuss the results of NASA's efforts over the past year to realign the ISS research programs to support a product-driven portfolio that is directed towards reducing the major risks of exploration missions. The fundamental challenge to science on ISS is completing experiments that answer key questions in time to shape design decisions for future exploration. In this context, exploration relevant research must do more than be conceptually connected to design decisions - it must become a part of the mission design process.

Rhatigan, Jennifer L.↗

NASA NTRS2011

Development and Field Testing of the FootFall Planning System for the ATHLETE Robots

The FootFall Planning System is a ground-based planning and decision support system designed to facilitate the control of walking activities for the ATHLETE (All-Terrain Hex-Limbed Extra-Terrestrial Explorer) family of robots. ATHLETE was developed at NASA's Jet Propulsion Laboratory (JPL) and is a large six-legged robot designed to serve multiple roles during manned and unmanned missions to the Moon; its roles include transportation, construction and exploration. Over the four years from 2006 through 2010 the FootFall Planning System was developed and adapted to two generations of the ATHLETE robots and tested at two analog field sites (the Human Robotic Systems Project's Integrated Field Test at Moses Lake, Washington, June 2008, and the Desert Research and Technology Studies (D-RATS), held at Black Point Lava Flow in Arizona, September 2010). Having 42 degrees of kinematic freedom, standing to a maximum height of just over 4 meters, and having a payload capacity of 450 kg in Earth gravity, the current version of the ATHLETE robot is a uniquely complex system. A central challenge to this work was the compliance of the high-DOF (Degree Of Freedom) robot, especially the compliance of the wheels, which affected many aspects of statically-stable walking. This paper will review the history of the development of the FootFall system, sharing design decisions, field test experiences, and the lessons learned concerning compliance and self-awareness.

SunSpiral, Vytas↗

NASA NTRS1997

Collaborative, Sequential and Isolated Decisions in Design

The Massachusetts Institute of Technology (MIT) Commission on Industrial Productivity, in their report Made in America, found that six recurring weaknesses were hampering American manufacturing industries. The two weaknesses most relevant to product development were 1) technological weakness in development and production, and 2) failures in cooperation. The remedies to these weaknesses are considered the essential twin pillars of CE: 1) improved development process, and 2) closer cooperation. In the MIT report, it is recognized that total cooperation among teams in a CE environment is rare in American industry, while the majority of the design research in mathematically modeling CE has assumed total cooperation. In this paper, we present mathematical constructs, based on game theoretic principles, to model degrees of collaboration characterized by approximate cooperation, sequential decision making and isolation. The design of a pressure vessel and a passenger aircraft are included as illustrative examples.

Lewis, Kemper↗

NASA NTRS2004

Towards a systems approach to risk considerations for concurrent design

This paper describes the new process used by the Project Design Center at NASA's Jet Propulsion Laboratory for the identification, assessment and communication of risk elements throughout the lifecycle of a mission design. This process includes a software tool, 'RAP' that collects and communicates risk information between the various designers and a 'risk expert' who mediates this process. The establishment of this process is an attempt towards the systematic consideration of risk in the design decision making process. Using this process, we are able to better keep track of the risks associated with the design decisions. Furthermore, it helps us develop better risk profiles for the studies under consideration. We aim to refine and expand the current process to enable more thorough risk analysis capabilities in the future.

concurrent design↗

NASA NTRS2007

Integrating Human Factors into Crew Exploration Vehicle Design

With NASA's new Vision for Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, and an iterative prototype/test/redesign process. Addressing human-system interface issues early on can be very cost effective even cost reducing when performed early in the design and development cycle. To achieve this goal within Crew Exploration Vehicle (CEV) Project Office, human engineering (HE) team is formed. Key tasks are to apply HE requirements and guidelines to hardware/software, and provide HE design, analysis and evaluation of crew interfaces. Initial activities included many practice-orientated evaluations using low-fidelity CEV mock-ups. What follows is a description of such evaluations that focused on a HE requirement regarding Net Habitable Volume (NHV). NHV is defined as the total remaining pressurized volume available to on-orbit crew after accounting for the loss of volume due to deployed hardware and structural inefficiencies which decrease functional volume. The goal of the NHV evaluations was to develop requirements providing sufficient CEV NHV for crewmembers to live and perform tasks in support of mission goals. Efforts included development of a standard NHV calculation method using computer models and physical mockups, and crew/ stakeholder evaluations. Nine stakeholders and ten crewmembers participated in the unsuited evaluations. Six crewmembers also participated in a suited evaluation. The mock-up was outfitted with volumetric representation of sub-systems such as seats, and stowage bags. Thirteen scenarios were developed to represent mission/crew tasks and considered to be primary volume drivers (e.g., suit donning) for the CEV. Unsuited evaluations included a structured walkthrough of these tasks. Suited evaluations included timed donning of the existing launch and entry suit to simulate a contingency scenario followed by doffing/ stowing of the suits. All mockup evaluations were videotaped. Structured questionnaires were used to document user interface issues and volume impacts of layout configuration. Computer model and physical measures of the NHV agreed within 1 percent. This included measurement of the gross habitable volume, subtraction of intrusive volumes, and other non-habitable spaces. Calculation method developed was validated as a standard means of measuring NHV, and was recommended as a verification method for the NHV requirements. Evaluations confirmed that there was adequate volume for unsuited scenarios and suit donning/ doffing activity. Seats, suit design stowage and waste hygiene system noted to be critical volume drivers. The low-fidelity mock-up evaluations along with human modeling analysis generated discussions that will lead to high-level systems requirements and human-centered design decisions. This approach allowed HE requirements and operational concepts to evolve in parallel with engineering system concepts and design requirements. As the CEV design matures, these evaluations will continue and help with design decisions, and assessment, verification and validation of HE requirements.

Whitmore, Mihriban↗

NASA NTRS2004

Automation of Design Engineering Processes

A method, and a computer program that helps to implement the method, have been developed to automate and systematize the retention and retrieval of all the written records generated during the process of designing a complex engineering system. It cannot be emphasized strongly enough that all the written records as used here is meant to be taken literally: it signifies not only final drawings and final engineering calculations but also such ancillary documents as minutes of meetings, memoranda, requests for design changes, approval and review documents, and reports of tests. One important purpose served by the method is to make the records readily available to all involved users via their computer workstations from one computer archive while eliminating the need for voluminous paper files stored in different places. Another important purpose served by the method is to facilitate the work of engineers who are charged with sustaining the system and were not involved in the original design decisions. The method helps the sustaining engineers to retrieve information that enables them to retrace the reasoning that led to the original design decisions, thereby helping them to understand the system better and to make informed engineering choices pertaining to maintenance and/or modifications of the system. The software used to implement the method is written in Microsoft Access. All of the documents pertaining to the design of a given system are stored in one relational database in such a manner that they can be related to each other via a single tracking number.

Torrey, Glenn↗

NASA NTRS1992

Compatibility and consistency in display-control systems - Implications for aircraft decision aid design

In this study we contrast display-control movement relations defined in terms of stimulus-response (physical) compatibility with those defined by stimulus-cognitive compatibility, and we relate these findings to the issue of command versus status levels of decision aid support. A second issue addressed is the cost of inconsistency across multiple display-control mappings. Subjects performed a flight control task while responding to one to four analog indicators, formatted as either command or status displays. The results suggest that there is an advantage for the status format when subjects are required to verbally report the state of the indicator(s), but no advantage was found for either format when subjects were required to manually correct the indicated state. The data point to the importance of display-control consistency and suggest that it may even outweigh that of compatibility.

Andre, Anthony D.↗

NASA NTRSDate not supplied

Playing with DIRT: Building the Framework for a Comprehensive In-Situ Soil Materials Testing Database

Long-term, sustainable planetary exploration will require the ability to "live off the land," relying on In-Situ Resource Utilization (ISRU) and In-Situ Construction as core capabilities. Reduction of both risk and launch mass for lunar construction will require evaluating and comparing regolith materials for use as feedstocks suitable for in-situ beneficiation and fabrication of building components. These material assessment capabilities will inform lunar infrastructure design decisions, with co-benefits for terrestrial construction using in-situ materials. Current planetary construction technology development relies on lunar mapping and orbital data, Apollo-era sample analyses, current simulant inventories, and tests conducted using analog site soils. Requirements for lunar infrastructure design decisions and construction systems will be determined based on specific environmental conditions, mission architectures, and the materials available within traverse range of lunar feedstock processing depots. Critical for success is the capability to identify, evaluate and make effective use of a wide range of materials as they are found in-situ on the lunar surface. This paper discusses the development of a digital repository for data on soil and regolith properties, beginning with their structural performance in both cementitious and non-cementitious building material formulations. The Database for In-situ Resource Testing (DIRT) compiles a catalog of raw materials, additives, and formulations, with notations pertaining to material sources and preparation techniques entered via a web-based user interface. Design of consistent data schemas for site-sourced materials evaluation will facilitate linkage with relevant terrestrial and planetary materials databases while enabling guided data input via templates for participation by broader groups of collaborators. Results of these analyses are compiled in a centralized repository to generate insights applicable for regolith resources and landing sites yet to be precisely defined. Collection of thorough records of material characteristics, applications and performance will support innovative construction solutions not only for space infrastructure but for sustainable, resilient design in the terrestrial built environment.

Sarah Joey Seitz↗

NASA NTRSDate not supplied

Secondary Side Considerations for the BOLT Flight Experiment

The Boundary Layer Transition (BOLT) Flight Experiment is preparing for launch in the Spring of 2020. Final designs decisions have been made to allow fabrication of hardware. The secondary side experiment, which was initially proposed to be a roughness experiment, was selected instead to be an investigation of step effects to provide better synergy with the primary side. Numerous design decisions have influenced the decision to revise and refine the goal of the secondary side, which is now to investigate the effects of rearward-facing steps. The present paper focused on the BOLT secondary side flight experiment, providing details of the key inputs and decisions made to finalize the flight vehicle and instrumentation.

Scott A Berry↗

NASA NTRSDate not supplied

Quantification of Design Trade-Offs When Comparing Transonic Truss-Braced Wing to Advanced Tube and Wing Aircraft

Interest in novel aircraft configurations has continued to grow in response to increasing demand for improved fuel efficiency. One such configuration of interest is the Transonic Truss-Braced Wing (TTBW). Because the improvement of the TTBW comes from increased efficiency during cruise, it offers increasing returns as the mission distance increases. As a result, there is often a crossover point which represents the minimum mission range where the TTBW will offer a fuel burn reduction relative to a similar Tube and Wing aircraft with similar component technology levels. Aircraft rarely fly missions at their maximum range, so it is important to investigate not only the maximum benefit, but also the most likely benefit. Design decisions and analysis assumptions that significantly impact this crossover point include whether to put fuel in body tanks, how weight build-up estimation is calibrated, engine technology selection, and flight Mach number. This study, conducted under NASA’s Sustainable Flight Demonstration project and inspired by differing assumptions made by different research teams, details the impacts of changing these design decisions and assumptions.

Carl J Recine↗

NASA NTRSDate not supplied

Quantification of Design Trade-Offs When Comparing Transonic Truss-Braced Wing to Advanced Tube and Wing Aircraft

Carl J Recine↗

NASA NTRS2018

Operability Engineering for the Europa Clipper Mission: Formulation Phase Results and Lessons

Operability is an important factor in both success and cost of space missions, but is difficult to quantify, and can suffer if not considered as part of early formulation and design. The Europa Clipper mission has taken a deliberate approach to infusing operability into the concepts and designs since early in the formulation phase. This paper reports on that approach to operability and the results thus far, as the Europa Clipper mission approaches its Preliminary Design Review. Definitions for operability and its various aspects are presented along with a description of the engineering and organizational approach taken to infusing operability into designs. A number of examples of operability requirements are shown, and key examples of trade studies and design decisions are described, along with influence on outcomes motivated by operability considerations. We find that support from management, empowerment of a cross-discipline Operability Working Group, consistent tracking of operability aspects over time, and broad infusion and participation in operability considerations are all significant factors in implementing operability. In particular, thoughtful and deliberate consideration of operability criteria has led to design decisions that include proper consideration of concerns related to the mission operations phase, and seem likely to provide better science results and mission outcomes.

Huh, Shin M.↗

NASA NTRS2019

UAS Service Supplier Framework for Authentication and Authorization

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Service Supplier (USS) Framework for Authentication and Authorization (UFAA) is the basis for secure and confident data exchanges between the Flight Information Management System (FIMS) and the USS Network and within the USS Network itself. UFAA is built upon the OAuth 2.0 approach to federated authorization, with details supplied by various Internet Engineering Task Force (IETF) Request for Comment documents (RFCs). Whenever possible, a specific standard is used to support a design decision within UFAA, and when an applicable standard is not found/used, the technical decision is explained as much as possible. This document describes UFAA in detail. It is intended to serve as a reference for other key UTM documents and should be useful to many UTM stakeholders. This is an informative document. The requirements stated or implied in this document will need to be fully vetted and reviewed by appropriate stakeholders before becoming operational. It is highly encouraged that in any design decisions for future applicable standards that are counter to or missing from the decisions presented herein be justified in that future standard.

UTM↗