Mentor Graphics’ Expedition Enterprise flow supports various ways of naming connectivity and PCB data such as net names and net class or constraints class names (and much more). In recent discussions with customers, we’ve found that reused naming mechanism is what enterprise customers do most often to optimize their design processes.
One example of creating net classes in CES is to give net class a meaningful name derived from net names this class is planned to represent. Net class PWR would be set for all of the power nets (such as PWR_5V, PWR_12V etc.) to represent their common constraints such trace widths. The same in example shown below where both types of classes, diff pairs and net names match.
Mentor wants to understand customer strategies for naming convention to optimally support constraints use cases in EE flow.We would like to hear from users about it though.
If you feel that discussion thread may be interesting or benefit to others or you have comments to it we encourage you to post your feedback.