Reading through this thread I think I'm in agreement with the majority of posters in saying that if 'experience' and 'competency' were a pre-requisite for doing any work then how would newbies develop.
Newbies should develop under a qualified veteran, after qualified instruction, for a number of years. Yes I see the variables, these are not for me to decide and I am not debating how long training should be only that there should be some. As of now , none is required.
Training only goes so far.
but so far is better than none.
To develop properly you need to be in the 'thick' of it actually making changes, modifying code, coming across and then surmounting obstacles. This is how we as programmers, and as humans, develop and improve.
and if no one is in any danger , I agree with this hands on cavelier aproach. Jump in and get wet. Then discover if you can swim. I have been thrown to the wolves on many occasions, I enjoy the rush.
I think anyone who has been in PLC's for a while will have had that experience of being a bit 'out of their depth' but you work through it and learn from it.
and if you get lucky the first couple of times and no one gets hurt then you gain the confidence to go to bigger things. Maye that's good , sometimes it's not.
The problem with 'licensing' would be that as soon as it was introduced it would become a requirement in order to comply with health and safety laws. This would mean that only the people who had attended the course would be in the programming roles.
I've been around long enough to know that just because you've done the course doesn't mean you can do the job!
yep qualified and certified does not mean good
no training and little experience can't be better.
I think it should be down to individuals to be able to ask for help if they need it or even get someone to check their code if they are unsure of anything.
yeah, my english teacher used this logic on me "Why don't you look up the words you missplled?"
and I said "Why would I look it up in the dictionary if I think that's how it's spelled?!!!! Do YOU look up words you think you spelled correctly???????"
Do you ask someone to check your code if you tested it and it passes your testing and logic checks? What about through lack of knowledge or experience you miss something? and then something bad happens? I have noticed that when someone gets hurt the investigator is usually some guy that has no idea what's going on and gets snowed by the company into blaming the operator and never is the machine or the code ever questioned. And what if I could prove it was a machine defect that caused the injury / death? Who is responsible? The company? the boss? the programmer?
nope.
and that's why we have no certification/ education requirement.
You can't run a daycare without a license and training and inspections. But a 16 year old girl is frequently trusted with all the kids and the house for hours.
I have seen so many shortcuts in every part of manufacturing, and so many good people who were slowly "taught" to accept it due to lack of training.
Someone mentioned Air Force iinstruction.
The USAF will train you on a task until you can not screw it up through lack of knowledge or training and they document every step and have you and the trainer sign off on every task, so when you do screw up, you can be held responsible. You know the job inside and out BEFORE you are let go on your own. Maybe this system is why I feel so untrained as a civilian. Nobody signed off on my PLC training and I dont know what I don't know.
And, to reiterate what has been said many times in the post, machine safety should never be reliant on the PLC anyway.
:site:
No it shouldn't but it many machines it so is. If machine safety was not affected by the PLC I would only have a quality arguement and would drop the whole debate.
I have been drilling safety into every manager I have ever talked to, most don't want to hear it.
Job one is production............safety is rarely in the top 5. I think it should at least make the top 3.