Posted By garyh This is not an easy thing to define, and even harder to make it workable. I was involved with a system for higher tier COMAH sites. If you are talking about COMAH sites then the COMAH report should have Id'd (for Higher tier sites) equipment which is critical, the failure of which could lead to an incident predicted in the Hazid. Thus your system could state than any COMAH safety critical equipment defects require specified action eg shut down, repair with period "X", Senior Manager to take action etc etc. Overall I would suggest that you need to ID defects in a defined hierarchy of seriousness, with an ID code eg 1234 or ABCD etc, also define what the required action is eg Cat A - must be repaired as soon as possible (shut down if not poss) Cat B - must be repaired as soon as possible Cat C - must be repaired withing 24 hrs Cat D - must be repaired within 7 days Cat E - must be repaired at next plant shutdown and so on. Each defect should be tracked (eg on a database - if you have an existing maintenance database such as Datastream this works OK). Each action should have the above on, and be assigned an action owner; regular (Monthly? Weekly?) reports should be published. Copies to man with executive Authority, name names! As an aside you can use a variation of this type of system to control regular mtce of safety critical items. If a database is not available, a colour coded spreadsheet etc works well and has the advantage of being visual - you can tell at a glance how things are going. (By this I mean that items status is tracked by coloured boxes alongside the wording - Green, yellow, Red etc). I have seen this done for COMAH actions tracking and many other areas.

Posted By Paul Bellis Thanks for the comments -a couple of good points to try. Anyone got a written procedure though to help things along - it will obviously be very different from th eenvironment I am using it (not COMAH) but its wording and terminology I am getting bogged down with cheers Paul