Apogee Insight Upgrade Options

Siemens has announced the end of life date for the Apogee Insight system as Jan 2022 although new system sales were ended before Jan 2020.

Apogee Insight Retiring table

The Siemens upgrade path is to Desigo CC using their Apogee P2 driver. This upgrade is being offered at a discount to clients on Insight version 3.15. Earlier versions of Insight do not qualify for the discount. Only the latest version of the panel firmware is supported by the Apogee P2 driver.

For those looking for alternatives to the Desigo CC upgrade path there are a few options which retain at least some if not all of the apogee devices.

The Siemens Apogee system is a complex system which has evolved over the past 30 years. For an overview of the Apogee system architecture please refer to our page here.

A simplified version of the Apogee system is shown below.

Insight Diagram

Some of the integration methods link into a specific physical layer of the Apogee architecture (P1 is a common choice) while others rely on integration options offered by Siemens themselves such as the BACnet server running on the Insight PC.

Each of these methods has its own advantages and disadvantages. Below we discuss the most common methods of integration.

1. Apogee BACnet Server

The Apogee BACnet server can be used to expose the Apogee panel / TEC points as BACnet read / write objects.

Apogee BACnet Server

2. HMI to BACnet gateway (terminal emulation)

This is the oldest and most common integration method. Each panel has a serial port connection which on legacy equipment is called the MMI but was renamed to HMI for political correctness one would assume. (MMI = Man Machine Interface)

The HMI is a console like interface which is keystroke driven. This method of integration relies on a program to "type" commands to the HMI and poll for system point values and to command points to new values etc.

The newer Siemens panels with Ethernet connections support the same console interface via telnet.


• Very simple (cheap) to write software interface.

• Gives access to all panel and TEC points on the local BLN network.


• Very (very) slow on medium and larger systems.

Gateway Terminal Emulator

3. P1 to BACnet gateway

The P1 to BACnet gateway replaces each panel in the system and controls the P1 communications. The P1 protocol is a (M)aster (S)lave design and the gateway takes on the (M)aster role polling each connected TEC device in turn. This is the same design as BACnet MSTP.


• Fast (low latency) and with auto discovery, easy to engineer.


• None of the panel system data is integrated.

• The TEC management code such as system AHU load scheduling will need to be created on the new system which adds costs and engineering time.

• Any equipment such as AHUs that were attached to the panels will require new controller devices with suitable control function programming which adds costs and engineering time.

P1 to BACnet gateway

4. P2 to BACnet gateway

The P2 protocol is a token passing (peer network) protocol. This means that a gateway can be added to the P2 BLN network without removing / replacing the panel as was the case with the P1 network.


• Fast (low latency) and with auto discovery, easy to engineer.


• Very difficult (expensive) to write software capable of P2 network communications.

P2 to BACnet Gateway