MarkTTU
Lifetime Supporting Member
As one who came from IT into control engineering I can tell you that under no circumstances do you want IT to take away control. There are times when you'll need to co-exist with IT, but when these times happen IT needs to be aware that the printer not working and the plant not working really do have very different priority levels.
We're a small company so I get the unique situation of being both controls engineer and the IT guy; problem solved.
When we've hired part timers, etc to help out with IT I always break down the expected up-time for the entire system (including all things IT, even the printers) into real time. I tell them that 99.9% uptime is easy to achieve and 99.99% uptime is the goal; somewhere in between is reality. At 99.9% uptime you are down 10 minutes every week; at 99.99% uptime you are down 1 minute every week; keep in mind a computer takes more than 1 minute to boot up. I then ask them if they still think a change that should take 10-15 minutes, but if it goes wrong could take 2-12 hours is no big deal. They usually answer no; they always answer no if I put a $/minute into their head for downtime.
We're a small company so I get the unique situation of being both controls engineer and the IT guy; problem solved.
When we've hired part timers, etc to help out with IT I always break down the expected up-time for the entire system (including all things IT, even the printers) into real time. I tell them that 99.9% uptime is easy to achieve and 99.99% uptime is the goal; somewhere in between is reality. At 99.9% uptime you are down 10 minutes every week; at 99.99% uptime you are down 1 minute every week; keep in mind a computer takes more than 1 minute to boot up. I then ask them if they still think a change that should take 10-15 minutes, but if it goes wrong could take 2-12 hours is no big deal. They usually answer no; they always answer no if I put a $/minute into their head for downtime.