Possible to outline an 'MVD exchange requirement' to address the concept of #groups? #3
Description
For the next Coordination View 3.0 Certification (presumably for IFC 2x4), would it be possible to support and outline an 'MVD exchange requirement' for Groups/Blocks/Cells/Objects/Families/Components/Assemblies/Modules/etc. (exact name is software dependent) between BIM software? (For the sake of consolidation and discussion here, i'll call them #Groups)
Would like to support a workflow similar to the following...
- A BIM file, from Vendor X, contains 10 instances of #Group Z. →
- This BIM file is exported, via IFC, and in turn imported into Vendor Y's BIM file. →
- Within vendor Y's program, a user changes/modifies the definition of #group Z. This change is, in turn, propagated throughout the 10 instances of #Group Z , within vendor Y's file.
Not necessarily looking to save the parametric values of these #Groups yet, just static definitions at this point, would suffice. Want to keep it as simple as possible.
In an ideal world, it would be great to outline this proposed exchange schema as a new type of MVD, call it a #RoundTripMVD or #Bi-DirectionalMVD. I have a sense, however, that it would be easier incorporating this proposed exchange requirement in an existing MVD--Coordination View 3.0, for example...but would defer to others on this.
Related conversation, if interested. http://sourceforge.net/p/ifcexporter/discussion/general/thread/fad5b2f8/
From my understanding, would one use the following IFC entities to accomplish this?
--IfcMappedItem
http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/ifcgeometryresource/lexical/ifcmappeditem.htm
--IfcGroup
http://www.buildingsmart-tech.org/ifc/IFC2x4/rc4/html/schema/ifckernel/lexical/ifcgroup.htm
Thanks Much, Ryan
I'm sure i'm missing a few, but provided the following for Reference...
- Revit (Families, Groups, Assembles)
- Microstations (Cells)
- Archicad (Objects, Modules)
- Vectorworks (Symbols)
- Tekla (Components)
- Sketchup (Components)