It's a better and straight way to let HW designer entry constraints directly in CES, not in the Excel. Because There are Enets, it's not so easy to write a script to import the excel file. CES is very easy to use, and can get familiar with it within 4 hours.
HW desinger can add and modify the constraints in front-end CES in entry side, and export an ASCII file which you can import it into back-end CES database in layout side.
Yanfeng is right, especially with clearance rules, it is quite simple to get familiar with CES.
But I also understand your engineers concerns about CES.
For a large design you get in troble with CES very fast. The GUI matrix is to hughe and you do not find any constraints not beeing default.
I know, there is no option to import Excel into CES. Only by the use of automation (reading the Excel worksheet and writing it's content back into CES)
you will reach your target, I am sorry.
We ourselfs have started to write automation code for reimporting Excel due to the issue mentioned above.
If you also think, that CES is much to complex to get an overview of all you constraints, you could vote for my idea for reducing the complexity of CES.
thanks for the reply.
Our main issue is not to find a specific rule, but to figure out where the differences to other rules are.
Thus, a CES gui only showing differences compared to the defaoult rule would make the GUI Matrix much smaller
and easier to analyze.
There is code in AATK that does this. It is in the CES AATK pulldown menu. It is only a crude example but take a look.