Skip to content

Nepenthes BIM edition

Installing Nepenthes BIM edition

For installing the Nepenthes BIM edition please follow the general system requirements and installation guidelines. Under Step 1 please select Nepenthes BIM.

Changing to Nepenthes BIM edition

An existing Nepenthes installation can easily be switched to the BIM Edition. The BIM Edition extends the capabilities of a normal Nepenthes installation with special features for the construction industry.

Switching to the BIM Edition will not affect your existing data. Your team will be able to continue working just as before. By switching to the BIM edition additional features will become available when you activate the "BCF" module in the project's settings.

Backup and upgrade

First, backup your data and update your installation to the latest Nepenthes version as described in Upgrading. Make sure that you not only install the new package but also run sudo openproject configure as described before proceeding.

Switching to BIM Edition

Now that your Nepenthes instance is up to date, you can reconfigure it to be a BIM Edition.

On the command line of your server run the following command. It will open a wizard that guides you through through the most important installation settings of your instance. On the first screen it will ask you to select the edition. Please select bim and click next. You can keep the screens that follow just as they are. You don't need to change any setting. Your current settings will be preselected for you. You can simply click "next" in every step until the end of the wizard. Finally, this will also trigger the installation of the necessary libraries and tools for 3D model conversion.

sudo openproject reconfigure

Congratulations, you've successfully switched to the BIM Edition. However, for the best experience you might consider also the next configuration.

You can check that all tools for the IFC model conversion were installed by going to -> Administration -> Information and check that IFC conversion pipeline available has a check icon (✓) to the right.

Activating the BCF module per default for every new project (optional)

You can enable the BCF module per default for all new projects in the future.

Go to -> Administration -> System settings -> Projects and within the section Settings for new projects activate the checkbox for BCF.

Add typical work package types and statuses for BCF management (optional)

For BCF management process you might want to add special work package types to your installation.

In freshly created Nepenthes BIM instances those types are already present. However, as you have just switched from a normal Nepenthes installation you will need to create those work package types by hand. Please find detailed instructions on how to add work package types in Manage Work Package Types.

You might consider adding the following typical work package types:

  • Issue (color indigo-7)
  • Clash (color red-8)
  • Remark (color GREEN (DARK))
  • Request (color cyan-7)

We recommend that each type has the following status options:

  • New (color blue-6)
  • In progress (color orange-6)
  • Resolved (color 'green-3)
  • Closed (color 'gray-3)

Activating the "Nepenthes BIM" theme (optional)

You can optionally switch to the BIM theme.

Go to -> Administration -> Design and from the Themes drop down menu choose Nepenthes BIM.

Docker installation Nepenthes BIM

Nepenthes BIM edition with Docker Compose

In order to use BIM edition inside a docker-compose Nepenthes installation, in the docker-compose.override.yml file in x-op-app > environment add one line


This could look like this after editing file:

x-op-app: &app
  <<: *image
  <<: *restart_policy
    DATABASE_URL: "postgres://postgres:p4ssw0rd@db/openproject"
    USE_PUMA: "true"
    # set to true to enable the email receiving feature. See ./docker/cron for more options

Note: If the current Docker installation does not yet hold important information it is recommended to simply create all docker containers from scratch as the seeded data such as themes, types, and demo projects are different in the BIM edition. The demo data gets seeded only at the very first time run of the container. The Docker volumes are required to be removed e.g. by issuing docker-compose down --volumes