Future-Proofing Kinetic Facade Controls Against Obsolescence

The aluminum will outlast the electronics. By decades.

A well-built kinetic facade can keep its panels, frames and even many of its actuators in service for thirty years or more, but the controllers, software and communication hardware that tell those panels when to move typically reach the end of manufacturer support far sooner, and when a proprietary controller fails after its maker has stopped producing parts, a perfectly sound facade can be left frozen in one position.

Kinetic facade control obsolescence is a design problem. It needs a design answer.

Key Takeaways

• Control hardware and software age much faster than panels and frames

• Open protocols such as BACnet, Modbus and KNX reduce dependence on one supplier

• Owner access to logic, source code and documentation makes future replacement possible

• Separating field devices, controllers and supervision lets each layer be replaced on its own

Why Controls Age So Fast

Different parts of a facade live on different clocks.

These figures are indicative and vary widely by product and use. The pattern is consistent, though. Electronics fall behind first.

When a controller model is discontinued, spare parts dry up over a few years, the engineers who wrote and understood the original software retire or move to other companies, and the knowledge of why the facade behaves the way it does slowly leaves the building. The facade still works. Until something breaks.

The Lock-In Trap

Many early kinetic facades used bespoke or proprietary control systems.

They worked well at handover, but every repair afterward depended on one company, and if that company stopped supporting the product, changed ownership or closed, the owner faced a full controls replacement with no documentation of how the original logic worked, which can cost far more than the original controls package.

Kinetic Facade Open Protocols

Kinetic facade open protocols are communication standards that many manufacturers support.

• BACnet, defined in ASHRAE Standard 135 and adopted as ISO 16484-5, is widely used for building automation

• Modbus is simple, long established and supported by a huge range of devices

• KNX, standardized as ISO/IEC 14543-3, is common in European building systems

• Standard analog signals, such as 0 to 10 V and 4 to 20 mA, are understood by almost every controller

Using open protocols means a replacement controller from a different manufacturer can talk to the same actuators, sensors and building management system.

BACnet Dynamic Facade BMS Integration

Most commercial buildings already run a BMS. The facade should join it, not sit beside it.

A BACnet dynamic facade BMS connection exposes facade zones, positions, alarms and modes as standard objects that the building management system can read and command. That allows operators to see faults, override zones and coordinate the facade with heating, cooling and lighting from one interface.

• Define facade points and objects in the specification

• Include zone positions, commanded and actual

• Include alarms, such as stalls, wind lock and winter lock

• Allow schedules and overrides from the BMS

• Document every point in a points list handed over to the owner

PLC Replacement on an Operable Facade

Many kinetic facades use programmable logic controllers. PLCs are robust, industrial and well understood.

PLC replacement operable facade projects become far simpler when the original logic is written in standard languages defined by IEC 61131-3, such as ladder diagram or structured text, rather than in proprietary tools. Standard logic can be migrated to a new controller platform with much less effort.

Choose widely used PLC platforms with long product support records. Ask suppliers for their published product lifecycle and migration policies.

Own the Logic and Documentation

The owner should own everything needed to run and replace the controls.

• Source code and project files for all controllers

• Control logic narrative, describing what the facade does and why

• Input and output lists for every controller

• Network diagrams, addresses and protocol settings

• Commissioning records and test results

• Software licenses transferable to the owner

Write ownership into the contract. Escrow arrangements can protect source code if a supplier will not release it directly.

Separate the Layers

A layered architecture lets each part be replaced alone.

Field Layer

Actuators, sensors and limit switches. These should use standard interfaces so they can work with any controller.

Control Layer

Zone controllers or PLCs running the movement logic. Replaceable without touching field devices if interfaces are standard.

Supervisory Layer

The BMS or facade supervisor. Replaceable without touching zone controllers.

This structure connects directly to the sensor and actuator layers described in our mechanism guide.

Manual Override and Safe States

When controls fail, the facade still needs to behave.

Provide local manual override that does not depend on the main software. Define safe states for loss of communication, such as holding position or moving to a wind-safe or winter-safe position. Make sure maintenance staff can move panels for access even with the controllers down.

Cybersecurity

A networked facade is part of the building network. It must be protected.

Segment facade controls from public networks, change every default password before handover, keep firmware updated for as long as the supplier supports it, and follow guidance such as the IEC 62443 series for industrial automation security, since an unpatched controller on a building network is an open door.

Plan the Replacement

Controls replacement should be planned. Not discovered.

Include controls replacement in the lifecycle plan, with a budget and an expected year. Buy critical spares while they are still available. Monitor supplier announcements for end-of-life notices. The lifecycle cost of the controls belongs in the original business case.

Drive data has a second use. Monitoring wear through drive data, such as rising motor current, helps target maintenance and spot failing parts early.

Our kinetic facade systems can be coordinated with project control specifications, and our media downloads provide technical documentation. For a guide to kinetic facade systems, see our main article.

Frequently Asked Questions

1. Why do kinetic facade controls become obsolete?

Controllers, software and communication hardware have much shorter support lives than panels and frames. When parts and support end, repairs become difficult or impossible.

2. Which open protocols suit kinetic facades?

BACnet, Modbus and KNX are the most common, along with standard analog signals. They allow equipment from different manufacturers to work together.

3. How should a kinetic facade connect to the BMS?

Through an open protocol such as BACnet, exposing zone positions, alarms, modes and overrides as standard points documented in a handover points list.

4. Can a PLC on an operable facade be replaced later?

Yes, much more easily if the logic is written in IEC 61131-3 languages and the owner holds the source code, documentation and input and output lists.

5. Who should own the facade control software?

The building owner. Source code, logic narratives and documentation should be handed over, or held in escrow, so future replacement does not depend on one supplier.

Build Controls That Can Be Replaced

Every control system will be replaced one day. Make that day easy.

Use open protocols, own the logic, separate the layers and plan the replacement from the start. Send us your controls specification and request a controls integration review for your kinetic facade.