> 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/frequently-asked-questions-faq.md). # Frequently Asked Questions (FAQ) Answers to the most common questions about BuildingPro Suites β€” the product, its architecture, connectivity, deployment, licensing, and the partner ecosystem. *** ## 🏒 General & Product ### What is ABB Abilityβ„’ BuildingPro Suites? ABB Abilityβ„’ BuildingPro Suites is a modular software platform that unifies building automation, HVAC, energy, OT, IoT, and IT systems into a single open and cybersecure environment. It transforms siloed building data into actionable, portfolio-level insights β€” helping building owners, operators, and system integrators improve energy efficiency, occupant comfort, sustainability, and operational performance. ### Who is BuildingPro Suites for? BuildingPro Suites supports a dual go-to-market model: * **System integrators** deploy the platform as a scalable digital foundation for their smart building projects. * **End users** β€” energy managers, facility managers, real estate managers, and sustainability leaders β€” adopt modular capabilities aligned with their operational priorities. It scales from a single building to an entire portfolio. ### What is the relationship between BuildingPro Suites and Eliona? BuildingPro Suites builds on software and intellectual property acquired by ABB, including the Eliona software platform and trademark. The technology is fully integrated into ABB's portfolio and continues to be developed and supported by ABB. You may still see the name "Eliona" in some documentation, developer resources, and app names during the transition. ### What can I achieve with the platform? Typical outcomes include reduced energy use, lower operating costs, improved space utilization, stronger asset visibility, predictive maintenance, and ESG performance tracking with sustainability reporting across building portfolios β€” enabled by real-time monitoring, analytics, and automation on a single data foundation. *** ## 🧱 Architecture & Suites ### How is BuildingPro Suites structured? Think of it as building blocks: * **Mandatory Base** β€” the foundation every installation includes: connectivity, asset modeling, identity, and governance. * **Platform toolbox** β€” optional platform capabilities such as dashboards, alarms, rules, tickets, analytics, and APIs. * **Suites** β€” domain-focused packages of modular software components, designed around validated user needs and practical job stories. You start with exactly what you need today and expand over time β€” adding Suites and Modules as requirements grow, without redesigning your system architecture. ### Which Suites are available? The software portfolio is organized into six domain-focused Suites covering **energy, operations, comfort, asset health, space, and grid interaction**. Each Suite consists of modular components, so customers can begin with targeted applications and scale across sites and portfolios. ### What is an "asset" in BuildingPro Suites? Assets are the central building blocks of the platform β€” think of them as containers for data points and information. Every sensor, device, or integrated system is represented as an asset with its own details, documents, and history. Asset Management gives you a complete overview, lets you store maintenance information and documents with versioning, and can synchronize documents via SharePoint for company-wide access. ### Where does the building structure come from β€” my BMS or BuildingPro? BuildingPro Suites owns the **canonical asset and location structure** (sites, buildings, floors, rooms, equipment). Data points from connected systems β€” BACnet, KNX, Modbus, and others β€” are then mapped onto that structure. Information from source systems (for example KNX group addresses) can serve as mapping hints, but the single source of truth for structure is the platform. This keeps the model consistent across all connected protocols and systems. *** ## πŸ”Œ Connectivity & Integration ### Which protocols and systems can I connect? BuildingPro Suites supports a broad range of interfaces, including: * **OT connectors** (also available remotely via EdgeNode): BACnet, KNX & KNX Secure, Modbus, M-Bus, OPC UA, SBUS * **IoT connectors**: MQTT, EnOcean, The Things Network, Loriot, Webhook, RESTful, Apache Kafka, and more * **BMS connectors**: B\&R Aprol, Siemens WinCC OA, Tridium Niagara (which itself opens up dozens of additional protocols) * **App connectors**: ABB free\@home, Akenza, Kentix, ROOMZ, Signify, Xovis, Microsoft 365, and many others from the Marketplace * **Escalation connectors**: e-mail, SMS, Slack, Google Chat ### What is the difference between a connector, an app, and the script engine? * **Connectors** are universal interfaces (MQTT, Webhook, RESTful, Kafka, OPC UA, …) designed for data exchange. They transmit data but are set up manually and don't create assets automatically. * **Apps** offer the deepest integration: they connect BuildingPro Suites with other systems *and* automatically create and synchronize the matching assets β€” including advanced functions like alarm processing, login, or booking. * **The script engine** enables lightweight integrations via SQL or Python scripts for simple, specific tasks. ### Can I connect buildings that have no direct cloud connectivity? Yes. OT protocols such as BACnet, KNX, Modbus, M-Bus, and OPC UA can also be connected remotely via **EdgeNodes** β€” edge devices that handle local fieldbus communication and link the site securely to the platform. ### My system isn't on the connector list. What are my options? There are several paths, in increasing depth: 1. **Data-only**: send data via standard interfaces such as MQTT, REST/Webhook, or OPC UA. 2. **App development**: build (or commission) a Marketplace app using the App SDK, with automatic asset creation. 3. **Embedded UI**: integrate an existing partner user interface into the platform. 4. **Co-development**: build a full native module together with ABB. See the **Partner Studio Guide** for details on all four options. *** ## 🍎 Apps & Marketplace ### What is the Marketplace? The Marketplace is the central hub for extending platform functionality with apps β€” official apps provided or verified by BuildingPro Suites. Apps cover system integrations (e.g., occupancy sensors, lighting, room booking) as well as platform extensions such as SSO, escalations, and notifications. Most apps can be installed and configured in minutes. ### How are apps built technically? Apps follow a microservice architecture: each app runs as a standalone container. This keeps the system modular, scalable, and fault-tolerant β€” every app can be deployed, updated, and maintained independently, both during integration of new functions and in daily operation. ### Can I develop my own app? Yes. The **App SDK** provides client libraries, an app template, and a mock environment for development and testing. Apps interact with the platform exclusively through the REST API and WebSockets and can automatically create assets, KPIs, and dashboards. Development of new apps requires technical know-how and is typically done by BuildingPro Suites or trained partners β€” see the App SDK documentation and the public GitHub organization to get started. *** ## πŸ€– Artificial Intelligence ### What AI capabilities does BuildingPro Suites offer? The platform includes AI capabilities for orchestration, analytics, and user assistance β€” for example, AI-supported recommendations that suggest the most relevant features based on your goals and challenges, and AI functions embedded in analytics and reporting workflows. See the chapter *Artificial intelligence in ABB BuildingPro* in the documentation for the current feature set. ### Is there help choosing the right features for my use case? Yes. The **Smart Recommendations with AI** advisor lets you describe your goals or challenges in plain language and suggests the most relevant BuildingPro Suites features and modules for your situation. *** ## πŸ’Ά Licensing & Commercial Model ### How is BuildingPro Suites licensed? BuildingPro Suites is offered through a flexible, **utilization-based commercial model** that scales according to data points and the software modules you select. You only license what you actually use β€” and can expand as your portfolio grows. ### Can I start small and grow? Yes β€” that is the core design principle. Start with a targeted use case (for example, energy monitoring for one building), then add Suites, Modules, and sites over time without re-architecting. The modular structure means your initial investment carries forward as you scale. ### Where do I get a quote? Licensing is provided through ABB and its partner network. Contact your ABB representative or the BuildingPro Suites team for a tailored offer based on your portfolio size, data points, and selected modules. *** ## πŸ” Deployment, Security & Data ### Is BuildingPro Suites cybersecure? Security is a foundation of the platform: BuildingPro Suites provides a single open and **cybersecure** environment with identity and governance as part of the Mandatory Base. Enterprise features such as SAML SSO are available, and role-based access control governs what each user can see and do. ### How is user access managed? The platform provides user and role management with fine-grained permissions. Single sign-on can be enabled via the SAML SSO app, allowing integration with your corporate identity provider. ### Who owns the data? Your building data remains yours. The platform gives you data sovereignty and a reliable single point of information β€” including versioned document storage on assets that can be shared across departments, with or without a platform login. *** ## πŸš€ Getting Started & Support ### How do I get started? The documentation includes a guided **Getting Started** path: (1) create users & projects, (2) set up assets, (3) connect data sources, (4) visualize & use data. New users also get an **interactive onboarding tour** β€” the first time you open a page, a short step-by-step introduction explains its main functions. ### Where do I find training material? The **Academy** section of the documentation provides structured learning content β€” from platform fundamentals and ontology concepts to Marketplace apps and practical configuration guides. ### Where do I find the full documentation? At [docs.buildings.ability.abb](https://docs.buildings.ability.abb/). Every page is also available as Markdown, and the complete documentation index is published as `llms.txt` β€” useful for AI assistants and automated tooling. A built-in AI support assistant helps you find the right page quickly. ### How do I report a bug or give feedback? Use the **Feedback** and **Report a bug** sections linked directly in the documentation, or contact your ABB support channel. ### I'm a startup or technology partner β€” how can I integrate or co-develop? See the **Partner Studio Guide**: it describes the four integration paths (data-only, Suites App, embedded UI, and full module co-development), including architecture diagrams, technical requirements, and the commercial framework β€” and how to schedule a scoping workshop with the BuildingPro Suites partner team. --- # 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/frequently-asked-questions-faq.md?ask=&goal= ``` `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.