Create / Update / Delete

Ch ch ch ch changes...

B. Create / Update / Delete

Once the user has verified the results of the Review stage, Konstru will then implement changes to the platform model (on download) or to the Konstru model (on upload). These changes can fall into one of three categories, with potential different outcomes based upon whether you are uploading or downloading:

Create (New)

Upload

Any object that does not currently exist in the Konstru model, but is found to exist in the BIM model upload set, will be considered as added 'NEW' to the database. The existing platform GUID is read by Konstru and added to the object at the same time as a new Konstru ID is created in the database to allow for future updates via Konstru.

Download

Any object that does not currently exist in the platform model, but is part of the Konstru database will be created 'NEW' in the platform model. As the object is created by Konstru in the platform, a GUID is assigned by the platform, and this is stored in the Konstru database, allowing for future updates to this object by Konstru.

Update (Existing)

Upload

Any object that is already part of the Konstru model database, which has had changes made to it within the modeling platform since the last Konstru upload, will be 'UPDATED' by Konstru during the upload. This process is facilitated by a match between the native platform GUID and the Konstru ID. Where the object in the platform model and the object in the Konstru model are the same, the objects are considered 'IN SYNC'.

Download

Any object that is present in the platform model, and also present in the Konstru model (as ascertained by ID comparison) will have it's BIM attributes updated by the Konstru model download, if there are differences. Where the object in the platform model and the object in the Konstru model are the same, the objects are considered 'IN SYNC'.

Delete (Existing)

Upload

During the comparison of the platform model and the Konstru model, any object's which have an ID present in the Konstru model, but whose corresponding GUID in the platform model is no longer present, will be 'DELETED' from the Konstru model during the upload process. The assumption here is that the user has deleted the object from the platform model since the last upload to Konstru.

Deletions from Konstru model, made by a deletion of the corresponding object in the Platform model.

Delete Existing on Upload to Konstru - Partial Models

Note, that the ability to Delete objects with Konstru on Upload is based on the comparison of the platform GUID's and the Konstru ID's. Where user's have utilized a Selection or Group to upload the model to begin with (and thus do not have a full list of objects represented in the Konstru model), any future upload that does not include the same set of object's will result in Deletion's to the Konstru model that may be unexpected. This can be considered an issue on both Upload and Download.

Download

Deletions from the platform model as dictated by Konstru act somewhat differently than during an Upload. The concept behind this is as follows:

Deletions from the platform model, made by a deletion of the Konstru object that may be occurred in ANY of the linked Konstru platforms.

Delete Existing on Download to Platform Model

With the understanding that you are unable to directly 'delete' an object via the Konstru web interface, deletions of object's are then limited to taking place in the platform models. As such, Konstru requires validation of any deletions that might be made to your platform model by a Konstru download. This validation occurs at the Download Review stage, where by users can check a box that will ensure that any Konstru objects who have an ID present in the database, but does not have an instance present in the model, will be deleted by