Subscribe to EDN

Standards

March 18, 2009

I was once at a standardization meeting many years ago when a friend of mine leaned over and said, “I tend to be against standards, they just perpetuate other people’s mistakes.” I think this is really a criticism of standardizing too early. You can only standardize something once you already know how to do it well.

In many businesses, the winner needs to be clear before the various stakeholders will move. Standards are one way for a critical mass of companies to agree on the winner. For example, Philips and Sony standardized the CD for audio and since it was the only game in town it was adopted immediately by vendors of CD players, the record labels knew which format to put discs out in, the people building factories to make the CDs knew what to make. A few years earlier there had been the first attempt to make videodiscs, but there were three or more competing formats. So everyone sat on their hands waiting for the winner to emerge, and in the meantime everything failed. When everyone tried again a few years later, the DVD standard was hammered out, it was the winner before it shipped a single disk, and the market took off. This was a lesson that seemed to have been lost in the HD-DVD vs BlueRay wars, although by then disks were starting to be irrelevant and downloading and streaming movies is clearly going to be the long-term winner.

EDA is an interesting business for standards. Since you can only standardize something you already know how to do, standards are useless for anything leading edge. By the time we know how to do something, the first batch of tools is out there using whatever interfaces or formats the initial authors came up with. Standardization, of the IEEE variety, lags far behind and serves to clean up the loose ends on things where there are already de facto standards. Also, EDA market expansion is not going to be driven by standards in the way that CDs were. Synopsys won synthesis (as opposed to Trimeter, Silc, Autologic and others) and so .lib and sdc became the standards, not the other way round. If all the other EDA companies had created a competing standard to .lib, nobody would have cared. It is the winningness not the standardization that is important.

Once the first tools are out there for some new technology, all using incompatible formats, then standard wars begin. The market leader wants its standard to become the de facto standard adopted by everyone. It is cheap for them since they don’t need to make changes; it is expensive for everyone else since they need to change their software to read the standard and probably make some internal changes so that their tool’s semantics match those implicit in the standard. Even if an IEEE-style standardization effort takes place, it is too slow. By the time the standard comes out it has often already been superseded by upgrading of the formats by the market leader to accommodate the realities of the process nodes that have come along in the meantime.

Customer behavior is very two-faced too. Every semiconductor vendor will talk about the importance of standards with a long solemn face. Especially their CAD managers. But, at least for their leading edge chips, they won’t put any money behind those statements and they will buy the best tool for the job whatever standards it does and does not support. Designing leading-edge chips is hard enough without worrying about whether some abstract standard is open enough.

Of course, once a market matures then supporting the de facto standard is an important part of “best tool for the job”. When I first started in EDA, Calma still maintained that GDSII was a proprietary standard that nobody else was allowed to read. However, every Calma system shipped with a file describing the format, so I took the legally dubious step of reading that file, and a couple of days later we could read chips into the VLSI Technology layout editor. A layout editor that didn’t read GDSII wasn’t really a layout editor no matter how good it was at editing layout.

So expect customers and EDA vendors going forward to talk a lot about how important standards are. But expect them to produce and buy the best tool for the job and the standard to emerge from the competition for that honor.

Posted by Paul McLellan on March 18, 2009 | Comments (3)

March 18, 2009
In response to: Standards
Free the Code commented:

Paul- you raise some really good points on the dynamics of standards in EDA and in general. I think the biggest misperception by many is the importance of openness vs. adoption. The value of a standard lies in the breadth of adoption both by end-users and by EDA suppliers. Openness in all its forms - open source, standards committees, IEEE, just provide a neutrality and and incentive for adoption, but are no indicator of market adoption or value of a standard. SO if you just look at adoption: A standard supported by all the EDA suppliers but only used by a single customer is useless - one only need look at CFI or DCL (an IEEE standard) to remember this mode of market failure. A "standard" adopted by essentially a single vendor, such as CPF or 'e' may build up a fair body of early end-user support in the short run, if the format or language enables tool capabilities ahead of the broader marketplace. Unfortunately, such standards eventually implode if a more broadly adopted standard can provide 95% of the same capabilities. The best is broadly adopted by both end-users and EDA suppliers. As you point out Paul, this can happen via either defacto codification of an existing format (lef/dfe, .lib, .sdc, Verilog) or through collaborative industry effort (UPF, SystemVerilog, VHDL).


March 18, 2009
In response to: Standards
rlsmith3 commented:

This discussion unfortunately brought my brain back to CFI, the CAD Framework Initiative. That venture lead to lots of effort from Cadence and Mentor but eventually yielded no unifying framework. A decade later we have Open Access (OA). It still doesn''t feel to me that this will get sufficient critical mass either. For file formats, the winner will dictate the standards. Frameworks would require the open source model, but it is not clear if EDA is a biggest market to benefit from that model. There just won''t be enough volunteers to make it work as there are for open sources such as Linux or Joomla.


March 18, 2009
In response to: Standards
SteveM commented:

Hi Paul: your post is a good description of the standards dynamic. The best standard is one which was designed by a single architect/organization and is released in a timely fashion as an open source controlled format (lib, sdc, def/lef, saif, SystemC, OA ...). Secondly committee based standards (Accellera, IEEE) with strong technical leads and a couple dominate leading companies (System Verilog, PSL). Worst is a standards fight from the outset with stalking stalwarts and a host of customers complaining about standard overlap (CPF vs. UPF). This type of environment forces compromises and committee politics which disrupts convergence based on technical merits. The most hypocritical company is TSMC who loves to talk about ''standards'' which are captive to just their foundry, yet all the EDA vendors are compelled to support them. A proprietary standard ... what an oxymoron! Cadence''s CPF was also a joke as they positioned it as an open standard, but excluded the 3 other EDA companies. Even under intense customer pressure they insisted on keeping their CPF party closed thus causing the overlap. Unfortunately my urging to standardize a power format much before CPF/UPF was summarily ignored by some marketing pinheads, and the result is an ugly mess. It should be a lesson for all, don''t compete based on formats, compete on the algorithms and software implementation, and the industry will grow faster. Luckily the DFM tools space has been unveiled as a marketing sham, otherwise the state of standards with BRION correction and TSMC''s proprietary hooks is a deep tarpit. Also watch the analog space as PCELL''s gets opened up for competing custom solutions.

POST A COMMENT
Display Name
captcha

Before submitting this form, please type the characters displayed above. Note the letters are case sensitive:

Advertisement
Advertisement
Advertisement
About EDN   |   Site Map   |   Contact Us   |   Subscription   |   RSS
© 2012 UBM Electronics. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy

Please visit these other UBM Canon sites

UBM Canon | Design News | Test & Measurement World | Packaging Digest | EDN | Qmed | Pharmalive | Appliance Magazine | Plastics Today | Powder Bulk Solids | Canon Trade Shows