NBS AMRF process planning system- system architecture

Inspection is an essential part of the entire manufacturing chain providing measurement feedback to the process planning system. Fully automated machining requires automatic inspection process planning and real-time inspection results feedback. As inspection process planning is still based on G&M codes containing low-level information or vendor-specific bespoke routines, inspection process planning is mostly isolated from machining process planning. With the development of new data model standards STEP and STEP-NC providing high-level product information for the entire manufacturing chain, it is achievable to combine machining and inspection process planning to generate optimal machining and inspection sequences with real-time measurement results feedback. This paper introduces an integrated process planning system architecture for combined machining and inspection. In order to provide real-time inspection feedback, On-Machine Inspection (OMI) is chosen to carry out inspection operations. Implementation of the proposed architecture has been partially carried out with a newly developed data model and interpreter software. A case study was carried out to test the feasibility of the proposed architecture.

Download Full-text

Study on Process Planning System for Holonic Manufacturing : 1st Report, System Architecture and Recognition of Machining Feature

TRANSACTIONS OF THE JAPAN SOCIETY OF MECHANICAL ENGINEERS Series C ◽

10.1299/kikaic.65.2129 ◽

1999 ◽

Vol 65 (633) ◽

pp. 2129-2134 ◽

Cited By ~ 1

Author(s):

Nobuhiro SUGIMURA ◽

SUYOTO ◽

Takeshi TANAKA

Keyword(s):

Process Planning ◽

System Architecture ◽

Planning System ◽

Machining Feature ◽

Process Planning System ◽

Report System ◽

Holonic Manufacturing

Download Full-text

OPPS-PRI 2.0: an open and optimized process planning system for prismatic parts to improve the performance of SMEs in the machining industry

International Journal of Production Research ◽

10.1080/0020754042000298548 ◽

2005 ◽

Vol 43 (5) ◽

pp. 1039-1087 ◽

Cited By ~ 5

Author(s):

T. Derelİ * ◽

A. Baykasoğlu

Keyword(s):

Process Planning ◽

Planning System ◽

Prismatic Parts ◽

Process Planning System

Download Full-text

Applications of Software Engineering to Manufacturing Process Planning

Journal of Computing and Information Science in Engineering ◽

10.1115/1.2960488 ◽

2008 ◽

Vol 8 (3) ◽

Cited By ~ 2

Author(s):

V. Sundararajan ◽

Paul K. Wright

Keyword(s):

Software Development ◽

Process Planning ◽

Tool Path ◽

Numerical Control ◽

Planning System ◽

Cnc Milling ◽

Design Development ◽

Tool Selection ◽

Process Planning System ◽

New Algorithms

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.

Download Full-text