Power Plant Black Time and Six Hour Rules
Favorites Post #79
Originally posted May 2, 2014:
Last week I mentioned in the post “Making Friends from Foes – A Tale of Power Plant Woes” that Jim Padgett called me at 2:15 am one morning to tell me that the coal dumper was broken and he needed for me to come out to the plant to work on it. You may have wondered why a plant electrician living in North Central Oklahoma would answer the phone in the middle of the night when it most certainly meant that they would have to crawl out of bed and go to work to fix something that was broken. Why not just roll over and pretend that the phone never rang?
You see… I knew when the phone rang that it was the power plant, because in the 20 years that I worked at the plant, just about every time the phone rang after midnight it meant that I would have to get dressed, and drive 30 miles to the plant to work on something that was most likely going to be in a dusty dirty place. You could always count on the coal train dumper switchgear being covered with coal dust. That was the usual point of failure past the “witching hour”.
A rotary dumper much like the one that was at our Power Plant
I suppose I could say there were two reasons why a Power Plant Man would answer the phone. One was that they were just all around nice guys and they wanted to help out any chance they could. The other reason was because of the pay.
Even though working at the power plant was perhaps one of the best jobs in the neighborhood (being the only job in the neighborhood, since the plant ground consisted of its own neighborhood out in the middle of nowhere), that didn’t mean that the pay was especially lucrative. That is, if a Power Plant Man had to rely on their base pay alone it would be difficult. So, in order to help the Brave Men and Women of Power Plant Fame pay their bills, many opportunities were provided for working overtime.
Think about this. What if, when I answered the call to save the day (uh… I mean the night) and spent 35 minutes driving out to the plant only to fix the problem in fifteen minutes? Then I would spend another 35 minutes driving back home with my clothes all full of coal dust, only to be paid a measly 15 minutes of over time? Even at double time, that would only be 30 minutes of pay. That would hardly cover the gas and the laundry soap.
Early in the life of this particular plant, it became apparent that something had to be done to motivate the heroic masters of Power Plant Maintenance to make the long lonely drive down Highway 177 at the wee hours of the morning. So, certain methods were devised to coax the restful souls to the phones when they rang. Once they answered the phone, then sheer guilt was enough to drag them out of the sack. It was that moment when the phone first began to ring, before the reasoning part of the brain kicked in and the more base reflexes such as those that were out to make an extra buck reacted instinctively that needed to be targeted.
So “Black Time” was introduced to the plant. Black time had probably been around long before the plant came into existence, but it came in handy when someone had to be called out in the middle of the night. Black time was the time that a person would be paid even though they didn’t actually work during that time. So, when a Power Plant Man was called out in the middle of the night, they would be guaranteed at least two hours of overtime even though they may only work for 15 minutes.
This would help defray the cost of gas and time for driving both ways to and from the plant. Anything from 7:30 pm to 7:00 am was paid as double-time. That is two times the normal base salary. So, two hours at double time came out to four hours of pay, or as much pay as someone would make for half of a day at work. That was some incentive for disturbing a Power Plant Man from their pleasant dreams of adventuring through the Power Plant Kingdom where the rule was always “Might For Right”. — Well, at least that’s what I was dreaming some of the time when the phone rang.
If Black Time wasn’t enough, it was taken a step further when the six hour rule was introduced. The Six Hour Rule was added fairly early on in the life of the Power Plant and went through a few variations when I was working at the plant. When it was first introduced, it came across as if someone downtown had made the decision that when someone is disturbed from their sleep during certain hours of their sleep cycle, it directly impacted their safety. Hence the Six Hour Rule was born.
Originally it worked like this…. The hours of midnight to 6:00 am were considered the prime sleeping hours for Heroic Power Plant Men. During this time, it was deemed that all Power Plant Men should be tucked in their beds dreaming of ways to work safely during the following day. Whenever this time period was disturbed, then the Electric Company should provide the loyal Power Plant Man for answering the call of duty during a time of early morning emergency by giving him back the same number of hours in black time so that he could go home and continue his all-important dreams and regeneration.
Power Plant Pocket Watch worn by Old Fogies
So, if I had been called out at one o’clock in the morning to work on something, and it took me two hours to fix it, then I could come into work two hours later in the morning. The first two hours of my regular work day would be payed as “Black Time”. — Makes sense… right? Two hours of work…. Come in two hours late in the morning…. black time… Easy to calculate.
This provided a pretty good incentive for going out to work in the middle of the night. First, you would get at least 2 hours of double time. Second, you would be able to make up for lost sleep by coming in late in the morning without having to lose any pay. You could also come in at the regular time and leave early in the afternoon if you wanted.
Well… That lasted for a few years, then the rules for the 6 hour rule began to change. Originally, even if the job was only 15 minutes, the least amount of black time that you would get was 2 hours. After all, it was an hour of driving back and forth for the large majority of the Power Plant Men that lived in a civilized village of more than 50 people. Later, the Six Hour Rule was changed so that only the actual time worked would count for the six hour rule.
This meant that if I drove all the way out to the plant to work on something that only took 15 minutes, then I could only come in 15 minutes late then next morning, even though I had spent at least an hour and 45 minutes away from my dreams of serving nobly in the Power Plant Palace. In that case the six hour rule didn’t apply anymore. I figured that someone who was short-sighted had come up with that idea. I’ll explain why in a few minutes.
The next phase of the Six Hour Rule came a few years after that… It was decided that after a person had been called out at night to fight the good fight, as soon as they left the plant, the six hour rule would start counting down. Let me explain this in a little more detail….
Say, I were called out to work in the middle of the night, and I worked from 1:00 am to 3:00 am (two hours). Then I left to go home at three. The hours start counting down so that by 5:00 am, the time I had spent at the plant were no longer valid, and I was expected to show up at work at the regular time. 8:00 am. Okay. So, in more and more cases (it would seem), the six hour rule would be made meaningless.
So, with this rule in place, if I was called out at midnight, and worked until 4:00 am, for a total of 4 hours, then by 8:00 am when I was supposed to be back at work all of the four hours would have ticked off and I would have no black time. I would have to show up at 8:00 am. See how that was supposed to basically take the six hour rule and make a joke out of it? (Or so, someone thought – which was probably me).
As most attempts at being underhanded without actually just coming out and telling us that it was decided that the Honorable Power Plant Men no longer needed their six hours of prime sleeping time to work safely the next day, the opposite effect was the result. Kind of like raising the minimum wage to help the workers, when you put more people out of work.
When the six hour rule was changed to count down from the time you left the plant, was when I made the most money from the six hour rule. I racked up loads of black time from this change as well as most Power Plant Men that were called out before Morning Prayers (Lauds). Here is how and why:
Suppose the phone rings and it is 1 o’clock in the morning. You decide to answer it and get called out to work on something that takes 15 minutes. You finish the job some time around 2:15 am (because, after all, you had to drive all the way out to the plant). What should you do now? If you go back home and go to bed, then because of the way the 6 hour rule worked, you would certainly have to come back to work at 8 o’clock. — hmm… You will still have collected 2 hours of double time. That’s something.
24 hour clock
Look at the alternatives. What if you went to the shop and worked on some other tasks while you were already there? For Power Plant Maintenance Men, there is always something that needs to be fixed. You may even ask the Shift Supervisor, “While I’m here, is there anything else you want me to work on?” Shift Supervisors just love having their own personal maintenance man in the middle of the night eager to help. There is always something they could find that needs fixing.
So, instead of turning around and going home, invariably, after the 15 minute job was over, I would end up doing other jobs for the Shift Supervisor until morning. Well, once 6:00 am rolled around, it was really too late to drive home and then wait an hour and drive back. So, I would just stay until 8.
Now look what happened! Instead of 2 hours of double time, I worked from 2:00 to 8:00 with all but the last hour at double time, the last hour at time and a half. That comes to 11 1/2 hours of my base salary. Compare that to the 4 hours I would have received for 2 hours of double time.
But here is the best part. 8:00 rolls around. We have our morning meeting. Since I worked for 4 hours of the special 6 hours from midnight to 6, I get to leave at noon and get paid black time for the rest of the day.
What fun! Every time the six hour rule was reigned in to reduce black time it produced more black time. And how was that safer? The final tweaks to the 6 hour rule before it was basically abolished a few years later came during the fall of 1991. I’m not saying that this alone was the reason, but in 1992, the Power Plant had the highest Accident Rate since 1983. Somewhere around 23 accidents. Given that in 1983, we had 50% more employees, 1991 had a much higher accident rate.
The number of call-outs in the early hours of the morning were not as common as I may have made them out to be. So, I don’t mean to claim that the change in the six hour rule was ever the cause of even one additional accident. I studied all the accidents that happened that year, and even though some of them were the result of fatigue, it was usually because they had worked an extra long shift – over 12 hours, and were injured because they were tired. Not because they were affected by the six hour rule. The question was never asked if the person had been called out the night before.
Even though (as far as we know, because we never asked the question) the six hour rule changes didn’t directly cause any particular accident that year, it was a symptom of an overarching problem. A certain apathy toward safety had crept into the plant. The previous years, we had an excellent safety record. One of our best years was in 1987. We had only 3 accidents that entire year. None of them serious.
I will discuss Safety in various other posts, so I won’t belabor the point now. The point I wanted to make from this post was that by focusing on the bottom line, or some other performance metric without putting your most important asset first (The Power Plant Man), almost always guarantees the opposite results.
Comments from the original post:
Another great story. I hadn’t thought of the “6 hour rule” for years. I really appreciated the true power plant workers who would answer the call. If I could do it all over again I think I would have gone to a Vo-Tech school and learned a skill (like machinist). The “6 hour rule” never applied to management. I never received any overtime, ever (start-ups, overhauls, routine emergencies, etc.). And we were responsible for getting those people to come to the plant who didn’t want to. I can show you a hole in the wall at the Seminole Plant today made by a mad operator that I “forced” to work (1982) when he didn’t want to. When he left my office he threw the door open so hard it hit the stop in the floor and flexed until the door knob mashed a hole in the wall. Then he told me “I’m not through with you yet.” He later transferred to Sooner – as a promotion. Oh the joys of management.
I’m grateful today for the people who still answer the call and keep our power on!
THAT’S HOW THEY WORK IT HERE FOR MAINTENANCE CALL-INS. TOO BAD THAT DOESN’T HAPPEN FOR SECURITY—ALTHO’ I WILL GET OVERTIME HOURS FOR COVERING THIS SHIFT.
Power Plant Men Take the Corporate Mainframe Computer Home
Favorites Post #78
Originally posted January 10, 2015
When the Coal-fired Power Plant in North Central Oklahoma downsized from 218 employees to 124 employees in 1994, everyone was scrambling to figure out how we were going to complete all the work that needed to be done to keep the plant running. We had become cross-functional teams which seemed to help right away, but we needed to know what jobs were the higher priority jobs, because it became obvious, at least for the short run, that we were not keeping up with the workload.
That was where the “Planners” came in. In other industries, we may call these guys, “Project Managers”. They planned the work, and gave us the Maintenance Orders when it was time to work on them. At first, this was a daunting task for the four planners at our plant. The planners were Mike Vogle, Glenn Rowland, Ben Davis and Tony Mena.
This was a new job for all of them. Glenn Rowland had been an A Foreman for the Instrument and Controls Department. Tony Mena had been on the Testing team. Mike Vogle had been a B Foreman over the Labor Crew. Ben Davis had been an electrician. Now they were suddenly working on a computer all day long trying to learn how to plan their days so they could plan ours. I currently don’t have any good pictures of this team, or I would let you see for yourself what great guys they are.
Oh. Ok. Here is a later picture of Mike Vogle which I absconded from his Facebook page:
Mike Vogle
At this time, though they were using the “state of the art” 286 PCs, they were really working on the Honeywell mainframe computer at Corporate Headquarters in Oklahoma City. They did this by using a Dumb Terminal emulator named GLink. See the post: “Working Smarter Power Plant with Dumb Terminals” for a better explanation.
This is GLink today. Back then it was for Windows 3.1
The Power Plant Men knew that I liked to play around on the computers. I was always going around helping people improve their computer experience by writing little programs that would do important things. For instance, Windows back then had a screensaver that would fly the windows logo out from the screen so that it looked like you were flying into the windows logos and they were passing you by.
Flying Windows Screensaver
In the executable program, if you changed the value of one particular byte, you could change the picture from the windows logo to any other of the 255 Wingding Characters. This included things like Skull and Crossbones, Hearts, Crosses, Envelopes, Stars, Snowflakes and a lot more. So, I was able to customize their screensavers using any of the wingding characters.
I wrote simple little programs to change their font size and color when they were using DOS, so they could read their screen easier (for the old timers that had a hard time reading the little letters).
Anyway, I had developed a reputation as not only being a troublemaker, but also of being a computer whiz. I have more stories to tell at a later time, but for now I will stick to the one about bringing the Honeywell mainframe home.
A Honeywell Mainframe computer
Mike Vogle first asked me the question. He explained to me that he was staying later and later each night at work doing his job. The earliest he was leaving was after 7pm each day, and he didn’t have time anymore to even see his family by the time he arrived home. So, he asked me if there was some way he could take his work home with him. What he would ideally like to do would be to take a disk from work with the Maintenance Orders on them where he could complete them. Then the next morning bring that disk back to work and put it in the computer and load it into the system.
I can see that a lot of you are rolling your eyes wondering why he didn’t just log into the company network and work remotely. Well, in 1994, the Internet was something new. We didn’t have the Network infrastructure built yet that would allow something like that. We were using Windows 3.1 on old 16 bit computers. Most of the programs we were running on the computers were still Pre-Windows. The GLink application, even though it had a windows Icon, was really a DOS program emulating a Dumb Terminal.
I told Mike I would look into it to see if there was some way I could emulate the emulator. That is, write a program that would be able to interact with the GLink program to upload and download data from the mainframe automatically. I was sitting in the Electric Shop Office with Charles Foster thinking about this over lunch when Terry Blevins came in.
Terry Blevins
Terry and I had worked together the last seven years on the precipitators. During the downsizing Terry was offered a job working on “Special Assignments”, which was a great move up for him. We were all happy for him. He had setup shop at the warehouse office where he could work part of the time from our plant instead of having to drive from Ponca City, Oklahoma to Oklahoma City to go to work.
When Terry came in to eat lunch with us, I told him what Mike Vogle had asked me. Terry said right away that the GLink program had a Macro language that we might be able to use to automate the process. This was just what I needed to hear. If I could write a program that would write macros and send them to GLink to run, then that would do it. I looked up the macro commands for GLink by opening up the Help section and printing out the list.
I used BASIC 7.0 (no. Not Visual Basic, I hadn’t advanced that far yet). BASIC 7.0 was the first BASIC that did away with line numbers and advanced to a real second generation programming language. It came out about the same time as MS Windows. When I first bought the program, it was about $500.00 which was quite a lot for me. But it allowed me to create actual DOS executables where I could do just about anything I wanted.
My BASIC 7.0 Programmer’s Guide
Keep in mind that the language I was using to write the program didn’t know about Text Boxes, or even “Word Wrap” for that matter. Everything that the user did on the screen, I had to take into account myself. Just like I was working with a dumb terminal. So it didn’t understand something as simple as “Word Wrap”.
So, when you finished typing at the end of the line, if it jumped down to the next line in the middle of the word, you had to arrow up, and arrow to the right (forget using a mouse), and backspace until you had erased the letters at the end of the line, and then arrow back down to the next line and start typing again.
So, I put in my own logic for word wrapping because the mainframe window had only so many characters per line, and it had no mercy. Everything had to be in the right box when you clicked on Submit. When I was finished writing this program, I was so proud of myself for creating something as simple as “Word Wrap”.
Word Wrap, for those of you who don’t understand the phrase is when you get to the end of the line you are typing and instead of splitting the word up when it goes to the next line, it moves the entire word down to the next line. You see it all the time now, but early on, the person writing a computer program had to take that into account if they wanted something to word wrap. Windows Text Boxes and Word Processors had Word Wrap built in, so today a programmer doesn’t have to worry about all those little things, because the objects already know how to do that. Just like this internet page knows how to do it.
Years later when I was interviewing for a Developer job with other companies and they would ask me what was one of my greatest programming accomplishments, I might blurt out “Word Wrap” before I realized how silly that sounds today.
Another problem I had was that strings of characters in the computer code are delimited by Double Quotes, so what happens when someone is filling out their Maintenance order and they use a Double Quote (“). I didn’t think about this, and the first time I gave the program to Mike Vogle to test it out, it went all crazy and entered a bunch of bad data into a Maintenance Order because there was a Double Quote in it….. Yeah. I forgot that if you want to say you worked on a four inch pipe, you would write that as 4” pipe.
So, my second great accomplishment when writing this program was to watch each key stroke, and if it was a double quote, then I would concatenate the string to another string around the double quote that was delimited with single quotes. After doing all that, the program worked pretty good. I gave it to Mike, and he tested it out and after making a few more tweeks, it was ready.
Mike could then take his disk of Maintenance orders home with him, and complete his work there, and in the morning he would put the disk in the computer, type a simple command, and it would open up GLink and start uploading all the work he did the night before. Flashing screen after screen as it worked through all the Maintenance Orders.
Over time (not overtime, but Over Time, as in after a number of days or weeks, not like getting paid time and a half), the program became popular with some of the foremen, because it had Word Wrap and the GLink Emulator didn’t because it was emulating the Dumb Terminal which is too dumb to wrap words from one line to the other. So, this one little feature that I was so proud of figuring out actually turned out to be the selling point for the foremen to use my new program during the day at work.
I had originally written the program so that Mike could take it home and use it to store macros on the disk that would upload the data to the Mainframe in the morning, but now the foremen were using it during the day at work because it was easier to use than the actual program that talked directly to the mainframe.
It was fun writing a program that essentially wrote another program (macros) that would tell another program (GLink) what to do. To me, it was the first step for me to take over the world (as one of my Managers at Dell used to accuse me of doing). What I mean is, that if you could write programs that writes other programs, aren’t you essentially creating some sort of “Artificial Intelligence”?
Because of my initial experience with this effort, it has given me the idea to write a program called: “Old Man” (well, this was before Alexa came out). Someday, maybe when I retire, I want to write a program that will help old men… like I will be. Old men that are losing their memory (like I will be… or already am). And it will learn what the old man does and how he lives, and it will remind him to do simple tasks. Basically, it will nag him like his wife would do if she was still living. It will use voice recognition so it will speak and listen to the old man speak back.
The “Old Man” application will remind him to brush his teeth. Go to the barber, wash the sheets on his bed. The list can be endless, because it will learn what this person needs from scratch and dynamically build the database and infrastructure in the background to take care of this old man when he can’t remember if he has just taken his medicine already or not. It will even make a shopping list for him and help him with cooking. It will be connected to the Internet so that it can pull all sorts of information it needs.
The “Mainframe Emulator Commander” program that I wrote for Mike Vogle really was my first step to becoming a real nuisance at the plant, because after that, I wanted to write more and more programs. So, I was always on the alert as to what I could do next. I will write about some of the things we came up with throughout this year.
Black Ops Raid Power Plant — Power Plant Men Ignore Attackers
Favorites Post #75
Originally posted January 17, 2015
I don’t know if they called them “Black Ops” in 1994, but when the control room operator David Evans answered the phone that day in October, I don’t think he ever expected to have the person on the other end of the line tell him that a military special forces unit was going to stage a mock raid on the coal-fired power plant in North Central Oklahoma some time that night. I’m sure Jack Maloy, the shift supervisor, was equally surprised when David told him about the phone call. I heard later that Jack was pretty upset to find out that a military force was going to be attacking our plant in the middle of the night without his permission!
David Evans waits for Jim Padgett to get a cup of coffee — Thanks Jim Cave for the photo
The first we heard about the call was when Jasper Christensen called a meeting of the entire maintenance department on the spur of the moment in the main break room. He told us about the phone call. He said we didn’t have any more information than that. Though the maintenance department shouldn’t be working that night, Jasper said that just in case we were called out for something, we should know that a group of commandos were going to be performing some sort of mock raid on our plant. If we encountered any soldiers sneaking around the plant in the middle of the night in full military gear, not to be alarmed. Just go on doing what you’re doing and don’t bother them.
Pay no attention to the man behind the mask. Photo from Call of Duty
Now that it is 21 years later (well, almost) the truth can finally come out…. Isn’t that how it goes? When we are sworn to secrecy, isn’t it 21 years before we can finally speak out? (That’s what Shadow Warriors always told me). I don’t remember us taking an oath or anything, but that’s the way it is with Power Plant Men. They just assume that if the military is staging a mock raid on our plant, it is a matter of national security. It seemed as if our plant sort of matched the layout of a power plant somewhere in Central America where the real raid was going to take place.
The main difference between our Power Plant and the one in Honduras, or wherever it was, is that our plant had recently gone through a downsizing. So, our operators at night now had to perform the duties that had before been done by the labor crew. They had to do coal cleanup throughout the conveyor system.
Coal conveyor carrying coal to the coal silos from the coalyard
This meant that if one of our auxiliary operators happened to run across someone dressed in the outfit above, they would have naturally handed him either a water hose or a shovel and pointed to the nearest conveyor and said something like, “I’ll start on this end, and you can start over there.” After all. He would already be wearing his respirator.
That day on the way home, Scott Hubbard and I discussed the significance of such a raid on our Power Plant. A year and a half earlier, Janet Reno had really messed up the raid on the Branch Davidian compound in Texas when it burned down and burned everyone to death including women and children. So, it would be good to go into a situation like this more prepared.
I had often thought about the steps that could covertly be taken to single-handed destroy the power plant without using any kind of explosives. Those who understood how all the systems worked together could do it if they really wanted to. Of course, that was just how I might occupy my mind when I was doing a repetitive job, like sweeping out the main switchgear. What better place for those thoughts to drift into your mind.
A picture of a clean switchgear. Picture 6 rows of switchgear like this
Actually, now that I think about it, instead of sending in the Special Forces, just send in a few Plant Operators, Electricians and Instrument and Controls guys and they could totally destroy the plant in a matter of hours if that was their intent. The same thing could be said about putting a few incompetent people in upper management even if it isn’t their intent, only it takes longer than a couple of hours to destroy the plant in that case.
The next morning when we arrived at the plant, our foreman Alan Kramer told us the stories about the raid that happened the night before. This is what I can remember about it (if any Power Plant Men want to correct me, or add some more stories, please do in the comments below).
Alan Kramer
First he said that it appeared as if the commandos had landed in some kind of stealth helicopter out on the north side of the intake because later when the power plant men had investigated the site they could see where two wheels on the helicopter had left an impression in the mud. Dan Landes had been keeping a lookout from the top of the Unit 1 boiler, and he thought for a moment that he saw the flash of a red light…. which… thinking about it now, could have been one of those laser sites taking aim at him and mock assassinating him by shooting him in the eye from about 1/2 mile. You know how good American Snipers can be (my plug for the new movie). Good thing he was wearing his auto-tinting safety glasses.
That’s Dan Landes in the second row with the Gray Shirt – Otherwise known as Deputy Dan
We also heard that one of the operators, Maybe Charles Peavler (Charles is standing next to Dan wearing the pink shirt and carrying something in his lower lip) had stepped out of the office elevator on the ground floor only to come face-to-face with a soldier. When the soldier was seen by the operator, he just turned around and walked out of the door… he evidently was considered a casualty if he was seen by anyone. Either that, or he had to go do coal cleanup the rest of the night.
I think it was Jeff Meyers (front row, left in the picture above) who told us later that the Special Ops forces had left a present for the operators on the Turbine-Generator Room floor. Tracked across the clean shiny red T-G floor were muddy boot prints leading from the Unit 1 boiler entrance to the door to the control room. The tracks ended at the control room door.
The Red T-G floor is always kept clean. The control room entrance is under the grating where this picture was taken. – Thanks Jim Cave for the picture
The tracks were extra muddy as if someone had intentionally wanted us to see that someone had walked right up to the control room door. The tracks did not lead away from the door. They just ended right there.
So, we did have proof that the commandos had actually visited our plant that night, only because one of the operators had come face-to-face with one in the main lobby. If that hadn’t happened, then they would have come and gone and we would have been none-the-wiser… other than wondering about the strange muddy footprints and the impression left in the mud by the stealth helicopter.
Stealth Helicopter
I suppose it was easy for the Power Plant operators to ignore the commandos since for the most part, they never saw them coming or going. The Power Plant Men were happy to play their part in the mock raid. Of all that has been asked of these Power Plant Men over the years, this was one of the more “unique” events. How many Power Plant Men across the country can say that they took part in a Special Ops Commando Raid on their Power Plant?
All I can say is that the commandos sure picked a great bunch of Power Plant Men and Women to attack. We were all honored (even those of us who were at home in bed asleep at the time) to be able to help out the military any way we could.
Power Plant Conspiracy Theory
Favorites Post #74
Originally posted September 20, 2014.
I remember the moment when it dawned on me that I may be witnessing an incredible Coal-fired Power Plant Conspiracy! I had just walked into the Control Room one morning in 1990 at the plant in North Central Oklahoma and saw the Shift Supervisor Jack Maloy and Merl Wright in a state of high concentration.
I always knew something was up when Jack Maloy was standing behind the large blue monitors near the Unit 1 Main Electric Board watching the big picture while the Control Room Operator Merl Wright was at the Main Control Panel turning knobs, tapping indicators to make sure they had the correct readings, twisting switches, holding them until red lights turned green…
I love this picture! — not our plant but may be part of the conspiracy
Where had I seen this before? Something was telling me that everything wasn’t as it seemed. Sure… there was an emergency going on. There was no doubt about that. I knew that between Jack Maloy and Merl Wright, the current problem of the main boiler drum losing water was quickly going to be solved. I knew that Oklahoma City wasn’t going to experience any blackouts that day. This was a Cracker Jack (Maloy) team! But I couldn’t help thinking I had seen this somewhere before, and it was gnawing at my common sense.
Here is a picture of Jack Maloy’s team at the time:
Jack Maloy is standing on the far right with the vertically striped shirt (like bars in a jail) directly behind Merl Wright kneeling before him – Coincidence? I think not.
I backed off in a corner to observe the situation while a crowd of operators began to grow to watch the master Shift Supervisor and his faithful Control Room Operator divert a disaster. Merl picked up the walkie talkie from the desk and called Larry Tapp ( Larry is the man in the light blue shirt in the front row in the middle. He’s the only one in the front row that is actually standing, while the rest are down on their knees while the picture is being taken).
Larry was on the boiler opening and closing valves. John Belusko, the Unit Supervisor was out there with him. I can’t tell you what magic they were performing, since I think that’s top secret. I figured that, because the operators seemed to be talking in code. Merl would key the microphone on the walkie talkie and say something like, “Larry, 45”. Larry would reply with something like “Quarter Turn”. “Position?”, “18 as far as I can tell”.
A Motorola Walkie Talkie like this
I translated the coded words to say: “….crawling under the path of the boom, whipped hold of a rope, secured one end to the bulwarks and then flinging the other like a lasso, caught it around the boom as it swept over his head, and at the next jerk, the spar was that way trapped and all was safe.” (Something I had read in Moby Dick, by Herman Melville).
Jack paced back and forth behind the counter with the monitors. Then he stopped and read the paper that was streaming out of the alarm printer as it continued humming as the paper piled up on the floor in front of him. Jack was a heavy smoker, and I could tell that right then he would rather be standing out on the T-G floor having a smoke at that moment. Before cigarettes were banned in the control room, Jack would have been pointing at that board with the cigarette.
When the water level began rising in the Boiler Drum, I could see the relieve on everyone’s face. I supposed it meant that a major catastrophe had been avoided due to the intricate knowledge that each operator possessed and their ability to quickly respond to any situation. This made the uneasy feeling I was having even worse. I couldn’t shake the feeling that I had seen this before. Just like Deja Vu.
It wasn’t till about a week later when my mom asked me if I knew someone at work named Jack Maloy. She had been talking to a friend of hers from Church named Louise and she mentioned that her husband worked at the Power Plant north of town. I replied by saying that I knew Jack Maloy well. He is a Shift Supervisor. She said that his wife Louise told her that Jack was a real nice person, but she wished that he would go to Church more. She hoped he would come around to that some day.
Then my mom mentioned something that brought back that feeling of uneasiness again. She said that the Maloys had moved to Oklahoma in 1979 from California. I thought that was odd that Jack had only arrived in Oklahoma in 1979, as he was a Shift Supervisor for as long as I could remember. Maybe even as far back as 1979 when I first worked at the plant as a summer help.
In that case, he would have been hired as a Shift Supervisor straight from California. — That seemed odd, since the majority of Shift Supervisors had worked their way up from Auxiliary Operator to Control Room Operator to Unit Supervisor, then finally to Shift Supervisor. Why would Jack be hired fresh from California? And how did Jack know so much about being a Shift Supervisor at our plant so quickly?
Then it dawned on me. You see…. It all went back to a lunch break about a year earlier when Charles Foster, an Electric Foreman and I were eating lunch in the Electric Shop office. When we didn’t know what to talk about, our favorite past time was to talk about movies and TV shows we had watched. We would describe the movie in detail to each other. On this particular day, Charles was doing the talking, and he was telling me about a movie that had to do with a Power Plant in California (yeah. California).
Charles Foster
As Charles described the story, he told me that there was this Shift Supervisor named Jack (yeah… like our Shift Supervisor… Jack Maloy), and he was such a good Shift Supervisor that he could tell that there was something wrong with the Boiler Feed Pumps just by the way the coffee in his coffee cup would vibrate. Yeah. He was that good.
Charles went on to tell me about how at one part of the movie the water level was dropping in a tank and it was imperative that they raise the water level or some big disaster was going to happen. — Now you see where I’m going with this? Yeah. Sounds familiar doesn’t it? At that time, the incident in the Control Room hadn’t happened yet with Jack Maloy.
The movie sounded interesting so, when I had the opportunity, we rented the VHS tape from the video store and I watched it. Sure enough. This is what I saw….
Here is Jack the Shift Supervisor in California working with his Control Room operator trying to divert a disaster
Here is Jack Maloy and Merl Wright from the team picture above:
Jack Maloy and Merl Wright
Very similar don’t you think? Two Shift Supervisors named Jack from California with the exact same hairstyle. Two Control Room Operators that look like Wilford Brimley. Coincidence?
Wilford Brimley in the movie playing the same job as Merl Wright
Even Wilford Brimley’s hairline is the same as Merl Wright’s hairline!
For those of you who don’t know yet. The name of the movie is: The China Syndrome. It is about a nuclear Power Plant that has a near meltdown:
The China Syndrome
Need more? Ok. — hey this is fun….. So…. This movie came out in 1979. The same year that Jack Maloy shows up in Oklahoma from California. Obviously an experienced Power Plant Shift Supervisor. Merl Wright went to work 10 months earlier in 1978 at an older power plant just down the road (The old Osage plant), and then shortly after, was transferred to the same plant with Jack Maloy, only to end up working for Jack.
Need more? The China Syndrome Movie came out on March 16, 1979. Jack Maloy began working at the Coal-Fired Power Plant in North Central Oklahoma February 26, 1979, just two and a half weeks earlier.
I mentioned this coincidence to Charles Foster one day, but as far as I know, I never mentioned it again to anyone else… Maybe Scott Hubbard, since he was my best friend as well…
Scott Hubbard – See how he smiled when I told him?
So, here are my thoughts about this….
What if Jack Maloy was the Shift Supervisor being portrayed in the movie “The China Syndrome”? He needed to move out of California just before the movie came out just in case someone found out his true identity. Being a Shift Supervisor at a Nuclear Power Plant, he would surely be in high demand at any Electric Company. Our particular Power Plant was in an out-of-the-way location. Sort of like a “witness protection program”.
I don’t know Merl’s earlier background, so I can still think that he moved to Oklahoma from California and began working for the Electric Company on April 24, 1978 just two weeks before I moved to Oklahoma from Columbia, Missouri. Since I don’t know any better, I can continue thinking this. It makes it more fun that way. — Of course, Merl, who may on occasion read this blog, may correct me in the comment section below…
So, what was it that I was experiencing that morning when I walked in the control room? I mean… What was I “really” experiencing? If, suppose, Jack and Merl really are the two that were in the control room when the “China Syndrome” almost occurred? Was it just an innocent crisis where the water level somehow decided to drop to a dangerously low level all by itself because of a faulty valve that was supposed to be closed, but was really open?
Or…
Was Jack and Merl trying to relive the excitement they had felt years earlier when they worked in a nuclear plant and they almost melted a hole all the way from there to China? Was this what experienced bored Power Plant Heroes do during downtime? I suppose it’s possible. It could have been a drill drummed up to test the acuity of the operators. To keep them on their toes. All “Shipshape and Bristol Fashion” just like on the Pequod in Moby Dick.
Something to think about.
Today Merl still lives in Ponca City, Oklahoma. Jack Maloy has moved to Cape Carol, Florida with his wife Louise. I suppose now that he has more time on his hand, hopefully he has given up smoking and is now making his wife happy by attending Church regularly. We can only hope he is at peace, on the opposite side of the United States from California so he doesn’t accidentally run into his old cohorts.
We are all glad that on his way to Florida from California that Jack decided to stop for 25 or so years in Oklahoma to Supervise the Coal-fired Power Plant out in the middle of the countryside…. As Charles Champlin from the Los Angeles Times said of the movie “The China Syndrome” — “Stunning and Skillfully Executed!” — Yeah. That describes Merl and Jack. Either way… Conspiracy or not. These two men are my heroes!
I wish Merl and Jack the best rest of their lives!
Comments from the original post: (one of my most commented posts)
Hitting the Power Plant HR Cardboard Ceiling
Favorites Post #61
Originally posted September 5, 2015
I spent 12 weeks in Oklahoma City in 1996 working in an office building while the Power Plant Men came to the rescue and caused a culture shock for some who had never experienced a group of Power Plant Men so closely packed in an office cubicle before. The effect can almost be the same as if you have too many radioactive particles compressed together causing a chain reaction ending in a tremendous explosion. Having survived this experience I became intrigued with the idea of working in an office on a computer instead of carrying a tool bucket up 25 flights of stairs to fix the boiler elevator.
Our team had been in Oklahoma City when we were converting the Electric Company in Oklahoma to a new financial and planning system known as SAP. See the post: “Corporate Executive Kent Norris Meets Power Plant Men“. One other person from out plant was in Oklahoma City for the entire 9 months it took to roll out SAP. That was Linda Dallas, our HR Supervisor at the Power Plant in North Central Oklahoma.
SAP Logo
Linda Dallas was on the core SAP team which was a coveted spot for one not so obvious reason. The few people that were on the core team were learning how to implement SAP in a fairly large public electric company. The consulting company Ernst and Young were teaching them how to build SAP screens and configure the application as well as how to run a large project. — Do you see where I’m going?
I went out and bought a book on programming SAP myself just in case I had a chance to play around with it when we were in Oklahoma City. I read the book, but unfortunately the opportunity to mess with SAP never came up (or did it?).
A programming book like this
Mark Romano, the engineer that was coordinating our efforts during the project tried to have me assigned to the testing team for SAP, but the SAP guys said they didn’t need anyone else…. For more about Mark Romano, read this post: “Power Plant Marine Battles with God and Wins“. Consequently, when Mark told me that the testing team positions were just as coveted as the core team and they didn’t want an outsider coming in and showing them up, I understood.
In case you haven’t figured it out yet…. SAP was an up and coming terrific software package that took practically your entire company’s computer activities and put them in one all encompassing application. People experienced in SAP were far and few between, so anyone looking for people with SAP experience were finding the pickin’s rather slim (as in Slim Pickens). Because of this, most of the people involved in the core SAP implementation could basically write their ticket when it came to finding a job with a company trying to implement SAP in 1996-97.
I thanked Mark for putting in a good word for me with the testing team. I also told him that the first time I actually am able to use SAP, I will break it within 10 minutes just so the testing team can see how it’s done. — I had a lot of experience with “Negative testing” as it is called in IT. That is when you do what you can to try to break the application.
I like the word “consequently” today, so I’m going to use it again…. Consequently, when Linda Dallas came back to our plant to show us all how to use SAP after we went live, here is what happened….
We went to the small conference room where I had setup about 15 computers all hooked up to the company’s Intranet. The team from Oklahoma City had actually brought the computers. I had just run all the network cables to the room so they could train people 15 at a time. The trainers wanted to “lock down” the computers so that they only had SAP on them and not other things like “Solitaire” that might distract the Power Plant Trainees.
Here is what happened when I showed up for my class…. Linda Dallas was teaching it along with one other guy from Corporate Headquarters…. I’ll call him “Jack”… for various reasons, but mainly because I can’t remember his name… Jack told us that the computers we were using were stripped down so that it didn’t have games like Minesweeper and Solitaire on them, (as did all the regular Windows NT computers).
The first thing I did when he told us that was to browse over to the electric shop computer through the network and copy the minesweeper and the solitaire games from the computer in the electric shop to my training computer….. See how rotten I used to be (yeah… used to be… Huh? What’s that?)… Then I opened Solitaire and started playing it while they explained how to go into SAP and start doing our jobs.
They showed us the Inventory section. That had all the parts in the company in it. That was the part of the application I had helped implement in our small way.
When they showed us the inventory section, I realized right away how I could break SAP, so I proceeded to open 10 different screens of the SAP client, and began some crazy wildcard searches on each one of them. The application came to a grinding halt. (for any developers reading this… let’s call it… “SQL Injection”).
Linda, who was trying to show us how to go from screen-to-screen suddenly was staring at a screen that was going no where. She tried to explain that they were still having some performance issues with the application….
I just stared at my own computer screen trying to figure out if I had a red ten to put on the black jack…. when a red-faced Jack came around the tables and saw me playing Solitaire. I just smiled up at him and he had a confused look on his face as we waited for the screen on the projector to begin working again.
My screen at the time
I knew of course what had happened and after about 5 minutes of everyone’s screen being locked up, the application finally began working again and the training continued. — I was happy. I had completed my testing that the testing team didn’t think they needed. Of course, I did it to honor Mark Romano’s failed attempt to have me moved to the SAP testing team.
Mark Romano
A couple of years later when I was working with Ray Eberle on a Saturday (as we were working 4 – 10s, and rotated onto a Saturday once every 4 weeks), I showed him how I could lock up SAP for the entire company any time I wanted. Since few people were working on Saturday, I figured I could show him how it was done without causing a raucous. It took about 35 seconds and SAP would be down for as long as I wanted. There was a way to prevent this… but…. If the testers never test it, they would never tell the developers to fix it (I’m sure they have fixed it by now… that was 18 years ago).
Ray Eberle
Anyway, the story about implementing SAP isn’t really what this post is about. It is just the preamble that explains why in the spring of 1997, Linda Dallas left as the Supervisor of HR at our plant. She found another job in Dallas (So, Linda Dallas moved to Dallas — how fitting) with some of the other core SAP team members implementing SAP.
When the job opening for Linda Dallas’s job came out at our plant, I figured that since I met the minimum qualification, I might as well apply for it. Why not. It would mean putting away my tool bucket and working on the computer a lot more, which was something I was interested in since my experience a few months earlier when I was working at Corporate Headquarters.
I knew right away that no one would really take my job application seriously. I had all the computer related skills. I had a degree in Psychology, and a Masters in Religious Education from Loyola with a focus on adult education. That wasn’t really the point. I had never been a clerk.
The natural progression of things meant that the only “real” possible pool of applicants were the women clerks in the front office. Specifically Louise Kalicki. Her desk was closest to Linda Dallas’s office, so, in a sense, she was “next-in-line”.
Even though I knew that the plant manager Bill Green and Jim Arnold the Maintenance Supervisor would never want me on the “staff”, I went ahead and applied for the job anyway. I figured, it was worth the experience to apply and go through the interview process even though I wouldn’t be taken seriously.
Bill Green
I think Louise and I were the only two to apply for the job. Maybe Linda Shiever did as well, as she had the most seniority at the plant. Linda was actually the first person hired at the plant when it was first built. Louise had been filling in for Linda Dallas for the past year while Linda Dallas had been in Oklahoma City working on SAP, so she was really a “shoe-in” for the job.
When I went up to the interview, the first thing I had to do was take a timed typing test to see if I could type 35 words a minute (I could type 70). I had dressed up for the interview so that when I walked into the plant manager’s office, Bill Green and Jim Arnold had a little “Hee Haw” about seeing me without coal dust and fly ash coming out of my nose and ears. I told them that “I can get cleaned up when I needed to” (notice that I used the word “get” and ended my sentence with a preposition… just so they didn’t think I was too stuck up. See the post: “Power Plant Men Learned Themselves Proper English“).
No one was surprised when Louise Kalicki was promoted to HR Supervisor. She was probably the best choice when you think about it. She had a better relationship with Bill Green and Jim Arnold than I did and a good part of the job was working with those two rascals (oh… did I actually call them rascals? Bless their hearts).
This was right around the time that I had made my decision to go back to school to work toward a degree in Computer Science. Working with computers was really my passion.
I have an interesting way of making decisions about what I’m going to do with my life. I let certain events help make the decisions, instead of just jumping right in. I had decided (knowing that it was pretty much a safe bet) that if I didn’t get the job as the HR Supervisor, then I would go down to Oklahoma State University just a few miles from my house and enroll in the Arts and Science College and work on a degree in Computer Science.
I made a lot of decisions that way. I figured that if I was meant to do something, then it would work out that way. If not, then, fine, I would go a different route.
Ok. One more side story about working with Ray Eberle and SAP (See the post: “Tales of Power Plant Prowess by Ray Eberle“)… This happened some time around the year 2000.
SAP had this icon of a drip of water dropping and causing a ripple of waves….
SAP water drops
When the application was thinking, this picture was in the upper right hand corner and it was animated, so that the water rippled out as the water dripped. That way you could tell the difference between the application being stuck and just thinking.
This wasn’t just an animated GIF as we might have today. It was actually a series of bitmap pictures that were all strung together into one file. Once I figured this out, I used Paint to modify the picture. I created three new versions…. The first one had a small ship with sails sailing across the rippling water. The second one had a yellow fish that would leap out of the water over and over.
It was the third picture that was my masterpiece. I reversed the flow, so that instead of the water rippling out, it came in as if it was a whirlpool sucking things down. Then I added a small picture of our HR Supervisor’s face being sucked down into the whirlpool.
HR Supervisor sucked down a whirlpool
Then I created a small application that allowed people to change their water rippling animated picture to any of the four (with the regular picture being the fourth option) that they wanted quickly and easily. I know the women in the front office liked the one with the HR supervisor being sucked down the whirlpool the best. I won’t mention who they were, but by the following two pictures, you may be able to guess….
Linda Shiever
Darlene Mitchell
I would think that Bill Green would have liked the sailing ship the best since he liked to sail…. though… for some reason, I never made it around to install my “SAP add-on” on his computer (or Louise Kalicki’s for that matter, since she was the HR Supervisor). Most of the Power Plant Men probably would like the fish jumping out of the water, since they liked fishing. — I know… I know… I was being rotten… but it was fun.
Ok. End of the Side Story and end of the post.
Spending Long Weekends with Power Plant Men Shoveling Coal
Favorites Post #60
Originally posted on: June 1, 2012
The first couple of years while I worked as a summer help at the Coal-Fired Power Plant Coal Cleanup was performed on weekends by volunteer He-Men that wanted to make a few extra dollars. As a summer help, I needed all the extra money I could get. My wages during the first year (1979) were $3.89 an hour.
This jumped to $5.84 an hour when I worked on the weekend, so you can imagine the thrill I had at receiving a paycheck that included the extra money made by doing “Coal Cleanup”. Another great advantage to doing coal cleanup on the weekends was that I was able to carpool with different people. So, during the first summer instead of just riding to work with Steve Higginbotham (See the post “Steve Higginbotham’s Junky Jalopy late for the Boiler Blowdown“), I caught a lot of rides with real Power Plant Men like Dale Hull, David Hankins, Jerry Mitchell, Preston Jenkins and Marlin McDaniel (Yeah. Marlin McDaniel as an A Foreman would volunteer for coal cleanup some times. Maybe it was when we were short a few people).
Coal Cleanup really became important during the second half of the first summer because Unit 1 was getting ready to go online. There was a major flaw in the Coal Conveyor logic when the conveyors first started conveying coal from the coal pile to the coal silos just above the bowl mills. What would happen was the same thing that happens if someone were to fall down at the top of a crowded escalator going up. Everyone behind that person would be shoved right on top of them if there wasn’t an emergency stop button to stop the escalator.
Non Power Plant Escalator
All the conveyors had a safety cord alongside the entire length that could be pulled to stop the conveyor in an emergency, but this was something different.
To give you an idea… once the coal on the coal pile has been fed onto either Belts 4, 5, 6 or 7, from there the coal is dropped onto either belt 8 or 9. That carries the coal up to the coal Crusher which has a bin above the crusher that can be filled with coal. If the bin gets too full, then conveyor 8 and/or 9 would stop. When that happens, belts 4, 5, 6 or 7 should stop also…. only they didn’t. Belts 8 and 9 continued dumping coal into the crusher bin until it filled up and then coal fell out all over the top of the crusher tower around belts 8 and 9 until the coal tripped the belt by hitting the safety cord on the side of the belt. Belts 4, 5, 6 and 7 continued dumping coal onto belts 8 and 9, which caused the coal to backup and spill out all over the floor until the coal piled up high enough to trip the safety cord on the side of the belt.
In the picture of the power plant on the side of this post, there is one long conveyor that goes from the coalyard to the plant. It is about 1/2 mile long. This is where belts 10 and 11 carry the coal from the crusher, which crushes the coal down from big pieces the size of baseballs down to the size of walnuts.
The long belts 10 and 11 were like these only they are in a metal enclosure so the coal didn’t spill out on the ground.
At the top of the Transfer tower the coal from belts 10 and 11 are dumped onto belts 12 and 13 which carry the coal up to the Surge Bin Tower where the coal is dumped into the Surge bin. When the Surge Bin fills up, it stops belts 12 and/or 13 and it should also stop belts 10 and 11 and the feeders that feed the coal into the crusher at the bottom of the crusher bin… only they didn’t.
They continued dumping coal into the Surge bin, which filled up and spilled coal all over the surge bin until belts 12 and 13 tripped, at which point, coal began spilling out all over the transfer tower filling up both floors of the transfer tower with tons of coal. The same thing would happen at the bottom of Belt 10 and 11, where the crusher feeders kept feeding coal down to belts 10 and 11, which spilled out all over the bottom floor of the crusher tower.
I have worked in the transfer tower where the coal was higher than the windows and you had to bend over because your head would hit the ceiling on the floor at the foot of belt 12 and 13. It was almost dangerous enough to picture yourself sliding down the pile of coal and slipping right out one of the windows (which had been broken out by the pile of coal). To give you an idea of what this felt like, it was then a straight drop of 150 feet to the concrete below.
If that doesn’t seem like enough coal spills, then picture this… The coal from the Surge Bin tower fed onto belts 14, 15, 18 and 19 which in turn fed onto belts 16 and 17, 20 and 21. These last 4 belts were in what was called the “Tripper Gallery”. These 4 belts would dump coal into 12 coal silos (6 on each unit) that would feed the bowl mills. These are big silos about 5 stories tall.
The same thing would happen to these belts leaving piles of coal at the bottom of the surge bin in the surge bin tower and all along the tripper gallery because when the coal silos were full, the tripper was supposed to move to the next silo and dump coal until it was full, and keep moving until all the silos were full. Only, the tripper wasn’t working correctly, so it wouldn’t detect that the silo was full so the belt would keep dumping coal and would end up spilling coal all over the entire tripper gallery which runs about 100 feet or so.
So, our first experience with doing coal cleanup was like being on a chain gang where we shoveled coal from morning until night trying to clean up these 15 or so major coal spills from the Trippers on back to the the first belts 4, 5, 6 and 7 by shoveling the coal back onto the conveyor while it was running. In some cases, we had to shovel the coal away from the belt before the belt could even run (as was the case with belts 12 and 13). So, you can imagine how shoveling coal one scoop at a time made it seem like you were not getting anywhere fast. 3 or 4 men could all be shoveling on one pile of coal for 30 minutes and not even make a noticeable dent in the pile. That is why when I went to the tool room to choose a shovel, instead of picking a regular shovel, I picked a large scoop shovel used to scoop grain.
Scoop Shovel
Regular Shovel
Even though each scoop of coal was heavier, it seemed more satisfying to see the bigger dent in the pile of coal with each shovelful. I remember one day after we had shoveled coal all day from morning until late at night only to come back into work the next morning to the new piles of coal just as big as the ones we had shoveled the day before. Once we had cleaned everything up they started up the conveyors again only to have it do the same thing as before.
After 2 years of volunteer coal cleanup which was becoming less volunteer and more rotational since the list of volunteers was growing smaller, Ray Butler pointed out that it didn’t make much sense to pay a first class machinist overtime to shovel coal when you could create a labor crew and pay them bottom dollar to do coal cleanup all the time, as well as other dirty jobs that no one really wanted to do (such as suck out sewage pits and other sump pits around the plant).
That was when the Labor crew was formed. While I was in my 3rd year as a summer help (1981). Bill Cook was a summer help then that stayed on as a labor crew hand at the end of the summer. By the 4th summer as summer help, the only time we did coal cleanup was when there was a major spill, which was only a couple of times all summer.
I will write later about coal cleanup with Dale Hull. I also remember doing coal-cleanup with Preston Jenkins one weekend. I hadn’t carpooled with him to work, but I caught a ride back to Stillwater with him because my ride left at the end of a full day, and I decided to stay behind to add a few extra dollars to my bank account. We left a couple of hours later around seven o’clock.
I climbed into the back of Preston’s Camaro. I apologized for being so dirty, as I was covered from head-to-toe in coal-dust and my clothes were soaked with coal-dust permeated sweat. Preston said that he didn’t mind. I soon found out why.
When I climbed into the backseat of his car, I noticed that the upholstery that covered the seat back of the back seat was stained with some blackish-brownish um…. something. Anyway. I decided to sit on the passenger side of the back seat instead of behind the driver side because that side wasn’t nearly as stained. As we drove down the highway toward home, I quickly learned why the seat back was so stained.
Being the “good-ol’ boy” that Preston was, when he climbed into the car, he took out his can of Skoal and put a pinch between his cheek and gums:
Just a pinch between your cheek and gums…. Never tried it myself.
As we flew down the highway like a Texan heading for Stillwater, Preston would lean his head out the window and squirt out a wad of spit. It would dance in the air like a little fairy just before it would be sucked into the back window of his car and splat against the seat back of the back seat. Yep that explained it all right. I always wondered if he knew, never having to sit in the back seat of his own car.
During the first summer when I was able to catch a ride with David Hankins a couple of times. He was the crane operator at the time and drove a black Trans Am. He was a black man with a very broad chest that never seemed to tire while doing coal cleanup. From the first day he always treated me with great respect which in turn gave me a great respect for him. I had him classified as a true Power Plant Man.
The second summer when I had been back at the plant for a couple of weeks, one day when Jim Heflin and I were going somewhere in a yellow Cushman cart, I asked Jim why I hadn’t seen David Hankins around.
A Cushman Cart Like this only Yellow
Jim (who hadn’t been at the plant the first summer) stopped the cart in the middle of the road and looked at me very solemnly and told me that David Hankins had died in a car accident in the spring. He had been going home from a Men’s Club event when he was killed. Because of this, alcoholic beverages were no longer allowed at Men’s Club events. As with all the people I have worked with at the power plant, I keep David Hankins in my memory and I often think about him to this day. David Hankins was a True Power Plant Man.
Comments from the original Post:
-
neenergyobserver June 1, 2012 as 6:28 pm
We’ve lost so many friends over the years, in the plants and on the line, especially when they were relaxing on their way home. You, and David’s family have my very belated condolences.
Somebody, somewhere, needs to teach engineers a course on Conveyor Logic 101, I’ve seen the same thing happen in nearly every plant (from automotive, rarely, to meat packing, often) I’ve been in. Or they could, just for once in their life, shut their pie-hole and listen to people like you and me.
-
Plant Electrician June 1, 2012 at 11:39 pm
Thanks Nebraska.
We were often exhausted while driving home from work when we had been working a lot of overtime. It was a wonder sometimes that we were able to keep the car on the road.
My uncle Bill Breazile worked for the Utility company in Nebraska City where someone closed a breaker while he was working on a line. He was in the hospital for about 6 months healing from his burns. This was about 30 years ago. He has since passed away. It takes a special person to be a lineman. Putting their life on the line every time they reach out to do their job.
-
neenergyobserver June 2, 2012 at 10:42 am
Not that different from you. It’s all about planning your work, and doing it right, and safely. You and I know that 480 will kill you just as quick as 7200 if you get careless. That’s why almost all (old) linemen and electricians are in some sense stolid and unexcitable.
-
-
-
jackcurtis July 14, 2012 at 12:59 pm
Industrial America returns in stories and comments in places like this, from the only place it still exists: the minds of those who were part of it. Industrial America was a giant; those who manned it were giant tamers and it seems to me, very much the special breed illuminated in these posts…
Comment from last repost:
-
I remember a time when I would have chose the bigger shovel, perhaps in the early 70’s. I was moving steel in a manufacturing plant. Carrying three bars on each shoulder seemed better than the two they suggested. We finished earlier, had to do other work, but somehow it felt better. Thanks for another interesting story and a wake-up call to younger days. Thanks also for the explanations. I love mechanical things and I get the impression that these plants are one big mechanical adventure.
-
Mr. Frog’s Wild Power Plant Ride
Favorites Post #57
Originally post October 10, 2015
I woke up from a dream this past Wednesday where I had just insulted a young lady who had cancer treatment by calling her “baldy”. In the dream I was attempting to be funny, but as soon as I said it, I knew I had crossed the line of common courtesy. I acknowledged right away that “I shouldn’t have said that”, and rose from my chair to go find whoever it was so that I could apologize. In my dream I was never able to find the person, though I thoroughly searched whatever restaurant-factory-office building we were in. You know how thing are in dreams.
I preface this post with that thought because someone may take offense to the title I have chosen today. So, let me just say that this is a story about someone that has been the source of constant conversation in my family for the past 30 years. Though I never refer to him as “Frog”, that is a title reserved for one of this man’s best friends. It is an expression of friendship bestowed upon Walt Oswalt by Ray Eberle.
Walt Oswalt
Ray Eberle is the most amazing storyteller of our time. He captivated Power Plant audiences for the past 40 years up until the day he recently retired. I have heard hundreds of stories by Ray, but none of them were ever said with more compassion and humor than the stories that Ray Eberle would tell me about our fellow Power Plant Man, Walt Oswalt.
Ray Eberle
I used to think that Walt’s parents named him Walt so that it would be easy for him to spell his entire name. Once he learned his first name, he just had to add an OS to it, and he could spell his last name. Well, actually, his full name was Walter Lee Oswalt. But whose counting? I also thought that OD McGaha (prounounced Muh Gay Hay) was in a similar situation, because OD simply stood for OD (prounounced O-D or Oh Dee). Not to forget Dee Ball. I’ll bet all of these guys could spell their names by the time they graduated the third grade.
Look closely at Ray Eberle’s picture above, because if you look closely into his eyes you can see that back behind those orbs, thousands of wonderful stories are packed in there waiting to be told. I don’t know if I have mentioned this in a post before, but Ray looks just like my grandfather when he was younger. I think I mentioned that to Ray one day. Since those days when we used to sit side-by-side working on the computers in the Coal-fired Power Plant in North Central Oklahoma, I have loved Ray with all my heart as if he is a member of my family (see the post: “Tales of Power Plant Prowess by Ray Eberle“).
Even though this post is about Walt Oswalt, I am spending an unusual amount of time talking about Ray, because the stories I am about to relay are told through the eyes of Ray. I have already passed on some stories about Walt in other posts, so I will focus on those stories about Walt experienced by Ray. I will only scratch the surface today, as it takes some time to absorb the universal significance of each story. If I flood you with too many Walt Oswalt stories at once it may cause confusion. I appreciated the fact that Ray didn’t lay all his Walt Oswalt stories on me in one sitting for this very reason.
Ray Eberle began his stories about Walt by telling me about going over to Jimmy Moore’s new house. Jimmy had just moved into a new house outside Morrison Oklahoma not too far from Ray. Ray described how nice the property was at the time. It was a picture perfect piece of property. The surrounding fields were pristine giving the feeling of peace when you looked around.
Jimmie Moore expression after moving into his nice house
Note the Sparco notepad in Jimmy’s pocket. A Power Plant Electrician Necessity, just like the notepads I always used:
One of My Power Plant Sparco Wirebound Memo Books
Just when Ray was soaking in the perfection of Jimmy’s new property, dreaming that he could have found such a great spot, Jimmy mentioned that Walt Oswalt bought the property across the road. Ray’s response was “Frog bought the land across the road? Oh no!” Not wanting to upset Jimmy, he didn’t say anything else, but he was thinking it…. You see, Walt is sort of a “junk collector”.
I have always been a junk collector myself, as you may have figured out by the fact that I still have a notepad left over from Christmas 1995. Actually, I could take a picture of the Sparco notepads I have kept from my time at the power plant and it would look like this:
My personal collection of used Power Plant Sparco Notepads
So, I was a note taker… Each page of these notepads are filled with work order numbers, part numbers, phrases I heard, Things Gone Right, Things Gone Wrong meeting notes, Meeting schedules, tools needed, and sometimes just thoughts that came to my mind. I am mentioning this because I have this common bond with Walt. We both like to collect things that others see as “junk”.
Ray was worried that after Walt moved in across the road that the Beatrice Potter Meadow was going to change into Fallout 3 terrain (well, my phrases, not his, but I think you can picture what I am saying). From what I understand, this is what happened. — This by the way is not a Walt Oswalt Story. This has been more of a Jimmy Moore story.
I have been waiting so long to actually write down a Walt Oswalt Story that I actually find it hard to bring myself to put it down on virtual paper, but here goes….
Here begins the first Walt Oswalt Story:
In the mid-90s the Internet was something of a new phenomenon. I had taught most of the Power Plant Men how to use the Internet (excluding upper management) as you can read in the post: “Power Plant Quest for the Internet“. One person who immediately saw the benefit of using the Internet beyond looking up indecent pictures or connecting with clandestine online “Match.com” experiences was Walt Oswalt. Walt saw “business opportunity”!
So, follow me on this story, because Walt stories can become complicated on paper because I can’t talk using my hands. I may need some help from Walt’s son Edward, since he played a major role in this one…
One day, Walt and Ray were talking and Walt told Ray that he was looking at buying a dump truck. Let me just show a picture of a dump truck, even though I don’t know the specific truck Walt had in mind. I just know the approximate size:
A Ford Dump Truck
Let’s just suppose that it is a truck like this…. anyway, Walt explained to Ray that he could buy the truck he wanted up in Wichita one hundred miles away. However, Walt wasn’t going to do that. He had found the same truck on the Internet for sale for $500 cheaper near Virginia Beach, Virginia, 1,400 miles away.
Ray asked, “But isn’t it going to cost you more than that to have the truck shipped to Oklahoma?” “Oh, I have that all figured out. I’m going to go pick it up myself.” He went on to explain that he and his son (this is where Edward enters the story) were going to drive non-stop to Virginia Beach and pick it up. They won’t have to stop because they can trade off driving while the other rests.
A Flat Bed Trailer
So, a marathon trip for 2,800 miles was planned. Walt had a trailer attached to his truck to bring the new truck back… Though I’m not sure why the thought that they could just drive the new truck home wasn’t considered (or flying out there and driving the truck back, but then, that would cost more than the $500 they were saving by buying the truck)…. The plan was that they would load the truck on the trailer and haul it home. Maybe it was so that they didn’t have to stop because they could swap off driving if they were only driving one of the two trucks.
Two members of the Oswalt family took off for the East Coast one Friday evening. They arrived early Sunday morning at the place of business where they were going to purchase the truck. From what I understand, the business was closed, (being Sunday, and all), so they called the owner and told him they were there to pick up the truck. After waiting a few hours, the truck was purchased, and Walt and Edward were on their way back home.
A couple of days later, Ray noticed that Walt had made it back home, so he went over to his house to see how he managed. Obviously, after travelling 2,800 miles in four days, the two were bushed, but the new truck was finally home. While Ray was talking to Walt about his trip, he happened to notice that the back of the dump truck was loaded with blown out tires.
“Hey Walt, what’s up with all the tires?” Ray asked. “Oh. Those.” Walt replied…. “Well, the trailer wasn’t really big enough to carry this much weight, so we kept blowing out tires on the trailer when we were coming home.” They must have blown out more than 20 tires driving home. So, it seems to me that this turned out to be a pretty costly savings of $500.
I would leave this story at that, but after a couple of trips to Los Angeles and back from Round Rock, TX, I have to say that spending countless hours with your family in the car where there is nothing to do but to talk to each other is an incredibly priceless experience. Once, my son Anthony and I drove the same distance, 1400 miles non-stop from Los Angeles to Round Rock without stopping (which is implied by calling it “non-stop”) and we talked the entire time. I would say it is an experience worth a million bucks.
The night before last, I received a message on Facebook from a Power Plant Technician, Doug Black. He wrote: Sooner retiree, Walter Oswalt passed away on September 30, 2015. Walter will be laid to rest at Yukon Cemetery with a grave service on October 23, at 2 p.m.
Doug Black
I looked up Walt’s Obituary, and it seemed to me that there was one phrase missing from the description. It said that “Walt had went to work for OG&E in Mustang Oklahoma and later retired from the OG&E plant in Redrock…” I didn’t see the words, “Power Plant Legend” mentioned anywhere in the Obituary. It should be mentioned, because that’s exactly who Walt Oswalt is.
I may not have had the benefit of sitting in a truck with Walt for 20 hours at a time, but I was able to work one-on-one with Walt one day for 19 hours straight on a Saturday when we were on “Coal Cleanup” that had turned into a job repairing conveyor belt rollers. During that day, while I was a young man of 20, I went through the motions directed by Walt to remove and install rollers on the number 10 belt up toward the top.
Coal conveyor carrying coal to the coal silos from the coalyard
I didn’t have much of a clue about what I was doing, but I had placed all my confidence in Walt. I felt the entire time as if Walt was keeping me safe in a potentially unsafe situation even after being awake for 19 hours. So, I have a little knowledge of what the road trip was like that Walt and his son Edward took “There and Back Again.”
It may seem that Walt had made a bad decision to make the Internet Purchase of a truck 1,400 miles away in order to save $500, but I think that God helps us along some times by sending us down a path that seems a little foolish, only to force us into a benefit we would not otherwise encounter. I keep Walt in mind whenever things like that happen to me today and I thank him for keeping me from being disappointed with those times in my life.
Now that Walt has met his maker, I’m sure that Walt is sitting there with Jesus Christ reviewing not only Walt’s life, but also Ray Eberle’s retelling of Walt’s story. Walt may now be surprised to find that moments that he thought were rather insignificant to anyone but himself have actually been spread to others across the world. As I mentioned in the post about Ray Eberle, a few years ago, CEOs of large companies across the U.S. were all learning about the “Wisdom of Walt”. Some day I wouldn’t be surprised to find that the Walt Oswalt Stories have become required reading in Oklahoma Schools.
Rest in Peace Walt Oswalt. We all love you.
Walt Oswalt
Since this was originally posted, Jimmie Moore has also passed away. I visited his grave this past summer in Morrison, Oklahoma on July 17, 2018. Jimmie was always a steady presence in the Electric Shop when I worked there. He was the more “grown-up” member of the family. Now that he has joined many of his Power Plant friends in heaven I’m sure his steady presence is much appreciated.
Comments from previous post
What a wonderful eulogy for a friend. We have a couple of “Walts” at our our paper mill–legends both at work and in their community and families. And very loved by most that they have the opportunity to spend time with. 🙂 They are few and far between and appreciated much more than they themselves will ever understand.
P.S. Do all industrial sites use those Sparco note pads?!! LOL!!
-
Thanks Jill for your kind words. Any factory that wants a high quality notepad will find that the Sparco notepad is reliable, dependable and just about the most fashionable notepad on the market.
Power Plant Birthday Phantom
Favorites Post #55
Originally posted March 14, 2015
Long before Facebook ever graced the pages of our browsers, Power Plant Birthday reminders began appearing in the Outlook E-mail Inboxes of Power Plant men at the Coal-fired Power Plant in North Central Oklahoma. Today it seems commonplace to be reminded of your friends birthdays as your smartphone pops up a message to remind you. In 1997, a strange event began happening at the plant. It sent some scurrying about to find the culprit. Others found it funny. Some worried that their secrets were about to be revealed. One person was totally surprised by the response (me).
January 3, 1997 Charles Foster and I went to our morning meeting with our team in the main break room where we would meet every morning to go over the work for the day. Alan Kramer began the meeting by asking me a direct question. He said something like, “Kevin. Do you know anything about emails from the Birthday Phantom?” I asked him what he meant, and he went on to explain.
Our Foreman Alan Kramer
Alan said that when someone opened up Outlook to check their e-mail that morning, shortly after they opened it up, an e-mail appeared in their inbox that was from themselves. So, when Alan had logged in that morning, he received an e-mail from Alan Kramer. When he opened it, it had a subject of “Today is Wayne Cranford’s Birthday”. The body of the e-mail said, “Today is Wayne Cranford’s Birthday. He is 48 years old today. Please wish him a Happy Birthday. The Birthday Phantom.”
Wayne Cranford is the bald guy front and center on one knee between David Evans and John Costello
It happened that when Wayne Cranford opened his own e-mail, the subject said, “Happy Birthday Wayne Cranford!” and the body of the email had the happy birthday song, “Happy Birthday to you. Happy Birthday to you. Happy Birthday dear Wayne. Happy Birthday to you. The Birthday Phantom.
So, after Alan explained this to me, he looked at me again with a rather stern look and said, “Kevin. Did you do this?” What could I say? So, I said, “Why is it that whenever something like this happens, I’m always the first one to be blamed for it?”. I knew at that point that Alan’s next response was going to mean the difference between night and day, so I put on the most indignant look I could.
Alan said, “Well. I just had to ask.” I shrugged like I understood and glanced over at Charles Foster who had a stunned look hidden behind his best poker face. Something like this:
Charles Foster
You see…. about a year earlier, before we were using Microsoft Outlook, we were using Novell’s Groupwise for email. Alan Kramer had come to me and asked me if I had done something “wrong” in regard to emails. It turned out that I was innocent of any “wrongdoing” in that instance (well, almost). Charles Foster was my witness.
What had happened was that one day, Danny Cain, who was the Instrument and Controls person on our team had come into the electric shop office to make a phone call to someone at Corporate Headquarters in Oklahoma City. I think it was Ed Mayberry. Email was a new idea for most people at the plant.
Danny Cain
While Danny was on the phone, I turned to the computer sitting on the desk across the room from Danny and wrote an e-mail to the person that Danny was talking to telling him not to believe a word Danny was saying… whatever it was…. it wasn’t important. I just thought it would be funny to send an email to Ed about Danny while he was talking to Danny on the phone.
The subject of the email was “Danny Cain”. As Danny was talking on the phone, he happened to turn around just as I was clicking “Send”, and he saw his name in the subject line. Charles was sitting there next to me, as we were on break at the time. Danny quickly asked what I was doing and why did he see his name on an e-mail. I put on the guiltiest look I could and said, “Oh. Nothing. Nothing at all.” Rolling my eyes with obvious guilt.
I didn’t know how much this bugged Danny until a couple of days later Alan came into the electric shop office and said he needed to ask me a serious question. I could tell he was upset with me. He asked, “Have you been reading other people’s emails?” I was confused by the question, because I didn’t relate it to Danny from the other day. So both Charles and I looked confused.
I told Alan that not only had I not read other people’s emails, but even if I could, I wouldn’t because I considered other people’s emails private. Then I explained to him that Novell’s Groupwise email was very secure, and I wouldn’t know how to hack into their email if I had a desire. Which I didn’t.
Novell’s Groupwise
Still confused by why Alan would ask the question both Charles and I asked Alan what this was all about. He didn’t want to say who it was that told him they thought I was reading their emails, but after we pressed him, he told us that Danny Cain said he saw me reading his email when he was in the office. Then both Charles and I knew what this was all about.
I explained to Alan that I was just joking around with Danny at the time. I reasoned with Alan that I would have to be pretty stupid to wait until Danny was standing a few feet away from me before I decided to read his emails. Alan accepted my explanation. Especially since it was backed by one of the most honest people at the plant, Charles Foster.
So, fast forward to November 6, 1996. We were now using Outlook. That was about as secure as a bag of Oreo cookies in a kindergarten classroom.
I was sitting in the electric shop office with Charles during lunch, and I had just finished writing some fun little programs that automated pulling stock prices from the Internet and putting them in Excel each day. I asked Charles, “What shall I do next?”
Charles thought for a few moments and said, “You know when we were still all in the electric shop before the downsizing, how when it was someone’s birthday we used to celebrate it by bringing a cake and having a lunch or something for that person? Well. We don’t do anything now. Can you come up with something that will help celebrate birthdays?”
After brainstorming ideas, we settled on sending emails and the “Birthday Phantom” was born. I thought it would be neat to learn how to write programs that used the Outlook API, sending emails, and stuff like that. So, I went to work during my lunch breaks writing the program.
It only took a week or so to get it working, and then we ran a bunch of tests on it until we settled on having the emails be sent by the same person that is receiving the email when they log on the computer. Each time a person logs on the computer, the program would be kicked off.
The first thing it would do was check to see if the person had already logged on that day. If they had logged on before, then it would shutdown because I didn’t want it to send more than one email for the same day, even if the person used a different computer.
The next thing it would check was if the person was on an exception list. We had decided that it was best to keep the plant manager and his cronies… um… I mean, his staff from receiving emails, as we didn’t think they would appreciate it since they didn’t have much use for such things. If the person logging on was on the exceptions list, the application would shutdown.
Then, it would check to see if it was anyone’s birthday that day. If it was, then it would send an email from the person logged on, to the person logged on. If it was the birthday of the person logging on, then it would modify the email so that it was personalized to say happy birthday to them.
There were little tweeks I made while testing the application before we went live with it. First, I added little things like making sure the gender was correct. So, if it was a woman’s birthday, then it would say “…wish her a happy birthday”.
Charles and I decided that the application would start running on January 1, 1997. So, during December, I made sure it was setup on all the computers in the plant except those belonging to the staff. This brings us to January 3, 1997, when Wayne Cranford was the first Power Plant Man to have a birthday.
As I hinted above, Alan’s response to my indignation at being accused of creating the Birthday Phantom would have determined how short-lived the Birthday Phantom would have been. Since Alan didn’t pursue the inquiry I didn’t offer any more information.
For instance. A few minutes after the meeting was over, I walked over the control room, and the control room operators were all standing around talking about the Birthday Phantom. David Evans asked me if I was the Birthday Phantom. I responded the same way I did with Alan, I said, “Why is it that when something like this happens, I am always the first person to be accused?” David responded with, “Yeah, but are you the Birthday Phantom?” Well. I wasn’t the type of person to blatantly lie, so I had to admit that “Yes. I’m the Birthday Phantom, but don’t tell anyone.” The Control room operators said they would all keep it to themselves (yeah. right).
Though some people thought the Birthday Phantom was a nuisance, others thought that their personal emails were at risk, and that the Birthday Phantom could be stealing their emails. Whenever I heard that anyone was upset (such as Alan) with the Birthday Phantom, I just added them to the exceptions list and they never received another Birthday Phantom email.
Jim Padgett, a Shift Supervisor, had received a Birthday Phantom email one day, and called IT to report it as they were trying to track down the program to figure out where it was coming from. Jim Cave told me that Padgett had the IT guy on the phone and he was logged into his computer to watch what happened when he logged on and opened up Outlook to try and find what was sending the emails.
Jim Padgett is on the far left standing next to Jim Cave in the Jean Jacket.
Jim Cave said that the IT guy was sounding hopeful that he was going to finally be able to catch the Birthday Phantom when all of the sudden he said, “Oh! That’s a Wiley One!” I came to understand that in Oklahoma City, the IT department was taking this so seriously that they assigned two people full time for two weeks to try and find the culprit (I added Jim Padgett to the exception list, so he didn’t receive any more emails).
I hadn’t thought about it when I was writing the application, but back at Corporate Headquarters, they thought that the application had somehow gained access to the HR system in order to find the birthdays of each employee. Even though, things like Birthdays and Social Security Numbers were not as sensitive in 1997 (for instance, the plant manager’s Social Security Number was 430-68-…. You really didn’t think I would put his Social Security number here did you?), if someone was accessing the HR database, that would have been serious.
Even though the IT department was taking this very seriously, there was one timekeeper at the Power Plant that was just about climbing the walls over the Birthday Phantom. She was so concerned that I was afraid she was on the verge of a nervous breakdown. I was not surprised by this at all, and had actually anticipated her anxiety. Actually, the Birthday Phantom was designed for just this reason. You see, this particular timekeeper was going to be turning 40 years old one week after the first Birthday Phantom email showed up.
After the second Birthday Phantom email arrived the next Monday on January 6, announcing that Jerry Potter had just turned 36, Linda Shiever called me and asked me if I could find out how to stop the Birthday Phantom. I told her I would look into it. I did look into it for about one second. Linda was turning 40 on Friday.
Linda Shiever
On Wednesday, January 8, not only did Elvis Presley turn 62 (if he had been alive… or…. um…well, you know…) but the Birthday Phantom informed everyone at the plant that Sonny Kendrick (who was only 5 days younger than Wayne Cranford) had also turned 48 years old. Linda Shiever was thinking about calling in sick on Friday.
Linda knew that when she came to work the morning of January 10, that her cube would be full of black balloons with the number 40 on them. She had resigned herself to this a while before when she helped blow up the balloons for Louise Kalicki’s cube the previous August 23, less than 5 months earlier. The appearance of the Birthday Phantom, however, had thrown in a new element of recognition.
The morning of January 10, 1997 finally arrived, and the Birthday Phantom email notified everyone that it was not only Linda Shiever’s birthday, but it was also Gene Day’s birthday as well. Yeah. The application could handle multiple birthdays on the same day. Linda Shiever was happy to find out that the Birthday Phantom had informed the entire Power Plant that she had just turned 29. In fact, that year, every woman at the plant was turning 29 years old according to the Birthday Phantom. — That was another one of those tweeks that came out of our testing.
Gene Day, on the other hand, according to the Birthday Phantom had just turned 100 years old…. Well.. Everyone knew he was ancient (See the post: “Power Plant Humor and Joking With Gene Day” and the “Psychological Profile of a Control Room Operator“). Needless to say, there was a lot less stress in the office area after that day.
The following week, when I went to the tool room to get some supplies, Darlene Mitchell stopped me and asked me if the Birthday Phantom would do her a favor. She was turning 45 years old on January 28, and she didn’t want the Birthday Phantom to tell everyone she was 29. She wanted it to say, “Today is Darlene Mitchell’s Birthday, She is 45 years old and Lovin’ it! Please wish her a Happy Birthday!” I told her I would have a talk with the Birthday Phantom and it shouldn’t be a problem.
Darlene Mitchell, a dear friend of the Birthday Phantom
After a month, when I was in the Control Room, Jim Cave, who was now referring to me regularly as “The Wiley One” said that the IT department had told Jack Maloy that they were no longer looking for the Birthday Phantom. They were not able to find it. The person that did it would just have to tell them who it was.
I still have the computer code I used when I wrote the program. Sometimes I take it out and read it and I remember that year when the Birthday Phantom visited the Power Plant in North Central Oklahoma to remind everyone that we were all growing older and as a family, we should take the time to stop and say “Happy Birthday” to each other on that one day each year when we are special.
Page 1 of the Birthday Phantom Code
Printing Impossible Power Plant Fast News Post
Favorites Post #54
Originally posted: July 12, 2014:
Tom Gibson, the Electric Supervisor at the Coal-fired Power Plant in North Central Oklahoma didn’t have a clue the large can of worms he opened the day in 1988 when he told me to find out all I could about the company computer in Corporate Headquarters…. The one that ran all the important financial systems for the company. I remember going straight down to the Electric Shop office and sending a request for a username on the Honeywell Mainframe to the IT department, with Tom’s approval.
A Honeywell Mainframe computer
This story is a continuation of two previous stories…. Last week I wrote a post called: “Power Plant Customer Service Team Gone Wild“. This is the next shoe that dropped in that story…. Earlier this year I wrote a post called: “Toby O’Brien and Doing the Impossible“. Well, this is the second story in the list of “Impossible Things” Power Plant Electricians were able to accomplish when others said it couldn’t be done.
As a reminder… and in case you didn’t read last week’s post…. as a summary….. let me just say that I had printed out a form on every printer in the company as part of a “Quality Idea” our team was investigating. In doing so, I sent commands to the printers to change their quality settings, as well as the Font Size and a few other settings. When I ran the little known command that sent the document to every printer listed on the mainframe, I didn’t realize that this included all the billing, paycheck and work order printers that all had their special kinds of paper and setting for those particular jobs to run.
This was probably the biggest “Faux Pas” (pronounced “Foe Paw” — yeah…. French… which literally means: “False Step”) of my 18 years as an Electrician. Before I tell you about how the second shoe dropped… Let me explain that a few weeks before I had hit enter on the keyboard sending the disastrous command to the Mainframe, In June, 1993, I had found an interesting program on the Honeywell mainframe called “Magna 8”.
It had to do with creating reports from the main database. This was the entire database that ran the Electric Company Business! I thought this would be a great program to learn in order to create all kinds of reports for our plant that would help us understand where our efforts were being spent. I thought I might actually be able to tie our Maintenance Orders to the time the employees spent on them to their wages, and to the cost of the parts used…. Nothing like that existed at the time, and the little I was able to read from the Magna 8 User Manual on the mainframe, this seemed like just the ticket..
We had never heard of SAP, or other ERP systems at the time. — Oh… sorry… ERP stands for “Enterprise Resource Planning”. It does just that. It combines all the company’s business together in one application so that you can account for all the costs down to each machine, person, and part. If I could learn more about Magna 8, maybe I could start piecing these pieces together from the database. I was having one problem…. When I would page down in the user manual, it kept skipping the bottom half of every page….
I couldn’t figure out how to stop it from scrolling past the second half of each page. So, I called in a favor from the IT guys downtown and asked them if they could send me a printed copy of the Magna 8 User’s Manual. They said they would be glad to send me a copy. About a week later, I received the User Manual through company mail. It was about 4 inches thick.
There were different sections. One was called: “The Update Module”. Yeah…. That’s right…. It was used to enter data into the database…. I thought about that module for about 2 seconds and decided It would be best to stay away from that one. Then there was the “Reporting Module”.
That was the one I was looking for. — on a side note…. I know “for” is a preposition, and I know you aren’t supposed to end a sentence in a preposition, however, who doesn’t say, “That’s what I was looking for”? In these circumstances, I figure that I better approach it from a whole different angle…. like…. “That’s the section I really wanted.” — End side note.
A couple of weeks after I received the copy of the Magna 8 User Guide, I sent the infamous form to all the printers in the company, and that’s when I was sort of had all my “atta boys” taken away with that one “Uh Oh”. I was all prepared to watch my step while on the mainframe. About a week after the episode in Tom’s office when he told me not to send anything outside the plant without Ron Kilman’s permission, my foreman, Andy Tubbs came in the office and told me that in two days, I was supposed to go to some training in Oklahoma City.
“Oh. Training!” One of my favorite things! I always liked to learn new things. I asked Andy what the training was for (Oh geez… did I really say that? “For” at the end of the sentence again! — how about “I asked Andy what kind of training would I be taking” — yeah…. that’s what I said…). Andy replied, “Something called ‘Magna 8′”.
Oh No! I hadn’t asked for training! I had just asked for the user guide! Now I was scheduled to go to training in Oklahoma City and I knew that no one at the plant had “okay-ed” it. Now what was I supposed to do? I did the only thing I could think of at the time…. I asked Andy where I was supposed to go at Corporate Headquarters for the class.
Since I knew that this class hadn’t been approved by Tom Gibson or even our A Foreman Bill Bennett, I decided that I was going to go on my own dime…. that is, I wasn’t going to expense anything. I would pay for my own mileage and lunch, etc. Hopefully, no one would notice that I was gone that day. — Anyway, I could always fall back on the fact that my own Foreman Andy had told me to go….
So, when the day came, I drove to Oklahoma City and entered Corporate Headquarters dressed in my cleanest steel-toed work boots and my cleanest tee-shirt!
I chose this picture because they look like my boots, only I never wore the toes out so that you could see the steel toes.
Yeah. Just like this — no not really
When I introduced myself to the instructor, Scott Overmeyer, I told him I was surprised that I had been scheduled for this class. He told me that since I had requested the User Guide that he figured that I should attend this course so that I would know how to use Magna 8 to create reports. — Well, that explained it.
The classroom was short on computers so we had to share one computer between two people. I sat in the back row on the right side if you are facing the instructor. A young lady sat next to me. Her name was something like Laura Burgert. We didn’t introduce ourselves right off the bat. We spent the morning learning about how our database was structured.
Our database was not what is referred to as a “relational database”. I’m not even sure if that term was being used at the time…. anyway, we had what is called a “Hierarchical Database”. The relationships are more like a family tree. If you needed to connect the data, you had to go up the tree to where you could go back down another branch… sort of like if you were into Genealogy and you were looking for your 3rd cousin twice removed. This was all new to me.
I found this diagram of a simple Hierarchical Database model on Wikipedia
Anyway, this isn’t an important part of this story, so don’t strain your brain trying to figure it out.
When noon came around and we were just breaking for lunch, Laura Burgert said to me, “You’re Kevin Breazile! Oh my Gosh! You’re the guy that printed out that form on everyone’s printers!” I replied, “Yeah, that’s me. I sure was in trouble for that one.”
She replied that they had been trying to do something like that for a long time. Then she explained… “I work in the Communication Department and we create the Fast News Bulletins that are sent out to the printers….”
You see… this was what you had to do before e-mail was available…. When there was some news about the company that they wanted to disseminate to all the employees quickly, they would send out a Fast News bulletin to the printers and we would post it on the bulletin board in our area.
She continued to explain….. We have asked IT to give us a list of printers that we should send the Fast News Bulletins, because we know that our list is old and we are sending some to printers that messes up billing jobs and other things…. I said, “Yeah. I know all about those.”
She continued to explain some more…. IT told us there isn’t any way to tell which printers are good printers and which ones we shouldn’t be sending Fast News Bulletins. I replied, “Well…. I know which ones are good and which ones are not. I have all the forms that were sent to me. You can tell right away by the paper they are printed on, and if that’s not enough to give you a hint, just read the ‘colorful’ notes they wrote to me trying to convince me not to print on their printers anymore…”
Laura said it would be a great help if I could send those forms to her. I said I would do it as soon as I was back at the plant.
When I arrived at the plant the next morning, and Andy Tubbs told me that Tom Gibson was upset when he found that I had gone to Oklahoma City for training when Bill Bennett had mentioned it to him the day before. He had been all hot because he hadn’t approved any training and here I was going off on my own to Oklahoma City. I told Andy…. “Well…. You did tell me to go….” (looking sheepishly innocent).
Anyway, after that I gathered up the stack of around 500 forms and carried them up to the mail room where Denise Anson helped me put them in a small box to mail them to Laura Burgert.
A few weeks went by and Laura called me on the phone. She asked me how I had created the header on the forms. You see, I had created a header with the name of the company and part of the name was normally smaller and had one word over the top of another so….. well…… let me just show you…..
An example of the Company Memo Header on our Dot Matrix Printer – without the “Quality” turned on.
Notice the “GAS/AND” in the middle of the name of the company…. — This doesn’t look like anything to you today, because we now have laser printers and Publishers and all sorts of Word Art at our fingertips. But back then, printing this from a mainframe document took some work…. let me explain, just to give you an idea.
First, I had to space all the way out to where the word GAS starts, then I had to turn on the underline and decrease the font size to the size of the small letters and print out the word GAS then I had to turn off the underline and backspace the three characters, change the font back to the large size, then backspace all the way back to the beginning of the line, then print out the word Oklahoma and a space, then change the font back to small and print out the word AND then change the font back to the large size, and continue with the rest of the line. Yeah… I had to send backspace commands to the printer…. I was pretty proud of my header.
You can see by the Memo above that I had been using it for almost a year. The picture above isn’t even using the “Quality” setting on the printer which even made it look a lot sharper.
Anyway, on with the story…… The Fast News Bulletin’s header had a simple design. The “F” in Fast was created using a bunch of F’s. The A using a bunch of A’s. Like this:
Yeah… pretty embarass… um… I mean exciting huh? Laura was looking for a way to add some Quality to the Fast News Bulletin. I told her that I could create large block letters using the graphic commands on the printer I asked her what her printer ID was and I quickly created a Fast News Bulletin for her with a real header: 
Laura was excited and said that she may be getting back to me soon…. which she did a few weeks later. She asked if I could attend the first meeting of a new Task Force they had created to enhance the Fast News. I said I would be glad to attend, but I would first have to have permission from my Electric Supervisor before I could go (see? I can actually learn something).
She said she would take care of it…. and she did.
Ben Brandt, our Assistant Plant Manager wanted to know why I was being asked to show up to a Corporate Communication Task Force! — “Uh… I don’t know.” I replied. Knowing that everything I did outside the plant grounds was being questioned after my previous “misstep”.
Memo Ben Brandt Received
So, one day I showed up at Corporate Headquarters again. Laura Burgert was there to greet me. She told me where to sit along a big long table in a meeting room. I was to sit about halfway down the table, while she sat on one end of the table.
When others came in, the IT person that was on the committee… I believe his name was Mike Russell sat on the far end from Laura. Laura opened the meeting by explaining the reason for the task force and when she finished she said, “For starters we were thinking that instead of using the ugly Fast News header we have been using, we would like to have a header like this…. And she passed a copy of the Fast News Bulletin I had printed out on her printer that day when she called me.
When Mike Russell saw it, he replied, “Our Printers can’t print a header like this.” Laura looked over at me, as if she wanted me to reply to Mike’s remark. So, I said, “This was printed out on the standard IBM network printer.”
Mike replied by saying, “No. Our printers can’t print like this. It’s impossible.” I repeated that this Fast News was printed out on Laura’s IBM printer from the mainframe just like the regular Fast News is printed out. I even told him that I could send him a copy of the header so that he could print it out and see for himself.
He said, “There’s no need to do that. Our printers can’t print this out.” — Though he held a bulletin in his hands that was printed out on our Standard IBM printer.
At the end of the meeting Laura thanked me for coming. She said, “See? This is what we have been dealing with. They probably weren’t going to be able to go anywhere with this.” I just nodded…. I thanked her for inviting me and I returned to the plant 75 miles north.
I guess it didn’t matter too much. A few months later and we were all being introduced to E-Mail, as I had been running telephone cable all over the plant so that we could set up a new NT Server network using Netware 4.0. Which used Novell’s GroupWise for e-mail. Fast News then just showed up in our Inbox.
It’s funny how things work out. What are the odds? I wreak havoc by sending a “rogue” form to printers that should be left alone, only to have those forms become useful to another department after I was “accidentally” enrolled in a training course where I happened to sit next to the one person in the company that could benefit from that printing blunder. Which then led her to look at ways to improve the Fast News Bulletin that she was responsible for creating….
Then the IT department refused to listen, but it didn’t matter anyway because new Technology quickly came along which began the process of weaning us off of the mainframe and onto a new state of the art network that later allowed us to use SAP a real ERP system that made the Magna 8 application that I went to learn in the first place obsolete.
I guess the Fast News Bulletin for the day is that Technology Moves Fast…. If you aren’t on for the ride, then you will be making statements like “That’s Impossible” and having a student in the 8th grade proving you wrong. It reminded me of what my dad always said when I was growing up… “Don’t ever say you can’t. — There’s always a way.”
Comments from the original post:
-
-
Great story! I still applaud your initiative, enthusiasm, and risk-taking tenacity.
-
-
Thanks Ron.
I am still amazed by how many times I am told that something is impossible when I’m already doing it.
-
-
-
-
-
How they ever let you get out of there is incredible, I guess you were just real popular all over the company LOL and proved things were not impossible too many times, what a group of talent at Sooner in one place unreal
-
-
That’s true Dave. It may sound like I was some lone wolf out there doing the impossible, but the truth is that we were surrounded by great Power Plant Men doing the impossible every day.
-
-
-
-
-
Great story! I have been working with IT equipment since the early 80’s. The changes have been amazing, but I will never forget listening to a print job that made a printer sing (literally). The new printers are amazing, but the experts could make those first ones do the strangest things.
The problem with the early computers, as you found out the hard way, is that almost any change involved programming. And since that early equipment was so costly, much of the testing had to be done on production equipment…….
Anyway, it seems your management made the sensible decision to chalk up your mistake as part of the costs of training and testing.
-
-
Couple of things…My wife is an IT person and I sent the link to this to her. She loved it.
Corporate Executive Kent Norris Meets Power Plant Men
Favorites Post #52
Originally posted on May 30, 2015
I wonder if Kent Norris felt proud when his boss Wayne Beasley told him that he was being assigned to manage the eight Power Plant Men that were coming to Corporate Headquarters for the next 10 weeks to help prepare for the transition to SAP. I’m sure he had no idea what he was signing up to do. For the next 12 weeks, Kent bravely endured one torture after the other.
Kent Norris was a young Corporate Executive working for the Electric Company in Central Oklahoma when the Power Plant Men showed up at his doorstep August 6, 1996. I wish I had a picture of Kent (Kent… I know you read this blog… if you send me your picture, I’ll add it to this post), because then you could see right away that he would be the perfect person for playing jokes. Just like Gene Day back at the Coal-fired Power Plant where I worked.
Gene Day is the one standing on the right with the Orange shirt.
See, you can tell by Gene Day’s expression that this guy was just right for Power Plant Jokes. Kent Norris was much like Gene in this respect, and the best part was that he was young and wasn’t from a plant, so he had never experienced the Power Plant Lifestyle of perpetual joke playing (see the post “Power Plant Humor and Joking with Gene Day“).
At the plant, Power Plant jokes are such a way of life that they include a section on the timecard to enter the number of Power Plant Jokes performed during the day, along with how many were successfully implemented. This was used to create a PPJ (for Power Plant Joke) Quotient that would go on your performance appraisal each year. That way you could set your stretch goals for the following year.
I explained last week why the eight of us were at Corporate Headquarters in the post: “Do Power Plant Men and Corporate Headquarters Mix?” so I won’t go into that much here other than to say that we were working for 10 weeks preparing the Inventory module in SAP so that our company would be prepared to go live with SAP on January 1, 1997. SAP is an ERP or Enterprise Resource Planning System.
SAP Logo
Once all 9 of us were sitting in one cube, (eight Power Plant Men, and one young Corporate Executive, Kent Norris), that was when the opportunity for Power Plant Jokes began to take shape. Kent sat at the table in the middle of the cube next to the telephone.
Most of the Power Plant Men had their backs to each other as they all faced the edge of the cube. This way, a person walking into the cube could easily see the computer monitors. I sat on the end of a table at the end of the elongated cube where I could watch everyone and no one could see my monitor (and incidentally, I had a great view of the outside world).
At first we began our harassm….uh… I mean… jokes…. on Kent by easing him into it with very simple things… When he would step out of his cube, we would do little things like put water in his pen cap so that when he went to write something down and removed the cap, water would spill on him.
Pen Cap used by Corporate Executives
Other minor pranks were things like, unplugging the keyboard and mouse from the computer so that Kent would think that his computer had locked up. He tried rebooting his computer and for five minutes couldn’t figure out how to fix his computer until he found that the mouse and keyboard were unplugged, at which point, several muffled chuckles could be heard emanating from the far corners of the cube… Not from me, because I had learned the fine art of keeping a straight face in the midst of a hilarious power plant joke — after years of training.
Kent was so good at having jokes played on him that I think he enjoyed them as much as we did. He would respond with phrases like “You guys!!! Geez!” The Power Plant Men were so fast at implementing jokes on the fly that all Kent had to do was turn around to talk to someone that had come to ask a question and all the wheels on his chair would be removed and hidden in various locations throughout the cube.
Ken Scott was the Supervisor of Maintenance at the Seminole Plant, who I had worked with at our plant since I first showed up as a new summer help in 1979. He knew I was a trouble causer from day one. I wondered how he was going to take our constant jokes with Kent, but he helped out with the rest of us, and when Kent would run off to tell his friend Rita Wing (I think that was her name) about a new joke we had just played on him, Ken Scott would break out of his straight “uninterested” expression into a big smile and laugh out loud.
Mike Gibbs and I would evaluate the day’s jokes on the way home each day. We were carpooling from Stillwater.
Mike Gibbs
The jokes became more elaborate over time, and I was reaching out to others beyond our cube to help out. At the time, we were using Windows 3.2 which had small program called “Windows Popup” (I believe the file name was popup.exe). It was sort of an old version of IMing someone before chatting was really common. I taught our team how to use it, so that we could pop up messages on each other’s computers to coordinate our jokes while we were doing our work without having to even look at each other.
Popup means so many things now that we all use Internet Browsers. “Windows Popup” allowed you to locate someone logged into the network, and pop a message right up in the middle of their screen. It would include the logon name of the person popping it up. My logon name on the computer system was BREAZIKJ. The popup message would say Message from BREAZIKJ in the title bar, and it would display the message. Here is an example I found on Google Images:
Windows Popup in Windows 3.2
I had noticed that Kent often talked to the admin for Dennis Dunkelgod, a manager over the Telecommunications team. His office was next to our bullpen cube.
Dennis Dunkelgod
I had worked with Dennis a couple of times running telephone cable at the coal-fired power plant in North Central Oklahoma when we needed to install the computer network, though I don’t think he knew me by sight. I sent a Popup message to his admin asking her if she would help us play a joke on Kent. The message was something like this…. “We are going to play a joke on Kent Norris and were wondering if you would like to help us out.”
The young lady admin didn’t know what to think when this message popped up in the middle of her computer screen, though she knew where it came from because our cube was just across the aisle from her. She took a print screen of the message and gave it to Dennis.
Dennis, not knowing the ways of Power Plant Men didn’t know what I meant by “joke” and thought we might be planning something inappropriate. So he came to our cube and asked who was this person BREAZIKJ. I told him I was Kevin. He asked me if I had sent that message. I told him that I had sent it. (In trouble again… as usual). As Dennis was replying Kent Norris walked into the cube and saw Dennis dressing me down. He was saying that things like this did not belong in the workplace and he didn’t want to hear about this again! I replied, “all right.”
Dennis left the cube, and Kent asked what was going on, so I said, “We were planning on playing a joke on you, and so I asked the admin sitting over there if she would like to help us out and it upset Dennis.” Kent knew that Dennis was just looking out for him, so he explained that to us that Dennis misunderstood our intention.
One joke I played on Kent was this… Since he always answered the phone in our cube, I found a way to connect to a modem on the mainframe and dial out of the company (thanks Craig Henry for the tip), and then dial back in again and ring a phone…. So, I would wait until Kent hung up from the phone, which was just one second after he would say “Toodles” (which was Kent’s way of saying goodbye), then I would ring the phone and hang it back up.
Kent would answer the phone with his regular cheerful telephone answering phrase that I don’t quite remember, but it was something like, “Kent Norris, how may I help you?” only more interesting than that. When he answered the phone the first time, he was surprised to find that no one was on the phone. He hung it up and said, “That’s odd.” Then throughout the week, at various times, just as Kent hung up the phone from a conversation, I would ring his phone again.
Kent began troubleshooting it… he noticed that the ring indicated that it was an outside number calling because of the double ring, but it seemed like the phone was malfunctioning, so he created a trouble ticket to have someone look into it. Of course, the phone was working fine.
One day, Toby O’Brien came to my cube to ask me if I could tell him how I would do a root cause analysis on a particular accident. Toby was working for the safety department at the time.
Power Plant Engineer and Good Friend – Toby O’Brien
I was showing him on the computer how I would make a hierarchy of causes and how each cause could be caused by something else, making something that looks like an organizational chart of causes (when you took this to an extreme, you would find that all causes lead back to God). While I was talking to him, Toby was looking over my shoulder at the computer screen. Kent was talking on the phone… As I was talking to Toby, I was also listening to Kent’s conversation and I could tell he was wrapping it up, and I wanted to ring the phone. I figured that since I was in the middle of a conversation with Toby, this would be great cover for me.
So, as I continued talking along with Toby, I opened up the program I had configured to ring the phone and had it all ready to click the button when Kent said “Toodles”. I could tell that Toby was a little confused by my talking to him while I was opening another program and acting oblivious to it. Still explaining to Toby as if nothing was happening I hit the call button just as Kent hung up the phone, and it immediately rang. As Kent picked it up, I hung up and closed the program. Kent said, “Hello this is Kent Norris….. Damn! Kevin!” as he slammed the receiver back down on the phone. For some reason Kent thought I was doing something, though, he couldn’t figure out what. I just gave him a confused look.
At this point I heard a chuckle from Toby, he had a grin much like his picture above. I couldn’t hold it in much longer as my stomach was beginning to quiver and my body was shaking. So I slunk down in my chair so Kent couldn’t see the smile on my face and put my hand over my eyes to try and concentrate on making a straight face again. I squeaked out “…and that’s how I would do the root cause analysis on that accident.”
A Power Plant Touch Tone Phone
The climax of the Telephone joke was when one day, I set the program up for redial and left to go to the bathroom leaving my screen locked. The phone kept calling Kent once every minute. When I returned to the cube, Kent said, “Kevin! Stop ringing my phone!” I said, “I just went to the bathroom! How could I be ringing your phone?” At that point the phone rang and Kent said, “Pick it up!” I picked it up and listened, and said, “There’s nobody there. But you can’t blame me for that.” Then I returned to my computer and turned off the program and didn’t call him anymore after that.
The most elaborate joke played on Kent began when one day Kent made the statement that he had never been to a Power Plant and had no desire in the world to ever visit a Power Plant! I think someone had asked him if he had seen the control room at one of the plants and that was his response. So, when an opening for an operator came up at our plant, we told Kent that we had sent in his application for the Operator job at the coal-fired Power Plant in North Central Oklahoma.
Who wouldn’t want to see this?
Kent didn’t believe us of course, he thought this was just another little joke we were playing. We told him that we put all the right things in the application so that he was sure to get the job. Even though he would tell us that he didn’t believe us, we could see the small hint of doubt on his face, which made it a successful small joke… but this was only the beginning.
A couple of weeks later, Kent received word that since all the engineers were up at our plant in North Central Oklahoma they were going to hold their monthly safety meeting there and Kent and Rita were going to have to drive up to the plant to attend. Which meant, Kent didn’t have a choice, he was going to have to visit the plant after all. What Kent didn’t know was that his boss Wayne Beasley had been updated by Ken Scott about what we had told Kent about applying him for the operations job at the plant.
We told Kent that the real reason Wayne was having the meeting at the plant was so that Kent would be able to have his interview for the operations job, because they had accepted his application. Of course… again… he thought we were just kidding him since he said he had no desire to even visit a plant in his life. It was quite the coincidence though that shortly after he told us he never wanted to visit a power plant, here he was going to one.
Using Windows Popup (since IM wasn’t around yet), I sent messages to Denise Anson, the receptionist at the plant telling her about our plan with Kent. When Kent and Rita drove up to the main gate at the plant and said that it was Kent Norris and Rita Wing from Corporate Headquarters, Denise replied with, “Oh yes. Kent Norris. You have an interview for the operator position.” Kent said something like, “No, I’m just going to a safety meeting.” At this point, he couldn’t believe that the joke had actually reached the plant.
Denise messaged me using Windows Popup that he had just entered the gate…. I sent a popup to Ron Madron, who was going to ride up in the elevator with him letting him know that Kent was on his way to the parking lot…. When Kent and Rita entered the building and stood at the elevator, Ron Madron entered from the Maintenance Shop and entered the elevator with Kent and Rita. Ron asked who they were and when Kent told Ron who he was, Ron replied with “Oh! You’re the new operator! Good to meet you!” Kent could not believe that we had involved yet another person in our joke…
Ken Scott told me that he had talked to Wayne Beasley, Kent’s manager who was holding the safety meeting. Here is his LinkedIn picture:
Wayne Beasley
Wayne had told Ken that he was going to make an announcement during the Safety Meeting that Kent Norris was going to soon begin working at the plant as their new operator. I messaged to Denise to ask her where Bill Green, the Plant Manager was because I wanted to fill him in on the plan. Denise told me he was in Wayne Beasley’s Safety Meeting.
I asked her if she could go get him out of the meeting because I needed to talk to him right away. So, she went and interrupted the safety meeting to tell Bill that I was on the phone and needed to talk to him. When Bill answered, I told him about the elaborate joke we had been playing on Kent Norris and how Wayne Beasley was going to announce in the meeting that Kent Norris was going to become an operator at the plant. Bill said thanks for letting him know because if he didn’t know it was a joke, he might have been upset if Wayne said that without him knowing it was coming…..
So, here is what happened in the safety meeting….. As the meeting was coming to a close, Bill Green, the Plant Manager, stood up and said, “We would all like to welcome Kent Norris to our plant and hope that he will enjoy coming to work for us as an operator.” — The perfect execution of a power plant joke after weeks of preparation, it was executed flawlessly.
Later that afternoon when Kent came back to our cube at Corporate Headquarters, he said that was the greatest joke ever! He couldn’t believe how we had everyone involved up to the plant manager. We were all glad that it went off without a hitch. We were also glad that Kent had enjoyed it so much. He said that it wasn’t until he walked in the control room and they didn’t know who he was that he felt sure that he really wasn’t going to be an operator at the plant.
The joke where I laughed the hardest was during the last week working at Corporate Headquarters. Wayne Beasley had come back from our plant to work where he normally worked, and he wanted to take our team out to lunch with Kent to congratulate us for doing such a good job. So, they picked a Mexican restaurant in Bricktown just east of downtown Oklahoma City. This restaurant was chosen specifically because it offered a great opportunity for a joke to be played on Kent.
When we walked into the restaurant, Doyle Fullen, the Plant foreman and electrician from Muskogee told the waiter that it was Kent Norris’s birthday. He told them that he was very shy and would deny that it was his birthday, but we were all bringing him out to lunch because we were celebrating it. So, toward the end of the meal, out came the group of waiters singing Felice Navidad carrying a huge Sombrero. Which they placed on Kent’s head!
Google Image of Large Sombrero
We all sang Felice Navidad at the top of our lungs and clapped and laughed. I laughed so hard at Kent’s culmination of Power Plant Jokes! Rarely in my life have I laughed so hard as Kent stood there under this huge sombrero looking humiliated and at the same time proud to be so well loved by the Power Plant Men!
The week ended on Friday afternoon around 3pm, as each of us started leaving one at a time to drive back home for the last time. Doyle and Bob Christy left first because they had the farthest to drive. the rest of us left some time later. Each saying goodbye to Kent a couple at a time…. until Kent was left sitting in the bullpen cube all by himself. Thinking…. “I’m finally rid of these bozos!”
Unknown to Kent, the majority of us didn’t exactly leave the building… instead we each went into the bathroom where I was the last to enter….. I carried a bag that was full of 12 cans of various colors of Silly String:
Power Plant Silly String
Once everyone was ready, we snuck up to the side of the cube where we could hear Kent typing on a computer and with all 12 cans the six of us sprayed silly string over the cube totally covering Kent in Silly String. That was our last goodbye. We couldn’t leave without one more Power Plant Man Joke!
A week or two after I returned to the plant, I received the following letter through Intra-Company mail:
Note I received from Kent after I returned home to our power plant
For years after, and up to today, I consider Kent Norris a dear friend. One day when I was at the Stillwater Public Library during their yearly book sale, I found a book that I just had to buy for Kent. It was perfect! I sent it by intra-company mail. Kent thanked me for it…. I figured it would remind him of the time he spent trying to Corral a passel of Power Plant Men! Oh… here is a picture of the book:
Tootle the Power Plant Coal Train. See the coal spilling out?
Power Plant Men 
I remember in the 1980’s when someone had taken one of the spare annunciator windows out and placed a hand written paper in it that said ” China Syndrome”. It was there for a while.
Thanks Fred for reminding me of that. Um… I didn’t do it!
Jack was from Byng, Oklahoma- a Byng graduate he had attended Okmulgee Tech as well- He worked at Barstow, CA awhile at a plant there- and there training was far different than ours is who he learned so much- he even did some lineman training for them as well as other stuff- I don’t know all his capacity while he was there- he had a lot of experience with combined cycle unit they had but, I know one thing he was a heck of an operator- seen him do some things know one else could ever do- he had the best power plant knowledge of any of the operators ever other than Joe , he, Joe Gallahar, and Padgett were all really good ones. learned a lot from everyone.
LOL You hooked me in early on this one, but as soon as you said “by the way the coffee in his coffee cup would vibrate” I knew which track we were on an enjoyed the rest of the ride. Reminded me of the movie and also the very real stress of Three Mile Island. Funny how your “conspiracy theory” brought those feelings of terror back more than 35 years after I was sitting glued to the TV every day when I came home from high school!
Great story! And 2 great men. Thanks for the memories.
awesome conspiracy story…maybe Jack knew just how to mess with the system, just so he could save it, all in hopes that they would make another movie out of his job.
So anyway, I really enjoyed that. Thanks for sharing.
We got The China Syndrome from the library based on this post! Good movie, it does seem very coincidental the way Jack just sort of appeared at your plant right before the movie came out. I love a good conspiracy theory 😉
God, I must be old. China Syndrome came to mind as soon as you said near tragedy in California plant! I saw this in the theater fresh out of high school. Jane and Jack were incredible by the way. Interesting theories. Anything is possible. And probable. Nice post.