A property management company in Warsaw spent six months implementing an IoT platform, only to discover that the sensors were incompatible with the existing BMS and the vendor did not support the required protocols. The project had to start from scratch. Most mistakes like this happen not because of the wrong equipment, but because of the wrong sequence of questions during the selection process.
This guide will help you ask the right questions before signing a contract with a vendor.
Step 1\. Define the Task Before Choosing the Technology
The most common mistake is starting the selection with a product rather than a problem. An IoT system for energy consumption monitoring, a system for predictive equipment maintenance, and a system for access control are different products with different architectures.
Before evaluating vendors, answer three questions:
What exactly do you want to measure or control? Energy consumption by zone, the condition of engineering equipment, indoor climate, occupancy, security — each task requires its own set of sensors and platforms.
Who will use the system? Technical staff need detailed operational data. An owner or investor needs consolidated reporting. Tenants need mobile access to the metrics for their own space.
What is the property or portfolio? A solution for a single office building and a solution for a network of 20 properties have different requirements for scalability and centralised management.
Step 2\. Verify Protocol Compatibility
Technical compatibility is the most common source of problems when integrating IoT into existing buildings. Ask the vendor:
- Which protocols does the platform support: BACnet, Modbus, KNX, Zigbee, Z-Wave, MQTT?
- Is the solution compatible with existing equipment in the building (HVAC controllers, meters, security systems)?
- Is there an open API for integration with the BMS and other management systems?
If a vendor offers exclusively proprietary hardware and does not support open protocols, this signals a vendor lock-in risk. Within three to five years, you will be unable to connect new devices or switch platforms without replacing the entire infrastructure.
Step 3\. Evaluate the Data Processing Architecture
A question that is often overlooked during selection: where is data stored and processed?
- Cloud architecture is convenient for access from any device and centralised portfolio management, but requires a stable internet connection and raises questions about data protection.
- Edge computing — processing data directly on a gateway within the building — reduces network dependency and minimises response latency. Relevant for critical equipment and properties with elevated security requirements.
- A hybrid model combines both approaches: critical operations are handled locally, while analytics and reporting run in the cloud.
Ask the vendor about data storage conditions, backup procedures, and GDPR compliance if you operate properties in the EU.
Step 4\. Verify Scalability
A system that works well for one building does not always scale to a portfolio. Key questions:
- Can new properties be connected without changing the architecture?
- How does pricing change as the number of sensors or properties grows?
- Does the platform support a centralised dashboard for comparing metrics across properties?
If you manage or plan to manage multiple buildings, set the requirement for a multi-property architecture from the very beginning.
Have a specific property or portfolio and want to understand which IoT architecture is right for you? The ORIL Innovation team advises property management companies and developers on selecting and integrating Smart Buildings solutions — from technical audit to system architecture design. Book a Consultation →
Step 5\. Evaluate the Vendor, Not Just the Product
The technical specifications of a platform are only half of the decision. The other half is vendor reliability and support terms.
Check:
- Whether there are completed case studies on properties similar to yours in type and scale
- What the technical support format looks like: SLA, response time, availability of a local team
- What happens to your data if you decide to change vendor
- Whether a product development roadmap exists and how frequently updates are released
A vendor that avoids specific answers to these questions or has no verified case studies represents an additional risk for your project.
Step 6\. Calculate the Real Cost of Implementation
The price of the platform itself rarely reflects the full project cost. The budget must account for:
- Hardware: sensors, gateways, actuators, cabling infrastructure or wireless modules
- Installation and configuration: particularly in existing buildings, where retrofit is more complex and expensive than new construction
- Integration: connecting to BMS, metering systems, ERP or ESG platforms
- Team training: operational staff must be able to work with the system without ongoing dependence on the vendor
- Technical support and updates: annual platform maintenance cost
A practical benchmark: the full cost of implementing an IoT system in an average commercial building is typically two to three times higher than the cost of the platform licence alone.
Checklist Before the Final Decision
Before signing a contract with a vendor, confirm that you have answers to every item:
– [ ] System objectives are clearly defined and agreed upon with the team
– [ ] Supported equipment protocols have been verified for compatibility with existing infrastructure
– [ ] Data processing architecture (cloud / edge / hybrid) matches security requirements and operational needs
– [ ] Scalability has been verified for the current and planned portfolio
– [ ] The vendor has provided verified case studies on comparable properties
– [ ] SLA and technical support terms are documented in the contract
– [ ] Full implementation cost has been calculated including hardware, integration and training
– [ ] Contract exit terms and data portability conditions are specified
Want to go deeper into IoT architecture and how smart building systems work before making a decision? Listen to the Innovation Blueprint podcast — conversations with engineers and systems architects on real-world solutions in Smart Buildings. Listen to Innovation Blueprint →
Choosing an IoT system for a building is a five-to-ten-year decision. Asking the right questions at the start saves time, money and headaches far more effectively than any analysis conducted after the system is already installed.