²ÝÁñÉçÇø

It¡¯s no secret that the cloud delivers high availability, reliability, scalability, performance, and affordability that most companies struggle to match with on-prem chip design solutions. However, concerns around security, predictability, cost, and ease-of-use have impacted cloud adoption among IC design teams. To overcome systemic complexity and constraints of power at higher performance while ensuring quick time-to-market, the time has come to look at the cloud pragmatically as an enabler of progress ¡ª one that is both undemanding and flexible.

With today¡¯s market conditions, innovative, cloud-oriented chip design solutions are needed to support the sky-high performance and computing demands from both hardware and software. But just how much IC hardware is ¡°made in the cloud¡±?

Read on to learn about the top ways that the cloud can support an existing on-prem strategy, enable large and small enterprises to manage cost and capacity more effectively, and offer unparalleled security for valuable semiconductor IP.

No. 1: IC Design Teams Need Flexibility Now to Meet Tomorrow¡¯s Challenges

For many organizations, on-prem development feels safe (like a lukewarm pool). Even though they recognize that it has limitations, moving to a new system such as the cloud looks like an unsettling jump. While this is perfectly understandable, tepid conditions are rarely conducive to innovation.

The onset of the SysMoore era means increasing systemic complexity and hyper-convergent design flows, calling for exponentially more compute and established electronic design automation (EDA) resources. In addition, as design tools and workflows become more automated and integrated with artificial intelligence (AI), design space exploration and verification will inevitably require increased and flexible access to these resources.

Going forward, restrictions and costs of a rigid corporate on-prem system will become much more apparent. Cloud service providers offer a way forward with the scaled high-performance computing (HPC) infrastructure, availability, capacity, and cost-effectiveness to manage these growing workloads comfortably and confidently.

No. 2: Balancing On-Prem vs. On-Cloud IC Design

Something to remember when considering cloud adoption for IC design is that it does not have to be a binary choice between an on-prem and a cloud environment. It isn¡¯t a rejection of the tried-and-tested past for an unknown future.

The economics of shifting methodologies is not always tied to making the most of cost. Even if your organization is large, your teams can start small by using the cloud for set tasks to explore opportunities for productivity and innovation without going all-in. Taking a one-workflow-at-a-time approach, or even a one-tool-at-a-time approach, enables you to get a feel for the environment and its benefits as well as potentially freeing up capacity in a constrained on-prem estate.

The bottom line is that not all workloads need to move. With hybrid optionality, the cloud lets you determine the balance that will enable you to work in the most agile way.

No. 3: Predictability vs. Scalability

On-prem teams typically worry that the potential for unlimited capacity in the cloud will cause costs to spiral. This is a legitimate fear and a risk that must be managed. Yet, on-prem deployments can become unwieldy fast: once you¡¯ve paid for a certain capacity, you can¡¯t simply dial it back, and maintaining capacity on standby is expensive.

With multiple engineering teams sharing on-prem resources, it falls on someone to anticipate demand and set capacity accordingly. Even with a wealth of historical data, forecasting has a high chance of failure. Getting it wrong risks either disrupting the product roadmap or overspending.

Smaller businesses need to manage their finances with extra care, even if their forecasting procedure may be less complex. Instead of channeling resources into building their own architecture, which includes hardware with a limited shelf-life, it makes more sense to adopt a pay-as-you-go¡ªor grow¡ªmodel that extends to IC design. This setup makes it possible to grow consumption to meet demand and flex capacities within budget constraints, paying only for what you use. The key is not losing sight of that budget and managing cloud capacity accordingly. In short, the beauty of the cloud is that all the costs associated with running a job can be accounted for on a single OPEX line¡ªin other words, a CFO¡¯s dream.

No. 5: All Roads Lead to Rome or Many Paths to the Cloud

IC design flows are complex and moving them to the cloud from a legacy on-prem model does require data preparation, compute planning, and most likely some re-architecting of the workflows to make them cloud-ready. You will also need to decide where to run the interactive elements of the workflow, such as debug. While the process will be new, the benefits in terms of compute power, scalability, and parallelization more than justify the effort.

There are various options for establishing a working cloud model for IC design. A bring-your-own-license (BYOL) model lets you use your existing on-prem licenses with your chosen cloud provider, while a bring-your-own-cloud (BYOC) model caters to users who have already established cloud capabilities with a provider and whose capacity demands fluctuate.

Another option is a software-as-a-service (SaaS) environment, which absorbs the complexities of the cloud such as setup and running costs. Lastly, a hybrid approach enables you to meet peak demands by bursting capacity into the cloud while running fewer portable workloads on-prem. Choosing the best option depends on the size of your organization, the extent of on-prem investment, and the scale of your workflows.