Cadence.com will be under maintenance from Friday, Oct. 3rd at 6pm (PST) thru Sunday, Oct 5th at 11pm (PST).
Cadence.com login, registration, community posting and commenting functionalities will be disabled.
Home > Community > Blogs > PCB Design > what s good about adw s team collaboration check out the 16 6 release and see
 
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 PCB Design 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: *

What's Good About Allegro Design Workbench Team Collaboration? Find Out in the 16.6 Release

Comments(0)Filed under: PCB design, SPB, Allegro Design Workbench, PCB, ADW, design, Team design, Grzenia, Allegro 16.6, 16.6, Cadence, Cadence Design Systems

The Allegro Design Workbench Team Design Option (TDO) offers two (2) specific integrator roles for team design and collaboration:
Logical design integrator
  Responsible for front-end design
Physical design integrator
  Responsible for back-end design

A logical design integrator or physical design integrator needs to enable Team Design and assign and inform team members to work on the design project from the list of designers.

Read on for more details…



Logical design integrator (LDI)


The LDI has complete permission on logical objects as defined in the design and assigns users to logical objects of the design. The physical objects are shown as read only for an LDI and by default the LDI sees the logical hierarchy. The Team Design interface displays the schematic design in a hierarchical form. It shows all the blocks and its logical objects such as:
Schematic
Symbol
Package

 


Physical design integrator (PDI)


The PDI has complete permission on physical objects as defined in the design and assigns users to physical objects of the design. The logical objects are shown as read-only for a PDI and by default the PDI sees the Physical Hierarchy. The Team Design interface displays the physical design in a parent/child hierarchical relationship.  It shows all the blocks and:
Physical view
Collections
Partitions
Modules
Package view


 

TDO User Model

A team of users is assigned for ECAD projects - the users are assigned either using LDAP or the template file. The user doing ETD is either the LDI or PDI or both, based upon either the LDAP or the template file. All project users get read-only permissions on a design. Users working on particular design objects get read and write permissions on design objects within a project based upon user assignment.

TDO pulls out user IDs from the corporate LDAP system, and the LDAP query and filter are controlled using the ldap.config file under cdssetup.

When the teamassignmnettemplate.xml file is placed in the proper directory, and the environment variable is defined, the project team assignment phase will access the team assignment template, providing a list of the user IDs defined within the template.


What do you think about this capability?
Jerry “GenPart” Grzenia

Comments(0)

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.