Following recommendations of federated files workflow, Complex Terrain is usually built from individual terrains located in separate attachments. Complex Terrain file is then attached to design files, i.e. geometry, corridors, etc.. During opening of such design files, all attachments containing the individual terrains used by the complex terrain file are also loaded which significantly increases the overall loading time. As complex terrain contains all the necessary information in its entity, there should be no need to communicate with its attachments when working with design files.

Depending on project size and complexity of survey data, complex terrain may require many individual terrains in large files. Complex terrains are usually the largest datasets on projects and by far the most time consuming components to load when design files are opened. Removing the need to load all attachments of complex terrains would significantly improve performance of file opening.