Selasa, Agustus 04, 2009

Reliability (Terusan Kemarin)

Lagi asyik nulis pengenalan reliability kemarin dah harus boarding... yah itulah gaya hidup yang terpaksa kujalani... kata mbah buyut-buyut koe doeloe..."I'm leeeeaaaaving on the jet plane... don't know when I'll be back again.... oooooh babe I had to goooooouuwww"... hush koq ngelantur seh


Kembali kee.... Laaaaapppppp...... (sencored... punya Tuqul)... rejeki orang

Buka-buka catatan jaman dahoeloe kala eighhh terbuka tentang reliability... uuugghhhh kenapa seh reliability lage... biar deh terus yah.
Dahoeloe kala pada hari senin 10 Agustus 2009 ( kalo gak percaya buka kalender pasti bener tanggalnya soale ada di notes koe...he..he.) di negeri yang bernama Soerabaja ada sebuah airlines dimana calon pendekar sedang digodog untuk menjadi ahli dalam engineering management (katanya seh), salah seorang diantara sedang tequn membaca buku "Basic Course of Aviation Technology"... wuih keren buanget... padahal waktu itu hanya "Killing time" soale gak dikasih kerjaan apa-apa... Ja'im biar keliatan qeren jadi baca buku english.


Tepatnya di chapter 3 tertulis banyak mengenai reliability, but I'll make a short sentence 4U guyz... biar gaul dikit..... ringkasannya aja yah ... this is cropped from my diary in blue kolor (lah diary koq isinya ginian..? bodo ah jangan ada yang komen)


Typical system used in reliability control are :

1. Data collection
2. Data analysis systems
3. Corrective action system
4. Performance standards
5. Data display and report
6. Maintenance interval adjustment and process change
7. Program revision

1. Data collection

  • Pilot report (Pireps)
  • In-Flight engine performance data
  • Mechanical interruptions /delays
  • Engine shutdowns
  • Unschedule removals
  • Confirmed Failures
  • Functional Checks
  • Bench checks
  • Shop findings
  • Sampling inspections
  • Inspection write-ups
  • Service Difficulty Reports
2. Data analysis Systems

  • Is a process of evaluating mechanical performance data to identify characteristics indicating a need for program adjustment, revision of maintenance practices, hardware improvement (modification) etc.
  • Program incorporating statistical performance standard (alert type program), example : delay/100 departures. This program can accommodate "Condition Monitoring" process
  • Program using other analysis standards (Non alert type program), example: incident report, engine monitoring report
  • Summary, the objective of data analaysis is to :

  1. Recognize the need for corrective action
  2. establish what corrective action is needed
  3. Determine the effectiveness of that action


3. Corrective action system

  • Is action taken to restore performance to an acceptable level within a reasonable time.
  • This system should provide periodic feedback until such time of performance has reached an acceptable level

4. Performance standards
  • Lupa nyatet... cari sendiri yah... gitu aja koq muangkel cari yah.. jangan takut anda pasti bisa

5. Data display and report
  • Mechanical interruption summary
  • Mechanical reliability report
  • Listing of all maintenance process and interval assignment (Master specification)
  • Weekly update to letter (c) above
  • Daily repetitive item listing
  • Monthly component premature removal report (include removal rate)
  • Monthly engine shutdown and removal report
  • Quarterly engine reliability analysis report
  • Engine threshold adjustment report
  • Worksheet for maintenance process and interval changes
6. Maintenance interval adjustment and process change system
  • Typical considerations for adjusting hard time and on-condition interval are : sampling, actuarial studies, unit performance, inspector or shop findings, pilot report
  • The system should includes procedures for initial classification of maintenance process (HT, OC & CM) and for change from one process to another. If should also include authority and procedure changing maintenance specification and related documents to reflect the interval adjustment or primary process change.
7. Program revision
If should include a procedure for revision which is compatible with Airworthiness Authority approvals. The procedure should identify organizational element involved in the revision process and their authority.
The program areas requiring formal Airworthiness approval includes any change to the programabove :
  1. Procedures relating to reliability measurement/performance standard
  2. Data collection system
  3. Data analysis methods and application to the total maintenance program
  4. Process changes : Alert type program & Non alert type program
  5. Adding or delating components/system
  6. Adding or deleting Aircraft type
  7. All procedure and organizational changes concerning administration of the program
Program Administration
Form should be used, as necessary, to facilitate and document recurring transactions that involve element such as :
  • Change form one maintenance process to another
  • Analysis of substandard system or component mechanical performance
  • Shop disassembly analysis for condition monitoring purposes or overhaul frequency adjustment, etc
  • Sampling inspection for A/C check or inspection adjustment
Reliabilty Program Document, should include :
  • General description of the program
  • Organizational structure, duties and responsibilities
  • Description of the individual systems
  • Derivation of performance standard (if used)
  • Change to the program including designition of changes requiring Airworthiness Authority Approval
  • Copy and explanation of all forms peculiar to the system
  • Revision control and certification of revision to the document
Program approval
  • Initial approval, Airworthiness aouthority form, operation specification are used for initial approval of relibility programs. This form, along with the program documents and related data should be submitted to the airworthiness authority office assigned responsibility for the operator. Approval will be certified in the program document in addition to the operation specification.
  • Revision approval, Revision requiring formal approval will be subject to the same consideration as initial approval. The mechanics of the approval certification will be as defined in the document. If the revision concerns item listed in the operations specifications, the effective page (s) will be amended to reflect the revision.
Habiiiiiisssss........ Belajar lanjutannya nantiiiiiiii sabaaar nunggu mood dulu yach nanti sampe juga ke hitungan..... kecuali anda berminat memberikan bahan.... _^^_

Naaah tuh Bapak-Bapak meknik or engineer yang terhormat.... begitu besarnya andil kerja kita yang kecil hanya dengan mencatat dengan benar apa yang kita lepas (removed) dan pasang (installed) terhadap kelanjutan perawatan pesawat dimasa mendatang (baca: anak cucu kita nanti)..... keteledoran kita dalam mencatat dengan benar akan berakibat sangat fatal terhadap data-data yang dihitung (belajar ngitungnya nanti) oleh teori diatas... istilah anakku..."Basi itu sih"

Ini bukannya ngomelin loch... berdasarkan pengalaman emang sangat njengkelin kalau harus traceback kesalahan catat or simpan record... amit-amit dah jangan sampe terulang lagi ketika giliran anda di temptakan di reliability or PPC harus metani kecerobohan yang seharusnya sangat simple untuk dihindari.... Udah ah dah malem gak patut ngomel terus... met tidur

Cheers
Otnaira

Tidak ada komentar:

Posting Komentar

Apa Pendapat Anda Mengenai Tulisan Diatas....?
Jangan Ragu Untuk Menuliskannya.... Nothing To Affraid Of... just type it

Tukang Ketiknya Adalah

Dunia Penerbangan Sudah Melekat Sejak Daqu Dilahirkan Tulisan Dalam Blog Ini Yang Based On True Story Akan Berkisar Pada:
1. Engineering
2. Material
3. PPC
4. Hangar
5. WorkShop
6. Quality
Selebihnya Adalah Curahan Isi Kepala Yang Tak Memiliki Tempat Lagi Di Dunia Nyata Sehingga Harus Mampir Di Dunia Maya Ini Baca Bismillah Sebelum Membaca..... Selamat Membaca

Pengikut