98,99 €
Multidisciplinary Design Optimization supported by Knowledge Based Engineering supports engineers confronting this daunting and new design paradigm. It describes methodology for conducting a system design in a systematic and rigorous manner that supports human creativity to optimize the design objective(s) subject to constraints and uncertainties. The material presented builds on decades of experience in Multidisciplinary Design Optimization (MDO) methods, progress in concurrent computing, and Knowledge Based Engineering (KBE) tools.
Key features:
Multidisciplinary Design Optimization supported by Knowledge Based Engineering is a one-stop-shop guide to the state-of-the-art tools in the MDO and KBE disciplines for systems design engineers and managers. Graduate or post-graduate students can use it to support their design courses, and researchers or developers of computer-aided design methods will find it useful as a wide-ranging reference.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 752
Veröffentlichungsjahr: 2015
Jaroslaw Sobieszczanski-Sobieski
NASA Langley Research Center, USA
Alan Morris
Cranfield University, UK
Michel J.L. van Tooren
University of South Carolina, USA
With contributions from
Gianfranco La Rocca
TU Delft, The Netherlands
Wen Yao
National University of Defense Technology, P.R. China
This edition first published 2015© 2015 John Wiley & Sons, Ltd.
Registered OfficeJohn Wiley & Sons, Ltd, The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom
For details of our global editorial offices, for customer services and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com.
The right of the author to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.
Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. The publisher is not associated with any product or vendor mentioned in this book.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. It is sold on the understanding that the publisher is not engaged in rendering professional services and neither the publisher nor the author shall be liable for damages arising herefrom. If professional advice or other expert assistance is required, the services of a competent professional should be sought
Library of Congress Cataloging-in-Publication Data
Sobieszczanski-Sobieski, Jaroslaw, author. Multidisciplinary design optimization supported by knowledge based engineering / JaroslawSobieszczanski-Sobieski, Alan Morris, Michel van Tooren. pages cm Includes bibliographical references and index.
ISBN 978-1-118-49212-3 (cloth)1. Engineering design. 2. Multidisciplinary design optimization. 3. Expert systems (Computer science) I. Morris, A. J., author. II. Tooren, M. J. L. van, author. III. Title. TA174.S697 2015 620′.0042–dc23
2015017649
A catalogue record for this book is available from the British Library.
The authors wish to dedicate this book:
On behalf of J. Sobieski to the memory of his wife Wanda and to his daughter Margaret Rietveld and son Ian Sobieski
On behalf of A. Morris to his wife Lilian,daughter Phiala Mehring, and sons Keric, Lucian and Damian
On behalf of M. van Tooren to his wife Tanja,his son Quinn, and his daughter Bibi
On behalf of W. Yao to her husband Jun and her son Yichen
On behalf of G. La Rocca to his parents,Marcella and Umberto, his brother Gianluca, and Alexandra
When Fillippo Brunelleschi designed the cupola of the Santa Maria del Fiore, Florence, in the fifteenth century, he worked alone. The great nineteenth-century engineers like Isambard Kingdom Brunel worked with small teams of assistants. In designing the Boeing 747, Joe Sutter started with a few hundred engineers in his team but finished with 4,500. In reality, the design team was much larger as there were design teams working on the engines that would power this aircraft. The number of individuals involved in the design process has grown with time reflecting the increase in complexity of the products and the design process itself. Designing a modern product is a process involving an intricate web of cross-connections between the parts of the product systems and their abstractions in the underlying mathematical modeling, reflected in the adage that “everything influences everything else.” An added complexity, today, is that any major design such as the Airbus 380 and a building like the London Shard are created by teams that are globally distributed.
Recognizing the need to develop tools to assist in this design task, the engineering community has invested an enormous effort in creating tools to support the design process. This had led to the development of a range of computational methods for analyzing the disciplines associated with a design, such as structures, aerodynamics, and thermal analysis. The requirement that a new design should represent an improvement on its predecessors requires a design engineer or design team being able to link these computational analysis and other design support tools with optimization methods to provide an effective method for seeking better designs. The task has been made more difficult by rapid technology changes that make reliance on historical data less useful compelling engineers to adopt an innovative approach to the design task that takes account of the interaction of the various physical phenomena and engineering disciplines involved. Two technologies have emerged to help cope with this situation: Multidisciplinary Design Methods (MDO) and Knowledge-Based Engineering (KBE) which are the topics described in this book.
MDO, which is the primary focus, has developed over the course of the last three decades originating from the optimization of structures, possibly, in combination with aerodynamics. In its present form, MDO draws together tools for optimizing a design with discipline-based tools involving high levels of interaction where disciplines and design requirements cannot be separated and handled individually. More recently, the complexity of the overall design task has led to the development of tools and methods to support a broader range of design activities than those coming within the scope of MDO. The main application to date, for this new set of tools and methods, is the capture, storage, and retrieval and manipulation of design data and the design process. The broad scope of KBE covers both the design process and the implementation of the computational design tools. It can play an important role in supporting the use of MDO methods by engineers who are not experts in their application.
Our primary objective is to present a coherent story that leads the reader through the basic concepts underpinning optimization methods that form the foundations of the MDO technology. This is covered in Chapters 2 through 6 and readers confident in their knowledge of optimization methods and theory may consider these chapters as forming an aid-memoire and refer to as required. The MDO core of the book is found in three chapters. Chapter 7 reviews sensitivity analysis methods that answers “what if” questions; Chapter 8 introduces a sample of MDO methods from the current state-of-the-art and Chapter 11 offers ways and means for reducing computational effort. Since no design can be successful without accounting for the variety of uncertainties involved, Chapter 10 addresses some typical tools and tools available that focus on the control of uncertainties.
Although these chapters constitute the main contents of the book, KBE has started to play an important role in the application of MDO methods, so we introduce this topic in Chapter 9 and Appendix A. The KBE material is presented in such a way that the reader can see how it can be deployed to assist in the process of assembling a set of tools that can find the optimal solution employing an MDO design approach. However, it goes beyond this limited scope to illustrate how, via KBE, wider design considerations can be incorporated into a computational design process. This allows the reader to gain an idea of how the scope of KBE is beginning to widen to manage the main activities in the design process of complex products within which MDO plays its key role.
The authors would like to acknowledge the assistance of Adrianna Beasley, McNair Center, for Aerospace Innovation and Research in the preparation of Chapter 8.
A consistent notation is used throughout the book to portray variables, vectors, matrices, and functions which is defined below, and variations arising in several chapters are defined within the specific chapter. The notation applies to both equations and text so they are consistent; thus, a term appearing in an equation in lowercase bold will also appear the same in the text. The following, therefore, applies:
Scalar and individual variables are identified by being written in lowercase italic as are functions of a single variable. A function of a single variable is written, for example, as
and the derivative of this term with respect to a single variable is written as:
Vectors use lowercase bold nonitalic and the individual components of a vector are written in lowercase italic, for example:
Lowercase bold is used for a function written in terms of a vector x defined by Equation (1.3); thus, a vector function representing an objective function with three independent components is written as:
Similarly constraints are written as bold lowercase with bold lowercase vectors inside brackets thus: g(x) ≤ 0, h(x) = 0, etc. This convention also applies when vector functions are functions of more than one vector; if the above objective function is a function of three vectors x, y, z, then it is written as f(x, y, z).
Square matrices, such as structural stiffness matrices, are uppercase bold nonitalic and thus
Components of matrices and vectors are lowercase italic as in Equations (1.3) and (1.5) above.
Non-square matrices are, essentially, a set of columns each of which are vectors and such matrices are represented as bold lowercase letters. The individual columns of these matrices are defined as vectors with suffices that identify the column occupied by a specific. If a multiload case is represented by
n
×
m
matrix
p
(implying there are
n
load cases operating at m nodes in an FE analysis), the individual load vectors are represented by
p
i
i
= 1…
n
; thus, for a set of
n
load cases, it is written
p
= {
p
1
p
2
p
3
…
p
n
}. The elements of a specific column in this matrix are given by:
Optimization formalizes the century’s old trial-and-error method which engineers have traditionally used to reason through the complexities of a design process where the merits and demerits of a large number of alternatives are evaluated and the best combination selected. Originally, this was done using hand-based calculation procedures but has evolved, in the modern design environment, into the application of sophisticated computer-based numerical algorithms. Whether done by hand calculation or by employing an advanced computer program, the underlying procedure is the same; the optimization process starts the search for a best solution from an initial guess and then iteratively seeks to find better alternatives. These alternative designs are generated by varying parameters that characterize the design problem. If the design is characterized by cost, these would be cost factors; if the design is to have minimum weight, structural parameters related to the volume of structural material would be used. These parameters are the design variables which are used as the defining terms in a design objective; for example, the cost of manufacture is defined in terms of economic cost factors; the total structural weight can be defined in terms of structural sizes. By the intelligent application of the trial-and-error process, a computer-based algorithm, or the engineer, evaluates the quality of the trial to decide on the next move. Employing a computer, the engineer can engage a numerical algorithmic process that brings the power of computational numerical methods into play which iteratively changes the values of the design variables to modify the numerical value(s) of the design objective(s) while adhering to the limitations on the design normally termed constraints. By proceeding in this manner, the algorithm is driving toward a design judged best for a given set of circumstances. While engineers naturally turn to computer methods to assist them in the design process, we should, nevertheless, not forget that the most innovative computer is the human brain and the best designs are always a result of the engineer thinking first and employing computers second.
In real world engineering where a large and complex system, for example, an aircraft, a ship, or a car, is being designed, a process involving trade-offs takes place both within disciplinary subsystem domains and across their boundaries. Optimization in this environment becomes multidisciplinary design optimization (MDO). The complexity of modern systems shows itself under a number of different headings: compositional, behavioral, modeling, and evaluative complexity. The compositional complexity relates to the high number of system elements in the design process and their connectivity; if we take into account manufacturing cost, structural mass, dynamic response, and so on, each of these interacts with each other and calls into play a wide range of associated software tools. The behavioral complexity comes from the many aspects that influence the behavior that the designer is looking for, or trying to avoid, and is well described by the adage that in a system “everything affects everything.” Modeling complexity is associated with the complex (physical) phenomena that need to be taken into account to analyze the system’s behavior such as major structural analysis programs, computational fluid dynamics software tools, and so on which also interact. Finally, evaluative complexity appears when conflicting design characteristics are aimed for and trade-offs are needed between disparate properties.
Many of the methods applied to design optimization originate from the world of operations research (OR) which aims at optimizing operations of existing systems while MDO extends the approach to the engineering system design process, explaining the D in MDO. However, as explained in Chapter 2, there is a long history to the development of optimization principles and methods that have migrated to the design environment from variety of mathematical sources. The totality of these inputs is made clear through the various chapters in this book.
MDO can be defined as an assemblage of methods, procedures, and algorithms for finding best designs measured against a set of specified criteria for complex engineering systems with interacting parts, whose behavior is governed by a number of coupled physical phenomena aligned with engineering disciplines. Such designs are brought to fruition by teams of engineers, often dispersed on a country or global scale, employing organization methods and processes that accommodate commercial realities which might involve human factors components, costs and profit considerations, market competitiveness, and so on. Within the design environment, uncertainties are always present, and handling them when employing optimizing methods is not always straightforward and currently a major research area. Coupled with the presence of uncertainties is the need to undertake reliability-based and robust (uncertainty tolerant) designs. It is in the resolution of this type of design problem, with its range of interactions and uncertainties, that MDO finds its application.
Knowledge-based engineering (KBE) aims at drawing together the knowledge required to construct an MDO system into a computer-based knowledge base which can be logically interrogated by an engineer. It supports those wishing to employ MDO methods by making knowledge directly available at each stage of the development and application of an MDO system—it cannot be expected that a designer is an expert in all aspects relating to this task. Currently, KBE tools are in a rapid state of development and as time passes will become directly linked with MDO in its successful support for generating optimized designs for complex products.
The aim of the book is to offer a basis for constructing a logical approach to the application and understanding of modern MDO methods and tools and provide a background to supporting MDO with KBE technology. This is an ambitious target, and it is not claimed the book gives a complete and totally comprehensive coverage of these major fields. Rather, it provides a door through which the reader is invited to step and after crossing the threshold absorb or possibly develop the ideas in these rapidly expanding areas. In essence, it provides a knowledge base that allows the reader to take advantage of this technology in engineering design. In the case of an inexperienced or new user of MDO/KBE technology, it represents a robust starting point. For an engineer experienced in the application of optimization tools for designing a product, we hope the book will give insight into a new set of optimization and optimization support tools for solving complex design problems.
In order to meet the book’s aim, we recognize the need to progress through the necessary background knowledge before launching into the complexities of the full MDO application. Before reaching the chapters devoted to multidisciplinary design, the book introduces and explains the basics of optimization and the method employed for single-discipline optimum design problems. Prior exposure to these basic optimization methods will assist the reader but is not a requirement as we start along the pathway to complex methods with a review of the necessary fundamentals. Readers familiar with the basics of optimization and optimization method may wish to pass by the earlier chapters. However, we all, from time to time, forget what we have previously learned, and in this situation, the early chapters can be viewed as a convenient aide-memoire that can be consulted when required. As regards prerequisite knowledge, we assume the reader is familiar with the vector and matrix calculus and the analysis methods commonly taught in undergraduate engineering courses.
Recent years have seen rapid development in computer technology leading to major increases in computer power and speed that have proved beneficial in general applications and for engineering design in particular. One development of particular importance in the field of MDO is massively concurrent data processing (MCDP) also popularly known as parallel computing. Therefore, throughout the book, we repeatedly point to the use of MCDP as an enabler for solving problems that, previously, were regarded as intractable.
Our objective is simple: to provide sufficient information for the reader to understand the basics of the MDO process rooted in the realities of engineering design practices and benefiting from the rapid advance in computer technology, to see how uncertainty can be incorporated, and to illustrate how KBE tools can give support to the implementation of an MDO design solution system.
It is probably worthwhile to discuss the fact that no optimization process exists to take us out of the box set by the definition of the design space implicit in the initialization and the underlying design concept. In this context, we may note that optimization is always reductionist. For example, an aircraft optimization starting with a biplane could evolve into a monoplane with a low, mid, or high wing; but a biplane will not arise from a configuration initialized as monoplane. This underscores the importance of the initial design concept and why the engineer will remain the designer for the foreseeable future and MDO will remain his subordinate.
Once an initial design configuration has been selected, the engineer has the major task of setting up the optimization system to be used in the search for an improved design. It is tempting to think that the application of MDO methods is simply a question of selecting a method from the set of MDO “recipes” found in Chapter 8 supported by appropriate KBE tools as introduced in Chapter 9. This temptation should be resisted as complex design problems do not readily submit to being fitted into a set of preconceived methods. The engineer has, therefore, to come forward with a solution method that reflects the idiosyncrasies of the design problem. In configuring an MDO system, the reader should take account of the fact that the methods presented in this book are the best available and most often used in current mainstream applications of MDO. Our readers should recall that MDO is a major research field and, as a result, there is no doubt new methods will be developed in the future.
Most technical books are not read as a novel where it is essential to start at the beginning and proceed sequentially to the final chapter; rather, the reader selects those parts relevant to the technical issues being addressed. To assist the reader in making a judgment as to where relevant information can be found, we now describe what can be found in the other chapters of this book.
To introduce the role played by MDO/KBE methods in a modern design environment where products are complex and created by distributed design teams.
This chapter looks forward to what is to come in the ensuing chapters; it introduces the modern design environment and discusses the position and role to be played by MDO in this environment. It discusses the underlying realities of the design process then moves on to examine the role that optimization can play in achieving improved design solutions. Initially, this is done by focusing on optimal designs involving a single discipline and then moves on to discuss the multidisciplinary case. It also indicates that a role can be played by KBE tools in implementing MDO systems.
To introduce the fundamental mathematical principles on which the methods for solving optimization problems are based.
At the heart of any MDO system are the algorithms that guide the design process to an optimizing point, but before looking at them, we need to discuss and elaborate some of the characteristics and properties of the space within which an optimizing point lies. This chapter covers this broad topic area and can be considered as a precursor to later chapters which discuss optimizing strategies. The material presented is not comprehensive but covers the basic principles and methods that are used to solve constrained optimization problems. This includes the mathematical principles that underpin the application of optimization methods to solve design problems.
The Kuhn–Tucker constrained optimization conditions are developed together with the concepts of duality and dual bounding. Lagrange multipliers are introduced and linked to the concept of active and passive constraints. Readers familiar with the foundations of nonlinear optimization and optimization theory may wish to move directly to latter chapters. However, the chapter does include information which an engineer experienced in optimization methods might consider using as an aide-memoire.
To describe the methods used in the solution of problems with a single-objective function.
The chapter supplies the reader with sufficient information to understand what the various mono-optimization methods and algorithms require in terms of gradients, update formulae, and so on. With this information, an engineer can make rational choices on the selection of appropriate optimization tools for use in a practical MDO design system. It does not attempt to provide a comprehensive set of methods covering the entire range of such software. The reader wanting to obtain a comprehensive description of the methods touched on should refer to the references found within the chapter. The chapter considers first unconstrained optimization problems with linear or nonlinear design objectives. It then moves on to review a range of constrained optimization solution methods. The concept of shadow prices is used to show how changes in the constraint limits can change the value of the optimized objective function. As with Chapter 3, an engineer experienced in employing optimization algorithms to solve engineering design problems may pass this chapter by but may want to employ it as a resource base.
To discuss the use of genetic algorithms and artificial neural nets in the solution of optimization problems.
There are a number of methods that attempt to find optimum designs using techniques that avoid following a specified search direction exploiting gradient or quasigradient information discussed in Chapter 4. The repetitious use of directional searches is replaced by a process which either exploits randomized variations in the design variables or avoids the direct variation of design variables altogether by using learning networks. The first group is called guided random search techniques, and this chapter uses genetic algorithms to represent this class of optimum seeking methods. The second group, introduced in the chapter, is learning-based methods which are trained to pick out optimal solutions to very complex problems. In covering this group, the chapter discusses network-based methods and specifically covers artificial neural networks. As with Chapter 4, it does not present the reader with a comprehensive treatment of these algorithms as there is extensive and comprehensive literature available. It gives the reader a sufficient understanding of how these work so that intelligent decisions can be made if these techniques are encountered in the development or use of an MDO system.
To describe the methods used in the solution of optimization problems with multiple-objective functions.
This chapter introduces the reader to methods that can be employed when a design has more than one objective function which is normal when real world design optimization problems are encountered. It indicates that the design engineer is confronted with a number of, possibly, conflicting design requirements that normally result in a need to undertake trade-off studies. The chapter covers Pareto-optimal solutions, the concept of the Pareto frontier, goal programming, weighted sum methods, and the application of the methods introduced in Chapter 5 to solve this type of complex design optimization problem.
To introduce the mathematical methods and procedures for generating sensitivities at both single and multiple levels for both complex and simple design problems.
At this stage, in the pathway to applying MDO methods in the solution of complex design problems involving several objective functions, sensitivity analysis emerges as a tool necessary for design in general and for optimization in particular. This chapter reviews the fundamentals of the sensitivity analysis based on analytic derivative methods, including the recently gaining attention method of computing the derivatives of the real-valued functions via complex numbers. It introduces a method for obtaining derivatives using adjoint methods as a means for reducing computational effort. Shadow prices, originally discussed in Chapter 4, are reintroduced in this chapter. The use of higher-order derivatives is considered, and the sensitivity of an optimum to the problem parameters is presented. A solution to the problem of the sensitivity of complex internally coupled systems is introduced.
To introduce and describe the methods that can be applied to the solution of problems where both the objective functions and the design constraints involve interacting disciplines or subsystems in the context of a large engineering optimization process conducted by a team that may be dispersed organizationally and geographically.
This chapter provides a detailed explanation of multidisciplinary design and optimization (MDO) and the methods for solving this class of optimization problems that represent the core topic of this book. It exploits the terminology, notation, and methods, introduced in the chapters preceding this chapter, augmenting them to support the discussion of MDO. The chapter describes how the large and difficult task of designing a complex engineering system can be decomposed into a set of smaller and simpler tasks that may be carried out concurrently by a geographically dispersed team with the aid of parallel computing technology and utilization of a formal data management. A review of a sample of methods applicable to engineering system optimization is then presented, contrasting the traditional sequential approaches that may be shown as leading to acceptable but suboptimal designs, with the MDO-based approach that has the potential for both reaching an optimum and reducing the cost and time of the design process. It is asserted that MDO supports “design agility” meaning an ability to quickly revise design decisions made early in the design process as required by new information obtained downstream. The chapter concludes with a summary of the key elements and features of MDO and assesses the current state of the art focusing on strength and weaknesses together with a forecast of future potential.
To describe the role played by KBE methods in supporting the application of MDO methods.
This chapter discusses the fundamentals of KBE and illustrates how this technology can support and enable multidisciplinary design optimization of complex products. A definition of KBE is provided, and its application in engineering design, supporting the use of MDO, is discussed. The working principles and main features of KBE systems are described with particular focus on their embedded programming language. This language is the core element of any KBE system and allows the capture and reuse of the design knowledge necessary to model complex engineering products. Of particular importance in this book is the facility it offers to automate the preparation phase for the multidisciplinary analysis process. The main categories of design rules that can be embedded in a KBE application are described, and several examples are given that pinpoint the main differences between KBE and classical rule-based design system and, in particular, conventional CAD tools. Finally, a section is provided describing the major steps in the evolution of KBE and its current trend in the broader CAD panorama.
To introduce methods that allow MDO solution methods to incorporate uncertainties.
The scope of this chapter is to systematically introduce the uncertainty-based multidisciplinary design and optimization (UMDO) theory and present a concise introduction to the typical UMDO methods. The chapter specifically focuses on the fundamental theory and general UMDO approaches but does not include a comprehensive review of the state-of-the-art algorithms. The chapter is structured to first present the preliminaries of UMDO, including the basic concepts and the general process for solving UMDO problems. Second, the key steps of UMDO, including uncertainty analysis and optimization under uncertainty, are expounded. Finally, an example is presented to illustrate the application of UMDO methods.
To describe methods that can be deployed to reduce the cost and time of an engineering design process based on the MDO methods.
This chapter reviews a variety of ways and means available for controlling and reducing the computational effort of both single-discipline and multidisciplinary design optimization. It takes into account the notion that “computational effort” may not be measured by a single metric. The chapter addresses the issues of speedup and cost reduction as scored by a number of different metrics that include the central processing unit (CPU) time, data transfer time, data storage, number of processors, and so on. Various techniques are presented that relate to these metrics in different ways and in varying degrees all utilizing the technology of parallel computing.
The aim of the appendix is to outline the implementation of a KBE system and describe its role in supporting the creation of a working MDO system.
The appendix provides information that can assist in incorporating a multimodel generator (MMG) in a commercial or self-made framework. It covers the steps necessary to go from the stage where the design problem is analyzed to go the point where a working framework has been developed. This includes the capture of basic design knowledge, the codification of product knowledge, and the application of this to support the creation of a Design and Engineering Engine (DEE). The different stages are illustrated with simple examples.
To provide an overview of the basic structure and process necessary for implementing a working MDO system (a DEE).
This appendix addresses the problem of constructing a framework which can house a DEE and make it into a working reality. It approaches this from the viewpoint that a process is required which can handle, manipulate, and operate with data across the entire design spectrum from requirements definition to a design tool. It, therefore, focuses on the software and other requirements need to convert the basic MDO systems, introduced in Chapter 8, into a working system.
This chapter sets the scene for the introduction of multidisciplinary design and optimization (MDO) methods and techniques in the design of modern products. It starts by exploring the nature of modern design then moves on to link this to the need for the application of optimizing methods which then leads on to the role played by MDO. We should emphasize that while, in the course of this book, we introduce and develop methods and models for MDO systems supporting the design of major engineering products, we are not advocating a rigid adherence to any of the methods and processes discussed. The key consideration in the selection or development of an appropriate design methodology is the nature of the design being addressed; it is always a question of “horses for courses.” It may be that a given design optimization problem is ideally suited to being solved by one of the methods to be presented in later chapters; but it may not be. In this latter situation, the reader may adopt a “pick and mix” approach taking components from several methods to generate an appropriate MDO system for the problem being confronted. Going farther down this pathway, the reader may decide to undertake a “pick and add” approach where some of the ideas presented are taken and added to by the introduction of new ideas specifically developed for the problem being addressed. This is an exciting path to go down as new ideas are required; however, if speed is of the essence, the engineer(s) adopting this approach needs to have well-honed arguments to avoid being publicly “hair dried” by senior management.
This chapter essentially sets the scene for what is to come in the ensuing chapters. We look at the modern design environment and discuss the position and role to be played by MDO in this environment. We start by looking at the underlying realities of the design process and then examine the role that optimization can play in finding an improved design.
The design of a large and complex engineering system such as an aircraft, an automobile, a ship, or a power plant may be described as a progression through a set of “what-if” questions and answers that engage a range of human, computing, and manufacturing resources, backed up by research and laboratory results and information. Underpinning this machinery is the need to find a solution to a set of design requirements, some of which will involve an optimum target, for example, that the weight or cost be minimized. In principle, the designer(s) must compile a design and computational architecture that is expected to create products that meet the requirements. Solving the design problem involves a sequential process employing a range of different analyses that create a set of trial designs whose performance can be compared with the required performance. This performance gap is then reduced through the sequential application of the design architecture until the gap closes. In an actual design environment, account has to be taken of the time and cost associated with the search. A design which is feasible but not optimal could very well be acceptable.
The team or teams involved in this design task may work in a single organization, but in today’s engineering environment, they are likely to be distributed across a number of cooperating organizations, some of which may be small and highly specialized. These teams work within a process that unfolds in time through a number of stages with increasing levels of complexity, as described in Section 2.3.1. MDO aspires to be the developer of the underlying methods and mathematical models employed in this process and provide the computing and data processing infrastructure. In achieving this objective, it must conform to the realities of the world in which engineers operate.
We now need to see how these realities map onto the MDO process which we do, in outline, under a number of key headings that make up the components in a working MDO system. These headings cover the multidisciplinary nature of the modern design process, introduce distributed design teams, and cover information growth and expansion as a design progresses down the time line. Some of the issues discussed in this section are addressed in greater detail in subsequent sections and in much finer detail in subsequent chapters. It should always be borne in mind that the type of formal methods being introduced in this book are focused on providing the design engineer with a computer-based architecture or infrastructure that supports, but does not replace, human ingenuity and creativity.
Multidisciplinary: The design of a major product in today’s world requires that individual disciplines interact and will not get disconnected. These include what might be called traditional disciplines, structures, aerodynamics, etc. but now encompass manufacturing, operations, disposal, and the associated economical business considerations. In normal practice, not all disciplines are taken into account to the same level of detail, and a key decision in setting out on an MDO design operation is what level of detail to consider for specific disciplines and, indeed, what to leave out.
Multiobjective Function: In the past, designers often tried to treat each design attribute as a separate function; today, attributes such as performance, quality, manufacturing cost, weight, safety, etc. must be grouped together in order to achieve a realistic optimum design and inform the designers about the trade-offs. In many cases, the sources of this information differ with respect to levels of fidelity, confidence, and completeness.
Multidisciplinary Multiteam Participation: The complexity of modern computer-based design support programs (such as FE, CFD, material design programs, etc.) means that the use of many of these tools has to be handled by separate specialists or specialist teams. These specialists expect to have authority in choosing their own tools and making design decisions in their domains as opposed to serving merely as analysts.
Distributed Design Team
