Trouble History Database of HIMAC Current Status and
Trouble History Database of HIMAC ~ Current Status and Future Plan ~ 28. SEP. 2007 WAO 2007@Trieste, Italy T. Kadowaki (Accelerator Engineering Corporation)
0: Contents 1: Introduction * About HIMAC * Purpose of Trouble History Database 2: Current Trouble History Database * Current Status * Example * Merit and Limitation 3: Future Plan * Improvement Plan 4: Summary
1: Introduction 1 -1: About HIMAC SYN INJ HEBT Chiba Pref. IRRD Beam direction
1 -2: Purpose of Trouble History Database How to Minimize the Down Time ? Trouble happen What kind of trouble ? Alarm message Device status Local control panel How to fix ? How long does it take to recover beam ? Inform beam user Log book Trouble reports Trouble history database Fix the failure parts
1 -3: Previous Status Clues how to fix the trouble - Past trouble reports - Old log books Difficult to search for past data Hard to find how to solve Necessity for easy way to search past solution Trouble History Database
2: Current Trouble History Database 2 -1: Schematic Diagram of Database WEB SERVER SYN DATA RESULT SEARCH Search CGI SEARCH CONDITION SETTING HEBT DATA Display CGI RESULT DISPLAY WEB Browser UPDATE Update CGI DATA UPDATE WEB Browser INJ DATA CORRECT Correct CGI DATA CORRECT WEB Browser
2 -2: Specification of Current System Server PC OS RAM CPU NEC Express 5800 Windows 2000 Professional SP 4 384 MB Pentium II 265 MHz Freeware httpd AN HTTP Daemon Ver. 1. 42 Perl Interpreter Active Perl 5. 8. 7 Trouble data as of Aug 2007 System development : 1 month / person Old data input : 6 month / 3 persons
2 -3: Example of Search Condition Setting Display Upper/Lower SYN Select Kind Select Date Select Status Select Down Time Select Run Search Magnet / Power supply Monitor Vacuum RF Computer Others All Completed(temporary) Wait for Repeat All
2 -4: Example of Search Result Display Date Operators Down time Failure Contents Failure Reason Solutions Others Failure device
2 -5: Example of Text Search Display Category Select Text Input Failure Device Failure Contents Failure Reason Solutions Others All
2 -6: Actual Status * Introduced since 2005 (for INJ, since 2006) * SYN/HEBT data contain past 10 years trouble data Accumulate know-how and experience of experts * Operators use this system as Trouble shooting tool Trouble statistic analyze tool
2 -7: Merit and Limitation • Merit • Quick search for past trouble solutions • Simultaneous access from some clients • Reuse for trouble reports • Limitation • Not automatically updated • Not opened for external network
3: Future Plan 3 -1: To Be Improved • Upload pictures • Inform a trouble to operators automatically by E-mail • Update trouble database automatically • Open for external network • Construct the way to follow up the improvement status of failure parts
3 -2: Improvement Plan Check solution Operator Hardware manufacturer Send E-mail Internet TROUBLE DB ( as WEB Server and Mail Server) Report repair status LAN Send alarm message Update trouble information Control System Operator Search solution
4: Summary • We have introduced a trouble history database since 2005 • Operators use this system as useful trouble shooting tool • We are planning to add some functions * Automatic trouble E-mail information * Follow up the improvement status Need to open for external network
2 -2: Current System (since 2005) * WEB Server and Client System Server PC : NEC Express 5800(Windows 2000) WEB Server Program : AN HTTP Daemon Ver. 1. 42 n Perl Interpreter : Active Perl 5. 8. 7 WEB SERVER INJ DATA Data search CGI WEB Client SYN DATA HEBT DATA Data commit CGI WEB Client
1 -2: Purpose of Trouble History Database Date Reasons Devices …… Solutions Can Be Used for Trouble Shooting Our Goal
1 -2: Purpose of Trouble History Database How to minimize the Down Time ? Trouble happen What kind of trouble ? Alarm message Device status etc. How to fix ? How long does it take to recover beam ? Inform beam user Log book Trouble reports Trouble history database Fix the failure parts
2 -4: Example of Trouble Input Display Device Kind Device Name Operator's Name Failure Contents Down Time Status Failure Reason Solutions Others Submit
3 -2: New Trouble Database Check solution Input comment Medical physicist TROUBLE DB Update trouble information Search solution Report repair status Check down time in similar trouble Operator Check solution Radiation therapy technologist Hardware manufacture
3 -2: Integration with Other Databases UNIFIED DATABASE Create trouble report Document DB Operation manual Trouble report Technical document Create improvement report Refer Trouble DB Trouble history Trouble solution, etc. Create proposal Improvement DB Proposal, etc.
- Slides: 21