Partners

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 existing cabling be reused during a retrofit?

In many cases, yes. During the preparation phase, Fixsus examines which existing power, bus, and signal cables are technically suitable for reuse.

What can potentially be retained?

Depending on the existing installation, cables to sensors, valves, motors, pumps, meters, and other field components, among others, can be retained.

Existing bus cabling and power supplies can also sometimes be reused if they meet the technical requirements of the new installation.

Technical inspection

Reuse is not automatic. Fixsus assesses, among other things:

• the condition and age of the cabling;
• the cable type and wire cross-section;
• the length and topology;
• the electrical load;
• the suitability for the communication protocol used;
• the available diagrams and documentation.

Where necessary, measurements, checks, or tests are carried out.

Benefits of reuse

By retaining existing cabling where possible, demolition work, material usage, execution time, and investment costs can be limited.

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 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 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.

How does a Fixsus project proceed from analysis to delivery?

A Fixsus project is developed step-by-step, from the initial technical analysis to final delivery and ongoing support.

1. Analysis of the building and requirements

Fixsus first maps out the existing or planned installations. This involves assessing:

• existing building technologies;
• comfort and energy requirements;
• existing cabling and components;
• desired integrations;
• users and access rights;
• future expansion possibilities.

2. Defining the scope of work

Before execution, the tasks assigned to Fixsus, the installer, the engineering firm, and other involved parties are clearly defined.

This ensures clarity beforehand regarding responsibilities for delivery, cabling, assembly, programming, integration, testing, and commissioning.

3. Architectural design

Fixsus determines the central control architecture, the required I/O, communication protocols, control strategies, and visualization.

For renovations, it is also determined which existing components can be retained or replaced in phases.

4. Programming and preparation

A significant portion of the programming and visualization is prepared in advance. Where possible, control cabinets and technical components are also assembled and tested prior to installation.

5. Execution and integration

On-site, the various installations are connected and integrated. Fixsus collaborates with the executing installers and other technical partners.

6. Commissioning and functional testing

The complete operation is verified, including:

• correct signals and controls;
• interaction between technologies;
• alarms and user rights;
• visualization and reporting;
• control strategies and comfort settings.

7. Delivery and training

Following the tests, the installation is delivered. Users and technical managers receive training on operation, monitoring, and key settings.

8. Aftercare and optimization

After commissioning, Fixsus can continue to monitor, adjust, and maintain the installation through the agreed Total Care formula.

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 is a quotation prepared?

The quotation is structured based on clear line items and pre-determined unit prices.

Transparent price structure

The various components of the project are listed separately, for example:

• I/O points;
• control cabinets;
• field devices;
• programming;
• integrations;
• commissioning;
• service and training.

This ensures visibility regarding which components are included in the price.

Established unit prices

Wherever possible, Fixsus works with fixed unit prices per item. This allows the client to better evaluate and compare the quotation.

Additional and reduced work

If the scope changes during the project, additional and reduced work will be settled according to the same agreed unit prices.

This prevents subsequent changes from being calculated on an opaque or entirely new price basis.

Aligned with the scope of work

The quotation aligns with the agreed division of tasks between Fixsus, the installer, and other involved parties. This clarifies which deliveries and activities are or are not included in the price.

How reliable is Fixsus as a partner?

The continuity of your partner also contributes to the operational reliability of your installation.

Healthy figures

Fixsus has a Graydon score of 93, a risk score of 99 (very low risk), and 16 years of steady growth.

Even in an extreme scenario

And even if you ever wish to change partners, your installation remains open and transferable: code, hardware, and tools are freely available. You are therefore never held hostage by your supplier.

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 cybersecurity solely the responsibility of Fixsus?

No. Cybersecurity is a shared responsibility between Fixsus, the client, IT administrators, network partners, installers, and other involved service providers.

Responsibility of Fixsus

Fixsus secures the components for which it is responsible within the project. This includes, among other things, the TIBA3 environment, secure access, the configuration of user rights, and the agreed-upon update and service processes.

Responsibility of the client

The client remains responsible for, among other things:

• their own corporate and IT network;
• user management and internal access procedures;
• password policy;
• workstations and mobile devices;
• physical access to technical installations;
• internal incident reporting and security guidelines.

Responsibility of other parties

Installers, integrators, and external IT or network partners must also securely design, configure, and maintain their part of the installation.

Clear agreements

A secure installation therefore requires clear agreements regarding roles, access rights, maintenance, updates, monitoring, incident reporting, and management.

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 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 Fixsus expect from other parties on the construction site?

Primarily timely coordination and clear agreements.

Specifically:

• correct execution of the cabling according to the specifications;
• availability of the technical systems for the start-up;
• one clear point of contact per party.

Structure through the scope of work

The scope of work and site meetings structure this cooperation: everyone knows who delivers and does what, and disputes on the site are avoided.

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 is the ‘scope of work’ and why is it important?

The scope of work is the document in which it is determined in advance which party is responsible for each part of the project.

Clear division of tasks

For each component, it is determined what will be delivered or executed by Fixsus, what falls under the responsibility of the installer, and which tasks lie with other involved parties.

This may include:

• delivery and assembly of components;
• cabinet construction;
• cabling;
• connection of field devices;
• programming;
• commissioning;
• testing and delivery.

Prepared together before execution

Fixsus prepares the scope of work together with the involved parties before the work commences. This allows technical interfaces to be discussed and coordinated in a timely manner.

Fewer discussions and missing scope

A clear scope of work prevents components from being provided twice or from no one taking responsibility for them. It limits discussions during execution and clarifies who should handle questions, changes, or problems.

Basis for planning and quotation

The agreements also form an important basis for planning, price structure, and the follow-up of contract variations.

What is the Fixsus Academy?

The Fixsus Academy is the training program offered by Fixsus for managers, technicians, users, installers, and integrators working with TIBA3 and the associated building technologies.

Training tailored to the user

Facility managers and daily users learn to work with visualization, alarms, schedules, and basic settings. Technical managers can delve deeper into control technology, trending, communication protocols, hardware, and system architecture.

Practical knowledge

The training courses combine theory with practical applications from real buildings. As a result, participants understand not only which actions they need to perform, but also how the various technologies work together.

Greater independence

The Fixsus Academy helps customers and technical partners build more knowledge within their own organization, use the installation more effectively, and carry out minor adjustments themselves.

What role does Fixsus play in a construction project?

Fixsus is the building automation specialist within the project: from concept support and design, through programming and commissioning, to after-sales service.

From concept to operation

Fixsus contributes ideas on automation from the earliest phase, helps develop the design, handles programming and commissioning, and remains responsible for monitoring and service after completion.

Flexible in project structure

Depending on the project, Fixsus works directly for the operator or client, or as a subcontractor within a contracting structure.

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.