ALCMS Workstation
The primary human‑machine interface (HMI) for the Airfield Lighting Control and Monitoring System. It provides airfield operators with real‑time visibility of all AGL assets, enabling intuitive control, alarm management, and system diagnostics through a graphical user interface.
Image disclaimer: For identification and illustration only. It may show a product by another manufacturer and may not depict the exact item described; it is not a statement of any product’s quality, approval or performance. Third-party image and trademark rights belong to their owners. See full notice.
What Is It?
The ALCMS Workstation (Airfield Lighting Control and Monitoring System Workstation) is the operator's primary interface for monitoring, controlling, and managing the entire airfield ground lighting system. It is a high‑performance desktop computer or thin client that runs the ALCMS client software, connecting to the ALCMS server to display real‑time status, issue control commands, and respond to alarms. The workstation presents a graphical, geospatial representation of the airfield, allowing operators to view the status of every runway, taxiway, and approach lighting circuit at a glance.
Key characteristics of the ALCMS workstation include:
- High‑Performance Graphics: Equipped with powerful graphics capabilities to render large, dynamic airfield maps with real‑time status indicators, colour‑coded circuits, and animated elements.
- Dual or Multi‑Monitor Support: Typically configured with two or more high‑resolution monitors to provide an expansive view of the airfield, alarm lists, and detailed status panels simultaneously.
- Intuitive User Interface: Designed with user‑centric principles, featuring clear icons, consistent colour coding (green = on, red = fault, amber = standby), and context‑sensitive menus.
- Role‑Based Access: Supports multiple user roles (operator, supervisor, administrator) with different levels of access and control authority, ensuring that only authorised personnel can execute critical commands.
Core functions of the ALCMS workstation include:
- Real‑Time Status Display: Shows the current state of all AGL circuits, including on/off status, brightness step, current readings, and alarm conditions, updated in real‑time (typically 1‑5 second refresh).
- Control Execution: Allows operators to turn circuits on/off, adjust brightness levels, control stop bars, and execute pre‑programmed lighting scenarios (e.g., runway configurations for different approach categories).
- Alarm Management: Displays active alarms in a prioritised list with clear visual and audible indicators. Operators can acknowledge, silence, and log alarms, and drill down for detailed diagnostic information.
- Historical Data Access: Provides access to historical logs for circuit status, current readings, alarm events, and operator actions, supporting trend analysis and compliance reporting.
- Diagnostic Tools: Includes built‑in diagnostic tools for troubleshooting, such as communication status indicators, device health checks, and system performance metrics.
The workstation is typically installed in the air traffic control tower, the airfield operations room, or the maintenance control centre. It is connected to the airfield network via redundant Ethernet links, and is often configured with a UPS to protect against power interruptions.
Purpose & Function
The ALCMS workstation exists to give a single operator command and visibility over an entire airfield's lighting infrastructure from one seat, condensing what would otherwise be an unmanageable number of individual circuit states into a geospatial, at-a-glance view they can actually act on under time pressure. During a rapidly changing weather event or a runway configuration change ahead of an arrival, this consolidated view is what lets an operator make and execute a decision in seconds rather than working through dozens of separate systems.
Role-based access control exists specifically because the commands available from this workstation are safety-critical — changing a runway's lighting configuration or disabling a stop bar has real operational consequences — so the interface has to ensure that only personnel with the right authority can issue those commands, while still giving every operator the situational awareness they need to respond to alarms and monitor system health.
Where Is It Used?
ALCMS workstations are used in all airfields that have a modern AGL control and monitoring system, including:
- Air Traffic Control Towers: Providing controllers with real‑time status of runway and taxiway lighting to support safe aircraft movements during all visibility conditions.
- Airfield Operations Rooms: Enabling operations staff to monitor and control AGL systems during routine operations, maintenance, and emergency situations.
- Maintenance Control Centres: Allowing engineering and maintenance teams to diagnose faults, plan maintenance activities, and verify system performance.
- Remote Monitoring Stations: Supporting off‑site monitoring and control (e.g., from a central airport operations centre) via secure network connections.
- Training Simulators: Used in training environments to familiarise operators with the ALCMS interface and procedures without affecting live systems.
The workstation is typically part of a larger ALCMS architecture that includes:
- ALCMS Server: The central data processing and storage platform.
- Network Infrastructure: Fibre optic or Ethernet switches and communication gateways.
- Field Equipment: CCRs, remote I/O, smart fixtures, and sensors.
- Peripheral Devices: Printers for alarm logging, large‑format displays for status boards, and external speakers for audible alarms.
In larger airports, multiple workstations may be deployed in different locations (tower, operations, maintenance), all connecting to the same ALCMS server and providing consistent, synchronised information across the facility.
Installation & Location
Workstations are desk-mounted at the operator position in the ATC tower, airfield operations room, or maintenance control centre, positioned for clear sightlines to the runway/taxiway where the tower cab is the location, and wired back to the network switch on structured Ethernet cabling rather than field cable. Screen and console placement follows the room's operator ergonomics rather than a fixed airfield setout rule, but power is typically fed from the same UPS-backed supply as the ALCMS server so the operator's control and monitoring capability survives a mains interruption; remote workstations at satellite locations connect back over the airport's secure network link rather than a direct cable run to the server room.
How Does It Work?
The ALCMS workstation functions as the primary interface between the operator and the AGL system, translating complex field data into an intuitive visual representation and translating operator commands into actionable control signals:
- Data Presentation: The workstation receives real‑time data from the ALCMS server via the network (typically using TCP/IP and proprietary or standard protocols such as OPC UA, MODBUS, or IEC 61850). The client software renders this data on the screen using a geospatial map of the airfield, with colour‑coded icons and dynamic indicators that show the status of each circuit and fixture.
- Interactive Controls: Operators interact with the interface using a mouse, keyboard, or touchscreen. Clicking on a circuit element brings up a control panel with options to turn the circuit on/off, adjust brightness, or view detailed status information. Operators can also execute pre‑defined lighting configurations (e.g., "Runway 09 Approach Lighting – CAT III") with a single command.
- Alarm Handling: When the server detects an alarm condition (e.g., circuit fault, overcurrent, communication loss), it sends an alarm notification to the workstation. The workstation displays the alarm in a prioritised list, with colour coding (red = critical, amber = major, yellow = minor) and an audible alert. Operators can acknowledge the alarm, add comments, and initiate corrective actions.
- Command Execution: When an operator issues a control command, the workstation sends the command to the ALCMS server, which validates the command (checking permissions, operational constraints, and interlock conditions), formats it for the target field device, and transmits it via the communication network. The workstation then updates the display to reflect the new status once the server confirms successful execution.
- Logging and Auditing: All operator actions (logins, control commands, alarm acknowledgements) are logged by the workstation and transmitted to the server for storage in the historian database. This provides a complete audit trail for compliance, safety investigations, and performance analysis.
- User Authentication: The workstation requires operators to log in with a username and password. The server verifies the credentials and assigns the appropriate role (operator, supervisor, administrator) with corresponding permissions. This ensures that only authorised personnel can perform critical control actions.
The workstation also includes self‑monitoring capabilities, such as network connectivity status, server connectivity status, and system resource usage (CPU, memory, disk). If the workstation detects a loss of connection to the server, it displays a warning and attempts to reconnect automatically. The workstation software is designed to be resilient, with automatic recovery from network interruptions and graceful handling of server failover events.
Status & Command Loop
Both directions are logged — status updates flow up in real time, while every command issued back down is authenticated, validated, and audited.
Physical Construction
The ALCMS workstation is built as a standard commercial computing platform housed in a desktop tower, rack-mount chassis, or all-in-one enclosure, selected to suit the control room's space and cooling arrangement. Internally, the chassis houses the motherboard, multi-core processor, memory, storage, and dedicated graphics card on standard mounting rails or trays, with cooling provided by fan-driven airflow through filtered intake vents to keep dust out of the control-room-grade electronics during continuous 24/7 operation. Multiple video outputs feed the dual or triple monitor array that forms the operator's primary display, with cabling routed through cable management channels built into the desk or console mounting. Where the workstation is deployed as a thin client connecting to a remote ALCMS server, the local unit is a smaller, fanless or low-power enclosure with reduced internal components, relying on the network connection rather than local processing power. The chassis and cabling are typically installed within a purpose-built control desk or 19-inch rack enclosure alongside an uninterruptible power supply, keeping the workstation's physical footprint integrated into the control tower or airfield lighting control room environment.
Technical Parameters
| Parameter | Typical Value |
|---|---|
| Form Factor | Desktop tower, rack‑mount (4U), or all‑in‑one (AIO) workstation |
| Processor | Intel Core i7/i9 or Xeon, AMD Ryzen 7/9 (high‑performance multi‑core) |
| Memory (RAM) | 16GB to 64GB (for large airfield datasets and multi‑monitor setups) |
| Storage | 512GB to 2TB SSD (for fast boot and application loading) |
| Graphics | Dedicated GPU (NVIDIA Quadro, RTX, or AMD Radeon Pro) with ≥ 4GB VRAM |
| Display Configuration | Dual or triple 24" to 32" monitors (4K UHD recommended for detailed maps) |
| Operating System | Windows 10/11 Pro, Windows Server (for thin client), or Linux (custom deployments) |
| Communication | 2 x 1G Ethernet (redundant), Wi‑Fi (optional), USB 3.0/3.1 |
| Software | ALCMS client software (proprietary), OPC UA client, web browser for web‑based interfaces |
| Power Supply | 500W to 800W (with UPS backup) |
| Peripherals | Keyboard, mouse, barcode scanner (optional), external speakers for audible alarms |
| Operating Temperature | 10°C to 35°C (standard office environment) |
| Regulatory Compliance | FCC, CE, RoHS, FAA AC 150/5345‑56 |
Electrical Requirements
| Requirement | Typical Value |
|---|---|
| Circuit Type | Mains-powered IT equipment — not part of the airfield series circuit |
| Power Supply | 500W to 800W PSU (desktop/rack workstation), with UPS backup |
| Cable Type | IEC C13/C14 mains cord; Cat5e/6 Ethernet (redundant) |
| Earthing/Grounding | Chassis bonded to the building/control-room earth |
| Fault Protection | UPS ride-through on mains interruption; surge protection on the mains input |
| Protection Class | IP20 (indoor use only) |
| Standards | FCC, CE, RoHS, FAA AC 150/5345-56 |
Applicable Standards
FAA AC 150/5345‑56
Specification for L-890 Airport Lighting Control and Monitoring System (ALCMS) — includes requirements for operator interfaces
ICAO Annex 14
Requirements for control and monitoring of AGL systems — includes human‑machine interface guidelines
IEC 61850
Communication networks and systems for power utility automation (used for data exchange with the ALCMS server)
ISO 9241
Ergonomics of human‑system interaction — guidelines for user interface design
Installation Requirements
Console/Rack Placement
CivilSite the workstation within the control desk or 19-inch rack enclosure in the control tower or lighting control room, keeping filtered intake vents clear for continuous 24/7 airflow.
UPS-Backed Power Feed
ElectricalFeed the workstation and its monitor array through the uninterruptible power supply installed alongside it, so a mains interruption does not drop the operator's display.
Redundant Network Connection
ElectricalTerminate both 1G Ethernet connections to the ALCMS server or network, confirming failover between the redundant links before going live.
Monitor Array Cabling
MechanicalRoute video outputs to the dual or triple monitor array through the desk or console's cable management channels, keeping runs tidy for the operator's workspace.
ALCMS Client Software Installation
ConfigurationInstall and license the ALCMS client software (and OPC UA client where used) before connecting to the live server, confirming the version matches the server's supported client list.
Operator Account & Access Setup
ConfigurationCreate operator accounts with the correct access level before handover, so the workstation is ready for controller use on day one.
Pre-Go-Live Sign-off
DocumentationRecord network configuration, software version, and account setup as-built before the workstation is placed into operational service.
Testing & Commissioning
Hardware Burn-in & Function Check
Pre-DeploymentRun the workstation through an extended burn-in period, confirming stable operation of the processor, memory, storage, and graphics under continuous load before deployment to the control room.
Display & HMI Configuration Verification
CommissioningConfirm the multi-monitor array displays the correct airfield overview, circuit status, and alarm layout at the intended resolution across all screens.
Network Connectivity & Redundant Link Test
CommissioningVerify both Ethernet connections establish and maintain a link to the ALCMS server, and confirm automatic failover if the primary link is interrupted.
ALCMS Client Software Verification
CommissioningConfirm the client software connects to the server, authenticates correctly, and displays live circuit and alarm data matching the field state.
Command & Control Function Test
CommissioningIssue a series of test commands from the workstation and confirm correct execution at the field level along with accurate status feedback on screen.
UPS Backup Verification
Pre-EnergisationConfirm the uninterruptible power supply sustains the workstation through a simulated mains interruption for the required bridging time.
Documentation & Sign-off
Final AcceptanceRecord hardware burn-in results, network test results, and command verification in the commissioning dossier for handover.
Inspection & Maintenance
OS & Software Patching
MonthlyApply operating system and ALCMS client software updates on a controlled schedule, testing on a non-production workstation first where possible.
Redundant Network Link Test
Semi-annualVerify both 1G Ethernet connections independently maintain the workstation's link to the ALCMS network, and that failover between them works correctly.
UPS Backup Verification
AnnualTest the UPS backup runtime and confirm the workstation transitions cleanly on mains loss, so a power blip doesn't drop the operator's view of the airfield.
Storage Health Check
QuarterlyCheck SSD health metrics and available free space, since a failing drive on a control workstation can interrupt airfield monitoring.
Display & GPU Function Check
AnnualConfirm all monitors render correctly at full resolution and that the GPU handles multi-monitor airfield map rendering without dropped frames or artefacts.
Audible Alarm Test
MonthlyTest external speakers and alarm audio output so operators can rely on audible alerts alongside on-screen alarms.
Dust & Cooling Check
AnnualClean dust from intake vents and fans, and confirm internal temperatures stay within spec, especially for tower or rack-mounted units in equipment rooms.
User Access & Peripheral Review
AnnualReview user accounts and access levels for currency, and confirm peripherals like barcode scanners remain functional for asset workflows.
Common Field Issues
Network Connectivity Loss
If the workstation loses network connectivity to the ALCMS server, it cannot display real‑time data or issue commands. Use redundant network interfaces and a dedicated network infrastructure (VLAN) for AGL systems. Implement automatic reconnection and display a clear warning message to the operator.
Slow Performance or Lag
Large airfield maps with many fixtures can cause performance issues on under‑specified workstations. Use a dedicated GPU, sufficient RAM, and an SSD for fast data access. Optimise the map rendering (e.g., using level‑of‑detail techniques) to maintain responsive performance.
Display Calibration Issues
Incorrect display calibration (brightness, contrast, colour) can affect the operator's ability to interpret colour‑coded status indicators correctly. Use professional‑grade monitors and calibrate them regularly. Ensure that colour coding is consistent across all workstations.
Software Bugs or Crashes
ALCMS client software can occasionally crash or exhibit bugs, interrupting operations. Ensure the software is thoroughly tested before deployment, and implement a rapid restart procedure. Maintain a backup workstation (hot‑standby) for critical operations.
Inadequate User Training
Operators who are not adequately trained on the ALCMS interface may make errors or fail to respond promptly to alarms. Provide comprehensive training, including hands‑on simulation exercises, and maintain up‑to‑date user manuals and quick‑reference guides.
Cybersecurity Vulnerabilities
Workstations are potential entry points for cyberattacks. Implement strong password policies, use antivirus and firewall protection, keep the operating system and software patched, and restrict physical access to workstations.
Alarm Fatigue
If the system generates too many alarms (especially nuisance alarms), operators may become desensitised and miss critical events. Implement alarm suppression and filtering to reduce nuisance alarms, and conduct regular alarm rationalisation to ensure that only important alarms are presented.
Troubleshooting Guide
Workstation Shows "Offline" / No Live Data from ALCMS Server
Map Rendering Lags or Freezes Under Load
Status Colours Appear Inconsistent or Hard to Distinguish
ALCMS Client Crashes or Freezes Mid‑Session
Operator Slow to Respond to or Misinterprets an Alarm
Suspicious Login Activity or Unpatched Vulnerability Flagged
Failure Modes & Root Causes
Network Connectivity Loss
Software Crash or Bug
Display / GPU Hardware Failure
UPS Backup Failure
Cybersecurity Vulnerability
Storage Health Degradation
Dust and Cooling System Degradation
Safety & Operational Notes
Verify Command Authority & State
OperationalConfirm the on-screen airfield state is current (not stale from a lost connection) before issuing a control command from the workstation, since a command sent against out-of-date data can act on the wrong circuit or setting.
Confirm Redundant Path Before Taking Primary Offline
OperationalVerify the backup network link or a second workstation can pick up monitoring and control before disconnecting or servicing the primary workstation, so the operator is never without airfield visibility.
Isolate Before Hardware Work
Electrical SafetyPower down and unplug the workstation before opening the case for hardware service, and use anti-static precautions when handling internal components.
UPS Backup for Operator Visibility
OperationalConfirm the workstation is on UPS-backed power where required, since losing the operator's display during a mains interruption removes real-time visibility exactly when field conditions may be changing.
Function-Test After Client Updates
VerificationRun a command-and-control function test after any ALCMS client software update before relying on the workstation for live operations, since an incompatible update is a known cause of crashes or unresponsive controls.
Access Control
OperationalKeep operator login credentials for the ALCMS client restricted to authorised personnel; the workstation is a direct control point for the entire lighting system, and unauthorised access is an operational risk in its own right.
Coordinate Before Taking the Workstation Down
OperationalNotify the tower or airfield operations before planned maintenance on the workstation that will interrupt monitoring or control, so alternate arrangements are in place for the outage window.
Restore to Compliant State
ComplianceConfirm live data, alarm annunciation, and command function are all working correctly before returning the workstation to unattended service after any maintenance.
Engineering & Expert Notes
Test Failover to the Backup Workstation on a Schedule, Not Just at Commissioning
ReliabilityA redundant workstation that was proven at commissioning can quietly drift out of sync with the primary's software version, display configuration, or user permissions over subsequent years of updates; periodically switch operations onto the backup as a planned exercise rather than only discovering a stale configuration during an actual primary-workstation failure.
Treat It as a Cybersecurity Asset, Not Just an Operator Terminal
CybersecurityBecause the workstation issues live control commands to the entire airfield lighting system, it warrants the same patching, access control, and network segmentation discipline as any other critical control-system asset; an unmanaged USB port or an unpatched OS on the workstation is a control-system vulnerability, not a minor IT hygiene item.
A Green Map Doesn't Guarantee the Underlying Data Is Current
DiagnosticsIf the workstation loses its live data feed from the server, some client software continues displaying the last known status rather than clearly flagging a stale connection; verify the workstation is actively distinguishing "confirmed healthy" from "no recent update" rather than assuming an all-green display always reflects the airfield's real-time state.
Review Operator Permission Levels Periodically, Not Just at Setup
Access ControlOperator accounts accumulate elevated permissions over time as staff change roles or cover for colleagues, often without a corresponding review of what access is actually still needed; periodically auditing who can issue which commands from the workstation reduces the risk of an unintended or unauthorised control action.
Version-Control Map and Configuration Changes
DocumentationChanges to the airfield map layout, alarm thresholds, or display configuration made directly on a live workstation can be difficult to trace back or roll back if something later behaves unexpectedly; keep a change log and, where the software supports it, versioned configuration backups rather than editing the live system as the only record of what changed.
Confirm UPS Runtime Actually Covers a Realistic Outage
PowerA workstation's UPS is often sized and tested when new, then left unverified for years; battery capacity degrades over time even without a real outage to reveal it, so periodically test actual runtime under load rather than trusting the UPS's self-reported status indicator alone.
Frequently Asked Questions
Short answers about the ALCMS Workstation: what it is, how it works, typical specifications, standards, maintenance and common faults.
Q1What is an ALCMS Workstation?
The ALCMS Workstation (Airfield Lighting Control and Monitoring System Workstation) is the operator's primary interface for monitoring, controlling, and managing the entire airfield ground lighting system. It is a high‑performance desktop computer or thin client that runs the ALCMS client software, connecting to the ALCMS server to display real‑time status, issue control commands, and respond to alarms. The workstation presents a graphical, geospatial representation of the airfield, allowing operators to view the status of every runway, taxiway, and approach lighting circuit at a glance.
Q2What is the purpose of an ALCMS Workstation?
The ALCMS workstation exists to give a single operator command and visibility over an entire airfield's lighting infrastructure from one seat, condensing what would otherwise be an unmanageable number of individual circuit states into a geospatial, at-a-glance view they can actually act on under time pressure. During a rapidly changing weather event or a runway configuration change ahead of an arrival, this consolidated view is what lets an operator make and execute a decision in seconds rather than working through dozens of separate systems.
Q3Where is an ALCMS Workstation used and installed?
ALCMS workstations are used in all airfields that have a modern AGL control and monitoring system, including: Air Traffic Control Towers: Providing controllers with real‑time status of runway and taxiway lighting to support safe aircraft movements during all visibility conditions. Airfield Operations Rooms: Enabling operations staff to monitor and control AGL systems during routine operations, maintenance, and emergency situations. Maintenance Control Centres: Allowing engineering and maintenance teams to diagnose faults, plan maintenance activities, and verify system performance.
Q4How does an ALCMS Workstation work?
The ALCMS workstation functions as the primary interface between the operator and the AGL system, translating complex field data into an intuitive visual representation and translating operator commands into actionable control signals: Data Presentation: The workstation receives real‑time data from the ALCMS server via the network (typically using TCP/IP and proprietary or standard protocols such as OPC UA, MODBUS, or IEC 61850).
Q5What are the typical technical parameters of an ALCMS Workstation?
Typical values are — Form Factor: Desktop tower, rack‑mount (4U), or all‑in‑one (AIO) workstation; Processor: Intel Core i7/i9 or Xeon, AMD Ryzen 7/9 (high‑performance multi‑core); Memory (RAM): 16GB to 64GB (for large airfield datasets and multi‑monitor setups); Storage: 512GB to 2TB SSD (for fast boot and application loading); Graphics: Dedicated GPU (NVIDIA Quadro, RTX, or AMD Radeon Pro) with ≥ 4GB VRAM; Display Configuration: Dual or triple 24" to 32" monitors (4K UHD recommended for detailed maps); Operating System: Windows 10/11 Pro, Windows Server (for thin client), or Linux (custom deployments).
Q6What are the electrical requirements for an ALCMS Workstation?
Typical requirements are — Circuit Type: Mains-powered IT equipment — not part of the airfield series circuit; Power Supply: 500W to 800W PSU (desktop/rack workstation), with UPS backup; Cable Type: IEC C13/C14 mains cord; Cat5e/6 Ethernet (redundant); Earthing/Grounding: Chassis bonded to the building/control-room earth; Fault Protection: UPS ride-through on mains interruption; surge protection on the mains input; Protection Class: IP20 (indoor use only); Standards: FCC, CE, RoHS, FAA AC 150/5345-56.
Q7Which standards apply to an ALCMS Workstation?
The main references are FAA AC 150/5345‑56 — Specification for L-890 Airport Lighting Control and Monitoring System (ALCMS) — includes requirements for operator interfaces; ICAO Annex 14 — Requirements for control and monitoring of AGL systems — includes human‑machine interface guidelines; IEC 61850 — Communication networks and systems for power utility automation (used for data exchange with the ALCMS server); ISO 9241 — Ergonomics of human‑system interaction — guidelines for user interface design. Always verify the current edition and your aerodrome's approved requirements.
Q8How often should an ALCMS Workstation be inspected and maintained?
Typical maintenance tasks and intervals are: OS & Software Patching (monthly); Redundant Network Link Test (semi-annual); UPS Backup Verification (annual); Storage Health Check (quarterly); Display & GPU Function Check (annual); Audible Alarm Test (monthly); Dust & Cooling Check (annual); User Access & Peripheral Review (annual). Your airport's approved maintenance programme takes precedence.
Q9How do I troubleshoot common ALCMS Workstation faults?
Common symptoms covered are: Workstation Shows "Offline" / No Live Data from ALCMS Server; Map Rendering Lags or Freezes Under Load; Status Colours Appear Inconsistent or Hard to Distinguish; ALCMS Client Crashes or Freezes Mid‑Session; Operator Slow to Respond to or Misinterprets an Alarm; Suspicious Login Activity or Unpatched Vulnerability Flagged. For example, for "Workstation Shows "Offline" / No Live Data from ALCMS Server": Likely Cause: Loss of network connectivity to the ALCMS server — a failed switch port, a downed VLAN link, or a network interface fault on the workstation itself. Diagnostic Steps: Check the workstation's network adapter status and IP configuration; ping the ALCMS server and intermediate switches; confirm the redundant network interface has failed over correctly; check switch port and VLAN status in the network management tool. Corrective Action: Restore the failed link or switch port, force failover to the redundant interface if it hasn't triggered automatically, and switch operations to a hot‑standby workstation while the primary connection is repaired.
Related Components
Go Beyond the Component. Understand the Complete AGL System.
You have explored the component. Now understand how it works within the complete Airfield Ground Lighting system.
Learn AGL from fundamentals to design, installation, testing, photometry, commissioning, maintenance and troubleshooting through structured technical training at Precision AGL Academy.
Build practical knowledge. Understand the circuit. Read the standards. Troubleshoot with confidence.
Your next step in AGL starts here.
Need expert guidance on ALCMS workstation setup, configuration, or user interface design for your airfield?
Precision AGL Academy provides advice on hardware selection, display configuration, alarm management, and operator training for effective AGL system control.
Follow the Academy
Important Notice, Disclaimer & Limitation of Liability
Please read before relying on any content on this page.
- Purpose and intended users. This page on ALCMS Workstation is an independent educational and informational reference for competent, suitably trained and authorised airfield ground lighting (AGL) and aerodrome electrical personnel. It is not professional engineering, legal or regulatory advice, and using it does not create any professional or client relationship.
- Safety. Work on series circuits, constant current regulators (CCRs), isolating transformers, cables, connectors and lighting equipment can be fatal. Always apply the aerodrome’s permit-to-work and isolation/LOTO procedures, prove dead, use correctly rated instruments and PPE, and follow the manufacturer’s instructions. Nothing here authorises work on live equipment or the bypassing of any safety device or interlock.
- Aviation operations. Nothing here authorises installation, modification, energisation, adjustment, return to service, a change of operating category (CAT I/II/III), a NOTAM or any aerodrome certification or approval decision. These rest with the aerodrome operator, the air navigation service provider and the competent regulator.
- Specifications, ratings and typical values. Descriptions, parameters, ratings, dimensions, photometric values, wattages, service lives, maintenance tasks and intervals, failure modes, certifications (for example CE, FCC, UL or IEC marks) and part or type designations are general, typical and indicative. They may not match any particular product, make, model or version, and they are not a datasheet, design, specification, selection, sizing, procurement or acceptance criterion. The manufacturer’s current documents, the approved design and the project specification prevail.
- Standards and regulations. References to ICAO, FAA, IEC, IEEE, ISO, BIS, DGCA and other standards are paraphrased summaries for orientation only. They may be incomplete or out of date, and standards are revised from time to time. Consult the current official editions. Following this content does not guarantee compliance with any law, standard or regulatory approval, and the regulator’s requirements always prevail.
- No warranty. Content is provided “as is” and “as available”, without warranty of any kind, express or implied, including accuracy, completeness, currency or fitness for a particular purpose. Real installations differ in design, equipment make and model, age and condition.
- Limitation of liability. To the fullest extent permitted by applicable law, Precision AGL Academy, Precision AGL Solutions and their owners, authors and contributors are not liable for any injury, death, loss, damage, downtime, penalty or regulatory consequence, whether direct or indirect, arising from the use of, reliance on, or inability to use this content. Nothing in this notice excludes or limits any liability that cannot lawfully be excluded or limited.
- Independence, brands and no endorsement. This is an independent publication. It is not affiliated with, sponsored by or endorsed by ICAO, the FAA, the IEC, DGCA, AAI, any airport, regulator, supplier or equipment manufacturer. Third-party names, product designations, standard designations and trademarks (including Megger®, Siemens, Eaton, Crouse-Hinds, ADB SAFEGATE, Fluke, ABB and Honeywell) belong to their respective owners and are used only for identification and description. Mention of a brand, product or supplier is not a recommendation, and we do not sell, supply or quote for any component described.
- Images and third-party content. Images and illustrations are shown to help identify the type of component. They may show products of various manufacturers, may not depict the exact item described, and are not a statement about any product’s quality, approval or performance. Copyright and trademarks in third-party images, logos and photographs belong to their respective owners and are not claimed as ours. If you are a rights holder and want an image removed, replaced or credited, email precisionaglsolutions@gmail.com with the page address and we will act promptly.
- Training and services. Mentions of training, courses, consultation, advice, selection, installation, calibration or other support, including the “Learn…Certify” pathway, describe learning stages and are not an offer, quotation, tender or promise of any result. Contacting us or our replying creates no engagement or duty of care; an engagement exists only under a written agreement. We are not a regulator or certification body, and completing any course or reading this content is not a certification, accreditation or authorisation to work on any aerodrome.
- Copyright, privacy and corrections. © 2026 Precision AGL Academy. All rights reserved. Text, structure, compilations and diagrams may be viewed for personal reference and internal training only; any other copying, republication or commercial use needs our written permission. If you email, telephone or message us, we use your details only to respond and handle your matter, in line with applicable Indian law including the Digital Personal Data Protection Act, 2023; please do not send confidential or security-sensitive information. To display this page your browser requests fonts, icons and images from third-party servers, which receive your IP address and browser details under their own policies. Content is reviewed periodically with no obligation to update. To report an error, safety concern or rights issue, write to precisionaglsolutions@gmail.com.