• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Blogs
  2. Analog/Custom Design
  3. What’s all the Hoopla with PDKs?
archive
archive
Blog Activity
Options
  • Subscribe by email
  • More
  • Cancel
CDNS - RequestDemo

Have a question? Need more information?

Contact Us
IC 6.1
Virtuoso
PDK
Custom IC Design
Process Design Kit

What’s all the Hoopla with PDKs?

31 Mar 2009 • 2 minute read

At a purely technical level, Process Design Kits are fairly innocuous. They are used to enable custom IC design flows. A Process Design Kit (PDK) includes device models, schematic symbols, netlisting procedures and parameterizable cell layout generators. Physical verification rule decks and a parasitic extraction technology file are usually included in the kit. Quite a few of the tools used in custom IC, such as placers and routers, need information about the process technology but not in as much detail as exists in the design rule manual. So the PDK also incorporates a technology file with this information in a form that can be more easily used by these tools.

 

PDK_Blog_01

 

PDKs often receive short thrift from the EDA cognoscenti. They tend to be considered a little mundane and, dare I say it, a bit boring. After all, they are not in the public eye like energy efficiency and low power. They are not on the cusp of the next big wave like RF and mixed-signal. They are just infrastructure. But that’s exactly it. They’re infrastructure. And infrastructure is a powerful competitive advantage.

One of the reasons why infrastructure is so potent is that it is largely invisible, especially if it is intertwined with a business process. Add a new feature to a product, and competitors will see it and be able to respond. Embed it in the infrastructure and no one knows it’s there or how it works. When the iPhone was launched, it was the first of its kind but within a very short space of time, others had produced similar looking products. However, no one has been able to replicate its user experience and delight. Its secret lies beneath its surface where no one can quite place their finger.

Infrastructure also exerts a hold on customers because it can be massively expensive to displace. Once ecosystems get built around a kernel, it becomes very expensive to move customers to something new because it takes a huge amount of energy to introduce and proliferate the new base. It can be done, but you need deep pockets and even more patient shareholders. Take a look at Verizon. To compete head-on with cable, Verizon has invested close to $20 billion1 this decade to lay fiber to the home.

There has been a buzz over the last year or so about re-implementing parts of a PDK in open languages to make them interoperable between different vendors’ solutions. At first glance, the notion has a certain appeal but on reflection one has to wonder whether taking a successful solution, fine tuned through years of extensive usage, and recasting it in a new language is really transformational.

If we want to create breakthroughs for our customers, our thinking has to be bolder, more expansive and more ambitious. What if PDKs were to become smarter? Suppose they could truly link process development, design, manufacturing and test. What could the new opportunities be for optimizing the supply chain and compressing time to market? Infrastructure is too valuable a resource to be relegated to a format. More than just interoperable PDKs, we should really be thinking about intelligent PDKs.

 

Robin Sarma

 

1 – Foust, Dean. “The BusinessWeek 50.” BusinessWeek, 6 Apr. 2009: 37-63.

 


CDNS - RequestDemo

Try Cadence Software for your next design!

Free Trials

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information