Friday, April 17, 2015

Revit 2015 Esperanto Language Pack

IFC format is supposed to be a common denominator for all BIM applications. I have said in another post that it would be great it to be used as a native format for all them. Just a dream - we will not see it.
.
I see two big problems for that.
.
First of all, most BIM applications come from ancient times. That´s good, but they have very consolidated data structures, and it is obvious (and logical) that shareable data properties they have, are just a small part of their full possibilities.
Yes, it may be easy to create a new property from zero: if an RFA Family comes with manufacturer's URL and a link to its PDF catalog, it seems easy to create a property field for that at, let´s say, AECOsim Dataset. I have a good wizard for that. Even a complete mapping table also. But not so easy; for example, there are some apps that don't have an MEP module, and they would get only the 3D side of the IFC Mechanical entities. Data lost.
.
.
Second,  there´s another part of specialization that it is even harder to share: localized data.Localized datasets from separate construction areas or countries are obviously very different. And they have to be; let´s suppose that we are finishing a big tower at Dubai. If they have to make an entity modification on their BIM model, do they have to wait to know how a very localized wall property from Mexico is translated to an IFC definition? Perhaps in IFC v5? No. They have to get it finished on time & budget, just that. They will use their language, their way of working, their currency, their construction slang.
Do we have to wait for Revit Esperanto Language Pack...? Esperanto: a great idea, created for all, used by no one.
.

No comments:

Post a Comment