Individual equipment can pass every test in isolation and the AGL system can still fail as a whole. Division 19 verifies that all major AGL subsystems — CCRs, PLCs, SCADA, ALCMS, HMI, remote monitoring, and the communication network that ties them together — actually talk to each other, exchange commands correctly, provide correct status feedback, generate and transmit alarms, execute approved interlocks and sequences, and behave as one integrated airport lighting control and monitoring system.
Philosophy: Division 19 is positioned after equipment-level testing, functional testing, and SAT, because its purpose is not to prove that individual equipment works — it is to prove that Command → Communication → Control Logic → Equipment Response → Field Response → Feedback → Monitoring → Alarm/Event works correctly across the complete integrated system.
Every Division 19 test — whatever the subsystem — is proving the same underlying chain, from the moment a command is issued to the moment the system is confirmed to have recovered correctly.
The strongest Division 19 acceptance test is never just “the CCR switched ON” — every link below has to hold across the complete integrated system before a test is accepted.
| Link | What It Confirms |
|---|---|
| Command | The operator or upstream system issues the approved command through an authorized interface |
| Communication | The command is correctly transmitted across the network to the intended controller/equipment |
| Control Logic | The PLC/controller processes the command correctly, with no cross-wiring or cross-mapping |
| Equipment Response | The correct CCR or equipment operates — and only that equipment |
| Field Response | The correct AGL circuit and fixtures respond as commanded |
| Status Feedback | Actual equipment status returns accurately to the control system |
| Alarm / Event | Applicable alarms and events are correctly generated, transmitted, and logged |
| Operator Confirmation | HMI/SCADA/ALCMS displays the condition that actually exists in the field |
| Recovery | The system returns correctly to its approved normal operating condition |
Two things should be established before any Division 19 test is run — what this division is not repeating, and how alarm/priority and emergency conditions are to be handled.
| Division | Primary Question |
|---|---|
| Division 14 — Monitoring, Control & ALCMS | Does the ALCMS/control system itself work? |
| Division 15 — Functional Testing | Does the complete installed system behave correctly during operation? |
| Division 18 — SAT | Does the installed system meet the overall site acceptance requirements? |
| Division 19 — System Integration Testing | Do all independent systems communicate and work together correctly across their interfaces? |
Grouped by integration focus, in the order a complete system is normally worked through — click any topic to expand its verification checks and acceptance criteria.
Test Sequence: ALCMS Command → Communication Network → CCR → Series Circuit → AGL Fixtures → CCR Feedback → ALCMS Indication
Acceptance Criteria: the CCR displayed on the ALCMS is verified as the actual CCR being controlled, with correct status, feedback, and alarm indication.
Test: Field Signal → PLC → Control Logic → Output, and Command → PLC → Equipment → Feedback → PLC
Hold Point: any cross-wired or cross-mapped signal is corrected and retested before the PLC integration is accepted.
Test: SCADA Command → AGL Control System → Equipment, and Equipment Status → Control System → SCADA
Acceptance Criteria: the SCADA display accurately represents the actual field condition at all times, in both directions of the command/status loop.
Test: Field Condition → Controller → Communication → Remote Monitoring
Acceptance Criteria: remote monitoring correctly receives and displays every applicable status, alarm, and recovery condition generated by the field system.
Test Chain: Equipment Fault/Condition → Equipment Detection → PLC/Controller → Communication Network → ALCMS/SCADA → HMI Alarm → Alarm History
Acceptance Criteria: the complete alarm chain, from field detection to alarm history, is verified for every tested alarm condition.
Hold Point (Critical Test): for every interface tested, only the intended equipment responds — no other equipment operates.
Test Principle: Attempt Applicable Prohibited/Conflicting Operation → Interlock Logic → Unintended Operation Prevented → Correct Indication/Alarm
Acceptance Criteria: every applicable interlock operates correctly, protects the correct equipment, and generates the correct indication.
Test: Change Actual Equipment State → Observe Controller → Observe ALCMS/HMI/SCADA → Verify Correct Status
Hold Point (Critical Verification): the displayed status must correspond to the actual physical condition of the equipment at every point in the test.
Test Sequence: Operator Command → Control Interface → PLC/Controller → Communication Network → CCR/Equipment → Physical Response → Status Feedback → ALCMS/HMI/SCADA
Acceptance Criteria: this is one of the most important tests in Division 19 — for example, commanding CCR-05 ON must confirm the command is received, CCR-05 operates, the correct circuit energizes, field lights operate, CCR status changes, the ALCMS indicates ON, and no unrelated CCR operates.
Test Sequence: Normal Communication → Controlled Primary Path Failure → Redundant Path → Communication Restored → Normal Configuration
Acceptance Criteria: the system remains operational as designed, the failure is detected and alarmed, the redundant path activates where applicable, and recovery occurs correctly.
Hold Point: any cross-assigned or incorrectly addressed device is corrected before the network is accepted.
Test: Remote Command → Communication → Control System → CCR → Circuit → Fixture
Acceptance Criteria: every tested remote command produces the correct field response within any specified response time, with correct feedback and indication.
Test Chain: Failure → Detection → Communication → Alarm → Identification → Event → Recovery
Acceptance Criteria: every applicable failure condition is correctly detected, alarmed, identified, logged, and recovered.
Example Classification: the project alarm philosophy defines categories such as Critical, Major, Minor, and Advisory
Hold Point: alarm priorities are never assigned solely during testing — they are verified against the approved alarm matrix.
Test: generate a controlled event and verify Actual Event → System Detection → Event Log → Correct Information
Acceptance Criteria: every tested event is correctly logged with accurate description, identification, timestamp, and sequence, and can be retrieved.
Example: Runway Lighting Command → ALCMS → PLC → CCR → Series Circuit → Runway Fixtures → Status Feedback → ALCMS Indication
Acceptance Criteria: every predefined sequence involving multiple systems executes correctly, in the correct order, with correct feedback and no unintended operation.
Test Chain: Emergency Condition/Command → Emergency Logic → PLC/Control System → CCR/AGL Equipment → Field Response → ALCMS Feedback → Alarm/Event
Hold Point: emergency testing must be carefully coordinated with airport operations and ATC where the test could affect operational lighting.
Acceptance Criteria: this is the highest-level test in Division 19 — the complete integrated AGL control, monitoring, and field system is demonstrated to operate correctly across the full command → communication → control logic → equipment response → field response → feedback → monitoring → alarm/event chain, and is restored to its approved normal condition.
Topic 18 runs as a single continuous 10-step sequence per system/circuit, and is the final gate before integration acceptance is issued.
Select the required AGL system/circuit through the approved control interface.
Send the required ON/OFF/intensity command.
Confirm the command reaches the intended controller/CCR.
Confirm the correct equipment operates.
Confirm the correct AGL fixtures operate.
Confirm actual equipment status returns to the control system.
Confirm the correct status appears on all applicable interfaces.
Where a controlled test condition is introduced, verify alarm transmission.
Confirm the event is correctly recorded.
Restore the system to the approved normal operating condition.
Quick answers about Division 19 — System Integration Testing in the AGL Testing & Commissioning Manual.
Division 19 of the AGL Testing & Commissioning Manual covers System Integration Testing. Individual equipment can pass every test in isolation and the AGL system can still fail as a whole. Division 19 verifies that all major AGL subsystems — CCRs, PLCs, SCADA, ALCMS, HMI, remote monitoring, and the communication network that ties them together — actually talk to each other, exchange commands correctly, provide correct status feedback, generate and transmit alarms, execute approved interlocks and sequences, and behave as one integrated airport lighting control and monitoring system. It contains 18 topics (TC-SIT-001 to TC-SIT-018) organised into 5 groups (A–E), each topic with its own verification checks.
Division 19 is positioned after equipment-level testing, functional testing, and SAT, because its purpose is not to prove that individual equipment works — it is to prove that Command → Communication → Control Logic → Equipment Response → Field Response → Feedback → Monitoring → Alarm/Event works correctly across the complete integrated system.
Every Division 19 test — whatever the subsystem — is proving the same underlying chain, from the moment a command is issued to the moment the system is confirmed to have recovered correctly. Steps: Command → Communication → Control Logic → Equipment Response → Field Response → Status Feedback → Alarm / Event → Operator Confirmation → Recovery. Focus areas: Subsystem interfaces; Command & feedback loop; Network & redundancy; Alarm, event & sequence logic; Emergency & full-system proof.
Division 19 has 18 topics in 5 groups. A — Subsystem Integration: CCR-to-ALCMS Integration, PLC Integration, SCADA Integration, Remote-Monitoring Integration. B — Command & Control Verification: Alarm Communication, Control-Interface Verification, Interlocking Verification, Equipment-Status Feedback, Command-Feedback Verification. C — Network & Communication Resilience: Communication Redundancy, Network Communication, Remote-Control Response, Failure Communication. D — Alarm, Event & Sequence Verification: Alarm Prioritization, Event Logging, System Sequence Verification. E — Emergency & Final Acceptance: Integrated Emergency Operation, Complete System Integration Test.
The strongest Division 19 acceptance test is never just “the CCR switched ON” — every link below has to hold across the complete integrated system before a test is accepted. Command: The operator or upstream system issues the approved command through an authorized interface; Communication: The command is correctly transmitted across the network to the intended controller/equipment; Control Logic: The PLC/controller processes the command correctly, with no cross-wiring or cross-mapping; Equipment Response: The correct CCR or equipment operates — and only that equipment; Field Response: The correct AGL circuit and fixtures respond as commanded; Status Feedback: Actual equipment status returns accurately to the control system; Alarm / Event: Applicable alarms and events are correctly generated, transmitted, and logged; Operator Confirmation: HMI/SCADA/ALCMS displays the condition that actually exists in the field; Recovery: The system returns correctly to its approved normal operating condition.
Two things should be established before any Division 19 test is run — what this division is not repeating, and how alarm/priority and emergency conditions are to be handled. Division 19 Is Not a Repeat: Division 14 asks whether the ALCMS/control system itself works; Division 15 asks whether the complete installed system behaves correctly during operation; Division 18 (SAT) asks whether the installed system meets overall site acceptance requirements; Division 19 asks whether all independent systems communicate and work together correctly across their interfaces. Coordination & Priority Rules: Alarm priorities are never assigned during testing — they are verified against the approved alarm matrix/philosophy; Emergency-operation testing must be carefully coordinated with airport operations and ATC where the test could affect operational lighting; Every command test must confirm that only the intended equipment responds — no unintended operation; No integration test is closed until the system is restored to its approved normal operating condition.
Each division answers a different primary question. Division 14 — Monitoring, Control & ALCMS: Does the ALCMS/control system itself work?; Division 15 — Functional Testing: Does the complete installed system behave correctly during operation?; Division 18 — SAT: Does the installed system meet the overall site acceptance requirements?
Topic 18 runs as a single continuous 10-step sequence per system/circuit, and is the final gate before integration acceptance is issued. (1) Select System — Select the required AGL system/circuit through the approved control interface; (2) Issue Command — Send the required ON/OFF/intensity command; (3) Verify Communication — Confirm the command reaches the intended controller/CCR; (4) Verify Equipment Response — Confirm the correct equipment operates; (5) Verify Field Response — Confirm the correct AGL fixtures operate; (6) Verify Feedback — Confirm actual equipment status returns to the control system; (7) Verify HMI/SCADA — Confirm the correct status appears on all applicable interfaces; (8) Verify Alarm — Where a controlled test condition is introduced, verify alarm transmission; (9) Verify Event — Confirm the event is correctly recorded; (10) Restore Normal Condition — Restore the system to the approved normal operating condition.
System integration testing proves that independently commissioned subsystems work correctly together.
Build the technical knowledge to understand interface testing, data exchange verification, and how a fault in one subsystem can propagate through an integrated AGL system if integration testing is skipped.
Integrate with precision. Verify with confidence. Commission with certainty.
Please read before relying on any content on this page or on any record downloaded from it.