Building a computer-assisted process planning system using the hierarchical case-based reasoning approach

2011 ◽  
Vol 11 (s1) ◽  
pp. S1-S13 ◽  
Author(s):  
Huan-Yu Lin ◽  
Jun-Ming Su ◽  
Shian-Shyong Tseng ◽  
Chi-Chun Hsu ◽  
Chung-Chao Ku ◽  
...  
Author(s):  
Hao Yang ◽  
Wen F. Lu

AbstractThis paper presents an approach for the case adaptation, especially case repairing, in a case-based process planning system: PROCASE, for machining of rotational parts. In PROCASE, a new process plan is generated by adapting an existing similar process plan from its case library. Case adaptation is a crucial issue in achieving an automated case-based process planning system. This is because, usually, an existing process plan cannot necessarily produce an exact identical part as of the desired part. Adaptation is essential to tailor this existing plan to generate a new process plan for the new part. The case adaptation in this paper comprises case modification, case simulation, and case repairing. The modifier uses the knowledge extracted from case library to edit the retrieved similar plan. The simulator plays an important role in verifying the adapted plan as well as in directing the plan repairing. The repairing rules are indexed by the error messages obtained from the simulation. With the proposed case adaptation, the system will have the capability to repair the erroneous plans to achieve an automated and intelligent process planning system. This paper will first briefly introduce the case representation and case retrieval in PROCASE. Then the rest of the paper is dedicated to the case adaptation.


Author(s):  
Hao Yang ◽  
Wen F. Lu

Abstract An intelligent case-based process planning system with interactive graphic simulation environment, PROCASE, is developed to demonstrate an integrated methodology of case-based process planning system. In PROCASE, both the mechanical part features and the machining operations are represented with a frame based scheme. PROCASE contains a retriever, a modifier, a simulator and a repairer. It distinguishes itself from traditional rule-based process planning systems by representing the process planning knowledge through previous process planning cases instead of production rules. It therefore can overcome some problems in the traditional rule-based expert systems. PROCASE currently resides in IRIS Indigo workstation. With a user friendly graphic environment, the generated process plans can be demonstrated vividly. This simulation environment not only serves as a good assistance in debugging, but also helps the user to be convinced of the outcomes of the reasoning of PROCASE.


Author(s):  
V. Sundararajan ◽  
Paul K. Wright

Agile methods of software development promote the use of flexible architectures that can be rapidly refactored and rebuilt as necessary for the project. In the mechanical engineering domain, software tends to be very complex and requires the integration of several modules that result from the efforts of large numbers of programmers over several years. Such software needs to be extensible, modular, and adaptable so that a variety of algorithms can be quickly tested and deployed. This paper presents an application of the unified process (UP) to the development of a research process planning system called CyberCut. UP is used to (1) analyze and critique early versions of CyberCut and (2) to guide current and future developments of the CyberCut system. CyberCut is an integrated process planning system that converts user designs to instructions for a computer numerical control (CNC) milling machine. The conversion process involves algorithms to perform tasks such as feature extraction, fixture planning, tool selection, and tool-path planning. The UP-driven approach to the development of CyberCut involves two phases. The inception phase outlines a clear but incomplete description of the user needs. The elaboration phase involves iterative design, development, and testing using short cycles. The software makes substantial use of design patterns to promote clean and well-defined separation between and within components to enable independent development and testing. The overall development of the software tool took about two months with five programmers. It was later possible to easily integrate or substitute new algorithms into the system so that programming resources were more productively used to develop new algorithms. The experience with UP shows that methodologies such as UP are important for engineering software development where research goals, technology, algorithms, and implementations show dramatic and frequent changes.


Sign in / Sign up

Export Citation Format

Share Document