D-Train to Endsville
New Member
Recently the hub i work at upgraded the system so that if a package is scanned into the wrong location, the supes would be notified and the error corrected. however, after dealing with this for awhile, i noticed a great fault in the system that in my opinion is slowing productivity. and lets face it, no matter how important they say safety is, we all know that productivity is the most important to them. i'm rambling on so to the point....
please note that i work in the small sort, and although this would go for the outbounds as well, its the small sort i see the real issue.
the situation i see: in the past if you scanned a package into the wrong bin but caught it, you could simply remove the package and move on with the job. however now, if you scan a package into the wrong bin and catch it, you must now close the bin, remove all the packages scanned, and redo the bag.
now doesn't that seem a little counter productive? simply remove the package from the system is no longer enough to clear your name of a misload.
maybe im getting ahead of myself, but in some ways, the old system is better, even if many packages are sent off to the wrong hub.
i find it surprising that they implemented a new system, that could be MUCH more effective if it could deduce on screen for us that a package that was scanned doesnt belong. doesnt that seem feasible? or am i just crazy? i;ve dabbled in programming in the past and know that regardless of what language our systems were designed with, it would take much to solve the misload issue once and forall.
throw me some feedback. what does the rest of you think?
please note that i work in the small sort, and although this would go for the outbounds as well, its the small sort i see the real issue.
the situation i see: in the past if you scanned a package into the wrong bin but caught it, you could simply remove the package and move on with the job. however now, if you scan a package into the wrong bin and catch it, you must now close the bin, remove all the packages scanned, and redo the bag.
now doesn't that seem a little counter productive? simply remove the package from the system is no longer enough to clear your name of a misload.
maybe im getting ahead of myself, but in some ways, the old system is better, even if many packages are sent off to the wrong hub.
i find it surprising that they implemented a new system, that could be MUCH more effective if it could deduce on screen for us that a package that was scanned doesnt belong. doesnt that seem feasible? or am i just crazy? i;ve dabbled in programming in the past and know that regardless of what language our systems were designed with, it would take much to solve the misload issue once and forall.
throw me some feedback. what does the rest of you think?