Sober,
In response to some of your items below....
Yes... the total time is considered. At least in the hourly ranks. It doesn't matter where you code the time, it shows up on the center cost report. So, the benefit side is definitely properly accounted. "Creative coding" won't impact that.
On the other hand, if a site uses a tremendous amount of management time, this is not necessarily accounted for. In determining payback, corporate assumes some amount of management time. If a district or site uses a huge amount, this "may" not show up.
Telematics as a safety item was certainly oversold. I did the same here. In my defense, that was the original campaign...
Automotive and Safety were the two new areas that Telematics provided. It turns out the performance gains provided more benefit that I expected...
You have a right to be skeptical based on that information.
However, there is no denying that safety elements are drastically improved.
You may call it harassment. That's your right. I call it attention to detail. For me, it takes little more than a conversation.
In a small amount of cases, the conversation gets intense, but I assure you I have never moved to harassment. I would say the opposite was true ....
P-Man
Originally Posted by pretzel_man
Of course you are not naive to think this is happening elsewhere. It definitely is. Coding out to meeting doesn't help the overall cost picture. It would help indices like SPORH, but not overall cost.
But the operations-level management could care less about the overall cost picture. Their promotion...their very survival...depends solely upon manipulating the "indices" such as SPORH that they are judged on. They are more than happy to waste 45 minutes of employee/steward overtime busting some guys balls over a two minute Telematic discrepancy, because that 45 minute meeting can simply be coded out onto someone elses time.
By the way, some of the best sites have been on the longest and do not have special assignment people in place or manage minutiae. The continually find the next largest issue, fix their dispatch, and use telematics to maintain the results.
Then why is this not a consistent practice company wide?
In no way do I mean to be disrespectful, P-man, but you didnt really answer my question. Has the total cost of Telematics...including the time spent on the nit-picking....ever been factored in when judging the merits of the system, or is this cost being swept under the rug by simply "coding it out"?
One more thing. You mentioned letting "big picture" facts drive one's opinion. When Telematics first came out, I was much against it. I thought we already had enough tools to look at yesterday. Once I saw it and used it, my opinion changed. I can very quickly analyze a driver's day and dispatch and take action.
I have always been consistent in my position that the company has every right to wire its equipment up with whatever sensors and technology it chooses to install.
I have simply been skeptical of whether or not the benefits of the system were truly as great as they were purported to be. I've not seen anything to change that skepticism....particularly when I see some of the costs being hidden through "creative coding".
I also refused to buy into the company line that Telematics was intended to be a "safety" enhancement. Lip service was in fact given to some of the data (backing) during the early stages of implementation, but it amounted to little more than a "flavor of the week" that was simply being spoon-fed to us in order to make the true intentions of the program...increased production through intense harassment and micro-management...more palatable.