DRAFT ETR Section C 10-5-18 CJM.pdf

10/12/2018 693KA8-18-R-00007

Page C-1

PART I – SECTION C

STATEMENT OF WORK

TABLE OF CONTENTS

C.1. INTRODUCTION

C.1.1 Purpose C.1.2 Scope

C.2. APPLICABLE DOCUMENTS

C.2.1 SPECIFICATIONS

C.2.2 STANDARDS AND ORDERS

C.3. REQUIREMENTS

C.3.1 EQUIPMENT & ASSOCIATED EQUIPMENT/DOCUMENTATION/SOFTWARE

C.3.1.1 Documentation C.3.1.2 Software C.3.1.3 Optional Maintenance Data Terminal Software (MDTS) Enterprise License (MDTSEL)

C.3.2 CONTRACT MANAGEMENT

C.3.2.1 Program Management C.3.2.1.1 Performance Based Management System (PBMS) C.3.2.1.2 Contract Work Breakdown Structure (CWBS) C.3.2.2 Integrated Master Schedule (IMS) C.3.2.3 Quality System Plan (QSP)

C.3.3 CONFIGURATION MANAGEMENT

C.3.3.1 Configuration Identification C.3.3.2 Documentation Management C.3.3.3 Product Baseline C.3.3.4 Configuration Control C.3.3.5 Configuration Status Accounting C.3.3.6 Configuration Audits C.3.3.6.1 Functional Configuration Audit (FCA) C.3.3.6.2 Physical Configuration Audit (PCA) C.3.3.6.2.1 PCA Conduct

C.3.4 MEETINGS

C.3.5 PROGRAM REPORTING

C.3.5.1 Monthly Progress Status Report (MPSR) C.3.5.2 Quarterly Financial Progress Status Report (QFPSR) C.3.5.3 Performance Report (PR)

C.3.6 INTEGRATED LOGISTICS SUPPORT (ILS)

C.3.6.1 Point of Contact C.3.6.2 National Airspace Integrated Logistics Support (NAILS) Program C.3.6.3 Integrated Support Plan (ISP) C.3.6.4 Logistics Guidance Conference (LGC) C.3.6.5 Logistics Management Information (LMI) C.3.6.5.1 LMI Data Acceptance Criteria

Page C-2

C.3.6.5.2 LMI Data Reviews C.3.6.5.3 Provisioning Conference (PC) C.3.6.6 Final Breakdown Structure C.3.6.7 Tools and Test Equipment List (T&TEL) C.3.6.8 Repairs C.3.6.8.1 Cannot Duplicate/No Fault Found (CND/NFF) C.3.6.8.2 Non-warranty Repair C.3.6.8.3 Monthly Repair Status Reports (MRSR) C.3.6.9 Technical Instruction Books (TIB) C.3.6.10 Training C.3.6.10.1 Training Guidance Conference (TGC) C.3.6.10.2 Environmental Occupational Safety and Health (EOSH) C.3.6.10.3 Personnel Qualification Report (PQR) C.3.6.10.4 Training Development Plan (TDP) C.3.6.10.5 Task and Skills Analysis (TASA) Report C.3.6.10.6 Course Design Guide (CDG) C.3.6.10.7 Student Achievement Tests (SAT) C.3.6.10.8 Theory of Operations (TOO) Course C.3.6.10.9 Course Walk-Through (CWT) – Contractor’s Presentation C.3.6.10.10 Operational Tryout (OTO) C.3.6.10.11 On-the-Job Training (OJT) Package C.3.6.10.12 Performance Examination C.3.6.11 Long Term Supportability Data Package (LTSDP) C.3.6.11.1 Escrow Account Index (EAI) C.3.6.11.2 LTSDP Inspection C.3.6.11.3 LTSDP Procurement

C.3.7 BAR CODE AND ASSET TRACKING SYSTEM

C.3.7.1 Identification Markings C.3.7.1.1 Warranty Markings C.3.7.1.2 Electrostatic Discharge (ESD) Sensitive Devices C.3.7.1.3 Individual Item Marking Requirements for LRU C.3.7.1.4 Human Readable Interpretation (HRI) C.3.7.2 Applying Identification Bar Codes on Containers C.3.7.3 Production, Warranty, and Repair Data Requirements C.3.7.4 FAA Scanning Process C.3.7.4.1 FAA Scanning Process Steps C.3.7.4.1.1 Contractors Using GFE for Scanning C.3.7.4.1.2 Contractors Using Internal Processes for Scanning C.3.7.5 FAA Scanning Process Pilot Run C.3.7.5.1 Pilot Run Definition C.3.7.5.2 Criteria for a Successful Pilot Run

C.3.8 TEST

C.3.8.1 Point of Contact C.3.8.2 Contractor Master Test Plan (CMTP)

Page C-3

C.3.8.2.1 Contractor Verification Requirements Traceability Matrix (CVRTM) C.3.8.2.2 Test Tool Accreditation Plan C.3.8.2.3 Problem Trouble Report (PTR) Processing C.3.8.3 Factory Acceptance Test (FAT) C.3.8.3.1 FAT Plan C.3.8.3.2 FAT Procedures C.3.8.3.3 Test Readiness Review (TRR) C.3.8.3.4 FAT Report C.3.8.4 FAA Operational Test (OT) C.3.8.4.1 OT Equipment C.3.8.4.2 ET Product Familiarization C.3.8.4.3 OT and FF Technical Support Services C.3.8.5 Production Acceptance Test (PAT) C.3.8.5.1 PAT Plan C.3.8.5.2 PAT Procedures C.3.8.5.3 PAT Report C.3.8.6 Production Unit Test (PUT) C.3.8.6.1 PUT Plan C.3.8.6.2 PUT Procedures C.3.8.6.3 PUT Report

C.3.9 TECHNICAL SUPPORT SERVICES

C.3.10 TELEPHONIC SUPPORT

Page C-4

C.1. INTRODUCTION

C.1.1 Purpose This Statement of Work (SOW) defines the requirements for the Contractor to deliver Emergency Transceiver (ET) equipment in accordance with (IAW) Federal Aviation Administration (FAA) ET Product Specification (FAA-E-7868) in Section J01.

The purpose of the ETR contract is to provide emergency air/ground communication capability for air traffic control (ATC) operations during catastrophic failure of the normal radio communication system. Communication failure might be experienced during loss of ATC facility power, or the failure of the inter/intra facility connectivity to the air/ground radio communications equipment. ET also provides emergency radio communication when a facility must be abandoned, e.g., in the event of facility fire, bomb threat, or severe weather. The ET provides the air/ground communication capability during the first critical 60 minutes after these events occur. The ET will replace the existing grab-n-go Transceiver Communications Equipment (TCEs) at all Air Traffic Control Towers (ATCTs), Terminal Radar Approach Control (TRACON), and Alaskan Flight Service Stations.

C.1.2 Scope The ETR contract scope encompasses all necessary equipment, software, documentation, and Contractor services required to replace existing emergency transceivers. Contractor services include warranty and repair, contract and program management, configuration management, integrated logistics support, bar code and asset tracking, support of Government testing activities, development of maintenance/operator training, support of Government spares provisioning and maintenance program and other required services necessary for the implementation, maintenance, and operation of the emergency transceivers.

The scope of the ID/IQ contract encompasses acquisition of future emergency communications equipment and/or services required during catastrophic failure of the normal radio communications systems or during emergency facility abandonment. Such additional equipment/services and their associated performance specifications would be determined as these requirements are identified. In addition, the ET equipment, software, and services may be ordered to support Department of Transportation (DOT) requirements, other FAA Program Offices, and other Government agencies, as needed.

C.2. APPLICABLE DOCUMENTS

The versions of the following documents in effect at Contract award are included in this SOW.

C.2.1 SPECIFICATIONS

FAA:

FAA-E-7868 NEXCOM II Emergency Transceiver Product Description

Page C-5

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

C.2.2 STANDARDS AND ORDERS

FAA:

FAA-Order 6000.15 General Maintenance Handbook for National Airspace System

(NAS) Facilities

FAA-STD-021 Configuration Management

FAA Order 3000.22 Air Traffic Organization Outcomes-Based Technical Training

FAA Order 3000.57 Air Traffic Organization Technical Operations Training and

Personnel Certification Programs

FED-STD-05 Standard Guides for Preparation of Proposed Item Logistics Data Records

Others:

GEIA-STD-0007-A Logistics Product Data Handbook (SAE)

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

C.3. REQUIREMENTS

The Contractor must fully manage all work to ensure its efficient and timely execution. The requirements include the specifications and standards set forth in SOW Section C.2. The data to be delivered by the Contractor, as a result of performing the tasks prescribed by this SOW, are specified in the Contract Data Requirement Lists (CDRLs) and Data Item Descriptions (DIDs) in Attachment J02 of the contract.

C.3.1 EQUIPMENT & ASSOCIATED EQUIPMENT/DOCUMENTATION/SOFTWARE

The Contractor for the ET equipment must have control over all aspects of this contract process.

The Contractor must provide equipment, firmware, and software that meet the contract’s requirements. The equipment, firmware, and software provided under this contract must be supported by the Contractor for the life of the contract and warranty period. The equipment includes the associated components, interface cables, firmware, and software.

Page C-6

C.3.1.1 Documentation The Contractor must provide a copy of the documentation for comparable commercial off the shelf (COTS) equipment, firmware, and software. A final list of this documentation must be provided at the end of the Post Award Conference as described in Section C.3.4.a.

C.3.1.2 Software The Contractor must provide and deliver to the Government all COTS executable (loadable) software IAW CDRL-S001 and CDRL-S002, which is part of the equipment delivered by the Contractor. The Government’s requirement is to allow internal Government transfer, update, etc.

of all associated software, without encumbrance, for the life of the system. The Contractor:

a) Must provide fully paid-up and transferable software licenses and the associated documents IAW with Section C.3.3.1, Configuration Identification.

b) Must provide the Government with the authorization to prepare back-up copies of all software delivered with the equipment without restriction. Exceptions such as commercial software where the Contractor holds no license must be identified prior to Production Acceptance Test (PAT).

c) Must provide the Government copies of all the Contractor’s validated software updates and modifications (e.g., routine updates to improve performance, enhance maintenance operations, correct system shortcomings), and the associated test procedures IAW CDRL- T001. Upon Government testing and approval, the software updates and modifications must be incorporated into the Configuration Status Accounting Reports (CSARs) IAW CDRL-A008 as specified by section C.3.3.5. The Product Baselines (Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) as necessary) must also be updated to reflect the current software releases.

d) Must describe the process for accommodating software upgrades and future version changes IAW Section C.3.3, Configuration Management Plan.

C.3.1.3 Optional Maintenance Data Terminal Software (MDTS) Enterprise License

(MDTSEL)

The Contractor must provide an enterprise license for the MDTS IAW CDRL-S003. This license will allow FAA and its support Contractors to distribute the MDTS freely without restriction.

Page C-7

C.3.2 CONTRACT MANAGEMENT

The Contractor must provide the required personnel and facilities to manage and administer the work required under the contract. This contract requires program management, planning, testing and testing management, configuration management, logistics planning and logistics management, quality assurance, scheduling, and coordination activities. These activities include the internal and external management activities necessary for basic contract performance, reporting progress, demonstrating results, and coordinating technical activities with the FAA.

C.3.2.1 Program Management The Contractor must maintain programmatic control over the work performed under this contract, including subcontractors and vendors. The Contractor must provide and maintain a Program Management Plan (PMP) as specified by CDRL-A001 and manage the contract in compliance with the approved PMP. The PMP must include the Quality System Plan (QSP) (CDRL-A005), defined in section C.3.2.3 and the Configuration Management Plan (CMP) (CDRL-A006), defined in section C.3.3, as they are integral to the successful execution of the contract. The Contractor must provide an Integrated Master Schedule (IMS) (CDRL-A004), defined in section C.3.2.2, as part of the PMP. The Contractor must specify an individual who serves as the Program Manager and will manage the contract using the PMP.

C.3.2.1.1 Performance Based Management System (PBMS) The PBMS is an internal management system which provides for reporting contract performance information to the Government. The Contractor must plan, schedule, budget, monitor, manage, and report performance applicable to the contract. The Contractor's PBMS must be the single point of integrated formal reporting for the Government. This reporting system must meet both the Contractor's internal management requirements and the requirements of the FAA for timely, reliable performance reporting information.

C.3.2.1.2 Contract Work Breakdown Structure (CWBS) The FAA will provide the Contractor a high-level framework for developing a complete CWBS.

The Contractor must generate and maintain a CWBS Dictionary for this effort based upon the standard FAA Work Breakdown Structure (WBS) defined in the FAA Acquisition Standard Toolset (FAST – http://fast.faa.gov) and IAW CDRL-A002 and CDRL-A003. The CWBS framework provided by the FAA will serve as the basis for further extension by the Contractor to lower levels during the performance of the contract. The Contractor must extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for FAA visibility.

The CWBS must identify the Government program or project that work is being performed on by utilizing a prefix code specified by the FAA. Contract modifications that modify, add, or delete work scope under the contract must be incorporated into appropriate CWBS elements for work effort identification, definition, and procurement request relationships, as in the basic contract.

The FAA will approve the CWBS. The Contractor must not change the approved CWBS, Page C-8 associated definitions, or any of the reporting elements without prior written approval from the CO during the performance of the contract.

C.3.2.2 Integrated Master Schedule (IMS) The Contractor must provide an IMS (CDRL-A004), as part of the PMP, which must be consistent with the CWBS. A field may be set aside to record the CWBS number if using the CWBS as part of the Activity ID proves restrictive. The Contractor must manage the execution of the contract using the IMS as the day-to-day planning and execution tool, and to assess program progress in meeting program requirements. The Contractor must report on program progress consistent with the IMS at each program management review, at selected technical reviews, and at other times at the Government’s request. The Contractor must revise the IMS, when necessary; to reflect current and changing contract milestones and deliverables. The IMS must include all activities and dependencies of the Contractor, subcontractor and interrelated Government activities (e.g.

Operational Test). All Contractor schedule information delivered to the Government or presented at program reviews must originate from the IMS. The Contractor must perform appropriate analyses of the IMS tasks and report potential or existing problem areas and recommend corrective actions to eliminate or reduce schedule impact to the program.

C.3.2.3 Quality System Plan (QSP) The Contractor must have quality control over all aspects of this contract, including the production process. The Contractor must maintain and update a QSP (CDRL-A005) IAW Section E, Quality Assurance Requirements of this contract. The QSP that complies with Section E of the contract must be attached to the PMP (CDRL-A001) as an appendix and integrated into the overall program.

The Contractor must operate under the approved PMP and its integrated QSP. The PMP must outline how the QSP will be applied for this contract. The Contractor must maintain quality control over work performed by subcontractors and vendors.

C.3.3 CONFIGURATION MANAGEMENT

The Contractor must have configuration management control over all contract deliverables including the production process. The Contractor must maintain and update a CMP (CDRL-A006) that is integrated into the PMP (CDRL-A001). The Contractor must maintain configuration management on all Configuration Items and Documentation, described in sections C.3.3.1 and C.3.3.2 respectively, IAW the approved CMP. The Contractor must specify an individual who serves as a point of contact for all configuration management related issues. The Contractor must maintain configuration control over work performed by subcontractors and vendors to include, but not limited to, configuration identification (hardware, software, and documentation), establishment and control of configuration baselines (FCA and PCA), configuration status accounting, and audits.

Page C-9

C.3.3.1 Configuration Identification The Contractor must maintain a system to identify, bar code, label, serialize, and mark Hardware Configuration Items (HWCI) and Software Configuration Items (SWCI) to provide traceability from delivery of the first FAA production unit to the final unit delivered under this contract. The identification process of HWCI and SWCI must be detailed in the CMP.

C.3.3.2 Documentation Management The Contractor must deliver documents under this contract that adhere to configuration management practices as identified in section C.3.3. The Contractor must identify by titling, labeling, numbering, identifying date of publication, identifying originator of the documentation, and cataloging all documentation. The procedures used must accomplish the following:

a) Identify specific versions of each element, HWCI, and/or SWCI to which a document applies; and,

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

C.3.3.3 Product Baseline The Contractor must establish the Product Baseline after successful completion of the Factory Acceptance Test (FAT), described in section C.3.8.3, FCA, described in section C.3.3.6.1, and the PCA, defined in section C.3.3.6.2. The Product Baseline must occur prior to PAT, described in section C.3.8.5. The software versions and components comprising the Lowest Replaceable Unit (LRU) must form the basis of the Product Baseline identified in the Final Breakdown Structure, described in section C.3.6.6. An LRU is the lowest level subassembly that can be replaced during site level maintenance activities. The Government will review for approval the results of FAT, FCA, and the PCA for the establishment of the Product Baseline. The Product Baseline results in the identification of an established Government accepted baseline of hardware and software versions. The CSAR (CDRL-A008), described in section C.3.3.5, must be part of the Product Baseline documents submitted for review and is the mechanism for tracking changes to the Product Baseline.

Page C-10

C.3.3.4 Configuration Control The Contractor must extend configuration control to include hardware, software, and documentation. The Contractor must maintain a Configuration Control Board (CCB) to support baseline management of the Product Baseline. The Contractor must maintain traceability, currency of the baselines, and consistency among all project documentation, hardware, and software. Changes generated by the Contractor after the Product Baseline has been established, which provide the same form, fit and function will not require formal approval by the Government.

This type of change, known as a Class II change, must be determined in concert with the Government. All changes that affect any of the Product Baseline documents or the Logistics Management Information (LMI) will require Government approval. Any such changes, known as Class I changes, must be submitted to the CO as Engineering Change Proposals (ECPs) (CDRL- A007). An accepted Class I change may require successful re-performance of FAT as described in section C.3.8.3. Class I and Class II changes are defined in FAA-STD-021A paragraphs 80.4.1.and 80.4.2.

The Contractor must submit the proposed changes prior to implementing any changes into the system design. FAA configuration control over system functional performance will be in effect from formal approval of the FCA. FAA configuration control over the physical form, fit, and function will be in effect from the formal PCA approval until the warranty expiration of the ultimate units delivered IAW this contract.

C.3.3.5 Configuration Status Accounting The Contractor must generate CSARs (CDRL-A008) to document changes to the Product Baseline. The CSAR identifies the configuration items, status of changes, and provides the supporting documentation reflecting these changes. The CSAR must provide traceability of any change through the change control process. The first submission of the CSAR must be generated for the Product Baseline as part of establishing the baseline.

C.3.3.6 Configuration Audits The Contractor must host a Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA) at the Contractor's facility. These audits must include all hardware, software, and documentation. The Contractor must submit the PCA Report, describing conduct and results of the audit as an attachment to the meeting minutes (CDRL-A006) for the PCA. The report must catalog any discovered deficiencies and provide conclusions and recommendations as well as planned corrective actions. The Government will disapprove the audit if identification of major discrepancies such as unbaselined (missed requirement traceability) specifications, invalid or unverified requirements and uncorrected test failures are found. The Government will indicate whether the audit is approved without conditions, approved with contingencies, or disapproved.

Production orders will not be placed until all deficiencies are resolved and the audits are approved by the Government. The Government will not schedule audits until the prerequisite material or contract requirement is successfully completed.

Page C-11

C.3.3.6.1 Functional Configuration Audit (FCA) The purpose of the FCA is to ensure that the system meets the functional performance requirements defined in the Product Specification (FAA-E-7868). The Government will review the FAT results prior to conducting the FCA. FCA must be conducted within 60 calendar days after the successful completion of the FAT and acceptance of the FAT Report, described in section C.3.8.3.4. The FCA is one of several meeting types outlined in section C.3.4.c). Production orders will not be placed until the Government has approved the Contractor’s proposed corrective actions for any unresolved FCA deficiencies.

C.3.3.6.2 Physical Configuration Audit (PCA) The purpose of the PCA is: 1) to review top level design documentation for each LRU to validate that the Contractor has adequate engineering drawings to continue production of the hardware, software, and documentation; and 2) to identify the baselined physical characteristics of the various devices and control changes (for FAA support purposes). The PCA must be conducted no more than 60 days after the successful completion of FCA, described in section C.3.3.6.1, on the equipment that passed the FAT. The Contractor must provide technically competent personnel to disassemble the equipment as necessary, and to respond to Government queries during the PCA.

Prior to conducting the PCA, the Contractor must resolve all action items assigned at FCA and provide documentary evidence of the resolution. The Government will not place production orders until all proposed corrective actions are approved. The PCA is one of several meeting types outlined in section C.3.4.d).

C.3.3.6.2.1 PCA Conduct The PCA baseline is established at the external perimeter of the primary LRUs, and includes all appurtenances, appliances, ancillary equipment, etc. that are part of the delivered device and/or that may be replaced for support purposes. The purpose of this baselining is to permit reliable configuration control by the FAA over the deployed equipment while avoiding unnecessary government involvement in internal system design.

C.3.4 MEETINGS

The Contractor must prepare and deliver to the Government an agenda, as specified by CDRL- A009, prior to each conference and meeting. The Contractor must record and prepare minutes, as specified by CDRL-A010, for each scheduled conference and meeting. Contractor administrative support must be provided only when meetings or conferences are held at a contractor facility. Such support may consist of providing facilities, office equipment, and clerical support. The Contractor must provide facilities with adequate accommodation to house a Government team that will generally consist of no more than twenty-five (25) representatives. The Government will not pay the direct costs for the meeting listed below, other than the price of the CLINs associated with CDRLs A009 and A010.

The Contractor must participate in the following meetings IAW contract requirements.

Page C-12

a) Post Award Conference (PAC). The Contractor must plan, host, provide administrative support, and participate in a PAC to be held at the Contractor’s facility, within the 48 contiguous states following contract award. The Government will determine the actual date of the PAC, which will occur no later than 60 calendar days after the contract award date. The PAC is held to provide detailed clarifications of the Government’s expectations of the contract. The PAC agenda is set by the Contactor but approved by the FAA. During the PAC, the Contractor must brief the plans and schedule for satisfying each SOW requirement and provide a list of all the COTS documentation that will be delivered with the software and equipment. The Contractor must include the finalized list of the COTS documentation as part of the PAC meeting minutes.

b) Logistics Guidance Conference (LGC), described in section C.3.6.4, and the Training

Guidance Conference described in Section C.3.6.10.1 must be at the Contractor’s facility, within the 48 contiguous states.

c) FCA, described in section C.3.3.6.1, must be at the Contractor's facility within the 48 contiguous states.

d) PCA, described in section C.3.3.6.2 , must be at the Contractor's facility within the 48 contiguous states.

e) Provisioning Conference, described in section C.3.6.5.3, must be at the Contractor’s facility within the 48 contiguous states.

f) Four Program Management Reviews (PMRs) will be held annually. The Government anticipates that two PMRs will be held at FAA Headquarters and two PMRs will be held at the Contractor's facility within the 48 contiguous states. The FAA will determine the location of PMRs and notify the Contractor NLT 21 calendar days in advance.

g) Technical Interchange Meetings (TIMs). The Contractor must support and participate in TIMs. The purpose of these meetings is to promote a free exchange of ideas between the Contractor and the Government in order to identify and resolve technical problems. The Contractor must provide the appropriate subject matter experts in order to respond to Government questions. The Contractor and FAA will coordinate the best location for the meetings. The Contractor must propose an agenda to the Government for review and approval for each TIM no later than 10 calendar days prior to each TIM.

Meetings will be coordinated with the Contracting Officer’s Representative (COR) and approved by the Contracting Officer (CO). Teleconference meetings may be held in lieu of travel. The CO will notify the Contractor of the Government's readiness at least 15 working days in advance of each teleconference. The Contractor must prepare minutes and action item list in support of all teleconferences and TIMs.

Page C-13

C.3.5 PROGRAM REPORTING

C.3.5.1 Monthly Progress Status Report (MPSR) The Contractor must track and report the identification and status of new and existing risks, action items, and problems as identified in the PMP. This data must be maintained for the life of the contract and no entry will be deleted without Government approval. The report must comply with CDRL-A011, the Monthly Program Status Report (MPSR).

C.3.5.2 Quarterly Financial Progress Status Report (QFPSR) The Contractor must furnish QFPSRs (CDRL-A012) that state the financial status of the contract.

C.3.5.3 Performance Report (PR) The Contractor must submit a monthly Performance Report prepared IAW CDRL-A013. The Contractor must report summarized performance information at each Program Management Review, at selected technical reviews, and at other times at the Government's request.

Performance information should be reported by CLIN. The reported budget and actual cost values are FAA prices and not internal Contractor costs.

C.3.6 INTEGRATED LOGISTICS SUPPORT (ILS)

C.3.6.1 Point of Contact The Contractor must specify an individual who serves as a point of contact for all logistics issues.

C.3.6.2 National Airspace Integrated Logistics Support (NAILS) Program The Contractor must establish and maintain a NAILS Program IAW the logistics requirements contained herein. The Contractor must participate as a member of the NAILS Management Team (NAILSMT) for the life of the contract. Participation must consist of attending NAILSMT meetings and resolving problems identified by the NAILSMT. Meeting support must 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.

Unless otherwise agreed to by the Government, NAILSMT meetings must be held at the Contractor’s facility. NAILSMT meetings should be combined with or included as part of other programmatic meetings (i.e., PMRs).

The Contractor must support the NAILSMT by submitting agenda items and ensuring participation (e.g., status briefings) of the Contractor/subcontractor personnel responsible for preparing the ILS deliverables identified in the NAILSMT meeting agenda. The Government will determine whether the Contractor’s subcontractor participation in scheduled meetings is required.

C.3.6.3 Integrated Support Plan (ISP) The Contractor must deliver an ISP (CDRL-L001). The ISP must detail the Contractor’s plan for managing the ILS program for the program life cycle. The ISP will include the Contractor’s

Page C-14

Logistics Management Information Plan. The Contractor must be responsible for ensuring that all subcontractors and vendors comply with the ISP requirements.

C.3.6.4 Logistics Guidance Conference (LGC) As part of the Post Award Conference described in section C.3.4.a), the Contractor must host an LGC. The purpose of the LGC is to ensure the Contractor understands all Integrated Logistics Support tasks. Included in the LGC will be a Provisioning Guidance Conference (PGC). The purpose of the PGC is to ensure contractor’s understanding of the provisioning requirements. The purpose of the TGC is to ensure contractors’ understanding of the training requirements. The Contractor must ensure the participation of appropriate Contractor/subcontractor personnel responsible for preparing the logistics deliverables specified in the contract. The Government will prepare the agenda for the LGC.

C.3.6.5 Logistics Management Information (LMI) The Contractor must deliver to the Government the LMI Data Products (CDRL-L002). The LMI data products must represent the physical top-down breakdown system design configuration including systems, subsystems, components, assemblies, subassemblies, cables and cable assemblies, support and test equipment, and training equipment required by the ET. Data submitted must be to the component level for all developmental items and to the LRU level for all COTS and non-developmental items. Any modification to a COTS item may disqualify it as COTS and may require LMI data to the component level. The Government will determine the level of LMI data required for COTS modified items. The Contractor must identify system LRUs (e.g., printed circuit boards, modules, disk drives, cables and cable assemblies, power supplies, etc.) during the LMI/Provisioning process. All items must be listed in the LMI submissions in the proper top down break down format. The Contractor must update the breakdown structure during the Government’s FCA/PCA and during the Provisioning Conference (PC) as required. After the PC the Contractor must deliver the final breakdown structure to the Government for approval IAW the CDRL-L003. During the PC, the Government has the right to determine final system LRUs.

Additionally, the Government reserves the right to add items it considers to be an LRU that are not considered an LRU by the Contractor. Data for temporary items is not required.

The Contractor must adhere to the data definitions, edits, and data formats as described in Appendix B of GEIA-STD-0007-A.

The Contractor must make maximum use of previously collected and analyzed data, and documentation prepared for COTS hardware and software components whenever possible.

Modified COTS items must be explicitly identified as modified COTS.

Items identified as proprietary must be clearly marked and identified as PROPRIETARY, marked in accordance with Clause 3.2.2.3-16, Restricting, Disclosing and Using Data (July 2004).

C.3.6.5.1 LMI Data Acceptance Criteria The Contractor must adhere to the data definitions, edits, and formats as described in LMI Data Products (CDRL-L002).

Page C-15

C.3.6.5.2 LMI Data Reviews The Contractor must present LMI Data Products for review at TIMs, program reviews, logistics reviews/meetings or via electronic means.

C.3.6.5.3 Provisioning Conference (PC) The Contractor must host and support PC(s), as outlined in section C.3.4 e), The PC must be held at the Contractor’s facility unless otherwise specified by the Government. The Contractor must ensure the participation of ET knowledgeable contractor/subcontractor personnel. A PC must be held no later than 60 calendar days after Government receipt of the initial LMI data.

During the PC, the Contractor:

a) Must make all ET Government approved drawings (e.g., approved during a PCA), 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 unless the Contractor is required to submit such data as part of other submissions.

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

c) Must make samples of systems, assemblies, and parts listed in the approved Product Baseline available for examination for the duration of the conference.

d) Must furnish technically knowledgeable personnel and the tools required to disassemble the equipment, to the extent required by the Government.

e) Must provide facilities (e.g., office space, conference room, access to telephone/facsimile/internet), 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) Must 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).

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

C.3.6.6 Final Breakdown Structure The Contractor must provide a top-down Final Breakdown Structure to the LRU level on all hardware, IAW CDRL-L003, after successful completion of FAT. The Final Breakdown Structure is developed by sequencing all parts comprising the end item in a lateral and descending family tree/generation breakdown. This breakdown must consist of the end item, including all components, listing every assembly, subassembly, and parts, which can be disassembled, reassembled/replaced. All parts are listed in their relation to the end item, component, assembly, or installation system in which they are contained and to their own further sub-subassemblies and parts. This relationship is shown by means of an indenture code. The Final Breakdown Structure

Page C-16 shows the relationship of all items to one another. The Contractor must update the breakdown structure during the Government’s audits (FCA and combined PCA/PC). After the PCA, the Contractor must deliver the Final Breakdown Structure (CDRL-L003) to the Government for approval.

C.3.6.7 Tools and Test Equipment List (T&TEL) The Contractor must prepare and deliver to the Government a list of all the tools and test equipment (CDRL-L004), both common and special, that are not an integral part of the ET but are required to inspect, test, calibrate, service, and repair them. This list must 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 Contractor must ensure that the T&TEL data on the list agrees with the T&TEL information contained in ET technical documentation, e.g., the technical instruction book.

C.3.6.8 Repairs The Contractor must furnish repair services IAW the provisions of this section for all repairable items and/or LRU(s). The Contractor must have the capability and expertise necessary to repair all repairable items and components.

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

The Contractor must furnish all qualified labor, supervision, materials, equipment, tools, appliances, and services to repair components of the equipment. The turn-around-time (TAT) for all repairs must be within 45 calendar days from the receipt of the item for repair unless otherwise specified by the CO.

Repairable items and components will be shipped to the Contractor facility for repair directly from the FAALC. The FAALC Item Manager will furnish shipping instructions for repaired items.

The Contractor must follow the repair requirements identified herein. Unless otherwise directed by the Government, the Contractor must ship the repaired LRU to the FAALC in Oklahoma City, OK.

a) Contractor repair procedures must 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.

4) All repaired LRUs must successfully pass Production Unit Testing (PUT), as described in C.3.8.6, prior to being returned to the Government.

5) The Contractor must integrate repair process activity into the bar code scanning activities IAW C.3.7 and must include such data IAW the bar code scanning reporting requirements in C.3.7.4 for the life of the contract.

Page C-17

b) The Contractor must conduct all repairs IAW the Contractor’s established shop methods and procedures developed for the equipment.

c) When the Contractor determines that an item is beyond the Contractor’s ability to repair or the cost to replace the item is less than the repair cost, the Contractor must promptly notify the FAA CO and submit rationale for that determination. If the FAA CO agrees that an item cannot be repaired, since the non-repairable item is GFE, the FAA CO will provide disposition instructions for the item to the Contractor and may request a replacement in lieu of repair.

d) The Contractor must complete any Government approved modification to items required by the contract and not previously accomplished at the time of repair. Each modified item or LRU must meet form, fit, and function of the item that it replaces and be two-way interchangeable, i.e., unmodified items must operate in place of modified items and modified items must operate in place of unmodified items.

e) The Contractor must be responsible for the initial lay-in of piece parts and for obtaining replenishment units and spare piece parts required for use in the repair of failed items.

These parts must remain the property of the Contractor until incorporated into the repaired items at which time they become Government property. All parts removed during repair become the property of the Contractor.

f) Upon receipt of a failed LRU from the Government, the Contractor must document the receipt and the initial determination of the LRU for warranty or non-warranty repair using the Monthly Repair Status Report (MRSR) described in section C.3.6.8.3 (CDRL-L005).

g) The Contractor must maintain the Government provided FAA Form 4650-12 that accompanies the failed LRU and report the information in the MRSR described in section C.3.6.8.3.

h) The Contractor must prepare the Packing List/Shipping Report/Invoice to include the following information: -Contract Number, Report Control Number, Part Number, Serial Number, Item Description, and National Stock Number for the FAALC receipt of a repaired LRU.

i) After inspection by the Quality Reliability Officer (QRO), the Contractor must ship the repaired LRU to the FAALC with a clean copy of the FAA Form 4650-12, Fed Express shipping label, and instructions inside the container within the contractual turn-around-time (TAT).

C.3.6.8.1 Cannot Duplicate/No Fault Found (CND/NFF) The Contractor must follow the repair requirements in Section C.3.6.8. If the contractor’s repair procedures IAW C.3.6.8 a) do not isolate any fault in the returned item, the return is a CND/NFF.

Page C-18

C.3.6.8.2 Non-warranty Repair The Contractor must follow the repair requirements identified in section C.3.6.8. Non-warranty repairs must apply to each unit that is determined not to be under warranty. This determination must be made IAW Section H.3.j of the contract.

a) The Contractor must fax (or otherwise electronically send) a copy of the FAA Form 4650-

12 and provide supporting information in sufficient detail to demonstrate that the cause of the failure was outside the warranty, to the FAA CO based on section H.3.j of the contract.

b) The transportation costs of equipment determined to be non-warranty repairs will be reimbursed to the Contractor for shipment from the FAA to the Contractor’s repair facility and from the Contractor’s facility to the FAA depot.

c) The TAT for repair of the non-warranty repairs must be the same time as warranty repairs

(refer to Section H.3.g) after receipt of a response from the FAA CO.

d) In the event a repair is required to return a defective LRU back into warranty status, the

Contractor must bill the Non-warranty Repair for the repair costs.

e) Should a defective LRU be determined to be out of the scope of the warranty repair by the

Contractor, the Contractor must provide a fixed repair cost to the FAA CO to determine if the LRU is to be returned to warranty status.

C.3.6.8.3 Monthly Repair Status Reports (MRSR) The Contractor must develop a MRSRs, as specified by CDRL-L005 and must contain the repair information for warranty and non-warranty repair actions.

C.3.6.9 Technical Instruction Books (TIB) The Contractor must develop and provide technical instruction books meeting the requirements of FAA-D-2494, Appendix I, as a minimum. The Contractor must deliver copies of the TIB (CDRL- L008). There must be no restriction on reproduction or use of the TIB. The Contractor must specify an individual who will serve as a point of contact for all TIB issues.

The Contractor must grant the Government unlimited rights to the TIB data, which includes the right to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

C.3.6.10 Training If the Contractor has COTS training materials, the Government requests that the materials be provided with their proposal.

Page C-19

The Contractor must develop and deliver training materials for FAA personnel responsible for operating, maintaining, and performing second level engineering of the ET equipment. Training must be developed using Instructional Systems Development methodologies described in JO3000.22 and JO3000.57 and operations and maintenance requirements of JO6000.15. The Contractor must ensure that training materials comply with the copyright and Section 508 of the Rehabilitation Act (29 U.S.C 749d requirements of JO3000.22. Details for these requirements will be answered during the Contractor hosted TGC.

C.3.6.10.1 Training Guidance Conference (TGC) As part of the Post Award Conference described in section C.3.4.a, the Contractor must host a TGC. The purpose of the TGC is to ensure the Contractor understands all training requirements.

The Contractor must ensure the participation of appropriate Contractor/subcontractor personnel responsible for preparing the training deliverables specified in the contract. The Contractor must submit agendas IAW CDRL-A009 and minutes IAW CDRL-A010.

C.3.6.10.2 Environmental Occupational Safety and Health (EOSH) All training developed or revised by a Contractor must meet or exceed the appropriate Environmental Occupational Safety and Health Administration (EOSHA) regulations (see OSHA 29 CFR 1910). OSHA safety regulations must be integrated into course content, as appropriate.

All instruction must emphasize each person’s accident prevention responsibilities, both as an individual and as a representative of the Government. Safety precautions related to training on the operations, maintenance, and/or troubleshooting of the equipment must be a prominent part of the training.

C.3.6.10.3 Personnel Qualification Report (PQR) The Contractor must submit for Government review and approval, a PQR (CDRL-L011).

C.3.6.10.4 Training Development Plan (TDP) The Contractor must develop and deliver for Government review and approval, a TDP (CDRL- L012).

C.3.6.10.5 Task and Skills Analysis (TASA) Report The Contractor must develop and submit for Government review and approval, a TASA Report

(CDRL-L013).

C.3.6.10.6 Course Design Guide (CDG) The Contractor must develop and deliver for Government review and approval, a CDG (CDRL- L014).

C.3.6.10.7 Student Achievement Tests (SAT) The contractor must provide Student Achievement Tests (CDRL-L015). The contractor must develop a minimum of three examination items for each objective identified in the CDG. The contractor must develop an end of course exam for the Theory (distant learning) course, an EHOT written exam and a Demonstration of Proficiency written exam.

Page C-20

C.3.6.10.8 Theory of Operations (TOO) Course The Contractor must develop and deliver for TOO Course for Government review and approval, a Theory of Operations (TOO) Course (CDRL-L016).

C.3.6.10.9 Course Walk-Through (CWT) – Contractor’s Presentation The Contractor must present the TASA, CDG, examination questions, and TOO course. The Contractor must correct deficiencies identified during the course walk-through. The Contractor must submit corrected course materials for review and approval.

C.3.6.10.10 Operational Tryout (OTO) The Contractor must present the TOO Course in its entirety. The Contractor must correct deficiencies identified during the OTO. The Contractor must submit corrected course materials for review and approval.

C.3.6.10.11 On-the-Job Training (OJT) Package The Contractor must provide an OJT package IAW CDRL-L017.

C.3.6.10.12 Performance Examination The Contractor must provide performance examinations in IAW CDRL-L018.

C.3.6.11 Long Term Supportability Data Package (LTSDP) The Contractor must assemble and submit for review and inspection by the Government, an LTSDP (CDRL-L006). The LTSDP must 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 must 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, must 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 must be provided. Source code for all associated software and firmware must be included within the LTSDP.

C.3.6.11.1 Escrow Account Index (EAI) The Contractor must deliver an EAI (CDRL-L007) of all the technical data contained in the escrow account. The Contractor must 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 must establish and maintain (including bear the cost) of a third-party escrow account containing a complete set of the technical documentation, including proprietary

Page C-21 information, for the portable transceiver system. Changes approved under the Contractor's configuration management program must be applied to the data in escrow. The escrow account must include the following data:

a. Product drawings and associated lists at least equivalent to MIL-T-31000A (i.e., commercial drawings and associated lists for NDI and production drawings for developmental equipment);

b. Special inspection equipment drawings and associated lists;

c. Special inspection equipment operating instructions;

d. Special inspection equipment calibration procedures;

e. Special tooling drawings and associated lists; and

f. Software procedures and products (includes source codes).

Additionally, the escrow account must contain all software products…