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
Does anybody see anything wrong with this idea?
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: 1160524" data-attributes="member: 31608"><p>Part of it is because all of the scans you see (arrival/departure) scans are what are known as "derived" scans; that is to say, they are not physically scanned, but are derived from a third source - in this case, TFCS.</p><p></p><p>I'm not talking down to anyone, but let's take a simple example of a package transiting from CHEMA to HARCT; first, the customer orders it, the driver (maybe) does a pickup, scans it, shipper does a proper EOD, and it is loaded onto a trailer.</p><p></p><p>There is still no DEPARTURE scan as it is seen by ETT or any external tracking tool; the departure scan is only shown when the unload/primary supervisor "unloads" or "transits" the load in TFCS, which is an archaic system. Once the load (via ULD) is sent out, the departure scan is uploaded to the "public" system and the timestamp is derived from whatever the unload soup entered into TFCS.</p><p></p><p>When the trailer/ULD arrives at another center, the unload soup there "inbounds" that load and the "arrival scan" is derived from that; this daisy chains through the system until it arrives at the distribution hub/center, and it is PAL'd out in the sort aisle, at which point it gets a "DELIVERY SCAN" put on it.</p><p></p><p>To the original point, arrival/departure scans are derived, not physical; and I can tell you from experience, unload soup's fudge the times so they can make their numbers. Which fudges the whole system, in a sense. It has started to get better recently because the new feeders have an automatic inbound/outbound system, but it is still shaky.</p><p></p><p>When a package is scanned as it is being loaded into the outbound, it has no external customer visibility and is purely for internal metric calculations.</p></blockquote><p></p>
[QUOTE="curiousbrain, post: 1160524, member: 31608"] Part of it is because all of the scans you see (arrival/departure) scans are what are known as "derived" scans; that is to say, they are not physically scanned, but are derived from a third source - in this case, TFCS. I'm not talking down to anyone, but let's take a simple example of a package transiting from CHEMA to HARCT; first, the customer orders it, the driver (maybe) does a pickup, scans it, shipper does a proper EOD, and it is loaded onto a trailer. There is still no DEPARTURE scan as it is seen by ETT or any external tracking tool; the departure scan is only shown when the unload/primary supervisor "unloads" or "transits" the load in TFCS, which is an archaic system. Once the load (via ULD) is sent out, the departure scan is uploaded to the "public" system and the timestamp is derived from whatever the unload soup entered into TFCS. When the trailer/ULD arrives at another center, the unload soup there "inbounds" that load and the "arrival scan" is derived from that; this daisy chains through the system until it arrives at the distribution hub/center, and it is PAL'd out in the sort aisle, at which point it gets a "DELIVERY SCAN" put on it. To the original point, arrival/departure scans are derived, not physical; and I can tell you from experience, unload soup's fudge the times so they can make their numbers. Which fudges the whole system, in a sense. It has started to get better recently because the new feeders have an automatic inbound/outbound system, but it is still shaky. When a package is scanned as it is being loaded into the outbound, it has no external customer visibility and is purely for internal metric calculations. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Does anybody see anything wrong with this idea?
Top