AC 150/5345-56 Specification for L-890 Airport Lighting Control and Monitoring System (ALCMS)
Specifies minimum requirements for an Airport Lighting Control and Monitoring System (ALCMS), which simplifies the control and monitoring of lighted visual aids and enhances airport safety.
This document is cancelled. It may have been replaced. Check the official source before relying on it.
U.S. Department of Transportation Federal Aviation Administration
Subject: SPECIFICATION FOR L-890 AIRPORT LIGHTING CONTROL AND MONITORING SYSTEM (ALCMS)
Date: 09/30/04 Initiated by: AAS-100 Change:
AC No.: 150/5345-56
1. PURPOSE. This advisory circular (AC) specifies minimum requirements for an Airport Lighting Control and Monitoring System (ALCMS). The ALCMS simplifies the control and monitoring of lighted visual aids and enhances airport safety. The basic function of the system remains the same whether for a general aviation airport that supports only a few operations in a day or a large commercial airport which caters to hundreds of operations on any given day. 2. EFFECTIVE DATE. Effective six months after the issue date of the AC, only that equipment qualified in accordance with the specification herein will be listed in accordance with AC 150/5345-53, Airport Lighting Equipment Certification Program. Airports that have previously installed an Airport Lighting Control and Monitoring System (ALCMS) will not be required to install a new system after the effective date of the AC. 3. APPLICATION. The standards contained in this AC are recommended by the Federal Aviation Administration (FAA) in all applications involving airport development of this nature.
Subject: SPECIFICATION FOR L-890 AIRPORT LIGHTING CONTROL AND MONITORING SYSTEM (ALCMS)
For airport projects receiving federal funds under the airport grant assistance program, the use of the standards in this AC are mandatory. 4. BACKGROUND. Many airports are requesting to install computerized touchscreen controls for airport lighting systems. The current specification for lighting control panel described in Advisory Circular (AC) 150/5345-3, Specification for L-821, Panels for Control of Airport Lighting, does not include specifications for this technology. However, under the Federal Aviation Administration’s (FAA) modification of standards provisions, computerized touchscreen control panels have been installed at some airports and have proven to meet the functional requirements for lighting control panels as specified in AC 150/5345-3 and other related AC’s. 5. METRICS. To promote an orderly transition to metric units, this advisory circular includes both English and metric dimensions. The metric conversion may not be exact equivalents, and until there is an official changeover to the metric system, the English dimensions will govern.
ii
6. COPIES OF THIS AC. The Office of Airport Safety and Standards is in the process of making ACs available to the public through the Internet. These ACs may be found through the Federal Aviation Administration (FAA) home page (www.faa.gov). To get to the AC area, on the home page: (select) Airports & Air Traffic: (select) Information for: Airport Operators: (select) Topic Index: Advisory Circulars. A printed copy of this and other ACs can be ordered from the U.S. Department of Transportation, Subsequent Business Office, Annmore East Business Center, 3341 Q 75th Avenue, Landover, Maryland, 20785. ACs may also be ordered through the AC Checklist, which can also be accessed through the FAA home page. To access the AC Checklist from the FAA home page, select "Site Map," “FAA Organizations," "Headquarters Offices," “Financial Services (ABA),” “Advisory Circulars,” then "Advisory Circular Checklist."
David L. Bennett Director of Airport Safety and Standards
iii
Table of Contents
Paragraph Page 1. Scope and Classification … 1 1.1 Scope … 1 1.2 Equipment Classifications … 1 1.3 Definition of Terms … 2 2. Reference Documents … 2 2.1 FAA Advisory Circulars … 2 2.2 FAA Orders … 3 2.3 Military Standards … 3 2.4 National Electric Code (NEC) … 3 3. ALCMS General System Requirements … 4 3.1 ALCMS Overview … 4 3.2 ALCMS Components … 5 4. Design Requirements … 7 4.1 Environmental Requirements … 7 4.2 Electrical Requirements … 7 4.3 Hardware Requirements … 7 4.4 Communication requirements … 9 4.5 Software Version Control … 9 4.6 Hardware Design Version Control … 9 4.7 Human Machine Interface (HMI) Graphics Requirements … 10 5. Control Design Requirements … 10 5.1 General Requirements … 10 5.2 Control Interfaces … 10 5.3 Control Soft Start Requirements … 11 5.4 Pre-programmed Control Buttons … 11 6. Monitoring Requirements … 12 6.1 Type A – Control Only … 12 6.2 Type B – Basic Monitoring … 12 6.3 Type C – Advanced Monitoring … 13 6.4 Type D – SMGCS Ready: Individual Lamps Out Monitoring … 14 7. Failsafe Design Requirements … 14 7.1 Failsafe Types … 15 7.2 Event Message Classification … 15 7.3 Audible Alarm … 16 7.4 Event Message Handling … 17 7.5 Security Administration … 17 7.6 Standard Reporting … 17 7.7 System Software Recovery … 18 8. Special Interface Design Requirements … 18 8.1 Constant Current Regulator Control … 18 8.2 Runway Visual Range (RVR) … 20 8.3 Approach Lighting … 21 8.4 General ON/OFF Contactor control and monitoring … 23 8.5 Generator and Automatic Transfer Switches (ATS) … 24 8.6 Rotating Beacon … 25 9. Manufacturer Support … 25 9.1 Warranty … 25
iv
9.2 Training … 25 9.3 Technical Support … 26 9.4 Documentation … 26 9.5 System Testing … 27 9.6 Spare Parts … 27 10. Qualification Requirements … 28 10.1 Qualification Procedures … 28 10.2 ALCMS Test System - Hardware Design Requirements … 28 10.3 ALCMS Test System – Touchscreen GUI Design Requirements … 32 10.4 Qualification Tests … 37 10.5 Operational Certification Test … 38 10.6 Level 1: ALCMS Certification Test … 38 10.7 Level 2: ALCMS Certification Test … 42 10.8 Level 3: ALCMS Certification Test … 42 10.9 Level 4: ALCMS Certification Test … 45
Appendices Appendix 1: Communications Application Notes … 53 Appendix 2: Fiber Optic Budget Worksheet … 56 Appendix 3: Touchscreen Technology Review … 57 Appendix 4: Touchscreen Installation Application Note … 61 Appendix 5: Radio Control (L-854) Interface Application Notes … 62 Appendix 6: Airport Lighting Preset Controls … 63 Appendix 7: Event Classification and Filtering … 64 Appendix 8: Design Application Notes … 65 Appendix 9: Generator and ATS Interface Application Notes … 66 Appendix 10: Beacon Control and Monitoring Application Notes … 67
v
List of Figures Figure 1: ALCMS Interface Overview … 4 Figure 2: ALCMS Components Overview … 5 Figure 3: Control Methodology Overview … 11 Figure 4: RVR Interface Diagram … 20 Figure 5: ALSF Interface Diagram … 21 Figure 6: Contactor Interface Diagram … 23 Figure 7: ALCMS Test System Hardware Design … 29 Figure 8: ALCMS Test System Touchscreen GUI: Preset Page … 32 Figure 9: ALCMS Test System Touchscreen GUI: RWY/TWY Page … 35 Figure 10: ALCMS Test System Touchscreen GUI: Utility Page … 36 Figure 11: SMGCS Test System … 46 Figure 12: Stopbar Control Page … 47 Figure 13: Touchscreen Installation … 61 Figure 14: Radio Control and Photocell interface examples … 62 Figure 15: Beacon Installation Example … 67
List of Tables Table 1: ALCMS Classification Types … 1 Table 2: CCR Control and Monitoring Index … 18 Table 3: ALSF / SSALR Interface Criteria … 21 Table 4: MALSR / MALSF Interface Criteria … 22 Table 5: REIL, ODALS, PAPI, and VASI Interface Criteria … 22 Table 6: Generator Control Interface Criteria … 24 Table 7: Generator Monitoring Interface Criteria … 24 Table 8: Greater than 5 miles Visibility … 33 Table 9: 3 to 5 miles Visibility … 33 Table 10: 2 to 3 miles Visibility … 34 Table 11: 1 to 2 miles Visibility … 34 Table 12: Less than 1 mile Visibility … 34 Table 13: Runway/Taxiway Page Control Methodology … 35 Table 14: Utility Page Control Methodology … 36 Table 15: Common Button and Indicator Functions … 37 Table 16: ALCMS Certification Tests … 38 Table 17: Less 1200 RVR Visibility … 48 Table 18: Fiber Optic Budget Calculator Worksheet … 56 Table 19: Fiber Optic Budget Worksheet Sample … 56 Table 20: Touchscreen Technology Comparison … 60 Table 21: L-854 Radio Control Airport Lighting Presets … 62 Table 22: Brightness Steps for 5-step Circuits … 63 Table 23: Brightness Steps for 3-step Circuits … 63 Table 24: Brightness Steps for 1-step Circuits … 63 Table 25: Event Classification Example … 64 Table 26: Generator and ATS Interface Example … 66
FAA Specification for L-890 Airport Lighting Control and Monitoring System (ALCMS) 1. Scope and Classification 1.1 Scope This specification covers the requirements and recommendations for an Airport Lighting Control and Monitoring System (ALCMS) 1.2 Equipment Classifications This specification covers the Airport Lighting Control and Monitoring System with the following classifications types.
1.2.1 Type The following types of systems are covered by this specification
1.2.1 Type The following types of systems are covered by this specification
Table 1: ALCMS Classification Types Details regarding requirements of the classification types are covered by this specification in the following sections: Control Design Requirements Section 5 Monitoring Requirements Section 6 Failsafe Design Requirements Section 7
L-890 X Y
A - Preset
B - Last State – Latching
A - Control Only
B - Basic Monitoring
C - Advanced Monitoring
D - SMGCS – Individual Lamps Out Monitoring
1.3 Definition of Terms To follow are definitions of terms and acronyms used in this specification
AC Advisory Circular AGL Airport Ground Lighting ALSF High Intensity Approach Lights with Sequenced Flasher ATC Airport Traffic Control – Includes ATCT and Flight Service Station ATCT Airport Traffic Control Tower CCR Constant Current Regulator CGC Commercial Grade Computer CPU Central Processing Unit CRT Cathode Ray Tube CSR Current Sensing Relay Designer One who designs and specifies the requirements for the ALCMS Electrical Vault Installation location of Constant Current Regulators EMI Electro-magnetic Interference FSS Flight Service Station GUI Graphical User Interface HMI Human Machine Interface: a touchscreen that displays an airport graphic with touch points that control the various constant current regulators and related equipment. IGC Industrial Grade Computer IRM Insulation Resistance Monitor LED Light Emitting Diode PC Personal Computer PLC Programmable Logic Controller MALSR Medium Approach Lighting System with Runway Alignment Indicator Lights M Ohm Meg Ohm PAPI Precision Approach Path Indicator RAID Redundant Array of Inexpensive Disks REIL Runway End Identifier Light RF Radio Frequency RVR Runway Visual Range SMGCS Surface Movement Guidance and Control System UPS Uninterruptible Power Supply VAC Voltage Alternating Current VASI Visual Approach Slope Indicator VDC Voltage Direct Current VP Vault Processor – Computer or Programmable Logic Controller (PLC) 2. Reference Documents 2.1 FAA Advisory Circulars
AC 120-57 Surface Movement Guidance and Control System AC 150-5340-30 Design and Installation Details for Airport Visual Aids AC 150/5345-3 Specification for L-821 Panels for Control of Airport Lighting AC 150/5345-5 Circuit Selector Switch AC 150/5345-10 Specification for Constant Current Regulators and Regulator Monitors AC 150/5345-53 Airport Lighting Equipment Certification Program AC 150/5370-10 Standards for Specifying Construction of Airports
2.2 FAA Orders
2.2 FAA Orders
Order 6750.24 Instrument Landing System and Ancillary Electronic Component Configuration and Performance Requirements Order 6850.2 Visual Guidance Lighting Systems Order 7110.65 Air Traffic Control 2.3 Military Standards MIL-STD-810F DoD Test Method Standard for Environmental Engineering Considerations and Laboratory Tests 2.4 National Electric Code (NEC)
NFPA 70 National Electrical Code
3. ALCMS General System Requirements 3.1 ALCMS Overview Figure 1 illustrates the integration of the primary control and monitoring functions of the ALCMS system. The airport operator can control and monitor all elements of the system using the computer processing power to simplify and manage the systems in a way defined by the airport operator. The arrows indicate the direction in which information flows. A solid line represents the minimum control and monitoring system interfaces one would expect in a basic system. The broken line indicates those options available that may be utilized depending on the airport configuration and requirements.
Figure 1: ALCMS Interface Overview
Airport Lighting Control & Monitoring System
ALCMS
RVR Runway Visual Range
Nav. Aid Systems ALSF, PAPI,
VASI, REIL
Airport
Power Commercial &
Standby
Power
Airfield Ground Lighting Runway & Taxiway lighting
Rotating Beacon and Obstruction Lights
ATC HMI AGL Operator
HMI Airfield Maintenance
VASI, REIL
SMGCS
System Stop Bars,
Sensors
Runway Guard Lights Inpavement RGL Lighting
HMI - Operations or
Remote Computer
Other Systems
Control
Monitoring
Monitoring
Control
Basic Equipment
Optional Equipment
Optional
System Interfaces Legend
L-854 Radio Controller Airport Lighting Control & Monitoring System
ALCMS
RVR Runway Visual Range
Nav. Aid Systems ALSF, PAPI,
VASI, REIL
Airport
Power Commercial &
Standby
Power
Airfield Ground Lighting Runway & Taxiway lighting
Rotating Beacon and Obstruction Lights
ATC HMI AGL Operator
HMI Airfield Maintenance
SMGCS
System Stop Bars,
Sensors
Runway Guard Lights Inpavement RGL Lighting
HMI - Operations or
Remote Computer
Other Systems
Control
Monitoring
Monitoring
Control
Basic Equipment
Optional Equipment
Optional
System Interfaces Legend Basic Equipment
Optional Equipment
Optional
System Interfaces Legend
L-854 Radio Controller
3.2 ALCMS Components Each control system utilizes similar hardware components to perform certain functions that are part of the overall system. The major components of an ALCMS are illustrated in Figure 2 and discussed in detail in the section to follow.
Figure 2: ALCMS Components Overview
3.2.1 ATC Human Machine Interface (HMI) This is the hardware that interfaces between the airport lighting control operator and the control system. The HMI is a touchscreen that displays an airport graphic with touch points that control the various constant current regulators and related equipment. The number of HMI units depends on the complexity of the airport and the desire for added redundancy.
ALCMS Communication Network
ATC
HMI
ATC Computer
Remote
HMI
Remote Computer
Electrical Vault
HMI Vault Communication
Network
Constant
Current Regulator 1
Control & Monitoring Equipment
1
Electrical Vault Computer/Processor
Constant
Current Regulator n
Control & Monitoring Equipment
n
Alternate Control and
Monitoring Methods
Constant
Current Regulator
Control & Monitoring Equipment
ALCMS Communication Network
ATC
HMI
ATC Computer
Remote
HMI
Remote Computer
Electrical Vault
HMI Vault Communication
Network
Constant
Current Regulator 1
Control & Monitoring Equipment
1
Electrical Vault Computer/Processor
Constant
Current Regulator n
Control & Monitoring Equipment
n
Alternate Control and
Monitoring Methods
Constant
Current Regulator
Control & Monitoring Equipment
Electrical Vault
HMI Vault Communication
Network
Constant
Current Regulator 1
Control & Monitoring Equipment
1
Electrical Vault Computer/Processor
Constant
Current Regulator n
Control & Monitoring Equipment
n
Alternate Control and
Monitoring Methods
Constant
Current Regulator
Control & Monitoring Equipment
Refer to 3.2.1 Refer to 3.2.3
Refer to 3.2.4 Refer to 3.2.2
Refer to 3.2.10
Refer to 3.2.7 Refer to 3.2.6
Refer to 3.2.5 Refer to 3.2.9
Refer to 3.2.8
3.2.2 ATC Computer This computer, usually located near the ATC HMI in the tower, receives the commands from the HMI and converts them to digital format for transmission over a fiber optic cable, wireless network or copper wire to a computer in the electrical vault. The computer must be an industrial type. The hardware must be suitable to run operating systems such as a Windows or UNIX platform. Two computers running simultaneously can be utilized if added redundancy is desired. Laptop computers must not be used for the ATC Computer. 3.2.3 Remote HMI This is the hardware that allows remote operating personnel to interface with the ALCMS. This HMI is typically a service monitor, keyboard and mouse (Touchscreen is optional). This HMI displays “view only” status information of the ALCMS. The number of Remote HMI units depends on the complexity of the airport and the desire for added redundancy. A Remote HMI must be capable of providing “control” capabilities if desired by the airport.
3.2.4 Remote Computer The airport may desire computer(s) at other locations around the airport for the purpose of monitoring the status of the airport lighting equipment (i.e. Operations). This computer will be connected to the airport network utilizing the appropriate network interface equipment and will display the information required by the airport via the Remote HMI mentioned previously. 3.2.5 Electrical Vault HMI This is the hardware that provides an operator interface at the Electrical Vault. This HMI is typically a service monitor, keyboard and mouse (Touchscreen is optional). This HMI defaults as “view only” status information of the ALCMS. The number of Vault HMI units depends on the complexity of the airport and the desire for added redundancy. The Vault HMI must be capable of providing “control” capabilities if desired by the airport. 3.2.6 Electrical Vault Computer This computer is the same type as the ATC computer except it is located in the electrical vault and has the necessary equipment for interfacing with the vault network.
The network interfacing equipment may be integral or separate from the vault computer. Two computers running simultaneously can be utilized if added redundancy is desired. Laptop computers must not be used for the Electrical Vault Computer. 3.2.7 Vault Processor (VP) This device interfaces directly with the ALCMS Communication Network. The VP may be a CPU, PLC or other device that provides the necessary link to the CCR, circuit selector switch, generator, insulation resistance meggering unit, power line carrier, or other system. 3.2.8 Control and Monitoring Equipment Interface This device interfaces with the Vault Communication Network and provides the necessary relay contacts or data link to the CCR, circuit selector switch, generator, insulation resistance meggering unit, power line carrier, or other system. The interface device must have inputs and outputs to handle the control of all previously mentioned equipment. Inputs and Outputs must include analog, digital and other data ports as required for interfacing with the equipment.
The interface device may also have a built in processor. It may also be used in transmitting equipment performance and circuit data to the vault network that will then be transmitted to the ATC HMI and Remote HMI. This device may be an integral component of the control and monitored element or a separate device that is interfaced to the element. 3.2.9 Vault Communication Network The vault communication network provides communication between the electrical vault computer and any controlled or monitored equipment. The vault network transmission medium may be hardwire or fiber optic cable. This network is dedicated for the ALCMS. Refer to Appendix 1: Communications Application Notes for designing the vault communication network.
3.2.10 ALCMS Communication Network The communication network ties all the various computers and the electrical vault computer(s) together forming the Airport Lighting Control and Monitoring System (ALCMS). The network transmission medium may be hardwire, fiber optic cable or wireless. This network is dedicated for the ALCMS. Refer to Appendix 1: Communications Application Notes for designing the ALCMS communication network. 4. Design Requirements This section provides design requirements for the ALCMS and reviews all of the subsystems that may be incorporated as part of the control and monitoring system. 4.1 Environmental Requirements The equipment furnished as part of the control and monitoring system must be suitable for the environment that it will be operated in. All equipment must be rated to operate in ambient temperature between 32°/+104°F (0°C/+40°C) at 0-90% relative humidity. The ALCMS components must be housed in an enclosure (minimum NEMA 12) in accordance with applicable NEC requirements for the environmental conditions.
Additional climate control of the ALCMS component enclosures may be required based on site conditions. The ALCMS must cause minimal radiated or conducted electromagnetic interference to other equipment such as computers, radars, instrument landing systems, radio receivers, very high frequency omni directional radio ranges, etc., that may be located on or near an airport, or that may use the same power supply. 4.2 Electrical Requirements All enclosures must meet the NEC requirements for volume to house components. Wiring sizes, insulation, and over-current protection devices must meet the NEC requirements. Fiber Optic cables must meet the NEC requirements. Low voltage from computer cabinets to control and monitoring devices must meet the NEC requirements for permanent wiring. 4.3 Hardware Requirements This section provides detailed hardware design requirements for the selection and specifying of the ALCMS components as illustrated in Figure 2.
4.3.1 ATC HMI The ATC HMI must be a touchscreen monitor. The Designer must specify the size, resolution and mounting requirements of the monitor. Monitor resolution must be capable of displaying the airport graphics. At a minimum the touchscreen monitor must have the following requirements: a. The monitor must be liquid crystal display (LCD) or equivalent technology. CRT monitors
are not acceptable. b. Integrated touchscreen technology. Refer to Appendix 3 for application notes in specifying
the touchscreen technology c. Non-glare, non-reflective viewing surface d. Refer to Appendix 4 for application note regarding touchscreen installation.
4.3.2 ATC Computer The ATC Computer associated with the ATC HMI must have the following minimum requirements:
a. Capable of being installed a minimum of 500 feet (to correspond to Appendix 4.h) from the
ATC HMI. Additional video/communication extension equipment may be required. b. Industrial Grade Computer (IGC) designed for industrial applications. This computer can
be a separate component or integrated with the ATC HMI.
c. All equipment must be assembled in NEMA 12 enclosures and connected as a complete
system. This enclosure must be suitable for the local environment. d. Required communication equipment capable of transmitting the control and status
information between the ATC HMI and the other ALCMS computers. e. Power for the ATC Computer must be from a circuit on the tower emergency power panel
or by an independent uninterruptible power supply specified by the Designer.
4.3.3 Remote HMI The Remote HMI must be a video monitor with keyboard and mouse (Touchscreen monitor is optional). The Designer must specify the size of the monitor based on installation limitations and recommendations from ALCMS manufacturers. Monitor resolution must be capable of handling the airport graphics.
4.3.4 Remote Computer The ALCMS must be capable of adding additional Remote Computers to its network topology as required. The Remote Computer must have the following minimum requirements:
a. Industrial or Commercial Grade Computer. b. Required communication equipment capable of viewing the control and status information
of the ALCMS c. At a minimum the Remote Computer must provide the operator the capabilities to display
the ALCMS historical and current information (events, warnings and alarms). If system has monitoring capabilities, the computer must display airport lighting circuit monitoring status. d. The Remote Computer must default to “view only” but have the capability to control the
airport lighting system if the airport requires this feature. e. Power for the Remote Computer must be from an uninterruptible power supply. 4.3.5 Electrical Vault HMI a. The Electrical Vault HMI must be a video monitor with keyboard and mouse (Touchscreen
monitor is optional). The Designer must specify the size of the monitor based on installation limitations and recommendations from ALCMS manufacturers. Monitor resolution must be capable of handling the airport graphics.
4.3.6 Electrical Vault Computer The Electrical Vault Computer associated with the Vault HMI must have the following minimum requirements:
a. Industrial Grade Computer (IGC) designed for industrial applications. b. All equipment must be assembled in NEMA 12 enclosures and connected as a complete
system. c. Required communication equipment capable of transmitting the control and status
information to the ATC HMI and the other ALCMS computers. d. Capable of control and/or monitoring of the airport circuits, generators, and other devices
within the Electrical Vault e. Interface to Vault Control and Monitoring Equipment. f. Interface to the Failsafe system. g. Power for the Vault Computer must be from an uninterruptible power supply.
4.3.7 Vault Processor The Vault Processor must have the following minimum requirements:
a. All equipment must be assembled in NEMA 12 enclosures and connected as a complete
system. b. Required communication equipment capable of transmitting the control and status
information to the ATC HMI and the other ALCMS computers.
c. Capable of control and/or monitoring of the airport circuits, generators, and other devices
within the Electrical Vault. d. Interface to Vault Control and Monitoring Equipment. e. Interface to the Failsafe system. f. Power for the Vault Computer must be from an uninterruptible power supply. 4.3.8 Control and Monitoring Equipment The Control and Monitoring Equipment must have the following minimum requirements:
a. Power for the Control and Monitoring Equipment must be from an uninterruptible power
supply. b. For design requirements of the Control and Monitoring Equipment, refer to the following
sections: Section 5 Control Design Requirements;
Section 6 Monitoring Requirements;
Section 7 Failsafe Design Requirements. 4.4 Communication requirements The communications subsystem must be capable of communicating over hard wire, fiber optic, wireless or telephone modems to interface the ALCMS components. For added redundancy, a backup link is recommended between the ATC and vault. Where a redundant link is used, it must automatically switch over to the backup link. Once the primary link is available and determined to be operational by the ALCMS the ALCMS must automatically switch back to the primary link. Application notes for communications are provided in Appendix 1 and a worksheet for performing fiber optic budget calculations is provided in Appendix 2. In the event of a loss of communication over one link between these subsystems, an alarm must be displayed on the ATC HMI touchscreens, Vault HMI, and other Remote Client HMIs as defined by the airport sponsor. Refer to section 7.2 for more detail on ALCMS event handling and storage. 4.5 Software Version Control The ALCMS software includes but is not limited to the software source code, compiled programs, executable files and PLC ladder logic. All software associated with the ALCMS must be kept under appropriate version control by the ALCMS manufacturer. Software version control must meet the following minimum requirements:
a. ALCMS manufacturer must have established ISO certified (current edition) software control
procedures. b. Proper software coding techniques must be practiced including software remarks when
appropriate. c. All ALCMS software must be version controlled utilizing a software version control system. d. Software versions must be date stamped with the ability to track software changes. e. All ALCMS software must be stored electronically (i.e. on a network). f. The network must be backed up with back-up copies stored off site. 4.6 Hardware Design Version Control The ALCMS hardware design, including assembly drawings, wiring diagrams and bill of materials must be kept under appropriate version control by the ALCMS manufacturer. Hardware design version control must meet the following minimum requirements:
a. ALCMS manufacturer must have established ISO certified documentation control procedures.
b. The ALCMS hardware must be designed using a commercially available Computer Aided
Design (CAD) software package. c. All ALCMS drawings must be tracked based on date of changes. d. All ALCMS drawings must be stored electronically (i.e. on a network). e. The network must be backed up with back-up copies stored off site. 4.7 Human Machine Interface (HMI) Graphics Requirements This section describes the graphical requirements for the HMI’s of the ALCMS.
4.7.1 General Requirements The ALCMS must have the following minimum HMI graphics requirements:
a. A “CONFIRM” or “ACCEPT” button to prevent unintentional actuation of circuits and to
allow an operator to authenticate a control action . b. A “REJECT” or “CANCEL” button to abort a control action. c. The color red must be used for alarm annunciation of circuit graphics and touch buttons. d. The color orange must be used for maintenance lockout. e. A color legend must be able to be displayed to indicate color representation. f. Various colors must be able to be used to indicate the change of runway and taxiway lighting brightness steps. g. Brightness step settings must be indicated by text on the associated circuit button.
4.7.2 Touchscreen Requirements The Touchscreen interfaces must have the following minimum HMI graphic requirements:
a. A clean screen button to prevent accidental actuation of circuits while cleaning the screen. b. Touch buttons or touch sensitive areas must be a minimum of 5/8 inch wide by 1/2 inch
high. (This is to prevent touching more than one button at a time). c. Separation between touch buttons or touch sensitive areas must be a minimum of 1/8 inch
between button/area edges. (This helps to prevent inadvertent pressing of buttons). d. The system must provide the user with the ability to calibrate the touchscreen. 5. Control Design Requirements
This section describes design requirements for the control methodology of the ALCMS system. 5.1 General Requirements The ALCMS must have the following minimum control requirements:
a. The ALCMS must have the capability of individually controlling each of the airport lighting circuit
elements. This includes changing brightness steps and switching the circuit on or off. b. The ALCMS must be capable of controlling circuit selector switches. c. Each ATC HMI must be capable of independently or simultaneously controlling and displaying
the entire airport lighting system. This applies when multiple ATC HMI’s are designed into the ALCMS. d. The ALCMS must allow transfer of control between the ATC HMI, Remote HMI and Vault HMI
stations. e. The ALCMS must provide the flexibility to provide exclusive control (1 HMI station in control) or
cumulative control (Multiple HMI stations in control). f. The ALCMS must have the capability to enable or disable control authorization at each HMI station. This prevents unauthorized locations from being able to control the airport lighting.
5.2 Control Interfaces The ALCMS must have the following minimum control interfaces:
a. The ALCMS must not allow other external interfaces to automatically control the airport lighting
without confirmation and intervention from an HMI. This includes automatic control changes from the Runway Visual Range (RVR), radio control, photocell, or Sunrise/Sunset tables. b. The ALCMS must have provisions for a photocell or air-to-ground radio (pilot-controlled radio)
to control the airport lighting as required by the operator. Refer to Appendix 5 for design guides on interfacing with air-to-ground radios and photocells. c. The ALCMS must be able to provide Sunrise and Sunset notifications at the ATC HMI as
requested by the Designer and airport d. The ALCMS must be capable of controlling CCRs and other equipment with control power
internally (i.e. CCI) or with control power from an external source (i.e. 120VAC circuit). e. The ALCMS must operate with control voltages of 24VDC, 48VDC or 115 VAC with a tolerance,
of +10% and -5%. f. The ALCMS must be capable of controlling AGL to meet the time requirements in AC 150/5340-30, Design and Installation Details for Airport Visual Aids. 5.3 Control Soft Start Requirements The ALCMS must have the following minimum soft start control requirements:
a. The ALCMS must provide “Soft Start” control functionality to allow for automatic ramping up
and down of brightness level of AGL. b. The “Soft Start” ramp up control function must switch circuits on, and then step up the
brightness level in a controlled fashion. c. The “Soft Start” ramp down control function must switch circuits down through the brightness
levels and then turn the circuit off. d. The “Soft Start” switching interval (time delay) must be adjustable.
Figure 3: Control Methodology Overview 5.4 Pre-programmed Control Buttons Refer to Figure 3: Control Methodology Overview
PRESET BUTTON
PRESET BUTTON
Taxiway
A Edge
Taxiway
A C/L
Runway 18 Edge Runway
18 C/L
CIRCUIT BUTTON
CCT A1
Edge
CCT A2
Edge
CCT A3
Edge
CCT A1
C/L
CCT A2
C/L
CCT 18E1
Edge
CCT 18E2
Edge
CCT 18C1
C/L
CCT 18C2
C/L
CIRCUIT ELEMENT
Runway 18
Operation
a. The ALCMS must have the capability to control a number of circuits using a circuit button. For
CIRCUIT ELEMENT
example, in Figure 3, the Taxiway A Edge Button controls three Taxiway A Edge circuits (A1, A2, A3). b. The ALCMS must be capable of executing preset commands using a preset button. c. Preset commands must be programmable for specific predefined lighting configurations that the
airport and/or air traffic control has established for various operational requirements as illustrated in Figure 3. The preset settings are established in accordance with FAA Order 7110.65, Air Traffic Control Handbook, latest revision. Refer to Appendix 6 for preset tables. d. The ALCMS must be able to override preset lighting configurations as needed using the
individual circuit button. 6. Monitoring Requirements This section reviews the requirements for the monitoring classification types of the ALCMS and provides design recommendations for specifying the monitoring options of the ALCMS. The type of airport lighting monitoring is dependant on the desired operating conditions as well as the level of monitoring information that an airport wishes to collect. The Designer must select the monitoring classification type(s) that matches the monitoring requirements of the airport. Design Note – A combination of all types of monitoring (Type A through D) can be designed into the system to maximize performance and meet any budget constraints. The monitoring selected must coincide with the category of operations the airport is certified for. 6.1 Type A – Control Only This type of monitoring is the lowest level of monitoring and provides basic system level diagnostic and alarm reporting. This monitoring level does not provide monitoring or feedback for the controlled elements of the system (i.e. Constant Current Regulators). The minimum Type A monitoring design criteria is as follows:
a. Annunciation of a computer malfunction to indicate system is unable to execute lighting control
commands. b. Annunciation of communication link warnings (1 link failure) and alarm (complete loss of
communication). c. Annunciation that system is in “Failsafe” to indicate the system is unable to execute remote
lighting control commands and that lighting circuits have switched to the systems failsafe state. Refer to Section 7 for more detail on failsafe. d. Annunciation of Vault control interface equipment failure to indicate the system is unable to
execute a lighting control command to a controlled element or group of elements (i.e. the constant current regulators). Optional monitoring e. Annunciation of loss of system commercial power indicating system is operating on emergency
power. f. Annunciation of UPS warnings and alarms to indicate possible faults with UPS equipment (i.e. loss of input power, UPS on inverter, low battery). 6.2 Type B – Basic Monitoring This type of monitoring increases system operational awareness and provides basic monitoring for the controlled elements not provided in the Type A monitoring. This level of monitoring is typically required at airports capable of operating in VFR or Category I conditions. The minimum Type B monitoring design criteria is as follows:
a. All monitoring requirements of the Type A. b. Feedback that a controlled element (i.e. Runway & Taxiway Lighting) is on or off. This
monitoring must provide positive feedback that a controlled element turned on when it was commanded on and turned off when it was commanded off. c. Basic monitoring must be completed via one of the following methods or an airport approved
equivalent:
Method A - Current Sensing Relay (CSR) - This monitoring method can be designed using a CSR on the output of the Constant Current Regulator or other controlled element. The CSR provides a positive feedback signal when there is a pre-determined current level present on the circuit. For example, the CSR can be set to detect current levels of > 2.5A for 5-step CCRs and > 4.5A on 3-step CCRs. Lower levels of current detection may be required for beacons and other contactors. Method B - Current Transducer Method – This monitoring method can be designed using a Current Transformer (CT) or 4-20mA Current Transducer installed on the output of the CCR or controlled element. This option provides positive feedback similar to the CSR method, but also provides an analog signal corresponding to the output current of the controlled element. Optional monitoring d. Annunciation of loss of system commercial power indicating system is operating on generator
power. e. Annunciation of UPS warnings and alarms to indicate possible faults with UPS equipment (i.e.
loss of input power, UPS on inverter, low battery).
6.3 Type C – Advanced Monitoring This type of monitoring expands even further the monitoring capabilities for the controlled elements not provided in the Type B monitoring. This level of monitoring is typically required at airports capable of operating in Category II and Category III conditions. The minimum Type C monitoring design criteria is as follows:
a. All monitoring requirements of the Type A and Type B. b. CCR monitoring must meet all requirements of AC 150/5345-10 (current edition) - Specification
for Constant Current Regulators and Regulator Monitors. Refer to AC 150/5345-10 for details on these monitoring requirements. c. Monitoring of burnt out lamps. d. Annunciation that number of lamps out has reached warning threshold (Configurable between 1
and 15 lamps). e. Annunciation that number of lamps out has reached alarm threshold (Configurable between 1
and 15 lamps). f. True RMS output current of the CCR (+/- 3%). g. True RMS output voltage of the CCR (+/- 3%).
Optional monitoring h. Annunciation of loss of system commercial power indicating system is operating on generator
power. i. Annunciation of UPS warnings and alarms to indicate possible faults with UPS equipment (i.e. loss of input power, UPS on inverter, low battery).
6.4 Type D – SMGCS Ready: Individual Lamps Out Monitoring This type of monitoring represents the highest level of monitoring capabilities. This level of monitoring is typically required at airports capable of operating at Category III levels that have implemented a SMGCS plan. The minimum Type D monitoring design criteria is as follows:
a. All monitoring requirements of the Type A, Type B and Type C. b. Individual Lamps Out monitoring that meets all the requirements of AC 120-57 and AC
150/5340-30. c. Notification of exact location and fixture ID of burnt out lamp. d. Annunciation of adjacent lights out as specified in SMGCS plan. e. Annunciation of non-adjacent lights out exceeding maintenance criteria specified in SMGCS
plan. f. Annunciation of a functional or operational failure of an individual control and monitoring device, devices or any control components that prevent the ALCMS from receiving accurate status of the individual lamps out system.
Optional monitoring g. Annunciation of loss of system commercial power indicating system is operating on
emergency power. h. Annunciation of UPS warnings and alarms to indicate possible faults with UPS equipment
(i.e. loss of input power, UPS on inverter, low battery). i. Annunciation of movement detected by airport sensors (i.e. microwave, inductive loops). j. Annunciation of alarms of airport sensors. 7. Failsafe Design Requirements
Failsafe is the action taken by the ALCMS to ensure the continued safe operation of the AGL resulting from the inability to execute a command for a controllable element. Failsafe can be executed at the system or component level.
Refer to Section 4.2 for failsafe equipment electrical requirements. An ALCMS that is designed with a self-contained failsafe feature must meet the following minimum criteria:
a. Self-monitor the ALCMS control and monitoring interface equipment and verify proper
operation. b. Ensure predefined default operation of the airport lighting in the event of ALCMS failure,
resulting in a failsafe condition. c. Ensure the airport lighting remains at the failsafe state as long as the CCR has primary power. d. It must be possible to override the failsafe state locally at the CCR or other controlled element
by local personnel. e. Permit maintenance on portions of the control system, without changing the operational status
of the lighting system. f. The failsafe feature must be adaptable to each CCR regardless of internal or external control voltage.
The Designer must select the failsafe mode that matches the requirements of the airport. Failsafe modes must be field changeable by the airport, but may be limited to the ALCMS hardware capabilities.
7.1 Failsafe Types
7.1 Failsafe Types
The ALCMS can be designed with various classification types of failsafe devices. AGL associated with Category II/III operations must have Type B Failsafe. This section reviews the classification types.
7.1.1 Type A - Preset
An ALCMS system with a Preset Failsafe classification type must meet the following minimum criteria:
7.1.1 Type A - Preset
a. Upon a failsafe condition, the ALCMS controlled devices must switch to a pre-defined state
(ON to a pre-defined brightness level, or OFF). b. The pre-defined setting (preset) must be configurable via hardware or software by the
operator. c. Preset failsafe must operate even in the event that there is loss of power to the failsafe
device.
7.1.2 Type B - Last State
7.1.2 Type B - Last State
An ALCMS system with a last state failsafe classification type must meet the following minimum criteria:
a. Upon a failsafe condition, the ALCMS controlled devices must remain on at the same
brightness level prior to failsafe condition. b. The failsafe device must maintain last state (latched) condition. c. The failsafe device must maintain last state even after complete loss of power, including
battery backup. d. Software or firmware within the ALCMS must not be used to maintain last state condition. e. If the CCR or other controlled element was switched OFF before the failure, it must remain
OFF. f. The brightness level of the CCR or other controlled elements must be able to be controlled locally at the CCR or controlled element as requested by the operator.
7.2 Event Message Classification This section reviews the requirements for the generation of event messages within the ALCMS. Event messages must provide a clear and concise understanding of system transactions, warnings and alarms. All Events, Warnings and Alarms are date and time stamped to the second. Application notes on how to specify ALCMS event classification and alarm filtering is provided in Appendix 7. Design Note – The capabilities of generating event messages is dependant upon the type of monitoring specified for the ALCMS. Certain events cannot be generated if the monitoring option is not specified. For example, an ALCMS that is designed as “Control Only” will not provide detailed CCR monitoring such as current, voltage and lamps out.
7.2.1 Events The ALCMS system must be capable of generating and recording event transactions. An event is any operator command or change in the status of monitored equipment. The ALCMS system must be flexible as to provide the user the ability to view the events and must meet the following criteria:
a. Events must be annunciated as specified by the airport sponsor and the ATCT to any
part of the HMI system.
b. Events must be logged to a database. c. Events must be date stamped with date and time of occurrence. This allows for possible
reconstruction of sequences of events within the ALCMS. d. Events that must be recorded include but are not limited to the following:
- Changes in airport lighting brightness steps - Changes in states of the computers (start-up, shut-down) - Changes in states of the communication links (link up, link down) - Changes in control authorizations (Tower control, Vault control) - Changes in warning and alarm states. 7.2.2 Warnings A warning is an event indicating a fault condition or a low-level failure detected by the ALCMS that has not yet resulted in a degradation of visual aids below defined serviceability criteria. The ALCMS system must be flexible as to provide the user the ability to view the warning and must meet the following criteria:
a. The system must provide the ability to classify events as warnings. b. Warnings must be annunciated at maintenance HMI interfaces. c. Warnings must not be annunciated (filtered) at the ATC HMI interfaces. d. Warnings must be logged to a database. e. Warnings must be date stamped with date and time of occurrence. This allows for
possible reconstruction of sequences of events within the ALCMS. f. Warnings that must be recorded include but are not limited to the following: - Commanded brightness step does not match actual output brightness current - Other low-level CCR monitored items (i.e. Low VA) - Lamps Out equal to warning threshold - Changes in states of the communication links (link up, link down) - Loss or change in utility status. 7.2.3 Alarms An alarm is an event indicating a fault condition, detected by the ALCMS that has resulted in a degradation of visual aids below defined serviceability criteria. The ALCMS system must be flexible as to provide the user the ability to view the alarms and must meet the following criteria:
a. The system must provide the ability to classify events as alarms. b. Alarms must be annunciated at maintenance HMI interfaces. c. Alarms must be annunciated at the ATC HMI interfaces. d. Alarms must be logged to a file. e. Alarms must be date stamped with date and time of occurrence. This allows for possible
reconstruction of sequences of events within the ALCMS. f. Alarms that must be recorded include but are not limited to the following: - Protective Shutdown of a CCR - Failure of a controlled element to respond to commanded step - Lamps Out equal to alarm threshold - Loss of communication links (all links down) - System in “failsafe” - Loss or change in utility status. 7.3 Audible Alarm As an option, an audible indication for an alarm event must be provided in conjunction with the ATC HMI touchscreen stations. The audible alarm assembly must be designed such that the tone can be disabled (turned off) and the user can control the volume.
7.4 Event Message Handling Event message handling determines how the ALMCS logs, displays, archives and purges the system events. The level of event handling is dependant upon the type of monitoring options specified. Design Note – A “Control Only” ALCMS system can be designed without an event database. This means that only currently active events (warnings or alarms) are viewable. Once an event is no longer active, the event is purged. An ALCMS with an events storage database for storing and retrieving events must meet the following minimum criteria:
a. Viewing – Events, including warnings and alarms, must be able to be viewed via a user
HMI interface. b. Subset Viewing - Subset of events, including warnings and alarms, must be able to be
viewed via a subset HMI interface that allows the user to specify a date and time range to view. c. Logging – All active and cleared events must be stored to a database designed for
optimal retrieval performance. d. Date/Time Stamp – Stored events must be stamped with the date and time of
occurrence. e. Archiving – Events must be stored for a predefined amount of time. Storage time must
be defined by the airport and must be configurable from 1 day to 1 year. f. Back-up – The ALCMS must provide a method (via HMI interface) for backing up event database to external media (floppy, CD-ROM, tape or other media). g. Purging – The ALCMS must provide a method (automatic or manual) for erasing the
events database to allow for hard disk space recovery. 7.5 Security Administration The ALCMS must provide system-wide security administration capabilities. The system must allow a system administrator to establish user accounts and passwords for end-users and determine each user’s level of system authorization. The security feature must be able to record user’s who logon to the system and record events that occur during the user’s logon period. User accounts are typically set up to be simple, yet allow only those that have been trained in certain aspects of the system to gain access to these features.
7.6 Standard Reporting The ALCMS must provide the capabilities to save (external media) or print out (paper hard-copy) ALCMS system reports. Design Note – A “Control Only” ALCMS system can be designed without an event database and thus would not provide system reporting capabilities. This means that only current active events (warnings or alarms) are viewable and could be printed out. At a minimum, the ALCMS must provide the ability to create the following reports:
a. Events Report – Events, including warnings and alarms, must be able to be saved to external
media or printed to a printer. b. Subset Events Report - Subset of events, including warnings and alarms, must be able to be
saved to external media or printed to a printer. c. Constant Current Regulator Report – Current status of all CCR and other controlled elements
including monitoring status must be able to be saved to external media or printed to a printer.
d. Monitoring Report – Current status of all CCR and other controlled elements including
monitoring status must be able to be saved to external media or printed to a printer. 7.7 System Software Recovery The ALCMS System must provide the ability for complete recovery from system hard drive crashes or computer malfunction. The system must be provided with backup software that would allow the enduser to rebuild a computer hard drive for any of the ALCMS computers (Tower, Vault or Maintenance Center). Design Note: Refer to Appendix 8 for application notes for designing a fault-tolerant hard drive system. 8. Special Interface Design Requirements Refer to section 4.2 for minimum electrical requirements of interface equipment. The Designer of the ALCMS must identify all airport equipment and other navigational aids that the ALCMS will interface with. Airport and FAA equipment may require special control and monitoring requirements. The Designer needs to research these requirements in order to specify them to the ALCMS manufacturer. If the airport wants to incorporate any FAA equipment into the ALCMS, approval must be obtained from the Regional FAA office. The Designer must be familiar with the approach lighting system and understand the control and monitoring operation. The Designer must determine proper contact sizes, current ratings and lightning protection on all control and monitoring points. The Designer must also note the location of the interface wiring. The ALCMS manufacturer must assume the control and monitoring interfaces are handled at the Airport Lighting Electrical Vault unless otherwise specified. The ALCMS manufacturer must assume that dry-contact closures are available for all monitoring feedback points unless specified by the Designer.
8.1 Constant Current Regulator Control An airport’s CCRs may be new or existing. During qualification testing, the ALCS manufacturer must verify that data typical of that shown in Table 4 can be configured into the ALCMS. The Designer must determine the final configuration of the CCRs and complete an index of the information as shown in Table 2: CCR Control and Monitoring Index (The index is shown with sample CCR descriptions).
CCR
# CCR Description Size Current
Output Steps CCI Int./Ext.
B1 (B10)
B2 (B30)
B3 (B100) B4 B5 Manfctr. Model # Monitoring Circuit Selector #
Circuit Selector Loop
Descriptions
1 Runway Edge -RE 30kW 6.6 5 Int. 120 X X X X X CCR Man. Model Lamps Out None
2 Runway Centerline - RC1 30kW 6.6 5 Int. 120 X X X X X CCR Man. Model Lamps Out None
3 Runway Centerline - RC2 30kW 6.6 5 Int. 120 X X X X X CCR Man. Model Lamps Out None
4 Distance Remaining Signs 20kW 6.6 5 Int. 120 X CCR Man. Model Lamps Out None
5 Taxiway A & B Edge 20kW 6.6 3 Int. 120 X X X CCR Man. Model Current Sensing Relay 1 Loop 1 - Twy A Edge Loop 2 - Twy B Edge
6 Taxiway C Edge 10kW 6.6 3 Int. 120 X X X CCR Man. Model Current Sensing Relay None
7 Taxiway Signs 10kW 6.6 3 Int. 120 X CCR Man. Model Current Sensing Relay None
8 Taxiway A Centerline 10kW 6.6 3 Int. 120 X X X CCR Man. Model Current Sensing Relay None
Steps Used (indicate w/ X)
Table 2: CCR Control and Monitoring Index
The following is a description of each column of the CCR control and monitoring index:
CCR # Number of ID used by the airport to designate the associated CCR. CCR Description Description or lighting function of the CCR. Size kW rating of the CCR (4kW – 70kW). Current Output Output current from the CCR (6.6A or 20A). Steps Number of steps available on the CCR (1, 3 or 5 step CCR). CCI Int./Ext. Control voltage availability internal to the CCR (48VDC or 120VAC). Older model CCRs do not have internal CCI and require external 120VAC power source to control and must be indicated as “Ext. “ Steps Used Indicate with an “X” what steps are used on the CCR. CCRs may have 3 or 5 steps but only 1 or some of the steps are used in the control system. Manufacturer Manufacturer indicated on the CCR product label. Model # Model number indicated on the CCR product label. Monitoring Monitoring requirements for the CCR. When L-829 monitoring is specified, the Designer must verify that appropriate monitoring points are available on existing equipment. Remote/Local and Primary Power monitoring points must be determined by the Designer and may require CCR manufacturer to modify the CCR to provide required monitoring points. Circuit Selector # The Designer must verify if CCR(s) are interfaced to circuit selector switches
and indicate selector switch number. Circuit Selector If circuit selector switches are interfaced to the CCR(s), the Designer must Loop Description indicate the function and description of each associated loop.
ALCMS Interface Equipment [dry-contact closures]
ALCMS SYSTEM
RVR EQUIPMENT Runway Visual Range (RVR) Equipment
ALCMS SYSTEM
Edge Step 3
Tower Touchscreen
HMI ALCMS System
RVR INTERFACE WIRING
Edge Step 4
Edge Step 5
C/L Step 3
C/L Step 4
C/L Step 5
TDZ Step 3
TDZ Step 4
TDZ Step 5
8.2 Runway Visual Range (RVR) An airport’s RVR equipment may be new or existing. The Designer must determine if RVR monitoring must remain “as-is” and be handled by the airport or if the ALCMS must be required to provide RVR monitoring feedback. RVR monitoring feedback from the ALCMS system must be able to provide simple dry-contact closures confirming circuit brightness steps as illustrated in Figure 4. This confirmation feedback is typically only needed for the top three brightness steps of the CCR. The contact closure must only occur when the CCR meets the desired monitoring feedback criteria. This means the contact must only close when the CCR has reached the brightness step and is providing the correct current for that brightness step.
RVR INTERFACE WIRING
Figure 4: RVR Interface Diagram
Design Note: This example is one method of providing RVR monitoring feedback that provides simple contact closures that are used for the interface point. The Designer must verify that this type of feedback is acceptable and must interface with the RVR equipment. The Designer must also note the location of the interface wiring. The ALCMS manufacturer must assume the control and monitoring interfaces are handled at the Airport Lighting Electrical Vault unless otherwise specified.
8.3 Approach Lighting Control and monitoring of airport’s approach lights and navigational aids is airport specific. Figure 5 provides general guidelines for specifying an interface between an ALSF and the ALCMS. Designer Note: If an airport is requesting integration of the approach lighting into the ALCMS system, the Designer must thoroughly research the control functionality that the airport requires. However, all interfaces with FAA owned equipment must be approved by the FAA. Typically approach lighting control and monitoring cabling is located at the ATCT. This means that control and monitoring equipment must now be designed into the ATC computer system (The ATC computer system normally does not provide any control or monitoring points).
Figure 5: ALSF Interface Diagram
8.3.1 ALSF / SSALR Approach System For steady burning lights refer to Section 5 and Section 6 for control and monitoring. The sequenced flasher lights must provide the minimum control and monitoring criteria outlined in Table 3.
Sequence Flasher Control Points Monitoring Points ALSF/SSALR Control ALSF/SSALR Mode Low Intensity Low Intensity Medium Intensity Medium Intensity High Intensity High Intensity Approach On/Off Flasher On Flashers On/Off Local Mode Caution Fault
Table 3: ALSF / SSALR Interface Criteria
ALCMS Interface Equipment [dry - contact closures]
ALCMS SYSTEM
ALCMS SYSTEM
ALSF EQUIPMENT
ALSF Master Control Cabinet
ALSF/ SSALR
Tower Touchscreen
HMI ALCMS System
Low Med
FAA INTERFACE
WIRING High
/ ALSF/ SSALR
Low Med High Flasher
On
Rem Local
Caution Fault
Control Monitoring
Approach Flasher
ALCMS Interface Equipment [dry - contact closures]
ALCMS SYSTEM
ALSF EQUIPMENT
ALSF EQUIPMENT
ALSF Master Control Cabinet
ALSF/ SSALR
Tower Touchscreen
HMI ALCMS System
Low Med
FAA INTERFACE
WIRING High
/ ALSF/ SSALR
Low Med High Flasher
On
Rem Local
Caution Fault
Control Monitoring
Approach Flasher
8.3.2 MALSR / MALSF Approach System The ALCMS interface must provide the minimum control and monitoring criteria outlined in Table 4: MALSR / MALSF Interface Criteria.
/ ALSF/ SSALR
Control Points Monitoring Points MALSR/MALSF Control MALSR/MALSF Mode Low Intensity Low Intensity Medium Intensity Medium Intensity High Intensity High Intensity Approach On/Off Flasher On Flashers On/Off Local Mode Caution Fault
Table 4: MALSR / MALSF Interface Criteria
8.3.3 REIL, ODALS, PAPI, and VASI Approach System The ALCMS interface must provide the minimum control and monitoring criteria outlined in Table 5.
Control Points Monitoring Points On/Off Control Lamp Out Low Intensity Medium Intensity High Intensity
Table 5: REIL, ODALS, PAPI, and VASI Interface Criteria
8.4 General ON/OFF Contactor control and monitoring Some airports will have several ON/OFF control contactors that may be used for controlling devices. Some examples of ON/OFF contactors include, but are not limited to, sequence flashers (current or voltage driven), low intensity approaches (LIA), windsocks, obstruction lights and floodlights. The Designer must be familiar with the ON/OFF contactors and understand the control and monitoring operation. The Designer must determine proper contact sizes, current ratings and lightning protection on all control and monitoring points for the ON/OFF contactors. Refer to Figure 6 for design guidelines for interfacing an ALCMS to control and monitor ON/OFF contactors or other types of ON/OFF controlled equipment. Designer Note: This type of design consideration applies to all types of airport equipment that does not follow the standard CCR (step 1 through step 5) control scheme. Special design research and precautions need to be taken when interfacing with any device that requires special control and/or the energizing of a contactor.
Figure 6: Contactor Interface Diagram
ALCMS SYSTEM
ON/OFF CONTROL EQUIPMENT
Miscellaneous Control and Monitoring
Contactor
ON/OFF
Tower Touchscreen
HMI ALCMS System
Feedback
1
INTERFACE WIRING
Control Monitoring
Contactor
ON/OFF
INTERPOSING RELAY CABINET
Feedback
2 Feedback
3
INTERFACE WIRING
INTERFACE WIRING
Source
Common
ALCMS Interface Equipment [dry-contact closures]
ALCMS SYSTEM
ON/OFF CONTROL EQUIPMENT
Miscellaneous Control and Monitoring
Contactor
ON/OFF
Tower Touchscreen
HMI ALCMS System
Feedback
1
INTERFACE WIRING
Control Monitoring
Contactor
ON/OFF
INTERPOSING RELAY CABINET
INTERPOSING RELAY CABINET
Feedback
2 Feedback
3
INTERFACE WIRING
Source
Common
ALCMS Interface Equipment [dry-contact closures]
8.4.1 Contactor Control Refer to Figure 6. Voltage driven equipment that require the energizing of a contactor may require a special interposing relay design to accommodate the low current switching capabilities of the ALCMS system.
INTERFACE WIRING
8.4.2 Contactor Monitoring Monitoring of the voltage driven equipment can be accomplished by adding a Current Sensing Relay (CSR) to the output side of the contactor. The CSR can be adjusted to provide positive feedback when a predetermined current level is detected on the contactor output. This type of on/off monitoring can be applied to any type of contactor-controlled device. 8.5 Generator and Automatic Transfer Switches (ATS) There are many options available for control and monitoring the generator and ATS. It is up to the Designer to determine control and monitoring “pick-up” points and terminal block connections within the existing or specified equipment. Refer to Appendix 9 for application notes on generator and ATS interface wiring.
8.5.1 Generator Control The control capabilities of the Generator are specific to each manufacturer. Refer to Table 6 for general guidelines for controlling Generators.
Option Control Signal Description Comments 1
Generator Start/Stop Maintained Contact Closed – Generator Start Open – Generator Stop 2 Generator Start/Stop Momentary Pulse 1st Pulse – Generator Start 2nd Pulse – Generator Stop 3 Generator Start Momentary Pulse Older Type Generators Generator Stop Momentary Pulse Older Type Generators 4 Generator Start Maintained Contact Generator Stop Maintained Contact
Table 6: Generator Control Interface Criteria
8.5.2 Generator and ATS Monitoring The monitoring capabilities of the Generator and Automatic Transfer Switch (ATS) are specific to each manufacturer. Not all Generator and ATS equipment provide monitoring signals by default. Designer must determine availability of monitoring points and determine if optional monitoring kits are needed to provide monitoring functions. The Designer must specify the monitoring kits. Refer to Table 7 for general guidelines for specifying Generator and ATS monitoring.
Monitoring Signal Description Comments Generator Alarm Common Alarm Alarm exists at the Generator. May require monitoring kit Utility Available Utility power is present May require monitoring kit Utility On-line Utility power is primary source of power
May require monitoring kit
Generator Available
Generator is running and available for transfer
May require monitoring kit
Generator On-line Generator power is primary source of power
May require monitoring kit
Table 7: Generator Monitoring Interface Criteria
8.6 Rotating Beacon The rotating beacon control differs for every airport. The Designer must become familiar with the airport’s equipment and understand the existing control and monitoring operation and design accordingly in the ALCMS. The Designer must determine proper contact sizes, current ratings and lightning protection on all control and monitoring points for the Rotating Beacon. Refer to Appendix 10 for more information.
8.6.1 Beacon control in ATCT If the beacon control wiring is located at the ATCT, this will require special control and monitoring equipment within the ATC computer enclosure such as additional control relays or a PLC.
8.6.2 Beacon control in Vault If the control wiring is located at the airport lighting vault, an additional control and monitoring device needs to be specified.
8.6.3 Remote Beacon control The beacon may be controlled via a radio, fiber optic, telephone line or a photocell. In this case, special control equipment must be specified indicating how the beacon is to be controlled by the ALCMS system. This may require the use of a dial-up modem control device, wireless radio equipment or new control wiring will have to be pulled between the beacon location and the ALCMS.
8.6.4 Beacon monitoring If beacon monitoring is required, the Designer must specify the type of monitoring and determine all of the proper wiring, “pick-up” points and contact ratings of the monitoring points. The beacon may provide monitoring contact closures that must interface with the ALCMS system or the Designer may have to specify a current sensing relay or other device to provide on/off monitoring. 9. Manufacturer Support 9.1 Warranty The ALCMS manufacturer must warrant against defects in workmanship, hardware and software for a minimum period of twelve (12) months. 9.2 Training The ALCMS manufacturer must provide the following documentation and training.
9.2.1 Touchscreen Simulation The ALCMS manufacturer must provide as part of the training package a method for running the ALCMS touchscreen HMI on a separate computer not connected to the ALCMS network. This Touchscreen simulation must run independently of the ALCMS and provide a method for training personnel outside of the ALCMS environment.
9.2.2 Training Agenda The ALCMS manufacturer must provide a sample training course syllabus and training schedule before on-site training.
9.2.3 FAA ATC Training The Designer must specify the amount and length of training classes required for FAA ATC training. The Designer must have previously coordinated with the FAA the number of controllers and shifts that will need to be trained. The total number of classes, lengths of classes and shifts
of classes needs to be specified. Training classes for FAA ATC personnel must be limited to a maximum of 4-6 people per class. Typical FAA ATC training classes last approximately 1-2 hours but depend on the complexity of the ALCMS system. The Designer must coordinate with the FAA ATC Training Coordinator that they are capable of performing touchscreen training. This method of training would allow the ALCMS manufacturer to train the FAA ATC training coordinator who would then be responsible for training all of the ATC personnel prior to commissioning of the new ALCMS system. This dramatically simplifies the FAA ATC training program and is the most efficient method. The FAA ATC training must include the following minimum criteria:
a. General system overview – Theory of Operation b. Review touchscreen operations c. Review AGL Operator HMI interface d. Review preset and control sequences e. Review Events, Alarm and Warning messages f. Review failsafe scenarios and what to do during failsafe g. Review how to grant and relinquish airport lighting control to the Vaults.
9.2.4 Maintenance Training The Designer must specify the amount and length of training classes required for maintenance and other airport personnel (i.e. Operations). The Designer must have previously coordinated with the airport the number of maintenance personnel and shifts that will need to be trained. The total number of classes, lengths of classes and shifts of classes needs to be specified. Training classes for maintenance personnel must be limited to a maximum of 4-6 people per class. Typical training classes for maintenance personnel must be scheduled for two (2) days at 8 hours per day, but depend on the complexity of the ALCMS system. The Maintenance training must include the following minimum criteria:
a. Review system block diagram – Theory of Operation b. Review drawing package - System assemblies and wiring diagrams c. Review touchscreen operation d. Review Maintenance HMI interface e. Review system maintenance f. Provide hands-on troubleshooting g. Review how to grant and relinquish airport lighting control to the Vaults h. Review system power-up and power-down sequences i. Review failsafe scenarios and what to do during failsafe j. Review system reporting capabilities k. Review control and monitoring capabilities. 9.3 Technical Support The ALCMS manufacturer must provide the following minimum technical support during the warranty period:
a. Technical phone assistance b. Technical support via telephone line must be available 7 days a week, 24 hours a day,
365 days a year c. On-site technical field service as required. 9.4 Documentation The Designer must specify the details of the ALCMS documentation package. The ALCMS manufacturer must demonstrate that they are capable of providing a professional documentation package that meets the criteria outlined in this section.
9.4.1 Maintenance Manuals The ALCMS manufacturer must provide one copy, or as specified, of the operation and maintenance manuals that are hard-covered and suitable for daily operation and maintenance of the system. The manuals must include operational overview, system theory of operation and graphical user interface screen operation. 9.4.2 FAA ATC Manuals The ALCMS manufacturer must provide one copy, or as specified, of the operation manuals for the Air Traffic Controllers (ATC) that are hard-covered and suitable for daily operation of the system. At a minimum, the manuals must include Touchscreen operation (human machine interface) and Touchscreen maintenance (i.e. calibration). 9.4.3 As-Installed Drawing Package The ALCMS manufacturer must provide one copy, or as specified, of As-Installed drawings after system acceptance. The As-Installed drawings must reflect the final installation design of the ALCMS including System Block Diagram (1-line drawings), System External Wiring Diagrams, Assembly Drawings and Assembly Wiring Diagrams. 9.5 System Testing The ALCMS manufacturer must provide a set of test documents detailing the level of testing to be performed. The ALCMS testing must meet the minimum criteria outlined in this section.
9.5.1 Factory Acceptance Test (FAT) The ALCMS manufacturer must perform a FAT at the manufacturer’s facility to assure that the ALCMS meets the requirements of the specification. The FAT must demonstrate operation of the software and hardware design. A report of the FAT must be provided by the manufacturer. Design Note: As an option, the Designer may specify that the FAT be witnessed by the Designer and/or an airport representative. The Designer must specify who is responsible (Contractor or ALCS manufacturer) for covering the expenses of the FAT including travel expenses and per diems. If not specified, the ALCMS manufacturer must assume that the Contractor covers FAT expenses not including ALCMS manufacturer’s labor.
9.5.2 System Acceptance Test (SAT) The ALCMS manufacturer must perform a SAT on-site (airport) to assure that the ALCMS meets the requirements of the specification. The SAT test plan must be submitted to the Designer for review and approval of the completeness of the SAT. The SAT must be witnessed by the Designer. The SAT must demonstrate operation of the software and hardware design to the satisfaction of the Designer. A report of the SAT must be provided by the manufacturer. 9.6 Spare Parts The Designer must specify the type of spare parts in the project specifications required for the continued operation of the ALCMS.
10. Qualification Requirements This section provides detail on the testing and qualification requirements that must be met by the ALCMS manufacturer initially and every four years in order to certify an ALCMS system. However, even though Advisory Circular 15/5345-53, Airport Lighting Equipment Certification Program, requires manufacturers to test and qualify airport lighting equipment every eight years, components associated with an ALCMS will change significantly over an eight-year term versus a four-year term, and therefore a recertification term of eight years for testing and qualification is too long. A length of four years will be used for testing and qualification of ALCMS equipment. The qualification testing is outlined to indicate what tests are necessary for each associated classification type. 10.1 Qualification Procedures An ALCMS manufacturer must successfully complete qualification tests outlined herein to receive certification of their ALCMS and specific classification type.
In addition, the procedures for qualifying equipment to be furnished under the Federal grant assistance program for airports contained in AC 150/5345-53, Airport Lighting Equipment Certification Program must also be met. 10.2 ALCMS Test System - Hardware Design Requirements The tests are designed to demonstrate all operational requirements using an actual ALCMS test system integrated with simulated airport lighting conditions and control equipment. This includes interfacing to CCRs, circuit selector switches and actual lighting loads. All control outputs with their associated interfaces must be demonstrated. All monitoring requirements must be verified by simulating the appropriate condition. A representative of each type of hardware, communication media, software structures, and interface equipment must be included in the qualification testing.
Lamp Load 10 lamps min.
Redundant ALCMS Communication Network
ATC HMI
ATC HMI
Electrical Vault
HMI
Redundant Vault Communication Network
Remote HMI
Twy Edge
CCR
Control & Monitoring Equipment
ATC Computer
Electrical Vault
Computer
Rwy 9/27
TDZ CCR
Control & Monitoring Equipment
L-847-2 Circuit Selector
Lamp Load 10 lamps min. Lamp Load 10 lamps min.
TDZ CCR
Loop 1 Loop 2
9 PAPI ON
GEN ON
BEACON ON
27 PAPI ON 9 REIL ON
Control & Monitoring Equipment
GEN AVAIL GEN ON-LINE UTIL AVAIL UTIL ON-LINE
MED
FLASHERS
LOW
HIGH ALSF/SSALR
ALSF/SSALR LOW MED HIGH FLASHER LOCAL/REM CAUTION FAULT
Control & Monitoring Equipment
1
2 4
3
6
7
8
9
10
11
ALSF/SSALR LOW MED HIGH FLASHER LOCAL/REM CAUTION FAULT
12
13
14 14
17
18
19
20
21
22
23
24 25
26
26
Rwy EDGE Simulated
CCR
Control & Monitoring Equipment
15
16
Remote Computer Laser Printer
5
The numbers in the shaded boxes refer to the text in the following section.
Figure 7: ALCMS Test System Hardware Design The minimum ALCMS test system design required for ALCMS certification is illustrated in Figure 7. To follow is an outline of the components indicated in Figure 7that is required to be assembled and tested for certification:
1. ATC HMI must meet the requirements of 4.3.1 and the following: Screen size: 15-inch minimum Resolution: 1024x768 Input device: touchscreen only (no keyboard or mouse). 2. ATC computer must meet the requirements of 4.3.2 and the following: Signal extension equipment tested with 500 feet extension cable. The signals must include video, audio, and touch input. An UPS must provide a minimum of ten minutes of run time for all equipment. All equipment must be assembled in NEMA 12 enclosures and connected as a complete system. 3. Remote HMI must meet the requirements of 4.3.3 and the following: Screen size: 15-inch minimum Resolution: 1024x768.
4. Remote computer must meet the requirements of 4.3.4. 5. Remote computer Laserjet Printer. 6. Vault HMI must meet the requirements of 4.3.5 and the following: Screen size: 15 inch minimum Resolution: 1024x768. 7. Vault computer must meet the requirements of 4.3.6 and meet the following requirements: An UPS must provide a minimum of ten minutes of run time for all equipment. All equipment must be assembled in NEMA 12 enclosures and connected as a complete system. 8. Control and monitoring equipment must meet the requirements of 4.3.8 and configured to control a 3 step CCR. 9. Taxiway Edge - A 3 step Constant Current Regulator must be used to assure control and monitoring equipment properly controls a 3 step CCR 10. A lighting load including a minimum of ten (10) isolation transformers and ten (10) lights. 11. Control and monitoring equipment must meet the requirements of 4.3.8 and configured to control a 5 step CCR and a L-847-2 circuit selector. 12. Runway 9 & 27 TDZ - A 5-step Constant Current Regulator must be used to assure control and monitoring equipment properly controls a 5 step CCR 13. An L-847-2 circuit selector must be used to assure control and monitoring equipment properly controls a circuit selector 14. A lighting load on the output of each loop of the circuit selector including a minimum of ten (10) isolation transformers and ten (10) lights. 15. Control and monitoring equipment must meet the requirements of 4.3.8 and configured to control a 5-step CCR.
16. Simulation equipment must be provided to demonstrate control of the following 5-step CCR control points.
O.1 Rwy Edge Step 1 O.2 Rwy Edge Step 2 O.3 Rwy Edge Step 3 O.4 Rwy Edge Step 4 O.5 Rwy Edge Step 5 17. Control and monitoring equipment must meet the requirements of 4.3.8 and configured to control five (5) On/Off elements and monitor four (4) feedback signals.
18. Simulation equipment must be provided to demonstrate control of the following five (5) Outputs.
O.6 Beacon ON O.7 PAPI #1 ON O.8 PAPI #2 ON O.9 REIL ON O.10 GEN ON. 19. Simulation equipment must be provided to demonstrate monitoring of the following four (4) inputs feedback signals.
I.1 GEN AVAIL I.2 GEN ON-LINE I.3 UTIL AVAIL I.4 UTIL ON-LINE.
20. Control and monitoring equipment must meet the requirements of 4.3.8 and configured to control an ALSF Approach System with five (5) control signals and monitor eight (8) feedback signals. 21. Simulation equipment must be provided to demonstrate control of the following five (5) On/Off signals for the ALSF Approach System.
O.11 LOW O.12 MED O.13 HIGH O.14 ALSF/SSALR O.15 FLASHERS. 22. Simulation equipment must be provided to demonstrate monitoring of the following eight (8) feedback signals from the ALSF Approach System.
I.5 ALSF/SSALR I.6 LOW I.7 MED I.8 HIGH I.9 FLASHER I.10 LOCAL/REMOTE I.11 CAUTION I.12 FAULT. 23. The Vault Communication Network must meet the requirements of 4.4 and must be configured as a multiple redundant network using hardwire communication cable. This item is not required if the Alternate Control and Monitoring method is used.
24. Link (1) of the ALCMS Communication Network must meet the requirements of 4.4 and must be configured as a fiber optic link. Simulation equipment must be provided to assure communication over 3 miles of fiber.
25. Link (2) of the ALCMS Communication Network must meet the requirements of 4.4 and must be configured as a hardwire link. Simulation equipment must be provided to assure communication over 1 miles of hardwire cable.
26. Link (3) of the ALCMS Communication Network must meet the requirements of 4.4 and must be configured as a wireless radio link. Simulation equipment must be provided to assure communication over 3 miles.
10.3 ALCMS Test System – Touchscreen GUI Design Requirements The ALCMS manufacturer must configure an ALCMS Test System according to the touchscreen GUI design requirements of this section. All regulator presets must follow the guidelines of FAA Order 7110.65. The touchscreen design and functionality must meet all of the criteria previously outlined in this document.
10.3.1 Test System Touchscreen GUI Overview The touchscreen GUI must be configured with three (3) pages referred to as Preset Page, Rwy/Twy Page and Utility Page. The GUI must depict the test airport graphics as shown in Figure 8.
Figure 8: ALCMS Test System Touchscreen GUI: Preset Page
PRESET
PAGE
RWY 9 RWY 27
RWY 9 RWY 27
UTIL AVAIL
CONFIRM REJECT
A A-W B D E A-E
North
UTIL ONLINE
GEN AVAIL
GEN ONLINE
UTILITY STATUS
UTILITY
PAGE RWY/TWY
PAGE
C
ATCT
VAULT
RWY
9
RWY OPERATIONS DAY/NIGHT VISIBILITY
RWY
27
DAY
NIGHT
< 1 m
1-2 m 2-3m
3-5m > 5m
ALARM SILENCE
ALARM DISPLAY Runway 9 Operations
ALARM SILENCE
Day 3-5m Visibility
10.3.2 Preset Page and Airport Lighting Presets The touchscreen’s preset page must match the test system shown in Figure 8. The preset lighting configurations must be programmed in accordance with preset tables outlined to follow. There is one (1) preset table for each visibility setting.
CIRCUIT DESCRIPTIONS Steps RWY 9 RWY 27 RWY 9 RWY 27 9-27 Edge 5 0 0 1 1 9 TDZ 5 0 0 1 0 27 TDZ 5 0 0 0 1 9 REIL 1 1 0 1 0 9 PAPI 1 1 0 1 0 27 Approach Lights 3 0 0 0 1 27 Flashers 3 0 0 0 1 27 PAPI 1 0 1 0 1 Taxiway Edge 3 0 0 1 1 Beacon 1 0 0 1 1 Generator 1 0 0 0 0
DAY OPERATIONS OPERATIONS
DAY OPERATIONS OPERATIONS
NIGHT
Table 8: Greater than 5 miles Visibility
CIRCUIT DESCRIPTIONS Steps RWY 9 RWY 27 RWY 9 RWY 27 9-27 Edge 5 0 0 2 2 9 TDZ 5 0 0 2 0 27 TDZ 5 0 0 0 2 9 REIL 1 1 0 1 0 9 PAPI 1 1 0 1 0 27 Approach Lights 3 0 0 0 1 27 Flashers 3 0 0 0 1 27 PAPI 1 0 1 0 1 Taxiway Edge 3 0 0 1 1 Beacon 1 0 0 1 1 Generator 1 0 0 0 0
DAY NIGHT OPERATIONS OPERATIONS
DAY NIGHT OPERATIONS OPERATIONS
Table 9: 3 to 5 miles Visibility
CIRCUIT DESCRIPTIONS Steps RWY 9 RWY 27 RWY 9 RWY 27 9-27 Edge 5 3 3 3 3 9 TDZ 5 3 0 3 0 27 TDZ 5 0 3 0 3 9 REIL 1 1 0 1 0 9 PAPI 1 1 0 1 0 27 Approach Lights 3 0 0 0 1 27 Flashers 3 0 0 0 1 27 PAPI 1 0 1 0 1 Taxiway Edge 3 0 0 1 1 Beacon 1 0 0 1 1 Generator 1 0 0 0 0
DAY NIGHT OPERATIONS OPERATIONS
Table 10: 2 to 3 miles Visibility
CIRCUIT DESCRIPTIONS Steps RWY 9 RWY 27 RWY 9 RWY 27 9-27 Edge 5 4 4 3 3 9 TDZ 5 4 0 3 0 27 TDZ 5 0 4 0 3 9 REIL 1 1 0 1 0 9 PAPI 1 1 0 1 0 27 Approach Lights 3 0 0 0 1 27 Flashers 3 0 0 0 1 27 PAPI 1 0 1 0 1 Taxiway Edge 3 0 0 1 1 Beacon 1 1 1 1 1 Generator 1 0 0 0 0
DAY NIGHT OPERATIONS OPERATIONS
Table 11: 1 to 2 miles Visibility
CIRCUIT DESCRIPTIONS Steps RWY 9 RWY 27 RWY 9 RWY 27 9-27 Edge 5 5 5 4 4 9 TDZ 5 5 0 4 0 27 TDZ 5 0 5 0 4 9 REIL 1 1 0 1 0 9 PAPI 1 1 0 1 0 27 Approach Lights 3 0 3 0 2 27 Flashers 3 0 3 0 2 27 PAPI 1 0 1 0 1 Taxiway Edge 3 3 3 2 2 Beacon 1 1 1 1 1 Generator 1 0 0 0 0
DAY NIGHT OPERATIONS OPERATIONS
Table 12: Less than 1 mile Visibility
10.3.3 Runway and Taxiway Page The touchscreen’s Rwy/Twy page must match the test system shown in Figure 9.
Figure 9: ALCMS Test System Touchscreen GUI: RWY/TWY Page
The control methodology for the runway, approach, taxiway and navigational aids must be configured according to the following table:
Button Description
Test System Circuit Name(s) Test System Circuit Name(s)
9-27 EDGE 9-27 EDGE Outputs 0.1 thru 0.5 9 TDZ 9 TDZ RWY TDZ CCR and Loop 1 27 TDZ 27 TDZ RWY TDZ CCR and Loop 2 9 REIL 9 REIL Output Point O.x 9 PAPI 9 PAPI Output Point O.x 27 APPRCH 27 APPRCH Output Points O.x thru O.x 27 FLASHERS 27 FLASHERS Output Points O.x thru O.x 27 PAPI 27 PAPI Output Points O.x thru O.x TWY EDGE TWY EDGE TWY EDGE CCR BEACON BEACON Output Point O.x GEN ON/OFF GENERATOR Output Point O.x
Table 13: Runway/Taxiway Page Control Methodology
TWY EDGE BEACON 9-27 EDGE
TWY EDGE BEACON 9-27 EDGE
PRESET
PAGE
RWY 9 RWY 27
27 APPRCH
9 PAPI
27 PAPI
9 REIL
UTIL AVAIL
OFF 1 CONFIRM REJECT
RWY 9-27
A A-W B D E A-E
2 3 4 5
North
UTIL ONLINE
GEN AVAIL
GEN ONLINE
UTILITY STATUS
27 FLASHERS
RWY 9 APPROACH
9 TDZ
RWY 27 APPROACH
27 TDZ
TAXIWAY NAV AIDS
UTILITY
PAGE RWY/TWY
PAGE RWY/TWY
PAGE
GEN ON/OFF
C
ATCT
VAULT
ALARM SILENCE
ALARM DISPLAY Runway 9 Operations
Day 3-5m Visibility
GENERATOR
10.3.4 Utility Page The touchscreen’s Utility page must match the test system shown in Figure 10.
Figure 10: ALCMS Test System Touchscreen GUI: Utility Page
The button functions for the Utility page must be configured according to the following table:
ALARM SILENCE
Button Description Button Function Control Authorization Executes program to authorize control of airport lighting at the Vault and Remote Computer locations. Calibrate Touchscreen Executes program to authorize calibration of the touchscreen. Clean Screen Executes program to allow for the cleaning of the touchscreen without affecting the airport lighting. Set Date/Time Executes program to allow for authorized user to set the system date and time.
Table 14: Utility Page Control Methodology
PRESET
PAGE
RWY 9 RWY 27
RWY 9 RWY 27
UTIL AVAIL
CONFIRM REJECT
A A-W B D E A-E
North
UTIL ONLINE
GEN AVAIL
GEN ONLINE
UTILITY STATUS
GEN ON/OFF
C
ATCT
VAULT
ALARM SILENCE
ALARM DISPLAY Runway 9 Operations
Day 3-5m Visibility
GENERATOR
CALIBRATE
TOUCH
UTILITIES
CLEAN SCREEN
SET DATE/TIME
CONTROL
AUTH
UTILITY
PAGE RWY/TWY
PAGE RWY/TWY
PAGE
10.3.5 Common Buttons and Indicators All the touchscreen GUI pages must have the following common buttons, indicators and operational fields:
Button, Indicator and Operational Fields
Function
Preset Settings Display in text format the current preset settings selected. Alarm Silence Silences the audible alarm. Alarm Display Executes program to allow for the viewing of current system alarms. UTIL AVAIL Indicator lights green when Utility Available feedback is present. UTIL ONLINE Indicator lights green when Utility Power Online feedback is present. GEN AVAIL Indicator lights green when Generator Available feedback is present. GEN ONLINE Indicator lights green when Generator Power Online feedback is present. OFF,1,2,3,4,5 Brightness Step buttons
Brightness step buttons provide brightness control. Confirm/Reject buttons Confirm and Reject buttons provides confirm and reject functionality.
Table 15: Common Button and Indicator Functions
. 10.4 Qualification Tests The following tests must be performed on each system submitted for qualification, to demonstrate compliance with the specification.
10.4.1 Visual Exam A visual exam must be performed to verify compliance with the specification requirements. All system component details must be identified. All system components must be verified to be an acceptable industrial grade. The HMI must be examined to verify that it meets standard requirements on dimensions, color, visibility, and format.
10.4.2 Hardware Design Review A review must be performed to verify that all required control and monitoring requirements of the specification are provided. Hardware design must match the ALCMS Test System (reference section 10.2). Any optional features must be completely documented.
10.4.3 Software Design Review A review must be performed to verify that all required control and monitoring requirements of the specification are provided. Software design must match the ALCMS Touchscreen GUI Test System (reference section 10.3). Any optional features must be completely documented.
10.4.4 Software Version Control Must meet the requirements of 4.5.
10.4.5 Hardware Design Version Control Must meet the requirements of 4.6.
10.4.6 Documentation Review A review of all documentation provided by the manufacturer to the end user must be performed to verify that it is in compliance with the specification. All warranty, training, and technical support material must be reviewed for adequacy and accuracy. 10.5 Operational Certification Test The operational certification test must be completed to demonstrate that all operational requirements have been met for the ALCMS classification type being certified. Operational tests are specific to the type of ALCMS being certified. The certification test for each type of ALCMS is outlined in Table 16.
Monitoring Failsafe Certification Test L-890- X Y A - Control Only A - Preset Level 1 B - Basic Monitoring A - Preset Level 2 C - Advanced Monitoring B - Last State Level 3 D - SMGCS Ready B – Last State Level 4
Table 16: ALCMS Certification Tests
Level 4 represents the most stringent testing requirements. An ALCMS manufacturer certified under Level 4 testing must complete all tests under Level 1 through 4. An ALCMS manufacturer certified under Level 4 testing must meet all of the requirements for every classification type of ALCMS. 10.6 Level 1: ALCMS Certification Test Level 1 certification test defines all of the test procedures that must be successfully performed for the Level 1 acceptance of an ALCMS. The tests in 10.6.1, 10.6.2, 10.6.3, 10.6.4, and 10.6.5 must be completed to ensure that the ALCMS meets all technical, operational, and performance requirements as designated by a Level 1 certification. 10.6.1 Communication Link Test This test must be used to verify the communication links between each computer node. The test must demonstrate the redundancy capabilities as well as the warning and alarm reporting of the system
Test ID
Action ALCMS Results Database Results
1.1.1 Disconnect Link 1 at Tower
1.1.1 Disconnect Link 1 at Tower
No noticeable operational change. System continues to operate on Link 2 and 3.
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.2 Initiate airfield lighting preset change
No noticeable operational change. All circuits turn on according to preset and control methodology tables.
1.1.3 Reconnect Link 1 at Tower
1.1.3 Reconnect Link 1 at Tower
No noticeable operational change. Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.4 Disconnect Link 2 at Tower
No noticeable operational change. System continues to operate on Link 1 and 3.
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.5 Initiate airfield lighting preset change
No noticeable operational change. All circuits turn on according to preset and control methodology tables.
1.1.6 Reconnect Link 2 at Tower
1.1.6 Reconnect Link 2 at Tower
No noticeable operational change. Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence.
1.1.7 Disconnect Link 3 at Tower
No noticeable operational change. System continues to operate on Link 1 and 2.
1.1.7 Disconnect Link 3 at Tower
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.8 Initiate airfield lighting preset change
No noticeable operational change. All circuits turn on according to preset and control methodology tables.
1.1.9 Reconnect Link 3 at Tower
1.1.9 Reconnect Link 3 at Tower
No noticeable operational change. Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.10 Disconnect Links 1&2 at Vault No noticeable operational change. System continues to operate on Link 3.
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.11 Initiate airfield lighting preset change
No noticeable operational change. All circuits turn on according to preset and control methodology tables.
1.1.12 Reconnect Links 1&2 at Vault No noticeable operational change. Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.13 Disconnect Links 1,2 & 3 at Tower System must go to failsafe condition within 1 minute according to Failsafe requirements.
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence.
1.1.14 Reconnect Links 1,2 & 3 at Tower System must return to normal system operation within 1 minute.
Verify event recorded in database. Event must be stamped with correct Link description and date/time of occurrence. 1.1.15 Initiate airfield lighting preset change
No noticeable operational change. All circuits turn on according to preset and control methodology tables.
10.6.2 Tower Preset Lighting Control Test This test must verify proper airport preset lighting control functionality. This test must be completed from the Tower GUI Preset Page and witnessed at the Vault and Remote Computer. All preset lighting settings must be programmed according to Preset Lighting Tables outlined in 10.3.2.
Test ID
Action ALCMS Results Database Results
Touchscreen Graphics Results 1.2.1 Select RWY 9, Day
1.2.2 Select >5 miles Visibility and Confirm
1.2.2 Select >5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.3 Select 3-5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.4 Select 2-3 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.5 Select 1-2 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.6 Select < 1 mile Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.7 Select Night
1.2.8 Select >5 miles Visibility and Confirm
1.2.8 Select >5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.9 Select 3-5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.10 Select 2-3 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.11 Select 1-2 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.12 Select < 1 mile Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI
1.2.13 Select RWY 27, Day
1.2.13 Select RWY 27, Day
1.2.14 Select >5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.15 Select 3-5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
1.2.14 Select >5 miles Visibility and Confirm
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.16 Select 2-3 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.17 Select 1-2 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.18 Select < 1 mile Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.19 Select Night
1.2.20 Select >5 miles Visibility and Confirm
1.2.20 Select >5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.21 Select 3-5 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.22 Select 2-3 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.23 Select 1-2 miles Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 1.2.24 Select < 1 mile Visibility and Confirm
All circuits must match brightness levels defined by Preset Table
Verify event recorded in computer database
Correct graphics illuminates on GUI 10.6.3 Tower Remote Control Test This test must verify proper individual airport lighting control functionality. This test must be completed from the Tower GUI Runway/Taxiway Page and witnessed at the Vault and Remote Computer. All individual control lighting settings must be programmed according to Circuit Control Methodology Table outlined in 10.3.3.
Test ID
Action Vault Control Outputs Response
Database Results Touchscreen Graphics Feedback Test 9-27 Edge 1.3.1 Select Step 1 and Confirm CCR ramps to Step-1 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.2 Select Step 2 and Confirm CCR ramps to Step-2 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.3 Select Step 3 and Confirm CCR ramps to Step-3 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.4 Select Step 4 and Confirm CCR ramps to Step-4 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.5 Select Step 5 and Confirm CCR ramps to Step-5 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.6 Select OFF and Confirm CCR ramps to Step- OFF
Verify event recorded in computer database
Correct graphics turns OFF on GUI 1.3.7 Select Step 5 and Confirm CCR ramps to Step-5 Verify event recorded in computer database
Correct graphics illuminates on GUI 1.3.8 Select OFF and Confirm CCR ramps to Step- OFF
Verify event recorded in computer database
Correct graphics turns OFF on GUI 1.3.9 Repeat for 9 TDZ 1.3.10 Repeat for 27 TDZ 1.3.11 Repeat for 9 REIL 1.3.12 Repeat for 9 PAPI 1.3.13 Repeat for 27 APPRCH 1.3.14 Repeat for 27 FLASHERS 1.3.15 Repeat for 27 PAPI 1.3.16 Repeat for TWY EDGE 1.3.17 Repeat for BEACON 1.3.18 Repeat for GENERATOR
10.6.4 Requesting and Granting Control This test must verify that the Vault and Remote Computer is capable of requesting and gaining control of the airport lighting system.
Test ID
Action Results
1.4.1 Request control from the Vault GUI using ALCMS program
1.4.1 Request control from the Vault GUI using ALCMS program
Verify standby message
1.4.2 At the Tower GUI, authorize control to the requesting station
Verify Tower GUI goes to “View Only Mode” and has the “Revoke” available 1.4.3 Make a preset lighting command change from the Vault GUI
Continue reading ↓ 120 of 188 passages shown