Bring up, validate, and operate the CAD/EDA layer cleanly
We support real ASIC environments on dedicated remote infrastructure: Virtuoso, licensing, ClioSoft SOS, PDKs, decks, verification, secure Linux workspaces, queues, migration, documentation, and post-go-live CAD operations. Flow coverage: analog, digital, layout and sign-off.
- Years combined experience
- 25+
- Engineering disciplines
- 4
# licence + queue check before a PVS run
$ lmutil lmstat -a -c 5280@lic01
License server status: 5280@lic01
lic01: license server UP (MASTER) v11.19.4
Vendor daemon status (on lic01):
cdslmd: UP v11.19.4
Users of Virtuoso_Layout_Suite_XL: (Total of 8 licenses issued; Total of 3 licenses in use)
$ qsub -q pv.q -pe smp 8 -cwd run_pvs_drc.sh
Your job 41827 ("run_pvs_drc.sh") has been submittedBest fit
Useful when the infrastructure is real and the CAD layer cannot slip.
- New client-owned infrastructure needs CAD/EDA bring-up before designers move in.
- An existing environment must migrate to new remote or on-prem systems.
- Tools, licenses, PDKs, decks, access, and queues need to coexist cleanly.
- The team wants documentation, handover, and dependable post-go-live support.
What we already deliver
- 01
Cadence Virtuoso Studio IC25
Install Virtuoso Studio IC25 and align the base client environment for real design work.
- 02
cdsmgr / FlexNet licensing
Configure license services, feature access, and operational handling for shared engineering use.
- 03
ClioSoft SOS Data Manager
Install SOS, create repository structure, and bring up the related license server.
- 04
RHEL / AlmaLinux platforms
Build production-grade Linux systems for secure EDA deployment and daily designer use.
- 05
Sun Grid Engine scheduling
Configure queues and distribute workload across clustered servers.
- 06
PDKs and rule decks
Install and maintain tsmc18rf, tsmcN22, gf12nm, and other PDKs with supporting decks.
- 07
Verification flows
Set up PVS, Assura, Pegasus, and Calibre for DRC, LVS, RCX, and related verification flows.
- 08
Secure remote operations
Deploy VPN, SSH, VNC, firewalling, backups, self-hosted access, and system hardening.
How support usually works
01
Assess the current stack
Review the current environment, target flow, user model, network boundaries, and migration constraints.
02
Plan + document
Turn the target into an implementation plan, validation checklist, and working documentation.
03
Deploy + support
Install, integrate, validate with the team, and stay available after go-live.
What the team should see
- Stable CAD/EDA environment for designers
- Tool, license, repo, and queue services operational
- PDKs, decks, and verification flows validated
- Remote access, security, and backup controls in place
- Documented rollout with post-go-live support
What we need from your side
Technical prerequisites
- Current environment details
- Target tools and flows
- User count and access model
- PDKs, decks, and license scope
- Security or network boundaries
- Target milestone or go-live window
Engagement options
- 01
Initial assessment
Short discovery phase to align tools, infrastructure assumptions, users, security boundaries, and first priorities.
Scoping - 02
Implementation
Hands-on setup for tools, licenses, PDKs, workspaces, queues, validation, and rollout tasks.
Project-based - 03
Ongoing support
External CAD/EDA reference for day-to-day issues, changes, follow-up, and operational stability.
Retainer or hours pack - 04
Training and handover
Documentation and knowledge transfer for internal staff once the environment is stable and in regular use.
Enablement
Next step
If the scope is close, the fastest move is a technical call.
Share the current systems, target stack, licensing assumptions, access model, and the first flows you want ready. We can align quickly on implementation scope, rollout sequence, and ongoing support shape.