SIR Section C.pdf

PART I – SECTION C – SIR #: DTFAWA-16-R-00016

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 Equipment Description

C.3.1.1 RRCIU

C.3.1.2 RRCIU Kits

C.3.2 Production Units C.3.3 Program Management

C.3.3.1 Program Control C.3.3.1.1 Program Management Plan C.3.3.1.2 Program Status Report

C.3.4 Meetings, Reviews and Conferences C.3.4.1.1 Post Award Conference (PAC) C.3.4.1.2 Program Overview Meeting C.3.4.1.3 Technical Interchange Meeting C.3.4.1.4 Provisioning Conference

C.3.5 Configuration Management Program C.3.5.1 Configuration Management (CM) Planning

C.3.5.1.1 Configuration Control C.3.5.1.2 Configuration Status Accounting C.3.5.1.3 Configuration Item (CI) Identification C.3.5.1.4 Engineering Change Proposals (ECPs) C.3.5.1.5 Request for Deviation and Waivers C.3.5.1.6 Verification Audit

C.3.6 Test and Evaluation (T&E) C.3.6.1 Test Program

C.3.6.1.1 Production Acceptance Test (PAT) C.3.7 Technical and Programmatic Risk C.3.8 Engineering Support Services

C.3.8.1 Parts Obsolescence C.3.8.2 Asset Identification Report

C.3.9 Integrated Logistic Support (ILS) C.3.9.1 Integrated Logistic Support Management Team (ILSMT) C.3.9.2 Logistics Management Information (LMI) C.3.9.3 Supply Support

C.3.9.3.1 Site Spares C.3.9.3.2 Depot Spares ii

C.3.9.4 Technical Data Package (TDP) C.3.10 Definitions C.3.11 Copyrighted Materials C.3.12 Acronyms

PART I – SECTION C Page 1

C.1.0 OVERVIEW

The Federal Aviation Administration (FAA) needs to acquire Remote Radio Control Interface Units (RRCIUs) to satisfy requirements for installation within the National Airspace System (NAS). The RRCIU provides an interface between radio control receivers and the following runway approach lighting systems: Medium Intensity Approach Lighting System with Runway Alignment Indicator Lights (MALSR);

Precision Approach Path Indicator Lights (PAPI); Runway End Identification Lights (REILS);

Omnidirectional Approach Lighting System (ODALS); and Visual Approach Slope Indicator (VASI). The primary function of the RRCIU is to convert DC and AC signals into the AC lines of voltages so that the lighting system can be controlled.

This Statement of Work (SOW) defines the effort required for acquisition of the RRCIU, Type FA-16100, defined in the RRCIU Performance Specification, FAA-E-2663a and RRCIU kits. Hereafter in this SOW, any reference to RRCIU (unless explicitly stated otherwise) means the RRCIU Type FA-16100, as specified in FAA-E-2663a.

C.1.1 Scope

The 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 RRCIUs.

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 versions of the following documents are the latest version existing as of the contract date.

C.2.1.1 Federal Aviation Administration (FAA) Documents

FAA Order 1370.82 Information Systems Security Program

FAA Order 1600.6C Physical Security Management Program

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-2663a Performance Specification Interface Unit, MALSR Remote Control

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

PART I – SECTION C Page 2

Drawing AE-D-1457-1 RRCIU Program Work Breakdown (PWB) Assembly Reference (with Parts List)

Drawing AE-D-1457-2 RRCIU PWB Parts Location (with Parts List)

Drawing AE-D-1457-3 RRCIU PWB Schematic

Drawing AE-D-1457-4 RRCIU PWB Component Side

Drawing AE-D-1457-5 RRCIU PWB Solder Side

Drawing AE-D-1457-6 RRCIU PWB Component Side Solder Mask

Drawing AE-D-1457-7 RRCIU PWB Solder Side Solder Mask

Drawing AE-D-1457-8 RRCIU PWB Drill and Trim

Drawing AE-D-1457-9 RRCIU PWB Silkscreen

Drawing AE-D-1457-20 RRCIU Cabinet Assembly (with Parts List)

Drawing AE-D-1457-21 RRCIU Cabinet Assembly

Drawing AE-D-1457-22 RRCIU Cabinet Assembly Interconnect Diagram

Drawing AE-D-1457-23 Plate Assembly Side View

Drawing AE-D-1457-24 Plate Assembly Bottom View

Drawing AE-D-1457-25 RRCIU Plate Drill & Dimension

Drawing AE-D-1457-26 Part Details, Rectangular Standoffs

Drawing AE-D-1457-27 Power Supply

Drawing AE-D-1457-28 Schematic Decal and I.D. Plate Layout

Drawing AE-D-1457-29 Door Schematic Decal

Drawing AE-D-1457-30 RRCIU Electrical Schematic

Drawing AE-D-1457-31 RRCIU Identification Plate

Drawing AE-D-1457-32 Interconnect Cable

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_title=Special%2 0Topics

TI 6850.91 Technical Instruction Book Remote Radio Control Interface Unit Type FA- 16100

C.2.1.2 Military Standards, Specifications, and Handbooks

MIL-P-55110H Printed Wiring Boards, Rigid, General Specification

MIL-HDBK-61A Configuration Management Guidance

MIL-HDBK-881 Work Breakdown Structure http://fast.faa.gov/ http://fast.faa.gov/SafetyManagement.cfm?p_title=Functions

PART I – SECTION C Page 3

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

C.2.1.3 Other Documents

ANSI/ISO/ASQC

Q9001-2000

Quality Systems – Requirements

ANSI/ISO/ASQC-

Q9003-1994

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 43 rd 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.

PART I – SECTION C Page 4

Requests for copies of documents not covered in the preceding paragraphs must be addressed to the RRCIU 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. FAA Engineering (Drawing) Package

c. TI 6850.91;

d. FAA-E-2663a, Performance Specification Interface Unit, MALSR Remote Control;

e. FAA Specifications;

f. FAA Standards and Orders;

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 RRCIUs and RRCIU kits, IAW this SOW.

The Government will provide the contractor with the following Government-Furnished Information (GFI) that contains “build-to-print” drawings, FAA-E-2663a specification, Production Acceptance Test (PAT) Report, field installation procedures and Technical Instruction Book 6850.91.

The 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 Equipment Description

The Contractor must build the RRCIU Type FA-16100 and RRCIU Kits.

C.3.1.1 RRCIU

If ordered by the Government, the Contractor must build the RRCIU Type FA-16100 (Contract Line Item Number (CLIN) 001, 1001, 2001, 3001, and 4001) IAW the Government-provided drawings, FAA-E- 2663a specification, and TI 6850.91. The RRCIU must consist of the following items listed below:

PART I – SECTION C Page 5

Quantity Description Type Number

1 Remote Radio Control Interface Unit FA-16100

1 Site spares kit TBD

2 Technical Instruction Book TI 6850.91

1 Certificate of Compliance

C.3.1.2 RRCIU Kits

If ordered by the Government, the contractor must develop RRCIU kits (CLIN 002) IAW the Government-provided drawings. These kits must include backplate, adapter plate for the Disan Power Supply, nameplate, circuit boards without relays, and door decals. The RRCIU kit must consist of the following items listed below:

1 Remote Radio Control Interface Unit kits

1 Site spares kit TBD

2 Technical Instruction Book TI 6850.91

1 Field Installation Instructions

1 Certificate of Compliance

C.3.2 Production Units

If ordered by the Government, the Contractor must manufacture and test RRCIU Production Units (CLIN

003) IAW Government-provided drawings, FAA-E-2663a specification, and TI 6850.91. The packing, packaging, and shipment requirements must be IAW Section D of this contract. The RRCIU production unit must consist of the following items listed below:

1 Remote Radio Control Interface Unit FA-16100

1 Production Acceptance Test Report

C.3.3 Program Management

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 Contractor must have the experience and resources necessary to ensure efficient and timely program execution.

C.3.3.1.1 Program Management Plan

An acceptable Project Management Plan (PMP) will be incorporated after award of the contract as specified in CDLR A001.

C.3.3.1.2 Program Status Report

If ordered by the Government, the Contractor must provide Program Status Reports (PSRs) IAW CDRL AOO2 (CLINs 004, 1004, 2004, 3004, and 4004) and Data Item Description (DID) AOO2 to the CO or COR on a quarterly basis. PSRs must include subcontract items and services. They must also 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. The PMP must include but are not limited to:

PART I – SECTION C Page 6

Summary of Project Status;

a. Issues and Concerns;

b. Risk Analysis;

c. Technical Performance; and

d. Network Logic Schedule.

CDRL AOO2 Program Status Report

C.3.4 Meetings, Reviews and Conferences

The Contractor may be required to 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 15 participants.

C.3.4.1.1 Post Award Conference (PAC)

If ordered by the Government, the Contractor must hold a Post Award Conference (PAC) (CLIN 005) at the Contractor’s facility in conjunction with a Logistics Guidance Conference (LGC) related to the RRCIU and RRCIU Kit. The Contractor must prepare a PAC briefing packaging and present their approach to accomplishing logistics management task(s). The Contractor must support the conference with the required resources to include the briefing, briefing documentation, and staffing necessary to discuss all support considerations. The LGC must clarify provisioning requirement and issues, provisioning deliverables, data requirements, technical documentation and data for provisioning. The CO or COR will coordinate with the Contractor to set the date of the PAC. The PAC must be 3-calendar days. The Contractor must transmit the PAC documents to the CO or COR via electronic mail at least 21-calendar days prior to the PAC. During the PAC, the Contractor must 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. Technical Data Package (TDP);

4. Support and test equipment;

5. Packaging and shipping;

6. Manpower and Personnel; and

7. Training.

PART I – SECTION C Page 7

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 A003 Meeting Agenda CDRL A004 Meeting Minutes

C.3.4.1.2 Program Overview Meeting

If ordered by the Government, the Contractor must host and conduct a maximum of five Program Overview Meetings (POMs) at the Contractor’s facility (CLIN 006, 1006, 2006, 3006, and 4006). 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 2-calendar days in length.

CDRL A003 Meeting Agenda CDRL A004 Meeting Minutes

C.3.4.1.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 (CLIN 007, 1007, 2007, 3007, and 4007) to discuss specific technical activities, including but not limited to: studies, test plans, risk, test results, design issues including human engineering, technical problems, training issues, logistics issues, implementation concerns, verification audit, and to monitor the technical progress of the contract. The CO or COR will determine the meeting location. The meeting duration, 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

PART I – SECTION C Page 8 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 2-calendar days in length.

CDRL A003 Meeting Agenda CDRL A004 Meeting Minutes

C.3.4.1.4 Provisioning Conference

If ordered by the Government, the Contractor must host and conduct a maximum of one Provisioning Conference (CLIN 008) at the Contractor’s facility. The Provisioning Conference (PC) 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 RRCIU (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.5 Configuration Management Program

C.3.5.1 Configuration Management (CM) Planning

If ordered by the Government, the Contractor must submit a Configuration Management Plan (CMP) (CLIN 009) 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 Project 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.

CDRL C001 Configuration Management Plan

PART I – SECTION C Page 9

C.3.5.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 RRCIU program life cycle.

C.3.5.1.2 Configuration Status Accounting

At the Government’s request, the Contractor must maintain the configuration baseline for the RRCIU 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.5.1.3 Configuration Item (CI) Identification

The Contractor must maintain configuration control of the RRCIU 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.5.1.4 Engineering Change Proposals (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. Upon receiving classification concurrence, the Contractor must formally submit all ECPs designated Class I to the CO IAW MIL-HDBK-

PART I – SECTION C Page 10

61A, Section 6.2. 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 RRCIU 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 RRCIU are considered Class II changes. Class II changes are to be specified for local approval by the QRO.

The Contractor must submit to the CO and COR all changes to documentation resulting from an ECP.

The Contractor must review any impacts and/or updates as a result of an ECP request to the following documentation:

a. Logistics Management Information(LMI) Data;

b. Technical Data Package (TDP);

c. Technical Instruction Manual; and the

d. 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.5.1.5 Request for Deviation and Waivers

The Contractor must submit a request for deviation or waiver to the CO or COR prior to departing from the approved baseline for a specific number of units or 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 RRCIU baseline documentation.

C.3.5.1.6 Verification Audit

If ordered by the Government, the Contractor must host and conduct a verification audit (CLIN 010) to validate the RRCIU design and function. The verification audit must be conducted on the initial production units only. Any approved ECP changes must be incorporated prior to the audit, and any differences (with respect to the Type FA-16100 RRCIU) must be documented with an explanation 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 contained in paragraph C.3.5.1.4. The verification audit must be planned for no more than 1-calendar day in length.

C.3.6 Test and Evaluation (T&E)

C.3.6.1 Test Program

Any Test and Evaluation (T&E) efforts must demonstrate that the RRCIU meet the performance requirements, as stated in FAA-E-2663a.

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

PART I – SECTION C Page 11

The Contractor must notify the COR, QRO and Test and Evaluation Team ANG-E63 prior to the start of testing. The Contractor must provide the COR QRO and Test and Evaluation Team ANG-E63 with copies of data within 7-calendar days of test completion.

C.3.6.1.1 Production Acceptance Test (PAT)

The Contractor must conduct Production Acceptance Testing (PAT) on every unit IAW Government-provided Production Acceptance Test Report. The Contractor must provide a test power supply and install a set of test relays into the circuit board to test the RRCIU kit. The Government may elect to witness these tests. The Contractor must be notified at least 14-calendar days in advance of each of these tests. The Contractor must complete the Government-provided Production Acceptance Test Report for Government review and approval.

C.3.7 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.8 Engineering Support Services

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

Included are a variety of tasks at the Contractor’s plant, field sites, FAA Logistics Center (FAALC), or other locations. This could include, but not be limited to the following:

a. Providing assistance during the installation of any RRCIU unit;

b. Conducting special RRCIU training which the Contractor is qualified to provide;

c. Adding, moving, and changing equipment at field sites;

d. Providing technical personnel and support during meetings at field sites and other

Government-designated locations;

e. Repairing RRCIU LRUs that are damaged by other than routine failure occurrences to serviceable operation conditions (e.g., lightning strikes, technician error, water damage, etc.);

f. Providing on-site RRCIU technical support including, but not limited to, interface testing and software functional testing to the Government during Government testing;

g. Providing on-site RRCIU troubleshooting of system failures or performance and/or functional anomalies;

h. Manufacturing and delivering minor hardware elements of the RRCIU system to the

Government; and

i. Providing technical support including, but not limited to, the development and testing of an RRCIU equipment interface.

The Contractor’s personnel provided must have experience on RRCIUs and must have knowledge of the system’s hardware, software, firmware, and functional and performance features sufficient to perform the assigned task(s). The personnel and the material needed to perform the task(s) must be available at the locations specified by the Government within 72 hours of notification.

PART I – SECTION C Page 12

When ordered by the Government, the Contractor must also perform site surveys, prepare site engineering reports, civil calculations, designs, construction plans and specifications, which may result in the preparation of data deliverables. The Contractor must also provide other assistance required to support turnkey efforts.

C.3.8.1 Parts Obsolescence

The Contractor must provide parts obsolescence management to ensure the availability of parts over the life cycle of the RRCIU.

The Contractor must notify the COR 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.8.2 Asset Identification Report

The Contractor must use the appropriate bar code symbology standard, as described in the Asset Identification Specification document, to identify contract assets at the Lowest Replaceable Unit (LRU) level. For each LRU barcoded asset, the contractor must provide the following types of information:

a. Bar code/pin number;

b. Item description;

c. Manufacturer’s part number;

d. Manufacturer’s serial number;

e. Manufacturer’s Commercial and Government Entity (CAGE) Code;

f. Year manufactured; and

g. Cost.

The Contractor must also provide system-level data, such as:

a. Major system components or enclosures;

b. Component/enclosure descriptive data;

c. System configuration; and

d. Any other associated data.

LRU’s may consist of circuit boards, modules, cable assemblies, motors, power supplies, etc. Ancillary equipment may consist of personal computer data terminals, displays, test rigs, etc. System components or enclosures may consist of cabinets, mounting assemblies, waveguides, etc.

The Contractor must use an FAA asset management system or equivalent Commercial Off-the-Shelf (COTS) package to manage the contract asset detail data for each category of asset from point of acquisition to production and delivery.

If ordered by the Government, the Contractor must provide a report (CLIN 012) IAW CDRL G001 that must contain a listing of all assets that have been identified with a bar code label. The report must include all of the data elements considered for bar coding as specified in the DID.

CDRL G001 Asset Identification Report

PART I – SECTION C Page 13

C.3.9 Integrated Logistic Support (ILS)

C.3.9.1 Integrated Logistic Support Management Team (ILSMT)

A joint FAA/Contractor-sponsored ILS Management Team (ILSMT) for the RRCIU system must be established to serve as the primary management vehicle for monitoring the status of the ILS program.

The Contractor must fully participate in and support the ILS meetings. The FAA will designate a chairperson for the ILSMT. The ILSMT provides a means for coordinating and monitoring logistics-related schedules, contract performance, and reviews. Any ILS topics/issues will be discussed during the POM or in the PSR if a POM is not held.

C.3.9.2 Logistics Management Information (LMI)

If ordered by the Government, the Contractor must deliver to the FAA the data products (CLIN 013) identified in CDRL L001, in accordance with GEIA-STD-0007 and the LMI Data Worksheet. The data products must represent the physical top-down breakdown system design configuration including system, subsystem, components, assemblies, subassemblies, support and test equipment required for the RRCIU. Data submitted must be to the component level for all developmental items and to the LRU level for all COTS and nondevelopment items. Any modification to a COTS item may disqualify it as COTS, and may require LMI Data to be modified to an applicable component level. The FAA will determine the level of LMI data required for COTS modified items. Data for temporary items are not required. The Contractor must update and maintain the LMI data and engineering drawing for the duration of the contract period including all option years. The Contractor must also provide an updated LMI data product at least 30-calendar days before end of the contract.

CDRL L001: Logistics Management Information (LMI) Data Products

C.3.9.3 Supply Support

Supply support includes all spare components and repair parts needed to support the mission of the RRCIU. Supply support also covers distribution of material, and personnel associated with the acquisition and maintenance of spare/repair part inventories of support locations. Consideration must include each maintenance level and each geographical location where spare/repair parts are distributed and stocked.

RRCIU component and parts are subjected to Government inspection—as outline in FAA Contract Clause 3.10.4.2, Inspection of Supplies-Fixed Price.

C.3.9.3.1 Site Spares

There must be one set of site spares included with each deliverable RRCIU. Site Spares must be delivered in accordance with sections D and F. The site spares must consist of one of each type of replaceable module and printed circuit card in the RRCIU. If the equipment contains more than one single replaceable module or card, only one spare module or card must be provided. Each replaceable module and printed circuit card must pass all required Production Acceptance Tests. If ordered by the Government, the Contractor must provide a recommended site spares, expendable and consumable items list (CLIN 014) to the Government IAW CDRL L002.

PART I – SECTION C Page 14

CDRL L002: Recommended Site Spares

C.3.9.3.2 Depot Spares

After the Provisioning Conference and depot spares prices are negotiated, if ordered by the Government, the Contractor must provide depot spares (CLIN 015, 1015, 2015, 3015, and 4015). 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) Destination to the following address:

Mike Monroney Aeronautical Center

FAA Logistics Center

6500 South MacArthur Blvd

Oklahoma City, OK 73125

Mark for: Operating Stock

C.3.9.4 Technical Data Package (TDP)

If ordered by the Government, the Contractor must provide a TDP (CLIN 016) in accordance with MIL- STD-31000, as tailored by CDRL L003. The TDP must contain a drawing tree with a reference designator, production drawings and associated lists, commercial drawings and associated lists, PCB (print circuit board) master pattern, special inspection equipment operating instructions, special inspection equipment calibration, test fixture, procedures, and special tooling drawings and associated lists. The Contractor must provide an index of all items in the TDP, by part number, where applicable. When delivered, the TDP must include all data necessary to enable the FAA to repair or re-procure (competitively from other contractors) all shop replaceable units and LRUs required under the contract.

The data in the TDP must be suitable for the procurement of items identical to those delivered and accepted under the contract. They must include all design and manufacturing information required to produce those items. The TDP must be provided to the FAA without any restrictions—such as proprietary stamp on its use by the Government or any Government contractor or subcontractor—notwithstanding any other provisions of the contract. The TDP must be under Configuration Management throughout the life of the contract, including all option years.

CDRL L003: Technical Data Package

C.3.10 Definitions

Line Replaceable Unit (LRU). An LRU is the lowest unit to be replaced within the system during site maintenance. It is a separate, installable, physical package performing a single function or a group of closely related functions.

Repairable. The condition of an item that can be returned to service after repair or rework IAW 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 FAALC directives.

Serviceable. The condition of an item in a good state of preservation that can be placed in service without repair IAW applicable manufacturer's overhaul limits and instructions and/or pertinent standards of the FAA.

Test. 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 FAA-authorized changes in procedures and limits.

PART I – SECTION C Page 15

C.3.11 Copyrighted Materials

The Contractor must ensure that all copyrighted materials, registered documents, drawings, software, or other materials delivered to the FAA is free of all encumbrances prohibiting or limiting reproduction that includes, but are not limited to, proprietary stamps. All material developed for the FAA will be the sole property of the FAA, and may not be used by the Contractor for any purpose other than in support of or as specified in the contract. At final delivery, the Contractor must provide written verification that the above requirements have been met.

C.3.12 Acronyms

Acronym Definition

ANSI American National Standards Institute

CDRL Contract Data Requirements List

CD-ROM Compact Disk Read-Only Memory

CI Configuration Item

CLIN Contract Line Item Number

CM Configuration Management

CMP Configuration Management Plan

CO Contracting Officer

COR Contracting Officer’s Representative

COTS Commercial-off-the-shelf

CS Contract Specialist

DID Data Item Description

DODSSP Department of Defense Single Stock Point

ECO Engineering Change Order

ECP Engineering Change Proposal

EULA End-User License Agreement

FAA Federal Aviation Administration

FAALC FAA Logistics Center

FAST FAA Acquisition System Toolset

GFE Government-Furnished Equipment

IAW In Accordance With

ICD Interface Control Document

IDS Item Development Specification

ISO International Organization for Standardization

LMI Logistics Management Information

LRU Line Replaceable Unit

NAS National Airspace System

NDI Non-Development Item

PART I – SECTION C Page 16

Acronym Definition

NIMS NAS Infrastructure Management System

PAC Post Award Conference

PAT Production Acceptance Test

PC Personal Computer

PM Program Manager

PMR Program Management Review

POM Program Overview Meeting

PSR Program Status Report

QA Quality Assurance

QRO Quality Reliability Officer

QSP Quality System Plan

RRCIU Remote Radio Control Interface Unit

SDD Software Design Description

SER System Engineering Review

SEMP System Engineering Management Plan

SIE Sensor Interface Electronics

SNMP Simple Network Management Protocol

SOW Statement of Work

SPS Software Product Specification

SVD Software Version Description

T&E Test and Evaluation

TDP Technical Data Package

TIM Technical Interchange Meeting

TRACON Terminal Radar Approach Control

VRTM Verification Requirements Traceability Matrix

END OF SECTION C