Skip to main content

How to structure your projects in Vind AI

In Vind AI, you have two primary levels of organisation: Projects and Branches. This guide will help you determine the best structure for your workflow to ensure your data remains organised, secure, and easy to analyse.

Written by Ingvild Lyckander
Updated over 2 weeks ago

Quick Guide: Projects vs. Branches

Use projects when:

  • You require access control over specific data.

  • You do not need to perform in-depth comparisons between different areas.

  • You want to separate teams or model parks that do not affect one another (e.g. different geographies)

Use branches within a project when:

  • You ar testing multiple scenarios of the same park (buildable area).

  • You want to perform detailed comparisons (e.g. screening multiple areas or competitor analysis).

  • You want to explore parallel solutions without affecting the "main" project (e.g. testing different layouts and configuration set-ups).

Example:

  1. Project 1

    1. Branch A

    2. Branch B

    3. Branch C

  2. Project 2

    1. Branch A

      1. Branch AI

      2. Branch AII

    2. Branch B

      1. Branch BI

Projects

Think of a Project as a dedicated environment. Each project acts as a separate, independent workspace to keep your data clean and secure.

  • Access Control: Permissions are managed at the project level. If specific data should only be visible to certain team members, simply structure those areas into separate projects.

  • Organisation Library: While projects are independent, you aren’t starting from scratch, configurations, components, and GIS data stored in your library can be shared across all your projects effortlessly.

Organising your workspace with folders

To keep your organisation page professional and easy to navigate, you can group projects into folders. Simply click "New folder" to start structuring your space. There is no one-size-fits-all approach—create a structure that mirrors your organisation:

  • By Team: (e.g. "North Sea Development Team")

  • By Geography: (e.g. "Scotland", "Baltic Sea")

  • By Stage: (e.g. "Early Stage Screening" or "Tendering")

👉 You can also apply access control at the folder level to simplify permission management for entire groups of projects. Read more about access control here.

Branches

Branches are separate “scenarios” of your project. They allow you to develop multiple project scenarios in parallel without affecting the primary setup.

  • Parallel development: Test new ideas and keep a clear record of how your work evolves without disrupting the "main" design.

  • Enhanced collaboration: Team members can work independently on separate branches, reducing workflow conflicts and ensuring a smoother process.

  • Powerful comparisons: The primary advantage of branches is the ability to use the Compare to evaluate different setups side-by-side within the same project.

  • Hierarchical structure: To keep your work organised, you can structure branches hierarchically, group them into folders, or archive older versions for future reference.

Tool for efficiency: Scenario Manager

To manage your versions effectively, use the Scenario Manager. This tool is available by clicking the second button from the left in the branch tab bar.

The Scenario Manager helps you organise, visualise, and manage different branches within a project:

  • Visualise hierarchy: It displays how branches relate to one another in a nested tree-like structure (e.g. showing which versions were derived from which parents).

  • Adjust on the fly: You can easily reposition branches or adjust the hierarchy by dragging connections.

  • Define progress: Mark a "Base Case", add comments, duplicate branches, or include archived branches to track project history and versioning.

Did this answer your question?