Implementasi Integer Programming dengan Algoritma Branch and Bound Menggunakan QM for Windows dalam Memaksimalkan Keuntungan di PT XYZ
Bibliographic record
Abstract
AbstractIn maximizing the profits to be obtained the company needs optimal production planning. The plan considers the resources of the company. PT XYZ is a furniture company. This research focuses on optimizing production planning on the manufacture of door products at PT. XYZ. There are several types of products issued in: D1 type door, D2 type door, D3 type door, and D4 type door. Production planning at PT. XYZ can be seen as an integer program model, which is a method related to optimizing resources to increase profits. Optimization is done by determining the amount of production for each type and each calculating existing resources. The solution search for this model is done by the Branch and Bound algorithm. Based on the calculation results using QM software for Windows, the amount corresponding to production is obtained by using Branches and Bound giving an increase of 36.5% compared to the acquisition of PT. XYZ before. Keywords: Branch and Bound Algorithms, Integer Programming,Optimization AbstrakDalam memaksimalkan keuntungan yang akan diperoleh perusahaan perlu adanya perencanaan produksi yang optimal. Perencanaan tersebut mempertimbangkan ketersediaan sumber daya pada perusahaan. PT XYZ merupakan perusahaan yang bergerak di bidang furniture. Penelitian ini fokus kepada pengoptimalan perencanaan produksi pada pembuatan produk pintu di PT.XYZ. Terdapat beberapa jenis produk yang diproduksi di antaranya: Pintu tipe D1, Pintu tipe D2, Pintu tipe D3, dan Pintu tipe D4. Perencanaan produksi di PT.XYZ ini dapat dikatakan sebagai model program integer, karena semua variabel menghendaki hasilnya berupa bilangan bulat. Program tersebut berhubungan dengan pengoptimalan ketersediaan sumber daya bertujuan untuk memaksimalkan keuntungan. Pengoptimalan yang dilakukan yaitu dengan menentukan jumlah produksi untuk masing-masing tipe serta mempertimbangkan semua ketersediaan sumber daya yang ada. Pencarian solusi untuk model ini dilakukan dengan algoritma Branch and Bound. Berdasarkan hasil perhitungan menggunakan software QM for Windows, diketahui bahwa penentuan jumlah produksi dengan menggunakan algoritma Branch and Bound memberikan peningkatan keuntungan sebesar 36.5% dibandingkan dengan keuntungan PT.XYZ sebelumnya. Kata kunci: Optimasi, program integer, algoritma Branch and BoundReferensi[1] Sofyan Assauri. Manajemen Produksi dan Operasi. Lembaga Penerbit FakultasEkonomi Universitas Indonesia. Jakarta. 2008.[2] Winston, W. L. Operations Research: Applications and Algorithms. Edisi Keempat.Canada: Brooks/Cole-Thomson Learning. 2004.[3] Akram, S. A., dan Jaya, A. I. Optimalisasi Produksi Roti dengan Menggunakan Metode Branch and Bound (Studi Kasus Pada Pabrik Roti Syariah Bakery, Jl. Maleo, Lrg.VIII No. 68 Palu). Jurnal Ilmiah Matematika dan Terapan, 13(2): 98-107. 2016.[4] Jiao, H. W., dkk. An Effective Branch and Bound Algorithm for MinimaxLinear Fractional Programming. Journal of Applied Mathematics, Volume 2014: 8. 2014.[5] Williams, H. P. The Problem with Integer Programming. Journal of Management Mathematics, 22(3): 213-230. 2011.[6] Falani, I. Penentuan Nilai Parameter Metode Exponential Smoothing dengan Algoritma Genetik dalam Meningkatkan Akurasi Forecasting. Journal of Computer Engineering System and Science, 3(1): 14–16. 2018.[7] Mehdizadeh, E., dan Jalili, S. An Algorithm Based on Theory of Constraints and Branch and Bound for Solving Integrated Product-Mix-Outsourcing Problem. Journal of Optimization in Industrial Engineering, 12(1): 167-172. 2019.[8] Taylor, B. W. Introduction to Management Science. Edisi ke-11. United States of America: Prentice-Hall International, INC. 2013[9] Puryani., dan Ristono, A. Penelitian Operasional. Yogyakarta: Graha Ilmu. 2012.[10] Yusrah N. dkk. Implementasi Algoritma Branch and Bound Dalam Penentuan Jumlah Produksi Untuk Memaksimalkan Keuntungan. Jurnal String Vol. 3 No. 1 Agustus 2018. ISSN: 2527-9661[11] Taha, H. A. Operations Research: An Introduction. Edisi ke-8. United States of America: Prentice-Hall International, INC. 2007.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.016 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".