What about the company H&S policy as some of what you are saying falls within scope of this and the EAWRThere is very limited guidance on this I’ve have a look through company policies and a lot of our guidance covers basics like maintaining isolations ect.
It is not clear from what you have posted how big the company is but there seems to be something lacking in the maintainance process within it, have you asked your foreman / chargehand / maintainance manager for their thoughts / comments on the maintainance process within the companyI agree, I’ve only ever been in a maintenance role at my company but not sure what other industrial setting are like? A lot of the problem is for years equipment was just ran till it failed no proper testing was ever done. If equipment failed they would just replace. This is where I struggle as just as I joined the company they were getting hotter on testing. So I still see it alot of the older lads don’t bother with it so would not notice the same things I do (such as lack of earthing and bad ZS). Hence why I decided to reach out on here as It’s not me to turn a blind eye to things but then again I can’t fix the world.
But yeah I think this is where it all stems from lack of testing which now I’m in the position where I’m finding bits that should have been picked up years ago so when I state the problems I get (oh no you can switch that off) or something to that effect.
A good planned maintainance system should minimise how much reactive maintainance needed the fact you mention coding some issues a C2 would infer that the issues are within the fixed wiring system if machinery is involved then for me it is more like ISITEE which if something warrants the C2 you suggest then really you are looking towards locking it off and placing a do not use on it until the necessary repairs are carried out
I think if it was me I would be taking a picture of any maintainance dockets before handing them to your foreman / chargehand so you have your own paper trail just in case an incident occurs and some documentation is convienently "lost" that then puts you in the frame