<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="http://scrmblog.dumke.me/taxonomy/term/557/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>Bimal Nepal</title>
    <link>http://scrmblog.dumke.me/taxonomy/term/557/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="http://scrmblog.dumke.me/taxonomy/term/557/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Matching Product Architecture with Supply Chain Design</title>
    <link>http://scrmblog.dumke.me/review/matching-product-architecture-with-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/EuropeanJournalOfOperationalResearch2011NepalMatchingProductArchitectureWithSupplyChainDesign.png?itok=2MBj2Mri&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 review is about a preprint article which already has been accepted for publication by the &amp;#8220;European Journal of Operational Research&amp;#8221;. But since there is only a limited space for articles in each issue of the journal, final publication of the article is delayed.&lt;br /&gt;
One could now argue in a general note that this behavior also signifies a delay of the progress of supply chain research over all, with all its negative long term effects. Furthermore, in the days of the internet journals should not limit themselves to an artificial (article) limit, but see only the sky or in this case the number of quality publications as their limit.&lt;br /&gt;
But in this case I was able to gain access to an early copy.&lt;/p&gt;

	&lt;h5&gt;Product design &amp;amp; supply chain management&lt;/h5&gt;

	&lt;p&gt;I already wrote several times (&lt;a href=&quot;http://scrmblog.dumke.me/archives/262-Combination-of-Product-and-Supply-Chain-Design.html&quot; title=&quot;SCRM Blog: Combination of Product and Supply Chain Design&quot;&gt;1&lt;/a&gt;, &lt;a href=&quot;http://scrmblog.dumke.me/archives/217-Strategic-Supply-Chain-Design-and-the-Product-Relationship-Matrix.html&quot; title=&quot;SCRM Blog: Strategic Supply Chain Design and the Product-Relationship Matrix&quot;&gt;2&lt;/a&gt;, &lt;a href=&quot;http://scrmblog.dumke.me/archives/193-Decision-Support-for-Supply-Chain%2C-Product-and-Process-Design.html&quot; title=&quot;SCRM Blog: Decision Support for Supply Chain, Product and Process Design&quot;&gt;3&lt;/a&gt;, &lt;a href=&quot;http://scrmblog.dumke.me/archives/38-Dealing-with-Product-Uncertainties-in-a-Supply-Chain.html&quot; title=&quot;SCRM Blog: Dealing with Product Uncertainties in a Supply Chain&quot;&gt;4&lt;/a&gt;) on how product architecture and supply chain design could be integrated, so this is not really a new topic. But it also touches a more integrative approach of supply chain management.&lt;/p&gt;

	&lt;p&gt;Building from the early models, where a supply chain could easily be defined by a handful of properties, supply chain models nowadays reach a new level of complexity. One of these extensions is the integration of supply chain activities into the product development process, which is supposed to yield (if we trust case studies like &lt;a href=&quot;http://www.emil.gatech.edu/news-events/hgarticle.php?nid=56529&quot; title=&quot;emil.gatech.edu: IKEA case study&quot;&gt;&lt;span class=&quot;caps&quot;&gt;IKEA&lt;/span&gt;&lt;/a&gt;) enormous benefits in every performance aspect of the supply chain and ultimately the company.In the study reviewed Nepal, Monplaisir and Famuyiwa first develop a conceptual and mathematical model to integrate the supply chain design decisions into the product development process. In a second step this model is then tested using two case studies.&lt;/p&gt;

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

	&lt;p&gt;The authors suggest an integrated three step process: 1) selection of product architecture, 2) evaluation of potential suppliers, and 3) optimal configuration of supply chain.&lt;/p&gt;

	&lt;p&gt;The &lt;strong&gt;first step&lt;/strong&gt; includes the development of a generic bill of materials (&lt;span class=&quot;caps&quot;&gt;GBOM&lt;/span&gt;) for every possible product architecture scenario. Figure 1 shows the &lt;span class=&quot;caps&quot;&gt;GBOM&lt;/span&gt; for an example Product X.&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;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;125&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalmodelproductarchitecture.png&quot; title=&quot;Generic Bill of Materials for an exemplary product&quot; alt=&quot;Generic bill of materials (GBOM) showing module relationship for Product X&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 1: Generic Bill of Materials for an exemplary product (Nepal et al., 2011)&lt;/div&gt;&lt;/div&gt;

	&lt;p&gt;This product design also leads to a similar generic supply chain structure which is shown in 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;img class=&quot;scrm_image_center&quot; width=&quot;500&quot; height=&quot;249&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalmodelsupplychain.png&quot; title=&quot;Corresponding Generic Supply Chain for Product X&quot; alt=&quot;Corresponding supply chain network diagram of product X.&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 2: Corresponding Generic Supply Chain for Product X (Nepal et al., 2011)&lt;/div&gt;&lt;/div&gt;

	&lt;p&gt;The &lt;strong&gt;second step&lt;/strong&gt; focusses on the identification and evaluation of available the supply chain participants. Necessary information, like production cost, lead-time and compatibility index has to be collected.&lt;br /&gt;
The compatibility index itself is developed by the authors as well and contains information on the compatibility of this potential supplier regarding the structural, managerial and financial dimension. Each of the dimensions is then weighted to generate the complete index. Since the compatibility of the future suppliers is hard to judge before the product is even designed, the authors employ &lt;a href=&quot;http://en.wikipedia.org/wiki/Fuzzy_logic&quot; title=&quot;Wikipedia: Fuzzy Logic&quot;&gt;fuzzy logic&lt;/a&gt;, allowing them to use ranges for each of the compatibility indices instead of fixed numbers.&lt;/p&gt;

	&lt;p&gt;The &lt;strong&gt;last step&lt;/strong&gt; aims to find the optimal supply chain configuration. This is done for each product architecture scenario by using a linear goal programming model, where total supply chain cost are minimized while maximizing the compatibility between the partners. &lt;/p&gt;

	&lt;h5&gt;Case studies&lt;/h5&gt;

	&lt;p&gt;There are two case studies, one on bulldozer assembly and manufacturing and the other on an automotive climate control system. I will only talk about the first case since I found it more interesting.&lt;/p&gt;

	&lt;p&gt;For the case the authors exercise the three steps mentioned above. First they design two different product architectures (integral and modular architectures; figure 3) and the corresponding generic supply chain networks (figure 4). &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;a class=&quot;scrm_image_link&quot; title=&quot;Case Study: Generic Bill of Materials for Bulldozer Manufacturing&quot; href=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalcaseproductarchitecture.png&quot; onclick=&quot;F1 = window.open(&#039;http://scrmblog.dumke.me/sites/default/files/images/nepalcaseproductarchitecture.png&#039;,&#039;Zoom&#039;,&#039;height=321,width=876,top=297,left=289.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;178&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalcaseproductarchitecturesmall.png&quot; title=&quot;Case Study: Generic Bill of Materials for Bulldozer Manufacturing&quot; alt=&quot;Modular structures of Bulldozer&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 3: Case Study: Generic Bill of Materials for Bulldozer Manufacturing (Nepal et al., 2011; click to enlarge)&lt;/div&gt;&lt;/div&gt;&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;Case Study: Generic Supply Chain Network for Bulldozer Manufacturing&quot; href=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalcasesupplychain.png&quot; onclick=&quot;F1 = window.open(&#039;http://scrmblog.dumke.me/sites/default/files/images/nepalcasesupplychain.png&#039;,&#039;Zoom&#039;,&#039;height=507,width=1047,top=204,left=204,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;238&quot; src=&quot;http://scrmblog.dumke.me/sites/default/files/images/nepalcasesupplychainsmall.png&quot; title=&quot;Case Study: Generic Supply Chain Network for Bulldozer Manufacturing&quot; alt=&quot;Supply chain network for bulldozer (adapted from Graves and Willems, 2003)&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;scrm_imageComment_txt&quot;&gt;Figure 4: Case Study: Generic Supply Chain Network for Bulldozer Manufacturing (Nepal et al., 2011; click to enlarge)&lt;/div&gt;&lt;/div&gt;

	&lt;p&gt;Lastly, the authors collect the necessary information of the potential suppliers regarding cost, lead-time and ranges for the compatibility index for two different process options:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;Two alternatives are considered for each node. If the node is a procurement stage, the first alternative represents the standard supply option (that is, the existing procurement arrangement). The second option represents a consignment option where the supplier is responsible for providing immediate delivery to the bulldozer line. Similarly, for the assembly node, the first option represents the standard manufacturing method while the second option represents an expedited alternative that corresponds to a supplier who has invested in process improvement efforts in order to decrease its supply lead-time.&lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;p&gt;After solving the model in the next step, the authors conclude:&lt;/p&gt;

	&lt;blockquote&gt;
		&lt;p&gt;In the majority of the bulldozer supply chain stages for a modular architectural design, option two has been selected. While it is more expensive than option one, option two has a lower production lead-time and higher compatibility ratings for all stages because its modularity increases the degree of dependency, based on relative costs of inputs, between supply chain nodes.&lt;/p&gt;
	&lt;/blockquote&gt;

	&lt;p&gt;Compared with base results, where only supply chain costs are considered, this model delivers a solution which performs (slightly) worse in cost (+0,36%), but on the other hand has the potential to deliver a much more balanced and robust solution considering also compatibility issues.&lt;/p&gt;

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

	&lt;p&gt;I found the paper to be a great read and I cannot add anything else to the issues the authors already detected and mentioned in their own conclusion:
	&lt;ol&gt;
		&lt;li&gt;Risk factors are missing in the model (e.g. random service times)&lt;/li&gt;
		&lt;li&gt;Additional factors like sustainability and flexibility should be considered&lt;/li&gt;
		&lt;li&gt;It is very obvious that this is again a supply oriented model, so it would be great to see how distribution network decisions behave when including product design decisions (since the customers might also change depending on the product design decisions)&lt;/li&gt;
	&lt;/ol&gt;&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=European+Journal+of+Operational+Research&amp;amp;rft_id=info%3A%2F10.1016%2Fj.ejor.2011.07.041&amp;amp;rfr_id=info%3Asid%2Fresearchblogging.org&amp;amp;rft.atitle=Matching+Product+Architecture+with+Supply+Chain+Design&amp;amp;rft.issn=&amp;amp;rft.date=2011&amp;amp;rft.volume=&amp;amp;rft.issue=&amp;amp;rft.spage=&amp;amp;rft.epage=&amp;amp;rft.artnum=&amp;amp;rft.au=Nepal%2C+B.&amp;amp;rft.au=Monplaisir%2C+L.&amp;amp;rft.au=Famuyiwa%2C+O.&amp;amp;rfe_dat=bpr3.included=1;bpr3.tags=Other%2CBusiness+Management%2C+Supply+Chain+Management&quot;&gt;Nepal, B., Monplaisir, L., &amp;amp; Famuyiwa, O. (2011). Matching Product Architecture with Supply Chain Design &lt;span style=&quot;font-style: italic;&quot;&gt;European Journal of Operational Research&lt;/span&gt; : &lt;a rev=&quot;review&quot; href=&quot;10.1016/j.ejor.2011.07.041&quot;&gt;10.1016/j.ejor.2011.07.041&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/557/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 Matching Product Architecture with Supply Chain Design 1/5&lt;/option&gt;&lt;option value=&quot;40&quot;&gt;Give Matching Product Architecture with Supply Chain Design 2/5&lt;/option&gt;&lt;option value=&quot;60&quot;&gt;Give Matching Product Architecture with Supply Chain Design 3/5&lt;/option&gt;&lt;option value=&quot;80&quot;&gt;Give Matching Product Architecture with Supply Chain Design 4/5&lt;/option&gt;&lt;option value=&quot;100&quot; selected=&quot;selected&quot;&gt;Give Matching Product Architecture with 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&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-1ZdlDzrv9hF-KNjbT7yRyJc8Q4NkjuxDcp-wuKFKmY4&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/model&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;model&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;a href=&quot;/tags/product-design&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;product design&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item odd&quot;&gt;&lt;a href=&quot;/tags/strategy&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;strategy&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;field-item even&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 odd&quot;&gt;&lt;a href=&quot;/tags/empirical-research&quot; typeof=&quot;skos:Concept&quot; property=&quot;rdfs:label skos:prefLabel&quot; datatype=&quot;&quot;&gt;empirical research&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 19 Oct 2011 15:31:00 +0000</pubDate>
 <dc:creator>Daniel Dumke</dc:creator>
 <guid isPermaLink="false">1675 at http://scrmblog.dumke.me</guid>
  </item>
  </channel>
</rss>
