1. Raise Immediate Action job card Record fault description Record repair details Include switch, valve, component numbers Etc. Start and end date & time Recorded On Job Card Immediate Action Request for maintenance Job Card Nr: mainttobe Equipment Name: Requested by: Equipment Number: Equipment Location: dd/mm/yy hh:mm Date and Time requested: Cost Centre: Fault Description: Containment Action: Name: Sign: Work Completed Date and Time: Maintenance Start Date & Time: Maintenance End Date & Time: Breakdown Maintenance Process Date & Time Recorded on production sheet Fix it Date & Time Recorded On Job Card Breakdown event Quick Fix Yes Production Operator/supervisor Investigate fault MaintenanceTeam Repair fault No Production sign Off on job Card recording date and time Machine stopped in cycle during clamping Notes: I built an MS Access database which uses the “DateDiff” function in a query, to calculate the time lapsed between the production “Date and Time requested” and the “Work completed date and time” This function is also used for the maintenance start - end times. I have found that this gives a more accurate Downtime Vs. Repair time comparison. It’s more reliable than getting people to record when events or actions start and end. Proximity switch 6b2 not made – Adjusted actuator And tested Capture Job card infoon Database Analyse data Corrective actions Modifications Modify TPM Checks or Actions The job card field design and field names are flexible. Use whatever works in with currently used processes. The only fields I recommend sticking to, are the ‘date, time’ fields and only because MS Access can calculate time lapsed based on date and time, in the same field.

2. Fig 1 Breakdown Analysis Using MS Access Queries in Pivot chart view to analyse breakdowns Fig 2 With production and maintenance completing the date and time fields on the job card and capturing this information in the database, it becomes possible to get a more accurate reflection of “Repair time” Vs “Downtime” (Fig 1) This chart enables maintenance personnel to see which machine had the most breakdowns for a given period. the next step would be to view the “Detail Report” which I have also built into the database to look at data for the same period. This way one can see exactly what the reasons were for the downtime. With this kind of information available the maintenance team will be able to determine whether corrective work or a modification can be done to reduce downtime. The “Fault Code chart” (Fig 2) offers the opportunity to analyse “Repair Time” and “Downtime” by fault code (causes). A line or even an specific machine can be selected within the chart to help narrow down route causes. This also helps when formulating “fixes” and modifications. An important benefit of cause analysis is that you can fine tune TPM inspections and actions. In the breakdown flow chart, we used a proximity switch example. In the chart above the code PRX (Proximity switch) is the highest cause of downtime. We can now decide to inspect the switch on a time based interval to ensure that the actuator is in the right place or even better redesign the actuator to ensure that it does not work loose. The point is, to reduce downtime for any given cause.