Conventional AGL vs IoT-Enabled AGL

Basic Comparison

Conventional AGL Architecture

   AGL CONTROL SYSTEM
          ↓
        CCRs
          ↓
  SERIES CIRCUITS
          ↓
ISOLATION TRANSFORMERS
          ↓
  AGL LIGHT FIXTURES

IoT-Enabled AGL Architecture

   AGL FIXTURES / CCRs
          ↓
       SENSORS
          ↓
EDGE DEVICE / GATEWAY
          ↓
       NETWORK
          ↓
IoT / MONITORING PLATFORM
     ↙          ↘
ANALYTICS      DASHBOARD
     ↓
MAINTENANCE DECISION

Visibility

EQUIPMENT
   ↓
  STATUS
   ↓
OPERATOR

EQUIPMENT
   ↓
 SENSORS
   ↓
   DATA
   ↓
 NETWORK
   ↓
ANALYTICS
   ↓
CONDITION
   ↓
MAINTENANCE / OPERATIONS

The fundamental change: IoT adds a continuous data layer around the physical AGL system.

LED Fixture Fault, Two Ways

FIXTURE #125
     ↓
ABNORMAL CURRENT
     ↓
REPEATED FAULT EVENTS
     ↓
TEMPERATURE TREND
INCREASING
     ↓
    ALERT
     ↓
MAINTENANCE
INVESTIGATION

The maintenance team can potentially act before complete fixture failure, depending on the monitoring capabilities and diagnostic algorithms.

IoT Does Not Automatically Mean "Smart Fixture"

An LED fixture can exist at several different levels of connectivity:

• LED but not connected
• LED + local diagnostics
• LED + digital monitoring
• LED + network connectivity
• LED + IoT platform + analytics

IoT and Smart AGL

TRADITIONAL AGL
      ↓
    LED AGL
      ↓
   SMART AGL
      ↓
CONNECTED / IoT-ENABLED AGL
      ↓
  DATA ANALYTICS
      ↓
CONDITION-BASED / PREDICTIVE
      MAINTENANCE

These terms can overlap, but they describe different levels of capability — moving from one level to the next isn't automatic.

What Each System Actually Reports

CCR = ON
CCR = FAULT
CIRCUIT = ON
CIRCUIT = FAULT

CCR STATUS
     +
OUTPUT CURRENT
     +
OUTPUT VOLTAGE
     +
TEMPERATURE
     +
POWER CONSUMPTION
     +
OPERATING HOURS
     +
FAULT HISTORY
     +
TREND ANALYSIS

This produces much more information for maintenance and operations. Note that a conventional AGL with an ALCMS already reports more than ON/FAULT, so treat the left column as the basic case.

Trend-Driven vs Calendar-Driven

SENSOR DATA
     ↓
NORMAL CONDITION
     ↓
GRADUAL DETERIORATION
     ↓
TREND DETECTED
     ↓
MAINTENANCE ALERT
     ↓
INSPECTION

CALENDAR
   ↓
MAINTENANCE INTERVAL
   ↓
INSPECT EVERYTHING

IoT data should support — not automatically replace — required scheduled inspections and formal tests.

One Step Further Than CBM

HISTORICAL DATA
      ↓
  CURRENT DATA
      ↓
TREND / ANALYTICS
      ↓
DETERIORATION PATTERN
      ↓
   FAILURE RISK
      ↓
MAINTENANCE PLANNING

Conventional vs IoT-Enabled CCR

CCR
 ↓
CURRENT CONTROL
 ↓
BASIC STATUS
 ↓
ALARM

CCR
 ↓
SENSORS / CONTROLLER
 ↓
CURRENT, VOLTAGE,
TEMPERATURE, POWER,
FAULTS, OPERATING
HOURS
 ↓
IoT GATEWAY
 ↓
MONITORING PLATFORM
 ↓
ANALYTICS

This can support both operational monitoring and maintenance analysis.

Granular Fault Localization

A conventional system may monitor only the CCR output. An IoT-enabled system can potentially collect information from multiple points along the circuit.

CCR
 ↓
SERIES CIRCUIT
 ↓
ISOLATION TRANSFORMERS
 ↓
FIXTURES
 ↓
SENSORS / SMART DEVICES

Instead of only knowing "circuit current abnormal," the system may help identify "abnormal condition associated with fixture/transformer location X."

The actual ability to localize a fault depends entirely on the sensor architecture in place. A conventional AGL with an ALCMS and individual lamp monitoring (common on CAT II/III circuits) can already report lamp-level status; the added value of IoT is broader data such as temperature, trends and asset history, plus analytics.

A Common Data Environment

                 A-SMGCS
                    ↕
           AGL CONTROL SYSTEM  (safety-critical control path)
                    ↕
   ┌────────────────┼────────────────┐
   ↓                ↓                ↓
  CCRs           FIXTURES          SIGNS
   │                │                │
   └── status / sensor data (monitoring copy, one-way) ──┘
                    ↓
             EDGE / GATEWAY
                    ↓
     IoT PLATFORM (monitoring + analytics)
                    ↓
    DASHBOARDS / MAINTENANCE SYSTEMS

The IoT platform can then provide a common data environment for AGL status, equipment health, alarms and maintenance information. The A-SMGCS link (for functions such as stop-bar or route-guidance control) stays on the AGL control system; the IoT platform normally receives a monitoring copy of status data through a controlled, preferably one-way, interface.

An Important Engineering Principle

   AGL
    ↓
   IoT
    ↓
   DATA
    ↓
DASHBOARD

       AGL
        ↕
IoT / CONTROL INTERFACE
        ↕
  CONTROL SYSTEM

For safety-critical airport lighting, automatic commands should be carefully segregated, authorized and validated.

The Cost of Connectivity

   AGL
    ↓
DEDICATED
CONTROL NETWORK

   AGL
    ↓
IoT DEVICES
    ↓
  GATEWAY
    ↓
  NETWORK
    ↓
  PLATFORM
    ↓
APPLICATIONS

Every additional connection introduces additional cybersecurity considerations, including:

• Device authentication
• Access control
• Network segmentation
• Encryption where appropriate
• Secure configuration
• Firmware management
• Logging
• Vulnerability management
• Controlled remote access
• Incident response

IoT provides connectivity, but connectivity must be engineered securely.

More Components, More Failure Points

  SENSOR
    ↓
  GATEWAY
    ↓
  NETWORK
    ↓
SERVER/PLATFORM
    ↓
APPLICATION

Any of these can fail. The AGL design should distinguish between the operational lighting function and the monitoring/data function.

   IoT FAILURE
        ↓
MONITORING UNAVAILABLE
        ↓
AGL REMAINS IN DEFINED
 SAFE OPERATING MODE

A monitoring failure should not cause loss of required AGL lighting. The exact behavior depends on the system safety and control philosophy.

What Gets Tested at the Factory

End-to-End Data Integrity

For IoT-enabled AGL, SAT should verify the complete chain:

PHYSICAL EQUIPMENT
       ↓
     SENSOR
       ↓
    GATEWAY
       ↓
    NETWORK
       ↓
  IoT PLATFORM
       ↓
   DATABASE
       ↓
   DASHBOARD
       ↓
   OPERATOR

Conventional vs IoT-Enabled in Practice

IoT does not eliminate physical inspections, photometry, alignment checks, or mandatory electrical tests.

The Complete IoT Data Chain

   SENSE
     ↓
  COLLECT
     ↓
 TRANSMIT
     ↓
   STORE
     ↓
  ANALYZE
     ↓
   ALERT
     ↓
   DECIDE
     ↓
  MAINTAIN
     ↓
  FEEDBACK

This is one of the biggest differences from conventional AGL, which has no equivalent continuous data lifecycle.

Where Each Approach Wins and Falls Short

How to Remember the Difference

    AGL
     ↓
  CONTROL
     ↓
PERIODIC INSPECTION
     ↓
  MAINTENANCE

    AGL
     ↓
   SENSE
     ↓
  CONNECT
     ↓
  ANALYZE
     ↓
   ALERT
     ↓
  MAINTAIN

Final Engineering Rule

Conventional AGL vs IoT-Enabled AGL

A monitoring failure should never be allowed to cause loss of required AGL lighting — the operational lighting function and the monitoring/data function must remain clearly separated in the design.

Engineering & Expert Notes

Frequently Asked Questions

Governing Documents

For an actual project design, always verify the current edition of the applicable documents.

Conventional and IoT-enabled AGL are not competing philosophies — IoT is a connectivity and intelligence layer added around the same fundamental safety-critical lighting system.

Continue Exploring