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…
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:
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”.
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).
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 Maloy and Merl Wright from the team picture above:
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?
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:
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…
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?
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)
Favorites Post #72
Originally posted August 30, 2014.
When a death or a near death occurs at a workplace due to an accident, OSHA (Occupational Safety and Health Administration) will investigate what happened. There are two reasons for this. If they find that the company has been negligent in following the safety regulations set down in CFR 1910, then they are fined (if the negligence is severe enough). OSHA also investigates the accident to see if changes are needed to regulations in order to protect employees due to new unsafe workplace conditions that are not currently covered under CFR 1910.
Because of the tragedy that happened at our plant that I outlined in the post: “Tragedy Occurs During Power Plant Safety Meeting” and after I had met with the OSHA man (Gerald Young) to give him my deposition as discussed in the post last week: “The OSHA Man Cometh“, the plant manager, the assistant plant manager, and I were summoned to the Department of Labor building in Oklahoma City at 10 o’clock on Monday April 18, 1994.
On a side note:
The Department of Labor office in Oklahoma City is just a couple of blocks from the Murrah Federal Building that was bombed exactly one year and one day after our visit on April 19, 1995. Not that there was any connection.
I mentioned this because I went to the Murrah building later that day after the meeting with OSHA to meet my brother for lunch. He was working there in the Marine Recruiting office at the time. I think he was a Major then. He changed jobs in June 1994 and moved to Washington D.C.. His replacement was killed in the bombing. Here he is Greg today as a full Marine Colonel:
End of Side Note:
I was asked by Ron Kilman our plant manager to show up at 9:00 am on Monday in the building south of our main corporate headquarters where we rented office space to meet with the guys from our own Safety Department because they were required to attend the OSHA meeting with us. The Department of Labor building was just across the parking lot and across the street from this building, so we planned to walk from there.
I drove myself because Ron said he had other meetings to attend in Oklahoma City after this meeting was over and he wouldn’t be driving back to the plant. That was why I arranged to have lunch with my brother. I figured that word had gone out from Tom Gibson that I talk a lot during long trips, and he just wanted some peace and quiet that morning.
When we met with the Corporate Safety Department Jack Cox told us how we should act during the meeting with OSHA. He didn’t tell us to do anything wrong, like withhold information. He just told us to answer all the questions as truthfully as we could. Don’t offer any information that isn’t directly asked by OSHA. Don’t argue with them if you disagree.
From what I understood from the conversation, we were supposed to be polite, truthful and don’t waste their time going down a rat hole with specifics. I was told that I shouldn’t have to say anything and I should be quiet unless I was asked a specific question. The Safety department would answer all the questions and make any statements that need to be made. I was assured by them that I had nothing to be worried about. I only needed to tell the truth if asked anything.
If you know my personality, I always want to throw in my 2 cents, even when I know it is wasted on the audience. But I took this seriously. We were going to be fined by OSHA for 10 different violations relating to the accident that occurred at the plant. I was there because I was directly in charge of the work that was being done when the accident occurred. It was my deposition that was used to determine about half of the violations.
After we had been briefed on how we should behave during the meeting, as a group we walked from the corporate building over to the Department Of Labor building. One of the safety guys was carrying a few binders. I think one was the company’s Policies and Procedures book (We called it the GP&P).
Upon entering the building we went to the 3rd floor where we were asked to wait in a room until OSHA was ready for the meeting. The room had a long table down the middle. As usual, I picked a seat about halfway down on one side. I remember Ron Kilman sitting across from me and about 2 seats down.
We waited and we waited….. 10:00 came and went, and no one came. We quietly discussed whether this was to make us more nervous by keeping us waiting. Then someone came to the door and apologized. They said that Robert B. Reich, the U.S. Secretary of Labor was in the office that day and that had thrown off everyone’s schedule.
This was quite a coincidence, and we wondered if Robert B. Reich (it seems like you need to put the B in his name in order to say it right) would be attending our meeting. That would sort of throw a whole new importance of me keeping my mouth shut to make sure I wasn’t putting my foot in it.
It seemed as if Mr. Reich had shown up unexpectedly. Or at least on short notice. Almost as if it was a surprise visit to check up on the place. He didn’t end up coming to our meeting. Now that I think about it. This was one day shy of being one year to the date that the Branch Davidians had burned themselves alive in Waco, which was one year and one day before the Murrah Building Bombing three blocks away from where we were sitting that morning. Aren’t coincidences interesting? Just saying…
More about why Robert B. Reich was there further below.
Around 10:30 four or five OSHA lawyers (I assume they were lawyers, they talked like they were), came in the room along with the Jerry that had interviewed me a few weeks earlier. They apologized again for being late due to the arrival of their “supreme” boss. They sort of sat at one end of the room and the people from our company was more on the other end. Jerry, the OSHA man, sat next to me in the middle.
I was saying a mantra to myself…. “Don’t say anything… just keep quiet and listen…. don’t say anything… just keep quiet and listen.
The meeting began by the Lady at the end of the table reading off the violations to us. I don’t remember all 10. I remember the most important violations. They mainly centered around the new Confined Space section of 1910. It was 1910.146 that dealt with confined spaces and it had gone into affect April 1, 1993, almost one year before the accident happened. Generally, OSHA gives companies about a year to comply to the new regulations, which kind of put us right on the edge since the accident at our plant had occurred on March 3, 1994.
Because of this, some of the violations were quickly removed. That lowered the number down to 6 violations right away. That was good. No one from our company had said a word yet, and already the OSHA lawyers seemed to be on our side. Then they read off a violation that said that our company had not implemented the required Confined Space Program as outlined in CFR 1910.146.
This was when our Safety Department leader, Jack Cox. said that we would like to contest that violation, because here is the company policy manual that shows that we implemented the Confined Space Program before the end of the year.
One of the OSHA lawyers responded by saying that we had not fully implemented it because we had not trained the employees how to follow the policy. When he made that statement, Ron Kilman contested it.
He had a stack of papers that showed that each of the employees at the plant had taken the training and had signed a paper saying they had read the policy. Not only that, but the person that was hurt was not a company employee, they were an outside vendor who was hired by the company to vacuum out the hoppers.
The OSHA man said that just because they took the course did not mean that they were properly trained. Ron asked how do you know they weren’t properly trained. The OSHA man replied, “Because they didn’t follow all the rules. If they had, no one would have been hurt.” — What do you say to that? You can tell we weren’t properly trained because someone was hurt? I suppose that the OSHA rules were written in such a way that if you followed them to the letter, no matter what kind of mechanical failure happens, no one will be hurt. I could see the frustration on Ron’s face.
I was a little amused by Ron’s statement though because Jack Cox had told us to just let them answer all the questions and the first seemingly absurd thing the OSHA man had said, Ron had addressed. — I smiled and said to myself…. “Don’t say anything… just keep quiet and listen…”
One of the violations was that we didn’t have a Confined Space Rescue Team. That was true, we didn’t. There was something in the regulations that said, if a rescue team could arrive in a reasonable time from somewhere else, we didn’t have to have our own rescue team…. Well, we lived 20 miles from the nearest fire station equipped with a Confined Space Rescue team. So, there was that…. That was a legitimate violation.
The next violation was that we didn’t have a rescue plan for every confined space in the plant and each confined space was not clearly marked with a Confined Space sign. This was a legitimate violation.
The next violation was that we hadn’t coordinated efforts between different work groups working in confined spaces together. This was clearly stated in the regulations…. — Oh oh. that was me… I think I was mid-mantra when I heard that one. I had just said to myself… “…anything….just keep….” when I heard this violation. I stopped muttering to myself and immediately forgot that I was supposed to keep quiet.
I said, “But wait a minute. We did coordinate between the three groups that were working in the confined spaces. I was coordinating that. I had posted a sheet on a beam in the middle of the hopper area where the accident occurred where the Brown and Root contractors, and the vacuum truck contractors knew what hoppers were still full and which were safe to enter.
I kept the sheet updated each day and so did the vacuum truck workers. They indicated when they had finished vacuuming out a hopper, and I would inspect it from above. When I deemed it safe, the Brown and Root contractors could enter the space. The accident occurred because one of the vacuum truck workers entered the confined space while still cleaning it out and before I had inspected it to make sure it was safe.”
Jerry (the OSHA man that had interviewed me turned and said, “Oh. I didn’t know that. Do you still have that piece of paper?” — Incredibly, I did. About a week after all the vacuuming had finished and all the hoppers were safe, I was walking through the hopper area under the precipitator where I found the paper with the duct tape still on it laying on the grating. Without realizing the importance, I picked it up and brought it back to the janitor closet behind the electric shop that we now used as a “Precipitator Fly Ash Cleanup Room”. I had laid it on a shelf there. The lawyers said, “Send us the original sheet and we will drop this violation.
Here is a copy of the piece of paper. The big black splotch at the top is what duct tape looks like when you make a copy of it.
Well, that worked out good. I had stepped out of line by opening my mouth before I had been asked a question, but everything worked out all right.
The final verdict was that we had four violations. We had to re-train our employees on Confined Spaces. We had to create a Confined Space Rescue Team. We had to put the correct signs on all of the confined spaces and we had to develop rescue plans for all of the confined spaces on the plant grounds. If we did that by August 1, 1994, the four remaining violations which amounted to a $40,000 fine would all be dropped. So, we had our work cut out for us. This not only impacted our plant, but all the Power Plants. The meeting was adjourned.
I already told you what I did after the meeting (I went and ate lunch with my brother). But I haven’t mentioned yet why Robert B. Reich had made a surprise visit to the Department of Labor building in Oklahoma City on April 18.
As it turned out, that morning, Labor Secretary Reich had come to Oklahoma City to hand deliver a $7.5 million fine to Dayton Tire Company. This was due to an accident that had resulted in a man, Bob L. Jullian, being crushed by a piece of machinery in the tire plant. He died a week and a half later at the age of 53.
Robert B. Reich had become so angry when he had studied the case on Friday that he wanted to hand deliver the citation himself the following Monday. That is how we ended up in the building at the same time on Monday, April 18, 1994. We resolved our dispute with OSHA on a congenial note and the citations were dropped on August 1. Dayton, however, was still fighting the conviction 18 years later, eventually paying around a $2 million penalty.
Now you know the rest of the story. Well, almost. Like I said, we had a lot of work to do in the next three and a half months.
Favorites Post #62
Originally posted October 19, 2013:
Everybody seemed to like Bill Bennett. We didn’t like him because he possessed a profound knowledge in the field of electricity. No. We liked him because he was a good person. Bill was a tall very thin black man that sort of reminded you of Bill Cosby.
Bill had a gruff cigarette voice as he was a chain smoker. Often he would say his first words to me when he came into the Electric Shop office for lunch each day in the same manner that Aunt Esther would say something to Fred Sanford. His lower jaw would jut out and he would shake his head with a look of total disgust… like this:
With this expression, Bill would often look at me and say, “You Scamp!” Dragging it out for the full effect. Nothing would bring a smile to my face faster than having Bill berate me by insulting my integrity as a person. He would also add on additional phrases like, “…You disgust me!” Or… “….you scum!” — I felt like Gomer Pyle by that point with a big grin on my face.
I just wish everyone could work for such a great guy at least once in their life.
I’m not saying that we didn’t have our disagreements throughout the years that he was our A Foreman at the Coal-fired Power Plant in North Central Oklahoma. I recognized that Bill had his way of viewing the world, and I had mine. And even though my way was always the right one, I realized he had a right to his view even when it was wrong.
At those times what could you do? Probably the same thing I would do. Fall on the ground kicking and screaming and then try to make your face turn blue by holding your breath. — That never seemed to change his mind though. Probably because I liked breathing too much and would find that it didn’t take long before I would develop an overwhelming urge to take another breath.
Anyway. After spending well over a thousand lunch times with Bill Bennett, just when I began to think that I had heard every story about Bill Bennett’s life that was imaginable, he would come up with another one.
I could tell you some stories about Bill where he was at the lowest point in his life. When he was an alcoholic at the point where he normally would have been fired from the electric company. Then someone gave him another chance for no other reason than because he understood human nature and cared about his fellow man.
You see. There are a number of people in the electric company throughout the years where they were at the low point in their lives. Sometimes people were there to give them a lift up from the gutter where they had fallen. At other times, they were cast aside mercilessly and forgotten because the company was priority. A useless and hypocritical attitude, I always thought, because what is electricity used for except to help mankind.
When Bill Bennett had reached that point in his life, someone was there to help him out of the gutter. They brushed him off (the dust I mean). Gave him some self dignity and “let it go”. Bill went on to become a good and compassionate person. I’m sure that those people in his life that helped him back then were the major force in reshaping his outlook on life. He was always fighting for the underdog. Once I understood that. I stopped my kicking and screaming, and picked myself up off of the floor.
So, I thought I would share a couple of my favorite stories about Bill.
When Bill was young, he lived in Oklahoma City, southeast of the capitol a couple of miles in the poor section of town. I could picture this story real well when he was telling it because my soon-to-be wife was living in this same area as she was attending Nursing School at the Oklahoma University Medical School.
Bill recounted this story: One day when he came home from school his dad gave him a little pet possum.
Bill was overwhelmed with happiness. This was like his one and only true friend. He took the possum with him wherever he went. After so many years since Bill told this story I don’t remember what name Bill had given the possum, but it was something like “Fred”, so I’ll just call him Fred for the rest of the story.
Bill taught Fred tricks, and he would run up his arm and perch on his shoulder. Bill would walk around the neighborhood proud to have his pet possum Fred sitting on his shoulder. The two became inseparable.
When the summer was over, in the morning when Bill went to school he would have to leave Fred at home. He had a certain sound that he would make to call his possum. So, when he would walk in the door after returning home from school he would call Fred, and he would come out from under the sofa, or the bed, or wherever he had decided to hide for the day. Fred was pretty much a grown possum by this time.
One day Bill came home from school. He didn’t remember whether he had called Fred or not when he came home, but if he had, Fred didn’t answer. This wouldn’t have concerned Bill much since Fred may have just been playing Possum as Possums are apt to do from time-to-time. Anyway. Bill didn’t see Fred when he came home.
When it came time for dinner Bill sat down and his mom served him a nice hot bowl of stew. As dinner progressed, at one point the subject of the stew came up. Maybe one of Bill’s brothers and sisters said, “Hey mom. This is sure some good tasting stew! What is it?” That was the point in Bill’s life when he decided to become a chain smoker and an alcoholic…. well… not all at once… This was just the point that led him down that path.
You see. As Granny in the Beverly Hillbillies would say, “Go eat your Possum Stew Jethro”. Here is Granny running for Possum Queen:
That’s right. Bill Bennett’s mom had cooked his pet possum Fred for dinner. When he heard this he was stunned. He didn’t have the same expression that Jethro had when Granny called him to the dinner table, that’s for sure.
When he asked his parents how they could do that to his pet possum, his father replied, “Why did you think I gave that possum to you?” That was when the grim reality of life hit Bill right between the eyes. Sick to his stomach he left the dinner table. From that day onward, Bill never again ate possum stew.
This might seem like a humorous or cute story to some. To Bill, it changed his entire outlook on life. As I mentioned. He later became an alcoholic. Which even later, with the help of his wife and others, he overcame. Though it was gradual, if you trace his life back, I believe that the downward spiral began at this one crucial point in his life. With the intentional loss of the life of someone he loved.
When Bill would call me a scamp…. I sometimes felt that down inside he was still crying for Fred, and was talking to his father instead of me. I could see a hint of sorrow even in his humor. He knew he could take out his hidden frustration in our presence because Bill always knew that friends like Charles Foster and I would always be there smiling back at him.
Ok. That was one of the more serious stories of Bill’s life, but one that I often think about when I think about Bill. Let me tell you a more humorous story:
Bill Bennett worked for an electronics store at one point in his life before he found his true calling as a “Power Plant Man”. Part of this job included making house calls to work on the security system in homes.
The employees would use the company van to go on house calls. It had the necessary equipment to install and repair the security systems. It also had one curious item sitting on the dashboard. A garage door opener.
The garage door opener was a point of amusement for the employees as they would drive through a neighborhood on the way to someone’s house they would click the opener as they drove along looking around to see if it would open anyone’s garage door. No one knew where the opener had come from, but they thought that just by chance it might randomly open a garage door here or there.
So, here is Bill’s story:
One day he was on his way to do a job in a high-end neighborhood. As he was slowly making his way down the neighborhood street to his destination, he was clicking the garage door opener to see if it would open any doors. When all of a sudden he saw a few houses up ahead that a garage door was opening.
For a brief moment Bill was excited that he had found a garage door that opened. Then he realized that the garage door that was opening was the house where he was making the service call. “Oh No!” He quickly began clicking the garage door opener to try to close the garage door, but it wouldn’t close.
Bill sat in the van for a while desperately clicking the garage door opener praying that it would work to close the garage door, but it never did. finally he decided he would act as if he didn’t know anything about how the garage door opened and climbed out of the van.
He walked over to the garage and peered in, sheepishly saying, “Hello?” He was conscious that he was a lone lower class black man in a predominantly rich white neighborhood walking into someone’s garage in broad daylight. He took a few steps into the garage when the garage door began to close!
In order to make it out of the garage, Bill would have had to dodge under the closing door, so he just froze in place and awaited his fate.
A few moments later, the door to the house opened and a little old lady entered. Bill tried to explain that he didn’t know how the garage door had opened and that he only entered the garage to see if someone was there. She said she had seen his van coming down the street, and had opened the garage door from inside the house.
So, the garage door opener in the van hadn’t opened the door after all. It was just a major coincidence that Bill happened to be driving down the street clicking a garage door opener when an elderly lady (like Granny) had seen his van and opened her garage door only to have Bill think that he had opened the door. Or was it a coincidence?
Sometimes I feel that when a coincidence of this statistical improbability occurs that there is often an extraordinary intervention from above telling you something. I’m sure that this little scare taught Bill something and helped him progress on to the view of life that he had when I met him years later. Something like: “When someone somewhere opens a garage door in life, some may find that there’s a little old lady behind the scenes actually pushing the buttons.”
I have another very coincidental story about a true Power Plant engineer that was a major turning point in this person’s life that I will share in a couple of years from now. When you read that story it will be very clear that there is someone definitely looking out for poor souls like us.
Comments from original post:
Favorites Post #56
Originally posted November 21, 2015
Sometimes when something is written on paper, it becomes carved in stone (I should copyright that phrase — oh. as soon as I click “Publish” I will). I saw a flaw in Power Plant logic one day in November 1994. Corporate Headquarters for the Electric Company in Oklahoma had decided that they needed very clear job descriptions for their Job Announcement program.
We had just completed a downsizing a few months earlier and two electricians were asked to determine what prerequisites someone would need to be able to do their jobs. My first thought was… “Is that really a smart way to go about this?” Just think about it…. You are asking someone who just survived a downsizing to determine what it would take to replace that person with someone else…. Can you see the flaw in this logic?
It was decided that in order to be hired as an electrician, you had to have the following prerequisites: A technical degree in an electrical field. A minimum of five years experience as an industrial electrician. Have a technical knowledge of how to walk on water. Able to swing from tall buildings using four size 2 conductor cable. Have extensive experience bending conduit. Able to work in confined space manholes. Can bend a one inch diameter stainless steel rod with bare hands. Black Belt in Six Sigma. Able to explain the meaning of each color on a resistor. Not afraid of heights. Willing to shovel coal. — Yep. that’s what it requires to do my job.
I knew right away this wasn’t going to be good. We would never find someone who can both walk on water and was willing to shovel coal. If we ever had to replace an electrician, it would be darn near impossible.
This wasn’t only true for electricians. Every type of job in the company was given similar treatment. I had been an electrician for 11 years at that point, and I didn’t even meet the minimum qualifications to be hired as an electrician. If I had left the company and tried to apply for a job at our plant as an electrician, I would have been turned away at the door.
Whatever minimum requirements were written down did not only apply to outside applicants. This was required of employees applying through the internal Career Announcement Program (CAP) as well. In other words, I never would have been able to join the electric shop from the Labor Crew as I did in 1983, with only a scant understanding of what it takes to be an electrician.
It wasn’t until a few years later that this occurred to anyone. The minimum requirements were relaxed a little. That was when the training program was put in place to take High School graduates and above and allow them to train at the plant for a particular skill as I described in the post: “Power Plant Train Wreck“. The rest of the company had to live with their own minimum requirements.
The results of asking the employees what the minimum requirements should be for their own jobs, HR had painted themselves into a corner. I knew why they did this. It was because they had lawsuits in the past where someone was hired over someone else, and they thought they were more qualified for the job and they claimed they were victims of discrimination. So, specific requirements for each job needed to be created…. Actually…. I think this is the opposite of what should have been done.
If I had my druthers, I would have approached this from the opposite direction… let me continue with my story and you will see why.
I started getting my degree in Management Information Systems (MIS) in 1997 at Oklahoma State University. I was going to graduate from the business school in May 2001. In the fall of 2000, I had only 6 credit hours (or two more classes) left. I had started in 1999 applying for IT jobs in our company. Many times I was asked by people in the IT department to apply for specific job openings. I had worked with a lot of them, and they would have liked for me to work for them.
Unfortunately, at that time, here was the minimum requirements for a Software Developer: You had to have one or more of the following: A Bachelor Degree in Computer Science… OR Bachelor Degree in MIS with at least 9 hours of computer languages (I had the 9 hours of computer languages)… OR Bachelor Degree in a business or technically related field with 18 hours of computer science courses including 9 hours of computer languages…. OR Associate Degree in Computer Science with 9 hours of computer languages and 2 years of software development experience….. OR 8 years of directly related experience such as development in C, C++, ABAP, Visual Basic or Cobol.
It was that last requirement that I thought I could use. Especially since I was well on my way to earning the degree. I had many years writing code in Visual Basic and C. I had taken a Cobol class already, and studied ABAP (which is used in SAP) on my own. So, along with almost having my degree and working with IT for more than 8 years, I applied for these jobs.
Every time I did, HR would kick the application back to me and explain that I didn’t meet the minimum requirements so I was not able to be considered for the position. Not until I had my degree in my hands. The HR Director said that all the work I had done with IT didn’t count because I was doing it as an electrician. She said her hands were tied.
In November 2000 the University had a career fair for students applying for IT or business careers. So, I attended it. It was in a large room where each of the companies had setup a booth and you walked around to each booth as the various companies explained why it would be nice to go work for their company. They explained their benefits, and when they were done, they asked you for your resume (pronounced “rez U May” in case you’re wondering) if you were interested.
Before the career fair, I had gone to lectures on how to go through the interview process, and I had read books about how to create a good resume. I had bought books on these subjects and read them after having gone to a lecture by the author Martin Yate. Here are three books that came in useful in my job hunt:
So, here I was at a job fair dressed in a nice suit I had bought in Oklahoma City at a high end Suit store. I had studied what color shoes, belt and tie to wear. I had a stack of my carefully designed resumes in hand. My wife Kelly had given me a professional haircut the night before, and I had even washed behind my ears.
I had quickly changed into my suit in the bathroom in the office area at the Power Plant. I quickly took the elevator down to the ground floor and stole out to the parking lot to drive the 30 miles to the Job Fair. No one saw me leave, except Denise Anson, the receptionist.
I made my way around each aisle of booths, carefully considering each company. I was not really interested in working as a consultant where I had to do a lot of travelling. After all, I had a family. I gave my resume to many companies that day, and later I had interviews with many of them. It felt very strange as a 40 year old acting as a kid in school handing resumes to companies. I really just wanted to stay at the Electric Company where I had worked for the past 19 years.
Then I spied the booth I was really curious to visit. It was the Electric Companies booth. The company where I worked. I saw a group of students walk up to the booth and the young man from HR began his speech about why it would be great to work for the Electric Company. I stood toward the back of the small crowd and listened. It was weird hearing him tell us about the benefits of working for the company.
The Director of HR was standing next to him. She was the person that kept rejecting all of my job applications through the internal job announcement program. I waited patiently thinking… I could come up with better reasons for working for the best Electric Company in the world. He never mentioned once that the best employees you would ever find in the entire world worked just 30 miles north on Hwy 177 at the big Power Plant on the hill. That would have been the first thing I would have mentioned.
I waited until the young man completed his speech and then asked the students if they would like to give him their resumes. I stood there, not moving, but smiling at the young man from HR. After everyone else left, the man turned to me and awkwardly asked me if I would like to give him my resume (it was awkward because I was just standing there watching him). I replied as I handed him my resume by saying, “I’ll give you my resume, but I don’t think you can hire me.”
He replied, “Sure we can.” as he glanced down at my resume. I continued, “See… I already work for the company.” The young man brightened up and said, “I thought I recognized you! You work at the Power Plant just north of here!” I said, “Yeah. You were the leader at my table during the Money Matters class.” “Yeah! I remember that!” He replied.
“Sure, we can hire you!” He replied. I said, “No. I don’t think you can. You see. I don’t meet the minimum requirements.” Then I turned my gaze to the Director of HR who was now staring off into space… The gaping hole in logic had suddenly become very apparent. She replied very slowly…. “No… I don’t think we can hire you.” The young man (I think his name is Ben), looked confused, so I explained….
“You see Ben… you can take resumes from all of these college students and offer them a job for when they graduate, but since I already work for the company, I have to have my degree already in my hand before I meet the requirements. I can go to any other booth in this room and have an interview and be offered a job, but I can’t find an IT job in the company where I work because I don’t meet the minimum requirements. Seems kind of odd. Doesn’t it?”
I continued…. “Not only that, but the Electric Company has paid for all my classes to get my degree and 75% of my books. I have only 6 more hours after December, and I can’t find a job with my own company. I will probably have to go to another company that is guaranteeing a job when I graduate. Does that make sense?”
The HR Director was still staring off into space. She knew as soon as I opened my mouth who I was. She had personally signed each rejection letter to me.
So, what had happened? It had happened a few years earlier when the employees were asked what the minimum requirements should be for someone to be hired for their jobs. That led them down a path of closed doors instead of opening up opportunities.
Here is what I would have done instead… I would have done what other companies do… Minimum Requirements: “Team Player. Able to work well with others. Demonstrated an ability to learn new skills.” — Who wouldn’t want an employee like that? Sure. Add some “Desired attributes” on the end like: Able to bend conduit. Able to Walk on Water, etc.
I had spent about an hour at the career fair handing my resume to potential employers before I left. I drove back to the plant. On the way back to the plant I was having this sinking feeling that I was not going to be able to stay with the Electric Company. I can’t describe how sad I was at this thought.
I couldn’t just stick around at the plant hoping that once I had a degree in my hands that I would be able to move into the IT department. For all I knew, our own plant manager could have been telling HR that I couldn’t leave the plant because I was the only person that worked inside the precipitator. I had been flown around the country to interview with different companies who were now offering me jobs. Those offers wouldn’t still be there if I waited until I graduated, so I had to make a decision soon.
I knew that the Plant Manager Bill Green kept asking the Supervisor over Maintenance about my degree because Jim Arnold would ask me from time-to-time, “What’s that degree you’re getting again?” I would say, “Management Information Systems” in the Business College. Jim would go back to Bill and say, “Oh. You don’t have to worry about Kevin leaving. No one wants someone with that degree” (Yeah. Heard that from someone on the staff that heard it first hand).
When I arrived back at the plant, I walked in the entrance and hurried to the elevator. I waved at Denise as I quickly walked by the receptionist window and quickly went into the men’s room to change back into my jeans and tee-shirt and work boots. No one else saw me. I returned to work with Ray Eberle in the Print Room to work on SAP. Ray asked me how it went…
I told Ray about my adventure and my encounter at the Electric Company booth. Ray came to the same realization that I had on the way back to the plant… I wasn’t going to be able to stay with the company. I was going to have to move on…
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.
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.”
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:
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.
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.
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 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.
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.
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.
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.
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!
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.
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…..
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”.
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:
Favorites Post #53
Originally posted July 4, 2014
I never would have guessed that playing Power Plant Man jokes on Gene Day would have led me to the “Uh Oh!” moment I later encountered when I was told in no uncertain terms that the President of the Electric Company, James G. Harlow Junior was personally upset with something I had done. I had learned my first year as a summer help at the coal-fired Power Plant in North Central Oklahoma that “One ‘Uh Oh’ wipes out all previous ‘Atta Boys’!” I could tell by the way the Electric Supervisor, Tom Gibson’s ears were glowing red that this was considered a little more serious than I had first realized.
I have mentioned in previous posts that playing jokes on Gene Day was one of my favorite Power Plant Man Pastimes. See the post, “Power Plant Humor and Joking With Gene Day“. Also see, “Psychological Profile of a Power Plant Control Room Operator“. My lunch breaks were usually consumed with learning more about how to program the Honeywell mainframe computer used by just about all the company processes that actually ran the company from payroll, to billing, to work orders and Inventory. I figured that as I learned more about the computer system, the more elaborate jokes I would be able to play on Gene. That was my ultimate motivation.
Already I had learned about the escape codes used by the large IBM printers that were used throughout the company at the time. This allowed me to create graphic images on the printer as well as large bold letters.
Besides the telephone and inter-company mail, printers were the only other way to communicate to non-present Power Plant Men in 1989. We had not yet been introduced to e-mail. I was one of the few people in the company that had an e-mail address on the mainframe, and the only other person that I knew that I could write to was Craig Henry, a Corporate Engineer downtown.
Much like the first time when I met Gene Day, when I first encountered Craig Henry, I could tell right away that he was a down-to-earth person that would shoot straight. Craig probably wouldn’t remember this far into the past that I would reach out to him occasionally just to say “Hi” and to pick his brain about how the corporate IT infrastructure was setup. I figured since he was one of the few people in the company that even knew what an e-mail address was at the time, he most likely had more knowledge about such things than the average person in Corporate Headquarters.
After finding out that Gene Day would go work out at the Rock Gym in Stillwater, Oklahoma after work, and I had played the joke on him with the notes from the private investigator, I used my knowledge of Printer Escape codes to write documents on the mainframe that when printed out would turn on the graphic commands on the printer so that I could print out pictures. I don’t mean that I would have a saved picture that I would send to a printer like we might do today. No. I had to create these pictures one pixel at a time using commands in a UNIX document on the mainframe. It was all codes that would not make sense to anyone that didn’t know the graphic commands of the IBM printers.
I had been teasing Gene Day about meeting up with a young “coed” from the University at the Gym each day. I would do this by printing out messages on the Control Room printer by the the Shift Supervisor’s office when I knew that Gene Day was there filling in as the Shift Supervisor. They were usually notes from someone that called herself “Bunny”. Usually they were short notes or “love letters” from Bunny just saying something about how she enjoyed her time with Gene at the Gym.
At the bottom I would sign it “Bunny” then under it, the printer would read the graphic commands and create a small Playboy Bunny symbol under the name. At the end, the document would send a command that would put the printer back into the text mode.
Of course. Whenever I walked into the control room shortly after, just to see how the precipitator was doing, Gene Day would confront me about the notes. With a grin on his face he would say, “This isn’t funny! What if my wife found one of these notes?” — Like that was ever going to happen…. unless he was like me, and likes to save everything.
In order to create the bunny at the bottom I had to create the pixels in small blocks of 9 pixel patterns. Here is the code I used to create the bunny:
In the last couple of weeks I have written about how the Power Plant Men were introduced to the “Quality Process” (otherwise known as “Six Sigma”). We had created teams with our crews and we met once each week to come up with Quality ideas. By August, 1993, I had received my official Certificate Certifying that I had completed all the QuickStart training and was on my way to making a difference in the Power Plant World!
So, what do these two events have in common and how did this lead the President of the Electric Company to send out a search warrant on a lowly (lowlife is more like it) Plant Electrician in North Central Oklahoma? Well. This is what happened…
First you have to remember that in 1993, the Internet was not easily accessible by the general public. Company e-mail was still not a reality in our company. We had dumb terminals and large IBM printers. That was the extent of most employees interaction with a computer. Each printer had a designation. It was a five character ID beginning with a “P”. So, the printer in the Electric Shop Office might be…. P1234. I needed to know this number if I wanted to send something to it.
At the time, the only thing people had to send to each other were requests for things from the mainframe systems that were used to run the company. So, for instance, if you wanted to request some parts from the warehouse at our plant, we would send over a list of parts to the warehouse printer where Dick Dale and Darlene Mitchell would pick it up and go retrieve the parts. So, the people that used the terminals and computers with mainframe emulators on them knew the most commonly used printer numbers in the plant.
If you wanted to send something to someone in Oklahoma City, or to the Power Plant in Muskogee, then you would have to call over there and ask the person what their Printer ID is so you can be sure you are sending your request to the appropriate printer. Without e-mail, and any other form of computerized communication. This was the only way at the time.
So, after our Customer Service Team was formed, we would meet once each week to brainstorm new ideas that would benefit the company. Andy Tubbs was our team leader, as he was our foreman.
The other members of our Customer Service Team were Diana Brien, Scott Hubbard, Sonny Kendrick, Ben Davis and Gary Wehunt. I haven’t properly introduced my bucket buddy Diana Brien in a post before. I have recently obtained a photograph that I can share:
We were called bucket buddies because we carried tool buckets with us whenever we went to work on something. They doubled as our stool and tripled as our trash can.
Thursday, July 15, 1993 during our Quality Brainstorming session, while we were pouring out ideas like…. “What if we changed out the street lights at the plant so that they would be different colors…. wouldn’t that help morale?…. and “How about if we wrapped fluorescent Christmas lights around the high voltage electric lines between here and Oklahoma City so that they could light up the night with colorful lights during the Christmas Season?”….. And other ingenious Brainstorming ideas that are bound to pull up an occasional brilliant idea….. well. One such idea popped up!
I don’t remember which one of our brilliant brainstorming ideas conjured up this idea, but Andy Tubbs suddenly blurted out…. “What if we had the Printer IDs added as a column in the Corporate Directory? — You see, each quarter we received an updated paper copy of the Corporate Phone Book. It included the names and office phone numbers of all the Electric Company employees. It also included their mail code. So, if you wanted to send something through inter-company mail to them, you would know where to send it. Our mail code was PP75. That was the code for our power plant.
So, what if we added a column where we had the printer ID that each person would use for people to send printed requests, among other things? This was Brilliant! We could just make this proposal and send it downtown to Corporate Headquarters where it would be lost in the “mail”. Or we could do more research to prove that it was a possible proposal that was really do-able.
So, I suggested…. Well… I can print a form out on every printer in the entire company requesting that they include all the names of all the people that use that printer and mail it through inter-company mail back to me at PP75. — I had recently uncovered a special printer command that allowed me to do this hidden away on the Honeywell mainframe. So, we took a vote and it was decided that we would pursue this proposal. I set to work on creating the form that I would send to every printer. If we could not only send the proposal to the Communications department downtown, but also a list of everyone and their printers, the work would already have been done for them.
I wanted to send a real fancy letter because I had already created a header using the Quality print settings on the printers. I had created a Company Logo that (I thought) ingeniously used the backspace command to create two words with one word on top of the other in the middle of a sentence…. Our company began as Oklahoma Gas and….. in the logo, I wanted the word Gas to be on top of the word And as it was in our company logo in smaller letters than the others. So… after playing around with it for a while, I created the logo and had it saved on the mainframe.
After attaching the header to the form, I included a message that told the person that discovered the form on the printer to add the names of all people who used the printer below and to send the form to Kevin Breazile at PP75. As I mentioned. In order to make the form look pretty, I turned on the Quality Print settings on the printer at the beginning of the document. Like the story of the Sorcerer’s Apprentice….. I didn’t know a good way to turn off all the settings I changed to revert the printers back to their original settings.
I ran the command to send the document to every printer on the print server and away they went…. A copy printed out on the printer in the Electric Shop office so I knew it was working. Copies printed out on the other 12 printers at our plant. They also printed out on the 500 other printers throughout Oklahoma. — With the thought that “My work here is done.” I went back to work repairing plant electric equipment.
The following Monday I had the day off. When I returned to work on Tuesday, Denise Anson called me from the front office. She said that I had a large stack of mail. I thought, “Oh good!” Results from our request on Thursday have arrived! I hurried up to the front office.
When I entered the mail cubicle I was surprised to see how big the pile of envelopes were. The stack of inter-company envelopes was over two feet high. “Um…. Thanks….” I said to Denise. I picked up the stack and headed back to the Electric Shop to sort out the forms.
After opening the first few envelopes. I suddenly came to an astonishing discovery. Not only did the form print out on the large mainframe IBM printers used in office areas, it also had printed out on other types of printers…. I opened one envelope and found the form printed out on a “Work Order” printer. The paper size was different than the standard paper size, and I hadn’t put a page feed at the end of the document, so, it had left the paper in the middle of the page…. “Uh Oh”.
My “Uh Oh” changed to “UH OH!” after opening a few more of the inter-company envelopes. I found that the form had printed out on Pay Check Printers! And Billing Printers! “UH OH!” quickly changed to “OH NO!” When I read comments like “Under no circumstances print anything on this Printer Again!!!!” I realized I had really messed things up. By changing the font size and the quality settings, the billing, payroll and work order printers all had to be manually reset and the jobs that printed out paychecks, customer bills and employee work orders had to be re-run!
After taking all the forms out of their envelopes, the stack of papers was over 4 inches thick, just to give you an idea about how many responses we had.
A couple of hours later, Tom Gibson called me to his office. “Uh Oh.” (remember… One “uh oh” erases all previous “atta boy”s). When I entered Tom’s office, I could tell that something was definitely wrong. Like I mentioned earlier. Tom’s ears were beet red…. and in case you don’t know what a beet looks like. Here is one:
Of course… I knew what this was all about, only I didn’t know yet, how Tom had found out about it…. Tom began by saying…. “Ron Kilman just received a call from James Harlow asking him who is Kevin Breazile and why is he printing something out on my printer? Ron didn’t like the fact that he wasn’t aware that you had sent something to the President of the Company’s printer.
Sorry. That’s the biggest picture I could find of James Harlow….
Um what could I say? So, I said this…
“Well. This was a quality idea that our team had. We wanted to collect the names of people that used each printer so that we could send in a proposal to have the printer ID added in the Corporate Directory.”
I didn’t mention that Harlow’s Secretary had returned the form with all the people that used his computer as I had requested, because I knew that the President of the Electric Company was not asking because he was upset that I had printed something out on HIS printer. No. He had probably been told that the reason the bills were late being sent to the one million customers that month was because some kook had messed up their printers and the jobs had to be run over again causing the delay. So, I thought it was best not to go down that route at this time…
So, I stuck with my story, which was the truth…. I had printed out the forms on all the printers as part of a quality idea by our CST (Customer Service Team). — I also didn’t mention that three years earlier, Tom had asked me to learn everything I could about the company computer, because he believe that the computer was going to be the wave of the future.
Even though Tom believed my explanation, he told me…. “Kevin, Ron never wants this to happen again, therefore, you are never to send anything out of this plant without Ron Kilman’s personal approval. Is that clear?”
I replied to Tom that this was unreasonable. I send things to other departments all the time. I send Substation Inspection forms, and blueprint revisions and all sorts of other forms downtown all the time. Ron Kilman wouldn’t want to waste his time approving all those things….
Tom thought about it and revised his statement…. “Then, don’t ever send out anything that isn’t part of your normal daily job without Ron’s approval first.” — Ok. I thought…. this works, since everything I do is part of my normal daily job…. Even printing out forms on all the printers in the company… since that was part of our normal “Quality Process” Customer Service Team activity…. So, I happily agreed. And I left Tom’s office happy that I hadn’t joined the ranks of the unemployed.
That was one thing about working at the plant at this time. As long as your heart was in the right place…. That is, you tried your best to keep the electricity humming through the electric lines…. then the chances of being fired for messing up, even as big of a mess up as this, most often didn’t end up by losing your job.
I sometimes think that this was my biggest mess up of all time… however…. after this episode was over… there was a part two to this story….. Believe it or not…. Someone else in the company was overjoyed about what I had just done. They had been trying to do something similar for a long time, only to be told that it was impossible. — Doing the Impossible… I was good at that… Part two of this story is a story for another day…
Since this is a repost of this story, I have written part two, which you can read here: “Printing Impossible Power Plant Fast News Post“.
Comment from previous post
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.
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.
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.
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.
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:
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.
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.
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.”
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.
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 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!
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:
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:
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:
Favorites Post #51
Originally posted May 22, 2015
August 6, 1996 in Corporate Headquarters America, jaws began dropping a few minutes before 8 a.m. At first the security guard just thought some Power Plant Giant had taken a wrong turn and showed up at Corporate Headquarters to ask for directions. When another one showed up, this time carrying his Playmate lunch box, hard hat on his head, and lip quivering looking for a handy spittoon, the men in their suits and women in their fine dresses began running for cover. That was the day eight Power Plant Men took over the floor in the building where the Corporate Engineers usually lived.
If you want to understand the shock that emanated throughout the building, just picture the following bunch showing up on your doorstep:
We had come from the four corners of the Oklahoma Electric Company Power Plant Kingdom and we were there in Oklahoma City because Corporate America needed our help! Two Power Plant Men from each of the main Power Plants were picked to help the company transition from the old Mainframe computer system to a new computer application called SAP. SAP was going to combine all of our computer needs into one big application that runs on the new computer network.
Ernst and Young was the consulting company that was helping us install and implement SAP at our company. The company began the implementation some time in March, and the big bang go live date was going to be January 1, 1997. According to Ernst and Young, this was a physical impossibility. There was no way we could convert all of our requirements into SAP realities in such a short time.
The Maintenance Module for SAP hadn’t even been fully developed. We were actually working with SAP to design the module. Our company had demonstrated how a Best In Class Maintenance process worked, and SAP was designing their module around our needs. Everyone insisted that our aggressive timeline was too unreasonable and would never be met.
The Electric Company in Central Oklahoma had one Ace up their sleeve (well, maybe more than one)… That was “Power Plant Men!” As I mentioned in last week’s post (See the post “Destruction of a Power Plant God“), I was told on Monday, August 5, to show up for work the following day in Oklahoma City to work for 10 weeks on an SAP project.
Mike Gibbs, a mechanic from our plant was going with me. Our task was to convert all the Power Plant parts in the Inventory system in searchable strings that had a limited number of characters. Mike Gibbs used to work in the warehouse, so he was a good candidate for knowing what odd parts actually were.
We were a cross-section of mechanics and electricians, and warehouse people. To give you an idea of how big our job was, we had over 100,000 different parts in the system. 75,000 of those parts were in the warehouse at the power plant where I worked. There were over 5,000 different types of Nuts and Bolts… just to give you an idea of the task ahead of us.
Ernst and Young said the task would take the eight regular employees four months to complete the task. The Electric Company said, “Power Plant Men can do it in 10 weeks.
We were able to use the office space used by all of the engineers because they all happened to be at the Coal-fired Power Plant in North Central Oklahoma where I normally worked because of the big explosion that destroyed part of the Turbine Generator room early Monday morning. While they packed up to begin the work of reconstruction, Mike and I packed up and headed to Oklahoma City.
Most of the “out-of-town” Power Plant Men stayed in hotels for the next 2 1/2 months, but Mike Gibbs and I decided that we couldn’t be away from our families that long, so we decided that we would drive back and forth to work each day from Stillwater, Oklahoma. This was about an hour drive with going to work traffic. We would meet in the parking lot of a Mexican Restaurant at the edge of town and take turns each day driving to Oklahoma City.
Normally, in an instance like this, we would get paid a mileage that was farther than if we drove to the plant and maybe even driving time to and from work each day, but when our Plant Manager Bill Green found out we were driving back and forth, he refused to pay us anything. He told us that it was far enough away that he would only pay for us to stay in a Hotel (which would have cost more than the mileage), he wouldn’t pay us mileage or even a per diem (which is a daily amount for expenses).
Bill Green knew that we were family men that wouldn’t want to be away from our families during the week if it was only an hour drive, so he played his card and said that we had to stay in a hotel, and he would pay the expense for that or he would pay nothing and we could drive back and forth all we wanted at our own expense, already knowing that we would rather wear our cars out and pay the extra gas each day to be with our families. I just thought this was pay back for me being so rotten all the time.
The first week I was there, I worked on converting the 5,000 different nuts, bolts and screws into cryptic search strings that all began with the three letter search word for bolt: BLT. If you wanted to search for a Bolt in the SAP inventory, you would know it begins with a the letters BLT. This only made me hungry all week, because to me, a BLT was a sandwich. A mighty good one too, I may add.
After the first week, it was decided that having Power Plant Men roaming around between offices asking each other questions about parts was a hazard waiting to happen, so the engineer that was running our project Mark Romano had a special holding pen… um… I mean, cubicle built just for us. It was decided that we should all be together in what is called a “Bullpen Cube”. All nine of us. Bullpen was a good name considering that there was a lot of bull going around for all of us.
There were nine, because a young Corporate executive had been assigned to help us with all things “Corporate”. His name is Kent Norris. He was lucky enough to stay behind to work with us, instead of having to go spend the next 2 1/2 months at our plant up north helping to repair the fire damage.
Well. I say lucky. Lucky for us, maybe not for him. After all, he was someone from “corporate” stuck in a cubicle with 8 rascally Power Plant Men that kept themselves motivated by playing practical jokes on whoever was willing to fall for them. Not ever having experienced the likes of us before, Kent was in for 2 1/2 months of relentless practical jokes being played at his expense.
I must say that we had a terrific time teasing poor Kent, but he was such fun and took our jokes so well, that we could only admire his resilience to bounce back and smile after we ran him ragged with one joke after the next. I will go into more detail about the jokes we played on Kent in a later post. For now, I am just mentioning our situation, so that you can get a picture of our situation.
Kent helped us with our expense reports each week, and showed us all the good places to eat lunch. He helped us adapt to corporate life. He even showed us how to use our temporary badges to badge in and out of the doors when we entered and left the building.
Mike Gibbs discovered a better way. He just put his badge in his wallet, and since he was tall enough, when he walked up to the badge reader, he just pressed the back pocket of his blue jeans against the badge reader, and voila! The door would open like magic! Onlookers were always staring at this strange assortment of men in blue jeans and tee shirts walking through the office building during lunch.
I tried to remember all the people that were there in the cube with us… I remember that I was there, and so was Mike Gibb from the coal-fired Power Plant in North Central Oklahoma.
Ken Scott, who was the Maintenance Superintendent at the Gas-fired Power Plant by Konawa, and David Roe who worked in the warehouse at that plant.
Doyle Fullen, an Electric Foreman from the coal fired plant in Muskogee, and Robert Christy, a mechanic also from that plant.
I believe Dan Hayer, the warehouse man, was there from the gas-fired plant in Harrah, Oklahoma on a small lake called Horseshoe Lake. I don’t remember who else was there from that plant. I remember seeing someone there, but I think he was a more of a quiet type and for some reason, his name has escaped me.
I was a sort of a computer programmer at this time, so I created small programs that would make our jobs easier. I created icons on the computers so that people didn’t have to log into the apps, and I created a couple of other small programs that just automated the monotonous manual steps that we would have to do over and over again as we plowed through the 100,000 different part descriptions.
After the first week, we had converted over 15,000 parts, and were on our way to meeting our goal.
So, how did we do? The Power Plant Men were able to convert all 100,000 parts in the inventory system to SAP in eight weeks! Two weeks ahead of schedule. This was typical for Power Plant Men, especially when you tell them it is impossible. This was another example of doing things that others said couldn’t be done.
I felt like a few people on our team were not too happy with me for creating things that made their job faster because they wanted to stay the full 10 weeks. Here we were in an air conditioned building working on computers all day instead of out in the heat and dirt.
We were all scheduled to go back to our home plants two weeks early when Mark Romano, our project manager came to our cube to give us the news… We had performed our job so well, they wanted to expand our scope. It seems that another department… I won’t mention which one, but their initials are T&D had been working on their measly 60,000 parts for the past 4 months and had only completed about 10,000 of them. They wanted to know if the Power Plant Men would be willing to give them a hand to convert the 50,000 parts in their inventory system the same way we did for Power Supply. Otherwise the go-live of January 1, would not be met since we were coming up to the end of September already.
Our Plant Managers had agreed that we could spend the next four weeks converting T&D’s parts as well, so of course, we agreed to stay on. I’m not sure if Corporate Headquarters was ever the same after that. Because we were able to stay on for the next four weeks, we were invited to an SAP banquet that we would have otherwise missed. We stood out like a sore thumb. I will write more about that banquet in a separate post as well as go into detail with some of the jokes that we played on Kent Norris.
Spending the 12 weeks in Corporate Headquarters was an important turning point in my career as a Power Plant Electrician. When we were in the bullpen cube, I was sitting in a chair where I could turn my head to the right and look out a window over the parking lot for the building. During the day I would watch people walking to-and-fro going about their business.
I had worked most of my adult life up to that point at a plant out in the country where when you climbed to the top of the 500 foot smoke stack and looked around, you could see fields and trees for 20 miles in any direction. Looking out that window at people made a big impression on me. Here I was sitting in an air conditioned office. No Coal Dust. No Fly Ash. No ear plugs to deafen the sound of steam shooting through the pipes turning the turbines. No 100 degrees in the summer. No freezing my fingers off in the winter. Just Power Plant Men quietly tapping on their computer keyboards, while they played jokes on Corporate Executive Kent. — This was the life.
I thought… things don’t get better than this. I was in computer heaven. Even though it was unconscious at the time, something stirred in me that thought… maybe… just maybe, I’m ready for a change…. I’ll wait and see what God wants me to do…
Comments from previous posts
Favorites Post #31
Originally posted May 2, 2015
The electric company in Oklahoma decided late 1995 that it was about time that the employees in the company learned about the Internet. The company recognized that the vast amount of information on the Internet was very useful and encouraged everyone to start using it. A request form was available to request access to various features the Internet provided and with your Foreman’s approval, all you had to do was take a short course in Internet Etiquette and you were in (well almost). The problem with this effort was that no one bothered to teach Plant Management about the Internet, so the “Quest for the Internet” was about to begin.
As the leading computer geek at the coal-fired power plant in North Central Oklahoma I had been accessing the Internet for years. I had used CompuServe and Telnet to log into the Internet before Internet Browsers and World Wide Web (WWW) were available.
I thought it was a great idea for everyone to use the Internet, so when Alan Kramer gave us the form it didn’t take long before I filled it out. Sounds pretty simple….. but unfortunately, after a short misstep on my part, a six month battle was about to begin.
The form was simple enough, you just needed to check the boxes for which part of the Internet you needed to access, and after your foreman signed it, you mailed it to Corporate Headquarters, where you would be scheduled to attend a two hour course on how to properly use the Internet in a business setting. The form was written in a curious way that sort of indicated to me that not a lot of thought had been put into it. It was either that, or the person that created the form didn’t understand the Internet very well. Here’s why:
The different parts of the Internet that you could check that you wanted to access were these: WWW, e-mail, Telnet, NewsGroups, FTP. The World Wide Web (WWW) had yet to become popular. The number of Web sites on the Internet was still less than 250,000. Compare that to today where there is almost 1 billion websites (now in 2020, there are over 2 billion).
Well, e-mail…. you know what that is (though at the time. This was something new). Telnet was the usual way I had accessed the Internet for years. I would log in through the Oklahoma State University computer using Telnet, and from there I had access to almost all of the University computers in the country as well as a lot of the Government computers. You could actually print out pages and pages of all the computers on the Internet at the time using a simple seek command.
For those of you who don’t know… Before MySpace and Facebook, NewsGroups were used to communicate to people who had similar interests. They were sort of small blog sites. — I’m not mentioning Bulletin Boards which were independently run sites you dialed up.
On a side note:
I was a member of a number of work related NewsGroups. One NewsGroup that I was active in was for Precipitators. There were about 50 people from all over the world in this group and we all were obsessed with working on precipitators. As it turned out, two of us lived in Stillwater Oklahoma. The other guy worked for a company called Nomadics that made bomb sniffing detectors called Fido. They had a tiny precipitator that collected the particles. We were on the opposite sides of the spectrum. We had a 70 foot tall, 200 foot wide and 100 foot long precipitator, where his precipitator was tiny. I thought a few times about applying for a job with them since they were only 4 miles from my house, but, since I wasn’t an engineer I didn’t think I had a chance of being hired. Besides, what is better than working at a Power plant?
End of Side Note.
FTP, the last item on the list stands for File Transport Protocol. This is how you downloaded or uploaded files after you have used Telnet to connect to a site. It would be hard to let someone have Telnet and not let them have FTP or Newsgroups, so that is why it didn’t look like the person who created the form really knew what they were asking.
I’m sorry I’m boring you with all this, but I’m explaining them for a reason. You see… I’m getting to the part where I made my “misstep”. Maybe it was meant to happen this way, because in the end, everything worked out better than it probably would have if I had just been a little more patient…. Here’s what I did…
After checking each of the boxes, next to WWW, Telnet, NewsGroup, e-mail and FTP, I went to the foremen’s office to have Alan Kramer sign the form so that I could mail it off to Corporate Headquarters. When I arrived, Alan was gone. He had left early that day for some reason, so I walked into Jasper Christensen’s office, our Supervisor of Maintenance and asked him to sign it. Big mistake.
I wrote a post recently about Jasper’s lack of computer knowledge and how I had goaded him for making a dumb computer decision, (see the post “Power Plant Trouble With Angels“). When I handed him the form, he glanced at it, and I could see the blank look on his face indicating that he didn’t understand the different terms such as Telnet, FTP and e-mail or WWW. He might have thought he knew what NewsGroups were, but most likely that would have been incorrect.
So, instead of signing the paper, he said, he would review it and get back to me. Well…. that was unexpected. The company was encouraging us to use the Internet, so I figured it was pretty much a slam dunk. From past experience I knew that Jasper was reluctant to approve anything that he didn’t fully understand, which makes some things difficult.
During the “We’ve Got the Power” Program (See the Post: “Power Plant ‘We’ve Got the Power’ Program“) I tried to elicit an approval from Jasper about a simple example of Thermodynamics that I thought was cut and dry, especially since Jasper was the Engineering Supervisor at the time. Even though I had a sound argument about how heat dissipates in the Air Preheater, he would never say that he would agree. Only that he understood what I was saying. So, when Jasper said that he would “get back to me on this” I knew what that meant. He was going to try to find out what these different things were.
Two weeks later (note… not the next day… Two Weeks!), Alan Kramer told me that Jasper had decided not to approve my request for Internet access. Somewhat peeved, I went into Jasper’s office and asked him why he wouldn’t approve my request. He responded with, “Give me reasons in writing why you need each of these items on this form.” — Oh. I figured that out right away. He had tried to find out what these things meant, but (without the Internet), it was hard to find the answers. So, he was asking me to tell him what these were.
So, I went back to the Electric Shop office and I wrote a full page paper outlining what each item was (WWW, Telnet, NewsGroups, FTP and e-mail). I also explained why I was requesting access to each of these. For Telnet and FTP, one of the reasons I used was that I would Telnet into the OSHA computer and download MSDS’s (Material Safety Data Sheets) for chemicals we had at our plant. The operators had asked me a number of times if I could give them a copy of an MSDS for chemicals. It is a government requirement to keep an MSDS for every chemical on the plant site, and I could easily download them from the OSHA.gov computer.
When I gave my explanation to Jasper, he said he would study it and get back to me later. Two weeks later (note… um… oh. you get the point. There is something about 2 weeks when it comes to Jasper’s decision-making), Jasper called me to his office and said that during a staff meeting they had discussed my request for Internet access and they had decided that I didn’t need access to the Internet to do my job.
The staff had also decided that the only thing on the list that anyone at the plant needed was e-mail and only Jim Arnold (The Supervisor of Operations) and Summer Goebel (The head engineer) needed e-mail. No one else at the plant needed anything else. — You can see why I used phrases like “Another Brilliant Idea” when describing some of Jasper’s Management decisions. Only two people at the plant needed e-mail… . Sounds funny today, huh?
A few months later, in March 1996, I was sent to Oklahoma City to learn how to install the SAP client on desktop computers. The way I was chosen was that someone downtown called each of the Power Plants and other offices and asked the receptionist who the computer geek was at the plant. Denise Anson, our receptionist gave them my name. We were supposed to change our entire financial, inventory, maintenance, and billing system over to SAP at the end of the year from our mainframe computer system. SAP is called an ERP system or Enterprise Resource Planning system. It combines almost all the computer activities in a company into one package where everything is accessible (by one hacker) in one application.
I will go into the implementation of SAP in more detail in later posts, but for now, I was just learning about installing the client application on the computers at our plant. There were a number of steps to the installation, and a lot of times it would fail. So, they gave us some troubleshooting tips and asked us to share any tips we came up with while we were doing this task.
When I returned to the plant, I went about installing SAP on each of the computers. I think we had 22 computers all together. Anyway, during this time, I was thinking that after 3 months, I would resubmit my request for the Internet, since after all, now everyone had e-mail since we had installed a computer network at the plant with Novell’s Netware in anticipation of going to SAP. It was obvious that we were progressing into the computer age with or without the plant staff.
So, I filled out another request form, and even before asking I wrote up another page of reasons why I could use each of the items on the form. One new reason was that the Thomas Register was now online. This was a large set of books that had information about every supplier and vendor in the United States (and beyond). It was used to find phone number, addresses and other fun stuff about vendors. A set of books could cost $5,000.00 each and you had to buy them every couple of years to keep them current.
I didn’t even need to waste my time writing out my reasons. When I gave the form to Alan, he signed it immediately and handed it back to me. I thanked him and mailed it off. A couple of weeks later I received a note through intra-company mail that I was signed up for an Internet class in Oklahoma City. Since I had been in trouble before with going to classes in Oklahoma City, I made sure I didn’t charge any driving time expenses to go to the class (see the post “Printing Impossible Power Plant Fast News Post“).
The lady who was teaching the class knew who I was, because she had worked with me before on computer issues at the plant. It was a simple course on computer etiquette, how the Internet worked and things we should and should not do on the Internet. At the end of the course, we were told that someone would come by our desk and install the Internet on our computers. — Well, our plant was 75 miles away and I knew that it was rare to have someone from the Computer Department come out to our plant, so I didn’t expect anything soon.
It was now the summer of 1996. I was driving down to the river pumps to clean motor filters with Charles Foster when Denise Anson called me on my radio and said that a guy from the SAP team was calling me. I asked her to patch the call to my Walkie Talkie, and she did. — new note: patching a phone call to a walkie talkie was our version of the Internet at that point.
It was the guy from Corporate Headquarters leading the effort to install all the client applications on the computers. He said they were going to have another meeting because everyone was having so much trouble with the installation. I told him that I had already successfully installed the client on all of the computers at the plant except for one, and that was because it was an old junky one that needed to be re-imaged.
The guy was surprised that we were already finished and said that our site was the first site in the company to complete the installation. Then he excitedly said, “If there is ANYTHING I can do for you, just let me know!” I glanced over at Charles who was driving the truck and could hear our conversation over the radio, and smiled.
I said, “There’s one thing. You see. Our plant is out here in the middle of nowhere. I have completed the Internet training course, but we are so far away that no one ever comes around that would install the Internet on my computer, so if you could send me the files, I’ll install it myself.” He replied, “Sure Thing Buddy! I’ll share a folder where you can go pick up the files.”
After installing the files, I realized that it was just an Internet Explorer browser. We were using Windows 3.2 at this time. After opening the browser and playing around with it for a while, I realized that there wasn’t any control around my username. That is, anyone could come into our office and log on our computer and use the browser. Then we found out that you didn’t even have to log on first (with Windows 3.2, you still booted up in DOS). The Internet was wide open. There were no real controls around the use of the Internet. The only control was just the lack of a browser on the computer!
So, here is what I did next. I went to every computer at the plant (except the staff’s computers) and installed the Internet Explorer browser on them. At each computer, I gave the Power Plant Men the same course I had taken downtown. I told them what they should do and what they shouldn’t. I showed them how the browser worked, and how to setup shortcuts, and other things. Before long every Power Plant Man and Woman at the plant was cruising the Internet except the staff…. After all… they had decided that all they needed was e-mail and only for Summer Goebel and Jim Arnold.
A few weeks (probably 2 weeks, since this IS Jasper) after I had taught all the Power Plant Men at the plant how to use the Internet, Jasper Christensen’s voice came over the radio…. “Kevin! I want to see you in my office right away!”. Okay. The gig was up. I recognized that tone of voice from Jasper. The showdown was about to begin. I was about to be chewed out for making the Internet available to everyone. Maybe even fired. I didn’t know how upset he was going to be when he found out.
As I walked from the Electric Shop to the far corner of the Maintenance Shop to Jasper’s office, I articulated in my mind what I would say. I had decided that the best defense was to explain that all I did was install the Internet browser on the computers. I didn’t have access to actually grant anyone access to the Internet. If everyone has access to the Internet, it isn’t because I gave them access. — This was true.
I took a deep breath just before entering Jasper’s office. I went in his office with the most straight face I could muster. “Here it comes,” I thought…. the six month battle for the Internet is coming to a head. Jasper said, “I want to ask you a question about the Internet.” Trying not to choke on my words and looking as if I was interested by cocking my head a little, I replied, “Yeah? What is it?” I was conscious of my thumb hanging in my right front pocket. I thought it gave me that down home innocent rustic look.
Then Jasper picked up a magazine sitting on his desk and said, “There is this article in this engineering magazine, and it has this website that you can visit. How would I go to that site?” — Oh my Gosh!!!! I wanted to laugh out loud with joy! I wasn’t about to be chewed out at all. He just wanted the computer geek to show him how to use the Internet browser that had been recently installed on his computer!
Jasper obviously hadn’t taken the Internet course, otherwise he would know where the address bar is at the top…… So, I said, “Let me show you.” I walked over to his computer and walked him through each step of the process. When we were done, he turned to look at me and smiled. He said, “Thank you.” I said, “Anytime. Just let me know if you have any other questions.” I turned and walked out of the office.
As I walked back to the Electric Shop Office, I met Charles Foster who wanted to know how it went, as he had heard Jasper call me on the radio. I told him that the battle for the Internet was now over. Jasper has now become a “user”. Life was good.