NEXCOM V2 Section C.pdf

DTFAWA-12-C-00040

Modification 0068

Page C-1

PART I – SECTION C

STATEMENT OF WORK

Section C

Statement of Work

Page C-2

TABLE OF CONTENTS

C.1. PURPOSE

C.2. APPLICABLE DOCUMENTS

C.2.1 Specifications C.2.2 Standards C.2.3 Orders

C.3. REQUIREMENTS

C.3.1 CONTRACT MANAGEMENT

C.3.1.1 Program Management Plan C.3.1.1.1 Meetings C.3.1.2 Monthly Financial Progress Status Report C.3.1.3 Performance Based Management System C.3.1.3.1 Contract Work Breakdown Structure C.3.1.3.2 Integrated Master Schedule C.3.1.3.3 Performance Report C.3.1.3.4 Contractor Integrated Baseline Review

C.3.2 QUALITY ASSURANCE

C.3.3 CONFIGURATION MANAGEMENT

C.3.3.1 Configuration Identification C.3.3.2 Composition of Baselines C.3.3.3 Configuration Control C.3.3.3.1 Physical Configuration Audit (PCA) Documentation C.3.3.3.2 Contractor Master Test Plan (CMTP), Test Procedures and Documentation C.3.3.3.3 Radio Software and Maintenance Data Terminal (MDT) Software C.3.3.3.4 LMI Data Products C.3.3.4 Configuration Status Accounting C.3.3.5 Configuration Audits

C.3.4 EQUIPMENT

C.3.5 TEST

C.3.5.1 Point of Contact C.3.5.2 Contractor’s Master Test Plan C.3.5.3 Test Management and Planning C.3.5.4 Test Documentation C.3.5.5 Operational Test (OT) C.3.5.5.1 Operational Test Equipment C.3.5.5.2 Operational Test Support Services C.3.5.5.3 Factory Acceptance Test (FAT)

Page C-3

C.3.5.5.4 Production Acceptance Test (PAT) C.3.5.5.5 Production Unit Test (PUT)

C.3.5.5.6 RESERVED

C.3.6 LOGISTICS

C.3.6.1 Point of Contact C.3.6.2 National Airspace Integrated Logistics Support Program C.3.6.2.1 National Airspace Integrated Logistics Management Team (NAILSMT) C.3.6.2.2 Integrated Support Plan (ISP) C.3.6.3 Maintenance C.3.6.3.1 Warranty and Non-Warranty Repairs C.3.6.3.2 Monthly Repair Status Reports C.3.6.4 Technical Support Services C.3.6.4.1 Telephone Communications Line C.3.6.5 Long Term Supportability Data Package (LTSDP) C.3.6.5.1 Long Term Supportability Data Package (Escrow Account) C.3.6.5.2 Long Term Supportability Data Package Inspection C.3.6.5.3 Procurement of Long Term Supportability Data Package C.3.6.6 Logistics Management Information C.3.6.6.1 Hardware Breakdown Structure C.3.6.6.2 LMI Data Reviews C.3.6.6.3 LMI/Provisioning Guidance Conference C.3.6.6.4 Provisioning Conference C.3.6.6.5 Cataloging C.3.6.7 Depot Spares C.3.6.8 Tools and Test Equipment C.3.6.9 Spare Parts C.3.6.9.1 Spare Parts-Peculiar C.3.6.10 Bar Code Asset Tracking System C.3.6.10.1 General Requirements C.3.6.10.1.1 Identification Markings C.3.6.10.1.2 Warranty Markings C.3.6.10.1.3 Electrostatic Discharge Sensitive (ESD) Devices C.3.6.11 Bar Code Markings C.3.6.11.1 Individual Item Marking Requirements for LRU C.3.6.11.2 Applying Identification Bar Codes on Containers C.3.6.11.2.1 Human Readable Interpretation (HRI) C.3.6.11.3 Production, Warranty, and Repair Data Requirements C.3.6.11.4 FAA Scanning Process C.3.7 TECHNICAL INSTRUCTION BOOKS (TIBs)

Page C-4

C.3.7.1 Point of Contact C.3.7.2 Format C.3.7.3 Technical Data C.3.7.4 TIB Description

C.3.7.5 RESERVED

C.3.7.6 Operational Test and Second Level Engineering Support Familiarization Package

C.3.7.7 RESERVED

C.3.8 TRAINING

C.3.8.1 Training Conferences and Meetings C.3.8.2 Task and Skills Analysis (TASA) Report C.3.8.3 Training Development Plan C.3.8.4 Course Design Guide C.3.8.5 Classroom Training C.3.8.6 Enhanced Hands-On Training (EHOT) Written Examination C.3.8.7 Demonstration of Proficiency (DoP) Written Examination C.3.8.8 NEXCOM Segment 2 Radios Correspondence Study Course C.3.8.9 Theory of Operations By-Pass Examination C.3.8.10 On-the-Job Training (OJT) Package C.3.8.11 Performance Examination C.3.8.12 Contractor’s Presentation/Course Walk-Through C.3.8.13 Operational Tryouts C.3.8.14 First Course Conduct

Figures

Figure 3.6.11a Examples of Barcode Labeling generated with 2D Data matrix symbology

Tables

Table C.3.8-1 Delivery and Certification Path Matrix

Attachments

Attachment A - Contract Award to In-Service Decision Flow Chart

Page C-5

Addendums

PART II – ADDENDUM TO SECTION C – ACCEPTED VHF/UHF RADIO

REQUIREMENTS

PART III – ADDENDUM TO SECTION C – STATEMENT OF WORK FOR BLOCK 1

CHANGES

PART IV – ADDENDUM TO SECTION C – PRODUCT DESCRIPTION FAA-E-3014

REQUIREMENT CHANGES FOR BLOCK 1

PART V – ADDENDUM TO SECTION C – PCA DOCUMENT VERSIONS_06-19-2014

Page C-6

C.1. PURPOSE

This Statement of Work (SOW) defines the tasks required for the contractor to perform as defined in the Very High Frequency (VHF) and Ultra High Frequency (UHF) Radio Product Descriptions. The Contract Data Requirements List (CDRL) defines the products to be delivered to the Federal Aviation Administration (FAA) resulting from the tasks defined in this SOW.

The contractor shall provide all necessary equipment; engineering; logistics support;

maintenance/operator training; spares provisioning and maintenance program; and provide the documentation for implementation and operation for the receivers and transmitters.

It is important that the FAA work with the contractor to achieve an In-Service Decision so that the various hardware and logistics requirements are met. Attachment A contains a chart showing the process between Contract Award and the In-Service Decision.

C.2. APPLICABLE DOCUMENTS

The following documents are in effect on the date as stated and form a part of this SOW and may be downloaded at http://ato-p.se-apps.faa.gov/faastandards/FAADocs.htm.

C.2.1 Specifications

FAA:

FAA-D-2494 Technical Instruction Book Manuscript: Electronic, Electrical, and Mechanical Equipment, Requirements for Preparation of Manuscript and Production of Books

FAA-E-3014 NEXCOM II Very High Frequency (VHF) and Ultra High

Frequency (UHF) Receivers and Transmitters

FAA-G-2100H Electronic Equipment, General Requirements

Page C-7

C.2.2 Standards

FAA-STD-021 Configuration Management, Contractor Requirements

FAA-STD-024 Preparation of Test Plans and Procedures

FAA-STD-028C Contract Training Programs

MIL:

MIL-PRF-49506 Logistics Management Information

C.2.3 Orders

3000.57 Air Traffic Organization Technical Operations Training and Personnel Certification

In the event of conflict between the documents referenced herein and this SOW, the contents of this SOW shall take precedence.

C.3. REQUIREMENTS

The tasks described herein shall be fully integrated to ensure their efficient and timely execution.

The data to be delivered by the contractor as a result of performing the tasks prescribed by this SOW are specified in the CDRL.

C.3.1 CONTRACT MANAGEMENT

The contractor shall provide the required personnel and facilities to manage and administer the work required under the contract. Technical management, planning, quality assurance, configuration management, scheduling, and coordination activities are required. These activities include the internal management within the contractor's organizational and management activities necessary for reporting progress, demonstrating results, and coordinating technical activities with the FAA.

Page C-8

C.3.1.1 Program Management Plan As ordered by the Government, the contractor shall maintain and update a Program Management Plan (CDRL-A004) that identifies all major and critical milestones and is supported by a risk analysis with appropriate mitigating factors identified.

C.3.1.1.1 Meetings The contractor shall prepare and deliver to the Government an agenda (CDRL-A001) prior to each conference and meeting, and minutes (CDRL-A002) subsequent to each scheduled conference and meeting. Contractor administrative support shall be provided only when meetings or conferences are held at the Contractor’s facility. Such support may consist of providing facilities, office equipment, and clerical support. Facilities with adequate accommodations shall be furnished for the Government team that will consist of a maximum of fifteen (15) representatives. The contractor shall participate in the following meetings at the Contractor’s facility in accordance with contract requirements:

a. Post Award Conference. The contractor shall plan, host, provide administrative support, and participate in a Post Award Conference (PAC) to be held at the contractor’s facility following contract award. The Government will determine the actual date of the PAC, which will occur no later than 60 days after the contract award date. During the PAC, the contractor shall brief their plans and schedule for satisfying each SOW requirement. The PAC shall also include a Provisioning Guidance Conference (PGC) and a Training Guidance Conference (TGC);

b. Functional Configuration Audit (FCA) (Para. C.3.3.5 herein);

c. Physical Configuration Audit (PCA) (Para. C.3.3.5 herein);

d. National Airspace Integrated Logistics Support (NAILS) Management Team

(NAILSMT) meetings (See Para. C.3.6.2.1 herein);

e. Integrated Baseline Review (IBR);

f. Program Management Reviews (PMRs). PMRs shall occur at least twice per year.

Additional PMRs requested by the Government will be ordered on a T&M basis. The focus of these meetings is on: Current program status/tasking; Technical problems/issues; Contract issues, schedules, data deliverables; Installation and integration issues; and Program cost/expenditure status.

g. Provisioning Conference (PC) (Para. C.3.6.6.4 herein);

C.3.1.2 Monthly Financial Progress Status Report The contractor shall furnish Monthly Financial Progress Status Reports (CDRL-A003) briefly stating the financial status of the contract. For each task order received the contractor shall state the not to exceed (NTE) value of the order and the costs incurred to date, both for the reporting

Page C-9 period and a cumulative amount. For purposes of this report, "incurred" means costs recorded on the books, and not voucher costs.

C.3.1.3 Performance Based Management System The Performance Based Management System (PBMS) is an internal management system which provides for reporting contract performance information to the Government. The Contractor will plan, schedule, budget, monitor, manage, and report performance to schedule applicable to the contract. The Contractor's internal PBMS serves as the single, formal, integrated reporting system that meets both the Contractor's internal management requirements and the requirements of the FAA for timely, reliable performance reporting information.

The Contractor must provide the reports specified in Section C.3.1.3 to the Government.

C.3.1.3.1 Contract Work Breakdown Structure The FAA will provide the Contractor a high-level framework for developing a complete Contract Work Breakdown Structure (CWBS). As ordered by the Government, the Contractor must generate and maintain a CWBS Dictionary for this effort based upon the general provisions of the contract, and IAW CDRL-A005 and CDRL-A006. The Contractor must extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement.

Contract modifications that modify, add, or delete work scope and Task Orders awarded under the contract must be incorporated into appropriate CWBS elements for work effort identification, definition, and procurement request relationships, as in the basic contract.

C.3.1.3.2 Integrated Master Schedule As ordered by the Government, the Contractor must develop, maintain, and submit an Integrated Master Schedule (IMS) IAW CDRL-A007. The IMS must be consistent with the CWBS.

The Contractor must manage the execution of the contract using the IMS as a day-to-day execution tool and periodically assess program progress in meeting program requirements. The Contractor must report on program progress consistent with the IMS at each program management review and at selected technical reviews.

The Contractor must revise the IMS, where necessary, to reflect current contract milestones and deliverables. The IMS will include all activities of the prime contractor, subcontractors, and dependencies on the Government. All contractor schedule information delivered to the Government or presented at program reviews shall originate from the IMS.

Page C-10

C.3.1.3.3 Performance Report The Contractor must submit a monthly Performance Report prepared IAW CDRL-A008. The Contractor must report summarized performance information at each program management review and at selected technical reviews.

Performance information should be reported by CLIN.

C.3.1.3.4 Contractor Integrated Baseline Review As ordered by the Government, the Contractor and Government shall conduct a baseline review of the IMS where the Contractor will walk through each WBS element and detail applicable resources and risks. The Contractor shall submit an initial draft of the IMS for the Government’s evaluation. Subsequent meetings will be scheduled as required to address Government comments. All IMS updates and actions will be mutually agreed upon.

C.3.2 QUALITY ASSURANCE

The contractor shall maintain a Quality System Plan (QSP) (CDRL-A009) in accordance with Section E of the Contract. Third party certification to International Standards Organization (ISO) standards is not required nor does such certification relieve the contractor of the requirement for submitting a QSP. The contractor shall operate under the approved QSP.

C.3.3 CONFIGURATION MANAGEMENT

As ordered by the Government, the contractor shall maintain and update a Configuration Management Plan (CDRL-B002) in accordance with FAA-STD-021. The contractor shall maintain a configuration management program on all configuration items in accordance with the contractor's Configuration Management Plan.

The contractor shall specify an individual who shall serve as a point of contact for all configuration management related issues.

The contractor shall maintain configuration control over work performed by subcontractors and vendors.

C.3.3.1 Configuration Identification The contractor shall maintain a system to identify, label, serialize, and mark Hardware Configuration Items (HWCI) to provide traceability from delivery of the first FAA production unit throughout the duration of the contract.

The contractor shall identify all documentation by titling, labeling, numbering, and cataloging.

The procedures used shall accomplish the following:

Page C-11

a) Identify specific versions of each element to which a document applies; and,

b) Uniquely identify the serial number, edition, change status, and other identification details of each document.

C.3.3.2 Composition of Baselines The equipment shall be defined by functional and product baselines.

a. The Functional Baseline shall be established at contract award by the product description and the Functional Configuration Audit (FCA).

b. The Product Baseline shall be established after successful completion of the Operational Test (OT) equipment testing and the Physical Configuration Audit (PCA).

C.3.3.3 Configuration Control The Contractor shall maintain procedures to accomplish configuration control, as defined in the Contractor's Configuration Management Plan. The Contractor shall extend configuration control to cover (1) Physical Configuration Audit (PCA) documentation, (2) the Contractor Master Test Plan (CMTP), manual and automated test plans, procedures and processes, (3) Radio firmware and application software and (4) Logistics Management Information (LMI) data products. The Contractor shall maintain a configuration control board to support baseline management. The Contractor shall maintain traceability, currency of the baselines, and consistency among all project documentation, as well as hardware and software.

The definition of “form, fit or function” is defined in MIL-HDBK-61A, “Configuration Management Guidance” as follows:

• Form. The shape, size, dimensions, mass, weight, and other physical parameters that uniquely characterize an item. For software, form denotes the language and media.

• Fit. The ability of an item to physically interface or interconnect with or become an integral part of another item.

• Function. The action or actions that an item is designed to perform.

At the option of the Government, the Contractor shall submit Design Change Notices (DCNs) or redlines (CDRL-B003) prior to implementation of the changes described in Sections C.3.3.3.1, C.3.3.3.3 and C.3.3.3.4. DCNs shall be submitted, effective with the Government’s acceptance of PCA, through the warranty period of the last receiver and transmitter units ordered under this contract. The Long Term Supportability Package (paragraph C.3.6.5 herein) shall also be updated to reflect all changes.

Page C-12

C.3.3.3.1 Physical Configuration Audit (PCA) Documentation The Contractor shall abide by the baseline as established with the Government’s acceptance of the PCA. The Contractor shall submit a DCN to the Government prior to implementing a modification that alters the form, fit or function of any PCA document, whether or not the change is at the Government’s request or direction. The Government will review the DCN and submit comments for clarification to the Contractor, if applicable, after receipt of a proposed modification. The Contractor shall respond to the Government’s comments after receipt. After comment resolution, the Government shall provide official notification of acceptance or rejection of the proposed modification outlined in the DCN.

Changes generated by the contractor after the baseline has been established, which provides the same form, fit and function, will not require formal approval by the Government. All other changes will require Government approval. The Government will review all changes requiring Government approval within thirty (30) days of submission of the change.

The Contractor shall submit a DCN when a modification to form, fit or function is proposed for any item in Part V – Addendum to Section C – PCA Document Versions_06-19-2014.

C.3.3.3.2 Contractor Master Test Plan (CMTP), Test Procedures and Documentation The Contractor shall maintain the Contractor Master Test Plan (CMTP) to reflect current manual and automated test procedures and software used to verify and validate compliance to FAA-E- 3014. The Contractor shall submit proposed modifications to the Government for review prior to their incorporation. The Contractor shall submit test procedures with redlines that clearly detail current and proposed test procedures and processes. (CDRL T001) The Government will review the redlines and submit comments for clarification to the Contractor after receipt of proposed changes. The Contractor shall respond to the Government’s comments after receipt. After comment resolution the Government will provide official notification of acceptance or rejection of the new plan or procedure.

The Contractor shall provide the configuration change control process described in this section to the following items:

Document #/Description 99-P57244R

• Contractor Master Test Plan (CMTP) for the NEXCOM Segment II UHF/VHF Radios 12-P57199R

• Factory Acceptance Test Procedures

• Contains procedures for verification of all requirements except those associated with Product

Acceptance Test (PAT) and Product Unit Test (PUT)

Page C-13

Document #/Description 12-P57387R

• CM-300/35(V2) PAT TAAP Automated Test, PAT TAAP Software SVD 12-P57562R

• CM 300/350 (V2) Series Transmitters Acceptance Test Procedure, Block 1 (ATP)

• Contains procedures for verification of PAT & PUT requirements for VHF & UHF transmitters 12-P57563R

• CM 300/350 (V2) Series Receivers Acceptance Test Procedure, Block 1 (ATP)

• Contains procedures for verification of PAT & PUT requirements for VHF & UHF receivers 98-P57385R

• CM-300/350 (V2) PAT TAAP Automated Test, TAAP Software Test Procedures 98-P57543R

• CM 300/350 (V2) System Tx STE Software Version Description (SVD)

• Software driving the transmitter STE test bed 98-57544R

• CM 300/350 (V2) System Rx STE Software Version Description (SVD)

• Software driving the receiver STE test bed 99-P57299R

• Receiver STE Test Limits File

• Frequencies used for receiver PUT & PAT 99-P57399R

• Transmitter STE Test Limits File

• Frequencies used for transmitter PUT & PAT

The Contractor shall incorporate this list into the CMTP and shall update the CMTP as new Production Acceptance Test (PAT) and Production Unit Test (PUT) procedures and software are added to maintain compliance to FAA-E-3014. The SOW shall be updated to reflect the addition of new acceptance test procedures.

New PAT and PUT procedures and software required to verify continued compliance to FAA-E- 3014 shall be subject to the change control processes described in this section.

C.3.3.3.3 Radio Software and Maintenance Data Terminal (MDT) Software After the software baseline has been established, the Contractor shall submit a DCN and trial version of the new software to the Government for review and approval.

The Contractor shall submit a DCN when any change to the following is proposed:

Modification P00086

Page C-14

Item #/Document #/Description

98-P57270

• CM-300 (V2) Receiver Software Version Document

• CM-300 (V2) Receiver Software Binary Image

98-P57271

• CM-300 (V2) Transmitter Software Version Document

• CM-300 (V2) Transmitter Software Binary Image

98-P57348R

• NEXCOM II Maintenance Data Terminal (MDT) SVD

• NEXCOM II Maintenance Data Terminal (MDT) Executable

To begin the DCN process the Contractor shall follow its Configuration Management Plan processes. During the Implementation Phase, the Contractor shall provide the Government with a trial version of the new software for evaluation. The Government shall provide comments to the Contractor on the suitability of the trial software. The Contractor shall correct software deficiencies noted by the Government, if applicable. The Government shall provide technical documentation required by the Contractor to exit the Implementation Phase and enter the

Verification Phase.

During the Verification Phase the Contractor and Government shall complete test processes determined during the Analysis Phase. The Government’s test process shall include evaluating the trial software at an operational site. As ordered by the Government, the Contractor shall provide technical services support to the Government to resolve anomalies that may arise during operational testing. The time frame for the Government’s operational testing shall not exceed eight months. The Government shall provide official notification of acceptance or rejection of the DCN. A rejection notice shall include the reasons why the trial software failed operational testing. Upon acceptance by the Government, the Contractor shall incorporate the Government approved Radio Software baseline in production. The Contractor shall deliver the Government approved Radio Software baseline via a final DCN in accordance with CDRL B003 for the

Government’s use in updating its fielded radios.

C.3.3.3.4 LMI Data Products

The Contractor shall submit a DCN when modifications are proposed for LMI data products.

The Government shall review the DCN after receipt and submit comments, if applicable. The

Contractor shall provide responses to Government inquiries after receipt. After receipt of the

Contractor responses, the Government shall assess the proposed LMI data product changes.

Page C-15

C.3.3.4 Configuration Status Accounting As ordered by the Government, the contractor shall generate Configuration Status Accounting Reports (CSARs) (CDRL-B001) which identify the configuration items changed and provide the supporting documentation reflecting these changes. The CSARs shall provide traceability of any change through the change control process.

C.3.3.5 Configuration Audits The contractor shall conduct Functional and Physical Configuration Audits at the contractor's facility. These audits shall include all equipment and documentation. The PCA shall include a review of the Long Term Supportability Package. After successful completion of the PCA, the product baseline shall be established.

C.3.4 EQUIPMENT

The contractor shall provide equipment that meets the requirements of FAA-E-3014, the Product Description for the VHF and UHF Receivers and Transmitters including requirements specified in the following Addendums to the SOW:

• Part II – Addendum to Section C – Accepted VHF/UHF Radio Requirements

• Part IV – Addendum to Section C – Product Description FAA-E-3014 Requirement

Changes for Block 1

The equipment provided under this contract shall be supportable by the contractor for the life of the contract.

C.3.5 TEST

C.3.5.1 Point of Contact The contractor shall specify an individual who shall serve as a point of contact for integration, control, coordination of all contractor and subcontractor testing, and support of Government testing.

C.3.5.2 Contractor’s Master Test Plan The contractor shall maintain the Contractor’s Master Test Plan (CDRL-T001), which shall serve as the overall test control document for the contractor’s program. The plan shall describe and clearly state the objectives of each test that the contractor will conduct to verify the radio requirements. The plan shall describe, for each phase, the contractor’s approach to be used in the conduct of each test. At the option of the Government, the contractor shall modify the Contractor’s Master Test Plan in accordance with CDRL-T001 and FAA-STD-024 (Preparation of Test Plans and Procedures).

Page C-16

C.3.5.3 Test Management and Planning The contractor shall establish a test and evaluation program to verify that the receivers and transmitters equipment meets the performance requirements as stated in FAA-E-3014, the product description.

C.3.5.4 Test Documentation As ordered by the Government, the contractor shall submit test plans, procedures, and actual receiver and transmitter test results for Factory Acceptance Test, the Production Acceptance Test and the Production Unit Test.

C.3.5.5 Operational Test (OT) OT is comprised of William J. Hughes (WJH) Technical Center/OT/Integration testing and FAA Engineering Field Service/OT/Field Familiarization testing at an FAA operational facility.

C.3.5.5.1 Operational Test Equipment The contractor shall provide receivers and transmitters as equipment for operational testing.

C.3.5.5.2 Operational Test Support Services As ordered by the Government, the contractor shall provide technical support services (paragraph C.3.6.4 herein) during the FAA's OT testing. The OT Support Services shall be provided at the WJH Technical Center for a period of 4-6 weeks, and at one (1) Operational Facility for a period of 2 weeks. OT does not start until completion of FAT, and the receipt of the FAT report.

C.3.5.5.3 Factory Acceptance Test (FAT) The purpose of the Factory Acceptance Test (FAT) is to demonstrate full functional compliance with the equipment Product Descriptions. The contractor shall conduct FAT on the configuration of the receivers and transmitters to be submitted for OT. FAT will be conducted at the contractor’s facility. The contractor shall provide all test equipment and special tools necessary to test the receivers and transmitters. The tests shall be conducted in the presence of the designated Government officer or representative who will validate the test results. (See Section I of this contract.)

C.3.5.5.4 Production Acceptance Test (PAT) The Production Acceptance Test (PAT) will be conducted on the first receiver(s) and transmitter(s) produced after successful completion of OT and permission for production has been received from the Government. PAT will also be conducted on every 200th unit of each type. While not intended to be as exhaustive as FAT, the test complement of PAT shall be as comprehensive as necessary to ensure that the units meet all requirements of the equipment

Page C-17

Product Description. PAT will be performed at the contractor’s facility. The Government may require PAT to be witnessed by a Government representative.

C.3.5.5.5 Production Unit Test (PUT) The purpose of the Production Unit Test (PUT) is to ensure that the production receivers and transmitters are equipped as required and are operational. PUT will be performed at the contractor’s facility on each receiver and transmitter prior to shipment to a Government site.

PUT need not be witnessed by a Government representative, however, electronic access to the test results shall be made available to the QRO while onsite. In addition, PUT data results shall be provided electronically to the FAA via secure transmission for each unit when shipped to include repaired items (reference section C.3.6.3.1, paragraph 5, item c).

C.3.5.5.6 RESERVED

C.3.6 LOGISTICS

C.3.6.1 Point of Contact The contractor shall specify an individual who shall serve as a point of contact for all logistics issues. This individual shall be at a management level equal to managers of engineering and other disciplines.

C.3.6.2 National Airspace Integrated Logistics Support Program The contractor shall establish and maintain a National Airspace Integrated Logistics Support (NAILS) Program in accordance with the requirements contained herein.

C.3.6.2.1 National Airspace Integrated Logistics Management Team (NAILSMT) The contractor shall participate as a member of the NAILS Management Team (NAILSMT) for the life of the contract. Participation shall consist of attending NAILSMT meetings and resolving problems identified by the NAILSMT. Meeting support shall include formulation/ submission of agenda items, reports of the contractor’s Integrated Logistics Support work, administrative support, and attendance by contractor personnel considered necessary by the contractor.

The contractor shall support the NAILSMT by submitting agenda items and ensuring participation (e.g., status briefings) of the contractor/sub-contractor personnel responsible for preparing the ILS deliverables identified in the NAILSMT meeting agenda. The Government will determine whether or not contractor’s sub-contractor participation in scheduled meetings shall be required.

Contractor administrative support shall be provided only when meetings or conferences are held at the Contractor’s facility. Such support shall consist of, but is not limited to providing

Page C-18 meeting/conference room, access to telephones, copy, and facsimile equipment, and clerical support for the recording and preparation of meeting minutes (CDRL-A001, CDRL-A002).

C.3.6.2.2 Integrated Support Plan (ISP) As ordered by the Government, the contractor shall deliver an Integrated Logistics Support (ISP) plan (CDRL-L001). The ISP shall detail the contractor’s plan for managing the ILS program for the program life cycle. The ISP will include the contractor’s logistics management information (LMI) plan. The contractor shall be responsible for ensuring that all sub-contractors and vendors comply with the ISP requirements.

C.3.6.3 Maintenance C.3.6.3.1 Warranty and Non-Warranty Repairs As ordered by the Government, the contractor shall furnish Warranty and Non-Warranty repairs in accordance with the provisions of this section for receiver and transmitter repairable items.

The contractor shall have the capability and expertise necessary to repair all repairable items and components. Non-Warranty repairs shall apply to each receiver and transmitter unit that is determined not to be under warranty.

Under this concept, the FAALC will manage the depot repair program and store exchange and repair (E&R) spares to support FAA sites.

The contractor shall furnish all qualified labor, supervision, materials, equipment, tools, appliances, and services to repair components of the equipment, to include the special tools and test equipment delivered by the contractor to support the equipment.

Repairable items and components will be shipped prepaid to the contractor facility for repair from the FAALC. The FAALC Item Manager will furnish shipping instructions for repaired items. The contractor’s return of repaired items and components shall be free on board (FOB) destination.

LRUs shall be repaired to restore them to a serviceable operating condition and shall meet the performance requirements of the Product Descriptions.

a. Contractor repair procedures shall include the following:

1) Cleaning, visual inspection, bench tests, and fault isolation;

2) Disassembly as necessary to identify and accomplish required repairs or to establish the item as serviceable;

3) Reassembly, calibration, functionality testing, acceptance inspection, and preparation for shipment.

Page C-21

b. Hardware maintenance support services including hardware maintenance, repair, restoration, validation, verification, and supply support. The contractor shall replace or repair all failed LRUs.

c. Other contractor support including clarification and upgrading of the Program Management Plan, Configuration Management Plan, Test Documentation, Integrated Support Plan, Training Materials Report, and other contractor documentation provided with their proposal.

C.3.6.4.1 Telephone Communications Line As ordered by the Government, the contractor, as part of their technical support service, shall maintain a telephone communications line for providing guidance to FAA personnel in resolving receiver and transmitter equipment engineering, maintenance, operation, and training problems.

This phone service shall be for the life of the contract.

C.3.6.5 Long Term Supportability Data Package (LTSDP) As ordered by the Government, the contractor shall assemble and submit for review and inspection by the Government, a Long Term Supportability Data Package (CDRL-L003). The Long Term Supportability Data Package shall be placed in a contractor established account and held in escrow by a third party, mutually agreed upon by the Government and contractor. The intent of the LTSDP is to ensure that in the event the Contractor refuses to continue support of the equipment or cessation of logistics support by the Contractor or Contractor bankrupts, the Government is not left without logistic support of the total system. This package shall include production drawings, associated lists and corresponding circuit descriptions narrating the production drawings, and master patterns to support follow-up sparing, equipment procurement, quality control, production and repair test procedures, and tolerances for each replaceable component. Production drawings, for each replaceable component, shall be provided to a level of definition sufficiently complete to enable a competent manufacturer to produce and maintain quality control of items to the degree that physical and performance characteristics interchangeable with those of the original design are obtained without resorting to additional product design effort, additional design data, or recourse to the original design activity.

Fabrication drawings of all production and depot level test beds and fixtures shall be provided.

Source code for all associated software and firmware shall be included within the LTSDP.

C.3.6.5.1 Long Term Supportability Data Package (Escrow Account) As ordered by the Government (CLIN 1204), the Contractor shall establish and maintain (including bear the cost) of a third party escrow account containing a complete set of the technical documentation, including proprietary information, for the VHF and UHF receiver and transmitter system. Changes approved under the Contractor's configuration management program shall be applied to the data in escrow. The escrow account shall include the complete LTSDP (as defined in the DID), which must show all versions and variants of all LRUs.

Page C-22

Additionally, the escrow account shall contain all software products necessary to view all file types that populate the LTSDP.

As ordered by the Government, the Contractor shall deliver an Escrow Account Index (CDRL-L004) CLIN 1206 of all the technical data contained in the escrow account. The Contractor shall maintain the index and deliver an updated index to the Government at the end of each month during which changes have been posted.

The Contractor shall document, in an escrow account data package validation report, that the data in the escrow account and elements thereof conform to the contractual requirements and accurately depict the hardware developed, produced and modified under the contract.

Contractor’s use of the data in the escrow to produce, inspect, and test the system hardware is considered acceptable evidence that the validation requirement has been met.

The Contractor shall identify sources for the repair, service, and replacement of the hardware and components used in the system, for the duration of the contract, including all options and the warranty obligations, and document the results in the LTSDP.

C.3.6.5.2 Long Term Supportability Data Package Inspection As ordered by the Government, the Contractor shall support a Long Term Supportability Data Package inspection (CLIN 1209). The Government will inspect the Long Term Supportability Data Package prior to its placement in escrow. Initial inspection of the Long Term Supportability Data Package shall be performed concurrently with the PCA. The contractor shall provide support to the Government, as required, during the inspection. The contractor shall manage the Long Term Supportability Data Package configuration and shall process documentation control numbers as changes occur to the system configuration.

C.3.6.5.3 Procurement of Long Term Supportability Data Package The Government shall have the option to purchase the LTSDP in the event that:

a. The Contractor fails to provide logistical support or

b. The Contractor bankrupts or

c. The Contractor fails to perform.

As ordered by the Government (CLIN 1205), the contractor shall deliver:

a. the LTSDP held in escrow,

b. the production and depot repair level test beds (utilized for repair and testing i.e., modules, mother boards, and circuit cards),

c. the test beds utilized in the performance of the repair of the equipment, and

d. any applicable support data not already in the LTSDP.

Page C-23

C.3.6.6 Logistics Management Information As ordered by the Government, the contractor shall deliver to the Government the data products contained on the attached Logistics Management Information (LMI) Data Products (CDRL-L006) Worksheets in the format attached to CDRL-L006. The data products shall represent the system design configuration including systems, subsystems, components, assemblies, subassemblies, support and test equipment, and training equipment.

a. The contractor shall provide LMI data to the LRU level for all COTS, modified COTS, NDI, and developmental items.

b. Data for temporary items are not required.

The contractor shall adhere to the data definitions, edits, and data formats as described in Appendix B, MIL-PRF-49506, the attached LMI Data Products worksheets, and the Product Format. The contractor shall develop and deliver a LMI Plan, in contractor format; as an attachment to the ISP (CDRL-L001). The LMI plan shall detail the contractor’s plan for performing the logistics requirements specified in this contract.

The contractor shall make maximum use of previously collected and analyzed data, and documentation prepared for COT/NDI hardware/components whenever possible.

Unless otherwise agreed to by the Government, all meetings and reviews to be held at the contractor's facility shall be understood to mean a contractor facility located in the Continental United States (CONUS).

C.3.6.6.1 Hardware Breakdown Structure As ordered by the Government, the contractor shall provide a top-down hardware breakdown structure to the LRU level on all hardware. The contractor shall update the breakdown structure during the Government’s functional and physical configuration audits (FCA/PCA) and during the Provisioning Conference. After the Provisioning Conference the contractor shall deliver the Final Breakdown Structure (CDRL-L002) to the Government for approval.

C.3.6.6.2 LMI Data Reviews As ordered by the Government, the contractor shall present LMI data for review at Technical Interchange Meetings (TIMs), program management reviews and logistics meetings.

C.3.6.6.3 LMI/Provisioning Guidance Conference As ordered by the Government, the contractor shall host and participate with the Government in a Provisioning Guidance Conference (PGC) that shall be scheduled in conjunction with the Post Award Conference (see Section C.3.1.1.1, item a. above). The contractor shall ensure the

Page C-24 participation of appropriate contractor/subcontractor personnel who shall be responsible for preparing the logistics and training deliverables specified in this contract.

The purpose of the PGC shall be to ensure contractor understanding of the logistics requirements specified in this contract. The Government will prepare the agenda for the PGC.

C.3.6.6.4 Provisioning Conference As ordered by the Government (see Section C.3.1.1.1, item g. above), the contractor shall host and support Provisioning Conference(s) (PCs) as specified in the LMI Data Products, CDRL-L006. The PC shall be held at the contractor’s facility unless otherwise specified by the Government. The contractor shall ensure the participation of knowledgeable contractor/subcontractor personnel. A PC shall be held, as mutually agreed upon, approximately 60 days after submission of the LMI.

During the PC, the contractor:

a. Shall make all Government approved drawings (e.g., approved during a physical configuration audit), both proprietary and non-proprietary, available for Government to use as references. The Government will not copy or remove any proprietary data from the contractor’s facility.

b. Shall have copies of the Government approved FCA/PCA documentation available for use as a reference.

c. Shall make samples of systems, assemblies, and parts listed in the approved Parts Master File (PMF) available for examination for the duration of the conference.

d. Shall furnish technically knowledgeable personnel to disassemble the equipment to the extent required by the Government, and such tools as may be needed for disassembly/reassembly.

e. Shall provide facilities, e.g., office space, conference room, access to telephone/facsimile, etc., for the Government provisioning team and contractor personnel. The number of Government participants in the PC will be provided to the contractor prior to the conference.

f. Shall ensure the participation of contractor personnel with detailed knowledge of the subject matter they represent, e.g., provisioning, provisioning and technical documentation, hardware/software maintenance, engineering and system design, etc.

At any time during the term of this contract or any extension thereof, the Government reserves the right to order additional provisioning conferences and the updates to LMI data that will be required to support the PC.

Page C-25

C.3.6.6.5 Cataloging Cataloging is a provisioning task performed by the Government. The purpose of cataloging is to assign unique identifiers to selected pieces of equipment, dependent on the need to carry stock.

Using delivered LMI, the FAA will screen the data with Defense Logistics Information Service (DLIS) for national stock numbers (NSNs), ensuring no duplication of NSNs and assigning NSNs as needed. The process starts with the LMI provided for the Provisioning Conference and results in assignment of NSNs for unique equipment.

C.3.6.7 Depot Spares As ordered by the Government and after the provisioning conference, the Government may order depot spares as required. The contractor shall package and ship the depot spares in accordance with this contract.

C.3.6.8 Tools and Test Equipment As ordered by the Government (CLIN 1004), the contractor shall prepare and deliver to the Government a list of all the tools and test equipment (T&TE), both common and special, that are not an integral part of the receivers and transmitters but are required to inspect, test, calibrate, service, and repair them. This list shall include only the tools and test equipment required to perform authorized site maintenance tasks (e.g., fault isolation and replacement to the LRU level). The list shall be in contractor format, include a section for all common and a section for all special T&TE, provide a detailed description of each tool and test equipment, the tool/test equipment part number and the manufacturer’s CAGE code, and the quantity required at each site to support the receivers and transmitters. The contractor shall ensure that the T&TE data on the list agrees with the T&TE information contained in receivers and transmitters technical documentation, e.g., the technical instruction book.

C.3.6.9 Spare Parts C.3.6.9.1 Spare Parts-Peculiar As ordered by the Government (CLIN 1212), the contractor shall deliver in their format a Spare Parts Peculiar List and all items specified as part-peculiar. The Contractor shall not be required to provide the List any earlier than LMI Data (CDRL L006).

C.3.6.10 Bar Code Asset Tracking System Each piece of equipment identified in Section B and ordered and delivered to the FAA shall have a bar code identifying the item in accordance with the FAA approved Bar Code.

Page C-26

C.3.6.10.1 General Requirements C.3.6.10.1.1 Identification Markings The contractor shall provide identification markings on all system packaging and containers. The following identification information shall be marked on all containers. Additional identification markings may be required by the contract and shall be placed either below these markings or in a conspicuous location on the identification-marked side(s) of the container. In the case of multiple items in single shipping containers, the shipping container will have a packing list that identifies all items within it, and each item within shall follow these marking requirements.

a. NSN (National Stock Number). The in-the-clear NSN will include spaces or dashes and any prefix or suffix specified in the contract or solicitation. The bar coded NSN and human readable interpretation (HRI) below the bar code will not include spaces or dashes, unless otherwise specified in the contract or solicitation.

b. CAGE code. The CAGE code of the company awarded the contract for the item being shipped.

c. Part Number. If a PN is specified in the contract or order, then only that PN shall be shown. The PN specified in the contract may be the PN assigned by the Government procuring activity, or it may be the PN of the actual manufacturer or the PN assigned to the item by the company awarded the contract. The letters "PN" or "P/N" shall be used to identify this information. If the item has no PN assigned to it or if no PN is cited, then nothing is shown.

d. Item description or nomenclature. The exact name and description of an item as it appears in the contract, purchase order or requisition shall be shown. Item description may be marked on more than one line if required due to space limitations. Standard abbreviations, although not desired, may be used if marking length is excessive.

e. Quantity and UI. A non-definitive UI shall be accompanied by a quantitative expression such as "1 RO (100 FT)."

f. Contract number or purchase order number (Procurement Instrument Identification Number (PIIN)) including four-digit delivery order or call number, modification for change order number, and lot number shall be shown. The in-the-clear contract number will include the dashes as shown in the contract, i.e., DTFAXX-XX-X-XXXXX.

Additional information may be required by the contract or purchase order.

g. Shelf-life markings, if applicable, shall be applied as specified below.

Page C-27

h. Serial number(s). When an item is assigned a serial number, that number shall be applied and preceded by the abbreviation "SER NO".

i. Gross weight. The capital letters "WT" shall precede the gross weight. The gross weight will be expressed in pounds rounded up to the nearest pound.

C.3.6.10.1.2 Warranty Markings When an item is procured with a warranty agreement, warranty markings shall be applied to all containers. Warranty markings shall indicate the time period or condition of the warranty (e.g., days/months, hours of operation, etc.). Warranty markings shall be applied by labeling, and shall be prefaced by the words "WARRANTIED ITEM." All warranty information, including "WARRANTIED ITEM," shall be in upper case letters of the same style font. The markings shall be located adjacent to or below the identification markings.

C.3.6.10.1.3 Electrostatic Discharge Sensitive (ESD) Devices Electrostatic Discharge Sensitive devices shall have identifying markings IAW MIL-STD-129.

C.3.6.11 Bar Code Markings Bar code markings, as applicable, are required for contractor-originated shipments, unless specifically exempted in the contract. The Bar Code Markings shall include all identification marking requirements of Section C.3.6.10.1.1 above plus the following individual item identifiers described in this section.

C.3.6.11.1 Individual Item Marking Requirements for LRU In addition to the package container having the items from C.3.6.11, the following barcode requirements that identify an individual LRU item will be placed in 2D Barcode format as specified in this section on the outside of the individual container (number 1) and on the front (number 2) of the LRU itself to total two (2) barcodes per individual LRU item. Identification bar code markings shall not be obscured by application of strapping or tape and shall be readily readable by a barcode scanner upon installation. The FAA 2D Datamatrix specification can also be found in the FAA Asset Identification Process and Procedure Guide, published February 24, 2011, but this contract direction takes precedence over any information in that guide.

Page C-28

2D Data matrix with Part Number, Cage Code, Serial Number and GS1 GIAI

Data Element Data Content Length Message Header [)> 3 Record separator (RS) Chr(30) 1 Format Header 05 2 Group separator (GS) Chr(29) 1 Application Identifier 8004

The Application Identifier (AI) for assets is 8004. It tells the scanning application that the data that follows is an asset number.

This prevents common errors, like a serial number being mistaken for an asset number.

Company Code Prefix Unique company identification assigned by GS1 US to members.

It ensures the asset number is unique worldwide.