Structure and Column Grid Management updates
OpenPlant Modeler and BRCM need a consistent and easy to use Structure and Column Grid Manager that users can work with to get quick reference points while locating equipment and routing piping. Ideally this would be a shared tool across other Bentley design apps so that it can be defined once to support all disciplines.
At minimum requirements would be.
Allow defining Structures with a defined XYZ offset and rotation relative to world 0,0
Allow Defining Floors relative to Structure 0 elevation.
Allow defining Column Rows relative to structure 0,0 and aligned with structure
Dynamically display the column row grid in the active dgn file without having to reference attached dgn files
User need to be able to choose which grids to show
User need to pick what floor the grid is shown at.
User need to be able to pick a structure and have the ACS and update to match offset and alignment
Displayed grid must be able to work with MicroStation accudraw and snaps.
Dynamically displayed grids should not be automatically included in published dgn.i.dgn files.
Update Grid line DGNlib also generates a DGN model for use in imodel reference and Gridline.txt file for isometric production.
Alternately I could see management of the gridline.txt being moved into OPIM directly with option to read from dgnlib or user input
Need ability to publish the structures, grid and floors into iModel hub.
| How frequently will feature be used? | Several times a day |
| How much time will you save? | This would save time by allowing single point of setup on the project then allowing all users to quickly orient to the grid while working. |
| Your Industry | Oil & Gas |
This is a great idea. This would be optimal if the same information can be used across platforms with a variable defined, like OpenBuildings Designer, OpenPlant Modeler and BRCM. Items 1-4 in my opinion need to work exactly the same as is in OpenBuildings Designer. Item 5 exposes that some existing features in OPM have similar buttons that complete different tasks, eg. Updating the gridlines.txt file in OPM updates the local grid models in OBD. These would have to be separated with different pick buttons. Item 6 is also a good idea. It would be optimal if all applications can publish the same content to the iModel hub.