This posting also available on this page

1. Handout CAPP by Dr TC Chang – Purdue University

Overview : Process planning is also called: manufacturing planning, process planning, material processing, process engineering, and machine routing. Which machining processes and parameters are to be used (as well as those machines capable of performing these processes) to convert (machine) a piece part from its initial form to a final form predetermined (usually by a design engineer) from an engineering drawing.  downloads handout capp

2. Computer Aided Process Planning Berdasar Pada Desain Berbasis Feature oleh Isa Setiasyah Toha (LSP ITB) & Hadeli (LSP Unika Parahyangan) downloads paper sp4_b13

Abstrak : Aktivitas pembuatan suatu produk, akan melalui beberapa tahap, yaitu : desain, perencanaan proses, perencanaan produksi dan proses produksi. Untuk mencapai suatu kapabilitas manufaktur yang tangkas, integrasi antar tahap tersebut merupakan suatu keharusan. Oleh karena itu penyelesaian pada masing- masing tahap harus diselaraskan sedemikian rupa sehingga membentuk suatu integrasi yang kokoh. Dengan CAPP ini akan dapat menentukan operasi pemesinan, pengurutan operasi pemesinan, pemilihan cutting tool, pemilihan mesin, penentuan setup, perhitungan parameter pemotongan, perencanaan gerak pahat dan pembuatan program NC(Numerical Control).

3. Desain Komponen Prismatik Berbantuan Feature Pembentuk oleh Isa Setiasyah Toha  & Arif Budiono (LSP ITB) download sp4_b25

Abstrak :Salah satu upaya untuk menurunkan waktu-manufaktur adalah melalui penurunan waktu-desain dan waktu-persiapan. Entitas yang sering digunakan untuk mengkomunikasikan dan mengintegrasikan adalah feature. Penelitian ini membahas permasalahan desain berbantuan feature yang berbeda dengan lainnya oleh karena menggunakan model feature yang baru. Dengan menggunakan model feature yang dikembangkan, dapat dihasilkan variasi feature yang lebih banyak dan lebih memudahkan bagi desainer, tanpa meningkatkan kerumitan dalam pengembangan algoritmanya.  Model feature yang baru ini digunakan pada pengembangan perangkat-lunak desain komponen berbantuan feature untuk komponen prismatik.

4. The Analysis of Methods for Computer Aided Process Planning by Edward Gawlik – Cracow Univ Poland (downloads here)

Summary : This paper presents the analysis of most important methods for Computer Aided Process Pla ning and application possibilities in practice.

5. Integrated Approach in Computer Aided Process Planning by George Dragichi & Iaoan Bondrea – Romania (downloads here)

Abstract : This paper presents the conception and achievement of a CAPP module integrated in a CIM system. For the conception of the CAPP module the DB, OOP and OODBMS methods have been integrated in . Thus, a hybride CAPP module (TechCIM) have been realised, which was integrated into a CIM system designed for the manufacturing of the cardanic transmissions from cars. By integrating of the product conception the technology processes and the manufacturing in the computer integrated manufacturing have been achieved a raise in the manufacturing flexibility, the reducing of the delivering times and the improvement of the realised products’ quality.

From Webopedia :

Most operating environments, such as MS-Windows, provide an API so that programmers can write applications consistent with the operating environment. Although APIs are designed for programmers, they are ultimately good for users because they guarantee that all programs using a common API will have similar interfaces. This makes it easier for users to learn new programs.

From Wikipedia : An API (Application Programming Interface) is a basic library consisting of interfaces, functions, classes, structures, enumerations, etc. for building a software application. An API is an interface used by development teams to interact with the software. It is very helpful for customizing the software or enhancing the needs for a software application. On a day to day basis, a lot of system- defined and user- defined functions/methods/classes become available within the API. As the list of these functions or classes increase, it becomes very tedious for developers to keep track or remember all the functions and the parameters defined. Hence, the API writers are responsible for the API content used for building such software applications.

Often, API writers are not only confined to writing or documenting these new functions or classes. It would be highly required for API writers to understand the software platform/product and document the new features or changes as part of the new software release. Usually, the software release change happens three times in a year or it may vary from organization to organization depending upon their needs. The writers need to well understand the software life cycle and are aligned within the SDLC process. Documentation becomes a very important activity as part of the life cycle. Also, it is very important to understand the complete process of operations within the life cycle.

_________________________________________________________________

Dari dua pengertian diatas, dapat kita tarik kesimpulan bahwasannya API atau Application Programming Interface merupakan suatu dokumentasi yang terdiri dari antar muka, fungsi, kelas,struktur, dsb untuk membangun sebuah perangkat lunak. Dengan adanya API ini, maka memudahkan seorang programmer untuk “membongkar” suatu software untuk kemudian dapat dikembangkan atau diintegrasikan dengan perangkat lunak yang lain.

API dapat dikatakan sebagai penghubung suatu aplikasi dengan aplikasi lainnya. Suatu rutin standar yang memungkinkan programmer menggunakan system function. Proses ini dikelola melalui operating sistem. Keunggulan dari API ini adalah memungkinkan suatu aplikasi dengan aplikasi lainnya untuk saling berinteraksi.

Kebanyakan Sistem Operasi, seperti Windows, menyediakan fasilitas API sehingga programmer dapat melakukan aktivitas programming dengan lebih konsisten. Meskipun API didesain untuk programer, namun API juga baik untuk user karena setidaknya dapat menjamin bahwa program tersebut memiliki interface yang sama, sehingga lebih mudah untuk dipelajari.

Dalam penelitian yang saya lakukan, saya banyak sekali terbantu oleh dokumentasi API dari software Solidworks ini, meskipun butuh waktu lama untuk memahaminya namun tanpa API ini tentunya proses pengembangan software akan lebih sulit dan akan memakan waktu yang lama. Untuk mengaksesnya, tinggal gunakan saja fasilitas help dan searching dengan keywords API. API pada Solidworks cukup baik, lengkap, dan terstruktur, saking banyaknya, mencari dan memahaminya harus sabar… Tapi, kesabaran adalah kunci keberhasilan bukan!? Untuk lebih memahami API, atau tertarik untuk mendesain API, silakan klik link – link berikut :

api-writing

IBM – Intro to API

Allwrite-Design

Computerworld

Apidesign.org

Wikipedia

]]> http://smartcapp.wordpress.com/2009/02/19/what-is-api/feed/ 2 smartcapp api http://smartcapp.wordpress.com/2009/02/14/capp-from-npd-solutionscom/ http://smartcapp.wordpress.com/2009/02/14/capp-from-npd-solutionscom/#comments Sat, 14 Feb 2009 17:07:17 +0000 smartcapp http://smartcapp.wordpress.com/?p=112 ]]> Introduction

Process planning translates design information into the process steps and instructions to efficiently and effectively manufacture products. As the design process is supported by many computer-aided tools, computer-aided process planning (CAPP) has evolved to simplify and improve process planning and achieve more effective use of manufacturing resources.

Process Planning

Process planning encompasses the activities and functions to prepare a detailed set of plans and instructions to produce a part. The planning begins with engineering drawings, specifications, parts or material lists and a forecast of demand. The results of the planning are:

• Routings which specify operations, operation sequences, work centers, standards, tooling and fixtures.This routing becomes a major input to the manufacturing resource planning system to define operations for production activity control purposes and define required resources for capacity requirements planning purposes.
• Process plans which typically provide more detailed,step-by-step work instructions including dimensions related to individual operations, machining parameters, set-up instructions, and quality assurance checkpoints.
• Fabrication and assembly drawings to support manufacture (as opposed to engineering drawings to define the part).

Manual process planning is based on a manufacturing engineer’s experience and knowledge of production facilities,equipment, their capabilities, processes, and tooling. Process planning is very time-consuming and the results vary based on the person doing the planning.

Computer Aided Process Planning

Manufacturers have been pursuing an evolutionary path to improve and computerize process planning in the following five stages:

Stage I – Manual classification; standardized process plans
Stage II – Computer maintained process plans
Stage III – Variant CAPP
Stage IV – Generative CAPP
Stage V – Dynamic, generative CAPP

Prior to CAPP, manufacturers attempted to overcome the problems of manual process planning by basic classification of parts into families and developing somewhat standardized process plans for parts families (Stage I). When a new part was introduced, the process plan for that family would be manually retrieved, marked-up and retyped. While this improved productivity, it did not improve the quality of the planning of processes and it did not easily take into account the differences between parts in a family nor improvements in production processes.

Computer-aided process planning initially evolved as a means to electronically store a process plan once it was created, retrieve it, modify it for a new part and print the plan (Stage II). Other capabilities of this stage are table-driven cost and standard estimating systems.

This initial computer-aided approach evolved into what is now known as “variant” CAPP. However, variant CAPP is based on a Group Technology (GT) coding and classification approach to identify a larger number of part attributes or parameters. These attributes allow the system to select a baseline process plan for the part family and accomplish about ninety percent of the planning work. The planner will add the remaining ten percent of the effort modifying or fine-tuning the process plan. The baseline process plans stored in the computer are manually entered using a super planner concept,that is, developing standardized plans based on the accumulated experience and knowledge of multiple planners and manufacturing engineers (Stage III).

The next stage of evolution is toward generative CAPP (Stage IV). At this stage, process planning decision rules are built into the system. These decision rules will operate based on a part’s group technology or features technology coding to produce a process plan that will require minimal manual interaction and modification (e.g., entry of dimensions).

While CAPP systems are moving more and more towards being generative, a pure generative system that can produce a complete process plan from part classification and other design data is a goal of the future. This type of purely generative system (in Stage V) will involve the use of artificial intelligence type capabilities to produce process plans as well as be fully integrated in a CIM environment. A further step in this stage is dynamic, generative CAPP which would consider plant and machine capacities, tooling availability, work center and equipment loads, and equipment status (e.g., maintenance downtime) in developing process plans.

The process plan developed with a CAPP system at Stage V would vary over time depending on the resources and workload in the factory. For example, if a primary work center for an operation(s) was overloaded, the generative planning process would evaluate work to be released involving that work center,alternate processes and the related routings. The decision rules would result in process plans that would reduce the overloading on the primary work center by using an alternate routing that would have the least cost impact. Since finite scheduling systems are still in their infancy, this additional dimension to production scheduling is still a long way off.

Dynamic, generative CAPP also implies the need for online display of the process plan on a workorder oriented basis to insure that the appropriate process plan was provided to the floor. Tight integration with a manufacturing resource planning system is needed to track shop floor status and load data and assess alternate routings vis-a-vis the schedule.Finally, this stage of CAPP would directly feed shop floor equipment controllers or, in a less automated environment,display assembly drawings online in conjunction with process plans.

CAPP Planning Process

The system logic involved in establishing a variant process planning system is relatively straight forward – it is one of matching a code with a pre-established process plan maintained in the system. The initial challenge is in developing the GT classification and coding structure for the part families and in manually developing a standard baseline process plan for each part family.

The first key to implementing a generative system is the development of decision rules appropriate for the items to be processed. These decision rules are specified using decision trees, computer languages involving logical “if-then” type statements, or artificial intelligence approaches with object-oriented programming.

The nature of the parts will affect the complexity of the decision rules for generative planning and ultimately the degree of success in implementing the generative CAPP system.The majority of generative CAPP systems implemented to date have focused on process planning for fabrication of sheet metal parts and less complex machined parts. In addition, there has been significant recent effort with generative process planning for assembly operations, including PCB assembly.

A second key to generative process planning is the available data related to the part to drive the planning. Simple forms of generative planning systems may be driven by GT codes. Group technology or features technology (FT) type classification without a numeric code may be used to drive CAPP. This approach would involve a user responding to a series of questions about a part that in essence capture the same information as in a GT or FT code. Eventually when features-oriented data is captured in a CAD system during the design process, this data can directly drive CAPP.

CAD/CAM Integration and CAPP Features

A frequently overlooked step in the integration of CAD/CAM is the process planning that must occur. CAD systems generate graphically oriented data and may go so far as graphically identifying metal, etc. to be removed during processing. In order to produce such things as NC instructions for CAM equipment, basic decisions regarding equipment to be used,tooling and operation sequence need to be made. This is the function of CAPP. Without some element of CAPP, there would not be such a thing as CAD/CAM integration. Thus CAD/CAM systems that generate tool paths and NC programs include limited CAPP capabilities or imply a certain approach to processing.

CAD systems also provide graphically-oriented data to CAPP systems to use to produce assembly drawings, etc. Further,this graphically-oriented data can then be provided to manufacturing in the form of hardcopy drawings or work instruction displays. This type of system uses work instruction displays at factory workstations to display process plans graphically and guide employees through assembly step by step. The assembly is shown on the screen and as a employee steps through the assembly process with a footswitch, the components to be inserted or assembled are shown on the CRT graphically along with text instructions and warnings for each step.

If NC machining processes are involved, CAPP software exists which will select tools, feeds, and speeds, and prepare NC programs.

CAPP Benefits

Significant benefits can result from the implementation of CAPP. In a detailed survey of twenty-two large and small companies using generative-type CAPP systems, the following estimated cost savings were achieved:

• 58% reduction in process planning effort
• 10% saving in direct labor
• 4% saving in material
• 10% saving in scrap
• 12% saving in tooling
• 6% reduction in work-in-process

In addition, there are intangible benefits as follows:

• Reduced process planning and production leadtime; faster response to engineering changes
• Greater process plan consistency; access to up-to-date information in a central database
• Improved cost estimating procedures and fewer calculation errors
• More complete and detailed process plans
• Improved production scheduling and capacity utilization
• Improved ability to introduce new manufacturing technology and rapidly update process plans to utilize the improved technology

Summary

CAPP is a highly effective technology for discrete manufacturers with a significant number of products and process steps. Rapid strides are being made to develop generative planning capabilities and incorporate CAPP into a computer-integrated manufacturing architecture. The first step is the implementation of GT or FT classification and coding. Commercially-available software tools currently exist to support both GT and CAPP. As a result, many companies can achieve the benefits of GT and CAPP with minimal cost and risk. Effective use of these tools can improve a manufacturer’s competitive advantage.

Note : I Use Visual Studio 2005

1. Buat project dan form baru pada Visual Studio.

2. Drag 2 buah text box dan beri nama txtDiameter dan txtTinggi

3. Drag button dan beri nama btDraw

4. Pada solution explorer, klik kanan project anda dan pilih

add reference.

5. Pilih COM dan cari library Solidworks 2008 Type Library dan Solidworks 2008 Constant Type Library

6. Kemudian ketik listing berikut :

Imports SldWorks

Imports SwConst

Public Class FrmCAPP

Private Sub btDraw_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btDraw.Click

Dim swApp As Object

Dim Part As Object

Dim diameter As Double

Dim tinggi As Double

‘Definisi Diameter dan Tinggi

diameter = CDbl(txtDiameter.Text) / 1000

tinggi = CDbl(txtTinggi.Text) / 1000

‘Koneksi ke Solidworks

swApp = New SldWorks.SldWorks()

Part = swApp.ActiveDoc

‘Membuat Part di Solidworks

Part.SketchManager.InsertSketch(True)

Part.CreateCircleByRadius2(0, 0, 0, diameter / 2)

Part.FeatureManager.FeatureExtrusion2(True, False, False, 0, _

0, tinggi, 0, False, False, False, False, 0.01745, _

0.01745, False, False, False, False, 1, 1, 1, 0, 0, False)

End Sub

Private Sub btExit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btExit.Click

Close()

End Sub

7. Bukalah program Solidworks 2008

8. Running program…

Rekayasa sistem adalah kumpulan konsep, pendekatan dan metodologi, serta alat-alat bantu (tools) untuk merancang dan menginstalasi sebuah kompleks sistem. Kompleksitas sistem bisa diakibatkan karena 2 hal yaitu kompleksitas dinamis dan kompleksitas detail. Kompleksitas detail ketika komponen atau sub-sistem yang dirancang tidak hanya banyak tetapi ditambah pula dengan multi-sourcing (multi suplier), multi standard, multi criteria dan lainnya.

Rekayasa sistem dewasa ini, terutama di Amerika, lekat dengan dunia militer, karena produk-produk militer memang memiliki kriteria akan kompleksitas detail seperti ini, misalnya pesawat tempur, kapal induk, sistem pertahanan rudal patrior dsb, dimana timbul kombinasi yang kompleks antara sub-sistem mekanis, sub-sistem elektronik dan sub-sistem manusia.

Disiplin ilmu sistem engineering sendiri dewasa ini sedang berevolusi untuk mencari jati diri. Sebagian besar masih bergabung dengan bidang ilmu lainnya seperti biologi, teknik industri, teknik komputer, teknik kimia (instalasi sebuah processing plant membutuhkan skill rekayasa sistem).[Hid07]

Dalam lingkup pengembangan perangkat lunak, rekayasa Sistem adalah kegiatan untuk menentukan spesifikasi, perancangan, pengimplementasian, penyebaran, dan pemeliharaan sistem sebagai satu kesatuan. Sehingga, rekayasa sistem atau lebih tepatnya, rekayasa sistem berbasis komputer berhubungan dengan semua aspek pengembangan dan evolusi sistem kompleks dimana perangkat lunak memainkan peran utama. Rekayasa sistem merupakan disiplin yang lebih tua dibandingkan dengan rekayasa perangkat lunak. Orang telah melakukan spesifikasi dan perakitan sistem industri secara kompleks seperti kereta api dan pabrik kimia selama lebih dari 100 tahun. Akan tetapi, seiring dengan bertambahnya persentase perangkat lunak pada sistem, maka teknik rekayasa perangkat lunak seperti pemodelan use – case, manajemen konfigurasi, dan lain sebagainya sering dipergunakan dalam proses rekayasa sistem [Som01].

Sommerville mendefinisikan sistem sebagai sekumpulan komponen yang saling berhubungan dan bekerja sama untuk mencapai tujuan. Definisi umum ini mencakup banyak jenis sistem. Sebagai contoh, sistem yang sederhana seperti sistem pencatatan skor mungkin hanya terdiri dari 2 atau 3 modul perangkat lunak. Sebaliknya, sistem kontrol lalu lintas dapat terdiri dari ratusan perangkat lunak dan keran, ditambah manusia sebagai pemakainya, yang membuat keputusan berdasarkan informasi dari sistem [Som01].

Sistem seringkali hierarkis, dimana bahwa mereka mencakup sistem – sistem lain. Sebagai contoh, sistem perintah dan kendali polisi mungkin melibatkan sistem informasi geografis untuk memberikan detail lokasi suatu peristiwa. Sistem – sistem lain inilah yang disebut sebagai subsistem. Karakteristik subsistem adalah kemampuannya untuk berinteraksi secara independen. Dengan demikian, beberapa sistem informasi geografis dapat dipakai pada sistem lain. Namun demikian, perilakunya pada sistem tertentu bergantung pada subsistem lain. Adanya hubungan yang kompleks dalam sistem inilah yang membuat rekayasa perangkat lunak merupakan bagian dari rekayasa sistem berbasis komputer mengingat pentingnya perangkat lunak pada sebuah sistem [Som01].

Pressman menyebut sistem yang didalamnya terdapat perangkat lunak sebagai sistem berbasis komputer. Pada sistem berbasis komputer terdapat komponen – komponen sebagai berikut :

1. Perangkat Keras (Hardware)

2. Orang (People)

3. Perangkat Lunak (Software)

4. Basis Data (Database)

5. Prosedur (Procedure)

6. Dokumentasi

Pada dasarnya, dari keenam komponen pembentuk sistem berbasis komputer, empat komponen terakhir diatas merupakan hasil aktivitas rekayasa perangkat lunak. Perangkat lunak sendiri terdiri dari artifak – artifak hasil rekayasa perangkat lunak yang merupakan hasil dari aktivitas proses rekayasa (pengembangan) sistem berbasis komputer [Pre05]

Ref :

[Pre05] Pressman, Roger.S (2005). Software Engineering : A Practitioner’s Approach 6^th Edition. McGraw – Hill International Edition. Singapore

[Som01] Sommerville, Ian (2001). Software Engineering : Jilid 1 & 2 Edisi 6. Penerbit Erlangga. Jakarta. Indonesia

http://hidayatno.wordpress.com/category/systems-engineering/