Konstru is exchanging full BIM elements, not only geometry. This means your Konstru Beam will be a native Revit, Tekla, SAP2000, ETABS or RAM beam once you downloaded it into your authoring platform. With native we mean just like as modeled manually in there. No massing elements you cannot play with. Konstru translates BIM elements from one platform into the other, just like you would have done it yourself.
To create native BIM elements in each platform Konstru stores centerlines and adjustments. So we can recreate each element by its driving geometry. Other Platforms are uploading meshes to the cloud but they have two major disadvantages: they cannot be used to rebuild the element and they are much larger in size. With storing centerlines and profile sections apart Konstru remains under 1 MB at 10,000 elements while meshed geometries require more than 5 MB. This doesn't sound much? Scale it. Konstru saves time, bandwidth and storage size, which translates into money.
A Revit Beam requires 320 bytes in Konstru while the same element requires 950 bytes as an IFC Beam. This is why Konstru up and downloads are very fast. Compared to a Revit model Konstru requires roughly a 10th of its filesize in storage.
Another reason for Konstru's great performance is its change management aspect. Konstru does not send the full model each time you upload. Konstru it sending and storing changes only. We understand a Model as a sum of its changes. This saves you time when uploading a change and requires less space than storing your full model again. And the best thing about it, it allows you to:
- Go Back in Time,
- Revert Changes and
- Compare Differences.
Just like your personal time-machine for BIM models.