It would be great to have 2D/double line routing in OpenPlant Modeler. This is not schematic or P&ID. These 2D or double line drawings are accurate and spec driven. OpenBuildings have this feature, even in AutoPLANT this feature was there. CAD...

Hello, I would like to suggest a new improvement for equipment import from an Excel spreadsheet. Beside equipment name, I would like also to define rotation axis and rotation degree. It will be very helpful e.g. while I am importing lighting fixtu...

If users want to read the pull description of piping data for fields such as DESCRIPTION or COMPONENT NAME in the properties dialog, or the modify component dialog, they try to extend the width of the dialog. However, OPM just add more categories ...

We have various Rest-API-capable software in use which could use the Rest-API for monitoring. Lansweeper, Paesler PRTG, Grafana and PowerBI. (We prefer Lansweeper and Paesler PRTG) Currently, Users get Information about updates and has inform the ...

It is bad practice to have two commands with the same name. Especially, while trying to train new users. Why is there an OpenPlant Move and a Microstation Move, but both buttons are labelled Move?

Currently, it is not possible to see Gaskets and Bolts in the piping compenets listed under a pipeline, or isometric sheet. It is not possible to change the gaskets or bolts, or perform Update From Spec of gaskets and bolts. There are many times w...

We would like to include a drawing name column in all tag browser component classes. When editing data, engineers need to be able to identify the drawing that each tag resides on.

We would like to have better tools to sort/organize the Shared Queries in the Query Browser. Currently, when a new query is shared, it is inserted at the end of the list. We would like to be able to sort the list of all Shared Queries or move one ...

We would like to have the ability to create more advanced queries, which would include an Update, Delete, and Alter (database structure revision) option.

We would like to have a published data structure diagram with relationships - similar to what was available with version v8i. This would provide an easier way to look up component codes to exclude from a query. For example, we might want an equipm...