ComputerAided_Design_Engineering_amp_Manufactur.pdf
ComputerAided_Design_Engineering_amp_Manufactur.pdf
ComputerAided_Design_Engineering_amp_Manufactur.pdf
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2. Specification of analysis-specific information—providing all details that are required for performing<br />
an effective and efficient analysis of the given design problem;<br />
3. FEM model discretization—discretizing the entire FEM model into a properly connected mesh<br />
of suitably sized and shaped elements;<br />
4. Specifying design conditions—specifying loads and boundary conditions at appropriate nodes<br />
and elements of the FEM model;<br />
5. FEM Analysis—conducting the FEM analysis using specialized codes (in-house software programs)<br />
or commercial codes such as NASTRAN, ANSYS, etc.;<br />
6. Interpretation of FEA results—assessing the validity of the results for the specified design requirements;<br />
7. Repeating the steps until acceptable results are obtained. 12 In the recent past, most of the research<br />
efforts5–7<br />
© 2001 by CRC Press LLC<br />
were directed toward automation of Step 3. In order to achieve complete automation of<br />
design analysis tasks, one would need to address issues pertaining to the individual requirements<br />
of all of the above steps.<br />
Since the FEA procedure would have to be integrated and driven by a CAD system, the most obvious<br />
requirement relates to modeling the object in the CAD system and transferring geometric as well<br />
functional requirements information from the CAD system to the finite element preprocessor. ‘‘The more<br />
complete the geometric information passed to the preprocessor, the more automated the finite element<br />
analysis process can be made.’’ 5 Current CAD systems that are developed based on conventional<br />
information processing technology rely mostly on procedural representation of 3-D objects (solid<br />
models) and do not have the capability to undertake tasks such as automatic FEA. In order to break<br />
this barrier for integration, steps should be undertaken for developing a ‘‘complete’’ representation of<br />
the design object and the corresponding object model which should include: (a) geometric information<br />
to represent the shape and form of the design structure; (b) design-specific functional information to<br />
represent attributes, properties, behaviors, and functions of the design artifact; and (c) information<br />
management attributes and directives in order to ensure the smooth integration between the CAD and<br />
FEM systems. Moreover, the object model cannot be a static entity (e.g., data base data structure), and<br />
it needs to adopt flexible object and attribute representation schemes to aid in the FEA process. The<br />
system should attempt to utilize as much design-specific knowledge as possible in order to obtain a<br />
successful CAD-FEM interface.<br />
Based on the above mentioned list of requirements, the object-oriented approach for object model<br />
definition has been adopted for modeling the FEM analysis attribute information. 12 Frames have been<br />
selected as the means of knowledge representation in the object-oriented programming (OOP) environment.<br />
In OOP, self-contained pieces of code called ‘‘classes’’ (at the information concept level) and<br />
‘‘objects’’ (at the implementation level) represent the informational attributes of an artifact associated<br />
with an application or function. For instance, the <strong>Design</strong>-Information class shown in Table 1.1 represents<br />
a class template that contains information pertinent to the specified loading and boundary conditions<br />
on the design component, as well as the stated design requirements for FEA. Since the modeling of the<br />
original geometric model to an appropriate FEM model is necessary for reducing the computation time,<br />
a considerable amount of knowledge needs to be represented and consulted with in order to reason<br />
about: (a) simplified geometric representation of the object—submodeling the object model based on<br />
the inherent symmetry of the component geometry and design loads and restraints, and (b) removing<br />
subcritical geometric features (e.g., small holes, fillets, etc.) from the FEM model. Once the task of model<br />
building is complete, the geometrical, topological, and material data needs to be transferred from the<br />
CAD package to a standard FEA package such as ANSYS, etc., and package-specific knowledge is required<br />
for creating the appropriate data set for running the object model in the specific analysis package. The<br />
analysis of FEA results obtained is then assessed. Similar to FE modeling, the analysis of FEA results is<br />
also a knowledge intensive task, and often the designer’s judgment and past experience play a critical<br />
role in successful execution of these tasks. Furthermore, based on the FEA results, the redesign of the<br />
design object is another task where the designer’s experience and the redesign procedures adopted for