> 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/overview/mandatory-base-platform-suites-and-modules.md).

# Mandatory Base, Platform, Suites & Modules

Understanding how the Platform Core, Platform, Suites, and Modules work   together in ABB Ability™ BuildingPro Suites.

ABB Ability™ BuildingPro Suites is built around a layered architecture that gives you full control over what you deploy and how you grow. Every deployment starts from the same mandatory foundation, and everything above it is assembled to match your specific needs.

There are three core concepts to understand:

* **Mandatory Base** — the foundation included in every deployment, providing connectivity, asset modeling, user management, and governance. Without it, nothing else runs.
* **Platform** — a comprehensive solution that unlocks the full capabilities of BuildingPro Suites, giving teams and integrators the complete toolbox to build tailored smart building solutions.
* **Suites and Modules** — outcome-focused packages that deliver measurable results in specific domains such as energy, occupant comfort, operations, and more. Each Suite contains Modules that address concrete use cases.

{% hint style="info" %}
Not sure which Suites or Modules fit your needs? Click below to chat with our AI Advisor.
{% endhint %}

{% embed url="<https://stage.advisor.buildings.ability.abb/ai-recommendation>" %}

***

## How It Fits Together

Think of it like building with blocks. The Mandatory Base is always the foundation, it is included in every deployment and cannot be removed. On top of it, you choose your path:

* Choose **Platform** if you need the full toolbox and maximum flexibility to build, extend, and customize your solution across any building type or portfolio.
* Choose **Suites and Modules** if you want to go live fast with defined, outcome-focused packages tailored to specific domains, and expand gradually.

Both approaches can be combined. Platform and Suite modules are complementary, not mutually exclusive.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/overview/mandatory-base-platform-suites-and-modules.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.