{"id":367,"date":"2023-10-16T19:38:59","date_gmt":"2023-10-16T19:38:59","guid":{"rendered":"https:\/\/onetools-project.lu\/?post_type=project&p=367"},"modified":"2026-03-10T09:20:23","modified_gmt":"2026-03-10T09:20:23","slug":"3d-modelle-im-facility-management","status":"publish","type":"project","link":"https:\/\/onetools-project.lu\/en\/project\/3d-modelle-im-facility-management\/","title":{"rendered":"3D models in Facility Management"},"content":{"rendered":"
\n
\n
\n

The use of 3D models for building management offers many benefits for facility management. However, it also comes with some challenges.<\/p>\n

One of these is the migration of models and elements to the latest versions of the CAD software.<\/p>\n

New versions of the various programmes come onto the market every year and the manufacturers have different approaches to ensure compatibility with elements from older versions.<\/p>\n<\/div><\/div>\n\n

<\/span><\/div>\n\n
<\/div><\/div>\n\n

ArchiCAD<\/h1><\/div><\/div>\n\n

Today we would like to report on a migration of an ArchiCAD model that still contained elements from version 11 (released in 2007). The model was migrated to ArchiCAD 27.<\/p>\n

As there are 16 years between the versions, it is not surprising that the whole thing was rather \"interesting\".<\/p>\n

ArchiCAD offers the option of saving elements with the model as an archive file in order to display them in newer versions. There are also migration libraries. The libraries of the older versions are loaded here. However, these do not go back to version 11.<\/p>\n

At first glance, you might think that you don't need to worry about migration, as all elements are retained, but if you want to maintain the models in operation and also include all construction measures in the model, there are a few limitations. One of these is the speed of loading the plans. The more \"old\" elements there are in a model, the more libraries have to be loaded and the longer the whole process takes.<\/p>\n

There are also differences in the properties of the elements between the versions. In order to use the new features and the elements effectively, it is important to migrate the elements to the latest versions.<\/p>\n<\/div><\/div>\n\n

<\/div><\/div>\n\n

The migration<\/h1><\/div><\/div>\n\n

You might actually think that it's quite simple. You select the old elements, go to the library, select the new, suitable element there and explain to ArchiCAD that this element should now be used instead of the old one and all settings such as size, materials etc. are adopted. Yes, that's what you would want. But unfortunately this is not the case.<\/p>\n

There are many points to consider in order to transfer the properties correctly. In some cases, you have to note down the information from the old element and then transfer it manually to the new element.<\/p>\n

Ideally, when creating and placing the elements, you should pay attention to a few points that will make migration much easier later on.<\/p>\n<\/div><\/div>\n\n

<\/div><\/div>\n\n

Conclusion<\/h1><\/div><\/div>\n\n

The good news is that it is possible to migrate from version 11 to version 27.<\/p>\n

However, we advise you not to wait so long and when switching from one version to another, take the time to migrate your models, including the elements, so that the current objects are always used.<\/p>\n

If you do this regularly, the effort is manageable. However, if you skip several versions, the whole thing can become \"exciting\", as in our example.<\/p>\n

After the successful migration, the model can be synchronised between ArchiCAD 27 and the latest version BuildingOne 16.<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n

\n
\n
\n
← <\/span>Significant time savings and simplification through digitalisation<\/span><\/a><\/span>Digitalisation \/ automation<\/span> →<\/span><\/a><\/span><\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":2,"featured_media":368,"comment_status":"open","ping_status":"closed","template":"","meta":{"iawp_total_views":0,"footnotes":""},"project_category":[],"project_tag":[],"class_list":["post-367","project","type-project","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project\/367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project"}],"about":[{"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/types\/project"}],"author":[{"embeddable":true,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/comments?post=367"}],"version-history":[{"count":4,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project\/367\/revisions"}],"predecessor-version":[{"id":711,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project\/367\/revisions\/711"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/media\/368"}],"wp:attachment":[{"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/media?parent=367"}],"wp:term":[{"taxonomy":"project_category","embeddable":true,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project_category?post=367"},{"taxonomy":"project_tag","embeddable":true,"href":"https:\/\/onetools-project.lu\/en\/wp-json\/wp\/v2\/project_tag?post=367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}