Know what you are working on.
Projects, libraries, cells and views organise the engineering work. Open the relevant design and use its supported technology settings instead of treating every tool session as a separate task.
One workspace for
every design iteration.
Circuit behaviour, physical design and verification belong in the same engineering conversation. WCS brings the tools, saved results and team review into a project your engineers can work through together.
Follow the work through the suiteA closer look at the working day.
Explore three connected parts of a custom IC design iteration.
Schematic and simulation
Test an engineering question.
Build the circuit, choose the simulation setup and inspect the result. Use saved runs and waveform measurements to understand the effect of a change.
- Work with
- Devices, connectivity, model references and analysis settings.
- Inspect
- Simulation readiness, waveforms and numerical differences between compatible runs.
Next in the design loop: work on the physical implementation in Prism.
Physical design
Make a deliberate layout change.
Open an imported GDSII layout or work on a design in your library. Navigate the hierarchy, inspect a selection and refine the geometry in its technology context.
- Work with
- Cells, views, layers and editable geometry.
- Inspect
- Selected shapes, local detail and cross-probed DRC markers.
Next in the design loop: save the change and submit the relevant verification run.
Physical verification
See what the correction changed.
Investigate DRC findings and LVS mismatches, then compare compatible runs. Bring the remaining findings to a design review with the result available for inspection.
- Work with
- Verification inputs, selected technology and rule decks.
- Inspect
- Rule-grouped results, run summaries and fixed, new or recurring findings.
Continue the loop: return to the design, make the next correction and check again.
Foundry-qualified pre-signoff and final signoff remain in your existing qualified toolchain.
Beyond opening another tool
Keep the next step
connected to the last.
In a custom design, the work moves back and forth. Engineers need to understand the inputs, reproduce the check and share the reasoning behind a correction.
Compare results that answer the same question.
Simulation and verification runs retain their inputs and results. Compare compatible runs after a change, investigate differences and return to the design when further work is needed.
Bring the finding into the discussion.
Ask NETI AI about a supported result, then involve the team through shared access and canvas-anchored comments. Reviewers can inspect the engineering context behind the discussion.
Technology belongs in the workflow
Your PDK gives the
design its context.
Layer definitions, device models and design rules determine what an engineering result means. We review the PDK and intended operations together, so the evaluation reflects the work your team needs to do.
- Layers and geometry
- Layer maps and supported technology definitions connect physical shapes to their intended purpose.
- Devices and models
- Supported device definitions and model references provide the context for schematic and simulation tasks.
- Rules and documentation
- Verification uses the selected deck. Relevant rule sources help engineers interpret supported findings.
Customer-supplied PDK material is handled under agreed confidentiality and licensing terms. The evaluation establishes suitability for the requested workflows.
Discuss your technology scopeCustom EDA Engineering
Extend WCS around
the work you do.
Need a specialized generator, design check or engineering workflow? Build a capability for your team, with agreed layout and netlist handoffs to the tools your customers require.
Explore custom EDA solutionsPut the suite to work
Evaluate a design iteration.
Start with a sample block and a clear engineering question. Agree the task, technology and results to review.