Issue link: https://resources.pcb.cadence.com/i/1541046
5. Using Descriptive Net and Component Naming Clear, descriptive net and component names are critical for design clarity, debugging, constraint management, manufacturing, and collaboration. Vague or default names like "Net00054" or "R99" slow down design reviews, make constraint and rule assignments error-prone, and lead to confusion during layout, bring-up, and troubleshooting - especially when working in teams or returning to a project after time away. Proper naming practices help enforce correct layout constraints, clarify circuit intent, and make your design readable to others, including manufacturing and test engineers. When And Where To Apply Apply naming discipline as you draw your schematic before exporting it to layout. Any net that carries a signal of interest (especially clocks, resets, power, differential pairs, buses, references, and interface lines) should have an explicit, descriptive name. Component naming conventions should be set as soon as parts are placed in the schematic and kept synchronized throughout the project. OrCAD X schematic net and component naming