Hello my friends, my friends, Logistic Beings! We are here today a CD in a Distribution Center, therefore of medicines. Newly opened this operation is quite new.
I wanted to start by showing you the Receiving Process. And it’s nice to demonstrate this example here, precisely due to the fact that it has many opportunities and that the that we will see here the errors that we will see here are very recurring whatever operation you’re visiting or maybe even on your own operation you identify yourself in some cases. Let's go start with identification.
Note that I have the invoice. The lecturer has just finalize the Conference Process of this receipt here. One receipt little.
There are five lines. There are 5 SKU's, so receipt and gave two pallets here is a receipt relatively small, but first point: the lecturer checks the receipt with the invoice document. So, what we understand is that it should be a "Poka-Yoke", that is, at this moment here the conferring power not letting in any mistakes, starts with the presumption that he knows the quantities he should be receiving.
And this over time favors the operator, here in the case, the checker of eventually looking at the pallet and saying: "That quantity is right", without having to count. Poka-Yoke at receipt should be. .
. it could be a role like that, but obviously we indicates the use of collectors, because the operation is much faster. But it could be a role like this, a "Nota Fiscal Mirror" without the quantities.
Hence the name Blind Conference. The lecturer should check knowing that he has five lines to receive and such SKU's. And he should indicate here the quantities conferred by him, so that are being received and someone processes it within the system.
This first non-conformity that we find in this operation here. The second non-compliance, when we look at the invoice document I look for something here that refers to the purchase order. "What are the quantities and items that were actually purchased by the buyer?
" And in this note it is not identified. We will not show obviously the note data, because this is a real case, but it is evident the need for the Purchase Order. So when I was interviewing the lecturer here, asking him "Honey, how do you know you should have these quantities here?
" "Oh no, we will see that later. " So here is the time to stop the operation: only enter if you are right. Do you have a Purchase Order?
Has. The quantities are these? They are.
. . Then you can enter.
And here we go now. . .
I should just do the physical conference: beat the quantities or not. In this case, as it is a medicine, there are some important observations in the label surrounding a Manufacturing Lot, the Manufacturing Date. Because, for example, one of the vehicles or one of the conferences that the lecturer should do here is the validity.
"I still have time to rotate my product in my stock? "So many cases we still recommend that, if it is below 30% of the product's shelf life you can already return it, because I I won't have time to rotate the product. I need, obviously depending on the chain of value that we are talking about, he needs time to be able to do this product rotate with validity.
I can't after delivering it to the customer a practically expiring product. So the Conference Point the quantities and then we’ll go into the specifics of the product: his manufacturing batch is in accordance with that avoiding notes in the note and its expiration date. Closing the physical conference I will tag this product, this pallet with a pallet identification unit.
On here, for example, it has a SKU, just to be able to follow up later on storage that and we will be able to see in the sequence. When we are talking about abandoning the sheet of paper inside the warehouse, we want to use Collectors of Data. In this case, a very simple collector, as well practical where I could be, instead of using paper, I be with everyone the SKU's listed here and with the "thumb" here, quickly typing the quantities in the Blind Conference that I counted here, giving "enter" and the system already says if it is ok and goes to the next SKU by entering the tracking batch of the product and, when checking in.
So we would quickly resolve this. With the paper I would have to do the notes at the Blind Conference, I would go somewhere in the administrative area to type (which also has a point of failure and eventually you can type it wrong), so that the system can tell if it is right or not with the invoice and eventually return to the operation. So, when I use the role in the Blind Conference he is very slow.
I've seen several cases of companies abandon the conference with paper, blind, because it becomes slow, due to lack of technology. So here I link, right? The conference blind is important to be done, even with paper.
Only it’s very slow, so we recommends the use of a data collector that can "beep" the main batch, the code product and simply enter the quantities and you gain speed in operation and consequently productivity, obviously. I think that you can have a good idea of the Receiving Conference Process and in our proposal here is for the blind conference to take place. Therefore, the operator does not know the quantities he has to count.
I hope you liked my name is Carlos Menchik, I am a Senior Consultant at PROLOG and if you have this case in your company, please comment here if your company uses the Conference or not Blind in the Receiving Operation of your warehouse. I hope you enjoyed. Big hug!