Download the latest issue of the Electronic Systems Design Engineering
and subscribe to receive future issues and the email newsletter
Published on June 07th, 2011
Everyone talks about innovation. Startup companies are the most visible vehicle for innovation. But they’re also the most risky, with a one-in-ten chance of modest success. Less visible is the innovation that constantly must occur in fully formed, large companies if they are to continue to succeed. System-Level Design (SLD) talked with the three major EDA companies about the challenges to innovation: Michael McNamara, vice president and general manager of system-level design at Cadence; Serge Leef, VP, new ventures GM, System-Level Engineering Division at Mentor Graphics; Michael Jackson, VP of engineering, Physical Design, Synopsys Inc.
SLD: How do you foster innovation inside an existing, successful company? How do you create new products inside a large and often bureaucratic commercial organization?
McNamara: A good example was the C-to-Silicon product line, a high-level synthesis tool. This product started inside of Cadence labs back in 1998, originating from a project called Metropolis with UC Berkeley. This project focused on the system-level development space and was the genesis of platform-based design. The idea was that you would have a single platform that you then customize for different usages. A modern example is today’s Droid phones that use TI’s OMAP to incorporate an ARM process, graphics, Bluetooth, and other radios into a collection of IP that is aggregated together. Others start with this platform to add their unique innovation and wham! In six months, you have a cell phone.
In 2002, an internal design team was exploring the idea of high-level synthesis. The idea was that a C-code program running a microprocessor could serve as a specification for what would need to be done by the hardware device. In those days, we had a silicon compiler, but needed to create a register-transfer-level (RTL) language as an in-between language. It was too hard to go all the way from C to transistors.
Interestingly enough, there was a product in the late ’90s called Behavioral Compiler, but it turned out to be a failure. The promise of high-level synthesis was huge, but it just wasn’t happening. Finding out why was the first goal of our research task group? and is a key difference between research and implementation (or product) groups. Research labs can step back and examine why things aren’t working as expected. We started by interviewing some two dozen companies that were doing various levels of high-level synthesis.
Our internal R&D group asked them why high-level synthesis wasn’t working. Those interviews identified a couple of issues. One was a manufacturing challenge related to correcting design issues (i.e., if RTL is automatically generated, how do you accommodate changes like specification or place-and-route changes?).
Another issue identified by the R&D group was the challenge of reuse. Designers really want a way to specify how the C-code program would be implemented in any given design. One example is the use of decoding and compression algorithms for video movies for different end-user applications--from smartphones to laptop computers and large home-entertainment theater systems. You are using the same exact algorithms, yet the implementation of each requires a different set of power, performance, and quality requirements. Quality issues might be that the smaller screen sizes on a smartphone don’t need the same display resolution as a home theater.
That was the nature of the research part of this project. The researchers gathered a bunch of data, then formulated three or four ideas that they believed constituted the major roadblocks for the adoption of this technology. Around this time, Cadence had serendipitously purchased a high-level synthesis tool from a company called Get-to-Chip. Suddenly, the researchers at Berkeley labs had a high-level synthesis tool that they could play with and try to implement some of their ideas to address the technology roadblocks, like ECO implementation and the separation of constraints from design.
The Get-to-Chip tool read and generated Verilog, but it didn’t support C or C++ or SystemC. But the researchers could use this tool to develop a prototype. The first step was involved research to identify an opportunity. The second step involved building a prototype.
SLD: Are there other ways in which large companies try to innovate new ideas?
Leef: I basically have a non-traditional venture portfolio, whereby I attempt to identify opportunities in markets or application domains that are adjacent to Mentor’s products, technologies, or know-how. In other words, I’m looking for adjacent places where our current assets can be leveraged. There are basically four operational models that we recognize, which I’ll list from the least to the most expensive.
The least expensive is adaptation because it augments existing horizontal products with domain-specific libraries, design examples, and application notes to create a vertical product. One example would be SystemVision, a horizontal megatronic simulator that is augmented with models applicable to implantable medical devices.
The next least expensive approach is to repurpose a relevant in-house technology and retarget it to a different domain. For us, an example of an in-house technology would be algorithm creation and implementation. We have a good understanding of optimization techniques in the EDA space. We are retargeting this technology to a different, but adjacent domain in the automotive electronic-simulation market.
Let me explain. There is an elaborate cost function in vehicle distributed computing that lends itself well to EDA place-and-route optimization technology. Such technology would be useful, but as yet not fully applied to automotive designer.
A third approach to adjacent markets is called incorporation. Here, we identify useful third-party technology companies that can be plugged into one of our existing products. Of course, such plug-ins would need to drastically improve or alter the opportunity side for whatever it is that we have. For example, consider the development of virtual prototypes, which typically include models of microprocessors, microcontrollers, and DSP cores. It is quite expensive to develop these models organically. Let’s just say, for kicks, that there is a third-party supplier of inexpensive, fast instruction-set simulators. We might acquire a license to such a technology, then snap it into multiple simulation-technology environments within our products. We would incorporate that technology as opposed to a standalone business acquisition.
The last and most expensive approach would be development. In this situation, we have some unique know-how, but that is it. In those cases, we’d invest in R&D to create something new based purely on our understanding of the problem and requisite technologies needed to solve it.
SLD: Would Calibre be an example of an R&D project?
Leef: Calibre is exactly such a case. But Calibre didn’t come through any kind of structured venture portfolio management. Instead, Calibre was truly a Skunkworks exercise, where a bunch of people worked on their own time for long periods without management noticing what they were doing. So they succeeded against organizational forces rather than because some infrastructure was in place to support the development.
What I am trying to do is create an environment where things like Calibre can grow and be nurtured in a repeatable way, as opposed to spontaneous like what happened with the actual Calibre.
Overall, we tend to view our innovation efforts in the same way as venture capitalists (VCs). Currently, I have projects that are in the A, B, C, and D stages of funding and development – similar to series funding in the VC world (see the Figure). Basically, we have a Pre-A stage, in which we explore a concept to decide if a business plan is warranted. In Stage A, a specific market and product are identified and we develop a prototype. Stage B consists of creating a commercial-strength product and engaging with early customers. Stage C is where we deploy the product to a broad set of customers and hopefully generate revenue.
SLD: How is R&D funded within a large company?
Jackson: We fund new technology and product development in our business units as opposed to an independent R&D organization. We have had many successful innovations doing this. Some recent examples include the creation of a new router (Zroute), test compression (DFTMax), RTL exploration (DC Explorer), and a constraint analyzer (Galaxy Constraint Analyzer).
SLD: Do you favor internal development or acquisition as a way to innovate technology?
Jackson: Generally, we rely more on home-grown development. This is especially true in areas where we are creating a replacement product or extending a product to address an adjacent area. Home-grown development is also used for new product areas, but acquisition can also play a role here.
John Blyler is the Editorial Director of Extension Media, which publishes Chip Design and Embedded Intel® Solutions magazine, plus over 36 EECatalog Resource Catalogs in vertical market areas.