What Should You Check Before Connecting Existing Building Systems?

Hearing “Yes, we can integrate with your BMS” is a good starting point when you evaluate a building platform. However, the next question will undoubtedly be what that integration will let your team do.

Think of your operators. Will they be able to review equipment status and historical trends? What about investigating alarms or adjusting a schedule? Are there still tasks that will need another interface or site visit?

These details matter to owners who manage different control vendors. A building systems integration needs to support all of the work that teams carry out every day.

That means that as a buyer, you will have to check how well a platform can monitor and automate third-party systems.

Unified building orchestration connects monitoring, analysis, control and verification in one platform. It organizes data from different systems around the equipment and spaces they serve, so teams can investigate issues, make changes and check the results.

That is why, to evaluate a platform, teams need to understand how its integrations support this process.

Five Checks to Make Before Connecting Existing Building Systems

Here are five areas to review, and how KODE OS addresses them.

1. Which Existing Systems Need to Be Connected?

Start with systems that your team already uses. You will need to record the manufacturers and software versions as well as available interfaces and the operating tasks you want to support.

Investigating a comfort complaint might require pulling information from the BMS and room sensors. When you review after-hours operation, it might include occupancy, lighting or metering information as well.

KODE’s integration library includes categories from building controls, lighting, occupancy, meters, to work order systems. This lets you plan the integration scope around the systems you already use in your operations.

    

             

KODE currently builds and maintains more than 250 connectors in-house. That is why owners don’t need to standardize their portfolio based on a specific manufacturer.

However, each site still needs to be assessed based on its available interfaces, access, and other requirements. That review shows us what can be delivered with your existing systems and where additional configuration might be needed.

For the owner, this means that the starting point is the portfolio they have today.

2. What Information Does Your Team Need to Investigate Problems?

For familiar tasks, operators will need specific readings and records. That’s why they need to be investigated. 

Let’s say there’s a hypothetical complaint about a warm office. Seeing the current room temperature shows you the condition, but the operator will also need to know when it started and how the equipment behaved during that time.

Multi-Point Trending lets you compare several connected points in one chart where you can select a time range and save a view for later use. Based on the example, this would mean comparing available temperatures and equipment-status trends.

    

             

Additionally, Building BI expands this analysis to dashboards and reports. It offers a variety of filters such as building, equipment type and time period. Based on this, teams can review portfolio performance and investigate more specific operating information.

    

             

3. What Should Operators Be Able to Do?

First, we need to clearly define the actions your team needs to perform and the information they need to access.

Managing schedules, centralizing alarms and executing mass actions on compatible devices are all features KODE offers.

In the warm office scenario, an operator could review the schedule or adjust a setpoint after assessing the current conditions. Then the actions available depend on the connected systems and its specific setup.

KODE OS also lets teams set permissions for accessing different platform functions. During this implementation, it’s important to determine who can view information, who can make changes and which questions require approval.

Local control sequences, interlocks and site procedures remain part of that operating environment.

Unified building orchestration works on this defined scope:

• The available action
• The person who is authorized to take that action
• The equipment response that teams expect to see

4. Can the Information Be Linked to the Right Equipment and Spaces?

An operator that is currently investigating Room 301 needs to know the equipment serving it and locate the readings.

KODE OS employs a standardized data model to define equipment, spaces, and their relationships. This approach gives context for connected information, even when different systems use various naming conventions.

    

             

KODE also offers interactive floor plans that allow teams to see the locations of devices and monitor real-time conditions in the spaces they manage.

    

             

In the warm-office example, the context helps link the affected room to the relevant equipment and details for the investigation. This gives the operator a clear starting point to understand the problem.

This is a crucial aspect of unified building orchestration: information from different systems can be integrated and utilized within the same operational task.

Before connecting a building, make sure that the necessary equipment, points, and spatial relationships for your intended workflows are included in the implementation scope.

5. What Work Is Needed to Get the Connections Ready?

A useful connection depends on 4 major points. Those are access, configuration, validation, as well as compatibility.

KODE’s implementation approach begins by focusing on the desired outcomes of the owner and reviewing the current infrastructure. This gap analysis helps identify relevant use cases and any necessary system improvements.

Next, the process involves ensuring connectivity, as well as validating and normalizing data, before moving into operational workflows and optimization.

For the owner, practical preparation includes identifying network and access requirements, determining any licenses or gateways needed, and assigning responsibility for equipment mapping and validation.

It’s also important to agree on how to manage ongoing changes. System upgrades, credential management and modifications to connected equipment should have designated owners and support systems in place.

How Do These Connections Support Unified Building Orchestration?

Once the relevant systems are connected and their data is organized, teams can work together more effectively.

If a team is looking into a warm office, they might check connected data trends, identify any operational issues and then either make an approved adjustment or schedule any necessary repairs. After that, they can monitor the performance to see the results of their actions.

KODE’s Functional Testing Tool can test the sequences of equipment and provide results to confirm the system’s performance after repairs have been made.

    

             

This approach creates a cohesive process that connects investigation, action and outcomes, which is also the goal of unified building orchestration.

KODE Labs was named a Leader in the Verdantix Green Quadrant for Unified Building Orchestration Platforms 2026. The research’s focus on mixed-vendor connectivity and operational depth reflects the questions owners need answered when connecting their buildings.

See how KODE OS connects your existing systems and puts them to work together.

See a Demo | Explore Unified Building Orchestration with KODE

FAQ

Frequently Asked Questions

Can KODE OS work with different controls vendors?

KODE OS connects mixed-vendor environments through its integration library. Compatibility and available functions should be confirmed for the systems, versions and interfaces in each building.

Does Connecting KODE OS require replacing the existing BMS?

KODE OS can work alongside an existing BMS, which continues to perform its local control functions. The deployment scope depends on the building’s infrastructure and intended use cases.

Can operators control equipment through KODE OS?

KODE OS supports functions such as schedule management and mass actions through supported connections. Available commands depend on the integration, configuration and user permissions.

How does building systems integration support unified building orchestration?

Integration makes information and supported commands available across systems. Unified building orchestration uses those connections and shared context to coordinate operational workflows and check results.