<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Kanban Calculation</title>
	<atom:link href="http://www.resourcesystemsconsulting.com/blog/archives/58/feed" rel="self" type="application/rss+xml" />
	<link>http://www.resourcesystemsconsulting.com/blog/archives/58</link>
	<description>Thoughts on Supply Chain with a Lean and Six Sigma twist.</description>
	<lastBuildDate>Sat, 24 Jul 2010 21:59:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: David McPhetrige</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9902</link>
		<dc:creator>David McPhetrige</dc:creator>
		<pubDate>Wed, 14 Jul 2010 19:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9902</guid>
		<description>Rick,

I agree 100% with Lawrence’s recommendations of using a ROP technique, estimating an EOQ, tracking actual stockouts and doing what you can to minimize daily demand variation.

Let’s see if I’ve properly understood your posts so far:
• Lead time = 1 day (24 hours from replenishment signal to replenishment).
• Replenishment interval = your choice; maximum (ROP + ROQ) is limited by dispensing-machine capacity, minimum can be as little as 1 day.
• Target service level = 95% = 1.645 z-value

Perhaps I could ask several more questions about your situation:
• Does each of the 25 dispensing machines hold all 400 different items? Or, does each dispensing machine hold about 16 items, so that 16 * 25 = 400?
• How often do you want the pharmacy to make a replenishment visit to each of the 25 dispensing machines (once per day, twice per week, etc.)?
• Do you have cost estimates for pharmacy replenishment? Cost per trip to the facility that has the 25 dispensing machines? Cost per trip to a dispensing machine? Cost per replenishment of each item in a dispensing machine?
• Is your week (and the pharmacy’s week) a 7-day week?
• Does the pharmacy always replenish within 24 hours? Or is this an expedite-only lead time? If so, what’s the non-expedite lead time?
• What happens during the 5% of the time when a drug is not available for a nurse? Does the drug get expedited immediately?

FYI – with daily average demand = 3.67, and std dev = 3.74, your example item definitely does not have a normal distribution of demand. Instead, it is doubtless right-skewed, and its demand is probably sporadic (some days have no demand). This is important, because your z-value service-level multiplier assumes a normal distribution. When you use a normality-based z-value with a distribution that is right-skewed, you run the risk of substantially understating the safety stock that’s included in the kanban or ROP calculation.

I’ve made some uneducated (and probably wrong) guesses about your example item’s demand distribution, and some other (probably wrong) assumptions, just for the sake of illustration. I ran my guesses through our proprietary safety-stock model, and came up with these example results for your item with average demand = 3.67 and std dev = 3.74:
Replenish once every 14 days: ROP = 53, ROQ = 53, Safety Stock = 0, Avg Qty On Hand = 28.0
Replenish once every 7 days: ROP = 27, ROQ = 27, SS = 0, AQOH = 16.6
Replenish twice per week: ROP = 14, ROQ = 14, SS = 0, AQOH = 11.9
Replenish once every two days: ROP = 10, ROQ = 8, SS = 2, AQOH = 10.7
Replenish once per day: ROP = 12, ROQ = 4, SS = 8, AQOH = 10.7

Notice that with the longer replenishment intervals, ROP = ROQ. This is because the ROQ itself is providing “de facto” safety stock that achieves the 95% target service level with 95% confidence, without additional calculated safety stock in the ROP.

As replenishment interval (RI) gets smaller, two days or less in this example, ROP &gt; ROQ. This is because the ROQ does not provide sufficient “de facto” safety stock, so the ROP must include additional calculated safety stock.

The “de facto” safety stock provided by larger ROQs is not efficient, in terms of inventory performance. That’s why AQOH drops significantly from the 14-day RI to the 7-day RI, and somewhat less significantly from the 7-day to the 3.5-day. However, from the 3.5-day RI to the 2-day RI, AQOH drops very little, and it doesn’t drop at all from the 2-day RI to the 1-day RI. This supports your intuitive conclusion that there&#039;s no value in replenishing every item every day. These AQOH values are an important component of an EOQ calculation.

I’ll be happy to perform our correct, comprehensive safety-stock analysis on up to 30 of your items as a free trial, just as I’ve offered at http://www.resourcesystemsconsulting.com/blog/blog (about the third posting down from the top). Feel free to contact me at http://www.topdownleansystems.com/contact.php.

Also emphasizing Lawrence’s suggestion, you may also be able to correlate demand to predictive factors such as flu season, etc., and adjust ROPs and ROQs accordingly. The more you can do this, the less you need to depend on a static safety-stock level (whether calculated or “de facto”) to achieve your target service level.

David McPhetrige, TopDown Lean Systems</description>
		<content:encoded><![CDATA[<p>Rick,</p>
<p>I agree 100% with Lawrence’s recommendations of using a ROP technique, estimating an EOQ, tracking actual stockouts and doing what you can to minimize daily demand variation.</p>
<p>Let’s see if I’ve properly understood your posts so far:<br />
• Lead time = 1 day (24 hours from replenishment signal to replenishment).<br />
• Replenishment interval = your choice; maximum (ROP + ROQ) is limited by dispensing-machine capacity, minimum can be as little as 1 day.<br />
• Target service level = 95% = 1.645 z-value</p>
<p>Perhaps I could ask several more questions about your situation:<br />
• Does each of the 25 dispensing machines hold all 400 different items? Or, does each dispensing machine hold about 16 items, so that 16 * 25 = 400?<br />
• How often do you want the pharmacy to make a replenishment visit to each of the 25 dispensing machines (once per day, twice per week, etc.)?<br />
• Do you have cost estimates for pharmacy replenishment? Cost per trip to the facility that has the 25 dispensing machines? Cost per trip to a dispensing machine? Cost per replenishment of each item in a dispensing machine?<br />
• Is your week (and the pharmacy’s week) a 7-day week?<br />
• Does the pharmacy always replenish within 24 hours? Or is this an expedite-only lead time? If so, what’s the non-expedite lead time?<br />
• What happens during the 5% of the time when a drug is not available for a nurse? Does the drug get expedited immediately?</p>
<p>FYI – with daily average demand = 3.67, and std dev = 3.74, your example item definitely does not have a normal distribution of demand. Instead, it is doubtless right-skewed, and its demand is probably sporadic (some days have no demand). This is important, because your z-value service-level multiplier assumes a normal distribution. When you use a normality-based z-value with a distribution that is right-skewed, you run the risk of substantially understating the safety stock that’s included in the kanban or ROP calculation.</p>
<p>I’ve made some uneducated (and probably wrong) guesses about your example item’s demand distribution, and some other (probably wrong) assumptions, just for the sake of illustration. I ran my guesses through our proprietary safety-stock model, and came up with these example results for your item with average demand = 3.67 and std dev = 3.74:<br />
Replenish once every 14 days: ROP = 53, ROQ = 53, Safety Stock = 0, Avg Qty On Hand = 28.0<br />
Replenish once every 7 days: ROP = 27, ROQ = 27, SS = 0, AQOH = 16.6<br />
Replenish twice per week: ROP = 14, ROQ = 14, SS = 0, AQOH = 11.9<br />
Replenish once every two days: ROP = 10, ROQ = 8, SS = 2, AQOH = 10.7<br />
Replenish once per day: ROP = 12, ROQ = 4, SS = 8, AQOH = 10.7</p>
<p>Notice that with the longer replenishment intervals, ROP = ROQ. This is because the ROQ itself is providing “de facto” safety stock that achieves the 95% target service level with 95% confidence, without additional calculated safety stock in the ROP.</p>
<p>As replenishment interval (RI) gets smaller, two days or less in this example, ROP &gt; ROQ. This is because the ROQ does not provide sufficient “de facto” safety stock, so the ROP must include additional calculated safety stock.</p>
<p>The “de facto” safety stock provided by larger ROQs is not efficient, in terms of inventory performance. That’s why AQOH drops significantly from the 14-day RI to the 7-day RI, and somewhat less significantly from the 7-day to the 3.5-day. However, from the 3.5-day RI to the 2-day RI, AQOH drops very little, and it doesn’t drop at all from the 2-day RI to the 1-day RI. This supports your intuitive conclusion that there&#8217;s no value in replenishing every item every day. These AQOH values are an important component of an EOQ calculation.</p>
<p>I’ll be happy to perform our correct, comprehensive safety-stock analysis on up to 30 of your items as a free trial, just as I’ve offered at <a href="http://www.resourcesystemsconsulting.com/blog/blog" rel="nofollow">http://www.resourcesystemsconsulting.com/blog/blog</a> (about the third posting down from the top). Feel free to contact me at <a href="http://www.topdownleansystems.com/contact.php" rel="nofollow">http://www.topdownleansystems.com/contact.php</a>.</p>
<p>Also emphasizing Lawrence’s suggestion, you may also be able to correlate demand to predictive factors such as flu season, etc., and adjust ROPs and ROQs accordingly. The more you can do this, the less you need to depend on a static safety-stock level (whether calculated or “de facto”) to achieve your target service level.</p>
<p>David McPhetrige, TopDown Lean Systems</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Loucka</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9899</link>
		<dc:creator>Lawrence Loucka</dc:creator>
		<pubDate>Wed, 07 Jul 2010 13:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9899</guid>
		<description>With a 95% service level there of course will be times when you will be out of stock.  People will remember being out of stock but won&#039;t easily be able to judge the frequency.  You might want to track a Fill Rate metric.

You might also look at why your standard deviation is so high and if there is anything you can do to dampen or level load.  As a rule of thumb I generally avoid kanban when Cv &gt; 1.0 where the Coefficient of Variation is the standard deviation divided by the mean (or average).

Also, demand can change over time, so you will want to regularly recalculate your order points and order quantities.

Good luck!</description>
		<content:encoded><![CDATA[<p>With a 95% service level there of course will be times when you will be out of stock.  People will remember being out of stock but won&#8217;t easily be able to judge the frequency.  You might want to track a Fill Rate metric.</p>
<p>You might also look at why your standard deviation is so high and if there is anything you can do to dampen or level load.  As a rule of thumb I generally avoid kanban when Cv > 1.0 where the Coefficient of Variation is the standard deviation divided by the mean (or average).</p>
<p>Also, demand can change over time, so you will want to regularly recalculate your order points and order quantities.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9898</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 07 Jul 2010 12:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9898</guid>
		<description>Great!  Thanks for the help.  I came up with the same number and just need to bounce it off of an expert.  These drug dispening machines have containers sizes that can be adjusted.  Right now they are all set to a size that will acomidate 2 weeks of drugs (based on 6 months of data converted to a 2 week quantity) ... therefore the sizes can vary.  The order point (low) is set at 1 week, and the critical low point is set at 1/2 of that.  My thought was to use the Kanban order quantity of 9.8 and add to that the average usage of 3.67 (times the number of day I what in the machine ... two weeks to start).  Then optimize by slowly reducing the average number of day OH when everyone feels confortable that the process works.

thoughts?

again thanks for the help!</description>
		<content:encoded><![CDATA[<p>Great!  Thanks for the help.  I came up with the same number and just need to bounce it off of an expert.  These drug dispening machines have containers sizes that can be adjusted.  Right now they are all set to a size that will acomidate 2 weeks of drugs (based on 6 months of data converted to a 2 week quantity) &#8230; therefore the sizes can vary.  The order point (low) is set at 1 week, and the critical low point is set at 1/2 of that.  My thought was to use the Kanban order quantity of 9.8 and add to that the average usage of 3.67 (times the number of day I what in the machine &#8230; two weeks to start).  Then optimize by slowly reducing the average number of day OH when everyone feels confortable that the process works.</p>
<p>thoughts?</p>
<p>again thanks for the help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Loucka</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9897</link>
		<dc:creator>Lawrence Loucka</dc:creator>
		<pubDate>Wed, 07 Jul 2010 11:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9897</guid>
		<description>From your description it seems that the replenishment time isn&#039;t 24 hours.  Semantics - in the kanban calculation replenishment time is the time it takes a card or container to make the complete cycle from empty to full to empty.  Imagine say three containers in circulation.  An empty container is a signal to refill and return to the point of use.  If you put a clock on the container and then follow it through its life you&#039;ll see the full container sitting at point of use, then some parts will be removed, then the container will be empty, and returned to supplier, then refilled, then returned to point of use to sit in queue. In the situation you describe it looks like your replenishment time is 2 weeks plus a couple days.

Perhaps rather than kanban you need to figure out a reorder point, or as you call it &quot;low stock level&quot;.  If restocking is truly only 24 hours from warning system alert then you would set your reorder point at AD + (SF* SD) or (3.67 + (1.65 * 3.74)), or 9.84 or rounded up to 10.  When stock in the machine falls to 10 you order more.

How much more?  Two weeks worth, or something less?  You can look into Economic Order Quantity to optimize inventory carrying cost, order filling cost, and service level.  Or you can use a fixed order quantity with kanban, but you need to rethink the bin quantity of 50, which I suppose is the quantity that your machine will hold?</description>
		<content:encoded><![CDATA[<p>From your description it seems that the replenishment time isn&#8217;t 24 hours.  Semantics &#8211; in the kanban calculation replenishment time is the time it takes a card or container to make the complete cycle from empty to full to empty.  Imagine say three containers in circulation.  An empty container is a signal to refill and return to the point of use.  If you put a clock on the container and then follow it through its life you&#8217;ll see the full container sitting at point of use, then some parts will be removed, then the container will be empty, and returned to supplier, then refilled, then returned to point of use to sit in queue. In the situation you describe it looks like your replenishment time is 2 weeks plus a couple days.</p>
<p>Perhaps rather than kanban you need to figure out a reorder point, or as you call it &#8220;low stock level&#8221;.  If restocking is truly only 24 hours from warning system alert then you would set your reorder point at AD + (SF* SD) or (3.67 + (1.65 * 3.74)), or 9.84 or rounded up to 10.  When stock in the machine falls to 10 you order more.</p>
<p>How much more?  Two weeks worth, or something less?  You can look into Economic Order Quantity to optimize inventory carrying cost, order filling cost, and service level.  Or you can use a fixed order quantity with kanban, but you need to rethink the bin quantity of 50, which I suppose is the quantity that your machine will hold?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9896</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 07 Jul 2010 11:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9896</guid>
		<description>So to summarize:
The machines need to have stock in them when the nurses need the drugs at least 95% of the time.
The pharmacy can refill the machines within 24 hours should the warning system alert them to a low stock level.
I would like to start with the same 2 weeks in the machines and then optimize later.  This is because we have 400 drugs in the 25 different machines and do not want to have someone refilling each position every day.
I can set the warning level to whatever I want ... the question is, what is that level for the above parameters.  I&#039;ll need to do this same process for all machines and all drugs.</description>
		<content:encoded><![CDATA[<p>So to summarize:<br />
The machines need to have stock in them when the nurses need the drugs at least 95% of the time.<br />
The pharmacy can refill the machines within 24 hours should the warning system alert them to a low stock level.<br />
I would like to start with the same 2 weeks in the machines and then optimize later.  This is because we have 400 drugs in the 25 different machines and do not want to have someone refilling each position every day.<br />
I can set the warning level to whatever I want &#8230; the question is, what is that level for the above parameters.  I&#8217;ll need to do this same process for all machines and all drugs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9895</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 07 Jul 2010 11:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9895</guid>
		<description>This is the situation.  I have a drug machine that dispenses drugs to nurses and internal pharmacy that has enough OH stock to refill.  The pharmacy has a 24 hour turn around time when the machines warn they are low.  The issue is that the low warnings are not set properly and we can run out of drugs.  I am trying to optimize the drug machines.  Right now we stock the machines with an average of two weeks of stock based on average daily usage ... but as you can see, the standard deviation is large.  I would like to minimize the stock within these machines while ensuring the nurses have the drugs OH 95% of the time.  My idea was to use the Kanban formula to find the right level of stock and the SF to determine the amount of stock needed for a particular Z.</description>
		<content:encoded><![CDATA[<p>This is the situation.  I have a drug machine that dispenses drugs to nurses and internal pharmacy that has enough OH stock to refill.  The pharmacy has a 24 hour turn around time when the machines warn they are low.  The issue is that the low warnings are not set properly and we can run out of drugs.  I am trying to optimize the drug machines.  Right now we stock the machines with an average of two weeks of stock based on average daily usage &#8230; but as you can see, the standard deviation is large.  I would like to minimize the stock within these machines while ensuring the nurses have the drugs OH 95% of the time.  My idea was to use the Kanban formula to find the right level of stock and the SF to determine the amount of stock needed for a particular Z.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Loucka</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9893</link>
		<dc:creator>Lawrence Loucka</dc:creator>
		<pubDate>Tue, 06 Jul 2010 21:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9893</guid>
		<description>Rick, if your replenishment time is really only one day then why not just use 2 Bins and keep your average daily demand + 2 or 3 standard deviations in each bin.

Also as far as your math goes - your bin quantity of 50 is a variable not a constant!  You can make the bin quantity (or what I call Standard Container Quantity any number you want.  

So OK, lets do some math ... # Kanban = ((AD * R) + (SF * SD))/ SCQ

#K = ((3.67 * 1) + (1.65 * 3.74))/50
#K = 0.19 which doesn&#039;t make sense.  If you change SCQ to say 5 then the number of kanban you need is 1.968.

You certain your replenishment time is 24 hours?</description>
		<content:encoded><![CDATA[<p>Rick, if your replenishment time is really only one day then why not just use 2 Bins and keep your average daily demand + 2 or 3 standard deviations in each bin.</p>
<p>Also as far as your math goes &#8211; your bin quantity of 50 is a variable not a constant!  You can make the bin quantity (or what I call Standard Container Quantity any number you want.  </p>
<p>So OK, lets do some math &#8230; # Kanban = ((AD * R) + (SF * SD))/ SCQ</p>
<p>#K = ((3.67 * 1) + (1.65 * 3.74))/50<br />
#K = 0.19 which doesn&#8217;t make sense.  If you change SCQ to say 5 then the number of kanban you need is 1.968.</p>
<p>You certain your replenishment time is 24 hours?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9892</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Tue, 06 Jul 2010 21:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9892</guid>
		<description>HELP!

This is great information ... however I seem to be getting stuck on symantics.  I tend to use the formula with standard deviation.  If I have an average daily usage of 3.67 parts, a standard deviation of 3.74, a 24 hour replenishment time, and I want to use a z factor of 1.645 ... I seem to be getting a kanban of 9.8.  The bin can hold 50 parts, but I do not think it makes since to put 50 parts into the bin and my supply can supply whatever quantity I ask for. So how can I tell what my reorder point and quantity should be?</description>
		<content:encoded><![CDATA[<p>HELP!</p>
<p>This is great information &#8230; however I seem to be getting stuck on symantics.  I tend to use the formula with standard deviation.  If I have an average daily usage of 3.67 parts, a standard deviation of 3.74, a 24 hour replenishment time, and I want to use a z factor of 1.645 &#8230; I seem to be getting a kanban of 9.8.  The bin can hold 50 parts, but I do not think it makes since to put 50 parts into the bin and my supply can supply whatever quantity I ask for. So how can I tell what my reorder point and quantity should be?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: business management</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9877</link>
		<dc:creator>business management</dc:creator>
		<pubDate>Sun, 30 May 2010 13:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9877</guid>
		<description>thanks for the post. its very helpful.</description>
		<content:encoded><![CDATA[<p>thanks for the post. its very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence Loucka</title>
		<link>http://www.resourcesystemsconsulting.com/blog/archives/58#comment-9840</link>
		<dc:creator>Lawrence Loucka</dc:creator>
		<pubDate>Thu, 08 Apr 2010 13:50:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.resourcesystemsconsulting.com/blog/?p=58#comment-9840</guid>
		<description>Jessie,
For kanban think of a container with 100 parts.  When the is empty it goes back to the suppler and is a signal to make or buy 100 more parts.  Then the container is filled up and returned to the customer.  This container makes a loop, going around and around.  How long does it take for this one container to make the whole round trip.  This we call Replenishment Time.  Replenishment Time is not Lead Time.

Equation I use:

Number of Kanban = ((Average Daily Demand * Replenishment Time) + Safety Stock)/Standard Container Quantity

So #Kanban = ((2000 * Replenishment Time) + 100)/100</description>
		<content:encoded><![CDATA[<p>Jessie,<br />
For kanban think of a container with 100 parts.  When the is empty it goes back to the suppler and is a signal to make or buy 100 more parts.  Then the container is filled up and returned to the customer.  This container makes a loop, going around and around.  How long does it take for this one container to make the whole round trip.  This we call Replenishment Time.  Replenishment Time is not Lead Time.</p>
<p>Equation I use:</p>
<p>Number of Kanban = ((Average Daily Demand * Replenishment Time) + Safety Stock)/Standard Container Quantity</p>
<p>So #Kanban = ((2000 * Replenishment Time) + 100)/100</p>
]]></content:encoded>
	</item>
</channel>
</rss>
