MatrixOneMatrixOne

The Data Management SolutionThe Data Management Solution

For OpenAccessFor OpenAccess

April 18, 2005

MatrixOne Confidential 1

Our Customer Base – All OA Enabled

OEMOEM

SemiconductorSemiconductor

ComponentComponentSupplierSupplier

EMS, Foundry & EMS, Foundry & EquipmentEquipment

IP & FPGAIP & FPGA

MatrixOne Confidential 2

Pre-packaged Semiconductor PLM Solutions

Cross-Enterprise Collaboration EnvironmentCrossCross--Enterprise Collaboration EnvironmentEnterprise Collaboration Environment

Enterprise Project ManagementEnterprise Project Management

Design Data Management Design Data Management

IP Reuse &DistributionIP Reuse &Distribution

Design toManufacturing

Design toManufacturing

DesignWin

DesignWin

Product Portfolio Planning

MatrixOne Confidential 3

OpenAccess - Background

• OpenAccess is an open API and reference database for IC design

• Developed and contributed by Cadence• Standardized by

Silicon Integration Initiative (Si2)

• OA 2.0 release (QX’XX) contained initial database and API implementation

• OA 2.2 release (Q4’04) contains major database improvements AND new Data Management plug-in architecture

• Don’t be confused by Si2 releases and Cadence releases.

MatrixOne Confidential 4

OpenAccess for Cadence IC tools - Background

• Release timeline for new versions1. API version released by OA via Si22. Cadence toolset with support for that OA version released3. Data management plug-ins can be

released that support the new Cadence tools

• DesignSyncDFII goal - release in conjunction with Cadence IC tools- Cadence IC5.2.51 release (Q2’05) will support OA2.2 database, but not

DM plug-in system DSDFII will support this as soon as released

- Future Cadence IC tool release will support DM plug-in system DSDFII will support that IC tool release when available

MatrixOne Confidential 5

OpenAccess 2.2 DM Architecture

• OA 2.2 provides for both Version Control (VC) & Data Management (DM) interfaces• DM interface controls the file/directory structure, and identifying what objects are in a

library• VC interface allows simple versioning: checkin/checkout, etc., plus status reporting:

“this file is locked”, etc.

DM product (e.g. DSDFII)

OA V2.2Version Control API

OA Application(e.g. Cadence IC tools)

Data Management API

VC plug-in DM plug-in

MatrixOne Confidential 6

OpenAccess 2.2 DM Plug-ins

Who is providing what?• Cadence providing two reference DM plug-ins:

- FileSys• Supports legacy Cadence library structure• DM plug-in only, no VC plug-in• Version control supported via integration with Cadence’s

GDM system. May not be supported long term.- Reminder: current DSDFII integrates with GDM

- Turbo• New flatter directory structure• Client/server application, with central catalog file, for

performance• DM plug-in only, no VC plug-in• Does not easily lend itself to support of a VC plug-in by

third party DM suppliers, due to naming structure

Library directory structure (FileSys):lib/

cell/view/

master.tagdd.dblayout.oa

Library directory structure (Turbo):lib/

lib.xmld1234/

f5678 (== layout.oa)f5679 (== dd.db)

MatrixOne Confidential 7

OpenAccess 2.2 DM Plug-ins

Who is providing what?

• MatrixOne- Supports a DM plug-in, using our own library

structure• Designed for efficiency and performance, while

remaining “user friendly”• Collection object system retained to ensure data

integrity- PLUS supports VC plug-in to DesignSync- Plugins delivered as part of DSDFII product

• Other DM suppliers?- Unknown

Library directory structure (DMSync):lib/

c23/cell.view.sync.oacell.view.layoutcell.view.dddb

MatrixOne Confidential 8

DSDFII & Cadence/OA 2.2 Support

• DesignSyncDFII will support both of Cadence’s OA DM models- ‘FileSys’ legacy support in DSDFII 4.1+ via GDM system- ‘DMSync’ high performance model available when IC tools support plug-in architecture

• Combined DM/VC plug-in• Support for simple VC-only plug-in to Turbo is TBD

- Desire customer feedback, but may not be possible due to Turbo structure

DS/Turbo VC plugDS/Turbo VC plug--inin

DMSyncDMSyncDM/VC plugDM/VC plug--inin

Cadence IC toolsCadence IC tools

GDMGDM

DSDFIIDSDFII

DesignSyncDesignSync

DS GUIDS GUIdsscdssc

FilesysFilesysDM plugDM plug--inin

Turbo DM plugTurbo DM plug--inin

OA V2.2OA V2.2

TBDTBD

MatrixOne Confidential 9

Performance Effects

• New library directory structure gives:- Fewer files per cellview- Significantly fewer directories for entire library- Fewer DSDFII workspace metadata files (one per directory)

• Possibly will collapse all metadata into one file per library• OA API separating library structure knowledge from application gives:

- Faster access to library contents via metadata (vs directory traversal)- Faster handling of objects in DSDFII due to new collection naming and use of DesignSync

custom type system (CTS)- Potential for “virtual objects” (see later)

• Positive performance impact- Operations driven from knowledge of library contents benefit greatly

• Sparse checkin, listing contents, comparing workspace to server, etc.- Operations working on all library data are helped by overhead reduction

• Savings depend on design data size- The smaller the design data size, the higher the % of time spent in overhead

• Raw design data size is tied to OA DB savings (if any)

MatrixOne Confidential 10

DesignSync/OA 2.2 Potential Timeline

CadenceOA 2.2 ‘Filesys’

release

DesignSync V4.1spX

DesignSync V??

CY 2004 CY 2006?

CadenceOA 2.2 ‘Turbo’

release, including general plug-in support

OA 2.2API FCS

DesignSync V4.0 based prototype

OA 2.2 ‘DMSync’ support

based on CIC release that supports plug-in

architecture

OA 2.2 ‘Filesys’ support

based on CIC 5.2.51