RVR Section C.pdf

SECTION C – 693KA8-21-D-00014

FY21 RVR STATEMENT OF WORK

i

Table of Contents

C.1.0 OVERVIEW

C.1.1 Scope

C.2.0 GENERAL INFORMATION

C.2.1 Applicable Documents C.2.1.1 Federal Aviation Administration (FAA) Documents C.2.1.2 Military Standards, Specifications, and Handbooks C.2.1.3 Other Documents C.2.1.4 Copies of Documents C.2.1.5 System Order of Precedence

C.3.0 REQUIREMENTS

C.3.1 Production Units C.3.2 Deliverables C.3.2.1 RVR Upper Level Components C.3.2.2 Contractor Data Requirements List (CDRLs)

C.3.3 Program Management C.3.3.1 Program Control

C.3.3.2 Meetings, Reviews, and Conferences C.3.4 Quality Assurance (QA) C.3.5 System Engineering

C.3.5.1 System Engineering Management C.3.6 Configuration Management Program

C.3.6.1 Configuration Management (CM) Planning C.3.7 Software Modification C.3.8 Engineering Change Proposal (ECPs)

C.3.8.1 ECP Package C.3.9 Request for Deviation and Waivers C.3.10 Test and Evaluation (T&E)

C.3.10.1 Test Program C.3.10.2 Production Acceptance Test (PAT) C.3.10.3 Test Readiness Review

C.3.11 Technical and Programmatic Risk C.3.12 Engineering Support Services/ Technical Support

C.3.12.1 Contractor Installation Services C.3.12.2 Contractor Repair Services C.3.12.3 Maintenance Support

C.3.13 RVR Parts C.3.13.1 Parts Obsolescence C.3.13.2 System Refresh and Upgrade C.3.13.3 Asset Identification Report

C.3.14 Logistics Management Information (LMI) C.3.14.1 Depot Spares

C.3.15 Technical Data Package (TDP) C.3.16 Copyrighted Materials ii

C.4.0 DEFINITIONS

C.5.0 ACRONYMS

C.1.0 OVERVIEW

C.1.1 SCOPE

This Statement of Work (SOW) includes provisions under which the contract must provide program management, production, system testing and evaluation, and technical and engineering support service to manufacture and deliver Runway Visual Range (RVR) systems.

C.2.0 GENERAL INFORMATION

C.2.1 APPLICABLE DOCUMENTS

The following specifications, handbooks, orders, standards, and drawings form a part of this SOW and are applicable to the extent herein. The applicable and latest versions of the following documents are to be used.

C.2.1.1 FEDERAL AVIATION ADMINISTRATION (FAA) DOCUMENTS

FAA Order1600.6E Facility Security Policy FAA Order 8040.4 Safety Risk Management (SRM) FAA Order 1800.66 Configuration Management Plan (CMP) FAA-STD-002E Standard Engineering Drawing Preparation and Support FAA-STD-021A Configuration Management (Contractor Requirements) FAA-STD-025D Preparation of Interface Documents FAA-STD-028C Contract Training Program FAA-D-1323A Repair and Testing Requirements for FAA Ground

Electronics Equipment FAA-D-2494B Technical Instruction Book (TIB) Manuscript: Requirements for Electronic, Electrical, and Mechanical Equipment FAA-E-2772B Performance Specification PC Based Runway Visual Range

(RVR) System FAA-E-2911 National Airspace System (NAS) System Level

Specification, NAS Infrastructure Management System (NIMS) Managed Subsystems

FAA-G-2100H Electronic Equipment General Requirements FAA-HF-STD-001 Human Factors Design Standard

(http://www.hf.faa.gov/hfds.htm) http://www.hf.faa.gov/hfds.htm

FAST-Toolset FAA Acquisition Strategy Toolset (FAST), Toolbox Guidance [http://fast.faa.gov/]

FAST-System Safety Handbook

FAA Acquisition Strategy Toolset (FAST), System Safety Handbook http://fast.faa.gov/SafetyManagement.cfm?p_title=Functions

FAST-Test and Evaluation

FAA Acquisition Strategy Toolset (FAST), Test and Evaluation Process Guidelines http://fast.faa.gov/test_evaluation/test_eval_toc.htm

FAST-WBS FAA Acquisition Strategy Toolset (FAST), Work Breakdown Structure (WBS),http://fast.faa.gov/WorkBreakdownStructure.cfm?p_t itle=Special%20Topics

TI 6560.74 Technical Instruction Book PC-Based Runway Visual Range (RVR) System Type FA-19200

C.2.1.2 MILITARY STANDARDS, SPECIFICATIONS, AND HANDBOOKS

MIL-P-55110H Printed Wiring Boards, Rigid, General MIL-HDBK-61A Configuration Management Guidance

MIL-HDBK-881 Work Breakdown Structure MIL-HDBK-46855A Human Engineering Program Process and

Procedures MIL-STD-454N Standard General Requirements for Electronic

Equipment MIL-STD-461F Requirements for the Control of Electromagnetic

Interference Emission and Susceptibility MIL-STD-462D Measurement of Electromagnetic Interference

Characteristics MIL-STD-31000 Technical Data Packages (TDPs) MIL-STD-129R Marking for Shipment and Storage MIL-STD-2073-1E Department of Defense (DOD) Standard Practice for Military Packaging MIL-STD-810G Environmental Test Methods and Engineering

Guidelines MIL-STD-882D Standard Practice for System Safety MIL-STD-961 Standard Practice for Defense Specifications http://fast.faa.gov/ http://fast.faa.gov/SafetyManagement.cfm?p_title=Functions

C.2.1.3 OTHER DOCUMENTS

ANSI/ISO/ASQC Q9001-

Quality Systems – Requirements

ANSI/ISO/ASQC-Q9003-

Quality Systems-Model for Quality Assurance in Final Inspection and Test

ANSI C37.90.1-2002 IEEE Standard Surge Withstand Capability (SWC) Tests for Relays and Relay Systems Associated with Electric Power Apparatus

ASTM-D3951-10 Commercial Packaging Requirements ASTM-D-3951 Standards and Practices for Commercial Packaging EIA/IS-649 National Consensus Standard for Configuration

Management Practical Software Measurement, Version 2.1

GEIA-STD-0007 Logistics Data Product NFPA No. 70 National Electric Code OSHA 29 CFR 1910 Occupational Safety and Health Administration

(OSHA) Standards

C.2.1.4 COPIES OF DOCUMENTS

Copies of FAA specifications, standards, publications, drawings, and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center, 800 Independence Avenue SW, Washington, DC 20591, (202) 267-3484.

Requests should fully identify material desired and cite the solicitation or Contract number.

Military Standards and Specifications may be ordered from the Department of Defense Single Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5098. Copies of Federal publications may be obtained from the U.S.

Government Printing Office, by calling (202) 512-0132, or through http://bookstore.gpo.gov/.

American National Standards Institute (ANSI) and International Organization for Standardization (ISO) documents may be obtained from the American National Standards Institute, 25 West 43rd Street, New York, NY 10036, or through http://www.ansi.org.

Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The online Internet address of FAST is: http://FAST.faa.gov.

Requests for copies of documents not covered in the preceding paragraphs must be addressed to the RVR Contracting Officer (CO). Requests must fully identify the material desired and cite the solicitation or contract number for which the copy is requested.

C.2.1.5 SYSTEM ORDER OF PRECEDENCE

The provisions within this SOW supersede and control any conflicting provisions that might exist in any of the documents. The following order of precedence controls conflicting provisions:

a. Schedule;

b. TI 6560.74;

c. FAA-E-2772B, Performance Specification PC Based Runway Visual Range (RVR);

d. FAA Specifications;

e. FAA Standards and Orders;

f. FAA Engineering (Drawing) Package

g. DoD Standards and Orders;

h. Other FAA documents (Other than Specifications);

i. Other documents incorporated by reference.

C.3.0 REQUIREMENTS

The Contractor must satisfy the requirements of this contract in accordance with (IAW) this SOW.

The Contractor must provide program management, engineering, production, system testing and evaluation, and technical and engineering support service to manufacture and deliver Runway Visual Range (RVR) Systems, IAW this SOW.

The Contracting Officer (CO) or Contracting Officer Representative (COR) will approve all items delivered in response to this SOW. All references to the “Government” or “FAA” in this SOW mean by authority of the CO or COR.

The Contractor must produce the data items referenced by Contract Data Requirements List (CDRL) titles IAW the CDRL of the same name. Unless otherwise specified, the Contractor must deliver all CDRLs to the Government electronically.

C.3.1 PRODUCTION UNITS

The packing, packaging, and shipment requirements of production units must be IAW section D of this contract. Each production unit must include at a minimum One Basic RVR System, Two Site Spares Kit, Two Technical Instruction Books, and One Certificate of Compliance. Any anomalies during production must be addressed in accordance with the latest FAA accepted Quality System Plan (QSP).

The FAA intends to acquire PC-Based RVR Systems and components. Contractor must build the RVR to part number RVR-BASIC-SYSTEM..

C.3.2 DELIVERABLES

C.3.2.1 RVR UPPER LEVEL COMPONENTS

The RVR must consist of all Contract Line Item Numbers (CLINs) or upper level components listed below. Upon FAA acceptance, the contractor must provide a copy of the high-level system and/or component configuration sheet (with all serial numbers included) to the Program Office within seven calendar days of acceptance.

C.3.2.1.1 CLIN 001 - BASIC RVR SYSTEM

The Basic RVR System must consist of the upper level components listed below.

Over the life of this contract the Basic RVR System will be ordered by CLINs 001, 1001, and 2001,respectively.One “Basic RVR System” must contain the following items (which can be ordered individually by CLIN):

• One Data Processing Unit (DPU)

• One Visibility Sensor (VS) Assembly

• One Ambient Light Sensor (ALS) Assembly

• One Runway Light Intensity Monitor (RLIM) assembly

• One set of Site Spares

• One Accessory Kit, and

• One Calibration Kit

C.3.2.1.2 CLIN 002 - DATA PROCESSING UNIT (DPU)

The Data Processing Unit, or DPU (Type FA-19200/1) consists of an industrial grade computer loaded with all required cards, interface ports, all required operational and maintenance software, monitor, power cords, keyboard and mouse.

Over the life of this contract the DPU will be ordered by CLINs 002, 1002, and 2002, respectively.

CLIN 002a-Digi Connector Port LTS 16 MEI

The Digi Connector Port LTS 16 MEI (p/n 249274) is part of the Data Processing Unit

CLIN 002b-1TB 7.2K RPM SATA 6Gbps 512n 3.5in Hot-plug Hard Drive

The part number is 2MN130-136, this is a part within the DELL R340 Server which is part of the Data Processing Unit (DPU).

CLIN 002c-DVD +/-RW, SATA, Internal for Hot Plug Chassis

The part number is KCC-REM-HLD-GU90N, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002d-Hot Plug Power Supplies

This part number is L350E-S1 (single), this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002e- PCle Riser, 1xFHx8 PCle Gen3 Slot, 1x LP x4 PCle Gen3 Slot

This part number is 0593D8, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002f- Dell Standard Bezel

This part number is 09MTRW, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002g-PERC H730P Adapter RAID Controller, 2GB

This part number is 01041DC00-000-G, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002h- 8GB 2666MT/s DDR4 ECC UDIMM

This part number is MTA9ASF1G72AZ-2G6E1Z1, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002 i- Ready Rails Sliding Rails Kit

The part number is 02J1CF, this is a part within the DELL R340 Server which is part of the DPU.

CLIN 002 j- Power Cord-C13, 3m, 125V, 15A

The part number is 00R215, this is a part within the DELL R340 Server which is part of the DPU.

C.3.2.1.3 CLIN 003 - VISIBILITY SENSOR (VS)

The Visibility Sensor, or VS assembly (Type FA-19200/2) consists of the visibility sensor, Sensor Interface Electronics (SIE), and interconnecting cables. Over the life of this contract the VS will be ordered by CLINs 003, 1003, and 2003 respectively.

CLIN 003a- VISIBILITY SENSOR (VS) PARTS

The Visibility Sensor parts (RVR-2A1A1) consist of the Visibility Sensor (VS) head and interconnecting cables. Over the life of this contract, the VS parts will be ordered by CLIN 003a.

C.3.2.1.4 CLIN 004 - AMBIENT LIGHT SENSOR (ALS)

The Ambient Light Sensor, or ALS assembly (Type FA-19200/2) consists of the ambient light sensor and interconnecting cables. Over the life of this contract the ALS will be ordered by CLINs 004, 1004, and 2004 respectively.

CLIN 004a – AMBIENT LIGHT SENSOR (ALS) PARTS

The Ambient Light Sensor Parts (RVR-2A2A1) consist of the Ambient Light Sensor head and interconnecting cables. Over the life of this contract, ALS parts will be ordered by CLIN 004a.

C.3.2.1.5 CLIN 005 - RUNWAY LIGHT INTENSITY MONITOR (RLIM)

The Runway Light Intensity Monitor, or RLIM assembly (Type FA-19200/3) consists of two Current Sensors, Sensor Interface Electronics (SIE), and interconnecting cables. Over the life of this contract the RLIM will be ordered by CLINs 005, 1005, and 2005 respectively.

C.3.2.1.6 CLIN 006 - CURRENT SENSORS (CS)

The Current Sensors, or CS are a key component of the RLIM. They may be ordered individually or by bulk within the CS CLIN. Over the life of this contract CS will be ordered by CLINs 006, 1006, and 2006 respectively.

C.3.2.1.7 CLIN 007 – RVR SPARES

If ordered by the Government, the Contractor must provide a recommended spares (including expendable and consumable items) list to the Government IAW CDRL A018. All Spares must be delivered in accordance with sections D and F of this contract.

(a) Site Spares Kit - There must be one set of site spares included with each deliverable RVR system. The site spares must satisfy the requirements of the PC- Based RVR Specification FAA-E-2772B. All RVR Site Spares Kits must include a network Switch, ALS Sensor, Visibility Sensor, SIE Modem, RLIM CLS (with associated cable), two Over Voltage Protection, an MCU Connector Plate. RLIM SIE IEA, VS/ALS SIE IEA, MCU Modem, and Spare Port Server must be included as part of the kit. If requested by the government, Spare Kit items must be made available for individual order by component as Spare Parts.

Each replaceable module and printed circuit card must pass all required Production Acceptance Tests. Over the life of this contract the Site Spares Kit will be ordered by CLINs 007, 1007, and 2007 respectively.

(b) – Spare Parts Peculiar - The Contractor must prepare and deliver IAW the above CDRL a Spare Parts List for Spare Parts Peculiar, identifying any parts that may become obsolete in the foreseeable future.

CDRL: RVR Site Spares and Spare Parts Peculiar List

C.3.2.1.8 CLIN 008 - CALIBRATION KIT

If ordered by the Government, the RVR Calibration Kit must include all tools needed to calibrate the VS Sensor and ALS Sensor. Over the life of this contract Calibration Kits will be ordered by CLINs 008, 1008, and 2008 respectively.

C.3.2.1.9 CLIN 009 - ACCESSORY KIT

The RVR Accessory Kit must include, at a minimum, two latest versions of the CD Users Guides, two versions of the FAA approved Technical Instruction Manual, and one special tools kit (see C.3.2.1.13). Over the life of this contract, Accessory Kits will be ordered by CLINs 009, 1009,and 2009 respectively.

Note: Any additional RVR components required to meet site-specific airport operational configurations are identified in Section B of this contract. The components will be added to the site shipments to meet the needs of individual airports, up to the maximum configuration specified in FAA-E-2772B.

C.3.2.1.10 CLIN 010 - PROGRAM OVERVIEW MEETING (POM)

If ordered by the Government, the Contractor must host and conduct Program Overview Meetings (POMs) at the Contractor’s facility IAW section C.3.3.2.2.

POMs will be ordered by CLINs 010, 1010, and 2010 respectively.

C.3.2.1.11 CLIN 011 - TECHNICAL INTERCHANGE MEETING (TIM)

If ordered by the Government, the Contractor must host and conduct a maximum of ten Technical Interchange Meetings (TIMs) at the Contractor’s facility IAW section C.3.3.2.3. TIMs will be ordered by CLINS 011, 1011, and 2011, respectively.

C.3.2.1.12 CLIN 012 - ENGINEERING SUPPORT SERVICES (ESS)

If ordered by the Government, the Contractor must provide Engineering Support Services (ESS) for the contract period (including all option years) IAW section C.3.12. Over the anticipated five-year life of this contract ESS will be ordered by CLINs 012, 1012, and 2012 respectively.

C.3.2.1.13 CLIN 013 - SPECIAL TOOLS AND TEST EQUIPMENT

Each RVR system’s special tools and test equipment, must include one set of any unique tools and test equipment peculiar to the Contractor’s RVR not readily available from other commercial sources, and which are required for performing site maintenance, for example VS calibration. In addition, the contractor must provide any special cabling required for system component testing or troubleshooting, which includes one controller display RS232 test cable assembly and one controller display RS485 test cable assembly.

C.3.2.1.14 CLIN 014 – POST AWARD CONFERENCE

If ordered by the Government, the Contractor must host and conduct a Post Award Conference (PAC) at the Contractor’s facility IAW section C.3.3.2.1. The PAC will be ordered by CLIN 014.

C.3.2.1.15 CLIN 1014- Depot Spares

If ordered by the Government; the Contractor must provide depot spares. The FAA will specify Depot Spare parts upon order based on agreed upon prices. The Contractor must package and ship the depot spares IAW section D and F. The contractor must ship all Depot spare parts, including spare parts peculiar, Freight on Board (FOB) Origin to the following address:

Mark for: Operating Stock

Mike Moroney Aeronautical Center FAA Logistics Center 6500 South MacArthur Blvd Oklahoma City, OK 73125

C.3.2.2 CONTRACTOR DATA REQUIREMENTS LIST (CDRLS)

Below are Contractor Data Requirements List (CDRL) items to be delivered under this contract. Timeframes for delivery are in accordance with the corresponding section unless written agreement has been received by the CO or program office.

A001 Program Management Plan (PMP) A002 Program Status Reports (PSR) A003 Delivery Schedule A004 Meeting Agenda A005 Meeting Minutes A006 Configuration Management Plan (CMP) A007 Request for Deviation or Waiver A008 Production Acceptance Test Report A009 Production Acceptance Test Plan A010 Production Acceptance Test Procedures A011 Asset Identification Report A012 Logistics Management Information (LMI) Data Products A013 Technical Data Package (TDP) A014 Quality System Plan A015 System Software (SS) Report A016 Systems Engineering Management Plan (SEMP) A017 Contractor Repair Results Report A018 RVR Site Spares and Spare Parts Peculiar List

C.3.3 PROGRAM MANAGEMENT

The contractor must establish a formal organization to manage this contract and any subcontracts. A management program must be established to efficiently and effectively execute the requirements of this contract. The Contractor must assign a Program Manager to organize, plan, schedule, implement, control, analyze, and report on all elements of the Contract. The Contractor must designate a Program Manager who has the experience and resources necessary to ensure efficient and timely program execution, and is the focal point for all required program tasks.

C.3.3.1 PROGRAM CONTROL

The Contractor is responsible for organizing, planning, scheduling, implementing, controlling, analyzing, and reporting on all elements of the Contract. The Program Manager must, with a maximum of five business days’ notice, be prepared to present and discuss the status of contract activities. All changes in key personnel must be submitted to the CO for approval.

C.3.3.1.1 PROGRAM MANAGEMENT PLAN

A draft Program Management Plan (PMP) must be provided to the CO and COR after award of the contract as specified in the Post Award Conference (PAC). The final version, with all edits and updates as a result of the PAC, must be submitted NLT 30 business days after the PAC for FAA approval. This plan at a minimum must entail the following sections/subsections.

1.0 Introduction – including Program scope, Program overview, any Program timeframe estimates, and any assumptions, dependencies, or constraints.

2.0 Program Management Structure – including organizational structure, staffing plan/key personnel, and roles and responsibilities.

3.0 Program Control

3.1 Program Technical Approach – including Work Breakdown Structure, schedule management, cost management requirements management, latest draft requirement Traceability Matrix, latest RVR Risk Register, Contract Management, Quality Management, Test evaluation approach, and integrated change control process.

3.2 Program Plans – Current version(s) of all government requested plans including CMP, PAT, QSP, and SEMP.

4.0 Packaging, handling, storage, and transportation.

5.0 Program Closeout.

CDRL: Program Management Plan

C.3.3.1.2 PROGRAM STATUS REPORT

If ordered by the Government, the Contractor must provide Program Status Reports (PSRs) and Data Item Description (DID) to the CO or COR on a quarterly basis. PSRs must include subcontract items and services. They must ensure cost, performance, and schedule requirements are met. PSRs must be used to provide early detection and resolution of problems, and to reduce any programmatic risk. As a result, if any plans (CMP, QSP, SEMP, etc.) are updated, the latest version must be included as an appendix in the following PSR. The PSR must include but is not limited to the following:

a. Summary of Program Status;

b. Issues and Concerns;

c. Equipment Repair items and status

d. Risk Analysis;

e. Obsolescence Issues/ Forecast

f. Technical Performance; and

g. Network Logic or Integrated Program Schedule.

CDRL: Program Status Report

C.3.3.1.3 DELIVERY SCHEDULE

The Contractor must present the delivery schedule at the Post Award Conference (PAC) for discussion and submit an updated version NLT 30 business days after PAC as part of the final PMP. The delivery schedule must detail the time it takes to build each component or CLIN of the RVR system (from time of award to delivery). The Contractor must provide an updated delivery schedule showing the progress of all items ordered quarterly in the PSR. The delivery schedule must be constructed and tracked using Microsoft Project.

CDRL: Delivery Schedule

C.3.3.2 MEETINGS, REVIEWS, AND CONFERENCES

If ordered by the Government, the Contractor must conduct meetings, conferences, and technical reviews at the Contractor’s facility. For each meeting, technical review and conference, the Contractor must prepare and submit agendas and meeting minutes. If meetings, technical reviews, or conferences are held at the Contractor’s site, the Contractor must provide facilities, office equipment (e.g., access to telephone, fax), internet access, and appropriate presentation materials, mock-ups, and technical data. Copies of presentation materials must be prepared for all meeting participants. Government attendance will be limited to no more than 25 participants.

All meetings, when ordered against a specific CLIN, are required to have a meeting agenda submitted to the FAA for approval no later than 10 (ten) days before each meeting unless otherwise expressed. After each meeting, minutes will be provided by the Contractor to the FAA for approval. These minutes will include a narrative summation of the meeting, a summary of action items assigned, a list of attendees, and the schedule of activities conducted, unless otherwise expressed. The minutes will need to be approved before submission of the invoice for that meeting.

C.3.3.2.1 POST AWARD CONFERENCE (PAC)

The Contractor must hold a Post Award Conference (PAC) (CLIN 014) at the Contractor’s facility in response to the RVR award. The Contractor must prepare a PAC briefing package and present their approach to accomplishing logistics management task(s). The Contractor must support the conference with the required resources to include the briefing, documentation including draft PMP, and staffing necessary to discuss any support considerations. The Contractor must clarify any potential requirements and issues, deliverables, data requirements, technical documentation and data as necessary. The CO or COR will coordinate with the Contractor to set the date of the PAC. The PAC must not be more than one business week in length. The Contractor must transmit the draft PAC documents including briefing package to the CO or COR via electronic mail at least 21-calendar days prior to the PAC. During the PAC, the Contractor must provide and brief the following:

a. Introduce key personnel;

b. Brief program plans and approaches for satisfying each SOW requirement— including management and quality control;

c. Provide and discuss in detail the schedule;

d. Contract review to discuss deliverables, tasks to perform, and special contract provisions;

e. Organizational diagram;

f. Change control; and the

g. Overview of Logistic Management Information (LMI) Data, which includes:

1. Maintenance Planning;

2. Supply support/provisioning (Logistics Management Information

(LMI);

3. Updated Technical Data Package (TDP);

4. Support and test equipment;

5. Packaging and shipping;

6. Manpower and Personnel; and

7. Training.

The Contractor must prepare and submit for Government review, a meeting agenda at least 10-calendar days prior to the conference. The FAA may, as a result of this review, direct the Contractor to add additional items to the agenda. The Contractor must prepare and submit to the CO or COR, minutes of the conference within 10-calendar days of the conference end date. Minutes are to include a detailed narrative summation of the meeting, a summary of action items assigned (inclusive of assignee and due date), a list of attendees, and the schedule of activities conducted.

CDRL: Meeting Agenda CDRL: Meeting Minutes

C.3.3.2.2 PROGRAM OVERVIEW MEETING

If ordered by the Government, the Contractor must host and conduct Program Overview Meetings (POMs) at the Contractor’s facility. The content of the POM must identify outstanding action items, include a detailed contract status, review potential and actual technical and programmatic areas, and provide a forum for highlighting all the activities planned for the next period. Areas normally covered at these meetings may include, but are not limited to:

a. Risk and problem identification, ranking, avoidance, reduction, and control;

b. Establishment of schedules, to include critical path identification and performance baseline;

c. Progress tracking and reporting of milestones;

d. Definition and implementation of contingency planning;

e. Subcontractor management to include technical effort status and the identification of potential problem areas;

f. Logistic support status;

g. Manufacturing status;

h. Production problems/status (resolved/unresolved);

i. Identification of parts obsolescence;

j. Inventory of parts; and

k. Quality Metrics.

The Contractor must prepare and submit for Government review, a meeting agenda at least 10-calendar days prior to the meeting. The FAA may, as a result of this review, direct the Contractor to add additional items to the agenda. The Contractor must prepare and submit to the CO or COR, minutes of each meeting within 10-calendar days of the meeting’s end date. Minutes are to include a detailed narrative summation of the meeting, a summary of action items assigned, a list of attendees inclusive of assignee and due date, and the schedule of activities conducted. The POM must be no more than 3-calendar days in length.

C.3.3.2.3 TECHNICAL INTERCHANGE MEETING

If ordered by the Government, the Contractor must host and conduct a maximum of five Technical Interchange Meetings (TIMs) at the Contractor’s facility to discuss specific technical activities, including but not limited to:

a. Studies;

b. Test plans;

c. Risk;

d. Test results;

e. Design issues including human engineering;

f. Technical problems;

g. Training issues;

h. Logistics issues;

i. Implementation concerns;

j. Verification audit; and

k. Monitor the technical progress of the contract.

Meeting durations, attendees, and agenda will be determined by the issues brought up or by the discussions during the meeting. The Contractor must prepare and submit for Government review, a meeting agenda at least 10-calendar days prior to the conference. The FAA may, as a result of this review, direct the Contractor to add additional items to the agenda. The Contractor must prepare and submit to the CO or COR detailed minutes, inclusive of assignee and due date, of each TIM within 10-calendar days of the meeting’s end date. The TIM must be planned for no more than 3-calendar days in length.

C.3.3.2.3.1 PROVISIONING CONFERENCE

If ordered by the Government, the Contractor must host and conduct a maximum of one Provisioning Conference (CLIN 011) at the Contractor’s facility. The Provisioning Conference may be held no later than 30-calendar days after completion of the Verification Audit, with all LMI updates incorporated.

The Contractor must hold a Provisioning Conference at the Contractor’s facility unless otherwise specified by the FAA. At the Provisioning Conference, the Contractor must provide the following data, equipment, and services:

a. One complete set of assembly and detail drawings for each item that appears on the LMI Data to include proprietary and nonproprietary documents/data.

Proprietary documents and data will not be removed from the facility;

b. The Government-approved Technical Instruction (TI) Manual;

c. Copies of the FAA-approved Verification Audit documentation available for use as a reference;

d. A complete assembled RVR (one of the First Article systems) including tools required;

e. A recommended list of required site and depot spares, including spare parts peculiar;

f. Knowledgeable personnel to disassemble the equipment(s) to the extent required by the FAA provisioning team and tools needed for disassembly;

and

g. Facilities with adequate accommodation for the FAA provisioning team and Contractor personnel.

The CO or COR will advise the Contractor of the number of FAA representatives prior to the Provisioning Conference. The audit can be performed separately, or as part of TIM activities. The Provisioning Conference must be planned for 2-calendar days in length.

C.3.3.2.3.2 VERIFICATION AUDIT

If ordered by the Government, the Contractor must host and conduct a verification audit to validate the RVR design and function. The verification audit must be conducted on the initial production units. Any approved ECP changes must be incorporated prior to the audit, and any differences must be documented with a justification for the change. The audit can be performed separately or as part of TIM activities. Any documented changes must be included in the subsequent PSR or TIM minutes, as appropriate. Once the audit results are approved by the FAA, all changes must follow the ECP process. The verification audit must be no more than 3-calendar days in length.

C.3.4 QUALITY ASSURANCE (QA)

The Contractor must use a quality system to assure compliance with the hardware, software, firmware, documentation, and support requirements of the contract. The Contractor must use the latest FAA accepted Quality System Plan (QSP). Any required changes to the QSP need approval from the FAA. The Contractor must be accountable for implementing the QSP. The QSP must ensure, as a minimum, that the following items and guidelines are included in the program:

a. Sufficient, independent responsibility and authority are granted to assigned personnel so that quality problems can be identified, evaluated, and reported, and that solutions can be recommended without fear of reprisal, intervention, or adverse action;

b. Software quality evaluations and internal in-process reviews are conducted, results are documented, and recommendations followed;

c. Adequate configuration management is performed throughout the lifecycle;

d. All tests and inspections are performed in compliance with contract requirements and all test data are complete, correct, traceable, repeatable, and acceptable.

All spare parts must be inspected and tested in-plant using the same production test procedures as the primary equipment components.

The Contractor must require of their sub-tier suppliers a quality system achieving quality control of the services and supplies provided. Further, the Contractor must report its quality metrics during each PSR and in the POM if one is held.

C.3.5 SYSTEM ENGINEERING

C.3.5.1 SYSTEM ENGINEERING MANAGEMENT

If requested by the Government, the Contractor must specify an Engineering Lead to serve as the point-of-contact for all system engineering issues. The Contractor must maintain the system engineering and design development process identified in the latest FAA accepted System Engineering Management Plan (SEMP) presented at the PAC. If ordered by the Government, the Contractor must submit a System Engineering Management Plan (SEMP) no later than 30-calendar days after date of order. The Contractor must follow the SEMP and ensure cost, performance, and schedule requirements are met, provide early detection and resolution of problems, and reduce risk. Any potential issues or risk as a result of system engineering must be identified in a POM, TIM, or PSR, as appropriate.

CDRL: System Engineering Management Plan

C.3.6 CONFIGURATION MANAGEMENT PROGRAM

C.3.6.1 CONFIGURATION MANAGEMENT (CM) PLANNING

If ordered by the Government, the Contractor must submit a Configuration Management Plan (CMP) no later than 30-calendar days after date of order. The CMP, as a minimum, must include responsibilities, methodology and procedures for baseline identification, configuration control and audit and status accounting of software, hardware, documentation, support equipment, firmware and databases. Any changes to the CMP after Government approval must have approval from the Government. The CMP must detail the contractor’s internal interface responsibilities and Contractor interface with FAA Program Management, Technical Systems Engineering, Quality Assurance (QA) and Test and Evaluation (T&E). The Contractor must maintain configuration control of the hardware to the Line Replaceable Unit (LRU) level. The Contractor must identify the single focal point, under the Program Manager, who will serve as the primary Point of Contact for all communication on CM-related issues. The Contractor must follow and maintain the CMP throughout the life of the contract.

CDRL: Configuration Management Plan

C.3.6.1.1 CONFIGURATION CONTROL

The Contractor must maintain a system that retains all documentation for identification, control, and status accounting of all Configuration Items (CIs) throughout the RVR program life cycle.

C.3.6.1.2 CONFIGURATION STATUS ACCOUNTING

At the Government’s request, the Contractor must maintain the configuration baseline for the RVR and the required documentation to support this baseline. The Contractor must record and report the following information for configuration status accounting:

a. Current approved configuration documentation associated with each configuration item;

b. Status of proposed engineering changes and deviations from initiation to approval and status of their implementation;

c. Results of configuration audits including disposition of actions;

d. Traceability of changes;

e. Status of the implementation of changes at all locations; and the

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

C.3.6.1.3 CONFIGURATION ITEM (CI) IDENTIFICATION

The Contractor must maintain configuration control of the RVR and its CIs. This includes:

a. Selecting CIs at appropriate levels of the product structure to aid documentation, control, and support of the items;

b. Determining the types of configuration documentation required for each CI to define its performance, functional and physical attributes, including internal and external interfaces;

c. Determining the appropriate configuration control authority for each configuration document consistent with logistic support planning for the associated CI;

d. Issuing identifiers for the CIs and the configuration documentation;

e. Maintaining the configuration identification of CIs to facilitate effective logistics support of items in service;

f. Releasing configuration documentation; and

g. Establishing CI configuration baselines.

The Contractor must designate as a CI any item subject to replacement that is used without modification from a subordinate vendor, as a serialized end-item for tracking, or for FAA acceptance purposes. The Contractor must assign a discrete part number or item identification number to each CI.

The Contractor must assign a discrete part/identification number to each magnetic disc or CD-ROM containing release or build-type software executables. The disc or CD-ROM must provide easy identification of releases after the product baseline is established.

C.3.7 SOFTWARE MODIFICATION

When applicable, the Contractor must obtain End-User License Agreements (EULAs) for all Commercial-Off-The-Shelf (COTS) software (such as Microsoft Windows) obtained or otherwise purchased in support of this contract, showing the FAA as the end user.

Further, the Contractor must forward a copy of each EULA with each RVR component delivered that contains COTS software. Software upgrade licenses will be handled similarly.

The Contractor must deliver to the FAA all ownership interests in and warranties for all COTS RVR hardware/software for all systems and components delivered under this contract.

The Contractor must provide the FAA with any updates to (i) the source code delivered under current contract and (ii) any software modules which the FAA funds under this contract provided either affect the PC-RVR functionality and/or operability. This source code and associated updates must be delivered together with detailed manufacturing and model nomenclature via CD-ROM or other FAA approved medium. Applicable updates to Development Item (DI) and NDI software running on the system, along with any changes in the software development environment, must be clearly identified with respect to latest FAA-accepted software documentation.

C.3.8 ENGINEERING CHANGE PROPOSAL (ECPS)

The Contractor must classify the ECPs as Class I and Class II, per MIL-HDBK-61A, Section 6.2.2. The change and its rationale are to be clearly identified in the ECP.

Following classification, the Contractor must submit all ECPs to the Quality Reliability

Officer (QRO) for classification concurrence. Classification disagreements must be referred to the CO or COR for final decision before formal submission. Upon receiving classification concurrence, the Contractor must formally submit all ECPs designated Class I to the CO IAW MIL-HDBK-61A, Section 6.2. ECPs which require testing must be submitted at least three weeks prior to the start of any formal testing. The Contractor must conduct a Risk versus Benefits Analysis, to include life cycle and transition planning, prior to notifying the FAA.

The ECP is Class I if it proposes any changes outside the RVR specification, including changes that affect the baselined limits or tolerances. The FAA CO or COR will approve Class I ECPs. The FAA will have a 60-calendar day review cycle for all Class I ECPs.

All other changes to the RVR are considered Class II changes. Class II changes are to be specified for local approval by the QRO.

C.3.8.1 ECP PACKAGE

The Contractor must submit to the CO and COR a draft package containing any/all proposed changes at a minimum 30 calendar days prior to a final ECP Package submission. The final ECP Package must include any updates to the below documents a-i for each RVR Basic System Component (DPU and/or Assemblies). If there are any FAA updates to the final ECP package, the final package must be updated and re-submitted to the FAA within 14 calendar days. The final package must contain all proposed changes to documentation by version number resulting from the corresponding ECP. At a minimum, the Contractor must review any impacts and provide updates by version number as a result of an ECP request to the following documentation:

a. Technical Data Package (TDP)

b. Software Design Description (SDD);

c. Software Product Specification (SPS);

d. Software Version Description (SVD);

e. Software Requirements Spec (SRS);

f. Logistics Management Information (LMI) Data;

g. Firmware Support Manual;

h. Technical Instruction Manual;

i. Item Development Specification (IDS).

Any changed documentation must have all changes highlighted by change bars, was/now annotations, and accompany any associated ECP request.

C.3.9 REQUEST FOR DEVIATION AND WAIVERS

The Contractor must submit a request for deviation or waiver to the CO or COR at least 14 calendar days prior to departing from the approved baseline. Each deviation request must detail a specific number of units and a specified period of time, IAW the guidance contained in FAA-STD-021A, Section 4.6. Deviations and waivers may not require changes to any RVR baseline documentation.

CDRL: Request for Deviation or Waiver

C.3.10 TEST AND EVALUATION (T&E)

Any Test and Evaluation (T&E) efforts must demonstrate that the RVR meet the performance requirements, as stated in the PC-Based RVR Specification FAA-E-2772B.

The FAA may witness Contractor testing during any test phase or level. The Contractor must furnish facilities, equipment, space, and personnel required to perform Contractor-conducted tests.

C.3.10.1 TEST PROGRAM

The contractor must notify the COR, QRO and Test and Evaluation team at least 15 business days prior to the start of formal testing in the USA, and 60 calendar days of any testing out of the USA. The Contractor must develop a draft test plan and provide to the FAA for comment and approval NLT 30 days prior to start of any formal testing, or as a result of a Test Readiness Review (TRR). The Contractor must provide the COR, QRO and Test and Evaluation Team (lead by the test director) with copies of raw data and final test results in a results report no later than 10-calendar days after completion of formal testing.

The Contractor must notify the FAA not less than 30 calendar days before the start of Testing. The Contractor must conduct Tests IAW FAA-approved Production Acceptance Test procedures.

C.3.10.2 PRODUCTION ACCEPTANCE TEST (PAT)

The Contractor must conduct Production Acceptance Testing (PAT) on every delivery order IAW Government- accepted PAT Procedures. The Government may elect to witness these tests. The Contractor must notify the FAA at least 10 calendar days in advance of each of these tests. The Contractor must complete and submit a PAT Report for Government review and approval.

The equipment under test must successfully complete and pass a formal PAT Test before the FAA accepts delivery of equipment. The QRO has discretion to identify the equipment the Contractor must test as part of a Delivery Order. In the event of multiple failures, the Contractor must make necessary repairs and retest the equipment at the

Contractor’s expense, IAW the QRO direction. After the repaired unit or units pass PAT Test, the QRO may select any other unit (part of the DO) for additional tests. If the second unit fails, the entire lot may be rejected. Failure to successfully complete PAT Tests may delay FAA acceptance of equipment until all deficiencies have been resolved.

C.3.10.2.1 PAT REPORT

If requested by the Government, the Contractor must provide a PAT report to the FAA within 30 Calendar days after request. The PAT report must contain four sections, Section 1, Introduction; The introduction must be a summary of all updates in both the PAT plan and PAT procedures. Section 2 PAT Plan; the PAT plan section is the latest PAT Plan with all updates incorporated. Section 3, PAT Procedures; the PAT Procedures section is the latest PAT Procedures with all updates incorporated. Section 4; results or findings as a result of PAT.

C.3.10.2.2 PAT PLAN

The Contractor must use the latest FAA-accepted PAT Plan. The PAT Plan must describe two series of tests: Manufacturing Tests which ensure the manufacturing process is producing quality units, and Factory Acceptance Tests which ensure each unit is defect free and meets requirements before shipment. The PAT Plan must relate test objectives to requirements of this SOW and the PC-RVR Specification FAA-E-2772B. The contractor must provide the latest PAT Plan no later than three calendar days before start of test. Any updates to the PAT plan require FAA approval.

C.3.10.2.3 PAT PROCEDURES

The Contractor must use the latest FAA-accepted PAT Procedures. The contractor must provide the latest PAT Plan no later than three calendar days before start of test. The Contractor must use the PAT Procedures for each PAT. The Contractor must ensure that the test procedures indicate traceable paths to the Verification Requirements Traceability Matrix (VRTM) in PC-RVR Specification FAA-E- 2772B.

CDRL: Production Acceptance Test Report CDRL: Production Acceptance Test (PAT) Plan CDRL: Production Acceptance Test (PAT) Procedures

C.3.10.3 TEST READINESS REVIEW

If ordered by the government the contractor must conduct a Test Readiness Review (TRR). The purpose of the test readiness review must be to ensure the Contractor is prepared for formal testing. Contractor must develop an initial draft test report (in the PAT Report format) and provide it to the FAA at least 1 business day prior to start of any TRR activity. The FAA Test Team must be allowed to review and comment on any TRR documents including test reports for approval prior to producing a final version. If multiple TRRs occur, the Contractor must include issue tracking as part of the TRR report.

C.3.11 TECHNICAL AND PROGRAMMATIC RISK

The Contractor must identify program technical and schedule risks and report the status of these risks to the Government in quarterly PSRs. The Contractor must evaluate program schedule risks and formulate plans and a risk management schedule, for the elimination or reduction of such risks. The risk management schedule, mitigation, and contingency plans will be reviewed and discussed at the PAC, TIMs, and/or potential POMs.

C.3.12 ENGINEERING SUPPORT SERVICES/ TECHNICAL SUPPORT

If ordered by the Government, the Contractor must provide Engineering Support Services for the contract period including all option years. These services will be used for items such as system and equipment maintenance and engineering, testing, installation services, maintenance efforts, product improvement, and documentation.

The Contractor’s personnel must have experience on RVRs and must have knowledge of the system’s hardware, software, firmware, and functional and performance features sufficient to perform any assigned task(s) associated with support services. The personnel and the material needed to perform any support services task(s) must be available at the locations specified by the Government within 5 business days of notification.

C.3.12.1 CONTRACTOR INSTALLATION SERVICES

Below is a non-exhaustive list of tasks that Contractor must perform if ordered by the Government, and which must be performed at the Contractor’s plant, field sites, FAA Logistics Center (FAALC) or other locations:

a. Provide assistance during the installation of any RVR unit;

b. Conduct special RVR field and/or classroom training which the Contractor is qualified to provide;

c. Adding, moving, and changing equipment at field sites. This includes the disassembling and reassembling of the DPU inside an FAA facility;

d. Provide technical personnel and support during meetings at field sites and other Government-designated locations;

e. Provide on-site RVR technical support including, but not limited to, interface testing and software functional testing;

f. Provide on-site RVR troubleshooting of system failures or performance and/or functional anomalies;

g. Manufacture and deliver minor hardware elements of the RVR system to the Government;

h. Provide technical support including, but not limited to, the development and testing of an RVR equipment component; and

i. Deliver to FAA a results report including any analysis or lessons learned for any engineering services rendered.

C.3.12.2 CONTRACTOR REPAIR SERVICES

The Contractor must perform equipment repair services as a result of an FAA issued delivery or task order. The Contractor must repair RVR LRUs and components that are damaged by other than routine failure occurrences to serviceable operation conditions (e.g., lightning strikes, technician error, water damage, etc.). The Contractor must provide RVR troubleshooting of system failures or performance and/or functional anomalies as a result of a repair task order. If requested by the Government, the Contractor must deliver to FAA a results report including a synopsis of the issue, likely cause(s) analysis, recommendation, and lessons learned for any repair services rendered within 14 calendar days of repair.

CDRL: Contractor Repair Results Report

C.3.12.3 MAINTENANCE SUPPORT

The Contractor must provide software support to the FAA Operational Support (AOS) personnel located in Oklahoma City, OK. The software support must include a report to be delivered annually to the Program Manager. The report must provide documentation for RVR verification and software development activities and updates.

CDRL: System Software Report

C.3.13 RVR PARTS

C.3.13.1 PARTS OBSOLESCENCE

The Contractor must provide parts obsolescence management to ensure the availability of the RVR system. Obsolescence management must include parts and components beyond the LRU level. When necessary, obsolescence management must identify alternate parts beyond the LRU level throughout the life of the RVR. An obsolescence forecast, including alternative parts, must be included in Program Status Reports (PSRs) delivered quarterly.

The Contractor must notify the QRO and COR in writing when any of the following conditions exist:

a. An item is no longer manufactured and cannot be procured;

b. An item is no longer repairable because the piece parts are no longer available from vendors;

c. Notification from a sub-vendor when they no longer intend to support a part; and

d. End-of-life notices for items that are received from the manufacturer.

C.3.13.2 SYSTEM REFRESH AND UPGRADE

The Contractor is encouraged to recommend routine updates, upgrades, design modifications, corrections, and improvements to the CO or designee.