Makes me wonder what workflow is actually using or benefiting from the 'one big repository' that OPMS provides. Reporting doesn't need a unified datastore. Aecosim and others seem pretty OK with scanning through multiple Ref attachments. Centralisedcomponent/specs libraries? Again, this can be handled via ISM + Bentley Data Manager I imagine. Aecosim and Mstn's DV's all read from a centralised dataset. Parametric propagation? Does OP actually do much of this at the moment? Plantwise / AXSYS probably does. I think that the paramtrics in OP is pretty low key and localised to the component placement tools... like Aecosim. Not much in the way of cross file/model propagation that you see in Catia or ShipConstructor's DDROM which would need an all-encompassing orover-arching traffic cop DB. ?? I think that the whole DB experience needs to get more like Mstn's Ref-file based way of working. When the user checks components out from OPMS, there should be an option to 'reference' the components as read only elements. This should help minimise the silly transaction check in procedure and the overheads, ie the whole OPMS SQLServer set up! If you are working on the structure, you work check the structure in the area you want to work on in edit mode, and check the piping, civils, arch components out in read only mode. OPM automatically groups and adds the different piping, civils etc components as separate Ref attachments by discipline. Why make OPMS check for mods on check in/out when you know you won't make any? If the user Activates a Ref because he needs to make a mod, then OPM then tries to tag to tag those components with an advisory lock and flags the components up for the usual transaction process. If another has in the mean time checked out the components than there will need to be a change resolution Q&A session for those components. SQlite even has Shared Cache mode looks that like just the thing for this kind of working. Why not use OPMS to provide the option to define multiple active/activated Ref attachments? Something that is already possible in Mstn . CE at some point? As KB mentioned : "If you're in a session of MicroStation and have, say, 30–40 files that are all being referenced, and you need to edit some of them, in the past with MicroStation and AutoCAD there was one lock on one file. Now we can modify multiple files and have a transaction that spans multiple, independently lockable files. This is a big thing . You can have a large project spread across multiple offices and multiple computers and files." OPMS may allow one user to access the whole repository for modification, but this will create chaos on a large ongoing database as the check-in / approval process would have to deal with a huge number of elements to be MANUALLY approved. This in fact means the changes would just be 'rubber stamped-through'... making the whole transaction management concept a joke. Need to provide for better flexible partitioning... like Ref-files, only improved. 3. Streaming data: .dgn's usually continually save changes to file. As the data gets synchs to/from the OPMS repository, I suppose this will look kind of like streaming information. SQlite is not purpose designed for streaming info but does had some streaming functions . Not sure what the bandwidth limit would be but there seems to be some success with realtime streaming . SCADA or simulation data from one of the simulation apps that AXSYS connect to?
↧