1,2,4,5: Just the same

3) I am not an internal ISO Auditor (although I heard I was high on their wish list ) But I was in the ISO team of the Refinery. So I haver written procedures, helped with creating the process maps etc. The internal auditor never audits his own facility. I am always audited by someone from our other sites (headquarter, oilfield).
The external auditers are more experienced, but they are not doing it for free. When the process is in place they don't want to slaughter the chicken laying gold eggs, so you must find something.
It was a recommendation of the external audit to tie a time span to completion. But with that the ISO Clan doesn't have to look far to find something to look good

With the ISO clan I refer to internal philosophers

5) How is your KPI build up?

We call 1,2 reactive, the rest is planned

planned <60% red
60-80 yellow
>80 green
It is build in the CMMS, so people see it daily.
We evalute the mode for the current year, thus all maintenance jobs initiated in 2005 are computed

To tie time span to completion: If I understand what is wanted here correctly, this can be measured by comparing planned start-finish dates with actual start-finish dates.

However, not confuse this time span to completion with the response time to attend to work request by converting to work order.

We only consider PPM as planned works. Any incidental works are not planned works regdless of priority.

quote:

this can be measured by comparing planned start-finish dates with actual start-finish dates

I know, but my question is: do you actually have a number (target) written for the ISO Clan
Like: "I Declare that emergencies will be solved in 2 days"

You only consider PPM as planned, what about a shutdown that must be executed, and you know that 3 weeks in advance? Lets say a leaking soaker valve and the temporary fixes did not succeed? Management has decided to replace the valve on the next opportunity. You have time to mobilize cranes, scaffolds, craft, special services, machine shop etc..
If this job is planned on the fly, lets say with 2 days notice, I consider it reactive.

Declaration - No we never declare or ask to do so. I thought I already answer that the completion of emergencies especially with HSE and/or production loss depends on the complexity of the problem. See above. I think setting a target in this case is not realistic (SMART) because the target can vary from several hours to several years.

We consider only work orders generated from planned preventive maintenance (PPM) plans (prev maint, condition-based, inspection, shutdown overhauls) as planned because these are already declared upfront. The KPI will be Manhours spent on PPM works. Therefore in our case, any incoming incidental works will be excluded even though we do planning and scheduling for them but they will be captured under another KPI namely Jobs planned & scheduled (%).

quote:

We only consider PPM as planned works. Any incidental works are not planned works

versus

quote:

any incoming incidental works will be excluded even though we do planning and scheduling for them but they will be captured under another KPI namely Jobs planned & scheduled

not planned but enters in the KPI

Enron did the same