One of the big challenges is that the design team was distributed, with designers at 5 different sites around the world. The collaboration platform for managing all the design data was ClioSoft. The golden repository was at LBNL and was automatically mirrored at all the other sites.
The features that they especially relied upon were:
- low-cost educational licenses
- worldwide access to design data in real time
- revision management (backups, versions, snapshots)
- graphic diff tool to visualize changes in schematics and layout
- simple and flexible administration
- very robust (they never lost any data)
- fast (with the caching, data access the same as accessing local data)
- flexible, allowing all data types to be shared in the same repository, digital and analog design, documentation etc.
- capability to link seamlessly to local design data such as PDKs, IP etc (that was not kept in the repository and was acquired separately at each site).
A large part of the talk is about the chip and the design methodology but there is an emphasis on how the design was organized to allow distributed collaboration and management of a large design. The team is the first to admit that they don't have a secret recipe guaranteed to work for organizing a big geographically distributed design like this. But the design was successful and they point out all the things they did well (and not so well). Of course, any major project needs a disciplined approach to design data management.
ClioSoft's hardware configuration management solutions are seamlessly integrated into the major schematic/layout environments: Cadence's Virtuoso, Mentor's Pyxis, Agilents ADS and both Synopsys Custom Designer and Synopsys Laker. Design data is automatically checked out from within these environments without requiring switching back and forth between the tool being used to get real work done and the design data management interface itself.
The slides for the talk are here (pdf of powerpoint).
<script type="IN/Share" data-counter="right"></script>