Programmable Logic Controller (PLC)

A Programmable Logic Controller (PLC) is a rugged industrial computer designed for real‑time control of electromechanical processes. In AGL applications, the PLC serves as the central automation engine that monitors input signals (e.g., CCR status, switch positions, sensor data) and executes programmed logic to control outputs (e.g., brightness steps, circuit switching, alarm annunciation). PLCs are distinguished by their deterministic scan cycle, high reliability, wide operating temperature range, and resistance to electrical noise and vibration. They are the backbone of modern Airfield Lighting Control and Monitoring Systems (ALCMS), providing the link between operator commands and the physical AGL infrastructure.

The PLC exists to translate an operator's high-level command — switch to CAT III lighting configuration, raise runway edge lights to full intensity — into the exact sequence of low-level actions that make it happen safely and correctly across potentially hundreds of circuits and devices, every single time, without the timing errors or inconsistency a manual process would introduce. Its deterministic scan cycle is what guarantees that a given input reliably produces the same output within a predictable time window, which matters enormously when a lighting change needs to happen in coordination with an approaching aircraft.

Because this component sits between operator intent and the physical infrastructure itself, its ruggedness and reliability requirements are especially strict: a PLC that fails or behaves unpredictably doesn't just lose data, it can leave lighting in an unintended state during live operations, which is why industrial-grade construction and resistance to electrical noise and vibration are treated as safety requirements rather than convenience features.

PLCs are deployed throughout the AGL control infrastructure, including:

• CCR Control Rooms: Central PLC racks managing multiple CCRs, brightness control, and circuit switching.
• Remote Substations: Distributed PLCs controlling local lighting circuits and reporting status back to the main ALCMS.
• Runway & Taxiway Lighting Control: Managing power distribution, step switching, and fault detection for each lighting circuit.
• Approach Lighting Systems: Controlling sequenced flashing lights, barrettes, and intensity levels.
• PAPI & Visual Aids: Managing power and monitoring lamp failures in glide slope indicators.
• Obstruction Lighting: Controlling beacon patterns and monitoring lamp/LED status.
• RWSL (Runway Status Light) Systems: Processing surveillance data and controlling stop bars, runway guard lights, and take‑off hold lights.
• SCADA Integration: Acting as the interface between the AGL system and higher‑level airport SCADA or building management systems.

The PLC rack mounts on a DIN rail inside the CCR control room cabinet or the remote substation enclosure it controls, positioned with clear access to its I/O terminal strips for field wiring and maintenance. Field wiring (CCR control/feedback, Remote I/O links, sensor inputs) terminates on the rack's own terminal blocks rather than being spliced elsewhere, keeping fault-finding straightforward; power is fed from the cabinet's UPS-backed DC supply, and the network-side connection to the ALCMS runs on structured Ethernet cabling separate from the field-side wiring. Remote substation PLCs are sited close to the CCRs and lighting circuits they manage so field cable runs stay short, reporting status back to the central ALCMS server over the fibre backbone rather than a direct copper run.

The PLC operates on a continuous scan cycle, executing the control program repeatedly. Key functional aspects include:

• Input Scan: The PLC reads all input signals (digital: switch states, alarm contacts; analog: current/voltage levels, temperature) from field devices via I/O modules.
• Program Execution: The user‑defined control program (ladder logic, structured text, or function block diagram) processes the input data, applies logical and mathematical operations, and determines the required output states.
• Output Update: The PLC writes the calculated output states to the output modules, which then actuate contactors, relays, CCR setpoints, or communication messages.
• Communication: PLCs communicate with the ALCMS, remote I/O, and other controllers via industrial protocols (Modbus, Profibus, Ethernet/IP, OPC UA) to exchange status, commands, and diagnostic data.
• Fault Detection: The PLC continuously monitors for abnormal conditions (overcurrent, open circuit, communication loss) and triggers alarms or automatic remedial actions.
• Redundancy: Critical AGL applications often use redundant PLC configurations (dual hot‑standby) to ensure zero downtime in case of a controller failure.

PLCs are programmed using vendor‑specific software (e.g., Siemens TIA Portal, Rockwell Studio 5000, Schneider EcoStruxure) and are designed for long service life (15‑20 years) with minimal maintenance.

The PLC sits one level below the ALCMS server and one level above the CCRs, Remote I/O, and field devices it directly controls, and it is where the actual switching and setpoint decisions for its assigned circuits are made. Commands arrive from the ALCMS server over the Ethernet backbone (Modbus TCP, Profinet, or OPC UA) — a brightness-step change, a circuit on/off instruction, a pre-set lighting configuration — and the PLC translates each into the specific outputs its own I/O and control program require, whether that means writing a setpoint to a CCR, energising a contactor, or issuing a command over a fieldbus to a Remote I/O unit further out. It executes that logic locally and continuously on its own scan cycle regardless of network conditions, so lighting control keeps functioning if the link to the ALCMS server is temporarily lost; it also continuously reports the resulting status and any fault conditions back upstream, and dual hot-standby PLCs are typically used for the circuits where a controller failure cannot be tolerated.

The PLC is built as a modular rack system: a base CPU module carrying the processor, memory, and communication ports clips onto a DIN rail alongside expansion I/O modules, each connected through a backplane bus connector so the system can be extended without rewiring. The housing is an extruded-aluminium or high-impact plastic shell with a conformally coated internal board to resist dust, humidity, and vibration in an unconditioned equipment room or field cabinet. Removable, colour-coded terminal blocks on each I/O module allow field wiring to be disconnected without removing the module itself, simplifying maintenance and module replacement. Where a field-mount rating is required rather than panel-mount, the entire rack assembly is enclosed in a sealed IP65 cabinet with cable glands for each conductor entry, and a lithium battery module clips onto the CPU board to retain the program and real-time clock through a power loss.