Home
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
What's really going on? Someone shed some light.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="curiousbrain" data-source="post: 1016468" data-attributes="member: 31608"><p>OK. So, I'm going to walk through what *I* think happened - others are free to tell me I'm full of it, blah blah blah ... but, we are all free to make our own judgements in life. So, I shall make mine in this case, and you can make yours.</p><p></p><p>In order to coordinate package/trailer movement through the feeder system at UPS, we use a system called TFCS - wherein, we (e.g. overworked idiots such as myself) enter the time that trailers arrive/depart our operations. These times are "derived" into Arrival/Departure scans - but, as I said, we are overworked; so, anytime you see an "arrival/departure" scan, I would take it with a grain of salt ... reason being, we are so overworked, we are invariably doing a bunch of other crap to keep track of when exactly trailers arrive/depart.</p><p></p><p>The "Out for Delivery" scan is also a "derived" scan; this scan means that a particular package has been hit with a SPA/PAL label (something we use internally to identify where a package goes - i.e.: what truck, what route, so on and so forth), and has allegedly been loaded in the right truck, to be delivered to you ... the consignee.</p><p></p><p>OK. So, that brings us to the first OFD scan: at 8/9, at 5:12 AM - the package was SPA'd out, and in several minutes will be loaded on the right truck for delivery to you. Sadly, there is no scan after that; so, here is where you start with your case against your local center. Ask them to find you a Discrepancy Report (via PFT) from 8/9/2012, and explain why there was a DNED for your package - if there is no DNED for you, that is an even bigger problem. Tell them to track it via eTT; make sure eTT matches your report.</p><p></p><p>The next scan is a Destination Scan; that doesn't help you at all. But, notice that the next scan is an OFD at 9:11AM ... I don't know what time the drivers are usually supposed to leave at that building, but 9:11 seems pretty damn late when they have commit times of 10:30 for their air. Maybe ask your local center what time the drivers are supposed to leave; if it is before 9:11, ask them why the hell your package was PAL'd out *after* they were supposed to leave?</p><p></p><p>Next scan is a Not In 1 (NI1); that is a classic tactic of avoiding responsibility by management/drivers (perhaps a collusion of both, I am not pointing fingers at either specific party). But, you said you "rescheduled delivery" ... did you track the package, see the NI1, then reschedule, or did you reschedule *after* 5:36PM? That is important, because it implies dishonesty on UPS's part.</p><p></p><p>If you actually requested redelivery, then the MyChoice scan (or DCO, whatever) will be an honest scan.</p><p></p><p>Ok, let's move on to the 13th, which is particularly interesting.</p><p></p><p>So, your package was re-PAL'd at 5:37AM - travelling the UPS belt system and allegedly being loaded into the right truck. Except, it says that at you, as the consignee, requested a delivery change already, at 6:19AM, on Monday? And, apparently, we just ignored your package entirely on Tuesday, and only on Wednesday did we decide to "complete" your delivery change request?</p><p></p><p>Again, ask your local center for the DNED/Missed package report for 8/14 ... maybe your package is on it? If it is, it means your parcel was just laying around somewhere in the building; and we were obviously to busy to get it to you. For a variety of reasons, that is unacceptable.</p><p></p><p>Yet, suddenly, on 8/15, your Delivery change request (that you never mention having made) was processed; sweet.</p><p></p><p>It is scanned again, on 8/16, at 8:36AM, at your local delivery center. It was scanned as 1:02PM as "missed" ... I can't stress enough how much management teams try and avoid "Missed" scans ... you do not randomly scan things as "Missed". And, for it to be scanned as that so early in a day, when management (or others) could still shuttle the misload, that smells fishy. Also, if it was a damage as other people claim, it is preferable to scan it as "Rewrap" rather than "Missed". That may not make much sense to you, as someone external to the company, but a damaged package is preferable to a missed one.</p><p></p><p>Not only that, we "Missed" the package on 8/16, and magically didn't scan the package as anything on 8/17? Come on; some guy with a GSS scanner key entered that tracking number, and "we" sent it back on 8/21.</p><p></p><p>As far as the latter two packages you mention in your latest post, that were RTS, I advice this - ask ... nay, demand ... that your local center/hub look up those tracking numbers in eTT, and find out the user names (ID's, or DIAD ID's) of the person who scanned them as RTS. That will pinpoint the responsibility on someone, and perhaps will begin to unravel the mystery of what is going on with your parcels.</p><p></p><p>Good luck; hope you are able to extrapolate some useful information from that wall of text.</p><p></p><p>edit: As to "who" your local delivery center is, it is Van Nuys; whatever is stamped "Out for Delivery" is your center. So, drive there and speak to them.</p></blockquote><p></p>
[QUOTE="curiousbrain, post: 1016468, member: 31608"] OK. So, I'm going to walk through what *I* think happened - others are free to tell me I'm full of it, blah blah blah ... but, we are all free to make our own judgements in life. So, I shall make mine in this case, and you can make yours. In order to coordinate package/trailer movement through the feeder system at UPS, we use a system called TFCS - wherein, we (e.g. overworked idiots such as myself) enter the time that trailers arrive/depart our operations. These times are "derived" into Arrival/Departure scans - but, as I said, we are overworked; so, anytime you see an "arrival/departure" scan, I would take it with a grain of salt ... reason being, we are so overworked, we are invariably doing a bunch of other crap to keep track of when exactly trailers arrive/depart. The "Out for Delivery" scan is also a "derived" scan; this scan means that a particular package has been hit with a SPA/PAL label (something we use internally to identify where a package goes - i.e.: what truck, what route, so on and so forth), and has allegedly been loaded in the right truck, to be delivered to you ... the consignee. OK. So, that brings us to the first OFD scan: at 8/9, at 5:12 AM - the package was SPA'd out, and in several minutes will be loaded on the right truck for delivery to you. Sadly, there is no scan after that; so, here is where you start with your case against your local center. Ask them to find you a Discrepancy Report (via PFT) from 8/9/2012, and explain why there was a DNED for your package - if there is no DNED for you, that is an even bigger problem. Tell them to track it via eTT; make sure eTT matches your report. The next scan is a Destination Scan; that doesn't help you at all. But, notice that the next scan is an OFD at 9:11AM ... I don't know what time the drivers are usually supposed to leave at that building, but 9:11 seems pretty damn late when they have commit times of 10:30 for their air. Maybe ask your local center what time the drivers are supposed to leave; if it is before 9:11, ask them why the hell your package was PAL'd out *after* they were supposed to leave? Next scan is a Not In 1 (NI1); that is a classic tactic of avoiding responsibility by management/drivers (perhaps a collusion of both, I am not pointing fingers at either specific party). But, you said you "rescheduled delivery" ... did you track the package, see the NI1, then reschedule, or did you reschedule *after* 5:36PM? That is important, because it implies dishonesty on UPS's part. If you actually requested redelivery, then the MyChoice scan (or DCO, whatever) will be an honest scan. Ok, let's move on to the 13th, which is particularly interesting. So, your package was re-PAL'd at 5:37AM - travelling the UPS belt system and allegedly being loaded into the right truck. Except, it says that at you, as the consignee, requested a delivery change already, at 6:19AM, on Monday? And, apparently, we just ignored your package entirely on Tuesday, and only on Wednesday did we decide to "complete" your delivery change request? Again, ask your local center for the DNED/Missed package report for 8/14 ... maybe your package is on it? If it is, it means your parcel was just laying around somewhere in the building; and we were obviously to busy to get it to you. For a variety of reasons, that is unacceptable. Yet, suddenly, on 8/15, your Delivery change request (that you never mention having made) was processed; sweet. It is scanned again, on 8/16, at 8:36AM, at your local delivery center. It was scanned as 1:02PM as "missed" ... I can't stress enough how much management teams try and avoid "Missed" scans ... you do not randomly scan things as "Missed". And, for it to be scanned as that so early in a day, when management (or others) could still shuttle the misload, that smells fishy. Also, if it was a damage as other people claim, it is preferable to scan it as "Rewrap" rather than "Missed". That may not make much sense to you, as someone external to the company, but a damaged package is preferable to a missed one. Not only that, we "Missed" the package on 8/16, and magically didn't scan the package as anything on 8/17? Come on; some guy with a GSS scanner key entered that tracking number, and "we" sent it back on 8/21. As far as the latter two packages you mention in your latest post, that were RTS, I advice this - ask ... nay, demand ... that your local center/hub look up those tracking numbers in eTT, and find out the user names (ID's, or DIAD ID's) of the person who scanned them as RTS. That will pinpoint the responsibility on someone, and perhaps will begin to unravel the mystery of what is going on with your parcels. Good luck; hope you are able to extrapolate some useful information from that wall of text. edit: As to "who" your local delivery center is, it is Van Nuys; whatever is stamped "Out for Delivery" is your center. So, drive there and speak to them. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
What's really going on? Someone shed some light.
Top