tieguy,
That is not true. I am not looking for a script, just an example.
I was hoping you would be so kind to take me through a practical example as to how the EC code is used, authorized and reported.
How would a center manager authorize the following statement the day after a significant snowstorm in his operating area?
"Everyone come in at 9.5 and code any missed stops as EC due to yesterday's snowstorm."
Sincerely,
I
pretzel_man,
Maybe if tieguy remains unwilling to share, you will be so kind to answer the above question. I think it would really add to this discussion thread.
Sincerely,
I
I will give you history so that there will be context. This is how I understand things. I believe it to be correct.....
UPS service used to be measured by doing sampling. Some number of packages were checked to see if they were delivered on the date and time promised. In addition, other measures were in place; missorts, left in building, missed on road, etc. Obviously, those measures were easy to manipulate.
Then a program called SEAS (Service Exception and Analysis System) was built. It took a long time to finish, but it measured service for each and every package, every day. Missorts, visibility reports, service reports were all system generated and greatly reduced any manipulation.
As people here would have guessed, the actual service was much different than our previous reports showed. The system pointed to problems, and operations started fixing them.
Another thing happened though.... The service we measured internally was different than the service from the customers point of view. Bad Address, Weather, Not in, etc. did NOT count against our service measurement. There were too many excuses internally that allowed us to look good but didn't get the package to the customer.
So, Cal Darden said he wanted a "no excuses" service measurement. SEAS was changed to say that it didn't matter why the package wasn't delivered... If it wasn't delivered on the promised date and time, it was a missed service. This "no excuses" measurement went into QPR's, etc.
Over time, the measurement of some codes changed in SEAS. I'm not 100% sure, but I think EC used to count against service measurement. Now I believe EC does not count against service. This came about because of things like Katrina. There was no way to deliver the packages, but they still counted against measured service.
There is an Operations Excellence group in Atlanta that monitors the use of these codes.
As Tie said, if a supervisor just decided to use EC to help their reports, this group in Atlanta will notice. They look at SEAS every day. They send out communications on how they want certain events coded so that the measurements are proper.
I am not aware of any manual that states exactly how to use each code. They handle it on a case by case basis. At least that is how I understand it.
If you need more, I can give you the phone number of the manager in charge of the function.
I can tell you that the system measured service is at an all time high. This can be verified by looking at SEAS and its impressive to see how the measurement works.
In the specific case of this thread, it seems to me that EC was improperly used. But I do not know, and neither do others here. Maybe the OE group approved it for a good reason. Maybe the supervisor just made a mistake. Maybe he / she intended to manipulate reports.
Weith 35,000 management people some will make mistakes, some will be dishonest. I do know that its insincere to point out the bad apple and then assume that all management are that way.