ALCMS & Control System Forms
The 25 forms that document the Airfield Lighting Control and Monitoring System (ALCMS) from installation through PLC/HMI configuration, communication and CCR interfacing, local/remote and intensity control, alarm/interlock/fail-safe testing, functional testing and SAT, all the way to maintenance, backup, configuration control, user access, alarm history, performance reporting and handover. Grouped into Installation & Configuration, Communication & Operational Control, Safety & Acceptance Testing, Maintenance & Configuration Control, and Access, Intelligence & Handover, this division is the master command-and-feedback traceability layer for the entire AGL system.
Where this fits — Division 16 gives every CCR and circuit its identity; this division is the digital layer that controls, monitors, alarms on and reports back through that identity. It integrates closely with Design & Engineering (Division 02), Testing (Division 06), Maintenance (Division 08), Failure Investigation (Division 09), QA/QC (Division 10), Asset Management (Division 11) and Safety & Permit (Division 13) — the Functional Test, CCR Interface Test and Alarm History are the records those divisions most often pull from.
A · Installation & Configuration
5 of 5 formsALC-01 ALCMS Installation Record Installation Record
Purpose
Documents the physical installation of the complete ALCMS hardware and associated control equipment — server, workstation, PLC, HMI, network gear and CCR interfaces — as a single as-built installation record for the control room.
Key Fields
- Airport / project / ALCMS system ID
- Installation location / control room
- Installation date and contractor
- Drawing / reference number
- Equipment mounting and panel installation
- Cable termination, power supply and earthing
- Network connections and communication interfaces
- Identification labels and environmental conditions
- Final status: Installed / Defective / Rectification Required
ALC-02 ALCMS Configuration Record Configuration Record
Purpose
Establishes the approved baseline configuration of the complete ALCMS — architecture, control stations, PLC/HMI setup, I/O allocation, CCR and circuit mapping, alarms and interlocks — as the single reference configuration for the system.
Key Fields
- System architecture and control stations
- PLC configuration and HMI configuration
- I/O allocation
- CCR mapping and circuit mapping
- Alarm configuration and interlock configuration
- Communication configuration
- Configuration file / drawing reference and revision
- Engineer, reviewer, approval
- Status: Approved Baseline Configuration
ALC-03 ALCMS Equipment Register Register
Purpose
Maintains the master inventory of every piece of ALCMS hardware — PLC, HMI, server, workstation, network switch, I/O modules, interface modules, communication equipment, UPS and control panels — with full lifecycle traceability.
Key Fields
- Equipment ID, type, manufacturer, model
- Serial number, part number
- Firmware / version and location
- Installation date
- Category (PLC / HMI / server / network / I/O / UPS / panel etc.)
- Warranty and maintenance history
- Failure history and replacement
- Configuration history
ALC-04 PLC Configuration Record Configuration Record
Purpose
Maintains controlled documentation of the PLC configuration — CPU, I/O modules, firmware, program version, digital/analog I/O mapping, CCR interface mapping, interlocks and control logic — under formal change authorization.
Key Fields
- PLC ID, manufacturer, model, CPU
- I/O modules and firmware
- Program version and configuration revision
- Digital and analog I/O, CCR interface mapping
- Interlocks, alarms and control logic
- Program backup and change authorization
- Version verification / validation reference
- Approval: Configuration Approved / Modification Required
ALC-05 HMI Configuration Record Configuration Record
Purpose
Documents the approved HMI configuration and operator interface — screen set, software version and revision — and verifies that every operator screen displays and controls correctly before it is released for use.
Key Fields
- HMI ID, manufacturer, model, software version
- Screen revision
- Screen set: overview, runway, taxiway, CCR, circuit status, intensity, alarm, equipment, maintenance
- Screen functionality and status indication
- Command functionality and alarm display
- Interlock indication and user access verification
B · Communication & Operational Control
6 of 6 formsALC-06 Communication Test Record Test Record
Purpose
Verifies communication between ALCMS components and connected equipment — PLC, HMI, server, CCR, remote workstations and interface equipment — confirming that commands transmit, status updates arrive and communication loss is detected.
Key Fields
- Communication links tested (PLC / HMI / server / CCR / remote workstation / interface)
- Communication established, data transmission and reception
- Status update and command transmission
- Response verification
- Communication loss detection
- Result: Pass / Fail
ALC-07 Network Test Record Test Record
Purpose
Documents testing of the ALCMS industrial communication network — switches, ports, devices and addressing — confirming connectivity, link status, communication stability, redundancy and fault indication.
Key Fields
- Network ID, switch ID, port, device
- IP / addressing reference and protocol
- Network connectivity and device visibility
- Link status and communication stability
- Redundancy (where applicable)
- Network fault indication
- Test result, equipment/software, date, technician
ALC-08 CCR Interface Test Test Record
Purpose
Verifies communication and control between the ALCMS and CCR equipment — status indication, ON/OFF and intensity commands, fault/alarm status and feedback confirmation — including detection of communication loss.
Key Fields
- CCR ID, circuit ID, interface ID, communication method
- CCR status indication
- ON/OFF command and intensity command
- Fault status and alarm status
- Feedback confirmation
- Communication loss indication
- Result: Pass / Fail
ALC-09 Remote Control Test Test Record
Purpose
Verifies authorized remote operation of AGL equipment through the ALCMS end-to-end — remote enable, circuit ON/OFF, intensity selection, status and alarm feedback — following the command-sent → response → feedback-received chain.
Key Fields
- Remote enable
- Circuit ON / circuit OFF
- Intensity selection
- Status feedback and alarm feedback
- Verification chain: command sent → equipment response → feedback received
- Final result: Pass / Fail
ALC-10 Local Control Test Test Record
Purpose
Verifies local/manual control of connected AGL equipment — local ON/OFF, intensity selection, status indication, local/remote selection and control priority — with correct command response and interlock operation.
Key Fields
- Local control availability
- Local ON/OFF and intensity selection
- Status indication
- Local / remote selection and control priority
- Command response and status feedback
- Correct interlock operation
ALC-11 Intensity Control Test Test Record
Purpose
Verifies correct control of AGL intensity levels through the ALCMS across every configured step — selected intensity level against expected and actual CCR output, confirmed through command, response, feedback and field lighting.
Key Fields
- CCR ID and circuit ID
- Selected intensity level
- Expected CCR output vs. actual CCR output
- Checks per configured step (Step 1, 2, 3…)
- Command, CCR response, feedback and field lighting response
- Result: Pass / Fail
C · Safety & Acceptance Testing
5 of 5 formsALC-12 Alarm Test Test Record
Purpose
Verifies that ALCMS alarms — CCR fault, circuit fault, communication failure, power failure, equipment failure, system fault and other configured alarms — are correctly generated, displayed, acknowledged and logged.
Key Fields
- Alarm types tested
- Test sequence: fault simulated → alarm generated → displayed → logged → acknowledged → reset
- Alarm text, timestamp, equipment reference
- Priority and operator acknowledgement
- Alarm history entry
ALC-13 Interlock Test Test Record
Purpose
Verifies that configured interlocks correctly prevent unsafe or unauthorized control actions — command attempted against interlock condition, expected vs. actual response, and correct reset/recovery.
Key Fields
- Interlock condition and command attempted
- Expected response vs. actual response
- Alarm / status indication
- Interlock operates and inhibited command rejected
- Correct indication displayed
- Reset / recovery verified
- Result: Pass / Fail
ALC-14 Fail-Safe Test Test Record
Purpose
Verifies that the ALCMS behaves correctly under defined abnormal or failure conditions — communication loss, PLC/HMI failure, power interruption, network failure or control system failure — reaching a defined safe state.
Key Fields
- Test conditions: comms loss, PLC/HMI failure, power interruption, network/equipment/control failure
- Defined safe state reached
- Alarm generation and operator indication
- Recovery behaviour
- Manual / local control availability (where applicable)
- Final status: Fail-Safe Verified / Rectification Required
ALC-15 ALCMS Functional Test Test Record
Purpose
Verifies complete end-to-end ALCMS functionality across startup, device status, CCR/circuit/intensity control, local/remote operation, alarm handling, interlocks, communication, status feedback, event logging and user access.
Key Fields
- Functional areas: startup, device status, CCR control, circuit control, intensity control
- Local / remote operation and status feedback
- Alarm handling and interlocks
- Communication and event logging
- User access
- End-to-end chain: operator command → ALCMS → PLC → interface → CCR → AGL circuit → status feedback → HMI
- Result: Functional / Non-Functional
ALC-16 ALCMS SAT Report Acceptance Report
Purpose
Provides the formal Site Acceptance Test record for the ALCMS, covering hardware, software, control, monitoring, safety and documentation as a single consolidated acceptance decision.
Key Fields
- Hardware: PLC, HMI, server/workstation, network, interface panels
- Software: application version, PLC program, HMI configuration, database
- Control: local, remote, CCR, intensity
- Monitoring: status, alarms, events, feedback
- Safety: interlocks, fail-safe, communication-loss response
- Documentation: as-built drawings, configuration files, backup, manuals, test records
- SAT status: Passed / Passed with Comments / Failed
D · Maintenance & Configuration Control
5 of 5 formsALC-17 ALCMS Maintenance Record Maintenance Record
Purpose
Documents preventive and corrective maintenance of the ALCMS — PLC, HMI, server/workstation, network equipment, panels, communication equipment, UPS, backup verification and software/configuration review.
Key Fields
- Work order, date, technician
- Activity performed (PLC / HMI / server / network / panel / UPS inspection)
- Backup verification and software/configuration review
- Findings and corrective action
- Test result
ALC-18 ALCMS Fault Report Fault Report
Purpose
Records faults affecting ALCMS operation — PLC, HMI, network, communication, CCR interface, software, hardware, power supply or configuration faults — through diagnosis, root cause and restoration.
Key Fields
- Fault ID, date/time, equipment, system condition
- Symptoms and alarm generated
- Fault category (PLC / HMI / network / comms / CCR interface / software / hardware / power / configuration)
- Diagnostic results and root cause
- Corrective action, retest and restoration
ALC-19 ALCMS Backup Record Backup Record
Purpose
Provides traceability of ALCMS backups — PLC program, HMI configuration, database, software/application and network configuration — confirming each backup is complete, readable and, where applicable, restore-tested.
Key Fields
- Backup date and system
- PLC program / HMI configuration / database / software / network configuration backed up
- Backup location / reference
- Backup completed and file readable
- Version recorded and restore test (where applicable)
- Backup custodian
- Status: Valid / Invalid / Replacement Required
ALC-20 Configuration Change Record Change Record
Purpose
Controls every authorized change to ALCMS configuration — existing configuration, proposed change and reason — through technical review, risk assessment, authorization, implementation and closure.
Key Fields
- Change ID, date, system, equipment
- Existing configuration and proposed change, with reason
- Change request, technical review, risk assessment, authorization
- Implementation date, engineer, configuration revision
- Backup completed and testing completed
- Closure: change validated, documentation updated, previous version archived
ALC-21 Software Version Register Register
Purpose
Establishes the master software and firmware version history for the ALCMS — application, manufacturer, version, release/installation dates and approved version — with full upgrade traceability.
Key Fields
- Software ID, application, manufacturer
- Version and release date
- Installation date and system/equipment
- License / reference and approved version
- Previous version, current version, upgrade date
- Reason, change reference and test reference
E · Access, Intelligence & Handover
4 of 4 formsALC-22 User Access Register Register
Purpose
Maintains controlled records of authorized ALCMS users — access level, authorization and periodic review — so every operator, supervisor, engineer, administrator and maintenance login is accounted for.
Key Fields
- User ID and name / role
- Access level (operator / supervisor / engineer / administrator / maintenance)
- Authorization and date granted
- Date reviewed and date revoked
- Password / access control and periodic review
- Account status
ALC-23 Alarm History Historical Log
Purpose
Maintains the historical record of ALCMS alarms and events — equipment, circuit, alarm type, priority and operator response — as the primary input to reliability intelligence and nuisance-alarm analysis.
Key Fields
- Alarm ID, date/time, equipment, circuit
- Alarm type, priority, description
- Acknowledged by, acknowledgement time
- Action taken, reset time, closure status
- Intelligence: repeated alarms, alarm frequency, alarm duration, unresolved alarms, alarm trends
ALC-24 ALCMS Performance Report Performance Report
Purpose
Assesses long-term ALCMS operational performance — system and communication availability, PLC/HMI uptime, network reliability, alarm frequency, CCR interface failures and mean time to repair — over a defined reporting period.
Key Fields
- System availability and communication availability
- PLC uptime and HMI availability
- Network reliability
- Alarm frequency and communication failures
- CCR interface failures and control failures
- Mean time to repair and repeated faults
- Reporting period (daily / weekly / monthly / quarterly / annual)
- Assessment: Normal / Degraded / Requires Investigation
ALC-25 ALCMS Handover Certificate Certificate
Purpose
Formally transfers the completed ALCMS system to operations and maintenance — hardware, software, functional performance and documentation — as the final controlled gate before the system is accepted into service.
Key Fields
- Hardware: equipment installed, tested, identification complete
- Software: approved versions, PLC program, HMI configuration, backup completed
- Functional: local/remote control, CCR interface, intensity control, alarm, interlock, fail-safe, communication
- Documentation: as-built drawings, configuration records, SAT report, test reports, manuals, backup records, software version register, user access register, warranty
- Handover status: Handed Over / Handed Over with Open Items / Not Accepted
- Signatures: contractor, ALCMS engineer, QA/QC, airport engineering, operations
How Division 19 Connects
These 25 forms are the ALCMS's command-and-feedback paper trail — from the day the control system is installed to the day it is formally handed over, and every alarm, fault and change in between.
Control & Feedback Path
Every control action and status update should be traceable in both directions:
Verified through ALC-08 CCR Interface Test, ALC-09 Remote Control Test, ALC-10 Local Control Test, ALC-11 Intensity Control Test, ALC-12 Alarm Test and ALC-15 Functional Test.
Related Divisions
- Division 02 — Design & Engineering (approved control architecture and I/O design)
- Division 06 — Testing (functional and SAT evidence feeding ALC-15 / ALC-16)
- Division 08 — Maintenance (preventive/corrective work feeding ALC-17)
- Division 09 — Troubleshooting & Failure Investigation (root-cause detail behind ALC-18)
- Division 10 — QA/QC and Division 11 — Asset Management (lifecycle and asset health)
- Division 13 — Safety & Permit and Division 16 — Cable, Connector & Circuit Records (CCR/circuit identity behind every ALC-08 test)
Frequently Asked Questions
Quick answers about the 25 Division 19 ALCMS & Control System forms, how they are grouped, and how they connect to the rest of the library.
Q1What is Division 19 — ALCMS & Control System Forms in the AGL Engineering Forms & Templates library?
Division 19 is a set of 25 alcms & control system forms (ALC-01 to ALC-25) in the AGL Engineering Forms & Templates library. It documents the Airfield Lighting Control and Monitoring System (ALCMS) from installation through PLC and HMI configuration, communication and CCR interfacing, control, alarm, interlock and fail-safe testing, and functional testing and SAT, through to maintenance, backup, configuration control and handover. The forms are grouped into 5 categories: Installation & Configuration, Communication & Operational Control, Safety & Acceptance Testing, Maintenance & Configuration Control and Access, Intelligence & Handover.
Q2Which forms are included in Installation & Configuration and Communication & Operational Control?
Installation & Configuration (5 forms): ALC-01 ALCMS Installation Record, ALC-02 ALCMS Configuration Record, ALC-03 ALCMS Equipment Register, ALC-04 PLC Configuration Record, ALC-05 HMI Configuration Record; Communication & Operational Control (6 forms): ALC-06 Communication Test Record, ALC-07 Network Test Record, ALC-08 CCR Interface Test, ALC-09 Remote Control Test, ALC-10 Local Control Test, ALC-11 Intensity Control Test.
Q3Which forms are included in Safety & Acceptance Testing and Maintenance & Configuration Control?
Safety & Acceptance Testing (5 forms): ALC-12 Alarm Test, ALC-13 Interlock Test, ALC-14 Fail-Safe Test, ALC-15 ALCMS Functional Test, ALC-16 ALCMS SAT Report; Maintenance & Configuration Control (5 forms): ALC-17 ALCMS Maintenance Record, ALC-18 ALCMS Fault Report, ALC-19 ALCMS Backup Record, ALC-20 Configuration Change Record, ALC-21 Software Version Register.
Q4Which forms are included in Access, Intelligence & Handover?
Access, Intelligence & Handover (4 forms): ALC-22 User Access Register, ALC-23 Alarm History, ALC-24 ALCMS Performance Report, ALC-25 ALCMS Handover Certificate.
Q5What is the difference between the communication, network, CCR interface, remote, local and intensity control tests?
The Communication Test Record (ALC-06) verifies communication between ALCMS components and connected equipment, and the Network Test Record (ALC-07) tests the industrial communication network. The CCR Interface Test (ALC-08) verifies communication and control with the CCRs. The Remote Control Test (ALC-09) verifies authorized remote operation, the Local Control Test (ALC-10) verifies local or manual control, and the Intensity Control Test (ALC-11) verifies control of intensity levels across every configured step.
Q6What do the Alarm, Interlock and Fail-Safe tests verify?
The Alarm Test (ALC-12) verifies that ALCMS alarms are correctly generated, displayed, acknowledged and logged, and the Interlock Test (ALC-13) verifies that configured interlocks prevent unsafe or unauthorized control actions. The Fail-Safe Test (ALC-14) verifies behavior under defined abnormal or failure conditions. The ALCMS Functional Test (ALC-15) and ALCMS SAT Report (ALC-16) then cover end-to-end functionality and formal Site Acceptance.
Q7Which forms control ALCMS configuration, software and access?
The ALCMS Configuration Record (ALC-02), PLC Configuration Record (ALC-04) and HMI Configuration Record (ALC-05) establish the approved baselines. The Configuration Change Record (ALC-20) controls every authorized change, the Software Version Register (ALC-21) holds software and firmware version history, and the ALCMS Backup Record (ALC-19) gives traceability of backups. The User Access Register (ALC-22) controls authorized users and their access levels.
Q8Can the forms in Division 19 be downloaded and filled in?
Yes. Each form has a Download as Word button that produces an uncontrolled sample Word template with letterhead, a document-control block, ruled entry fields and a three-tier approval table, ready to print or fill on-screen. The forms can also be searched by keyword or form ID.
Q9How does Division 19 connect to the CCR and circuit records?
Division 16 gives every CCR and circuit its identity, and this division is the digital layer that controls, monitors, alarms on and reports back through that identity. It also connects with design and engineering, testing, maintenance and failure investigation, and every control action and status update should be traceable in both directions.
MONITOR THE SYSTEM. UNDERSTAND THE LOGIC.
An ALCMS form records alarms and status changes — but real control-system competence means understanding CCR communication protocols, monitoring logic and how to read a fault before it becomes an outage.
Take your knowledge further with Precision AGL Academy.
Build Complete AGL Project Capability
Learn how technical AGL work connects with:
Develop the knowledge to not only record the work, but understand the engineering and project-management principles behind it.
Plan the project. Understand the engineering. Deliver with confidence.
Follow the Academy
Important Notice, Disclaimer & Limitation of Liability
Please read before relying on any content on this page or on any template downloaded from it.
- Purpose and intended users. This page is an independent educational and informational reference for competent, suitably trained and authorised airfield ground lighting (AGL), aerodrome electrical and project personnel. It is not professional engineering, legal or regulatory advice, and using it does not create any professional or client relationship.
- Sample templates, not controlled documents. Forms, checklists, registers, reports, certificate layouts and Word downloads are generic samples. They are uncontrolled copies and are not approved work instructions, procedures, permits, certificates, test or calibration records, or regulatory records. Letterheads, form numbers, revision labels, dates, document-control blocks and approval tables are layout only. Review and adapt a template under your own document-control system before any use; signatures on it carry no authority unless made under your own approved system. Precision AGL Academy does not issue, approve, certify or take responsibility for any record completed using a template, and does not receive or store such records.
- Safety. Work on series circuits, constant current regulators (CCRs), isolating transformers, cables, connectors and control equipment can be fatal. Always apply the aerodrome’s permit-to-work and isolation/LOTO procedures, prove dead, use correctly rated instruments and PPE, and follow the manufacturer’s instructions. Nothing here authorises work on live equipment or the bypassing of any safety device or interlock.
- Certificates, approvals and compliance. A completed template is not a certificate, approval, acceptance, release, permit or evidence of compliance, and listing a certificate, approval or sign-off field does not make the document valid. Reading this material or completing a template confers no certification, accreditation, competency assessment or authorisation to work on any aerodrome.
- Aviation operations. Nothing here authorises return to service, a change of operating category (CAT I/II/III), a NOTAM, a flight-inspection outcome or any aerodrome certification decision. These rest with the aerodrome operator, the air navigation service provider and the competent regulator.
- Standards, regulations and contracts. References to ICAO, FAA, IEC, IEEE, ISO, BIS, DGCA and other standards are for orientation only. They are summarised, may be incomplete or out of date, and standards are revised from time to time. Consult the current official editions. Following this content does not guarantee compliance with any law, standard, contract or regulatory approval. Contract, specification and official requirements always prevail, and nothing here is a contract document or legal advice.
- Personal and confidential data. Some templates have fields for names, signatures, training or competency records, and incident or injury details. If you record personal or confidential information on a template, you are responsible for handling it lawfully, including under India’s Digital Personal Data Protection Act, 2023 and your contracts. Word files are generated in your browser; the content you enter is not sent to us.
- Generic content; no warranty. Field lists, sequences, categories and example values are generic and indicative; real projects, installations and contracts differ. Content is provided “as is” and “as available”, without warranty of any kind, express or implied, including accuracy, completeness, currency or fitness for a particular purpose.
- Limitation of liability. To the fullest extent permitted by applicable law, Precision AGL Academy and its owners, authors and contributors are not liable for any injury, death, loss, damage, downtime, penalty, contractual dispute or regulatory consequence, whether direct or indirect, arising from the use of, reliance on, or inability to use this content or any template downloaded from it. Nothing in this notice excludes or limits any liability that cannot lawfully be excluded or limited.
- Independence and trademarks. This is an independent publication, not affiliated with or endorsed by ICAO, the FAA, the IEC, BIS, DGCA, any airport, regulator, certification body or equipment manufacturer. Third-party names, standard designations and trademarks, including Microsoft Word and Excel, belong to their respective owners and are used for identification only.
- Copyright and use. © 2026 Precision AGL Academy. All rights reserved. You may view this page and use downloaded templates for personal reference, internal training and, once adapted under your own document-control system, your own internal project records, keeping this notice attached to unadapted copies. You may not present them as approved or controlled documents, or copy, republish, redistribute, scrape or commercially use the library without our prior written permission.
- Corrections. Content is reviewed periodically, with no obligation to update. To report an error, safety concern or rights issue, write to precisionaglsolutions@gmail.com.