RRWSL FLS RCP Section C.pdf

Screening Information Request (SIR) No.: 693KA7-24-R-XXXXX

C-1

STATEMENT OF WORK

Runway Status Lights (RWSL) Field Lighting System (FLS)

Replacement Components Procurement (RCP)

February 2024

C-2

Table of Contents

C.1 Introduction

C.1.1 Background

C.1.2 Purpose

C.1.3 Scope

C.1.4 Obtaining Copies of Documents

C.2 FLS Technical Description

C.3 Requirements

C.3.1 Requirements to Minimize Impact on Airports

C.3.2 Compatibility with Existing Baseline of the RWSL System

C.4 Deliverables

C.5 FLS Replacement Component Schedule

C.5.1 FAAFurnished Site and Support

C.5.2 FLS Replacement Component Requirements

C.5.3 CCR Technician Safety, Grounding, and Labeling Requirements

C.6 Program Management

C.6.1 Program Management and Status Reporting

C.6.2 Program Reviews

C.6.3 Cost, Schedule and Technical Performance Management

C.6.4 Post Award Conference (PAC)

C.6.5 Integrated Baseline Review (IBR)

C.7 Engineering

C.7.1 RWSL Sustainment Projects

C.7.2 Technical Interchange Meetings (TIMs)

C.7.3 Systems Engineering Reviews

C.7.3.1 Technical Review Instructions

C.7.4 System Requirements Review (SRR)

C.7.5 SRRAcceptance Criteria

C.7.6 Preliminary Design Review (PDR)

C.7.7 PDRAcceptance Criteria

C.7.8 Critical Design Review (CDR)

C.7.9 CDR Acceptance Criteria

C.8 Configuration Management Program (CMP)

C-3

C.8.1 Configuration Item and Baseline

C.8.2 Part/Item Identification Numbers

C.8.3 Configuration Control

C.9 Quality Management

C.10 Systems Engineering and Design Development

C.10.1 Systems Engineering Documentation

C.10.2 Interface Design Description (IDD)

C.11 Software Development

C.11.1 Software Documentation

C.11.2 Software Development Plan (SDP)

C.11.3 Software Tools and Source Code

C.11.4 Software Requirements Specification (SRS)

C.11.5 Software Design Description (SDD)

C.11.6 Software Version Description (SVD)

C.11.7 Development of Operational and Non-Operational Software

C.12 Hardware Identification and Selection

C.12.1 Interchangeability

C.13 Security Program

C.13.1 Security Hardening and Compliance

C.13.2 Security Relevant Software Updates

C.13.3 FAASecurity Compliance

C.13.4 Information Security

C.14 System Test and Evaluation (T&E)

C.14.1 Test and Evaluation Management

C.14.2 First Articles

C.14.3 Test Support

C.14.4 Verification Requirements Traceability Matrix (VRTM)

C.14.5 Test Conduct

C.14.6 Initial Qualification Test (IQT)

C.14.7 First Article Test

C.14.8 First Article Test Conduct

C.14.9 Power and Inspection

C.14.10 RWSL Performance Part One

C.14.11 RWSL Performance Part Two

C.14.12 System Stability

C.14.13 SiteAcceptance Qualification Test

C-4

C.14.14 Key Site Testing Acceptance Criteria

C.14.15 Regression Test

C.15 RWSL FLS Sustainment Component Delivery and Support

C.15.1 Component Acceptance

C.15.2 Asset Identification and LRU Marking

C.15.3 Implementation at RWSLBaseline Sites

C.16 Support

C.16.1 Supply Support

C.16.2 Support and Test Equipment List

C.16.3 Technical Data

C.16.4 Technical Drawings and Associated Lists

C.16.5 Product Drawings

C.16.6 Commercial Off-the-Shelf (COTS) Manuals and Documentation

C.16.7 FLS Optimization

C.16.8 Second Level Engineering Training

C.16.9 Physical Security at Test Site, Key Site, and Operational Sites

C.16.10 Second Level Engineering Support

C.16.11 Obsolete Parts and COTS Software Program

C.16.12 Warranty

APPENDIX A: Acronym List

APPENDIX B: Security Requirements

APPENDIX C: RWSL BLOCK DIAGRAM

C-5

C.1 Introduction

Since the first prototype was installed in 2005 at the Dallas Fort Worth International Airport, the

Runway Status Lights (RWSL) service has enhanced runway safety for vehicles, aircraft, and people by increasing situational awareness for everyone. The system uses surveillance data provided by the Airport Surface Detection Equipment Model X (ASDE-X) and the Airport

Surface Surveillance Capability (ASSC) systems to reduce the chance of runway incursions and certain classes of runway accidents. RWSL automatically communicates directly to pilots and vehicle operators without demanding the attention of an air traffic controller.

RWSL consists of two subsystems; the RWSL Processor (RP) and the Field Lighting System

(FLS). The RP analyzes and provides real time airport surface operations, determining runway status based on surveillance data. The FLS portion of the system provides the physical interface indicating runway status directly to pilots and vehicle operators, thereby increasing situational awareness. This Statement of Work addresses sustainment of the RWSL FLS only. A block diagram of the RWSL with FLS components shaded in yellow is included within this document.

(See Appendix C)

For the purposes of this SOW, references to “days” mean calendar days, unless otherwise specified.

C.1.1 Background

RWSL operational sites are now at risk for a partial or complete service shut down resulting from component obsolescence, depletion of depot stock, and/or exploitation of age-related security risks. Two key FLS components, the Individual Light Controller (ILC) and Master Light

Controller (MLC), have reached end-of-life status and will not be able to be replaced when depot materials are exhausted. MLC inventory is expected to be exhausted by August 2026 and ILC inventory is expected to be exhausted by May 2025 if 50% recovery of these parts are returned to stock.

The FLS RCP will also address Constant Current Regulators (CCRs) used in the legacy FLS system which were sized to support incandescent fixtures. Over time, Light Emitting Diode

(LED) fixtures have replaced incandescent fixtures, reducing power consumption and rendering some CCRs grossly inefficient. The baseline 20KW CCRs are obsolete and a replacement 20KW

CCR will be qualified and will be replaced in the future upon failure. In addition, a replacement

10 KW CCR will be qualified for use in the RWSL baseline on under-loaded circuits.

The remaining FLS components being replaced during the FLS RCP are the Lighting Computer

(LC) and the CCR Controller (CCR-C). The LC is used for RWSL illumination decisions and maintenance access. The legacy LC poses multiple risks stemming from antiquated computer

C-6 processors and the resulting Information System Security (ISS) deficiencies.

The CCR-C provides communication and processing between the primary components of the

CCR and the Lighting Computer (LC) and provides a Graphical User Interface (GUI) for local control and monitoring. The CCR-C communicates with the RWSL via a serial communication system. Serial communication cards are no longer available in standard computer processors limiting the possibilities for a replacement processor for the LC.

If any of these components should malfunction or fail, RWSL could suffer a partial, or even full, service failure. The RWSL FLS RCP replaces, redesigns, or uses a combination of both, to address these issues.

C.1.2 Purpose

This statement of work (SOW) details the hardware, software, and services the Contractor must provide for component design and development and to support testing, installation, integration, and configuration of the FLS into the legacy RWSL system to satisfy the specific requirements of this SOW and each Delivery Order.

C.1.3 Scope

This SOW defines the requirements, to be outlined in individual Delivery Orders, for delivering a FLS that is backwards and forwards compatible with the existing RWSL system and the associated technical support required to incorporate the FLS into:

1) Four support systems at Mike Monroney Aeronautical Center (MMAC)

2) One system at key site1 Phoenix Sky Harbor International Airport (PHX); and

3) 19 operational sites. (see Section F.10)

FLS work to be developed and delivered are listed in J-16 (Statement of Work Matrix) and discussed elsewhere in this SOW.

The RWSL FLS RCP is a technical refresh of the FLS subsystem. The Contractor will be expected to update the program interface and design description documents to reflect interfaces among the FLS components; however, the Contractor must not make any changes to the interfaces outside of the FLS subsystem. No changes between the FLS and any part of the

RWSL Processing System will be accepted.

This SOW defines the scope of the support services required of the Contractor. The FAA will use Contractor support services for second-level engineering support of the FLS system until it is

1 The FAA retains the right to change key site testing from PHX to another designated site.

C-7 accepted by the FAA and transitions to FAA ownership. Acceptance of replacement components into the NAS is defined by approval of the Baseline National Airspace System (NAS) Change

Proposal (NCP). The Contractor must provide second level support as needed until the the NCP is approved. After the NCP has been approved, components are owned by the FAA and second level support will be provided by the FAA. The Contractor may be called upon as needed during operational site sustainment to support unique challenges.

The Contractor must provide qualified engineering and technical personnel for these services, as necessary, to complete assigned tasks. These services must be provided on an approved time and material (T&M) basis with the Contractor indicating any incidental hardware required to perform services.

This contract calls for modifying COTS software to enable the new LC (running on the Linux platform) to communicate with the rest of the FLS and the RP. The rights in data clauses called out in Sections C.7.6 and C11.3 state FAA will retain data rights in the software developed or modified for this contract.

Applicable Documents

The following specifications, handbooks, orders, standards, and drawings form a part of this

SOW and are applicable to the extent specified herein. The latest version of these documents apply, as of the contract award date. In the event of conflict between this SOW and any of the applicable documents cited below, the provisions of this SOW take precedence; additional any conflicts between the requirements documents FAA-E-3001, FAA-E-3002, and 700-022100, FAA-E-3001 takes precedence.

Document ID Title

FAA Specifications

FAA-E-3001 Performance Specification, RWSL System

FAA-E-3002 Performance Specification, Field Lighting System

(FLS)

FAA-G-2100J Electronic Equipment, General Requirements

FAA-C-1217H Electrical Work Interior

700-022100 Product Specification (PS) for the Field Lighting

System (FLS) For the Runway Status Lights (RWSL)

Program

710-022147 Interface Design Description (IDD) for RWSL

C-8

790-020415 Interface Control Document - Airport Surface

Detection Equipment Model – X (ASDE-X) To

Runway Status Lights (RWSL)

840-022120 System/Subsystem Design Document (SSDD)

710-022601 FLS Subsystem System Design Description (FLS-

SSDD)

FAA Standards

FAA-STD-019F CHG 3 Lightning and Surge Protection, Grounding, Bonding, and Shielding Requirements for Facilities and

Electronic Equipment

FAA Orders

FAA Oder 1600.75 Protecting Sensitive Unclassified Information (SUI)

FAA Order 1370.121B FAA Information Security and Privacy: Policy

1370.121B Supplemental

Implementing Directive

FAA Information Security and Privacy: FAA

Implementation Of NIST

Controls

Military Standards and Handbooks

MIL-PRF-28000B Digital Representation for Communication of Product

Definition Data: Initial Graphic Exchange

Specification (IGES) Application Subsets and IGES

Application Protocols

MIL-HDBK-61B Military Handbook: Configuration Management

Guidance (07 April 2020)

MIL-STD-31000B Technical Data Package

Other

IEEE 1100-19 Recommended Practice for Powering and Grounding

Electronic Equipment

NIST 800-53 Rev. 5 (December 10, 2020)

Security and Privacy Controls for Information Systems and Organizations

SAE AS9100D Quality Management Systems - Requirements for

C-9

Aviation, Space, and Defense Organizations

ASME Y14.100 Engineering Drawing Practices

C.1.4 Obtaining Copies of Documents

Copies of FAA specifications and interface documents may be obtained from the Federal

Aviation Administration Headquarters Public Inquiry Center (APA-230), located at 800

Independence Avenue SW, Washington, DC 20591, or via phone at 202-267-3484. Requests should fully identify the material desired and cite the solicitation or contract number.

Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer (CO). Requests should fully identify the material desired and cite the solicitation or contract number.

C.2 FLS Technical Description

RWSL processes Airport Surface Detection Equipment – Model X (ASDE-X) and Airport

Surface Surveillance Capability (ASSC) data using software algorithms with adjustable parameters to control airfield lights in accordance with air traffic operations, including anticipated separation. Runway Entrance Lights (RELs) and Takeoff Hold Lights (THLs) are embedded in the pavement on certain runways and taxiways, and turn red to notify pilots and vehicle operators when RWSL safety logic indicates it is unsafe to enter or depart. Further information regarding the RWSL program can be found at faa.gov/air_traffic/technology/rwsl/.

RWSL consists of two subsystems: the RWSL subsystem and the FLS subsystem. The RWSL subsystem consists of an Equipment Room Cabinet (ERC), up to three Cab Control Panels

(CCP), up to three Tower Cab Control Assembly(s) (TCCA), and up to three Kill Switch

Assembly(s). The FLS subsystem consists of equipment housed in a shelter and installed on the airfield. The LC (part of the FLS) resides in the ERC. A shelter contains one Remote

Maintenance Terminal Cabinet (RMTC) and up to four MLC/CCR Assemblies. Each MLC/CCR connects to one series circuit lighting loop (circuit) on the airfield.

A circuit contains in-pavement light assemblies. Each in-pavement light assembly consists of one isolation transformer, one ILC, and one light fixture. Circuits are identified by fixture type.

The RWSL system uses two types of fixtures: Runway Entrance Lights (REL) and Takeoff Hold

Lights (THL). A circuit will consist of either REL or THL fixtures and be identified by fixture type.

C-10

Within each circuit, REL and THL assemblies are grouped into arrays. A REL array has a minimum of six REL assemblies. A THL array typically has 32 THL assemblies. A RWSL runway installation can contain a combination of REL and THL arrays. All FLS subsystem configurations are limited by the following design constraints:

1) Number of shelters: one to eight

2) Number of circuits: one to 15 (limit of four per shelter)

3) Light fixtures: up to 1000 (limit of 120 per circuit)

Commissioned RWSL sites are operating on circuit lengths up to 45,000 feet, with up to 120 individual lights (RELs or THLs) using unshielded L-824 airfield cable. FLS replacement components must be capable of controlling all commissioned circuits without changing circuit layout or infrastructure.

C.3 Requirements

The Contractor must have the tools and materials necessary to support modification of COTS components, installation, configuration, and testing of the FLS, as ordered. The FAA will take ownership of the testing and configuration tools and materials used as deliverables under this contract upon acceptance of the FLS RCP system components. FLS components and supporting documents to be supplied and supported under this SOW are listed in Section F, Deliveries or

Performance.

The Contractor must support installation of each of the required components at the MMAC

RWSL test bed and follow on to the key site at Phoenix Sky Harbor International Airport (PHX).

The FAA will be performing all site preparation, installation, and testing at sites. After successfully completing key site testing, the RWSL program office will begin sustainment of the remaining 19 operational sites and the Training Academy at the MMAC. Contractor technical support is not anticipated to be necessary for installation of operational sites, other than possible technical support by phone. The FAA reserves the right to require in-person engineering support for operational site installation of each component, should the need arise. This SOW includes requirements for:

1) Full replacement of all MLC/ILC components

2) Full replacement of all LC components.

3) Full replacements of all CCR-C

4) Qualification for the 20 KW CCR replacement

5) Qualification for the 10 KW CCR

6) Technical support as the FAA conducts First Article testing at MMAC

7) Technical support at the PHX key site installation, FLS optimization and testing

8) Second Level Engineering training to support configuration and troubleshooting at operational site installations

C-11

9) Any documentation developed for this contract, such as COTS documentation, standard industry documentation, program documentation, system documentation, configuration documentation, commercial manuals, software manuals, connection guides, trouble-shooting guides, and schematics

10) Technical support provided from the Contractor as needed for installation, FLS optimization, and testing at operational sites

C.3.1 Requirements to Minimize Impact on Airports

FLS RCP execution has been designed to minimize impact on airport operations and leverage individual airport runway construction and/or maintenance planning as much as possible. This sustainment execution design is flexible, minimizes closures, and sustains the system by breaking the work into appropriate segments. During installation, the FAA will ensure that only affected segments of the RWSL FLS System will be removed from service while remaining segments remain operational. All FLS RCP components in the Contractor’s solution must be capable of being installed, optimized, tested and certified for operation, working seamlessly with all segments of legacy FLS equipment and operating system.

C.3.2 Compatibility with Existing Baseline of the RWSL System

The existing legacy system infrastructure using Power Line Communication (PLC) technology is a constraint upon the RWSL FLS RCP. The Contractor’s sustainment components must use existing unshielded airfield cable and be fully compatible with the legacy system. During each individual circuit’s sustainment outage, the FAA will replace, configure, test, and return to service that circuit’s MLC and associated ILCs. LC, CCR-C, and CCR replacements will be addressed on independent schedules after the MLC/ILC replacements. Consequently, the

Contractor must ensure that the next generation of hardware functionally integrates with the legacy RWSL system, being backwards and forwards compatible.

Independent sustainment projects conducted by the FAA will integrate and test components into the RWSL baseline system as follows:

1) MLC/ILC replacement qualification

2) CCR-C replacement qualification

3) LC replacement qualification

4) CCR replacement qualification

C.4 Deliverables

The Contractor must deliver, as ordered by the FAA:

1) RWSL FLS RCP components

2) An LC composed of a rack mountable computer with an x86_64 architecture compatible

C-12

CPU and Red Hat Enterprise Linux version 8 (or latest version). The LC must host the software applications necessary to provide an interface between the RWSL processor subsystem and FLS. This new LC must provide a direct replacement of the LC currently configured in the RWSL baseline such that no additional modifications to the RWSL processor subsystem are required.

3) Commercial manuals, software manuals, connection guides, troubleshooting guides and schematics, and technical support as needed to assist the FAA in successfully integrating replacement components into the RWSL system.

4) All operational and non-operational software, including any Original Equipment

Manufacturer (OEM) or third-party software that need to transfer with these products, as determined by the FAA.

5) Documentation and technical information necessary to demonstrate compliance with:

a. FAA-E-3001, FAA Performance Specification Runway Status Lights (RWSL)

System (Attachment J-1)

b. FAA-E-3002, Rev 1, FAA Performance Specification Runway Status Lights

(RWSL) Field Light System (FLS) (Attachment J-2)

c. 700-022100, Version 7 Product Specification (PS) for the Field Lighting System

(FLS) for the Runway Status Lights (RWSL) Program (Attachment J-7)

d. 710-022147, Version 9 Interface Design Description (IDD) for RWSL

(Attachment J-8)

e. 840-022120, Version 7 (Final) System Design Document for the Runway Status

Lights (RWSL) Program (SSDD) (Attachment J-9)

f. 710-022601, Version 4 (Final) Subsystem Design Description for the Field

Lighting System (FLS) for the Runway Status Lights (RWSL) Program (FLS-

SSDD) (Attachment J-10)

g. 790-020415, Interface Control Document (ICD – Airport Surface Detection

Equipment Model X (ASDE-X) to Runway Status Lights (RWSL) (Attachment J-

14)

h. The current NIST 800-53 Publication, Security and Privacy Controls for Federal

Information Systems and Organizations https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final

6) Hardware and software tools required for installation, configuration, and troubleshooting of installed components. Upon successful completion of testing, hardware or software tools used by the Contractor in the performance of these tasks will become Contractor-furnished property, with title vested in the FAA.

7) A five (5) day on site technical review for the FAA at MMAC of FLS equipment necessary to install, configure, integrate, and troubleshoot the First Articles, as delivered for each RWSL sustainment project.

8) In-person technical support provided by two engineers for the entire test baseline at

MMAC (estimated for up to six weeks total, but not necessarily contiguous) and field https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final

C-13 testing at PHX (estimated for up to four weeks total, but not necessarily contiguous).

Technical support includes documentation and/or software updates required to handle different FLS communication protocols.

9) Remote and on-site assistance with configuration of FLS components at baseline RWSL

Sites as requested.

10) Second level engineering training at MMAC for five business days.

11) Phone support during regular business hours (8:00 a.m. – 5:00 p.m.), anticipated to be

2000 hours over the life of the contract.

12) Software applications required to make sustainment components compatible with the

FAA legacy RWSL.

13) The FAA will retain data rights for all delivered operational and non-operational software in accordance with the Rights-in-Data clauses in Section I of this Contract.

14) Source Code for all FAA specific development must be provided with the software delivery.

15) Production and delivery of production components, including operational software, at each site including all required spares.

Note that delivery of 700-022100, 710-022147, 790-020415, 840-022120, and 710-022601are for Contractor updated documents as required for Contractor’s FAA-approved design.

C.5 FLS Replacement Component Schedule

The Contractor must include components as listed in Section F Table F10, Estimated

Sustainment Components by Site and in accordance with approved delivery orders.

The FAA estimates the existing MLC inventory will be depleted by August 2026. The existing

ILC inventory is expected to be depleted by May 2025. Current planning has established FLS

RCP sites by level of difficulty. The FLS RCP waterfall reflects current planning and is subject to change. (see SIR Section F.4)

C.5.1 FAAFurnished Site and Support

The FAA will provide the following FAA Furnished Information/Material/Support

(GFI/GFM/GFS):

1) A lab setting with operational RWSL test bed at MMAC for the duration of integration and testing;

2) Skilled labor to install and configure the First Articles and follow-on sites, with

Contractor assistance;

3) Coordination and scheduling support for installation activities at all sites;

4) Technical expertise for determining compliance with RWSL specifications; and

5) Information/Material (e.g. System/Subsystem Design Description, FLS Circuit

Optimization Guide, Verification Requirements Traceability Matrix (VRTM), Facility

Standard Drawings, etc.) that can be used as a starting point with probable modification

C-14 by the Contractor based upon their proposed system components.

C.5.2 FLS Replacement Component Requirements

The Contractor is responsible for providing project components that must meet the following requirements:

1) The interface between the FLS and the RP must be capable of operating on a Red Hat

Enterprise Linux (RHEL) Operating System platform.

2) The components must integrate with existing 20 kilowatt (kW) L-829 CCRs and contractor’s proposed new CCRs.

3) CCR-Cs will be replaced with a newer controller to eliminate the serial communication infrastructure and the Current Voltage Monitor (CVM). The FLS RCP CCR-C must work with the legacy CCRs as well as the FLS RCP CCR.

4) The components must provide the capability to operate the RWSL system in a “hybrid” configuration, with legacy components and sustainment components operating on separate circuits concurrently.

5) The FLS must interface with the existing RP with no changes required in the RP to FLS interface software message structure, as defined in the IDD (Interface Design

Description, Attachment J-8) and ICD (Interface Control Document) for interface to

Airport Surface Detection Equipment Model X (ASDE-X), Attachment J-14).

6) The FLS must be capable of providing reliable communication performance for airfield circuits using the installed RWSL infrastructure, which uses unshielded L-824 cable for the airfield circuits meeting the minimum insulation resistance requirement of 10 M-

Ohm, measured at 500Vdc.

7) MLCs must be capable of providing reliable communication performance for airfield circuits containing up to 120 individual lights on a circuit length up to 45,000 feet using unshielded L-824 cable.

8) The Contractor must provide ILCs that fit inside existing in-pavement light base cans with other components (i.e., legacy LED fixtures, L-830 Style Isolation Transformers, and L-824 cable).

9) The existing RWSL system uses L-830 Style Isolation Transformers between the airfield primary power and the ILC. Contractor components must integrate with the existing

Isolation Transformers.

10) The Contractor must provide components which operate with the legacy RWSL LED

REL/THL fixtures. The legacy RWSL system uses L-852T Style 3 LED THL fixtures and L-852S LED REL fixtures.

11) All components installed in the RWSL System must be compliant with FAA-STD-019F, Change 3, Lightning and Surge Protection, Grounding, Bonding and Shielding

Requirements for Facilities and Electronic Equipment, Attachment J-11, without changes to the existing infrastructure.

C-15

12) The Contractor must provide components that are not susceptible to or interfere with other lighting or communications systems on the airfield without changes to the existing infrastructure.

C.5.3 CCR Technician Safety, Grounding, and Labeling Requirements

CCRs provided for RWSL sustainment must meet all relevant functional and performance requirements of the RWSL specifications FAA-E-3001 Performance Specification for the

Runway Status Lights System and FAA-E-3002 Performance Specification for the RWSL

FLS. The following requirements must be included:

Technician Safety

a) Transparent protective guards must cover exposed electrical components including the

CCR controller to prevent incidental contact with voltages. The cover must be nonconductive material that does not require grounding as referenced in FAA-G-2100 J paragraph 3.3.5.1. The cover will be transparent, so that the maintenance technician will be able to view troubleshooting LEDs.

b) The transparent protective guards must have no sharp edges or use edge guards to protect personnel from injury.

c) Test points must be provided for measuring CCR input and output voltages and other measurements necessary for troubleshooting and maintenance without removal of protective guards.

d) Test point holes must be provided in the transparent guards to facilitate maintenance activities without removing the guard.

e) Test point slots must be sized and aligned to adequately take the measurement. The height for horizontal slots and the width for vertical slots are used as the “diameter” to determine the recessed distance, as referenced in FAA-G-2100 J paragraph 3.3.5.1.9.

f) A step-down transformer (100:1) and dedicated test point must facilitate input voltage measurements.

g) A test-loop and clamp block must facilitate output current measurements.

h) A hinged door stop will hold the front door of the CCR open when work is performed on the CCR, as referenced in FAA-G-2100 J paragraph 3.3.5.4.

i) All LRUs must be located on or near the front or rear CCR panels to facilitate maintenance and inspection without exposing the maintenance technician to dangerous voltages.

j) All LRUs must be easily accessible by the technician for remove and replace.

Grounding

a) CCR grounding must use bolts or threaded studs on bare metal surfaces. CCR frame grounding cables must be #6 American Wire Gauge (AWG) stranded wire with the color

C-16 code of green with a yellow stripe.

b) Ground wires from electrical components such as lightning arrestors must attach directly to the main ground lug as referenced in FAA-STD-019F.

c) The RWSL equipment lightning and surge protection, grounding, bonding and shielding must be in accordance with paragraphs 4.1 and 4.3 of FAA-STD-019F, FAA-C-1217H

(Attachment J-4), and sections eight and nine of IEEE 1100-2005

d) A point on the electrically conductive chassis or equipment frame must serve as the common tie point for the static or power ground, as referenced in FAA-G-2100J paragraph 3.3.5.1.1. h. (Attachment J-3)

Labeling

1) All cables will be permanently and legibly labeled, as referenced in FAA-G-2100J paragraph 3.3.1.4.10.2.

2) Cover above and below the CCR controller enclosure to warn “CAUTION 480 Volts”

3) A label to identify the test loop and clamp block must read “OUTPUT CURRENT

HANDLE” in Helvetica at 42 point font size.

4) Multi-wire connections that terminate on a connector will have a label for the connector, rather than the individual wire.

5) All LRUs must be identified with labels indicating LRU name, OEM part number, National Stock Number and serial number.

6) Where necessary, labels must be affixed to LRUs indicating installation direction or orientation/placement.

7) “DANGER” and “CAUTION” signs must be in accordance with FAA-G-2100J

8) The "DANGER” sign on the rear of the CCR should read “HIGH VOLTAGE 5000

VOLTS TURN OFF POWER BEFORE SERVICING”.

9) The “DANGER” sign on the front of the CCR should read “HIGH VOLTAGE 480

VOLTS”. This label will also be placed on the CCR front component mounting plate.

10) “CAUTION” signs must be placed on the CCR-C.

11) RWSL Facility Standard Drawings (FSD) drawings E318 thru E321D provide the standard labeling requirements for the RWSL equipment

C.6 Program Management

C.6.1 Program Management and Status Reporting

The Contractor must provide the necessary program management, including but not limited to:

project, risk, data, configuration, financial, cost, and schedule management, to accomplish the requirements of this SOW. In accordance with CDRL PM 01, the Contractor must submit a

Program Management Plan (PMP) 40 days after the contract award.

C-17

The PMP must describe the contractor’s overall strategy and approach to managing the RWSL

FLS RCP activities under this contract. It also must provide details on management processes, organization design, and roles and responsibilities of key personnel and teammates. In addition, the PMP must include the communication channels to be used internally and externally and approaches for general program management, systems engineering, software development, test and evaluation, and logistics support.

The Contractor must provide the appropriate program management and project controls necessary to manage the Delivery Orders (DOs) and ensure that cost, schedule, and quality requirements for each DO are continually tracked with status communicated to the FAA to ensure that each DO is successfully completed. The Contractor must assign a designated

Program Manager (PM) to manage this effort. The PM must be the point of contact between the

FAA and the Contractor in the execution of this contract and must be prepared at all times to present and discuss the status of contract activities with the FAA.

The Contractor must provide a monthly Program Status Report (PSR) in accordance with CDRL

PM 02 informing the FAA of the Contractor’s assessment of contractual effort as of the date of the report. The PSR must cover achievements, areas of difficulty, and the Contractor’s approach for correcting problems and maintaining baseline plans. The Contractor must deliver the reports to the COR. Reports must include, at a minimum, the following information:

a) overview of work completed, work in progress, and work planned for each DO;

b) status of individual deliverables, including cost, schedule and performance;

c) identification of risk areas with recommended remedial actions;

d) status of all outstanding risks identified in the previous PSRs;

e) status of all action items; and

f) additional information pertinent to the FAA in administering the performance of this effort or when directed by the CO or COR.

The Contractor must continuously monitor the performance of this contract to provide the FAA with a timely assessment of program progress or problems, and to control the contract activities.

The Contractor must establish and deliver an integrated master schedule (IMS) in accordance with CDRL PM 03, designed to monitor and track contract schedule performance, plans and accomplishments for the approved DOs described in this contract. The CO, Contracting

Officer’s Representative (COR), and FAA leads will hold regular coordination meetings and/or teleconferences with the vendor, in addition to quarterly Program Management Reviews (PMRs).

In accordance with CDRL PM 04, the Contractor must provide a Contract Funds Status Report

(CFSR) summarizing contract funding data for the purposes of: (a) updating and forecasting contract funds requirements, (b) planning and decision making on funding changes to contracts,

c) assessing the need of funds and timing of DOs, (d) determining funds in excess of contract needs and available for de-obligation, (e) assessing the financial risks, and (f) obtaining an

C-18 estimate of termination costs. The CFSR will be for active DOs, based on the deliverables identified in the applicable DO, as well as the total contract. The Contractor must provide a

CFSR that documents the activities of the previous month and identifies planned activities for the following month. The Contractor must deliver the reports to the COR. Reports must include, at a minimum, the following project financial status:

a) Contract Line Item Numbers (CLINs) used during month

b) Cost funded or apportioned by CLIN

c) Cost used by CLIN

C.6.2 Program Reviews

The Contractor must conduct Program Management Reviews (PMRs) to demonstrate the successful completion, or progress toward completion, of project milestones across all Delivery

Orders. The Contractor must conduct PMRs quarterly, or as requested by the FAA, during the period of performance of this contract. The PMRs will normally be conducted at the Contractor’s facility; however other sites or virtual meetings may be selected by mutual agreement between the FAA and Contractor. During the PMRs, the Contractor must present plans for accomplishing project milestones and activities, analyses, status of actions, cost and schedule, and the overall performance.

The Contractor must conduct meetings and program reviews in accordance with the final PMP and this SOW. For each meeting and management review, the Contractor must:

1) Create and provide an agenda, overall strategy for conducting each meeting and presentation materials as a deliverable in accordance with CDRL PM 06

2) Provide backup data regarding assumptions made and methodologies used in arriving at recommendations or conclusions

3) Provide meeting minutes, action items, and updated presentation materials in accordance with CDRL PM 06 within 7 days of the meeting. The Contractor is responsible for tracking and ensuring completion of all action items.

Designated management and formal reviews are not complete until FAA written approval is received from the CO or COR for the minutes or reports submitted at their conclusion.

Submissions for PM 06 are required for the Post Award Conference, all PMRs, Integrated

Baseline Reviews (IBR), System Design meetings (SRR, PDR and CDR) and all Technical

Interchange Meetings (TIMs).

CDRL PM 01 Program Management Plan (PMP)

CDRL PM 02 Program Status Report (PSR)

CDRL PM 03 Integrated Master Schedule (IMS)

CDRL PM 04 Contract Funds Status Report (CFSR)

C-19

C.6.3 Cost, Schedule and Technical Performance Management

The Contractor must monitor, track, and report cost performance in accordance with PM 04, Contract Funds Status Report. The Contractor must monitor, track, and report schedule performance in accordance with PM 03, Integrated Master Schedule. The Contractor must monitor, track, and report programmatic and technical performance in accordance with PM02, Program Status Report. All of these are provided monthly. These are augmented by the quarterly

Program Management Reviews.

C.6.4 Post Award Conference (PAC)

The Contractor must plan for, host, and support a post award conference to be held in person, telephonically, or online no later than 30 days after the contract award. The FAA will determine the actual date within two weeks after the contract award. At this conference, the Contractor must address the plans, cost, schedule, and risks for the FLS RCP work efforts. The Contractor must address the programmatic and technical processes to be used to ensure effective accomplishment of Contract requirements. The PAC must be documented in accordance with

CDRL PM06, Meeting Agenda and Minutes.

C.6.5 Integrated Baseline Review (IBR)

The Contractor must conduct an integrated baseline review no later than 200 days after the contract award (after completion of CDR), and after major contract modifications or significant baseline changes.

The purpose of the Integrated Baseline Review (IBR) is to:

1) ensure that the FAA and Contractor mutually understand program scope, schedule, resources, inherent risk, and management approach;

2) ensure early and adequate planning;

3) identify risk items for incorporation into the risk management plan; and

4) ensure appropriate reporting levels have been identified and variance thresholds agreed to by the FAA and Contractor

The Contractor must provide ongoing access during contract performance to pertinent records and data, which underlie and support the cost and schedule data reported. The IBR must be documented in accordance with CDRL PM06, Meeting Agenda and Minutes.

In accordance with CDRL PM 05, the Contractor must develop and maintain a Contractor Work

Breakdown Structure (CWBS) and dictionary based on the FAA Standard Work Breakdown

CDRL PM 06 Meeting Agenda and Minutes

C-20

Structure as noted in the appropriate portions of Sections 3 and 4 in Attachment J-17 . Once approved, the Contractor must not change the CWBS or associated definitions without FAA approval. Major elements that are sub-contracted must be identified in the CWBS.

CDRL PM 05 Contractor Work Breakdown Structure and Dictionary

C.7 Engineering

C.7.1 RWSL Sustainment Projects

The RWSL FLS RCP must support independently conducted sustainment projects, as ordered.

The Contractor must be prepared to adequately support these sustainment projects. The FAA reserves the right to modify, postpone or cancel any or all of the following projects. The planned

FAA sustainment projects include:

1) RWSL FLS Master Light Controller (MLC) and RWSL FLS Individual Light Controller (ILC)

Qualification Project

The MLC and ILC have reached End-Of-Life status and replacement of all components at each site is required. This qualification project requires Contractor development, integration, and test of replacement MLCs and ILCs. Software modifications on the LC are anticipated to complete integration into the RWSL FLS. This project includes assisting the FAA with conducting qualification testing at MMAC testbed and at key site PHX. This project must maximize commercial off the shelf (COTS) products to the greatest extent possible.

1) RWSL FLS Lighting Computer (LC) Replacement Qualification Project

The LC is a Windows XP based computer that is no longer supported, requiring replacement of all

LCs at each site. This qualification project requires Contractor development and replacement of the

LC with Red Hat Enterprise Linux (RHEL) Operating System (OS). LC Software modifications are anticipated to complete hosting of the existing FLS functionality on a new LC platform. The new

Lighting Computer (LC) must address necessary cybersecurity enhancements including transitioning the LC to utilize RHEL consistent with the other processors in the system. All critical and high priority vendor patches, as well as, necessary security hardening standards, must be applied prior to deployment within the NAS. This project includes assisting the FAA with integrating the LC into the

RWSL System and conducting qualification testing at MMAC testbed and at key site PHX.

2) RWSL FLS Constant Current Regulator – Controller (CCR-C) Replacement Qualification:

The CCR Controller has reached End-Of-Life status and replacement of all components at each site is required. This qualification project requires Contractor development, integration, and test of a replacement CCR-C. The next generation of the CCR-C, which is

C-21 currently LAN/IP based, will eliminate the serial communication infrastructure and add the CCR-C communication to the existing LAN communication between the FLS shelter and the Lighting

Computer. The next generation of CCR-C must use signals from the main control board in the CCR to monitor CCR output current and voltage and eliminate the existing Current Voltage Monitor

(CVM) line-replaceable unit (LRU) from the CCR. This project includes assisting the FAA with conducting qualification testing at MMAC testbed and at key site PHX. This project must maximize commercial off the shelf (COTS) products to the greatest extent possible.

3) RWSL FLS Constant Current Regulator (CCR) Replacement Qualification:

The 20 KW CCR has reached End-Of-Life status and a replacement CCR is required for qualification into the RWSL baseline. In addition, a 10 KW CCR must also be Contractor developed and FAA qualified into the RWSL Baseline in order to improve power consumption efficiency and increase reliability of CCRs on low-load circuits. The replacement CCR must include all technician safety, grounding, and labeling requirements consistent with the existing RWSL CCRs. The 20 KW CCRs will be replaced with the CCR qualified on this project at baseline sites on attrition. The 10KW CCRs will be installed at selected baseline circuits where the existing 20 KW CCR is less than 15% loaded

(approximately 20 CCRs in the RWSL baseline). This project includes assisting the FAA with conducting qualification testing at MMAC testbed and at key site PHX. This project must maximize commercial off the shelf (COTS) products to the greatest extent possible.

4) RWSL SERVICE LIFE EXTENSION PROGRAM (SLEP) (19 projects, 1 for each site): Provide approved MLC/ILC, LC, CCR-C, and CCR hardware including spares at all

RWSL operational sites. This project may include engineering support services as necessary.

Each qualification project must begin with the modification of COTS equipment and lab integration, Initial Qualification Testing, and First Article Testing at MMAC, and conclude with key site testing at PHX. Each project will progress concurrently and independently of the other projects. Once the qualification project is complete, the associated qualified components will be independently implemented at each of the RWSL operation sites through the RWSL SLEP project. Sustainment projects are individually funded on a yearly basis. The FAA does not guarantee that all projects will be funded.

C.7.2 Technical Interchange Meetings (TIMs)

The purpose of Technical Interchange Meetings (TIMs) is to ensure continued FAA visibility into the technical progress of the contract and to resolve any technical issues, concerns, or risks as they are identified. The Contractor must plan and effectively participate in TIMs between the

FAA and the Contractor at the Contractor's facility, sites selected by the FAA, or virtual TIMs requested by the FAA or Contractor. During TIMs, participants will discuss the status of technical activities, including, but not limited to, studies, test plans and results, design issues, C-22 cost, schedule, performance, and technical guidance. The Post Award Conference, Program

Management Reviews, System Engineering Reviews (SRR, PDR, CDR) and Integrated Baseline

Review are considered TIMs for the purpose of this Contract. All TIMs must be fully documented in accordance with CDRL PM06, Meeting Agenda and Minutes. All action items resulting from the TIMs must be documented and tracked to completion by the Contractor and reported to the FAA.

C.7.3 Systems Engineering Reviews

The Contractor must support the following planned System Engineering Reviews and Design

TIMs to manage the evolving FLS design and program control activities:

1) System Requirements Review (SRR)

2) Preliminary Design Review (PDR)

3) Critical Design Review (CDR)

No more than thirty-five (35) days after contract award, the Contractor must present to the

RWSL program office a schedule for system requirements, preliminary design, and critical design reviews in the form of Technical Interchange Meetings. At that time, the Contractor must also inform the FAA when they plan to deliver the First Articles.

The Contractor must prepare and submit to the FAA an agenda, presentation materials, and minutes for all technical reviews in accordance with CDRL PM 06. Presentations must be based upon the Contractor’s engineering efforts and related documentation. Minutes must contain copies of all presentation material, results of discussions and any decisions, a list of all actions, and a plan for each action item resulting from the review. The formal minutes must be used to document the meeting and will be used by the FAA in the approval process for the technical reviews.

At each review, the Contractor must be prepared to provide back-up data on assumptions made and methodologies used in arriving at specific recommendations/conclusions. Contractor key personnel listed in Section H. Clause 3.8.2-17 and qualifications described in Attachment J-15, Labor Category Descriptions, must be available to respond to FAA questions.

The Contractor must make available for reference and inspection at the reviews applicable engineering data, specifications, drawings, schematics, design and test documentation, software development files, schedules, and working papers and results of studies and analyses.

The Contractor must notify the COR and CO of readiness for a review at least 14 days in advance of the planned start of each review. If the previous technical review has not been approved by the FAA, or if documents required for a review have not been delivered to the FAA as scheduled, the FAA will have the option of postponement without prejudice to other

C-23 contractual requirements. Formal reviews will not be considered complete until approval by the

FAA CO or designated COR is granted in writing.

C.7.3.1 Technical Review Instructions

The following instructions apply to all technical reviews:

1) Presentations must be conducted by Contractor personnel, although the FAA reserves the right to revise the agenda and/or make presentations.

2) The location of the reviews will be determined by mutual agreement between the FAA and Contractor.

3) The Contractor must record all action items identified.

4) Response to all assigned action items by either closure or a plan for closure must be made by the Contractor to the FAA in the minutes of the meetings/reviews. The Contractor must track the status of all action items as an attachment in the Program Status Report until the action item has been resolved as mutually agreed by the FAA and Contractor.

5) Ten days after receipt of the review minutes, the FAA will formally notify the Contractor of the results of the subject review by:

a) Approval indicating that the review was completed satisfactorily;

b) Contingent Approval indicating that the review is not considered complete until completion of specific action items to the FAA satisfaction; or

c) Disapproval indicating that the review was not satisfactory with identification of those areas that were deficient. The Contractor must have 14 days to respond to the

FAA and provide a plan to maintain and complete the program schedule.

C.7.4 System Requirements Review (SRR)

The Contractor must conduct a System Requirements Review (SRR) 45 days after the contract award. The objective of this review is to ascertain the adequacy of the Contractor efforts in understanding and meeting system requirements and the requirements of the sustainment program.

During the SRR, the Contractor must present results of functional flow analysis, system interface studies, cost effectiveness analysis, and program risk analysis. The Contractor must present detailed requirement definitions of the integration of the Contractor’s components into the RWSL

FLS. The Contractor must demonstrate full understanding of the operational concepts of the

RWSL FLS and specific sustainment requirements.

During the SRR, the Contractor must present and review the following:

1) Flows and system requirements definitions

2) Review of the requirements and test methods in the VRTM

3) Security considerations, identification of security related requirements and implementation into the RWSL FLS.

C-24

4) Interfaces of components within the RWSL System.

5) Changes required within the FLS Software and the development plan for these changes.

6) System safety program considerations for personnel safety.

7) Critical tasks necessary for completion of each qualification project.

8) Draft #1 Integrated Master Schedule (IMS) in accordance with CDRL PM 03

9) Identification of design-driving/cost-driving requirements

10…