With 92% of airport leaders now identifying the modernisation of legacy systems as their primary commercial priority, the pressure on engineering teams to evolve has never been greater. You likely recognise that your ageing Siemens S5 hardware is approaching a critical point of obsolescence, yet the prospect of a migration often feels like a choice between technical stagnation or the risk of catastrophic operational downtime. It is a high-stakes environment where the margin for error is non-existent; the complexity of bridging the gap between decades-old mechanical assets and modern software can feel overwhelming. For a broader perspective on the strategic trends shaping this challenge, our guide to legacy system modernisation for airports provides essential context for engineering leaders navigating this transition.

This guide serves as a definitive roadmap for airport engineers to navigate legacy PLC migration services with precision and foresight. By adopting a methodical approach aligned with RIBA design stages, you can eliminate the threat of prolonged outages whilst ensuring full compliance with current UK engineering and safety standards. We will outline a strategic framework that moves beyond a simple hardware swap, providing a clear path to a future-proof control system designed to remain robust and reliable for at least 15 years.

Key Takeaways

  • Learn how to identify the “silent failure” risks inherent in ageing Siemens S5 hardware to prevent catastrophic operational outages before they occur.
  • Discover the critical importance of a pre-migration physical audit to address undocumented code and hidden modifications within your current control architecture.
  • Understand how applying the RIBA Plan of Work to legacy PLC migration services ensures strategic alignment and rigorous budget control from inception to commissioning.
  • Explore the transition to software-centric control via IEC 61499 and Schneider Electric EAE to secure a hardware-independent system that is future-proof for at least 15 years.
  • Recognise how specialist tools like the AIAB™ platform allow for exhaustive testing and rapid deployment without compromising live airport operations.

Identifying and Mitigating Legacy PLC Obsolescence Risks

In the high-stakes environment of airport operations, obsolescence is rarely a sudden event. It is a slow, systemic degradation of support. A Programmable logic controller (PLC) that has served faithfully for thirty years becomes a significant liability the moment its manufacturer ceases hardware production and software patches. This is the reality for many facilities still relying on Siemens S5 architecture. The “silent failure” risk is perhaps the most insidious aspect of legacy infrastructure. Because the system is currently operational, there’s often a false sense of security. However, if a critical component fails today, the lack of readily available, certified spares could lead to an indefinite grounding of essential services.

The Real Cost of Siemens S5 Obsolescence

The financial and reputational impact of a Baggage Handling System (BHS) failure during peak travel periods is staggering. Beyond the immediate chaos in the terminal, the long-term damage to airline partnerships and passenger trust can take years to repair. As we move through 2026, the scarcity of specialised engineering expertise capable of maintaining these systems has reached a critical point. Most engineers with deep S5 knowledge have retired, leaving a talent vacuum that makes reactive repairs nearly impossible. Engaging with Siemens S5 obsolescence risk management is no longer optional; it’s a fundamental requirement for operational continuity. Legacy PLC migration services provide the only viable path to eliminate this dependency on vanishing parts and expertise.

Regulatory and Safety Compliance Requirements

Modern aviation infrastructure must adhere to stringent functional safety standards, such as BS EN 61508. Legacy systems often lack the diagnostic capabilities and redundancy required to meet these evolving benchmarks. At the same time, as the aviation sector faces a 74% increase in cyberattacks since 2020, the inherent vulnerabilities of non-networked legacy hardware become glaring. Modernising your control layer allows for the integration of robust security frameworks like IEC 62443. This transition ensures that every software modification and hardware update is documented, creating a compliant audit trail that satisfies both UK engineering standards and international aviation security mandates. A structured migration isn’t just a technical upgrade; it’s a necessary step in maintaining your licence to operate.

Conducting a Comprehensive Control System Audit

A successful migration is built on ground truth, not assumptions. Many airport engineers rely on outdated as-built drawings that no longer reflect the reality of the terminal floor. A physical site audit is the mandatory first step for any legacy PLC migration services engagement. It reveals the hidden code, specifically those undocumented modifications made by maintenance teams over decades to bypass faulty sensors or optimise throughput. Without identifying these logic quirks, a software migration will simply replicate old errors in a new environment, potentially leading to unpredictable behaviour once the system goes live.

We must also map how the PLC logic feeds into higher-level SCADA systems. If the migration changes data polling rates or addresses, it could overwhelm legacy supervisory layers or break essential reporting dashboards. Simultaneously, we assess mechanical asset health. Modernised control speeds can place unforeseen stress on vintage motors and conveyors. Whilst the software might be capable of higher throughput, the physical assets must be able to handle new acceleration curves without mechanical failure. Consulting the NIST SP 800-82 Guide to ICS Security during this phase ensures that the audit also identifies potential entry points for cyber threats within the existing network, allowing security to be baked into the new design. For projects requiring this level of technical rigour, engaging an automation engineering consultancy ensures no detail is overlooked.

Hardware and Network Topology Mapping

Every I/O point and communication processor must be meticulously catalogued within the existing rack. We often find obsolete protocols like PROFIBUS DP or older serial links that are no longer supported by modern controllers. By establishing a performance baseline, specifically measuring latency and cycle times, we can prove that the migrated system meets or exceeds previous operational benchmarks. This mapping also identifies where hardware redundancy can be improved to increase overall system availability and resilience against single points of failure.

Software Logic Extraction and Analysis

Extracting code from Siemens S5 processors requires specialised tools to avoid accidental CPU stops in a live environment. Once extracted, the Step 5 logic is analysed for translation into modern Step 7 or TIA Portal environments. This isn’t a simple copy-paste exercise; it’s a strategic opportunity to identify and remove redundant code blocks. Streamlining the logic at this stage ensures the system remains maintainable and efficient for at least the next 15 years, providing a clean slate for future digital transformation initiatives.

The RIBA Design Framework for PLC Migration

Unlike generic industrial upgrades, airport infrastructure requires a framework that aligns with broader construction and engineering standards. The RIBA Plan of Work 2020, typically associated with architectural builds, offers a disciplined structure for legacy PLC migration services. By applying these stages to automation, airport engineers gain a predictable timeline and a clear audit trail. RIBA Stage 1, Preparation and Brief, is arguably the most critical phase for budget management. It is during this stage that we establish the fundamental constraints of the project, preventing the expensive requirement drift that often plagues large scale infrastructure upgrades.

As the project progresses into Stage 4, Technical Design, the focus shifts to the granular details of the control logic. This stage is designed to eliminate ambiguity, ensuring that the final software build matches the operational reality of the airport. Finally, Stage 5, Construction and Commissioning, addresses the logistical challenges of working in live airside environments, where every hour of downtime carries a significant cost. This methodical progression ensures that the migration is not merely a hardware swap but a strategic modernisation of the entire control ecosystem.

RIBA Stages 1-3: Concept and Spatial Coordination

During the initial stages, the focus remains on defining the strategic requirements for the new architecture, whether transitioning to Siemens S7 or a Schneider based environment. A thorough feasibility study is conducted to evaluate the merits of a total rip and replace versus a more cautious, phased migration approach. This phase culminates in the development of a Functional Design Specification (FDS). This document acts as the single source of truth for all stakeholders, ensuring that the proposed logic aligns perfectly with the airport’s throughput and safety requirements before any code is written.

RIBA Stages 4-5: Technical Design and Handover

The technical design phase involves rigorous software engineering and comprehensive Factory Acceptance Testing (FAT). By testing the code in a simulated environment first, we identify potential conflicts before they reach the site. Once airside, Site Acceptance Testing (SAT) is supplemented by periods of shadow running. This involves the new system processing data in parallel with the legacy hardware to ensure total stability. For a deeper dive into the specific technical requirements of these transitions, consult our Siemens S5 to S7 migration guide, which details the protocols required for a seamless handover. This methodical progression from design to delivery ensures a safe pair of hands approach to mission critical infrastructure.

How to Organise a Legacy PLC Migration for Airport Infrastructure

Modernising with IEC 61499 and Schneider Electric EAE

Traditional PLC programming follows the IEC 61131 standard, which binds the logic tightly to the physical processor. In the context of legacy PLC migration services, this often creates a cycle of dependency where the software is only as resilient as the specific hardware it inhabits. The industry is now shifting towards IEC 61499, a software-centric standard that treats control logic as a set of portable, distributed function blocks. Schneider Electric EcoStruxure Automation Expert (EAE) is at the forefront of this evolution, allowing airport engineers to design systems where the intelligence isn’t trapped within a single rack. Understanding the strategic trends driving legacy system modernisation at airports is essential context for engineering teams evaluating this architectural shift.

For complex baggage handling systems, an event-driven architecture is far more efficient than traditional cyclic scanning. It allows the system to respond instantly to specific triggers, such as a barcode scan or a diverted tray, without waiting for the next CPU cycle. This responsiveness is vital for maintaining high throughput during peak travel windows. By adopting this standard, you prevent the next legacy trap in ten years. If the hardware becomes obsolete, the software logic remains portable and can be redeployed on newer platforms with minimal reconfiguration. For a comprehensive overview of the steps involved in executing this transition safely, our PLC upgrade services aviation infrastructure modernisation checklist provides a structured methodology for zero-downtime migrations aligned with IEC 61499 standards.

Achieving Hardware Independence

Decoupling control software from the underlying hardware provides maximum flexibility for long-term asset management. As a Schneider Electric EAE Master Partner, we provide the expertise required to implement these advanced architectures within the constraints of an active airfield. This approach ensures that future hardware refreshes or expansions don’t require a total rewrite of the control logic. It turns the control system into a flexible software asset rather than a rigid hardware liability. If you are ready to transition away from vendor lock-in, our automation engineering consultancy can help you design a truly portable architecture.

Integrating with Airport SCADA Systems

A modernised PLC layer is only effective if it communicates seamlessly with the broader supervisory control environment. The transition to software-centric control allows for richer data packets and more granular asset visibility. HMIs and dashboards can now provide real-time diagnostic data that was previously locked away in the legacy Siemens S5 code. This integration is essential for predictive maintenance, allowing teams to identify motor wear or belt slippage before a failure occurs. For a more detailed look at how these systems align, refer to our Airport SCADA Integration guide, which explores the wider operational technology landscape.

Partnering with a Specialist Systems Integrator

Generalist automation firms often lack the specific domain knowledge required to operate within the stringent constraints of a live airfield. Whilst they may be proficient in standard industrial settings, they frequently underestimate the operational nuances of a terminal environment where every minute of downtime has national logistical implications. Specialist legacy PLC migration services understand that a baggage handling system is not merely a collection of conveyors; it is a mission-critical asset that requires a composed, methodical approach to modernisation. These projects demand a partner who acts as a strategic ally, prioritising technical precision over aggressive delivery schedules that might compromise system integrity.

The use of our proprietary AIAB™ (Airport-in-a-Box) platform is a cornerstone of this specialised approach. It allows us to create a high-fidelity digital twin of your infrastructure, enabling exhaustive off-site testing of the new control logic before a single cable is disturbed airside. This virtual commissioning process identifies potential logic conflicts and communication bottlenecks in a safe environment, significantly reducing the risks associated with the final cutover. By the time the software reaches the site, its stability has already been proven against the exact operational parameters of your facility.

Bespoke Engineering for Aviation

Bridging the gap between thirty-year-old mechanical assets and 2026 software requires bespoke engineering that goes beyond simple code translation. We craft custom logic that accounts for the unique physical behaviour of ageing hardware, such as specific acceleration curves and mechanical response times that modern “out-of-the-box” solutions often ignore. This “safe pair of hands” philosophy ensures that the new control layer respects the physical limits of your existing conveyors. As a UK-based SME, we provide a level of dedicated, responsive support for national infrastructure that larger, global generalists often struggle to match when faced with bespoke engineering challenges. Engineers seeking a structured approach to these challenges will find our definitive checklist for PLC upgrade services in aviation environments an invaluable reference for planning risk-aware modernisation programmes.

Post-Migration Support and Optimisation

A successful handover is merely the start of a new operational lifecycle. We work with your team to develop a ten-year roadmap for continuous system improvement, ensuring the architecture remains aligned with future security and throughput demands. This includes comprehensive training for your internal engineering staff, empowering them to maintain and troubleshoot the new Siemens or Schneider architecture with confidence. If you are ready to secure the long-term reliability of your infrastructure, you should consult AAC for your legacy PLC migration project to ensure a disciplined, future-proof transition.

Securing the Future of Airport Control Infrastructure

Successfully managing legacy PLC migration services requires a shift from reactive repairs to a disciplined, framework-driven modernisation strategy. By aligning your project with the RIBA Plan of Work and adopting software-centric standards like IEC 61499, you can eliminate the “silent failure” risks that currently threaten your operational continuity. This methodical approach ensures your infrastructure remains resilient, secure, and adaptable for at least the next 15 years.

As a certified Schneider Electric EAE Master Partner with expertise spanning RIBA Stages 1 to 5, AAC Ltd provides the technical precision required for these high-stakes aviation environments. We act as a strategic ally, ensuring that new control logic respects the unique physical behaviour of your existing mechanical assets whilst delivering a future-proof architecture. If you are ready to eliminate obsolescence risks and strengthen your system’s cybersecurity resilience, we invite you to discuss your mission-critical migration with AAC Ltd. It’s time to transform your ageing hardware into a robust software asset that supports the long-term success of your airport.

Frequently Asked Questions

How long does a typical Siemens S5 to S7 migration take for an airport system?

A typical migration timeline varies based on the complexity of the airport system, though the process generally spans six to twelve months from initial audit to final handover. The majority of this time is dedicated to off-site software engineering and Factory Acceptance Testing (FAT). This rigorous preparation ensures that the actual on-site installation and commissioning phases are compressed, minimising the window of potential disruption to terminal operations.

Can legacy PLC migration be performed whilst the airport remains operational?

Yes, legacy PLC migration services are specifically designed to be performed whilst the airport remains fully operational. By utilising phased migration strategies and our proprietary AIAB™ platform, we can run the new control logic in “shadow mode” alongside the existing system. This allows for real-time validation of the new code without impacting live baggage handling or passenger services, ensuring a risk-free transition during scheduled maintenance windows.

What are the main differences between IEC 61131 and IEC 61499 control architectures?

The primary difference lies in the shift from hardware-centric to software-centric control. IEC 61131 relies on a cyclic execution model tied to a specific processor, whereas IEC 61499 uses an event-driven architecture that allows for distributed, portable logic. This enables control functions to be decoupled from the physical PLC hardware, providing greater flexibility and preventing future vendor lock-in as airport infrastructure evolves over the next decade.

Is it better to replace the entire control panel or just the PLC processor?

Deciding between a full panel replacement or a processor upgrade depends entirely on the results of a comprehensive control system audit. Whilst a processor-only swap is often faster, it may leave you with ageing electrical components that remain a point of failure. In many mission-critical aviation environments, we recommend a backplate replacement. This retains the existing enclosure but replaces the internal logic and I/O modules to ensure long-term reliability.

How does modernising a PLC system improve cybersecurity for airport OT?

Modernising your PLC system allows for the implementation of the IEC 62443 security standard, which is impossible on non-networked legacy S5 hardware. New controllers support encrypted communications, secure boot protocols, and granular access controls. These features significantly reduce the attack surface of your operational technology (OT) network, protecting critical infrastructure from the 74% increase in cyberattacks observed within the aviation sector since 2020, as reported by recent industry data.

What documentation is required for a RIBA-compliant control system design?

A RIBA-compliant design requires a structured set of documents that track the project from concept to completion. This includes the Functional Design Specification (FDS) at Stage 3, detailed Software Design Specifications (SDS) at Stage 4, and comprehensive Factory and Site Acceptance Testing (FAT/SAT) protocols. These documents provide a transparent audit trail, ensuring that the final system meets all UK safety regulations and airport engineering standards for long-term maintainability.

What is the role of a Schneider Electric EAE Master Partner in migration?

As a Schneider Electric EAE Master Partner, our role is to deliver advanced, hardware-independent automation solutions using the EcoStruxure platform. This certification confirms our mastery of the IEC 61499 standard and our ability to design distributed control systems that are more resilient than traditional architectures. We act as a high-tier systems integrator, providing airport engineers with a safe pair of hands for complex, software-centric modernisation projects.

Can we migrate our legacy SCADA system at the same time as the PLC hardware?

Migrating your legacy SCADA system alongside the PLC hardware is often the most strategic approach. This ensures that the communication drivers and data polling rates are perfectly synchronised between the control and supervisory layers. A simultaneous upgrade prevents the performance bottlenecks that occur when modern, high-speed PLCs are forced to communicate with obsolete SCADA software, resulting in better asset visibility and more accurate real-time reporting across the terminal.