Home > Community > Blogs > Digital Implementation > three reasons to move to edi system 9 1
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the Digital Implementation blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Three Reasons to Move to EDI System 9.1

Comments(1)Filed under: Digital Implementation, Encounter Digital Implementation System 9.1, EDI system Encounter Digital Implementation System, Foundation Flow Design Closure

We recently announced the 9.1 version of the Encounter Digital Implementation System.  Head over to http://downloads.cadence.com, select your platform and choose EDI91.  Notice that in our download system, we’re calling it EDI as opposed to the former SOC to align with a name change from SoC-Encounter to EDI System that occurred in the 8.1 release.

I think customers will be interested in three high-level aspects of 9.1 that lead to one important benefit: getting your job done faster within the tool.  

The first area of focus was on raw turnaround time for a typical job that runs through the system.  Across a suite of designs that our developers use to test the tool, we’re seeing on average a 2x run-time improvement as compared to 8.1.RTM for multi-corner designs.

The second area of focus is improved quality of results, both in terms of setup time optimization with SI and hold fixing.  For example, our hold fixing algorithm is now better able to identify bottlenecks and efficiently repair hold violations without increasing area- especially locally.

The third area is in terms of correlation to signoff.  The parasitic extraction engine used during post-route optimization aligns more precisely with signoff extraction engines without the need for scale factors.  This leads to fewer iterations required to meet timing closure according to signoff timing.

I think these items together, along with other enhancements make 9.1 a release you’ll want to check out.  

Further Reading:

-Bob Dwyer

Comments(1)

By Manoj Chacko on February 2, 2010
Most excellent points. At advanced nodes, implementation and signoff should not be two separate parts of the flow but one leading into the other seamlessly. EDI system goes a step beyond with the ability to complete signoff analysis from within the platform thereby reducing iterative loops to near zero.

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.