Federal Aviation Administration

Runway Status Lights

Section C: Statement of Work

![](media/image1.png){width="2.3125in" height="2.21875in"}

**Federal Aviation Administration**

**800 Independence Avenue, SW**

Washington, DC 20591

[C.1 Introduction 1](#introduction)

[C.1.1 Background 1](#background)

[C.1.2 Scope 2](#scope)

[C.2 Applicable Documents 2](#applicable-documents)

[C.2.1 Obtaining Copies of Documents 6](#obtaining-copies-of-documents)

[C.3 System Requirements 7](#system-requirements)

[C.3.1 Program Management 7](#program-management)

[C.3.1.1 Program Management Planning and Status Reporting
7](#program-management-planning-and-status-reporting)

[C.3.1.2 Program Metrics 7](#program-metrics)

[C.3.1.3 Contract Work Breakdown Structure
8](#contract-work-breakdown-structure)

[C.3.1.4 Risk Management 8](#risk-management)

[C.3.1.5 Earned Value Management 8](#earned-value-management)

[C.3.1.6 Integrated Master Schedule 9](#integrated-master-schedule)

[C.3.1.7 Program Reviews 9](#program-reviews)

[C.3.1.8 System Safety Program 16](#system-safety-program)

[C.3.1.9 Configuration Management Program
18](#configuration-management-program)

[C.3.1.10 Quality Management 23](#quality-management)

[C.3.2 Systems Engineering and Design Development
23](#systems-engineering-and-design-development)

[C.3.2.1 Systems Engineering Documentation
23](#systems-engineering-documentation)

[C.3.2.2 System/Subsystem Design Description
23](#systemsubsystem-design-description)

[C.3.2.3 Interface Control Documentation
24](#interface-control-documentation)

[C.3.2.4 Human Engineering Design 24](#human-engineering-design)

[C.3.2.5 Engineering Services 25](#engineering-services)

[C.3.3 Software Development 26](#software-development)

[C.3.3.1 System Software Design 26](#system-software-design)

[C.3.4 System Test and Evaluation 31](#system-test-and-evaluation)

[C.3.4.1 Development Test and Evaluation
32](#development-test-and-evaluation)

[C.3.4.2 Operational Test and Evaluation
40](#operational-test-and-evaluation)

[C.3.4.3 Regression Tests 40](#regression-tests)

[C.3.4.4 Production Acceptance Test and Evaluation (PAT&E)
41](#production-acceptance-test-and-evaluation-pate)

[C.3.5 Construction, Delivery, Installation and Checkout
41](#construction-delivery-installation-and-checkout)

[C.3.5.1 Implementation Management 42](#implementation-management)

[C.3.5.2 Construction 44](#construction)

[C.3.5.3 System Installation 48](#system-installation)

[C.3.6 Integrated Logistics Support 51](#integrated-logistics-support)

[C.3.6.1 ILS Program Management 51](#ils-program-management)

[C.3.6.2 Integrated Support Plan 52](#integrated-support-plan)

[C.3.6.3 RWSL Maintenance Concept 52](#rwsl-maintenance-concept)

[C.3.6.4 Logistics Management Information
53](#logistics-management-information)

[C.3.6.5 Supply Support 53](#supply-support)

[C.3.6.6 Technical Data 54](#technical-data)

[C.3.6.7 Technical Operations Specialists Training
59](#technical-operations-specialists-training)

[C.3.6.8 Air Traffic Training 66](#air-traffic-training)

[C.3.6.9 Second Level Engineering Training
67](#second-level-engineering-training)

[C.3.6.10 Contractor Support and Services
68](#contractor-support-and-services)

[C.3.6.11 Interim Contractor Depot Logistics Support Requirements
70](#interim-contractor-depot-logistics-support-requirements)

[C.3.6.12 Post-Commissioning Technical Site Support
72](#post-commissioning-technical-site-support)

[C.3.6.13 System Support Equipment/Facilities Services
72](#system-support-equipmentfacilities-services)

[C.3.6.14 Contractor Support Services 74](#contractor-support-services)

[C.4 Full Production and Deployment Requirements
75](#full-production-and-deployment-requirements)

[C.4.1 Depot Setup 75](#depot-setup)

[C.4.2 Interim Contractor Depot Level Support Transition Plan (ICDLSTP)
75](#interim-contractor-depot-level-support-transition-plan-icdlstp)

[C.4.2.1 Tools and Test Equipment List
75](#tools-and-test-equipment-list)

[C.4.2.2 Depot Test Equipment Manuals 76](#depot-test-equipment-manuals)

[C.4.2.3 Depot Test Procedures 76](#depot-test-procedures)

[C.4.2.4 Depot Repair/Support Training
76](#depot-repairsupport-training)

[C.4.3 FAA Academy Training Support System
77](#faa-academy-training-support-system)

[C.5 Acronyms 78](#acronyms)

## Introduction 

This Statement of Work (SOW) describes the work required for the
Contractor to design, develop, produce, test, construct, install, and
provide support for the implementation of the Runway Status Lights
(RWSL) system at up to 35 airports, plus options for an additional three
(3) support systems. The RWSL system consists of the RWSL processor and
the Field Lighting System (FLS). This SOW states the requirements for:

a)  First Article (FA/pre-production) (1 each) of RWSL System at the
    Designated Key Site.

b)  Software design, integration, systems logistics support for the
    production (post FA acceptance), construction and installation of
    the RWSL processor and FLS (20 each)

c)  FLS installation and integration of the RWSL processor with the FLS
    (same 20 sites referenced in B)

d)  Depot Level Support

e)  Options for construction and installation of the FLS for up to 14
    additional sites, plus up to three support systems

f)  Options for integration of the RWSL processor with the FLS for up to
    14 additional sites, plus up to three support systems

g)  The items above (a-f) include the use of Commercial-off-the-Shelf
    (COTS) equipment where applicable and modified COTS for the FLS

### Background 

The Federal Aviation Administration (FAA) is dedicated to the goal of
enhancing runway safety while maximizing operational efficiency and
ensuring airport capacity. The reduction of runway incursions is one of
the most important aviation safety initiatives and is crucial for the
improvement of runway safety.

RWSL offer a means of reducing runway incursions and preventing runway
accidents. They do so by indicating to pilots and vehicle operators that
a runway is unsafe for entry or crossing or that a runway is unsafe for
departure, thereby increasing situational awareness. Direct pilot and
vehicle operator notification is required because surface surveillance
and air traffic controller tools alone cannot prevent some types of
runway incursions and accidents that are time critical. The RWSL display
critical, time-sensitive safety status information directly to pilots
and vehicle operators reducing the time it takes to alert them of
potentially unsafe situations. This need is identified in the National
Transportation Safety Board (NTSB) most wanted transportation safety
improvements. The NTSB action recommends that the FAA "Implement a
safety system for ground movement that will ensure the safe movement of
airplanes on the ground and provides direct warning capability to the
flight crews". This is a new capability and does not replace any
existing National Airspace System (NAS) assets.

The RWSL software detects the presence and motion of aircraft and
surface vehicles on or near the runways, assesses any possible conflicts
with other surface traffic, illuminates red runway-entrance lights
(RELs) if the runway is unsafe for entry or crossing, and illuminates
red takeoff-hold lights (THLs) if the runway is unsafe for departure.
The system turns the lights off automatically as appropriate when the
runway is no longer unsafe.

The RWSL system consists of an RWSL processor and an FLS. The RWSL
processor receives surveillance data of aircraft and vehicles on or near
the airport surface from the Airport Surface Detection Equipment Model
-- X (ASDE-X) surface surveillance system. The RWSL processor uses this
surveillance data to determine when to activate and deactivate the RELs
and THLs. These light commands are sent to the RWSL FLS. The FLS
includes a Light Computer, in-pavement light fixtures, and all light
system circuitry. The FLS receives the light commands and illuminates
and extinguishes the lights as commanded by the RWSL processor. The
system will automatically determine runway configurations and will
adjust the activation and deactivation of RELs and THLs accordingly. The
system will automatically adjust light intensity according to time of
day. The intended service life for RWSL is a minimum of 20 years.

RWSL does not significantly increase air traffic controller workload,
nor decrease airport capacity, but rather works in concert with existing
and new procedures to enhance runway safety. Controllers are not
required to monitor RWSL light illumination and extinguishing. The
ground surveillance system safety logic hold bars are independent of the
RWSL lights. The lights are driven automatically using computer
processing of integrated surface and terminal surveillance information.

### Scope 

This SOW defines the requirements for the Contractor development,
production, construction, installation, checkout, test and support for
implementation of the RWSL system across designated FAA airports. The
RWSL system includes all hardware, software, firmware, interfaces,
commercial and non-commercial licenses, special support and test
equipment necessary to meet the requirements of the RWSL System
Specification FAA-E-3001, FLS Specification FAA-E-3002, and this SOW.

This SOW encompasses the requirements for all resources required of the
Contractor to produce, deliver, install, test and provide support for
additional RWSL systems beyond the first article system.

## 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 as of the contract date
shall apply. In the event of conflict between this SOW and any of the
applicable documents cited below, the provisions of this SOW shall
apply.

**Table 1: Applicable Documents**

+-----------------------+----------------------------------------------+
| **Document Number**   | **Title**                                    |
+=======================+==============================================+
| **[FAA                |                                              |
| Specifica             |                                              |
| tions:]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| FAA-C-1391B           | Installation and Splicing of Underground     |
|                       | Cables                                       |
+-----------------------+----------------------------------------------+
| FAA-E-3001            | Performance Specification, RWSL System       |
+-----------------------+----------------------------------------------+
| FAA-E-3002            | Performance Specification, Field Lighting    |
|                       | System (FLS)                                 |
+-----------------------+----------------------------------------------+
| FAA-E-2761A           | Cable, Fiber Optic, Multimode, Multifiber    |
+-----------------------+----------------------------------------------+
| FAA-E-2942            | ASDE-X System Specification,                 |
+-----------------------+----------------------------------------------+
|                       | Interface Requirements Document, ASDE-X to   |
|                       | RWSL                                         |
+-----------------------+----------------------------------------------+
|                       | Interface Design Document for the ASDE-X     |
|                       | Program, Version 11, August 10, 2007.        |
+-----------------------+----------------------------------------------+
|                       | Interface Control Document; RWSL Processor   |
|                       | to Field Lighting System (FLS) Interface     |
+-----------------------+----------------------------------------------+
| FAA-C-1217F           | Electrical Work, Interior                    |
+-----------------------+----------------------------------------------+
| FAA-G-2100H           | Electronic Equipment, General Requirements   |
+-----------------------+----------------------------------------------+
| FAA-D-2494B           | Technical Instruction Book Manuscripts:      |
|                       | Electronic, Electrical, and Mechanical       |
|                       | Equipment, Requirements for Preparation of   |
|                       | Manuscript and Production of Book            |
+-----------------------+----------------------------------------------+
| **[FAA                |                                              |
| Stan                  |                                              |
| dards:]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| FAA-STD-002F          | Standard Engineering Drawing Preparation and |
|                       | Support                                      |
+-----------------------+----------------------------------------------+
|                       |                                              |
+-----------------------+----------------------------------------------+
| FAA-STD-019E          | Lightning Protection, Grounding, Bonding,    |
|                       | and Shielding Requirements for Facilities    |
+-----------------------+----------------------------------------------+
| FAA-STD-025F          | Preparation of Interface Documentation       |
+-----------------------+----------------------------------------------+
| FAA-STD-026A          | Software Development for the National        |
|                       | Airspace System (NAS)                        |
+-----------------------+----------------------------------------------+
| FAA-STD-028C          | Contract Training Programs                   |
+-----------------------+----------------------------------------------+
| FAA-STD-032           | Design Standards for National Airspace       |
|                       | Facilities                                   |
+-----------------------+----------------------------------------------+
| FAA-STD-39C           | National Airspace System (NAS) Open System   |
|                       | Architecture and Protocols                   |
+-----------------------+----------------------------------------------+
| FAA-STD-057           | Airport Fiber Optic Communications System    |
|                       | (FOCS) Standards                             |
+-----------------------+----------------------------------------------+
| **[FAA Advisory       |                                              |
| Cir                   |                                              |
| culars]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Ground Vehicle Operations on Airports        |
| AC 150/5210-20        |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Airport Design Standards                     |
| AC 150/5300-13        |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Airport Pavement Design and Evaluation       |
| AC 150/5320-6D        |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Measurement, Construction and Maintenance of |
| AC 150/5320-12C       | Skid Resistant Airport Pavement Surfaces     |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Pavement Surface Evaluation and Rating       |
| AC 150/5320-17        | Manuals                                      |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Standardized Method of Reporting Airport     |
| AC 150/5335-5A        | Pavement Strength                            |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Design and Installation of Airport Visual    |
| AC 150/5340-30C       | Aids                                         |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Approved Airport Equipment                   |
| AC 150/5345-1V        |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for L-821, Panels for the      |
| AC 150/5345-3F        | Control of Airport Lighting                  |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Circuit Selector Switch                      |
| AC 150/5345-5B        |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for L-824 Underground          |
| AC 150/5345-7E        | Electrical Cable for Airport Lighting        |
|                       | Circuits                                     |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for Constant Current           |
| AC 150/5345-10F       | Regulators and Regulator Monitors            |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | FAA Specification for L-823 Plug and         |
| AC 150/5345-26C       | Receptacle, Cable Connectors                 |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for Airport Lighting Bases,    |
| AC 150/5345-42F       | Transformer Housings, Junction Boxes, and    |
|                       | Accessories                                  |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for Runway and Taxiway Light   |
| AC 150/5345-46C       | Fixtures                                     |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Specification for Series to Series Isolation |
| AC 150/5345-47B       | Transformers for Airport Lighting Systems    |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Airport Lighting Equipment Certification     |
| AC 150/5345-53C       | Program                                      |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Operational Safety on Airports During        |
| AC 150/5370-2E        | Construction                                 |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Standards for Specifying Construction of     |
| AC 150/5370-10C       | Airports                                     |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Use of Nondestructive Testing Devices in the |
| AC 150/5370-11A       | Evaluation of Airport Pavement               |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Quality Control of Construction for Airport  |
| AC 150/5370-12A       | Grant Projects                               |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Off-Peak Construction of Airport Pavements   |
| AC 150/5370-13A       | Using Hot-Mix Asphalt                        |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Hot-Mix Asphalt Paving Handbook              |
| AC 150/5370-14A       |                                              |
+-----------------------+----------------------------------------------+
| FAA Advisory Circular | Rapid Construction of Rigid (Portland Cement |
| AC 150/5370-16        | Concrete) Airfield Pavements                 |
+-----------------------+----------------------------------------------+
| **[Military Standards |                                              |
| &                     |                                              |
| Han                   |                                              |
| dbooks]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| MIL-HDBK-61A          | Configuration Management Guidance            |
+-----------------------+----------------------------------------------+
| MIL-STD-129P          | Military Marking                             |
+-----------------------+----------------------------------------------+
| MIL-HDBK-470A         | Designing and Developing Maintainable        |
|                       | Products                                     |
|                       |                                              |
|                       | and Systems Volume I                         |
+-----------------------+----------------------------------------------+
| MIL-HDBK-781A         | Reliability Test Methods, Plans, and         |
|                       | Environments for Engineering Development,    |
|                       | Qualification, and Production                |
+-----------------------+----------------------------------------------+
| MIL-PRF-28000B        | Digital Representation for Communication of  |
|                       | Product Definition Data: IGES Application    |
|                       | Subsets and IGES Application Protocols       |
+-----------------------+----------------------------------------------+
| MIL-DTL-31000C        | Technical Data Package                       |
+-----------------------+----------------------------------------------+
| MIL-HDBK-46855A       | Human Engineering Program Process and        |
|                       | Procedures                                   |
+-----------------------+----------------------------------------------+
| MIL-PRF-49506         | Performance Specification, Logistics         |
|                       | Management Information                       |
+-----------------------+----------------------------------------------+
| **[Federal            |                                              |
| Doc                   |                                              |
| uments]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| Executive Order 12699 | Seismic Safety of Federal and Federally      |
|                       | Assisted or Regulated New Building           |
|                       | Construction                                 |
+-----------------------+----------------------------------------------+
| Executive Order 12941 | Seismic Safety of Existing Federally Owned   |
|                       | or Leased Buildings                          |
+-----------------------+----------------------------------------------+
|                       |                                              |
+-----------------------+----------------------------------------------+
| Executive Order 13423 | Strengthening Federal Environmental, Energy  |
|                       | and Transportation Management                |
+-----------------------+----------------------------------------------+
| 10 CFR 435            | Energy Efficiency Standards for New Federal  |
|                       | Low-Rise Residential Buildings               |
+-----------------------+----------------------------------------------+
| 14 CFR Part 77        | Objects Affecting Navigable Airspace         |
+-----------------------+----------------------------------------------+
| 29 CFR 1910           | Occupational Safety and Health Standards     |
+-----------------------+----------------------------------------------+
| 29 CFR 1926           | Safety and Health Regulations for            |
|                       | Construction                                 |
+-----------------------+----------------------------------------------+
| 29 CFR 1960.17        | Alternate Standards                          |
+-----------------------+----------------------------------------------+
| 29 CFR 1960.8         | Agency Responsibilities                      |
+-----------------------+----------------------------------------------+
| 47 CFR 2              | Frequency Allocations and Radio Treaty       |
|                       | Matters; General Rules and Regulations       |
+-----------------------+----------------------------------------------+
| 47 CFR 15             | Radio Frequency Devices                      |
+-----------------------+----------------------------------------------+
|                       | Federal Information Security Management Act  |
|                       | of 2002 (FISMA)                              |
+-----------------------+----------------------------------------------+
|                       | Federal Emergency Management Administration  |
|                       | (FEMA) Handbook 224, ICSSC RP-4              |
+-----------------------+----------------------------------------------+
|                       | National Environmental Policy Act (NEPA) of  |
|                       | 1969                                         |
+-----------------------+----------------------------------------------+
|                       | Environmental Protections Agency (EPA)       |
|                       | National and Local Building Codes            |
+-----------------------+----------------------------------------------+
|                       | Occupational Safety and Health               |
|                       | Administration (OSHA) Standards national and |
|                       | Local Building Codes                         |
+-----------------------+----------------------------------------------+
|                       | National Energy Conservation Policy Act      |
+-----------------------+----------------------------------------------+
| NFPA No. 70           | National Fire Protection Association,        |
|                       | National Electrical Code (NFPA) 70           |
+-----------------------+----------------------------------------------+
| NFPA No. 78           | National Fire Protection Association,        |
|                       | Lightning Protection Code                    |
+-----------------------+----------------------------------------------+
| DOT/FAA/CT03/05       | Human Factors Design Standard for            |
| (HF-STD-001)          | Acquisition of Commercial-off-the-Shelf      |
|                       | Subsystems, Non-Developmental Items, and     |
|                       | Developmental Systems                        |
+-----------------------+----------------------------------------------+
| **[Other FAA          |                                              |
| Doc                   |                                              |
| uments]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| FAA Order 1050.1E     | Policies and Procedures for Considering      |
|                       | Environmental Impacts                        |
+-----------------------+----------------------------------------------+
| FAA Order 1050.10C    | Prevention, Control, and Abatement of        |
|                       | Environmental Pollution at FAA Facilities    |
+-----------------------+----------------------------------------------+
| FAA Order 1050.14A    | Polychlorinated Biphenyls (PCBs) in the NAS  |
+-----------------------+----------------------------------------------+
| FAA Order 1050.18     | Chlorofluorocarbons and Halon Use at FAA     |
|                       | Facilities                                   |
+-----------------------+----------------------------------------------+
| FAA Order 1050.19B    | Environmental Due Diligence Audits in the    |
|                       | Conduct of FAA Real Property Transactions    |
+-----------------------+----------------------------------------------+
| FAA Order 1053.1A     | Energy and Water Management Program for FAA  |
|                       | Buildings and Facilities                     |
+-----------------------+----------------------------------------------+
| FAA Order 1370.82A    | Information Systems Security Program         |
+-----------------------+----------------------------------------------+
| FAA Order 1600.1E     | Personnel Security Program                   |
+-----------------------+----------------------------------------------+
| FAA Order 1600.2E     | Safeguarding Classified National Security    |
|                       | Information                                  |
+-----------------------+----------------------------------------------+
| FAA Order 1600.6E     | Facility Security Policy                     |
+-----------------------+----------------------------------------------+
| FAA Order 1600.69B    | FAA Facility Security Management Program     |
+-----------------------+----------------------------------------------+
| FAA Order 1600.72A    | Contractor and Industrial Security Program   |
+-----------------------+----------------------------------------------+
| FAA Order 1600.73     | Contractor and Industrial Security Program   |
|                       | Operating Procedures                         |
+-----------------------+----------------------------------------------+
| FAA Order 1600.75     | Protecting Sensitive Unclassified            |
|                       | Information (SUI)                            |
+-----------------------+----------------------------------------------+
| FAA Order 1800.66     | Configuration Management Policy              |
+-----------------------+----------------------------------------------+
| FAA Order 3000.22     | Air Traffic Services Training                |
+-----------------------+----------------------------------------------+
| FAA Orders 3120.4L    | Air Traffic Technical Training               |
+-----------------------+----------------------------------------------+
| FAA Order 3900.19B    | FAA Occupational Safety And Health Program   |
+-----------------------+----------------------------------------------+
| FAA Order 3900.57     | FAA Pre-Construction and Maintenance Project |
|                       | Safety and Health Checklist                  |
+-----------------------+----------------------------------------------+
| FAA Order 4800.8A     | Utilization and Disposal of Excess and       |
|                       | Surplus Personal Property                    |
+-----------------------+----------------------------------------------+
| FAA Order 6000.30D    | National Airspace System Maintenance Policy  |
+-----------------------+----------------------------------------------+
| FAA Order 6000.36A    | Communications Diversity                     |
+-----------------------+----------------------------------------------+
| FAA Order 6000.53B    | Remote Maintenance Monitoring Interface      |
|                       | Development and Implementation               |
+-----------------------+----------------------------------------------+
| FAA Order 6200.4F     | Test Equipment Management                    |
+-----------------------+----------------------------------------------+
| FAA Order 6950.22     | Maintenance of Electrical Power and Control  |
|                       | Cables                                       |
+-----------------------+----------------------------------------------+
| FAA Order 6950.27     | Short Circuit Analysis and Protective Device |
|                       | Coordination                                 |
+-----------------------+----------------------------------------------+
| FAA Order 6950.2D     | Electrical Power Policy Implementation at    |
|                       | National Airspace System Facilities          |
+-----------------------+----------------------------------------------+
| FAA Order 6970.3A     | Maintenance of Environmental Systems         |
+-----------------------+----------------------------------------------+
| FAA Order 8040.4      | Safety Risk Management                       |
+-----------------------+----------------------------------------------+
| FAA Order 9550.8      | Human Factors Policy                         |
+-----------------------+----------------------------------------------+
| ATO-S 2006-1 Version  | Safety Risk Management Guidance for System   |
| 1.4a                  | Acquisitions                                 |
+-----------------------+----------------------------------------------+
| SMS Manual            | FAA Safety Management System (SMS) Manual    |
|                       | (version 1.1) dated May 21, 2004.            |
+-----------------------+----------------------------------------------+
| **[Non-Government     |                                              |
| Doc                   |                                              |
| uments]{.underline}** |                                              |
+-----------------------+----------------------------------------------+
| ANSI/AIM-BC1          | Uniform Symbology Specification Code 39      |
+-----------------------+----------------------------------------------+
| ANSI/EIA-649-A 2004   | National Consensus Standard for              |
|                       | Configuration Management                     |
+-----------------------+----------------------------------------------+
| ANSI/EIA-748B         | Earned Value Management System (Published    |
|                       | June 2007)                                   |
+-----------------------+----------------------------------------------+
| ASTM-D3951-98 (2004)  | "Standard Practice for Commercial Packaging  |
+-----------------------+----------------------------------------------+
| ANSI/ISO/ASQ          | AMERICAN NATIONAL STANDARD, Quality          |
| Q9001-2000            | management system -- Requirements            |
+-----------------------+----------------------------------------------+
| ISO/IEC 90003-2004    | Software engineering -- Guidelines for the   |
|                       | Application of ISO 9001-2000 to the          |
|                       | development of computer software             |
+-----------------------+----------------------------------------------+
| IEEE/EIA 12207.0      | Industry Implementation of International     |
|                       | Standard ISO/IEC 12207:1995 -- Software Life |
|                       | Cycle Processes (ISO/IEC 12207:1995, MOD)    |
+-----------------------+----------------------------------------------+
| ISO 10007:2003        | Quality Management Systems -- Guidelines for |
|                       | Configuration Management                     |
+-----------------------+----------------------------------------------+
| RTCA DO-278           | Guidelines for Communication, Navigation,    |
|                       | Surveillance, and Air Traffic Management     |
|                       | (CNS/ATM) Systems Software Integrity         |
|                       | Assurance                                    |
+-----------------------+----------------------------------------------+

###  Obtaining Copies of Documents 

a\. Copies of FAA specifications and interface documents may be obtained
from the Federal Aviation Administration, Headquarters Public Inquiry
Center APA-230, 800 Independence Avenue SW, Washington, DC 20591,
202-267-3484. Requests should fully identify material desired and cite
the solicitation or contract number.

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

c\. Copies of Military Standards and Specifications may be obtained via
the following website, http://dodssp.daps.dla.mil/.

d\. Copies of ISO/ASQ Q9001-2000 and ISO/IEC 90003-2004 can be obtained
from the following source: American Society for Quality Control 600
North Plankinton Avenue P.O. Box 3005; Milwaukee, Wisconsin 53201-3005.
Phones: (414) 272-8575 or (800) 248-1946. The fax is: (414) 272-1734.

e\. Copies of the Acquisition Management System Test and Evaluation
Process Guidelines are available in the FAA Acquisition System Toolset
(FAST). The on-line internet address of FAST is: <http://fast.faa.gov/>.

##  System Requirements

### Program Management

#### Program Management Planning and Status Reporting

The Contractor shall provide the necessary program management, including
but not limited to, project management, risk management, data
management, configuration management, subcontract management, financial,
cost, and earned value management, schedule management, and resource
management, to accomplish the requirements of this SOW. The Contractor
shall submit a Program Management Plan (PMP) in accordance with CDRL
PM01.

The Contractor shall assign a designated Program Manager (PM) to manage
this effort. The PM shall be the point of contact between the FAA and
the Contractor in the execution of this program and shall be prepared at
all times, given reasonable notice, to present and discuss with the FAA
the status of contract activities.

The Contractor shall continuously monitor the performance of this
contract, and of all subcontracts, to provide the Government with a
timely assessment of program progress or problems, and to control the
contract activities as well as subcontractor and vendor activities. The
Contractor shall establish a schedule designed to accomplish the tasks
described in this contract. The schedule shall be maintained in an
Integrated Master Schedule (IMS) (3.1.6), and shall include both planned
dates and actual completion dates.

The contractor shall submit monthly Program Status Reports (PSR) in
accordance with the CDRL PM02.

CDRL PM01 Program Management Plan

CDRL PM02 Program Status Report

#### Program Metrics 

The Contractor shall track and report program metrics. These metrics
shall include the following:

-   Program Software Cost and Schedule (Contract Performance
    Measurement)

-   Program Staffing (Software Effort)

-   Program Requirements (Stability Measure)

-   Program Quality (Software Errors)

-   Software Program Size (Source Lines of Code)

-   Construction and implementation metrics

-   Technical Performance Measures

For the Software Program Size (Source Lines of Code) metric, the
Contractor shall prepare two sub-metrics (including charts). One
sub-metric is for tracking Contractor-developed code only. The second
sub-metric is for total non-COTS software in RWSL.

CDRL PM03 Program Metrics Report

#### Contract Work Breakdown Structure 

The Contractor shall develop and maintain a Contract Work Breakdown
Structure (CWBS) and dictionary based on the Acquisition Management
System (AMS) Work Breakdown Structure (WBS), particularly in Sections 3
and 4 located at <http://fast.faa.gov/wbs/wbssec.htm>. The Contractor
shall not change the CWBS or associated definitions without Government
approval. Major elements that are sub-contracted shall be identified in
the CWBS.

CDRL PM04 Contractor Work Breakdown Structure

####  Risk Management

The Contractor shall establish, implement and maintain a Risk Management
(RM) program that provides for an overall strategy and approach for
effectively managing cost, schedule, and technical performance risks
throughout the performance of the contract. The Contractor shall prepare
and submit a Risk Management Plan (RMP), in accordance with CDRL PM05,
that describes how the team intends to perform timely risk
identification, accurate risk assessment, determination and
implementation of mitigation plans, monitoring, tracking, and reporting
of risks items and risk management activities. The Contractor shall
include risk items identified by the Government and the subcontractors.
The risk item information (risk description, assessment and mitigation
plans) shall be reported on a monthly basis to the government in the
Risk Assessment Report (RAR) in accordance with CDRL PM06. The
Contractor shall provide the status of, and mitigation actions for,
identified medium and high program risks, with the exception of security
risks, at Program Management Reviews (PMRs) (3.1.7.2).

The Contractor shall also complete the following requirements:

-   Identify and quantify risks with respect to the impact on
    development, integration, manufacturing, test, installation,
    performance, schedule, and cost.

-   Develop and maintain a list identifying, analyzing, and classifying
    program risks. Program risks shall be classified as low, medium, or
    high priority.

-   Propose risk management techniques and define risk mitigation plans
    for medium and high priority risks.

-   Provide updates to the risk analysis status and risk mitigation
    plans through the Risk Assessment Reports and in the Program
    Management Reviews (PMR).

CDRL PM05 Risk Management Plan

CDRL PM06 Risk Assessment Report

####  Earned Value Management 

The Contractor shall establish, maintain, and use in the performance of
this contract, an integrated performance management system. Central to
this integrated system shall be a validated Earned Value Management
System (EVMS) in accordance with the guidelines for an EVMS contained in
ANSI/EIA-748-B. To establish the integrated performance management
system, the EVMS shall be linked to and supported by the Contractor's
management processes and systems to include the integrated master
schedule, contract work breakdown structure, change management, material
management, procurement, cost estimating, and accounting. The
correlation and integration of these systems and processes shall provide
for early indication of cost and schedule problems, and their relation
to technical achievement.

The Contractor shall provide a quarterly Contract Funds Status Report
(CFSR), in accordance with CDRL PM07, clearly delineating the contract
commitments and expenditures at the CLIN and appropriate CWBS level, as
well as forecast funding expenditures. The CFSR shall be included in the
Program Status Report. The Contractor shall provide a monthly Contract
Performance Report (CPR), in accordance with CDRL PM08, clearly stating
the contract cost baseline, actual and estimates.

CDRL PM07 Contract Funds Status Report

CDRL PM08 Contract Performance Report

####  Integrated Master Schedule 

The Contractor shall establish an IMS in accordance with CDRL PM 09.

CDRL PM09 Integrated Master Schedule

#### Program Reviews

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

-   Create and provide an agenda and overall strategy for conducting
    each meeting in accordance with CDRL PM10

-   Present material for meeting the objectives of the meeting

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

-   Provide minutes, action items and presentation materials in
    accordance with CDRL PM11

Designated management and formal reviews and audits shall not be
considered complete until Government approval.

Support provided by the Contractor shall include, but is not limited to,
facilities, materials, office equipment, clerical personnel, mockups,
technical data, and subcontractor participation (when requested by the
Government).

##### Post Award Conference 

The Contractor shall plan for, host, and support a post award conference
to be held at the Contractor\'s site within one month after contract
award. The Government will determine the actual date within 2 weeks
after contract award. At this conference, the Contractor shall address
the plans, cost, schedule and risks for the RWSL work efforts.

##### Program Management Reviews 

The Contractor shall convene PMRs to demonstrate the successful
completion, or progress toward completion, of project milestones. PMRs
shall be provided monthly during the period of performance of this
contract. The PMRs will normally be conducted at the Contractor\'s
facility; however other sites may be selected by mutual agreement
between the Government and Contractor. During the PMRs, the Contractor
shall present plans for accomplishing project milestones and activities,
an overview of system engineering, hardware and software development,
test, logistics and installation issues and analyses, and status as
reported in the PSR. The Contractor shall provide evidence that all
criteria that may be requested by the Government are satisfied to
receive approval.

The Contractor shall submit agendas and meeting minutes in accordance
with CDRL PM 10 and PM 11. Presentation materials shall be prepared and
included with the agenda.

CDRL PM10 Agenda

CDRL PM11 Meeting Minutes

##### Integrated Baseline Review

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

-   Ensure that the Government and Contractor mutually understand
    program scope, schedule, resources, inherent risk, and management
    approach

-   Ensure early and adequate planning

-   Identify risk items for incorporation into the risk management plan

-   Ensure appropriate reporting levels have been identified and
    variance thresholds agreed to by the Government and Contractor

The Contractor shall provide ongoing access during contract performance
to pertinent records and data, which underlie and support the cost and
schedule data reported. The Contractor shall provide an agenda,
presentation materials, and meeting minutes in accordance with CDRLs
PM10 and PM 11. The IBR shall be conducted as a separate review until
such time as the Government determines that it can be integrated into
PMRs.

#####  System Engineering Reviews and Technical Interchange Meetings 

The purpose of Technical Interchange Meetings (TIMs) is to ensure
continued Government visibility into the technical progress of the
contract. The Contractor shall plan and participate in bi-monthly TIMs
between the Government and the Contractor at the Contractor\'s facility
and sites selected by the Government. The TIMs will be conducted to
discuss the status of technical activities, including, but not limited
to: studies, test plans and results, design issues, and cost, schedule,
performance, implementation, logistics, and technical guidance.

The Contractor shall support the following planned technical interchange
meetings to manage the evolving RWSL design and program control
activities:

-   System Requirements Review (SRR)

-   Preliminary Design Review (PDR)

-   Critical Design Review (CDR)

-   Final Design Review (FDR)

The Contractor shall prepare and submit to the Government an agenda,
presentation materials, and minutes for all technical reviews in
accordance with CDRLs PM10 and PM 11. Presentations shall be based upon
the Contractor's system/subsystem engineering efforts and related
documentation. Minutes shall 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 shall be used to document the meeting and will be used by
the government in the approval process for the technical reviews and
audits

At each review, the Contractor shall be prepared to provide back-up data
on assumptions made and methodologies used in arriving at specific
recommendations/conclusions for the design approach. Key Contractor
personnel shall be available to respond to Government questions.

####  {#section .unnumbered}

The Contractor shall 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 shall notify the contracting officer of readiness for a
review at least 20 calendar days in advance of the planned start of each
review. If the previous technical review has not been approved by the
Government, or if documents required for a review have not been
delivered to the Government as scheduled, the Government shall have the
option of postponement without prejudice to other contractual
requirements. Formal reviews shall not be considered complete until
approval by the Government is granted in writing.

The following instructions apply to all technical reviews and audits:

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

2.  The location of the reviews may be changed by mutual agreement
    between the Government/Contractor.

3.  The Contractor shall record all action items identified.

4.  Response to all assigned action items by either closure or a plan
    for closure shall be made by the Contractor to the Government in the
    minutes of the meeting/reviews. The status of all action items shall
    be tracked at the PMRs and TIMs and provided in writing as part of
    the minutes until the action item has been resolved as mutually
    agreed by the Government/Contractor.

5.  Ten working days after receipt of the review/audit minutes, the
    Government will formally notify the Contractor of the results of the
    subject review/audit by:

-   Approval ‑ to indicate that the review/audit was completed
    satisfactorily.

-   Contingent Approval ‑ to indicate that the review/audit is not
    considered complete until completion of specific action items to the
    Government\'s satisfaction.

-   Disapproval ‑ to indicate that the review/audit was not
    satisfactory, and to identify those areas that were deficient. The
    Contractor shall have 15 working days to respond to the Government
    and provide a plan to complete the review/audit and maintain the
    program schedule.

##### System Requirements Review

The Contractor shall conduct a System Requirements Review (SRR). The
objective of this review is to ascertain the adequacy of the
Contractor's efforts in defining system design requirements and to
initiate the functional system requirements baseline.

During the SRR, the Contractor shall present results of functional flow
analysis, system interface studies, cost effectiveness analysis, and
program risk analysis. The Contractor shall present detailed requirement
definitions of the system under development. The Contractor shall prove
their full understanding of the operational concepts and problems that
the system is designed to solve. As part of the SRR, the Contractor
shall present and review the following documents with the Government:

1.  Deliverables, with overview of the following documents:

    a.  Software Development Plan (SDP)

    b.  Draft System/Subsystem Design Description (SSDD)

    c.  Draft Software Requirements Specification (SRS)

    d.  Draft Contractor's Master Test Plan (CMTP)

2.  Flows and system requirements definitions

3.  Critical Task Analysis

4.  Functional External System Interfaces

5.  System Safety Program safety considerations

6.  Security considerations and identification of security related
    requirements

7.  Human Engineering considerations

8.  Maintainability and Reliability requirements

9.  Plans for Key activities such as Testing or Site visits

10. Integrated Master Schedule

11. Identification of design-driving/cost-driving requirements

12. Program risk analysis, including assumptions, trade-offs and
    alternative approaches

13. Technical performance metrics and measures

14. Logistic Support overview

15. Manpower Requirements/Personnel analysis

####### 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.

2.  Initiation of the system and external interface functional
    requirements baseline fully traceable to the requirements in the
    RWSL System and FLS Specifications, SOW, and other related documents
    approved by the Government.

3.  Resolution of all action items.

####### Preliminary Design Review 

The Contractor shall conduct a Preliminary Design Review (PDR). This
review shall be conducted for an aggregation of configuration items.
This review shall evaluate software and hardware requirements
definitions. This review shall 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 Government
before a PDR may be conducted, and all SRR action items must be closed
prior to conducting the PDR, unless the Government has given permission
to proceed.

During the PDR, the Contractor shall present data flow and control flow
diagrams describing design solutions for each configuration item. During
the PDR, the Contractor shall 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 shall
provide a functional/physical description and define technical
requirements and interfaces with other system components. For these
non-developmental items, the Contractor shall 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 shall describe its plans for acquiring and
developing the required software to meet contract requirements. During
the PDR, the Contractor shall 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. At the PDR, the Contractor shall
describe the products, processes, methodologies, milestones, and
measurements to be used in conducting software development activities.
Overall technical program risks shall be reviewed on a technical, cost,
and schedule basis.

As part of the PDR, the Contractor shall present and review the
following documents with the Government:

1.  Deliverables, with overview of the following documents:

    a.  Draft Software Requirements Specification (SRS)

    b.  Draft Software Design Description (SDD)

    c.  Contractor Master Test Plan (CMTP)

    d.  Human Engineering Design Approach for Operators (HEDA-O)

    e.  Human Engineering Design Approach for Maintainers (HEDA-M)

    f.  Risk Assessment Report (RAR)

2.  System overview and software/hardware requirements definitions.

3.  Basic design approach for each configuration item, including CI to
    CI interfaces (HWCIs and CSCIs) and CI to external system
    interfaces.

4.  Functional flow, requirements allocation and schematic diagrams.

5.  CI development schedule.

6.  Preliminary processing algorithms description.

7.  Physical description including preliminary lists of materials,
    parts, manufacturing flow processes, and equipment layout.

8.  Power consumption goals.

9.  Preliminary power distribution and grounding design.

10. Producibility analysis.

11. Identification of design-driving/cost driving requirements.

12. Security considerations including how interfaces will be protected,
    how system access will be controlled, availability and integrity of
    data.

13. Vulnerability Assessment.

14. Results of contractor system safety assessments and status of
    support to FAA.

15. Reliability/maintainability/availability data such as analysis,
    including system, subsystem, and Line Replaceable Unit (LRU)
    component level reliability and maintainability predictions.

16. Installation requirements for Air Traffic Control Tower (ATCT),
    vault, airfield equipment and cabling.

17. Design concerns such as environmental control, electromagnetic
    compatibility/interoperability.

18. Program and technical risks.

19. Documentation status and availability.

####### PDR Acceptance Criteria

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

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.  Define 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, which requirements are already implemented but require
    modification, and which requirements require development.

8.  Present a preliminary design that shows how COTS, modified COTS, and
    new development will work together to satisfy the requirements
    baseline.

9.  Provide a draft SRS and SDD, and final CMTP, HEDA-O, HEDA-M and RAR
    that are acceptable to the Government.

10. Resolution, or an acceptable plan for resolution, of all action
    items.

##### Critical Design Review

The Contractor shall conduct a Critical Design Review (CDR). This review
shall be conducted for each configuration item when detailed design is
essentially complete. The PDR must be approved by the Government before
a CDR may be conducted, and all PDR action items must be closed prior to
conducting the CDR, unless the Government has given permission to
proceed. The CDR is intended to ensure that detailed design solutions,
as reflected in the draft CSCI design description, satisfy performance
requirements established by the baselined requirements documents. The
CDR is also performed for the purpose of establishing the integrity of
computer program design at the detailed level prior to coding and
testing. The objective of this review is to establish an allocated
baseline of low--level design requirements, which becomes an input to
the coding process.

The purpose of this review will be to:

1.  Ensure that technical, performance, safety, security and human
    interface requirements are correctly reflected in design.

2.  Ensure that architectural means in software design are correctly
    identified as derived requirements.

3.  Confirm that all derived requirements are defined and have undergone
    the system safety assessment process.

4.  Review all change requests generated by the software design process.

5.  Ensure that the computer software interfaces are documented and are
    congruent with high-level interfaces.

6.  Ensure that test plans and test procedures provide complete coverage
    of software requirements.

7.  Determine that the detailed design of the configuration item under
    review satisfies the performance and engineering specialty
    requirements of the HWCI development specifications

8.  Establish the detailed design compatibility among the configuration
    item and other items of equipment, facilities, computer software and
    personnel.

9.  Assess configuration item risk areas (on a technical, cost, and
    schedule basis).

10. Assess the results of the producibility analyses conducted on system
    hardware.

11. Review the hardware product specifications. For CSCIs, this review
    will focus on the determination of the acceptability of the detailed
    design, performance, and test characteristics of the design
    solution, and on the adequacy of the operation and support
    documents.

The CDR shall cover the detailed design of all Contractor-developed
hardware and computer software configuration items. For items that are
not Contractor-developed, the Contractor shall provide a detailed
functional/physical description of the item, any additional results
since the PDR of the analysis that verifies the item will meet the
associated technical requirements, and a detailed description of the
interfaces with other configuration items.

The Contractor shall provide further details than were presented at PDR
of its plans for acquiring and developing the required hardware and
software to meet contract requirements. Overall technical program risks
shall be reviewed on a technical, cost, and schedule basis.

As part of the CDR, the Contractor shall present and review in detail
the following documents with the Government in detail:

1.  Deliverables, with overview of the following documents:

    a.  Final SSDD

    b.  Final SRS

    c.  Final SDD

    d.  Draft Software Product Specification (SPS)

    e.  Software Version Description(s) (SVD)

    f.  RAR

    g.  Draft Software Transition Plan (STP)

2.  System and CIs overview

3.  System interface and schematic diagrams

4.  All CI to CI interfaces

5.  Processing algorithm descriptions

6.  Design analysis results

7.  Results of contractor system safety assessments and status of
    support to FAA

8.  Information Security considerations and status of support to FAA

9.  Human Engineering Design

10. Reliability and Maintainability Analysis and Predictions

11. Data recording formats

12. Operator controls and displays, and maintenance features overview
    including mockups and simulations

13. Design concerns such as environmental control, electromagnetic
    compatibility/interoperability

14. Program and technical risks

15. Identification of design-driving/cost driving requirements

16. Development and test schedule

17. Installation requirements for ATCT, vault, cabling and airfield
    equipment.

18. Producibility analysis

####### CDR Acceptance Criteria

To successfully complete CDR, the Contractor shall present objective
evidence of meeting the following requirements:

1.  Update a traceability of the design requirements to the CSCI/HWCI
    requirements

2.  Present a detailed design that shows how COTS, modified COTS, and
    new development will work together to satisfy the requirements
    baseline

3.  Present sufficient test data, analysis and detail to show that
    requirements of the SOW, RWSL System Specification FAA-E-3001, and
    RWSL FLS Specification FAA-E-3002 will be met.

4.  Provide a draft SPS and STP, and final SSDD, SRS, SPD and RAR that
    are acceptable to the Government.

5.  Resolution, or an acceptable plan for resolution, of all action
    items

##### Final Design Review 

The Contractor shall conduct a FDR. The FDR is intended to ensure that
the first article configuration is ready for operational testing. As
part of the FDR, the Contractor shall present and review in detail the
following items with the Government:

1.  Deliverables, with overview of the following documents:

    a.  Final SPS

    b.  SVD

    c.  Final STP

    d.  Software User Manual (SUM)

2.  Final software configuration and hardware configuration of the
    system for Operational Test.

3.  The proposed software builds to resolve any open issues .

4.  List of open SPRs and closure plans.

5.  List of outstanding waivers and any resolution on waivers.

6.  List of outstanding deviations and closure plans.

7.  Results of test and closure plans for handling test failures.

8.  List of any remaining technical problems not covered in items 3
    through 6.

9.  Results of the SAT testing and the Contractor Acceptance Inspection.

To successfully complete FDR, the Contractor shall present objective
evidence of meeting the requirements of items 1 through 8 and Government
approval of the documents in item 1 above.

#### System Safety Program 

The Contractor shall establish and implement a System Safety Program in
accordance with the FAA's Safety Risk Management Guidance for System
Acquisitions (SRMGSA). The Contractor shall develop a System Safety
Program Plan (SSPP) in support of the program and provide the Government
with the information, analysis and assessments to support the Government
development of System Safety documentation (i.e., Preliminary Hazard
Analysis (PHA), Sub-System Hazard Analysis (SSHA), (Safety Hazard
Analysis (SHA), Operating and Support Hazard Analysis (O&SHA), and
System Safety Assessment Report (SSAR)).

The Contractor shall identify a system safety point of contact to
provide the engineering services described in this section.

Guidelines for the SSPP are contained in DID SA-001 and Appendix B of
the FAA's Program Safety Plan Template. In addition to these guidelines,
the Contractor shall document their and their subcontractors' software
system safety and design assurance processes in the SSPP. RTCA DO-278
Guidelines for Communication, Navigation, Surveillance, and Air Traffic
Management (CNS/ATM) Systems Software Integrity Assurance may be used as
guidance in describing software design assurance processes in the SSPP.
Furthermore, the Contractor may reference Standard Operating Procedures
(SOPs), quality assurance processes, and/or any other standards for
software system safety and design assurance employed by the prime
Contractor and its subcontractors.

Safety tasks and activities shall be documented in the SSPP. The FAA's
SRMGSA and the Safety Management System (SMS) Manual may be used for
reference in preparing the SSPP. The Contractor system safety point of
contact shall complete FAA SMS training and act as a primary point of
contact for all communication on safety-related issues.

The Contractor shall participate in the RWSL Safety Risk Management
Panel (SRMP), as needed, to assist the FAA in developing safety hazard
analyses, identifying risk mitigation strategies, and tracking the
validation and verification status of system safety requirements.

The Contractor shall work collaboratively with the FAA to identify
system safety hazards, prepare risk assessments, and recommend
cost-effective risk mitigation strategies. The Contractor shall prepare
system functional analyses, fault tree analyses, reliability analyses,
and other engineering analyses as required to identify and analyze
system safety hazards.

The Contractor shall assist the FAA in preparing a SSHA. The SSHA is
accomplished once the system design is more mature and examines the
interfaces between the sub-elements of the system. The Contractor shall
work collaboratively with the FAA to verify subsystem compliance with
system safety requirements defined in the PHA, identify previously
unidentified hazards associated with each subsystem, assess the risk of
each subsystem design, and recommend cost-effective risk mitigation
strategies.

The Contractor shall assist the FAA in preparing a SHA. The purpose of
the SHA is to perform a detailed safety risk assessment of a system; in
particular the interfaces of that system with external systems and the
interfaces between sub-systems. The Contractor shall work
collaboratively with the FAA to verify system compliance with safety
requirements, identify previously unidentified hazards associated with
the system interfaces, system functional faults, and system operation in
the specified environment, assess the risk of the total system design,
and identify existing safety hazard controls.

The Contractor shall assist the FAA in preparing an O&SHA. The purpose
of the O&SHA is to perform a detailed safety risk assessment of a
system's operational and support (e.g., maintenance and certification)
procedures. The Contractor shall work collaboratively with the FAA to
(1) evaluate system operating and support procedures, (2) identify
hazards associated with those procedures, (3) assess the risk associated
with those hazards, (4) identify existing safety hazard controls, and
(5) develop alternative controls and/or procedures to eliminate or
control the hazards.

The Contractor shall assist the FAA in conducting safety reviews and
preparing a final SSAR. Safety reviews are periodically conducted in
part to (1) collect and document supporting evidence that safety
requirements are validated and verified and (2) recommend closure of
identified hazards based on verification of safety requirements. The
SSAR summarizes the results of the safety risk management program,
identifies all hazards and safety features in the program, and assesses
system readiness based on the cumulative safety risk to the NAS. The
final safety review and associated SSAR will trace hazards from the PHA
through the SHA to determine that hazards identified at various stages
of the program have been adequately addressed and resolved. The
Contractor shall provide system requirements, design, test, training,
and maintenance documentation needed to support each safety review. When
practical, safety reviews may be combined with TIMs, out-briefings
following formal test conduct, and functional and physical configuration
audits.

**CDRL SA01 System Safety Program Plan**

#### Configuration Management Program 

The Contractor shall use an internal Configuration Management (CM)
system for the control of all elements of the RWSL system, including
hardware, software and firmware, documentation, test equipment, space,
physical media, and physical parts. The detailed requirements are
included in these subparagraphs.

##### Contractor\'s Configuration Management Plan 

The Contractor shall develop and submit a Configuration Management Plan
(CMP). The CMP shall describe the Contractor's CM Program including
responsibilities, methodology and procedures for baseline
identification, configuration control and audit and status accounting of
software and hardware, documentation, support equipment, firmware, and
data bases. Configuration items shall be recommended using the
guidelines provided in MIL-HDBK-61A, section 5.3. Upon approval by the
Government of the CMP, the Contractor shall use this plan to establish,
implement and maintain a Configuration Management Program as specified
herein, using FAA Order 1800.66 and MIL-HDBK-61A as guidance. This
program shall be used for the control of all configuration items (e.g.,
software, physical media and parts, documentation, space, and power) and
to maintain the integrity and traceability of its configuration. The
Contractor shall specify a single authority to serve as a focal point
for all CM related issues.

A Configuration Control Board (CCB) shall be established to review and
approve any changes to the configuration of the system(s) and ensure
that documentation associated with an approved change to the RWSL is
updated to reflect the appropriate baseline. Affected documentation may
include training material, courseware, and other Integrated Logistics
Support documentation. The Government shall be provided access to the
process and be apprised of all proposed changes that affect the baseline
system and/or documentation. Proposed Changes that could affect the
interface to an existing NAS system (e.g., ASDE-X) shall be raised to
the Government's CCB.

CDRL CM01 Configuration Management Plan

##### Configuration Identification and Baseline 

The Contractor shall use and maintain a definitive basis for control and
status accounting for a Configuration Item (CI) throughout the RWSL
system life cycle. A CI is an aggregation of hardware and associated
software/firmware that satisfies an end-user function and is designated
by the Government for separate CM. The Contractor shall use an internal
developmental CM system. The documentation and repositories for this
developmental configuration shall remain the Contractor\'s
responsibility until the RWSL system is accepted by the Government. The
Contractor shall use and maintain configuration baselines and their
documentation. Incremental product baselines shall be permitted if
proposed and approved via an Engineering Change Proposal (ECP)
(3.1.9.2.4).

##### Part/Item Identification Numbers 

The Contractor shall assign a discrete part/item identification number
at the LRU level until such time as either an interim or final product
baseline is established. At that point, parts shall be re-identified
only upon Government approval whenever a non-interchangeable condition
is created. The Contractor shall assign a discrete part/item
identification number to each software medium (e.g., magnetic tape,
disk) containing RWSL system release- or build-type software
executables. The medium thus identified shall be inclusive and contain
all software segments, thereby providing easy identification of software
releases after the product baseline is established.

##### FAA Type Designations 

The Contractor shall request unique FAA equipment-type designations
based upon an engineering and logistical review of structural or
hardware items that could be identified by means of an FAA type number
as soon as practical, but no later than nine months after contract
award. FAA designations normally consist of two alpha characters in
combination with five numerals (e.g., FA-85000) which shall be affixed
to the unit on the nameplate in a location where it is readable, if
practical, in accordance with FAA-G-2100H. FAA type designations shall
not be assigned nor affixed to equipment that has been procured to
specifications of other Government agencies or previous FAA procurements
and that have already been assigned their own type designations or model
numbers, unless a \"major modification\" is applied to the equipment
based upon the RWSL system design. FAA type designations are applicable
to developmental and COTS items. The FAA type designation nameplate
shall not invalidate any warranty or equipment operation. Consideration
shall be given to adhesive attachment of the FAA type number nameplate
for COTS items.

##### Configuration Control 

The Contractor shall maintain change control of the engineering design
and production after Functional Configuration Audit/Physical
Configuration Audit (FCA/PCA) in accordance with the guidance contained
in MIL-HDBK-61A and the baseline requirements established at the PDR and
CDR.

#####  Engineering Change Proposal 

The Contractor shall submit ECPs, in accordance with the guidance in
MIL-HDBK-61A for approval prior to implementation and incorporation of a
change to baselined requirements or design. The Contractor shall submit,
attached to each ECP, a change description for each document that would
be changed if that ECP were approved. Each change description shall
include the exact proposed changes by citing the words/information to be
changed in "From/To" format, or other means to easily distinguish
proposed changes from approved documentation contents. (Proposed changes
affecting systems or interfaces with systems external to RWSL (e.g.,
ASDE-X) shall be submitted to the Government for review and approval, as
an NAS Change Proposals (NCP) in accordance with FAA Order 1800.66.)

The Contractor shall submit, with each ECP, as necessary, a Notice of
Revision (NOR) to drawings that are not controlled by the ECP
originator. The NOR shall be developed in accordance with the guidance
contained in MIL-HDBK-61A.

CDRL CM02 Engineering Change Proposal

####### System Enhancement ECPs

The Contractor shall provide the design, development, installation,
checkout, test and validation of specific system enhancements as
identified in requests by the Government. The CO may request that the
Contractor submit an ECP for Government identified system enhancements.
Once the ECP is approved, the Contractor shall be responsible for full,
development, implementation and documentation. Some potential system
enhancements are LED light fixtures in lieu of existing light fixtures,
Runway Intersection Lights (RILs) and Final Approach Runway Occupancy
Signal (FAROS) systems.

#####  Requests for Deviation 

The Contractor shall submit a request for deviation prior to departing
from the approved baseline for a specific number of units and a
specified period of time in accordance with the guidance contained in
MIL-HDBK-61A. Deviations shall be submitted only for temporary
departures from baseline, shall be for less than the production quantity
of the item, and shall not involve changes to any RWSL baseline
documentation.

CDRL CM03 Request for Deviation

#####  Requests for Waiver 

The Contractor shall submit waiver requests after the manufacture of a
hardware or software item that contains a departure from known
requirements and the Contractor proposes that the Government accept the
item \"as is\". Waivers shall be submitted only for specifically
identified items of less than the production quantity of that item, and
shall not involve changes to any RWSL baseline documentation.

CDRL CM04 Request for Waiver

#####  Parts Substitution 

The Contractor shall maintain parts substitution control.

#####  Configuration Status Accounting 

The Contractor shall generate Configuration Status Accounting Reports
(CSAR's) to ensure the configuration of development and implemented
systems and that delivered documentation accurately describes the
hardware configuration. The Contractor shall record and report the
following information:

1.  Current approved configuration documentation associated with each
    configuration item.

2.  Status of proposed engineering changes and requests for deviation or
    waiver from initiation to approval and status of implementation.

3.  Results of configuration audits including disposition of actions.

4.  Traceability of changes.

5.  Status of the implementation of changes at all locations.

6.  Identifiers of electronic documentation and software that have been
    delivered.

The Contractor shall use the CSAR's to provide traceability of any
change through the change control process. The Contractor shall present
status at PMR's as updates occur.

CDRL CM05 Configuration Status Accounting Report

#####  System Problem Reporting

The Contractor shall use a system problem reporting system as part of
the Contractor\'s CM program. The Contractor shall identify all system
level discrepancies or problems identified during development, testing,
production or installation and shall submit an SPR along with corrective
action plans. During each PMR, the Contractor shall report on any
outstanding discrepancies or problems, and the planned resolution. The
Government will have the right to witness or review the documentation
regarding the closure of any discrepancy item.

SPRs identified during testing shall be identified, along with
correction plans and status in the Test Reports submitted to the
Government.

**CDRL CM06 System Problem Report**

#####  Configuration Audits 

##### Configuration Audit Plan

The Contractor shall support configuration audits using ANSI/EIA-649-A
2004: National Consensus Standard for Configuration Management as
guidance. The Contractor shall be responsible for ensuring that
subcontractors, vendors, and suppliers participate, as required.

CDRL CM07 Configuration Audit Plan

#####  Configuration Audit Summary Report

The Contractor shall prepare for and support configuration audits to be
performed by the Government using MIL-HDBK-61A as guidance. The
Contractor shall be responsible for ensuring that subcontractors,
vendors, and suppliers participate in Government configuration audits.
The Contractor shall provide facilities, access to documentation and
equipment, security protocols, and shall ensure readiness for conduct of
the audits.

The Contractor shall support a Functional Configuration Audit (FCA) of
the RWSL system. Each individual requirement, irrespective of the test
guidance provided from any requirements or verification test matrix, may
be audited. The intent is to audit the attainment of all functional
requirements and to validate their attainment during the FCA.

FCA entrance criteria shall include:

1.  Successful completion of developmental testing including closure of
    SPRs and incorporation of any approved ECPs and required retest.

2.  Approval of all DT test reports.

FCA exit criteria shall include validation by the Government that all
requirements have been verified successfully.

The Contractor shall support a PCA of the RWSL system. The Contractor
shall provide support for subcontractor, vendor, and supplier PCAs for
CIs developed for the RWSL procurement or modified for use by other than
the RWSL prime Contractor.

PCA entrance criteria shall include:

1.  Fulfillment of FCA entrance criteria .

2.  Completion of requirements, design and product documentation
    including incorporation of all design changes and ECPs.

PCA exit criteria shall include:

1.  Verification by the Government that the documented product conforms
    with specified requirements.

2.  Verification by the Government that the documentation conforms to
    the physical RWSL system

3.  Successful completion of FCA .

4.  Government approval of as-built documentation to establish the RWSL
    Product Baseline.

**CDRL CM07 Functional and Physical Configuration Audit Summary Report**

#####  Data Management 

The Contractor shall establish a data management program to maintain all
contractually required and supporting documentation and correspondence
related to schedule, development, design, test, implementation,
management of equipment, and production documentation. Details of the
data management process shall be documented in the CMP. This shall also
include a process for monitoring, reporting, status accounting, and
cross-matrixing of changes, additions, or deletions of data item
deliverable contents. All data items shall be configuration-managed by
the Contractor. The Contractor shall control the generation, receipt,
approval, storage, and delivery of subcontractor data. The Contractor
shall also ensure that the subcontractor data meets requirements of the
contract and is integrated into contract deliverables.

The Contractor shall use an automated status accounting system for data
logging, recording, status reports, tracking, follow-up, record keeping,
and audit trails for contract data items. Status shall be documented in
the PSR.

####  Quality Management 

The Contractor shall provide and maintain a documented quality system as
a means of assuring compliance with the hardware and software
requirements of the contract. The contractor shall provide and maintain
a quality control program which fulfills the requirements of
ANSI/ISO/ASQ Q9001-2000 AMERICAN NATIONAL STANDARD, Quality management
system -- Requirements, and ISO/IEC 90003-2004, Software engineering --
Guidelines for the Application of ISO 9001-2000 to the development of
computer software. A Quality System Plan (QSP) shall be prepared and
submitted to the FAA for approval in accordance with CDRL QA01. The
Contractor shall ensure quality control and assurance of services and
supplies provided by all subcontractors and suppliers. All spare parts
shall be inspected and tested at the plant using the same procedures as
the primary equipment components.

Third party registration to ISO standards is not required nor does such
registration relieve the Offeror of the requirement of submitting a QSP.

**CDRL QA01 Quality System Plan**

### Systems Engineering and Design Development 

The Contractor shall execute a systems engineering program for the
definition, development, verification, integration, and testing of the
RWSL system requirements as allocated to RWSL processor and RWSL FLS
CSCIs and HWCIs as defined by the RWSL system specifications. System
engineering efforts shall consider all aspects of performance, quality,
life cycle cost, maintainability, reliability, schedule, data processing
reserves, and future growth requirements. Under this SOW, the Contractor
shall perform hardware prototyping as necessary to support system design
development, and shall designate and purchase, prior to CDR, long
lead-time hardware items necessary to implement the system design.

The Contractor shall provide a system design for all the requirements in
the RWSL System and RWSL FLS specifications and all applicable
interfaces. Where applicable, the Contractor shall follow
DOT/FAA/CT03/05 (HF-STD-001) Human Factors Design Standard for
Acquisition of Commercial-off-the-Shelf Subsystems, Non-Developmental
Items, and Developmental Systems. Specifically, Chapter 8 shall be used
as guidance for Contractor designed Graphical User Interfaces (GUI) and
user-computer interfaces.

The Contractor shall maintain effective control over the system
engineering and design development process, including subcontract items
and services, to ensure that cost, performance, and schedule are met, to
provide early detection and resolution of problems, and to reduce risk.
The Contractor shall specify a single authority who will serve as a
Point of Contact (POC) for systems engineering issues.

#### Systems Engineering Documentation 

The Contractor shall provide the engineering documents identified in the
following sections.

#### System/Subsystem Design Description 

The Contractor shall provide a SSDD for the entire RWSL System including
the RWSL processor, RWSL FLS, and all applicable interfaces in
accordance with DID-FAA-026-06.

CDRL SE01 System/Subsystem Design Description

#### Interface Control Documentation 

The Contractor shall define and prepare a RWSL Interface Control
Document (ICD) as a part of the systems engineering process and in
accordance with CDRL HW01. The Contractor shall design and develop the
physical and functional interfaces in accordance with FAA-STD-025F. The
ICD shall meet the requirements as specified in the ASDE-X to RWSL
Interface Requirements Document (IRD) and consistent with the Interface
Design Document for the ASDE-X Program. Interface controls shall be
established, coordinated, and maintained for interface requirements and
documents, and include applicable Contractor, subcontractor, and vendor
contract items, and GFP/GFE computer programs, facilities, and data. The
Contractor shall submit the ICD to the Government for approval. The
Contractor shall develop interface control documentation based on an
analysis and decomposition of the requirements contained in the RWSL
System Specification FAA-E-3001 and FAA-E-2942. The resultant ICD shall
define and illustrate performance, physical, and functional
characteristics in sufficient detail to ensure that all details on the
interface can be determined solely from the information in the ICD. The
Contractor shall use Interface Control Document RWSL processor to Field
Lighting System (FLS) Interface for the design of the interface between
the RWSL processor and the FLS. The Contractor shall participate in TIMs
with FAA and Contractor personnel who support or develop the systems to
which the RWSL System interfaces.

CDRL HW01 Interface Control Document

#### Human Engineering Design

##### Objective 

The objective of the HFE effort shall be to assure that the system
design is consistent with the capabilities and limitations of air
traffic control personnel (i.e., front-line manager or
controller-in-charge) and maintainer in the operational environment.
Further, the HFE effort is intended to ensure the usability of the
system from the user's perspective and should also ensure that the
implementation of RWSL does not negatively impact situational awareness
or workload for air traffic control personnel or maintainer.

##### Planning and Execution 

An adequately staffed Human Factors Engineering (HFE) effort shall be
dedicated to and be an integral part of the analysis, design, and test
process of the RWSL processor cab control panel, and maintenance
interface. An HFE program shall be planned and implemented in accordance
with MIL-HDBK-46855A, as applicable to the system\'s COTS or NDI program
objectives, and human-in-the-loop performance requirements,
characteristics and constraints. The Contractor shall develop an HFE
program plan and document it as part of CDRL PM01, RWSL Program
Management Plan. The plan should detail how Human Factors (HF)
analyses/studies, prototyping tradeoffs, user participation, and
demonstrations will provide design solutions in a timely manner and
support the achievement of the major RWSL milestones. This document
shall also describe the conduct of the HFE development, risk reduction
activities, and Government and Contractor HFE participation in major
design reviews. The HFE Program Plan should delineate a schedule of
activities for the execution of the tasks contained in the Plan and the
costs associated with the execution of the Plan. HFE should be an
integral part of the RWSL program and contribute towards fielding a
usable system

##### HFE Program Emphasis Areas 

Within the context of the above considerations, the HFE program shall
include, as a minimum, the following emphasis areas:

-   Cab Control Panel: Effectiveness of user controls, legibility, and
    identification of system status.

-   Cab Kill Switch: Effectiveness of user control, protection from
    accidental tripping.

-   Maintenance Interface: Suitability of maintenance hardware/software
    procedures to facilitate meeting system human-in-the-loop
    performance requirements including accomplishing the following:

    -   Maintenance tasks related to fault isolation, system
        optimization, manipulation, access, removal, replacement, and
        repair.

    -   Manual operations involving pulling, pushing, lifting, or
        carrying.

    -   Compatibility of tools with tasks, hand-wear, and environment..

-   Test and Evaluation: HFE requirements shall be integrated into
    system test and evaluation to demonstrate the capability of the cab
    control panel, interface with RWSL (e.g., RELs and THLs), and
    maintenance interface to required system performance characteristics
    (i.e., system requirements for maintenance and controller
    interfaces, in accordance with DOT/FAA/CT03/05 (HF-STD-001), Human
    Factors Design Standard for Acquisition of Commercial-off-the-Shelf
    Subsystems, Non-Developmental Items, and Developmental Systems). HFE
    tests may be integrated into other system tests. However, dedicated
    HFE tests shall be performed when validation of critical task
    accomplishments is necessary.

No more than two (2) user working groups shall be convened at the vendor
facility to address HF design specifications as applicable.

HFE reviews shall be conducted as a part of all design reviews. Each HFE
review shall cover at least the following:

-   HFE Program Accomplishments.

-   Principal Human Performance Requirements: System operation and
    maintenance requirements which depend on human performance shall be
    summarized.

-   Human Engineering Design: Compliance of controller and maintenance
    interfaces with engineering design requirements shall be presented.

The Contractor shall provide a Human Engineering Design Approach
Document for the Operator and for the Maintainer in accordance with
CDRLs HE01 and HE02.

CDRL HE01 Human Engineering Design Approach Document -- Operator

CDRL HE02 Human Engineering Design Approach Document -- Maintainer

#### Engineering Services

The Government may choose to exercise an option for engineering services
at any time during the life of the contract.  The Engineering Services
may include engineering analysis, requirements development and analysis,
engineering design and tradeoff analysis, design and engineering of
changes, including cost-benefit and risk analysis, safety, human factors
and security analysis, or other engineering services.

### Software Development 

The Contractor shall design, code, integrate, test, and deliver the RWSL
processor and FLS software required to meet the requirements of the RWSL
System Specification FAA-E-3001 and the FLS Specification FAA-E-3002.
The Contractor shall document software developed under this contract as
required in the following sub-paragraphs. **The Government Furnished
Information (GFI) software is provided as an example of an
implementation that has proven effective in prototype trials in an
operational setting. However, use of this software is not a requirement
of this SOW and [does not]{.underline} relieve the Contractor of
responsibility for meeting the requirements in this SOW or the RWSL
specifications.** The Contractor may choose to use the same methods in
the GFI software or may choose his own.

#### System Software Design 

Where RWSL requirements cannot be met by using commercially offered
software packages, the Contractor shall develop the required computer
software. The following guidelines shall apply:

-   Firmware (software that resides on programmable memory) shall be
    treated as software.

-   Commercially available operating systems used in the RWSL shall be
    Portable Operating System Interface (POSIX) compliant and be the
    most recent release or update.

-   RWSL software shall be in accordance with the operating system, COTS
    application manufacturer recommendations, and applicable industry
    standards.

-   Updates and revisions will be implemented by the Contractor as they
    occur until the test readiness review. If the Contractor chooses to
    modify commercial software, he shall supply the justification for
    the change to the Government. The justification shall state the
    method of documentation. All changes shall require Government
    approval.

For standard commercial product software employed to satisfy RWSL system
requirements, corresponding commercial documentation, licensing
agreements, and usage limitations shall be submitted to the Government
for approval. The Contractor shall ensure that the Government has
unrestricted access to additional copies of commercial software
documentation.

The Government shall have ownership and modification rights to all
source code of all software and firmware developed to satisfy the
requirements of this SOW and RWSL system specifications.

##### Software Documentation 

The Contractor shall provide the software documentation for requirements
allocation, design, test, quality assurance, delivery, installation,
operation, maintenance, and support of each computer resource CI and
CSCI. The Contractor shall submit software documentation to the
Government for review and approval.

The following sections describe the required software documentation to
be provided by the Contractor.

##### Software Development Plan 

The SDP is a tool for documenting the management processes for software
development, the methods to be used, the approach to be followed for
each activity, and project schedules, organization, and resources. The
SDP describes how to conduct the RWSL processor and FLS software
development effort.

The Contractor shall prepare, use, maintain, and update the SDP
throughout the performance of the contract. The SDP shall be developed
in accordance with DID-SW001 and is subject to Government approval.

The SDP shall not relieve the Contractor from complying with all other
requirements of the RWSL specifications and this SOW. The Contractor
shall ensure that software products developed by subcontractors are in
accordance with all prime contract requirements. The Contractor shall
specify the means by which this is to be accomplished in the SDP.

**CDRL SW01 Software Development Plan**

##### Software Requirements Specification 

The purpose of the SRS is to provide a complete allocation matrix of all
software requirements (explicit and derived) from the RWSL System
Specification FAA-E-3001, RWSL FLS Specification FAA-E-3002, and SSDD.

The SRS shall be prepared in accordance with DID SW-002 and is subject
to Government approval.

Following delivery to the Government, the SRS shall be subject to
configuration control.

**CDRL SW02 Software Requirements Specification**

##### Software Design Description 

The SDD shall be prepared in accordance with DID SW-003 and is subject
to Government approval. Upon completion of the PCA, the SDD, as part of
the SPS, shall be entered into the product baseline for the CSCI.
Subsequent to approval, the SDD shall be subject to formal configuration
control and shall not be changed without prior Government approval.

CDRL SW03 Software Design Description

##### Software Version Description 

The Contractor shall provide a SVD for each CSCI. The SVD shall be used
by the Contractor to release CSCI versions to the Government. The SVD
shall accompany the shipment of each CSCI to the Government. The
Contractor shall use and maintain a system that ensures that each CSCI
change is accounted for, following approval by the Government. The SVD
shall be updated as required to describe all changes to any CSCI version
delivered subsequent to the initial CSCI delivery. The SVD shall be
prepared in accordance with DID SW-004 and is subject to Government
approval.

CDRL SW04 Software Version Description

##### Software User Manual 

The Contractor shall provide one SUM for the RWSL program. The Software
User Manual shall provide user personnel with instructions sufficient to
utilize the RWSL system for its intended purpose. Functions described
shall include, but are not limited to, operations, log-in, and operator
switch settings/changes. The SUM shall be prepared in accordance with
DID SW-005 and is subject to Government approval.

CDRL SW05 Software User Manual

##### Software Product Specifications 

The Contractor shall prepare and provide a SPS for each CSCI. The SPS
shall address all COTS/Non-Developmental Item (NDI) products used in the
CSCI. The SPS shall include the design documents, software listings, and
source code for software and firmware. Upon Government approval, the SPS
shall establish the product baseline for the delivered CSCI. The SPS
shall be prepared in accordance with DID SW-006 and is subject to
Government approval.

CDRL SW06 Software Product Specification

##### Interface Design Document 

The Contractor shall provide a detailed design of the Hardware
Configuration Item to CSCI interfaces and the CSCI to CSCI interfaces.
The Interface Design Document shall be used to specify the design for
those interfaces. Following delivery to the Government, the Interface
Design Document shall be subject to configuration control. The IDDs
shall be prepared in accordance with DID HW-002 and are subject to
Government approval.

CDRL HW02 Interface Design Description

##### Development of Non-Operational Software 

The Contractor shall provide any non-operational software such as
simulation software, test software and development/maintenance tools
with documentation. This includes software used to test operational
system software via system level simulations and developmental software
used to create operational software and tools for maintaining
operational software. The development of non-operational software
excludes licensed commercially available software. In these cases, the
Contractor will need to supply a description of the software,
manufacturer, and version. Non-operational software that is required for
development, installation, test, support, maintenance or optimization of
the RWSL system shall be subject to validation.

Any programs developed on this software shall also be deliverables.

##### Hardware Identification and Selection 

The Contractor shall provide a detailed design of the RWSL hardware with
requirements traceability to the RWSL system and FLS specifications.
This design and development shall be in accordance with, and meet the
requirements of each. The Contractor shall make maximum use of readily
available COTS hardware systems which satisfy the functional and
performance requirements of the specification. Hardware subsystems,
assemblies, or components which meet the requirements of the
specification shall be procured according to applicable FAA regulations
and orders. COTS hardware shall remain consistent across all sites (same
manufacturer, type, and hardware family) and shall remain consistent
upon completion of any hardware upgrade of RWSL equipment/design. During
the engineering design process, the Contractor may propose, for
Government review and approval, a new configuration item, developmental
Line Replaceable Unit (LRU), or modified COTS/NDI if it is justified as
best value on a cost/benefit basis. The Contractor shall document the
interrelationships between the system/subsystem/equipment drawings in an
Engineering Drawing Tree, CDRL TD01, as defined in Section 3.6.6.1,
Technical Drawings and Associated Lists. The documentation of the
selected COTS equipment design shall be as defined in Section 3.6.6.4,
COTS Manuals and Documentation and MIL-HDBK-454B, Requirement 7. The
interchangeability shall be applied at the unit level.

##### Interchangeability

All like components of each system shall be interchangeable between
systems, and identical units within each system shall be
interchangeable. Identical components shall be identified with identical
part numbers and unlike parts shall not have the same part number. This
requirement does not prevent the readjustment or calibration of
exchanged modules nor does it prohibit exchange of control panels due to
the runway identification number.

##### Access to System Development Environment 

The Contractor shall provide the FAA full and timely access to the RWSL
system development environment. This shall include, but not be limited
to, access to data, documentation, draft CDRLs, source code, and the
physical plant. FAA access shall include access for FAA employees and
FAA contractor support personnel. FAA access shall also include FAA
Training Academy personnel in support of their development of Technical
Operations Technical Operations training. To facilitate such access, the
Contractor shall:

-   Provide the FAA with weekly physical access of not less than
    forty (40) hours.

-   Provide access to contract deliverables prior to delivery.

-   Provide the FAA with electronic access to data, documentation, and
    RWSL processor and FLS development environment elements, other than
    physical plant facilities.

-   Propose an alternative method of providing access, where remote
    electronic access is not feasible, subject to acceptance and
    approval by the Government.

-   Provide timely notification to the Government of any adverse impact
    to the development effort arising from the cooperation and access
    afforded to the FAA as specified herein.

-   Provide password protected Internet access to documents selected by
    the Government.

##### Reliability Program 

The Contractor shall establish a reliability program in accordance with
FAA RMA Handbook 06A and MIL-HDBK-781A to ensure that the reliability
requirements of the RWSL system and this SOW are satisfied. The
Contractor\'s overall methodology for conducting a reliability program
shall be documented in a Reliability Program/Demonstration Plan in
accordance with FAA-HDBK-06A and MIL-HDBK-781A.  The Contractor shall
propose a Reliability Growth Program consistent with FAA-HDBK-06A. For
the limited production systems, the Contractor shall be responsible for
the following:

-   Performing reliability predictions in accordance with MIL-HDBK-781A
    and document these in the Reliability Program/Demonstration Plan.
    Changes in predicted numbers resulting from development and test
    activities shall be calculated and shall be presented at PMRs and
    TIMs.

-   Tracking failed hardware (including receiving failed equipment from
    the fielded sites and returning them to the equipment manufacturers
    for repair/replacement) and software. Part of this effort shall
    include using the associated failure data as part of the
    Contractor\'s reliability program and for calculating reliability
    growth.

-   Documenting all failures (hardware and software) in PTRs and
    presenting these to the Government's Reliability Review Board for
    decision based upon the FAA-HDBK-06A.

-   Analyzing failures, presenting failure data and discussing
    engineering remedies/actions at TIMs and PMRs.

-   Aggressively correcting all PTRs to prevent recurrence and to meet
    Reliability requirements of this Contract.

-   Documenting the overall methodology for conducting a reliability
    program, including the process(es) for tracking failed hardware,
    using the failure data for reliability purposes in a Reliability
    Program/Demonstration Plan and conducting a successful Reliability
    Growth Program.

CDRL RP01 Reliability Program/Demonstration Plan

##### Maintainability Program 

The Contractor shall establish and demonstrate a maintainability program
to ensure that the maintainability requirements of the RWSL system
specifications and this SOW are satisfied. The Contractor\'s overall
methodology for conducting a maintainability program shall be documented
in a Maintainability Program/Demonstration Plan in accordance with
MIL-HDBK-470A. The Contractor shall develop maintainability predictions
in accordance with the guidance contained in MIL-HDBK-470A, Appendix D,
Method B, and submit them in the Maintainability Program/Demonstration
Plan. Changes in predicted numbers resulting from development and test
activities shall be calculated and shall be presented at PMRs and TIMs.

CDRL MP01 Maintainability Program/Demonstration Plan

##### Electromagnetic Interference and Susceptibility 

The Contractor shall design and construct the system to meet the
interference and susceptibility requirements of the RWSL specifications.
If a deficiency exists between the system and the requirements, the
Contractor shall correct these deficiencies. The RWSL FLS shall not
cause interference to, or be susceptible to, interference from other
airfield lighting systems.

#####  Security Program

The Contractor shall establish and implement a security program in
accordance with FAA Order 1370.82A, FAA Order 1600.72A, FAA Order
1600.75, and the RWSL System Specification FAA-E-3001. The Contractor
shall prepare an RWSL Security Plan, CDRL SE02, documenting the
applicable security features and their proposed implementation for the
RWSL. The Security Plan shall describe the information necessary to
support the FAA Security Certification and Authorization Package (SCAP)
process. The Security Plan shall detail the security risk assessment of
all NDI software and commercial item hardware to establish the
vulnerabilities of the system. Upon approval of the plan by the FAA, the
Contractor shall conduct the contract effort in accordance with the
provisions in the approved plan, including support to the Government in
development of the SCAP.

**CDRL SE02 Security Plan**

#####  Personnel Security

The Contractor shall comply with the requirements of FAA Order 1600.1E
in all personnel security matters. The Contractor shall submit the
security forms for all personnel so identified to the Government for
processing in accordance with FAA Order 1600.1E.

#####  Information Security

The Contractor shall comply with the requirements of FAA Order 1600.75
in the handling of all sensitive unclassified information (SUI) received
from the Government or developed by the Contractor.

##### Physical Security

The Contractor shall comply with the requirements of FAA Order 1600.6E
and FAA Order 1600.69B in all physical security matters.

### System Test and Evaluation

The Contractor shall develop and submit a Contractor's Master Test Plan
(CMTP) to the Government for approval. The CMTP shall provide the plan
for the conduct and documentation of an integrated test and evaluation
program in accordance with the SOW and for the testing of all
requirements in the RWSL System Specification FAA-E-3001, RWSL FLS
Specification FAA-E-3002, and this SOW. The Contractor shall designate a
Contractor Test Director to oversee the planning, conduct, and
documentation of an integrated test and evaluation program in accordance
with this SOW and the Government approved CMTP using the Acquisition
Management System Test & Evaluation Process Guidelines and the attached
Data Item Descriptions as guidance. The CMTP shall serve as the overall
test philosophy, definition, and control document for the Contractor's
RWSL Test and Evaluation Program. The test program shall verify that the
entire RWSL system and its support elements meet the physical,
functional, interface, and performance requirements as stated in the
RWSL System Specification and the RWSL FLS Specification.

The Contractor shall develop test schedules, test plans (TE02), and test
procedures (TE03) as required by the CDRLs of this SOW. The Contractor
shall conduct tests and generate test reports (TE04) as required by this
SOW. The Contractor shall get approval by the Government for each level
of Contractor test documentation prior to the submittal of the next
lower test documentation or test conduct. The CMTP shall be approved by
the Government prior to lower level Test Plan submittals. Each Test Plan
shall be approved by the Government prior to the submittal of associated
Draft Test Procedures. Draft Test Procedures shall be approved by the
Government prior to the conduct of the associated Development Test and
Evaluation (DT&E) Preliminary Qualification Test (PQT). The completion
of the PQT and the final Test Procedures shall be approved by the
Government prior to the conduct of the associated DT&E Formal
Qualification Test (FQT). The completion of the FQT must be approved by
the Government prior to the submittal of the associated Test Report. The
Contractor shall submit separate test documents (test plans, procedures
and reports) for the Factory Development Qualification Tests (FDQT),
Site Development Qualification Tests (SDQT), 1^st^ Article Tests,
Factory Acceptance Tests (FAT), and Site Acceptance Tests (SAT).

**CDRL TE01 Contractor Master Test Plan**

**CDRL TE02 Test Plan**

**CDRL TE03 Test Procedure**

**CDRL TE04 Test Report**

#### Development Test and Evaluation 

The Contractor shall perform DT&E. The purpose of DT&E shall be
primarily to assist in the engineering design, development, and
implementation process by determining incrementally the degree to which
functional engineering specifications are attained. DT&E shall consist
of FDQT, 1^st^ Article Tests, and SDQT.

##### Test and Evaluation Management

The Contractor shall furnish equipment, space, and personnel required to
perform Contractor-conducted factory tests. The Contractor shall
coordinate testing to be performed and ensure that there is minimal
redundancy of effort or data. The Contractor shall assign a Test Manager
to oversee the Contractor's responsibility for integration, control,
oversight, and coordination of all Contractor and Subcontractor testing,
and support for Government site tests.

Contractor-proposed test tools, documentation, and test-support hardware
and software shall be approved by the Government prior to the start of
testing. The Contractor shall conduct Test Issue Resolution Process
meetings in accordance with CDRLs PM 10 and PM11 with the Government as
part of the approval process to review comments and to finalize all test
plan and procedure approaches, to meet the CDRL requirements of this SOW
and the specifications. The Contractor shall integrate test schedules
into the overall RWSL program schedule. The Contractor shall notify the
Government of testing schedules at least five (5) working days prior to
the start of each test. The Government reserves the right to witness, on
a non-interfering basis, Contractor testing during any test phase or
level.

The Government may require, and the Contractor shall cooperate with and
perform, in-process quality inspections at any time in a manner not
disruptive to Contractor fabrication and assembly operations.

##### Configuration Management Inspections

In addition to its own in-house configuration management, the Contractor
shall cooperatively allow and perform random configuration management
inspections at the determination of the Government. These inspections
shall not require the preparation of formal plans or procedures. The
Contractor shall be prepared to show internal configuration management
documentation at these inspections. Any results of non-compliance or
unexplainable anomalies shall be entered into the Contractor's problem
reporting system as a SPR, and shall be formally tracked until
resolution.

##### Test Support

The Contractor shall provide all required support throughout the entire
test period as defined in the CMTP and approved by the Government,
including any Government testing. This shall include support continuing
through RWSL baseline and field acceptance for all Contractor equipment.

##### Test Equipment

The Contractor shall be responsible for assuring that all test equipment
required for the successful completion of testing is available, on time,
properly calibrated, and fully operational to support tests. Use of
Government test equipment may be permitted where Government test
equipment is (1) on site, (2) available, and (3) meets specified test
equipment requirements. Test equipment used by the Contractor during
Factory or Site Tests that is COTS shall not be modified without prior
written approval of the FAA. Test equipment shall operate in the manner
specified by the test equipment manufacturer. Ancillary equipment
required by the Contractor for test purposes shall be furnished by the
Contractor for the duration of the tests and approved by the Government.
The Government Test Director may require the Contractor to re-calibrate
any test equipment provided by the Contractor to be used in the test
program due to either of the following:

-   The test equipment is removed from the test set-up for unrelated
    purposes.

-   The test equipment fails, is damaged, or appears to be operating in
    a faulty manner based on Government evaluation of test results.

##### Verification Requirements Traceability Matrix 

The CMTP shall contain a Verification Requirements Traceability Matrix
(VRTM) as an attachment for Government approval. Each requirement from
RWSL System Specification FAA-E-3001, FLS Specification FAA-E-3002, and
this SOW shall be specifically addressed in the VRTM and correlated to a
verification method from the methods listed below:

> **R (Design Review)** - Requirements verification by design review
> shall determine requirements compliance by review and approval of a
> specific design data through the presentation of a Design Review Data
> Package (TE05) at formal reviews.
>
> **I (Inspection)** - Requirements Verification by inspection shall
> determine requirements compliance through visual observation,
> mechanical measurements of equipment, or examination of or comparison
> to engineering documents and standards in accordance with approved
> inspection procedures, data collection, and pre-defined success
> criteria.
>
> **A (Analysis)** - Requirements verification by analysis shall
> determine requirements compliance by comparing the applicable aspects
> of the subsystem design with known, established, and certified (or
> certifiable) technical data, scientific/technical principles,
> procedures and/or practices which validate the requirement in
> accordance with approved analysis procedures and pre-defined success
> criteria through the submittal of an Analysis Report (TE06).
>
> **D (Demonstration)** - Requirements verification by demonstration
> shall determine requirements compliance by the observation of the
> qualitative determination of properties of an end-item or unit and
> requiring procedures and pre-defined success criteria. Software
> demonstration is an activity that is limited to a readily observable
> functional operation to determine compliance with requirements (e.g.,
> the proper response at a site as a result of a specified interrogation
> or command to be processed by the program).
>
> **T (Test)** - Requirements verification by test shall determine
> requirements compliance by the measurement of the subsystem
> performance under specific configuration and load conditions with
> controlled application of known input stimuli. This results in the
> measurement of quantitative data which may be subject to reduction and
> analysis to validate the results against pre-defined success criteria,
> and which requires the employment of procedures and data collection.
>
> **TD (Test with Data)** - Requirements verification by test with data
> shall determine requirements compliance by means of an attachment to
> the CMTP that supplies data as obtained from prior testing. At a
> minimum, the data shall consist of the "as run" test procedure, a test
> report, and documentation of the "as run" test configuration. Data
> obtained from prior testing must conform to the following conditions:

1.  The data was obtained from an equivalent system that matches the
    baseline for the RWSL test program (this is determined by the
    Government examination of system configuration data for the baseline
    system and the system from which the data was obtained).

2.  The data was verified by an independent agent or Government (the
    Government will determine if the agent was independent based on
    verification of substantiation provided by the Contractor).

3.  The data is sufficient to fully satisfy the requirements of the
    contract (the Government will determine if the data is sufficient).

4.  Those RWSL requirements, which are to be verified by prior test
    data, shall be clearly indicated in the CMTP and the VRTM. Any use
    of the Test with Data verification method is subject to Government
    approval.

Each requirement from the RWSL System Specification FAA-E-3001, the RWSL
FLS specification FAA-E-3002, and this SOW shall be specifically
addressed in the VRTM and correlated to at least one system
configuration on which the requirement is to be verified from the
configurations listed below. The configuration must fully test the
requirement:

1.  Full RWSL System

```{=html}
<!-- -->
```
a.  FS (Full System) -- Full RWSL Processor Subsystem, Full Field
    Lighting Subsystem

```{=html}
<!-- -->
```
2.  Partial RWSL System

```{=html}
<!-- -->
```
a.  FR - Full RWSL Processor Subsystem

b.  PR - Partial RWSL Processor Subsystem

c.  FF - Full Field Lighting Subsystem

d.  PF - Partial Field Lighting Subsystem

Each requirement from the RWSL System Specification FAA-E-3001, the FLS
Specification FAA-E-3002, and this SOW shall also be specifically
addressed in the VRTM and correlated to at least one verification method
with which it will be verified. For each requirement, the Contractor
shall also indicate in which test plans the requirement will be
satisfied. Individual test plans, procedures, and reports shall clearly
indicate where their particular VRTM requirements are being addressed,
executed, and met in the proposed test sections therein. Separate test
plans and test procedures may be submitted for individual tests to allow
those tests to progress prior to the submittal and approval of the test
plans and test procedures for other tests.

The Contractor shall submit the final CMTP to the Government for review
and approval. As part of this final CMTP, and in accordance with CMTP
requirements, the Contractor shall perform a final mapping of the VRTM.
Post-"final mapping" changes after Government approval of the CMTP shall
be submitted in change pages for approval by the Government.

**CDRL TE05 Design Review Data Package**

**CDRL TE06 Analysis Report**

##### Test Conduct

Test conduct shall be conducted by Contractor test personnel assigned by
the Contractor's Test Director and witnessed by personnel assigned by
the Government Test Director.

####### Preliminary Qualification Test 

The Contractor shall conduct a Preliminary Qualification Test (PQT) or
"dry run" for each test event. The Contractor shall provide the
Government five (5) days advance notice of all PQT activities as defined
in the CMTP. The Government reserves the right to witness the PQTs.
Draft test procedures approved by the Government shall be used for the
PQT. The draft test procedures may be red-lined during the PQT to
necessitate test completion and accuracy. For inspections,
demonstrations, and tests, a PQT is complete when the associated test
procedures have been run in their entirety in a repeatable manner
(legible redlines) and all failures encountered have been documented
with SPRs. For analysis, the PQT is complete when a walkthrough of the
draft analysis report verifies that the forthcoming analysis will be
sufficient to verify the requirement's success criteria. The results of
a fully successful (no failures encountered, minimal red-lines required)
Government-witnessed PQT may, with the approval of the Government, be
used in place of a formal FQT.

Following the completion of each test, the Contractor shall present and
discuss SPRs, test log entries, and test results with the Government
representatives at a test debriefing, but no formal decision shall be
made by the Government at the debriefing relative to the formal
satisfaction of test requirements. The Contractor shall publish test
debriefing minutes (CDRL PM11).

####### Formal Qualification Test 

The Contractor shall conduct a Formal Qualification Test (FQT) for each
test event. All requirements (in accordance with the approved CMTP VRTM)
shall be verified during each formal test event. All formal test events
require five (5) days advance notice to the Government by Notification
of Test Letter (CDRL TE07) that a formal test event is scheduled. Final
Test Procedures approved by the Government shall be used for the FQT.
The final test procedures may only be minimally red-lined during the FQT
to necessitate test completion and accuracy.

Prior to a formal test event, the article under test shall be described
and the complete configuration of the article shall be provided to the
Government for inspection and concurrence, such that the configuration
is adequately documented. Test data and test logs (CDRL TE08) shall be
collected and authenticated as part of the RWSL Test Program.

All formal testing shall be conducted on test articles, which exactly
conform to the configurations documented in the associated test plans
and procedures. These tests shall employ only the baselined software
image as resident and operational. In the case of multiple First
Articles, the hardware and software configurations under test shall be
identical with the exception of application-specific configuration
differences (e.g., number of lights).

All test tools shall be certified by demonstration and/or inspection
prior to test, and the results validated by the Government prior to use
in any formal test event.

Each FQT shall be conducted on a pass/fail basis. The pass/fail success
criteria for each requirement shall provide a clear and unambiguous
objective for the determination of requirement verification. If the
requirement has been modified by deviation, the success criteria shall
be updated appropriately. A requirement verified by test, inspection, or
demonstration shall be considered passed when the test has been executed
without aborts or errors (unless they are part of the test procedure)
and when expected results and all analysis performed verify correct
operation in accordance with the specified success criteria. A
requirement verified by analysis shall be considered passed when an
analysis which verifies the requirement's success criteria and has been
completed and approved by the Government. A requirement for which a
waiver has been submitted shall be considered completed with no pass or
fail status.

Each FQT shall be capable of being repeated to achieve the same results.
Discrepancies between actual and expected test results shall be
explained by analysis of test data. Each FQT shall not be considered
successfully completed until:

1.  The Contractor has received written Government approval of the final
    test procedures.

2.  The Government representative has witnessed the actual test.

3.  The test has been conducted to the Government's satisfaction in
    accordance with the Government approved plans and procedures.

4.  The test report (CDRL TE04), including all data analysis, test
    results, and corrective actions, has been approved by the
    Government.

5.  All associated waivers and deviations have been approved by the
    Government.

Following the completion of each test, the Contractor shall present and
discuss SPRs, test log entries, and test results with the Government
representatives at a test debriefing, but no formal decision shall be
made by the Government at the debriefing relative to the formal
satisfaction of test requirements. The Contractor shall publish test
debriefing minutes (CDRL PM11).

**CDRL TE07 Notification of Test Letter**

**CDRL TE08 Test Log**

##### Factory Development Qualification Tests 

The Contractor shall perform Factory Development Qualification Tests
(FDQT) to verify that the implemented design meets functional and
performance requirements of the RWSL system and FLS specifications and
this SOW.

##### REL/THL Algorithm Test

The Government will provide recorded ASDE-X surveillance log data and
corresponding airborne departure timing data to be used to test
requirements from section 3.3.1 of the RWSL System Specification.

##### Parameter Test

The Contractor shall test all parameters developed from section 3.1.2
and 3.1.3 of the RWSL System Specification to verify all parameters
perform as designed. The Contractor shall test in as an efficient manner
as possible, using a minimum of three parameters per variable, including
an out of range parameter if pertinent.

##### Capacity and Throughput Test

System capacity and throughput tests shall be conducted using Government
provided scenarios (i.e., ASDE-X log data) to test the system's
throughput while the system is operating under capacity load conditions.

##### Human Factors Test

Human factors requirements that apply to the cab control panel shall be
verified by design review. Human factors requirements that apply to the
maintenance interface shall be verified during the maintainability
demonstration. Further human factors test and evaluation will be
conducted by the government during the Government operational test.

##### First Article Tests

##### Inspection Test

The First Article Inspections shall be conducted on the First Article
unit, module, or assembly. The mechanical inspection shall include a
visual examination to determine compliance with the applicable
specification requirements defined in FAA-G-2100H for strength and
rigidity, accessibility, types of components and materials, choice of
insulation, layout of chassis, panels and wiring, finishes, workmanship,
and similar attributes. The inspections as defined in the CMTP VRTM
shall be conducted, in accordance with approved (and preliminary
qualification test) inspection plans and procedures.

##### Electromagnetic Interference Test 

The Contractor shall show compliance for COTS equipment by showing that
all such COTS equipment meets the requirements of FAA-G-2100H and all
appropriate Federal Communications Commission (FCC) authorizations as
defined in 47CFR 2 and 47CFR 15 of the FCC Rules and Regulations. For
equipment chosen for use in the RWSL system that has not been certified
to meet Electromagnetic Interference (EMI )specified requirements
through FAA advisory circulars or FCC authorizations, the Contractor
shall perform EMI tests and provide data showing that the equipment
meets EMI requirements.

##### Environmental Test

The Contractor shall show compliance for all designed and COTS
equipments by testing in accordance with the requirements of
FAA-G-2100H.

The Contractor shall show compliance with environmental requirements by
supplying manufacturer specifications for COTS equipment as stated in
section FAA-G-2100H. If COTS equipment is placed in an enclosed cabinet,
then said equipment/cabinet must be tested to comply with the
requirements FAA-G-2100H. For equipment chosen for use in the RWSL
system that has not been certified to meet current environmental
requirements stated in the FAA-G-2100H, the Contractor shall perform
environmental tests and provide data showing that the equipment meets
environmental requirements.

##### Reliability, Maintainability, and Availability Analysis

Reliability, Maintainability, and Availability (RMA) analysis shall be
performed in accordance with sections 3.3.1.13 and 3.3.1.14 of this
document. Maintainability tests shall include nondestructive fault
insertion for each LRU to demonstrate BIT compliance. Removal and
replacement of each LRU shall be conducted to verify applicable
requirements from FAA-G-2100H. With Government approval large LRU
removal and replacement may be conducted by paper walk through.

For RMA testing, individual light bulbs shall be considered consumables.
Individual light failures shall not be considered critical failures as
long as the resultant light failure(s) do not cause the RWSL system to
exceed the light timing requirements. Any failure that causes the RWSL
system to exceed light timing requirements shall be considered a
critical failure. For the RMA analysis it can be assumed that individual
light failures will be repaired within 45 days. The Contractor shall
estimate the maximum number and type of light failures that might occur
in 45 days.

####### Reliability Development Growth Test (RDGT)

The Contractor shall conduct a RDGT through the life of the contract.
This test shall be conducted on all equipment following site acceptance.
The Contractor shall maintain a chronological log throughout the RDGT.
The RDGT log shall provide the dates and times of all significant
events. At a minimum these events shall include:

-   Power on and off times of each system or subsystem.

-   A running total of the number of RDGT hours for the
    Subsystem/system.

-   Start and Stop times of testing, all interruptions, including all
    failure details, any unusual conditions in the equipment under test,
    auxiliary equipment, source power, or environment, any repairs or
    adjustments made as well as parts replaced.

-   Start and Stop times of any simulators.

The RDGT shall be conducted to identify, analyze, and resolve system
reliability problems over the life of the contract. During the RDGT, all
failures, including critical, non-critical, relevant, and non-relevant,
shall be analyzed and corrective action proposed by the Contractor.
Failure relevance shall be determined in accordance with Section
3.4.1.3.4.2. Each failure shall be recorded and analyzed and all
relevant failures shall be corrected by repair and/or design or
manufacturing changes to cure the identified cause of the failure. The
Contractor shall be required to correct all relevant failures in
accordance with the corrective action proposed by the Contractor and
approved by the Government. The Government will approve repair and/or
design or manufacturing changes to correct all relevant failures. The
Government will witness each time the system is maintained to assure
that each failure is recorded and that preventive maintenance,
corrective maintenance, and incorporation of design and/or manufacturing
improvements are done in accordance with prescribed maintenance
procedures or approved system improvements.

All systems delivered to the Government shall incorporate all approved
design and/or manufacturing improvements that result from the RDGT.

As part of the RDGT, the Contractor shall collect light bulb usage and
failure rate data. This data shall be compiled to determine the average
number of hours a bulb lasts based on the number of hours from
installation and the number of light illumination hours. This data shall
be compiled separately for REL fixtures and THL fixtures and reported
for each airport individually.

####### Failure Relevance Definitions

> A relevant failure is a failure, which can be attributed, after
> failure analysis, to any of the following:

1.  Any maintenance or software action required to maintain specified
    system performance.

2.  Failure of the system to reconfigure automatically within the
    specified channel switchover and restoration time so as to maintain
    specified system performance.

3.  Hardware or software/firmware design defects.

4.  Manufacturing process, material or workmanship defects.

5.  Physical or functional deterioration (such as wear out, fatigue, or
    tolerance degradation).

6.  Failure of parts of known limited life occurring prior to the end of
    the stipulated period.

7.  Intermittent failure.

8.  Failures due to incorrect instruction in the technical manuals.

9.  Any other failure that is not listed as a non-relevant failure.

> A non-relevant failure is a failure, which can be attributed, after
> failure analysis, to any of the following:

a.  Damage resulting from improper installation.

b.  Failure of test instrumentation or monitoring equipment that is
    external to the test equipment under test.

c.  Interrupted operation caused by external power failures.

d.  Equipment failures caused by externally applied over-stressed
    conditions in excess of the specified requirements.

e.  Damage resulting from accident or mishandling by personnel
    performing the RDGT.

f.  Failures due to procedural errors by technicians or operators.

g.  Dependent failure (i.e., a failure of a part(s) as a direct result
    of a failure of another part within the same LRU). The vendor shall
    determine that the failure(s) was dependent upon another part
    failing and was not an unrelated incident occurring at the same
    time.

h.  Failure of certain parts (limited life parts) occurring after their
    known useful life has expired will not be counted as relevant if
    identified and approved by the Government prior to start of the
    RDGT.

##### Electrical Test

The contractor shall comply with the electrical power requirements as
defined in the RWSL System Specification FAA-E-3001, RWSL FLS
Specification FAA-E-3002, and FAA-G-2100H. For equipment that will be
installed in the FAA tower, the Contractor shall provide assistance to
the FAA Technical Center Power Test Group while they are performing
additional electrical power tests prior to the equipment being placed on
the FAA electrical bus.

##### Maintainability Demonstration (M-Demo)

The M-Demo shall be performed in accordance with MIL-HDBK-470A, Task
301. The Contractor shall conduct an M-Demo using MIL-HDBK-470A as
guidance for the development of the M-Demo test plan. The Contractor
shall use MIL-HDBK-470A as guidance to calculate the MTTR of each RWSL
LRU to determine that MTTR requirements are met.

##### Site Development Qualification Test (SDQT)

The Contractor shall perform a SDQT at the key site to satisfy those
requirements that require an operational environment not available at
the Contractor's facility. SDQT shall be conducted on a 1^st^ Article
system.

In general, targets of opportunity shall be used during the conduct of
SDQT. If needed, the Government will provide test vehicles or test
aircraft.

##### System Timing and Performance Test

The Contractor shall perform a RWSL system timing and performance test
on site to verify all RELs and THLs are meeting system timing and
performance requirements. The Contractor shall demonstrate correct
system timing performance with the maximum number of light failures as
determined in the RMA analysis. This will be done by masking the lights
on the field, individually failing RELs, THLs and individual light
components, and collecting timing and performance data on the RWSL
system.

##### System Adaptation and Map Verification Test

The Contractor shall verify the system adaptation and map set for the
entire airport movement area.

##### Cable High Potential Maintenance Test

##### The Contractor shall perform a cable high potential maintenance test in accordance with FAA Order 6950.22.  {#the-contractor-shall-perform-a-cable-high-potential-maintenance-test-in-accordance-with-faa-order-6950.22. .unnumbered}

#### Operational Test and Evaluation 

The Contractor shall provide system maintenance and operation support
during the Government conducted operational testing at the First Article
Key Site. This includes, but is not limited to, Operational Test and
Evaluation and Independent Operational Test and Evaluation.

#### Regression Tests

The Contractor shall be responsible for corrective action necessary to
ensure full specification compliance. Failure of the RWSL system
equipment to meet specified requirements as identified in the SPR shall
cause the Contractor to determine the reason for the non-compliance. The
Contractor shall complete repair or rework prior to submission for
re-testing. The Government Test Director will determine the extent of
re-testing required. No formal re-testing shall be commenced until the
Contractor has submitted in writing all information concerning the
non-compliance and the corrective action taken, and the Government Test
Director agrees to start the re-testing. If a review of the reasons for
failure to comply with RWSL system or FLS specification requirements
indicates that the cause may exist as latent defects in items previously
accepted, the Contractor shall be responsible to correct the defects in
a timely manner, even those previously accepted by the Government. The
Contractor shall re-verify, by the verification method identified in the
RWSL system VRTM, that the defect(s) have been corrected. The Contractor
shall utilize the problem reporting system for reporting the re-testing
plans, procedures, and results.

#### Production Acceptance Test and Evaluation (PAT&E)

The Contractor shall perform PAT&Es on each delivered system to verify
that end-items (1) conform to applicable specifications, (2) are free
from manufacturing defects, and (3) are substantially identical to the
qualified hardware. These tests shall ensure compliance to system-level
hardware and software requirements of the RWSL System Specification
FAA-E-3001. PAT&E shall consist of FAT and SAT.

##### Factory Acceptance Test (FAT)

The Contractor's quality assurance function shall perform FATs at the
factory for each delivered item to verify that it (1) conforms to
applicable specifications, (2) is free from manufacturing defects, and
(3) is substantially identical to the qualified hardware. The FAT
procedure is validated after DT&E at the factory on the production
system.

##### Site Acceptance Test (SAT)

The Contractor shall perform SATs at each field site before acceptance
of the system by the FAA. SAT procedures are validated during DT&E and
constitute part of PAT&E when being conducted at field deployment sites.

### Construction, Delivery, Installation and Checkout

The Contractor shall be responsible for all construction, equipment
delivery, installation, integration, checkout and support to the
Government for Operational Test and Evaluation or other activities as
directed by a Government issued Task Order. All activities at the
airport shall be in accordance with the applicable advisory circulars
referenced in Section 2 of this SOW. The construction at some airports
may be accomplished by the Government and/or the airport authority when
it is more cost-effective or advantageous to do so. In addition, at
airports where it is determined that there is no room in existing vaults
or where it is advantageous to the Government, some of the RWSL
equipment may be installed in Government Furnished Shelters. In such
cases, the Government will provide GFP shelters for the housing of the
RWSL equipment. The Contractor shall ship all shelter components to the
Mike Monroney Aeronautical Center (MMAC) Logistics Center for
installation of the equipment into the shelter. This equipment may
include, but is not limited to, constant current regulators (CCRs),
master light controller (MLC), fiber optic converters and switches, and
remote monitoring equipment. The Government will install the equipment
within the shelter per the Contractor specifications. The Contractor
will provide an on-site representative for quality assurance for the
first six (6) shelters. The Government will ship the fully populated
shelter to the site for Contractor installation and integration. Should
the Government elect to provide such shelters as GFP, the Government
will inform the Contractor who will then provide their required delivery
schedule to support the contractual RWSL site installation completion
date.

The Contractor shall be responsible for providing the following:

-   Personnel, equipment and materials required for the safety, quality
    control, and establishment of each RWSL system at designated sites.

-   Construction on airport property, when directed as part of the
    Government issued task order.

-   Installation, integration, test, implementation, alignment,
    checkout, and acceptance testing of the RWSL system.

-   Full-time supervision and direction of its personnel and
    subcontractors during all site activities.

The breadth and depth of services required shall be determined at each
site and shall be based upon site surveys plus coordination with site
personnel. The Contractor shall consider a typical RWSL installation to
include the RWSL processor, all FLS equipment and supporting
infrastructure, and systems required for operation of the RWSL system.
The Government will designate an FAA Installation POC for coordination
and oversight of all on-site activities. The Contractor shall provide
Airport Construction Coordinators (ACCs) to cover all periods of time
when construction activities take place within the Airport Operations
Area (AOA) of the airport for the entire life of the project.

The Contractor shall also comply with the following Government
regulations:

-   National Environmental Policy Act (NEPA) of 1969.

-   FAA Order 1050.1E, Policies and Procedures for Considering
    Environmental Impacts.

-   FAA Order 1600.1E, Personnel Security Program.

Installation of the FLS equipment will comply with all applicable codes,
rules and regulations on the site as well as AC 150/5370-2E, Operational
Safety on Airports During Construction.

#### Implementation Management 

The Contractor shall submit an Implementation Task Plan for each site in
accordance with DID IC01 providing the details of the plans for
construction, installation, integration and test of the full RWSL system
at the site. The Contractor shall manage the implementation and shall
perform the following activities:

-   Site engineering.

-   Subcontract design specification preparation, award, administration,
    inspection, and acceptance

-   Management and coordination of subcontractors' activities.

-   Integration and management of facility site preparations and
    physical facility modifications.

-   Construction on airport property, when directed as part of the
    Government issued Task Order.

-   Management of equipment installation at the site, to include
    installation of in-pavement lights on the airport movement area.

When so directed through the task order, the Contractor shall perform
the Engineering Site Survey, prepare a Contractor Site Engineering
Report (CSER) (3.5.2.3), prepare construction design specifications, and
obtain any construction permits necessary before the installation.

After the installation of the FLS, the Contractor will provide required
support during the systems integration and interface testing of the RWSL
system.

CDRL IC01 Implementation Task Plan

##### Priority and Coordination of Activities 

Air Traffic Control (ATC) activities and services shall have priority
over all Contractor construction and installation activities. There
shall be no compromise for the safe and timely control of aircraft
during the installation period. The Contractor shall provide services in
such a manner which avoids disruptions to ATC facilities and conforms to
the procedures considered essential by the Government for assuring
safety for air traffic control. Site preparation, physical facilities
construction, installation, inspection, and acceptance testing and the
movement (on/off airport or on/off other FAA sites) of equipment shall
be coordinated through the FAA POC. The FAA POC will coordinate such
activities with local and regional air traffic and airways facilities
personnel for final scheduling. Any required shutdowns of facilities to
accommodate the RWSL installation or testing shall be coordinated
through the FAA POC.

Facility heating, ventilation and air conditioning systems, any
primary/secondary power, and telecommunications systems shall not be
impacted during installation; supplemental HVAC shall be provided as
required.

Work shall proceed on a regularly scheduled basis through completion.
The Contractor shall notify the Government of any equipment, item, part
or service necessary for the proper installation of the RWSL not
specifically identified herein or in the RWSL System Specification
FAA-E-3001 or the RWSL FLS Specification FAA-E-3002 ninety days prior to
the delivery. Equipment, items, parts, or services specifically required
to install and test the RWSL within the designated area shall be
provided by the Contractor. Any installation hardware shall be new
material.

##### Site Security 

A security program to minimize risk to personnel, equipment, and other
RWSL assets on-site shall be incorporated in the CSER for construction
and installation phases of the program. The Contractor shall use the
applicable security requirements contained in FAA Order 1370.82A as a
guide. Implemented security shall be subject to Government approval.

The RWSL Contractor shall comply with FAA security controls as
determined by the FAA POC. All personnel security policies, requirements
and procedures, as stated in FAA Order 1600.1E, "Personnel Security
Program", shall be followed. The Contractor shall ensure that
appropriate technical, administrative, physical, and personnel security
requirements are implemented to ensure integrity, availability, and
confidentiality throughout the contract. RWSL system provider personnel
shall comply with FAA security controls implemented in accordance with
FAA policy.

The Contractor shall provide the FAA POC with a list of Contractor\'s
personnel and subcontractor's personnel who will require access to the
site. The list shall be kept current during project work. The Contractor
shall provide all personnel with readily identifiable numbered badges
during the period their access to the site is required. Badges shall be
shown to the Government on-site representative prior to site entry and
shall be worn on outer clothes while at work at the site.

The Contractor shall adhere to all specific security requirements in
accordance with airport policy and procedures. These should be discussed
as part of the initial site survey visit and documented in the Security
Plan portion of the CSER for approval by the Government.

##### Clean Up 

The Contractor shall be responsible for removing from the site all
surplus material such as tools, equipment, etc., belonging to the
Contractor and to clean up rubbish and debris resulting from the
modification/installation work. The Contractor shall leave the site in a
neat and workmanlike appearance. The Contractor shall conduct a foreign
object damage (FOD) inspection upon completion of work and prior to
releasing for operation. Upon completion of \"clean-up\" operations and
FOD inspection, the Contractor shall obtain a written release from the
FAA POC that the site has been restored to a satisfactory condition.

##### Damage to Site

Damage to facility buildings or premises caused by the Contractor\'s
activities shall be repaired by the Contractor to "as new" condition.
Damage and finish degradation of any building, electronic subsystem
interior or exterior surface and other installed equipment resulting
from transportation and installation activities shall be repaired or
replaced by the Contractor. Damage to critical operations infrastructure
shall be reported immediately and repaired immediately, with
notification to the FAA POC. All repairs shall be fully documented. The
Contractor shall be responsible for all such repairs at no additional
cost to the Government.

##### Contractor Use of Premises

The Contractor shall have access to facility environmental equipment
only after receiving approval from the on-site Government
representative. The job site shall be maintained by the Contractor in a
neat and orderly condition. This includes the daily removal of rubbish,
waste, tools, equipment, and materials not required for the work in
progress.

#### Construction

The Contractor shall be responsible for all construction activities when
directed through the Government issued Task Order. This shall include
the planning, site survey, site engineering report, construction and any
required support activities, clean-up, and site inspection and
acceptance by the Government and the Airport Authority.

##### Site Survey Criteria

> The Contractor shall adhere to the following criteria as part of the
> site survey:

a)  The interior equipment installation and spacing rules shall follow
    Standard 29 CFR 1910, Occupational Safety and Health Standards.

b)  FAA-C-1217F, Electrical Work, Interior, FAA-STD-032, Design
    Standards for National Air Space Facilities, and NFPA No. 70,
    National Electrical Code, shall be used as facility design standards
    for each specific location of an RWSL system.

c)  System(s) shall not create obstructions to visibility or movement
    within the Air Traffic Control Tower cab. Additional physical space
    requirements to install the RWSL system shall not restrict existing
    operations.

d)  RWSL system(s) placement shall be in accordance with Federal Air
    Regulation 14 CFR, Part 77, Objects Affecting Navigable Airspace,
    and AC 150/5300-13, Airport Design Standards.

e)  Installation and placement of in-pavement lights shall be in
    accordance with AC 150/5340-30C, Design and Installation of Airport
    Visual Aids, and the FLS Specification FAA-E-3002.

f)  Installation of the in-pavement lights on the movement area of the
    runway must adhere to Advisory Circular, AC 150/5370-2E, Operational
    Safety on Airports During Construction.

g)  Installation of equipment in a movement area shall comply with
    obstacle limitation requirements as contained in title 14 CFR, Part
    77.

h)  RWSL system installation shall meet seismic safety requirements as
    stated in Executive Orders 12699 (Seismic Safety of Federal and
    Federally Assisted or Regulated New Building Construction)
    and 13286. Local jurisdiction ordinances may also apply.

i)  The facility heating, ventilation and air conditioning systems in
    the Air Traffic Control Tower (ATCT) and airfield lighting
    vaults/shelters shall not be impacted during installation of RWSL.

j)  FAA-G-2100H, Electronic Equipment, General Requirements, Appendix I,
    "Applicability to Procurements for COTS/NDI equipment" or the
    National Fire Protection Association's National Electrical Code®
    (NFPA 70) and other national standards related to the specific needs
    of emerging technical requirement for ATC systems, shall apply.

k)  The Airport Layout Plan (ALP) shall be supplemented and verified by
    visual inspection of utility locations prior to construction.

l)  The RWSL system shall be located in a controlled access facility.

m)  All cables and other components connecting to the rest of the RWSL
    system shall be routed along mullions or within other existing
    structural elements of the cab tower to minimize visual blockage and
    interference with personnel movement.

n)  All field cable installations shall be in accordance with the
    requirements of FAA-C-1391B, Installation and Splicing of
    Underground cables.

##### Site Survey Requirements

The Contractor shall conduct a site survey for all designated sites. The
Contractor shall conduct site surveys of the first 21 sites starting 90
days after contract award, with two (2) site surveys convening each
month until all site surveys are complete. Site surveys will be
conducted by personnel familiar with RWSL Siting Criteria to ensure that
the selected sites satisfy all requirements. The Government will provide
operational requirements and priorities for each airport by letter. This
information will include specific equipment requirements (e.g., number
and location of FLS systems). The Government will provide site
information to the Contractor to show geographic locations with each
preliminary equipment destination, Airport Layout Plans including
airport movement and non-movement area engineering drawings, physical
interfaces, available Government resources, facility drawings, POCs, and
other available information to assist the Contractor in planning each
site installation. This information will be provided no later than 30
days prior to the scheduled site survey. The information will, as a
minimum, identify to the Contractor the specific locations that define
the intended site.

The site survey visit shall be coordinated at least 30 days in advance
of the proposed start of the site survey. A site survey meeting will be
convened to exchange information with the Government and airport
authorities, to provide notification of work to be accomplished in the
site survey and to obtain information on procedures to be followed, do's
and don'ts, and airport specific rules, regulations, or other
information that could affect the conduct of the survey. The agenda for
the meeting will be provided in advance by the Government. The
Contractor shall document the results of the meeting in meeting minutes
per CDRL PM11. The site survey visit shall begin with a briefing to site
personnel describing the RWSL system, interconnections, information to
be gathered, and a discussion of the potential impact to operations
during the installation phase. The Contractor shall prepare a generic
site survey checklist that shall be used to conduct the site surveys and
shall be adapted for each site, according to a Government-approved
survey schedule, to acquire site-specific information required for
performance of the system installation activities. The Contractor shall
also complete a survey of each RWSL location to include all RWSL
components, according to a Government-coordinated survey schedule, to
acquire site-specific information required for performance of the system
installation and integration activities. The siting shall be in
accordance with RWSL GFI siting criteria document as well as airport
design criteria. The Contractor shall coordinate the survey with the FAA
POC. The Contractor shall allow the FAA POC to fully participate in the
survey. The Contractor shall further discuss siting methodology and
requirements with the FAA POC such that the POC fully understands survey
objectives and results

The Contractor shall conduct a site survey for all designated sites. The
Contractor shall prepare a list of system installation constraints, such
as maximum cable lengths, power requirements, space requirements and
building or construction requirements, weight, and HVAC loads and shall
submit the list to the Government as part of the CSER (3.5.3.3). Space
shall be identified for prime mission equipment, physical storage space,
monitor and control space, maintenance space, Airfield Lighting
Equipment and other administrative space required to support the life
cycle of RWSL system. At each site survey, the Contractor shall work
with the Government to determine installation requirements for that
specific site.

##### Site Engineering Reports 

The Contractor shall provide a CSER to the Government for each FAA
designated site in accordance with CDRL IC01. After the site survey for
each site, the Contractor shall develop a Site Survey Report, which will
be delivered as part of the preliminary CSER. Based upon the information
provided by the Government prior to the site survey and the information
gathered at the site survey, the Contractor shall document in the
report 1) the actions that shall be performed by the Contractor prior to
system delivery and 2) the actions that will be performed by the
Government. A cost estimate shall be included for each site. The
Government will identify Airport Authority, FAA Air Traffic, FAA
Technical Operations, and any other personnel for coordination to obtain
instructions and requirements regarding safety, insurance, bonding, and
movement of Contractor personnel and equipment on the airport. As part
of each CSER, the Contractor shall deliver site-specific drawings that
include certified engineering drawings for the FLS and runway
in-pavement light installation part of the system. The site-specific
drawings shall be in an integrated drawing package with information from
several sources superimposed with new RWSL site installation data. These
drawings shall contain the appropriate regional title block and
site-adapted notes referencing the RWSL site or other drawing numbers
used to produce them. The Contractor shall participate in the
Government's risk mitigation planning using the FAA Pre-Construction and
Maintenance Project Safety and Health Checklist, Order 3900.57. Storage
and security of on-site materials shall be the responsibility of the
Contractor and shall be addressed in the CSER in accordance with CDRL
IC01. After Government review of the Preliminary CSER, the Contractor
shall incorporate changes and provide a final CSER with completed cost
information for Government approval. The Contractor shall not commence
any site installation activity until final approval of the CSER is
received from the Government.

[]{.mark}

CDRL IC02 Contractor Site Engineering Report

##### Red-lined and Government Facility Drawings 

The Contractor shall red-line site specific (e.g., airport movement and
non movement areas) and FAA facility drawings to show any changes
resulting from the installation and actual placement of RWSL equipment.
Red-line markings shall include, but not be limited to, wiring diagrams
(including color-coding), identification, and terminations. All markings
shall be legible and depicted in a manner that will enable the
Government to verify corrections to the original drawings. All drawings
and changes shall be in accordance with FAA-STD-002F. The following
drawings shall be made current to reflect the particulars of a given
site:

-   Installation Drawings. These drawings shall be modified to indicate
    actual dimensions, cable runs, and concretion specifics.

```{=html}
<!-- -->
```
-   Government Facility Drawings. These drawings shall include
    Government drawings of the ATCT and support buildings that show
    details of cable trays, equipment rooms, and console layouts. These
    drawings shall also include the Facilities General Layout Plan.

-   Engineering drawings for airport movement and non-movement areas:
    These drawings shall include airport drawings that show details of
    cabling, in-pavement light locations on the runway and taxiways,
    equipment rooms, and installation methods. These drawings shall also
    include the Airport General Layout Plan.

-   Facility Standard Drawings. These drawings are specific to the
    individual requirements of the RWSL equipment. Facility Standard
    Drawings will require Government approval.

CDRL IC03 Red-Lined Drawings

CDRL IC04 Facility Standard Drawings

##### Facility Site Preparation, Construction and Physical Facility Modification 

After Government approval of the CSER, the Contractor shall perform site
preparation and site modifications to prepare for installation of each
RWSL system. The facility site preparation and physical site
modification shall be accomplished in accordance with the RWSL FLS
Specification FAA-E-3002 and the approved CSER in accordance with
applicable ACs. The Contractor shall determine, select, provide, and
install cables and connectors necessary to connect the RWSL equipment to
the Government-designated power sources. All facilities shall be
grounded and bonded in accordance with current FAA orders,
specifications and NFPA requirements. Facility modification and design
shall be in accordance with current FAA orders, specifications and NFPA
requirements. Power installation shall be to the power bus. The services
required for the movement of Contractor personnel, mail, and materials
at each location shall be the Contractor\'s responsibility. Construction
shall allow for installation of FLS components into designated
runway/taxiway entrances; provision and routing of electrical and
fiberoptic communications cabling; and provision, installation and
connection of electrical equipment, where adequate equipment does not
exist, e.g., disconnect switch, 480 volt input panel, high voltage
output cabinet, utility transformer, distribution panel, etc.

The Government will provide to the Contractor three (3) acceptable
specifications and elevation drawings for the GFE shelter foundation to
be constructed at each site. The size of the shelter will be determined
by the Government from the CSER. The Contractor shall select the most
suitable foundation type from the three specifications provided for
consideration, based upon the Contractor's determination of the
applicable soil type, drainage requirements and other pertinent
information. The Contractor shall ensure that the appropriate footing
sub-grade, bearing pressure and anticipated settlement are considered
and applied to the construction of the shelter foundation. The
Contractor shall ensure that all local and national building codes and
seismic codes are followed in the design and construction. Areas
disturbed during construction shall be returned to the original or
natural state. Preventive measures shall be taken to ensure proper
drainage of the site and to prevent erosion or run off of excavated
soil.

For all construction activities, the Contractor shall:

a)  Participate in the pre-construction meeting with the FAA, airport
    representatives and other affected parties for discussion of
    activities, schedules, associated plans and procedures, and rules
    and regulations. The Contractor shall provide an Agenda and Minutes
    in accordance with CDRLs PM10 and PM11.

b)  Perform the civil site preparation per approved plans.

c)  Comply with environmental assessment/categorical exclusion
    requirements, if applicable.

d)  Perform clearing, earthwork, grading and drainage at each facility
    location.

e)  Engage in construction for the RWSL, FLS and associated equipment,
    as applicable.

f)  Install power and control cables in accordance with the requirements
    of FAA-C-1391B, installation and Splicing of Underground Cables.

g)  Provide trenching and cabling for all intra-airport RWSL
    connections. Land line communications from the ATCT to each
    vault/shelter shall be installed via fiber optic cable and comply
    with FAA-STD-057 Airport Fiber Optic Communication System (FOCS)
    Standards.

h)  Coordinate site restoration and facility clean-up.

i)  Prepare "as-built" design drawings, CDRL IC05.

j)  Notify the designated FAA POC and Airport designated authority
    within 5 minutes if any problems occur during any phase of the
    construction. After action, provide an incident report, including
    any required OSHA reporting, in accordance with instructions to be
    furnished by the RWSL Program Management Office within 24 hours.

k)  Secure all state and local permits, as applicable.

l)  Coordinate any required storage and security of all equipment
    delivered to the project site for purposes of installation.

m)  Coordinate a contractor's staging area.

n)  Coordinate all required access to the RWSL sites for construction
    activities.

o)  Ensure securable warehouse or hangar space is adequate; otherwise,
    space appropriate for a construction office trailer will suffice.

p)  Provide a list of submittals and technical documentation for
    Government Furnished Material/Information List to be installed in
    support of the construction. The submittals shall be included in the
    specific airport CSER. The FAA will review and approve the
    submittals.

q)  Conduct a construction final inspection and Site Acceptance with the
    Government as described in the Implementation Task Plan.

r)  Coordinate all shift start/stop times in advance with FAA POC and
    designated airport authority.

s)  Conduct daily clean-up and foreign object damage inspection upon
    completion of work and prior to releasing for operation.

#### System Installation

The Contractor shall install the CLIN 001 RWSL system at the location
listed in Section F, as well as additional sites in accordance with
approved CLINs. Install FLS hardware per the following table:

**Table 2: FLS Equipment**

  ---------------------------------- ------------------------------------
  **Item**                           **Relationship**

  Light Computer                     Nominally one per airport (dependent
                                     on a site-by-site basis in
                                     accordance with the FLS
                                     specification)

  Constant Current Regulator (CCR)   Nominally two per equipped runway,
                                     one for RELs and one for THLs

  RWSL Processor                     One per airport

  Control Panel                      One per Air Traffic Control Tower
                                     (ATCT)

  Master Light Controller            One per CCR

  Remote Maintenance Display         One per vault/shelter

  Semi-Flush Light Fixtures - THL    Nominally thirty-two (32) per array

  Semi-Flush Light Fixtures - REL    Nominally six (6) per Intersection
  ---------------------------------- ------------------------------------

Installation at RWSL sites includes, but is not limited to, the
following typical items:

-   Electrical wiring and FLS equipment (including CCRs, cable, conduit
    and in-pavement lights).

-   Mechanical mounting and grounding of all RWSL components.

-   Connection with distribution, demark, and terminal panels, boxes,
    and cabinets.

-   All required testing for quality assurance of construction and
    installation.

-   All required documentation in accordance with this SOW, CDRLs and
    specifications.

As part of the installation, the Contractor shall install the RWSL
system including processor, FLS, and auxiliary equipment in accordance
with the Government approved CSER, and shall ensure the following:

-   The RWSL system installation and implementation shall be
    accomplished within the framework of NEPA of 1969 and FAA Order
    1050.1E, "Policies and Procedures for Considering Environmental
    Impacts."

```{=html}
<!-- -->
```
-   The installation and spacing rules shall follow Standard 29 CFR
    1910.

```{=html}
<!-- -->
```
-   The facility heating, ventilation and air conditioning systems shall
    not be impacted during installation of RWSL.

```{=html}
<!-- -->
```
-   Conduits and cables shall be of standard type and appropriate for
    their applications in accordance with FAA-C-1391B, Installation and
    Splicing of Underground Cables.

```{=html}
<!-- -->
```
-   Installation and checkout shall be performed without disrupting
    current air traffic services and will not require additional
    workload from Air Traffic (AT) or Technical Operations (AF)
    personnel at the facility while performing their normal duties.

```{=html}
<!-- -->
```
-   Integration with existing equipment and coordination with facilities
    shall be the responsibility of the Contractor under the direct
    guidance of the designated the FAA POC.

```{=html}
<!-- -->
```
-   Preliminary work done in advance of installation that will disrupt
    ATC operations or airport operations shall be performed during
    non-peak operating hours.

```{=html}
<!-- -->
```
-   All work to be performed on-site shall be coordinated with the FAA
    POC.

```{=html}
<!-- -->
```
-   The Contractor and all subcontractors shall be responsible for
    meeting the security requirements of the airport authority and
    obtaining necessary access badges. Access to movement and
    non-movement areas of the airport may require Government escort.

-   The Contractor shall provide paper red-lined drawings for all FAA
    official drawings affected by the installation.

The Contractor and subcontractors shall use only factory-trained
personnel for installation supervision of field work. Subcontractors
used by the Contractor (e.g., electrical, rigging, crane service, labor,
trash removal, and other miscellaneous work and services) shall be the
responsibility of the Contractor and under direct supervision at all
times.

The Contractor shall be responsible for the unloading, care, and
protection from weather, theft, vandalism, or other factors of all
materials (GFE, Contractor Furnished Equipment, etc.) delivered until
completion and final acceptance by the Government.

##### Site Optimization

The Contractor shall provide analytic and software adaptation support to
the Government for site optimization of the First Article RWSL key site
prior to SAT.  Site optimization shall determine and tailor/implement
the site specific parameters to airport users and site environment
conditions. The Contractor shall provide a guide that can be used by the
Government for accomplishing successful site optimization at additional
sites.

##### Test Equipment 

The Contractor shall furnish all necessary standard test equipment and
special test equipment for maintenance, testing, and installation
activities on the RWSL system during installation and acceptance.
Required installation procedures, tuning/optimization adjustments,
maintenance procedures, and testing shall be performed using only the
test equipment, special and common, identified by the Contractor to the
Government for this purpose in accordance with the RWSL specification
and this SOW. The use of any other test equipment by Contractor is
prohibited unless approved by the Government.

##### Final As-Built Drawings 

The Contractor shall accurately and promptly amend (for all original
drawings) the changes, revisions, or additions resulting from the RWSL
installation. This amending process shall reflect the current
\"As-Built\" status. The amendment process shall apply to all
site-specific Contractor-generated drawings and Government facility
drawings that were \"red-lined\" during installation, and also to any
RWSL standard drawing. The drawings shall be amended with the
appropriate regional title block, facility title, and completed revision
block. The application of FAA-STD-002F, Standard Engineering Drawing
Preparation & Support, is required for all construction drawings. The
As-Built Drawings shall be prepared and submitted in accordance with
CDRL IC05.

CDRL IC05 Final As-Built Drawings

#####  Contractor Acceptance Inspection

At the completion of all construction, installation and test activities,
the Contractor shall perform the Contractor Acceptance Inspection (CAI)
to demonstrate conformance with equipment specification and standards at
each site.  At completion of testing, in accordance with the requirement
of Section 3.4.4.2 of this SOW, the Contractor shall submit a complete
report (TE04) of the results of the SAT tests to the Government for
approval. The contractor in conjunction with the Government shall
perform a CAI using a CAI checklist to confirm that the RWSL system is
working according to system specification.  The successful completion of
the CAI results in the official transfer of ownership of the system to
the FAA.

### Integrated Logistics Support 

The Integrated Logistics Support (ILS) effort begins upon contract award
and evolves throughout the development, test, installation and Interim
Contractor Depot Level Support (ICDLS). The Contractor shall plan,
manage, and execute an ILS program that addresses applicable elements of
logistics using the Acquisition Management System ILS Process Manual as
guidance. The ILS Process Guide is located on the FAST toolset at
fast.faa.gov (go to "Specialty Functions, Processes and Guidance, under
the Integrated Logistics Support heading). The Contractor shall
establish and maintain an ILS Program in accordance with this SOW. The
ILS is an interrelated, unified, and iterative approach to the
managerial and technical activities that support the RWSL Program. The
analyses associated with ILS influence system configuration to minimize
the life cycle cost. Through the ILS process, support requirements are
identified and acquired. The following paragraphs describe the intended
minimum ILS activities associated with the development of the RWLS
design and implementation activities.

#### ILS Program Management 

The Contractor shall designate an ILS Manager to serve as a single point
of contact between the Contractor and the Government Associate Program
Manager, Logistics (APML) in all matters relating to the ILS
requirements of the contract.

A joint Government/Contractor sponsored ILS Management Team (ILSMT) for
RWSL shall be established and shall serve as the primary management
vehicle for monitoring the status of the ILS program. The chairperson of
the ILSMT is the FAA APML. The ILSMT provides a means for coordinating
and monitoring logistics-related schedules and contract performance, and
reviews the adequacy, timeliness, and compliance with related contract
requirements. The ILSMT shall meet semi-annually or when requested by
the APML, not to exceed four meetings per year. ILSMTs shall be
conducted at mutually convenient locations, but usually at the
Contractor\'s facility.

The Contractor shall be responsible for the following:

-   Providing an agenda and minutes for each meeting. The agenda shall
    also provide for status reporting and analysis of problem areas. The
    agenda and meeting minutes, accompanied by a summary of action
    items, and all presentation materials used, shall be submitted for
    Government approval in accordance with CDRLs PM10 and 11.

-   Attending ILSMT meetings and assuring that subcontractor and
    engineering personnel are available when requested.

-   Briefing the status of the logistics elements and address support
    issues identified on the agenda.

##### Conferences

##### Logistics Guidance Conference

A Logistics Guidance Conference (LGC) shall be conducted at the
Contractor\'s facility in conjunction with the post-award conference.
The FAA APML will chair the meeting. Contractor logistics personnel
shall present the Contractor's approach to accomplish the required
logistics tasks. The Contractor shall support the conference with the
required resources (e.g., briefings, personnel, and facilities). The
Contractor shall provide an agenda and all presentation materials prior
to the meeting and minutes and action items after the meeting for
Government approval. The LGC shall clarify provisioning requirements and
issues (e.g., provisioning deliverables, data requirements, technical
documentation, and Engineering Data for Provisioning). The subjects the
Contractor shall be required to address at the LGC include the following
and shall follow CDRLs PM10 and 11:

-   Maintenance Planning

-   Manpower and Personnel

-   Supply Support

-   Support Equipment

-   Technical Data

-   Training and Training Support

-   Computer Resources Support

-   Packaging, Handling, Storage, and Transportation

-   Facilities Integrated Logistics Support (ILS) Management

##### Provisioning Conference 

The Contractor shall host and support a Provisioning Conference to be
conducted at the Contractor\'s facility no later than 30 days after the
PCA. Subsequent Provisioning Conferences (not to exceed three) shall be
conducted when requested by the Government. The Contractor and
subcontractor/vendors, as determined by the Government, shall attend,
participate, and contribute expertise to the Government in resolution of
provisioning and supply support problems or issues. The Contractor
support to the conference shall also include facilities, materials,
office equipment, clerical personnel, mockups, and technical data to
include drawings. The Contractor shall provide an agenda, minutes, and
presentation materials in accordance with CDRLs PM10 and 11, as well as
a summary of action items, for Government approval.

#### Integrated Support Plan 

The Contractor shall prepare and implement an Integrated Support Plan
(ISP) that provides a detailed description of the procedures, actions,
events, milestones and organizations the Contractor intends to employ to
successfully accomplish the ILS Program.

[]{.mark}

CDRL LM01 Integrated Support Plan

#### RWSL Maintenance Concept 

The RWSL maintenance concept is comprised of two-levels, site and depot,
with maintenance to be performed at both levels.

**Site maintenance** is intended to be centered on removal and
replacement of LRUs and will include periodic, preventative and
corrective maintenance. Periodic and preventative maintenance for the
system will be required no more frequently than four times per year and
will require no more than four hours and one person to perform with the
exception of visual inspection of the field lighting system which may be
more frequent and require two persons to perform.

**Depot level maintenance** will consist of repairing or replacing
failed, repairable LRUs that have been removed in the field. Depot
support will be available for the RWSL processor, cab control panel and
maintenance display LRUs and components. Initial depot maintenance and
inventory support shall be provided by the Contractor, and may migrate
to organic (FAA) depot.

#### Logistics Management Information 

##### LMI Requirements 

The Contractor shall develop and deliver to the Government, in
accordance with MIL-PRF-49506, the data products contained in the
Logistics Management Information (LMI) Data Products Worksheet in the
format attached to DID LM-002. MIL-PRF-49506 describes the information
required by the Government to perform acquisition logistics management
functions. The LMI Data Products Worksheet consists of the data that a
requiring authority needs in order to develop internal materiel
management processes. The data products shall represent the system
design configuration to the component level including systems,
subsystems, components, assemblies, subassemblies, support and test
equipment, and training equipment required for RWSL. Temporary items are
not required. The Contractor shall adhere to the data definitions,
edits, and data formats as described in MIL-PRF-49506, Appendix B, the
attached LMI Data Products worksheet, and the RWSL Data Products Format
attachment to DID LM-002. Modified data product requirements shown on
the LMI Data Products Worksheet and the RWSL Data Products Format shall
take precedence over MIL-PRF-49506. The Contractor shall update the LMI
Data Products based on changes to the LMI.

**CDRL LM02 LMI Data Products**

##### LMI Data Reviews 

The Contractor shall host an LMI Data Review 90 days following the LGC.
Topics shall include the Contractor\'s progress in LMI development and
plans for future efforts. Additional data reviews, not to exceed four
each year, may be held in conjunction with ILSMT meetings and at the
discretion of the APML. An agenda, meeting minutes, presentation
materials shall be provided in accordance with CDRLs PM10 and 11.

##### LMI Acceptance Criteria 

Upon receipt of data submittals, the Government will verify that the
data is documented as specified in 3.6.4.1 and that it meets the data
definition, edit, and data format requirements of MIL-PRF-49506 and the
attached worksheet. Data will not be accepted unless:

-   The submitted data reflects a level of detail to the component level
    as identified in 3.6.4.1.

-   The data is verified to accurately reflect the current design
    configuration.

-   The data conforms with the delivery requirements stated in DID
    LM-002.

-   The required data elements are provided as specified on the attached
    LMI Data Products Worksheet.

#### Supply Support 

##### Site and Depot Spares 

The Contractor shall develop and submit a list of site spares that
consists of LRUs, removable modules, common and bulk items, and any
other parts necessary to perform site maintenance. Upon Government
approval of the site spares list, the Contractor will be required to
deliver the approved range and quantity of site spares to each site. The
Contractor will update site spares list as required.

CDRL LM03 List of Recommended Site Spares

##### Consumables

The Contractor shall identify all site consumables required for
operation and maintenance of the RWSL system. A consumable is any
hardware item that can be removed and replaced to restore the system,
and is a low-cost, non-repairable item (e.g. fuses, light bulbs, knobs,
wire, battery terminal lugs, cleaning fluid) that is uneconomical to
repair.

**CDRL LM04 List of Recommended Consumables**

##### Support and Test Equipment 

The Contractor shall identify all site and depot common, RWSL unique,
and peculiar tools, handling, support and test equipment required to
support FAA planning and training. The Contractor shall also provide
RWSL unique support and test equipment for each system, but shall make
every effort to standardize support and test equipment with current FAA
inventory.

CDRL LM005 Support and Test Equipment List

##### LRU Identification and Marking

The Contractor shall use commercial marking practices for the purposes
of product identification and inventory management to control and
identify RWSL LRUs. The Contractor shall be responsible for marking all
RWSL LRU components including LRU spares. All LRU components and LRU
spares shall be marked with bar code symbology that is consistent with
commercial product identification in accordance with AIM-BC1 Uniform
Symbology Specification Code 39. Bar code markings shall be applied to
each LRU, or where impractical, on the individual LRU packaging. LRU
markings shall be sufficient to clearly and visually identify the LRU
and the contents of an LRU package in accordance with MIL-STD-129P.

**CDRL LM06 LRU Markings Report**

#### Technical Data

The Contractor shall be responsible for obtaining, integrating and
providing the necessary operations and maintenance technical data
required to maintain RWSL. The Contractor shall be responsible for
ensuring that RWSL technical data is updated to reflect
Government-approved engineering changes prior to establishment of the
product baseline.

##### Technical Drawings and Associated Lists 

The Contractor shall develop technical drawings and data for the
implementation and support of the RWSL. The Contractor shall develop an
engineering drawing tree that will identify all items to be delivered as
part of the drawing package.

Modified COTS is to be considered as COTS equipment that has been
modified or altered in any fashion to integrate it into the end product
or system.  In such cases, the Contractor shall provide the
documentation required in paragraph 3.6.6.4 of this SOW, in addition to
the drawing(s) and data reflecting what was modified or altered to the
COTS item.

CDRL TD01 Engineering Drawing Tree

##### Product Drawings 

For developed items, the Contractor shall provide product drawings in
accordance with MIL-PRF-28000B, Initial Graphic Exchange Specification
(IGES) Class 2 & 3 and associated lists shall be in accordance with
MIL-DTL-31000C paragraph 3.6.2.3.

CDRL TD02 Product Drawings

##### COTS Drawings

For all commercial items associated with the RWSL, the Contractor shall
provide all vendor supplied commercial drawings, technical documentation
and source control documents. The Contractor shall not be expected to
provide commercial drawings other than what is normally provided by the
vendor.

CDRL TD03 COTS Drawings

##### COTS Manuals and Documentation 

For all COTS (hardware/software) associated with the RWSL, the
Contractor shall provide all vendor supplied commercial drawings,
technical documentation and source control documents. The Contractor
shall not be expected to provide commercial drawings other than what is
normally provided by the vendor. The Government shall be provided with
reproduction rights on all deliverable COTS documentation. The following
are examples of COTS documents to be provided:

-   Operator/User\'s Manuals

-   Hardware/Repair Manuals

-   Installation Requirements (Space and Power) Manuals

-   Software/Software Development Tool Manuals

-   Diagnostics/Diagnostic Interpretations Manuals

-   Installation/Removal/Maintenance Instruction Manuals

-   Schematics/Wiring Diagrams

-   Parts Lists/Catalog

CDRL TD04 Commercial Off the Shelf (COTS) Manuals

##### COTS Hardware Description Document 

The Contractor shall develop a COTS hardware description document for
use in provisioning and baselining the system. This document shall be
developed to the LRU level and contain sufficient data (such as
input/output specifications, performance specifications, dimensions,
etc.) to provide the Government the information needed to procure the
items from commercial and other sources.

CDRL TD05 COTS Hardware Description

##### Technical Instruction Books 

The Contractor shall prepare and submit for Government approval, a
separate Technical Instruction Book for the RWSL processor, FLS, and any
associated Contractor-furnished peculiar Support/Test Equipment.

Each Technical Instruction Book shall comply with the requirements set
forth in the latest version of FAA-D-2494B.

##### Manuscript Plan

The Contractor shall prepare and submit for Government approval a
Technical Instruction Book Manuscript Plan which describes the
contractor's plan to comply with the requirements of the latest version
of specification FAA-D-2494B. The plan shall include a schedule for
manuscript preparation, review, and validation. The manuscript plan
shall also include a schedule for submittal and Government approval of a
prospectus for the manuscript. A separate manuscript plan shall be
provided for each of the RWSL processor and the FLS Technical
Instruction Books. Each Manuscript Plan shall comply with the
requirements of the latest version of specification FAA‑D‑2494B,
paragraph 3.2.

CDRL TD06 Manuscript Plan

##### Manuscript Prospectus

The Contractor shall prepare and submit for Government approval a
Prospectus for the Technical Instruction Book. The prospectus shall be
in the form of a detailed outline, developed in accordance the content
requirements of the latest version of specification FAA-D-2494B, and
prepared to the level of paragraphing necessary to show the major
physical and functional aspects of planned coverage. Each section and
paragraph title shall be followed by a brief statement outlining the
data to be presented and the planned approach. A listing of
illustrations, charts, tables, and graphs shall be included. Government
approval of the prospectus must be obtained before work on the
manuscript begins. A separate prospectus shall be provided for each of
the RWSL processor and FLS Technical Instruction Books.

CDRL TD07 Manuscript Prospectus

##### Verification and Validation Plan

The Contractor shall prepare and submit for Government approval a
Technical Instruction Book Verification and Validation Plan which
describes the contractor's plan to accomplish the verification and
validation requirements described in section 4 of the latest version of
specification FAA-D-2494B. Reviews other than in‑process may be
performed either on a chapter‑by‑chapter basis during preparation of the
manuscript or upon completion of the manuscript. The plan shall provide
a schedule of reviews indicating completion dates for each of the tasks
listed in paragraphs 4.3, 4.4, and 4.5 of the latest version of
specification FAA-D-2494B. A separate Verification and Validation Plan
shall be provided for each of the RWSL processor and FLS Technical
Instruction Books.

CDRL TD08 Verification and Validation Plan

##### Draft Manuscript

The Contractor shall prepare and submit for Government approval draft
Technical Instruction Book in accordance with the approved manuscript
plan and prospectus. The draft Technical Instruction Books shall comply
with the requirements set forth in paragraph 3.3.1 of FAA-D-2494B. A
draft Technical Instruction Book shall be submitted at each of three
in-process review stages: 30-percent complete; 60-percent complete; and
90-percent complete.

A separate draft shall be provided for each of the RWSL processor and
FLS Technical Instruction Books.

CDRL TD09 Manuscript

##### In-Process Review

In-process reviews for each of the 30%, 60%, and 90% draft Technical
Instruction Book submittals shall be conducted in accordance with
paragraph 3.3.1.1 of FAA-D-2494B. In-process reviews may be conducted at
the contractor's facility or as determined by the Contracting Officer
and shall be accomplished as listed in the manuscript schedule contained
within the approved manuscript plan. The Contractor shall provide
drawings, illustrations and support materials to assist in manuscript
review. Comments from the reviews shall be incorporated into the draft
manuscripts prior to their next submission. The Contractor shall submit
a Comment Resolution Report in accordance with CDRL TD10 for each review
listing of all comments received, indicating those accepted and
incorporated into the revised draft and those not accepted, along with
the reason for rejection. The Contractor shall prepare meeting minutes
and action items resulting from the meetings in accordance with CDRL
PM11.

CDRL TD10 Comment Resolution Report

##### Final Manuscripts for FAA Review 

The Contractor shall prepare and submit for Government approval final
draft Technical Instruction Books. Final draft manuscripts shall be
provided after comments from the 90% in-process review have been
incorporated. The drafts shall be provided for review and approval by
the Government. Government comments shall be incorporated into the
manuscripts. A separate final draft shall be provided for each of the
RWSL processor and the FLS Technical Instruction Books. The Contractor
shall submit a Comment Resolution Report listing in accordance with CDRL
TD10 of all comments received, indicating those accepted and
incorporated into the final manuscript and those not accepted, along
with the reason for rejection.

##### Final Manuscript

Upon Government approval of the draft manuscript, the Contractor shall
prepare and submit for Government approval a final reproducible version
of Technical Instruction Books, with all corrections incorporated, in
accordance with the schedule contained within the approved manuscript
plan. The final Technical Instruction Books shall comply with the
requirements set forth in paragraph 3.3.2 of the latest version of
specification FAA-D-2494B. A separate final version shall be provided
for each of RWSL processor and the FLS Technical Instruction Books.

CDRL TD09 Final Manuscript

##### Support/Test Equipment Manuals 

Separate, stand-alone instruction books shall be provided for the
operation, description, maintenance, and repair of the
Contractor-furnished peculiar support/test equipment. The instruction
books may be in the original equipment manufacturer\'s format.
Electronic media, programs, or documentation required for data analysis
shall be provided with electronic test equipment.

CDRL TD11 Support/Test Equipment Manuals

##### Technical Instruction Books Validation 

The Contractor shall validate each Technical Instruction Book in
accordance with the approved Verification and Validation Plans.
Validation shall be conducted by actual performance of operating and
maintenance procedures unless written authority is obtained from the
Government to use simulation for selected procedures. The Government
reserves the right to witness each procedure validation. Upon completion
of the each Technical Instruction Book validation, the Contractor shall
prepare and submit a

letter to the Contracting Officer indicating successful completion of
validation.

##### Verification

To assure that the contractor has fulfilled all requirements of the
validation process, the government reserves the right to witness any
contractor validation activities. Verification may also include the
actual performance, by government personnel, of any instruction
contained in the Technical Instruction Books. The Contractor shall
provide engineering and technical assistance support during Government
verification of all Technical Instruction Books.

##### Air Traffic Controller Operator\'s Manual 

The Contractor shall prepare and deliver a draft and final Operator\'s
Manual. The draft shall be provided for review and approval by the
Government. The manual shall contain the following information:

-   Description of the uses of the equipment.

-   Indication of the relationship to other program documentation.

-   Description of the function of all operator controls.

-   Description of the use of all peripheral equipment (including
    immediate interface equipment).

-   Description of operating procedures.

Copies of this manual shall be provided for each site.

**CDRL  TD12  Air Traffic Operator's Manual**

##### FAA Installation POC Manual

The Contractor shall develop and deliver a draft and final
reproducible/POC manual, in accordance with FAA-D-2494B for review and
approval by the Government, which will describe how all of the equipment
is integrated into a single operational system. The manual will provide
information regarding installation, integration, test, implementation,
alignment, checkout, and acceptance testing of the RWSL system.

**[CDRL TD13 FAA Installation Point Of Contact Manual]{.mark}**

#### Technical Operations Specialists Training 

##### Implementation

The Contractor shall develop and deliver resident (lecture with lab
exercises) training to provide designated FAA personnel with the
knowledge and skills required to ensure competence in performing their
respective duties as it relates to the RWSL system. The Contractor shall
develop and deliver all training and training materials in accordance
with FAA-STD-028C, Contract Training Programs and Technical Operations
Training, AMA-400 EHOT-DoP Policy and Procedures, as modified by the
Government in this document. The Contractor shall perform the training
tasks outlined in the following subsections and prepare all course
materials in a Government-approved contractor format.

All material developed for the Government by Contractors shall be the
sole property of the Government and shall not be used by the Contractor
for any purpose other than those in the contract unless approved by the
Government.

##### Training Guidance Conference

The Contractor shall participate in a Government sponsored RWSL Training
Guidance Conference (TGC). The purpose of the TGC is to provide the
Contractor with guidance or clarification on training requirements and
plans and associated CDRLs and DIDs. The TGC will be held at a
Government-approved Contractor or Government facility.

During the TGC, the Contractor shall be prepared to discuss their
understanding of the work to be performed, training requirements, and
other related items wherein the Contractor desires Government guidance.
As a minimum, the TGC shall include the following:

1.  Review of contract requirements such as training deliverables,
    personnel, schedules, training locations, and FAA-STD-028C.

2.  Discussion of the Contractor Personnel Qualifications Report.

3.  Discussion of the Contractor's schedule for completing the training
    development process and the requirements associated with each
    deliverable.

4.  Deliverable review and comment process.

5.  Discussion of methods for completing the Task and Skills Analysis
    (TASA). A sample TASA will be provided by the Government.

6.  Discussion of the Training Development Plan (TDP). A sample TDP will
    be provided by the Government.

7.  Permit inspection of the contractor's facility and establish a
    working relationship with contractor personnel.

8.  Discuss classroom administration requirements.

In the event the Government convenes a joint Air Traffic and Tech Ops
guidance conference, separate sessions will be held to discuss specific
Technical Operations and Air Traffic training requirements. In
accordance with CDRL PM10 and 11 the Contractor shall develop the TGC
agenda and prepare and distribute minutes.

##### Training Materials 

The Contractor shall develop training and reference materials to support
delivered training. The Contractor shall provide each student with a
complete a set of course materials for the respective course. Course
conduct shall make maximum use of all materials distributed. Student
manuals and guides will encompass a "how to" approach and work in
concert with the instructor materials (lesson plans, PowerPoint
presentations, figures, handouts, etc.). The Contractor shall furnish
and maintain all reference, instruction and student materials for each
class. The Contractor shall make one set of Technical Instruction Books
available to each student during the training classes.

At the conclusion of each class, students will retain all student course
materials issued to them. The Technical Instruction Books, made
available as reference material, shall be retained in the classroom. The
Contractor shall submit all course materials for review and approval
prior to conducting training classes. Training materials shall
incorporate all Government-approved revisions prior to conducting any
additional reviews and/or classes, and students in follow-on classes
shall be provided clean copies of student materials.

In addition the Contractor shall provide the following:

-   A copy of all student materials used in the course or briefing
    session for each Government instructor participating in designated
    courses or Operational Tryout.

-   Sufficient sets of classroom technical documentation reference
    materials, which shall be retained in or near the classroom as a
    reference library

-   Suggested list and quantities of reference materials needed for each
    course.

All training materials shall comply with RWSL Technical Instruction
Books.

##### Environmental Occupational Safety and Health

All training developed or revised by a Contractor must meet or exceed
the appropriate Occupational Safety and Health Administration (OSHA)
regulations in accordance with OSHA 29 CFR1910. OSHA safety regulations
are to be integrated into course content, as appropriate.

The Contractor must emphasize, in its developed instructional program,
each person's individual accident prevention responsibilities as well as
their responsibilities as representatives of the Government. Safety
precautions related to training on the operations, maintenance, and/or
troubleshooting of equipment must be a prominent part of the training.

##### Contractor Furnished Training Equipment

The Contractor shall furnish all training equipment, safety equipment,
including personal protective and material handling equipment, special
tools, etc., necessary to conduct training. Any equipment/system
furnished for training development and/or conduct shall include all
software, special tools, test equipment, simulators, emulators, and
support equipment required to provide the end product or service.

The Contractor shall maintain all equipment in an operable and usable
condition except for planned disassembly and fault isolation training
exercises. The Contractor shall notify the Government immediately by
telephone if training equipment becomes inoperable and/or unusable.
Pre-faulted LRUs and components (printed circuit boards, power supplies,
cables, etc.) shall be included as training equipment. If Contractor
furnished training equipment is to be returned to stock for subsequent
delivery to the Government, the Contractor shall keep configuration
management records on the equipment in accordance with FAA-STD-028C. Any
training aids, demonstration items, charts, mock-ups, etc., used in
training shall be provided to the Government at the conclusion of
Contractor training.

##### Contractor Furnished Training Site(s) and Facilities

The Government shall approve in advance all training sites. The
Contractor's facility shall be the preferred training site for all
training, and unless otherwise provided for in this contract, all
training shall be conducted at the Contractor's facility. The Government
may inspect any training sites and/or facilities furnished by the
Contractor during the contract period. The following conditions will be
appraised and must be approved: space, lighting, noise, heating and
cooling, safety of environment, cleanliness and sanitation, and
furniture. The contractor shall correct any known deficiencies
identified before the start of training.

The contractor shall provide training aids such as chalkboards, overhead
projectors, viewgraphs, etc., as identified in training documentation.

[]{.mark}

##### Government Furnished Training Equipment and Materials

If training is conducted at an FAA field site, the Government shall make
all system or other equipment to be used in training available to the
Contractor. The Government shall maintain Government-furnished training
equipment in an operable and usable condition except for planned
disassembly and fault isolation training exercises. Practical
application activities requiring use of the system or equipment shall be
coordinated with the FAA training representative onsite, at least 24
hours prior to need. The Contractor is not responsible for damages
sustained by Government-furnished training equipment except if caused as
a result of Contractor negligence.

##### Training Requirements

##### Hardware Maintenance Training

The Contractor shall develop and conduct this course in such a manner
that Technical Operations personnel completing this training shall be
equipped with the knowledge necessary to provide onsite RWSL system
maintenance. Course content will include, but not be limited to, the
following:

-   System overview.

```{=html}
<!-- -->
```
-   Theory, or concept, of operation.

-   Maintenance concepts and responsibilities.

-   System block and LRU diagrams.

-   In-depth parameters.

-   System and subsystem interfaces.

-   Operational, functional, and adjustment checks in accordance with
    the manufacturer's instructions or applicable FAA orders.

-   Routine periodic and preventive maintenance using the checks and
    procedures established for the RWSL system in accordance with FAA
    orders.

-   Fault isolation and diagnostics procedures for failures to the LRU
    level and restore the equipment to operational service through
    removal and replacement of the faulty LRU.

-   Required adjustments to restore the system to operational service
    following removal and replacement of the faulted LRU.

-   Configuration, restoration, and verification in accordance with RWSL
    technical instruction manuals and certification of service in
    accordance with FAA orders.

-   Software upgrades on remote site hardware.

-   Safety.

-   Use of RWSL system software for maintenance, restoration in
    accordance with RWSL technical instruction manuals and certification
    of service in accordance with FAA orders.

##### General Course Requirements

The Contractor shall provide RWSL system maintenance training via
lecture and laboratory. The lecture and laboratory training shall be
conducted at the Contractor's facility or a designated FAA site and
shall meet the following requirements:

-   Submittal of a course outline and formats for training materials to
    the Government for approval prior to use. Student manuals and lab
    manuals shall be developed using Content Design format. FAA shall
    provide the template to the contractor.

-   Thoroughly tested course objectives in written and/or graded lab
    practical examinations.

```{=html}
<!-- -->
```
-   Training:

    -   Shall be based on a Task and Skills Analysis (TASA) with
        cognitive and performance objectives directly derived from the
        TASA.

    -   Training course materials shall be based on the system/equipment
        Technical Instruction Book(s). Course materials shall include an
        instructor manual and an instructor laboratory guide with
        detailed lesson plans for consistent training, a student manual
        and a laboratory manual with performance exercises to enable
        students to practice the skills being taught.

    -   Instruction shall be comprised of 50 percent lecture and 50
        percent lab exercises.

    -   Upon training completion, each student shall be able to perform
        all preventive maintenance, as well as identify, isolate, and
        correct faults to the LRU level (corrective maintenance).
        Students shall understand the functional capabilities and
        operational concepts of the equipment/system.

```{=html}
<!-- -->
```
-   Written exams:

    -   Shall be multiple-choice items. The number of test items shall
        be sufficient to adequately measure student mastery of all the
        objectives.

    -   Each objective shall have three different versions of each exam
        item of equal difficulty.

    -   Exams shall be such that a student achieving a 70 percent score
        possesses the requisite knowledge of the equipment/system.

-   All students shall be given the opportunity to complete written
    evaluations during, or at the end of, the conduct of training.

##### Training Development

The Contractor shall develop and conduct this training in accordance
with FAA-STD-028C, Contractor Training Programs, and Programs and
Technical Operations Training, AMA-400 EHOT-DoP Policy and Procedures.

The Contractor shall revise and maintain all course materials,
curriculum materials and courseware until all contractor-conducted
training has been completed. The Contractor shall deliver final training
documents and materials in hard copy form and on electronic media files
in the latest version of Microsoft Office 2003.

##### Personnel Qualifications Report

The Contractor shall submit a resume of training experience for each
person assigned to develop courseware and/or conduct classes under this
contract. Each resume must include the name of organizations where the
person developed and/or conducted training, points of contact, including
phone numbers, and training dates.

The Contractor shall submit a Personnel Qualifications Report for the
training staff in accordance with DID TP-001 prior to the TGC.

**CDRL TP01 Personnel Qualifications Report**

##### Task and Skills Analysis 

The Contractor shall prepare and submit a Task and Skills Analysis
(TASA) Report in accordance with DID TP-002. The TASA Report must
identify the impact the introduction of the RWSL system equipment and
technology shall have on the current work force and identify the skills
required to monitor, control or maintain the system.

**CDRL TP02 Task and Skills Analysis Report**

##### Training/Course Schedule

The training shall be conducted on an eight-hour academic day, five
business days per week schedule. Course instruction, labs, and testing
shall be included in this time frame. Class instruction periods for
lecture will be 50 minutes in duration with a 10-minute break between
periods of instruction. The length of the practical application
(laboratory exercises) shall vary as the subject matter dictates.

Start and end times for classes conducted at FAA field locations may
vary to accommodate work schedules for FAA personnel.

Class shall not be held on Federal holidays. Federal holidays shall not
be absorbed into the overall course length. The Government shall
establish class start and stop times and class days.

Maximum class size is 8 students of FAA technicians, engineers and/or
supervisors, per class. The student-to-instructor ratio may be no
greater than 8-to-1 for classroom training, and no greater than 4-to-1
for lab training. The number of RWSL systems available for lab exercises
will determine the final class size.

The Contractor shall conduct a minimum of 2 classes with additional
classes purchased as needed upon successful completion of the
Operational Tryout and the First Course Conduct.

The Contractor shall develop course schedule(s) to be included with the
student training materials. The schedule(s) shall provide an overview of
the course chronology and shall show the major segments of the course
and their time allotments. The schedule shall be updated throughout the
development process as needed.

Government representatives, may at any time, monitor contractor
conducted training purchased for this program.

##### COTS Training Materials

COTS training materials may be used for part or all of the training;
however, the Contractor must follow the same planning and validation
steps as for any other training developed for the Government. COTS
training materials are defined as existing training regularly offered to
the general public and/or Government personnel in the course of normal
business operations; they are not "on-the-shelf technical documents."

For COTS training materials, the Contractor shall submit a COTS Training
Materials Report in accordance with DID TP-004. The report must include
an assessment of the suitability of the proposed COTS materials against
the training requirements identified in the TASA Report. When COTS
materials are proposed for use for FAA training, the contractor shall
follow the same planning and validation steps as any other training
developed for the FAA and shall match requirements as identified in the
TASA.

The proposed COTS training materials must be submitted along with the
report. If the contents do not match the TASA Report, or are
unavailable, unacceptable, or do not fully meet the requirements as
identified in General Course Requirements of this SOW, the contractor
shall develop and submit training to cover the portion of the required
training that is not in the COTS materials.

**CDRL TP03 COTS Training Materials Report**

##### Development of Training Materials

The Contractor shall develop the following documents for this training:

**CDRL TP04 Training Development Plan**

**CDRL TP05 Course Design Guide**

**CDRL TP06 Test**

**CDRL TP07 Classroom Training Materials**

##### Student Welcome Packages

All students attending contractor conducted training shall receive prior
notification of the content and methods to be used in the training. This
notification shall be provided to the Government, in electronic format,
in the form of a Welcome Package and shall include a description of the
course contents, directions to the Contractor's facility, class dates
and times, and restaurants for the local area.

**CDRL TP08 Student Welcome Packages**

##### Validation of Training Courses 

##### Contractor's Presentation

The Contractor's Presentation is a formal step in the validation of the
training materials in accordance with DID TP-009. During the
presentation, the Contractor shall present a shortened version of each
fully developed draft lesson, including draft test items. Each lesson
shall be given in enough detail and depth that the integration and
effectiveness of the instructional materials, learning sequence,
performance exercise, tests, and the time allocations, can be fully
assessed by the Government.

The Contractor's Presentation shall be conducted at the Contractor's
facility using materials that will be used in the actual training
course. Contractor personnel responsible for the design, development,
and technical accuracy of the training materials shall be available
during the presentation to answer questions about the course.
Additionally, if the Government requests their presence, the Contractor
shall require additional Contractor personnel to include instructor(s),
developer(s), and appropriate subject matter experts, available to
answer questions during and after the presentation. Government
representatives shall be as identified by the Government.

The Contractor shall correct errors, omissions and deficiencies in
student and instructor materials discovered during the Contractor's
Presentation and shall submit corrected copies of the course materials
for Government review and approval. The Contractor shall also ensure
that all copies requiring correction are corrected prior to their use in
any class.

**CDRL TP09 Contractor's Presentation**

##### Operational Tryout 

The Operational Tryout is a continuation of the training materials
validation process conducted in accordance with CDRL TP10. Completed
draft lessons are presented to representatives of the target population
to determine if the instructional approach is appropriate and effective,
test items and time allocations are appropriate, and the format of the
materials is easy to use. Information obtained from the Operational
Tryout is used to revise and improve the instructional effectiveness of
the materials prior to the First Course Conduct.

The Operational Tryout shall be conducted at the Contractor's facility
and must be planned to last one and a half times the length of the
proposed course. Government representatives selected as monitors shall
not count against the class enrollment. The Contractor shall correct
errors, omissions and deficiencies discovered during the Operational
Tryout and resubmit materials as directed by the contract. Subsequent
classes shall not commence until a successful Operational Tryout has
been conducted and is approved by the Government.

The contractor shall submit an Operational Tryout Report upon completion
of the Operational Tryout. The Operational Tryout class shall not count
against the number of classes to be conducted by the Contractor.

**CDRL TP10 Operational Tryout Report**

##### First Course Conduct 

The Contractor shall provide the First Course Conduct in its entirety in
the intended training environment to the target population to ensure the
course accomplishes the objectives established in accordance with DID
TP11. The Contractor shall submit a First Course Conduct Report upon
completion of the First Course Conduct class.

Course acceptance shall be contingent upon Government approval of the
First Course Conduct Report. The First Course Conduct class(es) shall
not count against the number of classes to be conducted by the
Contractor.

**CDRL TP11 First Course Conduct Report**

##### Course Evaluations

All students shall be given the opportunity to complete written
evaluations during, or at the end of, the conduct of training. The
Government shall provide the evaluation forms to the Contractor for
distribution to the students. These forms may include, but not be
limited to, student lesson critiques, time logs, errata sheets, and
end-of-course critiques.

During the Operational Tryout and First Course Conduct, the Government
shall review the forms and identify necessary changes to training
materials. The Contractor shall incorporate the revisions. At subsequent
course conducts, the Contractor shall administer the designated
evaluation forms and forward them to the Government designee.

##### Certificate of Training

The Contractor shall deliver a certificate of training to each student
who successfully completes the training. The certificate shall contain,
as a minimum:

-   Student name

-   Length of training, in hours

-   Course number and title

-   Location of training

-   Date completed

-   Issuing official

#### Air Traffic Training

The Contractor will be responsible for the required Air Traffic training
elements identified in this section.

##### Air Traffic Scenarios

The Contractor shall provide PC-based, animated scenarios of RWSL in
operation on the runway and taxiway.  The scenarios shall demonstrate
the timing of illuminating and extinguishing of both REL and THL light
arrays to show the air traffic controller how the system operates on the
airport.  The scenarios shall be operable within a Windows PowerPoint
environment. The Contractor shall provide a CD-ROM with executable and
support files in accordance with CDRL TP12.

**CDRL  TP12  CD-ROM with Executable and Support Files**

##### RWSL Cab Control Panel Trainer

The Contractor shall provide a PC-based software program that will
simulate all air traffic functions and displays of the cab control
panel, which controls brightness and the on/off function.  The program
shall be operated on a laptop computer with touch-screen capability to
accept controller input and then reflect the status of the input. The
Contractor shall provide a CD-ROM with executable and support files in
accordance with CDRL TP12.

##### Installation Point of Contact Training 

This course shall support installation point of contacts by providing a
high level familiarization and general overview of the RWSL system.
Training materials shall be prepared in accordance with TP07, Classroom
Training Materials. The Contractor shall (1) Apply best commercial
practices, (2) Provide modular training, ensuring that each module shall
address a single major topic or several closely related topics, and (3)
Develop instructional media materials in support of training

For COTS training materials proposed and approved by the Government, the
Contractor will conduct one with the option for two additional courses.

#### Second Level Engineering Training

The Contractor shall provide second level engineering training services
including training equipment (e.g., tools, test and support equipment)
to the Program Support Facility (PSF) at the Mike Monroney Aeronautical
Center in Oklahoma City, Oklahoma. The system or equipment shall
duplicate to the maximum extent possible the actual operating
environment.

This course shall support the PSF, NAS Engineering, ATO-W, by providing
advanced user training and software instruction necessary to maintain
the RWSL system. Training materials shall use best commercial practices.
Training content shall ensure that NAS Engineering personnel achieve a
level of competency needed to perform their respective duties.

Training shall be modular in nature. Each module shall address a single
major topic, or several closely related topics, as contained in the
training outcomes, which provide a logical training sequence. The
Contractor shall correct any errors, omissions, and deficiencies in the
revised course materials, which were discovered during the Government
review prior to training. Classroom instruction shall be supported by
lab exercises.

A Government furnished End-of-Course Evaluation Questionnaire will be
submitted to students at the conclusion of training. Completed
questionnaires shall be submitted to ATO-W.

The Government will maintain all training equipment in operable and
usable condition during the training course except for planned
disassembly and fault isolation training exercises. The Contractor shall
notify the Government immediately if training equipment is inoperable
and/or unusable. If Contractor furnished training equipment is to be
returned to stock for subsequent delivery to the Government, the
Contractor shall keep configuration management records on the equipment
in accordance with ISO 10007:2003. Any training aids, demonstration
items, charts, and mock-ups used in training shall be provided to the
Government at the conclusion of Contractor training.

The Contractor shall provide Course Materials in accordance with DID
TP-007.

##### Technical Interchange Meetings 

TIMs may be held to discuss in detail any training issues that require
mutual resolution or further clarification. The Contractor shall attend
and provide expertise to the Government, as well as access to the
vendor's system and expertise. Refer to 3.1.7.4 for TIMs.

#### Contractor Support and Services

The Contractor shall provide support and services in accordance with the
provisions in this SOW for complete supply support which includes
stocking, storing, issuing, receipting of LRUs and the repair of
returned LRUs from the field, and stocking, storing and issuing site
level consumables.

The Contractor shall provide site, depot and second level engineering
support services as described in this SOW.

##### Definitions

The following definitions are applicable and are included for
information only:

a.  [Exchange and Repair Item]{.underline}. Any hardware LRU, except
    expendable, when unserviceable, is returned to the Contractor after
    a serviceable replacement. The designation of an item of supply as
    Exchange and Repair (E&R) indicates the logistic status assigned for
    inventory management purposes rather than the physical condition of
    an item. A serviceable item is sent from the Contractor to a
    Government facility upon request by the FAALC inventory manager and
    an unserviceable item is returned to the repair facility
    (Contractor) in exchange for the serviceable item, unless otherwise
    authorized. In most cases these items will consist of critical
    supply LRUs (i.e., high value and/or special manufacture).

b.  [Expendable Item]{.underline}. Any hardware LRU, except E&R, that
    can be removed and replaced to restore the system. An expendable LRU
    possesses characteristics, qualities, and low cost that make it
    uneconomical to restore the defective LRU.

c.  [Line Replaceable Unit]{.underline}. An LRU is defined as an item
    that may consist of a unit, an assembly (circuit card assembly,
    electronic component assembly, etc.), a subassembly, or a part, that
    is removed and replaced at the site maintenance level to restore the
    system/equipment to its operational status. An LRU can be either an
    E&R item or an expendable item.

d.  [Piece Part]{.underline}. The lowest replaceable item of an assembly
    or SRU removed or replaced at an intermediate or depot maintenance
    level.

e.  [Repairable]{.underline}. The condition of an item that can be
    returned to service after repair or rework in accordance with
    procedures, tolerances, and limits established by the overhaul and
    repair instructions issued by the item manufacturer, or as otherwise
    authorized under the provisions of the Government regulations.

f.  [Serviceable]{.underline}. The condition of an item in a good state
    of preservation that can be placed in service in accordance with
    applicable manufacturers overhaul limits and instructions and/or
    pertinent regulations of the Government without repair.

g.  [Shop Replaceable Unit]{.underline}. An SRU is defined as an item
    that may consist of a unit, assemblies, and piece parts.  An LRU may
    consist of one or several SRUs.

h.  [Test]{.underline}. A test or check of equipment in its operational
    (or functional) environment, using equipment, procedures, and limits
    specified in applicable authorized manufacturer publications,
    manuals, and specifications and technical orders or Government
    authorized changes in procedures and limits.

##### Key Site Support

The Contractor shall provide full maintenance support at the RWSL key
site. This support shall include site level maintenance, depot repairs,
and second level engineering support. On-site maintenance will be under
a separate delivery order of this contract. The Contractor shall provide
inclusive maintenance support prior to initial operating capability,
with the exception of the key site as well as maintenance support
through commissioning of the key site.

##### Second Level Engineering Support

The Contractor shall provide on-call maintenance support to the
Government. On-call hardware support shall consist of providing
assistance in resolving problems or providing additional expertise
should unexpected problems develop. Software on-call maintenance shall
be directed toward resolution of software problems until the
establishment and operations of the PSF. It is anticipated that after
the establishment of the product baseline, the accumulation and the
simultaneous implementation of routine software changes will be
minimized with a corresponding limit of interim software versions and
related documentation changes. The Contractor shall be responsible for
maintaining the production RWSL software, investigating software
problems, and incorporating approved software changes until such time as
control of changes is passed to the PSF. The Contractor shall provide
the necessary materials required for this effort. This shall include all
software and procedural documentation required for the development,
generation, modification, CM, maintenance, testing, analysis, and
debugging of all RWSL software, as specified in the contract.

Second level engineering support services shall include:

-   Services for the restoration, integration, optimization, and
    maintenance of the system

-   Site restoration assistance to field personnel.

-   Development, prototype and production assistance, testing, and
    introduction of engineering solutions in response to problem reports
    and approved case files.

-   Configuration and documentation maintenance, release, and control.

-   Assuring the supportability of system software releases before they
    are deployed into the NAS.

The hardware and software engineering support service shall be available
during normal business hours, 40 hours per week. The Government may
require support services outside normal business hours during the week
and including weekends. Criticality of the RWSL system is essential. The
Contractor shall certify that all Contractor personnel are fully trained
and qualified to provide the above engineering support services.
Training for all engineering support services shall be the
responsibility of the Contractor.

#### Interim Contractor Depot Logistics Support Requirements 

The following requirements apply to Interim Contractor Depot Logistics
Support (ICDLS):

a.  The Contractor shall provide ICDLS for the RWSL systems throughout
    the duration of this contract. This shall include stocking, storing,
    issuing, and shipping expendable, consumable and repairable items.

b.  Those items covered by warranty shall be replaced at no cost to the
    Government.

c.  The Contractor shall repair, as required, all repairable Exchange
    and Repair (E&R) LRUs returned from FAA field sites. This repair
    cost shall not exceed 65% of the cost of a new item, unless approved
    by the contracting officer.

d.  The Contractor shall furnish all labor, tools, test equipment,
    parts, software, and any other technical or administrative support
    necessary to provide the required ICDLS.

e.  The Contractor shall be required to provide depot level support 7
    days a week, 24 hours a day, to meet a priority one request from the
    field. The government will designate the priority as follows:

    1.  Priority 1 is used when either the prime or standby equipment is
        inoperative or when a facility is operating at a reduced
        performance that adversely affects ATC operations. Shipment to
        the designated facility is to be within 24 hours, including
        weekends and holidays, after notification by the Government's
        authorized representative.

    2.  Priority 2 is used when a facility is operating with substandard
        equipment or operating conditions indicate imminent facility
        failures or outage. Shipment to the designated facility is to be
        received within 48 hours after receipt of notification by the
        Government's authorized representative.

    3.  Priority 5 is used with a routine requirement or stock
        replenishment. Shipment to the designated facility is to be
        received within eight days after receipt of notification by the
        Government's authorized representative.

##### E&R LRU Repair Procedure 

The following requirements apply to E&R LRU Repair Procedures:

-   E&R items shall be repaired to the extent necessary to restore them
    to a condition in which the items are capable of meeting all
    operational and functional requirements for which they were
    designed.

-   Any modification to items required by the contract and not
    previously accomplished shall be made by the Contractor at the time
    of repair.

-   All property removed during repair shall become the property of the
    government. Disposition of removed parts shall be at the direction
    of the Contracting Officer. Unusable parts are those items that
    cannot be placed in service without the item itself being repaired.

##### Depot and Lay-in Spares 

The Contractor shall lay-in and maintain a quantity of spares to support
the availability rate defined in the RWSL System Specification
FAA-E-3001. Initial lay‑in will be funded by the Government and will be
controlled as GFP/GFE. Replenishment of piece parts will follow
established/approved policy as funded and authorized by the contracting
officer. The Contractor shall maintain an inventory listing of these
repair items to include:

-   Part number and manufacturer\'s cage code

-   Nomenclature or description

-   Quantity

-   Unit of issue or Unit Ordering Quantity (UOQ)

-   National Stock Number

##### Contract Repair Service Status Reporting 

The Contractor shall provide a monthly repair service status report.
These status reports shall contain the following information on failed
LRUs:

-   Part number

-   Serial number

-   Description

-   Site

-   Date of request for repair

-   Date of shipment from site to repair facility

-   Date of repair

-   Date of shipment

-   Contractor\'s shipping number

-   Failure analysis

Failed components replaced in the repair process, shall be identified by
part number, quantity, probable cause of failure (including
identification of failures that cannot be duplicated), and be tracked
back to the failed LRU. The monthly failure report shall also include
cumulative failure information for each contract year, mathematical
calculations of observed availability by LRU type, and statistical data
that show repair trends, common failures, and site comparisons.

CDRL RP02 Contractor Repair Service Status Reports

##### Obsolete Parts Program

To properly advise the Government of the status of parts used in the
production systems, the Contractor shall implement an obsolete parts
program. This program shall include the maintenance and update of a
parts database, similar to a SMART database, of microcircuits and
semiconductor devices and a forecast of their lifecycle. The results of
this assessment shall be reported at PMRs.

Obsolete parts replacement shall be in accordance with Section H.26. All
documentation acquired with the purchase of the obsolete replacement
parts, including, but not limited to data, drawings and test results,
shall be furnished to the Government as change pages to existing
Technical Instruction Books.

#### Post-Commissioning Technical Site Support 

The FAA will be responsible for site-level maintenance for each site
after it reaches commissioning. When notified by the Government, the
Contractor shall provide assistance to resolve any RWSL site maintenance
or logistics problem. These services may vary from phone consultation to
Contractor on-site activities. If a Contractor on-site presence is
required, the Contractor shall arrive at the site no later than 24 hours
after notification that Contractor on-site assistance is necessary. The
Contractor shall provide the number of skilled personnel, support
equipment, and RWSL LRUs/components necessary to return the RWSL to its
operational performance level as specified in the RWSL specifications.

##### Contractor Transition Plan 

The Contractor shall prepare for Government review and approval a
Contractor Transition Plan (CTP). The CTP establishes the procedures and
means for the orderly transfer of the system support and maintenance
management activities from the Contractor to the FAA. The CTP shall
detail the activities that the Contractor shall undertake to ensure a
smooth transition from Contractor to Government operations, and the
preparations, facilities, and personnel that the Government will require
to assume responsibility for the conduct of all or some maintenance and
logistics services provided by the Contractor. The CTP shall include an
itemized list of Government-owned hardware/software used during
development that will be transferred to the FAA.

CDRL LM07 Contractor Transition Plan

#### System Support Equipment/Facilities Services 

##### Special Test Equipment 

The Contractor shall provide special test equipment and items required
for operation, use and maintenance including cables, and operation,
maintenance and vendor data manuals. Documentation shall be delivered
concurrently with special test equipment. Electronic media, programs, or
documentation required for data analysis shall be provided with
electronic test equipment.

##### Program Support Facility 

The Contractor shall plan, install and establish an RWSL PSF at the Mike
Monroney Aeronautical Center, Oklahoma City. The physical facility will
be provided by the Government. The PSF shall include those portions of
the RWSL system, equipment, supporting software, firmware, and
documentation (including revisions and upgrades) required for the
generation, maintenance, testing, analysis, and debugging of all the
functional software in accordance with the RWSL System Specification and
FLS Specification. Operation, maintenance and vendor data manuals for
PSF equipment shall be provided in accordance with FAA-D-2494B
concurrent with the PSF delivery. The PSF shall execute the RWSL
operational software, hardware, firmware and documentation to validate
programs (and associated tests) for test and debugging purposes. The PSF
shall provide the capability to modify the resulting changes. Non-COTS
software shall include Contractor-developed software and any implemented
GFP software. PSF personnel will be provided the training to read,
manipulate, evaluate, and display field-recorded time series and data.
The Contractor shall ensure that all appropriate Computer Aided System
Engineering (CASE) tools are in place and operational at the PSF, prior
to transition of the Software Maintenance effort from the Contractor to
the PSF. The PSF shall be established after a successful PCA/FCA and
prior to CAI.

##### Software Transition Plan 

The Contractor shall plan for transition of life-cycle support of the
RWSL software to the Government using FAA-STD-026 as guidance. The
Contractor shall identify the hardware, software, and other resources
needed for life cycle support of deliverable software and describe the
Contractor\'s plan for transitioning deliverable items to the
Government. Resources shall include the programming environment,
peripherals, memory, compilers, assemblers, and linkers for all non-COTS
software. The Contractor shall use existing documentation when it is
available and meets the data content intent of FAA-STD-026.

CDRL SW07 Software Transition Plan

##### Second Level Engineering Tools and Equipment

The Contractor shall provide the second level engineering tools
identified by the Contractor such as system performance tools and site
adaptation generation tools.

#######  {#section-1 .unnumbered}

##### Software Tools and Source Code

The Contractor shall provide two licensed copies of all software
development tools identified in the Software User Manual that were not
delivered in CLIN 001, or that have changed since CLIN 001 delivery.

The Contractor shall provide source code, as updated, to include changes
described in Section 3.3.1.9, for all non-proprietary,
Contractor-generated RWSL operational, support, including developmental,
tools, second level engineering tools, simulation computer, and test
support software including source code listings. Source code and source
code listings shall be provided as part of the Software Product
Specification, CDRL SW06. The Contractor shall also provide all software
programs used to develop required test data, technical design data, or
documentation data. Software development files shall be included. In
addition, the Contractor shall provide all software programs necessary
to load, analyze, modify, reassemble, and reproduce the system\'s
executable software and/or firmware. The Contractor shall provide above
software programs as part of the SDD.

The Contractor shall identify the specific software components that are
proprietary. All proprietary software used during the linking process
shall be included in executable form. Software development tools used
such as compilers, linkers, and libraries shall be included.
Instructions for building the RWSL, second level engineering tools, and
simulation computer software using the source code, software development
tools, and proprietary executables mentioned above shall be included.

Flow charts and fully documented source code listings and object code
for all Contractor-developed software and firmware shall be provided on
CD-ROM in accordance with CDRL SW06.

##### Computer Programmer's Manual

The Contractor shall develop a Computer Programmer's Manual (CPM) that
will provide maintenance programmer personnel with information necessary
to effectively maintain each Computer Program Configuration Item (CPCI)
of the RWSL. The CPM shall include development tool installation and
setup, CPCI build procedures, and firmware programming/CPCI installation
instructions. The CPM shall identify the software programming
environment, peripherals, memory, compilers, assemblers, and linkers.
All software development tools including hardware and software shall be
identified. The CPM shall satisfy the task oriented instruction mode
requirements of FAA-STD-026A. The Contractor shall validate the CPM.

**CDRL SW08 Computer Programmer's Manual**

#### Contractor Support Services 

This section further defines the scope of the time and materials
provisions in Section H of this Contract. The Government will use
Contractor Support Services for second-level support of the RWSL system,
excluding Contractor depot level maintenance.

At the request of the Government, the Contractor shall provide support
at Government sites, the Contractor\'s plant, or elsewhere, in specific
areas including, but not limited to:

-   Telecommunications network applications, planning, design,
    engineering, hardware, installation, and operation;

-   RWSL problem investigation (e.g., communications, hardware,
    software, firmware);

-   Planning, implementation, maintenance, and/or update of RWSL system;

-   Non-envisioned or catastrophic repair of RWSL equipment;

-   Field Modifications or retrofit activities;

-   Porting of Geographic Situation Display and Ribbon Display Terminal
    functionality to different COTS hardware platforms;

-   Graphical User Interface modifications;

-   Development of a remote RWSL Maintenance Data Terminal;

-   Additional interface development and modifications;

-   Additional hardware, as required, needed to support the RWSL
    program;

-   Software development;

-   Review of RWSL operational modes and procedures; and,

-   On-site maintenance.

The Contractor shall provide qualified engineering and technical
personnel for these services as necessary to complete assigned tasks.
These services shall be provided on a time and material basis with the
Contractor indicating any incidental hardware required to perform
services not otherwise covered in the RWSL contract.

Tasks shall be preceded by an estimate of the time, material, and
corresponding cost from the Contractor at the request of the Government.
Tasks shall begin after written Government authorization has been
received.

## Full Production and Deployment Requirements 

The Contractor shall produce, update, test, deliver, install, and
optionally support the Full Production RWSL in accordance with the
specifications, associated interface documentation, and the requirements
cited in this SOW. This includes production of hardware, software
adaptation for each site, integration of software on hardware platforms,
delivery of the system to the designated site, construction,
installation and checkout of the full RWSL system, test and evaluation
(SAT) and Government acceptance.

In addition, the Contractor shall also provide continued program
management functions (configuration management, data management, quality
management, security, risk management, EVMS, IMS, PMRs and PSRs); depot
logistics support, maintenance, second level maintenance, and residual
training; and set up of the Government depot and program support
facility in accordance with the approved Interim Contractor Depot Level
Support (ICDLS) Transition Plan (ICDLSTP); and set up of the RWSL
training system at the FAA Academy.

### Depot Setup

The Contractor shall furnish all labor, tools, test equipment, hot test
bench, parts, software, documentation, training and any other technical
or administrative support necessary to transition the required depot
level logistics support to the FAALC. The physical facility will be
provided by the Government. The depot system shall include those
portions of the RWSL system required for the performance of depot level
repair activities. Depot training course materials shall be developed in
accordance with CDRL and DID TP07.

### Interim Contractor Depot Level Support Transition Plan (ICDLSTP)

The Contractor shall prepare and provide to the Contracting Officer an
ICDLSTP. The ICDLSTP shall detail the activities required to ensure a
smooth transfer of the RWSL ICDLS operation from the Contractor to the
FAALC. These activities shall include the preparations, facilities, and
personnel that the FAALC will require to assume responsibility for the
conduct of the RWSL repair services. The ICDLSTP shall recommend the
time required to ensure a smooth transition with minimal interruption to
repair activities. The ICDLSTP shall be in the Contractor\'s format and
shall include, but not be limited to, recommendations for the following
items:

-   Formal/on-the-job training/familiarization required to support the
    repair functions.

-   Duration and type of Contractor support required, if any, at the
    FAALC facilities during the transfer or FAALC repair startup.

-   Disposition of lay-in stock, to include all accounting records.

-   Operating methods to be employed to assure repair service during the
    transition period.

-   Method or procedures of transitioning management of the vendor/OEM
    repair contracts to the FAA.

-   Approximate cost of managing vendor repair subcontracts for the life
    cycle of the system.

-   Preservation, packing, packaging and marking of any items shipped to
    FAALC in accordance with MIL-STD-129P (Marking for Shipment and
    Storage); and AIM-BC1 Uniform Symbology Specification Code 39.

-   Recommendations for additional equipment, processes, and
    documentation which would be beneficial to the FAALC operation of
    the transitioned Contractor Repair Service.

#### Tools and Test Equipment List

A list of recommended support items is required. These are items that
are not an integral part of the end item but are required to inspect,
test, calibrate, service, repair or overhaul the RWSL system and any of
its components. The Contractor shall provide the Tools and Test
Equipment List in accordance with DID LM-008.

**CDRL LM08 Tools and Test Equipment List**

#### Depot Test Equipment Manuals

For each unit of test equipment, a maintenance manual is required. The
manual should contain, at a minimum, procedures and guidelines for the
maintenance of software, interface devices/fixtures and documentation
included in each automated test equipment (ATE) test program set.
Instructions shall contain procedures and guidelines for the maintenance
and/or modification of any in-circuit board test program and component
models, including source code written for custom test and test not
included in the standard board test libraries. The manuals shall be
provided in accordance with DID LM-009.

**CDRL LM09 Depot Test Equipment Manuals**

#### Depot Test Procedures

Procedures are required for the operation, maintenance and overhaul of
the RWSL system. Use of existing repair manuals and documentation is
encouraged to the maximum extent possible. The Contractor shall provide
Depot Test Procedures in accordance with DID LM-010.

**CDRL LM10 Depot Test Procedures**

#### Depot Repair/Support Training

The Contractor shall develop a component-level training program on Shop
Replaceable Units (SRUs) and LRUs that make up the system, which
includes training to the FAA Logistics Center at Oklahoma City,
Oklahoma. The training shall include the following:

-   Repair procedures and depot-level specifications.

-   Use of special tools and test equipment, operational system
    troubleshooting and repair techniques.

-   Operation and maintenance of peculiar test equipment.

-   New or modified automated test equipment (ATE).

-   RWSL-unique commercial test equipment, diagnostic test-beds and
    software operations in support of the repair and maintenance of the
    SRUs and LRUs.

The ATE training shall be a separate training module. The students for
the ATE training may not necessarily be the same students as for the
component-level training.

[]{.mark}

The FAA Logistics Center (FAALC) will maintain all training equipment in
operable and usable condition during the training course except for
planned disassembly and fault isolation training exercises. The
Contractor shall notify FAALC immediately if training equipment is
inoperable and/or unusable. If Contractor furnished training equipment
is to be returned to stock for subsequent delivery to the Government,
the Contractor shall keep configuration management records on the
equipment in accordance with FAA-STD-021, paragraph 4.9. Any training
aids, demonstration items, charts, mock-ups, etc., used in training
shall be provided to the Government at the conclusion of Contractor
training.

### FAA Academy Training Support System

The Contractor shall deliver and install an RWSL system at the FAA
Academy in Oklahoma City. The physical facility will be provided by the
Government. The training support system will include those portions of
the RWSL system required to conduct the site level hardware training
course.

## Acronyms 

AC Advisory Circular

ACC Airport Construction Coordinators

AF Technical Operations

ALP Airport Layout Plan

AMS Acquisition Management System

AOA Airport Operations Area

APML Assistant Program Manager for Logistics

ASDE-X Airport Surface Detection Equipment Model -- X

AT Air Traffic

ATC Air Traffic Control

ATCT Air Traffic Control Tower

ATE Automated Test Equipment

CAI Contractor Acceptance Inspection

CASE Computer Aided System Engineering

CCB Configuration Control Board

CDR Critical Design Review

CDRL Contract Data Requirements List

CDROM Compact Disc Read Only Memory

CFSR Contract Funds Status Report

CI Configuration Item

CM Configuration Management

CMP Configuration Management Plan

CMTP Contractor\'s Master Test Plan

COTR Contracting Officer\'s Technical Representative

COTS Commercial Off-the-Shelf

CPCI Computer Program Configuration Item

CPM Computer Programmer's Manual

CPR Cost Performance Reports

CSAR Configuration Status Accounting Report

CSC Computer Software Components

CSCI Computer Software Configuration Item

C/SCSC Cost/Schedule Control Systems Criteria

CSER Contractor Site Engineering Report

CSU Computer Software Unit

CTP Contractor Transition Plan

CWBS Contract Work Breakdown Structure

DFU Display Functional Unit

DOD Department of Defense

DQT Design Qualification Test

DT Development Test

DT&E Developmental Test & Evaluation

E&R Exchange and Repair

ECP Engineering Change Proposal

EMI Electromagnetic Interference

EVMS Earned Value Management System

FA First Article

FAA Federal Aviation Administration

FAALC FAA Logistics Center

FAST FAA Acquisition System Toolset

FAT Factory Acceptance Test

FCA Functional Configuration Audit

FCC Federal Communications Commission

FDQT Factory Development Qualification Tests

FDR Final Design Review

FLS Field Lighting System

FOD Foreign Object Damage

FQT Formal Qualification Test

GFE Government Furnished Equipment

GFI Government Furnished Information

GFP Government Furnished Property

GUI Graphical User Interface

HEDA Human Engineering Design Approach

HEDA-M Human Engineering Design Approach for Maintainers

HEDA-O Human Engineering Design Approach for Operators

HF Human Factors

HFE Human Factors Engineering

HVAC Heating, Ventilation and Air Conditioning

HWCI Hardware Configuration Item

IBR Integrated Baseline Review

ICD Interface Control Document

ICDLS Interim Contractor Depot Level Support

ICDLSTP Interim Contractor Depot Level Support Transition Plan

ICS Interim Contractor Support

IDD Interface Design Document

IGES Initial Graphical Exchange Specification

ILS Integrated Logistics Support

ILSMT Integrated Logistics Support Management Team

IMS Integrated Master Schedule

IPR In-Process Reviews

IRD Interface Requirement Document

ISO International Standards Organization

ISP Integrated Support Plan

LCN LSA Control Number

LGC Logistics Guidance Conference

LMI Logistics Management Information

LORA Level of Repair Analysis

LP Limited Production

LRU Line Replaceable Unit

LSA Logistics Support Analysis

LSAP Logistics Support Analysis Plan

LSAR Logistics Support Analysis Record

MDT Maintenance Data Terminal

NAS National Airspace System

NCP NAS Change Proposal

NDI Non-Developmental Item

NEPA National Environmental Policy Act

NOR Notice of Revision

NTSB National Transportation Safety Board\
O&SHA Operating & Support Hazard Analysis

OEM Original Equipment Manufacturer

PAT&E Production Acceptance Test & Evaluation

PCA Physical Configuration Audit

PDR Preliminary Design Review

PHA Preliminary Hazard Analysis

PM Program Manager

PMP Program Management Plan

PMR Program Management Review

POC Point of Contact

POSIX Portable Operating System Interface

PQT Preliminary Qualification Test\
PQY Preliminary Qualification Test

PROM Programmable Read Only Memory

PSF Program Support Facility

PSR Program Status Reports

QSP Quality System Plan

RAR Risk Assessment Report

RDT Ribbon Display Terminal

RE Resident Engineer

REL Runway-Entrance Light

RM Risk Management

RMA Reliability, Maintainability, and Availability

RMP Risk Management Plan

ROM Read Only Memory

RWSL Runway Status Lights

SDD Software Design Description

SDM Software Diagnostics Manual

SDP Software Development Plan

SDQT Site Development Qualification Test

SHA System Hazard Analysis

SMR Source, Maintenance and Recoverability

SMS Safety Management System

SOW Statement of Work

SPP Security Program Plan

SPR System Problem Reports

SPS Software Product Specification

SRMGSA Safety Risk Management Guidance for System Acquisitions

SRMP Safety Risk Management Panel

SRR System Requirements Review

SRU Shop Replaceable Units

SSAR System Safety Assessment Report

SSDD System/Subsystem Design Description

SSHA Sub-System Hazard Analysis

SSPP System Safety Program Plan

STD Software Test Description

STP Software Transition Plan

SUM Software User Manual

SVD Software Version Description

TASA Task and Skills Analysis

TDP Training Development Plan

TGC Training Guidance Conference

THL Takeoff-Hold Light

TIM Technical Interchange Meeting

UOQ Unit Ordering Quantity

UPS Uninterruptible Power Supply

VRTM Verification Requirements Traceability Matrix

WBS Work Breakdown Structure