common licensing following mergers and acquisitions
DESCRIPTION
by Behshad Rejai, Director of Software Engineering, Synopsys Presented at SoftSummit 2010TRANSCRIPT
The Fast Track to CommonThe Fast Track to Common Licensing Following an
M&AM&A
Behshad RejaiDirector of Software EngineeringDirector of Software EngineeringSynopsys
Agenda• About Synopsys • Need for Acclimation• Need for Acclimation • Licensing Acclimation Process • Benefits• Benefits • Summary
About Synopsys
• An EDA Company Foundedin1986in1986
• Large, diverse, worldwide customer base
System Design
customer base• ~$1.3B Annual Sales (2009)
Functional Verification
Synthesis
• ~6,000 employees• ~ 65 offices and design y
Physical Implementation
Manufacturing Prep
gcenters worldwide
Manufacturing Prep.
IC Test
What Is EDA?
Designing a chip is the task of figuring out how toDesigning Designing a chip is the task of figuring out how to make the chip do what you want it to do
Designing Chips
Today’s chips have millions of gates and have feature sizes that are incredibly smallComplexity
Without automation, this task would be impossibleAutomation be impossible
EDA = Electronic Design AutomationEDAEDA
Synopsys Strategy - Complete SolutionS t
IP IP & Systems& SystemsSystems
Algorithms DesignWare IPPrototyping Synplify FPGA
Discovery Galaxy
VerificationVerificationDesignDesignVCS
MM
PIC
E
DesignCompiler
CustomDesignereT
ime
VerificationVerificationDesignDesignCustomSim
VM
HS
P
IC V lid t / St RC
ICCompiler
Designer
Prim
e
ManufacturingManufacturing
IC Validator / StarRC
ManufacturingManufacturingManufacturingProteus Litho YieldExplorerSentaurus TCAD
Synopsys Family Tree
ArchPro‘07
Sandwork ‘07
Synplicity ‘08
CHIPit ‘08 MIPS
MOSAID chip IP ‘07 TeraRoute’09
Gemini Design
VaSTSystems ‘10
CoWare,
ZeroSoft, Inc. ‘10
Synfora Nusym
Virage Logic ‘10
ADA ‘04Accelerant ‘04ISE ‘04 Monterey ‘04Progressant ‘04Virtio ‘06
SigmaC ‘06
TriCN ‘05
Sa d o 0 C t 08 SAnalog Business
Group ‘09
Ge es gTechnology
‘09
Co a e,Inc. ‘10
Sy o a‘10
usy‘10
InnologicA t! ‘02
inSilicon ‘03Numerical
T h l i ‘03
Leda Inc ‘04 iRoC SA ‘04Cascade ‘04
Nassda ‘05HPL ’05
Apteq ‘99
Stanza‘99
Leda SA ‘00 VirSim ‘00
The SiliconGroup ‘00
C LevelDesign ‘01
gSystems ‘03Avant! ‘02
CoDesign ‘02
Technologies ‘03
Qualis, Inc. ‘03
NihonSynopsys ‘95
Arkos ‘95
EPIC ‘97Viewlogic ‘97
Systems Science ‘98
Apteq 99Gambit
‘99 Smartech ‘99 Everest Design ‘98
Advanced TestCovermeter ‘99Silicon Architects ‘95
FoundingOSI ‘86 Zycad ‘90
IPO ’92Compiled Designs ‘93 Logic Modeling ‘94
CADIS ‘94Arcad
‘94
Technologies ‘97
Challenges of a Large Family
Each family member is unique!
• Visible to Customers• Sales, Marketing, etc.
• Not Visible to Customers• Software Development
• Software Installation • Licensing
process• Development Tools
Quality management • Bug Reporting & Tracking • Release Model
Etc etc etc
• Quality management • Infrastructure • Etc., etc., etc. • Etc., etc., etc. Etc., etc., etc.
Need for Acclimation
Interoperability and consistency p y yamong products is a must Systems
Algorithms DesignWareIPPrototyping Synplify
FPGA
• Predictable and consistent behavior across all products improves customer satisfaction
Discovery
VCS
M
Galaxy
CE
DesignCompiler
CustomD iTi
me
Tim
e
customer satisfaction
• Proven process and technologyCustomSim
VMM
HS
PIC
I CIC Validator / StarRC
ICCompiler
Designer
Prim
eTP
rimeT
• Proven process and technology drives down the cost of operation and support
Manufacturing
Proteus Litho YieldExplorerSentaurus TCAD
Scope of Acclimation
• Sales and Distribution ChannelsSales and Distribution Channels• Product Marketing• Order Management Infrastructure
.
.
.
g• Bug Reporting and Tracking• Global Support Channels.
• Product Installation • Product Release Model• Licensing
Synopsys Licensing Objectives • Best-in class customer support
• 24/7 365 days license server up time24/7, 365 days license server up time• Minimum/ zero impact to product usage due to licensing
• Consistent licensing behavior among all products• Pooling, Queuing, Heartbeat, etc.g, g, ,
Licensing Acclimation Goals
• Synopsys Business Needs • Customers’ Needs • Single channel for license key
retrieval – SmartKeys• Single system for saving
• Simplified licensing infra-structureSi l li dSingle system for saving
customer data • Single support channel -
SolvNet
• Single license server and license file for all products
• Serve keys to new versions SolvNet• Standard licensing infrastructure
• License daemon, key file, versioning scheme etc
yof products as well as products released prior to the acquisition
versioning scheme, etc. q
Challenges
I t i iti th li iArchPr Synplic
MOSAI Tera
VaST
ZeroS
VirageLogic • In most acquisitions the licensing
infrastructure is completely different • Key file generation, retrieval, and inSilic
ADA ‘0
Accelerant ‘04
ISE ‘04
Monterey ‘04Leda
Inc iRoCSA
Cascad
Progressant ‘04
Nassda
HPL
Virtio‘06
SigmaC‘06
TriCN‘0
hPro
‘07 Sandwork‘07
Synplicity ‘08 CHI
Pit ‘08
MIPSAnalog
Business Group ‘09
SAID
chip IP ‘07
TeraRoute
’09 Gemini
Design
Technology
‘09
TSystems ‘10
CoWare,
Inc.
‘10
oSoft, Inc
. ‘10
Synfora
‘10
Nusym‘10
Logic ‘10
delivery • License key encryption scheme • Licensing behavior (queuingNihon
Synopsys EPIC ViewlogApteq
Gambit‘99 Smar
Stanza‘99
Leda SA ‘00
VirSim ‘00
The SiliconGroup ‘00
Everest
C LevelDesign
‘01
Innologic
Systems ‘03
Avant! ‘02
CoDesign‘02
on ‘03NumericalTechnologies ‘03
Qualis, Inc. ‘03
04‘04 ‘04e
‘04‘05’05
05
• Licensing behavior (queuing, pooling, heartbeat, etc.)
FoundingOSI ‘86Zycad ‘90
IPO ’92Compiled
Designs ‘93Logic
Modeling ‘94
Synopsys ‘95
CADIS ‘94
Arcad
‘94
Arkos‘95
‘97g
ic ‘97Systems Science
‘98
q‘99
‘99 Smartech‘99
Everest Design ‘98
Advanced Test
Technologies ‘97
Covermeter
‘99
Maintenance of the acquired companies’ licensing infrastructure for several years is not scalable and operationally impractical y p y p
Licensing Acclimation Requirements • Single Key Generation and Retrieval
• Ability to issue keys for legacy versions of the acquired products y y g y q p
• Single License Server • Server keys to new and legacy versions of the acquired products• Support legacy versions of the acquired products for several years
• Synopsys• Unacceptable to provide two sets of license keys (no double dipping)!Unacceptable to provide two sets of license keys (no double dipping)!
• Customers• No impact to product usage
Licensing Integration Solution • Partnered with Flexera Software to develop CVD
• Combined Vendor Daemon
• CVD consolidates several license daemons into one• Enables license keys to be used for pre-acquired and new• Enables license keys to be used for pre-acquired and new
versions of the products • Enables a single, combined license file for products from
multiple acquisitionsmultiple acquisitions
• CVD was released in 2006
• Fully supported by Flexera Software
A 4-Step Acclimation Process
41 2 3 41 2 3 time
Acquisition:Change license key
Release single license daemon and key file
Remove support for legacy products (complete transition
Release 1st feature release usingChange license key
delivery processdaemon and key file products (complete transition
to Synopsys Licensing)release using
Synopsys SDK
Step 1: Acquisition – Change license key delivery process
Step 2: Release Combined Vendor Daemon (CVD) that supports acquired products
Step 3: Release 1st feature release of acquired products using Synopsys SDK
Step 4: Remove support for legacy products in key file
Step 1: Change license key delivery process
Synopsys SmartKeys
Pre-acquisitionSynopsys SmartKeys
Synopsys FLEXlm
License keys for acquired products retrieved via y p y
Daemon Daemon SmartKeys
Customer
Synopsys Products
Products
Step 2: Release CVD to support acquired products
Synopsys Acquired Synopsys Daemony p y
Daemonq
Daemon Daemon
Single license file and daemon including products released prior to acquisition
Synopsys Products
Acquired Products Synopsys
ProductsAcquired Products
Customers of the acquiredCustomers of the acquired company must upgrade their license server
Step 3: Release 1st feature release of acquired products using Synopsys SDKproducts using Synopsys SDK
Synopsys Daemon
License key supports both new and legacy versions of acquired products
Legacy Release of Acquired g y qProducts
Products of the acquired company release with Synopsys
Synopsys Products New Release of Acquired Products
release with Synopsys licensing SDK
Customers don’t need to upgrade their license server;Products upgrade their license server; only the key file
Step 4: Remove support for legacy products in key file
Synopsys Daemon
in key file
Legacy Release of Acquired dProducts
Implemented only when customers stop using the pre-acquisition versions of the acquired productsSynopsys Products New Release of Acquired
Productsthe acquired products
Licensing Acclimation Benefits
• Synopsys • Customers• Reduced cost of operation• Reduced cost of support
• Cost savings in terms of hardware and personnel to manage license server key
• No double licensing • Smooth and seamless
transition from legacy
manage license server, key files, etc.
• Improved end-user licensing itransition from legacy
daemon to Synopsys licensing
experience• No impact to product usage
Summary
• CVD project was successfully rolled out in 2006• Consolidated several license daemons into a single license serverCo so da ed se e a ce se dae o s o a s g e ce se se e
• All Synopsys customers use this functionalityy p y y• 1000s of installations of CVD daemon
• Acquired products migrate to CVD 1 or 2 releases after acquisition
• Licensing acclimation process proven to be very efficient
• Significant benefit to our customers and Synopsys
Backup slides
Overview of License Acclimation Process
Step 1: INCREMENT Spice-Works sandwork 2007.12 31-jan-2008 10000 ED373103EDEAF5DBFDAB \VENDOR_STRING=Spice-Work SUPERSEDE ISSUED=18-jun-2007 \SN=RK:3149-0:150665:443965 START=18-jun-2007 SIGN=ED373103EDEAF5DBFDABSN RK:3149 0:150665:443965 START 18 jun 2007 SIGN ED373103EDEAF5DBFDAB
Step 2: INCREMENT Spice-Works snpslmd 2007.12 31-jan-2008 10000 VENDOR_STRING=Spice-Work \SUPERSEDE ISSUED 18 j 2007 SN RK 3149 0 150665 443965 \SUPERSEDE ISSUED=18-jun-2007 SN=RK:3149-0:150665:443965 \START=18-jun-2007 AUTH={ sandwork=( SIGN=ED373103EDEAF5DBFDAB) }
Step 3: INCREMENT Spice-Works snpslmd 2007.12 31-jan-2008 10000 VENDOR_STRING=Spice-Work \SUPERSEDE ISSUED=18-jun-2007 SN=RK:3149-0:150665:443965 START=18-jun-2007
\AUTH={ snpslmd=( LK=AD3C73103EDEAF5DBFDCB) \
d k ( SIGN ED373103EDEAF5DBFDAB)sandwork=( SIGN=ED373103EDEAF5DBFDAB)
Step 4: INCREMENT Spice Works snpslmd 2007 12 31 jan 2008 10000 VENDOR STRING=Spice Work \Step 4: INCREMENT Spice-Works snpslmd 2007.12 31-jan-2008 10000 VENDOR_STRING=Spice-Work \SUPERSEDE ISSUED=18-jun-2007 SN=RK:3149-0:150665:443965 START=18-jun-2007
\AUTH={ snpslmd=( LK=AD3C73103EDEAF5DBFDCB) }