Locations, projects and teams
BIMcollab Twin organizes project files using a structured approach that facilitates easier navigation and streamlines collaboration between users. Documents and data are added throughout different project phases and are linked to their respective spatial structure elements.
BIMcollab Twin categorizes project files into two main structures, both of which exist simultaneously in a project:
1. Spatial Structure: this is hierarchically organized into the project's physical locations, buildings and stories. It reflects the real-world structure of the building, with all the listed parts having a physical representation.
2. Project Structure: this is designed for the organization of various projects and work that needs to be done in relation to the physical structure of the building. Project Structure helps to structure the project timeline through Project Phases (e.g. development, constriction documentation, and operations phase), aligning tasks, goals and planning.
BIMcollab projects are always managed through both of these structures. Starting with the spatial structure where project administrators create a digital representation of the actual physical structure. Next, the project administrators create a project structure, where they can plan and manage the work that will be performed on these structures in different timelines.
By combining these two structures, BIMcollab Twin allows you to manage your project throughout it's lifecycle in one platform.
This is also why future changes and additions can be easily managed in Twin. The spatial structure grows with the development of the building, so each phase has its own spatial structure. Whether it's the addition to the spatial structure (e.g. a new hospital wing in being built) or a new project needs to happen to the existing structure (e.g. a renovation of an existing building floor), future additions are easily accommodated.
And in addition to the file organization carried by the Spatial and Project structure, we also have the User Structure.
3. User structure: it is designed to manage project participants effectively by defining their roles, permissions, and teams within the platform. This structured approach ensures that the right people have access to the right information and tools at the right time.
The illustration below shows how the Spatial Structure, Project Structure and User Structure interact in BIMcollab Twin. In the following paragraphs, we will discuss each structure in detail.
Spatial Structure (1)
The Spatial structure is divided into the following categories: Locations, Plots, Buildings, Parts and Stoeys. When creating the spatial structure, it is important to have a clear idea of what it should look like and how it will be broken down.
Locations:
Locations are the primary category in Twin because they define the spatial structure of an account. The Location is the top-level container, which can contain lower-level elements like plots, buildings, building parts, or storeys. As such, a Location is a grouping of a contiguous plots and buildings. For example, a Location can be a University Campus where all the plots and various buildings are grouped under.
One account can have multiple locations, but a minimum of one Location is required to set up your first Twin project, and the Administrator of the space will be responsible for creating this.
Locations can be organized into Location Groups. Location groups combine Locations of similar functions. For example, each city can be a Location, and a Country can be a Location Group made up of multiple cities.
A location group can also consist of subgroups which comprise smaller locations that form the parent group (like in the example below, the subgroups are city neighborhoods). Note that subgroups are also considered Location groups, but simply put, they are Location groups that have a parent group. Using Location Groups is optional, but a great resource for spaces with complex projects that need to categorize projects flexibly.
Deciding to organize your Locations by their physical location, or by their typology and function, or some other order is at the discretion of the project administrator.
In the example image above, parent Location groups are countries "Nederland" and "Germany". "Eindhoven" is a Location group under the "Nederland" parent group. In addition, "Eindhoven" has a few subgroups assigned to its location which include: Gestel, Stratum, Strijp, Tongelre, Woensel.
Plots
Subsequent to Locations is the Plot category. A plot is a piece of land on which a building or multiple buildings are placed. A plot is physical item that may be already registered in the land registry. Multiple plots can be added under one Location, but a minimum of one plot is required to create a new spatial structure.
Buildings
A building is a physical structure located on the plot. It has a physical address that is assigned to the structure. Multiple buildings can be placed under one plot.
Parts
If required by your project, buildings can be further split into parts. This is an optional feature, but a useful one for complex buildings where different parts might have different storeys or need to be managed separately (e.g. a hospital with many departments and wings).
Storeys
Storeys are levels in the building with, typically, a floor assigned to it. In the spatial structure, storeys are defined by names and heights. Project stakeholders should agree on naming convections to be used across all aspect models. Storeys can be added to the building it self or to each building part indivisually.
Project Structure (2)
Projects
Once the spatial structure is created, Projects are created and linked to the spatial structure. Projects represent the work that has to be done in the spatial structure, for example, the process of building a structure, or renovating a part, etc. As such, Projects are created in association with one or more plots, buildings, parts or storeys. Project documents and data can be added at the project level.
Consider the example image below: the Location "Krone Campus" (a), a university campus with two plots which host some buildings in need of renovation. On the campus, there are two plots (c), one plot for offices, and another for study halls. Two projects (b) have been created in this location for the designated renovation of two buildings (Building A & Building 6A) which rest atop the aforementioned plots.
Project phases:
Project phases are representative of the stages of the project lifecycle, for example, the concept design, detailed design, and construction phase of a construction project. Project phases reflect the duration of each stage, and can differ per project. Documents may be added and linked to specific project phases in which they are created.
The account administrator is responsible for setting up the phases in the way that is applicable to the project.
Ensure that you are always working within the right Location, Project, and Project phase, especially because documents can be added and only be visible at a specific stage.
User Structure (3)
User Roles
All users added to a BIMcollab Space need to be added to a specific team (explained below) with a specific User Role in order to access the project phase and necessary documentation. Users who are not added to a team that is active in a project phase do not have access to any information, and can't participate in the project.
Through roles, admins create permissions and chose what project functions the users in these roles have access to. For example, can a user in this User Role upload documents, do they have access to confidential documents, can they download native model files, can they upload modes, etc. Visit the User role permissions article to learn more about this topic.
Teams
In BIMcollab Twin, users gain access to specific project phases by being assigned to one or more teams. The account administrator is also responsible for creating teams, adding users to a team in a selected User Role, and assigning teams to project phases.
Once this is assigned, users can access the necessary information and features within the designated phase. Furthermore, users can view parent projects and their respective locations, buildings, parts and storeys. Multiple teams can have access to the same project and project phases. Also, a user can be a part of multiple teams, meaning a user can have multiple roles within a project.
Because multiple teams may have access to the same project and/or phases, users' dashboards within a Twin space may vary due to the different permissions they have.
Related Articles
Get Started with BIMcollab Twin for Admins
This Get Started guide describes the functionalities and configuration of your BIMcollab Twin space. It will get you up and running in no time. Your space has already been activated by our team. When ordering a space, you were asked to provide ...Modules
What is each BIMcollab Twin module about? BIMcollab Twin consist of multiple modules in the Project Environment. The functionality of each module is tailored to the specific phase of a building life cycle: from design to use and management. Different ...User role permissions
When a user is added to a team, an administrator will assign a user role to that user based on what their responsibilities will be within the team. Because teams are then assigned at project phase level, the visibility of various locations, buildings ...API BIMcollab Twin Quickstart
This document aims to provide a human-friendly quick start description of the BIMcollab Twin Public API . Detailed documentation about our API is available at https://api.demo-bimlink.nl/swagger . To gain access to our API and the documentation you ...Create and add a documents naming convention to a project phase
Within BIMcollab Twin, the document number is very important, because the entire version management depends on corresponding document numbers. Document naming conventions are essential for organizing files in a structured and consistent manner. ...