Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Information Automation”

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 343 records · Page 19

Inspection and Verification of Domain Models with PlanWorks and Aver

When developing a domain model, it seems natural to bring the traditional informal tools of inspection and verification, debuggers and automated test suites, to bear upon the problems that will inevitably arise. Debuggers that allow inspection of registers and memory and stepwise execution have been a staple of software development of all sorts from the very beginning. Automated testing has repeatedly proven its considerable worth, to the extent that an entire design philosophy (Test Driven Development) has been developed around the writing of tests. Unfortunately, while not entirely without their uses, the limitations of these tools and the nature of the complexity of models and the underlying planning systems make the diagnosis of certain classes of problems and the verification of their solutions difficult or impossible. Debuggers provide a good local view of executing code, allowing a fine-grained look at algorithms and data. This view is, however, usually only at the level of the current scope in the implementation language, and the data-inspection capabilities of most debuggers usually consist of on-line print statements. More modem graphical debuggers offer a sort of tree view of data structures, but even this is too low-level and is often inappropriate for the kinds of structures created by planning systems. For instance, god or constraint networks are at best awkward when visualized as trees. Any any non-structural link between data structures, as through a lookup table, isn't captured at all. Further, while debuggers have powerful breakpointing facilities that are suitable for finding specific algorithmic errors, they have little use in the diagnosis of modeling errors.

Bedrax-Weiss, Tania↗

Onboard Autonomous Rock Shape Analysis for Mars Rovers

In the quest to maximize the scientific return of future robotic missions, it is imperative that our rovers be capable of determining the importance of the science they collect so that they may prioritize the acquisition and relay of that data. As an important step in this process, we present an automated technique to allow a rover to classify the shape and other geologic characteristics of rocks from two-dimensional photographic images and three-dimensional stereographically produced data. Experiments were conducted in the Matlab environment using images returned by JPL's Mars Pathfinder mission. Our method begins by first segmenting the rocks from the background using a combination of image intensity and height data. Various metrics are then used to classify the region's sphericity, roundness, and other geometric properties. Preliminary experiments to determine the most useful metrics were conducted by characterizing the two-dimensional rock shape while the three-dimensional shape was later studied with metrics derived from these two-dimensional techniques. Seven measures were developed and implemented. The performance of each measure was characterized by analyzing imagesfrom the Pathfinder mission and ranking the rocks according to the measured properties. Combined, the measures would provide a tool by which an automated rover could discover a greater amount of information about the data it collects, leading to a more productive mission.

image segmentation↗

Initial Design Guidelines for Onboard Automation of Flight Path Management

Achieving the National Academy of Science’s vision of advanced aerial mobility will depend on significant developments in automation to achieve safe and efficient operations. Flight path management (FPM), a major category of automation functionality needed to achieve this vision, will provide dynamic management of an aircraft’s flight path, ensuring that it remains feasible to fly to mission completion, deconflicted from hazards, coordinated with other traffic, flexible to accommodate future disturbances, and optimized to meet business objectives. While efforts are underway to advance FPM technology for the Urban Air Mobility application, initial design guidelines are presented for FPM automation capabilities to achieve each of these objectives based on 15+ years of prior FPM automation research and development. Methods to efficiently account for uncertainty in the prediction of trajectories are described, as are additional considerations for prioritizing safety in the design of FPM automation capabilities and interactions between aircraft. Recommendations are supported by extensive experience gained via previous work with the FPM reference automation system, Autonomous Operations Planner, developed by NASA. By employing capable FPM automation supported by cooperative operational flight rules and information sharing, future aircraft operators will benefit from an increased ability to plan and execute safe and efficient flights and to achieve mission success in a dynamic airspace.

Flight Path Management, FPM, AOP, UAM, deconflicti↗

Initial Design Guidelines for Onboard Automation of Flight Path Management

Achieving the National Academy of Science’s vision of advanced aerial mobility will depend on significant developments in automation to achieve safe and efficient operations. Flight path management (FPM), a major category of automation functionality needed to achieve this vision, will provide dynamic management of an aircraft’s flight path, ensuring that it remains feasible to fly to mission completion, deconflicted from hazards, coordinated with other traffic, flexible to accommodate future disturbances, and optimized to meet business objectives. While efforts are underway to advance FPM technology for the Urban Air Mobility application, initial design guidelines are presented for FPM automation capabilities to achieve each of these objectives based on 15+ years of prior FPM automation research and development. Methods to efficiently account for uncertainty in the prediction of trajectories are described, as are additional considerations for prioritizing safety in the design of FPM automation capabilities and interactions between aircraft. Recommendations are supported by extensive experience gained via previous work with the FPM reference automation system, Autonomous Operations Planner, developed by NASA. By employing capable FPM automation supported by cooperative operational flight rules and information sharing, future aircraft operators will benefit from an increased ability to plan and execute safe and efficient flights and to achieve mission success in a dynamic airspace.

Flight Path Management↗

Conjunction Assessment and Deconfliction Paradigm for Co-located Satellite Constellations with On-Spacecraft “Autonomous” Flight Dynamics Control

Constellations that employ highly-automated satellite flight dynamics can operate safely from a collision avoidance (CA) perspective using current CA screening technology and communication paradigms—except when in proximity to other highly-automated constellations: there is no existing arrangement and concept of operations to allow the low-latency CA screenings, exchange of information, and assignment/acceptance of mitigation responsibility that co-location of highly-automated constellations requires. However, the serendipitous co-location of the NASA Starling mission—an autonomously-controlled technology demonstration constellation—and the SpaceX Starlink constellation has presented an opportunity (indeed, a requirement) to develop and build out a solution for safe operations of two (or more) co-located, highly-automated satellite constellations. Such a solution has been designed and constructed, including the required ground node; and it will be exercised as a dedicated, in-flight safety experiment between the two constellations from January to September 2024. Lessons learned from this experiment are expected to feed the design of the US Department of Commerce’s Tracking Control System for Space (TraCSS) space traffic coordination solution.

conjunction assessment↗

Medical Data Architecture Project Capabilities and Design

Mission constraints will challenge the delivery of medical care on a long-term, deep space exploration mission. This type of mission will be restricted in the availability of medical knowledge, skills, procedures and resources to prevent, diagnose, and treat in-flight medical events. Challenges to providing medical care are anticipated, including resource and resupply constraints, delayed communications and no ability for medical evacuation. The Medical Data Architecture (MDA) project will enable medical care capability in this constrained environment. The first version of the system, called "Test Bed 1," includes capabilities for automated data collection, data storage and data retrieval to provide information to the Crew Medical Officer (CMO). Test Bed 1 seeks to establish a data architecture foundation and develop a scalable data management system through modular design and standardized interfaces. In addition, it will demonstrate to stakeholders the potential for an improved, automated, flow of data to and from the medical system over the current methods employed on the International Space Station (ISS). It integrates a set of external devices, software and processes, and a Subjective, Objective, Assessment, and Plan (SOAP) note commonly used by clinicians. Medical data like electrocardiogram plots, heart rate, skin temperature, respiration rate, medications taken, and more are collected from devices and stored in the Electronic Medical Records (EMR) system, and reported to crew and clinician. Devices integrated include the Astroskin biosensor vest and IMED CARDIAX electrocardiogram (ECG) device with INEED MD ECG Glove, and the NASA-developed Medical Dose Tracker application. The system is designed to be operated as a standalone system, and can be deployed in a variety of environments, from a laptop to a data center. The system is primarily composed of open-source software tools, and is designed to be modular, so new capabilities can be added. The software components and integration methods will be discussed.

Data architecture↗

Using WorldView-2 Imagery to Track Flooding in Thailand in a Multi-Asset Sensorweb

For the flooding seasons of 2011-2012 multiple space assets were used in a "sensorweb" to track major flooding in Thailand. Worldview-2 multispectral data was used in this effort and provided extremely high spatial resolution (2m / pixel) multispectral (8 bands at 0.45-1.05 micrometer spectra) data from which mostly automated workflows derived surface water extent and volumetric water information for use by a range of NGO and national authorities. We first describe how Worldview-2 and its data was integrated into the overall flood tracking sensorweb. We next describe the use of Support Vector Machine learning techniques that were used to derive surface water extent classifiers. Then we describe the fusion of surface water extent and digital elevation map (DEM) data to derive volumetric water calculations. Finally we discuss key future work such as speeding up the workflows and automating the data registration process (the only portion of the workflow requiring human input).

surface water extent↗

A knowledge-based system design/information tool

The objective of this effort was to develop a Knowledge Capture System (KCS) for the Integrated Test Facility (ITF) at the Dryden Flight Research Facility (DFRF). The DFRF is a NASA Ames Research Center (ARC) facility. This system was used to capture the design and implementation information for NASA's high angle-of-attack research vehicle (HARV), a modified F/A-18A. In particular, the KCS was used to capture specific characteristics of the design of the HARV fly-by-wire (FBW) flight control system (FCS). The KCS utilizes artificial intelligence (AI) knowledge-based system (KBS) technology. The KCS enables the user to capture the following characteristics of automated systems: the system design; the hardware (H/W) design and implementation; the software (S/W) design and implementation; and the utilities (electrical and hydraulic) design and implementation. A generic version of the KCS was developed which can be used to capture the design information for any automated system. The deliverable items for this project consist of the prototype generic KCS and an application, which captures selected design characteristics of the HARV FCS.

Allen, James G.↗

Shuttle Repair Tools Automate Vehicle Maintenance

Successfully building, flying, and maintaining the space shuttles was an immensely complex job that required a high level of detailed, precise engineering. After each shuttle landed, it entered a maintenance, repair, and overhaul (MRO) phase. Each system was thoroughly checked and tested, and worn or damaged parts replaced, before the shuttle was rolled out for its next mission. During the MRO period, workers needed to record exactly what needed replacing and why, as well as follow precise guidelines and procedures in making their repairs. That meant traceability, and with it lots of paperwork. In 2007, the number of reports generated during electrical system repairs was getting out of hand-placing among the top three systems in terms of paperwork volume. Repair specialists at Kennedy Space Center were unhappy spending so much time at a desk and so little time actually working on the shuttle. "Engineers weren't spending their time doing technical work," says Joseph Schuh, an electrical engineer at Kennedy. "Instead, they were busy with repetitive, time-consuming processes that, while important in their own right, provided a low return on time invested." The strain of such inefficiency was bad enough that slow electrical repairs jeopardized rollout on several occasions. Knowing there had to be a way to streamline operations, Kennedy asked Martin Belson, a project manager with 30 years experience as an aerospace contractor, to co-lead a team in developing software that would reduce the effort required to document shuttle repairs. The result was System Maintenance Automated Repair Tasks (SMART) software. SMART is a tool for aggregating and applying information on every aspect of repairs, from procedures and instructions to a vehicle s troubleshooting history. Drawing on that data, SMART largely automates the processes of generating repair instructions and post-repair paperwork. In the case of the space shuttle, this meant that SMART had 30 years worth of operations that it could apply to ongoing maintenance work. According to Schuh, "SMART standardized and streamlined many shuttle repair processes, saving time and money while increasing safety and the quality of repairs." Maintenance technicians and engineers now had a tool that kept them in the field, and because SMART is capable of continually evolving, each time an engineer put it to use, it would enrich the Agency-wide knowledge base. "If an engineer sees something in the work environment that they could improve, a repair process or a procedure, SMART can incorporate that data for use in future operations," says Belson.

Source record↗

Space flight manipulator technologies and requirements for the NASA Flight Telerobotic Servicer (FTS)

NASA Headquarters' Office of Advanced Concepts and Technology (OACT) joined efforts with Johnson Space Center's (JSC) Automation and Robotics Division and Langley Research Center's (LaRC) Information Systems Division to capture the technologies developed during the cancelled NASA Flight Telerobotic Servicer (FTS) program planned for use on Space Station Freedom. The recent FTS technology capture effort completed the build and testing of one flight qualifiable FTS manipulator, deliverable to JSC's Automation & Robotics Division for environmental testing. The many robotic technologies developed to meet the 30 year space environment design requirements are discussed in this paper. The manipulator properties were to allow positioning control to one thousandths of an inch, with zero actuator backlash over a temperature range of -50 to +95 C, and were to include impedance control and inertial decoupling. Safety and reliability requirements are discussed that were developed to allow a thirty year life in space with minimum maintenance. The system had to meet the safety requirements for hazardous payloads for operation in the shuttle payload bay during demonstration test flights prior to station use. A brief description is contained on an orbiter based robotic experiment and operational application using the dexterous FTS manipulator operating on the end of the shuttle remote manipulator systems (SRMS) from ground control.

Chladek, John T.↗

Management of Operations under Visual Flight Rules in UTM for Disaster Response Missions

The disaster response domain has experienced an increased focus in recent years due to the rise in number and scale of events, lessons learned from past experience, and emerging technologies that make possible a more coordinated and effective response. As part of this focus, JAXA and NASA have been collaborating on the integration of manned and unmanned aircraft in support of disaster response operations through integrated testing of their respective mission planning and optimization system (Disaster Relief Aircraft Information Sharing Network, or D-NET) and an automated UAS traffic management system (e.g., UTM). In 2018, JAXA and NASA jointly participated in a large-scale disaster drill in Japan where the integration of systems was successfully demonstrated through real-time data exchanges, visualization, and decision making as part of the coordinated airspace management of a manned helicopter in VFR conditions and unmanned small UAS operating in common areas. This work details a flight test consisting of two flights that were conducted December 2019 near the Chofu Aerodrome in Tokyo, which focused on the evaluation of pilots operating under Visual Flight Rules (VFR) communicating through D-NET and sharing intent and position information within UTM. This work contributes to defining the necessary requirements for digital coordination between manned and unmanned operations. UTM requires the use of operation volumes, which are spatial and temporal volumes that encompass UAS flight trajectories and account for technical performance errors and deviations due to disturbances (e.g., wind). A series of flights, representing different missions, used landmark-based operation volumes and conformance of the aircraft to those operation volumes were tracked within UTM. Experienced disaster response helicopter pilots provided insight on the development of the operation plans and their usability during disaster response operations. Results from the flight test supported the suggested benefits of using landmarks for planning and positional awareness and highlighted the need for future research in advanced visualization capabilities to support operations that consider both system constraints and flight deck/airspace management interaction.

disaster response↗

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗

Knowledge Discovery for Early Failure Assessment of Complex Engineered Systems Using Natural Language Processing

Emerging complex engineered systems may have unexpected safety issues due to novel operational environments, increasing autonomy, human-machine interaction, and other factors. To prevent failures in operation or testing that necessitate costly redesign, it is desirable to predict likely failure modes early in the design process. Information about past engineering failures in natural language format presents one possible solution by enabling the retrieval of information that can inform new designs. However, identifying documents containing usable information and extracting the required information can be prohibitively time-consuming when implemented at scale. In this research, an automated natural language processing (NLP) framework is proposed to discover relevant knowledge from documents containing failure-related design information. The framework is applied to NASA’s Lessons Learned Information System (LLIS),which is publicly available. Documents containing usable information are filtered using two different NLP-based models. Next, from the identified usable documents, a failure taxonomy is extracted using a partitioned hierarchical topic modeling approach. Partitions of the document describe different sections of the failure taxonomy – i.e., failure, cause of failure, and recommendations – as indicated by the structure of the original document. The extracted failure taxonomy can be leveraged in early design failure assessment methods. Moreover, the framework can be used to identify documents containing usable failure-related design information from other databases and extract relevant information from these documents.

Documentation and Information Science↗

Numerical analysis of stiffened shells of revolution. Volume 4: Engineer's program manual for STARS-2S shell theory automated for rotational structures - 2 (statics) digital computer program

The engineering programming information for the digital computer program for analyzing shell structures is presented. The program is designed to permit small changes such as altering the geometry or a table size to fit the specific requirements. Each major subroutine is discussed and the following subjects are included: (1) subroutine description, (2) pertinent engineering symbols and the FORTRAN coded counterparts, (3) subroutine flow chart, and (4) subroutine FORTRAN listing.

Svalbonas, V.↗

National Aeronautics and Space Administration Manned Spacecraft Center data base requirements study

A study was conducted to evaluate the types of data that the Manned Spacecraft Center (MSC) should automate in order to make available essential management and technical information to support MSC's various functions and missions. In addition, the software and hardware capabilities to best handle the storage and retrieval of this data were analyzed. Based on the results of this study, recommendations are presented for a unified data base that provides a cost effective solution to MSC's data automation requirements. The recommendations are projected through a time frame that includes the earth orbit space station.

Source record↗

Astronaut Photography of the Earth: A Long-Term Dataset for Earth Systems Research, Applications, and Education

The NASA Earth observations dataset obtained by humans in orbit using handheld film and digital cameras is freely accessible to the global community through the online searchable database at https://eol.jsc.nasa.gov, and offers a useful compliment to traditional ground-commanded sensor data. The dataset includes imagery from the NASA Mercury (1961) through present-day International Space Station (ISS) programs, and currently totals over 2.6 million individual frames. Geographic coverage of the dataset includes land and oceans areas between approximately 52 degrees North and South latitudes, but is spatially and temporally discontinuous. The photographic dataset includes some significant impediments for immediate research, applied, and educational use: commercial RGB films and camera systems with overlapping bandpasses; use of different focal length lenses, unconstrained look angles, and variable spacecraft altitudes; and no native geolocation information. Such factors led to this dataset being underutilized by the community but recent advances in automated and semi-automated image geolocation, image feature classification, and web-based services are adding new value to the astronaut-acquired imagery. A coupled ground software and on-orbit hardware system for the ISS is in development for planned deployment in mid-2017; this system will capture camera pose information for each astronaut photograph to allow automated, full georegistration of the data. The ground system component of the system is currently in use to fully georeference imagery collected in response to International Disaster Charter activations, and the auto-registration procedures are being applied to the extensive historical database of imagery to add value for research and educational purposes. In parallel, machine learning techniques are being applied to automate feature identification and classification throughout the dataset, in order to build descriptive metadata that will improve search capabilities. It is expected that these value additions will increase interest and use of the dataset by the global community.

Stefanov, William L.↗

Application of Design of Experiments and Surrogate Modeling within the NASA Advanced Concepts Office, Earth-to-Orbit Design Process

Decisions made during early conceptual design have a large impact upon the expected life-cycle cost (LCC) of a new program. It is widely accepted that up to 80% of such cost is committed during these early design phases.1 Therefore, to help minimize LCC, decisions made during conceptual design must be based upon as much information as possible. To aid in the decision making for new launch vehicle programs, the Advanced Concepts Office (ACO) at NASA Marshall Space Flight Center (MSFC) provides rapid turnaround pre-phase A and phase A concept definition studies. The ACO team utilizes a proven set of tools to provide customers with a full vehicle mass breakdown to tertiary subsystems, preliminary structural sizing based upon worst-case flight loads, and trajectory optimization to quantify integrated vehicle performance for a given mission.2 Although the team provides rapid turnaround for single vehicle concepts, the scope of the trade space can be limited due to analyst availability and the manpower requirements for manual execution of the analysis tools. In order to enable exploration of a broader design space, the ACO team has implemented an Advanced Design Methods (ADM) based approach. This approach applies the concepts of Design of Experiments (DOE) and surrogate modeling to more exhaustively explore the trade space and provide the customer with additional design information to inform decision making. This paper will first discuss the automation of the ACO tool set, which represents a majority of the development e ort. In order to t a surrogate model within tolerable error bounds a number of DOE cases are needed. This number will scale with the number of variable parameters desired and the complexity of the system's response to those variables. For all but the smallest design spaces, the number of cases required cannot be produced within an acceptable timeframe using a manual process. Therefore, automation of the tools was a key enabler for the successful application of an ADM approach to an ACO design study. Following the overview of the tool set automation, an example problem will be given to illustrate the implementation of the ADM approach. The example problem will first cover the inclusion of Ground Rules and Assumptions (GR&A) for a study. The GR&A are very important to the study as they determine the constraints within which a trade study can be conducted. These trades must ultimately reconcile with the customer's desired output and any anticipated \what if" questions. The example problem will then illustrate the setup and execution of a DOE through the automated ACO tools. This process is accomplished more efficiently in this work by splitting the tools into two separate environments. The first environment encompasses the structural optimization and mass estimation tools, while the second is focused on trajectory optimization. Surrogate models are t to the outputs of each environment and are integrated via connection of the surrogate equations. Throughout this process, checks are implemented to compare the output of the surrogates to the output of manually run cases to ensure that the error of the final surrogates is at an acceptable level. The conclusion of the example problem demonstrates the utility of the ADM based approach. Using surrogate models gives the ACO team the ability to visualize vehicle sensitivities to various design parameters and identify regions of interest within the design space. The ADM approach can thus be used to inform concept down selection and isolate promising vehicle configurations to be explored in more detail through the manual design process. In addition it provides the customer with an almost instantaneous turnaround on any \what if" questions that may arise within the bounds of the surrogate model. This approach ultimately expands the ability of the ACO team to provide its customer with broad and rapid turnaround trade studies for launch vehicle conceptual design. The ability to identify a selection of designs which can meet the customer requirements will have the potential to lower LCC of launch vehicle designs originating from ACO.

Zwack, Mathew R.↗

Application of Design of Experiments and Surrogate Modeling within the NASA Advanced Concepts Office, Earth-to-Orbit Design Process

Decisions made during early conceptual design have a large impact upon the expected life-cycle cost (LCC) of a new program. It is widely accepted that up to 80% of such cost is committed during these early design phases. Therefore, to help minimize LCC, decisions made during conceptual design must be based upon as much information as possible. To aid in the decision making for new launch vehicle programs, the Advanced Concepts Office (ACO) at NASA Marshall Space Flight Center (MSFC) provides rapid turnaround pre-phase A and phase A concept definition studies. The ACO team utilizes a proven set of tools to provide customers with a full vehicle mass breakdown to tertiary subsystems, preliminary structural sizing based upon worst-case flight loads, and trajectory optimization to quantify integrated vehicle performance for a given mission. Although the team provides rapid turnaround for single vehicle concepts, the scope of the trade space can be limited due to analyst availability and the manpower requirements for manual execution of the analysis tools. In order to enable exploration of a broader design space, the ACO team has implemented an advanced design methods (ADM) based approach. This approach applies the concepts of design of experiments (DOE) and surrogate modeling to more exhaustively explore the trade space and provide the customer with additional design information to inform decision making. This paper will first discuss the automation of the ACO tool set, which represents a majority of the development effort. In order to fit a surrogate model within tolerable error bounds a number of DOE cases are needed. This number will scale with the number of variable parameters desired and the complexity of the system's response to those variables. For all but the smallest design spaces, the number of cases required cannot be produced within an acceptable timeframe using a manual process. Therefore, automation of the tools was a key enabler for the successful application of an ADM approach to an ACO design study. Following the overview of the tool set automation, an example problem will be given to illustrate the implementation of the ADM approach. The example problem will first cover the inclusion of ground rules and assumptions (GR&A) for a study. The GR&A are very important to the study as they determine the constraints within which a trade study can be conducted. These trades must ultimately reconcile with the customer's desired output and any anticipated "what if" questions. The example problem will then illustrate the setup and execution of a DOE through the automated ACO tools. This process is accomplished more efficiently in this work by splitting the tools into two separate environments. The first environment encompasses the structural optimization and mass estimation tools, while the second is focused on trajectory optimization. Surrogate models are fit to the outputs of each environment and are "integrated" via connection of the surrogate equations. Throughout this process, checks are implemented to compare the output of the surrogates to the output of manually run cases to ensure that the error of the final surrogates is at an acceptable level. The conclusion of the example problem demonstrates the utility of the ADM based approach. Using surrogate models gives the ACO team the ability to visualize vehicle sensitivities to various design parameters and identify regions of interest within the design space. The ADM approach can thus be used to inform concept down selection and isolate promising vehicle configurations to be explored in more detail through the manual design process. In addition it provides the customer with an almost instantaneous turnaround on any ''what if" questions that may arise within the bounds of the surrogate model. This approach ultimately expands the ability of the ACO team to provide its customer with broad and rapid turnaround trade studies for launch vehicle conceptual design. The ability to identify a selection of designs which can meet the customer requirements will help ensure lower LCC of launch vehicle designs originating from ACO.

Zwack, Mathew R.↗