Crash report cnc

The low pay operator fuc**d up, but he is low pay, so they saved money. That will work to the bean counters .

" snipped-for-privacy@gmail.com" wrote in news: snipped-for-privacy@74g2000cwt.googlegroups.com:

You'll never get the full story, no matter what kind of report you generate. Many controls have a keylogger built in, this can help. Your best bet is to know the process and have the part and tooling that it crashed on. This can usually tell you fairly quickly what happened.

Why wrote in news:7499e217pea9u7fg61cd70c4f762ngpfvm@

Yup, That $2/hr cheaper person, caused $20,000 worth of damage to a machine. Now, how the bean counters can figure that into a cost savings...I have yet to figure out. Must be that 'new math'.

It takes a good machinist to make good parts.

It takes a good salesman to sell a bean counter on the value of skilled labor.

Good bean counters can see beyond tomorrow's balance sheet, and become self-employed or CFOs.

The good salesmen usually don't take machinists jobs and keep them. They either go self-employed, or find different jobs altogether.

That leaves good machinists in charge of shops full of cheap labor, hoping they can stay 1.5 steps ahead of impending disaster. Because the disaster is only impending, it's not a real cost to be dealt with- yet.

Later,

Charlie

=================== Easy enough --- comes out of different accounts charged to different people/departments. $2/hr person generates credit to Personnel/HR for cost savings [attaboy] while machine crash is shop's fault [boo -- no bonus for you -- send all the work to China].

End of year comments in department head meeting writing next years business plan -- Personnel generated another 40,000$ cost savings this year while you no-loads in the shop spent 200,000$ on machine repairs. What do I have to do? Get a new shop super? You say its the union's fault...:

Basic problem is that the same person/department is not charged for the expenses their "cost savings"/"cost avoidance" generates.

Unka George (George McDuffee)

...and at the end of the fight is a tombstone white with the name of the late deceased, and the epitaph drear: ?A Fool lies here, who tried to hustle the East.?

Rudyard Kipling The Naulahka, ch. 5, heading (1892).

Thats because they are the cheapest bean counters money can buy.

John

I love operate history screens. That decimal point is rather handy when entering offsets.

I've also noticed that a seriously out of alignment lathe has nice new tool holders with black oxide coating intact almost all of the time.

Wes S

Sometimes I wonder if anyone reads the things past file and forget.

Where I work it seems like most turning crashes are:

Not referencing machines after a switch from inch/metric or metric/inch.

Stupid fingers entering bad offsets.

Inserts blowing out.

Poor operator training. Temp training temp, training temp, ...

Parts pulling out of chuck because if you crank up the pressure enough to hold part it ain't round anymore.

Indexing turret when too close to chuck or part to change an insert.

Dropped data from dnc download.

Wrong program loaded.

Running similar parts with different overall lengths (castings) on two different machines at once.

I'm sure we can add to this.

Wes S

"If an account could run a business he would own one."

The reason: Shop owners are, creators, in business to MAKE money. Accountants are history majors in business to save money.

It's kinda like Don Garlits driving a top fuel machine to a WIN, while one of his crew is crying about all the money he is spending on fuel. *Smile

My RANT!

Regards,

I work in the mill dept. But most turning crashes are from "flip-flop" processes. I've seen "temp" employees come in and destroy machines in a short amount of time.

Dale