Posted on 05/04/2017 2:40:26 PM PDT by LouieFisk
LOWER ALLOWAYS CREEK TWP. -- A worker "deliberately" attempted to fix an error he had made while conducting tests at a New Jersey nuclear reactor causing the plant to shut down 2 years ago, federal officials say.
(Excerpt) Read more at nj.com ...
I am only 10 miles north of this plant.....YIKES.
Well he could run for President as a DemoncRAT now. He’s eminently qualified.
Was he supposed to not fix the error and allow the reactor to melt down instead of shut down?
“Was he supposed to not fix the error and allow the reactor to melt down instead of shut down? “
The reactor was not going to melt down. It was running fine. He made an error in his test procedure. Standard rule when you make a procedural error is to STOP and NOTIFY.
He ended up entering TWO test signals that caused the plant to shut down.
If he had consulted with supervisors they could have removed the incorrect signal before going to test the right circuit.
“Was he supposed to not fix the error “
He is an example of why you work by procedures and don’t try to fix your mistakes on your own on a reactor safety system.
He DIDN’T fix his mistake! His “fix” cost the company millions of dollars.
“Was he supposed to not fix the error and allow the reactor to melt down instead of shut down?”
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Oy. You did read the article, right?
Years ago I was present during a security check on some computer systems, and the guy doing the inspection asked a worker to log into a particular system. The guy started reaching into a file cabinet ...
The Inspector said: “Did you write down your password? Is that what you’re reaching for right now?”
The guy said, “Uhhhhhhh. No. Because .... uhhhhh ... that would be bad ... right?”
The inspector said, “Look, if you tell us there is a password written down in that file cabinet, it’s bad. But it’s not that bad. If you tell us that you don’t write down passwords, and we find out that you do write down passwords ... then it’s REALLY bad. Get it?”
Guy: “I write down passwords.”
Inspector: “Okay.”
Yup - as the saying goes “it’s the coverup” that is the bigger problem.
I’m not against storing passwords - just, if a person does it, change the file extension from .txt,.doc or whatever, to .dll or other name & extension that doesn’t attract attention. Also, encrypting the file helps.
“Also, encrypting the file helps.”
Where do you store the encryption key?
Here, Hold my Duff.
Make the key the same as the file name.
Is it possible to attempt to fix an error NOT deliberately?
Good point. I guess I’m so used to seeing sloppy journalism that I just don’t pick up on it as much.
Also the number of typos in articles is ridiculous. Breitbart is one of the worst.
“TexasGator to LouieFisk
“Also, encrypting the file helps.”
Where do you store the encryption key?”
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Late in replying, sorry! Good question, tho. In Windows I’d first zip it with 7Zip (free program) and select to encrypt the zip file. A simple, short password that’s very easy to remember will do just fine - especially since no one would ever be looking for anything in a .dll file (for example), anyway.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.