Siemens APOGEE: A Guide to Upgrading Legacy Building Automation

Siemens APOGEE systems have been installed in commercial buildings since the 1990s. If your building runs APOGEE, you're operating on a capable platform — but one that may be showing its age. Understanding your upgrade options helps you plan for the future while maintaining current operations.

Understanding Your APOGEE System

APOGEE has evolved through several generations:

APOGEE Generations

• APOGEE Terminal Equipment Controllers (TEC): Zone-level controllers for VAV and fan coil applications
• APOGEE Modular Building Controllers (MBC): Equipment-level controllers for AHUs, chillers, etc.
• APOGEE Application and Data Server (ADS): First-generation supervisory platform
• APOGEE Insight: Current supervisory platform with web-based interface

Communication Protocols

APOGEE systems use several protocols:

• P1 (FLN): Field Level Network for zone controllers
• Ethernet: Building-level communication between servers and controllers
• BACnet: Newer controllers support native BACnet/IP

Common APOGEE Challenges

Aging Controllers

MBC and TEC controllers from the 1990s and early 2000s are reaching end-of-life:

• Component failures becoming more frequent
• Replacement parts increasingly scarce
• No firmware updates or feature improvements

Software Obsolescence

Legacy APOGEE workstations run on outdated operating systems:

• Windows XP or Windows 7 dependencies
• Security vulnerabilities with no patches
• Difficulty finding compatible hardware

Limited Integration

P1/FLN protocol is proprietary to Siemens:

• Third-party equipment requires gateways
• Limited data visibility for energy management
• Integration complexity increasing as system ages

Upgrade Option 1: Siemens Desigo CC

Siemens' current building management platform offers a migration path from APOGEE.

What Desigo CC Provides

• Modern web-based interface
• Native BACnet support
• Integration with legacy P1 controllers via gateways
• Advanced analytics and reporting
• Cloud connectivity options

Migration Approach

• Replace ADS workstations with Desigo CC server
• Connect existing MBC controllers via Ethernet
• Gateway P1 zone controllers to the new platform
• Gradually replace controllers as they fail

Advantages

• Manufacturer-supported migration path
• Preserves existing controller investment
• Single vendor relationship

Considerations

• Premium pricing
• Continued dependency on Siemens
• P1 controller support will eventually end

Upgrade Option 2: Niagara Framework

The open Niagara platform can integrate with APOGEE systems while providing vendor independence.

Integration Approach

• Install Niagara JACE or server
• Connect to BACnet-capable APOGEE controllers directly
• Use P1 drivers or gateways for legacy controllers
• Add new equipment as native BACnet

Advantages

• Competitive service from multiple integrators
• Multi-vendor flexibility for future equipment
• Lower ongoing costs
• Modern web interface

Considerations

• Third-party P1 drivers may have limitations
• Requires Niagara-experienced integrator
• More configuration than turnkey Siemens solution

Upgrade Option 3: Phased Controller Replacement

Rather than overlay integration, systematically replace APOGEE controllers with BACnet devices.

Approach

• Install new supervisory platform (Niagara, Desigo CC, or other)
• Replace controllers in priority order as budget allows
• Use BACnet controllers from any manufacturer
• Maintain mixed environment during transition

Prioritization

Replace controllers based on:

• Failure frequency and reliability
• Criticality of served equipment
• Integration requirements
• Coordination with other building work

Practical Migration Considerations

Preserving Field Devices

APOGEE TEC controllers connect to sensors and actuators that often remain functional:

• Temperature sensors with compatible signal types can be reused
• Actuators may need evaluation for reuse vs. replacement
• Wiring infrastructure typically can be preserved

Sequence Migration

Control sequences must be recreated in the new platform:

• Document existing sequences thoroughly before migration
• Use migration as opportunity to optimize sequences
• Test new sequences before full deployment

Graphics Redevelopment

APOGEE graphics don't transfer to new platforms:

• Plan for complete graphics redevelopment
• Consider this an opportunity for interface improvement
• Budget appropriate time and resources

Cost Expectations

Supervisory Upgrade Only

Replacing ADS with modern supervisory platform while keeping controllers:

• Desigo CC: $75,000 - $200,000 depending on system size
• Niagara: $40,000 - $120,000 depending on integration scope

Full Controller Replacement

Complete migration to new controllers:

• Add $2,000 - $4,000 per zone controller (VAV, fan coil)
• Add $5,000 - $10,000 per equipment controller (AHU, plant)
• Include programming, commissioning, and graphics development

Phased Approach

Spread costs over 3-5 years with annual budget allocation.

Planning Your APOGEE Upgrade

Step 1: Assess Current State

• Inventory all APOGEE equipment with model numbers and conditions
• Document current issues and maintenance history
• Identify most critical systems and highest-risk components

Step 2: Define Requirements

• What capabilities do you need that APOGEE can't provide?
• What integration requirements exist?
• What's your timeline for migration?

Step 3: Evaluate Options

• Get proposals for both Siemens and open platform approaches
• Compare total cost of ownership, not just initial cost
• Consider long-term flexibility and service options

Step 4: Plan Implementation

• Phase work to match budget availability
• Coordinate with other building projects
• Minimize disruption to building operations

Working with Controls NYC

At Controls NYC, we have experience with APOGEE systems and can help you navigate your upgrade options. Whether you choose to stay with Siemens or move to an open platform, we can support your migration.

Contact us to discuss your APOGEE system and explore the best path forward for your building.