@ Supply Chain Management


Three issues in Supply Chain Management 2.0 – Part 3

As mentioned previously, Michael Lamoureux is hosting this year’s Big Bad Blogger Throwdown at his blog – Sourcing Innovation. Here is the link to the announcement of the cross-posting cornucopia. As recounted in the first and second part of this series at Three issues in Supply Chain Management 2.0 and Three issues in Supply Chain Management 2.0 – Part 2, I listed out my three top issues that I think are important for firms to be cognizant about. They were:
1. Supply Chain Talent
2. Closed loop Supply Chain Management
3. Supply Chain Collaboration
In this last post, I will delve into the second and third of the three issues in a more substantive fashion.
The essential design patterns in Web 2.0 are recounted here. The first issue is linked below.
Issue #1: Supply Chain Talent
Issue #2: Closed loop Supply Chain Management
I refer to closed loop supply chain management in a sense that is quite different from the usage that I have encountered at many websites and discussions proceeding on the web. A typical reference to a closed loop supply chain would be like this one linked here – The Challenge of Closed-Loop Supply Chains. The proposition advanced here is that a closed-loop supply chain includes the forward part of the supply chain (i.e. product/material flow from producer to customer) as well as the reverse part of the supply chain (i.e. product/material flow from customer back to the producer). The closed-loop supply chain here has more to do with product flow.
What I mean by closed loop supply chain management includes supply chain decision making and translation into operations and execution on the forward loop and information flow on the reverse loop of the supply chain. This proposition has more to do with information feedback about the effectiveness of the supply chain strategy and how to continually make course corrections in order to address the current market. Such a closed-loop supply chain naturally lends itself to continuous improvement – it is actually continuous improvement expressed in Supply Chain Management.
Remember that in the forward loop, lies strategic decisions concerning the supply chain such as manufacturing configurations, inventory levels, sourcing decisions, investments in supply chain assets etc. These decisions are taken by the few or perhaps within middle management with a view of the world that they have built up with experience and/or sales data (feedback loop), growth forecasts (wishful thinking and/or statistical inferences) etc. The closed loop that exists here is some decision making on the forward loop and data warehouses that either relay information or calculate forecasts on the feedback loop. The actual feedback loop should extend all the way to the customer and the sales rep who interacts with the customer because even if a customer doesn’t end up buying a product the information gathered about the customer within the context of a conversation (apart from a standard sales survey) is quite important for the whole system.
So how does Web 2.0 figure in this particular issue? Today, in Web 2.0, you would observe a proliferation of blogs – “71 million blogs… some of them have to be good – Matt” as the Technorati dogs-ear goes. A blog if anything can be described as the creation of meta-information by experts, semi-experts and downright doofuses that add content (of questionable value) to the information stream. In the case that we’ve been talking about, the customer and the sales-rep play the role of value creators except that instead of it being printed/typed, it is verbal information.
So in order to get at this valuable information, you need to store the conversation between a sales-rep (who is equipped with a vocabulary) and a customer, parse it and glean the required information (and perhaps for purposes of privacy – destroy the conversation at the end of the parsing process). This is the sort of process that Google undertakes within the context of its gMail service – or as I have understood it.
A system of the sort that I have described above, takes the feedback loop closer to the customer than the information that is presently obtained at the point-of-sale.
Read the rest of this entry »

About me

I am Chris Jacob Abraham and I live, work and blog from Newburgh, New York. I work for IBM as a Senior consultant in the Fab PowerOps group that works around the issue of detailed Fab (semiconductor fab) level scheduling on a continual basis. My erstwhile company ILOG was recently acquired by IBM and I've joined the Industry Solutions Group there.

@ SCM Clustrmap

Locations of visitors to this page

Subscribe by email

Enter email:
Delivered by FeedBurner

Enter email to subscribe
May 2007