ComputerAided_Design_Engineering_amp_Manufactur.pdf
ComputerAided_Design_Engineering_amp_Manufactur.pdf
ComputerAided_Design_Engineering_amp_Manufactur.pdf
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
• Provision for support functions and methodologies for design critiquing, recording of design<br />
rationale, and planning and execution of design changes<br />
• Facilitation of group interaction between different groups of designers and software systems used<br />
for product development activities<br />
• Facilitation of synchronization between different product design tasks<br />
• Mechanisms for resolving conflicts among competing multiple product design perspectives<br />
• Provision for infrastructural support for the integration of the different product design modules<br />
• Development of a suitably structured product model for every stage of the product design process<br />
• Algorithms for mapping functional requirements of the component into appropriate types and<br />
associated values of product specifications (e.g., tolerances, surface finishes, geometry specifications,<br />
etc.).<br />
Which of the above tasks an IPD system ought to do and how it should go about doing them have<br />
been the subject of continued debate. 2–4 As a first step toward realization of IPD systems, researchers<br />
have focused their attention on the use of Intelligent Computer-Aided <strong>Design</strong> (ICAD) techniques for the<br />
development of IPD systems. The domain of ICAD techniques among other things includes the organization,<br />
integration, information management and transfer, and control of knowledge bases, expert<br />
systems, and data bases within the framework of the IPD system.<br />
A conventional CAD system with drafting, solid modeling, and design analysis capabilities often forms<br />
the basis on which an IPD system is built. Knowledge-based expert systems and data bases are the other<br />
key elements of an IPD system. In the past, the role of ICAD techniques was limited to the task of enabling<br />
interoperability between different CAD systems and design analysis tasks. 5–8 However, the issue of an<br />
effective integration of all product design tasks has still not been solved even with the introduction of<br />
such knowledge engineering systems. The issues that need to be addressed are mainly from the standpoint<br />
of a generic framework for design data representation, effective integration and coordination of design<br />
tasks, information processing, retrieval of similar designs, and design modification.<br />
The objective of this chapter is to report on the application of ICAD techniques for the implementation<br />
of IPD systems for various tasks associated with product design, such as design analysis, process planning,<br />
and tolerance assignment. Several case studies are presented to demonstrate the salient features of the<br />
application of ICAD techniques for product design activities.<br />
1.2 Elements of IPD Systems: ICAD Techniques<br />
Expert System/Knowledge Base<br />
As outlined in the previous section, one of the most useful functions of an IPD system is to embody the<br />
knowledge available for a given design task. Currently, this task is performed by a technical specialist<br />
who uses various high-level intelligent functions such as intuition, creativity, association, induction,<br />
recognition, and deduction, as well as low-level functions such as computation and information retrieval.<br />
Among the above list of functions, only a few low-level functions involving computation and search have<br />
been analyzed and algorithms have been devised for automatically performing these tasks. To facilitate<br />
higher levels of knowledge processing in an IPD system, the design artifact needs to be defined completely<br />
along with its full functional description. However, there are two obstacles in embedding such knowledge<br />
into an IPD system. First, the expert knowledge is characteristic of an individual or an organization based<br />
on the past experiences and design practices and is often difficult to encapsulate in appropriate design<br />
rules and guidelines; furthermore, this knowledge is extremely context sensitive and cannot be generalized.<br />
Additionally, when several such sources of knowledge are available within an organization, there is<br />
no algorithmic procedure or guideline to resolve the conflicting suggestions. In spite of these difficulties,<br />
expert system shells, together with knowledge bases, can be used for various types of inferencing tasks<br />
such as exploration of the space of all design solutions, generation of design alternatives, etc.<br />
© 2001 by CRC Press LLC