Concurrent Engineering Fundamentals: Integrated Product and Process Organization, Volume I

About

Features

• explains the seven primary influencing agents for achieving CE concurrency and simultaneity.

• details the essential work-group concept representing the four CE teams: the personnel team, technology team, logical team, and the virtual team.

• shows how CE encompasses manufacturing competitiveness, life-cycle management, process reengineering, cooperative work groups, systems engineering, information modeling, and PPO (product, process, and organization) integration.

Description

The concurrent engineering (CE) approach to product design and development has two major steps: establishing the product realization process, or taxonomy, and applying this methodology to design and develop the total product system. This first volume of the two volume set articulates CE philosophy by illustrating the differences between the best methodologies and what is currently being practiced. KEY TOPICS: Examines the Japanese transformation from rigid, culture-driven companies to world leaders in quality; offers an understanding of the eight primary components of concurrency and simultaneity; describes modeling the concurrent engineering environment and its five essential components; covers the development of a cooperative work-group environment spanned by four concurrent teams.

Sample Content

Table of Contents

Computer Acronyms.


Preface.


Acknowledgments.


About the Author.


1. Manufacturing Competitiveness.

Introduction. Review of Historical Events. Push and Pull for New Paradigms. Areas of Manufacturing Competitiveness. Product and Services. Process and Methodologies. Performance Indicators. Infrastructure. References. Test Problems: Manufacturing Competitiveness.

Introduction. Shrinking Life-Cycle. Life-Cycle Management. New Product Introduction. Strategic Technology Insertions. Managing Continuity. Managing Revision Changes. Life-Cycle Cost Drivers. Life-Cycle Management Tools. Sequential versus Concurrent Engineering. References. Test Problems: Life-Cycle Management.

Introduction. Understanding and Managing Change. Reengineering Approaches. Tenents of Process Improvement. Work Flow Mapping. Information Flow-Charting. Enterprise Models. Process Improvement Methodology. Change Management Methodology. Concurrent Process Reengineering. Concluding Remarks. References. Test Problems: Process Reengineering.

Introduction. Basic Principles of CE. Components of CE. Concurrency and Simultaneity. Modes of Concurrency. Modes of Cooperation. Benefits of Concurrent Engineering. References. Test Problems: CE Definitions.

Introduction. Cooperative Concurrent Teams. Program Organization. Supplier Rationalization. Types of CE Organization. Management Styles or Philosophies. Workplace Organization and Visual Control. Employee Excellence Development (New Technologies and Team Capabilities). References. Test Problems: Cooperative Work Teams.

Introduction. An Automobile Manufacturing Process. System Engineering. Systems Thinking. Approaches to System Complexity. Sharing and Collaboration in CE 300. System Integration. Management and Reporting Structure. Agile Virtual Company. References. Test Problems: System Engineering.

Information Modeling. Modeling Methodology. Foundation of Information Modeling. Concurrent Engineering Process Invariant. Enterprise Model-Class. Specification Model-Class. Product Model-Class. Process Model- Class. Cognitive Models. Merits and Demerits. Summary. References. Test Problems: Information Modeling.

Introduction. Conventional Design and Development Process. A Transformation Model for a Manufacturing System. CE Enterprise System Taxonomy. Integrated Product and Process Development. Transformation System for Product Realization. Key Dimensions of a CE Specification Set. Artifact's Intent Definitions. References. Test Problems: The Whole System.

Introduction. Development Methodology for CPRT. Concurrent Product Realization Taxonomy. Pull System of Product Realization. Description of Parallel Tracks. Description of 2-T Loops. Description of 3-T Loops. Major Benefits. References. Test Problems: Product Realization Taxonomy.

Preface

Preface As the name implies, the book describes the fundamentals of Concurrent Engineering and explains the basic principles on which this very subject is founded. The most of the materials in the book are either original ideas or their extension to CE. Most is never reported elsewhere and is based on the author's successes while practicing CE on the job, and decades of his research and learning working with electronic, automotive, aerospace and railroad industries including Ford, General Motors, Electronic Data Systems, Association of American Railroads, NASA and numerous other places abroad. Concurrent Engineering approach to product design and development has two major themes. The first theme is establishing a concurrent product and process organization. This is referred to herein as "process taxonomy." The second theme is applying this process taxonomy (or methodology) to design and develop the total product system. This is referred to as integrated product development (IPD). Each theme is divided into several essential parts forming major chapters of this book. The first volume called integrated product and process organization has nine chapters. The second volume named integrated product development has ten chapters. The materials in these two volumes are brought together to balance the interests of both the customers and the companies. The contents of Volume One are: Manufacturing Competitiveness: Life-cycle Management, Process Reengineering, Concurrent Engineering Definitions, Cooperative Work Teams, System Engineering, Information Modeling, The Whole System, and Product Realization Taxonomy. The contents of Volume Two are: Total Value Management, CE Metrics and Measures, Concurrent Function Deployment, Integrated Product Development, Frameworks and Architectures, Decision Support System, Intelligent Information System, Capturing Life-Cycle Values, Life-Cycle Mechanization, and CE Implementation Guidelines. In Concurrent Engineering (CE) system, each modification of the product represents a transformation relationship between specifications (inputs, requirements and constraints), outputs, and the concept the modification represents. At the beginning of the transformation, the specifications are generally in abstract forms. As more and more of the specifications are satisfied, the product begins to take shape (begins to evolve into a physical form). To illustrate how a full CE system will work, and to show the inner-working of its elements, author defines this CE system as a set of two synchronized wheels. The representation is analogous to a set of synchronized wheels of a bicycle. Figure 1 shows this CE wheel set. Concurrent Engineering Wheels The first CE wheel represents the integrated product and process organization. The second CE wheel accomplishes the integrated product development. The two wheels together harmonize the interests of the customers and the fostering CE organization (frequently referred to as an enterprise). The contents of the first wheel are described in Volume One and the contents of second wheel are described in Volume Two of the CE fundamental books. Three concentric rings represent the three essential elements of a wheel. The middle ring represents the CE work-groups, which drive the customer and the enterprise like how a human drives a bike. The work-groups are divided into four quadrants representing the four so called CE teams. These teams are: the personnel team, the technology team, the logical team, and the virtual team. They are discussed in Chapter 5. The outer ring for each wheel is divided into eight parts. Each part represents a chapter of this book. The parts for the first wheel are discussed in Volume One. This volume explains how the CE design process (called herein CE process taxonomy) provides a stable, repeatable process through which increased accuracy is achieved. The book starts with an introductory chapter on manufacturing competitiveness reviewing the history and emerging trends. The remaining chapters of the book (Volume One) describe CE design process, explain how concurrent design process can create a competitive advantage, define CE process taxonomy, and address a number of major issues related to product and process organization. The parts of the second wheel are discussed in Volume Two. A separate chapter in the book is dedicated to discussing each part of the two CE wheels. First CE Wheel: Integrated Product and Process Organization The innermost ring of the first CE wheel is a hub. The layout of the hub is same for both wheels. The hub represents four supporting "M" elements: models, methods, metrics and measures. Models refer to information modeling. Methods refer to product realization taxonomy. They are discussed in Chapters 7 and 9 of Volume One, respectively. CE Metrics and Measures are discussed in Chapter 2 of Volume Two. The complexity of the product design and development (PDD) process differs depending upon the (i) Types of information and sources (ii) Complexity of tasks (iii) Degree of their incompleteness or ambiguity Other dimensions encountered during this PDD process that cannot be easily accommodated using traditional process (such as serial engineering) are: (iv) Timing of decision making (v) Order of decision making (vi) Communication mechanism The elements of the first CE wheel define a set of systems and processes that have the ability to handle all of the above six dimensions. In the following some salient points of the chapters are briefly highlighted: ¥ Manufacturing Competitiveness: The price of the product is dictated by world economy and not by one's own economy or a company's market edge alone. Those companies that can quickly change to world changing market place can position themselves to complete globally. This chapter outlines what is required to become a market leader and compete globally. Successful companies have been the ones who have gained a better focus on eliminating waste, normally sneaked into their products, by understanding what drives product and process costs and, how value can be added. They have focused on a product and process delivery-system-how to transform process innovations into technical success and how to leverage the implementation know-how into big commercial success. Many have chosen to emphasize high-quality flexible or agile production in product delivery rather than high-volume (mass) production. ¥ Life-cycle Management: Today, most companies are under extreme pressure to develop products within time periods that are rapidly shrinking. As the market changes so do the requirements. This has chilling effect in managing the complexity of such continuously varying product specifications and handling the changes within this shrinking time period. The ongoing success of an organization lies in its ability to: continue to evolve; quickly react to changing requirements; reinvent itself on a regular basis; and keep up with ever changing technology and innovation. Many companies are stepping up the pace of new product introduction, and are constantly learning new ways of engineering products more correctly the first time, and more often thereafter. This chapter outlines life-cycle management techniques, such as management change, and process improvement to remain globally competitive. ¥ Process Reengineering: The global marketplace of the 1990s has shown no sympathy to tradition. The reality is that if the products manufactured do not meet the market needs, demand declines and profits dwindle. Many companies are finding that true increase in productivity and efficiency begins with such factors as clean and efficient process, good communication infrastructure, teamwork, a constancy of shared vision and purpose. The challenge is simply not to crank up the speed of the machines so that its outputs (per unit of time) are increased or doubled, but to change the basic machinery or process that produces the outputs. To accomplish the latter goals, this chapter describes several techniques to achieve competitive superiority such as benchmarking, CPI, organizational restructuring, renovation, process re-engineering, etc. ¥ CE Definitions: The changing market conditions and international competitiveness are making the time-to-market a fast shrinking target. Over the same period, diversity and complexity of the products have increased multi-folds. Concurrency is the major force of Concurrent Engineering. Paralleling describes a "time overlap" of one or more work-groups, activities, tasks, etc. This chapter describes seven CE principles to aim at: Parallel Work-group, Parallel Product Decomposition; Concurrent Resource Scheduling; Concurrent Processing; Minimize Interfaces; Transparent Communication; and Quick Processing. This chapter also describes the seven forces that influence the domain of CE (called here as agents or 7Ts) namely: talents, tasks, teams, techniques, technology, time and tools. ¥ Cooperative Work-groups: It has been the challenge for the design and manufacturing engineers to work together as teams to improve quality while reducing costs, weight, and lead-time. A single person, or a team of persons, is not enough to provide all the links between: human knowledge and skills; logical organization; technology; and a set of 7Cs coordination features. A number of supporting teams is required, some either virtual or at least virtually collocated. For the waltz of CE synthesis to succeed, CE teams need clear choreography. This chapter describes for the first time the four collaborative teams that are essential for managing a CE organization. Examples of collaborative features include capabilities of electronic meeting such as message-posting and interactions through voice, text, graphics and pictures. ¥ System Engineering: Most groups diligently work to optimize their sub-systems, but due to lack of incentives they tend to work independently of each other. This results in a product, which is often sub- optimized at each decomposed level. System engineering requires that product realization problem is viewed as a "system-centered" problem as opposed to "component-centered." Systems Engineering does not disagree with the idea of compartments or divisions of works, but it emphasizes that the interface requirements between the divisions (inter-divisional) and across the level should be adequately covered. That way, when the time comes to modernize other components of the system, an enterprise has the assurance that previously introduced technologies and processes will work logically in a fully integrated fashion, thereby increasing the net efficiency and profitability. ¥ Information Modeling: A successful integrated product development (IPD) requires a sufficient understanding of the product and process behaviors. One way to achieve this understanding is to use a series of reliable information models for planning, designing, optimizing and controlling each unit of the IPD process. The demands go beyond the 3-D CAD geometric modeling. The demands require schemes that can model all phases of a product's life-cycle from cradle to grave. The different aspects of product design (planning, feasibility, design, process-planning), process design (process-execution, production, manufacturing, product support), the human behavior in teamwork, and the organization or environment in which it will operate, all have to be taken into account. Five major classes of modeling schemata are discussed in this chapter. The are: (a) Product representation schemes and tools for capturing and describing the product development process and design of various interfaces, such as design-manufacturing interface; (b) Schemes for modeling physical processes, including simulation, as well as models useful for product assessments, such as DFA/DFX, manufacturability evaluation of in-progress designs; (c) Schemes for capturing (product, process, and organization structure) requirements or characteristics for setting strategic and business goals; (d) Schemes to model enterprise activities (data and work flow) in order to determine what types of functions best fit the desired profitability, responsiveness, quality and productivity goals; and (e) Schemes to model team behavior, because most effective manufacturing environments involve a carefully orchestrated interplay between teams and machines. ¥ The Whole System: Often while designing an artifact, work-groups forget that the product is a system. It consists of a number of subassemblies, each fulfilling a different but distinct function. A product is far more than the collection of components. Without a structure or "constancy-of-purpose" there is no system. The central difference between a CE transformation system and any other manufacturing system, such as serial engineering, is the manner in which the tasks' distribution is stated and requirements are accomplished. In a CE transformation system, the purpose of every process step of a manufacturing system is not just to achieve a transformation but to accomplish this in an optimal and concurrent way. This chapter proposes a system-based taxonomy, which is founded on parallel scheduling of tasks and a breakdown structures for product, process and work to realize a drastic reduction in time and cost in product and process realizations. ¥ Product Realization Taxonomy: This constitutes a "state of series of evolution or transformation" leading to a complete design maturity. Product Realization Taxonomy involves items related to design incompleteness, product development practices, readiness feasibility, and assessing goodness. In addition, CE requires these taxonomies to have a unified "product realization base." The enterprise integration metrics of the CE model should be well characterized and the modeling methodologies and/or associated ontology for developing them should be adequate for describing and integrating enterprise functions. The methodologies should have built-in product and service accelerators. Taxonomy comprises of the product, process descriptions, classification techniques, information concepts, representation, and transformation model for product realization. They are included as part of the taxonomy descriptions. Second CE Wheel: Integrated Product Development The second CE wheel defines the integrated product development (IPD). This is discussed in the second Volume. IPD in this context does not imply a step-by-step serial process. Indeed, the beauty of this wheel (integrated product development) is that it offers a framework for a concurrent product design and development. A framework within which, the CE teams have flexibility to move about, fitting together bits of the jigsaw as they come together. CE teams have opportunity to apply a variety of techniques contained in this volume (such as: Concurrent Function Development, Total Value Management, Metrics and Measures, etc.) and through their use have opportunity to achieve steady overall progress towards a finished product. ¥ Concurrent Function Deployment: The role of the organization and engineers is changing today, as is the method of doing business. Competition has driven organization to consider concepts such as time compression (fast-to-market), Concurrent Engineering, Design for X-ability, and Tools and Technology (such as Taguchi, Value Engineering) while designing and developing an artifact. Quality Function Deployment (QFD) addresses major aspects of "quality" with reference to the functions it performs, but this is one of the many functions that need to be deployed. With conventional deployment, it is difficult, however, to address all aspects of Total Values Management (TVM) such as X-ability, Cost, Tools and Technology, Responsiveness and Organization issues. It is not enough to deploy just the "Quality" into the product and expect the outcome to be the World Class. TVM efforts are vital in maintaining a competitive edge in today's world marketplace. ¥ CE Merits and Measures: Metrics are the basis of monitoring and measuring process improvement methodology and managing their effectiveness. Metric information assists in monitoring team progress, measuring quality of products produced, managing the effectiveness of the improved process, and providing related feedback. Individual assurances of DFX specifications (one at a time) do not capture the most important aspect of Concurrent Engineering-the system perspectives, or the trade-off across the different DFX principles. While satisfying these DFX principles in this isolated manner, only those which are not in conflict are usually met. Concurrent engineering views the design and evaluates the artifact as a system, which has a wider impact than just sub-optimizing the sub-systems within each domain. ¥ Total Value Management: The most acclaimed slogan for introducing a quality program in early corporate days simply was to provide the most value for the lowest cost. This changed as the competitiveness became more fierce. For example, during the introduction of traditional TQM program in 1990 "getting a quality product to market for a fair price" was the name of the game. The new paradigm for CE now is total values management (TVM): "to provide the total value for the lowest cost in the least amount of time, which satisfies the customers the most and lets the company make a fair profit." Here use of "value" is not just limited to "quality." To provide long lasting added value, companies must change their philosophy towards things like x-ability, responsiveness, functionality, tools and technology, cost, architecture, etc. ¥ Integrated Product Development: A systematic methodology is essential in order to be able to integrate: (a) teamwork; (b) information modeling; (c) product realization taxonomy; and (d) measures of merits (called CE metrics), and quantitatively assess the effectiveness of the transformation. This may involve identification of performance metrics for measuring the product and process behaviors. Integrated product development methodology is geared to take advantage of the product realization taxonomy. ¥ Frameworks & Architectures: In order to adequately support the CE-4Ms (namely: modeling, methods, metrics and measurements), it is necessary to have an architecture that is openly accessible across different CE teams, information systems, platforms, and networks, Architecture consists of information contents, integrated data structures, knowledge-bases, behavior and rules. An architecture not only provides an information base for easy storage, retrieval, and tracking version control, but can also be accessed by different users simultaneously, under ramp-up scheduling of parallel tasks, and in synchronization. We also need a product management system containing work management capabilities integrated with the database. This is essential because in CE there exists a large degree of flexibility for parallelism that must be managed in conjunction with other routine file and data management tasks. ¥ Capturing Life-cycle Intent: Most CAD/CAM tools are not really "capture" tools. In static representation of CAD geometry, configuration changes cannot be handled easily, particularly when parts and dimensions are linked. This has resulted in loss of configuration control, proliferation of changes to fix the errors caused by other changes, and sometimes ambiguous designs. By capturing "design intent": as opposed to "static geometry," configuration changes could be made and controlled more effectively using the power of the computer than through traditional CAD attributes (such as lines and surfaces). The power of a "capture" tool comes from the methods used in capturing the "design intent" initially so that the required changes can be made easily and quickly, if needed. "Life-cycle capture" refers to the definition of the physical object and its environment in some generic form. "Life-cycle intent" means representing the "life-cycle capture" in a form, which can be modified and iterated until all the life-cycle specifications for the product are fully satisfied. ¥ Decision Support System: In CE, cooperation is required between CE teams, management, suppliers, and customers. A knowledge based support system will help the participating teams in decision making and to reflect balanced views. Tradeoffs between conflicting requirements can be made on the basis of information obtained from sensitivity, multi-criterion objectives, simulation, or feedback. The taxonomy can be made a part of decision support system (DSS) in supporting decisions about product decomposition by keeping track of what specifications are satisfied, in ensuring common visibility in the state of product realization, including dispatching and monitoring of tasks, structure, corporate design histories, etc. ¥ Intelligent Information System (IIS): Another major goal of CE is to handle information intelligently in multimedia-audio, video, text, graphics. Since IIS equals CIM plus CE, with IIS, many relevant CE demands can be addressed and quickly processed. Examples include: (a) over local or wide area networks, such as SQL, which connects remote, multiple databases and multimedia repositories; (b) any needed information, such as recorded product designers' design notes, figures, decisions, etc., can be made available on demand at the right place at the right time; (c) any team can retrieve information in the right format and distribute it promptly to the other members of the CE teams. ¥ Life-cycle Mechanization: Life-cycle mechanization equals CIM + Automation + CE. Life-cycle mechanization is arranged under a familiar acronym: CAE, for CIM, Automation, and CE. Since CAE also equals IIS plus automation, the major benefits of mechanization in CAE come from removing or breaking barriers. The three common barriers are: (a) integration (this is a term taken from CIM), (b) automation, and (c) cooperation (which is a term taken from CE). CE provides the decision support element, and CIM provides the framework & architecture plus the information management elements. Life-cycle Mechanization refers to the automation of life-cycle functions or creation of computerized modules that are built from one another and share the information from one another. This includes integration and seamless transfer of data between commercial computer-based engineering tools and product-specific in-house applications. This tends to reduce the dependency of many CE teams on communication links and product realization strategies, such as decomposition and concatenation. ¥ CE Implementation Guidelines: The purpose of this chapter is to offer an implementation guideline for product redesign and development through its life-cycle functions. IPD implementation is a multi-track methodology. The tracks overlap, but still provide a structured approach to organizing product ideas and measures for concurrently performing the associated tasks. Concurrency is built in a number of ways (similar to what was discussed in Volume One), depending upon the complexity of the process or the system involved. This chapter proposes a set of "Ten Commandments," which serves to guide the product and process iterative aspects of IPD rather than just the work-group collaborative aspects during the development cycle. The CE teamwork in the center of the wheel ensures that both local or zonal iterative refinements and collaborative refinements take place during each concurrent track. A Synchronized Wheel set for CE All the above nineteen parts of CE put together creates a synchronized wheel set for CE, as shown in Figure 1. The teamwork, with four cooperating components (technological teams, logical teams, virtual teams, and personnel teams), is in the middle ring. The 4Ms (models, metrics, measurements and methodology) form the center of this wheel. The center has four parts to it: Information Modeling; Product Realization Taxonomy; Measures of Merit; and Integrated Product Development. The 4Ms are shown in the center because it provides the methodology for guiding the product realization process. The two inner rings, which are the same for both wheels, makes the wheels a synchronized set. The teams in the middle ring are the driving force of the methodology (4Ms listed in the center) and controller of the technologies (listed on the outer ring). The emphasis of a team-centered wheel for CE is a departure from a conventional function- centered approach. Outer rings of each wheel contain the remaining parts of "integrated product and process organization (first Volume) and integrated product development (second Volume), respectively. The idea of this middle ring is to provide a team-centered 7Cs (Collaboration, Commitment, Communications, Compromise, Consensus, Continuous Improvement, and Coordination) interplay across layers of enabling technologies and methodologies. Everything is geared towards cutting and compressing the time needed to design, analyze, and manufacture marketable products. Along the way, costs are also reduced, product quality is improved and customer satisfaction is enhanced due to the synchronized process. There is, however, a finite window in which the benefits of time compression and cost cutting are available. As more manufacturers reduce lead time, what once represented a competitive advantage can become a weakening source. Fortunately, the CE wheel provides a continuum (dynamic) base through which new paradigms (process, tools, technology, and 7Ts) can be launched to remain globally competitive for a long haul. Before we take a closer look at the different parts of this wheel as different chapters of this book, it is important to note that all the parts are not of the same kind. They emphasize different aspects of CE. The four major aspects are (see Figure 2): ¥ Philosophical aspect ¥ Methodological aspect ¥ Conceptual aspect ¥ Virtual aspect ¥ Philosophical Aspect: Personnel CE team governs the philosophical aspects of CE. Philosophical aspect deals with the boundaries of the responsibility and the authority, culture, empowerment, teams make- up, program organization, supplier rationalization, management styles or philosophies, change management, workplace organization and visual control, physical proximity (collocation), management and reporting structure, etc. The chapters on Cooperative Teamwork and Life-cycle Management emphasize more of this aspect than others. ¥ Methodological Aspect: of CE is governed by technology team. Methodological aspect deals with system thinking, approaches to system complexity, system integration, transformation model of the manufacturing system, CE enterprise system taxonomy, integrated product and process development, transformation system for product realization, pull system for product realization, track and loop methodology, etc. The chapters on Systems Engineering, the Whole System and Product Realization Taxonomy emphasize more of this aspect than others. ¥ Conceptual Aspect: Logical CE team governs the conceptual aspect of CE. Conceptual aspect mostly deals with principles of CE, concurrency and simultaneity, modes of concurrency, modes of cooperation, understanding and managing change, reengineering approaches, work flow mapping, information flow charting, process improvement methodology, etc. The chapters on CE Definitions and Process Re-engineering emphasize more of this aspect than others. ¥ Virtual Aspect: of CE is governed by a virtual CE team. Virtual aspect mostly deals with capturing life-cycle intent, information modeling, electronic capture of CE invariants. These CE invariants deal with product model class, process model class, specification models, cognitive models, communication through virtual proximity, agile virtual company, artifact intent definitions, etc. The chapters on Information Modeling and Life-cycle Management emphasize more of this aspect than others. Major FEatures of this Book Whether you are a firm CE believer, or this is your first introduction to CE, this book provides a full view of CE from all of the above aspects and perspectives. The management perspective, which is a part of philosophical aspect, relates to organization and culture. Complete with a historical review and context, the author articulates these CE aspects by illustrating the differences between the best methodologies (or the best taxonomies) and what are currently being practiced in industries today. Some examples of topics include: ¥ Japan Transformation from rigid culture-driven company to world leader in quality. ¥ Eight fundamental principles on which CE is founded ¥ Understanding the seven primary components of concurrency and simultaneity ¥ Modeling the CE environment and its five essential components ¥ Accounting for Seven C's to ensure cooperation among work-groups ¥ Seven primary influencing agents (called 7Ts) for achieving concurrency and simultaneity. ¥ Cooperative work-group environment spanned by four concurrent teams: (namely-logical team, personnel team, virtual team and technological team) Integrated product and process organization (Volume One) deals with process taxonomy for CE. Process taxonomy is necessary to adequately classify, distribute and distinguish differences in behaviors of a complex enterprise from a traditional system. The innermost core of this process taxonomy is its foundation, which has four supporting M elements: models, methods, metrics and measures as mentioned earlier. The following table summarizes the major features of this book: What chapters or sections of the book contain these Features of this book How does this feature benefit readers? features or examples of them? This is the first CE book, which empha- This allows the readers to look for items Chapter 4 (see Figure 4.1) sized seven primary influencing that can significantly affect responsive- agents (called 7Ts) for achieving ness and may be the root cause for cost, concurrency and simultaneity. quality and productivity loss. Book features manufacturing competi- It allows the readers to consider a wider Chapters 1 through 8 tiveness, life-cycle management, view meaning "integrating over the process re-engineering, cooperative enterprise" while implementing CE. work-groups, systems engineering, This eliminates the common problem of information modeling, and PPO blindly automating design-that may (product, process and organization) mean repeating the same old mistakes integration issues all described under but doing it more often and more quickly. a unified theme of "process taxonomy." Concurrent system tends to operate in It allows the PDT groups to gradually built- Chapter 4 (see Figure 4.11) one of the two modes. The book up the right information and to link up describes for the first time these two the process activities with required skills modes of concurrency. These modes so that project can be finished on time. are called in this book overlapped pull system and a linked system. Organization of CE is approached by This constitutes a "state of series of Chapter 9 (see Figure 9.10, splitting the system level problem into transformation" leading to an early Figure 9.16 and Figure 9.19) its mutually separable transformation completion of a mature design. states, followed by modeling of each state, then the reconstruction of the system definition from the aggrega- tion of the definitions of its con- stituent states. No one has looked at the product realiza- The result is a virtual approach to defining Chapter 8 (see Figure 8.1) tion process by decomposing its five multi-disciplinary problems and their components (work, product, process, solutions for improved productivity. system and enterprise) into their cor- responding breakdown structures so as to exploit the inherent concurrency and independence of the decomposed parts. What chapters or sections of the book contain these Features of this book How does this feature benefit readers? features or examples of them? The book for the first time views the It allows the PDTs to come up with an Chapter 5 (see Figures 5.7 integrated product development as a effective team design. An effective team through 5.9) cooperative work-group environment is like a peak-performing symphony spanned by four concurrent teams: orchestra: a group of specialists from these (namely-logical team, personnel core CE teams creating an inspirational team, virtual team and technological performance through mutual harnessing team). and cooperating process. Cooperation is the key lynch-pin of Seven 7Cs help identify the extent to which Chapter 5 (see Figure 5.2) achieving teamwork. The book the organizational culture of "self-interest" describes for the first time the seven supports or detracts from achieving a elements (called 7Cs) to bring in unified product concept (or a common team cooperation philosophy. set of company goals). Benefits of CE stem from a few basic Principles help the teams make timely Chapter 4 (see Section 4.1) principles. The book describes a set of decisions and early problem discovery. eight fundamental principles on which Approximately eighty percent of product's CE is founded life-cycle development cost is driven by decisions made in the first twenty percent of the program effort. Concurrency is the major force of The rewards and satisfaction in CE come Chapter 4 (see Section 4.3) Concurrent Engineering. The book for from the success of its components. the first time describes seven major Components yield a significant competitive components that assure concurrency advantage in product cost, quality, in- and simultaneity vestments, and reduction in cycle time. At the end of each chapter, test problems are included. The instructor may choose a set of problems (ten or less) that he or she has covered in the class for that week from each chapter. Most test problems are based on the materials covered in the chapter itself. Some are based on materials covered in the earlier chapters thus stretching the student's grasp and understanding of the subject matters covered so far. Only a few test problems require stretching the students' imagination beyond what is discussed in this book. A rich reference section is provided for professors to reinforce the materials beyond what is discussed therein. The generous use of self-explanatory illustrations and bullets makes this book an easy and pleasant reading for everyone. Illustrations provide a quick visual grasp of the materials without the use of long and wordy sentences and paragraphs. Biren Prasad Electronic Data Systems General Motors

Updates

Submit Errata