Originally Posted by
osiyo
You should modify that to "receiving the blame for every mechanical, electrical, electronic, ethernet data networking, desktop/laptop computer, and engineering shortfall that can be imagined."
Give me a bit and I'll think of more.
Those are just the things I've had to deal with in the past couple holiday weeks (short weeks).
But it's my job. I mostly do startup and commissioning and testing. Last controls guy on the job site. So when something isn't working, or isn't working correctly, the finger gets pointed at me.
So I end up troubleshooting programs in controllers, I/O stuff connected to the controllers, graphics and front end residing programs, serial control networks, ethernet data networks (because the IT departments ALWAYS say its not their issue), mechanical systems, regular electrical systems, or whatever. And fix whatever if its something we are responsible for. Or troubleshoot and produce UNDENIABLE FACTS to show its mechanical or electrical .... because those guys aren't gonna come back to the job site willingly, will just blame it on controls unless you can show absolutely, positively its their stuff. Or, as has been the case just last week. I show customer where the design engineer .... THEY HIRED .... specified such and such a sequence of operation which we correctly implemented just as he demanded ... and IT DOESN'T WORK.
LOL ... keeps life interesting.
It's 4:20 am here, and I'm up and have been working on some network traffic analysis problems related to a job, for a couple hours now. System is bogging down. Have to be on the job site by 6:00 a.m.
Yes, today is technically a holiday for me and I should be kicking back and relaxing. But instead I'll be working, have been working. <Shrug> There are deadlines to meet, and all the pre-planning, programming, engineering, etc done back in the office for this project isn't working out as they expected ... so ... it's off to work I go.
LOL ... guess I'm a controls guy.