IP Lifecycle Management
The IP Lifecycle domain eliminates costly product development errors by enabling improved cross-functional product design, manufacturing planning and performance simulation. Within the IP Lifecycle domain are the following sub-processes: IP Work-in-Progress, IP Asset Release, and IP Classification and Re-Use.
ENOVIA Synchronicity for Synopsys CD
ENOVIA® Synchronicity® for Synopsys CD provides design data management for Synopsys Custom Designer data in Open Access format.
The ENOVIA Synchronicity for Synopsys CD integrates ENOVIA Synchronicity DesignSync Data Manager and ENOVIA Synchronicity DesignSync Central with the Synopsys Customer Designer graphical integrated circuit (IC) design environment recognizing and efficiently managing Synopsys library design data. The Synopsys Customer Designer graphical design environment is modified with the addition of ENOVIA Synchronicity menus and commands. Designers are able to perform automatic checkout and checkin operations without leaving the familiar Synopsys graphical environment, and without having to manage the actual collections of files and directories on disk which represent Synopsys library objects such as schematic diagrams.
EDA Data Awareness - Synopsys Library Recognition
Data awareness is important because data created and modified by Electronic Design Automation (EDA) tools, such as a Synopsys schematic diagram or physical layout, is typically not stored on disk as a single file. Rather, a design object such as a schematic diagram consists of a specific set of files. In order for a Design Data Management (DDM) system to maintain a version history of changes to the schematic diagram, this set of files must be managed as a group. The group of files is also referred to as a “co-managed” set, or “collection object.” These collection objects are stored in a larger directory structure called a “library.” A Synopsys “library” consists of “cells,” and a cell may contain multiple “views,” which are models used for different purposes, such a schematic view, a layout view, etc.
The ENOVIA Synchronicity for Synopsys CD recognizes Synopsys Open Access libraries on disk so as not to confuse them with ordinary directories and files. Collection objects are managed transparently to the end user. So, when a user issues a command to checkout a version of a schematic diagram, the appropriate versions of each of the member files of the collection object are checked out automatically. The member files of the collection are each individually version controlled, and a mapping is maintained between the version of the design object and the versions of the member files which constitute the version of the object. Storage of data in the DDM repository is efficient because only member files of a collection which are modified in an edit operation are stored in the new version of the design object. And because the design object is managed as a “collection,” the tool prevents direct modification to individual member files, which can result in the corruption of the object as a whole.
- By integrating into the Synopsys Custom Designer graphical design environment, designers work in the tools with which they are familiar
- All vaulting operations executed with a thorough understanding of the unique structure of a Synopsys data library
- Manages Synopsys data, along with non-Synopsys project data, letting companies connect to and manage the entire design chain with a unified DDM system
Synopsys Library Recognition and ProcessingSynopsys library directory structures are recognized as such. Users manipulate familiar constructs such as cells or views, while the tool automatically processes the underlying files and directories which comprise data views. Designers need not be concerned with detailed version control bookkeeping which is handled automatically.
Locking Model EnforcedBecause Synopsys design data is binary in nature, a strict locking model is enforced. This prevents the situation in which two designers are making changes to the same version of a cell view, because once the first designer checks in the changes, there is no automated capability to merge the changes of the second designer.
Association with a LibraryWhen libraries are created using Custom Designer, the library is automatically associated with ENOVIA Synchronicity DesignSync Data Manager’s version control system so that any subsequent read/edit access is via the DesignSync revision control repository.
Automatic Checkout and Checkin of Cell ViewsAuto checkout and checkin of cell views is enabled with functions registered with the Synopsys Version Control system. Custom Designer calls the Version Control System before editing (auto checkout) and after editing (auto checkin), which communicates with ENOVIA Synchronicity DesignSync Data Manager. User preferences control whether auto checkout and auto checkin occur automatically, or query the user first.
Status Reporting in the Library ManagerThe Custom Designer Library Manager is modified to include revision control information for cell views including versions, tags, and locking status.
Distributing a Library Across Multiple Data RepositoriesA single library can be distributed across multiple data repositories by using ENOVIA Synchronicity’s module based data storage. Local efficiencies are maximized at each design center because the majority of data transfer activity (checkin/checkout) occurs locally.
ENOVIA Synchronicity GUI and Command Line SupportAlthough most day to day data editing operations are performed from within the Synopsys Custom Designer graphical design environment, DDM operations on Synopsys library data can be performed using either ENOVIA Synchronicity’s GUI or the command line. Multiple libraries can be processed using one command which is not possible from within Synopsys.
The Role of ENOVIA V6 and PLM 2.0ENOVIA Synchronicity for Synopsys CD supports PLM 2.0, product lifecycle management online for everyone, and the ENOVIA V6 values: global collaborative innovation, single PLM platform for intellectual property (IP) management, online creation and collaboration, ready to use PLM business processes, and lower cost of ownership.