<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Supply Chain Risk &#124; Business Continuity &#124; Transport Vulnerability &#187; knowledge management</title> <atom:link href="http://www.husdal.com/tag/knowledge-management/feed/" rel="self" type="application/rss+xml" /><link>http://www.husdal.com</link> <description>Journal articles and papers, books and book chapters, research reports and whitepapers, blogs and websites</description> <lastBuildDate>Sun, 05 Feb 2012 20:15:21 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <item><title>A supply chain is never stronger than the weakest link</title><link>http://www.husdal.com/2009/07/17/a-supply-chain-is-never-stronger-than-the-weakest-link/</link> <comments>http://www.husdal.com/2009/07/17/a-supply-chain-is-never-stronger-than-the-weakest-link/#comments</comments> <pubDate>Fri, 17 Jul 2009 19:29:24 +0000</pubDate> <dc:creator>Jan Husdal</dc:creator> <category><![CDATA[ARTICLES AND PAPERS]]></category> <category><![CDATA[Dittmann Paul]]></category> <category><![CDATA[knowledge management]]></category> <category><![CDATA[Mentzer John T]]></category> <category><![CDATA[Slone Reuben E]]></category> <guid
isPermaLink="false">http://www.husdal.com/?p=6153</guid> <description><![CDATA[The article is geared towards company CEOs, advising them not to get too detached from supply management, but rather to actively engage in their company's supply chain management, particularly in businesses like manufacturing, retail and distribution.  [ ... ]]]></description> <content:encoded><![CDATA[<p
style="text-align: justify;"><img
class="size-full wp-image-6168 alignleft" style="margin-left: 5px; margin-right: 5px;" title="mentzer-dittmann-slone-weak-link-supply-chain" src="http://www.husdal.com/wp-content/uploads/2009/07/mentzer-dittmann-slone-weak-link-supply-chain1.gif" alt="mentzer-dittmann-slone-weak-link-supply-chain" width="79" height="100" />Are you the weakest link in your own supply chain? That&#8217;s the question asked in an article in the Harvard Business Review some time ago. The article is geared towards company CEOs, advising them not to get too detached from supply management, but rather to actively engage in their company&#8217;s supply chain management, particularly in businesses like manufacturing, retail and distribution. This article may not be that much related to supply chain risk, but it is not totally unrelated.</p><p><span
id="more-6153"></span></p><h3>Seven key areas</h3><p
style="text-align: justify;">The article divides the  supply chain domain into seven key areas where CEOs can exert a positive, or conversely, a negative influence:</p><p
style="text-align: justify;"><strong>Picking the right leaders</strong> &#8211; A CEO should never appoint  a person without the appropriate background for a senior position in supply chain management. Even if lateral job rotation is part of management training and the designated career path towards senior management positions, make sure that the supply chain management function is headed by someone who knows supply chain management.</p><blockquote><p
style="text-align: justify;">Only a CEO who is up to date on supply-chain practices and trends can properly evaluate a supply-chain executive’s performance.</p></blockquote><p
style="text-align: justify;"><strong>Initiating benchmarking and devising metrics</strong> &#8211;  A CEO ought to specify goals for improvement of inventory, transportation, and warehousing.  In order to do so he need to know benchmarking techniques and best practice metrics.</p><blockquote><p
style="text-align: justify;">Ensure that any tool purporting to evaluate customer service assesses the company’s performance from the customer’s viewpoint.</p></blockquote><p
style="text-align: justify;"><strong>Setting incentives for supportive behavior</strong> &#8211; A CEO ought to establish reward and incentive programmes to encourage employees to behave in ways that benefit the overall firm, not just their own functions.</p><blockquote><p
style="text-align: justify;">Purchasing, logistics, and merchandising managers work in cross-functional teams and are measured — and rewarded — according to supply-chain metrics that assess purchasing costs, logistics costs of getting the product to the store, and the selling price in the store.</p></blockquote><p
style="text-align: justify;"><strong>Keeping up with supply chain technologies and trends</strong> &#8211; A CEO should take the time to understand the sophisticated technologies that exist with supply chain management, among which RFID, machine readable codes  and bar codes.</p><blockquote><p
style="text-align: justify;">A CEO who understands new technologies can play the important devil’s advocate role by challenging the business case for technology adoption.</p></blockquote><p
style="text-align: justify;"><strong>Eliminating cross-functional crossed wires</strong> &#8211; A CEO should be aware of and avoid cross-functional sinkholes, where either part of the team has no understanding of the others&#8217; role and function in the overall supply chain.</p><blockquote><p
style="text-align: justify;">The CEO should thoroughly understand — so that he can help to harmonise — the interplay of cross-functional and supply chain priorities.</p></blockquote><p
style="text-align: justify;"><strong>Adding supply chain insight to business planning</strong> &#8211; A CEO ought to make sure that no key information is missing from the planning stage. Supply-chain considerations should be core components of business planning, including sales and marketing promotions and of contract negotiations with customers and partners, because unforeseen disjunctions can undermine the best strategic intentions.</p><blockquote><p
style="text-align: justify;">CEOs, if fully engaged, demand relevant business planning and negotiations anticipate and explicitly address important supply chain ramifications.</p></blockquote><p
style="text-align: justify;"><strong>Resisting the tyranny of short-term thinking</strong> &#8211; A CEO should guard, in particular, against allowing quarterly pressures to dictate unprofitable long-term trends. Why? Because it results in</p><blockquote><p
style="text-align: justify;">extreme costs and supply disruptions created by a quarterly cycle consisting of overcapacity and inventory build-up for two months, followed by rush production and delivery in the third month</p></blockquote><h3>Seven questions</h3><p>These are the seven question a CEO should ask:</p><ul><li>Is supply chain leadership a valued career path in your company?</li><li>Do you have a program of customer-focused metrics and best-practice benchmarking that drives cross-functional alignment?</li><li>Do employee and customer behavior reflect your supply chain strategies?</li><li>Do you understand important supply chain technology trends?</li><li>Do you play a constructive role in resolving cross-functional disjunctions?</li><li>Do you demand that supply chain expertise be factored into all or most business operations?</li><li>Do you ensure that short-term thinking doesn&#8217;t sabotage supply chain strategies?</li></ul><h3>A scorecard for self assessment</h3><p>The answer to the seven questions  can be assesed using a scorecard:</p><p><a
href="http://www.husdal.com/wp-content/uploads/2009/07/mentzer-dittmann-slone-weak-links-supply-chain.jpg"><img
class="alignnone size-thumbnail wp-image-6172" title="mentzer-dittmann-slone-weak-links-supply-chain" src="http://www.husdal.com/wp-content/uploads/2009/07/mentzer-dittmann-slone-weak-links-supply-chain-100x105.jpg" alt="mentzer-dittmann-slone-weak-links-supply-chain" width="100" height="105" /></a><br
/> <em>(Click image for larger version)</em></p><h3>Conclusion</h3><p
style="text-align: justify;">Although this article is more about suply chain management than supply chain risk, no supply chain is stronger than its weakest link, and weak links are a risk that can and should be avoided. This article is a step towards eliminating these weak links, at least the internal links.</p><h3>Links</h3><ul><li>Harvard Business  Review: <a
href="http://hbr.harvardbusiness.org/2007/09/are-you-the-weakest-link-in-your-companys-supply-chain/ar/1"> Are you the weakest link in your company&#8217;s supply chain?</a> (Login required)</li><li>cio.co.nz: <a
href="http://cio.co.nz/cio.nsf/specials/D01361A8ADFD239ECC257373007BEF11"> Are you  the weakest link in your company&#8217;s supply chain?</a> (Full article, but no graphics)</li></ul><h3>Author links</h3><ul><li>officemax.com: <a
href="http://officemax.mediaroom.com/index.php?s=20&amp;item=43">Reuben E Slone</a></li><li>utk.edu: <a
href="http://mlt.bus.utk.edu/meet_the_dept/bio/mentzer.html">John T Mentzer</a></li><li>dcvelocity.com: <a
href="http://www.dcvelocity.com/articles/?article_id=1424">J Paul Dittmann</a></li></ul><h3>Related</h3><ul><li>husdal.com: <a
href="http://www.husdal.com/2009/03/03/supply-chains-and-barcodes/">Barcodes &#8211; essential to supply chain management?</a></li></ul> ]]></content:encoded> <wfw:commentRss>http://www.husdal.com/2009/07/17/a-supply-chain-is-never-stronger-than-the-weakest-link/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>How the wrong people can ruin a supply chain</title><link>http://www.husdal.com/2009/05/15/how-the-wrong-people-can-ruin-a-supply-chain/</link> <comments>http://www.husdal.com/2009/05/15/how-the-wrong-people-can-ruin-a-supply-chain/#comments</comments> <pubDate>Thu, 14 May 2009 22:01:05 +0000</pubDate> <dc:creator>Jan Husdal</dc:creator> <category><![CDATA[THIS and THAT]]></category> <category><![CDATA[knowledge management]]></category> <category><![CDATA[supply chain risk]]></category> <guid
isPermaLink="false">http://husdal.com/?p=2996</guid> <description><![CDATA[People are what makes organizations work, or in some cases, not work. What happens if you don't have the right people? Well, you may have disaster waiting to happen from within. [ ... ]]]></description> <content:encoded><![CDATA[<p
style="text-align: justify;"><a
href="http://www.husdal.com/wp-content/uploads/2009/05/knowledge-management-supply-chain.jpg"><img
class="size-full wp-image-13323 alignleft" style="margin-left: 5px; margin-right: 5px; border: 1px solid black;" title="knowledge-management-supply-chain" src="http://www.husdal.com/wp-content/uploads/2009/05/knowledge-management-supply-chain.jpg" alt="" width="100" height="100" /></a>People are what makes organizations work, or in some cases, not work. Just as the &#8220;ordinary&#8221; supply chain is all about getting the right product to the right place at the right time and at the right price, the talent supply chain is all about getting the right people in the right jobs with the right skills at the right time and right price. What happens if you don&#8217;t have the right people? Well, you may have disaster waiting to happen from within.</p><p><span
id="more-2996"></span></p><h3 style="text-align: justify;">The biggest risk is inside</h3><p
style="text-align: justify;">When designing continuity plans, most companies think of all those things that are out of their control…fire, flood, labour unrest, storm damage, flu pandemics and the like. However, the risk that is most often overlooked is lurking not externally, but internally. Gen Ford from Ithaca puts it this way in his post on <a
href="http://journeylog.wordpress.com/2009/05/07/disaster-business-continuity-issues-are-most-often-caused-from-within%E2%80%A6/">DISASTER! Business Continuity Issues are Most Often Caused from Within…</a>:</p><blockquote><p
style="text-align: justify;">Risks &#8230; generally result from the natural way in which  organisations grow.  Ad hoc development of structure, process, new product and service creation often leads to gaps in competency, communication and function.</p></blockquote><p
style="text-align: justify;">How can you make sure your organization is fit to the task, even in the face of disaster? You must hire according to plan.</p><h3 style="text-align: justify;">The Talent Supply Chain</h3><p
style="text-align: justify;">In his post <a
href="http://www.supplychainnetwork.com/?p=479">People and Talent Supply Chain Management</a>, Jeff Ashcroft from SupplyChainNetwork says:</p><blockquote><p
style="text-align: justify;">Just as in supply chain management you begin with an inventory of your current human resources within the firm and the skills and attributes of those people. It’s then time to do some future planning relative to what your needs will be by location in three to five years. This will become your forecast for the talent supply chain in your firm but only represents the beginning of the full application of supply chain management principles to ensure the future health and stability of your workforce.</p></blockquote><p
style="text-align: justify;"><p
style="text-align: justify;">Nonetheless, even if you do apply the talent supply chain, one issue still remains, the loss of key personnel or key knowledge.</p><h3>Knowledge management</h3><p
style="text-align: justify;">Knowledge management is particularly important in today&#8217;s globalized supply chain, where teams work spread across the globe, perhaps only on a temporary or project basis, ready to move on when one project is completed. What happens then? You need to acquire the manpower and skills all over again. The figure below is one of the best illustrations I&#8217;ve seen on this subject: <em>This is a figure I found somewhere on the Internet at some point in time, but I forgot where and I am unable to find it again, or I would point you to it.</em></p><p
style="text-align: center;"><img
class="aligncenter size-full wp-image-3002" style="border: 1px solid black;" title="knowledge-management" src="http://www.husdal.com/wp-content/uploads/2009/05/knowledge-management.jpg" alt="knowledge-management" width="405" height="289" /></p><p
style="text-align: justify;">Having the wrong (=incompetent) people can certainly ruin your supply chain. Having the right people can be disastrous, too, if you have no contingency plan on how to replace them.</p><h3>Links</h3><ul><li>SupplyChainNetwork: <a
href="http://www.supplychainnetwork.com/?p=479">People and Talent Supply Chain Management</a></li><li>Finding Better Ways: <a
href="http://journeylog.wordpress.com/2009/05/07/disaster-business-continuity-issues-are-most-often-caused-from-within%E2%80%A6/">DISASTER! Business Continuity Issues are Most Often Caused from Within…</a></li></ul><h3>Related</h3><ul><li>husdal.com: <a
href="http://www.husdal.com/2009/06/25/trust-control-and-risk-in-strategic-alliances/">Trust, Control and Risk in Strategic Alliances</a></li></ul> ]]></content:encoded> <wfw:commentRss>http://www.husdal.com/2009/05/15/how-the-wrong-people-can-ruin-a-supply-chain/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> <item><title>Risk in Virtual Enterprise Networks</title><link>http://www.husdal.com/2009/03/31/managing-risk-in-virtual-enterprise-networks/</link> <comments>http://www.husdal.com/2009/03/31/managing-risk-in-virtual-enterprise-networks/#comments</comments> <pubDate>Mon, 30 Mar 2009 22:54:48 +0000</pubDate> <dc:creator>Jan Husdal</dc:creator> <category><![CDATA[BOOKS and BOOK CHAPTERS]]></category> <category><![CDATA[knowledge management]]></category> <category><![CDATA[peer review]]></category> <category><![CDATA[supply chain risk]]></category> <category><![CDATA[the networked enterprise]]></category> <category><![CDATA[Thompson Ken]]></category> <category><![CDATA[ven]]></category> <category><![CDATA[virtual enterprise]]></category> <category><![CDATA[virtual enterprise books]]></category> <category><![CDATA[virtual enterprise network]]></category> <guid
isPermaLink="false">http://husdal.com/?p=2242</guid> <description><![CDATA[I must admit that I knew very little, if anything, about Virtual Enterprise Networks when I started this adventure some months back, but I can now say that I am fascinated by the concept [ ... ]]]></description> <content:encoded><![CDATA[<p
style="text-align: justify;"><img
class="alignleft size-full wp-image-11176" style="margin-left: 5px; margin-right: 5px; border: 1px solid black;" title="igi-global" src="http://www.husdal.com/wp-content/uploads/2009/03/igi-global.jpg" alt="" width="100" height="100" />Done&#8230;I finally made it! Today I submitted my full chapter for the book on <strong><a
href="http://www.igi-global.com/Bookstore/Chapter.aspx?TitleId=42213">Managing Risk in Virtual Enterprise Networks: Implementing Supply Chain Principles</a></strong><img
style="border: none !important; margin: 0px !important;" src="http://www.assoc-amazon.com/e/ir?t=giswiz-20&amp;l=as2&amp;o=1&amp;a=1615206078" border="0" alt="" width="1" height="1" />. All I can do now is anxiously await the reviewers&#8217; verdict. Followers of this blog will already have noticed some of my posts on <a
href="http://husdal.com/tag/virtual-enterprise-network/">Virtual Enterprise Networks</a>, and wonder why I am suddenly deviating (albeit only slightly) from the main thrust of my blog, namely supply chain risk and transportation.</p><p><em> </em></p><p><span
id="more-2242"></span></p><h3 style="text-align: justify;">A new experience</h3><p
style="text-align: justify;">Writing a chapter for a book has been a whole new experience to me.  Daunting at first&#8230;how do your come up at least 9000 words on a topic you don&#8217;t really know much about? Following the references in <a
href="http://www.bioteams.com/2008/06/09/the_networked_enterprise.html">Ken Thompson&#8217;s </a><a
href="http://husdal.com/2009/03/17/jumpstart-your-ven-adventure/">The Networked Enterprise</a> as a starting point, it wasn&#8217;t too hard in the end, reaching some 12.700 words. Besides investigating a new field of study hitherto utterly unknown to me, writing a book chapter is considerably different from writing a journal article or a research report (<a
href="http://www.mfm.no/index.cfm?pageID=1811">which I do a lot of in my day job</a>), let alone reviewing books or literature or websites and thinking up some posts for this blog. My posts on  <a
href="http://husdal.com/tag/virtual-enterprise-network/">Virtual Enterprise Networks</a> are actually partly taken from my chapter proposal. For the sake of copyright and other issues, the full chapter will not be published on this blog until it is finalized and sent to the printers. The preliminary chapter proposal can be seen in my post on <a
href="http://husdal.com/2009/03/14/understanding-risks-in-virtual-enterprise-networks/">Understanding Risks in Virtual Enterprise Networks</a>.<a
href="http://husdal.com/tag/virtual-enterprise-network/"><br
/> </a></p><h3 style="text-align: justify;">Virtual Enterprise Networks</h3><p
style="text-align: justify;">I must admit that I knew very little, if anything, about Virtual Enterprise Networks when I started this adventure some months back, but I can now say that I am fascinated by the concept, and I believe that much of the future of supply chains lies in virtual enterprise networks. Supply chains have evolved in so far four stages, from the mere optimization of flows to economies of scale and further to economies of scope. The current stage is economies of integration, integrating and involving customer requirements in a value-driven rather than value-pushed supply chain, which leads to the next stage: economies of relationships. The basis for any virtual enterprise network is are the relationships among its partners, and my hope is that my chapter can contribute to managing the risks in the relationships that make up a virtual enterprise network.</p><h3 style="text-align: justify;">What if</h3><p
style="text-align: justify;">What if my chapter submission is not accepted? Well, as we say in Norwegian, &#8220;nothing is so bad it&#8217;s not good for something else&#8221;. I&#8217;ve covered some solid research ground and discovered many new articles on topics related to supply chain risk (and re-discovered som old ones I deemed not useful at that time). This means that large parts of my chapter could be re-worked into a journal article, or, if nothing else, at least I will be able to produce a whole string of posts about Virtual Enterprise Networks here on this blog.</p><h3>Related</h3><ul><li>husdal.com: <a
href="http://husdal.com/2009/03/14/understanding-risks-in-virtual-enterprise-networks/"><br
/> Understanding Risk in Virtual Enterprise Networks</a> (chapter proposal)</li><li>husdal.com: <a
href="http://www.husdal.com/2009/07/21/is-managing-risks-in-virtual-enterprise-networks-different-from-managing-risks-in-supply-chains/"><br
/> Is managing risks in Virtual Enterprise Networks different from managing risks in Supply Chains?</a> (conference presentation)</li><li>husdal.com:<br
/> <a
href="http://www.husdal.com/2010/03/17/managing-risks-in-virtual-enterprise-networks/">Finally, my book chapter is published</a></li></ul> ]]></content:encoded> <wfw:commentRss>http://www.husdal.com/2009/03/31/managing-risk-in-virtual-enterprise-networks/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Understanding risks in Virtual Enterprise Networks</title><link>http://www.husdal.com/2009/03/14/understanding-risks-in-virtual-enterprise-networks/</link> <comments>http://www.husdal.com/2009/03/14/understanding-risks-in-virtual-enterprise-networks/#comments</comments> <pubDate>Sat, 14 Mar 2009 09:05:50 +0000</pubDate> <dc:creator>Jan Husdal</dc:creator> <category><![CDATA[BOOKS and BOOK CHAPTERS]]></category> <category><![CDATA[knowledge management]]></category> <category><![CDATA[supply chain risk]]></category> <category><![CDATA[the networked enterprise]]></category> <category><![CDATA[Thompson Ken]]></category> <category><![CDATA[ven]]></category> <category><![CDATA[virtual enterprise]]></category> <category><![CDATA[virtual enterprise books]]></category> <category><![CDATA[virtual enterprise network]]></category> <guid
isPermaLink="false">http://husdal.com/?p=1772</guid> <description><![CDATA[I am currently writing a book chapter for the book Managing Risk in Virtual Enterprise Networks: Implementing Supply Chain Principles, which is about risks in Virtual Enterprise Networks (VENs). [ ... ]]]></description> <content:encoded><![CDATA[<p
style="text-align: justify;"><img
class="alignleft size-full wp-image-16021" style="margin-left: 5px; margin-right: 5px; border: 1px solid black;" title="the-networked-enterprise" src="http://www.husdal.com/wp-content/uploads/2009/03/the-networked-enterprise1.jpg" alt="" width="100" height="100" />Today&#8217;s unstable and highly competitive business environment has created a shift in how enterprises are established and managed, where past &#8220;traditional&#8221; enterprises are replaced by new &#8220;virtual&#8221; enterprises, forming temporary networks of independent companies or Virtual Enterprise Networks (VENs) that  share skills, costs and access to each other&#8217;s market. I am currently writing a book chapter for the book <strong><a
href="http://www.igi-global.com/Bookstore/Chapter.aspx?TitleId=42213">Managing Risk in Virtual Enterprise Networks: Implementing Supply Chain Principles</a></strong><img
style="border: none !important; margin: 0px !important;" src="http://www.assoc-amazon.com/e/ir?t=giswiz-20&amp;l=as2&amp;o=1&amp;a=1615206078" border="0" alt="" width="1" height="1" />, which is about risks in <a
href="http://www.bioteams.com/2008/06/09/the_networked_enterprise.html">Virtual Enterprise Networks</a> (VENs), and here are some the ideas that have come to my mind when trying to connect risks in supply chains with risks in VENs.</p><p
style="text-align: justify;"><span
id="more-1772"></span></p><h3>What is a VEN?</h3><p
style="text-align: justify;"><a
href="http://www.husdal.com/2009/03/17/jumpstart-your-ven-adventure/">Thompson (2008)</a> defines a VEN as &#8220;a voluntary and dynamic community of Small and Medium Enterprises that commit to working together for a set period of time, to collectively seek opportunities to participate in collaborative projects of mutual business interest&#8221;. A VEN is by definition a time-limited structure; it has a set life-cycle, i.e. the duration of a project in which the participating enterprises partake. This life cycle perspective poses certain challenges in how to manage VEN risks, as they may change from project to project.</p><h3><strong>Drivers of Supply Chain Vulnerability vis-à-vis Drivers of VEN Vulnerability</strong></h3><p
style="text-align: justify;">The view of a supply chain network that comes closest to a VEN is that of <a
href="http://husdal.com/2008/08/25/drivers-of-supply-chain-vulnerability/">Peck (2005)</a>, where the &#8220;chain&#8221; is not a chain, but a complex web or network of interlinked businesses. Here, this network is seen as operating on four levels, where the links within one level may not match the links within the other levels:</p><p
style="text-align: justify;">At level 1, the supply chain is seen as a logistics pipeline, where the focus on lean and agile practices have made supply chain performance the overall goal but at the same time it also exposed the supply chain to many risks. At level 2 the focus is on the supply chain as a carrier of goods and information, and supply chain vulnerability is determined by production sites, distribution centers and warehouses, as well as IT and other communication facilities, and also the whole transportation network from supplier to end customer. At level 3 the view is further afield, looking at the supply chain from a strategic and management perspective, where organizational management, power-sharing, collaboration and competition become important factors in evaluating vulnerability. At level 4 the view is a broad macroeconomic perspective, political, economic, social, legal and technological factors, and disruptions or sudden changes in these factors are more often than not beyond the control of the company, but must be dealt with accordingly.</p><p
style="text-align: justify;">The 4-level model employed by Peck is easily transferable to a VEN environment and is an excellent tool for explaining the scope and dynamic nature of supply chain risk. It emphasizes that a resilient network involves much more than the design and management of robust supply chain processes. It is also important to recognize that by taking actions to reduce risk at one point within the four levels, at the same time the risk profile for the other levels is changed, including players and stakeholders not thought of in the initial risk assessment. Supply chains are dynamic and constantly evolving, and so is supply chain risk, and managing this risk is a constant battle and a never-ending process. A VEN is by definition a time-limited structure; it has a set life-cycle, i.e. the duration of a project in which the participating enterprises partake. In a VEN, where the players are constantly changing, the risk is constantly changing, too.</p><h3><strong>VEN risk management vis-à-vis Business Continuity Management</strong></h3><p
style="text-align: justify;">A VEN is a collaboration rather than a competition, a collective effort rather than a set of individual efforts, and hence, the underlying idea of a VEN is that it is a win-win undertaking. Nonetheless, in today&#8217;s global and interwoven business environment, where supply chain disruptions can occur more or less frequently, the subsequent failure of one contributing participant in the supply network (or chain) can potentially lead to the collapse of the whole network (or chain). In a VEN environment, win-win turns into loose-loose, and consequently, the term <em>business continuity management</em> should be explored and related to <em>VEN continuity management</em>.</p><h3><strong>Strategies for managing VEN risks</strong></h3><p
style="text-align: justify;">Robustness, flexibility, and resilience stand out as three strategies or approaches towards supply chain disruptions. These three terms are distinctively different and which strategy that works best would depend not only on the supply chain in question as a whole, but also which part of the supply chain that may be vulnerable. A best-practice supply chain is likely to encompass all three, making it robust, flexible and resilient at the same time. There is a distinct notion of severity in these definitions, and in a business setting, the ability to survive (resilience) is likely to be much more important than the ability to quickly regain stability (robustness) or the ability to divert (flexibility). While on the supply chain side resilience may be the right way forward, on the VEN side it is more likely to be agility,  that should take priority, since essentially VENs are agile by nature. Agility in supply chains is a concept that is explored by for instance Christopher and Peck (2004).</p><h3><strong>Resilience as a key ingredient for managing VEN risks</strong></h3><p
style="text-align: justify;">A good illustration of where the susceptibility to disruption (and hence, the resilience and ability to recover) is a determining variable in the strength of a supply chain can be seen in a report from the New Zealand research initiative &#8220;Resilient Organisations&#8221; (<a
href="http://husdal.com/2007/12/09/can-supply-chain-management-learn-from-emergency-management/">Mc Manus, 2007</a>). Here, resilience is a 3-fold construct, depending on 1) keystone vulnerabilities, 2) situation awareness and 3) adaptive capacity. The adaptive capacity becomes particular important in recovering from a disruption. In a supply chain this could be viewed as the the inter- and intra-organizational &#8220;preparedness&#8221; (or worst case, &#8220;un-preparedness&#8221;). It is the preparedness then that determines the actual impact of supply chain disruptions.  However, supply chain resilience is not only a function of organizational preparedness; it is also a function of supply chain design, as in <a
href="http://husdal.com/2008/07/11/the-severity-of-supply-chain-disruptions-design-characteristics-and-mitigation-capabilities/">Craighead et al. (2007)</a>.</p><h3><strong>Supply chain vulnerability and VEN vulnerability</strong></h3><p
style="text-align: justify;">There is no one definition of supply chain vulnerability, and it is likewise difficult to make one definition of VEN vulnerability, but the closest definition is probably found in <a
href="http://husdal.com/2007/12/09/can-supply-chain-management-learn-from-emergency-management/">McManus (2007)</a>, where vulnerability is a function of the impact of a disruption and the organizational preparedness towards the disruption.</p><h3><strong>VEN characteristics as disruption impact parameters</strong></h3><p
style="text-align: justify;">The notion that both structural and organizational supply chain characteristics play a major role in supply chain disruptions is further underscored in <a
href="http://husdal.com/2008/07/11/the-severity-of-supply-chain-disruptions-design-characteristics-and-mitigation-capabilities/">Craighead et al. (2007</a>), where the severity of supply chain disruptions is related to supply chain design characteristics (supply chain density, supply chain complexity and node criticality) and supply chain mitigation capabilities (recovery capability and warning capability). In brief: supply chain structure and supply chain organization.</p><p
style="text-align: justify;">These factors are presented in the form of 6 propositions: Firstly, proposition 1 to 3, an unplanned event that disrupts a supply chain is more likely have a severe impact if the supply chain structure is 1) dense or 2) complex or 3) contains critical nodes or bottlenecks.  Secondly, proposition 4 and 5, an unplanned event that disrupts a supply chain is less likely have a severe impact if the supply chain 4) has proactive or reactive recovery capabilities or 5) warning capabilities,  as in detection and dissemination of critical information. Thirdly, proposition 6, combining the previous 5 propositions, an unplanned event disrupting a supply chain that is dense, complex and with many critical nodes is less likely to be severe if there is a capability to quickly detect and disseminate information about the event and thus respond and correct in a proactive or reactive manner.</p><p
style="text-align: justify;">It appears then that propositions 4, 5 and 6 are inherent to VENs, due to their collective and collaborative structure, and VENs should fare better vis-à-vis disruptions compared to traditional supply chains.</p><h3><strong>Conclusion</strong></h3><p
style="text-align: justify;">Supply chains are competitive, VENs are collaborative. Approaching VENs from a supply chain perspective can assist in defining the risks and challenges a VEN faces and how to manage them, particularly since many of the traditional supply chain risks stem from a lack of collaboration and visibility, the hallmarks of VENs, making VENs the ideal setup for supply chains and making supply chain risk management a fertile ground for researching VEN risk management.</p><h3><strong>Selected Key References</strong></h3><p
style="text-align: justify;">Christopher, M. (2005) Managing risk in the supply chain. In: Christopher, M. (Ed.) <a
href="http://www.amazon.com/gp/product/0273681761?ie=UTF8&amp;tag=giswiz-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0273681761"><em>Logistics and Supply Chain Management</em></a>. 3rd ed., Prentice Hall, pp. 231-258.</p><p
style="text-align: justify;">Christopher, M. and Peck, H. (2004) Building the Resilient Supply Chain. <em>The International Journal of Logistics Management</em>. Vol. 15, No. 2, pp. 1 &#8211; 14.</p><p
style="text-align: justify;">Craighead, C. W., Blackhurst, J., Rungtusanatham, M. J. &amp; Handfield, R. B. (2007) <a
href="http://husdal.com/2008/07/11/the-severity-of-supply-chain-disruptions-design-characteristics-and-mitigation-capabilities/">The Severity of Supply Chain Disruptions: Design Characteristics and Mitigation Capabilities</a>. <em>Decision Sciences</em>, Vol. 38, No. 1, pp. 131-156.</p><p
style="text-align: justify;">Mc Manus, S. et al (2007) <a
href="http://husdal.com/2007/12/09/can-supply-chain-management-learn-from-emergency-management/"><em>Resilience Management &#8211; A Framework for Assessing and Improving the Resilience of Organisations</em></a>. Research Report 2007/01, Resilient Organisations, New Zealand. www.resorgs.org.nz</p><p
style="text-align: justify;">Peck, H. (2005) <a
href="http://husdal.com/2008/08/25/drivers-of-supply-chain-vulnerability/">Drivers of supply chain vulnerability: an integrated framework.</a> <em>International Journal of Physical Distribution &amp; Logistics Management</em>, Vol. 35, No. 3/4, pp. 210-229.</p><p
style="text-align: justify;">Thompson, K. (2008) <a
href="http://www.husdal.com/2009/03/17/jumpstart-your-ven-adventure/"><em>The Networked Enterprise</em></a>. Meghan-Kiffer Press.</p><h3 style="text-align: justify;">Related</h3><ul><li>husdal.com: <a
href="http://www.husdal.com/2009/03/31/managing-risk-in-virtual-enterprise-networks/">Risks in Virtual Enterprise Networks</a></li></ul> ]]></content:encoded> <wfw:commentRss>http://www.husdal.com/2009/03/14/understanding-risks-in-virtual-enterprise-networks/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
<!-- This Quick Cache file was built for (  www.husdal.com/tag/knowledge-management/feed/ ) in 1.87989 seconds, on Feb 10th, 2012 at 11:18 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 7:18 pm UTC -->
