In OpenRoads Designer, when defining or editing parametric constraints, the Corridor Object toolbar disappears from the screen. This removes access to important corridor information at a critical stage of the workflow. This idea proposes that the ...

Introduce a built‑in interactive 3D viewer within the Template Editor that allows users to preview templates in real time. This viewer would display how a template applies to 3D models (e.g. corridors, terrain, alignments, utilities, or structural...

While it is easy for users to idenfity the purpose of creating a particular Point Control, there is a lack of visibility over the purpose of a Parametric Constraint. Adding a Description entry will make it easier for users to identify the purpose ...

It would be useful to stay in the same tool after one surface template has been placed, similar to all other tools in OpenRoads. At the moment, I have to pick the tool again everytime I want to place a surface template.

Suggest renaming the "merge" and "append" functions when creating a complex terrain to something more descriptive of the action being performed. For instance, merge could be renamed to "overwrite" and append could be renamed to "use both". Users h...

Perhaps this is a Bug, but it would be much more intuitive if ORD Explorer would automatically update while docked (specifically the "OpenRoads Model" portion). As it is right now, you constantly have to close explorer and re-open it to see update...

Turn off snap for ORD. Having the snap rule on by default causes so many problems for new users. Rules are created all over the place causing crashes and unnecessary processing.

In complex roadway designs, it is common to have a single horizontal alignment with several associated cant alignments to evaluate different scenarios. When annotating profiles, OpenRoads Designer correctly pulls data from only one "active" cant a...

Seems that users generally shouldn't be adding plan based reference files to dynamic cross section or profile window design models known as non-indexed models. Would be nice to prevent someone from accidentally doing this and not realizing.

Within the Item Types Import/Export tool, "Import From" and "Export To" lead directly to folders outside of ProjectWise. There is no option to import from or export to an excel file within ProjectWise.