1 Pertemuan 22 Analisis Studi Kasus 2 Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1.

Slides:



Advertisements
Presentasi serupa
Managing Software Requirements (manajemen kebutuhan perangkat lunak)
Advertisements

Chapter 10 Marketing.
PERKEMBANGAN DEFINISI TEKNOLOGI PENDIDIKAN
Roesfiansjah Rasjidin Program Studi Teknik Industri Fakultas Teknik – Univ. Esa Unggul.
1 DATA STRUCTURE “ STACK” SHINTA P STMIK MDP APRIL 2011.
KONSEP STRATEGI BISNIS DAN IMPLIKASINYA PADA STRATEGI IS/IT
Matakuliah : M0086/Analisis dan Perancangan Sistem Informasi
BLACK BOX TESTING.
ANALISIS STRATEGIS: MENENTUKAN POTENSI MASA MENDATANG MODUL 6 PERT. 19 S/D 21.
Bina Nusantara Model Simulasi Peretemuan 23 (Off Clas) Mata kuliah: K0194-Pemodelan Matematika Terapan Tahun: 2008.
Testing Implementasi Sistem Oleh :Rifiana Arief, SKom, MMSI
1 Pertemuan 09 Kebutuhan Sistem Matakuliah: T0234 / Sistem Informasi Geografis Tahun: 2005 Versi: 01/revisi 1.
1 Pertemuan 12 Pengkodean & Implementasi Matakuliah: T0234 / Sistem Informasi Geografis Tahun: 2005 Versi: 01/revisi 1.
Pendugaan Parameter Proporsi dan Varians (Ragam) Pertemuan 14 Matakuliah: L0104 / Statistika Psikologi Tahun : 2008.
1 Pertemuan 10 Statistical Reasoning Matakuliah: T0264/Inteligensia Semu Tahun: Juli 2006 Versi: 2/1.
Masalah Transportasi II (Transportation Problem II)
1 Pertemuan 21 Function Matakuliah: M0086/Analisis dan Perancangan Sistem Informasi Tahun: 2005 Versi: 5.
Bina Nusantara Mata Kuliah: K0194-Pemodelan Matematika Terapan Tahun : 2008 Aplikasi Model Markov Pertemuan 22:
1 Pertemuan 2 Unit 1 - Careers Matakuliah: G0682 / Bahasa Inggris Ekonomi 1 Tahun: 2005 Versi: versi/revisi.
Perencanaan Pengujian (Test Plan) Pertemuan 4
1 Pertemuan 8 JARINGAN COMPETITIVE Matakuliah: H0434/Jaringan Syaraf Tiruan Tahun: 2005 Versi: 1.
1 Pertemuan 11 The Manipulative part of the object data model (Lanjutan bagian 2) Matakuliah: M0174/OBJECT ORIENTED DATABASE Tahun: 2005 Versi: 1/0.
1 Pertemuan #3 Probability Distribution Matakuliah: H0332/Simulasi dan Permodelan Tahun: 2005 Versi: 1/1.
1 Pertemuan 6 Hubungan WCA dan Sistem Informasi Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
1 Pertemuan 11 Indikator Trend Matakuliah: F0392/Simulasi Perdagangan di Bursa Efek Tahun: 2005 Versi: 1/3.
1 Pertemuan 24 Contingency Planning Matakuliah:A0334/Pengendalian Lingkungan Online Tahun: 2005 Versi: 1/1.
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 11 Function dari System Matakuliah: M0446/Analisa dan Perancangan Sistem Informasi Tahun: 2005 Versi: 0/0.
1 Pertemuan 13 Algoritma Pergantian Page Matakuliah: T0316/sistem Operasi Tahun: 2005 Versi/Revisi: 5.
Materi. Introduction In this discussion the appliaction of maintainability to the design process is addressed. The maintainability design process is similar.
Pasar Faktor Produksi.
1 Pertemuan 13 Pemilihan strategi sistem informasi yang mendukung perkembangan bisnis Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
1 Pertemuan 25 QUIZ Matakuliah: J0274/Akuntansi Manajemen Tahun: 2005 Versi: 01/00.
13 Akuntansi Biaya Activity Based Costing
Inventory System Simulation Pemodelan Sistem. Kapan saat yang tepat untuk meng- order? Berapa banyak yang perlu di-order? Inventory Systems.
1 Pertemuan 17 Pengaruh perkembangan teknologi dalam usaha perjalanan wisata Matakuliah: G1174/Tourism Management and Planning Tahun: 2005 Versi: 1/R0.
1 INTRODUCTION Pertemuan 1 s.d 2 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
Keuangan dan Akuntansi Proyek Modul 2: BASIC TOOLS CHRISTIONO UTOMO, Ph.D. Bidang Manajemen Proyek ITS 2011.
Using Course-view to Enhance our Course Design
EIS (Executive Information Systems)
proses PERANGKAT LUNAK
Pert. 16. Menyimak lingkungan IS/IT saat ini
PEMILIHAN SISTEM.
Matakuliah : R0124 / Teknik Komunikasi Arsitektur
Pengujian Hipotesis (I) Pertemuan 11
Matakuliah : I0014 / Biostatistika Tahun : 2005 Versi : V1 / R1
CA113 Pengantar Manajemen Bisnis
Pertemuan <<18>> << Penemuan Fakta(01) >>
Pertemuan 2 Konsep Kehandalan Sistem
Sistem manajemen logistik & produksi isg3e3
Pengantar Bisnis 7 Sessi.
Pendugaan Parameter (II) Pertemuan 10
CA113 Pengantar Manajemen Bisnis
EIS (Executive Information Systems)
13-1 Lecture slides to accompany Engineering Economy 7 th edition Leland Blank Anthony Tarquin Chapter 13 Breakeven and Payback Analysis © 2012 by McGraw-Hill.
Phase III Rapid Prototyping and Demonstration Prototype
Modul 1 SISTEM PENDUKUNG PENGAMBILAN KEPUTUSAN
Pertemuan 13 Analisis kehandalan sistem 1
Manajemen Proyek Perangkat Lunak (MPPL)
Rekayasa Perangkat Lunak Part-5
Master data Management
Pertemuan 5 Computer Components
Pertemuan 21 dan 22 Analisis Regresi dan Korelasi Sederhana
Evidence-Based Medicine Prof. Carl Heneghan Director CEBM University of Oxford.
CA113 Pengantar Manajemen Bisnis
IMPLEMENTASI PERENCANAAN
Design for Reliability (12) & Design for Maintainability (13) Group 6 -Sudarmono -Irwan Setyaji -Pitarsono Yulihartanto -Subur Priyono.
Pertemuan 6 Mappa Panglima Banding. 2 COST DRIVER: Definition Is a factor that causes, “drives,” an activity’s costs. LO 4.
A SHORT ESSAY OF CIVIL ENGINEERING BY : ALFATIHATU RAHMI CIVIL ENGINEERING ENGINEERING FACULTY ANDALAS UNIVERSITY PADANG.
Wednesday/ September,  There are lots of problems with trade ◦ There may be some ways that some governments can make things better by intervening.
Transcript presentasi:

1 Pertemuan 22 Analisis Studi Kasus 2 Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1

2 Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Menghubungkan antara repair system dengan discard system

3 Outline Materi Repair versus Discard EvaluationStudi kasus : Repair versus Discard Evaluation

4 Studi Kasus 2 : Repair versus Discard Evaluation Bacalah studi kasus berikut ini In expanding the maintenance concept to establish criteria for equipment design, it is necessary to determine whether it is economically feasible to repair certain assemblies or to discard them when failures occur. If the decision is to accomplish repair, it is appropriate to determine the maintenance level at which the repair should be accomplished (i.e. intermediate maintenance or supplier/ depot maintenance). Suppose that a computer system will be distributed in quantities of 65 throughout three major geographical areas. The system will be utilized to support both scientific and management functions within various industrial firms and government agencies. Although the actual system utilization will vary from one consumer organization to the next, an average utilization of 4 hours per day (for a 360-day year) is assumed.

5 Studi Kasus 2 : Repair versus Discard Evaluation The computer system is currently in the early development stage, should be in production in 18 months, and will be operational in 2 years. The full complement of 65 computer systems is expected to be in use in 4 years and will be available through the eight year of the program before system phase out commences. The system life cycle, for the purposes of the analysis, is 10 years. Based on early design data, the computer system will be packaged in major units with a built-in test capability that will isolate faults to the unit level. Faulty unit will be removed and replaced at the organizational level (i.e comsumer’s facility), and sent to the intermediate maintenance shop for repair. Unit repair will be accomplished through assembly replacement, and assemblies will be either repaired or discarded. There is a total of 15 assemblies being considered, and the requirement is to justify the assembly repair or discard decision on the basis of life-cycle-cost criteria.

6 Studi Kasus 2 : Repair versus Discard Evaluation The stated problem primarily pertains to the analysis of 15 major assemblies of the given computer system configuration to determine whether the assemblies should be repaired or discarded when failures occur. In other words, the various assemblies will be individually evaluated in terms of (1) assembly repair at the intermediate level of maintenance, (2) assembly repair at the supplier or depot level of maintenance, and (3) disposing of the assembly. Life-cycle costs, as applicable to the assembly level, will be developed and employed in the alternative selection process. Total overall computer system costs have been determined at a higher level, and are not included in this example. The objective is to be consistent in analysis approach and in the use of input cost factors to the maximum extent possible and where appropriate.

7 Studi Kasus 2 : Repair versus Discard Evaluation The summary results for all 15 assemblies are presented in table 22.1 Assembly Number Maintenance StatusDecision Repair at Intermediate Cost ($) Repair at Supplier Cost ($) Discard at failure Cost ($) A - 1 A - 2 A - 3 A - 4 A - 5 A - 6 A - 7 A - 8 A - 9 A - 10 A - 11 A - 12 A - 13 A - 14 A ,665 58,149 85,115 85,778 66,679 65,101 72,223 89,348 78,762 63,915 67,001 69,212 77,101 59,299 71,919 64,952 51,341 81,544 78,972 61,724 72,988 75,591 78,204 71,444 67,805 66,158 71,575 65,555 62,515 65, , ,611 73,932 65,071 95,108 89,216 92,114 76,222 89,875 97,212 64,229 82,109 83,219 62,005 63,050 Repair – intermediate Repair – Supplier Discard Repair – Supplier Repair – intermediate Discard Repair – Supplier Repair – intermediate Discard Repair – intermediate Repair – Supplier Repair – intermediate Discard Policy Cost1,071,2671,035,6121,343,449

8 TUGAS / Diskusi Dari data yang diberikan, Buatlah model operational requirement, maintenance concept, and program plan Berikan rekomendasi untuk setiap item (dari A-1 sampai A-15) dalam mempertimbangkan maintenance cost Menurut anda, pilihan mana yang terbaik dari ketiga alternatif biaya perbaikan (maintenance cost), dan mengapa pilihan tersebut yang anda pilih. Diskusikan dalam kelompok dan kemudian dipresentasikan pada pertemuan berikutnya