<?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>Numetrics &#187; Products</title>
	<atom:link href="http://www.numetrics.com/category/products/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.numetrics.com</link>
	<description>Numetrics makes semiconductor product-development teams more productive</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:25:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>For Semiconductor Companies, a New Focus on Differentiation</title>
		<link>http://www.numetrics.com/2009/10/05/for-semiconductor-companies-a-new-focus-on-differentiation/</link>
		<comments>http://www.numetrics.com/2009/10/05/for-semiconductor-companies-a-new-focus-on-differentiation/#comments</comments>
		<pubDate>Mon, 05 Oct 2009 16:10:44 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[David Manners]]></category>
		<category><![CDATA[Electronics Weekly]]></category>
		<category><![CDATA[Future Horizons]]></category>
		<category><![CDATA[IEF]]></category>
		<category><![CDATA[new product development]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductors]]></category>

		<guid isPermaLink="false">http://blog.numetrics.com:8080/numetricsblog/?p=106</guid>
		<description><![CDATA[
(Summary: For semiconductor companies, differentiation has shifted from manufacturing to improving productivity in new-product development. That realization is the easy part; getting there requires help.)
By Ron Collett
I’m always impressed with the level of optimism I find at semiconductor industry events around the world. There may be pockets of gloom about the state of the semiconductor [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p align="center"><strong><br />
</strong></p>
<p style="padding-left: 30px;"><em>(<strong>Summary: </strong>For semiconductor companies, differentiation has shifted from manufacturing to improving productivity in new-product development. That realization is the easy part; getting there requires help.)</em></p>
<p><a href="mailto:ronc@numetrics.com"><em>By Ron Collett</em></a></p>
<p>I’m always impressed with the level of optimism I find at semiconductor industry events around the world. There may be pockets of gloom about the state of the semiconductor industry, but executives certainly don’t share it. Yes, it’s not the same industry it was 10 years ago, but, no, it’s not doomed. Far from it: The dynamics are just different.</p>
<p>That was my message when I presented last week at Malcolm Penn’s <a href="http://www.futurehorizons.com/page/9/international-electronics" target="_blank">International Electronics Forum</a> in Geneva. Here’s <em>why </em>the dynamics are different:</p>
<ul>
<li>The industry head count has shrunk 30 percent      this decade</li>
<li>Industry consolidation has picked up pace</li>
<li>Cost-cutting is rampant</li>
<li>There’s more pressure than ever on design      teams to get great products out the door on time and on budget</li>
</ul>
<p>Here’s <em>how</em> the dynamics are different: Differentiation has shifted as industry disaggregation has reached an end state. There was a time when a semiconductor company differentiated itself through manufacturing and process technology (or way back when, through making its own steppers!) No longer.</p>
<p>So where’s the differentiation? It’s not in cost-cutting. Everyone’s doing that.</p>
<p>Differentiation has <strong>shifted to the heart of the semiconductor company’s value proposition: its new-product development</strong>.</p>
<p>Electronics Weekly’s David Manners, in his coverage of IEF last week (“<a href="http://www.electronicsweekly.com/blogs/david-manners-semiconductor-blog/2009/10/whats-the-answer-to-the-chip-i.html" target="_blank">What’s the Answers to the Chip Industry’s Problems? Ask IEF</a>”), touched on how profound this can be. He quoted Alain Dutheil, CEO of ST-Ericsson, as saying 85 percent of his 8,000 employees are in R&amp;D.</p>
<p>The other part of the story, which we’ve blogged about, is that most SOC projects slip schedule and most <a href="../?p=90">IC teams tend to underestimate their product R&amp;D costs</a>.</p>
<p>That brings me back to our IEF presentation (“Raising the Bar on Semiconductor R&amp;D Management, Execution, and ROI”), which we created in partnership with <a href="http://prtm.com/">PRTM</a>, one of the world’s premier operational strategy consulting firms (with deep ties to the IC industry).</p>
<p>Our three take-aways were:</p>
<ul>
<li>The bar is being      significantly raised on semiconductor R&amp;D management, execution, and      achieving ROI</li>
<li>Companies must      continuously progress through the stages of maturity to thrive      (functional, project, portfolio, and cross-enterprise excellence)</li>
<li>Fact-based planning      is a critical foundation for ongoing NPD success</li>
</ul>
<p>Anyone can cut costs in challenging times but winning companies find news ways to differentiate themselves, and they are the companies that come out of recessions stronger than their competition.</p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/10/05/for-semiconductor-companies-a-new-focus-on-differentiation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Re-Planning semiconductor design projects effectively</title>
		<link>http://www.numetrics.com/2009/08/03/re-planning/</link>
		<comments>http://www.numetrics.com/2009/08/03/re-planning/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 17:29:10 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=23</guid>
		<description><![CDATA[
Summary: Re-planning a semiconductor design project is often inevitable as the program is underway. The key to effective, productive re-planning lies in understanding complexity, schedule and resources.

Change is inevitable. Economic factors, mergers and acquisitions, customer specification changes, management and strategy changes all affect project planning and execution. These factors create a need for re-planning IC [...]


Related posts:<ol><li><a href='http://www.numetrics.com/2011/03/03/optimal-team-sizes-for-chip-projects/' rel='bookmark' title='Permanent Link: Optimal Team Sizes for Chip Projects'>Optimal Team Sizes for Chip Projects</a> <small> What&#8217;s the optimal team size for a given IC...</small></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><em><strong>Summary</strong>: Re-planning a semiconductor design project is often inevitable as the program is underway. The key to effective, productive re-planning lies in understanding complexity, schedule and resources.</em></p>
</blockquote>
<p class="MsoBodyText">Change is inevitable. Economic factors, mergers and acquisitions, customer specification changes, management and strategy changes all affect project planning and execution. These factors create a need for re-planning IC projects while they are ongoing.</p>
<p class="MsoBodyText">The key to re-planning is the same as for the original planning process: an understanding of <a href="http://202.142.150.34/numetricsblog/?p=12">complexity</a>, schedule and resources. Numetrics’ NMX-ERP can capture not only the starting characteristics of your design, but also updates as work is completed. This means that at any point during the design, you can calculate the work remaining and the resource and/or schedule implications of that.</p>
<p class="MsoBodyText">Re-planning is simply a process of updating the assumptions based on new information. From there it is a simple process to re-run the analysis, and to generate a new plan. This is easy not only because there is explicit support in the tools for re-planning and the management of multiple scenarios for a single design, but also because there is no need for data re-entry. Everything is built from the original plan, saving a great deal of time for your planners.</p>
<div class="wp-caption alignright" style="width: 353px"><a href="http://www.numetrics.com/images/product_schedulerisk.jpg"><img style="border: 1px solid black;" title="Risk Analyzer" src="http://www.numetrics.com/images/product_schedulerisk.jpg" alt="Schedule Risk Analyzer generates a comprehensive set of reports that quantitatively assess the underlying schedule risk, given the design’s complexity, staffing assigned to the project and target cycle-time." width="343" height="224" /></a><p class="wp-caption-text">Schedule Risk Analyzer generates a comprehensive set of reports that quantitatively assess the underlying schedule risk, given the design’s complexity, staffing assigned to the project and target cycle-time.</p></div>
<p class="MsoBodyText">The real implication of the re-planning capability is that when a change is proposed, you can <strong>quickly determine feasibility</strong>. For example, if marketing comes to you and says, “We need samples six weeks early for a key customer,” you can rapidly tell them what that means for resources. If additional resources are not available, you might consider scaling back product features to meet the new schedule. Alternatively, you may be forced to complete the design with fewer engineers than you had originally planned for. In such a case, you can quickly determine the best way to meet your business objectives with the new constraint—either reducing the feature set, or planning for a managed schedule slip.</p>
<p class="MsoBodyText">The net benefit of Numetrics’ re-planning tools is fact-based decision-making in a time of stress. Fact-based planning improves the quality of internal decisions, leading to a healthier business and happier employees. And that can’t be bad.</p>
<p><!--EndFragment--></p>


<p>Related posts:<ol><li><a href='http://www.numetrics.com/2011/03/03/optimal-team-sizes-for-chip-projects/' rel='bookmark' title='Permanent Link: Optimal Team Sizes for Chip Projects'>Optimal Team Sizes for Chip Projects</a> <small> What&#8217;s the optimal team size for a given IC...</small></li></ol></p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/08/03/re-planning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Effective what-if scenario analysis for IC development projects</title>
		<link>http://www.numetrics.com/2009/03/17/what-if-scenario-analysis/</link>
		<comments>http://www.numetrics.com/2009/03/17/what-if-scenario-analysis/#comments</comments>
		<pubDate>Tue, 17 Mar 2009 17:20:55 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Industry Database]]></category>
		<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[Analysis]]></category>
		<category><![CDATA[ERP software]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[planning software]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[project management software]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>
		<category><![CDATA[semiconductors]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=17</guid>
		<description><![CDATA[
Summary: Comparing the specifics of your semiconductor design with industry and company history enables insightful what-if scenario analysis to help manage development programs effectively .

During the planning stages for a chip design, there are a number of variables that can be tweaked in the creation of the final product plan. We can reduce or expand [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><strong>Summary</strong>: Comparing the specifics of your semiconductor design with industry and company history enables insightful what-if scenario analysis to help manage development programs effectively .</p>
</blockquote>
<p class="MsoBodyText">During the planning stages for a chip design, there are a number of variables that can be tweaked in the creation of the final product plan. We can reduce or expand the feature set for a new device. We can reduce or extend the schedule. And we can reduce or increase the number of full-time-equivalent (FTE) staff allocated to the project. By manipulating these variables, we can negotiate a plan between the different stakeholders. In some cases, resources are the limiting factor. In others, the schedule is non-negotiable (for example a lot of consumer products must be ready for CES).</p>
<p><a href="http://www.numetrics.com/images/about_coretech_img3.jpg"><img class="alignleft" title="What-if scenario analysis" src="http://www.numetrics.com/images/about_coretech_img3.jpg" alt="" width="293" height="191" /></a></p>
<p class="MsoBodyText">Running a lot of plans against all these variables has historically been difficult and time-consuming. In addition, the results have always been subject to arguments because there has been no trusted model to relate complexity, resources and schedule. Numetrics changes all that. By tweaking resource, schedule or feature set (<a href="http://202.142.150.34/numetricsblog/2009/01/23/complexity/">complexity</a>) assumptions, <a href="http://www.numetrics.com/products/overview.jsp">NMX-ERP</a> can rapidly generate graphs that show the feasibility of each plan, and compare it with company and industry norms using their proprietary complexity engine and plan synthesizer.</p>
<p class="MsoBodyText">The speed and defensibility of these analyses lends them great power. It is not rational to assume productivity or schedules that are significantly different from past performance, so any feasible plan must lie close to the lessons of history. There is a cost to adding features, or to shrinking the schedule, or to reducing headcount. The most effective way to negotiate these choices is with the aid of <a href="http://www.numetrics.com/services/projplanning.jsp">an objective toolset that combines the specifics of your design and plan with industry and company history</a>. The tool is fast enough that you can run tens or even hundreds of plans in minutes or hours. From these scenarios you can then pick the plan that best meets your business goals.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/03/17/what-if-scenario-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is industry-norm effort for semiconductor designs?</title>
		<link>http://www.numetrics.com/2009/02/14/industry-norm-effort/</link>
		<comments>http://www.numetrics.com/2009/02/14/industry-norm-effort/#comments</comments>
		<pubDate>Sat, 14 Feb 2009 17:16:52 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[ERP software]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[planning software]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[project management software]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>
		<category><![CDATA[semiconductors]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=14</guid>
		<description><![CDATA[
Summary: Realistic semiconductor IC project planning hinges on industry-norm effort, which is the comparison of the actual productivity achieved by teams across the industry and the actual complexity of their designs.

Complexity is a measurement of how difficult it is to complete a design. It’s a measurement based on many attributes of the design, carefully correlated [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><strong>Summary</strong>: Realistic semiconductor IC project planning hinges on industry-norm effort, which is the comparison of the actual productivity achieved by teams across the industry and the actual complexity of their designs.</p>
</blockquote>
<p class="MsoBodyText">Complexity is a measurement of how difficult it is to complete a design. It’s a measurement based on many attributes of the design, carefully correlated across multiple historical designs. But in order to plan, we need <strong>to know the amount of effort it will take to complete a design</strong> of a certain <a href="http://202.142.150.34/numetricsblog/?p=12">complexity</a>. The answer lies in a comparison of the actual productivity achieved by teams across the industry and the actual complexity of their designs.</p>
<p class="MsoBodyText">From this comparison we can calculate the amount of complexity an average designer can implement in a unit of time. Because this is a normative value calculated across the industry, we call it <em>industry norm effort. </em></p>
<p class="MsoBodyText">We can also make the same calculation for your company—assessing the amount of complexity your designers have historically been able to implement in a unit time. By comparing this with the industry norm, you will get a sense of how your team is doing as compared with the industry.</p>
<p class="MsoBodyText">But the main use of industry norm effort is in conjunction with the complexity data for a proposed design:</p>
<ul>
<li>We can accurately and rapidly calculate the total effort required for that design using either your company data, or the industry norm data.</li>
</ul>
<p>This provides <strong>a firm foundation for realistic planning</strong>, while still allowing you to set aggressive (but not unrealistic) targets for your team.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/02/14/industry-norm-effort/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How do you quantify design complexity?</title>
		<link>http://www.numetrics.com/2009/01/23/complexity/</link>
		<comments>http://www.numetrics.com/2009/01/23/complexity/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 17:15:43 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[Complexity]]></category>
		<category><![CDATA[ERP software]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[planning software]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[project management software]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>
		<category><![CDATA[semiconductors]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=12</guid>
		<description><![CDATA[

Summary: Design complexity can be quantified and communicated in a way that makes IC projects predictable and more productive.


It doesn’t take a rocket scientist to know that the resources and time required to build a chip vary from one design to another. The variation is a function of how difficult the chip will be to [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.icubed.us/files/Rubiks_Cube-731722.jpg"><img class="alignright" title="Rubiks Cube" src="http://www.icubed.us/files/Rubiks_Cube-731722.jpg" alt="" width="409" height="281" /></a><br />
<!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><strong>Summary</strong>: Design complexity can be quantified and communicated in a way that makes IC projects predictable and more productive.</p>
</blockquote>
<p class="MsoBodyText">
<p class="MsoBodyText">It doesn’t take a rocket scientist to know that the resources and time required to build a chip vary from one design to another. The variation is a function of how difficult the chip will be to build. We <strong>measure that and call it complexity</strong>.</p>
<p class="MsoBodyText">
<p class="MsoBodyText">The hard part, however, is to know <em>which attributes of the design correlate to the effort required</em> to build the chip.</p>
<ul>
<li>Is clock speed important?</li>
<li>What about the number of transistors?</li>
<li>Re-use?</li>
<li>Analog and mixed signal?</li>
<li>Voltage islands?</li>
<li>Modes?</li>
</ul>
<p class="MsoBodyText">
<p class="MsoBodyText">The list goes on and on. One of the reasons why the <a href="http://www.numetrics.com/products/overview.jsp">NMX-ERP™ software suite</a> accurately forecasts the time and resource requirements for a design is that our engineers, using more than a thousand design projects, have developed a deep understanding of just how hard a given project may be so <strong>your engineers can be more productive</strong>.</p>
<p class="MsoBodyText">Knowing how to translate chip-design attributes into complexity is the foundation of <a href="http://www.numetrics.com/solutions/overview.jsp">apples-to-apples comparisons between designs</a>. That’s critical to making sure your latest design can be compared with other industry designs, as well as designs your company has done in the past. After taking in all the complexity factors as chip specifications, <strong>Numetrics’ engines can reliably and rapidly calculate the relative complexity of your design</strong>, as compared with every other design in our industry database. That’s the foundation upon which all the plan synthesis, what-if scenario analysis, re-planning and root-cause analysis capabilities of NMX-ERP are built.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/01/23/complexity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

