Derivatives
So, the first question that we got on this Blog was related to the supply chain. In my answer, I said that we preferred to deal with the customer facing space for the Enterprise. But, the customer is the end of the supply chain for a retailer. So we kind of have convergence.
One of the examples that we have for review and discussion is a "vintage" application that we created ten years ago for data poor environments. I discuss it because it is an example of the fragmentation of the supply chain and it is an example of how to create estimates that can be used to "run the business" in the absence of a completely automated system - when automation is not cost effective or possible. This may or may not be a problem today for a truly modern environment - in some companies I am sure it is. It is an example though of the reality that businesses deal with all of the time - they have to create estimating tools to manage the business wit.
In the fresh foods departments of supermarkets the business practice was to take an item and use it to produce other items inside of the store. So, an item was shipped to the store - like frozen loaves of French bread. Those frozen loaves could be used in a variety of ways - they could be used make French bread, Italian bread, buns and so on. In fact over twenty items could be produced. Each had a different yield, each had a different retail and as a result - each had a different gross margin.
The usual practice for the department in the supermarket was to estimate gross profit achievable in the store from the shipment to the store out of the warehouse or direct delivery vendor. This did not work when such a variety of different items could be produced - especially when an item like Italian bread was on sale - which was often.
So the category manager needed an "under the desk" (because it sat on a PC - under his or her desk) system that came up with the derivatives of the loaf of French bread (and other items). This was combined with the shipments from the warehouse system, and the sales from the point of sale system to create an estimated gross margin for the business area. Thus, we had a system that could determine the estimated product from the items that were derived from other items.
These types of systems are considered "run the business" systems - created by a non-IT professional and are not part of the census of the IT executive. We believe that the use of Enterprise Web 2.0 tools can help the CIO get control of these systems in a web fast fashion that is in compliance with needs of a post SOX IT organization.
One of the examples that we have for review and discussion is a "vintage" application that we created ten years ago for data poor environments. I discuss it because it is an example of the fragmentation of the supply chain and it is an example of how to create estimates that can be used to "run the business" in the absence of a completely automated system - when automation is not cost effective or possible. This may or may not be a problem today for a truly modern environment - in some companies I am sure it is. It is an example though of the reality that businesses deal with all of the time - they have to create estimating tools to manage the business wit.
In the fresh foods departments of supermarkets the business practice was to take an item and use it to produce other items inside of the store. So, an item was shipped to the store - like frozen loaves of French bread. Those frozen loaves could be used in a variety of ways - they could be used make French bread, Italian bread, buns and so on. In fact over twenty items could be produced. Each had a different yield, each had a different retail and as a result - each had a different gross margin.
The usual practice for the department in the supermarket was to estimate gross profit achievable in the store from the shipment to the store out of the warehouse or direct delivery vendor. This did not work when such a variety of different items could be produced - especially when an item like Italian bread was on sale - which was often.
So the category manager needed an "under the desk" (because it sat on a PC - under his or her desk) system that came up with the derivatives of the loaf of French bread (and other items). This was combined with the shipments from the warehouse system, and the sales from the point of sale system to create an estimated gross margin for the business area. Thus, we had a system that could determine the estimated product from the items that were derived from other items.
These types of systems are considered "run the business" systems - created by a non-IT professional and are not part of the census of the IT executive. We believe that the use of Enterprise Web 2.0 tools can help the CIO get control of these systems in a web fast fashion that is in compliance with needs of a post SOX IT organization.
Interesting - I had not thought about derivatives except in the financial sense. Back to the supermarket, how about applications driven off inventory and customer loyalty information? Just now, my grocery store is beginning to deliver personalized marketing to me based on items I have bought - tracked because I use my loyalty card to obtain a discount. I can imagine that this is just the beginning of what can and will be done with this data in the future. I have heard the mission phrase of "getting into the cart with the customer" in the context of supermarket marketing - any comments? Thanks Fred!
Reply to this
I used the term derivatives to indicate a formula derivation of ingredients based on a relationship (yield per case) that varied based on the item being produced.
In the area of your examples, I am sure that the "mash-up" of customer information is a challenge for many retailers. Household combinations are a big issue for data warehouses in the retail environment. But the profitability of the items purchased, and the shopping tracks through the store are examples of where customer data can be combined in a derivative like sense. Thanks for you comments Cal - good insight.
Fred
Reply to this
Cal - there is an interesting article - Is It Critical to use Customer Analytics - this month (August) in the magazine Retail Solutions Forum - that discusses the "mash-up" of some of the items that were raised in your questions. On-line link Hope this helps.
Fred
Reply to this
So, Kaplan and Norton first published the idea of a Balanced Scorecard in 1992. From there, the notion for all manner of dashboards with forensic drill-down (see Pilot Software for instance)buzzed in the market. These ideas make as much if not more sense today as they did then and yet development and implementation of these concepts are apparently still lagging. Some the analytics challenges are widely known such as the volume and complexity of the data overwhelms traditional OLAP cube solutions (see Panoratio Database Images for a unique solution to that problem). What do you believe are the greatest hurdles? Are they technology or "disbelief in the benefits" hurdles - both? Thanks Fred.
Reply to this