Showing posts with label Inventory-modeling. Show all posts
Showing posts with label Inventory-modeling. Show all posts

Monday, 4 August 2014

Next Generation DSRs - An Analytic name is not enough

You need not always build your analytic tools, sometimes you should buy in. If the chosen application does what you need that often makes good economic sense... as long as you know what you are buying.

Let's be clear, an Analytic name does NOT mean there are any real Analytics under the hood.

For many managers, Analytics is akin to magic. They do not know how an analytics application works in a meaningful way and have no real interest in knowing. At the same time, there is no business standard for what makes up "forecasting", "inventory optimization", "cluster analysis", "pricing analysis", "shopper analytics", "like products" or even (my favorite) "optimization".  Don't buy a lemon!


In the worst examples, there is nothing under the hood at all. One promotion-analytic tool I came across recently proudly proclaimed that you (the user) could calculate the baseline and lift for each promotion however you saw fit and then just enter the result into their system. They presented this as a positive feature, but calculating a meaningful baseline and lift is the difficult part!!

I've seen similar approaches for:
  • off-shelf alerting tools that ask you how long of a period of zero sales is abnormal (so they can report exceptions)
  • supply chain systems that need you to enter safety-stocks or re-order-points (so they can figure out when to order).  
  • assortment optimization tools that want you to input product substitution rates.
Hmmm, is a car without an engine still a car?
Many applications use pseudo-analytics. After all, how hard can it be? "cluster analysis" , that's finding groups of things right? I reckon I can figure that out, no stats required. Yeah, right, of course you can... FYI - meaningful, useful clusters may be a little more difficult. It's not that cluster analysis is particularly hard, but neither is it something you can knock together without the right tools or any statistical understanding.
Sadly, I have seen real world examples of pseudo-analytics too in pricing analytics, off-shelf alerting, demographic analyses, inventory optimization and forecasting.
The right tool for the right job. There are many good analytic applications available, but you can still make it useless if it does not suit the task you have in mind. Using a time-bucket oriented optimization program to schedule production runs with sequencing comes to mind. OK, relatively few people are going to understand that one and it's not a DSR application, but it is real, the software vendor did not come out shouting that there would be a problem and 2 years down the line that project was abandoned.

Are DSRs worse than other applications?

I think this kind of feature-optimism, is a general issue in buying any analytic app but my perception is that it is a bigger problem in the DSR space.  Perhaps because the DSR is trying to offer so much analytic functionality to so many functional areas?  Is a DSR really going to handle forecasting, pricing-analytics, cluster-analysis, weather-sensitivity-modeling, promotional analytics, inventory optimization, assortment selection and demographic analysis (note - not a complete list), all as packaged software, for $50K a year?   Not unless they can scale that investment across a huge user-base.  Some will be good, others not so much - be warned.   

Spotting a lemon

An expert in the field (with analytic and domain knowledge) can spot a lemon from quite a distance. If you do not possess one you would be wise to invest in some consulting to bolster your purchasing team. For those applications that pass the sniff-test, the proof of any analytic system is in it's performance. Define rational performance criteria, test, validate, pilot and never, ever, ever rely on a software vendor ticking the box in your RFP.

Monday, 5 May 2014

Recommended Reading: The Definitive Guide To Inventory Management

A little over 15 years go now, I was set the task to model how much inventory was needed for all of our, 3000 or so, products at every distribution center.  Prior to this point, inventory targets had been set at aggregate level based off experience and my management felt it was likely we had too much inventory in total and what we did have was probably not where it was most needed. (BTW - they were absolutely right and we were ultimately able to make substantial cuts in inventory while raising service levels).

I came to the project with a math degree, some programming expertise, practical experience simulating production lines, optimizing distribution networks, analyzing investments and with no real idea of how to get the job done.  The books I managed to get my hands on gave you some idea how to use such a system but no real idea how to build it.  They left out all the hard/useful bits I think.  So, I set about to work it out for myself with a lot of simulation models to validate that the outputs made sense.
Product Details
I still work occasionally in inventory modeling and I'll be teaching some components this fall, so I have been eagerly awaiting this new book : The Definitive Guide to Inventory Management: Principles and Strategies for the Efficient Flow of Inventory across... by CSCMP, Waller, Matthew A. and Esper, Terry L. (Mar 19, 2014)

Full disclosure here: one of the authors, Dr Matt Waller is a friend and colleague of mine.  He brings an astonishing level of expertise to many areas of supply-chain management and inventory modeling is clearly no exception.  Together Matt and Terry Esper have produced a book that (had I possessed it 15 years before it was published) could have short-cut my inventory modeling project by approximately 6 months.

This is not a long book, not quite 200 pages in fact, but it is no lightweight.  If you just want an overview of the topic you could skip the math, but my guess is that if you do that, you will never really understand.  The math is not particularly hard and it's presented in a sort of hybrid math/Excel fashion that I find easy to follow.  I'll also say that I hit my first "ahah!" moment before I got to page 20.  I won't embarrass myself by telling you what it was but something that had bothered me for years suddenly clicked into place.

Unlike most discussion on this topic, this book looks at inventory modeling from the manufacturer's or supplier's point of view right through to the retail shelf.  They also provide a number of means to estimate components of inventory from historical data so you can assess how well your planning and execution system are tracking to plan: something I was aware of but had never really thought through how useful it could be.  Details on how to conduct your own simulation studies in Excel and an overview to the most commonly used forecasting approaches that feed the inventory models round it out.

It's all here, what you need to understand (and if you so wish, build) a system to optimize your inventory  holding.  I highly recommended it.


Friday, 28 March 2014

Back to blogging on "Better Business Analytics"

It's been quite a while, just over 12 months in fact since my last blog post.  In that time, I've been hard at work developing analytic applications for the Orchestro DSR.  (Orchestro's off-shelf alerting tool is especially cool and something I am very proud of contributing to).    I enjoyed my time at Orchestro, they're a good team and have big plans, but one key thing I found out about myself is that I prefer working real-life problems to developing software for someone else to have all the fun :-)

So, I'm now back full-time on consulting and I will occasionally blog on topics of interest to me.   Expect to see more soon on:

  • Next-generations DSRs (Demand Signal Repositories)
  • Retail supply-chain analytics
  • Handling (BIG-ish) data for analytics
  • The right tools for the job (Predictive Analytics, Business Models, Optimization)
  • Some more thoughts on store-clustering
  • Inventory modeling at retail (and why it's different, again)
  • Order forecasting using POS data
  • Further thoughts on SNAP and other ignored demand drivers
  • and if there is something you would like to hear more on ... just drop me a line.



Saturday, 13 October 2012

How to save real money in truckload freight (Part II)


In the first post in this series (Part I) I looked at the opportunities to reduce freight cost from traditional transportation management, but the really big opportunities may lie outside of your transportation team's control.  In this post, we'll look at some additional (and very possibly larger) opportunities.

 By the time a request hits the Transportation Team the damage has been done.  It’s already been decided that something needs to move, how it needs to move and when it must depart/arrive.  This is where you can really save.

Don’t ship things you don’t need to.

This may be obvious but one of the best ways to save money on transportation is to do less of it.  How much of your transportation is driven by real need?    How much could you avoid by tightening up your forecasting process and inventory policies (see [Inventory modeling is not "Normal"] and [Inventory modeling in action]).  What about making better decisions about re-deployment ("Balancing" safety-stocks across DCs).

Don’t expedite when you don’t need to.

Air-freight is very expensive, expedited (team) truckload freight is better, but even truckload freight that must move NOW will probably not give you time to find the best rate.  With a little lead-time you can save a lot of money.   Does it really need to be there by 9:00 am tomorrow morning?   Even if the answer right now is ‘Yes’ what can we do to avoid getting in that situation tomorrow?

Bypass steps in the chain

Does your freight shoot like an arrow from production to shelf?  No? I thought not.  If you were to track a case from production through a manufacturer’s DC  to a retailer’s DC to store it has probably doubled back at least once.  If you have sufficient volume (and lead-time) skip a step you can save on both freight and handling expenses.  Optimally sourcing each order needs you to consider what it will cost to source (and replenish) that order from ALL viable shipping locations not just the default location.  This is a great analytic/optimization problem but to be successful you need it embedded in your order processing system.

Managing peaks in demand

Your transportation team will typically use a number of carriers on each lane they manage and the wide variation in freight rates for these carriers may surprise you.  Cheaper rates are associated with carriers that really want that volume: perhaps because it naturally fits with their networ,k filling trucks that would otherwise travel empty.  Once that capacity is used up, they won’t want to cover any more freight on that lane today, it would cost too much to position the equipment.  The more erratic your demand, the more likely that you have to tender loads to relatively expensive carriers or abandon your plan altogether and buy freight on the open (“spot”) market. 

Can you have any control over these peaks in demand – you bet!   You can handle this within your own network relatively easily.  When shipping to customers, retailer typically have shipping windows when their orders must be received: ship a few loads a day earlier, a few loads a day later, smooth out the demand within a lane and stop having to beg for capacity as often.

Fill those trucks – really fill them

How full is a full truck?   One particularly bad guideline I encountered said a truck was full when there was  38,000 lbs of product in it.  If I can find a way to, legally,  load 46,500 lbs in the trailer it’s as though 8,500 lbs of product just shipped free, effectively saving 18% (8,500/46,500 = 18%) in freight cost.

OK, this is a very extreme case to make a point, but why would anyone plan to 38,500 lbs?  Well it’s because the actual constraints around load building are complex, relating not just to product weight but distribution of weight in the rig and the 3D jigsaw puzzle to physically fit product in the space available and avoid damage in transit .

In the case of the 38,000 lb rule of thumb, some of the product was low density and hit space limits before it hit weight restrictions.  Of course not all the product had that problem, but the rule was generally used.

This needs a good analytic/optimization tool to get right, but the savings can be substantial.  There will be more on this in a subsequent post.  What's this worth?  The range varies a lot, but perhaps up to 5%.

Optimize your network

Every time there is a significant change to your network, an acquisition, a divestiture or just significant growth/decline it's worth running the analytics again to make sure your distribution network is in tune with your needs.  Do you need to add, remove or expand storage locations?  Is it time to change production policies on which products are made where?  For smaller changes in your supply chain, routinely fine-tuning the product flow to avoid unnecessary storage and handling can yield great results. An optimization model can include manufacturing, warehousing and transportation costs to find the lowest cost option overall.

Savings here can be huge (if changes have made your network seriously inappropriate for the supply chain it supports), but even ongoing fine-tuning is worth a few percentage points.


My take


There can be substantially more money to be saved in transportation from changes made outside of the transportation team than within it.  Look to better  forecasting, inventory-optimization, deployment, order-processing, maximizing truckloads and network optimization to save real money. 

What do you think?  Have I missed something?  Does this fit with your experience?

How to save real money in truckload freight (Part I)


How can you save real money in truckload transportation?   In this post, let’s look at the areas that your transportation team manages directly.

Transportation procurement

I’ve seen a number of supply-chain consulting projects conclude (wrongly) that concentrating purchasing power for transportation into fewer hands would drive significant savings, of the order of 10%.  Are there economies of scale in the truckload market? Yes, but primarily at a lane (origin-destination) level: if you are buying freight for Portland to Los Angeles you do NOT get a better rate because you also want to move freight from Cleveland to New York.

You can save some money in administering freight by concentrating it into one team, you may be able to drive more rapid change in management processes or new systems but economies of scale in purchasing – I don’t think so.

On the other hand, In a recent post [How much money can you save from a Transportation Procurement Rate-Bid?] I looked at a study from C.H.Robinson and Iowa-State researchers that concluded that regular freight bids can reduce your freight bid, to the tune of about 3% over a company that does not conduct regular freight bids.  That number looks right on the money to me, absolutely worth doing, especially if your freight is a large proportion of supply chain cost but it's not really BIG.

I also posted on the challenge of getting good benchmarks for truckload freight [...the challenge of transportation rates] and highlighted the CHAINalytics consortium that provides both excellent benchmarks AND quantifies various strategies for driving rates lower.  For the totality of your freight bill, there may be another 1-2 % points to be had there too.

Dedicated routes / dedicated equipment

If you have enough volume it may be possible to set up dedicated equipment and routes and if you can keep these assets  busy it will cost substantially less than if you contract separately for 1 way loads.  I have seen very few opportunities to do this cost effectively: it saves money in the few lanes where it makes sense but it’s probably not going to move the needle in terms of overall costs.

“Carrier friendly” freight / locations

During the last freight capacity crunch, I heard a lot about “carrier friendly freight”.  Think in terms of
  •  Loads that are quick to load/unload. 
  • Shipping Locations that are quick to get through with no waiting
  • Quick payment cycles.

This probably helps but I have not yet met anyone who can put a quantifiable  savings number to any of these “carrier friendly” initiatives.  I suspect that in total they may have a small impact, I’m unsure whether it offsets the cost of creating  it.

TMS optimization

Transportation management systems now include a range of algorithms to help with optimization.  Pulling together smaller orders into single shipments that deliver at multiple stops (“stop trucks”) is a great example of where such systems can drive value.   Or, perhaps it can automatically switch modes for you from truck to inter-modal or rail when you have sufficient lead-time. 

There is real money to be had here, but it does take a lot of setup.  All the constraints around carriers and shipping/receiving locations need to be embedded in the system and maintained on an ongoing basis or it will generate loads that can’t be shipped, moved or received.

Also, understand that the optimizer reviews the options available to you to find the “best” or at least a “good” solution automatically.    If you have given the system relatively few options to consider (by locking down when and how loads must ship), it will have relatively little opportunity to find savings.

My take

A superb transportation purchasing team may be able to save 5% on cost in comparison to a relatively weak team.  To save 10% requires a comparison to almost complete incompetence or a congruence of market and macro-economic forces that will unravel within 12 months.  (You got “lucky”, but it won’t last)


What do you think?   Have you seen opportunities I've missed?

Check out Part II for additional opportunities that may lie outside your Transportation Team's control

Monday, 10 September 2012

Inventory modeling is not "Normal"

We can build models to know how much inventory we need to hold of each product in each location. Do this well and you improve service levels AND reduce inventory.   I've posted on this topic before including an online calculator from a relatively simple Excel model to help you visualize the relationship between uncertainty, lead-time and case-fill rate. (Check out How much Inventory do you really need ?).

I wrapped up that post with a warning/disclaimer that the spreadsheet model was really too simple for real life use, but I didn't tell you why.  Now here's the kicker:  many packages appear to have the same problem and can cause you to severely underestimate your inventory needs and lose sales.


Just so you know, we are going to dip a toe into statistics here, but if you are a supply chain manger and you need to optimize your inventory usage, you need to know this - stick with it.  I'll be gentle, it won't hurt, I promise.

The key problem is that models assume uncertainty in demand follows a Normal distribution.  Something like this:
"Bell-shaped curve" - a Normal distribution


Let's take a simple example to see why this is a problem.  Let's say your forecast for the next month is for 100 units.   The normal distribution for your sales then would be centered at 100 units




You could sell more than 100 or less, but just how much more?  What if this is a hard-to-forecast product that could sell much more or much less.  Let's add in the rest of the horizontal axis.




Sticking with visual analysis for now, it looks as though you expect to sell  around 100 units (your forecast) and you could sell as much as 300 (yeah !!) and as little as -100... excuse me ?  How exactly are you going to sell -100?   Despite the widespread practice of representing returns as negative sales (not a good idea) that is not what this means.  This result is a physical impossibility that cannot ever happen in reality.  We really need a distribution that understands that negative sales are not possible.  Something like this:




The green line tells us that worst case sales are 0 (phew) but could go up to.. about 400 ?  Now what I know that you can't tell visually is that both of these distributions have exactly the same average and the same variability (standard deviation), either one could be used to model the same level of forecast and demand uncertainty...but... the green one shows a realistic possibility of much higher sales, sales that you may want to protect by having extra safety stock.    Set your safety stocks based off the Normal distribution and you will  miss that peak demand when it does happen.  How do you feel about cutting 100 units from total demand of 400?   Using the Normal distribution here can seriously damage your wealth.  (FYI - The green line in this case is from a LogNormal distribution.  It's not the only option available to us but I'll hold that detail for another post.)

BTW - If you want to get into Inventory optimization, modeling this correctly will be much more effective in helping you balance inventory and fill-rates.

If it's dangerous then, why is the Normal distribution so heavily used in practice?  Well, if your uncertainty around what you are going to sell is much smaller, it does a good job. The chart below shows the same Normal and LogNormal distributions for a product with much less demand uncertainty




The 2 distributions are practically the same, though the LogNormal still predicts slightly higher sales at the upper end - the end we are trying to protect with safety stock.

(It's also true that it's just easier to program the math to use the Normal distribution.)

In my experience, demand uncertainty  is often, even normally (pun intended), big enough that using the Normal distribution will cause you to severely underestimate safety-stock and lead to more cut orders (and lost sales) than you planned for.

Does your inventory model have this problem?



Inventory modeling in action

Inventory modeling and inventory optimization attempt to drive out unnecessary inventory from your systems, to improve service levels to your customers.  This does work and can drive very significant reductions in inventory, but, if you lack discipline around execution you will not get as much value as you should.

The list of 10 watch-outs that follows is based on my experience.  Some of  these are mistakes I've made and learned from, others are mistakes I have observed.
  1. You do need a good model.   I've seen a lot of inventory models, some are more "unique" than useful.  This is an area with a solid analytic/statistical framework available that has been real-world tested.   Here's a link to my online calculator  [How much inventory do you really need] or check out this Wikipedia entry for a basic introduction   http://en.wikipedia.org/wiki/Safety_stock  You are not going to build something with common-sense or street-smarts in Excel that can come close.  Do the necessary learning, hire someone that already has it or buy into one of the commercially available packages.
  2. Better models yield better results.  If inventory really matters to you, you may want to invest in a more rigorous level of modeling.  A basic, statistical model will generate results if used well.  A model that better fits your reality will let you cut deeper/faster.  For a simple example check out: [Inventory modeling is not "Normal"].  Some other areas that may warrant extra work/investment: 
    • fitting the most appropriate distributions of uncertainty
    • capturing demand uncertainty effectively
    • handling multi-level distribution networks
  3. You need people who know how the model works.  This does not have to be everybody that ever touches it, but someone either in your organization or that you have easy access to must understand this.  I've seen system-implementers (consultants in this case) hamstring a perfectly good commercial package because they did not understand how the models worked and set it to provide bad recommendations. ("Garbage in - Garbage out")
  4. Integrate inventory recommendations into your planning system.  With good models you will generate unique targets by product and location.  To make this part of the planning process this data must be integrated in to the planning systems: it's completely unreasonable to ask planners to keep this amount of information "in their heads" and to act on it appropriately.
  5. Get supply planners involved. Don't ignore one of your best assets - the people that work with product supply every day.  Their intuitive sense of what works is probably not far wrong, whereas computers have no intuitive sense.  The model should help them challenge their ideas  and refine them it does not replace sense.   Get them involved!  Teach them to work the model inputs, to understand why the model does what it does and create ownership of the answers.  If you implemented months ago and you're still hearing "Your targets aren't right..." you need to work on this.
  6. Measure compliance.  You will, I'm sure, be measuring what happens to your aggregate inventory and service levels.  These should be moving steadily in the right direction.  You need to look down in the weeds though to know if you are getting full value.  Excess inventory mounts up a with few cases here, a weeks extra supply over there and it all adds up. Exception based reporting to find item:locations that are not under control drives deeper/faster results.
  7. Use the right target for each decision.  Your system probably has just one place to embed a safety stock or replenishment point value for each [product:location] combination.  If you have done your modeling work effectively this value will represent your primary replenishment process.  But, what happens if you have alternatives?  Perhaps sourcing from another (expedited) supplier or re-deploying inventory from another facility?  The assumptions you made to generate your target are wrong for this alternative option.  Ignore this and you can spend a lot of money very quickly. Check out [Balancing safety stocks across DCs
  8. Continually update/revise.  Let's assume that your system will automatically record and update statistics around demand uncertainty so you do not have to touch every model every week.  Even so, things change:  manufacturing constraints change over time, your understanding of your own supply chain improves, your willingness to take risks shifts, ... things happen.  If you lock in your inventory targets once a year and forget them your supply chain will under-perform.  Continually tweak and revise the models.  these targets drive your supply systems, the better they are the better you will look.
  9. Resist the temptation to react to one-off events.  It is the nature of uncertainty in your supply chain that most of the time, most orders for most products are filled completely.  When there is a failure, orders get cut, service level for that product drops and it becomes the center of  attention for a period of time.  Understandably, this can become uncomfortable.  However, if your aggregate service-level metrics are in-line and this  appears to be a one-off event, reacting to it by pushing up inventory achieves only that - it pushes up inventory.  
  10. Be tough on inventory AND tough on the causes of inventory.  Your inventory models are not just a way of setting accurate inventory targets.  They are key to understanding what changes to your supply chain would drive lower inventory.  What is the value of:
    • 5 points of improvement in forecast accuracy?
    • a 25% reduction in lead-time from production?
    • replenishing once a week rather than once a month?
    • a delayed deployment strategy for hard-to-forecast  products
    • reducing service levels by 0.5 points
    • stratifying service targets for different groups of products (typically based on volume and/or demand uncertainty)
    • allowing service levels for individual product:locations to float in a wider range and using optimization to minimize the overall inventory while maintaining the aggregate service level target

A successful inventory modeling/optimization project does need a good model but it also needs  great execution.

Saturday, 25 August 2012

Balancing safety-stocks across DCs

Earlier today I saw and responded to a question posted on the IBF (Institute of Business Forecasting & Planning) LinkedIn Group.  It's a question I come across often so I thought I would repost it here (with a few edits).

Question:  
How do I go about preparing an aged inventory analysis? I need to show fast moving,slow moving item, then I want to transfer product with in DC's that are slow so that the amount of SS is balance



Response:
I would be wary of moving stock between DCs ("re-deployment") as a means of balancing safety-stocks, it can be very expensive while providing no no real gain.  Balancing stock is typically best done by rebalancing inventory levels when you next acquire production rather than through re-deployment.  As a general rule don't move anything until you have to: if you do, you will certainly incur freight cost and you may not fix a real problem.

If your inventory levels are very low you may risk cutting orders.  So how do you know if your inventory levels are too low?  In my experience, most businesses operate based on rule-of-thumb guidelines and in doing so risk both excessive stocks and cut orders (across a range of products and locations).  Do you know what your safety-stock really needs to be?  I'm talking about a valid, statistical inventory-model taking into account demand uncertainty (related to your forecast accuracy), supply uncertainty and lead-times?  Or is it more of an educated guess ?

(FYI - the lead-time to move product between DCs is typically very much less than the lead-time for acquiring new production so if you are willing to include re-deployment as part of your ongoing solution you can manage with even less safety stock than a basic models may suggest.)

If you're projecting inventory to drop below this safety stock level within your lead-time, it's time to move your inventory.

At the other end of the scale, you may want to move product because otherwise it may expire through age or otherwise become obsolete.  Again though don't move it unless you have to.  A very similar calculation to that used for safety stock, that takes into account your demand uncertainty can tell you when you are danger of being over-stocked.   Assuming you will lose more money by throwing it away then you will by moving it across country, when inventory exceeds this maximum target, load up a truck and ship it to the closest/cheapest place that will sell through it.  

Sunday, 29 July 2012

WARNING: Bad business analytics may be hazardous to your wealth !

You paid handsomely for the software, perhaps for consulting too and have had some bright sparks working on it for months: the results of your analytics project are in and the answer is ... useless without some understanding of how good the models are it's built on.  If the analyst cannot give you detail on how 'good" the model is for its purpose, all results should come with a wealth warning. 


BAD BUSINESS ANALYTICS MAY BE HAZARDOUS TO YOUR WEALTH.


Let's take a few real-life examples:

  • A project to improve sales forecasting where the accuracy of the forecast was not measured either before or after the project.
  • A project to maximize trailer loading (get more tonnage into freight trailers) with such a bad optimization model that it missed most of the opportunity.
  • A system to improve On-Shelf-Availability (the % of product actually on shelf in grocery stores) built entirely from arbitrary rules with no measurement, at all, of...On Shelf Availability.  Check out my post Point of Sale Data – Supply Chain Analytics for more details on On Shelf Availability.
  • Statistical inventory models to identify how much inventory you really need built entirely without  statistics. (Managing hundreds of $millions in inventory value)
  • Countless excel models that calculate nothing of value.
I could go on..

In many cases the issue is that the people assigned to the task do not have the skills to wield the tools they need.  The trailer loading project listed above was developed without real understanding of how to build an optimization model.  The developer had found an extended version of Excel's "Solver"  tool on the internet (a good small to medium scale optimizer from Frontline Systems).  Unfortunately the Excel model  was bad enough that Solver could only find the optimal solution to the wrong question: the model ran without throwing an error; it was a small improvement on what went before; the results were implemented; and the opportunity to do it right (worth $millions) was lost for a few years.

In other cases, and I saw a new one just this last week, the software tools leave out the diagnostics you need to tell whether the model is good.  Predictive Analytics tools packaged for business use (like price/promotion modeling packages, sales forecasting tools) tend to do this.  I can only assume that this is to prevent confusing the user.  

Before you use any tool's output to make critical decisions, someone with good modeling skills (perhaps your Primary Analytical Practitioner)  needs to check that your models are sound.

As my father taught me: “If a job is worth doing, it's worth doing well.”  How can that not be true when your financial results depend on getting it right ?  


Monday, 25 June 2012

Point of Sale Data – Supply Chain Analytics


I’ve spent a large part of my career working in Analytics for Supply Chain.  It’s an area blessed with a lot of data and I’ve been able to use predictive analytics and optimization very successfully to drive cost out of the system.  Much of what I learned in managing CPG supply chains translates directly to Retailer supply chains it’s just that there is much more data to deal with.  


If you have not read the previous posts in this series, please check out:
·         [Point of Sale Data –Basic Analytics] to see why you need to set up a DSR; and 
·         [Point of Sale Data – Sales Analytics] and [Point of Sale Data – Category Analytics] for some examples as to what else you can do with predictive analytics (and relatively basic POS data).

There is a lot that can be done with POS data from a supply-chain perspective.  Let’s start with a few examples:  
  • Use POS data to enhance your forecasting process. (At least recognize when the retailer’s inventory position is out of position as it will need a correction, thereby impacting what you sell to them.)
  • Measure store level and warehouse level demand uncertainty to calculate accurate safety stock and re-order point levels that make the Retailer’s replenishment system flow more effectively.  (see [How much inventory do you really need?]
  • Calculate Optimal order quantity minimums and multiples to reduce case picking (for you) and case sorting/segregation (for the retailer) 
  • Build optimal store orders to correct imbalances in the supply chain and/or correctly place inventory in advance of events. 
  • Where the retailer provides their forecast to you along with POS data:
    • monitor the accuracy and bias of the retailer’s forecasting process and help fix issues before they drive inappropriate ordering. 
    • build your own forecast (a “reference” model) from the POS data and look at where the 2 forecasts diverge strongly. Chances are that one of them is very wrong: if it’s the retailers forecast that’s wrong, remember that this is what drives your orders.
All of this is good and I certainly don’t discourage you from working on any of them but it seems to me that it may be missing the biggest problem   I may upset a few supply chain folks here (feel free to tell me so in the feedback section), but I’m going to say it as I see it - most retailer supply chain measurements do not help, in fact they distract from the one thing that is crucial – is the product available on the shelf? 

Unless the product is on the shelf where the shopper can find it, when they want to buy it, nothing else matters.  If you delivered to the retailer’s warehouse as ordered, in-full and on time, overall inventory levels at the retailer are within acceptable bounds, the forecast was reasonably accurate and the store shows that they we’re in stock that’s great – but it’s not enough.  The product MUST be on the shelf where the shopper can find it or you wasted all that effort.

And yet, it is very rare to see any form of systematic measurement of On-Shelf-Availability.  The few I have seen are so obviously biased as to be largely useless.  If you have the resources to do so and are interested in setting up a credible off-shelf measurement system, please, give me a call.  Otherwise, how can you know whether your hard work in product supply is really making a difference at this one moment of truth?  You need a good model to flag likely off shelf situations.  Do this well and you can make effective  use of field sales to correct the issues, work with your retailer’s operations team to help fix problem areas, identify planogram problems that are contributing to the issue or even examine whether some products or pack types are more frequently associated with off-shelf and could be changed .

It is possible to look at your sales and inventory history and try to “spot” periods where it looks as though the product was not on shelf.  Imagine a product that typically sells in multiple quantities every day in Store A that has not sold now for 10 days: the store reports having inventory all through this period, but no sales.  It seems very likely then that this product is not getting to the shelf.   For products that sell in smaller quantities it gets harder to guess how many days of zero sales would be unusual. 

You can build your own Off Shelf Alerts tool by (educated) guesswork and many people do.  Using some statistics you can get much “better” guesses.  Better guesses mean that you miss fewer real alerts, your alerts are correct more often and you find those issues with the biggest value to you.

Industry studies typically report that on-shelf positions range between the high 80’s to low 90’s in percentage terms.  Fixing this is probably worth 1%-3% in extra revenue.  What is that worth to you?  

How much inventory do you really need?

If you are following lean methodologies you will have encountered the concept of inventory as waste.   It’s something you have because you cannot instantly manufacture and deliver your product to a shopper when they want it, but not something that the shopper sees any value in.

I find that a very interesting idea as it challenges the reasons that you need inventory, and that’s definitely worthwhile.   However, many of these causes of inventory need more substantial changes in your supply chain (additional production capacity, shorter set-up times, multiple production locations) so as a first step, I suggest that you figure out what inventory your supply chain really needs and why.  Take out the truly wasted, unnecessary stock and then see what structural changes make sense.

Typically you can remove at least 10% of inventory while improving product availability. What’s that worth to you?  If that sounds a little aggressive, I can only say “been there, done that, got the coffee-mug”. (We didn’t do t-shirts).



I’m going to look at this from a manufacturer’s perspective and try to visualize for you why they need inventory and how to quantify the separate components.  Why does a manufacturer have inventory?  Let’s start with an easy one:

Cycle Stock is related to how often you add new inventory to the system.  Manufacturing lines typically make a number of different products, cycling through them on a reasonably consistent schedule.  “We make the blue-widgets around once a month”.  It may not be exactly a month apart and that’s not really important to us.  Once a month, in this case, a batch of blue widgets is made and added to inventory.  Over the course of the next month (or so) that inventory is consumed and inventory drops until we make another batch.  Over the course of 12 months it would look something like the example below.


Cycle Stock across time


Hopefully it’s not too hard to see that while “Cycle Stock” varies from 0 to about 30 days worth of demand, it will average out to about half-way between the peak and trough – roughly 15 days.  If you manufacture your product less frequently, say once every 2 months, Cycle Stock will peak at 60 days of demand and, on average, adds 30 days of inventory to your overall stock position.  If you manufacture your product once a week, Cycle Stock will peak at 7 days of demand and, on average, adds 3.5 days of inventory to your overall stock position.

If you want to reduce Cycle Stock you need to make your product more often.  That probably means reducing the time and lost production associated with line change-overs so changing more frequently is less painful.

Pipeline stock is slightly harder to explain but really easy to calculate.  Pipeline stock is inventory in your possession that is not available for immediate sale.  Good examples would be inventory that is in-transit, or awaiting release from quality testing: you own it but you can’t sell it yet.  Let’s say that from the point of manufacture it takes 3 days to move the product to your warehouse where it can be combined with other products to fulfill customer orders.  This has the effect of increasing your inventory by exactly … 3 days.  It really is that simple.  If you know how long inventory is yours but unavailable to meet demand, you know your Pipeline Stock.

If you want to reduce pipeline stock you need to reduce testing time post production, get your product to market faster even consider adding production capability nearer to your markets to reduce transportation time.

Inventory Build.  This is easy to describe but very difficult to model.   For products with large variations in sales volume across time (typically but not always due to seasonality) there may not be enough production capacity to manufacture everything you need just prior to the demand.    As long as the product can be stock-piled, the manufacturer just makes it earlier and holds it until its ready for sale.  If you want an example, think of Halloween Candy, it hasn’t really just been made in early October. 

So why is it so hard to calculate?  Well inventory models are typically built one product at a time but to know your production capacity availability you need to look at all products using shared resources and production-lines simultaneously and build a production plan that understands all your constraints and your planning policies.  Essentially, you need to build an entire (workable) production plan and that’s typically beyond the scope of an inventory modeling exercise.  Often the best place to get this is from your production planner.

If you want to reduce Inventory Build you may be able to do so by more effective production-planning , (Optimization models may be able to help here).  Alternatively you will need to add production capacity.

Safety Stock is the most complex part of the calculation but thankfully the math is not new and you can buy tools that do this for you.  You can’t make whatever you want whenever you want it (or you have little need for any inventory).  If I was to tell you now that we need another batch of “Red Doodas” it’s going to take some time to organize that.  Apart from purchasing raw and packaging materials you may need to break into the production schedule, reorganize line labor perhaps even organize overtime shifts.  You may say that you could that done in about 7 days by expediting, but you probably do not want to plan on having to expedite very much of your production.  So, think of something more reasonable, an estimate not too conservative but one that you could stick to most of the time…21 days ?  Let’s work with that and call it the “Replenishment Lead Time”.

Now, I want to set my safety stock so that it buffers me from most of the uncertainty I could encounter during the Replenishment Lead Time.  It seems highly unlikely that I will sell exactly what was forecast in the next 21 days.  If I sell less I am safe if unhappy.  If I sell more I need a little extra stock to help cover that possibility.  Similarly, even though I asked for 1000 “Red Doodas”, production does not always deliver what I asked for and sometimes it takes a little longer than it should too.  By measuring (or estimating) each of these sources of uncertainty and then combining them together we can get a picture of the total uncertainty you will face over the replenishment lead-time.  If we also know what level of uncertainty you want the safety stock to cover  we can calculate a safety stock level.

Typically the amount of uncertainty you wish it to cover is expressed in terms of the % of total demand that would be covered.  So, 99% means that safety stock would target fulfilling 99% of all product ordered.  The other 1% would, sadly, be lost  to back-orders; or future orders; or possibly lost completely.    As CPG case-fill rates (as measure of the proportion of cases fulfilled as ordered) are typically closer to 98%, 99% is actually rather high.

[Note: Don’t go asking for the safety stock to cover 100% of all uncertainty as this (theoretically at least) requires an infinite amount of safety stock]

Here’s our previous example with some additional variation (uncertainty) added in demand.  Safety stock has been set so that you should meet 99% of all demand from stock and production kicks off when we project inventory will drop below the safety stock level 30 days ahead.


Cycle and  Safety Stock across time

If there was no uncertainty the inventory would have a low point at exactly the safety stock level with production immediately afterwards.  Clearly actual sales did not turn out exactly as forecast.  Sometimes we sell less (and inventory is a little high when production kicks in).  Sometimes we sell more and sales start to use up the safety stock.

The safety stock level is intended to buffer most of this uncertainty, but as you can see, inventory does occasionally drop to 0 and (for very short periods of time) you would not have enough inventory to meet all orders.  On the days when this happens you will short a lot more than more than 1% of the ordered quantity but over time this would average out to about 1%.

If you want to reduce Safety Stock you have a few options.  Remember that they key inputs are:
·         Replenishment Lead-Time
·         Demand Uncertainty
·         Supply Uncertainty
·         % of uncertainty you want to cover.
If you can reduce any of these, your safety stock will come down.
I've embedded a simple inventory model below that you can use to experiment with the various inputs that drive your need for inventory.

Once you have set up the inputs appropriately for your business take a look at what a change to any of these inputs would do for total inventory.  What if you can:
·         improve Forecast Accuracy by 5 points;
·         reduce Replenishment Lead-Time by 1 week;
·         reduce you Cycle Time by 50%;
·         reduce Pipeline Length by 25% ?

  

Notes
Uncertainty of demand is typically measured by “forecast accuracy”.   There are some variations on the calculation of forecast accuracy but here I am using it as (1 – [Mean Absolute Percentage Error]) measured in monthly buckets.   [Mean Absolute Percentage Error] may seem a little scary, but it actually does exactly what it says, it’s the average, absolute error as a % of the forecast. (Absolute errors treat negative values as positive)


Forecast accuracy is typically measure in fixed periods that are relevant to you.  These may be close to but typically not the same as your Replenishment Lead-Time, so the model will try to estimate the value it needs from the standard metric.


If you are not already measuring your own forecast accuracy, you really do need to start.  A forecast with no sense of how accurate it is, is (relatively) useless.


Disclaimer:  This tool is a reasonable guide  and should give you a good sense of what is driving your need for inventory and what you might do to reduce it.  Ultimately though, its limited by the complexity I wanted to include in the Excel model it’s based off and of course it can only handle one product at a time.   Don't use it to build your inventory policies - invest in the real thing.

Sunday, 22 April 2012

Bringing your analytical guns to bear on Big Data – in-database analytics

I've blogged before about the need to use the right tools to hold and manipulate data as data quantity increases (Data Handling the Right Tool for the Job).  But, I really want to get to some value-enhancing analytics and as data grows it becomes increasingly hard to apply analytical tools.

Let’s assume that we have a few Terabytes of data and that it's sat in an industrial-strength database (Oracle, SQL*Server, MySQL, DB2, …)  - one that can handle the data volume without choking.  Each of these databases has its own dialect of the querying language (SQL) and while you can do a lot of sophisticated data manipulation, even a simple analytical routine like calculating correlations is a chore.
Here's an example:
SELECT
(COUNT(*)*SUM(x.Sales*y.Sales)-SUM(x.Sales)*SUM(y.Sales))/( SQRT(COUNT(*)*SUM(SQUARE(x.Sales))-SQUARE(SUM(x.Sales)))* SQRT(COUNT(*)*SUM(SQUARE(y.Sales))-SQUARE(SUM(y.Sales))))
correlationFROM BulbSales x JOIN BulbSales y ON x.month=y.monthWHERE x.Year=1997 AND y.Year=1998

extracted from the O'Reilly Transact SQL Cookbook
This calculates just one correlation coefficient between 2 years of sales.  If you want to calculate a correlogram showing correlation coefficients across all pairs of fields in a table this could take some time to code as you are re-coding the math every time you use it with the distinct possibility of human error.  It can be done, but it’s neither pretty nor simple.  Something slightly more complex like regression analysis is seriously beyond the capability of SQL.

Currently, we would pull the data we need into an analytic package (like SAS or R) to run analysis with the help of a statistician.  As the data gets bigger the overhead/delay in moving it across into another package becomes a more significant part of your project, particularly if you do not want to do that much with it when it gets there.   It also limits what you can do on-demand with your end user reporting tools. 

So, how can you bring better analytics to bear on your data in-situ?   This is the developing area of in-database analytics:   Extending the analytical capability of the SQL language so that analytics can be executed, quickly, within the database.  I think it fair to say that it’s still early days but with some exciting opportunities:
  • SAS, the gold standard for analytical software, has developed some capability but, so far, only for databases I'm not using (Teradata, Neteeza, Greenplum, DB2)  SAS in-database processing
  • Oracle recently announced new capability to embed R (an open source tool with a broad range of statistical capability) which sounds interesting but I have yet to see it. Oracle in database announcement
  • It’s possible to build some capability into Microsoft’s SQL Server using .NET/CLR   and I have had some direct (and quite successful) experience doing this for simpler analytics.  Some companies seem to be pushing it further still and I look forward to testing out their offerings.  (Fuzzy Logix, XLeratorDB).
No doubt there are other options that I have not yet encountered, let me know in the feedback section below.  


For complex modeling tasks, I am certain we will need dedicated, offline analytic tools for a very long time.  For big data that will mean similarly large application servers for your statistical tools and fast connections to your data mart.

For simpler analysis, in-database analytics appears to be a great step forward, but I’m wondering what this means in terms of the skills you need in your analysts: when the analysis is done in a sophisticated statistics package, it tends to get done by trained statisticians who should know what they are doing and make good choices around which tools to deploy and how.

Making it easier to apply analytical tools to your data is very definitely a good thing.  Applying these tools badly because you do not have the skills or knowledge to apply them effectively could be a developing problem.