> 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/mandatory-base/platform-core/connect-hub.md).

# Connect Hub

Connect Hub is the part of Platform Core where external systems are connected to BuildingPro Suites, incoming data is prepared for use inside the platform, and test data can be generated without physical devices.

It covers the full technical path from connection setup to secure communication and payload processing. This makes Connect Hub the central area for integrators and administrators who need to bring data from third-party systems into the shared BuildingPro Suites data model.

## What You Can Do in Connect Hub

Within Connect Hub, you can:

* configure protocol-based connections in [Connectivity as a Service](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service.md)
* define mappings and transformations in [Data processing (Function/Formats)](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/data-processing-function-formats.md)
* install and manage integrations in [Edge/App Marketplace for plug-ins & extentions](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/edge-app-marketplace-for-plug-ins-and-extentions.md)
* generate and manage test data for assets and attributes in [Device Simulator](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/device-simulator.md)
* manage certificates for secure communication in [PKI](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/pki.md)

## How the Areas Work Together

In a typical setup, a connection is first created to receive data from an external system. The incoming data is then decoded, transformed, and mapped to the correct assets and attributes. If needed, supporting apps or certificate-based trust settings are added as part of the same integration flow.

For testing without a physical connection, Device Simulator can generate values for dedicated virtual assets or selected attributes of existing assets.

Connect Hub therefore combines connectivity, integration management, simulation, data preparation, and security in one place.


---

# 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/mandatory-base/platform-core/connect-hub.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.
