Collaboration Workflows

This chapter lists the workflows and how the files used by PlantReporter are handled in a Collaboration (BIM360 / Autodesk Construction Cloud) environment.

Warning: When working with collaboration projects you have to consider a very high latency when configuration files are checked in and out. This also leads to delays when changes are applied to the configuration until they are available for other users working on the same collaboration project.

Definitions

For the handling of files we use the following definitions

1. DOWNLOADED A file is downloaded from BIM360/ACC to the work folder. It can still be DOWNLOADED or CHECKED OUT by other users.

2. CHECKED IN A file is uploaded to BIM360/ACC from the work folder. It can be DOWNLOADED or again CHECKED OUT by other users.

3. CHECKED OUT A file is downloaded from BIM360/ACC to the work folder. It can still be DOWNLOADED but not CHECKED OUT by other users.

4. COMMITTED A file is uploaded to BIM360/ACC from the work folder, but will still be checked out. It can still be DOWNLOADED but not CHECKED OUT by other users.

5. DELETED The file is physically removed from the work folder and from BIM360/ACC as well as unlinked from the project to not appear in Project Manager anymore.

6. UNLINKED The file is physically not removed from the work folder and from BIM360/ACC, but is unlinked from the project to not appear in Project Manager anymore.

7. UNDO CHECK OUT This is used if the file was checked out before with the purpose to lock it from being used by other users. Using UNDO CHECK OUT is faster, then checking the file in and it doesn't increase the version number.

8. UNDO CHECK OUT This is used if the file was checked out before with the purpose to lock it from being used by other users. Using UNDO CHECK OUT is faster, then checking the file in and it doesn't increase the version number.

Table of Content:

• General Workflow

• Report Configuration Files