ORD needs a pay item tool to manage all pay items and quantities for a project. This would help with keeping up with pay items that do not have elements in a file, especially in regard to digital delivery. PowerGeopak had a quantity manager that c...

The mark and intention of was missed for BCI-I-361 with the shipped version. The functionality we are requesting is in the behavior or expansion of the CivilExpression symbol library for reporting purposes on links and nodes.. The described method...

It would be useful to have FGEs in the beam elevation report that correspond to the girder 10th points provided in that report

It would be nice to have a toggle when using the compute haunch option to still model girders as straight as that is what we need for vertical clearance checks.

A feature to define within the Annotation Group for plan alignment annotation and vary the text favourite used based on element length. For example, I would like to use a text favourite with transition geometry text on 1 line for elements greater ...

Civil Cells are often difficult to create due to it's use of parent-child relationships. I find it easier to create what I'm looking for by using constraints and variables for Parametric Cells. I think most Parametric Cells act similar to how a Ci...

There should be a way to turn off Mesh (components) in reference files. Currently, if you untick the "Mesh" Feature Definition from ORD Standards in explorer, it only turns off Mesh Components within the active model. The Mesh components that use ...

Consider adding a set of variables to control XSEC view exaggeration and default exaggeration separate from profile view exaggeration. This would be similar to how there is a separate set of variables for super exaggeration. Suggested variables wo...

Corridors may use a variety of template drops that come from a non-default ITL (i.e. the one defined by the configuration variable CIVIL_ROADWAY_TEMPLATE_LIBRARY). A property of the corridor could be shown that identifies any of the ITLs associate...

We need this to label our profiles optimally there'd be two values, once the horizontal (projected) distance and once the true (slanted) distance between to VPI's