Please enable javascript in your browser to view this site!

ISO 26262 Compliance In An IP Based Development Flow

ISO 26262 Compliance In An IP Based Development Flow

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

There are many advantages to managing your design development activity in an IP-centric methodology. Optimally partitioned designs, where each block is treated as a reusable, self-contained IP with versioned dependencies on other blocks allows teams to be significantly more lean, agile, and flexible.

In addition to making the design process itself more efficient, an IP-centric methodology also allows users to attach relevant metadata to each IP. This metadata - engineering details, bugs, requirements, and ISO26262 compliance information - is as integral to an IP as its design files and dependencies.

ISO26262 compliance can be demonstrated using a survey designed by a compliance expert or team, and filled out by the design expert. These surveys and their responses are then used to determine the compliance or fitness of a particular part (or IP in this case) for an application that needs to meet certain functional safety (FuSa) standards.

This paper details a process to simplify the FuSa process for an ISO 26262 compliant flow for semiconductors by showing how templates can be used to automate the survey and response components of the FuSa process.



Design Partitioning with Percipient

Design Partitioning with Percipient

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

Semiconductor designs are most efficiently managed as related sets of functional blocks, and significant benefits can be achieved by fully aligning the overall development flow with this in mind.

Percipient enables users to abstract each functional block to a special data object, called an IP.  By abstracting to the IP level, powerful top down flows that simultaneously maintain a real-time connection to the lowest level design data are made possible.

This paper describes best practices for optimally partitioning designs using an IP management system that provides full traceability while removing any overhead burden from the end user.



Creating an IP

Creating an IP

Creating an IP - Watch the video to learn more

IP Types

IP Types

IP Types - Watch the video to learn more

Accelerating Innovation in Semiconductor Development (a Siemens-Methodics Perspective)

Accelerating Innovation in Semiconductor Development (a Siemens-Methodics Perspective)

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

PLM systems help businesses run their entire operation by creating an environment where all product data and metadata can be organized, accessed, and analyzed.  Historically, PLM systems came from mechanical CAD companies and were intended to combine part management and design process information, a relatively static environment.

In contrast, semiconductor design is a highly dynamic, iterative process that requires instantaneous access to quickly evolving data.  In order to meet time-to-market demands and confront the exponentially growing costs of semiconductor fabrication, companies have adopted intellectual property (IP) reuse to streamline semiconductor development.  By assembling designs made up of existing IP, they can reduce the time of development, and maximize the investment in the development of these IP blocks.


To enable this IP-reuse design methodology, companies must have an IP lifecycle management (IPLM) system that understands the highly dynamic nature of semiconductor development environment in addition to a more traditional PLM system.

By combining a best-in-class PLM system with a best-in-class IPLM system, a “digital thread” can be created that starts during product ideation and definition of requirements, and traces all the way through the semiconductor design process. It can then continue into manufacturing, and to sales and support, creating an environment where all the important information is interlinked and tracked.

In this way, requirements from the product ideation process can be linked to semiconductor IP, creating a traceable link that shows the specific product requirements that are met by that IP. During semiconductor verification, functional coverage results at the IP level can then be tracked and related back to the IP.  Companies that must achieve Functional Safety (FuSa) standards compliance, such as ISO26262 for the automotive Industry, can do so while, at the same time, reduce their costs by maximizing IP reuse and reduce time-to-market.


This white paper describes how a semiconductor company can benefit from using a best-in-class PLM solution integrated with a best-in-class IP management solution to achieve these goals.

HIGH-AVAILABILITY ARCHITECTURE FOR ENTERPRISE IPLM

HIGH-AVAILABILITY ARCHITECTURE FOR ENTERPRISE IPLM

About this Whitepaper

Addressing the need for 24/7 availability for infrastructure in an Enterprise IPLM environment.

Content and Organization

Information provided in this document is organized in the following parts: • The Need for High Availability in Enterprise IPLM Systems
• ArchitectingPercipientforHA

Intended Audience

The business process owners supporting product management, design engineering, program management, product planning, product master data management, and release operations will all have a stake in the subjects discussed in this white paper. Information technology professionals can use this document as a roadmap for reducing system overhead costs, consolidating systems, eliminating integrations, and reducing system support requirements.

AN IP-CENTRIC APPROACH TO GIT BASED DEVELOPMENT

AN IP-CENTRIC APPROACH TO GIT BASED DEVELOPMENT

About this Whitepaper
How to establish an IP-Centric methodology in a Git workflow.

Content and Organization

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

Information provided in this document is organized in the following parts: • IP-Centric Design Methodology
• Working with a Git IP
• Restrictions on Git Repositories

Intended Audience

The business process owners supporting product management, design engineering, program management, product planning, product master data management, and release operations will all have a stake in the subjects discussed in this white paper. Information technology professionals can use this document as a roadmap for reducing system overhead costs, consolidating systems, eliminating integrations, and reducing system support requirements.

Putting the “I” in PLM

Putting the “I” in PLM

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

The complexity of today’s semiconductor devices rivals the complexities of systems design in other industries, and the semiconductor industry can learn a lot from the evolution of systems design. One of the advancements of the past two decades has been the adoption of product lifecycle management (PLM) solutions to manage system designs from ideation through end of life.  PLM systems help businesses run their entire operation by creating an environment where all product data and metadata can be organized, accessed, and analyzed.  PLM systems allow information to be made available immediately and consumed in formats that make sense for each stakeholder.   However, once the data is in the PLM system, it is generally stabilized and static in nature.

In contrast, semiconductor design is a highly dynamic, iterative process that requires instantaneous access to quickly evolving data. This data needs to be rapidly assembled and integrated into highly specialized design and verification tools.  Traditional PLM systems are not designed to handle the "high velocity" nature of this changing data.

In order to get the best of both worlds, the ideal solution is for a best in class PLM solution to interface with a best in class semiconductor IP lifecycle management (IPLM) solution.  Semiconductor companies can then reap the benefits of both an optimized semiconductor IP-Centric and IP-Reuse design methodology in conjunction with streamlined and cost-efficient business processes.

Percipient: Taming Git for the Enterprise

Percipient: Taming Git for the Enterprise

 CLICK TO DOWNLOAD

CLICK TO DOWNLOAD

Git brings significant flow improvements to software and digital design, but these improvements come with heavy costs in increased complexity. This increased complexity is driven by the practical limits on Git repository sizes, leading to a proliferation of independent repositories, which in turn puts a greater burden on system integration and tracking.  The question is whether Git’s benefits justify the resultant increase in complexity and risk.  Percipient, the IP Lifecycle Management (IPLM) platform from Methodics, eliminates the trade-off; enterprises can leverage the power of Git and simplify their integration flow at the same time.

Samsung Advanced Computing Lab (ACL)

Samsung Advanced Computing Lab (ACL)

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

The ACL design build environment requires 1,000’s of runs consuming 1,000’s of CPU hours and many Terabytes of data on a continuous basis. These numbers are expected to continue to increase as ACL grows. Having top of the tree clean workspace is key requirement for build infrastructure where workspaces are created and deleted very frequently and the average life of work spaces was less than a week.

Enabling Hierarchical IP Reuse using Private Resources

Enabling Hierarchical IP Reuse using Private Resources

Introduction

 CLICK TO DOWNLOAD

CLICK TO DOWNLOAD

As design complexity increases and design cycles shrink, IP reuse has become a critical component of success for hardware teams. However, these two realities are often at odds with each other - complex IPs are hard to create, test and reuse. On the other hand, SOCs need to be able to incorporate more and more complex IPs from diverse sources in as seamless and low effort manner as possible.

One way to manage complexity is break down IPs into simpler components and build the complex pieces up hierarchically. While this is good for managing complexity, it introduces a host of issues that need to be handled by the IP management system to allow for hierarchical reuse of IPs.

Percipient introduces the concept of Private Resources to help ease this burden and allow teams to make meaningful progress in IP reuse.

Improving Time-To-Market With The Right IPLM Solution

Improving Time-To-Market With The Right IPLM Solution

 CLICK TO DOWNLOAD

CLICK TO DOWNLOAD

In the increasingly competitive semiconductor market, getting a product out on time is of critical importance. Missing market windows by even a few months can mean the difference between being highly profitable vs breaking even or even losing millions in revenue. In this scenario, it is of critical importance for teams to be able to reuse existing, proven IPs to reduce development time, complexity and cost. An IPLM (IP Lifecycle Management) solution like Methodics’ Percipient is designed to help customers adopt an IP-centric design flow to address this need. To fully capitalize on IP reuse, the IPLM system needs to be built from the ground up to handle the realities and complexities of identifying and reusing IP resources . This white paper discusses one of the key components of Percipient - the Graph Database - that helps the tool achieve its goal of enabling fast and seamless IP reuse

Improving Time-To-Market With The Right IPLM Solution

Improving Time-To-Market With The Right IPLM Solution

Introduction

 CLICK HERE TO DOWNLOAD

CLICK HERE TO DOWNLOAD

In the increasingly competitive semiconductor market, getting a product out on time is of critical importance. Missing market windows by even a few months can mean the difference between being highly profitable vs breaking even or even losing millions in revenue.

In this scenario, it is of critical importance for teams to be able to reuse existing, proven IPs to reduce development time, complexity and cost. An IPLM (IP Lifecycle Management) solution like Methodics’ Percipient is designed to help customers adopt an IP-centric design flow to address this need.

To fully capitalize on IP reuse, the IPLM system needs to be built from the ground up to handle the realities and complexities of identifying and reusing IP resources . This white paper discusses one of the key components of Percipient - the Graph Database - that helps the tool achieve its goal of enabling fast and seamless IP reuse.