Starting to see Bentley apps merging together...
- Aecosim and ProStructures
- OpenPlant and Aecosim / ProStructures ..
- Aecosim and GenerativeComponents
- Aecosim and Descartes?
- OpenBridge Modeler and OpenRoads and RM/LEAP Bridge
- Axsys and OpenPlant?
1. Aecosim and ProStructures:
The problem here is that both apps were developed independently, and have taken separate approaches to similar workflows. Aecosim has its DataGroup System to store its attribute data, and old Family and Parts for its resymbolisation / drawing production system. Lately, there is talk of and willingness to move this the Items and Element Template system provided at platform level. Aecosim electrical also dips into Mdb to store its electrical component info because DGS is not geared to that kind of database.
ProStructures has a separate system which pretty does a lot of the same the same stuff that Aecosim has to do. Storing structural steel sections... there are a growing number of Bentley apps (ABD,PS,STAAD/RAM,OP,OBM.LEAP etc etc) that have to do this. They really should be based on the same 'schema'. They should also have the same interface/dialog box framework. Reminds me of the confusion that IFC is trying address wrt taxomony etc standards. There is the platform SDK, but shouldn't there be a mid level SDK for providing some common patterns(?) for storing and accessing data so that all those app developers are inculcated to do things in a more standard way?
2. OpenPlant and Aecosim / ProStructures
OpenPlant introduced its Strutural Modeling Components (SMC) last year. These are components and tools that are binary compatible with Aecosim (and ProStructures?). Also includes grids. It would be great to see more of this. The idea is that if the piping modelers are manipulating some steel members, they should be able to active the structural modeler's Ref attachment and modify the element. By using the same tools on a common schema, there is no need for all that ISM or translation overheads.
ProStructures can also now parameterically link to Aecosim elements like walls and slabs. Changes in Aecosim are picked up in PS when the Aecosim Ref is reloaded, and the rebar array automatically updated. In future, this uni-directional workflow could be enhanced to work like SMC's, so that the PS modeler can also make changes to the Aecosim elements.