When using the drawing production tools and selecting the option to create the drawing in a separate dgn file there is no way of updating the annotation groups in the resulting drawing file. This seems like a completely flawed workflow as you are ...

Civil cells does not support turnout or crossing elements. Ability to include turnout and crossings in civil cells, will enable creating civil cells for siding and yard areas.

Currently, you can click the delete components within templates and draw a line through any component(s) to delete it(them). It would be nice to have a similar function to delete points by encircling them so you do not have to delete them using th...

Make the Edit Feature Definition dialog box an actual dialog box. Currently it's too difficult to expand the dialog window, and it only remains in view when your cursor is within the window. It disappears too easily with a slight move outside of t...

We need the software to have capability in reporting to interpolate lift and slew values between regression points. Because currently when a complex alignment end point is between regression points the reporting only picks up the lift and slew val...

One of the features that I think would improve the software is the ability to paste Design Standards Tables from Excel into the software. This would save a lot of time and effort for users who need to adjust these values frequently, especially whe...

It would be nice if there was a single list of configuration variables so that we don't have to hunt in different product Help documents (microstation vs openroads) to find details of how they are used. Furthermore there seems to be a lot of confi...

We need an item type civil expression for offset strings from corridor strings (lines created by template points) providing start / end station in respect of that corridor alignment. Currently alignment name needs to be specified manually to the e...

How to know what rules are on a specific element. we can have rules per terrain, corridor, alignement in plan and profiles but there is no way to know what rules are associated within a particular element.

It would be nice if the set feature definition function could remember the last feature.