<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>01. Introduction to the ePM</title>
    <link>http://123.writeboard.com/dc510f51540e15823/show</link>
    <description>Tracking all versions for 01. Introduction to the ePM</description>
    <language>en-us</language>
    <ttl>40</ttl>
    <item>
      <title>Paul Fox: 01. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain. It helps you set direction. It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Build-to-order demand in hours or days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/li&gt;
		&lt;li&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand side with long design times and &lt;span class=&quot;caps&quot;&gt;NPI&lt;/span&gt; of IP essential semiconductors&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc where their is competition with the competition for the very sources of production.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Uses of the ePM:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Assist in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension emphasizes the importance of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; from the previous level.  Meeting the conditions of each level is an &lt;em&gt;enabler&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An organization need not progress to the next level until and unless that level is justified by relevant factors; e.g. environment, complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be selected for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space will ideally have at least some programs or relationships at which the highest level has been attained.&lt;/p&gt;


	&lt;h3&gt;Future Additions&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;&amp;#8220;Playbook&amp;#8221; for using the ePM&lt;/li&gt;
		&lt;li&gt;Relationship of the ePM to the &lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt; model&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Tue, 02 May 2006 23:06:54 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/742983</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/742983</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
    <item>
      <title>Paul Fox: 01. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain. It helps you set direction. It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Build-to-order demand in hours or days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/li&gt;
		&lt;li&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand side with long design times and &lt;span class=&quot;caps&quot;&gt;NPI&lt;/span&gt; of IP essential semiconductors&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc where their is competition with the competition for the very sources of production.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Uses of the ePM:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Assist in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension emphasizes the importance of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; from the previous level.  Meeting the conditions of each level is an &lt;em&gt;enabler&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An organization need not progress to the next level until and unless that level is justified by relevant factors; e.g. environment, complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be selected for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space will ideally have at least some programs or relationships at which the highest level has been attained.&lt;/p&gt;


	&lt;h3&gt;Future Additions&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;&amp;#8220;Playbook&amp;#8221; for using the ePM&lt;/li&gt;
		&lt;li&gt;Relationship of the ePM to the &lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt; model&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Tue, 02 May 2006 20:17:02 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/742207</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/742207</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
    <item>
      <title>John La Bouff: 1. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain. &lt;ins class=&quot;diffins&quot;&gt; It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.  &lt;/ins&gt;&lt;strong&gt;It helps you set &lt;del class=&quot;diffmod&quot;&gt;direction. It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;direction&lt;/ins&gt;&lt;/strong&gt;&lt;ins class=&quot;diffmod&quot;&gt;.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Build-to-order demand in hours or days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/li&gt;
		&lt;li&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand side with long design times and &lt;span class=&quot;caps&quot;&gt;NPI&lt;/span&gt; of IP essential semiconductors&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc where their is competition with the competition for the very sources of production.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Uses of the ePM:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Assist in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension emphasizes the importance of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; from the previous level.  Meeting the conditions of each level is an &lt;em&gt;enabler&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An organization need not progress to the next level until and unless that level is justified by relevant factors; e.g. environment, complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be selected for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space will ideally have at least some programs or relationships at which the highest level has been attained.&lt;/p&gt;


	&lt;h3&gt;Future Additions&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;&amp;#8220;Playbook&amp;#8221; for using the ePM&lt;/li&gt;
		&lt;li&gt;Relationship of the ePM to the &lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt; model&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Tue, 02 May 2006 16:26:50 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/740877</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/740877</link>
      <dc:creator>John La Bouff</dc:creator>
    </item>
    <item>
      <title>Dean Strausl: 1. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.  &lt;strong&gt;It helps you set direction&lt;/strong&gt;.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Build-to-order demand in hours or days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/li&gt;
		&lt;li&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand side with long design times and &lt;span class=&quot;caps&quot;&gt;NPI&lt;/span&gt; of IP essential semiconductors&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc where their is competition with the competition for the very sources of production.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;&lt;del class=&quot;diffmod&quot;&gt;Uses of the ePM:&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Use Cases:&lt;/ins&gt;&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Assist in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension emphasizes the importance of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; &lt;del class=&quot;diffmod&quot;&gt;from &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;on &lt;/ins&gt;the previous level.  Meeting the conditions of each level is &lt;del class=&quot;diffmod&quot;&gt;an &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;a &lt;/ins&gt;&lt;em&gt;&lt;del class=&quot;diffmod&quot;&gt;enabler&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;prerequisit&lt;/ins&gt;&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An &lt;del class=&quot;diffmod&quot;&gt;organization &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;organisation &lt;/ins&gt;need not progress to the next level &lt;del class=&quot;diffdel&quot;&gt;until and &lt;/del&gt;unless that level is justified by &lt;del class=&quot;diffmod&quot;&gt;relevant factors; &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;the appropriate decision factors, &lt;/ins&gt;e.g. &lt;del class=&quot;diffmod&quot;&gt;environment, &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;environemnt, &lt;/ins&gt;complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be &lt;del class=&quot;diffmod&quot;&gt;selected &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;elected &lt;/ins&gt;for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space &lt;del class=&quot;diffmod&quot;&gt;will ideally &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;would &lt;/ins&gt;have at least some programs or relationships &lt;del class=&quot;diffmod&quot;&gt;at which &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;that must be represented by &lt;/ins&gt;the highest &lt;del class=&quot;diffmod&quot;&gt;level has been attained.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;level.&lt;/ins&gt;&lt;/p&gt;


	&lt;h3&gt;&lt;del class=&quot;diffmod&quot;&gt;Future Additions&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Furure Additions&amp;#8221;&lt;/ins&gt;&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;&amp;#8220;Playbook&amp;#8221; for using the ePM&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;Relationship &lt;del class=&quot;diffmod&quot;&gt;of the ePM to the &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;to &lt;/ins&gt;&lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt;&lt;del class=&quot;diffmod&quot;&gt; model&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;&lt;ins class=&quot;diffmod&quot;&gt;How to use the ePM&lt;/ins&gt;&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Mon, 01 May 2006 22:15:04 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/737484</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/737484</link>
      <dc:creator>Dean Strausl</dc:creator>
    </item>
    <item>
      <title>Dean Strausl: 1. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.  &lt;strong&gt;It helps you set direction&lt;/strong&gt;.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Build-to-order demand in hours or days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/li&gt;
		&lt;li&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand side with long design times and &lt;span class=&quot;caps&quot;&gt;NPI&lt;/span&gt; of IP essential semiconductors&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing &lt;del class=&quot;diffmod&quot;&gt;etc where their is competition with the competition for the very sources of production.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;etc.&lt;/ins&gt;&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Assist in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension emphasizes the importance of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; on the previous level.  Meeting the conditions of each level is a &lt;em&gt;prerequisit&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An organisation need not progress to the next level unless that level is justified by the appropriate decision factors, e.g. environemnt, complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;


	&lt;h3&gt;Furure Additions&amp;#8221;&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;Relationship to &lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt;&lt;/li&gt;
		&lt;li&gt;How to use the ePM&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Mon, 01 May 2006 22:09:10 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/737467</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/737467</link>
      <dc:creator>Dean Strausl</dc:creator>
    </item>
    <item>
      <title>Paul Fox: 1. Introduction to the ePM</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the esca Progression Model (ePM) is to provide a strategic framework and common language for the design and improvement of supply chains and supply chain relationships in the electronics industry community.&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.  &lt;strong&gt;It helps you set direction&lt;/strong&gt;.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model. The model does not attempt to set standards.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;&lt;del class=&quot;diffmod&quot;&gt;Build-to-order &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Extremely short customer order lead times on the &lt;/ins&gt;demand &lt;del class=&quot;diffmod&quot;&gt;in &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;side of the chain (in the order of &lt;/ins&gt;hours or &lt;del class=&quot;diffmod&quot;&gt;days for products that are dependent on build-to-forecast semiconductors in weeks or months&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffmod&quot;&gt;Tradional market-maker channel masters driving demand are dependent on enormously capital intensive semiconductor silicon foundry decisions for supply&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;days) and long lead times at the supply end. &lt;/ins&gt;&lt;/li&gt;
		&lt;li&gt;Volatile consumer trends and short time to market on the demand &lt;del class=&quot;diffmod&quot;&gt;side with &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;side, High capital cost and &lt;/ins&gt;long &lt;del class=&quot;diffmod&quot;&gt;design times and &lt;/del&gt;&lt;span class=&quot;caps&quot;&gt;&lt;del class=&quot;diffmod&quot;&gt;NPI&lt;/del&gt;&lt;/span&gt;&lt;del class=&quot;diffmod&quot;&gt; of IP essential semiconductors&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;leadtime for new fabs. Leading to boom-bust cycles.&lt;/ins&gt;&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Differentiation between high IP, high cost components and commodities.&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffmod&quot;&gt;Assist &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Assit &lt;/ins&gt;in the planning and establishment of new or improved supply chains.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; calcualtions.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;The structure and grouping of the  dimesions are designed to make the ePM practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;The dimensions flow from the top down to represent a logical progresion. The dimensions start with the definition of business objectives, then the risks to acheiving those objectives, then the processes, then the organisation, and ending in tool selection. The final dimension &lt;del class=&quot;diffmod&quot;&gt;emphasizes the importance &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;emphaises the important &lt;/ins&gt;of continuous improvement.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;Each level is a &lt;em&gt;progression&lt;/em&gt; on the previous level.  Meeting the conditions of each level is a &lt;em&gt;prerequisit&lt;/em&gt; of advancement to the next level..&lt;/p&gt;


	&lt;p&gt;An organisation need not progress to the next level unless that level is justified by the appropriate decision factors, e.g. environemnt, complexity, risk, relationships, available budget, &lt;span class=&quot;caps&quot;&gt;ROI&lt;/span&gt; etc.  The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;A large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;


	&lt;h3&gt;Furure Additions&amp;#8221;&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;Relationship to &lt;span class=&quot;caps&quot;&gt;SCOR&lt;/span&gt;&lt;/li&gt;
		&lt;li&gt;How to use the ePM&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Fri, 28 Apr 2006 19:23:46 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/728722</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/728722</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
    <item>
      <title>John La Bouff: 1. Introduction</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the &lt;del class=&quot;diffmod&quot;&gt;esca Progression Model (ePM) &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;progression model &lt;/ins&gt;is to provide a strategic framework and common language for the design &lt;del class=&quot;diffdel&quot;&gt;and improvement &lt;/del&gt;of supply chains and supply chain relationships in the electronics &lt;del class=&quot;diffmod&quot;&gt;industry community.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;industry.&lt;/ins&gt;&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;&lt;del class=&quot;diffdel&quot;&gt;Common Language.&lt;/del&gt;&lt;/strong&gt;&lt;del class=&quot;diffdel&quot;&gt;  The model is intended to provide a common language for in depth discussions between supply chain partners and the electronics supply chain community.&lt;/del&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.  &lt;strong&gt;It helps you set direction&lt;/strong&gt;.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;&lt;ins class=&quot;diffins&quot;&gt;Common Language.&lt;/ins&gt;&lt;/strong&gt;&lt;ins class=&quot;diffins&quot;&gt;  The model is intended to provide a common language for discussions between supply chain partners and the electronics supply chain community.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. &lt;del class=&quot;diffmod&quot;&gt;These relationships can range from simple supply relationships to turn-key outsourcing.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Recognizes that when you outsource a function it becomes a supply chain issue.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the &lt;del class=&quot;diffmod&quot;&gt;model. The model does not attempt to set standards.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;model.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;&lt;del class=&quot;diffmod&quot;&gt;Extremely &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;Dichotomy between extremely &lt;/ins&gt;short customer order lead times on the demand side of the chain (in the order of hours or days) and long lead times at the supply end. &lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Volatile consumer trends and short time to market on the demand side, High capital cost and long leadtime for new fabs. Leading to boom-bust cycles.&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Differentiation between high IP, high cost components and commodities.&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Assit in the planning and establishment of new or improved supply chains.&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;&lt;ins class=&quot;diffins&quot;&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/ins&gt;&lt;/li&gt;
		&lt;li&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Help identify the contributors and risks to be considered for cost-benefit and &lt;/del&gt;&lt;span class=&quot;caps&quot;&gt;&lt;del class=&quot;diffdel&quot;&gt;ROI&lt;/del&gt;&lt;/span&gt;&lt;del class=&quot;diffdel&quot;&gt; calcualtions.&lt;/del&gt;&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management &lt;ins class=&quot;diffins&quot;&gt;sophistication &lt;/ins&gt;required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;&lt;del class=&quot;diffmod&quot;&gt;The structure and grouping of the  dimesions are designed to &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;By their very nature, each of the dimensions is going to be highly related.  Pulling them into a one dimensional list is going to represent a compromise.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;ins class=&quot;diffmod&quot;&gt;Each of the dimensions should have a definition that also helps show the links to the other dimensions.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;ins class=&quot;diffmod&quot;&gt;We must &lt;/ins&gt;make &lt;del class=&quot;diffmod&quot;&gt;the ePM &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;it &lt;/ins&gt;practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;&lt;del class=&quot;diffmod&quot;&gt;The &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;One approach is to let the &lt;/ins&gt;dimensions flow from the top &lt;del class=&quot;diffmod&quot;&gt;down to represent a logical progresion. The dimensions start &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;down, starting &lt;/ins&gt;with &lt;del class=&quot;diffdel&quot;&gt;the definition of &lt;/del&gt;business &lt;del class=&quot;diffmod&quot;&gt;objectives, then the risks to acheiving those objectives, then the processes, then the organisation, &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;objectives &lt;/ins&gt;and ending in tool &lt;del class=&quot;diffmod&quot;&gt;selection. The final dimension emphaises the important of continuous improvement.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;selection.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;p&gt;&lt;del class=&quot;diffdel&quot;&gt;Beacause the dimensions are so highly related, pulling them into a one dimensional list is a compromise. However, each of the dimensions has a definition that also helps show the links to the other dimensions.&lt;/del&gt;&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;&lt;del class=&quot;diffmod&quot;&gt;Each &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;The Levels are not intended to imply that a higher &lt;/ins&gt;level is &lt;del class=&quot;diffmod&quot;&gt;a &lt;/del&gt;&lt;em&gt;&lt;del class=&quot;diffmod&quot;&gt;progression&lt;/del&gt;&lt;/em&gt;&lt;del class=&quot;diffmod&quot;&gt; on the previous &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;better or worse that a lower &lt;/ins&gt;level. &lt;del class=&quot;diffdel&quot;&gt; Meeting the conditions of each level is a &lt;/del&gt;&lt;em&gt;&lt;del class=&quot;diffdel&quot;&gt;prerequisit&lt;/del&gt;&lt;/em&gt;&lt;del class=&quot;diffdel&quot;&gt; of advancement to the next level..&lt;/del&gt;&lt;/p&gt;


	&lt;p&gt;&lt;del class=&quot;diffdel&quot;&gt;An organisation need not progress to the next level unless that level is justified by the appropriate decision factors, e.g. environemnt, complexity, risk, relationships, available budget, &lt;/del&gt;&lt;span class=&quot;caps&quot;&gt;&lt;del class=&quot;diffdel&quot;&gt;ROI&lt;/del&gt;&lt;/span&gt;&lt;del class=&quot;diffdel&quot;&gt; etc.  &lt;/del&gt;The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;&lt;del class=&quot;diffmod&quot;&gt;A &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;It is highly likely that a &lt;/ins&gt;large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;


	&lt;h3&gt;&lt;del class=&quot;diffdel&quot;&gt;Furure Additions&amp;#8221;&lt;/del&gt;&lt;/h3&gt;


	&lt;ul&gt;
	&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Relationship to &lt;/del&gt;&lt;span class=&quot;caps&quot;&gt;&lt;del class=&quot;diffdel&quot;&gt;SCOR&lt;/del&gt;&lt;/span&gt;&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;How to use the ePM&lt;/del&gt;&lt;/li&gt;
	&lt;/ul&gt;</description>
      <pubDate>Fri, 28 Apr 2006 19:15:00 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/728680</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/728680</link>
      <dc:creator>John La Bouff</dc:creator>
    </item>
    <item>
      <title>Paul Fox: 1. Introduction</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the progression model is to provide a strategic framework and common language for the design of supply chains and supply chain relationships in the electronics &lt;del class=&quot;diffmod&quot;&gt;industry.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;industry..&lt;/ins&gt;&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step &lt;del class=&quot;diffmod&quot;&gt;manner.  &lt;/del&gt;&lt;strong&gt;&lt;del class=&quot;diffmod&quot;&gt;It helps you set direction&lt;/del&gt;&lt;/strong&gt;&lt;del class=&quot;diffmod&quot;&gt;.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;manner.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization. Recognizes that when you outsource a function it becomes a supply chain issue.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Dichotomy between extremely short customer order lead times on the demand side of the chain (in the order of hours or days) and long lead times at the supply end. &lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Provides a vocabulary for shared communication across companies and functions.&lt;/del&gt;&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Serves as a guide for planning and prioritizing key business improvements.&lt;/del&gt;&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management sophistication required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;By their very nature, each of the dimensions is going to be highly related.  Pulling them into a one dimensional list is going to represent a compromise.&lt;/p&gt;


	&lt;p&gt;Each of the dimensions should have a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;p&gt;We must make it practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;One approach is to let the dimensions flow from the top down, starting with business objectives and ending in tool selection.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;The Levels are not intended to imply that a higher level is better or worse that a lower level. The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;It is highly likely that a large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;</description>
      <pubDate>Thu, 27 Apr 2006 23:10:32 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/725159</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/725159</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
    <item>
      <title>Paul Fox: 1. Introduction</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the progression model is to provide a strategic framework and common language for the design of supply chains and supply chain relationships in the electronics industry..&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the &lt;del class=&quot;diffmod&quot;&gt;organization. Recognizes that when you outsource a function it becomes a supply chain issue.&lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;organization.&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Recognizes the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Dichotomy between extremely short customer order lead times on the demand side of the chain (in the order of hours or days) and long lead times at the supply end. &lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Extremely short product life-cycles and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
		&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
		&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management sophistication required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;Dimensions&lt;/h3&gt;


	&lt;p&gt;By their very nature, each of the dimensions is going to be highly related.  Pulling them into a one dimensional list is going to represent a compromise.&lt;/p&gt;


	&lt;p&gt;Each of the dimensions should have a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;p&gt;We must make it practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;One approach is to let the dimensions flow from the top down, starting with business objectives and ending in tool selection.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;The Levels are not intended to imply that a higher level is better or worse that a lower level. The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;It is highly likely that a large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;</description>
      <pubDate>Wed, 26 Apr 2006 00:53:51 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/714505</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/714505</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
    <item>
      <title>Paul Fox: 1. Introduction</title>
      <description>&lt;h2&gt;Purpose / Objective&lt;/h2&gt;


	&lt;p&gt;The purpose of the progression model is to provide a strategic framework and common language for the design of supply chains and supply chain relationships in the electronics industry..&lt;/p&gt;


	&lt;h2&gt;Characteristics&lt;/h2&gt;


	&lt;p&gt;&lt;strong&gt;Strategic in Nature.&lt;/strong&gt; The model is strategic in nature. It helps define the strategic rationale and best practices behind a particular choice of supply chain.  It is not the intention of the model to describe supply chain contracts or processes in a line by line or step by step manner.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Common Language.&lt;/strong&gt;  The model is intended to provide a common language for discussions between supply chain partners and the electronics supply chain community.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Relationship Based.&lt;/strong&gt; The model inherently considers &#8220;relationships&#8221; within the supply network. Several of the dimensions are specifically about how we work with partners rather than what we do within the four walls of the organization.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;Non Judgmental.&lt;/strong&gt;  The model tries not to judge a particular decision as &#8220;good&#8221; or &#8220;bad&#8221;. For example neither &#8220;in house&#8221; or &#8220;outsourced&#8221; is considered best in a particular situation.  The highest level is not the &#8220;best level&#8221;, it is merely the highest level of sophistication needed to manage a particularly complex supply chain or relationship.  For many other supply chains or relationships, a lower level of sophistication may be best.  However, the model does imply that it is good supply chain practice to make explicit decisions based on all the factors considered in the model. Moreover, some &#8220;best practices&#8221; in supply chain may be implicit in the model.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;&lt;del class=&quot;diffmod&quot;&gt;Recognizes &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;*Recognises &lt;/ins&gt;the Characteristics of the Electronics Supply Chain:&lt;/strong&gt;&lt;/p&gt;


	&lt;ul&gt;
	&lt;li&gt;Dichotomy between extremely short customer order lead times on the demand side of the chain (in the order of hours or days) and long lead times at the supply end. &lt;/li&gt;
		&lt;li&gt;Intellectual property embedded in  both the end product and the silicon. &lt;/li&gt;
		&lt;li&gt;Extremely short product &lt;del class=&quot;diffmod&quot;&gt;life-cycles &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;lifecycles &lt;/ins&gt;and often inherently long development/approval cycles. &lt;/li&gt;
		&lt;li&gt;The adoption of extreme forms (whole of product or whole of life) of outsourcing, e.g. &lt;span class=&quot;caps&quot;&gt;ODM&lt;/span&gt;, contract design and manufacturing etc.&lt;/li&gt;
	&lt;/ul&gt;


	&lt;h2&gt;Use Cases:&lt;/h2&gt;


	&lt;ol&gt;
	&lt;li&gt;To assess the overall level of supply chain sophistication of an organization.  In this case we are looking at the top-most level used within the organization in all its supply chain relationships.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;ol&gt;
	&lt;li&gt;To assess the overall level of supply chain sophistication in a particular supply chain or particular supply chain relationship.&lt;/li&gt;
	&lt;/ol&gt;


	&lt;ol&gt;
	&lt;li&gt;Discuss developments and trends within electronics supply chain management.&lt;/li&gt;
		&lt;li&gt;&lt;del class=&quot;diffdel&quot;&gt;Enable participants in a supply chain to understand the drivers and constraints in another part of the supply chain (e.g. to enable a 3PL to understand the point of view of a semiconductor manufacturer).&lt;/del&gt;&lt;/li&gt;
	&lt;/ol&gt;


	&lt;h2&gt;Structure of the Model&lt;/h2&gt;


	&lt;p&gt;The model is a grid.  Down the left hand side are &amp;#8220;Dimensions&amp;#8221;.  Across the top are &amp;#8220;Levels&amp;#8221; which represent a degree of management sophistication required to manage a particular supply chain.&lt;/p&gt;


	&lt;h3&gt;&lt;del class=&quot;diffmod&quot;&gt;Dimensions&lt;/del&gt;&lt;/h3&gt;&lt;p&gt;&lt;ins class=&quot;diffmod&quot;&gt;h3.Dimensions&lt;/ins&gt;&lt;/p&gt;


	&lt;p&gt;By their very nature, each of the dimensions is going to be highly related.  Pulling them into a one dimensional list is going to represent a compromise.&lt;/p&gt;


	&lt;p&gt;Each of the dimensions should have a definition that also helps show the links to the other dimensions.&lt;/p&gt;


	&lt;p&gt;We must make it practical to use (rather than be a list of abstract concepts).&lt;/p&gt;


	&lt;p&gt;One approach is to let the dimensions flow from the top down, starting with business objectives and ending in tool selection.&lt;/p&gt;


	&lt;p&gt;This might be the manner in which you would design the supply chain or form a supply chain relationship with a new partner.  Of course this would be an iterative process, since the dimensions are so highly related.&lt;/p&gt;


	&lt;h3&gt;Levels&lt;/h3&gt;


	&lt;p&gt;The Levels are not intended to imply that a higher level is better or worse that a lower level. The appropriate level should be elected for the particular case.&lt;/p&gt;


	&lt;p&gt;It is highly &lt;del class=&quot;diffmod&quot;&gt;likely &lt;/del&gt;&lt;ins class=&quot;diffmod&quot;&gt;likley &lt;/ins&gt;that a large company operating in the electronics space would have at least some programs or relationships that must be represented by the highest level.&lt;/p&gt;</description>
      <pubDate>Tue, 25 Apr 2006 19:37:04 +0000</pubDate>
      <guid>http://123.writeboard.com/dc510f51540e15823/v/show/712858</guid>
      <link>http://123.writeboard.com/dc510f51540e15823/v/show/712858</link>
      <dc:creator>Paul Fox</dc:creator>
    </item>
  </channel>
</rss>
