The dedicated failure classification for modern, connected, intelligent and software-dependent AGL technologies — extending the Failure Database beyond conventional electrical, mechanical and component failures into systems where reliability depends on LED technology, smart sensors, IoT communication, wireless networks, smart controllers, remote monitoring, software, firmware, configuration management, cybersecurity, data synchronization, digital-twin platforms, cloud services and system interoperability.
Key principle — An emerging-technology failure may be physical, digital, communication-related, configuration-related or software-related — even when the underlying AGL hardware remains electrically healthy. Division 20 does not replace the conventional failure divisions; it adds a technology/reliability classification layer, answering both what physically/digitally failed? and what technology-related factor contributed to the failure?
Progressive deterioration of an LED-based AGL system resulting in reduced performance, reliability or useful service life.
Check:
An individual LED failure belongs primarily to Division 01. A systematic or progressive LED technology degradation issue can additionally be classified under Division 20.
A smart sensor fails to measure, detect, transmit or report the intended parameter correctly.
Loss of communication between an IoT-enabled AGL device and the associated monitoring/network infrastructure.
Failure of wireless communication required for monitoring, control, sensing or data transmission.
Check:
Failure of an AGL equipment system whose operation or monitoring depends on network connectivity.
The equipment itself may remain operational locally while becoming unavailable through the network.
Failure of an intelligent AGL controller to perform its programmed monitoring, control, processing or communication functions.
Cross-reference with Division 07 — Control System Failures.
The remote monitoring system fails to correctly receive, display, store or report AGL equipment condition.
A software update does not complete correctly or results in degraded, unavailable or abnormal system operation.
Software update activities should include:
Firmware malfunction or corruption affects the operation of an AGL intelligent device.
Incorrect or corrupted system configuration causes abnormal operation.
The hardware may be healthy; the configuration itself is the failure mechanism.
A cybersecurity-related condition affects the availability, integrity or reliable operation of an AGL digital/connected system.
The Failure Database should record the operational consequence, not sensitive security details.
A configuration is changed without appropriate authorization, approval, control or documentation, resulting in an operational or reliability issue.
Data between connected AGL systems becomes inconsistent, delayed, incomplete or unavailable.
The digital representation of an AGL asset/system does not accurately correspond with the actual physical asset or its current condition.
The digital twin should be treated as a representation of the physical asset, not automatically as the authoritative physical condition.
Failure of communication between AGL equipment/platforms and the associated cloud-based service.
Two or more intelligent/networked systems cannot exchange or correctly interpret information or commands as intended.
Record structure, failure chains, diagnostic matrix, cross-division mapping and core principles that apply across all 16 Division 20 failure topics.
For each Division 20 event, record the following fields across six groups:
Technology identification
Connectivity
Failure
Digital information
Investigation & corrective action
Verification & reliability
Each Division 20 failure category follows a recognisable propagation chain from initial trigger to operational consequence:
Primary investigation focus for each of the 16 Division 20 failure topics:
| No. | Failure | Primary investigation |
|---|---|---|
| ETF-01 | LED system degradation | LED performance/lifecycle |
| ETF-02 | Smart sensor failure | Sensor/measurement |
| ETF-03 | IoT communication loss | IoT communication path |
| ETF-04 | Wireless communication failure | Wireless network |
| ETF-05 | Networked-equipment failure | Network-dependent equipment |
| ETF-06 | Smart AGL controller failure | Controller hardware/software |
| ETF-07 | Remote-monitoring failure | Monitoring chain |
| ETF-08 | Software update failure | Update process/software |
| ETF-09 | Firmware failure | Firmware/version |
| ETF-10 | Configuration failure | Configuration parameters |
| ETF-11 | Cybersecurity-related operational issue | Security-related operational impact |
| ETF-12 | Unauthorized configuration change | Change/configuration control |
| ETF-13 | Data synchronization failure | Data exchange/synchronization |
| ETF-14 | Digital-twin synchronization error | Physical/digital consistency |
| ETF-15 | Cloud communication failure | Cloud connectivity |
| ETF-16 | Smart-system interoperability failure | System interfaces/protocols |
Division 20 does not replace the conventional failure divisions — it adds a technology/reliability classification layer alongside them:
| Emerging technology failure | Related division |
|---|---|
| LED system degradation | Division 01 / 19 |
| Smart sensor failure | Division 07 / 19 |
| IoT communication loss | Division 07 |
| Wireless communication failure | Division 07 |
| Networked-equipment failure | Division 07 |
| Smart AGL controller failure | Division 07 / 19 |
| Remote-monitoring failure | Division 07 |
| Software update failure | Division 07 |
| Firmware failure | Division 07 / 19 |
| Configuration failure | Division 07 |
| Cybersecurity-related operational issue | Division 07 |
| Unauthorized configuration change | Division 07 / 08 |
| Data synchronization failure | Division 07 |
| Digital-twin synchronization error | Asset/data management |
| Cloud communication failure | Division 07 |
| Smart-system interoperability failure | Division 07 / 17 |
Division 20 should be treated as the future-facing layer of the AGL Failure Database. It captures failures that conventional AGL databases can easily miss — particularly situations where the light, CCR, sensor or controller is physically healthy but its connected, software, communication, configuration or digital ecosystem is not functioning correctly. It also creates a direct bridge between the AGL Failure Database, AGL Product Encyclopedia, ALCMS/control-system documentation, testing & commissioning procedures, maintenance records and future smart-airport/digital-twin knowledge base.
Quick answers about connected, smart and software-dependent AGL failures, as covered in Division 20 of the AGL Failure Database.
Division 20 covers modern, connected, intelligent and software-dependent AGL technologies. It contains 16 published topics (ETF-01 to ETF-16) spanning LED degradation, smart sensors, IoT and wireless communication, smart controllers, software and firmware, configuration, cybersecurity, digital twins, cloud and interoperability failures.
LED system degradation, smart sensor failure, IoT communication loss, wireless communication failure, networked-equipment failure, smart AGL controller failure, remote-monitoring failure, software update failure, firmware failure, configuration failure, cybersecurity-related operational issue, unauthorized configuration change, data synchronization failure, digital-twin synchronization error, cloud communication failure and smart-system interoperability failure.
They fall into six groups: LED & Smart Device Technology (2 topics), Connected & Networked System Failures (5), Software & Firmware Failures (3), Cybersecurity & Configuration Control (2), Data & Digital-Twin Failures (2) and Cloud & Interoperability (2).
It captures failures that conventional AGL databases can easily miss, particularly where the light, CCR, sensor or controller is physically healthy but its connected, software, communication, configuration or digital ecosystem is not functioning correctly. It does not replace the conventional divisions; it adds a technology and reliability classification layer alongside them.
Each category follows a recognisable propagation chain. In the smart-sensor chain, degradation leads to incorrect measurement, incorrect data, incorrect monitoring or status and an affected operational decision. In the IoT chain, a network interruption causes IoT communication loss, remote monitoring becomes unavailable, equipment status is not visible and maintenance response is delayed. Software-update, firmware, configuration, digital-twin and interoperability chains are also captured.
LED system degradation relates to Divisions 01 and 19, and smart sensor failure to Divisions 07 and 19. IoT communication loss, wireless communication failure and networked-equipment failure relate to Division 07, and smart AGL controller failure to Divisions 07 and 19.
Records span six groups, beginning with technology identification: failure ID, airport, asset ID, equipment type, smart-system type, manufacturer, model, software, firmware and configuration versions. Connectivity fields cover communication type, network, gateway, controller, cloud or platform and communication status, and failure fields cover category, mode, date/time, duration and operational impact.
LED drivers, IoT-enabled fixtures and smart CCR interfaces fail differently than legacy AGL equipment — real troubleshooting means building the same depth of understanding for new technology that you already have for series-circuit fundamentals.
Take that knowledge further with Precision AGL Academy.
Learn how to connect:
Develop structured knowledge across AGL fundamentals, components, electrical systems, testing, photometry, troubleshooting, maintenance and commissioning.
Find the failure. Understand the cause. Build the engineering skill.
Please read before relying on any content on this page or on any record downloaded from it.