<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://scrmblog.dumke.me/taxonomy/term/567/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>N. Viswanadham</title>
    <link>http://scrmblog.dumke.me/taxonomy/term/567/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="http://scrmblog.dumke.me/taxonomy/term/567/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Conceptual and Analytical Framework for SCRM</title>
    <link>http://scrmblog.dumke.me/review/conceptual-and-analytical-framework-for-scrm</link>
    <description>&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;A supply chain risk management framework should help to define the cornerstones of risk related supply chain problems and give hints on how to take actions to mitigate impending disruptions.&lt;/p&gt;

	&lt;p&gt;Today&amp;#8217;s full paper has been published in 2004 and in it the authors (Gaonkar and Viswanadham) deal with this problem.&lt;/p&gt;

	&lt;h5&gt;Core definitions&lt;/h5&gt;

	&lt;p&gt;At the core of their framework the authors define the risk/supply chain related terms.&lt;/p&gt;

	&lt;p&gt;First, risks can be seen from an organizational-, supply chain- or industry-level. &lt;/p&gt;

	&lt;p&gt;&lt;blockquote&gt;&lt;br /&gt;
Network- related risk sources represent the second category of risk sources, which are the primary focus of this paper. These risks are of two broad kinds:
	&lt;ol&gt;
		&lt;li&gt;Firms are vulnerable not only to attacks on their own assets, but also to attacks on their suppliers, customers, transportation providers, communication lines, and other elements in their eco-system.&lt;/li&gt;
		&lt;li&gt;Firms are also vulnerable to irregular behavior of their network partners such as a supplier sharing sensitive product design with a competitor manufacturer.&lt;br /&gt;
&lt;/blockquote&gt;&lt;/li&gt;
	&lt;/ol&gt;&lt;/p&gt;

	&lt;p&gt;Second, there are different classes of risk problems:
	&lt;ul&gt;
		&lt;li&gt;Deviations: &amp;#8220;A deviation is said to have occurred when one or more parameters, such as cost, demand, lead-time, etc., within the supply chain system stray from their expected or mean value, without any changes to the underlying supply chain structure.&amp;#8221;&lt;/li&gt;
		&lt;li&gt;Disruptions: &amp;#8220;A disruption occurs when the structure of the supply chain system is radically transformed, through the non-availability of certain production, warehousing and distribution facilities or transportation options due to unexpected events caused by human or natural factors.&amp;#8221;&lt;/li&gt;
		&lt;li&gt;Disasters: &amp;#8220;A disaster is defined as a temporary irrecoverable shut-down of the supply chain network due to unforeseen catastrophic system-wide disruptions.&amp;#8221;&lt;/li&gt;
	&lt;/ul&gt;&lt;/p&gt;

	&lt;p&gt;This classification also contains an implicit rating of the risk impact and while it is possible to create a robust supply chain which can withstand deviations and disruptions &amp;#8220;it is impossible to design a supply chain network that is robust enough to react to disasters. This arises from the constraints of any system design, which is limited by its operational specification.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;The authors require the supply chains to be robust at three levels: the strategic, tactical and operational level. So each of these levels has to be prepared for deviations, disruptions and disasters.&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;For example, at the operational level, companies require decision support systems that can act on information from various partners regarding various deviations and disruptions to reschedule activities so that the business processes are synchronized and deliveries are undertaken within customer delivery windows and cost limitations. At the tactical level, plans need to have redundancies in terms of human and machine resources and also logistics and supply organizations. At the strategic level, more reliable partners with intrinsic capabilities in deviation and disruption handling, and the skills and ability to adapt to changing market conditions will be preferred and selected.&lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;p&gt;There are two distinct ways to supply chain risk mitigation:
	&lt;ul&gt;
		&lt;li&gt;&amp;#8220;The first approach involves the time tested “just in case” way of maintaining inventories all along the chain, employing dual or multi-sourcing and manufacturing at multiple sites. This is a highly inefficient option.&amp;#8221;&lt;/li&gt;
		&lt;li&gt;&amp;#8220;A better option would be to first design a sourcing strategy taking into account the disruption costs for the most relevant failure modes and then putting in place contingency plans for each disruption that include both description of the procedures to follow and a definition of roles and responsibilities.&amp;#8221;&lt;/li&gt;
	&lt;/ul&gt;&lt;/p&gt;

	&lt;p&gt;The authors distinguish three analytical approaches to risk management:
	&lt;ul&gt;
		&lt;li&gt;Mathematical planning models,&lt;/li&gt;
		&lt;li&gt;Adaptive control, and&lt;/li&gt;
		&lt;li&gt;Rule-based control.&lt;br /&gt;
And they continue to explain their preventive and interceptive approaches to risk management. Some of which can be found summarized in &lt;a href=&quot;http://scrmblog.dumke.me/review/exception-handling-for-robust-supply-chain-design&quot; title=&quot;SCRM Blog: Exception Handling for Robust Supply Chain Design&quot;&gt;this article in the blog&lt;/a&gt;.&lt;/li&gt;
	&lt;/ul&gt;&lt;/p&gt;

	&lt;h5&gt;Results&lt;/h5&gt;

	&lt;p&gt;Based on their framework of supply chain risks the authors develop two strategic level (mathematical) models which include risk considerations.&lt;br /&gt;
&lt;blockquote&gt;
	&lt;ol&gt;
		&lt;li&gt;Strategic-level Deviation Management Model: Given the expected costs and variability (deviation) of costs for all suppliers, the first problem relates to the selection of an optimal group of suppliers such that the expected cost of operating the entire supply chain and the risk of variations in total supply chain costs is minimized.&lt;/li&gt;
		&lt;li&gt;Strategic-level Disruption Management Model: Given the expected probabilities for various supplier disruption scenarios and the supply shortfalls under each of these scenarios the objective for the manufacturer is to choose a set of suppliers that minimize the expected shortfall during the operation of the supply chain.&lt;br /&gt;
&lt;/blockquote&gt;&lt;/li&gt;
	&lt;/ol&gt;&lt;/p&gt;

	&lt;p&gt;With the models numerical example case studies are executed and the authors conclude:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;Robustness is build into our supply chain design by selecting a portfolio of suppliers that minimize the variability of supply chain performance in terms of cost and output. The models we develop are preventive in nature and employ mathematical programming tools.&lt;/p&gt;
	&lt;/blockquote&gt;

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

	&lt;p&gt;This article is a double publication, the models and their results have already been discussed &lt;a href=&quot;http://scrmblog.dumke.me/review/exception-handling-for-robust-supply-chain-design&quot; title=&quot;SCRM Blog: Exception Handling for Robust Supply Chain Design&quot;&gt;here&lt;/a&gt;. Even though this is questionable behavior from a scientific point I did include this article due to the good and aggregated summary of the terms and definitions used in the field of supply chain risk management. &lt;br /&gt;
Using those as a minimum to analyze supply chains can already help a great deal in finding fitting mitigation strategies.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&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/RoboticsAndAutomation2004.Proceedings.Icra%2704.2004IeeeInternationalConferenceOn2005GaonkarAConceptualAndAnalyticalFrameworkForTheManagementOfRiskInSupplyChains.png?itok=23jrt7sB&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-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=Robotics+and+Automation&amp;amp;rft_id=info%3A%2F&amp;amp;rfr_id=info%3Asid%2Fresearchblogging.org&amp;amp;rft.atitle=A+Conceptual+and+Analytical+Framework+for+the+Management+of+Risk+in+Supply+Chains&amp;amp;rft.issn=&amp;amp;rft.date=2005&amp;amp;rft.volume=3&amp;amp;rft.issue=&amp;amp;rft.spage=2699&amp;amp;rft.epage=2704&amp;amp;rft.artnum=&amp;amp;rft.au=Gaonkar%2C+R.&amp;amp;rft.au=Viswanadham%2C+N.&amp;amp;rfe_dat=bpr3.included=1;bpr3.tags=Other%2CBusiness+Management%2C+Supply+Chain+Management&quot;&gt;Gaonkar, R., &amp;amp; Viswanadham, N. (2005). A Conceptual and Analytical Framework for the Management of Risk in Supply Chains &lt;span style=&quot;font-style: italic;&quot;&gt;Robotics and Automation, 3&lt;/span&gt;, 2699-2704&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/567/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 Conceptual and Analytical Framework for SCRM 1/5&lt;/option&gt;&lt;option value=&quot;40&quot;&gt;Give Conceptual and Analytical Framework for SCRM 2/5&lt;/option&gt;&lt;option value=&quot;60&quot;&gt;Give Conceptual and Analytical Framework for SCRM 3/5&lt;/option&gt;&lt;option value=&quot;80&quot; selected=&quot;selected&quot;&gt;Give Conceptual and Analytical Framework for SCRM 4/5&lt;/option&gt;&lt;option value=&quot;100&quot;&gt;Give Conceptual and Analytical Framework for SCRM 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-aV4t5HeF0Oa1kdJvSLvgdcpLGwWxz9AN7MLlpRwv-kM&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/framework&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;framework&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/supply-chain&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;supply chain&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;/tags/disruption&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;disruption&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;field field-name-field-count-pixel field-type-text-long field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 12 Mar 2012 18:18:16 +0000</pubDate>
 <dc:creator>Daniel Dumke</dc:creator>
 <guid isPermaLink="false">1782 at http://scrmblog.dumke.me</guid>
  </item>
  <item>
    <title>Exception Handling for Robust Supply Chain Design</title>
    <link>http://scrmblog.dumke.me/review/exception-handling-for-robust-supply-chain-design</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/ProceeingsOfThe2003IeeeInternationalConferenceOnRobotics%26Automation2003GaonkarRobustSupplyChainDesignAStrategicApproachForExceptionHandling.png?itok=FhhpHyjk&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;This article considers the design of robust supply chains from the viewpoint of exception handling. Disruptions of the supply chain happen all the time. Smaller disruptions like quality issues are part of the daily business; but a look at the recent ten years shows that large disruptions, happen more often as well (think of terrorist attacks or earthquakes). &amp;#8220;Thus, exception management is an important issue in global supply chain networks.&amp;#8221;&lt;/p&gt;

	&lt;h5&gt;Basics and definition&lt;/h5&gt;

	&lt;p&gt;If one accepts the fact, that exception cannot be eliminated completely there are two ways to treat them: preventive and interceptive. Figure 1 shows different exception management strategies. &lt;/p&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;a class=&quot;scrm_image_link&quot; title=&quot;Exception Management Strategies&quot; href=&quot;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandlingstrategies.png&quot; onclick=&quot;F1 = window.open(&#039;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandlingstrategies.png&#039;,&#039;Zoom&#039;,&#039;height=714,width=894,top=370.5,left=840.5,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;398&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandlingstrategiessmall.png&quot; title=&quot;Exception Management Strategies&quot; alt=&quot;Exception Management Strategies&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 1: Exception Management Strategies (Gaonkar and Viswanadham, 2003; click to zoom)&lt;/div&gt;&lt;/div&gt;

	&lt;p&gt;The authors define a supply chain exception as the opposite to the classical seven-Rs of logistics:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;We can use this description to define a supply chain failure or exception occurring whenever the supply chain deviates from any one of the [&amp;#8230;] required specifications &amp;#8211; either in terms of delivering the wrong product, in the wrong quantity, in the wrong condition, at the wrong place, at the wrong time, at the wrong cost and to the wrong customer. &lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;h5&gt;Exception management&lt;/h5&gt;

	&lt;p&gt;In this case exception management is addressed &amp;#8220;at the strategic level through the preventive selection of supply chain partners that mitigate risk in the network.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;In the first step the consequences of a given exception (here: supplier non-performance) are analyzed. The authors use a Cause-Consequence-Diagram for this end (figure 2).&lt;/p&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;a class=&quot;scrm_image_link&quot; title=&quot;Cause and Consequence Diagram for one Example (Supplier Non-Performance)&quot; href=&quot;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandling.png&quot; onclick=&quot;F1 = window.open(&#039;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandling.png&#039;,&#039;Zoom&#039;,&#039;height=771,width=945,top=342,left=815,toolbar=no,menubar=no,location=no,resize=1,resizable=1,scrollbars=yes&#039;); return false;&quot;&gt;&lt;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;406&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/gaonkarexceptionhandlingsmall.png&quot; title=&quot;Cause and Consequence Diagram for one Example (Supplier Non-Performance)&quot; alt=&quot;Cause Consequence Diagram for Supplier non-performance and the resulting outcome&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 2: Cause and Consequence Diagram for one Example (Supplier Non-Performance) (Gaonkar and Viswanadham, 2003; click to zoom)&lt;/div&gt;&lt;/div&gt;

	&lt;p&gt;Then, &amp;#8220;given the probability of occurrence of the initiating event, which is supplier non-performance, and the probabilities for the various intermedialy events, we can calculate the probability of occurrences for each of the end states or outcomes. Furthermore, each of these end states may result in different levels of supply shortfalls and financial cost. Hence, given the probability of each end state and the supply shortfall or financial cost for each end state, we can calculate the expected shortfall or financial risk for the non-performance of a given supplier.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;If repeated for each supplier, the supplier with the least expected impact can be identified.&lt;/p&gt;

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

	&lt;p&gt;To implement their approach the authors develop a small linear mixed-integer model.&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;The model was formulated in Microsoft Excel and solved using the Solver add-in. The model was solved for a problem with a single manufacturer (located in the US), dealing with 5 suppliers. The probabilities of supplier disruption for all the suppliers (individually and in various combination) were considered as given [the first part is shown in figure 3]. The relation cost was taken as $5000 and the quantity required by the manufacturer was 520 units.&lt;/p&gt;
	&lt;/blockquote&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;324&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/gaonkarmodel.png&quot; title=&quot;Scenario / Probability Table&quot; alt=&quot;Probabilities of various supply situations.&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 3: Scenario / Probability Table (Gaonkar and Viswanadham, 2003)&lt;/div&gt;&lt;/div&gt;

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

	&lt;p&gt;The presented approach makes it easy to include uncertainty into the supplier selection process. Considering the moderate efforts necessary for implementing the supplier assessment and implementing the model, I would like to read more about the effectiveness in a real business situation.&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=Proceeings+of+the+2003+IEEE+International+Conference+on+Robotics+%26+Automation&amp;amp;rft_id=info%3A%2F&amp;amp;rfr_id=info%3Asid%2Fresearchblogging.org&amp;amp;rft.atitle=Robust+Supply+Chain+Design%3A+a+Strategic+Approach+for+Exception+Handling&amp;amp;rft.issn=&amp;amp;rft.date=2003&amp;amp;rft.volume=&amp;amp;rft.issue=&amp;amp;rft.spage=1762&amp;amp;rft.epage=1767&amp;amp;rft.artnum=http%3A%2F%2Fieeexplore.ieee.org%2Fstamp%2Fstamp.jsp%3Ftp%3D%26arnumber%3D1241849&amp;amp;rft.au=Gaonkar%2C+R.&amp;amp;rft.au=Viswanadham%2C+N.&amp;amp;rfe_dat=bpr3.included=1;bpr3.tags=Other%2CBusiness+Management%2C+Supply+Chain+Management&quot;&gt;Gaonkar, R., &amp;amp; Viswanadham, N. (2003). Robust Supply Chain Design: a Strategic Approach for Exception Handling &lt;span style=&quot;font-style: italic;&quot;&gt;Proceeings of the 2003 &lt;span class=&quot;caps&quot;&gt;IEEE&lt;/span&gt; International Conference on Robotics &amp;amp; Automation&lt;/span&gt;, 1762-1767&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/567/all/feed&quot; method=&quot;post&quot; id=&quot;fivestar-custom-widget--2&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--4&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 Exception Handling for Robust Supply Chain Design 1/5&lt;/option&gt;&lt;option value=&quot;40&quot;&gt;Give Exception Handling for Robust Supply Chain Design 2/5&lt;/option&gt;&lt;option value=&quot;60&quot;&gt;Give Exception Handling for Robust Supply Chain Design 3/5&lt;/option&gt;&lt;option value=&quot;80&quot;&gt;Give Exception Handling for Robust Supply Chain Design 4/5&lt;/option&gt;&lt;option value=&quot;100&quot;&gt;Give Exception Handling for Robust Supply Chain Design 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--2&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-v3wipzWu4Jv-jktUrQ4fUNp42XjNKbU5FAiG-gR7J40&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/design&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;design&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/exception&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;exception&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;/tags/robust&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;robust&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/supply-chain&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;supply chain&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&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>Wed, 07 Dec 2011 18:33:00 +0000</pubDate>
 <dc:creator>Daniel Dumke</dc:creator>
 <guid isPermaLink="false">1689 at http://scrmblog.dumke.me</guid>
  </item>
  </channel>
</rss>
