> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/support-center/deployment-guide.md).

# Deployment Guide

Cloud and on-premises deployment requirements and options for ABB Ability™ BuildingPro Suites

This guide describes the system requirements, architecture, network configuration, hosting models, deployment options, and backup strategy for **ABB Ability™ BuildingPro Suites** cloud and on-premises installations.

## System Requirements

The following requirements apply to a BuildingPro Suites installation:

| Component        | Minimum          | Recommended                       | Notes                                                           |
| ---------------- | ---------------- | --------------------------------- | --------------------------------------------------------------- |
| Processor        | 8 CPUs           | 16 CPUs                           | Additional capacity may be required for larger installations.   |
| RAM              | 32 GB            | 64 GB                             | Additional memory may be required for data-intensive workloads. |
| Storage          | 1 TB SSD         | Based on the expected data volume | Storage is used primarily for trending data.                    |
| Operating system | Ubuntu 24.04 LTS | Ubuntu 24.04 LTS                  | Use a supported and maintained Ubuntu installation.             |

An internet connection specified by the integrator is required for installation and maintenance. Some functions also require a permanent internet connection during operation.

{% hint style="info" %}
Storage requirements can vary considerably depending on the system environment, the volume and retention period of trending data, and the space needed for updates. Storage requirements must therefore be assessed individually, especially for cloud and on-premises installations.
{% endhint %}

## Certificates and Encryption

Self-signed certificates are considered insecure and are marked as such by browsers. They can also prevent devices from some manufacturers from accessing BuildingPro Suites. Use certificates issued by a recognized certificate authority, such as Let's Encrypt, SwissSign, or VeriSign.

## Ports

The following ports must be accessible when the platform is reached from outside the hosting environment:

<table><thead><tr><th width="113.199951171875">Port</th><th>Purpose</th></tr></thead><tbody><tr><td>22</td><td>Deployment of BuildingPro Suites and automatic updates.</td></tr><tr><td>443</td><td>Encrypted browser and app access to BuildingPro Suites.</td></tr><tr><td>8883</td><td>Encrypted MQTT access to BuildingPro Suites.</td></tr><tr><td>9092</td><td>Encrypted Kafka access to BuildingPro Suites.</td></tr></tbody></table>

Ports **8883** and **9092** must be opened when Kubernetes is used. Some external load balancers only permit ports in the range **30000–32000**. In that case, port forwarding is required. Within the Kubernetes cluster, MQTT uses port **31833** and MQTTS uses port **31888**.

## Hosting

BuildingPro Suites is available through ABB Cloud in Germany or as a virtual machine image.

<table><thead><tr><th width="227.60009765625">Hosting model</th><th>Environment</th></tr></thead><tbody><tr><td>ABB Cloud</td><td>Hosted service in Germany.</td></tr><tr><td>Virtual machine image</td><td>Customer-managed virtual machine.</td></tr></tbody></table>

```mermaid
flowchart LR
	BPS[BuildingPro Suites]

	subgraph Cloud[ABB Cloud]
		BPSC[Hosted service in Germany]
	end

	subgraph Client[Customer-managed environments]
		VM[Dedicated virtual machine]
	end

	BPS -->|Cloud hosting| BPSC
	BPS -->|Customer installation| VM
```

ABB Cloud is hosted in Germany. Customer installations use a dedicated virtual machine.

### AI Features in On-Premises Installations

Not all AI features are available in on-premises installations. Some features use Microsoft Azure AI models and require an internet connection.

Some models can run locally but need substantial compute resources. Larger models may require dedicated GPU capacity and are not suitable for every on-premises environment.

### Managed Service

For stable and reliable long-term operation, a managed service is strongly recommended. It includes regular database maintenance and monitoring of relevant system logs, helping maintain a consistent and high-performing system environment.

## Deployment Options

```mermaid
flowchart TB
	BPS[BuildingPro Suites Platform]

	BPS --> D1[1. ABB Cloud]
	D1 --> CLOUD[Hosted service in Germany]

	BPS --> D2[2. Virtual machine image]
	D2 --> VM[Customer-managed virtual machine]
```

### 1. ABB Cloud

Access to ABB Cloud is included in the subscription price and provided as part of the service package. The service is hosted in Germany. A Deployment Package is required for the initial setup. Refer to the applicable price list for details.

### 2. Virtual Machine Image

BuildingPro Suites is delivered as a virtual machine with a preconfigured installation image. A Deployment Package is required for the initial deployment in the target environment. Additional integration work in the customer's data center is billed according to the actual time and materials required.

## Backup and Disaster Recovery

The backup strategy follows a modular approach that treats different data types separately. This improves availability, shortens recovery times, and minimizes data loss.

### Separation of Concerns

<table><thead><tr><th width="188.199951171875">Data category</th><th width="382.2000732421875">Description</th><th>Change frequency</th></tr></thead><tbody><tr><td>Schema</td><td>Database structure required for the platform to function.</td><td>Infrequent</td></tr><tr><td>Configuration</td><td>Users, tenants, rules, and other operational settings.</td><td>Moderate</td></tr><tr><td>Measurement data</td><td>Continuously growing time-series and trending data.</td><td>Continuous</td></tr></tbody></table>

Each category uses a backup method and frequency appropriate to its importance, size, and rate of change.

### Recovery Time Objective

The Recovery Time Objective (RTO) defines how quickly a system or data category should be restored:

<table><thead><tr><th width="199.60009765625">Data category</th><th>Recovery objective</th></tr></thead><tbody><tr><td>Schema</td><td>Recovery within seconds, for example after a failed update.</td></tr><tr><td>Configuration</td><td>Recovery within minutes after a misconfiguration or deletion.</td></tr><tr><td>Measurement data</td><td>Staged recovery over a longer period because of the larger data volume.</td></tr></tbody></table>

### Recovery Point Objective

The Recovery Point Objective (RPO) defines the maximum acceptable period of data loss:

<table><thead><tr><th width="188.4000244140625">Data category</th><th>Backup interval</th></tr></thead><tbody><tr><td>Schema</td><td>Weekly, because changes are infrequent.</td></tr><tr><td>Configuration</td><td>Daily, to preserve current operational settings.</td></tr><tr><td>Measurement data</td><td>Every six hours, limiting potential data loss to a few hours.</td></tr></tbody></table>

### Benefits

This strategy reduces backup duration and storage requirements. It enables targeted restores without unnecessarily overwriting unaffected data and reduces downtime. Clear recovery paths support incidents ranging from individual configuration errors to complete database loss.

An individual backup and disaster recovery strategy, including one tailored to an on-premises installation, is defined and implemented through a separate service-level agreement (SLA).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/support-center/deployment-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.