I'm cool with no paper log or exact record of visit.
Cutting corners comment was all about "funny" strange parts/consumable usage.
Grey
I'm cool with no paper log or exact record of visit.
Cutting corners comment was all about "funny" strange parts/consumable usage.
Grey
I do yield approval sometimes and it is a pain in the eyes to see this kind of reports.
Had many cases, the technician blindly requests parts because upon printing of PM parts it was not reset.
Had to reject many parts requests for not taking the yields
Aye! Cut the crap
Agree with emujo and Grey. It's utter nonsense to throw/replace working parts and do the same job twice. Besides no service log will hamper your colleagues troubleshooting and productivity.
We used to fill service cards on every machine when I was working with Toshiba. Just like Grey I studied machine history on service calls.
Nowadays as one man show I keep electronic logs/files, still missing those 'paper' days though.
A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.
I don't reply to private messages from end users.
We use eauto/remote tech. I absolutely hate the TINY link style buttons. The interface is ok at best IF you’re using it on a laptop. Absolute shit design for a phone. Even a phone with a larger screen.
You can only look up history if you have an actual work order in your queue. So if you’re onsite and asked about another machine, we’ll all you can do is guess.
The other thing is that you still get the tech, as previously mentioned, who “can’t spare a character” or God forbid, write a sentence. You get a description like: “Replaced listed parts”... Then in the next column, a list of part numbers, some common ones recognizable, others not. It’s just lazy, plain and simple.
As a solitary tech, I make it a point to keep pretty good records of my service calls. If I didn't I guess I would have to kick my own ass. I run a smc for every call and write on it what the particulars are, then after I get a pile of these in my inbox I scan them and enter the data into my service files on the computer for easy future reference. There is a little lag time, but this system seems to work out ok.
NEVER ASSUME ANYTHING
The company that I worked for required that that we turned in a report of every service call to include the complaint, what was done, what parts/supplies were used, the SMC and counter sheet.
I don't think I said anything about paper logs. We haven't used those in nearly a decade. I was talking about the call history in Remote Tech, and the not too specific work descriptions. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
Bookmarks