<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://scrmblog.dumke.me/taxonomy/term/510/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:og="http://ogp.me/ns#" xmlns:article="http://ogp.me/ns/article#" xmlns:book="http://ogp.me/ns/book#" xmlns:profile="http://ogp.me/ns/profile#" xmlns:video="http://ogp.me/ns/video#" xmlns:product="http://ogp.me/ns/product#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>recurrent</title>
    <link>http://scrmblog.dumke.me/taxonomy/term/510/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="http://scrmblog.dumke.me/taxonomy/term/510/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Recurrent versus Disruption Risk</title>
    <link>http://scrmblog.dumke.me/review/recurrent-versus-disruption-risk</link>
    <description>&lt;div class=&quot;field field-name-field-thumbnail field-type-image field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;img typeof=&quot;foaf:Image&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/styles/thumbnail/public/pubthumb/NavalResearchLogistics2007ChopraTheImportanceOfDecouplingRecurrentAndDisruptionRisksInASupplyChain.png?itok=u6FfjXml&quot; width=&quot;80&quot; height=&quot;80&quot; alt=&quot;&quot; /&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;	&lt;p&gt;The distinction between disruptions and recurrent / continuous risks is commonly used by researchers and practitioners in supply chain management. But how should the differences be reflected in the supply chain planning process? Is it necessary to differentiate between the risk types here as well?&lt;/p&gt;

	&lt;p&gt;In 2007 Sunil Chopra et al. analyzed this question in depth.&lt;/p&gt;

	&lt;h5&gt;Disruption vs. continuous risks&lt;/h5&gt;

	&lt;p&gt;For simplicity sake the authors define a disruption as a supplier which does not deliver any product at all. Figure 1 shows an example delivery listing for 20 periods. In periods 4, 7 and 13 nothing has been delivered and so a disruption has happened.&lt;/p&gt;

	&lt;p&gt;As you can see the overall mean (including the disrupted periods) is 86 with a standard deviation of 39. But the third column highlights an important point: If you leave out the disrupted periods, the mean rises and the standard deviation drops to a third. As a result it should make a difference if a decision maker used one or the other mean / standard deviation to make his decision. &lt;br /&gt;
&lt;div class=&quot;scrm_image_center&quot; style=&quot;width: 500px&quot;&gt;&lt;div class=&quot;scrm_imageComment_img&quot;&gt;&lt;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;514&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/chopradisruptiontable.png&quot; title=&quot;Exemplary Table containing Recurrent and Disruption Risks&quot; alt=&quot;Example delivery log&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 1: Exemplary Table containing Recurrent and Disruption Risks (Chopra et al., 2007)&lt;/div&gt;&lt;/div&gt;&lt;/p&gt;

	&lt;h5&gt;Model&lt;/h5&gt;

	&lt;p&gt;To test the effects of a differentiated versus a bundled view the authors develop a model. The focal company has two suppliers, one reliable and one unreliable (at risk of a disruption). The authors then analyze two cases: first, only recurrent risk and second, recurrent and disruption risks. Each with either a decision maker who views the risks bundled together or separately. &lt;br /&gt;
Figure 2 has a good graphic to show the implications of the different approaches with disruptions present. In a bundled view the excess order volume (y-axis, to prevent stock-outs) is increasing when the probability of the disruption increases. On the other hand, when the risks are decoupled the decision maker only focusses on the recurrent risk and the excess order even decreases with the probability of a disruption. The disruption risk is then mitigated by contingently using the more reliable supplier.&lt;br /&gt;
&lt;div class=&quot;scrm_image_center&quot; style=&quot;width: 500px&quot;&gt;&lt;div class=&quot;scrm_imageComment_img&quot;&gt;&lt;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;340&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/chopragraphdifference.png&quot; title=&quot;Comparison of Excess Orders for Decoupled and Non-Decoupled Risks&quot; alt=&quot;Optimal excess order from first supplier on bundling and decoupling.&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 2: Comparison of Excess Orders for Decoupled and Non-Decoupled Risks (Chopra et al., 2007)&lt;/div&gt;&lt;/div&gt;&lt;/p&gt;

	&lt;h5&gt;Implications&lt;/h5&gt;

	&lt;p&gt;The authors conclude that:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;Bundling of disruption and recurrent supply uncertainty results in an over (under) utilization of the low cost (reliable) supplier. The extent of over (under) utilization increases as the probability of disruption grows.&lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;p&gt;Furthermore:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;Growth in supply risk from increased disruption probability is best mitigated by increased use of the reliable (though more expensive) supplier and decreased use of the cheaper but less reliable supplier. Growth in supply risk from increased recurrent uncertainty, however, is better served by increased use of the cheaper, though less reliable, supplier.&lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;h5&gt;Conclusion&lt;/h5&gt;

	&lt;p&gt;I liked the article a lot, since it focusses on one simple question: Is it bad to combine different types of risk. The conclusion: There will always be different risk sources or types which, as this article shows, have to be mitigated differently as well. &lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-research-blogging field-type-text-long field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Reference:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;	&lt;p&gt;&lt;span class=&quot;Z3988&quot; title=&quot;ctx_ver=Z39.88-2004&amp;amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;amp;rft.jtitle=Naval+Research+Logistics&amp;amp;rft_id=info%3Adoi%2F10.1002%2Fnav.20228&amp;amp;rfr_id=info%3Asid%2Fresearchblogging.org&amp;amp;rft.atitle=The+importance+of+decoupling+recurrent+and+disruption+risks+in+a+supply+chain&amp;amp;rft.issn=0894069X&amp;amp;rft.date=2007&amp;amp;rft.volume=54&amp;amp;rft.issue=5&amp;amp;rft.spage=544&amp;amp;rft.epage=555&amp;amp;rft.artnum=http%3A%2F%2Fdoi.wiley.com%2F10.1002%2Fnav.20228&amp;amp;rft.au=Chopra%2C+S.&amp;amp;rft.au=Reinhardt%2C+G.&amp;amp;rft.au=Mohan%2C+U.&amp;amp;rfe_dat=bpr3.included=1;bpr3.tags=Other%2CBusiness+Management%2C+Supply+Chain+Management&quot;&gt;Chopra, S., Reinhardt, G., &amp;amp; Mohan, U. (2007). The importance of decoupling recurrent and disruption risks in a supply chain &lt;span style=&quot;font-style: italic;&quot;&gt;Naval Research Logistics, 54&lt;/span&gt; (5), 544-555 &lt;span class=&quot;caps&quot;&gt;DOI&lt;/span&gt;: &lt;a rev=&quot;review&quot; href=&quot;http://dx.doi.org/10.1002/nav.20228&quot;&gt;10.1002/nav.20228&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-user-rating field-type-fivestar field-label-above&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Rate This:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;form class=&quot;fivestar-widget&quot; action=&quot;/taxonomy/term/510/all/feed&quot; method=&quot;post&quot; id=&quot;fivestar-custom-widget&quot; accept-charset=&quot;UTF-8&quot;&gt;&lt;div&gt;&lt;div  class=&quot;clearfix fivestar-average-stars fivestar-form-item fivestar-outline&quot;&gt;&lt;div class=&quot;form-item form-type-fivestar form-item-vote&quot;&gt;
 &lt;div class=&quot;form-item form-type-select form-item-vote&quot;&gt;
 &lt;select id=&quot;edit-vote--2&quot; name=&quot;vote&quot; class=&quot;form-select&quot;&gt;&lt;option value=&quot;-&quot;&gt;Select rating&lt;/option&gt;&lt;option value=&quot;20&quot;&gt;Give Recurrent versus Disruption Risk 1/5&lt;/option&gt;&lt;option value=&quot;40&quot;&gt;Give Recurrent versus Disruption Risk 2/5&lt;/option&gt;&lt;option value=&quot;60&quot;&gt;Give Recurrent versus Disruption Risk 3/5&lt;/option&gt;&lt;option value=&quot;80&quot;&gt;Give Recurrent versus Disruption Risk 4/5&lt;/option&gt;&lt;option value=&quot;100&quot;&gt;Give Recurrent versus Disruption Risk 5/5&lt;/option&gt;&lt;/select&gt;
&lt;/div&gt;

&lt;div class=&quot;description&quot;&gt;Fivestar rating field for readers to rate the content.&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;input class=&quot;fivestar-submit form-submit&quot; type=&quot;submit&quot; id=&quot;edit-fivestar-submit&quot; name=&quot;op&quot; value=&quot;Rate&quot; /&gt;&lt;input type=&quot;hidden&quot; name=&quot;form_build_id&quot; value=&quot;form-rIR0g2rwzKyiqn8eTW4zgIZ-ni_WNmm7CUTqIsPYlP4&quot; /&gt;
&lt;input type=&quot;hidden&quot; name=&quot;form_id&quot; value=&quot;fivestar_custom_widget&quot; /&gt;
&lt;/div&gt;&lt;/form&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-tags-review field-type-taxonomy-term-reference field-label-inline clearfix&quot;&gt;&lt;div class=&quot;field-label&quot;&gt;Tags:&amp;nbsp;&lt;/div&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;/tags/mitigation&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;mitigation&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/recurrent&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;recurrent&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;/tags/risk&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;risk&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/disruptions&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;disruptions&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 18 Jul 2011 13:25:00 +0000</pubDate>
 <dc:creator>Daniel Dumke</dc:creator>
 <guid isPermaLink="false">1647 at http://scrmblog.dumke.me</guid>
  </item>
  </channel>
</rss>
