Integrations

Can Beckhoff communicate with systems from other manufacturers?

Yes. Beckhoff forms the central automation layer within TIBA3, but the connected field devices do not have to be from Beckhoff.

Open communication protocols

Through protocols such as Modbus, BACnet, KNX, DALI-2, M-Bus, OPC UA, and other common standards, the central controller can communicate with devices and installations from various manufacturers.

Freedom in component selection

This allows the most suitable device to be chosen for each application based on functionality, quality, availability, and price. The customer is therefore not obliged to purchase all components within a single brand or product family.

Integration of existing installations

Existing systems can also often be retained if they communicate via a standard protocol, API, or suitable interface.

Technical assessment per connection

Not every connection automatically offers the same functionality. Fixsus therefore assesses per device or system which data can be read, which commands can be written, and which conditions apply for reliable integration.

Can energy meters from different brands be read?

Yes. Energy and water meters are typically read via M-Bus or Modbus, regardless of the brand.

Open communication protocols

M-Bus and Modbus are open standards supported by almost all energy meter manufacturers. This allows you to choose your meters based on quality and price, rather than brand loyalty.

All measurement data on a single platform

Measurement data from all meters is consolidated within the energy management system on the same platform. This allows you to monitor electricity, gas, and water consumption centrally, making any deviations quickly visible.

Can Fixsus collaborate with my installer, integrator, or engineering firm?

Yes. Fixsus collaborates on projects with installers, integrators, engineering firms, and other technology partners. The precise division of tasks is clearly established in advance.

Collaboration based on expertise

Fixsus can be responsible for, among other things:

• the system architecture;
• the programming of TIBA3;
• the integration of building technologies;
• the visualization;
• the commissioning;
• the functional tests;
• training and further support.

The installation partner may, for example, be responsible for cabling, assembly, control cabinets, and the connection of field components.

Clear scope of work

Before the start of the project, it is determined who supplies which materials and who performs which activities. This avoids overlaps, missing items, and disputes during execution.

Support for local partners

For projects outside our familiar region, Fixsus can collaborate with a local technical partner. They understand the local market, regulations, and service expectations, while Fixsus supports the TIBA3 technology and project-specific knowledge.

Also for Beckhoff integrators

Integrators with experience in Beckhoff, TwinCAT, and building technology can incorporate TIBA3 and Fixsus hardware into their own projects. Depending on the collaboration, Fixsus can offer support with design, programming, training, and the initial project implementations.

No mandatory full takeover

Fixsus does not necessarily have to perform all technical disciplines itself. The goal is a workable project organization in which each party takes responsibility for its own expertise.

Can Fixsus hardware also be used without TIBA3?

Yes. Fixsus hardware has been developed to work optimally with TIBA3, but it is not exclusively tied to TIBA3.

Open communication

Fixsus field devices communicate via standard Modbus RTU. As a result, they can also be used in other building management systems or automation platforms that work with Modbus.

Central intelligence

The devices do not contain closed, project-specific logic. That intelligence is organized centrally within the system in which the hardware is integrated.

Integration by third parties

An external integrator can include the devices in their own central control system and is then responsible for the programming, addressing, and functional integration.

Fixsus can provide the necessary technical documentation, communication data, and product support for this purpose.

Can I export the data or use it externally?

Yes. Through Fixsus Open Gate, the platform’s REST API, every variable and measurement series can be read by external software.

Integrate with your own tools

Consider energy platforms, BI tools, dashboards, or your organization’s data warehouse: they can draw directly from the building’s measurement data.

Open instead of locked in

The data is not locked in a manufacturer’s closed environment. What the building measures belongs to you and is fully accessible.

Can nurse call and building management be integrated into a single system?

Yes. Fixsus Cura combines nurse call, room control, presence registration, and climate information into a single room solution, managed within the open building management platform.

A single room solution

The Cura Base Station integrates nurse call, badge sign-in, and climate measurement into a single wall-mounted unit. The Cura Pager provides residents with peace of mind through illuminated buttons and a short vibration confirming the call has been sent. With the Cura Pager Domo, they can also control lighting and sun blinds from their bed. Where only a wall-mounted call button is required, the Cura Base Badge is sufficient.

No parallel systems

Nurse call no longer runs alongside building technology, but within it. No duplicate infrastructure, no separate supplier, and no second system to maintain.

For new construction and renovation

The solution is maintenance-friendly and suitable for both new construction and renovation projects. In this way, the care room becomes the starting point of a building architecture that functions today and expands tomorrow.

Can other programmers or integrators work on the installation later?

Yes. TIBA3 is deliberately designed so that the customer is not technically excluded from their own installation.

Open and transferable architecture

The installation utilizes standard industrial hardware, open communication protocols, and a structured project design. This allows a technically qualified third party to maintain, modify, or expand the installation at a later date.

Availability of information

The programming, diagrams, settings, and technical documentation can be made available to the end customer or another authorized integrator under agreed conditions.

Required expertise

Another party must possess the necessary knowledge of Beckhoff, PLC programming, building technologies, and the communication protocols used.

Controlled handover

To avoid errors, security risks, and ambiguity regarding responsibility, a handover is best conducted in a structured manner with clear agreements on source code, documentation, access rights, and liability.

Can sustainable technologies such as geothermal energy be integrated?

Yes. Sustainable technologies are included in the building’s central control system.

From geothermal energy to heating networks

Geothermal energy (ATES/BTES), heating networks, hybrid heat production, and solar energy can be fully integrated into the platform.

The most sustainable source first

Because all sources are managed within the same central control system, the most cost-effective and sustainable source is always prioritized. This ensures you achieve the maximum return on your sustainable investments.

Can the system manage charging stations intelligently?

Yes. Charging station power management is one of the technologies that can be integrated into the platform.

Distributing power intelligently

The charging station power management distributes the available power across the charging points while taking other building consumption into account.

Staying within the connection capacity

This ensures that the grid connection capacity is not exceeded, even when many vehicles are charging simultaneously. After all, the building and the charging infrastructure share the same central control and the same measurement data.

Can TIBA3 also integrate a closed or outdated system?

In many cases, yes. Fixsus first investigates which installations, signals, and communication channels are available and then determines how the existing system can collaborate with TIBA3.

Direct coupling via a protocol

When the existing system supports a usable communication protocol, TIBA3 can read data and, where permitted, also send back commands.

This can be done, for example, via BACnet, Modbus, KNX, OPC UA, a REST API, or another available interface.

Coupling via hardware signals

When digital communication is not possible, certain functions can sometimes still be linked via classic input and output signals, such as:

• potential-free contacts;
• digital notifications;
• analog measurement and control signals;
• pulse outputs from meters.

The available information is then more limited than with a full protocol coupling.

Retention of the existing subsystem

A closed installation does not always have to be replaced entirely immediately. It can temporarily continue to function as an independent subsystem, while TIBA3 centrally consolidates the available statuses, alarms, or main commands.

Phased migration

When an old system is technically difficult to integrate, Fixsus can develop a migration path. In this process, components are replaced step-by-step as soon as it is technically, operationally, or financially most appropriate.

Preliminary technical analysis

Feasibility depends on the available documentation, protocols, access rights, interfaces, and support from the original supplier. Therefore, every coupling is technically investigated in advance.

Can TIBA3 be integrated with external software or platforms?

Yes. TIBA3 can exchange data with external software, dashboards, energy platforms, and other management systems.

Fixsus Open Gate

The integration can be facilitated through Fixsus Open Gate, a REST API that makes TIBA3 data available to other applications.

Read and write

External software can not only read measured values, alarms, statuses, and energy data, but can also write values, setpoints, or commands to TIBA3 within the defined permissions.

Possible applications

This enables the integration of facility management software, reservation systems, energy platforms, BI tools, dashboards, and data warehouses, among others.

Technical assessment

Each integration is subject to a technical assessment. This evaluation considers the available interface, the required data exchange, read and write permissions, cybersecurity, and the responsibilities of the respective systems.

Does the integration work in both directions?

Yes. External software can not only read data, but also write setpoints and commands.

Reading and writing via the REST API

Through Fixsus Open Gate, the platform’s REST API, every PLC variable can be both read and written. Two-way communication is also possible via the supported protocols.

Within the access rights you define

The writing of values naturally occurs within the access rights that you set yourself. This allows you to determine which external systems are only permitted to monitor and which are also allowed to control.

Does the platform support DALI lighting?

Yes. DALI and DALI-2 are standard components of the architecture.

One DALI line per zone

A DALI line runs from each zone to the fixtures and emergency lighting. This ensures that lighting is fully controlled on the same platform as the other technical systems.

Other lighting controls can also be connected

Controlling lighting via other systems is also possible, for example, linked lighting controls via BACnet. This allows existing lighting infrastructure to be included in the management system.

How do sun protection, lighting, and climate control work together energy-efficiently?

TIBA3 allows sun protection, lighting, heating, cooling, and ventilation to use the same data. As a result, these technologies do not react individually, but as one integrated system.

Limiting solar heat before cooling is required

When strong solar radiation is expected, the sun protection can close preventively. This ensures the room heats up less quickly and the cooling installation needs to provide less power.

Maximizing the use of daylight

Lighting can be dimmed or switched off when sufficient natural light is present. The sun protection is controlled in such a way that glare is limited without unnecessarily removing daylight.

Taking occupancy into account

In an unused room, the system can automatically:

• switch off the lighting;
• reduce ventilation;
• switch the temperature control to a more economical setting;
• position the sun protection according to the building strategy.

No conflicting controls

The central logic prevents technologies from working against each other. This avoids a room being actively heated and cooled at the same time, or lighting remaining on unnecessarily while sufficient daylight is available.

Tailored to comfort and energy

The precise strategy is determined per building. Orientation, operating hours, occupancy, indoor climate, and comfort requirements are all factored into the control system.

How does Fixsus prevent a customer from becoming dependent on a single supplier?

Fixsus deliberately chooses open communication protocols, freely programmable technology, and widely available components.

No closed ecosystem

The installation is not built around a single brand, product family, or exclusive supplier. This allows for the selection of the most suitable component for each application and ensures that long-term replacement remains manageable.

Open technology and data

This openness applies not only to communication protocols but also to hardware, programming, visualization, and data. As a result, the installation remains accessible and transferable.

Structured documentation

Programming, schematics, settings, and project documentation are managed in a structured manner. This ensures the installation remains understandable, adaptable, and expandable for technically qualified parties.

Long-term freedom

Openness does not mean that anyone without the necessary expertise should perform modifications. It does mean, however, that the customer is not technically locked into a system that can only be maintained or expanded by a single supplier.

How does TIBA3 integrate different building technologies?

TIBA3 integrates HVAC, lighting, sun protection, access control, energy monitoring, and other building technologies into a single central platform. This allows them to share data and be managed as a unified whole.

A single integrated control strategy

Instead of having each technology react individually, TIBA3 uses the same information for multiple functions. Measurements of occupancy, temperature, air quality, light intensity, and energy consumption can thus be utilized by various systems simultaneously.

Occupancy controls multiple technologies

When a room is not in use, the system can, for example:

• switch off the lighting;
• reduce ventilation;
• switch temperature control to a more energy-efficient mode;
• adjust sun protection according to the building strategy.

Sun protection and climate control work together

Sun protection can be closed preventively when high solar heat gain is expected. As a result, the room heats up more slowly, and the cooling system requires less power.

No conflicting controls

Because heating and cooling use the same room data and central logic, TIBA3 can prevent both systems from working against each other simultaneously.

Alignment with actual needs

The synergy between these technologies ensures that the building does not only react to fixed schedules, but also to the current status and usage of every room.

In which language and environment is TIBA3 programmed?

TIBA3 is programmed in TwinCAT 3, Beckhoff’s engineering and programming environment.

IEC 61131-3 programming languages

The PLC programming is developed according to the international IEC 61131-3 standard. Common PLC languages can be used, such as Structured Text, Function Block Diagram, and Ladder Diagram.

Relationship with CODESYS

CODESYS is another widely used programming environment that also operates according to IEC 61131-3. TwinCAT and CODESYS are therefore not the same software package, but they do use the same international programming standard and similar PLC concepts.

Transferable expertise

Programmers familiar with IEC 61131-3 and industrial PLC programming will therefore recognize the languages and principles used. In addition, modifications to a TIBA3 installation require specific knowledge of TwinCAT, Beckhoff, the Fixsus architecture, and building technologies.

Open and readable programming

The programming is structured and not intentionally locked technically. This allows an authorized party with the appropriate expertise to analyze, maintain, and further develop the system’s operation.

Is my building’s programming protected or restricted?

The programming of a TIBA3 installation is not intentionally restricted or locked down for the end customer.

No artificial lock-in

The PLC code is not used as a means to create vendor lock-in. The installation is designed to ensure that its operation remains transparent, documentable, and transferable.

Availability subject to clear agreements

The source code and technical project information can be made available to the end customer or an authorized third party under agreed terms. Clear agreements are established regarding usage, modifications, intellectual property, liability, and ongoing support.

Security remains essential

Open access to the programming does not mean that every user is permitted to make changes. Only technically qualified parties with knowledge of TwinCAT, Beckhoff, building technologies, and the Fixsus architecture are authorized to modify the underlying logic.

Protection against unauthorized changes

Access to the programming, visualization, and technical settings is managed through roles, permissions, and controlled transfer. This ensures the installation remains open and transferable without compromising operational reliability or security.

What are the advantages of Beckhoff technology in buildings?

Beckhoff combines industrial automation technology with an open, modular, and freely programmable architecture. This makes the platform suitable for buildings where various technical installations must work together reliably and flexibly.

Industrial reliability

The hardware is developed for continuous operation in demanding environments. This makes Beckhoff suitable for applications where operational reliability, speed, and a long service life are important.

Modular design

The installation can be built using central PLC technology, I/O stations, and communication terminals for diverse building technologies. New functions or additional zones can be added later without replacing the entire automation layer.

Open communication

Beckhoff can communicate with various bus systems and protocols. This allows components and installations from different manufacturers to be integrated within a single central control system.

Availability and replaceability

The hardware is available as standard and is not exclusively tied to Fixsus. This supports the replaceability of parts and reduces dependency on a single supplier.

The role of Fixsus

Fixsus uses Beckhoff as the technological foundation for TIBA3, combining that hardware with its own programming, visualization, control strategies, and knowledge of building technologies.

What are the components of a typical Fixsus installation?

A typical Fixsus installation consists of a central industrial controller, distributed I/O islands, and field devices connected to each other via open communication.

Central Beckhoff PLC

The central PLC forms the technical heart of the installation. This is where the project-specific control intelligence, the integration between technologies, and the link to the visualization are located.

EtherCAT backbone and I/O islands

I/O islands are placed throughout the building. These read signals from sensors and contacts and control installations, valves, motors, and other components.

Communication with the central controller takes place via a high-speed EtherCAT backbone.

Bus lines to the field devices

Open bus systems extend from the I/O islands to the various devices in the building, such as:

• Modbus RTU for room controls, sensors, and controllers;
• DALI for lighting;
• M-Bus or Modbus for energy meters;
• other open protocols for integrated technologies.

Field devices in the rooms

Depending on the project, the installation may include:

• room controls;
• temperature and air quality sensors;
• motion detectors;
• Room Controllers;
• badge readers;
• fire damper controllers;
• components of Fixsus Cura for nurse calls;
• switches, valves, and other technical actuators.

Visualization and secure access

The installation is completed with the TIBA3 web visualization and, where provided, secure remote access via TIBA Secure.

Project-specific configuration

Not every building has the same structure. The installation is tailored to the available technologies, the number of rooms, the desired functions, and the potential reuse of existing components.

What does ‘freely programmable’ mean?

Freely programmable means that the control strategy is not limited to a number of pre-defined functions from a single manufacturer.

Tailored to the building

The programming can be adapted to the technical installations, the architecture, the usage, and the specific requirements of the building.

For example, Fixsus can determine how heating, cooling, ventilation, lighting, and sun protection should work together under various conditions.

Adaptable in the long term

When the needs of the building change, the programming can be adjusted without necessarily having to replace all the hardware.

This is relevant, for instance, in the event of a modified room layout, new operating hours, additional technologies, or different comfort and energy objectives.

Operation without programming

Daily settings, such as schedules, setpoints, and certain control parameters, can be made accessible via the visualization. The user does not need to modify any PLC code for this.

Management by qualified parties

Freely programmable does not mean that every user must be able to program the entire installation themselves. The underlying control technology is managed in a controlled manner by parties with the necessary knowledge of PLC programming, building technologies, and the communication protocols used.

What does demand-driven control from the rooms mean?

With demand-driven control, the actual needs in the rooms determine how much heating, cooling, ventilation, and lighting the building requires.

Measurements per room

TIBA3 uses real-time data from the rooms, such as:

• temperature;
• air quality;
• presence;
• light intensity;
• set comfort values.

In this way, the control is based on what is actually happening in the building.

From room to central production

The demand from all rooms is aggregated and subsequently controls the central installations, such as boilers, heat pumps, chillers, and air handling units.

Production therefore follows the real needs in the building, rather than solely a fixed schedule or the outdoor temperature.

No unnecessary production

When few rooms require heating or cooling, the central installation does not need to operate at full capacity. In the event of higher demand, production can be scaled up in a timely manner.

More comfort and lower energy consumption

Because every room receives exactly what it needs, overheating, overcooling, and unnecessary ventilation are limited. This improves both comfort and energy performance.

Collaboration between technologies

Presence, sun protection, lighting, ventilation, and climate control can use the same room data. As a result, the various technologies react as one integrated system.

What does Fixsus mean by an ‘open concept’?

By an open concept, Fixsus means that an installation is not made dependent on a single closed brand, product family, or communication environment.

Open at different levels

The openness is not only found in the communication protocols. The hardware, programming, visualization, and data are also structured in such a way that the client is not unnecessarily tied to a single supplier.

TIBA3 utilizes open and widely used protocols, such as Modbus, BACnet, KNX, DALI-2, and M-Bus. This allows devices and technical installations from different manufacturers to be integrated within a single system.

Freedom in product choice

The client can choose the most suitable product for each application and is not obliged to purchase all components within a single brand or product family.

This also ensures that future replacements and expansions remain more manageable.

Access to the installation

The installation is not intentionally locked down technically. Hardware, project information, and interfaces are managed so that a technically qualified party can maintain or expand the installation at a later date.

Technical conditions

Openness does not mean that every device can automatically communicate with every other system. A connection must be technically possible and sufficiently documented.

What happens if a linked external system fails?

The central intelligence continues to operate autonomously: the building’s core control system does not depend on external links.

Autonomous core control

Heating, ventilation, lighting, and other technical systems continue to be managed by the central unit within the building. Therefore, a failed connection never brings the building to a standstill.

Notification and automatic recovery

A failed connection is reported via the alarm system so that it can be followed up. As soon as the connection is restored, the relevant function resumes automatically.

What is the difference with a system that ‘supports open protocols’?

Many traditional systems do communicate via BACnet or KNX externally, but keep their own controllers, tools, and licenses closed. At Fixsus, openness is structural.

Open interface versus open system

A system that only supports open protocols offers an open window into a closed core: for every adjustment, upgrade, or expansion, you remain dependent on the original supplier.

Openness on all fronts

At Fixsus, hardware, code, programming environment, and data are open: the hardware is freely available, the PLC code is not password-protected, the programming environment is license-free, and there is an open REST API. Not only is the interface open, the entire system is.

Which building technologies can be integrated with TIBA3?

TIBA3 can bring a wide range of building technologies together into one central management system.

Climate and comfort

This includes heating, cooling, ventilation, air handling, sun protection, screens, climate ceilings, and server room climate control.

Lighting and room functions

Lighting, occupancy detection, lux measurement, room controls, assistance calls, and other local functions can also be integrated.

Energy and infrastructure

TIBA3 can incorporate energy and water metering, geothermal energy, heating networks, charging station control, load balancing, leak detection, and cold storage monitoring into the central control system.

Access and building usage

Access control, badge readers, parking detection, people counting, and other systems that provide information on building usage can also be linked.

Integrated operation

Because these technologies exchange information with each other, they can not only be monitored centrally but also controlled as a single cohesive unit.

Which specific technologies are integrated depends on the building, the existing installations, and the objectives of the project.

Which communication protocols does TIBA3 support?

TIBA3 supports a wide range of open and common communication protocols for building technology and industrial automation.

Commonly used protocols

These include Modbus RTU and TCP, BACnet, KNX, DALI and DALI-2, M-Bus, OPC UA, MQTT, MP-Bus, EnOcean, PROFINET, CANopen, and EtherNet/IP.

Selection per application

The appropriate protocol is determined for each installation based on the available equipment, the desired functionality, and the technical structure of the project.

Integrations with existing systems

When a device or installation cannot communicate directly via a standard protocol, Fixsus investigates whether an integration is possible via a gateway, API, or other technical interface.

Technical support

Not every protocol is automatically usable in every situation. Feasibility, read and write capabilities, response times, and access rights are therefore technically assessed for each integration.

Which communication terminals are available for special interfaces?

The Beckhoff range includes terminals and software functions for virtually every protocol common in buildings and industry.

A terminal for virtually every protocol

Available options include RS-232/485, KNX/EIB, M-Bus, DALI, LON, MP-Bus, EnOcean, BACnet, PROFINET, CANopen, OPC UA, and MQTT.

Customization is rarely required

Special interfaces therefore rarely require custom hardware: there is a high probability that a standard terminal or software function already exists for your application.

Which protocols do the field devices use for communication?

All communication takes place via open, documented standards.

The right protocol for every application

• Fixsus field devices communicate via Modbus RTU (RS-485);
• lighting operates via DALI;
• energy meters are read via M-Bus or Modbus;
• the I/O islands communicate via EtherCAT.

Open standards

Because these are all open standards, you are not tied to a single manufacturer, and devices from other brands can also be integrated into the architecture.