> 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/suites/suites-coming-soon....md). # Suites coming soon... ABB Ability™ BuildingPro Suites is a unified cloud intelligence platform for integrated building and portfolio management. It connects building automation, Heating, Ventilation, and Air Conditioning (HVAC), energy, Information Technology (IT), and Operational Technology (OT) systems to turn real-time building data into actionable insights. {% hint style="info" %} #### Update We are actively working on the next phase of our Suites experience, including AI-related capabilities. Our teams are working hard on this, and we will share more information as soon as further details are available. {% endhint %} ### What BuildingPro Suites already stands for BuildingPro Suites is designed to help organizations: * connect siloed building and Internet of Things (IoT) data * gain real-time visibility across buildings and portfolios * improve operational efficiency * support sustainability goals * enable smarter, data-driven decisions ### A platform built to scale The platform is designed to scale: * from a single building to an entire portfolio * from one data source to multiple sources * from one application to many ### More to come Detailed information about Suites and Modules is currently being prepared. Please check back soon for further updates. --- # 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/suites/suites-coming-soon....md?ask=&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.