Stop buying everything, from paper clips to software? No. You should get a little bit smart about how you are going to ride it out.

Even in normal times, good inventory hygiene suggests that you continuously update your inventory control parameters: reorder points, order quantities, safety stocks, mins, maxes, lead times. Beyond that, you should be updating your inventory strategies, such as adjusting the target service levels or fill rates for every item you hold. That’s the “should.”

But in normal times, it’s easy enough to let those adjustments slide and focus on other things. Then, when the first whiff of recession is in the air, you might get panicky and jump into action in a way that makes it harder to survive the down times. You may look decisive by essentially freezing in place or even shutting some things down, but you risk looking decisive now and foolish later.

Better to take stock of your entire current inventory operation and do that tuning before things get really bad. It is common enough for inventory parameters like reorder points to be set at their current levels by somebody long gone at some time in the distant past for some reason that nobody remembers. Over time, conditions change but the system fails to adapt. So the start of a possible recession is an apt time to run your inventory optimization software to tune up your operations.

You may find that you can remove enough sludge in your current system to offset some or all of the bad news. For instance, your suppliers might be filling orders faster than your software thinks, so you can reduce inventories without risking more stockouts by recalculating reorder points. If you feel you must reduce stocks and ask your customers to accept lower fill rates, you should use your inventory optimization software to identify the best items to put on the chopping block, rather than, say, adjusting every item’s fill rate down by 5%.  If you have thousands or tens of thousands of inventory items, that kind of laser-focused adjustment may not be humanly possible without good software support. But with good software support, it’s doable and useful.

Before you hit the panic button, be sure to squeeze all the inefficiency out of your current operations. If, as is common, you have good software but your people are using only a fraction of its capabilities, fix that and get more out of the investment. If you don’t have modern inventory optimization, make a counter-cyclical decision and get some.

If you want to read more about demand planning, forecasting and find new business opportunities in economic recession, read this Journal of Business Forecasting article from the Institute of Business Forecasting (IBF) here or keep reading our new articles

We work with many customers in many industries to connect our advanced analytical, forecasting, and inventory planning software to their ERP systems. Despite the variety of situations we encounter, some data-related problems tend to crop up over and over. This blog lists ten tips that can help you avoid these common problems.

Once a customer is ready to implement software for demand planning and/or inventory optimization, they need to connect the analytics software to their corporate data stream. In our case, we mainline transaction data directly into the analytical software. This provides information on item demand and supplier lead times, among other things. We extract the rest of the data from the ERP system itself, which provides metadata such as each item’s location, unit cost, and product group.

These tips are important because it is not uncommon for implementation projects to start with great enthusiasm but then quickly bog down because of problems with the data that fuel for analytics. These delays can reduce team enthusiasm, embarrass project leaders, and delay (and thereby reduce) the ROI payoff that ultimately justified the implementation project in the first place.

The importance of connecting the analytics software to the corporate data stream

Here is the list of tips, grouped by the general themes of handling files safely, insuring data integrity, and dealing with exceptions.

Handling Files Safely

1. Have a test environment to use as a “sandbox.” Copy your current data to a test environment where you can safely experiment with the software without risking current operations. Besides helping users learn the ins-and-outs of the new software, having the latest data in the software allows end users to discover any problems with the data.

2. Protect your data extraction rules. If you aren’t utilizing a pre-built connector to your ERP system then you to need to ensure that you can create savable extract rules to move data from your ERP to a file.  Column orders, data types, date formats, etc. should not vary each time the same extract is re-executed.  Otherwise the project gets bogged down in manual errors or confusion in re-extracts after fixes to the data or when new data roll in. All data extraction rules should be saved and available to IT – we’ve encountered situations where files extracted were done so in ad hoc manner resulting in a slightly different formats with each new extract.  We’ve also seen customers work hard to develop a complex and accurate data extraction routine only to find all their work was lost when it was not properly archived.  Both situations led to confusion and project delays.

3. Don’t use Excel native file formats for data transfers. If your planning solution doesn’t have a direct integration to your ERP system, then export ERP data to a flat file format, such as comma delimited (.csv) or tab delimited text files.  Don’t use MS Excel formats such as .xls or .xlsx as the export file type because Excel auto-reformats field values in unexpected ways. Many users assume they need to use .xlsx files if they want to manually review them, not realizing that .csv or .txt files can be opened just as easily and don’t carry the risk of auto-reformats.

Insuring Data Integrity

Data Problems and solutions in Software Implementation. Here is the list of tips, grouped by the general themes of handling files safely, insuring data integrity, and dealing with exceptions.

4. Confirm the accuracy of your catalog data. Export your catalog data (i.e., list of products, list of customers, list of suppliers) and all their relevant attributes.  Check for wrong or suspicious values in the attributes (especially item lead times and costs).  Problematic values include blanks, zeros when you don’t expect zero as a data value, and text strings when you expect numeric values (or vice versa).  It can help to open each extract file in Excel and filter on each attribute field, looking at the unique values to see what jumps out as not like the others (e.g., “1”, “2”, “&&”, “3”…).

5. Confirm the accuracy of your grouping data. Another useful activity that can be done while viewing the product catalog data in Excel is to check major grouping/filtering fields like product family, category or class to make sure no products are assigned to the wrong category, class, or family.  Likewise check any product status/product lifecycle fields, e.g., make sure that you have correctly identified all discontinued products.

6. Check for spurious control characters within text fields. Check that there are no unusual characters extracted in your product descriptions, such as carriage returns or tabs within the description value itself.  If so, make sure you can extract that data using double quote enclosures around the description or else fix data entry errors in the ERP system directly.

7. Verify that data have a standard layout. Check that your extracts of transactional data (e.g., customer orders, customer shipments, purchase orders, supplier receipts) contain no duplicate rows.  If they do, either identify what fields need to be added to make the rows distinct or, if they are truly duplicates, remove the extra copies in the ERP database.

Dealing with Exceptions

8. Detect and react to exceptions. Identify any attributes of transactional data that would mean they should not be used, such as cancelled orders.  Understand the process around mistakenly entered orders or cancelled orders to ensure against counting, or double counting, these types of transactions.  Watch for other data attributes that would imply that attribute should not be used, such as drop shipping to the customer directly from a supplier rather than shipping it from your own company. 

9. Codify the handling of exceptional internal transfers. Define the idealized record of emergency internal stock transfers and then provide rules to edit any transactions done on an emergency basis that vary from the ideal pattern.  For example, if product P1 is supposed to be shipped out of location A, but there was an emergency shipment out of location B, the demand history for P1 at location A is hijacked and less than it should have been.  If possible, provide a rule on the preferred shipping location for each product so that the history can be corrected by the inventory optimization software for forecasting purposes.

10. Devise a procedure to handle supersession. Supersessions arise, for instance, when adopting a new ERP which re-indexes the products, or an old product is replaced by an updated version, or an entirely new product obsoletes and old one. If product identifiers changed within the past few years for any reason, identify a mapping from the old product ID to the new.  These rules should be available to the demand planning and forecasting system and editable within the application.

Failure to anticipate data problems is a major impediment to smooth implementation of new analytical software. No list can enumerate all the odd things that can go wrong in curating data, but this one highlights common problems and sensible responses.

Note: For more on how data problems can stymie the application of advanced analytical  software, see Sean Snapp’s excellent blog on how this issue is obstructing the application of artificial intelligence and machine learning.  https://www.brightworkresearch.com/demandplanning/2019/05/how-many-ai-projects-will-fail-due-to-a-lack-of-data/

What We’re Up Against

As a third-generation Boston Red Sox fan, I’m disinclined to take advice from any New York Yankee ballplayer, even a great one but have to agree that sometimes, you just need to make a decision.   However, wouldn’t it be better if we knew the tradeoffs associated with each decision. Perhaps one road is more scenic but takes longer while the other is more direct but boring. Then you wouldn’t have to simply “take it” but could make an informed decision based on the advantages/disadvantages of each approach.

In the supply chain planning world, the most fundamental decision is how to balance item availability against the cost of maintaining that availability (service levels and fill rates). At one extreme, you can grossly overstock and never run out until you go broke and have to close up shop from sinking all your cash into inventory that doesn’t sell.  At the other extreme, you can grossly understock and save a bundle on inventory holding costs but go broke and have to close up shop because all your customers took their business elsewhere.

There is no escaping this fundamental tension. They way to survive and thrive is to find a productive and sustainable balance. To do that requires fact-based tradeoffs based on the numbers. To get the numbers requires software.

The general drift of things is obvious. If you decide to keep more inventory, you will have more Holding Costs, lower Shortage Costs, and possibly lower Ordering Costs. Whether this costs or saves money is impossible to know without some sophisticated analysis, but usually the result is that the Total Cost goes up. But if you do invest in more inventory, something will be gained, because you will offer your customers higher Service Levels and Fill Rates. How much higher requires, as you might guess, some sophisticated analysis.

Show Me the Numbers

This blog lays out what such an analysis looks like. There is no universal solution pointing you to the “right” decision. You might think that the right decision is the one that does best by your bottom line. But to get those numbers, you would need something rarely seen: an accurate model of customer behavior with regard to service level (check out our article “How to choose a target service level”) For example, at what point will a customer walk away and take their business elsewhere?  Will it be after you stock out 1% of the time, 5% of time, 10% of the time? Will you still keep their business as long as you fill back orders quickly?  Will it be after a back order of 1 day, 2 days? 3 weeks? Will it be after this happens one time on one an important part or many times across many parts?  While modeling the precise service level that will allow you to keep your customer while minimizing costs seems like an unapproachable ideal, another type of sophisticated analysis is more pragmatic. 

Inventory optimization and forecasting software can factor all associated costs such as the cost of stocking out, cost of holding inventory, and cost of ordering inventory in order to prescribe an optimal service level target that yields the lowest total cost. However, even that “optimal” service level is sensitive to changes in the costs making the results potentially questionable.  For example, if you don’t accurately estimate the precise costs (shortage costs are the most difficult) it will be tough to definitely state something like “If I increase my on-hand inventory by an average of one unit for all items in an important product family, my company will see a net gain of $170,500.  That gain increases until I get to 4 units.  At 4 units and higher, the return declines due to excessive holding costs. So, the best decision factoring projected holding, ordering, and stockout is to increase inventory by 3 units to see a net gain of over $500,000.  

Short of that ideal, you can do something that is simpler yet still extremely valuable: Quantify the tradeoff curve between inventory cost and item availability. While you won’t necessarily know the service level you should target, you will know the costs of varying service levels.  Then you can earn your big bucks by finding a good place to be on that tradeoff curve and communicating where you at risk, where you aren’t, and setting expectations with customers and internal stakeholders.  Without the tradeoff curve to guide you, you are flying blind with no way to rationally modify stocking policy.

A Scenario to Learn From

Let’s sketch out a realistic tradeoff curve. We start with a scenario requiring a management decision. The scenario we will use and associated assumptions about demand, lead times, and costs are detailed below:

Inventory Policy

• Periodic review – Reorder decisions made every 30 days
• Order-Up-To-Level (“S”) – Varied from 30 to 60 units
• Shortage Policy – Allow backorders, no lost orders

Demand

• Demand is intermittent
• Average = 0.8 units per day
• Standard deviation = 1.2 units per day
• Largest demand in a year ≈ 9
• % of days with no demand = 53%

Lead Time

• Random at either 7, 14 or 21 days with probabilities 70%, 20% and 10%, respectively

Cost Parameters

• Holding cost = $1 per day
• Ordering Cost = $10 per order without regard to size of order
• Shortage Cost = $100 per unit not immediately shipped from stock

We imagine an inventory control policy that is known in the trade as a “periodic review” or (T,S) policy. In this instance, the Review Period (“T”) is 30 days, meaning that every 30 days the inventory position is checked and an ordering decision is made. The order quantity is the difference between the observed number of units on hand and the Order-Up-To Quantity (“S”). So, if the end-of-month inventory is 12 units and S = 20, the order quantity would be S – 12 = 20 -1 2 = 8. The next month, the order quantity is likely to be different. If the inventory ever goes negative (backorders) during a review period, the next order tries to restore equilibrium by ordering more in order to fill those backorders. For example, if the inventory is -5 (meaning 5 units ordered by not available for shipping, the next order would be S – (-5) = S + 5. Details of the hypothetical demand stream, supplier lead times, and cost elements are shown in Figure 1 below. Figure 2 show a sample of daily demand and daily inventory over five review periods. Demand is intermittent, as is often true for spare parts, and therefore difficult to plan for.

Figure 1: Different choices of inventory policy (order up to), associated costs, and service levels

Figure 2: Details of five months of system operation given one of the polices

Inventory Planning Software Is Our Friend

Software encodes the logic of the operation of the (T,S) system, generates many hypothetical but realistic demand scenarios, calculates how each of those scenarios plays out, then looks back on the simulated operation (here, 10 years or 3,650 consecutive days) to calculate cost and performance metrics.

To reveal the tradeoff curve, we ran several computational experiments in which we varied the Order-Up-To Level, S. The plots Figure 2 show the behavior of the on-hand inventory in “richest” alternative with S = 60. In the snippet shown in Figure 2, the on-hand inventory never comes close to stocking out. You can read that too ways. One, a bit naïve, is to say “Good, we’re well protected.” The other, more aggressive, is to say, “Oh no, we’re bloated. I wonder what would happen if we reduced S.”

The Tradeoff Curve Revealed

Figure 3 shows the results of reducing S from 60 down to 30 in steps of 5 units. The table shows that Total Cost is the sum of Holding Cost, Ordering Cost, and Shortage Cost. For the (T,S) policy, the ordering cost is always the same, since an order is placed like clockwork every 30 days. But the other components of cost respond to the changes in S.

Figure 3: The experimental results and corresponding tradeoff curve showing how changing the Order-Up-To Level (“S”) impacts both Service Level and Total Annual Cost

Note that the Service Level is always lower than the Fill Rate in these scenarios. As a professor, I always think of this difference in terms of exam grading. Each replenishment cycle is like a test. Service Level is about the probability of a stockout, so it’s a like the grade on pass/fail exam with one question that must be answered perfectly. If there is no stockout in a cycle, that’s an A. If there is a stockout, that’s an F. It doesn’t matter if it’s one unit that’s not supplied or 50 – it’s still an F. But Fill Rate is like a question that is graded with partial credit. So being short one of ten units gets you 90% Fill Rate for that cycle, not 0%. It’s important to understand the difference between these two important metrics for inventory planning – check out this vlog describing service level vs. fill rate via an interactive exercise in Excel.

The plot in Figure 3 is the real news. It pairs Total Cost and Service Level for various levels of S. If you read the graph right to left, it tells us that there are dramatic cost savings to be had by reducing S with very little penalty in terms of reduced item availability. For instance, reducing S from 60 to 55 saves close to $800 per year on this one item while reducing service level just a bit from (essentially) 100% to a still-impressive 99%. Cutting S some more does the same, though not as dramatically. If you read the graph left to right, you see that moving up from S = 30 to S = 35 costs about $1,000 per year but improves Service Level from an F grade (45%) to at least a C grade (71%). After that, pushing S higher costs progressively more while gaining progressive less.

The tradeoff curve doesn’t give you an answer to how to set the Order-Up-To Level, but it does let you evaluate the costs and benefits of each possible answer. Take a minute and pretend that this is your problem: Where would you want to be along the tradeoff curve?

You may object and say you hate your choices and want to change the game. Is there escape from the curve? Not from the general curve, but you might be able to shape a less painful curve. How?

You may have other cards to play. One avenue is to try to “shape” the demand so that it is less variable. The demand plot in Figure 2 shows a lot of variability. If you could smooth out the demand, the whole tradeoff curve would shift down, making every choice less expensive. A second avenue is to try to reduce the mean and variability of supplier lead times. Achieving either would also shift the curve down to make the choice less painful. Check out our article on how suppliers influence your inventory costs

Summary

The tradeoff curve is always with us. Sometimes we may be able to make it more friendly, but we always to pick our spot along it. It is better to know what you’re getting for any choice of inventory policy than to try to guess, and the curve gives you that.  When you have an accurate estimate of that curve, you are no longer flying blind when it comes to inventory planning. 

Physicists like my Smart Software co-founder, Dr. Nelson Hartunian, tell us civilians that everything is different when we drill down to the tiniest level of the world. Physics at the quantum level is quite weird – not at all like what we experience in our usual macroscopic life. Among the oddities are “superposition”, “entanglement”, and “quantum foam.”  Weird as these phenomena are, I cannot help seeing analogs in the supposedly different world of supply chain management.

Consider quantum superposition. Briefly, superposition means any quantum entity can be in two states at once. Schrödinger’s cat is the most famous illustration of this idea. But how many of you readers are also in a state of superposition? Don’t you find yourself being a manager of a team yet a member of your supervisor’s team, a trouble-shooter yet also a forecasting expert or an inventory optimizer and…? And doesn’t all this make you sometimes feel, like that cat, that you are simultaneously both dead and alive? Modern software can ease some of this burden by automating the tasks of demand planning and inventory optimization. The rest is up to you.

A second quantum analog is entanglement. Briefly, entanglement is the linkage between two elements of a system. They can be light years apart, yet changing one part of an entangled system will instantaneously change the other part. This bugged Albert Einstein, who derided it as “spooky action as a distance.” In our regular world, demand planning and inventory optimization are entangled, since the process of inventory optimization sits on top of the process of demand forecasting. Modern software links the two in an efficient interface.

Finally, the quantum foam – one of my favorite ideas. As I understand it, quantum foam is a substitute for empty space: there is no empty space, rather a constant bubbling of “vacuum energy” accompanied by a flux of “virtual particles” being born out of nothing and then disappearing back into nothing. In the supply chain world, the analogs of virtual particles are customer orders. Often it seems that they pop up with no warning out of thin air, and sometimes they disappear by cancellation in an equally random and mysterious process. This kind of demand fluctuation is the basis for all the theory of inventory control. Modern software therefore begins with probability models of customer demand. Those models then have implications for such tangible quantities as safety stocks, reorder points, and order quantities.

Does it really help demand planners and inventory managers to think about these ideas from quantum physics? Well, it’s a bit of fun to see the analogies to our regular world of work. And they do remind us of more macroscopic matters: the basic concepts of the need to deal with more than one task simultaneously, the linkage between forecasting and inventory management, and randomness as the fundamental feature of the supply chain.