This division verifies how the complete AGL system behaves during actual operational conditions — energization, de-energization, intensity control, switching, alarms, faults, control modes, interlocks, emergency operation, failure response, recovery, power restoration, and standby operation. Divisions 02–14 establish that individual equipment, circuits, and control interfaces are technically ready; Division 15 demonstrates that they work together as an operational system.
Distinction: component testing proves that equipment works. Functional testing proves that the equipment works correctly together as an operational AGL system. Every topic in this division follows the same underlying chain — Command → System Response → Field Operation → Monitoring/Feedback → Alarm/Indication → Recovery — before the system is carried forward into performance/photometric verification and final acceptance.
Every functional test in this division is a demonstration of the same underlying chain, regardless of which circuit, mode, or condition is under test.
Division 15 sits above the equipment-specific divisions and below final acceptance — each stage below has to pass before the next is meaningful.
| Stage | What It Confirms |
|---|---|
| Individual Equipment | Divisions 02–14 confirm each component, circuit, and control interface is technically functional on its own |
| Circuit | Each complete AGL circuit — CCR, series loop, and fixtures — operates correctly as an integrated circuit |
| Control / Monitoring | Intensity, switching, and control functions respond correctly from the operating interface through to the field |
| Functional Operation | Local, remote, and emergency operation, plus interlocks and the full system sequence, behave as designed |
| Failure Response | The system responds correctly and safely to an approved failure condition |
| Recovery | The system recovers correctly after a fault, power interruption, or standby transfer clears |
| System Functional Acceptance | The complete Functional Acceptance Test consolidates every stage above into a single sign-off |
Two requirement groups should be closed out before the Division 15 team starts working through the topic list.
Grouped by functional-test focus, in the order the system is normally worked through — click any topic to expand its verification checks and pass criteria.
Sequence: Select Circuit → Energize → Observe Complete Circuit → Verify Field Fixtures → Verify CCR → Verify ALCMS/HMI Status → De-energize.
Pass Criteria: the circuit energizes and de-energizes correctly with the right fixtures, CCR response, and ALCMS/HMI status — no dark fixtures, incorrect operation, or unexpected alarms.
Sequence: Energization Command → CCR → Series Circuit → Fixtures → Feedback.
Pass Criteria: the circuit energizes promptly on command with correct CCR response, normal current, correct fixture response, and correct status indication.
Pass Criteria: the commanded circuit reaches OFF completely and promptly, with correct status feedback and no unintended effect on any other circuit.
Sequence: Operator Command → HMI/ALCMS → PLC/Controller → CCR → Series Circuit → AGL Fixtures.
Pass Criteria: every commanded intensity step is reproduced correctly at the CCR, in the field, and on the HMI feedback, with no unintended circuit change.
Sequence: Command → Logic → Output → Equipment → Feedback.
Pass Criteria: the programmed switching logic operates only the intended equipment, in the intended sequence, with correct feedback and no logic conflict.
Sequence: Fault/Condition → Detection → Alarm → HMI/SCADA → Operator Indication → Alarm History.
Pass Criteria: every applicable alarm generates correctly, displays on HMI/SCADA, and is captured in the alarm history.
Pass Criteria: the fault indication correctly names the specific affected equipment/circuit, per the approved system design, and logs the event.
Pass Criteria: every applicable control function operates correctly both individually and as part of the full operational sequence.
Pass Criteria: local control operates correctly and the approved local/remote control priority is respected.
Sequence: Remote Command → Control System → CCR → Circuit → Fixture → Feedback.
Pass Criteria: remote commands reach only the intended equipment, with correct field response and correct status/alarm feedback.
Sequence: Emergency Condition/Command → Emergency Logic → Required AGL Response → Field Verification → HMI/SCADA Verification.
Hold Point: emergency testing is coordinated with airport operations/ATC whenever the test affects operational lighting.
Sequence: Attempt Applicable Conflicting/Prohibited Operation → Interlock Operates → Unintended Operation Prevented → Correct Indication Generated.
Pass Criteria: every applicable interlock prevents the prohibited operation, generates correct indication, and the event is recorded where applicable.
Sequence: Operator Command → ALCMS → CCR Selection → Circuit Energization → Intensity Selection → Field Lighting Operation → Status Feedback → Alarm Monitoring.
Pass Criteria: every step of the predefined sequence occurs in the correct order, within any specified timing, ending in the correct final system condition. This is one of the most important tests in Division 15.
Sequence: Failure → Detection → Alarm → Indication → Required System Response.
Pass Criteria: the approved failure condition is detected, alarmed, and correctly identified, with the required fallback response and no unsafe switching.
Sequence: Normal Operation → Controlled Fault → Fault Detection → Alarm → Fault Removal → System Recovery → Normal Operation.
Pass Criteria: the system returns cleanly to normal operation once the fault is removed, with no residual fault, persistent alarm, or unexpected equipment operation.
Sequence: Normal Operation → Controlled Power Interruption → System Response → Power Restoration → System Initialization → Equipment Recovery → Status Verification.
Pass Criteria: after power restoration, the system returns to the correct predefined state as required by the approved control philosophy — not merely whatever state results automatically.
Sequence: Normal System → Standby Condition → Transfer → Standby Operation → Monitoring → Return to Normal.
Pass Criteria: the standby/backup system transfers correctly, maintains continuity of equipment, control, and monitoring, and returns cleanly to the normal system.
Readiness Criteria: every category (A–F above) is closed with a PASS, RETEST REQUIRED items are cleared or formally accepted, and Functional Acceptance is signed — closing Division 15 and handing the system into performance/photometric verification and final handover.
The Functional Testing Report consolidates every category into a single, sign-off-ready record.
| Report Section | Contents |
|---|---|
| Project Information | Airport, project, system, area, test date, contractor, test engineer, client/consultant |
| Test Scope | Circuits, CCRs, control systems, and AGL equipment covered |
| Test Equipment | Instrument, manufacturer, model, serial number, calibration certificate, calibration validity |
| Functional Test Results | The complete FUNC-01–18 test matrix |
| Alarm & Fault Results | All alarm and failure tests |
| Interlock Results | All applicable interlock tests |
| Recovery Results | Fault recovery, communication recovery, power restoration, standby transfer |
| Punch List | Observation, location, corrective action, retest, status |
| Final Acceptance | Functional System Status — PASS / FAIL / RETEST REQUIRED / CONDITIONAL ACCEPTANCE |
| Sign-Off | Tested by, checked by, contractor, consultant, client, date |
When a functional test uncovers a genuine deviation rather than an approved test condition, the same sequence applies across every topic in this division.
Confirm exactly which command, step, or condition produced the unexpected result.
Identify the specific affected circuit, CCR, or control element — not a generic system fault.
Safety-critical / test-blocking / minor, and whether it affects operational lighting.
Add to the punch-list with owner and target date.
Rectify the equipment, logic, or configuration causing the deviation.
Re-run the specific functional test against the same pass criteria.
Update the FUNC matrix and punch-list before sign-off.
Unresolved test-blocking items withhold Functional Acceptance sign-off.
Quick answers about Division 15 — Functional Testing in the AGL Testing & Commissioning Manual.
Division 15 of the AGL Testing & Commissioning Manual covers Functional Testing. This division verifies how the complete AGL system behaves during actual operational conditions — energization, de-energization, intensity control, switching, alarms, faults, control modes, interlocks, emergency operation, failure response, recovery, power restoration, and standby operation. Divisions 02–14 establish that individual equipment, circuits, and control interfaces are technically ready; Division 15 demonstrates that they work together as an operational system. It contains 18 topics (TC-FUNC-001 to TC-FUNC-018) organised into 7 groups (A–G), each topic with its own verification checks.
Component testing proves that equipment works. Functional testing proves that the equipment works correctly together as an operational AGL system. Every topic in this division follows the same underlying chain — Command → System Response → Field Operation → Monitoring/Feedback → Alarm/Indication → Recovery — before the system is carried forward into performance/photometric verification and final acceptance.
Every functional test in this division is a demonstration of the same underlying chain, regardless of which circuit, mode, or condition is under test. Steps: Command → System Response → Field Operation → Monitoring/Feedback → Alarm/Indication → Recovery. Focus areas: Normal operation; Control & switching; Safety & interlock; Alarm & fault; Failure & recovery.
Division 15 has 18 topics in 7 groups. A — Circuit Functional Operation: Circuit Operation Testing, Circuit Energization Test, Circuit De-Energization Test. B — Intensity & Switching: Intensity-Control Test, Switching-Logic Test. C — Alarms & Faults: Alarm Verification, Fault Indication Test, Control-Function Test. D — Local, Remote & Emergency Operation: Local-Control Test, Remote-Control Test, Emergency-Operation Test. E — Interlock & Sequence Testing: Equipment Interlock Test, System Sequence Test. F — Failure & Recovery: Failure-Response Test, Recovery Test, Power-Restoration Test, Standby-System Test. G — Final Functional Acceptance: Functional Acceptance Test.
Division 15 sits above the equipment-specific divisions and below final acceptance — each stage below has to pass before the next is meaningful. Individual Equipment: Divisions 02–14 confirm each component, circuit, and control interface is technically functional on its own; Circuit: Each complete AGL circuit — CCR, series loop, and fixtures — operates correctly as an integrated circuit; Control / Monitoring: Intensity, switching, and control functions respond correctly from the operating interface through to the field; Functional Operation: Local, remote, and emergency operation, plus interlocks and the full system sequence, behave as designed; Failure Response: The system responds correctly and safely to an approved failure condition; Recovery: The system recovers correctly after a fault, power interruption, or standby transfer clears; System Functional Acceptance: The complete Functional Acceptance Test consolidates every stage above into a single sign-off.
Two requirement groups should be closed out before the Division 15 team starts working through the topic list. Reference Package: Approved control philosophy, functional requirement, and emergency philosophy documents; Circuit, CCR, and ALCMS/HMI schedules with correct circuit-to-CCR association; Approved alarm matrix and interlock logic schedule; Divisions 02–14 test records showing equipment-level PASS status; Standby/backup system design and approved transfer philosophy. Coordination & Access: Confirm Divisions 01–14 are closed or formally accepted with open items; Coordinate energization windows and emergency/failure simulations with ATC/airport operations; Confirm personnel are briefed on which circuits/modes will be commanded live; Do not assume automatic power-restoration behaviour is acceptable — verify it against the approved control philosophy.
The Functional Testing Report consolidates every category into a single, sign-off-ready record. Project Information: Airport, project, system, area, test date, contractor, test engineer, client/consultant; Test Scope: Circuits, CCRs, control systems, and AGL equipment covered; Test Equipment: Instrument, manufacturer, model, serial number, calibration certificate, calibration validity; Functional Test Results: The complete FUNC-01–18 test matrix; Alarm & Fault Results: All alarm and failure tests; Interlock Results: All applicable interlock tests; Recovery Results: Fault recovery, communication recovery, power restoration, standby transfer; Punch List: Observation, location, corrective action, retest, status; Final Acceptance: Functional System Status — PASS / FAIL / RETEST REQUIRED / CONDITIONAL ACCEPTANCE; Sign-Off: Tested by, checked by, contractor, consultant, client, date.
When a functional test uncovers a genuine deviation rather than an approved test condition, the same sequence applies across every topic in this division. (1) Detect — Confirm exactly which command, step, or condition produced the unexpected result; (2) Isolate — Identify the specific affected circuit, CCR, or control element — not a generic system fault; (3) Classify — Safety-critical / test-blocking / minor, and whether it affects operational lighting; (4) Log — Add to the punch-list with owner and target date; (5) Correct — Rectify the equipment, logic, or configuration causing the deviation; (6) Retest — Re-run the specific functional test against the same pass criteria; (7) Record — Update the FUNC matrix and punch-list before sign-off; (8) Escalate — Unresolved test-blocking items withhold Functional Acceptance sign-off.
Functional testing confirms that every commissioned system performs as an integrated whole, not just as isolated components.
Build the technical knowledge to understand end-to-end operational verification, and how functional testing ties together every division that came before it into one proven, working system.
Test with precision. Integrate with confidence. Commission with certainty.
Please read before relying on any content on this page or on any record downloaded from it.