Overview

The Teamwork tools makes available to work on the same project with your colleagues together. Every part of your project updates automatically, so that the plan and the documentation are one coherent unit through the lifecycle of it.

Basic concept

• Working area: working area organizes all items that a team member may make changes to under a logical unit. New items are automatically placed on the active layout owned by the team member.
• Master working area: the master working area collects all the common part of the team work such as drawings, building parts, floors, layers, views and geolocation. Because of its special role during the team workflow it is password protected. A team member who enters the mater working area also has administrative rights for the time being.
• Team member: a user identity consisting of a name and a(n optional) password, granting access to the teamwork project to make modifications on the works space that is owned by the team member.
• Administrator: a team member who owns the master working area. The administrator can modify the common parts of the team project and also has the right to create new working areas and add / remove team members.
• Central model / Central project: the central model is the result of the work of the team members, automatically merged into a central project file. It continuously evolves as team members publish changes. All team members working online can see and work on the latest status when they open the project file or when they refresh the project.
• Local version: all local changes created on the base of the central model. When saving the project all local changes are aotumatically published to the central model.

Operating rules

• Teamwork allows simultaneous access to a shared model through use of a central model.
• The central model has to be saved on a network drive to which all team members have access.
• Master working area is privileged to define team project fundamentals (Storey structure, layers, geo-location and initial state of the project)
• Group members can create or access any number of workspaces. For a team member, one workspace can always be active and have several Editable states. Access is automatically terminated when the project is closed.
• A team member can only create items in the Active workspace. A team member can only modify or delete an item in workspaces that are Active or Editable. Items in the Reference workspaces are available for reference only.
• Access to a workspace can be unlocked at any time by its owner. If you need to edit an item that is in the Workspace in the Reference state, you must request it from the workstation owner, who has to unlock your access to the workspace. Once unlocked, the other team member can set the workspace to Active or Editable. This makes the workspace free and open to another team member, who can open it in Active or Editable mode.
• Only the administrator can take away a workspace from other team members and, if necessary, merge or terminate it with another workspace.
• All users work locally on different working areas. Every user can manage one working area in active state to which new elements are added.
• Graphic Override enabled to provide different output of the view (color, line types, line weight, half-tone, and hatch pattern).
• Save command means synchronizing local working areas with the central model so that other users can see the updated workflow diagram.
• The team member can switch the project to Offline on their own computer if e.g. you leave the local network and want to continue working elsewhere. When you return, the project must be returned to Online mode and the project will be automatically resynchronized with the central model.
• A teamwork project can be converted to a single-user project for archiving purposes, e.g., when certain milestones are reached. The transformation creates another project that is no longer tied to the teamwork project in any way.