Well,
This work week was relatively uneventful. We were short handed last night, but we got by ok. Here's one funny thing that happened:
This is going to take some backstory to be comprehensible. So at my job, we have these big machines that we call "tools". We use them to test silicon wafers before they are shipped out of the factory. Each tool is connected to a workstation which is nothing more than a regular desktop PC. Well, sometimes the software in the workstation freezes up and we have to shut it down at different kinds of levels to get the tool running again. Last night, I encountered just this type of problem on one of our tools. The recovery progression goes like this...
1. We try to shut down the software normally, if that does not work..
2. We try to force the software to shut down via an external program. If that does not work...
3. We reboot the Workstation.
Well, I was following these steps, or trying to, but it turns out that there is a change in the procedures which has been recently implemented that I wasn't aware of at the time. Basically, when I tried to reboot the workstation, I followed and old procedure which not only does not work anymore, but also hoses up the entire tool.
So.. long story short. I broke the machine. Bad. And we had to call an automation guy from off site to come in and work on it. I am going to get soooooo much beef for this in the next few weeks. But it's ok. I don't think I am in serious trouble, I am just going to get made fun of a lot.
This work week was relatively uneventful. We were short handed last night, but we got by ok. Here's one funny thing that happened:
This is going to take some backstory to be comprehensible. So at my job, we have these big machines that we call "tools". We use them to test silicon wafers before they are shipped out of the factory. Each tool is connected to a workstation which is nothing more than a regular desktop PC. Well, sometimes the software in the workstation freezes up and we have to shut it down at different kinds of levels to get the tool running again. Last night, I encountered just this type of problem on one of our tools. The recovery progression goes like this...
1. We try to shut down the software normally, if that does not work..
2. We try to force the software to shut down via an external program. If that does not work...
3. We reboot the Workstation.
Well, I was following these steps, or trying to, but it turns out that there is a change in the procedures which has been recently implemented that I wasn't aware of at the time. Basically, when I tried to reboot the workstation, I followed and old procedure which not only does not work anymore, but also hoses up the entire tool.
So.. long story short. I broke the machine. Bad. And we had to call an automation guy from off site to come in and work on it. I am going to get soooooo much beef for this in the next few weeks. But it's ok. I don't think I am in serious trouble, I am just going to get made fun of a lot.