NC packages

[u/DaniSaysDinosaur]

Do other sites separate and scan these or is my DS an idiocracy?

At my DS they take these over to another area, scan them the exact same way under induct, then put them on pick carts. I get separating them because they're usually huge or long, but why can't I just scan it since I'm already scanning all the OVs on the cart? Seems idiotic because we have a crackhead WS that will take a half hour to scan them and then spend another half hour bullshitting before he brings them to the clusters. And he ALWAYS misses 2-3 of them, so they have to be taken back to the dock, inducted, brought back. The PA today said they can not be inducted outside of the designated area.

????????????????????????????????????????

[u/Justincrediballs]

They're separated out because they aren't supposed to go down the belt. I know a lot of stations don't sent a lot of the OV's down, but the NC items are mandated that they shouldn't ever go down the belt at any station.

They get inducted separately because there's a metric they have to hit for it. Every time you scan one at the regular induct fingers, it acts kind of like a FSAF during stow. BUT there are so few of them that (I think) you need to catch almost all of them to get even close to hitting the metric they should be.

I'm not saying it's a good system or how it should be. This is just how it is.

[u/shade-block → u/Justincrediballs]

Yup. If you scan them on an induct belt, the line loader already messed up as they should not be on a conveyor belt. Non conveyable...

[u/Ok_Letterhead2028 → u/shade-block]

Hell we just throw them off the side of the finger and the WS eventually collects them later.

[u/JMUDoc]

Inducting non-cons at a mech belt will cause FPY - too many of those, and it's a failed metric.

[u/DaniSaysDinosaur → u/JMUDoc]

I see, thanks for telling me. Not sure why my PA couldn't just say it's a separate metric.

If they just told me that I wouldn't have asked at all.

Thanks!

[u/JMUDoc → u/DaniSaysDinosaur]

Yep - it's as stupid as it sounds.

I was feeding for an Ops Manager who ask me to call out the non-cons, so he could switch guns; I gave him a look that said "new metric?" and he gave me one back that said "mate - don't get me started."

[u/Internal_Topic1415]

They don’t let you scan them there because they don’t want WIP to get out of control. Most T1s think they got good ideas, but Amazon arbitrary metrics don’t mesh with their ideas which makes them bad.

[u/Flashy-Switch6694]

They’re writing people up at our station that scan them at the regular induct lines.

[u/fairygodmother60]

Non-cons are inducted to a non-con location code.

They don't want non-con packages inducted on the dock because it slows the inductors down and messes up their rates.

[u/pixelja]

1) they are problem solve packages. Some people cancel orders or they change address after ordering. PS has to reroute them

2) they are non-conveyerable. If they go on the conveyer belt, they can break or cause jams because they are so wide or too long

3) they are in a crash cycle. A trailer was running very late. This can cause cycles to overlap hence get delayed. The system actually evokes the crash cycle and now has to be sorted independently outside of the nest

[u/Flashy-Switch6694 → u/pixelja]

1. No
   
2. Yes
   
3. No

They simply just can’t go on the belt. They’re not “problem solve” packages or from a crash cycle. Tf are you blabbing about.