Methodics
Methodics

IP Lifecycle Management

The Percipient IP Lifecycle Management (IPLM) solution provides all the capabilities needed to track an IP from its initial requirements to final implementation, though the 4 lifecycle stages as shown to the left.

In the Acquisition stage we are concerned with the creation of the IP. The IP can be bought from a 3rd party IP vendor, it could be reused from an existing IP inside the corporation or it could be designed from new as part of a project. Percipient provides various clients to enable the IP Acquisition phase, including a command line client IDE optimized for users working in Unix or Windows and integrated into Perforce, Git, SVN (and others), a Web based IP-Catalog to enable discovery/reuse of existing IPs and help plan resources as part of the project definition, and a mixed-signal design client integrated into the Cadence and Synopsys analog design environments

Tightly coupled to the IP’s Acquisition is the Qualification process where an IP will have its requirements, defects, quality, performance, and other defining information attached and measured as it matures through project releases. These releases are represented by IP Version objects in Percipient and include a roll up of the design data and the meta-data accumulated by the IP object as it moves through the project milestones.

The required meta-data is gathered from the design tools in the environment and attached to the IP object using the Percipient meta-layer. Custom reports and dashboards are configured to interpret and measure the state of the IP at each release. Fig. 2 shows how the Percipient IP model accommodates these disparate sources of metadata and enables IP tracking through the lifecycle.

Once the IP Version has been Qualified it needs to be Distributed to the various team members that need to interact with it in the system. This is done using the Percipient workspace management platform which includes integrations into industry standard data-management tools such as Perforce, Subversion, Git, and others.

Making the IP available across multiple sites is an important aspect of the distribution platform, as is tracking the contents of user workspaces to maintain the health and consistency of the project environment.

The final step in the IP Lifecycle is to Integrate the qualified IP Version into the project bill-of-materials (BoM). Percipient facilitates this by using hierarchical dependencies to manage the versioned dependency tree. These hierarchical BoMs can be defined via the PiWeb GUI or on the command line and can be self-managing using continuous integration and the Percipient events tracking layer to determine when a qualified IP release is available.

By tracking IPs and their projects from conception/requirements to implementation –  including quality measurements and test-archival and state – facilitates IP-creator to IP-consumer, end-to-end traceability for the enterprise. This is rapidly becoming a requirement across most component based design efforts, especially Functional Safety (FuSa) in the automotive space with the requirements to meet FuSa standards such as ISO26262.

Resources:

For more information on Methodics IP Lifecycle Management solutions, please download the following whitepapers:

Improving Time-to-Market with the Right IPLM Solution

Benefits of IP-Centric Design

Leveraging Single-Source-of-Truth Architecture to Speed Development Times, Improve Design Quality, and Reduce Risk