Attachment J-1 - FAA-E-3001.pdf

FAA-E-3001

REV_1

Department of Transportation

FEDERAL AVIATION ADMINISTRATION

PERFORMANCE SPECIFICATION

RUNWAY STATUS LIGHTS (RWSL) SYSTEM

DECEMBER 21, 2012

ATO-T Terminal Services, Surveillance Sector Federal Aviation Administration 800 Independence Avenue, SW

Washington, DC 20591

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

REV_1

REVISIONS SUMMARY PAGE

Change Letter Description of Change Changed By Approved By 1 Minor edits to overview section.

Corrected reference to match contract, changed FAA-E-2761A to rev C level.

Updated R199 and R200 to include FAA-STD-019e section 4.2 as per Phase II spec change ECP.

E. Chartier M. Scheufler

B. Halabi

REV 1

12/21/2012 i

TABLE OF CONTENTS

1. Scope

1.1 Scope

1.2 System Overview

1.2.1 Runway Entrance Lights (RELs)

1.2.2 Takeoff Hold Lights (THLs)

2. Applicable Documents

2.1 FAA Documents

2.2 Non-FAA Government Documents

2.3 Non-Government Documents

3. Requirements

3.1 RWSL Processor Requirements

3.1.1 Surveillance Processing

3.1.2 REL State Determination

3.1.3 THL State Determination

3.1.4 FLS Commands

3.1.5 RWSL Processor Latency

3.2 RWSL FLS Requirements

3.3 RWSL System Requirements

3.3.1 Light Accuracy

3.3.2 Capacity

3.3.3 Automatic Function Requirements

3.3.4 Modes of Operation

3.3.5 Cab Control Panel

3.3.6 Maintenance Terminal

3.3.7 Data Recording

3.3.8 Playback

3.3.9 Data Reprocessing

3.3.10 Maintenance Concept

3.3.11 RMA

3.3.12 System Recovery

3.3.13 Electrical and Environmental

3.3.14 Mechanical

3.3.15 Communications

3.3.16 Security

3.3.17 Service Life

3.3.18 Remote 2nd Level Engineering Access

4. Verification

5. Reserved

6. Notes

6.1 Glossary

6.2 Acronyms

12/21/2012 ii

This Page Intentionally Left Blank

12/21/2012 1

1. SCOPE

1.1 Scope

This specification establishes the performance requirements of the Runway Status Lights (RWSL) System.

1.2 System Overview

The purpose of the RWSL System is to reduce the number of runway incursions without interfering with normal airport operations. The RWSL System reduces runway incursions by indicating to pilots and vehicle operators that it would be in conflict with an aircraft if it crossed the hold line or begins its takeoff. Runway status lights display critical, time-sensitive safety status information directly to pilots and vehicle operators via in pavement lights giving them an immediate indication of potentially unsafe situations. Runway status lights indicate runway status only; they do not indicate clearance.

The RWSL System uses computer processing of integrated surface and terminal surveillance information to establish the presence and motion of aircraft and surface vehicles on or near the runways. The system illuminates red runway-entrance lights (RELs) if the runway is unsafe for entry or crossing, and illuminates red takeoff-hold lights (THLs) if the runway is unsafe for departure. The system extinguishes the lights automatically as appropriate when the runway is no longer unsafe.

The RWSL System consists of an RWSL processor and a Field Lighting System (FLS). The RWSL processor receives surveillance data of aircraft and vehicles on or near the airport surface from the ASDE-X surface surveillance system. The RWSL processor uses this surveillance data to determine when to activate and deactivate the RELs and THLs. These light commands are sent to the RWSL FLS. The FLS includes a Light Computer (LC), in pavement light fixtures, and all light system circuitry. The FLS receives the light commands and illuminates and extinguishes the lights as commanded by the RWSL processor. The system will automatically determine runway configurations and will adjust the activation and deactivation of RELs and THLs accordingly.

The system will automatically adjust light intensity according to time of day. The functions of the RWSL system and how they are partitioned among the two key subsystems is depicted in Figure 1.

Surveillance Inputs •Surface Radar •Terminal Radar •Multilateration •Terminal Automation

RWSL Processor •Surveillance Processing •REL State Determination •THL State Determination •FLS Commands •System Control and Monitoring

RWSL FLS

•Light Command Processing •REL/THL Illuminate/Extinguish •Light Intensity Control •Equipment Status Monitoring

RWSL System

Figure 1 RWSL System

12/21/2012 2

Air Traffic supervisors control the system using a Cab Control Panel (CCP). Control functions will include light intensity control (override of automatic intensity adjustment) separately by RELs and THLs. Status indication will be provided including system online/offline and if communications from the CCP to the system are working. A separate hard kill switch will be provided to deactivate all RWSL fixtures in the event of a system malfunction.

The RWSL System includes a maintenance terminal for Technical Operations personnel to control the RWSL System, to notify when maintenance is required, and to assist with identification of failed LRUs. The maintenance terminal also provides all tools and controls necessary to configure and optimize the system.

1.2.1 Runway Entrance Lights (RELs)

A runway incursion may occur when an aircraft or vehicle enters the runway when it is occupied by another aircraft. This might occur if the pilot or vehicle operator misunderstands his position on the airport movement area or if a controller gives a clearance without realizing the runway is occupied. The RWSL System prevents this situation by detecting the presence of the occupying traffic and automatically illuminating RELs at the entry point onto the runway.

RELs illuminate red when the runway is unsafe to enter; they are off otherwise. The RWSL System provides each high-speed operation, whether a departure or a landing, a safety zone in front of the aircraft. RELs for runway entrances that lie within that safety zone are illuminated to indicate to other aircraft or vehicles that it is unsafe to enter the runway at that position. In order not to interfere with the normal flow of airport traffic, the RELs are extinguished just before the high-speed operation clears the intersection, when it is safe to start motion into the intersection, allowing controllers to use anticipated separation. The presence of aircraft or vehicles at the intersecting taxiways or runways is not required to illuminate the RELs; they are illuminated for each high speed operation (departure or landing) whether or not other aircraft or vehicles are present.

1.2.2 Takeoff Hold Lights (THLs)

A runway incursion would occur if an aircraft attempts to take off when an aircraft or vehicle is occupying the runway. This might occur if the deviating pilot or vehicle operator misunderstands his position on the airport movement area or if a controller gives a takeoff clearance without realizing the runway is occupied. The RWSL System prevents this situation by detecting the presence of the occupying traffic and automatically illuminating THLs at the end of the runway where the departing aircraft begins its takeoff acceleration. Illumination of the THL will indicate to the pilot that runway is unsafe for departure.

THLs illuminate red when the runway is unsafe for departure because it is currently occupied or about to be occupied by entering or crossing traffic; they are off otherwise. In order not to interfere with the normal flow of airport traffic, the THLs are extinguished just before the blocking or crossing traffic clears the runway, when it is safe for the departure to commence, allowing controllers to use anticipated separation. THLs are only illuminated when an aircraft turns into position and hold on a runway and another aircraft or vehicle occupies the runway.

2. APPLICABLE DOCUMENTS

The following documents of the exact issue shown form a part of this specification to the extent specified herein. In the event of a conflict between the document referenced herein and the

12/21/2012 3 contents of this specification, the contents of this specification shall be considered the superseding requirement.

2.1 FAA Documents

1. Interface Design Document for the ASDE-X Program, Version 11, August 10, 2007.

2. RWSL Processor to Field Lighting System Interface Control Document, March 17, 2008.

3. FAA-E-3002, Performance Specification, RWSL Field Lighting System (FLS), December 21, 2012.

4. FAA Advisory Circular 150/5345-56, Specification for L-890 Airport Lighting Control and Monitoring System (ALCMS).

5. FAA-G-2100H, FAA Specification, Electronic Equipment, General Requirements.

6. FAA-STD-019E, FAA Standard for Lightening and Surge Protection, Grounding, Bonding and Shielding Requirements for Facilities and Electronic Equipment.

7. FAA-C-1217F, Electrical Work, Interior.

8. FAA-E-2761C, Cable, Fiber Optic, Multimode and Single-Mode, Multifiber.

9. FAA Order 1600.6E, Facility Security Policy.

10. FAA Order 1370.82A, Information Systems Security Program.

11. FAA Order 1600.1E, Personnel Security.

12. FAA Order 1600.72, Contractor and Industrial Security Program.

13. FAA Order 1600.73, Contractor and Industrial Security Operating Procedures.

14. FAA Advisory Circular 150/5345-10F, Specification for Constant Current Regulators and

Regulator Monitors, 6/24/2005.

2.2 Non-FAA Government Documents

None.

2.3 Non-Government Documents

None.

3. REQUIREMENTS

3.1 RWSL Processor Requirements

3.1.1 Surveillance Processing

3.1.1.1 The RWSL processor shall [R1] obtain surveillance, status, and operational configuration data from the ASDE-X System in accordance with reference [1].

3.1.1.2 The RWSL processor shall [R2] provide tracking, fusion, and target verification as needed to meet the light accuracy requirements of this specification.

3.1.2 REL State Determination

The RWSL processor shall [R3] determine the appropriate activation and deactivation of the RELs based on surveillance, status, and operational configuration data provided by the ASDE-X System.

3.1.2.1 REL Activation

12/21/2012 4

3.1.2.1.1 The RWSL processor shall [R4] activate RELs at individual intersections once an aircraft arriving to the runway is within an adaptable parameter distance or adaptable parameter time from the arrival end of the runway for each of three (3) aircraft approach speed ranges adapted separately for both runway directions.

3.1.2.1.2 The RWSL processor shall [R5] activate individual RELs that are located an adaptable parameter time ahead of an aircraft moving on the runway once the aircraft exceeds an adaptable parameter velocity.

3.1.2.1.3 The RWSL processor shall [R6] activate all RELs ahead of an aircraft moving on the runway once the aircraft exceeds an adaptable parameter velocity and adaptable parameter acceleration. The RWSL processor shall [R7] activate all RELs ahead of an aircraft moving on the runway once the aircraft exceeds a second higher adaptable parameter velocity.

3.1.2.1.4 The RWSL processor shall [R8] activate or maintain RELs in the activated state ahead of an aircraft that has aborted its departure based on an adaptable parameter velocity decrease.

The RWSL processor shall [R9] activate or maintain RELs in the activated state ahead of an aircraft that has aborted its departure based on an adaptable parameter acceleration decrease for an adaptable parameter time.

3.1.2.1.5 The RWSL processor shall [R10] activate RELs that are located an adaptable parameter time ahead of a vehicle moving on the runway once the vehicle exceeds an adaptable parameter velocity.

3.1.2.1.6 The RWSL processor shall [R11] activate individual RELs that are located an adaptable parameter time ahead of an unknown target type moving on the runway once the target exceeds an adaptable parameter velocity.

3.1.2.1.7 The RWSL processor shall [R12] activate all RELs ahead of an unknown target type moving on the runway once the target exceeds an adaptable parameter velocity and adaptable parameter acceleration for an adaptable parameter time.

3.1.2.2 REL Deactivation

3.1.2.2.1 The RWSL processor shall [R13] maintain RELs at individual intersections in the activated state for situations with multiple targets until the deactivation criteria for all targets effecting the intersection have been met.

3.1.2.2.2 The RWSL processor shall [R14] deactivate all RELs that were activated by an aircraft arriving to the runway if that aircraft aborts its approach.

3.1.2.2.3 The RWSL processor shall [R15] deactivate RELs at individual intersections once the aircraft or vehicle moving on or approaching to the runway is within an adaptable parameter time or an adaptable parameter distance from the center of the intersection adaptable separately for each intersection and both runway directions.

3.1.2.2.4 The RWSL processor shall [R16] deactivate all RELs in front of a landing aircraft that decelerates below an adaptable parameter velocity, except for those intersections that will be reached within an adaptable parameter time.

12/21/2012 5

3.1.2.2.5 The RWSL processor shall [R17] deactivate all RELs in front of an aircraft or vehicle once it begins to exit the runway at an intersection based on an parameter heading adapted separately for each intersection and both runway directions.

3.1.2.2.6 The RWSL processor shall [R18] deactivate all RELs in front of an aircraft once it decelerates below an adaptable parameter velocity.

3.1.2.2.7 The RWSL processor shall [R19] deactivate all RELs in front of a vehicle once it decelerates below an adaptable parameter velocity.

3.1.2.2.8 The RWSL processor shall [R20] deactivate all RELs in front of an unknown track type once it decelerates below an adaptable parameter velocity.

3.1.2.2.9 The RWSL processor shall [R21] maintain a REL in the activated state if an aircraft arriving to the runway will activate that REL within an adaptable parameter time or adaptable parameter distance.

3.1.2.2.10 The RWSL processor shall [R22] deactivate RELs ahead of a departing aircraft once the departing aircraft has achieved a positive rate of climb with required accuracy of ± 3 seconds 90% and ± 5 seconds 99%. The RWSL processor shall [R23] deactivate all RELs ahead of a departing aircraft once the departing aircraft is above an adaptable parameter height.

3.1.2.2.11 [Requirement R24 deleted].

3.1.2.2.12 The RWSL processor shall [R25] deactivate all RELs ahead of any aircraft or vehicle once it leaves the boundary of the runway surface for an adaptable parameter time.

3.1.3 THL State Determination

The RWSL processor shall [R26] determine the appropriate activation and deactivation of the THLs based on surveillance, status, and operational configuration data provided by the ASDE-X System.

3.1.3.1 General THL Operation

3.1.3.1.1 The RWSL processor shall [R27] provide two THL arrays per runway direction.

3.1.3.1.2 The RWSL processor shall [R28] provide a unique THL safety region and takeoff hold region for each THL array.

3.1.3.1.3 The RWSL processor shall [R29] uniquely define each THL safety region boundary.

The THL safety region boundary shall [R30] start from an adaptable parameter distance from the end of the runway. The THL safety region boundary shall [R31] end from an adaptable parameter distance from the same end of the runway. The THL safety region boundary shall [R32] be from an adaptable parameter distance from the center of the runway.

3.1.3.1.4 The RWSL processor shall [R33] uniquely define each THL safety region boundary per intersection by an adaptable parameter distance from the center of the runway for each intersection direction.

3.1.3.1.5 The RWSL processor shall [R34] uniquely define each takeoff hold region boundary.

The takeoff hold region boundary shall [R35] start from an adaptable parameter distance from the

12/21/2012 6 end of the runway. The takeoff hold region boundary shall [R36] end from an adaptable parameter distance from the same end of the runway. The takeoff hold region boundary shall [R37] be from an adaptable parameter distance from the center of the runway.

3.1.3.2 THL Safety Region Criteria

3.1.3.2.1 The RWSL processor shall [R38] declare a THL safety region occupied until all aircraft and vehicles in the THL safety region have completely exited or are projected to exit the THL safety region. The RWSL processor shall [R39] provide adaptable heading and time parameters to project aircraft or vehicles out of each THL safety region. The adaptable exit projection time and heading parameters shall [R40] be provided separately for each intersection. The adaptable exit projection time and heading parameters shall [R41] be provided separately for each runway direction.

3.1.3.2.2 The RWSL processor shall [R42] declare a THL safety region unoccupied if the THL safety region is solely occupied by a departing aircraft and that aircraft has achieved a positive rate of climb with required accuracy of ± 3 seconds 90% and ± 5 seconds 99%.

3.1.3.2.3 The RWSL processor shall [R43] declare a THL safety region unoccupied if the THL safety region is solely occupied by a departing aircraft and that aircraft is above an adaptable parameter height. The RWSL processor shall [R43.1] declare a THL safety region unoccupied if the THL safety region is solely occupied by a departing aircraft that meet adaptable velocity and acceleration parameters. The adaptable velocity and acceleration parameters shall [R43.2] be individually adaptable per THL.

3.1.3.2.4 The RWSL processor shall [R44] declare a THL safety region occupied if the THL safety region was declared unoccupied by a departing aircraft and that aircraft aborts its departure.

3.1.3.3 THL Takeoff Hold Region Criteria

3.1.3.3.1 The RWSL processor shall [R45] declare a takeoff hold region occupied when an aircraft is located within the takeoff hold region with a direction aligned within an adaptable parameter heading from the takeoff direction and an adaptable parameter speed. If the aircraft speed drops below an adaptable parameter, the RWSL processor shall [R46] set the target heading to be aligned with the takeoff direction.

3.1.3.3.2 The RWSL processor shall [R47] declare a takeoff hold region occupied until all aircraft in the takeoff hold region have completely exited or are projected to exit the takeoff hold region (except the departure side of the region; projection out of this side should not be allowed). The RWSL processor shall [R48] provide adaptable heading and time parameters to project aircraft out of each takeoff hold region.

3.1.3.4 THL Activation Criteria

3.1.3.4.1 The RWSL processor shall [R49] activate a THL array when both the associated THL safety region and associated takeoff hold region are declared occupied.

3.1.3.4.2 The RWSL processor shall [R50] activate a THL array when the associated takeoff hold region is declared occupied and the REL activation criteria for the intersection located at an intersecting runway are met.

12/21/2012 7

3.1.3.5 THL Deactivation Criteria

3.1.3.5.1 The RWSL processor shall [R51] deactivate a THL array when either the associated THL safety region or the associated takeoff hold region is declared unoccupied. The RWSL processor shall [R51.1] deactivate a THL array that was activated by the requirement R50 when either the takeoff hold region is declared unoccupied or the REL deactivation criteria for the intersection located at the intersecting runway are met.

3.1.3.6 REL and THL Closed Runway Behavior

3.1.3.6.1 The RWSL processor shall [R52] determine when a runway is set to “closed” by the ASDE-X system and command the RELs and THLs as follows.

3.1.3.6.2 The RWSL processor shall [R53] set RELs on or off on closed runways, adaptable separately for each intersection. The RWSL processor shall [R54] set THLs on, off, or to activate when an aircraft meets the takeoff hold region occupied criteria, adaptable separately for each THL array.

3.1.3.6.3 The RWSL processor shall [R55] revert to normal RWSL operations when a runway is reopened based on operational configuration data provided by the ASDE-X System in accordance with reference [1].

3.1.4 FLS Commands

3.1.4.1 The RWSL processor shall [R56] send control signals to the RWSL FLS to command the REL and THL activations and deactivations in accordance with the reference [2].

3.1.5 RWSL Processor Latency

3.1.5.1 The RWSL processor latency shall [R57] not exceed 500 milliseconds.

3.2 RWSL FLS Requirements

The RWSL FLS Requirements are contained in reference [3].

3.3 RWSL System Requirements

The requirements in this section pertain to the entire RWSL System and all equipment comprising the RWSL System, including the FLS.

3.3.1 Light Accuracy

3.3.1.1 REL Accuracy

3.3.1.1.1 The RWSL system shall [R58] limit REL missed detections to less than 0.167% of operations.

3.3.1.1.2 The RWSL system shall [R59] limit REL false activations to less than 0.05% of operations.

3.3.1.1.3 The RWSL system shall [R60] limit REL light flashes to less than 0.2% of operations.

3.3.1.2 THL Accuracy

12/21/2012 8

3.3.1.2.1 The RWSL system shall [R61] limit THL missed detections to less than 0.167% of total operations for the associated THL array.

3.3.1.2.2 The RWSL system shall [R62] limit THL missed detections when real aircraft are located in the THL safety region to less than 0.02% of operations for the associated THL array.

3.3.1.2.3 The RWSL system shall [R63] limit THL false activations rate to less than 0.05% of operations for the associated THL array.

3.3.1.2.4 The RWSL system shall [R64] limit THL false activations when real aircraft are located in the takeoff hold region to less than 0.02% of operations for the associated THL array.

3.3.2 Capacity

3.3.2.1 The RWSL system shall [R65] process the track load corresponding to 200 real targets without exceeding 50% CPU loading for each CPU in the system.

3.3.2.2 When the RWSL System reaches an overload condition, the RWSL system shall [R66] deactivate all lights, transition the system to offline, and indicate the overload condition on the maintenance terminal.

3.3.2.3 The RWSL system shall [R67] control from 1 to 20 THL arrays, 1 to 60 REL arrays, and 1 to 10 runways.

3.3.3 Automatic Function Requirements

3.3.3.1 The RWSL system shall [R68] automatically adjust all field light fixture intensities to adaptable night and day settings.

3.3.3.2 The RWSL system shall [R69] adjust to changes in the directional flow of traffic without user input.

3.3.3.3 The RWSL system shall [R70] synchronize the internal clock of all computers contained in the system such that each internal clock does not vary more than 1 second from ASDE-X system time.

3.3.4 Modes of Operation

3.3.4.1 The RWSL system shall [R71] provide an online mode. The RWSL system shall [R72] inhibit configuration changes while in on-line mode.

3.3.4.2 The RWSL system shall [R73] provide an offline mode. The RWSL System shall [R73.1] transition to offline when the kill switch is activated. The RWSL System shall [R73.2] remain online if some of the system components have been taken offline. The RWSL System shall [R73.3] transition to offline if all of the system components have been taken offline. The RWSL system shall [R74] determine when the ASDE-X System is not in operational mode and transition the RWSL System to offline. The RWSL system shall [R75] determine when the ASDE-X System returns to operational mode and transition the RWSL System to online. When in offline mode, the RWSL system shall [R76] prevent illumination of any REL or THL light fixtures. The RWSL system shall [R77] indicate the offline state on the maintenance terminal and cab control panel. The RWSL System shall [R78] transition to offline if the interface to the ASDE-X system

12/21/2012 9 fails. The RWSL System shall [R79] transition to offline if the interface to the FLS has failed or if the LC has failed. The RWSL System shall [R79.1] automatically transition back to online when the interface to FLS is restored and the FLS has no critical faults.

3.3.4.3 The RWSL system shall [R80] provide a rain mode. The RWSL system shall [R81] automatically switch to rain mode when ASDE-X is switched to rain mode. While in rain mode, the false activation requirements of paragraph 3.3.1 shall [R82] be met for all aircraft and vehicles. While in rain mode, the missed detection and false activation requirements of paragraph

3.3.1 shall [R83] be met for transponder equipped aircraft and vehicles. The RWSL system shall [R84] indicate to the RWSL maintenance terminal that the system is in rain mode. The RWSL system shall [R85] log occurrences of rain mode.

3.3.5 Cab Control Panel

The RWSL System shall [R86] provide system control capability in each ATCT cab.

[Requirement R87 deleted]. The cab control panel shall [R88] comply with paragraphs 4.1, 4.2, 4.3.1, 4.3.2 (except paragraph e), 4.5, 4.6, and 4.7 of reference [4].

3.3.5.1 The cab control panel shall [R89] set the power (light intensity) of RELs and THLs separately. The steps shall [R90] include intensity levels 1, 2, 3, 4, and 5 in accordance with reference [14]. The control panel shall [R91] indicate that an intensity change command has been accepted.

3.3.5.2 The cab control panel shall [R92] indicate the current REL and THL intensity levels.

3.3.5.3 The cab control panel shall [R93] indicate the operational status (online or offline) of the RWSL System.

3.3.6 Maintenance Terminal

3.3.6.1 The RWSL maintenance terminal shall [R94] include a display, keyboard, and user input device. The RWSL maintenance terminal shall [R95] be collocated in the ATCT equipment room with the RWSL processor and FLS Light Computer.

3.3.6.2 The RWSL maintenance terminal shall [R96] display surveillance data on a map of the airport movement area and approach paths and the state of all RELs and THLs, and all THL safety regions and takeoff hold regions. The display shall [R97] pan and zoom to provide a user customized view.

3.3.6.3 Performance monitoring

3.3.6.3.1 The RWSL System shall [R98] automatically monitor key system performance parameters. The RWSL System shall [R99] display key system performance parameters on the maintenance terminal. All key performance parameters shall [R100] be checked every status cycle.

3.3.6.3.2 Key performance parameters shall [R101] include RWSL System status. Key performance parameters shall [R102] include status of each LRU including all FLS LRUs. Key performance parameters shall [R103] include current and loop voltage of each FLS light circuit.

Key performance parameters shall [R104] include available data recording disk space. Key performance parameters shall [R105] include CPU usage. Key performance parameters shall

12/21/2012 10

[R106] include the status of each communications link throughout the system including ASDE-X to RWSL, RWSL processor to LC, LC to each MLC, LC to each CCR and MLC to each ILC.

3.3.6.3.3 The RWSL System status, diagnostic, and fault reports shall [R107] indicate the source of the report (LRU) and the system time that the report was generated. The RWSL System status, diagnostic, fault and security audit reports shall [R107.1] be stored in logs that are viewable, sortable, and searchable from the maintenance terminal and remote maintenance terminal. The RWSL System status, diagnostic, fault, and security audit logs shall [R107.2] be exportable to external media.

3.3.6.3.4 RWSL System status reports shall [R108] provide information on the operational status of an LRU or subsystem. Status reports shall [R109] be generated at an adaptable periodic frequency down to once per second.

3.3.6.3.5 RWSL System diagnostic reports shall [R110] indicate the most probable failed Line Replaceable Unit (LRU). The RWSL System diagnostic reports shall [R111] be generated after detection of a failure or upon request from the maintenance terminal.

3.3.6.3.6 RWSL System fault reports shall [R112] provide information on fault conditions for hardware and software parameters vital to the subsystem's performance. These reports shall [R113] be generated following detection of a failure.

3.3.6.4 The RWSL system shall [R114] log all occurrences of LRU failures.

3.3.6.5 The RWSL system shall [R115] calculate and display FLS lamp life statistics on the maintenance terminal. FLS lamp life statistics shall [R116] include lamp on time and activation cycles per light fixture. FLS lamp life statistics shall [R117] be updated no less than daily. FLS lamp life statistics shall [R118] include mean and standard deviation of all lamps.

3.3.6.5.1 The RWSL System shall [R119] monitor ILC switching time and send a fault report if ILC switching time exceeds an adaptable parameter time for more than an adaptable parameter ILC switching cycles.

3.3.6.5.2 The RWSL System shall [R120] provide overheat sensors in each separate enclosed cabinet to indicate when the temperature exceeds the maximum safe operating temperature for the equipment within the cabinet. The RWSL System shall [R121] generate a fault report when an adjustable parameter temperature is exceeded. The RWSL System shall [R122] automatically shut down if a higher adjustable parameter temperature is exceeded.

3.3.6.5.3 The RWSL System shall [R123] include additional diagnostic tools or procedures beyond performance monitoring if required to meet the system MTTR.

3.3.6.6 Control of the FLS

3.3.6.6.1 The RWSL maintenance terminal shall [R124] command the entire system to change between online and offline states. The RWSL maintenance terminal shall [R125] command individual runways to change between online and offline states. The RWSL maintenance terminal shall [R126] command individual circuits to change between online and offline states. The RWSL maintenance terminal shall [R127] command individual REL and THL arrays to change between online and offline states.

12/21/2012 11

3.3.6.6.2 When the RWSL System or a component of the system is offline, the RWSL maintenance terminal shall [R128] provide manual light control of light groups and individual light fixtures. Manual light control for all lights on a circuit shall [R129] be provided. Manual light control for all lights on a runway shall [R130] be provided. Manual light control for individual THL and REL arrays shall [R131] be provided. Manual light control for individual light fixtures shall [R132] be provided.

3.3.6.6.3 The RWSL maintenance terminal shall [R133] manually control the intensity of each individual light circuit.

3.3.6.7 Data Analysis and Optimization Tools

3.3.6.8 The RWSL maintenance terminal shall [R134] provide a graphical user interface to view and edit all adaptable RWSL System parameters. The RWSL maintenance terminal shall [R134.1] allow a site technician to load an adaptation file.

3.3.6.8.1 The RWSL maintenance terminal shall [R135] provide a user interface for all necessary maintenance user interaction with the FLS. The RWSL maintenance terminal shall [R136] provide a means for the user to create and update the configuration of light group identification numbers to physical device identification numbers while the RWSL System is in the off-line state.

3.3.6.9 The RWSL maintenance terminal shall [R137] provide data analysis tools that extract performance measures on recorded data files. The performance measures shall [R138] include LCA REL Analyzer, LCA Flash Analyzer, LCA THL Analyzer.

3.3.7 Data Recording

3.3.7.1 The RWSL System shall [R139] record and timestamp RWSL System data for a period of 45 days. The most recent 45 days shall [R140] be available on the system. Data older than 45 days shall [R141] be automatically overwritten. The following data shall [R142] be recorded:

• All surveillance data input from the ASDE-X System (only the surveillance messages used by the RWSL System).

• ASDE-X status messages

• RWSL target update message

• Operational status messages

• Cab control panel inputs

• All messages sent to the FLS

• All messages from the FLS

• RWSL processor adaptation data

• RWSL System status, fault and diagnostic reports

• Performance monitoring data

• Configuration changes

3.3.7.2 [Requirement R143 deleted].

3.3.7.3 Data recording shall [R144] be independent from the operational mode. The data recording and playback functions shall [R145] provide the recording and playback capabilities without loss in fidelity of RWSL System outputs. The data recording format shall [R146] include headers and other documentation to allow the data to be interpreted. The recorded data shall

12/21/2012 12

[R147] include a unique record number. The record number shall [R148] rollover less than once per 45 days. All recorded data shall [R149] be time-stamped with a resolution of at least 0.01 seconds.

3.3.7.4 The RWSL System shall [R150] provide a means of storing the recorded files on standard removable recording media.

3.3.7.5 All data recorded shall [R151] also be sent to a communications port.

3.3.8 Playback

3.3.8.1 The RWSL System shall [R152] play back the recorded data. The playback function shall [R153] display surveillance data and REL and THL activation/deactivation on a map of the airport. The playback function shall [R154] be accomplished both on the RWSL System and on a stand alone PC. The RWSL System shall [R155] provide a means to playback segments of recorded data in variable time frames, from a minimum of one (1) minute up to at least four (4) hours. Playback data shall [R156] be replayed at normal, 1/16x, 1/8x, 1/4x, 1/2x, 2x, 4x, 8x, 16x speed.

3.3.8.2 During playback, the RWSL System shall [R157] enable or suppress light commands to the FLS.

3.3.9 Data Reprocessing

3.3.9.1 The RWSL System shall [R158] accept recorded ASDE-X surveillance data as input for reprocessing. The RWSL System shall [R158.1] accept RWSL recorded data, either recorded locally or input from another system, as input for reprocessing. The RWSL System shall [R158.2] reprocess the recorded data using a new parameter set from a time parameter start to a time parameter end, creating a new recorded data file with new REL and THL activation and deactivation without any visual display at high speed.

3.3.9.2 The RWSL System shall [R159] reprocess and playback the recorded data using a new parameter set from a time parameter start to a time parameter end, creating a new recorded data file with new REL and THL activation and deactivation at a playback speed that is real time, faster, or slower and allow the playback to be paused and restarted or stopped. The playback function shall [R160] display surveillance data and REL and THL activation/deactivation on a map of the airport.

3.3.10 Maintenance Concept

The RWSL System shall [R161] support a two-level maintenance approach, site level maintenance and depot-level maintenance.

3.3.10.1 Site level maintenance activities shall [R162] be performed on the equipment installed in its operating environment and will include periodic and corrective maintenance.

3.3.10.1.1 Periodic maintenance of the RWSL System shall [R163] be required no more than four

(4) times per year and require no more than four (4) hours and one person to perform, with the exception of visual inspections which may be required more frequently and may require two persons.

12/21/2012 13

3.3.10.1.2 Corrective site maintenance shall [R164] consist of removal and replacement of failed line replaceable units (LRUs) to restore service.

3.3.10.2 Depot-level maintenance shall [R165] consist of repairing failed, repairable LRUs that have been removed in the field, including repair of failed shop replaceable unit (SRU). Depot-level repair includes exchange and repair identified support and test equipment.

3.3.11 RMA

3.3.11.1 The RWSL System mean time to repair (MTTR) shall [R166] not exceed 30 minutes for any single maintenance action, including time required for fault localizing, repair, test and restoration to service. The maximum time for any single repair action, including time required for fault localizing, repair, test and restoration to service, shall [R167] not exceed 120 minutes. These times do not include administrative and logistical time, which is time spent on activities (such as dispatch time, travel time, paperwork, etc.) not within the control of the RWSL System or its supplier. Lamps are considered consumables and should not be counted as a failure in the RMA analysis.

3.3.11.2 The RWSL System mean time between failures (MTBF) shall [R168] be greater than or equal to 499.5 hours.

3.3.11.3 The RWSL System inherent availability (Ai) shall [R169] be greater than or equal to 0.999, excluding ASDE-X system downtime.

3.3.11.4 The RWSL System shall [R170] not require interruption of service or de-soldering for the replacement of components that are by design consumable or subject to high failure rate.

3.3.12 System Recovery

3.3.12.1 The RWSL System shall [R171] recover full service in less than or equal to 5 minutes after power loss. The RWSL processor shall [R172] suppress light control commands to the FLS until the system has fully recovered and returned to online status.

3.3.12.2 For unplanned interrupts, the RWSL System shall [R173] recover to the same online/offline state of the components of the system that were active prior to the interruption.

[Requirement R174 deleted]

3.3.12.3 [Requirement R175 deleted] For interrupts involving a restart of a software application, the system shall [R176] recover to the same online/offline state of the components of the system that were active prior to the interrupt.

3.3.12.4 All recovery events shall [R177] be logged.

3.3.12.5 Operation of all redundant elements shall [R178] occur without degrading the performance of the elements. All such transitions shall [R179] be controlled automatically by the performance monitoring system, with manual override possible from the RWSL maintenance terminal. When an alternate element is placed online, congruency of output data shall [R180] be maintained without requiring adjustment of the RWSL System.

3.3.12.6 When the monitoring system detects a critical failure, the RWSL System shall [R181] transition to offline.

12/21/2012 14

3.3.12.7 When the monitoring system detects a recoverable system fault, the monitor shall [R182] take action to transfer to the redundant equipment (if required to meet the RMA requirements). At the same time, a message shall [R183] be displayed on the maintenance terminal indicating that a transfer action is in process and that system restoration is imminent. If, after transfer, proper system operation cannot be restored, the failure shall [R184] be treated as a non-recoverable fault.

3.3.13 Electrical and Environmental

3.3.13.1 Operating Environment

The RWSL equipment located in the ATCT shall [R185] operate in Type I environmental conditions as defined in FAA-G-2100H Standards, Section 3.2.1. Exceptions to the environmental requirements are the elevation shall [R186] be from 0 to 6,000 feet and the lower relative humidity limit shall [R187] be 40%.

3.3.13.2 Electrical Requirements

3.3.13.2.1 All RWSL equipment to be located in the ATCT shall [R188] meet all requirements necessary to receive power from the critical bus, including inrush current and harmonic distortion parameters in accordance with FAA-G-2100H Sections 3.1.1.3, and 3.1.1.5, NFPA 70, and FAA-

STD-019E.

3.3.13.2.2 The RWSL equipment located in the shelters/vaults and on the airfield shall [R189] perform fully in accordance with this specification when the furnished AC power varies by as much as 10% from nominal line voltage, and by as much as 5% from nominal frequency. The RWSL equipment shall [R190] not sustain damage to or alteration of its equipment, nor cause false operation or false output, when AC power is outside its normal limits of operation, including total loss of power. If proper operations cannot be maintained due to power conditions, the RWSL equipment shall [R191] transition to offline. The RWSL equipment shall [R192] operate without degradation of performance in the presence of partial or complete loss of the line voltage(s) for up to 20 ms at a time. Automated means for startup after such stoppage shall [R193] be provided. The RWSL equipment electrical features shall [R194] meet the electrical power source requirements of 3.1.1.2, 3.1.1.3, 3.1.1.4, 3.1.1.5-a through 3.1.1.5-d, and 3.1.1.6 in FAA-G-2100H. The power distribution design and implementation shall [R195] be in accordance with National Electric Code and NFPA-70.

3.3.13.2.3 All RWSL equipment shall [R196] be protected from electrical transients as specified in FAA-G-2100H paragraph 3.1.1.6 (f.).

3.3.13.2.4 Protective devices shall [R197] be provided as necessary to prevent damage to the equipment from surges on either the AC power lines or the signal/communications cables. The devices shall [R198] withstand repeated surges without damage or change in operating characteristics. The protective devices shall [R199] be in accordance with Paragraphs 4.2 and 4.3 of FAA-STD-019E.

3.3.13.2.5 RWSL equipment grounding, shielding, bonding and transient protection shall [R200] be in accordance with paragraphs 4.1, 4.2, and 4.3 of FAA-STD-019E, FAA-C-1217, and sections 8 and 9 of IEEE 1100-1996. If earth and AC power grounds are not available, the vendor shall [R201] furnish grounds as required by FAA-STD-019E.

3.3.13.2.6 The RWSL System grounding design shall [R202] contain two types of grounding systems:

12/21/2012 15

� Multipoint grounding system that bonds together all cabinets, frames and signal returns.

� Branch Circuit Fault-Safety for AC power grounds in accordance with NFPA-70, and

FAA-STD-019E.

3.3.13.2.7 All RWSL System batteries shall [R203] comply with paragraph 3.3.1.4.1 of FAA-G- 2100H, except for board-based workstation/PC batteries.

3.3.13.2.8 All circuit breakers shall [R204] comply with paragraph 3.3.1.4.2 of FAA-G-2100H.

3.3.13.2.9 All fuses, fuse holders and associated hardware provided with the RWSL equipment shall [R205] comply with paragraph 3.3.1.4.4 of FAA-G-2100H.

3.3.13.2.10 All AC power cables and wiring within the RWSL equipment shall [R206] be isolated from sensitive circuits. Cabling shall [R207] include all junction boxes, fittings and distribution equipment (switches and circuit breakers) from the FAA power source to the RWSL equipment primary power panel. Power connectors shall [R208] be compliant with paragraph

3.3.1.4.3.3 of FAA-G-2100H.

3.3.13.2.11 Test points and associated switches for use in measuring RWSL equipment power supply output voltages and currents shall [R209] be furnished.

3.3.13.2.12 [Requirement R210 deleted]. The RWSL system shall [R211] conform to Paragraph

3.3.5 of FAA-G-2100H.

3.3.14 Mechanical

3.3.14.1 All RWSL equipment located in the ATCT shall [R212] be placed in a single cabinet or rack.

3.3.14.2 All RWSL equipment shall [R213] meet the mechanical requirements of FAA-G-2100H paragraphs 3.1.2. All RWSL equipment shall [R214] meet the maintainability requirements of FAA-G-2100H paragraph 3.2.4.

3.3.14.3 Identification of RWSL equipment shall [R215] be in accordance with FAA-G-2100H, Paragraph 3.3.3.

3.3.14.4 The cabinets and racks frames shall [R216] not exceed a height of 72 inches (1.83 meters), a width of 36 inches (0.91 meters) and a depth of 38 inches (0.97 meters).

3.3.14.5 Removal of equipment or modules or interchanging of equipment modules shall [R217] not cause any deformation to the cabinets and racks. Removable components shall [R218] not exceed the weight limits specified in Paragraph 3.3.6.3 of FAA-G-2100H so as to permit removal and replacement by one person.

3.3.14.6 The RWSL equipment shall [R219] permit removal of all modules without causing damage to the modules or any other equipment. The RWSL equipment shall [R220] use mechanical means (interlocks or keys) to prevent insertion or connection of plug-in modules that are incorrectly oriented. When redundant modules are incorporated into the RWSL system, it shall [R221] be possible to remove any one of the redundant modules without interruption of service.

12/21/2012 16

3.3.14.7 No RWSL equipment, other than small parts or miscellaneous hardware, shall [R222] be mounted 5 ft. above the floor.

3.3.14.8 All cabinet wiring shall [R223] be provided with chafing protection in addition to individual wire or cable insulation jackets.

3.3.14.9 Each indoor cabinet requiring forced ventilation shall [R224] contain its own low-noise fan blower system and shall [R225] require no external ducts. Ventilation exhaust openings shall [R226] be through the top of the cabinet and shall [R227] direct the exhaust upward and away from personnel and other equipment. Exhaust outlet openings shall [R228] not interfere with or be obstructed by cable routings.

3.3.14.10 The RWSL equipment cabinets shall [R229] allow air intake from either below a raised floor or from floor level, by simple removal of cover plates or baffles. Air intakes shall [R230] be provided with uniform air filters in all equipment cabinets; filters shall [R231] be replaceable using only common hand tools.

3.3.14.11 The RWSL equipment shall [R232] provide access for interconnecting cables to enter through the top or bottom of the equipment cabinets.

3.3.14.12 All interconnection cables and connectors required for equipment site installation, checkout, acceptance testing, operation and maintenance shall [R233] be compatible with both under floor and overhead distribution and cable facilities provided by the FAA. All such cabling shall [R234] permit accessibility to equipment for site acceptance test, maintenance and replacement. Cabling and wiring shall [R235] comply with 3.3.1.4.10 of FAA-G-2100H; National Electric Code, NFPA-70; and FAA-C-1217E. All interconnecting cables shall [R236] be plenum-rated in accordance with NFPA-70 725-3, 725-61 and 800-53.

3.3.14.13 All cable connectors furnished on the equipment for making external connections shall [R237] be clearly identified on the plug-in side by labels descriptive of their specific function and by the proper reference designation. The mating connector part (connector or plug) that is electrically energized shall [R238] contain female contacts. All cable connectors shall [R239] be mechanically retained in place, excluding internal power cables. Connectors shall [R240] comply with paragraph 3.3.1.4.3 of FAA-G-2100H.

3.3.14.14 Signal cable end terminations shall [R241] be solderless, quick-disconnect terminal blocks or mass termination connectors. Power cable terminations shall [R242] be screw-type terminal blocks, pressure contact terminal blocks or connectors.

3.3.14.15 Selection of materials for RWLS components shall [R243] be consistent with the requirement of economically producing a system that performs its specified functions with ruggedness and durability for a 20 year operational period. Materials and the processes shall [R244] ensure the equipment will meet performance requirements contained herein for a period of two years in a non-operational state after Government acceptance.

3.3.14.16 All electrical, electronic or electromechanical parts used in the RWSL System shall [R245] be new.

3.3.14.17 The materials chosen shall [R246] be non-nutrient to fungus and insects, flame resistant, non-hygroscopic and not adversely affected by the environmental conditions specified herein.

12/21/2012 17

3.3.15 Communications

3.3.15.1 Land line communications from ATCT to each vault shall [R247] be via fiber optic cable. The fiber optic cables shall [R248] comply with FAA-E-2761C. The optical transmission equipment power budget shall [R249] ensure a bit error ratio of 10-9 or less with allowance for long term degradation (20 years).

3.3.16 Security

3.3.16.1 Physical Security

3.3.16.1.1 The physical security of the RWSL systems shall [R250] be implemented as called for in FAA Order 1600.6E, Facility Security Policy.

3.3.16.1.2 The RWSL System shall [R251] resist physical tampering with cables, connectors, interfaces, configuration settings, and operational parameters to all system components.

3.3.16.2 System Integrity

3.3.16.2.1 The RWSL System shall [R252] include backup of all system setup and optimization files as well as software and firmware.

3.3.16.2.2 In case of a system failure that causes a loss of setup and/or optimization data, the system shall [R253] provide a means of recovery that meets the MTTR requirements.

3.3.16.2.3 System maintenance and optimization commands that alter system performance shall [R254] require secondary verification [i.e., provides additional assurance of the validity of the change(s)] before implementation.

3.3.16.2.4 At start-up, The RWSL System shall [R255] perform a self-check of security functions.

3.3.16.2.5 The RWSL System shall [R256] abort and alarm upon negative security self-check findings.

3.3.16.2.6 The RWSL System shall [R257] protect assets from unauthorized modification.

3.3.16.2.7 The RWSL System shall [R258] protect assets from unauthorized deletion.

3.3.16.2.8 The RWSL System shall [R259] protect assets from unauthorized creation.

3.3.16.2.9 The RWSL System shall [R260] protect assets against false or misleading data.

3.3.16.2.10 The RWSL System shall [R261] test the system integrity at start-up.

3.3.16.2.11 The RWSL System shall [R262] test the system integrity periodically.

3.3.16.2.12 The RWSL System shall [R263] test the system integrity upon administrator request.

3.3.16.2.13 The RWSL System shall [R264] provide monitoring of the integrity of stored and transmitted data.

12/21/2012 18

3.3.16.2.14 The RWSL System shall [R265] generate alerts when data integrity is compromised.

3.3.16.2.15 The RWSL System shall [R266] provide basic rollback.

3.3.16.2.16 The RWSL System shall [R267] allow a rollback of at least three last transactions.

3.3.16.2.17 The RWSL System shall [R268] preserve a secure state after any failure.

3.3.16.2.18 The RWSL System shall [R269] provide centralized security incident reporting.

3.3.16.3 Availability

3.3.16.3.1 The RWSL System shall [R270] protect assets from denial of service.

3.3.16.3.2 The RWSL System shall [R271] protect assets from unacceptable degradation of service.

3.3.16.3.3 The RWSL System shall [R272] provide recovery features for survivability in the event of system failure.

3.3.16.3.4 The RWSL System shall [R273] provide recovery features for survivability in the event of system compromise.

3.3.16.3.5 The RWSL System shall [R274] assign priorities to system services and users.

3.3.16.3.6 The RWSL System shall [R275] enforce quotas on system resources for users and services.

3.3.1…