Divisions 01–13 qualify the individual pieces of AGL equipment. Division 14 verifies that all of it comes together as one integrated system through the Airfield Lighting Control and Monitoring System — HMI, PLC, SCADA interfaces, CCR communication, remote monitoring, remote control, alarms, status feedback, interlocks, switching logic, and event recording. This is the system-integration commissioning division: the point at which individual equipment acceptance becomes airport-wide operational control and monitoring capability.
Philosophy: ALCMS commissioning is not demonstrated by a working HMI screen alone. Every function is verified as a complete, closed-loop chain — Operator Command → HMI/SCADA → PLC → Communication Network → CCR → AGL Circuit → Field Equipment → Status Feedback → HMI/SCADA — and the equivalent reverse chain for monitoring, alarms and events.
ALCMS Installation → HMI → PLC → Communication → CCR → Field Equipment → Status Feedback → Control → Alarms → Interlocks → Events → Emergency Operation → Functional Acceptance.
ALCMS is evaluated as a complete, closed-loop chain — every link has to hold, in both the control direction and the monitoring direction, before the system is accepted.
| Link | What It Confirms |
|---|---|
| Installation Verified | ALCMS panels, HMI, PLC, network and control wiring match the approved architecture |
| HMI/PLC/SCADA Functional | Displayed data, logic execution and integrated interfaces reflect actual field equipment |
| CCR Communication Verified | Each CCR is individually addressed — a command to one CCR never operates another |
| Remote Monitoring Verified | Physical equipment condition matches HMI/SCADA indication under observed conditions |
| Remote Control Verified | The intended equipment responds; unintended equipment remains unaffected |
| Status Feedback Verified | Displayed status equals actual field condition, never assumed from the HMI alone |
| Interlocks & Logic Verified | Prohibited/conflicting commands are blocked; switching logic executes correctly |
| Alarms & Logging Verified | Alarms, alarm history and event log correctly capture real system activity |
| Failure & Emergency Response Verified | Communication-failure and emergency conditions produce the approved system behaviour |
| ALCMS Accepted | All applicable results are recorded, punch points closed, and the system formally accepted |
Two conditions should be established before ALCMS functional testing begins.
Grouped by commissioning focus, in the order the ALCMS is normally worked through — click any topic to expand its verification checks and acceptance criteria.
Hold Point: the physical installation must fully correspond with the approved design and control architecture before functional testing proceeds.
Acceptance Criteria: every HMI screen, indication and control accurately reflects real field equipment and status — not merely that the screen is operational.
Hold Point: any incorrect I/O mapping or wrong equipment association is corrected and retested before the PLC is accepted.
Acceptance Criteria: SCADA integration is verified where provided — data flows correctly and consistently in both directions.
Hold Point: cross-CCR command isolation must be positively demonstrated before proceeding to remote-control testing.
Acceptance Criteria: field equipment can be remotely monitored with the monitored value matching the physical condition under every tested condition.
Hold Point: any unintended equipment response to a remote command is investigated and corrected before acceptance.
Acceptance Criteria: every applicable alarm is transmitted correctly and promptly from field fault to HMI/SCADA indication.
Hold Point: every status feedback point is physically verified against the actual field condition, not accepted on HMI display alone.
Acceptance Criteria: every applicable control interface correctly selects, executes, and confirms commands on the intended equipment.
Hold Point: interlock testing is only performed under approved test conditions and coordination; safety functions are never bypassed for the purpose of the test.
Acceptance Criteria: programmed switching logic executes exactly as designed, with correct sequence, timing and feedback.
Acceptance Criteria: every commanded intensity step is correctly transmitted, applied at the CCR, and confirmed both in the field and on the HMI.
Acceptance Criteria: the alarm history provides a complete, accurate and traceable record of every generated alarm.
Acceptance Criteria: the event log provides a reliable, chronologically correct record of all significant control-system activity.
Hold Point: communication-failure testing that could affect operational lighting is performed only with ATC/operations coordination.
Hold Point: any deviation from the defined emergency/control philosophy is treated as a critical non-conformance.
Acceptance Criteria: local and remote modes each behave correctly per the approved philosophy, and the active mode is always unambiguously indicated.
Acceptance Criteria: ALCMS Functional Acceptance = Installation + HMI + PLC + SCADA + Communication + Monitoring + Control + Feedback + Alarms + Interlocks + Switching Logic + Intensity Commands + Event Logging + Communication-Failure Response + Emergency Control + Local/Remote Operation → ALCMS Accepted.
Acceptance Criteria: a dedicated, traceable ALCMS Commissioning Report is completed and signed off — this closes Division 14 and confirms the airport-wide monitoring and control environment is operational.
Division 14 runs as a single continuous system-integration sequence, from installation through to functional acceptance and the commissioning report.
Verify ALCMS panel, HMI, PLC, network and wiring installation.
Verify HMI displays and PLC hardware/I/O against field equipment.
Verify bidirectional SCADA data flow where provided.
Verify individually addressed communication with each CCR.
Confirm monitored values match physical equipment condition.
Confirm intended-equipment response, no unintended operation.
Verify alarm transmission and true status feedback.
Verify interlocks, switching logic and intensity commands.
Verify alarm history and event-log recording accuracy.
Verify communication-failure and emergency-control behaviour.
Verify mode transfer and unambiguous active-mode indication.
Close punch-list, complete acceptance and the commissioning report.
Quick answers about Division 14 — Monitoring, Control & ALCMS Testing in the AGL Testing & Commissioning Manual.
Division 14 of the AGL Testing & Commissioning Manual covers Monitoring, Control & ALCMS Testing. Divisions 01–13 qualify the individual pieces of AGL equipment. Division 14 verifies that all of it comes together as one integrated system through the Airfield Lighting Control and Monitoring System — HMI, PLC, SCADA interfaces, CCR communication, remote monitoring, remote control, alarms, status feedback, interlocks, switching logic, and event recording. This is the system-integration commissioning division: the point at which individual equipment acceptance becomes airport-wide operational control and monitoring capability. It contains 20 topics (TC-ALCMS-001 to TC-ALCMS-020) organised into 5 groups (A–E), each topic with its own verification checks.
ALCMS commissioning is not demonstrated by a working HMI screen alone. Every function is verified as a complete, closed-loop chain — Operator Command → HMI/SCADA → PLC → Communication Network → CCR → AGL Circuit → Field Equipment → Status Feedback → HMI/SCADA — and the equivalent reverse chain for monitoring, alarms and events.
ALCMS Installation → HMI → PLC → Communication → CCR → Field Equipment → Status Feedback → Control → Alarms → Interlocks → Events → Emergency Operation → Functional Acceptance. Steps: Install & Configure → Verify HMI/PLC/SCADA → Verify Communication → Verify Monitoring → Verify Control → Verify Alarms & Feedback → Verify Interlocks & Logic → Verify Logging → Verify Failure/Emergency Response → Accept → Report. Focus areas: System architecture & installation; Communication integrity; Monitoring & status accuracy; Control & safety logic; Recording & fault response.
Division 14 has 20 topics in 5 groups. A — ALCMS System Verification: ALCMS Installation Verification, HMI Verification, PLC Verification, SCADA Integration Testing. B — Communication & Monitoring: CCR Communication Testing, Remote-Monitoring Verification, Remote-Control Testing, Alarm Communication Testing, Equipment-Status Feedback Testing. C — Control & Logic: Control-Interface Testing, Interlocking Verification, Switching-Logic Verification, Intensity-Command Verification. D — Recording & Fault Response: Alarm-History Verification, Event-Log Verification, Communication-Failure Testing, Emergency-Control Testing, Local/Remote Control Verification. E — System Acceptance: ALCMS Functional Acceptance, ALCMS Commissioning Report.
ALCMS is evaluated as a complete, closed-loop chain — every link has to hold, in both the control direction and the monitoring direction, before the system is accepted. Installation Verified: ALCMS panels, HMI, PLC, network and control wiring match the approved architecture; HMI/PLC/SCADA Functional: Displayed data, logic execution and integrated interfaces reflect actual field equipment; CCR Communication Verified: Each CCR is individually addressed — a command to one CCR never operates another; Remote Monitoring Verified: Physical equipment condition matches HMI/SCADA indication under observed conditions; Remote Control Verified: The intended equipment responds; unintended equipment remains unaffected; Status Feedback Verified: Displayed status equals actual field condition, never assumed from the HMI alone; Interlocks & Logic Verified: Prohibited/conflicting commands are blocked; switching logic executes correctly; Alarms & Logging Verified: Alarms, alarm history and event log correctly capture real system activity; Failure & Emergency Response Verified: Communication-failure and emergency conditions produce the approved system behaviour; ALCMS Accepted: All applicable results are recorded, punch points closed, and the system formally accepted.
Two conditions should be established before ALCMS functional testing begins. Control Philosophy Governs Everything: Approved control and emergency philosophy documents define expected behaviour — never assume a "sensible" response; Interlock testing is performed only under approved test conditions and must never defeat a safety function merely to demonstrate it; Communication-failure testing that could affect operational lighting is coordinated with ATC/operations beforehand; Emergency-control testing confirms exact conformance to the defined philosophy, not merely that "something" happens.
Division boundary: Divisions 01–13 verify individual AGL equipment (CCRs, transformers, cabling, fixtures, etc.); Division 14 verifies the integrated system that monitors and controls that equipment; A displayed HMI status is never accepted as proof of a field condition — it must be cross-checked against the physical equipment; No ALCMS function is accepted until the full command/monitoring chain has been demonstrated end to end.
Division 14 runs as a single continuous system-integration sequence, from installation through to functional acceptance and the commissioning report. (1) Installation Verification — Verify ALCMS panel, HMI, PLC, network and wiring installation; (2) HMI & PLC Verification — Verify HMI displays and PLC hardware/I/O against field equipment; (3) SCADA Integration — Verify bidirectional SCADA data flow where provided; (4) CCR Communication — Verify individually addressed communication with each CCR; (5) Remote Monitoring — Confirm monitored values match physical equipment condition; (6) Remote Control — Confirm intended-equipment response, no unintended operation; (7) Alarms & Status Feedback — Verify alarm transmission and true status feedback; (8) Interlocks & Logic — Verify interlocks, switching logic and intensity commands; (9) Alarm History & Events — Verify alarm history and event-log recording accuracy; (10) Failure & Emergency Response — Verify communication-failure and emergency-control behaviour; (11) Local/Remote Modes — Verify mode transfer and unambiguous active-mode indication; (12) Functional Acceptance & Report — Close punch-list, complete acceptance and the commissioning report.
ALCMS testing confirms that monitoring and control functions reflect what's really happening in the field.
Build the technical knowledge to understand status feedback, fault reporting, remote control verification, and how accurate monitoring underpins every operational decision made from the control room.
Test with precision. Monitor with confidence. Commission with certainty.
Please read before relying on any content on this page or on any record downloaded from it.