When a model is added to Kinship the system attempts to place that model into an existing project if there is one available. If no suitable project can be found the model will be added as unassigned.

How Kinship decides on the correct project to add a model to.

Kinship looks at various parameters of a new model to decide to which project it should be assigned. The following are the possible alternatives:

• Assigned to a project If Kinship can find an existing project that matches the incoming model, it will be placed in that project. The process for deciding this is described below.
• Put into Unassigned If no suitable project can be found the project will be placed in Unassigned projects.
• Private Projects If a model is added as a private model then it will be added as a new project.
• A new project is created If Kinship is able to decide to which project the model should belong, but that project does not yet exist, it will create it.

At any time you can move models between projects or merge projects.

Kinship model assignment algorithm

Kinship uses the following steps to decide which project to add an incoming model to:

1. Is the central file stored on BIM 360? BIM 360 projects are uniquely defined with a project identifier that is set up when you create them. Kinship can therefore decide whether a BIM 360 model is part of a project or not.

   • Does it belong to an existing project on BIM 360? If so the model will be added to that project in Kinship.
   • If it does not belong to an existing project, then a new Kinship project is created for it.

2. Does the file name of the model follow the ISO 19650-2 NA.2 naming convention? The ISO 19650-2 standard defines a way of naming files used in a project. If your files follow this convention Kinship can use this to assign the project.

   • If there is an existing project where the project portion of the name matches, then the model will be assigned to this project.

3. Check for shared coordinates. If there are any projects with these coordinates, place the model in that project.

4. Does the model follow the ISO 19650-2 NA naming convention? If so and no existing project is suitable, then place this in a new project.

5. Are the Share Coordinates non-null or default. If so, create a new project and place the model in it.

6. If none of the above are true, place the model in Unassigned Models.

Kinship will use the following criteria to decide on which project a model should be placed in. If no suitable project exists then the model will be put in the Unassigned category.

Unassigned models

If no suitable project can be found when following the above process then the model will be placed in Unassigned Models. You can view the models in this category from the Projects landing page, where there is a section entitled Unassigned Models.

The only action that you can perform on an unassigned model is to assign it to a project or remove it from Kinship. You can perform these actions from the three-dots menu in the Model Detail page or from the Unassigned Models page.