STANDALONE SYSTEM VS INTEGRATED A-SMGCS
A standalone AGL system operates and controls airfield lighting independently, while an A-SMGCS-integrated system exchanges status, control and/or operational information with the Advanced Surface Movement Guidance and Control System (A-SMGCS). One is self-contained; the other is a defined system interface — and integration should be treated as engineering, not just "remote control of lights."
Basic Comparison
| Aspect | Standalone AGL System | Integrated A-SMGCS Interface |
|---|---|---|
| AGL operation | Independent | Integrated with A-SMGCS |
| Local AGL control | ✔ | ✔ |
| Central AGL control | Possible | ✔ |
| A-SMGCS communication | — | ✔ |
| Lighting status to A-SMGCS | Usually unavailable | ✔ |
| Commands from A-SMGCS | — | Possible, if designed |
| Automatic lighting response | Limited to AGL logic | Can be coordinated with surface-movement logic |
| Fault information | Local/AGL system | Can be shared with A-SMGCS |
| Traffic-dependent control | Limited | Possible |
| Taxi routing integration | No | Possible |
| Data exchange | Limited | ✔ |
| Network dependency | Lower | Higher |
| Integration complexity | Low | High |
| Cybersecurity requirements | Lower | Higher |
| Commissioning effort | Lower | Higher |
| Operational visibility | AGL-focused | Integrated surface-movement view |
Standalone AGL
A standalone system essentially looks like this — the AGL system controls its own equipment and does not need A-SMGCS to perform its fundamental lighting function.
AGL CONTROL SYSTEM
↓
CCRs
↓
Series Circuits
↓
Runway / Taxiway Lights
Example: operator selects Taxiway lighting → AGL controller operates the appropriate CCR/circuit.
A-SMGCS-Integrated AGL
An integrated architecture adds an interface between the AGL system and A-SMGCS, allowing the two systems to exchange relevant information.
A-SMGCS
↕
A-SMGCS / AGL Interface
↕
AGL Control System
↓
CCRs
↓
AGL Circuits
↓
Runway / Taxiway Lights
What Is A-SMGCS?
A-SMGCS is an airport surface-management system intended to support the safe and efficient movement of aircraft and vehicles on the aerodrome surface. It can involve surveillance, routing, guidance, control, situational awareness, and traffic management. AGL can become one of the systems that provides visual guidance information to support surface movement.
Why Integrate AGL with A-SMGCS?
The main reason is to make lighting behaviour more closely coordinated with actual surface operations.
Aircraft requires taxi route
↓
A-SMGCS determines route
↓
Relevant taxiway guidance
↓
AGL system receives command
↓
Appropriate lights/signs operate
This can provide a more dynamic lighting environment than a purely standalone system.
Standalone vs Integrated in Practice
Standalone Example
Suppose Taxiway A has a lighting circuit. The operator manually selects "Taxiway A — ON" and the AGL system operates the associated circuit. A-SMGCS isn't involved.
Operator ↓ AGL Control ↓ CCR ↓ Taxiway A Lights
Integrated Example
Suppose A-SMGCS determines that an aircraft should use a particular taxi route. The exact operational logic depends on the airport's system design and approved procedures.
Aircraft movement
↓
A-SMGCS
↓
Routing / guidance decision
↓
AGL Interface
↓
Lighting command
↓
Taxiway lights / signs
Information Can Flow in Both Directions
AGL → A-SMGCS
The AGL system may provide lighting status, CCR status, circuit status, equipment alarms, availability, and fault information.
AGL ↓ Status / alarm ↓ A-SMGCS
A-SMGCS → AGL
A-SMGCS may provide lighting configuration, routing-related commands, guidance requirements, and selected taxi route information.
A-SMGCS ↓ Operational command ↓ AGL ↓ Lighting configuration
The exact information and command set must be defined by the interface specification.
The Interface Does Not Mean Direct Lamp Control
A common misconception is that A-SMGCS controls each individual lamp directly. Usually the architecture is more structured — A-SMGCS communicates at a system/control level, while the AGL system manages the detailed lighting equipment.
A-SMGCS
↓
Interface
↓
AGL Control System
↓
CCR / Switching / Control Equipment
↓
AGL Circuit
↓
Fixtures
Where Smart AGL Fits In
Standalone Conventional AGL
Conventional AGL
↓
Local / central control
↓
Manual monitoring
Smart AGL
Smart AGL
↓
Digital control
↓
Remote monitoring
↓
Diagnostics
A-SMGCS
↕
Digital Interface
↕
Smart AGL
↓
Smart CCR
↓
AGL Circuits
↓
Fixtures
Smart AGL + A-SMGCS is a much more integrated architecture than either alone.
Standalone vs Integrated Monitoring
Standalone
The AGL operator sees status directly, and this information primarily belongs to the AGL control system.
CCR-01 = ON CCR-02 = ON CCR-03 = FAULT
Integrated
Relevant information may be made available to A-SMGCS, improving overall operational awareness.
A-SMGCS ↓ AGL availability AGL status Lighting configuration Relevant alarms
How Faults Propagate
Standalone
AGL fault ↓ AGL control system ↓ Maintenance/operator
Integrated
AGL fault ↓ AGL control system ↓ Interface ↓ A-SMGCS ↓ Operational awareness
The A-SMGCS can therefore take relevant lighting availability into account, depending on the implemented system.
Fail-Safe Consideration
Suppose communication between A-SMGCS and AGL is lost. The system must have a defined behaviour.
A-SMGCS X X Communication lost X AGL ↓ Defined fallback state
Possible design principles include:
- Maintain current safe state
- Return to predefined configuration
- Transfer to local control
- Generate alarm
- Prevent unauthorized automatic commands
The exact response must be specified and validated for the particular airport system.
Local Control Should Remain Important
An integrated A-SMGCS interface should not mean "if the network fails, the airport loses all lighting control." A robust architecture normally defines operational priorities and fallback modes.
A-SMGCS
↓
Automatic / integrated control
↕
AGL Control System
↓
Local / manual control
↓
AGL equipment
The actual control hierarchy must be defined in the system requirements.
The Interface Is Not a Single Fixed Protocol
The interface can involve digital communication, Ethernet/IP, serial communication, hardwired I/O, PLC/RTU, middleware/gateway, or proprietary interfaces.
"A-SMGCS interface" does not define a specific communication protocol by itself. The project specification needs to define the actual interface.
What Changes in Factory Acceptance Testing
Standalone AGL FAT
- CCR operation
- Intensity steps
- Circuit control
- Alarms
- Local/remote control
- Monitoring
- Electrical performance
A-SMGCS-Integrated FAT Adds
- Interface communication
- Data mapping
- Commands and status feedback
- Alarm transmission
- Interlocks
- Communication failure and recovery
- Control priority and invalid command handling
AGL FAT ↓ Equipment + control verification Integrated FAT ↓ AGL verification + A-SMGCS interface verification + End-to-end functional verification
What Changes in Site Acceptance Testing
Standalone AGL
AGL installation ↓ Electrical tests ↓ Functional tests ↓ Photometry/alignment ↓ Commissioning
A-SMGCS Integration
AGL installation ↓ Electrical tests ↓ AGL functional tests ↓ A-SMGCS interface ↓ Command verification ↓ Status verification ↓ Alarm verification ↓ Communication-loss test ↓ End-to-end operational test ↓ Commissioning
Integration Widens the Attack Surface
A standalone system has fewer external digital connections. An integrated A-SMGCS system introduces additional interfaces.
A-SMGCS ↕ Network ↕ AGL
The integrated system requires attention to:
- Network security and access control
- Authentication and segmentation
- Configuration management and logging
- Remote-access controls
- Failure/recovery procedures
The exact cybersecurity requirements depend on the airport's IT/OT architecture and applicable policies.
Coordination Is the Point
A-SMGCS → Traffic information AGL → Lighting information
A-SMGCS
↓
Traffic + Routing
↕
AGL
↓
Lighting Guidance
This creates a more coherent surface-movement system.
Integration Adds Complexity
| Benefit | Trade-off |
|---|---|
| Better coordination | More complex architecture |
| Centralized information | Network dependency |
| Automated operation | More complex control logic |
| Better situational awareness | Interface engineering |
| Faster status sharing | Cybersecurity requirements |
| Potentially reduced workload | More extensive FAT/SAT |
Integration should be justified by operational requirements, not simply because it is technologically possible.
How to Remember the Difference
"AGL controls AGL."
AGL Control
↓
CCR
↓
Lights
"A-SMGCS and AGL exchange
operational information."
A-SMGCS
↕
Interface
↕
AGL Control
↓
CCR
↓
Lights
Standalone System vs Integrated A-SMGCS Interface
A standalone AGL system operates independently, whereas an A-SMGCS-integrated AGL system exchanges defined control, status and operational information with the airport's surface-movement management system.
The key engineering point is that A-SMGCS integration should be treated as a defined system interface — not simply as "remote control of lights." The interface requirements should explicitly define data exchanged, commands, priorities, interlocks, failure behaviour, communication loss, cybersecurity, and FAT/SAT acceptance criteria.
The exact architecture, protocol, and fallback behaviour must always come from the airport's approved system design and interface specification — not a generic diagram.
Engineering & Expert Notes
Treat Cybersecurity as a Design Item
SecurityInterfaces extend exposure. Plan segmentation and access control.
Test the Interface in Both Directions
IntegrationVerify status and command exchange.
Check Standalone Fallback
FallbackMake sure lighting works if the interface fails.
Record Interface Specifications and Changes
RecordsControl versions.
Frequently Asked Questions
A standalone system operates and controls airfield lighting independently. An integrated system additionally exchanges status, control and/or operational information with A-SMGCS through a defined interface.
Usually not. A-SMGCS generally communicates at a system/control level with the AGL control system, which then manages the detailed lighting equipment such as CCRs and circuits.
The system must have a defined fallback behaviour — such as maintaining the current safe state, returning to a predefined configuration, transferring to local control, or raising an alarm. The exact response must be specified and validated for the particular airport system.
No. The interface can be implemented through digital communication, Ethernet/IP, serial communication, hardwired I/O, PLC/RTU, middleware/gateway, or proprietary means. The project specification defines the actual interface.
Yes. An integrated system introduces additional network interfaces and therefore requires attention to network security, access control, authentication, segmentation, configuration management, logging, and remote-access controls.
Not necessarily. Integration adds architectural, network and cybersecurity complexity, plus more extensive FAT/SAT. It should be justified by actual operational requirements rather than pursued simply because it's technologically possible.
Governing Documents
For an actual project, always verify the current edition of the applicable documents and the approved interface specification.
ICAO Doc 9830 (A-SMGCS Manual)
ICAO guidance on Advanced Surface Movement Guidance and Control System functions, architecture and implementation levels.
ICAO Annex 14 / FAA AC 150/5340-30
Underlying AGL design and installation requirements that any A-SMGCS interface must still comply with at the lighting-system level.
Applicable IT/OT Cybersecurity Policy
Airport or national cybersecurity requirements governing network segmentation, access control and remote access for integrated systems.
Final Engineering Note
Do not assume a generic architecture diagram defines the actual interface. The data exchanged, commands, priorities, interlocks, and fail-safe behaviour must always be defined in the approved project interface specification.
A standalone system and an A-SMGCS-integrated system are not simply "basic vs advanced" — they represent different architectural decisions with different testing, cybersecurity and fail-safe obligations.
Compare the Systems. Then Learn How to Engineer Them.
Understanding the difference between AGL systems is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.
Build Practical AGL Engineering Skills
Go deeper with structured training from Precision AGL Academy, covering:
Learn how AGL systems work as part of a complete airport lighting system, not just as individual components or configurations.