RWSL FLS RCP Sec. C.pdf

STATEMENT OF WORK

DRAFT

Runway Status Lights (RWSL) Field Lighting System (FLS) Replacement Components Procurement

January 2023

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

C-2

Table of Contents

C.1 Introduction

Background

Purpose

Scope

Security and Privacy Controls for Information Systems and Organizations

Obtaining Copies of Documents

C.2 FLS Technical Description

C.3 Requirements

Requirements to Minimize Impact on Airports

C.4 Deliverables

FLS Replacement Component Schedule

FAA Furnished Site and Support

FLS Replacement Component Requirements

CCR Mod Requirements

C.5 Program Management

Program Management and Status Reporting

Program Reviews

Earned Value Management (EVM)

Post Award Conference (PAC)

Integrated Baseline Review (IBR)

C.6 Engineering

Technical Interchange Meetings (TIMs)

Systems Engineering Reviews

System Requirements Review (SRR)

SRR Acceptance Criteria

Preliminary Design Review (PDR)

PDR Acceptance Criteria

Critical Design Review (CDR)

CDR Acceptance Criteria

C.7 Configuration Management Program (CMP)

C-3

Configuration Item and Baseline

Part/Item Identification Numbers

Configuration Control

C.8 Quality Management

C.9 Systems Engineering and Design Development

Systems Engineering Documentation

System/Subsystem Design Description (SSDD)

Interface Control Document (ICD)

C.10 Software Development

Software Development Plan (SDP)

Software Tools and Source Code

System Software Design (SSD)

C.11 Development of Non-Operational Software

C.12 Hardware Identification and Selection

Interchangeability

Security Program

Security Hardening and Compliance

Security Relevant Software Updates

Recurring Security Assessments and Penetration Evaluations

Information Security

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

Test and Evaluation Management

C.14 RWSL FLS Sustainment Component Delivery and Support

Production Acceptance Test and Evaluation

Component Acceptance

Component Delivery

Line Replaceable Unit (LRU) Identification and Marking

C.15 Support

Supply Support

APPENDIX A: RWSL FLS Component Descriptions

APPENDIX B: RWSL Block Diagram file://faa.gov/faafile/ATO/AWA/AJA/AJA-4/AJA-464%20flight%20Services%20Branch/AAQ-240/SOLICITATIONS/RWSL%20Sustainment/DRAFT%20SIR%20Documents/Section%20C/FLS%20Sec.%20C_01.26.2023.docx#_Toc125637696

C-4

APPENDIX C: Acronyms

APPENDIX D: Preliminary Waterfall Schedule of Sustainment Projects

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 B).

The RWSL FLS Replacement Components Procurement (RCP) is within the Federal Aviation Administration’s (FAA) Surface Surveillance Portfolio Sustainment 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. Of the 115 legacy CCRs, 20 will be replaced with smaller, more efficient CCRs.

The remaining FLS component being replaced during the FLS RCP is the Lighting Computer (LC) used for RWSL illumination decisions and maintenance access. The legacy LC poses multiple risks stemming from antiquated computer processors and the resulting Information System Security (ISS) deficiencies.

C-6

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.

Purpose

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

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 Orlando International Airport (MCO); and

3) 19 operational sites (see Appendix D)

FLS components are listed in Section B, Supplies or Services and Prices/Cost.

The RWSL FLS RCP is a technical refresh of the FLS subsystem. The Contractor must not change the Interface Control Document (ICD) outside of the FLS subsystem. No changes between the FLS and any part of the RP will be accepted.

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

The FAA reserves the right to 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) Qualifications Modify, integrate, and test COTS RWSL MLCs and ILCs. This includes assisting the FAA with conducting testing at the Mike Monroney Aeronautical Center (MMAC) testbed and at key site (Orlando International Airport (MCO)). This project must maximize commercial off the shelf (COTS) products to the greatest extent possible.

2) RWSL FLS Lighting Computer (LC) Replacement Qualification: Modify, integrate existing software for, and test a replacement LC to integrate with the RWSL System

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

C-7 procured through this contract. The new Lighting Computer (LC) will address necessary cybersecurity enhancements including transitioning the LC to utilize Red Hat Enterprise Linux consistent with the other processors in the system. All critical and high priority vendor patches, as well as, necessary security hardening standards, will be applied prior to implementation. This includes FAA testing at the Oklahoma City (OKC) National Airspace System (NAS) Engineering testbed (MMAC) and at key site (MCO). This project must maximize COTS products to the greatest extent possible.

3) RWSL FLS Constant Current Regulator – Controller (CCR-C) Replacement

Qualification: Modify, integrate, and test a COTS Constant Current Regulator – Controller (CCR-C) in all Constant Current Regulators (CCRs). The next generation of the CCR-C which is 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 includes FAA testing at the OKC NAS Engineering testbed (MMAC) and at key site (MCO). This project must maximize COTS products to the greatest extent possible.

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

Modify, integrate, and test a COTS replacement Constant Current Regulator 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. This includes FAA testing at the OKC NAS Engineering testbed (MMAC) and at key site (MCO). This project must maximize COTS products to the greatest extent possible.

5) RWSL SERVICE LIFE EXTENSION PROGRAM (SLEP) (19 projects, 1 for each site): Provide approved MLC/ILC, LC, CCR-C, and CCR hardware including spare at all RWSL operational sites. This project may include engineering support services as necessary.

Each qualification project will complete the modification of COTS equipment and lab integration, testing at MMAC, and conclude with key site testing at MCO 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.

This SOW defines the scope of the support services required of the Contractor. The FAA will use Contractor support services for second-level support of the FLS system until it is accepted by the FAA and transitions to FAA ownership.

C-8

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.

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.

Document ID Title

FAA Specifications

FAA-E-3001 Performance Specification, RWSL System

FAA-E-3002 Performance Specification, Field Lighting System

(FLS)

Interface Control Document; RWSL Processor to Field Lighting System (FLS) Interface

FAA-G-2100J Electronic Equipment, General Requirements

FAA-C-1217H FAA Spec. Common 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

840-022120 System/Subsystem Design Document (SSDD)

710-022601 FLS Subsystem System Design Description (SSDD)

FAA Standards

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

C-9

Document ID Title

FAA Orders

Tailored NIST SP 800-53 Rev4 (09/30/20)

ATO ISS Requirements for Authorization - FY23 ATO SSP HIGH Workbook22-1024

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-454B DEPARTMENT OF DEFENSE HANDBOOK: GENERAL

GUIDELINES FOR ELECTRONIC EQUIPMENT (15 APR

2007)

MIL-HDBK-61B MILITARY HANDBOOK: CONFIGURATION

MANAGEMENT GUIDANCE (07 APR 2020)

MIL-DTL-31000C Technical Data Package How to prepare a Technical Data Package to be delivered by MIL-PRF-28000B requirements.

Other

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

Security and Privacy Controls for Information Systems and Organizations

ANSI/EIA-478 Earned Value Management (EVM) System

NIST 800-18 Rev. 1 Guide for Developing Security Plans for Federal Information Systems

SAE AS9100D Quality Management Systems - Requirements for Aviation, Space, and Defense Organizations

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.

C-10

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; REL and THL. A circuit will consist of either REL or THL fixtures and be identified by fixture type.

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-11

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 services to be supplied and supported under this SOW are listed in Section B, Supplies and Services and Prices/Costs, and 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 MCO. 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 listed in Section B, should the need arise. This SOW includes requirements for:

1) Replacements for the MLC/ILC components

2) Replacements for the LC

3) Replacements for the CCR-C

4) Replacements for the CCR for low power consumption circuits

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

6) Test support at the MCO key site installation and testing

7) Field familiarization and Second Level Engineering training to support configuration and troubleshooting at operational site installations

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

9) Technical support provided from the Contractor as needed for installation, evaluation, and testing at operational sites

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. The RWSL FLS sustainment execution workflow

C-12 described in Appendix D2, Preliminary Waterfall Schedule of Sustainment Projects, is considered a significant requirement for success.

C.3.1.1 Compatibility with Existing Baseline of the RWSL System

The RWSL FLS RCP is constrained by existing legacy system infrastructure using Power Line Communication (PLC) technology. Sustainment components must use existing unshielded airfield cable and be fully compatible with the legacy system. During each individual circuit’s sustainment outage, that circuit’s MLC, and associated ILCs will be replaced, configured, tested, and returned to service. LC, CCR-C, and CCR replacements will be addressed on independent schedules. Consequently, the next generation of hardware must functionally integrate 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 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

CPU and Red Hat Enterprise Linux version 8 (or latest version), prior to entry into factory test. The LC will host the software applications necessary to provide an interface between the RWSL processor subsystem and FLS. This new LC will 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) Any Original Equipment Manufacturer (OEM) or third-party software licenses that need to transfer with these products.

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

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

System https://govtribe.com/file/government-file/6973gh18r00016-8-dot-3-rwsl-system-specification-faa-e-3001-rev-09-24-09-dot-pdf

2Dates in Appendix D are notional and may change based upon airport runway construction and / or maintenance.

https://govtribe.com/file/government-file/6973gh18r00016-8-dot-3-rwsl-system-specification-faa-e-3001-rev-09-24-09-dot-pdf https://govtribe.com/file/government-file/6973gh18r00016-8-dot-3-rwsl-system-specification-faa-e-3001-rev-09-24-09-dot-pdf

C-13

b. FAA-E-3002, FAA Performance Specification Runway Status Lights (RWSL) Field Light System (FLS) https://www.faa.gov/airports/engineering/engineering_briefs/media/eb-64d.pdf

c. 700-022100, Product Specification (PS) for the Field Lighting System (FLS) for the Runway Status Lights (RWSL) Program (Can be furnished upon request)

d. 710-022147, Interface Design Description (IDD) for RWSL (Can be furnished upon request)

e. 840-022120, System/Subsystem Design Document (SSDD) (Can be furnished upon request)

f. 710-022601, FLS Subsystem System Design Description (SSDD) (Can be furnished upon request)

g. National Institute of Standards and Technology (NIST) Special Publications 800- 18, Guide for Development of Security Plans for Information Technology Systems https://csrc.nist.gov/publications/detail/sp/800-18/rev-1/final

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

i. The current POAM compliance documentation

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) Field familiarization 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 testing at MCO (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) Second level engineering field familiarization at MMAC for five days

10) 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

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

FAA legacy RWSL

12) An integration plan that minimizes the time the existing RWSL system is removed from service for installation of new equipment

FLS Replacement Component Schedule

The Contractor must include components as listed in Section F Table F10, Estimated Sustainment Components by Site.

https://www.faa.gov/airports/engineering/engineering_briefs/media/eb-64d.pdf https://csrc.nist.gov/publications/detail/sp/800-18/rev-1/final https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final

C-14

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 Appendix D).

FAA Furnished Site and Support

The FAA will provide the following Government 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

Information/Material (e.g. System/Subsystem Design Description, FLS Circuit Optimization Guide, Verification Requirements Traceability Matrix (VRTM),etc.) that can be used as a starting point with probable modification by the Contractor based upon their proposed system components.

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 Operating System (RHEL) platform.

2) The components must integrate with existing 20 kilowatt (kW) L-829 CCR.

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 and ICD.

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

C-15 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. 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 without changes to the existing infrastructure.

12) The Contractor must provide components that meet the interference and susceptibility requirements of the RWSL specifications without changes to the existing infrastructure.

The Contractor must correct deficiencies if a deficiency is found to exist between the system and the requirements.

CCR Mod 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 H 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 H paragraph 3.3.5.1.9.

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

C-16 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-2100H 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 code of green with a yellow stripe.

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

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-019E, FAA-C-1217, and sections eight and nine of IEEE 1100-1996.

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.

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

6) All parts in boxes must be bar coded individually to facilitate tracking of parts and serial numbers

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

8) All LRU labels must be in Helvetica at 42 point font size

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

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

VOLTS TURN OFF POWER BEFORE SERVICING”.

C-17

11) 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.

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

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

C.5 Program Management

Program Management and Status Reporting

The Contractor must provide the necessary program management, as ordered, 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) 30 days after the contract award.

The Program Management Plan describes the contractor’s overall strategy and approach to managing the RWSL- FLS Replacement activities under this contract. It also provides details on management processes, organization design, and roles and responsibilities of key personnel and teammates. In addition, the Program Management Plan includes 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 and ensure that cost, schedule, and quality requirements for each Delivery Order are continually tracked with status communicated to the FAA to ensure that each Delivery Order 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 monthly Program Status Reports in accordance with CDRL PM 02 informing the Government of the Contractor’s assessment of contractual effort as of the date of the report. It covers 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 task

b) Status of individual deliverables

c) Identification of risk areas with recommended remedial actions

d) Status of all outstanding risks identified in the previous CFSRMSFRs

C-18

e) Additional information pertinent to the FAA in administering the performance of this effort or when directed by the 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 performance and accomplishments for the approved delivery orders 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 05, 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 task orders, (d) determining funds in excess of contract needs and available for de-obligation, (e) assessing the financial risks, and (f) obtaining an estimate of termination costs. The CFSR will be for active Delivery Orders, based on the deliverables identified in the applicable delivery order. 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

CDRL PM 01 Program Management Plan (PMP) CDRL PM 02 Program Status Report (PSR) CDRL PM 03 Integrated Master Schedule (IMS) CDRL PM 05 Contract Funds Status Report

Program Reviews

The Contractor must conduct PMRs in accordance with CDRL PM 04 to demonstrate the successful completion, or progress toward completion, of project milestones, across all Delivery Orders. PMRs must be provided quarterly, or as requested by the government, 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

C-19 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 07

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 07 within 10 working days. The Contractor is responsible for tracking and ensuring completion of all action items.

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

CDRL PM 07 Meeting Agenda and Minutes

Earned Value Management (EVM)

EVM must be provided through the Program Status Report in accordance with PM 02 that includes an IMS, monthly PMRs and Risk Management that specifically tracks cost, schedule and risk on a monthly basis.

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 calendar 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 PAC must be documented in accordance with CDRL PM07, Meeting Agenda and Minutes.

Integrated Baseline Review (IBR)

The Contractor must conduct an integrated baseline review no later than 120 days after the contract award 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

C-20

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 PM07, Meeting Agenda and Minutes.

In accordance with CDRL PM 06, the Contractor must develop and maintain a Contractor Work Breakdown Structure (CWBS) and dictionary based on the AMS Work Breakdown Structure, as noted in Sections 3 and 4 at https://fast.faa.gov/AMSBB_AMS_Building_Blocks.cfm. 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 06 Contractor Work Breakdown Structure and Dictionary

C.6 Engineering

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 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, cost, schedule, performance, and technical guidance. The Post Award Conference, Program Management Review, System Engineering Reviews (SRR, PDR, CDR) and Integrated Baseline Review are considered TIMs for the purpose of this Contract. All TIMs will be fully documented in accordance with CDRL PM07, Meeting Agenda and Minutes. All action items resulting from the TIMs will be documented and tracked to completion by the Contractor.

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 six weeks after the contract award, the Contractor must present to the RWSL https://fast.faa.gov/AMSBB_AMS_Building_Blocks.cfm

C-21 program office a schedule for design, preliminary, and critical 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 07. 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 and audits.

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 described in Section H, Special Contract Requirements, 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 20 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 contractual requirements. Formal reviews will not be considered complete until approval by the FAA is granted in writing.

C.6.2.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 status of all action items must be tracked 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

C-22 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

c) Disapproval indicating that the review was not satisfactory, and to identify those areas that were deficient. The Contractor must have 20 days to respond to the FAA and provide a plan to maintain and complete the program schedule.

System Requirements Review (SRR)

The Contractor must conduct a System Requirements Review (SRR) 6 weeks after the contract award in accordance with CDRL SE 01 The objective of this review is to ascertain the adequacy of the Contractor efforts in understanding and meeting system requirements.

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 problems that the sustainment contract is designed to solve. As part of the SRR, the Contractor must present and review the following documents with the FAA:

1) Software Development Plan (SDP) in accordance with CDRL SW 01.

2) Flows and system requirements definitions

3) Critical task analysis

4) Functional external system interfaces

5) System safety program considerations

6) Security considerations and identification of security related requirements

7) Plans for key activities such as testing or site visits

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

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

10) Identification of risks and plan for management or mitigation of risks, issues, and opportunities (RIOs).

11) Technical performance metrics and measures

SRR Acceptance Criteria

The SRR acceptance criteria are as follows:

1) Demonstration of analysis and a thorough understanding of the requirements in the

RWSL System Specification FAA-E-3001, FLS Specification FAA-E-3002, and the SOW. A complete list of specifications, handbooks, orders, standards, and drawings can be found in Section C.1.3

2) Initiation of the system integration and functional requirements baseline fully traceable to

C-23 the requirements in the RWSL System and FLS Specifications, SOW, and other related documents approved by the FAA

3) Resolution, or a plan for resolution acceptable to the FAA, of all action items

Preliminary Design Review (PDR)

The Contractor must conduct a PDR 120 days after the contract award in accordance with PM 03, Integrated Master Schedule. This review must be conducted for an aggregation of configuration items. This review must evaluate software and hardware requirements definitions, and evaluate design of each Hardware Configuration Item (HWCI) and Computer Software Configuration Item (CSCI). The objective of this review is to establish the software and hardware requirements baseline, and to approve the high-level design of each configuration item.

The SRR must be approved by the FAA before a PDR may be conducted, and all SRR action items must be closed prior to conducting the PDR, unless the FAA has given permission to proceed.

During the PDR, the Contractor must present data flow and control flow diagrams describing design solutions for each configuration item. During the PDR, the Contractor must present software and hardware requirements defined and recorded for each CSCI and HWCI, the methods to be used to ensure that each requirement has been met, and the traceability between the CSCI/HWCI requirements and system requirements.

For items that are not Contractor developed, the Contractor must provide a functional/physical description and define technical requirements and interfaces with other system components. For these non-developmental items, the Contractor must provide the results of the analysis that verifies the item will meet the associated technical requirements and the methods used to ensure that each requirement has been met. The Contractor must describe its plans for acquiring and developing the required software to meet contract requirements. During the PDR, the Contractor must present CSCI/HWCI-wide design decisions (i.e., decisions about the CSCI/HWCI's behavioral design and other decisions affecting the selection and design of the software components comprising the CSCI) defined and recorded for each CSCI/HWCI, and the traceability between design requirements and software/hardware requirements for each CSCI/HWCI. Configuration control of COTS software is the responsibility of the Contractor. If the Contractor chooses to modify commercial software, they must supply the justification for the change to the FAA. The justification must state the method of documentation and use common methods for documenting changes to software. At the PDR, the Contractor must describe the products, processes, methodologies, milestones, and measurements to be used in conducting software development activities. Overall technical program risks must be reviewed on a technical, cost, and schedule basis.

As part of the PDR, the Contractor must deliver and review the following documents with the

C-24

FAA:

Deliverables in accordance with CDRL PM 04, with overview of the following documents:

1) Preliminary System/Subsystem Design Description (SSDD)

2) Preliminary Software Requirements Specification (SRS)

3) Preliminary Software Design Description (SDD) (SW 02)

4) Preliminary Production Acceptance Test and Evaluation (PAT&E) Plan

PDR Acceptance Criteria

The PDR acceptance criteria are as follows. To successfully complete the PDR, the Contractor must:

1) Define and baseline high-level software/hardware requirements for all CSCIs/HWCIs

2) Provide a traceability of the requirements baseline to the system requirements

3) Define high-level design requirements for each CSCI

4) Provide traceability of the design requirements to the CSCI/HWCI requirements

5) Document interfaces between computer software components within each CSCI and with external configuration items

6) Recommend test resources, test requirements, and test schedule for the formal qualification testing of CSCIs under review

7) For each HWCI and CSCI, identify which requirements are satisfied by COTS products..

8) Present a preliminary design that shows how COTS equipment will work together to satisfy the requirements baseline

9) Demonstrate how the contractor’s design will comply with System/subsystem Design

Description (SSDD) and FLS Subsystem System Design Description (SSDD), Software Requirements Specification (SRS), and Software Design Description (SDD).

10) Provide a preliminary System/Subsystem Design Description (SSDD) and FLS Subsystem System Design Description (SSDD), and final in accordance with TE 01 and Risk Assessment Report (RAR) that are acceptable to the FAA,

11) Resolution, or an acceptable plan for resolution, of all action items

CDRL TE 01 Contractor’s Master Test Plan

Critical Design Review (CDR)

The Contractor must conduct a Critical Design Review (CDR) 180 days after the contract award in accordance with PM 03.