Originally posted May 23, 2014:
There were three times when I was an electrician at a coal-fired Power Plant in North Central Oklahoma when, according to others, I had done something that they labelled “impossible”. One of those times began when a Plant Engineer Toby O’Brien came to me and asked me if I could find a way to connect to the Prime Computer down at Corporate Headquarters so that he could edit some Engineering drawings he had worked on when he was working at Oklahoma City. That in itself wasn’t what was impossible. That came later, but it pertained to a similar subject.
Somewhere in Corporate Headquarters stashed away in a room somewhere was a Prime Computer just waiting for Toby.
Toby knew that I had an account on the Honeywell Mainframe computer downtown, since I was always getting myself in trouble playing around on it. Since I could connect to that, he wondered if it would be possible to connect to the Prime Computer where his Medusa CAD drawings were kept. He gave me some information about how he used to log into it when he was working downtown…. before he was banished to the Power Plant Palace 70 miles north out in the middle of the country.
Toby had a CAD tablet and a disk to install the driver on a computer. This would allow him to work on his CAD drawings. For those of you who don’t remember, or have never seen such a thing. It is like a very fancy mouse…. or should I say, Mouse Pad. Since you used a stylus to draw and point and click on a large pad called a tablet. Not anything like the little tablets we have today.
CAD Drawing Tablet
At the time, the only connection we had to the Honeywell Mainframe from the power plant was through a router called a Memotec. The bandwidth was a whopping 28,000 baud. A Baud is like bytes per second, only it is measured over an audio line as an audio signal. Like the sound that a Fax machine makes when it first connects. Toby had talked to some guys down at IT and they had a copy of the same Honeywell emulator called “GLink” we were using at the plant, only it would connect at a super whopping 56,000 baud. Twice as fast! They wanted someone to “Beta Test” it. They knew I liked doing that sort of stuff, so they were willing to give us a copy to try out.
This is GLink today. Back then it was for Windows 3.1
Toby and I decided that the best place to try out our “Beta Testing” was in the Chemistry Lab. The main reason was that it had one of the newer 386 desktop computers and it was in a room right next to the data closet where the Memotec was talking to the mainframe downtown. So, if I had to run in there real quick and spit in the back and “whomp it a good ‘un”, I wouldn’t have too go far. That was a trick I learned from watching “No Time for Sergeants” with Andy Griffith. Here is the lesson:
If you have trouble viewing the video from the picture above, this this link: “No Time For Sergeants Radio Operator“.
To make the rest of this part of the story a little shorter, I’ll just summarize it to say that by logging into the Honeywell Mainframe using my account, I was then able to connect to the Prime Computer using Toby’s account and he was able to edit his CAD drawings from the Chemistry Lab at the Power Plant 70 miles away from Corporate Headquarters. I know that doesn’t sound like much, but in those days, this was “new technology” for us Power Plant guys anyway.
Before I continue with the “impossible” task, I need to explain a little about how electricians kept the Electrical Blueprints up-to-date at a Power Plant. This was a task that I was given when Tom Gibson was the Electrical Supervisor. I was supposed to take all the blueprints that had been revised because of some change that had happened at the plant, and make sure they were properly updated. Then I had to go through a process to make sure they were permanently updated, not only on the three copies that we had at our plant, but also with the “System of Record” set of blueprints at Corporate Headquarters.
So, let me tell you the process, and I’m sure you will be able to relate this task to something you encounter in your job today. Even if it is preparing the Salads at a Sirloin Stockade before opening time.
The first step happens when someone in the electric shop has to rewire some piece of equipment or something because the equipment was moved, removed, upgraded to something else, or someone thought it would work better if we did it a different way. Then whoever made the change to the electric wiring would go to the prints that were kept in the electric shop and update them so that the new wiring job was reflected in the Blueprints.
This is important because if someone a week later had to go work on this equipment, they would need to be able to see how the equipment is now wired. If they were working off of an old print, then they might blow something up, or injure or even kill someone…. most likely themselves, if it ever came down to it.
The other two copies of prints also needed to be updated. One was in the Instrument and Controls shop, and the most important copy was in the “Print Room” right next to Tom Gibson’s office.
The second step was to send off a request to Corporate Headquarters in Oklahoma City for a copy of all the blueprints that were changed so that the change could be made on the copy and sent back to Oklahoma City.
The third step is when a fresh copy of the blueprints arrived at the plant from Oklahoma City a few weeks later. These were updated with the changes and sent back to Oklahoma City.
The fourth step is when the blueprints are reviewed by an engineer downtown and the changes are made permanently by a drafter downtown.
Step five: Then three copies of the permanently changed prints were sent back to plant where they replaced the three marked up copies.
This process generally took two to three months given that the drafter downtown had to take the Original drawing, scan it in the computer, make changes to it, and then save it, and send it to the printer to be printed.
Toby and I had “petitioned” our plant management to buy us a copy of AutoCAD so that we could make our own revisions right at the plant, and send the changes directly to Oklahoma City, all complete and ready to go. The only problem with this was that AutoCAD software did not come cheap. It was several thousand dollars for just one copy.
Even though this was before the World Wide Web, I knew where I could get a pirated copy of AutoCAD, but since neither Toby or I considered ourselves criminals, we never really considered that a viable alternative. Tom Gibson was pitching for us to have a copy, but it was figured that if we had a copy, the company would have to buy a copy for all six main power plants, and they weren’t willing to dish out that much money.
Somewhere along the line, after Tom Gibson had kept pushing for the importance of having up-to-date Plant Electric Blueprints in a timely fashion, a task force was formed to address a faster way to make print revisions. Because Toby and I (and Terry Blevins) had been pushing this at our plant, Tom asked Toby and I (actually, that should be “Toby and me”, but “Toby and I” makes me sound smarter than I am) to be on the Task Force with him.
So, one morning after arriving at the plant, we climbed into a company car and made the drive to Oklahoma City to the Corporate Headquarters. When we arrived, we sat in a big conference room with members from the different power plants, and a number of engineers from downtown. I was pretty excited that something was finally going to be done.
I don’t remember the name of the engineer that was the leader of the task force, I only remember that I had worked with him once or twice through the years on some small projects. When the meeting began, I expected that we would have some kind of brainstorming activity. I was all ready for it, since I had all sorts of ideas about how we could just edit the prints directly from the plant on the Prime Computer where the prints were stored, just like Toby had done.
When the meeting began there was no brainstorming session. There wasn’t even a “What do you guys think about how this can be done?” No. The engineer instead went on to explain his solution to the problem. I was a little disappointed. Mainly because I was all fired up about being asked to be on a task force in Oklahoma City to work on…. well…. anything…. to tell you the truth. And here we were listening to a conclusion. — Sound familiar? I knew it would.
This engineer had it all figured out. Here was his solution:
Step 1: A request was sent by company mail to downtown (same at the old second step) for some blueprints that need to be updated.
Step 2: The prints are downloaded onto a floppy disk (3.5 inch High Density – which meant, 1.44 Megabyte disks).
Step 3: The disks were mailed through company mail back to the Power Plant.
Step 4: The Power Plant receives the disks and loads them onto their computer at the plant and they edit the blueprint using a pared down CAD program called “RedLine”.
Step 5: The print revision is saved to the disk and the disk is mailed back to Corporate Headquarters using the Company Mail.
Step 6: The print is reviewed by the engineers for accuracy and is loaded into the computer as the system of record.
Ok…. this sounded just like the previous method only we were using a “RedLine” program to edit the changes instead of using Red, Green and Gray pencils.
It was evident that the engineer in charge of the meeting was expecting us to all accept this solution and that the task force no longer had to meet anymore, and we could all go home and not ever return to consider this problem again. — Well, this was when I said the “Impossible”.
I raised my hand as if I was in a classroom. The guy knowing me to be a regular troublemaker asked me what I wanted. I said, “Why mail the files? Why not just put them in a folder and have the person at the plant go there and pick them up?” — In today’s world the idea of a drop-box is about as easy to understand as “Google it”. Back then… I guess not. Especially for some engineers who had already decided on a solution.
So, the engineer responded, “Because that can’t be done.” I said, “Why not?” He said, “It’s impossible. Someone in a power plant can’t just go into a computer at Corporate Headquarters and access a file.”
Well, that did it….. I told him that we were able to edit CAD drawings on the Prime computer from the power plant. He said, “No you didn’t. That’s impossible!” I looked over at Toby who was sitting next to me with a big grin on his face. So I said, “Who is the IT guy in the room? He can tell you that you can get a file from the mainframe from the power plant.”
The engineer replied that he didn’t invite any IT people, because there wasn’t any reason. Everyone knows that you can’t copy files on a Corporate computer from a power plant. So, I said, “Invite someone from the IT department to the next meeting. I’m sure he will agree with me that this can be done. — Shortly after that, the meeting was adjourned (but at least I had managed to convince the team we needed a second meeting).
You should have heard me rant and rave all the way back to the power plant that afternoon. How could he possibly be so naive to make definite statements about something and basically call me a liar when I said that we had already done it. I’m sure Tom Gibson was glad when we arrived back at the plant and he was able to get out of the company car and into the silence of his own car for his drive back to Stillwater. Toby on the other hand carpooled with me, so he had to hear me rant and rave to Scott Hubbard all the way back to Stillwater that day.
Needless to say, we had another Print Revision Task Force meeting a few weeks later. Tom, Toby and I drove back to Oklahoma City. I couldn’t wait to see what was going to happen.
The meeting began with the engineer in charge of the task force saying, “The first thing we are going to address is Kevin Breazile’s statement about sending files to the power plant. We have invited someone from IT to answer this question.” Then he turned to a guy sitting at the table. I don’t remember his name either, only that I had worked with him also through the years (oh yes I do. It was Mike Russell).
The engineer turned to the IT guy and said (using a tone that indicated that I belonged in a mental institution or maybe kindergarten), “Kevin seems to think that he can somehow get on his computer at the power plant and access a folder on a server here at Corporate Headquarters and download a file.” He stopped and with a big smirk on his face looked at the IT guy. Mike just sat there for a moment looking at him.
The engineer just stood there with an evil grin on his face waiting… Mike said, “So? What do you want to know?” The engineer said, “Well. Is that even possible?” Mike replied, “Of course! It’s actually easier for him to do that than it is for someone on the 3rd floor of this building to access the mainframe on the fourth floor.”
The engineer’s jaw dropped and he eked out a meager little “what?” Mike asked if that was all. When he was assured that this was the only question, he stood up and walked out the door. As he was leaving he turned a side glance toward me and winked at me. I was grinning ear-to-ear. I could tell, I wasn’t the only one that had a beef with this particular engineer.
So, you would have thought that it would have been a quieter ride back to the plant that day, but leave it to me…. I kept on going on about how that guy was so sure of himself that he didn’t even bother to ask the IT guy before the meeting began just to check his own erroneous facts. Geez! That was the most surprising part of the day. If he had only asked him before the meeting, he wouldn’t have made a fool out of himself with his snide comments just before he was put in his place.
So, Toby and I proved that doing the impossible isn’t all that impossible when what someone thinks is impossible really isn’t so. This stemmed from a lesson my dad taught me growing up when he told me, “Don’t ever say “can’t”. There is always a way.”