Comments on: One + One = ??? - What Would You Pay? http://theasicguy.com/2008/07/02/one-one-what-would-you-pay/ sharing insights into the people side of ASIC design Sat, 22 Nov 2008 07:10:56 +0000 http://wordpress.org/?v=2.3.2 By: Lou Covey http://theasicguy.com/2008/07/02/one-one-what-would-you-pay/#comment-110 Lou Covey Fri, 11 Jul 2008 16:14:35 +0000 http://theasicguy.com/2008/07/02/one-one-what-would-you-pay/#comment-110 I wonder wear this attitude of entitlement actually began? The entire electronic design industry seems bathed in it. As a die-hard mac user, I'm well versed in the concepts of upgrades versus updates, features vs. bug fixes. Whenever Apple has an update, its generally to fix an inadequacy or a failure of some sort. I pay for support when I can't find an answer through the extensive information database or through my network of Apple users. And when there is a real upgrade , I know enough to wait a few months until everything is broken in before making the change. But in EDA, the vendors sell the product before its ready, because the customers demand it before it's ready and everyone complains because nothing works the way it should and costs more than it's "supposed" to. EDA vendors should fix problems in their tools on their dime. EDA customers should pay for changes that they ask for. EDA vendors should LISTEN to their customers and give them products they request, and the customers should pay when the vendors respond appropriately. And any new, unasked for feature should be bullet-proofed, adequately explained and supported by the vendors. I wonder wear this attitude of entitlement actually began? The entire electronic design industry seems bathed in it.

As a die-hard mac user, I’m well versed in the concepts of upgrades versus updates, features vs. bug fixes. Whenever Apple has an update, its generally to fix an inadequacy or a failure of some sort. I pay for support when I can’t find an answer through the extensive information database or through my network of Apple users. And when there is a real upgrade , I know enough to wait a few months until everything is broken in before making the change.

But in EDA, the vendors sell the product before its ready, because the customers demand it before it’s ready and everyone complains because nothing works the way it should and costs more than it’s “supposed” to.

EDA vendors should fix problems in their tools on their dime. EDA customers should pay for changes that they ask for. EDA vendors should LISTEN to their customers and give them products they request, and the customers should pay when the vendors respond appropriately. And any new, unasked for feature should be bullet-proofed, adequately explained and supported by the vendors.

]]> By: John Eaton http://theasicguy.com/2008/07/02/one-one-what-would-you-pay/#comment-107 John Eaton Thu, 03 Jul 2008 03:46:49 +0000 http://theasicguy.com/2008/07/02/one-one-what-would-you-pay/#comment-107 I’d like to know what you (EDA vendors and customers) think about this: 1. Should customers pay more for EDA tool enhancements or should they be part of the tool “support”? 2. How do you decide what is an “update” and what is an “upgrade”? Harry, Tool support covers a lot of ground. If the customer wants to have the support engineer read the manuals to him then you should charge for that. You shouldn't charge the customer when they find bugs in the tools. You should charge for training and adding new features but you should not charge for supporting new operating systems when you drop support for old ones. John Eaton I’d like to know what you (EDA vendors and customers) think about this:

1. Should customers pay more for EDA tool enhancements or should they be part of the tool “support”?
2. How do you decide what is an “update” and what is an “upgrade”?

Harry,

Tool support covers a lot of ground. If the customer wants to have the support engineer read the manuals to him then you should charge for that. You shouldn’t charge the customer when they find bugs in the tools.
You should charge for training and adding new features but you should not charge for supporting new operating systems when you drop support for old ones.

John Eaton

]]>