.
Welcome to the world of Supply Chain again...
.
Last time I said that Robust control on "Naming Convention Following Process" can reduce inventory and improve supplier negotiations. Let us start with couple of practical scenarios from industry.
.
On 1o-Jul-09, a customer service executive, while talking to a customer for an over the phone order fulfilment, when entered the item "MW Metal Rotor Blade 17 inches " in the ERP/ System, found that the quantity ordered for that item is 6, whereas they have only 5 items in the warehouse. She took the order, entered the order, back ordered it - the ATP engine runs and she gets a date of its availability in warehouse. She tells the customer that the 6th item will be available on the said date and do the customer wants them to ship the 5 items now and the 6th item on that future date. Customer disagrees and asked to send all 6 on the said date only. The conversation ends and she started taking the next call.
.
The planning engine of the IT system, saw the demand, checked supply available and accordingly planned a new purchase order for the item equal to the safety stock of the item that was 10. Everything worked well as per the script and the item arrives in the warehouse and got shipped to the customer.
.
Now, the 2nd scenario is the same company same day (1o-Jul-09) - another customer service representative got a call for the same item and did the same thing in system. He entered the item as "MW Rotor Blade 17 inches" and found that the stock is 17 whereas the customer wanted only 1. The order got fulfilled immediately and since the quantity was more than the safety stock, planning engine did not take any action.
.
What did we see now? I think we got the pointers now, as how the inventory for the same item increased by 10 and since this item is a high valued item ($500 per item), the inventory went up by $5000, not a small number by any standards. Just because the same item was named differently in the system and even customer service executives know it differently, the stock went up. But, look at the customer service levels - even at a high inventory the service level got impacted by no availability of one name of the item so double impact.
.
The 3rd impact of this issue is that when you buy quantities from supplier, naturally you buy small quantities and hence you have low negotiating influence but if we club the demand of both these names of same items (and who knows how many more names of same item exist in the system and for how many different items), we have a larger order and hence more influence, we can exercise while negotiating with suppliers.
.
Same can happen with the supplier names also, if different departments define the same supplier in the system by different names (assuming low control on naming conventions), they can end buying from same suppliers with different names and hence lose the potentially more influence to negotiate harder. In large companies, the impact of this small anomaly is quite large and my experience says that this issue exists in almost all large companies and just the extent is different. Some companies have this issue limited to just <10> 50.
.
Now, what do we do if we want to check if we have similar issue in our system or not. So, there are intelligent data cleansing tools available in market that will extract the data from your ERP/System as per the rules defined by you, transform the data into an excel for analysis and correction and help you making changes accordingly. In these testing times, overlooking this issue is a crime and we all must take care of this as soon as possible in our organizations.
.
Good Article Puneesh. We are facing similar issue where our client facing challlenge in cleaning the customer data. The data is available in Legacy system and when we conversted to Oracle, we found mismatches. Do you have any Idea if there is a tool available to clean it up?
ReplyDeleteThanks,
Punit
Oh well, my point of view on this is that this was a very badly done implementation. The SOPs were not in place or perhaps badly designed on part number definition process. Whenever a new part is defined, it is GENERALLY the responsibility of the Orders Management team and then the Engineering team to ensure that similar part does not already exist. However, if the organization has different customers who can order the same part - it is wise to separate them with a Customer prefix so that there is a clear segregation and LIABILITY based on Safety stock or even the Forecast with the customer. In such a case, even if your inventory levels go up, you always have the agreement with the customer wrt the liability. IF the organization does not have SPECIFIC customers and just anyone can call and order for parts - well - the order processing team is CERTAINLY responsible to make sure that there is no duplication of part numbers. PLUS it is the DUTY of the implementation team to put together an SOP after working with various departments on the part numbering process since ALL the departments are affected in one way or the other.
ReplyDeleteExcellent point Rajesh! You are right in terms of owning the reponsibilities but another fact is that in the last few years, we saw huge knowledge attrition in companies which contributed to this chaos. Also, the implementation team would have done a good job while deploying the product but then it is in the hands of users to maintain and normally after 3 years when the super users start moving to other departments or roles or companies, the process takes the hit (nobody keeps on opening the SOPs) and this chaos enters the instance
ReplyDeletePunit - Apologies for not answering your question earlier. Yes, there are out of the box tools available in market which can cleanse such data. I have sent you some more details at your mail-id so that you can touch base with the companies that provide such tools.
ReplyDelete