Collaborative intelligence

Resolve issues where
the design lives.

A location to inspect. A conversation to follow. A result to review.
Give the team a common place to work through a design issue, with NETI AI alongside the engineering discussion.

Follow one issue through a review.

Illustrative design review

Prism / Layout reviewMarker 1
1
The comment has a location. Open the design view and inspect the marked geometry before deciding on a correction.

The discussion at marker 1

1Identify the issueVerification engineer

“Check the spacing between these routes. Please review the highlighted section before the next DRC run.”

The design location gives the reviewer and designer a common reference.

2Coordinate the correctionLayout designer

“I’ll adjust this section and rerun the relevant check. I’ll use the previous result as the comparison baseline.”

Replies, issue assignment and status keep the follow-up attached to the discussion.

3Review before resolvingDesign reviewer

“Review the new and recurring findings as well as the corrected one. Then record the outcome in the issue.”

The responsible engineer checks the result and records the resolution.

Canvas comments and issues can be anchored in Prism or Pulse. The thread stays close to the work the team is discussing.

Explore connections to your team’s tools

NETI AI alongside the reviewer

Arrive with a
better question.

Use AI assistance for a first investigation of supported findings and results. Bring the explanation and source into the discussion so the team can spend more of its review on the engineering decision.

Explore NETI AI workflows

A practical review agenda

  1. Understand the reported issue

    Ask about a selected DRC or LVS discrepancy. Inspect the relevant rule or result before proposing a correction.

  2. Check what changed

    Use Parity run summaries and compatible comparisons to focus on fixed, new and recurring findings. In Pulse, investigate preflight results and numerical differences between simulation runs.

  3. Decide the next action together

    Discuss the findings at the design location, assign follow-up work and check the result. The team retains responsibility for the review decision.

A diverse team of IC engineers reviewing layout and verification results together

Across disciplines and locations

Less time reconstructing
someone else’s context.

A layout designer, verification engineer and team lead approach the same issue from different perspectives. Shared design access and a discussion anchored to the work give each person a place to begin.

That continuity also helps instructors review practical work and learners explain their design decisions.

See how review supports learning

Bring in the right people

Share the work.
Choose the access.

Grant access to projects, libraries or cells according to the collaboration needed. Update or revoke grants as responsibilities change.

Security and data controls
Viewer
Inspect the shared engineering work.
Commenter
Contribute observations and questions to the review.
Editor
Make authorised changes to the shared design.

Sharing a design and approving an AI proposal are separate responsibilities. Proposal approval follows the organisation’s configured permissions.

Bring your team’s review
into a WCS walkthrough.

Book a technical walkthrough